- Gnso-newgtld-wg-wt3 - lists.icann.org

ICANN62: GNSO Sessions How to Get Organized and Remote Participation Details
by Nathalie Peregrine June 6, 2018

June 6, 2018

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings’ team has put together an updated ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN62 Meeting Schedule<https://62.schedule.icann.org/> GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ> Step 1 – Create a profile and your personalized ICANN62 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you’ve added all your chosen meetings to “My Schedule” go to Export. 1. Importing creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. 2. Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. * For Outlook calendars: http://support.pathable.com/knowledgebase/articles/81449-moving-your-schedu…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> * For Google calendars: http://support.pathable.com/knowledgebase/articles/1313-moving-your-schedul…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> Step 3 All Adobe Connect rooms (which can be found on the session information on the Meeting Schedule<https://62.schedule.icann.org/> and on the GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ>) will provide audio streaming only Adobe Connect room microphones will not be enabled. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ> for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Step 4 Please download the mobile app by searching for “ICANN62” in your app stores. Nathalie Peregrine and Terri Agnew will be onsite in Panama to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<applewebdata://FB60497E-61D8-4FE9-BF9C-EB238191E416/gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

FW: [Gnso-next-gen-rds-lead] FW: URGENT REQUEST - Community Input re Accreditation Model Draft
by Terri Agnew April 2, 2018

April 2, 2018

FYI From: Brian Winterfeldt <Brian(a)Winterfeldt.law <mailto:Brian@Winterfeldt.law> > Date: Monday, April 2, 2018 at 15:07 To: "so-ac-sg-cleaders(a)icann.org <mailto:so-ac-sg-cleaders@icann.org> " <so-ac-sg-cleaders(a)icann.org <mailto:so-ac-sg-cleaders@icann.org> > Cc: "internet(a)winterfeldt.law <mailto:internet@winterfeldt.law> " <internet(a)winterfeldt.law <mailto:internet@winterfeldt.law> > Subject: RE: URGENT REQUEST - Community Input re Accreditation Model Draft Dear ICANN Community Leadership Colleagues: I write to follow up on my prior communication below to provide you with a formal invitation from the IPC and the BC to participate in a community-wide discussion regarding the proposed accreditation and access model for non-public WHOIS data, which was first circulated to the community during ICANN 61. The discussion will take place via ICANN-supported remote participation and/or audio bridge this Friday April 6, 2018 from 1400-1600 UTC. Please find the formal invitation attached with the pertinent participation details. Please distribute the invitation to your respective stakeholders and encourage broad distribution to encourage as much participation as possible in the discussion. Of course, please continue to channel written comments on the accreditation model proposal to <mailto:3amcomments@gmail.com> 3amcomments(a)gmail.com, with a copy to <mailto:internet@winterfeldt.law> internet(a)winterfeldt.law. Thank you very much for your assistance and engagement with respect to this ongoing effort. Best regards, Brian _____ <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d =DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2 x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ&s=XWpe sj5trpbb65DYwAD6KtjhoswZ8rGSMTTB7LZrTRc&e=> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d =DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2 x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ&s=XWpe sj5trpbb65DYwAD6KtjhoswZ8rGSMTTB7LZrTRc&e=> [winterfeldt.law] Brian J. Winterfeldt Principal Winterfeldt IP Group <x-apple-data-detectors://12/1> 1200 17 <x-apple-data-detectors://12/1> th <x-apple-data-detectors://12/1> St NW, <x-apple-data-detectors://12/1> Ste 501 <x-apple-data-detectors://12/1> Washington, DC 20036 <mailto:brian@winterfeldt.law> brian(a)winterfeldt.law +1 202 903 4422 From: Brian Winterfeldt Sent: Thursday, March 29, 2018 7:24 PM To: <mailto:so-ac-sg-cleaders@icann.org> so-ac-sg-cleaders(a)icann.org Cc: <mailto:internet@winterfeldt.law> internet(a)winterfeldt.law Subject: URGENT REQUEST - Community Input re Accreditation Model Draft Importance: High Dear ICANN Community Leadership Colleagues: As a follow-up to my statement on behalf of the IPC during Public Forum II at ICANN 61 in Puerto Rico with Steve DelBianco (from the BC), I am writing to again request your stakeholders' input and collaboration on the proposed Accreditation Model for access to non-public WHOIS data (Version 1.3). Our sincere hope is that this model will be implemented alongside the ICANN-developed Proposed Interim Model for GDPR Compliance. The Accreditation Model can be found here: <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ipconstituency.org_ assets_docs_WHOIS-2520Access-2520Accreditation-2520Process-25201.3-255b1-255 d.pdf&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhp AMF1nu2x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ &s=ZVAEQxooXzT86rLVPfHTxmzU0WSDnjHfiAcifwTNcmk&e=> http://www.ipconstituency.org/assets/docs/WHOIS%20Access%20Accreditation%20P rocess%201.3[1].pdf[ipconstituency.org]. We welcome any questions or feedback on the proposed Accreditation Model, put forward as a strawman to facilitate broader community-wide efforts to develop an accreditation system proposal. We had hoped to convene a community-wide call swiftly after ICANN 61, but the absence of Adobe Connect has made facilitating community discussion and input difficult. However, with the stop-gap solutions being put into place, we hope to convene a call to discuss Accreditation Model development within the next week or so. Developing an Accreditation Model for access to non-public WHOIS data is a critical yet-to-be-developed element of the interim GDPR compliance model, and as Goran noted in his letter to DPAs, the community has achieved consensus that something must be finalized and implemented to assure the appropriate functioning of a gated/tiered/layered access WHOIS system. Again, we hope that the Accreditation Model proposal we are sharing can act as a starting point for the community to make quick progress in this respect. Please send any input on this matter to <mailto:3amcomments@gmail.com> 3amcomments(a)gmail.com as soon as possible, with a copy to <mailto:internet@winterfeldt.law> internet(a)winterfeldt.law. This will help us make sure all the input provided is received and appropriately captured. Again, we hope to convene a community call to facilitate continued discussion on this issue next week, so we would love to receive your feedback ideally before the community session! Thank you for your input and timely engagement in this vital aspect of our ongoing work around GDPR and WHOIS! Best regards, Brian _____ <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d =DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2 x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ&s=XWpe sj5trpbb65DYwAD6KtjhoswZ8rGSMTTB7LZrTRc&e=> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d =DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DJ69mAe-idEhpAMF1nu2 x6c2w3xl7xb5cjS_7sB4h6Y&m=2B8W8Arbme-D4u-B_TRTbN1ysc44yNrgdHI9xYiXehQ&s=XWpe sj5trpbb65DYwAD6KtjhoswZ8rGSMTTB7LZrTRc&e=> [winterfeldt.law] Brian J. Winterfeldt Principal Winterfeldt IP Group <x-apple-data-detectors://12/1> 1200 17 <x-apple-data-detectors://12/1> th <x-apple-data-detectors://12/1> St NW, <x-apple-data-detectors://12/1> Ste 501 <x-apple-data-detectors://12/1> Washington, DC 20036 <mailto:brian@winterfeldt.law> brian(a)winterfeldt.law +1 202 903 4422

