Thank you everyone for getting this finished!
Matt Thomas
From: NCAP-Discuss <ncap-discuss-bounces(a)icann.org> on behalf of Michael Puckett <michael.puckett(a)icann.org>
Date: Saturday, 6 April 2024 at 02:05
To: "ncap-discuss(a)icann.org" <ncap-discuss(a)icann.org>
Subject: [EXTERNAL] [NCAP-Discuss] Final Report Docs
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.
Hello all,
Please find attached PDF copies of the finalized Study Two Report and Board Responses document. Additionally, the links to the docs in Google Drive are listed below.
Study Two Report: https://docs.google.com/document/d/1TO8uQf_17DwITy-jQUvPfDR9dcIk7nX_KLjjKQ0…
Board Responses: https://docs.google.com/document/d/1XoDIdQ-z8lnsd2JIQNmbghHLyAZ6IEWaAWZZOMl…
Thanks,
Michael Monarrez Puckett
Hello team!
Here’s a link to the completed Annex of public comments received, NCAP DG
responses, and report changes adopted.
Please review the responses in column 4 (NCAP DG Response) and leave a
comment in the document should you have any concerns or suggestions.
https://docs.google.com/document/d/1QXc6giTfSRsfLtvxJjzrHzFT1aCPuJgALFVPWZU…
I’m currently in the process of editing the report based upon the DG’s
responses to public comments. I will share those edits with the group as
soon as possible—by tomorrow or Wednesday at the very latest.
Having the report edits reviewed and approved (or else modified based on
feedback) prior to next week’s meeting would be ideal.
Thanks!
Michael
———
Focal points for report edits:
- Operationalization of TRT and implementation of Name Collision Risk
Assessment Framework should be expeditious, for which ICANN org would need
to provide sufficient resources.
- TRT should have the responsibility to remove a string from the String
Collision List upon finding that the risk of collision has been
appropriately mitigated.
- All strings should be subject to a typical technical evaluation process
without preferential review treatment for any grouping of strings. The
implementation of special procedures for certain types of strings based
upon policy adoption is out of scope for this report.
- Further research by the ICANN community will be necessary based on
evolutions in the DNS and name resolution issues.
- The data collection methods proposed for the TRT are a small sampling of
known and tested methods. Other methods may be used, but they remain
untested and are out of scope within this report. Ultimately, which methods
to use should be critically considered during the operationalization of the
TRT.
- The NCAP DG deliberated on the proposed data collection methods as a
sample of possible and available methods based upon careful consideration
and balance of data privacy risks and potential benefits.
- Data that is presently available to the public, which applicants could
use to self-assess their applications is constrained.
- The data to be made publicly available to applicants should be
recommended by the TRT during its implementation based upon critical focus
of data sources that would strengthen applications.
- The TRT should distribute time frames to the public as early as possible
for stages of the Name Collision Risk Assessment Framework based on
implementation details.
- Updated the agreed-upon definition of “name collision” within the report
based on the response from ICANN org.
- The NCAP DG does not find it within its remit to provide specific
guidance on elements of the operationalization of the Technical Review Team
and the Name Collision Risk Assessment Framework, including what data to
collect, how to assess this data, and how to maintain compliance with data
privacy and risk management standards. The intent of not prescribing
implementation details is for ICANN org to have broadly lateral oversight.
- The ICANN org would need to implement a data privacy and protection
policy, along with appropriate risk mitigation measures for legal
compliance.
Dear NCAP DG members,
Please find attached the notes from the DG meeting held on Wednesday 27 March at 20:00 UTC.
The notes are also posted to the meeting record on the wiki: https://community.icann.org/x/WwMZEw
The recording can be directly accessed here: https://icann.zoom.us/rec/share/zMg4KtcXp16Cx87V_uQrTzICIzFMOTtfXTnAgwav0al…
Best,
Jonathan
Jonathan Phillips
Operations Coordinator, Office of the CTO (OCTO)
Internet Corporation for Assigned Names and Numbers (ICANN)
Phone: (310) 804-6360
[ICANN Brand Identity Guide - Confluence]
www.icann.org
Dear NCAP Discussion Group,
The next (and it should be the last!) DG meeting is scheduled for Wednesday 27 March at 20:00 – 21:30 UTC.
We will use this time to finalize edits to the draft Study 2 documents, and respond to any comments or questions that people have come up with in reviewing the documents.
Agenda
1. Welcome, roll call, SOI updates
2. Walkthrough and finalize edits to the draft Study 2 documents:
* Edits to draft report<https://docs.google.com/document/d/1TO8uQf_17DwITy-jQUvPfDR9dcIk7nX_KLjjKQ0…> based on public comments
* Annex: Public Comments Analysis<https://docs.google.com/document/d/1QXc6giTfSRsfLtvxJjzrHzFT1aCPuJgALFVPWZU…>
3. Next steps to finalize the documents for handover to SSAC
4. AOB, close
Best,
Jennifer
--
Jennifer Bryce
Project Manager, Office of the Chief Technology Officer (OCTO)
Internet Corporation for Assigned Names and Numbers (ICANN)
www.icann.org<http://www.icann.org>
