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

ICANN64: Schedule of New gTLD Subsequent Procedures PDP Working Group Meetings
by Julie Hedlund March 5, 2019

March 5, 2019

Dear Working Group members, Please see below the schedule and links for the New gTLD Subsequent Procedures PDP Working Group at ICANN64. See the full ICANN64 schedule at: https://64.schedule.icann.org/meetings. Best, Julie Julie Hedlund, Policy Director Kobe ICANN64: New gTLD Subsequent Procedures Working Group and Related Meetings (with remote participation in the links below): Working Group and Work Track 5 Meetings: GNSO - New gTLD Subsequent Procedures Work Track 5 (Geographic Names) (1 of 2) 9:00 - 10:15, Sat, Mar 9, 2019, Room: Diamond Description: https://64.schedule.icann.org/meetings/962038 Remote Participation: https://participate.icann.org/kix64-diamond GNSO - New gTLD Subsequent Procedures Work Track 5 (Geographic Names) (2 of 2) 10:30 - 12:00, Sat, Mar 9, 2019, Room: Diamond Description: https://64.schedule.icann.org/meetings/962039 Remote Participation: https://participate.icann.org/kix64-diamond GNSO - New gTLD Subsequent Procedures (1 of 3) 13:30 - 15:00, Sat, Mar 9, 2019, Room: Diamond Description: https://64.schedule.icann.org/meetings/962036 Remote Participation: https://participate.icann.org/kix64-diamond GNSO - New gTLD Subsequent Procedures (2 of 3) 15:15 - 16:45, Sat, Mar 9, 2019, Room: Diamond Description: https://64.schedule.icann.org/meetings/962037 Remote Participation: https://participate.icann.org/kix64-diamond GNSO - New gTLD Subsequent Procedures (3 of 3) 15:15 - 16:45, Wed, Mar 13, 2019, Room: Ohwada C (GNSO) Description: https://64.schedule.icann.org/meetings/961983 Remote Participation: https://participate.icann.org/kix64-ohwadac

1 0

Recordings, attendance & AC chat / New gTLD Subsequent Procedures Working Group call / Monday, 04 March 2019 at 20:00 UTC
by Julie Bisland March 5, 2019

March 5, 2019

Dear All, Please find the attendance and AC chat attached to this email, and the MP3 and Adobe Connect recording below for the New gTLD Subsequent Procedures Working Group call held on Monday, 04 March 2019 at 20:00 UTC. Attendance of the call is also posted on the agenda wiki page: https://community.icann.org/x/SYs2Bg MP3: https://audio.icann.org/gnso/gnso-new-gtld-subsequent-04mar19-en.mp3 [audio.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__audio.icann.org_gnso_g…> Adobe Connect Recording: https://participate.icann.org/p9teovovd5a/<https://participate.icann.org/p9teovovd5a/?OWASP_CSRFTOKEN=414717bcb3e519bb…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg/ Main wiki page for the working group: https://community.icann.org/x/RgV1Aw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you. Kind regards, Julie Julie Bisland Secretariat Operations Coordinator for the GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland(a)icann.org<mailto:julie.bisland@icann.org> Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting the GNSO Newcomer pages [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_g…>

1 0

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 04 March 2019
by Julie Hedlund March 4, 2019

March 4, 2019