1 0

Re: [Gnso-newgtld-wg-wt3] [Gnso-newgtld-wg] [Gnso-newgtld-wg-wt5] [Gnso-newgtld-wg-wt2] [Gnso-newgtld-wg-wt4] Working Group Status and Next Steps
by Aikman-Scalese, Anne March 26, 2018

March 26, 2018

I think Greg Shatan is correct that this report is in fact only a Discussion Draft and not a true Initial Report. Anne E. Aikman-Scalese Of Counsel 520.629.4428 office 520.879.4725 fax AAikman(a)lrrc.com<mailto:AAikman@lrrc.com> _____________________________ [cid:image004.png@01D3C4F6.A6302B90] Lewis Roca Rothgerber Christie LLP One South Church Avenue, Suite 2000 Tucson, Arizona 85701-1611 lrrc.com<http://lrrc.com/> From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Kris Seeburn Sent: Monday, March 26, 2018 5:55 AM To: Vanda Scartezini Cc: gnso-newgtld-wg(a)icann.org; gnso-newgtld-wg-wt1(a)icann.org; gnso-newgtld-wg-wt2(a)icann.org; gnso-newgtld-wg-wt5(a)icann.org; gnso-newgtld-wg-wt4(a)icann.org; Cheryl Langdon-Orr; gnso-newgtld-wg-wt3(a)icann.org Subject: Re: [Gnso-newgtld-wg] [Gnso-newgtld-wg-wt5] [Gnso-newgtld-wg-wt2] [Gnso-newgtld-wg-wt4] Working Group Status and Next Steps Importance: High That works great even better …it should help greatly but we proceed cautiously. We do not need another battle in front of the door. On Mar 26, 2018, at 16:42, Vanda Scartezini <vanda(a)scartezini.org<mailto:vanda@scartezini.org>> wrote: Though I understand points raised by Greg, we could also use the opportunity to make an open survey with open issues to the community to not postponed too much those decisions. Another alternative could be finalizing points that demands no relevant changes, for instance: I do believe that related to “TLDs=city names” we did not have problems with the Application Book as it is. So why not open sliced Applications Books for each area we have no more questions?. To do so we need to make it public as a different reports and get feedback from the community. At least we would show some real progress and may be contribute to the ICANN’s budget. My 2c Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, cj 1004 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos. From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces(a)icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> on behalf of Kris Seeburn <seeburn.k(a)gmail.com<mailto:seeburn.k@gmail.com>> Date: Monday, March 26, 2018 at 04:12 To: "<Jorge.Cancio(a)bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>>" <Jorge.Cancio(a)bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>> Cc: "gnso-newgtld-wg(a)icann.org<mailto:gnso-newgtld-wg@icann.org>" <gnso-newgtld-wg(a)icann.org<mailto:gnso-newgtld-wg@icann.org>>, "Christopher. Wilkinson" <cw(a)christopherwilkinson.eu<mailto:cw@christopherwilkinson.eu>>, "gnso-newgtld-wg-wt1(a)icann.org<mailto:gnso-newgtld-wg-wt1@icann.org>" <gnso-newgtld-wg-wt1(a)icann.org<mailto:gnso-newgtld-wg-wt1@icann.org>>, "gnso-newgtld-wg-wt2(a)icann.org<mailto:gnso-newgtld-wg-wt2@icann.org>" <gnso-newgtld-wg-wt2(a)icann.org<mailto:gnso-newgtld-wg-wt2@icann.org>>, "gnso-newgtld-wg-wt5(a)icann.org<mailto:gnso-newgtld-wg-wt5@icann.org>" <gnso-newgtld-wg-wt5(a)icann.org<mailto:gnso-newgtld-wg-wt5@icann.org>>, "gnso-newgtld-wg-wt4(a)icann.org<mailto:gnso-newgtld-wg-wt4@icann.org>" <gnso-newgtld-wg-wt4(a)icann.org<mailto:gnso-newgtld-wg-wt4@icann.org>>, "gnso-newgtld-wg-wt3(a)icann.org<mailto:gnso-newgtld-wg-wt3@icann.org>" <gnso-newgtld-wg-wt3(a)icann.org<mailto:gnso-newgtld-wg-wt3@icann.org>> Subject: Re: [Gnso-newgtld-wg] [Gnso-newgtld-wg-wt5] [Gnso-newgtld-wg-wt2] [Gnso-newgtld-wg-wt4] Working Group Status and Next Steps makes logical sense….. Kris On Mar 26, 2018, at 10:53, <Jorge.Cancio(a)bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>> <Jorge.Cancio(a)bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>> wrote: Sensible thoughts Regards Jorge Von: Gnso-newgtld-wg-wt2 [mailto:gnso-newgtld-wg-wt2-bounces@icann.org] Im Auftrag von Greg Shatan Gesendet: Samstag, 24. März 2018 05:33 An: Aikman-Scalese, Anne <AAikman(a)lrrc.com<mailto:AAikman@lrrc.com>> Cc: gnso-newgtld-wg(a)icann.org<mailto:gnso-newgtld-wg@icann.org>; cw(a)christopherwilkinson.eu<mailto:cw@christopherwilkinson.eu>; gnso-newgtld-wg-wt1(a)icann.org<mailto:gnso-newgtld-wg-wt1@icann.org>; gnso-newgtld-wg-wt2(a)icann.org<mailto:gnso-newgtld-wg-wt2@icann.org>; Martin Sutton <martin(a)brandregistrygroup.org<mailto:martin@brandregistrygroup.org>>; Javier Rua <javrua(a)gmail.com<mailto:javrua@gmail.com>>; gnso-newgtld-wg-wt5(a)icann.org<mailto:gnso-newgtld-wg-wt5@icann.org>; gnso-newgtld-wg-wt4(a)icann.org<mailto:gnso-newgtld-wg-wt4@icann.org>; Olga Cavalli <olgacavalli(a)gmail.com<mailto:olgacavalli@gmail.com>>; gnso-newgtld-wg-wt3(a)icann.org<mailto:gnso-newgtld-wg-wt3@icann.org> Betreff: Re: [Gnso-newgtld-wg-wt2] [Gnso-newgtld-wg-wt4] [Gnso-newgtld-wg] Working Group Status and Next Steps I would like to raise a potential concern regarding the preliminary report/final report plan for this WG. Unlike most preliminary reports, this one will have a great many open issues and undecided options. As a result, the first time that the community will see the draft recommendations of the WG will be the final report, a role usually played by the preliminary report. That leaves us no room for error or uncertainty in the final report -- we can't bring it out for comment with significant open issues, if this is really intended to be the final report. That will result in a heavy lift to get this into "final" form straight from a fairly unsettled question-filled preliminary report. And what if the comments result in significant changes in the final report -- what happens? Do we have a supplemental final report (not really contemplated by the Charter)? An alternative approach could be to put this report out as a "discussion draft," intended to spur discussion, and then follow that with the preliminary report with our "beta version" and then the final report. There is precedent for working groups making requests to the community for input or comments or information during the pendency of their work. This would allow the preliminary report to play its usual role. Of course, this could raise timing issues. On the other hand, the cynic in me says that this plan to put out an undercooked preliminary report is intended to put timing ahead of fidelity to the PDP process. I'm not advocating form for the sake of form. Rather I think there are good reasons why the preliminary report is intended to be almost-ready-for-prime-time report, and not a sandbox/workshop/open kitchen for the community to join our "fun" and deliberations. (Maybe it's the "home version" of the Working Group....) Failing that, I think we have to brace ourselves for the possibility that we could need a supplemental final draft. I suppose the advantage of that is that we look like we're on schedule for the next year or so.... Just my 2 cents, Greg On Fri, Mar 23, 2018 at 5:00 PM, Aikman-Scalese, Anne <AAikman(a)lrrc.com<mailto:AAikman@lrrc.com>> wrote: It strikes me that to the extent that geo names may be defined more broadly than in the 2012 AGB, it might be a good compromise to establish an Objection process for those wider geo names rather than prohibiting applicants from applying altogether or requiring them to have permission first. The Objection would have to be supported by a substantial portion of the geo community described/implicated by the name, e.g. a particular region, and there would need to be a stated public policy reason for the Objection. Standing might be an issue in some cases and should always be resolved first, along with resolution of any conflicts of interest prior to the commencement of any substantive proceedings. It would be great to see Track 5 come up to speed with Tracks 1 to 4 given that there has been a good deal of discussion over the last several years regarding this arena. It’s hard to see how we can all move forward without getting the geo names issues resolved first. Maybe no one wants another Objection process, but then how can we move toward a resolution when the varying interests are far apart? I would favor a new Objection process to resolve this. At that point, the community may be able to accept some of the wider definitions of geo names (not sure exactly how wide). I would couple this one with the notion that if the applicant loses the Objection, its application fee will be refunded. Just to be clear, the process applicable to the names specified in the 2012 AGB would remain the same. Anne Anne E. Aikman-Scalese Of Counsel 520.629.4428<tel:(520)%20629-4428> office 520.879.4725<tel:(520)%20879-4725> fax AAikman(a)lrrc.com<mailto:AAikman@lrrc.com> _____________________________ <image001.png> Lewis Roca Rothgerber Christie LLP One South Church Avenue, Suite 2000 Tucson, Arizona 85701-1611 lrrc.com<http://lrrc.com/> From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>] On Behalf Of Jeff Neuman Sent: Friday, March 23, 2018 11:09 AM To: cw(a)christopherwilkinson.eu<mailto:cw@christopherwilkinson.eu>; Cheryl Langdon-Orr; Annebeth B. Lange; Martin Sutton; Olga Cavalli; Javier Rua; gnso-newgtld-wg-wt5(a)icann.org<mailto:gnso-newgtld-wg-wt5@icann.org> Cc: gnso-newgtld-wg-wt4(a)icann.org<mailto:gnso-newgtld-wg-wt4@icann.org>; gnso-newgtld-wg-wt1(a)icann.org<mailto:gnso-newgtld-wg-wt1@icann.org>; gnso-newgtld-wg-wt2(a)icann.org<mailto:gnso-newgtld-wg-wt2@icann.org>; gnso-newgtld-wg(a)icann.org<mailto:gnso-newgtld-wg@icann.org>;gnso-newgtld-wg-wt3(a)icann.org<mailto:gnso-newgtld-wg-wt3@icann.org> Subject: Re: [Gnso-newgtld-wg] Working Group Status and Next Steps Thanks Christopher. I do not believe that any of the Work of Work Tracks 1-4 will impinge the activities of Work Track 5. Work Track 5 is limited in scope to only address issues of “geographic names at the top level”. Of course Work Track 5 is working on defining “geographic names” as part of its work. To the extent that Work Track 5 believes that unique processes need to apply to “geographic names” including on business models for geographic names, free speech, predictability, objections, dispute resolution, etc., then Work Track 5 will need to address those and explain why geographic names at the top level need to be treated differently than what is recommended for Work Tracks 1-4. If you have issues about IDNs in general, or any other issues on top level domains in general then those should be addressed in Work Tracks 1-4. In short, I don’t believe there are issues at this point with operating on two different schedules. If, however, a conflict does arise, we will address it at that point in time. Thanks. Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514<tel:(703)%20635-7514> M: +1.202.549.5079<tel:(202)%20549-5079> @Jintlaw From: cw(a)christopherwilkinson.eu<mailto:cw@christopherwilkinson.eu> <cw(a)christopherwilkinson.eu<mailto:cw@christopherwilkinson.eu>> Sent: Friday, March 23, 2018 1:26 PM To: Jeff Neuman <jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com>>; Cheryl Langdon-Orr <langdonorr(a)gmail.com<mailto:langdonorr@gmail.com>>; Annebeth B. Lange <annebeth.lange(a)norid.no<mailto:annebeth.lange@norid.no>>; Martin Sutton <martin(a)brandregistrygroup.org<mailto:martin@brandregistrygroup.org>>; Olga Cavalli <olgacavalli(a)gmail.com<mailto:olgacavalli@gmail.com>>; Javier Rua <javrua(a)gmail.com<mailto:javrua@gmail.com>>; gnso-newgtld-wg-wt5(a)icann.org<mailto:gnso-newgtld-wg-wt5@icann.org> Cc: gnso-newgtld-wg(a)icann.org<mailto:gnso-newgtld-wg@icann.org>; gnso-newgtld-wg-wt1(a)icann.org<mailto:gnso-newgtld-wg-wt1@icann.org>; gnso-newgtld-wg-wt2(a)icann.org<mailto:gnso-newgtld-wg-wt2@icann.org>; gnso-newgtld-wg-wt3(a)icann.org<mailto:gnso-newgtld-wg-wt3@icann.org>; gnso-newgtld-wg-wt4(a)icann.org<mailto:gnso-newgtld-wg-wt4@icann.org> Subject: Re: [Gnso-newgtld-wg] Working Group Status and Next Steps Dear Jeff, Dear PDP friends and colleagues: Thankyou. I understand the interest in moving forward towards a draft of the Initial Report. However, we should all be aware of the interrelationships between WT1-4 and WT5. WT5 should not be constrained by prior understandings reached in WT1-4. In my view, resolution of the issues before WT5 will impinge directly on several related issues, including IDN TLDs, their Business Models, Predictably, freedom of speech and risk analysis. Consequently, notwithstanding the décalage of the WT schedules, I consider that the first draft of an Initial Report should comprise input from the PDP as a whole. Regards Christopher Wilkinson On 23 Mar 2018, at 03:28, Jeff Neuman <jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com>> wrote: Dear All Working Group Members/Observers & Work Tracks 1-4 Members/Observers, You may have noticed that in the last day or so notes have been sent out cancelling certain Work Track and overall Working Group meetings. We wanted to provide the group with an explanation and information on where we are going from here. Over the past year we have been broken out into Work Tracks to get through the voluminous amount of issues (both policy and some implementation) from the 2012 round of new gTLDs. Although there may be a couple of work track meetings over the next month to cover areas that we may not have covered (or may not have covered as in depth as we wanted), during the month of April, we will mostly operate as a full working group to get out an Initial Report. ICANN staff and the Working Group Leaders (including Work Track 1-4 Leaders) are working on taking all of the materials and combining it into one Initial Report. This not only means taking all of the power points and working documents and turning those into prose, but also organizing the report in a manner that flows. As we discussed prior to, and at, ICANN 61, our goal is to organize the Initial Report in more of a chronological order starting with the Overarching Issues, Pre-Application Activities, Application Activities, Objections/public comment, Evaluation, Pre-delegation and Post Delegation. The goal is to have a draft of the substantive elements out to the full working group by the end of the first week of April (some of the more boilerplate oriented language may be filled in subsequently). This will give the full working group at least 3 weeks to review before the target date for publishing the Initial Report for public comment. This will require that we really use e-mail for our comments and also that we will be scheduling 90 minute overall working group calls on April 9th, April 16th, and April 23rd. As a reminder, the Initial Report will be set up in such a way as to describe the issues, provide preliminary recommendations (if we have them), and to present options for possible paths forward. In addition, we will be attempting to provide pointed questions on where we would really like to see public comment. We are NOT going to be issuing Consensus Calls for the recommendations or the content. Rather, we are going to try and have general agreement that the Initial Report is ready to go out for public comment. We will be very clear in the introduction to the report that we have not done consensus calls and the purposes for which we are presenting preliminary recommendations. We will be doing consensus calls for the final report later this year This does not apply for Work Track 5. Work Track 5 is on a different schedule which will be communicated by the 4 Work Track 5 leaders. Please let us know if you have any questions or comments. Best regards, Jeffrey J. Neuman and Cheryl Langdon-Orr Subsequent Procedures PDP Overall Chairs _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg(a)icann.org<mailto:Gnso-newgtld-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. _______________________________________________ Gnso-newgtld-wg-wt4 mailing list Gnso-newgtld-wg-wt4(a)icann.org<mailto:Gnso-newgtld-wg-wt4@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4 _______________________________________________ Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5(a)icann.org<mailto:Gnso-newgtld-wg-wt5@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5 Kris Seeburn seeburn.k(a)gmail.com<mailto:seeburn.k@gmail.com> • www.linkedin.com/in/kseeburn/<http://www.linkedin.com/in/kseeburn/> "Life is a Beach, it all depends at how you look at it" <image001.gif> _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg(a)icann.org<mailto:Gnso-newgtld-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg Kris Seeburn seeburn.k(a)gmail.com<mailto:seeburn.k@gmail.com> * www.linkedin.com/in/kseeburn/<http://www.linkedin.com/in/kseeburn/> "Life is a Beach, it all depends at how you look at it" [cid:image003.gif@01D3C4F6.A6032820] ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

