December 2023 - SubPro-IRT - lists.icann.org

Topic 21.1: Geographic Names - Update
by Michael Karakash Dec. 22, 2023

Dec. 22, 2023

Dear IRT Members, We’ve updated and finalized the Geographic Names AGB section<https://docs.google.com/document/d/1N1iLzfPp4IeTuTyO46T7WSjww7kpe_fzJIVOaSQ…> based on discussions had during the 30 November IRT call as well as comments made on both the mailing list and the Google document. You can also find a PDF version of the document here<https://community.icann.org/pages/viewpage.action?pageId=238617525&preview=…>. As a reminder, updated documents, past agenda items, and video/audio recordings from previous sessions can be found on the IRT Community Wiki.<https://community.icann.org/pages/viewpage.action?pageId=238617525> Thank you and Happy Holidays! Best, Michael

4 3

Re: [SubPro-IRT] REMINDER | SubPro IRT Meeting #23 | 19 December 2023, 14:00-15:00 UTC
by Merritt, Jason (ISED/ISDE) Dec. 21, 2023

Dec. 21, 2023

Hi Mike, thanks for the follow up. It could just be the way I’m reading it, or the way that it is listed numerically makes it seem like additional criteria for an EW. For example, 2) seems to be an additional criteria (there may also be reasons other than national laws for an EW… the “Overview” section of the draft AGB seems to cover this). The second half of the sentence in 3) adds an additional ‘rationale’ criteria. Simply indicating that the only solution to address the concern is for the applicant to withdraw the application is an option for the GAC member in their EW. Either way, the written explanation would include these details. On 4), I don’t think there is an obligation to provide a contact. In the absence of a contact, the GAC Representative would be default. ICANN (GAC Staff) could facilitate a connection if need be. I think the language should read something like: GAC consensus is not required for GAC Member Early Warnings to be issued. Governments issuing Early Warnings must include a written explanation describing why the GAC Early Warning was submitted and how the applicant may potentially address the GAC member’s concerns, to the extent feasible. The GAC member issuing an Early Warning may indicate that its concern can only be addressed by the applicant withdrawing its application. Jason From: Mike Rodenbaugh <mike(a)rodenbaugh.com<mailto:mike@rodenbaugh.com>> Sent: December 19, 2023 9:10 AM To: Merritt; Merritt, Jason (ISED/ISDE) <Jason.Merritt(a)ised-isde.gc.ca<mailto:Jason.Merritt@ised-isde.gc.ca>> Cc: Next Round Policy Implementation <NextRound_PolicyImplementation(a)icann.org<mailto:NextRound_PolicyImplementation@icann.org>>; subpro-irt@ <icann.org subpro-irt(a)icann.org<mailto:subpro-irt@icann.org>> Subject: Re: [SubPro-IRT] REMINDER | SubPro IRT Meeting #23 | 19 December 2023, 14:00-15:00 UTC Hi Jason, thank you for the helpful background. "To the extent feasible" is better than "if applicable" as it eliminates the binary choice with the possibility of unexplained "not applicable". [Image removed by sender.] I note your last bullet containing Board advice: * The Board believes that the intent of this recommendation can be met if a GAC member provides a rationale why a remedy to their early warning is not possible. Your suggested language does not seem to require a rationale if the GAC member believes a remedy is not possible. I would therefore suggest the following: Governments issuing Early Warnings must include a written explanation describing 1) why the GAC Early Warning was submitted, 2) how specific national laws and/or sensitivities are implicated, 3) how the applicant may address remedy the GAC member’s concerns to the extent feasible, or if the GAC member believes a remedy is not possible then the GAC member must provide a rationale, if applicable, as well as and, 4) identify the all objecting countries and the nominated contact from each. Would that work for the GAC? [Image removed by sender. Logo] Mike Rodenbaugh address: 548 Market Street, Box 55819 San Francisco, CA 94104 email: mike(a)rodenbaugh.com<mailto:mike@rodenbaugh.com> phone: +1 (415) 738-8087 WORLD TRADEMARK REVIEW "WTR 1000" Top Global TM Counsel 2012 to present [Book a Meeting<https://www.cloudhq.net/meeting/XC81iInExBDubRBjgCt>] On Tue, Dec 19, 2023 at 2:54 AM Merritt, Jason (ISED/ISDE) <Jason.Merritt(a)ised-isde.gc.ca<mailto:Jason.Merritt@ised-isde.gc.ca>> wrote: Hi Mike, all, I just wanted to flag some language regarding the GAC EW’s. Your proposed edits / notes below remove some of the balanced language that was agreed with the Board following GAC input. I.e. “ how the applicant may address the GAC member’s concerns if applicable” – I believe the “if applicable” is what the Board added to address the GAC’s request to note this may not always be possible. The GAC noted this in the ICANN77 Communiqué: Regarding Recommendation 30.6, the GAC agrees with the notion that a GAC Early Warning should be explained and that in order to ensure constructive dialogue at an early stage of the procedure and mitigate these concerns it is important for government(s) issuing Early Warning(s) or the GAC in its advice to provide a written explanation/rationale. However, the GAC wishes to recall the compromise language brought forward by the GAC, as applications may not always be able to be remedied in the opinion of the government(s) issuing a GAC Early Warning. Therefore, the GAC proposes the adoption of an updated language to Recommendation 30.6 as follows: “[...] how the applicant may potentially address the GAC member’s concerns to the extent feasible”. The Board responded: Regarding Recommendation 30.6 (in the scorecard): * The Board notes that the GAC had previously proposed to amend the recommendation with the same language (“to the extent feasible”), see the 2020 GAC’s public comment<https://gac.icann.org/file-asset/GAC%20Subpro%20Final%20Report%20Collective…> on the Draft Final Report, and also the 2021 GAC’s public comment on the Final Report<https://gac.icann.org/statement/public/gac-comment-(final)-subpro-final-out…>. * The Board believes that the intent of this recommendation can be met if a GAC member provides a rationale why a remedy to their early warning is not possible. I think the wording has to be something like: Governments issuing Early Warnings must include a written explanation describing why the GAC Early Warning was submitted and how the applicant may address the GAC member’s concerns, [ if applicable, OR to the extent feasible ] as well as identify the objecting countries. I hope this helps. Regards, Jason Merritt Sr Policy Advisor, Telecommunications and Internet Policy Branch Innovation, Science and Economic Development Canada / Government of Canada Jason.Merritt(a)ised-isde.gc.ca<mailto:Jason.Merritt@ised-isde.gc.ca> / Tel: 343-571-9775 / TTY: 1-866-694-8389 Conseiller(ère) princ. en politiques, Direction generale des politiques de telecommunications et d'Internet Innovation, Sciences et Développement économique Canada / Gouvernement du Canada Jason.Merritt(a)ised-isde.gc.ca<mailto:Jason.Merritt@ised-isde.gc.ca> / Tél. : 343-571-9775 / ATS : 1-866-694-8389 From: SubPro-IRT <subpro-irt-bounces(a)icann.org<mailto:subpro-irt-bounces@icann.org>> On Behalf Of Mike Rodenbaugh Sent: December 19, 2023 12:39 AM To: Next Round Policy Implementation <NextRound_PolicyImplementation(a)icann.org<mailto:NextRound_PolicyImplementation@icann.org>> Cc: subpro-irt(a)icann.org<mailto:subpro-irt@icann.org> Subject: Re: [SubPro-IRT] REMINDER | SubPro IRT Meeting #23 | 19 December 2023, 14:00-15:00 UTC Hi all, Here are my notes on the current Topic #30 draft paper: First paragraph should state that government 'sensitivities' or national laws must be specified in the Early Warning. Delete fn. 2. Why should Org be allowed to unilaterally extend this time period on its own whim? Change this sentence: The GAC Early Warning notice may must include a nominated point of contact for further information consultation with the applicant. Clarify this last sentence re EWs: Governments issuing Early Warnings must include a written explanation describing 1) why the GAC Early Warning was submitted, 2) how specific national laws and/or sensitivities are implicated, 3) how the applicant may address the GAC member’s concerns, if applicable, as well as and, 4) identify the all objecting countries and the nominated contact from each. The paragraph at fn 6 and 7 needs to be reworked - bad grammar. This is not right: "The applicant will have a period of 21 calendar days from the time the Board acknowledges receipt of the advice in which to submit a response." The time period should be longer than 21 days (as it would typically take much longer than that to meet with government reps), and should not be keyed from a time unknown to the applicant. Also bad grammar. Best, Mike [Image removed by sender. Logo] Mike Rodenbaugh address: 548 Market Street, Box 55819 San Francisco, CA 94104 email: mike(a)rodenbaugh.com<mailto:mike@rodenbaugh.com> phone: +1 (415) 738-8087 WORLD TRADEMARK REVIEW "WTR 1000" Top Global TM Counsel 2012 to present [Book a Meeting<https://www.cloudhq.net/meeting/stTkgqqvVTxS40EySIJv>] On Mon, Dec 18, 2023 at 6:00 AM Next Round Policy Implementation <NextRound_PolicyImplementation(a)icann.org<mailto:NextRound_PolicyImplementation@icann.org>> wrote: Dear All, Meeting #23 of the SubPro IRT will be held on 19 December 2023 at 14:00-15:00 UTC [local time<https://www.timeanddate.com/worldclock/fixedtime.html?msg=SubPro+IRT+Meetin…>]. The agenda can be consulted here<https://community.icann.org/x/dZOZDg>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en>. Please note that the meeting was rescheduled. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/98960123523?pwd=SjU0cEtieS9Kc2NZRUNPNGdraGQ0QT09 Meeting ID: 989 6012 3523 Passcode: z6sLS^44@y Zoom Audio only: One tap mobile +13462487799,,98960123523#,,,,*8399371478# US (Houston) +16699006833,,98960123523#,,,,*8399371478# US (San Jose) Dial in directly with your local number: https://icann.zoom.us/u/aIO87mfSF Meeting ID: 989 6012 3523 Passcode: 8399371478 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Elisa _______________________________________________ SubPro-IRT mailing list SubPro-IRT(a)icann.org<mailto:SubPro-IRT@icann.org> https://mm.icann.org/mailman/listinfo/subpro-irt _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

