December 2017 - Gnso-newgtld-wg

Re: [Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP Working Group - 11 December 2017
by Emily Barabas Jan. 15, 2018

Jan. 15, 2018

Dear Working Group members, On the 11 December Working Group call, the co-chairs invited Working Group members to provide input on two items over the mailing list. This note serves as a reminder of the issues for which they are seeking comments. On the call, the WG reviewed the status of conversations regarding potential TLD types/categories for subsequent procedures (https://docs.google.com/spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJffzJ…) Your input is encouraged on the following questions: * Is it critical to carve out exceptions for some of the identified types? If so, what are the pros/cons for carving out specific mechanisms to accommodate any of the proposed types? * If there are critical exceptions needed for any of the proposed types, please help identify what they might be (e.g., applicant eligibility criteria, evaluation criteria/process, contractual requirements, etc.). The WG touched briefly on the Framework for Predictability (https://docs.google.com/document/d/1lzXxBLMtFr03BKnHsa-Ss7kR7EAJt7pCI1EP3H8…) which is intended to balance ICANN Org’s ability to operate in an effective manner while ensuring the community is properly consulted when issues arise. Your input is requested on the following:   * What are some use cases we can apply against the framework to test how it would work in practice? For background, please see the attached slides for the call. In order to help the Working Group progress deliberations on this topic, please share your thoughts on the mailing list prior to the next full Working Group call on 8 January 2018. Kind regards, Emily From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces(a)icann.org> on behalf of Emily Barabas <emily.barabas(a)icann.org> Date: Monday 11 December 2017 at 12:11 To: "gnso-newgtld-wg(a)icann.org" <gnso-newgtld-wg(a)icann.org> Subject: [Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP Working Group - 11 December 2017 Dear Working Group members, Please find below notes and action items from the call today. 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 chat transcript or the recording. The call recording, call transcript, and chat transcript will soon be available here: https://community.icann.org/x/SQxyB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. Some excerpts from the chat room are included in the notes. Please see the chat transcript for a full record of chat comments. Slides are attached for reference. Kind regards, Emily ACTION ITEM: Co-Chairs will contact Ombudsman regarding concerns raised on this call. 1. SOI Updates - no updates 2. Work Track Updates - Work Track 1 - next call on 19 Dec will cover systems, communications, and application queuing - Work Track 2 - There was a WT2 call last week which covered Contractual Compliance and TLD Rollout and CC2 comments on these topics. The next call is 21 December - the call will focus on reviewing strawman recommendations prepared by the co-leads. - Work Track 3 - Next meeting is on 12 December at 15:00 UTC. WT3 will discuss Community Applications and Objections. - Work Track 4 - Next meeting will be 14 December at 3:00 UTC. The call will focus on the applicant reviews with a focus on applicant financial models. - Work Track 5 - WT5 had a meeting last Wednesday in which it discussed the Terms of Reference. In the next meeting on 20 December, the WT will do a second reading on the TOR document. - Some GAC members were surprised by the response to the GAC conditions for participation in WT5. The GAC may provide a response on this issue. - Request to return to issue of participation model contained in the Terms of Reference on the upcoming call. - Additional work will need to be done to come to agreement on the Terms of Reference. - There is a single Chartering Organization in the PDP, which is the GNSO. Measures have been put into place to ensure that all voices are heard in WT5. Chat excerpt: kavouss Arasteh: I do not agree with your conclusions kavouss Arasteh: The issue of Georaphic name isc much beyound the leadership of GNSO kavouss Arasteh: The issue is disagreement on whether PDP is relevant here kavouss Arasteh: There seems to be that our concerns are not heard Greg Shatan: This is a GNSO PDP Working Group. That is a fundamental fact. The issue of gTLD policy is the raisin d’etre for the GNSO. kavouss Arasteh: It is a cross community issue and not GNSO issue Greg Shatan: That is certainly your opinion, and thank you for your personal views. kavouss Arasteh: I am speaking from my own side here Robin Gross: We need to follow the rules, not break them in order to privilege one of the groups that isn't happy with them. kavouss Arasteh: WHAT Rules Dear Mdam kavouss Arasteh: MADAM' Maxim Alzoba (FAITID ): in any case GEO TLDs had to obtain letter of approval from the relevant local/federal governmental body Greg Shatan: Robin, we don’t know that any group is asking for that. Only a single member of a group. Maxim Alzoba (FAITID ): or letter of non objection from the same governmental body kavouss Arasteh: It is not surprising that you want the domination of GNSO with its PDP Rules to be applied to Geographic names Steve Chan: As referenced by Cheryl, GNSO Operating Procedures, which are inclusive of the GNSO Working Group Guidelines and PDP Manual: https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf[gnso.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> kavouss Arasteh: Geographic names are not the property of any group. It belongs to the citizen of all countries Greg Shatan: Cheryl is a member of ALAC. Not sure how that contributes to anyone’s lack of surprise. Martin Sutton: @ Kavous - the GNSO is the vehicle for addressing the policy issue but allows all to be involved. All concerns and views are taken into consideration. Ultimately, all of the 4 leading groups and other advisory groups will have further opportunities to comment on any output from WT5. Greg Shatan: Kavouss, your personal views on that matter have been amply stated and heard. kavouss Arasteh: Dear Greg, we have difference of view in that subject - The unique nature of WT5 was designed to provide leadership balance in recognition of the importance of this issue in different parts of the community 3. Overarching Issue: Application Types - Status Quo - Different Types in 2012: Standard application, community-based application, geographic names, specification 13 (.Brand) Chat excerpt: Kurt Pritz: I think we might distinquish between the policy-based (i.e., in the Guidebook) categories: Community and Geographic; vs thise that were inserted via independent discussion afterward: Donna Austin, Neustar: Can we spell out NGPC please for some that weren't around in 2012 Steve Chan: NGPC = New gTLD Program Committee. Thanks Donna for the reminder. Heather Forrest: I agree that it is sensible to make the distinction that Kurt has raised between community policy-based and independent agreement kavouss Arasteh: There is no clear description on community kavouss Arasteh: If there is what is that? kavouss Arasteh: There is nalso no clear idea on how communities requirements to be compared with each other Kurt Pritz: My point earlier was that there is consensus policy on geo and Community categories and no consensus policy on closed generics and brands so the latter "categories" deseverve more discussion and should not be considered a status quo consensus policy - Work Track related efforts: WT2 is considering Closed Generics, WT3 is considering Community applications, and WT5 is considering Geographic Names - On slide 6, AGB section 2.2.1.4.2 is mentioned in the slides, but additional sections of the AGB also address geographic names, and these will also fall within the scope of WT5 discussions. Chat excerpt: kavouss Arasteh: Could one consider drug traffic group as a community?i Jim Prendergast: While we did have some lenghty disucssions on closed generics in WT2, there is still some healthy oppostion to the concept so I dont know how settled that issue is. Robin Gross: I suppose a pharmacy group could apply as a community. kavouss Arasteh: Those issues were written some 10 years ago and situation has changed drastically Maxim Alzoba (FAITID ): AGB might change as result f some PDP work Marc Palau: What about family names? that's not an strict community Marc Palau: like .kim Steve Chan: @Kavouss, the description of the AGB was to set the stage and to identify what took place in the 2012 round. As Maxim notes, things can change in the future as a result of the work of this PDP. Maxim Alzoba (FAITID ): it might depend on wealth of the family Greg Shatan: @Maxim, exactly; that is why this PDP exists.... kavouss Arasteh: Dear Colleagues, I am eligible to raise questions without being criticized or repressed is it not so? avri doria: Aren't there also other conditions in the AGB against crimminal behaviors and activities? kavouss Arasteh: We need to revisit the definition of community and revist various categories of communioties as they are not having the same conditions Maxim Alzoba (FAITID ): I think GAC advise might play it's role irto prevent such bad actor's communities kavouss Arasteh: As soon as we raise a legitimate question , an valanch of disagreement comes up without giving a convincing argument - Work Track 3 is still working to define community. One thing we can say confidently is that however we define community, it will need to be in support of the public interest. - There are conditions in the AGB against criminal activities. - If there is no consensus on recommendations for change in this PDP, the status quo remains. - Review of attributes for current application types. - Null Hypothesis: If we changed nothing in the approach to categories in the AGB for Subsequent Procedures, would there be a problem? - We may not need new categories, but there may need to be tweaks to the AGB regarding the relevant sections of the guidebook - .Brands are not in consensus policy, for example, so we would need to tidy that up. Discussions on Closed Generics are still underway. Chat excerpt: Kurt Pritz: If we change nothing in the Guidebook, there are no brand TLDs and no restrictions on closed generics - there is no consensus policies on these Greg Shatan: @Kurt, why would keeping the status quo AGB result in changes in implementation? Greg Shatan: We can add those to consensus policy, but the lack of consensus policy doesn’t roll back implementation. - . Brands are not covered in previous policy, so we would need to work that into future application processes Chat excerpt: Kurt Pritz: @ Greg: Are you advocating that the GB remail silent on Brands and closed generics but conducting the round in the same way? Kurt Pritz: I agree with Martin - the next round must encourage innovation by developing a flexible approach to accommodating new models Kurt Pritz: I think categorization is rigid and exclusionary (is that a word) Martin Sutton: Good point Donna - I agree that innovation should not be stifled through categorisation where it is not needed Christopher Wilkinson: @AGB It is already clear that the definition of Geo-Names and associated decision making policies will have to evolve - It is important to reflect on what we witnessed in the 2012 Round. We cannot predict everything. For any new types that emerge, there will be an opportunity to evolve the system, but it is difficult to predict this now. - We should also include generic as a category. It is intentionally broad. There were some things that happened after the application process closed that had an impact, and additional restrictions put in place following GAC Advice. There was no harm done by not having additional categories. - The GAC Advice could have been viewed as restrictive and reduced innovation - If we create too many rules or parameters around categories, we could further stifle innovation. We don't want to do that. -Slide 12: Preliminary List of Types (beyond existing) - Wouldn't it possible to address differences in different applications through specifications to the base agreement rather than creating categories, since these categories may have overlapping requirements. This seems to be a simpler approach. Are there any issues with this approach? Chat excerpt: Robin Gross: 4 seems to lump two different groups together. Highly regulated industries have nothing to do with words that others may be "sensitive" to hearing. Steve Chan: @Robin, I believe that lumping together carries from GAC Advice. That of course would not prevent this WG from decoupling the two types. Robin Gross: Thanks, Steve. I think we wouldn't want to lump them together. Kurt Pritz: With regards to status quo and Cheryl’s mantra that if we don’t arrive at a consensus for change, we are left to the stars quo: we don’t have a policy on brands and closed generics and they are not in the Guidebook. It is not that I am against Brand TLDs, it is that I think the accommodations provided brands could also be afforded that don’t own trademarks but that deserve and need them for there business model. This should be discussed as a consensus policy - Agree that there may be different applications that warrant different provisions that might not upset the existing policy. It is possible to provide accommodations as needed for applications where it is appropriate. Chat excerpt: kavouss Arasteh: I am referring to decision making process in Geo Names kavouss Arasteh: Is there any hope that such concerns be addressed? Donna Austin, Neustar: @Kavouss, it would be great if you could give the process a chance. Annebeth Lange,WT5: The problem, Kavouss, as I see it, is that GNSO, according to the bylaws of ICANN. is responsible for the new gTLD policy. So how to have a "true" cross community PDP, I am not sure how we can achieve this under the present bylaws. However, we should try to trust the process and see what can be achieved. Donna Austin, Neustar: @Annebeth, WT5 is a pro-active attempt to have a true cross community PDP and it is truly appreciated that the SO/ACs have responded positively to the request to participate. Annebeth Lange,WT5: *Donna, I agree. However, even if that is what is the intention, still many do not feel that it is a "true" CCWG. I trust the process, but there is still a feeling of "someone matters more than others" out there, unfortunately. Donna Austin, Neustar: @Annebeth, appreciate your thoughts and hopefully we can work together to dispell the myths. - One of the challenges is that there are 8 potential types of TLDs in the slides, and there would be more with geo, communities, and brands. If you develop different policies for each type, the administration will be significant. It will be harder to move through the process in a streamlined manner. It is also difficult on the backend for contractual compliance. Should the group consider the value, what are we trying to achieve, and what the potential impact will be. - The hope is that the full group conversation will provide additional input to the WTs that are considering some of the questions around categorization - Future Application Types - Potential Attributes (slide 13) - Attributes Matrix (slides 14, 15, 16) - Pros and Cons of categorization in general (slide 17) - Homework (slide 18): Share on the list if you believe it is critical to carve out exceptions for some of the identified types. WG members can help to identify pros/cons for specific proposed types and identify critical exceptions for specific proposed types - More homework (slide 20): WG members are encouraged to prposed use cases to test the predictability framework. . AOB - none Emily Barabas | Senior Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

14 16

FW: [Gnso-newgtld-wg-wt3] FW: Letter on behalf of FIP
by Steve Chan Dec. 21, 2017

Dec. 21, 2017

Dear WG Members, Attached, please see a letter sent to Work Track 3 and shared with the group on 19 Dec 2017. Please note, we’ve established a New gTLD Subsequent Procedures Correspondence page where this and future correspondence to this PDP WG can be made available: https://community.icann.org/x/3B5yB Best, Steve From: Gnso-newgtld-wg-wt3 <gnso-newgtld-wg-wt3-bounces(a)icann.org> on behalf of Karen Day <Karen.Day(a)sas.com> Date: Tuesday, December 19, 2017 at 10:26 AM To: "gnso-newgtld-wg-wt3(a)icann.org" <gnso-newgtld-wg-wt3(a)icann.org> Subject: [Gnso-newgtld-wg-wt3] FW: Letter on behalf of FIP Dear Work Track 3 Members, Please see the attached letter which we have received this morning for your consideration into our work. Best regards, Karen From: Rachel van Kesteren [mailto:Rachel@fip.org] Sent: Tuesday, December 19, 2017 7:03 AM To: Karen Day <Karen.Day(a)sas.com>; robin(a)ipjustice.org Cc: CEO@fip <ceo(a)fip.org>; President <president(a)fip.org>; Carola van der Hoeff <Carola(a)fip.org>; Thomas Menighan <tmenighan(a)aphanet.org> Subject: Letter on behalf of FIP EXTERNAL Dear Ms Day and Ms Gross, Please find attached a letter on behalf of Ms Ema Paulino, Interim CEO. Kind regards, Rachel [fip.org] [facebook.com][linkedin.com][twitter.com][youtube.com] Rachel van Kesteren | Executive Secretary International Pharmaceutical Federation (FIP) Andries Bickerweg 5 | 2517 JP | The Hague | The Netherlands Tel: +31 70 302 1971 | Fax: +31 70 302 1999 Email:Rachel@fip.org Website[fip.org] | Pharmacy Event Calendar[fip.org] | Publications[fip.org] Website[fip.org] | Programme[fip.org] | Press & Media[fip.org] | Glasgow[fip.org] Join us on 2 September - 6 September 2018, Glasgow Website | Programme | Press & Media | Geneva Join us on 19 May - 20 May 2018, Geneva World Health Professions Regulation Conference 2018 The International Pharmaceutical Federation (FIP) is the global federation of 140 national organisations of pharmacists and pharmaceutical scientists dedicated to improving the access to and value of appropriate medicine use, and contributing to changes in science, practice and health policies worldwide. FIP represents over four million pharmacists and pharmaceutical scientists worldwide and endeavors to advance the role of the pharmacist through such partnerships as our official NGO status with the World Health Organization (WHO).

1 0

ICANN News Alert -- ICANN Organization Publishes Reports on the Review of the Community Priority Evaluation Process
by Steve Chan Dec. 14, 2017

Dec. 14, 2017

Dear WG Members, Relevant to this WG and especially Work Track 3, please find the link below to the reports on the review of the Community Priority Evaluation process. Many of you will already be aware of these report, and those subscribed to the WT3 list will have also just been reminded there as well, so apologies for the possible multiple notifications. Best, Steve From: ICANN News Alert <no-reply(a)external.icann.org> Reply-To: "no-reply(a)external.icann.org" <no-reply(a)external.icann.org> Date: Wednesday, December 13, 2017 at 7:21 PM To: Steve Chan <steve.chan(a)icann.org> Subject: [Ext] ICANN News Alert -- ICANN Organization Publishes Reports on the Review of the Community Priority Evaluation Process [icann.org] News Alert https://www.icann.org/news/announcement-2017-12-13-en[icann.org] ICANN Organization Publishes Reports on the Review of the Community Priority Evaluation Process 13 December 2017 LOS ANGELES – 13 December 2017 – The Internet Corporation for Assigned Names and Numbers (ICANN) today published three reports on the review of the Community Priority Evaluation (CPE) process (the CPE Process Review). The CPE Process Review was initiated at the request of the ICANN Board as part of the Board's due diligence in the administration of the CPE process. The CPE Process Review was conducted by FTI Consulting Inc.'s (FTI)[fticonsulting.com] Global Risk and Investigations Practice (GRIP) and Technology Practice, and consisted of three parts: (i) reviewing the process by which the ICANN organization interacted with the CPE Provider related to the CPE reports issued by the CPE Provider (Scope 1); (ii) an evaluation of whether the CPE criteria were applied consistently throughout each CPE report (Scope 2); and (iii) a compilation of the reference material relied upon by the CPE Provider to the extent such reference material exists for the eight evaluations which are the subject of pending Reconsideration Requests that were pending at the time that ICANN initiated the CPE Process Review (Scope 3). FTI concluded that "there is no evidence that the ICANN organization had any undue influence on the CPE Provider with respect to the CPE reports issued by the CPE Provider or engaged in any impropriety in the CPE process" (Scope 1) and that "the CPE Provider consistently applied the criteria set forth in the New gTLD Applicant Guidebook [ ] and the CPE Guidelines throughout each CPE" (Scope 2). (See Scope 1 report[icann.org] [PDF, 159 KB], Pg. 3; Scope 2 report[icann.org] [PDF, 312 KB], Pg. 3.) For Scope 3, FTI observed that two of the eight relevant CPE reports included a citation in the report for each reference to research. In the remaining six reports, FTI observed instances where the CPE Provider referenced research but did not include the corresponding citations in the reports. Except for one evaluation, FTI observed that the working papers underlying the reports contained material that corresponded with the research referenced in the CPE reports. In one instance, FTI did not find that the working papers underlying the relevant report contained citation that corresponded with the research referenced in the CPE report. However, based on FTI's observations, it is possible that the research being referenced was cited in the CPE Provider's working papers underlying the first evaluation of that application. (See Scope 3 report[icann.org] [PDF, 309 KB], Pg. 4.) The findings will be considered by the Board Accountability Mechanisms Committee (BAMC) when the BAMC reviews the remaining pending Reconsideration Requests as part of the Reconsideration process. "The Board appreciates the community's patience during this detailed investigation, which has provided greater transparency into the CPE evaluation process," said Cherine Chalaby, Chairman of the ICANN Board. "Further, this CPE Process Review and due diligence has provided additional facts and information that outline and document the ICANN organization's interaction with the CPE Provider." For more information about the CPE process and the CPE Process Review, please visit https://newgtlds.icann.org/en/applicants/cpe[newgtlds.icann.org]. This message was sent to steve.chan(a)icann.org from no-reply(a)external.icann.org ICANN News Alert ICANN 12025 Waterfront Drive Suite 300 Los Angeles, CA 90094-2536 [icontact.com] Manage Your Subscription [app.icontact.com]

1 0

Recordings, attendance & AC chat from New gTLD Subsequent Procedures Working Group call on Monday, 11 December 2017
by Michelle DeSmyter Dec. 13, 2017

Dec. 13, 2017

Dear All, Please find the attendance of the call attached to this email and the AC Recording, MP3 recording, and AC Chat below for the New gTLD Subsequent Procedures Working Group call held on Monday, 11 December 2017 at 15:00 UTC. Attendance of the calls is also posted on the agenda wiki page: https://community.icann.org/x/SQxyB MP3: https://audio.icann.org/gnso/gnso-new-gtld-subsequent-11dec17-en.mp3 AC Recording: https://participate.icann.org/p5vmano7bhh/ 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/ Thank you. Kind regards, Michelle

3 2

Notes and Action Items - New gTLD Subsequent Procedures PDP Working Group - 11 December 2017
by Emily Barabas Dec. 11, 2017

Dec. 11, 2017

Dear Working Group members, Please find below notes and action items from the call today. 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 chat transcript or the recording. The call recording, call transcript, and chat transcript will soon be available here: https://community.icann.org/x/SQxyB. Some excerpts from the chat room are included in the notes. Please see the chat transcript for a full record of chat comments. Slides are attached for reference. Kind regards, Emily ACTION ITEM: Co-Chairs will contact Ombudsman regarding concerns raised on this call. 1. SOI Updates - no updates 2. Work Track Updates - Work Track 1 - next call on 19 Dec will cover systems, communications, and application queuing - Work Track 2 - There was a WT2 call last week which covered Contractual Compliance and TLD Rollout and CC2 comments on these topics. The next call is 21 December - the call will focus on reviewing strawman recommendations prepared by the co-leads. - Work Track 3 - Next meeting is on 12 December at 15:00 UTC. WT3 will discuss Community Applications and Objections. - Work Track 4 - Next meeting will be 14 December at 3:00 UTC. The call will focus on the applicant reviews with a focus on applicant financial models. - Work Track 5 - WT5 had a meeting last Wednesday in which it discussed the Terms of Reference. In the next meeting on 20 December, the WT will do a second reading on the TOR document. - Some GAC members were surprised by the response to the GAC conditions for participation in WT5. The GAC may provide a response on this issue. - Request to return to issue of participation model contained in the Terms of Reference on the upcoming call. - Additional work will need to be done to come to agreement on the Terms of Reference. - There is a single Chartering Organization in the PDP, which is the GNSO. Measures have been put into place to ensure that all voices are heard in WT5. Chat excerpt: kavouss Arasteh: I do not agree with your conclusions kavouss Arasteh: The issue of Georaphic name isc much beyound the leadership of GNSO kavouss Arasteh: The issue is disagreement on whether PDP is relevant here kavouss Arasteh: There seems to be that our concerns are not heard Greg Shatan: This is a GNSO PDP Working Group. That is a fundamental fact. The issue of gTLD policy is the raisin d’etre for the GNSO. kavouss Arasteh: It is a cross community issue and not GNSO issue Greg Shatan: That is certainly your opinion, and thank you for your personal views. kavouss Arasteh: I am speaking from my own side here Robin Gross: We need to follow the rules, not break them in order to privilege one of the groups that isn't happy with them. kavouss Arasteh: WHAT Rules Dear Mdam kavouss Arasteh: MADAM' Maxim Alzoba (FAITID ): in any case GEO TLDs had to obtain letter of approval from the relevant local/federal governmental body Greg Shatan: Robin, we don’t know that any group is asking for that. Only a single member of a group. Maxim Alzoba (FAITID ): or letter of non objection from the same governmental body kavouss Arasteh: It is not surprising that you want the domination of GNSO with its PDP Rules to be applied to Geographic names Steve Chan: As referenced by Cheryl, GNSO Operating Procedures, which are inclusive of the GNSO Working Group Guidelines and PDP Manual: https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf[gnso.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> kavouss Arasteh: Geographic names are not the property of any group. It belongs to the citizen of all countries Greg Shatan: Cheryl is a member of ALAC. Not sure how that contributes to anyone’s lack of surprise. Martin Sutton: @ Kavous - the GNSO is the vehicle for addressing the policy issue but allows all to be involved. All concerns and views are taken into consideration. Ultimately, all of the 4 leading groups and other advisory groups will have further opportunities to comment on any output from WT5. Greg Shatan: Kavouss, your personal views on that matter have been amply stated and heard. kavouss Arasteh: Dear Greg, we have difference of view in that subject - The unique nature of WT5 was designed to provide leadership balance in recognition of the importance of this issue in different parts of the community 3. Overarching Issue: Application Types - Status Quo - Different Types in 2012: Standard application, community-based application, geographic names, specification 13 (.Brand) Chat excerpt: Kurt Pritz: I think we might distinquish between the policy-based (i.e., in the Guidebook) categories: Community and Geographic; vs thise that were inserted via independent discussion afterward: Donna Austin, Neustar: Can we spell out NGPC please for some that weren't around in 2012 Steve Chan: NGPC = New gTLD Program Committee. Thanks Donna for the reminder. Heather Forrest: I agree that it is sensible to make the distinction that Kurt has raised between community policy-based and independent agreement kavouss Arasteh: There is no clear description on community kavouss Arasteh: If there is what is that? kavouss Arasteh: There is nalso no clear idea on how communities requirements to be compared with each other Kurt Pritz: My point earlier was that there is consensus policy on geo and Community categories and no consensus policy on closed generics and brands so the latter "categories" deseverve more discussion and should not be considered a status quo consensus policy - Work Track related efforts: WT2 is considering Closed Generics, WT3 is considering Community applications, and WT5 is considering Geographic Names - On slide 6, AGB section 2.2.1.4.2 is mentioned in the slides, but additional sections of the AGB also address geographic names, and these will also fall within the scope of WT5 discussions. Chat excerpt: kavouss Arasteh: Could one consider drug traffic group as a community?i Jim Prendergast: While we did have some lenghty disucssions on closed generics in WT2, there is still some healthy oppostion to the concept so I dont know how settled that issue is. Robin Gross: I suppose a pharmacy group could apply as a community. kavouss Arasteh: Those issues were written some 10 years ago and situation has changed drastically Maxim Alzoba (FAITID ): AGB might change as result f some PDP work Marc Palau: What about family names? that's not an strict community Marc Palau: like .kim Steve Chan: @Kavouss, the description of the AGB was to set the stage and to identify what took place in the 2012 round. As Maxim notes, things can change in the future as a result of the work of this PDP. Maxim Alzoba (FAITID ): it might depend on wealth of the family Greg Shatan: @Maxim, exactly; that is why this PDP exists.... kavouss Arasteh: Dear Colleagues, I am eligible to raise questions without being criticized or repressed is it not so? avri doria: Aren't there also other conditions in the AGB against crimminal behaviors and activities? kavouss Arasteh: We need to revisit the definition of community and revist various categories of communioties as they are not having the same conditions Maxim Alzoba (FAITID ): I think GAC advise might play it's role irto prevent such bad actor's communities kavouss Arasteh: As soon as we raise a legitimate question , an valanch of disagreement comes up without giving a convincing argument - Work Track 3 is still working to define community. One thing we can say confidently is that however we define community, it will need to be in support of the public interest. - There are conditions in the AGB against criminal activities. - If there is no consensus on recommendations for change in this PDP, the status quo remains. - Review of attributes for current application types. - Null Hypothesis: If we changed nothing in the approach to categories in the AGB for Subsequent Procedures, would there be a problem? - We may not need new categories, but there may need to be tweaks to the AGB regarding the relevant sections of the guidebook - .Brands are not in consensus policy, for example, so we would need to tidy that up. Discussions on Closed Generics are still underway. Chat excerpt: Kurt Pritz: If we change nothing in the Guidebook, there are no brand TLDs and no restrictions on closed generics - there is no consensus policies on these Greg Shatan: @Kurt, why would keeping the status quo AGB result in changes in implementation? Greg Shatan: We can add those to consensus policy, but the lack of consensus policy doesn’t roll back implementation. - . Brands are not covered in previous policy, so we would need to work that into future application processes Chat excerpt: Kurt Pritz: @ Greg: Are you advocating that the GB remail silent on Brands and closed generics but conducting the round in the same way? Kurt Pritz: I agree with Martin - the next round must encourage innovation by developing a flexible approach to accommodating new models Kurt Pritz: I think categorization is rigid and exclusionary (is that a word) Martin Sutton: Good point Donna - I agree that innovation should not be stifled through categorisation where it is not needed Christopher Wilkinson: @AGB It is already clear that the definition of Geo-Names and associated decision making policies will have to evolve - It is important to reflect on what we witnessed in the 2012 Round. We cannot predict everything. For any new types that emerge, there will be an opportunity to evolve the system, but it is difficult to predict this now. - We should also include generic as a category. It is intentionally broad. There were some things that happened after the application process closed that had an impact, and additional restrictions put in place following GAC Advice. There was no harm done by not having additional categories. - The GAC Advice could have been viewed as restrictive and reduced innovation - If we create too many rules or parameters around categories, we could further stifle innovation. We don't want to do that. -Slide 12: Preliminary List of Types (beyond existing) - Wouldn't it possible to address differences in different applications through specifications to the base agreement rather than creating categories, since these categories may have overlapping requirements. This seems to be a simpler approach. Are there any issues with this approach? Chat excerpt: Robin Gross: 4 seems to lump two different groups together. Highly regulated industries have nothing to do with words that others may be "sensitive" to hearing. Steve Chan: @Robin, I believe that lumping together carries from GAC Advice. That of course would not prevent this WG from decoupling the two types. Robin Gross: Thanks, Steve. I think we wouldn't want to lump them together. Kurt Pritz: With regards to status quo and Cheryl’s mantra that if we don’t arrive at a consensus for change, we are left to the stars quo: we don’t have a policy on brands and closed generics and they are not in the Guidebook. It is not that I am against Brand TLDs, it is that I think the accommodations provided brands could also be afforded that don’t own trademarks but that deserve and need them for there business model. This should be discussed as a consensus policy - Agree that there may be different applications that warrant different provisions that might not upset the existing policy. It is possible to provide accommodations as needed for applications where it is appropriate. Chat excerpt: kavouss Arasteh: I am referring to decision making process in Geo Names kavouss Arasteh: Is there any hope that such concerns be addressed? Donna Austin, Neustar: @Kavouss, it would be great if you could give the process a chance. Annebeth Lange,WT5: The problem, Kavouss, as I see it, is that GNSO, according to the bylaws of ICANN. is responsible for the new gTLD policy. So how to have a "true" cross community PDP, I am not sure how we can achieve this under the present bylaws. However, we should try to trust the process and see what can be achieved. Donna Austin, Neustar: @Annebeth, WT5 is a pro-active attempt to have a true cross community PDP and it is truly appreciated that the SO/ACs have responded positively to the request to participate. Annebeth Lange,WT5: *Donna, I agree. However, even if that is what is the intention, still many do not feel that it is a "true" CCWG. I trust the process, but there is still a feeling of "someone matters more than others" out there, unfortunately. Donna Austin, Neustar: @Annebeth, appreciate your thoughts and hopefully we can work together to dispell the myths. - One of the challenges is that there are 8 potential types of TLDs in the slides, and there would be more with geo, communities, and brands. If you develop different policies for each type, the administration will be significant. It will be harder to move through the process in a streamlined manner. It is also difficult on the backend for contractual compliance. Should the group consider the value, what are we trying to achieve, and what the potential impact will be. - The hope is that the full group conversation will provide additional input to the WTs that are considering some of the questions around categorization - Future Application Types - Potential Attributes (slide 13) - Attributes Matrix (slides 14, 15, 16) - Pros and Cons of categorization in general (slide 17) - Homework (slide 18): Share on the list if you believe it is critical to carve out exceptions for some of the identified types. WG members can help to identify pros/cons for specific proposed types and identify critical exceptions for specific proposed types - More homework (slide 20): WG members are encouraged to prposed use cases to test the predictability framework. . AOB - none Emily Barabas | Senior Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

Proposed Agenda: New gTLD Subsequent Procedures Working Group, 11 December 2017
by Emily Barabas Dec. 8, 2017

Dec. 8, 2017

Dear Working Group Members, Below, please find the proposed agenda for the New gTLD Subsequent Procedures Working Group meeting scheduled for Monday 11 December at 15:00 UTC. Please note, this call is scheduled for 90 minutes. 1. Welcome/Agenda Review/SOI Updates 2. Work Track Updates 3. Overarching Issue: Application Types (https://docs.google.com/spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJffzJ… ) 4. Next Steps: Predictability Framework (https://docs.google.com/document/d/1lzXxBLMtFr03BKnHsa-Ss7kR7EAJt7pCI1EP3H8… ) 5. Any Other Business Kind regards, Emily Emily Barabas | Senior Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

Working Group Newsletter - December 2017
by Emily Barabas Dec. 6, 2017

Dec. 6, 2017

Dear Working Group members, The December edition of the New gTLD Subsequent Procedures PDP Working Group newsletter is now available: https://gnso.icann.org/en/news/working-group-newsletters/newsletter-new-gtl…. Please feel free to share this newsletter with individuals and groups who may be interested in the Working Group’s activities. An archive of previous editions of the newsletter is available on the WG wiki<https://community.icann.org/pages/viewpage.action?pageId=58001970> and on the GNSO website<https://gnso.icann.org/en/news/working-group-newsletters>. Kind regards, Emily Emily Barabas | Senior Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0