Network Working Group J.G. Gould Internet-Draft VeriSign, Inc. Intended status: Informational 30 March 2023 Expires: 1 October 2023 Domain Name Registration Data (DNRD) .NAME Object Mapping draft-gould-dnrd-name-mapping-01 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 1 October 2023. Copyright Notice Copyright (c) 2023 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Gould Expires 1 October 2023 [Page 1] Internet-Draft DNRD .NAME Mapping March 2023 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. object . . . . . . . . . . 7 5.1.1.2. object . . . . . . . . . . . 9 5.1.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . 10 5.1.2.1. . . . . . . . . . . . . . 10 5.1.2.2. . . . . . . . . . . . . . . 17 5.2. Defensive Registration Object . . . . . . . . . . . . . . 18 5.2.1. XML Model . . . . . . . . . . . . . . . . . . . . . . 18 5.2.1.1. object . . . . . . . . . . . . 19 5.2.1.2. object . . . . . . . . . . . . 21 5.2.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . 22 5.2.2.1. . . . . . . . . . . . . . . 22 5.2.2.2. . . . . . . . . . . . . . . . 28 5.3. NameWatch Object . . . . . . . . . . . . . . . . . . . . 29 5.3.1. XML Model . . . . . . . . . . . . . . . . . . . . . . 29 5.3.1.1. object . . . . . . . . . 30 5.3.1.2. object . . . . . . . . . . 32 5.3.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . 32 5.3.2.1. . . . . . . . . . . . . . 33 5.3.2.2. . . . . . . . . . . . . . 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 1 October 2023 [Page 2] Internet-Draft DNRD .NAME Mapping March 2023 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 54 11.1. Normative References . . . . . . . . . . . . . . . . . . 54 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 55 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 55 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 1 October 2023 [Page 3] Internet-Draft DNRD .NAME Mapping March 2023 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 1 October 2023 [Page 4] Internet-Draft DNRD .NAME Mapping March 2023 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 1 October 2023 [Page 5] Internet-Draft DNRD .NAME Mapping March 2023 4.2. CSV common field elements Numerous fields reference the CSV common field elements, which are defined in [RFC9022]. For example, the 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 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 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 , under the element, and the element, under the element. Gould Expires 1 October 2023 [Page 6] Internet-Draft DNRD .NAME Mapping March 2023 5.1.1.1. object The element is based on the EPP email forwarding 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 Query Response, see Section 3.1.3. of https://www.verisign.com/assets/email-forwarding- mapping.pdf. A element substitutes for the abstract element to define a concrete definition of an email forwarding. The element can be replaced by other email forwarding definitions using the XML schema substitution groups feature. The element contains the following child elements: * A element that contains the fully qualified name of the email forwarding object. * A element that contains the repository object identifier assigned to the email forwarding object when it was created. * One or more elements that contain the current status descriptors associated with the email forwarding object. * An OPTIONAL 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 elements that contain identifiers for the individual or organizational social information objects associated with the email forwarding object. * An element that contains the forward to email address associated with the email forwarding object. * A element that contains the identifier of the sponsoring registrar. * An OPTIONAL 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 element that contains the date and time of the email forwarding object creation. Gould Expires 1 October 2023 [Page 7] Internet-Draft DNRD .NAME Mapping March 2023 * An OPTIONAL element that contains the date and time identifying the end (expiration) of the email forwarding object's registration period. * An OPTIONAL 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 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 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 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 element that contains the state of the most recent transfer request. - A 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 element that contains the date and time that the transfer was requested. - An 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 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 1 October 2023 [Page 8] Internet-Draft DNRD .NAME Mapping March 2023 - An OPTIONAL 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: ... chris@doe.name EXAMPLE1_EMAILFWD-VRSN jd1234 sh8013 sh8013 cdoe@example.com RegistrarX RegistrarX 1999-04-03T22:00:00.0Z 2021-04-03T22:00:00.0Z pending registrarY 2020-03-03T22:00:00.0Z RegistrarX 2020-03-08T22:00:00.0Z 2022-04-03T22:00:00.0Z ... 5.1.1.2. object The element contains the fully qualified email forwarding object that was deleted and purged. Example of object: ... ... chris@doe.name kris@doe.name ... ... Gould Expires 1 October 2023 [Page 9] Internet-Draft DNRD .NAME Mapping March 2023 5.1.2. CSV Model For the CSV Model of the email forwarding object, the child element of the element is used to hold the new or updated email forwarding objects for the deposit. The child element of the element is used to hold the deleted or purged email forwarding objects for the deposit. Both the and elements contain one or more elements with a set of named CSV file definitions using the "name" attribute. Differential and incremental deposits are based on changes to the email forwarding objects. The updated email forwarding object data under the 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 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 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. The is used to hold the new or updated email forwarding object information for the deposit. The is split into separate CSV file definitions using named 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 field. The following "csvEmailFwd" field elements MUST be used in the "emailFwd" element: Email forwarding name field that contains the Gould Expires 1 October 2023 [Page 10] Internet-Draft DNRD .NAME Mapping March 2023 fully qualified name of the email forwarding object with type="emailFwd:emailAddrType" and isRequired="true". 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" element: Registry Object IDentifier (ROID) for the email forwarding object with isRequired="true". or A choice of: Identifier of the sponsoring client with isRequired="true". 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" element: Identifier of the registrar, defined in Section 4.4, of the client that created the email forwarding object. Identifier of the client that created the email forwarding object. Identifier of the registrar, defined in Section 4.4, of the client that updated the email forwarding object. Identifier of the client that last updated the email forwarding object. Registrant contact identifier for the email forwarding object. Created date and time of the email forwarding object. Date and time of the last update to the email forwarding object. Expiration date and time for the email forwarding Gould Expires 1 October 2023 [Page 11] Internet-Draft DNRD .NAME Mapping March 2023 object. Date and time of the last successful transfer for the email forwarding object. Example of a "emailFwd" element. ... ... emailFwd-YYYYMMDD.csv ... ... 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 1 October 2023 [Page 12] Internet-Draft DNRD .NAME Mapping March 2023 The following "csvEmailFwd" field elements, defined for the "emailFwd" CSV File Definition (Section 5.1.2.1.1), MUST be used in the "emailFwdContacts" element: The name of the email forwarding object that is linked to the contact object with isRequired="true". 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" element: The server-unique contact identifier with isRequired="true". Example of a "emailFwdContacts" element. ... ... emailFwdContacts-YYYYMMDD.csv ... ... 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 1 October 2023 [Page 13] Internet-Draft DNRD .NAME Mapping March 2023 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" element: Email forwarding name field that contains the fully qualified name of the email forwarding object with type="emailFwd:emailAddrType" and isRequired="true". 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" element: Email forwarding object status description which is free-form text describing the rationale for the status. Language of the field. Example of a "emailFwdStatuses" element. Gould Expires 1 October 2023 [Page 14] Internet-Draft DNRD .NAME Mapping March 2023 ... ... emailFwdStatuses-YYYYMMDD.csv ... ... 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" element. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MUST be used in the "emailFwdTransfer" element: State of the most recent transfer request with isRequired="true". Identifier of the registrar, defined in Section 4.4, of the client that requested the transfer with isRequired="true". Date and time that the transfer was requested with isRequired="true". Gould Expires 1 October 2023 [Page 15] Internet-Draft DNRD .NAME Mapping March 2023 Identifier of the registrar, defined in Section 4.4, of the client that should take or took action with isRequired="true". 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" element: Expiration date if the transfer command caused or causes a change in the validity period. Identifier of the client that requested the transfer. 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" element: The name of the email forwarding object with isRequired="true". Example of a "emailFwdTransfer" element. Gould Expires 1 October 2023 [Page 16] Internet-Draft DNRD .NAME Mapping March 2023 ... ... emailFwdTransfer-YYYYMMDD.csv ... ... 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. The 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 is split into separate CSV file definitions using named 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" element: Gould Expires 1 October 2023 [Page 17] Internet-Draft DNRD .NAME Mapping March 2023 The name of the email forwarding object with isRequired="true". Example of a "emailFwd" element: ... ... emailfwd-delete-YYYYMMDD.csv ... ... 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 , under the element, and the element, under the element. Gould Expires 1 October 2023 [Page 18] Internet-Draft DNRD .NAME Mapping March 2023 5.2.1.1. object The element is based on the EPP defensive registration 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 Query Response, see Section 3.1.3. of https://www.verisign.com/assets/defensive- registration-mapping.pdf. A element substitutes for the abstract element to define a concrete definition of a defensive registration. The element can be replaced by other defensive registration definitions using the XML schema substitution groups feature. The element contains the following child elements: * A element that contains the repository object identifier assigned to the defensive registration object when it was created. * A 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 element that contain the identifier for the individual or organizational social information object associated as the holder of the defensive registration object. * An OPTIONAL element that contain the Trademark Identifier (ID) associated with the defensive registration. * An OPTIONAL element that contain the Country which issued the Trademark associated with the defensive registration. * An OPTIONAL element that contain the date when the Trademark was issued. * An OPTIONAL element that contain the identifier for the administrator associated with the defensive registration object. * One or more elements that contain the current status descriptors associated with the defensive registration object. * A element that contains the identifier of the sponsoring registrar. Gould Expires 1 October 2023 [Page 19] Internet-Draft DNRD .NAME Mapping March 2023 * An OPTIONAL 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 element that contains the date and time of the defensive registration object creation. * An OPTIONAL element that contains the date and time identifying the end (expiration) of the defensive registration object's registration period. * An OPTIONAL 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 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 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 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 element that contains the state of the most recent transfer request. - A 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 element that contains the date and time that the transfer was requested. Gould Expires 1 October 2023 [Page 20] Internet-Draft DNRD .NAME Mapping March 2023 - An 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 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 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: ... EXAMPLE3_DEFREG-REP doe jd1234 XYZ-123 US 1990-04-03 sh8013 RegistrarX RegistrarX 1999-04-03T22:00:00.0Z 2000-04-03T22:00:00.0Z ... 5.2.1.2. object The element contains the defensive registration repository object identifier that was deleted and purged. Example of object: Gould Expires 1 October 2023 [Page 21] Internet-Draft DNRD .NAME Mapping March 2023 ... ... EXAMPLE1_DEFREG-REP EXAMPLE2_DEFREG-REP ... ... 5.2.2. CSV Model For the CSV Model of the defensive registration object, the child element of the element is used to hold the new or updated defensive registration objects for the deposit. The child element of the element is used to hold the deleted or purged defensive registration objects for the deposit. Both the and elements contain one or more elements with a set of named CSV file definitions using the "name" attribute. Differential and incremental deposits are based on changes to the defensive registration objects. The updated defensive registration object data under the 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 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 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. The is used to hold the new or updated defensive registration object information for the deposit. The is split into separate CSV file definitions using named elements with the "name" attribute. The following sections include the supported defensive registration CSV file definitions: Gould Expires 1 October 2023 [Page 22] Internet-Draft DNRD .NAME Mapping March 2023 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 field. The following "csvDefReg" field elements MUST be used in the "defReg" element: Defensive registration name field for the defensive registration object with type="defReg:nameType" and isRequired="true". 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" element: Trademark Identifier (ID) associated with the defensive registration with type="defReg:tmType". Country which issued the Trademark associated with the defensive registration with type="defReg:ccType". Date when the Trademark associated with the defensive registration was issued with type="date". Administrator contact identifier for the defensive registration object with type="eppcom:clIDType". The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the "defReg" element: Registry Object IDentifier (ROID) for the defensive registration object with isRequired="true". or A choice of: Identifier of the sponsoring client with isRequired="true". Contains the ID assigned by ICANN with Gould Expires 1 October 2023 [Page 23] Internet-Draft DNRD .NAME Mapping March 2023 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" element: Identifier of the registrar, defined in Section 4.4, of the client that created the object. Identifier of the client that created the defensive registration object. Identifier of the registrar, defined in Section 4.4, of the client that updated the object. Identifier of the client that last updated the defensive registration object. Registrant contact identifier for the defensive registration object. Created date and time of the defensive registration object. Date and time of the last update to the defensive registration object. Expiration date and time for the defensive registration object. Date and time of the last successful transfer for the defensive registration object. Example of a "defReg" element. Gould Expires 1 October 2023 [Page 24] Internet-Draft DNRD .NAME Mapping March 2023 ... ... defReg-YYYYMMDD.csv ... ... 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" element: Gould Expires 1 October 2023 [Page 25] Internet-Draft DNRD .NAME Mapping March 2023 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" element: 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" element: Defensive registration object status description which is free-form text describing the rationale for the status. Language of the field. Example of a "defRegStatuses" element. ... ... csvDefRegStatuses-YYYYMMDD.csv ... ... Example of the corresponding defRegStatuses-YYYYMMDD.csv file. The file contains the statuses for the defensive registration object EXAMPLE1_DEFREG-REP. Gould Expires 1 October 2023 [Page 26] Internet-Draft DNRD .NAME Mapping March 2023 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" element. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MUST be used in the "defRegTransfer" element: Registry Object IDentifier (ROID) for the defensive registration object with isRequired="true". State of the most recent transfer request with isRequired="true". Identifier of the registrar, defined in Section 4.4, of the client that requested the transfer with isRequired="true". Date and time that the transfer was requested with isRequired="true". Identifier of the registrar, defined in Section 4.4, of the client that should take or took action with isRequired="true". 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" element: Expiration date if the transfer command caused or causes a change in the validity period. Identifier of the client that requested the transfer. Identifier of the client that should take or took action for transfer. Example of a "defRegTransfer" element. Gould Expires 1 October 2023 [Page 27] Internet-Draft DNRD .NAME Mapping March 2023 ... ... defRegTransfer-YYYYMMDD.csv ... ... 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. The 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 is split into separate CSV file definitions using named 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" element: Gould Expires 1 October 2023 [Page 28] Internet-Draft DNRD .NAME Mapping March 2023 Registry Object IDentifier (ROID) for the defensive registration object with isRequired="true". Example of a "defReg" element: ... ... defReg-delete-YYYYMMDD.csv ... ... 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 , under the element, and the element, under the element. Gould Expires 1 October 2023 [Page 29] Internet-Draft DNRD .NAME Mapping March 2023 5.3.1.1. object The element is based on the EPP NameWatch 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 Query Response, see Section 3.1.3. of https://www.verisign.com/assets/namewatch- mapping.pdf. A element substitutes for the abstract element to define a concrete definition of a NameWatch. The element can be replaced by other NameWatch definitions using the XML schema substitution groups feature. The element contains the following child elements: * A element that contains the repository object identifier assigned to the NameWatch object when it was created. * A element that contains the name of the NameWatch object. * An OPTIONAL element that contain the identifier for the individual or organizational social information object associated as the holder of the NameWatch object. * An OPTIONAL 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 elements that contain the current status descriptors associated with the NameWatch object. * A element that contains the identifier of the sponsoring registrar. * An OPTIONAL 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 element that contains the date and time of the NameWatch object creation. * An OPTIONAL element that contains the date and time identifying the end (expiration) of the NameWatch object's registration period. Gould Expires 1 October 2023 [Page 30] Internet-Draft DNRD .NAME Mapping March 2023 * An OPTIONAL 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 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 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 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 element that contains the state of the most recent transfer request. - A 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 element that contains the date and time that the transfer was requested. - An 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 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 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 1 October 2023 [Page 31] Internet-Draft DNRD .NAME Mapping March 2023 Example of a NameWatch object: ... EXAMPLE3_NAMEWATCH-VRSN doe jd1234 cdoe@example.com RegistrarX RegistrarX 1999-04-03T22:00:00.0Z 2021-04-03T22:00:00.0Z ... 5.3.1.2. object The element contains the NameWatch repository object identifier that was deleted and purged. Example of object: ... ... EXAMPLE1_NAMEWATCH-REP EXAMPLE2_NAMEWATCH-REP ... ... 5.3.2. CSV Model For the CSV Model of the NameWatch object, the child element of the element is used to hold the new or updated NameWatch objects for the deposit. The child element of the element is used to hold the deleted or purged NameWatch objects for the deposit. Both the and elements contain one or more elements with a set of named CSV file definitions using the "name" attribute. Gould Expires 1 October 2023 [Page 32] Internet-Draft DNRD .NAME Mapping March 2023 Differential and incremental deposits are based on changes to the NameWatch objects. The updated NameWatch object data under the 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 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 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. The is used to hold the new or updated NameWatch object information for the deposit. The is split into separate CSV file definitions using named 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 field. The following "csvNameWatch" field elements MUST be used in the "nameWatch" element: NameWatch name field with type="nameWatch:nameType" and isRequired="true". The following "csvNameWatch" field elements MAY be used in the "nameWatch" element: Report to field that contains the e-mail address to receive the NameWatch reports with type="nameWatch:emailAddrType". Report to frequency for sending of the NameWatch reports to the e-mail address with type="nameWatch:freqType" and the possible values of "daily", "weekly", or "monthly". Gould Expires 1 October 2023 [Page 33] Internet-Draft DNRD .NAME Mapping March 2023 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the "nameWatch" element: Registry Object IDentifier (ROID) for the NameWatch object with isRequired="true". or A choice of: Identifier of the sponsoring client with isRequired="true". 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" element: Identifier of the registrar, defined in Section 4.4, of the client that created the NameWatch object. Identifier of the client that created the NameWatch object. Identifier of the registrar, defined in Section 4.4, of the client that updated the NameWatch object. Identifier of the client that last updated the NameWatch object. Registrant contact identifier for the NameWatch object. Created date and time of the NameWatch object. Date and time of the last update to the NameWatch object. Expiration date and time for the NameWatch object. Date and time of the last successful transfer for the NameWatch object. Example of a "nameWatch" element. Gould Expires 1 October 2023 [Page 34] Internet-Draft DNRD .NAME Mapping March 2023 ... ... nameWatch-YYYYMMDD.csv ... ... 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" element: The status of the NameWatch with type="nameWatch:statusValueType" and isRequired="true". Gould Expires 1 October 2023 [Page 35] Internet-Draft DNRD .NAME Mapping March 2023 The following "rdeCsv" fields, defined for the CSV common field elements (Section 4.2), MUST be used in the "nameWatchStatuses" element: 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" element: NameWatch object status description which is free-form text describing the rationale for the status. Language of the field. Example of a "nameWatchStatuses" element. ... ... csvNameWatchStatuses-YYYYMMDD.csv ... ... 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 1 October 2023 [Page 36] Internet-Draft DNRD .NAME Mapping March 2023 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" element. The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MUST be used in the "nameWatchTransfer" element: Registry Object IDentifier (ROID) for the NameWatch object with isRequired="true". State of the most recent transfer request with isRequired="true". Identifier of the registrar, defined in Section 4.4, of the client that requested the transfer with isRequired="true". Date and time that the transfer was requested with isRequired="true". Identifier of the registrar, defined in Section 4.4, of the client that should take or took action with isRequired="true". 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" element: Expiration date if the transfer command caused or causes a change in the validity period. Identifier of the client that requested the transfer. Identifier of the client that should take or took action for transfer. Example of a "nameWatchTransfer" element. Gould Expires 1 October 2023 [Page 37] Internet-Draft DNRD .NAME Mapping March 2023 ... ... nameWatchTransfer-YYYYMMDD.csv ... ... 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. The 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 is split into separate CSV file definitions using named 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" element: Gould Expires 1 October 2023 [Page 38] Internet-Draft DNRD .NAME Mapping March 2023 Registry Object IDentifier (ROID) for the NameWatch object with isRequired="true". Example of a "nameWatch" element: ... ... nameWatch-delete-YYYYMMDD.csv ... ... 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 and the 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 Registry Data Escrow Email Forwarding Data. 6.2. CSV Email Forwarding Object Gould Expires 1 October 2023 [Page 41] Internet-Draft DNRD .NAME Mapping March 2023 Email Forwarding Comma-Separated Values (CSV) Object Gould Expires 1 October 2023 [Page 42] Internet-Draft DNRD .NAME Mapping March 2023 Gould Expires 1 October 2023 [Page 43] Internet-Draft DNRD .NAME Mapping March 2023 6.3. RDE Defensive Registration Object Registry Data Escrow Defensive Registration Data. Gould Expires 1 October 2023 [Page 44] Internet-Draft DNRD .NAME Mapping March 2023 6.4. CSV Defensive Registration Object Defensive Registration Comma-Separated Values (CSV) Object Gould Expires 1 October 2023 [Page 46] Internet-Draft DNRD .NAME Mapping March 2023 Gould Expires 1 October 2023 [Page 47] Internet-Draft DNRD .NAME Mapping March 2023 Gould Expires 1 October 2023 [Page 48] Internet-Draft DNRD .NAME Mapping March 2023 6.5. RDE NameWatch Object Gould Expires 1 October 2023 [Page 49] Internet-Draft DNRD .NAME Mapping March 2023 Registry Data Escrow NameWatch Data. Gould Expires 1 October 2023 [Page 50] Internet-Draft DNRD .NAME Mapping March 2023 6.6. CSV NameWatch Object NameWatch Comma-Separated Values (CSV) Object Gould Expires 1 October 2023 [Page 52] Internet-Draft DNRD .NAME Mapping March 2023 Gould Expires 1 October 2023 [Page 53] Internet-Draft DNRD .NAME Mapping March 2023 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, . [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, . Gould Expires 1 October 2023 [Page 54] Internet-Draft DNRD .NAME Mapping March 2023 [RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma- Separated Values (CSV) Files", RFC 4180, DOI 10.17487/RFC4180, October 2005, . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, January 2019, . [RFC8909] Lozano, G., "Registry Data Escrow Specification", RFC 8909, DOI 10.17487/RFC8909, November 2020, . [RFC9022] Lozano, G., Gould, J., and C. Thippeswamy, "Domain Name Registration Data (DNRD) Objects Mapping", RFC 9022, DOI 10.17487/RFC9022, May 2021, . Appendix A. Change History A.1. Change from 00 to 01 Ping update 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 1 October 2023 [Page 55]