Network Working Group                                         J.G. Gould
Internet-Draft                                            VeriSign, Inc.
Intended status: Informational                          15 November 2021
Expires: 19 May 2022


       Domain Name Registration Data (DNRD) .NAME Object Mapping
                    draft-gould-dnrd-name-mapping-00

Abstract

   This document defines the data escrow structure of depositing objects
   specific to the .NAME Top Level Domain (TLD) as an extension to the
   objects deposited with DNRD Objects Mapping.  The .NAME TLD-specific
   objects are Email Forwarding, Defensive Registration, and NameWatch.

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 https://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 19 May 2022.

Copyright Notice

   Copyright (c) 2021 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 (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.





Gould                      Expires 19 May 2022                  [Page 1]


Internet-Draft             DNRD .NAME Mapping              November 2021


   This document may not be modified, and derivative works of it may not
   be created, except to format it for publication as an RFC or to
   translate it into languages other than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Models  . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  General Conventions . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Date and Time . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  CSV common field elements . . . . . . . . . . . . . . . .   6
     4.3.  Contact Object  . . . . . . . . . . . . . . . . . . . . .   6
     4.4.  Registrar Object  . . . . . . . . . . . . . . . . . . . .   6
     4.5.  CSV Parent Child Relationship . . . . . . . . . . . . . .   6
   5.  Object Description  . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Email Forwarding Object . . . . . . . . . . . . . . . . .   6
       5.1.1.  XML Model . . . . . . . . . . . . . . . . . . . . . .   6
         5.1.1.1.  <rdeEmailFwd:emailFwd> object . . . . . . . . . .   7
         5.1.1.2.  <rdeEmailFwd:delete> object . . . . . . . . . . .   9
       5.1.2.  CSV Model . . . . . . . . . . . . . . . . . . . . . .  10
         5.1.2.1.  <csvEmailFwd:contents>  . . . . . . . . . . . . .  10
         5.1.2.2.  <csvEmailFwd:deletes> . . . . . . . . . . . . . .  17
     5.2.  Defensive Registration Object . . . . . . . . . . . . . .  18
       5.2.1.  XML Model . . . . . . . . . . . . . . . . . . . . . .  18
         5.2.1.1.  <rdeDefReg:defReg> object . . . . . . . . . . . .  19
         5.2.1.2.  <rdeDefReg:delete> object . . . . . . . . . . . .  21
       5.2.2.  CSV Model . . . . . . . . . . . . . . . . . . . . . .  22
         5.2.2.1.  <csvDefReg:contents>  . . . . . . . . . . . . . .  22
         5.2.2.2.  <csvDefReg:deletes> . . . . . . . . . . . . . . .  28
     5.3.  NameWatch Object  . . . . . . . . . . . . . . . . . . . .  29
       5.3.1.  XML Model . . . . . . . . . . . . . . . . . . . . . .  29
         5.3.1.1.  <rdeNameWatch:nameWatch> object . . . . . . . . .  30
         5.3.1.2.  <rdeNameWatch:delete> object  . . . . . . . . . .  32
       5.3.2.  CSV Model . . . . . . . . . . . . . . . . . . . . . .  32
         5.3.2.1.  <csvNameWatch:contents> . . . . . . . . . . . . .  33
         5.3.2.2.  <csvNameWatch:deletes>  . . . . . . . . . . . . .  38
   6.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .  39
     6.1.  RDE Email Forwarding Object . . . . . . . . . . . . . . .  39
     6.2.  CSV Email Forwarding Object . . . . . . . . . . . . . . .  41
     6.3.  RDE Defensive Registration Object . . . . . . . . . . . .  44
     6.4.  CSV Defensive Registration Object . . . . . . . . . . . .  46
     6.5.  RDE NameWatch Object  . . . . . . . . . . . . . . . . . .  49
     6.6.  CSV NameWatch Object  . . . . . . . . . . . . . . . . . .  51
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  54
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  54
   9.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  54
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  54



Gould                      Expires 19 May 2022                  [Page 2]


Internet-Draft             DNRD .NAME Mapping              November 2021


   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  54
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  54
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  55

1.  Introduction

   This document defines the data escrow structure of depositing .NAME
   Top Level Domain (TLD) specific objects as an extension to the
   objects deposited with [RFC9022].  The .NAME TLD specific objects
   include:

   Email Forwarding
      Email Forwarding object as defined in
      https://www.verisign.com/assets/email-forwarding-mapping.pdf

   Defensive Registration
      Defensive Registration object as defined in
      https://www.verisign.com/assets/defensive-registration-mapping.pdf

   NameWatch
      NameWatch object as defined in https://www.verisign.com/assets/
      namewatch-mapping.pdf

2.  Models

   This document supports the two models (XML and CSV) defined in
   [RFC9022] for depositing the .NAME TLD specific objects.

3.  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 RFC 2119 [RFC2119].

   CSV
      Comma-Seperated Value, see [RFC4180].

   DNRD
      Domain Name Registration Data that is based on [RFC9022].

   EPP
      Extensible Provisioning Protocol (EPP), see definition of the
      Extensible Provisioning Protocol in [RFC8499].

   Registrant
      See definition of Registrant in [RFC8499].





Gould                      Expires 19 May 2022                  [Page 3]


Internet-Draft             DNRD .NAME Mapping              November 2021


   Registrar
      See definition of Registrar in [RFC8499].

   Registry
      See definition of Registry in [RFC8499].

   RDE
      See definition of Registry Data Escrow in [RFC9022].

   TLD
      See definition of Top-Level Domain Name in [RFC8499].

   UTC
      See definition of Coordinated Universal Time in [RFC8499].

4.  General Conventions

   XML is case sensitive.  Unless stated otherwise, XML specifications
   and examples provided in this document MUST be interpreted in the
   character case presented in order to develop a conforming
   implementation.

   The following XML namespace prefixes are used in this document based
   on the dependent specifications, but implementations MUST NOT depend
   on this use and instead employ a namespace-aware XML parser and
   serializer to interpret and output the XML documents:

   "rdeEmailFwd"
      XML namespace prefix for "http://www.nic.name/rde/rdeEmailFwd-
      1.0".

   "csvEmailFwd"
      XML namespace prefix for "http://www.nic.name/rde/csvEmailFwd-
      1.0".

   "rdeDefReg"
      XML namespace prefix for "http://www.nic.name/rde/rdeDefReg-1.0".

   "csvDefReg"
      XML namespace prefix for "http://www.nic.name/rde/csvDefReg-1.0".

   "rdeNameWatch"
      XML namespace prefix for "http://www.nic.name/rde/rdeNameWatch-
      1.0".

   "csvNameWatch"
      XML namespace prefix for "http://www.nic.name/rde/csvNameWatch-
      1.0".



Gould                      Expires 19 May 2022                  [Page 4]


Internet-Draft             DNRD .NAME Mapping              November 2021


   The following XML namespace prefixes are used based on the dependent
   specifications, but implementations MUST NOT depend on it and instead
   employ a proper namespace-aware XML parser and serializer to
   interpret and output the XML documents:

   "csvContact"
      XML namespace prefix for "urn:ietf:params:xml:ns:csvContact-1.0"
      in [RFC9022].

   "csvRegistrar"
      XML namespace prefix for "urn:ietf:params:xml:ns:csvRegistrar-1.0"
      in [RFC9022].

   "defReg"
      XML namespace prefix for "http://www.nic.name/epp/defReg-1.0" in
      https://www.verisign.com/assets/defensive-registration-
      mapping.pdf.

   "emailFwd"
      XML namespace prefix for "http://www.nic.name/epp/emailFwd-1.0" in
      https://www.verisign.com/assets/email-forwarding-mapping.pdf.

   "eppcom"
      XML namespace prefix for "urn:ietf:params:xml:ns:eppcom-1.0" in
      [RFC5730].

   "nameWatch"
      XML namespace prefix for "http://www.nic.name/epp/nameWatch-1.0"
      in https://www.verisign.com/assets/namewatch-mapping.pdf.

   "rde"
      XML namespace prefix for "urn:ietf:params:xml:ns:rde-1.0" in
      [RFC8909].

   "rdeCsv"
      XML namespace prefix for "urn:ietf:params:xml:ns:rdeCsv-1.0" in
      [RFC9022].

4.1.  Date and Time

   Numerous fields include values that represent a calendar date/time,
   such as the creation and expiry dates for .NAME objects.  These
   fields SHALL contain timestamps indicating the date and time in UTC
   as specified in [RFC3339], with no offset from the zero meridian.







Gould                      Expires 19 May 2022                  [Page 5]


Internet-Draft             DNRD .NAME Mapping              November 2021


4.2.  CSV common field elements

   Numerous fields reference the CSV common field elements, which are
   defined in [RFC9022].  For example, the <rdeCsv:fRoid> field is
   referenced for each of the .NAME objects.

4.3.  Contact Object

   Numerous fields reference the Contact Object, which is defined in
   [RFC9022].  For example, the <csvContact:fId> field is referenced to
   define the contact identifier for the linked Contact Object.

4.4.  Registrar Object

   Numerous fields reference the Registrar Object, which is defined in
   [RFC9022].  For example, the <csvRegistrar:fGurid> field is
   referenced to define the registrar ID assigned by ICANN.

4.5.  CSV Parent Child Relationship

   The "CSV Parent Child Relationship" convention described in
   [RFC9022], with support for cascade replace and cascade delete,
   applies to the CSV Model in this document.

5.  Object Description

   This section describes the objects supported by this specification:

5.1.  Email Forwarding Object

   The email forwarding object is based on the EPP email forwarding
   mapping specified in https://www.verisign.com/assets/email-
   forwarding-mapping.pdf.  The email forwarding object supports both
   the XML Model and the CSV Model, defined in the Models (Section 2)
   section.  The elements used for both models are defined in the
   following sections.

5.1.1.  XML Model

   There are two elements used in the data escrow of the email
   forwarding objects for the XML model including the
   <rdeEmailFwd:emailFwd>, under the <rde:contents> element, and the
   <rdeEmailFwd:delete> element, under the <rde:deletes> element.








Gould                      Expires 19 May 2022                  [Page 6]


Internet-Draft             DNRD .NAME Mapping              November 2021


5.1.1.1.  <rdeEmailFwd:emailFwd> object

   The <emailFwd> element is based on the EPP email forwarding <info>
   response for an authorized client (see Section 3.1.2. of
   https://www.verisign.com/assets/email-forwarding-mapping.pdf) with
   additional data from an EPP <transfer> Query Response, see
   Section 3.1.3. of https://www.verisign.com/assets/email-forwarding-
   mapping.pdf.

   A <emailFwd> element substitutes for the <abstractEmailFwd> abstract
   element to define a concrete definition of an email forwarding.  The
   <abstractEmailFwd> element can be replaced by other email forwarding
   definitions using the XML schema substitution groups feature.

   The <emailFwd> element contains the following child elements:

   *  A <name> element that contains the fully qualified name of the
      email forwarding object.

   *  A <roid> element that contains the repository object identifier
      assigned to the email forwarding object when it was created.

   *  One or more <status> elements that contain the current status
      descriptors associated with the email forwarding object.

   *  An OPTIONAL <registrant> element that contain the identifier for
      the individual or organizational social information object
      associated as the holder of the email forwarding object.

   *  Zero or more OPTIONAL <contact> elements that contain identifiers
      for the individual or organizational social information objects
      associated with the email forwarding object.

   *  An <fwdTo> element that contains the forward to email address
      associated with the email forwarding object.

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

   *  An OPTIONAL <crRr> element that contains the identifier of the
      registrar that created the email forwarding object.  An OPTIONAL
      "client" attribute is used to specify the client that performed
      the operation.

   *  An OPTIONAL <crDate> element that contains the date and time of
      the email forwarding object creation.





Gould                      Expires 19 May 2022                  [Page 7]


Internet-Draft             DNRD .NAME Mapping              November 2021


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

   *  An OPTIONAL <upRr> element that contains the identifier of the
      registrar that last updated the email forwarding object.  This
      element MUST NOT be present if the email forwarding object has
      never been modified.  An OPTIONAL "client" attribute is used to
      specify the client that performed the operation.

   *  An OPTIONAL <upDate> element that contains the date and time of
      the most recent email forwarding object modification.  This
      element MUST NOT be present if the email forwarding object has
      never been modified.

   *  An OPTIONAL <trDate> element that contains the date and time of
      the most recent successful transfer of the email forwarding
      object.  This element MUST NOT be present if the email forwarding
      object has never been transferred.

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

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

      -  A <reRr> element that contains the identifier of the registrar
         that requested the email forwarding object transfer.  An
         OPTIONAL "client" attribute is used to specify the client that
         performed the operation.

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

      -  An <acRr> 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 OPTIONAL "client" attribute is used to
         specify the client that performed the operation.

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



Gould                      Expires 19 May 2022                  [Page 8]


Internet-Draft             DNRD .NAME Mapping              November 2021


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

   Example of an email forwarding object:

   ...
   <rdeEmailFwd:emailFwd>
     <rdeEmailFwd:name>chris@doe.name</rdeEmailFwd:name>
     <rdeEmailFwd:roid>EXAMPLE1_EMAILFWD-VRSN</rdeEmailFwd:roid>
     <rdeEmailFwd:status s="ok" />
     <rdeEmailFwd:registrant>jd1234</rdeEmailFwd:registrant>
     <rdeEmailFwd:contact type="admin">sh8013</rdeEmailFwd:contact>
     <rdeEmailFwd:contact type="tech">sh8013</rdeEmailFwd:contact>
     <rdeEmailFwd:fwdTo>cdoe@example.com</rdeEmailFwd:fwdTo>
     <rdeEmailFwd:clID>RegistrarX</rdeEmailFwd:clID>
     <rdeEmailFwd:crRr client="cdoe">RegistrarX</rdeEmailFwd:crRr>
     <rdeEmailFwd:crDate>1999-04-03T22:00:00.0Z</rdeEmailFwd:crDate>
     <rdeEmailFwd:exDate>2021-04-03T22:00:00.0Z</rdeEmailFwd:exDate>
     <rdeEmailFwd:trnData>
       <rdeEmailFwd:trStatus>pending</rdeEmailFwd:trStatus>
       <rdeEmailFwd:reRr>registrarY</rdeEmailFwd:reRr>
       <rdeEmailFwd:reDate>2020-03-03T22:00:00.0Z</rdeEmailFwd:reDate>
       <rdeEmailFwd:acRr>RegistrarX</rdeEmailFwd:acRr>
       <rdeEmailFwd:acDate>2020-03-08T22:00:00.0Z</rdeEmailFwd:acDate>
       <rdeEmailFwd:exDate>2022-04-03T22:00:00.0Z</rdeEmailFwd:exDate>
     </rdeEmailFwd:trnData>
   </rdeEmailFwd:emailFwd>
   ...

5.1.1.2.  <rdeEmailFwd:delete> object

   The <rdeEmailFwd:delete> element contains the fully qualified email
   forwarding object that was deleted and purged.

   Example of <rdeEmailFwd:delete> object:

   ...
   <rde:deletes>
     ...
     <rdeEmailFwd:delete>
       <rdeEmailFwd:name>chris@doe.name</rdeEmailFwd:name>
       <rdeEmailFwd:name>kris@doe.name</rdeEmailFwd:name>
     </rdeEmailFwd:delete>
     ...
   </rde:deletes>
   ...




Gould                      Expires 19 May 2022                  [Page 9]


Internet-Draft             DNRD .NAME Mapping              November 2021


5.1.2.  CSV Model

   For the CSV Model of the email forwarding object, the
   <csvEmailFwd:contents> child element of the <rde:contents> element is
   used to hold the new or updated email forwarding objects for the
   deposit.  The <csvEmailFwd:deletes> child element of the
   <rde:deletes> element is used to hold the deleted or purged email
   forwarding objects for the deposit.  Both the <csvEmailFwd:contents>
   and <csvEmailFwd:deletes> elements contain one or more <rdeCsv:csv>
   elements with a set of named CSV file definitions using the
   <rdeCsv:csv> "name" attribute.

   Differential and incremental deposits are based on changes to the
   email forwarding objects.  The updated email forwarding object data
   under the <csvEmailFwd:contents> element is a cascade replace
   (Section 4.5) using all of the email forwarding CSV files starting
   with the parent "emailFwd" CSV File Definition (Section 5.1.2.1.1).
   The child CSV file definitions include a <csvEmailFwd:fName
   parent="true"> field.  All the child CSV file definition data for the
   email forwarding objects in the parent "emailFwd" CSV File Definition
   (Section 5.1.2.1.1) MUST first be deleted and then set using the data
   in the child CSV files.  The deleted email forwarding object data
   under the <csvEmailFwd:deletes> element is a cascade delete
   (Section 4.5) starting from the "emailFwd" Deletes CSV File
   Definition (Section 5.1.2.2.1).

5.1.2.1.  <csvEmailFwd:contents>

   The <csvEmailFwd:contents> is used to hold the new or updated email
   forwarding object information for the deposit.  The
   <csvEmailFwd:contents> is split into separate CSV file definitions
   using named <rdeCsv:csv> elements with the "name" attribute.  The
   following sections include the supported email forwarding CSV file
   definitions:

5.1.2.1.1.  "emailFwd" CSV File Definition

   The "emailFwd" CSV File Definition defines the fields and CSV file
   references used for the parent email forwarding object records.  All
   the other email forwarding CSV file definitions are child CSV files
   based on the inclusion of the <csvEmailFwd:fName parent="true">
   field.

   The following "csvEmailFwd" field elements MUST be used in the
   "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:

   <csvEmailFwd:fName>  Email forwarding name field that contains the




Gould                      Expires 19 May 2022                 [Page 10]


Internet-Draft             DNRD .NAME Mapping              November 2021


      fully qualified name of the email forwarding object with
      type="emailFwd:emailAddrType" and isRequired="true".

   <csvEmailFwd:fFwdTo>  Email forwarding forward to field that contains
      the forward to email address associated with the email forwarding
      object with type="emailFwd:emailAddrType" and isRequired="true".

   The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the
   "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fRoid>  Registry Object IDentifier (ROID) for the email
      forwarding object with isRequired="true".

   <rdeCsv:fClID> or <csvRegistrar:fGurid>  A choice of:

      <rdeCsv:fClID>  Identifier of the sponsoring client with
         isRequired="true".

      <csvRegistrar:fGurid>  Contains the ID assigned by ICANN with
         type="positiveInteger".  The attribute "isRequired" MUST equal
         "true".

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MAY be used in the "emailFwd" <rdeCsv:csv>
   <rdeCsv:fields> element:

   <rdeCsv:fCrRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that created the email forwarding object.

   <rdeCsv:fCrID>  Identifier of the client that created the email
      forwarding object.

   <rdeCsv:fUpRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that updated the email forwarding object.

   <rdeCsv:fUpID>  Identifier of the client that last updated the email
      forwarding object.

   <rdeCsv:fRegistrant>  Registrant contact identifier for the email
      forwarding object.

   <rdeCsv:fCrDate>  Created date and time of the email forwarding
      object.

   <rdeCsv:fUpDate>  Date and time of the last update to the email
      forwarding object.

   <rdeCsv:fExDate>  Expiration date and time for the email forwarding



Gould                      Expires 19 May 2022                 [Page 11]


Internet-Draft             DNRD .NAME Mapping              November 2021


      object.

   <rdeCsv:fTrDate>  Date and time of the last successful transfer for
      the email forwarding object.

   Example of a "emailFwd" <csvEmailFwd:contents> <rdeCsv:csv> element.

   ...
   <csvEmailFwd:contents>
   ...
     <rdeCsv:csv name="emailFwd" sep=",">
       <rdeCsv:fields>
         <csvEmailFwd:fName/>
         <rdeCsv:fRoid/>
         <rdeCsv:fRegistrant/>
         <csvEmailFwd:fFwdTo/>
         <rdeCsv:fClID/>
         <rdeCsv:fCrRr/>
         <rdeCsv:fCrID/>
         <rdeCsv:fCrDate/>
         <rdeCsv:fUpRr/>
         <rdeCsv:fUpID/>
         <rdeCsv:fUpDate/>
         <rdeCsv:fExDate/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="F72A19A8">
           emailFwd-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvEmailFwd:contents>
   ...

   Example of the corresponding emailFwd-YYYYMMDD.csv file.  The file
   contains one record.

   chris@doe.name,EXAMPLE1_EMAILFWD-VRSN,jd1234,cdoe@example.com,
   RegistrarX,RegistrarX,cdoe,1999-04-03T22:00:00.0Z,,,,
   2021-04-03T22:00:00.0Z

5.1.2.1.2.  "emailFwdContacts" CSV File Definition

   The "emailFwdContacts" CSV File Definition defines the fields and CSV
   file references used for the email forwarding object link records to
   contact objects, as described in Contact Object (Section 4.3).



Gould                      Expires 19 May 2022                 [Page 12]


Internet-Draft             DNRD .NAME Mapping              November 2021


   The following "csvEmailFwd" field elements, defined for the
   "emailFwd" CSV File Definition (Section 5.1.2.1.1), MUST be used in
   the "emailFwdContacts" <rdeCsv:csv> <rdeCsv:fields> element:

   <csvEmailFwd:fName>  The name of the email forwarding object that is
      linked to the contact object with isRequired="true".

   <csvEmailFwd:fContactType>  The contact type for the contact object
      link with type="emailFwd:contactAttrType" and isRequired="true".
      The supported contact type values include "admin" for the
      administration contact, "billing" for the billing contact, and
      "tech" for the technical contact.

   The following "csvContact" fields, defined for the "contact" CSV File
   Definition (Section 4.3), MUST be used in the "emailFwdContacts"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <csvContact:fId>  The server-unique contact identifier with
      isRequired="true".

   Example of a "emailFwdContacts" <csvEmailFwd:contents> <rdeCsv:csv>
   element.

   ...
   <csvEmailFwd:contents>
   ...
     <rdeCsv:csv name="emailFwdContacts" sep=",">
       <rdeCsv:fields>
         <csvEmailFwd:fName parent="true"/>
         <csvContact:fId/>
         <csvEmailFwd:fContactType/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="B3FBC311">
           emailFwdContacts-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvEmailFwd:contents>
   ...

   Example of the corresponding emailFwdContacts-YYYYMMDD.csv file.  The
   file contains an admin and tech contact for the email forwarding
   object chris@doe.name.





Gould                      Expires 19 May 2022                 [Page 13]


Internet-Draft             DNRD .NAME Mapping              November 2021


   chris@doe.name,sh8013,admin
   chris@doe.name,sh8013,tech

5.1.2.1.3.  "emailFwdStatuses" CSV File Definition

   The "emailFwdStatuses" CSV File Definition defines the fields and CSV
   file references used for the email forwarding object statuses.

   The following "csvEmailFwd" fields, defined for the "emailFwd" CSV
   File Definition (Section 5.1.2.1.1), MUST be used in the
   "emailFwdStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

   <csvEmailFwd:fName>  Email forwarding name field that contains the
      fully qualified name of the email forwarding object with
      type="emailFwd:emailAddrType" and isRequired="true".

   <csvEmailFwd:fStatus>  The status of the email forwarding with
      type="emailFwd:statusValueType" and isRequired="true".

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MAY be used in the "emailFwdStatuses"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fStatusDescription>  Email forwarding object status
      description which is free-form text describing the rationale for
      the status.

   <rdeCsv:fLang>  Language of the <rdeCsv:fStatusDescription> field.

   Example of a "emailFwdStatuses" <csvEmailFwd:contents> <rdeCsv:csv>
   element.




















Gould                      Expires 19 May 2022                 [Page 14]


Internet-Draft             DNRD .NAME Mapping              November 2021


   ...
   <csvEmailFwd:contents>
   ...
     <rdeCsv:csv name="emailFwdStatuses" sep=",">
       <rdeCsv:fields>
         <csvEmailFwd:fName parent="true"/>
         <csvEmailFwd:fStatus/>
         <rdeCsv:fStatusDescription/>
         <rdeCsv:fLang/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="A7A59EB0">
           emailFwdStatuses-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvEmailFwd:contents>
   ...

   Example of the corresponding emailFwdStatuses-YYYYMMDD.csv file.  The
   file contains the statuses for the email forwarding object
   chris@doe.name.

   chris@doe.name,ok,

5.1.2.1.4.  "emailFwdTransfer" CSV File Definition

   The "emailFwdTransfer" CSV File Definition defines the fields and CSV
   file references used for the email forwarding object pending and
   completed transfer records.  No additional field elements were added
   for use in the "emailFwdTransfer" <rdeCsv:csv> <rdeCsv:fields>
   element.

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MUST be used in the "emailFwdTransfer"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fTrStatus>  State of the most recent transfer request with
      isRequired="true".

   <rdeCsv:fReRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that requested the transfer with isRequired="true".

   <rdeCsv:fReDate>  Date and time that the transfer was requested with
      isRequired="true".




Gould                      Expires 19 May 2022                 [Page 15]


Internet-Draft             DNRD .NAME Mapping              November 2021


   <rdeCsv:fAcRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that should take or took action with
      isRequired="true".

   <rdeCsv:fAcDate>  Date and time that the transfer action should be
      taken or has been taken with isRequired="true".

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MAY be used in the "emailFwdTransfer"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fExDate>  Expiration date if the transfer command caused or
      causes a change in the validity period.

   <rdeCsv:fReID>  Identifier of the client that requested the transfer.

   <rdeCsv:fAcID>  Identifier of the client that should take or took
      action for transfer.

   The following "csvEmailFwd" fields, defined for the "emailFwd" CSV
   File Definition (Section 5.1.2.1.1), MUST be used in the
   "emailFwdTransfer" <rdeCsv:csv> <rdeCsv:fields> element:

   <csvEmailFwd:fName>  The name of the email forwarding object with
      isRequired="true".

   Example of a "emailFwdTransfer" <csvEmailFwd:contents> <rdeCsv:csv>
   element.























Gould                      Expires 19 May 2022                 [Page 16]


Internet-Draft             DNRD .NAME Mapping              November 2021


   ...
   <csvEmailFwd:contents>
   ...
     <rdeCsv:csv name="emailFwdTransfer" sep=",">
       <rdeCsv:fields>
         <csvEmailFwd:fName parent="true"/>
         <rdeCsv:fTrStatus/>
         <rdeCsv:fReRr/>
         <rdeCsv:fReID/>
         <rdeCsv:fReDate/>
         <rdeCsv:fAcRr/>
         <rdeCsv:fAcID/>
         <rdeCsv:fAcDate/>
         <rdeCsv:fExDate/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="C71A9998">
           emailFwdTransfer-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvEmailFwd:contents>
   ...

   Example of the corresponding emailFwdTransfer-YYYYMMDD.csv file.  The
   file contains one email forwarding transfer record with a pending
   status.

   chris@doe.name,pending,registrarY,clientX,2020-03-03T22:00:00.0Z,
   RegistrarX,,2020-03-08T22:00:00.0Z,2022-04-03T22:00:00.0Z

5.1.2.2.  <csvEmailFwd:deletes>

   The <csvEmailFwd:deletes> is used to hold the deleted email
   forwarding objects in a differential or incremental deposit.  All the
   email forwarding object data is deleted as part of a cascade delete
   (Section 4.5).  The <csvEmailFwd:deletes> is split into separate CSV
   file definitions using named <rdeCsv:csv> elements with the "name"
   attribute.  The following section defines the supported email
   forwarding deletes CSV file definition.

5.1.2.2.1.  "emailFwd" Deletes CSV File Definition

   The following "csvEmailFwd" field elements MUST be used in the
   deletes "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:




Gould                      Expires 19 May 2022                 [Page 17]


Internet-Draft             DNRD .NAME Mapping              November 2021


   <csvEmailFwd:fName>  The name of the email forwarding object with
      isRequired="true".

   Example of a "emailFwd" <csvEmailFwd:deletes> <rdeCsv:csv> element:

   ...
   <rde:deletes>
   ...
     <csvEmailFwd:deletes>
       <rdeCsv:csv name="emailFwd">
         <rdeCsv:fields>
           <csvEmailFwd:fName/>
         </rdeCsv:fields>
         <rdeCsv:files>
           <rdeCsv:file
             cksum="6B23C283">
             emailfwd-delete-YYYYMMDD.csv
           </rdeCsv:file>
         </rdeCsv:files>
       </rdeCsv:csv>
     </csvEmailFwd:deletes>
   ...
   </rde:deletes>
   ...

   Example of the corresponding emailfwd-delete-YYYYMMDD.csv file.  The
   file contains two email forwarding records.

   chris@doe.name
   kris@doe.name

5.2.  Defensive Registration Object

   The defensive registration object is based on the EPP defensive
   registration mapping specified in https://www.verisign.com/assets/
   defensive-registration-mapping.pdf.  The defensive registration
   object supports both the XML Model and the CSV Model, defined in the
   Models (Section 2) section.  The elements used for both models are
   defined in the following sections.  There are two levels of defensive
   registration objects: Standard Defensive Registration and Premium
   Defensive Registration.

5.2.1.  XML Model

   There are two elements used in the data escrow of the defensive
   registration objects for the XML model including the
   <rdeDefReg:defReg>, under the <rde:contents> element, and the
   <rdeDefReg:delete> element, under the <rde:deletes> element.



Gould                      Expires 19 May 2022                 [Page 18]


Internet-Draft             DNRD .NAME Mapping              November 2021


5.2.1.1.  <rdeDefReg:defReg> object

   The <defReg> element is based on the EPP defensive registration
   <info> response for an authorized client (see Section 3.1.2. of
   https://www.verisign.com/assets/defensive-registration-mapping.pdf)
   with additional data from an EPP <transfer> Query Response, see
   Section 3.1.3. of https://www.verisign.com/assets/defensive-
   registration-mapping.pdf.

   A <defReg> element substitutes for the <abstractDefReg> abstract
   element to define a concrete definition of a defensive registration.
   The <abstractDefReg> element can be replaced by other defensive
   registration definitions using the XML schema substitution groups
   feature.

   The <defReg> element contains the following child elements:

   *  A <roid> element that contains the repository object identifier
      assigned to the defensive registration object when it was created.

   *  A <name> element that contains the name of the defensive
      registration object with the "level" attribute of "standard" for a
      Standard Defensive Registration or "premium" for a Premium
      Defensive Registration.

   *  An OPTIONAL <registrant> element that contain the identifier for
      the individual or organizational social information object
      associated as the holder of the defensive registration object.

   *  An OPTIONAL <tm> element that contain the Trademark Identifier
      (ID) associated with the defensive registration.

   *  An OPTIONAL <tmCountry> element that contain the Country which
      issued the Trademark associated with the defensive registration.

   *  An OPTIONAL <tmDate> element that contain the date when the
      Trademark was issued.

   *  An OPTIONAL <adminContact> element that contain the identifier for
      the administrator associated with the defensive registration
      object.

   *  One or more <status> elements that contain the current status
      descriptors associated with the defensive registration object.

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




Gould                      Expires 19 May 2022                 [Page 19]


Internet-Draft             DNRD .NAME Mapping              November 2021


   *  An OPTIONAL <crRr> element that contains the identifier of the
      registrar that created the defensive registration object.  An
      OPTIONAL "client" attribute is used to specify the client that
      performed the operation.

   *  An OPTIONAL <crDate> element that contains the date and time of
      the defensive registration object creation.

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

   *  An OPTIONAL <upRr> element that contains the identifier of the
      registrar that last updated the defensive registration object.
      This element MUST NOT be present if the defensive registration has
      never been modified.  An OPTIONAL "client" attribute is used to
      specify the client that performed the operation.

   *  An OPTIONAL <upDate> element that contains the date and time of
      the most recent defensive registration object modification.  This
      element MUST NOT be present if the defensive registration object
      has never been modified.

   *  An OPTIONAL <trDate> element that contains the date and time of
      the most recent successful transfer of the defensive registration
      object.  This element MUST NOT be present if the defensive
      registration object has never been transferred.

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

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

      -  A <reRr> element that contains the identifier of the registrar
         that requested the defensive registration object transfer.  An
         OPTIONAL "client" attribute is used to specify the client that
         performed the operation.

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







Gould                      Expires 19 May 2022                 [Page 20]


Internet-Draft             DNRD .NAME Mapping              November 2021


      -  An <acRr> 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 OPTIONAL "client" attribute is used to
         specify the client that performed the operation.

      -  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 OPTIONAL <exDate> element that contains the end of the
         defensive registration object's validity period (expiry date)
         if the transfer caused or causes a change in the validity
         period.

   Example of a defensive registration object:

   ...
   <rdeDefReg:defReg>
     <rdeDefReg:roid>EXAMPLE3_DEFREG-REP</rdeDefReg:roid>
     <rdeDefReg:name level="premium">doe</rdeDefReg:name>
     <rdeDefReg:registrant>jd1234</rdeDefReg:registrant>
     <rdeDefReg:tm>XYZ-123</rdeDefReg:tm>
     <rdeDefReg:tmCountry>US</rdeDefReg:tmCountry>
     <rdeDefReg:tmDate>1990-04-03</rdeDefReg:tmDate>
     <rdeDefReg:adminContact>sh8013</rdeDefReg:adminContact>
     <rdeDefReg:status s="ok"/>
     <rdeDefReg:clID>RegistrarX</rdeDefReg:clID>
     <rdeDefReg:crRr client="cdoe">RegistrarX</rdeDefReg:crRr>
     <rdeDefReg:crDate>1999-04-03T22:00:00.0Z</rdeDefReg:crDate>
     <rdeDefReg:exDate>2000-04-03T22:00:00.0Z</rdeDefReg:exDate>
   </rdeDefReg:defReg>
   ...

5.2.1.2.  <rdeDefReg:delete> object

   The <rdeDefReg:delete> element contains the defensive registration
   repository object identifier that was deleted and purged.

   Example of <rdeDefReg:delete> object:








Gould                      Expires 19 May 2022                 [Page 21]


Internet-Draft             DNRD .NAME Mapping              November 2021


   ...
   <rde:deletes>
     ...
     <rdeDefReg:delete>
       <rdeDefReg:roid>EXAMPLE1_DEFREG-REP
       </rdeDefReg:roid>
       <rdeDefReg:roid>EXAMPLE2_DEFREG-REP
       </rdeDefReg:roid>
     </rdeDefReg:delete>
     ...
   </rde:deletes>
   ...

5.2.2.  CSV Model

   For the CSV Model of the defensive registration object, the
   <csvDefReg:contents> child element of the <rde:contents> element is
   used to hold the new or updated defensive registration objects for
   the deposit.  The <csvDefReg:deletes> child element of the
   <rde:deletes> element is used to hold the deleted or purged defensive
   registration objects for the deposit.  Both the <csvDefReg:contents>
   and <csvDefReg:deletes> elements contain one or more <rdeCsv:csv>
   elements with a set of named CSV file definitions using the
   <rdeCsv:csv> "name" attribute.

   Differential and incremental deposits are based on changes to the
   defensive registration objects.  The updated defensive registration
   object data under the <csvDefReg:contents> element is a cascade
   replace (Section 4.5) using all of the defensive registration CSV
   files starting with the parent "defReg" CSV File Definition
   (Section 5.2.2.1.1).  The child CSV file definitions include a
   <rdeCsv:fRoid parent="true"> field.  All the child CSV file
   definition data for the defensive registration objects in the parent
   "defReg" CSV File Definition (Section 5.2.2.1.1) MUST first be
   deleted and then set using the data in the child CSV files.  The
   deleted defensive registration object data under the
   <csvDefReg:deletes> element is a cascade delete (Section 4.5)
   starting from the "defReg" Deletes CSV File Definition
   (Section 5.2.2.2.1).

5.2.2.1.  <csvDefReg:contents>

   The <csvDefReg:contents> is used to hold the new or updated defensive
   registration object information for the deposit.  The
   <csvDefReg:contents> is split into separate CSV file definitions
   using named <rdeCsv:csv> elements with the "name" attribute.  The
   following sections include the supported defensive registration CSV
   file definitions:



Gould                      Expires 19 May 2022                 [Page 22]


Internet-Draft             DNRD .NAME Mapping              November 2021


5.2.2.1.1.  "defReg" CSV File Definition

   The "defReg" CSV File Definition defines the fields and CSV file
   references used for the parent defensive registration object records.
   All the other defensive registration CSV file definitions are child
   CSV files based on the inclusion of the <rdeCsv:fRoid parent="true">
   field.

   The following "csvDefReg" field elements MUST be used in the "defReg"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <csvDefReg:fName>  Defensive registration name field for the
      defensive registration object with type="defReg:nameType" and
      isRequired="true".

   <csvDefReg:fLevel>  Defensive registration level to identify it as a
      Standard Defensive Registration ("standard") or a Premium
      Defensive Registration ("premium") with type="defReg:levelType"
      and isRequired="true".

   The following "csvDefReg" field elements MAY be used in the "defReg"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <csvDefReg:fTm>  Trademark Identifier (ID) associated with the
      defensive registration with type="defReg:tmType".

   <csvDefReg:fTmCountry>  Country which issued the Trademark associated
      with the defensive registration with type="defReg:ccType".

   <csvDefReg:fTmDate>  Date when the Trademark associated with the
      defensive registration was issued with type="date".

   <csvDefReg:fAdminContact>  Administrator contact identifier for the
      defensive registration object with type="eppcom:clIDType".

   The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the
   "defReg" <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fRoid>  Registry Object IDentifier (ROID) for the defensive
      registration object with isRequired="true".

   <rdeCsv:fClID> or <csvRegistrar:fGurid>  A choice of:

      <rdeCsv:fClID>  Identifier of the sponsoring client with
         isRequired="true".

      <csvRegistrar:fGurid>  Contains the ID assigned by ICANN with




Gould                      Expires 19 May 2022                 [Page 23]


Internet-Draft             DNRD .NAME Mapping              November 2021


         type="positiveInteger".  The attribute "isRequired" MUST equal
         "true".

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MAY be used in the "defReg" <rdeCsv:csv>
   <rdeCsv:fields> element:

   <rdeCsv:fCrRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that created the object.

   <rdeCsv:fCrID>  Identifier of the client that created the defensive
      registration object.

   <rdeCsv:fUpRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that updated the object.

   <rdeCsv:fUpID>  Identifier of the client that last updated the
      defensive registration object.

   <rdeCsv:fRegistrant>  Registrant contact identifier for the defensive
      registration object.

   <rdeCsv:fCrDate>  Created date and time of the defensive registration
      object.

   <rdeCsv:fUpDate>  Date and time of the last update to the defensive
      registration object.

   <rdeCsv:fExDate>  Expiration date and time for the defensive
      registration object.

   <rdeCsv:fTrDate>  Date and time of the last successful transfer for
      the defensive registration object.

   Example of a "defReg" <csvDefReg:contents> <rdeCsv:csv> element.
















Gould                      Expires 19 May 2022                 [Page 24]


Internet-Draft             DNRD .NAME Mapping              November 2021


   ...
   <csvDefReg:contents>
   ...
     <rdeCsv:csv name="defReg" sep=",">
       <rdeCsv:fields>
         <rdeCsv:fRoid/>
         <csvDefReg:fName/>
         <csvDefReg:fLevel/>
         <rdeCsv:fRegistrant/>
         <csvDefReg:fTm/>
         <csvDefReg:fTmCountry/>
         <csvDefReg:fTmDate/>
         <csvDefReg:fAdminContact/>
         <rdeCsv:fClID/>
         <rdeCsv:fCrRr/>
         <rdeCsv:fCrID/>
         <rdeCsv:fCrDate/>
         <rdeCsv:fUpRr/>
         <rdeCsv:fUpID/>
         <rdeCsv:fUpDate/>
         <rdeCsv:fExDate/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="3019A23F">
           defReg-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvDefReg:contents>
   ...

   Example of the corresponding defReg-YYYYMMDD.csv file.  The file
   contains one record.

   EXAMPLE1_DEFREG-REP,doe,premium,jd1234,XYZ-123,US,1990-04-03,
   sh8013,1999-04-03T22:00:00.0Z,,,,2021-04-03T22:00:00.0Z

5.2.2.1.2.  "defRegStatuses" CSV File Definition

   The "defRegStatuses" CSV File Definition defines the fields and CSV
   file references used for the defensive registration object statuses.

   The following "csvDefReg" fields, defined for the "defReg" CSV File
   Definition (Section 5.2.2.1.1), MUST be used in the "defRegStatuses"
   <rdeCsv:csv> <rdeCsv:fields> element:




Gould                      Expires 19 May 2022                 [Page 25]


Internet-Draft             DNRD .NAME Mapping              November 2021


   <csvDefReg:fStatus>  The status of the defensive registration with
      type="defReg:statusValueType" and isRequired="true".

   The following "rdeCsv" fields, defined for the CSV common field
   elements (Section 4.2), MUST be used in the "defRegStatuses"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fRoid>  Registry Object IDentifier (ROID) for the defensive
      registration object with isRequired="true".

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MAY be used in the "defRegStatuses"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fStatusDescription>  Defensive registration object status
      description which is free-form text describing the rationale for
      the status.

   <rdeCsv:fLang>  Language of the <rdeCsv:fStatusDescription> field.

   Example of a "defRegStatuses" <csvDefReg:contents> <rdeCsv:csv>
   element.

   ...
   <csvDefReg:contents>
   ...
     <rdeCsv:csv name="defRegStatuses" sep=",">
       <rdeCsv:fields>
         <rdeCsv:fRoid parent="true"/>
         <csvDefReg:fStatus/>
         <rdeCsv:fStatusDescription/>
         <rdeCsv:fLang/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="21D85E27">
           csvDefRegStatuses-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvDefReg:contents>
   ...

   Example of the corresponding defRegStatuses-YYYYMMDD.csv file.  The
   file contains the statuses for the defensive registration object
   EXAMPLE1_DEFREG-REP.




Gould                      Expires 19 May 2022                 [Page 26]


Internet-Draft             DNRD .NAME Mapping              November 2021


   EXAMPLE1_DEFREG-REP,ok,

5.2.2.1.3.  "defRegTransfer" CSV File Definition

   The "defRegTransfer" CSV File Definition defines the fields and CSV
   file references used for the defensive registration object pending
   and completed transfer records.  No additional field elements were
   added for use in the "defRegTransfer" <rdeCsv:csv> <rdeCsv:fields>
   element.

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MUST be used in the "defRegTransfer"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fRoid>  Registry Object IDentifier (ROID) for the defensive
      registration object with isRequired="true".

   <rdeCsv:fTrStatus>  State of the most recent transfer request with
      isRequired="true".

   <rdeCsv:fReRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that requested the transfer with isRequired="true".

   <rdeCsv:fReDate>  Date and time that the transfer was requested with
      isRequired="true".

   <rdeCsv:fAcRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that should take or took action with
      isRequired="true".

   <rdeCsv:fAcDate>  Date and time that the transfer action should be
      taken or has been taken with isRequired="true".

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MAY be used in the "defRegTransfer"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fExDate>  Expiration date if the transfer command caused or
      causes a change in the validity period.

   <rdeCsv:fReID>  Identifier of the client that requested the transfer.

   <rdeCsv:fAcID>  Identifier of the client that should take or took
      action for transfer.

   Example of a "defRegTransfer" <csvDefReg:contents> <rdeCsv:csv>
   element.




Gould                      Expires 19 May 2022                 [Page 27]


Internet-Draft             DNRD .NAME Mapping              November 2021


   ...
   <csvDefReg:contents>
   ...
     <rdeCsv:csv name="defRegTransfer" sep=",">
       <rdeCsv:fields>
         <rdeCsv:fRoid parent="true"/>
         <rdeCsv:fTrStatus/>
         <rdeCsv:fReRr/>
         <rdeCsv:fReID/>
         <rdeCsv:fReDate/>
         <rdeCsv:fAcRr/>
         <rdeCsv:fAcID/>
         <rdeCsv:fAcDate/>
         <rdeCsv:fExDate/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="6303FBAF">
           defRegTransfer-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvDefReg:contents>
   ...

   Example of the corresponding defRegTransfer-YYYYMMDD.csv file.  The
   file contains one defensive registration transfer record with a
   pending status.

   EXAMPLE1_DEFREG-REP,pending,registrarY,clientX,
   2020-03-03T22:00:00.0Z,RegistrarX,,2020-03-08T22:00:00.0Z,
   2022-04-03T22:00:00.0Z

5.2.2.2.  <csvDefReg:deletes>

   The <csvDefReg:deletes> is used to hold the deleted defensive
   registration objects in a differential or incremental deposit.  All
   the defensive registration object data is deleted as part of a
   cascade delete (Section 4.5).  The <csvDefReg:deletes> is split into
   separate CSV file definitions using named <rdeCsv:csv> elements with
   the "name" attribute.  The following section defines the supported
   defensive registration deletes CSV file definition.

5.2.2.2.1.  "defReg" Deletes CSV File Definition

   The following "rdeCsv" field elements MUST be used in the deletes
   "defReg" <rdeCsv:csv> <rdeCsv:fields> element:



Gould                      Expires 19 May 2022                 [Page 28]


Internet-Draft             DNRD .NAME Mapping              November 2021


   <rdeCsv:fRoid>  Registry Object IDentifier (ROID) for the defensive
      registration object with isRequired="true".

   Example of a "defReg" <csvDefReg:deletes> <rdeCsv:csv> element:

   ...
   <rde:deletes>
   ...
     <csvDefReg:deletes>
       <rdeCsv:csv name="defReg">
         <rdeCsv:fields>
           <rdeCsv:fRoid/>
         </rdeCsv:fields>
         <rdeCsv:files>
           <rdeCsv:file
             cksum="B6ED701B">
             defReg-delete-YYYYMMDD.csv
           </rdeCsv:file>
         </rdeCsv:files>
       </rdeCsv:csv>
     </csvDefReg:deletes>
   ...
   </rde:deletes>
   ...

   Example of the corresponding defReg-delete-YYYYMMDD.csv file.  The
   file contains two defensive registration records.

   EXAMPLE2_DEFREG-REP
   EXAMPLE3_DEFREG-REP

5.3.  NameWatch Object

   The NameWatch object is based on the EPP NameWatch mapping specified
   in https://www.verisign.com/assets/namewatch-mapping.pdf.  The
   NameWatch object supports both the XML Model and the CSV Model,
   defined in the Models (Section 2) section.  The elements used for
   both models are defined in the following sections.

5.3.1.  XML Model

   There are two elements used in the data escrow of the NameWatch
   objects for the XML model including the <rdeNameWatch:nameWatch>,
   under the <rde:contents> element, and the <rdeNameWatch:delete>
   element, under the <rde:deletes> element.






Gould                      Expires 19 May 2022                 [Page 29]


Internet-Draft             DNRD .NAME Mapping              November 2021


5.3.1.1.  <rdeNameWatch:nameWatch> object

   The <nameWatch> element is based on the EPP NameWatch <info> response
   for an authorized client (see Section 3.1.2. of
   https://www.verisign.com/assets/namewatch-mapping.pdf) with
   additional data from an EPP <transfer> Query Response, see
   Section 3.1.3. of https://www.verisign.com/assets/namewatch-
   mapping.pdf.

   A <nameWatch> element substitutes for the <abstractNameWatch>
   abstract element to define a concrete definition of a NameWatch.  The
   <abstractNameWatch> element can be replaced by other NameWatch
   definitions using the XML schema substitution groups feature.

   The <nameWatch> element contains the following child elements:

   *  A <roid> element that contains the repository object identifier
      assigned to the NameWatch object when it was created.

   *  A <name> element that contains the name of the NameWatch object.

   *  An OPTIONAL <registrant> element that contain the identifier for
      the individual or organizational social information object
      associated as the holder of the NameWatch object.

   *  An OPTIONAL <rptTo> element that contain the e-mail address to
      receive the NameWatch reports with the REQUIRED "freq" attribute
      whose value indicates the report frequency.  The "freq" attribute
      value MUST be "daily", "weekly", or "monthly".

   *  One or more <status> elements that contain the current status
      descriptors associated with the NameWatch object.

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

   *  An OPTIONAL <crRr> element that contains the identifier of the
      registrar that created the NameWatch object.  An OPTIONAL "client"
      attribute is used to specify the client that performed the
      operation.

   *  An OPTIONAL <crDate> element that contains the date and time of
      the NameWatch object creation.

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




Gould                      Expires 19 May 2022                 [Page 30]


Internet-Draft             DNRD .NAME Mapping              November 2021


   *  An OPTIONAL <upRr> element that contains the identifier of the
      registrar that last updated the NameWatch object.  This element
      MUST NOT be present if the NameWatch has never been modified.  An
      OPTIONAL "client" attribute is used to specify the client that
      performed the operation.

   *  An OPTIONAL <upDate> element that contains the date and time of
      the most recent successful transfer of the NameWatch object.  This
      element MUST NOT be present if the NameWatch object has never been
      modified.

   *  An OPTIONAL <trDate> element that contains the date and time of
      the most recent NameWatch object successful transfer.  This
      element MUST NOT be present if the NameWatch object has never been
      transferred.

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

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

      -  A <reRr> element that contains the identifier of the registrar
         that requested the NameWatch object transfer.  An OPTIONAL
         "client" attribute is used to specify the client that performed
         the operation.

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

      -  An <acRr> 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 OPTIONAL "client" attribute is used to
         specify the client that performed the operation.

      -  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 OPTIONAL <exDate> element that contains the end of the
         NameWatch object's validity period (expiry date) if the
         transfer caused or causes a change in the validity period.



Gould                      Expires 19 May 2022                 [Page 31]


Internet-Draft             DNRD .NAME Mapping              November 2021


   Example of a NameWatch object:

   ...
   <rdeNameWatch:nameWatch>
     <rdeNameWatch:roid>EXAMPLE3_NAMEWATCH-VRSN</rdeNameWatch:roid>
     <rdeNameWatch:name>doe</rdeNameWatch:name>
     <rdeNameWatch:registrant>jd1234</rdeNameWatch:registrant>
     <rdeNameWatch:rptTo freq="weekly">cdoe@example.com
     </rdeNameWatch:rptTo>
     <rdeNameWatch:status s="ok"/>
     <rdeNameWatch:clID>RegistrarX</rdeNameWatch:clID>
     <rdeNameWatch:crRr client="cdoe">RegistrarX</rdeNameWatch:crRr>
     <rdeNameWatch:crDate>1999-04-03T22:00:00.0Z</rdeNameWatch:crDate>
     <rdeNameWatch:exDate>2021-04-03T22:00:00.0Z</rdeNameWatch:exDate>
   </rdeNameWatch:nameWatch>
   ...

5.3.1.2.  <rdeNameWatch:delete> object

   The <rdeNameWatch:delete> element contains the NameWatch repository
   object identifier that was deleted and purged.

   Example of <rdeNameWatch:delete> object:

   ...
   <rde:deletes>
     ...
     <rdeNameWatch:delete>
       <rdeNameWatch:roid>EXAMPLE1_NAMEWATCH-REP
       </rdeNameWatch:roid>
       <rdeNameWatch:roid>EXAMPLE2_NAMEWATCH-REP
       </rdeNameWatch:roid>
     </rdeNameWatch:delete>
     ...
   </rde:deletes>
   ...

5.3.2.  CSV Model

   For the CSV Model of the NameWatch object, the
   <csvNameWatch:contents> child element of the <rde:contents> element
   is used to hold the new or updated NameWatch objects for the deposit.
   The <csvNameWatch:deletes> child element of the <rde:deletes> element
   is used to hold the deleted or purged NameWatch objects for the
   deposit.  Both the <csvNameWatch:contents> and <csvNameWatch:deletes>
   elements contain one or more <rdeCsv:csv> elements with a set of
   named CSV file definitions using the <rdeCsv:csv> "name" attribute.




Gould                      Expires 19 May 2022                 [Page 32]


Internet-Draft             DNRD .NAME Mapping              November 2021


   Differential and incremental deposits are based on changes to the
   NameWatch objects.  The updated NameWatch object data under the
   <csvNameWatch:contents> element is a cascade replace (Section 4.5)
   using all of the NameWatch CSV files starting with the parent
   "nameWatch" CSV File Definition (Section 5.3.2.1.1).  The child CSV
   file definitions include a <rdeCsv:fRoid parent="true"> field.  All
   the child CSV file definition data for the NameWatch objects in the
   parent "nameWatch" CSV File Definition (Section 5.3.2.1.1) MUST first
   be deleted and then set using the data in the child CSV files.  The
   deleted NameWatch object data under the <csvNameWatch:deletes>
   element is a cascade delete (Section 4.5) starting from the
   "nameWatch" Deletes CSV File Definition (Section 5.3.2.2.1).

5.3.2.1.  <csvNameWatch:contents>

   The <csvNameWatch:contents> is used to hold the new or updated
   NameWatch object information for the deposit.  The
   <csvNameWatch:contents> is split into separate CSV file definitions
   using named <rdeCsv:csv> elements with the "name" attribute.  The
   following sections include the supported NameWatch CSV file
   definitions:

5.3.2.1.1.  "nameWatch" CSV File Definition

   The "nameWatch" CSV File Definition defines the fields and CSV file
   references used for the parent NameWatch object records.  All the
   other NameWatch CSV file definitions are child CSV files based on the
   inclusion of the <rdeCsv:fRoid parent="true"> field.

   The following "csvNameWatch" field elements MUST be used in the
   "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:

   <csvNameWatch:fName>  NameWatch name field with
      type="nameWatch:nameType" and isRequired="true".

   The following "csvNameWatch" field elements MAY be used in the
   "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:

   <csvNameWatch:rptTo>  Report to field that contains the e-mail
      address to receive the NameWatch reports with
      type="nameWatch:emailAddrType".

   <csvNameWatch:fRptToFreqType>  Report to frequency for sending of the
      NameWatch reports to the <csvNameWatch:rptTo> e-mail address with
      type="nameWatch:freqType" and the possible values of "daily",
      "weekly", or "monthly".





Gould                      Expires 19 May 2022                 [Page 33]


Internet-Draft             DNRD .NAME Mapping              November 2021


   The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the
   "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fRoid>  Registry Object IDentifier (ROID) for the NameWatch
      object with isRequired="true".

   <rdeCsv:fClID> or <csvRegistrar:fGurid>  A choice of:

      <rdeCsv:fClID>  Identifier of the sponsoring client with
         isRequired="true".

      <csvRegistrar:fGurid>  Contains the ID assigned by ICANN with
         type="positiveInteger".  The attribute "isRequired" MUST equal
         "true".

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MAY be used in the "nameWatch" <rdeCsv:csv>
   <rdeCsv:fields> element:

   <rdeCsv:fCrRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that created the NameWatch object.

   <rdeCsv:fCrID>  Identifier of the client that created the NameWatch
      object.

   <rdeCsv:fUpRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that updated the NameWatch object.

   <rdeCsv:fUpID>  Identifier of the client that last updated the
      NameWatch object.

   <rdeCsv:fRegistrant>  Registrant contact identifier for the NameWatch
      object.

   <rdeCsv:fCrDate>  Created date and time of the NameWatch object.

   <rdeCsv:fUpDate>  Date and time of the last update to the NameWatch
      object.

   <rdeCsv:fExDate>  Expiration date and time for the NameWatch object.

   <rdeCsv:fTrDate>  Date and time of the last successful transfer for
      the NameWatch object.

   Example of a "nameWatch" <csvNameWatch:contents> <rdeCsv:csv>
   element.





Gould                      Expires 19 May 2022                 [Page 34]


Internet-Draft             DNRD .NAME Mapping              November 2021


   ...
   <csvNameWatch:contents>
   ...
     <rdeCsv:csv name="nameWatch" sep=",">
       <rdeCsv:fields>
         <rdeCsv:fRoid/>
         <csvNameWatch:fName/>
         <rdeCsv:fRegistrant/>
         <csvNameWatch:fRptTo/>
         <csvNameWatch:fRptToFreq/>
         <rdeCsv:fClID/>
         <rdeCsv:fCrRr/>
         <rdeCsv:fCrID/>
         <rdeCsv:fCrDate/>
         <rdeCsv:fUpRr/>
         <rdeCsv:fUpID/>
         <rdeCsv:fUpDate/>
         <rdeCsv:fExDate/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="75E2D01F">
           nameWatch-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvNameWatch:contents>
   ...

   Example of the corresponding nameWatch-YYYYMMDD.csv file.  The file
   contains one record.

   EXAMPLE1_NAMEWATCH-REP,doe,jd1234,cdoe@example.com,
   weekly,sh8013,1999-04-03T22:00:00.0Z,,,,2021-04-03T22:00:00.0Z

5.3.2.1.2.  "nameWatchStatuses" CSV File Definition

   The "nameWatchStatuses" CSV File Definition defines the fields and
   CSV file references used for the NameWatch object statuses.

   The following "csvNameWatch" fields, defined for the "nameWatch" CSV
   File Definition (Section 5.3.2.1.1), MUST be used in the
   "nameWatchStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

   <csvNameWatch:fStatus>  The status of the NameWatch with
      type="nameWatch:statusValueType" and isRequired="true".




Gould                      Expires 19 May 2022                 [Page 35]


Internet-Draft             DNRD .NAME Mapping              November 2021


   The following "rdeCsv" fields, defined for the CSV common field
   elements (Section 4.2), MUST be used in the "nameWatchStatuses"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fRoid>  Registry Object IDentifier (ROID) for the NameWatch
      object with isRequired="true".

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MAY be used in the "nameWatchStatuses"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fStatusDescription>  NameWatch object status description
      which is free-form text describing the rationale for the status.

   <rdeCsv:fLang>  Language of the <rdeCsv:fStatusDescription> field.

   Example of a "nameWatchStatuses" <csvNameWatch:contents> <rdeCsv:csv>
   element.

   ...
   <csvNameWatch:contents>
   ...
     <rdeCsv:csv name="nameWatchStatuses" sep=",">
       <rdeCsv:fields>
         <rdeCsv:fRoid parent="true"/>
         <csvNameWatch:fStatus/>
         <rdeCsv:fStatusDescription/>
         <rdeCsv:fLang/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="A2C261DC">
           csvNameWatchStatuses-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvNameWatch:contents>
   ...

   Example of the corresponding nameWatchStatuses-YYYYMMDD.csv file.
   The file contains the statuses for the NameWatch object
   EXAMPLE1_NAMEWATCH-REP.

   EXAMPLE1_NAMEWATCH-REP,ok,






Gould                      Expires 19 May 2022                 [Page 36]


Internet-Draft             DNRD .NAME Mapping              November 2021


5.3.2.1.3.  "nameWatchTransfer" CSV File Definition

   The "nameWatchTransfer" CSV File Definition defines the fields and
   CSV file references used for the NameWatch object pending and
   completed transfer records.  No additional field elements were added
   for use in the "nameWatchTransfer" <rdeCsv:csv> <rdeCsv:fields>
   element.

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MUST be used in the "nameWatchTransfer"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fRoid>  Registry Object IDentifier (ROID) for the NameWatch
      object with isRequired="true".

   <rdeCsv:fTrStatus>  State of the most recent transfer request with
      isRequired="true".

   <rdeCsv:fReRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that requested the transfer with isRequired="true".

   <rdeCsv:fReDate>  Date and time that the transfer was requested with
      isRequired="true".

   <rdeCsv:fAcRr>  Identifier of the registrar, defined in Section 4.4,
      of the client that should take or took action with
      isRequired="true".

   <rdeCsv:fAcDate>  Date and time that the transfer action should be
      taken or has been taken with isRequired="true".

   The following "rdeCsv" fields, defined in section CSV common field
   elements (Section 4.2), MAY be used in the "nameWatchTransfer"
   <rdeCsv:csv> <rdeCsv:fields> element:

   <rdeCsv:fExDate>  Expiration date if the transfer command caused or
      causes a change in the validity period.

   <rdeCsv:fReID>  Identifier of the client that requested the transfer.

   <rdeCsv:fAcID>  Identifier of the client that should take or took
      action for transfer.

   Example of a "nameWatchTransfer" <csvNameWatch:contents> <rdeCsv:csv>
   element.






Gould                      Expires 19 May 2022                 [Page 37]


Internet-Draft             DNRD .NAME Mapping              November 2021


   ...
   <csvNameWatch:contents>
   ...
     <rdeCsv:csv name="nameWatchTransfer" sep=",">
       <rdeCsv:fields>
         <rdeCsv:fRoid parent="true"/>
         <rdeCsv:fTrStatus/>
         <rdeCsv:fReRr/>
         <rdeCsv:fReID/>
         <rdeCsv:fReDate/>
         <rdeCsv:fAcRr/>
         <rdeCsv:fAcID/>
         <rdeCsv:fAcDate/>
         <rdeCsv:fExDate/>
       </rdeCsv:fields>
       <rdeCsv:files>
         <rdeCsv:file
           cksum="FE25CA7B">
           nameWatchTransfer-YYYYMMDD.csv
         </rdeCsv:file>
       </rdeCsv:files>
     </rdeCsv:csv>
   ...
   </csvNameWatch:contents>
   ...

   Example of the corresponding nameWatchTransfer-YYYYMMDD.csv file.
   The file contains one NameWatch transfer record with a pending
   status.

   EXAMPLE1_NAMEWATCH-REP,pending,registrarY,clientX,
   2020-03-03T22:00:00.0Z,RegistrarX,,
   2020-03-08T22:00:00.0Z,2022-04-03T22:00:00.0Z

5.3.2.2.  <csvNameWatch:deletes>

   The <csvNameWatch:deletes> is used to hold the deleted NameWatch
   objects in a differential or incremental deposit.  All the NameWatch
   object data is deleted as part of a cascade delete (Section 4.5).
   The <csvNameWatch:deletes> is split into separate CSV file
   definitions using named <rdeCsv:csv> elements with the "name"
   attribute.  The following section defines the supported NameWatch
   deletes CSV file definition.

5.3.2.2.1.  "nameWatch" Deletes CSV File Definition

   The following "rdeCsv" field elements MUST be used in the deletes
   "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:



Gould                      Expires 19 May 2022                 [Page 38]


Internet-Draft             DNRD .NAME Mapping              November 2021


   <rdeCsv:fRoid>  Registry Object IDentifier (ROID) for the NameWatch
      object with isRequired="true".

   Example of a "nameWatch" <csvNameWatch:deletes> <rdeCsv:csv> element:

   ...
   <rde:deletes>
   ...
     <csvNameWatch:deletes>
       <rdeCsv:csv name="nameWatch">
         <rdeCsv:fields>
           <rdeCsv:fRoid/>
         </rdeCsv:fields>
         <rdeCsv:files>
           <rdeCsv:file
             cksum="6D4BB372">
             nameWatch-delete-YYYYMMDD.csv
           </rdeCsv:file>
         </rdeCsv:files>
       </rdeCsv:csv>
     </csvNameWatch:deletes>
   ...
   </rde:deletes>
   ...

   Example of the corresponding nameWatch-delete-YYYYMMDD.csv file.  The
   file contains two NameWatch records.

   EXAMPLE2_NAMEWATCH-REP
   EXAMPLE3_NAMEWATCH-REP

6.  Formal Syntax

   The formal syntax is specified in XML Schema notation that is a
   complete schema representation suitable for automated valudation.
   The <CODE BEGINS> and the <CODE ENDS> tags are not part of the
   schema; they are used to note the beginning and ending of the schema
   for URI registration purposes.

6.1.  RDE Email Forwarding Object

   <CODE BEGINS>
   <?xml version="1.0" encoding="UTF-8"?>
   <schema
     targetNamespace="http://www.nic.name/rde/rdeEmailFwd-1.0"
     xmlns:rdeEmailFwd=
       "http://www.nic.name/rde/rdeEmailFwd-1.0"
     xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"



Gould                      Expires 19 May 2022                 [Page 39]


Internet-Draft             DNRD .NAME Mapping              November 2021


     xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
     xmlns:emailFwd="http://www.nic.name/epp/emailFwd-1.0"
     xmlns="http://www.w3.org/2001/XMLSchema"
     elementFormDefault="qualified">

     <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
     <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
     <import namespace="http://www.nic.name/epp/emailFwd-1.0"/>


     <annotation>
       <documentation>
         Registry Data Escrow Email Forwarding Data.
       </documentation>
     </annotation>

     <element name="abstractEmailFwd"
       type="rdeEmailFwd:abstractContentType"
       substitutionGroup="rde:content" abstract="true"/>
     <element name="emailFwd"
       substitutionGroup="rdeEmailFwd:abstractEmailFwd"/>
     <element name="delete"
       type="rdeEmailFwd:deleteType"
       substitutionGroup="rde:delete"/>

     <!-- Content Type -->
     <complexType name="abstractContentType">
       <complexContent>
         <extension base="rde:contentType">
           <sequence>
             <element name="name" type="emailFwd:emailAddrType"/>
             <element name="roid" type="eppcom:roidType"/>
             <element name="status" type="emailFwd:statusType"
              minOccurs="0" maxOccurs="11"/>
             <element name="registrant" type="emailFwd:contactType"
              minOccurs="0"/>
             <element name="contact" type="emailFwd:contactType"
              minOccurs="0" maxOccurs="unbounded"/>
             <element name="fwdTo" type="emailFwd:emailAddrType"
              minOccurs="0"/>
             <element name="clID" type="eppcom:clIDType"/>
             <element name="crRr"
               type="rde:rrType"/>
             <element name="crDate" type="dateTime"
              minOccurs="0"/>
              <element name="upRr"
                type="rde:rrType" minOccurs="0"/>
             <element name="upDate" type="dateTime"



Gould                      Expires 19 May 2022                 [Page 40]


Internet-Draft             DNRD .NAME Mapping              November 2021


              minOccurs="0"/>
             <element name="exDate" type="dateTime"
              minOccurs="0"/>
             <element name="trDate" type="dateTime"
              minOccurs="0"/>
             <element name="trnData"
               type="rdeEmailFwd:transferDataType"
               minOccurs="0"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <complexType name="transferDataType">
       <sequence>
         <element name="trStatus"
           type="eppcom:trStatusType"/>
         <element name="reRr"
           type="rde:rrType"/>
         <element name="reDate"
           type="dateTime"/>
         <element name="acRr"
           type="rde:rrType"/>
         <element name="acDate"
           type="dateTime"/>
         <element name="exDate"
           type="dateTime" minOccurs="0"/>
       </sequence>
     </complexType>

     <!-- Delete Type -->
     <complexType name="deleteType">
       <complexContent>
         <extension base="rde:deleteType">
           <sequence>
             <element name="name"
               type="emailFwd:emailAddrType" minOccurs="0"
               maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   </schema>
   <CODE ENDS>

6.2.  CSV Email Forwarding Object




Gould                      Expires 19 May 2022                 [Page 41]


Internet-Draft             DNRD .NAME Mapping              November 2021


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

   <schema targetNamespace="http://www.nic.name/rde/csvEmailFwd-1.0"
          xmlns:csvEmailFwd="http://www.nic.name/rde/csvEmailFwd-1.0"
          xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
          xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
          xmlns:emailFwd="http://www.nic.name/epp/emailFwd-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"/>
     <import namespace="http://www.nic.name/epp/emailFwd-1.0"/>
     <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
     <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>

     <annotation>
      <documentation>
       Email Forwarding Comma-Separated Values (CSV) Object
      </documentation>
     </annotation>

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

     <complexType name="contentType">
      <complexContent>
       <extension base="rde:contentType">
          <sequence>
            <element ref="rdeCsv:csv" maxOccurs="unbounded"/>
          </sequence>
       </extension>
      </complexContent>
     </complexType>

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




Gould                      Expires 19 May 2022                 [Page 42]


Internet-Draft             DNRD .NAME Mapping              November 2021


     <complexType name="deleteType">
      <complexContent>
       <extension base="rde:deleteType">
          <sequence>
            <element ref="rdeCsv:csv" maxOccurs="unbounded"/>
          </sequence>
       </extension>
      </complexContent>
     </complexType>

     <!-- EmailFwd name and fwdTo field -->
     <element name="fName" type="csvEmailFwd:fEmailAddrType"
      substitutionGroup="rdeCsv:field"/>

     <element name="fFwdTo" type="csvEmailFwd:fEmailAddrType"
      substitutionGroup="rdeCsv:field"/>

     <!-- EmailFwd Address type  -->
     <complexType name="fEmailAddrType">
      <complexContent>
        <extension base="rdeCsv:fieldRequiredType">
          <sequence/>
          <attribute name="type" type="token"
            default="emailFwd\:emailAddrType"/>
        </extension>
      </complexContent>
     </complexType>

    <!-- Contact type field -->
    <element name="fContactType" type="csvEmailFwd:fContactsTypeType"
     substitutionGroup="rdeCsv:field"/>
    <complexType name="fContactsTypeType">
     <complexContent>
       <extension base="rdeCsv:fieldOptionalType">
         <sequence/>
         <attribute name="type" type="token"
         default="emailFwd\:contactAttrType"/>
       </extension>
     </complexContent>
    </complexType>

    <!-- EmailFwd status field -->
    <element name="fStatus" type="csvEmailFwd:fStatusType"
     substitutionGroup="rdeCsv:field"/>
    <complexType name="fStatusType">
     <complexContent>
       <extension base="rdeCsv:fieldOptionalType">
         <sequence/>



Gould                      Expires 19 May 2022                 [Page 43]


Internet-Draft             DNRD .NAME Mapping              November 2021


         <attribute name="type" type="token"
           default="emailFwd\:statusValueType"/>
       </extension>
     </complexContent>
    </complexType>

     <!--
     End of schema.
     -->
   </schema>
   <CODE ENDS>

6.3.  RDE Defensive Registration Object

   <CODE BEGINS>
   <?xml version="1.0" encoding="UTF-8"?>
   <schema
     targetNamespace="http://www.nic.name/rde/rdeDefReg-1.0"
     xmlns:rdeDefReg=
       "http://www.nic.name/rde/rdeDefReg-1.0"
     xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
     xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
     xmlns:defReg="http://www.nic.name/epp/defReg-1.0"
     xmlns="http://www.w3.org/2001/XMLSchema"
     elementFormDefault="qualified">

     <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
     <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
     <import namespace="http://www.nic.name/epp/defReg-1.0"/>

     <annotation>
       <documentation>
         Registry Data Escrow Defensive Registration Data.
       </documentation>
     </annotation>

     <element name="abstractDefReg"
       type="rdeDefReg:abstractContentType"
       substitutionGroup="rde:content" abstract="true"/>
     <element name="defReg"
       substitutionGroup="rdeDefReg:abstractDefReg"/>
     <element name="delete"
       type="rdeDefReg:deleteType"
       substitutionGroup="rde:delete"/>

     <!-- Content Type -->
     <complexType name="abstractContentType">
       <complexContent>



Gould                      Expires 19 May 2022                 [Page 44]


Internet-Draft             DNRD .NAME Mapping              November 2021


         <extension base="rde:contentType">
           <sequence>
             <element name="roid" type="eppcom:roidType"/>
             <element name="name" type="defReg:nameType"/>
             <element name="registrant" type="eppcom:clIDType"
              minOccurs="0"/>
             <element name="tm" type="defReg:tmType"
              minOccurs="0"/>
             <element name="tmCountry" type="defReg:ccType"
              minOccurs="0"/>
             <element name="tmDate" type="date"
              minOccurs="0"/>
             <element name="adminContact" type="eppcom:clIDType"
              minOccurs="0"/>
             <element name="status" type="defReg:statusType"
              minOccurs="0" maxOccurs="11"/>
             <element name="clID" type="eppcom:clIDType"/>
             <element name="crRr"
               type="rde:rrType"/>
             <element name="crDate" type="dateTime"
              minOccurs="0"/>
              <element name="upRr"
                type="rde:rrType" minOccurs="0"/>
             <element name="upDate" type="dateTime"
              minOccurs="0"/>
             <element name="exDate" type="dateTime"
              minOccurs="0"/>
             <element name="trDate" type="dateTime"
              minOccurs="0"/>
             <element name="trnData"
               type="rdeDefReg:transferDataType"
               minOccurs="0"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <complexType name="transferDataType">
       <sequence>
         <element name="trStatus"
           type="eppcom:trStatusType"/>
         <element name="reRr"
           type="rde:rrType"/>
         <element name="reDate"
           type="dateTime"/>
         <element name="acRr"
           type="rde:rrType"/>
         <element name="acDate"



Gould                      Expires 19 May 2022                 [Page 45]


Internet-Draft             DNRD .NAME Mapping              November 2021


           type="dateTime"/>
         <element name="exDate"
           type="dateTime" minOccurs="0"/>
       </sequence>
     </complexType>

     <!-- Delete Type -->
     <complexType name="deleteType">
       <complexContent>
         <extension base="rde:deleteType">
           <sequence>
             <element name="roid"
               type="eppcom:roidType" minOccurs="0"
               maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   </schema>
   <CODE ENDS>

6.4.  CSV Defensive Registration Object

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

   <schema targetNamespace="http://www.nic.name/rde/csvDefReg-1.0"
          xmlns:csvDefReg="http://www.nic.name/rde/csvDefReg-1.0"
          xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
          xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
          xmlns:defReg="http://www.nic.name/epp/defReg-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"/>
     <import namespace="http://www.nic.name/epp/defReg-1.0"/>
     <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
     <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>

     <annotation>
      <documentation>
       Defensive Registration Comma-Separated Values (CSV) Object
      </documentation>



Gould                      Expires 19 May 2022                 [Page 46]


Internet-Draft             DNRD .NAME Mapping              November 2021


     </annotation>

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

     <complexType name="contentType">
      <complexContent>
       <extension base="rde:contentType">
          <sequence>
            <element ref="rdeCsv:csv" maxOccurs="unbounded"/>
          </sequence>
       </extension>
      </complexContent>
     </complexType>

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

     <complexType name="deleteType">
      <complexContent>
       <extension base="rde:deleteType">
          <sequence>
            <element ref="rdeCsv:csv" maxOccurs="unbounded"/>
          </sequence>
       </extension>
      </complexContent>
     </complexType>

     <!-- DefReg name field -->
     <element name="fName" type="csvDefReg:fNameType"
      substitutionGroup="rdeCsv:field"/>
     <complexType name="fNameType">
      <complexContent>
        <extension base="rdeCsv:fieldRequiredType">
          <sequence/>
          <attribute name="type" type="token"
            default="defReg\:nameType"/>
        </extension>
      </complexContent>
     </complexType>

     <!-- DefReg level field -->



Gould                      Expires 19 May 2022                 [Page 47]


Internet-Draft             DNRD .NAME Mapping              November 2021


     <element name="fLevel" type="csvDefReg:fLevelType"
      substitutionGroup="rdeCsv:field"/>
      <complexType name="fLevelType">
       <complexContent>
         <extension base="rdeCsv:fieldRequiredType">
           <sequence/>
           <attribute name="type" type="token"
             default="defReg\:levelType"/>
         </extension>
       </complexContent>
      </complexType>

    <!-- DefReg status field -->
    <element name="fStatus" type="csvDefReg:fStatusType"
     substitutionGroup="rdeCsv:field"/>
    <complexType name="fStatusType">
     <complexContent>
       <extension base="rdeCsv:fieldOptionalType">
         <sequence/>
         <attribute name="type" type="token"
           default="defReg\:statusValueType"/>
       </extension>
     </complexContent>
    </complexType>

    <!-- DefReg tm field -->
    <element name="fTm" type="csvDefReg:fTmType"
     substitutionGroup="rdeCsv:field"/>
    <complexType name="fTmType">
     <complexContent>
       <extension base="rdeCsv:fieldOptionalType">
         <sequence/>
         <attribute name="type" type="token"
           default="defReg\:tmType"/>
       </extension>
     </complexContent>
    </complexType>

    <!-- DefReg tmCountry field -->
    <element name="fTmCountry" type="csvDefReg:fTmCountryType"
     substitutionGroup="rdeCsv:field"/>
    <complexType name="fTmCountryType">
     <complexContent>
       <extension base="rdeCsv:fieldOptionalType">
         <sequence/>
         <attribute name="type" type="token"
           default="defReg\:ccType"/>
       </extension>



Gould                      Expires 19 May 2022                 [Page 48]


Internet-Draft             DNRD .NAME Mapping              November 2021


     </complexContent>
    </complexType>

    <!-- DefReg tmDate field -->
    <element name="fTmDate" type="csvDefReg:fTmDateType"
     substitutionGroup="rdeCsv:field"/>
    <complexType name="fTmDateType">
      <complexContent>
        <extension base="rdeCsv:fieldOptionalType">
          <sequence/>
          <attribute name="type" type="token"
            default="date"/>
        </extension>
      </complexContent>
    </complexType>

     <!-- DefReg Admin Contact field -->
     <element name="fAdminContact" type="csvDefReg:fAdminContactType"
       substitutionGroup="rdeCsv:field" />
     <complexType name="fAdminContactType">
       <complexContent>
         <extension base="rdeCsv:fieldOptionalType">
           <sequence />
           <attribute name="type" type="token"
             default="eppcom\:clIDType" />
         </extension>
       </complexContent>
     </complexType>

     <!--
     End of schema.
     -->
   </schema>
   <CODE ENDS>

6.5.  RDE NameWatch Object

   <CODE BEGINS>
   <?xml version="1.0" encoding="UTF-8"?>
   <schema
     targetNamespace="http://www.nic.name/rde/rdeNameWatch-1.0"
     xmlns:rdeNameWatch=
       "http://www.nic.name/rde/rdeNameWatch-1.0"
     xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
     xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
     xmlns:nameWatch="http://www.nic.name/epp/nameWatch-1.0"
     xmlns="http://www.w3.org/2001/XMLSchema"
     elementFormDefault="qualified">



Gould                      Expires 19 May 2022                 [Page 49]


Internet-Draft             DNRD .NAME Mapping              November 2021


     <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
     <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
     <import namespace="http://www.nic.name/epp/nameWatch-1.0"/>

     <annotation>
       <documentation>
         Registry Data Escrow NameWatch Data.
       </documentation>
     </annotation>

     <element name="abstractnameWatch"
       type="rdeNameWatch:abstractContentType"
       substitutionGroup="rde:content" abstract="true"/>
     <element name="nameWatch"
       substitutionGroup="rdeNameWatch:abstractnameWatch"/>
     <element name="delete"
       type="rdeNameWatch:deleteType"
       substitutionGroup="rde:delete"/>

     <!-- Content Type -->
     <complexType name="abstractContentType">
       <complexContent>
         <extension base="rde:contentType">
           <sequence>
             <element name="roid" type="eppcom:roidType"/>
             <element name="name" type="nameWatch:nameType"/>
             <element name="registrant" type="eppcom:clIDType"
              minOccurs="0"/>
             <element name="rptTo" type="nameWatch:rptToType"
              minOccurs="0"/>
             <element name="status" type="nameWatch:statusType"
              minOccurs="0" maxOccurs="11"/>
             <element name="clID" type="eppcom:clIDType"/>
             <element name="crRr"
               type="rde:rrType"/>
             <element name="crDate" type="dateTime"
              minOccurs="0"/>
              <element name="upRr"
                type="rde:rrType" minOccurs="0"/>
             <element name="upDate" type="dateTime"
              minOccurs="0"/>
             <element name="exDate" type="dateTime"
              minOccurs="0"/>
             <element name="trDate" type="dateTime"
              minOccurs="0"/>
             <element name="trnData"
               type="rdeNameWatch:transferDataType"
               minOccurs="0"/>



Gould                      Expires 19 May 2022                 [Page 50]


Internet-Draft             DNRD .NAME Mapping              November 2021


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

     <complexType name="transferDataType">
       <sequence>
         <element name="trStatus"
           type="eppcom:trStatusType"/>
         <element name="reRr"
           type="rde:rrType"/>
         <element name="reDate"
           type="dateTime"/>
         <element name="acRr"
           type="rde:rrType"/>
         <element name="acDate"
           type="dateTime"/>
         <element name="exDate"
           type="dateTime" minOccurs="0"/>
       </sequence>
     </complexType>

     <!-- Delete Type -->
     <complexType name="deleteType">
       <complexContent>
         <extension base="rde:deleteType">
           <sequence>
             <element name="roid"
               type="eppcom:roidType" minOccurs="0"
               maxOccurs="unbounded"/>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

   </schema>
   <CODE ENDS>

6.6.  CSV NameWatch Object

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

   <schema targetNamespace="http://www.nic.name/rde/csvNameWatch-1.0"
          xmlns:csvNameWatch="http://www.nic.name/rde/csvNameWatch-1.0"
          xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
          xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
          xmlns:nameWatch="http://www.nic.name/epp/nameWatch-1.0"



Gould                      Expires 19 May 2022                 [Page 51]


Internet-Draft             DNRD .NAME Mapping              November 2021


          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"
          s/>
     <import namespace="http://www.nic.name/epp/nameWatch-1.0"/>
     <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
     <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>

     <annotation>
      <documentation>
       NameWatch Comma-Separated Values (CSV) Object
      </documentation>
     </annotation>

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

     <complexType name="contentType">
      <complexContent>
       <extension base="rde:contentType">
          <sequence>
            <element ref="rdeCsv:csv" maxOccurs="unbounded"/>
          </sequence>
       </extension>
      </complexContent>
     </complexType>

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

     <complexType name="deleteType">
      <complexContent>
       <extension base="rde:deleteType">
          <sequence>
            <element ref="rdeCsv:csv" maxOccurs="unbounded"/>
          </sequence>
       </extension>



Gould                      Expires 19 May 2022                 [Page 52]


Internet-Draft             DNRD .NAME Mapping              November 2021


      </complexContent>
     </complexType>

     <!-- NameWatch name field -->
     <element name="fName" type="csvNameWatch:fNameType"
      substitutionGroup="rdeCsv:field"/>
     <complexType name="fNameType">
      <complexContent>
        <extension base="rdeCsv:fieldRequiredType">
          <sequence/>
          <attribute name="type" type="token"
            default="nameWatch\:nameType"/>
        </extension>
      </complexContent>
     </complexType>

     <!-- NameWatch rptTo field -->
     <element name="fRptTo" type="csvNameWatch:fRptToType"
      substitutionGroup="rdeCsv:field"/>
      <complexType name="fRptToType">
       <complexContent>
         <extension base="rdeCsv:fieldRequiredType">
           <sequence/>
           <attribute name="type" type="token"
             default="nameWatch\:emailAddrType"/>
         </extension>
       </complexContent>
      </complexType>

      <!-- NameWatch rptToFreq field -->
      <element name="fRptToFreq" type="csvNameWatch:fRptToFreqType"
       substitutionGroup="rdeCsv:field"/>
       <complexType name="fRptToFreqType">
        <complexContent>
          <extension base="rdeCsv:fieldRequiredType">
            <sequence/>
            <attribute name="type" type="token"
              default="nameWatch\:freqType"/>
          </extension>
        </complexContent>
       </complexType>

    <!-- NameWatch status field -->
    <element name="fStatus" type="csvNameWatch:fStatusType"
     substitutionGroup="rdeCsv:field"/>
    <complexType name="fStatusType">
     <complexContent>
       <extension base="rdeCsv:fieldOptionalType">



Gould                      Expires 19 May 2022                 [Page 53]


Internet-Draft             DNRD .NAME Mapping              November 2021


         <sequence/>
         <attribute name="type" type="token"
           default="nameWatch\:statusValueType"/>
       </extension>
     </complexContent>
    </complexType>

     <!--
     End of schema.
     -->
   </schema>
   <CODE ENDS>

7.  IANA Considerations

   No actions

8.  Security Considerations

   The extensions described in this document do not provide any security
   services beyond those described by [RFC8909] and [RFC9022].  The
   security considerations described in these specifications apply to
   this specification.

9.  Privacy Considerations

   This specification defines a format that may be used to escrow
   personal data.  The process of data escrow is governed by a legal
   document agreed by the parties, and such legal document must regulate
   the particularities regarding the protection of personal data.

10.  Acknowledgments

   The authors wish to thank the following persons for their feedback
   and suggestions: Scott Hollenbeck and Rick Wilhelm.

11.  References

11.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC3339]  Klyne, G. and C. Newman, "Date and Time on the Internet:
              Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
              <https://www.rfc-editor.org/info/rfc3339>.



Gould                      Expires 19 May 2022                 [Page 54]


Internet-Draft             DNRD .NAME Mapping              November 2021


   [RFC4180]  Shafranovich, Y., "Common Format and MIME Type for Comma-
              Separated Values (CSV) Files", RFC 4180,
              DOI 10.17487/RFC4180, October 2005,
              <https://www.rfc-editor.org/info/rfc4180>.

   [RFC5730]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
              STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
              <https://www.rfc-editor.org/info/rfc5730>.

   [RFC8499]  Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
              Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
              January 2019, <https://www.rfc-editor.org/info/rfc8499>.

   [RFC8909]  Lozano, G., "Registry Data Escrow Specification",
              RFC 8909, DOI 10.17487/RFC8909, November 2020,
              <https://www.rfc-editor.org/info/rfc8909>.

   [RFC9022]  Lozano, G., Gould, J., and C. Thippeswamy, "Domain Name
              Registration Data (DNRD) Objects Mapping", RFC 9022,
              DOI 10.17487/RFC9022, May 2021,
              <https://www.rfc-editor.org/info/rfc9022>.

Author's Address

   James Gould
   VeriSign, Inc.
   12061 Bluemont Way
   Reston, VA 20190
   United States of America

   Email: jgould@verisign.com
   URI:   http://www.verisign.com



















Gould                      Expires 19 May 2022                 [Page 55]