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

REMINDER | SubPro IRT Meeting #26b | 6 February 2024, 14:00-15:30 UTC
by Next Round Policy Implementation Feb. 6, 2024

Feb. 6, 2024

Dear All, Meeting #26b of the SubPro IRT will be held in one hour on 6 February 2024 at 14:00-15:30 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/NYQYEQ>. 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

REMINDER | SubPro IRT Meeting #26b | 6 February 2024, 14:00-15:30 UTC
by Next Round Policy Implementation Feb. 5, 2024

Feb. 5, 2024

Dear All, Meeting #26b of the SubPro IRT will be held on 6 February 2024 at 14:00-15:30 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/NYQYEQ>. 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

REMINDER | SubPro IRT Meeting #26b | 6 February 2024, 14:00-15:30 UTC
by Next Round Policy Implementation Feb. 2, 2024

Feb. 2, 2024

Dear All, Meeting #26b of the SubPro IRT will be held on 6 February 2024 at 14:00-15:30 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/NYQYEQ>. 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

Re: [SubPro-IRT] Public comment
by Lars Hoffmann Feb. 2, 2024

Feb. 2, 2024

Dear all, My copy and paste skills clearly need a refresher. Here is a link that should work: https://www.icann.org/en/public-comment/proceeding/proposed-language-for-dr… Best. Lars From: SubPro-IRT <subpro-irt-bounces(a)icann.org> on behalf of Lars Hoffmann <lars.hoffmann(a)icann.org> Date: Friday, 2 February 2024 at 09:49 To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [SubPro-IRT] Public comment Dear IRT members, The public comment went live yesterday. See the announcement here: https://www.icann.org/en/public-comment/proceeding/proposed-language-for-dr… Please remind your respective community groups that we are not planning on grating extensions to the deadline -which is already longer than the standard 40 days to take into account for ICANN79. Best wishes. Lars

1 0

Post call | SubPro IRT Meeting #26a | 1 February 2024
by Next Round Policy Implementation Feb. 2, 2024

Feb. 2, 2024

Dear All, The recordings for Meeting #26a of the SubPro IRT held on Thursday, 1 February 2024 at 20:00-21:30 UTC are published on the meeting wiki page<https://community.icann.org/x/LoQYEQ>. 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

Public comment
by Lars Hoffmann Feb. 2, 2024

Feb. 2, 2024

Dear IRT members, The public comment went live yesterday. See the announcement here: https://www.icann.org/en/public-comment/proceeding/proposed-language-for-dr… Please remind your respective community groups that we are not planning on grating extensions to the deadline -which is already longer than the standard 40 days to take into account for ICANN79. Best wishes. Lars

1 0

REMINDER | SubPro IRT Meeting #26a | 1 February 2024, 20:00-21:30 UTC
by Next Round Policy Implementation Feb. 1, 2024

Feb. 1, 2024

Dear All, Meeting #26a of the SubPro IRT will be held in one hour on 1 February 2024 at 20:00-21:30 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/LoQYEQ>. 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

Review of RST Test Specifications
by Next Round Policy Implementation Feb. 1, 2024

Feb. 1, 2024

Dear IRT members, An IRT meeting focused specifically on the Registry System Testing (RST) will be held on 13 February 2024 at 14:00-15:00 UTC. For more information, please refer to the meeting page: * https://community.icann.org/x/boPxDg As you may be aware, as part of our Next Round activities, ICANN org has been working on a new Registry System Testing (RST) service (RST v2.0), which includes a new set of test specifications and a RESTful API that will fully automate the process of testing, for both the RSP Evaluation Program, as well as Pre-Delegation Testing and post-delegation RST. Details of the new test specifications and the API were provided during ICANN78 in Hamburg[1] and the IRT RST Sub-Track Meeting #1 on 14 December 2023[2]. Since those meetings, we have made significant progress on developing the test specifications and the API specification, both of which have been published on GitHub: * https://icann.github.io/rst-test-specs/rst-test-specs.html * https://icann.github.io/rst-api-spec/rst-api-spec.html As we are approaching the anticipated Public Comment period (planned to begin at the end of March) for the RST v2.0 project, we are inviting members of the IRT and the TLD technical community to provide their feedback on the test and API specifications. The RST test specifications are broken down into ten separate test plans[3], each covering a particular scenario. For RSP evaluation, the relevant plans are the Main RSP Evaluation Test, IDN Test (RSP Evaluation), DNS RSP Evaluation Test, DNSSEC RSP Evaluation Test, and SRS Gateway RSP Evaluation Test. Each test plan uses one or more test suites[4], each of which covers a different registry service, such as EPP, RDAP, DNS, DNSSEC, Data Escrow, etc. Each test suite uses one or more test cases that test a specific component of that registry service. Each test case is tagged with a “Maturity” level, which is one of “ALPHA”, “BETA” or “GAMMA”. As of writing, most test cases are at BETA level or higher: while we welcome all feedback, we encourage you to avoid spending too much time reviewing the ALPHA-level cases, as these are the ones most likely to change in the future. To provide stability and predictability, we have moved to a weekly release process, where the test specifications are only updated once per week (on a Wednesday). Each release will be accompanied by a Change Log, which can be found: * https://icann.github.io/rst-test-specs/rst-test-specs.html#change-log If you are interested in seeing the most up to date version of the specifications, they are available in the “dev” branches of the GitHub repositories: * https://github.com/icann/rst-test-specs/tree/dev * https://github.com/icann/rst-api-spec/tree/dev Submitting Feedback We request to use GitHub to submit feedback. Each of the above repositories has its own issue tracker that can be used to submit feedback. You will need a GitHub account in order to submit issues. Current system For your reference, you may find the test specifications of the current RST system in the following link: https://www.icann.org/resources/registry-system-testing [1] https://community.icann.org/pages/viewpage.action?pageId=264372276 [2] https://community.icann.org/pages/viewpage.action?pageId=282951922 [3] https://icann.github.io/rst-test-specs/rst-test-specs.html#test-plans [4] https://icann.github.io/rst-test-specs/rst-test-specs.html#test-suites Best regards, Gustavo, Gavin, and Elisa

1 0