--- 1/draft-ietf-regext-dnrd-objects-mapping-04.txt 2020-01-09 15:13:13.803079588 -0800 +++ 2/draft-ietf-regext-dnrd-objects-mapping-05.txt 2020-01-09 15:13:14.107087351 -0800 @@ -1,20 +1,20 @@ Network Working Group G. Lozano Internet-Draft ICANN Intended status: Standards Track J. Gould -Expires: June 18, 2020 C. Thippeswamy +Expires: July 12, 2020 C. Thippeswamy VeriSign - Dec 16, 2019 + Jan 09, 2020 Domain Name Registration Data (DNRD) Objects Mapping - draft-ietf-regext-dnrd-objects-mapping-04 + draft-ietf-regext-dnrd-objects-mapping-05 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,25 +23,25 @@ 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 June 18, 2020. + This Internet-Draft will expire on July 12, 2020. Copyright Notice - Copyright (c) 2019 IETF Trust and the persons identified as the + 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -110,22 +110,23 @@ 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 151 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 152 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 152 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 152 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 152 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 152 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 152 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 152 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 154 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 154 + 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 155 17. Example of a full deposit using the XML model . . . . . . . . 155 - 18. Example of differential deposit using the XML model . . . . . 160 + 18. Example of differential deposit using the XML model . . . . . 161 19. Example of a full deposit using the CSV model . . . . . . . . 162 20. Example of differential deposit using the CSV model . . . . . 171 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 182 21.1. Normative References . . . . . . . . . . . . . . . . . . 182 21.2. Informative References . . . . . . . . . . . . . . . . . 183 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 184 1. Introduction Registry Data Escrow is the process by which a registry periodically @@ -1850,21 +1852,21 @@ hostAddresses-YYYYMMDD.csv ... ... - Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The + Example of the corresponding hostAddresses-YYYYMMDD.csv file. The file contains the IP addresses for the host names ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and ns2.domain2.example. Hns1_domain1_test-TEST,192.0.2.1,v4 Hns2_domain1_test-TEST,2001:DB8::1,v6 Hns1_domain2_test-TEST,192.0.2.2,v4 Hns2_domain2_test-TEST,2001:DB8::2,v6 5.2.2.2. @@ -3132,22 +3134,21 @@ 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". Example of a "idnLanguage" element. ... ... - - , + idnLanguage-YYYYMMDD.csv @@ -7029,20 +7030,34 @@ 8. draft-arias-noguchi-registry-data-escrow is now referenced from the I-D repository. 9. The XML prefix "rdeDomain" is now consistently used. 10. The prevID attribute was removed from the examples of full deposits. 11. The examples were updated to use present dates. +16.17. Changes REGEXT 04 to REGEXT 05 + + 1. draft-ietf-regext-data-escrow (version 04) is now referenced from + the I-D repository. + + 2. The example in idnLanguage CSV file definition updated to use the + sep attribute. + + 3. The reference in the example in hostAddresses CSV file definition + was updated. + + 4. Moved [RFC0791] and [RFC4291] to the Normative References + section. + 17. Example of a full deposit using the XML model Example of a full deposit using the XML model: 21. References 21.1. Normative References [I-D.ietf-regext-data-escrow] Lozano, G., "Registry Data Escrow Specification", draft- - ietf-regext-data-escrow-02 (work in progress), November - 2019. + ietf-regext-data-escrow-04 (work in progress), January + 2020. [ISO-3166-1] 3166, I. S., "Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes", ISO Standard 3166, November 2006. [ITU-E164] International Telecommunication Union, "The international public telecommunication numbering plan", ITU-T Recommendation E.164, February 2005. + [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, + DOI 10.17487/RFC0791, September 1981, + . + [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, . [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)", RFC 3915, DOI 10.17487/RFC3915, September 2004, . + [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing + Architecture", RFC 4291, DOI 10.17487/RFC4291, February + 2006, . + [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2009, . [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) @@ -8382,36 +8403,28 @@ Provisioning Protocol (EPP)", RFC 5910, DOI 10.17487/RFC5910, May 2010, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . 21.2. Informative References - [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, - DOI 10.17487/RFC0791, September 1981, - . - [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, DOI 10.17487/RFC3912, September 2004, . - [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing - Architecture", RFC 4291, DOI 10.17487/RFC4291, February - 2006, . - [RFC5891] Klensin, J., "Internationalized Domain Names in Applications (IDNA): Protocol", RFC 5891, DOI 10.17487/RFC5891, August 2010, . [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, .