Domain Name Data Escrow Specification
draft-arias-noguchi-registry-data-escrow-01

Abstract

This document specifies the format and contents of Data Escrow deposits for Domain Name Registration Organizations.

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 April 28, 2011.

Copyright Notice

Copyright (c) 2010 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.  Problem Scope
4.  General Conventions
    4.1.  Date and Time
    4.2.  Country names
    4.3.  Telephone numbers
    4.4.  IP addresses
5.  Protocol Description
    5.1.  Root element <deposit>
    5.2.  Child <watermark> element
    5.3.  Child <eppParams> element
    5.4.  Child <deletes> element
    5.5.  Child <contents> element
6.  Object Description
    6.1.  RDE Domain Object
    6.2.  RDE Host Object
    6.3.  RDE Contact Object
    6.4.  RDE Registrar Object
    6.5.  RDE IDN Table Reference
    6.6.  RDE IDN object
7.  Formal Syntax
    7.1.  RDE Schema
    7.2.  RDE Domain Object
    7.3.  RDE Host Object
    7.4.  RDE Contact Object
    7.5.  RDE Registrar Object
    7.6.  RDE IDN and IDN Table Reference Objects
8.  Extension Example
9.  Internationalization Considerations
10.  IANA Considerations
11.  Security Considerations
12.  Acknowledgments
13.  Change History
    13.1.  Changes from version 00 to 01
14.  References
    14.1.  Normative References
    14.2.  Informative References
§  Authors' Addresses

1.  Introduction

Registration Data Escrow is the process by which an Internet Registration Organization (e.g., a registry, registrar, etc.) periodically submits data deposits to a contracted third party called an Escrow Agent. These deposits comprise all the data needed to resume operations if the registration organization could not function as a result of a catastrophe or a financial situation. For a domain name registry or registrar the data to be deposited includes all the objects related to registered domain names, e.g., contacts, name servers, etc.

The purpose of data escrow is to permit quick resumption of registration service by another registration organization after a catastrophe. The goal is higher resiliency of registration services, for the benefit of Internet users. The beneficiaries of a registration organization are not just those registering information there, but all relying parties that need to identify the owners of objects.

In the context of domain name registries, registration data escrow is a requirement for the current generic top-level domains and it is expected to be for new registries. Some country code top-level domain managers are also currently escrowing data. There is also a similar requirement for ICANN's generic top-level domain accredited registrars.

This document specifies a format and contents of Data Escrow deposits for Domain Name Registration Organizations.

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] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).

DEPOSIT. Deposits can be of three kinds: Full, Differential or Incremental. For all kinds of Deposits, the Universe of Registry objects to be considered for data escrow are those objects necessary in order to offer the Registry Services.

DIFFERENTIAL DEPOSIT. Contains data that reflects all transactions involving the database that were not reflected in the last previous Full, Incremental or Differential Deposit, as the case may be. Differential deposit files will contain information from all database objects that were added, modified or deleted since the previous Deposit was completed as of its defined Timeline Watermark.

ESCROW AGENT. The organization contracted by the Registry or the Third-Party Beneficiary to receive and guard Data Escrow Deposits from the Registry.

FULL DEPOSIT. Contains the Registry Data that reflects the current and complete Registry Database and will consist of data that reflects the state of the registry as of a defined Timeline Watermark for the deposit.

INCREMENTAL DEPOSIT. Contains data that reflects all transactions involving the database that were not reflected in the last previous Full Deposit. Incremental Deposit files will contain information from all database objects that were added, modified or deleted since the previous Full Deposit was completed as of its defined Timeline Watermark. If the Timeline Watermark of an Incremental Deposit were to cover the Watermark of another (Incremental or Differential) Deposit since the last Full Deposit, the former Deposit MUST contain the transactions of the later Deposit.

REGISTRY. The organization providing Registry Services for a RCDN.

REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) or any other domain name at any level in the DNS tree for which a Registry (either directly or through and affiliate company) provides Registry services to other organizations or individuals. For example: .COM, .ORG, .BIZ, .CO.JP, .ORG.MX.

REGISTRY SERVICES. Services offered by the Registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the DNS servers for the RCDN; dissemination of RCDN zone files; operation of the Registry DNS servers; and dissemination of contact and other information concerning DNS registrations in the RCDN. Any other products or services that only a Registry is capable of providing, by reason of its designation as the Registry. Typical examples of Registry Services are: DNS resolution for the RCDN, WHOIS and EPP.

