June 2021 - Gnso-epdp-team - lists.icann.org

Question 4
by Alan Greenberg 30 Jun '21

30 Jun '21

This question is confusing in that it includes "... EPDP Team is looking for specific input on having been marked above with an asterisk (*), indicating the options that are under consideration.", but there is nothing above which is marked with a asterisk. That refers to a table in the body of the report." The wording should point to the report with detail as to exactly where to find the asterisked items. Alan

2 1

EPDP 2A Next Steps and Mediated Discussions
by Drazek, Keith 28 Jun '21

28 Jun '21

Dear EPDP Team, I hope you all had a well-deserved break following ICANN71. Thank you again for participating in the outreach session - hopefully it will result in submissions containing new and practical suggestions to help advance the EPDP Team's deliberations as we move into the next phase of our work. As discussed during our last meeting, the leadership team has worked with Melissa Allgood, a certified mediator and member of ICANN's policy team, to further plan for mediated conversations that we hope will prepare the ground for a constructive review of comments and deliberations on the path to a Final Report. I have copied Melissa on this email. As a next step, the gnso-secs team will be reaching out to each group represented on the team to schedule an optional 1:1 with Melissa. As indicated previously, these will be informal (not recorded) conversations that will allow each group to speak freely about possible concerns as well as possible opportunities for compromise and improvements. We know the EPDP process continues to challenge us all, but we hope that this approach will help us look ahead and find common ground, where possible. Following this first round of conversations, Melissa will make suggestions to leadership and the team on whether further conversations, either individually or in limited group settings, may be helpful. As part of the scheduling of the meeting, you will also have an opportunity to indicate whether or not you would like leadership and/or staff support for this effort, i.e., to be present on the call - it is really up to you to decide. We know that this is something new, and may or may not work, but we hope we can rely on everyone's goodwill to at least give it a shot. If you have any further questions, please do not hesitate to reach out to Leadership, Staff and/or Melissa. Best regards, Keith

1 0

Re: [Gnso-epdp-team] Question 5 to the Community - clarification needed
by Alan Greenberg 16 Jun '21

16 Jun '21

