--- 1/draft-ietf-regext-dnrd-objects-mapping-01.txt 2019-10-25 10:13:30.117252392 -0700 +++ 2/draft-ietf-regext-dnrd-objects-mapping-02.txt 2019-10-25 10:13:30.405259667 -0700 @@ -1,20 +1,20 @@ Network Working Group G. Lozano Internet-Draft ICANN Intended status: Standards Track J. Gould -Expires: February 27, 2020 C. Thippeswamy +Expires: April 27, 2020 C. Thippeswamy VeriSign - Aug 26, 2019 + Oct 25, 2019 Domain Name Registration Data (DNRD) Objects Mapping - draft-ietf-regext-dnrd-objects-mapping-01 + draft-ietf-regext-dnrd-objects-mapping-02 Abstract This document specifies the format, contents and semantics of Domain Name Registration Data (DNRD) Escrow deposits for a Domain Name Registry. Status of This Memo This Internet-Draft is submitted in full conformance with the @@ -23,21 +23,21 @@ 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 February 27, 2020. + This Internet-Draft will expire on April 27, 2020. Copyright Notice Copyright (c) 2019 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 @@ -58,78 +58,79 @@ 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6 4.6. CSV Parent Child Relationship . . . . . . . . . . . . . . 6 4.7. CSV elements . . . . . . . . . . . . . . . . . . . . . . 7 4.8. Internationalized and Localized Elements . . . . . . . . 12 5. Object Description . . . . . . . . . . . . . . . . . . . . . 14 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 14 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 33 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 43 - 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 60 - 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 68 - 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 72 - 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 77 - 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 79 - 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 79 - 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 82 - 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 - 8. Data escrow agent extended verification process . . . . . . . 83 - 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 84 - 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 84 - 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 94 - 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 97 - 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 102 - 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 104 - 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 107 - 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 110 - 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116 - 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 120 - 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 124 - 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 126 - 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 128 - 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 130 - 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 132 - 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 135 - 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 136 - 10. Internationalization Considerations . . . . . . . . . . . . . 138 - 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 138 - 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 144 - 12.1. Implementation in the gTLD space . . . . . . . . . . . . 144 + 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 61 + 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 69 + 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 73 + 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 78 + 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 80 + 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 80 + 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 83 + 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 + 8. Data escrow agent extended verification process . . . . . . . 84 + 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 85 + 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 85 + 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 95 + 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98 + 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 103 + 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 105 + 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 108 + 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 111 + 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 117 + 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 121 + 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 125 + 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 127 + 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 129 + 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 131 + 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 133 + 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 136 + 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 137 + 10. Internationalization Considerations . . . . . . . . . . . . . 139 + 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 139 + 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 145 + 12.1. Implementation in the gTLD space . . . . . . . . . . . . 145 - 13. Security Considerations . . . . . . . . . . . . . . . . . . . 145 - 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 145 - 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 145 - 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 146 + 13. Security Considerations . . . . . . . . . . . . . . . . . . . 146 + 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 146 + 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 146 + 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 147 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 - to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 146 - 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 146 - 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 147 - 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 147 - 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 147 - 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 148 - 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 149 - 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 149 - 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 150 - 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 150 - 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 150 - 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 150 - 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 150 - 17. Example of a full deposit using the XML model . . . . . . . . 150 - 18. Example of differential deposit using the XML model . . . . . 156 - 19. Example of a full deposit using the CSV model . . . . . . . . 157 - 20. Example of differential deposit using the CSV model . . . . . 166 - 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 177 - 21.1. Normative References . . . . . . . . . . . . . . . . . . 177 - 21.2. Informative References . . . . . . . . . . . . . . . . . 178 - 21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 179 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 179 + to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 147 + 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 147 + 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 148 + 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 148 + 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 148 + 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 149 + 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 150 + 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 150 + 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 151 + 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 151 + 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 151 + 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 151 + 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 151 + 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 151 + 17. Example of a full deposit using the XML model . . . . . . . . 153 + 18. Example of differential deposit using the XML model . . . . . 158 + 19. Example of a full deposit using the CSV model . . . . . . . . 160 + 20. Example of differential deposit using the CSV model . . . . . 169 + 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 180 + 21.1. Normative References . . . . . . . . . . . . . . . . . . 180 + 21.2. Informative References . . . . . . . . . . . . . . . . . 181 + 21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 182 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182 1. Introduction This document defines the data escrow structure of the standard set of objects for a Domain Name Registry which include: o Domain: Internet domain names that are typically provisioned in a Domain Name Registry using the EPP domain name mapping [RFC5731]. The attributes defined in the EPP domain name mapping [RFC5731] are fully supported by this document. @@ -463,51 +464,50 @@ Repository Object IDentifier (ROID) field with type="eppcom:roidType" and isRequired="true". Registrant contact identifier with type="eppcom:clIDType". The object status description, which is free form text describing the rationale for the status, with type="normalizedString". - Identifier of client (registrar) that sponsors the - object with type="eppcom:clIDType" and isRequired="true". + Identifier of the client (registrar) that sponsors + the object with type="eppcom:clIDType" and isRequired="true". Identifier of the registrar, defined in Section 5.4, of the client that created the object with type="eppcom:clIDType". - Identifier of client that created the object with + Identifier of the client that created the object with type="eppcom:clIDType". Identifier of the registrar, defined in Section 5.4, of the client that updated the object with type="eppcom:clIDType". - Identifier of client that updated the object with + Identifier of the client that updated the object with type="eppcom:clIDType". Identifier of the registrar, defined in Section 5.4, of the client that requested the transfer with type="eppcom:clIDType" and isRequired="true". - Identifier of client that requested the transfer with - type="eppcom:clIDType". + Identifier of the client that requested the transfer + with type="eppcom:clIDType". Identifier of the registrar, defined in Section 5.4, of the client that should take or took action with type="eppcom:clIDType" and isRequired="true". - Identifier of client that should take or took action - for transfer with type="eppcom:clIDType". + Identifier of the client that should take or took + action for transfer with type="eppcom:clIDType". - Created date of object with type="dateTime" and - isRequired="true". + Created date of object with type="dateTime". Updated date of object with type="dateTime". Expiration date of object with type="dateTime". Date that transfer was requested with type="dateTime" and isRequired="true". Date that transfer action should be taken or has been taken with type="dateTime" and isRequired="true". @@ -567,21 +567,21 @@ - + @@ -859,64 +859,68 @@ Domain name field with type="eppcom:labelType" and isRequired="true". The following "csvDomain" field elements MAY be used in the "domain" element: Fully qualified name of the original IDN domain name object related to the variant domain name object with type="eppcom:labelType". - The following "rdeCsv" fields, defined in section CSV common field - elements (Section 4.7.2), MUST be used in the "domain" - element: + The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the + "domain" element: Registry Object IDentifier (ROID) for the domain name object with isRequired="true". - Identifier of client that sponsors the domain name - object with isRequired="true". - - Created date and time of the domain name object - with isRequired="true". - - Identifier of the registrar, defined in Section 5.4, - of the client that updated the object. + or A choice of: - Date and time of the last update to the domain name - object. + Identifier of the sponsoring client with + isRequired="true". - Expiration date and time for the domain name - object. The attribute isRequired MUST equal "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.7.2), MAY be used in the "domain" element: Identifier of the registrar, defined in Section 5.4, of the client that created the object. + Identifier of the client that created the domain name + object. + + Identifier of the registrar, defined in Section 5.4, + of the client that updated the object. + + Identifier of the client that last updated the domain + name object. + UTF8 encoded domain name for the field element. IDN Table Identifier used for the IDN domain name object that MUST match a field element in the "idnLanguage" CSV files, as defined in Section 5.5.2. Registrant contact identifier for the domain name object. - Identifier of client that created the domain name + Created date and time of the domain name object. + + Date and time of the last update to the domain name object. - Identifier of the client that last updated the domain - name object. + Expiration date and time for the domain name + object. Date and time of the last transfer for the domain name object. Example of a "domain" element. ... ... @@ -962,36 +966,33 @@ xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--abc123.test, registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 5.1.2.1.2. "domainContacts" CSV File Definition The "domainContacts" CSV File Definition defines the fields and CSV file references used for the domain name object link records to contact objects, as described in Contact Object (Section 5.3). - The following "csvDomain" field elements MUST be used in the + The following "csvDomain" field elements, defined for the "domain" + CSV File Definition (Section 5.1.2.1.1), MUST be used in the "domainContacts" element: + The name of the domain object that is linked to + the contact object with isRequired="true". + The contact type for the contact object link with type="domain: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 "csvDomain" field elements, defined for the "domain" - CSV File Definition (Section 5.1.2.1.1), MUST be used in the - "domainContacts" element: - - The name of the domain object that is linked to - the contact object with isRequired="true". - The following "csvContact" fields, defined for the "contact" CSV File Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" element: The server-unique contact identifier with isRequired="true". Example of a "domainContacts" element. @@ -1031,36 +1032,33 @@ xn--abc123.test,xnabc123billing,billing xn--abc321.test,xnabc123admin,admin xn--abc321.test,xnabc123tech,tech xn--abc321.test,xnabc123billing,billing 5.1.2.1.3. "domainStatuses" CSV File Definition The "domainStatuses" CSV File Definition defines the fields and CSV file references used for the domain name object statuses. - The following "csvDomain" field elements MUST be used in the - "domainStatuses" element: + The following "csvDomain" fields, defined for the "domain" CSV File + Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" + element: + + Domain name of status with isRequired="true". The status of the domain name with type="domain:statusValueType" and isRequired="true". The Registry Grace Period (RGP) status, as a sub-status of the "pendingDelete" status value, with type="rgp:statusValueType" as defined in [RFC3915]. - The following "csvDomain" fields, defined for the "domain" CSV File - Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" - element: - - Domain name of status with isRequired="true". - The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.7.2), MAY be used in the "domainStatuses" element: Domain object status description which is free form text describing the rationale for the status. Language of the field. Example of a "domainStatuses" @@ -1106,29 +1104,33 @@ CSV file references used for the domain name delegated hosts (name servers). The "domainNameServers" CSV files define the relationship between a domain name object and a delegated host. The "domainNameServers" CSV File is used to support the model, defined in [RFC5731]. The following "csvDomain" fields, defined for the "domain" CSV File Definition (Section 5.1.2.1.1), MUST be used in the "domainNameServers" element: - Domain name using the delegated host with host - and isRequired="true". + Domain name using the delegated host with + isRequired="true". - The following "rdeCsv" fields, defined in section CSV common field - elements (Section 4.7.2), MUST be used in the "domainNameServers" - element: + The following "csvHost" and "rdeCsv" field elements MUST be used in + the "domainNameServers" element: - Registry Object IDentifier (ROID) used to uniquely - reference a delegated host record with isRequired="true". + or A choice of: + + Host name field with type="eppcom:labelType" and + isRequired="true". + + Host object Registry Object IDentifier (ROID) + assigned to the host object with isRequired="true". Example of a "domainNameServers" element. ... ... @@ -1372,24 +1373,24 @@ 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.7.2), MAY be used in the "domainTransfer" element: Expiration date if the transfer command caused or causes a change in the validity period. - Identifier of client that requested the transfer. + Identifier of the client that requested the transfer. - Identifier of client that should take or took action - for transfer. + Identifier of the client that should take or took + action for transfer. The following "csvDomain" fields, defined for the "domain" CSV File Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" element: Domain name of the domain object involved in the transfer with isRequired="true". Example of a "domainTransfer" element. @@ -1508,26 +1509,27 @@ o One or more elements that describe the status of the host object. o Zero or more elements that contain the IP addresses associated with the host object. o A element that contains the identifier of the sponsoring registrar. - o A element that contains the identifier of the registrar - that created the host object. An OPTIONAL client attribute is - used to specify the client that performed the operation. + o An OPTIONAL element that contains the identifier of the + registrar that created the host object. An OPTIONAL client + attribute is used to specify the client that performed the + operation. - o A element that contains the date and time of host-object - creation. + o An OPTIONAL element that contains the date and time of + host-object creation. o An OPTIONAL element that contains the identifier of the registrar that last updated the host object. This element MUST NOT be present if the host object has never been modified. An OPTIONAL client attribute is used to specify the client that performed the operation. o An OPTIONAL element that contains the date and time of the most recent host-object modification. This element MUST NOT be present if the host object has never been modified. @@ -1615,41 +1617,46 @@ Host name field with type="eppcom:labelType" and isRequired="true". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.7.2), MUST be used in the "host" element: Repository Object IDentifier (ROID) assigned to the host object with isRequired="true". - The following "rdeCsv" fields, defined in section CSV common field - elements (Section 4.7.2), MAY be used in the "host" - element: + The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the + "host" element: + + or A choice of: Identifier of the sponsoring client with isRequired="true". - Identifier of the registrar, defined in Section 5.4, - of the client that created the object with isRequired="true". + Contains the ID assigned by ICANN with + type="positiveInteger". The attribute "isRequired" MUST equal + "true". - Identifier of client that created the host object. + Identifier of the registrar, defined in Section 5.4, + of the client that created the object. - Date and time that the host object was created with - isRequired="true". + Identifier of the client that created the host + object. Identifier of the registrar, defined in Section 5.4, of the client that updated the object. - Identifier of client that last updated the host + Identifier of the client that last updated the host object. + Date and time that the host object was created. + Date and time that the host object was last updated. Date and time that the host was last transferred. Example of a "host" element. ... ... @@ -1703,36 +1710,36 @@ 5.2.2.1.2. "hostStatuses" CSV File Definition The "hostStatuses" CSV File Definition defines the fields and CSV file references used for the host object statuses. The following "csvHost" fields, defined for the "host" CSV File Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" element: The status of the host with - type="host:statusValueType" and isRequired="true"./>. + type="host:statusValueType" and isRequired="true". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.7.2), MUST be used in the "hostStatuses" element: Host object Registry Object IDentifier (ROID) assigned to the host object with isRequired="true". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.7.2), MAY be used in the "hostStatuses" element: Host object status description which is free form text describing the rationale for the status. The - attribute isRequired MUST equal "true". + attribute "isRequired" MUST equal "true". Language of the field. Example of a "hostStatuses" element. ... ... @@ -1766,34 +1773,34 @@ 5.2.2.1.3. "hostAddresses" CSV File Definition The "hostAddresses" CSV File Definition defines the fields and CSV file references used for the host object IP addresses. The following "csvHost" field elements MUST be used in the "hostAddresses" element: IP addresses associated with the host object with - type="host:addrStringType". The attribute isRequired MUST equal + type="host:addrStringType". The attribute "isRequired" MUST equal "true". IP addresses version associated with the host object with type="host:ipType". "host:ipType" has the enumerated - values of "v4" or "v6". The attribute isRequired MUST equal + values of "v4" or "v6". The attribute "isRequired" MUST equal "true". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.7.2), MUST be used in the "hostAddresses" element: Host object Registry Object IDentifier (ROID) - assigned to the host object. + assigned to the host object with isRequired="true". Example of a "hostAddresses" element. ... ... @@ -1941,26 +1948,27 @@ telephone number. o An OPTIONAL element that contains the contact's facsimile telephone number. o An element that contains the contact's email address. o A element that contains the identifier of the sponsoring registrar. - o A element that contains the identifier of the registrar - that created the contact object. An OPTIONAL client attribute is - used to specify the client that performed the operation. + o An OPTIONAL element that contains the identifier of the + registrar that created the contact object. An OPTIONAL client + attribute is used to specify the client that performed the + operation. - o A element that contains the date and time of contact- - object creation. + o An OPTIONAL element that contains the date and time of + contact-object creation. o An OPTIONAL element that contains the identifier of the registrar that last updated the contact object. This element MUST NOT be present if the contact has never been modified. An OPTIONAL client attribute is used to specify the client that performed the operation. o An OPTIONAL element that contains the date and time of the most recent contact-object modification. This element MUST NOT be present if the contact object has never been modified. @@ -2001,22 +2009,22 @@ o An OPTIONAL element that identifies elements that requiring exceptional server-operator handling to allow or restrict disclosure to third parties. See Section 2.9 of [RFC5733] for a description of the child elements contained within the element. Example object: ... - Csh8013-TEST sh8013 + Csh8013-TEST John Doe Example Inc. 123 Example Dr. Suite 100 Dulles VA @@ -2119,51 +2127,56 @@ Contains the contact's voice telephone number extension with type="token". Contains the contact's facsimile telephone number with type="contact:e164StringType". Contains the contact's facsimile telephone number extension with type="token". - The following "rdeCsv" fields, defined in section CSV common field - elements (Section 4.7.2), MUST be used in the "contact" - element: + The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the + "contact" element: The Registry Object IDentifier (ROID) for the contact object with isRequired="true". - Identifier of client (registrar) that sponsors the - contact object with isRequired="true". - - Identifier of the registrar, defined in Section 5.4, - of the client that created the object with isRequired="true". + or A choice of: - Created date and time of the contact object with + Identifier of the sponsoring client with isRequired="true". - Identifier of the registrar, defined in Section 5.4, - of the client that updated the object. - - Date and time of the last update to the contact - object. + 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.7.2), MAY be used in the "contact" element: - Identifier of client that created the contact object. + Identifier of the registrar, defined in Section 5.4, + of the client that created the object. + + Identifier of the client that created the contact + object. + + Identifier of the registrar, defined in Section 5.4, + of the client that updated the object. Identifier of the client that last updated the contact object. + Created date and time of the contact object. + + Date and time of the last update to the contact + object. + Date and time of the last transfer for the contact object. Example of a "contact" element. ... ... @@ -2434,24 +2447,24 @@ 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.7.2), MAY be used in the "contactTransfer" element: - Identifier of client that requested the transfer. + Identifier of the client that requested the transfer. - Identifier of client that should take or took action - for transfer. + Identifier of the client that should take or took + action for transfer. The following "csvContact" fields, defined for the "contact" CSV File Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" element: Server-unique contact identifier for the contact object with isRequired="true". Example of a "contactTransfer" element. @@ -2806,34 +2819,43 @@ definitions. 5.4.2.1.1. "registrar" CSV File Definition The "registrar" CSV File Definition defines the fields and CSV file references used for the registrar object records. The following "csvRegistrar" field elements MUST be used in the "registrar" element: - Contains the server-unique registrar identifier - with type="eppcom:clIDType" and isRequired="true". + or A choice of: + + Contains the server-unique registrar + identifier with type="eppcom:clIDType" and isRequired="true". + + Contains the ID assigned by ICANN with + type="positiveInteger". The attribute "isRequired" MUST equal + "true". Contains the name of the registrar with type="normalizedString" and isRequired="true". The following field elements MAY be used in the "registrar" element: Contains the status of the registrar with type="csvRegistrar:statusValueType". Contains the ID assigned by ICANN with - type="positiveInteger". + type="positiveInteger". This field is included in this section in + addition to the section above to support optionally providing the + field when the field is + used. Contains the Whois URL of the registrar with type="anyURI". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.7.2), MAY be used in the "registrar" element: Created date and time of the registrar object. @@ -2853,21 +2875,22 @@ Section 4.8. Registrar city with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in Section 4.8. Registrar country code with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in Section 4.8. - Registrar email address. + Registrar email address. The attribute + "isRequired" MUST equal "false". Registrar state or province with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in Section 4.8. Registrar postal code with an OPTIONAL "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in Section 4.8. Registrar voice telephone number. @@ -2894,21 +2917,21 @@ - + registrar-YYYYMMDD.csv @@ -2945,22 +2968,28 @@ is split into separate CSV file definitions using named elements with the "name" attribute. The following section defines the supported registrar deletes CSV file definition. 5.4.2.2.1. "registrar" Deletes CSV File Definition The following "csvRegistrar" field elements MUST be used in the deletes "registrar" element: - Contains the server-unique registrar identifier - with type="eppcom:clIDType" and isRequired="true". + or A choice of: + + Contains the server-unique registrar + identifier with type="eppcom:clIDType" and isRequired="true". + + Contains the ID assigned by ICANN with + type="positiveInteger". The attribute "isRequired" MUST equal + "true". Example of a "registrar" element. ... ... @@ -3051,25 +3080,25 @@ The "idnLanguage" CSV File Definition defines the fields and CSV file references used for the IDN table reference object records. The following "rdeCsv" fields, defined in Section 4.7.2, MUST be used in the "idnLanguage" element: The language identifier that matches the values for the field element in the "domain" CSV File Definition (Section 5.1.2.1.1) files. The attribute - isRequired MUST equal "true". + "isRequired" MUST equal "true". URL that defines the character code points that can be used for the language defined by the field element. - The attribute isRequired MUST equal "true". + The attribute "isRequired" MUST equal "true". Example of a "idnLanguage" element. ... ... , @@ -3104,21 +3133,21 @@ definition. 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition The following "idnLanguage" field elements MUST be used in the deletes "idnLanguage" element: The language identifier that matches the values for the field element in the "domain" CSV File Definition (Section 5.1.2.1.1) files. The attribute - isRequired MUST equal "true". + "isRequired" MUST equal "true". Example of a "idnLanguage" element. ... ... @@ -3199,22 +3228,22 @@ "withheld". This status is only used when the NNDN is used for an IDN variant. * If a NNDN is considered a mirrored IDN variant of a domain object, then the NNDN will be tagged as "mirrored". A mirroringNS attribute is used to specify if the mirrored IDN variant use the NS mirror mechanism. The default value of mirroringNS is true. If another mechanism such as DNAME is used, the value of mirroringNS attribute MUST be false. - o A element that contains the date and time of the NNDN - object creation. + o An OPTIONAL element that contains the date and time of + the NNDN object creation. Example of object: ... xn--exampl-gva.test pt-BR example1.test withheld 2005-04-23T11:49:00.0Z @@ -3279,29 +3308,24 @@ Domain name used to generate the IDN variant with type="eppcom:labelType". Defines whether the "mirroring" uses the NS mirror mechanism, as described for the "mirroringNS" attribute in Section 5.6.1.1, with type="boolean". If the field element is not defined the default value is "true". The following "rdeCsv" fields, defined in section CSV common field - elements (Section 4.7.2), MUST be used in the "domain" + elements (Section 4.7.2), MAY be used in the "NNDN" element: - Created date and time of the NNDN object with - isRequired="true". - - The following "rdeCsv" fields, defined in section CSV common field - elements (Section 4.7.2), MAY be used in the "domain" - element: + Created date and time of the NNDN object. Name of the NNDN in Unicode character set for the field element. IDN Table Identifier for the NNDN that matches an IDN Table Reference Object record, as defined in Section 5.5.2. Example of a "NNDN" element: ... @@ -3851,50 +3875,50 @@ default="eppcom\:clIDType"/> - + - - + - + - - - @@ -3904,21 +3928,21 @@ - + type="rde:rrType" minOccurs="0"/> + type="dateTime" minOccurs="0"/> @@ -4852,23 +4876,23 @@ type="contact:postalInfoType" maxOccurs="2"/> + type="rde:rrType" minOccurs="0"/> + type="dateTime" minOccurs="0"/> @@ -5542,21 +5566,21 @@ type="rdeCsv:fPositiveIntegerType" substitutionGroup="rdeCsv:field"/> - + @@ -5924,21 +5948,21 @@ type="eppcom:labelType"/> + type="dateTime" minOccurs="0"/> @@ -6836,20 +6860,103 @@ 16.13. Changes REGEXT 00 to REGEXT 01 1. Added the element to the "repositoryTypeGroup" group element in the rdeHeader. 2. Privacy consideration section was added 3. Updates on section 8 +16.14. Changes REGEXT 01 to REGEXT 02 + + 1. Added a choice between the use of the or + fields in the CSV "domain", "host", and + "contact" definitions. + + 2. Added a choice between the use of the or + fields in the CSV "domainNameServers" + definition. + + 3. Changed "of client" to "of the client" throughout the document. + + 4. Modified all references of 'The attribute isRequired MUST equal + "true".' to 'The attribute "isRequired" MUST equal "true".' + + 5. Combined the and + fields in a single required list for the CSV "domainContacts" + definition. + + 6. Combined the , , and + fields in a single required list for the + CSV "domainStatuses" definition. + + 7. Moved the the fields to the MAY + list for the CSV "domain", "host", and "contact" definitions. + + 8. Made the order of the , , + , and fields more consistent in the + CSV lists. + + 9. Fixed an error in the order of the object example. + + 10. Changed to be optional to match being + optional in the XML model, by having it use type + rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and + ensuring that is included in the MAY field + lists and not the MUST field lists. + + 11. Made optional for the "domain" CSV definition + to be consistent with the XML model, by removing the sentence + 'The attribute "isRequired" MUST equal "true".' from the + description and moving the field to the MAY field list. + + 12. Made optional for the "domain" and "contact" + CSV definitions to be consistent with the XML model, by moving + the field to the MAY field list. + + 13. Made optional to be consistent with the XML + model, by having it use type rdeCsv:fClIDType instead of + rdeCsv:fClIDRequiredType. + + 14. Made required to be consistent with the XML + model, by having it use type rdeCsv:fClIDRequiredType instead of + rdeCsv:fClIDType. + + 15. Made the field in the "host", "contact", + and "registrar" CSV definitions required explicitly by removing + 'and isRequired="true"' and adding the sentence 'The attribute + isRequired MUST equal "true".', when it is chosen as the primary + field. + + 16. Removed extra '/>.' at the end of the field + description in the "hostStatuses" CSV definition. + + 17. Made the field optional to be consistent + with the XML model, by having csvRegistrar:fStatusType extend + rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. + + 18. Made the field for the "registrar" CSV + definition explicitly optional to be consistent with the XML + model, by adding the sentence 'The attribute isRequired MUST + equal "false".' to the field description and including the + definition of isRequired="false" in the "registrar" CSV + definition examples. + + 19. Added the choice between the use of the and + fields in the deletes "registrar" CSV + definition to be consistent with the "registrar" CSV definition. + + 20. Made the and elements optional for the host and + contact objects in the XML model to be consistent with the + domain object. + 17. Example of a full deposit using the XML model Example of a full deposit using the XML model: - + registrar-YYYYMMDD.csv + @@ -8041,21 +8148,21 @@ - + registrar-YYYYMMDD.csv @@ -8211,22 +8317,22 @@ [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running Code: The Implementation Status Section", BCP 205, RFC 7942, DOI 10.17487/RFC7942, July 2016, . [variantTLDsReport] Internet Corporation for Assigned Names and Numbers (ICANN), "A Study of Issues Related to the Management of IDN Variant TLDs", February 2012, - . + . 21.3. URIs [1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data- escrow-05.txt Authors' Addresses Gustavo Lozano Internet Corporation for Assigned Names and Numbers