THIRD-PARTY BENEFICIARY. Is the organization that, under extraordinary circumstances, would receive the escrow Deposits the Registry transferred to the Escrow Agent. This organization could be a backup Registry, Registry regulator, contracting party of the Registry, etc.

TIMELINE WATERMARK. Point in time on which to base the collecting of database objects for a Deposit. Deposits are expected to be consistent to that point in time.

3.  Problem Scope

Since a few years ago, the issue of Registry continuity has been carefully considered in the gTLD and ccTLD space. Various organizations have made risk analysis and developed Business Continuity Plans to deal with those risks, should they materialize.

One of the solutions considered and used, especially in the gTLD space, is Registry Data Escrow as a way to ensure the Continuity of Registry Services in the extreme case of Registry failure.

So far, almost every Registry that uses Registry Data Escrow has its own specification. It is also anticipated that more Registries will be implementing Escrow especially with the advent of the new gTLD program.

Now, it would seem beneficial to have a standardized specification for Registry Data Escrow that can be used by any Registry to submit its Deposits and, in case, to use those deposits to operate Registry Services for a RCDN that has to be transitioned of Registry operator.

A solution to the problem at hand SHALL clearly identify the format and contents of the Deposits a Registry has to make, such that another different Registry would be able to rebuild the Registry Services of the former, without its help, in a timely manner, with minimum harm to the Registrants, Registrars and Internet users.

Since the list and details of Registry Services vary from Registry to Registry, the solution SHALL provide mechanisms that allow its extensibility to accommodate variations and extensions of the Registry Services.

Given the confidentiality and importance of some of the information that is handled in order to offer the Registry Services, the solution SHALL define confidentiality and integrity mechanisms when handling the Registry data.

The solution SHALL NOT include in the specification those objects of such delicate confidentiality that it is best to leave them out of the Deposits, e.g., DNSSEC KSK/ZSK private keys.

Details that are a matter of policy SHOULD be identified as such for the benefit of the implementers.

Legal issues around Data Escrow and the overall question of the use Registry Data Escrow are outside of scope of this document.

4.  General Conventions

4.1.  Date and Time

Numerous fields indicate "dates", such as the creation and expiry dates for domains. These fields SHALL contain timestamps indicating the date and time in UTC as specified in [RFC3339] (Klyne, G., Ed. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.), with no offset from the zero meridian.

4.2.  Country names

Country identifiers SHALL be represented using two character identifiers as specified in [ISO‑3166‑1] (International Organization for Standardization, “Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes,” November 2006.).

4.3.  Telephone numbers

Telephone numbers (both voice and fax) SHALL be formatted based on structures defined in [ITU‑E164] (International Telecommunication Union, “The international public telecommunication numbering plan,” February 2005.). 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] (International Telecommunication Union, “The international public telecommunication numbering plan,” February 2005.), followed by a dot (".", ASCII value 0x002E), followed by a sequence of digits representing the telephone number.

4.4.  IP addresses

IP addresses syntax MUST conform either to, Internet Protocol [RFC0791] (Postel, J., “Internet Protocol,” September 1981.), for IPv4 addresses, or IP Version 6 Addressing Architecture [RFC4291] (Hinden, R. and S. Deering, “IP Version 6 Addressing Architecture,” February 2006.), for IPv6 addresses.

5.  Protocol Description

The following is a format for Data Escrow deposits as produced by an Internet Domain Registry. Only the format of the objects deposited is defined, nothing is prescribed about the way to transfer such deposits between the Registry and the Escrow Agent or vice versa. The format is based on EPP [RFC5730] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP),” August 2009.) and related RFCs by Scott Hollenbeck.

5.1.  Root element <deposit>

The container or root element for a Registry Data Escrow deposits is <deposit>. This element contains the following child elements: watermark, deletes and contents. This element also contains the following attributes:

• A "type" attribute that MUST be used to identify the kind of deposit: FULL, INCR (Incremental) or DIFF (Differential).
• An "id" attribute that MUST be used to uniquely identify the escrow deposit. Each registry is responsible for maintaining its own escrow deposits identifier space to ensure uniqueness.
• An OPTIONAL "prevId" attribute that can be used to identify the previous incremental, differential or full escrow deposit. This attribute MUST be used in Differential Deposits ("DIFF" type).
• An OPTIONAL "resend" attribute that is used to identify resend attempts in case of previous failure. The first time a deposit is attempted to be sent, the attribute MUST be zero; The second attempt to send (first resend attempt) the attribute MUST be set to one; and so on. This would be used when for example, the previous deposit was not received complete, it failed verification at the receiving party, etc.

