Network Working Group F. Arias Internet-Draft ICANN Intended status: Standards Track S. Noguchi Expires: September 7, 2012 JPRS March 6, 2012 Domain Name Registration Data (DNRD) Objects Mapping draft-arias-noguchi-dnrd-objects-mapping-00 Abstract This document specifies the format and contents of Domain Name Registration Data (DNRD) Escrow deposits. Specified in Extensible Markup Language (XML), the mapping defines Registration Data Escrow (RDE) deposit syntax and semantics. 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 September 7, 2012. Copyright Notice Copyright (c) 2012 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 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. Arias & Noguchi Expires September 7, 2012 [Page 1] Internet-Draft DNRD Objects Mapping March 2012 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. General Conventions . . . . . . . . . . . . . . . . . . . . . 3 3.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 3 3.2. Country names . . . . . . . . . . . . . . . . . . . . . . 3 3.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 3 3.4. IP addresses . . . . . . . . . . . . . . . . . . . . . . . 3 4. Object Description . . . . . . . . . . . . . . . . . . . . . . 4 4.1. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 4 4.2. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 8 4.3. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 10 4.4. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 14 4.5. RDE IDN Table Reference . . . . . . . . . . . . . . . . . 17 4.6. RDE IDN object . . . . . . . . . . . . . . . . . . . . . . 17 4.7. RDE EPP Parameters object . . . . . . . . . . . . . . . . 19 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 22 5.1. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 22 5.2. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 25 5.3. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 28 5.4. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 31 5.5. RDE IDN and IDN Table Reference Objects . . . . . . . . . 34 5.6. EPP Parameters Object . . . . . . . . . . . . . . . . . . 37 6. Extension Guidelines . . . . . . . . . . . . . . . . . . . . . 39 7. Internationalization Considerations . . . . . . . . . . . . . 39 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39 9. Security Considerations . . . . . . . . . . . . . . . . . . . 42 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 43 11. Change History . . . . . . . . . . . . . . . . . . . . . . . . 43 11.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . . 43 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43 12.1. Normative References . . . . . . . . . . . . . . . . . . . 43 12.2. Informative References . . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 45 Arias & Noguchi Expires September 7, 2012 [Page 2] Internet-Draft DNRD Objects Mapping March 2012 1. Introduction This document specifies a format and contents of Domain Name Registration Data Escrow deposits. TBD 2. 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, RFC 2119 [RFC2119]. 3. General Conventions 3.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. 3.2. Country names Country identifiers SHALL be represented using two character identifiers as specified in [ISO-3166-1]. 3.3. Telephone numbers Telephone numbers (both voice and fax) 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. 3.4. IP addresses IP addresses syntax MUST conform either to, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 Addressing Architecture [RFC4291], for IPv6 addresses. Arias & Noguchi Expires September 7, 2012 [Page 3] Internet-Draft DNRD Objects Mapping March 2012 4. Object Description This section describes the base objects defined in EPP: domains, hosts and contacts with the addition of registrars, IDN Table References, IDNs and EPP parameters. 4.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. 4.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 some additions, including the 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]. 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 One or more elements that contain the current status descriptors associated with the domain name. o Zero or more element to represent the different states that a domain name can be in as a result of grace period processing as specified in [RFC3915]. o A element that contain the identifier for the human or organizational social information object associated as the holder of the domain name object. o One or more elements that contain identifiers for the human or organizational social information objects associated with the domain name object. o An element that contains the fully qualified names of the delegated host objects or host attributes (name servers) Arias & Noguchi Expires September 7, 2012 [Page 4] Internet-Draft DNRD Objects Mapping March 2012 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 Zero or more elements that contain the fully qualified names of the subordinate host objects that exist under this superordinate domain name 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 domain name object. o A element that contains the date and time of the domain name object creation. o An 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. o An 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 element that contains the date and time identifying the end (expiration) of the domain name object's registration period. o A element that contains the deletion date for the domain. This element is used by registries that support the Domain Registry Grace Period as specified in [RFC3915]. This element MUST be present if the domain name has been deleted, but not yet purged from the registry repository. o An element that contains authorization information associated with the domain name object. o A element that contains the public key information associated with Domain Name System security (DNSSEC) extensions for the domain name as specified in [RFC5910]. o A element that contains the following child elements related to the last transfer request of the domain name object: * A element that contains the state of the most recent transfer request. Arias & Noguchi Expires September 7, 2012 [Page 5] Internet-Draft DNRD Objects Mapping March 2012 * A element that contains the identifier of the registrar that requested the domain name object transfer. * 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 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 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: Arias & Noguchi Expires September 7, 2012 [Page 6] Internet-Draft DNRD Objects Mapping March 2012 ... pinguino.test Dpinguino-TEST jd1234 sh8013 sh8013 ns1.example.com ns1.example.net ns1.pinguino.test ns2.pinguino.test clientX clientY 1999-04-03T22:00:00.0Z clientX 2009-12-03T09:05:00.0Z 2015-04-03T22:00:00.0Z 2fooBAR 604800 12345 7 1 93358db22e956a451eb5ae8d2ec39526ca6a87b9 pending clientW 2011-03-08T19:38:00.0Z clientX 2011-03-13T23:59:59.0Z 2016-04-03T22:00:00.0Z ... Arias & Noguchi Expires September 7, 2012 [Page 7] Internet-Draft DNRD Objects Mapping March 2012 4.1.2. object The element contains the fully qualified domain name that was deleted and purged. Example of object: ... ... foo.test bar.test ... ... 4.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. 4.2.1. object The RDE host object is based on the EPP host response for an authorized client (see Section 3.1.2. of [RFC5732]). The 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. Arias & Noguchi Expires September 7, 2012 [Page 8] Internet-Draft DNRD Objects Mapping March 2012 o A element that contains the identifier of the registrar that created the host object. o A element that contains the date and time of host-object creation. o An 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. o An 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 A element that contains the date and time of the most recent successful host-object transfer. This element MUST NOT be present if the host object has never been transferred. Note that host objects are not transferred directly; host objects are transferred implicitly when the host object's superordinate domain object is transferred. Host objects that are subject to transfer when transferring a domain object are listed in the element subordinate to the element described above. Example of object: ... ns1.example.test Hns1_example_test-TEST 192.0.2.2 192.0.2.29 1080:0:0:0:8:800:200C:417A clientY clientX 1999-05-08T12:10:00.0Z clientX 2009-10-03T09:34:00.0Z 2007-01-08T09:19:00.0Z ... Arias & Noguchi Expires September 7, 2012 [Page 9] Internet-Draft DNRD Objects Mapping March 2012 4.2.2. object The element contains the fully qualified domain name of a host that was deleted. Example of object: ... ... ns1.example.test ... ... 4.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. 4.3.1. object The contact object is based on the EPP contact response for an authorized client (see 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 element contains the following child elements: o An 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 Arias & Noguchi Expires September 7, 2012 [Page 10] Internet-Draft DNRD Objects Mapping March 2012 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 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 elements that contain the contact's street address. + A element that contains the contact's city. + A element that contains the contact's state or province. + A element that contains the contact's postal code. + A element that contains the contact's two-letter country code. o A element that contains the contact's voice telephone number. o A 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. o A element that contains the date and time of contact- object creation. o An 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. Arias & Noguchi Expires September 7, 2012 [Page 11] Internet-Draft DNRD Objects Mapping March 2012 o An 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 element that contains authorization information associated with the contact object. o A element that identifies elements that require 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. o A 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. * 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 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. Example object: Arias & Noguchi Expires September 7, 2012 [Page 12] Internet-Draft DNRD Objects Mapping March 2012 ... sh8013 Csh8013-TEST John Doe Example Inc. 123 Example Dr. Suite 100 Dulles VA 20166-6503 US +1.7035555555 +1.7035555556 jdoe@example.test clientY clientX 2009-09-13T08:01:00.0Z clientX 2009-11-26T09:10:00.0Z 2fooBAR pending clientW 2011-03-08T19:38:00.0Z clientX 2011-03-13T23:59:59.0Z ... 4.3.2. object The element contains the id of a contact that was deleted. Arias & Noguchi Expires September 7, 2012 [Page 13] Internet-Draft DNRD Objects Mapping March 2012 Example of object: ... ... sh8013-TEST co8013-TEST ... ... 4.4. RDE Registrar Object The RDE registrar object is based on the EPP contact name mapping previously described. 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. 4.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 OPTIONAL element that contains the ID assigned by ICANN. 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: * An OPTIONAL element that contains the name of the organization with which the registrar is affiliated. Arias & Noguchi Expires September 7, 2012 [Page 14] Internet-Draft DNRD Objects Mapping March 2012 * 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 A 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 listenin on TCP port 43 as specified in [RFC3912]. * An OPTIONAL element that contains the name of the registrar WHOIS server listenin on TCP port 80/443. o One or more OPTIONAL elements that contain identifiers for the human or organizational social information objects associated with the registrar object. o A element that contains the date and time of registrar- object creation. o A 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. Arias & Noguchi Expires September 7, 2012 [Page 15] Internet-Draft DNRD Objects Mapping March 2012 o An OPTIONAL element that contains authorization information associated with the registar object to allow access to registry systems. This specification describes password-based authorization information, though other mechanisms are possible. Example of object: ... clientX RclientX-TEST 123 John Doe Example Inc. 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 https://whois.example.test rr0013 rr0012 2005-04-23T11:49:00.0Z 2009-02-17T17:51:00.0Z tHisaPaSSw ... 4.4.2. object The element contains the id of a registrar that was deleted. Arias & Noguchi Expires September 7, 2012 [Page 16] Internet-Draft DNRD Objects Mapping March 2012 Example of object: ... ... agnt0001-TEST ... ... 4.5. RDE IDN Table Reference The RDE Internationalized Domain Names (IDN) Table reference is a pseudobject that is used to provide a short reference to the IDN Table used in IDN registrations. The element has an "id" attribute that is used to uniquely identify an IDN Table stored externally. The has only one child element, that contains the URL of the IDN table that is being referenced. Example of object: ... http://www.iana.org/domains/idn-tables/tables/cl_latn_1.0.html ... 4.6. RDE IDN object 4.6.1. IDN Variants Handling Depending on the Registration Policy in place in the Registry; for a particular IDN there may be multiple variant names either canonical, blocked, withheld, allocated, mirrored, or delegated. See Section 5 of [variantTLDsReport] for further detail on variant name states. IDN variant names will be tagged as follows: 1. If the IDN is considered to be the base or primary string upon which the IDN variants are formed, the IDN object will be tagged as "canonical". Arias & Noguchi Expires September 7, 2012 [Page 17] Internet-Draft DNRD Objects Mapping March 2012 2. If the IDN variant is considered undesirable for registration (i.e., unavailable for allocation to anyone), the variant will be tagged as "blocked". 3. If only the holder of the canonical domain name is allowed to register the IDN variant but it is not currently allocated, the variant will be tagged as "withheld". 4. If the IDN variant is allocated to the holder of the canonical domain name though, it is not active in the DNS, the variant will be tagged as "allocated". 5. If the IDN variant is allocated to the holder of the canonical domain name, it is active in the DNS, and also has a mirroring requirement, the variant will be tagged as "mirrored". 6. If the IDN variant is allocated to the holder of the cannonical domain name, it has been delegated, but there is no requirement for the two names to be mirrored, the variant will be tagged as "delegated". IDN variants tagged as "blocked" or "withheld" SHOULD be escrowed if explicitly declared and known. All other variants MUST be escrowed. 4.6.2. object The element contains the following child elements: o An element that contains the ASCII Compatible Encoding (ACE) of an IDN. o An element that contains the name of the IDN in Unicode character set. It MUST be provided if available. o A element that indicates the type of variant this IDN is: canonical, blocked, withheld, allocated, mirrored, or delegated. See Section 4.6.1 above. o An element that references the IDN Table used for the IDN. This corresponds to the "id" attribute of the element. o A element that contains the repository object identifier of the corresponding domain object, if there is one. It MUST be provided if the domain object exists. o A element that contains the repository object identifier of the canonical domain name. It MUST be provided if Arias & Noguchi Expires September 7, 2012 [Page 18] Internet-Draft DNRD Objects Mapping March 2012 the IDN is NOT the canonical domain name. Example of object: ... xn--pingino-q2a.test pingueino.test withheld cl-es Dpinguino-TEST ... 4.6.3. object The element contains the ACE of an IDN that was deleted, i.e., the . Example of object: ... ... xn--pingino-q2a.test ... ... 4.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. Arias & Noguchi Expires September 7, 2012 [Page 19] Internet-Draft DNRD Objects Mapping March 2012 o One or more elements that contain namespace URIs representing the objects that the registry's EPP server is capable 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: Arias & Noguchi Expires September 7, 2012 [Page 20] Internet-Draft DNRD Objects Mapping March 2012 ... 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 & Noguchi Expires September 7, 2012 [Page 21] Internet-Draft DNRD Objects Mapping March 2012 5. 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. 5.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. 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 & Noguchi Expires September 7, 2012 [Page 23] Internet-Draft DNRD Objects Mapping March 2012 END 5.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. Arias & Noguchi Expires September 7, 2012 [Page 25] Internet-Draft DNRD Objects Mapping March 2012 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 host provisioning schema Arias & Noguchi Expires September 7, 2012 [Page 26] Internet-Draft DNRD Objects Mapping March 2012 Arias & Noguchi Expires September 7, 2012 [Page 27] Internet-Draft DNRD Objects Mapping March 2012 END 5.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 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 & Noguchi Expires September 7, 2012 [Page 30] Internet-Draft DNRD Objects Mapping March 2012 END 5.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 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 registrar provisioning schema Arias & Noguchi Expires September 7, 2012 [Page 32] Internet-Draft DNRD Objects Mapping March 2012 Arias & Noguchi Expires September 7, 2012 [Page 33] Internet-Draft DNRD Objects Mapping March 2012 END 5.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. 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 & Noguchi Expires September 7, 2012 [Page 34] Internet-Draft DNRD Objects Mapping March 2012 Registry Data Escrow IDN provisioning schema Arias & Noguchi Expires September 7, 2012 [Page 35] Internet-Draft DNRD Objects Mapping March 2012 Arias & Noguchi Expires September 7, 2012 [Page 36] Internet-Draft DNRD Objects Mapping March 2012 END 5.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 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 & Noguchi Expires September 7, 2012 [Page 37] Internet-Draft DNRD Objects Mapping March 2012 Registry Data Escrow EPP Parameters schema Arias & Noguchi Expires September 7, 2012 [Page 38] Internet-Draft DNRD Objects Mapping March 2012 END 6. Extension Guidelines TBD 7. 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. 8. 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 namespace: URI: urn:ietf:params:xml:ns:rde-1.0 Registrant Contact: See the "Author's Address" section of this document. Arias & Noguchi Expires September 7, 2012 [Page 39] Internet-Draft DNRD Objects Mapping March 2012 XML: None. Namespace URIs do not represent an XML specification. Registration request for the RDE XML schema: URI: urn:ietf:params:xml:schema:rde-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 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 & Noguchi Expires September 7, 2012 [Page 40] Internet-Draft DNRD Objects Mapping March 2012 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 & Noguchi Expires September 7, 2012 [Page 41] Internet-Draft DNRD Objects Mapping March 2012 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. 9. 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 & Noguchi Expires September 7, 2012 [Page 42] Internet-Draft DNRD Objects Mapping March 2012 RECOMMENDED to ensure not only the file was transmitted correctly from the Registry, but also the contents are also "meaningful". 10. Acknowledgments Parts of this document are based on EPP [RFC5730] and related RFCs by Scott Hollenbeck. TBD 11. Change History [[RFC Editor: Please remove this section.]] 11.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. 12. References 12.1. Normative References [I-D.arias-noguchi-registry-data-escrow] Arias, F. and S. Noguchi, "Domain Name Data Escrow Specification", draft-arias-noguchi-registry-data-escrow-02 (work in Arias & Noguchi Expires September 7, 2012 [Page 43] Internet-Draft DNRD Objects Mapping March 2012 progress), March 2011. [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. [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. 12.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, September 2004. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Arias & Noguchi Expires September 7, 2012 [Page 44] Internet-Draft DNRD Objects Mapping March 2012 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 4676 Admiralty Way, Suite 330 Marina del Rey 90292 United States of America Phone: +1.310.823.9358 Email: francisco.arias@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 & Noguchi Expires September 7, 2012 [Page 45]