February 2022 - GNSO-Accuracy-ST

Re: [GNSO-Accuracy-ST] Registration Data Accuracy Scoping Team meeting
by Lori Schulman Feb. 16, 2022

Feb. 16, 2022

Hello, I can only attend the first ½ hour of tomorrow's meeting. INTA' has it's regular staff meetings every other Thursday. This has never been an ideal time but I am doing my best to attend as many meetings as possible. With kind regards, Lori S. Schulman Senior Director, Internet Policy International Trademark Association (INTA) +1-202-704-0408, Skype: LSSchulman lschulman(a)inta.org<mailto:lschulman@inta.org>, www.inta.org<blocked::http://www.inta.org> -----Original Appointment----- From: ICANN Policy Calendar <PolicyCalendar(a)icann.org> Sent: Thursday, December 16, 2021 10:27 AM To: ICANN Policy Calendar; gnso-accuracy-st(a)icann.org; Michael Palage; Marika Konings; Caitlin Tubergen; Berry Cobb; Berry Cobb; Nathalie Peregrine; Michelle DeSmyter; Devan Reed; Terri Agnew; Board Calendaring; Julie Bisland Subject: Registration Data Accuracy Scoping Team meeting When: Thursday, February 17, 2022 2:00 PM-3:30 PM (UTC) Coordinated Universal Time. Where: 14:00 UTC | https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 Meeting: Registration Data Accuracy Scoping Team meeting Date/time: Recurring weekly on Thursdays at 14:00 UTC for 90 minutes, beginning 06 January 2022 through 24 February 2022 Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ficann.zoo…> 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefens…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [gnso.icann.org]<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefens…> 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefens…> * Visit the 2022 Wiki agenda pages: https://community.icann.org/x/7ID3Cg<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity…> (see dates on the left column) * Check your time zone: https://tinyurl.com/y732rcak<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftinyurl.c…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforms.gle…> 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity…>. 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.

1 0

ICANN73 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland Feb. 11, 2022

Feb. 11, 2022

Dear all, Now is the moment to prepare your schedules for ICANN73! There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to you, to your individual calendars. Please read the below points for a seamless ICANN73! YOU MUST REGISTER FOR ICANN73 INFORMATION * Sign into your ICANN Account, or create an account here [account.icann.org]<https://urldefense.com/v3/__https:/account.icann.org/login__;!!PtGJab4!r0Vr…>. * Register for ICANN73 by clicking in the ICANN SERVICES menu and selecting Meeting Registration and click on the ICANN73 Registration link. Click here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> for detailed instructions. Access the ICANN73 Schedule * ICANN73 schedule: https://73.schedule.icann.org/ [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/__;!!PtGJab4!r0Vro…> For security purposes, participation links will be posted 24-hours prior to the session start times. * ICANN73 GNSO Sessions have been grouped on the ICANN73 GNSO wiki page<https://community.icann.org/x/Fc0GCw>. Create your own schedule: * The ICANN Meeting website allows you to download all GNSO-related meetings to your inbox calendar in one go. For detailed instructions on how to create your personalized ICANN73 schedule and import your schedule to your calendar, click here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>. Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior on the ICANN73 Meeting Schedule [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/__;!!PtGJab4!r0Vro…>. * Visit the Participation Tools page [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/participation-tool…> for links to download the latest version of Zoom for access to the ICANN73 sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/attend__;!!PtGJab4…> for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN73 Meeting Schedule [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/__;!!PtGJab4!r0Vro…> GNSO ICANN73 Wiki Page<https://community.icann.org/x/Fc0GCw> GNSO Session agendas<https://community.icann.org/x/EM0GCw> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Post call | Registration Data Accuracy Scoping Team | Thursday, 10 February 2022
by Terri Agnew Feb. 10, 2022

Feb. 10, 2022

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 10 February 2022 can be found on the agenda wiki page <https://community.icann.org/x/_YD3Cg> (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 * 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

Notes and action items - RDA Scoping Team Meeting #17 - 10 Feb 2022
by Caitlin Tubergen Feb. 10, 2022

Feb. 10, 2022