Example of root element object:

<?xml version="1.0" encoding="UTF-8"?>
<rde:deposit
    xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
    ...
    type="FULL"
    id="FULL-20101017001" prevId="FULL-20101010001">
    <rde:watermark>2010-10-18T00:00:00Z</rde:watermark>
    <rde:eppParams>
       ...
    </rde:eppParams>
    <rde:deletes>
       ...
    </rde:deletes>
    <rde:contents>
       ...
    </rde:contents>
</rde:deposit>

5.2.  Child <watermark> element

A <watermark> element contains the data-time correspondent to the Timeline Watermark of the deposit.

Example of <watermark> element object:

<?xml version="1.0" encoding="UTF-8"?>
<rde:deposit
    xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
    ...
    type="FULL"
    id="FULL-20101017001" prevId="FULL-20101010001">
    <rde:watermark>2010-10-18T00:00:00Z</rde:watermark>
    ...
</rde:deposit>

5.3.  Child <eppParams> element

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] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP),” August 2009.). 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] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP),” August 2009.) 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:eppParams>
        <rde:version>1.0</rde:version>
        <rde:lang>en</rde:lang>
        <rde:objURI>urn:ietf:params:xml:ns:domain-1.0</rde:objURI>
        <rde:objURI>urn:ietf:params:xml:ns:contact-1.0</rde:objURI>
        <rde:objURI>urn:ietf:params:xml:ns:host-1.0</rde:objURI>
        <rde: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>
        </rde:svcExtension>
        <rde: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>
        </rde:dcp>
    </rde:eppParams>
    ...
</rde:deposit>

5.4.  Child <deletes> element

This section SHOULD only be present in deposits of type Incremental or Differential. It contains the list of objects that were deleted since the base previous deposit. Each object in this section contains an ID for the object deleted. For domains and hosts it will be the fully qualified domain name.

This section of the deposit SHOULD NOT be present in Full deposits. When rebuilding a registry it SHOULD be ignored if present in a Full deposit.

Elements that MAY appear in this section are: delContact, delHost, delDomain and/or delRegistrar. It MAY also contain an extension element allowing extending the element.

Example of <deletes> element object:

<?xml version="1.0" encoding="UTF-8"?>
<rde:deposit
    xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
    ...
    <rde:deletes>
        <rde:delContact>sh8013-TEST</rde:delContact>
        ...
        <rde:delHost>ns1.example.test</rde:delHost>
        ...
        <rde:delDomain>example.test</rde:delDomain>
        ...
        <rde:delRegistrar>agnt0001-TEST</rde:delRegistrar>
    </rde:deletes>
    ...
</rde:deposit>

5.5.  Child <contents> element

This section of the deposit contains the actual objects in the deposit. It MAY contain elements: contact, host, domain, registrar, idnTableRef and idn as defined in Section 6 (Object Description). This element MAY also contain an extension element allowing extending the format.

In the case of Incremental or Differential deposits, the objects indicate whether the object was added or modified after the base previous deposit. In order to distinguish between one and the other, it will be sufficient to check existence of the referenced object in the base previous deposit.

When applying Incremental or Differential deposits, i.e., when rebuilding the registry from data escrow deposits, the order of the <deletes> and <contents> elements is important. First, all the deletes MUST be applied and then the adds and updates, i.e., first apply what is in <deletes> and later what is in <contents>.

Example of <contents> element object:

<?xml version="1.0" encoding="UTF-8"?>
<rde:deposit
    xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
    ...
    <rde:contents>
        <rde:contact>
               ...
        </rde:contact>
        <rde:host>
               ...
        </rde:host>
        <rde:domain>
               ...
        </rde:domain>
        <rde:registrar>
               ...
        </rde:registrar>
        <rde:idnTableRef>
          ...
        </rde:idnTableRef>
        <rde:idn>
          ...
        </rde:idn>
    </rde:contents>
    ...
</rde:deposit>

6.  Object Description

This section describes the base objects defined in EPP: domains, hosts and contacts with the addition of registrars, idnTableRefs and idns.

6.1.  RDE Domain Object

