Domain Name Registration Data (DNRD) Comma-Separated Values (CSV) Objects Mapping

The Registry Data Escrow Specification can be extended to support any type of object that is included in a data escrow. This document defines the data escrow structure of the standard set of objects for Domain Name Registration Data (DNRD), using XML for definition and Comma-Seperated Values (CSV) files for data, which include: Internet domain names that are typically provisioned in a Domain Name Registry using the EPP domain name mapping. The attributes defined in the EPP domain name mapping are fully supported by this document. Internet host names that are typically provisioned in a Domain Name Registry using the EPP host mapping. The attributes defined in the EPP host mapping are fully supported by this document. Individual or organization social information provisioned in a Domain Name Registry using the EPP contact mapping. The attributes defined in the EPP contact mapping are fully supported by this document. The organization that sponsors objects like domains, hosts, and contacts in a Domain Name Registry. The Registrar MAY also be associated with contacts, referred to as registrars contacts. Internationalized Domain Names (IDN) in the Domain Object Data Escrow include references to the languages rules that define the set of character code points allowed for a specific language. Bulk data exports and imports from and to a database is a natural fit for the use of Comma-Seperated Values (CSV) files, but CSV files don't provide any formal description that is a natural fit for the use of XML. This document fully supports the full, incremental, and differential deposits defined in the Registry Data Escrow Specification with a flexible and extensible model for Domain Name Registration Data (DNRD) that leverages Comma-Seperated Values (CSV) files for creating and consuming the deposits in a cost effective manner.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Numerous fields indicate "dates", such as the creation and expiry dates for domains. These fields SHALL contain timestamps indicating the date and time in UTC as specified in , with no offset from the zero meridian.

Country identifiers SHALL be represented using two character identifiers as specified in .

Telephone numbers (both voice and fax) SHALL be formatted based on structures defined in . Telephone numbers described in this specification are character strings that MUST begin with a plus sign ("+", ASCII value 0x002B), followed by a country code defined in , followed by a dot (".", ASCII value 0x002E), followed by a sequence of digits representing the telephone number.

Some elements MAY be provided in either internationalized form ("int") or provided in localized form ("loc"). Those elements use a field value or "isLoc" attribute to specify the form used. If an "isLoc" attribute is used, a value of "true" indicates the use of the localized form and a value of "false" indicates the use of the internationalized form. This MAY override the form specified for a parent element. A value of "int" is used to indicate the internationalized form and a value of "loc" is used to indicate the localized form. When the internalized form ("int") is provided, the field value MUST be represented in a subset of UTF-8 that can be represented in the 7-bit US-ASCII character set. When the localized form ("loc") is provided, the field value MAY be represented in unrestricted UTF-8. Some of the field elements below of the "registrar" <rdeCsv:csv"> <rdeCsv:fields> element specify the internationalized form with the isLoc="false" attribute:

... , registrar-YYYYMMDD.csv ... ...]]> The following is an example of using the <csvContact:fPostalType> field value to define the internationalized or localized form of the remainder of the "contactPostal" field values.

... , contactPostal-YYYYMMDD.csv ... ...]]>

IP addresses syntax MUST conform either to, Internet Protocol , for IPv4 addresses, or IP Version 6 Addressing Architecture , for IPv6 addresses.

To support a CSV model with the Registry Data Escrow Specification, a <rdeCsv:csv> element is defined that substitutes for <rde:content> as a child element of a <rde:contents> substitute element like the <csvDomain:contents> element. A <rdeCsv:csvDelete> element substitutes for <rde:delete> as a child element of the <rde:deletes> element. The <rdeCsv:csv> and <rdeCsv:csvDelete> elements share the following child elements: Optional definition of the CSV separator characters with the default separator character of ",". Ordered list of CSV fields used in the CSV files. There is one or more child elements that substitute for the <rdeCsv:field> abstract element. Each element defines the format of the CSV field contained in the CSV files. <rdeCsv:field> elements by convention support the "type" attribute that defines the XML data type of the field elements. By convention all fields are optional, where an undefined field can be represented with an empty field value ",," in the CSV file, where ',' is the separator character. A list of one or more CSV files using the <rdeCsv:file> child element. The <rdeCsv:file> child element defines a reference to the CSV file name and has the following optional attributes: If the CSV file is compressed, the "compression" attribute defines the compression format like "gzip" or "zip". Defines the encoding of the CSV file with the default encoding of "UTF-8". Defines the checksum CRC (UNIX cksum) of the CSV file. This attribute is used to validate that the full CSV file exists and has not been tampered with. The <rdeCsv:csv> and <rdeCsv:csvDelete> elements requires a "name" attribute that defines the purpose of the CSV file with values like "domain", "host", "contact". The supported "name" attribute values are defined for each object type. The following is an example of the <rdeCsv:csv> element for domain name records.

, domain-YYYYMMDD.csv ]]> The following is example of the "domain-YYYYMMDD.csv" file with a single record matching the <rdeCsv:fields> definition.