I can't recall whether there have been PDP reports that have been revised, but ICANN has revised other published papers before. Sometimes without evening annotating the cover page that it is revised - or changing the URL. Hopefully, if this one is revised (and as I see it, the benefits far outweigh the problems), hopefully the cover page will note the revision and there will be a Revision list somewhere in the document. Alan At 2021-06-15 04:44 PM, Kapin, Laureen via Gnso-epdp-team wrote: >Although what you describe about the rest of the >report is accurate, I still think the omission >of the word âanonymizedâ is simply a mistake >that we should correct and to let it stand >uncorrected will cause confusion. Might you >explain why there is resistance to correcting >this simple error? I suspect that PDPâs have >published corrected versions before. > > >Kind regards, >Laureen Kapin > >Acting Assistant Director >Division of Consumer Response and Operations >Bureau of Consumer Protection >Federal Trade Commission > >From: Marika Konings <marika.konings(a)icann.org> >Sent: Tuesday, June 15, 2021 4:36 PM >To: Becky Burr <becky.burr(a)board.icann.org>; Kapin, Laureen <LKAPIN(a)ftc.gov> >Cc: gnso-epdp-team(a)icann.org >Subject: Re: [Gnso-epdp-team] Question 5 to the >Community - clarification needed > >Please also note that the preceding section in >the Initial Report defines these terms (note, >there are also some footnotes that go with these definitions): > >Â· "Registrant-based email contact", means >âan email for all domains registered by a >unique registrant [sponsored by a given >Registrar] OR [across Registrars], which is >intended to be pseudonymous data when processed by non-contracted parties. >Â· "Registration-based email contact", >means âa separate single use email for each >domain name registered by a unique registrant, >which is intended to be anonymous data when >processed by non-contracted parties. > >We can make sure that a reference to these >definitions is included in the public comment >form to make sure that those that only look at >the form have the appropriate context. > >Best regards, > >Caitlin, Berry and Marika > >From: Gnso-epdp-team ><gnso-epdp-team-bounces(a)icann.org> on behalf of >Becky Burr via Gnso-epdp-team <gnso-epdp-team(a)icann.org> >Reply to: Becky Burr <becky.burr(a)board.icann.org> >Date: Tuesday, 15 June 2021 at 21:59 >To: "Kapin, Laureen" <LKAPIN(a)ftc.gov> >Cc: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> >Subject: Re: [Gnso-epdp-team] Question 5 to the >Community - clarification needed > >do you mean pseudonymized rather than anonymized? > > >On Tue, Jun 15, 2021 at 3:36 PM Kapin, Laureen >via Gnso-epdp-team ><<mailto:gnso-epdp-team@icann.org>gnso-epdp-team(a)icann.org> wrote: >In preparing for tomorrowâs presentation, I >realized that Question 5 to the Community omits >an important word, âanonymized.â We should correct this. > >Here is the Question from the Initial Report: > >EPDP Team Question for Community Input #5 >Does this guidance as written provide sufficient >information and resources to Registrars and >Registry Operators who wish to publish a >registrant- or registration-based email address? >If not, what is missing and why? > >Taken literally, this might leave the impression >that the Recommendation is to publish a standard >email address. In fact, our deliberations >involved the publication of an anonymized (or >more precisely, pseudonymized) email address. I >request that we correct this oversight both so >that our intention is clear and so that the >public comments solicited focus on the real >topic to consider whether to publish some >formm of an anonymized email address. > >I propose that we publish a corrected version of >the Initial Report that inserts the word >âanonymizedâ prior to âregistrant- or >registration-based email addressâ to correct this oversight. > > >Kind regards, >Laureen Kapin > >Acting Assistant Director >Division of Consumer Response and Operations >Bureau of Consumer Protection >Federal Trade Commission > >_______________________________________________ >Gnso-epdp-team mailing list ><mailto:Gnso-epdp-team@icann.org>Gnso-epdp-team(a)icann.org >https://mm.icann.org/mailman/listinfo/gnso-epdp-team >_______________________________________________ >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>https://www.icann.org/privacy/policy) >and the website Terms of Service >(<https://www.icann.org/privacy/tos>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. > >_______________________________________________ >Gnso-epdp-team mailing list >Gnso-epdp-team(a)icann.org >https://mm.icann.org/mailman/listinfo/gnso-epdp-team >_______________________________________________ >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.

4 3

Question 5 to the Community - clarification needed
by Kapin, Laureen 15 Jun '21

15 Jun '21

In preparing for tomorrow's presentation, I realized that Question 5 to the Community omits an important word, "anonymized." We should correct this. Here is the Question from the Initial Report: EPDP Team Question for Community Input #5 Does this guidance as written provide sufficient information and resources to Registrars and Registry Operators who wish to publish a registrant- or registration-based email address? If not, what is missing and why? Taken literally, this might leave the impression that the Recommendation is to publish a standard email address. In fact, our deliberations involved the publication of an anonymized (or more precisely, pseudonymized) email address. I request that we correct this oversight both so that our intention is clear and so that the public comments solicited focus on the real topic to consider - whether to publish some form of an anonymized email address. I propose that we publish a corrected version of the Initial Report that inserts the word "anonymized" prior to "registrant- or registration-based email address" to correct this oversight. Kind regards, Laureen Kapin Acting Assistant Director Division of Consumer Response and Operations Bureau of Consumer Protection Federal Trade Commission

4 4

Re: [Gnso-epdp-team] Question 5 to the Community - clarification needed
by LEWIS-EVANS, Christopher 15 Jun '21

15 Jun '21

