- gtld-tech - lists.icann.org

Call for Presentations Hybrid TechDay ICANN 85 Mumbai
by Dr Eberhard W Lisse Feb. 16, 2026

Feb. 16, 2026

vTechDay at ICANN 85 (Mumbai) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 85 meeting (Monbay) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2025-10-27 for blocks: Block 2 10:30 - 12:00 (90 Min) Block 3 13:15 - 14:30 (75 min) Block 4 15:00 - 16:00 (60 min) Block 5 16:30 - 17:30 (60 min) All times are local (Mumbai) time. We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. UA/IDN In this respect we are anticipating a round table organized by the ccNSO-UA Committee. Please engage with them via email at ccnso-uacommittee(a)icann.org, keeping us in copy at ccNSO-techday(a)icann.org. 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. Open Source Tools that have been found helpful a) We would in particular like to hear about git based DNS zone management, especially simple setups usable as example for other (smaller) (cc|g)TLDs. b) We would also like to hear about further RDAP client implementations for the command line, devices and libraries. If there are enough proposals we might have round tables. 5. In addition, we welcome suggestions for additional topics If you are interested in presenting on any other topic, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 2

.taipei zone access via czds
by Jan Schaumann Jan. 14, 2026

Jan. 14, 2026

Hey, Talking about having trouble getting access to certain zones: Has anybody here been able to get access to the .taipei zone? I've repeatedly submitted requests that were always shut down with a note saying: --- Reason: Requester did not provide correct or legitimate credentials (explain why) Explanation: Please provide a complete address, a telephone number and associated FTP IP address and resubmit your request for approval. --- For each request, I _did_ in fact provide all that information. I've also tried to reach out to the contacts listed on https://www.iana.org/domains/root/db/taipei.html / whois, but the technical contact never replied and the administrative contact email address bounces. (I've filed a request with ICANN to update the information.) If anybody here managed to get access to the zone, would you mind sharing how you went about that? Thanks! -Jan

3 2

.TOP made inactive? (CZDS zone file access)
by John McCormac Jan. 12, 2026

Jan. 12, 2026

Just got an e-mail that ZFA for .TOP had been revoked as the gTLD had been made inactive. "Request revoked as TLD has been made inactive." Checked another stats site and it was showing 0 domain names in the zone which may indicate that it didn't get today's zone. Has .TOP gTTLD been made inactive or is this a problem on the CZDS or with the .TOP registry? Regards...jmcc -- ********************************************************** John McCormac * e-mail: jmcc(a)hosterstats.com MC2 * web: http://www.hosterstats.com/ 22 Viewmount * Domain Registrations Statistics Waterford * Domnomics - the business of domain names Ireland * https://amzn.to/2OPtEIO IE * Skype: hosterstats.com ********************************************************** -- This email has been checked for viruses by Avast antivirus software. www.avast.com

6 11

Name Collision IPv6 Research Study - Public Comment
by Francisco Arias Oct. 30, 2025

Oct. 30, 2025

Dear colleagues, ICANN has opened a public comment period on a research study titled "Controlled Interruption IPv6 Research Study". The study focuses on extending ICANN's "controlled interruption" mechanism, previously implemented using only the IPv4 address 127.0.53.53 into the IPv6 realm, given the growing adoption of IPv6 (> 40 % of hosts). The public comment period runs from 20 October 2025 to 22 December 2025: https://www.icann.org/en/public-comment/proceeding/name-collision-ipv6-rese… Controlled interruption is a phase in the establishment of a new generic top-level domain (gTLD) that is designed to reduce the risk of name collision. During controlled interruption, certain DNS resource records, designed to interrupt resolution processes, are temporarily published at and below the gTLD name. The content of these DNS records is intended to minimize any harm that arises from such interruption. This study produces an initial list of candidate prefixes, followed by technical tests of multiple applications on popular end-user operating systems. The aim was to identify candidate addresses where DNS lookups returning that address did not result in any unintended external network traffic. A preferred candidate that met these criteria was identified: ffff:127.0.53.53, which is the IPV6 mapping of the original IPv4 controlled interruption address. -- Francisco.

1 0

2nd Call for Presentations Hybrid TechDay ICANN 84 Dublin
by Dr Eberhard W Lisse Sept. 30, 2025

Sept. 30, 2025

All We have 15 minutes left in Block 5. el On 2025/08/26 18:00, Eberhard W Lisse via Ccnso-members wrote: > vTechDay at ICANN 84 (Dublin) > > The ICANN Tech Working Group is again planning a technical workshop > at the ICANN 84 meeting (Dublin) > > As the meeting will be hybrid so will be vTechDay which is currently > penciled in for Monday, 2025-10-27 for blocks: > > Block 2 10:45 - 12:15 > Block 3 13:15 - 14:30 > Block 4 15:00 - 16:00 > Block 5 16:30 - 17:30 > > All times are local (Dublin) time. > > We shall try to accommodate the time zone of virtual presenters in > setting the agenda. > > The TechDay workshop has been a part of ICANN meetings since 2006 > and has provided a forum for both experienced and new people to > meet, present and discuss technical topics related to registry and > DNS work and security. > > We are specially interested in: > > 1. DNSSEC > > 2. DNS Abuse Prevention and Mitigation Tools > > 3. Best (security) management practices, lines of defense, to > protect Registries from bad actors, attacks or malware, or even > reports of failures > > 4. Open Source Tools that have been found helpful > > a) We would in particular like to hear about git based DNS zone > management, especially simple setups usable as example for other > (smaller) (cc|g)TLDs. > > b) We would also like to hear about further RDAP client > implementations for the command line, devices and libraries. > > If there are enough proposals we might have round tables. > > 5. In addition, we welcome suggestions for additional topics > > > The ccNSO's DNS Abuse Committee has expressed an interest in > organizng a round table looking at detection/end-to-end case studies > from a (cc)TLD perspective and we are proposing Block 2 (ie 75 > minutes (including the opening remarks)). > > Interest in participating should be expressed by email to eitheror > all of > > Nick.Wenban-Smith(a)nominet.uk bruce.tonkin(a)auda.org.au > bart.boswinkel(a)icann.org > > keeping us in copy at ccNSO-techday(a)icann.org. > > If you are interested in presenting on any other topic, please email > us at ccNSO-techday(a)icann.org or reply to this email. > > We hope that you can join us and request that you disseminate this > Request to other lists where it might of interest. > > greetings, el > -- Eberhard W. Lisse \ /Obstetrician & Gynaecologist (retired) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht\ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

FW: ROW14 agenda & registration
by Hollenbeck, Scott Sept. 23, 2025

Sept. 23, 2025

FYI, folks. Remember, the workshop is scheduled for next Tuesday the 30th. Scott From: 'Row' via Regiops <regiops(a)googlegroups.com> Sent: Tuesday, September 23, 2025 7:43 AM Subject: [EXTERNAL] [regiops] ROW14 agenda & registration 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. ROW14<https://secure-web.cisco.com/1FGeiw9amzg3JmN8pZKPdUcQ-WKH-_NNoNBqm2u4j-Upa7…> Register now! | September 30th, 2025 | 13:00 - 17:00 UTC | Online Event The Program Committee<https://secure-web.cisco.com/1VuXiIxdyMpWjt0CKYlU24C98F_NoVU3q4IEjv3qZAJcvO…> is pleased to share the final agenda<https://secure-web.cisco.com/17yWS-FNuMlLLryBoC-B6WIe9-kj5E6fLgBNoJEbfams-J…> for ROW14, featuring insights into upcoming discussions and presentations. Presentation materials will be available on our website 24 hours before the session. Session recording will be posted within 24-48 hours after the event. 1. The Current State of RDAP - Andy Newton [ICANN] 2. Organization Validation PKI Certificate Automation with DNSSEC-Signed Attestations - Werner Staub [CORE Association] 3. An Update from the CENTR Registry Lock Task Force - Eric Skoglund [The Swedish Internet Foundation] 4. Provisioning Related Groups of Domain Objects in EPP - James Galvin [Identity Digital] 5. Towards an Industry Best Practice for DNSSEC Automation - Peter Thomassen [deSEC] 6. Domain Connect - a missing piece in DNS toolbox - Pawel Kowalik [DENIC eG] 7. Minimizing DNS Abuse in .lk Domains - A Balanced Approach Using Threat Intelligence and Domain Policies - Harsha Saparamadu [LK Domain Registry (.lk ccTLD)] 8. NIS2 Implementation in .at – Processes and EPP Extension - Alexander Mayrhofer [nic.at GmbH] 9. RDAP Bootstrap in Practice: Updates and Change Planning - James Mitchell [IANA] 10. Panel: Responsibly Bridging the Web2/Web3 Divide >>> Registration is required to enable participation! Attendance is free, but registration<https://secure-web.cisco.com/1SK2qcC4JTE560PYl2U1OJraxk0TwNfxRLhWst02Yt5CQY…> is required to receive Zoom login credentials. ROW events are open to all members of the domain name industry, including representatives from address, gTLD, and ccTLD registries, domain name registrars and resellers, second-level domain operators, academic institutions, and other interested stakeholders. >>> Workshop format To enhance engagement, this ROW session will place greater emphasis on the workshop aspect of the event. ••••••••• Each speaker will have 15 minutes for their presentation. The agenda includes two grouped Q&A sessions: o Q&A – Session A: For Presentations 1–5 (28 minutes) o Q&A – Session B: For Presentations 6–9 (28 minutes) ••••••••• The Panel session, planned at the end of the workshop, will explore various operational issues surrounding the responsible integration of Web3 domains into the existing public DNS infrastructure. The discussion, including panel questions and floor engagement, will be guided by our moderator as time permits. >>> Attendee Participation ••••••••••••••••••••• All attendees will be muted during the session. ••••••••• Please use the Zoom Q&A feature to submit questions or comments. ••••••••• Our session moderator will relay the questions to the speakers or may invite attendees to read their questions aloud. Unanswered questions will be addressed in the Q&A window or followed up by email after the session. >>> Zoom Here are some special tips if this is your first time using Zoom or you wish to get more familiar with its web conferencing capabilities: ••••••••• Download<https://secure-web.cisco.com/1FVXb0hLabXFV9ARGSRfInZ9P5YHZWjnf8Njkc7QLEFBNW…> the Zoom application to your computer or mobile phone or run Zoom from your web browser by navigating to join.zoom.us<http://secure-web.cisco.com/1WpHQXrzbzds-Ck5mDNf28WQIYNCa4E0vdct3WuUQon_ync…> and entering the meeting number and passcode. ••••••••• Want to try it out before ROW14? Join a Zoom test meeting<https://secure-web.cisco.com/1VB1gZOeAKcpH0It9egq2oCjiPdtwXjQNOkRhk4zw0jReB…> or access Zoom tutorials<https://secure-web.cisco.com/1wM50An4HHUjGQ5ihg-nRoK00nqMUJkladPntwGTSSseLV…>. If you have any questions, please contact us at: row(a)cofomo.com<mailto:row@cofomo.com>. Please feel free to share this message with other mailing lists and contacts who may find it relevant. We thank you and look forward to your participation! ROW Program Committee https://regiops.net<https://secure-web.cisco.com/1FGeiw9amzg3JmN8pZKPdUcQ-WKH-_NNoNBqm2u4j-Upa7…> Email: row(a)cofomo.com<mailto:row@cofomo.com> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> Connect with us: LinkedIn<https://secure-web.cisco.com/14S97RpTn-aFiKOZGaJCp6H1VPKmnIXZFaJzHQWWc25bHk…> | Twitter<https://twitter.com/ROWevents> | Bluesky<https://secure-web.cisco.com/13lI8G6s7T5Ig3swq9YvPaU5MHFVlEJW2ZAJ8JyUd0o3EL…> Event sponsored by Verisign<https://www.verisign.com/>, ICANN<https://secure-web.cisco.com/1Zrr4E4W7w-BC3CPVQ_Xe6tqDpzrrvNxbDE0kyNU4A-Dif…> & CIRA<https://secure-web.cisco.com/1SAWYBdvuxhep6ETGV1AB-AThbFz2cNOhYA4d8Cayp3ce3…> and organized by Cofomo<https://secure-web.cisco.com/1ZlT-E9CSUuKlrowftCAPfq1D8cD-D-Z027uhc21Fm2OlO…> Cross-posting to multiple lists - sorry for any duplicates. To stop receiving ROW updates, please reply ‘unsubscribe’ to this email. -- You received this message because you are subscribed to the Google Groups "Regiops" group. To unsubscribe from this group and stop receiving emails from it, send an email to regiops+unsubscribe(a)googlegroups.com<mailto:regiops+unsubscribe@googlegroups.com>. To view this discussion visit https://groups.google.com/d/msgid/regiops/YT3P288MB033177E8069ECBC2AE8AD2FC…<https://secure-web.cisco.com/1G7uxzrBqIG7h9WuYu-WL-f_ieM-Ib0jkCkSt7ryJvkGgB…>.

1 0

Call for Presentations Hybrid TechDay ICANN 84 Dublin
by Eberhard W Lisse Aug. 26, 2025

Aug. 26, 2025

vTechDay at ICANN 84 (Dublin) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 84 meeting (Dublin) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2025-10-27 for blocks: Block 2 10:45 - 12:15 Block 3 13:15 - 14:30 Block 4 15:00 - 16:00 Block 5 16:30 - 17:30 All times are local (Dublin) time. We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. Open Source Tools that have been found helpful a) We would in particular like to hear about git based DNS zone management, especially simple setups usable as example for other (smaller) (cc|g)TLDs. b) We would also like to hear about further RDAP client implementations for the command line, devices and libraries. If there are enough proposals we might have round tables. 5. In addition, we welcome suggestions for additional topics The ccNSO's DNS Abuse Committee has expressed an interest in organizng a round table looking at detection/end-to-end case studies from a (cc)TLD perspective and we are proposing Block 2 (ie 75 minutes (including the opening remarks)). Interest in participating should be expressed by email to eitheror all of Nick.Wenban-Smith(a)nominet.uk bruce.tonkin(a)auda.org.au bart.boswinkel(a)icann.org keeping us in copy at ccNSO-techday(a)icann.org. If you are interested in presenting on any other topic, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

FW: ROW14 - Final Call for Proposals
by Hollenbeck, Scott July 31, 2025

July 31, 2025

Last call, folks! Scott From: Row <row(a)cofomo.com> Sent: Thursday, July 31, 2025 11:55 AM Subject: [EXTERNAL] ROW14 - Final Call for Proposals 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. ROW14 | September 30th, 2025 | 13:00 - 17:00 UTC | Online Event The next Registration Operations Workshop<https://secure-web.cisco.com/1svjEsNWalm_Isqp6bX5pu8SZKWJfOBjWDedJ90QlNv0hp…> (ROW) will once again be held virtually, offering a broader platform for in-depth discussions on the technical aspects of registration operations within the Domain Name System. Thanks to the generous support of our sponsors - Verisign<https://www.verisign.com/>, ICANN<https://secure-web.cisco.com/1xEihnJFeMi45RRUUK1946jvrT8w1GH1goQ4St6hQn2u3A…> and CIRA<https://secure-web.cisco.com/1O1-LzJ18pv0TPIeLfPE6OB2ZgNVuT5N3zPB_7gR26oxAm…> - we look forward to our fourteenth edition (ROW14), featuring another engaging lineup of talks, panel discussions, and conversations with experts involved in domain name registration systems. LAST CALL for Presentation & Panel Proposals > Deadline August 15th, 2025 If you're interested in presenting, please submit a brief abstract summarizing your presentation and/or panel proposals to row(a)cofomo.com<mailto:row@cofomo.com> by August 15th. We will consider presenter time zones when organizing the agenda. We invite submissions guided by this non-exhaustive list of broad topics and welcome any discussions or suggestions for additional topics on the ROW's mailing list<mailto:regiops@googlegroups.com>: ********************* Operational impacts of provisioning protocol migration ********************* Examples of how AI is being used in the registration ecosystem ********************* RDAP implementation experience ********************* Implementation of NIS2 Directive ********************* Best practices for DNSSEC Key management ********************* DNS abuse (Global Signal Exchange, etc.) ********************* Topics relevant to EPP, RPKI and other protocols relevant to Registration Systems (Domain Connect protocol, etc.) ********************* Digital Identity topics (eIDAS, etc.) Registration is Required to Enable Participation While there is no fee to attend the Registration Operations Workshop, we encourage anyone interested in participating to register so that we can provide session login credentials. ROW events are open to all industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, second level domain registries, academia, and many more. Register<https://secure-web.cisco.com/1Ckeh2bwjqKZwkGlw3iAG_St1BM5aOFGRAMMhb_uGojQXF…> now for ROW14! ROW14 Important Dates ********************* Deadline to submit proposals: August 15th ********************* Program Committee to notify selected authors by: August 21st ********************* Expected agenda release date: September 2nd ********************* Speaker materials required by: September 23rd ********************* ROW14 event: September 30th, 13:00-17:00 UTC We hope that you can join us and look forward to receiving your proposals! Please feel free to share this message with other mailing lists and contacts who may find it relevant. Thank you. ROW Program Committee https://regiops.net<https://secure-web.cisco.com/1svjEsNWalm_Isqp6bX5pu8SZKWJfOBjWDedJ90QlNv0hp…> Email: row(a)cofomo.com<mailto:row@cofomo.com> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> Connect with us: LinkedIn<https://secure-web.cisco.com/12rXUishv4xa4fXfOts0TTc2jB0OWfIgRsJKf9P8gPqgdz…> | Twitter<https://twitter.com/ROWevents> | Bluesky<https://secure-web.cisco.com/1fJNAtZalJapodPidE1L98qrA92P5IebalgLaa8tk5ozHo…> Event sponsored by Verisign<https://www.verisign.com/>, ICANN<https://secure-web.cisco.com/1xEihnJFeMi45RRUUK1946jvrT8w1GH1goQ4St6hQn2u3A…> & CIRA<https://secure-web.cisco.com/1O1-LzJ18pv0TPIeLfPE6OB2ZgNVuT5N3zPB_7gR26oxAm…> and organized by Cofomo<https://secure-web.cisco.com/1PKFOxxjEG7nrohVeuPOgC8MCWz_6hFKWm_Bohf7d4mpuc…> Cross-posting to multiple lists - sorry for any duplicates. To stop receiving ROW updates, please reply 'unsubscribe' to this email.

1 0

FW: Launch of the RST v2.0 Service
by Gustavo Lozano Ibarra July 30, 2025

July 30, 2025

Hello Colleagues, You may find the following email of interest to you. Regards, Gustavo From: ICANN Global Support <noreply-globalsupport(a)icann.org> Date: Tuesday, July 29, 2025 at 10:50 Subject: Launch of the RST v2.0 Service Dear Colleagues, Further to our previous communications, ICANN org is providing this update on the status of the Registry System Testing (RST) v2.0 service. Following a “beta” phase, the production RST v2.0 environment has now been launched. This environment differs from the Operational Testing and Evaluation (OT&E) environment in that it will be used to test the registry systems of applicants in the Registry Service Provider (RSP) Evaluation Program. As such, the RSP Portal will create and configure the test objects defining the TLD(s) and registry functions being tested (in OT&E, users are free to configure these as needed). ICANN org is currently testing the integration between the RSP portal and RST systems. This is expected to be completed by 11 August 2025. After this date, applicants will have the opportunity to begin production RST testing once applicants have cleared technical screening. Although the RST v2.0 service has undergone extensive testing (both by ICANN org and by OT&E users), if you discover an issue with either environment that is not listed in the section Known Issues<https://www.icann.org/en/contracted-parties/registry-operators/registry-sys…> of the RST v2.0 page<https://www.icann.org/en/contracted-parties/registry-operators/registry-sys…>, please report the issue to ICANN’s Global Support via the Naming Services portal or by emailing globalsupport(a)icann.org<mailto:globalsupport@icann.org>. More information about the RST v2.0 service, including the process for requesting access to OT&E, may be found on the RST v2.0 page on the ICANN website: https://www.icann.org/en/contracted-parties/registry-operators/registry-sys… To request access to the OT&E environment, users must first complete the steps listed<https://www.icann.org/resources/pages/registry-system-testing-v2-2024-10-23…> on the page above. Best regards, Technical Services Team Global Domains and Strategy Internet Corporation for Assigned Names and Numbers

1 0

(no hat) translations needed for rdapper RDAP client
by Gavin Brown July 28, 2025

July 28, 2025

Greetings, Separately from my day jobm I maintain an open source RDAP client called rdapper: https://github.com/gbxyz/rdapper I have recently added localization support, and am in need of translations of the .po files that it uses. If that's something you can help with, instructions can be found here: https://metacpan.org/pod/App::rdapper::l10n Thanks, and apologies for the cross post! Gavin.

1 0

.top zonefile empty as of 2025-06-04
by Alex Edelchteine July 9, 2025

July 9, 2025

Hello, The latest .top zonefile is empty, are there any issues with it? Thanks Alex

7 15

FW: ROW14 - Call for proposals & registrations
by Hollenbeck, Scott June 24, 2025

June 24, 2025

FYI, folks. Please note that the topic list described below isn’t exclusive. Any topic focused on registry operations is in scope. Scott From: 'Row' via Regiops <regiops(a)googlegroups.com> Sent: Tuesday, June 24, 2025 7:20 AM Subject: [EXTERNAL] [regiops] ROW14 - Call for proposals & registrations 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. ROW14 Call for Proposals & Registrations NOW OPEN | September 30th, 2025 | 13:00 - 17:00 UTC | Online Event Registration Process is NOW OPEN! Join us to present and discuss technical topics related to real world experiences of implementing registration operations, including RDAP, EPP, WHOIS, RPKI, Registry Lock, and much more. The Registration Operations Workshop (ROW) events are open to all industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, second level domain registries, academia, and many more. Register<https://secure-web.cisco.com/1058M07m_hSpE1qb7NtiFkNKXYyEraLdTLShawfzphkkc8…> now to secure your spot and get the latest updates! Attendance is free, but registration is required to receive your conference login credentials. Call for Presentation & Panel Proposals is OPEN! Please submit a brief abstract outlining your presentation or panel proposal to row(a)cofomo.com<mailto:row@cofomo.com> by August 15th. We will consider presenter time zones when organizing the agenda. We invite submissions guided by this non-exhaustive list of broad topics and welcome any discussions or suggestions for additional topics on ROW’s mailing list<mailto:regiops@googlegroups.com>. • Operational impacts of provisioning protocol migration • Examples of how AI is being used in the registration ecosystem • RDAP implementation experience • Implementation of NIS2 Directive • Best practices for DNSSEC Key management • DNS abuse (Global Signal Exchange, etc.) • Topics relevant to EPP, RPKI and other protocols relevant to Registration Systems (Domain Connect protocol, etc.) • Digital Identity topics (eIDAS, etc.) ROW14 Important Dates! • Deadline to submit proposals: August 15th • Program Committee to notify selected authors by August 21st • Expected agenda release date: September 2nd • Speaker materials required by September 23rd • ROW14 event: September 30th, 13:00-17:00 UTC We hope that you can join us and look forward to receiving your proposals! Please feel free to share this message with other mailing lists and contacts who may find it relevant. Thank you. ROW Program Committee https://regiops.net<https://secure-web.cisco.com/1mH9LHa7jYQ7c9xUapo9Y6XH1R6t28Vp_e77wdH_2xCS-V…> Email: row(a)cofomo.com<mailto:row@cofomo.com> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> Connect with us: LinkedIn<https://secure-web.cisco.com/13mGVRahqlxp3PJ7G9fXtY0NUaneqYHNLPuTSFw4ZYqz2i…> | Twitter<https://twitter.com/ROWevents> | Bluesky<https://secure-web.cisco.com/19cKpzi8Z5V1l5sgvz1x21zuGKk9DwGgutzzsADRHEn-Q6…> Event sponsored by Verisign<https://www.verisign.com/>, ICANN<https://secure-web.cisco.com/1sZ4rKmH81yL3_SQJUL2P33W2PY07YTNp10jrROICNilXK…> & CIRA<https://secure-web.cisco.com/1b5o5wOOl0Fdd7BPho8MvOiFzl-_O5QCIeXlaFJNgVNalJ…> and organized by Cofomo<https://secure-web.cisco.com/1PcCeg3P5CVsexnpEbxSl0jFIWDiUxP0WQHU6saVNo6glW…> Cross-posting to multiple lists - sorry for any duplicates. To stop receiving ROW updates, please reply ‘unsubscribe’ to this email. -- You received this message because you are subscribed to the Google Groups "Regiops" group. To unsubscribe from this group and stop receiving emails from it, send an email to regiops+unsubscribe(a)googlegroups.com<mailto:regiops+unsubscribe@googlegroups.com>. To view this discussion visit https://groups.google.com/d/msgid/regiops/YT4P288MB0333BBF70E25400954909ED1…<https://secure-web.cisco.com/1Atu76wNi379LwJzP2FV1E5VJ1iFGZHAnY659Cf_D4FKdQ…>.

1 0

Root Zone DNSSEC Operational Update
by Wessels, Duane June 10, 2025

June 10, 2025

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Verisign, in its role as the root zone ZSK operator, is transitioning to a new Hardware Security Module (HSM) product for the root zone's Zone Signing Key (ZSK). The current HSM vendor, Ultra Intelligence & Communications, has announced their KeyperPLUS will no longer be supported by them. Verisign will use an HSM product from Thales for the root zone ZSK going forward. On July 1, 2025 we will begin using the Thales HSM to sign the root zone on a daily basis. Although we anticipate this will be a seamless change for end users and anticipate no problems, prudence dictates that we need a backout plan, should it become necessary. As part of our backout plan, we will be post-publishing the previous quarter's ZSK for a longer than normal period of time. Normally, following a quarterly ZSK rollover, the previous key is post-published for a period of 10 days. As part of our HSM transition, we will instead post-publish the previous ZSK for a period of 80 days. This provides ample time to remediate any issues that may arise as part of this transition, and should it become necessary, to revert to using the old HSM to sign the root zone. -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEvEG6oyZuoN5HQhnubJmkaajAmI0FAmhGex8ACgkQbJmkaajA mI1MEQgAo5/CB0GHYJq+4EqPCecevajsAhjcr4NXxViKyU5K3E//DwR82LIC9p6T HWLY1C0tiFk2Sg/3FbxF2arnUVC9yPJHOI5y2O+AE/BJibSVCyEEse+CbQkVljEd peaHNkkqp96AGgJiZv1On+B63Nog4CBrGMRxD14J0IAZShGbFqDZLRo6VhTHCCf+ isea/+1LbAbe/r2lTbm72q3a5lt/br6yRl37MZAbsJh8PyOAQE54jcnMlypL3qlx VribLjYduQAyKfUgMfVOXOionoY8i+4u1Rce9GXC130jklW7KXsp4un0SCGT5ByV gQWK5Hz73A4039CiUtjm3WqoIILIcg== =kLWP -----END PGP SIGNATURE-----

1 0

Call for Presentations Hybrid TechDay ICANN 83 Prague
by Dr Eberhard W Lisse June 5, 2025

June 5, 2025

As per our previous call we still have room on the agenda. Please also note that NIC.CZ is contemplating favorably our suggestion to have something like a Knot DNS Masterclass in addition to Techday. This would probably happen on Wednesday (2025-06-11) afternoon and as seats will be limited to around 30 we would like to have interested parties email to ccNSO-techday(a)icann.org (which is read by the organizers) as soon as possible. vTechDay at ICANN 83 (Prague) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 83 meeting (Prague) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2025-06-09 for blocks: Block 1 09:00 - 10:15 am local time / 07:00 - 08:15 UTC Block 2 10:45 - 12:15 pm local time / 08:45 - 10:15 UTC We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. Open Source Tools that have been found helpful a) We would in particular like to hear about git based DNS zone management, especially simple setups usable as example for other (smaller) (cc|g)TLDs. b) We would also like to hear about further RDAP client implementations for the command line, devices and libraries. If there are enough proposals we might have round tables. 5. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

2 1

Fwd: Update on RST v2.0 OT&E environment
by Gavin Brown April 22, 2025

April 22, 2025

Greetings, ICANN recently sent the communication below to existing Registry Operators, Registry Service Providers, and applicants to the RSP Evaluation Program, but I am sharing here as I think it will be of interest to people on this mailing list. Regards, Begin forwarded message: From: ICANN Global Support <noreply-globalsupport(a)icann.org> Subject: Update on RST v2.0 OT&E environment Date: 17 April 2025 at 20:32:10 BST To: tech-services <tech-services(a)icann.org> [PNG image.png] Dear Colleagues, Further to our previous communications, ICANN is providing this update on the status of the Registry System Testing (RST) v2.0 service. As previously announced, initial development was completed for 100% of the test cases in February 2025, with the exception of support for the gTLD Registration Data Access Protocol (RDAP) Profile 2024 that is planned to be added in CYQ3 2025. The service is currently in “beta”. ICANN org is continuing to carry out internal testing to ensure the service meets the community’s expectations of quality and reliability, but current and prospective Registry Operators and Registry Service Providers (RSPs) are encouraged to onboard onto the Operational Test & Evaluation (OT&E) environment as soon as possible, to integrate with the RST-API and test their registry systems against the new test plans. This will ensure that production RSP evaluation tests can be completed smoothly and without delay. The RST system is expected to remain in beta until the end of July 2025, rather than the originally planned March 2025 timeline, as ICANN org continues to address bugs and enhances system stability for production readiness. Currently, ICANN org does not consider that this delay will affect the New gTLD Program: Next Round critical path nor the start of technical testing in the RSP Evaluation Program. We understand that RSP applicants could be affected if their RSP's platforms do not conform with technical specifications and find out about this in the OT&E environment close to when technical testing starts. To mitigate the potential scenario for RSP applicants described above, ICANN org has updated the RST v2.0 web page with a list of known issues, which RSP applicants can consult when troubleshooting the results of tests carried out in the OT&E environment to understand if a test failed or is a known issue. ICANN org will regularly update this page as issues are fixed or new issues are identified. If you discover an issue with the OT&E environment that is not listed in the section Known Issues<https://www.icann.org/resources/registry-system-testing-v2.0/#Known-issues> of the RST v2.0 page<https://www.icann.org/resources/registry-system-testing-v2.0>, please submit it to ICANN’s Global Support via the Naming Services portal or by emailing globalsupport(a)icann.org<mailto:globalsupport@icann.org>. More information about the RST v2.0 service, including the process for requesting access, may be found on the new RST v2.0 page on the ICANN website: https://www.icann.org/resources/registry-system-testing-v2.0 To request access to the OT&E environment, users must first complete the steps listed on the page above. Best regards, Technical Services Team Global Domains and Strategy Internet Corporation for Assigned Names and Numbers -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org

1 0

FW: ROW14 - Call for proposals
by Hollenbeck, Scott April 3, 2025

April 3, 2025

FYI, folks! Scott From: 'Row' via Regiops <regiops(a)googlegroups.com> Sent: Thursday, April 3, 2025 7:20 AM To: 'Row' via Regiops <regiops(a)googlegroups.com> Subject: [EXTERNAL] [regiops] ROW14 - Call for proposals 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. <https://protect.checkpoint.com/v2/r03/___https:/regiops.net/___.YzFjOmNvZm9…> ROW14 Call for Proposals is Now Open! | September 30th, 2025 | Zoom Video Conference Since 2014, the Registration Operations Workshop (ROW)<https://protect.checkpoint.com/v2/r03/___https:/regiops.net/___.YzFjOmNvZm9…>, supported by our sponsors Verisign<https://protect.checkpoint.com/v2/r03/___https:/verisign.com/___.YzFjOmNvZm…> and ICANN<https://protect.checkpoint.com/v2/r03/___https:/icann.org/___.YzFjOmNvZm9tb…>, and more recently CIRA<https://protect.checkpoint.com/v2/r03/___https:/www.cira.ca/en/___.YzFjOmNv…>, brings together industry professionals—such as address/gTLD/ccTLD registries, domain name registrars, resellers, and second level domain registries—to share and discuss technical topics related to real-world experiences of implementing registration operations (RDAP, EPP, WHOIS, RPKI, Registry Lock, and many more). See all ROW events at: https://regiops.net/events<https://protect.checkpoint.com/v2/r03/___https:/regiops.net/events___.YzFjO…> The Program Committee is now accepting proposals for ROW14 and encourages you to submit a brief abstract outlining your presentation or panel proposal to row(a)cofomo.com<mailto:row@cofomo.com> by August 15th, 2025. We invite submissions guided by this non-exhaustive list of broad topics and welcome any discussions or suggestions for additional topics on ROW’s mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ••••••••••••••••••••• Operational impacts of provisioning protocol migration * Examples of how AI is being used in the registration ecosystem * RDAP implementation experience ••••••••••••••••••••• Implementation of NIS2 Directive * Best practices for DNSSEC Key management * DNS abuse (Global Signal Exchange, etc.) * Topics relevant to EPP, RPKI and other protocols relevant to Registration Systems (Domain Connect protocol, etc.) * Digital Identity topics (eIDAS, etc.) The Program Committee will inform selected authors by August 21st, 2025. Checkout other ROW14 important dates at: https://regiops.net<https://protect.checkpoint.com/v2/r03/___https:/regiops.net/___.YzFjOmNvZm9…>. We look forward to receiving your proposals. Please feel free to share this call for proposals with other mailing lists and contacts who may find it relevant. Thank you. ROW Program Committee regiops.net<https://protect.checkpoint.com/v2/r03/___http:/regiops.net/___.YzFjOmNvZm9t…> | row(a)cofomo.com<mailto:row@cofomo.com> | regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> <https://protect.checkpoint.com/v2/r03/___https:/twitter.com/ROWevents___.Yz…> <https://protect.checkpoint.com/v2/r03/___https:/bsky.app/profile/regiops.bs…> <https://protect.checkpoint.com/v2/r03/___https:/www.linkedin.com/company/re…> This event is sponsored by Verisign<https://protect.checkpoint.com/v2/r03/___https:/www.verisign.com/___.YzFjOm…>, ICANN<https://protect.checkpoint.com/v2/r03/___https:/www.icann.org/___.YzFjOmNvZ…> & CIRA<https://protect.checkpoint.com/v2/r03/___https:/www.cira.ca/en/___.YzFjOmNv…> and organized by Cofomo<https://protect.checkpoint.com/v2/r03/___https:/www.cofomo.com/___.YzFjOmNv…>. Cross-posting to multiple lists - sorry for any duplicates. To stop receiving ROW updates, please reply ‘unsubscribe’ to this email. -- You received this message because you are subscribed to the Google Groups "Regiops" group. To unsubscribe from this group and stop receiving emails from it, send an email to regiops+unsubscribe(a)googlegroups.com<mailto:regiops+unsubscribe@googlegroups.com>. To view this discussion visit https://groups.google.com/d/msgid/regiops/YT4P288MB0333327B5B68C660E4763002…<https://secure-web.cisco.com/1xuR1nF7Shhn2Mn0TKBioxMoF0p1zcYQ6XSZGqwa2UMML4…>.

1 0

Call for Presentations Hybrid TechDay ICANN 83 Prague
by Eberhard W Lisse March 31, 2025

March 31, 2025

vTechDay at ICANN 83 (Prague) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 83 meeting (Prague) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2025-06-09 for blocks: Block 1 09:00 - 10:15 am local time / 07:00 - 08:15 UTC Block 2 10:45 - 12:15 pm local time / 08:45 - 10:15 UTC We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. Open Source Tools that have been found helpful a) We would in particular like to hear about git based DNS zone management, especially simple setups usable as example for other (smaller) (cc|g)TLDs. b) We would also like to hear about further RDAP client implementations for the command line, devices and libraries. If there are enough proposals we might have round tables. 5. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

Fwd: RST v2.0 beta reaches 100% coverage of test cases
by Gavin Brown March 3, 2025

March 3, 2025

Greetings, ICANN recently sent the communication below to existing Registry Operators and Registry Service Providers, but I am sharing here as I think it will be of interest to people on this mailing list. Regards, > Begin forwarded message: > > From: ICANN Global Support <noreply-globalsupport(a)icann.org> > Subject: RST v2.0 beta reaches 100% coverage of test cases > Date: 28 February 2025 at 17:48:42 GMT > To: tech-services <tech-services(a)icann.org> > > Dear Colleagues, > > ICANN is pleased to announce that initial development was completed for 100% of the test cases in the Registry System Testing (RST) v2.0. These test cases are now available in the Operational Testing & Evaluation (OT&E) environment. > > If you are interested in participating as a Registry Service Provider in the New gTLD Program: Next Round[1], you are encouraged to onboard into the OT&E environment for the new service to: > > * Integrate into the new Registry System Testing API (RST-API) and, > * Ensure the readiness of registry systems for production RST during the RSP Evaluation Program and Pre-Delegation Testing of TLDs during the New gTLD Program: Next Round. > > In the future, RST v2.0 will replace version 1.0 of the RST System which traces back its origin to the original Pre-Delegation Testing system established for the 2012 round of the New gTLD Program. Processes such as the Material Subcontracting Arrangement (MSA) Change may require current gTLDs to go through RST. Current Registry Operators (ROs) and Registry Service Providers (RSPs) are invited to onboard into the OT&E in preparation for when RST v2.0 replaces RST v1.0. More information about the timeline of the RST 2.0 transition will be shared in the coming months, and it’s envisioned that ICANN org will provide a six-month advance notice before transitioning to RST 2.0 for current gTLDs. > > During ICANN 82, ICANN org will host an interactive session on the Registry Service Provider (RSP) Evaluation Program[2] and Registry System Testing (RST) 2.0[3]. If interested, please join us at: https://icann82.sched.com/event/1vpd5/learn-about-evaluation-and-testing-fo… > > More information about the RST v2.0 service, including the process for requesting access to the OT&E, may be found on the new RST v2.0 page on the ICANN website: > > https://www.icann.org/resources/registry-system-testing-v2.0/ > > If you have additional questions, please contact ICANN’s Global Support via the Naming Services portal or by emailing globalsupport(a)icann.org. > > Best regards, > > Technical Services Team > Global Domains and Strategy > Internet Corporation for Assigned Names and Numbers [1] https://newgtldprogram.icann.org/en [2] https://newgtldprogram.icann.org/en/application-rounds/round2/rsp [3] https://www.icann.org/resources/registry-system-testing-v2.0 -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org

1 0

3rd Call for Presentations Hybrid TechDay ICANN 82 Seattle
by Eberhard W Lisse Feb. 18, 2025

Feb. 18, 2025

We are having a number of open slots. el vTechDay at ICANN 82 (Seattle) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 82 meeting (Seattle) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2024-11-11 for four blocks: Block 2 10:45-12:00 Block 3 13:15-14:30 Block 4 15:00-16:00 Block 5 16:30-17:30 We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. Open Source Tools that have been found helpful 5. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

2 2

2nd Call for Presentations Hybrid TechDay ICANN 82 Seattle
by Dr Eberhard W Lisse Feb. 6, 2025

Feb. 6, 2025

vTechDay at ICANN 82 (Seattle) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 82 meeting (Seattle) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2024-11-11 for four blocks: Block 2 10:45-12:00 Block 3 13:15-14:30 Block 4 15:00-16:00 Block 5 16:30-17:30 We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. Open Source Tools that have been found helpful 5. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

ICANN Update: Launching RDAP; Sunsetting WHOIS
by Andy Newton Jan. 27, 2025

Jan. 27, 2025

HI all, Regarding the WHOIS sunset, the ICANN announcement “ICANN Update: Launching RDAP; Sunsetting WHOIS” can be here: https://www.icann.org/en/announcements/details/icann-update-launching-rdap-… The contents are below: As of 28 January 2025, the Registration Data Access Protocol (RDAP) will be the definitive source for delivering generic top-level domain name (gTLD) registration information in place of sunsetted WHOIS services. RDAP offers several advantages over WHOIS including support for internationalization, secure access to data, authoritative service discovery, and the ability to provide differentiated access to registration data. RDAP was developed by the Internet Engineering Task Force. RDAP has been offered by ICANN-accredited registrars and gTLDs since 2019. Users are encouraged to utilize ICANN's RDAP-based Lookup service at https://lookup.icann.org/en or ICANN's open-source command-line client hosted on GitHub. A list of other client implementations may be found on this page. To request access to nonpublic gTLD registration data, use the Registration Data Request Service (RDRS) for participating registrars or contact the sponsoring registrar directly to determine their disclosure process. Please make sure you have first checked that the data is unavailable through the ICANN Lookup tool. The RDRS is intended for use by those with a legitimate interest in nonpublic data like law enforcement, intellectual property professionals, consumer protection advocates, cybersecurity professionals, and government officials. -- Andy Newton Principal Engineer GDS Technical Services, ICANN

1 0

Call for Presentations Hybrid TechDay ICANN 82 Seattle
by Dr Eberhard W Lisse Jan. 20, 2025

Jan. 20, 2025

vTechDay at ICANN 82 (Seattle) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 82 meeting (Seattle) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2024-11-11 for four blocks: Block 2 10:45-12:00 Block 3 13:15-14:30 Block 4 15:00-16:00 Block 5 16:30-17:30 We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. Open Source Tools that have been found helpful 5. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 1

Launch of the Registry System Testing (RST) v2.0 OT&E environment
by Gavin Brown Nov. 22, 2024

Nov. 22, 2024

Dear colleagues, We are pleased to invite current and prospective Registry Operators (ROs) and Registry Service Providers (RSPs) to onboard into the Operational Testing & Evaluation (OT&E) environment for the new Registry System Testing (RST) v2.0 service. This environment is being provided to allow users to (1) integrate into the new Registry System Testing API (RST-API), (2) ensure the readiness of registry systems for production RST during the RSP Evaluation Programme and Pre-Delegation Testing of TLDs during the New gTLD Program: Next Round, and (3) verify that the RST v2.0 implementation correctly implements the RST test specifications. More information about the RST v2.0 service, including the process for requesting access, may be found on the new RST v2.0 page on the ICANN website: https://www.icann.org/resources/registry-system-testing-v2.0 To request access to the OT&E environment, users must first complete the steps listed on the page above to generate and publish one or more TLSA records in the DNS for authentication. Then, users must submit a request either by submitting a general inquiry in the Naming Services portal (for existing registry operators) or by emailing globalsupport(a)icann.org (for prospective Registry Operators or Registry Services Providers). Please note that development work on the RST v2.0 service is still ongoing, and several test cases have not yet been completed. The web page linked to above includes details of the level of coverage for each test suite and will be regularly updated. Participating users will be notified when the OT&E environment is updated and new test cases become available. Users are also encouraged to monitor the “Change Log” sections of the RST v2.0 test specifications ([1]) and API spec ([2]), since these may change during the course of development. Regards, Gavin. [1] https://icann.github.io/rst-test-specs/rst-test-specs.html [2] https://icann.github.io/rst-api-spec/rst-api-spec.html -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org

1 0

Call for Presentations Hybrid TechDay ICANN 81 Istanbul
by Dr Eberhard W Lisse Nov. 2, 2024

Nov. 2, 2024

Call for Presentations vTechDay at ICANN 81 (Istanbul) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 81 meeting (Istanbul) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2024-11-11 for four blocks: Block 2 10:45 - 12:00 Block 3 13:15 - 14:30 Block 4 15:00 - 16:00 Block 5 16:30 - 17:00 We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

3 3

2nd Call for Presentations Hybrid TechDay ICANN 81 Istanbul
by Eberhard W Lisse Oct. 9, 2024

Oct. 9, 2024

2nd Call for Presentations vTechDay at ICANN 81 (Istanbul) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 81 meeting (Istanbul) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2024-11-11 for four blocks: Block 2 10:45 - 12:00 Block 3 13:15 - 14:30 Block 4 15:00 - 16:00 Block 5 16:30 - 17:00 We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

Scheduled Maintenance Notification for the Centralized Zone Data Service (CZDS) system
by Mustafa Alrifaee Oct. 8, 2024

Oct. 8, 2024

Hello Colleagues, The Centralized Zone Data Service (CZDS) system will be undergoing routine maintenance starts on Tuesday, 15 October 2024, at 22:30 UTC, and ends on 16 October 2024, at 00:30 UTC. During this time, the CZDS portal and zone download service may be temporarily unavailable for a brief time. Please feel free to contact us at globalSupport(a)icann.org<mailto:globalSupport@icann.org> should you have any questions. Best Regards, Mustafa Alrifaee ICANN

1 0

REMINDER: Call for Participation -- ICANN81 DNSSEC and Security Workshop
by Jacques Latour Sept. 21, 2024

Sept. 21, 2024

Hi all! We still have a few openings in our schedule. Thanks, Jacques Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN Annual General Meeting In cooperation with the ICANN Security and Stability Advisory Committee (SSAC), we are planning a DNSSEC and Security Workshop for the ICANN81 Annual General Meeting being held as a hybrid meeting from 09-14 November 2024 in Istanbul, Türkiyea in the Turkey Time TRT- (UTC +3). This workshop date will be determined once ICANN creates a block schedule for us to follow; then we will be able to request a day and time. The DNSSEC and Security Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN80 The Policy Forum on Monday, 10 June 2024. The presentations and transcripts are available at: https://icann80.sched.com/<https://urldefense.com/v3/__https:/icann80.sched.com/__;!!PtGJab4!7Vwf_nce_…>. The DNSSEC Workshop Program Committee is developing a program for the upcoming meeting. Proposals will be considered for the following topic areas and included if space permits. In addition, we welcome suggestions for additional topics either for inclusion in the ICANN78 workshop, or for consideration for future workshops. 1. Global DNSSEC Activities Panel For this panel, we are seeking participation from those who have been involved in DNSSEC deployment as well as from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment, including Root Key Signing Key (KSK) Rollover activities and plans. 2. DNSSEC Best Practice Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? * Do you still submit/accept DS records with Digest Type 1? * What is the best practice around key roll-overs? * What about Algorithm roll-overs? * Do you use and support DNSKEY Algorithms 13-16? * How often do you review your disaster recovery procedures? * Is there operational familiarity within your customer support teams? * What operational statistics have been gathered about DNSSEC? * Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? Activities and issues related to DNSSEC in the DNS Root Zone are also desired. 3. DNSSEC Deployment Challenges The program committee is seeking input from those that are interested in implementation of DNSSEC but have general or particular concerns with DNSSEC. In particular, we are seeking input from individuals that would be willing to participate in a panel that would discuss questions of the following nature: * Are there any policies directly or indirectly impeding your DNSSEC deployment? (RRR model, CDS/CDNSKEY automation) * What are your most significant concerns with DNSSEC, e.g., complexity, training, implementation, operation or something else? * What do you expect DNSSEC to do for you and what doesn't it do? * What do you see as the most important trade-offs with respect to doing or not doing DNSSEC? 4. Security Panel The program committee is looking for presentations on DNS, DNSSEC, routing and other topics that could impact the security and/or stability of the Internet. We are looking for presentations that cover implementation issues, challenges, opportunities and best practices for: * Emerging threats that could impact the security and/or stability of the Internet * DoH and DoT * RPKI (Resource Public Key Infrastructure) * BGP routing & secure implementations * MANRS ( Mutually Agreed Norms for Routing Security) * Browser security - DNS, DNSSEC, DoH * EMAIL & DNS related security - DMARC, DKIM, TLSA, etc... If you are interested in participating, please send a brief (1-3 sentence) description of your proposed presentation to dnssec-security-workshop(a)icann.org<mailto:dnssec-security-workshop@icann.org> by Friday, 13 September 2024. Thank you, Kim and Kathy On behalf of the DNSSEC Workshop Program Committee: Gautam Akiwate, Stanford University Steve Crocker, Edgemoor Research Institute Mark Elkins, DNS/ZARC Jacques Latour, .CA Ram Mohan, Identity Digital Russ Mundy, Tislabs Yoshiro Yoneya Dan York, Internet Society

3 2

.med TLD 99.98% lame delegations?
by Viktor Dukhovni Aug. 25, 2024

Aug. 25, 2024

The current state of the .med TLD is rather odd, with ~99.98% delegations lame! Just 9 of the almost 42000 delegations are working. Is the TLD going away? If not, what explains the almost total breakage? -- Viktor.

3 6

CZDS .COM download problems?
by Viktor Dukhovni Aug. 20, 2024

Aug. 20, 2024

I'm having problems downloading the ".COM" zone from CZDS today, is this expected, reproducible? The download seems to disconnect prematurely, with the HTTP transfer delivering less than the promised Content-Length, The connection drops after ~120 of ~4000 MB. error: HttpExceptionRequest Request { host = "czds-download-api.icann.org" port = 443 requestHeaders = [("Connection","close"),("User-Agent","czds-sync/0.1.0.0"),("Accept","application/x-gzip"),("Authorization","<REDACTED>")] path = "/czds/downloads/com.zone" queryString = "" method = "GET" redirectCount = 10 requestVersion = HTTP/1.1 } (ResponseBodyTooShort 4201149204 124156800) -- Viktor.

3 8

pyCZDS
by Max M. Diez July 1, 2024

July 1, 2024

Dear Community, I am excited to announce the release of pyCZDS, a new Python library designed to simplify interactions with ICANN's Centralized Zone Data Service (CZDS) API. This tool provides an easy and efficient way to download zone files from participating Top-Level Domains (TLDs), streamlining the process for developers and researchers working with DNS data. It is released under the GPL-3.0 license. Key features of pyCZDS include: - Easy Authentication: Simplifies the process of authenticating with the CZDS API. - Automated Downloads: Provides functions to download zone files with minimal effort. - Error Handling: Includes robust error handling to manage common issues with API requests. - Documentation and Examples: Comes with comprehensive documentation and example scripts to help you get started quickly. You can find the library and its source code on GitHub: https://github.com/mdiez/pyCZDS. The repository includes detailed instructions on how to install and use the library, as well as examples to demonstrate its functionality. I encourage you to check out pyCZDS and provide feedback or contributions to help improve the tool. Your input is invaluable to ensure that this library meets the needs of the community and remains a reliable resource for accessing CZDS data. Thank you for your attention, and I look forward to your feedback. Best regards, Max Diez Max M. Diez | 5 Eleftheriou Chandrinou, #B209 | 8045 Paphos | Cyprus | +357 999 55 321 | +41 78 321 00 00

1 0

2nd Call for Presentation TechDay ICANN80 Kigali
by Eberhard W Lisse June 5, 2024

June 5, 2024

2nd Call for Presentations vTechDay at ICANN 80 (Kigali) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 80 meeting (Kigali) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2024-06-10 for two blocks We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the African Region 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Eberhard W. Lisse \ /Obstetrician & Gynaecologist (retired) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht\ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply _______________________________________________ CCNSO-TechDay mailing list CCNSO-TechDay(a)icann.org https://mm.icann.org/mailman/listinfo/ccnso-techday _______________________________________________ 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.

1 1

FW: ROW13 agenda & registration
by Hollenbeck, Scott May 28, 2024

May 28, 2024

Last poke, I promise! Scott From: 'Row' via Regiops <regiops(a)googlegroups.com> Sent: Tuesday, May 28, 2024 1:24 PM Subject: [EXTERNAL] [regiops] ROW13 agenda & registration 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. The 13th Registration Operations Workshop<https://secure-web.cisco.com/1C3nOSx_8nmwb6odzdTosMKa-1MVgP03oNuWziQvDV8TZK…> (ROW13) will be conducted virtually via Zoom on June 4th, 2024, 13:00 - 17:00 UTC. (check local time zone here<https://secure-web.cisco.com/1joVXge9xSaVfaAxVt-dxveL8636rZKK-TSSUXnB-jaJYo…>). >>> ROW13 Agenda! The Program Committee<https://secure-web.cisco.com/1SexAwI07t-J3BXSJymVIOUZbBMtmp0mMZdEUHeRg8Mb5E…> is delighted to announce the final agenda<https://secure-web.cisco.com/1T8qr8eRcOvZ05IW9tFMWcxS8ziar3cM_AuheQoLvi65bw…> for ROW13, featuring insights into upcoming discussions and presentations. Presentation materials will be made available on our website 24 hours before the session. Session recording will be posted within 24-48 hours after the session. ••••••••••••••••••••• Sofia Silva Berenguer [NRO/APNIC] & Brad Gorman [ARIN] – Collaborating to Advance RPKI: New Initiatives and Global Progress * Panel: Implementations of NIS 2 Directive o Polina Malaja [CENTR] - chair - NIS 2 Directive Overview: Impact on TLD operators * Pawel Kowalik [DENIC eG] - Exploring Synergies in NIS 2 Implementation: A Path to Convergence * Timo Võhmar [Estonian Internet Foundation] - Know your registrant (KYR) - making internet a safer place * Alexander Mayrhofer [nic. at GmbH] - EPP for NIS2 – The .at Approach * Simon Fernandez [Grenoble INP, Univ. Grenoble Alps] - WHOIS Right? An Analysis of WHOIS and RDAP Consistency * Gavin Brown [ICANN] - Stealth RDAP * Isaac Henderson [Fraunhofer IAO] - DNS as a bridge to establish interoperable trust across different trust anchors * Werner Staub [CORE Association] - Standardized DNSSEC-Signed Attestations for Sport (dnsattest. sport) * Gautam Akiwate [Stanford University] - Best Practices for Deletion in EPP >>> Registration is required to enable participation! Attendance is free, but registration<https://secure-web.cisco.com/1OHip54W0esUFV8NTVZ04jwPcOnIMKHIiZUtttwR9mkGEF…> is mandatory to receive conference login credentials. ROW events are open to all industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, and second level domain registries. >>> Session logistics & Zoom Here are some special tips if this is your first time using Zoom or you wish to get more familiar with its web conferencing capabilities: ••••••••••••••••••••• Download the Zoom application to your computer or mobile phone. You can do it at https://zoom.us/download<https://secure-web.cisco.com/1N5DmzDVNQNLBif9w6J8013i_Ey2-dGo5BTjKYPRPzyerw…>. You will also be prompted to download and install Zoom when you click the link to join. You can also run Zoom from your web browser by navigating to join.zoom.us<http://secure-web.cisco.com/1OIUEj9r0cpEIw7_MPL_aVr7VWtIVx30vM9_JsQp4oW1WsN…> and entering the meeting number and passcode. * Want to try it out before June 20th? Join a test meeting at https://zoom.us/test<https://secure-web.cisco.com/1wUM0iHCnWNWtQnZARPAI4HhFRDENU81ZT76AWkeumySVH…> anytime to familiarize yourself with Zoom. You can also access Zoom tutorials here: https://support.zoom.us/hc/en-us/articles/201362193-How-Do-I-Join-A-Meeting<https://secure-web.cisco.com/1psM1RNj5At6s392qwbNvzNBUEEXSyyJMMjPNOuGLHyNvH…> * As an attendee, you will be muted. For questions and comments, please use the Q&A feature. The session moderator will address them to the speakers on the mike as time permits or ask attendees to read the question on their microphone. Questions that cannot be answered due to time constraints, will be answered directly in the Q&A window or by email. * We will be recording this webinar, including the chat, and making it available on our website 24-48h after the session. We would like to thank our ROW Series Sponsors ICANN<https://secure-web.cisco.com/1JtQr0UwufZUNgQ_QakktAuwYxw29UdkazbqYVGOMHdfOc…> and Verisign<https://www.verisign.com/> for their continued support. If you have any questions, please contact us at: row(a)cofomo.com<mailto:row@cofomo.com> We look forward to seeing you online! Please feel to share this note with other relevant lists and contacts where it might be of interest. Thank you. <https://secure-web.cisco.com/1C3nOSx_8nmwb6odzdTosMKa-1MVgP03oNuWziQvDV8TZK…> ROW Program Committee regiops.net<https://secure-web.cisco.com/1C3nOSx_8nmwb6odzdTosMKa-1MVgP03oNuWziQvDV8TZK…> | row(a)cofomo.com<mailto:row@cofomo.com> | regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> <https://twitter.com/ROWevents> <https://secure-web.cisco.com/13h972JGOUuCk9Ncv9w4tHaKim7CSKPn_7G3WcyTric-Su…> Sponsored by: Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1JtQr0UwufZUNgQ_QakktAuwYxw29UdkazbqYVGOMHdfOc…> Organized by: Cofomo<https://secure-web.cisco.com/1HZ771JJwIxdZMG-TTdopCYdn9vy_Y_FsAnZhk5lxLckYZ…> Cross-posting to multiple lists - sorry for any duplicates. To stop receiving ROW updates, please reply ‘unsubscribe’ to this email. -- You received this message because you are subscribed to the Google Groups "Regiops" group. To unsubscribe from this group and stop receiving emails from it, send an email to regiops+unsubscribe(a)googlegroups.com<mailto:regiops+unsubscribe@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/regiops/BN9PR14MB5050DAEF3985D4B072B486D8…<https://secure-web.cisco.com/11O6swsMD7xwjSL2dz1gA58BFKeGGcqmhYQUPSlLEXwlsq…>.

1 0

Re: [gtld-tech] 2nd Call for Presentation TechDay ICANN80 Kigali
by Theo Kramer May 27, 2024

May 27, 2024

Hi Eberhard We would be happy to oblige for option 3 below with topic ISO27001:2022 for any of the days except Monday 10 June. > On 27 May 2024, at 08:57, Neil Dundas <neil(a)dns.business> wrote: > > Can we volunteer any pertinent subjects here? Perhaps more about our recent transition exercise? ISO, Approach to Dev and Product… anything to showcase our abilities and skills? > > Neil > > >> Begin forwarded message: >> >> From: Eberhard W Lisse via gtld-tech <gtld-tech(a)icann.org> >> Subject: [gtld-tech] 2nd Call for Presentation TechDay ICANN80 Kigali >> Date: 27 May 2024 at 00:08:46 SAST >> To: ccNSO-techday(a)icann.org >> Cc: gtld-tech(a)icann.org >> Reply-To: el(a)lisse.NA >> >> 2nd Call for Presentations >> vTechDay >> at ICANN 80 >> (Kigali) >> >> The ICANN Tech Working Group is again planning a technical workshop at >> the ICANN 80 meeting (Kigali) >> >> As the meeting will be hybrid so will be vTechDay which is currently >> penciled in for Monday, 2024-06-10 for two blocks >> >> We shall try to accommodate the time zone of virtual presenters in >> setting the agenda. >> >> The TechDay workshop has been a part of ICANN meetings since 2006 and >> has provided a forum for both experienced and new people to meet, >> present and discuss technical topics related to registry and DNS work >> and security. >> >> We are specially interested in: >> >> 1. DNSSEC, in particular within the African Region >> >> 2. DNS Abuse Prevention and Mitigation Tools >> >> 3. Best (security) management practices, lines of defense, to >> protect Registries from bad actors, attacks or malware, or even >> reports of failures >> >> 4. In addition, we welcome suggestions for additional topics >> >> If you are interested in presenting, please email us at >> ccNSO-techday(a)icann.org or reply to this email. >> >> We hope that you can join us and request that you disseminate this >> Request to other lists where it might of interest. >> >> greetings, el >> >> -- >> Eberhard W. Lisse \ /Obstetrician & Gynaecologist (retired) >> el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) >> PO Box 8421 Bachbrecht\ / If this email is signed with GPG/PGP >> 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply >> >> _______________________________________________ >> CCNSO-TechDay mailing list >> CCNSO-TechDay(a)icann.org >> https://mm.icann.org/mailman/listinfo/ccnso-techday >> >> _______________________________________________ >> 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. >> _______________________________________________ >> gtld-tech mailing list >> gtld-tech(a)icann.org >> https://mm.icann.org/mailman/listinfo/gtld-tech >> >> ________________________________________________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. > — Regards Theo Kramer DNS.Business DISCLAIMER: The email and its contents are confidential, unless specifically stated or if this is manifestly clear from the context (including, by way of example, press releases and other official statements, issued by way of email). If you are not certain of the confidentiality status of an email, please contact the sender to confirm this. In addition, emails may be logged for archival purposes and may be reviewed by parties at DNS other than those named in the message header. Any unauthorized copying, disclosure, adaption, distribution, publication and/or use of, or any other unauthorized action taken based on this email message, is strictly prohibited and may be unlawful and an infringement of copyright.

1 0

CZDS and RRI experiencing slower response
by Victor Figueroa Vazquez May 13, 2024

May 13, 2024

Dear colleagues, Please note we are currently experiencing slower response from the Centralized Zone Data Service (CZDS) and Registration Reporting Interfaces (RRI) services. We are actively working to fix this issue. We apologize for any inconvenience. We will keep you posted. Best, Victor Figueroa ICANN

1 1

CZDS service are currently experiencing a temporary downtime
by Mustafa Alrifaee May 8, 2024

May 8, 2024

Hello All, We wanted to inform you that our CZDS service are currently experiencing a temporary downtime. Our team is actively investigating the issue and working to fix it. We apologize for any inconvenience this may cause. Best Regards Mustafa Alrifaee Internet Corporation for Assigned Names and Numbers (ICANN)

1 1

FW: ROW13 - Final call for proposals
by Hollenbeck, Scott May 6, 2024

May 6, 2024

Last call, everyone! Scott From: 'Row' via Regiops <regiops(a)googlegroups.com> Sent: Monday, May 6, 2024 5:36 AM Subject: [EXTERNAL] [regiops] ROW13 - Final call for proposals 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. The 13th Registration Operations Workshop<https://secure-web.cisco.com/1QkFUTylp0sso8GOnOCpBRwz9x-NXbYMVpb_pw3n4YfMRK…> (ROW13) will be conducted virtually via Zoom on June 4th, 2024, 13:00 - 17:00 UTC. (check local time zone here<https://secure-web.cisco.com/1RspsVaZn0RQsJW06XJD9smIH8cVfZlxM_8M4YNoDlxl6r…>). >>> Proposals: LAST CALL! Please submit a brief abstract outlining your proposal to row(a)cofomo.com<mailto:row@cofomo.com> by May 10th, 2024. We will consider presenter time zones when scheduling the agenda. We invite submissions guided by this non-exhaustive list of broad topics: ••••••••••••••••••••• RDDS from an operational perspective * RDAP implementation experience * Implementation of NIS2 Directive * New DNS Delegation (deleg) - impact on registration systems * Best practices for DNSSEC Key management * DNS abuse * How might Artificial Intelligence (AI) affect the registration ecosystem * Topics relevant to EPP, RPKI and other protocols relevant to Registration Systems * Digital Identity topics (eIDAS, etc.) * Registry/Registrar Industry Coming of Age: o Handling turnover of staff or platform providers, transitioning * Evolving the role of the registry/registrar within the Internet economy/environment (meaning, gov’t/others) * Does having a distributed workforce help or hinder the operations of a registry/registrar? >>> Registration<https://secure-web.cisco.com/1xFrBU0-_lI-66CayPATbuQvn_4k_-Dus3bdy9bCF1C_QC…> is required to enable participation! Attendance is free, but registration is mandatory to receive conference login credentials. ROW events are open to all industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, and second level domain registries. >>> Important dates! ••••••••••••••••••••• Deadline to submit proposals: May 10th, 2024 * Program Committee to notify selected authors by May 14th, 2024 * Speaker materials required from selected presenters by May 28th, 2024 * ROW13 event: June 4th, 2024, 13:00-17:00 UTC We hope that you can join us and look forward to receiving your proposals!!! Please feel to share this note with other relevant lists and contacts where it might be of interest. Thank you. <https://secure-web.cisco.com/1QkFUTylp0sso8GOnOCpBRwz9x-NXbYMVpb_pw3n4YfMRK…> ROW Program Committee regiops.net<https://secure-web.cisco.com/1QkFUTylp0sso8GOnOCpBRwz9x-NXbYMVpb_pw3n4YfMRK…> | row(a)cofomo.com<mailto:row@cofomo.com> | regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> <https://twitter.com/ROWevents> <https://secure-web.cisco.com/1dkT81NaiRiF5rne51runSoq1W7koLeWCZe4wxAxGwTBxM…> Sponsored by: Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1wF1If32PMdAVUav5kUpo25IZGx0qFzs4FSqGVdED7pHRZ…> Organized by: Cofomo<https://secure-web.cisco.com/1wwW1QjJDAmzAVbHhjOqxiloZecMyByABtDFmw3hKe94oM…> Cross-posting to multiple lists - sorry for any duplicates. To stop receiving ROW updates, please reply ‘unsubscribe’ to this email. -- You received this message because you are subscribed to the Google Groups "Regiops" group. To unsubscribe from this group and stop receiving emails from it, send an email to regiops+unsubscribe(a)googlegroups.com<mailto:regiops+unsubscribe@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/regiops/BN9PR14MB50507F7C08969520587EE159…<https://groups.google.com/d/msgid/regiops/BN9PR14MB50507F7C08969520587EE159…>.

1 0

Re: [gtld-tech] Tech day talk on RDAP Conformance Tool
by Andy Newton May 2, 2024

May 2, 2024

Sorry… didn’t mean to spam the list. I hate Outlook! -andy From: gtld-tech <gtld-tech-bounces(a)icann.org> on behalf of Andy Newton via gtld-tech <gtld-tech(a)icann.org> Reply-To: Andy Newton <andy.newton(a)icann.org> Date: Thursday, May 2, 2024 at 2:32 PM To: Dr Eberhard W Lisse via gtld-tech <gtld-tech(a)icann.org> Subject: [gtld-tech] Tech day talk on RDAP Conformance Tool Hi Dr. Lisse, I would like to propose a TechDay talk on the ICANN RDAP Conformance Tool. The talk would focus on changes ICANN plans to make to the RDAP Conformance Tool to make it easier to use, bring it up to date with latest standards, and add missing tests. In addition, we would also like to cover common RDAP server implementation mistakes. Finally, we’d like to try to get feedback from participants regarding ICANN’s RDAP Conformance Tool regarding improvements they would like to see implemented. This would be given as a remote presentation. -- Andy Newton Principal Engineer GDS Technical Services, ICANN

1 0

Tech day talk on RDAP Conformance Tool
by Andy Newton May 2, 2024

May 2, 2024

Hi Dr. Lisse, I would like to propose a TechDay talk on the ICANN RDAP Conformance Tool. The talk would focus on changes ICANN plans to make to the RDAP Conformance Tool to make it easier to use, bring it up to date with latest standards, and add missing tests. In addition, we would also like to cover common RDAP server implementation mistakes. Finally, we’d like to try to get feedback from participants regarding ICANN’s RDAP Conformance Tool regarding improvements they would like to see implemented. This would be given as a remote presentation. -- Andy Newton Principal Engineer GDS Technical Services, ICANN

1 0

FW: ROW13 - Call for proposals & registrations
by Hollenbeck, Scott April 18, 2024

April 18, 2024

FYI, folks! Please note the 10 May submission deadline. Scott From: 'Row' via Regiops <regiops(a)googlegroups.com> Sent: Tuesday, April 16, 2024 6:33 AM Subject: [EXTERNAL] [regiops] ROW13 - Call for proposals & registrations 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. ROW13 Call for Proposals & Registrations | June 4th, 2024 | 13:00 - 17:00 UTC | Zoom Video Conference The 13th Registration Operations Workshop<https://secure-web.cisco.com/1IKQNIyXSdNWfitskL2MGJL93DVuOK6m9sfuLZTkER-5k4…> (ROW13) will be held via remote participation on June 4th, 2024, 13:00 - 17:00 UTC. (check local time zone here<https://secure-web.cisco.com/1wfbbR5EN6gQad7KqpnV20oisv5pEaDj1r3PFirYytoiu9…>). >>> Registration<https://secure-web.cisco.com/1-RwNBzEhw27HfsyA-CvO4NGu02iVbcaGT-HVuZqQPx8_y…> for ROW13 is NOW available! The attendance is free but registration is required to receive conference login credentials. ROW events are open to all industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, and second level domain registries, to present and discuss technical topics related to real world experiences of implementing registration operations, such as RDAP, EPP, WHOIS, RPKI, Registry Lock, and many more. >>> ROW13 call for presentation & panel proposals is still OPEN! Please submit a short abstract describing your proposal to row(a)cofomo.com<mailto:row@cofomo.com> by May 10th, 2024. We will accommodate presenter time zones in setting the agenda. We invite submissions guided by this non-exhaustive list of broad topics. We also encourage any discussions/suggestions for additional topics on ROW’s mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com>. * RDRS from an operational perspective * RDAP implementation experience * Implementation of NIS2 Directive * New DNS Delegation (deleg) - impact on registration systems * Best practices for DNSSEC Key management * DNS abuse * How might Artificial Intelligence (AI) affect the registration ecosystem * Topics relevant to EPP, RPKI and other protocols relevant to Registration Systems * Digital Identity topics (eIDAS, etc.) * Registry/Registrar Industry Coming of Age: * Handling turnover of staff or platform providers, transitioning * Evolving the role of the registry/registrar within the Internet economy/environment (meaning, gov’t/others) * Does having a distributed workforce help or hinder the operations of a registry/registrar? >>> Important dates! • Deadline to submit proposals: May 10th, 2024 • Program Committee to notify selected authors by May 14th, 2024 • Speaker materials required from selected presenters by May 28th, 2024 • ROW13 event: June 4th, 2024, 13:00-17:00 UTC We hope that you can join us and look forward to receiving your proposals!!! Please feel to share this note with other relevant lists and contacts where it might be of interest. Thank you. <https://secure-web.cisco.com/1IKQNIyXSdNWfitskL2MGJL93DVuOK6m9sfuLZTkER-5k4…> ROW Program Committee regiops.net<https://secure-web.cisco.com/1IKQNIyXSdNWfitskL2MGJL93DVuOK6m9sfuLZTkER-5k4…> | row(a)cofomo.com<mailto:row@cofomo.com> | regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> <https://twitter.com/ROWevents> <https://secure-web.cisco.com/1WulHN4pdmLxakLIfRzBcOymxceRtaNgEdpsrNN_HViZeR…> Sponsored by: Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1CD9ybqRA9do-1E4y14i7Q2d8_ExRxyYEAve4M2BoQ4wNz…> Organized by: Cofomo<https://secure-web.cisco.com/1AwtH1uXBhA5-smlkWbc54qGUEDep21nu3ecedXcBtB6hg…> Cross-posting to multiple lists - sorry for any duplicates. To stop receiving ROW updates, please reply ‘unsubscribe’ to this email. -- You received this message because you are subscribed to the Google Groups "Regiops" group. To unsubscribe from this group and stop receiving emails from it, send an email to regiops+unsubscribe(a)googlegroups.com<mailto:regiops+unsubscribe@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/regiops/BN9PR14MB5050EEE48CB1C9DD598B37D0…<https://secure-web.cisco.com/1h1AgpaDhf6-mUWEFwmP9Dezccxk4qTmNPjTblzf4rJu0F…>.

1 0

Call for Presentation TechDay ICANN80 Kigali
by Dr Eberhard W Lisse April 15, 2024

April 15, 2024

Call for Presentations vTechDay at ICANN 80 (Kigali) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 80 meeting (Kigali) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2024-06-10 for two blocks We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the African Region 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Eberhard W. Lisse \ /Obstetrician & Gynaecologist (retired) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht\ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

Review of the Registry System Testing 2.0 Test Specifications and API
by Gavin Brown March 26, 2024

March 26, 2024

Hi all, The Public Comment proceeding for the Registry System Testing 2.0 Test Specifications and API is now live and may be found at the link below: https://www.icann.org/en/public-comment/proceeding/review-of-the-registry-s… Regards, -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org

1 0

FW: ROW13 - Call for proposals
by Hollenbeck, Scott March 19, 2024

March 19, 2024

FYI, folks! Please note the date of the next Registration Operations Workshop (ROW) and the deadline for presentation abstracts (10 May 2024). Scott From: Row <row(a)cofomo.com> Sent: Tuesday, March 19, 2024 9:48 PM Subject: ROW13 - Call for proposals ROW13 Call for Proposals is Now Open! | June 4th, 2024 | 13:00 - 17:00 UTC | Zoom Video Conference Since 2014, thanks to our sponsors Verisign <https://www.verisign.com/> and ICANN <https://secure-web.cisco.com/1W6iwSiMoSb7k28GwPZwL5RZ1D3uiRX0z9BNCskjQPd89E VOAGk7owK2NWB29cVD8jv6ZWCan_uh4x6l6V1BLKOEy68bnzaf8DPdWEXPuM4ncisAiFQ3nromS- gBM3KhRqgBvaLZcUHS1QwDBeTmXuFsTnm6yBfs2rf4JPh7_9mg_VltwmO24Fw9FGDUMYsv33M9st cYFUe5y0PMjc31B2phcKYTwGms9KOjQMoPtnE7i5e0gFYmbLk5MGsKus0utfWwji832GE28s2Im- 4bDxge9lksqY2y77DuqWf3vTmcsbFs-XgjegOCROoKFpkqm/https%3A%2F%2Fwww.icann.org% 2F> , the Registration Operations Workshop <https://secure-web.cisco.com/1BFBbKFuzsLQ5LlS3ZNLhoW-auOU8lbTet52QIufq_jJSk dx6XE7P6DVbSMfTbPgJ3t7f67DSbMQTdkaW8YaOslwdj0__3SX3tEqoUI6vyta_5D26qcEPmO9uV aim1sppz_ZqvjBJ0ZlaflW2e9Oi43160F3xDWmPUPQGVeMqSfTJ_NkBUQBXZtmPWo4k4bLRuPZtd n6SOoX7Ey5SGREFeHnzIl_XMClMFBolwRgoB7jRzJqNEV5hJJiVFNZJw3rdLm3Pjr4voxj3fmiTA FAnZzUszd_erfVvJi7eRvwCih0UH5Ct2zm5JGIB3Or4n9Mq/https%3A%2F%2Fregiops.net%2F > (ROW) brings together industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, and second level domain registries, to present and discuss technical topics related to real world experiences of implementing registration operations, such as RDAP, EPP, WHOIS, RPKI, Registry Lock, and many more (https://regiops.net/events <https://secure-web.cisco.com/1sRwQVHc7dPsboBD4idcV_7KQ-tqXgRuDbQIowx459Q2Sz af0Q1avdyPOvB6qxJ3z26hvrR1lwXn238qZ0zZ1dU34rMNY4ZShK8AWN53KFrrIGHfkzxAxPIxc0 TX3DErdbce7HJMoHpjtjgGD1sIRskg7mRFO2d3_V1nXjvH49WO64wvzDCdh6UDwn_L_wafGMBDqq JeQvVwbZYYRp8pGv_RSnWGKTuLEAKbZQYnT1q3jSvEoxHoTk69ltNYfA7tZefAJUmLE_TGWOTbAq YMyTyd8u4aUvMwaJacWIDZGz0dJooMnYcMDW8FB3N9drK-z/https%3A%2F%2Fregiops.net%2F events> ). The Program Committee has now opened the call for proposals for ROW13 and invites you to submit a short abstract describing your presentation or panel proposal to our email address row(a)cofomo.com <mailto:row@cofomo.com> by May 10th, 2024. We invite submissions guided by this non-exhaustive list of broad topics and encourage any discussions/suggestions for additional topics on ROW's mailing list: regiops(a)googlegroups.com <mailto:regiops@googlegroups.com> * RDRS from an operational perspective * RDAP implementation experience * Implementation of NIS2 Directive * New DNS Delegation (deleg) - impact on registration systems * Best practices for DNSSEC Key management * DNS abuse * How might Artificial Intelligence (AI) affect the registration ecosystem * Topics relevant to EPP, RPKI and other protocols relevant to Registration Systems * Digital Identity topics (eIDAS, etc.) * Registry/Registrar Industry Coming of Age: o Handling turnover of staff or platform providers, transitioning * Evolving the role of the registry/registrar within the Internet economy/environment (meaning, gov't/others) * Does having a distributed workforce help or hinder the operations of a registry/registrar? The Program Committee will notify selected authors by May 14th, 2024 (additional ROW13 important dates available at https://regiops.net <https://secure-web.cisco.com/1BFBbKFuzsLQ5LlS3ZNLhoW-auOU8lbTet52QIufq_jJSk dx6XE7P6DVbSMfTbPgJ3t7f67DSbMQTdkaW8YaOslwdj0__3SX3tEqoUI6vyta_5D26qcEPmO9uV aim1sppz_ZqvjBJ0ZlaflW2e9Oi43160F3xDWmPUPQGVeMqSfTJ_NkBUQBXZtmPWo4k4bLRuPZtd n6SOoX7Ey5SGREFeHnzIl_XMClMFBolwRgoB7jRzJqNEV5hJJiVFNZJw3rdLm3Pjr4voxj3fmiTA FAnZzUszd_erfVvJi7eRvwCih0UH5Ct2zm5JGIB3Or4n9Mq/https%3A%2F%2Fregiops.net%2F > ). We look forward to receiving your proposals. Registration process will be made available shortly on our website. Please feel free to disseminate this call for proposals to other lists and contacts where it might be of interest. Thank you. <https://secure-web.cisco.com/1BFBbKFuzsLQ5LlS3ZNLhoW-auOU8lbTet52QIufq_jJSk dx6XE7P6DVbSMfTbPgJ3t7f67DSbMQTdkaW8YaOslwdj0__3SX3tEqoUI6vyta_5D26qcEPmO9uV aim1sppz_ZqvjBJ0ZlaflW2e9Oi43160F3xDWmPUPQGVeMqSfTJ_NkBUQBXZtmPWo4k4bLRuPZtd n6SOoX7Ey5SGREFeHnzIl_XMClMFBolwRgoB7jRzJqNEV5hJJiVFNZJw3rdLm3Pjr4voxj3fmiTA FAnZzUszd_erfVvJi7eRvwCih0UH5Ct2zm5JGIB3Or4n9Mq/https%3A%2F%2Fregiops.net%2F > ROW Program Committee regiops.net <https://secure-web.cisco.com/1rRYLovR-ZqKBQKjqjb5cYJGoZP_zdb1n9YQyXOAa8PZQc Utbx5w4zv9KLAaMsQuaVC8IsXDn8e6l4N5clfzcgsMQW0v9td8rQlKSJNvyOwNjrFHdnG24s3JBP 8T7K77rNIuDkDUO1-Z9XJ2JjXR8MWn2c8AipOecCJ-cxfGVLVatLJRXnk0-ETpYXnC8y3apvATZi hpQB7EHh0eXKOvBO1copqeSWPWm-kCbIKsk-tBp4TFSn6NauZpDtfhm5onodvxPZoYM-EYg8JCk7 gOzIBCmh0C8ldhexA90L7_AMoCF61d3ibB0JYUfG_-eDloj/https%3A%2F%2Fregiops.net> | row(a)cofomo.com | regiops(a)googlegroups.com <https://twitter.com/ROWevents> <https://secure-web.cisco.com/1wJyE23YTNSrXe8U-gQo4q1tivA1iSnar6VXwfPRPmhcvX HpzqPPN-GnE8L6Bo-cKV-wnpx53UwGXxb0FD4GC-kVkZ8ByYFmsgtxet75S6gTy5DhBFvliYXPMI ptffpTr0KSG4OkT0915H0NwufwRc1FUXlypP8dtEuW20DgpoWiWZiMg3lc3GUA_L-JEifLOdei4r ARYe9roWSpXs9JtCozcKBO2fJIKa9YZi4LVHBZR9lcrX5Mf301ruNA7rLSIaabH0GmShXWtpcZ0I tok83v0HCmh1MsIftyT75tQ1BqibElwXICmHM9GbDQHdyzC/https%3A%2F%2Fwww.linkedin.c om%2Fcompany%2Fregiops> Sponsored by: Verisign <https://www.verisign.com/> & ICANN <https://secure-web.cisco.com/1W6iwSiMoSb7k28GwPZwL5RZ1D3uiRX0z9BNCskjQPd89E VOAGk7owK2NWB29cVD8jv6ZWCan_uh4x6l6V1BLKOEy68bnzaf8DPdWEXPuM4ncisAiFQ3nromS- gBM3KhRqgBvaLZcUHS1QwDBeTmXuFsTnm6yBfs2rf4JPh7_9mg_VltwmO24Fw9FGDUMYsv33M9st cYFUe5y0PMjc31B2phcKYTwGms9KOjQMoPtnE7i5e0gFYmbLk5MGsKus0utfWwji832GE28s2Im- 4bDxge9lksqY2y77DuqWf3vTmcsbFs-XgjegOCROoKFpkqm/https%3A%2F%2Fwww.icann.org% 2F> Organized by: Cofomo <https://secure-web.cisco.com/1Jo3V3oeLc3zNAMP1nDl54BokDMBcNopCywRnjl0JSFwW9 tbPZxCVzRloQ5hYdWTayFDoiH2XTvxok2HBi0OEv8zpW9hC4lEehjCfG1qXR509mzJD31w7DORLx 0t0Ty1DAztL-Y0kfhWKcvd7Sd3YUfLodu5G5hfCE1ywWtXCi6IEqzSEBlFvhd7ML1591WjnEaLKE ro3UXs5GNfD9WqIjfGco4YGVcHF3UGdNQKEnKaizG2C_s-uj1PhTks9YOdw5LAs8vXaX7biY1_ph XpgF4SdjagI2Vdf5q0v4M-sM7-NzQiVgFtT-YRI0p2EyGLx/https%3A%2F%2Fwww.cofomo.com %2Fen> Cross-posting to multiple lists - sorry for any duplicates. To stop receiving ROW updates, please reply 'unsubscribe' to this email.

1 0

Public Comment proceedings now open for the Registry Service Provider Program
by Andy Newton March 13, 2024

March 13, 2024

Hi all, As part of opening the next round of applications for new gTLDs, ICANN is establishing a program that will separately evaluate organizations that provide technical services such as EPP, RDAP, DNS, etc,. from the organizations applying for gTLD labels. These Registry Service Providers (RSPs) will be able to offer their services to multiple gTLDs as part of this program. All organizations are eligible to become an evaluated RSP, regardless of past experience providing gTLD services. ICANN published RSP application materials for Public Comment today with final versions expected in May 2024. The RSP application period is expected to begin in the last quarter of 2024. The details of the RSP Evaluation Program are currently in development and being discussed as part of the work of the New gTLD Program Subsequent Procedures Implementation Review Team (IRT). If you would like to participate in the IRT, please complete this form. -- Andy Newton Principal Engineer GDS Technical Services, ICANN

1 0

Hopefully Final Agenda Hybrid TechDay ICANN 79 (San Juan)
by Eberhard W Lisse Feb. 21, 2024

Feb. 21, 2024

All, please find enclosed. el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

2nd Call For Presentation TechDay ICANN 79 San Juan
by Eberhard W Lisse Feb. 1, 2024

Feb. 1, 2024

2nd Call for Presentations vTechDay at ICANN 79 (San Juan) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 79 meeting (San Juan). The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. As the ICANN meeting will be hybrid so will be vTechDay which currently is penciled in for Monday 2024-03-04 and we shall try to accommodate the time zone of virtual presenters when setting the agenda. We are especially interested in: 1. DNS Abuse Prevention and Mitigation Tools 2. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 3. Identity Verification Tools and Methods 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please reply to this email or email us at ccNSO-techday(a)icann.org with a short (not more than 10 lines), unformatted abstract. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Eberhard W. Lisse \ /Obstetrician & Gynaecologist (retired) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht\ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply _______________________________________________ CCNSO-TechDay mailing list CCNSO-TechDay(a)icann.org https://mm.icann.org/mailman/listinfo/ccnso-techday _______________________________________________ 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.

1 0

Fwd: [SubPro-IRT] Review of RST Test Specifications
by Gavin Brown Feb. 1, 2024

Feb. 1, 2024

Hi all, I'm forwarding this as I think it may be relevant to this list. ICANN org is seeking feedback from the technical community on the new Registry System Testing (RST) specifications. If you are a current or prospective gTLD registry operator or Registry Services Provider, or have subject matter expertise on the same, your input would be appreciated! Thanks, Gavin. Begin forwarded message: From: Next Round Policy Implementation <NextRound_PolicyImplementation(a)icann.org> Subject: [SubPro-IRT] Review of RST Test Specifications Date: 1 February 2024 at 14:03:28 GMT To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Dear IRT members, An IRT meeting focused specifically on the Registry System Testing (RST) will be held on 13 February 2024 at 14:00-15:00 UTC. For more information, please refer to the meeting page: * https://community.icann.org/x/boPxDg As you may be aware, as part of our Next Round activities, ICANN org has been working on a new Registry System Testing (RST) service (RST v2.0), which includes a new set of test specifications and a RESTful API that will fully automate the process of testing, for both the RSP Evaluation Program, as well as Pre-Delegation Testing and post-delegation RST. Details of the new test specifications and the API were provided during ICANN78 in Hamburg[1] and the IRT RST Sub-Track Meeting #1 on 14 December 2023[2]. Since those meetings, we have made significant progress on developing the test specifications and the API specification, both of which have been published on GitHub: * https://icann.github.io/rst-test-specs/rst-test-specs.html * https://icann.github.io/rst-api-spec/rst-api-spec.html As we are approaching the anticipated Public Comment period (planned to begin at the end of March) for the RST v2.0 project, we are inviting members of the IRT and the TLD technical community to provide their feedback on the test and API specifications. The RST test specifications are broken down into ten separate test plans[3], each covering a particular scenario. For RSP evaluation, the relevant plans are the Main RSP Evaluation Test, IDN Test (RSP Evaluation), DNS RSP Evaluation Test, DNSSEC RSP Evaluation Test, and SRS Gateway RSP Evaluation Test. Each test plan uses one or more test suites[4], each of which covers a different registry service, such as EPP, RDAP, DNS, DNSSEC, Data Escrow, etc. Each test suite uses one or more test cases that test a specific component of that registry service. Each test case is tagged with a “Maturity” level, which is one of “ALPHA”, “BETA” or “GAMMA”. As of writing, most test cases are at BETA level or higher: while we welcome all feedback, we encourage you to avoid spending too much time reviewing the ALPHA-level cases, as these are the ones most likely to change in the future. To provide stability and predictability, we have moved to a weekly release process, where the test specifications are only updated once per week (on a Wednesday). Each release will be accompanied by a Change Log, which can be found: * https://icann.github.io/rst-test-specs/rst-test-specs.html#change-log If you are interested in seeing the most up to date version of the specifications, they are available in the “dev” branches of the GitHub repositories: * https://github.com/icann/rst-test-specs/tree/dev * https://github.com/icann/rst-api-spec/tree/dev Submitting Feedback We request to use GitHub to submit feedback. Each of the above repositories has its own issue tracker that can be used to submit feedback. You will need a GitHub account in order to submit issues. Current system For your reference, you may find the test specifications of the current RST system in the following link: https://www.icann.org/resources/registry-system-testing [1] https://community.icann.org/pages/viewpage.action?pageId=264372276 [2] https://community.icann.org/pages/viewpage.action?pageId=282951922 [3] https://icann.github.io/rst-test-specs/rst-test-specs.html#test-plans [4] https://icann.github.io/rst-test-specs/rst-test-specs.html#test-suites Best regards, Gustavo, Gavin, and Elisa _______________________________________________ SubPro-IRT mailing list SubPro-IRT(a)icann.org<mailto:SubPro-IRT@icann.org> https://mm.icann.org/mailman/listinfo/subpro-irt _______________________________________________ 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. -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org

1 0

CZDS download is broken due to failed auth server
by John Levine Jan. 31, 2024

Jan. 31, 2024

When my scripts try to contact https://account-api.icann.org to get a token, it rejects the connections. I gather I am not the only one seeing this problem. Anyone known when it'll be fixed? R's, John

4 4

Call For Presentation TechDay ICANN 79 San Juan
by Dr Eberhard W Lisse Jan. 23, 2024

Jan. 23, 2024

Call for Presentations vTechDay at ICANN 79 (San Juan) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 79 meeting (San Juan). The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. As the ICANN meeting will be hybrid so will be vTechDay which currently is penciled in for Monday 2024-03-04 and we shall try to accommodate the time zone of virtual presenters when setting the agenda. We are especially interested in: 1. DNS Abuse Prevention and Mitigation Tools 2. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 3. Identity Verification Tools and Methods 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please reply to this email or email us at ccNSO-techday(a)icann.org with a short (not more than 10 lines), unformatted abstract. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Eberhard W. Lisse \ /Obstetrician & Gynaecologist (retired) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht\ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

.gov zone file downloads stale since November 16?
by Joe Wein Dec. 14, 2023

Dec. 14, 2023

I am getting strange results where if I download a zone file from the browser after logging into the ICANN acount, I get yesterday's version as expected, yet the scripted downloads pick up a .gz that when extracted has a file dated November 16 and a serial in the vicinity of that date's epoch count: 1700092762 (2023-11-15 23:59:22) I did a browser download three days ago and it gave me: 1702261500 (2023-12-11 02:25:00) Today's download via the browser gives me: 1702520700 (2023-12-14 02:25:00) That raises a few questions: 1) Why is the regular download stuck in November? 2) Why is the website download unaffected? 3) Recent downloads give me a consistent time stamp for the time of day which is different from the stuck version, which is just before midnight. What changed there? Is it just me or can anybody else confirm this observation? Can we please fix this *and* add robust monitoring so that broken updates generate an alert! Joe SURBL

5 5

Problems on the CZDS and ZFA expiry even with extensions requested?
by John McCormac Dec. 1, 2023

Dec. 1, 2023

Are there problems with the CZDS as I've had a number of ZFAs expire even though extensions have been requested (2 more on 28/November/2023) The extension requests were filed on 03/November/2023)? ICANN Compliance seems to take weeks to get around to dealing with complaints. Regards...jmcc -- ********************************************************** John McCormac * e-mail: jmcc(a)hosterstats.com MC2 * web: http://www.hosterstats.com/ 22 Viewmount * Domain Registrations Statistics Waterford * Domnomics - the business of domain names Ireland * https://amzn.to/2OPtEIO IE * Skype: hosterstats.com ********************************************************** -- This email has been checked for viruses by Avast antivirus software. www.avast.com

2 1

.DESI to Be Placed in the Emergency Back-end Registry Operator Program
by Francisco Arias Oct. 20, 2023

Oct. 20, 2023

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello all, ICANN is transferring the operation of the .DESI gTLD to an Emergency Back-end Registry Operator (EBERO) to ensure the continued operation of the generic top-level domain (gTLD) and protect registrants. As part of this transfer, .DESI has transitioned from a secure DNSSEC state to an insecure DNSSEC state (i.e., the DS records for .DESI have been removed from the root zone). After the transfer, ICANN will work with the designated EBERO provider to transition the .DESI gTLD back to a secure state (i.e., signing the zone for .DESI and adding new DS records for .DESI in the root zone). After evaluating available options, we believe the temporary move to an insecure state was the best available option. For more information, please see the announcement at https://www.icann.org/en/announcements/details/desi-to-be-placed-in-the-eme… - - -- Francisco Arias Sr. Director, Technical Services Global Domains & Strategy ICANN https://icann.org/resources/pages/pgp-keys-2012-02-25-en#FranciscoArias -----BEGIN PGP SIGNATURE----- iQFOBAEBCgA4FiEEH96Bn3vsHLISfu5Umk0ze9UQ45cFAmUuf/caHGZyYW5jaXNj by5hcmlhc0BpY2Fubi5vcmcACgkQmk0ze9UQ45eapgf+O6OlrzpuFY5loiIhKkEk wJ1vh0qZQZXWE7UFhY2ixcip3xd7h+S37xEb8E895RxtWp8jMrZ8EtXAltT/bylG K0Q5xAzACnsznMLSrZ7a4K47D+Igpm8iINEUSofsiuQDDLUr9e5/MGljHP4JOSr6 7AZfMonb67+i0rSAOIS+x3DUGoDtEj5/W/2R1BD6CdrhHp0iDtcT8vnMR7aMr+hl bx+1f4p86Vwk1QaEYxUOWQhoFfFNHUD3iG3+z7Sw4xdE4Xaa8AOzRy74947ZqbC0 kjdp6PYvGzc3Q7ZvZ/TwxM06s4vr7fsLxrslUqZ9c8qJlNkGaLX9/kS7ezOlRi7p Vg== =QVDv -----END PGP SIGNATURE-----

8 20

[ccnso-techwg] Call For Presentation TechDay ICANN 78 Hamburg
by Dr Eberhard W Lisse Oct. 15, 2023

Oct. 15, 2023

Call for Presentations vTechDay at ICANN 78 (Hamburg) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 78 meeting (Hamburg). The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. As the ICANN meeting will be hybrid so will be vTechDay which currently is penciled in for Monday 2023-10-23 and we shall try to accommodate the time zone of virtual presenters when setting the agenda. We are especially interested in: 1. DNS Abuse Prevention and Mitigation Tools 2. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 3. In addition, we welcome suggestions for additional topics If you are interested in presenting, please reply to this email or email us at ccNSO-techday(a)icann.org. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el

1 2

Zodiac Registry: "access request for .xn--czru2d has been denied"
by Joe Wein Sept. 14, 2023

Sept. 14, 2023

I've had several requests for TLD ".xn--czru2d" denied by them recently. After applying for renewal (I've repeatedly renewed since 2015), they now send an email directing you to go to their website and email them additional information. This is what it says on their website: ==== .商城 AnnouncementCredentialing Requirements for CZDS applicant to access the xn-- czru2d Zone Files 一、简介 Zodiac Aquarius Limited（“注册局”）根据与ICANN签订的“.商城”域名RA协议specification 4中section 2的相关条款，对申请访问区域文件的个人或者组织（“申请人”），在验证环节，增加必要的材料审核，以确保区域文件不被滥用，特制定本补充政策（“政策”）。二、申请材料申请人需在收到注册局邮件通知7日内，将以下材料发送到mall-czds(a)nic.wang: a.. 1.邮件标题需为申请人在CZDS 申请时所用帐号的用户名b.. 2.申请人是组织机构的，需提供：（1）180天以内签发的组织存续证明（CCR）；（2）包含办理人姓名、职位等信息的组织授权文件；（3）组织机构的网址；（4）组织机构简介（重点提供域名相关的部分）；（5）防止区域文件被滥用的说明书；（6）保护区域文件不被滥用的承诺书。 c.. 3.申请人是个人的，需提供：（1）个人身份证件；（2）一份180天以内的个人的水/电/煤气账单（3）个人简介（重点提供域名相关的部分）（4）防止区域文件被滥用的说明书；（5）保护区域文件不被滥用的承诺书；（6）申请人不属于任何域名注册局，注册商，分销商的承诺书。三、审核申请人在收到注册局邮件通知7日内，未按规定发送材料邮件的，注册局将在CZDS系统拒绝。注册局在收到申请人的材料邮件后，将在15日内完成材料的完整性审核，材料完整的，将在45日内做出同意或者不同意的决定。同意的，将在CZDS系统批准，不同意的，将在CZDS系统拒绝。四、关于本政策注册局有权根据国家或者ICANN的法律政策调整等原因，修改本政策，无需事先通知。本政策和《CZDS条款》的目的相同，应视为一份文件来阅读和解释。 Zodiac Aquarius Limited 2022年11月24日 ==== If your Mandarin is as non-existent as mine, they're basically asking for official documents on the level of trying to open a corporate bank account at a bank. Of course I had submitted all the information required by the CZDS application process through the ICANN website. Two weeks later they denied my application, with this "explanation": "the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2..." Surely this is not correct. Any process involving submitting documents by email would not scale to about 1200 zones in CZDS, even if it was done in English. Joe Wein SURBL

5 7

FW: ROW12 agenda & registration
by Hollenbeck, Scott June 8, 2023

June 8, 2023

Last note, folks, I promise! The final agenda and registration details are available and described below. Scott From: row-committee(a)googlegroups.com <row-committee(a)googlegroups.com> On Behalf Of nicoleta munteanu Sent: Thursday, June 8, 2023 7:44 AM Subject: [EXTERNAL] ROW12 agenda & registration 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. ROW12 | June 20th, 2023 | 13:00 - 17:00 UTC | Zoom Video Conference ROW12 will take place via Zoom Webinar platform on June 20th, 2023, 13:00 - 17:00 UTC. Additional time zones may be checked here<https://secure-web.cisco.com/1lab7tYtra6YFT0_k_2Fh610HgkNaxCenWS-apajx38y_p…>. Please note the session has been extended to 4 hours. ROW12 Agenda<https://secure-web.cisco.com/1yWO186S_-h_aB_zguXWnBfCKM1vxSm-Hnthb3XRxV-3sd…> is now available on our website. Those interested in attending are required to Register<https://secure-web.cisco.com/1yWO186S_-h_aB_zguXWnBfCKM1vxSm-Hnthb3XRxV-3sd…> in order to receive the webinar access information (meeting ID and password). If you have any questions, please contact us at: row(a)cofomo.com<mailto:row@cofomo.com> ----- Here are some special tips if this is your first time using Zoom or you wish to get more familiar with its web conferencing capabilities: * Download the Zoom application to your computer or mobile phone. You can do it at https://zoom.us/download<https://secure-web.cisco.com/1zvf50Eo_RxU7jHDLpJR5t3eCl_at9H8b3ZMwnyQOMaTMN…>. You will also be prompted to download and install Zoom when you click the link to join. You can also run Zoom from your web browser by navigating to join.zoom.us<http://secure-web.cisco.com/1NDCQyIrQdLqjsqnY6T0Ui8twL3zY92IcEEOqTOeh_iMPzJ…> and entering the meeting number and passcode. * Want to try it out before June 20th? Join a test meeting at https://zoom.us/test<https://secure-web.cisco.com/1L539P3OiMNHaVM7otbM8EmvkWAEMJX1anWpVOPcCELe3G…> anytime to familiarize yourself with Zoom. You can also access Zoom tutorials here: https://support.zoom.us/hc/en-us/articles/201362193-How-Do-I-Join-A-Meeting<https://secure-web.cisco.com/1BRTvFOXVadQ3flpwb21yqzj35avZxUYIJGNNVvJ6RKURd…> * As an attendee, you will be muted. For questions and comments, please use the Q&A feature. The session moderator will address them to the speakers on the mike as time permits. Questions that cannot be answered due to time constraints, will be answered directly in the Q&A window or by email. * We will be recording this webinar, including the chat, and making it available on our website 24-48h after the session. ----- We would like to thank our ROW Series Sponsors ICANN<https://secure-web.cisco.com/1kXPotOGgAvxQSy8eJErxDuqwt1ko3sIkV5KAdQObtHFOB…> and Verisign<https://www.verisign.com/> for their continued support. We look forward to seeing you online! ROW Program Committee Stay tuned for further updates! Follow @ROWevents<https://twitter.com/ROWevents> ROW website: https://regiops.net<https://secure-web.cisco.com/1ovL2EO_2r-Nb4zff3BT9r_t_DXrlgkGRVGFe6sa0uUb2e…> Contact us: row(a)cofomo.com<mailto:row@cofomo.com> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1kXPotOGgAvxQSy8eJErxDuqwt1ko3sIkV5KAdQObtHFOB…>, organized by Cofomo Québec Inc.<https://secure-web.cisco.com/1TOa9F2yf2SaDrbyJePB8o7-fzO9h3Hoga63hMsy8E2Jrr…> (cross-posting to multiple lists - sorry for any duplicates)

1 0

Agenda TechDay ICANN 77
by Dr Eberhard W Lisse June 7, 2023

June 7, 2023

This is the 50'th TechDay by the way el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

3rd Call for Presentations Hybrid TechDay ICANN 77 (Washington)
by Dr Eberhard W Lisse June 7, 2023

June 7, 2023

This is the 50'th TechDay by the way el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

3rd Call for Presentations Hybrid TechDay ICANN 77 (Washington)
by Dr Eberhard W Lisse May 30, 2023

May 30, 2023

3rd Call for Presentations vTechDay at ICANN 77 (Washington) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 77 meeting (Washington) We have one slot of 20 Minutes left. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

xn--czru2d CZDS credentialing requirements?
by Viktor Dukhovni May 11, 2023

May 11, 2023

Dear gtld-tech, Is the RO operator of "xn--czru2d" compliant with obligations to provide CZDS access, in relation to the newly posted credentialing requirements? From: mall-czds <mall-czds(a)nic.wang> Date: Fri, 12 May 2023 10:41:09 +0800 (GMT+08:00) Subject: About Your CZDS Application for xn-- czru2d Zone Files To: ietf-dane(a)dukhovni.org receiver Dear applicant, comtent Your application is reviewed, please visit http://en.shangcheng.wang/notice.html to meet the “Credentialing Requirements for CZDS applicant to access the xn-- czru2d Zone Files”. Please be noted that if we do not get your email of the said credentialing requirements in 7 days, we will have to deny your access application via the CZDS. Once your credentialing requirements is considered completed, we will study carefully and then make the decision via the CZDS in 45 days. greetings Regards, Sender xn--czru2d Team The referenced web page further elaborates: Credentialing Requirements for CZDS applicant to access the xn--czru2d Zone Files 1. Introduction Zodiac Aquarius Limited (the "Registrar"), according to the relevant clauses in section 2 of specification 4 of the ".Mall" domain name RA agreement signed with ICANN, for individuals or organizations ("applicants") who apply for access to zone files, during the verification process, This Supplementary Policy ("Policy") is formulated to add necessary material review to ensure that zone files are not misused. 2. Application materials Applicants should send the following materials to mall-czds(a)nic.wang within 7 days of receiving the email notification from the registration office: 1). The title of the email must be the username of the account used by the applicant when applying in CZDS 2). The applicant is an organization and needs to provide: (1) Certificate of Organizational Continuity (CCR) issued within 180 days; (2) Organizational authorization documents containing information such as the name and position of the person in charge; (3) The website of the organization; (4) Brief introduction of the organization (emphasis is provided on the part related to the domain name); (5) Instructions for preventing zone files from being misused; (6) Commitment to protect zone files from misuse. 3). The applicant is an individual and needs to provide: (1) Personal ID card; (2) A personal water/electricity/gas bill within 180 days (3) Personal profile (focus on providing domain name related parts) (4) Instructions for preventing zone files from being misused; (5) A letter of commitment to protect the zone file from being abused; 3. Review If the applicant fails to send the materials by email within 7 days after receiving the email notification from the registration office, the registration office will reject it in the CZDS system. After receiving the applicant's material email, the registration office will complete the review of the completeness of the material within 15 days. If the material is complete, it will make a decision of approval or disapproval within 45 days. If you agree, it will be approved in the CZDS system, and if you disagree, it will be rejected in the CZDS system. 4. About this policy The Registry has the right to modify this policy without prior notice in accordance with national or ICANN legal policy adjustments and other reasons. This Policy and the "CZDS Terms" have the same purpose and should be read and interpreted as a document. Zodiac Aquarius Limited November 24, 2022 -- Viktor.

1 0

2nd Call for Presentations Hybrid TechDay ICANN 77 (Washington)
by Dr Eberhard W Lisse May 9, 2023

May 9, 2023

2nd Call for Presentations vTechDay at ICANN 77 (Washington) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 77 meeting (Washington) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2023-06-12 for two blocks: Blocks 1-2 13:00 UTC until 16:15 UTC, with one 30 minute break mandated by ICANN. We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the African (!) Region and with regards to SHA-1 Transition 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

FW: ROW12 - Final call for proposals
by Hollenbeck, Scott May 9, 2023

May 9, 2023

FYI, folks – final call for proposals. Scott From: row-committee(a)googlegroups.com <row-committee(a)googlegroups.com> On Behalf Of nicoleta munteanu Sent: Tuesday, May 9, 2023 5:04 AM Subject: [EXTERNAL] ROW12 - Final call for proposals 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. ROW12<https://secure-web.cisco.com/1assYtNxIflRU8taiRlYxLDR2tfgpPTla57ni2VC2U-T1X…> is scheduled to take place via remote participation on June 20th, 2023, 13:00 - 16:00 UTC. See additional time zones here<https://secure-web.cisco.com/1TiLhwN97Qm2MwRL28KSowvznQ9AFw42e2LOp_HcvTAk1h…>. —> Proposals: LAST CALL! The call for presentation and panel proposals is still open. Deadline is May 19th, 2023. Proposals in the form of a short abstract shall be submitted to row(a)cofomo.com<mailto:row@cofomo.com>. We will accommodate time zones for presenters in setting the agenda. In keeping with the Registration Operations' focus of the ROW, below is a non-exhaustive list of broad topics for this session. Discussions and suggestions for additional topics may also take place on the regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> mailing list. * Registries and DNS Hosting: * RPKI from a registry operator’s perspective * Experience with Universal Acceptance deployments * CDS/CDNSKEY or CSYNC deployment experience * Accommodating third party providers (i.e., not the registrant or registrar themselves) * Registries and Internet Ecosystem: * Registry database access * Interaction with Public Safety and Law Enforcement * Regulation, Current or Coming * Implementing Full-scale security, including Routing to Nameservers * Registry Industry Coming of Age: * Handling turnover of staff or platform providers, transitioning * Evolving the role of the registry within the Internet economy/environment (meaning, gov’t/others) —> Registration is required to enable participation! Those interested in attending the virtual meeting are required to register at the following link in order to receive the access information for the online session: https://regiops.net/event/12th-registration-operations-workshop-row12-onlin…<https://secure-web.cisco.com/1OFdb-H5lEtioWM4x3-AnuOd946uueg_Y3lgYEEtTHVRSJ…> —> ROW12 important dates! * Deadline to submit proposals: May 19th, 2023 * Program Committee to notify selected authors by May 23rd, 2023 * Speaker materials required from selected presenters by June 9th, 2023 * ROW12 event: June 20th, 2023, 13:00-16:00 UTC We look forward to your participation! Please feel free to disseminate this Call to other lists where it might be of interest. Thank you. ROW Program Committee Stay tuned for further updates! Follow @ROWevents<https://secure-web.cisco.com/1B0rPK1_2G1gx9kdIrSC529jiRE8CCEdU2B1LzXMYFBr7F…> ROW website: https://regiops.net<https://secure-web.cisco.com/1uLDKJLX3_oJe0I54W0RpRUCjH9ZyncrIQwBaIMFG1iy1a…> Contact us: row(a)cofomo.com<mailto:row@cofomo.com> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1GC6vbgNy1UD-kLD14osGf6NZUVQXCVr0cY8h5L8eG_sZq…>, organized by Cofomo Québec Inc.<https://secure-web.cisco.com/1eeUtc9-3IhJ0dGjb5ZnqsnZTXIHPsrMR2t-pn-5wo11-v…> (cross-posting to multiple lists - sorry for any duplicates) -- You received this message because you are subscribed to the Google Groups "Row Committee" group. To unsubscribe from this group and stop receiving emails from it, send an email to row-committee+unsubscribe(a)googlegroups.com<mailto:row-committee+unsubscribe@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/row-committee/DS7PR12MB57176AA8DAB9E9CE7A…<https://groups.google.com/d/msgid/row-committee/DS7PR12MB57176AA8DAB9E9CE7A…>. For more options, visit https://groups.google.com/d/optout.

1 0

FW: ROW12 -> Call for Proposals & Registration
by Hollenbeck, Scott April 26, 2023

April 26, 2023

FYI, folks. Scott From: row-committee(a)googlegroups.com <row-committee(a)googlegroups.com> On Behalf Of nicoleta munteanu Sent: Wednesday, April 26, 2023 8:41 AM Subject: [EXTERNAL] ROW12 -> Call for Proposals & Registration 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. ROW12 Call for Proposals and Registrataion | June 20th, 2023 | 13:00 - 16:00 UTC | Zoom Video Conference The 12th Registration Operations Workshop<https://regiops.net/> (ROW12) will be held via remote participation on June 20th, 2023, 13:00 - 16:00 UTC. See additional time zones here<https://secure-web.cisco.com/1mDGB1bizVN2LKJcuZTF75XEo9r2FBRLxz4gIYw81-PQdb…>. —> Registration is NOW available! Click here<https://regiops.net/event/12th-registration-operations-workshop-row12-onlin…> to register. —> The Call for presentation & panel proposals is still OPEN! The Program Committee is interested in: * Topic related presentation proposals * Topic suggestions for focused panel discussions * Suggestions for additional topics Please submit a short abstract describing your proposal to our NEW email address row(a)cofomo.com<mailto:row@cofomo.com> by May 19th, 2023. We will accommodate time zones for presenters in setting the agenda. Below is a non-exhaustive list of broad topics for ROW12. We also encourage any discussions/suggestions for additional topics on ROW’s mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com>. For further details on past workshop topics, see https://regiops.net/events * Registries and DNS Hosting: * RPKI from a registry operator’s perspective * Experience with Universal Acceptance deployments * CDS/CDNSKEY or CSYNC deployment experience * Accommodating third party providers (i.e., not the registrant or registrar themselves) * Registries and Internet Ecosystem: * Registry database access * Interaction with Public Safety and Law Enforcement * Regulation, Current or Coming * Implementing Full-scale security, including Routing to Nameservers * Registry Industry Coming of Age: * Handling turnover of staff or platform providers, transitioning * Evolving the role of the registry within the Internet economy/environment (meaning, gov’t/others) —> Important dates: * Deadline to submit proposals: May 19th, 2023 * Program Committee to notify selected authors by May 23rd, 2023 * Speaker materials required from selected presenters by June 9th, 2023 * ROW12 event: June 20th, 2023, 13:00-16:00 UTC We hope that you can join us!!! Register NOW and feel free to disseminate this Call to other lists where it might be of interest. Thank you. ROW Program Committee Stay tuned for further updates! Follow @ROWevents<https://secure-web.cisco.com/1VmqtXnfn_747vSAB5AAmaR27bkGn6BWj8TCWkY_zD-ZfX…> ROW website: https://regiops.net<https://regiops.net/> Contact us: row(a)cofomo.com<mailto:row@cofomo.com> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1AoJg2h51-99CRjK9ZuqPkrUxXajS-tmdPuiJ8aUAWJaLE…>, organized by Cofomo Québec Inc.<https://secure-web.cisco.com/1hm7G1kJlUeG0GPcqLmtCEcdAsuxppzVAGuFHM4ra04gb4…> (cross-posting to multiple lists - sorry for any duplicates) -- You received this message because you are subscribed to the Google Groups "Row Committee" group. To unsubscribe from this group and stop receiving emails from it, send an email to row-committee+unsubscribe(a)googlegroups.com<mailto:row-committee+unsubscribe@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/row-committee/DS7PR12MB57170D9D379EC12E28…<https://groups.google.com/d/msgid/row-committee/DS7PR12MB57170D9D379EC12E28…>. For more options, visit https://groups.google.com/d/optout.

1 0

Call for Presentations Hybrid TechDay ICANN 77 (Washington)
by Dr Eberhard W Lisse April 6, 2023

April 6, 2023

Call for Presentations vTechDay at ICANN 77 (Washington) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 77 meeting (Washington) As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2023-06-12 for two blocks: Blocks 1-2 13:00 UTC until 16:15 UTC, with one 30 minute break mandated by ICANN. We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the African (!) Region and with regards to SHA-1 Transition 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware, or even reports of failures 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

FW: ROW12 - Call for proposals
by Hollenbeck, Scott March 29, 2023

March 29, 2023

FYI, folks! Scott From: row-committee(a)googlegroups.com <row-committee(a)googlegroups.com> On Behalf Of nicoleta munteanu Sent: Wednesday, March 29, 2023 10:38 AM Subject: [EXTERNAL] ROW12 - Call for proposals 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. ROW12 Call for Participation is Now Open! | June 20th, 2023 | 13:00 - 16:00 UTC | Zoom Video Conference The Registration Operations Workshop<http://secure-web.cisco.com/1hANnlBmy23AJ7UjCP-LT-MHsB4you4QA9B9RtDlPVM0Vv9…> Program Committee invites you to submit your presentation and/or panel abstracts for the 12th Registration Operations Workshop (ROW12). Since 2014, the ROW series has provided a forum for all industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, and second level domain registries, to present and discuss technical topics related to real world experiences of implementing registration operations. Past workshops have included discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more (see https://regiops.net/events for further details on previous sessions). Please submit a short abstract describing your proposal to our NEW ROW email address row(a)cofomo.com<mailto:row@cofomo.com> by May 19th, 2023. The Program Committee provides below a non-exhaustive list of broad topics for ROW12 and encourages any discussions/suggestions for additional topics on ROW’s mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com>. * Registries and DNS Hosting: * RPKI from a registry operator’s perspective * Experience with Universal Acceptance deployments * CDS/CDNSKEY or CSYNC deployment experience * Accommodating third party providers (i.e., not the registrant or registrar themselves) * Registries and Internet Ecosystem: * Registry database access * Interaction with Public Safety and Law Enforcement * Regulation, Current or Coming * Implementing Full-scale security, including Routing to Nameservers * Registry Industry Coming of Age: * Handling turnover of staff or platform providers, transitioning * Evolving the role of the registry within the Internet economy/environment (meaning, gov’t/others) The Program Committee will notify selected authors by May 23rd, 2023. Presentations will be required from selected presenters by June 9th, 2023. We hope that you can join us. Registration process will be made available shortly on our website. This event is co-sponsored by Verisign<https://www.verisign.com/> and ICANN<https://secure-web.cisco.com/1Yw4bRTJB6or8IW7Yn9VUxVk6eFHBX4z9WYzOubPlWb-dG…> and organized by Cofomo<https://secure-web.cisco.com/1FnOHwGNaqj2nETXKOkaS-apbKif7PuGwwnTlgi_wctejy…>. Please feel free to disseminate this call for proposals to other lists where it might be of interest. Thank you. ROW Program Committee Stay tuned for further updates! Follow @ROWevents<https://secure-web.cisco.com/1ZwZfSXHw-wSAc4w7grMFwKcwPvLqfOK9Hehba3FkQSsI1…> ROW website: http://regiops.net<http://secure-web.cisco.com/1hANnlBmy23AJ7UjCP-LT-MHsB4you4QA9B9RtDlPVM0Vv9…> Contact us: row(a)cofomo.com<mailto:row@cofomo.com> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1Yw4bRTJB6or8IW7Yn9VUxVk6eFHBX4z9WYzOubPlWb-dG…>, organized by Cofomo<https://secure-web.cisco.com/1FnOHwGNaqj2nETXKOkaS-apbKif7PuGwwnTlgi_wctejy…> (cross-posting to multiple lists - sorry for any duplicates) -- You received this message because you are subscribed to the Google Groups "Row Committee" group. To unsubscribe from this group and stop receiving emails from it, send an email to row-committee+unsubscribe(a)googlegroups.com<mailto:row-committee+unsubscribe@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/row-committee/DS7PR12MB5717CC17D59D60D341…<https://groups.google.com/d/msgid/row-committee/DS7PR12MB5717CC17D59D60D341…>. For more options, visit https://groups.google.com/d/optout.

1 0

[CZDS] TLDs playing possum
by Viktor Dukhovni March 9, 2023

March 9, 2023

Despite long-standing complaints, no response to renewal requests: TLD Since #Delegations (last snapshot) ------------- ---------- ----- desi 2022-09-15 1170 xn--1qqw23a 2022-10-31 172 xn--30rr7y 2022-10-31 8 xn--3bst00m 2022-10-31 2861 xn--6qq986b3xl 2022-10-31 12959 xn--9et52u 2022-10-31 2 xn--xhq521b 2022-10-31 349 Is it just me, or are these broadly ignoring requests? -- Viktor.

5 8

3rd Call for Presentations Hybrid TechDay ICANN 76 (Cancun)
by Dr Eberhard W Lisse March 1, 2023

March 1, 2023

3rd Call for Presentations vTechDay at ICANN 76 (Cancún) We still have some slots... The ICANN Tech Working Group is again planning a technical workshop at the ICANN 76 meeting (Cancún) on Monday 2023-03-13 As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2023-03-13 for (up to) four blocks: Blocks 2-5 15:30 UTC until 22:30 UTC, with one 75 minute and two 30 minute breaks mandated by ICANN. We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the LACNIC Region and with regards to SHA-1 Transition 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

2nd Call for Presentations Hybrid TechDay ICANN 76 (Cancun)
by Dr Eberhard W Lisse Feb. 12, 2023

Feb. 12, 2023

2nd Call for Presentations vTechDay at ICANN 76 (Cancún) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 76 meeting (Cancún) on Monday 2023-03-13 As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2023-03-13 for (up to) four blocks: Blocks 2-5 15:30 UTC until 22:30 UTC, with one 75 minute and two 30 minute breaks mandated by ICANN. We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the LACNIC Region and with regards to SHA-1 Transition 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

Registrar 999x domains x Claims notices
by rubensk＠nic.br Feb. 3, 2023

Feb. 3, 2023

Hi there. My understanding was that registrar 999x (9999/9998) registrations do not require a claims service, even if the label is in the TMDB claims list. But I couldn't find this specify in the RPM requirements... is it right or wrong ? What was my original doubt though was about sending that such registration happened to the claims log. So assuming it does not require a notice, does it need to be recorded in the claims log ? Best, Rubens

2 1

NIS2 and impact on EPP
by InterNetX - Marco Schrieck Jan. 31, 2023

Jan. 31, 2023

Hi all, I wanted to ask if anyone has thought about the impact of NIS2 on EPP, Especially the validation of domain holder? There are many issues here regarding protocol and processes. E.g. How are certain checks of owner data represented in EPP/RDAP/Whois. Maybe we can work out some kind of best practice for the registries and registrars here. What is your opinion ? Regards Marco Schrieck Director Development Marco Schrieck Bereichsleiter Entwicklung -- InterNetX GmbH Johanna-Dachs-Str. 55 • 93055 Regensburg • Germany Tel. +49 941 59559-0 internetx.com - internetx.com/linkedin - internetx.com/twitter Geschäftsführer: Thomas Mörz (CEO), Hakan Ali, Elias Rendón Benger Amtsgericht Regensburg, HRB 7142

4 5

.gov TLD joins ICANN's CZDS system
by Eduardo Alvarez Jan. 30, 2023

Jan. 30, 2023

Hello colleagues, For those of you following CZDS, you may find it interesting that today the ICANN org added the .gov TLD to the list of zone files available for request in the CZDS system. It’s worth noting that the .gov TLD is different from the rest currently in the system, in the sense that the registry operator is not contractually required to provide access to their zone file, however they are voluntarily doing so. Best regards, Eduardo Alvarez ICANN

2 1

Call for Presentations Hybrid TechDay ICANN 76 (Cancun)
by Dr Eberhard W Lisse Jan. 13, 2023

Jan. 13, 2023

Call for Presentations vTechDay at ICANN 76 (Cancún) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 76 meeting (Cancún) on Monday 2023-03-13 As the meeting will be hybrid so will be vTechDay which is currently penciled in for Monday, 2023-03-13 for (up to) four blocks: Blocks 2-5 15:30 UTC until 22:30 UTC, with one 75 minute and two 30 minute breaks mandated by ICANN. We shall try to accommodate the time zone of virtual presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the LACNIC Region and with regards to SHA-1 Transition 2. DNS Abuse Prevention and Mitigation Tools 3. Best (security) management practices, lines of defense, to protect Registries from bad actors, attacks or malware 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email us at ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

TMCH Test-SMDs expired...
by Alexander Mayrhofer Oct. 24, 2022

Oct. 24, 2022

Hello everyone, the test SMD-Files provided by the TMCH have expired yesterday (see below). Our unit testing infrastructure obviously fails on these tests currently, because it requires/assumes the SMD files to be valid. Are there updated test files available yet? If not, when will they be provided? best, Alex SMDs from http://newgtlds.icann.org/en/about/trademark-clearinghouse/smd-active-15jul… $ grep notAfter *.smd Court-Agent-Arabic-Active.smd:notAfter: 2017-07-10 00:00:00 Court-Agent-Chinese-Active.smd:notAfter: 2017-07-10 00:00:00 Court-Agent-English-Active.smd:notAfter: 2017-07-10 00:00:00 Court-Agent-French-Active.smd:notAfter: 2017-07-10 00:00:00 Court-Agent-Russian-Active.smd:notAfter: 2017-07-10 00:00:00 Court-Holder-Arabic-Active.smd:notAfter: 2017-07-10 00:00:00 Court-Holder-Chinese-Active.smd:notAfter: 2017-07-10 00:00:00 Court-Holder-English-Active.smd:notAfter: 2017-07-10 00:00:00 Court-Holder-French-Active.smd:notAfter: 2017-07-10 00:00:00 Court-Holder-Russian-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Agent-Arabic-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Agent-Chinese-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Agent-English-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Agent-French-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Agent-Russian-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Holder-Arabic-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Holder-Chinese-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Holder-English-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Holder-French-Active.smd:notAfter: 2017-07-10 00:00:00 Trademark-Holder-Russian-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Agent-Arabic-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Agent-Chinese-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Agent-English-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Agent-French-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Agent-Russian-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Holder-Arabic-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Holder-Chinese-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Holder-English-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Holder-French-Active.smd:notAfter: 2017-07-10 00:00:00 TreatyStatute-Holder-Russian-Active.smd:notAfter: 2017-07-10 00:00:00

6 20

Beilong Zhongwang
by Joe Wein Oct. 19, 2022

Oct. 19, 2022

Has anyone else received an email in Chinese from an entity called Beilong Zhongwang in response to a recent CZDS application? I received one with a link to a Chinese language web page. According to a Google translate, they request information via e-mail over and above what I already supplied via the ICANN portal for all CZDS requests. In there they say they will take six months to process zone file requests and they will reject them unless the extra information is supplied by email. Google translate: ==== 3. Applicants need to send the following materials by email to wangzhi-czds(a)knet.cn: (1) Individual applicants need to provide materials: a. Personal identification materials b. Applicant's occupation (such as law enforcement officer, intellectual property lawyer, security researcher) and corresponding professional certificate; (2) Organization applicants need to provide materials: a. The organization needs to use the organization's domain name suffix to send emails; b. Organizational identity certification materials; c. The name and position of the authorized agent; d. The official website of the organization; e. Introduction to the main business and products of the organization; (3) Proof of the true use of the data must be provided; (4) A complete description of the measures taken by the applicant to prevent unauthorized access, use or disclosure of data to any third party; (5) The applicant is required to provide the following statement: "I, [full name of user], as the applicant, certify that the information in this application is accurate; the applicant will access and use the data only for lawful purposes and in compliance with applicable All legal and regulatory requirements of Longzhong.com; the applicant will take all reasonable steps to prevent unauthorized access, use and disclosure of the data to any third party; the applicant will not access or use the data for any marketing activities; and the applicant will not Will access or use the data to send inquiries or data in bulk to Beilong, any registrar or any registrant's system. Individual applicants need to sign under the declaration document, and organization applicants need to affix the official seal under the declaration document or be signed by a person who can sign on behalf of the organization (a document proof that the signer can sign on behalf of the organization must be attached). 3. Audit After Beilong Zhongwang receives a new data application, it will review the submitted application according to the additional information provided in the email. Beilong Zhongwang will verify all the information provided by the user, including but not limited to contacting the applicant by telephone, email or WeChat. The review process for Beilong Zhongwang generally takes six (6) months. 4. Rejection and Revocation 1. Beilong Zhongwang will reject the applicant's request, including but not limited to the following situations: (1) any request that does not meet the requirements of Article 2; (2) lack of sufficient information to properly identify and locate applicants; (3) There is a lack of credible or sufficient detail about the applicant's intended use of the data to cause Beilong.com to believe that the applicant is likely to do any of the following: a. Access or use the data for unlawful or abusive purposes, or in violation of all applicable laws and regulations; b. Access, use, or allow the data to be accessed or used to harass, annoy, interrupt, disrupt or interfere with the normal business operations of any registrant (including Beilong Zhongwang); c. access, use, or allow the data to be used for any marketing purposes; d. Access or use the data in a way that threatens the stability and security of the Internet; e. Distribute data to any third party without the express prior written consent of Beilong.com; f. The data usage scenario is inconsistent with the purpose submitted at the time of application; g. Failure to take all reasonable steps to prevent unauthorized access, use or disclosure to any third party; or h. Use data in a manner that violates this Policy or the terms of the CZDS. 2. Beilong.com may revoke the applicant 's right to use the data at any time for reasons such as non-compliance with the CZDS terms or any of the above terms , without separate notice . ==== This seems unreasonable, both the excessively long wait period and the additional requirements presumably not covered by the ICANN agreement. Joe SURBL

1 0

Purpose of this list?
by Michele Neylon - Blacknight Oct. 5, 2022

Oct. 5, 2022

All This list was originally for discussion of technologies related to gTLDs. But for the last few months it seems to have morphed into an extension of the ICANN helpdesk with a focus on zone files and pretty much nothing else. There are a bunch of technical issues that we should probably be discussing, like the sunsetting of whois, for example.. Or are people just going to continue using it to complain about CZDS issues? Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845

4 4

CZDS system routine maintenance
by Eduardo Alvarez Oct. 3, 2022

Oct. 3, 2022

Hello Colleagues, The Centralized Zone Data Service (CZDS) system will be undergoing routine maintenance on Tuesday, October 4th 2022, from 20:00 to 21:00 UTC. The CZDS portal and zone download service will remain available during the maintenance period with no impact to the system users. Please feel free to contact us at globalSupport(a)icann.org should you experience any issues. Best Regards, Eduardo Alvarez ICANN

1 0

[CZDS] Any luck with .VOTING lately?
by Viktor Dukhovni Oct. 3, 2022

Oct. 3, 2022

My renewal request is stalled since 2022-06-09. Cancelled and refiled 2022-09-05, still no luck... -- Viktor.

1 0

Call for Presentations vTechDay ICANN 71 (TheHague)
by Dr Eberhard W Lisse Sept. 17, 2022

Sept. 17, 2022

Call for Presentations 4th vTechDay at ICANN 71 (The Hague) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 71 meeting (The Hague) on Monday 2021-06-14. As the meeting will be virtual vTechDay will be conducted as Zoom Webinar/Meeting from 12:00 to 17:30 UTC. We shall try to accommodate the time zone of the presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the EUR Region and with regards to SHA-1 Transition 2. DNS Abuse Prevention and Mitigation Tools 3. Best security management practices, lines of defense, to protect the registry from bad actors, attacks or malware 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 16

Svelte CZDS zone files?
by Viktor Dukhovni Sept. 13, 2022

Sept. 13, 2022

It occurs to me that most CZDS users are interested primarily in the collection of "ordinary" records present in the gTLD zone files, and have no intention to e.g. operate secondary servers based on the complete zone data. In particular, the RRSIG and NSEC/NSEC3 records which can take up a significant (perhaps dominant) fraction of the zone file size, may be of little interest to most users. I'd like to propose that ICANN make available a version of each gTLDs zone file that elides the *derived* RRSIG, NSEC and NSEC3 records. Doing this can save significant tranmission costs on the ICANN size, and storage/processing costs on the CZDS user side. If some users want the zone files, RRSIGs and all, those can continue to be available. [ Please DO NOT elide "DS" records, these are not "derived" data, signal which delations are signed, and typically do not take up nearly as much space as RRSIGs. ] -- Viktor.

8 14

Re: [gtld-tech] ZFA access to .MTR
by Kevin Murphy Sept. 5, 2022

Sept. 5, 2022

I had the same response a few days ago. My request was submitted Sep 1 and it was denied the next day with "This gTLD is only for internal use. Thanks" This has been happening for almost a decade with various TLDs. I don't think ICANN Org cares that much unless you submit a report with Compliance. Kevin Murphy Domain Incite +44 7522 990 282 Twitter: @DomainIncite Skype: DomainIncite Facebook: facebook.com/domainincite > -------- Original Message -------- > Subject: [gtld-tech] ZFA access to .MTR > From: Adrian Wiedemann via gtld-tech <gtld-tech(a)icann.org> > Date: Fri, September 02, 2022 9:42 am > To: gtld-tech(a)icann.org > > > Did anyone get approval for the .MTR zonefile recently? Our requests for > > renweal are (repeatedly) denied with: > > > > -- > > Reason: > > > > Requester did not provide correct or legitimate credentials (explain why) > > > > Explanation: > > > > This gTLD is only for internal use. Thanks > > -- > > > > Complaint has been filed. > > > > > > Best regards, Adrian Wiedmeann > > > > -- > > BFK edv-consulting GmbH http://www.bfk.de/ > > Kriegsstrasse 100 tel: +49-721-96201-1 > > D-76133 Karlsruhe fax: +49-721-96201-99 > > Geschäftsführer: Christoph Fischer HRB105469 Mannheim<hr>_______________________________________________ > gtld-tech mailing list > gtld-tech(a)icann.org > https://mm.icann.org/mailman/listinfo/gtld-tech > > ________________________________________________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.

1 0

ZFA access to .MTR
by Adrian Wiedemann Sept. 2, 2022

Sept. 2, 2022

Did anyone get approval for the .MTR zonefile recently? Our requests for renweal are (repeatedly) denied with: -- Reason: Requester did not provide correct or legitimate credentials (explain why) Explanation: This gTLD is only for internal use. Thanks -- Complaint has been filed. Best regards, Adrian Wiedmeann -- BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstrasse 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 Geschäftsführer: Christoph Fischer HRB105469 Mannheim

2 1

ZFA access to .VOTING
by John Levine July 22, 2022

July 22, 2022

I just sent in yet another complaint that .VOTING has ignored my ZFA request. I see that from 2018 to late 2020 they were reasonably responsive, but they've been ignoing requests for almost two years now. Have they responded to anyone else? R's, John

4 4

RDE (Registrar Data Escrow) specs, verification, data handling
by Thomas Corte (COREhub support) July 7, 2022

July 7, 2022

Hello, lately we've received some new warnings in the response e-mails we're receiving from our RDE Agent (IronMountain/NCC) after making a deposit. They seem to indicate that ICANN is starting a stricter verification of the RDE CSV data than what was previously applied, to check compliance with https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf and a new document entitled "Registrar Data Escrow Guidelines" which we've received from NCC but which doesn't seem to be published anywhere online. In this context, we were wondering about some of the involved data handling that seems to be implied by the verification messages, and what other registrars on this list may be doing in this regard. In particular, 1) Do you locally store the data of non-sponsored contact objects referenced by your domains? For thick registries, it is usually perfectly legal for a domain sponsored by registrar A to use a contact sponsored by registrar B, e.g. after a transfer. Thanks to GDPR and other data protection policies, the data of such foreign contact can usually not be inquired by the non-sponsoring registrar, which makes its local storage impossible. Nevertheless, the Escrow guidelines seem to dictate that registrar A's RDE deposits should include the data of registrar B's contact, which in most cases cannot be known by registrar A. Of course, one way to solve this would be to require registrars to only use their own contacts in all of their domains, but this somewhat breaks the relation model between domains and contacts (as obviously intended by the inventors of EPP) as far as its cross-registrar application is concerned. 2) How to you handle domains which are lacking certain contact types? The contact types for which some data is expected in the RDE deposit are still the usual four: registrar, admin, tech, billing. However, some gTLDs are no longer requiring billing contacts thanks to GDPR (they never made much sense in the first place), and even admin and tech are oftentimes no longer required (e.g., CentralNic doesn't seem to enforce admin contacts anymore). If anyone from ICANN is reading this, any input would also be highly appreciated, especially regarding the new document "Registrar Data Escrow Guidelines" which seems to also introduce some new requirements regarding proxy contacts. Generally, this could be a good opportunity to standardize, streamline and modernize the RDE data format, which was so far highly underspecified. Unfortunately, the new documents that popped up recently (see above) are not helping with this issue, on the contrary: they are creating even more uncertainty instead. Best regards, Thomas Corte on behalf of COREhub -- --=== COREhub Technical Support ===------------------------------------- Thomas.Corte(a)knipp.de Thomas Corte COREhub, IANA ID 15

2 1

CZDS system updates for access extension requests
by Eduardo Alvarez July 4, 2022

July 4, 2022

Hello, Please note that a release was just completed in the Centralized Zone Data Service (CZDS) system with some new functionality. Active CZDS users and Registry Operators should be receiving the notification from ICANN directly too, however I thought I’d share here as well for anyone interested. Zone file access requesters already authorized to access a top-level domain (TLD) zone file in the CZDS system will now have the option to submit an access extension request up to 30 days prior to the expiration date of their currently approved access. To request an access extension though the CZDS portal, go to the TLD zone access request details page. If the expiration date is within 30 days or less, the option to request an extension will be displayed next to the expiration date. Click the “Request Extension” button and confirm the action in order to submit the extension request to the registry operator. Please note that an extension request still requires approval by the TLD registry operator to extend the expiration date. If the extension request is not approved prior to the access expiration date, the access request will expire normally. If you have any questions, please contact globalsupport(a)icann.org. Best, Eduardo Alvarez Global Domains and Strategy, Technical Services Internet Corporation for Assigned Names and Numbers (ICANN)

4 10

CZDS - System availability incident on 21-June-2022
by Eduardo Alvarez June 21, 2022

June 21, 2022

Dear CZDS users, Please note that earlier today the CZDS system was impacted by networking incident which caused some users to intermittently get an error message when trying to download zone files for which they have been previously been granted access. Impact to the CZDS system started on 21-June-2022 at 11:00 UTC, and was resolved at 20:00 UTC restoring the system availability. Apologies for the inconvenience. Best regards, Eduardo Alvarez ICANN

1 0

FW: [regiops] ROW11 agenda & registration
by Hollenbeck, Scott June 10, 2022

June 10, 2022

FYI – it’s not too late to register! Scott From: regiops(a)googlegroups.com <regiops(a)googlegroups.com> On Behalf Of nicoleta munteanu Sent: Friday, June 10, 2022 8:03 AM Subject: [EXTERNAL] [regiops] ROW11 agenda & registration 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. ROW11 | June 21st, 2022 | 13:00 - 16:00 UTC | Zoom Video Conference ROW11 will take place via Zoom Webinar platform on June 21st, 2022, 13:00 - 16:00 UTC. Additional time zones may be checked here<https://secure-web.cisco.com/1lVOdhaY1uY2xFpxrxTIvzZgOIVyZEd4zMB3qUHNp3z8Ai…>. Those interested in attending are required to register<https://regiops.net/events/virtual-11th-registration-operations-workshop-ro…> in order to receive the webinar access information (meeting ID and password). For details regarding the agenda, check out Marc Blanchet’s recent blog post<https://secure-web.cisco.com/1Q6B8hTtMXsnldhbc6-I55mSVk8Rn4suPgzu5FQWA_JPXN…> and our website<https://regiops.net>. If you have any questions, please contact us at row(a)viagenie.ca<mailto:row@viagenie.ca>. We would like to thank our ROW Series Sponsors ICANN<https://secure-web.cisco.com/1qda5JaSjgud7PtUA2IYIMBJw8_Pol5cNa9zFOfLuviEo7…> and Verisign<https://www.verisign.com/> for their continued support. ----- Here are some special tips if this is your first time using Zoom or you wish to get more familiar with its web conferencing capabilities: * Download the Zoom application to your computer or mobile phone. You can do it at https://zoom.us/download<https://secure-web.cisco.com/1qR0Y60i0-j-s09Ds_EJgO6Tw4xHWUP5IdgyAlWdTb3rlL…>. You will also be prompted to download and install Zoom when you click the link to join. You can also run Zoom from your web browser by navigating to join.zoom.us<http://secure-web.cisco.com/1oGBhsvolQUcO5p7rrfWG6qRloQwnHY8QfMQ3vEwJaEQkRN…> and entering the meeting number and passcode. * Want to try it out before June 21st? Join a test meeting at https://zoom.us/test<https://secure-web.cisco.com/11BJVzxY8VTSYpR6pBp_HwoLgSeYf6qp_lc2VIPz57ysfr…> anytime to familiarize yourself with Zoom. You can also access Zoom tutorials here: https://support.zoom.us/hc/en-us/articles/201362193-How-Do-I-Join-A-Meeting-<https://secure-web.cisco.com/1wSR_YMHxDJmyoDQp-8d9VHSOURRmpBrQO2WEtSlAQ-rBd…> * As an attendee, you will be muted. For questions and comments, please use the Q&A feature. The session moderator will address them to the speakers on the mike as time permits. Questions that cannot be answered due to time constraints, will be answered directly in the Q&A window or by email. * You do not have to use the Zoom web conferencing platform with video to participate. There is an option to call-in only. * We will be recording this webinar, including the chat, and making it available on our website 48h after the session. ----- We look forward to seeing you online! ROW Program Committee Stay tuned for further updates! Follow @ROWevents<https://secure-web.cisco.com/16UUlMbfCb9B0uembjfsV2ywqDSnIXgMVXSJ2Kif-VIhAy…> ROW website: https://regiops.net<https://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1qda5JaSjgud7PtUA2IYIMBJw8_Pol5cNa9zFOfLuviEo7…>, organized by Cofomo Québec Inc.<https://secure-web.cisco.com/1sCFFvvVk5SJCoD9JxEMmHba-H8Dokj_s9o3c84sHgdDe5…> (cross-posting to multiple lists - sorry for any duplicates)

1 0

Unsubscribing
by Ulrich Wisser June 2, 2022

June 2, 2022

Hi! Yes, I have found the link to mailman in the headers, but I still thought it to be a good idea to report this to ther "authorities". Whoever is running this list, please read the footer that is send with every message. For me it looks something like > 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. It might be just me, but I can't find the mailman link above. The link is in the headers https://mm.icann.org/mailman/options/gtld-tech, but certainly not in the text of the message. And this is not the only ICANN mailinglist with this footer! Kind regards /Ulrich

2 1

Fwd: Zone File Access for .citadel Denied
by Luis E. Muñoz May 27, 2022

May 27, 2022

Just received this form our friends at .citadel. Forwarded message: > From: no-reply(a)icann.org > To: czds(a)libertad.link > Subject: Zone File Access for .citadel Denied > Date: Wed, 25 May 2022 19:31:57 +0000 (UTC) > > Thank you for using CZDS. Your zone data access request for .citadel has been denied. The following reason was given by the Registry: > > Reason: > > Registry Operator reasonably believes the user will violate the terms of Section 2.1.5. of Specification 4 of the registry agreement (explain why and reference supporting evidence) > > Explanation: > > No business reason for needing this information > > To view your request, please login to https://czds.icann.org/. > > Thank you, > ICANN I don't think this is a valid reason to reject a request. What do you guys think? What would be my options? Best regards -lem

3 2

gtld-tech list misconfiguration
by John R Levine May 26, 2022

May 26, 2022

I see that the list-Id header looks like this: List-Id: "List to discuss technical issues related to gTLD registries and registrars." <gtld-tech.icann.org> The spec says you can't line fold a quoted string, and it's confusing my mail sorting scripts. Simple fix: take out the comment which nobody will see anyway. Tnx. Regards, John Levine, johnl(a)taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly

1 0

Re: [gtld-tech] CZDS Support for Request Cancellation
by Viktor Dukhovni May 26, 2022

May 26, 2022

On Wed, Apr 27, 2022 at 10:12:46PM +0000, ICANN Global Support wrote: > Today we have released new functionality in the Centralized Zone Data > Service (CZDS) system that allows zone file access requesters to > cancel a previously submitted access request that is still in pending > status. Thanks! This is very much appreciated. > Canceled access requests will no longer require any action from the > requester or the registry operator and will have no effect on future > access requests. > > If you have any questions, please contact globalsupport(a)icann.org. I think my question has a broader audience, so I am asking it here instead: What effect does cancelling a long neglected "pending" request have on outstanding complaints? Are they also automatically closed? The reason I ask, is that after closing long neglected requests I am opening fresh requests in the hope that they might get approved this time around. If they don't get processed in a fairly generous time frame (say 4 weeks), I'd like to file a fresh complaint, and would like it to not register as a duplicate... [ I've cancelled and reopened ZFA requests for "citadel" and "xn--kput3i", it'll be interesting to see whether this helps to unwedge the process. ] -- Viktor.

4 10

FW: ROW11 - Final call for proposals
by Hollenbeck, Scott May 11, 2022

May 11, 2022

FYI, folks – last call Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com<mailto:munteanu.nicoleta@outlook.com>> Subject: [regiops] ROW11 - Final call for proposals Date: May 10, 2022 at 10:35:49 PM GMT+2 To: Undisclosed recipients:; ROW11 | June 21st, 2022 | 13:00 - 17:00 UTC | Zoom Video Conference ROW11<https://regiops.net/> is scheduled to take place via remote participation on June 21st, 2022, 13:00 - 17:00 UTC. See additional time zones here<https://secure-web.cisco.com/1wlAaXgneBnzdyq3RS2duYmkHMi4JJ26V1oSc_vh3O5Egp…>. IMPORTANT: Registration is required to enable participation! Those interested in attending the virtual meeting are required to register at the following link in order to receive the access information for the online session: https://regiops.net/events/virtual-11th-registration-operations-workshop-ro… Please note that the call for presentation and panel proposals is still active. Proposals in the form of a short abstract shall be submitted to row(a)viagenie.ca<mailto:row@viagenie.ca>. Deadline is May 27th, 2022. We shall try to accommodate presenters’ time zones in setting the agenda. In keeping with the Registration Operations' focus of the ROW, below is a non-exhaustive list of possible topics for this session. Discussions of workshop topics may also take place on the regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> mailing list. * RDAP implementation experience * DNS abuse * DNS privacy and encryption * Differentiated access * Authentication and authorization * Credential Security/Credential Management * DNSSEC operalization (CSYNC, managing transfers of secured domains) * Registration support functions (data escrow/business continuity) * Automation * Other innovative uses for registration and resolution technologies ROW11 important dates: * Deadline to submit proposals: May 27th, 2022 * Program Committee to notify selected authors by May 31st, 2022 * Speaker agreements and materials required from selected presenters by June 10th, 2022 We look forward to your participation! Please feel free to disseminate this Call to other lists where it might be of interest. Thank you. ROW Program Committee Stay tuned for further updates! Follow @ROWevents<https://secure-web.cisco.com/1mxQ-YTKsecpSJvnESNzgDuZyo4AJzl18QcZPsdLtr-TSr…> ROW website: https://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/13S2eftgFHLJothtVBOkr3pQ_tHQtK8P2iBdoC-foH9Qvs…>, organized by Cofomo Québec Inc.<https://secure-web.cisco.com/11Gnghs04UbZSMA-lT-9cosyYYAYwL6bPrjAv4nAkC8Hy9…> (cross-posting to multiple lists - sorry for any duplicates)

1 0

Re: [gtld-tech] CZDS availability issues
by Eduardo Alvarez April 25, 2022

April 25, 2022

The issues impacting the CZDS system availability have been resolved. If you continue to experience these problems please let us know. Apologies for the inconvenience. Regards. --Eduardo A. From: gtld-tech <gtld-tech-bounces(a)icann.org> on behalf of Eduardo Alvarez via gtld-tech <gtld-tech(a)icann.org> Reply-To: Eduardo Alvarez <eduardo.alvarez(a)icann.org> Date: Monday, April 25, 2022 at 10:57 AM To: "gtld-tech(a)icann.org" <gtld-tech(a)icann.org> Subject: [gtld-tech] CZDS availability issues Dear CZDS users, Our team has become aware of an increased number of availability issues impacting the CZDS system over the past few days, and we are working to address these issues. We will keep you informed once the problem is resolved. Best regards, Eduardo Alvarez ICANN

1 0

CZDS increasingly broken
by John R Levine April 25, 2022

April 25, 2022

My daily script completely failed with a proxy error when it tried to fetch the list of available files Regards, John Levine, johnl(a)taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly ---------- Forwarded message ---------- 16:00:49 EDT === download par 3 === Traceback (most recent call last): File "download3.py", line 463, in <module> timestamp=args.ts, nosess=args.ns, retries=args.retries) File "download3.py", line 361, in getzones zlist = self.getzonelist() File "download3.py", line 150, in getzonelist zoner.raise_for_status() # throw HTTP error File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 943, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 502 Server Error: Proxy Error for url: https://czds-api.icann.org/czds/downloads/links

3 3

CZDS availability issues
by Eduardo Alvarez April 25, 2022

April 25, 2022

Dear CZDS users, Our team has become aware of an increased number if availability issues impacting the CZDS system over the past few days, and we are working to address these issues. We will keep you informed once the problem is resolved. Best regards, Eduardo Alvarez ICANN

1 0

CZDS timeouts / 503 issues?
by John McCormac April 24, 2022

April 24, 2022

Is anyone else seeing an increasing number of timeouts waiting for responses, timesouts waiting for authentication, 503s on the CZDS while downloading? It has been happening for a while now with some days having no issues but others, such as today, having a lot. Have also noticed a bit of sluggishness in the CZDS while updating or checking requests (this was via a different connection). Regards...jmcc -- ********************************************************** John McCormac * e-mail: jmcc(a)hosterstats.com MC2 * web: http://www.hosterstats.com/ 22 Viewmount * Domain Registrations Statistics Waterford * Domnomics - the business of domain names Ireland * https://amzn.to/2OPtEIO IE * Skype: hosterstats.com ********************************************************** -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 4

ROW11 Call for Proposals and Registration
by Hollenbeck, Scott April 14, 2022

April 14, 2022

FYI, folks! Scott --------------- ROW11 Call for Proposals and Registration June 21st, 2022 | 13:00 - 17:00 UTC | Zoom Video Conference ROW11 will be held via remote participation on June 21st, 2022, 13:00 - 17:00 UTC. See additional time zones here. Registration is NOW available at: https://regiops.net/events/virtual-11th-registration-operations-workshop-ro… ROW's Program Committee has also opened the call for presentation and panel proposals and is interested in: 1. Topic related presentation proposals. 2. Topic suggestions for focused panel discussions. 3. Suggestions for additional topics. In the past, workshops have included discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more (see ROW Archives for further details on previous sessions). Below is a non-exhaustive list of possible topics for this session. * RDAP implementation experience * DNS abuse * DNS privacy and encryption * Differentiated access * Authentication and authorization * Credential Security/Credential Management * DNSSEC operation (CSYNC, managing transfers of secured domains) * Registration support functions (data escrow/business continuity) * Automation * Other innovative uses for registration and resolution technologies Please email a short abstract describing your proposal to row(a)viagenie.ca We also encourage discussions/suggestions for additional topics on ROW's mailing list regiops(a)googlegroups.com. Important dates: * Deadline to submit proposals: May 27th, 2022 * Program Committee to notify selected authors by May 31st, 2022 * Speaker agreements and materials required from selected presenters by June 10th, 2022 We hope that you can join us. Register now and feel free to disseminate this Call to other lists where it might be of interest. Thank you. ROW Program Committee Stay tuned for further updates! Follow @ROWevents ROW website: https://regiops.net Contact us: row(a)viagenie.ca ROW mailing list: regiops(a)googlegroups.com ROW series: co-sponsored by Verisign & ICANN, organized by Cofomo Québec Inc. (cross-posting to multiple lists - sorry for any duplicates)

1 0

Re: [gtld-tech] ZFA complaints in hibernation?
by Viktor Dukhovni April 5, 2022

April 5, 2022

> On 31 Mar 2022, at 2:05 pm, Paul Karkas <pkarkas(a)tucows.com> wrote: > >> On Thu, Mar 31, 2022 at 1:59 PM Viktor Dukhovni via gtld-tech <gtld-tech(a)icann.org> wrote: >> >> Lately I'm seeing no action on ZFA complaints, not even notices that a >> complaint is a duplicate. It looks like nobody is looking at them at >> all... > > Hi - can you elaborate? Sure, I've twice filed CZDS ZFA complaints for: gTLD Expired on xn--1qqw23a 2022-02-02 xn--30rr7y 2022-02-02 xn--3bst00m 2022-02-02 xn--6qq986b3xl 2022-02-02 xn--9et52u 2022-02-02 xn--xhq521b 2022-02-02 with nothing by the initial salesforce email to show for it. No resolution from the TLD operator and no followup action from ICANN, not even to report that the second complaint is a duplicate. It looks like whoever is handling the complaints is a long-term leave or overwhelmed... -- Viktor.

3 4

ZFA complaints in hibernation?
by Viktor Dukhovni March 31, 2022

March 31, 2022

Lately I'm seeing no action on ZFA complaints, not even notices that a complaint is a duplicate. It looks like nobody is looking at them at all... What's up? -- Viktor.

1 0

FW: ROW11 - Call for proposals
by Hollenbeck, Scott March 17, 2022

March 17, 2022

FYI, folks. Scott From: regiops(a)googlegroups.com <regiops(a)googlegroups.com> On Behalf Of nicoleta munteanu Sent: Wednesday, March 16, 2022 5:38 PM Subject: [EXTERNAL] [regiops] ROW11 - Call for proposals 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. ROW11 Call for Participation Is Now Open! June 21st, 2022 | 13:00 - 17:00 UTC | Zoom Video Conference The Registration Operations Workshop<http://regiops.net/> Program Committee invites you to submit your presentation and/or panel abstracts for the 11th Registration Operations Workshop (ROW11). ROW11 virtual session will be held via Zoom platform on June 21st, 2022, 13:00 - 17:00 UTC. The ROW series provides since 2014, a forum for all industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, and second level domain registries, to present and discuss technical topics related to real world experiences of implementing registration operations. Past workshops have included discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more (see https://regiops.net/row-main/archives/ for further details on previous sessions). Please submit a short abstract describing your proposal to row(a)viagenie.ca<mailto:row@viagenie.ca>, by May 27th, 2022. The Program Committee provides below a non-exhaustive list of possible topics for ROW11 and encourages any discussions/suggestions for additional topics on ROW’s mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> * RDAP implementation experience * DNS abuse * DNS privacy and encryption * Differentiated access * Authentication and authorization * Credential Security/Credential Management * DNSSEC operalization (CSYNC, managing transfers of secured domains) * Registration support functions (data escrow/business continuity) * Automation * Other innovative uses for registration and resolution technologies The Program Committee will notify selected authors by May 31st, 2022. Presentations will be required from selected presenters by June 10th, 2022. We hope that you can join us. Registration process will be made available beginning of April on the ROW website: http://regiops.net<http://regiops.net/>. This event is co-sponsored by Verisign<https://www.verisign.com/> and ICANN<https://secure-web.cisco.com/10XXVeYZCpO6mQkQZbciKbvBtIvt3bRP7e0-A8MSFjSg68…> and organized by Cofomo<https://secure-web.cisco.com/1gDhCKeGHkoEGafpufTXHOquoWGcIoapg-BOEBuwfPcxEO…>. Please feel free to disseminate this call for proposals to other lists where it might be of interest. Thank you. ROW Program Committee Stay tuned for further updates! Follow @DNSregiops<https://twitter.com/DNSregiops> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/10XXVeYZCpO6mQkQZbciKbvBtIvt3bRP7e0-A8MSFjSg68…>, organized by Cofomo<https://secure-web.cisco.com/1gDhCKeGHkoEGafpufTXHOquoWGcIoapg-BOEBuwfPcxEO…> (cross-posting to multiple lists - sorry for any duplicates) -- You received this message because you are subscribed to the Google Groups "Regiops" group. To unsubscribe from this group and stop receiving emails from it, send an email to regiops+unsubscribe(a)googlegroups.com<mailto:regiops+unsubscribe@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/regiops/BYAPR12MB3608CAABE5228688789BB022…<https://groups.google.com/d/msgid/regiops/BYAPR12MB3608CAABE5228688789BB022…>.

1 0

gzipped error messages served as zone files
by Joe Wein Feb. 7, 2022

Feb. 7, 2022

Some recent CZDS zone file downloads were missing all zone data. Specifically, the gzipped files were not empty, but their content was error messages, not zone file data. For example: $ gunzip < bayern.zone.gz ;; Couldn't verify signature: expected a TSIG or SIG(0) ; Transfer failed. ;; Couldn't verify signature: expected a TSIG or SIG(0) $ gunzip < jot.zone.gz ;; Couldn't create key icann-axfr: bad base64 encoding ; Transfer failed. ;; Couldn't create key icann-axfr: bad base64 encoding "Transfer failed" should be a dead giveaway that something went wrong. Can we please improve error handling on the portal side so that output of a "dig axfr" to make a snapshot for distribution is only ever packaged up as a .gz file for download by CZDS users if it at least has a valid SOA record in its first few lines? Regards Joe Wein SURBL

4 7

New RDAP conformance tool is now available
by Eduardo Alvarez Feb. 3, 2022

Feb. 3, 2022

Dear colleagues, This week, ICANN organization has published an RDAP conformance tool. The RDAP conformance tool is a stand-alone, open source tool that can be used to verify if an RDAP server implementation is conformant with the specifications developed by the IETF and optionally, the gTLD RDAP profile. For more information about the RDAP conformance tool you may visit this recent publication at https://www.icann.org/en/blogs/details/icann-launches-new-tool-to-verify-co… The RDAP conformance tool and source code is available at https://github.com/icann/rdap-conformance-tool/ If you have any questions please contact ICANN Global Support as described in https://www.icann.org/resources/pages/customer-support-2015-06-22-en . Best regards, Eduardo Alvarez Technical Services Director ICANN

1 0

CZDS renewal limbo for xn--kput3i since 2021-08-25
by Viktor Dukhovni Feb. 2, 2022

Feb. 2, 2022

My renewal request for access to xn--kput3i zone data has been unanswered (neither approved nor denied) since 2021-08-25. A complaint was filed a couple of weeks later, to no effect. Anyone else in the same boat? What can be done to get this moving forward? (I've long given up on getting initial approval for .discover and .citadel, requested soon three years ago on 2019-01-29). -- Viktor.

5 7

[ICANN CZDS] Issue with gTLD zone downloads via CZDS on 2022-01-11
by Eduardo Alvarez Jan. 11, 2022

Jan. 11, 2022

Dear CZDS users, We have identified that the access to some of the gTLD zone files was impacted today 2022-01-11, in which approved users downloading the zone would get the uncompressed zone file instead of the gzip-compressed file. This issue has now been addressed and the system is providing the compressed files once again. If you have any questions, please let us know Regards, Eduardo Alvarez ICANN

1 0

FW: [regiops] ROW#10 event reminder - June 8, 2021
by Hollenbeck, Scott June 7, 2021

June 7, 2021

Last chance to register, folks – the workshop is happening tomorrow. Scotty From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Monday, June 7, 2021 3:18 PM To: Hollenbeck, Scott <shollenbeck(a)verisign.com> Subject: [EXTERNAL] Fwd: [regiops] ROW#10 event reminder - June 8, 2021 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. Begin forwarded message: From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com<mailto:munteanu.nicoleta@outlook.com>> Subject: [regiops] ROW#10 event reminder - June 8, 2021 Date: June 7, 2021 at 3:49:44 PM GMT+2 To: Undisclosed recipients:; 10th Registration Operations Workshop (ROW#10) | June 8th, 2021 | 13:00 - 17:00 UTC ROW#10 session is starting soon!!! Tuesday, June 8th, 2021, 13:00 – 17:00 UTC. Additional time zones may be checked here<https://secure-web.cisco.com/1zvJAvHvGeXSqqhQr6EiPgw-7Mhe1nFFIHuEwRjf9cXtG7…>. The event will take place online, via Zoom Webinar platform. Those interested in attending are required to register<https://secure-web.cisco.com/1mo6rKawFfejEsETn3Xk3xmC4sLrhfvvpXjdej933EDJQJ…> in order to receive the access information (meeting ID and password). --- ROW#10 agenda * Steve Crocker [Edgemoor Research Institute] – Project Jake: Precise Specification of Collection and Access Rules for Registration Data * Quoc Pham [GoDaddy Registry] – Domain Unrenew * Ulrich Wisser [The Swedish Internet Foundation] – Automated Registry Lock * Mario Loffredo [IIT-CNR/Registro.it<http://registro.it/>] – jscontact-tools * Carlos Ganan [ICANN] – A Primer in Registration Data Access Protocol (RDAP) Performance * Mario Loffredo, Francesco Donini, Maurizio Martinelli [IIT-CNR/Registro.it<http://registro.it/>] – Integrating .it RDAP Server with OpenID Connect through Keycloak: experiences and expectations * Jaromir Talir [CZ.NIC] – RegeID: Bringing electronic identity into domain industry * Michael Palage & Frank Cona [InfoNetworks] – Minimizing A Registry’s Operational and Legal Risk to GDPR & NIS 2.0; .MUSIC’s Approach * Werner Staub [CORE Association] – Using the Registrant Email Address Field to connect Identity Services to Domain Names * Jothan Frakes [CEO Private Label Registrar and lead Volunteer on Mozilla PSL] – Public Suffix List(s) – Voluntary “Rainbow Bridge” between Domains and Developers/Apps --- Session presentations are now available at: https://regiops.net/row-main/agenda/<http://secure-web.cisco.com/1QGXKF_Wu2GhjDrycOHt72VjA9VEwl5LVTe7x9czBuGg-2s…> We would like to thank our ROW Series Sponsors ICANN<https://secure-web.cisco.com/13eN1RovN9W1GLYUBVRZAss98OgM62_M3cZBWRmfCzBK5o…> and Verisign<https://www.verisign.com/> for allowing ROW#10 to happen. We look forward to seeing you online! ROW Program Committee Stay tuned for further updates! Follow @ROW_by_Viagenie<https://secure-web.cisco.com/1ALFzmwhVEwfvZ9uSLkxWIStereHPe1BEU4CwHDjdUfQsa…> ROW website: https://regiops.net<https://secure-web.cisco.com/1MTjG7PYeiY6kOcwviQzrYtrA-OeLKGRQQgaurEO97nVGG…> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/13eN1RovN9W1GLYUBVRZAss98OgM62_M3cZBWRmfCzBK5o…>, organized by Viagenie<https://viagenie.ca/> (cross-posting to multiple lists - sorry for any duplicates) -- You received this message because you are subscribed to the Google Groups "Regiops" group. To unsubscribe from this group and stop receiving emails from it, send an email to regiops+unsubscribe(a)googlegroups.com<mailto:regiops+unsubscribe@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/regiops/BYAPR12MB3160428AE50598B175917B34…<https://groups.google.com/d/msgid/regiops/BYAPR12MB3160428AE50598B175917B34…>.

1 0

FW: ROW#10 - Final call for proposals
by Hollenbeck, Scott May 5, 2021

May 5, 2021

Last call, folks! Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Friday, April 30, 2021 7:57 AM Subject: [EXTERNAL] ROW#10 - Final call for proposals ROW#10: Register now & submit your proposal before May 14th, 2021 The 10th Registration Operations Workshop<https://regiops.net/> (ROW#10) is scheduled to take place via remote participation on June 8th, 2021, 13:00 - 16:00 UTC. For additional time zone information, click here<https://secure-web.cisco.com/1X5hy76r62Nyeow3U6MPzgIKxtZOSpDeHN0G4R6Pe_Iodo…>. IMPORTANT: Registration is required to enable participation! Those interested in attending the virtual meeting are required to register at the following link in order to receive the access information for the online session: https://regiops.net/events/row10registration/ Please note that the call for presentation and panel proposals is still active. Proposals in the form of a short abstract shall be submitted to row(a)viagenie.ca<mailto:row@viagenie.ca>. Deadline is May 14th, 2021. Discussions of workshop topics may also take place on the regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> mailing list. In keeping with the Registration Operations' focus of the ROW, possible topics for this session could be: • RDAP implementation experience • DNS abuse • DNS privacy and encryption • Differentiated access • Authentication and authorization • Credential Security/Credential Management • DNSSEC operationalization (CSYNC, managing transfers of secured domains) • Registration support functions (data escrow/business continuity) • Automation • Other innovative uses for registration and resolution technologies Please feel free to disseminate this Call to other lists where it might be of interest. We look forward to your participation! For additional event details and previous ROW sessions, please visit http://regiops.net. ROW Program Committee Stay tuned for further updates! Follow @ROW_by_Viagenie<https://secure-web.cisco.com/135Q8NmU4j_bQT_NLV4mPJiLBZcIElz1cCkg8ZVgyGWsV_…> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1f5pirvRFCla60FKq7ZdoaxuGw6KRxaoN_THe3z7smAhZ_…>, organized by Viagenie<http://secure-web.cisco.com/1XhmBdHash8E78Bbt5NjrBlmpXBujXcqagCJFIOLx4_1Y49…>

1 0

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN71 Virtual Community Forum
by Jacques Latour May 5, 2021

May 5, 2021

Hi all! The DNSSEC Deployment Initiative and the Internet Society, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC and Security Workshop for the ICANN71 Virtual Policy Forum being held from 14-17 June 2021. This workshop date will be determined once ICANN creates a block schedule for us to follow; then we will be able to request a day and time. The DNSSEC and Security Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN70 Virtual Meeting on 24 March 2021. The presentations and transcripts are available at: https://tinyurl.com/57y5jzbz, https://tinyurl.com/u56v6kk7, and https://tinyurl.com/x29ets46. The DNSSEC Workshop Program Committee is developing a program. Proposals will be considered for the following topic areas and included if space permits. In addition, we welcome suggestions for additional topics either for inclusion in the ICANN71 workshop, or for consideration for future workshops. 1. Global DNSSEC Activities Panel For this panel, we are seeking participation from those who have been involved in DNSSEC deployment as well as from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment, including Root Key Signing Key (KSK) Rollover activities and plans. 2. DNSSEC Best Practice Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? Do you still submit/accept DS records with Digest Type 1? What is the best practice around key roll-overs? What about Algorithm roll-overs? Do you use and support DNSKEY Algorithms 13-16? How often do you review your disaster recovery procedures? Is there operational familiarity within your customer support teams? What operational statistics have we gathered about DNSSEC? Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? Activities and issues related to DNSSEC in the DNS Root Zone are also desired. 3. DNSSEC Deployment Challenges The program committee is seeking input from those that are interested in implementation of DNSSEC but have general or particular concerns with DNSSEC. In particular, we are seeking input from individuals that would be willing to participate in a panel that would discuss questions of the following nature: - Are there any policies directly or indirectly impeding your DNSSEC deployment? (RRR model, CDS/CDNSKEY automation) - What are your most significant concerns with DNSSEC, e.g., complexity, training, implementation, operation or something else? - What do you expect DNSSEC to do for you and what doesn't it do? - What do you see as the most important trade-offs with respect to doing or not doing DNSSEC? 4. Security Panel The program committee is looking for presentations on DNS and Routing topics that could impact the security and/or stability of the internet. . - DoH and DoT implementation issues, challenges and opportunities - RPKI adoption and implementation issues, challenges and opportunities - BGP/routing/hijack issues, challenges and opportunities - MANRS implementation challenges and opportunities - Emerging threats that could impact (real or perceived) the security and/or stability of the internet - Domain hacking/hijacking prevention, best practice and techniques - Browser related security implementations - DMARC Challenges, opportunities and Best Practices - BGP Flowspec challenges, opportunities and Best Practices If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-thehague(a)isoc.org<mailto:dnssec-thehague@isoc.org> by Friday, 14 May 2021 Thank you, Kathy and Andrew On behalf of the DNSSEC Workshop Program Committee: Mark Elkins, DNS/ZACR Jacques Latour, .CA Russ Mundy, Parsons Ondrej Filip, CZ.NIC Yoshiro Yoneya, JPRS Fred Baker, ISC Dan York, Internet Society CLASSIFICATION:CONFIDENTIAL

1 0

FW: ROW#10 - Call for proposals & registration
by Hollenbeck, Scott April 15, 2021

April 15, 2021

FYI, folks! Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Thursday, April 15, 2021 12:12 PM Subject: [EXTERNAL] ROW#10 - Call for proposals & registration 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. ROW#10: Register now & submit your proposal June 8th, 2021 | 13:00 - 16:00 UTC | Zoom Video Conference ROW#10<https://regiops.net> will be held via remote participation on June 8th, 2021, 13:00 - 16:00 UTC. Check additional time zones here<https://secure-web.cisco.com/1LdTXjICyUimrWgaShL5Q5eW0S5ezIqEddqmg6lpGK3bkq…>. Registration is NOW available at: https://regiops.net/events/row10registration/ ROW's Program Committee has also opened the call for presentation and panel proposals and is interested in: 1. Topic related presentation proposals. 2. Topic suggestions for focused panel discussions. 3. Suggestions for additional topics. In the past, workshops have included discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more. Below is a non-exhaustive list of possible topics for this session. • RDAP implementation experience • DNS abuse • DNS privacy and encryption • Differentiated access • Authentication and authorization • Credential Security/Credential Management • DNSSEC operationalization (CSYNC, managing transfers of secured domains) • Registration support functions (data escrow/business continuity) • Automation • Other innovative uses for registration and resolution technologies Please email a short abstract describing your proposal to row(a)viagenie.ca<mailto:row@viagenie.ca> . We also encourage discussions/suggestions for additional topics on ROW’s mailing list regiops(a)googlegroups.com<mailto:regiops@googlegroups.com>. Important dates: • Deadline to submit proposals: May 14th, 2021 • Program Committee to notify selected authors by May 21st, 2021 • Speaker agreements and materials required from selected presenters by May 31st, 2021 We hope that you can join us and request that you disseminate this Call to other lists where it might be of interest. ROW Program Committee Stay tuned for further updates! Follow @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie?ref_src=twsrc%5Etfw> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1j2xbUbG3jhtzBic28ilLZOfROIeuUd03lxro89jONmwJI…>, organized by Viagenie<http://secure-web.cisco.com/1DTFZAlabi0m_COmGQGQ-__5rod8YgKBsOFlQ9_MBql5M6a…> (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: June 8th, 2021 - ROW#10 - Call for proposals & participation
by Hollenbeck, Scott March 18, 2021

March 18, 2021

FYI, folks! Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Thursday, March 18, 2021 12:03 PM Subject: [EXTERNAL] June 8th, 2021 - ROW#10 - Call for proposals & participation 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. ROW#10 Call for Participation Is Now Open! June 8th, 2021 | 13:00 - 16:00 UTC | Zoom Video Conference The Registration Operations Workshop<http://regiops.net/> Program Committee invites you to save the date and submit your presentation and/or panel abstracts for the 10th Registration Operations Workshop (ROW#10). ROW#10 will be held via remote participation on June 8th, 2021, 13:00 - 16:00 UTC. As we continue to navigate our way through COVID-19 protocols, the Program Committee has decided to pursue the ROW#10 virtual session alternative for 2021. The ROW series provides since 2014 a forum for all industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, and second level domain registries, to present and discuss technical topics related to real world experiences of implementing registration operations. In the past, workshops have included discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more. Below is a non-exhaustive list of possible topics for this session. Please submit a short abstract describing your proposal to row(a)viagenie.ca<mailto:row@viagenie.ca>, by May 14th, 2021. We also encourage discussions/suggestions for additional topics on ROW’s mailing list regiops(a)googlegroups.com<mailto:regiops@googlegroups.com>. • RDAP implementation experience • DNS abuse • DNS privacy and encryption • Differentiated access • Authentication and authorization • Credential Security/Credential Management • DNSSEC operalization (CSYNC, managing transfers of secured domains) • Registration support functions (data escrow/business continuity) • Automation • Other innovative uses for registration and resolution technologies The Program Committee will notify selected authors by May 21st, 2021. Speaker agreements and materials such as bios and final presentations will be required from selected presenters by May 31st, 2021. We hope that you can join us. Registration process will be made available shortly on our website. For additional event details and previous ROW sessions, visit http://regiops.net. This event is co-sponsored by Verisign<https://www.verisign.com/> and ICANN<https://secure-web.cisco.com/1iI-jd3ibbSXvhxCvj_G42_otaaMhzkPaybFCwRFQtZ7gY…> and organized by Viagenie<http://viagenie.ca/>. Please feel free to disseminate this call for participation to other lists where it might be of interest. Thank you ROW Program Committee Stay tuned for further updates! Follow @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie?ref_src=twsrc%5Etfw> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1iI-jd3ibbSXvhxCvj_G42_otaaMhzkPaybFCwRFQtZ7gY…>, organized by Viagenie<http://viagenie.ca/> (cross-posting to multiple lists - sorry for any duplicates)

1 0

Call for Presentations vTechDay ICANN 70 (Cancún)
by Dr Eberhard W Lisse March 18, 2021

March 18, 2021

Call for Presentations 3rd vTechDay at ICANN 70 (Cancún) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 70 meeting (Cancún) on Monday 2021-03-22. As the meeting will be virtual vTechDay will be conducted as Zoom Webinar from 14:00 to 21:00 UTC. We shall try to accommodate the time zone of the presenters in setting the agenda. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the LACNIC Region and with regards to SHA-1 Transition 2. RDAP implementations 3. Best security management practices, lines of defense, to protect the registry from bad actors, attacks or malware 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 3

vTechDay ICANN 69 (Hamburg)
by Dr Eberhard W Lisse Oct. 18, 2020

Oct. 18, 2020

All, please not that we are going to be using two different URLS, look for "Supported sepaerately" in the first part in the second part is is listed directly. el

1 0

Hopefully final agenda for vTechDay ICANN 69 (Hamburg)
by Dr Eberhard W Lisse Oct. 13, 2020

Oct. 13, 2020

Please find enclosed, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

1 0

Second Call for Presentations vTechDay ICANN 69 (Hamburg)
by Dr Eberhard W Lisse Sept. 29, 2020

Sept. 29, 2020

Call for Presentations 2nd vTechDay at ICANN 69 (Hamburg) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 69 meeting (Hamburg) on Monday 2020-10-19. As the meeting will be virtual vTechDay will be conducted as Zoom Webinar. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the European Region and with regards to SHA-1 Transition 2. RDAP implementations 3. Best security management practices, lines of defence, to protect the registry from bad actors, attacks or malware 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply

2 6

Proposed: Call for Presentations vTechDay ICANN 69 (Hamburg)
by Dr Eberhard W Lisse Aug. 26, 2020

Aug. 26, 2020

And now witht he correct Subject line (copy/paste got the better of me) Call for Presentations 2nd vTechDay at ICANN 69 (Hamburg) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 69 meeting (Hamburg) on Monday 2020-10-19. As the meeting will be virtual vTechDay will be conducted as Zoom Webinar. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the European Region and with regards to SHA-1 Transition 2. RDAP implementations 3. Best security management practices, lines of defence, to protect the registry from bad actors, attacks or malware 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el

1 0

[CCNSO-TechDay] Proposed: Call for Presentations vTechDay ICANN 68 (Kuala Lumpur)
by Dr Eberhard W Lisse Aug. 26, 2020

Aug. 26, 2020

Call for Presentations 2nd vTechDay at ICANN 69 (Hamburg) The ICANN Tech Working Group is again planning a technical workshop at the ICANN 69 meeting (Hamburg) on Monday 2020-10-19. As the meeting will be virtual vTechDay will be conducted as Zoom Webinar. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNSSEC, in particular within the European Region and with regards to SHA-1 Transition 2. RDAP implementations 3. Best security management practices, lines of defence, to protect the registry from bad actors, attacks or malware 4. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email ccNSO-techday(a)icann.org or reply to this email. We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el

1 0

FW: ROW#9 event reminder - June 16th, 2020 - Zoom Webinar
by Hollenbeck, Scott June 16, 2020

June 16, 2020

The workshop starts in about an hour. Don’t miss it! Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Tuesday, June 16, 2020 12:18 AM Subject: [EXTERNAL] ROW#9 event reminder - June 16th, 2020 - Zoom Webinar 9th Registration Operations Workshop (ROW#9) ROW#9 session starting soon!!! Tuesday, 16 June 2020, 13:00 – 16:00 UTC. Check additional time zones here<https://secure-web.cisco.com/10ME9_zVEzKDFpAG39NZxRPPeAyMESpCzxZCI5bEnwKu2H…>. The event will take place via a Zoom Webinar platform. Those interested in attending are required to register<http://regiops.net/?event=virtual-9th-registration-operations-workshop-row9> in order to receive the access information. ROW#9 agenda • Panel: DNS Privacy and Encryption • Geoff Huston [APNIC] • John Levine [Standcore LLC] • Stephane Bortzmeyer [AFNIC] • An Architecture overview of APNIC’s RDAP deployment to cloud – George Michaelson [APNIC] • Deprecating jCard in RDAP: why and how – Mario Loffredo [IIT‐CNR/Registro.it<http://Registro.it>] & Gavin Brown [CentralNic] • i.whoswho – Whois/RDAP lookup for mere mortals – Werner Staub [CORE Association] • EPP Extension: Registry Maintenance – Tobias Sattler [UnitedDomains] • The Biggest Obstacle for Innovating with New TLDs – Thomas Barrett [EnCirca, Inc] • Drone Remote Identification Protocol (DRIP) Use Cases – Stuart W. Card [AX Enterprize, LLC] & Robert Moskowitz [HTT Consulting] Session presentations are now available at: http://regiops.net/?page_id=115 We would like to thank our ROW Series Sponsors ICANN<https://secure-web.cisco.com/1HeeagTMLhxkV-f8GyPigs1C5iGXrac6_CeH5wHl7Fo94w…> and Verisign<https://www.verisign.com> for allowing ROW#9 to happen. Visit http://regiops.net for updates, additional event details, and previous ROW events. If you have any questions, please contact us at row(a)viagenie.ca<mailto:row@viagenie.ca>. We look forward to seeing you online! ROW Program Committee Stay tuned for further updates! Follow us on Twitter @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (sign-up at: https://groups.google.com/forum/#!forum/regiops/join) (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: ROW#9 event reminder - June 16th, 2020 - Zoom Webinar
by Hollenbeck, Scott June 11, 2020

June 11, 2020

FYI, folks. Please note that the workshop takes place next Tuesday, 16 June. The agenda is available here: http://regiops.net/?page_id=115 Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Thursday, June 11, 2020 11:16 AM Subject: [EXTERNAL] ROW#9 event reminder - June 16th, 2020 - Zoom Webinar Register now to attend the 9th Registration Operations Workshop! June 16th, 2020 | 13:00 - 16:00 UTC ROW#9 will take place via Zoom Webinar platform on Tuesday, 16 June 2020, 13:00 – 16:00 UTC. Additional time zones may be checked here<https://secure-web.cisco.com/14iBSdNGdIhLdtmhZSPiVK0L3zN-qyvYmSLagFJM4vJkQS…>. Those interested in attending ROW#9 are required to register<http://regiops.net/?event=virtual-9th-registration-operations-workshop-row9> in order to receive the access information (meeting ID and password). For details on the agenda, check out Marc Blanchet’s [Viagenie] recent blog post at: http://www.circleid.com/posts/20200610-9th-registration-operations-workshop…<http://secure-web.cisco.com/1lDMzrAt8u6kD5i5eWEA5Ygc1JEraxnQs3gLQcEah64mRf-…> or visit http://regiops.net for registrations, agenda, updates, and previous ROW events. If you have any questions, please contact us at row(a)viagenie.ca<mailto:row@viagenie.ca>. We would like to thank our ROW Series Sponsors ICANN<https://secure-web.cisco.com/1jSquD5OZUKkw4AE28ycfXMESHrf5RUP-XnsbwgL9C_M7j…> and Verisign<https://www.verisign.com> for allowing ROW#9 to happen. ----- Here are some special tips if this is your first time using Zoom or you wish to get more familiar with its web conferencing capabilities: * Download the Zoom application to your computer or mobile phone. You can do it at https://zoom.us/download<https://secure-web.cisco.com/1eqKCB9PAq2TH_aBg_afQlNb3aqU2u5pcaqi-QG4O3qCeB…>. You will also be prompted to download and install Zoom when you click the link to join. You can also run Zoom from your web browser by navigating to join.zoom.us<http://secure-web.cisco.com/1bquRQ9_yma4wNdl81frsA_nq54PpIpTUwmmIg8SR7Szltb…> and entering the meeting number and passcode. * Want to try it out before June 16th? Join a test meeting at https://zoom.us/test<https://secure-web.cisco.com/1xJL4RBAUsdk_HFD4dKoJsUuLZdVQNfzUeCWb6aE0TRbxI…> anytime to familiarize yourself with Zoom. You can also access Zoom tutorials here: https://support.zoom.us/hc/en-us/articles/201362193-How-Do-I-Join-A-Meeting-<https://secure-web.cisco.com/10UWu4Chj350JQxEIQTOZXQQeVjxGlCrfrcyOn9uiLHFDv…> * As an attendee, you will be muted. The meeting host will open mics as needed for Q&As when announced by the session moderator. * You do not have to use the Zoom web conferencing platform with video to participate. There is an option to call-in only. * We will be recording this webinar, including the chat, and making it available on our website. ----- We look forward to seeing you online! ROW Program Committee Stay tuned for further updates! Follow us on Twitter @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (sign-up at: https://groups.google.com/forum/#!forum/regiops/join) (cross-posting to multiple lists - sorry for any duplicates)

1 0

Call for Presentations TechDay ICANN 67 Cancun
by Dr Eberhard W Lisse May 19, 2020

May 19, 2020

Call for Presentations 41th TechDay at ICANN 67 in Cancún The ICANN Tech Working Group is again planning a technical workshop at the ICANN 66 meeting in Cancún on Monday 2020-03-06 Blocks 2-5 starting 10:30 The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. DNS Abuse 2 DNS over TCP, DNS over HTTPS 3. IDN 4 DNSSEC, in particular within the LAC region 5. In addition, we welcome suggestions for additional topics If you are interested in presenting, please email ccNSO-techday(a)icann.org We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 3

FW: June 16th, 2020 - Virtual ROW#9 - Call for proposals & participation
by Hollenbeck, Scott May 8, 2020

May 8, 2020

FYI, folks! Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Thursday, May 7, 2020 8:27 PM Subject: [EXTERNAL] June 16th, 2020 - Virtual ROW#9 - Call for proposals & participation June 16th, 2020 | 13:00 - 16:00 UTC Register now & submit your proposal for newly scheduled virtual ROW#9 session The Program Committee would like to thank all those that took the time to respond to our latest survey. Given the community feedback, the Program Committee has decided to pursue the ROW#9 virtual session alternative for 2020. ROW#9<http://regiops.net> will be held via remote participation on June 16th, 2020, 13:00 - 16:00 UTC, to accommodate as many participants around the world as possible. (check different time zones here<https://secure-web.cisco.com/1TH8lKMBGJ3b2dP9qoD3qZ6JCyGcCvlELCNU_5Vpr0OXr9…>). IMPORTANT: Registration is required to enable participation! Those interested in attending the virtual meeting are required to register at the following link in order to receive the access information for the online session: http://regiops.net/?event=virtual-9th-registration-operations-workshop-row9 The Program Committee is also re-opening the call for presentation and panel proposals. Please email a short abstract describing your proposal to row(a)viagenie.ca<mailto:row@viagenie.ca> before May 25th, 2020. There is no need to re-submit a proposal that has already been submitted. In the past, workshops have included presentations and panel discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more. Below is a list of possible topics for this session: * RDAP implementation experience * DNS abuse * DNS privacy and encryption * Differentiated access * Authentication and authorization * Credential Security/Credential Management * DNSSEC operalization (CSYNC, managing transfers of secured domains) * Registration support functions (data escrow/business continuity) * Automation We hope that you can join us and request that you disseminate this Call to other lists where it might be of interest. We look forward to your participation! For additional event details and previous ROW sessions, visit http://regiops.net. Additional ROW discussions may take place on the regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> mailing list. ROW Program Committee Stay tuned for further updates! Follow @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie?ref_src=twsrc%5Etfw> ROW website: http://regiops.net Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1bJpgeba467F2fFDLwq_TCMrF4Cah27MUIBEiuQB4hOcjQ…>, organized by Viagenie<http://secure-web.cisco.com/1aTm39VNgSq5f5IiVa10LCNrmWxP-EqM-zp6KnSUHrDFY_5…> (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: June 16th, 2020 - Virtual ROW#9 - Call for proposals & participation
by Hollenbeck, Scott May 8, 2020

May 8, 2020

FYI, folks! Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Thursday, May 7, 2020 8:27 PM Subject: [EXTERNAL] June 16th, 2020 - Virtual ROW#9 - Call for proposals & participation June 16th, 2020 | 13:00 - 16:00 UTC Register now & submit your proposal for newly scheduled virtual ROW#9 session The Program Committee would like to thank all those that took the time to respond to our latest survey. Given the community feedback, the Program Committee has decided to pursue the ROW#9 virtual session alternative for 2020. ROW#9<http://regiops.net> will be held via remote participation on June 16th, 2020, 13:00 - 16:00 UTC, to accommodate as many participants around the world as possible. (check different time zones here<https://secure-web.cisco.com/1TH8lKMBGJ3b2dP9qoD3qZ6JCyGcCvlELCNU_5Vpr0OXr9…>). IMPORTANT: Registration is required to enable participation! Those interested in attending the virtual meeting are required to register at the following link in order to receive the access information for the online session: http://regiops.net/?event=virtual-9th-registration-operations-workshop-row9 The Program Committee is also re-opening the call for presentation and panel proposals. Please email a short abstract describing your proposal to row(a)viagenie.ca<mailto:row@viagenie.ca> before May 25th, 2020. There is no need to re-submit a proposal that has already been submitted. In the past, workshops have included presentations and panel discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more. Below is a list of possible topics for this session: * RDAP implementation experience * DNS abuse * DNS privacy and encryption * Differentiated access * Authentication and authorization * Credential Security/Credential Management * DNSSEC operalization (CSYNC, managing transfers of secured domains) * Registration support functions (data escrow/business continuity) * Automation We hope that you can join us and request that you disseminate this Call to other lists where it might be of interest. We look forward to your participation! For additional event details and previous ROW sessions, visit http://regiops.net. Additional ROW discussions may take place on the regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> mailing list. ROW Program Committee Stay tuned for further updates! Follow @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie?ref_src=twsrc%5Etfw> ROW website: http://regiops.net Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://secure-web.cisco.com/1bJpgeba467F2fFDLwq_TCMrF4Cah27MUIBEiuQB4hOcjQ…>, organized by Viagenie<http://secure-web.cisco.com/1aTm39VNgSq5f5IiVa10LCNrmWxP-EqM-zp6KnSUHrDFY_5…> (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: ROW#9 Postponed
by Hollenbeck, Scott March 23, 2020

March 23, 2020

FYI, folks. Please take a few minutes to complete the survey if you can - we want to hear from you. Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Monday, March 23, 2020 1:07 PM Subject: [EXTERNAL] ROW#9 Postponed Postponement of the 9th Registration Operations Workshop (ROW#9) As GDD Summit, IDS and OARC 33, the May 2020 in-person meeting of ROW#9<http://regiops.net> is cancelled. We are not scheduling another in-person event in 2020 but are considering alternatives. This decision was made as a result of the COVID-19 outbreak, considered a public health emergency of international concern by the World Health Organization. The Program Committee is looking into the possibility to organize a virtual ROW#9 session during 2020, should the community be interested in this option. For this purpose, please let us know via the following short survey (2 min) your interest regarding the next ROW session: https://www.surveymonkey.com/r/CJRVPMR The Program Committee thanks you for your continued interest into the ROW events. ROW Program Committee Stay tuned for further updates! Follow @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie?ref_src=twsrc%5Etfw> ROW website: http://regiops.net Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: Call for proposals - ROW#9 - Paris - May 6th, 2020
by Hollenbeck, Scott Jan. 31, 2020

Jan. 31, 2020

FYI, folks. Scott From: nicoleta munteanu <munteanu.nicoleta(a)outlook.com> Sent: Friday, January 31, 2020 1:23 PM Subject: Call for proposals - ROW#9 - Paris - May 6th, 2020 Register now & submit your proposal for the 9th Registration Operations Workshop (ROW#9) | May 6th, 2020 | Paris, France ROW#9<http://regiops.net> is scheduled to take place on the afternoon of Wednesday, 6 May 2020, in Paris, France. The workshop will take place immediately after the GDD Industry Summit<https://www.icann.org/gddsummit> (3-6 May) and prior to the DNS Symposium<https://www.icann.org/ids> (7-8 May) and DNS-OARC<https://indico.dns-oarc.net/event/34/> (9-10 May). Registration is now available at: http://regiops.net/?event=9th-registration-operations-workshop-row9 The Program Committee is now opening the call for presentation and panel proposals and is interested in: 1. Topic related presentation proposals. 2. Topic suggestions for focused panel discussions. 3. Suggestions for additional topics. In the past, workshops have included presentations and panel discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more. Below is a list of possible topics for this session: * RDAP implementation experience * DNS abuse * DNS privacy and encryption * Differentiated access * Authentication and authorization * Credential Security/Credential Management * DNSSEC operalization (CSYNC, managing transfers of secured domains) * Registration support functions (data escrow/business continuity) * Automation Please email a short abstract describing your proposal to row(a)viagenie.ca<mailto:row@viagenie.ca> . Discussions of workshop topics may also take place on the regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> mailing list. We hope that you can join us and request that you disseminate this Call to other lists where it might be of interest. We look forward to your participation in Paris! For additional event details, more information on the venue, and previous ROW events, visit http://regiops.net. ROW Program Committee Stay tuned for further updates! Follow @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie?ref_src=twsrc%5Etfw> ROW website: http://regiops.net Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (sign-up at: https://groups.google.com/forum/#!forum/regiops/join) ROW series: co-sponsored by Verisign<https://www.verisign.com/> & ICANN<https://www.icann.org/>, organized by Viagenie<http://viagenie.ca/> (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: ROW#9 - May 6th, 2020 - Paris, France
by Hollenbeck, Scott Nov. 1, 2019

Nov. 1, 2019

FYI, folks. Scott From: Nicoleta Munteanu <munteanu.nicoleta(a)outlook.com> Sent: Friday, November 1, 2019 2:14 PM Subject: [EXTERNAL] ROW#9 - May 6th, 2020 - Paris, France 9th Registration Operations Workshop (ROW#9) | May 6th, 2020 | Paris, France The Program Committee is pleased to invite you to save the date for our 9th Registration Operations Workshop<http://regiops.net> (ROW#9), scheduled to take place on the afternoon of Wednesday, 6 May 2020, in Paris, France at the Marriott Rive Gauche Hotel & Conference Center. Aiming for another successful session benefiting from the co-location with key industry events, the workshop will take place immediately after the GDD Industry Summit<https://www.icann.org/gddsummit> (3-6 May) and prior to the DNS Symposium<https://www.icann.org/ids> (7-8 May) and DNS-OARC<https://www.dns-oarc.net> (9-10 May). The ROW series, co-sponsored by Verisign<https://www.verisign.com> and ICANN<https://www.icann.org> and organized by Viagenie<http://viagenie.ca> has for the past 5 years provided a forum for all industry members, including address/gTLD/ccTLD registries, domain name registrars, resellers, and second level domain registries, to present and discuss technical topics related to real world experiences of implementing registration operations. In the past, workshops have included presentations and panel discussions focused on Extensible Provisioning Protocol (EPP), WHOIS, Registry Lock, Registration Data Access Protocol (RDAP) and many more. The Program Committee is aiming for another engaging set of talks, presentations and panel discussions with individuals involved with the operation of domain name registrations systems. Below is a list of possible topics for this session and we encourage you to discuss and suggest additional topics either on ROW’s mailing list regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> or by email at row(a)viagenie.ca<mailto:row@viagenie.ca>. * RDAP implementation experience * DNS abuse * DNS privacy and encryption * Differentiated access * Authentication and authorization * Credential Security/Credential Management * DNSSEC operalization (CSYNC, managing transfers of secured domains) * Registration support functions (data escrow/business continuity) * Automation We look forward to your participation in Paris! For additional event details, more information on the venue, and previous ROW events, visit http://regiops.net. ROW Program Committee Stay tuned for further updates! Follow @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie?ref_src=twsrc%5Etfw> ROW website: http://regiops.net Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (sign-up at: https://groups.google.com/forum/#!forum/regiops/join) (cross-posting to multiple lists - sorry for any duplicates)

1 0

Call for Presentations ICANN66 Montreal
by Dr Eberhard W Lisse Oct. 15, 2019

Oct. 15, 2019

Call for Presentations 40th TechDay at ICANN 66 in Montréal The ICANN Tech Working Group is again planning a technical workshop at the ICANN 66 meeting in Montréal on Monday 2019-11-04 The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. Planning for the Worst We all know classic advice to have off-site backup or secondary data centers. What measure can be taken to lessen the impact when disaster hits? Is it fine to let the registration system fail, while you concentrate on keeping DNS service alive? But what about when disaster does not hit you, but affects registrants somewhere else in the world? Do you extend the registration period, to prevent domains from expiring while they recover? We are interested in presentations on how registries prepare themselves for disaster, and especially encourage registries, that were struck by disaster, to share their experiences. 2. DNS Abuse As this is going to be one of the High Interest Topics for the Meeting we are quite interested in hearing from a technical perspective. 3. In addition, we welcome suggestions for additional topics, such as; * DNS over TCP, DNS over HTTPS If you are interested in presenting, please email ccNSO-techday(a)icann.org We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 1

Call for Presentations ICANN65 Marrakesh
by Dr Eberhard W Lisse June 14, 2019

June 14, 2019

Call for Presentations 40th TechDay at ICANN 65 in Marrakesh The ICANN Tech Working Group is again planning a technical workshop at the ICANN 65 meeting in Marrakesh on Monday 2019-06-24, Blocks 3-5, starting 13:30. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. IDN 2. Disaster Planning and Mitigation 3. Techniques for fighting abuse 4. DNSSEC In particular: Getting Africa signed) 5. RDAP – what is it, implementing, authentication, challenges 6. IDNA2008 – emoji 7. In addition, we welcome suggestions for additional topics. If you are interested in presenting, please email ccNSO-techday(a)icann.org We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. greetings, el

2 4

REMINDER: 2nd Call for Participation -- ICANN DNSSEC Workshop at ICANN65, Marrakech, Morocco.
by Jacques Latour June 4, 2019

June 4, 2019

Hi all! We have 3 or 4 spots (90 minutes total) available in the DNSSEC program. Let us know if you have something to present, in person or remote. Jacques =========================== 2nd Call for Participation -- ICANN DNSSEC Workshop at ICANN65, Marrakech, Morocco. The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC Workshop during the ICANN65 meeting held from 24-27 June 2019 in Marrakech, Morocco. The DNSSEC Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN Community Forum in Kobe, Japan on 13 March 2019. The presentations and transcripts are available at: https://64.schedule.icann.org/meetings/961937 <https://urldefense.proofpoint.com/v2/url?u=https-3A__64.schedule.icann.org_…> , https://64.schedule.icann.org/meetings/961938, and https://64.schedule.icann.org/meetings/961939. The DNSSEC Workshop Program Committee is developing a 3-hour program. Proposals will be considered for the following topic areas and included if space permits. In addition, we welcome suggestions for additional topics either for inclusion in the ICANN65 workshop, or for consideration for future workshops. 1. DNSSEC Activities Panel (Regional and global) For this panel, we are seeking participation from those who have been involved in DNSSEC deployment in the region and also from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment, including Root Key Signing Key (KSK) Rollover activities. Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? What is the best practice around key rollovers? How often do you review your disaster recovery procedures? Is there operational familiarity within your customer support teams? What operational statistics have we gathered about DNSSEC? Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? If you have a specific concern about the Root Key Rollover, or believe you have a method or solution to help address impacts, we would like to hear from you. 2. DNSSEC Deployment Challenges The program committee is seeking input from those that are interested in implementation of DNSSEC but have general or particular concerns with DNSSEC. In particular, we are seeking input from individuals that would be willing to participate in a panel that would discuss questions of the nature: - Are there any policies directly or indirectly impeding your DNSSEC deployment? (RRR model, CDS/CDNSKEY automation) - What are your most significant concerns with DNSSEC, e.g., complexity, training, implementation, operation or something else? - What do you expect DNSSEC to do for you and what doesn't it do? - What do you see as the most important trade-offs with respect to doing or not doing DNSSEC? We are interested in presentations related to any aspect of DNSSEC such as zone signing, DNS response validation, applications use of DNSSEC, registry/registrar DNSSEC activities, etc. In addition, we welcome suggestions for additional topics. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-marrakech(a)isoc.org<mailto:dnssec-marrakech@isoc.org> by **Friday, 31 May 2019** Thank you, Kathy and Julie On behalf of the DNSSEC Workshop Program Committee: Mark Elkins, DNS/ZACR Jean Robert Hountomey, AfricaCERT Jacques Latour, .CA Xiaodong Lee, Chinese Academy of Sciences (CAS) Russ Mundy, Parsons Ondrej Filip, CZ.NIC Yoshiro Yoneya, JPRS Dan York, Internet Society

1 0

Call for Participation -- ICANN DNSSEC Workshop at ICANN65, Marrakech, Morocco.
by Jacques Latour May 10, 2019

May 10, 2019

Call for Participation -- ICANN DNSSEC Workshop at ICANN65, Marrakech, Morocco. The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC Workshop during the ICANN65 meeting held from 24-27 June 2019 in Marrakech, Morocco. The DNSSEC Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN Community Forum in Kobe, Japan on 13 March 2019. The presentations and transcripts are available at: https://64.schedule.icann.org/meetings/961937, https://64.schedule.icann.org/meetings/961938, and https://64.schedule.icann.org/meetings/961939. The DNSSEC Workshop Program Committee is developing a 3-hour program. Proposals will be considered for the following topic areas and included if space permits. In addition, we welcome suggestions for additional topics either for inclusion in the ICANN65 workshop, or for consideration for future workshops. 1. DNSSEC Activities Panel (Regional and global) For this panel, we are seeking participation from those who have been involved in DNSSEC deployment in the region and also from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment, including Root Key Signing Key (KSK) Rollover activities. Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? What is the best practice around key rollovers? How often do you review your disaster recovery procedures? Is there operational familiarity within your customer support teams? What operational statistics have we gathered about DNSSEC? Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? If you have a specific concern about the Root Key Rollover, or believe you have a method or solution to help address impacts, we would like to hear from you. 2. DNSSEC Deployment Challenges The program committee is seeking input from those that are interested in implementation of DNSSEC but have general or particular concerns with DNSSEC. In particular, we are seeking input from individuals that would be willing to participate in a panel that would discuss questions of the nature: - Are there any policies directly or indirectly impeding your DNSSEC deployment? (RRR model, CDS/CDNSKEY automation) - What are your most significant concerns with DNSSEC, e.g., complexity, training, implementation, operation or something else? - What do you expect DNSSEC to do for you and what doesn't it do? - What do you see as the most important trade-offs with respect to doing or not doing DNSSEC? We are interested in presentations related to any aspect of DNSSEC such as zone signing, DNS response validation, applications use of DNSSEC, registry/registrar DNSSEC activities, etc. In addition, we welcome suggestions for additional topics. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-marrakech(a)isoc.org<mailto:dnssec-marrakech@isoc.org> by **Friday, 17 May 2019** Thank you, Jacques On behalf of the DNSSEC Workshop Program Committee: Mark Elkins, DNS/ZACR Jean Robert Hountomey, AfricaCERT Jacques Latour, .CA Xiaodong Lee, Chinese Academy of Sciences (CAS) Russ Mundy, Parsons Ondrej Filip, CZ.NIC Yoshiro Yoneya, JPRS Dan York, Internet Society

1 0

Fwd: ROW#8 event reminder - May 9th, 2019 - Bangkok, Thailand
by Hollenbeck, Scott May 7, 2019

May 7, 2019

FYI, folks! Scott Begin forwarded message: From: Nicoleta Munteanu <munteanu.nicoleta(a)outlook.com<mailto:munteanu.nicoleta@outlook.com>> Date: May 8, 2019 at 1:58:00 PM GMT+9 To: Undisclosed recipients:; Subject: [EXTERNAL] ROW#8 event reminder - May 9th, 2019 - Bangkok, Thailand 8th Registration Operations Workshop (ROW#8) ROW#8 will take place this Thursday, 9 May 2019, during the last day of the GDD Industry Summit<https://www.icann.org/gddsummit> and within the same venue. Please find event details below. --- ROW#8 session information Thursday, 9 May 2019 1.30pm – 5.00pm (ICT<https://www.timeanddate.com/worldclock/thailand/bangkok> timezone: UTC+7) Shangri-La hotel, Bangkok, Thailand Ballroom 1 Meeting Room, Lobby Level Remote Participation Information: • Remote participation link: https://icann.zoom.us/my/row2019 • Audio also available via phone: find your local number at https://zoom.us/u/abNdizrhtw and use 237 805 6203 participant code --- ROW#8 agenda • Panel: “Registry Lock: What’s the Standard?” – James Galvin [Afilias] – chair, Gavin Brown [CentralNic], Jaromir Talir [CZ.NIC], Justin Mack [MarkMonitor], Tongfeng Zhang [CIRA] • RSP Transition of an RDAP-enabled TLD – Gavin Brown [CentralNic] • An RDAP capability for server specification provisioning – Mario Loffredo & Maurizio Martinelli [IIT‐CNR/Registro.it<http://Registro.it>] • How to implement a thin registry with eligibility requirements – Gavin Brown [CentralNic] • RDAP CDN Distribution Experience – Tom Harrison [APNIC] • Panel: “RDAP Implementation and Deployment Experience” – Rick Wilhelm [Verisign] – chair, Gavin Brown [CentralNic], George Michaelson [APNIC], James Galvin [Afilias], Jaromir Talir [CZ.NIC], Justin Mack [MarkMonitor], Mario Loffredo [IIT‐CNR/Registro.it<http://Registro.it>] --- We would like to thank our ROW Series Sponsors ICANN<https://www.icann.org> and Verisign<https://www.verisign.com> for allowing ROW#8 to happen. Visit http://regiops.net for registrations, updates, additional event details, and previous ROW events. If you have any questions, please contact us at row(a)viagenie.ca<mailto:row@viagenie.ca>. We look forward to seeing you in Bangkok or remotely! ROW Program Committee Stay tuned for further updates! Follow us on Twitter @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie> <https://twitter.com/ROW_by_Viagenie> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (sign-up at: https://groups.google.com/forum/#!forum/regiops/join) (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: Upcoming ROW#8 agenda
by Hollenbeck, Scott April 23, 2019

April 23, 2019

FYI, folks! Scott From: Nicoleta Munteanu <munteanu.nicoleta(a)outlook.com> Sent: Monday, April 22, 2019 3:50 PM Subject: [EXTERNAL] Upcoming ROW#8 agenda 8th Registration Operations Workshop | May 9th, 2019 | Bangkok, Thailand Registration Operations Workshops co-sponsors Verisign<https://www.verisign.com/> and ICANN<https://www.icann.org/> and organizer Viagenie<http://viagenie.ca/> are looking forward to engaging in discussions during the upcoming Registration Operations Workshop<http://regiops.net/> (ROW#8). The event will take place on Thursday, 9 May 2019, 1.30pm-5.oopm ICT<https://www.timeanddate.com/worldclock/thailand/bangkok> timezone, in Bangkok, Thailand, during the last day of the GDD Industry Summit<https://www.icann.org/gddsummit> (6-9 May) and prior to ICANN DNS Symposium<https://www.icann.org/ids> (10-11 May) and OARC 30<https://indico.dns-oarc.net/event/31/> (12-13 May). ROW#8 session will include panel discussions and presentations exploring the following topics: • “Registry Lock: What’s the Standard?” Panel - James Galvin [Afilias] – chair, Jaromir Talir [CZ.NIC], Justin Mack [MarkMonitor] • RSP Transition of an RDAP-enabled TLD – Gavin Brown [CentralNic] • An RDAP capability for server specification provisioning – Mario Loffredo & Maurizio Martinelli [IIT‐CNR/Registro.it<http://Registro.it>] • How to implement a thin registry with eligibility requirements – Gavin Brown [CentralNic] • “RDAP Implementation and Deployment Experience” Panel - Rick Wilhelm [Verisign] – chair, Jaromir Talir [CZ.NIC], Justin Mack [MarkMonitor], James Galvin [Afilias], Mario Loffredo [IIT‐CNR/Registro.it<http://Registro.it>], Gavin Brown [CentralNic] If interested in adding another presentation topic or joining the panels, please email us asap at row(a)viagenie.ca<mailto:row@viagenie.ca>. While there is no fee to attend the ROW, we encourage anyone interested to register<http://regiops.net/?event=8th-registration-operations-workshop-row8> so that we can appropriately size the room. The session may also be accessed via remote participation. See details on our a<http://regiops.net/?page_id=115>genda<http://regiops.net/?page_id=115> page. Visit http://regiops.net for additional updates, event details, more information on the venue, and previous ROW events. We look forward to seeing you in Bangkok! ROW Program Committee Stay tuned for further updates! Follow us on Twitter @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (sign-up at: https://groups.google.com/forum/#!forum/regiops/join) (cross-posting to multiple lists - sorry for any duplicates)

1 0

RDAP zoneSigned flag
by Michael Bauland March 28, 2019

March 28, 2019

Hi, I just stumbled across the definition of zoneSigned as part of the secureDNS member in RFC7483. There is says: zoneSigned -- true if the zone has been signed, false otherwise. Now I'm wondering whether this relates to the TLD zone (i.e., it always MUST be set to true for ngTLDs) or whether the SLD zone is meant, in which case the registry does not know the value and simply won't publish it. Thanks in advance, Michael -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Dipl.-Informatiker Fon: +49 231 9703-0 Fax: +49 231 9703-200 Dr. Michael Bauland SIP: Michael.Bauland(a)knipp.de Software Development E-mail: Michael.Bauland(a)knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp

2 3

FW: Call for Registration & Proposals - ROW#8 - Bangkok
by Hollenbeck, Scott March 26, 2019

March 26, 2019

FYI, folks. Sorry for the cross-posting. Scott From: Nicoleta Munteanu <munteanu.nicoleta(a)outlook.com> Sent: Wednesday, March 27, 2019 1:42 AM Subject: [EXTERNAL] Call for Registration & Proposals - ROW#8 - Bangkok Register now for the 8th Registration Operations Workshop! | May 9th, 2019 | Bangkok, Thailand The 8th Registration Operations Workshop<http://regiops.net/> (ROW#8) is scheduled to take place on Thursday, 9 May 2019, afternoon, in Bangkok, Thailand, during the last day of the GDD Industry Summit<https://www.icann.org/gddsummit> (6-9 May) and within the same venue. The workshop will also be collocated with ICANN DNS Symposium<https://www.icann.org/ids> (10-11 May) and OARC 30<https://indico.dns-oarc.net/event/31/> (12-13 May). Registration process is now available at: http://regiops.net/?event=8th-registration-operations-workshop-row8 Please note that the call for presentation and panel proposals is still active. In keeping with the Registration Operations' focus of the ROW, possible topics for this session could be: * RDAP implementation experience (presentations and/or panel of implementors to discuss their experience) * Registry Lock / Security Lock (presentations and/or panel of operators to discuss approach, experience, challenges) * Operation (Performance) Statistics Related to Registration * Data Escrow * Suggestions for additional topics Proposals in the form of a short abstract shall be submitted to row(a)viagenie.ca<mailto:row@viagenie.ca>. Deadline is April 2nd, 2019. Discussions of workshop topics may also take place on the regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> mailing list. We hope that you can join us and request that you disseminate this Call to other lists where it might be of interest. Visit http://regiops.net for additional event details, more information on the venue, and previous ROW events. We look forward to seeing you in Bangkok! ROW Program Committee Stay tuned for further updates! Follow us on Twitter @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (sign-up at: https://groups.google.com/forum/#!forum/regiops/join) (cross-posting to multiple lists - sorry for any duplicates)

1 0

Technical Study Group Publishes Draft Model for Review and Input
by Francisco Arias March 8, 2019

March 8, 2019

FYI On 3/8/19, 3:42 PM, "TSG-Access-RD on behalf of Diana Middleton" <tsg-access-rd-bounces(a)icann.org<mailto:tsg-access-rd-bounces@icann.org> on behalf of diana.middleton(a)icann.org<mailto:diana.middleton@icann.org>> wrote: Dear all, the most recent blog on our progress was published: https://www.icann.org/news/blog/technical-study-group-publishes-draft-model… Best, Diana

1 0

Re: [gtld-tech] [Ext] AW: RDAP service in the gTLD space
by Francisco Arias March 4, 2019

March 4, 2019

Hi Alex, We are planning to release the update by May. -- Francisco On 2/27/19, 11:14 PM, "Alexander Mayrhofer" <alexander.mayrhofer(a)nic.at<mailto:alexander.mayrhofer@nic.at>> wrote: Francisco, can you give us a timeline for the potential extension of the “Registrar ID” registry at IANA (https://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml)? – I understand that the RDAP base URL is to be added there, so that registries don’t need to collect that information from registrars individually. Since we’d like to test that rather soon, it would be appreciated if that extension happened rather sooner than later. Best, Alex Von: gtld-tech <gtld-tech-bounces(a)icann.org> Im Auftrag von Francisco Arias Gesendet: Donnerstag, 28. Februar 2019 00:34 An: gtld-tech(a)icann.org Betreff: [gtld-tech] FYI: RDAP service in the gTLD space Today, ICANN org issued a notification to gTLD registries and registrars of the requirement to implement an RDAP service by 26 August 2019. https://www.icann.org/resources/pages/rdap-implementers-resources-2018-08-3… -- Francisco

1 0

Hopefully Final Agenda for TechDay Kobe ICANN64
by Dr Eberhard W Lisse March 4, 2019

March 4, 2019

Plnce ease find enclosed, the agenda will also be published by the ccNSO Secretatriat on the web site and in the Google Calendar for ease of planning. greetings, el -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 0

Re: [gtld-tech] [regext] EPDP recommendations and EPP
by Roger D Carney March 1, 2019

March 1, 2019

Good Morning, Thanks for the comments Patrick. Agreed, another one of the concerns going with placeholders is that to some, it will lessen the urgency to solve the underlying issue. Not speaking specifically to the examples you gave on multiple mechanisms, I still believe that adding an additional contact mapping will increase implementation complexity that is not needed, more below. As far as tailoring the protocol, it seems to me that the current RFC 5733 has been tailored. I am not sure why 5733 required these fields to exist in the first place, I assume it was discussed when it was written many years ago and it was decided for some reason these fields be treated special, but I don't see a technical reason to treat them differently. I don't think the idea of making the EPP Contact Mapping more flexible is a gTLD specific solution. Thanks for digging deeper into what it takes to "improve" the current mechanism. As Gavin mentioned in his original email, this would require a new RFC be created and you have provided some more logistics to that effort. As you mention, there may be clients that may need to support both namespaces, but for servers that choose to use the new namespace the interface on both sides would be less complex than having two mapping mechanisms. Servers could have the option of supporting the namespace that is appropriate for them (though I assume for gTLDs ICANN would update policy to use the new namespace). Thanks Roger -----Original Message----- From: regext <regext-bounces(a)ietf.org> On Behalf Of Patrick Mevzek Sent: Friday, March 1, 2019 9:55 AM To: regext(a)ietf.org Subject: Re: [regext] [gtld-tech] EPDP recommendations and EPP On Fri, Mar 1, 2019, at 16:22, Roger D Carney wrote: > Thanks for the comments Patrick. I agree about the pollution of > placeholders and that is one reason why I think it can only be used as > a temporary solution. If this is implemented, it will become permanent and there will be nothing else replacing it later. > I am not sold on creating a "new object." Another way to do the same > intention, to me this will just get convoluted for implementers (look > here unless you should look over there). I do not feel that convoluted and even if it is the case we already have many of them: - host attributes vs host objects - secDNS keyData vs dsData etc. > To me this is just creating a > new mechanism to avoid fixing a problem in the current mechanism. There is no problem in current mechanism. ccTLDs are all "fine" with it. Right now we are discussing (in multiple places so that makes participating difficult) things that will only apply to gTLDs. I really do not want again to give everyone's impression that we are tailoring a protocol to a very specific case just because the major vocal interests are there. In short, if gTLDs need another contact model because the one in RFC5733 is not fitting today anymore, it seems the clearer and simpler to me to just define a new model for contacts. > I am not sure how improving RFC 5733 to be more flexible and data > privacy/protection aware is a detriment to anyone using EPP. Anyone > using 5733 needs to be acutely aware of data "processing" and would > greatly benefit from a more flexible technical solution. You can not "improve" RFC 5733. You will need to create a new namespace, like "contact-2.0" At which point it is quite the same for implementors because any client with multi registries need will need to handle both namespaces (you can not expect all registries, specially non gTLD ones, just moving to your new schema, even if it is a strict superset of previous ones, because they will have absolutely 0 reasons, technical or economical, to do the change), so if you have "contact-1.0" and "contact-2.0" namespaces to handle OR "contact-1.0" and "lightContact-1.0" (or "shallowContact-1.0" or "gtldContact-1.0" or whatever) it is basically the same amount of work, but second option seems better to me for multiple reasons. And again, there is a huge non technical difference. If we give again the impression to change the EPP just to suite gTLD needs, we should not lament later on the state of EPP worldwide and why not everyone follows the standard to the letter, or best current practices, etc. -- Patrick Mevzek pm(a)dotandco.com _______________________________________________ regext mailing list regext(a)ietf.org https://www.ietf.org/mailman/listinfo/regext

1 0

Re: [gtld-tech] [regext] EPDP recommendations and EPP
by Roger D Carney March 1, 2019

March 1, 2019

Good Morning, Thanks for the comments Patrick. I agree about the pollution of placeholders and that is one reason why I think it can only be used as a temporary solution. I am not sold on creating a "new object." Another way to do the same intention, to me this will just get convoluted for implementers (look here unless you should look over there). To me this is just creating a new mechanism to avoid fixing a problem in the current mechanism. I am not sure how improving RFC 5733 to be more flexible and data privacy/protection aware is a detriment to anyone using EPP. Anyone using 5733 needs to be acutely aware of data "processing" and would greatly benefit from a more flexible technical solution. Thanks Roger -----Original Message----- From: regext <regext-bounces(a)ietf.org> On Behalf Of Patrick Mevzek Sent: Friday, March 1, 2019 9:03 AM To: regext(a)ietf.org Subject: Re: [regext] [gtld-tech] EPDP recommendations and EPP On Fri, Mar 1, 2019, at 15:39, Roger D Carney wrote: > I think I am in agreement with most people on this, that option 3 (or > C, whatever it is called) is the best short term solution “define a > "convention" that allows the <city> and <cc> elements to contain > placeholder values, such as: <city>-</city> and <cc>XX</cc> which pose > no data protection issues”. I am completely againts such placeholders. While they are the easy fast solution, they just pollute databases with useless data. Instead of updating RFC5733 I would suggest creating a new object, a "light (or shallow) contact" which is like a contact currently, just with less fields. Domains could use "full contacts" (the ones we know today) or light contacts (the new ones). One has to keep remembering that EPP is not just used by gTLDs, so any change has to be done in such a way that it does not impact negatively any operation done outside of ICANN circles. -- Patrick Mevzek pm(a)dotandco.com _______________________________________________ regext mailing list regext(a)ietf.org https://www.ietf.org/mailman/listinfo/regext

1 0

EPDP recommendations and EPP
by Gavin Brown March 1, 2019

March 1, 2019

Hi all, The EPDP final report says that, if a domain name has a technical contact (whose information is different from the registrant's), the only data that registrars should send to registries are the technical contact's name, email address, and phone number (if any). Assuming that technical contacts should still be created and managed as RFC 5733 contact objects, and also assuming that this recommendation is adopted without change, it poses a challenge, because the RFC requires all contact objects to have <city> and <cc> elements. I've been thinking about how this could be resolved, here are some ideas (in descending order of nastiness): * write a new RFC which updates RFC 5733 to make the <city> and <cc> elements optional * write a new EPP extension which makes the technical contact's name, email address, and phone number directly attributes of the the domain name rather than a contact object * define a "convention" that allows the <city> and <cc> elements to contain placeholder values, such as: <city>-</city> and <cc>XX</cc> which pose no data protection issues. Any thoughts? -- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://www.centralnic.com/ +44.7548243029 CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR.

6 9

FYI: RDAP service in the gTLD space
by Francisco Arias Feb. 27, 2019

Feb. 27, 2019

Today, ICANN org issued a notification to gTLD registries and registrars of the requirement to implement an RDAP service by 26 August 2019. https://www.icann.org/resources/pages/rdap-implementers-resources-2018-08-3… -- Francisco

2 1

Call for Presentations ICANN64 Kobe
by Dr Eberhard W Lisse Feb. 21, 2019

Feb. 21, 2019

Draft Call for Presentations 39th TechDay at ICANN 64 in Kobe The ICANN Tech Working Group is again planning a technical workshop at the ICANN 64 meeting in Kobe on Monday 2019-03-11 The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. Planning for the Worst We all know classic advice to have off-site backup or secondary datac enters. What measure can be taken to lessen the impact when disaster hits? Is it fine to let the registration system fail, while you concentrate on keeping DNS service alive? But what about when disaster does not hit you, but affects registrants somewhere else in the world? Do you extend the registration period, to prevent domains from expiring while they recover? We are interested in presentations on how registries prepare themselves for disaster, and especially encourage registries, that were struck by disaster, to share their experiences. 2. Universal Acceptance We are quite interested in presentations regarding the above and/or related to IDN. 3. In addition, we welcome suggestions for additional topics, such as; * DNS over TCP, DNS over HTTPS If you are interested in presenting, please email ccNSO-techday(a)icann.org We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. --------------------------cut-here---------------------- -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 1

FW: Call for proposals - ROW#8 - Bangkok
by Hollenbeck, Scott Feb. 15, 2019

Feb. 15, 2019

Forwarding for your info… Scott From: Nicoleta Munteanu <munteanu.nicoleta(a)outlook.com> Sent: Friday, February 15, 2019 12:06 AM Subject: [EXTERNAL] Call for proposals - ROW#8 - Bangkok Call for presentation and panel proposals for the 8th Registration Operations Workshop (ROW#8) | May 9th, 2019 | Bangkok, Thailand The 8th Registration Operations Workshop<http://regiops.net/> (ROW#8) is scheduled to take place on the afternoon of Thursday, 9 May 2019, in Bangkok, Thailand. The workshop will take place immediately after ICANN’s GDD Industry Summit<https://www.icann.org/gddsummit> and prior to ICANN DNS Symposium<https://www.icann.org/ids> and OARC 30<https://indico.dns-oarc.net/event/31/>. For the past 5 years, ROW has provided a forum for all industry members, including address registries, domain name registrars, gTLD registries, ccTLD registry operators, resellers, and second level domain registries, to present and discuss technical topics related to real world experiences of implementing registration operations. In the past, workshops have included presentations and discussions focused on the Extensible Provisioning Protocol (EPP), WHOIS, and the Registration Data Access Protocol (RDAP). Any technical topic associated with registration operations is “in scope”. The Program Committee is now opening a call for presentation and panel proposals and is interested in: 1. Topic related presentation proposals. 2. Topic suggestions for focused panel discussions. 3. Suggestions for additional topics. Please email an abstract describing your proposal to row(a)viagenie.ca<mailto:row@viagenie.ca>. Discussions of workshop topics may also take place on the regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> mailing list. We hope that you can join us and request that you disseminate this Call to other lists where it might be of interest. Visit http://regiops.net for additional event details, more information on the venue, and previous ROW events. We look forward to seeing you in Bangkok! ROW Program Committee Stay tuned for further updates! Follow us on Twitter @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (sign-up at: https://groups.google.com/forum/#!forum/regiops/join) (cross-posting to multiple lists - sorry for any duplicates)

1 0

Call for Participation -- ICANN DNSSEC Workshop at ICANN64 Kobe, Japan
by Jacques Latour Jan. 16, 2019

Jan. 16, 2019

Call for Participation -- ICANN DNSSEC Workshop at ICANN64 Kobe, Japan The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC Workshop during the ICANN64 meeting held from 09-14 March 2019 in Kobe, Japan. The DNSSEC Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN Annual General Meeting in Barcelona, Spain, on 24 October 2018. The presentations and transcripts are available at: https://63.schedule.icann.org/meetings/901549, and https://63.schedule.icann.org/meetings/901554, and https://63.schedule.icann.org/meetings/901555. At ICANN64 we are particularly interested in live demonstrations of uses of DNSSEC, DS automation or DANE. Examples might include: * DNSSEC automation and deployment using CDS, CDNSKEY, and CSYNC * DNSSEC/DANE validation in browsers and in applications * Secure email / email encryption using DNSSEC, OPENPGPKEY, or S/MIME * DNSSEC signing solutions and innovation (monitoring, managing, validation) * Tools for automating the generation of DNSSEC/DANE records * Extending DNSSEC/DANE with authentication, SSH, XMPP, SMTP, S/MIME or PGP/GPG and other protocols Our interest is to provide current examples of the state of development and to show real-world examples of how DNSSEC and DANE related innovation can be used to increase the overall security of the Internet. We are open to presentations and demonstrations related to any topic associated with DNSSEC and DANE. Examples of the types of topics we are seeking include: 1. DNSSEC Panel (Regional and Global) For this panel, we are seeking participation from those who have been involved in DNSSEC deployment in the region and also from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment. In particular, we will consider the following questions: Are you interested in reporting on DNSSEC validation of your ISPs? What can DNSSEC do for you? What doesn't it do? What are the internal tradeoffs to implementing DNSSEC? What did you learn in your deployment of DNSSEC? We are interested in presentations from both people involved with the signing of domains and people involved with the deployment of DNSSEC-validating DNS resolvers. 2. DS Automation We are looking at innovative ways to automate the parent child synchronization CDS / CDNSKEY and methods to bootstrap new or existing domains. We are also interested in development or plans related to CSYNC, which are aimed at keeping the glue up to date. We would like to hear from DNS Operators what their current thoughts on CDS/CDNSKEY automation are. 3. DNSSEC/DANE Support in the browsers We would be interested in hearing from browser develop what their plans are in terms of supporting DNSSEC/DANE validation. 4. DANE Automation For DNSSEC to reach massive deployment levels it is clear that a higher level of automation is required than is currently available. There also is strong interest for DANE usage within web transactions as well as for securing email and Voice-over-IP (VoIP). We are seeking presentations on topics such as: * How can the industry use DANE and other DNSSEC applications as a mechanism for creating a more secure Internet? * What tools, systems and services are available to help automate DNSSEC key management? * Can you provide an analysis of current tools/services and identify gaps? * What are some of the new and innovative uses of DANE and other DNSSEC applications in new areas or industries? * What tools and services are now available that can support DANE usage? We would be particularly interested in any live demonstrations of DNSSEC / DANE application automation and services. Demonstrations of new tools that make the setup of DNSSEC or DANE more automated would also be welcome. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-kobe(a)isoc.org' before ** 07 February 2019 ** We hope that you can join us. Thank you, Jacques Latour On behalf of the DNSSEC Workshop Program Committee: Jean Robert Hountomey, AfricaCERT Jacques Latour, .CA Russ Mundy, Parsons Ondřej Filip, CZ.NIC Yoshiro Yoneya, JPRS Dan York, Internet Society Mark Elkins, DNS/ZACR

1 0

FW: ROW#8 - May 9th, 2019 - Bangkok, Thailand
by Hollenbeck, Scott Nov. 4, 2018

Nov. 4, 2018

FYI, folks! Scott From: regiops(a)googlegroups.com <regiops(a)googlegroups.com> On Behalf Of Nicoleta Munteanu Sent: Thursday, November 01, 2018 6:41 PM Subject: [EXTERNAL] [regiops] ROW#8 - May 9th, 2019 - Bangkok, Thailand 8th Registration Operations Workshop (ROW#8) | May 9th, 2019 | Bangkok, Thailand The ROW Program Committee is pleased to invite you to save the date for our 8th Registration Operations Workshop<http://regiops.net/> (ROW#8), scheduled to take place on the afternoon of Thursday, 9 May 2019, in Bangkok, Thailand at the Shangri-La<http://www.shangri-la.com/bangkok/shangrila/> hotel. The workshop will take place immediately after ICANN’s Global Domains Division (GDD) Industry Summit and prior to ICANN’s Domain Name System (DNS) Symposium, and the DNS Operations, Analysis, and Research Center (DNS-OARC). The events will take place at the same venue, as follows: •• GDD Industry Summit<https://www.icann.org/gddsummit>: Monday, 6 May – Thursday, 9 May 2019 •• ROW#8<http://regiops.net>: Thursday, 9 May 2019, afternoon •• ICANN DNS Symposium<https://www.icann.org/ids>: Friday, 10 May – Saturday, 11 May 2019 •• DNS OARC<https://indico.dns-oarc.net/event/29/>: Sunday, 12 May – Monday, 13 May 2019 The workshop is a half-day event focused on, but not be limited to, technical aspects of real world experiences of implementing registration operations for the Registration Data Access Protocol (RDAP) pilot and gTLD launches. Given the current positioning of the ROW, the Program Committee is welcoming any suggestions for the ROW#8 theme, discussion/presentation proposals or comments regarding a change in the format of the session to allow for a goal oriented workshops incorporating deliverables, decisions or proposed solutions to be adopted. Discussions may take place on the regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> mailing list or by email at row(a)viagenie.ca<mailto:row@viagenie.ca>. Visit http://regiops.net for additional event details, more information on the venue, and previous ROW events. We look forward to seeing you in Bangkok! ROW Program Committee Stay tuned for further updates! Follow us on Twitter @ROW_by_Viagenie<https://twitter.com/ROW_by_Viagenie> ROW website: http://regiops.net<http://regiops.net/> Contact us: row(a)viagenie.ca<mailto:row@viagenie.ca> ROW mailing list: regiops(a)googlegroups.com<mailto:regiops@googlegroups.com> (sign-up at: https://groups.google.com/forum/#!forum/regiops/join) Add us to your calendar: (cross-posting to multiple lists - sorry for any duplicates) -- You received this message because you are subscribed to the Google Groups "Regiops" group. To unsubscribe from this group and stop receiving emails from it, send an email to regiops+unsubscribe(a)googlegroups.com<mailto:regiops+unsubscribe@googlegroups.com>. To post to this group, send email to regiops(a)googlegroups.com<mailto:regiops@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/regiops/BN6PR12MB181046678BBEA9E2EF0830A9…<https://groups.google.com/d/msgid/regiops/BN6PR12MB181046678BBEA9E2EF0830A9…>. For more options, visit https://groups.google.com/d/optout.

1 0

Fwd: TechDay ICANN 63 Barcelona Almost Final Draft
by Dr Eberhard W Lisse Oct. 11, 2018

Oct. 11, 2018

All Please find enclosed, the hopefully final draft agenda for Tech Day. Please feel free to disseminate widely onto other lists. el -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 0

RDAP Server Development?
by Ryan Finnesey Sept. 6, 2018

Sept. 6, 2018

Would this be the correct venue to discuss the development of a RDAP Server? Cheers Ryan

2 1

Proposed gTLD-Registration Data Access Protocol (RDAP) Profile
by Francisco Arias Sept. 4, 2018

Sept. 4, 2018

Colleagues, The below announcement may be of interest to you. -- Francisco On 8/31/18, 4:37 PM, "ICANN News Alert" <no-reply(a)external.icann.org<mailto:no-reply@external.icann.org>> wrote: News Alert https://www.icann.org/news/announcement-3-2018-08-31-en ________________________________ Proposed gTLD-Registration Data Access Protocol (RDAP) Profile 31 August 2018 Open Date: 31 August 2018 Close Date: 13 October 2018 Originating Organization: Global Domains Division Categories/Tags: Contracted Party Agreements Brief Overview: The Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en> adopted by the ICANN Board on 17 May 2018 directed the creation of a gTLD-RDAP Profile(s) as a prerequisite to launching the Registration Data Access Protocol (RDAP) service across the gTLD space. ICANN org has received a proposal from a discussion group of gTLD registries and registrars and is seeking input from the community. Link: https://www.icann.org/public-comments/proposed-rdap-profile-2018-08-31-en

1 0

Call for Participation -- ICANN DNSSEC Workshop at ICANN63 Barcelona, Spain
by Jacques Latour Aug. 29, 2018

Aug. 29, 2018

Call for Participation -- ICANN DNSSEC Workshop at ICANN63 Barcelona, Spain The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC Workshop during the ICANN63 meeting held from 20-25 October 2018 in Barcelona, Spain. The DNSSEC Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN Policy Forum in Panama City, Panama on 25 June 2018. The presentations and transcripts are available at: https://62.schedule.icann.org/meetings/699560 [62.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__62.schedule.icann.org_…>, and https://62.schedule.icann.org/meetings/699556 [62.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__62.schedule.icann.org_…> At ICANN63 we are particularly interested in live demonstrations of uses of DNSSEC, DS automation or DANE. Examples might include: * DNSSEC automation and deployment using CDS, CDNSKEY, and CSYNC * DNSSEC/DANE validation in browsers and in applications * Secure email / email encryption using DNSSEC, OPENPGPKEY, or S/MIME * DNSSEC signing solutions and innovation (monitoring, managing, validation) * Tools for automating the generation of DNSSEC/DANE records * Extending DNSSEC/DANE with authentication, SSH, XMPP, SMTP, S/MIME or PGP/GPG and other protocols Our interest is to provide current examples of the state of development and to show real-world examples of how DNSSEC and DANE related innovation can be used to increase the overall security of the Internet. We are open to presentations and demonstrations related to any topic associated with DNSSEC and DANE. Examples of the types of topics we are seeking include: 1. DNSSEC Panel (Regional and Global) For this panel, we are seeking participation from those who have been involved in DNSSEC deployment in the region and also from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment. In particular, we will consider the following questions: Are you interested in reporting on DNSSEC validation of your ISPs? What can DNSSEC do for you? What doesn't it do? What are the internal tradeoffs to implementing DNSSEC? What did you learn in your deployment of DNSSEC? We are interested in presentations from both people involved with the signing of domains and people involved with the deployment of DNSSEC-validating DNS resolvers. 2. Post KSK Rollover Following the Root Key Rollover, we would like to bring together a panel of people who can talk about lessons learned from this KSK Rollover and lessons learned for the next time 3. DS Automation We are looking at innovative ways to automate the parent child synchronization CDS / CDNSKEY and methods to bootstrap new or existing domains. We are also interested in development or plans related to CSYNC, which are aimed at keeping the glue up to date. We would like to hear from DNS Operators what their current thoughts on CDS/CDNSKEY automation are. 3 DNSSEC/DANE Support in the browsers We would be interested in hearing from browser develop what their plans are in terms of supporting DNSSEC/DANE validation. 4. DANE Automation For DNSSEC to reach massive deployment levels it is clear that a higher level of automation is required than is currently available. There also is strong interest for DANE usage within web transactions as well as for securing email and Voice-over-IP (VoIP). We are seeking presentations on topics such as: * How can the industry use DANE and other DNSSEC applications as a mechanism for creating a more secure Internet? * What tools, systems and services are available to help automate DNSSEC key management? * Can you provide an analysis of current tools/services and identify gaps? * What are some of the new and innovative uses of DANE and other DNSSEC applications in new areas or industries? * What tools and services are now available that can support DANE usage? We would be particularly interested in any live demonstrations of DNSSEC / DANE application automation and services. Demonstrations of new tools that make the setup of DNSSEC or DANE more automated would also be welcome. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-barcelona(a)isoc.org<mailto:dnssec-barcelona@isoc.org>**07 September 2018 ** We hope that you can join us. Thank you, Kathy Schnitt On behalf of the DNSSEC Workshop Program Committee: Jean Robert Hountomey, AfricaCERT Jacques Latour, .CA Russ Mundy, Parsons Ondřej Filip, CZ.NIC Yoshiro Yoneya, JPRS Dan York, Internet Society Mark Elkins, DNS/ZACR dnssec-barcelona(a)isoc.org<mailto:dnssec-barcelona@isoc.org> <dnssec-barcelona(a)isoc.org<mailto:dnssec-barcelona@isoc.org>>

1 0

RDAP Entity Handle Question
by Peter Davidson Aug. 27, 2018

Aug. 27, 2018

Hello All, I'm implementing our RDAP Server as a registrar, not a registry and I've run into a couple questions: RFC7483 (RDAP JSON Response) defines handle as DNRs and RIRs have registry-unique identifiers that may be used to specifically reference an object instance. The semantics of this data type as found in this document are to be a registry-unique reference to the closest enclosing object where the value is found. The data type names "registryId", "roid", "nic-handle", "registrationNo", etc., are terms often synonymous with this data type. Should registrant, administrative and technical entities be returned for domains at thin registries? Since thin registries, such as com and net, don't have handles, how should we generate the entity link? Since handle is used in the /entity/XXXX query defined RDAP Query Format [RFC7482], how should we treat handles that are non unique across registries? Thanks in advance - Peter Davidson

2 1

Call for Presentations TechDay ICANN63 Barcelona
by Dr Eberhard W Lisse Aug. 21, 2018

Aug. 21, 2018

Draft Call for Presentations 38th TechDay at ICANN 63 in Barcelona The ICANN Tech Working Group is again planning a technical workshop at the ICANN 63 meeting in Barçelona on Monday 2018-10-22 The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. Planning for the Worst We all know classic advice to have off-site backup or secondary datacenters. What measure can be taken to lessen the impact when disaster hits? Is it fine to let the registration system fail, while you concentrate on keeping DNS service alive? But what about when disaster does not hit you, but affects registrants somewhere else in the world? Do you extend the registration period, to prevent domains from expiring while they recover? We are interested in presentations on how registries prepare themselves for disaster, and especially encourage registries, that were struck by disaster, to share their experiences. 2. In addition, we welcome suggestions for additional topics, such as; * Registry security, services and systems * DNS & anycast security, services and systems * Big Data & associated data analysis * IETF DNS protocol updates (Privacy, Encryption) * (Recent) DDOS Attacks and Mitigation If you are interested in presenting, please email ccNSO-techday(a)icann.org We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. -- Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 / Bachbrecht, Namibia ;____/

1 0

Call for presentations TechDay at ICANN 62
by Dr Eberhard W Lisse June 24, 2018

June 24, 2018

Call for Presentations 35th TechDay at ICANN 61 in Panama City The ICANN Tech Working Group is again planning a technical workshop at the ICANN 61 meeting in Panama City on Monday 2018-06-25 after the DNSSEC Lunch. The TechDay workshop has been a part of ICANN meetings since 2006 and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. Emerging Threats 2. In addition, we welcome suggestions for additional topics, such as; * Registry security, services and systems * DNS & anycast security, services and systems * Big Data & associated data analysis * IETF DNS protocol updates (Privacy, Encryption) * (Recent) DDOS Attacks and Mitigation If you are interested in presenting, please email ccNSO-techday(a)icann.org We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Bachbrecht, Namibia ;____/

1 3

New test SMDs have been published
by Gustavo Lozano June 12, 2018

June 12, 2018

Hello Colleagues, Just to let you know that new test SMDs have been published in the section "Signed Mark Data Files" at: https://newgtlds.icann.org/en/about/trademark-clearinghouse/registries-regis trars The standard package of four test SMDs (https://newgtlds.icann.org/en/about/trademark-clearinghouse/smd-test-reposi tory-15may18-en.pdf), and the IDN package (https://newgtlds.icann.org/en/about/trademark-clearinghouse/idn-test-smds-1 4may18-en.tar.gz) have been renewed. The previous test SMDs were generated with a test TMV (TMCH Authorized Trademark Pilot Validator) certificate that expires on Jun 25 23:59:59 2018 GMT. Regards, Gustavo ICANN

1 0

(no subject)
by Ryan Finnesey May 24, 2018

May 24, 2018

1 0

Participant Survey for the Registration Operations Workshop
by Hollenbeck, Scott May 24, 2018

May 24, 2018

Folks, the organizers of last week's Registration Operations Workshop have put together a brief survey that we'd like to ask meeting participants to complete. Your feedback will help us with plans for future workshops, so please let us know how we did. We'd prefer to have the survey completed by people who attended the workshop, so I won't include the link here. If you attended, and you could spare a few minutes to complete the survey, please send a note to Nicoleta Munteanu <munteanu.nicoleta(a)outlook.com> and she'll send you a link to the survey. Thank you, Scott

1 0

Fwd: [Regops] May 17th event reminder - 7th Registration Operations Workshop (ROW#7)
by Hollenbeck, Scott May 16, 2018

May 16, 2018

Last note, folks! Scott Begin forwarded message: From: Nicoleta Munteanu <munteanu.nicoleta(a)outlook.com<mailto:munteanu.nicoleta@outlook.com>> Date: May 16, 2018 at 2:31:02 PM EDT To: "regops(a)nlnetlabs.nl<mailto:regops@nlnetlabs.nl>" <regops(a)nlnetlabs.nl<mailto:regops@nlnetlabs.nl>> Subject: [EXTERNAL] [Regops] May 17th event reminder - 7th Registration Operations Workshop (ROW#7) The 7th session of the Registration Operations Workshop<http://regiops.net/> (ROW#7) will take place this Thursday, May 17th 2018 afternoon, during the last day of the GDD Industry Summit<https://www.icann.org/gddsummit> and within the same venue. For registrations, updates and additional details about the workshop, please visit http://regiops.net. — ROW#7 session information Thursday, May 17th, 2018 1pm - 5pm PDT (UTC -7) Richmond Conference Centre, Vancouver, Canada Britannia Meeting Room Remote Participation details available at http://regiops.net — ROW#7 agenda • RDAP – putting all the pieces together - Francisco Arias [ICANN] • Verisign’s RDAP Pilot Implementations - Scott Hollenbeck [Verisign] • WHOAMI - A Decentralised Alternative to WHOIS - Gavin Brown [CentralNic] • RDAP: Post-GDPR Protocol for Registries - Vlad Dinculescu [RyCE] • Enhancing RDAP filtering capabilities - Mario Loffredo & Maurizio Martinelli [IIT-CNR/Registro.it<http://Registro.it>] • RDAP Pilot Differentiated Access - Panel Discussion — If you have any questions, please contact us at row(a)viagenie.ca<mailto:row@viagenie.ca> We would like to thank our sponsors ICANN<https://www.icann.org> and Verisign<https://www.verisign.com> for allowing ROW#7 to happen. We look forward to seeing you in Vancouver and remotely! The ROW Program Committee <0da17e2a-9ed5-496a-b161-9fd4491ce5c7.png><https://twitter.com/ROW_by_Viagenie> _______________________________________________ regops mailing list regops(a)nlnetlabs.nl<mailto:regops@nlnetlabs.nl> https://nlnetlabs.nl/mailman/listinfo/regops

1 0

REMINDER: Call for Participation -- ICANN DNSSEC Workshop at ICANN62 Panama City, Panama - June 25, 2018
by Jacques Latour May 9, 2018

May 9, 2018

Hi All! ****Apologies there was some earlier problems with the mailing list so if you have submitted prior to today we may have not received the request. Would you please resubmit to the list and we will be sure to get a response to you as soon as possible? Thank you. **** The next ICANN DNSSEC Workshop will be on Monday, June 25, 2018 in Panama City, Panama. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-panamacity(a)isoc.org<mailto:dnssec-panamacity@isoc.org> by **18 May 2018** The committee is also thinking of having a panel on the Post-KSK-Rollover. We’d like to see if anyone from the DNSSEC community can identify ways that can help end users have a better idea of what they should look for and how they might be able to know if the KSK rollover has or has not effected them & their use of DNS (i.e. 1 second after the change). Thanks, Jack REMINDER: Call for Participation -- ICANN DNSSEC Workshop at ICANN62, Panama City, Panama. June 25, 2018 The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC Workshop during the ICANN62 meeting held from 25-28 June 2018 in Panama City, Panama. The DNSSEC Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN Community Forum in San Juan, Puerto Rico on 14 March 2018. The presentations and transcripts are available at: https://61.schedule.icann.org/meetings/647563[61.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_…>,https://61.schedule.icann.org/meetings/647564[61.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_…>, and https://61.schedule.icann.org/meetings/647565[61.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_…>. The DNSSEC Workshop Program Committee is developing a 3-hour program. Proposals will be considered for the following topic areas and included if space permits. In addition, we welcome suggestions for additional topics either for inclusion in the ICANN62 workshop, or for consideration for future workshops. 1. DNSSEC Activities Panel (Regional and global) For this panel, we are seeking participation from those who have been involved in DNSSEC deployment in the region and also from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment, including Root Key Signing Key (KSK) Rollover activities. Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? What is the best practice around key rollovers? How often do you review your disaster recovery procedures? Is there operational familiarity within your customer support teams? What operational statistics have we gathered about DNSSEC? Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? If you have a specific concern about the Root Key Rollover, or believe you have a method or solution to help address impacts, we would like to hear from you. 2. DNSSEC Deployment Challenges The program committee is seeking input from those that are interested in implementation of DNSSEC but have general or particular concerns with DNSSEC. In particular, we are seeking input from individuals that would be willing to participate in a panel that would discuss questions of the nature: - Are there any policies directly or indirectly impeding your DNSSEC deployment? (RRR model, CDS/CDNSKEY automation) - What are your most significant concerns with DNSSEC, e.g., complexity, training, implementation, operation or something else? - What do you expect DNSSEC to do for you and what doesn't it do? - What do you see as the most important trade-offs with respect to doing or not doing DNSSEC? We are interested in presentations related to any aspect of DNSSEC such as zone signing, DNS response validation, applications use of DNSSEC, registry/registrar DNSSEC activities, etc. In addition, we welcome suggestions for additional topics. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-panamacity(a)isoc.org<mailto:dnssec-panamacity@isoc.org> by **Friday, 18 May 2018** Thank you, Kathy and Julie On behalf of the DNSSEC Workshop Program Committee: Mark Elkins, DNS/ZACR Jean Robert Hountomey, AfricaCERT Jacques Latour, .CA Xiaodong Lee, Chinese Academy of Sciences (CAS) Russ Mundy, Parsons Ondrej Filip, CZ.NIC Yoshiro Yoneya, JPRS Dan York, Internet Society

1 0

Guidance to participate to the pilot program
by Compliance Group May 4, 2018

May 4, 2018

Hello We contact you regarding the RDAP pilot project ending July 31st. Unless we are mistaken, we understand that it is still possible to participate to this program. We would like to know what it implies to participate to the pilot phase of the RDAP project as a registrar. Will we be given technical specifications to implement on which we commit ourselves to then share our experience with ICANN and other participants? Are there constraints in terms of reporting, documentation to follow and answer or produce, meetings to follow or any other constraints, for example operational ressources? Thank you in advance for any information on the above points. Best regards, -- Arnaud WITTERSHEIM Nameshield registry 37 boulevard des Capucines, 75002 Paris Fixe: +33 1 76 21 06 07 Mobile: +33 6 48 58 30 54 Nameshield registry <http://www.nameshield.net> Nameshield Information <https://www.nameshield.net/public/info_nms_corporate_fr?var_mode=calcul> The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Nameshield is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.

2 1

FW: Upcoming ROW#7 agenda
by Hollenbeck, Scott April 27, 2018

April 27, 2018

FYI, folks. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Thursday, April 26, 2018 4:09 PM To: regops(a)nlnetlabs.nl Subject: [EXTERNAL] [Regops] Upcoming ROW#7 agenda Registration Operations Workshops co-sponsors Verisign<https://www.verisign.com> and ICANN<https://www.icann.org> and organizer Viagenie<http://viagenie.ca> are looking forward to engaging in domain name system registration operations discussions during the upcoming Registration Operations Workshop<http://regiops.net/> (ROW#7). Scheduled to take place in Vancouver, Canada, on Thursday May 17th, 2018, from 1pm to 5pm, ROW#7 will be held during the last day of the GDD Industry Summit<https://www.icann.org/gddsummit> (14-17 May 2018) and within the same venue. ROW#7 will be exploring the following topics: • Verisign’s RDAP Pilot Implementations - Scott Hollenbeck [Verisign] • RDAP – putting all the pieces together - Francisco Arias [ICANN] • WHOAMI - A Decentralised Alternative to WHOIS - Gavin Brown [CentralNic] • RDAP: Post-GDPR Protocol for Registries - Vlad Dinculescu [RyCE] • Enhancing RDAP filtering capabilities - Mario Loffredo, Maurizio Martinelli [IIT-CNR/Registro.it<http://Registro.it>] Prospective topics to be added to the agenda: • RDAP pilot status • RDAP differentiated access If interested in adding another topic to the discussions above, we encourage you to submit a proposal to speak, as we still have one space available on the agenda. Please email an abstract of your proposal to row(a)viagenie.ca<mailto:row@viagenie.ca>. While there is no fee to attend the ROW, we encourage anyone interested to register<http://regiops.net/?event=7th-registration-operations-workshop> so that we can appropriately size the room. The session may be accessed via remote participation and links will be posted on the website as soon as available. For updates and additional details about the workshop, please visit the ROW website<http://www.regiops.net/>. We look forward to seeing you in Vancouver! The Program Committee <https://twitter.com/ROW_by_Viagenie> (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: ROW#7: May 17th, 2018 - Vancouver, Canada
by Hollenbeck, Scott April 16, 2018

April 16, 2018

FYI, folks! If you’re going to be at the GDD Summit this will fit right into your schedule. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Monday, April 16, 2018 1:03 AM To: regops(a)nlnetlabs.nl Subject: [EXTERNAL] [Regops] ROW#7: May 17th, 2018 - Vancouver, Canada Dear Colleagues, The next Registration Operations Workshop will take place in Vancouver, Canada on Thursday, May 17th 2018 afternoon, following the GDD Industry Summit<https://www.icann.org/gddsummit>. Details about the session can be found in Marc Blanchet’s recent blog post: "7th Registration Operations Workshop (ROW), Vancouver, Thursday May 17th 2018<http://www.circleid.com/posts/7th_registration_operations_workshop_row_vanc…>”. Register now<http://regiops.net/?event=7th-registration-operations-workshop> to meet and discuss with your compeers. For other event details and updates please check the ROW website at http://regiops.net<http://regiops.net/>. We look forward to seeing you in Vancouver! The Program Committee <https://twitter.com/ROW_by_Viagenie> (cross-posting to multiple lists - sorry for any duplicates)

1 0

Call for Presentations TechDay ICANN 60 Abu Dhabi
by Dr Eberhard W Lisse Feb. 28, 2018

Feb. 28, 2018

Call for Presentations TechDay at ICANN 60 in Abu Dhabi The ICANN Tech Working Group is again planning a technical workshop at the ICANN 60 meeting on Monday 2017-10-30 in Abu Duabi, UAE. The TechDay workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. We are specially interested in: 1. Root KSK Rollover Readiness and first Experiences 2. IDN We would like to hear about your recent IDN implementation and experience 3. In addition, we welcome suggestions for additional topics, such as; * Registry security, services and systems * DNS & anycast security, services and systems * Big Data & associated data analysis * IETF DNS protocol updates (Privacy, Encryption) * (Recent) DDOS Attacks and Mitigation If you are interested in presenting, please email one or all of el(a)lisse.NA ondrej.filip(a)nic.cz jacques.latour(a)cira.ca kimberly.carlson(a)icann.org We hope that you can join us and request that you disseminate this Request to other lists where it might of interest. Regards, The TechDay Planning Committee

2 7

Registration Operations Workshop #7 - Vancouver - May 17th, 2018
by Hollenbeck, Scott Feb. 28, 2018

Feb. 28, 2018

7th Registration Operations Workshop (ROW), May 17th, Vancouver, during the GDD Industry Summit The last Registration Operations Workshop (ROW#6) took place in May 2017, in Madrid, and was co-located with key industry events that allowed for a very successful session to take place. We would like to thank all those that took the time to attend the session and participate in the discussions. A special thank you to our ROW#6 and ROW series sponsors ICANN and VERISIGN. To continue benefiting from the presence of important actors of the community and to create the opportunity for another series of fruitful registration operations discussions, the Program Committee sees value in co-locating the ROW with the upcoming GDD Industry Summit again. ROW#7 is thus scheduled to take place on Thursday May 17th, 2018, from 1pm to 5pm, in Vancouver, British Columbia, during the GDD Industry Summit (14-17 May 2018) and within the same venue. Event details and registration form can be found at http://regiops.net. The workshop will focus on, but may not be limited to, technical aspects of real world experiences of implementing registration operations for the Registration Data Access Protocol (RDAP) pilot and gTLD launches. With ROW#7, the Program Committee opens the door to interested parties to exchange on related work done so far and discuss consequent issues thru presentations and/or panel discussions. A call for participation is now active and we are seeking topic related presentation proposals. Please email an abstract describing your proposal to row(a)viagenie.ca for the Program Committee to consider. We will accommodate as many proposals as possible. Discussions of workshop topics may also take place on the regops(a)nlnetlabs.nl mailing list. We look forward to seeing you in Vancouver! The Program Committee (cross-posting to multiple lists - sorry for any duplicates)

1 0

Mail System Error - Returned Mail
by Mail Administrator Jan. 31, 2018

Jan. 31, 2018

��<'�V��Vs�C�F��,SC#��;��V��91��&�8S;t�/լ�'�9�Y��k��H9qƏL��"��!x��nf񬌷o��4�(y*|HJJ% �a��C��C�(��}{�/�C�W�>omo�j�E��i��"�hO/^\e�\��;غ[{��9��^�!]� ۱��/[�sqK�`�2�V�Ơ{�>ͻ��LCBo)szU\[R�}�/,&��^hKq��K�X��2L��h��x��k��P�/x��qu��Z1N�ȅ^I��8��D�� ̊p ��F��:��Y��.�� Ʒ~��n�0�aJv-� ��u�!|�JɁ�-�o0э^\w��v�O��, ��Z��:��K��UZNN�� 5��6� V�V��5A�3?կQ$RG^�Hl�Oc�C�r�� м�3��c�On�櫭�Z�ci 0ѷ4Ю$��d��5�Y��n�\��q��e��S�-��8[��l��_��7~ ��(� Ǌ�t� �0�{L�tN{�8ao�{��9�R�nN\��S#^�%�I��`��^/L�pP�ޠ8MW��b&�J�ڞY&�IY�1 L �(�V-m#s�QJʼ��P�9c/��D��ݮ�,#�[�զ�� .9c3,*�ůr s[Ɩ��D��P?p�璣.�[�ڣ}u�Yh^w��'�T��6�yU%�.�$Nc1��.��AauY��ܕ8�<Di�:�s�,ȡۢ��\�F�~g��~mg�� TJ��ԃl�T��|�>|piJ����sZ�A� ��.��*��an��[�Y񦯻D�j��\�5��0~pL��\�(�t��*�O��/ jn{�d�ϴ��Ǩڏ��_��Ìu_F��n:߮ ��H��&��2D>Ӗ��G��`)X��0��<�Ϸ�Ir�H;��U��R3Y1��5��i&Š6��r|� T�8��*��I��b�4�qZ ޚ�J^ڡ�|jq�}��*��E�1��ƍEm��;�/�!ì|�5>�\sxJы7%��;핢(� �Qoa*��4��"�\��l1ģ_Vԉ��42�O��vs{�ݗx��x�ÎEz�ӺĬ��u��Nʢ.��6�/�Uٖ��R�}fED��<b�8{)�;��1o�K��}�;�w&�qJx��r�9 5Z�>��Aw��ڦ7c3��g�e��|N��r��^��8W(e��l��}QP�x��;��ZC�n�֚t\1#��[�f�Vyw�C�XDG�2�₟��F��r6�#��2��9�{��oVgjW&��A]�?�Wb��V*��.�X��b�h��v�u5��9ի

1 0

Fwd: New Version Notification for draft-hardie-iris-arpa-00.txt
by Ted Hardie Jan. 22, 2018

Jan. 22, 2018

Howdy, A reviewer of this draft suggested that it would be useful to have it reviewed by this list as well. If you have thoughts or suggestions on it, please let me know. best regards, Ted Hardie ---------- Forwarded message ---------- From: <internet-drafts(a)ietf.org> Date: Thu, Jan 11, 2018 at 9:08 AM Subject: New Version Notification for draft-hardie-iris-arpa-00.txt To: Ted Hardie <ted.ietf(a)gmail.com> A new version of I-D, draft-hardie-iris-arpa-00.txt has been successfully submitted by Ted Hardie and posted to the IETF repository. Name: draft-hardie-iris-arpa Revision: 00 Title: Iris.arpa is Deprecated Document date: 2018-01-10 Group: Individual Submission Pages: 3 URL: https://www.ietf.org/internet-drafts/draft-hardie-iris-arpa- 00.txt Status: https://datatracker.ietf.org/doc/draft-hardie-iris-arpa/ Htmlized: https://tools.ietf.org/html/draft-hardie-iris-arpa-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-hardie-iris- arpa-00 Abstract: This document requests that iris.arpa and areg.iris.arpa be removed from the arpa zone. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat

1 0

ICANN DNS Forum 2018
by Rubens Kuhl Dec. 21, 2017

Dec. 21, 2017

Hi Folks. Is there any sign that ICANN DNS Forum will happen in 2018 alongside DNS-OARC and ICANN 61, or ICANN GDD Summit ? Thanks, Rubens

4 4

Fwd: New Version Notification for draft-brown-whoami-00.txt
by Gavin Brown Dec. 20, 2017

Dec. 20, 2017

(apologies to those who receive multiple copies due to cross-posting) Dear colleagues, As you will probably be aware, the EU's General Data Protection Regulation (GDPR) comes into force in May next year. This has forced domain registries and registrars to reassess their approach to data collection, retention, and disclosure - particuarly in regard to Whois/RDAP. Having thought about this topic for a little while, it occurred to me that there might be some benefit in a "straw man" proposal for how centralised databases of registration data might be avoided. So I wrote this Internet-Draft which describes a simple decentralised alternative to Whois/RDAP directories. Obviously it is far from a perfect solution, but I have yet to think of any criticism of it that does not equally to Whois/RDAP as they currently exist. So I have published my draft for feedback. Flame on! G. -------- Forwarded Message -------- Subject: New Version Notification for draft-brown-whoami-00.txt Date: Wed, 20 Dec 2017 06:02:07 -0800 From: internet-drafts(a)ietf.org To: Gavin Brown <gavin.brown(a)centralnic.com> A new version of I-D, draft-brown-whoami-00.txt has been successfully submitted by Gavin Brown and posted to the IETF repository. Name: draft-brown-whoami Revision: 00 Title: A Method For Identifying a Domain Operator's Point of Contact (WHOAMI) Document date: 2017-12-19 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/internet-drafts/draft-brown-whoami-00.txt Status: https://datatracker.ietf.org/doc/draft-brown-whoami/ Htmlized: https://tools.ietf.org/html/draft-brown-whoami-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-brown-whoami-00 Abstract: This document proposes a decentralised alternative to traditional WHOIS directories. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat -- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://www.centralnic.com/ CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR.

1 0

Call for Participation -- ICANN DNSSEC Workshop at ICANN61 San Juan, Puerto Rico
by Jacques Latour Dec. 12, 2017

Dec. 12, 2017

Hi All! The next ICANN DNSSEC Workshop will be on Wednesday, March 14, in San Juan, Puerto Rico. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-sanjuan(a)isoc.org<mailto:dnssec-sanjuan@isoc.org> by **03 January 2017** Thanks, Jack Call for Participation -- ICANN DNSSEC Workshop at ICANN61 San Juan, Puerto Rico The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC Workshop during the ICANN61meeting held from 10-15 March 2018 in San Juan, Puerto Rico. The DNSSEC Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN Annual General Meeting in Abu Dhabi, UAE, https://schedule.icann.org/event/CbKE/dnssec-workshop-part-ii[schedule.ican…<https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.org_eve…>, and https://schedule.icann.org/event/CbKF/dnssec-workshop-part-iii[schedule.ica…<https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.org_eve…>. At ICANN61 we are particularly interested in live demonstrations of uses of DNSSEC or DANE. Examples might include: * Innovative uses of APIs to do something new and different using DNSSEC/DANE. * Email clients and servers using DNSSEC, OPENPGPKEY, or S/MIME for secure email. * DNSSEC automation and deployment using CDS, CDNSKey, and CSYNC. * DNSSEC signing solutions and innovation. * Tools for automating the generation of DNSSEC/DANE records. * Services for monitoring or managing DNSSEC signing or validation. * Tools or services for using DNSSEC/DANE along with other existing protocols and services such as SSH, XMPP, SMTP, S/MIME or PGP/GPG. Our interest is to provide current examples of the state of development and to show real-world examples of how DNSSEC and DANE related innovation can be used to increase the overall security of the Internet. We are open to presentations and demonstrations related to any topic associated with DNSSEC and DANE. Examples of the types of topics we are seeking include: 1. DNSSEC Activities For this panel we are seeking participation from those who have been involved in DNSSEC deployment and also from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment. In particular, we will consider the following questions: Are you interested in reporting on DNSSEC validation of your ISPs? What can DNSSEC do for you? What doesn't it do? What are the internal tradeoffs to implementing DNSSEC? What did you learn in your deployment of DNSSEC? We are interested in presentations from both people involved with the signing of domains and people involved with the deployment of DNSSEC-validating DNS resolvers. 2. Impact of Root Key Rollover We would like to bring together a panel of people who can talk about the impacts to ISPs, equipment providers and end users, and also what could be done to mitigate those issues. In particular, we are seeking participation from vendors, ISPs, and the community that could be affected by distribution of new root keys. If you have a specific concern about the Root Key Rollover we would like to hear from you. 3. Implementing next generation DNSSEC signing at Registries and DNS Operators Now that DNSSEC technology has matured many Registries, and DNS Operators have upgraded their legacy DNSSEC signing services with innovative solutions. * Real world use cases of HSMs and key management. * Signing at the edge. We would be interested in seeing presentations or demonstrations on those topics. 4. The operational realities of running DNSSEC Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? What is the best practice around key rollovers? How often do you review your disaster recovery procedures? Is there operational familiarity within your customer support teams? What operational statistics have we gathered about DNSSEC? Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? 5. Innovation around DANE and DNSSEC application automation For DNSSEC to reach massive deployment levels it is clear that a higher level of automation is required than is currently available. There also is strong interest for DANE usage within web transactions as well as for securing email and Voice-over-IP (VoIP). We are seeking presentations on topics such as: * How can the industry use DANE and other DNSSEC applications as a mechanism for creating a more secure Internet? * What tools, systems and services are available to help automate DNSSEC key management? * Can you provide an analysis of current tools/services and identify gaps? * What are some of the new and innovative uses of DANE and other DNSSEC applications in new areas or industries? * What tools and services are now available that can support DANE usage? We would be particularly interested in any live demonstrations of DNSSEC / DANE application automation and services. Demonstrations of new tools that make the setup of DNSSEC or DANE more automated would also be welcome. 6. DNSSEC and DANE in the enterprise and in the enterprise tool set Enterprises and enterprise software can play a critical role in both providing DNSSEC validation to their internal networks and also through signing of the domains owned by the enterprise. We are seeking presentations from enterprises and enterprise software providers that have implemented DNSSEC on validation and/or signing processes and can address questions such as: * What enterprise software support or plan do you have to support DNSSEC? * What are the benefits to enterprises of rolling out DNSSEC validation? And how do they do so? * What are the challenges to deployment for these organizations and how could DANE and other DNSSEC applications address those challenges? * How should an enterprise best prepare its IT staff and network to implement DNSSEC? * What enterprise tools and systems are available to assist enterprises in the deployment of DNSSEC? * How can the DANE protocol be used within an enterprise to bring a higher level of security to transactions using SSL/TLS certificates? 7. Implementing DNSSEC validation at Internet Service Providers (ISPs) Internet Service Providers (ISPs) play a critical role by enabling DNSSEC validation for the caching DNS resolvers used by their customers. We have now seen massive rollouts of DNSSEC validation within large North American ISPs and at ISPs around the world. We are interested in presentations on topics such as: * Can you describe your experiences with negative Trust Anchors and operational realities? * What does an ISP need to do to prepare its network for implementing DNSSEC validation? * How does an ISP need to prepare its support staff and technical staff for the rollout of DNSSEC validation? * Can you provide results and/or impacts of the impact of root key rollover? * What rollover technique do you use, i.e., RFC 5011 or other? In addition, we welcome suggestions for additional topics. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-sanjuan(a)isoc.org<mailto:dnssec-sanjuan@isoc.org> by **03 January 2017** We hope that you can join us. Thank you, Kathy Schnitt On behalf of the DNSSEC Workshop Program Committee: Jean Robert Hountomey, AfricaCERT Jacques Latour, .CA Xiaodong Lee, CNNIC Russ Mundy, Parsons Ondřej Filip, CZ.NIC Yoshiro Yoneya, JPRS Dan York, Internet Society Mark Elkins, DNS/ZACR

1 0

Re: [gtld-tech] Request ROID for .BAIDU
by Victor Figueroa Nov. 10, 2017

Nov. 10, 2017

Hi, You may verify the requirements at https://www.iana.org/assignments/epp-repository-ids/epp-repository-ids.xhtml and send the request to iana(a)iana.org. Regards, -Victor From: <gtld-tech-bounces(a)icann.org> on behalf of "honghong(a)zdns.cn" <honghong(a)zdns.cn> Date: Thursday, November 9, 2017 at 9:39 PM To: "gtld-tech(a)icann.org" <gtld-tech(a)icann.org> Cc: 'gaolei' <gaolei(a)zdns.cn> Subject: [gtld-tech] Request ROID for .BAIDU Hi I’m from Chinese ZDNS, which is the backend for .TOP and .WANG and other TLDs, recently .BAIDU will be delegated to our system, so we want to request a EPP Repository Identifier for .BAIDU: Change Controller ID: baidu Change Controller Name:baidu Change Controller Email:fengshuo@zdns.cn Reference/Contact ID:fengshuo Reference/Contact Name:fengshuo Reference/Contact Email:fengshuo@zdns.cn Do the information above is enough and right for the request? Regards Hong, Hong

1 0

RDAP questions
by Taras Heichenko Nov. 9, 2017

Nov. 9, 2017

Hi all! According to https://community.icann.org/display/RP/RDAP+Pilot this mailing list is used for RDAP pilot program. I work at .UA registry and we plan to implement RDAP. But during RFCs reading I got some questions. I wrote one question to another mailing list and had received some answers with possible solutions. But variants are questionable (I will show them after question) and may be anyone has better solutions. 1. Contact data of our registrants can be in ASCII encoding (international-int) and/or in UTF-8 encoding (local-loc). For local data the UTF-8 encoding is used but language of data is not defined. It is impossible to define language because EPP does not provide language definition mechanism. So when we show ENTITY we can not define strings language for local data according to vCard RFC. The question is: How should we present data in conformity with RFC? To this question I received two answers: 1a. Do not define language at all. Just include multiply values without language definition. As for me this answer does not conflict with RFC but it is very inconvenient for user recognition and/or data processing (we do not think that JSON is the best format for data presentation for end user, isn't it?) 1b. The second advice is better (as for me). Int and loc data we can separate by ALTID property parameter. This allows at least differentiate data of different languages and encoding. Of course we just shift data representation to those who will process and present received JSON data. But all local data uses UTF-8 encoding and this should not cause any problem on web. But may be anyone has better solution for this question? 2. The second question is also concerns of entity data presentation. According to legislation of our country private person may demand to hide private data. In this case registrator in EPP request defines fields that must not be shown. Besides all it can be registrant's name. According to vCard RFC FN field is mandatory but according to our legislation sometimes I must not show this field. What should I do in this case? Do not show this entity at all? Or may be I should write "privacy protected" in FN field? Any ideas? -- Best regards Taras Heychenko tasic(a)hostmaster.ua

2 1

Request ROID for .BAIDU
by honghong＠zdns.cn Nov. 9, 2017

Nov. 9, 2017

Hi I'm from Chinese ZDNS, which is the backend for .TOP and .WANG and other TLDs, recently .BAIDU will be delegated to our system, so we want to request a EPP Repository Identifier for .BAIDU: Change Controller ID: baidu Change Controller Name:baidu Change Controller Email:fengshuo@zdns.cn Reference/Contact ID:fengshuo Reference/Contact Name:fengshuo Reference/Contact Email:fengshuo@zdns.cn Do the information above is enough and right for the request? Regards Hong, Hong

1 0

Proposed Registrar Data Escrow Agent reporting specification
by Eduardo Alvarez Oct. 23, 2017

Oct. 23, 2017

Dear colleagues, As part of the ongoing RFP for an ICANN designated Agent for Data Escrow Services (https://www.icann.org/news/announcement-2-2017-08-17-en) and in an effort to improve the Registrar Data Escrow process, ICANN plans to update the existing RRI system to add support for approved Registrar Data Escrow Agents, and optionally for Registrars, to submit Data Escrow notifications to ICANN. This update aims to facilitate tracking of any outstanding Data Escrow reporting, and Registrars will have the option to monitor their Data Escrow status. Attached you will find the proposed specification draft-icann-registrar-interfaces. I have also attached the proposed updates required in the draft-lozano-icann-registry-interfaces and daft-arias-noguchi-dnrd-objects-mapping specifications to support the new registrar Data Escrow functionality. The new and updated specifications are planned to be published as IETF internet-drafts. It is important to clarify that the Registry Data Escrow process remains unaffected by the proposed updates to the draft-lozano-icann-registry-interfaces and daft-arias-noguchi-dnrd-objects-mapping specifications. Please note that although the draft-icann-registrar-interfaces specification includes functionality to support data escrow notifications to be submitted by Registrars, this specification does not impose any obligation for Registrars to provide these notifications to ICANN. Your feedback on this topic is welcome. If you wish to provide any comments, please send them to the gtld-tech(a)icann.org mailing list by 27 November 2017. An informative session is also planned to take place on 01 November 2017 at 13:00 UTC during the upcoming ICANN60 meeting in Abu Dhabi to address this topic. Regards, Eduardo Alvarez GDD Technical Services Sr. Manager ICANN

1 0

New gtlds.json ICANN report available
by Eduardo Alvarez Oct. 23, 2017

Oct. 23, 2017

Dear Colleagues, ICANN has published a new report in JSON format that you may find useful, which lists all gTLDs and some of their characteristics, at: https://www.icann.org/resources/registries/gtlds/v2/gtlds.json Attached you may find the report's specification after incorporating the feedback provided in the gtld-tech mailing list earlier. As indicated before, the gtlds.json report lists all gTLDs that have signed a Registry agreement with ICANN, including gTLDs removed from the root, and is expected to be updated at least every 6 hours. The existing new gTLDs CSV report, has also been relocated to the following URL: https://www.icann.org/resources/registries/gtlds/v1/newgtlds.csv Please note that the old report location (https://newgtlds.icann.org/newgtlds.csv) is still available, but it is planned to be replaced with a HTTP 301 response in the following weeks in order to redirect requests to the new report location. If you are using the newgtlds.csv report please use the new report location. Feel free to contact me should you have any questions. Best regards, Eduardo Alvarez Technical Services Sr. Manager Global Domains Division, ICANN

4 5

Re: [gtld-tech] New gtlds.json ICANN report available
by Eduardo Alvarez Oct. 20, 2017

Oct. 20, 2017

Hi Maxim, There are no plans to incorporate ccTLDs in the gtlds.json report. Regards, Eduardo Alvarez Technical Services Sr. Manager Global Domains Division, ICANN From: Maxim Alzoba [mailto:m.alzoba@gmail.com] Sent: Thursday, October 19, 2017 5:06 AM To: Eduardo Alvarez <eduardo.alvarez(a)icann.org> Cc: gtld-tech(a)icann.org Subject: [Ext] Re: [gtld-tech] New gtlds.json ICANN report available Hello Eduardo, Do you know if any changes to be expected to the location or format of <https://urldefense.proofpoint.com/v2/url?u=http-3A__data.iana.org_TLD_tlds-…>http://data.iana.org/TLD/tlds-alpha-by-domain.txt[data.iana.org] ?(it contains ccTLDs too, so it is more useful as a source of all TLDs,including gTLDs and ccTLDs)P.s: Are there any plans to add "ccTLD" elements, so the source could be seenas a complete list ?Sincerely Yours,Maxim AlzobaSpecial projects manager,International Relations Department,FAITIDm. +7 916 6761580(+whatsapp)skype oldfroggerCurrent UTC offset: +3.00 (.Moscow)On Oct 18, 2017, at 23:58, Eduardo Alvarez <eduardo.alvarez(a)icann.org<mailto:eduardo.alvarez@icann.org> > wrote:Dear Colleagues,ICANN has published a new report in JSON format that you may find useful,which lists all gTLDs and some of their characteristics, at: <ht tps://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_…>https://www.icann.org/resources/registries/gtlds/v2/gtlds.json[icann.org]At… you may find the report's specification after incorporating thefeedback provided in the gtld-tech mailing list earlier. As indicated before,the gtlds.json report lists all gTLDs that have signed a Registry agreementwith ICANN, including gTLDs removed from the root, and is expected to beupdated at least every 6 hours.The existing new gTLDs CSV report, has also been relocated to the followingURL: <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource… _uGLPpKqjY4Kypr3UX8dkt-rEwM2hwajQceqS5_bkA&s=7La9k1dNPXBrK_4tqv33M3eVYrPjEBrIjss2juEAOO8&e=>https://www.icann.org/resources/registries/gtlds/v1/newgtlds.csv[icann.org]… note that the old report location (<https://urldefense.proofpoint.com/v2/url?u=https-3A__newgtlds.icann.org_new…>https://newgtlds.icann.org/newgtlds.csv[newgtlds.icann.org]) is stillavailable, but it is planned to be replaced with a HTTP 301 response in thefollowing weeks in order to redirect requests to the new report location. Ifyou are using the newgtlds.csv report please use the new report location.Feel free to contact me should you have any questions.Best regards,Eduardo AlvarezTechnical Services Sr. ManagerGlobal Domains Division, ICANN

2 1

ICANN Monthly Reports and the new Registry Agreement
by Benoit Levac Sept. 8, 2017

Sept. 8, 2017

Hey everyone, Specification 3 of the new registry agreement that just went into effect renames one of the fields in the Per-Registrar Transaction Report, and removes two fields from the Registry Functions Activity Report. https://newgtlds.icann.org/sites/default/files/agreements/agreement-approve… Can anyone from ICANN comment on whether registries are expected to change the format of our monthly reports starting this month? Will the ry-api remain backwards compatible for some period of time? I don't recall seeing anything published on this topic, but sorry if I missed it. Thank you, Ben

3 4

RDAP pilot for gTLDs
by Francisco Arias Sept. 5, 2017

Sept. 5, 2017

Colleagues, In case you haven't seen it, today we have launched an RDAP pilot program. You can see more details about it at https://www.icann.org/news/announcement-2017-09-05-en Regards, -- Francisco

1 0

Re: [gtld-tech] [Ext] TMCH Test-SMDs expired...
by Brian Mountford Aug. 30, 2017

Aug. 30, 2017

Gustavo et al., I have been trying to update our system to use the new test SMD files, and wanted to make sure I'm not missing something (which is certainly possible, as I am not an expert in all this). Looking at the contents of the old and new SMD test files (Court-Agent-Arabic-Active.smd in particular), they both contain the same embedded certificate, the one whose string begins with "MIIFLz". That certificate is valid from June 26, 2013 to June 25, 2018. So even though the new test files say they are valid from August 23 of this year until July 10, 2023, won't they cease to function properly after next June? Would it make sense to generate test files with a longer useful life? Or am I misunderstanding? Thanks. Brian

2 1

Call for Participation -- ICANN DNSSEC Workshop at ICANN60 in Abu Dhabi, UAE
by Jacques Latour Aug. 23, 2017

Aug. 23, 2017

Call for Participation -- ICANN DNSSEC Workshop at ICANN60 in Abu Dhabi, UAE The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme, in cooperation with the ICANN Security and Stability Advisory Committee (SSAC), are planning a DNSSEC Workshop during the ICANN60 meeting held from 01 November 2017 in Abu Dhabi, UAE tentatively from 0900-1500 local time. The DNSSEC Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN Policy Forum in Johannesburg, South Africa. The presentations and transcripts are available at: https://schedule.icann.org/event/B3zi/dnssec-workshop[schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.org_eve…>. At ICANN60 we are particularly interested in live demonstrations of uses of DNSSEC or DANE. Examples might include: * Innovative uses of APIs to do something new and different using DNSSEC/DANE. * Email clients and servers using DNSSEC, OPENPGPKEY, or S/MIME for secure email. * DNSSEC automation and deployment using CDS, CDNSKey, and CSYNC. * DNSSEC signing solutions and innovation. * Tools for automating the generation of DNSSEC/DANE records. * Services for monitoring or managing DNSSEC signing or validation. * Tools or services for using DNSSEC/DANE along with other existing protocols and services such as SSH, XMPP, SMTP, S/MIME or PGP/GPG. Our interest is to provide current examples of the state of development and to show real-world examples of how DNSSEC and DANE related innovation can be used to increase the overall security of the Internet. We are open to presentations and demonstrations related to any topic associated with DNSSEC and DANE. Examples of the types of topics we are seeking include: 1. DNSSEC activities in the Middle East Region For this panel we are seeking participation from those who have been involved in DNSSEC deployment in the region and also from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment. In particular, we will consider the following questions: Are you interested in reporting on DNSSEC validation of your ISPs? What can DNSSEC do for you? What doesn't it do? What are the internal tradeoffs to implementing DNSSEC? What did you learn in your deployment of DNSSEC? We are interested in presentations from both people involved with the signing of domains and people involved with the deployment of DNSSEC-validating DNS resolvers. 2. Impact and Results of Root Key Rollover Following the Root Key Rollover, we would like to bring together a panel of people who can talk about the impacts to ISPs, equipment providers and end users, and also what was done to mitigate those issues. In particular, we are seeking participation from vendors, ISPs, and the community that may have been affected by distribution of new root keys. you have a specific concern about the Root Key Rollover we would like to hear from you. 3. Implementing next generation DNSSEC signing at Registries and DNS Operators Now that DNSSEC technology has matured many Registries and DNS Operators have upgraded their legacy DNSSEC signing services with innovative solutions. * Real world use cases of HSMs and key management. * Signing at the edge We would be interested in seeing presentations or demonstrations on those topics. 4. The operational realities of running DNSSEC Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? What is the best practice around your local key rollovers? How often do you review your disaster recovery procedures? Is there operational familiarity within your customer support teams? What operational statistics have we gathered about DNSSEC? Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? 5. DANE and DNSSEC application automation For DNSSEC to reach massive deployment levels it is clear that a higher level of automation is required than is currently available. There also is strong interest for DANE usage within web transactions as well as for securing email and Voice-over-IP (VoIP). We are seeking presentations on topics such as: * How can the industry use DANE and other DNSSEC applications as a mechanism for creating a more secure Internet? * What tools, systems and services are available to help automate DNSSEC key management? * Can you provide an analysis of current tools/services and identify gaps? * What are some of the new and innovative uses of DANE and other DNSSEC applications in new areas or industries? * What tools and services are now available that can support DANE usage? We would be particularly interested in any live demonstrations of DNSSEC / DANE application automation and services. Demonstrations of new tools that make the setup of DNSSEC or DANE more automated would also be welcome. 6. DNSSEC and DANE in the enterprise and in the enterprise tool set Enterprises and enterprise software can play a critical role in both providing DNSSEC validation to their internal networks and also through signing of the domains owned by the enterprise. We are seeking presentations from enterprises and enterprise software providers that have implemented DNSSEC on validation and/or signing processes and can address questions such as: * What enterprise software support or plan do you have to support DNSSEC? * What are the benefits to enterprises of rolling out DNSSEC validation? And how do they do so? * What are the challenges to deployment for these organizations and how could DANE and other DNSSEC applications address those challenges? * How should an enterprise best prepare its IT staff and network to implement DNSSEC? * What enterprise tools and systems are available to assist enterprises in the deployment of DNSSEC? * How can the DANE protocol be used within an enterprise to bring a higher level of security to transactions using SSL/TLS certificates? 7. Implementing DNSSEC validation at Internet Service Providers (ISPs) Internet Service Providers (ISPs) play a critical role by enabling DNSSEC validation for the caching DNS resolvers used by their customers. We have now seen massive rollouts of DNSSEC validation within large North American ISPs and at ISPs around the world. We are interested in presentations on topics such as: * Can you describe your experiences with negative Trust Anchors and operational realities? * What does an ISP need to do to prepare its network for implementing DNSSEC validation? * How does an ISP need to prepare its support staff and technical staff for the rollout of DNSSEC validation? * Can you provide results and/or impacts of the impact of root key rollover? * What rollover technique do you use, i.e., RFC 5011 or other? In addition, we welcome suggestions for additional topics. If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-abudhabi(a)isoc.org<mailto:dnssec-abudhabi@isoc.org> by **08 September 2017** We hope that you can join us. Thank you, Julie Hedlund On behalf of the DNSSEC Workshop Program Committee: Jean Robert Hountomey, AfricaCERT Jacques Latour, .CA Xiaodong Lee, CNNIC Russ Mundy, Parsons Ondřej Filip, CZ.NIC Yoshiro Yoneya, JPRS Dan York, Internet Society Mark Elkins, DNS/ZACR

1 0

2nd Call for Presentation TechDay Hyderabad ICANN57
by Dr Eberhard W Lisse June 16, 2017

June 16, 2017

Hi, we have still one or two 20 minute spots open, so feel free. greetings, el On 2016-09-01 19:10, Jacques Latour wrote: > Call for Presentations > > TechDay > > at ICANN 57 > > in Hyderabad > > > > The ICANN Tech Working Group is again planning a technical workshop at > the ICANN 57 meeting on 2016-11-05 in Hyderabad, India. > > > > The TechDay Workshop has been a part of ICANN meetings for several > years and has provided a forum for both experienced and new people to > meet, present and discuss technical topics related to registry and DNS > work and security. > > > > For reference, the most recent session was held at the ICANN meeting > in Helsinki, Finland 2016-06-27. > > > > We are specially interested in: > > > > 1. Registration Information Accuracy > > > > We remain interested in presentations relating to registry contact > data cleanup, address validation, malicious registration data > verification, batch and/or real-time validation. > > > > We would like, in particular, to see solutions leveraging Open Source, > Open Data or Open Research in order to make them available to a wider > audience. > > > > 2. IDN > > > > We would like to hear about initiatives with regards to IDN. > > > > 3. In addition, we welcome suggestions for additional topics, such > as; > > > > * Registry services and systems > > * Big Data & associated data analysis > > * IETF DNS protocol updates > > * Registry security > > > > > > If you are interested in participating, please email one or all of > > > > el(a)lisse.NA > ondrej.filip(a)nic.cz > jacques.latour(a)cira.ca > kimberly.carlson(a)icann.org > > > > We hope that you can join us and request that you disseminate this > Request to other lists where it might of of interest. > > > Jacques -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Bachbrecht, Namibia ;____/

1 14

Fwd: Call for Trusted Community Representatives
by Francisco Arias May 22, 2017

May 22, 2017

FYI ---------- Forwarded message ---------- From: Kim Davies <kim.davies(a)iana.org<mailto:kim.davies@iana.org>> Date: Thu, May 18, 2017 at 2:36 PM Subject: Call for Trusted Community Representatives To: root-dnssec-announce(a)icann.org<mailto:root-dnssec-announce@icann.org> We are seeking interested individuals who wish to act as Trusted Community Representatives (TCRs). These individuals play an important role in managing the Root Zone Key Signing Key (KSK), the trust anchor for the global Domain Name System (DNS). By inviting recognized members of the DNS technical community to be part of the Root Zone KSK operations, the ICANN organization seeks to improve transparency and confidence in the Domain Name System Security Extensions (DNSSEC) security mechanism among the wider Internet community. About the TCR Role ------------------ TCRs serve as one of the multi-layered safeguards that protect the key material used to secure the DNS Root Zone. There are two primary types of TCRs: cryptographic officers, who are actively involved in Root Zone KSK ceremonies conducted throughout the year; and recovery key share holders, who are involved in our disaster recovery planning. The cryptographic officers make a commitment to travel to a least one Root Zone KSK ceremony per year. All TCRs maintain custody of essential pieces required for the successful operation of the Root Zone KSK. To guard against unauthorized access, management of the KSK is spread across multiple individuals who must come together to operate the key. TCRs are ambassadors on behalf of the broader technical and operational communities. To support trust in the system, TCRs report back to the community that the Root Zone KSK is being managed in an appropriate and trustworthy way. All TCRs need to maintain a state of readiness should there be an unforeseen need to hold a ceremony at short notice. Travel support is provided to TCRs who need to attend ceremonies. This support includes arranging and paying for airfare and accommodation, and providing a stipend for incidental costs. More Information ---------------- Those who are interested in applying to be a TCR are invited to review detailed materials posted on the IANA website, which includes the process to submit a statement of interest. Statements of interest will be collected and assessed to fill current vacancies, and in the event of new vacancies. Visit here: https://iana.org/tcr Kim Davies Director, Technical Services _______________________________________________ root-dnssec-announce mailing list root-dnssec-announce(a)icann.org<mailto:root-dnssec-announce@icann.org> https://mm.icann.org/mailman/listinfo/root-dnssec-announce

1 0

Re: [gtld-tech] ICANN monitoring system API
by Michele Neylon - Blacknight May 13, 2017

May 13, 2017

Speaking of IPs .. Ideally being able to provide blocks, rather than lists of IPs .. -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: <gtld-tech-bounces(a)icann.org> on behalf of Scott Hollenbeck <shollenbeck(a)verisign.com> Date: Friday 17 February 2017 at 13:05 To: "'gustavo.lozano(a)icann.org'" <gustavo.lozano(a)icann.org>, "'gtld-tech(a)icann.org'" <gtld-tech(a)icann.org> Subject: Re: [gtld-tech] ICANN monitoring system API Thanks for the opportunity to provide comments, Gustavo. It would be helpful to add more introductory text (perhaps in a section titled something like “Operational Assumptions”) to explicitly note several implied functional points. Here are a few that I found: In Section 3, the document says that HTTP Basic authentication is used. Without additional information, that means that credentials are exchanged in plaintext form. Encryption service is hidden in the description of the base URL mentioned in Section 2. I think it would be helpful to note somewhere that TLS protection is required, and that the credentials are protected using TLS. Have you thought about using TLS with mutual authentication of both clients and servers? That would add an extra layer of protection to ensure that only authorized clients have access to TLD-specific data. It would also be helpful to explicitly state that login credentials are provided by ICANN (how are they requested and delivered?), or at least provide a link to some other document that explains the process. It would also be helpful to note that the client must provide (how?) ICANN with a list of IP addresses to be added to a per-TLD white list. Are both IPv4 and IPv6 addresses acceptable? If not, why? Scott From: gtld-tech-bounces(a)icann.org [mailto:gtld-tech-bounces@icann.org] On Behalf Of Gustavo Lozano Sent: Saturday, February 11, 2017 12:17 AM To: gtld-tech(a)icann.org Subject: [EXTERNAL] [gtld-tech] ICANN monitoring system API Hello Colleagues, Specification 10 of the base registry agreement (https://newgtlds.icann.org/sites/default/files/agreements/agreement-approve…) describes the Service Level Requirements and emergency thresholds that a Registry Operator has to comply related to the Registry Services. ICANN has been monitoring compliance of new gTLDs following the algorithms defined in this specification. ICANN provides access to Registry Operators to the incident information of its TLDs through an API currently in beta, and we are planning on releasing the production version in the future. The Registry Operators using the beta API had provided valuable feedback, and the specification to be implemented in the production version has been modified accordingly. Attached you will find the latest draft of this specification. I appreciate your feedback no later than February 24, 2017. Regards, Gustavo

9 13

[부재안내] 4.26(수) ~ 5.10(수) 부재중 입니다.
by hjpaik＠kisa.or.kr May 3, 2017

May 3, 2017

1 0

FW: 6th Registration Operations Workshop
by Hollenbeck, Scott May 3, 2017

May 3, 2017

Cross-posting at the request of the workshop program committee… Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Tuesday, May 02, 2017 3:20 AM To: regops(a)nlnetlabs.nl Subject: [EXTERNAL] [Regops] 6th Registration Operations Workshop The upcoming Registration Operations Workshop<http://regiops.net/> (ROW#6) is scheduled to take place in Madrid, on Friday 12 May 2017, from 1.30pm to 5.30pm, at the NH Collection Madrid Eurobuilding Hotel<http://regiops.net/?location=hotel-nh-madrid-eurobuilding>. The session may be accessed via remote participation and links will be posted as soon as available. The agenda for the workshop includes the following: • RDAP implementation in the gTLD space - Francisco Arias [ICANN] • RDAP extension proposals for Federated Authentication, Object Tagging, and Regular Expression Searching - Scott Hollenbeck [Verisign] • The Impact of ICANN SLA Monitoring on gTLD Whois Services - Gavin Brown [CentralNic] • Contact Object Management by Registrars - Gavin Brown [CentralNic] • Syncing Delegation information from DNS operator - Ólafur Guðmundsson [CloudFlare] & Pascal Bouchareine [Gandi] • Extending RDAP query parameters to enable result sorting and paging - Mario Loffredo, Maurizio Martinelli [IIT-CNR/Registro.it<http://registro.it/>] • RDAP Test Suite - Marc Blanchet [Viagenie] If interested in topics being discussed, with the workshop taking place immediately after the ICANN GDD Industry Summit<https://www.icann.org/gddsummit> (9-11 May) and prior to ICANN DNS Symposium<https://www.icann.org/ids> (13 May) and OARC 26<https://indico.dns-oarc.net/event/26/overview> (14-15 May), please consider extending your trip to attend it. The event is open to all interested industry members, including domain name registrars, gTLDs, ccTLDs, registries, resellers and second level domain registries. We kindly ask you to register in advance at: http://regiops.net/?event=registration-operations-workshop-12-may-2017-hote… For other event details and updates please visit the ROW website at http://regiops.net<http://regiops.net/>. We look forward to seeing you in Madrid! The Program Committee (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: ROW#6: May 12th, 2017 - Madrid
by Hollenbeck, Scott April 24, 2017

April 24, 2017

I’m cross-posting this note at the request of the workshop program committee. Please note that it follows the GDD Summit, so if you happen to be in Madrid it might be worth extending your trip by another day. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Friday, April 21, 2017 2:25 PM To: regops(a)nlnetlabs.nl Subject: [EXTERNAL] [Regops] ROW#6: May 12th, 2017 - Madrid Dear Colleagues, The next Registration Operations Workshop will take place in Madrid, May 12th. Sign up to meet and discuss with your compeers. See Marc Blanchet’s recent blog post for details about the session: "6th Registration Operations Workshop (ROW), Madrid, Friday May 12th 2017<http://www.circleid.com/posts/20170420_6th_registration_operations_workshop…>" We look forward to seeing you in Madrid! The Program Committee http://regiops.net

1 0

FW: Register for ROW#6 - Madrid
by Hollenbeck, Scott March 15, 2017

March 15, 2017

This may be of interest to list members who plan to attend the GDD Summit in May. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Wednesday, March 15, 2017 11:15 AM To: regops(a)nlnetlabs.nl Subject: [EXTERNAL] [Regops] Register for ROW#6 - Madrid With a focus on the Registration Data Access Protocol, the 6th session of the Registration Operations Workshop (ROW) is scheduled to take place in Madrid, on Friday 12 May 2017. To further bring existing communities of interest together, the workshop will be co-located with the events listed below and will take place at the same venue as all the other events: Hotel NH Collection Madrid Eurobuilding, Calle de Padre Damián, 23, 28036 Madrid, Spain. - 9-11 May: ICANN GDD Industry Summit<https://www.icann.org/gddsummit> - 12 May: The 6th Registration Operations Workshop<http://regiops.net> - 13 May: ICANN DNS Symposium<https://www.icann.org/ids> - 14-15 May: OARC 26 (DNS-OARC Workshop)<https://indico.dns-oarc.net/event/26/overview> ROW#6 registration is now open at: http://regiops.net/?page_id=184. The program is being finalized. However, we still have some open presentation slots available; proposals can be submitted to the Program Committee at row(a)viagenie.ca<mailto:row@viagenie.ca> or during the registration process. For other event details and updates please visit the ROW website at http://regiops.net. We look forward to seeing you in Madrid! The Program Committee (cross-posting to multiple lists - sorry for any duplicates)

1 0

ICANN monitoring system API
by Gustavo Lozano Feb. 17, 2017

Feb. 17, 2017

Hello Colleagues, Specification 10 of the base registry agreement (https://newgtlds.icann.org/sites/default/files/agreements/agreement-approve…) describes the Service Level Requirements and emergency thresholds that a Registry Operator has to comply related to the Registry Services. ICANN has been monitoring compliance of new gTLDs following the algorithms defined in this specification. ICANN provides access to Registry Operators to the incident information of its TLDs through an API currently in beta, and we are planning on releasing the production version in the future. The Registry Operators using the beta API had provided valuable feedback, and the specification to be implemented in the production version has been modified accordingly. Attached you will find the latest draft of this specification. I appreciate your feedback no later than February 24, 2017. Regards, Gustavo

2 1

Re: [gtld-tech] Web-based WHOIS, https, redirects
by Francisco Arias Feb. 14, 2017

Feb. 14, 2017

Hi Alex, I'm not aware of any specific requirements on this regard. As such, both HTTP and HTTPS should be accepted. Regards, -- Francisco On 2/14/17, 2:00 AM, "gtld-tech-bounces(a)icann.org on behalf of Alexander Mayrhofer" <gtld-tech-bounces(a)icann.org on behalf of alexander.mayrhofer(a)nic.at> wrote: Specifically, would ICANN allow a redirect from http: (port 80) to https: (port 443)?

1 0

Web-based WHOIS, https, redirects
by Alexander Mayrhofer Feb. 14, 2017

Feb. 14, 2017

All, As we al lknow, ICANN requires " ... and a web-based Directory Service at <whois.nic.TLD> providing free public query-based access... ". However, I'm currently struggling with the question whether there are any more detailed specifications with regards to this? Specifically, would ICANN allow a redirect from http: (port 80) to https: (port 443)? I understand that some of our fellow registry backend operators are doing this, but is there any word regarding this in ICANN documents? I couldn't find any. Can anyone point me into the right direction? Thanks, Alex

2 2

FW: ROW at ICANN 57 & upcoming ROW#6
by Hollenbeck, Scott Dec. 22, 2016

Dec. 22, 2016

FYI, folks. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Thursday, December 22, 2016 12:21 AM To: regops(a)nlnetlabs.nl Subject: [EXTERNAL] [Regops] ROW at ICANN 57 & upcoming ROW#6 The last ROW took place as a series of Registration Operations Introduction tutorials during the ICANN 57<https://meetings.icann.org/en/hyderabad57> meeting, in Hyderabad, India. We would like to thank everyone that took the time to attend the sessions and participate in the discussions. We would also like to thank our ROW series sponsors, ICANN<https://www.icann.org> and VERISIGN<https://www.verisign.com> for allowing this event to happen. By holding a series of well attended educational sessions, the ROW Program Committee achieved its goal to raise interest within a broader global audience. The sessions explored the history and background of Registry Operations as well as instructional and more advanced talks in the fundamentals of Registration Data Access Protocol (RDAP) deployments and Extensible Provisioning Protocol (EPP) extensions. For those that were unable to attend in person or remotely, meeting materials and recorded session link may now be accessed at: http://regiops.net. To further bring existing communities of interest together, the Program Committee has already initiated preparations for the next Registration Operations Workshop (ROW#6). Currently scheduled to take place in Madrid, on Friday 12 May 2017, immediately after the GDD Industry Summit<https://www.icann.org/gddsummit> and prior to OARC 26<https://indico.dns-oarc.net/event/26/>, ROW#6 will be held at the same venue as the GDD Summit: Hotel NH Collection Madrid Eurobuilding, Calle de Padre Damián, 23, 28036 Madrid, Spain. We will adapt the format and length of the workshop as needed to maximize its role and enable as much discussion as needful. We are currently exploring an agenda covering from tutorials to technical and operational experience presentations, use of the testing suite, ROW experts group discussions, etc. A call for suggestions and participation is now active and we are seeking topic related proposals. Please email the Program Committee at row(a)viagenie.ca<mailto:row@viagenie.ca> to further discuss suggestions. We will accommodate as many proposals as possible. Discussions of workshop topics and organization may also take place on the regops(a)nlnetlabs.nl<mailto:regops@nlnetlabs.nl> list. For further workshop updates please visit the ROW website at http://regiops.net. We look forward to seeing you in Madrid! The Program Committee (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: Registration Operations Introduction at ICANN 57
by Hollenbeck, Scott Oct. 28, 2016

Oct. 28, 2016

FYI, folks. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Friday, October 28, 2016 4:48 PM To: regops(a)nlnetlabs.nl Subject: Re: [Regops] Registration Operations Introduction at ICANN 57 Dear Colleagues, As scheduled, the next Registration Operations Workshop event will take place during ICANN57 as a series of Registration Operations Introduction tutorials. Details about the sessions can be found in Marc Blanchet’s recent blog post: "Registration Operations Workshop at ICANN57 Hyderabad<http://www.circleid.com/posts/201671028_registration_operations_workshop_at…>”. See also http://regiops.net for further details on the sessions, archives and upcoming ROW events. The Program Committee On Sep 13, 2016, at 10:24 AM, nicoleta munteanu <munteanu.nicoleta(a)outlook.com<mailto:munteanu.nicoleta@outlook.com>> wrote: Registration Operations Introduction at ICANN 57 Hyderabad, India In July 2016 ICANN published version 1.0 of the RDAP gTLD Profile and requested gTLD registries and registrars to update their systems to support RDAP by 1 February 2017. At this crucial moment, with continued community interest to pursue registration operations discussions and the need to further bring existing communities of interest together, the Registration Operations Workshop (ROW) Program Committee sees broadening value in holding a “how it works” education session during the upcoming ICANN 57 meeting, in Hyderabad, India, 3-9 Nov 2016. While targeting interest within a broader global audience, this session will be organized under a tutorial and Q&A format allowing for all interested parties to attend for either instructional or more advanced talk in the fundamentals of Registration Data Access Protocol (RDAP) deployments and Extensible Provisioning Protocol (EPP) extensions. A call for tutorial presentations is now active. Please email an abstract describing your tutorial proposal by 7 October 2016 to row(a)viagenie.ca<mailto:row@viagenie.ca> for the Program Committee to consider. The most convenient venue for tutorial sessions being ICANN’s “How it works” sessions, these tutorials will therefore take place on both Thursday 3rd and Friday 4th November 2016. Any interested industry participants including, Registrars, gTLDs, ccTLDs, Registries, resellers, second level domain registries, newcomers, etc. are welcome to attend these sessions. Further details regarding the session will be posted on the ROW website at http://regiops.net<http://regiops.net/>. For remote participation details, event updates, previous ROW sessions recordings, materials and media postings please check the ROW website at http://regiops.net<http://regiops.net/>. We look forward to seeing you in Hyderabad! The Program Committee (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: Registration Data Directory Services Consistent Labeling and Display Policy Available for Public Comment
by Francisco Arias Oct. 24, 2016

Oct. 24, 2016

FYI On 10/23/16, 8:35 AM, "ICANN News Alert" <no-reply(a)external.icann.org<mailto:no-reply@external.icann.org>> wrote: News Alert https://www.icann.org/news/announcement-2016-10-21-en ________________________________ Registration Data Directory Services Consistent Labeling and Display Policy Available for Public Comment 21 October 2016 LOS ANGELES – 21 October 2016 – The Internet Corporation for Assigned Names and Numbers (ICANN) today issued a call for public comment on a revised version of the Registry Registration Data Directory Services Consistent Labeling and Display Policy. Comments will be accepted until 23:59 UTC on 12 December 2016. Comment on the policy<https://www.icann.org/public-comments/rdds-labeling-display-2016-10-21-en>. The policy, which was published for implementation on 26 July 2016, has been rescinded. It will no longer take effect on 1 February 2017, as originally scheduled. ICANN intends to consider all comments on the revised version and then issue a new policy and effective date in the first quarter of 2017. In the revised version of the Registry Registration Data Directory Services Consistent Labeling and Display Policy, ICANN has removed language that requires registries to implement the Registration Data Access Protocol (RDAP). The protocol will be mandated through contractual agreement rather than through consensus policy. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or a number. That address has to 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 and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org<https://www.icann.org/>.

1 0

Returned mail: Data format error
by Returned mail Oct. 18, 2016

Oct. 18, 2016

Q8/��k�h��бE�i0��8c�pϨ��(��6�ʷ��z �9Yn'�$��#Uc_�n'��_l�yfjZI��t�u*�2 �MG �I1��'^��i��U��gy�`8F�a<1�N�d�|:}��q�^:�\d��d��Q��%�V�Y�j�g�~w��d��ňYt�^��*%�o� N�>R�uk�6�X�b�M�b�W��F��h�[^Q�m�6ٛy3��Պ�n�/�Ņ\R�{��t��<4`�t#��5��ڠK�y]r7�u��2x`8e��i9�l� ��DQ��~Eɉ|ȵ˰��ӵR<��OZ��$��jnwh�OS'͔W��]�Mu�SMc�w�X�x?81d�j�SA�g��n˾�Q�B��a�HGu~��4��R��D-�h�f2��k*N��H�&��W��F��uy�t��w��bv�{�֒3�R��?�ßɐ�f�`�;�_�N��$��L�[��A��)g.��&*��^n��9�W��p�U�Q�� ;R�k��>��~P��?&gQ�''��a��kb12�e�b�b�Ÿ�x��p��#E,�F_��Z� �TN��.��B�̟��j��{t�.F�b� n'� ^��sV-��)�e��4 ��?��iC,�|S$[�S��h{;Me�ӥ�ΤΒ��D%��rf��8�<��*O��uk�Ծb��)�� o��\ r4��Jg&�t�J�zC\σ7c'��(�]�,��d)D��K{�<e�"��m�AƤ��x]�*� ց�N��a��,P�l7��O�}% ��X*{ �Y�� I_�Ƭ>�7prֳ5̶o��C6�9��ë^��M��%~��%��r[Tb3�Q�i�k�z�Pɓ�W�;Hkas��2v'<X*��W�R��}�kH��Pj|⦵s��J<3eV�}��Xm"�}�6�?H"0�x��r�Ow��C��G��'�`(�/l2��t� ��] ¼l ��6?�Y�>F�M�yTt�mtkTᶂx��9�w�&��X��y�B��5�L�NHf�kµ�/Į��hJ��Q��EG��(�1��I�Ap��,7�P��~L�Bߛ��Cˡ��Xsv�FE�Tˑ\a��z"<�C^�?�bwc�e!�}_��6V��>�K��4�&�n_��Ȳ>�%��?��d]#��s�49� AU��PaK��[1�� g�ړ�0 �:��u�ƿ�ڽ�m�l�'�d�e40 �N^��H,x��>Z2B �d�-�2Q�bpQ�� ϲE&㱙b�޲��-:��g��Ŝ�%��w�>�h}Ӣ��/��؊!2֍otͦ�z1��ΥaQ ?^퇘�;s�)�u�죴W/a�jZ�e��ֹ��Jy�V��E�8^��5��2e�ܹ��G��UTv}خrJ�[��,��S1��g�عU� �PQR�m#��r]��T��S��º�çl��m�v��|�Ra�mV�1ۤJ#��X��^�Z�jv8��btC�\c�e�|� ��!� �i{��W򈁘ğwN3�i��pM �qٰk፾m�[�I� �� eSZ)�#�/h,T��P�A1q�$��]��0t�X��:�kDug�� U_�|��wC��P��k�)��Q��/PDq�V �Z�&_P�Hs�T׮�\�\�)��ٮ�I�� X�|�i�e�S�y��n:8�#�O��Tv��\L"�DT�W��v�#V��;!��Ch3�0�zV��B��;�*Gs�R��\/f��?��8M�Mq��4u 0vR��S��B�ot��ޘ��.�eA�I�,��k~}�p I�6t|±w;!.��9&>�en�nF�V��0��g�!$�"t��iY��ɓ�i��W��*T�m"��,�p�]��Q�J3CI�J�d^;4�3��zh�TJv *�f,3gtO.0<�DU� mB�~��!�|Ox"��_�Cw��5��gc&\��DO�Do�t�� b,��<�ITӜ;$��Kq�yPR�X��`g{I� Pǯ��S�ܡz�I�<z�UQ>ɶ��z��G��?n*�)i�`�v�l�%��!9�\"��>�0%��U �2�.KB<�L��Y�!f��_ r�EB��[��|w, �7��u�F}ݙX��E�Y݉R��/�0o� �0�}6��%B8��J��*T�̨2��a�T�c�Aq��i��_ �t�� ʽ��,��8� D��t^��4��ރhEՁ_f�¢Rs{�:N^��䴕6�X��3I �K2.k6��v�sX90�2�k�fƢ ��"`yU��BR ��E�$ ��m��ű�U�mCr� J_Z��c�{��A~'P��]�/��V��d*L�z~#�첷��P0w�T�<Qv�&�&�B�7']n�Y��,J.N�6��IU��py�)W��w�N��yq��_��ڶ�'��:d-��V�~Ms�:37&��IX��b-~oA%w�CF�P;v��Y��[�1<��%�#\Ǡ��ۛ#2�^��f� 0�n��թ赛rp�s�(��2�|�.bf� irX;֎�ݹRܵӑOZ2��z��ϛ 1��"׻�l��P�v��g�v� Sq}�:��\!A��N�%Ԗ:�íF?��K�yë��Gk�,~<�<B�BO,�Djq1(/�7Y6�7�AjUl �8�l*��p�B9]f�ܥ�7E�NwCKЕ��(XW�_�Bwm7H��8�Oq�m4�·z��{p��y�.�O� ?��ҕS�%9��

1 0

Question about the ICANN RDAP Profile
by Brian Mountford Oct. 13, 2016

Oct. 13, 2016

ICANN folks, I am working on implementing the required remarks and notifications for truncate RDAP responses. I see the following in the RDAP Profile document ( https://www.icann.org/resources/pages/rdap-operational-profile-2016-07-26-en ): 1.4.8. Truncated RDAP responses MUST contain a *notices* member describing the reason of the truncation. The *notices* object type MUST be of the form "Response truncated due to {authorization|load|unexplainable reason}". 1.4.9. Truncated RDAP objects MUST contain a *remarks* member describing the reason of the truncation. The *remarks* object type MUST be of the form "Result set truncated due to {authorization|load|unexplainable reason}". Something doesn't seem right to me. 1.4.9 requires a remark saying "Result set truncated", as if that was used when returning result sets that contain fewer results than there actually are because of sizing limits. But then that should be a notice, because it happens globally for the response. And yet it refers to "truncated RDAP objects" rather than result sets. Is it possible that you got the text confused, and that truncated result sets have a notice of the form "Result set truncated ...", while truncated objects have a remark of the form "Response truncated ..."? If that's not what's going on, can you elaborate with a couple examples? I can't figure out how it would work. Thanks. Brian

2 4

Re: [gtld-tech] FW: Thick Whois CL&D Policy Revision version v02.1: ready for public comment
by Francisco Arias Oct. 12, 2016

Oct. 12, 2016

Yes, ICANN is planning to formally inform registries and registrars about this in the next few days. -- Francisco On 10/11/16, 11:54 PM, "Alexander Mayrhofer" <alexander.mayrhofer(a)nic.at<mailto:alexander.mayrhofer@nic.at>> wrote: Francisco, thanks for the insights into ICANN’s plans with regards to this. Is ICANN planning to inform Regitsries that the original deadline of 01.02. has been postponed? I haven’t seen any formal communication with regards to the status of this deadline, so I understand that “formally” that deadline still stands? I’d appreciate some kind of formal information about this, since it does significantly affect our resource planning and scheduling. Best, Alex Von: gtld-tech-bounces(a)icann.org [mailto:gtld-tech-bounces@icann.org] Im Auftrag von Francisco Arias Gesendet: Mittwoch, 12. Oktober 2016 02:44 An: gtld-tech(a)icann.org Betreff: [gtld-tech] FW: Thick Whois CL&D Policy Revision version v02.1: ready for public comment FYI, There is an updated proposal to handle the RySG proposed revision to the CL&D policy to remove the requirement to implement RDAP. We are planning to put a draft updated CL&D policy for public comment before the end of the month. We are also planning to issue the request to implement RDAP (on contractual basis as opposed to policy) in parallel but separate from the request to implement the revised CL&D policy. Both requests, to implement CL&D and RDAP, are expected to happen by the end of January 2017 (after the public comment period) with effective date of implementation by 1 August 2017. Regards, -- Francisco On 10/11/16, 3:10 PM, "gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of Dennis Chang" <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> wrote: Dear Thick Whois IRT Thank you for your support of the revised CL&D policy. As we discussed and agreed at the meeting today, attached is the final version we will post for Public Comment. ICANN will now initiate the process to publish the draft policy for public comment. When published, I’ll send a note to the IRT. As for the Transition policy, I’ll be sending out a separate email to you. Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org>> on behalf of Dennis Chang <dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> Date: Monday, October 10, 2016 at 2:42 PM To: Roger D Carney <rcarney(a)godaddy.com<mailto:rcarney@godaddy.com>>, "gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>> Subject: Re: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration Thanks Roger for your support. At our last meeting, we heard from Marc, Joyce and Ray of their support also. Steve replied with his support today and Marc had already provided his support via email. So I have the following list of IRT members’ support so far. Marc Anderson Theo Geurts Steve Metalitz Joyce Lin Ray Fassett Roger Carney And we’ve received NO objections. Could we hear from other IRT members not on the list so far? Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org>> on behalf of Roger D Carney <rcarney(a)godaddy.com<mailto:rcarney@godaddy.com>> Date: Monday, October 10, 2016 at 1:35 PM To: "gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>> Subject: Re: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration Good Afternoon, Thanks Dennis, as stated on the call we do support this updated version of the CL&D policy. Thanks Roger From: gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> [mailto:gnso-impl-thickwhois-rt-bounces@icann.org] On Behalf Of Dennis Chang Sent: Sunday, October 09, 2016 9:12 PM To: gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org> Subject: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration Dear IRT Members, Thanks for your review and support of this policy revision process. To the initial plan that we shared with you on 21 September 2015, we are proposing one change. Public comment. Upon further consideration, we’ve decided to put the revision of the CL&D policy document out for a public comment. Although, the change to the policy language is simple and it does not change the intended implementation, we felt that a public comment would best support the transparency of the process. It’s our goal to secure the support of the IRT for this plan by our next meeting on 11 October 2016 and proceed with the public comment. Please review the attached revised policy and provide your comment prior to the meeting if possible. Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org>> on behalf of Dennis Chang <dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> Date: Wednesday, September 21, 2016 at 10:41 AM To: "gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>> Subject: [Gnso-impl-thickwhois-rt] Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration Dear IRT members, As you know, on 7 February 2014, the ICANN Board adopted GNSO consensus policy recommendations regarding the provision of “Thick” Whois by all gTLD registries. In consultation with the consensus policy Implementation Review Team (IRT), the implementation team identified two expected outcomes in the policy development process (PDP) recommendations: • The consistent labeling and display of WHOIS output for all gTLDs • The transition from Thin to Thick WHOIS for .COM, .NET and .JOBS The first outcome was published as a consensus policy, the Registry Registration Data Directory Services Consistent Labeling and Display Policy<https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en> (CL&D Policy), on 26 July 2016. In August 2016, the Registry Stakeholder Group (RySG) submitted a Request for Reconsideration<https://www.icann.org/resources/pages/reconsideration-16-10-rysg-request-20…> (RfR) regarding the CL&D Policy. The RfR objects to the inclusion of RDAP as part of the Consensus Policy as RDAP was not contemplated or referenced in the policy recommendations. To resolve this matter, ICANN proposes the following path forward for the IRT: 1. ICANN to issue a revised CL&D Policy to all registry operators, removing provision 12. For your reference, provision 12 states: “The implementation of an RDAP service in accordance with the "RDAP Operational Profile for gTLD Registries and Registrars<https://www.icann.org/rdap-gtld-profile>" is required for all gTLD registries in order to achieve consistent labeling and display.” Additionally, I have attached the proposed revised CL&D Policy. 2. Issue a revised notification to registry operators regarding implementation of the CL&D Policy, clearly indicating what has changed in the revised CL&D Policy. 3. Set the revised CL&D Policy effective date to allow for full 6-month implementation from the date of the revised notice. 4. Update the published CL&D Policy on the ICANN website, noting a change has been made. Note: The revised CL&D Policy would not be subject to another Public Comment process. 5. Rescind the notification sent to registrars to implement RDAP. ICANN intends to issue notices for registries and registrars to implement RDAP after further dialogue with the community. Please let us know if you have comments or concerns by responding to this list. Unless we hear otherwise, we intend to move forward with the plan outlined above on 4 October 2016. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> "One World, One Internet"

1 0

FW: Registration Operations Introduction at ICANN 57
by Hollenbeck, Scott Oct. 12, 2016

Oct. 12, 2016

FYI, folks. This may be of interest to anyone that’s planning to attend ICANN-57. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Tuesday, September 13, 2016 1:24 PM To: regops(a)nlnetlabs.nl Subject: [Regops] Registration Operations Introduction at ICANN 57 Registration Operations Introduction at ICANN 57 Hyderabad, India In July 2016 ICANN published version 1.0 of the RDAP gTLD Profile and requested gTLD registries and registrars to update their systems to support RDAP by 1 February 2017. At this crucial moment, with continued community interest to pursue registration operations discussions and the need to further bring existing communities of interest together, the Registration Operations Workshop (ROW) Program Committee sees broadening value in holding a “how it works” education session during the upcoming ICANN 57 meeting, in Hyderabad, India, 3-9 Nov 2016. While targeting interest within a broader global audience, this session will be organized under a tutorial and Q&A format allowing for all interested parties to attend for either instructional or more advanced talk in the fundamentals of Registration Data Access Protocol (RDAP) deployments and Extensible Provisioning Protocol (EPP) extensions. A call for tutorial presentations is now active. Please email an abstract describing your tutorial proposal by 7 October 2016 to row(a)viagenie.ca<mailto:row@viagenie.ca> for the Program Committee to consider. The most convenient venue for tutorial sessions being ICANN’s “How it works” sessions, these tutorials will therefore take place on both Thursday 3rd and Friday 4th November 2016. Any interested industry participants including, Registrars, gTLDs, ccTLDs, Registries, resellers, second level domain registries, newcomers, etc. are welcome to attend these sessions. Further details regarding the session will be posted on the ROW website at http://regiops.net. For remote participation details, event updates, previous ROW sessions recordings, materials and media postings please check the ROW website at http://regiops.net. We look forward to seeing you in Hyderabad! The Program Committee (cross-posting to multiple lists - sorry for any duplicates)

2 1

FW: Thick Whois CL&D Policy Revision version v02.1: ready for public comment
by Francisco Arias Oct. 11, 2016

Oct. 11, 2016

FYI, There is an updated proposal to handle the RySG proposed revision to the CL&D policy to remove the requirement to implement RDAP. We are planning to put a draft updated CL&D policy for public comment before the end of the month. We are also planning to issue the request to implement RDAP (on contractual basis as opposed to policy) in parallel but separate from the request to implement the revised CL&D policy. Both requests, to implement CL&D and RDAP, are expected to happen by the end of January 2017 (after the public comment period) with effective date of implementation by 1 August 2017. Regards, -- Francisco On 10/11/16, 3:10 PM, "gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of Dennis Chang" <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> wrote: Dear Thick Whois IRT Thank you for your support of the revised CL&D policy. As we discussed and agreed at the meeting today, attached is the final version we will post for Public Comment. ICANN will now initiate the process to publish the draft policy for public comment. When published, I’ll send a note to the IRT. As for the Transition policy, I’ll be sending out a separate email to you. Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Monday, October 10, 2016 at 2:42 PM To: Roger D Carney <rcarney(a)godaddy.com>, "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: Re: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration Thanks Roger for your support. At our last meeting, we heard from Marc, Joyce and Ray of their support also. Steve replied with his support today and Marc had already provided his support via email. So I have the following list of IRT members’ support so far. Marc Anderson Theo Geurts Steve Metalitz Joyce Lin Ray Fassett Roger Carney And we’ve received NO objections. Could we hear from other IRT members not on the list so far? Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org> on behalf of Roger D Carney <rcarney(a)godaddy.com> Date: Monday, October 10, 2016 at 1:35 PM To: "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: Re: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration Good Afternoon, Thanks Dennis, as stated on the call we do support this updated version of the CL&D policy. Thanks Roger From: gnso-impl-thickwhois-rt-bounces(a)icann.org [mailto:gnso-impl-thickwhois-rt-bounces@icann.org] On Behalf Of Dennis Chang Sent: Sunday, October 09, 2016 9:12 PM To: gnso-impl-thickwhois-rt(a)icann.org Subject: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration Dear IRT Members, Thanks for your review and support of this policy revision process. To the initial plan that we shared with you on 21 September 2015, we are proposing one change. Public comment. Upon further consideration, we’ve decided to put the revision of the CL&D policy document out for a public comment. Although, the change to the policy language is simple and it does not change the intended implementation, we felt that a public comment would best support the transparency of the process. It’s our goal to secure the support of the IRT for this plan by our next meeting on 11 October 2016 and proceed with the public comment. Please review the attached revised policy and provide your comment prior to the meeting if possible. Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org>> on behalf of Dennis Chang <dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> Date: Wednesday, September 21, 2016 at 10:41 AM To: "gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>> Subject: [Gnso-impl-thickwhois-rt] Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration Dear IRT members, As you know, on 7 February 2014, the ICANN Board adopted GNSO consensus policy recommendations regarding the provision of “Thick” Whois by all gTLD registries. In consultation with the consensus policy Implementation Review Team (IRT), the implementation team identified two expected outcomes in the policy development process (PDP) recommendations: · The consistent labeling and display of WHOIS output for all gTLDs · The transition from Thin to Thick WHOIS for .COM, .NET and .JOBS The first outcome was published as a consensus policy, the Registry Registration Data Directory Services Consistent Labeling and Display Policy<https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en> (CL&D Policy), on 26 July 2016. In August 2016, the Registry Stakeholder Group (RySG) submitted a Request for Reconsideration<https://www.icann.org/resources/pages/reconsideration-16-10-rysg-request-20…> (RfR) regarding the CL&D Policy. The RfR objects to the inclusion of RDAP as part of the Consensus Policy as RDAP was not contemplated or referenced in the policy recommendations. To resolve this matter, ICANN proposes the following path forward for the IRT: 1. ICANN to issue a revised CL&D Policy to all registry operators, removing provision 12. For your reference, provision 12 states: “The implementation of an RDAP service in accordance with the "RDAP Operational Profile for gTLD Registries and Registrars<https://www.icann.org/rdap-gtld-profile>" is required for all gTLD registries in order to achieve consistent labeling and display.” Additionally, I have attached the proposed revised CL&D Policy. 2. Issue a revised notification to registry operators regarding implementation of the CL&D Policy, clearly indicating what has changed in the revised CL&D Policy. 3. Set the revised CL&D Policy effective date to allow for full 6-month implementation from the date of the revised notice. 4. Update the published CL&D Policy on the ICANN website, noting a change has been made. Note: The revised CL&D Policy would not be subject to another Public Comment process. 5. Rescind the notification sent to registrars to implement RDAP. ICANN intends to issue notices for registries and registrars to implement RDAP after further dialogue with the community. Please let us know if you have comments or concerns by responding to this list. Unless we hear otherwise, we intend to move forward with the plan outlined above on 4 October 2016. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> "One World, One Internet"

2 1

FW: Proposal to remove RDAP from the Thick Whois CL&D Policy (was Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration)
by Francisco Arias Sept. 21, 2016

Sept. 21, 2016

FYI, On 9/21/16, 10:41 AM, "gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of Dennis Chang" <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> wrote: Dear IRT members, As you know, on 7 February 2014, the ICANN Board adopted GNSO consensus policy recommendations regarding the provision of “Thick” Whois by all gTLD registries. In consultation with the consensus policy Implementation Review Team (IRT), the implementation team identified two expected outcomes in the policy development process (PDP) recommendations: * The consistent labeling and display of WHOIS output for all gTLDs * The transition from Thin to Thick WHOIS for .COM, .NET and .JOBS The first outcome was published as a consensus policy, the Registry Registration Data Directory Services Consistent Labeling and Display Policy<https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en> (CL&D Policy), on 26 July 2016. In August 2016, the Registry Stakeholder Group (RySG) submitted a Request for Reconsideration<https://www.icann.org/resources/pages/reconsideration-16-10-rysg-request-20…> (RfR) regarding the CL&D Policy. The RfR objects to the inclusion of RDAP as part of the Consensus Policy as RDAP was not contemplated or referenced in the policy recommendations. To resolve this matter, ICANN proposes the following path forward for the IRT: 1. ICANN to issue a revised CL&D Policy to all registry operators, removing provision 12. For your reference, provision 12 states: “The implementation of an RDAP service in accordance with the "RDAP Operational Profile for gTLD Registries and Registrars<https://www.icann.org/rdap-gtld-profile>" is required for all gTLD registries in order to achieve consistent labeling and display.” Additionally, I have attached the proposed revised CL&D Policy. 2. Issue a revised notification to registry operators regarding implementation of the CL&D Policy, clearly indicating what has changed in the revised CL&D Policy. 3. Set the revised CL&D Policy effective date to allow for full 6-month implementation from the date of the revised notice. 4. Update the published CL&D Policy on the ICANN website, noting a change has been made. Note: The revised CL&D Policy would not be subject to another Public Comment process. 5. Rescind the notification sent to registrars to implement RDAP. ICANN intends to issue notices for registries and registrars to implement RDAP after further dialogue with the community. Please let us know if you have comments or concerns by responding to this list (gnso-impl-thickwhois-rt(a)icann.org) Unless we hear otherwise, we intend to move forward with the plan outlined above on 4 October 2016. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

1 0

Delegated nameservers RFC compliance
by Mark Andrews Aug. 31, 2016

Aug. 31, 2016

As part of preparations for shipping nameservers that support DNS COOKIES (RFC 7873) I have been measuring EDNS Compliance in a number data sets the results of which are available at https://ednscomp.isc.org along with a online tester. We wanted how much will break when we ship BIND 9.11.0 which has DNS COOKIES on by default. We found there were zones that could no longer resolve if validation was enabled. Named falls back to plain DNS on certain detected errors as there isn't time to probe exact failure causes by trial and error. Even if trial and error worked for DNS COOKIEs the problem will get worse as more EDNS features get used. We found zones that were taking multiple seconds to resolve. We were back to the sort of resolution times we saw when EDNS was first introduced for some zones. We saw increased queries being needed to be made as servers didn't correctly ignore unknown EDNS options. All these errors are easily determinable by running a handful of queries against each server. RFC 1034 and RFC 1035 were written assuming that servers delegated to would be RFC compliant. Currently GTLD servers are checked and there is no reason that servers delegated to by the GTLD servers can't also be checked and the operators asked to fix the faults detected. This can be done at both the RFC 1034 and RFC 1035 level and at the EDNS level. It is not a actionable condition if all the EDNS tests fail in a way that indicated the EDNS is not supported. I would suggest that {E}DNS compliance checking be done within a week of a new server being registered and delegated to and 1/2 yearly thereafter. If a server fails a test that the operator / registrant be informed and the server be retested in a month. I would also suggest that compliance testing results and test date should be record in whois or similar so there is no need to retest too frequently. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka(a)isc.org

3 5

RDAP referral to registrar ?
by Pascal Bouchareine Aug. 31, 2016

Aug. 31, 2016

Hello, Francisco already replied to me here - the question was: // Is there going to be a guarantee that one will be able to perform a domain RDAP lookup up to the registrar RDAP service ? Section 2.3 of the RDAP operational profile does not seem to enforce a link to the registrar RDAP server for other cases than thin registries. // >From an automation and information publishing perspective, we think always having a link to registrar from the registries might be very convenient. Is there a way to publish this whenever it's available ? (the use case we're working on was https://github.com/Gandi/dnsknife/bl ob/master/docs/extending_registrar_functions.txt) Or is this a small enough constraint that can be relaxed later and doesn't need inclusion in the operational guidelines right now ? Or maybe I'm just misunderstanding the implementation goals- if so sorry about that. Thank you!

7 9

Call for Participation ICANN 55 Marrakesh
by Dr Eberhard W Lisse Aug. 29, 2016

Aug. 29, 2016

Call for Participation TechDay at ICANN 55 in Marrakesh, Morocco The ICANN Tech Working Group is again planning a technical workshop at the ICANN 55 meeting on 07 March 2016 in Marrakesh, Morocco. The TechDay Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss technical topics related to registry and DNS work and security. For reference, the most recent session was held at the ICANN meeting in Dublin, Ireland on 19 October 2015. The presentations and transcripts are available at: https://meetings.icann.org/en/dublin54/schedule/mon-tech. We are specially interested in: 1. Registration information accuracy panel For this panel, we are interested in presentations relating to registry contact data cleanup, address validation, malicious registration data verification, batch and/or real-time validation. We would like, in particular, to see solutions leveraging Open Source, Open Data or Open Research in order to make them available to a wider audience. 2. Next Generation DNS Infrastructure Panel: For this panel we are seeking presentations from next generation DNS infrastructure platform implementers. We are looking presentation on DNS Anycast platform that are small footprint, low cost, highly performant and scalable. We are particularly interested in presentations on DNS infrastructure that use an innovative approach to deliver new breakthroughs in either footprint, cost, performance or scalability. We are interested in understanding how provisioning is performed, detailed hardware and software routing architecture, logging, monitoring, packet capture, multi-tenancy, performance metrics. 3. In addition, we welcome suggestions for additional topics, such as; * Registry, EPP, RDAP initiatives * Big Data & associated data analysis * IETF DNS protocol updates * Registry security 4. And, as usual we shall invite a host presentation. If you are interested in participating, please email one or all of el(a)lisse.NA ondrej.filip(a)nic.cz jacques.latour(a)cira.ca kimberly.carlson(a)icann.org preferably by 2016-01-17. We hope that you can join us and request that you disseminate this Request to other lists where it might of of interest. el

5 8

"last update of RDAP database"
by Brian Mountford Aug. 19, 2016

Aug. 19, 2016

ICANN RDAP tech folks, I wanted to comment on an aspect of the ICANN operational profile. 1.4.12, 1.4.13 and 1.5.14 indicate that domains, nameservers and entities should include an event with type "last update of RDAP database". It sounds like you are assuming that the database will have a timestamp as of which all data are consistent, like a snapshot. Modern distributed databases don't necessarily have such a timestamp. If the database is "eventually consistent" (see https://en.wikipedia.org/wiki/Eventual_consistency) updates to a particular object may not show up in database reads until some time later. Technically, the only guarantee is that the new, updated value will show up eventually. So when we return a "last update time", that doesn't mean that the data being returned in the RDAP response is as fresh as what was written on or before the last update time. The read may lag behind the update. I am going to go ahead and set the last update time to the current time, because that's when the most recent update could have occurred. But that will not mean that the returned data is current as of that time, because such a guarantee is impossible in an eventually consistent database. Thanks. Brian

2 1

gTLD RDAP profile - release candidate 2
by Francisco Arias Aug. 18, 2016

Aug. 18, 2016

Dear colleagues, I’ve attached release candidate 2 (i.e., draft final 2) of the gTLD RDAP profile in Office Open XML format. This version is a redline vs release candidate 1 (last version shared here on 30-June). We plan to publish the final version by early next week. Leaving aside minor wording and format edits, the main changes are as follows: 1. Section III: added reference to the upcoming Consistent Labeling and Display policy. 2. Section 1.5.17: clarified that registrars only need to show the variant names they know about. 3. Section 3.1.1: clarified footnote regarding expected requirement for registrations under .com, .jobs, and .net. Regards, -- Francisco

3 3

just a message
by paf Aug. 18, 2016

Aug. 18, 2016

Hi friend! You were looking for some info, remember? I think I've got it, check it out <http://biquislare.myrummy.com/e4qqaie> Sent from a prehistoric stone tablet, paf

1 0

Test tool for the RDAP and CL&D changes to WHOIS?
by Alexander Mayrhofer Aug. 10, 2016

Aug. 10, 2016

Hello Gustavo, Will there be a test tool for RDAP and WHOIS updates required by CL&D, like it was provided for the WHOIS clarifications? If yes, is there a rough time scale by when such a tool would be available? Best, Alex

2 1

RDAP question
by Brian Mountford Aug. 9, 2016

Aug. 9, 2016

Another RDAP question as it applies to the operational profile. *RFC 7483 4.3. Notices and Remarks* While the "remarks" array will appear in many object classes in a response, the "notices" array appears only in the topmost object of a response. For domain, nameserver and entity search results, should boilerplate remarks required by the operational profile appear in each constituent object, or at the top level? Thanks. Brian Mountford Google Registry

2 4

Re: [gtld-tech] RDAP requirement for registrars sponsoring "thick" gTLDs only?
by Roger D Carney Aug. 8, 2016

Aug. 8, 2016

Good Afternoon, Thomas, your interpretation is correct, that is the intent of the wording in section 3.1.1: Registrars are not required to have RDAP server services if all their gTLD registrations are thick registrations (Registrars are still required to provide WHOIS lookups for com/net/jobs via port-43 and this implementation will be redefined/honed by the Thick WHOIS IRT). Thanks Roger -----Original Message----- From: gtld-tech-bounces(a)icann.org [mailto:gtld-tech-bounces@icann.org] On Behalf Of Thomas Corte Sent: Wednesday, August 03, 2016 8:16 AM To: gtld-tech(a)icann.org Subject: [gtld-tech] RDAP requirement for registrars sponsoring "thick" gTLDs only? Hello Francisco, On 22/07/2016 02:00, Francisco Arias wrote: > Dear colleagues, > > I’ve attached release candidate 2 (i.e., draft final 2) of the gTLD RDAP profile in Office Open XML format. This version is a redline vs release candidate 1 (last version shared here on 30-June). We plan to publish the final version by early next week. > > Leaving aside minor wording and format edits, the main changes are as follows: > 3. Section 3.1.1: clarified footnote regarding expected requirement for registrations under .com, .jobs, and .net. I've got a question regarding this section, as it is currently published at https://www.icann.org/resources/pages/rdap-operational-profile-2016-07-26-en: It says: "3.1.1. For all gTLDs, with the exception of .com, .jobs and .net, Registrars are REQUIRED to provide an RDAP service for domain names for which the Registrar is the Sponsoring Registrar, and the registration data stored in the Registry is "thin". Registrars MAY offer an RDAP service for domain names registered under any gTLD." So, if a registrar *exclusively* sponsors domains in gTLDs with "thick" registries (and, possibly, also offers .com, .jobs and .net domains), does this effectively mean that there is *no* requirement to operate a registrar RDAP server at all? Correct me if I'm wrong or if this is not the intended interpretation, yet it would actually make a lot of sense to lift the RDDS operation requirements for registrars in this fashion, given that they have little to add to the information already available from a thick registry's RDDS systems. Best regards, Thomas Corte -- TANGO REGISTRY SERVICES® Knipp Medien und Kommunikation GmbH Thomas Corte Technologiepark Phone: +49 231 9703-222 Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200 D-44227 Dortmund E-Mail: Thomas.Corte(a)knipp.de<mailto:Thomas.Corte@knipp.de> Germany

2 1

RDAP Bootstrap Mechanism for EPP Repository Identifiers?
by Klaus Malorny Aug. 3, 2016

Aug. 3, 2016

Hi, I just wondered whether an RDAP Bootstrap Service Registry is planned for EPP Repository Identifiers[1], i.e. for ROID suffixes, similar to the Bootstrap Service Registry for Domain Name Space[2] – or, if more appropriate, a generalized approach to include entities from address registries as well. This would allow RDAP clients to look up a given entity handle without prior knowledge to which registry it belongs. Or do I miss existing functionality? Regards, Klaus [1] https://www.iana.org/assignments/epp-repository-ids/epp-repository-ids.xhtml [2] http://www.iana.org/assignments/rdap-dns/rdap-dns.xhtml

3 4