draft-ietf-regext-dnrd-objects-mapping-06.txt   draft-ietf-regext-dnrd-objects-mapping-07.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: August 23, 2020 C. Thippeswamy Expires: October 30, 2020 C. Thippeswamy
VeriSign VeriSign
Feb 20, 2020 Apr 28, 2020
Domain Name Registration Data (DNRD) Objects Mapping Domain Name Registration Data (DNRD) Objects Mapping
draft-ietf-regext-dnrd-objects-mapping-06 draft-ietf-regext-dnrd-objects-mapping-07
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 August 23, 2020. This Internet-Draft will expire on October 30, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 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
skipping to change at page 2, line 12 skipping to change at page 2, line 12
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. XML Model . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. XML Model . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6 4. Conventions Used in This Document . . . . . . . . . . . . . . 6
4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6
4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 7
4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 7 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 7
4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 7 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 7
4.6. Conventions applicable to the CSV Model . . . . . . . . . 7 4.6. Conventions applicable to the CSV Model . . . . . . . . . 7
5. Object Description . . . . . . . . . . . . . . . . . . . . . 15 5. Object Description . . . . . . . . . . . . . . . . . . . . . 15
5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 15 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 15
5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 34 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 34
5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 44 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 44
5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 62 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 62
5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 70 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 70
5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 74 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 74
5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 79 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 79
5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 81 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 81
5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 81 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 81
5.10. DNRD Common Objects Collection . . . . . . . . . . . . . 84
6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 84 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 84
7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8. Data escrow agent extended verification process . . . . . . . 85 8. Data escrow agent extended verification process . . . . . . . 85
9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 86 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 86
9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 86 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 87
9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 95 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 96
9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98
9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 102 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 102
9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 103 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 104
9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 106 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 106
9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 108 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 108
9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 114 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 114
9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 117 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 117
9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 120 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 120
9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 121 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 121
9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 123 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 123
9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 124 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 124
9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 125 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 126
9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 128 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 128
9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 128 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 128
9.17. DNRD Common Objects . . . . . . . . . . . . . . . . . . . 130
10. Internationalization Considerations . . . . . . . . . . . . . 130 10. Internationalization Considerations . . . . . . . . . . . . . 130
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 130 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 130
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 135 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 138
12.1. Implementation in the gTLD space . . . . . . . . . . . . 135 12.1. Implementation in the gTLD space . . . . . . . . . . . . 139
13. Security Considerations . . . . . . . . . . . . . . . . . . . 139
13. Security Considerations . . . . . . . . . . . . . . . . . . . 136 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 140
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 136 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 140
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 136 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 140
16. Change History . . . . . . . . . . . . . . . . . . . . . . . 137
16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02
to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 137 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 141
16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 137 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 141
16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 138 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 141
16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 138 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 142
16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 138 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 142
16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 139 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 143
16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 140 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 144
16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 140 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 144
16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 141 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 144
16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 141 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 145
16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 141 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 145
16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 141 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 145
16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 141 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 145
16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 141 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 145
16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 143 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 147
16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 143 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 147
16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 144 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 148
16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 144 16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 148
17. Example of a Full Deposit using the XML model . . . . . . . . 144 16.19. Changes REGEXT 06 to REGEXT 07 . . . . . . . . . . . . . 148
18. Example of Differential Deposit using the XML model . . . . . 150 17. Example of a Full Deposit using the XML model . . . . . . . . 148
19. Example of a Full Deposit using the CSV model . . . . . . . . 151 18. Example of Differential Deposit using the XML model . . . . . 154
20. Example of Differential Deposit using the CSV model . . . . . 160 19. Example of a Full Deposit using the CSV model . . . . . . . . 155
21. References . . . . . . . . . . . . . . . . . . . . . . . . . 171 20. Example of Differential Deposit using the CSV model . . . . . 164
21.1. Normative References . . . . . . . . . . . . . . . . . . 171 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 175
21.2. Informative References . . . . . . . . . . . . . . . . . 173 21.1. Normative References . . . . . . . . . . . . . . . . . . 175
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 173 21.2. Informative References . . . . . . . . . . . . . . . . . 177
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 178
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
submits data deposits to a third-party called an escrow agent. These submits data deposits to a third-party called an escrow agent. These
deposits comprise the minimum data needed by a third-party to resume deposits comprise the minimum data needed by a third-party to resume
operations if the registry cannot function and is unable or unwilling operations if the registry cannot function and is unable or unwilling
to facilitate an orderly transfer of service. For example, for a to facilitate an orderly transfer of service. For example, for a
domain name registry or registrar, the data to be deposited would domain name registry or registrar, the data to be deposited would
include all the objects related to registered domain names, e.g., include all the objects related to registered domain names, e.g.,
skipping to change at page 6, line 33 skipping to change at page 6, line 35
services that only a Registry is capable of providing, by reason of services that only a Registry is capable of providing, by reason of
its designation as the Registry. Typical examples of Registry its designation as the Registry. Typical examples of Registry
Services are DNS resolution for the RCDN, WHOIS and EPP. Services are DNS resolution for the RCDN, WHOIS and EPP.
ALLOCATED. A status of some label with respect to a zone, whereby ALLOCATED. A status of some label with respect to a zone, whereby
the label is associated administratively to some entity that has the label is associated administratively to some entity that has
requested the label. This term (and its cognates "allocation" and requested the label. This term (and its cognates "allocation" and
"to allocate") may represent the first step on the way to delegation "to allocate") may represent the first step on the way to delegation
in the DNS. in the DNS.
4. General Conventions 4. Conventions Used in This Document
4.1. Date and Time 4.1. Date and Time
Numerous fields indicate "dates", such as the creation and expiry Numerous fields indicate "dates", such as the creation and expiry
dates for domain names. These fields SHALL contain timestamps dates for domain names. These fields SHALL contain timestamps
indicating the date and time in UTC as specified in [RFC3339], with indicating the date and time in UTC as specified in [RFC3339], with
no offset from the zero meridian. no offset from the zero meridian.
4.2. Country names 4.2. Country names
skipping to change at page 84, line 30 skipping to change at page 84, line 30
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:csvIDN-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:csvIDN-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:csvNNDN-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:csvNNDN-1.0">1</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>
... ...
5.10. DNRD Common Objects Collection
The DNRD Common Objects Collection contains data structures
referenced by two or more of the main objects in the XML model.
6. RDE IDN Variants handling 6. RDE IDN Variants handling
Depending on the Registration Policy of the Registry, for a domain Depending on the Registration Policy of the Registry, for a domain
name there may be multiple variant names. See [variantTLDsReport] name there may be multiple variant names. See [variantTLDsReport]
for further detail on IDN variants. for further detail on IDN variants.
A registry could choose to escrow IDN variants as domains or NNDN A registry could choose to escrow IDN variants as domains or NNDN
objects. A specific IDN variant can be represented in the escrow objects. A specific IDN variant can be represented in the escrow
deposit, as a domain or as an NNDN object, but not both. deposit, as a domain or as an NNDN object, but not both.
skipping to change at page 86, line 35 skipping to change at page 86, line 41
o All idnTableRef definitions linked from other objects MUST be o All idnTableRef definitions linked from other objects MUST be
present. present.
o If an EPP Parameters Object was escrowed in the past, one and only o If an EPP Parameters Object was escrowed in the past, one and only
one EPP Parameters Object MUST be present. one EPP Parameters Object MUST be present.
o The watermark is not in the future. o The watermark is not in the future.
9. Formal Syntax 9. Formal Syntax
Schemas are presented here. This standard is specified in XML Schema notation. The formal syntax
presented here is a complete schema representation suitable for
automated validation.
The BEGIN and END tags are not part of the schema; they are used to
note the beginning and ending of the schema for URI registration
purposes.
9.1. RDE CSV Schema 9.1. RDE CSV Schema
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeCsv-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
schemaLocation="eppcom-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"
schemaLocation="rde-1.0.xsd"/>
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow Comma-Seperated Values (CSV) Registry Data Escrow Comma-Seperated Values (CSV)
</documentation> </documentation>
</annotation> </annotation>
<!-- csv content element --> <!-- csv content element -->
<element name="csv" type="rdeCsv:csvType"/> <element name="csv" type="rdeCsv:csvType"/>
skipping to change at page 95, line 47 skipping to change at page 96, line 17
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeDomain-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0" xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:domain-1.0"/> <import namespace="urn:ietf:params:xml:ns:domain-1.0"/>
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1"/> <import namespace="urn:ietf:params:xml:ns:secDNS-1.1"/>
<import namespace="urn:ietf:params:xml:ns:rgp-1.0"/> <import namespace="urn:ietf:params:xml:ns:rgp-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0"/> <import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"/>
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow Domain provisioning schema Registry Data Escrow Domain provisioning schema
</documentation> </documentation>
</annotation> </annotation>
<element name="abstractDomain" <element name="abstractDomain"
type="rdeDomain:abstractContentType" type="rdeDomain:abstractContentType"
substitutionGroup="rde:content" abstract="true"/> substitutionGroup="rde:content" abstract="true"/>
skipping to change at page 97, line 6 skipping to change at page 97, line 26
<element name="registrant" <element name="registrant"
type="eppcom:clIDType" minOccurs="0"/> type="eppcom:clIDType" minOccurs="0"/>
<element name="contact" <element name="contact"
type="domain:contactType" type="domain:contactType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<element name="ns" <element name="ns"
type="domain:nsType" minOccurs="0"/> type="domain:nsType" minOccurs="0"/>
<element name="clID" <element name="clID"
type="eppcom:clIDType"/> type="eppcom:clIDType"/>
<element name="crRr" <element name="crRr"
type="rde:rrType" minOccurs="0"/> type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="crDate" <element name="crDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="exDate" <element name="exDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="upRr" <element name="upRr"
type="rde:rrType" minOccurs="0"/> type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="upDate" <element name="upDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="secDNS" <element name="secDNS"
type="secDNS:dsOrKeyType" minOccurs="0"/> type="secDNS:dsOrKeyType" minOccurs="0"/>
<element name="trDate" <element name="trDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="trnData" <element name="trnData"
type="rdeDomain:transferDataType" type="rdeDomain:transferDataType"
minOccurs="0"/> minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="transferDataType"> <complexType name="transferDataType">
<sequence> <sequence>
<element name="trStatus" <element name="trStatus"
type="eppcom:trStatusType"/> type="eppcom:trStatusType"/>
<element name="reRr" <element name="reRr"
type="rde:rrType"/> type="rdeDnrdCommon:rrType"/>
<element name="reDate" <element name="reDate"
type="dateTime"/> type="dateTime"/>
<element name="acRr" <element name="acRr"
type="rde:rrType"/> type="rdeDnrdCommon:rrType"/>
<element name="acDate" <element name="acDate"
type="dateTime"/> type="dateTime"/>
<element name="exDate" <element name="exDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- Delete Type --> <!-- Delete Type -->
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
skipping to change at page 98, line 31 skipping to change at page 98, line 50
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
schemaLocation="eppcom-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:domain-1.0"/>
<import namespace="urn:ietf:params:xml:ns:domain-1.0" <import namespace="urn:ietf:params:xml:ns:secDNS-1.1"/>
schemaLocation="domain-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:rgp-1.0"/>
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1" <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
schemaLocation="secDNS-1.1.xsd"/> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rgp-1.0"
schemaLocation="rgp-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"
schemaLocation="rde-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
schemaLocation="rdeCsv-1.0.xsd"/>
<annotation> <annotation>
<documentation> <documentation>
Domain Name Comma-Separated Values (CSV) Object Domain Name Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
skipping to change at page 102, line 19 skipping to change at page 102, line 31
9.4. RDE Host Object 9.4. RDE Host Object
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeHost-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0" xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:host-1.0"/> <import namespace="urn:ietf:params:xml:ns:host-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"/>
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow Host provisioning schema Registry Data Escrow Host provisioning schema
</documentation> </documentation>
</annotation> </annotation>
<element name="abstractHost" type="rdeHost:abstractContentType" <element name="abstractHost" type="rdeHost:abstractContentType"
substitutionGroup="rde:content" abstract="true"/> substitutionGroup="rde:content" abstract="true"/>
<element name="host" substitutionGroup="rdeHost:abstractHost" /> <element name="host" substitutionGroup="rdeHost:abstractHost" />
skipping to change at page 103, line 4 skipping to change at page 103, line 19
<sequence> <sequence>
<element name="name" <element name="name"
type="eppcom:labelType"/> type="eppcom:labelType"/>
<element name="roid" <element name="roid"
type="eppcom:roidType"/> type="eppcom:roidType"/>
<element name="status" <element name="status"
type="host:statusType" maxOccurs="7"/> type="host:statusType" maxOccurs="7"/>
<element name="addr" <element name="addr"
type="host:addrType" minOccurs="0" type="host:addrType" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<element name="clID" <element name="clID"
type="eppcom:clIDType"/> type="eppcom:clIDType"/>
<element name="crRr" <element name="crRr"
type="rde:rrType" minOccurs="0"/> type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="crDate" <element name="crDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="upRr" <element name="upRr"
type="rde:rrType" minOccurs="0"/> type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="upDate" <element name="upDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="trDate" <element name="trDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- Delete Type --> <!-- Delete Type -->
skipping to change at page 104, line 6 skipping to change at page 104, line 22
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:host="urn:ietf:params:xml:ns:host-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
schemaLocation="eppcom-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:host-1.0"/>
<import namespace="urn:ietf:params:xml:ns:host-1.0" <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
schemaLocation="host-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"
schemaLocation="rde-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
schemaLocation="rdeCsv-1.0.xsd"/>
<annotation> <annotation>
<documentation> <documentation>
Host Comma-Separated Values (CSV) Object Host Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
skipping to change at page 106, line 18 skipping to change at page 106, line 31
9.6. RDE Contact Object 9.6. RDE Contact Object
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeContact-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeContact-1.0"
xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0" xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- Import common element types. --> <!-- Import common element types. -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:contact-1.0"/> <import namespace="urn:ietf:params:xml:ns:contact-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"/>
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow contact provisioning schema Registry Data Escrow contact provisioning schema
</documentation> </documentation>
</annotation> </annotation>
<element name="abstractContact" <element name="abstractContact"
type="rdeContact:abstractContentType" type="rdeContact:abstractContentType"
substitutionGroup="rde:content" abstract="true"/> substitutionGroup="rde:content" abstract="true"/>
skipping to change at page 107, line 14 skipping to change at page 107, line 29
type="contact:postalInfoType" maxOccurs="2"/> type="contact:postalInfoType" maxOccurs="2"/>
<element name="voice" <element name="voice"
type="contact:e164Type" minOccurs="0"/> type="contact:e164Type" minOccurs="0"/>
<element name="fax" <element name="fax"
type="contact:e164Type" minOccurs="0"/> type="contact:e164Type" minOccurs="0"/>
<element name="email" <element name="email"
type="eppcom:minTokenType"/> type="eppcom:minTokenType"/>
<element name="clID" <element name="clID"
type="eppcom:clIDType"/> type="eppcom:clIDType"/>
<element name="crRr" <element name="crRr"
type="rde:rrType" minOccurs="0"/> type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="crDate" <element name="crDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="upRr" <element name="upRr"
type="rde:rrType" minOccurs="0"/> type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="upDate" <element name="upDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="trDate" <element name="trDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="trnData" <element name="trnData"
type="rdeContact:transferDataType" minOccurs="0"/> type="rdeContact:transferDataType" minOccurs="0"/>
<element name="disclose" <element name="disclose"
type="contact:discloseType" minOccurs="0"/> type="contact:discloseType" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="transferDataType"> <complexType name="transferDataType">
<sequence> <sequence>
<element name="trStatus" type="eppcom:trStatusType"/> <element name="trStatus" type="eppcom:trStatusType"/>
<element name="reRr" type="rde:rrType"/> <element name="reRr" type="rdeDnrdCommon:rrType"/>
<element name="reDate" type="dateTime"/> <element name="reDate" type="dateTime"/>
<element name="acRr" type="rde:rrType"/> <element name="acRr" type="rdeDnrdCommon:rrType"/>
<element name="acDate" type="dateTime"/> <element name="acDate" type="dateTime"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- Delete Type --> <!-- Delete Type -->
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element name="id" <element name="id"
skipping to change at page 108, line 28 skipping to change at page 108, line 41
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:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types. Import common element types.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
schemaLocation="eppcom-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:contact-1.0"/>
<import namespace="urn:ietf:params:xml:ns:contact-1.0" <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
schemaLocation="contact-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"
schemaLocation="rde-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
schemaLocation="rdeCsv-1.0.xsd"/>
<annotation> <annotation>
<documentation> <documentation>
Contact Comma-Separated Values (CSV) Object Contact Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
<element name="contents" type="csvContact:contentType" <element name="contents" type="csvContact:contentType"
substitutionGroup="rde:content"/> substitutionGroup="rde:content"/>
<complexType name="contentType"> <complexType name="contentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
skipping to change at page 118, line 8 skipping to change at page 118, line 16
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types. Import common element types.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
schemaLocation="eppcom-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:domain-1.0"/>
<import namespace="urn:ietf:params:xml:ns:domain-1.0" <import namespace="urn:ietf:params:xml:ns:contact-1.0"/>
schemaLocation="domain-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:contact-1.0" <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
schemaLocation="contact-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"
schemaLocation="rde-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
schemaLocation="rdeCsv-1.0.xsd"/>
<annotation> <annotation>
<documentation> <documentation>
Registar Comma-Separated Values (CSV) Object Registar Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
skipping to change at page 122, line 8 skipping to change at page 122, line 12
<schema targetNamespace="urn:ietf:params:xml:ns:csvIDN-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvIDN-1.0"
xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0" xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-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="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:rde-1.0" <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
schemaLocation="rde-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
schemaLocation="rdeCsv-1.0.xsd"/>
<annotation> <annotation>
<documentation> <documentation>
IDN Language Comma-Separated Values (CSV) Object IDN Language Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
skipping to change at page 126, line 14 skipping to change at page 126, line 21
xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0" xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-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:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:rde-1.0" <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
schemaLocation="rde-1.0.xsd"/> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" <import namespace="urn:ietf:params:xml:ns:rdeNNDN-1.0"/>
schemaLocation="rdeCsv-1.0.xsd"/>
<import namespace="urn:ietf:params:xml:ns:rdeNNDN-1.0"
schemaLocation="rde-nndn-1.0.xsd"/>
<annotation> <annotation>
<documentation> <documentation>
NNDN (NNDN's not domain name) (CSV) Object NNDN (NNDN's not domain name) (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
skipping to change at page 130, line 5 skipping to change at page 130, line 5
<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>
</simpleContent> </simpleContent>
</complexType> </complexType>
</schema> </schema>
END END
9.17. DNRD Common Objects
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<annotation>
<documentation>
Data Escrow Deposit Common Objects schema
</documentation>
</annotation>
<complexType name="rrType">
<simpleContent>
<extension base="eppcom:clIDType">
<attribute name="client" type="eppcom:clIDType"/>
</extension>
</simpleContent>
</complexType>
</schema>
END
10. Internationalization Considerations 10. Internationalization Considerations
Data Escrow deposits are represented in XML, which provides native Data Escrow deposits are represented in XML, which provides native
support for encoding information using the Unicode character set and support for encoding information using the Unicode character set and
its more compact representations including UTF-8. Conformant XML its more compact representations including UTF-8. Conformant XML
processors recognize both UTF-8 and UTF-16. Though XML includes processors recognize both UTF-8 and UTF-16. Though XML includes
provisions to identify and use other character encodings through use provisions to identify and use other character encodings through use
of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is
RECOMMENDED. RECOMMENDED.
11. IANA Considerations 11. IANA Considerations
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. Fourteen conforming to a registry mechanism described in [RFC3688]. Fourteen
URI assignments have been registered by the IANA. URI assignments have been registered by the IANA.
Registration request for the RDE CSV namespace: Registration request for the RDE CSV namespace:
URI: urn:ietf:params:xml:ns:rdeCsv-1.0 URI: urn:ietf:params:xml:ns:rdeCsv-1.0
Registrant Contact: IESG <regext@ietf.org>
Registrant Contact: IETF <regext@ietf.org> Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE CSV XML schema: Registration request for the RDE CSV XML schema:
URI: urn:ietf:params:xml:schema:rdeCsv-1.0 URI: urn:ietf:params:xml:schema:rdeCsv-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.1 of this document. See section Section 9.1 of this document.
Registration request for the RDE domain namespace: Registration request for the RDE domain namespace:
URI: urn:ietf:params:xml:ns:rdeDomain-1.0 URI: urn:ietf:params:xml:ns:rdeDomain-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE domain XML schema: Registration request for the RDE domain XML schema:
URI: urn:ietf:params:xml:schema:rdeDomain-1.0 URI: urn:ietf:params:xml:schema:rdeDomain-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.2 of this document. See section Section 9.2 of this document.
Registration request for the CSV domain namespace: Registration request for the CSV domain namespace:
URI: urn:ietf:params:xml:ns:csvDomain-1.0 URI: urn:ietf:params:xml:ns:csvDomain-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV domain XML schema: Registration request for the CSV domain XML schema:
URI: urn:ietf:params:xml:schema:csvDomain-1.0 URI: urn:ietf:params:xml:schema:csvDomain-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.3 of this document. See section Section 9.3 of this document.
Registration request for the RDE host namespace: Registration request for the RDE host namespace:
URI: urn:ietf:params:xml:ns:rdeHost-1.0 URI: urn:ietf:params:xml:ns:rdeHost-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE host XML schema: Registration request for the RDE host XML schema:
URI: urn:ietf:params:xml:schema:rdeHost-1.0 URI: urn:ietf:params:xml:schema:rdeHost-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.4 of this document. See section Section 9.4 of this document.
Registration request for the CSV host namespace: Registration request for the CSV host namespace:
URI: urn:ietf:params:xml:ns:csvHost-1.0 URI: urn:ietf:params:xml:ns:csvHost-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV host XML schema: Registration request for the CSV host XML schema:
URI: urn:ietf:params:xml:schema:csvHost-1.0 URI: urn:ietf:params:xml:schema:csvHost-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.5 of this document. See section Section 9.5 of this document.
Registration request for the RDE contact namespace: Registration request for the RDE contact namespace:
URI: urn:ietf:params:xml:ns:rdeContact-1.0 URI: urn:ietf:params:xml:ns:rdeContact-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE contact XML schema: Registration request for the RDE contact XML schema:
URI: urn:ietf:params:xml:schema:rdeContact-1.0 URI: urn:ietf:params:xml:schema:rdeContact-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.6 of this document. See section Section 9.6 of this document.
Registration request for the CSV contact namespace: Registration request for the CSV contact namespace:
URI: urn:ietf:params:xml:ns:csvContact-1.0 URI: urn:ietf:params:xml:ns:csvContact-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV contact XML schema: Registration request for the CSV contact XML schema:
URI: urn:ietf:params:xml:schema:csvContact-1.0 URI: urn:ietf:params:xml:schema:csvContact-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.7 of this document. See section Section 9.7 of this document.
Registration request for the RDE registrar namespace: Registration request for the RDE registrar namespace:
URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE registrar XML schema: Registration request for the RDE registrar XML schema:
URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.8 of this document. See section Section 9.8 of this document.
Registration request for the CSV registrar namespace: Registration request for the CSV registrar namespace:
URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV registrar XML schema: Registration request for the CSV registrar XML schema:
URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.9 of this document. See section Section 9.9 of this document.
Registration request for the RDE IDN namespace: Registration request for the RDE IDN namespace:
URI: urn:ietf:params:xml:ns:rdeIDN-1.0 URI: urn:ietf:params:xml:ns:rdeIDN-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE IDN XML schema: Registration request for the RDE IDN XML schema:
URI: urn:ietf:params:xml:schema:rdeIDN-1.0 URI: urn:ietf:params:xml:schema:rdeIDN-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.10 of this document. See section Section 9.10 of this document.
Registration request for the CSV IDN namespace: Registration request for the CSV IDN namespace:
URI: urn:ietf:params:xml:ns:csvIDN-1.0 URI: urn:ietf:params:xml:ns:csvIDN-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV IDN XML schema: Registration request for the CSV IDN XML schema:
URI: urn:ietf:params:xml:schema:csvIDN-1.0 URI: urn:ietf:params:xml:schema:csvIDN-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.11 of this document. See section Section 9.11 of this document.
Registration request for the RDE EPP parameters namespace:
URI: urn:ietf:params:xml:ns:rdeEppParams-1.0
Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE EPP parameters XML schema:
URI: urn:ietf:params:xml:schema:rdeEppParams-1.0
Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.12 of this document.
Registration request for the RDE NNDN namespace: Registration request for the RDE NNDN namespace:
URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE NNDN XML schema: Registration request for the RDE NNDN XML schema:
URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.13 of this document. See section Section 9.13 of this document.
Registration request for the CSV NNDN namespace: Registration request for the CSV NNDN namespace:
URI: urn:ietf:params:xml:ns:csvNNDN-1.0 URI: urn:ietf:params:xml:ns:csvNNDN-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV NNDN XML schema: Registration request for the CSV NNDN XML schema:
URI: urn:ietf:params:xml:schema:csvNNDN-1.0 URI: urn:ietf:params:xml:schema:csvNNDN-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.14 of this document. See section Section 9.14 of this document.
Registration request for the RDE EPP parameters namespace: Registration request for the RDE Policy namespace:
URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 URI: urn:ietf:params:xml:ns:rdePolicy-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE EPP parameters XML schema: Registration request for the RDE Policy XML schema:
URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 URI: urn:ietf:params:xml:ns:rdePolicy-1.0
Registrant Contact: IETF <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
See section Section 9.12 of this document. Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.15 of this document.
Registration request for the RDE Header namespace:
URI: urn:ietf:params:xml:ns:rdeHeader-1.0
Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE Header XML schema:
URI: urn:ietf:params:xml:ns:rdeHeader-1.0
Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.16 of this document.
Registration request for the RDE Common Objects namespace:
URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0
Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE Common Objects XML schema:
URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0
Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC
after IANA records it.
See section Section 9.17 of this document.
12. Implementation Status 12. Implementation Status
Note to RFC Editor: Please remove this section and the reference to Note to RFC Editor: Please remove this section and the reference to
RFC 7942 [RFC7942] before publication. RFC 7942 [RFC7942] before publication.
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in RFC 7942 Internet-Draft, and is based on a proposal described in RFC 7942
[RFC7942]. The description of implementations in this section is [RFC7942]. The description of implementations in this section is
skipping to change at page 136, line 4 skipping to change at page 139, line 35
of Registry Service Provider transitions using data files that of Registry Service Provider transitions using data files that
conform to this specification. conform to this specification.
Level of maturity: production. Level of maturity: production.
Coverage: all aspects of this specification are implemented. Coverage: all aspects of this specification are implemented.
Version compatibility: versions 03 - 08 are known to be implemented. Version compatibility: versions 03 - 08 are known to be implemented.
Contact: gustavo.lozano@icann.org Contact: gustavo.lozano@icann.org
URL: https://www.icann.org/resources/pages/registries/registries- URL: https://www.icann.org/resources/pages/registries/registries-
agreements-en agreements-en
13. Security Considerations 13. Security Considerations
This specification does not define the security mechanisms to be used This specification does not define the security mechanisms to be used
in the transmission of the data escrow deposits, since it only in the transmission of the data escrow deposits, since it only
specifies the minimum necessary to enable the rebuilding of a specifies the minimum necessary to enable the rebuilding of a
Registry from deposits without intervention from the original registry from deposits without intervention from the original
Registry. registry.
Depending on local policies, some elements or, most likely, the whole Depending on local policies, some elements or, most likely, the whole
deposit will be considered confidential. As such, the Registry deposit will be considered confidential. As such, the registry
transmitting the data to the Escrow Agent should take all the transmitting the data to the escrow agent SHOULD take all the
necessary precautions such as encrypting the data itself and/or the necessary precautions such as encrypting the data itself and/or the
transport channel to avoid inadvertent disclosure of private data. transport channel to avoid inadvertent disclosure of private data.
Authentication of the parties passing data escrow deposit files is Authentication of the parties passing data escrow deposit files is
also of the utmost importance. The Escrow Agent SHOULD properly also of the utmost importance. The escrow agent MUST properly
authenticate the identity of the Registry before accepting data authenticate the identity of the registry before accepting data
escrow deposits. In a similar manner, the Registry SHOULD escrow deposits. In a similar manner, the registry MUST authenticate
authenticate the identity of the Escrow Agent before submitting any 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 MUST 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 that the file was transmitted RECOMMENDED to ensure not only that the file was transmitted
correctly from the Registry, but also that the contents are correctly from the registry, but also that the contents are
"meaningful". "meaningful".
Note: if Transport Layer Security (TLS) is used when providing an
escrow services, the recommendations in [RFC7525] MUST be
implemented.
14. Privacy Considerations 14. Privacy Considerations
This specification defines a format that may be used to escrow This specification defines a format that may be used to escrow
personal data. The process of data escrow is governed by a legal personal data. The process of data escrow is governed by a legal
document agreed by the parties, and such legal document must regulate document agreed by the parties, and such legal document must ensure
the particularities regarding the protection of personal data. that privacy-sensitive and/or personal data receives the required
protection.
15. Acknowledgments 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 Special suggestions that have been incorporated into this document
were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc
Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen
Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul
skipping to change at page 144, line 32 skipping to change at page 148, line 25
4. Moved [RFC0791] and [RFC4291] to the Normative References 4. Moved [RFC0791] and [RFC4291] to the Normative References
section. section.
16.18. Changes REGEXT 05 to REGEXT 06 16.18. Changes REGEXT 05 to REGEXT 06
1. Changes based on the feedback provided here: 1. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/ https://mailarchive.ietf.org/arch/msg/regext/
nA8eTYIrXJ44_6ullQlRLW6T74s nA8eTYIrXJ44_6ullQlRLW6T74s
16.19. Changes REGEXT 06 to REGEXT 07
1. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/hDLz2ym4oR-ukA4Fm-
QJ8FzaxxE
2. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/780Xw-
z1RMRb79nmZ6ABmRTo1fU
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 171, line 28 skipping to change at page 175, line 30
</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-04 (work in progress), January ietf-regext-data-escrow-08 (work in progress), April 2020.
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.
skipping to change at page 173, line 5 skipping to change at page 177, line 5
[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>.
[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>.
[W3C.REC-xml-20081126]
Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
Edition) REC-xml-20081126", November 2008,
<https://www.w3.org/TR/2008/REC-xml-20081126/>.
[W3C.REC-xmlschema-1-20041028]
Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,
"XML Schema Part 1: Structures Second Edition REC-
xmlschema-1-20041028", October 2004,
<https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/>.
[W3C.REC-xmlschema-2-20041028]
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
Second Edition REC-xmlschema-2-20041028", October 2004,
<https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/>.
21.2. Informative References 21.2. Informative References
[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>.
[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
2015, <https://www.rfc-editor.org/info/rfc7525>.
[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>.
[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/idn-vip-integrated- <http://www.icann.org/en/topics/idn/idn-vip-integrated-
 End of changes. 90 change blocks. 
158 lines changed or deleted 362 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/