The following is an example of the <rde:csvDelete> element for domain name records.

domain-delete-YYYYMMDD.csv ]]> The following is example of the "domain-delete-YYYYMMDD.csv" file with a single record and matching the single <csvDomain:fName> field.

The <rdeCsv:fields> element defined in the <rdeCsv:csv> and <rdeCsv:csvDelete> elements section has child elements that substitute for the abstract <rdeCsv:field> element. By convention <rdeCsv:field> elements incude an 'f' prefix to identify it as a field definition element. There are a set of common field elements that are used across multiple data escrow objects. The common field elements are defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and using the "rdeCsv" sample namespace prefix. The CSV common field elements include: UTF-8 encoded name field with type="eppcom:labelType". Repository Object IDentifier (ROID) field with type="eppcom:roidType". Registrant contact identifier with type="eppcom:clIDType". The object status with type="eppcom:statusType". The object status description, which is free form text describing the rationale for the status, with type="normalizedString". Identifier of client that sponsors the object with type="eppcom:clIDType". Identifier of client that created the object with type="eppcom:clIDType". Identifier of client that updated the object with type="eppcom:clIDType". Identifier of client that requested the transfer with type="eppcom:clIDType". Identifier of client that should take or took action for transfer with type="eppcom:clIDType". Created date of object with type="datetime". Updated date of object with type="datetime". Expiration date of object with type="datetime". Date that transfer was requested with type="datetime". Date that transfer action should be taken or has been taken with type="datetime". Date of last transfer with type="datetime". State of the most recent transfer request with type="eppcom:trStatusType". General token field with type="token". General language field with type="language". General positive integer field with type="positiveInteger". Password authorization info value with type="normalizedString". Contains the URL of an object like a registrar object with type="anyURI". Custom field with name attribute that defines the custom field name" with type="token".

The following is a format for Data Escrow deposits for the standard set of objects for Domain Name Registration Data (DNRD). Format elements are reused from the EPP and related RFCs.

The domain name object is based on the EPP domain name mapping in . The elements used for the Domain Name Object is defined in this section. The <csvDomain:contents> child element of the <rde:contents> element is used to hold the domain name objects for the deposit. The <rdeCsv:csv> and the <rdeCsv:csvDelete> elements, defined in the "<rdeCsv:csv> and <rdeCsv:csvDelete> elements" section, are used with the following supported "name" attribute values: Defines the fields and CSV file references used for the domain name object records. The following field elements were added for use in the "domain" <rdeCsv:csv> <rdeCsv:fields> element: Domain name field with type="eppcom:labelType". Boolean flag indicating if the domain name object is an IDN domain name object with type="boolean". Boolean flag indicating if the domain name object is an IDN variant domain name object with type="boolean". Fully qualified name of the original IDN domain name object related to the variant domain name object with type="eppcom:labelType". Boolean flag indicating if the domain name object is a reserved domain with type="boolean". The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "domain" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: UTF8 encoded domain name for the <csvDomain:fName> field element. Registry Object IDentifier (ROID) for the domain name object. IDN language tag for the IDN domain name object. Registrant contact identifier for the domain name object. Identifier of client that sponsors the domain name object. Identifier of client that created the domain name object. Created date and time of the domain name object. Identifier of the client that last updated the domain name object. Date and time of the last update to the domain name object. Expiration date and time for the domain name object. Date and time of the last transfer for the domain name object. - Password authorization info value for the domain name object. Example of a "domain" <rdeCsv:csv> element:

... , domain-YYYYMMDD.csv ... ...]]> Example of the corresponding domain-YYYYMMDD.csv file. The file contains four records (active ASCII domain, pendingDelete domain, original IDN with LANG1 language rules, and variant IDN with LANG1 language rules).

Example of a "domain" <rdeCsv:csvDelete> element:

... domain-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding domain-delete-YYYYMMDD.csv file. The file contains three domain name records.

Defines the fields and CSV file references used for the domain name object link records to contact objects, as described in . The following field elements were added for use in the "domainContacts" <rdeCsv:csv> <rdeCsv:fields> element: The contact type for the contact object link with type="domain:contactAttrType". The supported contact type values include "admin" for the administration contact, "billing" for the billing contact, and "tech" for the technical contact. The following "csvDomain" fields, defined for the "domain" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "domainContacts" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: The name of the domain object that is linked to the contact object. The following "csvContact" fields, defined for the "contact" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "domainContacts" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: The server-unique contact identifier. The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "domainContacts" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Identifier of client that created the domain object link to the contact object. Date and time that the domain object link to the contact object was created. Example of a "domainContacts" <rdeCsv:csv> element:

... , domainContacts-YYYYMMDD.csv ... ...]]> Example of the corresponding domainContacts-YYYYMMDD.csv file. The file contains an admin, tech, and billing contact for the two domain names domain1.test and domain2.test.

Example of a "domainContacts" <rdeCsv:csvDelete> element:

... domainContacts-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding domainContacts-delete-YYYYMMDD.csv file. The file contains two tech contact records.