Dear RDA Scoping Team Members, Please find below the notes and action items from today’s meeting. The next RDA Scoping Team meeting will be Thursday, 17 February at 14:00 UTC. Best regards, Marika, Berry, and Caitlin -- Action Items 1. Scoping Team to review the Support Staff list of data sources for accuracy<https://mm.icann.org/pipermail/gnso-accuracy-st/2022-February/000253.html> and confirm that nothing is missing. 2. Scoping Team to work asynchronously via the email list to further discuss the definition of accuracy and what changes might be necessary. (For current working definition/construct, please refer to p. 12 of this Google Doc<https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit>.) 3. Still outstanding for BC, GAC, ISPCP, and SSAC reps: Scoping Team members who have not yet completed the assignment to consider what is needed and from whom to obtain information identified as necessary to measure whether current goals are met. Additionally, scoping team members to begin identifying specific ways in which measurement can be undertaken. (see page 25 at https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p… [docs.google.com] For groups that referenced ARS, please consider ICANN org’s recent memo in your response: https://mm.icann.org/pipermail/gnso-accuracy-st/2022-January/000236.html. Registration Data Accuracy Scoping Team – Meeting #17 Thursday 10 February at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Continuing the work of last week * Many stakeholder groups have completed their homework, still waiting BC, GAC, ISPCP, SSAC * If we finish this part of our work early today, we will discuss the potential of gathering UDRP decision data that has been discussed on the list 1. Measurement of accuracy (60 minutes) * Review of existing data sources - role in existing current situation & identifying possible gaps (seehttps://mm.icann.org/pipermail/gnso-accuracy-st/2022-February/000253.html) * Further to Support Staff’s action item, Support Staff has compiled a separate list of data sources that have been referenced. * Many (if not all) were included as part of the briefing materials; however, now all are included in a dedicated document. * Scoping Team to please review and ensure that this is complete. * Review input received on google doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…>, see page 25 - How and by whom can it be measured whether current goal(s) of existing accuracy requirements are met? * RySG: This assignment was a challenge because Ry Reps are still struggling against which standard to measure accuracy against – there is no current agreed-upon definition. * There are different ways to ask Rrs to report on their accuracy rates, such as ask Rrs to track email bounces from WDRP notices. One challenge here is that we, as an accuracy scoping team, do not have a way of compelling registrars to provide this data. * Could have a third-party audit of existing data, but DPAs would need to be in place. While this is possible, there are challenges with cross-jurisdictional transfers of data. * With respect to third-party audits and the issue of DPAs, instead of doing a random sampling, would it be better to focus on domains that show up in OCTO reports – that may, on its face, have a higher chance of passing the legitimate interest test * Disagree – rather than looking at names that are so-called bad is not a comprehensive look at the ecosystem. Important to have a holistic look into the DNS and not just zero in on alleged bad actors. * Doing scoping on what has already been identified as bad isn’t going to get us very far. Think that there could be a carefully-crafted and narrow DPA exclusively for this purpose. * There is a DPA between registries and registrars. This should be doable. * The purposes have to be defined narrowly and the DPA needs to be crafted carefully – hard to say if this would be OK without seeing the DPA. Any transfer of data across borders (as seen in recent Google analytics decision) leaves some question as to how this could be organized. A third party should probably be used, rather than ICANN doing it. Ultimately, this will not be the easiest task. * The group has been looking at data on the number of complaints ICANN gets. There is a difference of opinion on why that number has dropped between pre-GDPR and post-GDPR. As we’re looking at easy data sets to get to, if we are looking at illegal activity, that may give us a heightened legitimacy for access to the data. * What is the standard for measurement – unclear if this is about how to measure something or what thresholds exist for how good something is or how bad something is. There are basically two kinds of numbers that stick out: (1) number of domains viewed as abusive vs. (2) percentage of registrations per registry that are being used for malicious purposes – these two are different numbers. For new gTLDs, the set of registrations is relatively small, but the percentage for some is relatively high, rather than .com – which has a large number of abusive domains but a small percentage overall. Need to be careful about where we focus our attention. The drop in complaints from ICANN Compliance does not translate into a positive signal that accuracy rates have changed for the better. * This discussion started way back when discussing voluntary contributions from registrars since ICANN cannot compel registrars to provide data. A DPA that would need to be voluntarily signed by certain registrars has very little merit. It’s unlikely to be signed by bad actors. If there is no benefit to a registrar, why would they spend money doing this? ICANN could certainly decide to do audits of various sorts. Many companies have set up data protection authorities in certain jurisdictions to avoid cross-border data flow. In terms of audits of just domains that have shown abuse -this is a fine idea. Why is it that we want data? No need to contact all 200,000,000 people but may want to contact the ones that have some relevance. Targeting may not give us a holistic picture, but it could give us a view into accuracy vs. registrant data. It may be accurate as data, but not contact information for that registrant. * The scope of this group is not abusive domain names, but looking at domain names involved in illegal activity could the safest and legally viable data sampling to do. * Do not see how abuse stats b/w TLDs relate to accuracy. Abuse is not what we are looking at regardless of what the domain name is used for. New gTLDs are, in general, more regulated than legacy TLDs. If new gTLDs have high abuse whereas .com has a moderate number of abusive domain names, that leads to the conclusion that more regulation does not lead to less abuse, or, the more regulation = greater abuse. * The two most abused gTLDs, 2 account for over 40% of abuse * If it seems like we need to get more data, this is perhaps a way to do this. Suggest that Rys and Rrs put their heads together and see what data we have, who could be the aggregator of data and come up with something that could be a light scope. * It looks like only 3% of abuse deals with trademark infringement – this deals with specific automated detection system, and the detection system excludes malicious abuse. What does compromised mean? Does that go beyond malicious? * CPs, during ICANN 73, will have a session about abuse and distinguish if it is about maliciously registered domain names or compromised domain names. * Appreciate that this group of Rrs and Rys would go back and think about what could be done, but it’s the age-old problem – the problem is usually not with the Rrs and Rys that participate in ICANN – especially not the registrars that are represented here. If all Rrs do not participate, the data would be skewed. * Just because something is abusive is very prejudicial – this makes the assumption that inaccurate data means abusive data – this should be looked at more holistically. * IPC: Shares opinions submitted by others such as ALAC – concerned about time to determine whether goals are met. In terms of AFAV, this would be helpful if this were enforced. GAC used the definition for domain name registration data for the ARS – this has been suspended, but its definition did also include identity (not just operability and syntax). Identity verification should be considered. ICANN org should be the entity that audits compliance. There were previous references to the NORC group that was the prototype for ARS and it included validation and they private and public sector validation experts. Perhaps we could use these experts again. * When it comes to how to measure accuracy, there is a suggestion to have ICANN compliance do an audit that accuracy measures are being followed. Is that correct? * Thought validation or verification experts from the public and private sector might be useful to assist ICANN in this exercise. * ALAC – This is a different question – confused by how the scoping team is supposed to be running studies – if it is, the scoping team is short on time. * If there are recommendations on what we are supposed to do, we can adjust the timeline accordingly. * Group seems to be conflating whether people are adhering to the RAA and whether information is accurate. The RAA is very targeted and only looks at accuracy for some fields for new and updated names. We are not in a position to compel registrars to do a full audit of their own data. If there is a belief that this is out of scope and that ICANN does not have the right to do it, we need to get clarity on that. * Most domain names fell under the 2013 RAA due because they were transferred or deleted. Only a small subset of domain names remained under the grandfathered rules – also names registered a long time ago usually do not present an accuracy issue * If the group comes up with a mechanism for measuring accuracy, it is important to get the results of this to get to the other parts of the assignment * What would this look like from a process standpoint? * Procedurally, once this group has identified the guardrails or scope of any type of study, this would need to be documented and presented to the GNSO Council first, and this would need to be approved by the Council – it would then be submitted to the Board or Org (this presumes that it would be a sizeable resource). Ultimately, that request would be evaluated by the Board and Org to determine feasibility and funding. As it stands right now, this would be an unplanned expense – the planning and financing team would have to determine where the funding would come from. This may not be the exact process; this is how the process worked for EPDP Phase 1 and 2. * The third charge to the scoping team – undertake an analysis based on data from assignment 2 (the measurement of accuracy). It’s critical to have good data that we can take concrete and actionable steps against. * It could take over six months if we commission a study like the NORC study, assuming it’s all possible and viable to do that, this would be a very significant amount of time. In terms of what RDS review team found, understanding is that there are still significant domain names that are not treated as new and not subject to 2013 RAA requirements. * If we must pause and wait for results of a study in order to get important data, that would be worth it. * Have heard the argument that we need data to provide concrete and helpful recommendations. One option would be to stall work. One problem is to check the magnitude of the problem. The fact that there is an inability to check whether there is an accuracy issue – for that, we do not need data – we need to think of ways to tackle this issue. * Group could work asynchronously on the definitional issue on the mailing list. * Confirm next steps 1. Confirm action items & next meeting (Thursday 17 February at 14.00 UTC)

