- SubPro-IRT - lists.icann.org

REMINDER | SubPro IRT Meeting #3 | 30 May 2023, 13:00-14:00 UTC
by Elisa Busetto May 30, 2023

May 30, 2023

Dear All, The third meeting of the Subsequent Procedures (SubPro) Implementation Review Team (IRT) will be held in one hour, on 30 May 2023 at 13:00-14: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/ToZXDg>. 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

SubPro IRT | Useful information
by Next Round Policy Implementation May 30, 2023

May 30, 2023

Dear All, Please find below some useful information about the SubPro IRT: 1. Please verify if you have access to the shared drive<https://drive.google.com/drive/folders/1CrHArVTtKEXOk2qdLwgq2oDr6Sa9BLwP?us…>. Please disregard the link shared previously - apologies for the confusion. Should you not have access, please send an email to nextround_policyimplementation(a)icann.org<mailto:nextround_policyimplementation@icann.org>. Please note that all documents will also be published on the wiki workspace<https://community.icann.org/x/pQM5Dg> and/or sent to the mailing list, so that you will be able to access them even if you do not have a Google account. 1. As you know, any person participating in an IRT is required to complete a Statement of Interest (SOI). The members of this group<https://community.icann.org/x/qAM5Dg> who already have an SOI are kindly requested to ensure it is up to date. The members who do not yet have an SOI on file are kindly requested to follow the instructions on this page<https://community.icann.org/x/c4Lg> and create one at their earliest convenience. If you do not have or cannot retrieve your login details, or if you have any technical issues, please email nextround_policyimplementation(a)icann.org<mailto:nextround_policyimplementation@icann.org>. Please be as specific as possible in your request so we can address your issue swiftly. 1. If you cannot attend a SubPro IRT meeting, please send an email to the mailing list or to nextround_policyimplementation(a)icann.org<mailto:nextround_policyimplementation@icann.org>. Thank you very much! Please do not hesitate to reach out should you have any questions. Best regards, Elisa

2 1

Re: [SubPro-IRT] Materials for 30 May 2023
by Lars Hoffmann May 29, 2023

May 29, 2023

Hi everyone! I was just informed that at the moment you cannot access the drive folders, just the documents. We will work on a fix. In the meantime, the google document<https://docs.google.com/document/d/1wFZvHTnCDvr9uAAqtqgWf1Ikf_fJd6M2Fxddbi-…> (the only file in that folder for now) should be accessible to all IRT members. Best Lars From: SubPro-IRT <subpro-irt-bounces(a)icann.org> on behalf of Lars Hoffmann <lars.hoffmann(a)icann.org> Date: Friday, 26 May 2023 at 17:34 To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [SubPro-IRT] Materials for 30 May 2023 Hello everyone, A little later than anticipated, I am attaching materials for next week’s IRT call (30 May 2023, 13:00 UTC<https://community.icann.org/pages/viewpage.action?pageId=240617038>). Both these documents have also been uploaded to the wiki space<https://community.icann.org/x/ToZXDg>. For context, the updated workplan contains the following: * Timing estimation for a range of 15-24 months. * Estimated level of complexity for each of the 40 topics * Anticipated number of IRT meetings per topic. * More clarity around the concepts of first and second readings (with or without sleepy voice) * Methodology around the creating of subgroups. * Commitment from ICANN org to submit new topics to the IRT on a regular cadence of 2-4 weeks, with the longer range applicable to the start of the IRT. In addition, we have put together a google document<https://docs.google.com/document/d/1wFZvHTnCDvr9uAAqtqgWf1Ikf_fJd6M2Fxddbi-…> on the chartering of the Standing Predictability Implementation Review Team (SPIRT) [ see also IRT google drive link<https://drive.google.com/drive/u/1/folders/0AEfyW7TE-4_fUk9PVA>].* For those who cannot access google documents, a PDF is also attached. * Please note, this document is a starting point to draft the Charter for the SPIRT not for the Predictability Framework itself. For context: We have taken the output from Annex E of the Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-rep…> and moved it to the google document. We then annotated that text with questions that staff believes the IRT might want to consider finalizing the SPIRT’s charter. SPIRT is a community group, and there are no recommendations on the SPIRT’s chartering. Therefore, while chartering the SPIRT is a necessary step to open the next round, the work to do so should be a community-driven exercise. In preparation for Tuesday, you may want to provide comments directly to the google document - or at a minimum familiarize yourself with Annex E of the final report and review the questions staff added in red to the document. We are looking forward to our next call on Tuesday 30 May. Many thanks and best wishes, Lars *If you have any trouble accessing the drive, please reach out to nextround_policyimplementation(a)icann.org<mailto:nextround_policyimplementation@icann.org>

3 3

REMINDER | SubPro IRT Meeting #3 | 30 May 2023, 13:00-14:00 UTC
by Next Round Policy Implementation May 26, 2023

May 26, 2023

Dear All, The third meeting of the Subsequent Procedures (SubPro) Implementation Review Team (IRT) will be held tomorrow, on 30 May 2023 at 13:00-14: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/ToZXDg>. 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