Defines the fields and CSV file references used for the domain name object statuses. The following field elements were added for use in the "domainStatuses" <rdeCsv:csv> <rdeCsv:fields> element: The Registry Grace Period (RGP) status, as a sub-status of the <csvDomain:fStatus> "pendingDelete" status value, with type="rgp:statusType" as defined in . The following "csvDomain" fields, defined for the "domain" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "domainStatuses" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Domain name of status. The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "domainStatuses" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Domain object status a defined in . Domain object status description which is free form text describing the rationale for the status. Language of the <rdeCsv:fStatusDescription> field. Identifier of client that set the status for the domain name object. Date and time that the status was set for the domain name object. Example of a "domainStatuses" <rdeCsv:csv> element:

... , domainStatuses-YYYYMMDD.csv ... ...]]> Example of the corresponding domainStatuses-YYYYMMDD.csv file. The file contains the statuses for the two domain names domain1.test and domain2.test.

Example of a "domainStatuses" <rdeCsv:csvDelete> element:

... domainStatuses-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding domainStatuses-delete-YYYYMMDD.csv file. The file contains two status records.

Defines the fields and CSV file references used for the domain name delegated hosts (name servers). The "domainNameServers" CSV files define the relationship between a domain name object and a delegated host, so it will support both the <domain:hostAttr>, using a <rdeCsv:fRoid> field element, or the <domain:hostObj> model, using a <csvHost:fName> field element, defined in . See for information in how to support either the <domain:hostAttr> or <domain:hostObj> model defined in in the "host" CSV files. The following "csvDomain" fields, defined for the "domain" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "domainNameServers" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Domain name using the delegated host name <csvHost:fName>. The following "csvHost" fields, defined for the "host" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "domainNameServers" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Host name of the delegated host. The host name MAY be used to uniquely identify the host object when using the <domain:hostObj> model defined in . The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "domainNameServers" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Identifier of client that created the link between the domain name object and the delegated host. Date and time that the delegated host (name server) was set for the domain name object. Registry Object IDentifier (ROID) used to uniquely reference a delegated host record with the <domain:hostAttr> model in . The host ROID MAY be used in place of the host name using the <csvHost:fName> field element. The <rdeCsv:fRoid> field element MAY also be defined for external hosts when the server supports a separate set of external host objects per sponsoring client. Example of a "domainNameServers" <rdeCsv:csv> element for a server supporting the <domain:hostObj> model of .

... , domainNameServersObj-YYYYMMDD.csv ... ...]]> Example of the corresponding domainNameServersObj-YYYYMMDD.csv file. The file contains the delegated hosts (name servers) for the two domain names domain1.test and domain2.test.

Example of a "domainNameServers" <rdeCsv:csv> element for a server supporting the <domain:hostAttr> model of .

... , domainNameServersAttr-YYYYMMDD.csv ... ...]]> Example of the corresponding domainNameServersAttr-YYYYMMDD.csv file. The file contains the delegated hosts (name servers) for the two domain names domain1.test and domain2.test referenced via the <rdeCsv:fRoid> field element.

Example of a "domainNameServers" <rdeCsv:csvDelete> element for a server supporting the <domain:hostObj> model of .

... domainNameServersObj-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding domainNameServersObj-delete-YYYYMMDD.csv file. The file contains two status records.

Example of a "domainNameServers" <rdeCsv:csvDelete> element for a server supporting the <domain:hostAttr> model of

... domainNameServersAttr-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding domainNameServersAttr-delete-YYYYMMDD.csv file. The file contains two status records.

Defines the fields and CSV file referenes used for the domain name object DNSSEC records (DS or Key Data). The following field elements were added for use in the "dnssec" <rdeCsv:csv> and <rdeCsv:csvDelete> rdeCsv:fields> elements: Indicates a child's preference for the number of seconds after signature generation when the parent's signature on the DS information provided by the child will expire with type="secDNS:maxSigLifeType" defined in . Contains the DS key tag value per with type="unsignedShort". Contains the DS algorithm value per with type="unsignedByte". Contains the DS digest type value per with type="unsignedByte". Contains the DS digest value per with type="hexBinary". Contains the flags field value per with type="unsignedShort". Contains the Key protocol value per with type="unsignedByte". Contains the Key algorithm value per with type="unsignedByte". Contains the public key value per with type="secDNS:keyType". The following "domain" fields, defined for the "domain" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "dnssec" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Domain name of the domain object associated with the DNSSEC record. Example of a "dnssec" <rdeCsv:csv> element with the DS Data Interface of :

... , dnssec-YYYYMMDD.csv ... ...]]> Example of the corresponding dnssec-YYYYMMDD.csv file. The file contains two DS records for domain1.test.

Example of a "dnssec" <rdeCsv:csv> element with the Key Data Interface of :

... , dnssec-YYYYMMDD.csv ... ...]]> Example of the corresponding dnssec-YYYYMMDD.csv file. The file contains two key records for domain1.test.

