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 August 31, 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.

Table of Contents

• 1. Introduction
• 2. Terminology
• 3. General Conventions
• 3.1. Date and Time
• 3.2. Country names
• 3.3. Telephone numbers
• 3.4. IP addresses
• 4. Object Description
• 4.1. RDE Domain Object
• 4.1.1. <domain> object
• 4.1.2. <rdeDomain:delete> object
• 4.2. RDE Host Object
• 4.2.1. <host> object
• 4.2.2. <rdeHost:delete> object
• 4.3. RDE Contact Object
• 4.3.1. <contact> object
• 4.3.2. <rdeContact:delete> object
• 4.4. RDE Registrar Object
• 4.4.1. <registrar> object
• 4.4.2. <rdeRegistrar:delete> object
• 4.5. RDE IDN Table Reference
• 4.6. RDE IDN object
• 4.6.1. IDN Variants Handling
• 4.6.2. <idn> object
• 4.6.3. <rdeIDN:delete> object
• 4.7. RDE EPP Parameters object
• 5. Formal Syntax
• 5.1. RDE Domain Object
• 5.2. RDE Host Object
• 5.3. RDE Contact Object
• 5.4. RDE Registrar Object
• 5.5. RDE IDN and IDN Table Reference Objects
• 5.6. EPP Parameters Object
• 6. Extension Guidelines
• 7. Internationalization Considerations
• 8. IANA Considerations
• 9. Security Considerations
• 10. Acknowledgments
• 11. Change History
• 11.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to -dnrd-objects-mapping-00
• 12. References
• 12.1. Normative References
• 12.2. Informative References
• Authors' Addresses

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.

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 <contents> element and the <rdeDomain:delete> object used inside the <deletes> element.

4.1.1. <domain> object

The domain element is based on the EPP domain <info> response for an authorized client (see Section 3.1.2. of [RFC5731]) with some additions, including the data from an EPP <transfer> Query Response, see Section 3.1.3. of [RFC5731], RGP status from [RFC3915], and data from the EPP <secDns:create> command, see Section 5.2.1. of [RFC5910].

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 [RFC3915].
• 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 [RFC5731] 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 [RFC3915]. 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 [RFC5910].
• 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:

...
<rdeDomain:domain>
    <rdeDomain:name>pinguino.test</rdeDomain:name>
    <rdeDomain:roid>Dpinguino-TEST</rdeDomain:roid>
    <rdeDomain:status s="pendingDelete"/>
    <rdeDomain:rgpStatus s="redemptionPeriod"/>
    <rdeDomain:registrant>jd1234</rdeDomain:registrant>
    <rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
    <rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
    <rdeDomain:ns>
        <domain:hostObj>ns1.example.com</domain:hostObj>
        <domain:hostObj>ns1.example.net</domain:hostObj>
    </rdeDomain:ns>
    <rdeDomain:host>ns1.pinguino.test</rdeDomain:host>
    <rdeDomain:host>ns2.pinguino.test</rdeDomain:host>
    <rdeDomain:clID>clientX</rdeDomain:clID>
    <rdeDomain:crID>clientY</rdeDomain:crID>
    <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
    <rdeDomain:upID>clientX</rdeDomain:upID>
    <rdeDomain:upDate>2009-12-03T09:05:00.0Z</rdeDomain:upDate>
    <rdeDomain:exDate>2015-04-03T22:00:00.0Z</rdeDomain:exDate>
    <rdeDomain:authInfo>
        <domain:pw>2fooBAR</domain:pw>
    </rdeDomain:authInfo>
    <rdeDomain:secDNS>
        <secDNS:maxSigLife>604800</secDNS:maxSigLife>
        <secDNS:dsData>
            <secDNS:keyTag>12345</secDNS:keyTag>
            <secDNS:alg>7</secDNS:alg>
            <secDNS:digestType>1</secDNS:digestType>
            <secDNS:digest>
              93358db22e956a451eb5ae8d2ec39526ca6a87b9
            </secDNS:digest>
        </secDNS:dsData>
    </rdeDomain:secDNS>
    <rdeDomain:trnData>
        <rdeDomain:trStatus>pending</rdeDomain:trStatus>
        <rdeDomain:reID>clientW</rdeDomain:reID>
        <rdeDomain:reDate>2011-03-08T19:38:00.0Z</rdeDomain:reDate>
        <rdeDomain:acID>clientX</rdeDomain:acID>
        <rdeDomain:acDate>2011-03-13T23:59:59.0Z</rdeDomain:acDate>
        <rdeDomain:exDate>2016-04-03T22:00:00.0Z</rdeDomain:exDate>
    </rdeDomain:trnData>