The RDE domain object is based on the EPP domain name mapping in [RFC5731] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP) Domain Name Mapping,” August 2009.). There are two elements used in this format related to domains: the domain object per se, used inside the <contents> element and the delDomain object used inside the <deletes> element.

6.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] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP) Domain Name Mapping,” August 2009.)).

Example of domain object:

...
<rde: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:trDate>2010-04-08T09:28:00.0Z</rdeDomain:trDate>
    <rdeDomain:authInfo>
        <domain:pw>2fooBAR</domain:pw>
    </rdeDomain:authInfo>
    <rdeDomain:dnssec>
        <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:dnssec>
</rde:domain>
...

6.1.2.  <delDomain> object

The delDomain element contains the fully qualified domain name of a domain that was deleted.

Example of <delDomain> object:

...
<rde:delDomain>example.test</rde:delDomain>
...

6.2.  RDE Host Object

The RDE host object is based on the EPP host name mapping in [RFC5732] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP) Host Mapping,” August 2009.). There are two elements used in this format related to hosts: the host object per se, used inside the <contents> element and the delHost object used inside the <deletes> element.

6.2.1.  <host> object

The RDE domain object is based on the EPP host <info> response for an authorized client (see Section 3.1.2. of [RFC5732] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP) Host Mapping,” August 2009.)).

Example of <host> object:

...
<rde: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>
</rde:host>
...

6.2.2.  <delHost> object

The delHost element contains the fully qualified domain name of a host that was deleted.

Example of <delHost> object:

...
<rde:delHost>ns1.example.test</rde:delHost>
...

6.3.  RDE Contact Object

The RDE contact object is based on the EPP contact name mapping in [RFC5733] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP) Contact Mapping,” August 2009.). There are two elements used in this format related to contacts: the contact object per se, used inside the <contents> element and the delContact object used inside the <deletes> element.

6.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] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP) Contact Mapping,” August 2009.)).

Example <contact> object:

...
<rde: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:trDate>2010-03-18T19:28:00.0Z</rdeContact:trDate>
    <rdeContact:authInfo>
        <contact:pw>2fooBAR</contact:pw>
    </rdeContact:authInfo>
    <rdeContact:disclose flag="0">
        <contact:voice/>
        <contact:email/>
    </rdeContact:disclose>
</rde:contact>
...

6.3.2.  <delContact> object

The delContact element contains the id of a contact that was deleted.

Example of <delContact> object:

...
<rde:delContact>sh8013</rde:delContact>
...

6.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 delRegistrar object used inside the <deletes> element.

6.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 <icannId> 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.
• A <email> element that contains the registrar's email address.
• A <url> element that contains the registrar's URL.
• 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 <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:

...
<rde:registrar>
    <rdeRegistrar:id>clientX</rdeRegistrar:id>
    <rdeRegistrar:roid>RclientX-TEST</rdeRegistrar:roid>
    <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: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>
</rde:registrar>
...

6.4.2.  <delRegistrar> object

The delRegistrar element contains the id of a registrar that was deleted.

Example of <delRegistrar> object:

...
<rde:delRegistrar>clientZ</rde:delRegistrar>
...

6.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:url>
    http://www.iana.org/domains/idn-tables/tables/cl_latn_1.0.html
</rdeIDN:url>
...

6.6.  RDE IDN object

6.6.1.  IDN variants Handling

Depending on the Registration Policy in place in the Registry; for a particular IDN, there may be multiple variant domains either registered, reserved or blocked:

1. If the IDN variant is actually registered, bundled with its canonical domain name in the Registry system, the variant SHALL be tagged as "registered".
2. If only the holder of the canonical domain name is allowed to register the IDN variant but it is not actually registered, the variant SHALL be tagged as "reserved".
3. If the IDN variant is considered undesirable for registration, the variant SHALL be tagged as "blocked".

6.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 OPTIONAL <uName> element that contains the name of the IDN in Unicode character set. It SHOULD be provided if available.
• A <type> element that indicates the type of variant this IDN is: registered, reserved, blocked or canonical; see Section 6.6.1 (IDN variants Handling)
• An <idnTableId> element that references the IDN Table used for the IDN. This corresponds to the "id" attribute of the <idnTableRef> element.
• An OPTIONAL <roid> element that contains the ROID of the corresponding domain object, if there is one. It MUST be provided if the domain object exists.
• A <canonicalRoid> element that contains the ROID of the canonical domain name. It MUST be provided if the IDN is NOT the canonical domain name.
• An OPTIONAL <extension> element that allows extending the IDN object.