Example of a "dnssec" <rdeCsv:csvDelete> element with the DS Data Interface of :

... dnssec-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding dnssec-delete-YYYYMMDD.csv file. The file contains two DS records for domain1.test.

Example of a "dnssec" <rdeCsv:csvDelete> element with the Key Data Interface of :

... dnssec-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding dnssec-delete-YYYYMMDD.csv file. The file contains two key records for domain1.test.

Defines the fields and CSV file referenes used for the domain name object pending and completed transfer records. No additional field elements were added for use in the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element. The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "domainTransfer" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: State of the most recent transfer request. Identifier of client that requested the transfer. Date and time that the transfer was requested Identifier of client that should take or took action for transfer. Date and time that the transfer action should be taken or has been taken. Expiration date if the transfer command caused or causes a change in the validity period. The following "csvDomain" fields, defined for the "domain" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "domainContacts" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Domain name of the domain object involved in the transfer. Example of a "domainTransfer" <rdeCsv:csv> element:

... , domainTransfer-YYYYMMDD.csv ... ...]]> Example of the corresponding domainTransfer-YYYYMMDD.csv file. The file contains two domain transfer records, with one in pending status and the second in clientApproved status.

Example of a "domainTransfer" <rdeCsv:csvDelete> element:

... domainTransfer-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding domainTransfer-delete-YYYYMMDD.csv file. The file contains two domain transfer records.

The host object is based on the EPP host mapping in . The elements used for Host Object is defined in this section. The <csvHost:contents> child element of the <rde:contents> element is used to hold the host objects for the deposit. The <rdeCsv:csv> and the <rdeCsv:csvDelete> elements, defined in the "<rdeCsv:csv> and <rdeCsv:csvDelete> elements" section, are used with the following supported "name" attribute values: Defines the fields and CSV file references used for the host object records. The following field elements were added for use in the "host" <rdeCsv:csv> <rdeCsv:fields> element: Host name field with type="eppcom:labelType". Contains parent domain name for the subordinate host object with type="eppcom:labelType". Boolean flag indicating if the host object is an IDN host object with type="boolean". The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "host" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: UTF8 encoded name of an IDN host name. Repository Object IDentifier (ROID) assigned to the host object. The <rdeCsv:fRoid> uniquely identifies the host object that MAY be used in place of the <csvHost:fName> field element to uniquely identify the host object when the &;lt;csvHost:fName> is not unique due to the server supporting the <domain:hostAttr> model of or when the server supports a set of external hosts per sponsoring client. Identifier of the sponsoring client. In the case of external hosts, the server MAY create a unique set of external hosts for each sponsoring client, so the <csvHost:fName> itself won't be unique but instead the combination of the <rdeCsv:fClID> and the <csvHost:fName> is unique. Identifier of client that created the host object. Date and time that the host object was created. Identifier of client that last updated the host object. Date and time that the host object was last updated. Date and time that the host was last transferred. Example of a "host" <rdeCsv:csv> element:

... , host-YYYYMMDD.csv ... ...]]> Example of the corresponding host-YYYYMMDD.csv file. The file contains two host records with one being an internal host and the second being an external host.

Example of a "host" <rdeCsv:csvDelete> element:

... host-delete-YYYYMMDD.csv ... ...]]> Example of the host-delete-YYYYMMDD.csv file. The file contains two host records.

Defines the fields and CSV file references used for the host object statuses. The following "csvHost" fields, defined for the "host" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "hostStatuses" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Host name of status. The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "hostStatuses" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Host object Registry Object IDentifier (ROID) that uniquely identifies the host object when the <csvHost:fName> is not unique. The <rdeCsv:fRoid> is used for servers that support a set of external host objects per sponsoring client. Host object status a defined in . Host object status description which is free form text describing the rationale for the status. Language of the <rdeCsv:fStatusDescription> field. Identifier of client that set the status for the host object. Date and time that the status was set for the host object. Example of a "hostStatuses" <rdeCsv:csv> element:

... , hostStatuses-YYYYMMDD.csv ... ...]]> Example of the corresponding hostStatuses-YYYYMMDD.csv file. The file contains the statuses for the two host names ns1.domain1.test and ns1.domain2.test.

Example of a "hostStatuses" <rdeCsv:csvDelete> element:

... hostStatuses-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding hostStatuses-delete-YYYYMMDD.csv file. The file contains two status records.

Defines the fields and CSV file references used for the host object IP addresses. The following field elements were added for use in the "hostAddresses" <rdeCsv:csv> <rdeCsv:fields> element: IP addresses associated with the host object with type="host:addrStringType". IP addresses version associated with the host object with type="host:ipType". "host:ipType" has the enumerated values of "v4" or "v6". The following "csvHost" fields, defined for the "host" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "hostAddresses" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Host name of IP address. The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "hostAddresses" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Host object Registry Object IDentifier (ROID) that uniquely identifies the host object when the <csvHost:fName> is not unique. The <rdeCsv:fRoid> is used for servers that supports a set of external host objects per sponsoring client or when the server supports the <domain:hostAttr> model of . Identifier of client that set the address for the host object. Date and time that the address was set for the host object. Example of a "hostAddresses" <rdeCsv:csv> element for server that supports the <domain:hostObj> model of .