</rdeDomain:domain>
...
                        

4.1.2. <rdeDomain:delete> object

The <rdeDomain:delete> element contains the fully qualified domain name that was deleted and purged.

Example of <rdeDomain:delete> object:

...
<rde:deletes>
        ...
        <rdeDomain:delete>
            <rdeDomain:name>foo.test</rdeDomain:name>
            <rdeDomain:name>bar.test</rdeDomain:name>
        </rdeDomain:delete>
        ...
</rde:deletes>
...
                        

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 <contents> element and the <rdeHost:delete> object used inside the <deletes> element.

4.2.1. <host> object

The RDE host object is based on the EPP host <info> response for an authorized client (see Section 3.1.2. of [RFC5732]).

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:

...
<rdeHost:host>
    <rdeHost:name>ns1.example.test</rdeHost:name>
    <rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid>
    <rdeHost:status s="linked"/>
    <rdeHost:status s="clientUpdateProhibited"/>
    <rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr>
    <rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr>
    <rdeHost:addr ip="v6">1080:0:0:0:8:800:200C:417A</rdeHost:addr>
    <rdeHost:clID>clientY</rdeHost:clID>
    <rdeHost:crID>clientX</rdeHost:crID>
    <rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate>
    <rdeHost:upID>clientX</rdeHost:upID>
    <rdeHost:upDate>2009-10-03T09:34:00.0Z</rdeHost:upDate>
    <rdeHost:trDate>2007-01-08T09:19:00.0Z</rdeHost:trDate>
</rdeHost:host>
...
                        

4.2.2. <rdeHost:delete> object

The <rdeHost:delete> element contains the fully qualified domain name of a host that was deleted.

Example of <rdeHost:delete> object:

...
    <rde:deletes>
        ...
        <rdeHost:delete>
            <rdeHost:name>ns1.example.test</rdeHost:name>
        </rdeHost:delete>
        ...
    </rde:deletes>
...
                        

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 <contents> element and the <rdeContact:delete> object used inside the <deletes> element.

4.3.1. <contact> object

The contact object is based on the EPP contact <info> response for an authorized client (see Section 3.1.2. of [RFC5733]) with some additions including the data from an EPP <transfer> Query Response, see Section 3.1.3. of [RFC5733].

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 [RFC5733] 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:

...
<rdeContact:contact>
    <rdeContact:id>sh8013</rdeContact:id>
    <rdeContact:roid>Csh8013-TEST</rdeContact:roid>
    <rdeContact:status s="linked"/>
    <rdeContact:status s="clientDeleteProhibited"/>
    <rdeContact:postalInfo type="int">
        <contact:name>John Doe</contact:name>
        <contact:org>Example Inc.</contact:org>
        <contact:addr>
            <contact:street>123 Example Dr.</contact:street>
            <contact:street>Suite 100</contact:street>
            <contact:city>Dulles</contact:city>
            <contact:sp>VA</contact:sp>
            <contact:pc>20166-6503</contact:pc>
            <contact:cc>US</contact:cc>
        </contact:addr>
    </rdeContact:postalInfo>
    <rdeContact:voice x="1234">+1.7035555555</rdeContact:voice>
    <rdeContact:fax>+1.7035555556</rdeContact:fax>
    <rdeContact:email>jdoe@example.test</rdeContact:email>
    <rdeContact:clID>clientY</rdeContact:clID>
    <rdeContact:crID>clientX</rdeContact:crID>
    <rdeContact:crDate>2009-09-13T08:01:00.0Z</rdeContact:crDate>
    <rdeContact:upID>clientX</rdeContact:upID>
    <rdeContact:upDate>2009-11-26T09:10:00.0Z</rdeContact:upDate>
    <rdeContact:authInfo>
        <contact:pw>2fooBAR</contact:pw>
    </rdeContact:authInfo>
    <rdeContact:disclose flag="0">
        <contact:voice/>
        <contact:email/>
    </rdeContact:disclose>
    <rdeContact:trnData>
        <rdeContact:trStatus>pending</rdeContact:trStatus>
        <rdeContact:reID>clientW</rdeContact:reID>
        <rdeContact:reDate>2011-03-08T19:38:00.0Z</rdeContact:reDate>
        <rdeContact:acID>clientX</rdeContact:acID>
        <rdeContact:acDate>2011-03-13T23:59:59.0Z</rdeContact:acDate>
    </rdeContact:trnData>
</rdeContact:contact>
...
                        

4.3.2. <rdeContact:delete> object

The <rdeContact:delete> element contains the id of a contact that was deleted.

Example of <rdeContact:delete> object:

...
    <rde:deletes>
        ...
        <rdeContact:delete>
            <rdeContact:id>sh8013-TEST</rdeContact:id>
            <rdeContact:id>co8013-TEST</rdeContact:id>
        </rdeContact:delete>
        ...
    </rde:deletes>
...
                        

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 <contents> element and the <rdeRegistrar:delete> object used inside the <deletes> element.

4.4.1. <registrar> object

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 [RFC3912].
  • 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:

...
<rdeRegistrar:registrar>
    <rdeRegistrar:id>clientX</rdeRegistrar:id>
    <rdeRegistrar:roid>RclientX-TEST</rdeRegistrar:roid>
    <rdeRegistrar:gurid>123</rdeRegistrar:gurid>
    <rdeRegistrar:postalInfo type="int">
        <contact:name>John Doe</contact:name>
        <contact:org>Example Inc.</contact:org>
        <contact:addr>
            <contact:street>123 Example Dr.</contact:street>
            <contact:street>Suite 100</contact:street>
            <contact:city>Dulles</contact:city>
            <contact:sp>VA</contact:sp>
            <contact:pc>20166-6503</contact:pc>
            <contact:cc>US</contact:cc>
        </contact:addr>
    </rdeRegistrar:postalInfo>
    <rdeRegistrar:voice x="1234">+1.7035555555</rdeRegistrar:voice>
    <rdeRegistrar:fax>+1.7035555556</rdeRegistrar:fax>
    <rdeRegistrar:email>jdoe@example.test</rdeRegistrar:email>
    <rdeRegistrar:url>http://www.example.test</rdeRegistrar:url>
    <rdeRegistrar:whoisInfo>
        <rdeRegistrar:name>whois.example.test</rdeRegistrar:name>
        <rdeRegistrar:url>http://whois.example.test</rdeRegistrar:url>
        <rdeRegistrar:url>https://whois.example.test</rdeRegistrar:url>
    </rdeRegistrar:whoisInfo>
    <rdeRegistrar:contact type="admin">rr0013</rdeRegistrar:contact>
    <rdeRegistrar:contact type="tech">rr0012</rdeRegistrar:contact>
    <rdeRegistrar:crDate>2005-04-23T11:49:00.0Z</rdeRegistrar:crDate>
    <rdeRegistrar:upDate>2009-02-17T17:51:00.0Z</rdeRegistrar:upDate>
    <rdeRegistrar:authInfo>
        <contact:pw>tHisaPaSSw</contact:pw>
    </rdeRegistrar:authInfo>
</rdeRegistrar:registrar>
...
                        

4.4.2. <rdeRegistrar:delete> object

The <rdeRegistrar:delete> element contains the id of a registrar that was deleted.

Example of <rdeRegistrar:delete> object:

...
    <rde:deletes>
        ...
        <rdeRegistrar:delete>
            <rdeRegistrar:id>agnt0001-TEST</rdeRegistrar:id>
        </rdeRegistrar:delete>
        ...
    </rde:deletes>
...
                        

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 <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:

...
<rdeIDN:idnTableRef id="cl-es">
    <rdeIDN:url>
        http://www.iana.org/domains/idn-tables/tables/cl_latn_1.0.html
    </rdeIDN:url>
</rdeIDN:idnTableRef>
...
                    

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".
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. <idn> object

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 Section 4.6.1 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:

...
<rdeIDN:idn>
    <rdeIDN:aName>xn--pingino-q2a.test</rdeIDN:aName>
    <rdeIDN:uName>pingüino.test</rdeIDN:uName>
    <rdeIDN:type>withheld</rdeIDN:type>
    <rdeIDN:idnTableId>cl-es</rdeIDN:idnTableId>
    <rdeIDN:canonicalRoid>Dpinguino-TEST</rdeIDN:canonicalRoid>
</rdeIDN:idn>
...
                        

4.6.3. <rdeIDN:delete> object

The <rdeIDN:delete> element contains the ACE of an IDN that was deleted, i.e., the <aName>.

Example of <rdeIDN:delete> object:

...
    <rde:deletes>
        ...
        <rdeIDN:delete>
            <rdeIDN:aName>xn--pingino-q2a.test</rdeIDN:aName>
        </rdeIDN:delete>
        ...
    </rde:deletes>
...
                        

4.7. RDE EPP Parameters 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 [RFC5730]. 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 [RFC5730] for more details.

Example of <eppParams> element object:

<?xml version="1.0" encoding="UTF-8"?>
<rde:deposit
    xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
    ...
    <rde:contents>
        ...
        <rdeEppParams:contents>
            <rdeEppParams:eppParams>
                <rdeEppParams:version>1.0</rdeEppParams:version>
                <rdeEppParams:lang>en</rdeEppParams:lang>
                <rdeEppParams:objURI>
                   urn:ietf:params:xml:ns:domain-1.0
                </rdeEppParams:objURI>
                <rdeEppParams:objURI>
                   urn:ietf:params:xml:ns:contact-1.0
                </rdeEppParams:objURI>
                <rdeEppParams:objURI>
                   urn:ietf:params:xml:ns:host-1.0
                </rdeEppParams:objURI>
                <rdeEppParams:svcExtension>
                    <epp:extURI>
                       urn:ietf:params:xml:ns:rgp-1.0
                    </epp:extURI>
                    <epp:extURI>
                       urn:ietf:params:xml:ns:secDNS-1.1
                    </epp:extURI>
                </rdeEppParams:svcExtension>
                <rdeEppParams:dcp>
                    <epp:access><epp:all/></epp:access>
                    <epp:statement>
                        <epp:purpose>
                            <epp:admin/>
                            <epp:prov/>
                        </epp:purpose>
                        <epp:recipient>
                            <epp:ours/>
                            <epp:public/>
                        </epp:recipient>
                        <epp:retention>
                            <epp:stated/>
                        </epp:retention>
                    </epp:statement>
                </rdeEppParams:dcp>
            </rdeEppParams:eppParams>
            ...
        </rdeEppParams:contents>
    ...
</rde:deposit>
                    

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:

• 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.

BEGIN
<?xml version="1.0" encoding="UTF-8"?>