Example of <idn> object:

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

6.6.3.  <delIdn> object

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

Example of <delIdn> object:

...
<rde:delIdn>xn--pingino-q2a.test</rde:delIdn>
...

7.  Formal Syntax

Six 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 last schema defines the idnTableRef and IDN objects.

7.1.  RDE Schema

Copyright (c) 2010 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:rde-1.0"
        xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
        xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
        xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
        xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
        xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
        xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
        xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
        xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
        xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-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:rdeContact-1.0"
          schemaLocation="rdeContact-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rdeHost-1.0"
          schemaLocation="rdeHost-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rdeDomain-1.0"
          schemaLocation="rdeDomain-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
          schemaLocation="rdeRegistrar-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0"
          schemaLocation="rdeIDN-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:epp-1.0"
          schemaLocation="epp-1.0.xsd"/>

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

  <!--
  Root element
  -->
  <element name="deposit" type="rde:escrowDepositType"/>

  <!--
  RDE types
  -->
  <complexType name="escrowDepositType">
    <sequence>
      <element name="watermark" type="dateTime"/>
      <element name="eppParams" type="rde:rdeEppParamsType"
       minOccurs="0"/>
      <element name="deletes" type="rde:deletesType"
       minOccurs="0"/>
      <element name="contents" type="rde:contentsType"/>
      <element name="extension" type="rde:extAnyType"
       minOccurs="0"/>
    </sequence>
    <attribute name="type" type="rde:depositType"
     use="required"/>
    <attribute name="id" type="rde:depositIdType"
     use="required"/>
    <attribute name="prevId" type="rde:depositIdType"
     use="optional"/>
    <attribute name="resend" type="unsignedShort"
     default="0"/>
  </complexType>

  <complexType name="contentsType">
    <sequence>
      <element name="contact" type="rdeContact:rdeContactType"
       minOccurs="0" maxOccurs="unbounded"/>
      <element name="host" type="rdeHost:rdeHostType"
       minOccurs="0" maxOccurs="unbounded"/>
      <element name="domain" type="rdeDomain:rdeDomainType"
       minOccurs="0" maxOccurs="unbounded"/>
      <element name="registrar"
       type="rdeRegistrar:rdeRegistrarType"
       minOccurs="0" maxOccurs="unbounded"/>
      <element name="idnTableRef"
       type="rdeIDN:rdeIDNTableRefType" minOccurs="0"
       maxOccurs="unbounded"/>
      <element name="idn" type="rdeIDN:rdeIDNType"
       minOccurs="0" maxOccurs="unbounded"/>
      <element name="extension" type="rde:extAnyType"
       minOccurs="0"/>
      </sequence>
  </complexType>

  <complexType name="deletesType">
    <sequence>
      <element name="delContact" type="eppcom:clIDType"
       minOccurs="0" maxOccurs="unbounded"/>
      <element name="delHost" type="eppcom:labelType"
       minOccurs="0" maxOccurs="unbounded"/>
      <element name="delDomain" type="eppcom:labelType"
       minOccurs="0" maxOccurs="unbounded"/>
      <element name="delRegistrar" type="eppcom:clIDType"
       minOccurs="0" maxOccurs="unbounded"/>
      <element name="extension" type="rde:extAnyType"
       minOccurs="0"/>
    </sequence>
  </complexType>

  <!--
  Type of deposit
  -->
  <simpleType name="depositType">
    <restriction base="token">
      <enumeration value="FULL"/>
      <enumeration value="INCR"/>
      <enumeration value="DIFF"/>
    </restriction>
  </simpleType>

  <!--
  Deposit identifier type
  -->
  <simpleType name="depositIdType">
    <restriction base="token">
      <pattern value="(FULL|INCR|DIFF)-\w{1,13}"/>
    </restriction>
  </simpleType>

  <!--
  Extension framework type
  -->
  <complexType name="extAnyType">
    <sequence>
      <any namespace="##other"
       maxOccurs="unbounded"/>
    </sequence>
  </complexType>

  <!--
   Child elements of an EPP Params object
  -->
  <complexType name="rdeEppParamsType">
    <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>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
END

7.2.  RDE Domain Object