... , hostAddressesObj-YYYYMMDD.csv ... ...]]> Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The file contains the IP addresses for the host name ns1.domain1.test.

Example of a "hostAddresses" <rdeCsv:csvDelete> element:

... hostAddressesObj-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding hostAddressesObj-delete-YYYYMMDD.csv file. The file contains three IP address records.

Example of a "hostAddresses" <rdeCsv:csv> element for server that supports the <domain:hostAttr> model of .

... , hostAddressesAttr-YYYYMMDD.csv ... ...]]> Example of the corresponding hostAddressesAttr-YYYYMMDD.csv file. The file contains the IP addresses for the host name ns1.domain1.test.

Example of a "hostAddresses" <rdeCsv:csvDelete> element:

... hostAddressesAttr-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding hostAddressesAttr-delete-YYYYMMDD.csv file. The file contains three IP address records.

The contact object is based on the EPP contact mapping in . The elements used for the Contact Object are defined in this sections The <csvContact:contents> child element of the <rde:contents> element to hold the contact objects for the deposit. The <rdeCsv:csv> and the <rdeCsv:csvDelete> elements, defined in the "<rdeCsv:csv> and <rdeCsv:csvDelete> elements" section, are used with the following supported "name" attribute values: Defines the fields and CSV file references used for the contact object records. The following field elements were added for use in the "contact" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Contains the server-unique contact identifier with type="eppcom:clIDType". Contains the contact's voice telephone number with type="contact:e164StringType". Contains the contact's voice telephone number extension with type="token". Contains the contact's facsimile telephone number with type="contact:e164StringType". Contains the contact's facsimile telephone number extension with type="token". Contains the contact's email address with type="eppcom:minTokenType". Defines whether the contact record is a registrar contact with type="boolean". Registrar contacts MAY be mixed with other contacts but MAY not have the same set of required fields. For example, a registrar contact should always have the sponsoring client identifier be that of the registrar. This means that a registrar contact should not support transfer and subsequently does not require an authorization info value with the <rdeCsv:fPwAuthInfo> field element. The <svContact:fIsRegistrarContact> flag MAY further be used to validate against the list of contacts in the "registrarContacts" CSV file, defined in , to ensure that they are all registrar contacts. The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "contact" <rdeCsv:csv> <rdeCsv:fields> element: The Registry Object IDentifier (ROID) for the contact object. Identifier of client that sponsors the contact object. Identifier of client that created the contact object. Created date and time of the contact object Identifier of the client that last updated the contact object. Date and time of the last update to the contact object. Date and time of the last transfer for the contact object. Password authorization info value for the domain name object. Example of a "contact" <rdeCsv:csv> element:

... , contact-YYYYMMDD.csv ... ...]]> Example of the contact-YYYYMMDD.csv file. The file contains two object contact records and one registrar contact record.

Example of a "contact" <rdeCsv:csvDelete> element:

... contact-delete-YYYYMMDD.csv ... ...]]> Example of the contact-delete-YYYYMMDD.csv file. The file contains two contact records.

Defines the fields and CSV file references used for the contact object statuses. The following "csvContact" fields, defined for the "contact" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "contactStatuses" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Server-unique contact identifier of status. The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "contactStatuses" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: The contact object status a defined in . The contact object status description which is free form text describing the rationale for the status. Language of the <rdeCsv:fStatusDescription> field. Identifier of client that set the status for the contact object. The date and time that the status was set for the contact object. Example of a "contactStatuses" <rdeCsv:csv> element:

... , contactStatuses-YYYYMMDD.csv ... ...]]> Example of the corresponding contactStatuses-YYYYMMDD.csv file. The file contains the statuses for the two contact identifiers sh8013 and mycontactid.

Example of a "contactStatuses" <rdeCsv:csvDelete> element:

... contactStatuses-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding contactStatuses-delete-YYYYMMDD.csv file. The file contains two status records.

