gTLD Registry Advisory: Correction of non-compliant ROIDs
On 17 May 2018 the ICANN Board adopted a Temporary Specification for gTLD Registration Data. This page is under review and will be updated to address the Temporary Specification.
Publication Date: 26 August 2015
This advisory intends to provide Registries using non-compliant Repository Object Identifiers (ROIDs) with the requirements to correct such ROIDs, while reducing impact on third parties.
The terms "MAY", "MUST", "MUST NOT", "RECOMMENDED", "REQUIRED", "SHOULD" and "SHOULD NOT" are used to indicate the requirement level in accordance with RFC 2119, which is available at http://www.ietf.org/rfc/rfc2119.txt [TXT, 5 KB].
Per Specification 6 of the new gTLD registry agreement and the Functional Specifications Appendix of most legacy gTLDs, according to RFC 5730 (http://tools.ietf.org/html/rfc5730), a globally unique identifier MUST be assigned to every object when the object is created. Registries must register their EPP Repository identifier with IANA (https://www.iana.org/assignments/epp-repository-ids).
Per the Registry Agreement, the use of ROIDs is required, at least, in the RDDS output, data escrow, BRDA, EPP and TMDB LORDN files.
ROID format will be verified during Pre-Delegation Testing (PDT) as part of the Whois tests cases. The verification will confirm the following:
- The ROID is properly formatted as described in RFC 5730; and
- The repository identifier is registered with IANA.
Starting on 2 November 2015, this verification will report warnings (no failures) for deviations, and strict enforcement for deviations (with failures) will start on 31 January 2016.
ROID correction plan requirements:
To update any non-compliant ROIDs, the following actions are required from the registry:
- The Registry MUST register their EPP Repository identifier with IANA. It is RECOMMENDED to use one suffix per TLD, where possible, with the purpose of uniqueness (e.g., use the TLD as the suffix for the ROID).
- The Registry MUST use a unique-per-object ROID in the format specified in RFC 5730.
- The Registry MUST notify all affected registrars of the upcoming change in the current ROIDs, specifying the date of the change and the transition plan.
- The Registry MUST provide the affected registrars and ICANN (through a Naming Services portal case), one of the following:
- The mapping of the old to the new ROIDs; or,
- A conversion algorithm to obtain the new ROIDs from the old ROID values.
- The Registry SHOULD maintain a ROID transition period for at least one month after the ROID update, during which SRS transactions using either old or new ROIDs are supported.