- gtld-tech - lists.icann.org

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 5, 2022

July 5, 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 22, 2022

June 22, 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