Best Practices by TechOps

About Us


TechOps is an initiative first founded in April 2017 by the ICANN Registrar Stakeholder Group to address technical and operational needs and challenges. In this process it became clear that an additional joint initiative with the ICANN Registry Stakeholder Group is necessary. Our joint goal is to create an open space to exchange experiences, to discuss ideas, and ideally to create best practices. In September 2017, the joint group was kicked off with its first remote meeting. Since that time we had many calls and face to face meetings, during those we have been working on many topics, such as Maintenance, Reports, Domain Transfers.

Members


TechOps is supported i.a. by members of the following companies

If you are a member of the RySG or RrSG and some of your software developers, product managers and/or other colleagues want to join, please contact the respective Secretaries.

united-domains
GoDaddy
1&1 IONOS
Realtime Register
Brandma
Tucows
MarkMonitor
Donuts

Publications, Papers, Projects and Presentations


Documents and best practices we are working or we are supporting

What is the workflow and what are the next steps for our own documents? It usually starts with a discussion, then we start drafting a first paper, which we iteratively improve. If we think it is good enough, we are publishing it. Work that we are supporting are usually discussed and then we provide feedback.

1. New Transfer Process

in discussion
GDPR had an effect on the gTLD transfer process. Currently we discuss how to improve the transfer process to be smoother, securer and GDPR compliant in the future.
The current status of this work can be found on Google Docs.
 

2. Registry Reporting

These documents describe a standardized Registry Reporting Repository and Report Structure including specific Reports.
 
2.1. Registry Reporting Repository
submitted to IETF
This document describes a domain name registry reporting repository used to provide reports to accredited domain name registrars.
The current status of this work can be found on GitHub and IETF.
 
2.2. Registry Report Structure
submitted to IETF
This document describes the structure for reports that a domain name registry can provide via the standardized registry reporting repository.
The current status of this work can be found on GitHub and IETF.
 
2.3. Registry Transaction Report
submitted to IETF
This document describes the content of a Transaction Report based on the Registry Report Structure and delivered by the Registry Reporting Repository.
The current status of this work can be found on GitHub and IETF.
 
2.4. Registry Domain Fee Report
submitted to IETF
This document describes the content of a Domain Fee Report based on the Registry Report Structure and delivered by the Registry Reporting Repository.
The current status of this work can be found on GitHub and IETF.
 
2.5. Registry Domain Inventory Report
submitted to IETF
This document describes the content of a Domain Inventory Report based on the Registry Report Structure and delivered by the Registry Reporting Repository.
The current status of this work can be found on GitHub and IETF.
 
2.6. Registry Domain Drop Report
submitted to IETF
This document describes the content of a Domain Drop Report based on the Registry Report Structure and delivered by the Registry Reporting Repository.
The current status of this work can be found on GitHub and IETF.
 
2.7. Registry Unavailable Domain Report
submitted to IETF
This document describes the content of an Unavailable Domain Report based on the Registry Report Structure and delivered by the Registry Reporting Repository.
The current status of this work can be found on GitHub and IETF.
 

3. Extensible Provisioning Protocol (EPP) related

These documents are related to EPP and include maintenance, mapping, transition, etc.
 
3.1. Registry Maintenance Notifications for the Extensible Provisioning Protocol (EPP)
candidate for adoption at IETF
This document describes an Extensible Provision Protocol (EPP) mapping for the Registry Maintenance Notifications used when Domain Name Registries will conduct a maintenance, and for retrieving these information.
The current status of this work can be found on GitHub and IETF.
 
3.2. Registry Mapping for the Extensible Provisioning Protocol (EPP)
supporting
This document describes an Extensible Provisioning Protocol (EPP) mapping for provisioning registry zones (e.g. top-level domains) in a Domain Name Registry. The attributes of a registry zone include the features and policies of the registry zone.
The current status of this work can be found on IETF.
 
3.3. Registry Transition
in discussion
Given the expansion of the DNS namespace, registry transitions occur more often. Therefore, it is desirable to provide a method for registrars to see the difference between registry implementations.

Letters that we have sent to ICANN

07.05.2018 – Reply to ICANN’s response to CPH TechOps’ updated proposal on GDPR Impact on Domain Name Transfers and Registrant Contact Changes PDF

01.05.2018 – CPH TechOps Letter on GDPR Impact on Domain Name Transfers and Registrant Contact Changes PDF

08.03.2018 – GDPR Impact on Domain Name Transfers and Registrant Contact Changes PDF

Meetings


The group usually meets up remotely every two weeks and in person at ICANN meetings A and C as well as the GDD Summit. We also have a mailing list for regular exchange.

 

upcoming October 2019 – 65th ICANN Meeting in Montreal, Canada

upcoming May 2019 – ICANN GDD Summit 2019 in Bangkok, Thailand

upcoming March 2019 – 64th ICANN Meeting in Kobe, Japan

21.10.201863rd ICANN meeting in Barcelona, Spain

15. - 16.05.2018ICANN GDD Summit 2018 in Vancouver, Canada

12.03.201861st ICANN meeting in San Juan, Puerto Rico

30.10.201760th ICANN meeting in Abu Dhabi, UAE

Contact


TechOps is an initiative of the ICANN Registry and Registrar Stakeholder Groups, if you have any further questions please contact the respective Secretaries.

 

The technical contact of this site is Tobias Sattler, Hauptstr. 5, 85586 Poing, mail [at] tobiassattler.com