1 0

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 17 February 2022 at 14:00 UTC
by Terri Agnew Feb. 10, 2022

Feb. 10, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 17 February 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<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 <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 <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/_4D3Cg * Check your time zone: https://tinyurl.com/2p82fdw6 ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select 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://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> 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

**Starting in 15 minutes | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 10 February 2022 at 14:00 UTC
by Terri Agnew Feb. 10, 2022

Feb. 10, 2022

**Starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 10 February 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<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 <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 <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/_YD3Cg * Check your time zone: https://tinyurl.com/mv9h95yv [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mv9h95yv__;!!PtGJab4!oBJfxsm…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select 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://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> 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

UDRP Data Points wrt Accuracy
by Michael Palage Feb. 9, 2022

Feb. 9, 2022

Hello All, So I reached out to Brian Beckham from WIPO in response to this thread yesterday. Listed below is his email response. I also spoke with Brian today about how we might go about involving other UDRP providers in this outreach. If we complete our assignments tomorrow we can add this to the agenda. Best regards, Michael <EMAIL RESPONSE FROM BRIAN BECKHAM (WIPO)> Thanks Michael, Do let me know if/how we can assist. An initial observation, which you and the WG will already know, is that while perhaps anecdotally useful, this will yield incomplete data and obviously the search terms should be creatively widened (yet will inevitably not be fully comprehensive given that if a panel chooses to record such fact in the decision, it could do so in different ways (or even in different places: e.g., in the procedural history vs the bad faith analysis) and using different terms). If only to state the obvious, information can be “accurate” in the sense that it provides an entry into the required data fields, but still inaccurate in the sense of authenticity vis-à-vis an actual registrant. These types of scenarios in particular cause unnecessary time (giving room for cyberflight, or prolonged illegitimate activity) and expense in the UDRP cases, and even potential due process issues (even if they would be occasioned by registrants). While this goes beyond UDRP cases (as will your efforts), I wonder if your WG has considered the utility of cross-field challenge/matching (which may not be the technical term) such as is employed by postal and shipping companies around the world (i.e., you cannot provide a 4-digit zip code in Switzerland but list a US or UK address). Mindful that these conversations and policies need to look at scale and potential ripple effects/unintended consequences, I would also caution, as Roger seems to allude to below, that there may indeed be broader policy considerations than a mere one-to-one correlation between “extent” and “impact” can reasonably be expected to reveal. While a slightly different topic (P/P), the following may be of interest: https://circleid.com/posts/20201104-icann-meeting-concluded-with-no-action-… Thanks, and again, do let me know if we can assist further. Brian

