Advisory: Guidance to Registry Operator regarding escrowing Registrar’s Abuse Contact Information
Please note that the English language version of all translated content and documents are the official versions and that translations in other languages are for informational purposes only.
Version 18 April 2024
This Advisory is intended to provide guidance to registry operators regarding the escrow requirements of the data elements described in sections 8.4.8 and 8.4.9 of the Registration Data Policy.
Definitions:
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
Background
Per section 8.4.8 and 8.4.9 of the Registration Data Policy, Registry Operators MUST escrow the following data elements:
- 8.4.8. Registrar Abuse Contact Email
- 8.4.9. Registrar Abuse Contact Phone
Per section 3.1, Specification 2 of the gTLD Base Registry Agreement, RFC8909 and RFC9022 MUST be used as the deposit's format.
RFC9022 does not have dedicated fields for Registrar Abuse Contact Email or Registrar Abuse Contact Phone but there are two generic fields that could be used to satisfy the requirements of section 8.4.8 and 8.4.9 of the Registration Data Policy.
Registrar's Abuse Contact Information escrow plan:
In order to satisfy the requirements of section 8.4.8 and 8.4.9 of the Registration Data Policy, the following actions are required from the Registry Operator:
- Registry Operator MUST escrow the data element "Registrar Abuse Contact Email" in the <email> element described in RFC9022 section 5.4.1.1 or the <csvContact:fEmail> element described in RFC9022 section 5.4.2.1.1.
- Registry Operator MUST escrow the data element "Registrar Abuse Contact Phone" in the <voice> element described in RFC9022 section 5.4.1.1 or <csvContact:fVoice> and/or <csvContact:fVoiceExt> elements in RFC9022 section 5.4.2.1.1.