draft-ietf-regext-dnrd-objects-mapping-05.txt   draft-ietf-regext-dnrd-objects-mapping-06.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: July 12, 2020 C. Thippeswamy Expires: August 23, 2020 C. Thippeswamy
VeriSign VeriSign
Jan 09, 2020 Feb 20, 2020
Domain Name Registration Data (DNRD) Objects Mapping Domain Name Registration Data (DNRD) Objects Mapping
draft-ietf-regext-dnrd-objects-mapping-05 draft-ietf-regext-dnrd-objects-mapping-06
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 July 12, 2020. This Internet-Draft will expire on August 23, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 34 skipping to change at page 2, line 34
5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 70 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 70
5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 74 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 74
5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 79 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 79
5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 81 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 81
5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 81 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 81
6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 84 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 84
7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8. Data escrow agent extended verification process . . . . . . . 85 8. Data escrow agent extended verification process . . . . . . . 85
9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 86 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 86
9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 86 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 86
9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 96 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 95
9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 99 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98
9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 104 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 102
9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 106 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 103
9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 109 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 106
9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 112 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 108
9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 118 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 114
9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 122 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 117
9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 126 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 120
9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 128 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 121
9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 130 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 123
9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 132 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 124
9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 134 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 125
9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 137 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 128
9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 138 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 128
10. Internationalization Considerations . . . . . . . . . . . . . 140 10. Internationalization Considerations . . . . . . . . . . . . . 130
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 140 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 130
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 146 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 135
12.1. Implementation in the gTLD space . . . . . . . . . . . . 146 12.1. Implementation in the gTLD space . . . . . . . . . . . . 135
13. Security Considerations . . . . . . . . . . . . . . . . . . . 147 13. Security Considerations . . . . . . . . . . . . . . . . . . . 136
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 147 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 136
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 147 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 136
16. Change History . . . . . . . . . . . . . . . . . . . . . . . 148 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 137
16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02
to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 148 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 137
16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 148 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 137
16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 149 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 138
16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 149 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 138
16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 149 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 138
16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 151 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 139
16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 151 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 140
16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 152 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 140
16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 152 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 141
16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 152 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 141
16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 152 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 141
16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 152 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 141
16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 152 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 141
16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 152 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 141
16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 154 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 143
16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 154 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 143
16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 155 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 144
17. Example of a full deposit using the XML model . . . . . . . . 155 16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 144
18. Example of differential deposit using the XML model . . . . . 161 17. Example of a Full Deposit using the XML model . . . . . . . . 144
19. Example of a full deposit using the CSV model . . . . . . . . 162 18. Example of Differential Deposit using the XML model . . . . . 150
20. Example of differential deposit using the CSV model . . . . . 171 19. Example of a Full Deposit using the CSV model . . . . . . . . 151
21. References . . . . . . . . . . . . . . . . . . . . . . . . . 182 20. Example of Differential Deposit using the CSV model . . . . . 160
21.1. Normative References . . . . . . . . . . . . . . . . . . 182 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 171
21.2. Informative References . . . . . . . . . . . . . . . . . 183 21.1. Normative References . . . . . . . . . . . . . . . . . . 171
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 184 21.2. Informative References . . . . . . . . . . . . . . . . . 173
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 173
1. Introduction 1. Introduction
Registry Data Escrow is the process by which a registry periodically Registry Data Escrow is the process by which a registry periodically
submits data deposits to a third-party called an escrow agent. These submits data deposits to a third-party called an escrow agent. These
deposits comprise the minimum data needed by a third-party to resume deposits comprise the minimum data needed by a third-party to resume
operations if the registry cannot function and is unable or unwilling operations if the registry cannot function and is unable or unwilling
to facilitate an orderly transfer of service. For example, for a to facilitate an orderly transfer of service. For example, for a
domain name registry or registrar, the data to be deposited would domain name registry or registrar, the data to be deposited would
include all the objects related to registered domain names, e.g., include all the objects related to registered domain names, e.g.,
skipping to change at page 4, line 34 skipping to change at page 4, line 34
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): Domain Name Registries may maintain o NNDN (NNDN's not domain name): Domain Name Registries may maintain
domain names without them being persisted as domain objects in the domain names without their being persisted as domain objects in
registry system, for example, a list of reserved names not the registry system, for example, a list of reserved names not
available for registration. The NNDN is a lightweight domain-like available for registration. The NNDN is a lightweight domain-like
object that is used to escrow domain names not maintained as object that is used to escrow domain names not maintained as
domain name objects. 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.
skipping to change at page 6, line 12 skipping to change at page 6, line 12
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
organization providing Registry Services for a REGISTRY-CLASS DOMAIN organization providing Registry Services for a REGISTRY-CLASS DOMAIN
NAME. NAME.
REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD)
or any other domain name at any level in the DNS tree for which a or any other domain name at any level in the DNS tree for which a
Registry (either directly or through and affiliate company) provides Registry (either directly or through an affiliate company) provides
Registry Services for other organizations or individuals. For Registry Services for other organizations or individuals. For
example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. example: .COM, .ORG, .BIZ, .CO.JP, .B.BR.
REGISTRY SERVICES. Services offered by the Registry critical to the REGISTRY SERVICES. Services offered by the Registry critical to the
following tasks: the provisioning of domain names on receipt of following tasks: the provisioning of domain names on receipt of
requests and data from registrars; responding to registrar queries requests and data from registrars; responding to registrar queries
for status information relating to the DNS servers for the RCDN; for status information relating to the DNS servers for the RCDN;
dissemination of RCDN zone files; operation of the Registry DNS dissemination of RCDN zone files; operation of the Registry DNS
servers; and responding to queries for contact and other information servers; responding to queries for contact and other information
concerning DNS registrations in the RCDN. Any other products or concerning DNS registrations in the RCDN; and any other products or
services that only a Registry is capable of providing, by reason of services that only a Registry is capable of providing, by reason of
its designation as the Registry. Typical examples of Registry its designation as the Registry. Typical examples of Registry
Services are: DNS resolution for the RCDN, WHOIS and EPP. Services are DNS resolution for the RCDN, WHOIS and EPP.
ALLOCATED. A status of some label with respect to a zone, whereby ALLOCATED. A status of some label with respect to a zone, whereby
the label is associated administratively to some entity that has the label is associated administratively to some entity that has
requested the label. This term (and its cognates "allocation" and requested the label. This term (and its cognates "allocation" and
"to allocate") may represents the first step on the way to delegation "to allocate") may represent the first step on the way to delegation
in the DNS. in the DNS.
4. General Conventions 4. General Conventions
4.1. Date and Time 4.1. Date and Time
Numerous fields indicate "dates", such as the creation and expiry Numerous fields indicate "dates", such as the creation and expiry
dates for domain names. These fields SHALL contain timestamps dates for domain names. These fields SHALL contain timestamps
indicating the date and time in UTC as specified in [RFC3339], with indicating the date and time in UTC as specified in [RFC3339], with
no offset from the zero meridian. no offset from the zero meridian.
skipping to change at page 7, line 10 skipping to change at page 7, line 10
Telephone numbers (both voice and facsimile) SHALL be formatted based Telephone numbers (both voice and facsimile) SHALL be formatted based
on structures defined in [ITU-E164]. Telephone numbers described in on structures defined in [ITU-E164]. Telephone numbers described in
this specification are character strings that MUST begin with a plus this specification are character strings that MUST begin with a plus
sign ("+", ASCII value 0x002B), followed by a country code defined in sign ("+", ASCII value 0x002B), followed by a country code defined in
[ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by
a sequence of digits representing the telephone number. a sequence of digits representing the telephone number.
4.4. Checksum 4.4. Checksum
Checksum of the CSV data escrow files MUST use CRC32, that is the The checksum of the CSV data escrow files MUST use CRC32, which is
algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of the algorithm used in the ISO 3309 standard and in section 8.1.1.6.2
ITU-T recommendation V.42. of ITU-T recommendation V.42.
4.5. IP addresses 4.5. IP addresses
IP addresses syntax MUST conform to the text representation of either The syntax of IP addresses MUST conform to the text representation of
Internet Protocol Version 4 [RFC0791] or Internet Protocol Version 6 either Internet Protocol Version 4 [RFC0791] or Internet Protocol
[RFC4291]. Version 6 [RFC4291].
4.6. Conventions applicable to the CSV Model 4.6. Conventions applicable to the CSV Model
4.6.1. CSV Parent Child Relationship 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
used to support a cascade replace or cascade delete of records used to support a cascade replace or cascade delete of records
starting from the parent record in differential and incremental starting from the parent record in Differential and Incremental
deposits. Deposits (see [I-D.ietf-regext-data-escrow]).
The following is an example of the CSV file definitions for a Sample The following is an example of the CSV file definitions for a Sample
object consisting of a parent "sample" CSV File Definition and a object consisting of a parent "sample" CSV File Definition and a
child "sampleStatuses" CSV File Definition. The primary key for the child "sampleStatuses" CSV File Definition. The primary key for the
Sample object is the field <csvSample:fName> that is used as the Sample object is the field <csvSample:fName> that is used as the
foreign key in the "sampleStatuses" CSV File Definition by specifying foreign key in the "sampleStatuses" CSV File Definition by specifying
the "parent=true" attribute. If a Sample record is updated or the "parent=true" attribute. If a Sample record is updated or
deleted in a differential or incremental deposit, it should cascade deleted in a Differential or Incremental Deposit, it should cascade
replace the data using the records included in the child replace the data using the records included in the child
"sampleStatuses" CSV File Definition or cascade delete the existing "sampleStatuses" CSV File Definition or cascade delete the existing
records in the child "sampleStatuses" CSV File Definition, records in the child "sampleStatuses" CSV File Definition,
respectively. respectively.
<csvSample:contents> <csvSample:contents>
... ...
<rdeCsv:csv name="sample" sep=","> <rdeCsv:csv name="sample" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvSample:fName/> <csvSample:fName/>
skipping to change at page 9, line 9 skipping to change at page 9, line 9
substitutes for the <rde:content> element and for the <rde:delete> substitutes for the <rde:content> element and for the <rde:delete>
element, that contains one or more <rdeCsv:csv> elements. For element, that contains one or more <rdeCsv:csv> elements. For
example, the Domain Name Object (Section 5.1) defines the example, the Domain Name Object (Section 5.1) defines the
<csvDomain:contents> element, that substitutes for the <rde:content> <csvDomain:contents> element, that substitutes for the <rde:content>
element, and the <csvDomain:deletes> element, that substitutes for element, and the <csvDomain:deletes> element, that substitutes for
the <rde:delete> element. Both the <csvDomain:contents> element and the <rde:delete> element. Both the <csvDomain:contents> element and
the <csvDomain:deletes> elements contain one or more <rdeCsv:csv> 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 are 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
skipping to change at page 9, line 43 skipping to change at page 9, line 43
compression If the CSV file is compressed, the "compression" compression If the CSV file is compressed, the "compression"
attribute defines the compression format like "gzip" or "zip". attribute defines the compression format like "gzip" or "zip".
encoding Defines the encoding of the CSV file with the default encoding Defines the encoding of the CSV file with the default
encoding of "UTF-8". encoding of "UTF-8".
cksum Defines the checksum of the CSV file using CRC32, as cksum Defines the checksum of the CSV file using CRC32, as
defined in Section 4.4. This attribute is used to validate defined in Section 4.4. This attribute is used to validate
that the full CSV file exists and has not been tampered with. that the full CSV file exists and has not been tampered with.
The <rdeCsv:csv> elements requires a "name" attribute that defines The <rdeCsv:csv> element requires a "name" attribute that defines the
the purpose of the CSV file with values like "domain", "host", purpose of the CSV file with values like "domain", "host", "contact".
"contact". The supported "name" attribute values are defined for The supported "name" attribute values are defined for each object
each object type. The OPTIONAL "sep" attribute defines the CSV type. The OPTIONAL "sep" attribute defines the CSV separator
separator character with the default separator character of ",". character with the default separator character of ",".
The following is an example of the <csvDomain:contents> <rdeCsv:csv> The following is an example of the <csvDomain:contents> <rdeCsv:csv>
element for domain name records where the <rdeCsv:fRegistrant> is set element for domain name records where the <rdeCsv:fRegistrant> is set
as required with isRequired="true". as required with isRequired="true".
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domain" sep=","> <rdeCsv:csv name="domain" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
skipping to change at page 13, line 27 skipping to change at page 13, line 27
<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.6.3. 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 localized form ("loc"). Those elements use a field value
field value or "isLoc" attribute to specify the form used. If an or "isLoc" attribute to specify the form used. If an "isLoc"
"isLoc" attribute is used, a value of "true" indicates the use of the 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
field value MUST be represented in a subset of UTF-8 that can be field value MUST be represented in a subset of UTF-8 that can be
represented in the 7-bit US-ASCII character set. When the localized represented in the 7-bit US-ASCII character set. When the localized
form ("loc") is provided, the field value MAY be represented in form ("loc") is provided, the field value MAY be represented in
unrestricted UTF-8. unrestricted UTF-8.
skipping to change at page 16, line 28 skipping to change at page 16, line 28
<secDns:create> command, see Section 5.2.1. of [RFC5910]. <secDns:create> command, see Section 5.2.1. of [RFC5910].
A <domain> element substitutes for the <abstractDomain> abstract A <domain> element substitutes for the <abstractDomain> abstract
element to define a concrete definition of a domain. The element to define a concrete definition of a domain. The
<abstractDomain> element can be replaced by other domain definitions <abstractDomain> element can be replaced by other domain definitions
using the XML schema substitution groups feature. using the XML schema substitution groups feature.
The <domain> element contains the following child elements: The <domain> element contains the following child elements:
o A <name> element that contains the fully qualified name of the o A <name> element that contains the fully qualified name of the
domain name object. If the domain name is an IDN, the ASCII domain name object. For IDNs the A-Label is used (see [RFC5891],
Compatible Encoding (ACE) MUST be used. Section 4.4).
o A <roid> element that contains the repository object identifier o A <roid> element that contains the repository object identifier
assigned to the domain name object when it was created. assigned to the domain name object when it was created.
o An OPTIONAL <uName> element that contains the fully qualified name o An OPTIONAL <uName> element that contains the fully qualified
of the domain name in Unicode character set. It MUST be provided domain name in Unicode character set. It MUST be provided if
if available. available.
o An OPTIONAL <idnTableId> element that references the IDN o An OPTIONAL <idnTableId> element that references the IDN
Table used for the IDN. This corresponds to the "id" attribute of Table used for the IDN. This corresponds to the "id" attribute of
the <idnTableRef> element. This element MUST be present if the the <idnTableRef> element. This element MUST be present if the
domain name is an IDN. domain name is an IDN.
o An OPTIONAL <originalName> element is used to indicate that the o An OPTIONAL <originalName> element is used to indicate that the
domain name is an IDN variant. This element contains the domain domain name is an IDN variant. This element contains the domain
name used to generate the IDN variant. name used to generate the IDN variant.
o One or more <status> elements that contain the current status o One or more <status> elements that contain the current status
descriptors associated with the domain name. descriptors associated with the domain name.
o Zero or more OPTIONAL <rgpStatus> element to represent o Zero or more OPTIONAL <rgpStatus> elements to represent
"pendingDelete" sub-statuses, including "redemptionPeriod", "pendingDelete" sub-statuses, including "redemptionPeriod",
"pendingRestore", and "pendingDelete", that a domain name can be "pendingRestore", and "pendingDelete", that a domain name can be
in as a result of grace period processing as specified in in as a result of grace period processing as specified in
[RFC3915]. [RFC3915].
o An OPTIONAL <registrant> element that contain the identifier for o An OPTIONAL <registrant> element that contains the identifier for
the human or organizational social information object associated the human or organizational social information object associated
as the holder of the domain name object. as the holder of the domain name object.
o Zero or more OPTIONAL <contact> elements that contain identifiers o Zero or more OPTIONAL <contact> elements that contain identifiers
for the human or organizational social information objects for the human or organizational social information objects
associated with the domain name object. associated with the domain name object.
o An OPTIONAL <ns> element that contains the fully qualified names o An OPTIONAL <ns> element that contains the fully qualified names
of the delegated host objects or host attributes (name servers) of the delegated host objects or host attributes (name servers)
associated with the domain name object. See Section 1.1 of associated with the domain name object. See Section 1.1 of
skipping to change at page 18, line 27 skipping to change at page 18, line 27
* A <reRr> element that contains the identifier of the registrar * A <reRr> element that contains the identifier of the registrar
that requested the domain name object transfer. An OPTIONAL that requested the domain name object transfer. An OPTIONAL
client attribute is used to specify the client that performed client attribute is used to specify the client that performed
the operation. the operation.
* A <reDate> element that contains the date and time that the * A <reDate> element that contains the date and time that the
transfer was requested. transfer was requested.
* An <acRr> element that contains the identifier of the registrar * An <acRr> element that contains the identifier of the registrar
that SHOULD act upon a PENDING transfer request. For all other that should act upon a PENDING transfer request. For all other
status types, the value identifies the registrar that took the status types, the value identifies the registrar that took the
indicated action. An OPTIONAL client attribute is used to indicated action. An OPTIONAL client attribute is used to
specify the client that performed the operation. specify the client that performed the operation.
* An <acDate> element that contains the date and time of a * An <acDate> element that contains the date and time of a
required or completed response. For a PENDING request, the required or completed response. For a PENDING request, the
value identifies the date and time by which a response is value identifies the date and time by which a response is
required before an automated response action will be taken by required before an automated response action will be taken by
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:
... ...
<rdeDomain:domain> <rdeDomain:domain>
<rdeDomain:name>example1.example</rdeDomain:name> <rdeDomain:name>xn--exampl-gva.example</rdeDomain:name>
<rdeDomain:roid>Dexample1-TEST</rdeDomain:roid> <rdeDomain:roid>Dexample1-TEST</rdeDomain:roid>
<rdeDomain:idnTableId>pt-BR</rdeDomain:idnTableId>
<rdeDomain:originalName>example.example</rdeDomain:originalName>
<rdeDomain:status s="ok"/> <rdeDomain:status s="ok"/>
<rdeDomain:registrant>jd1234</rdeDomain:registrant> <rdeDomain:registrant>jd1234</rdeDomain:registrant>
<rdeDomain:contact type="admin">sh8013</rdeDomain:contact> <rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
<rdeDomain:contact type="tech">sh8013</rdeDomain:contact> <rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
<rdeDomain:ns> <rdeDomain:ns>
<domain:hostObj>ns1.example.com</domain:hostObj> <domain:hostObj>ns1.example.com</domain:hostObj>
<domain:hostObj>ns1.example1.example</domain:hostObj> <domain:hostObj>ns1.example1.example</domain:hostObj>
</rdeDomain:ns> </rdeDomain:ns>
<rdeDomain:clID>RegistrarX</rdeDomain:clID> <rdeDomain:clID>RegistrarX</rdeDomain:clID>
<rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr> <rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr>
skipping to change at page 20, line 7 skipping to change at page 20, line 8
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
<csvDomain:deletes> child element of the <rde:deletes> element is <csvDomain:deletes> child element of the <rde:deletes> element is
used to hold the deleted or purged domain name objects for the used to hold the deleted or purged domain name objects for the
deposit. Both the <csvDomain:contents> and <csvDomain:deletes> deposit. Both the <csvDomain:contents> and <csvDomain:deletes>
elements contain one or more <rdeCsv:csv> elements with a set of elements contain one or more <rdeCsv:csv> elements with a set of
named CSV file definitions using the <rdeCsv:csv> "name" attribute. named CSV file definitions using the <rdeCsv:csv> "name" attribute.
Differential and incremental deposits are based on changes to the Differential and Incremental Deposits are based on changes to the
domain name objects. The updated domain name object data under the domain name objects. The updated domain name object data under the
<csvDomain:contents> element is a cascade replace down all of the <csvDomain:contents> element is a cascade replace down all of the
domain name CSV files starting with the parent "domain" CSV File domain name CSV files starting with the parent "domain" CSV File
Definition (Section 5.1.2.1.1). The child CSV file definitions Definition (Section 5.1.2.1.1). The child CSV file definitions
include a <csvDomain:fName parent="true"> field. All the child CSV include a <csvDomain:fName parent="true"> field. All the child CSV
file definition data for the domain name objects in the parent file definition data for the domain name objects in the parent
"domain" CSV File Definition (Section 5.1.2.1.1) MUST first be "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be
deleted and then set using the data in the child CSV files. The deleted and then set using the data in the child CSV files. The
deleted domain name object data under the <csvDomain:deletes> element deleted domain name object data under the <csvDomain:deletes> element
is a cascade delete starting from the "domain" Deletes CSV File is a cascade delete starting from the "domain" Deletes CSV File
skipping to change at page 22, line 47 skipping to change at page 22, line 47
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.example,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.example,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.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, xn--bc123-3ve.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.example,Dxnabc321-TEST,LANG-1,xn--abc123.example, xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.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 24, 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.example, domain2.example, xn--abc123.example and xn-- names domain1.example, domain2.example, xn--bc123-3ve.example and
abc321.example. xn--bc321-3ve.example.
domain1.example,domain1admin,admin domain1.example,domain1admin,admin
domain1.example,domain1tech,tech domain1.example,domain1tech,tech
domain1.example,domain1billing,billing domain1.example,domain1billing,billing
domain2.example,domain2admin,admin domain2.example,domain2admin,admin
domain2.example,domain2tech,tech domain2.example,domain2tech,tech
domain2.example,domain2billing,billing domain2.example,domain2billing,billing
xn--abc123.example,xnabc123admin,admin xn--bc123-3ve.example,xnabc123admin,admin
xn--abc123.example,xnabc123tech,tech xn--bc123-3ve.example,xnabc123tech,tech
xn--abc123.example,xnabc123billing,billing xn--bc123-3ve.example,xnabc123billing,billing
xn--abc321.example,xnabc123admin,admin xn--bc321-3ve.example,xnabc123admin,admin
xn--abc321.example,xnabc123tech,tech xn--bc321-3ve.example,xnabc123tech,tech
xn--abc321.example,xnabc123billing,billing xn--bc321-3ve.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:
skipping to change at page 25, line 32 skipping to change at page 25, line 32
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.example, file contains the statuses for the four domain names domain1.example,
domain2.example, xn--abc123.example and xn--abc321.example. domain2.example, xn--bc123-3ve.example and xn--bc321-3ve.example.
domain1.example,clientUpdateProhibited,"Disallow update", domain1.example,clientUpdateProhibited,"Disallow update",
en, en,
domain1.example,clientDeleteProhibited,"Disallow delete", domain1.example,clientDeleteProhibited,"Disallow delete",
en, en,
domain2.example,ok,,, domain2.example,ok,,,
xn--abc123.example,ok,,, xn--bc123-3ve.example,ok,,,
xn--abc321.example,ok,,, xn--bc321-3ve.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 27, 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.example, domain2.example, xn--abc123.example and domain names domain1.example, domain2.example, xn--bc123-3ve.example
xn--abc321.example referenced via the <rdeCsv:fRoid> field element. and xn--bc321-3ve.example referenced via the <rdeCsv:fRoid> field
element.
domain1.example,Hns1_domain1_test-TEST domain1.example,Hns1_domain1_test-TEST
domain1.example,Hns2_domain1_test-TEST domain1.example,Hns2_domain1_test-TEST
domain2.example,Hns1_domain2_test-TEST domain2.example,Hns1_domain2_test-TEST
domain2.example,Hns2_domain2_test-TEST domain2.example,Hns2_domain2_test-TEST
xn--abc123.example,Hns1_example_test-TEST xn--bc123-3ve.example,Hns1_example_test-TEST
xn--abc123.example,Hns2_example_test-TEST xn--bc123-3ve.example,Hns2_example_test-TEST
xn--abc321.example,Hns1_example_test-TEST xn--bc321-3ve.example,Hns1_example_test-TEST
xn--abc321.example,Hns2_example_test-TEST xn--bc321-3ve.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 28, line 32 skipping to change at page 28, line 32
</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.example, domain2.example, xn-- four domain names domain1.example, domain2.example, xn--
abc123.example and xn--abc321.example. bc123-3ve.example and xn--bc321-3ve.example.
domain1.example,ns1.domain1.example,192.0.2.1,v4 domain1.example,ns1.domain1.example,192.0.2.1,v4
domain1.example,ns2.domain1.example,2001:DB8::1,v6 domain1.example,ns2.domain1.example,2001:DB8::1,v6
domain2.example,ns1.example.net,, domain2.example,ns1.example.net,,
domain2.example,ns2.example.net,, domain2.example,ns2.example.net,,
xn--abc123.example,ns1.example.net,, xn--bc123-3ve.example,ns1.example.net,,
xn--abc123.example,ns2.example.net,, xn--bc123-3ve.example,ns2.example.net,,
xn--abc321.example,ns1.example.net,, xn--bc321-3ve.example,ns1.example.net,,
xn--abc321.example,ns2.example.net,, xn--bc321-3ve.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 33, line 44 skipping to change at page 33, line 44
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.example,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
section defines the supported domain name deletes CSV file section defines the supported domain name deletes CSV file
definition. definition.
5.1.2.2.1. "domain" Deletes CSV File Definition 5.1.2.2.1. "domain" Deletes CSV File Definition
The following "csvDomain" field elements MUST be used in the deletes The following "csvDomain" field elements MUST be used in the deletes
"domain" <rdeCsv:csv> <rdeCsv:fields> element: "domain" <rdeCsv:csv> <rdeCsv:fields> element:
skipping to change at page 37, line 13 skipping to change at page 37, line 13
... ...
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
element of the <rde:deletes> element is used to hold the deleted or element of the <rde:deletes> element is used to hold the deleted or
purged host objects for the deposit. purged host objects for the deposit.
Differential and incremental deposits are based on changes to the Differential and Incremental Deposits are based on changes to the
host objects. The updated host object data under the host objects. The updated host object data under the
<csvHost:contents> element is a cascade replace down all of the host <csvHost:contents> element is a cascade replace down all of the host
CSV files starting with the parent "host" CSV File Definition CSV files starting with the parent "host" CSV File Definition
(Section 5.2.2.1.1). The child CSV file definitions include a (Section 5.2.2.1.1). The child CSV file definitions include a
<rdeCsv:fRoid parent="true"> field. All the child CSV file <rdeCsv:fRoid parent="true"> field. All the child CSV file
definition data for the host objects in the parent "host" CSV File definition data for the host objects in the parent "host" CSV File
Definition (Section 5.2.2.1.1) MUST first be deleted and then set Definition (Section 5.2.2.1.1) MUST first be deleted and then set
using the data in the child CSV files. The deleted host object data using the data in the child CSV files. The deleted host object data
under the <csvHost:deletes> element is a cascade delete starting from under the <csvHost:deletes> element is a cascade delete starting from
the "host" Deletes CSV File Definition (Section 5.2.2.2.1). the "host" Deletes CSV File Definition (Section 5.2.2.2.1).
skipping to change at page 43, line 8 skipping to change at page 43, line 8
ns2.domain2.example. ns2.domain2.example.
Hns1_domain1_test-TEST,192.0.2.1,v4 Hns1_domain1_test-TEST,192.0.2.1,v4
Hns2_domain1_test-TEST,2001:DB8::1,v6 Hns2_domain1_test-TEST,2001:DB8::1,v6
Hns1_domain2_test-TEST,192.0.2.2,v4 Hns1_domain2_test-TEST,192.0.2.2,v4
Hns2_domain2_test-TEST,2001:DB8::2,v6 Hns2_domain2_test-TEST,2001:DB8::2,v6
5.2.2.2. <csvHost:deletes> 5.2.2.2. <csvHost:deletes>
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.6.2.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:
skipping to change at page 46, line 27 skipping to change at page 46, line 27
* A <trStatus> element that contains the state of the most recent * A <trStatus> element that contains the state of the most recent
transfer request. transfer request.
* A <reRr> element that contains the identifier of the registrar * A <reRr> element that contains the identifier of the registrar
that requested the domain name object transfer. An OPTIONAL that requested the domain name object transfer. An OPTIONAL
client attribute is used to specify the client that performed client attribute is used to specify the client that performed
the operation. the operation.
* An <acRr> element that contains the identifier of the registrar * An <acRr> element that contains the identifier of the registrar
that SHOULD act upon a PENDING transfer request. For all other that should act upon a PENDING transfer request. For all other
status types, the value identifies the registrar that took the status types, the value identifies the registrar that took the
indicated action. An OPTIONAL client attribute is used to indicated action. An OPTIONAL client attribute is used to
specify the client that performed the operation. specify the client that performed the operation.
* A <reDate> element that contains the date and time that the * A <reDate> element that contains the date and time that the
transfer was requested. transfer was requested.
* An <acDate> element that contains the date and time of a * An <acDate> element that contains the date and time of a
required or completed response. For a PENDING request, the required or completed response. For a PENDING request, the
value identifies the date and time by which a response is value identifies the date and time by which a response is
skipping to change at page 48, line 29 skipping to change at page 48, line 29
For the CSV Model of the contact object, the <csvContact:contents> For the CSV Model of the contact object, the <csvContact: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 contacts objects for the deposit. The or updated contacts objects for the deposit. The
<csvContact:deletes> child element of the <rde:deletes> element is <csvContact:deletes> child element of the <rde:deletes> element is
used to hold the deleted or purged contact objects for the deposit. used to hold the deleted or purged contact objects for the deposit.
Both the <csvContact:contents> and <csvContact:deletes> elements Both the <csvContact:contents> and <csvContact:deletes> elements
contain one or more <rdeCsv:csv> elements with a set of named CSV contain one or more <rdeCsv:csv> elements with a set of named CSV
file definitions using the <rdeCsv:csv> "name" attribute. file definitions using the <rdeCsv:csv> "name" attribute.
Differential and incremental deposits are based on changes to the Differential and Incremental Deposits are based on changes to the
contact objects. The updated contact object data under the contact objects. The updated contact object data under the
<csvContact:contents> element is a cascade replace down all of the <csvContact:contents> element is a cascade replace down all of the
contact CSV files starting with the parent "contact" CSV File contact CSV files starting with the parent "contact" CSV File
Definition (Section 5.3.2.1.1). The child CSV file definitions Definition (Section 5.3.2.1.1). The child CSV file definitions
include a <csvContact:fId parent="true"> field. All the child CSV include a <csvContact:fId parent="true"> field. All the child CSV
file definition data for the contact objects in the parent "contact" file definition data for the contact objects in the parent "contact"
CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and
then set using the data in the child CSV files. The deleted contact then set using the data in the child CSV files. The deleted contact
object data under the <csvContact:deletes> element is a cascade object data under the <csvContact:deletes> element is a cascade
delete starting from the "contact" Deletes CSV File Definition delete starting from the "contact" Deletes CSV File Definition
skipping to change at page 54, line 39 skipping to change at page 54, line 39
"loc"), as defined in Section 4.6.3, 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.6.3. section Section 4.6.3.
<csvContact:fStreet> Contains the contact's contact's street address <csvContact:fStreet> Contains the contact's street address line with
line with type="contact:fPostalLineType". An index attribute is type="contact:fPostalLineType". An index attribute is required to
required to indicate which street address line the field indicate which street address line the field represents with index
represents with index "0" for the first line and index "2" for the "0" for the first line and index "2" for the last line. An
last line. An OPTIONAL "isLoc" attribute to used to indicate the OPTIONAL "isLoc" attribute to used to indicate the localized or
localized or internationalized form as defined in section internationalized form as defined in section Section 4.6.3.
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.6.3. 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.6.3. form as defined in section Section 4.6.3.
skipping to change at page 61, line 14 skipping to change at page 61, line 14
Example of the contactDisclose-YYYYMMDD.csv file. The file contains Example of the contactDisclose-YYYYMMDD.csv file. The file contains
one disclosure records, disabling disclosure of voice, fax, and one disclosure records, disabling disclosure of voice, fax, and
email. email.
xnabc123admin,0,0,0,0,0,0,0,1,1,1 xnabc123admin,0,0,0,0,0,0,0,1,1,1
5.3.2.2. <csvContact:deletes> 5.3.2.2. <csvContact:deletes>
The <csvContact:deletes> is used to hold the deleted contact objects The <csvContact:deletes> is used to hold the deleted contact objects
in a differential or incremental deposit. All the contact object in a Differential or Incremental Deposit. All the contact object
data is deleted as part of a cascade delete. The data is deleted as part of a cascade delete. The
<csvContact:deletes> is split into separate CSV file definitions <csvContact: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 contact deletes CSV file following section defines the supported contact deletes CSV file
definition. definition.
5.3.2.2.1. "contact" Deletes CSV File Definition 5.3.2.2.1. "contact" Deletes CSV File Definition
The following "csvContact" field elements MUST be used in the deletes The following "csvContact" field elements MUST be used in the deletes
"contact" <rdeCsv:csv> <rdeCsv:fields> element: "contact" <rdeCsv:csv> <rdeCsv:fields> element:
skipping to change at page 62, line 18 skipping to change at page 62, line 18
domain1admin domain1admin
domain1tech domain1tech
domain1billing domain1billing
domain2admin domain2admin
domain2tech domain2tech
domain2billing domain2billing
5.4. Registrar Object 5.4. Registrar Object
The registrar object represents the sponsoring client for other The registrar object represents the sponsoring client for other
objects, for operational purposes MAY be the registry operator. The objects, and is typically referred to as the sponsoring registrar.
registrar object supports both the XML Model and the CSV Model, The registrar object supports both the XML Model and the CSV Model,
defined in Section 2. The elements used for both models are defined defined in Section 2. The elements used for both models are defined
in the following sections. in the following sections.
5.4.1. XML Model 5.4.1. XML Model
There are two elements used in the data escrow of the registrar There are two elements used in the data escrow of the registrar
objects for the XML model including the <rdeRegistrar:registrar>, objects for the XML model including the <rdeRegistrar:registrar>,
under the <rdeRegistrar:contents> element, and the under the <rdeRegistrar:contents> element, and the
<rdeRegistrar:delete> element, under the <rde:deletes> element. <rdeRegistrar:delete> element, under the <rde:deletes> element.
skipping to change at page 63, line 5 skipping to change at page 63, line 5
o An <name> element that contains the name of the registrar. o An <name> element that contains the name of the registrar.
o An OPTIONAL <gurid> element that contains the ID assigned by o An OPTIONAL <gurid> element that contains the ID assigned by
ICANN. ICANN.
o An OPTIONAL <status> element that contains the operational status o An OPTIONAL <status> element that contains the operational status
of the registrar. Possible values are: ok, readonly and of the registrar. Possible values are: ok, readonly and
terminated. terminated.
o Zero or two OPTIONAL <postalInfo> elements that contain postal- o One or two OPTIONAL <postalInfo> elements that contain postal-
address information. Two elements are provided so that address address information. Two elements are provided so that address
information can be provided in both internationalized and information can be provided in both internationalized and
localized forms; a "type" attribute is used to identify the two localized forms; a "type" attribute is used to identify the two
forms. If an internationalized form (type="int") is provided, forms. If an internationalized form (type="int") is provided,
element content MUST be represented in a subset of UTF-8 that can element content MUST be represented in a subset of UTF-8 that can
be represented in the 7-bit US-ASCII character set. If a be represented in the 7-bit US-ASCII character set. If a
localized form (type="loc") is provided, element content MAY be localized form (type="loc") is provided, element content MAY be
represented in unrestricted UTF-8. The <postalInfo> element represented in unrestricted UTF-8. The <postalInfo> element
contains the following child elements: contains the following child elements:
skipping to change at page 65, line 28 skipping to change at page 65, line 28
For the CSV Model of the registrar object, the For the CSV Model of the registrar object, the
<csvRegistrar:contents> child element of the <rde:contents> element <csvRegistrar:contents> child element of the <rde:contents> element
is used to hold the new or updated registrar objects for the deposit. is used to hold the new or updated registrar objects for the deposit.
The <csvRegistrar:deletes> child element of the <rde:deletes> element The <csvRegistrar:deletes> child element of the <rde:deletes> element
is used to hold the deleted or purged registrar objects for the is used to hold the deleted or purged registrar objects for the
deposit. Both the <csvRegistrar:contents> and <csvRegistrar:deletes> deposit. Both the <csvRegistrar:contents> and <csvRegistrar:deletes>
elements contain one or more <rdeCsv:csv> elements with a set of elements contain one or more <rdeCsv:csv> elements with a set of
named CSV file definitions using the <rdeCsv:csv> "name" attribute. named CSV file definitions using the <rdeCsv:csv> "name" attribute.
Differential and incremental deposits are based on changes to the Differential and Incremental Deposits are based on changes to the
registrar objects. The updated registrar object data under the registrar objects. The updated registrar object data under the
<csvContact:contents> element is a cascade replace down all of the <csvContact:contents> element is a cascade replace down all of the
registrar CSV files starting with the parent "registrar" CSV File registrar CSV files starting with the parent "registrar" CSV File
Definition (Section 5.4.2.1.1). The child CSV file definitions Definition (Section 5.4.2.1.1). The child CSV file definitions
include a <csvRegistrar:fId parent="true"> field. All the child CSV include a <csvRegistrar:fId parent="true"> field. All the child CSV
file definition data for the registrar objects in the parent file definition data for the registrar objects in the parent
"registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be
deleted and then set using the data in the child CSV files. The deleted and then set using the data in the child CSV files. The
deleted registrar object data under the <csvRegistrar:deletes> deleted registrar object data under the <csvRegistrar:deletes>
element is a cascade delete starting from the "registrar" Deletes CSV element is a cascade delete starting from the "registrar" Deletes CSV
skipping to change at page 69, line 27 skipping to change at page 69, line 27
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.example,http://www.example.example, +1.7035555556,,jdoe@example.example,http://www.example.example,
http://whois.example.example,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
definition. definition.
5.4.2.2.1. "registrar" Deletes CSV File Definition 5.4.2.2.1. "registrar" Deletes CSV File Definition
The following "csvRegistrar" field elements MUST be used in the The following "csvRegistrar" field elements MUST be used in the
deletes "registrar" <rdeCsv:csv> <rdeCsv:fields> element: deletes "registrar" <rdeCsv:csv> <rdeCsv:fields> element:
skipping to change at page 73, line 8 skipping to change at page 73, line 8
contains two IDN language records. contains two IDN language records.
LANG-1, LANG-1,
http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt
LANG-2, LANG-2,
http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt
5.5.2.2. <csvIDN:deletes> 5.5.2.2. <csvIDN:deletes>
The <csvIDN:deletes> is used to hold the deleted IDN table reference The <csvIDN:deletes> is used to hold the deleted IDN table reference
objects in a differential or incremental deposit. The objects in a Differential or Incremental Deposit. The
<csvIDN:deletes> is split into separate CSV file definitions using <csvIDN: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
section defines the supported IDN table reference deletes CSV file section defines the supported IDN table reference deletes CSV file
definition. definition.
5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition
The following "idnLanguage" field elements MUST be used in the The following "idnLanguage" field elements MUST be used in the
deletes "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element: deletes "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element:
skipping to change at page 74, line 7 skipping to change at page 74, line 7
</csvIDN:deletes> </csvIDN:deletes>
... ...
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 An 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.
Domain Name Registries may maintain domain names without them being Domain Name Registries may maintain domain names without their being
persisted as domain objects in the registry system, for example, a persisted as domain objects in the registry system, for example, a
list of reserved names not available for registration. The NNDN is a list of reserved names not available for registration. The NNDN is a
lightweight domain-like object that is used to escrow domain names lightweight domain-like object that is used to escrow domain names
not maintained as domain name objects. 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 an NNDN
but not both. object, 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
There are two elements used in the data escrow of the NNDN objects There are two elements used in the data escrow of the NNDN objects
for the XML model including the <rdeNNDN:NNDN>, under the for the XML model including the <rdeNNDN:NNDN>, under the
<rde:contents> element, and the <rdeNNDN:delete> element, under the <rde:contents> element, and the <rdeNNDN:delete> element, under the
<rde:deletes> element. <rde:deletes> element.
A <rdeNNDN:NNDN> element substitutes for the <rdeNNDN:abstractNNDN> A <rdeNNDN:NNDN> element substitutes for the <rdeNNDN:abstractNNDN>
abstract element to define a concrete definition of a NNDN. The abstract element to define a concrete definition of an NNDN. The
<rdeNNDN:abstractDomain> element can be replaced by other NNDN <rdeNNDN:abstractDomain> element can be replaced by other NNDN
definitions using the XML schema substitution groups feature. definitions using the XML schema substitution groups feature.
5.6.1.1. <rdeNNDN:NNDN> object 5.6.1.1. <rdeNNDN:NNDN> object
The <rdeNNDN:NNDN> element contains the following child elements: The <rdeNNDN:NNDN> element contains the following child elements:
o An <aName> element that contains the fully qualified name of the o An <aName> element that contains the fully qualified name of the
NNDN. If the NNDN is an IDN, the ASCII Compatible Encoding (ACE) NNDN. For IDNs the A-Label is used (see [RFC5891], Section 4.4).
MUST be used.
o An OPTIONAL <uName> element that contains the fully qualified name o An OPTIONAL <uName> element that contains the fully qualified name
of the NNDN in Unicode character set. It MUST be provided if of the NNDN in Unicode character set. It MUST be provided if
available. available.
o An OPTIONAL <idnTableId> element that references the IDN o An OPTIONAL <idnTableId> element that references the IDN
Table used for the NNDN. This corresponds to the "id" attribute Table used for the NNDN. This corresponds to the "id" attribute
of the <idnTableRef> element. This element MUST be present if the of the <idnTableRef> element. This element MUST be present if the
NNDN is an IDN. NNDN is an IDN.
o An OPTIONAL <originalName> element is used to indicate that the o An OPTIONAL <originalName> element is used to indicate that the
NNDN is used for an IDN variant. This element contains the domain NNDN is used for an IDN variant. This element contains the domain
name used to generate the IDN variant. name used to generate the IDN variant.
o A <nameState> element that indicates the state of the NNDN: o A <nameState> element that indicates the state of the NNDN:
blocked, withheld or mirrored. blocked, withheld or mirrored.
* If a NNDN is considered undesirable for registration (i.e., * If an NNDN is considered undesirable for registration (i.e.,
unavailable for allocation to anyone), then the NNDN will be unavailable for allocation to anyone), then the NNDN will be
tagged as "blocked". tagged as "blocked".
* If a NNDN is considered a potential registration of a domain * If an NNDN is considered a potential registration of a domain
object for a registrant, then the NNDN will be tagged as object for a registrant, then the NNDN will be tagged as
"withheld". This status is only used when the NNDN is used for "withheld". This status is only used when the NNDN is used for
an IDN variant. an IDN variant.
* If a NNDN is considered a mirrored IDN variant of a domain * If an NNDN is considered a mirrored IDN variant of a domain
object, then the NNDN will be tagged as "mirrored". A object, then the NNDN will be tagged as "mirrored". A
mirroringNS attribute is used to specify if the mirrored IDN mirroringNS attribute is used to specify if the mirrored IDN
variant use the NS mirror mechanism. The default value of variant use the NS mirror mechanism. The default value of
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 an <rdeNNDN:NNDN> object:
... ...
<rdeNNDN:NNDN> <rdeNNDN:NNDN>
<rdeNNDN:aName>xn--exampl-gva.example</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.example</rdeNNDN:originalName> <rdeNNDN:originalName>example.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 NNDN that was deleted,
deleted, i.e., the <aName>. i.e., the <aName>.
Example of <rdeNNDN::delete> object: Example of an <rdeNNDN::delete> object:
... ...
<rde:deletes> <rde:deletes>
... ...
<rdeNNDN:delete> <rdeNNDN:delete>
<rdeNNDN:aName>xn--pingino-q2a.example</rdeNNDN:aName> <rdeNNDN:aName>xn--pingino-q2a.example</rdeNNDN:aName>
</rdeNNDN:delete> </rdeNNDN:delete>
... ...
</rde:deletes> </rde:deletes>
... ...
skipping to change at page 76, line 44 skipping to change at page 76, line 44
NNDN CSV file definitions. NNDN CSV file definitions.
5.6.2.1.1. "NNDN" CSV File Definition 5.6.2.1.1. "NNDN" CSV File Definition
The "NNDN" CSV File Definition defines the fields and CSV file The "NNDN" CSV File Definition defines the fields and CSV file
references used for the NNDN object records. references used for the NNDN object records.
The following "csvNNDN" field elements MUST be used in the "NNDN" The following "csvNNDN" field elements MUST be used in the "NNDN"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvNNDN:fAName> ASCII Compatible Encoding (ACE) field of the NNDN <csvNNDN:fAName> Fully qualified name of the NNDN with
with type="eppcom:labelType" and isRequired="true". type="eppcom:labelType" and isRequired="true". For IDNs the
A-Label is used (see [RFC5891], Section 4.4).
<csvNNDN:fNameState> State of the NNDN: blocked or withheld with <csvNNDN:fNameState> State of the NNDN: blocked or withheld with
type="rdeNNDN:nameState" and isRequired="true". See type="rdeNNDN:nameState" and isRequired="true". See
Section 5.6.1.1 for a description of the possible values for the Section 5.6.1.1 for a description of the possible values for the
<rdeNNDN:nameState> element. <rdeNNDN:nameState> element.
The following field elements MAY be used in the "NNDN" <rdeCsv:csv> The following field elements MAY be used in the "NNDN" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<csvNNDN:fOriginalName> Domain name used to generate the IDN variant <csvNNDN:fOriginalName> Domain name used to generate the IDN variant
skipping to change at page 78, line 5 skipping to change at page 78, line 5
<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.
Example of a "NNDN" <csvNNDN:contents> <rdeCsv:csv> element: Example of an "NNDN" <csvNNDN:contents> <rdeCsv:csv> element:
... ...
<csvNNDN:contents> <csvNNDN:contents>
... ...
<rdeCsv:csv name="NNDN" sep=","> <rdeCsv:csv name="NNDN" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvNNDN:fAName/> <csvNNDN:fAName/>
<rdeCsv:fIdnTableId/> <rdeCsv:fIdnTableId/>
<csvNNDN:fOriginalName/> <csvNNDN:fOriginalName/>
<csvNNDN:fNameState/> <csvNNDN:fNameState/>
skipping to change at page 78, 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.example,LANG-1,xn--abc123.example, xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example,
blocked,,2005-04-23T11:49:00.0Z blocked,,2005-04-23T11:49:00.0Z
xn--abc789.example,LANG-1,xn--abc123.example, xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.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.
5.6.2.2.1. "NNDN" Deletes CSV File Definition 5.6.2.2.1. "NNDN" Deletes CSV File Definition
The following "NNDN" field elements MUST be used in the deletes The following "NNDN" field elements MUST be used in the deletes
"NNDN" <rdeCsv:csv> <rdeCsv:fields> element: "NNDN" <rdeCsv:csv> <rdeCsv:fields> element:
<csvNNDN:fAName> ASCII Compatible Encoding (ACE) field of the NNDN <csvNNDN:fAName> Fully qualified name of the NNDN with
with type="eppcom:labelType" and isRequired="true". type="eppcom:labelType" and isRequired="true".
Example of a "NNDN" <csvNNDN:deletes> <rdeCsv:csv> element. Example of an "NNDN" <csvNNDN:deletes> <rdeCsv:csv> element.
... ...
<csvNNDN:deletes> <csvNNDN:deletes>
... ...
<rdeCsv:csv name="NNDN"> <rdeCsv:csv name="NNDN">
<rdeCsv:fields> <rdeCsv:fields>
<csvNNDN:fAName/> <csvNNDN:fAName/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
skipping to change at page 79, 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.example xn--bc456-3ve.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 81, line 35 skipping to change at page 81, line 35
... ...
<rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain" <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain"
element="rdeDomain: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 Deposit. 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
present per escrow deposit regardless of using XML Model or CSV present per escrow deposit regardless of using XML Model or CSV
Model. The Header Object is defined using the <rdeHeader:header> Model. The Header Object is defined using the <rdeHeader:header>
element. element.
5.9.1. <rdeHeader:header> object 5.9.1. <rdeHeader:header> object
The <rdeHeader:header> contains the following elements: The <rdeHeader:header> contains the following elements:
o A choice of one of the elements defined in the o A choice of one of the elements defined in the
"repositoryTypeGroup" group element that indicates the unique "repositoryTypeGroup" group element that indicates the unique
identifier for the repository being escrowed. Possible elements identifier for the repository being escrowed. Possible elements
are: are:
* A <rdeHeader:tld> element that defines TLD or the REGISTRY- * A <rdeHeader:tld> element that defines TLD or the REGISTRY-
CLASS DOMAIN NAME (RCDN) being escrowed in the case of a CLASS DOMAIN NAME (RCDN) being escrowed in the case of a
Registry data escrow deposit. For IDNs the A-Label is used Registry data escrow deposit. For IDNs the A-Label is used
[RFC5891]. (see [RFC5891], Section 4.4).
* A <rdeHeader:registrar> element that defines the Registrar ID * A <rdeHeader:registrar> element that defines the Registrar ID
corresponding to a Registrar data escrow deposit. In the case corresponding to a Registrar data escrow deposit. In the case
of an ICANN-accredited Registrar, the <rdeHeader:registrar> of an ICANN-accredited Registrar, the <rdeHeader:registrar>
element MUST be the IANA Registrar ID assigned by ICANN. element MUST be the IANA Registrar ID assigned by ICANN.
* A <rdeHeader:ppsp> element that defines the provider ID * A <rdeHeader:ppsp> element that defines the provider ID
corresponding to a Privacy and Proxy Services Provider data corresponding to a Privacy and Proxy Services Provider data
escrow deposit. In the case of an ICANN-accredited Privacy and escrow deposit. In the case of an ICANN-accredited Privacy and
Proxy Services Provider, the <rdeHeader:ppsp> element MUST be Proxy Services Provider, the <rdeHeader:ppsp> element MUST be
the unique ID assigned by ICANN. the unique ID assigned by ICANN.
* A <rdeHeader:reseller> element that defines the provider ID * A <rdeHeader:reseller> element that defines the provider ID
corresponding to a Reseller data escrow deposit. corresponding to a Reseller data escrow deposit.
o A <count> element that contains the number of objects in the SRS o A <count> element that contains the number of objects in the SRS
at a specific point in time (watermark) regardless of the type of at a specific point in time (watermark) regardless of the type of
deposit: differential, full or incremental. The <count> element deposit: Differential, Full or Incremental. The <count> element
supports the following attributes: supports the following attributes:
* A "uri" attribute reflects the XML namespace URI of the primary * A "uri" attribute reflects the XML namespace URI of the primary
objects for the XML Model and CSV Model. For example, the objects for the XML Model and CSV Model. For example, the
"uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for
domain name objects using the XML Model, and the "uri" is set domain name objects using the XML Model, and the "uri" is set
to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name
objects using the CSV Model. objects using the CSV Model.
* An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS
DOMAIN NAME (RCDN) of the objects included in the <count> DOMAIN NAME (RCDN) of the objects included in the <count>
element. For IDNs the A-Label is used [RFC5891]. If the element. For IDNs the A-Label is used [RFC5891], Section 4.4.
"rcdn" attribute is present, the value of the <count> element If the "rcdn" attribute is present, the value of the <count>
must include only objects related to registrations in the same element must include only objects related to registrations in
and lower levels. For example in a data escrow deposit for the the same and lower levels. For example in a data escrow
.EXAMPLE TLD, a value of "example" in the "rcdn" attribute deposit for the .EXAMPLE TLD, a value of "example" in the
within the <count> element indicates the number of objects in "rcdn" attribute within the <count> element indicates the
the TLD including objects in other RCDNs within the TLD, number of objects in the TLD including objects in other RCDNs
whereas a value of "com.example" indicates the number of within the TLD, whereas a value of "com.example" indicates the
elements for objects under "com.example" and lower levels. number of elements for objects under "com.example" and lower
Omitting the "rcdn" attribute indicates that the total includes levels. Omitting the "rcdn" attribute indicates that the total
all objects of the specified "uri" in the repository (e.g. the includes all objects of the specified "uri" in the repository
TLD, Registrar, or PPSP). (e.g. the TLD, Registrar, or PPSP).
* An OPTIONAL "registrarId" attribute indicates the identifier of * An OPTIONAL "registrarId" attribute indicates the identifier of
the sponsoring Registrar of the objects included in the <count> the sponsoring Registrar of the objects included in the <count>
element. In the case of an ICANN-accredited Registrar, the element. In the case of an ICANN-accredited Registrar, the
value MUST be the IANA Registrar ID assigned by ICANN. value MUST be the IANA Registrar ID assigned by ICANN.
o An OPTIONAL <contentTag> element that contains a tag that defines o An OPTIONAL <contentTag> element that contains a tag that defines
the expected content in the deposit. The producer and consumer of the expected content in the deposit. The producer and consumer of
the deposits will coordinate the set of possible <contentTag> the deposits will coordinate the set of possible <contentTag>
element values. element values.
skipping to change at page 84, line 32 skipping to change at page 84, line 32
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:csvNNDN-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:csvNNDN-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
</rdeHeader:count> </rdeHeader:count>
</rdeHeader:header> </rdeHeader:header>
... ...
6. RDE IDN Variants handling 6. RDE IDN Variants handling
Depending on the Registration Policy of the Registry; for a domain Depending on the Registration Policy of the Registry, for a domain
name there may be multiple variant names. See [variantTLDsReport] name there may be multiple variant names. See [variantTLDsReport]
for further detail on IDN variants. for further detail on IDN variants.
A registry could choose to escrow IDN variants as domains or NNDN A registry could choose to escrow IDN variants as domains or NNDN
objects. A specific IDN variant can be represented in the escrow objects. A specific IDN variant can be represented in the escrow
deposit, as a domain or as a NNDN object, but not both. deposit, as a domain or as an NNDN object, but not both.
If using domain objects to represent IDN variants, the normal If using domain objects to represent IDN variants, the normal
behavior during restoration of a SRS based on an escrow deposit is to behavior during restoration of an SRS based on an escrow deposit is
restore the IDN variants as a mirrored variant. If the registration to restore the IDN variants as a mirrored variant. If the
data of the IDN variant is different from the original name, the registration data of the IDN variant is different from the original
details of this specific implementation MUST be described in the IDN name, the details of this specific implementation MUST be described
policy document. in the IDN policy document.
A NNDN or a domain name are explicit representations of an IDN An NNDN or a domain name are explicit representations of an IDN
variant while an IDN variant computed based on an algorithm is an variant while an IDN variant computed based on an algorithm is an
implicit representation. Explicit representation of an IDN variant implicit representation. Explicit representation of an IDN variant
takes precedence over an implicit representation. takes precedence over an implicit representation.
7. Profile 7. Profile
Different business models of registries exist, therefore the registry Different business models of registries exist, therefore the registry
is responsible to define a profile that matches its particular is responsible for defining a profile that matches its particular
business model. The profile mechanism allows a registry to extend business model. The profile mechanism allows a registry to extend
this specification. this specification.
A profile is the process of: A profile is the process of:
1. Extending base objects with the mechanisms defined for XML and 1. Extending base objects with the mechanisms defined for XML and
CSV models. CSV models.
* In the case of the XML model, abstract elements could be use * In the case of the XML model, abstract elements could be use
to extend the following objects: <domain>, <host>, <contact>, to extend the following objects: <domain>, <host>, <contact>,
<NNDN> and <registrar> using XML schema substitution groups <NNDN> and <registrar> using XML schema substitution groups
feature. feature.
2. Defining a <policy> object to specify which OPTIONAL elements of 2. Defining a <policy> object to specify which OPTIONAL elements of
this base specification is required based on the business model this base specification is required based on the business model
of the registry. An example is the <registrant> element that is of the registry. An example is the <registrant> element that is
usually REQUIRED but it is specified as OPTIONAL in this usually REQUIRED but it is specified as OPTIONAL in this
specification to support existing business models. specification to support some existing business models.
3. Adding new escrowed objects using the <rde:contents> and 3. Adding new escrowed objects using the <rde:contents> and
<rde:deletes> elements. <rde:deletes> elements.
4. Providing the XML schemas to third parties that require them to 4. Providing the XML schemas to third parties that require them to
validate the escrow deposits. validate the escrow deposits.
8. Data escrow agent extended verification process 8. Data escrow agent extended verification process
A Data Escrow Agent SHOULD perform an extended verification process A Data Escrow Agent SHOULD perform an extended verification process
that starts by creating a dataset to be tested. that starts by creating a dataset to be tested.
o If a full deposit is to be tested, the full deposit is the o If a Full Deposit is to be tested, the Full Deposit is the
dataset. dataset.
o If an incremental deposit is to be tested, the dataset is created o If an Incremental Deposit is to be tested, the dataset is created
by using the incremental plus the last previous full deposit. by using the Incremental Deposit plus the last previous Full
Deposit.
o If a differential deposit is to be tested, the dataset is created o If a Differential Deposit is to be tested, the dataset is created
by using the differential deposit plus all the required deposits by using the Differential Deposit plus all the required deposits
leading to the last previous full deposit. leading to the last previous Full Deposit.
The following are the minimum suggested tests on the dataset: The following are the minimum suggested tests on the dataset:
o Validate the escrow deposits using the definition agreed with the o Validate the escrow deposits using the definition agreed with the
registry. registry.
* In the case of the XML model, the contents of the escrow * In the case of the XML model, the contents of the escrow
deposits MUST be validated using the XML schemas of the deposits MUST be validated using the XML schemas of the
profile. profile.
o Count the objects and validate that the number of objects is equal o Count the objects and validate that the number of objects is equal
to the number objects reported in the <header> element of the to the number objects reported in the <header> element of the
escrow deposit of that point in time (watermark). escrow deposit of that point in time (watermark).
o All contact objects linked to domain names MUST be present. o All contact objects linked to domain names MUST be present.
o All registrars objects linked to other objects MUST be present. o All registrars objects linked to other objects MUST be present.
o A domain name exists as a domain name or NNDN, but not both. o No domain name exists as both a domain name and an NNDN.
o The elements listed as required in the <policy> element MUST be o The elements listed as required in the <policy> element MUST be
present. present.
o All idnTableRef definitions linked from other objects MUST be o All idnTableRef definitions linked from other objects MUST be
present. present.
o If an EPP Parameters Object was escrowed in the past, one and only o If an EPP Parameters Object was escrowed in the past, one and only
one EPP Parameters Object MUST be present. one EPP Parameters Object MUST be present.
o The watermark is not in the future. o The watermark is not in the future.
9. Formal Syntax 9. Formal Syntax
Schemas are presented here. Schemas are presented here.
9.1. RDE CSV Schema 9.1. RDE CSV Schema
Copyright (c) 2012 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeCsv-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
skipping to change at page 96, line 17 skipping to change at page 95, line 37
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.2. RDE Domain Object 9.2. RDE Domain Object
Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeDomain-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0" xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
skipping to change at page 99, line 16 skipping to change at page 98, line 4
</complexType> </complexType>
<!-- Delete Type --> <!-- Delete Type -->
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element name="name" <element name="name"
type="eppcom:labelType" minOccurs="0" type="eppcom:labelType" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END END
9.3. CSV Domain Object 9.3. CSV Domain Object
Copyright (c) 2012 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvDomain-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
skipping to change at page 103, line 45 skipping to change at page 102, line 4
<!-- Domain status based on domain-1.0.xsd --> <!-- Domain status based on domain-1.0.xsd -->
<complexType name="fStatusType"> <complexType name="fStatusType">
<complexContent> <complexContent>
<extension base="rdeCsv:fieldRequiredType"> <extension base="rdeCsv:fieldRequiredType">
<sequence/> <sequence/>
<attribute name="type" type="token" <attribute name="type" type="token"
default="domain\:statusValueType"/> default="domain\:statusValueType"/>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.4. RDE Host Object 9.4. RDE Host Object
Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeHost-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0" xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
skipping to change at page 106, line 17 skipping to change at page 103, line 40
type="eppcom:roidType"/> type="eppcom:roidType"/>
</choice> </choice>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END END
9.5. CSV Host Object 9.5. CSV Host Object
Copyright (c) 2012 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvHost-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvHost-1.0"
xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
skipping to change at page 109, line 15 skipping to change at page 106, line 4
<extension base="rdeCsv:fieldRequiredType"> <extension base="rdeCsv:fieldRequiredType">
<sequence/> <sequence/>
<attribute name="type" type="token" <attribute name="type" type="token"
default="host\:statusValueType"/> default="host\:statusValueType"/>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.6. RDE Contact Object 9.6. RDE Contact Object
Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeContact-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeContact-1.0"
xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0" xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
skipping to change at page 111, line 45 skipping to change at page 108, line 4
<!-- Delete Type --> <!-- Delete Type -->
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element name="id" <element name="id"
type="eppcom:clIDType" minOccurs="0" type="eppcom:clIDType" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END END
9.7. CSV Contact Object 9.7. CSV Contact Object
Copyright (c) 2012 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvContact-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvContact-1.0"
xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0" xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
skipping to change at page 118, line 42 skipping to change at page 114, line 17
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.8. RDE Registrar Object 9.8. RDE Registrar Object
Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeRegistrar-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0" xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
skipping to change at page 122, line 48 skipping to change at page 117, line 40
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END END
9.9. CSV Registrar Object 9.9. CSV Registrar Object
Copyright (c) 2012 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvRegistrar-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvRegistrar-1.0"
xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0" xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
skipping to change at page 126, line 26 skipping to change at page 120, line 33
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.10. RDE IDN Table Reference Objects 9.10. RDE IDN Table Reference Objects
Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeIDN-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
skipping to change at page 128, line 21 skipping to change at page 121, line 44
<minLength value="1"/> <minLength value="1"/>
<maxLength value="64"/> <maxLength value="64"/>
</restriction> </restriction>
</simpleType> </simpleType>
</schema> </schema>
END END
9.11. CSV IDN Language Object 9.11. CSV IDN Language Object
Copyright (c) 2012 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvIDN-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvIDN-1.0"
xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0" xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
skipping to change at page 130, line 14 skipping to change at page 123, line 4
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element ref="rdeCsv:csv" maxOccurs="unbounded"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.12. EPP Parameters Object 9.12. EPP Parameters Object
Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeEppParams-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeEppParams-1.0"
xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
skipping to change at page 132, line 8 skipping to change at page 124, line 14
type="epp:dcpType"/> type="epp:dcpType"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END END
9.13. NNDN Object 9.13. NNDN Object
Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeNNDN-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeNNDN-1.0"
xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
skipping to change at page 134, line 26 skipping to change at page 125, line 48
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END END
9.14. CSV NNDN Object 9.14. CSV NNDN Object
Copyright (c) 2013 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvNNDN-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvNNDN-1.0"
xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0" xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
skipping to change at page 137, line 4 skipping to change at page 127, line 42
<attribute name="type" type="token" <attribute name="type" type="token"
default="rdeNNDN\:nameState"/> default="rdeNNDN\:nameState"/>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- Mirroring uses NS mirror mechanism? --> <!-- Mirroring uses NS mirror mechanism? -->
<element name="fMirroringNS" <element name="fMirroringNS"
type="rdeCsv:fBooleanType" type="rdeCsv:fBooleanType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END END
9.15. Policy Object 9.15. Policy Object
Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdePolicy-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdePolicy-1.0"
xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0" xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<annotation> <annotation>
<documentation> <documentation>
skipping to change at page 138, line 36 skipping to change at page 128, line 38
<attribute name="scope" type="token" use="required"/> <attribute name="scope" type="token" use="required"/>
<attribute name="element" type="anyURI" use="required"/> <attribute name="element" type="anyURI" use="required"/>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END END
9.16. Header Object 9.16. Header Object
Copyright (c) 2019 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BEGIN BEGIN
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeHeader-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
skipping to change at page 140, line 51 skipping to change at page 130, line 25
11. IANA Considerations 11. IANA Considerations
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. Fourteen conforming to a registry mechanism described in [RFC3688]. Fourteen
URI assignments have been registered by the IANA. URI assignments have been registered by the IANA.
Registration request for the RDE CSV namespace: Registration request for the RDE CSV namespace:
URI: urn:ietf:params:xml:ns:rdeCsv-1.0 URI: urn:ietf:params:xml:ns:rdeCsv-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE CSV XML schema: Registration request for the RDE CSV XML schema:
URI: urn:ietf:params:xml:schema:rdeCsv-1.0 URI: urn:ietf:params:xml:schema:rdeCsv-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.1 of this document.
Registration request for the RDE domain namespace: Registration request for the RDE domain namespace:
URI: urn:ietf:params:xml:ns:rdeDomain-1.0 URI: urn:ietf:params:xml:ns:rdeDomain-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE domain XML schema: Registration request for the RDE domain XML schema:
URI: urn:ietf:params:xml:schema:rdeDomain-1.0 URI: urn:ietf:params:xml:schema:rdeDomain-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.2 of this document.
Registration request for the CSV domain namespace: Registration request for the CSV domain namespace:
URI: urn:ietf:params:xml:ns:csvDomain-1.0 URI: urn:ietf:params:xml:ns:csvDomain-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV domain XML schema: Registration request for the CSV domain XML schema:
URI: urn:ietf:params:xml:schema:csvDomain-1.0 URI: urn:ietf:params:xml:schema:csvDomain-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.3 of this document.
Registration request for the RDE host namespace: Registration request for the RDE host namespace:
URI: urn:ietf:params:xml:ns:rdeHost-1.0 URI: urn:ietf:params:xml:ns:rdeHost-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE host XML schema: Registration request for the RDE host XML schema:
URI: urn:ietf:params:xml:schema:rdeHost-1.0 URI: urn:ietf:params:xml:schema:rdeHost-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.4 of this document.
Registration request for the CSV host namespace: Registration request for the CSV host namespace:
URI: urn:ietf:params:xml:ns:csvHost-1.0 URI: urn:ietf:params:xml:ns:csvHost-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV host XML schema: Registration request for the CSV host XML schema:
URI: urn:ietf:params:xml:schema:csvHost-1.0 URI: urn:ietf:params:xml:schema:csvHost-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.5 of this document.
Registration request for the RDE contact namespace: Registration request for the RDE contact namespace:
URI: urn:ietf:params:xml:ns:rdeContact-1.0 URI: urn:ietf:params:xml:ns:rdeContact-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE contact XML schema: Registration request for the RDE contact XML schema:
URI: urn:ietf:params:xml:schema:rdeContact-1.0 URI: urn:ietf:params:xml:schema:rdeContact-1.0
Registrant Contact: See the "Author's Address" section of this
document.
See the "Formal Syntax" section of this document. Registrant Contact: IETF <regext@ietf.org>
See section Section 9.6 of this document.
Registration request for the CSV contact namespace: Registration request for the CSV contact namespace:
URI: urn:ietf:params:xml:ns:csvContact-1.0 URI: urn:ietf:params:xml:ns:csvContact-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV contact XML schema: Registration request for the CSV contact XML schema:
URI: urn:ietf:params:xml:schema:csvContact-1.0 URI: urn:ietf:params:xml:schema:csvContact-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.7 of this document.
Registration request for the RDE registrar namespace: Registration request for the RDE registrar namespace:
URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE registrar XML schema: Registration request for the RDE registrar XML schema:
URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.8 of this document.
Registration request for the CSV registrar namespace: Registration request for the CSV registrar namespace:
URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV registrar XML schema: Registration request for the CSV registrar XML schema:
URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.9 of this document.
Registration request for the RDE IDN namespace: Registration request for the RDE IDN namespace:
URI: urn:ietf:params:xml:ns:rdeIDN-1.0 URI: urn:ietf:params:xml:ns:rdeIDN-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE IDN XML schema: Registration request for the RDE IDN XML schema:
URI: urn:ietf:params:xml:schema:rdeIDN-1.0 URI: urn:ietf:params:xml:schema:rdeIDN-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.10 of this document.
Registration request for the CSV IDN namespace: Registration request for the CSV IDN namespace:
URI: urn:ietf:params:xml:ns:csvIDN-1.0 URI: urn:ietf:params:xml:ns:csvIDN-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV IDN XML schema: Registration request for the CSV IDN XML schema:
URI: urn:ietf:params:xml:schema:csvIDN-1.0 URI: urn:ietf:params:xml:schema:csvIDN-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.11 of this document.
Registration request for the RDE NNDN namespace: Registration request for the RDE NNDN namespace:
URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE NNDN XML schema: Registration request for the RDE NNDN XML schema:
URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.13 of this document.
Registration request for the CSV NNDN namespace: Registration request for the CSV NNDN namespace:
URI: urn:ietf:params:xml:ns:csvNNDN-1.0 URI: urn:ietf:params:xml:ns:csvNNDN-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV NNDN XML schema: Registration request for the CSV NNDN XML schema:
URI: urn:ietf:params:xml:schema:csvNNDN-1.0 URI: urn:ietf:params:xml:schema:csvNNDN-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
See the "Formal Syntax" section of this document. See section Section 9.14 of this document.
Registration request for the RDE EPP parameters namespace: Registration request for the RDE EPP parameters namespace:
URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0
Registrant Contact: See the "Author's Address" section of this Registrant Contact: IETF <regext@ietf.org>
document.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE EPP parameters XML schema: Registration request for the RDE EPP parameters XML schema:
URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0
Registrant Contact: See the "Author's Address" section of this
document.
See the "Formal Syntax" section of this document. Registrant Contact: IETF <regext@ietf.org>
See section Section 9.12 of this document.
12. Implementation Status 12. Implementation Status
Note to RFC Editor: Please remove this section and the reference to Note to RFC Editor: Please remove this section and the reference to
RFC 7942 [RFC7942] before publication. RFC 7942 [RFC7942] before publication.
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in RFC 7942 Internet-Draft, and is based on a proposal described in RFC 7942
[RFC7942]. The description of implementations in this section is [RFC7942]. The description of implementations in this section is
skipping to change at page 147, line 22 skipping to change at page 136, line 15
agreements-en agreements-en
13. Security Considerations 13. Security Considerations
This specification does not define the security mechanisms to be used This specification does not define the security mechanisms to be used
in the transmission of the data escrow deposits, since it only in the transmission of the data escrow deposits, since it only
specifies the minimum necessary to enable the rebuilding of a specifies the minimum necessary to enable the rebuilding of a
Registry from deposits without intervention from the original Registry from deposits without intervention from the original
Registry. Registry.
Depending on local policies, some elements or most likely, the whole Depending on local policies, some elements or, most likely, the whole
deposit will be considered confidential. As such the Registry deposit will be considered confidential. As such, the Registry
transmitting the data to the Escrow Agent SHOULD take all the transmitting the data to the Escrow Agent should take all the
necessary precautions like encrypting the data itself and/or the necessary precautions such as encrypting the data itself and/or the
transport channel to avoid inadvertent disclosure of private data. transport channel to avoid inadvertent disclosure of private data.
It is also of the utmost importance the authentication of the parties Authentication of the parties passing data escrow deposit files is
passing data escrow deposit files. The Escrow Agent SHOULD properly also of the utmost importance. The Escrow Agent SHOULD properly
authenticate the identity of the Registry before accepting data authenticate the identity of the Registry before accepting data
escrow deposits. In a similar manner, the Registry SHOULD escrow deposits. In a similar manner, the Registry SHOULD
authenticate the identity of the Escrow Agent before submitting any authenticate the identity of the Escrow Agent before submitting any
data. data.
Additionally, the Registry and the Escrow Agent SHOULD use integrity Additionally, the Registry and the Escrow Agent SHOULD use integrity
checking mechanisms to ensure the data transmitted is what the source checking mechanisms to ensure the data transmitted is what the source
intended. Validation of the contents by the Escrow Agent is intended. Validation of the contents by the Escrow Agent is
RECOMMENDED to ensure not only the file was transmitted correctly RECOMMENDED to ensure not only that the file was transmitted
from the Registry, but also the contents are also "meaningful". correctly from the Registry, but also that the contents are
"meaningful".
14. Privacy Considerations 14. Privacy Considerations
This specification defines a format that may be used to escrow This specification defines a format that may be used to escrow
personal data. The process of data escrow is governed by a legal personal data. The process of data escrow is governed by a legal
document agreed by the parties, and such legal document must regulate document agreed by the parties, and such legal document must regulate
the particularities regarding the protection of personal data. the particularities regarding the protection of personal data.
15. Acknowledgments 15. Acknowledgments
skipping to change at page 155, line 33 skipping to change at page 144, line 26
2. The example in idnLanguage CSV file definition updated to use the 2. The example in idnLanguage CSV file definition updated to use the
sep attribute. sep attribute.
3. The reference in the example in hostAddresses CSV file definition 3. The reference in the example in hostAddresses CSV file definition
was updated. was updated.
4. Moved [RFC0791] and [RFC4291] to the Normative References 4. Moved [RFC0791] and [RFC4291] to the Normative References
section. section.
17. Example of a full deposit using the XML model 16.18. Changes REGEXT 05 to REGEXT 06
Example of a full deposit using the XML model: 1. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/
nA8eTYIrXJ44_6ullQlRLW6T74s
17. Example of a Full Deposit using the XML model
Example of a Full Deposit using the XML model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit type="FULL" id="20191017001" <rde:deposit type="FULL" id="20191017001"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:rdeDomain="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"
skipping to change at page 161, line 5 skipping to change at page 150, line 5
</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="rdeDomain: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="20191017002" prevId="20191017001" <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:rdeDomain="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"
skipping to change at page 162, line 34 skipping to change at page 151, line 34
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1 uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1
</rdeHeader:count> </rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
</rdeHeader:count> </rdeHeader:count>
</rdeHeader:header> </rdeHeader:header>
</rde:contents> </rde:contents>
</rde:deposit> </rde:deposit>
19. Example of a full deposit using the CSV model 19. Example of a Full Deposit using the CSV model
Example of a full deposit using the CSV model: Example of a Full Deposit using the CSV model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit <rde:deposit
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
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"
skipping to change at page 171, line 37 skipping to change at page 160, line 37
</epp:recipient> </epp:recipient>
<epp:retention> <epp:retention>
<epp:indefinite/> <epp:indefinite/>
</epp:retention> </epp:retention>
</epp:statement> </epp:statement>
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
</rde:contents> </rde:contents>
</rde:deposit> </rde:deposit>
20. Example of differential deposit using the CSV model 20. Example of Differential Deposit using the CSV model
Example of a differential deposit using the CSV model: Example of a Differential Deposit using the CSV model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit <rde:deposit
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
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"
skipping to change at page 183, line 35 skipping to change at page 172, line 35
<https://www.rfc-editor.org/info/rfc5731>. <https://www.rfc-editor.org/info/rfc5731>.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
August 2009, <https://www.rfc-editor.org/info/rfc5732>. August 2009, <https://www.rfc-editor.org/info/rfc5732>.
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
August 2009, <https://www.rfc-editor.org/info/rfc5733>. August 2009, <https://www.rfc-editor.org/info/rfc5733>.
[RFC5891] Klensin, J., "Internationalized Domain Names in
Applications (IDNA): Protocol", RFC 5891,
DOI 10.17487/RFC5891, August 2010,
<https://www.rfc-editor.org/info/rfc5891>.
[RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS)
Security Extensions Mapping for the Extensible Security Extensions Mapping for the Extensible
Provisioning Protocol (EPP)", RFC 5910, Provisioning Protocol (EPP)", RFC 5910,
DOI 10.17487/RFC5910, May 2010, DOI 10.17487/RFC5910, May 2010,
<https://www.rfc-editor.org/info/rfc5910>. <https://www.rfc-editor.org/info/rfc5910>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
21.2. Informative References 21.2. Informative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
DOI 10.17487/RFC3912, September 2004, DOI 10.17487/RFC3912, September 2004,
<https://www.rfc-editor.org/info/rfc3912>. <https://www.rfc-editor.org/info/rfc3912>.
[RFC5891] Klensin, J., "Internationalized Domain Names in
Applications (IDNA): Protocol", RFC 5891,
DOI 10.17487/RFC5891, August 2010,
<https://www.rfc-editor.org/info/rfc5891>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
[variantTLDsReport] [variantTLDsReport]
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
(ICANN), "A Study of Issues Related to the Management of (ICANN), "A Study of Issues Related to the Management of
IDN Variant TLDs", February 2012, IDN Variant TLDs", February 2012,
<http://www.icann.org/en/topics/idn/idn-vip-integrated- <http://www.icann.org/en/topics/idn/idn-vip-integrated-
 End of changes. 161 change blocks. 
792 lines changed or deleted 270 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/