<schema targetNamespace="urn:ietf:params:xml:ns:rdeDomain-1.0"
          xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
          xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
          xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
          xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
          xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
          xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
          xmlns="http://www.w3.org/2001/XMLSchema"
          elementFormDefault="qualified">

  <!--
  Import common element types
  -->
  <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
          schemaLocation="eppcom-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:domain-1.0"
          schemaLocation="domain-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:secDNS-1.1"
          schemaLocation="secDNS-1.1.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rgp-1.0"
          schemaLocation="rgp-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rde-1.0"
          schemaLocation="rde-1.0.xsd"/>

  <annotation>
    <documentation>
      Registry Data Escrow Domain provisioning schema
    </documentation>
  </annotation>

  <!--
  Child elements of the <rde:contents> object
  -->
  <element name="contents" type="rdeDomain:contentsType"
   substitutionGroup="rde:contents"/>

  <complexType name="contentsType">
    <complexContent>
      <extension base="rde:contentsType"/>
    </complexContent>
  </complexType>

  <!--
  Child elements of the <rde:content> object
  -->
  <element name="domain" type="rdeDomain:contentType"
   substitutionGroup="rde:content"/>

 <complexType name="contentType">
  <complexContent>
   <extension base="rde:contentType">
    <sequence>
     <element name="name" type="eppcom:labelType"/>
     <element name="roid" type="eppcom:roidType"/>
     <element name="status" type="domain:statusType"
      maxOccurs="11"/>
     <element name="rgpStatus" type="rgp:statusType"
      minOccurs="0"/>
     <element name="registrant" type="eppcom:clIDType"
      minOccurs="0"/>
     <element name="contact" type="domain:contactType"
      minOccurs="0" maxOccurs="unbounded"/>
     <element name="ns" type="domain:nsType"
      minOccurs="0"/>
     <element name="host" type="eppcom:labelType"
      minOccurs="0" maxOccurs="unbounded"/>
     <element name="clID" type="eppcom:clIDType"/>
     <element name="crID" type="eppcom:clIDType"
      minOccurs="0"/>
     <element name="crDate" type="dateTime"
      minOccurs="0"/>
     <element name="upID" type="eppcom:clIDType"
      minOccurs="0"/>
     <element name="upDate" type="dateTime"
      minOccurs="0"/>
     <element name="exDate" type="dateTime"
      minOccurs="0"/>
     <element name="deDate" type="dateTime"
      minOccurs="0"/>
     <element name="authInfo" type="domain:authInfoType"
      minOccurs="0"/>
     <element name="secDNS" type="secDNS:dsOrKeyType"
      minOccurs="0"/>
     <element name="trnData" type="rdeDomain:transferDataType"
      minOccurs="0"/>
    </sequence>
   </extension>
  </complexContent>
 </complexType>
 
 <complexType name="transferDataType">
  <sequence>
   <element name="trStatus" type="eppcom:trStatusType"/>
   <element name="reID" type="eppcom:clIDType"/>
   <element name="reDate" type="dateTime"/>
   <element name="acID" type="eppcom:clIDType"/>
   <element name="acDate" type="dateTime"/>
   <element name="exDate" type="dateTime"
    minOccurs="0"/>
  </sequence>
 </complexType>

  <!--
  Child elements of the <rde:delete> object
  -->
  <element name="delete" type="rdeDomain:deleteType"
   substitutionGroup="rde:delete"/>

  <complexType name="deleteType">
    <complexContent>
      <extension base="rde:deleteType">
        <sequence>
          <element name="name" type="eppcom:labelType"
           minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
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:

• 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.

BEGIN
<?xml version="1.0" encoding="UTF-8"?>