OFFICIAL Good spot Laureen and I tripped over the lack of anonymised when presenting to the GAC today but had assumed it was my slide/presentation issue. Becky I think anonymised is better as the returned string/email will be anonymised from the viewpoint of most of the public commenters (as non-controllers) and fits with the rest of the language better. Also the differentiation is better explained in the report rather than making the question long. Thanks Chris From: Gnso-epdp-team [mailto:gnso-epdp-team-bounces@icann.org] On Behalf Of Becky Burr via Gnso-epdp-team Sent: 15 June 2021 20:59 To: Kapin, Laureen Cc: gnso-epdp-team(a)icann.org Subject: Re: [Gnso-epdp-team] Question 5 to the Community - clarification needed do you mean pseudonymized rather than anonymized? On Tue, Jun 15, 2021 at 3:36 PM Kapin, Laureen via Gnso-epdp-team <gnso-epdp-team(a)icann.org<mailto:gnso-epdp-team@icann.org>> wrote: In preparing for tomorrow's presentation, I realized that Question 5 to the Community omits an important word, "anonymized." We should correct this. Here is the Question from the Initial Report: EPDP Team Question for Community Input #5 Does this guidance as written provide sufficient information and resources to Registrars and Registry Operators who wish to publish a registrant- or registration-based email address? If not, what is missing and why? Taken literally, this might leave the impression that the Recommendation is to publish a standard email address. In fact, our deliberations involved the publication of an anonymized (or more precisely, pseudonymized) email address. I request that we correct this oversight both so that our intention is clear and so that the public comments solicited focus on the real topic to consider - whether to publish some form of an anonymized email address. I propose that we publish a corrected version of the Initial Report that inserts the word "anonymized" prior to "registrant- or registration-based email address" to correct this oversight. Kind regards, Laureen Kapin Acting Assistant Director Division of Consumer Response and Operations Bureau of Consumer Protection Federal Trade Commission _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team _______________________________________________ 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. This information is supplied in confidence by the NCA. The NCA is not listed as a Public Authority under the Freedom of Information Act 2000. Any information supplied by, or relating to, the NCA is also subject to an absolute exemption. It may also be subject to exemption under other UK legislation. Onward disclosure may be unlawful, for example, under data protection legislation. Requests for disclosure to the public must be referred to the NCA FOI single point of contact, by email on StatutoryDisclosureTeam(a)nca.gov.uk. All email sent and received by the NCA is scanned and subject to assessment. Messages sent or received by NCA staff are not private and may be the subject of lawful business monitoring. Email may be passed at any time and without notice to an appropriate branch within the NCA, on authority from the Director General or their Deputy for analysis. This email and any files transmitted with it are intended solely for the individual or entity to whom they are addressed. If you have received this message in error, please contact the sender as soon as possible.

1 0

Re: [Gnso-epdp-team] [EXTERNAL] Re: EPDP 2A - Initial Report Status and ICANN 71 Session Coordination
by Mark Svancarek (CELA) 14 Jun '21

14 Jun '21

