--- 1/draft-ietf-regext-dnrd-objects-mapping-10.txt 2020-12-16 13:13:25.448123432 -0800 +++ 2/draft-ietf-regext-dnrd-objects-mapping-11.txt 2020-12-16 13:13:25.756131311 -0800 @@ -1,20 +1,20 @@ Network Working Group G. Lozano Internet-Draft ICANN Intended status: Standards Track J. Gould -Expires: April 11, 2021 C. Thippeswamy +Expires: June 19, 2021 C. Thippeswamy VeriSign - Oct 08, 2020 + Dec 16, 2020 Domain Name Registration Data (DNRD) Objects Mapping - draft-ietf-regext-dnrd-objects-mapping-10 + draft-ietf-regext-dnrd-objects-mapping-11 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 April 11, 2021. + This Internet-Draft will expire on June 19, 2021. Copyright Notice Copyright (c) 2020 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 @@ -118,24 +118,25 @@ 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 147 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 147 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 149 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 149 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 150 16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 150 16.19. Changes REGEXT 06 to REGEXT 07 . . . . . . . . . . . . . 150 16.20. Changes REGEXT 07 to REGEXT 08 . . . . . . . . . . . . . 150 16.21. Changes REGEXT 08 to REGEXT 09 . . . . . . . . . . . . . 151 16.22. Changes REGEXT 09 to REGEXT 10 . . . . . . . . . . . . . 151 + 16.23. Changes REGEXT 10 to REGEXT 11 . . . . . . . . . . . . . 151 17. Example of a Full Deposit using the XML model . . . . . . . . 151 18. Example of Differential Deposit using the XML model . . . . . 157 19. Example of a Full Deposit using the CSV model . . . . . . . . 158 - 20. Example of Differential Deposit using the CSV model . . . . . 167 + 20. Example of Differential Deposit using the CSV model . . . . . 168 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 178 21.1. Normative References . . . . . . . . . . . . . . . . . . 178 21.2. Informative References . . . . . . . . . . . . . . . . . 181 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182 1. Introduction Registry Data Escrow (RDE) is the process by which a registry periodically submits data deposits to a third-party called an escrow agent. These deposits comprise the minimum data needed by a third- @@ -987,21 +988,21 @@ Registry Object IDentifier (ROID) for the domain name object with isRequired="true". or A choice of: Identifier of the sponsoring client with isRequired="true". Contains the Globally Unique Registrar Identifier (GURID) assigned by ICANN with - type="positiveInteger" and "isRequired"="true". + type="positiveInteger" and isRequired="true". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2.2), MAY be used in the "domain" element: Identifier of the registrar, defined in Section 5.4, of the client that created the domain name object. Identifier of the client that created the domain name object. @@ -1112,21 +1113,21 @@ Example of a "domainContacts" element. ... ... - + domainContacts-YYYYMMDD.csv ... @@ -1244,21 +1245,21 @@ Example of a "domainNameServers" element. ... ... - + domainNameServers-YYYYMMDD.csv ... @@ -1434,21 +1435,21 @@ domain1.example,604800,30730,8,2,91C9B176EB////F1C46F6A55 domain1.example,604800,61882,8,2,9F8FEAC94B////1272AF09F3 Example of a "dnssec" element with the Key Data Interface of [RFC5910]: ... - + dnssec-key-YYYYMMDD.csv @@ -1746,21 +1747,21 @@ 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". Contains the Globally Unique Registrar Identifier (GURID) assigned by ICANN with - type="positiveInteger" and "isRequired"="true". + type="positiveInteger" and isRequired="true". Identifier of the registrar, defined in Section 5.4, of the client that created the host object. Identifier of the client that created the host object. Identifier of the registrar, defined in Section 5.4, of the client that last updated the host object. @@ -2262,21 +2263,21 @@ The Registry Object IDentifier (ROID) for the contact object with isRequired="true". or A choice of: Identifier of the sponsoring client with isRequired="true". Contains the Globally Unique Registrar Identifier (GURID) assigned by ICANN with - type="positiveInteger" and "isRequired"="true". + type="positiveInteger" and isRequired="true". The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.6.2.2), MAY be used in the "contact" element: Identifier of the registrar, defined in Section 5.4, of the client that created the contact object. Identifier of the client that created the contact object. @@ -2949,21 +2950,21 @@ The following "csvRegistrar" field elements MUST be used in the "registrar" element: or A choice of: Contains the server-unique registrar identifier with type="eppcom:clIDType" and isRequired="true". Contains the Globally Unique Registrar Identifier (GURID) assigned by ICANN with - type="positiveInteger" and "isRequired"="true". + type="positiveInteger" and isRequired="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". @@ -6893,20 +6894,26 @@ regext/7JiP2fzOr8KCnzI2rwoP-_KlxZY 6. Changes based on the feedback provided here: https://mailarchive.ietf.org/arch/msg/regext/dbuyW5YTYj4VcFHUQYC- D8OMv_g 7. Changes based on the feedback provided here: https://mailarchive.ietf.org/arch/msg/regext/ ExUZenwC81ZQe9x24-8IKT_FWm8 +16.23. Changes REGEXT 10 to REGEXT 11 + + 1. Changes based on the feedback provided here: + https://mailarchive.ietf.org/arch/msg/regext/ + ghEr55r7CVdwUSvkvMGpol4aSh0 + 17. Example of a Full Deposit using the XML model Example of a Full Deposit using the XML model: