[NCAP-Discuss] Agenda Items for NCAP DG

[Anne ICANN]

Dear Michael, Suzanne, and Matt T,

I have now had time to reread the answers to the Board questions.  I
conclude there are sections that need revision based on the draft Study 2
report.  Please take a very close look at Theme 4: Mitigating Harm,
especially the section called "Proactive Measures to Reduce the Potential
For Harm".  As previously mentioned, I believe this section MUST be revised
to reflect the work done by the DG and to reflect the proposed new Name
Collision Risk Assessment Framework.  In fact, it may be possible to
significantly shorten this section and then cross-reference the proposed
new Name Collision Risk Assessment Framework.  If this is not done, the
answers to the Board Question outlined in Theme 4 appears not to take
account of that work and that is definitely confusing.

In addition, the answers relative to Theme 6: Undelegated Strings and
Collision Strings should be impacted by the work done by the DG and that
work should be integrated into the responses on Theme 6.  At present the
draft responses deal with many of the same issues that have now been
addressed by the Study 2 work and the draft responses don't reflect that
work.  For example, there is no mention of a TRT and no mention of a String
Collision Risk.

In my opinion, it would be a mistake to put these Answers to Board
Questions out for public comment without conforming the responses to the
work done by the DG in Study 2.j  The impression given in the current
draft, in particular in relation to Theme 4 and Theme 6, would be very
disjointed.

Hopefully the Co-Chairs and Michael can see a way forward here by
incorporating reference to the draft Study 2 Report, especially in respect
of Theme 4 "Proactive Measures to Reduce Potential for Harm" - this is the
whole point of Study 2.  Also in respect of Theme 6 - especially the
section on "Criteria for Determining Whether a String Should Not Be
Delegated" - currently no eference to the TRT and the proposed new
Framework.  Alsoi "Criteria for Determining the Removal of a Collision
String from the Do Not Delegate list.   This list is now called the
Collision String List and terms are important and there should be a
reference to Study 2 sections re that list and how, in the Workflow, an
applicant can propose a mitigation plan.

There is substantial work to be done here in connection with the above.

Thank you,
Anne


Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2024
anneicanngnso at gmail.com


On Wed, Jan 10, 2024 at 1:42 PM Michael Puckett <michael.puckett at icann.org>
wrote:

> Hello all,
>
>
>
> In preparation for our meeting at the top of the hour, I’m sharing a list
> of items for the DG to review/discuss during our call. Please see the Outstanding
> NCAP Report Items
> <https://docs.google.com/document/d/1W-pil0kd4WsHGykDTCKcMCMWa3OcTCyhLyb9f2Khm-E/edit>
> doc I’ve been updating for what needs to be done to finalize the report
> rough draft. Link pasted below as well.
>
>
>
> There are various sections of text that need to be reviewed—either because
> of minor changes or more substantive additions/deletions.
>
>
>
> Two sections to note are “*3.6 – Ethical Considerations*” & “*4.5 –
> Notification to users of name collisions…*”. For both sections, large
> rewrites are being made at the bottom of each respective document under a
> heading titled *Candidate Text*.
>
>
>
> Additionally, I would appreciate eyes on the *Board Questions doc* (links
> to all documents in Outstanding NCAP Report Items doc).
>
>
>
> Following our call today, the documents (Sec. 1-3, Sec. 4-5, Board
> Questions) will be open for final input & suggestions *until end of day
> Friday, 10-January 2024*. At that point, the documents will be closed for
> discussion so that I can finalize the documents and compile all sections
> into a single rough draft report, including the three studies completed.
>
>
>
> The full rough draft report will be shared with the group Monday
> 15-January for acceptance by the DG, any final minor changes, and creation
> of a backlog of action items for the final draft. This will allow us to
> deliver the rough draft on time by Wednesday 17-January.
>
>
>
> Looking forward to a productive call with you all very shortly!
>
>
>
> Thanks,
>
> Michael Puckett
>
> Technical Writer, ICANN
>
>
>
>
> https://docs.google.com/document/d/1W-pil0kd4WsHGykDTCKcMCMWa3OcTCyhLyb9f2Khm-E/edit
> _______________________________________________
> NCAP-Discuss mailing list
> NCAP-Discuss at icann.org
> https://mm.icann.org/mailman/listinfo/ncap-discuss
>
> _______________________________________________
> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/ncap-discuss/attachments/20240112/f0fb94f6/attachment.html>