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