3 3

REMINDER | SubPro IRT Meeting #23 | 19 December 2023, 14:00-15:00 UTC
by Next Round Policy Implementation Dec. 21, 2023

Dec. 21, 2023

Dear All, Meeting #23 of the SubPro IRT will be held on 19 December 2023 at 14:00-15:00 UTC [local time<https://www.timeanddate.com/worldclock/fixedtime.html?msg=SubPro+IRT+Meetin…>]. The agenda can be consulted here<https://community.icann.org/x/dZOZDg>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en>. Please note that the meeting was rescheduled. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/98960123523?pwd=SjU0cEtieS9Kc2NZRUNPNGdraGQ0QT09 Meeting ID: 989 6012 3523 Passcode: z6sLS^44@y Zoom Audio only: One tap mobile +13462487799,,98960123523#,,,,*8399371478# US (Houston) +16699006833,,98960123523#,,,,*8399371478# US (San Jose) Dial in directly with your local number: https://icann.zoom.us/u/aIO87mfSF Meeting ID: 989 6012 3523 Passcode: 8399371478 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Elisa

4 5

Post call | SubPro IRT Meeting #23 | 19 December 2023
by Next Round Policy Implementation Dec. 19, 2023

Dec. 19, 2023

Dear All, The recordings for Meeting #23 of the SubPro IRT held on Tuesday, 19 December 2023 at 14:00-15:00 UTC are published on the meeting wiki page<https://community.icann.org/x/dZOZDg>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) For additional information, you may consult the mailing list archives<https://mm.icann.org/pipermail/subpro-irt/> and the main wiki page<https://community.icann.org/x/pQM5Dg>. Best regards, Elisa