Resending on list Agree with Brian on all counts: 1. Thanks for the efforts, it helps 2. Concern remains with the original wording, despite the mitigation 3. I don’t think I am anyone’s first choice as a presenter, but given the shortage I am willing to step up. I am most interested in the Natural/Legal topic /marksv From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org<mailto:gnso-epdp-team-bounces@icann.org>> On Behalf Of King, Brian via Gnso-epdp-team Sent: Monday, June 14, 2021 7:32 AM To: Drazek, Keith <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>>; gnso-epdp-team(a)icann.org<mailto:gnso-epdp-team@icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [EXTERNAL] Re: [Gnso-epdp-team] EPDP 2A - Initial Report Status and ICANN 71 Session Coordination Hello Keith, Thank you and thanks to staff for taking these concerns on board. I am truly grateful for your understanding and your efforts to address this. At the risk of sounding ungrateful – though I assure you I truly am grateful – the issue remains with the wording of the Preliminary Recommendation 1 as worded. That said, if you still need volunteers for Wednesday’s session, I would raise my hand to provide an unbiased view in a report to the community on our work. If you think we need to limit this to one speaker per group, I defer to Jan. Thank you for your consideration. Brian King He/Him/His Head of Policy and Advocacy T +1 443 761 3726 Time zone: US Eastern clarivate.com<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.clariv…> | Accelerating innovation Follow us on LinkedIn<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…>, Twitter<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.c…>, Facebook<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> and Instagram<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org<mailto:gnso-epdp-team-bounces@icann.org>> On Behalf Of Drazek, Keith via Gnso-epdp-team Sent: Saturday, June 12, 2021 8:49 PM To: gnso-epdp-team(a)icann.org<mailto:gnso-epdp-team@icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [Gnso-epdp-team] EPDP 2A - Initial Report Status and ICANN 71 Session Coordination Dear EPDP Team, As agreed during our call on Thursday, I’ve consulted with our Staff colleagues on how to best address the concerns expressed around how the text of preliminary recommendation #1, in isolation, might be interpreted by the community. As indicated during the call, I am hesitant to make changes to the Initial Report as this may set an unhelpful precedent. It could also lead to confusion as there would be different versions of the Initial Report circulating. As some of you noted, those interested in commenting on the Initial Report will be focusing on the public comment announcement as well as the public comment input form. As a result, the leadership team and Staff have decided to proceed as follows. * The following sentence will be added to 1) the public comment forum, 2) the public comment input form, and 3) the slides for the EPDP outreach session: “For clarity, preliminary recommendation #1 aims to reflect that there is currently no consensus on whether there should be changes to the phase 1 recommendation. The EPDP Team will consider this question further following the close of the public comment period”. I hope this approach achieves the goal that several of you wanted to achieve, namely, a clear communication to the broader community about how preliminary recommendation #1 should be interpreted. Thank you again for all your comments and suggestions. I do hope that we now can start looking forward to the next phase of our work; focusing on how we can bridge the gaps and difference of opinion that still exist. On a separate note, as we did not get additional volunteers for the ICANN71 outreach session, our Staff colleagues will start reaching out to a number of you for your support. If anyone would like to volunteer, please advise ASAP as the session is on Wednesday. I hope you are able to make the time to assist with this session. Best regards, Keith Confidentiality note: This e-mail may contain confidential information from Clarivate. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this e-mail is strictly prohibited. If you have received this e-mail in error, please delete this e-mail and notify the sender immediately.

1 0

EPDP 2A - Initial Report Status and ICANN 71 Session Coordination
by Drazek, Keith 14 Jun '21

14 Jun '21

Dear EPDP Team, As agreed during our call on Thursday, I've consulted with our Staff colleagues on how to best address the concerns expressed around how the text of preliminary recommendation #1, in isolation, might be interpreted by the community. As indicated during the call, I am hesitant to make changes to the Initial Report as this may set an unhelpful precedent. It could also lead to confusion as there would be different versions of the Initial Report circulating. As some of you noted, those interested in commenting on the Initial Report will be focusing on the public comment announcement as well as the public comment input form. As a result, the leadership team and Staff have decided to proceed as follows. * The following sentence will be added to 1) the public comment forum, 2) the public comment input form, and 3) the slides for the EPDP outreach session: "For clarity, preliminary recommendation #1 aims to reflect that there is currently no consensus on whether there should be changes to the phase 1 recommendation. The EPDP Team will consider this question further following the close of the public comment period". I hope this approach achieves the goal that several of you wanted to achieve, namely, a clear communication to the broader community about how preliminary recommendation #1 should be interpreted. Thank you again for all your comments and suggestions. I do hope that we now can start looking forward to the next phase of our work; focusing on how we can bridge the gaps and difference of opinion that still exist. On a separate note, as we did not get additional volunteers for the ICANN71 outreach session, our Staff colleagues will start reaching out to a number of you for your support. If anyone would like to volunteer, please advise ASAP as the session is on Wednesday. I hope you are able to make the time to assist with this session. Best regards, Keith

2 1

Post Call | GNSO Temp Spec gTLD RD EPDP – Phase 2A | Thursday, 10 June 2021 at 14:00 UTC
by Terri Agnew 10 Jun '21

10 Jun '21

