draft-ietf-regext-dnrd-objects-mapping-09.txt   draft-ietf-regext-dnrd-objects-mapping-10.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: February 13, 2021 C. Thippeswamy Expires: April 11, 2021 C. Thippeswamy
VeriSign VeriSign
Aug 12, 2020 Oct 08, 2020
Domain Name Registration Data (DNRD) Objects Mapping Domain Name Registration Data (DNRD) Objects Mapping
draft-ietf-regext-dnrd-objects-mapping-09 draft-ietf-regext-dnrd-objects-mapping-10
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 February 13, 2021. This Internet-Draft will expire on April 11, 2021.
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 10 skipping to change at page 2, line 10
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. XML Model . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. XML Model . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Glossary . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Glossary . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Conventions Used in This Document . . . . . . . . . . . . . . 7 4. Conventions Used in This Document . . . . . . . . . . . . . . 7
4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 7 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 7
4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 7 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 8
4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 7 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 8
4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 8 4.4. CSV Integrity Check . . . . . . . . . . . . . . . . . . . 8
4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 8 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 8
4.6. Conventions applicable to the CSV Model . . . . . . . . . 8 4.6. Conventions applicable to the CSV Model . . . . . . . . . 8
5. Object Description . . . . . . . . . . . . . . . . . . . . . 16 5. Object Description . . . . . . . . . . . . . . . . . . . . . 17
5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 16 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 17
5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 35 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 36
5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 45 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 46
5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 63 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 64
5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 71 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 72
5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 75 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 75
5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 80 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 80
5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 82 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 82
5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 82 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 82
5.10. DNRD Common Objects Collection . . . . . . . . . . . . . 85 5.10. DNRD Common Objects Collection . . . . . . . . . . . . . 85
6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 85 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 85
7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8. Data escrow agent extended verification process . . . . . . . 86 8. Data escrow agent extended verification process . . . . . . . 86
9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 87 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 87
9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 88 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 87
9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 97 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 97
9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 99 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 100
9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 103 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 103
9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 105 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 105
9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 107 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 107
9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 109 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 110
9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 115 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116
9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 118 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 119
9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 121 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 122
9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 122 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 123
9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 124 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 124
9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 125 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 125
9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 127 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 127
9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 129 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 129
9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 129 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 130
9.17. DNRD Common Objects . . . . . . . . . . . . . . . . . . . 131 9.17. DNRD Common Objects . . . . . . . . . . . . . . . . . . . 132
10. Internationalization Considerations . . . . . . . . . . . . . 131 10. Internationalization Considerations . . . . . . . . . . . . . 132
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 131 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 132
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 139 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 140
12.1. Implementation in the gTLD space . . . . . . . . . . . . 140 12.1. Implementation in the gTLD space . . . . . . . . . . . . 141
13. Security Considerations . . . . . . . . . . . . . . . . . . . 140 13. Security Considerations . . . . . . . . . . . . . . . . . . . 141
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 141 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 142
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 141 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 142
16. Change History . . . . . . . . . . . . . . . . . . . . . . . 142 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 143
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 . . . . . . . . . . . . . . 142 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 143
16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 142 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 143
16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 142 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 144
16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 143 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 144
16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 143 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 144
16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 144 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 145
16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 145 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 146
16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 145 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 146
16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 146 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 147
16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 146 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 147
16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 146 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 147
16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 146 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 147
16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 146 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 147
16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 146 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 147
16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 148 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 149
16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 148 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 149
16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 149 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 150
16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 149 16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 150
16.19. Changes REGEXT 06 to REGEXT 07 . . . . . . . . . . . . . 149 16.19. Changes REGEXT 06 to REGEXT 07 . . . . . . . . . . . . . 150
16.20. Changes REGEXT 07 to REGEXT 08 . . . . . . . . . . . . . 149 16.20. Changes REGEXT 07 to REGEXT 08 . . . . . . . . . . . . . 150
16.21. Changes REGEXT 08 to REGEXT 09 . . . . . . . . . . . . . 150 16.21. Changes REGEXT 08 to REGEXT 09 . . . . . . . . . . . . . 151
17. Example of a Full Deposit using the XML model . . . . . . . . 150 16.22. Changes REGEXT 09 to REGEXT 10 . . . . . . . . . . . . . 151
18. Example of Differential Deposit using the XML model . . . . . 155 17. Example of a Full Deposit using the XML model . . . . . . . . 151
19. Example of a Full Deposit using the CSV model . . . . . . . . 157 18. Example of Differential Deposit using the XML model . . . . . 157
20. Example of Differential Deposit using the CSV model . . . . . 166 19. Example of a Full Deposit using the CSV model . . . . . . . . 158
21. References . . . . . . . . . . . . . . . . . . . . . . . . . 176 20. Example of Differential Deposit using the CSV model . . . . . 167
21.1. Normative References . . . . . . . . . . . . . . . . . . 177 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 178
21.2. Informative References . . . . . . . . . . . . . . . . . 179 21.1. Normative References . . . . . . . . . . . . . . . . . . 178
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 180 21.2. Informative References . . . . . . . . . . . . . . . . . 181
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182
1. Introduction 1. Introduction
Registry Data Escrow is the process by which a registry periodically Registry Data Escrow (RDE) is the process by which a registry
submits data deposits to a third-party called an escrow agent. These periodically submits data deposits to a third-party called an escrow
deposits comprise the minimum data needed by a third-party to resume agent. These deposits comprise the minimum data needed by a third-
operations if the registry cannot function and is unable or unwilling party to resume operations if the registry cannot function and is
to facilitate an orderly transfer of service. For example, for a unable or unwilling to facilitate an orderly transfer of service.
domain name registry or registrar, the data to be deposited would For example, for a domain name registry or registrar, the data to be
include all the objects related to registered domain names, e.g., deposited would include all the objects related to registered domain
names, contacts, name servers, etc. names, e.g., names, contacts, name servers, etc.
The goal of data escrow is higher resiliency of registration The goal of data escrow is higher resiliency of registration
services, for the benefit of Internet users. The beneficiaries of a services, for the benefit of Internet users. The beneficiaries of a
registry are not just those registering information there, but also registry are not just those registering information there, but also
the users of services relying on the registry data. the users of services relying on the registry data.
In the context of domain name registries, registration data escrow is In the context of domain name registries, registration data escrow is
a requirement for generic top-level domains (e.g., Specification 2 of a requirement for generic top-level domains (e.g., Specification 2 of
the ICANN Base Registry Agreement, see [ICANN-GTLD-RA-20170731]) and the ICANN Base Registry Agreement, see [ICANN-GTLD-RA-20170731]) and
some country code top-level domain managers are also currently some country code top-level domain managers are also currently
skipping to change at page 5, line 5 skipping to change at page 5, line 9
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.
o EPP parameters: Definition of the specific EPP parameters o EPP parameters: Contains the EPP parameters supported by the
supported by the Registry Operator. Registry Operator.
o Header: Used to specify counters of objects in the database at a o Header: Used to specify counters of objects in the database at a
certain point in time (watermark). certain point in time (watermark).
o Policy: Used to specify OPTIONAL elements from this specification o Policy: Used to specify OPTIONAL elements from this specification
that are REQUIRED based on the business model of the registry. that are REQUIRED based on the business model of the registry.
Extensible Markup Language (XML) 1.0 as described in Extensible Markup Language (XML) 1.0 as described in
[W3C.REC-xml-20081126] and XML Schema notation as described in [W3C.REC-xml-20081126] and XML Schema notation as described in
[W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028] are [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028] are
skipping to change at page 7, line 52 skipping to change at page 8, line 15
4.2. Country names 4.2. Country names
Country identifiers SHALL be represented using two character Country identifiers SHALL be represented using two character
identifiers as specified in [ISO-3166-1]. identifiers as specified in [ISO-3166-1].
4.3. Telephone numbers 4.3. Telephone numbers
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 0x2B), followed by a country code defined in
[ITU-E164], followed by a dot (".", ASCII value 0x2E), followed by a
[ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by sequence of digits representing the telephone number.
a sequence of digits representing the telephone number.
4.4. Checksum 4.4. CSV Integrity Check
A checksum MAY be used to verify the integrity of the CSV files, for A checksum MAY be used to verify the integrity of the CSV files, for
example, if another layer (i.e., encryption of an archive containing example, if another layer (i.e., encryption of an archive containing
the deposit files) does not provide integrity. By default the CRC32 the deposit files) does not provide integrity. By default the CRC32
algorithm (see, 8.1.1.6.2 of [V42]) is used. A stronger algorithm, algorithm (see, 8.1.1.6.2 of [V42]) is used. A stronger algorithm,
such as SHA-256 (see, [RFC6234]) MAY be specified for enhanced such as SHA-256 (see, [RFC6234]) MAY be used for enhanced security if
security if required. required.
4.5. IP addresses 4.5. IP addresses
The syntax of IP addresses MUST conform to the text representation of The syntax of IP addresses MUST conform to the text representation of
either Internet Protocol Version 4 [RFC0791] or Internet Protocol either Internet Protocol Version 4 [RFC0791] or Internet Protocol
Version 6 [RFC4291]. Version 6 [RFC5952].
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 (see [I-D.ietf-regext-data-escrow]). 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, using the
object consisting of a parent "sample" CSV File Definition and a element <rdeCsv:csv> (see Section 4.6.2.1), for a Sample object
child "sampleStatuses" CSV File Definition. The primary key for the consisting of a parent "sample" CSV File Definition and a child
Sample object is the field <csvSample:fName> that is used as the "sampleStatuses" CSV File Definition. The primary key for the Sample
foreign key in the "sampleStatuses" CSV File Definition by specifying object is the field <csvSample:fName> that is used as the foreign key
the "parent=true" attribute. If a Sample record is updated or in the "sampleStatuses" CSV File Definition by specifying the
deleted in a Differential or Incremental Deposit, it should cascade "parent=true" attribute. If a Sample record is updated or deleted in
replace the data using the records included in the child a Differential or Incremental Deposit, it should cascade replace the
"sampleStatuses" CSV File Definition or cascade delete the existing data using the records included in the child "sampleStatuses" CSV
records in the child "sampleStatuses" CSV File Definition, File Definition or cascade delete the existing records in the child
respectively. "sampleStatuses" CSV File Definition, respectively.
<csvSample:contents> <csvSample:contents>
... ...
<rdeCsv:csv name="sample" sep=","> <rdeCsv:csv name="sample" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvSample:fName/> <csvSample:fName/>
<rdeCsv:fClID/> <rdeCsv:fClID/>
<rdeCsv:fCrRr/> <rdeCsv:fCrRr/>
<rdeCsv:fCrID/> <rdeCsv:fCrID/>
<rdeCsv:fCrDate/> <rdeCsv:fCrDate/>
skipping to change at page 10, line 48 skipping to change at page 11, line 14
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, as described in cksum Defines the checksum of the CSV file, as described in
Section 4.4, using the algorithm defined by the "cksumAlg" Section 4.4, using the algorithm defined by the "cksumAlg"
attribute. If the "cksumAlg" attribute is not present, the attribute. If the "cksumAlg" attribute is not present, the
checksum is calculated using "CRC32". checksum is calculated using "CRC32".
cksumAlg Defines the checksum algorithm used to calculate the cksumAlg Defines the checksum algorithm used to calculate the
"cksum" attribute, with the default value of "CRC32". If this "cksum" attribute, with the default value of "CRC32". If the
attribute is present, the "cksum" attribute MUST also be value "SHA256" is specified, the SHA-256 algorithm (see,
present. The supported checksum algorithms are negotiated out- [RFC6234]) MUST be used to calculate the "cksum" attribute.
of-band. Parties receiving and processing data escrow deposits MUST
support CRC32 and SHA-256. If this attribute is present, the
"cksum" attribute MUST also be present. Additional checksum
algorithms are negotiated out-of-band.
The <rdeCsv:csv> element requires a "name" attribute that defines the The <rdeCsv:csv> element requires a "name" attribute that defines the
purpose of the CSV file with values like "domain", "host", "contact". purpose of the CSV file with values like "domain", "host", "contact".
The supported "name" attribute values are defined for each object The supported "name" attribute values are defined for each object
type. The OPTIONAL "sep" attribute defines the CSV separator type. The OPTIONAL "sep" attribute defines the CSV separator
character with the default separator character of ",". character with the default separator character of ",". The need for
quoting/escaping of the CSV data could be avoided by choosing a
separator character that is not in the data set of the CSV files.
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 11, line 50 skipping to change at page 12, line 42
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
The following is example of the "domain-YYYYMMDD.csv" file with one The following is example of the "domain-YYYYMMDD.csv" file with one
record matching the <rdeCsv:fields> definition. record matching the <rdeCsv:fields> definition.
domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX,
clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
The following is an example of the <csvDomain:deletes> <rdeCsv:csv> The following is an example of the <csvDomain:deletes> <rdeCsv:csv>
element for domain name records. element for domain name records.
<csvDomain:deletes> <csvDomain:deletes>
... ...
<rdeCsv:csv name="domain"> <rdeCsv:csv name="domain">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
skipping to change at page 13, line 19 skipping to change at page 14, line 19
<rdeCsv:fClID> Identifier of the client (registrar) that sponsors <rdeCsv:fClID> Identifier of the client (registrar) that sponsors
the object with type="eppcom:clIDType" and isRequired="true". the object with type="eppcom:clIDType" and isRequired="true".
<rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
of the client that created the object with type="eppcom:clIDType". of the client that created the object with type="eppcom:clIDType".
<rdeCsv:fCrID> Identifier of the client that created the object with <rdeCsv:fCrID> Identifier of the client that created the object with
type="eppcom:clIDType". type="eppcom:clIDType".
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the object with type="eppcom:clIDType". of the client that last updated the object with
<rdeCsv:fUpID> Identifier of the client that updated the object with
type="eppcom:clIDType". type="eppcom:clIDType".
<rdeCsv:fUpID> Identifier of the client that last updated the object
with type="eppcom:clIDType".
<rdeCsv:fReRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fReRr> Identifier of the registrar, defined in Section 5.4,
of the client that requested the transfer with of the client that requested the transfer with
type="eppcom:clIDType" and isRequired="true". type="eppcom:clIDType" and isRequired="true".
<rdeCsv:fReID> Identifier of the client that requested the transfer <rdeCsv:fReID> Identifier of the client that requested the transfer
with type="eppcom:clIDType". with type="eppcom:clIDType".
<rdeCsv:fAcRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fAcRr> Identifier of the registrar, defined in Section 5.4,
of the client that should take or took action with of the client that should take or took action with
type="eppcom:clIDType" and isRequired="true". type="eppcom:clIDType" and isRequired="true".
skipping to change at page 19, line 10 skipping to change at page 20, line 10
o An OPTIONAL <upDate> element that contains the date and time of o An OPTIONAL <upDate> element that contains the date and time of
the most recent domain-name-object modification. This element the most recent domain-name-object modification. This element
MUST NOT be present if the domain name object has never been MUST NOT be present if the domain name object has never been
modified. modified.
o An OPTIONAL <secDNS> element that contains the public key o An OPTIONAL <secDNS> element that contains the public key
information associated with Domain Name System security (DNSSEC) information associated with Domain Name System security (DNSSEC)
extensions for the domain name as specified in [RFC5910]. extensions for the domain name as specified in [RFC5910].
o An OPTIONAL <trDate> element that contains the date and time of o An OPTIONAL <trDate> element that contains the date and time of
the most recent domain object successful transfer. This element the most recent domain name object successful transfer. This
MUST NOT be present if the domain name object has never been element MUST NOT be present if the domain name object has never
transferred. been transferred.
o An OPTIONAL <trnData> element that contains the following child o An OPTIONAL <trnData> element that contains the following child
elements related to the last transfer request of the domain name elements related to the last transfer request of the domain name
object. This element MUST NOT be present if a transfer request object. This element MUST NOT be present if a transfer request
for the domain name has never been created. for the domain name has never been created.
* 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
skipping to change at page 20, line 5 skipping to change at page 21, line 5
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 name object:
... ...
<rdeDomain:domain> <rdeDomain:domain>
<rdeDomain:name>xn--exampl-gva.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:idnTableId>pt-BR</rdeDomain:idnTableId>
<rdeDomain:originalName>example.example</rdeDomain:originalName> <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>
<rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
<rdeDomain:exDate>2015-04-03T22:00:00.0Z</rdeDomain:exDate> <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate>
</rdeDomain:domain> </rdeDomain:domain>
... ...
5.1.1.2. <rdeDomain:delete> object 5.1.1.2. <rdeDomain:delete> object
The <rdeDomain:delete> element contains the fully-qualified domain The <rdeDomain:delete> element contains the fully-qualified domain
name that was deleted and purged. name that was deleted and purged.
Example of <rdeDomain:delete> object: Example of <rdeDomain:delete> object:
skipping to change at page 22, line 13 skipping to change at page 23, line 13
"domain" <rdeCsv:csv> <rdeCsv:fields> element: "domain" <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fRoid> Registry Object IDentifier (ROID) for the domain name <rdeCsv:fRoid> Registry Object IDentifier (ROID) for the domain name
object with isRequired="true". object with isRequired="true".
<rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of: <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of:
<rdeCsv:fClID> Identifier of the sponsoring client with <rdeCsv:fClID> Identifier of the sponsoring client with
isRequired="true". isRequired="true".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with <csvRegistrar:fGurid> Contains the Globally Unique Registrar
type="positiveInteger". The attribute "isRequired" MUST equal Identifier (GURID) assigned by ICANN with
"true". type="positiveInteger" and "isRequired"="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.6.2.2), MAY be used in the "domain" <rdeCsv:csv> elements (Section 4.6.2.2), MAY be used in the "domain" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
of the client that created the object. of the client that created the domain name object.
<rdeCsv:fCrID> Identifier of the client that created the domain name <rdeCsv:fCrID> Identifier of the client that created the domain name
object. object.
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the object. of the client that last updated the domain name object.
<rdeCsv:fUpID> Identifier of the client that last updated the domain <rdeCsv:fUpID> Identifier of the client that last updated the domain
name object. name object.
<rdeCsv:fUName> UTF8 encoded domain name for the <csvDomain:fName> <rdeCsv:fUName> UTF8 encoded domain name for the <csvDomain:fName>
field element. field element.
<rdeCsv:fIdnTableId> IDN Table Identifier used for the IDN domain <rdeCsv:fIdnTableId> IDN Table Identifier used for the IDN domain
name object that MUST match a <rdeCsv:fIdnTableId> field element name object that MUST match a <rdeCsv:fIdnTableId> field element
in the "idnLanguage" CSV files, as defined in Section 5.5.2. in the "idnLanguage" CSV files, as defined in Section 5.5.2.
<rdeCsv:fRegistrant> Registrant contact identifier for the domain <rdeCsv:fRegistrant> Registrant contact identifier for the domain
name object. name object.
<rdeCsv:fCrDate> Created date and time of the domain name object. <rdeCsv:fCrDate> Created date and time of the domain name object.
<rdeCsv:fUpDate> Date and time of the last update to the domain name <rdeCsv:fUpDate> Date and time of the last update to the domain name
object. object. This field MUST NOT be set if the domain name object has
never been modified.
<rdeCsv:fExDate> Expiration date and time for the domain name <rdeCsv:fExDate> Expiration date and time for the domain name
object. object.
<rdeCsv:fTrDate> Date and time of the last transfer for the domain <rdeCsv:fTrDate> Date and time of the last transfer for the domain
name object. name object. This field MUST NOT be set if the domain name object
has never been transferred.
Example of a "domain" <csvDomain:contents> <rdeCsv:csv> element. Example of a "domain" <csvDomain:contents> <rdeCsv:csv> element.
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domain"> <rdeCsv:csv name="domain">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
skipping to change at page 23, line 43 skipping to change at page 25, line 11
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding domain-YYYYMMDD.csv file. The file Example of the corresponding domain-YYYYMMDD.csv file. The file
contains four records (two active ASCII domains, original IDN with contains four records (two active ASCII domains, original IDN with
LANG-1 language rules, and variant IDN with LANG-1 language rules). LANG-1 language rules, and variant IDN with LANG-1 language rules).
domain1.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,2025-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,2025-04-03T22:00:00.0Z
xn--bc123-3ve.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,2025-04-03T22:00:00.0Z
xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.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,2025-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"
CSV File Definition (Section 5.1.2.1.1), MUST be used in the CSV File Definition (Section 5.1.2.1.1), MUST be used in the
"domainContacts" <rdeCsv:csv> <rdeCsv:fields> element: "domainContacts" <rdeCsv:csv> <rdeCsv:fields> element:
skipping to change at page 25, line 45 skipping to change at page 27, line 22
type="domain:statusValueType" and isRequired="true". type="domain:statusValueType" and isRequired="true".
<csvDomain:fRgpStatus> The RGP status, as a sub-status of the <csvDomain:fRgpStatus> The RGP status, as a sub-status of the
<csvDomain:fStatus> "pendingDelete" status value, with <csvDomain:fStatus> "pendingDelete" status value, with
type="rgp:statusValueType" as defined in [RFC3915]. type="rgp:statusValueType" as defined in [RFC3915].
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.6.2.2), MAY be used in the "domainStatuses" elements (Section 4.6.2.2), MAY be used in the "domainStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fStatusDescription> Domain object status description which <rdeCsv:fStatusDescription> Domain name object status description
is free form text describing the rationale for the status. which is free form text describing the rationale for the status.
<rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field. <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
Example of a "domainStatuses" <csvDomain:contents> <rdeCsv:csv> Example of a "domainStatuses" <csvDomain:contents> <rdeCsv:csv>
element. element.
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domainStatuses"> <rdeCsv:csv name="domainStatuses">
skipping to change at page 28, line 23 skipping to change at page 29, line 45
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--bc123-3ve.example,Hns1_example_test-TEST xn--bc123-3ve.example,Hns1_example_test-TEST
xn--bc123-3ve.example,Hns2_example_test-TEST xn--bc123-3ve.example,Hns2_example_test-TEST
xn--bc321-3ve.example,Hns1_example_test-TEST xn--bc321-3ve.example,Hns1_example_test-TEST
xn--bc321-3ve.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 domain host
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:
<csvDomain:fName> Domain name using the delegated host with host <csvDomain:fName> Domain name using the delegated host with host
<csvHost:fName> and isRequired="true". <csvHost:fName> and isRequired="true".
The following "rdeCsv" fields, defined in section Host CSV model The following "rdeCsv" fields, defined in section Host CSV model
skipping to change at page 30, line 47 skipping to change at page 32, line 23
<csvDomain:fMaxSigLife> Indicates a child's preference for the <csvDomain:fMaxSigLife> Indicates a child's preference for the
number of seconds after signature generation when the parent's number of seconds after signature generation when the parent's
signature on the DS information provided by the child will expire signature on the DS information provided by the child will expire
with type="secDNS:maxSigLifeType" defined in [RFC5910]. with type="secDNS:maxSigLifeType" defined in [RFC5910].
The following "domain" fields, defined for the "domain" CSV File The following "domain" fields, defined for the "domain" CSV File
Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" Definition (Section 5.1.2.1.1), MUST be used in the "dnssec"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvDomain:fName> Domain name of the domain object associated with <csvDomain:fName> Domain name of the domain name object associated
the DNSSEC record and isRequired="true". with the DNSSEC record and isRequired="true".
Example of a "dnssec" <csvDomain:contents> <rdeCsv:csv> element with Example of a "dnssec" <csvDomain:contents> <rdeCsv:csv> element with
the DS Data Interface of [RFC5910]: the DS Data Interface of [RFC5910]:
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="dnssec"> <rdeCsv:csv name="dnssec">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<csvDomain:fMaxSigLife/> <csvDomain:fMaxSigLife/>
skipping to change at page 31, line 33 skipping to change at page 33, line 8
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file
contains two DS records for domain1.example. contains two DS records for domain1.example.
domain1.example,604800,12345,3,1,49FD46E6C4B45C55D4AC domain1.example,604800,30730,8,2,91C9B176EB////F1C46F6A55
domain1.example,604800,12346,3,1,38EC35D5B3A34B44C39B domain1.example,604800,61882,8,2,9F8FEAC94B////1272AF09F3
Example of a "dnssec" <csvDomain:contents> <rdeCsv:csv> element with Example of a "dnssec" <csvDomain:contents> <rdeCsv:csv> element with
the Key Data Interface of [RFC5910]: the Key Data Interface of [RFC5910]:
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="dnssec"> <rdeCsv:csv name="dnssec">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
<csvDomain:fMaxSigLife/> <csvDomain:fMaxSigLife/>
<csvDomain:fFlags/> <csvDomain:fFlags/>
skipping to change at page 32, line 32 skipping to change at page 33, line 39
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file
contains two key records for domain1.example. contains two key records for domain1.example.
domain1.example,604800,257,3,1,AQPJ////4Q== domain1.example,604800,257,3,8,AwEAAZD1+z////G1jqviK8c=
domain1.example,604800,257,3,1,AQPJ////4QQQ domain1.example,604800,257,3,8,AwEAAbntWP////vwDitt940=
5.1.2.1.7. "domainTransfer" CSV File Definition 5.1.2.1.7. "domainTransfer" CSV File Definition
The "domainTransfer" CSV File Definition defines the fields and CSV The "domainTransfer" CSV File Definition defines the fields and CSV
file references used for the domain name object pending and completed file references used for the domain name object pending and completed
transfer records. No additional field elements were added for use in transfer records. No additional field elements were added for use in
the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element. the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element.
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.6.2.2), MUST be used in the "domainTransfer" elements (Section 4.6.2.2), MUST be used in the "domainTransfer"
skipping to change at page 33, line 31 skipping to change at page 34, line 37
<rdeCsv:fReID> Identifier of the client that requested the transfer. <rdeCsv:fReID> Identifier of the client that requested the transfer.
<rdeCsv:fAcID> Identifier of the client that should take or took <rdeCsv:fAcID> Identifier of the client that should take or took
action for transfer. action for transfer.
The following "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 "domainTransfer" Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvDomain:fName> Domain name of the domain object involved in the <csvDomain:fName> Domain name of the domain name object involved in
transfer with isRequired="true". the transfer with isRequired="true".
Example of a "domainTransfer" <csvDomain:contents> <rdeCsv:csv> Example of a "domainTransfer" <csvDomain:contents> <rdeCsv:csv>
element. element.
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domainTransfer"> <rdeCsv:csv name="domainTransfer">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
skipping to change at page 34, line 39 skipping to change at page 35, line 39
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
... ...
Example of the corresponding domainTransfer-YYYYMMDD.csv file. The Example of the corresponding domainTransfer-YYYYMMDD.csv file. The
file contains one domain transfer record with a pending status. file contains one domain transfer record with a pending status.
domain1.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 2025-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.
skipping to change at page 39, line 10 skipping to change at page 40, line 10
host object with isRequired="true". host object with isRequired="true".
The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the
"host" <rdeCsv:csv> <rdeCsv:fields> element: "host" <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of: <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of:
<rdeCsv:fClID> Identifier of the sponsoring client with <rdeCsv:fClID> Identifier of the sponsoring client with
isRequired="true". isRequired="true".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with <csvRegistrar:fGurid> Contains the Globally Unique Registrar
type="positiveInteger". The attribute "isRequired" MUST equal Identifier (GURID) assigned by ICANN with
"true". type="positiveInteger" and "isRequired"="true".
<rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
of the client that created the object. of the client that created the host object.
<rdeCsv:fCrID> Identifier of the client that created the host <rdeCsv:fCrID> Identifier of the client that created the host
object. object.
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the object. of the client that last updated the host object.
<rdeCsv:fUpID> Identifier of the client that last updated the host <rdeCsv:fUpID> Identifier of the client that last updated the host
object. object.
<rdeCsv:fCrDate> Date and time that the host object was created. <rdeCsv:fCrDate> Date and time that the host object was created.
<rdeCsv:fUpDate> Date and time that the host object was last <rdeCsv:fUpDate> Date and time that the host object was last
updated. updated. This field MUST NOT be set if the domain name object has
never been modified.
<rdeCsv:fTrDate> Date and time that the host was last transferred. <rdeCsv:fTrDate> Date and time that the host object was last
transferred. This field MUST NOT be set if the domain name object
has never been transferred.
Example of a "host" <csvHost:contents> <rdeCsv:csv> element. Example of a "host" <csvHost:contents> <rdeCsv:csv> element.
... ...
<csvHost:contents> <csvHost:contents>
... ...
<rdeCsv:csv name="host"> <rdeCsv:csv name="host">
<rdeCsv:fields> <rdeCsv:fields>
<csvHost:fName/> <csvHost:fName/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
skipping to change at page 42, line 6 skipping to change at page 42, line 52
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fRoid> Host object Registry Object IDentifier (ROID) <rdeCsv:fRoid> Host object Registry Object IDentifier (ROID)
assigned to the host object with isRequired="true". assigned to the host object with isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.6.2.2), MAY be used in the "hostStatuses" elements (Section 4.6.2.2), MAY be used in the "hostStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fStatusDescription> Host object status description which is <rdeCsv:fStatusDescription> Host object status description which is
free form text describing the rationale for the status. The free form text describing the rationale for the status.
attribute "isRequired" MUST equal "true".
<rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field. <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
Example of a "hostStatuses" <csvHost:contents> <rdeCsv:csv> element. Example of a "hostStatuses" <csvHost:contents> <rdeCsv:csv> element.
... ...
<csvHost:contents> <csvHost:contents>
... ...
<rdeCsv:csv name="hostStatuses"> <rdeCsv:csv name="hostStatuses">
<rdeCsv:fields> <rdeCsv:fields>
skipping to change at page 50, line 45 skipping to change at page 51, line 45
"contact" <rdeCsv:csv> <rdeCsv:fields> element: "contact" <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fRoid> The Registry Object IDentifier (ROID) for the contact <rdeCsv:fRoid> The Registry Object IDentifier (ROID) for the contact
object with isRequired="true". object with isRequired="true".
<rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of: <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of:
<rdeCsv:fClID> Identifier of the sponsoring client with <rdeCsv:fClID> Identifier of the sponsoring client with
isRequired="true". isRequired="true".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with <csvRegistrar:fGurid> Contains the Globally Unique Registrar
type="positiveInteger". The attribute "isRequired" MUST equal Identifier (GURID) assigned by ICANN with
"true". type="positiveInteger" and "isRequired"="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.6.2.2), MAY be used in the "contact" <rdeCsv:csv> elements (Section 4.6.2.2), MAY be used in the "contact" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
of the client that created the object. of the client that created the contact object.
<rdeCsv:fCrID> Identifier of the client that created the contact <rdeCsv:fCrID> Identifier of the client that created the contact
object. object.
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the object. of the client that last updated the contact object.
<rdeCsv:fUpID> Identifier of the client that last updated the <rdeCsv:fUpID> Identifier of the client that last updated the
contact object. contact object.
<rdeCsv:fCrDate> Created date and time of the contact object. <rdeCsv:fCrDate> Created date and time of the contact object.
<rdeCsv:fUpDate> Date and time of the last update to the contact <rdeCsv:fUpDate> Date and time of the last update to the contact
object. object. This field MUST NOT be set if the domain name object has
never been modified.
<rdeCsv:fTrDate> Date and time of the last transfer for the contact <rdeCsv:fTrDate> Date and time of the last transfer for the contact
object. object. This field MUST NOT be set if the domain name object has
never been transferred.
Example of a "contact" <csvContact:contacts> <rdeCsv:csv> element. Example of a "contact" <csvContact:contacts> <rdeCsv:csv> element.
... ...
<csvContact:contents> <csvContact:contents>
... ...
<rdeCsv:csv name="contact"> <rdeCsv:csv name="contact">
<rdeCsv:fields> <rdeCsv:fields>
<csvContact:fId/> <csvContact:fId/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
skipping to change at page 54, line 6 skipping to change at page 55, line 6
5.3.2.1.2. "contactStatuses" CSV File Definition 5.3.2.1.2. "contactStatuses" CSV File Definition
The "contactStatuses" CSV File Definition defines the fields and CSV The "contactStatuses" CSV File Definition defines the fields and CSV
file references used for the contact object statuses. file references used for the contact object statuses.
The following "csvContact" field elements, defined for the "contact" The following "csvContact" field elements, defined for the "contact"
CSV File Definition (Section 5.3.2.1.1), MUST be used in the CSV File Definition (Section 5.3.2.1.1), MUST be used in the
"contactStatuses" <rdeCsv:csv> <rdeCsv:fields> element: "contactStatuses" <rdeCsv:csv> <rdeCsv:fields> element:
<csvContact:fId> Server-unique contact identifier of status with <csvContact:fId> Server-unique contact identifier of status with
isRequired="true". isRequired="true" and parent="true".
<csvContact:fStatus> The status of the contact with <csvContact:fStatus> The status of the contact with
type="contact:statusValueType" and isRequired="true". type="contact:statusValueType" and isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.6.2.2), MAY be used in the "contactStatuses" elements (Section 4.6.2.2), MAY be used in the "contactStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fStatusDescription> The contact object status description <rdeCsv:fStatusDescription> The contact object status description
which is free form text describing the rationale for the status. which is free form text describing the rationale for the status.
skipping to change at page 55, line 35 skipping to change at page 56, line 35
<csvContact:fPostalType> Contains the form of the postal-address <csvContact:fPostalType> Contains the form of the postal-address
information with type="contact:postalLineType" and information with type="contact:postalLineType" and
isRequired="true". This field specifies the form ("int" or isRequired="true". This field specifies the form ("int" or
"loc"), as defined in Section 4.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 is 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 4.6.3.
<csvContact:fStreet> Contains the contact's street address line with <csvContact:fStreet> Contains the contact's street address line with
type="contact:fPostalLineType". An index attribute is required to type="contact:fPostalLineType". An index attribute is required to
indicate which street address line the field represents with index indicate which street address line the field represents with index
"0" for the first line and index "2" for the last line. An "0" for the first line and incrementing for each line up to index
OPTIONAL "isLoc" attribute to used to indicate the localized or "2" for the third line. An OPTIONAL "isLoc" attribute is used to
internationalized form as defined in section Section 4.6.3. indicate the localized or internationalized form as defined in
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 is used to indicate the localized or
internationalized form as defined in section Section 4.6.3. internationalized form as defined in 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 is used to indicate the localized or internationalized
form as defined in section Section 4.6.3. form as defined in Section 4.6.3.
The following "csvContact" field elements MAY be used in the The following "csvContact" field elements MAY be used in the
"contactPostal" <rdeCsv:csv> <rdeCsv:fields> element: "contactPostal" <rdeCsv:csv> <rdeCsv:fields> element:
<csvContact:fOrg> Contains the name of the organization with which <csvContact:fOrg> Contains the name of the organization with which
the contact is affiliated with type="contact:optPostalLineType". the contact is affiliated with type="contact:optPostalLineType".
An OPTIONAL "isLoc" attribute to used to indicate the localized or An OPTIONAL "isLoc" attribute is used to indicate the localized or
internationalized form as defined in section Section 4.6.3. internationalized form as defined in Section 4.6.3.
<csvContact:fSp> Contains the contact's state or province with <csvContact:fSp> Contains the contact's state or province with
type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute
to used to indicate the localized or internationalized form as is used to indicate the localized or internationalized form as
defined in section Section 4.6.3. defined in Section 4.6.3.
<csvContact:fPc> Contains the contact's postal code with <csvContact:fPc> Contains the contact's postal code with
type="contact:pcType". An OPTIONAL "isLoc" attribute to used to type="contact:pcType". An OPTIONAL "isLoc" attribute is 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 4.6.3.
The following "csvContact" fields, defined for the "contact" CSV File The following "csvContact" fields, defined for the "contact" CSV File
Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvContact:fId> Server-unique contact identifier for the contact <csvContact:fId> Server-unique contact identifier for the contact
object with isRequired="true". object with isRequired="true" and parent="true".
Example of a "contactPostal" <csvContact:contents> <rdeCsv:csv> Example of a "contactPostal" <csvContact:contents> <rdeCsv:csv>
element. element.
... ...
<csvContact:contents> <csvContact:contents>
... ...
<rdeCsv:csv name="contactPostal"> <rdeCsv:csv name="contactPostal">
<rdeCsv:fields> <rdeCsv:fields>
<csvContact:fId parent="true"/> <csvContact:fId parent="true"/>
skipping to change at page 63, line 47 skipping to change at page 64, line 47
The <registrar> element contains the following child elements: The <registrar> element contains the following child elements:
o An <id> element that contains the Registry-unique identifier of o An <id> element that contains the Registry-unique identifier of
the registrar object. This <id> has a superordinate relationship the registrar object. This <id> has a superordinate relationship
to a subordinate <clID>, <crRr> or <upRr> of domain, contact and to a subordinate <clID>, <crRr> or <upRr> of domain, contact and
host objects. host objects.
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 Globally Unique
ICANN. Registrar Identifier (GURID) assigned by 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 One 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,
skipping to change at page 65, line 9 skipping to change at page 66, line 9
registrar WHOIS server listening on TCP port 43 as specified in registrar WHOIS server listening on TCP port 43 as specified in
[RFC3912]. [RFC3912].
* An OPTIONAL <url> element that contains the name of the * An OPTIONAL <url> element that contains the name of the
registrar WHOIS server listening on TCP port 80/443. registrar WHOIS server listening on TCP port 80/443.
o An OPTIONAL <crDate> element that contains the date and time of o An OPTIONAL <crDate> element that contains the date and time of
registrar-object creation. registrar-object creation.
o An OPTIONAL <upDate> element that contains the date and time of o An OPTIONAL <upDate> element that contains the date and time of
the most recent RDE registrar-object modification. This element the most recent registrar-object modification. This element MUST
MUST NOT be present if the rdeRegistrar object has never been NOT be present if the registrar-object has never been modified.
modified.
Example of <registrar> object: Example of a <registrar> object:
... ...
<rdeRegistrar:registrar> <rdeRegistrar:registrar>
<rdeRegistrar:id>RegistrarX</rdeRegistrar:id> <rdeRegistrar:id>RegistrarX</rdeRegistrar:id>
<rdeRegistrar:name>Registrar X</rdeRegistrar:name> <rdeRegistrar:name>Registrar X</rdeRegistrar:name>
<rdeRegistrar:gurid>123</rdeRegistrar:gurid> <rdeRegistrar:gurid>8</rdeRegistrar:gurid>
<rdeRegistrar:status>ok</rdeRegistrar:status> <rdeRegistrar:status>ok</rdeRegistrar:status>
<rdeRegistrar:postalInfo type="int"> <rdeRegistrar:postalInfo type="int">
<rdeRegistrar:addr> <rdeRegistrar:addr>
<rdeRegistrar:street>123 Example Dr.</rdeRegistrar:street> <rdeRegistrar:street>123 Example Dr.</rdeRegistrar:street>
<rdeRegistrar:street>Suite 100</rdeRegistrar:street> <rdeRegistrar:street>Suite 100</rdeRegistrar:street>
<rdeRegistrar:city>Dulles</rdeRegistrar:city> <rdeRegistrar:city>Dulles</rdeRegistrar:city>
<rdeRegistrar:sp>VA</rdeRegistrar:sp> <rdeRegistrar:sp>VA</rdeRegistrar:sp>
<rdeRegistrar:pc>20166-6503</rdeRegistrar:pc> <rdeRegistrar:pc>20166-6503</rdeRegistrar:pc>
<rdeRegistrar:cc>US</rdeRegistrar:cc> <rdeRegistrar:cc>US</rdeRegistrar:cc>
</rdeRegistrar:addr> </rdeRegistrar:addr>
skipping to change at page 67, line 18 skipping to change at page 68, line 18
references used for the registrar object records. references used for the registrar object records.
The following "csvRegistrar" field elements MUST be used in the The following "csvRegistrar" field elements MUST be used in the
"registrar" <rdeCsv:csv> <rdeCsv:fields> element: "registrar" <rdeCsv:csv> <rdeCsv:fields> element:
<csvRegistrar:fId> or <csvRegistrar:fGurid> A choice of: <csvRegistrar:fId> or <csvRegistrar:fGurid> A choice of:
<csvRegistrar:fId> Contains the server-unique registrar <csvRegistrar:fId> Contains the server-unique registrar
identifier with type="eppcom:clIDType" and isRequired="true". identifier with type="eppcom:clIDType" and isRequired="true".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with <csvRegistrar:fGurid> Contains the Globally Unique Registrar
type="positiveInteger". The attribute "isRequired" MUST equal Identifier (GURID) assigned by ICANN with
"true". type="positiveInteger" and "isRequired"="true".
<csvRegistrar:fName> Contains the name of the registrar with <csvRegistrar:fName> Contains the name of the registrar with
type="normalizedString" and isRequired="true". type="normalizedString" and isRequired="true".
The following field elements MAY be used in the "registrar" The following field elements MAY be used in the "registrar"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvRegistrar:fStatus> Contains the status of the registrar with <csvRegistrar:fStatus> Contains the status of the registrar with
type="csvRegistrar:statusValueType". type="csvRegistrar:statusValueType".
skipping to change at page 67, line 47 skipping to change at page 68, line 47
<csvRegistrar:fWhoisUrl> Contains the Whois URL of the registrar <csvRegistrar:fWhoisUrl> Contains the Whois URL of the registrar
with type="anyURI". with type="anyURI".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.6.2.2), MAY be used in the "registrar" elements (Section 4.6.2.2), MAY be used in the "registrar"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fCrDate> Created date and time of the registrar object. <rdeCsv:fCrDate> Created date and time of the registrar object.
<rdeCsv:fUpDate> Date and time of the last update to the registrar <rdeCsv:fUpDate> Date and time of the last update to the registrar
object. object. This field MUST NOT be set if the domain name object has
never been modified.
<rdeCsv:fUrl> URL for the registrar web home page. <rdeCsv:fUrl> URL for the registrar web home page.
The following "csvContact" fields, defined in section Contact Object The following "csvContact" fields, defined in section Contact Object
(Section 5.3), MAY be used in the "registrar" <rdeCsv:csv> (Section 5.3), MAY be used in the "registrar" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<csvContact:fStreet> Registrar street address line with an "index" <csvContact:fStreet> Registrar street address line with an "index"
attribute that represents the order of the street address line attribute that represents the order of the street address line
from "0" to "2". An OPTIONAL "isLoc" attribute that is used to from "0" to "2". An OPTIONAL "isLoc" attribute that is used to
skipping to change at page 70, line 5 skipping to change at page 70, line 45
<rdeCsv:file <rdeCsv:file
cksum="57F6856F"> cksum="57F6856F">
registrar-YYYYMMDD.csv registrar-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvRegistrar:contents> </csvRegistrar:contents>
... ...
Example of the registrar-YYYYMMDD.csv file. The file contains three Example of the registrar-YYYYMMDD.csv file. The file contains one
registrar records. registrar record.
registrarX,"Example Inc.",1234,ok,"123 Example Dr.", registrarX,"Example Inc.",8,ok,"123 Example Dr.",
"Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,http://www.example.example,
http://whois.example.example,2005-04-23T11:49:00.0Z,
2009-02-17T17:51:00.0Z
registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.",
"Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,http://www.example.example,
http://whois.example.example,2005-04-23T11:49:00.0Z,
2009-02-17T17:51:00.0Z
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
skipping to change at page 70, line 44 skipping to change at page 71, line 25
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:
<csvRegistrar:fId> or <csvRegistrar:fGurid> A choice of: <csvRegistrar:fId> or <csvRegistrar:fGurid> A choice of:
<csvRegistrar:fId> Contains the server-unique registrar <csvRegistrar:fId> Contains the server-unique registrar
identifier with type="eppcom:clIDType" and isRequired="true". identifier with type="eppcom:clIDType" and isRequired="true".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with <csvRegistrar:fGurid> Contains the Globally Unique Registrar
Identifier (GURID) assigned by ICANN with
type="positiveInteger". The attribute "isRequired" MUST equal type="positiveInteger". The attribute "isRequired" MUST equal
"true". "true".
Example of a "registrar" <csvRegistrar:deletes> <rdeCsv:csv> element. Example of a "registrar" <csvRegistrar:deletes> <rdeCsv:csv> element.
... ...
<csvRegistrar:deletes> <csvRegistrar:deletes>
... ...
<rdeCsv:csv name="registrar"> <rdeCsv:csv name="registrar">
<rdeCsv:fields> <rdeCsv:fields>
skipping to change at page 73, line 19 skipping to change at page 73, line 44
The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be
used in the "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element: used in the "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fIdnTableId> The language identifier that matches the values <rdeCsv:fIdnTableId> The language identifier that matches the values
for the <rdeCsv:fIdnTableId> field element in the "domain" CSV for the <rdeCsv:fIdnTableId> field element in the "domain" CSV
File Definition (Section 5.1.2.1.1) files. The attribute File Definition (Section 5.1.2.1.1) files. The attribute
"isRequired" MUST equal "true". "isRequired" MUST equal "true".
<rdeCsv:fUrl> URL that defines the character code points that can be <rdeCsv:fUrl> URL that defines the character code points that can be
used for the language defined by the <rdeCsv:fLang> field element. used for <csvDomain:fName> field in the "domain" CSV File
The attribute "isRequired" MUST equal "true". Definition Section 5.1.2.1.1 files. The attribute "isRequired"
MUST equal "true".
Example of a "idnLanguage" <csvIDN:contents> <rdeCsv:csv> element. Example of a "idnLanguage" <csvIDN:contents> <rdeCsv:csv> element.
... ...
<csvIDN:contents> <csvIDN:contents>
... ...
<rdeCsv:csv name="idnLanguage" sep=","> <rdeCsv:csv name="idnLanguage" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fIdnTableId isRequired="true"/> <rdeCsv:fIdnTableId isRequired="true"/>
<rdeCsv:fUrl isRequired="true"/> <rdeCsv:fUrl isRequired="true"/>
skipping to change at page 76, line 17 skipping to change at page 76, line 41
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 an 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 an 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 name 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 an 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 name 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 uses the NS mirror mechanism, meaning that the
mirroringNS is true. If another mechanism such as DNAME is activated variant domain name (i.e., NNDN) is delegated in the
used, the value of mirroringNS attribute MUST be false. DNS using the same NS records as in the <originalName>. The
default value of mirroringNS is true. If another mechanism
such as DNAME is 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 an <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>
skipping to change at page 80, line 41 skipping to change at page 80, line 41
xn--bc456-3ve.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. A maximum of one EPP Parameters Object MUST
a certain point in time (watermark). exist at a certain point in time (watermark).
The syntax and content of the <rdeEppParams:eppParams> children The syntax and content of the <rdeEppParams:eppParams> children
elements is as explained in section 2.4 of [RFC5730]. The children elements is as explained in section 2.4 of [RFC5730]. The children
of the <eppParams> are as follows: of the <eppParams> are as follows:
o One or more <version> elements that indicate the EPP versions o One or more <version> elements that indicate the EPP versions
supported by the registry. supported by the registry.
o One or more <lang> elements that indicate the identifiers of the o One or more <lang> elements that indicate the identifiers of the
text response languages supported by the registry's EPP server. text response languages supported by the registry's EPP server.
skipping to change at page 82, line 21 skipping to change at page 82, line 21
Section 4.6.2.1, is used to specify which OPTIONAL fields are Section 4.6.2.1, is used to specify which OPTIONAL fields are
REQUIRED based on the business model of the registry. REQUIRED based on the business model of the registry.
5.8.1. <rdePolicy:policy> object 5.8.1. <rdePolicy:policy> object
The OPTIONAL <policy> contains the following attributes: The OPTIONAL <policy> contains the following attributes:
o An <element> that defines that the referenced <element> is o An <element> that defines that the referenced <element> is
REQUIRED. REQUIRED.
o <scope> that defines the XPath of the element referenced by o <scope> that defines the XPath (see, [W3C.REC-xpath-31-20170321])
<element>. of the element referenced by <element>.
Example of <rdePolicy:policy> object: Example of <rdePolicy:policy> object:
... ...
<rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain" <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain"
element="rdeDomain:registrant" /> element="rdeDomain:registrant" />
... ...
5.9. Header Object 5.9. Header Object
skipping to change at page 86, line 42 skipping to change at page 86, line 42
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 by following section
5.2 in [I-D.ietf-regext-data-escrow].
o If a Full Deposit is to be tested, the Full Deposit is the
dataset.
o If an Incremental Deposit is to be tested, the dataset is created
by using the Incremental Deposit plus the last previous Full
Deposit.
o If a Differential Deposit is to be tested, the dataset is created
by using the Differential Deposit plus all the required deposits
leading to the last previous Full Deposit.
The following are the minimum suggested tests on the dataset: 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.
skipping to change at page 87, line 45 skipping to change at page 87, line 32
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
This standard is specified in XML Schema notation. The formal syntax This standard is specified in XML Schema notation. The formal syntax
presented here is a complete schema representation suitable for presented here is a complete schema representation suitable for
automated validation. automated validation.
The BEGIN and END tags are not part of the schema; they are used to The <CODE BEGINS> and <CODE ENDS> tags are not part of the schema;
note the beginning and ending of the schema for URI registration they are used to note the beginning and ending of the schema for URI
purposes. registration purposes.
9.1. RDE CSV Schema 9.1. RDE CSV Schema
BEGIN <CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeCsv-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow Comma-Seperated Values (CSV) Registry Data Escrow Comma-Separated Values (CSV)
</documentation> </documentation>
</annotation> </annotation>
<!-- csv content element --> <!-- csv content element -->
<element name="csv" type="rdeCsv:csvType"/> <element name="csv"
type="rdeCsv:csvType" />
<!-- Definition of CSV file --> <!-- Definition of CSV file -->
<complexType name="csvType"> <complexType name="csvType">
<sequence> <sequence>
<element name="fields" type="rdeCsv:fieldsType"/> <element name="fields"
<element name="files" type="rdeCsv:filesType"/> type="rdeCsv:fieldsType" />
</sequence> <element name="files"
<attribute name="name" type="token" use="required"/> type="rdeCsv:filesType" />
<attribute name="sep" type="rdeCsv:sepType" default=","/> </sequence>
<attribute name="name"
type="token"
use="required" />
<attribute name="sep"
type="rdeCsv:sepType"
default="," />
</complexType> </complexType>
<!-- field seperator must be a single character --> <!-- field seperator must be a single character -->
<simpleType name="sepType"> <simpleType name="sepType">
<restriction base="string"> <restriction base="string">
<minLength value="1"/> <minLength value="1" />
<maxLength value="1"/> <maxLength value="1" />
</restriction> </restriction>
</simpleType> </simpleType>
<!-- Abstract field type -->
<element name="field"
type="rdeCsv:fieldType"
abstract="true" />
<complexType name="fieldType">
<sequence />
</complexType>
<!-- fieldType with optional value (isRequired=false) -->
<complexType name="fieldOptionalType">
<complexContent>
<extension base="rdeCsv:fieldType">
<sequence />
<attribute name="isRequired"
type="boolean"
default="false" />
<attribute name="parent"
type="boolean"
default="false" />
</extension>
</complexContent>
<!-- Abstract field type --> </complexType>
<element name="field" type="rdeCsv:fieldType" <!-- fieldType with required value (isRequired=false) -->
abstract="true"/> <complexType name="fieldRequiredType">
<complexContent>
<complexType name="fieldType"> <extension base="rdeCsv:fieldType">
<sequence/> <sequence />
</complexType> <attribute name="isRequired"
type="boolean"
<!-- fieldType with optional value (isRequired=false) --> default="true" />
<complexType name="fieldOptionalType"> <attribute name="parent"
<complexContent> type="boolean"
<extension base="rdeCsv:fieldType"> default="false" />
<sequence/> </extension>
<attribute name="isRequired" type="boolean" </complexContent>
default="false"/> </complexType>
<attribute name="parent" type="boolean" <!-- Concrete field types -->
default="false"/> <!-- UTF-8 Name field (e.g. domain name) -->
</extension> <element name="fUName"
</complexContent> type="rdeCsv:fNameType"
</complexType> substitutionGroup="rdeCsv:field" />
<complexType name="fNameType">
<!-- fieldType with required value (isRequired=false) --> <complexContent>
<complexType name="fieldRequiredType"> <extension base="rdeCsv:fieldOptionalType">
<complexContent> <sequence />
<extension base="rdeCsv:fieldType"> <attribute name="type"
<sequence/> type="token"
<attribute name="isRequired" type="boolean" default="eppcom\:labelType" />
default="true"/> </extension>
<attribute name="parent" type="boolean" </complexContent>
default="false"/> </complexType>
</extension> <complexType name="fNameRequiredType">
</complexContent> <complexContent>
</complexType> <extension base="rdeCsv:fieldRequiredType">
<sequence />
<!-- Concrete field types --> <attribute name="type"
type="token"
<!-- UTF-8 Name field (e.g. domain name) --> default="eppcom\:labelType" />
<element name="fUName" type="rdeCsv:fNameType" </extension>
substitutionGroup="rdeCsv:field"/> </complexContent>
<complexType name="fNameType"> </complexType>
<complexContent> <!-- Registry Object IDentifier (roid) field -->
<extension base="rdeCsv:fieldOptionalType"> <element name="fRoid"
<sequence/> type="rdeCsv:fRoidType"
<attribute name="type" type="token" substitutionGroup="rdeCsv:field" />
default="eppcom\:labelType"/> <complexType name="fRoidType">
</extension> <complexContent>
</complexContent> <extension base="rdeCsv:fieldRequiredType">
</complexType> <sequence />
<complexType name="fNameRequiredType"> <attribute name="type"
<complexContent> type="token"
<extension base="rdeCsv:fieldRequiredType"> default="eppcom\:roidType" />
<sequence/> </extension>
<attribute name="type" type="token" </complexContent>
default="eppcom\:labelType"/> </complexType>
</extension> <!-- Registrant field -->
</complexContent> <element name="fRegistrant"
</complexType> type="rdeCsv:fRegistrantType"
substitutionGroup="rdeCsv:field" />
<!-- Registry Object IDentifier (roid) field --> <complexType name="fRegistrantType">
<element name="fRoid" type="rdeCsv:fRoidType" <complexContent>
substitutionGroup="rdeCsv:field"/> <extension base="rdeCsv:fieldOptionalType">
<complexType name="fRoidType"> <sequence />
<complexContent> <attribute name="type"
<extension base="rdeCsv:fieldRequiredType"> type="token"
<sequence/> default="eppcom\:clIDType" />
<attribute name="type" type="token" </extension>
default="eppcom\:roidType"/> </complexContent>
</extension> </complexType>
</complexContent> <!-- Object Status Description -->
</complexType> <element name="fStatusDescription"
type="rdeCsv:fNormalizedStringType"
<!-- Registrant field --> substitutionGroup="rdeCsv:field" />
<element name="fRegistrant" type="rdeCsv:fRegistrantType" <!-- clID fields (fClID, fCrID, fUpID) -->
substitutionGroup="rdeCsv:field"/> <!-- Identifier of the client that sponsors the object -->
<complexType name="fRegistrantType"> <element name="fClID"
<complexContent> type="rdeCsv:fClIDRequiredType"
<extension base="rdeCsv:fieldOptionalType"> substitutionGroup="rdeCsv:field" />
<sequence/> <!-- Identifier of registrar of client
<attribute name="type" type="token"
default="eppcom\:clIDType"/>
</extension>
</complexContent>
</complexType>
<!-- Object Status Description -->
<element name="fStatusDescription"
type="rdeCsv:fNormalizedStringType"
substitutionGroup="rdeCsv:field"/>
<!-- clID fields (fClID, fCrID, fUpID) -->
<!-- Identifier of the client that sponsors the object -->
<element name="fClID" type="rdeCsv:fClIDRequiredType"
substitutionGroup="rdeCsv:field"/>
<!-- Identifier of registrar of client
that created the object --> that created the object -->
<element name="fCrRr" type="rdeCsv:fClIDType" <element name="fCrRr"
substitutionGroup="rdeCsv:field"/> type="rdeCsv:fClIDType"
<!-- Identifier of the client that created the object --> substitutionGroup="rdeCsv:field" />
<element name="fCrID" type="rdeCsv:fClIDType" <!-- Identifier of the client that created the object -->
substitutionGroup="rdeCsv:field"/> <element name="fCrID"
<!-- Identifier of registrar of client that type="rdeCsv:fClIDType"
substitutionGroup="rdeCsv:field" />
<!-- Identifier of registrar of client that
updated the object --> updated the object -->
<element name="fUpRr" type="rdeCsv:fClIDType" <element name="fUpRr"
substitutionGroup="rdeCsv:field"/> type="rdeCsv:fClIDType"
<!-- Identifier of the client that updated the object --> substitutionGroup="rdeCsv:field" />
<element name="fUpID" type="rdeCsv:fClIDType" <!-- Identifier of the client that updated the object -->
substitutionGroup="rdeCsv:field"/> <element name="fUpID"
<!-- Identifier of registrar of client that type="rdeCsv:fClIDType"
substitutionGroup="rdeCsv:field" />
<!-- Identifier of registrar of client that
requested the transfer --> requested the transfer -->
<element name="fReRr" type="rdeCsv:fClIDRequiredType" <element name="fReRr"
substitutionGroup="rdeCsv:field"/> type="rdeCsv:fClIDRequiredType"
<!-- Identifier of the client that requested substitutionGroup="rdeCsv:field" />
<!-- Identifier of the client that requested
the transfer --> the transfer -->
<element name="fReID" type="rdeCsv:fClIDType" <element name="fReID"
substitutionGroup="rdeCsv:field"/> type="rdeCsv:fClIDType"
<!-- Identifier of registrar client that substitutionGroup="rdeCsv:field" />
<!-- Identifier of registrar client that
should take or took action --> should take or took action -->
<element name="fAcRr" type="rdeCsv:fClIDRequiredType" <element name="fAcRr"
substitutionGroup="rdeCsv:field"/> type="rdeCsv:fClIDRequiredType"
<!-- Identifier of the client that should take or substitutionGroup="rdeCsv:field" />
<!-- Identifier of the client that should take or
took action --> took action -->
<element name="fAcID" type="rdeCsv:fClIDType" <element name="fAcID"
substitutionGroup="rdeCsv:field"/> type="rdeCsv:fClIDType"
<complexType name="fClIDType"> substitutionGroup="rdeCsv:field" />
<complexContent> <complexType name="fClIDType">
<extension base="rdeCsv:fieldOptionalType"> <complexContent>
<sequence/> <extension base="rdeCsv:fieldOptionalType">
<attribute name="type" type="token" <sequence />
default="eppcom\:clIDType"/> <attribute name="type"
</extension> type="token"
</complexContent> default="eppcom\:clIDType" />
</complexType> </extension>
<complexType name="fClIDRequiredType"> </complexContent>
<complexContent> </complexType>
<extension base="rdeCsv:fieldRequiredType"> <complexType name="fClIDRequiredType">
<sequence/> <complexContent>
<attribute name="type" type="token" <extension base="rdeCsv:fieldRequiredType">
default="eppcom\:clIDType"/> <sequence />
</extension> <attribute name="type"
</complexContent> type="token"
</complexType> default="eppcom\:clIDType" />
</extension>
<!-- dateTime fields (fCrDate, fUpDate, fExDate) --> </complexContent>
<element name="fCrDate" type="rdeCsv:fDateTimeType" </complexType>
substitutionGroup="rdeCsv:field"/> <!-- dateTime fields (fCrDate, fUpDate, fExDate) -->
<element name="fCrDate"
<element name="fUpDate" type="rdeCsv:fDateTimeType" type="rdeCsv:fDateTimeType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<element name="fExDate" type="rdeCsv:fDateTimeType" <element name="fUpDate"
substitutionGroup="rdeCsv:field"/> type="rdeCsv:fDateTimeType"
<!-- Date and time that transfer was requested --> substitutionGroup="rdeCsv:field" />
<element name="fReDate" type="rdeCsv:fRequiredDateTimeType" <element name="fExDate"
substitutionGroup="rdeCsv:field"/> type="rdeCsv:fDateTimeType"
<!-- Date and time of a required or completed response --> substitutionGroup="rdeCsv:field" />
<element name="fAcDate" type="rdeCsv:fRequiredDateTimeType" <!-- Date and time that transfer was requested -->
substitutionGroup="rdeCsv:field"/> <element name="fReDate"
<element name="fTrDate" type="rdeCsv:fDateTimeType" type="rdeCsv:fRequiredDateTimeType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<complexType name="fDateTimeType"> <!-- Date and time of a required or completed response -->
<complexContent> <element name="fAcDate"
<extension base="rdeCsv:fieldOptionalType"> type="rdeCsv:fRequiredDateTimeType"
<sequence/> substitutionGroup="rdeCsv:field" />
<attribute name="type" type="token" <element name="fTrDate"
default="dateTime"/> type="rdeCsv:fDateTimeType"
</extension> substitutionGroup="rdeCsv:field" />
</complexContent> <complexType name="fDateTimeType">
</complexType> <complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="dateTime" />
</extension>
</complexContent>
</complexType>
<complexType name="fRequiredDateTimeType"> <complexType name="fRequiredDateTimeType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="dateTime"/>
</extension>
</complexContent>
</complexType>
<!-- boolean type -->
<complexType name="fBooleanType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="boolean"/>
</extension>
</complexContent>
</complexType>
<complexType name="fRequiredBooleanType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="boolean"/>
</extension>
</complexContent>
</complexType>
<!-- unsignedByte type -->
<complexType name="fUnsignedByteType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="unsignedByte"/>
</extension>
</complexContent>
</complexType>
<complexType name="fRequiredUnsignedByteType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="unsignedByte"/>
</extension>
</complexContent>
</complexType>
<!-- unsignedShort type -->
<complexType name="fUnsignedShortType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="unsignedShort"/>
</extension>
</complexContent>
</complexType>
<complexType name="fRequiredUnsignedShortType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="unsignedShort"/>
</extension>
</complexContent>
</complexType>
<!-- hexBinary type -->
<complexType name="fHexBinaryType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="hexBinary"/>
</extension>
</complexContent>
</complexType>
<complexType name="fRequiredHexBinaryType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="hexBinary"/>
</extension>
</complexContent>
</complexType>
<!-- language type -->
<element name="fLang" type="rdeCsv:fLangType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fLangType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="language"/>
</extension>
</complexContent>
</complexType>
<!-- IDN Table Identifier -->
<element name="fIdnTableId" type="rdeCsv:fTokenType"
substitutionGroup="rdeCsv:field"/>
<!-- State of the most recent transfer request -->
<element name="fTrStatus" type="rdeCsv:fTrStatusType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fTrStatusType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="eppcom\:trStatusType"/>
</extension>
</complexContent>
</complexType>
<!-- General token type -->
<complexType name="fTokenType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="token"/>
</extension>
</complexContent>
</complexType>
<!-- General normalizedString type -->
<complexType name="fNormalizedStringType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="normalizedString"/>
</extension>
</complexContent>
</complexType>
<!-- positive integer type -->
<complexType name="fPositiveIntegerType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="positiveInteger"/>
</extension>
</complexContent>
</complexType>
<!-- Custom / extension field type -->
<element name="fCustom" type="rdeCsv:fCustomType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fCustomType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="name" type="token"/>
<attribute name="type" type="token"
default="token"/>
</extension>
</complexContent>
</complexType>
<!-- Ordered list of field definitions for the csv -->
<complexType name="fieldsType">
<sequence maxOccurs="unbounded">
<element ref="rdeCsv:field"/>
</sequence>
</complexType>
<!-- List of files -->
<complexType name="filesType">
<sequence>
<element name="file" type="rdeCsv:fileType"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<!-- File definition -->
<complexType name="fileType">
<simpleContent>
<extension base="token">
<attribute name="compression" type="token"/>
<attribute name="encoding" type="token"
default="UTF-8"/>
<attribute name="cksum" type="token"/>
<attribute name="cksumAlg" type="token"
default="CRC32"/>
</extension>
</simpleContent>
</complexType>
<!-- URL fields -->
<element name="fUrl" type="rdeCsv:anyURIType"
substitutionGroup="rdeCsv:field"/>
<complexType name="anyURIType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="anyURI"/>
</extension>
</complexContent>
</complexType>
<!--
End of schema.
-->
</schema>
END
9.2. RDE Domain Object
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="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:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:domain-1.0"/>
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1"/>
<import namespace="urn:ietf:params:xml:ns:rgp-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"/>
<annotation>
<documentation>
Registry Data Escrow Domain provisioning schema
</documentation>
</annotation>
<element name="abstractDomain"
type="rdeDomain:abstractContentType"
substitutionGroup="rde:content" abstract="true"/>
<element name="domain"
substitutionGroup="rdeDomain:abstractDomain"/>
<element name="delete"
type="rdeDomain:deleteType"
substitutionGroup="rde:delete"/>
<!-- Content Type -->
<complexType name="abstractContentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rdeCsv:fieldRequiredType">
<sequence> <sequence />
<element name="name" <attribute name="type"
type="eppcom:labelType"/> type="token"
<element name="roid" default="dateTime" />
type="eppcom:roidType"/>
<element name="uName"
type="eppcom:labelType" minOccurs="0"/>
<element name="idnTableId"
type="rdeIDN:idType" minOccurs="0"/>
<element name="originalName"
type="eppcom:labelType" minOccurs="0"/>
<element name="status"
type="domain:statusType" maxOccurs="11"/>
<element name="rgpStatus"
type="rgp:statusType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="registrant"
type="eppcom:clIDType" minOccurs="0"/>
<element name="contact"
type="domain:contactType"
minOccurs="0" maxOccurs="unbounded"/>
<element name="ns"
type="domain:nsType" minOccurs="0"/>
<element name="clID"
type="eppcom:clIDType"/>
<element name="crRr"
type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="crDate"
type="dateTime" minOccurs="0"/>
<element name="exDate"
type="dateTime" minOccurs="0"/>
<element name="upRr"
type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="upDate"
type="dateTime" minOccurs="0"/>
<element name="secDNS"
type="secDNS:dsOrKeyType" minOccurs="0"/>
<element name="trDate"
type="dateTime" minOccurs="0"/>
<element name="trnData"
type="rdeDomain:transferDataType"
minOccurs="0"/>
</sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- boolean type -->
<complexType name="transferDataType"> <complexType name="fBooleanType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="boolean" />
</extension>
</complexContent>
</complexType>
<complexType name="fRequiredBooleanType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="boolean" />
</extension>
</complexContent>
</complexType>
<!-- unsignedByte type -->
<complexType name="fUnsignedByteType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="unsignedByte" />
</extension>
</complexContent>
</complexType>
<complexType name="fRequiredUnsignedByteType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="unsignedByte" />
</extension>
</complexContent>
</complexType>
<!-- unsignedShort type -->
<complexType name="fUnsignedShortType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="unsignedShort" />
</extension>
</complexContent>
</complexType>
<complexType name="fRequiredUnsignedShortType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="unsignedShort" />
</extension>
</complexContent>
</complexType>
<!-- hexBinary type -->
<complexType name="fHexBinaryType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="hexBinary" />
</extension>
</complexContent>
</complexType>
<complexType name="fRequiredHexBinaryType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="hexBinary" />
</extension>
</complexContent>
</complexType>
<!-- language type -->
<element name="fLang"
type="rdeCsv:fLangType"
substitutionGroup="rdeCsv:field" />
<complexType name="fLangType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="language" />
</extension>
</complexContent>
</complexType>
<!-- IDN Table Identifier -->
<element name="fIdnTableId"
type="rdeCsv:fTokenType"
substitutionGroup="rdeCsv:field" />
<!-- State of the most recent transfer request -->
<element name="fTrStatus"
type="rdeCsv:fTrStatusType"
substitutionGroup="rdeCsv:field" />
<complexType name="fTrStatusType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="eppcom\:trStatusType" />
</extension>
</complexContent>
</complexType>
<!-- General token type -->
<complexType name="fTokenType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="token" />
</extension>
</complexContent>
</complexType>
<!-- General normalizedString type -->
<complexType name="fNormalizedStringType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="normalizedString" />
</extension>
</complexContent>
</complexType>
<!-- positive integer type -->
<complexType name="fPositiveIntegerType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="positiveInteger" />
</extension>
</complexContent>
</complexType>
<!-- Custom / extension field type -->
<element name="fCustom"
type="rdeCsv:fCustomType"
substitutionGroup="rdeCsv:field" />
<complexType name="fCustomType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="name"
type="token" />
<attribute name="type"
type="token"
default="token" />
</extension>
</complexContent>
</complexType>
<!-- Ordered list of field definitions for the csv -->
<complexType name="fieldsType">
<sequence maxOccurs="unbounded">
<element ref="rdeCsv:field" />
</sequence>
</complexType>
<!-- List of files -->
<complexType name="filesType">
<sequence> <sequence>
<element name="trStatus" <element name="file"
type="eppcom:trStatusType"/> type="rdeCsv:fileType"
<element name="reRr" maxOccurs="unbounded" />
type="rdeDnrdCommon:rrType"/>
<element name="reDate"
type="dateTime"/>
<element name="acRr"
type="rdeDnrdCommon:rrType"/>
<element name="acDate"
type="dateTime"/>
<element name="exDate"
type="dateTime" minOccurs="0"/>
</sequence> </sequence>
</complexType> </complexType>
<!-- File definition -->
<!-- Delete Type --> <complexType name="fileType">
<complexType name="deleteType"> <simpleContent>
<extension base="token">
<attribute name="compression"
type="token" />
<attribute name="encoding"
type="token"
default="UTF-8" />
<attribute name="cksum"
type="token" />
<attribute name="cksumAlg"
type="token"
default="CRC32" />
</extension>
</simpleContent>
</complexType>
<!-- URL fields -->
<element name="fUrl"
type="rdeCsv:anyURIType"
substitutionGroup="rdeCsv:field" />
<complexType name="anyURIType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rdeCsv:fieldOptionalType">
<sequence> <sequence />
<element name="name" <attribute name="type"
type="eppcom:labelType" minOccurs="0" type="token"
maxOccurs="unbounded"/> default="anyURI" />
</sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!--
End of schema.
-->
</schema> </schema>
END <CODE ENDS>
9.3. CSV Domain Object
BEGIN 9.2. RDE Domain Object
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvDomain-1.0" <CODE BEGINS>
xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<!-- <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
Import common element types <import namespace="urn:ietf:params:xml:ns:secDNS-1.1" />
--> <import namespace="urn:ietf:params:xml:ns:rgp-1.0" />
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:domain-1.0"/> <import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0" />
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1"/> <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
<import namespace="urn:ietf:params:xml:ns:rgp-1.0"/> <annotation>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<annotation>
<documentation> <documentation>
Domain Name Comma-Separated Values (CSV) Object Registry Data Escrow Domain provisioning schema
</documentation> </documentation>
</annotation> </annotation>
<element name="abstractDomain"
<!-- type="rdeDomain:abstractContentType"
Child elements of the <rde:contents> object substitutionGroup="rde:content"
--> abstract="true" />
<element name="contents" type="csvDomain:contentType" <element name="domain"
substitutionGroup="rde:content"/> substitutionGroup="rdeDomain:abstractDomain" />
<element name="delete"
<complexType name="contentType"> type="rdeDomain:deleteType"
substitutionGroup="rde:delete" />
<!-- Content Type -->
<complexType name="abstractContentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element name="name"
type="eppcom:labelType" />
<element name="roid"
type="eppcom:roidType" />
<element name="uName"
type="eppcom:labelType"
minOccurs="0" />
<element name="idnTableId"
type="rdeIDN:idType"
minOccurs="0" />
<element name="originalName"
type="eppcom:labelType"
minOccurs="0" />
<element name="status"
type="domain:statusType"
maxOccurs="11" />
<element name="rgpStatus"
type="rgp:statusType"
minOccurs="0"
maxOccurs="unbounded" />
<element name="registrant"
type="eppcom:clIDType"
minOccurs="0" />
<element name="contact"
type="domain:contactType"
minOccurs="0"
maxOccurs="unbounded" />
<element name="ns"
type="domain:nsType"
minOccurs="0" />
<element name="clID"
type="eppcom:clIDType" />
<element name="crRr"
type="rdeDnrdCommon:rrType"
minOccurs="0" />
<element name="crDate"
type="dateTime"
minOccurs="0" />
<element name="exDate"
type="dateTime"
minOccurs="0" />
<element name="upRr"
type="rdeDnrdCommon:rrType"
minOccurs="0" />
<element name="upDate"
type="dateTime"
minOccurs="0" />
<element name="secDNS"
type="secDNS:dsOrKeyType"
minOccurs="0" />
<element name="trDate"
type="dateTime"
minOccurs="0" />
<element name="trnData"
type="rdeDomain:transferDataType"
minOccurs="0" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="transferDataType">
<!-- <sequence>
Child elements of the <rde:deletes> object <element name="trStatus"
--> type="eppcom:trStatusType" />
<element name="deletes" type="csvDomain:deleteType" <element name="reRr"
substitutionGroup="rde:delete"/> type="rdeDnrdCommon:rrType" />
<element name="reDate"
<complexType name="deleteType"> type="dateTime" />
<element name="acRr"
type="rdeDnrdCommon:rrType" />
<element name="acDate"
type="dateTime" />
<element name="exDate"
type="dateTime"
minOccurs="0" />
</sequence>
</complexType>
<!-- Delete Type -->
<complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element name="name"
type="eppcom:labelType"
minOccurs="0"
maxOccurs="unbounded" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType>
<!-- Domain name field -->
<element name="fName" type="rdeCsv:fNameRequiredType"
substitutionGroup="rdeCsv:field"/>
<!-- RGP status field -->
<element name="fRgpStatus"
type="csvDomain:fRgpStatusType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fRgpStatusType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="rgp\:statusValueType"/>
</extension>
</complexContent>
</complexType>
<!-- Contact type field -->
<element name="fContactType" type="csvDomain:fContactsTypeType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fContactsTypeType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="domain\:contactAttrType"/>
</extension>
</complexContent>
</complexType>
<!-- DNSSEC field types -->
<!-- Maximum signature lifetime field -->
<element name="fMaxSigLife" type="csvDomain:fMaxSigLifeType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fMaxSigLifeType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="secDNS\:maxSigLifeType"/>
</extension>
</complexContent>
</complexType>
<!-- Key tag field -->
<element name="fKeyTag" type="rdeCsv:fRequiredUnsignedShortType"
substitutionGroup="rdeCsv:field"/>
<!-- DS Algorithm field -->
<element name="fDsAlg" type="rdeCsv:fRequiredUnsignedByteType"
substitutionGroup="rdeCsv:field"/>
<!-- Digest type field -->
<element name="fDigestType" type="rdeCsv:fRequiredUnsignedByteType"
substitutionGroup="rdeCsv:field"/>
<!-- Digest field -->
<element name="fDigest" type="rdeCsv:fRequiredHexBinaryType"
substitutionGroup="rdeCsv:field"/>
<!-- Flags field -->
<element name="fFlags" type="rdeCsv:fRequiredUnsignedShortType"
substitutionGroup="rdeCsv:field"/>
<!-- Protocol field -->
<element name="fProtocol" type="rdeCsv:fRequiredUnsignedByteType"
substitutionGroup="rdeCsv:field"/>
<!-- Key Algorithm field -->
<element name="fKeyAlg" type="rdeCsv:fRequiredUnsignedByteType"
substitutionGroup="rdeCsv:field"/>
<!-- Public Key field -->
<element name="fPubKey" type="csvDomain:fPubKeyType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fPubKeyType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="secDNS\:keyType"/>
</extension>
</complexContent>
</complexType> </complexType>
</schema>
<CODE ENDS>
<!-- Original Domain Name for Variant field --> 9.3. CSV Domain Object
<element name="fOriginalName" type="rdeCsv:fNameType"
substitutionGroup="rdeCsv:field"/>
<!-- Variant group / tag field -->
<element name="fVariantGroup"
type="rdeCsv:fTokenType"
substitutionGroup="rdeCsv:field"/>
<!-- Domain status field -->
<element name="fStatus" type="csvDomain:fStatusType"
substitutionGroup="rdeCsv:field"/>
<!-- Domain status based on domain-1.0.xsd -->
<complexType name="fStatusType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="domain\:statusValueType"/>
</extension>
</complexContent>
</complexType>
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!-- <!--
End of schema. Import common element types
--> -->
</schema> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
END <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1" />
9.4. RDE Host Object <import namespace="urn:ietf:params:xml:ns:rgp-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" />
BEGIN <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="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:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:host-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"/>
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow Host provisioning schema Domain Name Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!--
<element name="abstractHost" type="rdeHost:abstractContentType" Child elements of the <rde:contents> object
substitutionGroup="rde:content" abstract="true"/> -->
<element name="host" substitutionGroup="rdeHost:abstractHost" /> <element name="contents"
<element name="delete" type="rdeHost:deleteType" type="csvDomain:contentType"
substitutionGroup="rde:delete"/> substitutionGroup="rde:content" />
<complexType name="contentType">
<!-- Content Type -->
<complexType name="abstractContentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element name="name" <element ref="rdeCsv:csv"
type="eppcom:labelType"/> maxOccurs="unbounded" />
<element name="roid"
type="eppcom:roidType"/>
<element name="status"
type="host:statusType" maxOccurs="7"/>
<element name="addr"
type="host:addrType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="clID"
type="eppcom:clIDType"/>
<element name="crRr"
type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="crDate"
type="dateTime" minOccurs="0"/>
<element name="upRr"
type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="upDate"
type="dateTime" minOccurs="0"/>
<element name="trDate"
type="dateTime" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!--
<!-- Delete Type --> Child elements of the <rde:deletes> object
-->
<element name="deletes"
type="csvDomain:deleteType"
substitutionGroup="rde:delete" />
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<choice minOccurs="0" maxOccurs="unbounded"> <sequence>
<element name="name" <element ref="rdeCsv:csv"
type="eppcom:labelType"/> maxOccurs="unbounded" />
<element name="roid" </sequence>
type="eppcom:roidType"/> </extension>
</choice> </complexContent>
</complexType>
<!-- Domain name field -->
<element name="fName"
type="rdeCsv:fNameRequiredType"
substitutionGroup="rdeCsv:field" />
<!-- RGP status field -->
<element name="fRgpStatus"
type="csvDomain:fRgpStatusType"
substitutionGroup="rdeCsv:field" />
<complexType name="fRgpStatusType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="rgp\:statusValueType" />
</extension>
</complexContent>
</complexType>
<!-- Contact type field -->
<element name="fContactType"
type="csvDomain:fContactsTypeType"
substitutionGroup="rdeCsv:field" />
<complexType name="fContactsTypeType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="domain\:contactAttrType" />
</extension>
</complexContent>
</complexType>
<!-- DNSSEC field types -->
<!-- Maximum signature lifetime field -->
<element name="fMaxSigLife"
type="csvDomain:fMaxSigLifeType"
substitutionGroup="rdeCsv:field" />
<complexType name="fMaxSigLifeType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="secDNS\:maxSigLifeType" />
</extension>
</complexContent>
</complexType>
<!-- Key tag field -->
<element name="fKeyTag"
type="rdeCsv:fRequiredUnsignedShortType"
substitutionGroup="rdeCsv:field" />
<!-- DS Algorithm field -->
<element name="fDsAlg"
type="rdeCsv:fRequiredUnsignedByteType"
substitutionGroup="rdeCsv:field" />
<!-- Digest type field -->
<element name="fDigestType"
type="rdeCsv:fRequiredUnsignedByteType"
substitutionGroup="rdeCsv:field" />
<!-- Digest field -->
<element name="fDigest"
type="rdeCsv:fRequiredHexBinaryType"
substitutionGroup="rdeCsv:field" />
<!-- Flags field -->
<element name="fFlags"
type="rdeCsv:fRequiredUnsignedShortType"
substitutionGroup="rdeCsv:field" />
<!-- Protocol field -->
<element name="fProtocol"
type="rdeCsv:fRequiredUnsignedByteType"
substitutionGroup="rdeCsv:field" />
<!-- Key Algorithm field -->
<element name="fKeyAlg"
type="rdeCsv:fRequiredUnsignedByteType"
substitutionGroup="rdeCsv:field" />
<!-- Public Key field -->
<element name="fPubKey"
type="csvDomain:fPubKeyType"
substitutionGroup="rdeCsv:field" />
<complexType name="fPubKeyType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="secDNS\:keyType" />
</extension>
</complexContent>
</complexType>
<!-- Original Domain Name for Variant field -->
<element name="fOriginalName"
type="rdeCsv:fNameType"
substitutionGroup="rdeCsv:field" />
<!-- Domain status field -->
<element name="fStatus"
type="csvDomain:fStatusType"
substitutionGroup="rdeCsv:field" />
<!-- Domain status based on domain-1.0.xsd -->
<complexType name="fStatusType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="domain\:statusValueType" />
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema>
END
9.5. CSV Host Object
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!-- <!--
Import common element types End of schema.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> </schema>
<import namespace="urn:ietf:params:xml:ns:host-1.0"/> <CODE ENDS>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<annotation> 9.4. RDE Host Object
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="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:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:host-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
<annotation>
<documentation> <documentation>
Host Comma-Separated Values (CSV) Object Registry Data Escrow Host provisioning schema
</documentation> </documentation>
</annotation> </annotation>
<element name="abstractHost"
<!-- type="rdeHost:abstractContentType"
Child elements of the <rde:contents> object substitutionGroup="rde:content"
--> abstract="true" />
<element name="contents" type="csvHost:contentType" <element name="host"
substitutionGroup="rde:content"/> substitutionGroup="rdeHost:abstractHost" />
<element name="delete"
<complexType name="contentType"> type="rdeHost:deleteType"
substitutionGroup="rde:delete" />
<!-- Content Type -->
<complexType name="abstractContentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element name="name"
type="eppcom:labelType" />
<element name="roid"
type="eppcom:roidType" />
<element name="status"
type="host:statusType"
maxOccurs="7" />
<element name="addr"
type="host:addrType"
minOccurs="0"
maxOccurs="unbounded" />
<element name="clID"
type="eppcom:clIDType" />
<element name="crRr"
type="rdeDnrdCommon:rrType"
minOccurs="0" />
<element name="crDate"
type="dateTime"
minOccurs="0" />
<element name="upRr"
type="rdeDnrdCommon:rrType"
minOccurs="0" />
<element name="upDate"
type="dateTime"
minOccurs="0" />
<element name="trDate"
type="dateTime"
minOccurs="0" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType>
<!--
Child elements of the <rde:deletes> object
-->
<element name="deletes" type="csvHost:deleteType"
substitutionGroup="rde:delete"/>
<complexType name="deleteType"> </complexType>
<!-- Delete Type -->
<complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <choice minOccurs="0"
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> maxOccurs="unbounded">
</sequence> <element name="name"
</extension> type="eppcom:labelType" />
<element name="roid"
type="eppcom:roidType" />
</choice>
</extension>
</complexContent> </complexContent>
</complexType>
<!-- Host name field -->
<element name="fName" type="rdeCsv:fNameRequiredType"
substitutionGroup="rdeCsv:field"/>
<!-- IP address field -->
<element name="fAddr" type="csvHost:fAddrType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fAddrType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="host\:addrStringType"/>
</extension>
</complexContent>
</complexType>
<!-- IP address version field -->
<element name="fAddrVersion" type="csvHost:fAddrVersionType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fAddrVersionType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="host\:ipType"/>
</extension>
</complexContent>
</complexType> </complexType>
</schema>
<CODE ENDS>
<!-- Host status field --> 9.5. CSV Host Object
<element name="fStatus" type="csvHost:fStatusType"
substitutionGroup="rdeCsv:field"/>
<!-- Host status based on host-1.0.xsd -->
<complexType name="fStatusType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="host\:statusValueType"/>
</extension>
</complexContent>
</complexType>
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!-- <!--
End of schema. Import common element types
--> -->
</schema> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
END <import namespace="urn:ietf:params:xml:ns:host-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" />
9.6. RDE Contact Object <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="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:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!-- Import common element types. -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:contact-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"/>
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow contact provisioning schema Host Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!--
Child elements of the <rde:contents> object
-->
<element name="contents"
type="csvHost:contentType"
substitutionGroup="rde:content" />
<element name="abstractContact" <complexType name="contentType">
type="rdeContact:abstractContentType"
substitutionGroup="rde:content" abstract="true"/>
<element name="contact"
substitutionGroup="rdeContact:abstractContact"/>
<element name="delete"
type="rdeContact:deleteType"
substitutionGroup="rde:delete"/>
<!-- Contact Type -->
<complexType name="abstractContentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element name="id" <element ref="rdeCsv:csv"
type="eppcom:clIDType"/> maxOccurs="unbounded" />
<element name="roid"
type="eppcom:roidType"/>
<element name="status"
type="contact:statusType" maxOccurs="7"/>
<element name="postalInfo"
type="contact:postalInfoType" maxOccurs="2"/>
<element name="voice"
type="contact:e164Type" minOccurs="0"/>
<element name="fax"
type="contact:e164Type" minOccurs="0"/>
<element name="email"
type="eppcom:minTokenType"/>
<element name="clID"
type="eppcom:clIDType"/>
<element name="crRr"
type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="crDate"
type="dateTime" minOccurs="0"/>
<element name="upRr"
type="rdeDnrdCommon:rrType" minOccurs="0"/>
<element name="upDate"
type="dateTime" minOccurs="0"/>
<element name="trDate"
type="dateTime" minOccurs="0"/>
<element name="trnData"
type="rdeContact:transferDataType" minOccurs="0"/>
<element name="disclose"
type="contact:discloseType" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!--
<complexType name="transferDataType"> Child elements of the <rde:deletes> object
<sequence> -->
<element name="trStatus" type="eppcom:trStatusType"/> <element name="deletes"
<element name="reRr" type="rdeDnrdCommon:rrType"/> type="csvHost:deleteType"
<element name="reDate" type="dateTime"/> substitutionGroup="rde:delete" />
<element name="acRr" type="rdeDnrdCommon:rrType"/>
<element name="acDate" type="dateTime"/>
</sequence>
</complexType>
<!-- Delete Type -->
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element name="id" <element ref="rdeCsv:csv"
type="eppcom:clIDType" minOccurs="0" maxOccurs="unbounded" />
maxOccurs="unbounded"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- Host name field -->
<element name="fName"
type="rdeCsv:fNameRequiredType"
substitutionGroup="rdeCsv:field" />
<!-- IP address field -->
<element name="fAddr"
type="csvHost:fAddrType"
substitutionGroup="rdeCsv:field" />
<complexType name="fAddrType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="host\:addrStringType" />
</extension>
</complexContent>
</complexType>
<!-- IP address version field -->
<element name="fAddrVersion"
type="csvHost:fAddrVersionType"
substitutionGroup="rdeCsv:field" />
<complexType name="fAddrVersionType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="host\:ipType" />
</extension>
</complexContent>
</complexType>
<!-- Host status field -->
<element name="fStatus"
type="csvHost:fStatusType"
substitutionGroup="rdeCsv:field" />
<!-- Host status based on host-1.0.xsd -->
<complexType name="fStatusType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="host\:statusValueType" />
</extension>
</complexContent>
</complexType>
<!--
End of schema.
-->
</schema> </schema>
END <CODE ENDS>
9.6. RDE Contact Object
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="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:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!-- Import common element types. -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:contact-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
<annotation>
<documentation>
Registry Data Escrow contact provisioning schema
</documentation>
</annotation>
<element name="abstractContact"
type="rdeContact:abstractContentType"
substitutionGroup="rde:content"
abstract="true" />
<element name="contact"
substitutionGroup="rdeContact:abstractContact" />
<element name="delete"
type="rdeContact:deleteType"
substitutionGroup="rde:delete" />
<!-- Contact Type -->
<complexType name="abstractContentType">
<complexContent>
<extension base="rde:contentType">
<sequence>
<element name="id"
type="eppcom:clIDType" />
<element name="roid"
type="eppcom:roidType" />
<element name="status"
type="contact:statusType"
maxOccurs="7" />
<element name="postalInfo"
type="contact:postalInfoType"
maxOccurs="2" />
<element name="voice"
type="contact:e164Type"
minOccurs="0" />
<element name="fax"
type="contact:e164Type"
minOccurs="0" />
<element name="email"
type="eppcom:minTokenType" />
<element name="clID"
type="eppcom:clIDType" />
<element name="crRr"
type="rdeDnrdCommon:rrType"
minOccurs="0" />
<element name="crDate"
type="dateTime"
minOccurs="0" />
<element name="upRr"
type="rdeDnrdCommon:rrType"
minOccurs="0" />
<element name="upDate"
type="dateTime"
minOccurs="0" />
<element name="trDate"
type="dateTime"
minOccurs="0" />
<element name="trnData"
type="rdeContact:transferDataType"
minOccurs="0" />
<element name="disclose"
type="contact:discloseType"
minOccurs="0" />
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="transferDataType">
<sequence>
<element name="trStatus"
type="eppcom:trStatusType" />
<element name="reRr"
type="rdeDnrdCommon:rrType" />
<element name="reDate"
type="dateTime" />
<element name="acRr"
type="rdeDnrdCommon:rrType" />
<element name="acDate"
type="dateTime" />
</sequence>
</complexType>
<!-- Delete Type -->
<complexType name="deleteType">
<complexContent>
<extension base="rde:deleteType">
<sequence>
<element name="id"
type="eppcom:clIDType"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
</schema>
<CODE ENDS>
9.7. CSV Contact Object 9.7. CSV Contact Object
BEGIN <CODE BEGINS>
<?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"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!--
<!--
Import common element types. Import common element types.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:contact-1.0"/> <import namespace="urn:ietf:params:xml:ns:contact-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
<annotation>
<annotation> <documentation>
<documentation>
Contact Comma-Separated Values (CSV) Object Contact Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
<element name="contents" type="csvContact:contentType" <element name="contents"
substitutionGroup="rde:content"/> type="csvContact:contentType"
substitutionGroup="rde:content" />
<complexType name="contentType"> <complexType name="contentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element ref="rdeCsv:csv"
</sequence> maxOccurs="unbounded" />
</extension> </sequence>
</complexContent> </extension>
</complexContent>
</complexType> </complexType>
<!-- <!--
Child elements of the <rde:deletes> object Child elements of the <rde:deletes> object
--> -->
<element name="deletes" type="csvContact:deleteType" <element name="deletes"
substitutionGroup="rde:delete"/> type="csvContact:deleteType"
substitutionGroup="rde:delete" />
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element ref="rdeCsv:csv"
</sequence> maxOccurs="unbounded" />
</extension> </sequence>
</complexContent> </extension>
</complexContent>
</complexType> </complexType>
<!-- Server-unique contact identifier field -->
<!-- Server-unique contact identifier field --> <element name="fId"
<element name="fId" type="csvContact:fIdType" type="csvContact:fIdType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<complexType name="fIdType"> <complexType name="fIdType">
<complexContent> <complexContent>
<extension base="rdeCsv:fieldRequiredType"> <extension base="rdeCsv:fieldRequiredType">
<sequence/> <sequence />
<attribute name="type" type="token" <attribute name="type"
default="eppcom\:clIDType"/> type="token"
</extension> default="eppcom\:clIDType" />
</complexContent> </extension>
</complexType> </complexContent>
</complexType>
<!-- Is Registrar Contact field --> <!-- Is Registrar Contact field -->
<element name="fIsRegistrarContact" <element name="fIsRegistrarContact"
type="rdeCsv:fBooleanType" type="rdeCsv:fBooleanType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<!-- voice and fax telephone number fields -->
<!-- voice and fax telephone number fields --> <element name="fVoice"
<element name="fVoice" type="csvContact:fE164StringType" type="csvContact:fE164StringType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<element name="fFax" type="csvContact:fE164StringType" <element name="fFax"
substitutionGroup="rdeCsv:field"/> type="csvContact:fE164StringType"
<complexType name="fE164StringType"> substitutionGroup="rdeCsv:field" />
<complexContent> <complexType name="fE164StringType">
<extension base="rdeCsv:fieldOptionalType"> <complexContent>
<sequence/> <extension base="rdeCsv:fieldOptionalType">
<attribute name="type" type="token" <sequence />
default="contact\:e164StringType"/> <attribute name="type"
</extension> type="token"
</complexContent> default="contact\:e164StringType" />
</complexType> </extension>
</complexContent>
<!-- voice and fax telephone extension fields --> </complexType>
<element name="fVoiceExt" type="rdeCsv:fTokenType" <!-- voice and fax telephone extension fields -->
substitutionGroup="rdeCsv:field"/> <element name="fVoiceExt"
<element name="fFaxExt" type="rdeCsv:fTokenType" type="rdeCsv:fTokenType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<element name="fFaxExt"
<!-- contact email address field --> type="rdeCsv:fTokenType"
<element name="fEmail" type="csvContact:fEmailType" substitutionGroup="rdeCsv:field" />
substitutionGroup="rdeCsv:field"/> <!-- contact email address field -->
<complexType name="fEmailType"> <element name="fEmail"
<complexContent> type="csvContact:fEmailType"
<extension base="rdeCsv:fieldRequiredType"> substitutionGroup="rdeCsv:field" />
<sequence/> <complexType name="fEmailType">
<attribute name="type" type="token" <complexContent>
default="eppcom\:minTokenType"/> <extension base="rdeCsv:fieldRequiredType">
</extension> <sequence />
</complexContent> <attribute name="type"
</complexType> type="token"
default="eppcom\:minTokenType" />
<!-- </extension>
</complexContent>
</complexType>
<!--
Postal type field Postal type field
("loc" = localized, "int" = internationalized) ("loc" = localized, "int" = internationalized)
--> -->
<element name="fPostalType" type="csvContact:fPostalTypeType" <element name="fPostalType"
substitutionGroup="rdeCsv:field"/> type="csvContact:fPostalTypeType"
<complexType name="fPostalTypeType"> substitutionGroup="rdeCsv:field" />
<complexContent> <complexType name="fPostalTypeType">
<extension base="rdeCsv:fieldRequiredType"> <complexContent>
<sequence/> <extension base="rdeCsv:fieldRequiredType">
<attribute name="type" type="token" <sequence />
default="contact\:postalInfoEnumType"/> <attribute name="type"
</extension> type="token"
</complexContent> default="contact\:postalInfoEnumType" />
</complexType> </extension>
</complexContent>
<!-- Standard postal line field --> </complexType>
<complexType name="fPostalLineType"> <!-- Standard postal line field -->
<complexContent> <complexType name="fPostalLineType">
<extension base="rdeCsv:fieldRequiredType"> <complexContent>
<sequence/> <extension base="rdeCsv:fieldRequiredType">
<attribute name="type" type="token" <sequence />
default="contact\:postalLineType"/> <attribute name="type"
<attribute name="isLoc" type="boolean"/> type="token"
</extension> default="contact\:postalLineType" />
</complexContent> <attribute name="isLoc"
</complexType> type="boolean" />
</extension>
<!-- Standard optional postal line field --> </complexContent>
<complexType name="fOptPostalLineType"> </complexType>
<complexContent> <!-- Standard optional postal line field -->
<extension base="rdeCsv:fieldOptionalType"> <complexType name="fOptPostalLineType">
<sequence/> <complexContent>
<attribute name="type" type="token" <extension base="rdeCsv:fieldOptionalType">
default="contact\:optPostalLineType"/> <sequence />
<attribute name="isLoc" type="boolean"/> <attribute name="type"
</extension> type="token"
</complexContent> default="contact\:optPostalLineType" />
</complexType> <attribute name="isLoc"
type="boolean" />
<!-- Name of the individual or role field --> </extension>
<element name="fName" type="csvContact:fPostalLineType" </complexContent>
substitutionGroup="rdeCsv:field"/> </complexType>
<!-- Name of the individual or role field -->
<!-- Name organization field --> <element name="fName"
<element name="fOrg" type="csvContact:fOptPostalLineType" type="csvContact:fPostalLineType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<!-- Name organization field -->
<!-- Street address line field with required index attribute --> <element name="fOrg"
<!-- starting with index 0. --> type="csvContact:fOptPostalLineType"
<element name="fStreet" type="csvContact:fStreetType" substitutionGroup="rdeCsv:field" />
substitutionGroup="rdeCsv:field"/> <!-- Street address line field with required index attribute -->
<complexType name="fStreetType"> <!-- starting with index 0. -->
<complexContent> <element name="fStreet"
<extension base="csvContact:fOptPostalLineType"> type="csvContact:fStreetType"
<sequence/> substitutionGroup="rdeCsv:field" />
<attribute name="index" type="int" <complexType name="fStreetType">
use="required"/> <complexContent>
</extension> <extension base="csvContact:fOptPostalLineType">
</complexContent> <sequence />
</complexType> <attribute name="index"
type="int"
<!-- Contact's city field --> use="required" />
<element name="fCity" type="csvContact:fPostalLineType" </extension>
substitutionGroup="rdeCsv:field"/> </complexContent>
</complexType>
<!-- Contact's state or province field --> <!-- Contact's city field -->
<element name="fSp" type="csvContact:fOptPostalLineType" <element name="fCity"
substitutionGroup="rdeCsv:field"/> type="csvContact:fPostalLineType"
substitutionGroup="rdeCsv:field" />
<!-- Contact's postal code field --> <!-- Contact's state or province field -->
<element name="fPc" type="csvContact:fPcType" <element name="fSp"
substitutionGroup="rdeCsv:field"/> type="csvContact:fOptPostalLineType"
<complexType name="fPcType"> substitutionGroup="rdeCsv:field" />
<complexContent> <!-- Contact's postal code field -->
<extension base="rdeCsv:fieldOptionalType"> <element name="fPc"
<sequence/> type="csvContact:fPcType"
<attribute name="type" type="token" substitutionGroup="rdeCsv:field" />
default="contact\:pcType"/> <complexType name="fPcType">
<attribute name="isLoc" type="boolean"/> <complexContent>
</extension> <extension base="rdeCsv:fieldOptionalType">
</complexContent> <sequence />
</complexType> <attribute name="type"
type="token"
<!-- Contact's country code field --> default="contact\:pcType" />
<element name="fCc" type="csvContact:fCcType" <attribute name="isLoc"
substitutionGroup="rdeCsv:field"/> type="boolean" />
<complexType name="fCcType"> </extension>
<complexContent> </complexContent>
<extension base="rdeCsv:fieldRequiredType"> </complexType>
<sequence/> <!-- Contact's country code field -->
<attribute name="type" type="token" <element name="fCc"
default="contact\:ccType"/> type="csvContact:fCcType"
<attribute name="isLoc" type="boolean"/> substitutionGroup="rdeCsv:field" />
</extension> <complexType name="fCcType">
</complexContent> <complexContent>
</complexType> <extension base="rdeCsv:fieldRequiredType">
<sequence />
<!-- Disclosure element fields --> <attribute name="type"
<!-- Flag of "1" to allow disclosure type="token"
default="contact\:ccType" />
<attribute name="isLoc"
type="boolean" />
</extension>
</complexContent>
</complexType>
<!-- Disclosure element fields -->
<!-- Flag of "1" to allow disclosure
and "0" to disallow disclosure --> and "0" to disallow disclosure -->
<element name="fDiscloseFlag"
<element name="fDiscloseFlag" type="csvContact:fBoolean" type="csvContact:fBoolean"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<!-- Disclosure of localized name <!-- Disclosure of localized name
based on fDiscloseFlag? --> based on fDiscloseFlag? -->
<element name="fDiscloseNameLoc" type="csvContact:fBoolean" <element name="fDiscloseNameLoc"
substitutionGroup="rdeCsv:field"/> type="csvContact:fBoolean"
<!-- Disclosure of internationalized name substitutionGroup="rdeCsv:field" />
<!-- Disclosure of internationalized name
based on fDiscloseFlag? --> based on fDiscloseFlag? -->
<element name="fDiscloseNameInt" type="csvContact:fBoolean" <element name="fDiscloseNameInt"
substitutionGroup="rdeCsv:field"/> type="csvContact:fBoolean"
<!-- Disclosure of localized org substitutionGroup="rdeCsv:field" />
<!-- Disclosure of localized org
based on fDiscloseFlag? --> based on fDiscloseFlag? -->
<element name="fDiscloseOrgLoc" type="csvContact:fBoolean" <element name="fDiscloseOrgLoc"
substitutionGroup="rdeCsv:field"/> type="csvContact:fBoolean"
<!-- Disclosure of internationalized org substitutionGroup="rdeCsv:field" />
<!-- Disclosure of internationalized org
based on fDiscloseFlag? --> based on fDiscloseFlag? -->
<element name="fDiscloseOrgInt" type="csvContact:fBoolean" <element name="fDiscloseOrgInt"
substitutionGroup="rdeCsv:field"/> type="csvContact:fBoolean"
<!-- Disclosure of localized address substitutionGroup="rdeCsv:field" />
<!-- Disclosure of localized address
based on fDiscloseFlag? --> based on fDiscloseFlag? -->
<element name="fDiscloseAddrLoc" type="csvContact:fBoolean" <element name="fDiscloseAddrLoc"
substitutionGroup="rdeCsv:field"/> type="csvContact:fBoolean"
<!-- Disclosure of internationalized address substitutionGroup="rdeCsv:field" />
<!-- Disclosure of internationalized address
based on fDiscloseFlag? --> based on fDiscloseFlag? -->
<element name="fDiscloseAddrInt" type="csvContact:fBoolean" <element name="fDiscloseAddrInt"
substitutionGroup="rdeCsv:field"/> type="csvContact:fBoolean"
<!-- Disclosure voice telephone number substitutionGroup="rdeCsv:field" />
<!-- Disclosure voice telephone number
based on fDiscloseFlag? --> based on fDiscloseFlag? -->
<element name="fDiscloseVoice" type="csvContact:fBoolean" <element name="fDiscloseVoice"
substitutionGroup="rdeCsv:field"/> type="csvContact:fBoolean"
<!-- Disclosure facsimile telephone number substitutionGroup="rdeCsv:field" />
<!-- Disclosure facsimile telephone number
based on fDiscloseFlag? --> based on fDiscloseFlag? -->
<element name="fDiscloseFax" type="csvContact:fBoolean" <element name="fDiscloseFax"
substitutionGroup="rdeCsv:field"/> type="csvContact:fBoolean"
<!-- Disclosure email address substitutionGroup="rdeCsv:field" />
<!-- Disclosure email address
based on fDiscloseFlag? --> based on fDiscloseFlag? -->
<element name="fDiscloseEmail" type="csvContact:fBoolean" <element name="fDiscloseEmail"
substitutionGroup="rdeCsv:field"/> type="csvContact:fBoolean"
<complexType name="fBoolean"> substitutionGroup="rdeCsv:field" />
<complexContent> <complexType name="fBoolean">
<extension base="rdeCsv:fieldOptionalType"> <complexContent>
<sequence/> <extension base="rdeCsv:fieldOptionalType">
<attribute name="type" type="token" <sequence />
default="boolean"/> <attribute name="type"
</extension> type="token"
</complexContent> default="boolean" />
</complexType> </extension>
<!-- Contact status field --> </complexContent>
<element name="fStatus" type="csvContact:fStatusType" </complexType>
substitutionGroup="rdeCsv:field"/> <!-- Contact status field -->
<element name="fStatus"
<!-- Host status based on contact-1.0.xsd --> type="csvContact:fStatusType"
<complexType name="fStatusType"> substitutionGroup="rdeCsv:field" />
<complexContent> <!-- Host status based on contact-1.0.xsd -->
<extension base="rdeCsv:fieldRequiredType"> <complexType name="fStatusType">
<sequence/> <complexContent>
<attribute name="type" type="token" <extension base="rdeCsv:fieldRequiredType">
default="contact\:statusValueType"/> <sequence />
</extension> <attribute name="type"
</complexContent> type="token"
</complexType> default="contact\:statusValueType" />
</extension>
<!-- </complexContent>
</complexType>
<!--
End of schema. End of schema.
--> -->
</schema> </schema>
END <CODE ENDS>
9.8. RDE Registrar Object 9.8. RDE Registrar Object
BEGIN <CODE BEGINS>
<?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">
<!-- Import common element types. --> <!-- Import common element types. -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:domain-1.0"/> <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
<import namespace="urn:ietf:params:xml:ns:contact-1.0"/> <import namespace="urn:ietf:params:xml:ns:contact-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow registrar provisioning schema Registry Data Escrow registrar provisioning schema
</documentation> </documentation>
</annotation> </annotation>
<element name="abstractRegistrar" <element name="abstractRegistrar"
type="rdeRegistrar:abstractContentType" type="rdeRegistrar:abstractContentType"
substitutionGroup="rde:content" abstract="true"/> substitutionGroup="rde:content"
abstract="true" />
<element name="registrar" <element name="registrar"
substitutionGroup="rdeRegistrar:abstractRegistrar"/> substitutionGroup="rdeRegistrar:abstractRegistrar" />
<element name="delete" type="rdeRegistrar:deleteType" <element name="delete"
substitutionGroup="rde:delete"/> type="rdeRegistrar:deleteType"
substitutionGroup="rde:delete" />
<!-- Content Type --> <!-- Content Type -->
<complexType name="abstractContentType"> <complexType name="abstractContentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element name="id" <element name="id"
type="eppcom:clIDType"/> type="eppcom:clIDType" />
<element name="name" <element name="name"
type="rdeRegistrar:nameType"/> type="rdeRegistrar:nameType" />
<element name="gurid" <element name="gurid"
type="positiveInteger" minOccurs="0"/> type="positiveInteger"
minOccurs="0" />
<element name="status" <element name="status"
type="rdeRegistrar:statusType" minOccurs="0"/> type="rdeRegistrar:statusType"
minOccurs="0" />
<element name="postalInfo" <element name="postalInfo"
type="rdeRegistrar:postalInfoType" type="rdeRegistrar:postalInfoType"
minOccurs="0" maxOccurs="2"/> minOccurs="0"
maxOccurs="2" />
<element name="voice" <element name="voice"
type="contact:e164Type" minOccurs="0"/> type="contact:e164Type"
minOccurs="0" />
<element name="fax" <element name="fax"
type="contact:e164Type" minOccurs="0"/> type="contact:e164Type"
minOccurs="0" />
<element name="email" <element name="email"
type="eppcom:minTokenType" minOccurs="0"/> type="eppcom:minTokenType"
minOccurs="0" />
<element name="url" <element name="url"
type="anyURI" minOccurs="0"/> type="anyURI"
minOccurs="0" />
<element name="whoisInfo" <element name="whoisInfo"
type="rdeRegistrar:whoisInfoType" minOccurs="0"/> type="rdeRegistrar:whoisInfoType"
minOccurs="0" />
<element name="crDate" <element name="crDate"
type="dateTime" minOccurs="0"/> type="dateTime"
minOccurs="0" />
<element name="upDate" <element name="upDate"
type="dateTime" minOccurs="0"/> type="dateTime"
minOccurs="0" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<simpleType name="nameType"> <simpleType name="nameType">
<restriction base="normalizedString"> <restriction base="normalizedString">
<minLength value="1" /> <minLength value="1" />
<maxLength value="255" /> <maxLength value="255" />
</restriction> </restriction>
</simpleType> </simpleType>
<simpleType name="statusType"> <simpleType name="statusType">
<restriction base="token"> <restriction base="token">
<enumeration value="ok"/> <enumeration value="ok" />
<enumeration value="readonly"/> <enumeration value="readonly" />
<enumeration value="terminated"/> <enumeration value="terminated" />
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="postalInfoType"> <complexType name="postalInfoType">
<sequence> <sequence>
<element name="addr" <element name="addr"
type="rdeRegistrar:addrType" /> type="rdeRegistrar:addrType" />
</sequence> </sequence>
<attribute name="type" <attribute name="type"
type="rdeRegistrar:postalInfoEnumType" type="rdeRegistrar:postalInfoEnumType"
use="required" /> use="required" />
</complexType> </complexType>
<simpleType name="postalInfoEnumType"> <simpleType name="postalInfoEnumType">
<restriction base="token"> <restriction base="token">
<enumeration value="loc" /> <enumeration value="loc" />
<enumeration value="int" /> <enumeration value="int" />
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="addrType"> <complexType name="addrType">
<sequence> <sequence>
<element name="street" <element name="street"
type="rdeRegistrar:optPostalLineType" type="rdeRegistrar:optPostalLineType"
minOccurs="0" maxOccurs="3" /> minOccurs="0"
maxOccurs="3" />
<element name="city" <element name="city"
type="rdeRegistrar:postalLineType" /> type="rdeRegistrar:postalLineType" />
<element name="sp" <element name="sp"
type="rdeRegistrar:optPostalLineType" type="rdeRegistrar:optPostalLineType"
minOccurs="0" /> minOccurs="0" />
<element name="pc" <element name="pc"
type="rdeRegistrar:pcType" minOccurs="0" /> type="rdeRegistrar:pcType"
minOccurs="0" />
<element name="cc" <element name="cc"
type="rdeRegistrar:ccType" /> type="rdeRegistrar:ccType" />
</sequence> </sequence>
</complexType> </complexType>
<simpleType name="postalLineType"> <simpleType name="postalLineType">
<restriction base="normalizedString"> <restriction base="normalizedString">
<minLength value="1" /> <minLength value="1" />
<maxLength value="255" /> <maxLength value="255" />
</restriction> </restriction>
</simpleType> </simpleType>
<simpleType name="optPostalLineType"> <simpleType name="optPostalLineType">
<restriction base="normalizedString"> <restriction base="normalizedString">
<maxLength value="255" /> <maxLength value="255" />
</restriction> </restriction>
skipping to change at page 118, line 9 skipping to change at page 119, line 4
<restriction base="normalizedString"> <restriction base="normalizedString">
<minLength value="1" /> <minLength value="1" />
<maxLength value="255" /> <maxLength value="255" />
</restriction> </restriction>
</simpleType> </simpleType>
<simpleType name="optPostalLineType"> <simpleType name="optPostalLineType">
<restriction base="normalizedString"> <restriction base="normalizedString">
<maxLength value="255" /> <maxLength value="255" />
</restriction> </restriction>
</simpleType> </simpleType>
<simpleType name="pcType"> <simpleType name="pcType">
<restriction base="token"> <restriction base="token">
<maxLength value="16" /> <maxLength value="16" />
</restriction> </restriction>
</simpleType> </simpleType>
<simpleType name="ccType"> <simpleType name="ccType">
<restriction base="token"> <restriction base="token">
<length value="2" /> <length value="2" />
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="whoisInfoType"> <complexType name="whoisInfoType">
<sequence> <sequence>
<element name="name" <element name="name"
type="eppcom:labelType" minOccurs="0"/> type="eppcom:labelType"
minOccurs="0" />
<element name="url" <element name="url"
type="anyURI" minOccurs="0"/> type="anyURI"
minOccurs="0" />
</sequence> </sequence>
</complexType> </complexType>
<!-- Delete Type --> <!-- Delete Type -->
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element name="id" <element name="id"
type="eppcom:clIDType" minOccurs="0" type="eppcom:clIDType"
maxOccurs="unbounded"/> minOccurs="0"
maxOccurs="unbounded" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END <CODE ENDS>
9.9. CSV Registrar Object 9.9. CSV Registrar Object
BEGIN <CODE BEGINS>
<?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"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types. Import common element types.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:domain-1.0"/> <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
<import namespace="urn:ietf:params:xml:ns:contact-1.0"/> <import namespace="urn:ietf:params:xml:ns:contact-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Registar Comma-Separated Values (CSV) Object Registar Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
<element name="contents" type="csvRegistrar:contentType" <element name="contents"
substitutionGroup="rde:content"/> type="csvRegistrar:contentType"
substitutionGroup="rde:content" />
<complexType name="contentType"> <complexType name="contentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element ref="rdeCsv:csv"
</sequence> maxOccurs="unbounded" />
</extension> </sequence>
</complexContent> </extension>
</complexContent>
</complexType> </complexType>
<!-- <!--
Child elements of the <rde:deletes> object Child elements of the <rde:deletes> object
--> -->
<element name="deletes" type="csvRegistrar:deleteType" <element name="deletes"
substitutionGroup="rde:delete"/> type="csvRegistrar:deleteType"
substitutionGroup="rde:delete" />
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element ref="rdeCsv:csv"
</sequence> maxOccurs="unbounded" />
</extension> </sequence>
</complexContent> </extension>
</complexContent>
</complexType> </complexType>
<!-- Registrar unique identifier (short name / id) -->
<element name="fId"
type="rdeCsv:fClIDRequiredType"
substitutionGroup="rdeCsv:field" />
<!-- Registrar name (full name) -->
<element name="fName"
type="csvRegistrar:fNameType"
substitutionGroup="rdeCsv:field" />
<!-- Registrar name field -->
<complexType name="fNameType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence />
<attribute name="type"
type="token"
default="normalizedString" />
<attribute name="isLoc"
type="boolean"
default="false" />
</extension>
</complexContent>
</complexType>
<!-- Registrar GURID field -->
<element name="fGurid"
type="rdeCsv:fPositiveIntegerType"
substitutionGroup="rdeCsv:field" />
<!-- Registrar status field -->
<element name="fStatus"
type="csvRegistrar:fStatusType"
substitutionGroup="rdeCsv:field" />
<element name="fStatusName"
type="rdeCsv:fTokenType"
substitutionGroup="rdeCsv:field" />
<complexType name="fStatusType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type"
type="token"
default="csvRegistrar\:statusType" />
</extension>
</complexContent>
</complexType>
<!-- Registrar status type with optional name attr -->
<complexType name="statusType">
<simpleContent>
<extension base="csvRegistrar:statusValueType">
<attribute name="name"
type="token" />
</extension>
<!-- Registrar unique identifier (short name / id) --> </simpleContent>
<element name="fId" type="rdeCsv:fClIDRequiredType" </complexType>
substitutionGroup="rdeCsv:field"/> <!-- Registrar status enumerated values -->
<simpleType name="statusValueType">
<!-- Registrar name (full name) --> <restriction base="token">
<element name="fName" type="csvRegistrar:fNameType" <enumeration value="ok" />
substitutionGroup="rdeCsv:field"/> <enumeration value="readonly" />
<enumeration value="terminated" />
<!-- Registrar name field --> </restriction>
<complexType name="fNameType"> </simpleType>
<complexContent> <!-- Whois URL field -->
<extension base="rdeCsv:fieldRequiredType"> <element name="fWhoisUrl"
<sequence/> type="rdeCsv:anyURIType"
<attribute name="type" type="token" substitutionGroup="rdeCsv:field" />
default="normalizedString"/>
<attribute name="isLoc" type="boolean" default="false"/>
</extension>
</complexContent>
</complexType>
<!-- Registrar GURID field -->
<element name="fGurid"
type="rdeCsv:fPositiveIntegerType"
substitutionGroup="rdeCsv:field"/>
<!-- Registrar status field -->
<element name="fStatus" type="csvRegistrar:fStatusType"
substitutionGroup="rdeCsv:field"/>
<element name="fStatusName" type="rdeCsv:fTokenType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fStatusType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="csvRegistrar\:statusType"/>
</extension>
</complexContent>
</complexType>
<!-- Registrar status type with optional name attr -->
<complexType name="statusType">
<simpleContent>
<extension base="csvRegistrar:statusValueType">
<attribute name="name" type="token"/>
</extension>
</simpleContent>
</complexType>
<!-- Registrar status enumerated values -->
<simpleType name="statusValueType">
<restriction base="token">
<enumeration value="ok"/>
<enumeration value="readonly"/>
<enumeration value="terminated"/>
</restriction>
</simpleType>
<!-- Whois URL field -->
<element name="fWhoisUrl"
type="rdeCsv:anyURIType"
substitutionGroup="rdeCsv:field"/>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END <CODE ENDS>
9.10. RDE IDN Table Reference Objects 9.10. RDE IDN Table Reference Objects
BEGIN <CODE BEGINS>
<?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"/>
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow IDN provisioning schema Registry Data Escrow IDN provisioning schema
</documentation> </documentation>
</annotation> </annotation>
<element name="idnTableRef"
<element name="idnTableRef" type="rdeIDN:contentType" type="rdeIDN:contentType"
substitutionGroup="rde:content"/> substitutionGroup="rde:content" />
<element name="delete" type="rdeIDN:deleteType" <element name="delete"
substitutionGroup="rde:delete"/> type="rdeIDN:deleteType"
substitutionGroup="rde:delete" />
<!-- Content Types --> <!-- Content Types -->
<complexType name="contentType"> <complexType name="contentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element name="url" type="anyURI"/> <element name="url"
<element name="urlPolicy" type="anyURI"/> type="anyURI" />
<element name="urlPolicy"
type="anyURI" />
</sequence> </sequence>
<attribute name="id" type="rdeIDN:idType" use="required"/> <attribute name="id"
type="rdeIDN:idType"
use="required" />
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element name="id" type="rdeIDN:idType"/> <element name="id"
type="rdeIDN:idType" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- Simple Types --> <!-- Simple Types -->
<simpleType name="idType"> <simpleType name="idType">
<restriction base="token"> <restriction base="token">
<minLength value="1"/> <minLength value="1" />
<maxLength value="64"/> <maxLength value="64" />
</restriction> </restriction>
</simpleType> </simpleType>
</schema> </schema>
END <CODE ENDS>
9.11. CSV IDN Language Object 9.11. CSV IDN Language Object
BEGIN <CODE BEGINS>
<?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">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
<annotation> <annotation>
<documentation> <documentation>
IDN Language Comma-Separated Values (CSV) Object IDN Language Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation>
</annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
<element name="contents" type="csvIDN:contentType" <element name="contents"
substitutionGroup="rde:content"/> type="csvIDN:contentType"
substitutionGroup="rde:content" />
<complexType name="contentType"> <complexType name="contentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element ref="rdeCsv:csv"
</sequence> maxOccurs="unbounded" />
</extension> </sequence>
</complexContent> </extension>
</complexContent>
</complexType> </complexType>
<!-- <!--
Child elements of the <rde:deletes> object Child elements of the <rde:deletes> object
--> -->
<element name="deletes" type="csvIDN:deleteType" <element name="deletes"
substitutionGroup="rde:delete"/> type="csvIDN:deleteType"
substitutionGroup="rde:delete" />
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element ref="rdeCsv:csv"
</sequence> maxOccurs="unbounded" />
</extension> </sequence>
</complexContent> </extension>
</complexContent>
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END <CODE ENDS>
9.12. EPP Parameters Object 9.12. EPP Parameters Object
BEGIN <CODE BEGINS>
<?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">
<import namespace="urn:ietf:params:xml:ns:epp-1.0" />
<import namespace="urn:ietf:params:xml:ns:epp-1.0"/> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow EPP Parameters schema Registry Data Escrow EPP Parameters schema
</documentation> </documentation>
</annotation> </annotation>
<!-- Content Type --> <!-- Content Type -->
<element name="eppParams" <element name="eppParams"
substitutionGroup="rdeEppParams:abstractEppParams"/> substitutionGroup="rdeEppParams:abstractEppParams" />
<!-- Abstract Content Type --> <!-- Abstract Content Type -->
<element name="abstractEppParams" <element name="abstractEppParams"
type="rdeEppParams:abstractContentType" type="rdeEppParams:abstractContentType"
substitutionGroup="rde:content" abstract="true"/> substitutionGroup="rde:content"
abstract="true" />
<complexType name="abstractContentType"> <complexType name="abstractContentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element name="version" type="epp:versionType" <element name="version"
maxOccurs="unbounded"/> type="epp:versionType"
maxOccurs="unbounded" />
<element name="lang" <element name="lang"
type="language" maxOccurs="unbounded"/> type="language"
maxOccurs="unbounded" />
<element name="objURI" <element name="objURI"
type="anyURI" maxOccurs="unbounded"/> type="anyURI"
maxOccurs="unbounded" />
<element name="svcExtension" <element name="svcExtension"
type="epp:extURIType" type="epp:extURIType"
minOccurs="0"/> minOccurs="0" />
<element name="dcp" <element name="dcp"
type="epp:dcpType"/> type="epp:dcpType" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END <CODE ENDS>
9.13. NNDN Object 9.13. NNDN Object
BEGIN <CODE BEGINS>
<?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">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0"/>
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow NNDN provisioning schema Registry Data Escrow NNDN provisioning schema
</documentation> </documentation>
</annotation> </annotation>
<element name="abstractNNDN"
<element name="abstractNNDN" type="rdeNNDN:abstractContentType" type="rdeNNDN:abstractContentType"
substitutionGroup="rde:content" abstract="true"/> substitutionGroup="rde:content"
<element name="NNDN" substitutionGroup="rdeNNDN:abstractNNDN"/> abstract="true" />
<element name="delete" type="rdeNNDN:deleteType" <element name="NNDN"
substitutionGroup="rde:delete"/> substitutionGroup="rdeNNDN:abstractNNDN" />
<element name="delete"
type="rdeNNDN:deleteType"
substitutionGroup="rde:delete" />
<!-- Content Type --> <!-- Content Type -->
<complexType name="abstractContentType"> <complexType name="abstractContentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element name="aName" <element name="aName"
type="eppcom:labelType"/> type="eppcom:labelType" />
<element name="uName" <element name="uName"
type="eppcom:labelType" minOccurs="0"/> type="eppcom:labelType"
minOccurs="0" />
<element name="idnTableId" <element name="idnTableId"
type="rdeIDN:idType" minOccurs="0"/> type="rdeIDN:idType"
minOccurs="0" />
<element name="originalName" <element name="originalName"
type="eppcom:labelType" minOccurs="0"/> type="eppcom:labelType"
minOccurs="0" />
<element name="nameState" <element name="nameState"
type="rdeNNDN:nameState"/> type="rdeNNDN:nameState" />
<element name="crDate" <element name="crDate"
type="dateTime" minOccurs="0"/> type="dateTime"
minOccurs="0" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<simpleType name="nameStateValue"> <simpleType name="nameStateValue">
<restriction base="token"> <restriction base="token">
<enumeration value="withheld" /> <enumeration value="withheld" />
<enumeration value="blocked" /> <enumeration value="blocked" />
<enumeration value="mirrored" /> <enumeration value="mirrored" />
</restriction> </restriction>
</simpleType> </simpleType>
<complexType name="nameState"> <complexType name="nameState">
<simpleContent> <simpleContent>
<extension base="rdeNNDN:nameStateValue"> <extension base="rdeNNDN:nameStateValue">
<attribute name="mirroringNS" <attribute name="mirroringNS"
type="boolean" default="true"/> type="boolean"
default="true" />
</extension> </extension>
</simpleContent> </simpleContent>
</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="aName" <element name="aName"
type="eppcom:labelType" minOccurs="0" type="eppcom:labelType"
maxOccurs="unbounded"/> minOccurs="0"
maxOccurs="unbounded" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END <CODE ENDS>
9.14. CSV NNDN Object 9.14. CSV NNDN Object
BEGIN <CODE BEGINS>
<?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">
<!-- <!--
Import common element types Import common element types
--> -->
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeNNDN-1.0"/> <import namespace="urn:ietf:params:xml:ns:rdeNNDN-1.0" />
<annotation> <annotation>
<documentation> <documentation>
NNDN (NNDN's not domain name) (CSV) Object NNDN (NNDN's not domain name) (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
<element name="contents" type="csvNNDN:contentType" <element name="contents"
substitutionGroup="rde:content"/> type="csvNNDN:contentType"
substitutionGroup="rde:content" />
<complexType name="contentType"> <complexType name="contentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element ref="rdeCsv:csv"
</sequence> maxOccurs="unbounded" />
</extension> </sequence>
</complexContent> </extension>
</complexContent>
</complexType> </complexType>
<!-- <!--
Child elements of the <rde:deletes> object Child elements of the <rde:deletes> object
--> -->
<element name="deletes" type="csvNNDN:deleteType" <element name="deletes"
substitutionGroup="rde:delete"/> type="csvNNDN:deleteType"
substitutionGroup="rde:delete" />
<complexType name="deleteType"> <complexType name="deleteType">
<complexContent> <complexContent>
<extension base="rde:deleteType"> <extension base="rde:deleteType">
<sequence> <sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/> <element ref="rdeCsv:csv"
</sequence> maxOccurs="unbounded" />
</extension> </sequence>
</complexContent> </extension>
</complexContent>
</complexType> </complexType>
<!-- A-Label format name field -->
<!-- ASCII Compatible Encoding (ACE) name field --> <element name="fAName"
<element name="fAName" type="rdeCsv:fNameRequiredType" type="rdeCsv:fNameRequiredType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<!-- domain name used to generate the IDN variant field -->
<!-- domain name used to generate the IDN variant field --> <element name="fOriginalName"
<element name="fOriginalName" type="rdeCsv:fNameType" type="rdeCsv:fNameType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field" />
<!-- RGP status field -->
<!-- Variant group / tag field --> <element name="fNameState"
<element name="fVariantGroup" type="csvNNDN:fNameStateType"
type="rdeCsv:fTokenType" substitutionGroup="rdeCsv:field" />
substitutionGroup="rdeCsv:field"/> <complexType name="fNameStateType">
<complexContent>
<!-- RGP status field --> <extension base="rdeCsv:fieldRequiredType">
<element name="fNameState" <sequence />
type="csvNNDN:fNameStateType" <attribute name="type"
substitutionGroup="rdeCsv:field"/> type="token"
<complexType name="fNameStateType"> default="rdeNNDN\:nameState" />
<complexContent> </extension>
<extension base="rdeCsv:fieldRequiredType"> </complexContent>
<sequence/> </complexType>
<attribute name="type" type="token" <!-- Mirroring uses NS mirror mechanism? -->
default="rdeNNDN\:nameState"/> <element name="fMirroringNS"
</extension> type="rdeCsv:fBooleanType"
</complexContent> substitutionGroup="rdeCsv:field" />
</complexType>
<!-- Mirroring uses NS mirror mechanism? -->
<element name="fMirroringNS"
type="rdeCsv:fBooleanType"
substitutionGroup="rdeCsv:field"/>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
END <CODE ENDS>
9.15. Policy Object 9.15. Policy Object
<CODE BEGINS>
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>
Registry Data Escrow Policy schema Registry Data Escrow Policy schema
</documentation> </documentation>
</annotation> </annotation>
<import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <element name="policy"
<element name="policy" type="rdePolicy:policyType" type="rdePolicy:policyType"
substitutionGroup="rde:content"/> substitutionGroup="rde:content" />
<complexType name="policyType"> <complexType name="policyType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<attribute name="scope" type="token" use="required"/> <attribute name="scope"
<attribute name="element" type="anyURI" use="required"/> type="token"
use="required" />
<attribute name="element"
type="anyURI"
use="required" />
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
END <CODE ENDS>
9.16. Header Object 9.16. Header Object
BEGIN <CODE BEGINS>
<?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"/> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<annotation> <annotation>
<documentation> <documentation>
Data Escrow Deposit Header schema Data Escrow Deposit Header schema
</documentation> </documentation>
</annotation> </annotation>
<!-- Root Element --> <!-- Root Element -->
<element name="header" type="rdeHeader:contentType" <element name="header"
substitutionGroup="rde:content"/> type="rdeHeader:contentType"
substitutionGroup="rde:content" />
<!-- Content Type --> <!-- Content Type -->
<complexType name="contentType"> <complexType name="contentType">
<complexContent> <complexContent>
<extension base="rde:contentType"> <extension base="rde:contentType">
<sequence> <sequence>
<group ref="rdeHeader:repositoryTypeGroup"/> <group ref="rdeHeader:repositoryTypeGroup" />
<element name="count" type="rdeHeader:countType" <element name="count"
maxOccurs="unbounded"/> type="rdeHeader:countType"
<element name="contentTag" type="token" maxOccurs="unbounded" />
minOccurs="0"/> <element name="contentTag"
type="token"
minOccurs="0" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<group name="repositoryTypeGroup"> <group name="repositoryTypeGroup">
<choice> <choice>
<element name="tld" type="eppcom:labelType" /> <element name="tld"
<element name="registrar" type="positiveInteger"/> type="eppcom:labelType" />
<element name="ppsp" type="token"/> <element name="registrar"
<element name="reseller" type="token"/> type="positiveInteger" />
<element name="ppsp"
type="token" />
<element name="reseller"
type="token" />
</choice> </choice>
</group> </group>
<complexType name="countType"> <complexType name="countType">
<simpleContent> <simpleContent>
<extension base="long"> <extension base="long">
<attribute name="uri" type="anyURI" use="required"/> <attribute name="uri"
<attribute name="rcdn" type="eppcom:labelType"/> type="anyURI"
<attribute name="registrarId" type="positiveInteger"/> use="required" />
<attribute name="rcdn"
type="eppcom:labelType" />
<attribute name="registrarId"
type="positiveInteger" />
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
</schema> </schema>
END <CODE ENDS>
9.17. DNRD Common Objects 9.17. DNRD Common Objects
BEGIN <CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns: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"/> <annotation>
<documentation>
<annotation> Data Escrow Deposit Common Objects schema
<documentation> </documentation>
Data Escrow Deposit Common Objects schema </annotation>
</documentation> <complexType name="rrType">
</annotation> <simpleContent>
<extension base="eppcom:clIDType">
<complexType name="rrType"> <attribute name="client"
<simpleContent> type="eppcom:clIDType" />
<extension base="eppcom:clIDType"> </extension>
<attribute name="client" type="eppcom:clIDType"/> </simpleContent>
</extension> </complexType>
</simpleContent> </schema>
</complexType> <CODE ENDS>
</schema>
END
10. Internationalization Considerations 10. Internationalization Considerations
Data Escrow deposits are represented in XML, which provides native Data Escrow deposits are represented in XML, which provides native
support for encoding information using the Unicode character set and support for encoding information using the Unicode character set and
its more compact representations including UTF-8. Conformant XML its more compact representations including UTF-8. Conformant XML
processors recognize both UTF-8 and UTF-16. Though XML includes processors recognize both UTF-8 and UTF-16. Though XML includes
provisions to identify and use other character encodings through use provisions to identify and use other character encodings through use
of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is
RECOMMENDED. RECOMMENDED.
11. IANA Considerations 11. IANA Considerations
This document uses URNs to describe XML namespaces and XML schemas This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in [RFC3688]. Fourteen conforming to a registry mechanism described in [RFC3688]. The
URI assignments have been registered by the IANA. following URI assignments is requested of IANA.
Registration request for the RDE CSV namespace: Registration request for the RDE CSV namespace:
URI: urn:ietf:params:xml:ns:rdeCsv-1.0 URI: urn:ietf:params:xml:ns:rdeCsv-1.0
Registrant Contact: IESG <regext@ietf.org>
Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE CSV XML schema: Registration request for the RDE CSV XML schema:
URI: urn:ietf:params:xml:schema:rdeCsv-1.0 URI: urn:ietf:params:xml:schema:rdeCsv-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.1 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 132, line 42 skipping to change at page 133, line 40
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.2 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 133, line 16 skipping to change at page 134, line 14
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.3 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 133, line 38 skipping to change at page 134, line 36
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.4 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 134, line 6 skipping to change at page 135, line 4
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV host XML schema: Registration request for the CSV host XML schema:
URI: urn:ietf:params:xml:schema:csvHost-1.0 URI: urn:ietf:params:xml:schema:csvHost-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.5 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 134, line 34 skipping to change at page 135, line 31
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.6 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 135, line 4 skipping to change at page 135, line 49
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the CSV contact XML schema: Registration request for the CSV contact XML schema:
URI: urn:ietf:params:xml:schema:csvContact-1.0 URI: urn:ietf:params:xml:schema:csvContact-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.7 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 135, line 29 skipping to change at page 136, line 27
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.8 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 135, line 51 skipping to change at page 136, line 49
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.9 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 136, line 25 skipping to change at page 137, line 23
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.10 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 136, line 47 skipping to change at page 137, line 45
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.11 of this document. See Section 9.11 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: IESG <regext@ietf.org>
Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE EPP parameters XML schema: Registration request for the RDE EPP parameters XML schema:
URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.12 of this document. See Section 9.12 of this document.
Registration request for the RDE NNDN namespace: Registration request for the RDE NNDN namespace:
URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 137, line 42 skipping to change at page 138, line 40
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.13 of this document. See 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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 138, line 16 skipping to change at page 139, line 14
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: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.14 of this document. See Section 9.14 of this document.
Registration request for the RDE Policy namespace: Registration request for the RDE Policy namespace:
URI: urn:ietf:params:xml:ns:rdePolicy-1.0 URI: urn:ietf:params:xml:ns:rdePolicy-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 138, line 38 skipping to change at page 139, line 36
Registration request for the RDE Policy XML schema: Registration request for the RDE Policy XML schema:
URI: urn:ietf:params:xml:ns:rdePolicy-1.0 URI: urn:ietf:params:xml:ns:rdePolicy-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.15 of this document. See Section 9.15 of this document.
Registration request for the RDE Header namespace: Registration request for the RDE Header namespace:
URI: urn:ietf:params:xml:ns:rdeHeader-1.0 URI: urn:ietf:params:xml:ns:rdeHeader-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 139, line 6 skipping to change at page 140, line 4
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
XML: None. Namespace URIs do not represent an XML specification. XML: None. Namespace URIs do not represent an XML specification.
Registration request for the RDE Header XML schema: Registration request for the RDE Header XML schema:
URI: urn:ietf:params:xml:ns:rdeHeader-1.0 URI: urn:ietf:params:xml:ns:rdeHeader-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.16 of this document. See Section 9.16 of this document.
Registration request for the RDE Common Objects namespace: Registration request for the RDE Common Objects namespace:
URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
skipping to change at page 139, line 34 skipping to change at page 140, line 31
Registration request for the RDE Common Objects XML schema: Registration request for the RDE Common Objects XML schema:
URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0
Registrant Contact: IESG <regext@ietf.org> Registrant Contact: IESG <regext@ietf.org>
Note to RFC Editor: Please remove the email address from the RFC Note to RFC Editor: Please remove the email address from the RFC
after IANA records it. after IANA records it.
See section Section 9.17 of this document. See Section 9.17 of this document.
12. Implementation Status 12. Implementation Status
Note to RFC Editor: Please remove this section and the reference to Note to RFC Editor: Please remove this section and the reference to
RFC 7942 [RFC7942] before publication. RFC 7942 [RFC7942] before publication.
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in RFC 7942 Internet-Draft, and is based on a proposal described in RFC 7942
[RFC7942]. The description of implementations in this section is [RFC7942]. The description of implementations in this section is
skipping to change at page 140, line 32 skipping to change at page 141, line 32
specification. ICANN receives on a weekly basis per gTLD, from more specification. ICANN receives on a weekly basis per gTLD, from more
than 1,200 gTLD registries, a Bulk Registration Data Access file that than 1,200 gTLD registries, a Bulk Registration Data Access file that
also complies with this specification. In addition, ICANN is aware also complies with this specification. In addition, ICANN is aware
of Registry Service Provider transitions using data files that of Registry Service Provider transitions using data files that
conform to this specification. conform to this specification.
Level of maturity: production. Level of maturity: production.
Coverage: all aspects of this specification are implemented. Coverage: all aspects of this specification are implemented.
Version compatibility: versions 03 - 08 are known to be implemented. Version compatibility: versions 03 - 09 are known to be implemented.
Contact: gustavo.lozano@icann.org Contact: gustavo.lozano@icann.org
URL: https://www.icann.org/resources/pages/registries/registries- URL: https://www.icann.org/resources/pages/registries/registries-
agreements-en agreements-en
13. Security Considerations 13. Security Considerations
This specification does not define the security mechanisms to be used This specification does not define the security mechanisms to be used
in the transmission of the data escrow deposits, since it only in the transmission of the data escrow deposits, since it only
skipping to change at page 141, line 9 skipping to change at page 142, line 9
Depending on local policies, some elements, or, most likely, the Depending on local policies, some elements, or, most likely, the
whole deposit will be considered confidential. As such, the parties whole deposit will be considered confidential. As such, the parties
SHOULD take all the necessary precautions such as encrypting the data SHOULD take all the necessary precautions such as encrypting the data
at rest and in transit to avoid inadvertent disclosure of private at rest and in transit to avoid inadvertent disclosure of private
data. Regardless of the precautions taken by the parties regarding data. Regardless of the precautions taken by the parties regarding
data at rest and in transit, authentication credentials MUST NOT be data at rest and in transit, authentication credentials MUST NOT be
escrowed. escrowed.
Authentication of the parties passing data escrow deposit files is Authentication of the parties passing data escrow deposit files is
also of the utmost importance. The escrow agent MUST properly also of the utmost importance. The escrow agent MUST properly
authenticate the identity of the registry before accepting data authenticate the registry's identity before accepting data escrow
escrow deposits. In a similar manner, the registry MUST authenticate deposits. The registry MUST authenticate the escrow agent's identity
the identity of the escrow agent before submitting any data. before submitting any data, and the data escrow agent MUST
authenticate the identity of the party receiving the data escrow
deposits for the purposes deemed appropriate.
Additionally, the registry and the escrow agent MUST use integrity Additionally, the registry and the escrow agent MUST use integrity
checking mechanisms to ensure the data transmitted is what the source checking mechanisms to ensure the data transmitted is what the source
intended. Validation of the contents by the escrow agent is intended. Validation of the contents by the parties is RECOMMENDED
RECOMMENDED to ensure not only that the file was transmitted to ensure that the file was transmitted correctly from the registry
correctly from the registry, but also that the contents are or escrow agent and that the contents are "meaningful".
"meaningful".
A few elements in this specification contain URLs, the use of HTTP
over TLS (Transport Layer Security), [RFC2818] is RECOMMENDED on the
URLs.
The various data structures in the document include a few places that
have internal redundancy, and if the values become inconsistent there
can be harmful consequences, such as different entities using
different fields as their reference.
Note: if Transport Layer Security (TLS) is used when providing an Note: if Transport Layer Security (TLS) is used when providing an
escrow services, the recommendations in [RFC7525] MUST be escrow services, the recommendations in [BCP195] MUST be implemented.
implemented.
14. Privacy Considerations 14. Privacy Considerations
This specification defines a format that may be used to escrow This specification defines a format that may be used to escrow
personal data. The process of data escrow is governed by a legal personal data. The process of data escrow is governed by a legal
document agreed by the parties, and such legal document must ensure document agreed by the parties, and such legal document must ensure
that privacy-sensitive and/or personal data receives the required that privacy-sensitive and/or personal data receives the required
protection. protection.
15. Acknowledgments 15. Acknowledgments
Parts of this document are based on EPP [RFC5730] and related RFCs by Parts of this document are based on EPP [RFC5730] and related RFCs by
Scott Hollenbeck. Scott Hollenbeck.
Special suggestions that have been incorporated into this document Special suggestions that have been incorporated into this document
were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc
Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen
Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul
Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan,
Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James
Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. Mitchell, Francisco Obispo, Bhadresh Modi, Alexander Mayrhofer and
Benjamin Kaduk.
Shoji Noguchi and Francisco Arias participated as co-authors until Shoji Noguchi and Francisco Arias participated as co-authors until
version 05 providing invaluable support for this document. version 05 providing invaluable support for this document.
16. Change History 16. Change History
[[RFC Editor: Please remove this section.]] [[RFC Editor: Please remove this section.]]
16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to -
dnrd-objects-mapping-00 dnrd-objects-mapping-00
skipping to change at page 149, line 21 skipping to change at page 150, line 23
1. draft-ietf-regext-data-escrow (version 04) is now referenced from 1. draft-ietf-regext-data-escrow (version 04) is now referenced from
the I-D repository. the I-D repository.
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 [RFC5952] to the Normative References
section. section.
16.18. Changes REGEXT 05 to REGEXT 06 16.18. Changes REGEXT 05 to REGEXT 06
1. Changes based on the feedback provided here: 1. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/ https://mailarchive.ietf.org/arch/msg/regext/
nA8eTYIrXJ44_6ullQlRLW6T74s nA8eTYIrXJ44_6ullQlRLW6T74s
16.19. Changes REGEXT 06 to REGEXT 07 16.19. Changes REGEXT 06 to REGEXT 07
skipping to change at page 150, line 11 skipping to change at page 151, line 11
2. Changes based on the feedback provided here: 2. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/ https://mailarchive.ietf.org/arch/msg/regext/
B3QTxUCWUE4R_QharAQlA3041j0 B3QTxUCWUE4R_QharAQlA3041j0
16.21. Changes REGEXT 08 to REGEXT 09 16.21. Changes REGEXT 08 to REGEXT 09
1. Changes based on the feedback provided here: 1. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/ https://mailarchive.ietf.org/arch/msg/regext/
EmKW32exlPgLbBUIbS8OjdYUJWc EmKW32exlPgLbBUIbS8OjdYUJWc
16.22. Changes REGEXT 09 to REGEXT 10
1. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/
tmoKLAV6jhh2zp4JczjeWdr_jJE
2. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/m7gyDTjHuRqIQCuKMHF-
OLSS99k
3. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/
regext/3Acx5KHfeUdxZbx6A7zgoZHxIto
4. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/
regext/3Acx5KHfeUdxZbx6A7zgoZHxIto
5. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/
regext/7JiP2fzOr8KCnzI2rwoP-_KlxZY
6. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/dbuyW5YTYj4VcFHUQYC-
D8OMv_g
7. Changes based on the feedback provided here:
https://mailarchive.ietf.org/arch/msg/regext/
ExUZenwC81ZQe9x24-8IKT_FWm8
17. Example of a Full Deposit using the XML model 17. Example of a Full Deposit using the XML model
Example of a Full Deposit using the XML model: Example of a Full Deposit using the XML model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit type="FULL" id="20191017001" <rde:deposit type="FULL" id="20191017001"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
skipping to change at page 151, line 47 skipping to change at page 153, line 29
<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>
<rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
<rdeDomain:exDate>2015-04-03T22:00:00.0Z</rdeDomain:exDate> <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate>
</rdeDomain:domain> </rdeDomain:domain>
<!-- Domain: example2.example --> <!-- Domain: example2.example -->
<rdeDomain:domain> <rdeDomain:domain>
<rdeDomain:name>example2.example</rdeDomain:name> <rdeDomain:name>example2.example</rdeDomain:name>
<rdeDomain:roid>Dexample2-TEST</rdeDomain:roid> <rdeDomain:roid>Dexample2-TEST</rdeDomain:roid>
<rdeDomain:status s="ok"/> <rdeDomain:status s="ok"/>
<rdeDomain:status s="clientUpdateProhibited"/> <rdeDomain:status s="clientUpdateProhibited"/>
<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:clID>RegistrarX</rdeDomain:clID> <rdeDomain:clID>RegistrarX</rdeDomain:clID>
<rdeDomain:crRr>RegistrarX</rdeDomain:crRr> <rdeDomain:crRr>RegistrarX</rdeDomain:crRr>
<rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
<rdeDomain:exDate>2015-04-03T22:00:00.0Z</rdeDomain:exDate> <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate>
</rdeDomain:domain> </rdeDomain:domain>
<!-- Host: ns1.example.example --> <!-- Host: ns1.example.example -->
<rdeHost:host> <rdeHost:host>
<rdeHost:name>ns1.example1.example</rdeHost:name> <rdeHost:name>ns1.example1.example</rdeHost:name>
<rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid> <rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid>
<rdeHost:status s="ok"/> <rdeHost:status s="ok"/>
<rdeHost:status s="linked"/> <rdeHost:status s="linked"/>
<rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr>
<rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr>
skipping to change at page 153, line 30 skipping to change at page 155, line 12
<rdeContact:disclose flag="0"> <rdeContact:disclose flag="0">
<contact:voice/> <contact:voice/>
<contact:email/> <contact:email/>
</rdeContact:disclose> </rdeContact:disclose>
</rdeContact:contact> </rdeContact:contact>
<!-- Registrar: RegistrarX --> <!-- Registrar: RegistrarX -->
<rdeRegistrar:registrar> <rdeRegistrar:registrar>
<rdeRegistrar:id>RegistrarX</rdeRegistrar:id> <rdeRegistrar:id>RegistrarX</rdeRegistrar:id>
<rdeRegistrar:name>Registrar X</rdeRegistrar:name> <rdeRegistrar:name>Registrar X</rdeRegistrar:name>
<rdeRegistrar:gurid>123</rdeRegistrar:gurid> <rdeRegistrar:gurid>8</rdeRegistrar:gurid>
<rdeRegistrar:status>ok</rdeRegistrar:status> <rdeRegistrar:status>ok</rdeRegistrar:status>
<rdeRegistrar:postalInfo type="int"> <rdeRegistrar:postalInfo type="int">
<rdeRegistrar:addr> <rdeRegistrar:addr>
<rdeRegistrar:street>123 Example Dr. <rdeRegistrar:street>123 Example Dr.
</rdeRegistrar:street> </rdeRegistrar:street>
<rdeRegistrar:street>Suite 100 <rdeRegistrar:street>Suite 100
</rdeRegistrar:street> </rdeRegistrar:street>
<rdeRegistrar:city>Dulles</rdeRegistrar:city> <rdeRegistrar:city>Dulles</rdeRegistrar:city>
<rdeRegistrar:sp>VA</rdeRegistrar:sp> <rdeRegistrar:sp>VA</rdeRegistrar:sp>
<rdeRegistrar:pc>20166-6503</rdeRegistrar:pc> <rdeRegistrar:pc>20166-6503</rdeRegistrar:pc>
skipping to change at page 177, line 4 skipping to change at page 178, line 31
<epp:retention> <epp:retention>
<epp:indefinite/> <epp:indefinite/>
</epp:retention> </epp:retention>
</epp:statement> </epp:statement>
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
</rde:contents> </rde:contents>
</rde:deposit> </rde:deposit>
21. References 21. References
21.1. Normative References 21.1. Normative References
[BCP195] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
2015, <https://www.rfc-editor.org/info/bcp195>.
[I-D.ietf-regext-data-escrow] [I-D.ietf-regext-data-escrow]
Lozano, G., "Registry Data Escrow Specification", draft- Lozano, G., "Registry Data Escrow Specification", draft-
ietf-regext-data-escrow-10 (work in progress), June 2020. ietf-regext-data-escrow-10 (work in progress), June 2020.
[ISO-3166-1] [ISO-3166-1]
3166, I. S., "Codes for the representation of names of 3166, I. S., "Codes for the representation of names of
countries and their subdivisions -- Part 1: Country countries and their subdivisions -- Part 1: Country
codes", ISO Standard 3166, November 2006. codes", ISO Standard 3166, November 2006.
[ITU-E164] [ITU-E164]
skipping to change at page 177, line 38 skipping to change at page 179, line 23
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
[RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for
the Extensible Provisioning Protocol (EPP)", RFC 3915, the Extensible Provisioning Protocol (EPP)", RFC 3915,
DOI 10.17487/RFC3915, September 2004, DOI 10.17487/RFC3915, September 2004,
<https://www.rfc-editor.org/info/rfc3915>. <https://www.rfc-editor.org/info/rfc3915>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<https://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
Domain Name Mapping", STD 69, RFC 5731, Domain Name Mapping", STD 69, RFC 5731,
DOI 10.17487/RFC5731, August 2009, DOI 10.17487/RFC5731, August 2009,
<https://www.rfc-editor.org/info/rfc5731>. <https://www.rfc-editor.org/info/rfc5731>.
[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
skipping to change at page 178, line 24 skipping to change at page 180, line 5
Applications (IDNA): Protocol", RFC 5891, Applications (IDNA): Protocol", RFC 5891,
DOI 10.17487/RFC5891, August 2010, DOI 10.17487/RFC5891, August 2010,
<https://www.rfc-editor.org/info/rfc5891>. <https://www.rfc-editor.org/info/rfc5891>.
[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>.
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", RFC 5952,
DOI 10.17487/RFC5952, August 2010,
<https://www.rfc-editor.org/info/rfc5952>.
[RFC6234] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms
(SHA and SHA-based HMAC and HKDF)", RFC 6234,
DOI 10.17487/RFC6234, May 2011,
<https://www.rfc-editor.org/info/rfc6234>.
[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>.
[RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
January 2019, <https://www.rfc-editor.org/info/rfc8499>. January 2019, <https://www.rfc-editor.org/info/rfc8499>.
[V42] International Telecommunication Union, "V.42 : Error- [V42] International Telecommunication Union, "V.42 : Error-
correcting procedures for DCEs using asynchronous-to- correcting procedures for DCEs using asynchronous-to-
skipping to change at page 179, line 5 skipping to change at page 180, line 45
Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,
"XML Schema Part 1: Structures Second Edition REC- "XML Schema Part 1: Structures Second Edition REC-
xmlschema-1-20041028", October 2004, xmlschema-1-20041028", October 2004,
<https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/>. <https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/>.
[W3C.REC-xmlschema-2-20041028] [W3C.REC-xmlschema-2-20041028]
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
Second Edition REC-xmlschema-2-20041028", October 2004, Second Edition REC-xmlschema-2-20041028", October 2004,
<https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/>. <https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/>.
[W3C.REC-xpath-31-20170321]
Robie, J., Dyck, M., and J. Spiegel, "XML Path Language
(XPath) 3.1", March 2017,
<https://www.w3.org/TR/2017/REC-xpath-31-20170321/>.
21.2. Informative References 21.2. Informative References
[ICANN-GTLD-AGB-20120604] [ICANN-GTLD-AGB-20120604]
ICANN, "gTLD Applicant Guidebook Version 2012-06-04", June ICANN, "gTLD Applicant Guidebook Version 2012-06-04", June
2012, <http://newgtlds.icann.org/en/applicants/agb/ 2012, <http://newgtlds.icann.org/en/applicants/agb/
guidebook-full-04jun12-en.pdf>. guidebook-full-04jun12-en.pdf>.
[ICANN-GTLD-RA-20170731] [ICANN-GTLD-RA-20170731]
ICANN, "Base Registry Agreement 2017-07-31", July 2017, ICANN, "Base Registry Agreement 2017-07-31", July 2017,
<https://newgtlds.icann.org/sites/default/files/ <https://newgtlds.icann.org/sites/default/files/
agreements/agreement-approved-31jul17-en.pdf>. agreements/agreement-approved-31jul17-en.pdf>.
[RFC1952] Deutsch, P., "GZIP file format specification version 4.3", [RFC1952] Deutsch, P., "GZIP file format specification version 4.3",
RFC 1952, DOI 10.17487/RFC1952, May 1996, RFC 1952, DOI 10.17487/RFC1952, May 1996,
<https://www.rfc-editor.org/info/rfc1952>. <https://www.rfc-editor.org/info/rfc1952>.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,
DOI 10.17487/RFC2818, May 2000,
<https://www.rfc-editor.org/info/rfc2818>.
[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>.
[RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma- [RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma-
Separated Values (CSV) Files", RFC 4180, Separated Values (CSV) Files", RFC 4180,
DOI 10.17487/RFC4180, October 2005, DOI 10.17487/RFC4180, October 2005,
<https://www.rfc-editor.org/info/rfc4180>. <https://www.rfc-editor.org/info/rfc4180>.
[RFC6234] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms
(SHA and SHA-based HMAC and HKDF)", RFC 6234,
DOI 10.17487/RFC6234, May 2011,
<https://www.rfc-editor.org/info/rfc6234>.
[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
2015, <https://www.rfc-editor.org/info/rfc7525>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
[variantTLDsReport] [variantTLDsReport]
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
(ICANN), "A Study of Issues Related to the Management of (ICANN), "A Study of Issues Related to the Management of
IDN Variant TLDs", February 2012, IDN Variant TLDs", February 2012,
<http://www.icann.org/en/topics/idn/idn-vip-integrated- <http://www.icann.org/en/topics/idn/idn-vip-integrated-
 End of changes. 360 change blocks. 
1836 lines changed or deleted 1957 lines changed or added

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