Dear Working Group members, Please see below the notes from the meeting today, 04 March 2019. These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted at: https://community.icann.org/display/NGSPP/2019-03-04+New+gTLD+Subsequent+Pr…. Please also see the referenced document at: https://docs.google.com/spreadsheets/d/1Ea-CjtL-heQjEwTesr7MYC_8gFEvmhY8XBC…. Kind regards, Julie Julie Hedlund, Policy Director Notes and Action Items: Actions: ACTION ITEM 1: Send the link to the presentation provided to the GNSO Council on 21 February. Includes a timeline that notes that it assumes there would be no additional public comment period. DONE: See: https://community.icann.org/x/u4E2Bg ACTION ITEM 2: Send list of topics for full WG discussion in Kobe by 05 March. Notes: 1. Updates to Statements of Interest (SOIs): No updates provided. 3. Next steps for Sub Group comment analysis: -- Sub Groups A and C are completed with their analysis; Sub Group B will likely conclude at the end of March. -- Role is to group the comments (agreement, divergence, concerns, new ideas); staff and Co-Leaders are beginning to create summaries. -- Summarizing the sub group discussions into something more concise and digestible by the full WG. -- Call out where commenters have identified the same elements (support for recommendations, for example). -- Summaries are being included within the public comment review tool. -- See proof of concept at tab 2.8.2 and column F here: https://docs.google.com/spreadsheets/d/1MQmo1B6zBqGXYFRF2pKZXPhGmz0JfZhIaMx… 4. Planning for ICANN64: WT5, Saturday, 09 March: 09:00-10:15; 10:30-Noon Full WG, Saturday 09 March, 13:30-15:00 & 15:30-14:45 -- Full WG Session 1: Focus on Open topics to try to close them out -- such as 'Closure' of a Round, Appeals Mechanisms, ect. -- Full WG Sesssion 2: Topics worthy of closure based on public comment input so far. Full WG, Wednesday, 13 March, 15:15-16:45 -- Full WG Session 3: Final Reporting (recommendation drafting), Implementation Guidance (implementation). Work Track 5 Status: -- Good mix of responses to the Supplemental Initial Report. -- Two meetings to go through the General Comments and Preliminary Recommendations. -- On pending strings: Will have more information on why some strings are still pending (help to inform discussion on closure of rounds. The intention is not to try to resolve the statuses or develop policies to facilitate the resolution of those strings. It is more illustrative to help us understand what 'closure' means. 5. Review of comments - Supplemental Initial Report: 2.3: Role of Application Comment: 2.3.c.1: Line 9, BRG -- Agreement (Supports continuing guidance in Implementation Guideline C, use of verification methods, and inclusion of a filtering/sorting mechanism for comments) Lines 10-13, ALAC, ALAC, IPC, RySG -- Agreement (Supports the recommendations) Lines 14-15, RrSG & BC -- Agreement (verification of commenter) Line 16, ICANN Org -- Agreement (Supports the recommendations -- but notes that the Application Comment tool already provides these features) Concerns (about problems with searching and sorting of attachments) 2.3.c.2: Lines 18-21, dotgay LLC, ALAC, ALAC, IPC -- Agreement (Supports the recommendations) Line 22, ICANN org -- Agreement (but requesting clarifications in the context of the 2012 process) Lines 23 & 24, RrSG, RrSG -- Agreement (Supports allowing applicants to respond) Line 265 BC -- Agreement (Supports requiring response when comment may impact scoring) Line 26 & 27, BRG & RySG -- Agreement (Supports the recommendations) Concerns (needs more details) -- Letters of opposition should also be grouped as public comments. 2.3.e.1: Line 29, ALAC -- Agreement (Supports the recommendations) Line 30, ALAC -- Agreement (support for limiting the comment period for CPE) Line 31, IPC -- Agreement (with qualifications - same comment period for all types of applications) Line 32, dotgay LLC -- Agreement (qualified -- equal length of time for all public comments) New Idea (letters of opposition as public comments) Line 33-36, BRG, RySG, NCSG, BC -- Divergence (opposes changes to the extended comment period)

1 0

Proposed Agenda - New gTLD Subsequent Procedures PDP WG meeting - Monday, 04 March 2019 at 20:00 UTC
by Julie Hedlund March 2, 2019

March 2, 2019

Dear WG members, Please find below the proposed agenda for the upcoming call on Monday, 04 March 2019 at 20:00 UTC for 60 minutes: Draft Agenda: 1. Welcome/Review of the Agenda/Updates to Statements of Interest (SOIs) 3. Next steps for Sub Group comment analysis 4. Planning for ICANN64 5. Review of comments - Supplemental Initial Report: see the document at: https://docs.google.com/spreadsheets/d/1Ea-CjtL-heQjEwTesr7MYC_8gFEvmhY8XBC…: 2.3: Role of Application Comment (start at line 8) 6. AOB If you need a dial out or would like to send an apology for this call, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Best regards, Julie Julie Hedlund, Policy Director

2 1

Please share with your groups / ICANN64 GNSO Policy Briefing Available for Download
by Terri Agnew Feb. 27, 2019

Feb. 27, 2019

Dear all, GNSO Policy Briefing for ICANN64 is now available for download at http://go.icann.org/gnsobriefing<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.icann.org_gnsobriefi…> If you prefer to download individual sections, you can do so by visiting this page [go.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.icann.org_policybrie…>. The policy briefing is intended to facilitate your preparation for ICANN64. Please feel free to share the link with your respective groups and anyone else that may be interested: https://twitter.com/ICANN_GNSO/status/1100428245936291841 Happy reading! Best Regards, Terri

