draft-ietf-regext-dnrd-objects-mapping-00.txt   draft-ietf-regext-dnrd-objects-mapping-01.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: December 20, 2019 C. Thippeswamy Expires: February 27, 2020 C. Thippeswamy
VeriSign VeriSign
Jun 18, 2019 Aug 26, 2019
Domain Name Registration Data (DNRD) Objects Mapping Domain Name Registration Data (DNRD) Objects Mapping
draft-ietf-regext-dnrd-objects-mapping-00 draft-ietf-regext-dnrd-objects-mapping-01
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 December 20, 2019. This Internet-Draft will expire on February 27, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
skipping to change at page 2, line 36 skipping to change at page 2, line 36
5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 77 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 77
5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 79 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 79
5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 79 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 79
6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 82 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 82
7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8. Data escrow agent extended verification process . . . . . . . 83 8. Data escrow agent extended verification process . . . . . . . 83
9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 84 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 84
9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 84 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 84
9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 94 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 94
9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 97 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 97
9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 101 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 102
9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 104 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 104
9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 107 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 107
9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 110 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 110
9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116
9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 120 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 120
9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 124 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 124
9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 126 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 126
9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 128 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 128
9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 130 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 130
9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 132 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 132
9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 135 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 135
9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 136 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 136
10. Internationalization Considerations . . . . . . . . . . . . . 138 10. Internationalization Considerations . . . . . . . . . . . . . 138
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 138 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 138
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 144 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 144
12.1. Implementation in the gTLD space . . . . . . . . . . . . 144 12.1. Implementation in the gTLD space . . . . . . . . . . . . 144
13. Security Considerations . . . . . . . . . . . . . . . . . . . 145 13. Security Considerations . . . . . . . . . . . . . . . . . . . 145
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 145 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 145
15. Change History . . . . . . . . . . . . . . . . . . . . . . . 145 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 145
15.1. Changes from draft-arias-noguchi-registry-data-escrow-02 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 146
16.1. Changes from draft-arias-noguchi-registry-data-escrow-02
to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 146 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 146
15.2. Changes from version 00 to 01 . . . . . . . . . . . . . 146 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 146
15.3. Changes from version 01 to 02 . . . . . . . . . . . . . 146 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 147
15.4. Changes from version 02 to 03 . . . . . . . . . . . . . 147 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 147
15.5. Changes from version 03 to 04 . . . . . . . . . . . . . 147 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 147
15.6. Changes from version 04 to 05 . . . . . . . . . . . . . 148 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 148
15.7. Changes from version 05 to 06 . . . . . . . . . . . . . 149 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 149
15.8. Changes from version 06 to 07 . . . . . . . . . . . . . 149 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 149
15.9. Changes from version 07 to 08 . . . . . . . . . . . . . 149 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 150
15.10. Changes from version 08 to 09 . . . . . . . . . . . . . 150 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 150
15.11. Changes from version 09 to 10 . . . . . . . . . . . . . 150 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 150
15.12. Changes from version 10 to 00 . . . . . . . . . . . . . 150 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 150
16. Example of a full deposit using the XML model . . . . . . . . 150 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 150
17. Example of differential deposit using the XML model . . . . . 155 17. Example of a full deposit using the XML model . . . . . . . . 150
18. Example of a full deposit using the CSV model . . . . . . . . 157 18. Example of differential deposit using the XML model . . . . . 156
19. Example of differential deposit using the CSV model . . . . . 166 19. Example of a full deposit using the CSV model . . . . . . . . 157
20. References . . . . . . . . . . . . . . . . . . . . . . . . . 177 20. Example of differential deposit using the CSV model . . . . . 166
20.1. Normative References . . . . . . . . . . . . . . . . . . 177 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 177
20.2. Informative References . . . . . . . . . . . . . . . . . 178 21.1. Normative References . . . . . . . . . . . . . . . . . . 177
20.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 179 21.2. Informative References . . . . . . . . . . . . . . . . . 178
21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 179 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 179
1. Introduction 1. Introduction
This document defines the data escrow structure of the standard set This document defines the data escrow structure of the standard set
of objects for a Domain Name Registry which include: of objects for a Domain Name Registry which include:
o Domain: Internet domain names that are typically provisioned in a o Domain: Internet domain names that are typically provisioned in a
Domain Name Registry using the EPP domain name mapping [RFC5731]. Domain Name Registry using the EPP domain name mapping [RFC5731].
The attributes defined in the EPP domain name mapping [RFC5731] The attributes defined in the EPP domain name mapping [RFC5731]
skipping to change at page 80, line 18 skipping to change at page 80, line 18
corresponding to a Registrar data escrow deposit. In the case corresponding to a Registrar data escrow deposit. In the case
of an ICANN-accredited Registrar, the <rdeHeader:registrar> of an ICANN-accredited Registrar, the <rdeHeader:registrar>
element MUST be the IANA Registrar ID assigned by ICANN. element MUST be the IANA Registrar ID assigned by ICANN.
* A <rdeHeader:ppsp> element that defines the provider ID * A <rdeHeader:ppsp> element that defines the provider ID
corresponding to a Privacy and Proxy Services Provider data corresponding to a Privacy and Proxy Services Provider data
escrow deposit. In the case of an ICANN-accredited Privacy and escrow deposit. In the case of an ICANN-accredited Privacy and
Proxy Services Provider, the <rdeHeader:ppsp> element MUST be Proxy Services Provider, the <rdeHeader:ppsp> element MUST be
the unique ID assigned by ICANN. the unique ID assigned by ICANN.
* A <rdeHeader:reseller> element that defines the provider ID
corresponding to a Reseller data escrow deposit.
o A <count> element that contains the number of objects in the SRS o A <count> element that contains the number of objects in the SRS
at a specific point in time (watermark) regardless of the type of at a specific point in time (watermark) regardless of the type of
deposit: differential, full or incremental. The <count> element deposit: differential, full or incremental. The <count> element
supports the following attributes: supports the following attributes:
* A "uri" attribute reflects the XML namespace URI of the primary * A "uri" attribute reflects the XML namespace URI of the primary
objects for the XML Model and CSV Model. For example, the objects for the XML Model and CSV Model. For example, the
"uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for
domain name objects using the XML Model, and the "uri" is set domain name objects using the XML Model, and the "uri" is set
to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name
skipping to change at page 83, line 36 skipping to change at page 83, line 36
specification to support existing business models. specification to support existing business models.
3. Adding new escrowed objects using the <rde:contents> and 3. Adding new escrowed objects using the <rde:contents> and
<rde:deletes> elements. <rde:deletes> elements.
4. Providing the XML schemas to third parties that require them to 4. Providing the XML schemas to third parties that require them to
validate the escrow deposits. validate the escrow deposits.
8. Data escrow agent extended verification process 8. Data escrow agent extended verification process
The Data Escrow Agent MUST perform a extended verification process A Data Escrow Agent SHOULD perform an extended verification process
using the contents of the data escrow deposits to a point in time that starts by creating a dataset to be tested.
(watermark), last full plus all differentials or last full plus last
incremental escrow deposits. The following are the minimum suggested o If a full deposit is to be tested, the full deposit is the
tests: dataset.
o If an incremental deposit is to be tested, the dataset is created
by using the incremental plus the last previous full deposit.
o If a differential deposit is to be tested, the dataset is created
by using the differential deposit plus all the required deposits
leading to the last previous full deposit.
The following are the minimum suggested tests on the dataset:
o Validate the escrow deposits using the definition agreed with the o Validate the escrow deposits using the definition agreed with the
registry. registry.
* In the case of the XML model, the contents of the escrow * In the case of the XML model, the contents of the escrow
deposits MUST be validated using the XML schemas of the deposits MUST be validated using the XML schemas of the
profile. profile.
o Count the objects and validate that the number of objects is equal o Count the objects and validate that the number of objects is equal
to the number objects reported in the <header> element of the to the number objects reported in the <header> element of the
skipping to change at page 138, line 12 skipping to change at page 138, line 12
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<group name="repositoryTypeGroup"> <group name="repositoryTypeGroup">
<choice> <choice>
<element name="tld" type="eppcom:labelType" /> <element name="tld" type="eppcom:labelType" />
<element name="registrar" type="positiveInteger"/> <element name="registrar" type="positiveInteger"/>
<element name="ppsp" type="token"/> <element name="ppsp" type="token"/>
<element name="reseller" type="token"/>
</choice> </choice>
</group> </group>
<complexType name="countType"> <complexType name="countType">
<simpleContent> <simpleContent>
<extension base="long"> <extension base="long">
<attribute name="uri" type="anyURI" use="required"/> <attribute name="uri" type="anyURI" use="required"/>
<attribute name="rcdn" type="eppcom:labelType"/> <attribute name="rcdn" type="eppcom:labelType"/>
<attribute name="registrarId" type="positiveInteger"/> <attribute name="registrarId" type="positiveInteger"/>
</extension> </extension>
skipping to change at page 145, line 37 skipping to change at page 145, line 37
escrow deposits. In a similar manner, the Registry SHOULD escrow deposits. In a similar manner, the Registry SHOULD
authenticate the identity of the Escrow Agent before submitting any authenticate the identity of the Escrow Agent before submitting any
data. data.
Additionally, the Registry and the Escrow Agent SHOULD use integrity Additionally, the Registry and the Escrow Agent SHOULD use integrity
checking mechanisms to ensure the data transmitted is what the source checking mechanisms to ensure the data transmitted is what the source
intended. Validation of the contents by the Escrow Agent is intended. Validation of the contents by the Escrow Agent is
RECOMMENDED to ensure not only the file was transmitted correctly RECOMMENDED to ensure not only the file was transmitted correctly
from the Registry, but also the contents are also "meaningful". from the Registry, but also the contents are also "meaningful".
14. Acknowledgments 14. 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.
15. Acknowledgments
Parts of this document are based on EPP [RFC5730] and related RFCs by Parts of this document are based on EPP [RFC5730] and related RFCs by
Scott Hollenbeck. Scott Hollenbeck.
Special suggestions that have been incorporated into this document
were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc
Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen
Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul
Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan,
Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James
Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer.
Shoji Noguchi and Francisco Arias participated as co-authors until Shoji Noguchi and Francisco Arias participated as co-authors until
version 05 providing invaluable support for this document. version 05 providing invaluable support for this document.
15. Change History 16. Change History
[[RFC Editor: Please remove this section.]] [[RFC Editor: Please remove this section.]]
15.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to -
dnrd-objects-mapping-00 dnrd-objects-mapping-00
1. Added definition for child elements under the <domain> element. 1. Added definition for child elements under the <domain> element.
2. Added definition for child elements under the <host> element. 2. Added definition for child elements under the <host> element.
3. Added definition for child elements under the <contact> element. 3. Added definition for child elements under the <contact> element.
4. Rewrote the IDN Variants Handling section to use the variant 4. Rewrote the IDN Variants Handling section to use the variant
states as described in ICANN's Study of Issues Related to the states as described in ICANN's Study of Issues Related to the
skipping to change at page 146, line 28 skipping to change at page 146, line 38
5. Renamed <icannID> to <gurid> in the <rdeRegistrar>. 5. Renamed <icannID> to <gurid> in the <rdeRegistrar>.
6. Renamed <dnssec> to <secDNS> in the <domain> element. 6. Renamed <dnssec> to <secDNS> in the <domain> element.
7. Renamed <transfData> to <trnData> in the <domain> element. 7. Renamed <transfData> to <trnData> in the <domain> element.
8. Added <whoisInfo> element under <rdeRegistrar> element. 8. Added <whoisInfo> element under <rdeRegistrar> element.
9. Fixed some typographical errors and omissions. 9. Fixed some typographical errors and omissions.
15.2. Changes from version 00 to 01 16.2. Changes from 00 to 01
1. Specify OPTIONAL elements in the draft. 1. Specify OPTIONAL elements in the draft.
2. Added NNDN object to support list of reserved names and different 2. Added NNDN object to support list of reserved names and different
IDN variants models. IDN variants models.
3. Removed subordinated host element from the domain object. 3. Removed subordinated host element from the domain object.
4. Added eppParams object. 4. Added eppParams object.
5. Added variantGenerator element to the domain object. 5. Added variantGenerator element to the domain object.
6. Added lgr to the IDN table object. 6. Added lgr to the IDN table object.
15.3. Changes from version 01 to 02 16.3. Changes from 01 to 02
1. Updates to the all objects based on feedback from the list. 1. Updates to the all objects based on feedback from the list.
2. Start of XML and CSV drafts merge. 2. Start of XML and CSV drafts merge.
3. Added header object. 3. Added header object.
4. Added report object. 4. Added report object.
5. Added notification object. 5. Added notification object.
6. Added Data Escrow Agent Extended Verification Process section. 6. Added Data Escrow Agent Extended Verification Process section.
7. Added Notifications from Registries to Third Parties. 7. Added Notifications from Registries to Third Parties.
8. Added Notifications from Data Escrow Agents to Third Parties. 8. Added Notifications from Data Escrow Agents to Third Parties.
9. Added FULL, DIFF deposit examples using the XML model only. 9. Added FULL, DIFF deposit examples using the XML model only.
15.4. Changes from version 02 to 03 16.4. Changes from 02 to 03
1. Remove authinfo from the XML Schema. 1. Remove authinfo from the XML Schema.
2. Resend attribute is now an element 2. Resend attribute is now an element
3. Scope attribute added to policy object. 3. Scope attribute added to policy object.
15.5. Changes from version 03 to 04 16.5. Changes from 03 to 04
1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft-
arias-noguchi-dnrd-objects-mapping-02. arias-noguchi-dnrd-objects-mapping-02.
2. Changed the cksum attribute of <rdeCsv:file> to use CRC32 and 2. Changed the cksum attribute of <rdeCsv:file> to use CRC32 and
changed all of the sample cksum values to use CRC32, based on changed all of the sample cksum values to use CRC32, based on
feedback from David Kipling. feedback from David Kipling.
3. Changed the optional <rdeCsv:sep> element to be an optional 3. Changed the optional <rdeCsv:sep> element to be an optional
"sep" attribute value of the <rdeCsv:csv> element with a default "sep" attribute value of the <rdeCsv:csv> element with a default
skipping to change at page 148, line 37 skipping to change at page 148, line 47
files. files.
18. Added use of the MUST keyword for CSV fields that are required 18. Added use of the MUST keyword for CSV fields that are required
to be supported in an EPP based system. to be supported in an EPP based system.
19. Removed use of the <rdeCsv:fRoid> field element for the 19. Removed use of the <rdeCsv:fRoid> field element for the
"registrar" CSV file. "registrar" CSV file.
20. Added definition of <csvNNDN:fMirroringNS> field element. 20. Added definition of <csvNNDN:fMirroringNS> field element.
15.6. Changes from version 04 to 05 16.6. Changes from 04 to 05
1. Updated the examples of the full and differential deposits using 1. Updated the examples of the full and differential deposits using
the CSV and XML model. the CSV and XML model.
2. Made <rdeCsv:fExDate> optional for the "domainTransfer" CSV file 2. Made <rdeCsv:fExDate> optional for the "domainTransfer" CSV file
to match the XML definition. to match the XML definition.
3. Made <csvDomain:fOriginalName> optional for the "domain" CSV file 3. Made <csvDomain:fOriginalName> optional for the "domain" CSV file
to match the XML definition. to match the XML definition.
4. Made <rdeCsv:fTrDate> optional for the "domain" and "contact" CSV 4. Made <rdeCsv:fTrDate> optional for the "domain" and "contact" CSV
files to match the XML definition. files to match the XML definition.
5. Change <idnTableId> from IDREF to idType. 5. Change <idnTableId> from IDREF to idType.
6. Minor editorial changes. 6. Minor editorial changes.
15.7. Changes from version 05 to 06 16.7. Changes from 05 to 06
1. Revised the differential and incremental deposits for the CSV 1. Revised the differential and incremental deposits for the CSV
format to use cascade update / replace and delete from the parent format to use cascade update / replace and delete from the parent
object to be consistent with the XML format. object to be consistent with the XML format.
2. Revised the structure of the CSV format sections to utilize sub- 2. Revised the structure of the CSV format sections to utilize sub-
sections instead of a list for the CSV file definitions. sections instead of a list for the CSV file definitions.
3. Added the "CSV Parent Child Relationship" section to describe the 3. Added the "CSV Parent Child Relationship" section to describe the
concept of parent child relationships across CSV file concept of parent child relationships across CSV file
skipping to change at page 149, line 36 skipping to change at page 149, line 47
<csvDomain:fKeyTag>, <csvDomain:fDsAlg>, <csvDomain:fDigestType>, <csvDomain:fKeyTag>, <csvDomain:fDsAlg>, <csvDomain:fDigestType>,
<csvDomain:fDigest>, <csvDomain:fFlags>, <csvDomain:fProtocol>, <csvDomain:fDigest>, <csvDomain:fFlags>, <csvDomain:fProtocol>,
<csvDomain:fKeyAlg>, <csvDomain:fPubKey>, <rdeCsv:fTrStatus>, <csvDomain:fKeyAlg>, <csvDomain:fPubKey>, <rdeCsv:fTrStatus>,
<rdeCsv:fReRr>, <rdeCsv:fReDate<, <rdeCsv:fAcRr>, <rdeCsv:fReRr>, <rdeCsv:fReDate<, <rdeCsv:fAcRr>,
<rdeCsv:fAcDate>, <csvHost:fStatus>, <csvContact:fCc>, <rdeCsv:fAcDate>, <csvHost:fStatus>, <csvContact:fCc>,
<csvContact:fStatus>, <csvContact:fPostalType>, <csvContact:fStatus>, <csvContact:fPostalType>,
<csvRegistrar:fStatus>, and <csvNNDN:fNameState>. <csvRegistrar:fStatus>, and <csvNNDN:fNameState>.
6. Revised the CSV examples to use a more realistic set of records. 6. Revised the CSV examples to use a more realistic set of records.
15.8. Changes from version 06 to 07 16.8. Changes from 06 to 07
1. Created "repositoryTypeGroup" group element in the rdeHeader 1. Created "repositoryTypeGroup" group element in the rdeHeader
including the <rdeHeader:registrar>, <rdeHeader:ppsp> and including the <rdeHeader:registrar>, <rdeHeader:ppsp> and
<rdeHeader:tld> elements. <rdeHeader:tld> elements.
2. Added the optional "rcdn" and "registrarId" attributes to the 2. Added the optional "rcdn" and "registrarId" attributes to the
<rdeHeader:count> element <rdeHeader:count> element
15.9. Changes from version 07 to 08 16.9. Changes from 07 to 08
1. The following registrar elements were made optional to support 1. The following registrar elements were made optional to support
greater flexibility for the implementation of policies: status, greater flexibility for the implementation of policies: status,
postalInfo, email and crDate. postalInfo, email and crDate.
2. The following domain name elements were made optional to support 2. The following domain name elements were made optional to support
greater flexibility for the implementation of policies: crRr. greater flexibility for the implementation of policies: crRr.
15.10. Changes from version 08 to 09 16.10. Changes from 08 to 09
1. Implementation Status section was added 1. Implementation Status section was added
15.11. Changes from version 09 to 10 16.11. Changes from 09 to 10
1. Editorial changes in section Section 5.1.2.1.6. 1. Editorial changes in section Section 5.1.2.1.6.
2. Added MAY clause when the DS Data Interface is used in section 2. Added MAY clause when the DS Data Interface is used in section
Section 5.1.2.1.6. Section 5.1.2.1.6.
15.12. Changes from version 10 to 00 16.12. Changes from 10 to REGEXT 00
1. Internet Draft (I-D) adopted by the REGEXT WG. 1. Internet Draft (I-D) adopted by the REGEXT WG.
16. Example of a full deposit using the XML model 16.13. Changes REGEXT 00 to REGEXT 01
1. Added the <rdeHeader:reseller> element to the
"repositoryTypeGroup" group element in the rdeHeader.
2. Privacy consideration section was added
3. Updates on section 8
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="20101017001" prevId="20101010001" <rde:deposit type="FULL" id="20101017001" prevId="20101010001"
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"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
skipping to change at page 155, line 31 skipping to change at page 156, line 4
<epp:prov/> <epp:prov/>
</epp:purpose> </epp:purpose>
<epp:recipient> <epp:recipient>
<epp:ours/> <epp:ours/>
<epp:public/> <epp:public/>
</epp:recipient> </epp:recipient>
<epp:retention> <epp:retention>
<epp:stated/> <epp:stated/>
</epp:retention> </epp:retention>
</epp:statement> </epp:statement>
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
<rdePolicy:policy <rdePolicy:policy
scope="//rde:deposit/rde:contents/rdeDomain:domain" scope="//rde:deposit/rde:contents/rdeDomain:domain"
element="rdeDom:registrant" /> element="rdeDom:registrant" />
</rde:contents> </rde:contents>
</rde:deposit> </rde:deposit>
17. Example of differential deposit using the XML model 18. Example of differential deposit using the XML model
Example of a differential deposit using the XML model: Example of a differential deposit using the XML model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit type="DIFF" id="20101017002" prevId="20101017001" <rde:deposit type="DIFF" id="20101017002" prevId="20101017001"
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"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
skipping to change at page 157, line 21 skipping to change at page 157, line 41
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1 uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1
</rdeHeader:count> </rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
</rdeHeader:count> </rdeHeader:count>
</rdeHeader:header> </rdeHeader:header>
</rde:contents> </rde:contents>
</rde:deposit> </rde:deposit>
18. Example of a full deposit using the CSV model 19. Example of a full deposit using the CSV model
Example of a full deposit using the CSV model: Example of a full deposit using the CSV model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit <rde:deposit
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
skipping to change at page 166, line 24 skipping to change at page 166, line 45
</epp:recipient> </epp:recipient>
<epp:retention> <epp:retention>
<epp:indefinite/> <epp:indefinite/>
</epp:retention> </epp:retention>
</epp:statement> </epp:statement>
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
</rde:contents> </rde:contents>
</rde:deposit> </rde:deposit>
19. Example of differential deposit using the CSV model 20. Example of differential deposit using the CSV model
Example of a differential deposit using the CSV model: Example of a differential deposit using the CSV model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit <rde:deposit
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
skipping to change at page 177, line 4 skipping to change at page 177, line 25
</epp:purpose> </epp:purpose>
<epp:recipient> <epp:recipient>
<epp:ours/> <epp:ours/>
<epp:public/> <epp:public/>
<epp:unrelated/> <epp:unrelated/>
</epp:recipient> </epp:recipient>
<epp:retention> <epp:retention>
<epp:indefinite/> <epp:indefinite/>
</epp:retention> </epp:retention>
</epp:statement> </epp:statement>
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
</rde:contents> </rde:contents>
</rde:deposit> </rde:deposit>
20. References 21. References
20.1. Normative References 21.1. Normative References
[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.
skipping to change at page 178, line 15 skipping to change at page 178, line 33
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
August 2009, <https://www.rfc-editor.org/info/rfc5733>. August 2009, <https://www.rfc-editor.org/info/rfc5733>.
[RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS)
Security Extensions Mapping for the Extensible Security Extensions Mapping for the Extensible
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>.
20.2. Informative References 21.2. Informative References
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC0791, September 1981, DOI 10.17487/RFC0791, September 1981,
<https://www.rfc-editor.org/info/rfc791>. <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,
skipping to change at page 179, line 5 skipping to change at page 179, line 22
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>.
[variantTLDsReport] [variantTLDsReport]
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
(ICANN), "A Study of Issues Related to the Management of (ICANN), "A Study of Issues Related to the Management of
IDN Variant TLDs", February 2012, IDN Variant TLDs", February 2012,
<http://www.icann.org/en/topics/idn/ <http://www.icann.org/en/topics/idn/
idn-vip-integrated-issues-final-clean-20feb12-en.pdf>. idn-vip-integrated-issues-final-clean-20feb12-en.pdf>.
20.3. URIs 21.3. URIs
[1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data- [1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data-
escrow-05.txt escrow-05.txt
Authors' Addresses Authors' Addresses
Gustavo Lozano Gustavo Lozano
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
12025 Waterfront Drive, Suite 300 12025 Waterfront Drive, Suite 300
Los Angeles 90292 Los Angeles 90292
 End of changes. 35 change blocks. 
55 lines changed or deleted 94 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/