July 2024 - SubPro-IRT - lists.icann.org

Letter from Board Chair to GAC Chair
by Lars Hoffmann July 3, 2024

July 3, 2024

Dear members of the IRT, In case you are not glued to the ICANN correspondence page, here is the link to Monday’s letter from Tripti to Nico re: recent GAC advice. https://www.icann.org/en/system/files/correspondence/sinha-to-caballero-01j… Best. Lars

2 1

Follow-up: ASP Bid Credit Options
by Kristy Buckley July 3, 2024

July 3, 2024

Greetings IRT members, It was a pleasure meeting with you in Kigali. Thank you again for your inputs to the ASP bid credit discussion. As a follow up from that conversation, there seemed to be interest in exploring whether and how we could combine aspects of Options A and B from the presentation during <https://community.icann.org/download/attachments/322994373/ASP%20Bid%20Cred…> IRT Meeting #48<https://community.icann.org/download/attachments/322994373/ASP%20Bid%20Cred…>. For those who expressed interest in that request, we would like to solicit your feedback on what particular aspects you would like to look at combining so that we can consult the auction experts on those ideas. Please send any additional questions or comments regarding the ASP bid credit on-list by 20:00 UTC Friday, 21 June 2024. This will allow us to continue moving that work forward. Kind Regards, Kristy Buckley, on behalf of the ASP Project Team

4 7

[Review Requested by 5 July 2024] Updated Legal Compliance and Background Screening Sections for Final Review
by Jared Erwin July 2, 2024

July 2, 2024

Dear IRT Members, I’m writing with an update on the Legal Compliance and Background Screening sections, discussed on 20<https://community.icann.org/x/UgCAF> and 25<https://community.icann.org/x/poEEF> June 2024. * Legal Compliance: https://docs.google.com/document/d/1wov5kKCTjUvYa_beZ8pVurla-lt0-Duki_IbKHU… * Re: SDN List -- After discussing with the team, we have opted not to include the link to the actual SDN list but rather the general OFAC page. This is because we feel it may be more useful to provide more context with the general link, and the SDN list is navigable from that link as well. This will be updated in the ASP and RSP handbooks. * There were also a few more additional edits made to clarify the text. * Background Screening: https://docs.google.com/document/d/19kisd4tjCGxwj18wpkG95zsK3t1Eh8Bsm-HWlvM… * Re: removing reference to conducting screening in “two areas” (page 3), the team agreed with the proposed edits, which have been captured in the text * Re: concerns with Onboarding Question 2 (page 5), the team agreed that it is important to clarify this and the proposed edits have been captured in the text Please review and provide any final feedback by 5 July 2024. Thank you very much for work on these sections! Best, Jared -- Jared Erwin Director, New gTLD Program Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) jared.erwin(a)icann.org<mailto:jared.erwin@icann.org>

1 0

Post call | SubPro IRT Meeting #52 | 2 July 2024
by Next Round Policy Implementation July 2, 2024

July 2, 2024

Dear All, The recordings for Meeting #52 of the SubPro IRT held on Tuesday, 2 July 2024 at 13:00-14:00 UTC are published on the meeting wiki page<https://community.icann.org/x/tIEEF>. 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, Renate

1 0

Re: [SubPro-IRT] Predictability Changes
by Lars Hoffmann July 2, 2024

July 2, 2024

Thank you, Jeff, for your message. Am I right in assuming that this message below, and the helpful google doc, essentially replace your message on the same topic from last week? In other words, we only need to go to these proposed changes on today’s call, is that right? Thank you and all the best Lars From: SubPro-IRT <subpro-irt-bounces(a)icann.org> on behalf of Jeff Neuman <jeff(a)jjnsolutions.com> Date: Monday, 1 July 2024 at 23:36 To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [SubPro-IRT] Predictability Changes All, I have had a conversation with some people on the Predictability model who may have had different interpretations of the language as I had. In order to clear things up, I am providing my slight redline to Section 4.1 of this Section, which I think would clear things up so that we are all on the same page. I have placed that language in this Google Doc: https://docs.google.com/document/d/1DUCaJcLK1r54r5fW5pUiYwqeVXeFK12Qw1sO6xe… Essentially my proposal: 1. changes the language to make it clear that the 4 options in this section are not "sequential", but are really four (4) different paths for a change to be made to the program. 1. Re-orders the paths so that they reflect the next page order of paths (reading left to right). 1. Makes Path 3 clear that the GNSO Council can refer any issue it wants to the SPIRT without having to go through ICANN Org. It also clarifies the language that it is the Council who refers things to the SPIRT and not the SPIRT raising issues on its own (which was in the adopted policy recommendations). 1. Recommends 2 slight changes to the boxes in the flow chart to reflect the changes in Path 3. I believe the wording changes are minor, but the concepts are major in the sense that they would be in line with the SubPro Final Report and , if my understanding is correct, would be what was intended. I hope you find this helpful. Sincerely, Jeff [Image removed by sender.]<https://docs.google.com/document/d/1DUCaJcLK1r54r5fW5pUiYwqeVXeFK12Qw1sO6xe…> Jeff's Proposed Predictability Changes<https://docs.google.com/document/d/1DUCaJcLK1r54r5fW5pUiYwqeVXeFK12Qw1sO6xe…> 4.1 Change Request The change request flow chart outlines the procedural steps the Advisory Committee (AC), GNSO Council, ICANN Board, and ICANN org take if they determine a change to the Program is required. Path 1: ICANN org determines a change is required to the Program, ICANN org applies ... docs.google.com [cid:image001.png@01DACC86.65FB4160]

