[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10

Network Working Group                                           F. Arias
Internet-Draft                                                 G. Lozano
Intended status: Standards Track                                   ICANN
Expires: April 24, 2013                                       S. Noguchi
                                                                    JPRS
                                                        October 21, 2012


          Domain Name Registration Data (DNRD) Objects Mapping
              draft-arias-noguchi-dnrd-objects-mapping-01

Abstract

   This document specifies the format and contents of Domain Name
   Registration Data (DNRD) Escrow deposits.  Specified in Extensible
   Markup Language (XML), the mapping defines Registration Data Escrow
   (RDE) deposit syntax and semantics.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 24, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as



Arias, et al.            Expires April 24, 2013                 [Page 1]


Internet-Draft            DNRD Objects Mapping              October 2012


   described in the Simplified BSD License.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  General Conventions  . . . . . . . . . . . . . . . . . . . . .  3
     3.1.  Date and Time  . . . . . . . . . . . . . . . . . . . . . .  3
     3.2.  Country names  . . . . . . . . . . . . . . . . . . . . . .  4
     3.3.  Telephone numbers  . . . . . . . . . . . . . . . . . . . .  4
     3.4.  IP addresses . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Object Description . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  RDE Domain Object  . . . . . . . . . . . . . . . . . . . .  4
     4.2.  RDE Host Object  . . . . . . . . . . . . . . . . . . . . .  9
     4.3.  RDE Contact Object . . . . . . . . . . . . . . . . . . . . 11
     4.4.  RDE Registrar Object . . . . . . . . . . . . . . . . . . . 15
     4.5.  RDE IDN Table Reference  . . . . . . . . . . . . . . . . . 18
     4.6.  RDE NNDN . . . . . . . . . . . . . . . . . . . . . . . . . 19
     4.7.  RDE EPP Parameters object  . . . . . . . . . . . . . . . . 21
   5.  RDE IDN Variants Handling  . . . . . . . . . . . . . . . . . . 23
   6.  Formal Syntax  . . . . . . . . . . . . . . . . . . . . . . . . 23
     6.1.  RDE Domain Object  . . . . . . . . . . . . . . . . . . . . 23
     6.2.  RDE Host Object  . . . . . . . . . . . . . . . . . . . . . 27
     6.3.  RDE Contact Object . . . . . . . . . . . . . . . . . . . . 29
     6.4.  RDE Registrar Object . . . . . . . . . . . . . . . . . . . 32
     6.5.  RDE IDN Table Reference Objects  . . . . . . . . . . . . . 35
     6.6.  RDE NNDN Objects . . . . . . . . . . . . . . . . . . . . . 37
     6.7.  EPP Parameters Object  . . . . . . . . . . . . . . . . . . 40
   7.  Internationalization Considerations  . . . . . . . . . . . . . 42
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 42
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 45
   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 46
   11. Change History . . . . . . . . . . . . . . . . . . . . . . . . 46
     11.1. Changes from
           draft-arias-noguchi-registry-data-escrow-02 to
           -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . . 46
     11.2. Changes from version 00 to 01  . . . . . . . . . . . . . . 46
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 47
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 47
     12.2. Informative References . . . . . . . . . . . . . . . . . . 48
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 48









Arias, et al.            Expires April 24, 2013                 [Page 2]


Internet-Draft            DNRD Objects Mapping              October 2012


1.  Introduction

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

   TBD


2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, [RFC2119].

   REGISTRY.  In the context of this draft the definition will be
   overloaded (from the definition in the base protocol) to indicate an
   organization providing Registry Services for a REGISTRY-CLASS DOMAIN
   NAME.

   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 for 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 provisioning of domain names on receipt of
   requests and data from registrars; responding to registrar queries
   for status information relating to the DNS servers for the RCDN;
   dissemination of RCDN zone files; operation of the Registry DNS
   servers; and responding to queries for 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.


3.  General Conventions

3.1.  Date and Time

   Numerous fields indicate "dates", such as the creation and expiry
   dates for domain names.  These fields SHALL contain timestamps
   indicating the date and time in UTC as specified in [RFC3339], with
   no offset from the zero meridian.






Arias, et al.            Expires April 24, 2013                 [Page 3]


Internet-Draft            DNRD Objects Mapping              October 2012


3.2.  Country names

   Country identifiers SHALL be represented using two character
   identifiers as specified in [ISO-3166-1].

3.3.  Telephone numbers

   Telephone numbers (both voice and fax) SHALL be formatted based on
   structures defined in [ITU-E164].  Telephone numbers described in
   this specification are character strings that MUST begin with a plus
   sign ("+", ASCII value 0x002B), followed by a country code defined in
   [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by
   a sequence of digits representing the telephone number.

3.4.  IP addresses

   IP addresses syntax MUST conform either to, Internet Protocol
   [RFC0791], for IPv4 addresses, or IP Version 6 Addressing
   Architecture [RFC4291], for IPv6 addresses.


4.  Object Description

   This section describes the base objects defined in EPP: domains,
   hosts and contacts with the addition of registrars, IDN Table
   References, NNDNs and EPP parameters.

4.1.  RDE Domain Object

   The RDE domain object is based on the EPP domain name mapping
   specified in [RFC5731].  There are two elements used in this format
   related to domains: the domain object per se, used inside the
   <contents> element and the <rdeDomain:delete> object used inside the
   <deletes> element.

4.1.1.  <domain> object

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

   The <domain> element contains the following child elements:






Arias, et al.            Expires April 24, 2013                 [Page 4]


Internet-Draft            DNRD Objects Mapping              October 2012


   o  A <name> element that contains the fully qualified name of the
      domain name object.

   o  A <roid> element that contains the repository object identifier
      assigned to the domain name object when it was created.

   o  One or more <status> elements that contain the current status
      descriptors associated with the domain name.

   o  Zero or more OPTIONAL <rgpStatus> element to represent the
      different states that a domain name can be in as a result of grace
      period processing as specified in [RFC3915].

   o  An OPTIONAL <registrant> element that contain the identifier for
      the human or organizational social information object associated
      as the holder of the domain name object.

   o  Zero or more OPTIONAL <contact> elements that contain identifiers
      for the human or organizational social information objects
      associated with the domain name object.

   o  An OPTIONAL <ns> element that contains the fully qualified names
      of the delegated host objects or host attributes (name servers)
      associated with the domain name object.  See Section 1.1 of
      [RFC5731] for a description of the elements used to specify host
      objects or host attributes.

   o  A <clID> element that contains the identifier of the sponsoring
      registrar.

   o  A <crID> element that contains the identifier of the registrar
      that created the domain name object.

   o  An OPTIONAL <crDate> element that contains the date and time of
      the domain name object creation.

   o  An OPTIONAL <exDate> element that contains the date and time
      identifying the end (expiration) of the domain name object's
      registration period.

   o  An <upID> element that contains the identifier of the registrar
      that last updated the domain name object.  This element MUST NOT
      be present if the domain has never been modified.

   o  An <upDate> element that contains the date and time of the most
      recent domain-name-object modification.  This element MUST NOT be
      present if the domain name object has never been modified.




Arias, et al.            Expires April 24, 2013                 [Page 5]


Internet-Draft            DNRD Objects Mapping              October 2012


   o  An <trDate> element that contains the date and time of the most
      recent domain object successful transfer.  This element MUST NOT
      be present if the domain name object has never been transfered.

   o  A <deDate> element that contains the deletion date for the domain.
      This element is used by registries that support the Domain
      Registry Grace Period as specified in [RFC3915].  This element
      MUST be present if the domain name has been deleted, but not yet
      purged from the registry repository.

   o  An <authInfo> element that contains authorization information
      associated with the domain name object.

   o  An OPTIONAL <secDNS> element that contains the public key
      information associated with Domain Name System security (DNSSEC)
      extensions for the domain name as specified in [RFC5910].

   o  An OPTIONAL <idnTableId> element that references the IDN Table
      used for the IDN.  This corresponds to the "id" attribute of the
      <idnTableRef> element.  This element MUST be present if the domain
      name object is an IDN or variantGenerator is present.

   o  An OPTIONAL <variantGenerator> element that can be used to specify
      algorithmically generated variants, e.g., when the number of
      variants is so big that is unpractical to list them explicitly.  A
      defaultState attribute can be used to specify the default state
      for the generated variants: blocked, withheld or allocated.  If
      the LGR does not specify the state of the generated variants then
      the default_state attribute is used.  The LGR defined IDN variant
      state takes precedence over the default_state attribute.

   o  An OPTIONAL <trnData> element that contains the following child
      elements related to the last transfer request of the domain name
      object.  This element MUST NOT be present if a transfer request
      for the domain name has never been created.

      *  A <trStatus> element that contains the state of the most recent
         transfer request.

      *  A <reID> element that contains the identifier of the registrar
         that requested the domain name object transfer.

      *  A <reDate> element that contains the date and time that the
         transfer was requested.

      *  An <acID> element that contains the identifier of the registrar
         that SHOULD act upon a PENDING transfer request.  For all other
         status types, the value identifies the registrar that took the



Arias, et al.            Expires April 24, 2013                 [Page 6]


Internet-Draft            DNRD Objects Mapping              October 2012


         indicated action.

      *  An <acDate> element that contains the date and time of a
         required or completed response.  For a PENDING request, the
         value identifies the date and time by which a response is
         required before an automated response action will be taken by
         the registry.  For all other status types, the value identifies
         the date and time when the request was completed.

      *  An <exDate> element that contains the end of the domain name
         object's validity period (expiry date) if the transfer caused
         or causes a change in the validity period.

   Example of a domain object:





































Arias, et al.            Expires April 24, 2013                 [Page 7]


Internet-Draft            DNRD Objects Mapping              October 2012


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







Arias, et al.            Expires April 24, 2013                 [Page 8]


Internet-Draft            DNRD Objects Mapping              October 2012


4.1.2.  <rdeDomain:delete> object

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

   Example of <rdeDomain:delete> object:


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

4.2.  RDE Host Object

   The RDE host object is based on the EPP host name mapping in
   [RFC5732].  There are two elements used in this format related to
   hosts: the host object per se, used inside the <contents> element and
   the <rdeHost:delete> object used inside the <deletes> element.

4.2.1.  <host> object

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

   The OPTIONAL <host> element contains the following child elements:

   o  A <name> element that contains the fully qualified name of the
      host object.

   o  A <roid> element that contains the repository object identifier
      assigned to the host object when the object was created.

   o  One or more <status> elements that describe the status of the host
      object.

   o  Zero or more <addr> elements that contain the IP addresses
      associated with the host object.

   o  A <clID> element that contains the identifier of the sponsoring
      registrar.




Arias, et al.            Expires April 24, 2013                 [Page 9]


Internet-Draft            DNRD Objects Mapping              October 2012


   o  A <crID> element that contains the identifier of the registrar
      that created the host object.

   o  A <crDate> element that contains the date and time of host-object
      creation.

   o  An <upID> element that contains the identifier of the registrar
      that last updated the host object.  This element MUST NOT be
      present if the host object has never been modified.

   o  An <upDate> element that contains the date and time of the most
      recent host-object modification.  This element MUST NOT be present
      if the host object has never been modified.

   Example of <host> object:


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

4.2.2.  <rdeHost:delete> object

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

   Example of <rdeHost:delete> object:











Arias, et al.            Expires April 24, 2013                [Page 10]


Internet-Draft            DNRD Objects Mapping              October 2012


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

4.3.  RDE Contact Object

   The RDE contact object is based on the EPP contact name mapping in
   [RFC5733].  There are two elements used in this format related to
   contacts: the contact object per se, used inside the <contents>
   element and the <rdeContact:delete> object used inside the <deletes>
   element.

4.3.1.  <contact> object

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

   The OPTIONAL <contact> element contains the following child elements:

   o  An <id> element that contains the repository object identifier
      assigned to the contact object when the object was created.

   o  One or more <status> elements that describe the status of the
      contact object.

   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:

      *  A <name> element that contains the name of the individual or
         role represented by the contact.





Arias, et al.            Expires April 24, 2013                [Page 11]


Internet-Draft            DNRD Objects Mapping              October 2012


      *  An OPTIONAL <org> element that contains the name of the
         organization with which the contact is affiliated.

      *  An <addr> element that contains address information associated
         with the contact.  An <addr> element contains the following
         child elements:

         +  One, two, or three OPTIONAL <street> elements that contain
            the contact's street address.

         +  A <city> element that contains the contact's city.

         +  An OPTIONAL <sp> element that contains the contact's state
            or province.

         +  An OPTIONAL <pc> element that contains the contact's postal
            code.

         +  A <cc> element that contains the contact's two-letter
            country code.

   o  An OPTIONAL <voice> element that contains the contact's voice
      telephone number.

   o  An OPTIONAL <fax> element that contains the contact's facsimile
      telephone number.

   o  An <email> element that contains the contact's email address.

   o  A <clID> element that contains the identifier of the sponsoring
      registrar.

   o  A <crID> element that contains the identifier of the registrar
      that created the contact object.

   o  A <crDate> element that contains the date and time of contact-
      object creation.

   o  An <upID> element that contains the identifier of the registrar
      that last updated the contact object.  This element MUST NOT be
      present if the contact has never been modified.

   o  An <upDate> element that contains the date and time of the most
      recent contact-object modification.  This element MUST NOT be
      present if the contact object has never been modified.

   o  An <trDate> element that contains the date and time of the most
      recent contact object sucessful transfer.  This element MUST NOT



Arias, et al.            Expires April 24, 2013                [Page 12]


Internet-Draft            DNRD Objects Mapping              October 2012


      be present if the contact object has never been transfered.

   o  An <authInfo> element that contains authorization information
      associated with the contact object.

   o  An OPTIONAL <disclose> element that identifies elements that
      require exceptional server-operator handling to allow or restrict
      disclosure to third parties.  See Section 2.9 of [RFC5733] for a
      description of the child elements contained within the <disclose>
      element.

   o  A <trnData> element that contains the following child elements
      related to the last transfer request of the contact object:

      *  A <trStatus> element that contains the state of the most recent
         transfer request.

      *  A <reID> element that contains the identifier of the registrar
         that requested the domain name object transfer.

      *  A <reDate> element that contains the date and time that the
         transfer was requested.

      *  An <acID> element that contains the identifier of the registrar
         that SHOULD act upon a PENDING transfer request.  For all other
         status types, the value identifies the registrar that took the
         indicated action.

      *  An <acDate> element that contains the date and time of a
         required or completed response.  For a PENDING request, the
         value identifies the date and time by which a response is
         required before an automated response action will be taken by
         the registry.  For all other status types, the value identifies
         the date and time when the request was completed.

   Example <contact> object:















Arias, et al.            Expires April 24, 2013                [Page 13]


Internet-Draft            DNRD Objects Mapping              October 2012


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








Arias, et al.            Expires April 24, 2013                [Page 14]


Internet-Draft            DNRD Objects Mapping              October 2012


4.3.2.  <rdeContact:delete> object

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

   Example of <rdeContact:delete> object:


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

4.4.  RDE Registrar Object

   The RDE registrar object is based on the EPP contact name mapping
   previously described.  There are two elements used in this format
   related to registrars: the registrar object per se, used inside the
   <contents> element and the <rdeRegistrar:delete> object used inside
   the <deletes> element.

4.4.1.  <registrar> object

   The <registrar> element contains the following child elements:

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

   o  An OPTIONAL <gurid> element that contains the ID assigned by
      ICANN.

   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



Arias, et al.            Expires April 24, 2013                [Page 15]


Internet-Draft            DNRD Objects Mapping              October 2012


      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.

   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  An <email> element that contains the registrar's email address.

   o  An OPTIONAL <url> element that contains the registrar's URL.

   o  An OPTIONAL <whoisInfo> elements that contains whois information.
      The <whoisInfo> element contains the following child elements:

      *  An OPTIONAL <name> element that contains the name of the
         registrar WHOIS server listenin on TCP port 43 as specified in
         [RFC3912].

      *  An OPTIONAL <url> element that contains the name of the
         registrar WHOIS server listenin on TCP port 80/443.

   o  Zero 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.



Arias, et al.            Expires April 24, 2013                [Page 16]


Internet-Draft            DNRD Objects Mapping              October 2012


   o  An OPTIONAL <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.

   o  An OPTIONAL <authInfo> element that contains authorization
      information associated with the registar object to allow access to
      registry systems.  This specification describes password-based
      authorization information, though other mechanisms are possible.

   Example of <registrar> object:

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




Arias, et al.            Expires April 24, 2013                [Page 17]


Internet-Draft            DNRD Objects Mapping              October 2012


4.4.2.  <rdeRegistrar:delete> object

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

   Example of <rdeRegistrar:delete> object:


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

4.5.  RDE IDN Table Reference

   The RDE Internationalized Domain Names (IDN) Table reference is a
   pseudobject that is used to provide a short reference to the IDN
   Table used in IDN registrations.  The <idnTableRef> element has an
   "id" attribute that is used to uniquely identify an IDN Table stored
   externally.

4.5.1.  <idnTableRef> object

   The OPTIONAL <idnTableRef> contains the following elements:

   o  An <url> element that contains the URL of the IDN table that is
      being referenced.

   o  An <lgr> element that contains the type of representation of the
      Label Generation Ruleset (LGR).  Allowed values are: [RFC3743],
      [RFC4290] and draft-davies-idntables.

   Example of <idnTableRef> object:


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



Arias, et al.            Expires April 24, 2013                [Page 18]


Internet-Draft            DNRD Objects Mapping              October 2012


4.6.  RDE NNDN

4.6.1.  NNDN's not domain name

   A NNDN (NNDN's not domain name) does not exist as a domain object; it
   is stored in the SRS database and precludes the coexistence of an
   homonimous domain object.  NNDNs can be used to store registry
   reserved names or IDN variant handling.  A NNDN of state withheld and
   blocked can be created because of IDN variant handling or for other
   purposes like a list of reserved names.  An allocated NNDN can only
   be created if it is an IDN variant.

4.6.2.  <NNDN> object

   The OPTIONAL <NNDN> element contains the following child elements:

   o  An <aName> element that contains the ASCII Compatible Encoding
      (ACE) of the NNDN.

   o  An OPTIONAL <uName> element that contains the name of the NNDN in
      Unicode character set.  It MUST be provided if available.

   o  A <nameState> element that indicates the state of the NNDN:
      blocked, withheld and allocated.

      *  If a NNDN is considered undesirable for registration (i.e.,
         unavailable for allocation to anyone), then the NNDN will be
         tagged as "blocked".

      *  If a NNDN is created to allow the registration of a domain
         object to a particular registrant then the NNDN will be tagged
         as "withheld".

      *  If a NNDN is created to replicate the exact information from
         the canonical name, then the NNDN will be tagged "allocated".
         A NNDN of state "allocated" reflect the same information from
         the canonical domain.  E.g.  If the canonical domain is present
         in the DNS zone, then the NNDN is going to be present in the
         DNS zone.

   o  An OPTIONAL <idnTableId> element that references the IDN Table in
      case the NNDN is an IDN variant.  This corresponds to the "id"
      attribute of the <idnTableRef> element.

   o  A <crDate> element that contains the date and time of the NNDN
      object creation.





Arias, et al.            Expires April 24, 2013                [Page 19]


Internet-Draft            DNRD Objects Mapping              October 2012


   o  An OPTIONAL <originElement> element that MUST be present when
      state is withheld or allocated.  One of the following elements
      MUST be present.

      *  An OPTIONAL <canonicalRoid> element that contains the
         repository object identifier of the canonical domain name.  An
         IDN variant generated NNDN MUST be associated to a canonical
         domain name.

      *  An OPTIONAL <registrant> element that contain the identifier
         for the human or organizational social information object
         allowed to register the domain name.  The <registrant> element
         takes precedence over the registrant of the <canonicalRoid>
         domain name in case <registrant> and <canonicalRoid> are
         present.

   Example of <NNDN> object:


   ...
   <rdeNDN:NNDN>
       <rdeNDN:aName>xn--pingino-q2a.test</rdeNDN:aName>
       <rdeNDN:uName>pingueino.test</rdeNDN:uName>
       <rdeNDN:nameState>allocated</rdeNDN:nameState>
       <rdeNDN:idnTableId>cl-es</rdeNDN:idnTableId>
       <rdeNDN:crDate>2005-04-23T11:49:00.0Z</rdeNDN:crDate>
       <rdeNDN:originElement><rdeNDN:canonicalRoid>Dpinguino-TEST
       </rdeNDN:canonicalRoid></rdeNDN:originElement></rdeNDN:NNDN>
   ...

4.6.3.  <rdeNDN:delete> object

   The <rdeNDN:delete> element contains the ACE of a NNDN that was
   deleted, i.e., the <aName>.

   Example of <rdeNDN:delete> object:


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




Arias, et al.            Expires April 24, 2013                [Page 20]


Internet-Draft            DNRD Objects Mapping              October 2012


4.7.  RDE EPP Parameters object

   An OPTIONAL <eppParams> element contains some EPP parameters that may
   be helpful when rebuilding a registry from the escrow deposits.  The
   element SHOULD be included in Deposits if the registry uses EPP.

   The syntax and content of the <eppParams> children elements is as
   explained in section 2.4 of [RFC5730].  The children of the
   <eppParams> are as follows:

   o  One or more <version> elements that indicate the EPP versions
      supported by the registry.

   o  One or more <lang> elements that indicate the identifiers of the
      text response languages supported by the registry's EPP server.

   o  One or more <objURI> elements that contain namespace URIs
      representing the objects that the registry's EPP server is capable
      of managing.

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

   o  A <dcp> element that contains child elements used to describe the
      server's privacy policy for data collection and management.  See
      section 2.4 of [RFC5730] for more details.

   Example of <eppParams> element object:






















Arias, et al.            Expires April 24, 2013                [Page 21]


Internet-Draft            DNRD Objects Mapping              October 2012


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



Arias, et al.            Expires April 24, 2013                [Page 22]


Internet-Draft            DNRD Objects Mapping              October 2012


5.  RDE IDN Variants Handling

   Depending on the Registration Policy of the Registry; for a
   particular domain name there may be multiple variant names.  See
   [variantTLDsReport] for further detail on IDN variants.

   A registry could choose to create IDN variants as domain or NNDN
   objects.

   A LGR could be used to compute IDN variants in real-time by the
   registry instead of creating domain or NNDN objects.

   A NNDN or a domain name are explicit representations of an IDN
   variant while an IDN variant computed based on a LGR is an implicit
   representation.  Explicit representation of an IDN variant takes
   precedence over an implicit representation.


6.  Formal Syntax

   Seven schemas are presented here.  The first schema is the base RDE
   schema.  The second schema defines domain object for RDE.  The third
   schema defines host object for RDE.  The fourth schema defines
   contact object for RDE.  The fifth schema defines registrar object
   for RDE.  The sixth schema defines the idnTableRef and IDN objects.
   The last schema defines the eppParams objects.

6.1.  RDE Domain Object

   Copyright (c) 2011 IETF Trust and the persons identified as authors
   of the code.  All rights reserved.

   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions
   are met:

   o  Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.

   o  Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in
      the documentation and/or other materials provided with the
      distribution.

   o  Neither the name of Internet Society, IETF or IETF Trust, nor the
      names of specific contributors, may be used to endorse or promote
      products derived from this software without specific prior written
      permission.



Arias, et al.            Expires April 24, 2013                [Page 23]


Internet-Draft            DNRD Objects Mapping              October 2012


   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
   A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT
   OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
   LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
   DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
   THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

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

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

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

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

     <!--
     Child elements of the <rde:contents> object
     -->



Arias, et al.            Expires April 24, 2013                [Page 24]


Internet-Draft            DNRD Objects Mapping              October 2012


     <element name="contents" type="rdeDomain:contentsType"
      substitutionGroup="rde:contents"/>

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

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

    <complexType name="contentType">
     <complexContent>
      <extension base="rde:contentType">
       <sequence>
        <element name="name" type="eppcom:labelType"/>
        <element name="roid" type="eppcom:roidType"/>
        <element name="status" type="domain:statusType"
         maxOccurs="11"/>
        <element name="rgpStatus" type="rgp:statusType"
         minOccurs="0"/>
        <element name="registrant" type="eppcom:clIDType"
         minOccurs="0"/>
        <element name="contact" type="domain:contactType"
         minOccurs="0" maxOccurs="unbounded"/>
        <element name="ns" type="domain:nsType"
         minOccurs="0"/>
        <element name="clID" type="eppcom:clIDType"/>
        <element name="crID" type="eppcom:clIDType"
         minOccurs="0"/>
        <element name="crDate" type="dateTime"
         minOccurs="0"/>
        <element name="exDate" type="dateTime"
         minOccurs="0"/>
        <element name="upID" type="eppcom:clIDType"
         minOccurs="0"/>
        <element name="upDate" 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"/>



Arias, et al.            Expires April 24, 2013                [Page 25]


Internet-Draft            DNRD Objects Mapping              October 2012


        <element name="secDNS" type="secDNS:dsOrKeyType"
         minOccurs="0"/>
        <element name="idnTableId" type="IDREF"
         minOccurs="0"/>
        <element name="trnData" type="rdeDomain:transferDataType"
         minOccurs="0"/>
       </sequence>
      </extension>
     </complexContent>
    </complexType>

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

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

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

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






Arias, et al.            Expires April 24, 2013                [Page 26]


Internet-Draft            DNRD Objects Mapping              October 2012


6.2.  RDE Host Object

   Copyright (c) 2011 IETF Trust and the persons identified as authors
   of the code.  All rights reserved.

   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions
   are met:

   o  Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.

   o  Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in
      the documentation and/or other materials provided with the
      distribution.

   o  Neither the name of Internet Society, IETF or IETF Trust, nor the
      names of specific contributors, may be used to endorse or promote
      products derived from this software without specific prior written
      permission.

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



Arias, et al.            Expires April 24, 2013                [Page 27]


Internet-Draft            DNRD Objects Mapping              October 2012


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

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

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

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

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

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



Arias, et al.            Expires April 24, 2013                [Page 28]


Internet-Draft            DNRD Objects Mapping              October 2012


           </sequence>
         </extension>
       </complexContent>
     </complexType>

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

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

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

6.3.  RDE Contact Object

   Copyright (c) 2011 IETF Trust and the persons identified as authors
   of the code.  All rights reserved.

   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions
   are met:

   o  Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.

   o  Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in
      the documentation and/or other materials provided with the
      distribution.

   o  Neither the name of Internet Society, IETF or IETF Trust, nor the
      names of specific contributors, may be used to endorse or promote
      products derived from this software without specific prior written



Arias, et al.            Expires April 24, 2013                [Page 29]


Internet-Draft            DNRD Objects Mapping              October 2012


      permission.

   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
   A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT
   OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
   LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
   DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
   THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

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

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

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

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

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

     <complexType name="contentsType">



Arias, et al.            Expires April 24, 2013                [Page 30]


Internet-Draft            DNRD Objects Mapping              October 2012


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

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

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

    <complexType name="transferDataType">
     <sequence>



Arias, et al.            Expires April 24, 2013                [Page 31]


Internet-Draft            DNRD Objects Mapping              October 2012


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

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

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

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

6.4.  RDE Registrar Object

   Copyright (c) 2011 IETF Trust and the persons identified as authors
   of the code.  All rights reserved.

   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions
   are met:

   o  Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.

   o  Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in
      the documentation and/or other materials provided with the
      distribution.




Arias, et al.            Expires April 24, 2013                [Page 32]


Internet-Draft            DNRD Objects Mapping              October 2012


   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"
           xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
           xmlns="http://www.w3.org/2001/XMLSchema"
           elementFormDefault="qualified">

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

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

     <!--



Arias, et al.            Expires April 24, 2013                [Page 33]


Internet-Draft            DNRD Objects Mapping              October 2012


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

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

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

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



Arias, et al.            Expires April 24, 2013                [Page 34]


Internet-Draft            DNRD Objects Mapping              October 2012


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

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

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

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

6.5.  RDE IDN Table Reference Objects

   Copyright (c) 2011 IETF Trust and the persons identified as authors
   of the code.  All rights reserved.

   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions
   are met:

   o  Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.

   o  Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in
      the documentation and/or other materials provided with the
      distribution.



Arias, et al.            Expires April 24, 2013                [Page 35]


Internet-Draft            DNRD Objects Mapping              October 2012


   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:rdeIDN-1.0"
           xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
           xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
           xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
           xmlns="http://www.w3.org/2001/XMLSchema"
           elementFormDefault="qualified">

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

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

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

     <complexType name="idnTableRefType">



Arias, et al.            Expires April 24, 2013                [Page 36]


Internet-Draft            DNRD Objects Mapping              October 2012


       <complexContent>
         <extension base="rde:contentType">
           <sequence>
             <element name="url" type="anyURI"/>
           </sequence>
           <attribute name="lgr" type="rdeIDN:LGRType"/>
         </extension>
       </complexContent>
     </complexType>

     <simpleType name="LGRType">
       <restriction base="token">
         <enumeration value="RFC3743"/>
         <enumeration value="RFC4290"/>
         <enumeration value="XML"/>
       </restriction>
     </simpleType>

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

6.6.  RDE NNDN Objects

   Copyright (c) 2011 IETF Trust and the persons identified as authors
   of the code.  All rights reserved.

   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions
   are met:

   o  Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.

   o  Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in
      the documentation and/or other materials provided with the
      distribution.

   o  Neither the name of Internet Society, IETF or IETF Trust, nor the
      names of specific contributors, may be used to endorse or promote
      products derived from this software without specific prior written
      permission.

   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT



Arias, et al.            Expires April 24, 2013                [Page 37]


Internet-Draft            DNRD Objects Mapping              October 2012


   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:rdeNNDN-1.0"
           xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
           xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
           xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
           xmlns="http://www.w3.org/2001/XMLSchema"
           elementFormDefault="qualified">

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

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

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

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

     <!--
     Child elements of the <rde:content> object



Arias, et al.            Expires April 24, 2013                [Page 38]


Internet-Draft            DNRD Objects Mapping              October 2012


     -->
     <element name="nndn" type="rdeNNDN:contentType"
      substitutionGroup="rde:content"/>

     <complexType name="contentType">
       <complexContent>
         <extension base="rde:contentType">
           <sequence>
             <element name="aName" type="eppcom:labelType"/>
             <element name="uName" type="eppcom:labelType"
              minOccurs="0"/>
             <element name="nameState" type="rdeNNDN:nameState"/>
             <element name="idnTableId" type="IDREF"/>
             <element name="roid" type="eppcom:roidType"
              minOccurs="0"/>
             <element name="crDate" type="dateTime"/>
             <element name="originElement" type="rdeNNDN:originElement"
              minOccurs="0"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <simpleType name="nameState">
       <restriction base="token">
         <enumeration value="allocated"/>
         <enumeration value="withheld"/>
         <enumeration value="blocked"/>
       </restriction>
     </simpleType>

       <complexType name="originElement">
         <sequence>
           <element name="canonicalRoid" type="eppcom:roidType"
            minOccurs="0"/>
           <element name="registrant" type="eppcom:clIDType"
            minOccurs="0"/>
         </sequence>
       </complexType>

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

     <complexType name="deleteType">
       <complexContent>



Arias, et al.            Expires April 24, 2013                [Page 39]


Internet-Draft            DNRD Objects Mapping              October 2012


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

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

6.7.  EPP Parameters Object

   Copyright (c) 2011 IETF Trust and the persons identified as authors
   of the code.  All rights reserved.

   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions
   are met:

   o  Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.

   o  Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in
      the documentation and/or other materials provided with the
      distribution.

   o  Neither the name of Internet Society, IETF or IETF Trust, nor the
      names of specific contributors, may be used to endorse or promote
      products derived from this software without specific prior written
      permission.

   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
   A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT
   OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
   LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
   DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
   THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.



Arias, et al.            Expires April 24, 2013                [Page 40]


Internet-Draft            DNRD Objects Mapping              October 2012


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

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

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

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

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

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

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

     <complexType name="contentType">
       <complexContent>
         <extension base="rde:contentType">



Arias, et al.            Expires April 24, 2013                [Page 41]


Internet-Draft            DNRD Objects Mapping              October 2012


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

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


7.  Internationalization Considerations

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


8.  IANA Considerations

   This document uses URNs to describe XML namespaces and XML schemas
   conforming to a registry mechanism described in [RFC3688].  Fourteen
   URI assignments have been registered by the IANA.

   Registration request for the RDE namespace:

      URI: urn:ietf:params:xml:ns:rde-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      XML: None.  Namespace URIs do not represent an XML specification.




Arias, et al.            Expires April 24, 2013                [Page 42]


Internet-Draft            DNRD Objects Mapping              October 2012


   Registration request for the RDE XML schema:

      URI: urn:ietf:params:xml:schema:rde-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      See the "Formal Syntax" section of this document.

   Registration request for the RDE domain namespace:

      URI: urn:ietf:params:xml:ns:rdeDomain-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      XML: None.  Namespace URIs do not represent an XML specification.

   Registration request for the RDE domain XML schema:

      URI: urn:ietf:params:xml:schema:rdeDomain-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      See the "Formal Syntax" section of this document.

   Registration request for the RDE host namespace:

      URI: urn:ietf:params:xml:ns:rdeHost-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      XML: None.  Namespace URIs do not represent an XML specification.

   Registration request for the RDE host XML schema:

      URI: urn:ietf:params:xml:schema:rdeHost-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      See the "Formal Syntax" section of this document.

   Registration request for the RDE contact namespace:





Arias, et al.            Expires April 24, 2013                [Page 43]


Internet-Draft            DNRD Objects Mapping              October 2012


      URI: urn:ietf:params:xml:ns:rdeContact-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      XML: None.  Namespace URIs do not represent an XML specification.

   Registration request for the RDE contact XML schema:

      URI: urn:ietf:params:xml:schema:rdeContact-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      See the "Formal Syntax" section of this document.

   Registration request for the RDE registrar namespace:

      URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      XML: None.  Namespace URIs do not represent an XML specification.

   Registration request for the RDE registrar XML schema:

      URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      See the "Formal Syntax" section of this document.

   Registration request for the RDE IDN namespace:

      URI: urn:ietf:params:xml:ns:rdeIDN-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      XML: None.  Namespace URIs do not represent an XML specification.

   Registration request for the RDE IDN XML schema:

      URI: urn:ietf:params:xml:schema:rdeIDN-1.0





Arias, et al.            Expires April 24, 2013                [Page 44]


Internet-Draft            DNRD Objects Mapping              October 2012


      Registrant Contact: See the "Author's Address" section of this
      document.

      See the "Formal Syntax" section of this document.

   Registration request for the RDE EPP parameters namespace:

      URI: urn:ietf:params:xml:ns:rdeEppParams-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      XML: None.  Namespace URIs do not represent an XML specification.

   Registration request for the RDE EPP parameters XML schema:

      URI: urn:ietf:params:xml:schema:rdeEppParams-1.0

      Registrant Contact: See the "Author's Address" section of this
      document.

      See the "Formal Syntax" section of this document.


9.  Security Considerations

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

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

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

   Additionally, the Registry and the Escrow Agent SHOULD use integrity
   checking mechanisms to ensure the data transmitted is what the source
   intended.  Validation of the contents by the Escrow Agent is



Arias, et al.            Expires April 24, 2013                [Page 45]


Internet-Draft            DNRD Objects Mapping              October 2012


   RECOMMENDED to ensure not only the file was transmitted correctly
   from the Registry, but also the contents are also "meaningful".


10.  Acknowledgments

   Parts of this document are based on EPP [RFC5730] and related RFCs by
   Scott Hollenbeck.

   TBD


11.  Change History

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

11.1.  Changes from draft-arias-noguchi-registry-data-escrow-02 to
       -dnrd-objects-mapping-00

   1.  Added definition for child elements under the <domain> element.

   2.  Added definition for child elements under the <host> element.

   3.  Added definition for child elements under the <contact> element.

   4.  Rewrote the IDN Variants Handling section to use the variant
       states as described in ICANN's Study of Issues Related to the
       Management of IDN Variant TLDs.

   5.  Renamed <icannID> to <gurid> in the <rdeRegistrar>.

   6.  Renamed <dnssec> to <secDNS> in the <domain> element.

   7.  Renamed <transfData> to <trnData> in the <domain> element.

   8.  Added <whoisInfo> element under <rdeRegistrar> element.

   9.  Fixed some typographical errors and omissions.

11.2.  Changes from version 00 to 01

   1.  Specify OPTIONAL elements in the draft.

   2.  Added NNDN object to support list of reserved names and different
       IDN variants models.

   3.  Removed subordinated host element from the domain object.




Arias, et al.            Expires April 24, 2013                [Page 46]


Internet-Draft            DNRD Objects Mapping              October 2012


   4.  Added eppParams object.

   5.  Added variantGenerator element to the domain object.

   6.  Added lgr to the IDN table object.


12.  References

12.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]
              International Telecommunication Union, "The international
              public telecommunication numbering plan", ITU-T
              Recommendation E.164, February 2005.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC3339]  Klyne, G., Ed. and C. Newman, "Date and Time on the
              Internet: Timestamps", RFC 3339, July 2002.

   [RFC3915]  Hollenbeck, S., "Domain Registry Grace Period Mapping for
              the Extensible Provisioning Protocol (EPP)", RFC 3915,
              September 2004.

   [RFC5731]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Domain Name Mapping", STD 69, RFC 5731, August 2009.

   [RFC5732]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Host Mapping", STD 69, RFC 5732, August 2009.

   [RFC5733]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Contact Mapping", STD 69, RFC 5733, August 2009.

   [RFC5910]  Gould, J. and S. Hollenbeck, "Domain Name System (DNS)
              Security Extensions Mapping for the Extensible
              Provisioning Protocol (EPP)", RFC 5910, May 2010.







Arias, et al.            Expires April 24, 2013                [Page 47]


Internet-Draft            DNRD Objects Mapping              October 2012


12.2.  Informative References

   [RFC0791]  Postel, J., "Internet Protocol", STD 5, RFC 791,
              September 1981.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              January 2004.

   [RFC3743]  Konishi, K., Huang, K., Qian, H., and Y. Ko, "Joint
              Engineering Team (JET) Guidelines for Internationalized
              Domain Names (IDN) Registration and Administration for
              Chinese, Japanese, and Korean", RFC 3743, April 2004.

   [RFC3912]  Daigle, L., "WHOIS Protocol Specification", RFC 3912,
              September 2004.

   [RFC4290]  Klensin, J., "Suggested Practices for Registration of
              Internationalized Domain Names (IDN)", RFC 4290,
              December 2005.

   [RFC4291]  Hinden, R. and S. Deering, "IP Version 6 Addressing
              Architecture", RFC 4291, February 2006.

   [RFC5730]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
              STD 69, RFC 5730, August 2009.

   [variantTLDsReport]
              Internet Corporation for Assigned Names and Numbers
              (ICANN), "A Study of Issues Related to the Management of
              IDN Variant TLDs", February 2012, <http://www.icann.org/
              en/topics/idn/
              idn-vip-integrated-issues-final-clean-20feb12-en.pdf>.


Authors' Addresses

   Francisco Arias
   Internet Corporation for Assigned Names and Numbers
   12025 Waterfront Drive, Suite 300
   Los Angeles  90292
   United States of America

   Phone: +1.310.823.9358
   Email: francisco.arias@icann.org







Arias, et al.            Expires April 24, 2013                [Page 48]


Internet-Draft            DNRD Objects Mapping              October 2012


   Gustavo Lozano
   Internet Corporation for Assigned Names and Numbers
   12025 Waterfront Drive, Suite 300
   Los Angeles  90292
   United States of America

   Phone: +1.310.823.9358
   Email: gustavo.lozano@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, et al.            Expires April 24, 2013                [Page 49]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/