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

Proposed Agenda: New gTLD Subsequent Procedures Working Group, 27 February at 1500 UTC
by Steve Chan Feb. 24, 2017

Feb. 24, 2017

Dear WG Members, Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday, 27 February 2017 at 1500 UTC for 90 minutes. 1. Welcome/Review Agenda 2. SOIs 3. Work Track Updates 4. Community Comment 2 (CC2) first reading (Working document here: https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLsMHKkNczR_b6-jH2Wl5eVH…) 5. ICANN58 Planning 6. AOB If you need a dial-out or want to send an apology, please email 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 mobile: +1.310.339.4410 office tel: +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/

1 0

Pre-ICANN58 Policy Open House - Monday, 6 March 2017 10:00 UTC and 19:00 UTC
by Terri Agnew Feb. 22, 2017

Feb. 22, 2017

https://www.icann.org/news/announcement-2017-02-22-en[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Monday, 6 March 2017 - 10:00 UTC and 19:00 UTC The Policy Development Support Team is pleased to announce two sessions of the Pre-ICANN58 Policy Open House on Monday, 6 March 2017 at 10:00 UTC and 19:00 UTC. The Policy Open House builds on the previous Policy Update Webinar and incorporates more interaction. The new format will feature: · Decreased Duration | Two 60-minute sessions, rather than two 90-minute briefings · Interactive Format | A question and answer exchange with the Policy Team · Preparatory Materials | The Pre-ICANN58 Policy Report and Generic Names Supporting Organization Policy Development Process Briefings will be published one week prior to the open house This improved structure will allow the ICANN community to ask questions about policy and advice development work taking place at ICANN58. The Policy Team also welcomes questions through the upcoming registration form and via email at policyinfo(a)icann.org <mailto:policyinfo@icann.org> . Registration begins on Monday, 27 February 2017. The open house will run in English and will be conducted in Adobe Connect along with a dial-in conference bridge for audio. Recordings of the sessions will be made available here[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> . The Policy Team looks forward to assisting the ICANN community prepare for ICANN58! --------------- David A. Olive Senior Vice President | Policy Development Support Managing Director ICANN Regional Headquarters | Istanbul <mailto:david.olive@icann.org> david.olive(a)icann.org ICANN | Internet Corporation for Assigned Names and Numbers | Hakki Yeten Caddesi | Selenium Plaza | No:10/C K:10 | 34349 | Fulya | Besiktas | Istanbul Mobile +1. 202.341.3611 | Mobile +90.533.341.6550 | Direct Line +90.212.999.6212

1 0

Proposed Agenda: New gTLD Subsequent Procedures Working Group, 13 February 2017
by Steve Chan Feb. 14, 2017

Feb. 14, 2017

