- GNSO-Accuracy-ST - lists.icann.org

Registration Data Accuracy Scoping Team | Thursday, 04 November 2021
by Terri Agnew Nov. 4, 2021

Nov. 4, 2021

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 04 November 2021 can be found on the agenda wiki page <https://community.icann.org/x/Lg2HCg> (attendance included) and the GNSO Master Calendar [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive<https://icann.zoom.us/rec/sdownload/hduQWjFS2LW0X0Nn0fZSynNnO9THVn_afKtDw5Y…> * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-accuracy-st/> and the main wiki page<https://community.icann.org/x/hQIuCg>. Thank you! Kind Regards, Terri

1 0

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 11 November 2021 at 14:00 UTC
by Terri Agnew Nov. 4, 2021

Nov. 4, 2021

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 11 November 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/1AC7Cg * Check your time zone: https://tinyurl.com/znz8kmf4 ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://forms.gle/GZqMAi4kKDaVP5o66> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

1 0

Registration Data Accuracy Scoping Team meeting
by ICANN Policy Calendar Nov. 4, 2021

Nov. 4, 2021

Meeting: Registration Data Accuracy Scoping Team meeting Date/time: Recurring weekly on Thursday’s from 11 November - 23 December 2021 at 14:00 UTC for 90 minutes Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the 2021 Wiki agenda pages: https://community.icann.org/x/mwIuCg * Check your time zone: https://tinyurl.com/znz8kmf4 ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://forms.gle/GZqMAi4kKDaVP5o66> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

1 0

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 04 November 2021 at 13:00 UTC
by Julie Bisland Nov. 4, 2021

Nov. 4, 2021

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 04 November 2021 at 13:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/Lg2HCg * Check your time zone: https://tinyurl.com/5zkn6vmc [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5zkn6vmc__;!!PtGJab4!orSeJ0y…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

2 1

Registry Accuracy Reference Data Points
by Michael Palage Nov. 4, 2021

Nov. 4, 2021

So why the baseline Registry Agreement is largely void of any issues on accuracy of registrant data, there are other Registry Operators which have voluntarily subjected themselves to heightened standards via policies and/or RSPEs when it comes to additional data elements collected/processed by Registry Operators that I think touch on accuracy. Listed below are some of the RA policies I will be running up the flag pole with the group. >From the original 2001 proof of concept round, .AERO was one of the first TLD that required the process of registrant data prior to being able to obtain a gTLD domain name registration. If you look at the current .AERO registration website you will see the following requirement: Obtain your .aero ID, prior to registration of your chosen domain name through a .aero authorised registrar, this unique validity process screens potential domain registrants thus ensuring the integrity and the exclusivity of the .aero domain. See https://information.aero/registration and https://information.aero/node/add/request-aero-id >From the 2004 Sponsored round perhaps the best example was .XXX which made the following representations: 5.0 PREVENTING ABUSIVE REGISTRATIONS The Registry will authenticate members of the Sponsored Community, as part of the name registration process. As part of this process, the Registry will validate contact information for the Registrant, secure the Registrant’s affirmative consent to the Registry-Registrant Agreement, and issue unique Membership Credentials. The Membership Application Process must be completed before a domain name is permitted to resolve in the TLD. See https://www.icmregistry.com/about/policies/launch/#general_aval Moving forward to the 2012 Round there were several registries that processed registrant data as part of the registration process: fTLD submitted an approved RSEP to ICANN for the processing of Registrant information prior to registration. The name of this RSEP is Dynamic Registration Verification and is available here, see https://www.icann.org/en/system/files/files/rsep-2017039-bank-et-al-request… This webpage shows the information that fTLD collects from prospective registrants as part of their verification process, see https://www.register.bank/get-started/ NABP, the Registry Operator of .PHARMACY, has also vetted prospective registrants as part of its registration process, see https://nabp.pharmacy/programs/accreditations-inspections/dotpharmacy/#apply In addition, every .BRAND Registry Operator has a requirement to limit registrations in that TLD to either the Brand owner or “Trademark Licensee” so this would be a further example of where a Registry Operator is processing data about a Registrant (e.g. Trademark Licensee) that may or may not appear in the Whois/RDDS output.

