[NCAP-Discuss] Reminder - Please review the Data Sensitivity Study

[Jennifer Bryce]

Hi Tom, hi all,

Apologies for any confusion related to meetings/zoom. There was no meeting this week. NCAP DG meetings resume 12 January at the usual time of 19:00 UTC.

Best,
Jennifer

--
Jennifer Bryce
Project Manager, Office of the Chief Technology Officer (OCTO)
Internet Corporation for Assigned Names and Numbers (ICANN)

Skype: jennifer.bryce.icann
Email: jennifer.bryce at icann.org


From: NCAP-Discuss <ncap-discuss-bounces at icann.org> on behalf of Tom Barrett via NCAP-Discuss <ncap-discuss at icann.org>
Reply to: Tom Barrett <tbarrett at encirca.com>
Date: Thursday, 6 January 2022 at 10:50
To: "Thomas, Matthew" <mthomas at verisign.com>
Cc: "ncap-discuss at icann.org" <ncap-discuss at icann.org>
Subject: Re: [NCAP-Discuss] Reminder - Please review the Data Sensitivity Study

Hi Matthew,

I was unable to attend today's meeting due to receiving zoom error 1001 via various devices and browsers.

I wanted to make just one observation and suggestion.  I'm having some difficulty with the definitiveness of this conclusion:
" A complete and accurate risk assessment of a string’s name collision potential cannot be determined prior to the string's delegation."


I can appreciate the challenge of currently accessing public recursive resolver data as summarized here : "in part due to legal and privacy concerns, it is likely that public resolver data will be even more obscure or scarce in the future.".


However, since this is not a technical issue but rater a "speculative" commercial issue, it appears it might be a solvable problem that could be addressed well before ICANN starts accepting applications for the next round (~in 4-5 years).


What are your thoughts about qualifying your conclusion somewhere along the lines of:
" A complete and accurate risk assessment of a string’s name collision potential cannot be determined prior to the string's delegation, unless ICANN is able to generate or obtain public recursive resolver data prior to the next round of new gTLDs."


best regards,


Tom















[Image removed by sender.][avg.com]<https://urldefense.com/v3/__http:/www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail__;!!PtGJab4!oi-lkWlIKHnv4W56nDqAed7_TjkQnZdhl-0_mvtCJaRMT6ZJKCcC2tsbassyVEGpjsLWXutJIw$>

Virus-free. www.avg.com [avg.com]<https://urldefense.com/v3/__http:/www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail__;!!PtGJab4!oi-lkWlIKHnv4W56nDqAed7_TjkQnZdhl-0_mvtCJaRMT6ZJKCcC2tsbassyVEGpjsLWXutJIw$>


On Tue, Jan 4, 2022 at 8:12 AM Thomas, Matthew via NCAP-Discuss <ncap-discuss at icann.org<mailto:ncap-discuss at icann.org>> wrote:
All,

Happy New Year!

As promised here is a gentle reminder for the group to review the Data Sensitivity Study [1] (PDF version also attached here).  We will be discussing the document at the next NCAP DG call on 1/12/2022.  It is important we reach a final version near the 12th so we can release the document for public comment in conjunction with the already reviewed CORP, HOME, and MAIL case study.

Best,

Matt Thomas

[1]  https://docs.google.com/document/d/1sLPrBn8T6ym7gumySHeWG9THSGSRoEeKldv3uRMMy6Y/edit?usp=sharing [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sLPrBn8T6ym7gumySHeWG9THSGSRoEeKldv3uRMMy6Y/edit?usp=sharing__;!!PtGJab4!oi-lkWlIKHnv4W56nDqAed7_TjkQnZdhl-0_mvtCJaRMT6ZJKCcC2tsbassyVEGpjsLAK9QeuA$>

_______________________________________________
NCAP-Discuss mailing list
NCAP-Discuss at icann.org<mailto: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.


--
Thomas Barrett
President
EnCirca, Inc
+1.781.942.9975 (office)
400 W. Cummings Park, Suite 1725
Woburn, MA 01801 USA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/ncap-discuss/attachments/20220106/fa2f8f3a/attachment-0001.html>