Materials for 30 May 2023
by Lars Hoffmann May 26, 2023

May 26, 2023

Hello everyone, A little later than anticipated, I am attaching materials for next week’s IRT call (30 May 2023, 13:00 UTC<https://community.icann.org/pages/viewpage.action?pageId=240617038>). Both these documents have also been uploaded to the wiki space<https://community.icann.org/x/ToZXDg>. For context, the updated workplan contains the following: * Timing estimation for a range of 15-24 months. * Estimated level of complexity for each of the 40 topics * Anticipated number of IRT meetings per topic. * More clarity around the concepts of first and second readings (with or without sleepy voice) * Methodology around the creating of subgroups. * Commitment from ICANN org to submit new topics to the IRT on a regular cadence of 2-4 weeks, with the longer range applicable to the start of the IRT. In addition, we have put together a google document<https://docs.google.com/document/d/1wFZvHTnCDvr9uAAqtqgWf1Ikf_fJd6M2Fxddbi-…> on the chartering of the Standing Predictability Implementation Review Team (SPIRT) [ see also IRT google drive link<https://drive.google.com/drive/u/1/folders/0AEfyW7TE-4_fUk9PVA>].* For those who cannot access google documents, a PDF is also attached. * Please note, this document is a starting point to draft the Charter for the SPIRT not for the Predictability Framework itself. For context: We have taken the output from Annex E of the Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-rep…> and moved it to the google document. We then annotated that text with questions that staff believes the IRT might want to consider finalizing the SPIRT’s charter. SPIRT is a community group, and there are no recommendations on the SPIRT’s chartering. Therefore, while chartering the SPIRT is a necessary step to open the next round, the work to do so should be a community-driven exercise. In preparation for Tuesday, you may want to provide comments directly to the google document - or at a minimum familiarize yourself with Annex E of the final report and review the questions staff added in red to the document. We are looking forward to our next call on Tuesday 30 May. Many thanks and best wishes, Lars *If you have any trouble accessing the drive, please reach out to nextround_policyimplementation(a)icann.org<mailto:nextround_policyimplementation@icann.org>

1 0

SubPro IRT Meeting #4 | 14 June 2023, 13:00-14:15 UTC / 09:00-10:15 EDT
by Next Round Policy Implementation May 26, 2023

May 26, 2023

Dear All, The fourth meeting of the SubPro IRT will be held on 14 June 2023 at 13:00-14:15 UTC / 09:00-10:15 EDT [local time<https://www.timeanddate.com/worldclock/fixedtime.html?msg=SubPro+IRT+Meetin…>] during ICANN77 in Washington, D.C., United States, in a hybrid format. Up-to-date information on the session is published on this page<https://sched.co/1NMu8>, and the agenda is available here<https://community.icann.org/x/NoZXDg>. 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>. In addition, 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. 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

SubPro IRT Meeting #3 | 30 May 2023, 13:00-14:00 UTC
by Next Round Policy Implementation May 26, 2023

May 26, 2023

Dear All, The third meeting of the Subsequent Procedures (SubPro) Implementation Review Team (IRT) will be held on 30 May 2023 at 13:00-14: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/ToZXDg>. 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

3 2

Post Call | SubPro IRT call | Tuesday, 23 May 2023
by Next Round Policy Implementation May 24, 2023

May 24, 2023

Dear all, The Zoom recording for the Subsequent Procedures (SubPro) Implementation Review Team (IRT) call held on 23 May 2023 at 20:00-21:00 UTC is now available on the agenda wiki page.<https://community.icann.org/pages/viewpage.action?pageId=240617030> For additional information, please consult the mailing list archives<https://mm.icann.org/pipermail/subpro-irt/> and the main wiki page<https://community.icann.org/display/SPIR>. Thank you! Best, Michael

1 0

Work Plan is way too conservative and we need to do better......
by jeff＠jjnsolutions.com May 24, 2023

May 24, 2023

Dear SubPro Team, Background I have been doing a bunch of thinking on the proposed work plan and I really believe we need to push much harder on the timelines being proposed and that we need to be much more aggressive. For those of you that do not know me, I was one of the co-chairs of the SubPro Working Group with Cheryl, so we have been living and breathing all of this for years. But in addition to that, I have participated in every one of ICANN's new gTLD rounds (starting in 2000), and have implemented not only hundreds of policies for registries, but I have also personally been involved in the launch of hundreds of TLD registries. From 2011-Jan 2015, I was responsible for the Neustar Registry business that included supporting hundreds of new gTLD applications both as front and back-ends, but also included the launch of most of those TLDs. Specific Comments to Workplan According to the Workplan, it says that Modules 1-3 (as ICANN has designated will take about a year. Then Modules 4-8 are listed as each one taking 3-4 months and operating serially one after the other. And Modules 9 and 10 are not even included in the scheduling (which I am hoping means they will be overlapping). It should be noted, however, that as far as I can tell, Module 1 overlaps with practically every other Module and once we get done with Module 1, that constitutes the bulk of the work. For example, the following topics seem to be in Module 1: Predictability - which would include the SPIRT Applicant Freedom of Expression Different TLD Types Conflict of Interest Applications Assessed in Rounds (Overlaps with Module 2) Metrics / Monitoring Dispute Resolution Procedures - Question Why is this not covered in Module 4? Reserved Names - If this refers to the top-level, fine; but second level is more Module 6 GAC Consensus Advices / Early Warnings IDNs Auctions / Resolution of Contention Sets Registry/Registrar Standardization / Registrar Non-Discrimination (Should be in Module 6) Comments on Modules 1-5 will come separately. But I wanted to comment on Modules 6-8 and the Workplan. There is no reason why Modules 6, 7 and 8 (contracting, Post-Contracting, and Terms and Conditions should take 3-4 months each (for 9-12 months total). Realistically, there is no reason these 3 modules should take any longer than 2 months combined. That alone would shave off 7-10 months off the plan). This is because: a) Module 6 - Contracting: Topics 36-38 of Final Report - I honestly believe this can be done in a couple of weeks 1. Topic 36- The final report contains 2 Affirmations and 2 Recommendations, namely: Affirmation of the 2007 policy which is already included in the 2013 Base Registry Agreement as amended....so this affirmation does not require any work. Affirmation of the use of "Specifications" - No additional work required Recommendation that ICANN add a contractual provision stating that Registry Operator will not engage in fraudulent or deceptive practices. - No IRT work needed Recommendation that there should be some opportunity to negotiate contracts / exemptions subject to notice and comment in cases where there are unique aspects of strings or operators and provides ability to accommodate changing marketplace. This one will require a little work, but overlaps with TLD Types in Module 1 2. Topic 37: Registrar Non-Discriminating / Registry/Registrar Standardization. This is already in Module 1, but really should only be here. 1 recommendation: which states that Registries must use only ICANN accredited Registrars in registering domain names, and may not discriminate among such accredited registrars unless an exemption to the Registry Code of Conduct is granted as stated therein,provided, however, that no such exemptions shall be granted without public comment.” This has already been implemented except for one thing.....Only thing added here is that if a Registry seeks an exemption to the Code of Conduct, there should be a comment period before granting the request. 3. Topic 38: Registrar Support for new TLDs - This one is just an affirmation which requires no new implementation at all. It just states that registrars can determine which TLDs it wants to offer. Module 7 : Post Contracting - I believe this can be done in 2 weeks at most I assume this relates to Topics 39-41 of the Subpro Final Report a) Registry System Testing 6 Recommendations here which essentially state that the ICANN should develop testing to demonstrate the technical capabilities of the registry which includes testing readiness for DNSSEC. It states that testing must be efficient and need not be done multiple times for the same operator it that operator supports multiple TLDs. Then it calls for the implementation of 2 recommendations that were already contained within the ICANN staff's own Program Implementation Review Report in 2016 or so. b) TLD Rollout: This contains 2 affirmations of what was done in 2012. No new implementation work needed. c) Contractual Compliance - consists of an affirmation of the sanctions policy (already in place) and a recommendation for ICANN Compliance to publish more stats on rationale for closing cases (Mostly implemented already). Module 8: Terms and Condition - Only real work is (d) below. My time estimate: 3 weeks at most. 4 Recommendations; 3 Implementation Guidance a) ICANN should only reject applications if done so in accordance with Guidebook, Bylaws, laws, etc. This recommendation is being discussed with GNSO/Board, but if accepted this requires a very limited couple of words being changed. b) ICANN should publish specific reason by applications are rejected but should avoid disclosing confidential information. - Requires no new implementation in advance. c) Ts and Cs should only have covenant not to sue if there is an appeals/challenge process. This is still being discussed, but at end of day, if there is no appeals, then implementation is crossing out covenant not to sue. If there is one, implementation is keeping things the way they are. No new work likely. d) Refunds - This one will require some implementation work to define circumstances where refunds will be given due to changes made in the program where such changes materially impact applicants. - Note this is being discussed with Board, but assuming Board approves, then work here is just coming up with a definition of "material impact" and ensuring that is not gamed. e) Name Collisions - if ICANN cannot delegate a TLD because of name collision reasons, then a full refund should be given. No real new implementation work. f) Confidential portions of applications should only be disclosed to those with a need to know...my paraphrasing. But no new implementation work here really because this is standard in all Non-disclosure agreements.

11 13

REMINDER | SubPro IRT Meeting #2 | 23 May 2023, 20:00-21:00 UTC
by Next Round Policy Implementation May 23, 2023

May 23, 2023

Dear All, The second meeting of the Subsequent Procedures (SubPro) Implementation Review Team (IRT) will be held on 23 May 2023 at 20:00-21:00 UTC [local time<https://www.timeanddate.com/worldclock/fixedtime.html?msg=SubPro+IRT+Meetin…>]. The draft agenda and background documents can be consulted here<https://community.icann.org/x/RoZXDg>. 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, Michael

3 3