Copyright (c) 2010 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:domain="urn:ietf:params:xml:ns:domain-1.0"
          xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
          xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
          xmlns:rgp="urn:ietf:params:xml:ns:rgp-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:rde-1.0"
          schemaLocation="rde-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"/>

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

  <!--
  Child elements of a Domain object
  -->
  <complexType name="rdeDomainType">
    <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="trDate" type="dateTime"
       minOccurs="0"/>
      <element name="deDate" type="dateTime"
       minOccurs="0"/>
      <element name="authInfo" type="domain:authInfoType"
       minOccurs="0"/>
      <element name="dnssec" type="secDNS:dsOrKeyType"
       minOccurs="0"/>
      <element name="extension" type="rde:extAnyType"
       minOccurs="0"/>
    </sequence>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
END

7.3.  RDE Host Object

Copyright (c) 2010 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:rde-1.0"
          schemaLocation="rde-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:host-1.0"
          schemaLocation="host-1.0.xsd"/>

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

  <!--
  Child elements of Host object
  -->
  <complexType name="rdeHostType">
    <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"/>
      <element name="extension" type="rde:extAnyType"
       minOccurs="0"/>
    </sequence>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
END

7.4.  RDE Contact Object

Copyright (c) 2010 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:rde-1.0"
          schemaLocation="rde-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:contact-1.0"
          schemaLocation="contact-1.0.xsd"/>

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

  <!--
  Child elements of Contact object
  -->
  <complexType name="rdeContactType">
    <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="trDate" type="dateTime"
       minOccurs="0"/>
      <element name="authInfo" type="contact:authInfoType"
       minOccurs="0"/>
      <element name="disclose" type="contact:discloseType"
      minOccurs="0"/>
     <element name="extension" type="rde:extAnyType"
      minOccurs="0"/>
    </sequence>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
END

7.5.  RDE Registrar Object

Copyright (c) 2010 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: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:eppcom-1.0"
          schemaLocation="eppcom-1.0.xsd"/>
  <import namespace="urn:ietf:params:xml:ns:rde-1.0"
          schemaLocation="rde-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:domain-1.0"
          schemaLocation="domain-1.0.xsd"/>

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

  <!--
  Child elements of Registrar object
  -->
  <complexType name="rdeRegistrarType">
    <sequence>
     <element name="id" type="eppcom:clIDType"/>
     <element name="roid" type="eppcom:roidType"/>
     <element name="icannId" 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="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"/>
     <element name="extension" type="rde:extAnyType"
      minOccurs="0"/>
    </sequence>
  </complexType>

  <!--
  End of schema.
  -->
</schema>
END

7.6.  RDE IDN and IDN Table Reference Objects

Copyright (c) 2010 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: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:rde-1.0"
   schemaLocation="rde-1.0.xsd"/>

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

  <!--
  Child elements of an IDN object
  -->
  <complexType name="rdeIDNType">
    <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"/>
      <element name="extension" type="rde:extAnyType"
       minOccurs="0"/>
    </sequence>
  </complexType>

  <complexType name="rdeIDNTableRefType">
    <sequence>
      <element name="url" type="anyURI"/>
    </sequence>
    <attribute name="id" type="ID"/>
  </complexType>

  <simpleType name="variantType">
    <restriction base="token">
      <enumeration value="registered"/>
      <enumeration value="reserved"/>
      <enumeration value="blocked"/>
      <enumeration value="canonical"/>
    </restriction>
  </simpleType>

  <!--
  End of schema.
  -->
</schema>
END

8.  Extension Example

Consider the following XML Schema for an extension example:

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

<schema targetNamespace="urn:ietf:params:xml:ns:rdeExtOne-1.0"
        xmlns:secExExt1="urn:ietf:params:xml:ns:rdeExtOne-1.0"
        xmlns:rde="urn:ietf:params:xml:ns:rde-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"/>

  <annotation>
    <documentation>
      Example Extension #1
    </documentation>
  </annotation>

  <!--
  Child elements of a ExtOne object
  -->
  <element name="delIdData" type="secExExt1:extIdType"/>
  <element name="idData" type="secExExt1:idDataType"/>

  <complexType name="idDataType">
    <sequence>
      <element name="id" type="secExExt1:extIdType"/>
      <element name="contactId" type="eppcom:roidType"/>
      <element name="passport" type="NCName"/>
      <element name="country" type="string"/>
    </sequence>
  </complexType>

  <simpleType name="extIdType">
    <restriction base="token" />
  </simpleType>

  <!--
  End of schema.
  -->