1 0

CANCELLED | SubPro IRT Meeting #23b | 21 December 2023
by Next Round Policy Implementation Dec. 19, 2023

Dec. 19, 2023

Dear All, Meeting #23b <https://community.icann.org/x/q5FME> of the SubPro IRT, scheduled for 21 December 2023, is cancelled. Thank you for your understanding. Best regards, Elisa

1 1

REMINDER | SubPro IRT Meeting #23 | 19 December 2023, 14:00-15:00 UTC
by Next Round Policy Implementation Dec. 19, 2023

Dec. 19, 2023

Dear All, Meeting #23 of the SubPro IRT will be held in an hour on 19 December 2023 at 14:00-15:00 UTC [local time<https://www.timeanddate.com/worldclock/fixedtime.html?msg=SubPro+IRT+Meetin…>]. The agenda can be consulted here<https://community.icann.org/x/dZOZDg>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en>. Please note that the meeting was rescheduled. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/98960123523?pwd=SjU0cEtieS9Kc2NZRUNPNGdraGQ0QT09 Meeting ID: 989 6012 3523 Passcode: z6sLS^44@y Zoom Audio only: One tap mobile +13462487799,,98960123523#,,,,*8399371478# US (Houston) +16699006833,,98960123523#,,,,*8399371478# US (San Jose) Dial in directly with your local number: https://icann.zoom.us/u/aIO87mfSF Meeting ID: 989 6012 3523 Passcode: 8399371478 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Elisa

