draft-ietf-regext-dnrd-objects-mapping-03.txt   draft-ietf-regext-dnrd-objects-mapping-04.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: May 29, 2020 C. Thippeswamy Expires: June 18, 2020 C. Thippeswamy
VeriSign VeriSign
Nov 26, 2019 Dec 16, 2019
Domain Name Registration Data (DNRD) Objects Mapping Domain Name Registration Data (DNRD) Objects Mapping
draft-ietf-regext-dnrd-objects-mapping-03 draft-ietf-regext-dnrd-objects-mapping-04
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 May 29, 2020. This Internet-Draft will expire on June 18, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. XML Model . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6
4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . . . . 6
4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 7
4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 7
4.6. CSV Parent Child Relationship . . . . . . . . . . . . . . 6 4.6. Conventions applicable to the CSV Model . . . . . . . . . 7
4.7. CSV elements . . . . . . . . . . . . . . . . . . . . . . 7 5. Object Description . . . . . . . . . . . . . . . . . . . . . 15
4.8. Internationalized and Localized Elements . . . . . . . . 12 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 15
5. Object Description . . . . . . . . . . . . . . . . . . . . . 14 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 34
5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 14 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 44
5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 33 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 62
5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 43 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 70
5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 61 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 74
5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 69 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 79
5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 73 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 81
5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 78 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 81
5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 80 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 84
5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 80 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 83 8. Data escrow agent extended verification process . . . . . . . 85
7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 86
8. Data escrow agent extended verification process . . . . . . . 84 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 86
9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 85 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 96
9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 85 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 99
9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 95 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 104
9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 106
9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 103 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 109
9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 105 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 112
9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 108 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 118
9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 111 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 122
9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 117 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 126
9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 121 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 128
9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 125 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 130
9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 127 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 132
9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 129 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 134
9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 131 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 137
9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 133 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 138
9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 136 10. Internationalization Considerations . . . . . . . . . . . . . 140
9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 137 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 140
10. Internationalization Considerations . . . . . . . . . . . . . 139 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 146
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 139 12.1. Implementation in the gTLD space . . . . . . . . . . . . 146
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 145
12.1. Implementation in the gTLD space . . . . . . . . . . . . 145
13. Security Considerations . . . . . . . . . . . . . . . . . . . 146 13. Security Considerations . . . . . . . . . . . . . . . . . . . 147
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 146 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 147
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 146 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 147
16. Change History . . . . . . . . . . . . . . . . . . . . . . . 147 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 148
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 . . . . . . . . . . . . . . 147 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 148
16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 147 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 148
16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 148 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 149
16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 148 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 149
16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 148 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 149
16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 150 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 151
16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 150 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 151
16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 151 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 152
16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 151 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 152
16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 151 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 152
16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 151 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 152
16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 151 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 152
16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 151 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 152
16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 151 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 152
16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 153 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 154
17. Example of a full deposit using the XML model . . . . . . . . 153 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 154
18. Example of differential deposit using the XML model . . . . . 159 17. Example of a full deposit using the XML model . . . . . . . . 155
19. Example of a full deposit using the CSV model . . . . . . . . 160 18. Example of differential deposit using the XML model . . . . . 160
20. Example of differential deposit using the CSV model . . . . . 169 19. Example of a full deposit using the CSV model . . . . . . . . 162
21. References . . . . . . . . . . . . . . . . . . . . . . . . . 180 20. Example of differential deposit using the CSV model . . . . . 171
21.1. Normative References . . . . . . . . . . . . . . . . . . 180 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 182
21.2. Informative References . . . . . . . . . . . . . . . . . 181 21.1. Normative References . . . . . . . . . . . . . . . . . . 182
21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 182 21.2. Informative References . . . . . . . . . . . . . . . . . 183
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 184
1. Introduction 1. Introduction
This document defines the data escrow structure of the standard set Registry Data Escrow is the process by which a registry periodically
of objects for a Domain Name Registry which include: submits data deposits to a third-party called an escrow agent. These
deposits comprise the minimum data needed by a third-party to resume
operations if the registry cannot function and is unable or unwilling
to facilitate an orderly transfer of service. For example, for a
domain name registry or registrar, the data to be deposited would
include all the objects related to registered domain names, e.g.,
names, contacts, name servers, etc.
The goal of data escrow is higher resiliency of registration
services, for the benefit of Internet users. The beneficiaries of a
registry are not just those registering information there, but all
relying parties that need to identify the owners of objects.
In the context of domain name registries, registration data escrow is
a requirement for generic top-level domains and some country code
top-level domain managers are also currently escrowing data. There
is also a similar requirement for ICANN-accredited domain registrars.
This document defines the standard set of objects for a Domain Name
Registry that uses the Registry Data Escrow Specification described
in [I-D.ietf-regext-data-escrow] for escrow. The set of objects
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]
are fully supported by this document. are fully supported by this document.
o Host: Internet host names that are typically provisioned in a o Host: Internet host names that are typically provisioned in a
Domain Name Registry using the EPP host mapping [RFC5732]. The Domain Name Registry using the EPP host mapping [RFC5732]. The
attributes defined in the EPP host mapping [RFC5732] are fully attributes defined in the EPP host mapping [RFC5732] are fully
supported by this document. supported by this document.
skipping to change at page 4, line 4 skipping to change at page 4, line 24
The attributes defined in the EPP domain name mapping [RFC5731] The attributes defined in the EPP domain name mapping [RFC5731]
are fully supported by this document. are fully supported by this document.
o Host: Internet host names that are typically provisioned in a o Host: Internet host names that are typically provisioned in a
Domain Name Registry using the EPP host mapping [RFC5732]. The Domain Name Registry using the EPP host mapping [RFC5732]. The
attributes defined in the EPP host mapping [RFC5732] are fully attributes defined in the EPP host mapping [RFC5732] are fully
supported by this document. supported by this document.
o Contact: Individual or organization social information provisioned o Contact: Individual or organization social information provisioned
in a Domain Name Registry using the EPP contact mapping [RFC5733]. in a Domain Name Registry using the EPP contact mapping [RFC5733].
The attributes defined in the EPP contact mapping [RFC5733] are The attributes defined in the EPP contact mapping [RFC5733] are
fully supported by this document. fully supported by this document.
o Registrar: The organization that sponsors objects like domains, o Registrar: The organization that sponsors objects like domains,
hosts, and contacts in a Domain Name Registry. hosts, and contacts in a Domain Name Registry.
o NNDN (NNDN's not domain name): A lightweight domain-like object o NNDN (NNDN's not domain name): Domain Name Registries may maintain
that is not linked to a Registrar. domain names without them being persisted as domain objects in the
registry system, for example, a list of reserved names not
available for registration. The NNDN is a lightweight domain-like
object that is used to escrow domain names not maintained as
domain name objects.
This document defines the following pseudo-objects: This document defines the following pseudo-objects:
o IDN Table Reference: Internationalized Domain Names (IDN) included o IDN Table Reference: Internationalized Domain Names (IDN) included
in the Domain Object Data Escrow include references to the IDN in the Domain Object Data Escrow include references to the IDN
Table and Policy used in IDN registration. Table and Policy used in IDN registration.
o EPP parameters: Definition of the specific EPP parameters o EPP parameters: Definition of the specific EPP parameters
supported by the Registry Operator. supported by the Registry Operator.
o Header: Used to specify counters of objects in the database at a o Header: Used to specify counters of objects in the database at a
certain point in time (watermark). certain point in time (watermark).
o Policy: Used to specify OPTIONAL elements from this specification o Policy: Used to specify OPTIONAL elements from this specification
that are REQUIRED based on the business model of the registry. that are REQUIRED based on the business model of the registry.
2. Models 2. Models
This document defines two different models that can be used to This document defines two different models that can be used to
deposit data escrow objects: deposit data escrow objects: XML and CSV.
o XML: The XML model includes all the deposit information (meta-data
and data) in an XML document. The definition of the XML format is
fully defined in the XML schemas. As a convention, the objects
represented using the XML model are referenced using RDE and an
XML namespace that is prefixed with "rde". For example, the
Domain Name object represented using the XML model can be referred
to as the RDE Domain Name with the XML namespace including
rdeDomain (urn:ietf:params:xml:ns:rdeDomain-1.0).
o CSV: The CSV model uses XML to define the data escrow format of
the data contained in referenced Comma-Separated Values (CSV)
files. As a convention, the objects represented using the CSV
model is referenced using CSV and an XML namespace that is
prefixed with "csv". For example, the Domain Name object
represented using the CSV model can be referred to as the CSV
Domain Name with the XML namespace including csvDomain
(urn:ietf:params:xml:ns:csvDomain-1.0).
The data escrow deposit MAY contain a mix of both models but an The data escrow deposit MAY contain a mix of both models but an
object MUST be escrowed only in one model. object MUST be escrowed only in one model.
This document does not suggest the use of a particular model, and
both are equivalent. A Domain Name Registry may choose the model
that is more appropriate for the peculiarities of its systems. For
example, a registry may use the CSV-export functionality of the RDBMS
for escrow; therefore, the CSV model may be more appropriate.
Another registry may use the code developed for EPP to implement
escrow.
2.1. XML Model
XML: The XML model includes all the deposit information (meta-data
and data) in an XML document. The definition of the XML format is
fully defined in the XML schemas. As a convention, the objects
represented using the XML model are referenced using RDE and an XML
namespace that is prefixed with "rde". For example, the Domain Name
object represented using the XML model can be referred to as the RDE
Domain Name with the XML namespace including rdeDomain
(urn:ietf:params:xml:ns:rdeDomain-1.0).
2.2. CSV Model
CSV: The CSV model uses XML to define the data escrow format of the
data contained in referenced Comma-Separated Values (CSV) files. As
a convention, the objects represented using the CSV model is
referenced using CSV and an XML namespace that is prefixed with
"csv". For example, the Domain Name object represented using the CSV
model can be referred to as the CSV Domain Name with the XML
namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0).
3. Terminology 3. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
REGISTRY. In the context of this draft the definition will be REGISTRY. In the context of this draft the definition will be
overloaded (from the definition in the base protocol) to indicate an overloaded (from the definition in the base protocol) to indicate an
skipping to change at page 6, line 28 skipping to change at page 7, line 14
4.4. Checksum 4.4. Checksum
Checksum of the CSV data escrow files MUST use CRC32, that is the Checksum of the CSV data escrow files MUST use CRC32, that is the
algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of
ITU-T recommendation V.42. ITU-T recommendation V.42.
4.5. IP addresses 4.5. IP addresses
IP addresses syntax MUST conform to the text representation of either IP addresses syntax MUST conform to the text representation of either
of, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 Internet Protocol Version 4 [RFC0791] or Internet Protocol Version 6
Addressing Architecture [RFC4291], for IPv6 addresses. [RFC4291].
4.6. CSV Parent Child Relationship 4.6. Conventions applicable to the CSV Model
4.6.1. CSV Parent Child Relationship
The CSV model represents a relational model, where the CSV files The CSV model represents a relational model, where the CSV files
represent relational tables, the fields of the CSV files represent represent relational tables, the fields of the CSV files represent
columns of the tables, and each line of the CSV file represents a columns of the tables, and each line of the CSV file represents a
record. As in a relational model, the CSV files can have record. As in a relational model, the CSV files can have
relationships utilizing primary keys in the parent CSV file relationships utilizing primary keys in the parent CSV file
definitions and foreign keys in the child CSV file definitions for a definitions and foreign keys in the child CSV file definitions for a
1-to-many relationship. The primary keys are not explicitly defined, 1-to-many relationship. The primary keys are not explicitly defined,
but the foreign keys are using the boolean "parent" field attribute but the foreign keys are using the boolean "parent" field attribute
in the child CSV file. The relationships between the CSV files are in the child CSV file. The relationships between the CSV files are
skipping to change at page 7, line 47 skipping to change at page 8, line 43
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="EB9C558E"> cksum="EB9C558E">
sampleStatuses-YYYYMMDD.csv sampleStatuses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvSample:contents> </csvSample:contents>
4.7. CSV elements 4.6.2. CSV elements
4.7.1. <rdeCsv:csv> element
To support a CSV model with the Registry Data Escrow Specification 4.6.2.1. <rdeCsv:csv> element
[1], an element is defined for each object that substitutes for the
<rde:content> element and for the <rde:delete> element, that contains To support the CSV model, an element is defined for each object that
one or more <rdeCsv:csv> elements. For example, the Domain Name substitutes for the <rde:content> element and for the <rde:delete>
Object (Section 5.1) defines the <csvDomain:contents> element, that element, that contains one or more <rdeCsv:csv> elements. For
substitutes for the <rde:content> element, and the example, the Domain Name Object (Section 5.1) defines the
<csvDomain:deletes> element, that substitutes for the <rde:delete> <csvDomain:contents> element, that substitutes for the <rde:content>
element. Both the <csvDomain:contents> element and the element, and the <csvDomain:deletes> element, that substitutes for
<csvDomain:deletes> elements contain one or more <rdeCsv:csv> the <rde:delete> element. Both the <csvDomain:contents> element and
the <csvDomain:deletes> elements contain one or more <rdeCsv:csv>
elements. The <rdeCsv:csv> element has the following child elements: elements. The <rdeCsv:csv> element has the following child elements:
<rdeCsv:fields> Ordered list of CSV fields used in the CSV files. <rdeCsv:fields> Ordered list of CSV fields used in the CSV files.
There is one or more child elements that substitute for the There is one or more child elements that substitute for the
<rdeCsv:field> abstract element. Each element defines the format <rdeCsv:field> abstract element. Each element defines the format
of the CSV field contained in the CSV files. The <rdeCsv:field> of the CSV field contained in the CSV files. The <rdeCsv:field>
elements support the "type" attribute that defines the XML simple elements support the "type" attribute that defines the XML simple
data type of the field element. The <rdeCsv:field> elements data type of the field element. The <rdeCsv:field> elements
support the "isRequired" attribute, with a default value of support the "isRequired" attribute, with a default value of
"false", when set to "true" indicates that the field must be non- "false", when set to "true" indicates that the field must be non-
empty in the CSV files and when set to "false" indicates that the empty in the CSV files and when set to "false" indicates that the
field MAY be empty in the CSV files. The "isRequired" attribute field MAY be empty in the CSV files. The "isRequired" attribute
MAY be specifically set for the field elements within the XML MAY be specifically set for the field elements within the XML
schema and MAY be overridden when specifying the fields under the schema and MAY be overridden when specifying the fields under the
<rdeCsv:fields> element. The <rdeCsv:field> element supports an <rdeCsv:fields> element. The <rdeCsv:field> element supports an
OPTIONAL "parent" attribute that identifies the field as a OPTIONAL "parent" attribute that identifies the field as a
reference to a parent object, as defined in CSV Parent Child reference to a parent object, as defined in CSV Parent Child
Relationship (Section 4.6). For example, the <rdeCsv:csv Relationship (Section 4.6.1). For example, the <rdeCsv:csv
name="domainStatuses"> <csvDomain:fName> field SHOULD set the name="domainStatuses"> <csvDomain:fName> field SHOULD set the
"parent" attribute to "true" to identify it as the parent domain "parent" attribute to "true" to identify it as the parent domain
name of the domain status. name of the domain status.
<rdeCsv:files> A list of one or more CSV files using the <rdeCsv:files> A list of one or more CSV files using the
<rdeCsv:file> child element. The <rdeCsv:file> child element <rdeCsv:file> child element. The <rdeCsv:file> child element
defines a reference to the CSV file name and has the following defines a reference to the CSV file name and has the following
optional attributes: optional attributes:
compression If the CSV file is compressed, the "compression" compression If the CSV file is compressed, the "compression"
skipping to change at page 9, line 50 skipping to change at page 10, line 40
domain-YYYYMMDD.csv domain-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
The following is example of the "domain-YYYYMMDD.csv" file with one The following is example of the "domain-YYYYMMDD.csv" file with one
record matching the <rdeCsv:fields> definition. record matching the <rdeCsv:fields> definition.
domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX,
clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z
The following is an example of the <csvDomain:deletes> <rdeCsv:csv> The following is an example of the <csvDomain:deletes> <rdeCsv:csv>
element for domain name records. element for domain name records.
<csvDomain:deletes> <csvDomain:deletes>
... ...
<rdeCsv:csv name="domain"> <rdeCsv:csv name="domain">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
skipping to change at page 10, line 26 skipping to change at page 11, line 26
domain-delete-YYYYMMDD.csv domain-delete-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:deletes> </csvDomain:deletes>
The following is example of the "domain-delete-YYYYMMDD.csv" file The following is example of the "domain-delete-YYYYMMDD.csv" file
with three records that matches the single <csvDomain:fName> field. with three records that matches the single <csvDomain:fName> field.
domain1.test domain1.example
domain2.test domain2.example
domainN.test domainN.example
4.7.2. CSV common field elements 4.6.2.2. CSV common field elements
The <rdeCsv:fields> element defined in the <rdeCsv:csv> element The <rdeCsv:fields> element defined in the <rdeCsv:csv> element
(Section 4.7.1) section has child elements that substitute for the (Section 4.6.2.1) section has child elements that substitute for the
abstract <rdeCsv:field> element. By convention <rdeCsv:field> abstract <rdeCsv:field> element. By convention <rdeCsv:field>
elements include an 'f' prefix to identify them as field definition elements include an 'f' prefix to identify them as field definition
elements. There are a set of common field elements that are used elements. There are a set of common field elements that are used
across multiple data escrow objects. The common field elements are across multiple data escrow objects. The common field elements are
defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and
using the "rdeCsv" sample namespace prefix. The CSV common field using the "rdeCsv" sample namespace prefix. The CSV common field
elements include: elements include:
<rdeCsv:fUName> UTF-8 encoded name field with <rdeCsv:fUName> UTF-8 encoded name field with
type="eppcom:labelType". type="eppcom:labelType".
skipping to change at page 12, line 24 skipping to change at page 13, line 24
<rdeCsv:fPositiveIntegerType> General positive integer field with <rdeCsv:fPositiveIntegerType> General positive integer field with
type="positiveInteger". type="positiveInteger".
<rdeCsv:fUrl> Contains the URL of an object like a registrar object <rdeCsv:fUrl> Contains the URL of an object like a registrar object
with type="anyURI". with type="anyURI".
<rdeCsv:fCustom> Custom field with name attribute that defines the <rdeCsv:fCustom> Custom field with name attribute that defines the
custom field name" with type="token". custom field name" with type="token".
4.8. Internationalized and Localized Elements 4.6.3. Internationalized and Localized Elements
Some elements MAY be provided in either internationalized form Some elements MAY be provided in either internationalized form
("int") or provided in localized form ("loc"). Those elements use a ("int") or provided in localized form ("loc"). Those elements use a
field value or "isLoc" attribute to specify the form used. If an field value or "isLoc" attribute to specify the form used. If an
"isLoc" attribute is used, a value of "true" indicates the use of the "isLoc" attribute is used, a value of "true" indicates the use of the
localized form and a value of "false" indicates the use of the localized form and a value of "false" indicates the use of the
internationalized form. This MAY override the form specified for a internationalized form. This MAY override the form specified for a
parent element. A value of "int" is used to indicate the parent element. A value of "int" is used to indicate the
internationalized form and a value of "loc" is used to indicate the internationalized form and a value of "loc" is used to indicate the
localized form. When the internalized form ("int") is provided, the localized form. When the internalized form ("int") is provided, the
skipping to change at page 18, line 8 skipping to change at page 19, line 8
the registry. For all other status types, the value identifies the registry. For all other status types, the value identifies
the date and time when the request was completed. the date and time when the request was completed.
* An OPTIONAL <exDate> element that contains the end of the * An OPTIONAL <exDate> element that contains the end of the
domain name object's validity period (expiry date) if the domain name object's validity period (expiry date) if the
transfer caused or causes a change in the validity period. transfer caused or causes a change in the validity period.
Example of a domain object: Example of a domain object:
... ...
<rdeDom:domain> <rdeDomain:domain>
<rdeDom:name>example1.test</rdeDom:name> <rdeDomain:name>example1.example</rdeDomain:name>
<rdeDom:roid>Dexample1-TEST</rdeDom:roid> <rdeDomain:roid>Dexample1-TEST</rdeDomain:roid>
<rdeDom:status s="ok"/> <rdeDomain:status s="ok"/>
<rdeDom:registrant>jd1234</rdeDom:registrant> <rdeDomain:registrant>jd1234</rdeDomain:registrant>
<rdeDom:contact type="admin">sh8013</rdeDom:contact> <rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
<rdeDom:contact type="tech">sh8013</rdeDom:contact> <rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
<rdeDom:ns> <rdeDomain:ns>
<domain:hostObj>ns1.example.com</domain:hostObj> <domain:hostObj>ns1.example.com</domain:hostObj>
<domain:hostObj>ns1.example1.test</domain:hostObj> <domain:hostObj>ns1.example1.example</domain:hostObj>
</rdeDom:ns> </rdeDomain:ns>
<rdeDom:clID>RegistrarX</rdeDom:clID> <rdeDomain:clID>RegistrarX</rdeDomain:clID>
<rdeDom:crRr client="jdoe">RegistrarX</rdeDom:crRr> <rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr>
<rdeDom:crDate>1999-04-03T22:00:00.0Z</rdeDom:crDate> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
<rdeDom:exDate>2015-04-03T22:00:00.0Z</rdeDom:exDate> <rdeDomain:exDate>2015-04-03T22:00:00.0Z</rdeDomain:exDate>
</rdeDom:domain> </rdeDomain:domain>
... ...
5.1.1.2. <rdeDomain:delete> object 5.1.1.2. <rdeDomain:delete> object
The <rdeDomain:delete> element contains the fully qualified domain The <rdeDomain:delete> element contains the fully qualified domain
name that was deleted and purged. name that was deleted and purged.
Example of <rdeDomain:delete> object: Example of <rdeDomain:delete> object:
... ...
<rde:deletes> <rde:deletes>
... ...
<rdeDomain:delete> <rdeDomain:delete>
<rdeDomain:name>foo.test</rdeDomain:name> <rdeDomain:name>foo.example</rdeDomain:name>
<rdeDomain:name>bar.test</rdeDomain:name> <rdeDomain:name>bar.example</rdeDomain:name>
</rdeDomain:delete> </rdeDomain:delete>
... ...
</rde:deletes> </rde:deletes>
... ...
5.1.2. CSV Model 5.1.2. CSV Model
For the CSV Model of the domain name object, the <csvDomain:contents> For the CSV Model of the domain name object, the <csvDomain:contents>
child element of the <rde:contents> element is used to hold the new child element of the <rde:contents> element is used to hold the new
or updated domain name objects for the deposit. The or updated domain name objects for the deposit. The
skipping to change at page 20, line 18 skipping to change at page 21, line 18
<rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of: <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of:
<rdeCsv:fClID> Identifier of the sponsoring client with <rdeCsv:fClID> Identifier of the sponsoring client with
isRequired="true". isRequired="true".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with <csvRegistrar:fGurid> Contains the ID assigned by ICANN with
type="positiveInteger". The attribute "isRequired" MUST equal type="positiveInteger". The attribute "isRequired" MUST equal
"true". "true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "domain" <rdeCsv:csv> elements (Section 4.6.2.2), MAY be used in the "domain" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
of the client that created the object. of the client that created the object.
<rdeCsv:fCrID> Identifier of the client that created the domain name <rdeCsv:fCrID> Identifier of the client that created the domain name
object. object.
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the object. of the client that updated the object.
skipping to change at page 21, line 41 skipping to change at page 22, line 41
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding domain-YYYYMMDD.csv file. The file Example of the corresponding domain-YYYYMMDD.csv file. The file
contains four records (two active ASCII domains, original IDN with contains four records (two active ASCII domains, original IDN with
LANG-1 language rules, and variant IDN with LANG-1 language rules). LANG-1 language rules, and variant IDN with LANG-1 language rules).
domain1.test,Ddomain1-TEST,,,registrantid,registrarX,registrarX, domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX,
clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z
domain2.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX,
clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, clientY,1999-04-03T22:00:00.0Z,registrarX,clientY,
2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z
xn--abc123.test,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, xn--abc123.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX,
registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z
xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--abc123.test, xn--abc321.example,Dxnabc321-TEST,LANG-1,xn--abc123.example,
registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z,
registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z
5.1.2.1.2. "domainContacts" CSV File Definition 5.1.2.1.2. "domainContacts" CSV File Definition
The "domainContacts" CSV File Definition defines the fields and CSV The "domainContacts" CSV File Definition defines the fields and CSV
file references used for the domain name object link records to file references used for the domain name object link records to
contact objects, as described in Contact Object (Section 5.3). contact objects, as described in Contact Object (Section 5.3).
The following "csvDomain" field elements, defined for the "domain" The following "csvDomain" field elements, defined for the "domain"
skipping to change at page 23, line 7 skipping to change at page 24, line 7
domainContacts-YYYYMMDD.csv domainContacts-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding domainContacts-YYYYMMDD.csv file. The Example of the corresponding domainContacts-YYYYMMDD.csv file. The
file contains an admin, tech, and billing contact for the four domain file contains an admin, tech, and billing contact for the four domain
names domain1.test, domain2.test, xn--abc123.test and xn-- names domain1.example, domain2.example, xn--abc123.example and xn--
abc321.test. abc321.example.
domain1.test,domain1admin,admin domain1.example,domain1admin,admin
domain1.test,domain1tech,tech domain1.example,domain1tech,tech
domain1.test,domain1billing,billing domain1.example,domain1billing,billing
domain2.test,domain2admin,admin domain2.example,domain2admin,admin
domain2.test,domain2tech,tech domain2.example,domain2tech,tech
domain2.test,domain2billing,billing domain2.example,domain2billing,billing
xn--abc123.test,xnabc123admin,admin xn--abc123.example,xnabc123admin,admin
xn--abc123.test,xnabc123tech,tech xn--abc123.example,xnabc123tech,tech
xn--abc123.test,xnabc123billing,billing xn--abc123.example,xnabc123billing,billing
xn--abc321.test,xnabc123admin,admin xn--abc321.example,xnabc123admin,admin
xn--abc321.test,xnabc123tech,tech xn--abc321.example,xnabc123tech,tech
xn--abc321.test,xnabc123billing,billing xn--abc321.example,xnabc123billing,billing
5.1.2.1.3. "domainStatuses" CSV File Definition 5.1.2.1.3. "domainStatuses" CSV File Definition
The "domainStatuses" CSV File Definition defines the fields and CSV The "domainStatuses" CSV File Definition defines the fields and CSV
file references used for the domain name object statuses. file references used for the domain name object statuses.
The following "csvDomain" fields, defined for the "domain" CSV File The following "csvDomain" fields, defined for the "domain" CSV File
Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvDomain:fName> Domain name of status with isRequired="true". <csvDomain:fName> Domain name of status with isRequired="true".
<csvDomain:fStatus> The status of the domain name with <csvDomain:fStatus> The status of the domain name with
type="domain:statusValueType" and isRequired="true". type="domain:statusValueType" and isRequired="true".
<csvDomain:fRgpStatus> The Registry Grace Period (RGP) status, as a <csvDomain:fRgpStatus> The Registry Grace Period (RGP) status, as a
sub-status of the <csvDomain:fStatus> "pendingDelete" status sub-status of the <csvDomain:fStatus> "pendingDelete" status
value, with type="rgp:statusValueType" as defined in [RFC3915]. value, with type="rgp:statusValueType" as defined in [RFC3915].
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "domainStatuses" elements (Section 4.6.2.2), MAY be used in the "domainStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fStatusDescription> Domain object status description which <rdeCsv:fStatusDescription> Domain object status description which
is free form text describing the rationale for the status. is free form text describing the rationale for the status.
<rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field. <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
Example of a "domainStatuses" <csvDomain:contents> <rdeCsv:csv> Example of a "domainStatuses" <csvDomain:contents> <rdeCsv:csv>
element. element.
skipping to change at page 24, line 31 skipping to change at page 25, line 31
cksum="98D139A3"> cksum="98D139A3">
domainStatuses-YYYYMMDD.csv domainStatuses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding domainStatuses-YYYYMMDD.csv file. The Example of the corresponding domainStatuses-YYYYMMDD.csv file. The
file contains the statuses for the four domain names domain1.test, file contains the statuses for the four domain names domain1.example,
domain2.test, xn--abc123.test and xn--abc321.test. domain2.example, xn--abc123.example and xn--abc321.example.
domain1.test,clientUpdateProhibited,"Disallow update", domain1.example,clientUpdateProhibited,"Disallow update",
en, en,
domain1.test,clientDeleteProhibited,"Disallow delete", domain1.example,clientDeleteProhibited,"Disallow delete",
en, en,
domain2.test,ok,,, domain2.example,ok,,,
xn--abc123.test,ok,,, xn--abc123.example,ok,,,
xn--abc321.test,ok,,, xn--abc321.example,ok,,,
5.1.2.1.4. "domainNameServers" CSV File Definition 5.1.2.1.4. "domainNameServers" CSV File Definition
The "domainNameServers" CSV File Definition defines the fields and The "domainNameServers" CSV File Definition defines the fields and
CSV file references used for the domain name delegated hosts (name CSV file references used for the domain name delegated hosts (name
servers). The "domainNameServers" CSV files define the relationship servers). The "domainNameServers" CSV files define the relationship
between a domain name object and a delegated host. The between a domain name object and a delegated host. The
"domainNameServers" CSV File is used to support the <domain:hostObj> "domainNameServers" CSV File is used to support the <domain:hostObj>
model, defined in [RFC5731]. model, defined in [RFC5731].
skipping to change at page 26, line 7 skipping to change at page 27, line 7
domainNameServers-YYYYMMDD.csv domainNameServers-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding domainNameServers-YYYYMMDD.csv file. Example of the corresponding domainNameServers-YYYYMMDD.csv file.
The file contains the delegated hosts (name servers) for the four The file contains the delegated hosts (name servers) for the four
domain names domain1.test, domain2.test, xn--abc123.test and xn-- domain names domain1.example, domain2.example, xn--abc123.example and
abc321.test referenced via the <rdeCsv:fRoid> field element. xn--abc321.example referenced via the <rdeCsv:fRoid> field element.
domain1.test,Hns1_domain1_test-TEST domain1.example,Hns1_domain1_test-TEST
domain1.test,Hns2_domain1_test-TEST domain1.example,Hns2_domain1_test-TEST
domain2.test,Hns1_domain2_test-TEST domain2.example,Hns1_domain2_test-TEST
domain2.test,Hns2_domain2_test-TEST domain2.example,Hns2_domain2_test-TEST
xn--abc123.test,Hns1_example_test-TEST xn--abc123.example,Hns1_example_test-TEST
xn--abc123.test,Hns2_example_test-TEST xn--abc123.example,Hns2_example_test-TEST
xn--abc321.test,Hns1_example_test-TEST xn--abc321.example,Hns1_example_test-TEST
xn--abc321.test,Hns2_example_test-TEST xn--abc321.example,Hns2_example_test-TEST
5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition
The "domainNameServersAddresses" CSV File Definition defines the The "domainNameServersAddresses" CSV File Definition defines the
fields and CSV file references used for supporting the host as domain fields and CSV file references used for supporting the host as domain
attributes model. attributes model.
The following "csvDomain" fields, defined for the "domain" CSV File The following "csvDomain" fields, defined for the "domain" CSV File
Definition (Section 5.1.2.1.1), MUST be used in the Definition (Section 5.1.2.1.1), MUST be used in the
"domainNameServersAddresses" <rdeCsv:csv> <rdeCsv:fields> element: "domainNameServersAddresses" <rdeCsv:csv> <rdeCsv:fields> element:
skipping to change at page 27, line 31 skipping to change at page 28, line 31
domainNameServersAddresses-YYYYMMDD.csv domainNameServersAddresses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv
file. The file contains the delegated hosts (name servers) for the file. The file contains the delegated hosts (name servers) for the
four domain names domain1.test, domain2.test, xn--abc123.test and four domain names domain1.example, domain2.example, xn--
xn--abc321.test. abc123.example and xn--abc321.example.
domain1.test,ns1.domain1.test,192.0.2.1,v4 domain1.example,ns1.domain1.example,192.0.2.1,v4
domain1.test,ns2.domain1.test,2001:DB8::1,v6 domain1.example,ns2.domain1.example,2001:DB8::1,v6
domain2.test,ns1.domain2.test2,192.0.2.2,v4 domain2.example,ns1.example.net,,
domain2.test,ns2.domain2.test2,2001:DB8::2,v6 domain2.example,ns2.example.net,,
xn--abc123.test,ns1.example.example,, xn--abc123.example,ns1.example.net,,
xn--abc123.test,ns2.example.example,, xn--abc123.example,ns2.example.net,,
xn--abc321.test,ns1.example.example,, xn--abc321.example,ns1.example.net,,
xn--abc321.test,ns2.example.example,, xn--abc321.example,ns2.example.net,,
5.1.2.1.6. "dnssec" CSV File Definition 5.1.2.1.6. "dnssec" CSV File Definition
The "dnssec" CSV File Definition defines the fields and CSV file The "dnssec" CSV File Definition defines the fields and CSV file
references used for the domain name object DNSSEC records (DS or Key references used for the domain name object DNSSEC records (DS or Key
Data). Data).
The following "csvDomain" field elements MUST be used in the "dnssec" The following "csvDomain" field elements MUST be used in the "dnssec"
<rdeCsv:csv> <rdeCsv:fields> element when the DS Data Interface per <rdeCsv:csv> <rdeCsv:fields> element when the DS Data Interface per
[RFC5910] is used: [RFC5910] is used:
skipping to change at page 29, line 31 skipping to change at page 30, line 31
cksum="10ED6C42"> cksum="10ED6C42">
dnssec-ds-YYYYMMDD.csv dnssec-ds-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file
contains two DS records for domain1.test. contains two DS records for domain1.example.
domain1.test,604800,12345,3,1,49FD46E6C4B45C55D4AC domain1.example,604800,12345,3,1,49FD46E6C4B45C55D4AC
domain1.test,604800,12346,3,1,38EC35D5B3A34B44C39B domain1.example,604800,12346,3,1,38EC35D5B3A34B44C39B
Example of a "dnssec" <csvDomain:contents> <rdeCsv:csv> element with Example of a "dnssec" <csvDomain:contents> <rdeCsv:csv> element with
the Key Data Interface of [RFC5910]: the Key Data Interface of [RFC5910]:
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="dnssec"> <rdeCsv:csv name="dnssec">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
<csvDomain:fMaxSigLife/> <csvDomain:fMaxSigLife/>
<csvDomain:fFlags/> <csvDomain:fFlags/>
skipping to change at page 30, line 30 skipping to change at page 31, line 30
cksum="183C3F79"> cksum="183C3F79">
dnssec-key-YYYYMMDD.csv dnssec-key-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file
contains two key records for domain1.test. contains two key records for domain1.example.
domain1.test,604800,257,3,1,AQPJ////4Q== domain1.example,604800,257,3,1,AQPJ////4Q==
domain1.test,604800,257,3,1,AQPJ////4QQQ domain1.example,604800,257,3,1,AQPJ////4QQQ
5.1.2.1.7. "domainTransfer" CSV File Definition 5.1.2.1.7. "domainTransfer" CSV File Definition
The "domainTransfer" CSV File Definition defines the fields and CSV The "domainTransfer" CSV File Definition defines the fields and CSV
file references used for the domain name object pending and completed file references used for the domain name object pending and completed
transfer records. No additional field elements were added for use in transfer records. No additional field elements were added for use in
the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element. the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element.
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "domainTransfer" elements (Section 4.6.2.2), MUST be used in the "domainTransfer"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fTrStatus> State of the most recent transfer request with <rdeCsv:fTrStatus> State of the most recent transfer request with
isRequired="true". isRequired="true".
<rdeCsv:fReRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fReRr> Identifier of the registrar, defined in Section 5.4,
of the client that requested the transfer with isRequired="true". of the client that requested the transfer with isRequired="true".
<rdeCsv:fReDate> Date and time that the transfer was requested with <rdeCsv:fReDate> Date and time that the transfer was requested with
isRequired="true". isRequired="true".
<rdeCsv:fAcRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fAcRr> Identifier of the registrar, defined in Section 5.4,
of the client that should take or took action with of the client that should take or took action with
isRequired="true". isRequired="true".
<rdeCsv:fAcDate> Date and time that the transfer action should be <rdeCsv:fAcDate> Date and time that the transfer action should be
taken or has been taken with isRequired="true". taken or has been taken with isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "domainTransfer" elements (Section 4.6.2.2), MAY be used in the "domainTransfer"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fExDate> Expiration date if the transfer command caused or <rdeCsv:fExDate> Expiration date if the transfer command caused or
causes a change in the validity period. causes a change in the validity period.
<rdeCsv:fReID> Identifier of the client that requested the transfer. <rdeCsv:fReID> Identifier of the client that requested the transfer.
<rdeCsv:fAcID> Identifier of the client that should take or took <rdeCsv:fAcID> Identifier of the client that should take or took
action for transfer. action for transfer.
skipping to change at page 32, line 37 skipping to change at page 33, line 37
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding domainTransfer-YYYYMMDD.csv file. The Example of the corresponding domainTransfer-YYYYMMDD.csv file. The
file contains one domain transfer record with a pending status. file contains one domain transfer record with a pending status.
domain1.test,pending,registrarX,clientY, domain1.example,pending,registrarX,clientY,
2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z,
2016-04-03T22:00:00.0Z 2016-04-03T22:00:00.0Z
5.1.2.2. <csvDomain:deletes> 5.1.2.2. <csvDomain:deletes>
The <csvDomain:deletes> is used to hold the deleted domain name The <csvDomain:deletes> is used to hold the deleted domain name
objects in a differential or incremental deposit. All the domain objects in a differential or incremental deposit. All the domain
name object data is deleted as part of a cascade delete. The name object data is deleted as part of a cascade delete. The
<csvDomain:deletes> is split into separate CSV file definitions using <csvDomain:deletes> is split into separate CSV file definitions using
named <rdeCsv:csv> elements with the "name" attribute. The following named <rdeCsv:csv> elements with the "name" attribute. The following
skipping to change at page 33, line 36 skipping to change at page 34, line 36
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:deletes> </csvDomain:deletes>
... ...
Example of the corresponding domain-delete-YYYYMMDD.csv file. The Example of the corresponding domain-delete-YYYYMMDD.csv file. The
file contains two domain name records. file contains two domain name records.
domain1.test domain1.example
domain2.test domain2.example
5.2. Host Object 5.2. Host Object
The host object is based on the EPP host name mapping in [RFC5732]. The host object is based on the EPP host name mapping in [RFC5732].
The host object supports both the XML Model and the CSV Model, The host object supports both the XML Model and the CSV Model,
defined in Models (Section 2) section. The elements used for both defined in Models (Section 2) section. The elements used for both
models are defined in the following sections. Both the models are defined in the following sections. Both the
<csvHost:contents> and <csvHost:deletes> elements contain one or more <csvHost:contents> and <csvHost:deletes> elements contain one or more
<rdeCsv:csv> elements with a set of named CSV file definitions using <rdeCsv:csv> elements with a set of named CSV file definitions using
the <rdeCsv:csv> "name" attribute. the <rdeCsv:csv> "name" attribute.
skipping to change at page 35, line 18 skipping to change at page 36, line 18
o An OPTIONAL <trDate> element that contains the date and time of o An OPTIONAL <trDate> element that contains the date and time of
the most recent host object successful transfer. This element the most recent host object successful transfer. This element
MUST NOT be present if the domain name object has never been MUST NOT be present if the domain name object has never been
transfered. transfered.
Example of <host> object: Example of <host> object:
... ...
<rdeHost:host> <rdeHost:host>
<rdeHost:name>ns1.example1.test</rdeHost:name> <rdeHost:name>ns1.example1.example</rdeHost:name>
<rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid> <rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid>
<rdeHost:status s="ok"/> <rdeHost:status s="ok"/>
<rdeHost:status s="linked"/> <rdeHost:status s="linked"/>
<rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr>
<rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr>
<rdeHost:addr ip="v6">1080:0:0:0:8:800:200C:417A</rdeHost:addr> <rdeHost:addr ip="v6">1080:0:0:0:8:800:200C:417A</rdeHost:addr>
<rdeHost:clID>RegistrarX</rdeHost:clID> <rdeHost:clID>RegistrarX</rdeHost:clID>
<rdeHost:crRr>RegistrarX</rdeHost:crRr> <rdeHost:crRr>RegistrarX</rdeHost:crRr>
<rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate> <rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate>
<rdeHost:upRr>RegistrarX</rdeHost:upRr> <rdeHost:upRr>RegistrarX</rdeHost:upRr>
skipping to change at page 35, line 47 skipping to change at page 36, line 47
supports host removal based on roid to support SRS systems in which supports host removal based on roid to support SRS systems in which
different hosts with the same fully qualified domain name are active different hosts with the same fully qualified domain name are active
at the same time. at the same time.
Example of <rdeHost:delete> object: Example of <rdeHost:delete> object:
... ...
<rde:deletes> <rde:deletes>
... ...
<rdeHost:delete> <rdeHost:delete>
<rdeHost:name>ns1.example.test</rdeHost:name> <rdeHost:name>ns1.example.example</rdeHost:name>
</rdeHost:delete> </rdeHost:delete>
... ...
</rde:deletes> </rde:deletes>
... ...
5.2.2. CSV Model 5.2.2. CSV Model
For the CSV Model of the host object, the <csvHost:contents> child For the CSV Model of the host object, the <csvHost:contents> child
element of the <rde:contents> element is used to hold the new or element of the <rde:contents> element is used to hold the new or
updated host objects for the deposit. The <csvHost:deletes> child updated host objects for the deposit. The <csvHost:deletes> child
skipping to change at page 36, line 45 skipping to change at page 37, line 45
The "host" CSV File Definition defines the fields and CSV file The "host" CSV File Definition defines the fields and CSV file
references used for the host object records. references used for the host object records.
The following "csvHost" field elements MUST be used in the "host" The following "csvHost" field elements MUST be used in the "host"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvHost:fName> Host name field with type="eppcom:labelType" and <csvHost:fName> Host name field with type="eppcom:labelType" and
isRequired="true". isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "host" <rdeCsv:csv> elements (Section 4.6.2.2), MUST be used in the "host" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fRoid> Repository Object IDentifier (ROID) assigned to the <rdeCsv:fRoid> Repository Object IDentifier (ROID) assigned to the
host object with isRequired="true". host object with isRequired="true".
The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the
"host" <rdeCsv:csv> <rdeCsv:fields> element: "host" <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of: <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of:
skipping to change at page 39, line 9 skipping to change at page 40, line 9
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvHost:contents> </csvHost:contents>
... ...
Example of the corresponding host-YYYYMMDD.csv file. The file Example of the corresponding host-YYYYMMDD.csv file. The file
contains six host records with four being internal hosts and two contains six host records with four being internal hosts and two
being external hosts. being external hosts.
ns1.domain1.test,Hns1_example_test-TEST,registrarX,registrarX, ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns2.domain1.test,Hns2_domain1_test-TEST,registrarX,registrarX, ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns1.domain2.test,Hns1_domain2_test-TEST,registrarX,registrarX, ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns2.domain2.test,Hns2_domain2_test-TEST,registrarX,registrarX, ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns1.example.example,Hns1_example_test-TEST,registrarX,registrarX, ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns2.example.example,Hns2_example_test-TEST,registrarX,registrarX, ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
5.2.2.1.2. "hostStatuses" CSV File Definition 5.2.2.1.2. "hostStatuses" CSV File Definition
The "hostStatuses" CSV File Definition defines the fields and CSV The "hostStatuses" CSV File Definition defines the fields and CSV
file references used for the host object statuses. file references used for the host object statuses.
The following "csvHost" fields, defined for the "host" CSV File The following "csvHost" fields, defined for the "host" CSV File
Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvHost:fStatus> The status of the host with <csvHost:fStatus> The status of the host with
type="host:statusValueType" and isRequired="true". type="host:statusValueType" and isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "hostStatuses" elements (Section 4.6.2.2), MUST be used in the "hostStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fRoid> Host object Registry Object IDentifier (ROID) <rdeCsv:fRoid> Host object Registry Object IDentifier (ROID)
assigned to the host object with isRequired="true". assigned to the host object with isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "hostStatuses" elements (Section 4.6.2.2), MAY be used in the "hostStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fStatusDescription> Host object status description which is <rdeCsv:fStatusDescription> Host object status description which is
free form text describing the rationale for the status. The free form text describing the rationale for the status. The
attribute "isRequired" MUST equal "true". attribute "isRequired" MUST equal "true".
<rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field. <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
Example of a "hostStatuses" <csvHost:contents> <rdeCsv:csv> element. Example of a "hostStatuses" <csvHost:contents> <rdeCsv:csv> element.
skipping to change at page 40, line 35 skipping to change at page 41, line 35
cksum="0DAE0583"> cksum="0DAE0583">
hostStatuses-YYYYMMDD.csv hostStatuses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvHost:contents> </csvHost:contents>
... ...
Example of the corresponding hostStatuses-YYYYMMDD.csv file. The Example of the corresponding hostStatuses-YYYYMMDD.csv file. The
file contains the statuses for the six host names ns1.domain1.test, file contains the statuses for the six host names
ns2.domain1.test, ns1.domain2.test, ns2.domain2.test, ns1.domain1.example, ns2.domain1.example, ns1.domain2.example,
ns1.example.example and ns2.example.example. ns2.domain2.example, ns1.example.net and ns2.example.net.
Hns1_domain1_test-TEST,ok,, Hns1_domain1_test-TEST,ok,,
Hns2_domain1_test-TEST,ok,, Hns2_domain1_test-TEST,ok,,
Hns1_domain2_test-TEST,ok,, Hns1_domain2_test-TEST,ok,,
Hns2_domain2_test-TEST,ok,, Hns2_domain2_test-TEST,ok,,
Hns1_example_test-TEST,ok,, Hns1_example_test-TEST,ok,,
Hns2_example_test-TEST,ok,, Hns2_example_test-TEST,ok,,
5.2.2.1.3. "hostAddresses" CSV File Definition 5.2.2.1.3. "hostAddresses" CSV File Definition
skipping to change at page 41, line 15 skipping to change at page 42, line 15
<csvHost:fAddr> IP addresses associated with the host object with <csvHost:fAddr> IP addresses associated with the host object with
type="host:addrStringType". The attribute "isRequired" MUST equal type="host:addrStringType". The attribute "isRequired" MUST equal
"true". "true".
<csvHost:fAddrVersion> IP addresses version associated with the host <csvHost:fAddrVersion> IP addresses version associated with the host
object with type="host:ipType". "host:ipType" has the enumerated object with type="host:ipType". "host:ipType" has the enumerated
values of "v4" or "v6". The attribute "isRequired" MUST equal values of "v4" or "v6". The attribute "isRequired" MUST equal
"true". "true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "hostAddresses" elements (Section 4.6.2.2), MUST be used in the "hostAddresses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fRoid> Host object Registry Object IDentifier (ROID) <rdeCsv:fRoid> Host object Registry Object IDentifier (ROID)
assigned to the host object with isRequired="true". assigned to the host object with isRequired="true".
Example of a "hostAddresses" <csvHost:contents> <rdeCsv:csv> element. Example of a "hostAddresses" <csvHost:contents> <rdeCsv:csv> element.
... ...
<csvHost:contents> <csvHost:contents>
... ...
skipping to change at page 41, line 44 skipping to change at page 42, line 44
cksum="28B194B0"> cksum="28B194B0">
hostAddresses-YYYYMMDD.csv hostAddresses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvHost:contents> </csvHost:contents>
... ...
Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The
file contains the IP addresses for the host names ns1.domain1.test, file contains the IP addresses for the host names
ns2.domain1.test, ns1.domain2.test and ns2.domain2.test. ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and
ns2.domain2.example.
Hns1_domain1_test-TEST,192.0.2.1,v4 Hns1_domain1_test-TEST,192.0.2.1,v4
Hns2_domain1_test-TEST,2001:DB8::1,v6 Hns2_domain1_test-TEST,2001:DB8::1,v6
Hns1_domain2_test-TEST,192.0.2.2,v4 Hns1_domain2_test-TEST,192.0.2.2,v4
Hns2_domain2_test-TEST,2001:DB8::2,v6 Hns2_domain2_test-TEST,2001:DB8::2,v6
5.2.2.2. <csvHost:deletes> 5.2.2.2. <csvHost:deletes>
The <csvHost:deletes> is used to hold the deleted host objects in a The <csvHost:deletes> is used to hold the deleted host objects in a
differential or incremental deposit. All the host object data is differential or incremental deposit. All the host object data is
deleted as part of a cascade delete. The <csvHost:deletes> is split deleted as part of a cascade delete. The <csvHost:deletes> is split
into separate CSV file definitions using named <rdeCsv:csv> elements into separate CSV file definitions using named <rdeCsv:csv> elements
with the "name" attribute. The following section defines the with the "name" attribute. The following section defines the
supported host deletes CSV file definition. supported host deletes CSV file definition.
5.2.2.2.1. "host" Deletes CSV File Definition 5.2.2.2.1. "host" Deletes CSV File Definition
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "host" <rdeCsv:csv> elements (Section 4.6.2.2), MUST be used in the "host" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fRoid> Repository Object IDentifier (ROID) assigned to the <rdeCsv:fRoid> Repository Object IDentifier (ROID) assigned to the
host object with isRequired="true". host object with isRequired="true".
Example of a "host" <csvHost:deletes> <rdeCsv:csv> element. Example of a "host" <csvHost:deletes> <rdeCsv:csv> element.
... ...
<csvHost:deletes> <csvHost:deletes>
... ...
skipping to change at page 46, line 27 skipping to change at page 47, line 27
<contact:street>123 Example Dr.</contact:street> <contact:street>123 Example Dr.</contact:street>
<contact:street>Suite 100</contact:street> <contact:street>Suite 100</contact:street>
<contact:city>Dulles</contact:city> <contact:city>Dulles</contact:city>
<contact:sp>VA</contact:sp> <contact:sp>VA</contact:sp>
<contact:pc>20166-6503</contact:pc> <contact:pc>20166-6503</contact:pc>
<contact:cc>US</contact:cc> <contact:cc>US</contact:cc>
</contact:addr> </contact:addr>
</rdeContact:postalInfo> </rdeContact:postalInfo>
<rdeContact:voice x="1234">+1.7035555555</rdeContact:voice> <rdeContact:voice x="1234">+1.7035555555</rdeContact:voice>
<rdeContact:fax>+1.7035555556</rdeContact:fax> <rdeContact:fax>+1.7035555556</rdeContact:fax>
<rdeContact:email>jdoe@example.test</rdeContact:email> <rdeContact:email>jdoe@example.example</rdeContact:email>
<rdeContact:clID>RegistrarX</rdeContact:clID> <rdeContact:clID>RegistrarX</rdeContact:clID>
<rdeContact:crRr client="jdoe">RegistrarX</rdeContact:crRr> <rdeContact:crRr client="jdoe">RegistrarX</rdeContact:crRr>
<rdeContact:crDate>2009-09-13T08:01:00.0Z</rdeContact:crDate> <rdeContact:crDate>2009-09-13T08:01:00.0Z</rdeContact:crDate>
<rdeContact:upRr client="jdoe">RegistrarX</rdeContact:upRr> <rdeContact:upRr client="jdoe">RegistrarX</rdeContact:upRr>
<rdeContact:upDate>2009-11-26T09:10:00.0Z</rdeContact:upDate> <rdeContact:upDate>2009-11-26T09:10:00.0Z</rdeContact:upDate>
<rdeContact:trDate>2009-12-03T09:05:00.0Z</rdeContact:trDate> <rdeContact:trDate>2009-12-03T09:05:00.0Z</rdeContact:trDate>
<rdeContact:trnData> <rdeContact:trnData>
<rdeContact:trStatus>pending</rdeContact:trStatus> <rdeContact:trStatus>pending</rdeContact:trStatus>
<rdeContact:reRr client="jstiles">clientW</rdeContact:reRr> <rdeContact:reRr client="jstiles">clientW</rdeContact:reRr>
<rdeContact:reDate>2011-03-08T19:38:00.0Z</rdeContact:reDate> <rdeContact:reDate>2011-03-08T19:38:00.0Z</rdeContact:reDate>
skipping to change at page 48, line 50 skipping to change at page 49, line 50
<rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of: <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of:
<rdeCsv:fClID> Identifier of the sponsoring client with <rdeCsv:fClID> Identifier of the sponsoring client with
isRequired="true". isRequired="true".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with <csvRegistrar:fGurid> Contains the ID assigned by ICANN with
type="positiveInteger". The attribute "isRequired" MUST equal type="positiveInteger". The attribute "isRequired" MUST equal
"true". "true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "contact" <rdeCsv:csv> elements (Section 4.6.2.2), MAY be used in the "contact" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
of the client that created the object. of the client that created the object.
<rdeCsv:fCrID> Identifier of the client that created the contact <rdeCsv:fCrID> Identifier of the client that created the contact
object. object.
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the object. of the client that updated the object.
skipping to change at page 51, line 9 skipping to change at page 52, line 9
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvContact:contents> </csvContact:contents>
... ...
Example of the contact-YYYYMMDD.csv file. The file contains nine Example of the contact-YYYYMMDD.csv file. The file contains nine
object contact records. object contact records.
domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, domain1admin,Cdomain1admin-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, domain1tech,Cdomain1tech-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, domain1billing,Cdomain1billing-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, domain2admin,Cdomain2admin-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, domain2tech,Cdomain2tech-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, domain2billing,Cdomain2billing-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
5.3.2.1.2. "contactStatuses" CSV File Definition 5.3.2.1.2. "contactStatuses" CSV File Definition
The "contactStatuses" CSV File Definition defines the fields and CSV The "contactStatuses" CSV File Definition defines the fields and CSV
file references used for the contact object statuses. file references used for the contact object statuses.
The following "csvContact" field elements, defined for the "contact" The following "csvContact" field elements, defined for the "contact"
CSV File Definition (Section 5.3.2.1.1), MUST be used in the CSV File Definition (Section 5.3.2.1.1), MUST be used in the
"contactStatuses" <rdeCsv:csv> <rdeCsv:fields> element: "contactStatuses" <rdeCsv:csv> <rdeCsv:fields> element:
<csvContact:fId> Server-unique contact identifier of status with <csvContact:fId> Server-unique contact identifier of status with
isRequired="true". isRequired="true".
<csvContact:fStatus> The status of the contact with <csvContact:fStatus> The status of the contact with
type="contact:statusValueType" and isRequired="true". type="contact:statusValueType" and isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "contactStatuses" elements (Section 4.6.2.2), MAY be used in the "contactStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fStatusDescription> The contact object status description <rdeCsv:fStatusDescription> The contact object status description
which is free form text describing the rationale for the status. which is free form text describing the rationale for the status.
<rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field. <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
Example of a "contactStatuses" <csvContact:contents> <rdeCsv:csv> Example of a "contactStatuses" <csvContact:contents> <rdeCsv:csv>
element. element.
skipping to change at page 53, line 29 skipping to change at page 54, line 29
The "contactPostal" CSV File Definition defines the fields and CSV The "contactPostal" CSV File Definition defines the fields and CSV
file references used for the contact postal info object records. file references used for the contact postal info object records.
The following "csvContact" field elements MUST be used in the The following "csvContact" field elements MUST be used in the
"contactPostal" <rdeCsv:csv> <rdeCsv:fields> element: "contactPostal" <rdeCsv:csv> <rdeCsv:fields> element:
<csvContact:fPostalType> Contains the form of the postal-address <csvContact:fPostalType> Contains the form of the postal-address
information with type="contact:postalLineType" and information with type="contact:postalLineType" and
isRequired="true". This field specifies the form ("int" or isRequired="true". This field specifies the form ("int" or
"loc"), as defined in Section 4.8, of the <csvContact:fName>, "loc"), as defined in Section 4.6.3, of the <csvContact:fName>,
<csvContact:fOrg>, <csvContact:fStreet>, <csvContact:fCity>, <csvContact:fOrg>, <csvContact:fStreet>, <csvContact:fCity>,
<csvContact:fSp>, <csvContact:fPc>, <csvContact:fCc> fields. <csvContact:fSp>, <csvContact:fPc>, <csvContact:fCc> fields.
<csvContact:fName> Contains the contact's name of the individual or <csvContact:fName> Contains the contact's name of the individual or
role represented by the contact with type="contact:postalLineType" role represented by the contact with type="contact:postalLineType"
and isRequired="true". An OPTIONAL "isLoc" attribute to used to and isRequired="true". An OPTIONAL "isLoc" attribute to used to
indicate the localized or internationalized form as defined in indicate the localized or internationalized form as defined in
section Section 4.8. section Section 4.6.3.
<csvContact:fStreet> Contains the contact's contact's street address <csvContact:fStreet> Contains the contact's contact's street address
line with type="contact:fPostalLineType". An index attribute is line with type="contact:fPostalLineType". An index attribute is
required to indicate which street address line the field required to indicate which street address line the field
represents with index "0" for the first line and index "2" for the represents with index "0" for the first line and index "2" for the
last line. An OPTIONAL "isLoc" attribute to used to indicate the last line. An OPTIONAL "isLoc" attribute to used to indicate the
localized or internationalized form as defined in section localized or internationalized form as defined in section
Section 4.8. Section 4.6.3.
<csvContact:fCity> Contains the contact's city with <csvContact:fCity> Contains the contact's city with
type="contact:postalLineType" and isRequired="true". An OPTIONAL type="contact:postalLineType" and isRequired="true". An OPTIONAL
"isLoc" attribute to used to indicate the localized or "isLoc" attribute to used to indicate the localized or
internationalized form as defined in section Section 4.8. internationalized form as defined in section Section 4.6.3.
<csvContact:fCc> Contains the contact's country code with <csvContact:fCc> Contains the contact's country code with
type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc"
attribute to used to indicate the localized or internationalized attribute to used to indicate the localized or internationalized
form as defined in section Section 4.8. form as defined in section Section 4.6.3.
The following "csvContact" field elements MAY be used in the The following "csvContact" field elements MAY be used in the
"contactPostal" <rdeCsv:csv> <rdeCsv:fields> element: "contactPostal" <rdeCsv:csv> <rdeCsv:fields> element:
<csvContact:fOrg> Contains the name of the organization with which <csvContact:fOrg> Contains the name of the organization with which
the contact is affiliated with type="contact:optPostalLineType". the contact is affiliated with type="contact:optPostalLineType".
An OPTIONAL "isLoc" attribute to used to indicate the localized or An OPTIONAL "isLoc" attribute to used to indicate the localized or
internationalized form as defined in section Section 4.8. internationalized form as defined in section Section 4.6.3.
<csvContact:fSp> Contains the contact's state or province with <csvContact:fSp> Contains the contact's state or province with
type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute
to used to indicate the localized or internationalized form as to used to indicate the localized or internationalized form as
defined in section Section 4.8. defined in section Section 4.6.3.
<csvContact:fPc> Contains the contact's postal code with <csvContact:fPc> Contains the contact's postal code with
type="contact:pcType". An OPTIONAL "isLoc" attribute to used to type="contact:pcType". An OPTIONAL "isLoc" attribute to used to
indicate the localized or internationalized form as defined in indicate the localized or internationalized form as defined in
section Section 4.8. section Section 4.6.3.
The following "csvContact" fields, defined for the "contact" CSV File The following "csvContact" fields, defined for the "contact" CSV File
Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvContact:fId> Server-unique contact identifier for the contact <csvContact:fId> Server-unique contact identifier for the contact
object with isRequired="true". object with isRequired="true".
Example of a "contactPostal" <csvContact:contents> <rdeCsv:csv> Example of a "contactPostal" <csvContact:contents> <rdeCsv:csv>
element. element.
skipping to change at page 56, line 34 skipping to change at page 57, line 34
xnabc123billing,int,"John Doe","Example Inc.", xnabc123billing,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US "123 Example Dr.","Suite 100",,Reston,VA,20190,US
5.3.2.1.4. "contactTransfer" CSV File Definition 5.3.2.1.4. "contactTransfer" CSV File Definition
The "contactTransfer" CSV File Definition defines the fields and CSV The "contactTransfer" CSV File Definition defines the fields and CSV
file references used for the contact object pending and completed file references used for the contact object pending and completed
transfer records. No additional field elements were added for use in transfer records. No additional field elements were added for use in
the "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element. The the "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element. The
following "rdeCsv" fields, defined in section CSV common field following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "contactTransfer" elements (Section 4.6.2.2), MUST be used in the "contactTransfer"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fTrStatus> State of the most recent transfer request with <rdeCsv:fTrStatus> State of the most recent transfer request with
isRequired="true". isRequired="true".
<rdeCsv:fReRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fReRr> Identifier of the registrar, defined in Section 5.4,
of the client that requested the transfer with isRequired="true". of the client that requested the transfer with isRequired="true".
<rdeCsv:fReDate> Date and time that the transfer was requested with <rdeCsv:fReDate> Date and time that the transfer was requested with
isRequired="true". isRequired="true".
<rdeCsv:fAcRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fAcRr> Identifier of the registrar, defined in Section 5.4,
of the client that should take or took action with of the client that should take or took action with
isRequired="true". isRequired="true".
<rdeCsv:fAcDate> Date and time that the transfer action should be <rdeCsv:fAcDate> Date and time that the transfer action should be
taken or has been taken with isRequired="true". taken or has been taken with isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "contactTransfer" elements (Section 4.6.2.2), MAY be used in the "contactTransfer"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fReID> Identifier of the client that requested the transfer. <rdeCsv:fReID> Identifier of the client that requested the transfer.
<rdeCsv:fAcID> Identifier of the client that should take or took <rdeCsv:fAcID> Identifier of the client that should take or took
action for transfer. action for transfer.
The following "csvContact" fields, defined for the "contact" CSV File The following "csvContact" fields, defined for the "contact" CSV File
Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
skipping to change at page 63, line 33 skipping to change at page 64, line 33
<rdeRegistrar:street>123 Example Dr.</rdeRegistrar:street> <rdeRegistrar:street>123 Example Dr.</rdeRegistrar:street>
<rdeRegistrar:street>Suite 100</rdeRegistrar:street> <rdeRegistrar:street>Suite 100</rdeRegistrar:street>
<rdeRegistrar:city>Dulles</rdeRegistrar:city> <rdeRegistrar:city>Dulles</rdeRegistrar:city>
<rdeRegistrar:sp>VA</rdeRegistrar:sp> <rdeRegistrar:sp>VA</rdeRegistrar:sp>
<rdeRegistrar:pc>20166-6503</rdeRegistrar:pc> <rdeRegistrar:pc>20166-6503</rdeRegistrar:pc>
<rdeRegistrar:cc>US</rdeRegistrar:cc> <rdeRegistrar:cc>US</rdeRegistrar:cc>
</rdeRegistrar:addr> </rdeRegistrar:addr>
</rdeRegistrar:postalInfo> </rdeRegistrar:postalInfo>
<rdeRegistrar:voice x="1234">+1.7035555555</rdeRegistrar:voice> <rdeRegistrar:voice x="1234">+1.7035555555</rdeRegistrar:voice>
<rdeRegistrar:fax>+1.7035555556</rdeRegistrar:fax> <rdeRegistrar:fax>+1.7035555556</rdeRegistrar:fax>
<rdeRegistrar:email>jdoe@example.test</rdeRegistrar:email> <rdeRegistrar:email>jdoe@example.example</rdeRegistrar:email>
<rdeRegistrar:url>http://www.example.test</rdeRegistrar:url> <rdeRegistrar:url>http://www.example.example</rdeRegistrar:url>
<rdeRegistrar:whoisInfo> <rdeRegistrar:whoisInfo>
<rdeRegistrar:name>whois.example.test</rdeRegistrar:name> <rdeRegistrar:name>whois.example.example</rdeRegistrar:name>
<rdeRegistrar:url>http://whois.example.test</rdeRegistrar:url> <rdeRegistrar:url>http://whois.example.example</rdeRegistrar:url>
</rdeRegistrar:whoisInfo> </rdeRegistrar:whoisInfo>
<rdeRegistrar:crDate>2005-04-23T11:49:00.0Z</rdeRegistrar:crDate> <rdeRegistrar:crDate>2005-04-23T11:49:00.0Z</rdeRegistrar:crDate>
<rdeRegistrar:upDate>2009-02-17T17:51:00.0Z</rdeRegistrar:upDate> <rdeRegistrar:upDate>2009-02-17T17:51:00.0Z</rdeRegistrar:upDate>
</rdeRegistrar:registrar> </rdeRegistrar:registrar>
... ...
5.4.1.2. <rdeRegistrar:delete> object 5.4.1.2. <rdeRegistrar:delete> object
The <rdeRegistrar:delete> element contains the id of a registrar that The <rdeRegistrar:delete> element contains the id of a registrar that
was deleted. was deleted.
skipping to change at page 65, line 41 skipping to change at page 66, line 41
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with <csvRegistrar:fGurid> Contains the ID assigned by ICANN with
type="positiveInteger". This field is included in this section in type="positiveInteger". This field is included in this section in
addition to the section above to support optionally providing the addition to the section above to support optionally providing the
<csvRegistrar:fGurid> field when the <csvRegistrar:fId> field is <csvRegistrar:fGurid> field when the <csvRegistrar:fId> field is
used. used.
<csvRegistrar:fWhoisUrl> Contains the Whois URL of the registrar <csvRegistrar:fWhoisUrl> Contains the Whois URL of the registrar
with type="anyURI". with type="anyURI".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "registrar" <rdeCsv:csv> elements (Section 4.6.2.2), MAY be used in the "registrar"
<rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fCrDate> Created date and time of the registrar object. <rdeCsv:fCrDate> Created date and time of the registrar object.
<rdeCsv:fUpDate> Date and time of the last update to the registrar <rdeCsv:fUpDate> Date and time of the last update to the registrar
object. object.
<rdeCsv:fUrl> URL for the registrar web home page. <rdeCsv:fUrl> URL for the registrar web home page.
The following "csvContact" fields, defined in section Contact Object The following "csvContact" fields, defined in section Contact Object
(Section 5.3), MAY be used in the "registrar" <rdeCsv:csv> (Section 5.3), MAY be used in the "registrar" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<csvContact:fStreet> Registrar street address line with an "index" <csvContact:fStreet> Registrar street address line with an "index"
attribute that represents the order of the street address line attribute that represents the order of the street address line
from "0" to "2". An OPTIONAL "isLoc" attribute that is used to from "0" to "2". An OPTIONAL "isLoc" attribute that is used to
indicate the localized or internationalized form, as defined in indicate the localized or internationalized form, as defined in
Section 4.8. Section 4.6.3.
<csvContact:fCity> Registrar city with an OPTIONAL "isLoc" attribute <csvContact:fCity> Registrar city with an OPTIONAL "isLoc" attribute
that is used to indicate the localized or internationalized form, that is used to indicate the localized or internationalized form,
as defined in Section 4.8. as defined in Section 4.6.3.
<csvContact:fCc> Registrar country code with an OPTIONAL "isLoc" <csvContact:fCc> Registrar country code with an OPTIONAL "isLoc"
attribute that is used to indicate the localized or attribute that is used to indicate the localized or
internationalized form, as defined in Section 4.8. internationalized form, as defined in Section 4.6.3.
<csvContact:fEmail> Registrar email address. The attribute <csvContact:fEmail> Registrar email address. The attribute
"isRequired" MUST equal "false". "isRequired" MUST equal "false".
<csvContact:fSp> Registrar state or province with an OPTIONAL <csvContact:fSp> Registrar state or province with an OPTIONAL
"isLoc" attribute that is used to indicate the localized or "isLoc" attribute that is used to indicate the localized or
internationalized form, as defined in Section 4.8. internationalized form, as defined in Section 4.6.3.
<csvContact:fPc> Registrar postal code with an OPTIONAL "isLoc" <csvContact:fPc> Registrar postal code with an OPTIONAL "isLoc"
attribute that is used to indicate the localized or attribute that is used to indicate the localized or
internationalized form, as defined in Section 4.8. internationalized form, as defined in Section 4.6.3.
<csvContact:fVoice> Registrar voice telephone number. <csvContact:fVoice> Registrar voice telephone number.
<csvContact:fVoiceExt> Registrar voice telephone number extension. <csvContact:fVoiceExt> Registrar voice telephone number extension.
<csvContact:fFax> Registrar facsimile telephone number. <csvContact:fFax> Registrar facsimile telephone number.
<csvContact:fFaxExt> Registrar facsimile telephone number extension. <csvContact:fFaxExt> Registrar facsimile telephone number extension.
Example of a "registrar" <csvRegistrar:contents> <rdeCsv:csv> Example of a "registrar" <csvRegistrar:contents> <rdeCsv:csv>
skipping to change at page 68, line 10 skipping to change at page 69, line 10
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvRegistrar:contents> </csvRegistrar:contents>
... ...
Example of the registrar-YYYYMMDD.csv file. The file contains three Example of the registrar-YYYYMMDD.csv file. The file contains three
registrar records. registrar records.
registrarX,"Example Inc.",1234,ok,"123 Example Dr.", registrarX,"Example Inc.",1234,ok,"123 Example Dr.",
"Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,http://www.example.test, +1.7035555556,,jdoe@example.example,http://www.example.example,
http://whois.example.test,2005-04-23T11:49:00.0Z, http://whois.example.example,2005-04-23T11:49:00.0Z,
2009-02-17T17:51:00.0Z 2009-02-17T17:51:00.0Z
registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.",
"Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,http://www.example.test, +1.7035555556,,jdoe@example.example,http://www.example.example,
http://whois.example.test,2005-04-23T11:49:00.0Z, http://whois.example.example,2005-04-23T11:49:00.0Z,
2009-02-17T17:51:00.0Z 2009-02-17T17:51:00.0Z
registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.",
"Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234,
+1.7035555556,,jdoe@example.test,http://www.example.test, +1.7035555556,,jdoe@example.example,http://www.example.example,
http://whois.example.test,2005-04-23T11:49:00.0Z, http://whois.example.example,2005-04-23T11:49:00.0Z,
2009-02-17T17:51:00.0Z 2009-02-17T17:51:00.0Z
5.4.2.2. <csvRegistrar:deletes> 5.4.2.2. <csvRegistrar:deletes>
The <csvRegistrar:deletes> is used to hold the deleted registrar The <csvRegistrar:deletes> is used to hold the deleted registrar
objects in a differential or incremental deposit. All the registrar objects in a differential or incremental deposit. All the registrar
object data is deleted as part of a cascade delete. The object data is deleted as part of a cascade delete. The
<csvRegistrar:deletes> is split into separate CSV file definitions <csvRegistrar:deletes> is split into separate CSV file definitions
using named <rdeCsv:csv> elements with the "name" attribute. The using named <rdeCsv:csv> elements with the "name" attribute. The
following section defines the supported registrar deletes CSV file following section defines the supported registrar deletes CSV file
skipping to change at page 71, line 10 skipping to change at page 72, line 10
reference object information for the deposit. The <csvIDN:contents> reference object information for the deposit. The <csvIDN:contents>
is split into separate CSV file definitions using named <rdeCsv:csv> is split into separate CSV file definitions using named <rdeCsv:csv>
elements with the "name" attribute. The following sections include elements with the "name" attribute. The following sections include
the supported IDN table reference CSV file definitions. the supported IDN table reference CSV file definitions.
5.5.2.1.1. "idnLanguage" CSV File Definition 5.5.2.1.1. "idnLanguage" CSV File Definition
The "idnLanguage" CSV File Definition defines the fields and CSV file The "idnLanguage" CSV File Definition defines the fields and CSV file
references used for the IDN table reference object records. references used for the IDN table reference object records.
The following "rdeCsv" fields, defined in Section 4.7.2, MUST be used The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be
in the "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element: used in the "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fIdnTableId> The language identifier that matches the values <rdeCsv:fIdnTableId> The language identifier that matches the values
for the <rdeCsv:fIdnTableId> field element in the "domain" CSV for the <rdeCsv:fIdnTableId> field element in the "domain" CSV
File Definition (Section 5.1.2.1.1) files. The attribute File Definition (Section 5.1.2.1.1) files. The attribute
"isRequired" MUST equal "true". "isRequired" MUST equal "true".
<rdeCsv:fUrl> URL that defines the character code points that can be <rdeCsv:fUrl> URL that defines the character code points that can be
used for the language defined by the <rdeCsv:fLang> field element. used for the language defined by the <rdeCsv:fLang> field element.
The attribute "isRequired" MUST equal "true". The attribute "isRequired" MUST equal "true".
skipping to change at page 73, line 10 skipping to change at page 74, line 10
Example of the idnLanguage-delete-YYYYMMDD.csv file. The file Example of the idnLanguage-delete-YYYYMMDD.csv file. The file
contains one IDN language record. contains one IDN language record.
LANG-2 LANG-2
5.6. NNDN Object 5.6. NNDN Object
A NNDN (NNDN's not domain name) can be used to store registry A NNDN (NNDN's not domain name) can be used to store registry
reserved names or (blocked, withheld or mirrored) IDN variants. reserved names or (blocked, withheld or mirrored) IDN variants.
A NNDN is a lightweight domain-like object that is not linked Domain Name Registries may maintain domain names without them being
directly to a Registrar (a mirroring NNDN is linked to a Registrar persisted as domain objects in the registry system, for example, a
via the original name). list of reserved names not available for registration. The NNDN is a
lightweight domain-like object that is used to escrow domain names
not maintained as domain name objects.
A domain name can only exist as a domain name object or NNDN object, A domain name can only exist as a domain name object or NNDN object,
but not both. but not both.
The NNDN object supports both the XML and the CSV Model, defined in The NNDN object supports both the XML and the CSV Model, defined in
the Models (Section 2) section. The elements used for both models the Models (Section 2) section. The elements used for both models
are defined in the following sections. are defined in the following sections.
5.6.1. XML Model 5.6.1. XML Model
skipping to change at page 74, line 31 skipping to change at page 75, line 35
mirroringNS is true. If another mechanism such as DNAME is mirroringNS is true. If another mechanism such as DNAME is
used, the value of mirroringNS attribute MUST be false. used, the value of mirroringNS attribute MUST be false.
o An OPTIONAL <crDate> element that contains the date and time of o An OPTIONAL <crDate> element that contains the date and time of
the NNDN object creation. the NNDN object creation.
Example of <rdeNNDN:NNDN> object: Example of <rdeNNDN:NNDN> object:
... ...
<rdeNNDN:NNDN> <rdeNNDN:NNDN>
<rdeNNDN:aName>xn--exampl-gva.test</rdeNNDN:aName> <rdeNNDN:aName>xn--exampl-gva.example</rdeNNDN:aName>
<rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId> <rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId>
<rdeNNDN:originalName>example1.test</rdeNNDN:originalName> <rdeNNDN:originalName>example1.example</rdeNNDN:originalName>
<rdeNNDN:nameState>withheld</rdeNNDN:nameState> <rdeNNDN:nameState>withheld</rdeNNDN:nameState>
<rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate> <rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate>
</rdeNNDN:NNDN> </rdeNNDN:NNDN>
... ...
5.6.1.2. <rdeNNDN:delete> object 5.6.1.2. <rdeNNDN:delete> object
The <rdeNNDN:delete> element contains the ACE of a NNDN that was The <rdeNNDN:delete> element contains the ACE of a NNDN that was
deleted, i.e., the <aName>. deleted, i.e., the <aName>.
Example of <rdeNNDN::delete> object: Example of <rdeNNDN::delete> object:
... ...
<rde:deletes> <rde:deletes>
... ...
<rdeNNDN:delete> <rdeNNDN:delete>
<rdeNNDN:aName>xn--pingino-q2a.test</rdeNDN:aName> <rdeNNDN:aName>xn--pingino-q2a.example</rdeNNDN:aName>
</rdeNNDN:delete> </rdeNNDN:delete>
... ...
</rde:deletes> </rde:deletes>
... ...
5.6.2. CSV Model 5.6.2. CSV Model
For the CSV Model of the NNDN object, the <csvNNDN:contents> child For the CSV Model of the NNDN object, the <csvNNDN:contents> child
element of the <rde:contents> element is used to hold the new or element of the <rde:contents> element is used to hold the new or
updated NNDN objects for the deposit. The <csvNNDN:deletes> child updated NNDN objects for the deposit. The <csvNNDN:deletes> child
skipping to change at page 76, line 18 skipping to change at page 77, line 18
<csvNNDN:fOriginalName> Domain name used to generate the IDN variant <csvNNDN:fOriginalName> Domain name used to generate the IDN variant
with type="eppcom:labelType". with type="eppcom:labelType".
<csvNNDN:fMirroringNS> Defines whether the "mirroring" <csvNNDN:fMirroringNS> Defines whether the "mirroring"
<csvNNDN:fNameState> uses the NS mirror mechanism, as described <csvNNDN:fNameState> uses the NS mirror mechanism, as described
for the <rdeNNDN:nameState> "mirroringNS" attribute in for the <rdeNNDN:nameState> "mirroringNS" attribute in
Section 5.6.1.1, with type="boolean". If the field element is not Section 5.6.1.1, with type="boolean". If the field element is not
defined the default value is "true". defined the default value is "true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "NNDN" <rdeCsv:csv> elements (Section 4.6.2.2), MAY be used in the "NNDN" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fCrDate> Created date and time of the NNDN object. <rdeCsv:fCrDate> Created date and time of the NNDN object.
<rdeCsv:fUName> Name of the NNDN in Unicode character set for the <rdeCsv:fUName> Name of the NNDN in Unicode character set for the
<csvNNDN:fAName> field element. <csvNNDN:fAName> field element.
<rdeCsv:fIdnTableId> IDN Table Identifier for the NNDN that matches <rdeCsv:fIdnTableId> IDN Table Identifier for the NNDN that matches
an IDN Table Reference Object record, as defined in Section 5.5.2. an IDN Table Reference Object record, as defined in Section 5.5.2.
skipping to change at page 77, line 34 skipping to change at page 78, line 34
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvNNDN:contents> </csvNNDN:contents>
... ...
Example of the corresponding NNDN-YYYYMMDD.csv file. The file Example of the corresponding NNDN-YYYYMMDD.csv file. The file
contains two NNDN records for an IDN with one blocked variant and one contains two NNDN records for an IDN with one blocked variant and one
mirrored variant. mirrored variant.
xn--abc456.test,LANG-1,xn--abc123.test, xn--abc456.example,LANG-1,xn--abc123.example,
blocked,,2005-04-23T11:49:00.0Z blocked,,2005-04-23T11:49:00.0Z
xn--abc789.test,LANG-1,xn--abc123.test, xn--abc789.example,LANG-1,xn--abc123.example,
mirrored,1,2005-04-23T11:49:00.0Z mirrored,1,2005-04-23T11:49:00.0Z
5.6.2.2. <csvNNDN:deletes> 5.6.2.2. <csvNNDN:deletes>
The <csvNNDN:deletes> is used to hold the deleted NNDN objects in a The <csvNNDN:deletes> is used to hold the deleted NNDN objects in a
differential or incremental deposit. The <csvNNDN:deletes> is split differential or incremental deposit. The <csvNNDN:deletes> is split
into separate CSV file definitions using named <rdeCsv:csv> elements into separate CSV file definitions using named <rdeCsv:csv> elements
with the "name" attribute. The following section defines the with the "name" attribute. The following section defines the
supported NNDN deletes CSV file definition. supported NNDN deletes CSV file definition.
skipping to change at page 78, line 31 skipping to change at page 79, line 31
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvNNDN:deletes> </csvNNDN:deletes>
... ...
Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file
contains one NNDN records. contains one NNDN records.
xn--abc456.test xn--abc456.example
5.7. EPP Parameters Object 5.7. EPP Parameters Object
The EPP Parameters Object is a pseudo-object that defines the set of The EPP Parameters Object is a pseudo-object that defines the set of
object and object extension services supported by the registry, as object and object extension services supported by the registry, as
defined in [RFC5730]. The EPP Parameters Object is only defined as defined in [RFC5730]. The EPP Parameters Object is only defined as
XML but could be used in the XML model or CSV model. The EPP XML but could be used in the XML model or CSV model. The EPP
Parameters Object is defined using the <rdeEppParams:eppParams> Parameters Object is defined using the <rdeEppParams:eppParams>
element. The EPP Parameters Object SHOULD be included if the element. The EPP Parameters Object SHOULD be included if the
registry supports EPP. Only one EPP Parameters Object MUST exist at registry supports EPP. Only one EPP Parameters Object MUST exist at
skipping to change at page 80, line 11 skipping to change at page 81, line 11
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
... ...
5.8. Policy Object 5.8. Policy Object
The Policy object is a pseudo-object that is used to specify which The Policy object is a pseudo-object that is used to specify which
OPTIONAL elements from the XML Model are REQUIRED based on the OPTIONAL elements from the XML Model are REQUIRED based on the
business model of the registry. For the CSV Model, the OPTIONAL business model of the registry. For the CSV Model, the OPTIONAL
"isRequired" attribute of the <rdeCsv:field> elements, defined in "isRequired" attribute of the <rdeCsv:field> elements, defined in
Section 4.7.1, is used to specify which OPTIONAL fields are REQUIRED Section 4.6.2.1, is used to specify which OPTIONAL fields are
based on the business model of the registry. REQUIRED based on the business model of the registry.
5.8.1. <rdePolicy:policy> object 5.8.1. <rdePolicy:policy> object
The OPTIONAL <policy> contains the following attributes: The OPTIONAL <policy> contains the following attributes:
o An <element> that defines that the referenced <element> is o An <element> that defines that the referenced <element> is
REQUIRED. REQUIRED.
o <scope> that defines the XPath of the element referenced by o <scope> that defines the XPath of the element referenced by
<element>. <element>.
Example of <rdePolicy:policy> object: Example of <rdePolicy:policy> object:
... ...
<rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain" <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain"
element="rdeDom:registrant" /> element="rdeDomain:registrant" />
... ...
5.9. Header Object 5.9. Header Object
The Header Object is a pseudo-object that is used to specify the The Header Object is a pseudo-object that is used to specify the
number of objects in the repository at a specific point in time number of objects in the repository at a specific point in time
(watermark) regardless of the type of deposit: differential, full or (watermark) regardless of the type of deposit: differential, full or
incremental. The Header Object may also be used to provide incremental. The Header Object may also be used to provide
additional information on the contents of the deposit. The Header additional information on the contents of the deposit. The Header
Object is only defined as XML but one header object MUST always be Object is only defined as XML but one header object MUST always be
skipping to change at page 153, line 37 skipping to change at page 154, line 37
definition to be consistent with the "registrar" CSV definition. definition to be consistent with the "registrar" CSV definition.
20. Made the <crRr> and <crDate> elements optional for the host and 20. Made the <crRr> and <crDate> elements optional for the host and
contact objects in the XML model to be consistent with the contact objects in the XML model to be consistent with the
domain object. domain object.
16.15. Changes REGEXT 02 to REGEXT 03 16.15. Changes REGEXT 02 to REGEXT 03
1. Added the optional element contentTag in the header object. 1. Added the optional element contentTag in the header object.
2. Editorial updates 2. Editorial updates.
16.16. Changes REGEXT 03 to REGEXT 04
1. Note: Updates from version REGEXT 03 to REGEXT 04 attend the
feedback provided during the document shepherd review.
2. Editorial updates.
3. Examples now use domain names from the .example TLD.
4. The introduction was enhanced by explaining the need for data
escrow and the proposed solution.
5. Explanation regarding NNDN was improved.
6. Explanation regarding the CSV and XML model was improved.
7. Section 4.5 updated to make the text clearer.
8. draft-arias-noguchi-registry-data-escrow is now referenced from
the I-D repository.
9. The XML prefix "rdeDomain" is now consistently used.
10. The prevID attribute was removed from the examples of full
deposits.
11. The examples were updated to use present dates.
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="20101017001" prevId="20101010001" <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"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:rdeDom="urn:ietf:params:xml:ns:rdeDomain-1.0" xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0" xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0" xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0" xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0" xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
<rde:watermark>2010-10-17T00:00:00Z</rde:watermark> <rde:watermark>2019-10-17T00:00:00Z</rde:watermark>
<rde:rdeMenu> <rde:rdeMenu>
<rde:version>1.0</rde:version> <rde:version>1.0</rde:version>
<rde:objURI>urn:ietf:params:xml:ns:rdeHeader-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeHeader-1.0
</rde:objURI> </rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:rdeContact-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeContact-1.0
</rde:objURI> </rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:rdeHost-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeHost-1.0
</rde:objURI> </rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:rdeDomain-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeDomain-1.0
</rde:objURI> </rde:objURI>
skipping to change at page 155, line 4 skipping to change at page 156, line 32
</rdeHeader:count> </rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeContact-1.0">1 uri="urn:ietf:params:xml:ns:rdeContact-1.0">1
</rdeHeader:count> </rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1 uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1
</rdeHeader:count> </rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1 uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1
</rdeHeader:count> </rdeHeader:count>
<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>
<!-- Domian: example1.test --> <!-- Domain: example1.example -->
<rdeDom:domain> <rdeDomain:domain>
<rdeDom:name>example1.test</rdeDom:name> <rdeDomain:name>example1.example</rdeDomain:name>
<rdeDom:roid>Dexample1-TEST</rdeDom:roid> <rdeDomain:roid>Dexample1-TEST</rdeDomain:roid>
<rdeDom:status s="ok"/> <rdeDomain:status s="ok"/>
<rdeDom:registrant>jd1234</rdeDom:registrant> <rdeDomain:registrant>jd1234</rdeDomain:registrant>
<rdeDom:contact type="admin">sh8013</rdeDom:contact> <rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
<rdeDom:contact type="tech">sh8013</rdeDom:contact> <rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
<rdeDom:ns> <rdeDomain:ns>
<domain:hostObj>ns1.example.com</domain:hostObj> <domain:hostObj>ns1.example.com</domain:hostObj>
<domain:hostObj>ns1.example1.test</domain:hostObj> <domain:hostObj>ns1.example1.example</domain:hostObj>
</rdeDom:ns> </rdeDomain:ns>
<rdeDom:clID>RegistrarX</rdeDom:clID> <rdeDomain:clID>RegistrarX</rdeDomain:clID>
<rdeDom:crRr client="jdoe">RegistrarX</rdeDom:crRr> <rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr>
<rdeDom:crDate>1999-04-03T22:00:00.0Z</rdeDom:crDate> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
<rdeDom:exDate>2015-04-03T22:00:00.0Z</rdeDom:exDate> <rdeDomain:exDate>2015-04-03T22:00:00.0Z</rdeDomain:exDate>
</rdeDom:domain> </rdeDomain:domain>
<!-- Domian: example2.test --> <!-- Domain: example2.example -->
<rdeDom:domain> <rdeDomain:domain>
<rdeDom:name>example2.test</rdeDom:name> <rdeDomain:name>example2.example</rdeDomain:name>
<rdeDom:roid>Dexample2-TEST</rdeDom:roid> <rdeDomain:roid>Dexample2-TEST</rdeDomain:roid>
<rdeDom:status s="ok"/> <rdeDomain:status s="ok"/>
<rdeDom:status s="clientUpdateProhibited"/> <rdeDomain:status s="clientUpdateProhibited"/>
<rdeDom:registrant>jd1234</rdeDom:registrant> <rdeDomain:registrant>jd1234</rdeDomain:registrant>
<rdeDom:contact type="admin">sh8013</rdeDom:contact> <rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
<rdeDom:contact type="tech">sh8013</rdeDom:contact> <rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
<rdeDom:clID>RegistrarX</rdeDom:clID> <rdeDomain:clID>RegistrarX</rdeDomain:clID>
<rdeDom:crRr>RegistrarX</rdeDom:crRr> <rdeDomain:crRr>RegistrarX</rdeDomain:crRr>
<rdeDom:crDate>1999-04-03T22:00:00.0Z</rdeDom:crDate> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
<rdeDom:exDate>2015-04-03T22:00:00.0Z</rdeDom:exDate> <rdeDomain:exDate>2015-04-03T22:00:00.0Z</rdeDomain:exDate>
</rdeDom:domain> </rdeDomain:domain>
<!-- Host: ns1.example.test --> <!-- Host: ns1.example.example -->
<rdeHost:host> <rdeHost:host>
<rdeHost:name>ns1.example1.test</rdeHost:name> <rdeHost:name>ns1.example1.example</rdeHost:name>
<rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid> <rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid>
<rdeHost:status s="ok"/> <rdeHost:status s="ok"/>
<rdeHost:status s="linked"/> <rdeHost:status s="linked"/>
<rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr>
<rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr>
<rdeHost:addr ip="v6">1080:0:0:0:8:800:200C:417A <rdeHost:addr ip="v6">1080:0:0:0:8:800:200C:417A
</rdeHost:addr> </rdeHost:addr>
<rdeHost:clID>RegistrarX</rdeHost:clID> <rdeHost:clID>RegistrarX</rdeHost:clID>
<rdeHost:crRr>RegistrarX</rdeHost:crRr> <rdeHost:crRr>RegistrarX</rdeHost:crRr>
<rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate> <rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate>
skipping to change at page 156, line 36 skipping to change at page 158, line 16
<contact:city>Dulles</contact:city> <contact:city>Dulles</contact:city>
<contact:sp>VA</contact:sp> <contact:sp>VA</contact:sp>
<contact:pc>20166-6503</contact:pc> <contact:pc>20166-6503</contact:pc>
<contact:cc>US</contact:cc> <contact:cc>US</contact:cc>
</contact:addr> </contact:addr>
</rdeContact:postalInfo> </rdeContact:postalInfo>
<rdeContact:voice x="1234">+1.7035555555 <rdeContact:voice x="1234">+1.7035555555
</rdeContact:voice> </rdeContact:voice>
<rdeContact:fax>+1.7035555556 <rdeContact:fax>+1.7035555556
</rdeContact:fax> </rdeContact:fax>
<rdeContact:email>jdoe@example.test <rdeContact:email>jdoe@example.example
</rdeContact:email> </rdeContact:email>
<rdeContact:clID>RegistrarX</rdeContact:clID> <rdeContact:clID>RegistrarX</rdeContact:clID>
<rdeContact:crRr client="jdoe">RegistrarX <rdeContact:crRr client="jdoe">RegistrarX
</rdeContact:crRr> </rdeContact:crRr>
<rdeContact:crDate>2009-09-13T08:01:00.0Z <rdeContact:crDate>2009-09-13T08:01:00.0Z
</rdeContact:crDate> </rdeContact:crDate>
<rdeContact:upRr client="jdoe">RegistrarX <rdeContact:upRr client="jdoe">RegistrarX
</rdeContact:upRr> </rdeContact:upRr>
<rdeContact:upDate>2009-11-26T09:10:00.0Z <rdeContact:upDate>2009-11-26T09:10:00.0Z
</rdeContact:upDate> </rdeContact:upDate>
skipping to change at page 157, line 25 skipping to change at page 159, line 4
<rdeRegistrar:addr> <rdeRegistrar:addr>
<rdeRegistrar:street>123 Example Dr. <rdeRegistrar:street>123 Example Dr.
</rdeRegistrar:street> </rdeRegistrar:street>
<rdeRegistrar:street>Suite 100 <rdeRegistrar:street>Suite 100
</rdeRegistrar:street> </rdeRegistrar:street>
<rdeRegistrar:city>Dulles</rdeRegistrar:city> <rdeRegistrar:city>Dulles</rdeRegistrar:city>
<rdeRegistrar:sp>VA</rdeRegistrar:sp> <rdeRegistrar:sp>VA</rdeRegistrar:sp>
<rdeRegistrar:pc>20166-6503</rdeRegistrar:pc> <rdeRegistrar:pc>20166-6503</rdeRegistrar:pc>
<rdeRegistrar:cc>US</rdeRegistrar:cc> <rdeRegistrar:cc>US</rdeRegistrar:cc>
</rdeRegistrar:addr> </rdeRegistrar:addr>
</rdeRegistrar:postalInfo> </rdeRegistrar:postalInfo>
<rdeRegistrar:voice x="1234">+1.7035555555 <rdeRegistrar:voice x="1234">+1.7035555555
</rdeRegistrar:voice> </rdeRegistrar:voice>
<rdeRegistrar:fax>+1.7035555556 <rdeRegistrar:fax>+1.7035555556
</rdeRegistrar:fax> </rdeRegistrar:fax>
<rdeRegistrar:email>jdoe@example.test <rdeRegistrar:email>jdoe@example.example
</rdeRegistrar:email> </rdeRegistrar:email>
<rdeRegistrar:url>http://www.example.test <rdeRegistrar:url>http://www.example.example
</rdeRegistrar:url> </rdeRegistrar:url>
<rdeRegistrar:whoisInfo> <rdeRegistrar:whoisInfo>
<rdeRegistrar:name>whois.example.test <rdeRegistrar:name>whois.example.example
</rdeRegistrar:name> </rdeRegistrar:name>
<rdeRegistrar:url>http://whois.example.test <rdeRegistrar:url>http://whois.example.example
</rdeRegistrar:url> </rdeRegistrar:url>
</rdeRegistrar:whoisInfo> </rdeRegistrar:whoisInfo>
<rdeRegistrar:crDate>2005-04-23T11:49:00.0Z <rdeRegistrar:crDate>2005-04-23T11:49:00.0Z
</rdeRegistrar:crDate> </rdeRegistrar:crDate>
<rdeRegistrar:upDate>2009-02-17T17:51:00.0Z <rdeRegistrar:upDate>2009-02-17T17:51:00.0Z
</rdeRegistrar:upDate> </rdeRegistrar:upDate>
</rdeRegistrar:registrar> </rdeRegistrar:registrar>
<!-- IDN Table --> <!-- IDN Table -->
<rdeIDN:idnTableRef id="pt-BR"> <rdeIDN:idnTableRef id="pt-BR">
skipping to change at page 158, line 4 skipping to change at page 159, line 33
</rdeRegistrar:upDate> </rdeRegistrar:upDate>
</rdeRegistrar:registrar> </rdeRegistrar:registrar>
<!-- IDN Table --> <!-- IDN Table -->
<rdeIDN:idnTableRef id="pt-BR"> <rdeIDN:idnTableRef id="pt-BR">
<rdeIDN:url> <rdeIDN:url>
http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html
</rdeIDN:url> </rdeIDN:url>
<rdeIDN:urlPolicy> <rdeIDN:urlPolicy>
http://registro.br/dominio/regras.html http://registro.br/dominio/regras.html
</rdeIDN:urlPolicy> </rdeIDN:urlPolicy>
</rdeIDN:idnTableRef> </rdeIDN:idnTableRef>
<!-- NNDN: pinguino.test --> <!-- NNDN: pinguino.example -->
<rdeNNDN:NNDN> <rdeNNDN:NNDN>
<rdeNNDN:aName>xn--exampl-gva.test</rdeNNDN:aName> <rdeNNDN:aName>xn--exampl-gva.example</rdeNNDN:aName>
<rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId> <rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId>
<rdeNNDN:originalName>example1.test</rdeNNDN:originalName> <rdeNNDN:originalName>example1.example</rdeNNDN:originalName>
<rdeNNDN:nameState>withheld</rdeNNDN:nameState> <rdeNNDN:nameState>withheld</rdeNNDN:nameState>
<rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate> <rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate>
</rdeNNDN:NNDN> </rdeNNDN:NNDN>
<!-- EppParams --> <!-- EppParams -->
<rdeEppParams:eppParams> <rdeEppParams:eppParams>
<rdeEppParams:version>1.0</rdeEppParams:version> <rdeEppParams:version>1.0</rdeEppParams:version>
<rdeEppParams:lang>en</rdeEppParams:lang> <rdeEppParams:lang>en</rdeEppParams:lang>
<rdeEppParams:objURI> <rdeEppParams:objURI>
urn:ietf:params:xml:ns:domain-1.0 urn:ietf:params:xml:ns:domain-1.0
skipping to change at page 159, line 4 skipping to change at page 160, line 32
<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="rdeDomain:registrant" />
</rde:contents> </rde:contents>
</rde:deposit> </rde:deposit>
18. 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="20191017002" prevId="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"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:rdeDom="urn:ietf:params:xml:ns:rdeDomain-1.0" xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0" xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0" xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0" xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
<rde:watermark>2010-10-17T00:00:00Z</rde:watermark> <rde:watermark>2019-10-17T00:00:00Z</rde:watermark>
<rde:rdeMenu> <rde:rdeMenu>
<rde:version>1.0</rde:version> <rde:version>1.0</rde:version>
<rde:objURI>urn:ietf:params:xml:ns:rdeHeader-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeHeader-1.0
</rde:objURI> </rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:rdeContact-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeContact-1.0
</rde:objURI> </rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:rdeHost-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeHost-1.0
</rde:objURI> </rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:rdeDomain-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeDomain-1.0
</rde:objURI> </rde:objURI>
skipping to change at page 160, line 5 skipping to change at page 161, line 33
<rde:objURI>urn:ietf:params:xml:ns:rdeIDN-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeIDN-1.0
</rde:objURI> </rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:rdeNNDN-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeNNDN-1.0
</rde:objURI> </rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0 <rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0
</rde:objURI> </rde:objURI>
</rde:rdeMenu> </rde:rdeMenu>
<!-- Deletes --> <!-- Deletes -->
<rde:deletes> <rde:deletes>
<rdeDom:delete> <rdeDomain:delete>
<rdeDom:name>example2.test</rdeDom:name> <rdeDomain:name>example2.example</rdeDomain:name>
</rdeDom:delete> </rdeDomain:delete>
</rde:deletes> </rde:deletes>
<!-- Contents --> <!-- Contents -->
<rde:contents> <rde:contents>
<!-- Header --> <!-- Header -->
<rdeHeader:header> <rdeHeader:header>
<rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:tld>test</rdeHeader:tld>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeDomain-1.0">1 uri="urn:ietf:params:xml:ns:rdeDomain-1.0">1
</rdeHeader:count> </rdeHeader:count>
skipping to change at page 161, line 10 skipping to change at page 162, line 39
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"
xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0" xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0"
xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0" xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0"
xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0" xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0" xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0"
xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
type="FULL" type="FULL"
id="20101017001" prevId="20101010001"> id="20191017001">
<rde:watermark>2010-10-18T00:00:00Z</rde:watermark> <rde:watermark>2019-10-18T00:00:00Z</rde:watermark>
<rde:rdeMenu> <rde:rdeMenu>
<rde:version>1.0</rde:version> <rde:version>1.0</rde:version>
<rde:objURI>urn:ietf:params:xml:ns:csvDomain-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvDomain-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:csvHost-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvHost-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:csvContact-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvContact-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:csvRegistrar-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvRegistrar-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:csvIDN-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvIDN-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:csvNNDN-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvNNDN-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0</rde:objURI>
</rde:rdeMenu> </rde:rdeMenu>
skipping to change at page 170, line 13 skipping to change at page 171, line 41
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"
xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0" xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0"
xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0" xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0"
xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0" xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0" xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0"
xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
type="DIFF" type="DIFF"
id="20101017001" prevId="20101010001"> id="20191017001" prevId="20191010001">
<rde:watermark>2010-10-18T00:00:00Z</rde:watermark> <rde:watermark>2019-10-18T00:00:00Z</rde:watermark>
<rde:rdeMenu> <rde:rdeMenu>
<rde:version>1.0</rde:version> <rde:version>1.0</rde:version>
<rde:objURI>urn:ietf:params:xml:ns:csvDomain-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvDomain-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:csvHost-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvHost-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:csvContact-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvContact-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:csvRegistrar-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvRegistrar-1.0</rde:objURI>
<rde:objURI>urn:ietf:params:xml:ns:csvIDN-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvIDN-1.0</rde:objURI>
</rde:rdeMenu> </rde:rdeMenu>
<rde:deletes> <rde:deletes>
<csvDomain:deletes> <csvDomain:deletes>
skipping to change at page 180, line 24 skipping to change at page 182, line 4
<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>
21. References 21. References
21.1. Normative References 21.1. Normative References
[I-D.ietf-regext-data-escrow]
Lozano, G., "Registry Data Escrow Specification", draft-
ietf-regext-data-escrow-02 (work in progress), November
2019.
[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 182, line 26 skipping to change at page 184, line 12
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-
issues-final-clean-20feb12-en.pdf>. issues-final-clean-20feb12-en.pdf>.
21.3. URIs
[1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data-
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
United States of America United States of America
Phone: +1.310.823.9358 Phone: +1.310.823.9358
Email: gustavo.lozano@icann.org Email: gustavo.lozano@icann.org
 End of changes. 141 change blocks. 
330 lines changed or deleted 397 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/