draft-ietf-regext-dnrd-objects-mapping-04.txt   draft-ietf-regext-dnrd-objects-mapping-05.txt 
Network Working Group G. Lozano Network Working Group G. Lozano
Internet-Draft ICANN Internet-Draft ICANN
Intended status: Standards Track J. Gould Intended status: Standards Track J. Gould
Expires: June 18, 2020 C. Thippeswamy Expires: July 12, 2020 C. Thippeswamy
VeriSign VeriSign
Dec 16, 2019 Jan 09, 2020
Domain Name Registration Data (DNRD) Objects Mapping Domain Name Registration Data (DNRD) Objects Mapping
draft-ietf-regext-dnrd-objects-mapping-04 draft-ietf-regext-dnrd-objects-mapping-05
Abstract Abstract
This document specifies the format, contents and semantics of Domain This document specifies the format, contents and semantics of Domain
Name Registration Data (DNRD) Escrow deposits for a Domain Name Name Registration Data (DNRD) Escrow deposits for a Domain Name
Registry. Registry.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 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. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 26 skipping to change at page 3, line 26
16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 151 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 151
16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 152 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 152
16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 152 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 152
16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 152 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 152
16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 152 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 152
16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 152 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 152
16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 152 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 152
16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 152 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 152
16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 154 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 154
16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 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 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 19. Example of a full deposit using the CSV model . . . . . . . . 162
20. Example of differential deposit using the CSV model . . . . . 171 20. Example of differential deposit using the CSV model . . . . . 171
21. References . . . . . . . . . . . . . . . . . . . . . . . . . 182 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 182
21.1. Normative References . . . . . . . . . . . . . . . . . . 182 21.1. Normative References . . . . . . . . . . . . . . . . . . 182
21.2. Informative References . . . . . . . . . . . . . . . . . 183 21.2. Informative References . . . . . . . . . . . . . . . . . 183
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 184 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 184
1. Introduction 1. Introduction
Registry Data Escrow is the process by which a registry periodically Registry Data Escrow is the process by which a registry periodically
skipping to change at page 42, line 43 skipping to change at page 42, line 43
<rdeCsv:file <rdeCsv:file
cksum="28B194B0"> cksum="28B194B0">
hostAddresses-YYYYMMDD.csv hostAddresses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvHost:contents> </csvHost:contents>
... ...
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 file contains the IP addresses for the host names
ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and
ns2.domain2.example. ns2.domain2.example.
Hns1_domain1_test-TEST,192.0.2.1,v4 Hns1_domain1_test-TEST,192.0.2.1,v4
Hns2_domain1_test-TEST,2001:DB8::1,v6 Hns2_domain1_test-TEST,2001:DB8::1,v6
Hns1_domain2_test-TEST,192.0.2.2,v4 Hns1_domain2_test-TEST,192.0.2.2,v4
Hns2_domain2_test-TEST,2001:DB8::2,v6 Hns2_domain2_test-TEST,2001:DB8::2,v6
5.2.2.2. <csvHost:deletes> 5.2.2.2. <csvHost:deletes>
skipping to change at page 72, line 27 skipping to change at page 72, line 27
<rdeCsv:fUrl> URL that defines the character code points that can be <rdeCsv:fUrl> URL that defines the character code points that can be
used for the language defined by the <rdeCsv:fLang> field element. used for the language defined by the <rdeCsv:fLang> field element.
The attribute "isRequired" MUST equal "true". The attribute "isRequired" MUST equal "true".
Example of a "idnLanguage" <csvIDN:contents> <rdeCsv:csv> element. Example of a "idnLanguage" <csvIDN:contents> <rdeCsv:csv> element.
... ...
<csvIDN:contents> <csvIDN:contents>
... ...
<rdeCsv:csv name="idnLanguage"> <rdeCsv:csv name="idnLanguage" sep=",">
<rdeCsv:sep>,</rdeCsv:sep>
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fIdnTableId isRequired="true"/> <rdeCsv:fIdnTableId isRequired="true"/>
<rdeCsv:fUrl isRequired="true"/> <rdeCsv:fUrl isRequired="true"/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="D6B0424F"> cksum="D6B0424F">
idnLanguage-YYYYMMDD.csv idnLanguage-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
skipping to change at page 155, line 19 skipping to change at page 155, line 19
8. draft-arias-noguchi-registry-data-escrow is now referenced from 8. draft-arias-noguchi-registry-data-escrow is now referenced from
the I-D repository. the I-D repository.
9. The XML prefix "rdeDomain" is now consistently used. 9. The XML prefix "rdeDomain" is now consistently used.
10. The prevID attribute was removed from the examples of full 10. The prevID attribute was removed from the examples of full
deposits. deposits.
11. The examples were updated to use present dates. 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 17. Example of a full deposit using the XML model
Example of a full deposit using the XML model: Example of a full deposit using the XML model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit type="FULL" id="20191017001" <rde:deposit type="FULL" id="20191017001"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
skipping to change at page 182, line 15 skipping to change at page 182, line 28
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
</rde:contents> </rde:contents>
</rde:deposit> </rde:deposit>
21. References 21. References
21.1. Normative References 21.1. Normative References
[I-D.ietf-regext-data-escrow] [I-D.ietf-regext-data-escrow]
Lozano, G., "Registry Data Escrow Specification", draft- Lozano, G., "Registry Data Escrow Specification", draft-
ietf-regext-data-escrow-02 (work in progress), November ietf-regext-data-escrow-04 (work in progress), January
2019. 2020.
[ISO-3166-1] [ISO-3166-1]
3166, I. S., "Codes for the representation of names of 3166, I. S., "Codes for the representation of names of
countries and their subdivisions -- Part 1: Country countries and their subdivisions -- Part 1: Country
codes", ISO Standard 3166, November 2006. codes", ISO Standard 3166, November 2006.
[ITU-E164] [ITU-E164]
International Telecommunication Union, "The international International Telecommunication Union, "The international
public telecommunication numbering plan", ITU-T public telecommunication numbering plan", ITU-T
Recommendation E.164, February 2005. Recommendation E.164, February 2005.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC0791, September 1981,
<https://www.rfc-editor.org/info/rfc791>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
[RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for
the Extensible Provisioning Protocol (EPP)", RFC 3915, the Extensible Provisioning Protocol (EPP)", RFC 3915,
DOI 10.17487/RFC3915, September 2004, DOI 10.17487/RFC3915, September 2004,
<https://www.rfc-editor.org/info/rfc3915>. <https://www.rfc-editor.org/info/rfc3915>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<https://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, Domain Name Mapping", STD 69, RFC 5731,
DOI 10.17487/RFC5731, August 2009, DOI 10.17487/RFC5731, August 2009,
<https://www.rfc-editor.org/info/rfc5731>. <https://www.rfc-editor.org/info/rfc5731>.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
skipping to change at page 183, line 25 skipping to change at page 183, line 47
Provisioning Protocol (EPP)", RFC 5910, Provisioning Protocol (EPP)", RFC 5910,
DOI 10.17487/RFC5910, May 2010, DOI 10.17487/RFC5910, May 2010,
<https://www.rfc-editor.org/info/rfc5910>. <https://www.rfc-editor.org/info/rfc5910>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
21.2. Informative References 21.2. Informative References
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC0791, September 1981,
<https://www.rfc-editor.org/info/rfc791>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
DOI 10.17487/RFC3912, September 2004, DOI 10.17487/RFC3912, September 2004,
<https://www.rfc-editor.org/info/rfc3912>. <https://www.rfc-editor.org/info/rfc3912>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC5891] Klensin, J., "Internationalized Domain Names in [RFC5891] Klensin, J., "Internationalized Domain Names in
Applications (IDNA): Protocol", RFC 5891, Applications (IDNA): Protocol", RFC 5891,
DOI 10.17487/RFC5891, August 2010, DOI 10.17487/RFC5891, August 2010,
<https://www.rfc-editor.org/info/rfc5891>. <https://www.rfc-editor.org/info/rfc5891>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
 End of changes. 15 change blocks. 
19 lines changed or deleted 33 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/