April 2019 - Gnso-newgtld-wg

Re: [Gnso-newgtld-wg] Proposed agenda - New gTLD Subsequent Procedures PDP WG - 8 October 2018 at 15:00 UTC
by Jamie Baxter 04 Jun '19

04 Jun '19

3 2

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 30 April 2019
by Julie Hedlund 01 May '19

01 May '19

Dear Working Group members, Please see below the notes from the meeting today, 30 April 2019. These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted at: https://community.icann.org/display/NGSPP/2019-04-30+New+gTLD+Subsequent+Pr…. Please also see the referenced document at: https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsX…. Kind regards, Julie Julie Hedlund, Policy Director Notes and Action Items: Action Items: -- Staff will check on the ICANN Board response to the GAC advice in the Helsinki Communique’ on new gTLDs. -- WG to come up with a different name for the “standing IRT”. Maybe “Post Application Advisory Team”. Notes: 1. Updates to Statements of Interest: No updates provided. 2. Review of Summary Documents – (see: https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsX…) 2.2.1 Continuing Subsequent Procedures Policy Goals / What the WG is Seeking to Accomplish -- First bullet: replace “rounds” with “procedures”. 2.2.1.c.1: The Working Group recommends no changes to the existing policy calling for subsequent application rounds introduced in an ongoing, orderly, timely and predictable manner. -- Support from most commenters New Ideas/Concepts for Deliberations: -- GAC Advice and BC: Support for new rounds but no rounds started until reviews (CCT-RT) are complete. Need to do a cost-benefit analysis before starting new round. -- WG is taking into consideration the CCT-RT recommendations. Discussion: -- Policy does not have a demand component. -- Action Item: Board response to GAC Advice in the Helskinki Communique’. -- Note that the CCT-RT did have an economic study done by the Analysis Group, although perhaps not a full cost-benefit analysis. -- Concerns with maintaining the current policy unless there are objections. -- Unless there is a consensus on changing precedent we should stay on the same path. -- Can build on what we have learned, but hard to do analysis on what people might want. -- If the WG wants to request for an assessment to be done that will have to be approved by the Council. -- Calling for rounds introduced in an ongoing orderly timely and predictable manner support came from pretty much every group that responded in public comments to the Initial Report. -- We have some qualifications from the GAC. 2.2.1.e.1: The 2007 Final Report noted that success metrics would be developed around the New gTLD Program. What are some specific metrics that the program should be measured against? -- Support from most commenters. New Ideas/Concepts for Deliberations: ALAC, BRG, BC, RySG – New Ideas Discussion: -- Good proposals for different types of metrics. -- Need to define what we mean by success; CCT-RT referred that issue to the SubPro WG. -- Questions and issues in the CCT-RT could put some of these issues to rest. -- This WG could come up with a half dozen categories (elements of the program) and develop definitions of success for those – or develop targets, which is a less loaded word. -- Good conversation to continue on email. -- You could have a high-level structure from the 2012 round (to foster diversity, encourage competition, and enhance the utility of the DNS), then create specific targets within that structure within that framework. 2.2.2 Predictability -- Support from most commenters -- BC/RySG/IPC/ALAC (in response to e.1): New Idea - The Standing IRT must be representative of the community, but must also allow for the appointment of experts where needed. New Ideas/Concepts for Deliberations -- ICANN Org: Concerns/New Ideas Discussion: -- Can things in the model be improved so that you can support it? If not, what takes its place? -- Don’t think it’s in our authority to replace the GNSO policy process. -- We're not changing any of the policies or processes that have been established. -- Changes to policies after the launch need to go through the GNSO policy process; the predictability framework is for issues that come up outside of that process and guidance to the standing IRT. In the report we called it a standing IRT, but that seems to be confusing so we should change the name. Could call it a “gateway” to decide what is policy and what is not, and only looking at non-policy issues. -- Need to be more conscious of the need for predictability for third party interests. We use the term “affected parties” for that reason. -- WG needs to come up with a different name for the “standing IRT”. Maybe a Post Application Advisory Team.

7 9