Defines the fields and CSV file references used for the contact postal info object records. The following field elements were added for use in the "contactPostal" <rdeCsv:csv> <rdeCsv:fields> element: Contains the form of the postal-address information with type="contact:postalLineType". This field specifies the form ("int" or "loc"), as defined in , of the <csvContact:fName>, <csvContact:fOrg>, <csvContact:fStreet>, <csvContact:fCity>, <csvContact:fSp>, <csvContact:fPc>, <csvContact:fCc> fields. Contains the contact's name of the individual or role represented by the contact with type="contact:postalLineType". An OPTIONAL "isLoc" attribute to used to indicate the localized or internationalized form as defined in section . Contains the name of the organization with which the contact is affiliated with type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute to used to indicate the localized or internationalized form as defined in section . Contains the contact's contact's street address line with type="contact:fPostalLineType". An index attribute is required to indicate which street address line the field represents with index "0" for the first line and index "2" for the last line. An OPTIONAL "isLoc" attribute to used to indicate the localized or internationalized form as defined in section . Contains the contact's city with type="contact:postalLineType". An OPTIONAL "isLoc" attribute to used to indicate the localized or internationalized form as defined in section . Contains the contact's state or province with type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute to used to indicate the localized or internationalized form as defined in section . Contains the contact's postal code with type="contact:pcType". An OPTIONAL "isLoc" attribute to used to indicate the localized or internationalized form as defined in section . Contains the contact's country code with type="contact:ccType". An OPTIONAL "isLoc" attribute to used to indicate the localized or internationalized form as defined in section . The following "csvContact" fields, defined for the "contact" <rdeCsv:csv> <rdeCsv:fields> element, is used in the "contactPostal" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Server-unique contact identifier for the contact object. Example of a "contactPostal" <rdeCsv:csv> element:

... , contactPostal-YYYYMMDD.csv ... ...]]> Example of the contactPostal-YYYYMMDD.csv file. The file contains two contact postal records.

Example of a "contactPostal" <rdeCsv:csvDelete> element:

... , contactPostal-delete-YYYYMMDD.csv ... ...]]> Example of the contactPostal-delete-YYYYMMDD.csv file. The file contains two contact postal records.

Defines the fields and CSV file referenes used for the contact object pending and completed transfer records. No additional field elements were added for use in the "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element. The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element: State of the most recent transfer request. Identifier of client that requested the transfer. Date and time that the transfer was requested. Identifier of client that should take or took action for transfer. Date and time that the transfer action should be taken or has been taken The following "csvContact" fields, defined for the "contact" <rdeCsv:csv> <rdeCsv:fields> element, is used in the "contactTransfer" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Server-unique contact identifier for the contact object. Example of a "contactTransfer" <rdeCsv:csv> element:

... , contactTransfer-YYYYMMDD.csv ... ...]]> Example of the contactTransfer-YYYYMMDD.csv file. The file contains two contact transfer records with one in pending status and the second in clientApproved status.

Example of a "contactTransfer" <rdeCsv:csvDelete> element:

... contactTransfer-delete-YYYYMMDD.csv ... ...]]> Example of the contactTransfer-delete-YYYYMMDD.csv file. The file contains two contact transfer records.

Defines the fields and CSV file references used for the contact disclose object records. The following field elements were added for use in the "contactDisclose" <rdeCsv:csv> <rdeCsv:fields> element: Contains flag with a value of "true" or "1" (one) notes the preference to allow disclosure of the specified elements as an exception to the stated data-collection policy. A value of "false" or "0" (zero) notes a client preference to not allow disclosure of the specified elements as an exception to the stated data-collection policy with type="boolean". The additional fields define specific exceptional disclosure preferences based on the <csvContact:fDiscloseFlag> field. Exceptional disclosure preference flag for the localized form of the contact name with type="boolean". Exceptional disclosure preference flag for the internationalized form of the contact name with type="boolean". Exceptional disclosure preference flag for the localized form of the contact organization with type="boolean". with type="boolean". Exceptional disclosure preference flag for the internationalized form of the contact organization with type="boolean". with type="boolean". Exceptional disclosure preference flag for the localized form of the contact address with type="boolean". Exceptional disclosure preference flag for the internationalized form of the contact address with type="boolean". Exceptional disclosure preference flag of the contact voice telephone number with type="boolean". Exceptional disclosure preference flag of the contact facsimile telephone number with type="boolean". Exceptional disclosure preference flag of the contact email address with type="boolean". The following "csvContact" fields, defined for the "contact" <rdeCsv:csv> <rdeCsv:fields> element, is used in the "contactDisclose" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Server-unique contact identifier for the contact object. Example of a "contactDisclose" <rdeCsv:csv> element:

... , contactDisclose-YYYYMMDD.csv ... ...]]> Example of the contactDisclose-YYYYMMDD.csv file. The file contains two disclosure records. The first contact disables disclosure of voice, fax, and email. The second contact enables disclosure of the localized and internationalized form of the name.

Example of a "contactDisclose" <rdeCsv:csvDelete> element:

... contactDisclose-delete-YYYYMMDD.csv ... ...]]> Example of the contactDisclose-delete-YYYYMMDD.csv file. The file contains two disclosure records.

