March 2019 - Gnso-newgtld-wg

Re: [Gnso-newgtld-wg] Subsequent Procedures Working Group - Name Collisions covered in SubGroup B today
by Rubens Kuhl March 5, 2019

March 5, 2019

> On 5 Mar 2019, at 17:17, Aikman-Scalese, Anne <AAikman(a)lrrc.com> wrote: > > Thanks Rubens. I think the Initial Report and some of the public comment conflicts with the SAC 90 recommendations adopted by the Board and that is why I am raising this for discussion with the full WG. You refer to “consideration” of SAC 90. Are you saying that as long as the WG has “considered” SAC 90 (and perhaps rejected it if not consistent with the policy development process of the WG), then that is all we need to do? Board can't order GNSO anything, and GNSO can't order Board anything. Note that even the SAC 90 scorecard says "ask", not "order", "mandate", "demand" or anything like that. The bylaws stipulate what every group can do, what procedures they must follow etc. > > When a recommendation is adopted by the Board, what is the obligation of the WG to conform its own recommendations to recommendations already adopted by the Board? (We may have similar questions in relation to the Competition, Consumer Trust, and Consumer Choice Review Team (CCTRT) recommendations, if these are adopted by the Board.) If you look at overall registry of advices from SOs and ACs, you will see that Board "adopts" a lot of those and then implement them in a manner that - in my reading - is actually rejecting instead of adopting. So documents that say "Board adopted this advice" actually bring little value in determining what is being ruled by the Board. The actual implementation of those is much more informative. Board works in mysterious ways... > > CCTRT Final Report is here: https://www.icann.org/en/system/files/files/cct-rt-final-08sep18-en.pdf <https://www.icann.org/en/system/files/files/cct-rt-final-08sep18-en.pdf> > > I realize that the Co-leaders could take the approach that the Sub Pro WG is not bound by the Board’s adoption of recommendations and is only bound to consider these items and make whatever recommendations it deems appropriate. Unfortunately, that approach can result in a bottleneck at the Board level since the Board is often dealing with conflicting opinions. > I don't know if they think they are bound or not, but they are actually not. And in this case there is not even something tangible to be bound to, since there was no actual implementation of those recommendations. But, since no GNSO policy comes into effect without Board ratification, I'm sure that if we got this wrong, they will tell us in due time. It should be remembered from the history of name collisions that Board actually went to a different path from SSAC advices a good number of times in this topic, including the choice of the controlled interruption signal where Board preferred the ICANN Org suggested local network value (127.0.53.53) and SSAC advised an actually addressable system that would collect information. So even if this actually deviates from SSAC advice, which I'm not sure I agree, it wouldn't be unprecedented to follow a different path. Rubens > Anne > > > > > From: Rubens Kuhl [mailto:rubensk@nic.br <mailto:rubensk@nic.br>] > Sent: Tuesday, March 5, 2019 12:20 PM > To: Aikman-Scalese, Anne <AAikman(a)lrrc.com <mailto:AAikman@lrrc.com>> > Cc: gnso-newgtld-wg(a)icann.org <mailto:gnso-newgtld-wg@icann.org> > Subject: Re: [Gnso-newgtld-wg] Subsequent Procedures Working Group - Name Collisions covered in SubGroup B today > Importance: High > > > Anne, > > The completion of this work will exactly be publishing the PDP WG Final Report and GNSO Council adopting it, so it seems we are on track, as long as the final report doesn't remove the SAC 90 consideration. > > > > > Rubens > > > > On 5 Mar 2019, at 15:49, Aikman-Scalese, Anne <AAikman(a)lrrc.com <mailto:AAikman@lrrc.com>> wrote: > > Please see below. > > Hi all – Regarding Name Collisions, when we get to the full WG consideration, we will need to refer to the fact that the Board gave the WG specific directions regarding the recommendations that it adopted pursuant to SSAC Advice. These appear below – excerpted from the Board’s Scorecard. Recommendation 4 is the item that Jeff said he thought was not in SAC 90: “The SSAC recommends that ICANN complete this work before making any decision to add new TLD names to the global DNS.” The work to be completed it described in SAC 90 Recommendations 1 through 3 as shown below with the corresponding Board adoption shown in the far right column. Thanks, Anne > > <image001.png> > > Anne E. Aikman-Scalese > Of Counsel > 520.629.4428 office > 520.879.4725 fax > AAikman(a)lrrc.com <mailto:AAikman@lrrc.com> > _____________________________ > <image003.png> > Lewis Roca Rothgerber Christie LLP > One South Church Avenue, Suite 700 > Tucson, Arizona 85701-1611 > lrrc.com <http://lrrc.com/> > > > > > From: Ntfy-GNSO-NewGTLD-WG-SGB [mailto:ntfy-gnso-newgtld-wg-sgb-bounces@icann.org <mailto:ntfy-gnso-newgtld-wg-sgb-bounces@icann.org>] On Behalf Of Michelle DeSmyter > Sent: Tuesday, March 5, 2019 9:52 AM > To: ntfy-gnso-newgtld-wg-sgb(a)icann.org <mailto:ntfy-gnso-newgtld-wg-sgb@icann.org> > Cc: gnso-secs(a)icann.org <mailto:gnso-secs@icann.org> > Subject: [Ntfy-GNSO-NewGTLD-WG-SGB] ***CALL IN 10 MINUTES*** Meeting invitation: New gTLD Subsequent Procedures PDP - Sub Group B call / Tuesday, 05 March 2019 at 17:00 UTC > > [EXTERNAL] > Dear all, <> > > The details are below for the New gTLD Subsequent Procedures PDP - Sub Group B call on Tuesday, 05 March 2019 at 17:00 UTC for 60 minutes. > 09:00 PST, 12:00 EST, 18:00 Paris CET, 22:00 Karachi PKT, (Wednesday) 02:00 Tokyo JST, (Wednesday) 04:00 Melbourne AEDT > For other times: https://tinyurl.com/y4o7z723 [tinyurl.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y4o7z723&d…> > > Agenda Wiki: https://community.icann.org/x/WIs2Bg <https://community.icann.org/x/WIs2Bg> > Please join the meeting room here: https://participate.icann.org/newgtldsubteams/ <https://participate.icann.org/newgtldsubteams/> > If you’re having trouble joining, please check your plug ins: http://tinyurl.com/icannactest [tinyurl.com] <https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_icannactest…> > Please allow yourself additional time before start of meeting to log into Adobe Connect > Please log in with First and Last Name when joining the AC room. > Instructions explaining how to connect the audio in the Adobe Connect room are attached. A calendar invitation has equally been sent and an ical (if your inbox doesn’t receive direct calendar invitations) is available here as attachment for you to download to your calendar. > If you require a dial-out or to send apologies (do not send to full sub team) please send an email request with your preferred contact number to gnso-secs(a)icann.org <mailto:gnso-secs@icann.org> > > Conference Bridge: > Toll-free access number (US and Canada): 800 550 6865 and Toll 213 233 3193 > > Other telephone numbers found here: http://www.adigo.com/icann [adigo.com] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.adigo.com_icann&d=D…> > > Enter passcode (Conference ID) on telephone: 7349 > Please let me know if you have any questions. > > Thank you. > > Kind regards, > > Julie > > > > > This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. > _______________________________________________ > Gnso-newgtld-wg mailing list > Gnso-newgtld-wg(a)icann.org <mailto:Gnso-newgtld-wg@icann.org> > https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg <https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg> > > > > This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

2 1

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