2 1

REMINDER | SubPro IRT Meeting #52 | 2 July 2024, 13:00-14:00 UTC
by Next Round Policy Implementation July 2, 2024

July 2, 2024

Dear All, Meeting #52 of the SubPro IRT will be held in one hour on 2 July 2024 at 13:00-14:00 UTC [local time<https://tinyurl.com/mur4njxs>]. The agenda can be consulted here<https://community.icann.org/x/tIEEF>. 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/97063459905?pwd=VUVsd0J0RnNtRXkyNXJFZW9vdTEzZz09 Meeting ID: 970 6345 9905 Passcode: DQ#0L.9x5e Zoom Audio only: One tap mobile +13462487799,,97063459905#,,,,*5806401747# US (Houston) +16699006833,,97063459905#,,,,*5806401747# US (San Jose) Meeting ID: 970 6345 9905 Passcode: 5806401747 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, Renate

1 0

Predictability Changes
by Jeff Neuman July 1, 2024

July 1, 2024

All, I have had a conversation with some people on the Predictability model who may have had different interpretations of the language as I had. In order to clear things up, I am providing my slight redline to Section 4.1 of this Section, which I think would clear things up so that we are all on the same page. I have placed that language in this Google Doc: https://docs.google.com/document/d/1DUCaJcLK1r54r5fW5pUiYwqeVXeFK12Qw1sO6xe… Essentially my proposal: 1. changes the language to make it clear that the 4 options in this section are not "sequential", but are really four (4) different paths for a change to be made to the program. 2. Re-orders the paths so that they reflect the next page order of paths (reading left to right). 3. Makes Path 3 clear that the GNSO Council can refer any issue it wants to the SPIRT without having to go through ICANN Org. It also clarifies the language that it is the Council who refers things to the SPIRT and not the SPIRT raising issues on its own (which was in the adopted policy recommendations). 4. Recommends 2 slight changes to the boxes in the flow chart to reflect the changes in Path 3. I believe the wording changes are minor, but the concepts are major in the sense that they would be in line with the SubPro Final Report and , if my understanding is correct, would be what was intended. I hope you find this helpful. Sincerely, Jeff [https://lh7-us.googleusercontent.com/docs/AHkbwyIvi-dPKmytHayElgwLpFFxCPYYX…]<https://docs.google.com/document/d/1DUCaJcLK1r54r5fW5pUiYwqeVXeFK12Qw1sO6xe…> Jeff's Proposed Predictability Changes<https://docs.google.com/document/d/1DUCaJcLK1r54r5fW5pUiYwqeVXeFK12Qw1sO6xe…> 4.1 Change Request The change request flow chart outlines the procedural steps the Advisory Committee (AC), GNSO Council, ICANN Board, and ICANN org take if they determine a change to the Program is required. Path 1: ICANN org determines a change is required to the Program, ICANN org applies ... docs.google.com [cid:59a44134-5111-4912-8b6b-4839c5fcc6e2]

1 0

REMINDER | SubPro IRT Meeting #52 | 2 July 2024, 13:00-14:00 UTC
by Next Round Policy Implementation July 1, 2024

July 1, 2024

Dear All, Meeting #52 of the SubPro IRT will be held on 2 July 2024 at 13:00-14:00 UTC [local time<https://tinyurl.com/mur4njxs>]. The agenda can be consulted here<https://community.icann.org/x/tIEEF>. 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/97063459905?pwd=VUVsd0J0RnNtRXkyNXJFZW9vdTEzZz09 Meeting ID: 970 6345 9905 Passcode: DQ#0L.9x5e Zoom Audio only: One tap mobile +13462487799,,97063459905#,,,,*5806401747# US (Houston) +16699006833,,97063459905#,,,,*5806401747# US (San Jose) Meeting ID: 970 6345 9905 Passcode: 5806401747 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, Renate

1 0