1 0

ICANN64: GNSO Sessions How to Get Organized and Remote Participation Details
by Julie Bisland Feb. 25, 2019

Feb. 25, 2019

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings' team has put together an updated ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN64 Meeting Schedule<https://64.schedule.icann.org/> GNSO Remote Participation Wiki Page<https://community.icann.org/x/-6MWBg> Step 1 - Create a profile and your personalized ICANN64 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you've added all your chosen meetings to "My Schedule" go to Export. * Importing creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. * Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. Step 3 All Adobe Connect rooms (which can be found on the session information on the ICANN64 Meeting Schedule<https://64.schedule.icann.org/> and on the <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/-6MWBg>) will provide audio streaming only, Adobe Connect room microphones will not be enabled. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/-6MWBg> for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Step 4 Please download the mobile app by searching for "ICANN64" in your app stores. Nathalie Peregrine and Terri Agnew will be onsite in Kobe to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team Julie Bisland Secretariat Operations Coordinator for the GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland(a)icann.org<mailto:julie.bisland@icann.org> Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting the GNSO Newcomer pages<https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy…>

1 0

Recordings, attendance & AC chat New gTLD Subsequent Procedures Working Group call / Tuesday, 19 February 2019 at 15:00 UTC
by Julie Bisland Feb. 20, 2019

Feb. 20, 2019

Dear All, Please find the attendance and AC chat attached to this email, and the MP3 and Adobe Connect recording below for the New gTLD Subsequent Procedures Working Group call held on Tuesday, 19 February 2019 at 15:00 UTC. Attendance of the call is also posted on the agenda wiki page: https://community.icann.org/x/fpsWBg MP3: https://audio.icann.org/gnso/gnso-new-gtld-subsequent-19feb19-en.mp3 [audio.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__audio.icann.org_gnso_g…> Adobe Connect Recording: https://participate.icann.org/p3zwz7ex92h/<https://participate.icann.org/p3zwz7ex92h/?OWASP_CSRFTOKEN=7fc12b33ae086884…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg/ Main wiki page for the working group: https://community.icann.org/x/RgV1Aw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you. Kind regards, Julie Julie Bisland Secretariat Operations Coordinator for the GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland(a)icann.org<mailto:julie.bisland@icann.org> Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting the GNSO Newcomer pages [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_g…>

1 0

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 19 February 2019
by Julie Hedlund Feb. 19, 2019

Feb. 19, 2019

Dear Working Group members, Please see below the notes from the meeting today, 19 February 2019. These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted at: https://community.icann.org/display/NGSPP/2019-02-19+New+gTLD+Subsequent+Pr…. Please also see the referenced document at: https://docs.google.com/spreadsheets/d/1Ea-CjtL-heQjEwTesr7MYC_8gFEvmhY8XBC…. Kind regards, Julie Julie Hedlund, Policy Director Notes and Action Items: Actions: ACTION ITEM 1: 2.2.e.1: RySG Comment -- request for clarification on their statement: "If private resolutions and private auctions are to be prohibited from the next round, ICANN must first conduct and then publish an legal analysis supporting the prohibition of these methods of contention resolution." Notes: 1. Updates to Statements of Interest (SOIs): Cheryl Langdon-Orr(@CLO3 PDP Co-Chair): My minor SOI update (shared with a SG or two already) is my recent confirmation as ATRT3 Co-Chair -Patrick Kane from Verisign is the other Co-Chair FYI 2. Discussion of Role of GNSO Council Liaisons: -- Two (new) GNSO Council Liaisons: Elsa Saade and Flip Petillion. -- Roll of the GNSO Council Liaison has changed -- improvement is the further definition of the role. -- Much more important role than in the past. -- See: https://gnso.icann.org/en/council/gnso-liaison-wg-22feb18-en.pdf. -- Make sure that any concerns the WG members may have are conveyed to the GNSO Council (if they can't be resolved at the WG level). -- Also keeps the Council up to date on PDP WG status and any issues that may arisse. 3. Discussion of the Draft Work Plan: See Draft Work Plan at: https://docs.google.com/document/d/1l9pIXkiu_d5zPVqTM09Z5BiJ1Y3-mhnwaZLPfDD… -- Envisions WT5 joining up with the full WG. -- Finish 2 of 3 Sub Groups before Kobe -- SG A and C. -- Sub Group B will complete by end of March. -- WG can begin review of topics even before SG B is finished. -- Remove 25 Feb call from the Work Plan as it was canceled. -- Staff have completed draft comment tool and analysis of WT5 Supplemental Initial Report comments. -- Work Plan doesn't include another comment period -- not to say that we won't have one, but it hasn't definitely been decided. -- Add dates and times for ICANN64 Meetings and topics. 4. Continue Review of Supplemental Initial Report Public Comments – see the document at: https://docs.google.com/spreadsheets/d/1Ea-CjtL-heQjEwTesr7MYC_8gFEvmhY8XBC… -- 2.1 Auctions: Mechanisms of Last Resort: 2.1.e.3: Line 63, ALAC -- New Idea (Supports modified Vickrey auction) Line 64, RySG -- New Idea (Consider multiplier for qualified applicants/more data is needed.) Line 65, IPC -- New Idea (Principles of 'fairness" should not conflict with IP rights) Line 66, RySG -- New Idea (Supports Vickrey auction/but balance fairness and competition) Line 67, Neustar -- New Idea (fairness not considered in isolation) LIne 68, NCSG -- New Idea (suggests consulting with auction specialists) Line 69, BRG -- Divergence (support current process as mechanism of last resort, doesnt agree that it is unfair) 2.1.e.4: Line 71, BC -- Agreement (eliminate auction of last resort/supports RFP process and Vickrey auction) Line 72, IPC -- Agreement (qualified support for Random Drawing) Divergence (opposes RFP) LIne 73, RySG -- Agreement (qualified support for Random Drawing) Divergence (opposes RFP) Line 74, Neustar -- Agreement (qualified support for Random Drawing) Divergence (opposes RFP) Line 75, NCSG -- Concerns (with comparative evaluations) Divergence (auctions of last resort remain the best method) Line 76, BRG -- Divergence (support current process as mechanism of last resort) Line 77, ALAC -- Divergence (supports Vickrey auction over RFPs or Random Draw) 2.1.e.5: Line 79, NCSG -- Agreement (supports limits) Line 80, BRG -- Divergence (support current process as mechanism of last resort) Line 81, ALAC -- Divergence (opposes limits/supports multiplier-enhanced Vickrey auction) Line 82, IPC -- Divergence (opposes limits) Line 83, RySG -- Divergence (opposes limits/support for Vickery auction) Line 84, Neustar -- Divergence (opposes limits) -- 2.2 Private Resolution of Contention Sets (including Private Auctions): Summary: Very little support to elimination of all mechanisms of private resolutions; also not much support for raising fees. General Comments: Line 4, GAC -- Agreement (supports measure to disincentivise private auctions) Line 5, RrSG -- Support (qualified -- consider high fees to reduce speculative applications) Concerns (any action ICANN might try to prevent private resolution) New Idea (one round then move to FCFS) Line 6, ICANN Board -- Concerns (new procedures that may be open to abuse) Line 7, ALAC -- Divergence (strongly against private resolution) 2.2.d.1: Line 9, ALAC -- Agreement (supports option to disallow private resolution where there is a financial benefit) From the chat: Justine Chew: @jeff, correct, we oppose private auctions namely Justine Chew: and any form of private resolutions which result in financial benefit to applicant withdrawing application in a contention set Line 10, RySG -- Agreement (some support for disallowing private resolutions) New Idea (some support for recreative contention resolution) Divergence (some oppose the option to disallow private resolution) Line 11, BRG -- Divergence (opposes restrictions on private auctions) Line 12, IPC -- Divergence (opposes restrictions on private resolution) Line 13, Neustar -- Divergence (opposes disallowing private resolution) 2.2.d.2: Line 15, RySG -- Agreement (some support disallowing private resolution) Divergence (some oppose disallowing private resolution) Line 16, BRG -- Divergence (opposes disallowing private resolution) Line 17, ALAC -- Divergence (opposes disallowing private resolution) Line 18, IPC -- Divergence (opposes disallowing private resolution) Line 19, Neustar -- Divergence (opposes disallowing private resolution) 2.1.d.2.2: Line 21, BRG -- Divergence (opposes drawing as an alternative to private resolution) 2.2.d.3: Line 23, ALAC -- Agreement (supports allowing some types of private resolutions but disallowing others) Line 24, IPC -- Agreement (supports allowing some types of private resolutions but disallowing others) Line 25, RySG -- Agreement (some support the option) Divergence (some oppose disallowing some types of private resolutions but disallowing others) LIne 26, Neustar -- Divergence (opposes allowing some types of private resolutions but disallowing others) Line 27, BRG -- Divergence (opposes disallowing some types of private resolutions) 2.2.e.1: LIne 29, BRG -- Agreement (supports allowing private resolutions, but no suggesting for how to distribute funds) Line 30, ALAC -- Agreement (but support for Vickrey auction and oppose applicant financial benefit) New Idea (handle funds in the same manner as the 2012 round) Line 31, Neustar -- Agreement (support allowing private resolution) New Idea (funds distribted among those in the contention set) Line 32, RySG -- Agreement (some support for allowing private resolution and for ICANN to manage the funds) Divergence (some oppose allowing private resolution) Lien 33, NCSG -- Divergence (opposes private resolution) 2.2.e.2: Line 35, BRG -- [Doesn't directly answer the question, supports private resolution] Line 36, Neustar -- [no opinion] Line 37, ALAC -- Agreement (equally problematic across TLDs, but geo names may have different factors) Line 38, NCSG -- Agreement (that private auctions are always problematic) Line 39, RySG -- Agreement (some agree that private resolutions are problematic across all TLD types) Divergence (some oppose restricting the use of private resolution) Line 40, IPC -- Divergence (doesn't agree that private resolutions are problematic) 2.2.e.3: Line 42, NIXI -- Agreement (supports prohibition in the AGB, T&Cs, RA) Divergence (opposes increasing application fees) Line 43, ALAC -- Agreement (supports prohibition in the AGB, T&Cs, RA) Divergence (opposes increasing application fees) Line 44, RySG -- Agreement (some support Vickrey auction and ramifications for private resolutions) Divergence (some oppose restricting private resolutions) Line 45, NCSG -- Agreement (supports prohibition in the AGB, T&Cs, RA) Divergence (opposes increasing application fees) Line 46, BRG -- Divergence (opposes restricting private resolutions) Line 47, IPC -- Divergence (opposes restricting private resolutions) Line 48, Neustar -- Divergence (oppose restricting private resolutions) 2.2.e.4: Line 50, NCSG -- Agreement (that some private resolutions are problematic and some requirements in T&Cs) Line 51, ALAC -- Agreement (supports restrictions where losing applicant receives financial benefit) Divergence (opposes ban on private resolution) Line 52, RySG -- Agreement (some support prohibiting private resolutions) Divergence (some do not think private resolution is problematic) Line 53, BRG -- Divergence (does not think private resolution is problematic) Line 54, IPC -- Divergence (does not think private resolution is problematic) Line 55, Neustar -- Divergence (does not think private resolution is problematic) 2.2.e.5: Line 57, NCSG -- Agreement (that there may be private resolutions that are appropriate with transparent T&Cs) Line 58, ALAC -- New Idea (review on a case-by-case basis) Line 59, RySG -- Agreement (some support some restrictions) Divergence (some oppose restrictions on private resolution) Line 60, BRG -- Divergence (opposes restrictions on private resolution) Line 61, IPC -- Divergence (disagrees that there is an issue) Line 62, Neustar -- Divergence (disagrees that there is an issue) 2.2.e.6: Line 64, RySG -- Agreement (some agree with qualifications) Divergence (some oppose use of an application fee as a control mechanism) Line 65, IPC -- New Idea (if higher fee combine with partial refunds) Divergence (opposes use of an application fee as a control mechanism; application fees should be cost-neutral) Line 66, BRG -- Divergence (opposes use of an application fee as a control mechanism) Line 67, ALAC -- Divergence (opposes use of an application fee as a control mechanism) Line 68, Neustar -- Divergence (opposes use of an application fee as a control mechanism) Line 69, NCSG -- Divergence (opposes use of an application fee as a control mechanism) 2.3: Role of Application Comment General Comments: Line 4, GAC -- Supports Early Warning and AGB-consensus advice; welcomes dialogue to increase transparency and fairness; opposes the PDP making recommendations on GAC activities; notes that change to the likely operator of a gTLD should invoke notification requirement and possible re-evaluation, including public comment Line 5, ALAC -- Agreement (Supports the WG’s preliminary recommendations 2.3.c.1 -- optimize the mechanisms and system for Application Comment; 2.3.c.2 -- ICANN to be more explicit in the Applicant Guidebook on how public comments are to be utilized; 2.3.e.1 -- CPE to run parallel to the Initial Evaluation comment period; 2.3.e.3 -- applicants limited period to respond to late comments) Line 6, BC -- Agreement (2.3.c.2 -- Requiring response when comment may impact scoring; 2.3.c.1 -- Verifying commenter; 2.3.e.1 -- longer comment period) Line 7, RrSG -- Agreement (2.3.c.1 -- verifying commenter; 2.3.c.2 and 2.3.e.2 -- allow applicants to respond) Start on line 8 for the next meeting. 5. Update on ICANN64: -- Schedule released, SubPro is mostly on Saturday. WT5 in the morning and full WG in the afternoon, as well as one session on Wednesday. -- Can change the Wednesday session if there is anything else we need to devote time to. -- For the WG meeting, we may pick out some full WG topics on which we need to make progress. For example, the notion of the close of an application round and the ramification of defining the close of a round. Recap comments we have and how to move forward. -- There will be remote participation as usual.

1 0

Re: [Gnso-newgtld-wg] Proposed Agenda - New gTLD Subsequent Procedures PDP WG meeting - Tuesday, 19 February 2019 at 15:00 UTC
by Steve Chan Feb. 15, 2019

Feb. 15, 2019

Thanks Julie! Dear WG Members, To add to Julie’s message, please find some additional resources to support our WG call. For agenda item 2, please find the role description of the GNSO Council Liaison to GNSO WGs: https://gnso.icann.org/en/council/gnso-liaison-wg-22feb18-en.pdf. These responsibilities are ultimately derived from the GNSO Operating Procedures, but this role description helps provide a consolidated list of those activities. For agenda item 3, please find a link to the draft work plan: https://docs.google.com/document/d/1l9pIXkiu_d5zPVqTM09Z5BiJ1Y3-mhnwaZLPfDD…. The WG Co-Chairs would like to stress that this is a living document and will be adjusted as it becomes clearer what the WG’s trajectory to its Final Report looks like. Best, Steve From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Friday, February 15, 2019 at 8:05 AM To: "gnso-newgtld-wg(a)icann.org" <gnso-newgtld-wg(a)icann.org> Subject: [Gnso-newgtld-wg] Proposed Agenda - New gTLD Subsequent Procedures PDP WG meeting - Tuesday, 19 February 2019 at 15:00 UTC Dear WG members, Please find below the proposed agenda for the upcoming call on Tuesday, 19 February 2019 at 15:00 UTC for 90 minutes: Draft Agenda: 1. Review Agenda/Statements of Interest 2. Discussion of Role of GNSO Council Liaisons 3. Discussion of the Timeline 4. Continue Review of Supplemental Initial Report Public Comments – see the document at: https://docs.google.com/spreadsheets/d/1Ea-CjtL-heQjEwTesr7MYC_8gFEvmhY8XBC… -- 2.1 Auctions: Mechanisms of Last Resort – Start at 2.1.e.3, Line 62 -- 2.2 Private Resolution of Contention Sets (including Private Auctions) -- 2.3 Role of Applicant Comment (time permitting) 5. Update on ICANN64 6. AOB If you need a dial out or would like to send an apology for this call, please email gnso-secs(a)icann.org. Best regards, Julie Julie Hedlund, Policy Director

1 0

Proposed Agenda - New gTLD Subsequent Procedures PDP WG meeting - Tuesday, 19 February 2019 at 15:00 UTC
by Julie Hedlund Feb. 15, 2019

Feb. 15, 2019

Dear WG members, Please find below the proposed agenda for the upcoming call on Tuesday, 19 February 2019 at 15:00 UTC for 90 minutes: Draft Agenda: 1. Review Agenda/Statements of Interest 2. Discussion of Role of GNSO Council Liaisons 3. Discussion of the Timeline 4. Continue Review of Supplemental Initial Report Public Comments – see the document at: https://docs.google.com/spreadsheets/d/1Ea-CjtL-heQjEwTesr7MYC_8gFEvmhY8XBC… -- 2.1 Auctions: Mechanisms of Last Resort – Start at 2.1.e.3, Line 62 -- 2.2 Private Resolution of Contention Sets (including Private Auctions) -- 2.3 Role of Applicant Comment (time permitting) 5. Update on ICANN64 6. AOB If you need a dial out or would like to send an apology for this call, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Best regards, Julie Julie Hedlund, Policy Director

1 0