Domain Name Registration Data (DNRD) Objects Mapping
Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330United States of America90292Marina del Rey+1.310.823.9358francisco.arias@icann.org
Japan Registry Services Co., Ltd.
Chiyoda First Bldg. East 13F, 3-8-1 Nishi-KandaJapan101-0065Chiyoda-ku, Tokyo+81.3.5215.8451noguchi@jprs.co.jp
Applications
data escrowregistrydomain namedomain name registration data
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.
This document specifies a format and contents of Domain Name Registration Data Escrow deposits.
TBD
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 .
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 ,
with no offset from the zero meridian.
Country identifiers SHALL be represented using two character identifiers as specified in
.
Telephone numbers (both voice and fax) SHALL be formatted based on structures defined in
. Telephone numbers described in this specification are character strings
that MUST begin with a plus sign ("+", ASCII value 0x002B), followed by a country code defined in
, followed by a dot (".", ASCII value 0x002E), followed by a sequence of
digits representing the telephone number.
IP addresses syntax MUST conform either to, Internet Protocol , for IPv4
addresses, or IP Version 6 Addressing Architecture , for IPv6 addresses.
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.
The RDE domain object is based on the EPP domain name mapping specified in . There are
two elements used in this format related to domains: the domain object per se, used inside the
<contents> element and the <rdeDomain:delete> object used inside the <deletes> element.
The domain element is based on the EPP domain <info>
response for an authorized client (see Section 3.1.2. of )
with some additions, including the data from an EPP <transfer> Query Response, see
Section 3.1.3. of , RGP status from , and data from
the EPP <secDns:create> command, see Section 5.2.1. of .
The <domain> element contains the following child elements:
A <name> element that contains the fully qualified name of the domain name object.
A <roid> element that contains the repository object identifier assigned to the domain
name object when it was created.
One or more <status> elements that contain the current status descriptors associated
with the domain name.
Zero or more <rgpStatus> element to represent the different states that a domain name can be
in as a result of grace period processing as specified in .
A <registrant> element that contain the identifier for the human or organizational social
information object associated as the holder of the domain name object.
One or more <contact> elements that contain identifiers for the human or organizational
social information objects associated with the domain name object.
An <ns> 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
for a description of the elements used to specify host objects or
host attributes.
Zero or more <host> elements that contain the fully qualified names of the subordinate
host objects that exist under this superordinate domain name object.
A <clID> element that contains the identifier of the sponsoring registrar.
A <crID> element that contains the identifier of the registrar that created the domain
name object.
A <crDate> element that contains the date and time of the domain name object creation.
An <upID> 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 <upDate> 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.
An <exDate> element that contains the date and time identifying the end (expiration) of the
domain name object's registration period.
A <deDate> 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
. This element MUST be present if the domain name has been deleted,
but not yet purged from the registry repository.
An <authInfo> element that contains authorization information associated with the domain
name object.
A <secDNS> element that contains the public key information associated with Domain Name
System security (DNSSEC) extensions for the domain name as specified in .
A <trnData> element that contains the following child elements related to the last transfer
request of the domain name object:
A <trStatus> element that contains the state of the most recent transfer request.
A <reID> element that contains the identifier of the registrar that requested
the domain name object transfer.
A <reDate> element that contains the date and time that the transfer was requested.
An <acID> 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 <acDate> 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 <exDate> 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:
The <rdeDomain:delete> element contains the fully qualified domain name that was deleted and purged.
Example of <rdeDomain:delete> object:
The RDE host object is based on the EPP host name mapping in . There are
two elements used in this format related to hosts: the host object per se, used inside the
<contents> element and the <rdeHost:delete> object used inside the <deletes> element.
The RDE host object is based on the EPP host <info> response for
an authorized client (see Section 3.1.2. of ).
The <host> element contains the following child elements:
A <name> element that contains the fully qualified name of the host object.
A <roid> element that contains the repository object identifier assigned to the host
object when the object was created.
One or more <status> elements that describe the status of the host object.
Zero or more <addr> elements that contain the IP addresses associated with the host object.
A <clID> element that contains the identifier of the sponsoring registrar.
A <crID> element that contains the identifier of the registrar that created the host object.
A <crDate> element that contains the date and time of host-object creation.
An <upID> 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 <upDate> 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.
A <trDate> 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 <host> element
subordinate to the <domain> element described above.
Example of <host> object:
The <rdeHost:delete> element contains the fully qualified domain name of a host
that was deleted.
Example of <rdeHost:delete> object:
The RDE contact object is based on the EPP contact name mapping in . There
are two elements used in this format related to contacts: the contact object per se, used inside the
<contents> element and the <rdeContact:delete> object used inside the <deletes> element.
The contact object is based on the EPP contact <info>
response for an authorized client (see Section 3.1.2. of ) with
some additions including the data from an EPP <transfer> Query Response, see
Section 3.1.3. of .
The <contact> element contains the following child elements:
An <id> element that contains the repository object identifier assigned to the contact
object when the object was created.
One or more <status> elements that describe the status of the contact object.
One or two <postalInfo> 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 <postalInfo> element contains
the following child elements:
A <name> element that contains the name of the individual or role represented by
the contact.
An <org> element that contains the name of the organization with which the contact
is affiliated.
An <addr> element that contains address information associated with the contact.
An <addr> element contains the following child elements:
One, two, or three <street> elements that contain the contact's street
address.
A <city> element that contains the contact's city.
A <sp> element that contains the contact's state or province.
A <pc> element that contains the contact's postal code.
A <cc> element that contains the contact's two-letter country code.
A <voice> element that contains the contact's voice telephone number.
A <fax> element that contains the contact's facsimile telephone number.
An <email> element that contains the contact's email address.
A <clID> element that contains the identifier of the sponsoring registrar.
A <crID> element that contains the identifier of the registrar that created the contact
object.
A <crDate> element that contains the date and time of contact-object creation.
An <upID> 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 <upDate> 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.
An <authInfo> element that contains authorization information associated with the contact
object.
A <disclose> element that identifies elements that require exceptional server-operator
handling to allow or restrict disclosure to third parties. See Section 2.9 of
for a description of the child elements contained within the
<disclose> element.
A <trnData> element that contains the following child elements related to the last transfer
request of the contact object:
A <trStatus> element that contains the state of the most recent transfer request.
A <reID> element that contains the identifier of the registrar that requested
the domain name object transfer.
A <reDate> element that contains the date and time that the transfer was requested.
An <acID> 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 <acDate> 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 <contact> object:
The <rdeContact:delete> element contains the id of a contact that was deleted.
Example of <rdeContact:delete> 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 <contents> element and the <rdeRegistrar:delete> object used inside the
<deletes> element.
The <registrar> element contains the following child elements:
An <id> element that contains the Registry-unique identifier of the
registrar object. This <id> has a superordinate relationship to a subordinate
<clID>, <crID> or <upID> of domain, contact and host objects.
An OPTIONAL <gurid> element that contains the ID assigned by ICANN.
One or two <postalInfo> 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 <postalInfo>
element contains the following child elements:
An OPTIONAL <org> element that contains the name of the
organization with which the registrar is affiliated.
A <addr> element that contains address information associated
with the registrar.
The <addr> element contains the following child elements:
One, two, or three OPTIONAL <street> elements that
contain the registrar's street address.
A <city> element that contains the registrar's
city.
An OPTIONAL <sp> element that contains the
registrar's state or province.
An OPTIONAL <pc> element that contains the
registrar's postal code.
A <cc> element that contains the registrar's
country code.
An OPTIONAL <voice> element that contains the registrar's voice
telephone number.
An OPTIONAL <fax> element that contains the registrar's
facsimile telephone number.
An <email> element that contains the registrar's email address.
A <url> element that contains the registrar's URL.
An OPTIONAL <whoisInfo> elements that contains whois information.
The <whoisInfo> element contains the following child elements:
An OPTIONAL <name> element that contains the name of the registrar
WHOIS server listenin on TCP port 43 as specified in .
An OPTIONAL <url> element that contains the name of the registrar
WHOIS server listenin on TCP port 80/443.
One or more OPTIONAL <contact> elements that contain identifiers for
the human or organizational social information objects associated with the
registrar object.
A <crDate> element that contains the date and time of
registrar-object creation.
A <upDate> 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.
An OPTIONAL <authInfo> 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 <registrar> object:
The <rdeRegistrar:delete> element contains the id of a registrar that was deleted.
Example of <rdeRegistrar:delete> object:
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 <idnTableRef>
element has an "id" attribute that is used to uniquely identify an IDN Table stored externally.
The <idnTableRef> has only one child element, <url> that contains the URL of the
IDN table that is being referenced.
Example of <idnTableRef> object:
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 for further detail on variant name states.
IDN variant names will be tagged as follows:
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".
If the IDN variant is considered undesirable for registration (i.e., unavailable for allocation to
anyone), the variant will be tagged as "blocked".
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".
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".
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".
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.
The <idn> element contains the following child elements:
An <aName> element that contains the ASCII Compatible Encoding (ACE) of an IDN.
An <uName> element that contains the name of the IDN in Unicode character set. It
MUST be provided if available.
A <type> element that indicates the type of variant this IDN is: canonical, blocked,
withheld, allocated, mirrored, or delegated. See above.
An <idnTableId> element that references the IDN Table used for the IDN. This corresponds
to the "id" attribute of the <idnTableRef> element.
A <roid> 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.
A <canonicalRoid> element that contains the repository object identifier of the canonical
domain name. It MUST be provided if the IDN is NOT the canonical domain name.
Example of <idn> object:
The <rdeIDN:delete> element contains the ACE of an IDN that was deleted, i.e., the <aName>.
Example of <rdeIDN:delete> object:
An OPTIONAL <eppParams> 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 <eppParams> children elements is as explained in section
2.4 of . The children of the <eppParams> are as follows:
One or more <version> elements that indicate the EPP versions supported by the
registry.
One or more <lang> elements that indicate the identifiers of the text response
languages supported by the registry's EPP server.
One or more <objURI> elements that contain namespace URIs representing the objects
that the registry's EPP server is capable of managing.
An OPTIONAL <svcExtension> element that contains one or more <extURI>
elements that contain namespace URIs representing object extensions supported by the
registry's EPP server.
A <dcp> element that contains child elements used to describe the server's privacy
policy for data collection and management. See section 2.4 of
for more details.
Example of <eppParams> element object:
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.
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:
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
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:
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
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:
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
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:
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
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:
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
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:
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
TBD
Data Escrow deposits are represented in XML, which provides native support for encoding information
using the Unicode character set and its more compact representations including UTF-8. Conformant XML
processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other
character encodings through use of an "encoding" attribute in an <?xml?> declaration, use of UTF-8
is RECOMMENDED.
This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in .
Fourteen URI assignments have been registered by the IANA.
Registration request for the RDE namespace:
URI: urn:ietf:params:xml:ns:rde-1.0Registrant 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 XML schema:
URI: urn:ietf:params:xml:schema:rde-1.0Registrant 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.0Registrant 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.0Registrant 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.0Registrant 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.0Registrant Contact: See the "Author's Address" section of this document.See the "Formal Syntax" section of this document.Registration request for the RDE contact namespace:
URI: urn:ietf:params:xml:ns:rdeContact-1.0Registrant 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.0Registrant 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.0Registrant 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.0Registrant 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.0Registrant 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.0Registrant 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.0Registrant 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.0Registrant Contact: See the "Author's Address" section of this document.See the "Formal Syntax" section of this document.
This specification does not define the security mechanisms to be used in the transmission of the data escrow
deposits, since it only specifies the minimum necessary to enable the rebuilding of a Registry from
deposits without intervention from the original Registry.
Depending on local policies, some elements or most likely, the whole deposit will be considered confidential. As
such the Registry transmitting the data to the Escrow Agent SHOULD take all the necessary precautions
like encrypting the data itself and/or the transport channel to avoid inadvertent disclosure of private data.
It is also of the utmost importance the authentication of the parties passing data escrow deposit files. The
Escrow Agent SHOULD properly authenticate the identity of the Registry before accepting data escrow
deposits. In a similar manner, the Registry SHOULD authenticate the identity of the Escrow Agent
before submitting any data.
Additionally, the Registry and the Escrow Agent SHOULD use integrity checking mechanisms to ensure the
data transmitted is what the source intended. Validation of the contents by the Escrow Agent is RECOMMENDED
to ensure not only the file was transmitted correctly from the Registry, but also the contents are also
"meaningful".
Parts of this document are based on EPP and related RFCs by Scott Hollenbeck.
TBD
[[RFC Editor: Please remove this section.]]
Added definition for child elements under the <domain> element.Added definition for child elements under the <host> element.Added definition for child elements under the <contact> element.
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.
Renamed <icannID> to <gurid> in the <rdeRegistrar>.Renamed <dnssec> to <secDNS> in the <domain> element.Renamed <transfData> to <trnData> in the <domain> element.Added <whoisInfo> element under <rdeRegistrar> element.Fixed some typographical errors and omissions. Codes for the representation of names of countries and their
subdivisions -- Part 1: Country codes
International Organization for Standardization
The international public telecommunication numbering plan
International Telecommunication UnionA Study of Issues Related to the Management of IDN Variant TLDsInternet Corporation for Assigned Names and Numbers (ICANN)