1 0

**Starting in 15 minutes | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 04 November 2021 at 13:00 UTC
by Terri Agnew Nov. 4, 2021

Nov. 4, 2021

**starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 04 November 2021 at 13:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/Lg2HCg * Check your time zone: https://tinyurl.com/5zkn6vmc [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5zkn6vmc__;!!PtGJab4!orSeJ0y…> ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri

1 0

Re: [GNSO-Accuracy-ST] Proposed Agenda - Accuracy Scoping Team meeting #4 on Thursday 4 November at 13.00 UTC
by Berry Cobb Nov. 3, 2021

Nov. 3, 2021

Dear Scoping Team, Please find attached the proposed project plan for the Registration Data Accuracy Scoping Team. This plan will be submitted to the GNSO Council for them to acknowledge the proposed deliverable dates. A few notes that the Chair will speak to on Thursday and will be used as messaging to the GNSO Council: * The RDA_ST is setting an aspirational goal to deliver its report to the GNSO Council by ICANN75 and the GNSO Council’s Motions & Documents deadline of 11 Sep 2022. * Assignments #1 & #2 will be worked on mostly in parallel and are scheduled to conclude 24 Jan 2022. * The EPDP will spend the month of February to determine next steps and exactly what must be done to complete Assignment #3. This assignment is the most elusive at this point, as it has a pure dependency to Assignments #1 &#2. The Leadership team is hopeful clarity will be gained as we work through the first two assignments. * At ICANN73, the Leadership team will engage with the GNSO Council to confirm or change the timeline as more clarity about the deliverables from Assignment #3 are achieved. The Chair will provide additional details at our call tomorrow, 4 Nov 2021 at 13:00 UTC. Thank you. RDA_ST Leadership Team Berry Cobb Policy Development - Portfolio Manager Internet Corporation for Assigned Names and Numbers (ICANN) berry.cobb(a)icann.org From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Tuesday, November 2, 2021 at 10:15 To: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: [GNSO-Accuracy-ST] Proposed Agenda - Accuracy Scoping Team meeting #4 on Thursday 4 November at 13.00 UTC Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team which is scheduled for Thursday 4 November at 13.00 UTC. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #4 Thursday 4 November at 13.00 UTC 1. Welcome & Chair Updates * Council non-objection to appointing alternates and vice-chair * Appointment of Council liaison * Adjustment of call time & duration from next week onwards to accommodate for DST 1. Proposed Work plan & timeline * Review proposed work plan & timeline * Confirm next steps 1. Working definition of accuracy From assignment #1: “The Scoping Team shall, with reference to the resources that will be included in the index of relevant resources cited below, consider whether there is an agreed definition of registration data accuracy and, if not, consider what working definitions should be used in the context of the Scoping Team's deliberations. Particular attention should be given to the definition that ICANN Compliance employs for “accuracy” in ICANN’s contracts. Note, this does not preclude any subsequent effort from formalising the definition(s) that should be applied in the context of any existing and/or new accuracy requirements that may be developed”. * Review input received on definition (see page 12 - https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1k9fvA4gnb13b…>) * Consider whether in addition to working definition focused on current application, input should be requested on aspirational definitions to identify perceived gap between current definition and aspirational definition * Scoping team input * Confirm next steps 1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System * Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1…> * Scoping team input * Confirm deadline for submission of questions 1. Confirm action items & next meeting (Thursday 11 November at 14.00 UTC)

1 0

Proposed Agenda - Accuracy Scoping Team meeting #4 on Thursday 4 November at 13.00 UTC
by Marika Konings Nov. 2, 2021