<schema targetNamespace="urn:ietf:params:xml:ns:rdeHost-1.0"
        xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
        xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
        xmlns:host="urn:ietf:params:xml:ns:host-1.0"
        xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
        xmlns="http://www.w3.org/2001/XMLSchema"
        elementFormDefault="qualified">

  <!--
  Import common element types
  -->
  <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
          schemaLocation="eppcom-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:host-1.0"
          schemaLocation="host-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rde-1.0"
          schemaLocation="rde-1.0.xsd"/>

  <annotation>
    <documentation>
      Registry Data Escrow host provisioning schema
    </documentation>
  </annotation>

  <!--
  Child elements of the <rde:contents> object
  -->
  <element name="contents" type="rdeHost:contentsType"
   substitutionGroup="rde:contents"/>

  <complexType name="contentsType">
    <complexContent>
      <extension base="rde:contentsType"/>
    </complexContent>
  </complexType>

  <!--
  Child elements of the <rde:content> object
  -->
  <element name="host" type="rdeHost:contentType"
   substitutionGroup="rde:content"/>

  <complexType name="contentType">
    <complexContent>
      <extension base="rde:contentType">
        <sequence>
          <element name="name" type="eppcom:labelType"/>
          <element name="roid" type="eppcom:roidType"/>
          <element name="status" type="host:statusType"
           maxOccurs="7"/>
          <element name="addr" type="host:addrType"
           minOccurs="0" maxOccurs="unbounded"/>
          <element name="clID" type="eppcom:clIDType"/>
          <element name="crID" type="eppcom:clIDType"/>
          <element name="crDate" type="dateTime"/>
          <element name="upID" type="eppcom:clIDType"
           minOccurs="0"/>
          <element name="upDate" type="dateTime"
           minOccurs="0"/>
          <element name="trDate" type="dateTime"
           minOccurs="0"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <!--
  Child elements of the <rde:delete> object
  -->
  <element name="delete" type="rdeHost:deleteType"
   substitutionGroup="rde:delete"/>

  <complexType name="deleteType">
    <complexContent>
      <extension base="rde:deleteType">
        <sequence>
          <element name="name" type="eppcom:labelType"
           minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
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:

• 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.

BEGIN
<?xml version="1.0" encoding="UTF-8"?>

<schema targetNamespace="urn:ietf:params:xml:ns:rdeContact-1.0"
        xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
        xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
        xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
        xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
        xmlns="http://www.w3.org/2001/XMLSchema"
        elementFormDefault="qualified">

  <!--
  Import common element types.
  -->
  <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
          schemaLocation="eppcom-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:contact-1.0"
          schemaLocation="contact-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rde-1.0"
          schemaLocation="rde-1.0.xsd"/>

  <annotation>
    <documentation>
      Registry Data Escrow contact provisioning schema
    </documentation>
  </annotation>

  <!--
  Child elements of the <rde:contents> object
  -->
  <element name="contents" type="rdeContact:contentsType"
   substitutionGroup="rde:contents"/>

  <complexType name="contentsType">
    <complexContent>
      <extension base="rde:contentsType"/>
    </complexContent>
  </complexType>

  <!--
  Child elements of the <rde:content> object
  -->
  <element name="contact" type="rdeContact:contentType"
   substitutionGroup="rde:content"/>

  <complexType name="contentType">
    <complexContent>
      <extension base="rde:contentType">
        <sequence>
          <element name="id" type="eppcom:clIDType"/>
          <element name="roid" type="eppcom:roidType"/>
          <element name="status" type="contact:statusType"
           maxOccurs="7"/>
          <element name="postalInfo" type="contact:postalInfoType"
           maxOccurs="2"/>
          <element name="voice" type="contact:e164Type"
           minOccurs="0"/>
          <element name="fax" type="contact:e164Type"
           minOccurs="0"/>
          <element name="email" type="eppcom:minTokenType"/>
          <element name="clID" type="eppcom:clIDType"/>
          <element name="crID" type="eppcom:clIDType"/>
          <element name="crDate" type="dateTime"/>
          <element name="upID" type="eppcom:clIDType"
           minOccurs="0"/>
          <element name="upDate" type="dateTime"
           minOccurs="0"/>
          <element name="authInfo" type="contact:authInfoType"
           minOccurs="0"/>
          <element name="disclose" type="contact:discloseType"
           minOccurs="0"/>
          <element name="trnData" type="rdeContact:transferDataType"
           minOccurs="0"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

 <complexType name="transferDataType">
  <sequence>
   <element name="trStatus" type="eppcom:trStatusType"/>
   <element name="reID" type="eppcom:clIDType"/>
   <element name="reDate" type="dateTime"/>
   <element name="acID" type="eppcom:clIDType"/>
   <element name="acDate" type="dateTime"/>
  </sequence>
 </complexType>

 <!--
  Child elements of the <rde:delete> object
  -->
  <element name="delete" type="rdeContact:deleteType"
   substitutionGroup="rde:delete"/>

  <complexType name="deleteType">
    <complexContent>
      <extension base="rde:deleteType">
        <sequence>
          <element name="id" type="eppcom:clIDType"
           minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
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:

• 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.

BEGIN
<?xml version="1.0" encoding="UTF-8"?>

<schema targetNamespace="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
        xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
        xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
        xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
        xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
        xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
        xmlns="http://www.w3.org/2001/XMLSchema"
        elementFormDefault="qualified">

  <!--
  Import common element types.
  -->
  <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
          schemaLocation="eppcom-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:domain-1.0"
          schemaLocation="domain-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:contact-1.0"
          schemaLocation="contact-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rde-1.0"
          schemaLocation="rde-1.0.xsd"/>

  <annotation>
    <documentation>
      Registry Data Escrow registrar provisioning schema
    </documentation>
  </annotation>

  <!--
  Child elements of the <rde:contents> object
  -->
  <element name="contents" type="rdeRegistrar:contentsType"
   substitutionGroup="rde:contents"/>

  <complexType name="contentsType">
    <complexContent>
      <extension base="rde:contentsType"/>
    </complexContent>
  </complexType>

  <!--
  Child elements of the <rde:content> object
  -->
  <element name="registrar" type="rdeRegistrar:contentType"
   substitutionGroup="rde:content"/>

   <complexType name="contentType">
    <complexContent>
      <extension base="rde:contentType">
        <sequence>
          <element name="id" type="eppcom:clIDType"/>
          <element name="roid" type="eppcom:roidType"/>
          <element name="gurid" type="positiveInteger"
           minOccurs="0"/>
          <element name="postalInfo" type="contact:postalInfoType"
           maxOccurs="2"/>
          <element name="voice" type="contact:e164Type"
           minOccurs="0"/>
          <element name="fax" type="contact:e164Type"
           minOccurs="0"/>
          <element name="email" type="eppcom:minTokenType"
           minOccurs="0"/>
          <element name="url" type="anyURI"
           minOccurs="0"/>
          <element name="whoisInfo" type="rdeRegistrar:whoisInfoType"
           minOccurs="0"/>
          <element name="contact" type="domain:contactType"
           minOccurs="0" maxOccurs="unbounded"/>
          <element name="crDate" type="dateTime"/>
          <element name="upDate" type="dateTime"
           minOccurs="0"/>
          <element name="authInfo" type="contact:authInfoType"
           minOccurs="0"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <complexType name="whoisInfoType">
    <sequence>
      <element name="name" type="eppcom:labelType"
       minOccurs="0"/>
      <element name="url" type="anyURI"
       minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
  </complexType>

  <!--
  Child elements of the <rde:delete> object
  -->
  <element name="delete" type="rdeRegistrar:deleteType"
   substitutionGroup="rde:delete"/>

  <complexType name="deleteType">
    <complexContent>
      <extension base="rde:deleteType">
        <sequence>
          <element name="id" type="eppcom:clIDType"
           minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
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:

• 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.

BEGIN
<?xml version="1.0" encoding="UTF-8"?>

