idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (Oct 08, 2020) is 1296 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 7525 (ref. 'BCP195') (Obsoleted by RFC 9325) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' ** Downref: Normative reference to an Informational RFC: RFC 6234 ** Obsolete normative reference: RFC 8499 (Obsoleted by RFC 9499) -- Possible downref: Non-RFC (?) normative reference: ref. 'V42' -- Obsolete informational reference (is this intentional?): RFC 2818 (Obsoleted by RFC 9110) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track J. Gould 5 Expires: April 11, 2021 C. Thippeswamy 6 VeriSign 7 Oct 08, 2020 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-10 12 Abstract 14 This document specifies the format, contents and semantics of Domain 15 Name Registration Data (DNRD) Escrow deposits for a Domain Name 16 Registry. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on April 11, 2021. 35 Copyright Notice 37 Copyright (c) 2020 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 54 2.1. XML Model . . . . . . . . . . . . . . . . . . . . . . . . 5 55 2.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . . . 6 56 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 57 3.1. Glossary . . . . . . . . . . . . . . . . . . . . . . . . 6 58 4. Conventions Used in This Document . . . . . . . . . . . . . . 7 59 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 7 60 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 8 61 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 8 62 4.4. CSV Integrity Check . . . . . . . . . . . . . . . . . . . 8 63 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 8 64 4.6. Conventions applicable to the CSV Model . . . . . . . . . 8 65 5. Object Description . . . . . . . . . . . . . . . . . . . . . 17 66 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 17 67 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 36 68 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 46 69 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 64 70 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 72 71 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 75 72 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 80 73 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 82 74 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 82 75 5.10. DNRD Common Objects Collection . . . . . . . . . . . . . 85 76 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 85 77 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 78 8. Data escrow agent extended verification process . . . . . . . 86 79 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 87 80 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 87 81 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 97 82 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 100 83 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 103 84 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 105 85 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 107 86 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 110 87 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116 88 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 119 89 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 122 90 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 123 91 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 124 92 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 125 93 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 127 94 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 129 95 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 130 96 9.17. DNRD Common Objects . . . . . . . . . . . . . . . . . . . 132 97 10. Internationalization Considerations . . . . . . . . . . . . . 132 98 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 132 99 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 140 100 12.1. Implementation in the gTLD space . . . . . . . . . . . . 141 101 13. Security Considerations . . . . . . . . . . . . . . . . . . . 141 102 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 142 103 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 142 104 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 143 105 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 106 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 143 107 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 143 108 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 144 109 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 144 110 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 144 111 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 145 112 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 146 113 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 146 114 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 147 115 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 147 116 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 147 117 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 147 118 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 147 119 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 147 120 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 149 121 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 149 122 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 150 123 16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 150 124 16.19. Changes REGEXT 06 to REGEXT 07 . . . . . . . . . . . . . 150 125 16.20. Changes REGEXT 07 to REGEXT 08 . . . . . . . . . . . . . 150 126 16.21. Changes REGEXT 08 to REGEXT 09 . . . . . . . . . . . . . 151 127 16.22. Changes REGEXT 09 to REGEXT 10 . . . . . . . . . . . . . 151 128 17. Example of a Full Deposit using the XML model . . . . . . . . 151 129 18. Example of Differential Deposit using the XML model . . . . . 157 130 19. Example of a Full Deposit using the CSV model . . . . . . . . 158 131 20. Example of Differential Deposit using the CSV model . . . . . 167 132 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 178 133 21.1. Normative References . . . . . . . . . . . . . . . . . . 178 134 21.2. Informative References . . . . . . . . . . . . . . . . . 181 135 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182 137 1. Introduction 139 Registry Data Escrow (RDE) is the process by which a registry 140 periodically submits data deposits to a third-party called an escrow 141 agent. These deposits comprise the minimum data needed by a third- 142 party to resume operations if the registry cannot function and is 143 unable or unwilling to facilitate an orderly transfer of service. 144 For example, for a domain name registry or registrar, the data to be 145 deposited would include all the objects related to registered domain 146 names, e.g., names, contacts, name servers, etc. 148 The goal of data escrow is higher resiliency of registration 149 services, for the benefit of Internet users. The beneficiaries of a 150 registry are not just those registering information there, but also 151 the users of services relying on the registry data. 153 In the context of domain name registries, registration data escrow is 154 a requirement for generic top-level domains (e.g., Specification 2 of 155 the ICANN Base Registry Agreement, see [ICANN-GTLD-RA-20170731]) and 156 some country code top-level domain managers are also currently 157 escrowing data. There is also a similar requirement for ICANN- 158 accredited domain registrars. 160 This document defines the standard set of objects for a Domain Name 161 Registry that uses the Registry Data Escrow Specification described 162 in [I-D.ietf-regext-data-escrow] for escrow. The set of objects 163 include: 165 o Domain: Internet domain names that are typically provisioned in a 166 Domain Name Registry using the EPP domain name mapping [RFC5731]. 167 The attributes defined in the EPP domain name mapping [RFC5731] 168 are fully supported by this document. 170 o Host: Internet host names that are typically provisioned in a 171 Domain Name Registry using the EPP host mapping [RFC5732]. The 172 attributes defined in the EPP host mapping [RFC5732] are fully 173 supported by this document. 175 o Contact: Individual or organization social information provisioned 176 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 177 The attributes defined in the EPP contact mapping [RFC5733] are 178 fully supported by this document. 180 o Registrar: The organization that sponsors objects like domains, 181 hosts, and contacts in a Domain Name Registry. 183 o NNDN (NNDN's not domain name): Domain Name Registries may maintain 184 domain names without being persisted as domain objects in the 185 registry system, for example, a list of reserved names not 186 available for registration. The NNDN is a lightweight domain-like 187 object that is used to escrow domain names not maintained as 188 domain name objects. 190 This document defines the following pseudo-objects: 192 o IDN Table Reference: Internationalized Domain Names (IDN) included 193 in the Domain Object Data Escrow include references to the IDN 194 Table and Policy used in IDN registration. 196 o EPP parameters: Contains the EPP parameters supported by the 197 Registry Operator. 199 o Header: Used to specify counters of objects in the database at a 200 certain point in time (watermark). 202 o Policy: Used to specify OPTIONAL elements from this specification 203 that are REQUIRED based on the business model of the registry. 205 Extensible Markup Language (XML) 1.0 as described in 206 [W3C.REC-xml-20081126] and XML Schema notation as described in 207 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028] are 208 used in this specification. 210 2. Models 212 This document defines two different models that can be used to 213 deposit data escrow objects: XML and CSV. 215 The data escrow deposit MAY contain a mix of both models but an 216 object MUST be escrowed only in one model. 218 This document does not suggest the use of a particular model, and 219 both are equivalent. A Domain Name Registry may choose the model 220 that is more appropriate for the peculiarities of its systems. For 221 example, a registry may use the CSV-export functionality of the 222 Relational Database Management System (RDBMS) for escrow; therefore, 223 the CSV model may be more appropriate. Another registry may use the 224 code developed for EPP to implement escrow. 226 2.1. XML Model 228 XML: The XML model includes all the deposit information (meta-data 229 and data) in an XML document. The definition of the XML format is 230 fully defined in the XML schemas. As a convention, the objects 231 represented using the XML model are referenced using RDE and an XML 232 namespace that is prefixed with "rde". For example, the Domain Name 233 object represented using the XML model can be referred to as the RDE 234 Domain Name with the XML namespace including rdeDomain 235 (urn:ietf:params:xml:ns:rdeDomain-1.0). 237 2.2. CSV Model 239 CSV: The CSV model uses XML to define the data escrow format of the 240 data contained in referenced Comma-Separated Values (CSV) files. As 241 a convention, the objects represented using the CSV model is 242 referenced using CSV and an XML namespace that is prefixed with 243 "csv". For example, the Domain Name object represented using the CSV 244 model can be referred to as the CSV Domain Name with the XML 245 namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). 247 3. Terminology 249 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 250 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 251 "OPTIONAL" in this document are to be interpreted as described in BCP 252 14 [RFC2119] [RFC8174] when, and only when, they appear in all 253 capitals, as shown here. 255 3.1. Glossary 257 In the following section, the most common terms are briefly 258 explained: 260 o Allocated: a status of some label with respect to a zone, whereby 261 the label is associated administratively to some entity that has 262 requested the label. This term (and its cognates "allocation" and 263 "to allocate") may represent the first step on the way to 264 delegation in the DNS. 266 o Comma-Separated Values (CSV), see [RFC4180]. 268 o Domain name: see definition of Domain name in [RFC8499]. 270 o Extensible Provisioning Protocol (EPP), see definition of the 271 Extensible Provisioning Protocol in [RFC8499]. 273 o Fully-Qualified Domain Name (FQDN), see definition of FQDN in 274 [RFC8499]. 276 o Internationalized Domain Name (IDN), see definition of 277 Internationalized Domain Name in [RFC8499]. 279 o Label: see definition of Label in [RFC8499]. 281 o Registrant: see definition of Registrant in [RFC8499]. 283 o Registrar: see definition of Registrar in [RFC8499]. 285 o Registry: see definition of Registry in [RFC8499]. 287 o Registry-class domain name (RCDN): refers to a top-level domain 288 (TLD) or any other domain name at any level in the DNS tree for 289 which a Registry (either directly or through an affiliate company) 290 provides Registry Services for other organizations or individuals. 291 For example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 293 o Registry Data Escrow (RDE): registry data escrow is the process by 294 which a registry periodically submits data deposits to a third- 295 party called an escrow agent. These deposits comprise the minimum 296 data needed by a third-party to resume operations if the registry 297 cannot function and is unable or unwilling to facilitate an 298 orderly transfer of service. 300 o Registry services: services offered by the Registry critical to 301 the following tasks: the provisioning of domain names on receipt 302 of requests and data from registrars; responding to registrar 303 queries for status information relating to the DNS servers for the 304 RCDN; dissemination of RCDN zone files; operation of the Registry 305 DNS servers; responding to queries for contact and other 306 information concerning DNS registrations in the RCDN; and any 307 other products or services that only a Registry is capable of 308 providing, by reason of its designation as the Registry. Typical 309 examples of Registry Services are DNS resolution for the RCDN, 310 WHOIS and EPP. 312 o SRS: Shared Registration System, see also 313 [ICANN-GTLD-AGB-20120604]. 315 o Top-Level Domain Name (TLD), see definition of Top-Level Domain in 316 [RFC8499]. 318 o UTC: Coordinated Universal Time, as maintained by the Bureau 319 International des Poids et Mesures (BIPM); see also [RFC3339]. 321 4. Conventions Used in This Document 323 4.1. Date and Time 325 Numerous fields indicate "dates", such as the creation and expiry 326 dates for domain names. These fields SHALL contain timestamps 327 indicating the date and time in UTC as specified in [RFC3339], with 328 no offset from the zero meridian. 330 4.2. Country names 332 Country identifiers SHALL be represented using two character 333 identifiers as specified in [ISO-3166-1]. 335 4.3. Telephone numbers 337 Telephone numbers (both voice and facsimile) SHALL be formatted based 338 on structures defined in [ITU-E164]. Telephone numbers described in 339 this specification are character strings that MUST begin with a plus 340 sign ("+", ASCII value 0x2B), followed by a country code defined in 341 [ITU-E164], followed by a dot (".", ASCII value 0x2E), followed by a 342 sequence of digits representing the telephone number. 344 4.4. CSV Integrity Check 346 A checksum MAY be used to verify the integrity of the CSV files, for 347 example, if another layer (i.e., encryption of an archive containing 348 the deposit files) does not provide integrity. By default the CRC32 349 algorithm (see, 8.1.1.6.2 of [V42]) is used. A stronger algorithm, 350 such as SHA-256 (see, [RFC6234]) MAY be used for enhanced security if 351 required. 353 4.5. IP addresses 355 The syntax of IP addresses MUST conform to the text representation of 356 either Internet Protocol Version 4 [RFC0791] or Internet Protocol 357 Version 6 [RFC5952]. 359 4.6. Conventions applicable to the CSV Model 361 4.6.1. CSV Parent Child Relationship 363 The CSV model represents a relational model, where the CSV files 364 represent relational tables, the fields of the CSV files represent 365 columns of the tables, and each line of the CSV file represents a 366 record. As in a relational model, the CSV files can have 367 relationships utilizing primary keys in the parent CSV file 368 definitions and foreign keys in the child CSV file definitions for a 369 1-to-many relationship. The primary keys are not explicitly defined, 370 but the foreign keys are using the boolean "parent" field attribute 371 in the child CSV file. The relationships between the CSV files are 372 used to support a cascade replace or cascade delete of records 373 starting from the parent record in Differential and Incremental 374 Deposits (see [I-D.ietf-regext-data-escrow]). 376 The following is an example of the CSV file definitions, using the 377 element (see Section 4.6.2.1), for a Sample object 378 consisting of a parent "sample" CSV File Definition and a child 379 "sampleStatuses" CSV File Definition. The primary key for the Sample 380 object is the field that is used as the foreign key 381 in the "sampleStatuses" CSV File Definition by specifying the 382 "parent=true" attribute. If a Sample record is updated or deleted in 383 a Differential or Incremental Deposit, it should cascade replace the 384 data using the records included in the child "sampleStatuses" CSV 385 File Definition or cascade delete the existing records in the child 386 "sampleStatuses" CSV File Definition, respectively. 388 389 ... 390 391 392 393 394 395 396 397 398 399 400 401 402 403 405 sample-YYYYMMDD.csv 406 407 408 409 410 411 412 413 414 415 416 417 419 sampleStatuses-YYYYMMDD.csv 420 421 422 423 ... 424 426 4.6.2. CSV elements 428 4.6.2.1. element 430 To support the CSV model, an element is defined for each object that 431 substitutes for the element and for the 432 element, that contains one or more elements. For 433 example, the Domain Name Object (Section 5.1) defines the 434 element, that substitutes for the 435 element, and the element, that substitutes for 436 the element. Both the element and 437 the elements contain one or more 438 elements. The element has the following child elements: 440 Ordered list of CSV fields used in the CSV files. 441 There are one or more child elements that substitute for the 442 abstract element. Each element defines the format 443 of the CSV field contained in the CSV files. The 444 elements support the "type" attribute that defines the XML simple 445 data type of the field element. The elements 446 support the "isRequired" attribute, with a default value of 447 "false", when set to "true" indicates that the field must be non- 448 empty in the CSV files and when set to "false" indicates that the 449 field MAY be empty in the CSV files. The "isRequired" attribute 450 MAY be specifically set for the field elements within the XML 451 schema and MAY be overridden when specifying the fields under the 452 element. The element supports an 453 OPTIONAL "parent" attribute that identifies the field as a 454 reference to a parent object, as defined in CSV Parent Child 455 Relationship (Section 4.6.1). For example, the field SHOULD set the 457 "parent" attribute to "true" to identify it as the parent domain 458 name of the domain status. 460 A list of one or more CSV files using the 461 child element. The child element 462 defines a reference to the CSV file name and has the following 463 optional attributes: 465 compression If the CSV file is compressed, the "compression" 466 attribute defines the compression format. For example, setting 467 this attribute to "gzip" signals that the CSV file is 468 compressed using the GZIP file format (see, [RFC1952]). The 469 supported compression formats are negotiated out-of-band. 471 encoding Defines the encoding of the CSV file with the default 472 encoding of "UTF-8". 474 cksum Defines the checksum of the CSV file, as described in 475 Section 4.4, using the algorithm defined by the "cksumAlg" 476 attribute. If the "cksumAlg" attribute is not present, the 477 checksum is calculated using "CRC32". 479 cksumAlg Defines the checksum algorithm used to calculate the 480 "cksum" attribute, with the default value of "CRC32". If the 481 value "SHA256" is specified, the SHA-256 algorithm (see, 482 [RFC6234]) MUST be used to calculate the "cksum" attribute. 483 Parties receiving and processing data escrow deposits MUST 484 support CRC32 and SHA-256. If this attribute is present, the 485 "cksum" attribute MUST also be present. Additional checksum 486 algorithms are negotiated out-of-band. 488 The element requires a "name" attribute that defines the 489 purpose of the CSV file with values like "domain", "host", "contact". 490 The supported "name" attribute values are defined for each object 491 type. The OPTIONAL "sep" attribute defines the CSV separator 492 character with the default separator character of ",". The need for 493 quoting/escaping of the CSV data could be avoided by choosing a 494 separator character that is not in the data set of the CSV files. 496 The following is an example of the 497 element for domain name records where the is set 498 as required with isRequired="true". 500 501 ... 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 521 domain-YYYYMMDD.csv 522 523 524 525 ... 526 528 The following is example of the "domain-YYYYMMDD.csv" file with one 529 record matching the definition. 531 domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 532 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 533 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 534 The following is an example of the 535 element for domain name records. 537 538 ... 539 540 541 542 543 544 546 domain-delete-YYYYMMDD.csv 547 548 549 550 ... 551 553 The following is example of the "domain-delete-YYYYMMDD.csv" file 554 with three records that matches the single field. 556 domain1.example 557 domain2.example 558 domainN.example 560 4.6.2.2. CSV common field elements 562 The element defined in the element 563 (Section 4.6.2.1) section has child elements that substitute for the 564 abstract element. By convention 565 elements include an 'f' prefix to identify them as field definition 566 elements. There are a set of common field elements that are used 567 across multiple data escrow objects. The common field elements are 568 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 569 using the "rdeCsv" sample namespace prefix. The CSV common field 570 elements include: 572 UTF-8 encoded name field with 573 type="eppcom:labelType". 575 Repository Object IDentifier (ROID) field with 576 type="eppcom:roidType" and isRequired="true". 578 Registrant contact identifier with 579 type="eppcom:clIDType". 581 The object status description, which is 582 free form text describing the rationale for the status, with 583 type="normalizedString". 585 Identifier of the client (registrar) that sponsors 586 the object with type="eppcom:clIDType" and isRequired="true". 588 Identifier of the registrar, defined in Section 5.4, 589 of the client that created the object with type="eppcom:clIDType". 591 Identifier of the client that created the object with 592 type="eppcom:clIDType". 594 Identifier of the registrar, defined in Section 5.4, 595 of the client that last updated the object with 596 type="eppcom:clIDType". 598 Identifier of the client that last updated the object 599 with type="eppcom:clIDType". 601 Identifier of the registrar, defined in Section 5.4, 602 of the client that requested the transfer with 603 type="eppcom:clIDType" and isRequired="true". 605 Identifier of the client that requested the transfer 606 with type="eppcom:clIDType". 608 Identifier of the registrar, defined in Section 5.4, 609 of the client that should take or took action with 610 type="eppcom:clIDType" and isRequired="true". 612 Identifier of the client that should take or took 613 action for transfer with type="eppcom:clIDType". 615 Created date of object with type="dateTime". 617 Updated date of object with type="dateTime". 619 Expiration date of object with type="dateTime". 621 Date that transfer was requested with 622 type="dateTime" and isRequired="true". 624 Date that transfer action should be taken or has 625 been taken with type="dateTime" and isRequired="true". 627 Date of last transfer with type="dateTime". 629 State of the most recent transfer request with 630 type="eppcom:trStatusType" and isRequired="true". 632 General token field with type="token". 634 General language field with type="language". 636 IDN Table Identifier used for IDN domain names 637 with type="token". 639 General positive integer field with 640 type="positiveInteger". 642 Contains the URL of an object like a registrar object 643 with type="anyURI". 645 Custom field with name attribute that defines the 646 custom field name" with type="token". 648 4.6.3. Internationalized and Localized Elements 650 Some elements MAY be provided in either internationalized form 651 ("int") or localized form ("loc"). Those elements use a field value 652 or "isLoc" attribute to specify the form used. If an "isLoc" 653 attribute is used, a value of "true" indicates the use of the 654 localized form and a value of "false" indicates the use of the 655 internationalized form. This MAY override the form specified for a 656 parent element. A value of "int" is used to indicate the 657 internationalized form and a value of "loc" is used to indicate the 658 localized form. When the internalized form ("int") is provided, the 659 field value MUST be represented in a subset of UTF-8 that can be 660 represented in the 7-bit US-ASCII character set. When the localized 661 form ("loc") is provided, the field value MAY be represented in 662 unrestricted UTF-8. 664 The field elements below of the "registrar" 665 element specify the internationalized form with the 666 isLoc="false" attribute. 668 ... 669 670 ... 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 702 registrar-YYYYMMDD.csv 703 704 705 706 ... 707 708 ... 710 The following is an example of using the 711 field value to define the internationalized or localized form of the 712 remainder of the "contactPostal" field values. 714 ... 715 716 ... 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 734 contactPostal-YYYYMMDD.csv 735 736 737 738 ... 739 740 ... 742 5. Object Description 744 This section describes the base objects supported by this 745 specification: 747 5.1. Domain Name Object 749 The domain name object is based on the EPP domain name mapping 750 specified in [RFC5731]. The domain name object supports both the XML 751 Model and the CSV Model, defined in the Models (Section 2) section. 752 The elements used for both models are defined in the following 753 sections. 755 5.1.1. XML Model 757 There are two elements used in the data escrow of the domain name 758 objects for the XML model including the , under the 759 element, and the element, under the 760 element. 762 5.1.1.1. object 764 The domain element is based on the EPP domain response for an 765 authorized client (see Section 3.1.2. of [RFC5731]) with additional 766 data from an EPP Query Response, see Section 3.1.3. of 767 [RFC5731], Registry Grace Period (RGP) status from [RFC3915], and 768 data from the EPP command, see Section 5.2.1. of 769 [RFC5910]. 771 A element substitutes for the abstract 772 element to define a concrete definition of a domain. The 773 element can be replaced by other domain definitions 774 using the XML schema substitution groups feature. 776 The element contains the following child elements: 778 o A element that contains the fully-qualified name of the 779 domain name object. For IDNs the A-Label is used (see [RFC5891], 780 Section 4.4). 782 o A element that contains the repository object identifier 783 assigned to the domain name object when it was created. 785 o An OPTIONAL element that contains the fully-qualified 786 domain name in Unicode character set. It MUST be provided if 787 available. 789 o An OPTIONAL element that references the IDN 790 Table used for the IDN. This corresponds to the "id" attribute of 791 the element. This element MUST be present if the 792 domain name is an IDN. 794 o An OPTIONAL element is used to indicate that the 795 domain name is an IDN variant. This element contains the domain 796 name used to generate the IDN variant. 798 o One or more elements that contain the current status 799 descriptors associated with the domain name. 801 o Zero or more OPTIONAL elements to represent 802 "pendingDelete" sub-statuses, including "redemptionPeriod", 803 "pendingRestore", and "pendingDelete", that a domain name can be 804 in as a result of grace period processing as specified in 805 [RFC3915]. 807 o An OPTIONAL element that contains the identifier for 808 the human or organizational social information object associated 809 as the holder of the domain name object. 811 o Zero or more OPTIONAL elements that contain identifiers 812 for the human or organizational social information objects 813 associated with the domain name object. 815 o An OPTIONAL element that contains the fully-qualified names 816 of the delegated host objects or host attributes (name servers) 817 associated with the domain name object. See Section 1.1 of 818 [RFC5731] for a description of the elements used to specify host 819 objects or host attributes. 821 o A element that contains the identifier of the sponsoring 822 registrar. 824 o An OPTIONAL element that contains the identifier of the 825 registrar that created the domain name object. An OPTIONAL client 826 attribute is used to specify the client that performed the 827 operation. 829 o An OPTIONAL element that contains the date and time of 830 the domain name object creation. This element MUST be present if 831 the domain name has been allocated. 833 o An OPTIONAL element that contains the date and time 834 identifying the end (expiration) of the domain name object's 835 registration period. This element MUST be present if the domain 836 name has been allocated. 838 o An OPTIONAL element that contains the identifier of the 839 registrar that last updated the domain name object. This element 840 MUST NOT be present if the domain has never been modified. An 841 OPTIONAL client attribute is used to specify the client that 842 performed the operation. 844 o An OPTIONAL element that contains the date and time of 845 the most recent domain-name-object modification. This element 846 MUST NOT be present if the domain name object has never been 847 modified. 849 o An OPTIONAL element that contains the public key 850 information associated with Domain Name System security (DNSSEC) 851 extensions for the domain name as specified in [RFC5910]. 853 o An OPTIONAL element that contains the date and time of 854 the most recent domain name object successful transfer. This 855 element MUST NOT be present if the domain name object has never 856 been transferred. 858 o An OPTIONAL element that contains the following child 859 elements related to the last transfer request of the domain name 860 object. This element MUST NOT be present if a transfer request 861 for the domain name has never been created. 863 * A element that contains the state of the most recent 864 transfer request. 866 * A element that contains the identifier of the registrar 867 that requested the domain name object transfer. An OPTIONAL 868 client attribute is used to specify the client that performed 869 the operation. 871 * A element that contains the date and time that the 872 transfer was requested. 874 * An element that contains the identifier of the registrar 875 that should act upon a PENDING transfer request. For all other 876 status types, the value identifies the registrar that took the 877 indicated action. An OPTIONAL client attribute is used to 878 specify the client that performed the operation. 880 * An element that contains the date and time of a 881 required or completed response. For a PENDING request, the 882 value identifies the date and time by which a response is 883 required before an automated response action will be taken by 884 the registry. For all other status types, the value identifies 885 the date and time when the request was completed. 887 * An OPTIONAL element that contains the end of the 888 domain name object's validity period (expiry date) if the 889 transfer caused or causes a change in the validity period. 891 Example of a domain name object: 893 ... 894 895 xn--exampl-gva.example 896 Dexample1-TEST 897 pt-BR 898 example.example 899 900 jd1234 901 sh8013 902 sh8013 903 904 ns1.example.com 905 ns1.example1.example 906 907 RegistrarX 908 RegistrarX 909 1999-04-03T22:00:00.0Z 910 2025-04-03T22:00:00.0Z 911 912 ... 914 5.1.1.2. object 916 The element contains the fully-qualified domain 917 name that was deleted and purged. 919 Example of object: 921 ... 922 923 ... 924 925 foo.example 926 bar.example 927 928 ... 929 930 ... 932 5.1.2. CSV Model 934 For the CSV Model of the domain name object, the 935 child element of the element is used to hold the new 936 or updated domain name objects for the deposit. The 937 child element of the element is 938 used to hold the deleted or purged domain name objects for the 939 deposit. Both the and 940 elements contain one or more elements with a set of 941 named CSV file definitions using the "name" attribute. 943 Differential and Incremental Deposits are based on changes to the 944 domain name objects. The updated domain name object data under the 945 element is a cascade replace down all of the 946 domain name CSV files starting with the parent "domain" CSV File 947 Definition (Section 5.1.2.1.1). The child CSV file definitions 948 include a field. All the child CSV 949 file definition data for the domain name objects in the parent 950 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 951 deleted and then set using the data in the child CSV files. The 952 deleted domain name object data under the element 953 is a cascade delete starting from the "domain" Deletes CSV File 954 Definition (Section 5.1.2.2.1). 956 5.1.2.1. 958 The is used to hold the new or updated domain 959 name object information for the deposit. The is 960 split into separate CSV file definitions using named 961 elements with the "name" attribute. The following sections include 962 the supported domain name CSV file definitions: 964 5.1.2.1.1. "domain" CSV File Definition 966 The "domain" CSV File Definition defines the fields and CSV file 967 references used for the parent domain name object records. All the 968 other domain name CSV file definitions are child CSV files based on 969 the inclusion of the field. 971 The following "csvDomain" field elements MUST be used in the "domain" 972 element: 974 Domain name field with type="eppcom:labelType" and 975 isRequired="true". 977 The following "csvDomain" field elements MAY be used in the "domain" 978 element: 980 Fully-qualified name of the original IDN 981 domain name object related to the variant domain name object with 982 type="eppcom:labelType". 984 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 985 "domain" element: 987 Registry Object IDentifier (ROID) for the domain name 988 object with isRequired="true". 990 or A choice of: 992 Identifier of the sponsoring client with 993 isRequired="true". 995 Contains the Globally Unique Registrar 996 Identifier (GURID) assigned by ICANN with 997 type="positiveInteger" and "isRequired"="true". 999 The following "rdeCsv" fields, defined in section CSV common field 1000 elements (Section 4.6.2.2), MAY be used in the "domain" 1001 element: 1003 Identifier of the registrar, defined in Section 5.4, 1004 of the client that created the domain name object. 1006 Identifier of the client that created the domain name 1007 object. 1009 Identifier of the registrar, defined in Section 5.4, 1010 of the client that last updated the domain name object. 1012 Identifier of the client that last updated the domain 1013 name object. 1015 UTF8 encoded domain name for the 1016 field element. 1018 IDN Table Identifier used for the IDN domain 1019 name object that MUST match a field element 1020 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 1022 Registrant contact identifier for the domain 1023 name object. 1025 Created date and time of the domain name object. 1027 Date and time of the last update to the domain name 1028 object. This field MUST NOT be set if the domain name object has 1029 never been modified. 1031 Expiration date and time for the domain name 1032 object. 1034 Date and time of the last transfer for the domain 1035 name object. This field MUST NOT be set if the domain name object 1036 has never been transferred. 1038 Example of a "domain" element. 1040 ... 1041 1042 ... 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1062 domain-YYYYMMDD.csv 1063 1064 1065 1066 ... 1067 1068 ... 1070 Example of the corresponding domain-YYYYMMDD.csv file. The file 1071 contains four records (two active ASCII domains, original IDN with 1072 LANG-1 language rules, and variant IDN with LANG-1 language rules). 1074 domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 1075 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1076 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 1077 domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 1078 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 1079 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 1080 xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 1081 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1082 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 1083 xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example, 1084 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 1085 registrarX,clientY,2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 1087 5.1.2.1.2. "domainContacts" CSV File Definition 1089 The "domainContacts" CSV File Definition defines the fields and CSV 1090 file references used for the domain name object link records to 1091 contact objects, as described in Contact Object (Section 5.3). 1093 The following "csvDomain" field elements, defined for the "domain" 1094 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 1095 "domainContacts" element: 1097 The name of the domain object that is linked to 1098 the contact object with isRequired="true". 1100 The contact type for the contact object 1101 link with type="domain:contactAttrType" and isRequired="true". 1102 The supported contact type values include "admin" for the 1103 administration contact, "billing" for the billing contact, and 1104 "tech" for the technical contact. 1106 The following "csvContact" fields, defined for the "contact" CSV File 1107 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 1108 element: 1110 The server-unique contact identifier with 1111 isRequired="true". 1113 Example of a "domainContacts" 1114 element. 1116 ... 1117 1118 ... 1119 1120 1121 1122 1123 1124 1125 1126 1128 domainContacts-YYYYMMDD.csv 1129 1130 1131 1132 ... 1133 1134 ... 1136 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1137 file contains an admin, tech, and billing contact for the four domain 1138 names domain1.example, domain2.example, xn--bc123-3ve.example and 1139 xn--bc321-3ve.example. 1141 domain1.example,domain1admin,admin 1142 domain1.example,domain1tech,tech 1143 domain1.example,domain1billing,billing 1144 domain2.example,domain2admin,admin 1145 domain2.example,domain2tech,tech 1146 domain2.example,domain2billing,billing 1147 xn--bc123-3ve.example,xnabc123admin,admin 1148 xn--bc123-3ve.example,xnabc123tech,tech 1149 xn--bc123-3ve.example,xnabc123billing,billing 1150 xn--bc321-3ve.example,xnabc123admin,admin 1151 xn--bc321-3ve.example,xnabc123tech,tech 1152 xn--bc321-3ve.example,xnabc123billing,billing 1154 5.1.2.1.3. "domainStatuses" CSV File Definition 1156 The "domainStatuses" CSV File Definition defines the fields and CSV 1157 file references used for the domain name object statuses. 1159 The following "csvDomain" fields, defined for the "domain" CSV File 1160 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1161 element: 1163 Domain name of status with isRequired="true". 1165 The status of the domain name with 1166 type="domain:statusValueType" and isRequired="true". 1168 The RGP status, as a sub-status of the 1169 "pendingDelete" status value, with 1170 type="rgp:statusValueType" as defined in [RFC3915]. 1172 The following "rdeCsv" fields, defined in section CSV common field 1173 elements (Section 4.6.2.2), MAY be used in the "domainStatuses" 1174 element: 1176 Domain name object status description 1177 which is free form text describing the rationale for the status. 1179 Language of the field. 1181 Example of a "domainStatuses" 1182 element. 1184 ... 1185 1186 ... 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1198 domainStatuses-YYYYMMDD.csv 1199 1200 1201 1202 ... 1203 1204 ... 1206 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1207 file contains the statuses for the four domain names domain1.example, 1208 domain2.example, xn--bc123-3ve.example and xn--bc321-3ve.example. 1210 domain1.example,clientUpdateProhibited,"Disallow update", 1211 en, 1212 domain1.example,clientDeleteProhibited,"Disallow delete", 1213 en, 1214 domain2.example,ok,,, 1215 xn--bc123-3ve.example,ok,,, 1216 xn--bc321-3ve.example,ok,,, 1218 5.1.2.1.4. "domainNameServers" CSV File Definition 1220 The "domainNameServers" CSV File Definition defines the fields and 1221 CSV file references used for the domain name delegated hosts (name 1222 servers). The "domainNameServers" CSV files define the relationship 1223 between a domain name object and a delegated host. The 1224 "domainNameServers" CSV File is used to support the 1225 model, defined in [RFC5731]. 1227 The following "csvDomain" fields, defined for the "domain" CSV File 1228 Definition (Section 5.1.2.1.1), MUST be used in the 1229 "domainNameServers" element: 1231 Domain name using the delegated host with 1232 isRequired="true". 1234 The following "csvHost" and "rdeCsv" field elements MUST be used in 1235 the "domainNameServers" element: 1237 or A choice of: 1239 Host name field with type="eppcom:labelType" and 1240 isRequired="true". 1242 Host object Registry Object IDentifier (ROID) 1243 assigned to the host object with isRequired="true". 1245 Example of a "domainNameServers" 1246 element. 1248 ... 1249 1250 ... 1251 1252 1253 1254 1255 1256 1257 1259 domainNameServers-YYYYMMDD.csv 1260 1261 1262 1263 ... 1264 1265 ... 1267 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1268 The file contains the delegated hosts (name servers) for the four 1269 domain names domain1.example, domain2.example, xn--bc123-3ve.example 1270 and xn--bc321-3ve.example referenced via the field 1271 element. 1273 domain1.example,Hns1_domain1_test-TEST 1274 domain1.example,Hns2_domain1_test-TEST 1275 domain2.example,Hns1_domain2_test-TEST 1276 domain2.example,Hns2_domain2_test-TEST 1277 xn--bc123-3ve.example,Hns1_example_test-TEST 1278 xn--bc123-3ve.example,Hns2_example_test-TEST 1279 xn--bc321-3ve.example,Hns1_example_test-TEST 1280 xn--bc321-3ve.example,Hns2_example_test-TEST 1282 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1284 The "domainNameServersAddresses" CSV File Definition defines the 1285 fields and CSV file references used for supporting the domain host 1286 attributes model. 1288 The following "csvDomain" fields, defined for the "domain" CSV File 1289 Definition (Section 5.1.2.1.1), MUST be used in the 1290 "domainNameServersAddresses" element: 1292 Domain name using the delegated host with host 1293 and isRequired="true". 1295 The following "rdeCsv" fields, defined in section Host CSV model 1296 elements (Section 5.2.2), MUST be used in the 1297 "domainNameServersAddresses" element: 1299 Host name field with type="eppcom:labelType" and 1300 isRequired="true". 1302 The following "csvHost" fields, defined in section Host CSV model 1303 elements (Section 5.2.2), MAY be used in the 1304 "domainNameServersAddresses" element: 1306 IP addresses associated with the host object with 1307 type="host:addrStringType". 1309 IP addresses version associated with the host 1310 object with type="host:ipType". "host:ipType" has the enumerated 1311 values of "v4" or "v6". 1313 Example of a "domainNameServersAddresses" 1314 element. 1316 ... 1317 1318 ... 1319 1320 1321 1322 1323 1324 1325 1326 1327 1329 domainNameServersAddresses-YYYYMMDD.csv 1330 1331 1332 1333 ... 1334 1335 ... 1337 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1338 file. The file contains the delegated hosts (name servers) for the 1339 four domain names domain1.example, domain2.example, xn-- 1340 bc123-3ve.example and xn--bc321-3ve.example. 1342 domain1.example,ns1.domain1.example,192.0.2.1,v4 1343 domain1.example,ns2.domain1.example,2001:DB8::1,v6 1344 domain2.example,ns1.example.net,, 1345 domain2.example,ns2.example.net,, 1346 xn--bc123-3ve.example,ns1.example.net,, 1347 xn--bc123-3ve.example,ns2.example.net,, 1348 xn--bc321-3ve.example,ns1.example.net,, 1349 xn--bc321-3ve.example,ns2.example.net,, 1351 5.1.2.1.6. "dnssec" CSV File Definition 1353 The "dnssec" CSV File Definition defines the fields and CSV file 1354 references used for the domain name object DNSSEC records (DS or Key 1355 Data). 1357 The following "csvDomain" field elements MUST be used in the "dnssec" 1358 element when the DS Data Interface per 1359 [RFC5910] is used: 1361 Contains the DS key tag value per [RFC5910] with 1362 type="unsignedShort" and isRequired="true". 1364 Contains the DS algorithm value per [RFC5910] 1365 with type="unsignedByte" and isRequired="true". 1367 Contains the DS digest type value per 1368 [RFC5910] with type="unsignedByte" and isRequired="true". 1370 Contains the DS digest value per [RFC5910] with 1371 type="hexBinary" and isRequired="true". 1373 The following "csvDomain" field elements MUST be used in the "dnssec" 1374 element when the Key Data Interface per 1375 [RFC5910] is used and MAY be used in the "dnssec" 1376 element when the DS Data Interface per [RFC5910] is 1377 used: 1379 Contains the flags field value per [RFC5910] with 1380 type="unsignedShort" and isRequired="true". 1382 Contains the Key protocol value per [RFC5910] 1383 with type="unsignedByte" and isRequired="true". 1385 Contains the Key algorithm value per [RFC5910] 1386 with type="unsignedByte" and isRequired="true". 1388 Contains the public key value per [RFC5910] with 1389 type="secDNS:keyType" and isRequired="true". 1391 The following "csvDomain" field elements MAY be used in the "dnssec" 1392 element: 1394 Indicates a child's preference for the 1395 number of seconds after signature generation when the parent's 1396 signature on the DS information provided by the child will expire 1397 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1399 The following "domain" fields, defined for the "domain" CSV File 1400 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1401 element: 1403 Domain name of the domain name object associated 1404 with the DNSSEC record and isRequired="true". 1406 Example of a "dnssec" element with 1407 the DS Data Interface of [RFC5910]: 1409 1410 ... 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1423 dnssec-ds-YYYYMMDD.csv 1424 1425 1426 1427 ... 1428 1429 ... 1431 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1432 contains two DS records for domain1.example. 1434 domain1.example,604800,30730,8,2,91C9B176EB////F1C46F6A55 1435 domain1.example,604800,61882,8,2,9F8FEAC94B////1272AF09F3 1437 Example of a "dnssec" element with 1438 the Key Data Interface of [RFC5910]: 1440 1441 ... 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1454 dnssec-key-YYYYMMDD.csv 1455 1456 1457 1458 ... 1459 1460 ... 1462 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1463 contains two key records for domain1.example. 1465 domain1.example,604800,257,3,8,AwEAAZD1+z////G1jqviK8c= 1466 domain1.example,604800,257,3,8,AwEAAbntWP////vwDitt940= 1468 5.1.2.1.7. "domainTransfer" CSV File Definition 1470 The "domainTransfer" CSV File Definition defines the fields and CSV 1471 file references used for the domain name object pending and completed 1472 transfer records. No additional field elements were added for use in 1473 the "domainTransfer" element. 1475 The following "rdeCsv" fields, defined in section CSV common field 1476 elements (Section 4.6.2.2), MUST be used in the "domainTransfer" 1477 element: 1479 State of the most recent transfer request with 1480 isRequired="true". 1482 Identifier of the registrar, defined in Section 5.4, 1483 of the client that requested the transfer with isRequired="true". 1485 Date and time that the transfer was requested with 1486 isRequired="true". 1488 Identifier of the registrar, defined in Section 5.4, 1489 of the client that should take or took action with 1490 isRequired="true". 1492 Date and time that the transfer action should be 1493 taken or has been taken with isRequired="true". 1495 The following "rdeCsv" fields, defined in section CSV common field 1496 elements (Section 4.6.2.2), MAY be used in the "domainTransfer" 1497 element: 1499 Expiration date if the transfer command caused or 1500 causes a change in the validity period. 1502 Identifier of the client that requested the transfer. 1504 Identifier of the client that should take or took 1505 action for transfer. 1507 The following "csvDomain" fields, defined for the "domain" CSV File 1508 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1509 element: 1511 Domain name of the domain name object involved in 1512 the transfer with isRequired="true". 1514 Example of a "domainTransfer" 1515 element. 1517 ... 1518 1519 ... 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1535 domainTransfer-YYYYMMDD.csv 1536 1537 1538 1539 ... 1540 1541 ... 1543 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1544 file contains one domain transfer record with a pending status. 1546 domain1.example,pending,registrarX,clientY, 1547 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1548 2025-04-03T22:00:00.0Z 1550 5.1.2.2. 1552 The is used to hold the deleted domain name 1553 objects in a Differential or Incremental Deposit. All the domain 1554 name object data is deleted as part of a cascade delete. The 1555 is split into separate CSV file definitions using 1556 named elements with the "name" attribute. The following 1557 section defines the supported domain name deletes CSV file 1558 definition. 1560 5.1.2.2.1. "domain" Deletes CSV File Definition 1562 The following "csvDomain" field elements MUST be used in the deletes 1563 "domain" element: 1565 Domain name field with type="eppcom:labelType" and 1566 isRequired="true". 1568 Example of a "domain" element: 1570 ... 1571 1572 ... 1573 1574 1575 1576 1577 1578 1580 domain-delete-YYYYMMDD.csv 1581 1582 1583 1584 ... 1585 1586 ... 1588 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1589 file contains two domain name records. 1591 domain1.example 1592 domain2.example 1594 5.2. Host Object 1596 The host object is based on the EPP host name mapping in [RFC5732]. 1597 The host object supports both the XML Model and the CSV Model, 1598 defined in Models (Section 2) section. The elements used for both 1599 models are defined in the following sections. Both the 1600 and elements contain one or more 1601 elements with a set of named CSV file definitions using 1602 the "name" attribute. 1604 5.2.1. XML Model 1606 There are two elements used in the data escrow of the host objects 1607 for the XML model including the , under the 1608 element, and the element, under 1609 the element. 1611 A element substitutes for the 1612 abstract element to define a concrete definition of a host. The 1613 element can be replaced by other host 1614 definitions using the XML schema substitution groups feature. 1616 5.2.1.1. element 1618 The RDE host object is based on the EPP host response for an 1619 authorized client (Section 3.1.2. of [RFC5732]). 1621 The OPTIONAL element contains the following child elements: 1623 o A element that contains the fully-qualified name of the 1624 host object. 1626 o A element that contains the repository object identifier 1627 assigned to the host object when the object was created. 1629 o One or more elements that describe the status of the host 1630 object. 1632 o Zero or more elements that contain the IP addresses 1633 associated with the host object. 1635 o A element that contains the identifier of the sponsoring 1636 registrar. 1638 o An OPTIONAL element that contains the identifier of the 1639 registrar that created the host object. An OPTIONAL client 1640 attribute is used to specify the client that performed the 1641 operation. 1643 o An OPTIONAL element that contains the date and time of 1644 host-object creation. 1646 o An OPTIONAL element that contains the identifier of the 1647 registrar that last updated the host object. This element MUST 1648 NOT be present if the host object has never been modified. An 1649 OPTIONAL client attribute is used to specify the client that 1650 performed the operation. 1652 o An OPTIONAL element that contains the date and time of 1653 the most recent host-object modification. This element MUST NOT 1654 be present if the host object has never been modified. 1656 o An OPTIONAL element that contains the date and time of 1657 the most recent host object successful transfer. This element 1658 MUST NOT be present if the domain name object has never been 1659 transfered. 1661 Example of object: 1663 ... 1664 1665 ns1.example1.example 1666 Hns1_example_test-TEST 1667 1668 1669 192.0.2.2 1670 192.0.2.29 1671 2001:DB8:1::1 1672 RegistrarX 1673 RegistrarX 1674 1999-05-08T12:10:00.0Z 1675 RegistrarX 1676 2009-10-03T09:34:00.0Z 1677 1678 ... 1680 5.2.1.2. object 1682 The element contains the fully-qualified domain name 1683 of a host that was deleted. The element also 1684 supports host removal based on roid to support SRS systems in which 1685 different hosts with the same fully-qualified domain name are active 1686 at the same time. 1688 Example of object: 1690 ... 1691 1692 ... 1693 1694 ns1.example.example 1695 1696 ... 1697 1698 ... 1700 5.2.2. CSV Model 1702 For the CSV Model of the host object, the child 1703 element of the element is used to hold the new or 1704 updated host objects for the deposit. The child 1705 element of the element is used to hold the deleted or 1706 purged host objects for the deposit. 1708 Differential and Incremental Deposits are based on changes to the 1709 host objects. The updated host object data under the 1710 element is a cascade replace down all of the host 1711 CSV files starting with the parent "host" CSV File Definition 1712 (Section 5.2.2.1.1). The child CSV file definitions include a 1713 field. All the child CSV file 1714 definition data for the host objects in the parent "host" CSV File 1715 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1716 using the data in the child CSV files. The deleted host object data 1717 under the element is a cascade delete starting from 1718 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1720 5.2.2.1. 1722 The is used to hold the new or updated host object 1723 information for the deposit. The is split into 1724 separate CSV file definitions using named elements with 1725 the "name" attribute. The following sections include the supported 1726 host CSV file definitions. 1728 5.2.2.1.1. "host" CSV File Definition 1730 The "host" CSV File Definition defines the fields and CSV file 1731 references used for the host object records. 1733 The following "csvHost" field elements MUST be used in the "host" 1734 element: 1736 Host name field with type="eppcom:labelType" and 1737 isRequired="true". 1739 The following "rdeCsv" fields, defined in section CSV common field 1740 elements (Section 4.6.2.2), MUST be used in the "host" 1741 element: 1743 Repository Object IDentifier (ROID) assigned to the 1744 host object with isRequired="true". 1746 The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the 1747 "host" element: 1749 or A choice of: 1751 Identifier of the sponsoring client with 1752 isRequired="true". 1754 Contains the Globally Unique Registrar 1755 Identifier (GURID) assigned by ICANN with 1756 type="positiveInteger" and "isRequired"="true". 1758 Identifier of the registrar, defined in Section 5.4, 1759 of the client that created the host object. 1761 Identifier of the client that created the host 1762 object. 1764 Identifier of the registrar, defined in Section 5.4, 1765 of the client that last updated the host object. 1767 Identifier of the client that last updated the host 1768 object. 1770 Date and time that the host object was created. 1772 Date and time that the host object was last 1773 updated. This field MUST NOT be set if the domain name object has 1774 never been modified. 1776 Date and time that the host object was last 1777 transferred. This field MUST NOT be set if the domain name object 1778 has never been transferred. 1780 Example of a "host" element. 1782 ... 1783 1784 ... 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1801 host-YYYYMMDD.csv 1802 1803 1804 1805 ... 1806 1807 ... 1809 Example of the corresponding host-YYYYMMDD.csv file. The file 1810 contains six host records with four being internal hosts and two 1811 being external hosts. 1813 ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX, 1814 clientY,1999-05-08T12:10:00.0Z,registrarX, 1815 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1816 ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX, 1817 clientY,1999-05-08T12:10:00.0Z,registrarX, 1818 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1819 ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX, 1820 clientY,1999-05-08T12:10:00.0Z,registrarX, 1821 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1822 ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, 1823 clientY,1999-05-08T12:10:00.0Z,registrarX, 1824 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1825 ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, 1826 clientY,1999-05-08T12:10:00.0Z,registrarX, 1827 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1828 ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, 1829 clientY,1999-05-08T12:10:00.0Z,registrarX, 1830 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1832 5.2.2.1.2. "hostStatuses" CSV File Definition 1834 The "hostStatuses" CSV File Definition defines the fields and CSV 1835 file references used for the host object statuses. 1837 The following "csvHost" fields, defined for the "host" CSV File 1838 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1839 element: 1841 The status of the host with 1842 type="host:statusValueType" and isRequired="true". 1844 The following "rdeCsv" fields, defined in section CSV common field 1845 elements (Section 4.6.2.2), MUST be used in the "hostStatuses" 1846 element: 1848 Host object Registry Object IDentifier (ROID) 1849 assigned to the host object with isRequired="true". 1851 The following "rdeCsv" fields, defined in section CSV common field 1852 elements (Section 4.6.2.2), MAY be used in the "hostStatuses" 1853 element: 1855 Host object status description which is 1856 free form text describing the rationale for the status. 1858 Language of the field. 1860 Example of a "hostStatuses" element. 1862 ... 1863 1864 ... 1865 1866 1867 1868 1869 1870 1871 1872 1873 1875 hostStatuses-YYYYMMDD.csv 1876 1877 1878 1879 ... 1880 1881 ... 1883 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1884 file contains the statuses for the six host names 1885 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example, 1886 ns2.domain2.example, ns1.example.net and ns2.example.net. 1888 Hns1_domain1_test-TEST,ok,, 1889 Hns2_domain1_test-TEST,ok,, 1890 Hns1_domain2_test-TEST,ok,, 1891 Hns2_domain2_test-TEST,ok,, 1892 Hns1_example_test-TEST,ok,, 1893 Hns2_example_test-TEST,ok,, 1895 5.2.2.1.3. "hostAddresses" CSV File Definition 1897 The "hostAddresses" CSV File Definition defines the fields and CSV 1898 file references used for the host object IP addresses. 1900 The following "csvHost" field elements MUST be used in the 1901 "hostAddresses" element: 1903 IP addresses associated with the host object with 1904 type="host:addrStringType". The attribute "isRequired" MUST equal 1905 "true". 1907 IP addresses version associated with the host 1908 object with type="host:ipType". "host:ipType" has the enumerated 1909 values of "v4" or "v6". The attribute "isRequired" MUST equal 1910 "true". 1912 The following "rdeCsv" fields, defined in section CSV common field 1913 elements (Section 4.6.2.2), MUST be used in the "hostAddresses" 1914 element: 1916 Host object Registry Object IDentifier (ROID) 1917 assigned to the host object with isRequired="true". 1919 Example of a "hostAddresses" element. 1921 ... 1922 1923 ... 1924 1925 1926 1927 1928 1929 1930 1931 1933 hostAddresses-YYYYMMDD.csv 1934 1935 1936 1937 ... 1938 1939 ... 1941 Example of the corresponding hostAddresses-YYYYMMDD.csv file. The 1942 file contains the IP addresses for the host names 1943 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and 1944 ns2.domain2.example. 1946 Hns1_domain1_test-TEST,192.0.2.1,v4 1947 Hns2_domain1_test-TEST,2001:DB8::1,v6 1948 Hns1_domain2_test-TEST,192.0.2.2,v4 1949 Hns2_domain2_test-TEST,2001:DB8::2,v6 1951 5.2.2.2. 1953 The is used to hold the deleted host objects in a 1954 Differential or Incremental Deposit. All the host object data is 1955 deleted as part of a cascade delete. The is split 1956 into separate CSV file definitions using named elements 1957 with the "name" attribute. The following section defines the 1958 supported host deletes CSV file definition. 1960 5.2.2.2.1. "host" Deletes CSV File Definition 1962 The following "rdeCsv" fields, defined in section CSV common field 1963 elements (Section 4.6.2.2), MUST be used in the "host" 1964 element: 1966 Repository Object IDentifier (ROID) assigned to the 1967 host object with isRequired="true". 1969 Example of a "host" element. 1971 ... 1972 1973 ... 1974 1975 1976 1977 1978 1979 1981 host-delete-YYYYMMDD.csv 1982 1983 1984 1985 ... 1986 1987 ... 1989 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1990 host records. 1992 Hns1_domain1_test-TEST 1993 Hns2_domain1_test-TEST 1994 Hns1_domain2_test-TEST 1995 Hns2_domain2_test-TEST 1997 5.3. Contact Object 1999 The contact object is based on the EPP contact name mapping in 2000 [RFC5733]. The contact object supports both the XML Model and the 2001 CSV Model, defined in Models (Section 2) section. The elements used 2002 for both models are defined in the following sections. 2004 5.3.1. XML Model 2006 There are two elements used in the data escrow of the contact objects 2007 for the XML model including the , under the 2008 element, and the element, 2009 under the element. 2011 A element substitutes for the abstract 2012 element to define a concrete definition of a contact. The 2013 element can be replaced by other contact 2014 definitions using the XML schema substitution groups feature. 2016 5.3.1.1. object 2018 The contact object is based on the EPP contact response for an 2019 authorized client (Section 3.1.2. of [RFC5733]) with some additions 2020 including the data from an EPP Query Response, see 2021 Section 3.1.3. of [RFC5733]. 2023 The OPTIONAL element contains the following child elements: 2025 o A element that contains the server-unique identifier of the 2026 contact object 2028 o A element that contains the Repository Object IDentifier 2029 assigned to the contact object when the object was created. 2031 o One or more elements that describe the status of the 2032 contact object. 2034 o One or two elements that contain postal-address 2035 information. Two elements are provided so that address 2036 information can be provided in both internationalized and 2037 localized forms; a "type" attribute is used to identify the two 2038 forms. If an internationalized form (type="int") is provided, 2039 element content MUST be represented in a subset of UTF-8 that can 2040 be represented in the 7-bit US-ASCII character set. If a 2041 localized form (type="loc") is provided, element content MAY be 2042 represented in unrestricted UTF-8. The element 2043 contains the following child elements: 2045 * A element that contains the name of the individual or 2046 role represented by the contact. 2048 * An OPTIONAL element that contains the name of the 2049 organization with which the contact is affiliated. 2051 * An element that contains address information associated 2052 with the contact. An element contains the following 2053 child elements: 2055 + One, two, or three OPTIONAL elements that contain 2056 the contact's street address. 2058 + A element that contains the contact's city. 2060 + An OPTIONAL element that contains the contact's state 2061 or province. 2063 + An OPTIONAL element that contains the contact's postal 2064 code. 2066 + A element that contains the contact's two-letter 2067 country code. 2069 o An OPTIONAL element that contains the contact's voice 2070 telephone number. 2072 o An OPTIONAL element that contains the contact's facsimile 2073 telephone number. 2075 o An element that contains the contact's email address. 2077 o A element that contains the identifier of the sponsoring 2078 registrar. 2080 o An OPTIONAL element that contains the identifier of the 2081 registrar that created the contact object. An OPTIONAL client 2082 attribute is used to specify the client that performed the 2083 operation. 2085 o An OPTIONAL element that contains the date and time of 2086 contact-object creation. 2088 o An OPTIONAL element that contains the identifier of the 2089 registrar that last updated the contact object. This element MUST 2090 NOT be present if the contact has never been modified. An 2091 OPTIONAL client attribute is used to specify the client that 2092 performed the operation. 2094 o An OPTIONAL element that contains the date and time of 2095 the most recent contact-object modification. This element MUST 2096 NOT be present if the contact object has never been modified. 2098 o An OPTIONAL element that contains the date and time of 2099 the most recent contact object successful transfer. This element 2100 MUST NOT be present if the contact object has never been 2101 transferred. 2103 o An OPTIONAL element that contains the following child 2104 elements related to the last transfer request of the contact 2105 object: 2107 * A element that contains the state of the most recent 2108 transfer request. 2110 * A element that contains the identifier of the registrar 2111 that requested the domain name object transfer. An OPTIONAL 2112 client attribute is used to specify the client that performed 2113 the operation. 2115 * An element that contains the identifier of the registrar 2116 that should act upon a PENDING transfer request. For all other 2117 status types, the value identifies the registrar that took the 2118 indicated action. An OPTIONAL client attribute is used to 2119 specify the client that performed the operation. 2121 * A element that contains the date and time that the 2122 transfer was requested. 2124 * An element that contains the date and time of a 2125 required or completed response. For a PENDING request, the 2126 value identifies the date and time by which a response is 2127 required before an automated response action will be taken by 2128 the registry. For all other status types, the value identifies 2129 the date and time when the request was completed. 2131 o An OPTIONAL element that identifies elements that 2132 requiring exceptional server-operator handling to allow or 2133 restrict disclosure to third parties. See Section 2.9 of 2134 [RFC5733] for a description of the child elements contained within 2135 the element. 2137 Example object: 2139 ... 2140 2141 sh8013 2142 Csh8013-TEST 2143 2144 2145 2146 John Doe 2147 Example Inc. 2148 2149 123 Example Dr. 2150 Suite 100 2151 Dulles 2152 VA 2153 20166-6503 2154 US 2155 2156 2157 +1.7035555555 2158 +1.7035555556 2159 jdoe@example.example 2160 RegistrarX 2161 RegistrarX 2162 2009-09-13T08:01:00.0Z 2163 RegistrarX 2164 2009-11-26T09:10:00.0Z 2165 2009-12-03T09:05:00.0Z 2166 2167 pending 2168 clientW 2169 2011-03-08T19:38:00.0Z 2170 RegistrarX 2171 2011-03-13T23:59:59.0Z 2172 2173 2174 2175 2176 2177 2178 ... 2180 5.3.1.2. object 2182 The element contains the id of a contact that was 2183 deleted. 2185 Example of object: 2187 ... 2188 2189 ... 2190 2191 sh8013-TEST 2192 co8013-TEST 2193 2194 ... 2195 2196 ... 2198 5.3.2. CSV Model 2200 For the CSV Model of the contact object, the 2201 child element of the element is used to hold the new 2202 or updated contacts objects for the deposit. The 2203 child element of the element is 2204 used to hold the deleted or purged contact objects for the deposit. 2205 Both the and elements 2206 contain one or more elements with a set of named CSV 2207 file definitions using the "name" attribute. 2209 Differential and Incremental Deposits are based on changes to the 2210 contact objects. The updated contact object data under the 2211 element is a cascade replace down all of the 2212 contact CSV files starting with the parent "contact" CSV File 2213 Definition (Section 5.3.2.1.1). The child CSV file definitions 2214 include a field. All the child CSV 2215 file definition data for the contact objects in the parent "contact" 2216 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2217 then set using the data in the child CSV files. The deleted contact 2218 object data under the element is a cascade 2219 delete starting from the "contact" Deletes CSV File Definition 2220 (Section 5.3.2.2.1). 2222 5.3.2.1. 2224 The is used to hold the new or updated contact 2225 object information for the deposit. The is 2226 split into separate CSV file definitions using named 2227 elements with the "name" attribute. The following sections include 2228 the supported contact CSV file definitions. 2230 5.3.2.1.1. "contact" CSV File Definition 2232 The "contact" CSV File Definition defines the fields and CSV file 2233 references used for the contact object records. 2235 The following "csvContact" field elements MUST be used in the 2236 "contact" element: 2238 Contains the server-unique contact identifier with 2239 type="eppcom:clIDType" and isRequired="true". 2241 Contains the contact's email address with 2242 type="eppcom:minTokenType" and isRequired="true". 2244 The following field elements MAY be used in the "contact" 2245 element: 2247 Contains the contact's voice telephone number 2248 with type="contact:e164StringType". 2250 Contains the contact's voice telephone number 2251 extension with type="token". 2253 Contains the contact's facsimile telephone number 2254 with type="contact:e164StringType". 2256 Contains the contact's facsimile telephone 2257 number extension with type="token". 2259 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 2260 "contact" element: 2262 The Registry Object IDentifier (ROID) for the contact 2263 object with isRequired="true". 2265 or A choice of: 2267 Identifier of the sponsoring client with 2268 isRequired="true". 2270 Contains the Globally Unique Registrar 2271 Identifier (GURID) assigned by ICANN with 2272 type="positiveInteger" and "isRequired"="true". 2274 The following "rdeCsv" fields, defined in section CSV common field 2275 elements (Section 4.6.2.2), MAY be used in the "contact" 2276 element: 2278 Identifier of the registrar, defined in Section 5.4, 2279 of the client that created the contact object. 2281 Identifier of the client that created the contact 2282 object. 2284 Identifier of the registrar, defined in Section 5.4, 2285 of the client that last updated the contact object. 2287 Identifier of the client that last updated the 2288 contact object. 2290 Created date and time of the contact object. 2292 Date and time of the last update to the contact 2293 object. This field MUST NOT be set if the domain name object has 2294 never been modified. 2296 Date and time of the last transfer for the contact 2297 object. This field MUST NOT be set if the domain name object has 2298 never been transferred. 2300 Example of a "contact" element. 2302 ... 2303 2304 ... 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2325 contact-YYYYMMDD.csv 2326 2327 2328 2329 ... 2330 2331 ... 2333 Example of the contact-YYYYMMDD.csv file. The file contains nine 2334 object contact records. 2336 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2337 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2338 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2339 2009-11-26T09:10:00.0Z 2340 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2341 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2342 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2343 2009-11-26T09:10:00.0Z 2344 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2345 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2346 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2347 2009-11-26T09:10:00.0Z 2348 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2349 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2350 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2351 2009-11-26T09:10:00.0Z 2352 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2353 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2354 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2355 2009-11-26T09:10:00.0Z 2356 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2357 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2358 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2359 2009-11-26T09:10:00.0Z 2360 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2361 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2362 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2363 2009-11-26T09:10:00.0Z 2364 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2365 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2366 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2367 2009-11-26T09:10:00.0Z 2368 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2369 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2370 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2371 2009-11-26T09:10:00.0Z 2373 5.3.2.1.2. "contactStatuses" CSV File Definition 2375 The "contactStatuses" CSV File Definition defines the fields and CSV 2376 file references used for the contact object statuses. 2378 The following "csvContact" field elements, defined for the "contact" 2379 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2380 "contactStatuses" element: 2382 Server-unique contact identifier of status with 2383 isRequired="true" and parent="true". 2385 The status of the contact with 2386 type="contact:statusValueType" and isRequired="true". 2388 The following "rdeCsv" fields, defined in section CSV common field 2389 elements (Section 4.6.2.2), MAY be used in the "contactStatuses" 2390 element: 2392 The contact object status description 2393 which is free form text describing the rationale for the status. 2395 Language of the field. 2397 Example of a "contactStatuses" 2398 element. 2400 ... 2401 2402 ... 2403 2404 2405 2406 2407 2408 2409 2410 2411 2413 contactStatuses-YYYYMMDD.csv 2414 2415 2416 2417 ... 2418 2419 ... 2421 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2422 file contains the statuses for the nine contact identifiers. 2424 domain1admin,ok,, 2425 domain1tech,ok,, 2426 domain1billing,ok,, 2427 domain2admin,ok,, 2428 domain2tech,ok,, 2429 domain2billing,ok,, 2430 xnabc123admin,ok,, 2431 xnabc123tech,ok,, 2432 xnabc123billing,ok,, 2434 5.3.2.1.3. "contactPostal" CSV File Definition 2436 The "contactPostal" CSV File Definition defines the fields and CSV 2437 file references used for the contact postal info object records. 2439 The following "csvContact" field elements MUST be used in the 2440 "contactPostal" element: 2442 Contains the form of the postal-address 2443 information with type="contact:postalLineType" and 2444 isRequired="true". This field specifies the form ("int" or 2445 "loc"), as defined in Section 4.6.3, of the , 2446 , , , 2447 , , fields. 2449 Contains the contact's name of the individual or 2450 role represented by the contact with type="contact:postalLineType" 2451 and isRequired="true". An OPTIONAL "isLoc" attribute is used to 2452 indicate the localized or internationalized form as defined in 2453 Section 4.6.3. 2455 Contains the contact's street address line with 2456 type="contact:fPostalLineType". An index attribute is required to 2457 indicate which street address line the field represents with index 2458 "0" for the first line and incrementing for each line up to index 2459 "2" for the third line. An OPTIONAL "isLoc" attribute is used to 2460 indicate the localized or internationalized form as defined in 2461 Section 4.6.3. 2463 Contains the contact's city with 2464 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2465 "isLoc" attribute is used to indicate the localized or 2466 internationalized form as defined in Section 4.6.3. 2468 Contains the contact's country code with 2469 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2470 attribute is used to indicate the localized or internationalized 2471 form as defined in Section 4.6.3. 2473 The following "csvContact" field elements MAY be used in the 2474 "contactPostal" element: 2476 Contains the name of the organization with which 2477 the contact is affiliated with type="contact:optPostalLineType". 2478 An OPTIONAL "isLoc" attribute is used to indicate the localized or 2479 internationalized form as defined in Section 4.6.3. 2481 Contains the contact's state or province with 2482 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2483 is used to indicate the localized or internationalized form as 2484 defined in Section 4.6.3. 2486 Contains the contact's postal code with 2487 type="contact:pcType". An OPTIONAL "isLoc" attribute is used to 2488 indicate the localized or internationalized form as defined in 2489 Section 4.6.3. 2491 The following "csvContact" fields, defined for the "contact" CSV File 2492 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2493 element: 2495 Server-unique contact identifier for the contact 2496 object with isRequired="true" and parent="true". 2498 Example of a "contactPostal" 2499 element. 2501 ... 2502 2503 ... 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2521 contactPostal-YYYYMMDD.csv 2522 2523 2524 2525 ... 2526 2527 ... 2529 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2530 nine contact postal records. 2532 domain1admin,int,"John Doe","Example Inc.", 2533 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2534 domain1tech,int,"John Doe","Example Inc.", 2535 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2536 domain1billing,int,"John Doe","Example Inc.", 2537 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2538 domain2admin,int,"John Doe","Example Inc.", 2539 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2540 domain2tech,int,"John Doe","Example Inc.", 2541 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2542 domain2billing,int,"John Doe","Example Inc.", 2543 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2544 xnabc123admin,int,"John Doe","Example Inc.", 2545 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2546 xnabc123tech,int,"John Doe","Example Inc.", 2547 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2548 xnabc123billing,int,"John Doe","Example Inc.", 2549 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2551 5.3.2.1.4. "contactTransfer" CSV File Definition 2553 The "contactTransfer" CSV File Definition defines the fields and CSV 2554 file references used for the contact object pending and completed 2555 transfer records. No additional field elements were added for use in 2556 the "contactTransfer" element. The 2557 following "rdeCsv" fields, defined in section CSV common field 2558 elements (Section 4.6.2.2), MUST be used in the "contactTransfer" 2559 element: 2561 State of the most recent transfer request with 2562 isRequired="true". 2564 Identifier of the registrar, defined in Section 5.4, 2565 of the client that requested the transfer with isRequired="true". 2567 Date and time that the transfer was requested with 2568 isRequired="true". 2570 Identifier of the registrar, defined in Section 5.4, 2571 of the client that should take or took action with 2572 isRequired="true". 2574 Date and time that the transfer action should be 2575 taken or has been taken with isRequired="true". 2577 The following "rdeCsv" fields, defined in section CSV common field 2578 elements (Section 4.6.2.2), MAY be used in the "contactTransfer" 2579 element: 2581 Identifier of the client that requested the transfer. 2583 Identifier of the client that should take or took 2584 action for transfer. 2586 The following "csvContact" fields, defined for the "contact" CSV File 2587 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2588 element: 2590 Server-unique contact identifier for the contact 2591 object with isRequired="true". 2593 Example of a "contactTransfer" 2594 element. 2596 ... 2597 2598 ... 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2613 contactTransfer-YYYYMMDD.csv 2614 2615 2616 2617 ... 2618 2619 ... 2621 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2622 one contact transfer record in pending status. 2624 xnabc123admin,clientApproved,registrarX,clientX, 2625 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2627 5.3.2.1.5. "contactDisclose" CSV File Definition 2629 The "contactDisclose" CSV File Definition defines the fields and CSV 2630 file references used for the contact disclose object records. 2632 The following "csvContact" field elements MAY be used in the 2633 "contactDisclose" element: 2635 Contains flag with a value of "true" or 2636 "1" (one) notes the preference to allow disclosure of the 2637 specified elements as an exception to the stated data-collection 2638 policy. A value of "false" or "0" (zero) notes a client 2639 preference to not allow disclosure of the specified elements as an 2640 exception to the stated data-collection policy with 2641 type="boolean". The additional fields define specific exceptional 2642 disclosure preferences based on the 2643 field. 2645 Exceptional disclosure preference flag 2646 for the localized form of the contact name with type="boolean". 2648 Exceptional disclosure preference flag 2649 for the internationalized form of the contact name with 2650 type="boolean". 2652 Exceptional disclosure preference flag 2653 for the localized form of the contact organization with 2654 type="boolean". 2656 Exceptional disclosure preference flag 2657 for the internationalized form of the contact organization with 2658 type="boolean". 2660 Exceptional disclosure preference flag 2661 for the localized form of the contact address with type="boolean". 2663 Exceptional disclosure preference flag 2664 for the internationalized form of the contact address with 2665 type="boolean". 2667 Exceptional disclosure preference flag 2668 of the contact voice telephone number with type="boolean". 2670 Exceptional disclosure preference flag of 2671 the contact facsimile telephone number with type="boolean". 2673 Exceptional disclosure preference flag 2674 of the contact email address with type="boolean". 2676 The following "csvContact" fields, defined for the "contact" CSV File 2677 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2678 element: 2680 Server-unique contact identifier for the contact 2681 object with isRequired="true". 2683 Example of a "contactDisclose" 2684 element. 2686 ... 2687 2688 ... 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2706 contactDisclose-YYYYMMDD.csv 2707 2708 2709 2710 ... 2711 2712 ... 2714 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2715 one disclosure records, disabling disclosure of voice, fax, and 2716 email. 2718 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2720 5.3.2.2. 2722 The is used to hold the deleted contact objects 2723 in a Differential or Incremental Deposit. All the contact object 2724 data is deleted as part of a cascade delete. The 2725 is split into separate CSV file definitions 2726 using named elements with the "name" attribute. The 2727 following section defines the supported contact deletes CSV file 2728 definition. 2730 5.3.2.2.1. "contact" Deletes CSV File Definition 2732 The following "csvContact" field elements MUST be used in the deletes 2733 "contact" element: 2735 Contains the server-unique contact identifier with 2736 type="eppcom:clIDType" and isRequired="true". 2738 Example of a "contact" element. 2740 ... 2741 2742 ... 2743 2744 2745 2746 2747 2748 2750 contact-delete-YYYYMMDD.csv 2751 2752 2753 2754 ... 2755 2756 ... 2758 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2759 six contact records. 2761 domain1admin 2762 domain1tech 2763 domain1billing 2764 domain2admin 2765 domain2tech 2766 domain2billing 2768 5.4. Registrar Object 2770 The registrar object represents the sponsoring client for other 2771 objects, and is typically referred to as the sponsoring registrar. 2772 The registrar object supports both the XML Model and the CSV Model, 2773 defined in Section 2. The elements used for both models are defined 2774 in the following sections. 2776 5.4.1. XML Model 2778 There are two elements used in the data escrow of the registrar 2779 objects for the XML model including the , 2780 under the element, and the 2781 element, under the element. 2783 A element substitutes for the 2784 abstract element to define a 2785 concrete definition of a registrar. The 2786 element can be replaced by other 2787 domain definitions using the XML schema substitution groups feature. 2789 5.4.1.1. element 2791 The element contains the following child elements: 2793 o An element that contains the Registry-unique identifier of 2794 the registrar object. This has a superordinate relationship 2795 to a subordinate , or of domain, contact and 2796 host objects. 2798 o An element that contains the name of the registrar. 2800 o An OPTIONAL element that contains the Globally Unique 2801 Registrar Identifier (GURID) assigned by ICANN. 2803 o An OPTIONAL element that contains the operational status 2804 of the registrar. Possible values are: ok, readonly and 2805 terminated. 2807 o One or two OPTIONAL elements that contain postal- 2808 address information. Two elements are provided so that address 2809 information can be provided in both internationalized and 2810 localized forms; a "type" attribute is used to identify the two 2811 forms. If an internationalized form (type="int") is provided, 2812 element content MUST be represented in a subset of UTF-8 that can 2813 be represented in the 7-bit US-ASCII character set. If a 2814 localized form (type="loc") is provided, element content MAY be 2815 represented in unrestricted UTF-8. The element 2816 contains the following child elements: 2818 * A element that contains address information associated 2819 with the registrar. The element contains the following 2820 child elements: 2822 + One, two, or three OPTIONAL elements that contain 2823 the registrar's street address. 2825 + A element that contains the registrar's city. 2827 + An OPTIONAL element that contains the registrar's state 2828 or province. 2830 + An OPTIONAL element that contains the registrar's 2831 postal code. 2833 + A element that contains the registrar's country code. 2835 o An OPTIONAL element that contains the registrar's voice 2836 telephone number. 2838 o An OPTIONAL element that contains the registrar's facsimile 2839 telephone number. 2841 o An OPTIONAL element that contains the registrar's email 2842 address. 2844 o An OPTIONAL element that contains the registrar's URL. 2846 o An OPTIONAL elements that contains whois information. 2847 The element contains the following child elements: 2849 * An OPTIONAL element that contains the name of the 2850 registrar WHOIS server listening on TCP port 43 as specified in 2851 [RFC3912]. 2853 * An OPTIONAL element that contains the name of the 2854 registrar WHOIS server listening on TCP port 80/443. 2856 o An OPTIONAL element that contains the date and time of 2857 registrar-object creation. 2859 o An OPTIONAL element that contains the date and time of 2860 the most recent registrar-object modification. This element MUST 2861 NOT be present if the registrar-object has never been modified. 2863 Example of a object: 2865 ... 2866 2867 RegistrarX 2868 Registrar X 2869 8 2870 ok 2871 2872 2873 123 Example Dr. 2874 Suite 100 2875 Dulles 2876 VA 2877 20166-6503 2878 US 2879 2880 2881 +1.7035555555 2882 +1.7035555556 2883 jdoe@example.example 2884 http://www.example.example 2885 2886 whois.example.example 2887 http://whois.example.example 2888 2889 2005-04-23T11:49:00.0Z 2890 2009-02-17T17:51:00.0Z 2891 2892 ... 2894 5.4.1.2. object 2896 The element contains the id of a registrar that 2897 was deleted. 2899 Example of object: 2901 ... 2902 2903 ... 2904 2905 agnt0001-TEST 2906 2907 ... 2908 2909 ... 2911 5.4.2. CSV Model 2913 For the CSV Model of the registrar object, the 2914 child element of the element 2915 is used to hold the new or updated registrar objects for the deposit. 2916 The child element of the element 2917 is used to hold the deleted or purged registrar objects for the 2918 deposit. Both the and 2919 elements contain one or more elements with a set of 2920 named CSV file definitions using the "name" attribute. 2922 Differential and Incremental Deposits are based on changes to the 2923 registrar objects. The updated registrar object data under the 2924 element is a cascade replace down all of the 2925 registrar CSV files starting with the parent "registrar" CSV File 2926 Definition (Section 5.4.2.1.1). The child CSV file definitions 2927 include a field. All the child CSV 2928 file definition data for the registrar objects in the parent 2929 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2930 deleted and then set using the data in the child CSV files. The 2931 deleted registrar object data under the 2932 element is a cascade delete starting from the "registrar" Deletes CSV 2933 File Definition (Section 5.4.2.2.1). 2935 5.4.2.1. 2937 The is used to hold the new or updated 2938 registrar object information for the deposit. The 2939 is split into separate CSV file definitions 2940 using named elements with the "name" attribute. The 2941 following sections include the supported contact CSV file 2942 definitions. 2944 5.4.2.1.1. "registrar" CSV File Definition 2946 The "registrar" CSV File Definition defines the fields and CSV file 2947 references used for the registrar object records. 2949 The following "csvRegistrar" field elements MUST be used in the 2950 "registrar" element: 2952 or A choice of: 2954 Contains the server-unique registrar 2955 identifier with type="eppcom:clIDType" and isRequired="true". 2957 Contains the Globally Unique Registrar 2958 Identifier (GURID) assigned by ICANN with 2959 type="positiveInteger" and "isRequired"="true". 2961 Contains the name of the registrar with 2962 type="normalizedString" and isRequired="true". 2964 The following field elements MAY be used in the "registrar" 2965 element: 2967 Contains the status of the registrar with 2968 type="csvRegistrar:statusValueType". 2970 Contains the ID assigned by ICANN with 2971 type="positiveInteger". This field is included in this section in 2972 addition to the section above to support optionally providing the 2973 field when the field is 2974 used. 2976 Contains the Whois URL of the registrar 2977 with type="anyURI". 2979 The following "rdeCsv" fields, defined in section CSV common field 2980 elements (Section 4.6.2.2), MAY be used in the "registrar" 2981 element: 2983 Created date and time of the registrar object. 2985 Date and time of the last update to the registrar 2986 object. This field MUST NOT be set if the domain name object has 2987 never been modified. 2989 URL for the registrar web home page. 2991 The following "csvContact" fields, defined in section Contact Object 2992 (Section 5.3), MAY be used in the "registrar" 2993 element: 2995 Registrar street address line with an "index" 2996 attribute that represents the order of the street address line 2997 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2998 indicate the localized or internationalized form, as defined in 2999 Section 4.6.3. 3001 Registrar city with an OPTIONAL "isLoc" attribute 3002 that is used to indicate the localized or internationalized form, 3003 as defined in Section 4.6.3. 3005 Registrar country code with an OPTIONAL "isLoc" 3006 attribute that is used to indicate the localized or 3007 internationalized form, as defined in Section 4.6.3. 3009 Registrar email address. The attribute 3010 "isRequired" MUST equal "false". 3012 Registrar state or province with an OPTIONAL 3013 "isLoc" attribute that is used to indicate the localized or 3014 internationalized form, as defined in Section 4.6.3. 3016 Registrar postal code with an OPTIONAL "isLoc" 3017 attribute that is used to indicate the localized or 3018 internationalized form, as defined in Section 4.6.3. 3020 Registrar voice telephone number. 3022 Registrar voice telephone number extension. 3024 Registrar facsimile telephone number. 3026 Registrar facsimile telephone number extension. 3028 Example of a "registrar" 3029 element. 3031 ... 3032 3033 ... 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3060 registrar-YYYYMMDD.csv 3061 3062 3063 3064 ... 3065 3066 ... 3068 Example of the registrar-YYYYMMDD.csv file. The file contains one 3069 registrar record. 3071 registrarX,"Example Inc.",8,ok,"123 Example Dr.", 3072 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3073 +1.7035555556,,jdoe@example.example,http://www.example.example, 3074 http://whois.example.example,2005-04-23T11:49:00.0Z, 3075 2009-02-17T17:51:00.0Z 3077 5.4.2.2. 3079 The is used to hold the deleted registrar 3080 objects in a Differential or Incremental Deposit. All the registrar 3081 object data is deleted as part of a cascade delete. The 3082 is split into separate CSV file definitions 3083 using named elements with the "name" attribute. The 3084 following section defines the supported registrar deletes CSV file 3085 definition. 3087 5.4.2.2.1. "registrar" Deletes CSV File Definition 3089 The following "csvRegistrar" field elements MUST be used in the 3090 deletes "registrar" element: 3092 or A choice of: 3094 Contains the server-unique registrar 3095 identifier with type="eppcom:clIDType" and isRequired="true". 3097 Contains the Globally Unique Registrar 3098 Identifier (GURID) assigned by ICANN with 3099 type="positiveInteger". The attribute "isRequired" MUST equal 3100 "true". 3102 Example of a "registrar" element. 3104 ... 3105 3106 ... 3107 3108 3109 3110 3111 3112 3114 registrar-delete-YYYYMMDD.csv 3115 3116 3117 3118 ... 3119 3120 ... 3122 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 3123 one registrar record. 3125 registrarZ 3127 5.5. IDN Table Reference Object 3129 The Internationalized Domain Names (IDN) table reference object is a 3130 pseudo-object that is used to provide a short reference to the IDN 3131 Table and Policy used in IDN registrations. The IDN reference object 3132 supports both the XML and the CSV Model, defined in the Models 3133 (Section 2) section. The elements used for both models are defined 3134 in the following sections. 3136 5.5.1. XML Model 3138 There is one element used in the data escrow of the IDN table 3139 reference objects for the XML model that is the , 3140 under the element. 3142 5.5.1.1. object 3144 The contains the following elements. An "id" 3145 attribute is used to specify an identifier for the IDN table. 3147 o An element that contains the URL of the IDN table that is 3148 being referenced. 3150 o A element that contains the URL of the IDN policy 3151 document. If IDN variants are generated algorithmically, the 3152 policy document MUST define the algorithm and the state of the 3153 implicit generated IDN variants. For a list of suggested states 3154 for implicit IDN variants, please see [variantTLDsReport]. 3156 Example of object: 3158 ... 3159 3160 3161 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3162 3163 3164 http://registro.br/dominio/regras.html 3165 3166 3167 ... 3169 5.5.2. CSV Model 3171 The IDN domain names, defined in Section 5.1, MAY have references to 3172 the IDN language identifier using the field 3173 element. The IDN table reference object defines the mapping of a 3174 language identifier to a language table URL. The language table URL 3175 defines the character code points that can be used for the language 3176 identifier. The elements used for the IDN table reference object is 3177 defined in this section. The child element of the 3178 element is used to hold the new or updated IDN table 3179 reference objects for the deposit. The child 3180 element of the element is used to hold the deleted or 3181 purged IDN table reference objects for the deposit. Both the 3182 and elements contain one or more 3183 elements with a set of named CSV file definitions using 3184 the "name" attribute. 3186 5.5.2.1. 3188 The is used to hold the new or updated IDN table 3189 reference object information for the deposit. The 3190 is split into separate CSV file definitions using named 3191 elements with the "name" attribute. The following sections include 3192 the supported IDN table reference CSV file definitions. 3194 5.5.2.1.1. "idnLanguage" CSV File Definition 3196 The "idnLanguage" CSV File Definition defines the fields and CSV file 3197 references used for the IDN table reference object records. 3199 The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be 3200 used in the "idnLanguage" element: 3202 The language identifier that matches the values 3203 for the field element in the "domain" CSV 3204 File Definition (Section 5.1.2.1.1) files. The attribute 3205 "isRequired" MUST equal "true". 3207 URL that defines the character code points that can be 3208 used for field in the "domain" CSV File 3209 Definition Section 5.1.2.1.1 files. The attribute "isRequired" 3210 MUST equal "true". 3212 Example of a "idnLanguage" element. 3214 ... 3215 3216 ... 3217 3218 3219 3220 3221 3222 3223 3225 idnLanguage-YYYYMMDD.csv 3226 3227 3228 3229 ... 3230 3231 ... 3233 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3234 contains two IDN language records. 3236 LANG-1, 3237 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3238 LANG-2, 3239 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3241 5.5.2.2. 3243 The is used to hold the deleted IDN table reference 3244 objects in a Differential or Incremental Deposit. The 3245 is split into separate CSV file definitions using 3246 named elements with the "name" attribute. The following 3247 section defines the supported IDN table reference deletes CSV file 3248 definition. 3250 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3252 The following "idnLanguage" field elements MUST be used in the 3253 deletes "idnLanguage" element: 3255 The language identifier that matches the values 3256 for the field element in the "domain" CSV 3257 File Definition (Section 5.1.2.1.1) files. The attribute 3258 "isRequired" MUST equal "true". 3260 Example of a "idnLanguage" element. 3262 ... 3263 3264 ... 3265 3266 3267 3268 3269 3270 3272 idnLanguage-delete-YYYYMMDD.csv 3273 3274 3275 3276 ... 3277 3278 ... 3280 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3281 contains one IDN language record. 3283 LANG-2 3285 5.6. NNDN Object 3287 An NNDN (NNDN's not domain name) can be used to store registry 3288 reserved names or (blocked, withheld or mirrored) IDN variants. 3290 Domain Name Registries may maintain domain names without their being 3291 persisted as domain objects in the registry system, for example, a 3292 list of reserved names not available for registration. The NNDN is a 3293 lightweight domain-like object that is used to escrow domain names 3294 not maintained as domain name objects. 3296 A domain name can only exist as a domain name object or an NNDN 3297 object, but not both. 3299 The NNDN object supports both the XML and the CSV Model, defined in 3300 the Models (Section 2) section. The elements used for both models 3301 are defined in the following sections. 3303 5.6.1. XML Model 3305 There are two elements used in the data escrow of the NNDN objects 3306 for the XML model including the , under the 3307 element, and the element, under the 3308 element. 3310 A element substitutes for the 3311 abstract element to define a concrete definition of an NNDN. The 3312 element can be replaced by other NNDN 3313 definitions using the XML schema substitution groups feature. 3315 5.6.1.1. object 3317 The element contains the following child elements: 3319 o An element that contains the fully-qualified qualified 3320 name of the NNDN. For IDNs the A-Label is used (see [RFC5891], 3321 Section 4.4). 3323 o An OPTIONAL element that contains the fully-qualified name 3324 of the NNDN in Unicode character set. It MUST be provided if 3325 available. 3327 o An OPTIONAL element that references the IDN 3328 Table used for the NNDN. This corresponds to the "id" attribute 3329 of the element. This element MUST be present if the 3330 NNDN is an IDN. 3332 o An OPTIONAL element is used to indicate that the 3333 NNDN is used for an IDN variant. This element contains the domain 3334 name used to generate the IDN variant. 3336 o A element that indicates the state of the NNDN: 3337 blocked, withheld or mirrored. 3339 * If an NNDN is considered undesirable for registration (i.e., 3340 unavailable for allocation to anyone), then the NNDN will be 3341 tagged as "blocked". 3343 * If an NNDN is considered a potential registration of a domain 3344 name object for a registrant, then the NNDN will be tagged as 3345 "withheld". This status is only used when the NNDN is used for 3346 an IDN variant. 3348 * If an NNDN is considered a mirrored IDN variant of a domain 3349 name object, then the NNDN will be tagged as "mirrored". A 3350 mirroringNS attribute is used to specify if the mirrored IDN 3351 variant uses the NS mirror mechanism, meaning that the 3352 activated variant domain name (i.e., NNDN) is delegated in the 3353 DNS using the same NS records as in the . The 3354 default value of mirroringNS is true. If another mechanism 3355 such as DNAME is used, the value of mirroringNS attribute MUST 3356 be false. 3358 o An OPTIONAL element that contains the date and time of 3359 the NNDN object creation. 3361 Example of an object: 3363 ... 3364 3365 xn--exampl-gva.example 3366 pt-BR 3367 example.example 3368 withheld 3369 2005-04-23T11:49:00.0Z 3370 3371 ... 3373 5.6.1.2. object 3375 The element contains the NNDN that was deleted, 3376 i.e., the . 3378 Example of an object: 3380 ... 3381 3382 ... 3383 3384 xn--pingino-q2a.example 3385 3386 ... 3387 3388 ... 3390 5.6.2. CSV Model 3392 For the CSV Model of the NNDN object, the child 3393 element of the element is used to hold the new or 3394 updated NNDN objects for the deposit. The child 3395 element of the element is used to hold the deleted or 3396 purged NNDN objects for the deposit. Both the and 3397 elements contain one or more elements 3398 with a set of named CSV file definitions using the 3399 "name" attribute. 3401 5.6.2.1. 3403 The is used to hold the new or updated NNDN object 3404 information for the deposit. The is split into 3405 separate CSV file definitions using named elements with 3406 the "name" attribute. The following sections include the supported 3407 NNDN CSV file definitions. 3409 5.6.2.1.1. "NNDN" CSV File Definition 3411 The "NNDN" CSV File Definition defines the fields and CSV file 3412 references used for the NNDN object records. 3414 The following "csvNNDN" field elements MUST be used in the "NNDN" 3415 element: 3417 Fully-qualified name of the NNDN with 3418 type="eppcom:labelType" and isRequired="true". For IDNs the 3419 A-Label is used (see [RFC5891], Section 4.4). 3421 State of the NNDN: blocked or withheld with 3422 type="rdeNNDN:nameState" and isRequired="true". See 3423 Section 5.6.1.1 for a description of the possible values for the 3424 element. 3426 The following field elements MAY be used in the "NNDN" 3427 element: 3429 Domain name used to generate the IDN variant 3430 with type="eppcom:labelType". 3432 Defines whether the "mirroring" 3433 uses the NS mirror mechanism, as described 3434 for the "mirroringNS" attribute in 3435 Section 5.6.1.1, with type="boolean". If the field element is not 3436 defined the default value is "true". 3438 The following "rdeCsv" fields, defined in section CSV common field 3439 elements (Section 4.6.2.2), MAY be used in the "NNDN" 3440 element: 3442 Created date and time of the NNDN object. 3444 Name of the NNDN in Unicode character set for the 3445 field element. 3447 IDN Table Identifier for the NNDN that matches 3448 an IDN Table Reference Object record, as defined in Section 5.5.2. 3450 Example of an "NNDN" element: 3452 ... 3453 3454 ... 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3467 NNDN-YYYYMMDD.csv 3468 3469 3470 3471 ... 3472 3473 ... 3475 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3476 contains two NNDN records for an IDN with one blocked variant and one 3477 mirrored variant. 3479 xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example, 3480 blocked,,2005-04-23T11:49:00.0Z 3481 xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example, 3482 mirrored,1,2005-04-23T11:49:00.0Z 3484 5.6.2.2. 3486 The is used to hold the deleted NNDN objects in a 3487 Differential or Incremental Deposit. The is split 3488 into separate CSV file definitions using named elements 3489 with the "name" attribute. The following section defines the 3490 supported NNDN deletes CSV file definition. 3492 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3494 The following "NNDN" field elements MUST be used in the deletes 3495 "NNDN" element: 3497 Fully-qualified name of the NNDN with 3498 type="eppcom:labelType" and isRequired="true". 3500 Example of an "NNDN" element. 3502 ... 3503 3504 ... 3505 3506 3507 3508 3509 3510 3512 NNDN-delete-YYYYMMDD.csv 3513 3514 3515 3516 ... 3517 3518 ... 3520 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3521 contains one NNDN records. 3523 xn--bc456-3ve.example 3525 5.7. EPP Parameters Object 3527 The EPP Parameters Object is a pseudo-object that defines the set of 3528 object and object extension services supported by the registry, as 3529 defined in [RFC5730]. The EPP Parameters Object is only defined as 3530 XML but could be used in the XML model or CSV model. The EPP 3531 Parameters Object is defined using the 3532 element. The EPP Parameters Object SHOULD be included if the 3533 registry supports EPP. A maximum of one EPP Parameters Object MUST 3534 exist at a certain point in time (watermark). 3536 The syntax and content of the children 3537 elements is as explained in section 2.4 of [RFC5730]. The children 3538 of the are as follows: 3540 o One or more elements that indicate the EPP versions 3541 supported by the registry. 3543 o One or more elements that indicate the identifiers of the 3544 text response languages supported by the registry's EPP server. 3546 o One or more elements that contain namespace URIs 3547 representing the objects that the registry's EPP server is capable 3548 of managing. 3550 o An OPTIONAL element that contains one or more 3551 elements that contain namespace URIs representing object 3552 extensions supported by the registry's EPP server. 3554 o A element that contains child elements used to describe the 3555 server's privacy policy for data collection and management. See 3556 section 2.4 of [RFC5730] for more details. 3558 Example of element object: 3560 ... 3561 3562 1.0 3563 en 3564 urn:ietf:params:xml:ns:domain-1.0 3565 3566 urn:ietf:params:xml:ns:contact-1.0 3567 3568 urn:ietf:params:xml:ns:host-1.0 3569 3570 3571 urn:ietf:params:xml:ns:rgp-1.0 3572 urn:ietf:params:xml:ns:secDNS-1.1 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 ... 3593 5.8. Policy Object 3595 The Policy object is a pseudo-object that is used to specify which 3596 OPTIONAL elements from the XML Model are REQUIRED based on the 3597 business model of the registry. For the CSV Model, the OPTIONAL 3598 "isRequired" attribute of the elements, defined in 3599 Section 4.6.2.1, is used to specify which OPTIONAL fields are 3600 REQUIRED based on the business model of the registry. 3602 5.8.1. object 3604 The OPTIONAL contains the following attributes: 3606 o An that defines that the referenced is 3607 REQUIRED. 3609 o that defines the XPath (see, [W3C.REC-xpath-31-20170321]) 3610 of the element referenced by . 3612 Example of object: 3614 ... 3615 3617 ... 3619 5.9. Header Object 3621 The Header Object is a pseudo-object that is used to specify the 3622 number of objects in the repository at a specific point in time 3623 (watermark) regardless of the type of deposit: Differential, Full or 3624 Incremental Deposit. The Header Object may also be used to provide 3625 additional information on the contents of the deposit. The Header 3626 Object is only defined as XML but one header object MUST always be 3627 present per escrow deposit regardless of using XML Model or CSV 3628 Model. The Header Object is defined using the 3629 element. 3631 5.9.1. object 3633 The contains the following elements: 3635 o A choice of one of the elements defined in the 3636 "repositoryTypeGroup" group element that indicates the unique 3637 identifier for the repository being escrowed. Possible elements 3638 are: 3640 * A element that defines TLD or the RCDN being 3641 escrowed in the case of a Registry data escrow deposit. For 3642 IDNs the A-Label is used (see [RFC5891], Section 4.4). 3644 * A element that defines the Registrar ID 3645 corresponding to a Registrar data escrow deposit. In the case 3646 of an ICANN-accredited Registrar, the 3647 element MUST be the IANA Registrar ID assigned by ICANN. 3649 * A element that defines the provider ID 3650 corresponding to a Privacy and Proxy Services Provider data 3651 escrow deposit. In the case of an ICANN-accredited Privacy and 3652 Proxy Services Provider, the element MUST be 3653 the unique ID assigned by ICANN. 3655 * A element that defines the provider ID 3656 corresponding to a Reseller data escrow deposit. 3658 o A element that contains the number of objects in the SRS 3659 at a specific point in time (watermark) regardless of the type of 3660 deposit: Differential, Full or Incremental. The element 3661 supports the following attributes: 3663 * A "uri" attribute reflects the XML namespace URI of the primary 3664 objects for the XML Model and CSV Model. For example, the 3665 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3666 domain name objects using the XML Model, and the "uri" is set 3667 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3668 objects using the CSV Model. 3670 * An OPTIONAL "rcdn" attribute indicates the RCDN of the objects 3671 included in the element. For IDNs the A-Label is used 3672 [RFC5891], Section 4.4. If the "rcdn" attribute is present, 3673 the value of the element must include only objects 3674 related to registrations in the same and lower levels. For 3675 example in a data escrow deposit for the .EXAMPLE TLD, a value 3676 of "example" in the "rcdn" attribute within the element 3677 indicates the number of objects in the TLD including objects in 3678 other RCDNs within the TLD, whereas a value of "com.example" 3679 indicates the number of elements for objects under 3680 "com.example" and lower levels. Omitting the "rcdn" attribute 3681 indicates that the total includes all objects of the specified 3682 "uri" in the repository (e.g. the TLD, Registrar, or PPSP). 3684 * An OPTIONAL "registrarId" attribute indicates the identifier of 3685 the sponsoring Registrar of the objects included in the 3686 element. In the case of an ICANN-accredited Registrar, the 3687 value MUST be the IANA Registrar ID assigned by ICANN. 3689 o An OPTIONAL element that contains a tag that defines 3690 the expected content in the deposit. The producer and consumer of 3691 the deposits will coordinate the set of possible 3692 element values. 3694 Example of object referencing only the XML Model 3695 objects: 3697 ... 3698 3699 test 3700 2 3702 1 3704 1 3706 1 3708 3709 1 3711 1 3713 1 3715 3716 3717 ... 3719 Example of object referencing the CSV and XML 3720 Model objects: 3722 ... 3723 3724 test 3725 2 3727 1 3729 1 3731 1 3733 3734 1 3736 1 3738 1 3740 3741 3742 ... 3744 5.10. DNRD Common Objects Collection 3746 The DNRD Common Objects Collection contains data structures 3747 referenced by two or more of the main objects in the XML model. 3749 6. RDE IDN Variants handling 3751 Depending on the Registration Policy of the Registry, for a domain 3752 name there may be multiple variant names. See [variantTLDsReport] 3753 for further detail on IDN variants. 3755 A registry could choose to escrow IDN variants as domains or NNDN 3756 objects. A specific IDN variant can be represented in the escrow 3757 deposit, as a domain or as an NNDN object, but not both. 3759 If using domain objects to represent IDN variants, the normal 3760 behavior during restoration of an SRS based on an escrow deposit is 3761 to restore the IDN variants as a mirrored variant. If the 3762 registration data of the IDN variant is different from the original 3763 name, the details of this specific implementation MUST be described 3764 in the IDN policy document. 3766 An NNDN or a domain name are explicit representations of an IDN 3767 variant while an IDN variant computed based on an algorithm is an 3768 implicit representation. Explicit representation of an IDN variant 3769 takes precedence over an implicit representation. 3771 7. Profile 3773 Different business models of registries exist, therefore the registry 3774 is responsible for defining a profile that matches its particular 3775 business model. The profile mechanism allows a registry to extend 3776 this specification. 3778 A profile is the process of: 3780 1. Extending base objects with the mechanisms defined for XML and 3781 CSV models. 3783 * In the case of the XML model, abstract elements could be use 3784 to extend the following objects: , , , 3785 and using XML schema substitution groups 3786 feature. 3788 2. Defining a object to specify which OPTIONAL elements of 3789 this base specification is required based on the business model 3790 of the registry. An example is the element that is 3791 usually REQUIRED but it is specified as OPTIONAL in this 3792 specification to support some existing business models. 3794 3. Adding new escrowed objects using the and 3795 elements. 3797 4. Providing the XML schemas to third parties that require them to 3798 validate the escrow deposits. 3800 8. Data escrow agent extended verification process 3802 A Data Escrow Agent SHOULD perform an extended verification process 3803 that starts by creating a dataset to be tested by following section 3804 5.2 in [I-D.ietf-regext-data-escrow]. 3806 The following are the minimum suggested tests on the dataset: 3808 o Validate the escrow deposits using the definition agreed with the 3809 registry. 3811 * In the case of the XML model, the contents of the escrow 3812 deposits MUST be validated using the XML schemas of the 3813 profile. 3815 o Count the objects and validate that the number of objects is equal 3816 to the number objects reported in the
element of the 3817 escrow deposit of that point in time (watermark). 3819 o All contact objects linked to domain names MUST be present. 3821 o All registrars objects linked to other objects MUST be present. 3823 o No domain name exists as both a domain name and an NNDN. 3825 o The elements listed as required in the element MUST be 3826 present. 3828 o All idnTableRef definitions linked from other objects MUST be 3829 present. 3831 o If an EPP Parameters Object was escrowed in the past, one and only 3832 one EPP Parameters Object MUST be present. 3834 o The watermark is not in the future. 3836 9. Formal Syntax 3838 This standard is specified in XML Schema notation. The formal syntax 3839 presented here is a complete schema representation suitable for 3840 automated validation. 3842 The and tags are not part of the schema; 3843 they are used to note the beginning and ending of the schema for URI 3844 registration purposes. 3846 9.1. RDE CSV Schema 3848 3849 3850 3856 3859 3860 3861 3862 3863 Registry Data Escrow Comma-Separated Values (CSV) 3864 3865 3866 3867 3869 3870 3871 3872 3874 3876 3877 3880 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3895 3896 3897 3898 3899 3900 3901 3902 3903 3906 3909 3910 3912 3913 3914 3915 3916 3917 3918 3921 3924 3925 3926 3927 3928 3929 3932 3933 3934 3935 3936 3939 3940 3941 3942 3943 3944 3945 3946 3949 3950 3951 3952 3953 3956 3957 3958 3959 3960 3963 3964 3965 3966 3967 3970 3971 3972 3973 3974 3977 3978 3979 3980 3981 3984 3985 3986 3989 3991 3994 3995 3998 4000 4003 4004 4007 4010 4013 4015 4018 4020 4023 4025 4028 4029 4030 4031 4032 4035 4036 4037 4038 4039 4040 4041 4042 4045 4046 4047 4048 4049 4052 4055 4058 4059 4062 4063 4066 4069 4070 4071 4072 4073 4076 4077 4078 4079 4080 4081 4082 4083 4086 4087 4088 4089 4090 4091 4092 4093 4094 4097 4098 4099 4100 4101 4102 4103 4104 4107 4108 4109 4110 4111 4112 4113 4114 4115 4118 4119 4120 4121 4122 4123 4124 4125 4128 4129 4130 4131 4132 4133 4134 4135 4136 4139 4140 4141 4142 4143 4144 4145 4146 4149 4150 4151 4152 4153 4154 4155 4156 4157 4160 4161 4162 4163 4164 4165 4166 4167 4170 4171 4172 4173 4174 4177 4178 4179 4180 4181 4184 4185 4186 4187 4188 4191 4192 4195 4196 4197 4198 4199 4202 4203 4204 4205 4206 4207 4208 4209 4210 4213 4214 4215 4216 4217 4218 4219 4220 4221 4224 4225 4226 4227 4228 4229 4230 4231 4232 4235 4236 4237 4238 4239 4242 4243 4244 4245 4246 4248 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4266 4267 4268 4269 4270 4271 4272 4274 4277 4279 4282 4283 4284 4285 4286 4289 4290 4291 4292 4293 4296 4298 4299 4300 4303 4304 4306 9.2. RDE Domain Object 4308 4309 4310 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 Registry Data Escrow Domain provisioning schema 4331 4332 4333 4337 4339 4342 4343 4344 4345 4346 4347 4349 4351 4354 4357 4360 4363 4367 4370 4374 4377 4379 4382 4385 4388 4391 4395 4398 4401 4404 4405 4406 4407 4408 4409 4410 4412 4414 4416 4418 4420 4423 4424 4425 4426 4427 4428 4429 4430 4434 4435 4436 4437 4438 4439 4441 9.3. CSV Domain Object 4443 4444 4445 4455 4458 4459 4460 4461 4462 4463 4464 4465 4466 Domain Name Comma-Separated Values (CSV) Object 4467 4468 4469 4472 4475 4476 4477 4478 4479 4481 4482 4483 4484 4485 4488 4491 4492 4493 4494 4495 4497 4498 4499 4500 4501 4502 4505 4506 4509 4510 4511 4512 4513 4516 4517 4518 4519 4520 4523 4524 4525 4526 4527 4530 4531 4532 4533 4534 4535 4538 4539 4540 4541 4542 4545 4546 4547 4548 4549 4552 4553 4556 4557 4560 4561 4564 4565 4568 4569 4572 4573 4576 4577 4580 4581 4582 4583 4584 4587 4588 4589 4590 4591 4594 4595 4598 4599 4600 4601 4602 4603 4606 4607 4608 4609 4612 4613 4615 9.4. RDE Host Object 4617 4618 4619 4627 4628 4629 4630 4631 4632 4633 Registry Data Escrow Host provisioning schema 4634 4635 4636 4640 4642 4645 4646 4647 4648 4649 4650 4652 4654 4657 4661 4663 4666 4669 4672 4675 4678 4679 4680 4682 4683 4684 4685 4686 4687 4689 4691 4693 4694 4695 4696 4697 4698 4700 9.5. CSV Host Object 4702 4703 4704 4712 4715 4716 4717 4718 4719 4720 4721 Host Comma-Separated Values (CSV) Object 4722 4723 4724 4727 4731 4732 4733 4734 4735 4737 4738 4739 4740 4741 4744 4747 4748 4749 4750 4751 4753 4754 4755 4756 4757 4758 4761 4762 4765 4766 4767 4768 4769 4772 4773 4774 4775 4776 4780 4781 4782 4783 4784 4787 4788 4789 4790 4791 4794 4795 4796 4797 4798 4799 4802 4803 4804 4805 4808 4809 4811 9.6. RDE Contact Object 4813 4814 4815 4823 4824 4825 4826 4827 4828 4829 4830 Registry Data Escrow contact provisioning schema 4831 4832 4833 4837 4839 4842 4843 4844 4845 4846 4847 4849 4851 4854 4857 4860 4863 4865 4867 4870 4873 4877 4880 4883 4886 4889 4890 4891 4892 4893 4894 4895 4897 4899 4901 4903 4905 4906 4907 4908 4909 4910 4911 4912 4916 4917 4918 4919 4920 4921 4923 9.7. CSV Contact Object 4925 4926 4927 4935 4938 4939 4940 4941 4942 4943 4944 Contact Comma-Separated Values (CSV) Object 4945 4946 4947 4950 4953 4954 4955 4956 4957 4959 4960 4961 4962 4963 4966 4969 4970 4971 4972 4973 4975 4976 4977 4978 4979 4980 4983 4984 4985 4986 4987 4990 4991 4992 4993 4994 4997 4998 5001 5004 5005 5006 5007 5008 5011 5012 5013 5014 5015 5018 5021 5022 5025 5026 5027 5028 5029 5032 5033 5034 5035 5039 5042 5043 5044 5045 5046 5049 5050 5051 5052 5053 5054 5055 5056 5057 5060 5062 5063 5064 5065 5066 5067 5068 5069 5070 5073 5075 5076 5077 5078 5079 5082 5083 5086 5087 5088 5091 5092 5093 5094 5095 5098 5099 5100 5101 5102 5105 5106 5109 5110 5113 5114 5115 5116 5117 5120 5122 5123 5124 5125 5126 5129 5130 5131 5132 5133 5136 5138 5139 5140 5141 5142 5144 5147 5149 5152 5154 5157 5159 5162 5164 5167 5169 5172 5174 5177 5179 5182 5184 5187 5189 5192 5193 5194 5195 5196 5199 5200 5201 5202 5203 5206 5207 5208 5209 5210 5211 5214 5215 5216 5217 5220 5221 5223 9.8. RDE Registrar Object 5225 5226 5227 5235 5236 5237 5238 5239 5240 5241 5242 Registry Data Escrow registrar provisioning schema 5243 5244 5245 5249 5251 5254 5255 5256 5257 5258 5259 5261 5263 5266 5269 5273 5276 5279 5282 5285 5288 5291 5294 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5315 5316 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5332 5334 5337 5340 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5370 5373 5374 5375 5376 5377 5378 5379 5380 5384 5385 5386 5387 5388 5389 5391 9.9. CSV Registrar Object 5393 5394 5395 5404 5407 5408 5409 5410 5411 5412 5413 5414 Registar Comma-Separated Values (CSV) Object 5415 5416 5417 5420 5423 5424 5425 5426 5427 5429 5430 5431 5432 5433 5436 5439 5440 5441 5442 5443 5445 5446 5447 5448 5449 5450 5453 5454 5457 5458 5459 5460 5461 5462 5465 5468 5469 5470 5471 5472 5475 5476 5479 5482 5483 5484 5485 5486 5489 5490 5491 5492 5493 5494 5495 5496 5498 5500 5501 5502 5503 5504 5505 5506 5507 5508 5509 5510 5511 5514 5517 5518 5520 9.10. RDE IDN Table Reference Objects 5522 5523 5524 5529 5530 5531 5532 Registry Data Escrow IDN provisioning schema 5533 5534 5535 5538 5541 5542 5543 5544 5545 5546 5549 5551 5552 5555 5556 5557 5558 5559 5560 5561 5562 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5578 9.11. CSV IDN Language Object 5580 5581 5582 5588 5591 5592 5593 5594 5595 IDN Language Comma-Separated Values (CSV) Object 5596 5598 5599 5602 5605 5606 5607 5608 5609 5611 5612 5613 5614 5615 5618 5621 5622 5623 5624 5625 5627 5628 5629 5630 5631 5634 5635 5637 9.12. EPP Parameters Object 5639 5640 5641 5648 5649 5650 5651 5652 5653 Registry Data Escrow EPP Parameters schema 5654 5655 5656 5657 5659 5660 5664 5665 5666 5667 5668 5671 5674 5677 5680 5682 5683 5684 5685 5686 5687 5689 9.13. NNDN Object 5691 5692 5693 5700 5701 5702 5703 5704 5705 Registry Data Escrow NNDN provisioning schema 5706 5707 5708 5712 5714 5717 5718 5719 5720 5721 5722 5724 5727 5730 5733 5735 5738 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5755 5756 5757 5758 5759 5760 5761 5762 5763 5767 5768 5769 5770 5771 5772 5774 9.14. CSV NNDN Object 5776 5777 5778 5785 5788 5789 5790 5791 5792 5793 NNDN (NNDN's not domain name) (CSV) Object 5794 5795 5796 5799 5802 5803 5804 5805 5806 5808 5809 5810 5811 5812 5815 5818 5819 5820 5821 5822 5824 5825 5826 5827 5828 5829 5832 5833 5836 5837 5840 5841 5842 5843 5844 5847 5848 5849 5850 5851 5854 5857 5858 5860 9.15. Policy Object 5861 5862 5863 5868 5869 5870 Registry Data Escrow Policy schema 5871 5872 5873 5874 5877 5878 5879 5880 5883 5886 5887 5888 5889 5890 5892 9.16. Header Object 5894 5895 5896 5902 5903 5904 5905 5906 Data Escrow Deposit Header schema 5907 5908 5909 5910 5913 5914 5915 5916 5917 5918 5919 5922 5925 5926 5927 5928 5929 5930 5931 5933 5935 5937 5939 5940 5941 5942 5943 5944 5947 5949 5951 5952 5953 5954 5955 5957 9.17. DNRD Common Objects 5959 5960 5961 5966 5967 5968 5969 Data Escrow Deposit Common Objects schema 5970 5971 5972 5973 5974 5975 5977 5978 5979 5980 5981 5983 10. Internationalization Considerations 5985 Data Escrow deposits are represented in XML, which provides native 5986 support for encoding information using the Unicode character set and 5987 its more compact representations including UTF-8. Conformant XML 5988 processors recognize both UTF-8 and UTF-16. Though XML includes 5989 provisions to identify and use other character encodings through use 5990 of an "encoding" attribute in an declaration, use of UTF-8 is 5991 RECOMMENDED. 5993 11. IANA Considerations 5995 This document uses URNs to describe XML namespaces and XML schemas 5996 conforming to a registry mechanism described in [RFC3688]. The 5997 following URI assignments is requested of IANA. 5999 Registration request for the RDE CSV namespace: 6001 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6003 Registrant Contact: IESG 6004 Note to RFC Editor: Please remove the email address from the RFC 6005 after IANA records it. 6007 XML: None. Namespace URIs do not represent an XML specification. 6009 Registration request for the RDE CSV XML schema: 6011 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6013 Registrant Contact: IESG 6015 Note to RFC Editor: Please remove the email address from the RFC 6016 after IANA records it. 6018 See Section 9.1 of this document. 6020 Registration request for the RDE domain namespace: 6022 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6024 Registrant Contact: IESG 6026 Note to RFC Editor: Please remove the email address from the RFC 6027 after IANA records it. 6029 XML: None. Namespace URIs do not represent an XML specification. 6031 Registration request for the RDE domain XML schema: 6033 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6035 Registrant Contact: IESG 6037 Note to RFC Editor: Please remove the email address from the RFC 6038 after IANA records it. 6040 See Section 9.2 of this document. 6042 Registration request for the CSV domain namespace: 6044 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6046 Registrant Contact: IESG 6048 Note to RFC Editor: Please remove the email address from the RFC 6049 after IANA records it. 6051 XML: None. Namespace URIs do not represent an XML specification. 6053 Registration request for the CSV domain XML schema: 6055 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6057 Registrant Contact: IESG 6059 Note to RFC Editor: Please remove the email address from the RFC 6060 after IANA records it. 6062 See Section 9.3 of this document. 6064 Registration request for the RDE host namespace: 6066 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6068 Registrant Contact: IESG 6070 Note to RFC Editor: Please remove the email address from the RFC 6071 after IANA records it. 6073 XML: None. Namespace URIs do not represent an XML specification. 6075 Registration request for the RDE host XML schema: 6077 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6079 Registrant Contact: IESG 6081 Note to RFC Editor: Please remove the email address from the RFC 6082 after IANA records it. 6084 See Section 9.4 of this document. 6086 Registration request for the CSV host namespace: 6088 URI: urn:ietf:params:xml:ns:csvHost-1.0 6090 Registrant Contact: IESG 6092 Note to RFC Editor: Please remove the email address from the RFC 6093 after IANA records it. 6095 XML: None. Namespace URIs do not represent an XML specification. 6097 Registration request for the CSV host XML schema: 6099 URI: urn:ietf:params:xml:schema:csvHost-1.0 6100 Registrant Contact: IESG 6102 Note to RFC Editor: Please remove the email address from the RFC 6103 after IANA records it. 6105 See Section 9.5 of this document. 6107 Registration request for the RDE contact namespace: 6109 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6111 Registrant Contact: IESG 6113 Note to RFC Editor: Please remove the email address from the RFC 6114 after IANA records it. 6116 XML: None. Namespace URIs do not represent an XML specification. 6118 Registration request for the RDE contact XML schema: 6120 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6122 Registrant Contact: IESG 6124 Note to RFC Editor: Please remove the email address from the RFC 6125 after IANA records it. 6127 See Section 9.6 of this document. 6129 Registration request for the CSV contact namespace: 6131 URI: urn:ietf:params:xml:ns:csvContact-1.0 6133 Registrant Contact: IESG 6135 Note to RFC Editor: Please remove the email address from the RFC 6136 after IANA records it. 6138 XML: None. Namespace URIs do not represent an XML specification. 6140 Registration request for the CSV contact XML schema: 6142 URI: urn:ietf:params:xml:schema:csvContact-1.0 6144 Registrant Contact: IESG 6146 Note to RFC Editor: Please remove the email address from the RFC 6147 after IANA records it. 6149 See Section 9.7 of this document. 6151 Registration request for the RDE registrar namespace: 6153 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6155 Registrant Contact: IESG 6157 Note to RFC Editor: Please remove the email address from the RFC 6158 after IANA records it. 6160 XML: None. Namespace URIs do not represent an XML specification. 6162 Registration request for the RDE registrar XML schema: 6164 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6166 Registrant Contact: IESG 6168 Note to RFC Editor: Please remove the email address from the RFC 6169 after IANA records it. 6171 See Section 9.8 of this document. 6173 Registration request for the CSV registrar namespace: 6175 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6177 Registrant Contact: IESG 6179 Note to RFC Editor: Please remove the email address from the RFC 6180 after IANA records it. 6182 XML: None. Namespace URIs do not represent an XML specification. 6184 Registration request for the CSV registrar XML schema: 6186 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6188 Registrant Contact: IESG 6190 Note to RFC Editor: Please remove the email address from the RFC 6191 after IANA records it. 6193 See Section 9.9 of this document. 6195 Registration request for the RDE IDN namespace: 6197 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6199 Registrant Contact: IESG 6201 Note to RFC Editor: Please remove the email address from the RFC 6202 after IANA records it. 6204 XML: None. Namespace URIs do not represent an XML specification. 6206 Registration request for the RDE IDN XML schema: 6208 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6210 Registrant Contact: IESG 6212 Note to RFC Editor: Please remove the email address from the RFC 6213 after IANA records it. 6215 See Section 9.10 of this document. 6217 Registration request for the CSV IDN namespace: 6219 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6221 Registrant Contact: IESG 6223 Note to RFC Editor: Please remove the email address from the RFC 6224 after IANA records it. 6226 XML: None. Namespace URIs do not represent an XML specification. 6228 Registration request for the CSV IDN XML schema: 6230 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6232 Registrant Contact: IESG 6234 Note to RFC Editor: Please remove the email address from the RFC 6235 after IANA records it. 6237 See Section 9.11 of this document. 6239 Registration request for the RDE EPP parameters namespace: 6241 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6243 Registrant Contact: IESG 6244 Note to RFC Editor: Please remove the email address from the RFC 6245 after IANA records it. 6247 XML: None. Namespace URIs do not represent an XML specification. 6249 Registration request for the RDE EPP parameters XML schema: 6251 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6253 Registrant Contact: IESG 6255 Note to RFC Editor: Please remove the email address from the RFC 6256 after IANA records it. 6258 See Section 9.12 of this document. 6260 Registration request for the RDE NNDN namespace: 6262 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6264 Registrant Contact: IESG 6266 Note to RFC Editor: Please remove the email address from the RFC 6267 after IANA records it. 6269 XML: None. Namespace URIs do not represent an XML specification. 6271 Registration request for the RDE NNDN XML schema: 6273 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6275 Registrant Contact: IESG 6277 Note to RFC Editor: Please remove the email address from the RFC 6278 after IANA records it. 6280 See Section 9.13 of this document. 6282 Registration request for the CSV NNDN namespace: 6284 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6286 Registrant Contact: IESG 6288 Note to RFC Editor: Please remove the email address from the RFC 6289 after IANA records it. 6291 XML: None. Namespace URIs do not represent an XML specification. 6293 Registration request for the CSV NNDN XML schema: 6295 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6297 Registrant Contact: IESG 6299 Note to RFC Editor: Please remove the email address from the RFC 6300 after IANA records it. 6302 See Section 9.14 of this document. 6304 Registration request for the RDE Policy namespace: 6306 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6308 Registrant Contact: IESG 6310 Note to RFC Editor: Please remove the email address from the RFC 6311 after IANA records it. 6313 XML: None. Namespace URIs do not represent an XML specification. 6315 Registration request for the RDE Policy XML schema: 6317 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6319 Registrant Contact: IESG 6321 Note to RFC Editor: Please remove the email address from the RFC 6322 after IANA records it. 6324 See Section 9.15 of this document. 6326 Registration request for the RDE Header namespace: 6328 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6330 Registrant Contact: IESG 6332 Note to RFC Editor: Please remove the email address from the RFC 6333 after IANA records it. 6335 XML: None. Namespace URIs do not represent an XML specification. 6337 Registration request for the RDE Header XML schema: 6339 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6340 Registrant Contact: IESG 6342 Note to RFC Editor: Please remove the email address from the RFC 6343 after IANA records it. 6345 See Section 9.16 of this document. 6347 Registration request for the RDE Common Objects namespace: 6349 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6351 Registrant Contact: IESG 6353 Note to RFC Editor: Please remove the email address from the RFC 6354 after IANA records it. 6356 XML: None. Namespace URIs do not represent an XML specification. 6358 Registration request for the RDE Common Objects XML schema: 6360 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6362 Registrant Contact: IESG 6364 Note to RFC Editor: Please remove the email address from the RFC 6365 after IANA records it. 6367 See Section 9.17 of this document. 6369 12. Implementation Status 6371 Note to RFC Editor: Please remove this section and the reference to 6372 RFC 7942 [RFC7942] before publication. 6374 This section records the status of known implementations of the 6375 protocol defined by this specification at the time of posting of this 6376 Internet-Draft, and is based on a proposal described in RFC 7942 6377 [RFC7942]. The description of implementations in this section is 6378 intended to assist the IETF in its decision processes in progressing 6379 drafts to RFCs. Please note that the listing of any individual 6380 implementation here does not imply endorsement by the IETF. 6381 Furthermore, no effort has been spent to verify the information 6382 presented here that was supplied by IETF contributors. This is not 6383 intended as, and must not be construed to be, a catalog of available 6384 implementations or their features. Readers are advised to note that 6385 other implementations may exist. 6387 According to RFC 7942 [RFC7942], "this will allow reviewers and 6388 working groups to assign due consideration to documents that have the 6389 benefit of running code, which may serve as evidence of valuable 6390 experimentation and feedback that have made the implemented protocols 6391 more mature. It is up to the individual working groups to use this 6392 information as they see fit". 6394 12.1. Implementation in the gTLD space 6396 Organization: ICANN 6398 Name: ICANN Registry Agreement 6400 Description: the ICANN Base Registry Agreement requires Registries, 6401 Data Escrow Agents, and ICANN to implement this specification. ICANN 6402 receives daily notifications from Data Escrow Agents confirming that 6403 more than 1,200 gTLDs are sending deposits that comply with this 6404 specification. ICANN receives on a weekly basis per gTLD, from more 6405 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6406 also complies with this specification. In addition, ICANN is aware 6407 of Registry Service Provider transitions using data files that 6408 conform to this specification. 6410 Level of maturity: production. 6412 Coverage: all aspects of this specification are implemented. 6414 Version compatibility: versions 03 - 09 are known to be implemented. 6416 Contact: gustavo.lozano@icann.org 6418 URL: https://www.icann.org/resources/pages/registries/registries- 6419 agreements-en 6421 13. Security Considerations 6423 This specification does not define the security mechanisms to be used 6424 in the transmission of the data escrow deposits, since it only 6425 specifies the minimum necessary to enable the rebuilding of a 6426 registry from deposits without intervention from the original 6427 registry. 6429 Depending on local policies, some elements, or, most likely, the 6430 whole deposit will be considered confidential. As such, the parties 6431 SHOULD take all the necessary precautions such as encrypting the data 6432 at rest and in transit to avoid inadvertent disclosure of private 6433 data. Regardless of the precautions taken by the parties regarding 6434 data at rest and in transit, authentication credentials MUST NOT be 6435 escrowed. 6437 Authentication of the parties passing data escrow deposit files is 6438 also of the utmost importance. The escrow agent MUST properly 6439 authenticate the registry's identity before accepting data escrow 6440 deposits. The registry MUST authenticate the escrow agent's identity 6441 before submitting any data, and the data escrow agent MUST 6442 authenticate the identity of the party receiving the data escrow 6443 deposits for the purposes deemed appropriate. 6445 Additionally, the registry and the escrow agent MUST use integrity 6446 checking mechanisms to ensure the data transmitted is what the source 6447 intended. Validation of the contents by the parties is RECOMMENDED 6448 to ensure that the file was transmitted correctly from the registry 6449 or escrow agent and that the contents are "meaningful". 6451 A few elements in this specification contain URLs, the use of HTTP 6452 over TLS (Transport Layer Security), [RFC2818] is RECOMMENDED on the 6453 URLs. 6455 The various data structures in the document include a few places that 6456 have internal redundancy, and if the values become inconsistent there 6457 can be harmful consequences, such as different entities using 6458 different fields as their reference. 6460 Note: if Transport Layer Security (TLS) is used when providing an 6461 escrow services, the recommendations in [BCP195] MUST be implemented. 6463 14. Privacy Considerations 6465 This specification defines a format that may be used to escrow 6466 personal data. The process of data escrow is governed by a legal 6467 document agreed by the parties, and such legal document must ensure 6468 that privacy-sensitive and/or personal data receives the required 6469 protection. 6471 15. Acknowledgments 6473 Parts of this document are based on EPP [RFC5730] and related RFCs by 6474 Scott Hollenbeck. 6476 Special suggestions that have been incorporated into this document 6477 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6478 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6479 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6480 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6481 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6482 Mitchell, Francisco Obispo, Bhadresh Modi, Alexander Mayrhofer and 6483 Benjamin Kaduk. 6485 Shoji Noguchi and Francisco Arias participated as co-authors until 6486 version 05 providing invaluable support for this document. 6488 16. Change History 6490 [[RFC Editor: Please remove this section.]] 6492 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6493 dnrd-objects-mapping-00 6495 1. Added definition for child elements under the element. 6497 2. Added definition for child elements under the element. 6499 3. Added definition for child elements under the element. 6501 4. Rewrote the IDN Variants Handling section to use the variant 6502 states as described in ICANN's Study of Issues Related to the 6503 Management of IDN Variant TLDs. 6505 5. Renamed to in the . 6507 6. Renamed to in the element. 6509 7. Renamed to in the element. 6511 8. Added element under element. 6513 9. Fixed some typographical errors and omissions. 6515 16.2. Changes from 00 to 01 6517 1. Specify OPTIONAL elements in the draft. 6519 2. Added NNDN object to support list of reserved names and different 6520 IDN variants models. 6522 3. Removed subordinated host element from the domain object. 6524 4. Added eppParams object. 6526 5. Added variantGenerator element to the domain object. 6528 6. Added lgr to the IDN table object. 6530 16.3. Changes from 01 to 02 6532 1. Updates to the all objects based on feedback from the list. 6534 2. Start of XML and CSV drafts merge. 6536 3. Added header object. 6538 4. Added report object. 6540 5. Added notification object. 6542 6. Added Data Escrow Agent Extended Verification Process section. 6544 7. Added Notifications from Registries to Third Parties. 6546 8. Added Notifications from Data Escrow Agents to Third Parties. 6548 9. Added FULL, DIFF deposit examples using the XML model only. 6550 16.4. Changes from 02 to 03 6552 1. Remove authinfo from the XML Schema. 6554 2. Resend attribute is now an element 6556 3. Scope attribute added to policy object. 6558 16.5. Changes from 03 to 04 6560 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6561 arias-noguchi-dnrd-objects-mapping-02. 6563 2. Changed the cksum attribute of to use CRC32 and 6564 changed all of the sample cksum values to use CRC32, based on 6565 feedback from David Kipling. 6567 3. Changed the optional element to be an optional 6568 "sep" attribute value of the element with a default 6569 value of "," based on feedback from David Kipling. 6571 4. Added support for the optional "parent" attribute for the to the 6572 CSV fields to indicate a field as a reference to a parent 6573 object, based on feedback from David Kipling. 6575 5. Added support for the CSV model for the NNDN. 6577 6. Added support to delete hosts based on roid. 6579 7. Added mirrored state to NNDN 6581 8. Minor fixes to XML XSDs. 6583 9. The Report and Notification objects were moved to draft-lozano- 6584 icann-registry-interfaces 6586 10. The section Data escrow notifications was moved to draft-lozano- 6587 icann-registry-interfaces 6589 11. Removed references to the , , and 6590 from the "hostStatuses" and "hostAddresses" CSV 6591 files. 6593 12. Removed references to the , , and 6594 from the "contactStatuses" CSV file. 6596 13. Removed references to the , , and 6597 from the "domainContacts", "domainStatuses", 6598 and "domainNameServers" CSV files. 6600 14. Changed to . 6602 15. Replaced use of to new field 6603 in the "domain", "idnLanguage", and "NNDN" CSV files. 6605 16. Replaced use of with in the 6606 "host" element. 6608 17. Changed the foreign key of the hosts to use 6609 instead of and removed use of in 6610 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6611 files. 6613 18. Added use of the MUST keyword for CSV fields that are required 6614 to be supported in an EPP based system. 6616 19. Removed use of the field element for the 6617 "registrar" CSV file. 6619 20. Added definition of field element. 6621 16.6. Changes from 04 to 05 6623 1. Updated the examples of the full and differential deposits using 6624 the CSV and XML model. 6626 2. Made optional for the "domainTransfer" CSV file 6627 to match the XML definition. 6629 3. Made optional for the "domain" CSV file 6630 to match the XML definition. 6632 4. Made optional for the "domain" and "contact" CSV 6633 files to match the XML definition. 6635 5. Change from IDREF to idType. 6637 6. Minor editorial changes. 6639 16.7. Changes from 05 to 06 6641 1. Revised the differential and incremental deposits for the CSV 6642 format to use cascade update / replace and delete from the parent 6643 object to be consistent with the XML format. 6645 2. Revised the structure of the CSV format sections to utilize sub- 6646 sections instead of a list for the CSV file definitions. 6648 3. Added the "CSV Parent Child Relationship" section to describe the 6649 concept of parent child relationships across CSV file 6650 definitions. 6652 4. Added the "domainNameServersAddresses" CSV File Definition 6653 section to support the domain host attributes model of [RFC5731]. 6655 5. Made the required fields in the CSV format consistent with the 6656 XML format. The CSV fields updated to be required include: 6657 , , , 6658 , , , 6659 , , , 6660 , , , 6661 , , 6662 , , , 6663 , , 6664 , and . 6666 6. Revised the CSV examples to use a more realistic set of records. 6668 16.8. Changes from 06 to 07 6670 1. Created "repositoryTypeGroup" group element in the rdeHeader 6671 including the , and 6672 elements. 6674 2. Added the optional "rcdn" and "registrarId" attributes to the 6675 element 6677 16.9. Changes from 07 to 08 6679 1. The following registrar elements were made optional to support 6680 greater flexibility for the implementation of policies: status, 6681 postalInfo, email and crDate. 6683 2. The following domain name elements were made optional to support 6684 greater flexibility for the implementation of policies: crRr. 6686 16.10. Changes from 08 to 09 6688 1. Implementation Status section was added 6690 16.11. Changes from 09 to 10 6692 1. Editorial changes in section Section 5.1.2.1.6. 6694 2. Added MAY clause when the DS Data Interface is used in section 6695 Section 5.1.2.1.6. 6697 16.12. Changes from 10 to REGEXT 00 6699 1. Internet Draft (I-D) adopted by the REGEXT WG. 6701 16.13. Changes REGEXT 00 to REGEXT 01 6703 1. Added the element to the 6704 "repositoryTypeGroup" group element in the rdeHeader. 6706 2. Privacy consideration section was added 6708 3. Updates on section 8 6710 16.14. Changes REGEXT 01 to REGEXT 02 6712 1. Added a choice between the use of the or 6713 fields in the CSV "domain", "host", and 6714 "contact" definitions. 6716 2. Added a choice between the use of the or 6717 fields in the CSV "domainNameServers" 6718 definition. 6720 3. Changed "of client" to "of the client" throughout the document. 6722 4. Modified all references of 'The attribute isRequired MUST equal 6723 "true".' to 'The attribute "isRequired" MUST equal "true".' 6725 5. Combined the and 6726 fields in a single required list for the CSV "domainContacts" 6727 definition. 6729 6. Combined the , , and 6730 fields in a single required list for the 6731 CSV "domainStatuses" definition. 6733 7. Moved the the fields to the MAY 6734 list for the CSV "domain", "host", and "contact" definitions. 6736 8. Made the order of the , , 6737 , and fields more consistent in the 6738 CSV lists. 6740 9. Fixed an error in the order of the object example. 6742 10. Changed to be optional to match being 6743 optional in the XML model, by having it use type 6744 rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and 6745 ensuring that is included in the MAY field 6746 lists and not the MUST field lists. 6748 11. Made optional for the "domain" CSV definition 6749 to be consistent with the XML model, by removing the sentence 6750 'The attribute "isRequired" MUST equal "true".' from the 6751 description and moving the field to the MAY field list. 6753 12. Made optional for the "domain" and "contact" 6754 CSV definitions to be consistent with the XML model, by moving 6755 the field to the MAY field list. 6757 13. Made optional to be consistent with the XML 6758 model, by having it use type rdeCsv:fClIDType instead of 6759 rdeCsv:fClIDRequiredType. 6761 14. Made required to be consistent with the XML 6762 model, by having it use type rdeCsv:fClIDRequiredType instead of 6763 rdeCsv:fClIDType. 6765 15. Made the field in the "host", "contact", 6766 and "registrar" CSV definitions required explicitly by removing 6767 'and isRequired="true"' and adding the sentence 'The attribute 6768 isRequired MUST equal "true".', when it is chosen as the primary 6769 field. 6771 16. Removed extra '/>.' at the end of the field 6772 description in the "hostStatuses" CSV definition. 6774 17. Made the field optional to be consistent 6775 with the XML model, by having csvRegistrar:fStatusType extend 6776 rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. 6778 18. Made the field for the "registrar" CSV 6779 definition explicitly optional to be consistent with the XML 6780 model, by adding the sentence 'The attribute isRequired MUST 6781 equal "false".' to the field description and including the 6782 definition of isRequired="false" in the "registrar" CSV 6783 definition examples. 6785 19. Added the choice between the use of the and 6786 fields in the deletes "registrar" CSV 6787 definition to be consistent with the "registrar" CSV definition. 6789 20. Made the and elements optional for the host and 6790 contact objects in the XML model to be consistent with the 6791 domain object. 6793 16.15. Changes REGEXT 02 to REGEXT 03 6795 1. Added the optional element contentTag in the header object. 6797 2. Editorial updates. 6799 16.16. Changes REGEXT 03 to REGEXT 04 6801 1. Note: Updates from version REGEXT 03 to REGEXT 04 attend the 6802 feedback provided during the document shepherd review. 6804 2. Editorial updates. 6806 3. Examples now use domain names from the .example TLD. 6808 4. The introduction was enhanced by explaining the need for data 6809 escrow and the proposed solution. 6811 5. Explanation regarding NNDN was improved. 6813 6. Explanation regarding the CSV and XML model was improved. 6815 7. Section 4.5 updated to make the text clearer. 6817 8. draft-arias-noguchi-registry-data-escrow is now referenced from 6818 the I-D repository. 6820 9. The XML prefix "rdeDomain" is now consistently used. 6822 10. The prevID attribute was removed from the examples of full 6823 deposits. 6825 11. The examples were updated to use present dates. 6827 16.17. Changes REGEXT 04 to REGEXT 05 6829 1. draft-ietf-regext-data-escrow (version 04) is now referenced from 6830 the I-D repository. 6832 2. The example in idnLanguage CSV file definition updated to use the 6833 sep attribute. 6835 3. The reference in the example in hostAddresses CSV file definition 6836 was updated. 6838 4. Moved [RFC0791] and [RFC5952] to the Normative References 6839 section. 6841 16.18. Changes REGEXT 05 to REGEXT 06 6843 1. Changes based on the feedback provided here: 6844 https://mailarchive.ietf.org/arch/msg/regext/ 6845 nA8eTYIrXJ44_6ullQlRLW6T74s 6847 16.19. Changes REGEXT 06 to REGEXT 07 6849 1. Changes based on the feedback provided here: 6850 https://mailarchive.ietf.org/arch/msg/regext/hDLz2ym4oR-ukA4Fm- 6851 QJ8FzaxxE 6853 2. Changes based on the feedback provided here: 6854 https://mailarchive.ietf.org/arch/msg/regext/780Xw- 6855 z1RMRb79nmZ6ABmRTo1fU 6857 16.20. Changes REGEXT 07 to REGEXT 08 6859 1. Changes based on the feedback provided here: 6860 https://mailarchive.ietf.org/arch/msg/regext/ 6861 UaMNvl1xh60ldjpqHHYc3TNsfhg 6863 2. Changes based on the feedback provided here: 6864 https://mailarchive.ietf.org/arch/msg/regext/ 6865 B3QTxUCWUE4R_QharAQlA3041j0 6867 16.21. Changes REGEXT 08 to REGEXT 09 6869 1. Changes based on the feedback provided here: 6870 https://mailarchive.ietf.org/arch/msg/regext/ 6871 EmKW32exlPgLbBUIbS8OjdYUJWc 6873 16.22. Changes REGEXT 09 to REGEXT 10 6875 1. Changes based on the feedback provided here: 6876 https://mailarchive.ietf.org/arch/msg/regext/ 6877 tmoKLAV6jhh2zp4JczjeWdr_jJE 6879 2. Changes based on the feedback provided here: 6880 https://mailarchive.ietf.org/arch/msg/regext/m7gyDTjHuRqIQCuKMHF- 6881 OLSS99k 6883 3. Changes based on the feedback provided here: 6884 https://mailarchive.ietf.org/arch/msg/ 6885 regext/3Acx5KHfeUdxZbx6A7zgoZHxIto 6887 4. Changes based on the feedback provided here: 6888 https://mailarchive.ietf.org/arch/msg/ 6889 regext/3Acx5KHfeUdxZbx6A7zgoZHxIto 6891 5. Changes based on the feedback provided here: 6892 https://mailarchive.ietf.org/arch/msg/ 6893 regext/7JiP2fzOr8KCnzI2rwoP-_KlxZY 6895 6. Changes based on the feedback provided here: 6896 https://mailarchive.ietf.org/arch/msg/regext/dbuyW5YTYj4VcFHUQYC- 6897 D8OMv_g 6899 7. Changes based on the feedback provided here: 6900 https://mailarchive.ietf.org/arch/msg/regext/ 6901 ExUZenwC81ZQe9x24-8IKT_FWm8 6903 17. Example of a Full Deposit using the XML model 6905 Example of a Full Deposit using the XML model: 6907 6908 6924 2019-10-17T00:00:00Z 6925 6926 1.0 6927 urn:ietf:params:xml:ns:rdeHeader-1.0 6928 6929 urn:ietf:params:xml:ns:rdeContact-1.0 6930 6931 urn:ietf:params:xml:ns:rdeHost-1.0 6932 6933 urn:ietf:params:xml:ns:rdeDomain-1.0 6934 6935 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6936 6937 urn:ietf:params:xml:ns:rdeIDN-1.0 6938 6939 urn:ietf:params:xml:ns:rdeNNDN-1.0 6940 6941 urn:ietf:params:xml:ns:rdeEppParams-1.0 6942 6943 6945 6946 6947 6948 6949 test 6950 2 6952 6953 1 6955 6956 1 6958 6959 1 6961 6962 1 6964 6965 1 6967 6968 1 6970 6971 6973 6974 6975 example1.example 6976 Dexample1-TEST 6977 6978 jd1234 6979 sh8013 6980 sh8013 6981 6982 ns1.example.com 6983 ns1.example1.example 6984 6985 RegistrarX 6986 RegistrarX 6987 1999-04-03T22:00:00.0Z 6988 2025-04-03T22:00:00.0Z 6989 6991 6992 6993 example2.example 6994 Dexample2-TEST 6995 6996 6997 jd1234 6998 sh8013 6999 sh8013 7000 RegistrarX 7001 RegistrarX 7002 1999-04-03T22:00:00.0Z 7003 2025-04-03T22:00:00.0Z 7004 7006 7007 7008 ns1.example1.example 7009 Hns1_example_test-TEST 7010 7011 7012 192.0.2.2 7013 192.0.2.29 7014 2001:DB8:1::1 7015 RegistrarX 7016 RegistrarX 7017 1999-05-08T12:10:00.0Z 7018 RegistrarX 7019 2009-10-03T09:34:00.0Z 7020 7022 7023 7024 sh8013 7025 Csh8013-TEST 7026 7027 7028 7029 John Doe 7030 Example Inc. 7031 7032 123 Example Dr. 7033 Suite 100 7034 Dulles 7035 VA 7036 20166-6503 7037 US 7038 7039 7040 +1.7035555555 7041 7042 +1.7035555556 7043 7044 jdoe@example.example 7045 7046 RegistrarX 7047 RegistrarX 7048 7049 2009-09-13T08:01:00.0Z 7050 7051 RegistrarX 7052 7053 2009-11-26T09:10:00.0Z 7054 7055 2009-12-03T09:05:00.0Z 7056 7057 7058 7059 7060 7061 7063 7064 7065 RegistrarX 7066 Registrar X 7067 8 7068 ok 7069 7070 7071 123 Example Dr. 7072 7073 Suite 100 7074 7075 Dulles 7076 VA 7077 20166-6503 7078 US 7079 7080 7081 +1.7035555555 7082 7083 +1.7035555556 7084 7085 jdoe@example.example 7086 7087 http://www.example.example 7088 7089 7090 whois.example.example 7091 7092 http://whois.example.example 7093 7094 7095 2005-04-23T11:49:00.0Z 7096 7097 2009-02-17T17:51:00.0Z 7098 7099 7101 7102 7103 7104 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 7105 7106 7107 http://registro.br/dominio/regras.html 7108 7109 7111 7112 7113 xn--exampl-gva.example 7114 pt-BR 7115 example1.example 7116 withheld 7117 2005-04-23T11:49:00.0Z 7118 7120 7121 7122 1.0 7123 en 7124 7125 urn:ietf:params:xml:ns:domain-1.0 7126 7127 7128 urn:ietf:params:xml:ns:contact-1.0 7129 7130 7131 urn:ietf:params:xml:ns:host-1.0 7132 7133 7134 urn:ietf:params:xml:ns:rgp-1.0 7135 7136 urn:ietf:params:xml:ns:secDNS-1.1 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7156 7157 7160 7161 7163 18. Example of Differential Deposit using the XML model 7165 Example of a Differential Deposit using the XML model: 7167 7168 7183 2019-10-17T00:00:00Z 7184 7185 1.0 7186 urn:ietf:params:xml:ns:rdeHeader-1.0 7187 7188 urn:ietf:params:xml:ns:rdeContact-1.0 7189 7190 urn:ietf:params:xml:ns:rdeHost-1.0 7191 7192 urn:ietf:params:xml:ns:rdeDomain-1.0 7193 7194 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7195 7196 urn:ietf:params:xml:ns:rdeIDN-1.0 7197 7198 urn:ietf:params:xml:ns:rdeNNDN-1.0 7199 7200 urn:ietf:params:xml:ns:rdeEppParams-1.0 7201 7202 7203 7204 7205 7206 example2.example 7207 7208 7210 7211 7212 7213 7214 test 7215 1 7217 7218 1 7220 7221 1 7223 7224 1 7226 7227 1 7229 7230 1 7232 7233 1 7235 7236 7237 7238 7240 19. Example of a Full Deposit using the CSV model 7242 Example of a Full Deposit using the CSV model: 7244 7245 7259 2019-10-18T00:00:00Z 7260 7261 1.0 7262 urn:ietf:params:xml:ns:csvDomain-1.0 7263 urn:ietf:params:xml:ns:csvHost-1.0 7264 urn:ietf:params:xml:ns:csvContact-1.0 7265 urn:ietf:params:xml:ns:csvRegistrar-1.0 7266 urn:ietf:params:xml:ns:csvIDN-1.0 7267 urn:ietf:params:xml:ns:csvNNDN-1.0 7268 urn:ietf:params:xml:ns:rdeEppParams-1.0 7269 7270 7271 7272 test 7273 7274 4 7275 7276 7277 6 7278 7279 7280 9 7281 7282 7283 3 7284 7285 7286 2 7287 7288 7289 2 7290 7291 7292 1 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7315 domain-YYYYMMDD.csv 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7328 domainContacts-YYYYMMDD.csv 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7343 domainStatuses-YYYYMMDD.csv 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7355 domainNameServers-name-YYYYMMDD.csv 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7367 domainNameServers-roid-YYYYMMDD.csv 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7383 dnssec-ds-YYYYMMDD.csv 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7396 7397 7398 7400 dnssec-key-YYYYMMDD.csv 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7419 domainTransfer-YYYYMMDD.csv 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7441 host-YYYYMMDD.csv 7442 7443 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7456 hostStatuses-YYYYMMDD.csv 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7469 hostAddresses-YYYYMMDD.csv 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7495 contact-YYYYMMDD.csv 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7509 contactStatuses-YYYYMMDD.csv 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7530 contactPostal-YYYYMMDD.csv 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7548 contactTransfer-YYYYMMDD.csv 7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7569 contactDisclose-YYYYMMDD.csv 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7601 registrar-YYYYMMDD.csv 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7615 idnLanguage-YYYYMMDD.csv 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7633 NNDN-YYYYMMDD.csv 7634 7635 7636 7638 7639 7640 1.0 7641 en 7642 urn:ietf:params:xml:ns:domain-1.0 7643 7644 urn:ietf:params:xml:ns:host-1.0 7645 7646 urn:ietf:params:xml:ns:contact-1.0 7647 7648 7649 urn:ietf:params:xml:ns:secDNS-1.1 7650 7651 urn:ietf:params:xml:ns:rgp-1.0 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7678 20. Example of Differential Deposit using the CSV model 7680 Example of a Differential Deposit using the CSV model: 7682 7683 7697 2019-10-18T00:00:00Z 7698 7699 1.0 7700 urn:ietf:params:xml:ns:csvDomain-1.0 7701 urn:ietf:params:xml:ns:csvHost-1.0 7702 urn:ietf:params:xml:ns:csvContact-1.0 7703 urn:ietf:params:xml:ns:csvRegistrar-1.0 7704 urn:ietf:params:xml:ns:csvIDN-1.0 7705 7706 7707 7708 7709 7710 7711 7712 7713 7715 domain-delete-YYYYMMDD.csv 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7728 host-delete-YYYYMMDD.csv 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7741 contact-delete-YYYYMMDD.csv 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7754 registrar-delete-YYYYMMDD.csv 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7767 idnLanguage-delete-YYYYMMDD.csv 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7780 NNDN-delete-YYYYMMDD.csv 7781 7783 7784 7785 7786 7787 7788 7789 test 7790 7791 2 7792 7793 7794 2 7795 7796 7797 3 7798 7799 7800 1 7801 7802 7803 1 7804 7805 7806 1 7807 7808 7809 1 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7832 domain-YYYYMMDD.csv 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7845 domainContacts-YYYYMMDD.csv 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7860 domainStatuses-YYYYMMDD.csv 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7872 domainNameServers-name-YYYYMMDD.csv 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7884 domainNameServers-roid-YYYYMMDD.csv 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7900 dnssec-ds-YYYYMMDD.csv 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7916 dnssec-key-YYYYMMDD.csv 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7935 domainTransfer-YYYYMMDD.csv 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7957 host-YYYYMMDD.csv 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7971 hostStatuses-YYYYMMDD.csv 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7984 hostAddresses-YYYYMMDD.csv 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8010 contact-YYYYMMDD.csv 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8024 contactStatuses-YYYYMMDD.csv 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8045 contactPostal-YYYYMMDD.csv 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8063 contactTransfer-YYYYMMDD.csv 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8084 contactDisclose-YYYYMMDD.csv 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8116 registrar-YYYYMMDD.csv 8117 8118 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8131 idnLanguage-YYYYMMDD.csv 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8149 NNDN-YYYYMMDD.csv 8150 8151 8152 8153 8154 8155 1.0 8156 en 8157 urn:ietf:params:xml:ns:domain-1.0 8158 8159 urn:ietf:params:xml:ns:host-1.0 8160 8161 urn:ietf:params:xml:ns:contact-1.0 8162 8163 8164 urn:ietf:params:xml:ns:secDNS-1.1 8165 8166 urn:ietf:params:xml:ns:rgp-1.0 8167 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8194 21. References 8196 21.1. Normative References 8198 [BCP195] Sheffer, Y., Holz, R., and P. Saint-Andre, 8199 "Recommendations for Secure Use of Transport Layer 8200 Security (TLS) and Datagram Transport Layer Security 8201 (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 8202 2015, . 8204 [I-D.ietf-regext-data-escrow] 8205 Lozano, G., "Registry Data Escrow Specification", draft- 8206 ietf-regext-data-escrow-10 (work in progress), June 2020. 8208 [ISO-3166-1] 8209 3166, I. S., "Codes for the representation of names of 8210 countries and their subdivisions -- Part 1: Country 8211 codes", ISO Standard 3166, November 2006. 8213 [ITU-E164] 8214 International Telecommunication Union, "The international 8215 public telecommunication numbering plan", ITU-T 8216 Recommendation E.164, February 2005. 8218 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8219 DOI 10.17487/RFC0791, September 1981, 8220 . 8222 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8223 Requirement Levels", BCP 14, RFC 2119, 8224 DOI 10.17487/RFC2119, March 1997, 8225 . 8227 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8228 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8229 . 8231 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8232 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8233 DOI 10.17487/RFC3915, September 2004, 8234 . 8236 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8237 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8238 . 8240 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8241 Domain Name Mapping", STD 69, RFC 5731, 8242 DOI 10.17487/RFC5731, August 2009, 8243 . 8245 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8246 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8247 August 2009, . 8249 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8250 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8251 August 2009, . 8253 [RFC5891] Klensin, J., "Internationalized Domain Names in 8254 Applications (IDNA): Protocol", RFC 5891, 8255 DOI 10.17487/RFC5891, August 2010, 8256 . 8258 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8259 Security Extensions Mapping for the Extensible 8260 Provisioning Protocol (EPP)", RFC 5910, 8261 DOI 10.17487/RFC5910, May 2010, 8262 . 8264 [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 8265 Address Text Representation", RFC 5952, 8266 DOI 10.17487/RFC5952, August 2010, 8267 . 8269 [RFC6234] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms 8270 (SHA and SHA-based HMAC and HKDF)", RFC 6234, 8271 DOI 10.17487/RFC6234, May 2011, 8272 . 8274 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 8275 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 8276 May 2017, . 8278 [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS 8279 Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, 8280 January 2019, . 8282 [V42] International Telecommunication Union, "V.42 : Error- 8283 correcting procedures for DCEs using asynchronous-to- 8284 synchronous conversion", March 2002, 8285 . 8287 [W3C.REC-xml-20081126] 8288 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 8289 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 8290 Edition) REC-xml-20081126", November 2008, 8291 . 8293 [W3C.REC-xmlschema-1-20041028] 8294 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 8295 "XML Schema Part 1: Structures Second Edition REC- 8296 xmlschema-1-20041028", October 2004, 8297 . 8299 [W3C.REC-xmlschema-2-20041028] 8300 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 8301 Second Edition REC-xmlschema-2-20041028", October 2004, 8302 . 8304 [W3C.REC-xpath-31-20170321] 8305 Robie, J., Dyck, M., and J. Spiegel, "XML Path Language 8306 (XPath) 3.1", March 2017, 8307 . 8309 21.2. Informative References 8311 [ICANN-GTLD-AGB-20120604] 8312 ICANN, "gTLD Applicant Guidebook Version 2012-06-04", June 8313 2012, . 8316 [ICANN-GTLD-RA-20170731] 8317 ICANN, "Base Registry Agreement 2017-07-31", July 2017, 8318 . 8321 [RFC1952] Deutsch, P., "GZIP file format specification version 4.3", 8322 RFC 1952, DOI 10.17487/RFC1952, May 1996, 8323 . 8325 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, 8326 DOI 10.17487/RFC2818, May 2000, 8327 . 8329 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8330 DOI 10.17487/RFC3688, January 2004, 8331 . 8333 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8334 DOI 10.17487/RFC3912, September 2004, 8335 . 8337 [RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma- 8338 Separated Values (CSV) Files", RFC 4180, 8339 DOI 10.17487/RFC4180, October 2005, 8340 . 8342 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8343 Code: The Implementation Status Section", BCP 205, 8344 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8345 . 8347 [variantTLDsReport] 8348 Internet Corporation for Assigned Names and Numbers 8349 (ICANN), "A Study of Issues Related to the Management of 8350 IDN Variant TLDs", February 2012, 8351 . 8354 Authors' Addresses 8356 Gustavo Lozano 8357 Internet Corporation for Assigned Names and Numbers 8358 12025 Waterfront Drive, Suite 300 8359 Los Angeles 90292 8360 United States of America 8362 Phone: +1.310.823.9358 8363 Email: gustavo.lozano@icann.org 8365 James Gould 8366 VeriSign, Inc. 8367 12061 Bluemont Way 8368 Reston 20190 8369 United States of America 8371 Email: jgould@verisign.com 8373 Chethan Thippeswamy 8374 VeriSign, Inc. 8375 12061 Bluemont Way 8376 Reston 20190 8377 United States of America 8379 Email: cthippeswamy@verisign.com