Nov. 2, 2021

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team which is scheduled for Thursday 4 November at 13.00 UTC. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #4 Thursday 4 November at 13.00 UTC 1. Welcome & Chair Updates * Council non-objection to appointing alternates and vice-chair * Appointment of Council liaison * Adjustment of call time & duration from next week onwards to accommodate for DST 1. Proposed Work plan & timeline * Review proposed work plan & timeline * Confirm next steps 1. Working definition of accuracy From assignment #1: “The Scoping Team shall, with reference to the resources that will be included in the index of relevant resources cited below, consider whether there is an agreed definition of registration data accuracy and, if not, consider what working definitions should be used in the context of the Scoping Team's deliberations. Particular attention should be given to the definition that ICANN Compliance employs for “accuracy” in ICANN’s contracts. Note, this does not preclude any subsequent effort from formalising the definition(s) that should be applied in the context of any existing and/or new accuracy requirements that may be developed”. * Review input received on definition (see page 12 - https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit) * Consider whether in addition to working definition focused on current application, input should be requested on aspirational definitions to identify perceived gap between current definition and aspirational definition * Scoping team input * Confirm next steps 1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System * Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit * Scoping team input * Confirm deadline for submission of questions 1. Confirm action items & next meeting (Thursday 11 November at 14.00 UTC)

1 0

Re: [GNSO-Accuracy-ST] Alt on Nov 11?
by Michael Palage Oct. 29, 2021

Oct. 29, 2021

Hello Sarah, We did get the green light for alternates and a vice-chair yesterday from the GNSO Council as well as an appointment of a GNSO Liaison. I have been informed that the call for alternates will go out next week. So the RrSG should be able to have an alternative in place by then. Best regards, Michael From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> On Behalf Of Sarah Wyld Sent: Friday, October 29, 2021 12:01 PM To: Roger D Carney via GNSO-Accuracy-ST <gnso-accuracy-st(a)icann.org> Subject: [GNSO-Accuracy-ST] Alt on Nov 11? Hi team, I will not be available for our Nov. 11 meeting. I understand that we don’t yet have formal approval to allow Alts in this Scoping Team, so I’d like to know if the group would allow me to assign one or if that’s not yet possible. If it is permitted, then Owen Smigelski will act as my Alt for that meeting. He’s already been observing the team and is up to speed on what’s happening, so he will be well able to contribute meaningfully. Thank you, -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they <mailto:swyld@tucows.com> swyld(a)tucows.com +1.416 535 0123 Ext. 1392

1 0

Re: [GNSO-Accuracy-ST] Accuracy definition updates
by Steve Crocker Oct. 29, 2021

Oct. 29, 2021

