July 2022 - gtld-tech - lists.icann.org

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

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

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 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