1 0

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 10 February 2022 at 14:00 UTC
by Julie Bisland Feb. 9, 2022

Feb. 9, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 10 February 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<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 <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 <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/_YD3Cg * Check your time zone: https://tinyurl.com/mv9h95yv [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mv9h95yv__;!!PtGJab4!oBJfxsm…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select 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://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> 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

Message from the Chair
by Michael Palage Feb. 9, 2022

Feb. 9, 2022

Hello All, I would like to remind all the stakeholder groups to please complete their assignments by this Thursday’s call. As Chair I have tried to be sensitive to the Zoom burnout that is impacting most of the ICANN community. However, we are falling behind and that is a concern, especially after reading Kevin Murphy’s recent article <https://domainincite.com/27434-icann-hasnt-implemented-a-policy-since-2016> on the lack of policy implementation within ICANN over the past 6 years. In fact, I produced the following image below which I mocked up and now have as my desktop background. While I am not opposed to taking time to get to where we need to be, I am concerned that some groups have not been pulling their full weight. As noted above, I know that the two plus years with no face to face meetings is taking its toll, but we need to plow forward with our work. If we continue to fall behind in our work, I think we need to access whether we make the recommendation to Council to suspend/terminate this working group until a later time. This is not my preference as I personally believe that there is a problem that needs to be addressed based on my own professional and personal experience. I also believe that the numerous references to “accuracy” in the recent EU’s DNS Abuse Report is further evidence that there is work to be done in this area. I appreciate the time restrains that this Working Group and the broader ICANN multi-stakeholder model (MSM) places on everyone’s professional and personal lives. I am especially sensitive to those volunteers that are not employees of an ICANN contracting party. For these volunteers, the responsibilities of this Working Group go well above and beyond your other professional responsibilities. My concern, however, is that there has been a steady and continuing decline in the number of volunteers within the ICANN community willing to do the heavy MSM lifting. Unfortunately the likely outcome of this trajectory is an ICANN that looks more like a trade association, or worse a cartel. This is not a potential outcome that I find acceptable based upon the last twenty three years of trying to make this ICANN MSM experiment work. Looking forward to a productive call on Thursday. Best regards, Michael

2 1

UDRP review
by Roger D Carney Feb. 8, 2022

Feb. 8, 2022

Good Afternoon, Several times during our deliberations, the issue of registration data accuracy and UDRPs has been raised, with Becky even suggesting an X/Y summary in chat last week. Although some anecdotes were provided, the CPH would like to propose a review of UDRP decisions to determine the extent of registration data inaccuracies in UDRPs, as well as the impact of those inaccuracies on UDRP proceedings. We believe that obtaining comprehensive data regarding the issue should help guide our deliberations. Two UDRP providers (WIPO and the Forum) have easily accessible (and searchable) Decisions. WIPO has almost 49,000 Decisions (of which 764 include the word “inaccurate”), and the Forum has almost 32,000 Decisions (of which 188 include the work “inaccurate”). The other providers do not have easily accessible online databases (or limited search capabilities). The CPH proposes the Scoping Team create a small team to determine how to gather and then review the data. There are several methods to do so, and we think this is something that is well suited to a small team. Thanks Roger

3 2