I'm in agreement with Sarah's wording. The actual application of syntactic validation and operational validation depends on the specific data elements. For example, there's not much that can be done to validate the syntax of the Name or Organization data elements. We will need specific requirements for each data element. Attached is an attempt at capturing the complete set of collection, validation and sensitivity rules. V0 means no validation, V1 means syntactic validation, V2 is operational validation, and V3 is identity validation. The reason for using ranges, e.g. V1..V3, is to allow registrars to use higher levels of validation if they choose to. If we want to preclude them from doing so, it's easy to specify the precise level of validation they must do, though I doubt that's the policy we actually want. The attachment is a draft. Please do comment or ask questions. Thanks, Steve On Fri, Oct 29, 2021 at 12:09 PM Sarah Wyld <swyld(a)tucows.com> wrote: > Hello team, > > Thank you for the opportunity to consider further updates to the working > definition of registration data accuracy. > > We have reviewed Michael’s suggested text and have some notes/questions > (see below); we’re of course happy to discuss but think that the definition > we proposed, including both the bold text sentence and the explanatory > paragraphs following it, with some changes as noted below/taken from your > proposal, is more clear. > > Notes: > > - Technical contact data may not be provided by the Registrant, but > instead by the Account Holder, and accuracy requirements still apply. > > > - We have taken onboard the changes from Michael’s definition as > prompting update of our proposed definition to include the > Account-Holder-provided data > > > - The additional explanatory text (paragraphs below the bold-text > sentence) is important for explaining syntactical and operational accuracy > and should be included in the definition; this helps make the definition > clear and useful without trying to include all the information in the first > sentence. > > > - Also taken onboard the feedback re clarity of operational accuracy > and made adjustments in the relevant text > > > - Is there a singular definition of Registrar Data Directory Services > (RDDS) data elements? We think “registration data elements” is more clear > and directly relates to the RAA and so we’ve stuck to that language here. > > Our updated working definition, based on current contractual and Consensus > Policy requirements, with the updates from Michael’s proposed changes > included: > > *Accuracy shall be strictly defined as syntactical accuracy of the > registration data elements provided by the Registered Name Holder or > Account Holder as well as the operational accuracy of either the telephone > number or the email address.* > > To be determined to be *syntactically accurate*, the contact must satisfy > all requirements for validity (see Whois Accuracy Program Specification > <https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#who…> > Sections 1b-d). For example, for email addresses all characters must be > permissible, the “@” symbol is required, and there must be characters > before the “@” symbol. > > To be determined to be *operably accurate*, the contact must be operable > as defined in the Whois Accuracy Program Specification > <https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#who…> > Section f. The RAA currently requires validation of syntactical accuracy > and verification of operational accuracy including an affirmative response > from the Registered Name Holder for either email or phone. > > > > Thanks, > > > > > > -- > > *Sarah Wyld*, CIPP/E > > > > Policy & Privacy Manager > > Pronouns: she/they > > > > swyld(a)tucows.com > > +1.416 535 0123 Ext. 1392 > > > > > > *From: *Michael Palage <michael(a)palage.com> > *Sent: *October 27, 2021 4:48 PM > *To: *gnso-accuracy-st(a)icann.org > *Subject: *[GNSO-Accuracy-ST] All Aboard !!! > > > > Hello All, > > > > Per my comments yesterday during our open plenary call, I made very clear > that it is my strong desire to have our work complete by ICANN75. In order > for that to happen, there may be times that I will have to gently nudge in > a neutral fashion people to get things done. In advance of our call next > week, I want to tee up a more in-depth discussion of a working accuracy > definition. > > > > Listed below is current definition that the RrSG has extracted from the > RAA: > > > > Accuracy shall be strictly defined as syntactical accuracy of the > registration data elements provided by the Registered Name Holder as well > as the operational accuracy of either the telephone number or the email > address. > > > > Having read all the documents and listened to all of the > comments/discussion I would like to put on the table for > consideration/discussion the following friendly amendment. > > > > Accuracy encompasses both syntactical accuracy and operational accuracy of > Registration Data Directory Service (RDDS) data elements processed by > Registrars. Syntactical accuracy is imposed on all RDDS data elements > processed by Registrars, whereas operational accuracy is only required of > either email or telephone of RDDS data elements. An additional requirement > of operational accuracy is an affirmative response from the recipient to > the confirmation request. > > > > The basis of these friendly amendments are as follows: > > > > - I am proposing the definition to include syntactical and operational > accuracy for ALL data elements that are processes (including voluntary > ones) not just mandated ones. If a registrar is collecting data elements > they should apply the same standard to all elements, both mandatory and > voluntary. > - I do not believe that the operational aspect of the RrSG definition > properly encapsulated the affirmative response component set forth in the > Whois Accuracy Program Specification. > > > > Any thoughts or comments. > > > > If there are any alternative definitions, I ask that they be provided to > the group via the mailing list 24 hours prior to our next call. > > > > Best regards, > > > > Michael > > > > > > > > > > > > > _______________________________________________ > GNSO-Accuracy-ST mailing list > GNSO-Accuracy-ST(a)icann.org > https://mm.icann.org/mailman/listinfo/gnso-accuracy-st > > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on.

1 0