Network Working Group F. Arias Internet-Draft G. Lozano Intended status: Standards Track ICANN Expires: October 6, 2013 S. Noguchi JPRS J. Gould C. Thippeswamy VeriSign April 04, 2013 Domain Name Registration Data (DNRD) Objects Mapping draft-arias-noguchi-dnrd-objects-mapping-03 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 October 6, 2013. 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 October 6, 2013 [Page 1] Internet-Draft DNRD Objects Mapping April 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. IP addresses . . . . . . . . . . . . . . . . . . . . . . . 6 5. Object Description . . . . . . . . . . . . . . . . . . . . . . 6 5.1. RDE Domain object . . . . . . . . . . . . . . . . . . . . 6 5.2. RDE Host object . . . . . . . . . . . . . . . . . . . . . 10 5.3. RDE Contact object . . . . . . . . . . . . . . . . . . . . 12 5.4. RDE Registrar object . . . . . . . . . . . . . . . . . . . 16 5.5. RDE IDN Practices . . . . . . . . . . . . . . . . . . . . 19 5.6. RDE NNDN . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.7. RDE EPP Parameters object . . . . . . . . . . . . . . . . 21 5.8. RDE Policy object . . . . . . . . . . . . . . . . . . . . 23 5.9. Header object . . . . . . . . . . . . . . . . . . . . . . 23 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 24 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 25 8.1. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 25 8.2. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 28 8.3. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 30 8.4. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 32 8.5. RDE IDN and IDN Table Reference Objects . . . . . . . . . 36 8.6. EPP Parameters Object . . . . . . . . . . . . . . . . . . 38 8.7. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 41 8.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 43 8.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 44 8.10. Report Object . . . . . . . . . . . . . . . . . . . . . . 47 8.11. Notification Object . . . . . . . . . . . . . . . . . . . 48 9. Internationalization Considerations . . . . . . . . . . . . . 50 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 11. Security Considerations . . . . . . . . . . . . . . . . . . . 53 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 54 13. Change History . . . . . . . . . . . . . . . . . . . . . . . . 54 13.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . . 54 13.2. Changes from version 00 to 01 . . . . . . . . . . . . . . 54 Arias, et al. Expires October 6, 2013 [Page 2] Internet-Draft DNRD Objects Mapping April 2013 13.3. Changes from version 01 to 02 . . . . . . . . . . . . . . 55 13.4. Changes from version 02 to 03 . . . . . . . . . . . . . . 55 14. Example of a full deposit using the XML model only . . . . . . 55 15. Example of differential deposit using the XML model only . . . 60 16. Data escrow agent extended verification process . . . . . . . 62 17. Data escrow notifications . . . . . . . . . . . . . . . . . . 62 17.1. Notifications from Registry Operators to Third Parties . . 62 17.2. Notifications from Data Escrow Agents to Third Parties . . 64 18. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66 18.1. Normative References . . . . . . . . . . . . . . . . . . . 66 18.2. Informative References . . . . . . . . . . . . . . . . . . 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 68 Arias, et al. Expires October 6, 2013 [Page 3] Internet-Draft DNRD Objects Mapping April 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 practices: Internationalized Domain Names (IDN) included in the Domain Object Data Escrow include references to the languages rules that define the set of character code points allowed for a specific language. o EPP parameters: Definition of the specific EPP parameters supported by the Registry Operator. o Header: Used to specify counters of objects in the SRS 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 October 6, 2013 [Page 4] Internet-Draft DNRD Objects Mapping April 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. o CSV: The CSV model uses XML to define the data escrow format of the data contained in referenced Comma-Separated Values (CSV) files. 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 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. Arias, et al. Expires October 6, 2013 [Page 5] Internet-Draft DNRD Objects Mapping April 2013 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. 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. 5. Object Description This section describes the base objects supported by this specification: 5.1. RDE Domain object The RDE domain object is based on the EPP domain name mapping specified in [RFC5731]. There are two elements used in this format related to domains: the domain object per se, used inside the element and the object used inside the element. 5.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 Arias, et al. Expires October 6, 2013 [Page 6] Internet-Draft DNRD Objects Mapping April 2013 [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 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 Arias, et al. Expires October 6, 2013 [Page 7] Internet-Draft DNRD Objects Mapping April 2013 [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. * A element that contains the state of the most recent transfer request. Arias, et al. Expires October 6, 2013 [Page 8] Internet-Draft DNRD Objects Mapping April 2013 * 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 October 6, 2013 [Page 9] Internet-Draft DNRD Objects Mapping April 2013 5.1.2. object The element contains the fully qualified domain name that was deleted and purged. Example of object: ... ... foo.test bar.test ... ... 5.2. RDE Host object The RDE host object is based on the EPP host name mapping in [RFC5732]. There are two elements used in this format related to hosts: the host object per se, used inside the element and the object used inside 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. 5.2.1. object 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. Arias, et al. Expires October 6, 2013 [Page 10] Internet-Draft DNRD Objects Mapping April 2013 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: ... 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 ... Arias, et al. Expires October 6, 2013 [Page 11] Internet-Draft DNRD Objects Mapping April 2013 5.2.2. object The element contains the fully qualified domain name of a host that was deleted. Example of object: ... ... ns1.example.test ... ... 5.3. RDE Contact object The RDE contact object is based on the EPP contact name mapping in [RFC5733]. There are two elements used in this format related to contacts: the contact object per se, used inside the element and the object used inside 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. 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. Arias, et al. Expires October 6, 2013 [Page 12] Internet-Draft DNRD Objects Mapping April 2013 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. * 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 Arias, et al. Expires October 6, 2013 [Page 13] Internet-Draft DNRD Objects Mapping April 2013 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 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. Arias, et al. Expires October 6, 2013 [Page 14] Internet-Draft DNRD Objects Mapping April 2013 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: ... 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 Arias, et al. Expires October 6, 2013 [Page 15] Internet-Draft DNRD Objects Mapping April 2013 ... 5.3.2. object The element contains the id of a contact that was deleted. Example of object: ... ... sh8013-TEST co8013-TEST ... ... 5.4. RDE Registrar object The RDE registrar object is the sponsoring client of other RDE objects, for operational purposes MAY be the registry operator. There are two elements used in this format related to registrars: the registrar object per se, used inside the element and the object used inside 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. 5.4.1. object 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. Arias, et al. Expires October 6, 2013 [Page 16] Internet-Draft DNRD Objects Mapping April 2013 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. 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]. Arias, et al. Expires October 6, 2013 [Page 17] Internet-Draft DNRD Objects Mapping April 2013 * 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: ... 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.2. object The element contains the id of a registrar that was deleted. Arias, et al. Expires October 6, 2013 [Page 18] Internet-Draft DNRD Objects Mapping April 2013 Example of object: ... ... agnt0001-TEST ... ... 5.5. RDE IDN Practices The RDE Internationalized Domain Names (IDN) Practices reference is a pseudo-object that is used to provide a short reference to the IDN Table and Policy used in IDN registrations. The element has an "id" attribute that is used to uniquely identify an IDN Table stored externally. 5.5.1. object The OPTIONAL 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 ... Arias, et al. Expires October 6, 2013 [Page 19] Internet-Draft DNRD Objects Mapping April 2013 5.6. RDE NNDN A NNDN (NNDN's not domain name) does not exist as a domain object, however it is stored in the SRS database. NNDNs can optionally be used to store registry reserved names or (blocked or withheld) IDN variants. A NNDN is a lightweight domain-like object that is not linked to a Registrar. A FQDN can only exists as a domain name or NNDN, but not both. 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. object The OPTIONAL element contains the following child elements: o An element that contains the A-label 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 or withheld. * 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". o A element that contains the date and time of the NNDN object creation. Example of object: Arias, et al. Expires October 6, 2013 [Page 20] Internet-Draft DNRD Objects Mapping April 2013 ... xn--exampl-gva.test pt-BR Dexample1-TEST withheld 2005-04-23T11:49:00.0Z ... 5.6.2. object The element contains the ACE of a NNDN that was deleted, i.e., the . Example of object: ... ... xn--pingino-q2a.test ... ... 5.7. RDE EPP Parameters object An OPTIONAL element contains some EPP parameters that may be helpful when rebuilding a registry from the escrow deposits. The element SHOULD be included in Deposits if the registry uses EPP. 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 of managing. Arias, et al. Expires October 6, 2013 [Page 21] Internet-Draft DNRD Objects Mapping April 2013 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 October 6, 2013 [Page 22] Internet-Draft DNRD Objects Mapping April 2013 5.8. RDE Policy object The RDE Policy is a pseudo-object that is used to specify which OPTIONAL elements from this specification are REQUIRED based on the business model of the registry. 5.8.1. object The OPTIONAL contains the following attributes: o 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 RDE Header 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. 5.9.1.
object The
contains the following attributes: o A element that defines TLD being escrowed. o A element that number of objects being escrowed. An uri attribute is used to define the type of object. Example of
object: Arias, et al. Expires October 6, 2013 [Page 23] Internet-Draft DNRD Objects Mapping April 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. 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. 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: Arias, et al. Expires October 6, 2013 [Page 24] Internet-Draft DNRD Objects Mapping April 2013 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. Formal Syntax Seven schemas are presented here. The first schema is the base RDE schema. The second schema defines domain object for RDE. The third schema defines host object for RDE. The fourth schema defines contact object for RDE. The fifth schema defines registrar object for RDE. The sixth schema defines the idnTableRef and IDN objects. The last schema defines the eppParams objects. 8.1. RDE Domain 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. Arias, et al. Expires October 6, 2013 [Page 25] Internet-Draft DNRD Objects Mapping April 2013 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 Domain provisioning schema Arias, et al. Expires October 6, 2013 [Page 26] Internet-Draft DNRD Objects Mapping April 2013 Arias, et al. Expires October 6, 2013 [Page 27] Internet-Draft DNRD Objects Mapping April 2013 END 8.2. 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 "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 Arias, et al. Expires October 6, 2013 [Page 28] Internet-Draft DNRD Objects Mapping April 2013 (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 October 6, 2013 [Page 29] Internet-Draft DNRD Objects Mapping April 2013 END 8.3. 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 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 Arias, et al. Expires October 6, 2013 [Page 30] Internet-Draft DNRD Objects Mapping April 2013 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 October 6, 2013 [Page 31] Internet-Draft DNRD Objects Mapping April 2013 END 8.4. 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 Arias, et al. Expires October 6, 2013 [Page 32] Internet-Draft DNRD Objects Mapping April 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 Arias, et al. Expires October 6, 2013 [Page 33] Internet-Draft DNRD Objects Mapping April 2013 Registry Data Escrow registrar provisioning schema Arias, et al. Expires October 6, 2013 [Page 34] Internet-Draft DNRD Objects Mapping April 2013 Arias, et al. Expires October 6, 2013 [Page 35] Internet-Draft DNRD Objects Mapping April 2013 END 8.5. RDE IDN and 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. Arias, et al. Expires October 6, 2013 [Page 36] Internet-Draft DNRD Objects Mapping April 2013 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 October 6, 2013 [Page 37] Internet-Draft DNRD Objects Mapping April 2013 BEGIN Registry Data Escrow IDN provisioning schema END 8.6. 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 Arias, et al. Expires October 6, 2013 [Page 38] Internet-Draft DNRD Objects Mapping April 2013 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 October 6, 2013 [Page 39] Internet-Draft DNRD Objects Mapping April 2013 BEGIN Registry Data Escrow EPP Parameters schema END Arias, et al. Expires October 6, 2013 [Page 40] Internet-Draft DNRD Objects Mapping April 2013 8.7. 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 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 October 6, 2013 [Page 41] Internet-Draft DNRD Objects Mapping April 2013 Registry Data Escrow NNDN provisioning schema Arias, et al. Expires October 6, 2013 [Page 42] Internet-Draft DNRD Objects Mapping April 2013 END 8.8. 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 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 October 6, 2013 [Page 43] Internet-Draft DNRD Objects Mapping April 2013 BEGIN Registry Data Escrow Policy schema END 8.9. Header 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. Arias, et al. Expires October 6, 2013 [Page 44] Internet-Draft DNRD Objects Mapping April 2013 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 October 6, 2013 [Page 45] Internet-Draft DNRD Objects Mapping April 2013 BEGIN Registry Data Escrow Header schema END Arias, et al. Expires October 6, 2013 [Page 46] Internet-Draft DNRD Objects Mapping April 2013 8.10. Report 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 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Arias, et al. Expires October 6, 2013 [Page 47] Internet-Draft DNRD Objects Mapping April 2013 BEGIN Registry Data Escrow Report schema END 8.11. Notification 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: Arias, et al. Expires October 6, 2013 [Page 48] Internet-Draft DNRD Objects Mapping April 2013 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 October 6, 2013 [Page 49] Internet-Draft DNRD Objects Mapping April 2013 BEGIN Registry Data Escrow Notification schema END 9. 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 Arias, et al. Expires October 6, 2013 [Page 50] Internet-Draft DNRD Objects Mapping April 2013 RECOMMENDED. 10. 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 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 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 RDE contact namespace: Arias, et al. Expires October 6, 2013 [Page 51] Internet-Draft DNRD Objects Mapping April 2013 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 RDE registrar namespace: 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 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 October 6, 2013 [Page 52] Internet-Draft DNRD Objects Mapping April 2013 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. 11. 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 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 Arias, et al. Expires October 6, 2013 [Page 53] Internet-Draft DNRD Objects Mapping April 2013 RECOMMENDED to ensure not only the file was transmitted correctly from the Registry, but also the contents are also "meaningful". 12. Acknowledgments Parts of this document are based on EPP [RFC5730] and related RFCs by Scott Hollenbeck. TBD 13. Change History [[RFC Editor: Please remove this section.]] 13.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. 13.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. Arias, et al. Expires October 6, 2013 [Page 54] Internet-Draft DNRD Objects Mapping April 2013 4. Added eppParams object. 5. Added variantGenerator element to the domain object. 6. Added lgr to the IDN table object. 13.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. 13.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. Example of a full deposit using the XML model only Example of a full deposit using the XML model only: 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 test 2 1 1 1 1 1 1 example1.test Arias, et al. Expires October 6, 2013 [Page 56] Internet-Draft DNRD Objects Mapping April 2013 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 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 Arias, et al. Expires October 6, 2013 [Page 57] Internet-Draft DNRD Objects Mapping April 2013 sh8013 Csh8013-TEST 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 RegistrarX Registrar X 123 ok 123 Example Dr. Suite 100 Dulles VA 20166-6503 US Arias, et al. Expires October 6, 2013 [Page 58] Internet-Draft DNRD Objects Mapping April 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 Dexample1-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 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 October 6, 2013 [Page 59] Internet-Draft DNRD Objects Mapping April 2013 15. Example of differential deposit using the XML model only Example of a differential deposit using the XML model only: 2010-10-17T00:00:00Z Arias, et al. Expires October 6, 2013 [Page 60] Internet-Draft DNRD Objects Mapping April 2013 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 Arias, et al. Expires October 6, 2013 [Page 61] Internet-Draft DNRD Objects Mapping April 2013 16. Data escrow agent extended verification process The Data Escrow Agent MAY perform a extended verification process using the contents of 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 number of objects is equal to the number objects reported in the
element of the escrow deposit of that point in time (watermark). o All contacts linked to domain names are present. o All registrars linked to other objects are present. o A name exists only as a domain name or NNDN. o The elements listed in the element are present. o All idnTableRef definitions linked from other objects are present. 17. Data escrow notifications Data escrowing involves several parties interacting with the objective of restoring the operations of a Domain Registry in case of an emergency. The following section defines several notifications that are suggested to be sent between the interacting parties. The parties based on the notification can know the status of the data escrow deposit even if no access to the data escrow deposit file is available. 17.1. Notifications from Registry Operators to Third Parties Registry Operators may need to notify Third Parties that a data escrow deposit file was sent to the Data Escrow Agent depending on local policy or contractual requirements. Arias, et al. Expires October 6, 2013 [Page 62] Internet-Draft DNRD Objects Mapping April 2013 17.1.1. object The object is used by Registry Operator to notify Third Parties about successful delivery of a data escrow deposit to a Data Escrow Agent. The element contains the following child elements: o An element contains the identifier assigned to this report. It is recommended that the report identifier be the same as the data escrow deposit identifier. o An OPTIONAL element that contains to the value of the resend attribute of the rde deposit. o A element contains the date and time that the data escrow deposit was successful received by the data escrow agent. o An OPTIONAL element contains the date and time that the data escrow deposit was successfully validated by the data escrow agent. o A element is used to identify the kind of deposit: FULL, INCR (Incremental) or DIFF (Differential). o A element contains the date and time of the last FULL data escrow deposit that was successfully validated by the data escrow agent. o A element contains the data-time corresponding to the Timeline Watermark of the deposit. o A
element contains the header of the data escrow deposit. Example object: Arias, et al. Expires October 6, 2013 [Page 63] Internet-Draft DNRD Objects Mapping April 2013 20101017001 0 2010-10-17T01:51:10.0Z 2010-10-17T02:51:10.0Z FULL 2010-10-16 2010-10-17T00:00:00Z test 2 1 1 1 1 1 1 17.2. Notifications from Data Escrow Agents to Third Parties Data Escrow Agents may need to notify Third Parties that a data escrow deposit file was received or it is missing for a specific date depending on local policy or contractual requirements. 17.2.1. object The object is used by Data Escrow Agents to notify Third Parties about successful reception/validation of a data escrow deposit. If multiple deposits are received in a day, a notification MUST be generated for each deposit that was successfully received regardless of the result of the verification process performed by the Data Escrow Agent. Arias, et al. Expires October 6, 2013 [Page 64] Internet-Draft DNRD Objects Mapping April 2013 The element contains the following child elements: o An element contains the reported date. o A element is used to specify the status of . The possible values of status are: valid, invalid and missing. * Valid: The last received data escrow deposit for the specified date in was successfully validated. * Invalid: The last received data escrow deposit for the specified date in was not successfully validated. * Missing: No data escrow deposit was received on the date specified in . o A element it is used by the data escrow agent to provide extended information about the data escrow deposit. The
element MUST be generated by the data escrow agent for a certain point in time (watermark) based on the contents of the escrow deposits. The last full plus all differentials or last full plus last incremental escrow deposits MUST be used to generate
element. Example object: Arias, et al. Expires October 6, 2013 [Page 65] Internet-Draft DNRD Objects Mapping April 2013 2010-10-17 valid 20101017001 0 2010-10-17T02:51:10.0Z 2010-10-17T01:51:10.0Z FULL 2010-10-16 2010-10-17T00:00:00Z test 2 1 1 1 1 1 1 18. References 18.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. Arias, et al. Expires October 6, 2013 [Page 66] Internet-Draft DNRD Objects Mapping April 2013 [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. [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. 18.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. [RFC3743] Konishi, K., Huang, K., Qian, H., and Y. Ko, "Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean", RFC 3743, April 2004. [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, September 2004. [RFC4290] Klensin, J., "Suggested Practices for Registration of Internationalized Domain Names (IDN)", RFC 4290, December 2005. Arias, et al. Expires October 6, 2013 [Page 67] Internet-Draft DNRD Objects Mapping April 2013 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, August 2009. [variantTLDsReport] Internet Corporation for Assigned Names and Numbers (ICANN), "A Study of Issues Related to the Management of IDN Variant TLDs", February 2012, . 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 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 Arias, et al. Expires October 6, 2013 [Page 68] Internet-Draft DNRD Objects Mapping April 2013 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 October 6, 2013 [Page 69]