1 0

Re: [Gnso-newgtld-wg-wt3] [Gnso-newgtld-wg-wt4] [Gnso-newgtld-wg] Working Group Status and Next Steps
by Rubens Kuhl March 25, 2018

March 25, 2018

Christopher, The work track 1-4 co-chairs have been noticing the possible inter-relationships throughout the process, and those have been addressed. Even for WT5, the overlap consisting of additional reserved names and some names requiring letters of support/non-objection was also always envisioned... something like a geo objection was not, but that is something that can be harmonised and integrated with the objection process, if's that what WT5 ends up suggesting. That can be even done by WT5 by taking what has already been proposed, like number of panelists and fees bearing, and then defining standing and principles specifically to that process. Even the possibility of adding more contractual requirements, if decided by WT5, can be dealt by with Geo PICs, something that was also foreseen... so I may be optimistic here, but I couldn't think of anything WT5 could come up with that wouldn't be easily integrated into the SubPro output.That doesn't prevent people's imagination to go beyond and actually find something that would be harder to harmonise... but considering the low likelihood, we can deal with it, if it happens, but only if it happens, instead of planning for something that likely won't happen. Rubens > On 25 Mar 2018, at 14:29, lists(a)christopherwilkinson.eu wrote: > > Good afternoon: > > I have considerable empathy with the concerns expressed by Greg here below > I suggest that the current plan underestimates the inter-relationships between the Work Tracks, notably but not exclusively with WT5. > > Regards > > CW > > >> On 24 Mar 2018, at 05:32, Greg Shatan <gregshatanipc(a)gmail.com <mailto:gregshatanipc@gmail.com>> wrote: >> >> I would like to raise a potential concern regarding the preliminary report/final report plan for this WG. Unlike most preliminary reports, this one will have a great many open issues and undecided options. As a result, the first time that the community will see the draft recommendations of the WG will be the final report, a role usually played by the preliminary report. That leaves us no room for error or uncertainty in the final report -- we can't bring it out for comment with significant open issues, if this is really intended to be the final report. That will result in a heavy lift to get this into "final" form straight from a fairly unsettled question-filled preliminary report. And what if the comments result in significant changes in the final report -- what happens? Do we have a supplemental final report (not really contemplated by the Charter)? >> >> An alternative approach could be to put this report out as a "discussion draft," intended to spur discussion, and then follow that with the preliminary report with our "beta version" and then the final report. There is precedent for working groups making requests to the community for input or comments or information during the pendency of their work. This would allow the preliminary report to play its usual role. >> >> Of course, this could raise timing issues. On the other hand, the cynic in me says that this plan to put out an undercooked preliminary report is intended to put timing ahead of fidelity to the PDP process. I'm not advocating form for the sake of form. Rather I think there are good reasons why the preliminary report is intended to be almost-ready-for-prime-time report, and not a sandbox/workshop/open kitchen for the community to join our "fun" and deliberations. (Maybe it's the "home version" of the Working Group....) >> >> Failing that, I think we have to brace ourselves for the possibility that we could need a supplemental final draft. I suppose the advantage of that is that we look like we're on schedule for the next year or so.... >> >> Just my 2 cents, >> >> Greg >> >> On Fri, Mar 23, 2018 at 5:00 PM, Aikman-Scalese, Anne <AAikman(a)lrrc.com <mailto:AAikman@lrrc.com>> wrote: >> It strikes me that to the extent that geo names may be defined more broadly than in the 2012 AGB, it might be a good compromise to establish an Objection process for those wider geo names rather than prohibiting applicants from applying altogether or requiring them to have permission first. The Objection would have to be supported by a substantial portion of the geo community described/implicated by the name, e.g. a particular region, and there would need to be a stated public policy reason for the Objection. Standing might be an issue in some cases and should always be resolved first, along with resolution of any conflicts of interest prior to the commencement of any substantive proceedings. >> >> >> >> It would be great to see Track 5 come up to speed with Tracks 1 to 4 given that there has been a good deal of discussion over the last several years regarding this arena. It’s hard to see how we can all move forward without getting the geo names issues resolved first. Maybe no one wants another Objection process, but then how can we move toward a resolution when the varying interests are far apart? I would favor a new Objection process to resolve this. At that point, the community may be able to accept some of the wider definitions of geo names (not sure exactly how wide). >> >> >> >> I would couple this one with the notion that if the applicant loses the Objection, its application fee will be refunded. Just to be clear, the process applicable to the names specified in the 2012 AGB would remain the same. >> >> >> >> Anne >> >> >> >> Anne E. Aikman-Scalese >> >> Of Counsel >> >> 520.629.4428 <tel:(520)%20629-4428> office >> >> 520.879.4725 <tel:(520)%20879-4725> fax >> >> AAikman(a)lrrc.com <mailto:AAikman@lrrc.com> >> _____________________________ >> >> <image002.png> >> >> Lewis Roca Rothgerber Christie LLP >> >> One South Church Avenue, Suite 2000 >> >> Tucson, Arizona 85701-1611 >> >> lrrc.com <http://lrrc.com/> >> >> >> >> >> From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org <mailto:gnso-newgtld-wg-bounces@icann.org>] On Behalf Of Jeff Neuman >> Sent: Friday, March 23, 2018 11:09 AM >> To: cw(a)christopherwilkinson.eu <mailto:cw@christopherwilkinson.eu>; Cheryl Langdon-Orr; Annebeth B. Lange; Martin Sutton; Olga Cavalli; Javier Rua; gnso-newgtld-wg-wt5(a)icann.org <mailto:gnso-newgtld-wg-wt5@icann.org> >> Cc: gnso-newgtld-wg-wt4(a)icann.org <mailto:gnso-newgtld-wg-wt4@icann.org>; gnso-newgtld-wg-wt1(a)icann.org <mailto:gnso-newgtld-wg-wt1@icann.org>; gnso-newgtld-wg-wt2(a)icann.org <mailto:gnso-newgtld-wg-wt2@icann.org>; gnso-newgtld-wg(a)icann.org <mailto:gnso-newgtld-wg@icann.org>; gnso-newgtld-wg-wt3(a)icann.org <mailto:gnso-newgtld-wg-wt3@icann.org> >> >> Subject: Re: [Gnso-newgtld-wg] Working Group Status and Next Steps >> >> >> >> Thanks Christopher. >> >> >> >> I do not believe that any of the Work of Work Tracks 1-4 will impinge the activities of Work Track 5. Work Track 5 is limited in scope to only address issues of “geographic names at the top level”. Of course Work Track 5 is working on defining “geographic names” as part of its work. >> >> >> >> To the extent that Work Track 5 believes that unique processes need to apply to “geographic names” including on business models for geographic names, free speech, predictability, objections, dispute resolution, etc., then Work Track 5 will need to address those and explain why geographic names at the top level need to be treated differently than what is recommended for Work Tracks 1-4. >> >> >> >> If you have issues about IDNs in general, or any other issues on top level domains in general then those should be addressed in Work Tracks 1-4. >> >> >> >> In short, I don’t believe there are issues at this point with operating on two different schedules. If, however, a conflict does arise, we will address it at that point in time. >> >> Thanks. >> >> >> >> Jeffrey J. Neuman >> >> Senior Vice President |Valideus USA | Com Laude USA >> >> 1751 Pinnacle Drive, Suite 600 >> >> Mclean, VA 22102, United States >> >> E: jeff.neuman(a)valideus.com <mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com <mailto:jeff.neuman@comlaude.com> >> T: +1.703.635.7514 <tel:(703)%20635-7514> >> M: +1.202.549.5079 <tel:(202)%20549-5079> >> @Jintlaw >> >> >> >> From: cw(a)christopherwilkinson.eu <mailto:cw@christopherwilkinson.eu> <cw(a)christopherwilkinson.eu <mailto:cw@christopherwilkinson.eu>> >> Sent: Friday, March 23, 2018 1:26 PM >> To: Jeff Neuman <jeff.neuman(a)comlaude.com <mailto:jeff.neuman@comlaude.com>>; Cheryl Langdon-Orr <langdonorr(a)gmail.com <mailto:langdonorr@gmail.com>>; Annebeth B. Lange <annebeth.lange(a)norid.no <mailto:annebeth.lange@norid.no>>; Martin Sutton <martin(a)brandregistrygroup.org <mailto:martin@brandregistrygroup.org>>; Olga Cavalli <olgacavalli(a)gmail.com <mailto:olgacavalli@gmail.com>>; Javier Rua <javrua(a)gmail.com <mailto:javrua@gmail.com>>; gnso-newgtld-wg-wt5(a)icann.org <mailto:gnso-newgtld-wg-wt5@icann.org> >> Cc: gnso-newgtld-wg(a)icann.org <mailto:gnso-newgtld-wg@icann.org>; gnso-newgtld-wg-wt1(a)icann.org <mailto:gnso-newgtld-wg-wt1@icann.org>; gnso-newgtld-wg-wt2(a)icann.org <mailto:gnso-newgtld-wg-wt2@icann.org>; gnso-newgtld-wg-wt3(a)icann.org <mailto:gnso-newgtld-wg-wt3@icann.org>; gnso-newgtld-wg-wt4(a)icann.org <mailto:gnso-newgtld-wg-wt4@icann.org> >> Subject: Re: [Gnso-newgtld-wg] Working Group Status and Next Steps >> >> >> >> Dear Jeff, Dear PDP friends and colleagues: >> >> >> >> Thankyou. I understand the interest in moving forward towards a draft of the Initial Report. However, we should all be aware of the interrelationships between WT1-4 and WT5. WT5 should not be constrained by prior understandings reached in WT1-4. >> >> >> >> In my view, resolution of the issues before WT5 will impinge directly on several related issues, including IDN TLDs, their Business Models, Predictably, freedom of speech and risk analysis. >> >> >> >> Consequently, notwithstanding the décalage of the WT schedules, I consider that the first draft of an Initial Report should comprise input from the PDP as a whole. >> >> >> >> Regards >> >> >> >> Christopher Wilkinson >> >> >> >> >> >> >> >> On 23 Mar 2018, at 03:28, Jeff Neuman <jeff.neuman(a)comlaude.com <mailto:jeff.neuman@comlaude.com>> wrote: >> >> >> >> Dear All Working Group Members/Observers & Work Tracks 1-4 Members/Observers, >> >> >> >> You may have noticed that in the last day or so notes have been sent out cancelling certain Work Track and overall Working Group meetings. We wanted to provide the group with an explanation and information on where we are going from here. >> >> >> >> Over the past year we have been broken out into Work Tracks to get through the voluminous amount of issues (both policy and some implementation) from the 2012 round of new gTLDs. Although there may be a couple of work track meetings over the next month to cover areas that we may not have covered (or may not have covered as in depth as we wanted), during the month of April, we will mostly operate as a full working group to get out an Initial Report. >> >> >> >> ICANN staff and the Working Group Leaders (including Work Track 1-4 Leaders) are working on taking all of the materials and combining it into one Initial Report. This not only means taking all of the power points and working documents and turning those into prose, but also organizing the report in a manner that flows. As we discussed prior to, and at, ICANN 61, our goal is to organize the Initial Report in more of a chronological order starting with the Overarching Issues, Pre-Application Activities, Application Activities, Objections/public comment, Evaluation, Pre-delegation and Post Delegation. The goal is to have a draft of the substantive elements out to the full working group by the end of the first week of April (some of the more boilerplate oriented language may be filled in subsequently). This will give the full working group at least 3 weeks to review before the target date for publishing the Initial Report for public comment. >> >> >> >> This will require that we really use e-mail for our comments and also that we will be scheduling 90 minute overall working group calls on April 9th, April 16th, and April 23rd. >> >> >> >> As a reminder, the Initial Report will be set up in such a way as to describe the issues, provide preliminary recommendations (if we have them), and to present options for possible paths forward. In addition, we will be attempting to provide pointed questions on where we would really like to see public comment. We are NOT going to be issuing Consensus Calls for the recommendations or the content. Rather, we are going to try and have general agreement that the Initial Report is ready to go out for public comment. We will be very clear in the introduction to the report that we have not done consensus calls and the purposes for which we are presenting preliminary recommendations. We will be doing consensus calls for the final report later this year >> >> >> >> This does not apply for Work Track 5. Work Track 5 is on a different schedule which will be communicated by the 4 Work Track 5 leaders. >> >> >> >> Please let us know if you have any questions or comments. >> >> >> >> Best regards, >> >> >> >> Jeffrey J. Neuman and Cheryl Langdon-Orr >> >> Subsequent Procedures PDP Overall Chairs >> >> >> >> >> >> _______________________________________________ >> Gnso-newgtld-wg mailing list >> Gnso-newgtld-wg(a)icann.org <mailto:Gnso-newgtld-wg@icann.org> >> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg <https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg> >> >> >> >> >> This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. >> >> _______________________________________________ >> Gnso-newgtld-wg-wt4 mailing list >> Gnso-newgtld-wg-wt4(a)icann.org <mailto:Gnso-newgtld-wg-wt4@icann.org> >> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4 <https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4> >> >> _______________________________________________ >> Gnso-newgtld-wg mailing list >> Gnso-newgtld-wg(a)icann.org <mailto:Gnso-newgtld-wg@icann.org> >> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg <https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg> > _______________________________________________ > Gnso-newgtld-wg-wt4 mailing list > Gnso-newgtld-wg-wt4(a)icann.org <mailto:Gnso-newgtld-wg-wt4@icann.org> > https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4 <https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4>

1 0

Re: [Gnso-newgtld-wg-wt3] [Gnso-newgtld-wg] Working Group Status and Next Steps
by Jeff Neuman March 24, 2018

March 24, 2018

Thanks Christopher. I do not believe that any of the Work of Work Tracks 1-4 will impinge the activities of Work Track 5. Work Track 5 is limited in scope to only address issues of “geographic names at the top level”. Of course Work Track 5 is working on defining “geographic names” as part of its work. To the extent that Work Track 5 believes that unique processes need to apply to “geographic names” including on business models for geographic names, free speech, predictability, objections, dispute resolution, etc., then Work Track 5 will need to address those and explain why geographic names at the top level need to be treated differently than what is recommended for Work Tracks 1-4. If you have issues about IDNs in general, or any other issues on top level domains in general then those should be addressed in Work Tracks 1-4. In short, I don’t believe there are issues at this point with operating on two different schedules. If, however, a conflict does arise, we will address it at that point in time. Thanks. Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514 M: +1.202.549.5079 @Jintlaw From: cw(a)christopherwilkinson.eu <cw(a)christopherwilkinson.eu> Sent: Friday, March 23, 2018 1:26 PM To: Jeff Neuman <jeff.neuman(a)comlaude.com>; Cheryl Langdon-Orr <langdonorr(a)gmail.com>; Annebeth B. Lange <annebeth.lange(a)norid.no>; Martin Sutton <martin(a)brandregistrygroup.org>; Olga Cavalli <olgacavalli(a)gmail.com>; Javier Rua <javrua(a)gmail.com>; gnso-newgtld-wg-wt5(a)icann.org Cc: gnso-newgtld-wg(a)icann.org; gnso-newgtld-wg-wt1(a)icann.org; gnso-newgtld-wg-wt2(a)icann.org; gnso-newgtld-wg-wt3(a)icann.org; gnso-newgtld-wg-wt4(a)icann.org Subject: Re: [Gnso-newgtld-wg] Working Group Status and Next Steps Dear Jeff, Dear PDP friends and colleagues: Thankyou. I understand the interest in moving forward towards a draft of the Initial Report. However, we should all be aware of the interrelationships between WT1-4 and WT5. WT5 should not be constrained by prior understandings reached in WT1-4. In my view, resolution of the issues before WT5 will impinge directly on several related issues, including IDN TLDs, their Business Models, Predictably, freedom of speech and risk analysis. Consequently, notwithstanding the décalage of the WT schedules, I consider that the first draft of an Initial Report should comprise input from the PDP as a whole. Regards Christopher Wilkinson On 23 Mar 2018, at 03:28, Jeff Neuman <jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com>> wrote: Dear All Working Group Members/Observers & Work Tracks 1-4 Members/Observers, You may have noticed that in the last day or so notes have been sent out cancelling certain Work Track and overall Working Group meetings. We wanted to provide the group with an explanation and information on where we are going from here. Over the past year we have been broken out into Work Tracks to get through the voluminous amount of issues (both policy and some implementation) from the 2012 round of new gTLDs. Although there may be a couple of work track meetings over the next month to cover areas that we may not have covered (or may not have covered as in depth as we wanted), during the month of April, we will mostly operate as a full working group to get out an Initial Report. ICANN staff and the Working Group Leaders (including Work Track 1-4 Leaders) are working on taking all of the materials and combining it into one Initial Report. This not only means taking all of the power points and working documents and turning those into prose, but also organizing the report in a manner that flows. As we discussed prior to, and at, ICANN 61, our goal is to organize the Initial Report in more of a chronological order starting with the Overarching Issues, Pre-Application Activities, Application Activities, Objections/public comment, Evaluation, Pre-delegation and Post Delegation. The goal is to have a draft of the substantive elements out to the full working group by the end of the first week of April (some of the more boilerplate oriented language may be filled in subsequently). This will give the full working group at least 3 weeks to review before the target date for publishing the Initial Report for public comment. This will require that we really use e-mail for our comments and also that we will be scheduling 90 minute overall working group calls on April 9th, April 16th, and April 23rd. As a reminder, the Initial Report will be set up in such a way as to describe the issues, provide preliminary recommendations (if we have them), and to present options for possible paths forward. In addition, we will be attempting to provide pointed questions on where we would really like to see public comment. We are NOT going to be issuing Consensus Calls for the recommendations or the content. Rather, we are going to try and have general agreement that the Initial Report is ready to go out for public comment. We will be very clear in the introduction to the report that we have not done consensus calls and the purposes for which we are presenting preliminary recommendations. We will be doing consensus calls for the final report later this year This does not apply for Work Track 5. Work Track 5 is on a different schedule which will be communicated by the 4 Work Track 5 leaders. Please let us know if you have any questions or comments. Best regards, Jeffrey J. Neuman and Cheryl Langdon-Orr Subsequent Procedures PDP Overall Chairs _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg(a)icann.org<mailto:Gnso-newgtld-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg

3 2

Working Group Status and Next Steps
by Jeff Neuman March 23, 2018

March 23, 2018

Dear All Working Group Members/Observers & Work Tracks 1-4 Members/Observers, You may have noticed that in the last day or so notes have been sent out cancelling certain Work Track and overall Working Group meetings. We wanted to provide the group with an explanation and information on where we are going from here. Over the past year we have been broken out into Work Tracks to get through the voluminous amount of issues (both policy and some implementation) from the 2012 round of new gTLDs. Although there may be a couple of work track meetings over the next month to cover areas that we may not have covered (or may not have covered as in depth as we wanted), during the month of April, we will mostly operate as a full working group to get out an Initial Report. ICANN staff and the Working Group Leaders (including Work Track 1-4 Leaders) are working on taking all of the materials and combining it into one Initial Report. This not only means taking all of the power points and working documents and turning those into prose, but also organizing the report in a manner that flows. As we discussed prior to, and at, ICANN 61, our goal is to organize the Initial Report in more of a chronological order starting with the Overarching Issues, Pre-Application Activities, Application Activities, Objections/public comment, Evaluation, Pre-delegation and Post Delegation. The goal is to have a draft of the substantive elements out to the full working group by the end of the first week of April (some of the more boilerplate oriented language may be filled in subsequently). This will give the full working group at least 3 weeks to review before the target date for publishing the Initial Report for public comment. This will require that we really use e-mail for our comments and also that we will be scheduling 90 minute overall working group calls on April 9th, April 16th, and April 23rd. As a reminder, the Initial Report will be set up in such a way as to describe the issues, provide preliminary recommendations (if we have them), and to present options for possible paths forward. In addition, we will be attempting to provide pointed questions on where we would really like to see public comment. We are NOT going to be issuing Consensus Calls for the recommendations or the content. Rather, we are going to try and have general agreement that the Initial Report is ready to go out for public comment. We will be very clear in the introduction to the report that we have not done consensus calls and the purposes for which we are presenting preliminary recommendations. We will be doing consensus calls for the final report later this year This does not apply for Work Track 5. Work Track 5 is on a different schedule which will be communicated by the 4 Work Track 5 leaders. Please let us know if you have any questions or comments. Best regards, Jeffrey J. Neuman and Cheryl Langdon-Orr Subsequent Procedures PDP Overall Chairs

2 1

PLEASE READ - NEW SESSION INFORMATION ICANN61
by Terri Agnew March 14, 2018

March 14, 2018

Dear all, Due to security difficulties, (see Goran's blog <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo g_issues-2Dwith-2Dadobe-2Dconnect-2Dat-2Dicann61&d=DwMGaQ&c=FmY1u3PJp6wrcrwl l3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTB s0i1jYiBM_uTSDzgqG&m=fxijpUJu6LmmroHN9tH8OL-ro_yRzrp5RcsF-DsRnHY&s=_RqTDbLxF ZWrmTMt09Hldqs9KQbB7-Kg-pZFjJw0ink&e=> here[icann.org]) the Adobe Connect room facilities will no longer be available to ICANN61 participants. In order to minimize disruption, we have the following steps we encourage you to follow: 1. TO JOIN THE AUDIO * Audio streaming will be available for all open, public meetings. Links can be find on the ICANN61 schedule meeting pages: <https://61.schedule.icann.org/> https://61.schedule.icann.org/ * The audio bridge is available for those who would like to ask questions or comment over the telephone. Dial in details for open GNSO sessions can be found here: <https://community.icann.org/x/3wC8B> https://community.icann.org/x/3wC8B 2. TO ACCESS THE PRESENTATIONS * All presentations and documents which were to be shown in the AC room will be uploaded to the corresponding page on the ICANN61 schedule meeting pages: <https://61.schedule.icann.org/> https://61.schedule.icann.org/ * Presentations and documents will also be circulated via email on demand 3. ASKING QUESTIONS AND COMMENTING IN WRITTEN FORMAT * These will be handed via live management of email comments and questions by the Remote Participation Manager. Please see list of meeting room email addresses here: <https://61.schedule.icann.org/pages/2350> https://61.schedule.icann.org/pages/2350 We apologize for the inconvenience caused. We encourage participants who have not already done so to download the ICANN61 mobile app by searching for "ICANN61" in your app stores. Please do not hesitate to email us at <mailto:gnso-secs@icann.org> gnso-secs(a)icann.org if you need a dial out specifying which meeting you would like to join and your preferred contact number. Kind regards, Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our i <applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses /gnso> nteractive courses and visiting the <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn so.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DgM FAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUh becsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=-d9m4sr16OXloyLjz4TF6npbe51hgE0EH toX1U6WUOA&s=Bw2Uzbh2Pu1X0lObLtbwtN5ZNEP3ECdPAfcqzVvIOYE&e=> GNSO Newcomer pages

1 0

AC Recording, attendance & AC Chat for New gTLD Subsequent Procedures Sub Team Track 3 String Contention, Objections & Disputes call on Tuesday, 27 February 2018 at 20:00 UTC
by Michelle DeSmyter Feb. 28, 2018

Feb. 28, 2018

Dear All, Please find the attendance and Adobe Connect chat of the call attached to this email and the Adobe Connect recording and Mp3 are below for the New gTLD Subsequent Procedures Sub Team - Track 3 - String Contention, Objections & Disputes held on Tuesday, 27 February 2018 at 20:00 UTC for 60 minutes. Mp3: https://audio.icann.org/gnso/gnso-new-gtld-subsequent-track3-27feb18-en.mp3 Adobe Connect recording: https://participate.icann.org/p1r3gvmib4e/ The recordings of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg-wt3 Agenda Wiki page: https://community.icann.org/x/DwWfB Thank you. Kind regards, Michelle

1 0

Notes and Action Items - New gTLD Subsequent Procedures PDP WG Work Track 3 - 27 February 2018
by Emily Barabas Feb. 27, 2018

Feb. 27, 2018

Dear Work Track members, Please find below the action items and discussion notes from today’s call. These high-level notes are designed to help Work Track members navigate through the content of the call and are not a substitute for the recording. The slides, recording, and chat transcript for this meeting will be available at https://community.icann.org/x/DwWfB. Kind regards, Emily ------------------------------------------------------------------------------------ Action Items: Action Item 1: Cancel WT3 meeting tentatively scheduled for 6 March 2018. Notes: 1. Welcome & Introductions 2. SOI Updates - no updates 3. Plenary Update - The last plenary call took place at 3:00 UTC today. The topic was Types of TLDs. 4. String Similarity and String Confusion - Slide 4 - review of recommendation 2 and points of general agreement - From the slide: Going forward allowing plurals and singulars in the same language to move forward is not desirable; Terms need to be intended as plurals and singulars. Thus the TLDs .new and .news would not be considered a plural or singular of the same string; Elimination of the SWORD Algorithm. Chat excerpt: Gg Levine (NABP): Agree strongly with plurals/sigular issue. Kristina Rosette (Amazon Registry): Support the points of general agreement Donna Austin, Neustar: Support the points of general agreement as well. Cheryl Langdon-Orr (CLO): happy for points of General Agreement to be agreed to. - Slide 5 - Review of proposal for string confusion objection Chat excerpt: Rubens Kuhl: The only thing missing is standing. - Comment: we need to provide for an exception for a prior agreement between the parties. We don't want to put people in the position where they have to decide between filing an objection against one applicant and violating a prior agreement with another applicant in the same contention set. - Question: This potentially implicates the Independent Objector. There shouldn't be anything in private applicants' agreements that would prevent the IO from taking action, correct? Chat excerpt: Trang Nguyen: Regarding the string similarity review, ICANN org will provide input on the points of general agreement during the initial report public comment process. Rubens Kuhl: 2012 AGB had no standing for IO to file SCOs. I would like that standing to be added. Kristina Rosette (Amazon Registry): IO doesn't have standing for SCO. Rubens Kuhl: (If IO still exists, of course) Rubens Kuhl: Kristina - Current registries, current applicants and IO would have standing. Kristina Rosette (Amazon Registry): So, to be clear, we're talking about automatic consolidation, right? - WT leadership confirmed that we are talking about automatic consolidation. - What would the group like to see in terms of standing on this objection? Chat excerpt: Rubens Kuhl: Standing needs to be defined. I have a suggestion, others might prefer different standings, but we need to pick one. Rubens Kuhl: Option 1: 2012 AGB (Registries and Applicants) Rubens Kuhl: Option 2: Registries + Applicants + Independent Objector Rubens Kuhl: Option 3: Anyone Rubens Kuhl: My vote: option 2, to add IO. Kristina Rosette (Amazon Registry): If we're going to relax standing (which would be IO and anyone), we need to require an early dismissal mechanism so applicants don't have to spend $ defending ridiculous objections. Cheryl Langdon-Orr (CLO): I see advantage in an early dismissal process regardless,Nye's @Kristina Kristina Rosette (Amazon Registry): Rubens' earlier point is important - can we be reminded what we agreed w/r/t IO? (No point in saying we're giving him standing for SCO if we're eliminating it) Anne Aikman-Scalese (IPC): Option 2 looks fine. Agree there needs to be IO reform - and more than one IO so conflicts of interest can be avoided. - One perspective - the IO should have standing on the string confusion objection. - Slide 6 - Outstanding questions from previous discussions: Is consolidation of objections inherently unfair in anyway? How to proceed if the objector is an existing TLD operator? Are special considerations/guidelines needed? - Question - why was this question raised on slide 6 - "how to proceed if the objector is an existing TLD operator?" - The issue of verified TLDs in a highly regulated sector has come up in previous conversations. If there is an application for a string that is a synonym/exact translation of a highly regulated string in the same sector and that new string is not regulated, one perspective is that there could be a public safety issue. In this view, if the additional string is allowed, it should have the same restrictions. Chat excerpt: Steve Chan: For the last point about appeals on the previous page, is that specific in any way to the string confusion objections? Or is that the appeal mechanism that has been discussed for all objections grounds and evaluation elements? Rubens Kuhl: I don't see any difference for the 2nd bullet from 2012; if existing TLD, application fails. Like .COM and .ECOM. Rubens Kuhl: Restricting in the same sector would be anti-competitive. Rubens Kuhl: Anything in that sector should only have to carry similar PICs. Cheryl Langdon-Orr (CLO): important point Jamie the for raising that Cheryl Langdon-Orr (CLO): might be hard to mandate though Anne Aikman-Scalese (IPC): Agree with GG re regulated strings and eligibility Rubens Kuhl: SCOs in 2012 were actually not expensive. So as long as ICANN keeps it in that range, people will likely won't get "denial of money" attacks. avri doria: Rubens, not all applicants are quite as well set for money. Rubens Kuhl: Avri, I was in the receiving end of one such SCO... and except for the ones in Applicant Support level, I assure you it wouldn't be a problem. Kristina Rosette (Amazon Registry): There's another reason to avoid automatic consolidation - one of the applicants may have trademark rights in the mark that the string matches - required consolidation would likely weaken that applicant's ability to prevail in an SCO Rubens Kuhl: But that could be particular to that dispute resolution provider... if it was carried by ICC, then it could be a million instead of 5 thousand. Anne Aikman-Scalese (IPC): Is ICC the provider for string confusion panels? Rubens Kuhl: Consolidate by default, allow for exception to be request by applicant, perhaps ? Jamie Baxter | dotgay: The problem with letting the provider make a final decision on consolidation is that the loss of income for them will always be an influencer Rubens Kuhl: Anne, not in 2012. For SubPro, who knows ? - In response the the first question, one perspective is that consolidation should happen when possible and should be encouraged. In the view of one WT member, there should be additional guidance about where and how to consolidate, so that costs for applicants are not unnecessarily high. - Concern raised about consolidation of objections - failure of weakness of one applicant's response will have an impact on the other applicants in the contention set. - One perspective - the consolidation should be more focused on the financial aspect than it is on only giving one answer. In some cases in the 2012 round, the same answer was given on multiple objections but they were all paid for independently. - Comment: the objectors should be able to provide a rationale for why the objections should be consolidated. - Comment: Unless we hear how existing TLD operators should be treated differently, there is no merit in keeping that question for further consideration. Chat excerpt: Steve Chan: Would the opposite make sense perhaps? Where an objector can specifically request that their objection not be consolidated? Jamie Baxter | dotgay: @Steve .. i believe the objector should have the option to make a case for consolidation. the final say on consolidation however cannot be left exclusively in the hands of the provider because money has proven to be a nasty inflencer Steve Chan: @Jamie, I was thinking perhaps in addition to your point? Essentially, the objector would have some say whether or not consolidation for their objection takes place. Jamie Baxter | dotgay: @Steve .. i see that as being fair as well. Jamie Baxter | dotgay: @Steve .. what cannot happen however is that the provider declines consolidation because of a single concern from an applicant that financial info may be shared with other applicants in the consolidation when financials had nothing to do with the objection. for the provider to decline consolidation and then assign the same panelist to all cases is a slap in the face and a clear attempt to bill for as much money as possible. 5. Upcoming Meetings - Upcoming call tentatively scheduled for 6 March at 15:00 UTC. The WT would go over material for the Initial Report and prepare for the face-to-face session at ICANN61. - WT members expressed that they may not be able to attend this meeting prior to travel for ICANN61. This meeting will be cancelled. - WG face-to-face session - 10 March 12:00 local time - this session will include material for Work Track 3. - Question - how will the face-to-face meeting be organized? Will this be a good setting to discuss the draft document? - Suggestion - circulate the draft document as early as possible prior to ICANN61. - The leadership team is working on developing draft content and this document will be shared as soon as possible. - For the session in ICANN61 - each Work Track will have a segment of time to cover WT topics. This may be a good opportunity to review draft recommendations and outstanding questions at a high level. 6. AOB - None.

1 0

WT3 Mtg Draft Agenda - 27 February @ 20:00 UTC: String Similarity & String Confusion
by Robin Gross Feb. 26, 2018

Feb. 26, 2018

All, In preparation for our WT3 call tomorrow, Tuesday, 27 February 2018 @ 20:00 UTC, please see below for our proposed discussion agenda. I hope you will join the discussion. Thank you. Best, Robin Gross Meeting Discussion Agenda: 1. Welcome & Introductions 2. SOI Updates 3. Plenary Update 4. String Similarity and String Confusion 5. Upcoming Meetings 6. AOB

1 0