Dear all, All recordings for the GNSO Temp Spec gTLD RD EPDP – Phase 2A call held on Tuesday, 10 June 2021 at 14:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/IALpCQ> (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 As a reminder only members and alternates can join the call as a panelist, observers can join as an attendee to listen. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-epdp-team/> and the main wiki page<https://community.icann.org/x/IYEpBQ>. Thank you. With kind regards, Terri

1 0

Meeting Invitation | GNSO Temp Spec gTLD RD EPDP - Phase 2A call | Thursday, 15 July 2021 at 14:00 UTC
by Terri Agnew 10 Jun '21

10 Jun '21

Dear all, The GNSO Temp Spec gTLD RD EPDP – Phase 2A call is scheduled on Thursday, 15 July 2021 at 14:00 UTC for 90 minutes. Zoom room information: Main Zoom Webinar link: https://icann.zoom.us/j/92181477886?pwd=TlJHTU5EY1d3bUxLV2s3UStPS2MxZz09 Passcode: Z@S07?t=v5 If you are joining via audio only: One tap mobile US: +13126266799,,92181477886#,,,,,,0#,,3121016458# or +13462487799,,92181477886#,,,,,,0#,,3121016458# Webinar ID: 921 8147 7886 Passcode: 3121016458 International numbers available: https://icann.zoom.us/u/acVxz9PmJI [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/acVxz9PmJI__;!!PtGJab4!q…> Members, alternates, 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/SQPpCQ * Check your time zone: https://tinyurl.com/xevu7dxf ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_a_ican…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the EPDP Team is aware at any time who is active. Alternate Assignment – EPDP Phase 2A wiki page<https://community.icann.org/x/h4jzC>. * Members (and alternates replacing members), please select Panelists and Attendees when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates not replacing a member: Please rename your line by adding THREE Zs - (zzz)’before your name and add, in parentheses at the end, (your affiliation - alternate). To rename in Zoom, hover over your name and click ‘rename’. * Alternates (not replacing a member) are not allowed to engage in the chat (apart from private chats) or use any of the other zoom room functionalities such as raising hands or agreeing / disagreeing. 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 | GNSO Temp Spec gTLD RD EPDP - Phase 2A call | Thursday, 10 June 2021 at 14:00 UTC
by Terri Agnew 10 Jun '21

10 Jun '21

**Starting in 15 minutes Meeting Invites for this group will now be sent only to the main mailing list with the ics attachments. Directions for members, alternates and observers are listed below. Dear all, The GNSO Temp Spec gTLD RD EPDP – Phase 2A call is scheduled on Thursday, 10 June 2021 at 14:00 UTC for 90 minutes. Zoom room information: Main Zoom Webinar link: https://icann.zoom.us/j/92181477886?pwd=TlJHTU5EY1d3bUxLV2s3UStPS2MxZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92181477886?pwd=TlJHTU5E…> Passcode: Z@S07?t=v5 If you are joining via audio only: One tap mobile US: +13126266799,,92181477886#,,,,,,0#,,3121016458# or +13462487799,,92181477886#,,,,,,0#,,3121016458# Webinar ID: 921 8147 7886 Passcode: 3121016458 International numbers available: https://icann.zoom.us/u/acVxz9PmJI [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/acVxz9PmJI__;!!PtGJab4!q…> Members, alternates, 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/IALpCQ * Check your time zone: https://tinyurl.com/255722be [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/255722be__;!!PtGJab4!t9HxSzz…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_a_ican…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the EPDP Team is aware at any time who is active. Alternate Assignment – EPDP Phase 2A wiki page<https://community.icann.org/x/h4jzC>. * Members (and alternates replacing members), please select Panelists and Attendees when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates not replacing a member: Please rename your line by adding THREE Zs - (zzz)’before your name and add, in parentheses at the end, (your affiliation - alternate). To rename in Zoom, hover over your name and click ‘rename’. * Alternates (not replacing a member) are not allowed to engage in the chat (apart from private chats) or use any of the other zoom room functionalities such as raising hands or agreeing / disagreeing. 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