draft-ietf-regext-dnrd-objects-mapping-01.txt   draft-ietf-regext-dnrd-objects-mapping-02.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 27, 2020 C. Thippeswamy Expires: April 27, 2020 C. Thippeswamy
VeriSign VeriSign
Aug 26, 2019 Oct 25, 2019
Domain Name Registration Data (DNRD) Objects Mapping Domain Name Registration Data (DNRD) Objects Mapping
draft-ietf-regext-dnrd-objects-mapping-01 draft-ietf-regext-dnrd-objects-mapping-02
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 27, 2020. This Internet-Draft will expire on April 27, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 23 skipping to change at page 2, line 23
4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6
4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6
4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6
4.6. CSV Parent Child Relationship . . . . . . . . . . . . . . 6 4.6. CSV Parent Child Relationship . . . . . . . . . . . . . . 6
4.7. CSV elements . . . . . . . . . . . . . . . . . . . . . . 7 4.7. CSV elements . . . . . . . . . . . . . . . . . . . . . . 7
4.8. Internationalized and Localized Elements . . . . . . . . 12 4.8. Internationalized and Localized Elements . . . . . . . . 12
5. Object Description . . . . . . . . . . . . . . . . . . . . . 14 5. Object Description . . . . . . . . . . . . . . . . . . . . . 14
5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 14 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 14
5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 33 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 33
5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 43 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 43
5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 60 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 61
5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 68 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 69
5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 72 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 73
5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 77 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 78
5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 79 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 80
5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 79 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 80
6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 82 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 83
7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8. Data escrow agent extended verification process . . . . . . . 83 8. Data escrow agent extended verification process . . . . . . . 84
9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 84 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 85
9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 84 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 85
9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 94 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 95
9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 97 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98
9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 102 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 103
9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 104 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 105
9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 107 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 108
9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 110 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 111
9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 117
9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 120 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 121
9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 124 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 125
9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 126 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 127
9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 128 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 129
9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 130 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 131
9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 132 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 133
9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 135 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 136
9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 136 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 137
10. Internationalization Considerations . . . . . . . . . . . . . 138 10. Internationalization Considerations . . . . . . . . . . . . . 139
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 138 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 139
12. Implementation Status . . . . . . . . . . . . . . . . . . . . 144 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 145
12.1. Implementation in the gTLD space . . . . . . . . . . . . 144 12.1. Implementation in the gTLD space . . . . . . . . . . . . 145
13. Security Considerations . . . . . . . . . . . . . . . . . . . 145 13. Security Considerations . . . . . . . . . . . . . . . . . . . 146
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 145 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 146
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 145 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 146
16. Change History . . . . . . . . . . . . . . . . . . . . . . . 146 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 147
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 . . . . . . . . . . . . . . 146 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 147
16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 146 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 147
16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 147 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 148
16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 147 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 148
16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 147 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 148
16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 148 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 149
16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 149 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 150
16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 149 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 150
16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 150 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 151
16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 150 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 151
16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 150 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 151
16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 150 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 151
16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 150 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 151
17. Example of a full deposit using the XML model . . . . . . . . 150 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 151
18. Example of differential deposit using the XML model . . . . . 156 17. Example of a full deposit using the XML model . . . . . . . . 153
19. Example of a full deposit using the CSV model . . . . . . . . 157 18. Example of differential deposit using the XML model . . . . . 158
20. Example of differential deposit using the CSV model . . . . . 166 19. Example of a full deposit using the CSV model . . . . . . . . 160
21. References . . . . . . . . . . . . . . . . . . . . . . . . . 177 20. Example of differential deposit using the CSV model . . . . . 169
21.1. Normative References . . . . . . . . . . . . . . . . . . 177 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 180
21.2. Informative References . . . . . . . . . . . . . . . . . 178 21.1. Normative References . . . . . . . . . . . . . . . . . . 180
21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 179 21.2. Informative References . . . . . . . . . . . . . . . . . 181
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 179 21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182
1. Introduction 1. Introduction
This document defines the data escrow structure of the standard set This document defines the data escrow structure of the standard set
of objects for a Domain Name Registry which include: of objects for a Domain Name Registry which include:
o Domain: Internet domain names that are typically provisioned in a o Domain: Internet domain names that are typically provisioned in a
Domain Name Registry using the EPP domain name mapping [RFC5731]. Domain Name Registry using the EPP domain name mapping [RFC5731].
The attributes defined in the EPP domain name mapping [RFC5731] The attributes defined in the EPP domain name mapping [RFC5731]
are fully supported by this document. are fully supported by this document.
skipping to change at page 11, line 9 skipping to change at page 11, line 9
<rdeCsv:fRoid> Repository Object IDentifier (ROID) field with <rdeCsv:fRoid> Repository Object IDentifier (ROID) field with
type="eppcom:roidType" and isRequired="true". type="eppcom:roidType" and isRequired="true".
<rdeCsv:fRegistrant> Registrant contact identifier with <rdeCsv:fRegistrant> Registrant contact identifier with
type="eppcom:clIDType". type="eppcom:clIDType".
<rdeCsv:fStatusDescription> The object status description, which is <rdeCsv:fStatusDescription> The object status description, which is
free form text describing the rationale for the status, with free form text describing the rationale for the status, with
type="normalizedString". type="normalizedString".
<rdeCsv:fClID> Identifier of client (registrar) that sponsors the <rdeCsv:fClID> Identifier of the client (registrar) that sponsors
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 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 updated the object with type="eppcom:clIDType".
<rdeCsv:fUpID> Identifier of client that updated the object with <rdeCsv:fUpID> Identifier of the client that updated the object with
type="eppcom:clIDType". 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 client that requested the transfer with <rdeCsv:fReID> Identifier of the client that requested the transfer
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".
<rdeCsv:fAcID> Identifier of client that should take or took action <rdeCsv:fAcID> Identifier of the client that should take or took
for transfer with type="eppcom:clIDType". action for transfer with type="eppcom:clIDType".
<rdeCsv:fCrDate> Created date of object with type="dateTime" and <rdeCsv:fCrDate> Created date of object with type="dateTime".
isRequired="true".
<rdeCsv:fUpDate> Updated date of object with type="dateTime". <rdeCsv:fUpDate> Updated date of object with type="dateTime".
<rdeCsv:fExDate> Expiration date of object with type="dateTime". <rdeCsv:fExDate> Expiration date of object with type="dateTime".
<rdeCsv:fReDate> Date that transfer was requested with <rdeCsv:fReDate> Date that transfer was requested with
type="dateTime" and isRequired="true". type="dateTime" and isRequired="true".
<rdeCsv:fAcDate> Date that transfer action should be taken or has <rdeCsv:fAcDate> Date that transfer action should be taken or has
been taken with type="dateTime" and isRequired="true". been taken with type="dateTime" and isRequired="true".
skipping to change at page 13, line 30 skipping to change at page 13, line 30
<csvContact:fStreet isLoc="false" index="1"/> <csvContact:fStreet isLoc="false" index="1"/>
<csvContact:fStreet isLoc="false" index="2"/> <csvContact:fStreet isLoc="false" index="2"/>
<csvContact:fCity isLoc="false" /> <csvContact:fCity isLoc="false" />
<csvContact:fSp isLoc="false" /> <csvContact:fSp isLoc="false" />
<csvContact:fPc isLoc="false" /> <csvContact:fPc isLoc="false" />
<csvContact:fCc isLoc="false" /> <csvContact:fCc isLoc="false" />
<csvContact:fVoice/> <csvContact:fVoice/>
<csvContact:fVoiceExt/> <csvContact:fVoiceExt/>
<csvContact:fFax/> <csvContact:fFax/>
<csvContact:fFaxExt/> <csvContact:fFaxExt/>
<csvContact:fEmail/> <csvContact:fEmail isRequired="false"/>
<rdeCsv:fUrl/> <rdeCsv:fUrl/>
<csvRegistrar:fWhoisUrl/> <csvRegistrar:fWhoisUrl/>
<rdeCsv:fCrRr/> <rdeCsv:fCrRr/>
<rdeCsv:fCrID/> <rdeCsv:fCrID/>
<rdeCsv:fCrDate/> <rdeCsv:fCrDate/>
<rdeCsv:fUpRr/> <rdeCsv:fUpRr/>
<rdeCsv:fUpID/> <rdeCsv:fUpID/>
<rdeCsv:fUpDate/> <rdeCsv:fUpDate/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
skipping to change at page 19, line 48 skipping to change at page 19, line 48
<csvDomain:fName> Domain name field with type="eppcom:labelType" and <csvDomain:fName> Domain name field with type="eppcom:labelType" and
isRequired="true". isRequired="true".
The following "csvDomain" field elements MAY be used in the "domain" The following "csvDomain" field elements MAY be used in the "domain"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvDomain:fOriginalName> Fully qualified name of the original IDN <csvDomain:fOriginalName> Fully qualified name of the original IDN
domain name object related to the variant domain name object with domain name object related to the variant domain name object with
type="eppcom:labelType". type="eppcom:labelType".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the
elements (Section 4.7.2), MUST be used in the "domain" <rdeCsv:csv> "domain" <rdeCsv:csv> <rdeCsv:fields> element:
<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> Identifier of client that sponsors the domain name <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of:
object with isRequired="true".
<rdeCsv:fCrDate> Created date and time of the domain name object
with isRequired="true".
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the object.
<rdeCsv:fUpDate> Date and time of the last update to the domain name <rdeCsv:fClID> Identifier of the sponsoring client with
object. isRequired="true".
<rdeCsv:fExDate> Expiration date and time for the domain name <csvRegistrar:fGurid> Contains the ID assigned by ICANN with
object. The attribute isRequired MUST equal "true". type="positiveInteger". The attribute "isRequired" MUST equal
"true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "domain" <rdeCsv:csv> elements (Section 4.7.2), MAY be used in the "domain" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
of the client that created the object. of the client that created the object.
<rdeCsv:fCrID> Identifier of the client that created the domain name
object.
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the object.
<rdeCsv:fUpID> Identifier of the client that last updated the domain
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:fCrID> Identifier of client that created the domain name <rdeCsv:fCrDate> Created date and time of the domain name object.
<rdeCsv:fUpDate> Date and time of the last update to the domain name
object. object.
<rdeCsv:fUpID> Identifier of the client that last updated the domain <rdeCsv:fExDate> Expiration date and time for the domain name
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.
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">
skipping to change at page 22, line 11 skipping to change at page 22, line 11
xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--abc123.test, xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--abc123.test,
registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z,
registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z
5.1.2.1.2. "domainContacts" CSV File Definition 5.1.2.1.2. "domainContacts" CSV File Definition
The "domainContacts" CSV File Definition defines the fields and CSV The "domainContacts" CSV File Definition defines the fields and CSV
file references used for the domain name object link records to file references used for the domain name object link records to
contact objects, as described in Contact Object (Section 5.3). contact objects, as described in Contact Object (Section 5.3).
The following "csvDomain" field elements MUST be used in the The following "csvDomain" field elements, defined for the "domain"
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:
<csvDomain:fName> The name of the domain object that is linked to
the contact object with isRequired="true".
<csvDomain:fContactType> The contact type for the contact object <csvDomain:fContactType> The contact type for the contact object
link with type="domain:contactAttrType" and isRequired="true". link with type="domain:contactAttrType" and isRequired="true".
The supported contact type values include "admin" for the The supported contact type values include "admin" for the
administration contact, "billing" for the billing contact, and administration contact, "billing" for the billing contact, and
"tech" for the technical contact. "tech" for the technical contact.
The following "csvDomain" field elements, defined for the "domain"
CSV File Definition (Section 5.1.2.1.1), MUST be used in the
"domainContacts" <rdeCsv:csv> <rdeCsv:fields> element:
<csvDomain:fName> The name of the domain object that is linked to
the contact object with isRequired="true".
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 "domainContacts" Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvContact:fId> The server-unique contact identifier with <csvContact:fId> The server-unique contact identifier with
isRequired="true". isRequired="true".
Example of a "domainContacts" <csvDomain:contents> <rdeCsv:csv> Example of a "domainContacts" <csvDomain:contents> <rdeCsv:csv>
element. element.
skipping to change at page 23, line 51 skipping to change at page 23, line 28
xn--abc123.test,xnabc123billing,billing xn--abc123.test,xnabc123billing,billing
xn--abc321.test,xnabc123admin,admin xn--abc321.test,xnabc123admin,admin
xn--abc321.test,xnabc123tech,tech xn--abc321.test,xnabc123tech,tech
xn--abc321.test,xnabc123billing,billing xn--abc321.test,xnabc123billing,billing
5.1.2.1.3. "domainStatuses" CSV File Definition 5.1.2.1.3. "domainStatuses" CSV File Definition
The "domainStatuses" CSV File Definition defines the fields and CSV The "domainStatuses" CSV File Definition defines the fields and CSV
file references used for the domain name object statuses. file references used for the domain name object statuses.
The following "csvDomain" field elements MUST be used in the The following "csvDomain" fields, defined for the "domain" CSV File
"domainStatuses" <rdeCsv:csv> <rdeCsv:fields> element: Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses"
<rdeCsv:csv> <rdeCsv:fields> element:
<csvDomain:fName> Domain name of status with isRequired="true".
<csvDomain:fStatus> The status of the domain name with <csvDomain:fStatus> The status of the domain name with
type="domain:statusValueType" and isRequired="true". type="domain:statusValueType" and isRequired="true".
<csvDomain:fRgpStatus> The Registry Grace Period (RGP) status, as a <csvDomain:fRgpStatus> The Registry Grace Period (RGP) status, as a
sub-status of the <csvDomain:fStatus> "pendingDelete" status sub-status of the <csvDomain:fStatus> "pendingDelete" status
value, with type="rgp:statusValueType" as defined in [RFC3915]. value, with type="rgp:statusValueType" as defined in [RFC3915].
The following "csvDomain" fields, defined for the "domain" CSV File
Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses"
<rdeCsv:csv> <rdeCsv:fields> element:
<csvDomain:fName> Domain name of status with isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "domainStatuses" elements (Section 4.7.2), MAY be used in the "domainStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fStatusDescription> Domain object status description which <rdeCsv:fStatusDescription> Domain object status description which
is free form text describing the rationale for the status. is free form text describing the rationale for the status.
<rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field. <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
Example of a "domainStatuses" <csvDomain:contents> <rdeCsv:csv> Example of a "domainStatuses" <csvDomain:contents> <rdeCsv:csv>
skipping to change at page 25, line 30 skipping to change at page 25, line 9
CSV file references used for the domain name delegated hosts (name CSV file references used for the domain name delegated hosts (name
servers). The "domainNameServers" CSV files define the relationship servers). The "domainNameServers" CSV files define the relationship
between a domain name object and a delegated host. The between a domain name object and a delegated host. The
"domainNameServers" CSV File is used to support the <domain:hostObj> "domainNameServers" CSV File is used to support the <domain:hostObj>
model, defined in [RFC5731]. model, defined in [RFC5731].
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
"domainNameServers" <rdeCsv:csv> <rdeCsv:fields> element: "domainNameServers" <rdeCsv:csv> <rdeCsv:fields> element:
<csvDomain:fName> Domain name using the delegated host with host <csvDomain:fName> Domain name using the delegated host with
<rdeCsv:fRoid> and isRequired="true". isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "csvHost" and "rdeCsv" field elements MUST be used in
elements (Section 4.7.2), MUST be used in the "domainNameServers" the "domainNameServers" <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fRoid> Registry Object IDentifier (ROID) used to uniquely <csvHost:fName> or <rdeCsv:fRoid> A choice of:
reference a delegated host record with isRequired="true".
<csvHost:fName> Host name field with type="eppcom:labelType" and
isRequired="true".
<rdeCsv:fRoid> Host object Registry Object IDentifier (ROID)
assigned to the host object with isRequired="true".
Example of a "domainNameServers" <csvDomain:contents> <rdeCsv:csv> Example of a "domainNameServers" <csvDomain:contents> <rdeCsv:csv>
element. element.
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domainNameServers"> <rdeCsv:csv name="domainNameServers">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
skipping to change at page 31, line 28 skipping to change at page 31, line 22
<rdeCsv:fAcDate> Date and time that the transfer action should be <rdeCsv:fAcDate> Date and time that the transfer action should be
taken or has been taken with isRequired="true". taken or has been taken with isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "domainTransfer" elements (Section 4.7.2), MAY be used in the "domainTransfer"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fExDate> Expiration date if the transfer command caused or <rdeCsv:fExDate> Expiration date if the transfer command caused or
causes a change in the validity period. causes a change in the validity period.
<rdeCsv:fReID> Identifier of client that requested the transfer. <rdeCsv:fReID> Identifier of the client that requested the transfer.
<rdeCsv:fAcID> Identifier of client that should take or took action <rdeCsv:fAcID> Identifier of the client that should take or took
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 object involved in the
transfer with isRequired="true". transfer with isRequired="true".
Example of a "domainTransfer" <csvDomain:contents> <rdeCsv:csv> Example of a "domainTransfer" <csvDomain:contents> <rdeCsv:csv>
element. element.
skipping to change at page 34, line 39 skipping to change at page 34, line 39
o One or more <status> elements that describe the status of the host o One or more <status> elements that describe the status of the host
object. object.
o Zero or more <addr> elements that contain the IP addresses o Zero or more <addr> elements that contain the IP addresses
associated with the host object. associated with the host object.
o A <clID> element that contains the identifier of the sponsoring o A <clID> element that contains the identifier of the sponsoring
registrar. registrar.
o A <crRr> element that contains the identifier of the registrar o An OPTIONAL <crRr> element that contains the identifier of the
that created the host object. An OPTIONAL client attribute is registrar that created the host object. An OPTIONAL client
used to specify the client that performed the operation. attribute is used to specify the client that performed the
operation.
o A <crDate> element that contains the date and time of host-object o An OPTIONAL <crDate> element that contains the date and time of
creation. host-object creation.
o An OPTIONAL <upRr> element that contains the identifier of the o An OPTIONAL <upRr> element that contains the identifier of the
registrar that last updated the host object. This element MUST registrar that last updated the host object. This element MUST
NOT be present if the host object has never been modified. An NOT be present if the host object has never been modified. An
OPTIONAL client attribute is used to specify the client that OPTIONAL client attribute is used to specify the client that
performed the operation. performed the operation.
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 host-object modification. This element MUST NOT the most recent host-object modification. This element MUST NOT
be present if the host object has never been modified. be present if the host object has never been modified.
skipping to change at page 37, line 5 skipping to change at page 36, line 51
<csvHost:fName> Host name field with type="eppcom:labelType" and <csvHost:fName> Host name field with type="eppcom:labelType" and
isRequired="true". isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "host" <rdeCsv:csv> elements (Section 4.7.2), MUST be used in the "host" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fRoid> Repository Object IDentifier (ROID) assigned to the <rdeCsv:fRoid> Repository Object IDentifier (ROID) assigned to the
host object with isRequired="true". host object with isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the
elements (Section 4.7.2), MAY be used in the "host" <rdeCsv:csv> "host" <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fields> element:
<rdeCsv:fClID> Identifier of the sponsoring client with <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of:
isRequired="true".
<rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fClID> Identifier of the sponsoring client with
of the client that created the object with isRequired="true". isRequired="true".
<rdeCsv:fCrID> Identifier of client that created the host object. <csvRegistrar:fGurid> Contains the ID assigned by ICANN with
type="positiveInteger". The attribute "isRequired" MUST equal
"true".
<rdeCsv:fCrDate> Date and time that the host object was created with <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
isRequired="true". of the client that created the object.
<rdeCsv:fCrID> Identifier of the client that created the host
object.
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the object. of the client that updated the object.
<rdeCsv:fUpID> Identifier of 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:fUpDate> Date and time that the host object was last <rdeCsv:fUpDate> Date and time that the host object was last
updated. updated.
<rdeCsv:fTrDate> Date and time that the host was last transferred. <rdeCsv:fTrDate> Date and time that the host was last transferred.
Example of a "host" <csvHost:contents> <rdeCsv:csv> element. Example of a "host" <csvHost:contents> <rdeCsv:csv> element.
... ...
<csvHost:contents> <csvHost:contents>
... ...
skipping to change at page 39, line 38 skipping to change at page 39, line 38
5.2.2.1.2. "hostStatuses" CSV File Definition 5.2.2.1.2. "hostStatuses" CSV File Definition
The "hostStatuses" CSV File Definition defines the fields and CSV The "hostStatuses" CSV File Definition defines the fields and CSV
file references used for the host object statuses. file references used for the host object statuses.
The following "csvHost" fields, defined for the "host" CSV File The following "csvHost" fields, defined for the "host" CSV File
Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvHost:fStatus> The status of the host with <csvHost:fStatus> The status of the host with
type="host:statusValueType" and isRequired="true"./>. type="host:statusValueType" and isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "hostStatuses" elements (Section 4.7.2), MUST be used in the "hostStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fRoid> Host object Registry Object IDentifier (ROID) <rdeCsv:fRoid> Host object Registry Object IDentifier (ROID)
assigned to the host object with isRequired="true". assigned to the host object with isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "hostStatuses" elements (Section 4.7.2), MAY be used in the "hostStatuses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fStatusDescription> Host object status description which is <rdeCsv:fStatusDescription> Host object status description which is
free form text describing the rationale for the status. The free form text describing the rationale for the status. The
attribute isRequired MUST equal "true". attribute "isRequired" MUST equal "true".
<rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field. <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
Example of a "hostStatuses" <csvHost:contents> <rdeCsv:csv> element. Example of a "hostStatuses" <csvHost:contents> <rdeCsv:csv> element.
... ...
<csvHost:contents> <csvHost:contents>
... ...
<rdeCsv:csv name="hostStatuses"> <rdeCsv:csv name="hostStatuses">
<rdeCsv:fields> <rdeCsv:fields>
skipping to change at page 41, line 6 skipping to change at page 41, line 6
5.2.2.1.3. "hostAddresses" CSV File Definition 5.2.2.1.3. "hostAddresses" CSV File Definition
The "hostAddresses" CSV File Definition defines the fields and CSV The "hostAddresses" CSV File Definition defines the fields and CSV
file references used for the host object IP addresses. file references used for the host object IP addresses.
The following "csvHost" field elements MUST be used in the The following "csvHost" field elements MUST be used in the
"hostAddresses" <rdeCsv:csv> <rdeCsv:fields> element: "hostAddresses" <rdeCsv:csv> <rdeCsv:fields> element:
<csvHost:fAddr> IP addresses associated with the host object with <csvHost:fAddr> IP addresses associated with the host object with
type="host:addrStringType". The attribute isRequired MUST equal type="host:addrStringType". The attribute "isRequired" MUST equal
"true". "true".
<csvHost:fAddrVersion> IP addresses version associated with the host <csvHost:fAddrVersion> IP addresses version associated with the host
object with type="host:ipType". "host:ipType" has the enumerated object with type="host:ipType". "host:ipType" has the enumerated
values of "v4" or "v6". The attribute isRequired MUST equal values of "v4" or "v6". The attribute "isRequired" MUST equal
"true". "true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "hostAddresses" elements (Section 4.7.2), MUST be used in the "hostAddresses"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fRoid> Host object Registry Object IDentifier (ROID) <rdeCsv:fRoid> Host object Registry Object IDentifier (ROID)
assigned to the host object. assigned to the host object with isRequired="true".
Example of a "hostAddresses" <csvHost:contents> <rdeCsv:csv> element. Example of a "hostAddresses" <csvHost:contents> <rdeCsv:csv> element.
... ...
<csvHost:contents> <csvHost:contents>
... ...
<rdeCsv:csv name="hostAddresses"> <rdeCsv:csv name="hostAddresses">
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fRoid parent="true"/> <rdeCsv:fRoid parent="true"/>
<csvHost:fAddr isRequired="true"/> <csvHost:fAddr isRequired="true"/>
skipping to change at page 44, line 40 skipping to change at page 44, line 40
telephone number. telephone number.
o An OPTIONAL <fax> element that contains the contact's facsimile o An OPTIONAL <fax> element that contains the contact's facsimile
telephone number. telephone number.
o An <email> element that contains the contact's email address. o An <email> element that contains the contact's email address.
o A <clID> element that contains the identifier of the sponsoring o A <clID> element that contains the identifier of the sponsoring
registrar. registrar.
o A <crRr> element that contains the identifier of the registrar o An OPTIONAL <crRr> element that contains the identifier of the
that created the contact object. An OPTIONAL client attribute is registrar that created the contact object. An OPTIONAL client
used to specify the client that performed the operation. attribute is used to specify the client that performed the
operation.
o A <crDate> element that contains the date and time of contact- o An OPTIONAL <crDate> element that contains the date and time of
object creation. contact-object creation.
o An OPTIONAL <upRr> element that contains the identifier of the o An OPTIONAL <upRr> element that contains the identifier of the
registrar that last updated the contact object. This element MUST registrar that last updated the contact object. This element MUST
NOT be present if the contact has never been modified. An NOT be present if the contact has never been modified. An
OPTIONAL client attribute is used to specify the client that OPTIONAL client attribute is used to specify the client that
performed the operation. performed the operation.
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 contact-object modification. This element MUST the most recent contact-object modification. This element MUST
NOT be present if the contact object has never been modified. NOT be present if the contact object has never been modified.
skipping to change at page 46, line 9 skipping to change at page 46, line 9
o An OPTIONAL <disclose> element that identifies elements that o An OPTIONAL <disclose> element that identifies elements that
requiring exceptional server-operator handling to allow or requiring exceptional server-operator handling to allow or
restrict disclosure to third parties. See Section 2.9 of restrict disclosure to third parties. See Section 2.9 of
[RFC5733] for a description of the child elements contained within [RFC5733] for a description of the child elements contained within
the <disclose> element. the <disclose> element.
Example <contact> object: Example <contact> object:
... ...
<rdeContact:contact> <rdeContact:contact>
<rdeContact:roid>Csh8013-TEST</rdeContact:roid>
<rdeContact:id>sh8013</rdeContact:id> <rdeContact:id>sh8013</rdeContact:id>
<rdeContact:roid>Csh8013-TEST</rdeContact:roid>
<rdeContact:status s="linked"/> <rdeContact:status s="linked"/>
<rdeContact:status s="clientDeleteProhibited"/> <rdeContact:status s="clientDeleteProhibited"/>
<rdeContact:postalInfo type="int"> <rdeContact:postalInfo type="int">
<contact:name>John Doe</contact:name> <contact:name>John Doe</contact:name>
<contact:org>Example Inc.</contact:org> <contact:org>Example Inc.</contact:org>
<contact:addr> <contact:addr>
<contact:street>123 Example Dr.</contact:street> <contact:street>123 Example Dr.</contact:street>
<contact:street>Suite 100</contact:street> <contact:street>Suite 100</contact:street>
<contact:city>Dulles</contact:city> <contact:city>Dulles</contact:city>
<contact:sp>VA</contact:sp> <contact:sp>VA</contact:sp>
skipping to change at page 48, line 34 skipping to change at page 48, line 34
<csvContact:fVoiceExt> Contains the contact's voice telephone number <csvContact:fVoiceExt> Contains the contact's voice telephone number
extension with type="token". extension with type="token".
<csvContact:fFax> Contains the contact's facsimile telephone number <csvContact:fFax> Contains the contact's facsimile telephone number
with type="contact:e164StringType". with type="contact:e164StringType".
<csvContact:fFaxExt> Contains the contact's facsimile telephone <csvContact:fFaxExt> Contains the contact's facsimile telephone
number extension with type="token". number extension with type="token".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the
elements (Section 4.7.2), MUST be used in the "contact" <rdeCsv:csv> "contact" <rdeCsv:csv> <rdeCsv:fields> element:
<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> Identifier of client (registrar) that sponsors the <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of:
contact object with isRequired="true".
<rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
of the client that created the object with isRequired="true".
<rdeCsv:fCrDate> Created date and time of the contact object with
isRequired="true".
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4, <rdeCsv:fClID> Identifier of the sponsoring client with
of the client that updated the object. isRequired="true".
<rdeCsv:fUpDate> Date and time of the last update to the contact <csvRegistrar:fGurid> Contains the ID assigned by ICANN with
object. type="positiveInteger". The attribute "isRequired" MUST equal
"true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "contact" <rdeCsv:csv> elements (Section 4.7.2), MAY be used in the "contact" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fCrID> Identifier of client that created the contact object. <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
of the client that created the object.
<rdeCsv:fCrID> Identifier of the client that created the contact
object.
<rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
of the client that updated the 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:fUpDate> Date and time of the last update to the contact
object.
<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.
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>
skipping to change at page 56, line 9 skipping to change at page 57, line 9
of the client that should take or took action with of the client that should take or took action with
isRequired="true". isRequired="true".
<rdeCsv:fAcDate> Date and time that the transfer action should be <rdeCsv:fAcDate> Date and time that the transfer action should be
taken or has been taken with isRequired="true". taken or has been taken with isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "contactTransfer" elements (Section 4.7.2), MAY be used in the "contactTransfer"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fReID> Identifier of client that requested the transfer. <rdeCsv:fReID> Identifier of the client that requested the transfer.
<rdeCsv:fAcID> Identifier of client that should take or took action <rdeCsv:fAcID> Identifier of the client that should take or took
for transfer. action for transfer.
The following "csvContact" fields, defined for the "contact" CSV File The following "csvContact" fields, defined for the "contact" CSV File
Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer"
<rdeCsv:csv> <rdeCsv:fields> element: <rdeCsv:csv> <rdeCsv:fields> element:
<csvContact:fId> Server-unique contact identifier for the contact <csvContact:fId> Server-unique contact identifier for the contact
object with isRequired="true". object with isRequired="true".
Example of a "contactTransfer" <csvContact:contents> <rdeCsv:csv> Example of a "contactTransfer" <csvContact:contents> <rdeCsv:csv>
element. element.
skipping to change at page 64, line 13 skipping to change at page 65, line 13
definitions. definitions.
5.4.2.1.1. "registrar" CSV File Definition 5.4.2.1.1. "registrar" CSV File Definition
The "registrar" CSV File Definition defines the fields and CSV file The "registrar" CSV File Definition defines the fields and CSV file
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> Contains the server-unique registrar identifier <csvRegistrar:fId> or <csvRegistrar:fGurid> A choice of:
with type="eppcom:clIDType" and isRequired="true".
<csvRegistrar:fId> Contains the server-unique registrar
identifier with type="eppcom:clIDType" and isRequired="true".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with
type="positiveInteger". The attribute "isRequired" MUST equal
"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".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with <csvRegistrar:fGurid> Contains the ID assigned by ICANN with
type="positiveInteger". type="positiveInteger". This field is included in this section in
addition to the section above to support optionally providing the
<csvRegistrar:fGurid> field when the <csvRegistrar:fId> field is
used.
<csvRegistrar:fWhoisUrl> Contains the Whois URL of the registrar <csvRegistrar:fWhoisUrl> Contains the Whois URL of the registrar
with type="anyURI". with type="anyURI".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "registrar" <rdeCsv:csv> elements (Section 4.7.2), MAY be used in the "registrar" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fCrDate> Created date and time of the registrar object. <rdeCsv:fCrDate> Created date and time of the registrar object.
skipping to change at page 65, line 13 skipping to change at page 66, line 23
Section 4.8. Section 4.8.
<csvContact:fCity> Registrar city with an OPTIONAL "isLoc" attribute <csvContact:fCity> Registrar city with an OPTIONAL "isLoc" attribute
that is used to indicate the localized or internationalized form, that is used to indicate the localized or internationalized form,
as defined in Section 4.8. as defined in Section 4.8.
<csvContact:fCc> Registrar country code with an OPTIONAL "isLoc" <csvContact:fCc> Registrar country code with an OPTIONAL "isLoc"
attribute that is used to indicate the localized or attribute that is used to indicate the localized or
internationalized form, as defined in Section 4.8. internationalized form, as defined in Section 4.8.
<csvContact:fEmail> Registrar email address. <csvContact:fEmail> Registrar email address. The attribute
"isRequired" MUST equal "false".
<csvContact:fSp> Registrar state or province with an OPTIONAL <csvContact:fSp> Registrar state or province with an OPTIONAL
"isLoc" attribute that is used to indicate the localized or "isLoc" attribute that is used to indicate the localized or
internationalized form, as defined in Section 4.8. internationalized form, as defined in Section 4.8.
<csvContact:fPc> Registrar postal code with an OPTIONAL "isLoc" <csvContact:fPc> Registrar postal code with an OPTIONAL "isLoc"
attribute that is used to indicate the localized or attribute that is used to indicate the localized or
internationalized form, as defined in Section 4.8. internationalized form, as defined in Section 4.8.
<csvContact:fVoice> Registrar voice telephone number. <csvContact:fVoice> Registrar voice telephone number.
skipping to change at page 66, line 28 skipping to change at page 67, line 28
<csvContact:fStreet isLoc="false" index="1"/> <csvContact:fStreet isLoc="false" index="1"/>
<csvContact:fStreet isLoc="false" index="2"/> <csvContact:fStreet isLoc="false" index="2"/>
<csvContact:fCity isLoc="false"/> <csvContact:fCity isLoc="false"/>
<csvContact:fSp isLoc="false" /> <csvContact:fSp isLoc="false" />
<csvContact:fPc isLoc="false" /> <csvContact:fPc isLoc="false" />
<csvContact:fCc isLoc="false"/> <csvContact:fCc isLoc="false"/>
<csvContact:fVoice/> <csvContact:fVoice/>
<csvContact:fVoiceExt/> <csvContact:fVoiceExt/>
<csvContact:fFax/> <csvContact:fFax/>
<csvContact:fFaxExt/> <csvContact:fFaxExt/>
<csvContact:fEmail/> <csvContact:fEmail isRequired="false"/>
<rdeCsv:fUrl/> <rdeCsv:fUrl/>
<csvRegistrar:fWhoisUrl/> <csvRegistrar:fWhoisUrl/>
<rdeCsv:fCrDate/> <rdeCsv:fCrDate/>
<rdeCsv:fUpDate/> <rdeCsv:fUpDate/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="57F6856F"> cksum="57F6856F">
registrar-YYYYMMDD.csv registrar-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
skipping to change at page 67, line 39 skipping to change at page 68, line 39
<csvRegistrar:deletes> is split into separate CSV file definitions <csvRegistrar:deletes> is split into separate CSV file definitions
using named <rdeCsv:csv> elements with the "name" attribute. The using named <rdeCsv:csv> elements with the "name" attribute. The
following section defines the supported registrar deletes CSV file following section defines the supported registrar deletes CSV file
definition. definition.
5.4.2.2.1. "registrar" Deletes CSV File Definition 5.4.2.2.1. "registrar" Deletes CSV File Definition
The following "csvRegistrar" field elements MUST be used in the The following "csvRegistrar" field elements MUST be used in the
deletes "registrar" <rdeCsv:csv> <rdeCsv:fields> element: deletes "registrar" <rdeCsv:csv> <rdeCsv:fields> element:
<csvRegistrar:fId> Contains the server-unique registrar identifier <csvRegistrar:fId> or <csvRegistrar:fGurid> A choice of:
with type="eppcom:clIDType" and isRequired="true".
<csvRegistrar:fId> Contains the server-unique registrar
identifier with type="eppcom:clIDType" and isRequired="true".
<csvRegistrar:fGurid> Contains the ID assigned by ICANN with
type="positiveInteger". The attribute "isRequired" MUST equal
"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>
<csvRegistrar:fId/> <csvRegistrar:fId/>
</rdeCsv:fields> </rdeCsv:fields>
skipping to change at page 70, line 16 skipping to change at page 71, line 16
The "idnLanguage" CSV File Definition defines the fields and CSV file The "idnLanguage" CSV File Definition defines the fields and CSV file
references used for the IDN table reference object records. references used for the IDN table reference object records.
The following "rdeCsv" fields, defined in Section 4.7.2, MUST be used The following "rdeCsv" fields, defined in Section 4.7.2, MUST be used
in the "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element: in the "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element:
<rdeCsv:fIdnTableId> The language identifier that matches the values <rdeCsv:fIdnTableId> The language identifier that matches the values
for the <rdeCsv:fIdnTableId> field element in the "domain" CSV for the <rdeCsv:fIdnTableId> field element in the "domain" CSV
File Definition (Section 5.1.2.1.1) files. The attribute File Definition (Section 5.1.2.1.1) files. The attribute
isRequired MUST equal "true". "isRequired" MUST equal "true".
<rdeCsv:fUrl> URL that defines the character code points that can be <rdeCsv:fUrl> URL that defines the character code points that can be
used for the language defined by the <rdeCsv:fLang> field element. used for the language defined by the <rdeCsv:fLang> field element.
The attribute isRequired MUST equal "true". The attribute "isRequired" MUST equal "true".
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"> <rdeCsv:csv name="idnLanguage">
<rdeCsv:sep>,</rdeCsv:sep> <rdeCsv:sep>,</rdeCsv:sep>
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fIdnTableId isRequired="true"/> <rdeCsv:fIdnTableId isRequired="true"/>
skipping to change at page 71, line 22 skipping to change at page 72, line 22
definition. definition.
5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition
The following "idnLanguage" field elements MUST be used in the The following "idnLanguage" field elements MUST be used in the
deletes "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element: deletes "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element:
<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".
Example of a "idnLanguage" <csvIDN:deletes> <rdeCsv:csv> element. Example of a "idnLanguage" <csvIDN:deletes> <rdeCsv:csv> element.
... ...
<csvIDN:deletes> <csvIDN:deletes>
... ...
<rdeCsv:csv name="idnLanguage"> <rdeCsv:csv name="idnLanguage">
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fIdnTableId isRequired="true"/> <rdeCsv:fIdnTableId isRequired="true"/>
</rdeCsv:fields> </rdeCsv:fields>
skipping to change at page 73, line 24 skipping to change at page 74, line 24
"withheld". This status is only used when the NNDN is used for "withheld". This status is only used when the NNDN is used for
an IDN variant. an IDN variant.
* If a NNDN is considered a mirrored IDN variant of a domain * If a NNDN is considered a mirrored IDN variant of a domain
object, then the NNDN will be tagged as "mirrored". A object, then the NNDN will be tagged as "mirrored". A
mirroringNS attribute is used to specify if the mirrored IDN mirroringNS attribute is used to specify if the mirrored IDN
variant use the NS mirror mechanism. The default value of variant use the NS mirror mechanism. The default value of
mirroringNS is true. If another mechanism such as DNAME is mirroringNS is true. If another mechanism such as DNAME is
used, the value of mirroringNS attribute MUST be false. used, the value of mirroringNS attribute MUST be false.
o A <crDate> element that contains the date and time of the NNDN o An OPTIONAL <crDate> element that contains the date and time of
object creation. the NNDN object creation.
Example of <rdeNNDN:NNDN> object: Example of <rdeNNDN:NNDN> object:
... ...
<rdeNNDN:NNDN> <rdeNNDN:NNDN>
<rdeNNDN:aName>xn--exampl-gva.test</rdeNNDN:aName> <rdeNNDN:aName>xn--exampl-gva.test</rdeNNDN:aName>
<rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId> <rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId>
<rdeNNDN:originalName>example1.test</rdeNNDN:originalName> <rdeNNDN:originalName>example1.test</rdeNNDN:originalName>
<rdeNNDN:nameState>withheld</rdeNNDN:nameState> <rdeNNDN:nameState>withheld</rdeNNDN:nameState>
<rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate> <rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate>
skipping to change at page 75, line 18 skipping to change at page 76, line 18
<csvNNDN:fOriginalName> Domain name used to generate the IDN variant <csvNNDN:fOriginalName> Domain name used to generate the IDN variant
with type="eppcom:labelType". with type="eppcom:labelType".
<csvNNDN:fMirroringNS> Defines whether the "mirroring" <csvNNDN:fMirroringNS> Defines whether the "mirroring"
<csvNNDN:fNameState> uses the NS mirror mechanism, as described <csvNNDN:fNameState> uses the NS mirror mechanism, as described
for the <rdeNNDN:nameState> "mirroringNS" attribute in for the <rdeNNDN:nameState> "mirroringNS" attribute in
Section 5.6.1.1, with type="boolean". If the field element is not Section 5.6.1.1, with type="boolean". If the field element is not
defined the default value is "true". defined the default value is "true".
The following "rdeCsv" fields, defined in section CSV common field The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MUST be used in the "domain" <rdeCsv:csv> elements (Section 4.7.2), MAY be used in the "NNDN" <rdeCsv:csv>
<rdeCsv:fields> element: <rdeCsv:fields> element:
<rdeCsv:fCrDate> Created date and time of the NNDN object with <rdeCsv:fCrDate> Created date and time of the NNDN object.
isRequired="true".
The following "rdeCsv" fields, defined in section CSV common field
elements (Section 4.7.2), MAY be used in the "domain" <rdeCsv:csv>
<rdeCsv:fields> element:
<rdeCsv:fUName> Name of the NNDN in Unicode character set for the <rdeCsv:fUName> Name of the NNDN in Unicode character set for the
<csvNNDN:fAName> field element. <csvNNDN:fAName> field element.
<rdeCsv:fIdnTableId> IDN Table Identifier for the NNDN that matches <rdeCsv:fIdnTableId> IDN Table Identifier for the NNDN that matches
an IDN Table Reference Object record, as defined in Section 5.5.2. an IDN Table Reference Object record, as defined in Section 5.5.2.
Example of a "NNDN" <csvNNDN:contents> <rdeCsv:csv> element: Example of a "NNDN" <csvNNDN:contents> <rdeCsv:csv> element:
... ...
skipping to change at page 88, line 10 skipping to change at page 89, line 10
default="eppcom\:clIDType"/> default="eppcom\:clIDType"/>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- Object Status Description --> <!-- Object Status Description -->
<element name="fStatusDescription" <element name="fStatusDescription"
type="rdeCsv:fNormalizedStringType" type="rdeCsv:fNormalizedStringType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- clID fields (fClID, fCrID, fUpID) --> <!-- clID fields (fClID, fCrID, fUpID) -->
<!-- Identifier of client that sponsors the object --> <!-- Identifier of the client that sponsors the object -->
<element name="fClID" type="rdeCsv:fClIDRequiredType" <element name="fClID" type="rdeCsv:fClIDRequiredType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Identifier of registrar of client <!-- Identifier of registrar of client
that created the object --> that created the object -->
<element name="fCrRr" type="rdeCsv:fClIDRequiredType" <element name="fCrRr" type="rdeCsv:fClIDType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Identifier of client that created the object --> <!-- Identifier of the client that created the object -->
<element name="fCrID" type="rdeCsv:fClIDType" <element name="fCrID" type="rdeCsv:fClIDType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Identifier of registrar of client that <!-- Identifier of registrar of client that
updated the object --> updated the object -->
<element name="fUpRr" type="rdeCsv:fClIDType" <element name="fUpRr" type="rdeCsv:fClIDType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Identifier of client that updated the object --> <!-- Identifier of the client that updated the object -->
<element name="fUpID" type="rdeCsv:fClIDType" <element name="fUpID" type="rdeCsv:fClIDType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Identifier of registrar of client that <!-- Identifier of registrar of client that
requested the transfer --> requested the transfer -->
<element name="fReRr" type="rdeCsv:fClIDType" <element name="fReRr" type="rdeCsv:fClIDRequiredType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Identifier of client that requested <!-- Identifier of the client that requested
the transfer --> the transfer -->
<element name="fReID" type="rdeCsv:fClIDType" <element name="fReID" type="rdeCsv:fClIDType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Identifier of registrar client that <!-- Identifier of registrar client that
should take or took action --> should take or took action -->
<element name="fAcRr" type="rdeCsv:fClIDRequiredType" <element name="fAcRr" type="rdeCsv:fClIDRequiredType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Identifier of client that should take or <!-- Identifier of the client that should take or
took action --> took action -->
<element name="fAcID" type="rdeCsv:fClIDType" <element name="fAcID" type="rdeCsv:fClIDType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<complexType name="fClIDType"> <complexType name="fClIDType">
<complexContent> <complexContent>
<extension base="rdeCsv:fieldOptionalType"> <extension base="rdeCsv:fieldOptionalType">
<sequence/> <sequence/>
<attribute name="type" type="token" <attribute name="type" type="token"
default="eppcom\:clIDType"/> default="eppcom\:clIDType"/>
</extension> </extension>
skipping to change at page 89, line 15 skipping to change at page 90, line 15
<complexContent> <complexContent>
<extension base="rdeCsv:fieldRequiredType"> <extension base="rdeCsv:fieldRequiredType">
<sequence/> <sequence/>
<attribute name="type" type="token" <attribute name="type" type="token"
default="eppcom\:clIDType"/> default="eppcom\:clIDType"/>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- dateTime fields (fCrDate, fUpDate, fExDate) --> <!-- dateTime fields (fCrDate, fUpDate, fExDate) -->
<element name="fCrDate" type="rdeCsv:fRequiredDateTimeType" <element name="fCrDate" type="rdeCsv:fDateTimeType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<element name="fUpDate" type="rdeCsv:fDateTimeType" <element name="fUpDate" type="rdeCsv:fDateTimeType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<element name="fExDate" type="rdeCsv:fDateTimeType" <element name="fExDate" type="rdeCsv:fDateTimeType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Date and time that transfer was requested --> <!-- Date and time that transfer was requested -->
<element name="fReDate" type="rdeCsv:fRequiredDateTimeType" <element name="fReDate" type="rdeCsv:fRequiredDateTimeType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Date and time of a required or completed response --> <!-- Date and time of a required or completed response -->
<element name="fAcDate" type="rdeCsv:fRequiredDateTimeType" <element name="fAcDate" type="rdeCsv:fRequiredDateTimeType"
skipping to change at page 103, line 33 skipping to change at page 104, line 33
<element name="roid" <element name="roid"
type="eppcom:roidType"/> type="eppcom:roidType"/>
<element name="status" <element name="status"
type="host:statusType" maxOccurs="7"/> type="host:statusType" maxOccurs="7"/>
<element name="addr" <element name="addr"
type="host:addrType" minOccurs="0" type="host:addrType" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<element name="clID" <element name="clID"
type="eppcom:clIDType"/> type="eppcom:clIDType"/>
<element name="crRr" <element name="crRr"
type="rde:rrType"/> type="rde:rrType" minOccurs="0"/>
<element name="crDate" <element name="crDate"
type="dateTime"/> type="dateTime" minOccurs="0"/>
<element name="upRr" <element name="upRr"
type="rde:rrType" minOccurs="0"/> type="rde:rrType" minOccurs="0"/>
<element name="upDate" <element name="upDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="trDate" <element name="trDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
skipping to change at page 109, line 8 skipping to change at page 110, line 8
type="contact:postalInfoType" maxOccurs="2"/> type="contact:postalInfoType" maxOccurs="2"/>
<element name="voice" <element name="voice"
type="contact:e164Type" minOccurs="0"/> type="contact:e164Type" minOccurs="0"/>
<element name="fax" <element name="fax"
type="contact:e164Type" minOccurs="0"/> type="contact:e164Type" minOccurs="0"/>
<element name="email" <element name="email"
type="eppcom:minTokenType"/> type="eppcom:minTokenType"/>
<element name="clID" <element name="clID"
type="eppcom:clIDType"/> type="eppcom:clIDType"/>
<element name="crRr" <element name="crRr"
type="rde:rrType"/> type="rde:rrType" minOccurs="0"/>
<element name="crDate" <element name="crDate"
type="dateTime"/> type="dateTime" minOccurs="0"/>
<element name="upRr" <element name="upRr"
type="rde:rrType" minOccurs="0"/> type="rde:rrType" minOccurs="0"/>
<element name="upDate" <element name="upDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="trDate" <element name="trDate"
type="dateTime" minOccurs="0"/> type="dateTime" minOccurs="0"/>
<element name="trnData" <element name="trnData"
type="rdeContact:transferDataType" minOccurs="0"/> type="rdeContact:transferDataType" minOccurs="0"/>
<element name="disclose" <element name="disclose"
type="contact:discloseType" minOccurs="0"/> type="contact:discloseType" minOccurs="0"/>
skipping to change at page 123, line 35 skipping to change at page 124, line 35
type="rdeCsv:fPositiveIntegerType" type="rdeCsv:fPositiveIntegerType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<!-- Registrar status field --> <!-- Registrar status field -->
<element name="fStatus" type="csvRegistrar:fStatusType" <element name="fStatus" type="csvRegistrar:fStatusType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<element name="fStatusName" type="rdeCsv:fTokenType" <element name="fStatusName" type="rdeCsv:fTokenType"
substitutionGroup="rdeCsv:field"/> substitutionGroup="rdeCsv:field"/>
<complexType name="fStatusType"> <complexType name="fStatusType">
<complexContent> <complexContent>
<extension base="rdeCsv:fieldRequiredType"> <extension base="rdeCsv:fieldOptionalType">
<sequence/> <sequence/>
<attribute name="type" type="token" <attribute name="type" type="token"
default="csvRegistrar\:statusType"/> default="csvRegistrar\:statusType"/>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- Registrar status type with optional name attr --> <!-- Registrar status type with optional name attr -->
<complexType name="statusType"> <complexType name="statusType">
<simpleContent> <simpleContent>
skipping to change at page 131, line 34 skipping to change at page 132, line 34
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"/> 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" />
skipping to change at page 150, line 41 skipping to change at page 151, line 41
16.13. Changes REGEXT 00 to REGEXT 01 16.13. Changes REGEXT 00 to REGEXT 01
1. Added the <rdeHeader:reseller> element to the 1. Added the <rdeHeader:reseller> element to the
"repositoryTypeGroup" group element in the rdeHeader. "repositoryTypeGroup" group element in the rdeHeader.
2. Privacy consideration section was added 2. Privacy consideration section was added
3. Updates on section 8 3. Updates on section 8
16.14. Changes REGEXT 01 to REGEXT 02
1. Added a choice between the use of the <rdeCsv:fClID> or
<csvRegistrar:fGurid> fields in the CSV "domain", "host", and
"contact" definitions.
2. Added a choice between the use of the <rdeCsv:fRoid> or
<csvHost:fName> fields in the CSV "domainNameServers"
definition.
3. Changed "of client" to "of the client" throughout the document.
4. Modified all references of 'The attribute isRequired MUST equal
"true".' to 'The attribute "isRequired" MUST equal "true".'
5. Combined the <csvDomain:fName> and <csvDomain:fContactType>
fields in a single required list for the CSV "domainContacts"
definition.
6. Combined the <csvDomain:fName>, <csvDomain:fStatus>, and
<csvDomain:fRgpStatus> fields in a single required list for the
CSV "domainStatuses" definition.
7. Moved the <rdeCsv:fCrRr> the <rdeCsv:fUpRr> fields to the MAY
list for the CSV "domain", "host", and "contact" definitions.
8. Made the order of the <rdeCsv:fCrRr>, <rdeCsv:crID>,
<rdeCsv:UpRr>, and <rdeCsv:UpID> fields more consistent in the
CSV lists.
9. Fixed an error in the order of the <contact> object example.
10. Changed <rdeCsv:fCrDate> to be optional to match <crDate> being
optional in the XML model, by having it use type
rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and
ensuring that <rdeCsv:fCrDate> is included in the MAY field
lists and not the MUST field lists.
11. Made <rdeCsv:fExDate> optional for the "domain" CSV definition
to be consistent with the XML model, by removing the sentence
'The attribute "isRequired" MUST equal "true".' from the
description and moving the field to the MAY field list.
12. Made <rdeCsv:fUpDate> optional for the "domain" and "contact"
CSV definitions to be consistent with the XML model, by moving
the field to the MAY field list.
13. Made <rdeCsv:fCrRr> optional to be consistent with the XML
model, by having it use type rdeCsv:fClIDType instead of
rdeCsv:fClIDRequiredType.
14. Made <rdeCsv:fReRr> required to be consistent with the XML
model, by having it use type rdeCsv:fClIDRequiredType instead of
rdeCsv:fClIDType.
15. Made the <csvRegistrar:fGurid> field in the "host", "contact",
and "registrar" CSV definitions required explicitly by removing
'and isRequired="true"' and adding the sentence 'The attribute
isRequired MUST equal "true".', when it is chosen as the primary
field.
16. Removed extra '/>.' at the end of the <csvHost:fStatus> field
description in the "hostStatuses" CSV definition.
17. Made the <csvRegistrar:fStatus> field optional to be consistent
with the XML model, by having csvRegistrar:fStatusType extend
rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType.
18. Made the <csvContact:fEmail> field for the "registrar" CSV
definition explicitly optional to be consistent with the XML
model, by adding the sentence 'The attribute isRequired MUST
equal "false".' to the field description and including the
definition of isRequired="false" in the "registrar" CSV
definition examples.
19. Added the choice between the use of the <csvRegistrar:fId> and
<csvRegistrar:fGurid> fields in the deletes "registrar" CSV
definition to be consistent with the "registrar" CSV definition.
20. Made the <crRr> and <crDate> elements optional for the host and
contact objects in the XML model to be consistent with the
domain object.
17. Example of a full deposit using the XML model 17. Example of a full deposit using the XML model
Example of a full deposit using the XML model: Example of a full deposit using the XML model:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit type="FULL" id="20101017001" prevId="20101010001" <rde:deposit type="FULL" id="20101017001" prevId="20101010001"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
skipping to change at page 160, line 8 skipping to change at page 162, line 43
<rdeCsv:file <rdeCsv:file
cksum="EB8C548E"> cksum="EB8C548E">
domainStatuses-YYYYMMDD.csv domainStatuses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
<rdeCsv:csv name="domainNameServers" sep=","> <rdeCsv:csv name="domainNameServers" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<csvHost:fName parent="true"/> <csvHost:fName parent="true"/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="984C3097"> cksum="984C3097">
domainNameServers-name-YYYYMMDD.csv domainNameServers-name-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
<rdeCsv:csv name="domainNameServers" sep=","> <rdeCsv:csv name="domainNameServers" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
skipping to change at page 165, line 7 skipping to change at page 167, line 42
<csvContact:fStreet isLoc="false" index="1"/> <csvContact:fStreet isLoc="false" index="1"/>
<csvContact:fStreet isLoc="false" index="2"/> <csvContact:fStreet isLoc="false" index="2"/>
<csvContact:fCity isLoc="false" /> <csvContact:fCity isLoc="false" />
<csvContact:fSp isLoc="false" /> <csvContact:fSp isLoc="false" />
<csvContact:fPc isLoc="false" /> <csvContact:fPc isLoc="false" />
<csvContact:fCc isLoc="false" /> <csvContact:fCc isLoc="false" />
<csvContact:fVoice/> <csvContact:fVoice/>
<csvContact:fVoiceExt/> <csvContact:fVoiceExt/>
<csvContact:fFax/> <csvContact:fFax/>
<csvContact:fFaxExt/> <csvContact:fFaxExt/>
<csvContact:fEmail/> <csvContact:fEmail isRequired="false"/>
<rdeCsv:fUrl/> <rdeCsv:fUrl/>
<csvRegistrar:fWhoisUrl/> <csvRegistrar:fWhoisUrl/>
<rdeCsv:fCrDate/> <rdeCsv:fCrDate/>
<rdeCsv:fUpDate/> <rdeCsv:fUpDate/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="306178BB"> cksum="306178BB">
registrar-YYYYMMDD.csv registrar-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
</csvRegistrar:contents> </csvRegistrar:contents>
<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"/>
</rdeCsv:fields> </rdeCsv:fields>
skipping to change at page 171, line 5 skipping to change at page 173, line 40
<rdeCsv:file <rdeCsv:file
cksum="984C3097"> cksum="984C3097">
domainNameServers-name-YYYYMMDD.csv domainNameServers-name-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
<rdeCsv:csv name="domainNameServers" sep=","> <rdeCsv:csv name="domainNameServers" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="569D4638"> cksum="569D4638">
domainNameServers-roid-YYYYMMDD.csv domainNameServers-roid-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
<rdeCsv:csv name="dnssec" sep=","> <rdeCsv:csv name="dnssec" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
skipping to change at page 175, line 40 skipping to change at page 178, line 27
<csvContact:fStreet isLoc="false" index="1"/> <csvContact:fStreet isLoc="false" index="1"/>
<csvContact:fStreet isLoc="false" index="2"/> <csvContact:fStreet isLoc="false" index="2"/>
<csvContact:fCity isLoc="false" /> <csvContact:fCity isLoc="false" />
<csvContact:fSp isLoc="false" /> <csvContact:fSp isLoc="false" />
<csvContact:fPc isLoc="false" /> <csvContact:fPc isLoc="false" />
<csvContact:fCc isLoc="false" /> <csvContact:fCc isLoc="false" />
<csvContact:fVoice/> <csvContact:fVoice/>
<csvContact:fVoiceExt/> <csvContact:fVoiceExt/>
<csvContact:fFax/> <csvContact:fFax/>
<csvContact:fFaxExt/> <csvContact:fFaxExt/>
<csvContact:fEmail/> <csvContact:fEmail isRequired="false"/>
<rdeCsv:fUrl/> <rdeCsv:fUrl/>
<csvRegistrar:fWhoisUrl/> <csvRegistrar:fWhoisUrl/>
<rdeCsv:fCrDate/> <rdeCsv:fCrDate/>
<rdeCsv:fUpDate/> <rdeCsv:fUpDate/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="306178BB"> cksum="306178BB">
registrar-YYYYMMDD.csv registrar-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
skipping to change at page 179, line 19 skipping to change at page 181, line 51
[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/ <http://www.icann.org/en/topics/idn/idn-vip-integrated-
idn-vip-integrated-issues-final-clean-20feb12-en.pdf>. issues-final-clean-20feb12-en.pdf>.
21.3. URIs 21.3. URIs
[1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data- [1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data-
escrow-05.txt escrow-05.txt
Authors' Addresses Authors' Addresses
Gustavo Lozano Gustavo Lozano
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
 End of changes. 89 change blocks. 
200 lines changed or deleted 309 lines changed or added

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