Dear All, Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday, 13 February 2017 at 2000 UTC for 90 minutes. 1. Welcome/Review Agenda 2. SOIs 3. Work Track Updates 4. Community Comment 2 (CC2) discussion (Working document here: https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLsMHKkNczR_b6-jH2Wl5eVH…) 5. AOB a. ICANN58 planning b. Overarching Issues drafting teams reminder (sign-up sheet here: https://docs.google.com/document/d/1g-OoBec_Q6nnBofBvcTnfAotFh7yq07HUM7kxh6…) If you need a dial-out or want to send an apology, please email 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 mobile: +1.310.339.4410 office tel: +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/

5 4

Mp3, Attendance & AC Chat for New gTLD Subsequent Procedures WG on Monday, 13 February 2017 at 20:00 UTC
by Michelle DeSmyter Feb. 14, 2017

Feb. 14, 2017

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 Monday, 13 February 2017 at 20:00 UTC. Attendance of the calls is also posted on the agenda wiki page: https://community.icann.org/x/lbHDAw MP3: http://audio.icann.org/gnso/gnso-new-gtld-subsequent-13feb17-en.mp3 <http://audio.icann.org/gnso/gnso-new-gtld-subsequent-08sep16-en.mp3> 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/lbHDAw Thank you. Kind regards, Michelle ------------------------------- Adobe Connect chat transcript for Monday, 13 February 2017 Michelle DeSmyter:Dear All, Welcome to the New gTLD Subsequent Procedures Working Group call on Monday, 13 February 2017 at 20:00 UTC. Michelle DeSmyter:Meeting page: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Kavouss Arasteh:Hi Emioly, Hi Michelle Kavouss Arasteh:Is it possible to providing scroll contzrol Kavouss Arasteh:By the way I am disconnectzed Michelle DeSmyter:thank you Kavouss - I will let the operator know to redial you as soon as possible Michelle DeSmyter:stand by... Cheryl Langdon-Orr (CLO):hi all Karen Day:Good afternoon everyone Jeff Neuman:hello... Jeff Neuman:Avri - can you turn up mic Carlton Samuels:Howdy all Christa Taylor:+1 Avri! Michelle DeSmyter:Phil will have audio momentarily Michelle DeSmyter:Phil Buckingham is now connected on the audio phone line Rubens Kuhl:Emily also has her hand up. Cheryl Langdon-Orr (CLO):thx Emily Jeff Neuman:Emily - Thanks...i knew i would mess that up :) Heather Forrest:Thanks, Emily Jeff Neuman:@Heather, did I misstate anything? Jeff Neuman:There have been some articles published recently about trying to move the process along (not to put anyone on the spot), but the best way to move us forward is to actively participate. :) Jeff Neuman:The IDN discussion in WT4 last week was really helpful. I encourage everyone who doesnt fully understand IDN to listen to it. Rubens Kuhl:"Everything you wanted to know about IDNs but was afraid to ask" Emily Barabas:The CC2 Google document is available at https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume… Emily Barabas:Everyone has scroll control of the PDF version in the center pod Trang Nguyen:@Jeff: Should the EBERO program be factored into the RSP Programs discussion? Trang Nguyen:ok Rubens Kuhl:@Trang some people believe EBERO and COI can be dealt with outside of a formal RSP Program. Some do think it needs to be bundled. Steve Coates:I had to reenter. Worked well the 2nd time. Trang Nguyen:Thanks, Rubens. I guess it all depends on how the program (EBERO) is designed. Susan Payne:now in, thanks Emily Barabas:Apologies for the interruption Jeff Emily Barabas:@Susan, great. Thanks for letting us know. vanda scartezini:sorry to be late, in another call. Phil Buckingham:Apologises for being late ( and Michael 's absence ) . Re WT2 Update ; Re background checks - as discussed on our call last week . Q to ICANN . Could WT2 be provided with the number of applicants that failed the background check @ Trang Does ICANN have this data ? can we discuss on email ? Christa Taylor:Noted and will add for the next call Trang Nguyen:@Phil, apologies I missed the last WT2 call due to a conflict. When I listened to the recording, it was not clear that the WT agreed on a formulation of question to ICANN org? If you and/or Michael could please send the WT's question to the list, we'd be happy to respond. As we have different data that we collect, it would be helpful when formulating the question to indicate the intent/purpose of the question so we can make sure that we provide the appropriate response. Donna Austin, Neustar:I think understanding the audience is an important point. Kavouss Arasteh:This group seems to be very popular as 42 persons attending Dietmar Lenden - Valideus:yes Phil Buckingham:Trang , many thanks . Will do . Rubens Kuhl:@Phil and @Trang, possibly knowing also whether background checks at application time had different results from the ones at contract signing time is also an interesting indicator. Emily Barabas:It does not appear that Denise is back in the AC room. If anyone is connected to her by Skype or other chat, it would be helpful to know if she is still having technical difficulties. Kavouss Arasteh:Avri, there is some echo when you tak avri doria:thanks Kavous. i am using a headet, so i am not sure how i could be casing it. Kavouss Arasteh:May the secretariat kindly include my question in the note and actions to betaken Julie Hedlund:@Kavouss: I endeavored to capture it. If it is not sufficient please include additional text in this chat. Julie Hedlund:@Kavouss: I apologize because it is hard for me to hear you clearly. Emily Barabas:90 mins Julie Hedlund:90 minutes Rubens Kuhl:@Kavouss All gTLD registries are obliged by contract to serve all accredited registrars on a non-discriminatory basis. But for instance, if the country where registry is established blocks business with some countries, law of the landprevails over ICANN principles. Jon Nevett:I just joined due to a conflict -- sorry I'm late Phil Buckingham:@ kavouss. your question has been noted. WT2 will discuss this on our 2nd March call. re vertical integration . Thanks. Heather Forrest:Apologies, all, I have to drop off now to attend another call. Have a good day! Donna Austin, Neustar:Apologies all, I have to join another call. Olga Cavalli:My apologies I must attend another meeting. Kavouss Arasteh:Tom. we are the only one from GAC if I am not mistaken Steve Chan:I will circulate an email to the group that details the meetings that are currently requested/tentatively scheduled. Karen Day:@Steve is GAC Sub-Pro Session for bi-lateral discussion between the groups? Rubens Kuhl:Jeff has been cut off. Karen Day:Sat at 17:00 Jeff Neuman:Back in...thankanks Jeff Neuman:thanks Steve Chan:@Karen, I believe the intention would be that it is an open session, not just bilateral Karen Day:Thanks, Steve Kavouss Arasteh:But we need to mention that Cheryl Langdon-Orr (CLO):your audio is starting to distort a lot Avri at least for me Emily Barabas:Sign up here: https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume… Steve Chan:FYI, Jeff and Avri volunteered for all of the groups :) Jeff Neuman:Someone is typing into the mic Kavouss Arasteh:What we mean by "Differenrt TLD"? Jeff Neuman:Categories Rubens Kuhl:Different types of TLDs, actually. Cheryl Langdon-Orr (CLO):see I thought we were trying to get others/ more people involved not just the existing Rapouteur list Rubens Kuhl:If a phone call is deemed necessary, I suggested asking WT leaders for a slot inside the most relevant WT close to the matter. Rubens Kuhl:(I suggest) Kavouss Arasteh:I have a point to raise under AOB Christa Taylor:There is overlap so might be difficult to have only one WT oversee the activities. Also, please consider our current restraining timelines Kavouss Arasteh:But it would good to have an executive summary of that Report to be made available to the enitre community Carlton Samuels:Bye all Cheryl Langdon-Orr (CLO):bye for now then.... talk again soon... Kavouss Arasteh:Tks Avri Kavouss Arasteh:Tks JEFF Jeff Neuman:Thanks everyone! Sara Bockey:thanks all Rubens Kuhl:Bye all! Thanks! Christa Taylor:Thank-you. Great call! avri doria:bye Alexander Schubert:Tnx Susan Payne:bye vanda scartezini:thanks to all, good meeting Laura Watkins (Nominet):thanks Phil Buckingham:thanks jeff , avri avri doria:bye all. thanks Susan Payne:thank avri

1 0

Actions/Discussion Notes: New gTLD Subsequent Procedures PDP Meeting 13 February 2017
by Emily Barabas Feb. 13, 2017

Feb. 13, 2017

Dear working group members, Please see below the action items and discussion notes captured by staff from the meeting on 13 February. These high-level notes are designed to help working group members navigate through the content of the call and are not a substitute for the transcript or the recording. See the chat record, call transcript, and recording at: https://community.icann.org/x/lbHDAw. Kind regards, Emily Agenda: New gTLD Subsequent Procedures Working Group Audio Only: Apologies: Annebeth Lange, Alan Greenberg, Sara Bockey, Phil Corwin, Kristina Rosette Agenda: 1. Welcome/Review Agenda 2. SOIs 3. WT Updates 4. Community Comment 2 (CC2) discussion (Working document here: https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLs MHKkNczR_b6-jH2Wl5eVH-WWM/edit?usp=sharing). 5. AOB 6. ICANN58 planning 7. Overarching Issues drafting teams reminder (sign-up sheet here: https://docs.google.com/document/d/1g-OoBec_Q6nnBofBvcTnfAotFh7yq07HUM7kxh6…) Action Items: ACTION ITEM: Staff will email the group with details of meetings currently requested/tentatively scheduled Notes: 1. Work Track Updates -- Note that all groups need more participation and contribution. Work Track 1 -- Christa Taylor, Co-Chair -- Call later this evening. Topic is accreditation. -- Cost recovery gap. -- Follow on prioritization. -- Touch on systems and communications. -- AGB. -- CC2 questions. Work Track 2 -- Jeff Neuman -- Meeting this week. -- Discussion on Terms and Conditions from policy level, but not a re-write of the text. Whether to include issue of excluding certain claims; other issues. -- CCWG on Use of Country and Territory Names at the Top Level -- might refer some issues to Work Track 2. That group is still meeting and will come out with final recommendations for public comment and will be out following ICANN58. Endeavoring to liaise with them and the GAC on a framework to have this discussion. From the Chat: Phil Buckingham: Re WT2 Update; Re background checks - as discussed on our call last week . Q to ICANN . Could WT2 be provided with the number of applicants that failed the background check @ Trang Does ICANN have this data ? can we discuss on email ? Trang Nguyen: @Phil, apologies I missed the last WT2 call due to a conflict. When I listened to the recording, it was not clear that the WT agreed on a formulation of question to ICANN org? If you and/or Michael could please send the WT's question to the list, we'd be happy to respond. As we have different data that we collect, it would be helpful when formulating the question to indicate the intent/purpose of the question so we can make sure that we provide the appropriate response. Rubens Kuhl: @Phil and @Trang, possibly knowing also whether background checks at application time had different results from the ones at contract signing time is also an interesting indicator. Work Track 3 -- Karen Day, Co-Chair -- Last meeting went through a strawman proposal on changes to the legal rights objection process; this is out for comment on the list. -- Next call is 21 February -- discussing confusing similarity objection process. Work Track 4 -- Rubens Kuhl, Co-Chair -- Had a WT4 call last week that focused on IDNs. Growing consensus on allowing 1 character IDNs in specific instances; allowing for variant TLDs. Specific policies for confusing similarity that may arise. -- Hoping to discuss universal acceptance on next call. -- Next call is on 23 February. From the chat: Jeff Neuman: There have been some articles published recently about trying to move the process along (not to put anyone on the spot), but the best way to move us forward is to actively participate. :) Jeff Neuman: The IDN discussion in WT4 last week was really helpful. I encourage everyone who doesn’t fully understand IDN to listen to it. Rubens Kuhl: "Everything you wanted to know about IDNs but was afraid to ask" 2. Community Comment 2 (CC2) discussion (Working document here: https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLs MHKkNczR_b6-jH2Wl5eVH-WWM/edit?usp=sharing). Work Track 1 -- Overall Process, Support and Outreach 1.1 Accreditation Programs -- "accreditation" means different things to different people; trying to reword. -- Asking if others see the benefits or risks of a program. -- Asking about scalability. -- Relationship between the transfer of RSP for an existing registry operator be considered in scope of the PDP. From the Chat: Trang Nguyen: @Jeff: Should the EBERO program be factored into the RSP Programs discussion? -- Think there are some connections there. Rubens Kuhl: @Trang some people believe EBERO and COI can be dealt with outside of a formal RSP Program. Some do think it needs to be bundled. Trang Nguyen: Thanks, Rubens. I guess it all depends on how the program (EBERO) is designed. 1.2 Applicant Support -- Some issues from the last round -- is there value in suggestions already made? -- What else other than financial support? -- How to make sure there is awareness of the program. 1.3 Clarity of the Overall Application Process: -- Areas of possible revision, such as change requests, customer support, etc. 1.4 Application Fees -- Discussion at last Work Track 1 call. -- Floor or ceiling threshold and how to establish. -- Question as a policy matter of what to do if there is a shortfall or surplus. 1.5 Variable Fees -- Whether different types of applications should have different types of costs. Seems to be support for "one fee fits all". 1.6 Application Submission Period -- Is 3 months an appropriate length to accept applications. Future application windows may not need as much time. 1.7 Application Queuing -- Appears to be support for an evaluation ordering process such as the prioritization draw, instead of first come, first served. -- Prioritization given to IDNs in the last round -- keep that? 1.8 Systems -- Discussion in Work Track 1 on systems used in applications and evaluation processes. Communications with existing registries. 1.9 Communications -- Issues about communications from last round. -- Metrics for success. 1.10 Application Guidebook -- Makes sense to partition the AGB into different audience driven sections or type of application. Question: What is appropriate for discussion in this group on rights protection mechanism and what should be discussed in the RPM PDP WG? There does seem to be overlap. From the chat: Donna Austin, Neustar: I think understanding the audience is an important point. Work Track 2 -- Legal, Regulatory, and Contractual Requirements 2.1 Base Registry Agreement 2.2 RPMs -- Preliminary questions. -- For second-level RPMs just a reference to the PDP WG. There are areas of overlap. 2.3 Reserved Names -- String requirements; string ineligible for delegation, specification 5. -- Work going on in IETF that may or may not have an effect on reserved names. Important to get an overview of that work. 2.4 Registrant Protections -- Relates to COI, EBERO, data escrow, registry performance specifications. -- Background checks (don't have a question yet). -- Question: Registrars having restriction to access to certain TLDs, what action can be taken to remove that restriction - from access to gTLDs in countries? REQUEST: Is it convenient when GAC has a meeting with GNSO that some of the main issues of this question could be put in that meeting? Trying to reply timely to questions that are raised. Answer: Haven't gotten to registry/registrar separation and non-discrimination, separation by country and other factors -- Section 2.8 of these questions. Helpful to have examples. From the chat: Rubens Kuhl: @Kavouss All gTLD registries are obliged by contract to serve all accredited registrars on a non-discriminatory basis. But for instance, if the country where registry is established blocks business with some countries, law of the land prevails over ICANN principles. 2.5 IGO/INGO Procedures -- PDP WG already going on. May or may not ask any questions depending on that. 2.6 Closed Generics -- Exclusive use -- allowed? -- How to define "generic"? 2.7 Applicant Terms and Conditions 2.8 Registrar Non Discrimination & Registry/Registrar Separation 2.9 Registry/Registrar Standardization 2.10 TLD Rollout 2.11 Contractual Compliance 2.12 Global Public Interest Work Track 3 – String Contention Objections and Disputes -- 3.1: Feedback is needed on the objections sections, WG members are encouraged to provide input -- Additional WT3 topics: New gTLD Applicant Freedom of Expression (3.2), Community Applications (3.3), String Similarity (3.4), Accountability Mechanisms (3.5) Work Track 4 – IDNs and Technical & Operations -- IDNs (4.1), Universal Acceptance (4.2), Application Evaluation (4.3), Name Collision (4.4), Security and Stability (4.5) 6. ICANN58 Planning -- 3 hour face-to-face WG session scheduled. How should we structure our time? -- Hopefully we will be done with the CC2 questions by ICANN58 and can focus on substantive issues addressed in the PDP -- Additional sessions during ICANN58 tentatively scheduled, community-facing session (90 mins on Day 5, 17:00 to 18:30 local time), possible meeting with the GAC ACTION ITEM: Staff will email the group with details of meetings currently requested/tentatively scheduled -- Question: Will the question be addressed as to whether the GNSO PDP is subject to human rights considerations? -- Answer: This PDP does not determine the framework of interpretation. On a personal level, supportive of the topic being discussed in general. -- Feedback: some reference should be made to human rights, to be consistent with the whole of ICANN. 7. Overarching Issues Drafting Teams (sign-up sheet here: https://docs.google.com/document/d/1g-OoBec_Q6nnBofBvcTnfAotFh7yq07HUM7kxh6…) -- Three groups are being formed: Different TLD Types (currently 7 signed up); Predictability/Community Engagement (currently 1 signed up); Applications Assessed in Rounds (currently 3 signed up) -- We need more volunteers, especially for the Predictability/Community Engagement team -- Question: How will the groups work? Will there be more phone calls? -- Answer: That will be up to the group. The group can decide to work over email and using shared documents. Phone calls are not anticipated, but the group can determine if they need to schedule a call. The leadership will not set up regular calls for these groups. From the chat: Rubens Kuhl: If a phone call is deemed necessary, I suggest asking WT leaders for a slot inside the most relevant WT close to the matter. 5. AOB -- Question: Do you foresee a brief summary about this group and its progress that will be available to the ICANN community? -- This group will be doing a report to the GNSO on the status of this group -- The Policy group puts together a pre-meeting webinar -- GNSO Policy Briefing and SO/AC Policy Briefing documents are circulated prior to the ICANN meeting -- GAC early engagement documents also provide an update on each PDP WG -- The group may want to revisit the idea of a WG newsletter to keep the community and group members up-to-date on activities Emily Barabas | Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

- Drafting Teams Call for Volunteers
by Steve Chan Feb. 9, 2017

Feb. 9, 2017

Dear WG Members, During recent full WG calls, it was agreed that in order to drive progress, drafting teams should be established for a handful of the overarching issues. The expectation is that these drafting teams will be able to develop proposals that can then be considered by the full WG. Please review the three calls for volunteers below and follow the instructions to participate in any or all where you are interested. Please indicate your interest by 15 February so that these teams can initiate their work in a timely manner. If you have any questions, please let WG leadership or staff know. Best, Steve Call for Volunteers – Subsequent Procedure Drafting Teams 1. Charter Topic: Different TLD Types (https://community.icann.org/x/Nz2AAw) What This Team Will Do: The WG is seeking to define the characteristics of the preliminary set of categories identified by the WG, then determine what changes could be needed. This drafting team will prepare a set of draft outputs that will be considered by the full WG. The anticipated deliverables include: · A matrix that pinpoints the specific characteristics of the categories · At least at a high level, the related changes to the application process, evaluation criteria, and contractual requirements that would likely be necessary and perhaps unique to certain categories/characteristics. · Any enforcement mechanisms that may be needed as a result of establishing different paths to obtaining a new gTLD. · A recommendation as to whether the creation of applicable categories is necessary or whether the unique aspects of those categories can be handled through the existing processes. Documentation of deliberations to date can be found here: https://docs.google.com/document/d/16Sd6mpO5MqHl7BHOl9HBENDgUvcqQ04QumbVNfV… How This Team Will Work: This drafting team may employ a variety of mechanisms to address its work. It is anticipated that the drafting team will complete its work primarily over email, collaborating via Google Docs, and occasional meetings. Meetings will be recorded, the email list archived, and the group will utilize public workspaces (i.e., Google Docs, Wiki). How to Participate: Simply add your name to the sign-up document here (https://docs.google.com/document/d/1g-OoBec_Q6nnBofBvcTnfAotFh7yq07HUM7kxh6…) The only requirement to participate is that you are a member of the WG. If you have any issues accessing the Google Doc, you can send an email to staff instead and we can add your name on your behalf. 2. Charter Topic: Predictability/Community Engagement (https://community.icann.org/x/Nz2AAw and https://community.icann.org/x/IT2AAw) What This Team Will Do: Preliminarily, the WG has determined that a framework for predictability and change control may help mitigate the destabilizing effect from unforeseen issues encountered after policy implementation and/or program launch. Some elements of the framework could include determining what factors should be predictable (e.g., outcomes, timeframes, input from the community, etc.), expectations for what could cause change and the scope of an acceptable level of change, how fundamental changes are dealt with, etc. This drafting team will prepare a set of draft outputs that will considered by the full WG. Documentation of deliberations to date can be found here: https://docs.google.com/document/d/16Sd6mpO5MqHl7BHOl9HBENDgUvcqQ04QumbVNfV… How This Team Will Work: This drafting team may employ a variety of mechanisms to address its work. It is anticipated that the drafting team will complete its work primarily over email, collaborating via Google Docs, and occasional meetings. Meetings will be recorded, the email list archived, and the group will utilize public workspaces (i.e., Google Docs, Wiki). How to Participate: Simply add your name to the sign-up document here (https://docs.google.com/document/d/1g-OoBec_Q6nnBofBvcTnfAotFh7yq07HUM7kxh6…) The only requirement to participate is that you are a member of the WG. If you have any issues accessing the Google Doc, you can send an email to staff instead and we can add your name on your behalf. 3. Charter Topic: Applications Assessed in Rounds (https://community.icann.org/x/Jz2AAw) What This Team Will Do: The WG agreed that there should be an ongoing process that is clearly defined and provides clear guidance on how and when applications will be accepted in the future, however, it has yet to establish specific details to promote these features. The WG has agreed that a drafting team should document the issue, identify requirements, and propose a solution or solutions for consideration by the full WG. The WG has already considered several options detailed below, but the drafting team would not be limited to just these ideas: · A fixed set of rounds (or perhaps defined by certain criteria to determine the “extent of demand”), followed by some form of steady state. o The steady state could be first come, first served, though issues have been identified with this approach (e.g., may favor ICANN insiders, may cause a strain on ICANN systems, may promote hastily prepared applications, etc.) o The steady state could be annual windows, or something similar (e.g., three months of application acceptance, remaining 9 months to complete evaluation, repeat on a yearly basis). · Immediately settling into a steady state. Documentation of deliberations to date can be found here: https://docs.google.com/document/d/16Sd6mpO5MqHl7BHOl9HBENDgUvcqQ04QumbVNfV… How This Team Will Work: This drafting team may employ a variety of mechanisms to address its work. It is anticipated that the drafting team will complete its work primarily over email, collaborating via Google Docs, and occasional meetings. Meetings will be recorded, the email list archived, and the group will utilize public workspaces (i.e., Google Docs, Wiki). How to Participate: Simply add your name to the sign-up document here (https://docs.google.com/document/d/1g-OoBec_Q6nnBofBvcTnfAotFh7yq07HUM7kxh6…) The only requirement to participate is that you are a member of the WG. If you have any issues accessing the Google Doc, you can send an email to staff instead and we can add your name on your behalf. Steven Chan  Sr. Policy Manager   ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org mobile: +1.310.339.4410 office tel: +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 2

- Work Track Meeting Schedules
by Steve Chan Feb. 3, 2017

Feb. 3, 2017

Dear WG Members, The leadership and staff have created a schedule of upcoming work track meetings through ICANN58, that highlight what is expected to be discussed at each meeting. I’ve attached a PDF of the current version of this schedule, but this is expected to be a living document. You can find the Google Doc here: https://docs.google.com/spreadsheets/d/1O_NpWTXFMNHkJARveqCapEssRt1CaEqwWe8… The primary intention in creating this document is to help members better prepare and participate in the work track meetings. We will likely add the full WG meetings into the schedule as well. Please let us know if you have any questions, concerns, or suggestions for improvement. 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://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

1 0

Community Comment 2 (CC2) Drafting
by Steve Chan Feb. 1, 2017

Feb. 1, 2017

Dear WG Members, Staff had an action item from Monday’s full WG call to provide a PDF version of the Community Comment 2 (CC2) draft, which you will find attached. Additional questions have been added and revisions have been made to existing questions since that meeting. This is a living document until it is finalized, so please provide suggestions (e.g., redlines) or comments directly to the Google Doc (https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLsMHKkNczR_b6-jH2Wl5eVH…) or to this email thread if you would prefer. 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://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

1 0

Mp3, Attendance & AC Chat for New gTLD Subsequent Procedures WG call on Monday, 30 January 2017 at 15:00 UTC
by Michelle DeSmyter Jan. 30, 2017

Jan. 30, 2017

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 Monday, 30 January 2017 at 15:00 UTC. Attendance of the calls is also posted on the agenda wiki page: MP3: http://audio.icann.org/gnso/gnso-new-gtld-subsequent-30jan17-en.mp3 <http://audio.icann.org/gnso/gnso-new-gtld-subsequent-08sep16-en.mp3> 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/krHDAw <http://audio.icann.org/gnso/gnso-new-gtld-subsequent-30jan17-en.mp3> Thank you. Kind regards, Michelle ------------------------------- Adobe Connect chat transcript for Monday, 30 January 2017 Michelle DeSmyter:Dear All, Welcome to the New gTLD Subsequent Procedures Working Group call on Monday, 30 January 2017 at 15:00 UTC. Michelle DeSmyter:Meeting page: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Kavouss Arasteh:Pls kindly advise to dial me up Kavouss Arasteh:Pls kindkly advise to dial me up Kavouss Arasteh:Kavouss Kavouss Arasteh:Pls kindly advise for dial up Kavouss Arasteh:Dear Stve Karen Day:avri you are very very quite Kavouss Arasteh:It is a headacke to attend this meeting$ Steve Chan:Kavouss, Michelle is having some AC issues. I've just let her know to provide you with a dial out. Vaibhav Aggarwal, NCSG:Hello Team Vaibhav Aggarwal, NCSG:Greetings Kavouss Arasteh 2:PLS PLS SPEAK SLOWLYT Vaibhav Aggarwal, NCSG:Excellent Point Vaibhav Aggarwal, NCSG::-) Kavouss Arasteh 2:NOISE Jeff Neuman:Sara, we will come back to you Jeff Neuman:Michael? Jeff Neuman:yes Vanda Scartezini:good morning from LA. I can stay just half hour - I am here fro an ICANN regional meeting that will start in half hour Jeff Neuman:Terms of Use Jeff Neuman:for the Application Kavouss Arasteh 2:Terms and Conditions on what pls ? Jeff Neuman:Module 6 of the Applicant Guidebook Kavouss Arasteh 2:Then we should say that Sara Bockey:i hear a fax Jeff Neuman:This has been a test of the emergency broadcast system Rubens Kuhl:Karen, you need to rewind a little. Jeff Neuman:Someone is breathing heavy on the phone Robin Gross:sounds good, thanks! Susan Payne:thanks! Kavouss Arasteh 2:I prefer e-mail. I have difficulties to read Google Doc. Jeff Neuman:nope Jim Prendergast:yes Phil Buckingham:If WT2 participants could fill out the doodle poll on a suggested time change ( after our next call 2 February ) - that would be much appreciated. . Michael and myself would prefer a later time than the current 20.00 UTC - up to 24.00 UTC on alternate Thursdays . Please put you suggestions to the list ..Thks . Kavouss Arasteh 2:May we take it Pra. by Pra. pls Jon Nevett:The application fee question seems to be pretty leading imo Vanda Scartezini:agree Kavouss Arasteh 2:What is the criteria to decide or identify who is middle applicant Vanda Scartezini: yes Kavouss - i will need to leave for another meeting here in ICANN - will read it later on. have a productive meeting Phil Buckingham:so is the cost ( recovery ) to be flexed according to the number of applications ? Phil Buckingham:it is a cart before the horse scenario Sara Bockey:Sure, no problem Jon Nevett:take out the givens Jon Nevett:but happy to do it offline Jon Nevett:sounds good Jon Nevett:you got it Kavouss Arasteh 2:Should there be some sort of periodical review of cost recovery value Steve Chan:@Jeff, maybe we could ask a question related to Phil's question re: the unknown number of incoming applications? Rubens Kuhl:I think the recurring fees is more of a deterrance to squatting than application fees, unless they move into 7-digits. Jeff Neuman:All good questions to add Trang Nguyen:A reminder that a portion of the $185K was allocated to the risk fund. Whatever the method to be used in the future should consider how the risk fund should be accounted for. Rubens Kuhl:It seems that part of the users are connected to others with a high delay. Quite possibly the AC to phone bridge link. Alexander.gay:Please also factor in "abuse": Porfolio applicants will simply form shell companies in "developing countries" to save fees! Kavouss Arasteh 2:THere is more than one cost recovery model as well as more than one method on how to calculate cost recovery fees Alexander.gay:The lottery could be BUILT IN by a random number assignment during aplication! Alexander.gay:*application Steve Chan:Channeling ICANN legal, I would suggest using a different word than lottery. Jeff Neuman:@steve....how about "sweepstakes" :) Vaibhav Aggarwal, NCSG:Shell Companies need to go through Veetting process of the APplicant Vaibhav Aggarwal, NCSG:that is already part of the process Vaibhav Aggarwal, NCSG:@jeff :-) Steve Chan:As long as it's not lottery and is able to be legally supported by ICANN, sure! :) Rubens Kuhl:Alexander, that can be dealt with by defining registration restrictions that larger operators wouldn't like. If applicant support requires not selling to registrants in OECD countries, (Spec 12 Registration Restrictions, as for Community TLDs), no commercial interest doing so. Alexander.gay:90 Alexander.gay:In my opinion the period of actual application acceptance doesn't really matter. What matters is that there is sufficient time to create a meaningful application once the deadline is announced! Donna Austin, Neustar:Application Submission Period may want to include questions about advertising the submission period. Donna Austin, Neustar:Correct Jeff Alexander.gay:The portfolio applicants can churn out run of the mill applications within 24h. But if we want MEANINGFUL applications by for example geo entities or communities: They need time to put togeher consensus policy! Steve Chan:@Kavouss., I've updated the header from "WT" to "Work Track" in the Google document Vaibhav Aggarwal, NCSG:Appologies have to rush for another meeting. will catch up on the notes :-) Vaibhav Aggarwal, NCSG:Have a good One Kavouss Arasteh 2:Avri, are we on section 3 pls Sara Bockey:Kavouss you are a bit muffled. Can you speak louder? Steve Chan:Staff will make sure the questions are provided in the same place (e.g., in the table above or in the Annex) Rubens Kuhl:A possible question would be on possible implementations of community priority. Priority can be different from death warrants for non-community applicants. Cheryl Langdon-Orr (CLO):comments only open until EOM for WT4 Rubens Kuhl:Tks Kavouss. Cheryl Langdon-Orr (CLO):BYE Katrin Ohlmer, DOTZON:Bye, all - see/hear next time. Sara Bockey:thanks all!

1 0

Actions/Discussion Notes: New gTLD Subsequent Procedures PDP Meeting 30 January 2017
by Emily Barabas Jan. 30, 2017

Jan. 30, 2017

Dear working group members, Please see below the action items and discussion notes captured by staff from the meeting on 30 January. These high-level notes are designed to help working group members navigate through the content of the call and are not a substitute for the transcript or the recording. See the chat record, call transcript, and recording at: https://community.icann.org/x/krHDAw. Kind regards, Emily Agenda: 1. Welcome/Review Agenda 2. SOIs 3. WT Updates 4. Overarching Issues/CC1 – Update/Next steps 5. CC2 discussion (Working document here: https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLsMHKkNczR_b6-jH2Wl5eVH…<https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLsMHKkNczR_b6-jH2Wl5eVH…> ) 6. AOB Action Items: 1. Staff will circulate PDF version of CC2 document Notes: 3. Work Track Updates WT1 -- Application queuing, submission period, and variable fees discussed -- Move on to systems, communications, and CC2 questions WT2 -- Wrapped up initial discussions for registrant protections, but will look to continue this conversation (e.g., background check) -- Will look at Terms & Conditions from Module 6 of the AGB -- Will discuss CC2 draft questions -- Michael to resend discussion materials WT3 -- Discussing objections, particularly around legal rights objections (straw man) -- Applicant freedom of expression will be discussed on next WT call -- CC2 questions already circulated and looking for input WT4 -- CC2 questions discussed on last meeting, please provide any input/feedback ASAP -- Next WT is 9 Feb, will primarily discuss IDNs 4. Overarching issues/CC1 -- Will circulate call for volunteers for 3 drafting teams. Please volunteer if you're interested or have anything you'd like to provide. -- Drafting teams will be flexible (e.g., calls, emails, collaborative documents) -- Drafting teams related to different TLD types, predictability, and rounds 5. CC2 discussion WT1 -- Accreditation programs - leadership does not anticipate needing CC2 questions on this topic -- Applicant support - this question should be clarified. Why does the question focus on the "middle applicant" and what is the origin of this concept? -- This concept came up during an APAC session in Hyderabad as a way to expand the program. -- How is the middle applicant defined? This has not yet been determined and would need to be discussed further. -- The idea of the middle applicant was not to exclude underserved regions but to add to the existing program. -- Application fees - is the question too leading as it is currently framed? How can it be phrased more objectively? Consider removing clauses beginning with the word “given.” -- Variable fees - additional clarity needed on the one-fee-fits-all model mentioned in the question. -- Application queuing – Steve Chan (from the chat): Channeling ICANN legal, I would suggest using a different word than lottery. -- Application submission period – consider listing application submission period question before application queuing. Consider listing the three distinct options under application submission period. -- Donna Austin, Neustar (from the chat): Application Submission Period may want to include questions about advertising the submission period. -- Response: this may best fit under CC2 section on communications. -- Suggestion - repeat header on each page to make clear that the left column contains WT numbers. -- Suggestion - add space for general comments in CC2. WT2 -- The group will be working on developing questions in its meeting this week. WT3 -- Additional questions will be developed in the upcoming call. -- Clarify the term "game" in question 1. -- In question 2, ask why the respondent does or does not support the use of an Independent Objector in future rounds. -- Question 5 may be leading and should be phrased in a neutral manner. -- Should question 5 and 6 be a single question or two questions? -- The group may want to add a question (or multiple questions) about auctions under Work Track 3. WT4 -- The proposed questions have been in circulation for some time. Leadership would like to finalize them asap and encourages final comments in the Google Doc before end of January. Rubens Kuhl (from the chat): A possible question would be on possible implementations of community priority. Priority can be different from death warrants for non-community applicants. 6. AOB - None Emily Barabas | Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0