1 Internet Engineering Task Force (IETF) G. Lozano
2 Request for Comments: 9022 ICANN
3 Category: Standards Track J. Gould
4 ISSN: 2070-1721 C. Thippeswamy
5 VeriSign
6 May 2021
7
8
9 Domain Name Registration Data (DNRD) Objects Mapping
10
11 Abstract
12
13 This document specifies the format, contents, and semantics of Domain
14 Name Registration Data (DNRD) escrow deposits for a domain name
15 registry.
16
17 Status of This Memo
18
19 This is an Internet Standards Track document.
20
21 This document is a product of the Internet Engineering Task Force
22 (IETF). It represents the consensus of the IETF community. It has
23 received public review and has been approved for publication by the
24 Internet Engineering Steering Group (IESG). Further information on
25 Internet Standards is available in Section 2 of RFC 7841.
26
27 Information about the current status of this document, any errata,
28 and how to provide feedback on it may be obtained at
29 https://www.rfc-editor.org/info/rfc9022.
30
31 Copyright Notice
32
33 Copyright (c) 2021 IETF Trust and the persons identified as the
34 document authors. All rights reserved.
35
36 This document is subject to BCP 78 and the IETF Trust's Legal
37 Provisions Relating to IETF Documents
38 (https://trustee.ietf.org/license-info) in effect on the date of
39 publication of this document. Please review these documents
40 carefully, as they describe your rights and restrictions with respect
41 to this document. Code Components extracted from this document must
42 include Simplified BSD License text as described in Section 4.e of
43 the Trust Legal Provisions and are provided without warranty as
44 described in the Simplified BSD License.
45
46 Table of Contents
47
48 1. Introduction
49 2. Models
50 2.1. XML Model
51 2.2. CSV Model
52 3. Terminology
53 3.1. Glossary
54 4. Conventions Used in This Document
55 4.1. Date and Time
56 4.2. Country Names
57 4.3. Telephone Numbers
58 4.4. CSV Integrity Check
59 4.5. IP Addresses
60 4.6. Conventions Applicable to the CSV Model
61 5. Object Description
62 5.1. Domain Name Object
63 5.2. Host Object
64 5.3. Contact Object
65 5.4. Registrar Object
66 5.5. IDN Table Reference Object
67 5.6. NNDN Object
68 5.7. EPP Parameters Object
69 5.8. Policy Object
70 5.9. Header Object
71 5.10. DNRD Common Objects Collection
72 6. RDE IDN Variants Handling
73 7. Profile
74 8. Data Escrow Agent Extended Verification Process
75 9. Formal Syntax
76 9.1. RDE CSV Schema
77 9.2. RDE Domain Object
78 9.3. CSV Domain Object
79 9.4. RDE Host Object
80 9.5. CSV Host Object
81 9.6. RDE Contact Object
82 9.7. CSV Contact Object
83 9.8. RDE Registrar Object
84 9.9. CSV Registrar Object
85 9.10. RDE IDN Table Reference Objects
86 9.11. CSV IDN Language Object
87 9.12. EPP Parameters Object
88 9.13. NNDN Object
89 9.14. CSV NNDN Object
90 9.15. Policy Object
91 9.16. Header Object
92 9.17. DNRD Common Objects
93 10. Internationalization Considerations
94 11. IANA Considerations
95 12. Security Considerations
96 13. Privacy Considerations
97 14. Example of a Full Deposit Using the XML Model
98 15. Example of a Differential Deposit Using the XML Model
99 16. Example of a Full Deposit Using the CSV Model
100 17. Example of a Differential Deposit Using the CSV Model
101 18. References
102 18.1. Normative References
103 18.2. Informative References
104 Acknowledgments
105 Authors' Addresses
106
107 1. Introduction
108
109 Registry Data Escrow (RDE) is the process by which a registry
110 periodically submits data deposits to a third party called an escrow
111 agent. These deposits comprise the minimum data needed by a third
112 party to resume operations if the registry cannot function and is
113 unable or unwilling to facilitate an orderly transfer of service.
114 For example, for a domain name registry or registrar, the data to be
115 deposited would include all the objects related to registered domain
116 names, e.g., names, contacts, name servers, etc.
117
118 The goal of data escrow is higher resiliency of registration services
119 for the benefit of Internet users. The beneficiaries of a registry
120 are not just those registering information there, but also the users
121 of services relying on the registry data.
122
123 In the context of domain name registries, registration data escrow is
124 a requirement for generic top-level domains (e.g., Specification 2 of
125 the ICANN Base Registry Agreement, see [ICANN-GTLD-RA-20170731]) and
126 some country code top-level domain managers are also currently
127 escrowing data. There is also a similar requirement for ICANN-
128 accredited domain registrars.
129
130 This document defines the standard set of objects for a domain name
131 registry that uses the Registry Data Escrow Specification described
132 in [RFC8909] for escrow. The set of objects include:
133
134 Domain: Internet domain names that are typically provisioned in a
135 domain name registry using the Extensible Provisioning Protocol
136 (EPP) domain name mapping [RFC5731]. The attributes defined in
137 the EPP domain name mapping [RFC5731] are fully supported by this
138 document.
139
140 Host: Internet host names that are typically provisioned in a domain
141 name registry using the EPP host mapping [RFC5732]. The
142 attributes defined in the EPP host mapping [RFC5732] are fully
143 supported by this document.
144
145 Contact: Individual or organization social information provisioned
146 in a domain name registry using the EPP contact mapping [RFC5733].
147 The attributes defined in the EPP contact mapping [RFC5733] are
148 fully supported by this document.
149
150 Registrar: The organization that sponsors objects like domains,
151 hosts, and contacts in a domain name registry.
152
153 NNDN (NNDN's not domain name): Domain Name Registries may maintain
154 domain names without being persisted as domain objects in the
155 registry system, for example, a list of reserved names not
156 available for registration. The NNDN is a lightweight domain-like
157 object that is used to escrow domain names not maintained as
158 domain name objects.
159
160 This document defines the following pseudo-objects:
161
162 IDN table reference: Internationalized Domain Names (IDN) included
163 in the domain object data escrow include references to the IDN
164 table and policy used in IDN registration.
165
166 EPP parameters: Contains the EPP parameters supported by the
167 registry operator.
168
169 Header: Used to specify counters of objects in the database at a
170 certain point in time (Timeline Watermark).
171
172 Policy: Used to specify OPTIONAL elements from this specification
173 that are REQUIRED based on the business model of the registry.
174
175 Extensible Markup Language (XML) 1.0 as described in
176 [W3C.REC-xml-20081126] and XML Schema notation as described in
177 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028] are
178 used in this specification.
179
180 2. Models
181
182 This document defines two different models that can be used to
183 deposit data escrow objects: XML and CSV (comma-separated values).
184
185 The data escrow deposit MAY contain a mix of both models, but an
186 object MUST be escrowed only in one model.
187
188 This document does not suggest the use of a particular model, and
189 both are equivalent. A domain name registry may choose the model
190 that is more appropriate for the peculiarities of its systems. For
191 example, a registry may use the CSV-export functionality of the
192 Relational Database Management System (RDBMS) for escrow; therefore,
193 the CSV model may be more appropriate. Another registry may use the
194 code developed for EPP to implement escrow.
195
196 2.1. XML Model
197
198 The XML model includes all the deposit information (metadata and
199 data) in an XML document. The definition of the XML format is fully
200 defined in the XML schemas. As a convention, the objects represented
201 using the XML model are referenced using RDE and an XML namespace
202 that is prefixed with "rde". For example, the Domain Name object
203 represented using the XML model can be referred to as the RDE Domain
204 Name with the XML namespace including rdeDomain
205 (urn:ietf:params:xml:ns:rdeDomain-1.0).
206
207 2.2. CSV Model
208
209 The CSV model uses XML to define the data escrow format of the data
210 contained in referenced CSV files. As a convention, the objects
211 represented using the CSV model is referenced using CSV and an XML
212 namespace that is prefixed with "csv". For example, the domain name
213 object represented using the CSV model can be referred to as the CSV
214 Domain Name with the XML namespace including csvDomain
215 (urn:ietf:params:xml:ns:csvDomain-1.0).
216
217 3. Terminology
218
219 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
220 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
221 "OPTIONAL" in this document are to be interpreted as described in
222 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
223 capitals, as shown here.
224
225 3.1. Glossary
226
227 In the following section, the most common terms are briefly
228 explained:
229
230 Allocated: A status of some label with respect to a zone, whereby
231 the label is associated administratively to some entity that has
232 requested the label. This term (and its cognates "allocation" and
233 "to allocate") may represent the first step on the way to
234 delegation in the DNS.
235
236 Comma-Separated Values (CSV): See [RFC4180].
237
238 Domain Name: See the definition of Domain Name in Section 2 of
239 [RFC8499].
240
241 Extensible Provisioning Protocol (EPP): See the definition of the
242 Extensible Provisioning Protocol in Section 9 of [RFC8499].
243
244 Fully-Qualified Domain Name (FQDN): See the definition of FQDN in
245 Section 2 of [RFC8499].
246
247 Internationalized Domain Name (IDN): See the definition of
248 Internationalized Domain Name in Section 2 of [RFC8499].
249
250 Label See the definition of Label in Section 2 of [RFC8499].
251
252 Registrant: See the definition of Registrant in Section 9 of
253 [RFC8499].
254
255 Registrar: See the definition of Registrar in Section 9 of
256 [RFC8499].
257
258 Registry: See the definition of Registry in Section 9 of [RFC8499].
259
260 Registry-Class Domain Name (RCDN): Refers to a top-level domain
261 (TLD) or any other domain name at any level in the DNS tree for
262 which a registry (either directly or through an affiliate company)
263 provides Registry Services for other organizations or individuals.
264 For example: .COM, .ORG, .BIZ, .CO.JP, .B.BR.
265
266 Registry Data Escrow (RDE): Registry Data Escrow is the process by
267 which a registry periodically submits data deposits to a third
268 party called an escrow agent. These deposits comprise the minimum
269 data needed by a third party to resume operations if the registry
270 cannot function and is unable or unwilling to facilitate an
271 orderly transfer of service.
272
273 Registry Services: Services offered by the registry critical to the
274 following tasks: the provisioning of domain names on receipt of
275 requests and data from registrars; responding to registrar queries
276 for status information relating to the DNS servers for the RCDN;
277 dissemination of RCDN zone files; operation of the registry DNS
278 servers; responding to queries for contact and other information
279 concerning DNS registrations in the RCDN; and any other products
280 or services that only a registry is capable of providing, by
281 reason of its designation as the registry. Typical examples of
282 Registry Services are DNS resolution for the RCDN, WHOIS, and EPP.
283
284 SRS: Shared Registration System, see also [ICANN-GTLD-AGB-20120604].
285
286 Top-Level Domain Name (TLD): See the definition of Top-Level Domain
287 in Section 2 of [RFC8499].
288
289 UTC: Coordinated Universal Time, as maintained by the Bureau
290 International des Poids et Mesures (BIPM), see also [RFC3339].
291
292 4. Conventions Used in This Document
293
294 4.1. Date and Time
295
296 Numerous fields indicate "dates", such as the creation and expiry
297 dates for domain names. These fields SHALL contain timestamps
298 indicating the date and time in UTC as specified in [RFC3339], with
299 no offset from the zero meridian.
300
301 4.2. Country Names
302
303 Country identifiers SHALL be represented using two character
304 identifiers as specified in [ISO-3166-1].
305
306 4.3. Telephone Numbers
307
308 Telephone numbers (both voice and facsimile) SHALL be formatted based
309 on structures defined in [ITU-E164]. Telephone numbers described in
310 this specification are character strings that MUST begin with a plus
311 sign ("+", ASCII value 0x2B), followed by a country code defined in
312 [ITU-E164], followed by a dot (".", ASCII value 0x2E), followed by a
313 sequence of digits representing the telephone number.
314
315 4.4. CSV Integrity Check
316
317 A checksum MAY be used to verify the integrity of the CSV files, for
318 example, if another layer (i.e., encryption of an archive containing
319 the deposit files) does not provide integrity. By default, the CRC32
320 algorithm (see Section 8.1.1.6.2 of [V42]) is used. A stronger
321 algorithm, such as SHA-256 (see [RFC6234]) MAY be used for enhanced
322 security if required.
323
324 4.5. IP Addresses
325
326 The syntax of IP addresses MUST conform to the text representation of
327 either Internet Protocol Version 4 [RFC0791] or Internet Protocol
328 Version 6 [RFC5952].
329
330 4.6. Conventions Applicable to the CSV Model
331
332 4.6.1. CSV Parent Child Relationship
333
334 The CSV model represents a relational model where the CSV files
335 represent relational tables, the fields of the CSV files represent
336 columns of the tables, and each line of the CSV file represents a
337 record. As in a relational model, the CSV files can have
338 relationships utilizing primary keys in the parent CSV file
339 definitions and foreign keys in the child CSV file definitions for a
340 one-to-many relationship. The primary keys are not explicitly
341 defined, but the foreign keys are using the boolean "parent" field
342 attribute in the child CSV file. The relationships between the CSV
343 files are used to support a cascade replace or cascade delete of
344 records starting from the parent record in Differential and
345 Incremental Deposits (see [RFC8909]).
346
347 The following is an example of the CSV file definitions, using the
348 element <rdeCsv:csv> (see Section 4.6.2.1), for a Sample object
349 consisting of a parent "sample" CSV File Definition and a child
350 "sampleStatuses" CSV File Definition. The primary key for the Sample
351 object is the field <csvSample:fName> that is used as the foreign key
352 in the "sampleStatuses" CSV File Definition by specifying the
353 "parent=true" attribute. If a Sample record is updated or deleted in
354 a Differential or Incremental Deposit, it should cascade replace the
355 data using the records included in the child "sampleStatuses" CSV
356 File Definition or cascade delete the existing records in the child
357 "sampleStatuses" CSV File Definition, respectively.
358
359 <csvSample:contents>
360 ...
361 <rdeCsv:csv name="sample" sep=",">
362 <rdeCsv:fields>
363 <csvSample:fName/>
364 <rdeCsv:fClID/>
365 <rdeCsv:fCrRr/>
366 <rdeCsv:fCrID/>
367 <rdeCsv:fCrDate/>
368 <rdeCsv:fUpRr/>
369 <rdeCsv:fUpID/>
370 <rdeCsv:fUpDate/>
371 <rdeCsv:fExDate/>
372 </rdeCsv:fields>
373 <rdeCsv:files>
374 <rdeCsv:file
375 cksum="75E2D22F">
376 sample-YYYYMMDD.csv
377 </rdeCsv:file>
378 </rdeCsv:files>
379 </rdeCsv:csv>
380 <rdeCsv:csv name="sampleStatuses" sep=",">
381 <rdeCsv:fields>
382 <csvSample:fName parent="true"/>
383 <csvSample:fStatus/>
384 <rdeCsv:fStatusDescription/>
385 <rdeCsv:fLang/>
386 </rdeCsv:fields>
387 <rdeCsv:files>
388 <rdeCsv:file
389 cksum="EB9C558E">
390 sampleStatuses-YYYYMMDD.csv
391 </rdeCsv:file>
392 </rdeCsv:files>
393 </rdeCsv:csv>
394 ...
395 </csvSample:contents>
396
397 4.6.2. CSV Elements
398
399 4.6.2.1. <rdeCsv:csv> Element
400
401 To support the CSV model, an element is defined for each object that
402 substitutes for the <rde:content> element and for the <rde:delete>
403 element, that contains one or more <rdeCsv:csv> elements. For
404 example, the 'Domain Name Object' (Section 5.1) defines the
405 <csvDomain:contents> element, that substitutes for the <rde:content>
406 element, and the <csvDomain:deletes> element, that substitutes for
407 the <rde:delete> element. Both the <csvDomain:contents> element and
408 the <csvDomain:deletes> elements contain one or more <rdeCsv:csv>
409 elements. The <rdeCsv:csv> element has the following child elements:
410
411 <rdeCsv:fields> Ordered list of CSV fields used in the CSV files.
412 There are one or more child elements that substitute for the
413 <rdeCsv:field> abstract element. Each element defines the format
414 of the CSV field contained in the CSV files. The <rdeCsv:field>
415 elements support the "type" attribute that defines the XML simple
416 data type of the field element. The <rdeCsv:field> elements
417 support the "isRequired" attribute, which has a default value of
418 "false". When set to "true", this indicates that the field must
419 be non-empty in the CSV files, and when set to "false", this
420 indicates that the field MAY be empty in the CSV files. The
421 "isRequired" attribute MAY be specifically set for the field
422 elements within the XML schema and MAY be overridden when
423 specifying the fields under the <rdeCsv:fields> element. The
424 <rdeCsv:field> element supports an OPTIONAL "parent" attribute
425 that identifies the field as a reference to a parent object, as
426 defined in the 'CSV Parent Child Relationship' (Section 4.6.1).
427 For example, the <rdeCsv:csv name="domainStatuses">
428 <csvDomain:fName> field SHOULD set the "parent" attribute to
429 "true" to identify it as the parent domain name of the domain
430 status.
431
432 <rdeCsv:files> A list of one or more CSV files using the
433 <rdeCsv:file> child element. The <rdeCsv:file> child element
434 defines a reference to the CSV file name and has the following
435 optional attributes:
436
437 compression If the CSV file is compressed, the "compression"
438 attribute defines the compression format. For example, setting
439 this attribute to "gzip" signals that the CSV file is
440 compressed using the GZIP file format (see [RFC1952]). The
441 supported compression formats are negotiated out of band.
442
443 encoding Defines the encoding of the CSV file with the default
444 encoding of "UTF-8".
445
446 cksum Defines the checksum of the CSV file, as described in
447 Section 4.4, using the algorithm defined by the "cksumAlg"
448 attribute. If the "cksumAlg" attribute is not present, the
449 checksum is calculated using "CRC32".
450
451 cksumAlg Defines the checksum algorithm used to calculate the
452 "cksum" attribute, with the default value of "CRC32". If the
453 value "SHA256" is specified, the SHA-256 algorithm (see
454 [RFC6234]) MUST be used to calculate the "cksum" attribute.
455 Parties receiving and processing data escrow deposits MUST
456 support CRC32 and SHA-256. If this attribute is present, the
457 "cksum" attribute MUST also be present. Additional checksum
458 algorithms are negotiated out of band.
459
460 The <rdeCsv:csv> element requires a "name" attribute that defines the
461 purpose of the CSV file with values like "domain", "host", "contact".
462 The supported "name" attribute values are defined for each object
463 type. The OPTIONAL "sep" attribute defines the CSV separator
464 character with the default separator character of ",". The need for
465 quoting or escaping of the CSV data could be avoided by choosing a
466 separator character that is not in the data set of the CSV files.
467
468 The following is an example of the <csvDomain:contents> <rdeCsv:csv>
469 element for domain name records where the <rdeCsv:fRegistrant> is set
470 as required with isRequired="true".
471
472 <csvDomain:contents>
473 ...
474 <rdeCsv:csv name="domain" sep=",">
475 <rdeCsv:fields>
476 <csvDomain:fName/>
477 <rdeCsv:fRoid/>
478 <rdeCsv:fIdnTableId/>
479 <csvDomain:fOriginalName/>
480 <rdeCsv:fRegistrant isRequired="true"/>
481 <rdeCsv:fClID/>
482 <rdeCsv:fCrRr/>
483 <rdeCsv:fCrID/>
484 <rdeCsv:fCrDate/>
485 <rdeCsv:fUpRr/>
486 <rdeCsv:fUpID/>
487 <rdeCsv:fUpDate/>
488 <rdeCsv:fExDate/>
489 </rdeCsv:fields>
490 <rdeCsv:files>
491 <rdeCsv:file
492 cksum="75E2D01F">
493 domain-YYYYMMDD.csv
494 </rdeCsv:file>
495 </rdeCsv:files>
496 </rdeCsv:csv>
497 ...
498 </csvDomain:contents>
499
500 The following is an example of the domain-YYYYMMDD.csv file with one
501 record matching the <rdeCsv:fields> definition.
502
503 domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX,
504 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
505 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
506
507 The following is an example of the <csvDomain:deletes> <rdeCsv:csv>
508 element for domain name records.
509
510 <csvDomain:deletes>
511 ...
512 <rdeCsv:csv name="domain">
513 <rdeCsv:fields>
514 <csvDomain:fName/>
515 </rdeCsv:fields>
516 <rdeCsv:files>
517 <rdeCsv:file
518 cksum="6F2B988F">
519 domain-delete-YYYYMMDD.csv
520 </rdeCsv:file>
521 </rdeCsv:files>
522 </rdeCsv:csv>
523 ...
524 </csvDomain:deletes>
525
526 The following is example of the domain-delete-YYYYMMDD.csv file with
527 three records that matches the single <csvDomain:fName> field.
528
529 domain1.example
530 domain2.example
531 domainN.example
532
533 4.6.2.2. CSV Common Field Elements
534
535 The <rdeCsv:fields> element defined in the '<rdeCsv:csv> Element'
536 (Section 4.6.2.1) has child elements that substitute for the abstract
537 <rdeCsv:field> element. By convention, <rdeCsv:field> elements
538 include an "f" prefix to identify them as field definition elements.
539 There are a set of common field elements that are used across
540 multiple data escrow objects. The common field elements are defined
541 using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and using the
542 "rdeCsv" sample namespace prefix. The CSV common field elements
543 include:
544
545 <rdeCsv:fUName> UTF-8 encoded name field with
546 type="eppcom:labelType".
547
548 <rdeCsv:fRoid> Repository Object IDentifier (ROID) field with
549 type="eppcom:roidType" and isRequired="true".
550
551 <rdeCsv:fRegistrant> Registrant contact identifier with
552 type="eppcom:clIDType".
553
554 <rdeCsv:fStatusDescription> The object status description, which is
555 free-form text describing the rationale for the status, with
556 type="normalizedString".
557
558 <rdeCsv:fClID> Identifier of the client (registrar) that sponsors
559 the object with type="eppcom:clIDType" and isRequired="true".
560
561 <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
562 of the client that created the object with type="eppcom:clIDType".
563
564 <rdeCsv:fCrID> Identifier of the client that created the object with
565 type="eppcom:clIDType".
566
567 <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
568 of the client that last updated the object with
569 type="eppcom:clIDType".
570
571 <rdeCsv:fUpID> Identifier of the client that last updated the object
572 with type="eppcom:clIDType".
573
574 <rdeCsv:fReRr> Identifier of the registrar, defined in Section 5.4,
575 of the client that requested the transfer with
576 type="eppcom:clIDType" and isRequired="true".
577
578 <rdeCsv:fReID> Identifier of the client that requested the transfer
579 with type="eppcom:clIDType".
580
581 <rdeCsv:fAcRr> Identifier of the registrar, defined in Section 5.4,
582 of the client that should take or took action with
583 type="eppcom:clIDType" and isRequired="true".
584
585 <rdeCsv:fAcID> Identifier of the client that should take or took
586 action for transfer with type="eppcom:clIDType".
587
588 <rdeCsv:fCrDate> Created date of object with type="dateTime".
589
590 <rdeCsv:fUpDate> Updated date of object with type="dateTime".
591
592 <rdeCsv:fExDate> Expiration date of object with type="dateTime".
593
594 <rdeCsv:fReDate> Date that transfer was requested with
595 type="dateTime" and isRequired="true".
596
597 <rdeCsv:fAcDate> Date that transfer action should be taken or has
598 been taken with type="dateTime" and isRequired="true".
599
600 <rdeCsv:fTrDate> Date of last transfer with type="dateTime".
601
602 <rdeCsv:fTrStatus> State of the most recent transfer request with
603 type="eppcom:trStatusType" and isRequired="true".
604
605 <rdeCsv:fTokenType> General token field with type="token".
606
607 <rdeCsv:fLang> General language field with type="language".
608
609 <rdeCsv:fIdnTableId> IDN table identifier used for IDN domain names
610 with type="token".
611
612 <rdeCsv:fPositiveIntegerType> General positive integer field with
613 type="positiveInteger".
614
615 <rdeCsv:fUrl> Contains the URL of an object like a registrar object
616 with type="anyURI".
617
618 <rdeCsv:fCustom> Custom field with name attribute that defines the
619 custom field name with type="token".
620
621 4.6.3. Internationalized and Localized Elements
622
623 Some elements MAY be provided in either internationalized form
624 ("int") or localized form ("loc"). Those elements use a field value
625 or "isLoc" attribute to specify the form used. If an "isLoc"
626 attribute is used, a value of "true" indicates the use of the
627 localized form, and a value of "false" indicates the use of the
628 internationalized form. This MAY override the form specified for a
629 parent element. A value of "int" is used to indicate the
630 internationalized form, and a value of "loc" is used to indicate the
631 localized form. When the internalized form ("int") is provided, the
632 field value MUST be represented in a subset of UTF-8 that can be
633 represented in the 7-bit US-ASCII character set. When the localized
634 form ("loc") is provided, the field value MAY be represented in
635 unrestricted UTF-8.
636
637 The field elements below of the "registrar" <rdeCsv:csv>
638 <rdeCsv:fields> element specify the internationalized form with the
639 isLoc="false" attribute.
640
641 ...
642 <csvRegistrar:contents>
643 ...
644 <rdeCsv:csv name="registrar" sep=",">
645 <rdeCsv:fields>
646 <csvRegistrar:fId/>
647 <rdeCsv:fRoid/>
648 <csvRegistrar:fName isLoc="false"/>
649 <csvRegistrar:fGurid/>
650 <csvRegistrar:fStatus/>
651 <csvContact:fStreet isLoc="false" index="0"/>
652 <csvContact:fStreet isLoc="false" index="1"/>
653 <csvContact:fStreet isLoc="false" index="2"/>
654 <csvContact:fCity isLoc="false" />
655 <csvContact:fSp isLoc="false" />
656 <csvContact:fPc isLoc="false" />
657 <csvContact:fCc isLoc="false" />
658 <csvContact:fVoice/>
659 <csvContact:fVoiceExt/>
660 <csvContact:fFax/>
661 <csvContact:fFaxExt/>
662 <csvContact:fEmail isRequired="false"/>
663 <rdeCsv:fUrl/>
664 <csvRegistrar:fWhoisUrl/>
665 <rdeCsv:fCrRr/>
666 <rdeCsv:fCrID/>
667 <rdeCsv:fCrDate/>
668 <rdeCsv:fUpRr/>
669 <rdeCsv:fUpID/>
670 <rdeCsv:fUpDate/>
671 </rdeCsv:fields>
672 <rdeCsv:files>
673 <rdeCsv:file
674 cksum="306178BB">
675 registrar-YYYYMMDD.csv
676 </rdeCsv:file>
677 </rdeCsv:files>
678 </rdeCsv:csv>
679 ...
680 </csvRegistrar:contents>
681 ...
682
683 The following is an example of using the <csvContact:fPostalType>
684 field value to define the internationalized or localized form of the
685 remainder of the "contactPostal" field values.
686
687 ...
688 <csvContact:contents>
689 ...
690 <rdeCsv:csv name="contactPostal">
691 <rdeCsv:fields>
692 <csvContact:fId parent="true"/>
693 <csvContact:fPostalType/>
694 <csvContact:fName/>
695 <csvContact:fOrg/>
696 <csvContact:fStreet index="0"/>
697 <csvContact:fStreet index="1"/>
698 <csvContact:fStreet index="2"/>
699 <csvContact:fCity/>
700 <csvContact:fSp/>
701 <csvContact:fPc/>
702 <csvContact:fCc/>
703 </rdeCsv:fields>
704 <rdeCsv:files>
705 <rdeCsv:file
706 cksum="02CC2504">
707 contactPostal-YYYYMMDD.csv
708 </rdeCsv:file>
709 </rdeCsv:files>
710 </rdeCsv:csv>
711 ...
712 </csvContact:contents>
713 ...
714
715 5. Object Description
716
717 This section describes the base objects supported by this
718 specification:
719
720 5.1. Domain Name Object
721
722 The domain name object is based on the EPP domain name mapping
723 specified in [RFC5731]. The domain name object supports both the XML
724 model and the CSV model, defined in 'Models' (Section 2). The
725 elements used for both models are defined in the following sections.
726
727 5.1.1. XML Model
728
729 There are two elements used in the data escrow of the domain name
730 objects for the XML model, including the <rdeDomain:domain> element,
731 under the <rde:contents> element, and the <rdeDomain:delete> element,
732 under the <rde:deletes> element.
733
734 5.1.1.1. <rdeDomain:domain> Object
735
736 The domain element is based on the EPP domain <info> response for an
737 authorized client (see Section 3.1.2 of [RFC5731]) with additional
738 data from an EPP <transfer> query response, see Section 3.1.3 of
739 [RFC5731], Registry Grace Period (RGP) status from [RFC3915], and
740 data from the EPP <secDNS:create> command, see Section 5.2.1 of
741 [RFC5910].
742
743 A <domain> element substitutes for the <abstractDomain> abstract
744 element to create a concrete definition of a domain. The
745 <abstractDomain> element can be replaced by other domain definitions
746 using the XML schema substitution groups feature.
747
748 The <domain> element contains the following child elements:
749
750 * A <name> element that contains the fully qualified name of the
751 domain name object. For IDNs, the A-label is used (see [RFC5891],
752 Section 4.4).
753
754 * A <roid> element that contains the ROID assigned to the domain
755 name object when it was created.
756
757 * An OPTIONAL <uName> element that contains the FQDN in the Unicode
758 character set. It MUST be provided if available.
759
760 * An OPTIONAL <idnTableId> element that references the IDN table
761 used for the IDN. This corresponds to the "id" attribute of the
762 <idnTableRef> element. This element MUST be present if the domain
763 name is an IDN.
764
765 * An OPTIONAL <originalName> element is used to indicate that the
766 domain name is an IDN variant. This element contains the domain
767 name used to generate the IDN variant.
768
769 * One or more <status> elements that contain the current status
770 descriptors associated with the domain name.
771
772 * Zero or more OPTIONAL <rgpStatus> elements to represent
773 "pendingDelete" sub-statuses, including "redemptionPeriod",
774 "pendingRestore", and "pendingDelete", that a domain name can be
775 in as a result of grace period processing as specified in
776 [RFC3915].
777
778 * An OPTIONAL <registrant> element that contains the identifier for
779 the human or the organizational social information object
780 associated with the holder of the domain name object.
781
782 * Zero or more OPTIONAL <contact> elements that contain identifiers
783 for the human or organizational social information objects
784 associated with the domain name object.
785
786 * An OPTIONAL <ns> element that contains the fully qualified names
787 of the delegated host objects or host attributes (name servers)
788 associated with the domain name object. See Section 1.1 of
789 [RFC5731] for a description of the elements used to specify host
790 objects or host attributes.
791
792 * A <clID> element that contains the identifier of the sponsoring
793 registrar.
794
795 * An OPTIONAL <crRr> element that contains the identifier of the
796 registrar that created the domain name object. An OPTIONAL
797 "client" attribute is used to specify the client that performed
798 the operation.
799
800 * An OPTIONAL <crDate> element that contains the date and time of
801 the domain name object creation. This element MUST be present if
802 the domain name has been allocated.
803
804 * An OPTIONAL <exDate> element that contains the date and time
805 identifying the end (expiration) of the domain name object's
806 registration period. This element MUST be present if the domain
807 name has been allocated.
808
809 * An OPTIONAL <upRr> element that contains the identifier of the
810 registrar that last updated the domain name object. This element
811 MUST NOT be present if the domain has never been modified. An
812 OPTIONAL "client" attribute is used to specify the client that
813 performed the operation.
814
815 * An OPTIONAL <upDate> element that contains the date and time of
816 the most recent modification of the domain name object. This
817 element MUST NOT be present if the domain name object has never
818 been modified.
819
820 * An OPTIONAL <secDNS> element that contains the public key
821 information associated with Domain Name System security (DNSSEC)
822 extensions for the domain name as specified in [RFC5910].
823
824 * An OPTIONAL <trDate> element that contains the date and time of
825 the most recent successful transfer of a domain name object. This
826 element MUST NOT be present if the domain name object has never
827 been transferred.
828
829 * An OPTIONAL <trnData> element that contains the following child
830 elements related to the last transfer request of the domain name
831 object. This element MUST NOT be present if a transfer request
832 for the domain name has never been created.
833
834 - A <trStatus> element that contains the state of the most recent
835 transfer request.
836
837 - A <reRr> element that contains the identifier of the registrar
838 that requested the domain name object transfer. An OPTIONAL
839 "client" attribute is used to specify the client that performed
840 the operation.
841
842 - A <reDate> element that contains the date and time that the
843 transfer was requested.
844
845 - An <acRr> element that contains the identifier of the registrar
846 that should act upon a pending transfer request. For all other
847 status types, the value identifies the registrar that took the
848 indicated action. An OPTIONAL "client" attribute is used to
849 specify the client that performed the operation.
850
851 - An <acDate> element that contains the date and time of a
852 required or completed response. For a pending request, the
853 value identifies the date and time by which a response is
854 required before an automated response action will be taken by
855 the registry. For all other status types, the value identifies
856 the date and time when the request was completed.
857
858 - An OPTIONAL <exDate> element that contains the end of the
859 domain name object's validity period (expiry date) if the
860 transfer caused or causes a change in the validity period.
861
862 The following is an example of a domain name object:
863
864 ...
865 <rdeDomain:domain>
866 <rdeDomain:name>xn--exampl-gva.example</rdeDomain:name>
867 <rdeDomain:roid>Dexample1-TEST</rdeDomain:roid>
868 <rdeDomain:idnTableId>pt-BR</rdeDomain:idnTableId>
869 <rdeDomain:originalName>example.example</rdeDomain:originalName>
870 <rdeDomain:status s="ok"/>
871 <rdeDomain:registrant>jd1234</rdeDomain:registrant>
872 <rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
873 <rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
874 <rdeDomain:ns>
875 <domain:hostObj>ns1.example.com</domain:hostObj>
876 <domain:hostObj>ns1.example1.example</domain:hostObj>
877 </rdeDomain:ns>
878 <rdeDomain:clID>RegistrarX</rdeDomain:clID>
879 <rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr>
880 <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
881 <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate>
882 </rdeDomain:domain>
883 ...
884
885 5.1.1.2. <rdeDomain:delete> Object
886
887 The <rdeDomain:delete> element contains the FQDN that was deleted and
888 purged.
889
890 The following is an example of an <rdeDomain:delete> object:
891
892 ...
893 <rde:deletes>
894 ...
895 <rdeDomain:delete>
896 <rdeDomain:name>foo.example</rdeDomain:name>
897 <rdeDomain:name>bar.example</rdeDomain:name>
898 </rdeDomain:delete>
899 ...
900 </rde:deletes>
901 ...
902
903 5.1.2. CSV Model
904
905 For the CSV model of the domain name object, the <csvDomain:contents>
906 child element of the <rde:contents> element is used to hold the new
907 or updated domain name objects for the deposit. The
908 <csvDomain:deletes> child element of the <rde:deletes> element is
909 used to hold the deleted or purged domain name objects for the
910 deposit. Both the <csvDomain:contents> and <csvDomain:deletes>
911 elements contain one or more <rdeCsv:csv> elements with a set of
912 named CSV file definitions using the <rdeCsv:csv> "name" attribute.
913
914 Differential and Incremental Deposits are based on changes to the
915 domain name objects. The updated domain name object data under the
916 <csvDomain:contents> element is a cascade replace down all of the
917 domain name CSV files starting with the parent '"domain" CSV File
918 Definition' (Section 5.1.2.1.1). The child CSV file definitions
919 include a <csvDomain:fName parent="true"> field. All the child CSV
920 file definition data for the domain name objects in the parent
921 '"domain" CSV File Definition' (Section 5.1.2.1.1) MUST first be
922 deleted and then set using the data in the child CSV files. The
923 deleted domain name object data under the <csvDomain:deletes> element
924 is a cascade delete starting from the '"domain" Deletes CSV File
925 Definition' (Section 5.1.2.2.1).
926
927 5.1.2.1. <csvDomain:contents>
928
929 The <csvDomain:contents> is used to hold the new or updated domain
930 name object information for the deposit. The <csvDomain:contents> is
931 split into separate CSV file definitions using named <rdeCsv:csv>
932 elements with the "name" attribute. The following sections include
933 the supported domain name CSV file definitions.
934
935 5.1.2.1.1. "domain" CSV File Definition
936
937 The "domain" CSV File Definition defines the fields and CSV file
938 references used for the parent domain name object records. All the
939 other domain name CSV file definitions are child CSV files based on
940 the inclusion of the <csvDomain:fName parent="true"> field.
941
942 The following "csvDomain" field elements MUST be used in the "domain"
943 <rdeCsv:csv> <rdeCsv:fields> element:
944
945 <csvDomain:fName> Domain name field with type="eppcom:labelType" and
946 isRequired="true".
947
948 The following "csvDomain" field elements MAY be used in the "domain"
949 <rdeCsv:csv> <rdeCsv:fields> element:
950
951 <csvDomain:fOriginalName> Fully qualified name of the original IDN
952 domain name object related to the variant domain name object with
953 type="eppcom:labelType".
954
955 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the
956 "domain" <rdeCsv:csv> <rdeCsv:fields> element:
957
958 <rdeCsv:fRoid> ROID for the domain name object with
959 isRequired="true".
960
961 <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of the following:
962
963 <rdeCsv:fClID> Identifier of the sponsoring client with
964 isRequired="true".
965
966 <csvRegistrar:fGurid> Contains the Globally Unique Registrar
967 Identifier (GURID) assigned by ICANN with
968 type="positiveInteger" and isRequired="true".
969
970 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
971 (Section 4.6.2.2), MAY be used in the "domain" <rdeCsv:csv>
972 <rdeCsv:fields> element:
973
974 <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
975 of the client that created the domain name object.
976
977 <rdeCsv:fCrID> Identifier of the client that created the domain name
978 object.
979
980 <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
981 of the client that last updated the domain name object.
982
983 <rdeCsv:fUpID> Identifier of the client that last updated the domain
984 name object.
985
986 <rdeCsv:fUName> UTF-8 encoded domain name for the <csvDomain:fName>
987 field element.
988
989 <rdeCsv:fIdnTableId> IDN table identifier used for the IDN domain
990 name object that MUST match an <rdeCsv:fIdnTableId> field element
991 in the "idnLanguage" CSV files, as defined in Section 5.5.2.
992
993 <rdeCsv:fRegistrant> Registrant contact identifier for the domain
994 name object.
995
996 <rdeCsv:fCrDate> Date and time of the domain name object creation.
997
998 <rdeCsv:fUpDate> Date and time of the last update to the domain name
999 object. This field MUST NOT be set if the domain name object has
1000 never been modified.
1001
1002 <rdeCsv:fExDate> Expiration date and time for the domain name
1003 object.
1004
1005 <rdeCsv:fTrDate> Date and time of the last transfer for the domain
1006 name object. This field MUST NOT be set if the domain name object
1007 has never been transferred.
1008
1009 The following is an example of a "domain" <csvDomain:contents>
1010 <rdeCsv:csv> element.
1011
1012 ...
1013 <csvDomain:contents>
1014 ...
1015 <rdeCsv:csv name="domain">
1016 <rdeCsv:fields>
1017 <csvDomain:fName/>
1018 <rdeCsv:fRoid/>
1019 <rdeCsv:fIdnTableId/>
1020 <csvDomain:fOriginalName/>
1021 <rdeCsv:fRegistrant/>
1022 <rdeCsv:fClID/>
1023 <rdeCsv:fCrRr/>
1024 <rdeCsv:fCrID/>
1025 <rdeCsv:fCrDate/>
1026 <rdeCsv:fUpRr/>
1027 <rdeCsv:fUpID/>
1028 <rdeCsv:fUpDate/>
1029 <rdeCsv:fExDate isRequired="true"/>
1030 </rdeCsv:fields>
1031 <rdeCsv:files>
1032 <rdeCsv:file
1033 cksum="5E403BD6">
1034 domain-YYYYMMDD.csv
1035 </rdeCsv:file>
1036 </rdeCsv:files>
1037 </rdeCsv:csv>
1038 ...
1039 </csvDomain:contents>
1040 ...
1041
1042 The following is an example of the corresponding domain-YYYYMMDD.csv
1043 file. The file contains four records (two active ASCII domains,
1044 original IDN with LANG-1 language rules, and variant IDN with LANG-1
1045 language rules).
1046
1047 domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX,
1048 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
1049 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
1050 domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX,
1051 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY,
1052 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
1053 xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX,
1054 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
1055 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
1056 xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example,
1057 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z,
1058 registrarX,clientY,2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
1059
1060 5.1.2.1.2. "domainContacts" CSV File Definition
1061
1062 The "domainContacts" CSV File Definition defines the fields and CSV
1063 file references used for the domain name object link records to
1064 contact objects, as described in 'Contact Object' (Section 5.3).
1065
1066 The following "csvDomain" field elements, defined for the '"domain"
1067 CSV File Definition' (Section 5.1.2.1.1), MUST be used in the
1068 "domainContacts" <rdeCsv:csv> <rdeCsv:fields> element:
1069
1070 <csvDomain:fName> The name of the domain object that is linked to
1071 the contact object with isRequired="true".
1072
1073 <csvDomain:fContactType> The contact type for the contact object
1074 link with type="domain:contactAttrType" and isRequired="true".
1075 The supported contact type values include "admin" for the
1076 administration contact, "billing" for the billing contact, and
1077 "tech" for the technical contact.
1078
1079 The following "csvContact" fields, defined for the '"contact" CSV
1080 File Definition' (Section 5.3.2.1.1), MUST be used in the
1081 "domainContacts" <rdeCsv:csv> <rdeCsv:fields> element:
1082
1083 <csvContact:fId> The server-unique contact identifier with
1084 isRequired="true".
1085
1086 The following is an example of a "domainContacts"
1087 <csvDomain:contents> <rdeCsv:csv> element:
1088
1089 ...
1090 <csvDomain:contents>
1091 ...
1092 <rdeCsv:csv name="domainContacts">
1093 <rdeCsv:fields>
1094 <csvDomain:fName parent="true"/>
1095 <csvContact:fId/>
1096 <csvDomain:fContactType/>
1097 </rdeCsv:fields>
1098 <rdeCsv:files>
1099 <rdeCsv:file
1100 cksum="6B976A6C">
1101 domainContacts-YYYYMMDD.csv
1102 </rdeCsv:file>
1103 </rdeCsv:files>
1104 </rdeCsv:csv>
1105 ...
1106 </csvDomain:contents>
1107 ...
1108
1109 The following is an example of the corresponding domainContacts-
1110 YYYYMMDD.csv file. The file contains an admin, tech, and billing
1111 contact for the four domain names domain1.example, domain2.example,
1112 xn--bc123-3ve.example, and xn--bc321-3ve.example:
1113
1114 domain1.example,domain1admin,admin
1115 domain1.example,domain1tech,tech
1116 domain1.example,domain1billing,billing
1117 domain2.example,domain2admin,admin
1118 domain2.example,domain2tech,tech
1119 domain2.example,domain2billing,billing
1120 xn--bc123-3ve.example,xnabc123admin,admin
1121 xn--bc123-3ve.example,xnabc123tech,tech
1122 xn--bc123-3ve.example,xnabc123billing,billing
1123 xn--bc321-3ve.example,xnabc123admin,admin
1124 xn--bc321-3ve.example,xnabc123tech,tech
1125 xn--bc321-3ve.example,xnabc123billing,billing
1126
1127 5.1.2.1.3. "domainStatuses" CSV File Definition
1128
1129 The "domainStatuses" CSV File Definition defines the fields and CSV
1130 file references used for the domain name object statuses.
1131
1132 The following "csvDomain" fields, defined for the '"domain" CSV File
1133 Definition' (Section 5.1.2.1.1), MUST be used in the "domainStatuses"
1134 <rdeCsv:csv> <rdeCsv:fields> element:
1135
1136 <csvDomain:fName> Domain name of status with isRequired="true".
1137
1138 <csvDomain:fStatus> The status of the domain name with
1139 type="domain:statusValueType" and isRequired="true".
1140
1141 <csvDomain:fRgpStatus> The RGP status, as a sub-status of the
1142 <csvDomain:fStatus> "pendingDelete" status value, with
1143 type="rgp:statusValueType" as defined in [RFC3915].
1144
1145 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
1146 (Section 4.6.2.2), MAY be used in the "domainStatuses" <rdeCsv:csv>
1147 <rdeCsv:fields> element:
1148
1149 <rdeCsv:fStatusDescription> Domain name object status description,
1150 which is free-form text describing the rationale for the status.
1151
1152 <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
1153
1154 The following is an example of a "domainStatuses"
1155 <csvDomain:contents> <rdeCsv:csv> element:
1156
1157 ...
1158 <csvDomain:contents>
1159 ...
1160 <rdeCsv:csv name="domainStatuses">
1161 <rdeCsv:fields>
1162 <csvDomain:fName parent="true"/>
1163 <csvDomain:fStatus/>
1164 <rdeCsv:fStatusDescription/>
1165 <rdeCsv:fLang/>
1166 <csvDomain:fRgpStatus/>
1167 </rdeCsv:fields>
1168 <rdeCsv:files>
1169 <rdeCsv:file
1170 cksum="98D139A3">
1171 domainStatuses-YYYYMMDD.csv
1172 </rdeCsv:file>
1173 </rdeCsv:files>
1174 </rdeCsv:csv>
1175 ...
1176 </csvDomain:contents>
1177 ...
1178
1179 The following is an example of the corresponding domainStatuses-
1180 YYYYMMDD.csv file. The file contains the statuses for the four
1181 domain names domain1.example, domain2.example, xn--bc123-3ve.example,
1182 and xn--bc321-3ve.example:
1183
1184 domain1.example,clientUpdateProhibited,"Disallow update",
1185 en,
1186 domain1.example,clientDeleteProhibited,"Disallow delete",
1187 en,
1188 domain2.example,ok,,,
1189 xn--bc123-3ve.example,ok,,,
1190 xn--bc321-3ve.example,ok,,,
1191
1192 5.1.2.1.4. "domainNameServers" CSV File Definition
1193
1194 The "domainNameServers" CSV File Definition defines the fields and
1195 CSV file references used for the domain name delegated hosts (name
1196 servers). The "domainNameServers" CSV files define the relationship
1197 between a domain name object and a delegated host. The
1198 "domainNameServers" CSV File is used to support the <domain:hostObj>
1199 model, defined in [RFC5731].
1200
1201 The following "csvDomain" fields, defined for the '"domain" CSV File
1202 Definition' (Section 5.1.2.1.1), MUST be used in the
1203 "domainNameServers" <rdeCsv:csv> <rdeCsv:fields> element:
1204
1205 <csvDomain:fName> Domain name using the delegated host with
1206 isRequired="true".
1207
1208 The following "csvHost" and "rdeCsv" field elements MUST be used in
1209 the "domainNameServers" <rdeCsv:csv> <rdeCsv:fields> element:
1210
1211 <csvHost:fName> or <rdeCsv:fRoid> A choice of the following:
1212
1213 <csvHost:fName> Host name field with type="eppcom:labelType" and
1214 isRequired="true".
1215
1216 <rdeCsv:fRoid> Host object ROID assigned to the host object with
1217 isRequired="true".
1218
1219 The following is an example of a "domainNameServers"
1220 <csvDomain:contents> <rdeCsv:csv> element:
1221
1222 ...
1223 <csvDomain:contents>
1224 ...
1225 <rdeCsv:csv name="domainNameServers">
1226 <rdeCsv:fields>
1227 <csvDomain:fName parent="true"/>
1228 <rdeCsv:fRoid/>
1229 </rdeCsv:fields>
1230 <rdeCsv:files>
1231 <rdeCsv:file
1232 cksum="8FE6E9E1">
1233 domainNameServers-YYYYMMDD.csv
1234 </rdeCsv:file>
1235 </rdeCsv:files>
1236 </rdeCsv:csv>
1237 ...
1238 </csvDomain:contents>
1239 ...
1240
1241 The following is an example of the corresponding domainNameServers-
1242 YYYYMMDD.csv file. The file contains the delegated hosts (name
1243 servers) for the four domain names domain1.example, domain2.example,
1244 xn--bc123-3ve.example, and xn--bc321-3ve.example referenced via the
1245 <rdeCsv:fRoid> field element:
1246
1247 domain1.example,Hns1_domain1_test-TEST
1248 domain1.example,Hns2_domain1_test-TEST
1249 domain2.example,Hns1_domain2_test-TEST
1250 domain2.example,Hns2_domain2_test-TEST
1251 xn--bc123-3ve.example,Hns1_example_test-TEST
1252 xn--bc123-3ve.example,Hns2_example_test-TEST
1253 xn--bc321-3ve.example,Hns1_example_test-TEST
1254 xn--bc321-3ve.example,Hns2_example_test-TEST
1255
1256 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition
1257
1258 The "domainNameServersAddresses" CSV File Definition defines the
1259 fields and CSV file references used for supporting the domain host
1260 attributes model.
1261
1262 The following "csvDomain" fields, defined for the '"domain" CSV File
1263 Definition' (Section 5.1.2.1.1), MUST be used in the
1264 "domainNameServersAddresses" <rdeCsv:csv> <rdeCsv:fields> element:
1265
1266 <csvDomain:fName> Domain name using the delegated host with host
1267 <csvHost:fName> and isRequired="true".
1268
1269 The following "rdeCsv" fields, defined in 'CSV Model'
1270 (Section 5.2.2), MUST be used in the "domainNameServersAddresses"
1271 <rdeCsv:csv> <rdeCsv:fields> element:
1272
1273 <csvHost:fName> Host name field with type="eppcom:labelType" and
1274 isRequired="true".
1275
1276 The following "csvHost" fields, defined in 'CSV Model'
1277 (Section 5.2.2), MAY be used in the "domainNameServersAddresses"
1278 <rdeCsv:csv> <rdeCsv:fields> element:
1279
1280 <csvHost:fAddr> IP addresses associated with the host object with
1281 type="host:addrStringType".
1282
1283 <csvHost:fAddrVersion> IP addresses version associated with the host
1284 object with type="host:ipType". "host:ipType" has the enumerated
1285 values of "v4" or "v6".
1286
1287 The following is an example of a "domainNameServersAddresses"
1288 <csvDomain:contents> <rdeCsv:csv> element:
1289
1290 ...
1291 <csvDomain:contents>
1292 ...
1293 <rdeCsv:csv name="domainNameServersAddresses">
1294 <rdeCsv:fields>
1295 <csvDomain:fName parent="true"/>
1296 <csvHost:fName/>
1297 <csvHost:fAddr/>
1298 <csvHost:fAddrVersion/>
1299 </rdeCsv:fields>
1300 <rdeCsv:files>
1301 <rdeCsv:file
1302 cksum="D3B77438">
1303 domainNameServersAddresses-YYYYMMDD.csv
1304 </rdeCsv:file>
1305 </rdeCsv:files>
1306 </rdeCsv:csv>
1307 ...
1308 </csvDomain:contents>
1309 ...
1310
1311 The following is an example of the corresponding
1312 domainNameServersAddresses-YYYYMMDD.csv file. The file contains the
1313 delegated hosts (name servers) for the four domain names
1314 domain1.example, domain2.example, xn--bc123-3ve.example, and xn--
1315 bc321-3ve.example:
1316
1317 domain1.example,ns1.domain1.example,192.0.2.1,v4
1318 domain1.example,ns2.domain1.example,2001:DB8::1,v6
1319 domain2.example,ns1.example.net,,
1320 domain2.example,ns2.example.net,,
1321 xn--bc123-3ve.example,ns1.example.net,,
1322 xn--bc123-3ve.example,ns2.example.net,,
1323 xn--bc321-3ve.example,ns1.example.net,,
1324 xn--bc321-3ve.example,ns2.example.net,,
1325
1326 5.1.2.1.6. "dnssec" CSV File Definition
1327
1328 The "dnssec" CSV File Definition defines the fields and CSV file
1329 references used for the domain name object DNSSEC records (Delegation
1330 Signer (DS) or key data).
1331
1332 The following "csvDomain" field elements MUST be used in the "dnssec"
1333 <rdeCsv:csv> <rdeCsv:fields> element when the DS Data Interface per
1334 [RFC5910] is used:
1335
1336 <csvDomain:fKeyTag> Contains the DS key tag value per [RFC5910] with
1337 type="unsignedShort" and isRequired="true".
1338
1339 <csvDomain:fDsAlg> Contains the DS algorithm value per [RFC5910]
1340 with type="unsignedByte" and isRequired="true".
1341
1342 <csvDomain:fDigestType> Contains the DS digest type value per
1343 [RFC5910] with type="unsignedByte" and isRequired="true".
1344
1345 <csvDomain:fDigest> Contains the DS digest value per [RFC5910] with
1346 type="hexBinary" and isRequired="true".
1347
1348 The following "csvDomain" field elements MUST be used in the "dnssec"
1349 <rdeCsv:csv> <rdeCsv:fields> element when the Key Data Interface per
1350 [RFC5910] is used and MAY be used in the "dnssec" <rdeCsv:csv>
1351 <rdeCsv:fields> element when the DS Data Interface per [RFC5910] is
1352 used:
1353
1354 <csvDomain:fFlags> Contains the flags field value per [RFC5910] with
1355 type="unsignedShort" and isRequired="true".
1356
1357 <csvDomain:fProtocol> Contains the key protocol value per [RFC5910]
1358 with type="unsignedByte" and isRequired="true".
1359
1360 <csvDomain:fKeyAlg> Contains the key algorithm value per [RFC5910]
1361 with type="unsignedByte" and isRequired="true".
1362
1363 <csvDomain:fPubKey> Contains the public key value per [RFC5910] with
1364 type="secDNS:keyType" and isRequired="true".
1365
1366 The following "csvDomain" field elements MAY be used in the "dnssec"
1367 <rdeCsv:csv> <rdeCsv:fields> element:
1368
1369 <csvDomain:fMaxSigLife> Indicates a child's preference for the
1370 number of seconds after signature generation when the parent's
1371 signature on the DS information provided by the child will expire
1372 with type="secDNS:maxSigLifeType" defined in [RFC5910].
1373
1374 The following "domain" fields, defined for the '"domain" CSV File
1375 Definition' (Section 5.1.2.1.1), MUST be used in the "dnssec"
1376 <rdeCsv:csv> <rdeCsv:fields> element:
1377
1378 <csvDomain:fName> Domain name of the domain name object associated
1379 with the DNSSEC record and isRequired="true".
1380
1381 The following is an example of a "dnssec" <csvDomain:contents>
1382 <rdeCsv:csv> element with the DS Data Interface of [RFC5910]:
1383
1384 <csvDomain:contents>
1385 ...
1386 <rdeCsv:csv name="dnssec">
1387 <rdeCsv:fields>
1388 <csvDomain:fName parent="true"/>
1389 <csvDomain:fMaxSigLife/>
1390 <csvDomain:fKeyTag/>
1391 <csvDomain:fDsAlg/>
1392 <csvDomain:fDigestType/>
1393 <csvDomain:fDigest/>
1394 </rdeCsv:fields>
1395 <rdeCsv:files>
1396 <rdeCsv:file
1397 cksum="10ED6C42">
1398 dnssec-ds-YYYYMMDD.csv
1399 </rdeCsv:file>
1400 </rdeCsv:files>
1401 </rdeCsv:csv>
1402 ...
1403 </csvDomain:contents>
1404 ...
1405
1406 The following is an example of the corresponding dnssec-ds-
1407 YYYYMMDD.csv file. The file contains two DS records for
1408 domain1.example:
1409
1410 domain1.example,604800,30730,8,2,91C9B176EB////F1C46F6A55
1411 domain1.example,604800,61882,8,2,9F8FEAC94B////1272AF09F3
1412
1413 The following is an example of a "dnssec" <csvDomain:contents>
1414 <rdeCsv:csv> element with the Key Data Interface of [RFC5910]:
1415
1416 <csvDomain:contents>
1417 ...
1418 <rdeCsv:csv name="dnssec">
1419 <rdeCsv:fields>
1420 <csvDomain:fName parent="true"/>
1421 <csvDomain:fMaxSigLife/>
1422 <csvDomain:fFlags/>
1423 <csvDomain:fProtocol/>
1424 <csvDomain:fKeyAlg/>
1425 <csvDomain:fPubKey/>
1426 </rdeCsv:fields>
1427 <rdeCsv:files>
1428 <rdeCsv:file
1429 cksum="183C3F79">
1430 dnssec-key-YYYYMMDD.csv
1431 </rdeCsv:file>
1432 </rdeCsv:files>
1433 </rdeCsv:csv>
1434 ...
1435 </csvDomain:contents>
1436 ...
1437
1438 The following is an example of the corresponding dnssec-key-
1439 YYYYMMDD.csv file. The file contains two key records for
1440 domain1.example:
1441
1442 domain1.example,604800,257,3,8,AwEAAZD1+z////G1jqviK8c=
1443 domain1.example,604800,257,3,8,AwEAAbntWP////vwDitt940=
1444
1445 5.1.2.1.7. "domainTransfer" CSV File Definition
1446
1447 The "domainTransfer" CSV File Definition defines the fields and CSV
1448 file references used for the domain name object pending and completed
1449 transfer records. No additional field elements were added for use in
1450 the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element.
1451
1452 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
1453 (Section 4.6.2.2), MUST be used in the "domainTransfer" <rdeCsv:csv>
1454 <rdeCsv:fields> element:
1455
1456 <rdeCsv:fTrStatus> State of the most recent transfer request with
1457 isRequired="true".
1458
1459 <rdeCsv:fReRr> Identifier of the registrar, defined in Section 5.4,
1460 of the client that requested the transfer with isRequired="true".
1461
1462 <rdeCsv:fReDate> Date and time that the transfer was requested with
1463 isRequired="true".
1464
1465 <rdeCsv:fAcRr> Identifier of the registrar, defined in Section 5.4,
1466 of the client that should take or took action with
1467 isRequired="true".
1468
1469 <rdeCsv:fAcDate> Date and time that the transfer action should be
1470 taken or has been taken with isRequired="true".
1471
1472 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
1473 (Section 4.6.2.2), MAY be used in the "domainTransfer" <rdeCsv:csv>
1474 <rdeCsv:fields> element:
1475
1476 <rdeCsv:fExDate> Expiration date if the transfer command caused or
1477 causes a change in the validity period.
1478
1479 <rdeCsv:fReID> Identifier of the client that requested the transfer.
1480
1481 <rdeCsv:fAcID> Identifier of the client that should take or took
1482 action for transfer.
1483
1484 The following "csvDomain" fields, defined for the '"domain" CSV File
1485 Definition' (Section 5.1.2.1.1), MUST be used in the "domainTransfer"
1486 <rdeCsv:csv> <rdeCsv:fields> element:
1487
1488 <csvDomain:fName> Domain name of the domain name object involved in
1489 the transfer with isRequired="true".
1490
1491 The following is an example of a "domainTransfer"
1492 <csvDomain:contents> <rdeCsv:csv> element:
1493
1494 ...
1495 <csvDomain:contents>
1496 ...
1497 <rdeCsv:csv name="domainTransfer">
1498 <rdeCsv:fields>
1499 <csvDomain:fName parent="true"/>
1500 <rdeCsv:fTrStatus/>
1501 <rdeCsv:fReRr/>
1502 <rdeCsv:fReID/>
1503 <rdeCsv:fReDate/>
1504 <rdeCsv:fAcRr/>
1505 <rdeCsv:fAcID/>
1506 <rdeCsv:fAcDate/>
1507 <rdeCsv:fExDate/>
1508 </rdeCsv:fields>
1509 <rdeCsv:files>
1510 <rdeCsv:file
1511 cksum="2E5A9ACD">
1512 domainTransfer-YYYYMMDD.csv
1513 </rdeCsv:file>
1514 </rdeCsv:files>
1515 </rdeCsv:csv>
1516 ...
1517 </csvDomain:contents>
1518 ...
1519
1520 The following is an example of the corresponding domainTransfer-
1521 YYYYMMDD.csv file. The file contains one domain transfer record with
1522 a pending status:
1523
1524 domain1.example,pending,registrarX,clientY,
1525 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z,
1526 2025-04-03T22:00:00.0Z
1527
1528 5.1.2.2. <csvDomain:deletes>
1529
1530 The <csvDomain:deletes> is used to hold the deleted domain name
1531 objects in a Differential or Incremental Deposit. All the domain
1532 name object data is deleted as part of a cascade delete. The
1533 <csvDomain:deletes> is split into separate CSV file definitions using
1534 named <rdeCsv:csv> elements with the "name" attribute. The following
1535 section defines the supported domain name deletes CSV file
1536 definition.
1537
1538 5.1.2.2.1. "domain" Deletes CSV File Definition
1539
1540 The following "csvDomain" field elements MUST be used in the deletes
1541 "domain" <rdeCsv:csv> <rdeCsv:fields> element:
1542
1543 <csvDomain:fName> Domain name field with type="eppcom:labelType" and
1544 isRequired="true".
1545
1546 The following is an example of a "domain" <csvDomain:deletes>
1547 <rdeCsv:csv> element:
1548
1549 ...
1550 <csvDomain:deletes>
1551 ...
1552 <rdeCsv:csv name="domain">
1553 <rdeCsv:fields>
1554 <csvDomain:fName/>
1555 </rdeCsv:fields>
1556 <rdeCsv:files>
1557 <rdeCsv:file
1558 cksum="A06D8194">
1559 domain-delete-YYYYMMDD.csv
1560 </rdeCsv:file>
1561 </rdeCsv:files>
1562 </rdeCsv:csv>
1563 ...
1564 </csvDomain:deletes>
1565 ...
1566
1567 The following is an example of the corresponding domain-delete-
1568 YYYYMMDD.csv file. The file contains two domain name records:
1569
1570 domain1.example
1571 domain2.example
1572
1573 5.2. Host Object
1574
1575 The host object is based on the EPP host name mapping in [RFC5732].
1576 The host object supports both the XML model and the CSV model,
1577 defined in 'Models' (Section 2). The elements used for both models
1578 are defined in the following sections. Both the <csvHost:contents>
1579 and <csvHost:deletes> elements contain one or more <rdeCsv:csv>
1580 elements with a set of named CSV file definitions using the
1581 <rdeCsv:csv> "name" attribute.
1582
1583 5.2.1. XML Model
1584
1585 There are two elements used in the data escrow of the host objects
1586 for the XML model including the <rdeHost:host> element, under the
1587 <rdeHost:contents> element, and the <rdeHost:delete> element, under
1588 the <rde:deletes> element.
1589
1590 An <rdeHost:host> element substitutes for the <rdeHost:abstractHost>
1591 abstract element to create a concrete definition of a host. The
1592 <rdeHost:abstractHost> element can be replaced by other host
1593 definitions using the XML schema substitution groups feature.
1594
1595 5.2.1.1. <rdeHost:host> Element
1596
1597 The RDE host object is based on the EPP host <info> response for an
1598 authorized client (Section 3.1.2 of [RFC5732]).
1599
1600 The OPTIONAL <host> element contains the following child elements:
1601
1602 * A <name> element that contains the fully qualified name of the
1603 host object.
1604
1605 * A <roid> element that contains the ROID assigned to the host
1606 object when the object was created.
1607
1608 * One or more <status> elements that describe the status of the host
1609 object.
1610
1611 * Zero or more <addr> elements that contain the IP addresses
1612 associated with the host object.
1613
1614 * A <clID> element that contains the identifier of the sponsoring
1615 registrar.
1616
1617 * An OPTIONAL <crRr> element that contains the identifier of the
1618 registrar that created the host object. An OPTIONAL "client"
1619 attribute is used to specify the client that performed the
1620 operation.
1621
1622 * An OPTIONAL <crDate> element that contains the date and time of
1623 host object creation.
1624
1625 * An OPTIONAL <upRr> element that contains the identifier of the
1626 registrar that last updated the host object. This element MUST
1627 NOT be present if the host object has never been modified. An
1628 OPTIONAL "client" attribute is used to specify the client that
1629 performed the operation.
1630
1631 * An OPTIONAL <upDate> element that contains the date and time of
1632 the most recent host object modification. This element MUST NOT
1633 be present if the host object has never been modified.
1634
1635 * An OPTIONAL <trDate> element that contains the date and time of
1636 the most recent host object successful transfer. This element
1637 MUST NOT be present if the domain name object has never been
1638 transferred.
1639
1640 The following is an example of a <host> object:
1641
1642 ...
1643 <rdeHost:host>
1644 <rdeHost:name>ns1.example1.example</rdeHost:name>
1645 <rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid>
1646 <rdeHost:status s="ok"/>
1647 <rdeHost:status s="linked"/>
1648 <rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr>
1649 <rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr>
1650 <rdeHost:addr ip="v6">2001:DB8:1::1</rdeHost:addr>
1651 <rdeHost:clID>RegistrarX</rdeHost:clID>
1652 <rdeHost:crRr>RegistrarX</rdeHost:crRr>
1653 <rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate>
1654 <rdeHost:upRr>RegistrarX</rdeHost:upRr>
1655 <rdeHost:upDate>2009-10-03T09:34:00.0Z</rdeHost:upDate>
1656 </rdeHost:host>
1657 ...
1658
1659 5.2.1.2. <rdeHost:delete> Object
1660
1661 The <rdeHost:delete> element contains the FQDN of a host that was
1662 deleted. The <rdeHost:delete> element also supports host removal
1663 based on ROID to support SRS systems in which different hosts with
1664 the same FQDN are active at the same time.
1665
1666 The following is an example of an <rdeHost:delete> object:
1667
1668 ...
1669 <rde:deletes>
1670 ...
1671 <rdeHost:delete>
1672 <rdeHost:name>ns1.example.example</rdeHost:name>
1673 </rdeHost:delete>
1674 ...
1675 </rde:deletes>
1676 ...
1677
1678 5.2.2. CSV Model
1679
1680 For the CSV model of the host object, the <csvHost:contents> child
1681 element of the <rde:contents> element is used to hold the new or
1682 updated host objects for the deposit. The <csvHost:deletes> child
1683 element of the <rde:deletes> element is used to hold the deleted or
1684 purged host objects for the deposit.
1685
1686 Differential and Incremental Deposits are based on changes to the
1687 host objects. The updated host object data under the
1688 <csvHost:contents> element is a cascade replace down all of the host
1689 CSV files starting with the parent '"host" CSV File Definition'
1690 (Section 5.2.2.1.1). The child CSV file definitions include an
1691 <rdeCsv:fRoid parent="true"> field. All the child CSV file
1692 definition data for the host objects in the parent '"host" CSV File
1693 Definition' (Section 5.2.2.1.1) MUST first be deleted and then set
1694 using the data in the child CSV files. The deleted host object data
1695 under the <csvHost:deletes> element is a cascade delete starting from
1696 the '"host" Deletes CSV File Definition' (Section 5.2.2.2.1).
1697
1698 5.2.2.1. <csvHost:contents>
1699
1700 The <csvHost:contents> is used to hold the new or updated host object
1701 information for the deposit. The <csvHost:contents> is split into
1702 separate CSV file definitions using named <rdeCsv:csv> elements with
1703 the "name" attribute. The following sections include the supported
1704 host CSV file definitions.
1705
1706 5.2.2.1.1. "host" CSV File Definition
1707
1708 The "host" CSV File Definition defines the fields and CSV file
1709 references used for the host object records.
1710
1711 The following "csvHost" field elements MUST be used in the "host"
1712 <rdeCsv:csv> <rdeCsv:fields> element:
1713
1714 <csvHost:fName> Host name field with type="eppcom:labelType" and
1715 isRequired="true".
1716
1717 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
1718 (Section 4.6.2.2), MUST be used in the "host" <rdeCsv:csv>
1719 <rdeCsv:fields> element:
1720
1721 <rdeCsv:fRoid> ROID assigned to the host object with
1722 isRequired="true".
1723
1724 The following "rdeCsv" and "csvRegistrar" fields MAY be used in the
1725 "host" <rdeCsv:csv> <rdeCsv:fields> element:
1726
1727 <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of the following:
1728
1729 <rdeCsv:fClID> Identifier of the sponsoring client with
1730 isRequired="true".
1731
1732 <csvRegistrar:fGurid> Contains the GURID assigned by ICANN with
1733 type="positiveInteger" and isRequired="true".
1734
1735 <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
1736 of the client that created the host object.
1737
1738 <rdeCsv:fCrID> Identifier of the client that created the host
1739 object.
1740
1741 <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
1742 of the client that last updated the host object.
1743
1744 <rdeCsv:fUpID> Identifier of the client that last updated the host
1745 object.
1746
1747 <rdeCsv:fCrDate> Date and time that the host object was created.
1748
1749 <rdeCsv:fUpDate> Date and time that the host object was last
1750 updated. This field MUST NOT be set if the domain name object has
1751 never been modified.
1752
1753 <rdeCsv:fTrDate> Date and time that the host object was last
1754 transferred. This field MUST NOT be set if the domain name object
1755 has never been transferred.
1756
1757 The following is an example of a "host" <csvHost:contents>
1758 <rdeCsv:csv> element:
1759
1760 ...
1761 <csvHost:contents>
1762 ...
1763 <rdeCsv:csv name="host">
1764 <rdeCsv:fields>
1765 <csvHost:fName/>
1766 <rdeCsv:fRoid/>
1767 <rdeCsv:fClID/>
1768 <rdeCsv:fCrRr/>
1769 <rdeCsv:fCrID/>
1770 <rdeCsv:fCrDate/>
1771 <rdeCsv:fUpRr/>
1772 <rdeCsv:fUpID/>
1773 <rdeCsv:fUpDate/>
1774 <rdeCsv:fTrDate/>
1775 </rdeCsv:fields>
1776 <rdeCsv:files>
1777 <rdeCsv:file
1778 cksum="6F1E58E5">
1779 host-YYYYMMDD.csv
1780 </rdeCsv:file>
1781 </rdeCsv:files>
1782 </rdeCsv:csv>
1783 ...
1784 </csvHost:contents>
1785 ...
1786
1787 The following is an example of the corresponding host-YYYYMMDD.csv
1788 file. The file contains six host records with four being internal
1789 hosts and two being external hosts:
1790
1791 ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX,
1792 clientY,1999-05-08T12:10:00.0Z,registrarX,
1793 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
1794 ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX,
1795 clientY,1999-05-08T12:10:00.0Z,registrarX,
1796 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
1797 ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX,
1798 clientY,1999-05-08T12:10:00.0Z,registrarX,
1799 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
1800 ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX,
1801 clientY,1999-05-08T12:10:00.0Z,registrarX,
1802 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
1803 ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX,
1804 clientY,1999-05-08T12:10:00.0Z,registrarX,
1805 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
1806 ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX,
1807 clientY,1999-05-08T12:10:00.0Z,registrarX,
1808 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
1809
1810 5.2.2.1.2. "hostStatuses" CSV File Definition
1811
1812 The "hostStatuses" CSV File Definition defines the fields and CSV
1813 file references used for the host object statuses.
1814
1815 The following "csvHost" fields, defined for the '"host" CSV File
1816 Definition' (Section 5.2.2.1.1), MUST be used in the "hostStatuses"
1817 <rdeCsv:csv> <rdeCsv:fields> element:
1818
1819 <csvHost:fStatus> The status of the host with
1820 type="host:statusValueType" and isRequired="true".
1821
1822 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
1823 (Section 4.6.2.2), MUST be used in the "hostStatuses" <rdeCsv:csv>
1824 <rdeCsv:fields> element:
1825
1826 <rdeCsv:fRoid> Host object ROID assigned to the host object with
1827 isRequired="true".
1828
1829 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
1830 (Section 4.6.2.2), MAY be used in the "hostStatuses" <rdeCsv:csv>
1831 <rdeCsv:fields> element:
1832
1833 <rdeCsv:fStatusDescription> Host object status description, which is
1834 free-form text describing the rationale for the status.
1835
1836 <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
1837
1838 The following is an example of a "hostStatuses" <csvHost:contents>
1839 <rdeCsv:csv> element:
1840
1841 ...
1842 <csvHost:contents>
1843 ...
1844 <rdeCsv:csv name="hostStatuses">
1845 <rdeCsv:fields>
1846 <rdeCsv:fRoid parent="true"/>
1847 <csvHost:fStatus/>
1848 <rdeCsv:fStatusDescription/>
1849 <rdeCsv:fLang/>
1850 </rdeCsv:fields>
1851 <rdeCsv:files>
1852 <rdeCsv:file
1853 cksum="0DAE0583">
1854 hostStatuses-YYYYMMDD.csv
1855 </rdeCsv:file>
1856 </rdeCsv:files>
1857 </rdeCsv:csv>
1858 ...
1859 </csvHost:contents>
1860 ...
1861
1862 The following is an example of the corresponding hostStatuses-
1863 YYYYMMDD.csv file. The file contains the statuses for the six host
1864 names ns1.domain1.example, ns2.domain1.example, ns1.domain2.example,
1865 ns2.domain2.example, ns1.example.net, and ns2.example.net:
1866
1867 Hns1_domain1_test-TEST,ok,,
1868 Hns2_domain1_test-TEST,ok,,
1869 Hns1_domain2_test-TEST,ok,,
1870 Hns2_domain2_test-TEST,ok,,
1871 Hns1_example_test-TEST,ok,,
1872 Hns2_example_test-TEST,ok,,
1873
1874 5.2.2.1.3. "hostAddresses" CSV File Definition
1875
1876 The "hostAddresses" CSV File Definition defines the fields and CSV
1877 file references used for the host object IP addresses.
1878
1879 The following "csvHost" field elements MUST be used in the
1880 "hostAddresses" <rdeCsv:csv> <rdeCsv:fields> element:
1881
1882 <csvHost:fAddr> IP addresses associated with the host object with
1883 type="host:addrStringType". The attribute "isRequired" MUST equal
1884 "true".
1885
1886 <csvHost:fAddrVersion> IP addresses version associated with the host
1887 object with type="host:ipType". "host:ipType" has the enumerated
1888 values of "v4" or "v6". The attribute "isRequired" MUST equal
1889 "true".
1890
1891 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
1892 (Section 4.6.2.2), MUST be used in the "hostAddresses" <rdeCsv:csv>
1893 <rdeCsv:fields> element:
1894
1895 <rdeCsv:fRoid> Host object ROID assigned to the host object with
1896 isRequired="true".
1897
1898 The following is an example of a "hostAddresses" <csvHost:contents>
1899 <rdeCsv:csv> element:
1900
1901 ...
1902 <csvHost:contents>
1903 ...
1904 <rdeCsv:csv name="hostAddresses">
1905 <rdeCsv:fields>
1906 <rdeCsv:fRoid parent="true"/>
1907 <csvHost:fAddr isRequired="true"/>
1908 <csvHost:fAddrVersion isRequired="true"/>
1909 </rdeCsv:fields>
1910 <rdeCsv:files>
1911 <rdeCsv:file
1912 cksum="28B194B0">
1913 hostAddresses-YYYYMMDD.csv
1914 </rdeCsv:file>
1915 </rdeCsv:files>
1916 </rdeCsv:csv>
1917 ...
1918 </csvHost:contents>
1919 ...
1920
1921 The following is an example of the corresponding hostAddresses-
1922 YYYYMMDD.csv file. The file contains the IP addresses for the host
1923 names ns1.domain1.example, ns2.domain1.example, ns1.domain2.example,
1924 and ns2.domain2.example:
1925
1926 Hns1_domain1_test-TEST,192.0.2.1,v4
1927 Hns2_domain1_test-TEST,2001:DB8::1,v6
1928 Hns1_domain2_test-TEST,192.0.2.2,v4
1929 Hns2_domain2_test-TEST,2001:DB8::2,v6
1930
1931 5.2.2.2. <csvHost:deletes>
1932
1933 The <csvHost:deletes> is used to hold the deleted host objects in a
1934 Differential or Incremental Deposit. All the host object data is
1935 deleted as part of a cascade delete. The <csvHost:deletes> is split
1936 into separate CSV file definitions using named <rdeCsv:csv> elements
1937 with the "name" attribute. The following section defines the
1938 supported host deletes CSV file definition.
1939
1940 5.2.2.2.1. "host" Deletes CSV File Definition
1941
1942 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
1943 (Section 4.6.2.2), MUST be used in the "host" <rdeCsv:csv>
1944 <rdeCsv:fields> element:
1945
1946 <rdeCsv:fRoid> ROID assigned to the host object with
1947 isRequired="true".
1948
1949 The following is an example of a "host" <csvHost:deletes>
1950 <rdeCsv:csv> element:
1951
1952 ...
1953 <csvHost:deletes>
1954 ...
1955 <rdeCsv:csv name="host">
1956 <rdeCsv:fields>
1957 <rdeCsv:fRoid/>
1958 </rdeCsv:fields>
1959 <rdeCsv:files>
1960 <rdeCsv:file
1961 cksum="777F5F0E">
1962 host-delete-YYYYMMDD.csv
1963 </rdeCsv:file>
1964 </rdeCsv:files>
1965 </rdeCsv:csv>
1966 ...
1967 </csvHost:deletes>
1968 ...
1969
1970 The following is an example of the host-delete-YYYYMMDD.csv file.
1971 The file contains four host records:
1972
1973 Hns1_domain1_test-TEST
1974 Hns2_domain1_test-TEST
1975 Hns1_domain2_test-TEST
1976 Hns2_domain2_test-TEST
1977
1978 5.3. Contact Object
1979
1980 The contact object is based on the EPP contact name mapping in
1981 [RFC5733]. The contact object supports both the XML model and the
1982 CSV model, defined in 'Models' (Section 2). The elements used for
1983 both models are defined in the following sections.
1984
1985 5.3.1. XML Model
1986
1987 There are two elements used in the data escrow of the contact objects
1988 for the XML model including the <rdeContact:contact> element, under
1989 the <rdeContact:contents> element, and the <rdeContact:delete>
1990 element, under the <rde:deletes> element.
1991
1992 A <contact> element substitutes for the <abstractContact> abstract
1993 element to create a concrete definition of a contact. The
1994 <abstractContact> element can be replaced by other contact
1995 definitions using the XML schema substitution groups feature.
1996
1997 5.3.1.1. <rdeContact:contact> Object
1998
1999 The contact object is based on the EPP contact <info> response for an
2000 authorized client (Section 3.1.2 of [RFC5733]) with some additions
2001 including the data from an EPP <transfer> query response, see
2002 Section 3.1.3 of [RFC5733].
2003
2004 The OPTIONAL <contact> element contains the following child elements:
2005
2006 * A <id> element that contains the server-unique identifier of the
2007 contact object.
2008
2009 * A <roid> element that contains the ROID assigned to the contact
2010 object when the object was created.
2011
2012 * One or more <status> elements that describe the status of the
2013 contact object.
2014
2015 * One or two <postalInfo> elements that contain postal-address
2016 information. Two elements are provided so that address
2017 information can be provided in both internationalized and
2018 localized forms; a "type" attribute is used to identify the two
2019 forms. If an internationalized form (type="int") is provided,
2020 element content MUST be represented in a subset of UTF-8 that can
2021 be represented in the 7-bit US-ASCII character set. If a
2022 localized form (type="loc") is provided, element content MAY be
2023 represented in unrestricted UTF-8. The <postalInfo> element
2024 contains the following child elements:
2025
2026 - A <name> element that contains the name of the individual or
2027 role represented by the contact.
2028
2029 - An OPTIONAL <org> element that contains the name of the
2030 organization with which the contact is affiliated.
2031
2032 - An <addr> element that contains address information associated
2033 with the contact. An <addr> element contains the following
2034 child elements:
2035
2036 o One, two, or three OPTIONAL <street> elements that contain
2037 the contact's street address.
2038
2039 o A <city> element that contains the contact's city.
2040
2041 o An OPTIONAL <sp> element that contains the contact's state
2042 or province.
2043
2044 o An OPTIONAL <pc> element that contains the contact's postal
2045 code.
2046
2047 o A <cc> element that contains the contact's two-letter
2048 country code.
2049
2050 * An OPTIONAL <voice> element that contains the contact's voice
2051 telephone number.
2052
2053 * An OPTIONAL <fax> element that contains the contact's facsimile
2054 telephone number.
2055
2056 * An <email> element that contains the contact's email address.
2057
2058 * A <clID> element that contains the identifier of the sponsoring
2059 registrar.
2060
2061 * An OPTIONAL <crRr> element that contains the identifier of the
2062 registrar that created the contact object. An OPTIONAL "client"
2063 attribute is used to specify the client that performed the
2064 operation.
2065
2066 * An OPTIONAL <crDate> element that contains the date and time of
2067 contact object creation.
2068
2069 * An OPTIONAL <upRr> element that contains the identifier of the
2070 registrar that last updated the contact object. This element MUST
2071 NOT be present if the contact has never been modified. An
2072 OPTIONAL "client" attribute is used to specify the client that
2073 performed the operation.
2074
2075 * An OPTIONAL <upDate> element that contains the date and time of
2076 the most recent contact object modification. This element MUST
2077 NOT be present if the contact object has never been modified.
2078
2079 * An OPTIONAL <trDate> element that contains the date and time of
2080 the most recent contact object successful transfer. This element
2081 MUST NOT be present if the contact object has never been
2082 transferred.
2083
2084 * An OPTIONAL <trnData> element that contains the following child
2085 elements related to the last transfer request of the contact
2086 object:
2087
2088 - A <trStatus> element that contains the state of the most recent
2089 transfer request.
2090
2091 - An <reRr> element that contains the identifier of the registrar
2092 that requested the domain name object transfer. An OPTIONAL
2093 "client" attribute is used to specify the client that performed
2094 the operation.
2095
2096 - An <acRr> element that contains the identifier of the registrar
2097 that should act upon a pending transfer request. For all other
2098 status types, the value identifies the registrar that took the
2099 indicated action. An OPTIONAL "client" attribute is used to
2100 specify the client that performed the operation.
2101
2102 - An <reDate> element that contains the date and time that the
2103 transfer was requested.
2104
2105 - An <acDate> element that contains the date and time of a
2106 required or completed response. For a pending request, the
2107 value identifies the date and time by which a response is
2108 required before an automated response action will be taken by
2109 the registry. For all other status types, the value identifies
2110 the date and time when the request was completed.
2111
2112 * An OPTIONAL <disclose> element that identifies elements that
2113 requiring exceptional server-operator handling to allow or
2114 restrict disclosure to third parties. See Section 2.9 of
2115 [RFC5733] for a description of the child elements contained within
2116 the <disclose> element.
2117
2118 The following is an example of a <contact> object:
2119
2120 ...
2121 <rdeContact:contact>
2122 <rdeContact:id>sh8013</rdeContact:id>
2123 <rdeContact:roid>Csh8013-TEST</rdeContact:roid>
2124 <rdeContact:status s="linked"/>
2125 <rdeContact:status s="clientDeleteProhibited"/>
2126 <rdeContact:postalInfo type="int">
2127 <contact:name>John Doe</contact:name>
2128 <contact:org>Example Inc.</contact:org>
2129 <contact:addr>
2130 <contact:street>123 Example Dr.</contact:street>
2131 <contact:street>Suite 100</contact:street>
2132 <contact:city>Dulles</contact:city>
2133 <contact:sp>VA</contact:sp>
2134 <contact:pc>20166-6503</contact:pc>
2135 <contact:cc>US</contact:cc>
2136 </contact:addr>
2137 </rdeContact:postalInfo>
2138 <rdeContact:voice x="1234">+1.7035555555</rdeContact:voice>
2139 <rdeContact:fax>+1.7035555556</rdeContact:fax>
2140 <rdeContact:email>jdoe@example.example</rdeContact:email>
2141 <rdeContact:clID>RegistrarX</rdeContact:clID>
2142 <rdeContact:crRr client="jdoe">RegistrarX</rdeContact:crRr>
2143 <rdeContact:crDate>2009-09-13T08:01:00.0Z</rdeContact:crDate>
2144 <rdeContact:upRr client="jdoe">RegistrarX</rdeContact:upRr>
2145 <rdeContact:upDate>2009-11-26T09:10:00.0Z</rdeContact:upDate>
2146 <rdeContact:trDate>2009-12-03T09:05:00.0Z</rdeContact:trDate>
2147 <rdeContact:trnData>
2148 <rdeContact:trStatus>pending</rdeContact:trStatus>
2149 <rdeContact:reRr client="jstiles">clientW</rdeContact:reRr>
2150 <rdeContact:reDate>2011-03-08T19:38:00.0Z</rdeContact:reDate>
2151 <rdeContact:acRr client="rmiles">RegistrarX</rdeContact:acRr>
2152 <rdeContact:acDate>2011-03-13T23:59:59.0Z</rdeContact:acDate>
2153 </rdeContact:trnData>
2154 <rdeContact:disclose flag="0">
2155 <contact:voice/>
2156 <contact:email/>
2157 </rdeContact:disclose>
2158 </rdeContact:contact>
2159 ...
2160
2161 5.3.1.2. <rdeContact:delete> Object
2162
2163 The <rdeContact:delete> element contains the id of a contact that was
2164 deleted.
2165
2166 The following is an example of an <rdeContact:delete> object:
2167
2168 ...
2169 <rde:deletes>
2170 ...
2171 <rdeContact:delete>
2172 <rdeContact:id>sh8013-TEST</rdeContact:id>
2173 <rdeContact:id>co8013-TEST</rdeContact:id>
2174 </rdeContact:delete>
2175 ...
2176 </rde:deletes>
2177 ...
2178
2179 5.3.2. CSV Model
2180
2181 For the CSV model of the contact object, the <csvContact:contents>
2182 child element of the <rde:contents> element is used to hold the new
2183 or updated contacts objects for the deposit. The
2184 <csvContact:deletes> child element of the <rde:deletes> element is
2185 used to hold the deleted or purged contact objects for the deposit.
2186 Both the <csvContact:contents> and <csvContact:deletes> elements
2187 contain one or more <rdeCsv:csv> elements with a set of named CSV
2188 file definitions using the <rdeCsv:csv> "name" attribute.
2189
2190 Differential and Incremental Deposits are based on changes to the
2191 contact objects. The updated contact object data under the
2192 <csvContact:contents> element is a cascade replace down all of the
2193 contact CSV files starting with the parent '"contact" CSV File
2194 Definition' (Section 5.3.2.1.1). The child CSV file definitions
2195 include a <csvContact:fId parent="true"> field. All the child CSV
2196 file definition data for the contact objects in the parent '"contact"
2197 CSV File Definition' (Section 5.3.2.1.1) MUST first be deleted and
2198 then set using the data in the child CSV files. The deleted contact
2199 object data under the <csvContact:deletes> element is a cascade
2200 delete starting from the '"contact" Deletes CSV File Definition'
2201 (Section 5.3.2.2.1).
2202
2203 5.3.2.1. <csvContact:contents>
2204
2205 The <csvContact:contents> is used to hold the new or updated contact
2206 object information for the deposit. The <csvContact:contents> is
2207 split into separate CSV file definitions using named <rdeCsv:csv>
2208 elements with the "name" attribute. The following sections include
2209 the supported contact CSV file definitions.
2210
2211 5.3.2.1.1. "contact" CSV File Definition
2212
2213 The "contact" CSV File Definition defines the fields and CSV file
2214 references used for the contact object records.
2215
2216 The following "csvContact" field elements MUST be used in the
2217 "contact" <rdeCsv:csv> <rdeCsv:fields> element:
2218
2219 <csvContact:fId> Contains the server-unique contact identifier with
2220 type="eppcom:clIDType" and isRequired="true".
2221
2222 <csvContact:fEmail> Contains the contact's email address with
2223 type="eppcom:minTokenType" and isRequired="true".
2224
2225 The following field elements MAY be used in the "contact"
2226 <rdeCsv:csv> <rdeCsv:fields> element:
2227
2228 <csvContact:fVoice> Contains the contact's voice telephone number
2229 with type="contact:e164StringType".
2230
2231 <csvContact:fVoiceExt> Contains the contact's voice telephone number
2232 extension with type="token".
2233
2234 <csvContact:fFax> Contains the contact's facsimile telephone number
2235 with type="contact:e164StringType".
2236
2237 <csvContact:fFaxExt> Contains the contact's facsimile telephone
2238 number extension with type="token".
2239
2240 The following "rdeCsv" and "csvRegistrar" fields MUST be used in the
2241 "contact" <rdeCsv:csv> <rdeCsv:fields> element:
2242
2243 <rdeCsv:fRoid> The ROID for the contact object with
2244 isRequired="true".
2245
2246 <rdeCsv:fClID> or <csvRegistrar:fGurid> A choice of the following:
2247
2248 <rdeCsv:fClID> Identifier of the sponsoring client with
2249 isRequired="true".
2250
2251 <csvRegistrar:fGurid> Contains the GURID assigned by ICANN with
2252 type="positiveInteger" and isRequired="true".
2253
2254 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
2255 (Section 4.6.2.2), MAY be used in the "contact" <rdeCsv:csv>
2256 <rdeCsv:fields> element:
2257
2258 <rdeCsv:fCrRr> Identifier of the registrar, defined in Section 5.4,
2259 of the client that created the contact object.
2260
2261 <rdeCsv:fCrID> Identifier of the client that created the contact
2262 object.
2263
2264 <rdeCsv:fUpRr> Identifier of the registrar, defined in Section 5.4,
2265 of the client that last updated the contact object.
2266
2267 <rdeCsv:fUpID> Identifier of the client that last updated the
2268 contact object.
2269
2270 <rdeCsv:fCrDate> Date and time of the contact object creation.
2271
2272 <rdeCsv:fUpDate> Date and time of the last update to the contact
2273 object. This field MUST NOT be set if the domain name object has
2274 never been modified.
2275
2276 <rdeCsv:fTrDate> Date and time of the last transfer for the contact
2277 object. This field MUST NOT be set if the domain name object has
2278 never been transferred.
2279
2280 The following is an example of a "contact" <csvContact:contacts>
2281 <rdeCsv:csv> element:
2282
2283 ...
2284 <csvContact:contents>
2285 ...
2286 <rdeCsv:csv name="contact">
2287 <rdeCsv:fields>
2288 <csvContact:fId/>
2289 <rdeCsv:fRoid/>
2290 <csvContact:fVoice/>
2291 <csvContact:fVoiceExt/>
2292 <csvContact:fFax/>
2293 <csvContact:fFaxExt/>
2294 <csvContact:fEmail/>
2295 <rdeCsv:fClID/>
2296 <rdeCsv:fCrRr/>
2297 <rdeCsv:fCrID/>
2298 <rdeCsv:fCrDate/>
2299 <rdeCsv:fUpRr/>
2300 <rdeCsv:fUpID/>
2301 <rdeCsv:fUpDate/>
2302 </rdeCsv:fields>
2303 <rdeCsv:files>
2304 <rdeCsv:file
2305 cksum="8587AA49">
2306 contact-YYYYMMDD.csv
2307 </rdeCsv:file>
2308 </rdeCsv:files>
2309 </rdeCsv:csv>
2310 ...
2311 </csvContact:contents>
2312 ...
2313
2314 The following is an example of the contact-YYYYMMDD.csv file. The
2315 file contains nine object contact records:
2316
2317 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234,
2318 +1.7035555556,,jdoe@example.example,registrarX,registrarX,
2319 clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2320 2009-11-26T09:10:00.0Z
2321 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234,
2322 +1.7035555556,,jdoe@example.example,registrarX,registrarX,
2323 clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2324 2009-11-26T09:10:00.0Z
2325 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234,
2326 +1.7035555556,,jdoe@example.example,registrarX,registrarX,
2327 clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2328 2009-11-26T09:10:00.0Z
2329 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234,
2330 +1.7035555556,,jdoe@example.example,registrarX,registrarX,
2331 clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2332 2009-11-26T09:10:00.0Z
2333 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234,
2334 +1.7035555556,,jdoe@example.example,registrarX,registrarX,
2335 clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2336 2009-11-26T09:10:00.0Z
2337 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234,
2338 +1.7035555556,,jdoe@example.example,registrarX,registrarX,
2339 clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2340 2009-11-26T09:10:00.0Z
2341 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234,
2342 +1.7035555556,,jdoe@example.example,registrarX,registrarX,
2343 clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2344 2009-11-26T09:10:00.0Z
2345 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234,
2346 +1.7035555556,,jdoe@example.example,registrarX,registrarX,
2347 clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2348 2009-11-26T09:10:00.0Z
2349 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234,
2350 +1.7035555556,,jdoe@example.example,registrarX,registrarX,
2351 clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2352 2009-11-26T09:10:00.0Z
2353
2354 5.3.2.1.2. "contactStatuses" CSV File Definition
2355
2356 The "contactStatuses" CSV File Definition defines the fields and CSV
2357 file references used for the contact object statuses.
2358
2359 The following "csvContact" field elements, defined in the '"contact"
2360 CSV File Definition' (Section 5.3.2.1.1), MUST be used in the
2361 "contactStatuses" <rdeCsv:csv> <rdeCsv:fields> element:
2362
2363 <csvContact:fId> Server-unique contact identifier of status with
2364 isRequired="true" and parent="true".
2365
2366 <csvContact:fStatus> The status of the contact with
2367 type="contact:statusValueType" and isRequired="true".
2368
2369 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
2370 (Section 4.6.2.2), MAY be used in the "contactStatuses" <rdeCsv:csv>
2371 <rdeCsv:fields> element:
2372
2373 <rdeCsv:fStatusDescription> The contact object status description,
2374 which is free-form text describing the rationale for the status.
2375
2376 <rdeCsv:fLang> Language of the <rdeCsv:fStatusDescription> field.
2377
2378 The following is an example of a "contactStatuses"
2379 <csvContact:contents> <rdeCsv:csv> element:
2380
2381 ...
2382 <csvContact:contents>
2383 ...
2384 <rdeCsv:csv name="contactStatuses">
2385 <rdeCsv:fields>
2386 <csvContact:fId parent="true"/>
2387 <csvContact:fStatus/>
2388 <rdeCsv:fStatusDescription/>
2389 <rdeCsv:fLang/>
2390 </rdeCsv:fields>
2391 <rdeCsv:files>
2392 <rdeCsv:file
2393 cksum="137E13EC">
2394 contactStatuses-YYYYMMDD.csv
2395 </rdeCsv:file>
2396 </rdeCsv:files>
2397 </rdeCsv:csv>
2398 ...
2399 </csvContact:contents>
2400 ...
2401
2402 The following is an example of the corresponding contactStatuses-
2403 YYYYMMDD.csv file. The file contains the statuses for the nine
2404 contact identifiers:
2405
2406 domain1admin,ok,,
2407 domain1tech,ok,,
2408 domain1billing,ok,,
2409 domain2admin,ok,,
2410 domain2tech,ok,,
2411 domain2billing,ok,,
2412 xnabc123admin,ok,,
2413 xnabc123tech,ok,,
2414 xnabc123billing,ok,,
2415
2416 5.3.2.1.3. "contactPostal" CSV File Definition
2417
2418 The "contactPostal" CSV File Definition defines the fields and CSV
2419 file references used for the contact postal info object records.
2420
2421 The following "csvContact" field elements MUST be used in the
2422 "contactPostal" <rdeCsv:csv> <rdeCsv:fields> element:
2423
2424 <csvContact:fPostalType> Contains the form of the postal address
2425 information with type="contact:postalLineType" and
2426 isRequired="true". This field specifies the form ("int" or
2427 "loc"), as defined in Section 4.6.3, of the <csvContact:fName>,
2428 <csvContact:fOrg>, <csvContact:fStreet>, <csvContact:fCity>,
2429 <csvContact:fSp>, <csvContact:fPc>, and <csvContact:fCc> fields.
2430
2431 <csvContact:fName> Contains the contact's name of the individual or
2432 role represented by the contact with type="contact:postalLineType"
2433 and isRequired="true". An OPTIONAL "isLoc" attribute is used to
2434 indicate the localized or internationalized form as defined in
2435 Section 4.6.3.
2436
2437 <csvContact:fStreet> Contains the contact's street address line with
2438 type="contact:fPostalLineType". An "index" attribute is required
2439 to indicate which street address line the field represents with
2440 index="0" for the first line and incrementing for each line up to
2441 index="2" for the third line. An OPTIONAL "isLoc" attribute is
2442 used to indicate the localized or internationalized form as
2443 defined in Section 4.6.3.
2444
2445 <csvContact:fCity> Contains the contact's city with
2446 type="contact:postalLineType" and isRequired="true". An OPTIONAL
2447 "isLoc" attribute is used to indicate the localized or
2448 internationalized form as defined in Section 4.6.3.
2449
2450 <csvContact:fCc> Contains the contact's country code with
2451 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc"
2452 attribute is used to indicate the localized or internationalized
2453 form as defined in Section 4.6.3.
2454
2455 The following "csvContact" field elements MAY be used in the
2456 "contactPostal" <rdeCsv:csv> <rdeCsv:fields> element:
2457
2458 <csvContact:fOrg> Contains the name of the organization with which
2459 the contact is affiliated with type="contact:optPostalLineType".
2460 An OPTIONAL "isLoc" attribute is used to indicate the localized or
2461 internationalized form as defined in Section 4.6.3.
2462
2463 <csvContact:fSp> Contains the contact's state or province with
2464 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute
2465 is used to indicate the localized or internationalized form as
2466 defined in Section 4.6.3.
2467
2468 <csvContact:fPc> Contains the contact's postal code with
2469 type="contact:pcType". An OPTIONAL "isLoc" attribute is used to
2470 indicate the localized or internationalized form as defined in
2471 Section 4.6.3.
2472
2473 The following "csvContact" fields, defined in the '"contact" CSV File
2474 Definition' (Section 5.3.2.1.1), MUST be used in the "contactPostal"
2475 <rdeCsv:csv> <rdeCsv:fields> element:
2476
2477 <csvContact:fId> Server-unique contact identifier for the contact
2478 object with isRequired="true" and parent="true".
2479
2480 The following is an example of a "contactPostal"
2481 <csvContact:contents> <rdeCsv:csv> element:
2482
2483 ...
2484 <csvContact:contents>
2485 ...
2486 <rdeCsv:csv name="contactPostal">
2487 <rdeCsv:fields>
2488 <csvContact:fId parent="true"/>
2489 <csvContact:fPostalType/>
2490 <csvContact:fName/>
2491 <csvContact:fOrg/>
2492 <csvContact:fStreet index="0"/>
2493 <csvContact:fStreet index="1"/>
2494 <csvContact:fStreet index="2"/>
2495 <csvContact:fCity/>
2496 <csvContact:fSp/>
2497 <csvContact:fPc/>
2498 <csvContact:fCc/>
2499 </rdeCsv:fields>
2500 <rdeCsv:files>
2501 <rdeCsv:file
2502 cksum="1456A89C">
2503 contactPostal-YYYYMMDD.csv
2504 </rdeCsv:file>
2505 </rdeCsv:files>
2506 </rdeCsv:csv>
2507 ...
2508 </csvContact:contents>
2509 ...
2510
2511 The following is an example of the contactPostal-YYYYMMDD.csv file.
2512 The file contains nine contact postal records:
2513
2514 domain1admin,int,"John Doe","Example Inc.",
2515 "123 Example Dr.","Suite 100",,Reston,VA,20190,US
2516 domain1tech,int,"John Doe","Example Inc.",
2517 "123 Example Dr.","Suite 100",,Reston,VA,20190,US
2518 domain1billing,int,"John Doe","Example Inc.",
2519 "123 Example Dr.","Suite 100",,Reston,VA,20190,US
2520 domain2admin,int,"John Doe","Example Inc.",
2521 "123 Example Dr.","Suite 100",,Reston,VA,20190,US
2522 domain2tech,int,"John Doe","Example Inc.",
2523 "123 Example Dr.","Suite 100",,Reston,VA,20190,US
2524 domain2billing,int,"John Doe","Example Inc.",
2525 "123 Example Dr.","Suite 100",,Reston,VA,20190,US
2526 xnabc123admin,int,"John Doe","Example Inc.",
2527 "123 Example Dr.","Suite 100",,Reston,VA,20190,US
2528 xnabc123tech,int,"John Doe","Example Inc.",
2529 "123 Example Dr.","Suite 100",,Reston,VA,20190,US
2530 xnabc123billing,int,"John Doe","Example Inc.",
2531 "123 Example Dr.","Suite 100",,Reston,VA,20190,US
2532
2533 5.3.2.1.4. "contactTransfer" CSV File Definition
2534
2535 The "contactTransfer" CSV File Definition defines the fields and CSV
2536 file references used for the contact object pending and completed
2537 transfer records. No additional field elements were added for use in
2538 the "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element. The
2539 following "rdeCsv" fields, defined in 'CSV Common Field Elements'
2540 (Section 4.6.2.2), MUST be used in the "contactTransfer" <rdeCsv:csv>
2541 <rdeCsv:fields> element:
2542
2543 <rdeCsv:fTrStatus> State of the most recent transfer request with
2544 isRequired="true".
2545
2546 <rdeCsv:fReRr> Identifier of the registrar, defined in Section 5.4,
2547 of the client that requested the transfer with isRequired="true".
2548
2549 <rdeCsv:fReDate> Date and time that the transfer was requested with
2550 isRequired="true".
2551
2552 <rdeCsv:fAcRr> Identifier of the registrar, defined in Section 5.4,
2553 of the client that should take or took action with
2554 isRequired="true".
2555
2556 <rdeCsv:fAcDate> Date and time that the transfer action should be
2557 taken or has been taken with isRequired="true".
2558
2559 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
2560 (Section 4.6.2.2), MAY be used in the "contactTransfer" <rdeCsv:csv>
2561 <rdeCsv:fields> element:
2562
2563 <rdeCsv:fReID> Identifier of the client that requested the transfer.
2564
2565 <rdeCsv:fAcID> Identifier of the client that should take or took
2566 action for transfer.
2567
2568 The following "csvContact" fields, defined for the '"contact" CSV
2569 File Definition' (Section 5.3.2.1.1), MUST be used in the
2570 "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element:
2571
2572 <csvContact:fId> Server-unique contact identifier for the contact
2573 object with isRequired="true".
2574
2575 The following is an example of a "contactTransfer"
2576 <csvContact:contents> <rdeCsv:csv> element:
2577
2578 ...
2579 <csvContact:contents>
2580 ...
2581 <rdeCsv:csv name="contactTransfer">
2582 <rdeCsv:fields>
2583 <csvContact:fId parent="true"/>
2584 <rdeCsv:fTrStatus/>
2585 <rdeCsv:fReRr/>
2586 <rdeCsv:fReID/>
2587 <rdeCsv:fReDate/>
2588 <rdeCsv:fAcRr/>
2589 <rdeCsv:fAcID/>
2590 <rdeCsv:fAcDate/>
2591 </rdeCsv:fields>
2592 <rdeCsv:files>
2593 <rdeCsv:file
2594 cksum="788D308E">
2595 contactTransfer-YYYYMMDD.csv
2596 </rdeCsv:file>
2597 </rdeCsv:files>
2598 </rdeCsv:csv>
2599 ...
2600 </csvContact:contents>
2601 ...
2602
2603 The following is an example of the contactTransfer-YYYYMMDD.csv file.
2604 The file contains one contact transfer record in pending status:
2605
2606 xnabc123admin,clientApproved,registrarX,clientX,
2607 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z
2608
2609 5.3.2.1.5. "contactDisclose" CSV File Definition
2610
2611 The "contactDisclose" CSV File Definition defines the fields and CSV
2612 file references used for the contact disclose object records.
2613
2614 The following "csvContact" field elements MAY be used in the
2615 "contactDisclose" <rdeCsv:csv> <rdeCsv:fields> element:
2616
2617 <csvContact:fDiscloseFlag> Contains flag with a value of "true" or
2618 "1" (one) notes the preference to allow disclosure of the
2619 specified elements as an exception to the stated data-collection
2620 policy. A value of "false" or "0" (zero) notes a client
2621 preference to not allow disclosure of the specified elements as an
2622 exception to the stated data-collection policy with
2623 type="boolean". The additional fields define specific exceptional
2624 disclosure preferences based on the <csvContact:fDiscloseFlag>
2625 field.
2626
2627 <csvContact:fDiscloseNameLoc> Exceptional disclosure preference flag
2628 for the localized form of the contact name with type="boolean".
2629
2630 <csvContact:fDiscloseNameInt> Exceptional disclosure preference flag
2631 for the internationalized form of the contact name with
2632 type="boolean".
2633
2634 <csvContact:fDiscloseOrgLoc> Exceptional disclosure preference flag
2635 for the localized form of the contact organization with
2636 type="boolean".
2637
2638 <csvContact:fDiscloseOrgInt> Exceptional disclosure preference flag
2639 for the internationalized form of the contact organization with
2640 type="boolean".
2641
2642 <csvContact:fDiscloseAddrLoc> Exceptional disclosure preference flag
2643 for the localized form of the contact address with type="boolean".
2644
2645 <csvContact:fDiscloseAddrInt> Exceptional disclosure preference flag
2646 for the internationalized form of the contact address with
2647 type="boolean".
2648
2649 <csvContact:fDiscloseVoice> Exceptional disclosure preference flag
2650 of the contact voice telephone number with type="boolean".
2651
2652 <csvContact:fDiscloseFax> Exceptional disclosure preference flag of
2653 the contact facsimile telephone number with type="boolean".
2654
2655 <csvContact:fDiscloseEmail> Exceptional disclosure preference flag
2656 of the contact email address with type="boolean".
2657
2658 The following "csvContact" fields, defined for the '"contact" CSV
2659 File Definition' (Section 5.3.2.1.1), MUST be used in the
2660 "contactDisclose" <rdeCsv:csv> <rdeCsv:fields> element:
2661
2662 <csvContact:fId> Server-unique contact identifier for the contact
2663 object with isRequired="true".
2664
2665 The following is an example of a "contactDisclose"
2666 <csvContact:contents> <rdeCsv:csv> element:
2667
2668 ...
2669 <csvContact:contents>
2670 ...
2671 <rdeCsv:csv name="contactDisclose">
2672 <rdeCsv:fields>
2673 <csvContact:fId parent="true"/>
2674 <csvContact:fDiscloseFlag/>
2675 <csvContact:fDiscloseNameLoc/>
2676 <csvContact:fDiscloseNameInt/>
2677 <csvContact:fDiscloseOrgLoc/>
2678 <csvContact:fDiscloseOrgInt/>
2679 <csvContact:fDiscloseAddrLoc/>
2680 <csvContact:fDiscloseAddrInt/>
2681 <csvContact:fDiscloseVoice/>
2682 <csvContact:fDiscloseFax/>
2683 <csvContact:fDiscloseEmail/>
2684 </rdeCsv:fields>
2685 <rdeCsv:files>
2686 <rdeCsv:file
2687 cksum="1141EFD4">
2688 contactDisclose-YYYYMMDD.csv
2689 </rdeCsv:file>
2690 </rdeCsv:files>
2691 </rdeCsv:csv>
2692 ...
2693 </csvContact:contents>
2694 ...
2695
2696 The following is an example of the contactDisclose-YYYYMMDD.csv file.
2697 The file contains one disclosure records, disabling disclosure of
2698 voice, fax, and email:
2699
2700 xnabc123admin,0,0,0,0,0,0,0,1,1,1
2701
2702 5.3.2.2. <csvContact:deletes>
2703
2704 The <csvContact:deletes> is used to hold the deleted contact objects
2705 in a Differential or Incremental Deposit. All the contact object
2706 data is deleted as part of a cascade delete. The
2707 <csvContact:deletes> is split into separate CSV file definitions
2708 using named <rdeCsv:csv> elements with the "name" attribute. The
2709 following section defines the supported contact deletes CSV file
2710 definition.
2711
2712 5.3.2.2.1. "contact" Deletes CSV File Definition
2713
2714 The following "csvContact" field elements MUST be used in the deletes
2715 "contact" <rdeCsv:csv> <rdeCsv:fields> element:
2716
2717 <csvContact:fId> Contains the server-unique contact identifier with
2718 type="eppcom:clIDType" and isRequired="true".
2719
2720 The following is an example of a "contact" <csvContact:deletes>
2721 <rdeCsv:csv> element:
2722
2723 ...
2724 <csvContact:deletes>
2725 ...
2726 <rdeCsv:csv name="contact">
2727 <rdeCsv:fields>
2728 <csvContact:fId/>
2729 </rdeCsv:fields>
2730 <rdeCsv:files>
2731 <rdeCsv:file
2732 cksum="0C4B70DC">
2733 contact-delete-YYYYMMDD.csv
2734 </rdeCsv:file>
2735 </rdeCsv:files>
2736 </rdeCsv:csv>
2737 ...
2738 </csvContact:deletes>
2739 ...
2740
2741 The following is an example of the contact-delete-YYYYMMDD.csv file.
2742 The file contains six contact records:
2743
2744 domain1admin
2745 domain1tech
2746 domain1billing
2747 domain2admin
2748 domain2tech
2749 domain2billing
2750
2751 5.4. Registrar Object
2752
2753 The registrar object represents the sponsoring client for other
2754 objects and is typically referred to as the sponsoring registrar.
2755 The registrar object supports both the XML model and the CSV model,
2756 defined in Section 2. The elements used for both models are defined
2757 in the following sections.
2758
2759 5.4.1. XML Model
2760
2761 There are two elements used in the data escrow of the registrar
2762 objects for the XML model including the <rdeRegistrar:registrar>
2763 element, under the <rdeRegistrar:contents> element, and the
2764 <rdeRegistrar:delete> element, under the <rde:deletes> element.
2765
2766 An <rdeRegistrar:registrar> element substitutes for the
2767 <rdeRegistrar:abstractRegistrar> abstract element to create a
2768 concrete definition of a registrar. The
2769 <rdeRegistrar:abstractRegistrar> element can be replaced by other
2770 domain definitions using the XML schema substitution groups feature.
2771
2772 5.4.1.1. <rdeRegistrar:registrar> Element
2773
2774 The <registrar> element contains the following child elements:
2775
2776 * An <id> element that contains the registry-unique identifier of
2777 the registrar object. This <id> has a superordinate relationship
2778 to a subordinate <clID>, <crRr>, or <upRr> of domain, contact, and
2779 host objects.
2780
2781 * An <name> element that contains the name of the registrar.
2782
2783 * An OPTIONAL <gurid> element that contains the GURID assigned by
2784 ICANN.
2785
2786 * An OPTIONAL <status> element that contains the operational status
2787 of the registrar. Possible values are: ok, readonly, and
2788 terminated.
2789
2790 * One or two OPTIONAL <postalInfo> elements that contain postal
2791 address information. Two elements are provided so that address
2792 information can be provided in both internationalized and
2793 localized forms; a "type" attribute is used to identify the two
2794 forms. If an internationalized form (type="int") is provided,
2795 element content MUST be represented in a subset of UTF-8 that can
2796 be represented in the 7-bit US-ASCII character set. If a
2797 localized form (type="loc") is provided, element content MAY be
2798 represented in unrestricted UTF-8. The <postalInfo> element
2799 contains the following child elements:
2800
2801 - A <addr> element that contains address information associated
2802 with the registrar. The <addr> element contains the following
2803 child elements:
2804
2805 o One, two, or three OPTIONAL <street> elements that contain
2806 the registrar's street address.
2807
2808 o A <city> element that contains the registrar's city.
2809
2810 o An OPTIONAL <sp> element that contains the registrar's state
2811 or province.
2812
2813 o An OPTIONAL <pc> element that contains the registrar's
2814 postal code.
2815
2816 o A <cc> element that contains the registrar's country code.
2817
2818 * An OPTIONAL <voice> element that contains the registrar's voice
2819 telephone number.
2820
2821 * An OPTIONAL <fax> element that contains the registrar's facsimile
2822 telephone number.
2823
2824 * An OPTIONAL <email> element that contains the registrar's email
2825 address.
2826
2827 * An OPTIONAL <url> element that contains the registrar's URL.
2828
2829 * An OPTIONAL <whoisInfo> element that contains WHOIS information.
2830 The <whoisInfo> element contains the following child elements:
2831
2832 - An OPTIONAL <name> element that contains the name of the
2833 registrar WHOIS server listening on TCP port 43 as specified in
2834 [RFC3912].
2835
2836 - An OPTIONAL <url> element that contains the name of the
2837 registrar WHOIS server listening on TCP port 80/443.
2838
2839 * An OPTIONAL <crDate> element that contains the creation date and
2840 time of the registrar object.
2841
2842 * An OPTIONAL <upDate> element that contains the date and time of
2843 the most recent modification of the registrar object. This
2844 element MUST NOT be present if the registrar object has never been
2845 modified.
2846
2847 The following is an example of a <registrar> object:
2848
2849 ...
2850 <rdeRegistrar:registrar>
2851 <rdeRegistrar:id>RegistrarX</rdeRegistrar:id>
2852 <rdeRegistrar:name>Registrar X</rdeRegistrar:name>
2853 <rdeRegistrar:gurid>8</rdeRegistrar:gurid>
2854 <rdeRegistrar:status>ok</rdeRegistrar:status>
2855 <rdeRegistrar:postalInfo type="int">
2856 <rdeRegistrar:addr>
2857 <rdeRegistrar:street>123 Example Dr.</rdeRegistrar:street>
2858 <rdeRegistrar:street>Suite 100</rdeRegistrar:street>
2859 <rdeRegistrar:city>Dulles</rdeRegistrar:city>
2860 <rdeRegistrar:sp>VA</rdeRegistrar:sp>
2861 <rdeRegistrar:pc>20166-6503</rdeRegistrar:pc>
2862 <rdeRegistrar:cc>US</rdeRegistrar:cc>
2863 </rdeRegistrar:addr>
2864 </rdeRegistrar:postalInfo>
2865 <rdeRegistrar:voice x="1234">+1.7035555555</rdeRegistrar:voice>
2866 <rdeRegistrar:fax>+1.7035555556</rdeRegistrar:fax>
2867 <rdeRegistrar:email>jdoe@example.example</rdeRegistrar:email>
2868 <rdeRegistrar:url>http://www.example.example</rdeRegistrar:url>
2869 <rdeRegistrar:whoisInfo>
2870 <rdeRegistrar:name>whois.example.example</rdeRegistrar:name>
2871 <rdeRegistrar:url>http://whois.example.example</rdeRegistrar:url>
2872 </rdeRegistrar:whoisInfo>
2873 <rdeRegistrar:crDate>2005-04-23T11:49:00.0Z</rdeRegistrar:crDate>
2874 <rdeRegistrar:upDate>2009-02-17T17:51:00.0Z</rdeRegistrar:upDate>
2875 </rdeRegistrar:registrar>
2876 ...
2877
2878 5.4.1.2. <rdeRegistrar:delete> Object
2879
2880 The <rdeRegistrar:delete> element contains the id of a registrar that
2881 was deleted.
2882
2883 The following is an example of <rdeRegistrar:delete> object:
2884
2885 ...
2886 <rde:deletes>
2887 ...
2888 <rdeRegistrar:delete>
2889 <rdeRegistrar:id>agnt0001-TEST</rdeRegistrar:id>
2890 </rdeRegistrar:delete>
2891 ...
2892 </rde:deletes>
2893 ...
2894
2895 5.4.2. CSV Model
2896
2897 For the CSV model of the registrar object, the
2898 <csvRegistrar:contents> child element of the <rde:contents> element
2899 is used to hold the new or updated registrar objects for the deposit.
2900 The <csvRegistrar:deletes> child element of the <rde:deletes> element
2901 is used to hold the deleted or purged registrar objects for the
2902 deposit. Both the <csvRegistrar:contents> and <csvRegistrar:deletes>
2903 elements contain one or more <rdeCsv:csv> elements with a set of
2904 named CSV file definitions using the <rdeCsv:csv> "name" attribute.
2905
2906 Differential and Incremental Deposits are based on changes to the
2907 registrar objects. The updated registrar object data under the
2908 <csvContact:contents> element is a cascade replace down all of the
2909 registrar CSV files starting with the parent '"registrar" CSV File
2910 Definition' (Section 5.4.2.1.1). The child CSV file definitions
2911 include a <csvRegistrar:fId parent="true"> field. All the child CSV
2912 file definition data for the registrar objects in the parent
2913 '"registrar" CSV File Definition' (Section 5.4.2.1.1) MUST first be
2914 deleted and then set using the data in the child CSV files. The
2915 deleted registrar object data under the <csvRegistrar:deletes>
2916 element is a cascade delete starting from the '"registrar" Deletes
2917 CSV File Definition' (Section 5.4.2.2.1).
2918
2919 5.4.2.1. <csvRegistrar:contents>
2920
2921 The <csvRegistrar:contents> is used to hold the new or updated
2922 registrar object information for the deposit. The
2923 <csvRegistrar:contents> is split into separate CSV file definitions
2924 using named <rdeCsv:csv> elements with the "name" attribute. The
2925 following sections include the supported registrar CSV file
2926 definitions.
2927
2928 5.4.2.1.1. "registrar" CSV File Definition
2929
2930 The "registrar" CSV File Definition defines the fields and CSV file
2931 references used for the registrar object records.
2932
2933 The following "csvRegistrar" field elements MUST be used in the
2934 "registrar" <rdeCsv:csv> <rdeCsv:fields> element:
2935
2936 <csvRegistrar:fId> or <csvRegistrar:fGurid> A choice of the
2937 following:
2938
2939 <csvRegistrar:fId> Contains the server-unique registrar
2940 identifier with type="eppcom:clIDType" and isRequired="true".
2941
2942 <csvRegistrar:fGurid> Contains the GURID assigned by ICANN with
2943 type="positiveInteger" and isRequired="true".
2944
2945 <csvRegistrar:fName> Contains the name of the registrar with
2946 type="normalizedString" and isRequired="true".
2947
2948 The following field elements MAY be used in the "registrar"
2949 <rdeCsv:csv> <rdeCsv:fields> element:
2950
2951 <csvRegistrar:fStatus> Contains the status of the registrar with
2952 type="csvRegistrar:statusValueType".
2953
2954 <csvRegistrar:fGurid> Contains the ID assigned by ICANN with
2955 type="positiveInteger". This field is included in this section in
2956 addition to the section above to support optionally providing the
2957 <csvRegistrar:fGurid> field when the <csvRegistrar:fId> field is
2958 used.
2959
2960 <csvRegistrar:fWhoisUrl> Contains the Whois URL of the registrar
2961 with type="anyURI".
2962
2963 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
2964 (Section 4.6.2.2), MAY be used in the "registrar" <rdeCsv:csv>
2965 <rdeCsv:fields> element:
2966
2967 <rdeCsv:fCrDate> Date and time of the registrar object creation.
2968
2969 <rdeCsv:fUpDate> Date and time of the last update to the registrar
2970 object. This field MUST NOT be set if the domain name object has
2971 never been modified.
2972
2973 <rdeCsv:fUrl> URL for the registrar web home page.
2974
2975 The following "csvContact" fields, defined in 'Contact Object'
2976 (Section 5.3), MAY be used in the "registrar" <rdeCsv:csv>
2977 <rdeCsv:fields> element:
2978
2979 <csvContact:fStreet> Registrar street address line with an "index"
2980 attribute that represents the order of the street address line
2981 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to
2982 indicate the localized or internationalized form, as defined in
2983 Section 4.6.3.
2984
2985 <csvContact:fCity> Registrar city with an OPTIONAL "isLoc" attribute
2986 that is used to indicate the localized or internationalized form,
2987 as defined in Section 4.6.3.
2988
2989 <csvContact:fCc> Registrar country code with an OPTIONAL "isLoc"
2990 attribute that is used to indicate the localized or
2991 internationalized form, as defined in Section 4.6.3.
2992
2993 <csvContact:fEmail> Registrar email address. The attribute
2994 "isRequired" MUST equal "false".
2995
2996 <csvContact:fSp> Registrar state or province with an OPTIONAL
2997 "isLoc" attribute that is used to indicate the localized or
2998 internationalized form, as defined in Section 4.6.3.
2999
3000 <csvContact:fPc> Registrar postal code with an OPTIONAL "isLoc"
3001 attribute that is used to indicate the localized or
3002 internationalized form, as defined in Section 4.6.3.
3003
3004 <csvContact:fVoice> Registrar voice telephone number.
3005
3006 <csvContact:fVoiceExt> Registrar voice telephone number extension.
3007
3008 <csvContact:fFax> Registrar facsimile telephone number.
3009
3010 <csvContact:fFaxExt> Registrar facsimile telephone number extension.
3011
3012 The following is an example of a "registrar" <csvRegistrar:contents>
3013 <rdeCsv:csv> element:
3014
3015 ...
3016 <csvRegistrar:contents>
3017 ...
3018 <rdeCsv:csv name="registrar">
3019 <rdeCsv:fields>
3020 <csvRegistrar:fId/>
3021 <csvRegistrar:fName isLoc="false"/>
3022 <csvRegistrar:fGurid/>
3023 <csvRegistrar:fStatus/>
3024 <csvContact:fStreet isLoc="false" index="0"/>
3025 <csvContact:fStreet isLoc="false" index="1"/>
3026 <csvContact:fStreet isLoc="false" index="2"/>
3027 <csvContact:fCity isLoc="false"/>
3028 <csvContact:fSp isLoc="false" />
3029 <csvContact:fPc isLoc="false" />
3030 <csvContact:fCc isLoc="false"/>
3031 <csvContact:fVoice/>
3032 <csvContact:fVoiceExt/>
3033 <csvContact:fFax/>
3034 <csvContact:fFaxExt/>
3035 <csvContact:fEmail isRequired="false"/>
3036 <rdeCsv:fUrl/>
3037 <csvRegistrar:fWhoisUrl/>
3038 <rdeCsv:fCrDate/>
3039 <rdeCsv:fUpDate/>
3040 </rdeCsv:fields>
3041 <rdeCsv:files>
3042 <rdeCsv:file
3043 cksum="57F6856F">
3044 registrar-YYYYMMDD.csv
3045 </rdeCsv:file>
3046 </rdeCsv:files>
3047 </rdeCsv:csv>
3048 ...
3049 </csvRegistrar:contents>
3050 ...
3051
3052 The following is an example of the registrar-YYYYMMDD.csv file. The
3053 file contains one registrar record:
3054
3055 registrarX,"Example Inc.",8,ok,"123 Example Dr.",
3056 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234,
3057 +1.7035555556,,jdoe@example.example,http://www.example.example,
3058 http://whois.example.example,2005-04-23T11:49:00.0Z,
3059 2009-02-17T17:51:00.0Z
3060
3061 5.4.2.2. <csvRegistrar:deletes>
3062
3063 The <csvRegistrar:deletes> is used to hold the deleted registrar
3064 objects in a Differential or Incremental Deposit. All the registrar
3065 object data is deleted as part of a cascade delete. The
3066 <csvRegistrar:deletes> is split into separate CSV file definitions
3067 using named <rdeCsv:csv> elements with the "name" attribute. The
3068 following section defines the supported registrar deletes CSV file
3069 definition.
3070
3071 5.4.2.2.1. "registrar" Deletes CSV File Definition
3072
3073 The following "csvRegistrar" field elements MUST be used in the
3074 deletes "registrar" <rdeCsv:csv> <rdeCsv:fields> element:
3075
3076 <csvRegistrar:fId> or <csvRegistrar:fGurid> A choice of the
3077 following:
3078
3079 <csvRegistrar:fId> Contains the server-unique registrar
3080 identifier with type="eppcom:clIDType" and isRequired="true".
3081
3082 <csvRegistrar:fGurid> Contains the GURID assigned by ICANN with
3083 type="positiveInteger". The attribute "isRequired" MUST equal
3084 "true".
3085
3086 The following is an example of a "registrar" <csvRegistrar:deletes>
3087 <rdeCsv:csv> element:
3088
3089 ...
3090 <csvRegistrar:deletes>
3091 ...
3092 <rdeCsv:csv name="registrar">
3093 <rdeCsv:fields>
3094 <csvRegistrar:fId/>
3095 </rdeCsv:fields>
3096 <rdeCsv:files>
3097 <rdeCsv:file
3098 cksum="5CB20A52">
3099 registrar-delete-YYYYMMDD.csv
3100 </rdeCsv:file>
3101 </rdeCsv:files>
3102 </rdeCsv:csv>
3103 ...
3104 </csvRegistrar:deletes>
3105 ...
3106
3107 The following is an example of the registrar-delete-YYYYMMDD.csv
3108 file. The file contains one registrar record:
3109
3110 registrarZ
3111
3112 5.5. IDN Table Reference Object
3113
3114 The Internationalized Domain Names (IDN) table reference object is a
3115 pseudo-object that is used to provide a short reference to the IDN
3116 table and policy used in IDN registrations. The IDN reference object
3117 supports both the XML and the CSV model, defined in 'Models'
3118 (Section 2). The elements used for both models are defined in the
3119 following sections.
3120
3121 5.5.1. XML Model
3122
3123 There is one element used in the data escrow of the IDN table
3124 reference objects for the XML model, and that is the
3125 <rdeIDN:idnTableRef>, under the <rde:contents> element.
3126
3127 5.5.1.1. <rdeIDN:idnTableRef> Object
3128
3129 The <rdeIDN:idnTableRef> contains the following elements. An "id"
3130 attribute is used to specify an identifier for the IDN table.
3131
3132 * A <url> element that contains the URL of the IDN table that is
3133 being referenced.
3134
3135 * A <urlPolicy> element that contains the URL of the IDN policy
3136 document. If IDN variants are generated algorithmically, the
3137 policy document MUST define the algorithm and the state of the
3138 implicitly generated IDN variants. For a list of suggested states
3139 for implicit IDN variants, please see [variantTLDsReport].
3140
3141 The following is an example of <idnTableRef> object:
3142
3143 ...
3144 <rdeIDN:idnTableRef id="pt-BR">
3145 <rdeIDN:url>
3146 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html
3147 </rdeIDN:url>
3148 <rdeIDN:urlPolicy>
3149 http://registro.br/dominio/regras.html
3150 </rdeIDN:urlPolicy>
3151 </rdeIDN:idnTableRef>
3152 ...
3153
3154 5.5.2. CSV Model
3155
3156 The IDN domain names, defined in Section 5.1, MAY have references to
3157 the IDN language identifier using the <rdeCsv:fIdnTableId> field
3158 element. The IDN table reference object defines the mapping of a
3159 language identifier to a language table URL. The language table URL
3160 defines the character code points that can be used for the language
3161 identifier. The elements used for the IDN table reference object are
3162 defined in this section. The <csvIDN:contents> child element of the
3163 <rde:contents> element is used to hold the new or updated IDN table
3164 reference objects for the deposit. The <csvIDN:deletes> child
3165 element of the <rde:deletes> element is used to hold the deleted or
3166 purged IDN table reference objects for the deposit. Both the
3167 <csvIDN:contents> and <csvIDN:deletes> elements contain one or more
3168 <rdeCsv:csv> elements with a set of named CSV file definitions using
3169 the <rdeCsv:csv> "name" attribute.
3170
3171 5.5.2.1. <csvIDN:contents>
3172
3173 The <csvIDN:contents> is used to hold the new or updated IDN table
3174 reference object information for the deposit. The <csvIDN:contents>
3175 is split into separate CSV file definitions using named <rdeCsv:csv>
3176 elements with the "name" attribute. The following sections include
3177 the supported IDN table reference CSV file definitions.
3178
3179 5.5.2.1.1. "idnLanguage" CSV File Definition
3180
3181 The "idnLanguage" CSV File Definition defines the fields and CSV file
3182 references used for the IDN table reference object records.
3183
3184 The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be
3185 used in the "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element:
3186
3187 <rdeCsv:fIdnTableId> The language identifier that matches the values
3188 for the <rdeCsv:fIdnTableId> field element in the '"domain" CSV
3189 File Definition' (Section 5.1.2.1.1) files. The attribute
3190 "isRequired" MUST equal "true".
3191
3192 <rdeCsv:fUrl> URL that defines the character code points that can be
3193 used for <csvDomain:fName> field in the '"domain" CSV File
3194 Definition' (Section 5.1.2.1.1) files. The attribute "isRequired"
3195 MUST equal "true".
3196
3197 The following is an example of a "idnLanguage" <csvIDN:contents>
3198 <rdeCsv:csv> element:
3199
3200 ...
3201 <csvIDN:contents>
3202 ...
3203 <rdeCsv:csv name="idnLanguage" sep=",">
3204 <rdeCsv:fields>
3205 <rdeCsv:fIdnTableId isRequired="true"/>
3206 <rdeCsv:fUrl isRequired="true"/>
3207 </rdeCsv:fields>
3208 <rdeCsv:files>
3209 <rdeCsv:file
3210 cksum="D6B0424F">
3211 idnLanguage-YYYYMMDD.csv
3212 </rdeCsv:file>
3213 </rdeCsv:files>
3214 </rdeCsv:csv>
3215 ...
3216 </csvIDN:contents>
3217 ...
3218
3219 The following is an example of the corresponding idnLanguage-
3220 YYYYMMDD.csv file. The file contains two IDN language records:
3221
3222 LANG-1,
3223 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt
3224 LANG-2,
3225 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt
3226
3227 5.5.2.2. <csvIDN:deletes>
3228
3229 The <csvIDN:deletes> is used to hold the deleted IDN table reference
3230 objects in a Differential or Incremental Deposit. The
3231 <csvIDN:deletes> is split into separate CSV file definitions using
3232 named <rdeCsv:csv> elements with the "name" attribute. The following
3233 section defines the supported IDN table reference deletes CSV file
3234 definition.
3235
3236 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition
3237
3238 The following "idnLanguage" field elements MUST be used in the
3239 deletes "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element:
3240
3241 <rdeCsv:fIdnTableId> The language identifier that matches the values
3242 for the <rdeCsv:fIdnTableId> field element in the '"domain" CSV
3243 File Definition' (Section 5.1.2.1.1) files. The attribute
3244 "isRequired" MUST equal "true".
3245
3246 The following is an example of a "idnLanguage" <csvIDN:deletes>
3247 <rdeCsv:csv> element:
3248
3249 ...
3250 <csvIDN:deletes>
3251 ...
3252 <rdeCsv:csv name="idnLanguage">
3253 <rdeCsv:fields>
3254 <rdeCsv:fIdnTableId isRequired="true"/>
3255 </rdeCsv:fields>
3256 <rdeCsv:files>
3257 <rdeCsv:file
3258 cksum="4A28A569">
3259 idnLanguage-delete-YYYYMMDD.csv
3260 </rdeCsv:file>
3261 </rdeCsv:files>
3262 </rdeCsv:csv>
3263 ...
3264 </csvIDN:deletes>
3265 ...
3266
3267 The following is an example of the idnLanguage-delete-YYYYMMDD.csv
3268 file. The file contains one IDN language record:
3269
3270 LANG-2
3271
3272 5.6. NNDN Object
3273
3274 An NNDN (NNDN's not domain name) can be used to store registry
3275 reserved names or (blocked, withheld, or mirrored) IDN variants.
3276
3277 Domain name registries may maintain domain names without their being
3278 persisted as domain objects in the registry system, for example, a
3279 list of reserved names not available for registration. The NNDN is a
3280 lightweight domain-like object that is used to escrow domain names
3281 not maintained as domain name objects.
3282
3283 A domain name can only exist as a domain name object or an NNDN
3284 object, but not both.
3285
3286 The NNDN object supports both the XML and the CSV model, defined in
3287 'Models' (Section 2). The elements used for both models are defined
3288 in the following sections.
3289
3290 5.6.1. XML Model
3291
3292 There are two elements used in the data escrow of the NNDN objects
3293 for the XML model including the <rdeNNDN:NNDN> element, under the
3294 <rde:contents> element, and the <rdeNNDN:delete> element, under the
3295 <rde:deletes> element.
3296
3297 An <rdeNNDN:NNDN> element substitutes for the <rdeNNDN:abstractNNDN>
3298 abstract element to create a concrete definition of an NNDN. The
3299 <rdeNNDN:abstractDomain> element can be replaced by other NNDN
3300 definitions using the XML schema substitution groups feature.
3301
3302 5.6.1.1. <rdeNNDN:NNDN> Object
3303
3304 The <rdeNNDN:NNDN> element contains the following child elements:
3305
3306 * An <aName> element that contains the fully qualified name of the
3307 NNDN. For IDNs, the A-label is used (see [RFC5891], Section 4.4).
3308
3309 * An OPTIONAL <uName> element that contains the fully qualified name
3310 of the NNDN in the Unicode character set. It MUST be provided if
3311 available.
3312
3313 * An OPTIONAL <idnTableId> element that references the IDN table
3314 used for the NNDN. This corresponds to the "id" attribute of the
3315 <idnTableRef> element. This element MUST be present if the NNDN
3316 is an IDN.
3317
3318 * An OPTIONAL <originalName> element is used to indicate that the
3319 NNDN is used for an IDN variant. This element contains the domain
3320 name used to generate the IDN variant.
3321
3322 * A <nameState> element that indicates the state of the NNDN:
3323 blocked, withheld, or mirrored.
3324
3325 - If an NNDN is considered undesirable for registration (i.e.,
3326 unavailable for allocation to anyone), then the NNDN will be
3327 tagged as "blocked".
3328
3329 - If an NNDN is considered a potential registration of a domain
3330 name object for a registrant, then the NNDN will be tagged as
3331 "withheld". This status is only used when the NNDN is used for
3332 an IDN variant.
3333
3334 - If an NNDN is considered a mirrored IDN variant of a domain
3335 name object, then the NNDN will be tagged as "mirrored". A
3336 "mirroringNS" attribute is used to specify if the mirrored IDN
3337 variant uses the NS mirror mechanism, meaning that the
3338 activated variant domain name (i.e., NNDN) is delegated in the
3339 DNS using the same NS records as in the <originalName>. The
3340 default value of "mirroringNS" is true. If another mechanism
3341 such as DNAME [RFC6672] is used, the value of the "mirroringNS"
3342 attribute MUST be false.
3343
3344 * An OPTIONAL <crDate> element that contains the date and time of
3345 the NNDN object creation.
3346
3347 The following is an example of an <rdeNNDN:NNDN> object:
3348
3349 ...
3350 <rdeNNDN:NNDN>
3351 <rdeNNDN:aName>xn--exampl-gva.example</rdeNNDN:aName>
3352 <rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId>
3353 <rdeNNDN:originalName>example.example</rdeNNDN:originalName>
3354 <rdeNNDN:nameState>withheld</rdeNNDN:nameState>
3355 <rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate>
3356 </rdeNNDN:NNDN>
3357 ...
3358
3359 5.6.1.2. <rdeNNDN:delete> Object
3360
3361 The <rdeNNDN:delete> element contains the NNDN that was deleted,
3362 i.e., the <aName>.
3363
3364 The following is an example of an <rdeNNDN::delete> object:
3365
3366 ...
3367 <rde:deletes>
3368 ...
3369 <rdeNNDN:delete>
3370 <rdeNNDN:aName>xn--pingino-q2a.example</rdeNNDN:aName>
3371 </rdeNNDN:delete>
3372 ...
3373 </rde:deletes>
3374 ...
3375
3376 5.6.2. CSV Model
3377
3378 For the CSV model of the NNDN object, the <csvNNDN:contents> child
3379 element of the <rde:contents> element is used to hold the new or
3380 updated NNDN objects for the deposit. The <csvNNDN:deletes> child
3381 element of the <rde:deletes> element is used to hold the deleted or
3382 purged NNDN objects for the deposit. Both the <csvNNDN:contents> and
3383 <csvNNDN:deletes> elements contain one or more <rdeCsv:csv> elements
3384 with a set of named CSV file definitions using the <rdeCsv:csv>
3385 "name" attribute.
3386
3387 5.6.2.1. <csvNNDN:contents>
3388
3389 The <csvNNDN:contents> is used to hold the new or updated NNDN object
3390 information for the deposit. The <csvNNDN:contents> is split into
3391 separate CSV file definitions using named <rdeCsv:csv> elements with
3392 the "name" attribute. The following sections include the supported
3393 NNDN CSV file definitions.
3394
3395 5.6.2.1.1. "NNDN" CSV File Definition
3396
3397 The "NNDN" CSV File Definition defines the fields and CSV file
3398 references used for the NNDN object records.
3399
3400 The following "csvNNDN" field elements MUST be used in the "NNDN"
3401 <rdeCsv:csv> <rdeCsv:fields> element:
3402
3403 <csvNNDN:fAName> Fully qualified name of the NNDN with
3404 type="eppcom:labelType" and isRequired="true". For IDNs, the
3405 A-label is used (see [RFC5891], Section 4.4).
3406
3407 <csvNNDN:fNameState> State of the NNDN: blocked or withheld with
3408 type="rdeNNDN:nameState" and isRequired="true". See
3409 Section 5.6.1.1 for a description of the possible values for the
3410 <rdeNNDN:nameState> element.
3411
3412 The following field elements MAY be used in the "NNDN" <rdeCsv:csv>
3413 <rdeCsv:fields> element:
3414
3415 <csvNNDN:fOriginalName> Domain name used to generate the IDN variant
3416 with type="eppcom:labelType".
3417
3418 <csvNNDN:fMirroringNS> Defines whether the "mirroring"
3419 <csvNNDN:fNameState> uses the NS mirror mechanism, as described
3420 for the <rdeNNDN:nameState> "mirroringNS" attribute in
3421 Section 5.6.1.1, with type="boolean". If the field element is not
3422 defined the default value is "true".
3423
3424 The following "rdeCsv" fields, defined in 'CSV Common Field Elements'
3425 (Section 4.6.2.2), MAY be used in the "NNDN" <rdeCsv:csv>
3426 <rdeCsv:fields> element:
3427
3428 <rdeCsv:fCrDate> Date and time of the NNDN object creation.
3429
3430 <rdeCsv:fUName> Name of the NNDN in the Unicode character set for
3431 the <csvNNDN:fAName> field element.
3432
3433 <rdeCsv:fIdnTableId> IDN table identifier for the NNDN that matches
3434 an IDN table reference object record, as defined in Section 5.5.2.
3435
3436 The following is an example of an "NNDN" <csvNNDN:contents>
3437 <rdeCsv:csv> element:
3438
3439 ...
3440 <csvNNDN:contents>
3441 ...
3442 <rdeCsv:csv name="NNDN" sep=",">
3443 <rdeCsv:fields>
3444 <csvNNDN:fAName/>
3445 <rdeCsv:fIdnTableId/>
3446 <csvNNDN:fOriginalName/>
3447 <csvNNDN:fNameState/>
3448 <csvNNDN:fMirroringNS/>
3449 <rdeCsv:fCrDate/>
3450 </rdeCsv:fields>
3451 <rdeCsv:files>
3452 <rdeCsv:file
3453 cksum="085A7CE4">
3454 NNDN-YYYYMMDD.csv
3455 </rdeCsv:file>
3456 </rdeCsv:files>
3457 </rdeCsv:csv>
3458 ...
3459 </csvNNDN:contents>
3460 ...
3461
3462 The following is an example of the corresponding NNDN-YYYYMMDD.csv
3463 file. The file contains two NNDN records for an IDN with one blocked
3464 variant and one mirrored variant:
3465
3466 xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example,
3467 blocked,,2005-04-23T11:49:00.0Z
3468 xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example,
3469 mirrored,1,2005-04-23T11:49:00.0Z
3470
3471 5.6.2.2. <csvNNDN:deletes>
3472
3473 The <csvNNDN:deletes> is used to hold the deleted NNDN objects in a
3474 Differential or Incremental Deposit. The <csvNNDN:deletes> is split
3475 into separate CSV file definitions using named <rdeCsv:csv> elements
3476 with the "name" attribute. The following section defines the
3477 supported NNDN deletes CSV file definition.
3478
3479 5.6.2.2.1. "NNDN" Deletes CSV File Definition
3480
3481 The following "NNDN" field elements MUST be used in the deletes
3482 "NNDN" <rdeCsv:csv> <rdeCsv:fields> element:
3483
3484 <csvNNDN:fAName> Fully qualified name of the NNDN with
3485 type="eppcom:labelType" and isRequired="true".
3486
3487 The following is an example of an "NNDN" <csvNNDN:deletes>
3488 <rdeCsv:csv> element:
3489
3490 ...
3491 <csvNNDN:deletes>
3492 ...
3493 <rdeCsv:csv name="NNDN">
3494 <rdeCsv:fields>
3495 <csvNNDN:fAName/>
3496 </rdeCsv:fields>
3497 <rdeCsv:files>
3498 <rdeCsv:file
3499 cksum="A41F1D9B">
3500 NNDN-delete-YYYYMMDD.csv
3501 </rdeCsv:file>
3502 </rdeCsv:files>
3503 </rdeCsv:csv>
3504 ...
3505 </csvNNDN:deletes>
3506 ...
3507
3508 The following is an example of the corresponding NNDN-delete-
3509 YYYYMMDD.csv file. The file contains one NNDN records:
3510
3511 xn--bc456-3ve.example
3512
3513 5.7. EPP Parameters Object
3514
3515 The EPP parameters object is a pseudo-object that defines the set of
3516 object and object extension services supported by the registry, as
3517 defined in [RFC5730]. The EPP parameters object is only defined as
3518 XML but could be used in either the XML model or CSV model. The EPP
3519 parameters object is defined using the <rdeEppParams:eppParams>
3520 element. The EPP parameters object SHOULD be included if the
3521 registry supports EPP. A maximum of one EPP parameters object MUST
3522 exist at a certain point in time (Time Watermark).
3523
3524 The syntax and content of the <rdeEppParams:eppParams> children
3525 elements is as explained in Section 2.4 of [RFC5730]. The children
3526 of the <eppParams> are as follows:
3527
3528 * One or more <version> elements that indicate the EPP versions
3529 supported by the registry.
3530
3531 * One or more <lang> elements that indicate the identifiers of the
3532 text response languages supported by the registry's EPP server.
3533
3534 * One or more <objURI> elements that contain namespace URIs
3535 representing the objects that the registry's EPP server is capable
3536 of managing.
3537
3538 * An OPTIONAL <svcExtension> element that contains one or more
3539 <extURI> elements that contain namespace URIs representing object
3540 extensions supported by the registry's EPP server.
3541
3542 * A <dcp> element that contains child elements used to describe the
3543 server's privacy policy for data collection and management. See
3544 Section 2.4 of [RFC5730] for more details.
3545
3546 The following is an example of <eppParams> element object:
3547
3548 ...
3549 <rdeEppParams:eppParams>
3550 <rdeEppParams:version>1.0</rdeEppParams:version>
3551 <rdeEppParams:lang>en</rdeEppParams:lang>
3552 <rdeEppParams:objURI>urn:ietf:params:xml:ns:domain-1.0
3553 </rdeEppParams:objURI>
3554 <rdeEppParams:objURI>urn:ietf:params:xml:ns:contact-1.0
3555 </rdeEppParams:objURI>
3556 <rdeEppParams:objURI>urn:ietf:params:xml:ns:host-1.0
3557 </rdeEppParams:objURI>
3558 <rdeEppParams:svcExtension>
3559 <epp:extURI>urn:ietf:params:xml:ns:rgp-1.0</epp:extURI>
3560 <epp:extURI>urn:ietf:params:xml:ns:secDNS-1.1</epp:extURI>
3561 </rdeEppParams:svcExtension>
3562 <rdeEppParams:dcp>
3563 <epp:access><epp:all/></epp:access>
3564 <epp:statement>
3565 <epp:purpose>
3566 <epp:admin/>
3567 <epp:prov/>
3568 </epp:purpose>
3569 <epp:recipient>
3570 <epp:ours/>
3571 <epp:public/>
3572 </epp:recipient>
3573 <epp:retention>
3574 <epp:stated/>
3575 </epp:retention>
3576 </epp:statement>
3577 </rdeEppParams:dcp>
3578 </rdeEppParams:eppParams>
3579 ...
3580
3581 5.8. Policy Object
3582
3583 The policy object is a pseudo-object that is used to specify which
3584 OPTIONAL elements from the XML model are REQUIRED based on the
3585 business model of the registry. For the CSV model, the OPTIONAL
3586 "isRequired" attribute of the <rdeCsv:field> elements, defined in
3587 Section 4.6.2.1, is used to specify which OPTIONAL fields are
3588 REQUIRED based on the business model of the registry.
3589
3590 5.8.1. <rdePolicy:policy> Object
3591
3592 The OPTIONAL <policy> contains the following attributes:
3593
3594 * An <element> that defines that the referenced <element> is
3595 REQUIRED.
3596
3597 * <scope> that defines the XPath (see [W3C.REC-xpath-31-20170321])
3598 of the element referenced by <element>.
3599
3600 The following is an example of <rdePolicy:policy> object:
3601
3602 ...
3603 <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain"
3604 element="rdeDomain:registrant" />
3605 ...
3606
3607 5.9. Header Object
3608
3609 The header object is a pseudo-object that is used to specify the
3610 number of objects in the repository at a specific point in time
3611 (Timeline Watermark) regardless of the type of deposit: Differential,
3612 Full, or Incremental Deposit. The header object may also be used to
3613 provide additional information on the contents of the deposit. The
3614 header object is only defined as XML but one header object MUST
3615 always be present per escrow deposit regardless of using the XML
3616 model or CSV model. The header object is defined using the
3617 <rdeHeader:header> element.
3618
3619 5.9.1. <rdeHeader:header> Object
3620
3621 The <rdeHeader:header> contains the following elements:
3622
3623 * A choice of one of the elements defined in the
3624 "repositoryTypeGroup" group element that indicates the unique
3625 identifier for the repository being escrowed. Possible elements
3626 are:
3627
3628 - An <rdeHeader:tld> element that defines TLD or the RCDN being
3629 escrowed in the case of a registry data escrow deposit. For
3630 IDNs, the A-label is used (see [RFC5891], Section 4.4).
3631
3632 - An <rdeHeader:registrar> element that defines the Registrar ID
3633 corresponding to a registrar data escrow deposit. In the case
3634 of an ICANN-accredited registrar, the <rdeHeader:registrar>
3635 element MUST be the IANA Registrar ID assigned by ICANN.
3636
3637 - An <rdeHeader:ppsp> element that defines the provider ID
3638 corresponding to a Privacy and Proxy Services Provider (PPSP)
3639 data escrow deposit. In the case of an ICANN-accredited PPSP,
3640 the <rdeHeader:ppsp> element MUST be the unique ID assigned by
3641 ICANN.
3642
3643 - An <rdeHeader:reseller> element that defines the provider ID
3644 corresponding to a reseller data escrow deposit.
3645
3646 * A <count> element that contains the number of objects in the SRS
3647 at a specific point in time (Timeline Watermark) regardless of the
3648 type of deposit: Differential, Full, or Incremental. The <count>
3649 element supports the following attributes:
3650
3651 - A "uri" attribute reflects the XML namespace URI of the primary
3652 objects for the XML model and CSV model. For example, the
3653 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for
3654 domain name objects using the XML model, and the "uri" is set
3655 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name
3656 objects using the CSV model.
3657
3658 - An OPTIONAL "rcdn" attribute indicates the RCDN of the objects
3659 included in the <count> element. For IDNs, the A-label is used
3660 [RFC5891], Section 4.4. If the "rcdn" attribute is present,
3661 the value of the <count> element must include only objects
3662 related to registrations in the same and lower levels. For
3663 example in a data escrow deposit for the .EXAMPLE TLD, a value
3664 of "example" in the "rcdn" attribute within the <count> element
3665 indicates the number of objects in the TLD including objects in
3666 other RCDNs within the TLD, whereas a value of "com.example"
3667 indicates the number of elements for objects under
3668 "com.example" and lower levels. Omitting the "rcdn" attribute
3669 indicates that the total includes all objects of the specified
3670 "uri" in the repository (e.g., the TLD, Registrar, or PPSP).
3671
3672 - An OPTIONAL "registrarId" attribute indicates the identifier of
3673 the sponsoring registrar of the objects included in the <count>
3674 element. In the case of an ICANN-accredited registrar, the
3675 value MUST be the IANA Registrar ID assigned by ICANN.
3676
3677 * An OPTIONAL <contentTag> element that contains a tag that defines
3678 the expected content in the deposit. The producer and consumer of
3679 the deposits will coordinate the set of possible <contentTag>
3680 element values.
3681
3682 The following is an example of <rdeHeader:header> object referencing
3683 only the XML model objects:
3684
3685 ...
3686 <rdeHeader:header>
3687 <rdeHeader:tld>test</rdeHeader:tld>
3688 <rdeHeader:count
3689 uri="urn:ietf:params:xml:ns:rdeDomain-1.0">2</rdeHeader:count>
3690 <rdeHeader:count
3691 uri="urn:ietf:params:xml:ns:rdeHost-1.0">1</rdeHeader:count>
3692 <rdeHeader:count
3693 uri="urn:ietf:params:xml:ns:rdeContact-1.0">1</rdeHeader:count>
3694 <rdeHeader:count
3695 uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1
3696 </rdeHeader:count>
3697 <rdeHeader:count
3698 uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1</rdeHeader:count>
3699 <rdeHeader:count
3700 uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1</rdeHeader:count>
3701 <rdeHeader:count
3702 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
3703 </rdeHeader:count>
3704 </rdeHeader:header>
3705 ...
3706
3707 The following is an example of an <rdeHeader:header> object
3708 referencing the CSV and XML model objects:
3709
3710 ...
3711 <rdeHeader:header>
3712 <rdeHeader:tld>test</rdeHeader:tld>
3713 <rdeHeader:count
3714 uri="urn:ietf:params:xml:ns:csvDomain-1.0">2</rdeHeader:count>
3715 <rdeHeader:count
3716 uri="urn:ietf:params:xml:ns:csvHost-1.0">1</rdeHeader:count>
3717 <rdeHeader:count
3718 uri="urn:ietf:params:xml:ns:csvContact-1.0">1</rdeHeader:count>
3719 <rdeHeader:count
3720 uri="urn:ietf:params:xml:ns:csvRegistrar-1.0">1
3721 </rdeHeader:count>
3722 <rdeHeader:count
3723 uri="urn:ietf:params:xml:ns:csvIDN-1.0">1</rdeHeader:count>
3724 <rdeHeader:count
3725 uri="urn:ietf:params:xml:ns:csvNNDN-1.0">1</rdeHeader:count>
3726 <rdeHeader:count
3727 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
3728 </rdeHeader:count>
3729 </rdeHeader:header>
3730 ...
3731
3732 5.10. DNRD Common Objects Collection
3733
3734 The DNRD common objects collection contains data structures
3735 referenced by two or more of the main objects in the XML model.
3736
3737 6. RDE IDN Variants Handling
3738
3739 Depending on the registration policy of the registry, for a domain
3740 name there may be multiple variant names. See [variantTLDsReport]
3741 for further details on IDN variants.
3742
3743 A registry could choose to escrow IDN variants as domains or NNDN
3744 objects. A specific IDN variant can be represented in the escrow
3745 deposit, as a domain or as an NNDN object, but not both.
3746
3747 If using domain objects to represent IDN variants, the normal
3748 behavior during restoration of an SRS based on an escrow deposit is
3749 to restore the IDN variants as a mirrored variant. If the
3750 registration data of the IDN variant is different from the original
3751 name, the details of this specific implementation MUST be described
3752 in the IDN policy document.
3753
3754 An NNDN or a domain name are explicit representations of an IDN
3755 variant while an IDN variant that is computed based on an algorithm
3756 is an implicit representation. Explicit representation of an IDN
3757 variant takes precedence over an implicit representation.
3758
3759 7. Profile
3760
3761 Different business models of registries exist, therefore the registry
3762 is responsible for defining a profile that matches its particular
3763 business model. The profile mechanism allows a registry to extend
3764 this specification.
3765
3766 A profile is the process of the following:
3767
3768 1. Extending base objects with the mechanisms defined for XML and
3769 CSV models.
3770
3771 * In the case of the XML model, abstract elements could be used
3772 to extend the following objects: <domain>, <host>, <contact>,
3773 <NNDN>, and <registrar> using the XML schema substitution
3774 groups feature.
3775
3776 2. Defining a <policy> object to specify which OPTIONAL elements of
3777 this base specification are required based on the business model
3778 of the registry. An example is the <registrant> element that is
3779 usually REQUIRED, but it is specified as OPTIONAL in this
3780 specification to support some existing business models.
3781
3782 3. Adding new escrowed objects using the <rde:contents> and
3783 <rde:deletes> elements.
3784
3785 4. Providing the XML schemas to third parties that require them to
3786 validate the escrow deposits.
3787
3788 8. Data Escrow Agent Extended Verification Process
3789
3790 A data escrow agent SHOULD perform an extended verification process
3791 that starts by creating a dataset to be tested by following
3792 Section 5.2 of [RFC8909].
3793
3794 The following are the minimum suggested tests on the dataset:
3795
3796 * Validate the escrow deposits using the definition agreed with the
3797 registry.
3798
3799 - In the case of the XML model, the contents of the escrow
3800 deposits MUST be validated using the XML schemas of the
3801 profile.
3802
3803 * Count the objects and validate that the number of objects is equal
3804 to the number objects reported in the <header> element of the
3805 escrow deposit of that point in time (Timeline Watermark).
3806
3807 * All contact objects linked to domain names MUST be present.
3808
3809 * All registrar objects linked to other objects MUST be present.
3810
3811 * No domain name exists as both a domain name and an NNDN.
3812
3813 * The elements listed as required in the <policy> element MUST be
3814 present.
3815
3816 * All idnTableRef definitions linked from other objects MUST be
3817 present.
3818
3819 * If an EPP parameters object was escrowed in the past, one and only
3820 one EPP parameters object MUST be present.
3821
3822 * The Timeline Watermark is not in the future.
3823
3824 9. Formal Syntax
3825
3826 This standard is specified in XML Schema notation. The formal syntax
3827 presented here is a complete schema representation suitable for
3828 automated validation.
3829
3830 The <CODE BEGINS> and <CODE ENDS> tags are not part of the schema;
3831 they are used to note the beginning and ending of the schema for URI
3832 registration purposes.
3833
3834 9.1. RDE CSV Schema
3835
3836 <CODE BEGINS>
3837 <?xml version="1.0" encoding="UTF-8"?>
3838 <schema targetNamespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
3839 xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
3840 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
3841 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
3842 xmlns="http://www.w3.org/2001/XMLSchema"
3843 elementFormDefault="qualified">
3844 <!--
3845 Import common element types
3846 -->
3847 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
3848 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
3849 <annotation>
3850 <documentation>
3851 Registry Data Escrow Comma-Separated Values (CSV)
3852 </documentation>
3853 </annotation>
3854 <!-- csv content element -->
3855 <element name="csv"
3856 type="rdeCsv:csvType" />
3857 <!-- Definition of CSV file -->
3858 <complexType name="csvType">
3859 <sequence>
3860 <element name="fields"
3861 type="rdeCsv:fieldsType" />
3862 <element name="files"
3863 type="rdeCsv:filesType" />
3864 </sequence>
3865 <attribute name="name"
3866 type="token"
3867 use="required" />
3868 <attribute name="sep"
3869 type="rdeCsv:sepType"
3870 default="," />
3871 </complexType>
3872 <!-- field separator must be a single character -->
3873 <simpleType name="sepType">
3874 <restriction base="string">
3875 <minLength value="1" />
3876 <maxLength value="1" />
3877 </restriction>
3878 </simpleType>
3879 <!-- Abstract field type -->
3880 <element name="field"
3881 type="rdeCsv:fieldType"
3882 abstract="true" />
3883 <complexType name="fieldType">
3884 <sequence />
3885 </complexType>
3886 <!-- fieldType with optional value (isRequired=false) -->
3887 <complexType name="fieldOptionalType">
3888 <complexContent>
3889 <extension base="rdeCsv:fieldType">
3890 <sequence />
3891 <attribute name="isRequired"
3892 type="boolean"
3893 default="false" />
3894 <attribute name="parent"
3895 type="boolean"
3896 default="false" />
3897 </extension>
3898 </complexContent>
3899 </complexType>
3900 <!-- fieldType with required value (isRequired=false) -->
3901 <complexType name="fieldRequiredType">
3902 <complexContent>
3903 <extension base="rdeCsv:fieldType">
3904 <sequence />
3905 <attribute name="isRequired"
3906 type="boolean"
3907 default="true" />
3908 <attribute name="parent"
3909 type="boolean"
3910 default="false" />
3911 </extension>
3912 </complexContent>
3913 </complexType>
3914 <!-- Concrete field types -->
3915 <!-- UTF-8 Name field (e.g., domain name) -->
3916 <element name="fUName"
3917 type="rdeCsv:fNameType"
3918 substitutionGroup="rdeCsv:field" />
3919 <complexType name="fNameType">
3920 <complexContent>
3921 <extension base="rdeCsv:fieldOptionalType">
3922 <sequence />
3923 <attribute name="type"
3924 type="token"
3925 default="eppcom\:labelType" />
3926 </extension>
3927 </complexContent>
3928 </complexType>
3929 <complexType name="fNameRequiredType">
3930 <complexContent>
3931 <extension base="rdeCsv:fieldRequiredType">
3932 <sequence />
3933 <attribute name="type"
3934 type="token"
3935 default="eppcom\:labelType" />
3936 </extension>
3937 </complexContent>
3938 </complexType>
3939 <!-- Registry Object IDentifier (roid) field -->
3940 <element name="fRoid"
3941 type="rdeCsv:fRoidType"
3942 substitutionGroup="rdeCsv:field" />
3943 <complexType name="fRoidType">
3944 <complexContent>
3945 <extension base="rdeCsv:fieldRequiredType">
3946 <sequence />
3947 <attribute name="type"
3948 type="token"
3949 default="eppcom\:roidType" />
3950 </extension>
3951 </complexContent>
3952 </complexType>
3953 <!-- Registrant field -->
3954 <element name="fRegistrant"
3955 type="rdeCsv:fRegistrantType"
3956 substitutionGroup="rdeCsv:field" />
3957 <complexType name="fRegistrantType">
3958 <complexContent>
3959 <extension base="rdeCsv:fieldOptionalType">
3960 <sequence />
3961 <attribute name="type"
3962 type="token"
3963 default="eppcom\:clIDType" />
3964 </extension>
3965 </complexContent>
3966 </complexType>
3967 <!-- Object Status Description -->
3968 <element name="fStatusDescription"
3969 type="rdeCsv:fNormalizedStringType"
3970 substitutionGroup="rdeCsv:field" />
3971 <!-- clID fields (fClID, fCrID, fUpID) -->
3972 <!-- Identifier of the client that sponsors the object -->
3973 <element name="fClID"
3974 type="rdeCsv:fClIDRequiredType"
3975 substitutionGroup="rdeCsv:field" />
3976 <!-- Identifier of registrar of client
3977 that created the object -->
3978 <element name="fCrRr"
3979 type="rdeCsv:fClIDType"
3980 substitutionGroup="rdeCsv:field" />
3981 <!-- Identifier of the client that created the object -->
3982 <element name="fCrID"
3983 type="rdeCsv:fClIDType"
3984 substitutionGroup="rdeCsv:field" />
3985 <!-- Identifier of registrar of client that
3986 updated the object -->
3987 <element name="fUpRr"
3988 type="rdeCsv:fClIDType"
3989 substitutionGroup="rdeCsv:field" />
3990 <!-- Identifier of the client that updated the object -->
3991 <element name="fUpID"
3992 type="rdeCsv:fClIDType"
3993 substitutionGroup="rdeCsv:field" />
3994 <!-- Identifier of registrar of client that
3995 requested the transfer -->
3996 <element name="fReRr"
3997 type="rdeCsv:fClIDRequiredType"
3998 substitutionGroup="rdeCsv:field" />
3999 <!-- Identifier of the client that requested
4000 the transfer -->
4001 <element name="fReID"
4002 type="rdeCsv:fClIDType"
4003 substitutionGroup="rdeCsv:field" />
4004 <!-- Identifier of registrar client that
4005 should take or took action -->
4006 <element name="fAcRr"
4007 type="rdeCsv:fClIDRequiredType"
4008 substitutionGroup="rdeCsv:field" />
4009 <!-- Identifier of the client that should take or
4010 took action -->
4011 <element name="fAcID"
4012 type="rdeCsv:fClIDType"
4013 substitutionGroup="rdeCsv:field" />
4014 <complexType name="fClIDType">
4015 <complexContent>
4016 <extension base="rdeCsv:fieldOptionalType">
4017 <sequence />
4018 <attribute name="type"
4019 type="token"
4020 default="eppcom\:clIDType" />
4021 </extension>
4022 </complexContent>
4023 </complexType>
4024 <complexType name="fClIDRequiredType">
4025 <complexContent>
4026 <extension base="rdeCsv:fieldRequiredType">
4027 <sequence />
4028 <attribute name="type"
4029 type="token"
4030 default="eppcom\:clIDType" />
4031 </extension>
4032 </complexContent>
4033 </complexType>
4034 <!-- dateTime fields (fCrDate, fUpDate, fExDate) -->
4035 <element name="fCrDate"
4036 type="rdeCsv:fDateTimeType"
4037 substitutionGroup="rdeCsv:field" />
4038 <element name="fUpDate"
4039 type="rdeCsv:fDateTimeType"
4040 substitutionGroup="rdeCsv:field" />
4041 <element name="fExDate"
4042 type="rdeCsv:fDateTimeType"
4043 substitutionGroup="rdeCsv:field" />
4044 <!-- Date and time that transfer was requested -->
4045 <element name="fReDate"
4046 type="rdeCsv:fRequiredDateTimeType"
4047 substitutionGroup="rdeCsv:field" />
4048 <!-- Date and time of a required or completed response -->
4049 <element name="fAcDate"
4050 type="rdeCsv:fRequiredDateTimeType"
4051 substitutionGroup="rdeCsv:field" />
4052 <element name="fTrDate"
4053 type="rdeCsv:fDateTimeType"
4054 substitutionGroup="rdeCsv:field" />
4055 <complexType name="fDateTimeType">
4056 <complexContent>
4057 <extension base="rdeCsv:fieldOptionalType">
4058 <sequence />
4059 <attribute name="type"
4060 type="token"
4061 default="dateTime" />
4062 </extension>
4063 </complexContent>
4064 </complexType>
4065 <complexType name="fRequiredDateTimeType">
4066 <complexContent>
4067 <extension base="rdeCsv:fieldRequiredType">
4068 <sequence />
4069 <attribute name="type"
4070 type="token"
4071 default="dateTime" />
4072 </extension>
4073 </complexContent>
4074 </complexType>
4075 <!-- boolean type -->
4076 <complexType name="fBooleanType">
4077 <complexContent>
4078 <extension base="rdeCsv:fieldOptionalType">
4079 <sequence />
4080 <attribute name="type"
4081 type="token"
4082 default="boolean" />
4083 </extension>
4084 </complexContent>
4085 </complexType>
4086 <complexType name="fRequiredBooleanType">
4087 <complexContent>
4088 <extension base="rdeCsv:fieldRequiredType">
4089 <sequence />
4090 <attribute name="type"
4091 type="token"
4092 default="boolean" />
4093 </extension>
4094 </complexContent>
4095 </complexType>
4096 <!-- unsignedByte type -->
4097 <complexType name="fUnsignedByteType">
4098 <complexContent>
4099 <extension base="rdeCsv:fieldOptionalType">
4100 <sequence />
4101 <attribute name="type"
4102 type="token"
4103 default="unsignedByte" />
4104 </extension>
4105 </complexContent>
4106 </complexType>
4107 <complexType name="fRequiredUnsignedByteType">
4108 <complexContent>
4109 <extension base="rdeCsv:fieldRequiredType">
4110 <sequence />
4111 <attribute name="type"
4112 type="token"
4113 default="unsignedByte" />
4114 </extension>
4115 </complexContent>
4116 </complexType>
4117 <!-- unsignedShort type -->
4118 <complexType name="fUnsignedShortType">
4119 <complexContent>
4120 <extension base="rdeCsv:fieldOptionalType">
4121 <sequence />
4122 <attribute name="type"
4123 type="token"
4124 default="unsignedShort" />
4125 </extension>
4126 </complexContent>
4127 </complexType>
4128 <complexType name="fRequiredUnsignedShortType">
4129 <complexContent>
4130 <extension base="rdeCsv:fieldRequiredType">
4131 <sequence />
4132 <attribute name="type"
4133 type="token"
4134 default="unsignedShort" />
4135 </extension>
4136 </complexContent>
4137 </complexType>
4138 <!-- hexBinary type -->
4139 <complexType name="fHexBinaryType">
4140 <complexContent>
4141 <extension base="rdeCsv:fieldOptionalType">
4142 <sequence />
4143 <attribute name="type"
4144 type="token"
4145 default="hexBinary" />
4146 </extension>
4147 </complexContent>
4148 </complexType>
4149 <complexType name="fRequiredHexBinaryType">
4150 <complexContent>
4151 <extension base="rdeCsv:fieldRequiredType">
4152 <sequence />
4153 <attribute name="type"
4154 type="token"
4155 default="hexBinary" />
4156 </extension>
4157 </complexContent>
4158 </complexType>
4159 <!-- language type -->
4160 <element name="fLang"
4161 type="rdeCsv:fLangType"
4162 substitutionGroup="rdeCsv:field" />
4163 <complexType name="fLangType">
4164 <complexContent>
4165 <extension base="rdeCsv:fieldOptionalType">
4166 <sequence />
4167 <attribute name="type"
4168 type="token"
4169 default="language" />
4170 </extension>
4171 </complexContent>
4172 </complexType>
4173 <!-- IDN Table Identifier -->
4174 <element name="fIdnTableId"
4175 type="rdeCsv:fTokenType"
4176 substitutionGroup="rdeCsv:field" />
4177 <!-- State of the most recent transfer request -->
4178 <element name="fTrStatus"
4179 type="rdeCsv:fTrStatusType"
4180 substitutionGroup="rdeCsv:field" />
4181 <complexType name="fTrStatusType">
4182 <complexContent>
4183 <extension base="rdeCsv:fieldRequiredType">
4184 <sequence />
4185 <attribute name="type"
4186 type="token"
4187 default="eppcom\:trStatusType" />
4188 </extension>
4189 </complexContent>
4190 </complexType>
4191 <!-- General token type -->
4192 <complexType name="fTokenType">
4193 <complexContent>
4194 <extension base="rdeCsv:fieldOptionalType">
4195 <sequence />
4196 <attribute name="type"
4197 type="token"
4198 default="token" />
4199 </extension>
4200 </complexContent>
4201 </complexType>
4202 <!-- General normalizedString type -->
4203 <complexType name="fNormalizedStringType">
4204 <complexContent>
4205 <extension base="rdeCsv:fieldOptionalType">
4206 <sequence />
4207 <attribute name="type"
4208 type="token"
4209 default="normalizedString" />
4210 </extension>
4211 </complexContent>
4212 </complexType>
4213 <!-- positive integer type -->
4214 <complexType name="fPositiveIntegerType">
4215 <complexContent>
4216 <extension base="rdeCsv:fieldOptionalType">
4217 <sequence />
4218 <attribute name="type"
4219 type="token"
4220 default="positiveInteger" />
4221 </extension>
4222 </complexContent>
4223 </complexType>
4224 <!-- Custom / extension field type -->
4225 <element name="fCustom"
4226 type="rdeCsv:fCustomType"
4227 substitutionGroup="rdeCsv:field" />
4228 <complexType name="fCustomType">
4229 <complexContent>
4230 <extension base="rdeCsv:fieldOptionalType">
4231 <sequence />
4232 <attribute name="name"
4233 type="token" />
4234 <attribute name="type"
4235 type="token"
4236 default="token" />
4237 </extension>
4238 </complexContent>
4239 </complexType>
4240 <!-- Ordered list of field definitions for the csv -->
4241 <complexType name="fieldsType">
4242 <sequence maxOccurs="unbounded">
4243 <element ref="rdeCsv:field" />
4244 </sequence>
4245 </complexType>
4246 <!-- List of files -->
4247 <complexType name="filesType">
4248 <sequence>
4249 <element name="file"
4250 type="rdeCsv:fileType"
4251 maxOccurs="unbounded" />
4252 </sequence>
4253 </complexType>
4254 <!-- File definition -->
4255 <complexType name="fileType">
4256 <simpleContent>
4257 <extension base="token">
4258 <attribute name="compression"
4259 type="token" />
4260 <attribute name="encoding"
4261 type="token"
4262 default="UTF-8" />
4263 <attribute name="cksum"
4264 type="token" />
4265 <attribute name="cksumAlg"
4266 type="token"
4267 default="CRC32" />
4268 </extension>
4269 </simpleContent>
4270 </complexType>
4271 <!-- URL fields -->
4272 <element name="fUrl"
4273 type="rdeCsv:anyURIType"
4274 substitutionGroup="rdeCsv:field" />
4275 <complexType name="anyURIType">
4276 <complexContent>
4277 <extension base="rdeCsv:fieldOptionalType">
4278 <sequence />
4279 <attribute name="type"
4280 type="token"
4281 default="anyURI" />
4282 </extension>
4283 </complexContent>
4284 </complexType>
4285 <!--
4286 End of schema.
4287 -->
4288 </schema>
4289 <CODE ENDS>
4290
4291 9.2. RDE Domain Object
4292
4293 <CODE BEGINS>
4294 <?xml version="1.0" encoding="UTF-8"?>
4295 <schema targetNamespace="urn:ietf:params:xml:ns:rdeDomain-1.0"
4296 xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
4297 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
4298 xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
4299 xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
4300 xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
4301 xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
4302 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
4303 xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
4304 xmlns="http://www.w3.org/2001/XMLSchema"
4305 elementFormDefault="qualified">
4306 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
4307 <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
4308 <import namespace="urn:ietf:params:xml:ns:secDNS-1.1" />
4309 <import namespace="urn:ietf:params:xml:ns:rgp-1.0" />
4310 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
4311 <import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0" />
4312 <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
4313 <annotation>
4314 <documentation>
4315 Registry Data Escrow Domain provisioning schema
4316 </documentation>
4317 </annotation>
4318 <element name="abstractDomain"
4319 type="rdeDomain:abstractContentType"
4320 substitutionGroup="rde:content"
4321 abstract="true" />
4322 <element name="domain"
4323 substitutionGroup="rdeDomain:abstractDomain" />
4324 <element name="delete"
4325 type="rdeDomain:deleteType"
4326 substitutionGroup="rde:delete" />
4327 <!-- Content Type -->
4328 <complexType name="abstractContentType">
4329 <complexContent>
4330 <extension base="rde:contentType">
4331 <sequence>
4332 <element name="name"
4333 type="eppcom:labelType" />
4334 <element name="roid"
4335 type="eppcom:roidType" />
4336 <element name="uName"
4337 type="eppcom:labelType"
4338 minOccurs="0" />
4339 <element name="idnTableId"
4340 type="rdeIDN:idType"
4341 minOccurs="0" />
4342 <element name="originalName"
4343 type="eppcom:labelType"
4344 minOccurs="0" />
4345 <element name="status"
4346 type="domain:statusType"
4347 maxOccurs="11" />
4348 <element name="rgpStatus"
4349 type="rgp:statusType"
4350 minOccurs="0"
4351 maxOccurs="unbounded" />
4352 <element name="registrant"
4353 type="eppcom:clIDType"
4354 minOccurs="0" />
4355 <element name="contact"
4356 type="domain:contactType"
4357 minOccurs="0"
4358 maxOccurs="unbounded" />
4359 <element name="ns"
4360 type="domain:nsType"
4361 minOccurs="0" />
4362 <element name="clID"
4363 type="eppcom:clIDType" />
4364 <element name="crRr"
4365 type="rdeDnrdCommon:rrType"
4366 minOccurs="0" />
4367 <element name="crDate"
4368 type="dateTime"
4369 minOccurs="0" />
4370 <element name="exDate"
4371 type="dateTime"
4372 minOccurs="0" />
4373 <element name="upRr"
4374 type="rdeDnrdCommon:rrType"
4375 minOccurs="0" />
4376 <element name="upDate"
4377 type="dateTime"
4378 minOccurs="0" />
4379 <element name="secDNS"
4380 type="secDNS:dsOrKeyType"
4381 minOccurs="0" />
4382 <element name="trDate"
4383 type="dateTime"
4384 minOccurs="0" />
4385 <element name="trnData"
4386 type="rdeDomain:transferDataType"
4387 minOccurs="0" />
4388 </sequence>
4389 </extension>
4390 </complexContent>
4391 </complexType>
4392 <complexType name="transferDataType">
4393 <sequence>
4394 <element name="trStatus"
4395 type="eppcom:trStatusType" />
4396 <element name="reRr"
4397 type="rdeDnrdCommon:rrType" />
4398 <element name="reDate"
4399 type="dateTime" />
4400 <element name="acRr"
4401 type="rdeDnrdCommon:rrType" />
4402 <element name="acDate"
4403 type="dateTime" />
4404 <element name="exDate"
4405 type="dateTime"
4406 minOccurs="0" />
4407 </sequence>
4408 </complexType>
4409 <!-- Delete Type -->
4410 <complexType name="deleteType">
4411 <complexContent>
4412 <extension base="rde:deleteType">
4413 <sequence>
4414 <element name="name"
4415 type="eppcom:labelType"
4416 minOccurs="0"
4417 maxOccurs="unbounded" />
4418 </sequence>
4419 </extension>
4420 </complexContent>
4421 </complexType>
4422 </schema>
4423 <CODE ENDS>
4424
4425 9.3. CSV Domain Object
4426
4427 <CODE BEGINS>
4428 <?xml version="1.0" encoding="UTF-8"?>
4429 <schema targetNamespace="urn:ietf:params:xml:ns:csvDomain-1.0"
4430 xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
4431 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
4432 xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
4433 xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
4434 xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
4435 xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
4436 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
4437 xmlns="http://www.w3.org/2001/XMLSchema"
4438 elementFormDefault="qualified">
4439 <!--
4440 Import common element types
4441 -->
4442 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
4443 <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
4444 <import namespace="urn:ietf:params:xml:ns:secDNS-1.1" />
4445 <import namespace="urn:ietf:params:xml:ns:rgp-1.0" />
4446 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
4447 <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
4448 <annotation>
4449 <documentation>
4450 Domain Name Comma-Separated Values (CSV) Object
4451 </documentation>
4452 </annotation>
4453 <!--
4454 Child elements of the <rde:contents> object
4455 -->
4456 <element name="contents"
4457 type="csvDomain:contentType"
4458 substitutionGroup="rde:content" />
4459 <complexType name="contentType">
4460 <complexContent>
4461 <extension base="rde:contentType">
4462 <sequence>
4463 <element ref="rdeCsv:csv"
4464 maxOccurs="unbounded" />
4465 </sequence>
4466 </extension>
4467 </complexContent>
4468 </complexType>
4469 <!--
4470 Child elements of the <rde:deletes> object
4471 -->
4472 <element name="deletes"
4473 type="csvDomain:deleteType"
4474 substitutionGroup="rde:delete" />
4475 <complexType name="deleteType">
4476 <complexContent>
4477 <extension base="rde:deleteType">
4478 <sequence>
4479 <element ref="rdeCsv:csv"
4480 maxOccurs="unbounded" />
4481 </sequence>
4482 </extension>
4483 </complexContent>
4484 </complexType>
4485 <!-- Domain name field -->
4486 <element name="fName"
4487 type="rdeCsv:fNameRequiredType"
4488 substitutionGroup="rdeCsv:field" />
4489 <!-- RGP status field -->
4490 <element name="fRgpStatus"
4491 type="csvDomain:fRgpStatusType"
4492 substitutionGroup="rdeCsv:field" />
4493 <complexType name="fRgpStatusType">
4494 <complexContent>
4495 <extension base="rdeCsv:fieldOptionalType">
4496 <sequence />
4497 <attribute name="type"
4498 type="token"
4499 default="rgp\:statusValueType" />
4500 </extension>
4501 </complexContent>
4502 </complexType>
4503 <!-- Contact type field -->
4504 <element name="fContactType"
4505 type="csvDomain:fContactsTypeType"
4506 substitutionGroup="rdeCsv:field" />
4507 <complexType name="fContactsTypeType">
4508 <complexContent>
4509 <extension base="rdeCsv:fieldRequiredType">
4510 <sequence />
4511 <attribute name="type"
4512 type="token"
4513 default="domain\:contactAttrType" />
4514 </extension>
4515 </complexContent>
4516 </complexType>
4517 <!-- DNSSEC field types -->
4518 <!-- Maximum signature lifetime field -->
4519 <element name="fMaxSigLife"
4520 type="csvDomain:fMaxSigLifeType"
4521 substitutionGroup="rdeCsv:field" />
4522 <complexType name="fMaxSigLifeType">
4523 <complexContent>
4524 <extension base="rdeCsv:fieldOptionalType">
4525 <sequence />
4526 <attribute name="type"
4527 type="token"
4528 default="secDNS\:maxSigLifeType" />
4529 </extension>
4530 </complexContent>
4531 </complexType>
4532 <!-- Key tag field -->
4533 <element name="fKeyTag"
4534 type="rdeCsv:fRequiredUnsignedShortType"
4535 substitutionGroup="rdeCsv:field" />
4536 <!-- DS Algorithm field -->
4537 <element name="fDsAlg"
4538 type="rdeCsv:fRequiredUnsignedByteType"
4539 substitutionGroup="rdeCsv:field" />
4540 <!-- Digest type field -->
4541 <element name="fDigestType"
4542 type="rdeCsv:fRequiredUnsignedByteType"
4543 substitutionGroup="rdeCsv:field" />
4544 <!-- Digest field -->
4545 <element name="fDigest"
4546 type="rdeCsv:fRequiredHexBinaryType"
4547 substitutionGroup="rdeCsv:field" />
4548 <!-- Flags field -->
4549 <element name="fFlags"
4550 type="rdeCsv:fRequiredUnsignedShortType"
4551 substitutionGroup="rdeCsv:field" />
4552 <!-- Protocol field -->
4553 <element name="fProtocol"
4554 type="rdeCsv:fRequiredUnsignedByteType"
4555 substitutionGroup="rdeCsv:field" />
4556 <!-- Key Algorithm field -->
4557 <element name="fKeyAlg"
4558 type="rdeCsv:fRequiredUnsignedByteType"
4559 substitutionGroup="rdeCsv:field" />
4560 <!-- Public Key field -->
4561 <element name="fPubKey"
4562 type="csvDomain:fPubKeyType"
4563 substitutionGroup="rdeCsv:field" />
4564 <complexType name="fPubKeyType">
4565 <complexContent>
4566 <extension base="rdeCsv:fieldRequiredType">
4567 <sequence />
4568 <attribute name="type"
4569 type="token"
4570 default="secDNS\:keyType" />
4571 </extension>
4572 </complexContent>
4573 </complexType>
4574 <!-- Original Domain Name for Variant field -->
4575 <element name="fOriginalName"
4576 type="rdeCsv:fNameType"
4577 substitutionGroup="rdeCsv:field" />
4578 <!-- Domain status field -->
4579 <element name="fStatus"
4580 type="csvDomain:fStatusType"
4581 substitutionGroup="rdeCsv:field" />
4582 <!-- Domain status based on domain-1.0.xsd -->
4583 <complexType name="fStatusType">
4584 <complexContent>
4585 <extension base="rdeCsv:fieldRequiredType">
4586 <sequence />
4587 <attribute name="type"
4588 type="token"
4589 default="domain\:statusValueType" />
4590 </extension>
4591 </complexContent>
4592 </complexType>
4593 <!--
4594 End of schema.
4595 -->
4596 </schema>
4597 <CODE ENDS>
4598
4599 9.4. RDE Host Object
4600
4601 <CODE BEGINS>
4602 <?xml version="1.0" encoding="UTF-8"?>
4603 <schema targetNamespace="urn:ietf:params:xml:ns:rdeHost-1.0"
4604 xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
4605 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
4606 xmlns:host="urn:ietf:params:xml:ns:host-1.0"
4607 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
4608 xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
4609 xmlns="http://www.w3.org/2001/XMLSchema"
4610 elementFormDefault="qualified">
4611 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
4612 <import namespace="urn:ietf:params:xml:ns:host-1.0" />
4613 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
4614 <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
4615 <annotation>
4616 <documentation>
4617 Registry Data Escrow Host provisioning schema
4618 </documentation>
4619 </annotation>
4620 <element name="abstractHost"
4621 type="rdeHost:abstractContentType"
4622 substitutionGroup="rde:content"
4623 abstract="true" />
4624 <element name="host"
4625 substitutionGroup="rdeHost:abstractHost" />
4626 <element name="delete"
4627 type="rdeHost:deleteType"
4628 substitutionGroup="rde:delete" />
4629 <!-- Content Type -->
4630 <complexType name="abstractContentType">
4631 <complexContent>
4632 <extension base="rde:contentType">
4633 <sequence>
4634 <element name="name"
4635 type="eppcom:labelType" />
4636 <element name="roid"
4637 type="eppcom:roidType" />
4638 <element name="status"
4639 type="host:statusType"
4640 maxOccurs="7" />
4641 <element name="addr"
4642 type="host:addrType"
4643 minOccurs="0"
4644 maxOccurs="unbounded" />
4645 <element name="clID"
4646 type="eppcom:clIDType" />
4647 <element name="crRr"
4648 type="rdeDnrdCommon:rrType"
4649 minOccurs="0" />
4650 <element name="crDate"
4651 type="dateTime"
4652 minOccurs="0" />
4653 <element name="upRr"
4654 type="rdeDnrdCommon:rrType"
4655 minOccurs="0" />
4656 <element name="upDate"
4657 type="dateTime"
4658 minOccurs="0" />
4659 <element name="trDate"
4660 type="dateTime"
4661 minOccurs="0" />
4662 </sequence>
4663 </extension>
4664 </complexContent>
4665 </complexType>
4666 <!-- Delete Type -->
4667 <complexType name="deleteType">
4668 <complexContent>
4669 <extension base="rde:deleteType">
4670 <choice minOccurs="0"
4671 maxOccurs="unbounded">
4672 <element name="name"
4673 type="eppcom:labelType" />
4674 <element name="roid"
4675 type="eppcom:roidType" />
4676 </choice>
4677 </extension>
4678 </complexContent>
4679 </complexType>
4680 </schema>
4681 <CODE ENDS>
4682
4683 9.5. CSV Host Object
4684
4685 <CODE BEGINS>
4686 <?xml version="1.0" encoding="UTF-8"?>
4687 <schema targetNamespace="urn:ietf:params:xml:ns:csvHost-1.0"
4688 xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
4689 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
4690 xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
4691 xmlns:host="urn:ietf:params:xml:ns:host-1.0"
4692 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
4693 xmlns="http://www.w3.org/2001/XMLSchema"
4694 elementFormDefault="qualified">
4695 <!--
4696 Import common element types
4697 -->
4698 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
4699 <import namespace="urn:ietf:params:xml:ns:host-1.0" />
4700 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
4701 <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
4702 <annotation>
4703 <documentation>
4704 Host Comma-Separated Values (CSV) Object
4705 </documentation>
4706 </annotation>
4707 <!--
4708 Child elements of the <rde:contents> object
4709 -->
4710 <element name="contents"
4711 type="csvHost:contentType"
4712 substitutionGroup="rde:content" />
4713 <complexType name="contentType">
4714 <complexContent>
4715 <extension base="rde:contentType">
4716 <sequence>
4717 <element ref="rdeCsv:csv"
4718 maxOccurs="unbounded" />
4719 </sequence>
4720 </extension>
4721 </complexContent>
4722 </complexType>
4723 <!--
4724 Child elements of the <rde:deletes> object
4725 -->
4726 <element name="deletes"
4727 type="csvHost:deleteType"
4728 substitutionGroup="rde:delete" />
4729 <complexType name="deleteType">
4730 <complexContent>
4731 <extension base="rde:deleteType">
4732 <sequence>
4733 <element ref="rdeCsv:csv"
4734 maxOccurs="unbounded" />
4735 </sequence>
4736 </extension>
4737 </complexContent>
4738 </complexType>
4739 <!-- Host name field -->
4740 <element name="fName"
4741 type="rdeCsv:fNameRequiredType"
4742 substitutionGroup="rdeCsv:field" />
4743 <!-- IP address field -->
4744 <element name="fAddr"
4745 type="csvHost:fAddrType"
4746 substitutionGroup="rdeCsv:field" />
4747 <complexType name="fAddrType">
4748 <complexContent>
4749 <extension base="rdeCsv:fieldOptionalType">
4750 <sequence />
4751 <attribute name="type"
4752 type="token"
4753 default="host\:addrStringType" />
4754 </extension>
4755 </complexContent>
4756 </complexType>
4757 <!-- IP address version field -->
4758 <element name="fAddrVersion"
4759 type="csvHost:fAddrVersionType"
4760 substitutionGroup="rdeCsv:field" />
4761 <complexType name="fAddrVersionType">
4762 <complexContent>
4763 <extension base="rdeCsv:fieldOptionalType">
4764 <sequence />
4765 <attribute name="type"
4766 type="token"
4767 default="host\:ipType" />
4768 </extension>
4769 </complexContent>
4770 </complexType>
4771 <!-- Host status field -->
4772 <element name="fStatus"
4773 type="csvHost:fStatusType"
4774 substitutionGroup="rdeCsv:field" />
4775 <!-- Host status based on host-1.0.xsd -->
4776 <complexType name="fStatusType">
4777 <complexContent>
4778 <extension base="rdeCsv:fieldRequiredType">
4779 <sequence />
4780 <attribute name="type"
4781 type="token"
4782 default="host\:statusValueType" />
4783 </extension>
4784 </complexContent>
4785 </complexType>
4786 <!--
4787 End of schema.
4788 -->
4789 </schema>
4790 <CODE ENDS>
4791
4792 9.6. RDE Contact Object
4793
4794 <CODE BEGINS>
4795 <?xml version="1.0" encoding="UTF-8"?>
4796 <schema targetNamespace="urn:ietf:params:xml:ns:rdeContact-1.0"
4797 xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
4798 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
4799 xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
4800 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
4801 xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
4802 xmlns="http://www.w3.org/2001/XMLSchema"
4803 elementFormDefault="qualified">
4804 <!-- Import common element types. -->
4805 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
4806 <import namespace="urn:ietf:params:xml:ns:contact-1.0" />
4807 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
4808 <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
4809 <annotation>
4810 <documentation>
4811 Registry Data Escrow contact provisioning schema
4812 </documentation>
4813 </annotation>
4814 <element name="abstractContact"
4815 type="rdeContact:abstractContentType"
4816 substitutionGroup="rde:content"
4817 abstract="true" />
4818 <element name="contact"
4819 substitutionGroup="rdeContact:abstractContact" />
4820 <element name="delete"
4821 type="rdeContact:deleteType"
4822 substitutionGroup="rde:delete" />
4823 <!-- Contact Type -->
4824 <complexType name="abstractContentType">
4825 <complexContent>
4826 <extension base="rde:contentType">
4827 <sequence>
4828 <element name="id"
4829 type="eppcom:clIDType" />
4830 <element name="roid"
4831 type="eppcom:roidType" />
4832 <element name="status"
4833 type="contact:statusType"
4834 maxOccurs="7" />
4835 <element name="postalInfo"
4836 type="contact:postalInfoType"
4837 maxOccurs="2" />
4838 <element name="voice"
4839 type="contact:e164Type"
4840 minOccurs="0" />
4841 <element name="fax"
4842 type="contact:e164Type"
4843 minOccurs="0" />
4844 <element name="email"
4845 type="eppcom:minTokenType" />
4846 <element name="clID"
4847 type="eppcom:clIDType" />
4848 <element name="crRr"
4849 type="rdeDnrdCommon:rrType"
4850 minOccurs="0" />
4851 <element name="crDate"
4852 type="dateTime"
4853 minOccurs="0" />
4854 <element name="upRr"
4855 type="rdeDnrdCommon:rrType"
4856 minOccurs="0" />
4857 <element name="upDate"
4858 type="dateTime"
4859 minOccurs="0" />
4860 <element name="trDate"
4861 type="dateTime"
4862 minOccurs="0" />
4863 <element name="trnData"
4864 type="rdeContact:transferDataType"
4865 minOccurs="0" />
4866 <element name="disclose"
4867 type="contact:discloseType"
4868 minOccurs="0" />
4869 </sequence>
4870 </extension>
4871 </complexContent>
4872 </complexType>
4873 <complexType name="transferDataType">
4874 <sequence>
4875 <element name="trStatus"
4876 type="eppcom:trStatusType" />
4877 <element name="reRr"
4878 type="rdeDnrdCommon:rrType" />
4879 <element name="reDate"
4880 type="dateTime" />
4881 <element name="acRr"
4882 type="rdeDnrdCommon:rrType" />
4883 <element name="acDate"
4884 type="dateTime" />
4885 </sequence>
4886 </complexType>
4887 <!-- Delete Type -->
4888 <complexType name="deleteType">
4889 <complexContent>
4890 <extension base="rde:deleteType">
4891 <sequence>
4892 <element name="id"
4893 type="eppcom:clIDType"
4894 minOccurs="0"
4895 maxOccurs="unbounded" />
4896 </sequence>
4897 </extension>
4898 </complexContent>
4899 </complexType>
4900 </schema>
4901 <CODE ENDS>
4902
4903 9.7. CSV Contact Object
4904
4905 <CODE BEGINS>
4906 <?xml version="1.0" encoding="UTF-8"?>
4907 <schema targetNamespace="urn:ietf:params:xml:ns:csvContact-1.0"
4908 xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0"
4909 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
4910 xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
4911 xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
4912 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
4913 xmlns="http://www.w3.org/2001/XMLSchema"
4914 elementFormDefault="qualified">
4915 <!--
4916 Import common element types.
4917 -->
4918 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
4919 <import namespace="urn:ietf:params:xml:ns:contact-1.0" />
4920 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
4921 <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
4922 <annotation>
4923 <documentation>
4924 Contact Comma-Separated Values (CSV) Object
4925 </documentation>
4926 </annotation>
4927 <!--
4928 Child elements of the <rde:contents> object
4929 -->
4930 <element name="contents"
4931 type="csvContact:contentType"
4932 substitutionGroup="rde:content" />
4933 <complexType name="contentType">
4934 <complexContent>
4935 <extension base="rde:contentType">
4936 <sequence>
4937 <element ref="rdeCsv:csv"
4938 maxOccurs="unbounded" />
4939 </sequence>
4940 </extension>
4941 </complexContent>
4942 </complexType>
4943 <!--
4944 Child elements of the <rde:deletes> object
4945 -->
4946 <element name="deletes"
4947 type="csvContact:deleteType"
4948 substitutionGroup="rde:delete" />
4949 <complexType name="deleteType">
4950 <complexContent>
4951 <extension base="rde:deleteType">
4952 <sequence>
4953 <element ref="rdeCsv:csv"
4954 maxOccurs="unbounded" />
4955 </sequence>
4956 </extension>
4957 </complexContent>
4958 </complexType>
4959 <!-- Server-unique contact identifier field -->
4960 <element name="fId"
4961 type="csvContact:fIdType"
4962 substitutionGroup="rdeCsv:field" />
4963 <complexType name="fIdType">
4964 <complexContent>
4965 <extension base="rdeCsv:fieldRequiredType">
4966 <sequence />
4967 <attribute name="type"
4968 type="token"
4969 default="eppcom\:clIDType" />
4970 </extension>
4971 </complexContent>
4972 </complexType>
4973 <!-- Is Registrar Contact field -->
4974 <element name="fIsRegistrarContact"
4975 type="rdeCsv:fBooleanType"
4976 substitutionGroup="rdeCsv:field" />
4977 <!-- voice and fax telephone number fields -->
4978 <element name="fVoice"
4979 type="csvContact:fE164StringType"
4980 substitutionGroup="rdeCsv:field" />
4981 <element name="fFax"
4982 type="csvContact:fE164StringType"
4983 substitutionGroup="rdeCsv:field" />
4984 <complexType name="fE164StringType">
4985 <complexContent>
4986 <extension base="rdeCsv:fieldOptionalType">
4987 <sequence />
4988 <attribute name="type"
4989 type="token"
4990 default="contact\:e164StringType" />
4991 </extension>
4992 </complexContent>
4993 </complexType>
4994 <!-- voice and fax telephone extension fields -->
4995 <element name="fVoiceExt"
4996 type="rdeCsv:fTokenType"
4997 substitutionGroup="rdeCsv:field" />
4998 <element name="fFaxExt"
4999 type="rdeCsv:fTokenType"
5000 substitutionGroup="rdeCsv:field" />
5001 <!-- contact email address field -->
5002 <element name="fEmail"
5003 type="csvContact:fEmailType"
5004 substitutionGroup="rdeCsv:field" />
5005 <complexType name="fEmailType">
5006 <complexContent>
5007 <extension base="rdeCsv:fieldRequiredType">
5008 <sequence />
5009 <attribute name="type"
5010 type="token"
5011 default="eppcom\:minTokenType" />
5012 </extension>
5013 </complexContent>
5014 </complexType>
5015 <!--
5016 Postal type field
5017 ("loc" = localized, "int" = internationalized)
5018 -->
5019 <element name="fPostalType"
5020 type="csvContact:fPostalTypeType"
5021 substitutionGroup="rdeCsv:field" />
5022 <complexType name="fPostalTypeType">
5023 <complexContent>
5024 <extension base="rdeCsv:fieldRequiredType">
5025 <sequence />
5026 <attribute name="type"
5027 type="token"
5028 default="contact\:postalInfoEnumType" />
5029 </extension>
5030 </complexContent>
5031 </complexType>
5032 <!-- Standard postal line field -->
5033 <complexType name="fPostalLineType">
5034 <complexContent>
5035 <extension base="rdeCsv:fieldRequiredType">
5036 <sequence />
5037 <attribute name="type"
5038 type="token"
5039 default="contact\:postalLineType" />
5040 <attribute name="isLoc"
5041 type="boolean" />
5042 </extension>
5043 </complexContent>
5044 </complexType>
5045 <!-- Standard optional postal line field -->
5046 <complexType name="fOptPostalLineType">
5047 <complexContent>
5048 <extension base="rdeCsv:fieldOptionalType">
5049 <sequence />
5050 <attribute name="type"
5051 type="token"
5052 default="contact\:optPostalLineType" />
5053 <attribute name="isLoc"
5054 type="boolean" />
5055 </extension>
5056 </complexContent>
5057 </complexType>
5058 <!-- Name of the individual or role field -->
5059 <element name="fName"
5060 type="csvContact:fPostalLineType"
5061 substitutionGroup="rdeCsv:field" />
5062 <!-- Name organization field -->
5063 <element name="fOrg"
5064 type="csvContact:fOptPostalLineType"
5065 substitutionGroup="rdeCsv:field" />
5066 <!-- Street address line field with required index attribute -->
5067 <!-- starting with index 0. -->
5068 <element name="fStreet"
5069 type="csvContact:fStreetType"
5070 substitutionGroup="rdeCsv:field" />
5071 <complexType name="fStreetType">
5072 <complexContent>
5073 <extension base="csvContact:fOptPostalLineType">
5074 <sequence />
5075 <attribute name="index"
5076 type="int"
5077 use="required" />
5078 </extension>
5079 </complexContent>
5080 </complexType>
5081 <!-- Contact's city field -->
5082 <element name="fCity"
5083 type="csvContact:fPostalLineType"
5084 substitutionGroup="rdeCsv:field" />
5085 <!-- Contact's state or province field -->
5086 <element name="fSp"
5087 type="csvContact:fOptPostalLineType"
5088 substitutionGroup="rdeCsv:field" />
5089 <!-- Contact's postal code field -->
5090 <element name="fPc"
5091 type="csvContact:fPcType"
5092 substitutionGroup="rdeCsv:field" />
5093 <complexType name="fPcType">
5094 <complexContent>
5095 <extension base="rdeCsv:fieldOptionalType">
5096 <sequence />
5097 <attribute name="type"
5098 type="token"
5099 default="contact\:pcType" />
5100 <attribute name="isLoc"
5101 type="boolean" />
5102 </extension>
5103 </complexContent>
5104 </complexType>
5105 <!-- Contact's country code field -->
5106 <element name="fCc"
5107 type="csvContact:fCcType"
5108 substitutionGroup="rdeCsv:field" />
5109 <complexType name="fCcType">
5110 <complexContent>
5111 <extension base="rdeCsv:fieldRequiredType">
5112 <sequence />
5113 <attribute name="type"
5114 type="token"
5115 default="contact\:ccType" />
5116 <attribute name="isLoc"
5117 type="boolean" />
5118 </extension>
5119 </complexContent>
5120 </complexType>
5121 <!-- Disclosure element fields -->
5122 <!-- Flag of "1" to allow disclosure
5123 and "0" to disallow disclosure -->
5124 <element name="fDiscloseFlag"
5125 type="csvContact:fBoolean"
5126 substitutionGroup="rdeCsv:field" />
5127 <!-- Disclosure of localized name
5128 based on fDiscloseFlag? -->
5129 <element name="fDiscloseNameLoc"
5130 type="csvContact:fBoolean"
5131 substitutionGroup="rdeCsv:field" />
5132 <!-- Disclosure of internationalized name
5133 based on fDiscloseFlag? -->
5134 <element name="fDiscloseNameInt"
5135 type="csvContact:fBoolean"
5136 substitutionGroup="rdeCsv:field" />
5137 <!-- Disclosure of localized org
5138 based on fDiscloseFlag? -->
5139 <element name="fDiscloseOrgLoc"
5140 type="csvContact:fBoolean"
5141 substitutionGroup="rdeCsv:field" />
5142 <!-- Disclosure of internationalized org
5143 based on fDiscloseFlag? -->
5144 <element name="fDiscloseOrgInt"
5145 type="csvContact:fBoolean"
5146 substitutionGroup="rdeCsv:field" />
5147 <!-- Disclosure of localized address
5148 based on fDiscloseFlag? -->
5149 <element name="fDiscloseAddrLoc"
5150 type="csvContact:fBoolean"
5151 substitutionGroup="rdeCsv:field" />
5152 <!-- Disclosure of internationalized address
5153 based on fDiscloseFlag? -->
5154 <element name="fDiscloseAddrInt"
5155 type="csvContact:fBoolean"
5156 substitutionGroup="rdeCsv:field" />
5157 <!-- Disclosure voice telephone number
5158 based on fDiscloseFlag? -->
5159 <element name="fDiscloseVoice"
5160 type="csvContact:fBoolean"
5161 substitutionGroup="rdeCsv:field" />
5162 <!-- Disclosure facsimile telephone number
5163 based on fDiscloseFlag? -->
5164 <element name="fDiscloseFax"
5165 type="csvContact:fBoolean"
5166 substitutionGroup="rdeCsv:field" />
5167 <!-- Disclosure email address
5168 based on fDiscloseFlag? -->
5169 <element name="fDiscloseEmail"
5170 type="csvContact:fBoolean"
5171 substitutionGroup="rdeCsv:field" />
5172 <complexType name="fBoolean">
5173 <complexContent>
5174 <extension base="rdeCsv:fieldOptionalType">
5175 <sequence />
5176 <attribute name="type"
5177 type="token"
5178 default="boolean" />
5179 </extension>
5180 </complexContent>
5181 </complexType>
5182 <!-- Contact status field -->
5183 <element name="fStatus"
5184 type="csvContact:fStatusType"
5185 substitutionGroup="rdeCsv:field" />
5186 <!-- Host status based on contact-1.0.xsd -->
5187 <complexType name="fStatusType">
5188 <complexContent>
5189 <extension base="rdeCsv:fieldRequiredType">
5190 <sequence />
5191 <attribute name="type"
5192 type="token"
5193 default="contact\:statusValueType" />
5194 </extension>
5195 </complexContent>
5196 </complexType>
5197 <!--
5198 End of schema.
5199 -->
5200 </schema>
5201 <CODE ENDS>
5202
5203 9.8. RDE Registrar Object
5204
5205 <CODE BEGINS>
5206 <?xml version="1.0" encoding="UTF-8"?>
5207 <schema targetNamespace="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
5208 xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
5209 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
5210 xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
5211 xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
5212 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
5213 xmlns="http://www.w3.org/2001/XMLSchema"
5214 elementFormDefault="qualified">
5215 <!-- Import common element types. -->
5216 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
5217 <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
5218 <import namespace="urn:ietf:params:xml:ns:contact-1.0" />
5219 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
5220 <annotation>
5221 <documentation>
5222 Registry Data Escrow registrar provisioning schema
5223 </documentation>
5224 </annotation>
5225 <element name="abstractRegistrar"
5226 type="rdeRegistrar:abstractContentType"
5227 substitutionGroup="rde:content"
5228 abstract="true" />
5229 <element name="registrar"
5230 substitutionGroup="rdeRegistrar:abstractRegistrar" />
5231 <element name="delete"
5232 type="rdeRegistrar:deleteType"
5233 substitutionGroup="rde:delete" />
5234 <!-- Content Type -->
5235 <complexType name="abstractContentType">
5236 <complexContent>
5237 <extension base="rde:contentType">
5238 <sequence>
5239 <element name="id"
5240 type="eppcom:clIDType" />
5241 <element name="name"
5242 type="rdeRegistrar:nameType" />
5243 <element name="gurid"
5244 type="positiveInteger"
5245 minOccurs="0" />
5246 <element name="status"
5247 type="rdeRegistrar:statusType"
5248 minOccurs="0" />
5249 <element name="postalInfo"
5250 type="rdeRegistrar:postalInfoType"
5251 minOccurs="0"
5252 maxOccurs="2" />
5253 <element name="voice"
5254 type="contact:e164Type"
5255 minOccurs="0" />
5256 <element name="fax"
5257 type="contact:e164Type"
5258 minOccurs="0" />
5259 <element name="email"
5260 type="eppcom:minTokenType"
5261 minOccurs="0" />
5262 <element name="url"
5263 type="anyURI"
5264 minOccurs="0" />
5265 <element name="whoisInfo"
5266 type="rdeRegistrar:whoisInfoType"
5267 minOccurs="0" />
5268 <element name="crDate"
5269 type="dateTime"
5270 minOccurs="0" />
5271 <element name="upDate"
5272 type="dateTime"
5273 minOccurs="0" />
5274 </sequence>
5275 </extension>
5276 </complexContent>
5277 </complexType>
5278 <simpleType name="nameType">
5279 <restriction base="normalizedString">
5280 <minLength value="1" />
5281 <maxLength value="255" />
5282 </restriction>
5283 </simpleType>
5284 <simpleType name="statusType">
5285 <restriction base="token">
5286 <enumeration value="ok" />
5287 <enumeration value="readonly" />
5288 <enumeration value="terminated" />
5289 </restriction>
5290 </simpleType>
5291 <complexType name="postalInfoType">
5292 <sequence>
5293 <element name="addr"
5294 type="rdeRegistrar:addrType" />
5295 </sequence>
5296 <attribute name="type"
5297 type="rdeRegistrar:postalInfoEnumType"
5298 use="required" />
5299 </complexType>
5300 <simpleType name="postalInfoEnumType">
5301 <restriction base="token">
5302 <enumeration value="loc" />
5303 <enumeration value="int" />
5304 </restriction>
5305 </simpleType>
5306 <complexType name="addrType">
5307 <sequence>
5308 <element name="street"
5309 type="rdeRegistrar:optPostalLineType"
5310 minOccurs="0"
5311 maxOccurs="3" />
5312 <element name="city"
5313 type="rdeRegistrar:postalLineType" />
5314 <element name="sp"
5315 type="rdeRegistrar:optPostalLineType"
5316 minOccurs="0" />
5317 <element name="pc"
5318 type="rdeRegistrar:pcType"
5319 minOccurs="0" />
5320 <element name="cc"
5321 type="rdeRegistrar:ccType" />
5322 </sequence>
5323 </complexType>
5324 <simpleType name="postalLineType">
5325 <restriction base="normalizedString">
5326 <minLength value="1" />
5327 <maxLength value="255" />
5328 </restriction>
5329 </simpleType>
5330 <simpleType name="optPostalLineType">
5331 <restriction base="normalizedString">
5332 <maxLength value="255" />
5333 </restriction>
5334 </simpleType>
5335 <simpleType name="pcType">
5336 <restriction base="token">
5337 <maxLength value="16" />
5338 </restriction>
5339 </simpleType>
5340 <simpleType name="ccType">
5341 <restriction base="token">
5342 <length value="2" />
5343 </restriction>
5344 </simpleType>
5345 <complexType name="whoisInfoType">
5346 <sequence>
5347 <element name="name"
5348 type="eppcom:labelType"
5349 minOccurs="0" />
5350 <element name="url"
5351 type="anyURI"
5352 minOccurs="0" />
5353 </sequence>
5354 </complexType>
5355 <!-- Delete Type -->
5356 <complexType name="deleteType">
5357 <complexContent>
5358 <extension base="rde:deleteType">
5359 <sequence>
5360 <element name="id"
5361 type="eppcom:clIDType"
5362 minOccurs="0"
5363 maxOccurs="unbounded" />
5364 </sequence>
5365 </extension>
5366 </complexContent>
5367 </complexType>
5368 </schema>
5369 <CODE ENDS>
5370
5371 9.9. CSV Registrar Object
5372
5373 <CODE BEGINS>
5374 <?xml version="1.0" encoding="UTF-8"?>
5375 <schema targetNamespace="urn:ietf:params:xml:ns:csvRegistrar-1.0"
5376 xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0"
5377 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
5378 xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
5379 xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
5380 xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
5381 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
5382 xmlns="http://www.w3.org/2001/XMLSchema"
5383 elementFormDefault="qualified">
5384 <!--
5385 Import common element types.
5386 -->
5387 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
5388 <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
5389 <import namespace="urn:ietf:params:xml:ns:contact-1.0" />
5390 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
5391 <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
5392 <annotation>
5393 <documentation>
5394 Registrar Comma-Separated Values (CSV) Object
5395 </documentation>
5396 </annotation>
5397 <!--
5398 Child elements of the <rde:contents> object
5399 -->
5400 <element name="contents"
5401 type="csvRegistrar:contentType"
5402 substitutionGroup="rde:content" />
5403 <complexType name="contentType">
5404 <complexContent>
5405 <extension base="rde:contentType">
5406 <sequence>
5407 <element ref="rdeCsv:csv"
5408 maxOccurs="unbounded" />
5409 </sequence>
5410 </extension>
5411 </complexContent>
5412 </complexType>
5413 <!--
5414 Child elements of the <rde:deletes> object
5415 -->
5416 <element name="deletes"
5417 type="csvRegistrar:deleteType"
5418 substitutionGroup="rde:delete" />
5419 <complexType name="deleteType">
5420 <complexContent>
5421 <extension base="rde:deleteType">
5422 <sequence>
5423 <element ref="rdeCsv:csv"
5424 maxOccurs="unbounded" />
5425 </sequence>
5426 </extension>
5427 </complexContent>
5428 </complexType>
5429 <!-- Registrar unique identifier (short name / id) -->
5430 <element name="fId"
5431 type="rdeCsv:fClIDRequiredType"
5432 substitutionGroup="rdeCsv:field" />
5433 <!-- Registrar name (full name) -->
5434 <element name="fName"
5435 type="csvRegistrar:fNameType"
5436 substitutionGroup="rdeCsv:field" />
5437 <!-- Registrar name field -->
5438 <complexType name="fNameType">
5439 <complexContent>
5440 <extension base="rdeCsv:fieldRequiredType">
5441 <sequence />
5442 <attribute name="type"
5443 type="token"
5444 default="normalizedString" />
5445 <attribute name="isLoc"
5446 type="boolean"
5447 default="false" />
5448 </extension>
5449 </complexContent>
5450 </complexType>
5451 <!-- Registrar GURID field -->
5452 <element name="fGurid"
5453 type="rdeCsv:fPositiveIntegerType"
5454 substitutionGroup="rdeCsv:field" />
5455 <!-- Registrar status field -->
5456 <element name="fStatus"
5457 type="csvRegistrar:fStatusType"
5458 substitutionGroup="rdeCsv:field" />
5459 <element name="fStatusName"
5460 type="rdeCsv:fTokenType"
5461 substitutionGroup="rdeCsv:field" />
5462 <complexType name="fStatusType">
5463 <complexContent>
5464 <extension base="rdeCsv:fieldOptionalType">
5465 <sequence />
5466 <attribute name="type"
5467 type="token"
5468 default="csvRegistrar\:statusType" />
5469 </extension>
5470 </complexContent>
5471 </complexType>
5472 <!-- Registrar status type with optional name attr -->
5473 <complexType name="statusType">
5474 <simpleContent>
5475 <extension base="csvRegistrar:statusValueType">
5476 <attribute name="name"
5477 type="token" />
5478 </extension>
5479 </simpleContent>
5480 </complexType>
5481 <!-- Registrar status enumerated values -->
5482 <simpleType name="statusValueType">
5483 <restriction base="token">
5484 <enumeration value="ok" />
5485 <enumeration value="readonly" />
5486 <enumeration value="terminated" />
5487 </restriction>
5488 </simpleType>
5489 <!-- Whois URL field -->
5490 <element name="fWhoisUrl"
5491 type="rdeCsv:anyURIType"
5492 substitutionGroup="rdeCsv:field" />
5493 <!--
5494 End of schema.
5495 -->
5496 </schema>
5497 <CODE ENDS>
5498
5499 9.10. RDE IDN Table Reference Objects
5500
5501 <CODE BEGINS>
5502 <?xml version="1.0" encoding="UTF-8"?>
5503 <schema targetNamespace="urn:ietf:params:xml:ns:rdeIDN-1.0"
5504 xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
5505 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
5506 xmlns="http://www.w3.org/2001/XMLSchema"
5507 elementFormDefault="qualified">
5508 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
5509 <annotation>
5510 <documentation>
5511 Registry Data Escrow IDN provisioning schema
5512 </documentation>
5513 </annotation>
5514 <element name="idnTableRef"
5515 type="rdeIDN:contentType"
5516 substitutionGroup="rde:content" />
5517 <element name="delete"
5518 type="rdeIDN:deleteType"
5519 substitutionGroup="rde:delete" />
5520 <!-- Content Types -->
5521 <complexType name="contentType">
5522 <complexContent>
5523 <extension base="rde:contentType">
5524 <sequence>
5525 <element name="url"
5526 type="anyURI" />
5527 <element name="urlPolicy"
5528 type="anyURI" />
5529 </sequence>
5530 <attribute name="id"
5531 type="rdeIDN:idType"
5532 use="required" />
5533 </extension>
5534 </complexContent>
5535 </complexType>
5536 <complexType name="deleteType">
5537 <complexContent>
5538 <extension base="rde:deleteType">
5539 <sequence>
5540 <element name="id"
5541 type="rdeIDN:idType" />
5542 </sequence>
5543 </extension>
5544 </complexContent>
5545 </complexType>
5546 <!-- Simple Types -->
5547 <simpleType name="idType">
5548 <restriction base="token">
5549 <minLength value="1" />
5550 <maxLength value="64" />
5551 </restriction>
5552 </simpleType>
5553 </schema>
5554 <CODE ENDS>
5555
5556 9.11. CSV IDN Language Object
5557
5558 <CODE BEGINS>
5559 <?xml version="1.0" encoding="UTF-8"?>
5560 <schema targetNamespace="urn:ietf:params:xml:ns:csvIDN-1.0"
5561 xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0"
5562 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
5563 xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
5564 xmlns="http://www.w3.org/2001/XMLSchema"
5565 elementFormDefault="qualified">
5566 <!--
5567 Import common element types
5568 -->
5569 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
5570 <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
5571 <annotation>
5572 <documentation>
5573 IDN Language Comma-Separated Values (CSV) Object
5574 </documentation>
5575 </annotation>
5576 <!--
5577 Child elements of the <rde:contents> object
5578 -->
5579 <element name="contents"
5580 type="csvIDN:contentType"
5581 substitutionGroup="rde:content" />
5582 <complexType name="contentType">
5583 <complexContent>
5584 <extension base="rde:contentType">
5585 <sequence>
5586 <element ref="rdeCsv:csv"
5587 maxOccurs="unbounded" />
5588 </sequence>
5589 </extension>
5590 </complexContent>
5591 </complexType>
5592 <!--
5593 Child elements of the <rde:deletes> object
5594 -->
5595 <element name="deletes"
5596 type="csvIDN:deleteType"
5597 substitutionGroup="rde:delete" />
5598 <complexType name="deleteType">
5599 <complexContent>
5600 <extension base="rde:deleteType">
5601 <sequence>
5602 <element ref="rdeCsv:csv"
5603 maxOccurs="unbounded" />
5604 </sequence>
5605 </extension>
5606 </complexContent>
5607 </complexType>
5608 <!--
5609 End of schema.
5610 -->
5611 </schema>
5612 <CODE ENDS>
5613
5614 9.12. EPP Parameters Object
5615
5616 <CODE BEGINS>
5617 <?xml version="1.0" encoding="UTF-8"?>
5618 <schema targetNamespace="urn:ietf:params:xml:ns:rdeEppParams-1.0"
5619 xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
5620 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
5621 xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
5622 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
5623 xmlns="http://www.w3.org/2001/XMLSchema"
5624 elementFormDefault="qualified">
5625 <import namespace="urn:ietf:params:xml:ns:epp-1.0" />
5626 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
5627 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
5628 <annotation>
5629 <documentation>
5630 Registry Data Escrow EPP Parameters schema
5631 </documentation>
5632 </annotation>
5633 <!-- Content Type -->
5634 <element name="eppParams"
5635 substitutionGroup="rdeEppParams:abstractEppParams" />
5636 <!-- Abstract Content Type -->
5637 <element name="abstractEppParams"
5638 type="rdeEppParams:abstractContentType"
5639 substitutionGroup="rde:content"
5640 abstract="true" />
5641 <complexType name="abstractContentType">
5642 <complexContent>
5643 <extension base="rde:contentType">
5644 <sequence>
5645 <element name="version"
5646 type="epp:versionType"
5647 maxOccurs="unbounded" />
5648 <element name="lang"
5649 type="language"
5650 maxOccurs="unbounded" />
5651 <element name="objURI"
5652 type="anyURI"
5653 maxOccurs="unbounded" />
5654 <element name="svcExtension"
5655 type="epp:extURIType"
5656 minOccurs="0" />
5657 <element name="dcp"
5658 type="epp:dcpType" />
5659 </sequence>
5660 </extension>
5661 </complexContent>
5662 </complexType>
5663 </schema>
5664 <CODE ENDS>
5665
5666 9.13. NNDN Object
5667
5668 <CODE BEGINS>
5669 <?xml version="1.0" encoding="UTF-8"?>
5670 <schema targetNamespace="urn:ietf:params:xml:ns:rdeNNDN-1.0"
5671 xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
5672 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
5673 xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
5674 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
5675 xmlns="http://www.w3.org/2001/XMLSchema"
5676 elementFormDefault="qualified">
5677 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
5678 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
5679 <import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0" />
5680 <annotation>
5681 <documentation>
5682 Registry Data Escrow NNDN provisioning schema
5683 </documentation>
5684 </annotation>
5685 <element name="abstractNNDN"
5686 type="rdeNNDN:abstractContentType"
5687 substitutionGroup="rde:content"
5688 abstract="true" />
5689 <element name="NNDN"
5690 substitutionGroup="rdeNNDN:abstractNNDN" />
5691 <element name="delete"
5692 type="rdeNNDN:deleteType"
5693 substitutionGroup="rde:delete" />
5694 <!-- Content Type -->
5695 <complexType name="abstractContentType">
5696 <complexContent>
5697 <extension base="rde:contentType">
5698 <sequence>
5699 <element name="aName"
5700 type="eppcom:labelType" />
5701 <element name="uName"
5702 type="eppcom:labelType"
5703 minOccurs="0" />
5704 <element name="idnTableId"
5705 type="rdeIDN:idType"
5706 minOccurs="0" />
5707 <element name="originalName"
5708 type="eppcom:labelType"
5709 minOccurs="0" />
5710 <element name="nameState"
5711 type="rdeNNDN:nameState" />
5712 <element name="crDate"
5713 type="dateTime"
5714 minOccurs="0" />
5715 </sequence>
5716 </extension>
5717 </complexContent>
5718 </complexType>
5719 <simpleType name="nameStateValue">
5720 <restriction base="token">
5721 <enumeration value="withheld" />
5722 <enumeration value="blocked" />
5723 <enumeration value="mirrored" />
5724 </restriction>
5725 </simpleType>
5726 <complexType name="nameState">
5727 <simpleContent>
5728 <extension base="rdeNNDN:nameStateValue">
5729 <attribute name="mirroringNS"
5730 type="boolean"
5731 default="true" />
5732 </extension>
5733 </simpleContent>
5734 </complexType>
5735 <!-- Delete Type -->
5736 <complexType name="deleteType">
5737 <complexContent>
5738 <extension base="rde:deleteType">
5739 <sequence>
5740 <element name="aName"
5741 type="eppcom:labelType"
5742 minOccurs="0"
5743 maxOccurs="unbounded" />
5744 </sequence>
5745 </extension>
5746 </complexContent>
5747 </complexType>
5748 </schema>
5749 <CODE ENDS>
5750
5751 9.14. CSV NNDN Object
5752
5753 <CODE BEGINS>
5754 <?xml version="1.0" encoding="UTF-8"?>
5755 <schema targetNamespace="urn:ietf:params:xml:ns:csvNNDN-1.0"
5756 xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0"
5757 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
5758 xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
5759 xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
5760 xmlns="http://www.w3.org/2001/XMLSchema"
5761 elementFormDefault="qualified">
5762 <!--
5763 Import common element types
5764 -->
5765 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
5766 <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
5767 <import namespace="urn:ietf:params:xml:ns:rdeNNDN-1.0" />
5768 <annotation>
5769 <documentation>
5770 NNDN (NNDN's not domain name) (CSV) Object
5771 </documentation>
5772 </annotation>
5773 <!--
5774 Child elements of the <rde:contents> object
5775 -->
5776 <element name="contents"
5777 type="csvNNDN:contentType"
5778 substitutionGroup="rde:content" />
5779 <complexType name="contentType">
5780 <complexContent>
5781 <extension base="rde:contentType">
5782 <sequence>
5783 <element ref="rdeCsv:csv"
5784 maxOccurs="unbounded" />
5785 </sequence>
5786 </extension>
5787 </complexContent>
5788 </complexType>
5789 <!--
5790 Child elements of the <rde:deletes> object
5791 -->
5792 <element name="deletes"
5793 type="csvNNDN:deleteType"
5794 substitutionGroup="rde:delete" />
5795 <complexType name="deleteType">
5796 <complexContent>
5797 <extension base="rde:deleteType">
5798 <sequence>
5799 <element ref="rdeCsv:csv"
5800 maxOccurs="unbounded" />
5801 </sequence>
5802 </extension>
5803 </complexContent>
5804 </complexType>
5805 <!-- A-Label format name field -->
5806 <element name="fAName"
5807 type="rdeCsv:fNameRequiredType"
5808 substitutionGroup="rdeCsv:field" />
5809 <!-- domain name used to generate the IDN variant field -->
5810 <element name="fOriginalName"
5811 type="rdeCsv:fNameType"
5812 substitutionGroup="rdeCsv:field" />
5813 <!-- RGP status field -->
5814 <element name="fNameState"
5815 type="csvNNDN:fNameStateType"
5816 substitutionGroup="rdeCsv:field" />
5817 <complexType name="fNameStateType">
5818 <complexContent>
5819 <extension base="rdeCsv:fieldRequiredType">
5820 <sequence />
5821 <attribute name="type"
5822 type="token"
5823 default="rdeNNDN\:nameState" />
5824 </extension>
5825 </complexContent>
5826 </complexType>
5827 <!-- Mirroring uses NS mirror mechanism? -->
5828 <element name="fMirroringNS"
5829 type="rdeCsv:fBooleanType"
5830 substitutionGroup="rdeCsv:field" />
5831 <!--
5832 End of schema.
5833 -->
5834 </schema>
5835 <CODE ENDS>
5836
5837 9.15. Policy Object
5838
5839 <CODE BEGINS>
5840 <?xml version="1.0" encoding="UTF-8"?>
5841 <schema targetNamespace="urn:ietf:params:xml:ns:rdePolicy-1.0"
5842 xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0"
5843 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
5844 xmlns="http://www.w3.org/2001/XMLSchema"
5845 elementFormDefault="qualified">
5846 <annotation>
5847 <documentation>
5848 Registry Data Escrow Policy schema
5849 </documentation>
5850 </annotation>
5851 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
5852 <element name="policy"
5853 type="rdePolicy:policyType"
5854 substitutionGroup="rde:content" />
5855 <complexType name="policyType">
5856 <complexContent>
5857 <extension base="rde:contentType">
5858 <attribute name="scope"
5859 type="token"
5860 use="required" />
5861 <attribute name="element"
5862 type="anyURI"
5863 use="required" />
5864 </extension>
5865 </complexContent>
5866 </complexType>
5867 </schema>
5868 <CODE ENDS>
5869
5870 9.16. Header Object
5871
5872 <CODE BEGINS>
5873 <?xml version="1.0" encoding="UTF-8"?>
5874 <schema targetNamespace="urn:ietf:params:xml:ns:rdeHeader-1.0"
5875 xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
5876 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
5877 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
5878 xmlns="http://www.w3.org/2001/XMLSchema"
5879 elementFormDefault="qualified">
5880 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
5881 <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
5882 <annotation>
5883 <documentation>
5884 Data Escrow Deposit Header schema
5885 </documentation>
5886 </annotation>
5887 <!-- Root Element -->
5888 <element name="header"
5889 type="rdeHeader:contentType"
5890 substitutionGroup="rde:content" />
5891 <!-- Content Type -->
5892 <complexType name="contentType">
5893 <complexContent>
5894 <extension base="rde:contentType">
5895 <sequence>
5896 <group ref="rdeHeader:repositoryTypeGroup" />
5897 <element name="count"
5898 type="rdeHeader:countType"
5899 maxOccurs="unbounded" />
5900 <element name="contentTag"
5901 type="token"
5902 minOccurs="0" />
5903 </sequence>
5904 </extension>
5905 </complexContent>
5906 </complexType>
5907 <group name="repositoryTypeGroup">
5908 <choice>
5909 <element name="tld"
5910 type="eppcom:labelType" />
5911 <element name="registrar"
5912 type="positiveInteger" />
5913 <element name="ppsp"
5914 type="token" />
5915 <element name="reseller"
5916 type="token" />
5917 </choice>
5918 </group>
5919 <complexType name="countType">
5920 <simpleContent>
5921 <extension base="long">
5922 <attribute name="uri"
5923 type="anyURI"
5924 use="required" />
5925 <attribute name="rcdn"
5926 type="eppcom:labelType" />
5927 <attribute name="registrarId"
5928 type="positiveInteger" />
5929 </extension>
5930 </simpleContent>
5931 </complexType>
5932 </schema>
5933 <CODE ENDS>
5934
5935 9.17. DNRD Common Objects
5936
5937 <CODE BEGINS>
5938 <?xml version="1.0" encoding="UTF-8"?>
5939 <schema targetNamespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
5940 xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
5941 xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
5942 xmlns="http://www.w3.org/2001/XMLSchema"
5943 elementFormDefault="qualified">
5944 <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
5945 <annotation>
5946 <documentation>
5947 Data Escrow Deposit Common Objects schema
5948 </documentation>
5949 </annotation>
5950 <complexType name="rrType">
5951 <simpleContent>
5952 <extension base="eppcom:clIDType">
5953 <attribute name="client"
5954 type="eppcom:clIDType" />
5955 </extension>
5956 </simpleContent>
5957 </complexType>
5958 </schema>
5959 <CODE ENDS>
5960
5961 10. Internationalization Considerations
5962
5963 Data escrow deposits are represented in XML, which provides native
5964 support for encoding information using the Unicode character set and
5965 its more compact representations including UTF-8. Conformant XML
5966 processors recognize both UTF-8 and UTF-16. Though XML includes
5967 provisions to identify and use other character encodings through use
5968 of an "encoding" attribute in an <?xml?> declaration, the use of
5969 UTF-8 is RECOMMENDED.
5970
5971 11. IANA Considerations
5972
5973 This document uses URNs to describe XML namespaces and XML schemas
5974 conforming to a registry mechanism described in [RFC3688]. The
5975 following URIs have been assigned by IANA.
5976
5977 RDE CSV namespace:
5978
5979 URI: urn:ietf:params:xml:ns:rdeCsv-1.0
5980 Registrant Contact: IESG
5981 XML: None. Namespace URIs do not represent an XML specification.
5982
5983 RDE CSV XML schema:
5984
5985 URI: urn:ietf:params:xml:schema:rdeCsv-1.0
5986 Registrant Contact: IESG
5987
5988 See Section 9.1 of this document.
5989
5990 RDE domain namespace:
5991
5992 URI: urn:ietf:params:xml:ns:rdeDomain-1.0
5993 Registrant Contact: IESG
5994 XML: None. Namespace URIs do not represent an XML specification.
5995
5996 RDE domain XML schema:
5997
5998 URI: urn:ietf:params:xml:schema:rdeDomain-1.0
5999 Registrant Contact: IESG
6000
6001 See Section 9.2 of this document.
6002
6003 CSV domain namespace:
6004
6005 URI: urn:ietf:params:xml:ns:csvDomain-1.0
6006 Registrant Contact: IESG
6007 XML: None. Namespace URIs do not represent an XML specification.
6008
6009 CSV domain XML schema:
6010
6011 URI: urn:ietf:params:xml:schema:csvDomain-1.0
6012 Registrant Contact: IESG
6013
6014 See Section 9.3 of this document.
6015
6016 RDE host namespace:
6017
6018 URI: urn:ietf:params:xml:ns:rdeHost-1.0
6019 Registrant Contact: IESG
6020 XML: None. Namespace URIs do not represent an XML specification.
6021
6022 RDE host XML schema:
6023
6024 URI: urn:ietf:params:xml:schema:rdeHost-1.0
6025 Registrant Contact: IESG
6026
6027 See Section 9.4 of this document.
6028
6029 CSV host namespace:
6030
6031 URI: urn:ietf:params:xml:ns:csvHost-1.0
6032 Registrant Contact: IESG
6033 XML: None. Namespace URIs do not represent an XML specification.
6034
6035 CSV host XML schema:
6036
6037 URI: urn:ietf:params:xml:schema:csvHost-1.0
6038 Registrant Contact: IESG
6039
6040 See Section 9.5 of this document.
6041
6042 RDE contact namespace:
6043
6044 URI: urn:ietf:params:xml:ns:rdeContact-1.0
6045 Registrant Contact: IESG
6046 XML: None. Namespace URIs do not represent an XML specification.
6047
6048 RDE contact XML schema:
6049
6050 URI: urn:ietf:params:xml:schema:rdeContact-1.0
6051 Registrant Contact: IESG
6052
6053 See Section 9.6 of this document.
6054
6055 CSV contact namespace:
6056
6057 URI: urn:ietf:params:xml:ns:csvContact-1.0
6058 Registrant Contact: IESG
6059 XML: None. Namespace URIs do not represent an XML specification.
6060
6061 CSV contact XML schema:
6062
6063 URI: urn:ietf:params:xml:schema:csvContact-1.0
6064 Registrant Contact: IESG
6065
6066 See Section 9.7 of this document.
6067
6068 RDE registrar namespace:
6069
6070 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0
6071 Registrant Contact: IESG
6072 XML: None. Namespace URIs do not represent an XML specification.
6073
6074 RDE registrar XML schema:
6075
6076 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0
6077 Registrant Contact: IESG
6078
6079 See Section 9.8 of this document.
6080
6081 CSV registrar namespace:
6082
6083 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0
6084 Registrant Contact: IESG
6085 XML: None. Namespace URIs do not represent an XML specification.
6086
6087 CSV registrar XML schema:
6088
6089 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0
6090 Registrant Contact: IESG
6091
6092 See Section 9.9 of this document.
6093
6094 RDE IDN namespace:
6095
6096 URI: urn:ietf:params:xml:ns:rdeIDN-1.0
6097 Registrant Contact: IESG
6098 XML: None. Namespace URIs do not represent an XML specification.
6099
6100 RDE IDN XML schema:
6101
6102 URI: urn:ietf:params:xml:schema:rdeIDN-1.0
6103 Registrant Contact: IESG
6104
6105 See Section 9.10 of this document.
6106
6107 CSV IDN namespace:
6108
6109 URI: urn:ietf:params:xml:ns:csvIDN-1.0
6110 Registrant Contact: IESG
6111 XML: None. Namespace URIs do not represent an XML specification.
6112
6113 CSV IDN XML schema:
6114
6115 URI: urn:ietf:params:xml:schema:csvIDN-1.0
6116 Registrant Contact: IESG
6117
6118 See Section 9.11 of this document.
6119
6120 RDE EPP parameters namespace:
6121
6122 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0
6123 Registrant Contact: IESG
6124 XML: None. Namespace URIs do not represent an XML specification.
6125
6126 RDE EPP parameters XML schema:
6127
6128 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0
6129 Registrant Contact: IESG
6130
6131 See Section 9.12 of this document.
6132
6133 RDE NNDN namespace:
6134
6135 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0
6136 Registrant Contact: IESG
6137 XML: None. Namespace URIs do not represent an XML specification.
6138
6139 RDE NNDN XML schema:
6140
6141 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0
6142 Registrant Contact: IESG
6143
6144 See Section 9.13 of this document.
6145
6146 CSV NNDN namespace:
6147
6148 URI: urn:ietf:params:xml:ns:csvNNDN-1.0
6149 Registrant Contact: IESG
6150 XML: None. Namespace URIs do not represent an XML specification.
6151
6152 CSV NNDN XML schema:
6153
6154 URI: urn:ietf:params:xml:schema:csvNNDN-1.0
6155 Registrant Contact: IESG
6156
6157 See Section 9.14 of this document.
6158
6159 RDE Policy namespace:
6160
6161 URI: urn:ietf:params:xml:ns:rdePolicy-1.0
6162 Registrant Contact: IESG
6163 XML: None. Namespace URIs do not represent an XML specification.
6164
6165 RDE Policy XML schema:
6166
6167 URI: urn:ietf:params:xml:schema:rdePolicy-1.0
6168 Registrant Contact: IESG
6169
6170 See Section 9.15 of this document.
6171
6172 RDE Header namespace:
6173
6174 URI: urn:ietf:params:xml:ns:rdeHeader-1.0
6175 Registrant Contact: IESG
6176 XML: None. Namespace URIs do not represent an XML specification.
6177
6178 RDE Header XML schema:
6179
6180 URI: urn:ietf:params:xml:schema:rdeHeader-1.0
6181 Registrant Contact: IESG
6182
6183 See Section 9.16 of this document.
6184
6185 RDE Common Objects namespace:
6186
6187 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0
6188 Registrant Contact: IESG
6189 XML: None. Namespace URIs do not represent an XML specification.
6190
6191 RDE Common Objects XML schema:
6192
6193 URI: urn:ietf:params:xml:schema:rdeDnrdCommon-1.0
6194 Registrant Contact: IESG
6195
6196 See Section 9.17 of this document.
6197
6198 12. Security Considerations
6199
6200 This specification does not define the security mechanisms to be used
6201 in the transmission of the data escrow deposits, since it only
6202 specifies the minimum necessary to enable the rebuilding of a
6203 registry from deposits without intervention from the original
6204 registry.
6205
6206 Depending on local policies, some elements, or, most likely, the
6207 whole deposit will be considered confidential. As such, the parties
6208 SHOULD take all the necessary precautions such as encrypting the data
6209 at rest and in transit to avoid inadvertent disclosure of private
6210 data. Regardless of the precautions taken by the parties regarding
6211 data at rest and in transit, authentication credentials MUST NOT be
6212 escrowed.
6213
6214 Authentication of the parties passing data escrow deposit files is
6215 also of the utmost importance. The escrow agent MUST properly
6216 authenticate the registry's identity before accepting data escrow
6217 deposits. The registry MUST authenticate the escrow agent's identity
6218 before submitting any data, and the data escrow agent MUST
6219 authenticate the identity of the party receiving the data escrow
6220 deposits for the purposes deemed appropriate.
6221
6222 Additionally, the registry and the escrow agent MUST use integrity
6223 checking mechanisms to ensure the data transmitted is what the source
6224 intended. Validation of the contents by the parties is RECOMMENDED
6225 to ensure that the file was transmitted correctly from the registry
6226 or escrow agent and that the contents are "meaningful".
6227
6228 A few elements in this specification contain URLs; the use of HTTP
6229 over TLS (Transport Layer Security) [RFC2818] is RECOMMENDED on the
6230 URLs.
6231
6232 The various data structures in the document include a few places that
6233 have internal redundancy, and if the values become inconsistent there
6234 can be harmful consequences, such as different entities using
6235 different fields as their reference.
6236
6237 | Note: if TLS is used when providing an escrow service, the
6238 | recommendations in [BCP195] MUST be implemented.
6239
6240 13. Privacy Considerations
6241
6242 This specification defines a format that may be used to escrow
6243 personal data. The process of data escrow is governed by a legal
6244 document that is agreed to by the parties, and such a legal document
6245 must ensure that privacy-sensitive and/or personal data receives the
6246 required protection.
6247
6248 14. Example of a Full Deposit Using the XML Model
6249
6250 The following is an example of a Full Deposit using the XML model:
6251
6252 <?xml version="1.0" encoding="UTF-8"?>
6253 <rde:deposit type="FULL" id="20191017001"
6254 xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
6255 xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
6256 xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
6257 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
6258 xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
6259 xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
6260 xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
6261 xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
6262 xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
6263 xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
6264 xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
6265 xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
6266 xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0"
6267 xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
6268
6269 <rde:watermark>2019-10-17T00:00:00Z</rde:watermark>
6270 <rde:rdeMenu>
6271 <rde:version>1.0</rde:version>
6272 <rde:objURI>urn:ietf:params:xml:ns:rdeHeader-1.0
6273 </rde:objURI>
6274 <rde:objURI>urn:ietf:params:xml:ns:rdeContact-1.0
6275 </rde:objURI>
6276 <rde:objURI>urn:ietf:params:xml:ns:rdeHost-1.0
6277 </rde:objURI>
6278 <rde:objURI>urn:ietf:params:xml:ns:rdeDomain-1.0
6279 </rde:objURI>
6280 <rde:objURI>urn:ietf:params:xml:ns:rdeRegistrar-1.0
6281 </rde:objURI>
6282 <rde:objURI>urn:ietf:params:xml:ns:rdeIDN-1.0
6283 </rde:objURI>
6284 <rde:objURI>urn:ietf:params:xml:ns:rdeNNDN-1.0
6285 </rde:objURI>
6286 <rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0
6287 </rde:objURI>
6288 </rde:rdeMenu>
6289
6290 <!-- Contents -->
6291 <rde:contents>
6292 <!-- Header -->
6293 <rdeHeader:header>
6294 <rdeHeader:tld>test</rdeHeader:tld>
6295 <rdeHeader:count
6296 uri="urn:ietf:params:xml:ns:rdeDomain-1.0">2
6297 </rdeHeader:count>
6298 <rdeHeader:count
6299 uri="urn:ietf:params:xml:ns:rdeHost-1.0">1
6300 </rdeHeader:count>
6301 <rdeHeader:count
6302 uri="urn:ietf:params:xml:ns:rdeContact-1.0">1
6303 </rdeHeader:count>
6304 <rdeHeader:count
6305 uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1
6306 </rdeHeader:count>
6307 <rdeHeader:count
6308 uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1
6309 </rdeHeader:count>
6310 <rdeHeader:count
6311 uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1
6312 </rdeHeader:count>
6313 <rdeHeader:count
6314 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
6315 </rdeHeader:count>
6316 </rdeHeader:header>
6317
6318 <!-- Domain: example1.example -->
6319 <rdeDomain:domain>
6320 <rdeDomain:name>example1.example</rdeDomain:name>
6321 <rdeDomain:roid>Dexample1-TEST</rdeDomain:roid>
6322 <rdeDomain:status s="ok"/>
6323 <rdeDomain:registrant>jd1234</rdeDomain:registrant>
6324 <rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
6325 <rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
6326 <rdeDomain:ns>
6327 <domain:hostObj>ns1.example.com</domain:hostObj>
6328 <domain:hostObj>ns1.example1.example</domain:hostObj>
6329 </rdeDomain:ns>
6330 <rdeDomain:clID>RegistrarX</rdeDomain:clID>
6331 <rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr>
6332 <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
6333 <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate>
6334 </rdeDomain:domain>
6335
6336 <!-- Domain: example2.example -->
6337 <rdeDomain:domain>
6338 <rdeDomain:name>example2.example</rdeDomain:name>
6339 <rdeDomain:roid>Dexample2-TEST</rdeDomain:roid>
6340 <rdeDomain:status s="ok"/>
6341 <rdeDomain:status s="clientUpdateProhibited"/>
6342 <rdeDomain:registrant>jd1234</rdeDomain:registrant>
6343 <rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
6344 <rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
6345 <rdeDomain:clID>RegistrarX</rdeDomain:clID>
6346 <rdeDomain:crRr>RegistrarX</rdeDomain:crRr>
6347 <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
6348 <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate>
6349 </rdeDomain:domain>
6350
6351 <!-- Host: ns1.example.example -->
6352 <rdeHost:host>
6353 <rdeHost:name>ns1.example1.example</rdeHost:name>
6354 <rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid>
6355 <rdeHost:status s="ok"/>
6356 <rdeHost:status s="linked"/>
6357 <rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr>
6358 <rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr>
6359 <rdeHost:addr ip="v6">2001:DB8:1::1</rdeHost:addr>
6360 <rdeHost:clID>RegistrarX</rdeHost:clID>
6361 <rdeHost:crRr>RegistrarX</rdeHost:crRr>
6362 <rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate>
6363 <rdeHost:upRr>RegistrarX</rdeHost:upRr>
6364 <rdeHost:upDate>2009-10-03T09:34:00.0Z</rdeHost:upDate>
6365 </rdeHost:host>
6366
6367 <!-- Contact: sh8013 -->
6368 <rdeContact:contact>
6369 <rdeContact:id>sh8013</rdeContact:id>
6370 <rdeContact:roid>Csh8013-TEST</rdeContact:roid>
6371 <rdeContact:status s="linked"/>
6372 <rdeContact:status s="clientDeleteProhibited"/>
6373 <rdeContact:postalInfo type="int">
6374 <contact:name>John Doe</contact:name>
6375 <contact:org>Example Inc.</contact:org>
6376 <contact:addr>
6377 <contact:street>123 Example Dr.</contact:street>
6378 <contact:street>Suite 100</contact:street>
6379 <contact:city>Dulles</contact:city>
6380 <contact:sp>VA</contact:sp>
6381 <contact:pc>20166-6503</contact:pc>
6382 <contact:cc>US</contact:cc>
6383 </contact:addr>
6384 </rdeContact:postalInfo>
6385 <rdeContact:voice x="1234">+1.7035555555
6386 </rdeContact:voice>
6387 <rdeContact:fax>+1.7035555556
6388 </rdeContact:fax>
6389 <rdeContact:email>jdoe@example.example
6390 </rdeContact:email>
6391 <rdeContact:clID>RegistrarX</rdeContact:clID>
6392 <rdeContact:crRr client="jdoe">RegistrarX
6393 </rdeContact:crRr>
6394 <rdeContact:crDate>2009-09-13T08:01:00.0Z
6395 </rdeContact:crDate>
6396 <rdeContact:upRr client="jdoe">RegistrarX
6397 </rdeContact:upRr>
6398 <rdeContact:upDate>2009-11-26T09:10:00.0Z
6399 </rdeContact:upDate>
6400 <rdeContact:trDate>2009-12-03T09:05:00.0Z
6401 </rdeContact:trDate>
6402 <rdeContact:disclose flag="0">
6403 <contact:voice/>
6404 <contact:email/>
6405 </rdeContact:disclose>
6406 </rdeContact:contact>
6407
6408 <!-- Registrar: RegistrarX -->
6409 <rdeRegistrar:registrar>
6410 <rdeRegistrar:id>RegistrarX</rdeRegistrar:id>
6411 <rdeRegistrar:name>Registrar X</rdeRegistrar:name>
6412 <rdeRegistrar:gurid>8</rdeRegistrar:gurid>
6413 <rdeRegistrar:status>ok</rdeRegistrar:status>
6414 <rdeRegistrar:postalInfo type="int">
6415 <rdeRegistrar:addr>
6416 <rdeRegistrar:street>123 Example Dr.
6417 </rdeRegistrar:street>
6418 <rdeRegistrar:street>Suite 100
6419 </rdeRegistrar:street>
6420 <rdeRegistrar:city>Dulles</rdeRegistrar:city>
6421 <rdeRegistrar:sp>VA</rdeRegistrar:sp>
6422 <rdeRegistrar:pc>20166-6503</rdeRegistrar:pc>
6423 <rdeRegistrar:cc>US</rdeRegistrar:cc>
6424 </rdeRegistrar:addr>
6425 </rdeRegistrar:postalInfo>
6426 <rdeRegistrar:voice x="1234">+1.7035555555
6427 </rdeRegistrar:voice>
6428 <rdeRegistrar:fax>+1.7035555556
6429 </rdeRegistrar:fax>
6430 <rdeRegistrar:email>jdoe@example.example
6431 </rdeRegistrar:email>
6432 <rdeRegistrar:url>http://www.example.example
6433 </rdeRegistrar:url>
6434 <rdeRegistrar:whoisInfo>
6435 <rdeRegistrar:name>whois.example.example
6436 </rdeRegistrar:name>
6437 <rdeRegistrar:url>http://whois.example.example
6438 </rdeRegistrar:url>
6439 </rdeRegistrar:whoisInfo>
6440 <rdeRegistrar:crDate>2005-04-23T11:49:00.0Z
6441 </rdeRegistrar:crDate>
6442 <rdeRegistrar:upDate>2009-02-17T17:51:00.0Z
6443 </rdeRegistrar:upDate>
6444 </rdeRegistrar:registrar>
6445
6446 <!-- IDN Table -->
6447 <rdeIDN:idnTableRef id="pt-BR">
6448 <rdeIDN:url>
6449 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html
6450 </rdeIDN:url>
6451 <rdeIDN:urlPolicy>
6452 http://registro.br/dominio/regras.html
6453 </rdeIDN:urlPolicy>
6454 </rdeIDN:idnTableRef>
6455
6456 <!-- NNDN: pinguino.example -->
6457 <rdeNNDN:NNDN>
6458 <rdeNNDN:aName>xn--exampl-gva.example</rdeNNDN:aName>
6459 <rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId>
6460 <rdeNNDN:originalName>example1.example</rdeNNDN:originalName>
6461 <rdeNNDN:nameState>withheld</rdeNNDN:nameState>
6462 <rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate>
6463 </rdeNNDN:NNDN>
6464
6465 <!-- EppParams -->
6466 <rdeEppParams:eppParams>
6467 <rdeEppParams:version>1.0</rdeEppParams:version>
6468 <rdeEppParams:lang>en</rdeEppParams:lang>
6469 <rdeEppParams:objURI>
6470 urn:ietf:params:xml:ns:domain-1.0
6471 </rdeEppParams:objURI>
6472 <rdeEppParams:objURI>
6473 urn:ietf:params:xml:ns:contact-1.0
6474 </rdeEppParams:objURI>
6475 <rdeEppParams:objURI>
6476 urn:ietf:params:xml:ns:host-1.0
6477 </rdeEppParams:objURI>
6478 <rdeEppParams:svcExtension>
6479 <epp:extURI>urn:ietf:params:xml:ns:rgp-1.0
6480 </epp:extURI>
6481 <epp:extURI>urn:ietf:params:xml:ns:secDNS-1.1
6482 </epp:extURI>
6483 </rdeEppParams:svcExtension>
6484 <rdeEppParams:dcp>
6485 <epp:access><epp:all/></epp:access>
6486 <epp:statement>
6487 <epp:purpose>
6488 <epp:admin/>
6489 <epp:prov/>
6490 </epp:purpose>
6491 <epp:recipient>
6492 <epp:ours/>
6493 <epp:public/>
6494 </epp:recipient>
6495 <epp:retention>
6496 <epp:stated/>
6497 </epp:retention>
6498 </epp:statement>
6499 </rdeEppParams:dcp>
6500 </rdeEppParams:eppParams>
6501 <rdePolicy:policy
6502 scope="//rde:deposit/rde:contents/rdeDomain:domain"
6503 element="rdeDomain:registrant" />
6504 </rde:contents>
6505 </rde:deposit>
6506
6507 15. Example of a Differential Deposit Using the XML Model
6508
6509 The following is an example of a Differential Deposit using the XML
6510 model:
6511
6512 <?xml version="1.0" encoding="UTF-8"?>
6513 <rde:deposit type="DIFF" id="20191017002" prevId="20191017001"
6514 xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
6515 xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
6516 xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
6517 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
6518 xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
6519 xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
6520 xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
6521 xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
6522 xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
6523 xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
6524 xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
6525 xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
6526 xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
6527
6528 <rde:watermark>2019-10-17T00:00:00Z</rde:watermark>
6529 <rde:rdeMenu>
6530 <rde:version>1.0</rde:version>
6531 <rde:objURI>urn:ietf:params:xml:ns:rdeHeader-1.0
6532 </rde:objURI>
6533 <rde:objURI>urn:ietf:params:xml:ns:rdeContact-1.0
6534 </rde:objURI>
6535 <rde:objURI>urn:ietf:params:xml:ns:rdeHost-1.0
6536 </rde:objURI>
6537 <rde:objURI>urn:ietf:params:xml:ns:rdeDomain-1.0
6538 </rde:objURI>
6539 <rde:objURI>urn:ietf:params:xml:ns:rdeRegistrar-1.0
6540 </rde:objURI>
6541 <rde:objURI>urn:ietf:params:xml:ns:rdeIDN-1.0
6542 </rde:objURI>
6543 <rde:objURI>urn:ietf:params:xml:ns:rdeNNDN-1.0
6544 </rde:objURI>
6545 <rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0
6546 </rde:objURI>
6547 </rde:rdeMenu>
6548
6549 <!-- Deletes -->
6550 <rde:deletes>
6551 <rdeDomain:delete>
6552 <rdeDomain:name>example2.example</rdeDomain:name>
6553 </rdeDomain:delete>
6554 </rde:deletes>
6555
6556 <!-- Contents -->
6557 <rde:contents>
6558 <!-- Header -->
6559 <rdeHeader:header>
6560 <rdeHeader:tld>test</rdeHeader:tld>
6561 <rdeHeader:count
6562 uri="urn:ietf:params:xml:ns:rdeDomain-1.0">1
6563 </rdeHeader:count>
6564 <rdeHeader:count
6565 uri="urn:ietf:params:xml:ns:rdeHost-1.0">1
6566 </rdeHeader:count>
6567 <rdeHeader:count
6568 uri="urn:ietf:params:xml:ns:rdeContact-1.0">1
6569 </rdeHeader:count>
6570 <rdeHeader:count
6571 uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1
6572 </rdeHeader:count>
6573 <rdeHeader:count
6574 uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1
6575 </rdeHeader:count>
6576 <rdeHeader:count
6577 uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1
6578 </rdeHeader:count>
6579 <rdeHeader:count
6580 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
6581 </rdeHeader:count>
6582 </rdeHeader:header>
6583 </rde:contents>
6584 </rde:deposit>
6585
6586 16. Example of a Full Deposit Using the CSV Model
6587
6588 The following is an example of a Full Deposit using the CSV model:
6589
6590 <?xml version="1.0" encoding="UTF-8"?>
6591 <rde:deposit
6592 xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
6593 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
6594 xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
6595 xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
6596 xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
6597 xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0"
6598 xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0"
6599 xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0"
6600 xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
6601 xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0"
6602 xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
6603 type="FULL"
6604 id="20191017001">
6605 <rde:watermark>2019-10-18T00:00:00Z</rde:watermark>
6606 <rde:rdeMenu>
6607 <rde:version>1.0</rde:version>
6608 <rde:objURI>urn:ietf:params:xml:ns:csvDomain-1.0</rde:objURI>
6609 <rde:objURI>urn:ietf:params:xml:ns:csvHost-1.0</rde:objURI>
6610 <rde:objURI>urn:ietf:params:xml:ns:csvContact-1.0</rde:objURI>
6611 <rde:objURI>urn:ietf:params:xml:ns:csvRegistrar-1.0</rde:objURI>
6612 <rde:objURI>urn:ietf:params:xml:ns:csvIDN-1.0</rde:objURI>
6613 <rde:objURI>urn:ietf:params:xml:ns:csvNNDN-1.0</rde:objURI>
6614 <rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0</rde:objURI>
6615 </rde:rdeMenu>
6616 <rde:contents>
6617 <rdeHeader:header>
6618 <rdeHeader:tld>test</rdeHeader:tld>
6619 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvDomain-1.0">
6620 4
6621 </rdeHeader:count>
6622 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvHost-1.0">
6623 6
6624 </rdeHeader:count>
6625 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvContact-1.0">
6626 9
6627 </rdeHeader:count>
6628 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvRegistrar-1.0">
6629 3
6630 </rdeHeader:count>
6631 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvIDN-1.0">
6632 2
6633 </rdeHeader:count>
6634 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvNNDN-1.0">
6635 2
6636 </rdeHeader:count>
6637 <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">
6638 1
6639 </rdeHeader:count>
6640 </rdeHeader:header>
6641 <csvDomain:contents>
6642 <rdeCsv:csv name="domain" sep=",">
6643 <rdeCsv:fields>
6644 <csvDomain:fName/>
6645 <rdeCsv:fRoid/>
6646 <rdeCsv:fIdnTableId/>
6647 <csvDomain:fOriginalName/>
6648 <rdeCsv:fRegistrant/>
6649 <rdeCsv:fClID/>
6650 <rdeCsv:fCrRr/>
6651 <rdeCsv:fCrID/>
6652 <rdeCsv:fCrDate/>
6653 <rdeCsv:fUpRr/>
6654 <rdeCsv:fUpID/>
6655 <rdeCsv:fUpDate/>
6656 <rdeCsv:fExDate isRequired="true"/>
6657 </rdeCsv:fields>
6658 <rdeCsv:files>
6659 <rdeCsv:file
6660 cksum="75E2D01F">
6661 domain-YYYYMMDD.csv
6662 </rdeCsv:file>
6663 </rdeCsv:files>
6664 </rdeCsv:csv>
6665 <rdeCsv:csv name="domainContacts" sep=",">
6666 <rdeCsv:fields>
6667 <csvDomain:fName parent="true"/>
6668 <csvContact:fId/>
6669 <csvDomain:fContactType/>
6670 </rdeCsv:fields>
6671 <rdeCsv:files>
6672 <rdeCsv:file
6673 cksum="70A7C17B">
6674 domainContacts-YYYYMMDD.csv
6675 </rdeCsv:file>
6676 </rdeCsv:files>
6677 </rdeCsv:csv>
6678 <rdeCsv:csv name="domainStatuses" sep=",">
6679 <rdeCsv:fields>
6680 <csvDomain:fName parent="true"/>
6681 <csvDomain:fStatus/>
6682 <rdeCsv:fStatusDescription/>
6683 <rdeCsv:fLang/>
6684 <csvDomain:fRgpStatus/>
6685 </rdeCsv:fields>
6686 <rdeCsv:files>
6687 <rdeCsv:file
6688 cksum="EB8C548E">
6689 domainStatuses-YYYYMMDD.csv
6690 </rdeCsv:file>
6691 </rdeCsv:files>
6692 </rdeCsv:csv>
6693 <rdeCsv:csv name="domainNameServers" sep=",">
6694 <rdeCsv:fields>
6695 <csvDomain:fName parent="true"/>
6696 <csvHost:fName parent="true"/>
6697 </rdeCsv:fields>
6698 <rdeCsv:files>
6699 <rdeCsv:file
6700 cksum="984C3097">
6701 domainNameServers-name-YYYYMMDD.csv
6702 </rdeCsv:file>
6703 </rdeCsv:files>
6704 </rdeCsv:csv>
6705 <rdeCsv:csv name="domainNameServers" sep=",">
6706 <rdeCsv:fields>
6707 <csvDomain:fName parent="true"/>
6708 <rdeCsv:fRoid/>
6709 </rdeCsv:fields>
6710 <rdeCsv:files>
6711 <rdeCsv:file
6712 cksum="569D4638">
6713 domainNameServers-roid-YYYYMMDD.csv
6714 </rdeCsv:file>
6715 </rdeCsv:files>
6716 </rdeCsv:csv>
6717 <rdeCsv:csv name="dnssec" sep=",">
6718 <rdeCsv:fields>
6719 <csvDomain:fName parent="true"/>
6720 <csvDomain:fMaxSigLife/>
6721 <csvDomain:fKeyTag/>
6722 <csvDomain:fDsAlg/>
6723 <csvDomain:fDigestType/>
6724 <csvDomain:fDigest/>
6725 </rdeCsv:fields>
6726 <rdeCsv:files>
6727 <rdeCsv:file
6728 cksum="AA15CB43">
6729 dnssec-ds-YYYYMMDD.csv
6730 </rdeCsv:file>
6731 </rdeCsv:files>
6732 </rdeCsv:csv>
6733 <rdeCsv:csv name="dnssec" sep=",">
6734 <rdeCsv:fields>
6735 <csvDomain:fName parent="true"/>
6736 <csvDomain:fMaxSigLife/>
6737 <csvDomain:fFlags/>
6738 <csvDomain:fProtocol/>
6739 <csvDomain:fKeyAlg/>
6740 <csvDomain:fPubKey/>
6741 </rdeCsv:fields>
6742 <rdeCsv:files>
6743 <rdeCsv:file
6744 cksum="1B16F334">
6745 dnssec-key-YYYYMMDD.csv
6746 </rdeCsv:file>
6747 </rdeCsv:files>
6748 </rdeCsv:csv>
6749 <rdeCsv:csv name="domainTransfer" sep=",">
6750 <rdeCsv:fields>
6751 <csvDomain:fName parent="true"/>
6752 <rdeCsv:fTrStatus/>
6753 <rdeCsv:fReRr/>
6754 <rdeCsv:fReID/>
6755 <rdeCsv:fReDate/>
6756 <rdeCsv:fAcRr/>
6757 <rdeCsv:fAcID/>
6758 <rdeCsv:fAcDate/>
6759 <rdeCsv:fExDate/>
6760 </rdeCsv:fields>
6761 <rdeCsv:files>
6762 <rdeCsv:file
6763 cksum="71170194">
6764 domainTransfer-YYYYMMDD.csv
6765 </rdeCsv:file>
6766 </rdeCsv:files>
6767 </rdeCsv:csv>
6768 </csvDomain:contents>
6769 <csvHost:contents>
6770 <rdeCsv:csv name="host" sep=",">
6771 <rdeCsv:fields>
6772 <csvHost:fName/>
6773 <rdeCsv:fRoid/>
6774 <rdeCsv:fClID/>
6775 <rdeCsv:fCrRr/>
6776 <rdeCsv:fCrID/>
6777 <rdeCsv:fCrDate/>
6778 <rdeCsv:fUpRr/>
6779 <rdeCsv:fUpID/>
6780 <rdeCsv:fUpDate/>
6781 <rdeCsv:fTrDate/>
6782 </rdeCsv:fields>
6783 <rdeCsv:files>
6784 <rdeCsv:file
6785 cksum="120938E3">
6786 host-YYYYMMDD.csv
6787 </rdeCsv:file>
6788 </rdeCsv:files>
6789 </rdeCsv:csv>
6790 <rdeCsv:csv name="hostStatuses" sep=",">
6791 <rdeCsv:fields>
6792 <rdeCsv:fRoid parent="true"/>
6793 <csvHost:fStatus/>
6794 <rdeCsv:fStatusDescription/>
6795 <rdeCsv:fLang/>
6796 </rdeCsv:fields>
6797 <rdeCsv:files>
6798 <rdeCsv:file
6799 cksum="0BA504FC">
6800 hostStatuses-YYYYMMDD.csv
6801 </rdeCsv:file>
6802 </rdeCsv:files>
6803 </rdeCsv:csv>
6804 <rdeCsv:csv name="hostAddresses" sep=",">
6805 <rdeCsv:fields>
6806 <rdeCsv:fRoid parent="true"/>
6807 <csvHost:fAddr isRequired="true"/>
6808 <csvHost:fAddrVersion isRequired="true"/>
6809 </rdeCsv:fields>
6810 <rdeCsv:files>
6811 <rdeCsv:file
6812 cksum="17888F02">
6813 hostAddresses-YYYYMMDD.csv
6814 </rdeCsv:file>
6815 </rdeCsv:files>
6816 </rdeCsv:csv>
6817 </csvHost:contents>
6818 <csvContact:contents>
6819 <rdeCsv:csv name="contact" sep=",">
6820 <rdeCsv:fields>
6821 <csvContact:fId/>
6822 <rdeCsv:fRoid/>
6823 <csvContact:fVoice/>
6824 <csvContact:fVoiceExt/>
6825 <csvContact:fFax/>
6826 <csvContact:fFaxExt/>
6827 <csvContact:fEmail/>
6828 <rdeCsv:fClID/>
6829 <rdeCsv:fCrRr/>
6830 <rdeCsv:fCrID/>
6831 <rdeCsv:fCrDate/>
6832 <rdeCsv:fUpRr/>
6833 <rdeCsv:fUpID/>
6834 <rdeCsv:fUpDate/>
6835 </rdeCsv:fields>
6836 <rdeCsv:files>
6837 <rdeCsv:file
6838 cksum="D7F106A5">
6839 contact-YYYYMMDD.csv
6840 </rdeCsv:file>
6841 </rdeCsv:files>
6842 </rdeCsv:csv>
6843 <rdeCsv:csv name="contactStatuses" sep=",">
6844 <rdeCsv:fields>
6845 <csvContact:fId parent="true"/>
6846 <csvContact:fStatus/>
6847 <rdeCsv:fStatusDescription/>
6848 <rdeCsv:fLang/>
6849 </rdeCsv:fields>
6850 <rdeCsv:files>
6851 <rdeCsv:file
6852 cksum="2AAF99D4">
6853 contactStatuses-YYYYMMDD.csv
6854 </rdeCsv:file>
6855 </rdeCsv:files>
6856 </rdeCsv:csv>
6857 <rdeCsv:csv name="contactPostal" sep=",">
6858 <rdeCsv:fields>
6859 <csvContact:fId parent="true"/>
6860 <csvContact:fPostalType/>
6861 <csvContact:fName/>
6862 <csvContact:fOrg/>
6863 <csvContact:fStreet index="0"/>
6864 <csvContact:fStreet index="1"/>
6865 <csvContact:fStreet index="2"/>
6866 <csvContact:fCity/>
6867 <csvContact:fSp/>
6868 <csvContact:fPc/>
6869 <csvContact:fCc/>
6870 </rdeCsv:fields>
6871 <rdeCsv:files>
6872 <rdeCsv:file
6873 cksum="02CC2504">
6874 contactPostal-YYYYMMDD.csv
6875 </rdeCsv:file>
6876 </rdeCsv:files>
6877 </rdeCsv:csv>
6878 <rdeCsv:csv name="contactTransfer" sep=",">
6879 <rdeCsv:fields>
6880 <csvContact:fId parent="true"/>
6881 <rdeCsv:fTrStatus/>
6882 <rdeCsv:fReRr/>
6883 <rdeCsv:fReID/>
6884 <rdeCsv:fReDate/>
6885 <rdeCsv:fAcRr/>
6886 <rdeCsv:fAcID/>
6887 <rdeCsv:fAcDate/>
6888 </rdeCsv:fields>
6889 <rdeCsv:files>
6890 <rdeCsv:file
6891 cksum="D0929632">
6892 contactTransfer-YYYYMMDD.csv
6893 </rdeCsv:file>
6894 </rdeCsv:files>
6895 </rdeCsv:csv>
6896 <rdeCsv:csv name="contactDisclose" sep=",">
6897 <rdeCsv:fields>
6898 <csvContact:fId parent="true"/>
6899 <csvContact:fDiscloseFlag/>
6900 <csvContact:fDiscloseNameLoc/>
6901 <csvContact:fDiscloseNameInt/>
6902 <csvContact:fDiscloseOrgLoc/>
6903 <csvContact:fDiscloseOrgInt/>
6904 <csvContact:fDiscloseAddrLoc/>
6905 <csvContact:fDiscloseAddrInt/>
6906 <csvContact:fDiscloseVoice/>
6907 <csvContact:fDiscloseFax/>
6908 <csvContact:fDiscloseEmail/>
6909 </rdeCsv:fields>
6910 <rdeCsv:files>
6911 <rdeCsv:file
6912 cksum="89043A90">
6913 contactDisclose-YYYYMMDD.csv
6914 </rdeCsv:file>
6915 </rdeCsv:files>
6916 </rdeCsv:csv>
6917 </csvContact:contents>
6918 <csvRegistrar:contents>
6919 <rdeCsv:csv name="registrar" sep=",">
6920 <rdeCsv:fields>
6921 <csvRegistrar:fId/>
6922 <csvRegistrar:fName isLoc="false"/>
6923 <csvRegistrar:fGurid/>
6924 <csvRegistrar:fStatus/>
6925 <csvContact:fStreet isLoc="false" index="0"/>
6926 <csvContact:fStreet isLoc="false" index="1"/>
6927 <csvContact:fStreet isLoc="false" index="2"/>
6928 <csvContact:fCity isLoc="false" />
6929 <csvContact:fSp isLoc="false" />
6930 <csvContact:fPc isLoc="false" />
6931 <csvContact:fCc isLoc="false" />
6932 <csvContact:fVoice/>
6933 <csvContact:fVoiceExt/>
6934 <csvContact:fFax/>
6935 <csvContact:fFaxExt/>
6936 <csvContact:fEmail isRequired="false"/>
6937 <rdeCsv:fUrl/>
6938 <csvRegistrar:fWhoisUrl/>
6939 <rdeCsv:fCrDate/>
6940 <rdeCsv:fUpDate/>
6941 </rdeCsv:fields>
6942 <rdeCsv:files>
6943 <rdeCsv:file
6944 cksum="306178BB">
6945 registrar-YYYYMMDD.csv
6946 </rdeCsv:file>
6947 </rdeCsv:files>
6948 </rdeCsv:csv>
6949 </csvRegistrar:contents>
6950 <csvIDN:contents>
6951 <rdeCsv:csv name="idnLanguage" sep=",">
6952 <rdeCsv:fields>
6953 <rdeCsv:fIdnTableId isRequired="true"/>
6954 <rdeCsv:fUrl isRequired="true"/>
6955 </rdeCsv:fields>
6956 <rdeCsv:files>
6957 <rdeCsv:file
6958 cksum="D462EAD0">
6959 idnLanguage-YYYYMMDD.csv
6960 </rdeCsv:file>
6961 </rdeCsv:files>
6962 </rdeCsv:csv>
6963 </csvIDN:contents>
6964 <csvNNDN:contents>
6965 <rdeCsv:csv name="NNDN" sep=",">
6966 <rdeCsv:fields>
6967 <csvNNDN:fAName/>
6968 <rdeCsv:fIdnTableId/>
6969 <csvNNDN:fOriginalName/>
6970 <csvNNDN:fNameState/>
6971 <csvNNDN:fMirroringNS/>
6972 <rdeCsv:fCrDate/>
6973 </rdeCsv:fields>
6974 <rdeCsv:files>
6975 <rdeCsv:file
6976 cksum="11C80D60">
6977 NNDN-YYYYMMDD.csv
6978 </rdeCsv:file>
6979 </rdeCsv:files>
6980 </rdeCsv:csv>
6981 </csvNNDN:contents>
6982 <rdeEppParams:eppParams>
6983 <rdeEppParams:version>1.0</rdeEppParams:version>
6984 <rdeEppParams:lang>en</rdeEppParams:lang>
6985 <rdeEppParams:objURI>urn:ietf:params:xml:ns:domain-1.0
6986 </rdeEppParams:objURI>
6987 <rdeEppParams:objURI>urn:ietf:params:xml:ns:host-1.0
6988 </rdeEppParams:objURI>
6989 <rdeEppParams:objURI>urn:ietf:params:xml:ns:contact-1.0
6990 </rdeEppParams:objURI>
6991 <rdeEppParams:svcExtension>
6992 <epp:extURI>urn:ietf:params:xml:ns:secDNS-1.1
6993 </epp:extURI>
6994 <epp:extURI>urn:ietf:params:xml:ns:rgp-1.0
6995 </epp:extURI>
6996 </rdeEppParams:svcExtension>
6997 <rdeEppParams:dcp>
6998 <epp:access>
6999 <epp:all/>
7000 </epp:access>
7001 <epp:statement>
7002 <epp:purpose>
7003 <epp:admin/>
7004 <epp:other/>
7005 <epp:prov/>
7006 </epp:purpose>
7007 <epp:recipient>
7008 <epp:ours/>
7009 <epp:public/>
7010 <epp:unrelated/>
7011 </epp:recipient>
7012 <epp:retention>
7013 <epp:indefinite/>
7014 </epp:retention>
7015 </epp:statement>
7016 </rdeEppParams:dcp>
7017 </rdeEppParams:eppParams>
7018 </rde:contents>
7019 </rde:deposit>
7020
7021 17. Example of a Differential Deposit Using the CSV Model
7022
7023 The following is an example of a Differential Deposit using the CSV
7024 model:
7025
7026 <?xml version="1.0" encoding="UTF-8"?>
7027 <rde:deposit
7028 xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
7029 xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
7030 xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
7031 xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
7032 xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
7033 xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0"
7034 xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0"
7035 xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0"
7036 xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
7037 xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0"
7038 xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
7039 type="DIFF"
7040 id="20191017001" prevId="20191010001">
7041 <rde:watermark>2019-10-18T00:00:00Z</rde:watermark>
7042 <rde:rdeMenu>
7043 <rde:version>1.0</rde:version>
7044 <rde:objURI>urn:ietf:params:xml:ns:csvDomain-1.0</rde:objURI>
7045 <rde:objURI>urn:ietf:params:xml:ns:csvHost-1.0</rde:objURI>
7046 <rde:objURI>urn:ietf:params:xml:ns:csvContact-1.0</rde:objURI>
7047 <rde:objURI>urn:ietf:params:xml:ns:csvRegistrar-1.0</rde:objURI>
7048 <rde:objURI>urn:ietf:params:xml:ns:csvIDN-1.0</rde:objURI>
7049 </rde:rdeMenu>
7050 <rde:deletes>
7051 <csvDomain:deletes>
7052 <rdeCsv:csv name="domain">
7053 <rdeCsv:fields>
7054 <csvDomain:fName/>
7055 </rdeCsv:fields>
7056 <rdeCsv:files>
7057 <rdeCsv:file
7058 cksum="6F2B988F">
7059 domain-delete-YYYYMMDD.csv
7060 </rdeCsv:file>
7061 </rdeCsv:files>
7062 </rdeCsv:csv>
7063 </csvDomain:deletes>
7064 <csvHost:deletes>
7065 <rdeCsv:csv name="host">
7066 <rdeCsv:fields>
7067 <rdeCsv:fRoid/>
7068 </rdeCsv:fields>
7069 <rdeCsv:files>
7070 <rdeCsv:file
7071 cksum="E3408F5E">
7072 host-delete-YYYYMMDD.csv
7073 </rdeCsv:file>
7074 </rdeCsv:files>
7075 </rdeCsv:csv>
7076 </csvHost:deletes>
7077 <csvContact:deletes>
7078 <rdeCsv:csv name="contact">
7079 <rdeCsv:fields>
7080 <csvContact:fId/>
7081 </rdeCsv:fields>
7082 <rdeCsv:files>
7083 <rdeCsv:file
7084 cksum="6F2B988F">
7085 contact-delete-YYYYMMDD.csv
7086 </rdeCsv:file>
7087 </rdeCsv:files>
7088 </rdeCsv:csv>
7089 </csvContact:deletes>
7090 <csvRegistrar:deletes>
7091 <rdeCsv:csv name="registrar">
7092 <rdeCsv:fields>
7093 <csvRegistrar:fId/>
7094 </rdeCsv:fields>
7095 <rdeCsv:files>
7096 <rdeCsv:file
7097 cksum="307B87AE">
7098 registrar-delete-YYYYMMDD.csv
7099 </rdeCsv:file>
7100 </rdeCsv:files>
7101 </rdeCsv:csv>
7102 </csvRegistrar:deletes>
7103 <csvIDN:deletes>
7104 <rdeCsv:csv name="idnLanguage">
7105 <rdeCsv:fields>
7106 <rdeCsv:fIdnTableId/>
7107 </rdeCsv:fields>
7108 <rdeCsv:files>
7109 <rdeCsv:file
7110 cksum="757B573A">
7111 idnLanguage-delete-YYYYMMDD.csv
7112 </rdeCsv:file>
7113 </rdeCsv:files>
7114 </rdeCsv:csv>
7115 </csvIDN:deletes>
7116 <csvNNDN:deletes>
7117 <rdeCsv:csv name="NNDN">
7118 <rdeCsv:fields>
7119 <csvNNDN:fAName/>
7120 </rdeCsv:fields>
7121 <rdeCsv:files>
7122 <rdeCsv:file
7123 cksum="FF104E83">
7124 NNDN-delete-YYYYMMDD.csv
7125 </rdeCsv:file>
7126 </rdeCsv:files>
7127 </rdeCsv:csv>
7128 </csvNNDN:deletes>
7129 </rde:deletes>
7130 <rde:contents>
7131 <rdeHeader:header>
7132 <rdeHeader:tld>test</rdeHeader:tld>
7133 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvDomain-1.0">
7134 2
7135 </rdeHeader:count>
7136 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvHost-1.0">
7137 2
7138 </rdeHeader:count>
7139 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvContact-1.0">
7140 3
7141 </rdeHeader:count>
7142 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvRegistrar-1.0">
7143 1
7144 </rdeHeader:count>
7145 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvIDN-1.0">
7146 1
7147 </rdeHeader:count>
7148 <rdeHeader:count uri="urn:ietf:params:xml:ns:csvNNDN-1.0">
7149 1
7150 </rdeHeader:count>
7151 <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">
7152 1
7153 </rdeHeader:count>
7154 </rdeHeader:header>
7155 <csvDomain:contents>
7156 <rdeCsv:csv name="domain" sep=",">
7157 <rdeCsv:fields>
7158 <csvDomain:fName/>
7159 <rdeCsv:fRoid/>
7160 <rdeCsv:fIdnTableId/>
7161 <csvDomain:fOriginalName/>
7162 <rdeCsv:fRegistrant/>
7163 <rdeCsv:fClID/>
7164 <rdeCsv:fCrRr/>
7165 <rdeCsv:fCrID/>
7166 <rdeCsv:fCrDate/>
7167 <rdeCsv:fUpRr/>
7168 <rdeCsv:fUpID/>
7169 <rdeCsv:fUpDate/>
7170 <rdeCsv:fExDate isRequired="true"/>
7171 </rdeCsv:fields>
7172 <rdeCsv:files>
7173 <rdeCsv:file
7174 cksum="75E2D01F">
7175 domain-YYYYMMDD.csv
7176 </rdeCsv:file>
7177 </rdeCsv:files>
7178 </rdeCsv:csv>
7179 <rdeCsv:csv name="domainContacts" sep=",">
7180 <rdeCsv:fields>
7181 <csvDomain:fName parent="true"/>
7182 <csvContact:fId/>
7183 <csvDomain:fContactType/>
7184 </rdeCsv:fields>
7185 <rdeCsv:files>
7186 <rdeCsv:file
7187 cksum="70A7C17B">
7188 domainContacts-YYYYMMDD.csv
7189 </rdeCsv:file>
7190 </rdeCsv:files>
7191 </rdeCsv:csv>
7192 <rdeCsv:csv name="domainStatuses" sep=",">
7193 <rdeCsv:fields>
7194 <csvDomain:fName parent="true"/>
7195 <csvDomain:fStatus/>
7196 <rdeCsv:fStatusDescription/>
7197 <rdeCsv:fLang/>
7198 <csvDomain:fRgpStatus/>
7199 </rdeCsv:fields>
7200 <rdeCsv:files>
7201 <rdeCsv:file
7202 cksum="EB8C548E">
7203 domainStatuses-YYYYMMDD.csv
7204 </rdeCsv:file>
7205 </rdeCsv:files>
7206 </rdeCsv:csv>
7207 <rdeCsv:csv name="domainNameServers" sep=",">
7208 <rdeCsv:fields>
7209 <csvDomain:fName parent="true"/>
7210 <csvHost:fName parent="true"/>
7211 </rdeCsv:fields>
7212 <rdeCsv:files>
7213 <rdeCsv:file
7214 cksum="984C3097">
7215 domainNameServers-name-YYYYMMDD.csv
7216 </rdeCsv:file>
7217 </rdeCsv:files>
7218 </rdeCsv:csv>
7219 <rdeCsv:csv name="domainNameServers" sep=",">
7220 <rdeCsv:fields>
7221 <csvDomain:fName parent="true"/>
7222 <rdeCsv:fRoid/>
7223 </rdeCsv:fields>
7224 <rdeCsv:files>
7225 <rdeCsv:file
7226 cksum="569D4638">
7227 domainNameServers-roid-YYYYMMDD.csv
7228 </rdeCsv:file>
7229 </rdeCsv:files>
7230 </rdeCsv:csv>
7231 <rdeCsv:csv name="dnssec" sep=",">
7232 <rdeCsv:fields>
7233 <csvDomain:fName parent="true"/>
7234 <csvDomain:fMaxSigLife/>
7235 <csvDomain:fKeyTag/>
7236 <csvDomain:fDsAlg/>
7237 <csvDomain:fDigestType/>
7238 <csvDomain:fDigest/>
7239 </rdeCsv:fields>
7240 <rdeCsv:files>
7241 <rdeCsv:file
7242 cksum="AA15CB43">
7243 dnssec-ds-YYYYMMDD.csv
7244 </rdeCsv:file>
7245 </rdeCsv:files>
7246 </rdeCsv:csv>
7247 <rdeCsv:csv name="dnssec" sep=",">
7248 <rdeCsv:fields>
7249 <csvDomain:fName parent="true"/>
7250 <csvDomain:fMaxSigLife/>
7251 <csvDomain:fFlags/>
7252 <csvDomain:fProtocol/>
7253 <csvDomain:fKeyAlg/>
7254 <csvDomain:fPubKey/>
7255 </rdeCsv:fields>
7256 <rdeCsv:files>
7257 <rdeCsv:file
7258 cksum="1B16F334">
7259 dnssec-key-YYYYMMDD.csv
7260 </rdeCsv:file>
7261 </rdeCsv:files>
7262 </rdeCsv:csv>
7263 <rdeCsv:csv name="domainTransfer" sep=",">
7264 <rdeCsv:fields>
7265 <csvDomain:fName parent="true"/>
7266 <rdeCsv:fTrStatus/>
7267 <rdeCsv:fReRr/>
7268 <rdeCsv:fReID/>
7269 <rdeCsv:fReDate/>
7270 <rdeCsv:fAcRr/>
7271 <rdeCsv:fAcID/>
7272 <rdeCsv:fAcDate/>
7273 <rdeCsv:fExDate/>
7274 </rdeCsv:fields>
7275 <rdeCsv:files>
7276 <rdeCsv:file
7277 cksum="71170194">
7278 domainTransfer-YYYYMMDD.csv
7279 </rdeCsv:file>
7280 </rdeCsv:files>
7281 </rdeCsv:csv>
7282 </csvDomain:contents>
7283 <csvHost:contents>
7284 <rdeCsv:csv name="host" sep=",">
7285 <rdeCsv:fields>
7286 <csvHost:fName/>
7287 <rdeCsv:fRoid/>
7288 <rdeCsv:fClID/>
7289 <rdeCsv:fCrRr/>
7290 <rdeCsv:fCrID/>
7291 <rdeCsv:fCrDate/>
7292 <rdeCsv:fUpRr/>
7293 <rdeCsv:fUpID/>
7294 <rdeCsv:fUpDate/>
7295 <rdeCsv:fTrDate/>
7296 </rdeCsv:fields>
7297 <rdeCsv:files>
7298 <rdeCsv:file
7299 cksum="120938E3">
7300 host-YYYYMMDD.csv
7301 </rdeCsv:file>
7302 </rdeCsv:files>
7303 </rdeCsv:csv>
7304 <rdeCsv:csv name="hostStatuses" sep=",">
7305 <rdeCsv:fields>
7306 <rdeCsv:fRoid parent="true"/>
7307 <csvHost:fStatus/>
7308 <rdeCsv:fStatusDescription/>
7309 <rdeCsv:fLang/>
7310 </rdeCsv:fields>
7311 <rdeCsv:files>
7312 <rdeCsv:file
7313 cksum="0BA504FC">
7314 hostStatuses-YYYYMMDD.csv
7315 </rdeCsv:file>
7316 </rdeCsv:files>
7317 </rdeCsv:csv>
7318 <rdeCsv:csv name="hostAddresses" sep=",">
7319 <rdeCsv:fields>
7320 <rdeCsv:fRoid parent="true"/>
7321 <csvHost:fAddr isRequired="true"/>
7322 <csvHost:fAddrVersion isRequired="true"/>
7323 </rdeCsv:fields>
7324 <rdeCsv:files>
7325 <rdeCsv:file
7326 cksum="17888F02">
7327 hostAddresses-YYYYMMDD.csv
7328 </rdeCsv:file>
7329 </rdeCsv:files>
7330 </rdeCsv:csv>
7331 </csvHost:contents>
7332 <csvContact:contents>
7333 <rdeCsv:csv name="contact" sep=",">
7334 <rdeCsv:fields>
7335 <csvContact:fId/>
7336 <rdeCsv:fRoid/>
7337 <csvContact:fVoice/>
7338 <csvContact:fVoiceExt/>
7339 <csvContact:fFax/>
7340 <csvContact:fFaxExt/>
7341 <csvContact:fEmail/>
7342 <rdeCsv:fClID/>
7343 <rdeCsv:fCrRr/>
7344 <rdeCsv:fCrID/>
7345 <rdeCsv:fCrDate/>
7346 <rdeCsv:fUpRr/>
7347 <rdeCsv:fUpID/>
7348 <rdeCsv:fUpDate/>
7349 </rdeCsv:fields>
7350 <rdeCsv:files>
7351 <rdeCsv:file
7352 cksum="D7F106A5">
7353 contact-YYYYMMDD.csv
7354 </rdeCsv:file>
7355 </rdeCsv:files>
7356 </rdeCsv:csv>
7357 <rdeCsv:csv name="contactStatuses" sep=",">
7358 <rdeCsv:fields>
7359 <csvContact:fId parent="true"/>
7360 <csvContact:fStatus/>
7361 <rdeCsv:fStatusDescription/>
7362 <rdeCsv:fLang/>
7363 </rdeCsv:fields>
7364 <rdeCsv:files>
7365 <rdeCsv:file
7366 cksum="2AAF99D4">
7367 contactStatuses-YYYYMMDD.csv
7368 </rdeCsv:file>
7369 </rdeCsv:files>
7370 </rdeCsv:csv>
7371 <rdeCsv:csv name="contactPostal" sep=",">
7372 <rdeCsv:fields>
7373 <csvContact:fId parent="true"/>
7374 <csvContact:fPostalType/>
7375 <csvContact:fName/>
7376 <csvContact:fOrg/>
7377 <csvContact:fStreet index="0"/>
7378 <csvContact:fStreet index="1"/>
7379 <csvContact:fStreet index="2"/>
7380 <csvContact:fCity/>
7381 <csvContact:fSp/>
7382 <csvContact:fPc/>
7383 <csvContact:fCc/>
7384 </rdeCsv:fields>
7385 <rdeCsv:files>
7386 <rdeCsv:file
7387 cksum="02CC2504">
7388 contactPostal-YYYYMMDD.csv
7389 </rdeCsv:file>
7390 </rdeCsv:files>
7391 </rdeCsv:csv>
7392 <rdeCsv:csv name="contactTransfer" sep=",">
7393 <rdeCsv:fields>
7394 <csvContact:fId parent="true"/>
7395 <rdeCsv:fTrStatus/>
7396 <rdeCsv:fReRr/>
7397 <rdeCsv:fReID/>
7398 <rdeCsv:fReDate/>
7399 <rdeCsv:fAcRr/>
7400 <rdeCsv:fAcID/>
7401 <rdeCsv:fAcDate/>
7402 </rdeCsv:fields>
7403 <rdeCsv:files>
7404 <rdeCsv:file
7405 cksum="D0929632">
7406 contactTransfer-YYYYMMDD.csv
7407 </rdeCsv:file>
7408 </rdeCsv:files>
7409 </rdeCsv:csv>
7410 <rdeCsv:csv name="contactDisclose" sep=",">
7411 <rdeCsv:fields>
7412 <csvContact:fId parent="true"/>
7413 <csvContact:fDiscloseFlag/>
7414 <csvContact:fDiscloseNameLoc/>
7415 <csvContact:fDiscloseNameInt/>
7416 <csvContact:fDiscloseOrgLoc/>
7417 <csvContact:fDiscloseOrgInt/>
7418 <csvContact:fDiscloseAddrLoc/>
7419 <csvContact:fDiscloseAddrInt/>
7420 <csvContact:fDiscloseVoice/>
7421 <csvContact:fDiscloseFax/>
7422 <csvContact:fDiscloseEmail/>
7423 </rdeCsv:fields>
7424 <rdeCsv:files>
7425 <rdeCsv:file
7426 cksum="89043A90">
7427 contactDisclose-YYYYMMDD.csv
7428 </rdeCsv:file>
7429 </rdeCsv:files>
7430 </rdeCsv:csv>
7431 </csvContact:contents>
7432 <csvRegistrar:contents>
7433 <rdeCsv:csv name="registrar" sep=",">
7434 <rdeCsv:fields>
7435 <csvRegistrar:fId/>
7436 <csvRegistrar:fName isLoc="false"/>
7437 <csvRegistrar:fGurid/>
7438 <csvRegistrar:fStatus/>
7439 <csvContact:fStreet isLoc="false" index="0"/>
7440 <csvContact:fStreet isLoc="false" index="1"/>
7441 <csvContact:fStreet isLoc="false" index="2"/>
7442 <csvContact:fCity isLoc="false" />
7443 <csvContact:fSp isLoc="false" />
7444 <csvContact:fPc isLoc="false" />
7445 <csvContact:fCc isLoc="false" />
7446 <csvContact:fVoice/>
7447 <csvContact:fVoiceExt/>
7448 <csvContact:fFax/>
7449 <csvContact:fFaxExt/>
7450 <csvContact:fEmail isRequired="false"/>
7451 <rdeCsv:fUrl/>
7452 <csvRegistrar:fWhoisUrl/>
7453 <rdeCsv:fCrDate/>
7454 <rdeCsv:fUpDate/>
7455 </rdeCsv:fields>
7456 <rdeCsv:files>
7457 <rdeCsv:file
7458 cksum="306178BB">
7459 registrar-YYYYMMDD.csv
7460 </rdeCsv:file>
7461 </rdeCsv:files>
7462 </rdeCsv:csv>
7463 </csvRegistrar:contents>
7464 <csvIDN:contents>
7465 <rdeCsv:csv name="idnLanguage" sep=",">
7466 <rdeCsv:fields>
7467 <rdeCsv:fIdnTableId isRequired="true"/>
7468 <rdeCsv:fUrl isRequired="true"/>
7469 </rdeCsv:fields>
7470 <rdeCsv:files>
7471 <rdeCsv:file
7472 cksum="D462EAD0">
7473 idnLanguage-YYYYMMDD.csv
7474 </rdeCsv:file>
7475 </rdeCsv:files>
7476 </rdeCsv:csv>
7477 </csvIDN:contents>
7478 <csvNNDN:contents>
7479 <rdeCsv:csv name="NNDN" sep=",">
7480 <rdeCsv:fields>
7481 <csvNNDN:fAName/>
7482 <rdeCsv:fIdnTableId/>
7483 <csvNNDN:fOriginalName/>
7484 <csvNNDN:fNameState/>
7485 <csvNNDN:fMirroringNS/>
7486 <rdeCsv:fCrDate/>
7487 </rdeCsv:fields>
7488 <rdeCsv:files>
7489 <rdeCsv:file
7490 cksum="11C80D60">
7491 NNDN-YYYYMMDD.csv
7492 </rdeCsv:file>
7493 </rdeCsv:files>
7494 </rdeCsv:csv>
7495 </csvNNDN:contents>
7496 <rdeEppParams:eppParams>
7497 <rdeEppParams:version>1.0</rdeEppParams:version>
7498 <rdeEppParams:lang>en</rdeEppParams:lang>
7499 <rdeEppParams:objURI>urn:ietf:params:xml:ns:domain-1.0
7500 </rdeEppParams:objURI>
7501 <rdeEppParams:objURI>urn:ietf:params:xml:ns:host-1.0
7502 </rdeEppParams:objURI>
7503 <rdeEppParams:objURI>urn:ietf:params:xml:ns:contact-1.0
7504 </rdeEppParams:objURI>
7505 <rdeEppParams:svcExtension>
7506 <epp:extURI>urn:ietf:params:xml:ns:secDNS-1.1
7507 </epp:extURI>
7508 <epp:extURI>urn:ietf:params:xml:ns:rgp-1.0
7509 </epp:extURI>
7510 </rdeEppParams:svcExtension>
7511 <rdeEppParams:dcp>
7512 <epp:access>
7513 <epp:all/>
7514 </epp:access>
7515 <epp:statement>
7516 <epp:purpose>
7517 <epp:admin/>
7518 <epp:other/>
7519 <epp:prov/>
7520 </epp:purpose>
7521 <epp:recipient>
7522 <epp:ours/>
7523 <epp:public/>
7524 <epp:unrelated/>
7525 </epp:recipient>
7526 <epp:retention>
7527 <epp:indefinite/>
7528 </epp:retention>
7529 </epp:statement>
7530 </rdeEppParams:dcp>
7531 </rdeEppParams:eppParams>
7532 </rde:contents>
7533 </rde:deposit>
7534
7535 18. References
7536
7537 18.1. Normative References
7538
7539 [BCP195] Sheffer, Y., Holz, R., and P. Saint-Andre,
7540 "Recommendations for Secure Use of Transport Layer
7541 Security (TLS) and Datagram Transport Layer Security
7542 (DTLS)", BCP 195, RFC 7525, May 2015.
7543
7544 <https://www.rfc-editor.org/info/bcp195>
7545
7546 [ISO-3166-1]
7547 International Organization for Standardization, "Codes for
7548 the representation of names of countries and their
7549 subdivisions -- Part 1: Country codes", ISO Standard 3166,
7550 August 2020.
7551
7552 [ITU-E164] International Telecommunication Union, "The international
7553 public telecommunication numbering plan", ITU-T
7554 Recommendation E.164, February 2005.
7555
7556 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
7557 DOI 10.17487/RFC0791, September 1981,
7558 <https://www.rfc-editor.org/info/rfc791>.
7559
7560 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
7561 Requirement Levels", BCP 14, RFC 2119,
7562 DOI 10.17487/RFC2119, March 1997,
7563 <https://www.rfc-editor.org/info/rfc2119>.
7564
7565 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
7566 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
7567 <https://www.rfc-editor.org/info/rfc3339>.
7568
7569 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for
7570 the Extensible Provisioning Protocol (EPP)", RFC 3915,
7571 DOI 10.17487/RFC3915, September 2004,
7572 <https://www.rfc-editor.org/info/rfc3915>.
7573
7574 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
7575 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
7576 <https://www.rfc-editor.org/info/rfc5730>.
7577
7578 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
7579 Domain Name Mapping", STD 69, RFC 5731,
7580 DOI 10.17487/RFC5731, August 2009,
7581 <https://www.rfc-editor.org/info/rfc5731>.
7582
7583 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
7584 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
7585 August 2009, <https://www.rfc-editor.org/info/rfc5732>.
7586
7587 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
7588 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
7589 August 2009, <https://www.rfc-editor.org/info/rfc5733>.
7590
7591 [RFC5891] Klensin, J., "Internationalized Domain Names in
7592 Applications (IDNA): Protocol", RFC 5891,
7593 DOI 10.17487/RFC5891, August 2010,
7594 <https://www.rfc-editor.org/info/rfc5891>.
7595
7596 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS)
7597 Security Extensions Mapping for the Extensible
7598 Provisioning Protocol (EPP)", RFC 5910,
7599 DOI 10.17487/RFC5910, May 2010,
7600 <https://www.rfc-editor.org/info/rfc5910>.
7601
7602 [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
7603 Address Text Representation", RFC 5952,
7604 DOI 10.17487/RFC5952, August 2010,
7605 <https://www.rfc-editor.org/info/rfc5952>.
7606
7607 [RFC6234] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms
7608 (SHA and SHA-based HMAC and HKDF)", RFC 6234,
7609 DOI 10.17487/RFC6234, May 2011,
7610 <https://www.rfc-editor.org/info/rfc6234>.
7611
7612 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
7613 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
7614 May 2017, <https://www.rfc-editor.org/info/rfc8174>.
7615
7616 [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
7617 Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
7618 January 2019, <https://www.rfc-editor.org/info/rfc8499>.
7619
7620 [RFC8909] Lozano, G., "Registry Data Escrow Specification",
7621 RFC 8909, DOI 10.17487/RFC8909, November 2020,
7622 <https://www.rfc-editor.org/info/rfc8909>.
7623
7624 [V42] International Telecommunication Union, "V.42 : Error-
7625 correcting procedures for DCEs using asynchronous-to-
7626 synchronous conversion", ITU-T Recommendation V.42, March
7627 2002, <https://www.itu.int/rec/T-REC-V.42/en>.
7628
7629 [W3C.REC-xml-20081126]
7630 Bray, T., Paoli, J., Sperberg-McQueen, C. M., Maler, E.,
7631 and F. Yergeau, "Extensible Markup Language (XML) 1.0
7632 (Fifth Edition) REC-xml-20081126", W3C Recommendation,
7633 November 2008,
7634 <https://www.w3.org/TR/2008/REC-xml-20081126/>.
7635
7636 [W3C.REC-xmlschema-1-20041028]
7637 Thompson, H. S., Beech, D., Maloney, M., and N.
7638 Mendelsohn, "XML Schema Part 1: Structures Second Edition
7639 REC-xmlschema-1-20041028", W3C Recommendation, October
7640 2004,
7641 <https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/>.
7642
7643 [W3C.REC-xmlschema-2-20041028]
7644 Biron, P. V. and A. Malhotra, "XML Schema Part 2:
7645 Datatypes Second Edition REC-xmlschema-2-20041028",
7646 W3C Recommendation, October 2004,
7647 <https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/>.
7648
7649 [W3C.REC-xpath-31-20170321]
7650 Robie, J., Dyck, M., and J. Spiegel, "XML Path Language
7651 (XPath) 3.1", W3C Recommendation, March 2017,
7652 <https://www.w3.org/TR/2017/REC-xpath-31-20170321/>.
7653
7654 18.2. Informative References
7655
7656 [ICANN-GTLD-AGB-20120604]
7657 ICANN, "gTLD Applicant Guidebook Version 2012-06-04", 4
7658 June 2012, <http://newgtlds.icann.org/en/applicants/agb/
7659 guidebook-full-04jun12-en.pdf>.
7660
7661 [ICANN-GTLD-RA-20170731]
7662 ICANN, "Base Registry Agreement 2017-07-31", 31 July 2017,
7663 <https://newgtlds.icann.org/sites/default/files/
7664 agreements/agreement-approved-31jul17-en.pdf>.
7665
7666 [RFC1952] Deutsch, P., "GZIP file format specification version 4.3",
7667 RFC 1952, DOI 10.17487/RFC1952, May 1996,
7668 <https://www.rfc-editor.org/info/rfc1952>.
7669
7670 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,
7671 DOI 10.17487/RFC2818, May 2000,
7672 <https://www.rfc-editor.org/info/rfc2818>.
7673
7674 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
7675 DOI 10.17487/RFC3688, January 2004,
7676 <https://www.rfc-editor.org/info/rfc3688>.
7677
7678 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
7679 DOI 10.17487/RFC3912, September 2004,
7680 <https://www.rfc-editor.org/info/rfc3912>.
7681
7682 [RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma-
7683 Separated Values (CSV) Files", RFC 4180,
7684 DOI 10.17487/RFC4180, October 2005,
7685 <https://www.rfc-editor.org/info/rfc4180>.
7686
7687 [RFC6672] Rose, S. and W. Wijngaards, "DNAME Redirection in the
7688 DNS", RFC 6672, DOI 10.17487/RFC6672, June 2012,
7689 <https://www.rfc-editor.org/info/rfc6672>.
7690
7691 [variantTLDsReport]
7692 Internet Corporation for Assigned Names and Numbers
7693 (ICANN), "A Study of Issues Related to the Management of
7694 IDN Variant TLDs", 20 February 2012,
7695 <https://www.icann.org/en/system/files/files/idn-vip-
7696 integrated-issues-final-clean-20feb12-en.pdf>.
7697
7698 Acknowledgments
7699
7700 Parts of this document are based on EPP [RFC5730] and related RFCs by
7701 Scott Hollenbeck.
7702
7703 Special suggestions that have been incorporated into this document
7704 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc
7705 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen
7706 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul
7707 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan,
7708 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James
7709 Mitchell, Francisco Obispo, Bhadresh Modi, Alexander Mayrhofer, and
7710 Benjamin Kaduk.
7711
7712 Shoji Noguchi and Francisco Arias participated as coauthors through
7713 version 05 of earlier drafts of this document and provided invaluable
7714 support.
7715
7716 Authors' Addresses
7717
7718 Gustavo Lozano
7719 Internet Corporation for Assigned Names and Numbers
7720 Suite 300
7721 12025 Waterfront Drive
7722 Los Angeles, CA 90292
7723 United States of America
7724
7725 Phone: +1.310.823.9358
7726 Email: gustavo.lozano@icann.org
7727
7728
7729 James Gould
7730 VeriSign, Inc.
7731 12061 Bluemont Way
7732 Reston, VA 20190
7733 United States of America
7734
7735 Email: jgould@verisign.com
7736
7737
7738 Chethan Thippeswamy
7739 VeriSign, Inc.
7740 12061 Bluemont Way
7741 Reston, VA 20190
7742 United States of America
7743
7744 Email: cthippeswamy@verisign.com
7745
The IETF is responsible for the creation and maintenance of the DNS RFCs. The ICANN DNS RFC annotation project provides a forum for collecting community annotations on these RFCs as an aid to understanding for implementers and any interested parties. The annotations displayed here are not the result of the IETF consensus process.
This RFC is included in the DNS RFCs annotation project whose home page is here.