Network Working Group F. Arias Internet-Draft G. Lozano Intended status: Standards Track ICANN Expires: February 1, 2014 S. Noguchi JPRS J. Gould C. Thippeswamy VeriSign July 31, 2013 Domain Name Registration Data (DNRD) Objects Mapping draft-arias-noguchi-dnrd-objects-mapping-04 Abstract This document specifies the format, contents and semantics of Domain Name Registration Data (DNRD) Escrow deposits for a Domain Name Registry. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on February 1, 2014. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must Arias, et al. Expires February 1, 2014 [Page 1] Internet-Draft DNRD Objects Mapping July 2013 include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6 4.6. CSV elements . . . . . . . . . . . . . . . . . . . . . . 6 4.7. Internationalized and Localized Elements . . . . . . . . 11 5. Object Description . . . . . . . . . . . . . . . . . . . . . 13 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 13 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 35 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 44 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 63 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 71 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 74 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 79 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 81 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 81 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 83 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 8. Data escrow agent extended verification process . . . . . . . 84 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 85 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 85 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 93 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 97 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 101 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 103 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 106 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 109 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 120 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 124 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 125 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 127 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 129 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 132 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 134 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 135 Arias, et al. Expires February 1, 2014 [Page 2] Internet-Draft DNRD Objects Mapping July 2013 10. Internationalization Considerations . . . . . . . . . . . . . 138 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 138 12. Security Considerations . . . . . . . . . . . . . . . . . . . 143 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 144 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 144 14.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . 144 14.2. Changes from version 00 to 01 . . . . . . . . . . . . . . 145 14.3. Changes from version 01 to 02 . . . . . . . . . . . . . . 145 14.4. Changes from version 02 to 03 . . . . . . . . . . . . . . 145 14.5. Changes from version 03 to 04 . . . . . . . . . . . . . . 145 15. Example of a full deposit using the XML model . . . . . . . . 147 16. Example of differential deposit using the XML model . . . . . 152 17. Example of a full deposit using the CSV model . . . . . . . . 154 18. Example of differential deposit using the CSV model . . . . . 163 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 177 19.1. Normative References . . . . . . . . . . . . . . . . . . 177 19.2. Informative References . . . . . . . . . . . . . . . . . 177 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 178 Arias, et al. Expires February 1, 2014 [Page 3] Internet-Draft DNRD Objects Mapping July 2013 1. Introduction This document defines the data escrow structure of the standard set of objects for a Domain Name Registry which include: o Domain: Internet domain names that are typically provisioned in a Domain Name Registry using the EPP domain name mapping [RFC5731]. The attributes defined in the EPP domain name mapping [RFC5731] are fully supported by this document. o Host: Internet host names that are typically provisioned in a Domain Name Registry using the EPP host mapping [RFC5732]. The attributes defined in the EPP host mapping [RFC5732] are fully supported by this document. o Contact: Individual or organization social information provisioned in a Domain Name Registry using the EPP contact mapping [RFC5733]. The attributes defined in the EPP contact mapping [RFC5733] are fully supported by this document. o Registrar: The organization that sponsors objects like domains, hosts, and contacts in a Domain Name Registry. o NNDN (NNDN's not domain name): A lightweight domain-like object that is not linked to a Registrar. This document defines the following pseudo-objects: o IDN Table Reference: Internationalized Domain Names (IDN) included in the Domain Object Data Escrow include references to the IDN Table and Policy used in IDN registration. o EPP parameters: Definition of the specific EPP parameters supported by the Registry Operator. o Header: Used to specify counters of objects in the database at a certain point in time (watermark). o Policy: Used to specify OPTIONAL elements from this specification that are REQUIRED based on the business model of the registry. 2. Models This document defines two different models that can be used to deposit data escrow objects: Arias, et al. Expires February 1, 2014 [Page 4] Internet-Draft DNRD Objects Mapping July 2013 o XML: The XML model includes all of the deposit information (meta- data and data) in an XML document. The definition of the XML format is fully defined in the XML schemas. As a convention, the objects represented using the XML model are referenced using RDE and an XML namespace that is prefixed with "rde". For example, the Domain Name object represented using the XML model can be referred to as the RDE Domain Name with the XML namespace including rdeDomain (urn:ietf:params:xml:ns:rdeDomain-1.0). o CSV: The CSV model uses XML to define the data escrow format of the data contained in referenced Comma-Separated Values (CSV) files. As a convention, the objects represented using the CSV model are referenced using CSV and an XML namespace that is prefixed with "csv". For example, the Domain Name object represented using the CSV model can be referred to as the CSV Domain Name with the XML namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). The data escrow deposit MAY contain a mix of both models but an object MUST be escrowed only in one model. 3. Terminology 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 BCP 14, [RFC2119]. REGISTRY. In the context of this draft the definition will be overloaded (from the definition in the base protocol) to indicate an organization providing Registry Services for a REGISTRY-CLASS DOMAIN NAME. REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) or any other domain name at any level in the DNS tree for which a Registry (either directly or through and affiliate company) provides Registry Services for other organizations or individuals. For example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. REGISTRY SERVICES. Services offered by the Registry critical to the following tasks: the provisioning of domain names on receipt of requests and data from registrars; responding to registrar queries for status information relating to the DNS servers for the RCDN; dissemination of RCDN zone files; operation of the Registry DNS servers; and responding to queries for contact and other information concerning DNS registrations in the RCDN. Any other products or services that only a Registry is capable of providing, by reason of its designation as the Registry. Typical examples of Registry Arias, et al. Expires February 1, 2014 [Page 5] Internet-Draft DNRD Objects Mapping July 2013 Services are: DNS resolution for the RCDN, WHOIS and EPP. ALLOCATED. A status of some label with respect to a zone, whereby the label is associated administratively to some entity that has requested the label. This term (and its cognates "allocation" and "to allocate") may represents the first step on the way to delegation in the DNS. 4. General Conventions 4.1. Date and Time Numerous fields indicate "dates", such as the creation and expiry dates for domain names. These fields SHALL contain timestamps indicating the date and time in UTC as specified in [RFC3339], with no offset from the zero meridian. 4.2. Country names Country identifiers SHALL be represented using two character identifiers as specified in [ISO-3166-1]. 4.3. Telephone numbers Telephone numbers (both voice and facsimile) SHALL be formatted based on structures defined in [ITU-E164]. 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 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by a sequence of digits representing the telephone number. 4.4. Checksum Checksum of the CSV data escrow files MUST use CRC32, that is the algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of ITU-T recommendation V.42. 4.5. IP addresses IP addresses syntax MUST conform to the text representation of either of, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 Addressing Architecture [RFC4291], for IPv6 addresses. 4.6. CSV elements Arias, et al. Expires February 1, 2014 [Page 6] Internet-Draft DNRD Objects Mapping July 2013 4.6.1. element To support a CSV model with the Registry Data Escrow Specification [1], an element is defined for each object that substitutes for the element and for the element, that contains one or more elements. For example, the Domain Name Object (Section 5.1) defines the element, that substitutes for the element, and the element, that substitutes for the element. Both the element and the elements contain one or more elements. The element has the following child elements: Ordered list of CSV fields used in the CSV files. There is one or more child elements that substitute for the abstract element. Each element defines the format of the CSV field contained in the CSV files. The elements support the "type" attribute that defines the XML simple data type of the field element. The elements support the "isRequired" attribute, with a default value of "false", when set to "true" indicates that the field must be non- empty in the CSV files and when set to "false" indicates that the field MAY be empty in the CSV files. The "isRequired" attribute MAY be specifically set for the field elements within the XML schema and MAY be overridden when specifying the fields under the element. The element supports an OPTIONAL "parent" attribute that identifies the field as a reference to a parent object. For example, the field SHOULD set the "parent" attribute to "true" to identify it as the parent domain name of the domain status. A list of one or more CSV files using the child element. The child element defines a reference to the CSV file name and has the following optional attributes: compression If the CSV file is compressed, the "compression" attribute defines the compression format like "gzip" or "zip". encoding Defines the encoding of the CSV file with the default encoding of "UTF-8". Arias, et al. Expires February 1, 2014 [Page 7] Internet-Draft DNRD Objects Mapping July 2013 cksum Defines the checksum of the CSV file using CRC32, as defined in Section 4.4. This attribute is used to validate that the full CSV file exists and has not been tampered with. The 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 OPTIONAL "sep" attribute defines the CSV separator character with the default separator character of ",". The following is an example of the element for domain name records where the is set as required with isRequired="true". ... domain-YYYYMMDD.csv ... The following is example of the "domain-YYYYMMDD.csv" file with one record matching the definition. Arias, et al. Expires February 1, 2014 [Page 8] Internet-Draft DNRD Objects Mapping July 2013 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z The following is an example of the element for domain name records. ... domain-delete-YYYYMMDD.csv ... The following is example of the "domain-delete-YYYYMMDD.csv" file with three records that matches the single field. domain1.test domain2.test domainN.test 4.6.2. CSV common field elements The element defined in the element (Section 4.6.1) section has child elements that substitute for the abstract element. By convention elements include an 'f' prefix to identify them as field definition elements. 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: Arias, et al. Expires February 1, 2014 [Page 9] Internet-Draft DNRD Objects Mapping July 2013 UTF-8 encoded name field with type="eppcom: labelType". Repository Object IDentifier (ROID) field with type="eppcom:roidType" and isRequired="true". Registrant contact identifier with type="eppcom:clIDType". The object status description, which is free form text describing the rationale for the status, with type="normalizedString". Identifier of client (registrar) that sponsors the object with type="eppcom:clIDType" and isRequired="true". Identifier of the registrar, defined in Section 5.4, of the client that created the object with type="eppcom:clIDType". Identifier of client that created the object with type="eppcom:clIDType". Identifier of the registrar, defined in Section 5.4, of the client that updated the object with type="eppcom:clIDType". Identifier of client that updated the object with type="eppcom:clIDType". Identifier of the registrar, defined in Section 5.4, of the client that requested the transfer with type="eppcom: clIDType". Identifier of client that requested the transfer with type="eppcom:clIDType". Identifier of the registrar, defined in Section 5.4, of the client that should take or took action 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". Arias, et al. Expires February 1, 2014 [Page 10] Internet-Draft DNRD Objects Mapping July 2013 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". IDN Table Identifier used for IDN domain names with type="token". General positive integer field with type="positiveInteger". 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". 4.7. Internationalized and Localized Elements 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" element specify the internationalized form with the isLoc="false" attribute: Arias, et al. Expires February 1, 2014 [Page 11] Internet-Draft DNRD Objects Mapping July 2013 ... ... registrar-YYYYMMDD.csv ... ... The following is an example of using the field value to define the internationalized or localized form of the remainder of the "contactPostal" field values. Arias, et al. Expires February 1, 2014 [Page 12] Internet-Draft DNRD Objects Mapping July 2013 ... ... contactPostal-YYYYMMDD.csv ... ... 5. Object Description This section describes the base objects supported by this specification: 5.1. Domain Name Object The domain name object is based on the EPP domain name mapping specified in [RFC5731]. The domain name object supports both the XML Model and the CSV Model, defined in the Models (Section 2) section. The elements used for both models are defined in the following sections. 5.1.1. XML Model There are two elements used in the data escrow of the domain name objects for the XML model including the , under the element, and the element, under the element. Arias, et al. Expires February 1, 2014 [Page 13] Internet-Draft DNRD Objects Mapping July 2013 5.1.1.1. object The domain element is based on the EPP domain response for an authorized client (see Section 3.1.2. of [RFC5731]) with additional data from an EPP Query Response, see Section 3.1.3. of [RFC5731], RGP status from [RFC3915], and data from the EPP command, see Section 5.2.1. of [RFC5910]. A element substitutes for the abstract element to define a concrete definition of a domain. The element can be replaced by other domain definitions using the XML schema substitution groups feature. The element contains the following child elements: o A element that contains the fully qualified name of the domain name object. o A element that contains the repository object identifier assigned to the domain name object when it was created. o An OPTIONAL element that contains the name of the domain name in Unicode character set. It MUST be provided if available. o An OPTIONAL element that references the IDN Table used for the IDN. This corresponds to the "id" attribute of the element. This element MUST be present if the domain name is an IDN. o An OPTIONAL element is used to indicate that the domain name is an IDN variant. This element contains the domain name used to generate the IDN variant. o One or more elements that contain the current status descriptors associated with the domain name. o Zero or more OPTIONAL element to represent "pendingDelete" sub-statuses, including "redemptionPeriod", "pendingRestore", and "pendingDelete", that a domain name can be in as a result of grace period processing as specified in [RFC3915]. o An OPTIONAL element that contain the identifier for the human or organizational social information object associated as the holder of the domain name object. o Zero or more OPTIONAL elements that contain identifiers for the human or organizational social information objects Arias, et al. Expires February 1, 2014 [Page 14] Internet-Draft DNRD Objects Mapping July 2013 associated with the domain name object. o An OPTIONAL element that contains the fully qualified names of the delegated host objects or host attributes (name servers) associated with the domain name object. See Section 1.1 of [RFC5731] for a description of the elements used to specify host objects or host attributes. o A element that contains the identifier of the sponsoring registrar. o A element that contains the identifier of the registrar that created the domain name object. An OPTIONAL client attribute is used to specify the client that performed the operation. o An OPTIONAL element that contains the date and time of the domain name object creation. This element MUST be present if the domain name has been allocated. o An OPTIONAL element that contains the date and time identifying the end (expiration) of the domain name object's registration period. This element MUST be present if the domain name has been allocated. o An OPTIONAL element that contains the identifier of the registrar that last updated the domain name object. This element MUST NOT be present if the domain has never been modified. An OPTIONAL client attribute is used to specify the client that performed the operation. o An OPTIONAL element that contains the date and time of the most recent domain-name-object modification. This element MUST NOT be present if the domain name object has never been modified. o An OPTIONAL element that contains the public key information associated with Domain Name System security (DNSSEC) extensions for the domain name as specified in [RFC5910]. o An OPTIONAL element that contains the date and time of the most recent domain object successful transfer. This element MUST NOT be present if the domain name object has never been transfered. o An OPTIONAL element that contains the following child elements related to the last transfer request of the domain name object. This element MUST NOT be present if a transfer request for the domain name has never been created. Arias, et al. Expires February 1, 2014 [Page 15] Internet-Draft DNRD Objects Mapping July 2013 * A element that contains the state of the most recent transfer request. * A element that contains the identifier of the registrar that requested the domain name object transfer. An OPTIONAL client attribute is used to specify the client that performed the operation. * A element that contains the date and time that the transfer was requested. * An element that contains the identifier of the registrar that SHOULD act upon a PENDING transfer request. For all other status types, the value identifies the registrar that took the indicated action. An OPTIONAL client attribute is used to specify the client that performed the operation. * An element that contains the date and time of a required or completed response. For a PENDING request, the value identifies the date and time by which a response is required before an automated response action will be taken by the registry. For all other status types, the value identifies the date and time when the request was completed. * An OPTIONAL element that contains the end of the domain name object's validity period (expiry date) if the transfer caused or causes a change in the validity period. Example of a domain object: ... example1.test Dexample1-TEST jd1234 sh8013 sh8013 ns1.example.com ns1.example1.test RegistrarX RegistrarX 1999-04-03T22:00:00.0Z 2015-04-03T22:00:00.0Z Arias, et al. Expires February 1, 2014 [Page 16] Internet-Draft DNRD Objects Mapping July 2013 ... 5.1.1.2. object The element contains the fully qualified domain name that was deleted and purged. Example of object: ... ... foo.test bar.test ... ... 5.1.2. CSV Model For the CSV Model of the domain name object, the child element of the element is used to hold the new or updated domain name objects for the deposit. The child element of the element is used to hold the deleted or purged domain name objects for the deposit. Both the and elements contain one or more elements with the following supported "name" attribute values: "domain" Defines the fields and CSV file references used for the domain name object records. The following "csvDomain" field elements, defined for the "domain" element, MUST be used in the "domain" element: Domain name field with type="eppcom:labelType" and isRequired="true". Fully qualified name of the original IDN domain name object related to the variant domain name object with type="eppcom:labelType". Arias, et al. Expires February 1, 2014 [Page 17] Internet-Draft DNRD Objects Mapping July 2013 The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "domain" element: Registry Object IDentifier (ROID) for the domain name object. Identifier of client that sponsors the domain name object. Identifier of the registrar, defined in Section 5.4, of the client that created the object. Created date and time of the domain name object. Identifier of the registrar, defined in Section 5.4, of the client that updated the 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. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MAY be used in the "domain" element: UTF8 encoded domain name for the field element. IDN Table Identifier used for the IDN domain name object that MUST match a field element in the "idnLanguage" CSV files, as defined in Section 5.5.2. Registrant contact identifier for the domain name object. Arias, et al. Expires February 1, 2014 [Page 18] Internet-Draft DNRD Objects Mapping July 2013 Identifier of client that created the domain name object. Identifier of the client that last updated the domain name object. Example of a "domain" 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). Arias, et al. Expires February 1, 2014 [Page 19] Internet-Draft DNRD Objects Mapping July 2013 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z domain2.test,Ddomain1-TEST,,,registrantid,registrarX,registrarX, clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z xn--abc123.test,Dxnabc123-TEST,LANG1,,registrantid,registrarX, registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z xn--abc321.test,Dxnabc321-TEST,LANG1,xn--cbc321.test, registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z Example of a "domain" element: ... ... domain-delete-YYYYMMDD.csv ... ... Example of the corresponding domain-delete-YYYYMMDD.csv file. The file contains three domain name records. domain1.test domain2.test domainN.test Arias, et al. Expires February 1, 2014 [Page 20] Internet-Draft DNRD Objects Mapping July 2013 "domainContacts" Defines the fields and CSV file references used for the domain name object link records to contact objects, as described in Section 5.3. The following "csvDomain" field elements, defined for the "domainContacts" element, MUST be used in the "domainContacts" 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" field elements, defined for the "domain" element, MUST be used in the "domainContacts" element: The name of the domain object that is linked to the contact object. The following "csvContact" fields, defined for the "contact" element, MUST be used in the "domainContacts" element: The server-unique contact identifier. Example of a "domainContacts" element: Arias, et al. Expires February 1, 2014 [Page 21] Internet-Draft DNRD Objects Mapping July 2013 ... ... 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. domain1.test,sh8013,admin domain1.test,mycontactid,tech domain1.test,mycontactid,billing domain2.test,mycontactid,admin domain2.test,sh8013,tech domain2.test,mycontactid,billing Example of a "domainContacts" element: Arias, et al. Expires February 1, 2014 [Page 22] Internet-Draft DNRD Objects Mapping July 2013 ... ... domainContacts-delete-YYYYMMDD.csv ... ... Example of the corresponding domainContacts-delete-YYYYMMDD.csv file. The file contains two tech contact records. domain1.test,mycontactid,tech domain2.test,sh8013,tech "domainStatuses" Defines the fields and CSV file references used for the domain name object statuses. The following "csvDomain" field elements, defined for the "domainStatuses" element, MUST be used in the "domainStatuses" element: The status of the domain name with type="domain:statusValueType". The Registry Grace Period (RGP) status, as a sub-status of the "pendingDelete" status value, with type="rgp:statusValueType" as defined in [RFC3915]. Arias, et al. Expires February 1, 2014 [Page 23] Internet-Draft DNRD Objects Mapping July 2013 The following "csvDomain" fields, defined for the "domain" element, MUST be used in the "domainStatuses" element: Domain name of status. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MAY be used in the "domainStatuses" element: Domain object status description which is free form text describing the rationale for the status. Language of the field. Example of a "domainStatuses" element: ... ... domainStatuses-YYYYMMDD.csv ... ... Arias, et al. Expires February 1, 2014 [Page 24] Internet-Draft DNRD Objects Mapping July 2013 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The file contains the statuses for the two domain names domain1.test and domain2.test. domain1.test,clientUpdateProhibited,"Disallow update", en, domain1.test,clientDeleteProhibited,"Disallow delete", en, domain2.test,clientUpdateProhibited,"Disallow update", en, domain2.test,pendingDelete,,, redemptionPeriod Example of a "domainStatuses" element: ... ... domainStatuses-delete-YYYYMMDD.csv ... ... Example of the corresponding domainStatuses-delete-YYYYMMDD.csv file. The file contains two status records. domain1.test,clientUpdateProhibited domain2.test,pendingDelete Arias, et al. Expires February 1, 2014 [Page 25] Internet-Draft DNRD Objects Mapping July 2013 "domainNameServers" 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. To support both the and the model, defined in [RFC5731], the host field element is used to reference the host. The following "csvDomain" fields, defined for the "domain" element, MUST be used in the "domainNameServers" element: Domain name using the delegated host with host . The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "domainNameServers" element: Registry Object IDentifier (ROID) used to uniquely reference a delegated host record. Example of a "domainNameServers" element. ... ... domainNameServers-YYYYMMDD.csv ... Arias, et al. Expires February 1, 2014 [Page 26] Internet-Draft DNRD Objects Mapping July 2013 ... Example of the corresponding domainNameServers-YYYYMMDD.csv file. The file contains the delegated hosts (name servers) for the two domain names domain1.test and domain2.test referenced via the field element. domain1.test,Dns1domain2test-TEST domain1.test,Dns2domain2test-TEST domain2.test,Dns1domainexample-TEST domain2.test,Dns2domainexample-TEST Example of a "domainNameServers" element. ... ... domainNameServers-delete-YYYYMMDD.csv ... ... Example of the corresponding domainNameServers-delete-YYYYMMDD.csv file. The file contains two records. domain1.test,Dns1domain2test-TEST domain1.test,Dns2domain2test-TEST domain2.test,Dns1domainexample-TEST domain2.test,Dns2domainexample-TEST Arias, et al. Expires February 1, 2014 [Page 27] Internet-Draft DNRD Objects Mapping July 2013 "dnssec" Defines the fields and CSV file references used for the domain name object DNSSEC records (DS or Key Data). The following "csvDomain" field elements, defined for the "dnssec" element, MUST be used in the "dnssec" rdeCsv:fields> element when the DS Data Interface per [RFC5910] is used: Contains the DS key tag value per [RFC5910] with type="unsignedShort". Contains the DS algorithm value per [RFC5910] with type="unsignedByte". Contains the DS digest type value per [RFC5910] with type="unsignedByte". Contains the DS digest value per [RFC5910] with type="hexBinary". The following "csvDomain" field elements, defined for the "dnssec" element, MUST be used in the "dnssec" rdeCsv:fields> element when the Key Data Interface per [RFC5910] is used: Contains the flags field value per [RFC5910] with type="unsignedShort". Contains the Key protocol value per [RFC5910] with type="unsignedByte". Contains the Key algorithm value per [RFC5910] with type="unsignedByte". Contains the public key value per [RFC5910] with type="secDNS:keyType". The following "csvDomain" field elements, defined for the "dnssec" element, MAY be used in the "dnssec" rdeCsv:fields> element: Arias, et al. Expires February 1, 2014 [Page 28] Internet-Draft DNRD Objects Mapping July 2013 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 [RFC5910]. The following "domain" fields, defined for the "domain" element, MUST be used in the "dnssec" element: Domain name of the domain object associated with the DNSSEC record. Example of a "dnssec" element with the DS Data Interface of [RFC5910]: ... dnssec-ds-YYYYMMDD.csv ... ... Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file contains two DS records for domain1.test. Arias, et al. Expires February 1, 2014 [Page 29] Internet-Draft DNRD Objects Mapping July 2013 domain1.test,604800,12345,3,1,49FD46E6C4B45C55D4AC domain1.test,604800,12346,3,1,38EC35D5B3A34B44C39B Example of a "dnssec" element with the Key Data Interface of [RFC5910]: ... dnssec-key-YYYYMMDD.csv ... ... Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file contains two key records for domain1.test. domain1.test,604800,257,3,1,AQPJ////4Q== domain1.test,604800,257,3,1,AQPJ////4QQQ Example of a "dnssec" element with the DS Data Interface of [RFC5910]: Arias, et al. Expires February 1, 2014 [Page 30] Internet-Draft DNRD Objects Mapping July 2013 ... ... dnssec-ds-delete-YYYYMMDD.csv ... ... Example of the corresponding dnssec-ds-delete-YYYYMMDD.csv file. The file contains two DS records for domain1.test. domain1.test,12345,3,1,49FD46E6C4B45C55D4AC domain1.test,12346,3,1,38EC35D5B3A34B44C39B Example of a "dnssec" element with the Key Data Interface of [RFC5910]: Arias, et al. Expires February 1, 2014 [Page 31] Internet-Draft DNRD Objects Mapping July 2013 ... ... dnssec-key-delete-YYYYMMDD.csv ... ... Example of the corresponding dnssec-key-delete-YYYYMMDD.csv file. The file contains two key records for domain1.test. domain1.test,257,3,1,AQPJ////4Q== domain1.test,257,3,1,AQPJ////4QQQ "domainTransfer" Defines the fields and CSV file references used for the domain name object pending and completed transfer records. No additional field elements were added for use in the "domainTransfer" element. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "domainTransfer" element: State of the most recent transfer request. Identifier of the registrar, defined in Section 5.4, of the client that requested the transfer. Arias, et al. Expires February 1, 2014 [Page 32] Internet-Draft DNRD Objects Mapping July 2013 Date and time that the transfer was requested. Identifier of the registrar, defined in Section 5.4, of the client that should take or took action. 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 "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MAY be used in the "domainTransfer" element: Identifier of client that requested the transfer. Identifier of client that should take or took action for transfer. The following "csvDomain" fields, defined for the "domain" element, MUST be used in the "domainTransfer" element: Domain name of the domain object involved in the transfer. Example of a "domainTransfer" element: Arias, et al. Expires February 1, 2014 [Page 33] Internet-Draft DNRD Objects Mapping July 2013 ... ... 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. domain1.test,pending,registrarX,clientY, 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 2016-04-03T22:00:00.0Z domain2.test,clientApproved,registrarX,clientY, 2012-03-08T19:38:00.0Z,registrarY,clientY, 2012-03-09T23:59:59.0Z,2016-05-04T23:00:00.0Z Example of a "domainTransfer" element: Arias, et al. Expires February 1, 2014 [Page 34] Internet-Draft DNRD Objects Mapping July 2013 ... ... domainTransfer-delete-YYYYMMDD.csv ... ... Example of the corresponding domainTransfer-delete-YYYYMMDD.csv file. The file contains two domain transfer records. domain1.test,2011-03-08T19:38:00.0Z domain2.test,2012-03-08T19:38:00.0Z 5.2. Host Object The host object is based on the EPP host name mapping in [RFC5732]. The host object supports both the XML Model and the CSV Model, defined in Models (Section 2) section. The elements used for both models are defined in the following sections. 5.2.1. XML Model There are two elements used in the data escrow of the host objects for the XML model including the , under the element, and the element, under the element. A element substitutes for the abstract element to define a concrete definition of a host. The element can be replaced by other host definitions using the XML schema substitution groups feature. Arias, et al. Expires February 1, 2014 [Page 35] Internet-Draft DNRD Objects Mapping July 2013 5.2.1.1. element The RDE host object is based on the EPP host response for an authorized client (Section 3.1.2. of [RFC5732]). The OPTIONAL element contains the following child elements: o A element that contains the fully qualified name of the host object. o A element that contains the repository object identifier assigned to the host object when the object was created. o One or more elements that describe the status of the host object. o Zero or more elements that contain the IP addresses associated with the host object. o A element that contains the identifier of the sponsoring registrar. o A element that contains the identifier of the registrar that created the host object. An OPTIONAL client attribute is used to specify the client that performed the operation. o A element that contains the date and time of host-object creation. o An OPTIONAL element that contains the identifier of the registrar that last updated the host object. This element MUST NOT be present if the host object has never been modified. An OPTIONAL client attribute is used to specify the client that performed the operation. o An OPTIONAL element that contains the date and time of the most recent host-object modification. This element MUST NOT be present if the host object has never been modified. o An OPTIONAL element that contains the date and time of the most recent host object successful transfer. This element MUST NOT be present if the domain name object has never been transfered. Example of object: Arias, et al. Expires February 1, 2014 [Page 36] Internet-Draft DNRD Objects Mapping July 2013 ... ns1.example1.test Hns1_example_test-TEST 192.0.2.2 192.0.2.29 1080:0:0:0:8:800:200C:417A RegistrarX RegistrarX 1999-05-08T12:10:00.0Z RegistrarX 2009-10-03T09:34:00.0Z ... 5.2.1.2. object The element contains the fully qualified domain name of a host that was deleted. The element also supports host removal based on roid to support SRS systems in which different hosts with the same fully qualified domain name are active at the same time. Example of object: ... ... ns1.example.test ... ... 5.2.1.3. CSV Model For the CSV Model of the host object, the child element of the element is used to hold the new or updated host objects for the deposit. The child element of the element is used to hold the deleted or purged host objects for the deposit. Both the and elements contain one or more elements with the following supported "name" attribute values: Arias, et al. Expires February 1, 2014 [Page 37] Internet-Draft DNRD Objects Mapping July 2013 "host" Defines the fields and CSV file references used for the host object records. The following "csvHost" field elements, defined for the "host" element, MUST be used in the "host" element: Host name field with type="eppcom:labelType" and isRequired="true". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "host" element: Repository Object IDentifier (ROID) assigned to the host object. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MAY be used in the "host" element: Identifier of the sponsoring client. Identifier of the registrar, defined in Section 5.4, of the client that created the object. Identifier of client that created the host object. Date and time that the host object was created. Identifier of the registrar, defined in Section 5.4, of the client that updated the object. Identifier of client that last updated the host object. Date and time that the host object was last updated. Arias, et al. Expires February 1, 2014 [Page 38] Internet-Draft DNRD Objects Mapping July 2013 Date and time that the host was last transferred. Example of a "host" 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. ns1.example.test,Hns1_example_test-TEST,registrarX,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z ns1.example.test2,Hns1_example_test2-TEST,clientY, clientX,2009-05-08T12:10:00.0Z,clientX, 2010-10-03T09:34:00.0Z, Arias, et al. Expires February 1, 2014 [Page 39] Internet-Draft DNRD Objects Mapping July 2013 Example of a "host" element: ... ... host-delete-YYYYMMDD.csv ... ... Example of the host-delete-YYYYMMDD.csv file. The file contains two host records. Hns1_example_test-TEST Hns1_example_test2-TEST "hostStatuses" Defines the fields and CSV file references used for the host object statuses. The following "csvHost" fields, defined for the "host" element, MUST be used in the "hostStatuses" element: The status of the host with type="host: statusValueType"/>. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "hostStatuses" element: Arias, et al. Expires February 1, 2014 [Page 40] Internet-Draft DNRD Objects Mapping July 2013 Host object Registry Object IDentifier (ROID) assigned to the host object. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MAY be used in the "hostStatuses" element: Host object status description which is free form text describing the rationale for the status. Language of the field. Example of a "hostStatuses" 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. Arias, et al. Expires February 1, 2014 [Page 41] Internet-Draft DNRD Objects Mapping July 2013 ns1domain1test-TEST,clientUpdateProhibited,"Disallow update",en ns1domain1test-TEST,clientDeleteProhibited,"Disallow delete",en ns1domain2test-TEST,ok,, Example of a "hostStatuses" element: ... ... hostStatuses-delete-YYYYMMDD.csv ... ... Example of the corresponding hostStatuses-delete-YYYYMMDD.csv file. The file contains two status records. ns1domain1test-TEST,clientUpdateProhibited ns1domain1test-TEST,clientDeleteProhibited "hostAddresses" Defines the fields and CSV file references used for the host object IP addresses. The following "csvHost" field elements, defined for the "hostAddresses" rdeCsv:fields> element, MUST be used in the "hostAddresses" element: Arias, et al. Expires February 1, 2014 [Page 42] Internet-Draft DNRD Objects Mapping July 2013 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 "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "hostAddresses" element: Host object Registry Object IDentifier (ROID) assigned to the host object. Example of a "hostAddresses" element. ... ... hostAddresses-YYYYMMDD.csv ... ... Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The file contains the IP addresses for the host name ns1.domain1.test. Arias, et al. Expires February 1, 2014 [Page 43] Internet-Draft DNRD Objects Mapping July 2013 ns1domain1test-TEST,192.0.2.2,v4 ns1domain1test-TEST,192.0.2.29,v4 ns1domain1test-TEST,1080:0:0:0:8:800:200C:417A,v6 Example of a "hostAddresses" element: ... ... hostAddresses-delete-YYYYMMDD.csv ... ... Example of the corresponding hostAddresses-delete-YYYYMMDD.csv file. The file contains three IP address records. ns1domain1test-TEST,192.0.2.2 ns1domain1test-TEST,192.0.2.29 ns1domain1test-TEST,1080:0:0:0:8:800:200C:417A 5.3. Contact Object The contact object is based on the EPP contact name mapping in [RFC5733]. The contact object supports both the XML Model and the CSV Model, defined in Models (Section 2) section. The elements used for both models are defined in the following sections. Arias, et al. Expires February 1, 2014 [Page 44] Internet-Draft DNRD Objects Mapping July 2013 5.3.1. XML Model There are two elements used in the data escrow of the contact objects for the XML model including the , under the element, and the element, under the element. A element substitutes for the abstract element to define a concrete definition of a contact. The element can be replaced by other contact definitions using the XML schema substitution groups feature. 5.3.1.1. object The contact object is based on the EPP contact response for an authorized client (Section 3.1.2. of [RFC5733]) with some additions including the data from an EPP Query Response, see Section 3.1.3. of [RFC5733]. The OPTIONAL element contains the following child elements: o A element that contains the server-unique identifier of the contact object o A element that contains the Repository Object IDentifier assigned to the contact object when the object was created. o One or more elements that describe the status of the contact object. o One or two elements that contain postal-address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, element content MUST be represented in a subset of UTF-8 that can be represented in the 7-bit US-ASCII character set. If a localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The element contains the following child elements: * A element that contains the name of the individual or role represented by the contact. * An OPTIONAL element that contains the name of the organization with which the contact is affiliated. Arias, et al. Expires February 1, 2014 [Page 45] Internet-Draft DNRD Objects Mapping July 2013 * An element that contains address information associated with the contact. An element contains the following child elements: + One, two, or three OPTIONAL elements that contain the contact's street address. + A element that contains the contact's city. + An OPTIONAL element that contains the contact's state or province. + An OPTIONAL element that contains the contact's postal code. + A element that contains the contact's two-letter country code. o An OPTIONAL element that contains the contact's voice telephone number. o An OPTIONAL element that contains the contact's facsimile telephone number. o An element that contains the contact's email address. o A element that contains the identifier of the sponsoring registrar. o A element that contains the identifier of the registrar that created the contact object. An OPTIONAL client attribute is used to specify the client that performed the operation. o A element that contains the date and time of contact- object creation. o An OPTIONAL element that contains the identifier of the registrar that last updated the contact object. This element MUST NOT be present if the contact has never been modified. An OPTIONAL client attribute is used to specify the client that performed the operation. o An OPTIONAL element that contains the date and time of the most recent contact-object modification. This element MUST NOT be present if the contact object has never been modified. o An OPTIONAL element that contains the date and time of the most recent contact object successful transfer. This element Arias, et al. Expires February 1, 2014 [Page 46] Internet-Draft DNRD Objects Mapping July 2013 MUST NOT be present if the contact object has never been transferred. o An OPTIONAL element that contains the following child elements related to the last transfer request of the contact object: * A element that contains the state of the most recent transfer request. * A element that contains the identifier of the registrar that requested the domain name object transfer. An OPTIONAL client attribute is used to specify the client that performed the operation. * An element that contains the identifier of the registrar that SHOULD act upon a PENDING transfer request. For all other status types, the value identifies the registrar that took the indicated action. An OPTIONAL client attribute is used to specify the client that performed the operation. * A element that contains the date and time that the transfer was requested. * An element that contains the date and time of a required or completed response. For a PENDING request, the value identifies the date and time by which a response is required before an automated response action will be taken by the registry. For all other status types, the value identifies the date and time when the request was completed. o An OPTIONAL element that identifies elements that requiring exceptional server-operator handling to allow or restrict disclosure to third parties. See Section 2.9 of [RFC5733] for a description of the child elements contained within the element. Example object: Arias, et al. Expires February 1, 2014 [Page 47] Internet-Draft DNRD Objects Mapping July 2013 ... Csh8013-TEST sh8013 John Doe Example Inc. 123 Example Dr. Suite 100 Dulles VA 20166-6503 US +1.7035555555 +1.7035555556 jdoe@example.test RegistrarX RegistrarX 2009-09-13T08:01:00.0Z RegistrarX 2009-11-26T09:10:00.0Z 2009-12-03T09:05:00.0Z pending clientW 2011-03-08T19:38:00.0Z RegistrarX 2011-03-13T23:59:59.0Z ... 5.3.1.2. object The element contains the id of a contact that was deleted. Example of object: Arias, et al. Expires February 1, 2014 [Page 48] Internet-Draft DNRD Objects Mapping July 2013 ... ... sh8013-TEST co8013-TEST ... ... 5.3.2. CSV Model For the CSV Model of the contact object, the child element of the element is used to hold the new or updated contact objects for the deposit. The child element of the element is used to hold the deleted or purged contact objects for the deposit. Both the and elements contain one or more elements with the following supported "name" attribute values: "contact" Defines the fields and CSV file references used for the contact object records. The following "csvContact" field elements, defined for the "contact" element, MUST be used in the "contact" element: Contains the server-unique contact identifier with type="eppcom:clIDType" and isRequired="true". Contains the contact's email address with type="eppcom:minTokenType" and isRequired="true". The following field elements MAY be used in the "contact" element: Contains the contact's voice telephone number with type="contact:e164StringType". Arias, et al. Expires February 1, 2014 [Page 49] Internet-Draft DNRD Objects Mapping July 2013 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". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "contact" element: The Registry Object IDentifier (ROID) for the contact object. Identifier of client (registrar) that sponsors the contact object. Identifier of the registrar, defined in Section 5.4, of the client that created the object. Created date and time of the contact object Identifier of the registrar, defined in Section 5.4, of the client that updated the object. Date and time of the last update to the contact object. Date and time of the last transfer for the contact object. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MAY be used in the "contact" element: Identifier of client that created the contact object. Identifier of the client that last updated the contact object. Arias, et al. Expires February 1, 2014 [Page 50] Internet-Draft DNRD Objects Mapping July 2013 Example of a "contact" element: ... ... contact-YYYYMMDD.csv ... ... Example of the contact-YYYYMMDD.csv file. The file contains two object contact records. sh8013,Csh8013-TEST,+1.7035555555,1234,+1.7035555556,, jdoe@example.test,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2009-11-26T09:10:00.0Z mycontactid,Cmycontactid-TEST,+1.7034444444,1234, +1.7033333333,,jsmith@example.test,registrarX,registarX,clientY, 2010-09-13T08:01:00.0Z,registarX,clientY,2011-11-26T09:10:00.0Z Arias, et al. Expires February 1, 2014 [Page 51] Internet-Draft DNRD Objects Mapping July 2013 Example of a "contact" element: ... ... contact-delete-YYYYMMDD.csv ... ... Example of the contact-delete-YYYYMMDD.csv file. The file contains two contact records. sh8013 mycontactid "contactStatuses" Defines the fields and CSV file references used for the contact object statuses. The following "csvContact" field elements, defined for the "contact" element, MUST be used in the "contactStatuses" element: Server-unique contact identifier of status. The status of the contact with type="contact:statusValueType". Arias, et al. Expires February 1, 2014 [Page 52] Internet-Draft DNRD Objects Mapping July 2013 The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MAY be used in the "contactStatuses" element: The contact object status description which is free form text describing the rationale for the status. Language of the field. Example of a "contactStatuses" 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. sh8013,clientUpdateProhibited,"Disallow update",en sh8013,clientDeleteProhibited,"Disallow delete",en mycontactid,ok,, Arias, et al. Expires February 1, 2014 [Page 53] Internet-Draft DNRD Objects Mapping July 2013 Example of a "contactStatuses" element: ... ... contactStatuses-delete-YYYYMMDD.csv ... ... Example of the corresponding contactStatuses-delete-YYYYMMDD.csv file. The file contains two status records. sh8013,clientUpdateProhibited sh8013,clientDeleteProhibited "contactPostal" Defines the fields and CSV file references used for the contact postal info object records. The following "csvContact" field elements, defined for the "contactPostal" element, MUST be used in the "contactPostal" element: Contains the contact's name of the individual or role represented by the contact with type="contact: postalLineType" and isRequired="true". An OPTIONAL "isLoc" attribute to used to indicate the localized or internationalized form as defined in section Section 4.7. Arias, et al. Expires February 1, 2014 [Page 54] Internet-Draft DNRD Objects Mapping July 2013 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 Section 4.7. Contains the contact's city with type="contact:postalLineType" and isRequired="true". An OPTIONAL "isLoc" attribute to used to indicate the localized or internationalized form as defined in section Section 4.7. 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 Section 4.7. "contactPostal" Defines the fields and CSV file references used for the contact postal info object records. The following "csvContact" field elements, defined for the "contactPostal" element, MAY be used in the "contactPostal" element: Contains the form of the postal-address information with type="contact:postalLineType". This field specifies the form ("int" or "loc"), as defined in Section 4.7, of the , , , , , , fields. 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 Section 4.7. 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 Section 4.7. Arias, et al. Expires February 1, 2014 [Page 55] Internet-Draft DNRD Objects Mapping July 2013 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 Section 4.7. The following "csvContact" fields, defined for the "contact" element, MUST be used in the "contactPostal" element: Server-unique contact identifier for the contact object. Example of a "contactPostal" element: ... ... contactPostal-YYYYMMDD.csv ... ... Arias, et al. Expires February 1, 2014 [Page 56] Internet-Draft DNRD Objects Mapping July 2013 Example of the contactPostal-YYYYMMDD.csv file. The file contains two contact postal records. sh8013,int,"John Doe","Example Inc.", "123 Example Dr.","Suite 100",,Reston,VA,20190,US mycontactid,int,"John Smith","Acme Inc.", "123 Sample Dr.",,,Reston,VA,20190,US Example of a "contactPostal" element: ... ... contactPostal-delete-YYYYMMDD.csv ... ... Example of the contactPostal-delete-YYYYMMDD.csv file. The file contains two contact postal records. sh8013,int mycontactid,int "contactTransfer" Defines the fields and CSV file references used for the contact object pending and completed transfer records. No additional field elements were added for use in the "contactTransfer" element. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "contactTransfer" Arias, et al. Expires February 1, 2014 [Page 57] Internet-Draft DNRD Objects Mapping July 2013 element: State of the most recent transfer request. Identifier of the registrar, defined in Section 5.4, of the client that requested the transfer. Date and time that the transfer was requested. Identifier of the registrar, defined in Section 5.4, of the client that should take or took action. Date and time that the transfer action should be taken or has been taken The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MAY be used in the "contactTransfer" element: Identifier of client that requested the transfer. Identifier of client that should take or took action for transfer. The following "csvContact" fields, defined for the "contact" element, MUST be used in the "contactTransfer" element: Server-unique contact identifier for the contact object. Example of a "contactTransfer" element: Arias, et al. Expires February 1, 2014 [Page 58] Internet-Draft DNRD Objects Mapping July 2013 ... ... 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. sh8013,pending,registrarX,clientX,2011-03-08T19:38:00.0Z, registrarY,,2011-03-13T23:59:59.0Z mycontactid,clientApproved,registrarX,clientX,2011-04-08T19:38:00.0Z, registrarY,clientY,2011-04-09T20:38:00.0Z Example of a "contactTransfer" element: Arias, et al. Expires February 1, 2014 [Page 59] Internet-Draft DNRD Objects Mapping July 2013 ... ... contactTransfer-delete-YYYYMMDD.csv ... ... Example of the contactTransfer-delete-YYYYMMDD.csv file. The file contains two contact transfer records. sh8013,2011-03-08T19:38:00.0Z mycontactid,2011-04-08T19:38:00.0Z "contactDisclose" Defines the fields and CSV file references used for the contact disclose object records. The following "csvContact" field elements, defined for the "contactDisclose" element, MAY be used in the "contactDisclose" 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 field. Arias, et al. Expires February 1, 2014 [Page 60] Internet-Draft DNRD Objects Mapping July 2013 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" element, is used in the "contactDisclose" element: Server-unique contact identifier for the contact object. Example of a "contactDisclose" element: Arias, et al. Expires February 1, 2014 [Page 61] Internet-Draft DNRD Objects Mapping July 2013 ... ... 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. sh8013,0,0,0,0,0,0,0,1,1,1 mycontactid,1,1,1,0,0,0,0,0,0,0 Example of a "contactDisclose" element: Arias, et al. Expires February 1, 2014 [Page 62] Internet-Draft DNRD Objects Mapping July 2013 ... ... contactDisclose-delete-YYYYMMDD.csv ... ... Example of the contactDisclose-delete-YYYYMMDD.csv file. The file contains two disclosure records. sh8013 mycontactid 5.4. Registrar Object The registrar object represents the sponsoring client for other objects, for operational purposes MAY be the registry operator. The registrar object supports both the XML Model and the CSV Model, defined in Section 2. The elements used for both models are defined in the following sections. 5.4.1. XML Model There are two elements used in the data escrow of the registrar objects for the XML model including the , under the element, and the element, under the element. A element substitutes for the abstract element to define a concrete definition of a registrar. The element can be replaced by other domain definitions using the XML schema substitution groups feature. Arias, et al. Expires February 1, 2014 [Page 63] Internet-Draft DNRD Objects Mapping July 2013 5.4.1.1. element The element contains the following child elements: o An element that contains the Registry-unique identifier of the registrar object. This has a superordinate relationship to a subordinate , or of domain, contact and host objects. o An element that contains the name of the registrar. o An OPTIONAL element that contains the ID assigned by ICANN. o A element that contains the operational status of the registrar. Possible values are: ok, readonly and terminated. o One or two elements that contain postal- address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, element content MUST be represented in a subset of UTF-8 that can be represented in the 7-bit US-ASCII character set. If a localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The element contains the following child elements: * A element that contains address information associated with the registrar. The element contains the following child elements: + One, two, or three OPTIONAL elements that contain the registrar's street address. + A element that contains the registrar's city. + An OPTIONAL element that contains the registrar's state or province. + An OPTIONAL element that contains the registrar's postal code. + A element that contains the registrar's country code. o An OPTIONAL element that contains the registrar's voice telephone number. Arias, et al. Expires February 1, 2014 [Page 64] Internet-Draft DNRD Objects Mapping July 2013 o An OPTIONAL element that contains the registrar's facsimile telephone number. o An element that contains the registrar's email address. o An OPTIONAL element that contains the registrar's URL. o An OPTIONAL elements that contains whois information. The element contains the following child elements: * An OPTIONAL element that contains the name of the registrar WHOIS server listening on TCP port 43 as specified in [RFC3912]. * An OPTIONAL element that contains the name of the registrar WHOIS server listening on TCP port 80/443. o A element that contains the date and time of registrar- object creation. o An OPTIONAL element that contains the date and time of the most recent RDE registrar-object modification. This element MUST NOT be present if the rdeRegistrar object has never been modified. Example of object: Arias, et al. Expires February 1, 2014 [Page 65] Internet-Draft DNRD Objects Mapping July 2013 ... RegistrarX Registrar X 123 ok 123 Example Dr. Suite 100 Dulles VA 20166-6503 US +1.7035555555 +1.7035555556 jdoe@example.test http://www.example.test whois.example.test http://whois.example.test 2005-04-23T11:49:00.0Z 2009-02-17T17:51:00.0Z ... 5.4.1.2. object The element contains the id of a registrar that was deleted. Example of object: ... ... agnt0001-TEST ... ... Arias, et al. Expires February 1, 2014 [Page 66] Internet-Draft DNRD Objects Mapping July 2013 5.4.2. CSV Model For the CSV Model of the registrar object, The child element of the element is used to hold the new or updated registrar objects for the deposit. The child element of the element is used to hold the deleted or purged registrar objects for the deposit. Both the and elements contain one or more elements with the following supported "name" attribute values: "registrar" Defines the fields and CSV file references used for the registrar object records. The following "csvRegistrar" field elements, defined for the "registrar" element, MUST be used in the "registrar" element: Contains the server-unique registrar identifier with type="eppcom:clIDType" and isRequired="true". Contains the name of the registrar with type="normalizedString" and isRequired="true". Contains the status of the registrar with type="csvRegistrar:statusValueType". The following field elements MAY be used in the "registrar" element: Contains the ID assigned by ICANN with type="positiveInteger". Contains the Whois URL of the registrar with type="anyURI". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "registrar" element: Arias, et al. Expires February 1, 2014 [Page 67] Internet-Draft DNRD Objects Mapping July 2013 Created date and time of 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 Section 5.3, MUST be used in the "registrar" 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 Section 4.7. Registrar city with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in Section 4.7. Registrar country code with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in Section 4.7. Registrar email address. The following "csvContact" fields, defined in section Section 5.3, MAY be used in the "registrar" element: Registrar state or province with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in Section 4.7. Registrar postal code with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in Section 4.7. Registrar voice telephone number. Arias, et al. Expires February 1, 2014 [Page 68] Internet-Draft DNRD Objects Mapping July 2013 Registrar voice telephone number extension. Registrar facsimile telephone number. Registrar facsimile telephone number extension. Example of a "registrar" element. ... ... registrar-YYYYMMDD.csv ... Arias, et al. Expires February 1, 2014 [Page 69] Internet-Draft DNRD Objects Mapping July 2013 ... Example of the registrar-YYYYMMDD.csv file. The file contains one registrar record. EXAMPLE,"Example Inc.",1234,ok,"123 Example Dr.", "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, +1.7035555556,,jdoe@example.test,http://www.example.test, http://whois.example.test,2005-04-23T11:49:00.0Z, 2009-02-17T17:51:00.0Z Example of a "registrar" element: ... ... registrar-delete-YYYYMMDD.csv ... ... Example of the registrar-delete-YYYYMMDD.csv file. The file contains two registrar records. EXAMPLE EXAMPLE2 Arias, et al. Expires February 1, 2014 [Page 70] Internet-Draft DNRD Objects Mapping July 2013 5.5. IDN Table Reference Object The Internationalized Domain Names (IDN) table reference object is a pseudo-object that is used to provide a short reference to the IDN Table and Policy used in IDN registrations. The IDN reference object supports both the XML and the CSV Model, defined in the Models (Section 2) section. The elements used for both models are defined in the following sections. 5.5.1. XML Model There is one element used in the data escrow of the IDN table reference objects for the XML model that is the , under the element. 5.5.1.1. object The contains the following elements. An "id" attribute is used to specify an identifier for the IDN table. o An element that contains the URL of the IDN table that is being referenced. o A element that contains the URL of the IDN policy document. If IDN variants are generated algorithmically, the policy document MUST define the algorithm and the state of the implicit generated IDN variants. For a list of suggested states for implicit IDN variants, please see [variantTLDsReport]. Example of object: ... http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html http://registro.br/dominio/regras.html ... 5.5.2. CSV Model The IDN domain names, defined in Section 5.1, MAY have references to the IDN language identifier using the field element. The IDN table reference object defines the mapping of a Arias, et al. Expires February 1, 2014 [Page 71] Internet-Draft DNRD Objects Mapping July 2013 language identifier to a language table URL. The language table URL defines the character code points that can be used for the language identifier. The elements used for the IDN table reference object is defined in this section. The child element of the element is used to hold the new or updated IDN table reference objects for the deposit. The child element of the element is used to hold the deleted or purged IDN table reference objects for the deposit. Both the and elements contain one or more elements with the following supported "name" attribute values: "idnLanguage" Defines the fields and CSV file references used for the IDN table reference object records. The following "rdeCsv" fields, defined in Section 4.6.2, MUST be used in the "idnLanguage" element: The language identifier that matches the values for the field element in the "domain" CSV files, as defined in Section 5.1. URL that defines the character code points that can be used for the language defined by the field element. Example of a "idnLanguage" element: Arias, et al. Expires February 1, 2014 [Page 72] Internet-Draft DNRD Objects Mapping July 2013 ... ... , idnLanguage-YYYYMMDD.csv ... ... Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file contains two IDN language records. LANG-1, http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt LANG-2, http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt Example of a "idnLanguage" element: Arias, et al. Expires February 1, 2014 [Page 73] Internet-Draft DNRD Objects Mapping July 2013 ... ... idnLanguage-delete-YYYYMMDD.csv ... ... Example of the idnLanguage-delete-YYYYMMDD.csv file. The file contains two IDN language records. LANG1 LANG2 5.6. NNDN Object A NNDN (NNDN's not domain name) can be used to store registry reserved names or (blocked, withheld or mirrored) IDN variants. A NNDN is a lightweight domain-like object that is not linked directly to a Registrar (a mirroring NNDN is linked to a Registrar via the original name). A domain name can only exist as a domain name object or NNDN object, but not both. The NNDN object supports both the XML and the CSV Model, defined in the Models (Section 2) section. The elements used for both models are defined in the following sections. 5.6.1. XML Model There are two elements used in the data escrow of the NNDN objects for the XML model including the , under the element, and the element, under the element. Arias, et al. Expires February 1, 2014 [Page 74] Internet-Draft DNRD Objects Mapping July 2013 A element substitutes for the abstract element to define a concrete definition of a NNDN. The element can be replaced by other NNDN definitions using the XML schema substitution groups feature. 5.6.1.1. object The element contains the following child elements: o An element that contains the ASCII Compatible Encoding (ACE) field of the NNDN. o An OPTIONAL element that contains the name of the NNDN in Unicode character set. It MUST be provided if available. o An OPTIONAL element that references the IDN Table used for the NNDN. This corresponds to the "id" attribute of the element. This element MUST be present if the NNDN is an IDN. o An OPTIONAL element is used to indicate that the NNDN is an IDN variant. This element contains the domain name used to generate the IDN variant. o A element that indicates the state of the NNDN: blocked, withheld or mirrored. * If a NNDN is considered undesirable for registration (i.e., unavailable for allocation to anyone), then the NNDN will be tagged as "blocked". * If a NNDN is considered a potential registration of a domain object for a particular registrant, then the NNDN will be tagged as "withheld". * If a NNDN is considered a mirrored IDN variant of a domain object, then the NNDN will be tagged as "mirrored". A mirroringNS attribute is used to specify if the mirrored IDN variant use the NS mirror mechanism. The default value of mirroringNS is true. If another mechanism such as DNAME is used, the value of mirroringNS attribute MUST be false. o A element that contains the date and time of the NNDN object creation. Example of object: Arias, et al. Expires February 1, 2014 [Page 75] Internet-Draft DNRD Objects Mapping July 2013 ... xn--exampl-gva.test pt-BR example1.test withheld 2005-04-23T11:49:00.0Z ... 5.6.1.2. object The element contains the ACE of a NNDN that was deleted, i.e., the . Example of object: ... ... xn--pingino-q2a.test ... ... 5.6.2. CSV Model For the CSV Model of the NNDN object, the child element of the element is used to hold the new or updated NNDN objects for the deposit. The child element of the element is used to hold the deleted or purged NNDN objects for the deposit. Both the and elements contain one or more elements with the following supported "name" attribute values: "NNDN" Defines the fields and CSV file references used for the NNDN object records. The following "csvNNDN" field elements, defined for the "NNDN" element, MUST be used in the "NNDN" element: Arias, et al. Expires February 1, 2014 [Page 76] Internet-Draft DNRD Objects Mapping July 2013 ASCII Compatible Encoding (ACE) field of the NNDN with type="eppcom:labelType" and isRequired="true". Domain name used to generate the IDN variant with type="eppcom:labelType". State of the NNDN: blocked or withheld with type="rdeNNDN:nameState". See Section 5.6.1.1 for a description of the possible values for the element. The following field elements MAY be used in the "NNDN" element: Domain name used to generate the IDN variant with type="eppcom:labelType". Defines whether the "mirroring" uses the NS mirror mechanism, as described for the "mirroringNS" attribute in Section 5.6.1.1, with type="boolean". If the field element is not defined the default value is "true". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MUST be used in the "domain" element: Created date and time of the domain name object. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2), MAY be used in the "domain" element: Name of the NNDN in Unicode character set for the field element. IDN Table Identifier for the NNDN that matches an IDN Table Reference Object record, as defined in Section 5.5.2. Arias, et al. Expires February 1, 2014 [Page 77] Internet-Draft DNRD Objects Mapping July 2013 Example of a "NNDN" element: ... ... NNDN-YYYYMMDD.csv ... ... Example of the corresponding NNDN-YYYYMMDD.csv file. The file contains two NNDN records for an IDN with one blocked variant and one mirrored variant. xn--exampl-gva.test,pt-BR,xn--exampl.test, blocked,,2005-04-23T11:49:00.0Z xn--exampl2-gva.test,pt-BR,xn--exampl.test, mirrored,1,2005-04-23T11:49:00.0Z Example of a "NNDN" element: Arias, et al. Expires February 1, 2014 [Page 78] Internet-Draft DNRD Objects Mapping July 2013 ... ... NNDN-delete-YYYYMMDD.csv ... ... Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file contains one NNDN record. xn--pingino-q2a.test 5.7. EPP Parameters Object The EPP Parameters Object is a pseudo-object that defines the set of object and object extension services supported by the registry, as defined in [RFC5730]. The EPP Parameters Object is only defined as XML but could be used in the the XML model or CSV model. The EPP Parameters Object is defined using the the element. The EPP Parameters Object SHOULD be included if the registry supports EPP. Only one EPP Parameters Object MUST exist at a certain point in time (watermark). The syntax and content of the children elements is as explained in section 2.4 of [RFC5730]. The children of the are as follows: o One or more elements that indicate the EPP versions supported by the registry. o One or more elements that indicate the identifiers of the text response languages supported by the registry's EPP server. o One or more elements that contain namespace URIs representing the objects that the registry's EPP server is capable Arias, et al. Expires February 1, 2014 [Page 79] Internet-Draft DNRD Objects Mapping July 2013 of managing. o An OPTIONAL element that contains one or more elements that contain namespace URIs representing object extensions supported by the registry's EPP server. o A element that contains child elements used to describe the server's privacy policy for data collection and management. See section 2.4 of [RFC5730] for more details. Example of element object: ... 1.0 en urn:ietf:params:xml:ns:domain-1.0 urn:ietf:params:xml:ns:contact-1.0 urn:ietf:params:xml:ns:host-1.0 urn:ietf:params:xml:ns:rgp-1.0 urn:ietf:params:xml:ns:secDNS-1.1 ... Arias, et al. Expires February 1, 2014 [Page 80] Internet-Draft DNRD Objects Mapping July 2013 5.8. Policy Object The Policy object is a pseudo-object that is used to specify which OPTIONAL elements from the XML Model are REQUIRED based on the business model of the registry. For the CSV Model, the OPTIONAL "isRequired" attribute of the elements, defined in Section 4.6.1, is used to specify which OPTIONAL fields are REQUIRED based on the business model of the registry. 5.8.1. object The OPTIONAL contains the following attributes: o An that defines that the referenced is REQUIRED. o that defines the XPath of the element referenced by . Example of object: ... ... 5.9. Header Object The Header Object is a pseudo-object that is used to specify the number of objects in the SRS at a specific point in time (watermark) regardless of the type of deposit: differential, full or incremental. The Header Object is only defined as XML but one header object MUST always be present per escrow deposit regardless of using XML Model or CSV Model. The Header Object is defined using the element. 5.9.1. object The contains the following attributes: o A element that defines TLD being escrowed. o A element that contains the number of objects in the SRS at a specific point in time (watermark) regardless of the type of deposit: differential, full or incremental. The "uri" attributes reflects the XML namespace URI of the primary objects for the XML Model and CSV Model. For example, the "uri" is set to Arias, et al. Expires February 1, 2014 [Page 81] Internet-Draft DNRD Objects Mapping July 2013 "urn:ietf:params:xml:ns:rdeDomain-1.0" for domain name objects using the XML Model, and the "uri" is set to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name objects using the CSV Model. Example of object referencing only the XML Model objects: ... test 2 1 1 1 1 1 1 ... Example of object referencing the CSV and XML Model objects: Arias, et al. Expires February 1, 2014 [Page 82] Internet-Draft DNRD Objects Mapping July 2013 ... test 2 1 1 1 1 1 1 ... 6. RDE IDN Variants handling Depending on the Registration Policy of the Registry; for a particular domain name there may be multiple variant names. See [variantTLDsReport] for further detail on IDN variants. A registry could choose to escrow IDN variants as domains or NNDN objects. An specific IDN variant can be represented in the escrow deposit, as a domain or as a NNDN object, but not both. If using domain objects to represent IDN variants, the normal behavior during restoration of a SRS based on an escrow deposit is to restore the IDN variants as a mirrored variant. If the registration data of the IDN variant is different from the original name, the details of this specific implementation MUST be described in the IDN policy document. A NNDN or a domain name are explicit representations of an IDN variant while an IDN variant computed based on an algorithm is an implicit representation. Explicit representation of an IDN variant takes precedence over an implicit representation. Arias, et al. Expires February 1, 2014 [Page 83] Internet-Draft DNRD Objects Mapping July 2013 7. Profile Different business models of registries exist, therefore the registry is responsible to define a profile that matches its particular business model. The profile mechanism allows a registry to extend this specification. A profile is the process of: 1. Extending base objects with the mechanisms defined for XML and CSV models. * In the case of the XML model, abstract elements could be use to extend the following objects: , , , and using XML schema substitution groups feature. 2. Defining a object to specify which OPTIONAL elements of this base specification are required based on the business model of the registry. An example is the element that is usually REQUIRED but it is specified as OPTIONAL in this specification to support existing business models. 3. Adding new escrowed objects using the and elements. 4. Providing the XML schemas to third parties that require them to validate the escrow deposits. 8. Data escrow agent extended verification process The Data Escrow Agent MUST perform a extended verification process using the contents of the data escrow deposits to a point in time (watermark), last full plus all differentials or last full plus last incremental escrow deposits. The following are the minimum suggested tests: o Validate the escrow deposits using the definition agreed with the registry. * In the case of the XML model, the contents of the escrow deposits MUST be validated using the XML schemas of the profile. o Count the objects and validate that the number of objects is equal to the number objects reported in the
element of the escrow deposit of that point in time (watermark). Arias, et al. Expires February 1, 2014 [Page 84] Internet-Draft DNRD Objects Mapping July 2013 o All contacts objects linked to domain names MUST be present. o All registrars objects linked to other objects MUST be present. o A domain name exists as a domain name or NNDN, but not both. o The elements listed as required in the element MUST be present. o All idnTableRef definitions linked from other objects MUST be present. o If an EPP Parameters Object was escrowed in the past, one and only one EPP Parameters Object MUST be present. 9. Formal Syntax Schemas are presented here. 9.1. RDE CSV Schema 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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 Arias, et al. Expires February 1, 2014 [Page 85] Internet-Draft DNRD Objects Mapping July 2013 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. BEGIN Registry Data Escrow Comma-Seperated Values (CSV) Arias, et al. Expires February 1, 2014 [Page 86] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 88] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 89] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 91] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 92] Internet-Draft DNRD Objects Mapping July 2013 END 9.2. RDE Domain Object Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Arias, et al. Expires February 1, 2014 [Page 93] Internet-Draft DNRD Objects Mapping July 2013 Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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. BEGIN Arias, et al. Expires February 1, 2014 [Page 94] Internet-Draft DNRD Objects Mapping July 2013 Registry Data Escrow Domain provisioning schema END Arias, et al. Expires February 1, 2014 [Page 96] Internet-Draft DNRD Objects Mapping July 2013 9.3. CSV Domain 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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. BEGIN Arias, et al. Expires February 1, 2014 [Page 97] Internet-Draft DNRD Objects Mapping July 2013 Domain Name Comma-Separated Values (CSV) Object Arias, et al. Expires February 1, 2014 [Page 98] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 99] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 100] Internet-Draft DNRD Objects Mapping July 2013 END 9.4. RDE Host Object Copyright (c) 2011 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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 Arias, et al. Expires February 1, 2014 [Page 101] Internet-Draft DNRD Objects Mapping July 2013 "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. BEGIN Registry Data Escrow Host provisioning schema Arias, et al. Expires February 1, 2014 [Page 102] Internet-Draft DNRD Objects Mapping July 2013 END 9.5. CSV Host 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Arias, et al. Expires February 1, 2014 [Page 103] Internet-Draft DNRD Objects Mapping July 2013 o 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. o 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. BEGIN Arias, et al. Expires February 1, 2014 [Page 104] Internet-Draft DNRD Objects Mapping July 2013 Host Comma-Separated Values (CSV) Object Arias, et al. Expires February 1, 2014 [Page 105] Internet-Draft DNRD Objects Mapping July 2013 END 9.6. RDE Contact Object Copyright (c) 2011 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 Arias, et al. Expires February 1, 2014 [Page 106] Internet-Draft DNRD Objects Mapping July 2013 are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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. BEGIN Registry Data Escrow contact provisioning schema Arias, et al. Expires February 1, 2014 [Page 107] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 108] Internet-Draft DNRD Objects Mapping July 2013 END 9.7. CSV Contact 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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. Arias, et al. Expires February 1, 2014 [Page 109] Internet-Draft DNRD Objects Mapping July 2013 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. BEGIN Contact Comma-Separated Values (CSV) Object Arias, et al. Expires February 1, 2014 [Page 110] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 111] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 112] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 113] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 114] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 115] Internet-Draft DNRD Objects Mapping July 2013 END 9.8. RDE Registrar Object Copyright (c) 2011 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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 Arias, et al. Expires February 1, 2014 [Page 116] Internet-Draft DNRD Objects Mapping July 2013 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BEGIN Registry Data Escrow registrar provisioning schema Arias, et al. Expires February 1, 2014 [Page 118] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 119] Internet-Draft DNRD Objects Mapping July 2013 END 9.9. CSV Registrar 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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 Arias, et al. Expires February 1, 2014 [Page 120] Internet-Draft DNRD Objects Mapping July 2013 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. BEGIN Registar Comma-Separated Values (CSV) Object Arias, et al. Expires February 1, 2014 [Page 121] Internet-Draft DNRD Objects Mapping July 2013 Arias, et al. Expires February 1, 2014 [Page 122] Internet-Draft DNRD Objects Mapping July 2013 END Arias, et al. Expires February 1, 2014 [Page 123] Internet-Draft DNRD Objects Mapping July 2013 9.10. RDE IDN Table Reference Objects Copyright (c) 2011 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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. Arias, et al. Expires February 1, 2014 [Page 124] Internet-Draft DNRD Objects Mapping July 2013 BEGIN Registry Data Escrow IDN provisioning schema END 9.11. CSV IDN Language 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 Arias, et al. Expires February 1, 2014 [Page 125] Internet-Draft DNRD Objects Mapping July 2013 are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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. BEGIN IDN Language Comma-Separated Values (CSV) Object Arias, et al. Expires February 1, 2014 [Page 126] Internet-Draft DNRD Objects Mapping July 2013 END 9.12. EPP Parameters Object Copyright (c) 2011 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 Arias, et al. Expires February 1, 2014 [Page 127] Internet-Draft DNRD Objects Mapping July 2013 are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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. BEGIN Registry Data Escrow EPP Parameters schema Arias, et al. Expires February 1, 2014 [Page 128] Internet-Draft DNRD Objects Mapping July 2013 END 9.13. NNDN Object Copyright (c) 2011 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote Arias, et al. Expires February 1, 2014 [Page 129] Internet-Draft DNRD Objects Mapping July 2013 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. BEGIN Registry Data Escrow NNDN provisioning schema Arias, et al. Expires February 1, 2014 [Page 130] Internet-Draft DNRD Objects Mapping July 2013 END Arias, et al. Expires February 1, 2014 [Page 131] Internet-Draft DNRD Objects Mapping July 2013 9.14. CSV NNDN Object Copyright (c) 2013 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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. BEGIN Arias, et al. Expires February 1, 2014 [Page 132] Internet-Draft DNRD Objects Mapping July 2013 NNDN (NNDN's not domain name) (CSV) Object Arias, et al. Expires February 1, 2014 [Page 133] Internet-Draft DNRD Objects Mapping July 2013 END 9.15. Policy Object Copyright (c) 2011 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: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote Arias, et al. Expires February 1, 2014 [Page 134] Internet-Draft DNRD Objects Mapping July 2013 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. BEGIN Registry Data Escrow Policy schema END 9.16. Header Object Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Arias, et al. Expires February 1, 2014 [Page 135] Internet-Draft DNRD Objects Mapping July 2013 Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o 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. o 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. Arias, et al. Expires February 1, 2014 [Page 136] Internet-Draft DNRD Objects Mapping July 2013 BEGIN Registry Data Escrow Header schema END Arias, et al. Expires February 1, 2014 [Page 137] Internet-Draft DNRD Objects Mapping July 2013 10. Internationalization Considerations 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 declaration, use of UTF-8 is RECOMMENDED. 11. IANA Considerations This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. 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 domain namespace: URI: urn:ietf:params:xml:ns:rdeDomain-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 domain XML schema: URI: urn:ietf:params:xml:schema:rdeDomain-1.0 Arias, et al. Expires February 1, 2014 [Page 138] Internet-Draft DNRD Objects Mapping July 2013 Registrant Contact: See the "Author's Address" section of this document. See the "Formal Syntax" section of this document. Registration request for the 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 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 host namespace: URI: urn:ietf:params:xml:ns:rdeHost-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 host XML schema: URI: urn:ietf:params:xml:schema:rdeHost-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 CSV host namespace: URI: urn:ietf:params:xml:ns:csvHost-1.0 Registrant Contact: See the "Author's Address" section of this document. Arias, et al. Expires February 1, 2014 [Page 139] Internet-Draft DNRD Objects Mapping July 2013 XML: None. Namespace URIs do not represent an XML specification. Registration request for the 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 contact namespace: URI: urn:ietf:params:xml:ns:rdeContact-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 contact XML schema: URI: urn:ietf:params:xml:schema:rdeContact-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 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 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 registrar namespace: Arias, et al. Expires February 1, 2014 [Page 140] Internet-Draft DNRD Objects Mapping July 2013 URI: urn:ietf:params:xml:ns:rdeRegistrar-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 registrar XML schema: URI: urn:ietf:params:xml:schema:rdeRegistrar-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 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 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 IDN namespace: URI: urn:ietf:params:xml:ns:rdeIDN-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 IDN XML schema: URI: urn:ietf:params:xml:schema:rdeIDN-1.0 Arias, et al. Expires February 1, 2014 [Page 141] Internet-Draft DNRD Objects Mapping July 2013 Registrant Contact: See the "Author's Address" section of this document. See the "Formal Syntax" section of this document. Registration request for the 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 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. Registration request for the RDE NNDN namespace: URI: urn:ietf:params:xml:ns:rdeNNDN-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 NNDN XML schema: URI: urn:ietf:params:xml:schema:rdeNNDN-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 CSV NNDN namespace: URI: urn:ietf:params:xml:ns:csvNNDN-1.0 Registrant Contact: See the "Author's Address" section of this document. Arias, et al. Expires February 1, 2014 [Page 142] Internet-Draft DNRD Objects Mapping July 2013 XML: None. Namespace URIs do not represent an XML specification. Registration request for the CSV NNDN XML schema: URI: urn:ietf:params:xml:schema:csvNNDN-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 EPP parameters namespace: URI: urn:ietf:params:xml:ns:rdeEppParams-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 EPP parameters XML schema: URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 Registrant Contact: See the "Author's Address" section of this document. See the "Formal Syntax" section of this document. 12. Security Considerations 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 Arias, et al. Expires February 1, 2014 [Page 143] Internet-Draft DNRD Objects Mapping July 2013 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". 13. Acknowledgments Parts of this document are based on EPP [RFC5730] and related RFCs by Scott Hollenbeck. TBD 14. Change History [[RFC Editor: Please remove this section.]] 14.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to -dnrd-objects-mapping-00 1. Added definition for child elements under the element. 2. Added definition for child elements under the element. 3. Added definition for child elements under the element. 4. Rewrote the IDN Variants Handling section to use the variant states as described in ICANN's Study of Issues Related to the Management of IDN Variant TLDs. 5. Renamed to in the . 6. Renamed to in the element. 7. Renamed to in the element. 8. Added element under element. 9. Fixed some typographical errors and omissions. Arias, et al. Expires February 1, 2014 [Page 144] Internet-Draft DNRD Objects Mapping July 2013 14.2. Changes from version 00 to 01 1. Specify OPTIONAL elements in the draft. 2. Added NNDN object to support list of reserved names and different IDN variants models. 3. Removed subordinated host element from the domain object. 4. Added eppParams object. 5. Added variantGenerator element to the domain object. 6. Added lgr to the IDN table object. 14.3. Changes from version 01 to 02 1. Updates to the all objects based on feedback from the list. 2. Start of XML and CSV drafts merge. 3. Added header object. 4. Added report object. 5. Added notification object. 6. Added Data Escrow Agent Extended Verification Process section. 7. Added Notifications from Registries to Third Parties. 8. Added Notifications from Data Escrow Agents to Third Parties. 9. Added FULL, DIFF deposit examples using the XML model only. 14.4. Changes from version 02 to 03 1. Remove authinfo from the XML Schema. 2. Resend attribute is now an element 3. Scope attribute added to policy object. 14.5. Changes from version 03 to 04 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft-arias-noguchi-dnrd-objects-mapping-02. Arias, et al. Expires February 1, 2014 [Page 145] Internet-Draft DNRD Objects Mapping July 2013 2. Changed the cksum attribute of to use CRC32 and changed all of the sample cksum values to use CRC32, based on feedback from David Kipling. 3. Changed the optional element to be an optional "sep" attribute value of the element with a default value of "," based on feedback from David Kipling. 4. Added support for the optional "parent" attribute for the to the CSV fields to indicate a field as a reference to a parent object, based on feedback from David Kipling. 5. Added support for the CSV model for the NNDN. 6. Added support to delete hosts based on roid. 7. Added mirrored state to NNDN 8. Minor fixes to XML XSDs. 9. The Report and Notification objects were moved to draft-lozano-icann-registry-interfaces 10. The section Data escrow notifications was moved to draft-lozano-icann-registry-interfaces 11. Removed references to the , , and from the "hostStatuses" and "hostAddresses" CSV files. 12. Removed references to the , , and from the "contactStatuses" CSV file. 13. Removed references to the , , and from the "domainContacts", "domainStatuses", and "domainNameServers" CSV files. 14. Changed to . 15. Replaced use of to new field in the "domain", "idnLanguage", and "NNDN" CSV files. 16. Replaced use of with in the "host" element. 17. Changed the foreign key of the hosts to use instead of and removed use of in the "domainNameServers", "hostStatuses", and "hostAddresses" CSV Arias, et al. Expires February 1, 2014 [Page 146] Internet-Draft DNRD Objects Mapping July 2013 files. 18. Added use of the MUST keyword for CSV fields that are required to be supported in an EPP based system. 19. Removed use of the field element for the "registrar" CSV file. 20. Added definition of field element. 15. Example of a full deposit using the XML model Example of a full deposit using the XML model: 2010-10-17T00:00:00Z 1.0 urn:ietf:params:xml:ns:rdeHeader-1.0 urn:ietf:params:xml:ns:rdeContact-1.0 urn:ietf:params:xml:ns:rdeHost-1.0 urn:ietf:params:xml:ns:rdeDomain-1.0 urn:ietf:params:xml:ns:rdeRegistrar-1.0 urn:ietf:params:xml:ns:rdeIDN-1.0 Arias, et al. Expires February 1, 2014 [Page 147] Internet-Draft DNRD Objects Mapping July 2013 urn:ietf:params:xml:ns:rdeNNDN-1.0 urn:ietf:params:xml:ns:rdeEppParams-1.0 test 2 1 1 1 1 1 1 example1.test Dexample1-TEST jd1234 sh8013 sh8013 ns1.example.com ns1.example1.test RegistrarX RegistrarX Arias, et al. Expires February 1, 2014 [Page 148] Internet-Draft DNRD Objects Mapping July 2013 1999-04-03T22:00:00.0Z 2015-04-03T22:00:00.0Z example2.test Dexample2-TEST jd1234 sh8013 sh8013 RegistrarX RegistrarX 1999-04-03T22:00:00.0Z 2015-04-03T22:00:00.0Z ns1.example1.test Hns1_example_test-TEST 192.0.2.2 192.0.2.29 1080:0:0:0:8:800:200C:417A RegistrarX RegistrarX 1999-05-08T12:10:00.0Z RegistrarX 2009-10-03T09:34:00.0Z sh8013 Csh8013-TEST John Doe Example Inc. 123 Example Dr. Arias, et al. Expires February 1, 2014 [Page 149] Internet-Draft DNRD Objects Mapping July 2013 Suite 100 Dulles VA 20166-6503 US +1.7035555555 +1.7035555556 jdoe@example.test RegistrarX RegistrarX 2009-09-13T08:01:00.0Z RegistrarX 2009-11-26T09:10:00.0Z 2009-12-03T09:05:00.0Z RegistrarX Registrar X 123 ok 123 Example Dr. Suite 100 Dulles VA 20166-6503 US Arias, et al. Expires February 1, 2014 [Page 150] Internet-Draft DNRD Objects Mapping July 2013 +1.7035555555 +1.7035555556 jdoe@example.test http://www.example.test whois.example.test http://whois.example.test 2005-04-23T11:49:00.0Z 2009-02-17T17:51:00.0Z http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html http://registro.br/dominio/regras.html xn--exampl-gva.test pt-BR example1.test withheld 2005-04-23T11:49:00.0Z 1.0 en urn:ietf:params:xml:ns:domain-1.0 urn:ietf:params:xml:ns:contact-1.0 Arias, et al. Expires February 1, 2014 [Page 151] Internet-Draft DNRD Objects Mapping July 2013 urn:ietf:params:xml:ns:host-1.0 urn:ietf:params:xml:ns:rgp-1.0 urn:ietf:params:xml:ns:secDNS-1.1 16. Example of differential deposit using the XML model Example of a differential deposit using the XML model: 2010-10-17T00:00:00Z 1.0 urn:ietf:params:xml:ns:rdeHeader-1.0 urn:ietf:params:xml:ns:rdeContact-1.0 urn:ietf:params:xml:ns:rdeHost-1.0 urn:ietf:params:xml:ns:rdeDomain-1.0 urn:ietf:params:xml:ns:rdeRegistrar-1.0 urn:ietf:params:xml:ns:rdeIDN-1.0 urn:ietf:params:xml:ns:rdeNNDN-1.0 urn:ietf:params:xml:ns:rdeEppParams-1.0 example2.test test 1 1 1 1 1 1 1 17. Example of a full deposit using the CSV model Example of a full deposit using the CSV model: Arias, et al. Expires February 1, 2014 [Page 154] Internet-Draft DNRD Objects Mapping July 2013 2010-10-18T00:00:00Z 1.0 urn:ietf:params:xml:ns:csvDomain-1.0 urn:ietf:params:xml:ns:csvHost-1.0 urn:ietf:params:xml:ns:csvContact-1.0 urn:ietf:params:xml:ns:csvRegistrar-1.0 urn:ietf:params:xml:ns:csvIDN-1.0 urn:ietf:params:xml:ns:csvNNDN-1.0 urn:ietf:params:xml:ns:rdeEppParams-1.0 test 4 2 2 1 2 1 1 Arias, et al. Expires February 1, 2014 [Page 155] Internet-Draft DNRD Objects Mapping July 2013 domain-YYYYMMDD.csv domainContacts-YYYYMMDD.csv domainStatuses-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 156] Internet-Draft DNRD Objects Mapping July 2013 domainNameServers-YYYYMMDD.csv dnssec-ds-YYYYMMDD.csv dnssec-key-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 157] Internet-Draft DNRD Objects Mapping July 2013 domainTransfer-YYYYMMDD.csv host-YYYYMMDD.csv hostStatuses-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 158] Internet-Draft DNRD Objects Mapping July 2013 hostAddresses-YYYYMMDD.csv contact-YYYYMMDD.csv contactStatuses-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 159] Internet-Draft DNRD Objects Mapping July 2013 contactPostal-YYYYMMDD.csv contactTransfer-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 160] Internet-Draft DNRD Objects Mapping July 2013 contactDisclose-YYYYMMDD.csv registrar-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 161] Internet-Draft DNRD Objects Mapping July 2013 idnLanguage-YYYYMMDD.csv NNDN-YYYYMMDD.csv 1.0 en urn:ietf:params:xml:ns:domain-1.0 urn:ietf:params:xml:ns:host-1.0 urn:ietf:params:xml:ns:contact-1.0 urn:ietf:params:xml:ns:secDNS-1.1 urn:ietf:params:xml:ns:rgp-1.0 Arias, et al. Expires February 1, 2014 [Page 162] Internet-Draft DNRD Objects Mapping July 2013 18. Example of differential deposit using the CSV model Example of a differential deposit using the CSV model: 2010-10-18T00:00:00Z 1.0 urn:ietf:params:xml:ns:csvDomain-1.0 urn:ietf:params:xml:ns:csvHost-1.0 urn:ietf:params:xml:ns:csvContact-1.0 urn:ietf:params:xml:ns:csvRegistrar-1.0 urn:ietf:params:xml:ns:csvIDN-1.0 domain-delete-YYYYMMDD.csv domainContacts-delete-YYYYMMDD.csv domainStatuses-delete-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 164] Internet-Draft DNRD Objects Mapping July 2013 domainNameServers-delete-YYYYMMDD.csv dnssec-ds-delete-YYYYMMDD.csv dnssec-key-delete-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 165] Internet-Draft DNRD Objects Mapping July 2013 domainTransfer-delete-YYYYMMDD.csv host-delete-YYYYMMDD.csv hostStatuses-delete-YYYYMMDD.csv hostAddresses-delete-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 166] Internet-Draft DNRD Objects Mapping July 2013 contact-delete-YYYYMMDD.csv contactStatuses-delete-YYYYMMDD.csv contactPostal-delete-YYYYMMDD.csv contactTransfer-delete-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 167] Internet-Draft DNRD Objects Mapping July 2013 contactDisclose-delete-YYYYMMDD.csv registrar-delete-YYYYMMDD.csv idnLanguage-delete-YYYYMMDD.csv NNDN-delete-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 168] Internet-Draft DNRD Objects Mapping July 2013 test 4 2 2 1 2 1 1 domain-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 169] Internet-Draft DNRD Objects Mapping July 2013 domainContacts-YYYYMMDD.csv domainStatuses-YYYYMMDD.csv domainNameServers-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 170] Internet-Draft DNRD Objects Mapping July 2013 dnssec-YYYYMMDD.csv domainTransfer-YYYYMMDD.csv host-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 171] Internet-Draft DNRD Objects Mapping July 2013 hostStatuses-YYYYMMDD.csv hostAddresses-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 172] Internet-Draft DNRD Objects Mapping July 2013 contact-YYYYMMDD.csv contactStatuses-YYYYMMDD.csv contactPostal-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 173] Internet-Draft DNRD Objects Mapping July 2013 contactTransfer-YYYYMMDD.csv contactDisclose-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 174] Internet-Draft DNRD Objects Mapping July 2013 registrar-YYYYMMDD.csv idnLanguage-YYYYMMDD.csv NNDN-YYYYMMDD.csv Arias, et al. Expires February 1, 2014 [Page 175] Internet-Draft DNRD Objects Mapping July 2013 1.0 en urn:ietf:params:xml:ns:domain-1.0 urn:ietf:params:xml:ns:host-1.0 urn:ietf:params:xml:ns:contact-1.0 urn:ietf:params:xml:ns:secDNS-1.1 urn:ietf:params:xml:ns:rgp-1.0 19. References Arias, et al. Expires February 1, 2014 [Page 176] Internet-Draft DNRD Objects Mapping July 2013 19.1. Normative References [ISO-3166-1] International Organization for Standardization, "Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes", ISO Standard 3166, November 2006. [ITU-E164] International Telecommunication Union, "The international public telecommunication numbering plan", ITU-T Recommendation E.164, February 2005. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, July 2002. [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)", RFC 3915, September 2004. [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, August 2009. [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, August 2009. [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Host Mapping", STD 69, RFC 5732, August 2009. [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Contact Mapping", STD 69, RFC 5733, August 2009. [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)", RFC 5910, May 2010. 19.2. Informative References [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, Arias, et al. Expires February 1, 2014 [Page 177] Internet-Draft DNRD Objects Mapping July 2013 September 2004. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. [variantTLDsReport] Internet Corporation for Assigned Names and Numbers (ICANN), "A Study of Issues Related to the Management of IDN Variant TLDs", February 2012, . URIs [1] Authors' Addresses Francisco Arias Internet Corporation for Assigned Names and Numbers 12025 Waterfront Drive, Suite 300 Los Angeles 90292 United States of America Phone: +1.310.823.9358 Email: francisco.arias@icann.org Gustavo Lozano Internet Corporation for Assigned Names and Numbers 12025 Waterfront Drive, Suite 300 Los Angeles 90292 United States of America Phone: +1.310.823.9358 Email: gustavo.lozano@icann.org Arias, et al. Expires February 1, 2014 [Page 178] Internet-Draft DNRD Objects Mapping July 2013 Shoji Noguchi Japan Registry Services Co., Ltd. Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda Chiyoda-ku, Tokyo 101-0065 Japan Phone: +81.3.5215.8451 Email: noguchi@jprs.co.jp James Gould VeriSign, Inc. 12061 Bluemont Way Reston 20190 United States of America Email: jgould@verisign.com Chethan Thippeswamy VeriSign, Inc. 12061 Bluemont Way Reston 20190 United States of America Email: cthippeswamy@verisign.com Arias, et al. Expires February 1, 2014 [Page 179]