The registrar object represents the sponsoring client for other objects. The registrar object MAY be related to registrar contacts using Contact Object, as defined in , references or MAY contain registrar contacts. The elements used for the Registrar Object references are defined in this section. The <csvRegistrar:contents> child element of the <rde:contents> element holds the registrar objects for the deposit. The <rdeCsv:csv> and the <rdeCsv:csvDelete> elements, defined in the "<rdeCsv:csv> and <rdeCsv:csvDelete> elements" section, are used with the following supported "name" attribute values: Defines the fields and CSV file references used for the registrar object records. The following field elements were added for use in the "registrar" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Contains the server-unique registrar identifier with type="eppcom:clIDType". Contains the name of the registrar with type="normalizedString". Contains the ID assigned by ICANN with type="positiveInteger". Contains the status of the registrar with type="csvRegistrar:statusValueType". Contains the name of the registrar sub-status or the full name of the status when the fStatus value is "custom" with type="token". Contains the Whois URL of the registrar with type="anyURI". The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "registrar" <rdeCsv:csv> <rdeCsv:fields> element: Registry Object IDentifier (ROID) for the registrar object. Identifier of client that created the registrar object. Created date and time of the registrar object. Identifier of the client that last updated the registrar object. Date and time of the last update to the registrar object. URL for the registrar web home page. The following "csvContact" fields, defined in section , MAY be used in the "registrar" <rdeCsv:csv> <rdeCsv:fields> element: Registrar street address line with an "index" attribute that represents the order of the street address line from "0" to "2". An OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in . Registrar city with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in . Registrar state or province with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in . Registrar postal code with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in . Registrar country code with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in . Registrar voice telephone number. Registrar facsimile telephone number. Registrar facsimile telephone number extension. Registrar email address. Example of a "registrar" <rdeCsv:csv> element.

... , registrar-YYYYMMDD.csv ... ...]]> Example of the registrar-YYYYMMDD.csv file. The file contains one registrar record.

Example of a "registrar" <rdeCsv:csvDelete> element:

... registrar-delete-YYYYMMDD.csv ... ...]]> Example of the registrar-delete-YYYYMMDD.csv file. The file contains two registrar records.

Defines the fields and CSV file references used for the registrar object link records to contact objects, as described in . The following field elements were added for use in the "registrarContacts" <rdeCsv:csv> <rdeCsv:fields> element: The registrar contact type for the contact object link with type="csvRegistrar:contactAttrType". The possible values for the <csvRegistrar:fContactType> include: Administration registrar contact. Billing registrar contact. Primary billing registrar contact. If supported, there SHOULD be at most one "primaryBilling" contact per registrar for invoicing. Technical registrar contact. Marketing registrar contact. ICANN registrar registrar contact. Customer support registrar contact. Abuse registrar contact. CEO registrar contact Custom registrar contact type. If custom is used, the <csvRegistrar:fCustomContactTypeName> field element MUST be defined to define the name of the custom contact type. The name of the custom registrar contact type, when the <csvRegistrar:fContactType> field element value is "custom", with type="token". The following "csvRegistrar" fields, defined for the "registrar" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "registrarContacts" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Contains the server-unique registrar identifier for the registrar object. The following "csvContact" fields, defined for the "contact" <rdeCsv:csv> <rdeCsv:fields> element, MAY be used in the "registrarContacts" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Server-unique contact identifier reference. The matching contact object, as defined in , SHOULD define the <csvContact:fIsRegistrarContact> field element with a value of "true" or "1". The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "registrarContacts" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: Identifier of client that created the registrar object link to the contact object. Date and time that the registrar object link to the contact object was created. Example of a "registrarContacts" <rdeCsv:csv> element:

... , registrarContacts-YYYYMMDD.csv ... ...]]> Example of the corresponding registrarContacts-YYYYMMDD.csv file. The file contains a admin, tech, billing, abuse, and custom "policy" contact for the EXAMPLE registrar.

Example of a "registrarContacts" <rdeCsv:csvDelete> element:

... registrarContacts-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding registrarContacts-delete-YYYYMMDD.csv file. The file contains five contact records for the EXAMPLE registrar.

The IDN domain names, defined in , MAY have references to the IDN language using the <rdeCsv:fLanguage> field element. The IDN language object defines the mapping of a language to a language table URL. The language table URL defines the character code points that can be used for the language. The elements used for the IDN language object is defined in this section. The <csvIDN:contents> child element of the <rde:contents> element is used to hold the IDN language objects for the deposit. The <rdeCsv:csv> and the <rdeCsv:csvDelete> elements, defined in the "<rdeCsv:csv> and <rdeCsv:csvDelete> elements" section, are used with the following supported "name" attribute values: Defines the fields and CSV file references used for the IDN language object records. The following "rdeCsv" fields, defined in , MAY be used in the "idnLanguage" <rdeCsv:csv> and <rdeCsv:csvDelete> <rdeCsv:fields> elements: The language tag that matches the values for the <rdeCsv:fLanguage> field element in the "domain" CSV files, as defined in . URL that defines the character code points that can be used for the language defined by the <rdeCsv:fLanguage> field element. Example of a "idnLanguage" <rdeCsv:csv> element:

... , idnLanguage-YYYYMMDD.csv ... ...]]> Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file contains two IDN language records.

Example of a "idnLanguage" <rdeCsv:csvDelete> element:

... idnLanguage-YYYYMMDD.csv ... ...]]> Example of the idnLanguage-delete-YYYYMMDD.csv file. The file contains two IDN language records.