<schema targetNamespace="urn:ietf:params:xml:ns:rdeIDN-1.0"
        xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
        xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
        xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
        xmlns="http://www.w3.org/2001/XMLSchema"
        elementFormDefault="qualified">

  <!--
  Import common element types
  -->
  <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
   schemaLocation="eppcom-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rde-1.0"
   schemaLocation="rde-1.0.xsd"/>

  <annotation>
    <documentation>
      Registry Data Escrow IDN provisioning schema
    </documentation>
  </annotation>

  <!--
  Child elements of the <rde:contents> object
  -->
  <element name="contents" type="rdeIDN:contentsType"
    substitutionGroup="rde:contents"/>

  <complexType name="contentsType">
    <complexContent>
      <extension base="rde:contentsType"/>
    </complexContent>
  </complexType>

  <!--
  Child elements of the <rde:content> object
  -->
  <element name="idn" type="rdeIDN:contentType"
    substitutionGroup="rde:content"/>

  <complexType name="contentType">
    <complexContent>
      <extension base="rde:contentType">
        <sequence>
          <element name="aName" type="eppcom:labelType"/>
          <element name="uName" type="eppcom:labelType"
           minOccurs="0"/>
          <element name="type" type="rdeIDN:variantType"/>
          <element name="idnTableId" type="IDREF"/>
          <element name="roid" type="eppcom:roidType"
           minOccurs="0"/>
          <element name="canonicalRoid" type="eppcom:roidType"
           minOccurs="0"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <simpleType name="variantType">
    <restriction base="token">
      <enumeration value="allocated"/>
      <enumeration value="withheld"/>
      <enumeration value="blocked"/>
      <enumeration value="canonical"/>
      <enumeration value="mirrored"/>
      <enumeration value="delegated"/>
    </restriction>
  </simpleType>
  
  <!--
    Child elements of the <rde:delete> object
  -->
  <element name="delete" type="rdeIDN:deleteType"
    substitutionGroup="rde:delete"/>
  
  <complexType name="deleteType">
    <complexContent>
      <extension base="rde:deleteType">
        <sequence>
          <element name="aName" type="eppcom:labelType"
            minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <!--
  Child elements of the <rde:content> object
  -->
  <element name="idnTableRef" type="rdeIDN:idnTableRefType"
   substitutionGroup="rde:content"/>

  <complexType name="idnTableRefType">
    <complexContent>
      <extension base="rde:contentType">
        <sequence>
          <element name="url" type="anyURI"/>
        </sequence>
        <attribute name="id" type="ID"/>
      </extension>
    </complexContent>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
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:

• 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.

BEGIN
<?xml version="1.0" encoding="UTF-8"?>

<schema targetNamespace="urn:ietf:params:xml:ns:rdeEppParams-1.0"
        xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
        xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
        xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
        xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
        xmlns="http://www.w3.org/2001/XMLSchema"
        elementFormDefault="qualified">

  <!--
  Import common element types
  -->
  <import namespace="urn:ietf:params:xml:ns:epp-1.0"
   schemaLocation="epp-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
   schemaLocation="eppcom-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rde-1.0"
   schemaLocation="rde-1.0.xsd"/>

  <annotation>
    <documentation>
      Registry Data Escrow EPP Parameters schema
    </documentation>
  </annotation>

  <!--
  Child elements of the <rde:contents> object
  -->
  <element name="contents" type="rdeEppParams:contentsType"
    substitutionGroup="rde:contents"/>

  <complexType name="contentsType">
    <complexContent>
      <extension base="rde:contentsType"/>
    </complexContent>
  </complexType>

  <!--
  Child elements of the <rde:content> object
  -->
  <element name="eppParams" type="rdeEppParams:contentType"
    substitutionGroup="rde:content"/>

  <complexType name="contentType">
    <complexContent>
      <extension base="rde:contentType">
        <sequence>
          <element name="version" type="epp:versionType"
            maxOccurs="unbounded"/>
          <element name="lang" type="language"
            maxOccurs="unbounded"/>
          <element name="objURI" type="anyURI"
            maxOccurs="unbounded"/>
          <element name="svcExtension" type="epp:extURIType"
            minOccurs="0"/>
          <element name="dcp" type="epp:dcpType"/>
        </sequence>
      </extension>
    </complexContent>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
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 <?xml?> 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.
• 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:

• 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
• 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 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 <domain> element.
2. Added definition for child elements under the <host> element.
3. Added definition for child elements under the <contact> 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 <icannID> to <gurid> in the <rdeRegistrar>.
6. Renamed <dnssec> to <secDNS> in the <domain> element.
7. Renamed <transfData> to <trnData> in the <domain> element.
8. Added <whoisInfo> element under <rdeRegistrar> element.
9. Fixed some typographical errors and omissions.

12. References

12.1. Normative References

12.2. Informative References

Authors' Addresses