</schema>
END

The following is an example deposit that includes the "idData" and "delIdData" elements:

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

<rde:deposit
    xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
    xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
    xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
    xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
    xmlns:secExExt1="urn:ietf:params:xml:ns:rdeExtOne-1.0"
    type="FULL" id="FULL-20101016001" prevId="FULL-20101015001">

    <rde:watermark>2010-10-16T00:00:00Z</rde:watermark>

    <rde:deletes>
        <rde:delHost>ns1.example.test</rde:delHost>
        <rde:extension>
            <secExExt1:delIdData>B54321Y</secExExt1:delIdData>
            <secExExt1:delIdData>C94820X</secExExt1:delIdData>
        </rde:extension>
    </rde:deletes>

    <rde:contents>

        <rde:extension>
            <secExExt1:idData>
                <secExExt1:id>a12345z</secExExt1:id>
                <secExExt1:contactId>SH8013-REP</secExExt1:contactId>
                <secExExt1:passport>G01348919</secExExt1:passport>
                <secExExt1:country>MX</secExExt1:country>
            </secExExt1:idData>
            <secExExt1:idData>
                <secExExt1:id>b56243x</secExExt1:id>
                <secExExt1:contactId>SH8013-REP</secExExt1:contactId>
                <secExExt1:passport>G937434319</secExExt1:passport>
                <secExExt1:country>JP</secExExt1:country>
            </secExExt1:idData>
        </rde:extension>

    </rde:contents>
</rde:deposit>
END

9.  Internationalization Considerations

Data Escrow deposits are represented in XML, which provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8. Conformant XML processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED.

10.  IANA Considerations

This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688] (Mealling, M., “The IETF XML Registry,” January 2004.). Two 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 registrar 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.

11.  Security Considerations

This specification does not define the security mechanisms to be used in the transmission of the data escrow deposits, since it only specifies the minimum necessary to enable the rebuilding of a Registry from deposits without intervention from the original Registry.

Depending on local policies, some elements or most likely, the whole deposit will be considered confidential. As such the Registry transmitting the data to the Escrow Agent SHOULD take all the necessary precautions like encrypting the data itself and/or the transport channel to avoid inadvertent disclosure of private data.

It is also of the utmost importance the authentication of the parties passing data escrow deposit files. The Escrow Agent SHOULD properly authenticate the identity of the Registry before accepting data escrow deposits. In a similar manner, the Registry SHOULD authenticate the identity of the Escrow Agent before submitting any data.

Additionally, the Registry and the Escrow Agent SHOULD use integrity checking mechanisms to ensure the data transmitted is what the source intended. Validation of the contents by the Escrow Agent is RECOMMENDED to ensure not only the file was transmitted correctly from the Registry, but also the contents are also "meaningful".

12.  Acknowledgments

Parts of this document are based on EPP [RFC5730] (Hollenbeck, S., “Extensible Provisioning Protocol (EPP),” August 2009.) and related RFCs by Scott Hollenbeck.

13.  Change History

[[RFC Editor: Please remove this section.]]

13.1.  Changes from version 00 to 01

1. Included DNSSEC elements as part of the basic <domain> element as defined in [RFC5910] (Gould, J. and S. Hollenbeck, “Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP),” May 2010.).
2. Included RGP elements as part of the basic <domain> element as defined in [RFC3915] (Hollenbeck, S., “Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP),” September 2004.).
3. Added support for IDNs and IDN variants.
4. Eliminated the <summary> element and all its subordinate objects, except <watermarkDate>.
5. Renamed <watermarkDate> to <watermark> and included it directly under root element.
6. Renamed root element to <deposit>.
7. Added <authinfo> element under <registrar> element.
8. Added <roid> element under <registrar> element.
9. Reversed the order of the <deletes> and <contents> elements.
10. Removed <rdeDomain:status> minOccurs="0".
11. Added <extension> element under root element.
12. Added <extension> element under <contact> element.
13. Removed <period> element from <domain> element.
14. Populated the "Security Considerations" section.
15. Populated the "Internationalization Considerations" section.
16. Populated the "Extension Example" section.
17. Added <deDate> element under <domain> element.
18. Added <icannId> element under <registrar> element.
19. Added <eppParams> element under root element.
20. Fixed some typographical errors and omissions.

14.  References

14.1. Normative References

14.2. Informative References

Authors' Addresses