Network Working Group F. Arias
Internet-Draft ICANN
Intended status: Standards Track S. Noguchi
Expires: January 7, 2011 JPRS
July 6, 2010
Internet Domain Registry Data Escrow specification
draft-arias-noguchi-registry-data-escrow-00
Abstract
This document specifies the format and contents of Data Escrow
deposits for Domain Registries.
Status of this Memo
This Internet-Draft is submitted to IETF 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 January 7, 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.
Arias & Noguchi Expires January 7, 2011 [Page 1]
Internet-Draft Registry Data Escrow July 2010
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Problem Scope . . . . . . . . . . . . . . . . . . . . . . . . 5
4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6
4.1. Dates . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6
4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6
4.4. IP addresses . . . . . . . . . . . . . . . . . . . . . . . 6
5. Protocol Description . . . . . . . . . . . . . . . . . . . . . 6
5.1. Root element <escrowDeposit> . . . . . . . . . . . . . . . 6
5.2. Child <summary> element . . . . . . . . . . . . . . . . . 7
5.3. Child <contents> element . . . . . . . . . . . . . . . . . 8
5.4. Child <deletes> element . . . . . . . . . . . . . . . . . 9
6. Object Description . . . . . . . . . . . . . . . . . . . . . . 10
6.1. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 10
6.2. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 12
6.3. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 13
6.4. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 15
7. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1. RDE Schema . . . . . . . . . . . . . . . . . . . . . . . . 18
7.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 22
7.3. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 24
7.4. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 26
7.5. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 28
8. Extension Handling . . . . . . . . . . . . . . . . . . . . . . 30
9. Internationalization Considerations . . . . . . . . . . . . . 30
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
11. Security Considerations . . . . . . . . . . . . . . . . . . . 32
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
13.1. Normative References . . . . . . . . . . . . . . . . . . . 32
13.2. Informative References . . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34
Arias & Noguchi Expires January 7, 2011 [Page 2]
Internet-Draft Registry Data Escrow July 2010
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 would include all
the objectes 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 registry
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
such a requirement for ICANN's generic top-level domain accredited
registrars.
This document specifies a format and contents of Data Escrow deposits
for Domain Name Registries.
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].
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.
Arias & Noguchi Expires January 7, 2011 [Page 3]
Internet-Draft Registry Data Escrow July 2010
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 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 directl 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.
Arias & Noguchi Expires January 7, 2011 [Page 4]
Internet-Draft Registry Data Escrow July 2010
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 benefitial 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 whether
to use Registry Data Escrow are outside of scope of this document.
Arias & Noguchi Expires January 7, 2011 [Page 5]
Internet-Draft Registry Data Escrow July 2010
4. General Conventions
4.1. Dates
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 with no offset from the zero meridian, as
specified in [RFC3339].
4.2. Country names
Country identifiers SHALL be represented using two character
identifiers as specified in [ISO-3166-1].
4.3. Telephone numbers
Telephone numbers (both voice and 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.
4.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.
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.
Format is based on EPP [RFC5730] and related RFCs by Scott
Hollenbeck.
5.1. Root element <escrowDeposit>
The container or root element for a Registry Data Escrow deposits is
<escrowDeposit>. This element contains the following child elements:
summary, contents and deletes. This element also contains que
following attributes:
Arias & Noguchi Expires January 7, 2011 [Page 6]
Internet-Draft Registry Data Escrow July 2010
o A "type" attribute that MUST be used to identify the kind of
deposit: FULL, INCR (Incremental) or DIFF (Differential).
o 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.
o An OPTIONAL "prevId" attribute that can be used to identify the
previous incremental, differential or full escrow deposit. This
attribute MUST be used by a differential deposit "DIFF" type.
o 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.
Example of root element object:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rde:escrowDeposit
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
type="FULL"
id="FULL-20080616001" prevId="FULL-20080615001">
<rde:summary>
...
</rde:summary>
<rde:contents>
...
</rde:contents>
<rde:deletes>
...
</rde:deletes>
</rde:escrowDeposit>
5.2. Child <summary> element
This element contains the following child elements:
o A <watermarkDate> element contains the data-time correspondent to
the Timeline Watermark of the deposit.
o A <contentsCount> element contains four child elements:
<contactCount>, <hostCount>, <domainCount> and <registrarCount>
that identify the number of objects contained in the "contents"
section. This element MAY also contain and extension element
allowing extending the format.
Arias & Noguchi Expires January 7, 2011 [Page 7]
Internet-Draft Registry Data Escrow July 2010
o A <deletesCount> element ontains four elements: <contactCount>,
<hostCount>, <domainCount> and <registrarCount> that identify the
number of objects contained in the "deletes" section. This
element MAY also contain and extension element allowing extending
the format.
Example of <summary> element object:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rde:escrowDeposit
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
type="FULL"
id="FULL-20080616001" prevId="FULL-20080615001">
<rde:summary>
<rde:watermarkDate>2008-06-16T03:46:00.0Z</rde:watermarkDate>
<rde:contentsCount>
<rde:contactCount>1234</rde:contactCount>
<rde:hostCount>123456</rde:hostCount>
<rde:domainCount>123456</rde:domainCount>
<rde:registrarCount>123</rde:registrarCount>
</rde:contentsCount>
<rde:deletesCount>
<rde:contactCount>12</rde:contactCount>
<rde:hostCount>1234</rde:hostCount>
<rde:domainCount>1234</rde:domainCount>
<rde:registrarCount>1</rde:registrarCount>
</rde:deletesCount>
</rde:summary>
...
</rde:escrowDeposit>
5.3. Child <contents> element
This section of the deposit contains the actual objects in the
deposit. It MAY contain: contacts, hosts, domains and registrars as
defined in Section 6. This element MAY also contain and extension
element allowing extending the format.
In the case of Incremental or Differential deposits, the objects
indicate one of two posibilities the object was added or modified
after the base previous deposit. In order to distinguish between one
or the other, it will be sufficient to check existence of the
referenced object in the base previous deposit.
Example of <contents> element object:
Arias & Noguchi Expires January 7, 2011 [Page 8]
Internet-Draft Registry Data Escrow July 2010
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rde:escrowDeposit
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
type="FULL"
id="FULL-20080616001" prevId="FULL-20080615001">
...
<rde:contents>
<rde:contact
xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0">
...
</rde:contact>
<rde:host
xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0">
...
</rde:host>
<rde:domain
xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0">
...
</rde:domain>
<rde:registrar
xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0">
...
</rde:registrar>
</rde:contents>
...
</rde:escrowDeposit>
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 delete
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 case of a Full
deposit. 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 and extension
element allowing extending the format.
Example of <deletes> element object:
Arias & Noguchi Expires January 7, 2011 [Page 9]
Internet-Draft Registry Data Escrow July 2010
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rde:escrowDeposit
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
type="FULL"
id="FULL-20080616001" prevId="FULL-20080615001">
...
<rde:deletes>
<rde:delContact>sh8013</rde:delContact>
...
<rde:delHost>ns1.example.com</rde:delHost>
...
<rde:delDomain>example.com</rde:delDomain>
...
<rde:delRegistrar>agnt0001</rde:delRegistrar>
...
</rde:deletes>
</rde:escrowDeposit>
6. Object Description
This section describes the base objects defined in EPP: domains,
hosts and objects with the addition of registrars.
6.1. RDE Domain Object
The RDE domain object is based on the EPP domain name mapping 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 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]).
Example of domain object:
Arias & Noguchi Expires January 7, 2011 [Page 10]
Internet-Draft Registry Data Escrow July 2010
...
<rde:domain
xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0">
<rdeDomain:name>example.com</rdeDomain:name>
<rdeDomain:roid>EXAMPLE1-REP</rdeDomain:roid>
<rdeDomain:status s="ok"/>
<rdeDomain:registrant>jd1234</rdeDomain:registrant>
<rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
<rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
<rdeDomain:ns
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<domain:hostObj>ns1.example.com</domain:hostObj>
<domain:hostObj>ns1.example.net</domain:hostObj>
</rdeDomain:ns>
<rdeDomain:host>ns1.example.com</rdeDomain:host>
<rdeDomain:host>ns2.example.com</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>1999-12-03T09:00:00.0Z</rdeDomain:upDate>
<rdeDomain:exDate>2005-04-03T22:00:00.0Z</rdeDomain:exDate>
<rdeDomain:trDate>2000-04-08T09:00:00.0Z</rdeDomain:trDate>
<rdeDomain:authInfo
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<domain:pw>2fooBAR</domain:pw>
</rdeDomain:authInfo>
<rdeDomain:extension>
<secDNS:create
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.0">
<secDNS:dsData>
<secDNS:keyTag>12345</secDNS:keyTag>
<secDNS:alg>3</secDNS:alg>
<secDNS:digestType>1</secDNS:digestType>
<secDNS:digest>49FD46E6C4B45C55D4AC</secDNS:digest>
</secDNS:dsData>
</secDNS:create>
</rdeDomain:extension>
</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:
Arias & Noguchi Expires January 7, 2011 [Page 11]
Internet-Draft Registry Data Escrow July 2010
...
<rde:delDomain>EXAMPLE.COM</rde:delDomain>
...
6.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 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]).
Example of <host> object:
...
<rde:host
xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0">
<rdeHost:name>ns1.example.com</rdeHost:name>
<rdeHost:roid>NS1_EXAMPLE1-REP</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-04-03T22:00:00.0Z</rdeHost:crDate>
<rdeHost:upID>ClientX</rdeHost:upID>
<rdeHost:upDate>1999-12-03T09:00:00.0Z</rdeHost:upDate>
<rdeHost:trDate>2000-04-08T09:00: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.com</rde:delHost>
...
Arias & Noguchi Expires January 7, 2011 [Page 12]
Internet-Draft Registry Data Escrow July 2010
6.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 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]).
Example <contact> object:
Arias & Noguchi Expires January 7, 2011 [Page 13]
Internet-Draft Registry Data Escrow July 2010
...
<rde:contact
xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0">
<rdeContact:id>sh8013</rdeContact:id>
<rdeContact:roid>SH8013-REP</rdeContact:roid>
<rdeContact:status s="linked"/>
<rdeContact:status s="clientDeleteProhibited"/>
<rdeContact:postalInfo type="int"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
<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.com</rdeContact:email>
<rdeContact:clID>ClientY</rdeContact:clID>
<rdeContact:crID>ClientX</rdeContact:crID>
<rdeContact:crDate>1999-04-03T22:00:00.0Z</rdeContact:crDate>
<rdeContact:upID>ClientX</rdeContact:upID>
<rdeContact:upDate>1999-12-03T09:00:00.0Z</rdeContact:upDate>
<rdeContact:trDate>2000-04-08T09:00:00.0Z</rdeContact:trDate>
<rdeContact:authInfo
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
<contact:pw>2fooBAR</contact:pw>
</rdeContact:authInfo>
<rdeContact:disclose flag="0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.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:
Arias & Noguchi Expires January 7, 2011 [Page 14]
Internet-Draft Registry Data Escrow July 2010
...
<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:
o An <id> element that contains the Registry-unique identifier of
the registrar object.
o A <company> element that contains the name of the company.
o 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.
Arias & Noguchi Expires January 7, 2011 [Page 15]
Internet-Draft Registry Data Escrow July 2010
+ An OPTIONAL <pc> element that contains the registrar's
postal code.
+ A <cc> element that contains the registrar's country code.
o An OPTIONAL <voice> element that contains the registrar's voice
telephone number.
o An OPTIONAL <fax> element that contains the registrar's facsimile
telephone number.
o A <email> element that contains the registrar's email address.
o A <url> element that contains the registrar's URL.
o One or more OPTIONAL <contact> elements that contain identifiers
for the human or organizational social information objects
associated with the registrar object.
o A <crDate> element that contains the date and time of registrar-
object creation.
o 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.
Example of <registrar> object:
Arias & Noguchi Expires January 7, 2011 [Page 16]
Internet-Draft Registry Data Escrow July 2010
...
<rde:registrar
xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0">
<rdeRegistrar:id>agnt0001</rdeRegistrar:id>
<rdeRegistrar:company type="int">Example Inc.</rdeRegistrar:company>
<rdeRegistrar:postalInfo type="int"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
<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.com</rdeRegistrar:email>
<rdeRegistrar:url>http://www.example.com</rdeRegistrar:url>
<rdeRegistrar:contact type="admin">rr0013</rdeRegistrar:contact>
<rdeRegistrar:contact type="tech">rr0012</rdeRegistrar:contact>
<rdeRegistrar:crDate>1999-04-03T22:00:00.0Z</rdeRegistrar:crDate>
<rdeRegistrar:upDate>1999-12-03T09:00:00.0Z</rdeRegistrar:upDate>
</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>agnt0001</rde:delRegistrar>
...
7. Formal Syntax
Five 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.
Arias & Noguchi Expires January 7, 2011 [Page 17]
Internet-Draft Registry Data Escrow July 2010
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:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN
<?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: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="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!--
Arias & Noguchi Expires January 7, 2011 [Page 18]
Internet-Draft Registry Data Escrow July 2010
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"/>
<annotation>
<documentation>
Registry Data Escrow schema
</documentation>
</annotation>
<!--
Root element
-->
<element name="escrowDeposit" type="rde:escrowDepositType"/>
<!--
RDE types
-->
<complexType name="escrowDepositType">
<sequence>
<element name="summary" type="rde:summaryType"/>
<element name="contents" type="rde:contentsType"/>
<element name="deletes" type="rde:deletesType"
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="summaryType">
<sequence>
<element name="watermarkDate" type="dateTime"
minOccurs="1" maxOccurs="1"/>
Arias & Noguchi Expires January 7, 2011 [Page 19]
Internet-Draft Registry Data Escrow July 2010
<element name="contentsCount" type="rde:countType"
minOccurs="1" maxOccurs="1"/>
<element name="deletesCount" type="rde:countType"
minOccurs="1" maxOccurs="1"/>
</sequence>
</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="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>
<!--
Object count type
-->
<complexType name="countType">
<sequence>
<element name="contactCount" type="unsignedLong"
minOccurs="1" maxOccurs="1"/>
<element name="hostCount" type="unsignedLong"
minOccurs="1" maxOccurs="1"/>
<element name="domainCount" type="unsignedLong"
Arias & Noguchi Expires January 7, 2011 [Page 20]
Internet-Draft Registry Data Escrow July 2010
minOccurs="1" maxOccurs="1"/>
<element name="registrarCount" type="unsignedLong"
minOccurs="1" maxOccurs="1"/>
<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>
<!--
End of schema.
-->
</schema>
END
Arias & Noguchi Expires January 7, 2011 [Page 21]
Internet-Draft Registry Data Escrow July 2010
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:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN
<?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="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!--
Import common element types
-->
Arias & Noguchi Expires January 7, 2011 [Page 22]
Internet-Draft Registry Data Escrow July 2010
<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 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"
minOccurs="0" maxOccurs="11"/>
<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="authInfo" type="domain:authInfoType"
minOccurs="0"/>
<element name="extension" type="rde:extAnyType"
minOccurs="0"/>
</sequence>
Arias & Noguchi Expires January 7, 2011 [Page 23]
Internet-Draft Registry Data Escrow July 2010
</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:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN
<?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"
Arias & Noguchi Expires January 7, 2011 [Page 24]
Internet-Draft Registry Data Escrow July 2010
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.
Arias & Noguchi Expires January 7, 2011 [Page 25]
Internet-Draft Registry Data Escrow July 2010
-->
</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:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN
<?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">
Arias & Noguchi Expires January 7, 2011 [Page 26]
Internet-Draft Registry Data Escrow July 2010
<!--
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"/>
</sequence>
</complexType>
Arias & Noguchi Expires January 7, 2011 [Page 27]
Internet-Draft Registry Data Escrow July 2010
<!--
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:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN
<?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"
Arias & Noguchi Expires January 7, 2011 [Page 28]
Internet-Draft Registry Data Escrow July 2010
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="company" type="rdeRegistrar:companyType"
maxOccurs="2"/>
<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"/>
</sequence>
</complexType>
Arias & Noguchi Expires January 7, 2011 [Page 29]
Internet-Draft Registry Data Escrow July 2010
<complexType name="companyType">
<simpleContent>
<extension base="eppcom:minTokenType">
<attribute name="type" type="contact:postalInfoEnumType"
use="required"/>
</extension>
</simpleContent>
</complexType>
<!--
End of schema.
-->
</schema>
END
8. Extension Handling
(To be developed.)
9. Internationalization Considerations
(To be developed.)
10. IANA Considerations
This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. 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.
Arias & Noguchi Expires January 7, 2011 [Page 30]
Internet-Draft Registry Data Escrow July 2010
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:
Arias & Noguchi Expires January 7, 2011 [Page 31]
Internet-Draft Registry Data Escrow July 2010
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.
11. Security Considerations
(To be developed.)
12. Acknowledgments
Parts of this document are based on EPP [RFC5730] and related RFCs by
Scott Hollenbeck.
13. References
13.1. Normative References
[ISO-3166-1]
International Organization for Standardization, "Codes for
the representation of names of countries and their
subdivisions -- Part 1: Country codes", ISO Standard 3166,
November 2006.
[ITU-E164]
Arias & Noguchi Expires January 7, 2011 [Page 32]
Internet-Draft Registry Data Escrow July 2010
International Telecommunication Union, "The international
public telecommunication numbering plan", ITU-T
Recommendation E.164, February 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for
the Extensible Provisioning Protocol (EPP)", RFC 3915,
September 2004.
[RFC4880] Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R.
Thayer, "OpenPGP Message Format", RFC 4880, November 2007.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, August 2009.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, August 2009.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Host Mapping", STD 69, RFC 5732, August 2009.
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, August 2009.
[RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS)
Security Extensions Mapping for the Extensible
Provisioning Protocol (EPP)", RFC 5910, May 2010.
13.2. Informative References
[PGP-params]
IANA, "OpenPGP parameters", <http://www.iana.org/
assignments/pgp-parameters/pgp-parameters.xhtml>.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
Arias & Noguchi Expires January 7, 2011 [Page 33]
Internet-Draft Registry Data Escrow July 2010
Authors' Addresses
Francisco Arias
Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330
Marina del Rey 90292
United States of America
Phone: +1.310.823.9358
Email: francisco.arias@icann.org
Shoji Noguchi
Japan Registry Services Co., Ltd.
Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda
Chiyoda-ku, Tokyo 101-0065
Japan
Phone: +81.3.5215.8451
Email: noguchi@jprs.co.jp
Arias & Noguchi Expires January 7, 2011 [Page 34]