Six schemas are presented here. The first schema is the base CSV schema. The second schema defines domain name CSV object for RDE. The third schema defines host CSV object for RDE. The fourth schema defines contact CSV object for RDE. The fifth schema defines registrar CSV object for RDE. The sixth schema defines the IDN language CSV object.

Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Registry Data Escrow Comma-Seperated Values (CSV) END]]>

Domain Name Comma-Separated Values (CSV) Object END]]>

Host Comma-Separated Values (CSV) Object END]]>

Contact Comma-Separated Values (CSV) Object END]]>

Registar Comma-Separated Values (CSV) Object END]]>

IDN Language Comma-Separated Values (CSV) Object END]]>

TBD

Data Escrow deposits are represented in XML, which provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8. Conformant XML processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED.

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in . Fourteen URI assignments have been registered by the IANA. Registration request for the RDE CSV namespace: URI: urn:ietf:params:xml:ns:rdeCsv-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the RDE CSV XML schema: URI: urn:ietf:params:xml:schema:rdeCsv-1.0 Registrant Contact: See the "Author's Address" section of this document. See the "Formal Syntax" section of this document. Registration request for the RDE CSV domain namespace: URI: urn:ietf:params:xml:ns:csvDomain-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the RDE CSV domain XML schema: URI: urn:ietf:params:xml:schema:csvDomain-1.0 Registrant Contact: See the "Author's Address" section of this document. See the "Formal Syntax" section of this document. Registration request for the RDE CSV host namespace: URI: urn:ietf:params:xml:ns:csvHost-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the RDE CSV host XML schema: URI: urn:ietf:params:xml:schema:csvHost-1.0 Registrant Contact: See the "Author's Address" section of this document. See the "Formal Syntax" section of this document. Registration request for the RDE CSV contact namespace: URI: urn:ietf:params:xml:ns:csvContact-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the RDE CSV contact XML schema: URI: urn:ietf:params:xml:schema:csvContact-1.0 Registrant Contact: See the "Author's Address" section of this document. See the "Formal Syntax" section of this document. Registration request for the RDE CSV registrar namespace: URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the RDE CSV registrar XML schema: URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 Registrant Contact: See the "Author's Address" section of this document. See the "Formal Syntax" section of this document. Registration request for the RDE CSV IDN namespace: URI: urn:ietf:params:xml:ns:csvIDN-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the RDE CSV IDN XML schema: URI: urn:ietf:params:xml:schema:csvIDN-1.0 Registrant Contact: See the "Author's Address" section of this document. See the "Formal Syntax" section of this document.

This specification does not define the security mechanisms to be used in the transmission of the data escrow deposits, since it only specifies the minimum necessary to enable the rebuilding of a Registry from deposits without intervention from the original Registry. Depending on local policies, some elements or most likely, the whole deposit will be considered confidential. As such the Registry transmitting the data to the Escrow Agent SHOULD take all the necessary precautions like encrypting the data itself and/or the transport channel to avoid inadvertent disclosure of private data. It is also of the utmost importance the authentication of the parties passing data escrow deposit files. The Escrow Agent SHOULD properly authenticate the identity of the Registry before accepting data escrow deposits. In a similar manner, the Registry SHOULD authenticate the identity of the Escrow Agent before submitting any data. Additionally, the Registry and the Escrow Agent SHOULD use integrity checking mechanisms to ensure the data transmitted is what the source intended. Validation of the contents by the Escrow Agent is RECOMMENDED to ensure not only the file was transmitted correctly from the Registry, but also the contents are also "meaningful".

Parts of this document are based on EPP and related RFCs by Scott Hollenbeck. The structure and some of the sample data and content of this document is based on the Domain Name Registration Data (DNRD) Objects Mapping by Francisco Arias and Shoji Noguchi. TBD

Removed definition of <rdeCsv:fName> and replaced with <csvDomain:fName> and <csvHost:fName> to be more specific. Removed definition of the <rdeCsv:fields> optional "list" attribute. Removed definition of list field elements: <rdeCsv:fStatuses>, <rdeCsv:fAdminContacts>, <rdeCsv:fTechContacts>, <rdeCsv:fBillingContacts>, <csvDomain:fNsObjs>, <csvDomain:fRgpStatuses>, <csvHost:fV4Addrs>, <csvHost:fV6Addrs>, and <csvRegistrar:fContactTypes>. Added field elements <rdeCsv:fStatus>, <rdeCsv:fStatusDescription>, <rdeCsv:fStatusDescriptionLang>, <csvDomain:fContactType>, <csvDomain:fRgpStatus>, <csvHost:fAddr>, and <csvHost:fAddrVersion>. Added <rdeCsv:csv> name values and definition of "domainStatuses", "domainNameServers", "hostStatuses", "hostAddresses", "contactStatuses", and "registrarContacts". Remove "registrarContact" <rdeCsv:csv> name value to fully use the contact object for both domain contacts and registrar contacts. Added definition of <csvContact:fIsRegistrarContact> to enable the mixing of registrar contacts and the object contacts in the same contact object CSV files.