June 2016 - Gnso-newgtld-wg

- Draft Community Comment 1
by Steve Chan June 6, 2016

June 6, 2016

Dear WG Members, As agreed on the WG’s call on 1 June, staff has attempted to incorporate the feedback received on the call, as well as attempting to “normalize” the text so that it’s written from a single voice. The starting point was an export of the draft contained in the Google Doc (https://docs.google.com/document/d/1Gh8ugZAomD2AGNymmVRgKGP9TA2KQ7BkQbrRAEv…) to a Word document, which was then redlined with proposed changes. I’ve also included a clean document for your ease of reading. In the interest of providing as much time as possible for WG members to consider this latest draft ahead of the next WG call on Monday, 6 June, staff and the co-chairs agreed to share this document without a full review by the co-chairs, though limited discussion was held to discuss the expected changes. As a result, the co-chairs may contribute to suggested changes on the list, alongside WG members. As a reminder, the intent is for WG members to suggest edits on the list ahead of the 6 June meeting, come to agreement on a final version at the conclusion of that meeting, and send to the SO/AC/SG/Cs shortly thereafter. Please let me know if you have any questions or concerns. Best, Steve Steven Chan  Sr. Policy Manager   ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org direct: +1.310.301.3886  mobile: +1.310.339.4410 tel: +1.310.301.5800 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://twitter.com/ICANN_GNSO http://gnso.icann.org/en/

2 1

SSAC response to advice request
by avri doria June 6, 2016

June 6, 2016

FYI SSAC has released a SAC082 https://www.icann.org/en/system/files/files/sac-082-en.pdf in response to this groups request "seeking assistance in building a catalog of existing Advice or Statements for Working Group consideration during its deliberations. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

Pre-ICANN56 Policy Update Webinar Announcement
by Nathalie Peregrine June 2, 2016

June 2, 2016

PRE-ICANN56 POLICY UPDATE WEBINAR <https://www.icann.org/news/announcement-2016-06-02-en#><https://www.icann.org/news/announcement-2016-06-02-en#><https://www.icann.org/news/announcement-2016-06-02-en#><https://www.icann.org/news/announcement-2016-06-02-en#><https://www.icann.org/news/announcement-2016-06-02-en#><https://www.icann.org/news/announcement-2016-06-02-en#> Please RSVP via this form<http://goo.gl/forms/NEFg46A88QnWK8Z33> by 10 June 2016. Remote participation details will be sent the week of 13 June 2016. The ICANN Policy Development Support Team will provide a Policy Update Webinar on Thursday, 16 June 2016 at 10:00 UTC and 19:00 UTC, in preparation for the upcoming ICANN Policy Forum in Helsinki. The purpose of the webinar is to summarize policy activities across the ICANN policy development community and briefing the community on the Cross-Community sessions taking place in Helsinki. Cross-Community Sessions Briefings: * ICANN Accountability & Cross-Community Working Group (CCWG) Update * Charter for the Cross-Community Working Group (CCWG) on the use of new generic Top Level Domain (gTLD) Auction Proceeds * Draft Framework of Principles for Future Cross-Community Working Groups * New gTLD Subsequent Procedures Policy Development Process (PDP) * Next Generation generic Top Level Domain (gTLD) Registration Directory Service (WHOIS) Policy Development Process (PDP) * Review of All Rights Protection Mechanisms in all generic Top Level Domains (gTLDs) Policy Development Process (PDP) Supporting Organizations & Advisory Committee Updates: * Address Supporting Organization (ASO) and Regional Internet Registries (RIR) Policy Development * Country Code Names Supporting Organization (ccNSO) * ICANN Operational Plan & Budget * Country & Other Geographic Names Forum * Generic Names Supporting Organization (GNSO) * GNSO Review * Possible Modification of the WHOIS Conflicts with Local Law Procedure * At-Large Advisory Committee (ALAC) and At-Large Community * Policy Advice Development * Next Steps on the At-Large Review * Activities at ICANN56, including Outreach and Engagement and Regional At-Large Organizations (RALO) Sessions * Government Advisory Committee (GAC) * 2-Character Labels and Country Names as Second Level Domains in New generic Top Level Domains (gTLDs) * Advice Effectiveness * Privacy and Proxy Services Accreditation * International Governmental Organization (IGO) Acronyms Protections in New generic Top Level Domains (gTLDs) * Root Server System Advisory Committee (RSSAC) Advisory * Security and Stability Advisory Committee (SSAC) * Publications * DNSSEC Workshop The two sessions are duplicates, scheduled to accommodate different time zones. Each session runs for 90 minutes and will be conducted in English. The webinar will be conducted in Adobe Connect along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, questions may be submitted using the chat function in Adobe Connect. Recordings of the webinars will be made available here<https://www.icann.org/resources/pages/presentations-2012-08-27-en>. The Policy Development Support Team is always available to answer any questions via email at policyinfo(a)icann.org<mailto:policyinfo@icann.org>. Please RSVP via this form<http://goo.gl/forms/NEFg46A88QnWK8Z33> by 10 June 2016. Remote participation details will be sent the week of 13 June 2016.

1 0

Actions/Discussion Notes: New gTLD Subsequent Procedures PDP WG 01 June 2016
by Julie Hedlund June 2, 2016

June 2, 2016

Dear PDP WG members, Please see below the action items and discussion notes captured by staff from the meeting on 01 June. These high-level notes are designed to help PDP WG members navigate through the content of the call and are not meant as a substitute for the transcript. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/display/NGSPP/1.+WG+Meetings. Kind regards, Julie Julie Hedlund, Policy Director Actions/Discussion Notes: New gTLD Subsequent Procedures PDP WG Meeting, 01 June 2016 1. Review of action items (https://community.icann.org/x/A0WAAw) #7: Work Plan: Complete - Integrated comments received from PDP WG; further refinement likely needed in future, including integrating CCT-RT expected outputs. #19 Liaison for Review of All Rights Protection Mechanisms (RPMs): Staff is facilitating a search for a volunteer. #22 Drafting Team to Develop Constituency Comment 1: Staff is finalizing the document based on the discussion during the 01 June call. Produce final after 06 June call and send prior to 10 June document deadline. #24 Pull data on who applied, how many applied, and how many for at least the top 10 applicants (from discussion on application limits, pros and cons) – ongoing. 2. CC1 Discussion (Working Draft here: https://docs.google.com/document/d/1Gh8ugZAomD2AGNymmVRgKGP9TA2KQ7BkQbrRAEv…) Action Items: 1. Document format -- send as a cover letter with an annex. 2. Staff will produce a final document after the meeting on 06 June. Deliver the letter and document to the SO/AC/SG/C Chairs. 3. Enumerate questions for each section. Discussion Notes: Letter: 1. Staff confirmed that the letters be personalized if the Working Group desires. 2. Move the first sentence further down in the letter. 3. Look at the PDP Manual to determine if "Constituency Comment" is the correct terminology. 4. Deadline: 35 days is the minimum. Increase deadline from 35 days to 45 to account for Helsinki? Annex/Questions: General: Check consistency of use of terms. For example, instead of “types” use "categories" throughout the document. Another example, put “rounds” either in quotes or not. Question 1, page 4: 1. Use "ongoing" instead of "continuing". 2. Risk to "healthy development of the DNS market" or something more neutral, since the competition verdict is not out yet? - or "would the absence of a continuing mechanism have an anti-competitive effect?" 3. What does it mean to make a diverse set of names more diverse? The basic assumption is "Choice and Trust". Question 2, page 6: Delete “further information” comment. Page 7: Change to "Open for only one or a limited number of gTLDs". Question 3, page 8: Take out "further explanation". Page 9: 1. Put rounds in quotes, or drop them from the previous question (check for consistency). 2. Change to: "Does restricting applications to rounds or other cyclical applications models lead to more consistent treatment of applicants?" Page 10: 1. Change to two separate questions: Do rounds create artificial demand and/or artificial scarcity? 2. What is an ideal interval between rounds? Please explain. Page 11: Re-word introductory question. Page 12: Change to: What are the impacts on applicants, users and related parties/consumers from a process that lacks predictability? Page 13: 1. Define DG. 2. Change to: community engagement from early engagement. 3. Move PDP related questions lower, and more of a catch-all question at the end. 4. The more pre-work done, in theory, may lead to less problems downstream. However, not amount of planning will account for all problems that may arise. Page 14: Requires wording help: "Is there a time at which the application procedure in one application window should be frozen until after a new application window is opened for policy review.?" 3. Any Other Business: Work Plan Action Item: As there have not been any objections to the attached draft work plan, it will be considered as adopted by the Working Group, although this certainly does not prevent revisiting and revising in the future.

1 0

Mp3, Attendance & AC Chat from New gTLD Subsequent Procedures WG 01 June 2016
by Michelle DeSmyter June 2, 2016

June 2, 2016

Dear All, Please find the attendance of the call attached to this email and the MP3 recording below for the New gTLD Subsequent Procedures Working Group call held on Wednesday, 01 June 2016 at 22:00 UTC. MP3: http://audio.icann.org/gnso/gnso-new-gtld-subsequent-01jun16-en.mp3 <http://audio.icann.org/gnso/gnso-new-gtld-subsequent-01jun16-en.mp3> <http://audio.icann.org/gnso/gnso-new-gtld-subsequent-16may16-en.mp3> <http://audio.icann.org/gnso/gnso-new-gtld-subsequent-09may16-en.mp3http://a…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar<http://gnso.icann.org/en/group-activities/calendar#nov> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg/ Wiki page: https://community.icann.org/x/9xGOAw Thank you. Kind regards, Michelle DeSmyter ------------------------------- Adobe Connect chat transcript for Wednesday, 01 June 2016 Michelle DeSmyter:Dear All, Welcome to the New gTLD Subsequent Procedures WG call on Wednesday, 1 June 2016 at 22:00 UTC. Carlos Raul (CCT Review Team):90 minutes? Carlos Raul (CCT Review Team):I mean, is the call scheduled to last 90 minutes? Steve Chan:Yes, scheduled to last for up to 90 minutes Carlos Raul (CCT Review Team):Danke Steve Chan:De nada Steve Chan:Or according to Google Translate, Bitte Carlos Raul (CCT Review Team):Steve, I have a technical question: Adob asked me to donwload an app (in Safari) and it does not work eversince. While Adobe-Chrome does not activate my mic. Have you heard similar complaints? Carlos Raul (CCT Review Team):it has been like this for a week or so Steve Chan:I have not, but those complaints would probably not go to me. I had to download new Java plugins for Firefox. Carlos Raul (CCT Review Team):well, then may i please just ask for a phone bridge to +506-8837-7176 justin case I may need it? Steve Chan:Sure, I'll let Michelle know. Carlos Raul (CCT Review Team):thanks Carlos Raul (CCT Review Team):sorry Carlos Raul (CCT Review Team):terrible connections Freida Tallon (.sky):Good evening all Jeff Neuman:Its funny when all you hear is silence....I hope you all heard me just state the 2 minute warning Steve Chan:Confirmed! Jeff Neuman:funny story while we wait.....i used the phrase " I will be out of pocket for the next few hours" today and apparently that is an american expression. A non-american asked me if that meant I was out of money :) Jeff Neuman:To which I responded Yes, I will not be reachable by phone and I am also out of money ;) Rubens Kuhl:Jeff is out of money due to USD 1 per "round" ... Richard Padilla:Hi all Carlos Raul (CCT Review Team):Jeff will never learn Steve Chan:Avri, at least for me, you're a bit faint and distant sounding? Jeff Neuman:me too Steve Chan:Much better! Steve Coates (Twitter):I have to drop off for a family emegency. Apologies. Jeff Neuman:Sure. Steve hope everything is ok Rubens Kuhl:What's the target date for releasing the CC1 document ? Greg Shatan:Hello all. Sorry to be late. Jeff Neuman:By the document deadline for the helsinki meeting Jeff Neuman:which I believe is June 10th Carlos Raul (CCT Review Team):yes Carlos Raul (CCT Review Team):thnaks you avri Steve Chan:no problem Rubens Kuhl:Considering the CC1 documents gets out June 10th, what would be deadline for responses ? Steve Chan:@Rubens, as noted in the PDP Manual, 35 days are allotted Rubens Kuhl:Tks Steve Chan:35 days at a minimum :) Kristina Rosette (Amazon Registry):Hi. Have been on the call for a bit, but was having Adobe Connect issues. Carlos Raul (CCT Review Team):@Kristina Adobe connect.sucks as of late Rubens Kuhl:Adobe working for me without issues for the last few weeks... Susan Payne:I thought we were going to ask the HAC specifically to identify ways and what they are working on. or is that in he cover letter? Susan Payne:sorry typo GAC Carlos Raul (CCT Review Team):just lost the bridge Carlos Raul (CCT Review Team):it was not an open issue Carlos Raul (CCT Review Team):just a clarification Carlos Raul (CCT Review Team):thank you Carlos Raul (CCT Review Team): sorry I have no mic Cheryl Langdon-Orr (CLO):bad echo for me Jeff Neuman:big echo Susan Payne:identify WGs and what they are working on. apologies for typo/autocorrect issues Carlos Raul (CCT Review Team):Disclaimer: Carlos didn´t mean to be a pain in the neck, but was aked to take a look at the draft letter from the point of view of English as a second language. Carlos normally respects Avri´s drafting fully. :) Carlos Raul (CCT Review Team):jajajajaja Steve Chan:@Susan, we can customize for the GAC. DId you have specific changes in mind, perhaps in section 3? Kristina Rosette (Amazon Registry):Would the absence of a continuing mechanism be anticompetitive or likely to have an anticompetitive effect? (or something along those lines) Kristina Rosette (Amazon Registry):works for me. thank you Steve Chan:Just a reminder to participants that the CC1 document is available here: https://docs.google.com/document/d/1Gh8ugZAomD2AGNymmVRgKGP9TA2KQ7BkQbrRAEv… Steve Chan:And Avri is making real-time edits during the meeting. Jeff Neuman:I agree that someone will need to review for grammar as lots of wordsmithing going on...including by me :) Carlos Raul (CCT Review Team):Question is type=categroies??? Carlos Raul (CCT Review Team):right now in this question is a little confusing Carlos Raul (CCT Review Team):thanks Jeff Jeff Neuman:I am good with that "type" of change throughout Robin Gross:of course the GAC isn't the only group who can categorize in this process. Jeff Neuman:Understood Jeff Neuman:I think so Samantha Demetriou:Maybe and/or rather than and? Samantha Demetriou:Yes, sorry! Vaibhav Aggarwal:redoubt q Vaibhav Aggarwal:redundant Vaibhav Aggarwal:for the pent up demand Steve Chan:I think we should enummerate the questions in each section Steve Chan:yes Vaibhav Aggarwal:t he first one with artificial one Vaibhav Aggarwal:demand and scarcity Greg Shatan:I don't think they're the same. Vaibhav Aggarwal:right Greg Shatan:Not sure there is such a thing as 'artificial demand".... Vaibhav Aggarwal:the wait time is there anywhichways Robin Gross:"unmet demand" might be better than "pent up demand" Greg Shatan:Although one might say that defensive registrations are a form of "artificial demand" Greg Shatan:I kind of like pent up.... Robin Gross:I don't feel strongly about it, just a suggestion. Greg Shatan:Agree they are not synonymous Robin Gross:don't mind. Cheryl Langdon-Orr (CLO):thx for restating I found the last speaker hard to hear ... ok to delete Kristina Rosette (Amazon Registry):Have to drop for another meeting. I'll read the transcript to catch up on what I miss. Vaibhav Aggarwal:pent up demand is demand created due to external forces Rubens Kuhl:Have to drop sooner today as well. Bye all! Greg Shatan:No, pent up demand is demand that exists but has no outlet. Cheryl Langdon-Orr (CLO):yup Vaibhav Aggarwal:so this could be on artificial and pent up and artificial scarcity Greg Shatan:Those are 3 different concepts. Steve Chan:Correct Vaibhav Aggarwal:if it is important for the sake of redundancy, we can ask three separate questions then, depending on the purpose it is serving Greg Shatan:I don't think there is any redundancy. Jeff Neuman:What wol dyou propose for the 3 questions? Jeff Neuman:oops...what would you propose Greg Shatan:On a related note, I recommend listening to "Pent-Up House" by Sonny Rollins; https://youtu.be/yIlpEnsa2d8 Vaibhav Aggarwal:related parties Carlos Raul (CCT Review Team):Applicants and users are summarized as conumers in CCT Carlos Raul (CCT Review Team):Consumers=Applicants + Useres Carlos Raul (CCT Review Team):about the 3rd parties???? Carlos Raul (CCT Review Team):its in our charter Carlos Raul (CCT Review Team):right Carlos Raul (CCT Review Team):applicants, users and others Carlos Raul (CCT Review Team):and important others Carlos Raul (CCT Review Team)::) Jeff Neuman:ok Cheryl Langdon-Orr (CLO):other parties Greg Shatan:Good point -- this should be focused on the application process, not the PDP process. Carlos Raul (CCT Review Team):it is clear, thanks Steve Chan:I do not necessarily have an opinion one way or the other, but just wanted to try and provide context. Cheryl Langdon-Orr (CLO):agree Jeff Vaibhav Aggarwal:sure. will do. Richard Padilla:got to go bye for now Philip Corwin:ciao all Jeff Neuman:I think once the changes are made, we can review for flow and "understandability". I think we will be fine. Cheryl Langdon-Orr (CLO):Sorry I have to leave now as well BYE Jeff Neuman:Lets just get a commitment from everyone to work on the list PLEASE :) Vaibhav Aggarwal::-) Christa Taylor:Thank-you Robin Gross:thanks, bye!

1 0

- Proposed Agenda
by Steve Chan June 1, 2016

June 1, 2016

Dear WG Members, Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Wednesday 1 June 2016 at 22:00 UTC. 1. Review Agenda 2. Roll Call/SOIs 3. Review of action items (https://community.icann.org/x/A0WAAw) 4. CC1 Discussion, continued (Working Draft here: https://docs.google.com/document/d/1Gh8ugZAomD2AGNymmVRgKGP9TA2KQ7BkQbrRAEv…) 5. AOB a. Work Plan – As there have not been any objections to the attached draft work plan, it will be considered as adopted by the WG, although this certainly does not prevent revisiting and revising in the future. Those signed up as Members to this PDP WG should have received meeting information from the GNSO Secretariat. If you did not receive these participation details, please contact the GNSO Secretariat for assistance (gnso-secs(a)icann.org) Best, Steve Steven Chan  Sr. Policy Manager   ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org direct: +1.310.301.3886  mobile: +1.310.339.4410 tel: +1.310.301.5800 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://twitter.com/ICANN_GNSO http://gnso.icann.org/en/

3 2