1 0

TIME CHANGE | SubPro IRT Meeting #23 | 19 December 2023, 14:00-15:00 UTC
by Next Round Policy Implementation Dec. 14, 2023

Dec. 14, 2023

Dear All, Meeting #23 of the SubPro IRT will be held on 19 December 2023 at 14:00-15:00 UTC [local time<https://www.timeanddate.com/worldclock/fixedtime.html?msg=SubPro+IRT+Meetin…>]. The agenda can be consulted here<https://community.icann.org/x/dZOZDg>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en>. Please note that the meeting was rescheduled. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/98960123523?pwd=SjU0cEtieS9Kc2NZRUNPNGdraGQ0QT09 Meeting ID: 989 6012 3523 Passcode: z6sLS^44@y Zoom Audio only: One tap mobile +13462487799,,98960123523#,,,,*8399371478# US (Houston) +16699006833,,98960123523#,,,,*8399371478# US (San Jose) Dial in directly with your local number: https://icann.zoom.us/u/aIO87mfSF Meeting ID: 989 6012 3523 Passcode: 8399371478 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Elisa

1 0

Call for volunteers RSP, RST and ASP sub-tracks
by Next Round Policy Implementation Dec. 14, 2023

Dec. 14, 2023

Dear All, As mentioned during the last calls, we are looking for volunteers for three upcoming IRT sub-tracks as follows: * Topic 6 | Registry Service Provider (RSP) Pre-Evaluation * Topic 39 | Registry System Testing (RST) * Topic 17 | Applicant Support [Program] (ASP) Volunteers should be able to commit to participating in weekly meetings and be familiar with the relevant SubPro Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-rep…> recommendations and subject matter. We expect to launch these sub-tracks late in Q4 this year or early in Q1 next year. More information on the exact timeline will be provided in due course. Should you be interested in joining one or more sub-tracks, please send an email to the list at subpro-irt(a)icann.org<mailto:subpro-irt@icann.org> or to the IPT at nextround_policyimplementation(a)icann.org<mailto:nextround_policyimplementation@icann.org>. New members are welcome to join but will have to fill out this form<https://docs.google.com/forms/d/e/1FAIpQLSftZbaKdGr-CULrNjp-sJ94G4uwZWqXcRz…> first. Please do not hesitate to reach out should you have any questions. Best regards, Elisa

23 25

Post call | SubPro IRT Meeting #22 | 12 December 2023
by Next Round Policy Implementation Dec. 12, 2023

Dec. 12, 2023

Dear All, The recordings for Meeting #22 of the SubPro IRT held on Tuesday, 12 December 2023 at 20:00-21:00 UTC are published on the meeting wiki page<https://community.icann.org/x/bpOZDg>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) For additional information, you may consult the mailing list archives<https://mm.icann.org/pipermail/subpro-irt/> and the main wiki page<https://community.icann.org/x/pQM5Dg>. Best regards, Elisa

1 0

REMINDER | SubPro IRT Meeting #22 | 12 December 2023, 20:00-21:00 UTC
by Next Round Policy Implementation Dec. 12, 2023

Dec. 12, 2023

Dear All, Meeting #22 of the SubPro IRT will be held in an hour on 12 December 2023 at 20:00-21:00 UTC [local time<https://www.timeanddate.com/worldclock/fixedtime.html?msg=SubPro+IRT+Meetin…>]. The agenda can be consulted here<https://community.icann.org/x/bpOZDg>. Before the meeting, please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en>. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Zoom information: Join the Zoom Webinar directly (recommended): https://icann.zoom.us/j/98960123523?pwd=SjU0cEtieS9Kc2NZRUNPNGdraGQ0QT09 Meeting ID: 989 6012 3523 Passcode: z6sLS^44@y Zoom Audio only: One tap mobile +13462487799,,98960123523#,,,,*8399371478# US (Houston) +16699006833,,98960123523#,,,,*8399371478# US (San Jose) Dial in directly with your local number: https://icann.zoom.us/u/aIO87mfSF Meeting ID: 989 6012 3523 Passcode: 8399371478 Should you be unable to attend the meeting, please let us know in advance. A recording will be made available. Please do not hesitate to contact us should you have any questions. Best regards, Elisa

1 0