Thank you for the very insightful session this morning (and to Jim as well). It would be great and necessary to know, upon release of the Name Collision Observatory access and relevant documents, the data source(s) of the Observatory. -- Ching On Wed, Jan 8, 2025 at 11:02 AM Mike Rodenbaugh via SubPro-IRT < subpro-irt@icann.org> wrote:

We also need to know what documents will be made public, and when, wrt mitigation requirements for particular strings, proposed mitigation plans, ICANN comments on plans, and approved plans.

Thank you, Mike

[image: Logo]

Mike Rodenbaugh

*Rodenbaugh Law LLC*

email:

mike@rodenbaugh.com

phone:

+1 (415) 738-8087

On Wed, Jan 8, 2025 at 11:54 AM Pruis, Elaine via SubPro-IRT < subpro-irt@icann.org> wrote:

...

Thanks for this helpful discussion and especially to Jim Galvin for providing SSAC / NCAP report insights.

One area we didn’t cover in detail is the Name Collision Observatory access—ICANN folks, since this will be available sometime this spring, could we see proposed licensing agreement language? Given that there will be data applicants review and potentially store and use in mitigation plans, it would be helpful to see what limitations and rights are being considered.

Thanks much

Elaine

*From: *Next Round Policy Implementation via SubPro-IRT < subpro-irt@icann.org> *Reply-To: *Next Round Policy Implementation < NextRound_PolicyImplementation@icann.org> *Date: *Wednesday, January 8, 2025 at 7:10 AM *To: *"subpro-irt@icann.org" <subpro-irt@icann.org> *Subject: *[EXTERNAL] [SubPro-IRT] Post call | SubPro IRT Meetings #100a | 8 January 2025

*Caution:* This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Dear All,

The recording for Meeting #100a of the SubPro IRT held on Wednesday, 8 January 2024 at 13:00-14:00 UTC are published on the meeting wiki page <https://secure-web.cisco.com/1nQ0YLeKkbP2zr74e4L58BfTJtwfmNSA29Xb0zv7ZhCYuDP...>

These include:

- Audio recording - Zoom recording (including audio, visual, rough transcript, chat) - Attendance

For additional information, you may consult the mailing list archives <https://secure-web.cisco.com/1v6u_ProExeNDNkBTbydh_yap9aBriVBDLI1zbNuUUVuoWM...> and the main wiki page <https://secure-web.cisco.com/1KmRIZUyelAOaIvc8tnCVbAqPremZiKSU26wY1bjntvWBGz...> .

Best regards,

Renate

_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to subpro-irt-leave@icann.org

_______________________________________________ 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.

_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to subpro-irt-leave@icann.org

_______________________________________________ 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.

Hi Mike,

On 8 Jan 2025, at 16:01, Mike Rodenbaugh via SubPro-IRT <subpro-irt@icann.org> wrote:

We also need to know what documents will be made public, and when, wrt mitigation requirements for particular strings, proposed mitigation plans, ICANN comments on plans, and approved plans.

ICANN org plans to publish the findings of the initial assessment, as was the case in the last round. If a string which undergoes temporary delegation is classified as high-risk as a result, the Technical Review Team (TRT) will produce a report which will be published. ICANN org’s preference would be for Mitigation Plans to be published by default, but there are risks associated with doing so (such as malicious interference) which must be acknowledged. Our current thinking is that, if approved, Mitigation Plans will be published unless the applicant and ICANN agree that doing so would jeopardize the effectiveness of such plans, in which case, publication would be delayed until after those mitigations have been implemented, and their effectiveness has been confirmed. Regards, -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org

Hi Mike,

On 10 Jan 2025, at 16:11, Mike Rodenbaugh <mike@rodenbaugh.com> wrote:

Hi Gavin,

Thanks for the prompt reply. I think we need to understand better what are the potential "associated risks" of publishing Mitigation Plans (including malicious interference). What is that risk exactly? And what are any other perceived risks? Further, what documented criteria would ICANN and the Applicant use to decide this question, and how would that decision be reviewed by anyone else?

The risk is of malicious interference, where an actor tries manipulate "Critical Diagnostic Measurements" (CDMs) to make it seem that mitigation actions were not effective, when in fact they were. In such circumstances, temporarily postponing the publication of the plan if there is a reasonable likelihood of manipulation seems appropriate. Regards, -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org