Domain Name Registration Data (DNRD) Objects Mapping
Extracted elements (26)
IDN domain names use the A-label (ACE-encoded) form in the primary <name> field per RFC 5891 Section 4.4, with the Unicode representation carried in the optional <uName> element, keeping the primary key compatible with ASCII-only systems.
The CSV model uses a relational parent-child structure where the 'parent=true' attribute on a child field acts as a foreign key, enabling cascade replace and cascade delete in Differential and Incremental Deposits without requiring explicit primary key declarations in the schema.
Two equivalent data models are defined — XML (all deposit information in a single XML document) and CSV (XML metadata referencing external CSV files) — so registries can choose based on their systems, e.g., using a database's native CSV export or existing EPP code.
Domain, Host, and Contact objects fully support all attributes from EPP mappings RFC 5731, RFC 5732, and RFC 5733 respectively; the XML schema substitution groups feature allows registry-specific extensions to replace the abstract element definitions (abstractDomain, abstractHost, abstractContact).
A data escrow deposit MAY contain a mix of XML and CSV models, but any individual object MUST be escrowed in only one model.
Country identifiers SHALL be represented using two-character codes as specified in ISO 3166-1.
Date and time fields SHALL contain timestamps in UTC as specified in RFC 3339 with no offset from the zero meridian.
Parties receiving and processing data escrow deposits MUST support both CRC32 and SHA-256 checksum algorithms for CSV file integrity verification; if 'cksumAlg' is present, the 'cksum' attribute MUST also be present.
Telephone numbers SHALL be formatted per ITU-E.164 and MUST begin with a plus sign ('+', ASCII 0x2B), followed by a country code, a dot ('.', ASCII 0x2E), and a digit sequence.
The <idnTableId> element MUST be present in a domain object if the domain is an IDN; <uName> (Unicode FQDN) MUST be provided if available; <crDate> and <exDate> MUST be present if the domain has been allocated.
<upRr>, <upDate>, <trDate>, and <trnData> MUST NOT be present in a domain object if the domain has never been modified, transferred, or had a transfer request, respectively.
When the internationalized postal/contact form ('int') is provided, the field value MUST be representable in the 7-bit US-ASCII subset of UTF-8; the localized form ('loc') MAY use unrestricted UTF-8.
Contact objects include personally identifiable information (name, postal address, telephone numbers, email address); the <disclose> element carried in contact objects conveys registrant preferences for restricting third-party access to specific fields, which escrow agents and successor operators must respect.
The Contact Object (rdeContact) is based on EPP contact mapping (RFC 5733) and includes server-unique ID, ROID, statuses, up to two <postalInfo> elements (internationalized and/or localized), voice, fax, email, sponsoring registrar, optional transfer data, and an optional <disclose> element controlling third-party disclosure.
The Domain Name Object (rdeDomain) is based on the EPP domain info response (RFC 5731) and includes name (A-label), ROID, optional Unicode name (<uName>), IDN table reference, statuses, optional RGP sub-statuses, registrant, contacts, name servers, DNSSEC data, sponsoring registrar, creation/expiry/update dates, and optional transfer data.
The EPP Parameters Object records the EPP extensions and parameters supported by the registry operator, providing context needed to interpret objects in the deposit.
The Header Object specifies object counts for each object type in the registry database at a given Timeline Watermark, providing a consistency cross-check for the escrow deposit.
The Host Object (rdeHost) is based on EPP host mapping (RFC 5732) and contains the FQDN, ROID, one or more statuses, zero or more IPv4/IPv6 address elements, sponsoring registrar, and optional creation/update/transfer dates.
The IDN Table Reference Object links internationalized domain names to the specific IDN table and associated language policy used during registration, referenced by <idnTableId> in domain objects.
The NNDN (NNDN's Not a Domain Name) Object is a lightweight record for escrowing domain name labels that exist in the registry (e.g., reserved or blocked names) but are not maintained as full domain objects in the SRS.
The Policy Object allows a registry to declare which OPTIONAL elements of this specification are REQUIRED for its operational model, enabling the escrow agent to verify compliance during the extended verification process.
Section 11 registers XML namespace URNs with IANA for all object schemas defined in this document, including urn:ietf:params:xml:ns:rdeDomain-1.0, rdeHost-1.0, rdeContact-1.0, rdeRegistrar-1.0, rdeIDN-1.0, rdeNNDN-1.0, rdeEPPParams-1.0, rdePolicy-1.0, rdeHeader-1.0, rdeDNRD-1.0, rdeCsv-1.0, and the corresponding csv* namespaces.
Escrow deposits contain sensitive registration data including contact PII, DNSSEC key material, and the full domain inventory; secure transport and storage with access controls at the escrow agent are required to prevent unauthorized disclosure or manipulation of the deposit.
DNSSEC data is escrowed in a separate 'dnssec' CSV file supporting either the DS Data Interface (fKeyTag unsignedShort, fDsAlg unsignedByte, fDigestType unsignedByte, fDigest hexBinary) or the Key Data Interface (fFlags unsignedShort, fProtocol unsignedByte, fKeyAlg unsignedByte, fPubKey) per RFC 5910.
The 'domain' CSV file definition is the parent record requiring fName (domain name, eppcom:labelType) and fRoid, with a choice of fClID or fGurid as the sponsoring registrar identifier, plus optional IDN table ID, registrant, and date fields.
The <rdeCsv:csv> element defines a CSV file set with a 'name' attribute (e.g., 'domain', 'host'), an optional separator character (default ','), ordered <rdeCsv:fields> children with 'type' and 'isRequired' attributes, and <rdeCsv:files> children with optional 'compression', 'encoding', 'cksum', and 'cksumAlg' attributes.