Recordings, attendance & Zoom chat / New gTLD Subsequent Procedures Working Group call on Tuesday, 30 April 2019 at 03:00 UTC.
by Michelle DeSmyter 30 Apr '19

30 Apr '19

Dear All, Please find the attendance and Zoom chat attached, and the MP3 and Zoom recording below for the New gTLD Subsequent Procedures Working Group call held on Tuesday, 30 April 2019 at 03:00 UTC. Attendance of the call is also posted on the agenda wiki page: https://community.icann.org/x/9RVIBg Mp3: https://audio.icann.org/gnso/gnso-new-gtld-subsequent-30apr19-en.mp3 Zoom Recording: https://icann.zoom.us/recording/share/HNQYCpVjGS4XnuWapz8fvmgwO_JND3O8IQdZb… The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg/ Main wiki page for the working group: https://community.icann.org/x/RgV1Aw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you. Kind regards, Michelle

1 0

Proposed Agenda - New gTLD Subsequent Procedures PDP WG meeting - Tuesday, 30 April 2019 at 03:00 UTC
by Steve Chan 29 Apr '19

29 Apr '19

Dear WG members, Please find below the proposed agenda for the upcoming call on Tuesday, 30 April 2019 at 03:00 UTC for 90 minutes: Draft Agenda: Welcome/Review of the Agenda/Updates to Statements of Interest (SOIs) Review of Summary Documents – (see: https://docs.google.com/document/d/1R4zXTH3hIgfbqoxyqsSp19Bl6J96NNeV7oCgxsX…) 2.2.1 Continuing Subsequent Procedures 2.2.2 Predictability / 2.2.2.2 Clarity of Application Process AOB Note, in relation to agenda item 2, WG leadership and staff have tried to prepare summary documents for each topic that seeks to help you review some of the background material, consider a high-level summary of what we believe the WG is seeking to accomplish for the topic, a high-level summary of public comment received, and finally, a sort of catch all at the end of each section (e.g., follow-up, parking lot, next steps). If you need a dial out or would like to send an apology for this call, please email gnso-secs(a)icann.org. Best, Steve Steven Chan  Policy Director, GNSO Support ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Mobile: +1.310.339.4410 Office Telephone: +1.310.301.5800 Office Fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

3 3

FW: AFRALO-AFRICANN statement - ICANN 64 Kobe, Japan
by Jeff Neuman 24 Apr '19

24 Apr '19

All, We received the following correspondence today and wanted to make sure that the Working Group was made aware of the statement from AFRALO-AFRICANN. This is being provided for informational purposes and will be incorporated into our discussions as applicable. Best regards, Jeff Neuman Senior Vice President Com Laude | Valideus 1751 Pinnacle Drive Suite 600, McLean VA 22102, USA M: +1.202.549.5079 D: +1.703.635.7514 E: jeff.neuman(a)comlaude.com www.comlaude.com<http://www.comlaude.com/> Liability cannot be accepted for statements made which are clearly the sender’s own and not made on behalf of Com Laude USA or Valideus USA. This message is intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. Do not use, copy or disclose the information contained in this message or in any attachment.Com Laude USA and Valideus are trading names of Consonum, Inc. From: Silvia Vivanco <silvia.vivanco(a)icann.org> Sent: Monday, April 8, 2019 8:59 PM To: Jeff Neuman <jeff.neuman(a)comlaude.com>; Jeff Neuman <jeff.neuman(a)valideus.com>; langdonorr(a)gmail.com Cc: ICANN At-Large Staff <staff(a)atlarge.icann.org>; Mohamed Bashir <mbashir(a)mbash.net>; Tijani BEN JEMAA <tijani.benjemaa(a)fmai.org.tn>; Sarah Kiden <skiden(a)gmail.com>; Seun Ojedeji <seun.ojedeji(a)gmail.com>; Fatimata com> <fsylla(a)gmail.com> Subject: AFRALO-AFRICANN statement - ICANN 64 Kobe, Japan Dear co-chairs of the New gTLD Subsequent Procedures PDP WG, On behalf of AFRALO’s Chair Mohamed El Bashir, kindly find attached the AFRALO/AFRICANN Statement “New gTLD Subsequent Procedure: Proposal of Neustar regarding the upcoming round of New gTLDs" which was discussed and approved at the ICANN 64 meeting in Kobe, Japan. Please be so kind to find attached the statement for your consideration. Thank you! Kind regards, Silvia Vivanco Senior Manager, At Large Regional Affairs Internet Corporation for Assigned Names and Numbers (ICANN) Tel: + 51-997510935

11 20

El Pais article on .amazon. Fwd: [Gnso-newgtld-wg-wt5] Reminder - Proposed Agenda - Work Track 5 - 24 April 2019 at 14:00 UTC
by lists＠christopherwilkinson.eu 24 Apr '19

24 Apr '19

FYI. CW > Begin forwarded message: > > From: "lists(a)christopherwilkinson.eu" <lists(a)christopherwilkinson.eu> > Subject: Re: [Gnso-newgtld-wg-wt5] Reminder - Proposed Agenda - Work Track 5 - 24 April 2019 at 14:00 UTC > Date: 24 April 2019 at 15:43:45 GMT+2 > To: "gnso-newgtld-wg-wt5(a)icann.org" <gnso-newgtld-wg-wt5(a)icann.org> > Cc: Julie Hedlund <julie.hedlund(a)icann.org> > > > Good afternoon, and with a view to our call at 14.0’0 UTC: > > https://elpais.com/sociedad/2019/04/23/actualidad/1556046616_957867.html <https://elpais.com/sociedad/2019/04/23/actualidad/1556046616_957867.html> > > Full page article in El Pais, 24 April on .amazon > > Could Staff please post an EN translation. > > Regards > > CW > >> On 23 Apr 2019, at 21:10, Julie Hedlund <julie.hedlund(a)icann.org <mailto:julie.hedlund@icann.org>> wrote: >> >> Dear all, >> >> Please find below the proposed agenda for the Work Track 5 call taking place Wednesday, 24 April 2019 at 14:00 UTC for 60 mins. >> >> Welcome/Agenda Review/SOI Updates >> Continue Review of Public Comments: >> Questions for Community Input – start at Question e10, line 181 >> Options/Proposals: country and territory names (see deliberations section f.2.2.2 for context) >> AOB >> >> For agenda item 2, please review the Google document at:https://docs.google.com/spreadsheets/d/1WKSC_pPBviCnbHxW171ZIp4CzuhQXRCV… [docs.google.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spread…>. >> >> If you need a dial out or would like to send an apology for this call, please email gnso-secs(a)icann.org <mailto:gnso-secs@icann.org>. >> >> Kind regards, >> Julie >> Julie Hedlund, Policy Director >> >> _______________________________________________ >> 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 <https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5>

1 0

Recordings, attendance & Chat / New gTLD Subsequent Procedures Working Group call / Monday, 22 April 2019 at 20:00 UTC
by Julie Bisland 23 Apr '19

23 Apr '19

Dear All, Please find the attendance and Zoom chat attached, and the MP3 and Zoom recording below for the New gTLD Subsequent Procedures Working Group call held on Monday, 22 April 2019 at 20:00 UTC. Attendance of the call is also posted on the agenda wiki page: https://community.icann.org/x/9xVIBg Mp3: https://gnso.icann.org/sites/default/files/policy/2019/audio/audio-new-gtld… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> Zoom Recording: https://icann.zoom.us/recording/play/kYR4anrYTGHHL4BeVa3Aoi5DQxuCDO6JVNz7di… The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg/ Main wiki page for the working group: https://community.icann.org/x/RgV1Aw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you. Kind regards, Julie

1 0

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 22 April 2019
by Julie Hedlund 22 Apr '19

22 Apr '19

Dear Working Group members, Please see below the notes from the meeting today, 22 April 2019. These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted at: https://community.icann.org/display/NGSPP/2019-04-22+New+gTLD+Subsequent+Pr…. Please also see the referenced document at: https://docs.google.com/document/d/1VSrLyWvfAiwDP-pe-QhAokRVoY1rpnDhfTqViwo…<https://docs.google.com/document/d/1VSrLyWvfAiwDP-pe-QhAokRVoY1rpnDhfTqViwo…> Kind regards, Julie Julie Hedlund, Policy Director Notes and Action Items: 1. Updates to Statements of Interest: No updates provided. 2. Zoom Introduction -- Staff/hosts cannot see private chat unless it is directed at staff/hosts. That is not included in the transcript reports. Staff/hosts will not see private chat between members. 3. Update on Work Track 5 -- Review of Questions for Community Input. -- Next will begin review of the proposals. 4. Review of Summary Documents – Continuation of Discussion from ICANN64 to Reach Closure on Select Topics -- Section 2.4.3 Systems: https://docs.google.com/document/d/1VSrLyWvfAiwDP-pe-QhAokRVoY1rpnDhfTqViwo…  2.4.3.c.1: The ICANN organization should ensure that enough time is provided for development and testing before any system is deployed. -- Support from all commenters. 2.4.3.c.2: Systems should undergo extensive, robust Quality Assurance (QA), User Interface (UI), and Penetration testing to ensure that they are stable and secure, and that data is properly protected and kept confidential where appropriate. -- Support from all commenters. 2.4.3.c.3: Applicant-facing systems should be usable and integrated, ideally with a single login. -- Support from all commenters. 2.4.3.c.4: Once a system is in use, the ICANN organization should be transparent about any system changes that impact applicants or the application process. In the event of any security breach, ICANN should immediately notify all impacted parties. -- Support from most commenters. -- New Ideas from RySG and ICANN Org. Discussion: -- Include language of what ICANN should do when there is a security breach (from Terms of Use already vetted by ICANN Legal). See here for possible language to address Security Incidents: https://www.icann.org/en/system/files/files/nsp-terms-of-use-11may18-en.pdf 2.4.3.c.5: The ICANN organization should offer prospective system end-users with the opportunity to beta-test systems while ensuring no unfair advantages are created for individuals who test the tools. It may accomplish this by setting up an Operational Test and Evaluation environment. -- Support from all commenters. 2.4.3.c.6: As stated in section 2.4.1 above, “Any Agreements/Terms of Use for systems access (including those required to be “clicked-through”) should be finalized in advance and included in the Applicant Guidebook with the goal of minimizing obstacles and/or legal burdens on applicants. -- Support from all commenters. Discussion: -- Delete “and included in the Applicant Guidebook”. 2.4.3.c.7: Implementation Guidance regarding technical systems: Applicants should be able to enter non-ASCII characters in certain fields. -- Support from all commenters. Discussion: -- What other fields must allow IDN scripts? At least TLD. 2.4.3.c.8: Implementation Guidance regarding technical systems: Applicants should be able to access live (real time) support using tools such as a phone helpline or online chat to address technical system issues. -- Support from all commenters. 2.4.3.c.9: Implementation Guidance regarding technical systems: A single applicant should be able to submit and access multiple applications without duplicative data entry and multiple logins. -- Support from most commenters. -- New Idea from ICANN Org. Discussion: -- Request from Kobe for ICANN Org to provide specifics on what improvements would add complexity, cost, and time. -- BRG suggested that this should be a low priority. -- Neustar concerns about possible delay, but generally supportive. -- Perhaps use the term “user” as opposed to “applicant” to avoid confusion. “User” meaning an already contracted party versus “applicant” being an applicant for a new string”. Include a definition. 2.4.3.c.10: Implementation Guidance regarding technical systems: Applicants should be able to receive automated confirmation emails from the systems. -- Support from all commenters. 2.4.3.c.11: Implementation Guidance regarding technical systems: Applicants should be able to receive automated application fee related invoices. -- Support from all commenters. 2.4.3.c.12: Implementation Guidance regarding technical systems: Applicants should be able to view changes that have been made to an application in the application system. -- Support from most commenters. -- ICANN Org Concerns. 2.4.3.c.13: Implementation Guidance regarding technical systems: Applicants should be able to upload application documents in the application system. -- Support from all commenters. 2.4.3.c.14: Implementation Guidance regarding technical systems: Applicants should be able to update information/documentation in multiple fields without having to copy and paste information into the relevant fields. -- Support from most commenters. -- ICANN Org Concerns. -- Some ICANN64 Concerns re: Mission and Purpose not be appropriate for “autofill”, and issue about “autofill” in relation to Question 23 as related to “services to be rendered” in the new TLD. Discussion: -- If we recommend a policy that limits where “autofill” can be used then the systems should be consistent with that policy. This discussion is limited to a system that allows autofill (where the policy allows it). -- The systems section will not override concerns about allowing autofill for answers to certain questions. -- Could the WG agree that autofill could be allowed for fields if technically feasible except for mission, purpose, and services to be rendered -- which will be parked and returned to later. Parking lost should include Question 18 and 23, but not exclude any other question referencing mission, purpose, or proposed services. 2.4.3.c.15: Implementation Guidance regarding technical systems: Applicants should be able to specify additional contacts to receive communication about the application and/or access the application and be able to specify different levels of access for these additional points of contact. The systems should provide means for portfolio applicants to provide answers to questions and then have them disseminated across all applications being supported. -- Support from most commenters. -- ICANN Org Concerns. -- BC Divergence. -- ICANN64 Concerns. Discussion: -- Tied to c.14 so it should be consistent. 2.4.3.c.16: Implementation Guidance regarding technical systems: The systems should provide clearly defined contacts within the ICANN organization for particular types of questions. -- Support from most commenters. -- BC New Idea. -- ICANN Org Divergence. Discussion: -- BC New Idea is consistent with how ICANN Org says it is actually done. -- Need to determine if ICANN Org is in agreement with the recommendation, or to rely on the existing system. Next Steps: Leadership to rank the recommendations in the systems section -- what would be high priority, not high priority, etc. Next call: Tuesday, 30 April 2019 at 03:00 UTC for 90 minutes.

1 0

Proposed Agenda - New gTLD Subsequent Procedures PDP WG meeting - Monday, 22 April 2019 at 20:00 UTC
by Julie Hedlund 17 Apr '19

17 Apr '19

Dear WG members, Please find below the proposed agenda for the upcoming call on Monday, 22 April 2019 at 20:00 UTC for 90 minutes: Draft Agenda: 1. Welcome/Review of the Agenda/Updates to Statements of Interest (SOIs) 2. Zoom Introduction 2. Update on Work Track 5 3. Review of Summary Documents – Continuation of Discussion from ICANN64 to Reach Closure on Select Topics (see: https://docs.google.com/document/d/1VSrLyWvfAiwDP-pe-QhAokRVoY1rpnDhfTqViwo…<https://docs.google.com/document/d/1VSrLyWvfAiwDP-pe-QhAokRVoY1rpnDhfTqViwo…>): Start with section 2.4.3 Systems 4. AOB Note, in relation to agenda item 2, WG leadership and staff have tried to prepare summary documents for each topic that seeks to help you review some of the background material, consider a high-level summary of what we believe the WG is seeking to accomplish for the topic, a high-level summary of public comment received, and finally, a sort of catch all at the end of each section (e.g., follow-up, parking lot, next steps). If you need a dial out or would like to send an apology for this call, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Julie Julie Hedlund, Policy Director

1 0

Recordings, attendance & AC chat / New gTLD Subsequent Procedures Working Group call held on Monday, 15 April 2019 at 15:00 UTC
by Michelle DeSmyter 16 Apr '19

16 Apr '19

Dear All, Please find the attendance and AC chat attached to this email, and the MP3 and Adobe Connect recording below for the New gTLD Subsequent Procedures Working Group call held on Monday, 15 April 2019 at 15:00 UTC. Attendance of the call is also posted on the agenda wiki page: https://community.icann.org/x/8hVIBg Zoom Recording: https://icann.zoom.us/recording/share/0mqpd9v31AM4nn5ylgBAW91WdDrWiuEIdjJhH… The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg/ Main wiki page for the working group: https://community.icann.org/x/RgV1Aw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you. Kind regards, Michelle

1 0