Thanks Nathalie. All, I’ll share this with the ISPs, I think it’s an important group for us to follow, not only in view of subpro but also as a means of improving our knowledge of DNS traffic in general. I’ve reached my own limits of night calls and those are a bit challenging but I do intend to monitor the discussions I also hope we can have a readout to council at some point, but with my councilor’s hat off, I would also hope that ncap can capitalize on the 2012 experience of the “controlled interruption an’ all that”, and whether being overly cautious had been worth the pain for some or any of the hundreds of applications. I may have told the story in corridor discussions but councilors may like the irony of the following example. The TLD from my affiliation was on the infamous Interisle/jas study list with significant pre-existing x.tld traffic on the roots, part of which we knew came from internal sources. We did things right; put an escalation procedure in place, 24/7 email/phone number, emails to CTOs around the planet calling people in the field to reach out in case anything happened, bracing ourselves for judgment day. That fateful day came, TLD went live, we were feverishly staring at our screens, mobile in hand, and then…. Nothing. Not an email, not a call. Nothing. One of the most uneventful days of my professional life. Same after the controlled interruption period. The pre-existing traffic was still there, and still is. I suppose a lot of others had the same experience. If there are counterexamples to this (heard of some), it would be good to focus time, energy (and budget) on those. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Nathalie Peregrine Sent: Monday, May 06, 2019 1:59 PM To: council@gnso.icann.org Subject: [council] ICANN Announcement: Participants for the Name Collision Analysis Project (NCAP) discussion group FYI https://www.icann.org/news/announcement-2-2019-04-17-en LOS ANGELES – 17 April 2019 – The Internet Corporation for Assigned Names and Numbers (ICANN) is seeking participants for the Name Collision Analysis Project (NCAP) discussion group. The NCAP discussion group, as defined by the Security and Stability Advisory Committee (SSAC) proposal and revised by ICANN's Office of the CTO, is an open and public group tasked with discussing issues pertaining to the work of the NCAP Study 1. The NCAP Study 1 was authorized by the ICANN Board of Directors on 14 March 2019. The study will: • examine all prior work on the issue of name collisions and produce a summary report that brings forward important knowledge from prior work into this study, and which can act as a primer for those new to the subject. • create a list of data sets used in past studies, identify gaps, if any, and list additional data that would be required to successfully complete Studies 2 and 3. • decide if the project should proceed based on the results of the survey of prior work and the availability of data. There are two ways to participate in the NCAP discussion group: • Individual participants – Participants are expected to actively contribute to mailing list conversations as well as meetings. Each potential participant will be required to provide a Statement of Interest (SOI) before gaining posting rights to the mailing list. It is anticipated that participants will provide essential input to the process. • Mailing list observers – The position of observer is for those only interested in monitoring the NCAP discussions. Observers are offered read-only access to the mailing list. At any point in time, a mailing list observer can join the NCAP discussion group as a participant simply by submitting a SOI. To operate in a transparent manner, all mailing list exchanges are publicly archived<https://mm.icann.org/pipermail/ncap-discuss/>. All participants are responsible for abiding by ICANN's Expected Standards for Behavior<https://www.icann.org/resources/pages/expected-standards-2012-05-15-en>. To join the Name Collision Analysis Project discussion group, please fill out the following questionnaire<https://docs.google.com/forms/d/1PDlX6sMldP4vLn1LLuefxsup78mLM0iDb8ybWhlw2T4...> by 6 May 2019. Background For more information on NCAP study 1, click here<https://community.icann.org/display/NCAP/NCAP+Working+Documents?preview=/794...>. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine@icann.org <nathalie.peregrine@icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gns...> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.