idnits 2.17.00 (12 Aug 2021) /tmp/idnits20837/draft-ietf-regext-dnrd-objects-mapping-11.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 (Dec 16, 2020) is 514 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) == Outdated reference: draft-ietf-regext-data-escrow has been published as RFC 8909 -- 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 -- Possible downref: Non-RFC (?) normative reference: ref. 'V42' Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 4 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: June 19, 2021 C. Thippeswamy 6 VeriSign 7 Dec 16, 2020 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-11 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 June 19, 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 16.23. Changes REGEXT 10 to REGEXT 11 . . . . . . . . . . . . . 151 129 17. Example of a Full Deposit using the XML model . . . . . . . . 151 130 18. Example of Differential Deposit using the XML model . . . . . 157 131 19. Example of a Full Deposit using the CSV model . . . . . . . . 158 132 20. Example of Differential Deposit using the CSV model . . . . . 168 133 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 178 134 21.1. Normative References . . . . . . . . . . . . . . . . . . 178 135 21.2. Informative References . . . . . . . . . . . . . . . . . 181 136 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182 138 1. Introduction 140 Registry Data Escrow (RDE) is the process by which a registry 141 periodically submits data deposits to a third-party called an escrow 142 agent. These deposits comprise the minimum data needed by a third- 143 party to resume operations if the registry cannot function and is 144 unable or unwilling to facilitate an orderly transfer of service. 145 For example, for a domain name registry or registrar, the data to be 146 deposited would include all the objects related to registered domain 147 names, e.g., names, contacts, name servers, etc. 149 The goal of data escrow is higher resiliency of registration 150 services, for the benefit of Internet users. The beneficiaries of a 151 registry are not just those registering information there, but also 152 the users of services relying on the registry data. 154 In the context of domain name registries, registration data escrow is 155 a requirement for generic top-level domains (e.g., Specification 2 of 156 the ICANN Base Registry Agreement, see [ICANN-GTLD-RA-20170731]) and 157 some country code top-level domain managers are also currently 158 escrowing data. There is also a similar requirement for ICANN- 159 accredited domain registrars. 161 This document defines the standard set of objects for a Domain Name 162 Registry that uses the Registry Data Escrow Specification described 163 in [I-D.ietf-regext-data-escrow] for escrow. The set of objects 164 include: 166 o Domain: Internet domain names that are typically provisioned in a 167 Domain Name Registry using the EPP domain name mapping [RFC5731]. 168 The attributes defined in the EPP domain name mapping [RFC5731] 169 are fully supported by this document. 171 o Host: Internet host names that are typically provisioned in a 172 Domain Name Registry using the EPP host mapping [RFC5732]. The 173 attributes defined in the EPP host mapping [RFC5732] are fully 174 supported by this document. 176 o Contact: Individual or organization social information provisioned 177 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 178 The attributes defined in the EPP contact mapping [RFC5733] are 179 fully supported by this document. 181 o Registrar: The organization that sponsors objects like domains, 182 hosts, and contacts in a Domain Name Registry. 184 o NNDN (NNDN's not domain name): Domain Name Registries may maintain 185 domain names without being persisted as domain objects in the 186 registry system, for example, a list of reserved names not 187 available for registration. The NNDN is a lightweight domain-like 188 object that is used to escrow domain names not maintained as 189 domain name objects. 191 This document defines the following pseudo-objects: 193 o IDN Table Reference: Internationalized Domain Names (IDN) included 194 in the Domain Object Data Escrow include references to the IDN 195 Table and Policy used in IDN registration. 197 o EPP parameters: Contains the EPP parameters supported by the 198 Registry Operator. 200 o Header: Used to specify counters of objects in the database at a 201 certain point in time (watermark). 203 o Policy: Used to specify OPTIONAL elements from this specification 204 that are REQUIRED based on the business model of the registry. 206 Extensible Markup Language (XML) 1.0 as described in 207 [W3C.REC-xml-20081126] and XML Schema notation as described in 208 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028] are 209 used in this specification. 211 2. Models 213 This document defines two different models that can be used to 214 deposit data escrow objects: XML and CSV. 216 The data escrow deposit MAY contain a mix of both models but an 217 object MUST be escrowed only in one model. 219 This document does not suggest the use of a particular model, and 220 both are equivalent. A Domain Name Registry may choose the model 221 that is more appropriate for the peculiarities of its systems. For 222 example, a registry may use the CSV-export functionality of the 223 Relational Database Management System (RDBMS) for escrow; therefore, 224 the CSV model may be more appropriate. Another registry may use the 225 code developed for EPP to implement escrow. 227 2.1. XML Model 229 XML: The XML model includes all the deposit information (meta-data 230 and data) in an XML document. The definition of the XML format is 231 fully defined in the XML schemas. As a convention, the objects 232 represented using the XML model are referenced using RDE and an XML 233 namespace that is prefixed with "rde". For example, the Domain Name 234 object represented using the XML model can be referred to as the RDE 235 Domain Name with the XML namespace including rdeDomain 236 (urn:ietf:params:xml:ns:rdeDomain-1.0). 238 2.2. CSV Model 240 CSV: The CSV model uses XML to define the data escrow format of the 241 data contained in referenced Comma-Separated Values (CSV) files. As 242 a convention, the objects represented using the CSV model is 243 referenced using CSV and an XML namespace that is prefixed with 244 "csv". For example, the Domain Name object represented using the CSV 245 model can be referred to as the CSV Domain Name with the XML 246 namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). 248 3. Terminology 250 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 251 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 252 "OPTIONAL" in this document are to be interpreted as described in BCP 253 14 [RFC2119] [RFC8174] when, and only when, they appear in all 254 capitals, as shown here. 256 3.1. Glossary 258 In the following section, the most common terms are briefly 259 explained: 261 o Allocated: a status of some label with respect to a zone, whereby 262 the label is associated administratively to some entity that has 263 requested the label. This term (and its cognates "allocation" and 264 "to allocate") may represent the first step on the way to 265 delegation in the DNS. 267 o Comma-Separated Values (CSV), see [RFC4180]. 269 o Domain name: see definition of Domain name in [RFC8499]. 271 o Extensible Provisioning Protocol (EPP), see definition of the 272 Extensible Provisioning Protocol in [RFC8499]. 274 o Fully-Qualified Domain Name (FQDN), see definition of FQDN in 275 [RFC8499]. 277 o Internationalized Domain Name (IDN), see definition of 278 Internationalized Domain Name in [RFC8499]. 280 o Label: see definition of Label in [RFC8499]. 282 o Registrant: see definition of Registrant in [RFC8499]. 284 o Registrar: see definition of Registrar in [RFC8499]. 286 o Registry: see definition of Registry in [RFC8499]. 288 o Registry-class domain name (RCDN): refers to a top-level domain 289 (TLD) or any other domain name at any level in the DNS tree for 290 which a Registry (either directly or through an affiliate company) 291 provides Registry Services for other organizations or individuals. 292 For example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 294 o Registry Data Escrow (RDE): registry data escrow is the process by 295 which a registry periodically submits data deposits to a third- 296 party called an escrow agent. These deposits comprise the minimum 297 data needed by a third-party to resume operations if the registry 298 cannot function and is unable or unwilling to facilitate an 299 orderly transfer of service. 301 o Registry services: services offered by the Registry critical to 302 the following tasks: the provisioning of domain names on receipt 303 of requests and data from registrars; responding to registrar 304 queries for status information relating to the DNS servers for the 305 RCDN; dissemination of RCDN zone files; operation of the Registry 306 DNS servers; responding to queries for contact and other 307 information concerning DNS registrations in the RCDN; and any 308 other products or services that only a Registry is capable of 309 providing, by reason of its designation as the Registry. Typical 310 examples of Registry Services are DNS resolution for the RCDN, 311 WHOIS and EPP. 313 o SRS: Shared Registration System, see also 314 [ICANN-GTLD-AGB-20120604]. 316 o Top-Level Domain Name (TLD), see definition of Top-Level Domain in 317 [RFC8499]. 319 o UTC: Coordinated Universal Time, as maintained by the Bureau 320 International des Poids et Mesures (BIPM); see also [RFC3339]. 322 4. Conventions Used in This Document 324 4.1. Date and Time 326 Numerous fields indicate "dates", such as the creation and expiry 327 dates for domain names. These fields SHALL contain timestamps 328 indicating the date and time in UTC as specified in [RFC3339], with 329 no offset from the zero meridian. 331 4.2. Country names 333 Country identifiers SHALL be represented using two character 334 identifiers as specified in [ISO-3166-1]. 336 4.3. Telephone numbers 338 Telephone numbers (both voice and facsimile) SHALL be formatted based 339 on structures defined in [ITU-E164]. Telephone numbers described in 340 this specification are character strings that MUST begin with a plus 341 sign ("+", ASCII value 0x2B), followed by a country code defined in 342 [ITU-E164], followed by a dot (".", ASCII value 0x2E), followed by a 343 sequence of digits representing the telephone number. 345 4.4. CSV Integrity Check 347 A checksum MAY be used to verify the integrity of the CSV files, for 348 example, if another layer (i.e., encryption of an archive containing 349 the deposit files) does not provide integrity. By default the CRC32 350 algorithm (see, 8.1.1.6.2 of [V42]) is used. A stronger algorithm, 351 such as SHA-256 (see, [RFC6234]) MAY be used for enhanced security if 352 required. 354 4.5. IP addresses 356 The syntax of IP addresses MUST conform to the text representation of 357 either Internet Protocol Version 4 [RFC0791] or Internet Protocol 358 Version 6 [RFC5952]. 360 4.6. Conventions applicable to the CSV Model 362 4.6.1. CSV Parent Child Relationship 364 The CSV model represents a relational model, where the CSV files 365 represent relational tables, the fields of the CSV files represent 366 columns of the tables, and each line of the CSV file represents a 367 record. As in a relational model, the CSV files can have 368 relationships utilizing primary keys in the parent CSV file 369 definitions and foreign keys in the child CSV file definitions for a 370 1-to-many relationship. The primary keys are not explicitly defined, 371 but the foreign keys are using the boolean "parent" field attribute 372 in the child CSV file. The relationships between the CSV files are 373 used to support a cascade replace or cascade delete of records 374 starting from the parent record in Differential and Incremental 375 Deposits (see [I-D.ietf-regext-data-escrow]). 377 The following is an example of the CSV file definitions, using the 378 element (see Section 4.6.2.1), for a Sample object 379 consisting of a parent "sample" CSV File Definition and a child 380 "sampleStatuses" CSV File Definition. The primary key for the Sample 381 object is the field that is used as the foreign key 382 in the "sampleStatuses" CSV File Definition by specifying the 383 "parent=true" attribute. If a Sample record is updated or deleted in 384 a Differential or Incremental Deposit, it should cascade replace the 385 data using the records included in the child "sampleStatuses" CSV 386 File Definition or cascade delete the existing records in the child 387 "sampleStatuses" CSV File Definition, respectively. 389 390 ... 391 392 393 394 395 396 397 398 399 400 401 402 403 404 406 sample-YYYYMMDD.csv 407 408 409 410 411 412 413 414 415 416 417 418 420 sampleStatuses-YYYYMMDD.csv 421 422 423 424 ... 425 427 4.6.2. CSV elements 429 4.6.2.1. element 431 To support the CSV model, an element is defined for each object that 432 substitutes for the element and for the 433 element, that contains one or more elements. For 434 example, the Domain Name Object (Section 5.1) defines the 435 element, that substitutes for the 436 element, and the element, that substitutes for 437 the element. Both the element and 438 the elements contain one or more 439 elements. The element has the following child elements: 441 Ordered list of CSV fields used in the CSV files. 442 There are one or more child elements that substitute for the 443 abstract element. Each element defines the format 444 of the CSV field contained in the CSV files. The 445 elements support the "type" attribute that defines the XML simple 446 data type of the field element. The elements 447 support the "isRequired" attribute, with a default value of 448 "false", when set to "true" indicates that the field must be non- 449 empty in the CSV files and when set to "false" indicates that the 450 field MAY be empty in the CSV files. The "isRequired" attribute 451 MAY be specifically set for the field elements within the XML 452 schema and MAY be overridden when specifying the fields under the 453 element. The element supports an 454 OPTIONAL "parent" attribute that identifies the field as a 455 reference to a parent object, as defined in CSV Parent Child 456 Relationship (Section 4.6.1). For example, the field SHOULD set the 458 "parent" attribute to "true" to identify it as the parent domain 459 name of the domain status. 461 A list of one or more CSV files using the 462 child element. The child element 463 defines a reference to the CSV file name and has the following 464 optional attributes: 466 compression If the CSV file is compressed, the "compression" 467 attribute defines the compression format. For example, setting 468 this attribute to "gzip" signals that the CSV file is 469 compressed using the GZIP file format (see, [RFC1952]). The 470 supported compression formats are negotiated out-of-band. 472 encoding Defines the encoding of the CSV file with the default 473 encoding of "UTF-8". 475 cksum Defines the checksum of the CSV file, as described in 476 Section 4.4, using the algorithm defined by the "cksumAlg" 477 attribute. If the "cksumAlg" attribute is not present, the 478 checksum is calculated using "CRC32". 480 cksumAlg Defines the checksum algorithm used to calculate the 481 "cksum" attribute, with the default value of "CRC32". If the 482 value "SHA256" is specified, the SHA-256 algorithm (see, 483 [RFC6234]) MUST be used to calculate the "cksum" attribute. 484 Parties receiving and processing data escrow deposits MUST 485 support CRC32 and SHA-256. If this attribute is present, the 486 "cksum" attribute MUST also be present. Additional checksum 487 algorithms are negotiated out-of-band. 489 The element requires a "name" attribute that defines the 490 purpose of the CSV file with values like "domain", "host", "contact". 491 The supported "name" attribute values are defined for each object 492 type. The OPTIONAL "sep" attribute defines the CSV separator 493 character with the default separator character of ",". The need for 494 quoting/escaping of the CSV data could be avoided by choosing a 495 separator character that is not in the data set of the CSV files. 497 The following is an example of the 498 element for domain name records where the is set 499 as required with isRequired="true". 501 502 ... 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 522 domain-YYYYMMDD.csv 523 524 525 526 ... 527 529 The following is example of the "domain-YYYYMMDD.csv" file with one 530 record matching the definition. 532 domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 533 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 534 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 535 The following is an example of the 536 element for domain name records. 538 539 ... 540 541 542 543 544 545 547 domain-delete-YYYYMMDD.csv 548 549 550 551 ... 552 554 The following is example of the "domain-delete-YYYYMMDD.csv" file 555 with three records that matches the single field. 557 domain1.example 558 domain2.example 559 domainN.example 561 4.6.2.2. CSV common field elements 563 The element defined in the element 564 (Section 4.6.2.1) section has child elements that substitute for the 565 abstract element. By convention 566 elements include an 'f' prefix to identify them as field definition 567 elements. There are a set of common field elements that are used 568 across multiple data escrow objects. The common field elements are 569 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 570 using the "rdeCsv" sample namespace prefix. The CSV common field 571 elements include: 573 UTF-8 encoded name field with 574 type="eppcom:labelType". 576 Repository Object IDentifier (ROID) field with 577 type="eppcom:roidType" and isRequired="true". 579 Registrant contact identifier with 580 type="eppcom:clIDType". 582 The object status description, which is 583 free form text describing the rationale for the status, with 584 type="normalizedString". 586 Identifier of the client (registrar) that sponsors 587 the object with type="eppcom:clIDType" and isRequired="true". 589 Identifier of the registrar, defined in Section 5.4, 590 of the client that created the object with type="eppcom:clIDType". 592 Identifier of the client that created the object with 593 type="eppcom:clIDType". 595 Identifier of the registrar, defined in Section 5.4, 596 of the client that last updated the object with 597 type="eppcom:clIDType". 599 Identifier of the client that last updated the object 600 with type="eppcom:clIDType". 602 Identifier of the registrar, defined in Section 5.4, 603 of the client that requested the transfer with 604 type="eppcom:clIDType" and isRequired="true". 606 Identifier of the client that requested the transfer 607 with type="eppcom:clIDType". 609 Identifier of the registrar, defined in Section 5.4, 610 of the client that should take or took action with 611 type="eppcom:clIDType" and isRequired="true". 613 Identifier of the client that should take or took 614 action for transfer with type="eppcom:clIDType". 616 Created date of object with type="dateTime". 618 Updated date of object with type="dateTime". 620 Expiration date of object with type="dateTime". 622 Date that transfer was requested with 623 type="dateTime" and isRequired="true". 625 Date that transfer action should be taken or has 626 been taken with type="dateTime" and isRequired="true". 628 Date of last transfer with type="dateTime". 630 State of the most recent transfer request with 631 type="eppcom:trStatusType" and isRequired="true". 633 General token field with type="token". 635 General language field with type="language". 637 IDN Table Identifier used for IDN domain names 638 with type="token". 640 General positive integer field with 641 type="positiveInteger". 643 Contains the URL of an object like a registrar object 644 with type="anyURI". 646 Custom field with name attribute that defines the 647 custom field name" with type="token". 649 4.6.3. Internationalized and Localized Elements 651 Some elements MAY be provided in either internationalized form 652 ("int") or localized form ("loc"). Those elements use a field value 653 or "isLoc" attribute to specify the form used. If an "isLoc" 654 attribute is used, a value of "true" indicates the use of the 655 localized form and a value of "false" indicates the use of the 656 internationalized form. This MAY override the form specified for a 657 parent element. A value of "int" is used to indicate the 658 internationalized form and a value of "loc" is used to indicate the 659 localized form. When the internalized form ("int") is provided, the 660 field value MUST be represented in a subset of UTF-8 that can be 661 represented in the 7-bit US-ASCII character set. When the localized 662 form ("loc") is provided, the field value MAY be represented in 663 unrestricted UTF-8. 665 The field elements below of the "registrar" 666 element specify the internationalized form with the 667 isLoc="false" attribute. 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 701 703 registrar-YYYYMMDD.csv 704 705 706 707 ... 708 709 ... 711 The following is an example of using the 712 field value to define the internationalized or localized form of the 713 remainder of the "contactPostal" field values. 715 ... 716 717 ... 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 735 contactPostal-YYYYMMDD.csv 736 737 738 739 ... 740 741 ... 743 5. Object Description 745 This section describes the base objects supported by this 746 specification: 748 5.1. Domain Name Object 750 The domain name object is based on the EPP domain name mapping 751 specified in [RFC5731]. The domain name object supports both the XML 752 Model and the CSV Model, defined in the Models (Section 2) section. 753 The elements used for both models are defined in the following 754 sections. 756 5.1.1. XML Model 758 There are two elements used in the data escrow of the domain name 759 objects for the XML model including the , under the 760 element, and the element, under the 761 element. 763 5.1.1.1. object 765 The domain element is based on the EPP domain response for an 766 authorized client (see Section 3.1.2. of [RFC5731]) with additional 767 data from an EPP Query Response, see Section 3.1.3. of 768 [RFC5731], Registry Grace Period (RGP) status from [RFC3915], and 769 data from the EPP command, see Section 5.2.1. of 770 [RFC5910]. 772 A element substitutes for the abstract 773 element to define a concrete definition of a domain. The 774 element can be replaced by other domain definitions 775 using the XML schema substitution groups feature. 777 The element contains the following child elements: 779 o A element that contains the fully-qualified name of the 780 domain name object. For IDNs the A-Label is used (see [RFC5891], 781 Section 4.4). 783 o A element that contains the repository object identifier 784 assigned to the domain name object when it was created. 786 o An OPTIONAL element that contains the fully-qualified 787 domain name in Unicode character set. It MUST be provided if 788 available. 790 o An OPTIONAL element that references the IDN 791 Table used for the IDN. This corresponds to the "id" attribute of 792 the element. This element MUST be present if the 793 domain name is an IDN. 795 o An OPTIONAL element is used to indicate that the 796 domain name is an IDN variant. This element contains the domain 797 name used to generate the IDN variant. 799 o One or more elements that contain the current status 800 descriptors associated with the domain name. 802 o Zero or more OPTIONAL elements to represent 803 "pendingDelete" sub-statuses, including "redemptionPeriod", 804 "pendingRestore", and "pendingDelete", that a domain name can be 805 in as a result of grace period processing as specified in 806 [RFC3915]. 808 o An OPTIONAL element that contains the identifier for 809 the human or organizational social information object associated 810 as the holder of the domain name object. 812 o Zero or more OPTIONAL elements that contain identifiers 813 for the human or organizational social information objects 814 associated with the domain name object. 816 o An OPTIONAL element that contains the fully-qualified names 817 of the delegated host objects or host attributes (name servers) 818 associated with the domain name object. See Section 1.1 of 819 [RFC5731] for a description of the elements used to specify host 820 objects or host attributes. 822 o A element that contains the identifier of the sponsoring 823 registrar. 825 o An OPTIONAL element that contains the identifier of the 826 registrar that created the domain name object. An OPTIONAL client 827 attribute is used to specify the client that performed the 828 operation. 830 o An OPTIONAL element that contains the date and time of 831 the domain name object creation. This element MUST be present if 832 the domain name has been allocated. 834 o An OPTIONAL element that contains the date and time 835 identifying the end (expiration) of the domain name object's 836 registration period. This element MUST be present if the domain 837 name has been allocated. 839 o An OPTIONAL element that contains the identifier of the 840 registrar that last updated the domain name object. This element 841 MUST NOT be present if the domain has never been modified. An 842 OPTIONAL client attribute is used to specify the client that 843 performed the operation. 845 o An OPTIONAL element that contains the date and time of 846 the most recent domain-name-object modification. This element 847 MUST NOT be present if the domain name object has never been 848 modified. 850 o An OPTIONAL element that contains the public key 851 information associated with Domain Name System security (DNSSEC) 852 extensions for the domain name as specified in [RFC5910]. 854 o An OPTIONAL element that contains the date and time of 855 the most recent domain name object successful transfer. This 856 element MUST NOT be present if the domain name object has never 857 been transferred. 859 o An OPTIONAL element that contains the following child 860 elements related to the last transfer request of the domain name 861 object. This element MUST NOT be present if a transfer request 862 for the domain name has never been created. 864 * A element that contains the state of the most recent 865 transfer request. 867 * A element that contains the identifier of the registrar 868 that requested the domain name object transfer. An OPTIONAL 869 client attribute is used to specify the client that performed 870 the operation. 872 * A element that contains the date and time that the 873 transfer was requested. 875 * An element that contains the identifier of the registrar 876 that should act upon a PENDING transfer request. For all other 877 status types, the value identifies the registrar that took the 878 indicated action. An OPTIONAL client attribute is used to 879 specify the client that performed the operation. 881 * An element that contains the date and time of a 882 required or completed response. For a PENDING request, the 883 value identifies the date and time by which a response is 884 required before an automated response action will be taken by 885 the registry. For all other status types, the value identifies 886 the date and time when the request was completed. 888 * An OPTIONAL element that contains the end of the 889 domain name object's validity period (expiry date) if the 890 transfer caused or causes a change in the validity period. 892 Example of a domain name object: 894 ... 895 896 xn--exampl-gva.example 897 Dexample1-TEST 898 pt-BR 899 example.example 900 901 jd1234 902 sh8013 903 sh8013 904 905 ns1.example.com 906 ns1.example1.example 907 908 RegistrarX 909 RegistrarX 910 1999-04-03T22:00:00.0Z 911 2025-04-03T22:00:00.0Z 912 913 ... 915 5.1.1.2. object 917 The element contains the fully-qualified domain 918 name that was deleted and purged. 920 Example of object: 922 ... 923 924 ... 925 926 foo.example 927 bar.example 928 929 ... 930 931 ... 933 5.1.2. CSV Model 935 For the CSV Model of the domain name object, the 936 child element of the element is used to hold the new 937 or updated domain name objects for the deposit. The 938 child element of the element is 939 used to hold the deleted or purged domain name objects for the 940 deposit. Both the and 941 elements contain one or more elements with a set of 942 named CSV file definitions using the "name" attribute. 944 Differential and Incremental Deposits are based on changes to the 945 domain name objects. The updated domain name object data under the 946 element is a cascade replace down all of the 947 domain name CSV files starting with the parent "domain" CSV File 948 Definition (Section 5.1.2.1.1). The child CSV file definitions 949 include a field. All the child CSV 950 file definition data for the domain name objects in the parent 951 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 952 deleted and then set using the data in the child CSV files. The 953 deleted domain name object data under the element 954 is a cascade delete starting from the "domain" Deletes CSV File 955 Definition (Section 5.1.2.2.1). 957 5.1.2.1. 959 The is used to hold the new or updated domain 960 name object information for the deposit. The is 961 split into separate CSV file definitions using named 962 elements with the "name" attribute. The following sections include 963 the supported domain name CSV file definitions: 965 5.1.2.1.1. "domain" CSV File Definition 967 The "domain" CSV File Definition defines the fields and CSV file 968 references used for the parent domain name object records. All the 969 other domain name CSV file definitions are child CSV files based on 970 the inclusion of the field. 972 The following "csvDomain" field elements MUST be used in the "domain" 973 element: 975 Domain name field with type="eppcom:labelType" and 976 isRequired="true". 978 The following "csvDomain" field elements MAY be used in the "domain" 979 element: 981 Fully-qualified name of the original IDN 982 domain name object related to the variant domain name object with 983 type="eppcom:labelType". 985 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 986 "domain" element: 988 Registry Object IDentifier (ROID) for the domain name 989 object with isRequired="true". 991 or A choice of: 993 Identifier of the sponsoring client with 994 isRequired="true". 996 Contains the Globally Unique Registrar 997 Identifier (GURID) assigned by ICANN with 998 type="positiveInteger" and isRequired="true". 1000 The following "rdeCsv" fields, defined in section CSV common field 1001 elements (Section 4.6.2.2), MAY be used in the "domain" 1002 element: 1004 Identifier of the registrar, defined in Section 5.4, 1005 of the client that created the domain name object. 1007 Identifier of the client that created the domain name 1008 object. 1010 Identifier of the registrar, defined in Section 5.4, 1011 of the client that last updated the domain name object. 1013 Identifier of the client that last updated the domain 1014 name object. 1016 UTF8 encoded domain name for the 1017 field element. 1019 IDN Table Identifier used for the IDN domain 1020 name object that MUST match a field element 1021 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 1023 Registrant contact identifier for the domain 1024 name object. 1026 Created date and time of the domain name object. 1028 Date and time of the last update to the domain name 1029 object. This field MUST NOT be set if the domain name object has 1030 never been modified. 1032 Expiration date and time for the domain name 1033 object. 1035 Date and time of the last transfer for the domain 1036 name object. This field MUST NOT be set if the domain name object 1037 has never been transferred. 1039 Example of a "domain" element. 1041 ... 1042 1043 ... 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1063 domain-YYYYMMDD.csv 1064 1065 1066 1067 ... 1068 1069 ... 1071 Example of the corresponding domain-YYYYMMDD.csv file. The file 1072 contains four records (two active ASCII domains, original IDN with 1073 LANG-1 language rules, and variant IDN with LANG-1 language rules). 1075 domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 1076 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1077 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 1078 domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 1079 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 1080 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 1081 xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 1082 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1083 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 1084 xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example, 1085 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 1086 registrarX,clientY,2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 1088 5.1.2.1.2. "domainContacts" CSV File Definition 1090 The "domainContacts" CSV File Definition defines the fields and CSV 1091 file references used for the domain name object link records to 1092 contact objects, as described in Contact Object (Section 5.3). 1094 The following "csvDomain" field elements, defined for the "domain" 1095 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 1096 "domainContacts" element: 1098 The name of the domain object that is linked to 1099 the contact object with isRequired="true". 1101 The contact type for the contact object 1102 link with type="domain:contactAttrType" and isRequired="true". 1103 The supported contact type values include "admin" for the 1104 administration contact, "billing" for the billing contact, and 1105 "tech" for the technical contact. 1107 The following "csvContact" fields, defined for the "contact" CSV File 1108 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 1109 element: 1111 The server-unique contact identifier with 1112 isRequired="true". 1114 Example of a "domainContacts" 1115 element. 1117 ... 1118 1119 ... 1120 1121 1122 1123 1124 1125 1126 1127 1129 domainContacts-YYYYMMDD.csv 1130 1131 1132 1133 ... 1134 1135 ... 1137 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1138 file contains an admin, tech, and billing contact for the four domain 1139 names domain1.example, domain2.example, xn--bc123-3ve.example and 1140 xn--bc321-3ve.example. 1142 domain1.example,domain1admin,admin 1143 domain1.example,domain1tech,tech 1144 domain1.example,domain1billing,billing 1145 domain2.example,domain2admin,admin 1146 domain2.example,domain2tech,tech 1147 domain2.example,domain2billing,billing 1148 xn--bc123-3ve.example,xnabc123admin,admin 1149 xn--bc123-3ve.example,xnabc123tech,tech 1150 xn--bc123-3ve.example,xnabc123billing,billing 1151 xn--bc321-3ve.example,xnabc123admin,admin 1152 xn--bc321-3ve.example,xnabc123tech,tech 1153 xn--bc321-3ve.example,xnabc123billing,billing 1155 5.1.2.1.3. "domainStatuses" CSV File Definition 1157 The "domainStatuses" CSV File Definition defines the fields and CSV 1158 file references used for the domain name object statuses. 1160 The following "csvDomain" fields, defined for the "domain" CSV File 1161 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1162 element: 1164 Domain name of status with isRequired="true". 1166 The status of the domain name with 1167 type="domain:statusValueType" and isRequired="true". 1169 The RGP status, as a sub-status of the 1170 "pendingDelete" status value, with 1171 type="rgp:statusValueType" as defined in [RFC3915]. 1173 The following "rdeCsv" fields, defined in section CSV common field 1174 elements (Section 4.6.2.2), MAY be used in the "domainStatuses" 1175 element: 1177 Domain name object status description 1178 which is free form text describing the rationale for the status. 1180 Language of the field. 1182 Example of a "domainStatuses" 1183 element. 1185 ... 1186 1187 ... 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1199 domainStatuses-YYYYMMDD.csv 1200 1201 1202 1203 ... 1204 1205 ... 1207 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1208 file contains the statuses for the four domain names domain1.example, 1209 domain2.example, xn--bc123-3ve.example and xn--bc321-3ve.example. 1211 domain1.example,clientUpdateProhibited,"Disallow update", 1212 en, 1213 domain1.example,clientDeleteProhibited,"Disallow delete", 1214 en, 1215 domain2.example,ok,,, 1216 xn--bc123-3ve.example,ok,,, 1217 xn--bc321-3ve.example,ok,,, 1219 5.1.2.1.4. "domainNameServers" CSV File Definition 1221 The "domainNameServers" CSV File Definition defines the fields and 1222 CSV file references used for the domain name delegated hosts (name 1223 servers). The "domainNameServers" CSV files define the relationship 1224 between a domain name object and a delegated host. The 1225 "domainNameServers" CSV File is used to support the 1226 model, defined in [RFC5731]. 1228 The following "csvDomain" fields, defined for the "domain" CSV File 1229 Definition (Section 5.1.2.1.1), MUST be used in the 1230 "domainNameServers" element: 1232 Domain name using the delegated host with 1233 isRequired="true". 1235 The following "csvHost" and "rdeCsv" field elements MUST be used in 1236 the "domainNameServers" element: 1238 or A choice of: 1240 Host name field with type="eppcom:labelType" and 1241 isRequired="true". 1243 Host object Registry Object IDentifier (ROID) 1244 assigned to the host object with isRequired="true". 1246 Example of a "domainNameServers" 1247 element. 1249 ... 1250 1251 ... 1252 1253 1254 1255 1256 1257 1258 1260 domainNameServers-YYYYMMDD.csv 1261 1262 1263 1264 ... 1265 1266 ... 1268 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1269 The file contains the delegated hosts (name servers) for the four 1270 domain names domain1.example, domain2.example, xn--bc123-3ve.example 1271 and xn--bc321-3ve.example referenced via the field 1272 element. 1274 domain1.example,Hns1_domain1_test-TEST 1275 domain1.example,Hns2_domain1_test-TEST 1276 domain2.example,Hns1_domain2_test-TEST 1277 domain2.example,Hns2_domain2_test-TEST 1278 xn--bc123-3ve.example,Hns1_example_test-TEST 1279 xn--bc123-3ve.example,Hns2_example_test-TEST 1280 xn--bc321-3ve.example,Hns1_example_test-TEST 1281 xn--bc321-3ve.example,Hns2_example_test-TEST 1283 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1285 The "domainNameServersAddresses" CSV File Definition defines the 1286 fields and CSV file references used for supporting the domain host 1287 attributes model. 1289 The following "csvDomain" fields, defined for the "domain" CSV File 1290 Definition (Section 5.1.2.1.1), MUST be used in the 1291 "domainNameServersAddresses" element: 1293 Domain name using the delegated host with host 1294 and isRequired="true". 1296 The following "rdeCsv" fields, defined in section Host CSV model 1297 elements (Section 5.2.2), MUST be used in the 1298 "domainNameServersAddresses" element: 1300 Host name field with type="eppcom:labelType" and 1301 isRequired="true". 1303 The following "csvHost" fields, defined in section Host CSV model 1304 elements (Section 5.2.2), MAY be used in the 1305 "domainNameServersAddresses" element: 1307 IP addresses associated with the host object with 1308 type="host:addrStringType". 1310 IP addresses version associated with the host 1311 object with type="host:ipType". "host:ipType" has the enumerated 1312 values of "v4" or "v6". 1314 Example of a "domainNameServersAddresses" 1315 element. 1317 ... 1318 1319 ... 1320 1321 1322 1323 1324 1325 1326 1327 1328 1330 domainNameServersAddresses-YYYYMMDD.csv 1331 1332 1333 1334 ... 1335 1336 ... 1338 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1339 file. The file contains the delegated hosts (name servers) for the 1340 four domain names domain1.example, domain2.example, xn-- 1341 bc123-3ve.example and xn--bc321-3ve.example. 1343 domain1.example,ns1.domain1.example,192.0.2.1,v4 1344 domain1.example,ns2.domain1.example,2001:DB8::1,v6 1345 domain2.example,ns1.example.net,, 1346 domain2.example,ns2.example.net,, 1347 xn--bc123-3ve.example,ns1.example.net,, 1348 xn--bc123-3ve.example,ns2.example.net,, 1349 xn--bc321-3ve.example,ns1.example.net,, 1350 xn--bc321-3ve.example,ns2.example.net,, 1352 5.1.2.1.6. "dnssec" CSV File Definition 1354 The "dnssec" CSV File Definition defines the fields and CSV file 1355 references used for the domain name object DNSSEC records (DS or Key 1356 Data). 1358 The following "csvDomain" field elements MUST be used in the "dnssec" 1359 element when the DS Data Interface per 1360 [RFC5910] is used: 1362 Contains the DS key tag value per [RFC5910] with 1363 type="unsignedShort" and isRequired="true". 1365 Contains the DS algorithm value per [RFC5910] 1366 with type="unsignedByte" and isRequired="true". 1368 Contains the DS digest type value per 1369 [RFC5910] with type="unsignedByte" and isRequired="true". 1371 Contains the DS digest value per [RFC5910] with 1372 type="hexBinary" and isRequired="true". 1374 The following "csvDomain" field elements MUST be used in the "dnssec" 1375 element when the Key Data Interface per 1376 [RFC5910] is used and MAY be used in the "dnssec" 1377 element when the DS Data Interface per [RFC5910] is 1378 used: 1380 Contains the flags field value per [RFC5910] with 1381 type="unsignedShort" and isRequired="true". 1383 Contains the Key protocol value per [RFC5910] 1384 with type="unsignedByte" and isRequired="true". 1386 Contains the Key algorithm value per [RFC5910] 1387 with type="unsignedByte" and isRequired="true". 1389 Contains the public key value per [RFC5910] with 1390 type="secDNS:keyType" and isRequired="true". 1392 The following "csvDomain" field elements MAY be used in the "dnssec" 1393 element: 1395 Indicates a child's preference for the 1396 number of seconds after signature generation when the parent's 1397 signature on the DS information provided by the child will expire 1398 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1400 The following "domain" fields, defined for the "domain" CSV File 1401 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1402 element: 1404 Domain name of the domain name object associated 1405 with the DNSSEC record and isRequired="true". 1407 Example of a "dnssec" element with 1408 the DS Data Interface of [RFC5910]: 1410 1411 ... 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1424 dnssec-ds-YYYYMMDD.csv 1425 1426 1427 1428 ... 1429 1430 ... 1432 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1433 contains two DS records for domain1.example. 1435 domain1.example,604800,30730,8,2,91C9B176EB////F1C46F6A55 1436 domain1.example,604800,61882,8,2,9F8FEAC94B////1272AF09F3 1438 Example of a "dnssec" element with 1439 the Key Data Interface of [RFC5910]: 1441 1442 ... 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1455 dnssec-key-YYYYMMDD.csv 1456 1457 1458 1459 ... 1460 1461 ... 1463 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1464 contains two key records for domain1.example. 1466 domain1.example,604800,257,3,8,AwEAAZD1+z////G1jqviK8c= 1467 domain1.example,604800,257,3,8,AwEAAbntWP////vwDitt940= 1469 5.1.2.1.7. "domainTransfer" CSV File Definition 1471 The "domainTransfer" CSV File Definition defines the fields and CSV 1472 file references used for the domain name object pending and completed 1473 transfer records. No additional field elements were added for use in 1474 the "domainTransfer" element. 1476 The following "rdeCsv" fields, defined in section CSV common field 1477 elements (Section 4.6.2.2), MUST be used in the "domainTransfer" 1478 element: 1480 State of the most recent transfer request with 1481 isRequired="true". 1483 Identifier of the registrar, defined in Section 5.4, 1484 of the client that requested the transfer with isRequired="true". 1486 Date and time that the transfer was requested with 1487 isRequired="true". 1489 Identifier of the registrar, defined in Section 5.4, 1490 of the client that should take or took action with 1491 isRequired="true". 1493 Date and time that the transfer action should be 1494 taken or has been taken with isRequired="true". 1496 The following "rdeCsv" fields, defined in section CSV common field 1497 elements (Section 4.6.2.2), MAY be used in the "domainTransfer" 1498 element: 1500 Expiration date if the transfer command caused or 1501 causes a change in the validity period. 1503 Identifier of the client that requested the transfer. 1505 Identifier of the client that should take or took 1506 action for transfer. 1508 The following "csvDomain" fields, defined for the "domain" CSV File 1509 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1510 element: 1512 Domain name of the domain name object involved in 1513 the transfer with isRequired="true". 1515 Example of a "domainTransfer" 1516 element. 1518 ... 1519 1520 ... 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1536 domainTransfer-YYYYMMDD.csv 1537 1538 1539 1540 ... 1541 1542 ... 1544 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1545 file contains one domain transfer record with a pending status. 1547 domain1.example,pending,registrarX,clientY, 1548 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1549 2025-04-03T22:00:00.0Z 1551 5.1.2.2. 1553 The is used to hold the deleted domain name 1554 objects in a Differential or Incremental Deposit. All the domain 1555 name object data is deleted as part of a cascade delete. The 1556 is split into separate CSV file definitions using 1557 named elements with the "name" attribute. The following 1558 section defines the supported domain name deletes CSV file 1559 definition. 1561 5.1.2.2.1. "domain" Deletes CSV File Definition 1563 The following "csvDomain" field elements MUST be used in the deletes 1564 "domain" element: 1566 Domain name field with type="eppcom:labelType" and 1567 isRequired="true". 1569 Example of a "domain" element: 1571 ... 1572 1573 ... 1574 1575 1576 1577 1578 1579 1581 domain-delete-YYYYMMDD.csv 1582 1583 1584 1585 ... 1586 1587 ... 1589 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1590 file contains two domain name records. 1592 domain1.example 1593 domain2.example 1595 5.2. Host Object 1597 The host object is based on the EPP host name mapping in [RFC5732]. 1598 The host object supports both the XML Model and the CSV Model, 1599 defined in Models (Section 2) section. The elements used for both 1600 models are defined in the following sections. Both the 1601 and elements contain one or more 1602 elements with a set of named CSV file definitions using 1603 the "name" attribute. 1605 5.2.1. XML Model 1607 There are two elements used in the data escrow of the host objects 1608 for the XML model including the , under the 1609 element, and the element, under 1610 the element. 1612 A element substitutes for the 1613 abstract element to define a concrete definition of a host. The 1614 element can be replaced by other host 1615 definitions using the XML schema substitution groups feature. 1617 5.2.1.1. element 1619 The RDE host object is based on the EPP host response for an 1620 authorized client (Section 3.1.2. of [RFC5732]). 1622 The OPTIONAL element contains the following child elements: 1624 o A element that contains the fully-qualified name of the 1625 host object. 1627 o A element that contains the repository object identifier 1628 assigned to the host object when the object was created. 1630 o One or more elements that describe the status of the host 1631 object. 1633 o Zero or more elements that contain the IP addresses 1634 associated with the host object. 1636 o A element that contains the identifier of the sponsoring 1637 registrar. 1639 o An OPTIONAL element that contains the identifier of the 1640 registrar that created the host object. An OPTIONAL client 1641 attribute is used to specify the client that performed the 1642 operation. 1644 o An OPTIONAL element that contains the date and time of 1645 host-object creation. 1647 o An OPTIONAL element that contains the identifier of the 1648 registrar that last updated the host object. This element MUST 1649 NOT be present if the host object has never been modified. An 1650 OPTIONAL client attribute is used to specify the client that 1651 performed the operation. 1653 o An OPTIONAL element that contains the date and time of 1654 the most recent host-object modification. This element MUST NOT 1655 be present if the host object has never been modified. 1657 o An OPTIONAL element that contains the date and time of 1658 the most recent host object successful transfer. This element 1659 MUST NOT be present if the domain name object has never been 1660 transfered. 1662 Example of object: 1664 ... 1665 1666 ns1.example1.example 1667 Hns1_example_test-TEST 1668 1669 1670 192.0.2.2 1671 192.0.2.29 1672 2001:DB8:1::1 1673 RegistrarX 1674 RegistrarX 1675 1999-05-08T12:10:00.0Z 1676 RegistrarX 1677 2009-10-03T09:34:00.0Z 1678 1679 ... 1681 5.2.1.2. object 1683 The element contains the fully-qualified domain name 1684 of a host that was deleted. The element also 1685 supports host removal based on roid to support SRS systems in which 1686 different hosts with the same fully-qualified domain name are active 1687 at the same time. 1689 Example of object: 1691 ... 1692 1693 ... 1694 1695 ns1.example.example 1696 1697 ... 1698 1699 ... 1701 5.2.2. CSV Model 1703 For the CSV Model of the host object, the child 1704 element of the element is used to hold the new or 1705 updated host objects for the deposit. The child 1706 element of the element is used to hold the deleted or 1707 purged host objects for the deposit. 1709 Differential and Incremental Deposits are based on changes to the 1710 host objects. The updated host object data under the 1711 element is a cascade replace down all of the host 1712 CSV files starting with the parent "host" CSV File Definition 1713 (Section 5.2.2.1.1). The child CSV file definitions include a 1714 field. All the child CSV file 1715 definition data for the host objects in the parent "host" CSV File 1716 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1717 using the data in the child CSV files. The deleted host object data 1718 under the element is a cascade delete starting from 1719 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1721 5.2.2.1. 1723 The is used to hold the new or updated host object 1724 information for the deposit. The is split into 1725 separate CSV file definitions using named elements with 1726 the "name" attribute. The following sections include the supported 1727 host CSV file definitions. 1729 5.2.2.1.1. "host" CSV File Definition 1731 The "host" CSV File Definition defines the fields and CSV file 1732 references used for the host object records. 1734 The following "csvHost" field elements MUST be used in the "host" 1735 element: 1737 Host name field with type="eppcom:labelType" and 1738 isRequired="true". 1740 The following "rdeCsv" fields, defined in section CSV common field 1741 elements (Section 4.6.2.2), MUST be used in the "host" 1742 element: 1744 Repository Object IDentifier (ROID) assigned to the 1745 host object with isRequired="true". 1747 The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the 1748 "host" element: 1750 or A choice of: 1752 Identifier of the sponsoring client with 1753 isRequired="true". 1755 Contains the Globally Unique Registrar 1756 Identifier (GURID) assigned by ICANN with 1757 type="positiveInteger" and isRequired="true". 1759 Identifier of the registrar, defined in Section 5.4, 1760 of the client that created the host object. 1762 Identifier of the client that created the host 1763 object. 1765 Identifier of the registrar, defined in Section 5.4, 1766 of the client that last updated the host object. 1768 Identifier of the client that last updated the host 1769 object. 1771 Date and time that the host object was created. 1773 Date and time that the host object was last 1774 updated. This field MUST NOT be set if the domain name object has 1775 never been modified. 1777 Date and time that the host object was last 1778 transferred. This field MUST NOT be set if the domain name object 1779 has never been transferred. 1781 Example of a "host" element. 1783 ... 1784 1785 ... 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1802 host-YYYYMMDD.csv 1803 1804 1805 1806 ... 1807 1808 ... 1810 Example of the corresponding host-YYYYMMDD.csv file. The file 1811 contains six host records with four being internal hosts and two 1812 being external hosts. 1814 ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX, 1815 clientY,1999-05-08T12:10:00.0Z,registrarX, 1816 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1817 ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX, 1818 clientY,1999-05-08T12:10:00.0Z,registrarX, 1819 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1820 ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX, 1821 clientY,1999-05-08T12:10:00.0Z,registrarX, 1822 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1823 ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, 1824 clientY,1999-05-08T12:10:00.0Z,registrarX, 1825 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1826 ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, 1827 clientY,1999-05-08T12:10:00.0Z,registrarX, 1828 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1829 ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, 1830 clientY,1999-05-08T12:10:00.0Z,registrarX, 1831 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1833 5.2.2.1.2. "hostStatuses" CSV File Definition 1835 The "hostStatuses" CSV File Definition defines the fields and CSV 1836 file references used for the host object statuses. 1838 The following "csvHost" fields, defined for the "host" CSV File 1839 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1840 element: 1842 The status of the host with 1843 type="host:statusValueType" and isRequired="true". 1845 The following "rdeCsv" fields, defined in section CSV common field 1846 elements (Section 4.6.2.2), MUST be used in the "hostStatuses" 1847 element: 1849 Host object Registry Object IDentifier (ROID) 1850 assigned to the host object with isRequired="true". 1852 The following "rdeCsv" fields, defined in section CSV common field 1853 elements (Section 4.6.2.2), MAY be used in the "hostStatuses" 1854 element: 1856 Host object status description which is 1857 free form text describing the rationale for the status. 1859 Language of the field. 1861 Example of a "hostStatuses" element. 1863 ... 1864 1865 ... 1866 1867 1868 1869 1870 1871 1872 1873 1874 1876 hostStatuses-YYYYMMDD.csv 1877 1878 1879 1880 ... 1881 1882 ... 1884 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1885 file contains the statuses for the six host names 1886 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example, 1887 ns2.domain2.example, ns1.example.net and ns2.example.net. 1889 Hns1_domain1_test-TEST,ok,, 1890 Hns2_domain1_test-TEST,ok,, 1891 Hns1_domain2_test-TEST,ok,, 1892 Hns2_domain2_test-TEST,ok,, 1893 Hns1_example_test-TEST,ok,, 1894 Hns2_example_test-TEST,ok,, 1896 5.2.2.1.3. "hostAddresses" CSV File Definition 1898 The "hostAddresses" CSV File Definition defines the fields and CSV 1899 file references used for the host object IP addresses. 1901 The following "csvHost" field elements MUST be used in the 1902 "hostAddresses" element: 1904 IP addresses associated with the host object with 1905 type="host:addrStringType". The attribute "isRequired" MUST equal 1906 "true". 1908 IP addresses version associated with the host 1909 object with type="host:ipType". "host:ipType" has the enumerated 1910 values of "v4" or "v6". The attribute "isRequired" MUST equal 1911 "true". 1913 The following "rdeCsv" fields, defined in section CSV common field 1914 elements (Section 4.6.2.2), MUST be used in the "hostAddresses" 1915 element: 1917 Host object Registry Object IDentifier (ROID) 1918 assigned to the host object with isRequired="true". 1920 Example of a "hostAddresses" element. 1922 ... 1923 1924 ... 1925 1926 1927 1928 1929 1930 1931 1932 1934 hostAddresses-YYYYMMDD.csv 1935 1936 1937 1938 ... 1939 1940 ... 1942 Example of the corresponding hostAddresses-YYYYMMDD.csv file. The 1943 file contains the IP addresses for the host names 1944 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and 1945 ns2.domain2.example. 1947 Hns1_domain1_test-TEST,192.0.2.1,v4 1948 Hns2_domain1_test-TEST,2001:DB8::1,v6 1949 Hns1_domain2_test-TEST,192.0.2.2,v4 1950 Hns2_domain2_test-TEST,2001:DB8::2,v6 1952 5.2.2.2. 1954 The is used to hold the deleted host objects in a 1955 Differential or Incremental Deposit. All the host object data is 1956 deleted as part of a cascade delete. The is split 1957 into separate CSV file definitions using named elements 1958 with the "name" attribute. The following section defines the 1959 supported host deletes CSV file definition. 1961 5.2.2.2.1. "host" Deletes CSV File Definition 1963 The following "rdeCsv" fields, defined in section CSV common field 1964 elements (Section 4.6.2.2), MUST be used in the "host" 1965 element: 1967 Repository Object IDentifier (ROID) assigned to the 1968 host object with isRequired="true". 1970 Example of a "host" element. 1972 ... 1973 1974 ... 1975 1976 1977 1978 1979 1980 1982 host-delete-YYYYMMDD.csv 1983 1984 1985 1986 ... 1987 1988 ... 1990 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1991 host records. 1993 Hns1_domain1_test-TEST 1994 Hns2_domain1_test-TEST 1995 Hns1_domain2_test-TEST 1996 Hns2_domain2_test-TEST 1998 5.3. Contact Object 2000 The contact object is based on the EPP contact name mapping in 2001 [RFC5733]. The contact object supports both the XML Model and the 2002 CSV Model, defined in Models (Section 2) section. The elements used 2003 for both models are defined in the following sections. 2005 5.3.1. XML Model 2007 There are two elements used in the data escrow of the contact objects 2008 for the XML model including the , under the 2009 element, and the element, 2010 under the element. 2012 A element substitutes for the abstract 2013 element to define a concrete definition of a contact. The 2014 element can be replaced by other contact 2015 definitions using the XML schema substitution groups feature. 2017 5.3.1.1. object 2019 The contact object is based on the EPP contact response for an 2020 authorized client (Section 3.1.2. of [RFC5733]) with some additions 2021 including the data from an EPP Query Response, see 2022 Section 3.1.3. of [RFC5733]. 2024 The OPTIONAL element contains the following child elements: 2026 o A element that contains the server-unique identifier of the 2027 contact object 2029 o A element that contains the Repository Object IDentifier 2030 assigned to the contact object when the object was created. 2032 o One or more elements that describe the status of the 2033 contact object. 2035 o One or two elements that contain postal-address 2036 information. Two elements are provided so that address 2037 information can be provided in both internationalized and 2038 localized forms; a "type" attribute is used to identify the two 2039 forms. If an internationalized form (type="int") is provided, 2040 element content MUST be represented in a subset of UTF-8 that can 2041 be represented in the 7-bit US-ASCII character set. If a 2042 localized form (type="loc") is provided, element content MAY be 2043 represented in unrestricted UTF-8. The element 2044 contains the following child elements: 2046 * A element that contains the name of the individual or 2047 role represented by the contact. 2049 * An OPTIONAL element that contains the name of the 2050 organization with which the contact is affiliated. 2052 * An element that contains address information associated 2053 with the contact. An element contains the following 2054 child elements: 2056 + One, two, or three OPTIONAL elements that contain 2057 the contact's street address. 2059 + A element that contains the contact's city. 2061 + An OPTIONAL element that contains the contact's state 2062 or province. 2064 + An OPTIONAL element that contains the contact's postal 2065 code. 2067 + A element that contains the contact's two-letter 2068 country code. 2070 o An OPTIONAL element that contains the contact's voice 2071 telephone number. 2073 o An OPTIONAL element that contains the contact's facsimile 2074 telephone number. 2076 o An element that contains the contact's email address. 2078 o A element that contains the identifier of the sponsoring 2079 registrar. 2081 o An OPTIONAL element that contains the identifier of the 2082 registrar that created the contact object. An OPTIONAL client 2083 attribute is used to specify the client that performed the 2084 operation. 2086 o An OPTIONAL element that contains the date and time of 2087 contact-object creation. 2089 o An OPTIONAL element that contains the identifier of the 2090 registrar that last updated the contact object. This element MUST 2091 NOT be present if the contact has never been modified. An 2092 OPTIONAL client attribute is used to specify the client that 2093 performed the operation. 2095 o An OPTIONAL element that contains the date and time of 2096 the most recent contact-object modification. This element MUST 2097 NOT be present if the contact object has never been modified. 2099 o An OPTIONAL element that contains the date and time of 2100 the most recent contact object successful transfer. This element 2101 MUST NOT be present if the contact object has never been 2102 transferred. 2104 o An OPTIONAL element that contains the following child 2105 elements related to the last transfer request of the contact 2106 object: 2108 * A element that contains the state of the most recent 2109 transfer request. 2111 * A element that contains the identifier of the registrar 2112 that requested the domain name object transfer. An OPTIONAL 2113 client attribute is used to specify the client that performed 2114 the operation. 2116 * An element that contains the identifier of the registrar 2117 that should act upon a PENDING transfer request. For all other 2118 status types, the value identifies the registrar that took the 2119 indicated action. An OPTIONAL client attribute is used to 2120 specify the client that performed the operation. 2122 * A element that contains the date and time that the 2123 transfer was requested. 2125 * An element that contains the date and time of a 2126 required or completed response. For a PENDING request, the 2127 value identifies the date and time by which a response is 2128 required before an automated response action will be taken by 2129 the registry. For all other status types, the value identifies 2130 the date and time when the request was completed. 2132 o An OPTIONAL element that identifies elements that 2133 requiring exceptional server-operator handling to allow or 2134 restrict disclosure to third parties. See Section 2.9 of 2135 [RFC5733] for a description of the child elements contained within 2136 the element. 2138 Example object: 2140 ... 2141 2142 sh8013 2143 Csh8013-TEST 2144 2145 2146 2147 John Doe 2148 Example Inc. 2149 2150 123 Example Dr. 2151 Suite 100 2152 Dulles 2153 VA 2154 20166-6503 2155 US 2156 2157 2158 +1.7035555555 2159 +1.7035555556 2160 jdoe@example.example 2161 RegistrarX 2162 RegistrarX 2163 2009-09-13T08:01:00.0Z 2164 RegistrarX 2165 2009-11-26T09:10:00.0Z 2166 2009-12-03T09:05:00.0Z 2167 2168 pending 2169 clientW 2170 2011-03-08T19:38:00.0Z 2171 RegistrarX 2172 2011-03-13T23:59:59.0Z 2173 2174 2175 2176 2177 2178 2179 ... 2181 5.3.1.2. object 2183 The element contains the id of a contact that was 2184 deleted. 2186 Example of object: 2188 ... 2189 2190 ... 2191 2192 sh8013-TEST 2193 co8013-TEST 2194 2195 ... 2196 2197 ... 2199 5.3.2. CSV Model 2201 For the CSV Model of the contact object, the 2202 child element of the element is used to hold the new 2203 or updated contacts objects for the deposit. The 2204 child element of the element is 2205 used to hold the deleted or purged contact objects for the deposit. 2206 Both the and elements 2207 contain one or more elements with a set of named CSV 2208 file definitions using the "name" attribute. 2210 Differential and Incremental Deposits are based on changes to the 2211 contact objects. The updated contact object data under the 2212 element is a cascade replace down all of the 2213 contact CSV files starting with the parent "contact" CSV File 2214 Definition (Section 5.3.2.1.1). The child CSV file definitions 2215 include a field. All the child CSV 2216 file definition data for the contact objects in the parent "contact" 2217 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2218 then set using the data in the child CSV files. The deleted contact 2219 object data under the element is a cascade 2220 delete starting from the "contact" Deletes CSV File Definition 2221 (Section 5.3.2.2.1). 2223 5.3.2.1. 2225 The is used to hold the new or updated contact 2226 object information for the deposit. The is 2227 split into separate CSV file definitions using named 2228 elements with the "name" attribute. The following sections include 2229 the supported contact CSV file definitions. 2231 5.3.2.1.1. "contact" CSV File Definition 2233 The "contact" CSV File Definition defines the fields and CSV file 2234 references used for the contact object records. 2236 The following "csvContact" field elements MUST be used in the 2237 "contact" element: 2239 Contains the server-unique contact identifier with 2240 type="eppcom:clIDType" and isRequired="true". 2242 Contains the contact's email address with 2243 type="eppcom:minTokenType" and isRequired="true". 2245 The following field elements MAY be used in the "contact" 2246 element: 2248 Contains the contact's voice telephone number 2249 with type="contact:e164StringType". 2251 Contains the contact's voice telephone number 2252 extension with type="token". 2254 Contains the contact's facsimile telephone number 2255 with type="contact:e164StringType". 2257 Contains the contact's facsimile telephone 2258 number extension with type="token". 2260 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 2261 "contact" element: 2263 The Registry Object IDentifier (ROID) for the contact 2264 object with isRequired="true". 2266 or A choice of: 2268 Identifier of the sponsoring client with 2269 isRequired="true". 2271 Contains the Globally Unique Registrar 2272 Identifier (GURID) assigned by ICANN with 2273 type="positiveInteger" and isRequired="true". 2275 The following "rdeCsv" fields, defined in section CSV common field 2276 elements (Section 4.6.2.2), MAY be used in the "contact" 2277 element: 2279 Identifier of the registrar, defined in Section 5.4, 2280 of the client that created the contact object. 2282 Identifier of the client that created the contact 2283 object. 2285 Identifier of the registrar, defined in Section 5.4, 2286 of the client that last updated the contact object. 2288 Identifier of the client that last updated the 2289 contact object. 2291 Created date and time of the contact object. 2293 Date and time of the last update to the contact 2294 object. This field MUST NOT be set if the domain name object has 2295 never been modified. 2297 Date and time of the last transfer for the contact 2298 object. This field MUST NOT be set if the domain name object has 2299 never been transferred. 2301 Example of a "contact" element. 2303 ... 2304 2305 ... 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2326 contact-YYYYMMDD.csv 2327 2328 2329 2330 ... 2331 2332 ... 2334 Example of the contact-YYYYMMDD.csv file. The file contains nine 2335 object contact records. 2337 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2338 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2339 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2340 2009-11-26T09:10:00.0Z 2341 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2342 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2343 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2344 2009-11-26T09:10:00.0Z 2345 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2346 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2347 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2348 2009-11-26T09:10:00.0Z 2349 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2350 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2351 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2352 2009-11-26T09:10:00.0Z 2353 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2354 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2355 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2356 2009-11-26T09:10:00.0Z 2357 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2358 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2359 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2360 2009-11-26T09:10:00.0Z 2361 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2362 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2363 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2364 2009-11-26T09:10:00.0Z 2365 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2366 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2367 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2368 2009-11-26T09:10:00.0Z 2369 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2370 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2371 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2372 2009-11-26T09:10:00.0Z 2374 5.3.2.1.2. "contactStatuses" CSV File Definition 2376 The "contactStatuses" CSV File Definition defines the fields and CSV 2377 file references used for the contact object statuses. 2379 The following "csvContact" field elements, defined for the "contact" 2380 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2381 "contactStatuses" element: 2383 Server-unique contact identifier of status with 2384 isRequired="true" and parent="true". 2386 The status of the contact with 2387 type="contact:statusValueType" and isRequired="true". 2389 The following "rdeCsv" fields, defined in section CSV common field 2390 elements (Section 4.6.2.2), MAY be used in the "contactStatuses" 2391 element: 2393 The contact object status description 2394 which is free form text describing the rationale for the status. 2396 Language of the field. 2398 Example of a "contactStatuses" 2399 element. 2401 ... 2402 2403 ... 2404 2405 2406 2407 2408 2409 2410 2411 2412 2414 contactStatuses-YYYYMMDD.csv 2415 2416 2417 2418 ... 2419 2420 ... 2422 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2423 file contains the statuses for the nine contact identifiers. 2425 domain1admin,ok,, 2426 domain1tech,ok,, 2427 domain1billing,ok,, 2428 domain2admin,ok,, 2429 domain2tech,ok,, 2430 domain2billing,ok,, 2431 xnabc123admin,ok,, 2432 xnabc123tech,ok,, 2433 xnabc123billing,ok,, 2435 5.3.2.1.3. "contactPostal" CSV File Definition 2437 The "contactPostal" CSV File Definition defines the fields and CSV 2438 file references used for the contact postal info object records. 2440 The following "csvContact" field elements MUST be used in the 2441 "contactPostal" element: 2443 Contains the form of the postal-address 2444 information with type="contact:postalLineType" and 2445 isRequired="true". This field specifies the form ("int" or 2446 "loc"), as defined in Section 4.6.3, of the , 2447 , , , 2448 , , fields. 2450 Contains the contact's name of the individual or 2451 role represented by the contact with type="contact:postalLineType" 2452 and isRequired="true". An OPTIONAL "isLoc" attribute is used to 2453 indicate the localized or internationalized form as defined in 2454 Section 4.6.3. 2456 Contains the contact's street address line with 2457 type="contact:fPostalLineType". An index attribute is required to 2458 indicate which street address line the field represents with index 2459 "0" for the first line and incrementing for each line up to index 2460 "2" for the third line. An OPTIONAL "isLoc" attribute is used to 2461 indicate the localized or internationalized form as defined in 2462 Section 4.6.3. 2464 Contains the contact's city with 2465 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2466 "isLoc" attribute is used to indicate the localized or 2467 internationalized form as defined in Section 4.6.3. 2469 Contains the contact's country code with 2470 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2471 attribute is used to indicate the localized or internationalized 2472 form as defined in Section 4.6.3. 2474 The following "csvContact" field elements MAY be used in the 2475 "contactPostal" element: 2477 Contains the name of the organization with which 2478 the contact is affiliated with type="contact:optPostalLineType". 2479 An OPTIONAL "isLoc" attribute is used to indicate the localized or 2480 internationalized form as defined in Section 4.6.3. 2482 Contains the contact's state or province with 2483 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2484 is used to indicate the localized or internationalized form as 2485 defined in Section 4.6.3. 2487 Contains the contact's postal code with 2488 type="contact:pcType". An OPTIONAL "isLoc" attribute is used to 2489 indicate the localized or internationalized form as defined in 2490 Section 4.6.3. 2492 The following "csvContact" fields, defined for the "contact" CSV File 2493 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2494 element: 2496 Server-unique contact identifier for the contact 2497 object with isRequired="true" and parent="true". 2499 Example of a "contactPostal" 2500 element. 2502 ... 2503 2504 ... 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2522 contactPostal-YYYYMMDD.csv 2523 2524 2525 2526 ... 2527 2528 ... 2530 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2531 nine contact postal records. 2533 domain1admin,int,"John Doe","Example Inc.", 2534 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2535 domain1tech,int,"John Doe","Example Inc.", 2536 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2537 domain1billing,int,"John Doe","Example Inc.", 2538 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2539 domain2admin,int,"John Doe","Example Inc.", 2540 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2541 domain2tech,int,"John Doe","Example Inc.", 2542 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2543 domain2billing,int,"John Doe","Example Inc.", 2544 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2545 xnabc123admin,int,"John Doe","Example Inc.", 2546 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2547 xnabc123tech,int,"John Doe","Example Inc.", 2548 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2549 xnabc123billing,int,"John Doe","Example Inc.", 2550 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2552 5.3.2.1.4. "contactTransfer" CSV File Definition 2554 The "contactTransfer" CSV File Definition defines the fields and CSV 2555 file references used for the contact object pending and completed 2556 transfer records. No additional field elements were added for use in 2557 the "contactTransfer" element. The 2558 following "rdeCsv" fields, defined in section CSV common field 2559 elements (Section 4.6.2.2), MUST be used in the "contactTransfer" 2560 element: 2562 State of the most recent transfer request with 2563 isRequired="true". 2565 Identifier of the registrar, defined in Section 5.4, 2566 of the client that requested the transfer with isRequired="true". 2568 Date and time that the transfer was requested with 2569 isRequired="true". 2571 Identifier of the registrar, defined in Section 5.4, 2572 of the client that should take or took action with 2573 isRequired="true". 2575 Date and time that the transfer action should be 2576 taken or has been taken with isRequired="true". 2578 The following "rdeCsv" fields, defined in section CSV common field 2579 elements (Section 4.6.2.2), MAY be used in the "contactTransfer" 2580 element: 2582 Identifier of the client that requested the transfer. 2584 Identifier of the client that should take or took 2585 action for transfer. 2587 The following "csvContact" fields, defined for the "contact" CSV File 2588 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2589 element: 2591 Server-unique contact identifier for the contact 2592 object with isRequired="true". 2594 Example of a "contactTransfer" 2595 element. 2597 ... 2598 2599 ... 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2614 contactTransfer-YYYYMMDD.csv 2615 2616 2617 2618 ... 2619 2620 ... 2622 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2623 one contact transfer record in pending status. 2625 xnabc123admin,clientApproved,registrarX,clientX, 2626 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2628 5.3.2.1.5. "contactDisclose" CSV File Definition 2630 The "contactDisclose" CSV File Definition defines the fields and CSV 2631 file references used for the contact disclose object records. 2633 The following "csvContact" field elements MAY be used in the 2634 "contactDisclose" element: 2636 Contains flag with a value of "true" or 2637 "1" (one) notes the preference to allow disclosure of the 2638 specified elements as an exception to the stated data-collection 2639 policy. A value of "false" or "0" (zero) notes a client 2640 preference to not allow disclosure of the specified elements as an 2641 exception to the stated data-collection policy with 2642 type="boolean". The additional fields define specific exceptional 2643 disclosure preferences based on the 2644 field. 2646 Exceptional disclosure preference flag 2647 for the localized form of the contact name with type="boolean". 2649 Exceptional disclosure preference flag 2650 for the internationalized form of the contact name with 2651 type="boolean". 2653 Exceptional disclosure preference flag 2654 for the localized form of the contact organization with 2655 type="boolean". 2657 Exceptional disclosure preference flag 2658 for the internationalized form of the contact organization with 2659 type="boolean". 2661 Exceptional disclosure preference flag 2662 for the localized form of the contact address with type="boolean". 2664 Exceptional disclosure preference flag 2665 for the internationalized form of the contact address with 2666 type="boolean". 2668 Exceptional disclosure preference flag 2669 of the contact voice telephone number with type="boolean". 2671 Exceptional disclosure preference flag of 2672 the contact facsimile telephone number with type="boolean". 2674 Exceptional disclosure preference flag 2675 of the contact email address with type="boolean". 2677 The following "csvContact" fields, defined for the "contact" CSV File 2678 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2679 element: 2681 Server-unique contact identifier for the contact 2682 object with isRequired="true". 2684 Example of a "contactDisclose" 2685 element. 2687 ... 2688 2689 ... 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2707 contactDisclose-YYYYMMDD.csv 2708 2709 2710 2711 ... 2712 2713 ... 2715 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2716 one disclosure records, disabling disclosure of voice, fax, and 2717 email. 2719 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2721 5.3.2.2. 2723 The is used to hold the deleted contact objects 2724 in a Differential or Incremental Deposit. All the contact object 2725 data is deleted as part of a cascade delete. The 2726 is split into separate CSV file definitions 2727 using named elements with the "name" attribute. The 2728 following section defines the supported contact deletes CSV file 2729 definition. 2731 5.3.2.2.1. "contact" Deletes CSV File Definition 2733 The following "csvContact" field elements MUST be used in the deletes 2734 "contact" element: 2736 Contains the server-unique contact identifier with 2737 type="eppcom:clIDType" and isRequired="true". 2739 Example of a "contact" element. 2741 ... 2742 2743 ... 2744 2745 2746 2747 2748 2749 2751 contact-delete-YYYYMMDD.csv 2752 2753 2754 2755 ... 2756 2757 ... 2759 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2760 six contact records. 2762 domain1admin 2763 domain1tech 2764 domain1billing 2765 domain2admin 2766 domain2tech 2767 domain2billing 2769 5.4. Registrar Object 2771 The registrar object represents the sponsoring client for other 2772 objects, and is typically referred to as the sponsoring registrar. 2773 The registrar object supports both the XML Model and the CSV Model, 2774 defined in Section 2. The elements used for both models are defined 2775 in the following sections. 2777 5.4.1. XML Model 2779 There are two elements used in the data escrow of the registrar 2780 objects for the XML model including the , 2781 under the element, and the 2782 element, under the element. 2784 A element substitutes for the 2785 abstract element to define a 2786 concrete definition of a registrar. The 2787 element can be replaced by other 2788 domain definitions using the XML schema substitution groups feature. 2790 5.4.1.1. element 2792 The element contains the following child elements: 2794 o An element that contains the Registry-unique identifier of 2795 the registrar object. This has a superordinate relationship 2796 to a subordinate , or of domain, contact and 2797 host objects. 2799 o An element that contains the name of the registrar. 2801 o An OPTIONAL element that contains the Globally Unique 2802 Registrar Identifier (GURID) assigned by ICANN. 2804 o An OPTIONAL element that contains the operational status 2805 of the registrar. Possible values are: ok, readonly and 2806 terminated. 2808 o One or two OPTIONAL elements that contain postal- 2809 address information. Two elements are provided so that address 2810 information can be provided in both internationalized and 2811 localized forms; a "type" attribute is used to identify the two 2812 forms. If an internationalized form (type="int") is provided, 2813 element content MUST be represented in a subset of UTF-8 that can 2814 be represented in the 7-bit US-ASCII character set. If a 2815 localized form (type="loc") is provided, element content MAY be 2816 represented in unrestricted UTF-8. The element 2817 contains the following child elements: 2819 * A element that contains address information associated 2820 with the registrar. The element contains the following 2821 child elements: 2823 + One, two, or three OPTIONAL elements that contain 2824 the registrar's street address. 2826 + A element that contains the registrar's city. 2828 + An OPTIONAL element that contains the registrar's state 2829 or province. 2831 + An OPTIONAL element that contains the registrar's 2832 postal code. 2834 + A element that contains the registrar's country code. 2836 o An OPTIONAL element that contains the registrar's voice 2837 telephone number. 2839 o An OPTIONAL element that contains the registrar's facsimile 2840 telephone number. 2842 o An OPTIONAL element that contains the registrar's email 2843 address. 2845 o An OPTIONAL element that contains the registrar's URL. 2847 o An OPTIONAL elements that contains whois information. 2848 The element contains the following child elements: 2850 * An OPTIONAL element that contains the name of the 2851 registrar WHOIS server listening on TCP port 43 as specified in 2852 [RFC3912]. 2854 * An OPTIONAL element that contains the name of the 2855 registrar WHOIS server listening on TCP port 80/443. 2857 o An OPTIONAL element that contains the date and time of 2858 registrar-object creation. 2860 o An OPTIONAL element that contains the date and time of 2861 the most recent registrar-object modification. This element MUST 2862 NOT be present if the registrar-object has never been modified. 2864 Example of a object: 2866 ... 2867 2868 RegistrarX 2869 Registrar X 2870 8 2871 ok 2872 2873 2874 123 Example Dr. 2875 Suite 100 2876 Dulles 2877 VA 2878 20166-6503 2879 US 2880 2881 2882 +1.7035555555 2883 +1.7035555556 2884 jdoe@example.example 2885 http://www.example.example 2886 2887 whois.example.example 2888 http://whois.example.example 2889 2890 2005-04-23T11:49:00.0Z 2891 2009-02-17T17:51:00.0Z 2892 2893 ... 2895 5.4.1.2. object 2897 The element contains the id of a registrar that 2898 was deleted. 2900 Example of object: 2902 ... 2903 2904 ... 2905 2906 agnt0001-TEST 2907 2908 ... 2909 2910 ... 2912 5.4.2. CSV Model 2914 For the CSV Model of the registrar object, the 2915 child element of the element 2916 is used to hold the new or updated registrar objects for the deposit. 2917 The child element of the element 2918 is used to hold the deleted or purged registrar objects for the 2919 deposit. Both the and 2920 elements contain one or more elements with a set of 2921 named CSV file definitions using the "name" attribute. 2923 Differential and Incremental Deposits are based on changes to the 2924 registrar objects. The updated registrar object data under the 2925 element is a cascade replace down all of the 2926 registrar CSV files starting with the parent "registrar" CSV File 2927 Definition (Section 5.4.2.1.1). The child CSV file definitions 2928 include a field. All the child CSV 2929 file definition data for the registrar objects in the parent 2930 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2931 deleted and then set using the data in the child CSV files. The 2932 deleted registrar object data under the 2933 element is a cascade delete starting from the "registrar" Deletes CSV 2934 File Definition (Section 5.4.2.2.1). 2936 5.4.2.1. 2938 The is used to hold the new or updated 2939 registrar object information for the deposit. The 2940 is split into separate CSV file definitions 2941 using named elements with the "name" attribute. The 2942 following sections include the supported contact CSV file 2943 definitions. 2945 5.4.2.1.1. "registrar" CSV File Definition 2947 The "registrar" CSV File Definition defines the fields and CSV file 2948 references used for the registrar object records. 2950 The following "csvRegistrar" field elements MUST be used in the 2951 "registrar" element: 2953 or A choice of: 2955 Contains the server-unique registrar 2956 identifier with type="eppcom:clIDType" and isRequired="true". 2958 Contains the Globally Unique Registrar 2959 Identifier (GURID) assigned by ICANN with 2960 type="positiveInteger" and isRequired="true". 2962 Contains the name of the registrar with 2963 type="normalizedString" and isRequired="true". 2965 The following field elements MAY be used in the "registrar" 2966 element: 2968 Contains the status of the registrar with 2969 type="csvRegistrar:statusValueType". 2971 Contains the ID assigned by ICANN with 2972 type="positiveInteger". This field is included in this section in 2973 addition to the section above to support optionally providing the 2974 field when the field is 2975 used. 2977 Contains the Whois URL of the registrar 2978 with type="anyURI". 2980 The following "rdeCsv" fields, defined in section CSV common field 2981 elements (Section 4.6.2.2), MAY be used in the "registrar" 2982 element: 2984 Created date and time of the registrar object. 2986 Date and time of the last update to the registrar 2987 object. This field MUST NOT be set if the domain name object has 2988 never been modified. 2990 URL for the registrar web home page. 2992 The following "csvContact" fields, defined in section Contact Object 2993 (Section 5.3), MAY be used in the "registrar" 2994 element: 2996 Registrar street address line with an "index" 2997 attribute that represents the order of the street address line 2998 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2999 indicate the localized or internationalized form, as defined in 3000 Section 4.6.3. 3002 Registrar city with an OPTIONAL "isLoc" attribute 3003 that is used to indicate the localized or internationalized form, 3004 as defined in Section 4.6.3. 3006 Registrar country code with an OPTIONAL "isLoc" 3007 attribute that is used to indicate the localized or 3008 internationalized form, as defined in Section 4.6.3. 3010 Registrar email address. The attribute 3011 "isRequired" MUST equal "false". 3013 Registrar state or province with an OPTIONAL 3014 "isLoc" attribute that is used to indicate the localized or 3015 internationalized form, as defined in Section 4.6.3. 3017 Registrar postal code with an OPTIONAL "isLoc" 3018 attribute that is used to indicate the localized or 3019 internationalized form, as defined in Section 4.6.3. 3021 Registrar voice telephone number. 3023 Registrar voice telephone number extension. 3025 Registrar facsimile telephone number. 3027 Registrar facsimile telephone number extension. 3029 Example of a "registrar" 3030 element. 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 3059 3061 registrar-YYYYMMDD.csv 3062 3063 3064 3065 ... 3066 3067 ... 3069 Example of the registrar-YYYYMMDD.csv file. The file contains one 3070 registrar record. 3072 registrarX,"Example Inc.",8,ok,"123 Example Dr.", 3073 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3074 +1.7035555556,,jdoe@example.example,http://www.example.example, 3075 http://whois.example.example,2005-04-23T11:49:00.0Z, 3076 2009-02-17T17:51:00.0Z 3078 5.4.2.2. 3080 The is used to hold the deleted registrar 3081 objects in a Differential or Incremental Deposit. All the registrar 3082 object data is deleted as part of a cascade delete. The 3083 is split into separate CSV file definitions 3084 using named elements with the "name" attribute. The 3085 following section defines the supported registrar deletes CSV file 3086 definition. 3088 5.4.2.2.1. "registrar" Deletes CSV File Definition 3090 The following "csvRegistrar" field elements MUST be used in the 3091 deletes "registrar" element: 3093 or A choice of: 3095 Contains the server-unique registrar 3096 identifier with type="eppcom:clIDType" and isRequired="true". 3098 Contains the Globally Unique Registrar 3099 Identifier (GURID) assigned by ICANN with 3100 type="positiveInteger". The attribute "isRequired" MUST equal 3101 "true". 3103 Example of a "registrar" element. 3105 ... 3106 3107 ... 3108 3109 3110 3111 3112 3113 3115 registrar-delete-YYYYMMDD.csv 3116 3117 3118 3119 ... 3120 3121 ... 3123 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 3124 one registrar record. 3126 registrarZ 3128 5.5. IDN Table Reference Object 3130 The Internationalized Domain Names (IDN) table reference object is a 3131 pseudo-object that is used to provide a short reference to the IDN 3132 Table and Policy used in IDN registrations. The IDN reference object 3133 supports both the XML and the CSV Model, defined in the Models 3134 (Section 2) section. The elements used for both models are defined 3135 in the following sections. 3137 5.5.1. XML Model 3139 There is one element used in the data escrow of the IDN table 3140 reference objects for the XML model that is the , 3141 under the element. 3143 5.5.1.1. object 3145 The contains the following elements. An "id" 3146 attribute is used to specify an identifier for the IDN table. 3148 o An element that contains the URL of the IDN table that is 3149 being referenced. 3151 o A element that contains the URL of the IDN policy 3152 document. If IDN variants are generated algorithmically, the 3153 policy document MUST define the algorithm and the state of the 3154 implicit generated IDN variants. For a list of suggested states 3155 for implicit IDN variants, please see [variantTLDsReport]. 3157 Example of object: 3159 ... 3160 3161 3162 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3163 3164 3165 http://registro.br/dominio/regras.html 3166 3167 3168 ... 3170 5.5.2. CSV Model 3172 The IDN domain names, defined in Section 5.1, MAY have references to 3173 the IDN language identifier using the field 3174 element. The IDN table reference object defines the mapping of a 3175 language identifier to a language table URL. The language table URL 3176 defines the character code points that can be used for the language 3177 identifier. The elements used for the IDN table reference object is 3178 defined in this section. The child element of the 3179 element is used to hold the new or updated IDN table 3180 reference objects for the deposit. The child 3181 element of the element is used to hold the deleted or 3182 purged IDN table reference objects for the deposit. Both the 3183 and elements contain one or more 3184 elements with a set of named CSV file definitions using 3185 the "name" attribute. 3187 5.5.2.1. 3189 The is used to hold the new or updated IDN table 3190 reference object information for the deposit. The 3191 is split into separate CSV file definitions using named 3192 elements with the "name" attribute. The following sections include 3193 the supported IDN table reference CSV file definitions. 3195 5.5.2.1.1. "idnLanguage" CSV File Definition 3197 The "idnLanguage" CSV File Definition defines the fields and CSV file 3198 references used for the IDN table reference object records. 3200 The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be 3201 used in the "idnLanguage" element: 3203 The language identifier that matches the values 3204 for the field element in the "domain" CSV 3205 File Definition (Section 5.1.2.1.1) files. The attribute 3206 "isRequired" MUST equal "true". 3208 URL that defines the character code points that can be 3209 used for field in the "domain" CSV File 3210 Definition Section 5.1.2.1.1 files. The attribute "isRequired" 3211 MUST equal "true". 3213 Example of a "idnLanguage" element. 3215 ... 3216 3217 ... 3218 3219 3220 3221 3222 3223 3224 3226 idnLanguage-YYYYMMDD.csv 3227 3228 3229 3230 ... 3231 3232 ... 3234 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3235 contains two IDN language records. 3237 LANG-1, 3238 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3239 LANG-2, 3240 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3242 5.5.2.2. 3244 The is used to hold the deleted IDN table reference 3245 objects in a Differential or Incremental Deposit. The 3246 is split into separate CSV file definitions using 3247 named elements with the "name" attribute. The following 3248 section defines the supported IDN table reference deletes CSV file 3249 definition. 3251 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3253 The following "idnLanguage" field elements MUST be used in the 3254 deletes "idnLanguage" element: 3256 The language identifier that matches the values 3257 for the field element in the "domain" CSV 3258 File Definition (Section 5.1.2.1.1) files. The attribute 3259 "isRequired" MUST equal "true". 3261 Example of a "idnLanguage" element. 3263 ... 3264 3265 ... 3266 3267 3268 3269 3270 3271 3273 idnLanguage-delete-YYYYMMDD.csv 3274 3275 3276 3277 ... 3278 3279 ... 3281 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3282 contains one IDN language record. 3284 LANG-2 3286 5.6. NNDN Object 3288 An NNDN (NNDN's not domain name) can be used to store registry 3289 reserved names or (blocked, withheld or mirrored) IDN variants. 3291 Domain Name Registries may maintain domain names without their being 3292 persisted as domain objects in the registry system, for example, a 3293 list of reserved names not available for registration. The NNDN is a 3294 lightweight domain-like object that is used to escrow domain names 3295 not maintained as domain name objects. 3297 A domain name can only exist as a domain name object or an NNDN 3298 object, but not both. 3300 The NNDN object supports both the XML and the CSV Model, defined in 3301 the Models (Section 2) section. The elements used for both models 3302 are defined in the following sections. 3304 5.6.1. XML Model 3306 There are two elements used in the data escrow of the NNDN objects 3307 for the XML model including the , under the 3308 element, and the element, under the 3309 element. 3311 A element substitutes for the 3312 abstract element to define a concrete definition of an NNDN. The 3313 element can be replaced by other NNDN 3314 definitions using the XML schema substitution groups feature. 3316 5.6.1.1. object 3318 The element contains the following child elements: 3320 o An element that contains the fully-qualified qualified 3321 name of the NNDN. For IDNs the A-Label is used (see [RFC5891], 3322 Section 4.4). 3324 o An OPTIONAL element that contains the fully-qualified name 3325 of the NNDN in Unicode character set. It MUST be provided if 3326 available. 3328 o An OPTIONAL element that references the IDN 3329 Table used for the NNDN. This corresponds to the "id" attribute 3330 of the element. This element MUST be present if the 3331 NNDN is an IDN. 3333 o An OPTIONAL element is used to indicate that the 3334 NNDN is used for an IDN variant. This element contains the domain 3335 name used to generate the IDN variant. 3337 o A element that indicates the state of the NNDN: 3338 blocked, withheld or mirrored. 3340 * If an NNDN is considered undesirable for registration (i.e., 3341 unavailable for allocation to anyone), then the NNDN will be 3342 tagged as "blocked". 3344 * If an NNDN is considered a potential registration of a domain 3345 name object for a registrant, then the NNDN will be tagged as 3346 "withheld". This status is only used when the NNDN is used for 3347 an IDN variant. 3349 * If an NNDN is considered a mirrored IDN variant of a domain 3350 name object, then the NNDN will be tagged as "mirrored". A 3351 mirroringNS attribute is used to specify if the mirrored IDN 3352 variant uses the NS mirror mechanism, meaning that the 3353 activated variant domain name (i.e., NNDN) is delegated in the 3354 DNS using the same NS records as in the . The 3355 default value of mirroringNS is true. If another mechanism 3356 such as DNAME is used, the value of mirroringNS attribute MUST 3357 be false. 3359 o An OPTIONAL element that contains the date and time of 3360 the NNDN object creation. 3362 Example of an object: 3364 ... 3365 3366 xn--exampl-gva.example 3367 pt-BR 3368 example.example 3369 withheld 3370 2005-04-23T11:49:00.0Z 3371 3372 ... 3374 5.6.1.2. object 3376 The element contains the NNDN that was deleted, 3377 i.e., the . 3379 Example of an object: 3381 ... 3382 3383 ... 3384 3385 xn--pingino-q2a.example 3386 3387 ... 3388 3389 ... 3391 5.6.2. CSV Model 3393 For the CSV Model of the NNDN object, the child 3394 element of the element is used to hold the new or 3395 updated NNDN objects for the deposit. The child 3396 element of the element is used to hold the deleted or 3397 purged NNDN objects for the deposit. Both the and 3398 elements contain one or more elements 3399 with a set of named CSV file definitions using the 3400 "name" attribute. 3402 5.6.2.1. 3404 The is used to hold the new or updated NNDN object 3405 information for the deposit. The is split into 3406 separate CSV file definitions using named elements with 3407 the "name" attribute. The following sections include the supported 3408 NNDN CSV file definitions. 3410 5.6.2.1.1. "NNDN" CSV File Definition 3412 The "NNDN" CSV File Definition defines the fields and CSV file 3413 references used for the NNDN object records. 3415 The following "csvNNDN" field elements MUST be used in the "NNDN" 3416 element: 3418 Fully-qualified name of the NNDN with 3419 type="eppcom:labelType" and isRequired="true". For IDNs the 3420 A-Label is used (see [RFC5891], Section 4.4). 3422 State of the NNDN: blocked or withheld with 3423 type="rdeNNDN:nameState" and isRequired="true". See 3424 Section 5.6.1.1 for a description of the possible values for the 3425 element. 3427 The following field elements MAY be used in the "NNDN" 3428 element: 3430 Domain name used to generate the IDN variant 3431 with type="eppcom:labelType". 3433 Defines whether the "mirroring" 3434 uses the NS mirror mechanism, as described 3435 for the "mirroringNS" attribute in 3436 Section 5.6.1.1, with type="boolean". If the field element is not 3437 defined the default value is "true". 3439 The following "rdeCsv" fields, defined in section CSV common field 3440 elements (Section 4.6.2.2), MAY be used in the "NNDN" 3441 element: 3443 Created date and time of the NNDN object. 3445 Name of the NNDN in Unicode character set for the 3446 field element. 3448 IDN Table Identifier for the NNDN that matches 3449 an IDN Table Reference Object record, as defined in Section 5.5.2. 3451 Example of an "NNDN" element: 3453 ... 3454 3455 ... 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3468 NNDN-YYYYMMDD.csv 3469 3470 3471 3472 ... 3473 3474 ... 3476 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3477 contains two NNDN records for an IDN with one blocked variant and one 3478 mirrored variant. 3480 xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example, 3481 blocked,,2005-04-23T11:49:00.0Z 3482 xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example, 3483 mirrored,1,2005-04-23T11:49:00.0Z 3485 5.6.2.2. 3487 The is used to hold the deleted NNDN objects in a 3488 Differential or Incremental Deposit. The is split 3489 into separate CSV file definitions using named elements 3490 with the "name" attribute. The following section defines the 3491 supported NNDN deletes CSV file definition. 3493 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3495 The following "NNDN" field elements MUST be used in the deletes 3496 "NNDN" element: 3498 Fully-qualified name of the NNDN with 3499 type="eppcom:labelType" and isRequired="true". 3501 Example of an "NNDN" element. 3503 ... 3504 3505 ... 3506 3507 3508 3509 3510 3511 3513 NNDN-delete-YYYYMMDD.csv 3514 3515 3516 3517 ... 3518 3519 ... 3521 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3522 contains one NNDN records. 3524 xn--bc456-3ve.example 3526 5.7. EPP Parameters Object 3528 The EPP Parameters Object is a pseudo-object that defines the set of 3529 object and object extension services supported by the registry, as 3530 defined in [RFC5730]. The EPP Parameters Object is only defined as 3531 XML but could be used in the XML model or CSV model. The EPP 3532 Parameters Object is defined using the 3533 element. The EPP Parameters Object SHOULD be included if the 3534 registry supports EPP. A maximum of one EPP Parameters Object MUST 3535 exist at a certain point in time (watermark). 3537 The syntax and content of the children 3538 elements is as explained in section 2.4 of [RFC5730]. The children 3539 of the are as follows: 3541 o One or more elements that indicate the EPP versions 3542 supported by the registry. 3544 o One or more elements that indicate the identifiers of the 3545 text response languages supported by the registry's EPP server. 3547 o One or more elements that contain namespace URIs 3548 representing the objects that the registry's EPP server is capable 3549 of managing. 3551 o An OPTIONAL element that contains one or more 3552 elements that contain namespace URIs representing object 3553 extensions supported by the registry's EPP server. 3555 o A element that contains child elements used to describe the 3556 server's privacy policy for data collection and management. See 3557 section 2.4 of [RFC5730] for more details. 3559 Example of element object: 3561 ... 3562 3563 1.0 3564 en 3565 urn:ietf:params:xml:ns:domain-1.0 3566 3567 urn:ietf:params:xml:ns:contact-1.0 3568 3569 urn:ietf:params:xml:ns:host-1.0 3570 3571 3572 urn:ietf:params:xml:ns:rgp-1.0 3573 urn:ietf:params:xml:ns:secDNS-1.1 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 ... 3594 5.8. Policy Object 3596 The Policy object is a pseudo-object that is used to specify which 3597 OPTIONAL elements from the XML Model are REQUIRED based on the 3598 business model of the registry. For the CSV Model, the OPTIONAL 3599 "isRequired" attribute of the elements, defined in 3600 Section 4.6.2.1, is used to specify which OPTIONAL fields are 3601 REQUIRED based on the business model of the registry. 3603 5.8.1. object 3605 The OPTIONAL contains the following attributes: 3607 o An that defines that the referenced is 3608 REQUIRED. 3610 o that defines the XPath (see, [W3C.REC-xpath-31-20170321]) 3611 of the element referenced by . 3613 Example of object: 3615 ... 3616 3618 ... 3620 5.9. Header Object 3622 The Header Object is a pseudo-object that is used to specify the 3623 number of objects in the repository at a specific point in time 3624 (watermark) regardless of the type of deposit: Differential, Full or 3625 Incremental Deposit. The Header Object may also be used to provide 3626 additional information on the contents of the deposit. The Header 3627 Object is only defined as XML but one header object MUST always be 3628 present per escrow deposit regardless of using XML Model or CSV 3629 Model. The Header Object is defined using the 3630 element. 3632 5.9.1. object 3634 The contains the following elements: 3636 o A choice of one of the elements defined in the 3637 "repositoryTypeGroup" group element that indicates the unique 3638 identifier for the repository being escrowed. Possible elements 3639 are: 3641 * A element that defines TLD or the RCDN being 3642 escrowed in the case of a Registry data escrow deposit. For 3643 IDNs the A-Label is used (see [RFC5891], Section 4.4). 3645 * A element that defines the Registrar ID 3646 corresponding to a Registrar data escrow deposit. In the case 3647 of an ICANN-accredited Registrar, the 3648 element MUST be the IANA Registrar ID assigned by ICANN. 3650 * A element that defines the provider ID 3651 corresponding to a Privacy and Proxy Services Provider data 3652 escrow deposit. In the case of an ICANN-accredited Privacy and 3653 Proxy Services Provider, the element MUST be 3654 the unique ID assigned by ICANN. 3656 * A element that defines the provider ID 3657 corresponding to a Reseller data escrow deposit. 3659 o A element that contains the number of objects in the SRS 3660 at a specific point in time (watermark) regardless of the type of 3661 deposit: Differential, Full or Incremental. The element 3662 supports the following attributes: 3664 * A "uri" attribute reflects the XML namespace URI of the primary 3665 objects for the XML Model and CSV Model. For example, the 3666 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3667 domain name objects using the XML Model, and the "uri" is set 3668 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3669 objects using the CSV Model. 3671 * An OPTIONAL "rcdn" attribute indicates the RCDN of the objects 3672 included in the element. For IDNs the A-Label is used 3673 [RFC5891], Section 4.4. If the "rcdn" attribute is present, 3674 the value of the element must include only objects 3675 related to registrations in the same and lower levels. For 3676 example in a data escrow deposit for the .EXAMPLE TLD, a value 3677 of "example" in the "rcdn" attribute within the element 3678 indicates the number of objects in the TLD including objects in 3679 other RCDNs within the TLD, whereas a value of "com.example" 3680 indicates the number of elements for objects under 3681 "com.example" and lower levels. Omitting the "rcdn" attribute 3682 indicates that the total includes all objects of the specified 3683 "uri" in the repository (e.g. the TLD, Registrar, or PPSP). 3685 * An OPTIONAL "registrarId" attribute indicates the identifier of 3686 the sponsoring Registrar of the objects included in the 3687 element. In the case of an ICANN-accredited Registrar, the 3688 value MUST be the IANA Registrar ID assigned by ICANN. 3690 o An OPTIONAL element that contains a tag that defines 3691 the expected content in the deposit. The producer and consumer of 3692 the deposits will coordinate the set of possible 3693 element values. 3695 Example of object referencing only the XML Model 3696 objects: 3698 ... 3699 3700 test 3701 2 3703 1 3705 1 3707 1 3709 3710 1 3712 1 3714 1 3716 3717 3718 ... 3720 Example of object referencing the CSV and XML 3721 Model objects: 3723 ... 3724 3725 test 3726 2 3728 1 3730 1 3732 1 3734 3735 1 3737 1 3739 1 3741 3742 3743 ... 3745 5.10. DNRD Common Objects Collection 3747 The DNRD Common Objects Collection contains data structures 3748 referenced by two or more of the main objects in the XML model. 3750 6. RDE IDN Variants handling 3752 Depending on the Registration Policy of the Registry, for a domain 3753 name there may be multiple variant names. See [variantTLDsReport] 3754 for further detail on IDN variants. 3756 A registry could choose to escrow IDN variants as domains or NNDN 3757 objects. A specific IDN variant can be represented in the escrow 3758 deposit, as a domain or as an NNDN object, but not both. 3760 If using domain objects to represent IDN variants, the normal 3761 behavior during restoration of an SRS based on an escrow deposit is 3762 to restore the IDN variants as a mirrored variant. If the 3763 registration data of the IDN variant is different from the original 3764 name, the details of this specific implementation MUST be described 3765 in the IDN policy document. 3767 An NNDN or a domain name are explicit representations of an IDN 3768 variant while an IDN variant computed based on an algorithm is an 3769 implicit representation. Explicit representation of an IDN variant 3770 takes precedence over an implicit representation. 3772 7. Profile 3774 Different business models of registries exist, therefore the registry 3775 is responsible for defining a profile that matches its particular 3776 business model. The profile mechanism allows a registry to extend 3777 this specification. 3779 A profile is the process of: 3781 1. Extending base objects with the mechanisms defined for XML and 3782 CSV models. 3784 * In the case of the XML model, abstract elements could be use 3785 to extend the following objects: , , , 3786 and using XML schema substitution groups 3787 feature. 3789 2. Defining a object to specify which OPTIONAL elements of 3790 this base specification is required based on the business model 3791 of the registry. An example is the element that is 3792 usually REQUIRED but it is specified as OPTIONAL in this 3793 specification to support some existing business models. 3795 3. Adding new escrowed objects using the and 3796 elements. 3798 4. Providing the XML schemas to third parties that require them to 3799 validate the escrow deposits. 3801 8. Data escrow agent extended verification process 3803 A Data Escrow Agent SHOULD perform an extended verification process 3804 that starts by creating a dataset to be tested by following section 3805 5.2 in [I-D.ietf-regext-data-escrow]. 3807 The following are the minimum suggested tests on the dataset: 3809 o Validate the escrow deposits using the definition agreed with the 3810 registry. 3812 * In the case of the XML model, the contents of the escrow 3813 deposits MUST be validated using the XML schemas of the 3814 profile. 3816 o Count the objects and validate that the number of objects is equal 3817 to the number objects reported in the
element of the 3818 escrow deposit of that point in time (watermark). 3820 o All contact objects linked to domain names MUST be present. 3822 o All registrars objects linked to other objects MUST be present. 3824 o No domain name exists as both a domain name and an NNDN. 3826 o The elements listed as required in the element MUST be 3827 present. 3829 o All idnTableRef definitions linked from other objects MUST be 3830 present. 3832 o If an EPP Parameters Object was escrowed in the past, one and only 3833 one EPP Parameters Object MUST be present. 3835 o The watermark is not in the future. 3837 9. Formal Syntax 3839 This standard is specified in XML Schema notation. The formal syntax 3840 presented here is a complete schema representation suitable for 3841 automated validation. 3843 The and tags are not part of the schema; 3844 they are used to note the beginning and ending of the schema for URI 3845 registration purposes. 3847 9.1. RDE CSV Schema 3849 3850 3851 3857 3860 3861 3862 3863 3864 Registry Data Escrow Comma-Separated Values (CSV) 3865 3866 3867 3868 3870 3871 3872 3873 3875 3877 3878 3881 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3896 3897 3898 3899 3900 3901 3902 3903 3904 3907 3910 3911 3913 3914 3915 3916 3917 3918 3919 3922 3925 3926 3927 3928 3929 3930 3933 3934 3935 3936 3937 3940 3941 3942 3943 3944 3945 3946 3947 3950 3951 3952 3953 3954 3957 3958 3959 3960 3961 3964 3965 3966 3967 3968 3971 3972 3973 3974 3975 3978 3979 3980 3981 3982 3985 3986 3987 3990 3992 3995 3996 3999 4001 4004 4005 4008 4011 4014 4016 4019 4021 4024 4026 4029 4030 4031 4032 4033 4036 4037 4038 4039 4040 4041 4042 4043 4046 4047 4048 4049 4050 4053 4056 4059 4060 4063 4064 4067 4070 4071 4072 4073 4074 4077 4078 4079 4080 4081 4082 4083 4084 4087 4088 4089 4090 4091 4092 4093 4094 4095 4098 4099 4100 4101 4102 4103 4104 4105 4108 4109 4110 4111 4112 4113 4114 4115 4116 4119 4120 4121 4122 4123 4124 4125 4126 4129 4130 4131 4132 4133 4134 4135 4136 4137 4140 4141 4142 4143 4144 4145 4146 4147 4150 4151 4152 4153 4154 4155 4156 4157 4158 4161 4162 4163 4164 4165 4166 4167 4168 4171 4172 4173 4174 4175 4178 4179 4180 4181 4182 4185 4186 4187 4188 4189 4192 4193 4196 4197 4198 4199 4200 4203 4204 4205 4206 4207 4208 4209 4210 4211 4214 4215 4216 4217 4218 4219 4220 4221 4222 4225 4226 4227 4228 4229 4230 4231 4232 4233 4236 4237 4238 4239 4240 4243 4244 4245 4246 4247 4249 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4267 4268 4269 4270 4271 4272 4273 4275 4278 4280 4283 4284 4285 4286 4287 4290 4291 4292 4293 4294 4297 4299 4300 4301 4304 4305 4307 9.2. RDE Domain Object 4309 4310 4311 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 Registry Data Escrow Domain provisioning schema 4332 4333 4334 4338 4340 4343 4344 4345 4346 4347 4348 4350 4352 4355 4358 4361 4364 4368 4371 4375 4378 4380 4383 4386 4389 4392 4396 4399 4402 4405 4406 4407 4408 4409 4410 4411 4413 4415 4417 4419 4421 4424 4425 4426 4427 4428 4429 4430 4431 4435 4436 4437 4438 4439 4440 4442 9.3. CSV Domain Object 4444 4445 4446 4456 4459 4460 4461 4462 4463 4464 4465 4466 4467 Domain Name Comma-Separated Values (CSV) Object 4468 4469 4470 4473 4476 4477 4478 4479 4480 4482 4483 4484 4485 4486 4489 4492 4493 4494 4495 4496 4498 4499 4500 4501 4502 4503 4506 4507 4510 4511 4512 4513 4514 4517 4518 4519 4520 4521 4524 4525 4526 4527 4528 4531 4532 4533 4534 4535 4536 4539 4540 4541 4542 4543 4546 4547 4548 4549 4550 4553 4554 4557 4558 4561 4562 4565 4566 4569 4570 4573 4574 4577 4578 4581 4582 4583 4584 4585 4588 4589 4590 4591 4592 4595 4596 4599 4600 4601 4602 4603 4604 4607 4608 4609 4610 4613 4614 4616 9.4. RDE Host Object 4618 4619 4620 4628 4629 4630 4631 4632 4633 4634 Registry Data Escrow Host provisioning schema 4635 4636 4637 4641 4643 4646 4647 4648 4649 4650 4651 4653 4655 4658 4662 4664 4667 4670 4673 4676 4679 4680 4681 4683 4684 4685 4686 4687 4688 4690 4692 4694 4695 4696 4697 4698 4699 4701 9.5. CSV Host Object 4703 4704 4705 4713 4716 4717 4718 4719 4720 4721 4722 Host Comma-Separated Values (CSV) Object 4723 4724 4725 4728 4732 4733 4734 4735 4736 4738 4739 4740 4741 4742 4745 4748 4749 4750 4751 4752 4754 4755 4756 4757 4758 4759 4762 4763 4766 4767 4768 4769 4770 4773 4774 4775 4776 4777 4781 4782 4783 4784 4785 4788 4789 4790 4791 4792 4795 4796 4797 4798 4799 4800 4803 4804 4805 4806 4809 4810 4812 9.6. RDE Contact Object 4814 4815 4816 4824 4825 4826 4827 4828 4829 4830 4831 Registry Data Escrow contact provisioning schema 4832 4833 4834 4838 4840 4843 4844 4845 4846 4847 4848 4850 4852 4855 4858 4861 4864 4866 4868 4871 4874 4878 4881 4884 4887 4890 4891 4892 4893 4894 4895 4896 4898 4900 4902 4904 4906 4907 4908 4909 4910 4911 4912 4913 4917 4918 4919 4920 4921 4922 4924 9.7. CSV Contact Object 4926 4927 4928 4936 4939 4940 4941 4942 4943 4944 4945 Contact Comma-Separated Values (CSV) Object 4946 4947 4948 4951 4954 4955 4956 4957 4958 4960 4961 4962 4963 4964 4967 4970 4971 4972 4973 4974 4976 4977 4978 4979 4980 4981 4984 4985 4986 4987 4988 4991 4992 4993 4994 4995 4998 4999 5002 5005 5006 5007 5008 5009 5012 5013 5014 5015 5016 5019 5022 5023 5026 5027 5028 5029 5030 5033 5034 5035 5036 5040 5043 5044 5045 5046 5047 5050 5051 5052 5053 5054 5055 5056 5057 5058 5061 5063 5064 5065 5066 5067 5068 5069 5070 5071 5074 5076 5077 5078 5079 5080 5083 5084 5087 5088 5089 5092 5093 5094 5095 5096 5099 5100 5101 5102 5103 5106 5107 5110 5111 5114 5115 5116 5117 5118 5121 5123 5124 5125 5126 5127 5130 5131 5132 5133 5134 5137 5139 5140 5141 5142 5143 5145 5148 5150 5153 5155 5158 5160 5163 5165 5168 5170 5173 5175 5178 5180 5183 5185 5188 5190 5193 5194 5195 5196 5197 5200 5201 5202 5203 5204 5207 5208 5209 5210 5211 5212 5215 5216 5217 5218 5221 5222 5224 9.8. RDE Registrar Object 5226 5227 5228 5236 5237 5238 5239 5240 5241 5242 5243 Registry Data Escrow registrar provisioning schema 5244 5245 5246 5250 5252 5255 5256 5257 5258 5259 5260 5262 5264 5267 5270 5274 5277 5280 5283 5286 5289 5292 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5316 5317 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5333 5335 5338 5341 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 5368 5371 5374 5375 5376 5377 5378 5379 5380 5381 5385 5386 5387 5388 5389 5390 5392 9.9. CSV Registrar Object 5394 5395 5396 5405 5408 5409 5410 5411 5412 5413 5414 5415 Registar Comma-Separated Values (CSV) Object 5416 5417 5418 5421 5424 5425 5426 5427 5428 5430 5431 5432 5433 5434 5437 5440 5441 5442 5443 5444 5446 5447 5448 5449 5450 5451 5454 5455 5458 5459 5460 5461 5462 5463 5466 5469 5470 5471 5472 5473 5476 5477 5480 5483 5484 5485 5486 5487 5490 5491 5492 5493 5494 5495 5496 5497 5499 5501 5502 5503 5504 5505 5506 5507 5508 5509 5510 5511 5512 5515 5518 5519 5521 9.10. RDE IDN Table Reference Objects 5523 5524 5525 5530 5531 5532 5533 Registry Data Escrow IDN provisioning schema 5534 5535 5536 5539 5542 5543 5544 5545 5546 5547 5550 5552 5553 5556 5557 5558 5559 5560 5561 5562 5563 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5577 5579 9.11. CSV IDN Language Object 5581 5582 5583 5589 5592 5593 5594 5595 5596 IDN Language Comma-Separated Values (CSV) Object 5597 5599 5600 5603 5606 5607 5608 5609 5610 5612 5613 5614 5615 5616 5619 5622 5623 5624 5625 5626 5628 5629 5630 5631 5632 5635 5636 5638 9.12. EPP Parameters Object 5640 5641 5642 5649 5650 5651 5652 5653 5654 Registry Data Escrow EPP Parameters schema 5655 5656 5657 5658 5660 5661 5665 5666 5667 5668 5669 5672 5675 5678 5681 5683 5684 5685 5686 5687 5688 5690 9.13. NNDN Object 5692 5693 5694 5701 5702 5703 5704 5705 5706 Registry Data Escrow NNDN provisioning schema 5707 5708 5709 5713 5715 5718 5719 5720 5721 5722 5723 5725 5728 5731 5734 5736 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5753 5756 5757 5758 5759 5760 5761 5762 5763 5764 5768 5769 5770 5771 5772 5773 5775 9.14. CSV NNDN Object 5777 5778 5779 5786 5789 5790 5791 5792 5793 5794 NNDN (NNDN's not domain name) (CSV) Object 5795 5796 5797 5800 5803 5804 5805 5806 5807 5809 5810 5811 5812 5813 5816 5819 5820 5821 5822 5823 5825 5826 5827 5828 5829 5830 5833 5834 5837 5838 5841 5842 5843 5844 5845 5848 5849 5850 5851 5852 5855 5858 5859 5861 9.15. Policy Object 5862 5863 5864 5869 5870 5871 Registry Data Escrow Policy schema 5872 5873 5874 5875 5878 5879 5880 5881 5884 5887 5888 5889 5890 5891 5893 9.16. Header Object 5895 5896 5897 5903 5904 5905 5906 5907 Data Escrow Deposit Header schema 5908 5909 5910 5911 5914 5915 5916 5917 5918 5919 5920 5923 5926 5927 5928 5929 5930 5931 5932 5934 5936 5938 5940 5941 5942 5943 5944 5945 5948 5950 5952 5953 5954 5955 5956 5958 9.17. DNRD Common Objects 5960 5961 5962 5967 5968 5969 5970 Data Escrow Deposit Common Objects schema 5971 5972 5973 5974 5975 5976 5978 5979 5980 5981 5982 5984 10. Internationalization Considerations 5986 Data Escrow deposits are represented in XML, which provides native 5987 support for encoding information using the Unicode character set and 5988 its more compact representations including UTF-8. Conformant XML 5989 processors recognize both UTF-8 and UTF-16. Though XML includes 5990 provisions to identify and use other character encodings through use 5991 of an "encoding" attribute in an declaration, use of UTF-8 is 5992 RECOMMENDED. 5994 11. IANA Considerations 5996 This document uses URNs to describe XML namespaces and XML schemas 5997 conforming to a registry mechanism described in [RFC3688]. The 5998 following URI assignments is requested of IANA. 6000 Registration request for the RDE CSV namespace: 6002 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6004 Registrant Contact: IESG 6005 Note to RFC Editor: Please remove the email address from the RFC 6006 after IANA records it. 6008 XML: None. Namespace URIs do not represent an XML specification. 6010 Registration request for the RDE CSV XML schema: 6012 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6014 Registrant Contact: IESG 6016 Note to RFC Editor: Please remove the email address from the RFC 6017 after IANA records it. 6019 See Section 9.1 of this document. 6021 Registration request for the RDE domain namespace: 6023 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6025 Registrant Contact: IESG 6027 Note to RFC Editor: Please remove the email address from the RFC 6028 after IANA records it. 6030 XML: None. Namespace URIs do not represent an XML specification. 6032 Registration request for the RDE domain XML schema: 6034 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6036 Registrant Contact: IESG 6038 Note to RFC Editor: Please remove the email address from the RFC 6039 after IANA records it. 6041 See Section 9.2 of this document. 6043 Registration request for the CSV domain namespace: 6045 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6047 Registrant Contact: IESG 6049 Note to RFC Editor: Please remove the email address from the RFC 6050 after IANA records it. 6052 XML: None. Namespace URIs do not represent an XML specification. 6054 Registration request for the CSV domain XML schema: 6056 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6058 Registrant Contact: IESG 6060 Note to RFC Editor: Please remove the email address from the RFC 6061 after IANA records it. 6063 See Section 9.3 of this document. 6065 Registration request for the RDE host namespace: 6067 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6069 Registrant Contact: IESG 6071 Note to RFC Editor: Please remove the email address from the RFC 6072 after IANA records it. 6074 XML: None. Namespace URIs do not represent an XML specification. 6076 Registration request for the RDE host XML schema: 6078 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6080 Registrant Contact: IESG 6082 Note to RFC Editor: Please remove the email address from the RFC 6083 after IANA records it. 6085 See Section 9.4 of this document. 6087 Registration request for the CSV host namespace: 6089 URI: urn:ietf:params:xml:ns:csvHost-1.0 6091 Registrant Contact: IESG 6093 Note to RFC Editor: Please remove the email address from the RFC 6094 after IANA records it. 6096 XML: None. Namespace URIs do not represent an XML specification. 6098 Registration request for the CSV host XML schema: 6100 URI: urn:ietf:params:xml:schema:csvHost-1.0 6101 Registrant Contact: IESG 6103 Note to RFC Editor: Please remove the email address from the RFC 6104 after IANA records it. 6106 See Section 9.5 of this document. 6108 Registration request for the RDE contact namespace: 6110 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6112 Registrant Contact: IESG 6114 Note to RFC Editor: Please remove the email address from the RFC 6115 after IANA records it. 6117 XML: None. Namespace URIs do not represent an XML specification. 6119 Registration request for the RDE contact XML schema: 6121 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6123 Registrant Contact: IESG 6125 Note to RFC Editor: Please remove the email address from the RFC 6126 after IANA records it. 6128 See Section 9.6 of this document. 6130 Registration request for the CSV contact namespace: 6132 URI: urn:ietf:params:xml:ns:csvContact-1.0 6134 Registrant Contact: IESG 6136 Note to RFC Editor: Please remove the email address from the RFC 6137 after IANA records it. 6139 XML: None. Namespace URIs do not represent an XML specification. 6141 Registration request for the CSV contact XML schema: 6143 URI: urn:ietf:params:xml:schema:csvContact-1.0 6145 Registrant Contact: IESG 6147 Note to RFC Editor: Please remove the email address from the RFC 6148 after IANA records it. 6150 See Section 9.7 of this document. 6152 Registration request for the RDE registrar namespace: 6154 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6156 Registrant Contact: IESG 6158 Note to RFC Editor: Please remove the email address from the RFC 6159 after IANA records it. 6161 XML: None. Namespace URIs do not represent an XML specification. 6163 Registration request for the RDE registrar XML schema: 6165 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6167 Registrant Contact: IESG 6169 Note to RFC Editor: Please remove the email address from the RFC 6170 after IANA records it. 6172 See Section 9.8 of this document. 6174 Registration request for the CSV registrar namespace: 6176 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6178 Registrant Contact: IESG 6180 Note to RFC Editor: Please remove the email address from the RFC 6181 after IANA records it. 6183 XML: None. Namespace URIs do not represent an XML specification. 6185 Registration request for the CSV registrar XML schema: 6187 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6189 Registrant Contact: IESG 6191 Note to RFC Editor: Please remove the email address from the RFC 6192 after IANA records it. 6194 See Section 9.9 of this document. 6196 Registration request for the RDE IDN namespace: 6198 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6200 Registrant Contact: IESG 6202 Note to RFC Editor: Please remove the email address from the RFC 6203 after IANA records it. 6205 XML: None. Namespace URIs do not represent an XML specification. 6207 Registration request for the RDE IDN XML schema: 6209 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6211 Registrant Contact: IESG 6213 Note to RFC Editor: Please remove the email address from the RFC 6214 after IANA records it. 6216 See Section 9.10 of this document. 6218 Registration request for the CSV IDN namespace: 6220 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6222 Registrant Contact: IESG 6224 Note to RFC Editor: Please remove the email address from the RFC 6225 after IANA records it. 6227 XML: None. Namespace URIs do not represent an XML specification. 6229 Registration request for the CSV IDN XML schema: 6231 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6233 Registrant Contact: IESG 6235 Note to RFC Editor: Please remove the email address from the RFC 6236 after IANA records it. 6238 See Section 9.11 of this document. 6240 Registration request for the RDE EPP parameters namespace: 6242 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6244 Registrant Contact: IESG 6245 Note to RFC Editor: Please remove the email address from the RFC 6246 after IANA records it. 6248 XML: None. Namespace URIs do not represent an XML specification. 6250 Registration request for the RDE EPP parameters XML schema: 6252 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6254 Registrant Contact: IESG 6256 Note to RFC Editor: Please remove the email address from the RFC 6257 after IANA records it. 6259 See Section 9.12 of this document. 6261 Registration request for the RDE NNDN namespace: 6263 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6265 Registrant Contact: IESG 6267 Note to RFC Editor: Please remove the email address from the RFC 6268 after IANA records it. 6270 XML: None. Namespace URIs do not represent an XML specification. 6272 Registration request for the RDE NNDN XML schema: 6274 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6276 Registrant Contact: IESG 6278 Note to RFC Editor: Please remove the email address from the RFC 6279 after IANA records it. 6281 See Section 9.13 of this document. 6283 Registration request for the CSV NNDN namespace: 6285 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6287 Registrant Contact: IESG 6289 Note to RFC Editor: Please remove the email address from the RFC 6290 after IANA records it. 6292 XML: None. Namespace URIs do not represent an XML specification. 6294 Registration request for the CSV NNDN XML schema: 6296 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6298 Registrant Contact: IESG 6300 Note to RFC Editor: Please remove the email address from the RFC 6301 after IANA records it. 6303 See Section 9.14 of this document. 6305 Registration request for the RDE Policy namespace: 6307 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6309 Registrant Contact: IESG 6311 Note to RFC Editor: Please remove the email address from the RFC 6312 after IANA records it. 6314 XML: None. Namespace URIs do not represent an XML specification. 6316 Registration request for the RDE Policy XML schema: 6318 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6320 Registrant Contact: IESG 6322 Note to RFC Editor: Please remove the email address from the RFC 6323 after IANA records it. 6325 See Section 9.15 of this document. 6327 Registration request for the RDE Header namespace: 6329 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6331 Registrant Contact: IESG 6333 Note to RFC Editor: Please remove the email address from the RFC 6334 after IANA records it. 6336 XML: None. Namespace URIs do not represent an XML specification. 6338 Registration request for the RDE Header XML schema: 6340 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6341 Registrant Contact: IESG 6343 Note to RFC Editor: Please remove the email address from the RFC 6344 after IANA records it. 6346 See Section 9.16 of this document. 6348 Registration request for the RDE Common Objects namespace: 6350 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6352 Registrant Contact: IESG 6354 Note to RFC Editor: Please remove the email address from the RFC 6355 after IANA records it. 6357 XML: None. Namespace URIs do not represent an XML specification. 6359 Registration request for the RDE Common Objects XML schema: 6361 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6363 Registrant Contact: IESG 6365 Note to RFC Editor: Please remove the email address from the RFC 6366 after IANA records it. 6368 See Section 9.17 of this document. 6370 12. Implementation Status 6372 Note to RFC Editor: Please remove this section and the reference to 6373 RFC 7942 [RFC7942] before publication. 6375 This section records the status of known implementations of the 6376 protocol defined by this specification at the time of posting of this 6377 Internet-Draft, and is based on a proposal described in RFC 7942 6378 [RFC7942]. The description of implementations in this section is 6379 intended to assist the IETF in its decision processes in progressing 6380 drafts to RFCs. Please note that the listing of any individual 6381 implementation here does not imply endorsement by the IETF. 6382 Furthermore, no effort has been spent to verify the information 6383 presented here that was supplied by IETF contributors. This is not 6384 intended as, and must not be construed to be, a catalog of available 6385 implementations or their features. Readers are advised to note that 6386 other implementations may exist. 6388 According to RFC 7942 [RFC7942], "this will allow reviewers and 6389 working groups to assign due consideration to documents that have the 6390 benefit of running code, which may serve as evidence of valuable 6391 experimentation and feedback that have made the implemented protocols 6392 more mature. It is up to the individual working groups to use this 6393 information as they see fit". 6395 12.1. Implementation in the gTLD space 6397 Organization: ICANN 6399 Name: ICANN Registry Agreement 6401 Description: the ICANN Base Registry Agreement requires Registries, 6402 Data Escrow Agents, and ICANN to implement this specification. ICANN 6403 receives daily notifications from Data Escrow Agents confirming that 6404 more than 1,200 gTLDs are sending deposits that comply with this 6405 specification. ICANN receives on a weekly basis per gTLD, from more 6406 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6407 also complies with this specification. In addition, ICANN is aware 6408 of Registry Service Provider transitions using data files that 6409 conform to this specification. 6411 Level of maturity: production. 6413 Coverage: all aspects of this specification are implemented. 6415 Version compatibility: versions 03 - 09 are known to be implemented. 6417 Contact: gustavo.lozano@icann.org 6419 URL: https://www.icann.org/resources/pages/registries/registries- 6420 agreements-en 6422 13. Security Considerations 6424 This specification does not define the security mechanisms to be used 6425 in the transmission of the data escrow deposits, since it only 6426 specifies the minimum necessary to enable the rebuilding of a 6427 registry from deposits without intervention from the original 6428 registry. 6430 Depending on local policies, some elements, or, most likely, the 6431 whole deposit will be considered confidential. As such, the parties 6432 SHOULD take all the necessary precautions such as encrypting the data 6433 at rest and in transit to avoid inadvertent disclosure of private 6434 data. Regardless of the precautions taken by the parties regarding 6435 data at rest and in transit, authentication credentials MUST NOT be 6436 escrowed. 6438 Authentication of the parties passing data escrow deposit files is 6439 also of the utmost importance. The escrow agent MUST properly 6440 authenticate the registry's identity before accepting data escrow 6441 deposits. The registry MUST authenticate the escrow agent's identity 6442 before submitting any data, and the data escrow agent MUST 6443 authenticate the identity of the party receiving the data escrow 6444 deposits for the purposes deemed appropriate. 6446 Additionally, the registry and the escrow agent MUST use integrity 6447 checking mechanisms to ensure the data transmitted is what the source 6448 intended. Validation of the contents by the parties is RECOMMENDED 6449 to ensure that the file was transmitted correctly from the registry 6450 or escrow agent and that the contents are "meaningful". 6452 A few elements in this specification contain URLs, the use of HTTP 6453 over TLS (Transport Layer Security), [RFC2818] is RECOMMENDED on the 6454 URLs. 6456 The various data structures in the document include a few places that 6457 have internal redundancy, and if the values become inconsistent there 6458 can be harmful consequences, such as different entities using 6459 different fields as their reference. 6461 Note: if Transport Layer Security (TLS) is used when providing an 6462 escrow services, the recommendations in [BCP195] MUST be implemented. 6464 14. Privacy Considerations 6466 This specification defines a format that may be used to escrow 6467 personal data. The process of data escrow is governed by a legal 6468 document agreed by the parties, and such legal document must ensure 6469 that privacy-sensitive and/or personal data receives the required 6470 protection. 6472 15. Acknowledgments 6474 Parts of this document are based on EPP [RFC5730] and related RFCs by 6475 Scott Hollenbeck. 6477 Special suggestions that have been incorporated into this document 6478 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6479 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6480 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6481 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6482 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6483 Mitchell, Francisco Obispo, Bhadresh Modi, Alexander Mayrhofer and 6484 Benjamin Kaduk. 6486 Shoji Noguchi and Francisco Arias participated as co-authors until 6487 version 05 providing invaluable support for this document. 6489 16. Change History 6491 [[RFC Editor: Please remove this section.]] 6493 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6494 dnrd-objects-mapping-00 6496 1. Added definition for child elements under the element. 6498 2. Added definition for child elements under the element. 6500 3. Added definition for child elements under the element. 6502 4. Rewrote the IDN Variants Handling section to use the variant 6503 states as described in ICANN's Study of Issues Related to the 6504 Management of IDN Variant TLDs. 6506 5. Renamed to in the . 6508 6. Renamed to in the element. 6510 7. Renamed to in the element. 6512 8. Added element under element. 6514 9. Fixed some typographical errors and omissions. 6516 16.2. Changes from 00 to 01 6518 1. Specify OPTIONAL elements in the draft. 6520 2. Added NNDN object to support list of reserved names and different 6521 IDN variants models. 6523 3. Removed subordinated host element from the domain object. 6525 4. Added eppParams object. 6527 5. Added variantGenerator element to the domain object. 6529 6. Added lgr to the IDN table object. 6531 16.3. Changes from 01 to 02 6533 1. Updates to the all objects based on feedback from the list. 6535 2. Start of XML and CSV drafts merge. 6537 3. Added header object. 6539 4. Added report object. 6541 5. Added notification object. 6543 6. Added Data Escrow Agent Extended Verification Process section. 6545 7. Added Notifications from Registries to Third Parties. 6547 8. Added Notifications from Data Escrow Agents to Third Parties. 6549 9. Added FULL, DIFF deposit examples using the XML model only. 6551 16.4. Changes from 02 to 03 6553 1. Remove authinfo from the XML Schema. 6555 2. Resend attribute is now an element 6557 3. Scope attribute added to policy object. 6559 16.5. Changes from 03 to 04 6561 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6562 arias-noguchi-dnrd-objects-mapping-02. 6564 2. Changed the cksum attribute of to use CRC32 and 6565 changed all of the sample cksum values to use CRC32, based on 6566 feedback from David Kipling. 6568 3. Changed the optional element to be an optional 6569 "sep" attribute value of the element with a default 6570 value of "," based on feedback from David Kipling. 6572 4. Added support for the optional "parent" attribute for the to the 6573 CSV fields to indicate a field as a reference to a parent 6574 object, based on feedback from David Kipling. 6576 5. Added support for the CSV model for the NNDN. 6578 6. Added support to delete hosts based on roid. 6580 7. Added mirrored state to NNDN 6582 8. Minor fixes to XML XSDs. 6584 9. The Report and Notification objects were moved to draft-lozano- 6585 icann-registry-interfaces 6587 10. The section Data escrow notifications was moved to draft-lozano- 6588 icann-registry-interfaces 6590 11. Removed references to the , , and 6591 from the "hostStatuses" and "hostAddresses" CSV 6592 files. 6594 12. Removed references to the , , and 6595 from the "contactStatuses" CSV file. 6597 13. Removed references to the , , and 6598 from the "domainContacts", "domainStatuses", 6599 and "domainNameServers" CSV files. 6601 14. Changed to . 6603 15. Replaced use of to new field 6604 in the "domain", "idnLanguage", and "NNDN" CSV files. 6606 16. Replaced use of with in the 6607 "host" element. 6609 17. Changed the foreign key of the hosts to use 6610 instead of and removed use of in 6611 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6612 files. 6614 18. Added use of the MUST keyword for CSV fields that are required 6615 to be supported in an EPP based system. 6617 19. Removed use of the field element for the 6618 "registrar" CSV file. 6620 20. Added definition of field element. 6622 16.6. Changes from 04 to 05 6624 1. Updated the examples of the full and differential deposits using 6625 the CSV and XML model. 6627 2. Made optional for the "domainTransfer" CSV file 6628 to match the XML definition. 6630 3. Made optional for the "domain" CSV file 6631 to match the XML definition. 6633 4. Made optional for the "domain" and "contact" CSV 6634 files to match the XML definition. 6636 5. Change from IDREF to idType. 6638 6. Minor editorial changes. 6640 16.7. Changes from 05 to 06 6642 1. Revised the differential and incremental deposits for the CSV 6643 format to use cascade update / replace and delete from the parent 6644 object to be consistent with the XML format. 6646 2. Revised the structure of the CSV format sections to utilize sub- 6647 sections instead of a list for the CSV file definitions. 6649 3. Added the "CSV Parent Child Relationship" section to describe the 6650 concept of parent child relationships across CSV file 6651 definitions. 6653 4. Added the "domainNameServersAddresses" CSV File Definition 6654 section to support the domain host attributes model of [RFC5731]. 6656 5. Made the required fields in the CSV format consistent with the 6657 XML format. The CSV fields updated to be required include: 6658 , , , 6659 , , , 6660 , , , 6661 , , , 6662 , , 6663 , , , 6664 , , 6665 , and . 6667 6. Revised the CSV examples to use a more realistic set of records. 6669 16.8. Changes from 06 to 07 6671 1. Created "repositoryTypeGroup" group element in the rdeHeader 6672 including the , and 6673 elements. 6675 2. Added the optional "rcdn" and "registrarId" attributes to the 6676 element 6678 16.9. Changes from 07 to 08 6680 1. The following registrar elements were made optional to support 6681 greater flexibility for the implementation of policies: status, 6682 postalInfo, email and crDate. 6684 2. The following domain name elements were made optional to support 6685 greater flexibility for the implementation of policies: crRr. 6687 16.10. Changes from 08 to 09 6689 1. Implementation Status section was added 6691 16.11. Changes from 09 to 10 6693 1. Editorial changes in section Section 5.1.2.1.6. 6695 2. Added MAY clause when the DS Data Interface is used in section 6696 Section 5.1.2.1.6. 6698 16.12. Changes from 10 to REGEXT 00 6700 1. Internet Draft (I-D) adopted by the REGEXT WG. 6702 16.13. Changes REGEXT 00 to REGEXT 01 6704 1. Added the element to the 6705 "repositoryTypeGroup" group element in the rdeHeader. 6707 2. Privacy consideration section was added 6709 3. Updates on section 8 6711 16.14. Changes REGEXT 01 to REGEXT 02 6713 1. Added a choice between the use of the or 6714 fields in the CSV "domain", "host", and 6715 "contact" definitions. 6717 2. Added a choice between the use of the or 6718 fields in the CSV "domainNameServers" 6719 definition. 6721 3. Changed "of client" to "of the client" throughout the document. 6723 4. Modified all references of 'The attribute isRequired MUST equal 6724 "true".' to 'The attribute "isRequired" MUST equal "true".' 6726 5. Combined the and 6727 fields in a single required list for the CSV "domainContacts" 6728 definition. 6730 6. Combined the , , and 6731 fields in a single required list for the 6732 CSV "domainStatuses" definition. 6734 7. Moved the the fields to the MAY 6735 list for the CSV "domain", "host", and "contact" definitions. 6737 8. Made the order of the , , 6738 , and fields more consistent in the 6739 CSV lists. 6741 9. Fixed an error in the order of the object example. 6743 10. Changed to be optional to match being 6744 optional in the XML model, by having it use type 6745 rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and 6746 ensuring that is included in the MAY field 6747 lists and not the MUST field lists. 6749 11. Made optional for the "domain" CSV definition 6750 to be consistent with the XML model, by removing the sentence 6751 'The attribute "isRequired" MUST equal "true".' from the 6752 description and moving the field to the MAY field list. 6754 12. Made optional for the "domain" and "contact" 6755 CSV definitions to be consistent with the XML model, by moving 6756 the field to the MAY field list. 6758 13. Made optional to be consistent with the XML 6759 model, by having it use type rdeCsv:fClIDType instead of 6760 rdeCsv:fClIDRequiredType. 6762 14. Made required to be consistent with the XML 6763 model, by having it use type rdeCsv:fClIDRequiredType instead of 6764 rdeCsv:fClIDType. 6766 15. Made the field in the "host", "contact", 6767 and "registrar" CSV definitions required explicitly by removing 6768 'and isRequired="true"' and adding the sentence 'The attribute 6769 isRequired MUST equal "true".', when it is chosen as the primary 6770 field. 6772 16. Removed extra '/>.' at the end of the field 6773 description in the "hostStatuses" CSV definition. 6775 17. Made the field optional to be consistent 6776 with the XML model, by having csvRegistrar:fStatusType extend 6777 rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. 6779 18. Made the field for the "registrar" CSV 6780 definition explicitly optional to be consistent with the XML 6781 model, by adding the sentence 'The attribute isRequired MUST 6782 equal "false".' to the field description and including the 6783 definition of isRequired="false" in the "registrar" CSV 6784 definition examples. 6786 19. Added the choice between the use of the and 6787 fields in the deletes "registrar" CSV 6788 definition to be consistent with the "registrar" CSV definition. 6790 20. Made the and elements optional for the host and 6791 contact objects in the XML model to be consistent with the 6792 domain object. 6794 16.15. Changes REGEXT 02 to REGEXT 03 6796 1. Added the optional element contentTag in the header object. 6798 2. Editorial updates. 6800 16.16. Changes REGEXT 03 to REGEXT 04 6802 1. Note: Updates from version REGEXT 03 to REGEXT 04 attend the 6803 feedback provided during the document shepherd review. 6805 2. Editorial updates. 6807 3. Examples now use domain names from the .example TLD. 6809 4. The introduction was enhanced by explaining the need for data 6810 escrow and the proposed solution. 6812 5. Explanation regarding NNDN was improved. 6814 6. Explanation regarding the CSV and XML model was improved. 6816 7. Section 4.5 updated to make the text clearer. 6818 8. draft-arias-noguchi-registry-data-escrow is now referenced from 6819 the I-D repository. 6821 9. The XML prefix "rdeDomain" is now consistently used. 6823 10. The prevID attribute was removed from the examples of full 6824 deposits. 6826 11. The examples were updated to use present dates. 6828 16.17. Changes REGEXT 04 to REGEXT 05 6830 1. draft-ietf-regext-data-escrow (version 04) is now referenced from 6831 the I-D repository. 6833 2. The example in idnLanguage CSV file definition updated to use the 6834 sep attribute. 6836 3. The reference in the example in hostAddresses CSV file definition 6837 was updated. 6839 4. Moved [RFC0791] and [RFC5952] to the Normative References 6840 section. 6842 16.18. Changes REGEXT 05 to REGEXT 06 6844 1. Changes based on the feedback provided here: 6845 https://mailarchive.ietf.org/arch/msg/regext/ 6846 nA8eTYIrXJ44_6ullQlRLW6T74s 6848 16.19. Changes REGEXT 06 to REGEXT 07 6850 1. Changes based on the feedback provided here: 6851 https://mailarchive.ietf.org/arch/msg/regext/hDLz2ym4oR-ukA4Fm- 6852 QJ8FzaxxE 6854 2. Changes based on the feedback provided here: 6855 https://mailarchive.ietf.org/arch/msg/regext/780Xw- 6856 z1RMRb79nmZ6ABmRTo1fU 6858 16.20. Changes REGEXT 07 to REGEXT 08 6860 1. Changes based on the feedback provided here: 6861 https://mailarchive.ietf.org/arch/msg/regext/ 6862 UaMNvl1xh60ldjpqHHYc3TNsfhg 6864 2. Changes based on the feedback provided here: 6865 https://mailarchive.ietf.org/arch/msg/regext/ 6866 B3QTxUCWUE4R_QharAQlA3041j0 6868 16.21. Changes REGEXT 08 to REGEXT 09 6870 1. Changes based on the feedback provided here: 6871 https://mailarchive.ietf.org/arch/msg/regext/ 6872 EmKW32exlPgLbBUIbS8OjdYUJWc 6874 16.22. Changes REGEXT 09 to REGEXT 10 6876 1. Changes based on the feedback provided here: 6877 https://mailarchive.ietf.org/arch/msg/regext/ 6878 tmoKLAV6jhh2zp4JczjeWdr_jJE 6880 2. Changes based on the feedback provided here: 6881 https://mailarchive.ietf.org/arch/msg/regext/m7gyDTjHuRqIQCuKMHF- 6882 OLSS99k 6884 3. Changes based on the feedback provided here: 6885 https://mailarchive.ietf.org/arch/msg/ 6886 regext/3Acx5KHfeUdxZbx6A7zgoZHxIto 6888 4. Changes based on the feedback provided here: 6889 https://mailarchive.ietf.org/arch/msg/ 6890 regext/3Acx5KHfeUdxZbx6A7zgoZHxIto 6892 5. Changes based on the feedback provided here: 6893 https://mailarchive.ietf.org/arch/msg/ 6894 regext/7JiP2fzOr8KCnzI2rwoP-_KlxZY 6896 6. Changes based on the feedback provided here: 6897 https://mailarchive.ietf.org/arch/msg/regext/dbuyW5YTYj4VcFHUQYC- 6898 D8OMv_g 6900 7. Changes based on the feedback provided here: 6901 https://mailarchive.ietf.org/arch/msg/regext/ 6902 ExUZenwC81ZQe9x24-8IKT_FWm8 6904 16.23. Changes REGEXT 10 to REGEXT 11 6906 1. Changes based on the feedback provided here: 6907 https://mailarchive.ietf.org/arch/msg/regext/ 6908 ghEr55r7CVdwUSvkvMGpol4aSh0 6910 17. Example of a Full Deposit using the XML model 6912 Example of a Full Deposit using the XML model: 6914 6915 6931 2019-10-17T00:00:00Z 6932 6933 1.0 6934 urn:ietf:params:xml:ns:rdeHeader-1.0 6935 6936 urn:ietf:params:xml:ns:rdeContact-1.0 6937 6938 urn:ietf:params:xml:ns:rdeHost-1.0 6939 6940 urn:ietf:params:xml:ns:rdeDomain-1.0 6941 6942 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6943 6944 urn:ietf:params:xml:ns:rdeIDN-1.0 6945 6946 urn:ietf:params:xml:ns:rdeNNDN-1.0 6947 6948 urn:ietf:params:xml:ns:rdeEppParams-1.0 6949 6950 6952 6953 6954 6955 6956 test 6957 2 6959 6960 1 6962 6963 1 6965 6966 1 6968 6969 1 6971 6972 1 6974 6975 1 6977 6978 6980 6981 6982 example1.example 6983 Dexample1-TEST 6984 6985 jd1234 6986 sh8013 6987 sh8013 6988 6989 ns1.example.com 6990 ns1.example1.example 6991 6992 RegistrarX 6993 RegistrarX 6994 1999-04-03T22:00:00.0Z 6995 2025-04-03T22:00:00.0Z 6996 6998 6999 7000 example2.example 7001 Dexample2-TEST 7002 7003 7004 jd1234 7005 sh8013 7006 sh8013 7007 RegistrarX 7008 RegistrarX 7009 1999-04-03T22:00:00.0Z 7010 2025-04-03T22:00:00.0Z 7011 7012 7013 7014 ns1.example1.example 7015 Hns1_example_test-TEST 7016 7017 7018 192.0.2.2 7019 192.0.2.29 7020 2001:DB8:1::1 7021 RegistrarX 7022 RegistrarX 7023 1999-05-08T12:10:00.0Z 7024 RegistrarX 7025 2009-10-03T09:34:00.0Z 7026 7028 7029 7030 sh8013 7031 Csh8013-TEST 7032 7033 7034 7035 John Doe 7036 Example Inc. 7037 7038 123 Example Dr. 7039 Suite 100 7040 Dulles 7041 VA 7042 20166-6503 7043 US 7044 7045 7046 +1.7035555555 7047 7048 +1.7035555556 7049 7050 jdoe@example.example 7051 7052 RegistrarX 7053 RegistrarX 7054 7055 2009-09-13T08:01:00.0Z 7056 7057 RegistrarX 7058 7059 2009-11-26T09:10:00.0Z 7060 7061 2009-12-03T09:05:00.0Z 7062 7063 7064 7065 7066 7067 7069 7070 7071 RegistrarX 7072 Registrar X 7073 8 7074 ok 7075 7076 7077 123 Example Dr. 7078 7079 Suite 100 7080 7081 Dulles 7082 VA 7083 20166-6503 7084 US 7085 7086 7087 +1.7035555555 7088 7089 +1.7035555556 7090 7091 jdoe@example.example 7092 7093 http://www.example.example 7094 7095 7096 whois.example.example 7097 7098 http://whois.example.example 7099 7100 7101 2005-04-23T11:49:00.0Z 7102 7103 2009-02-17T17:51:00.0Z 7104 7105 7107 7108 7109 7110 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 7111 7112 7113 http://registro.br/dominio/regras.html 7114 7115 7117 7118 7119 xn--exampl-gva.example 7120 pt-BR 7121 example1.example 7122 withheld 7123 2005-04-23T11:49:00.0Z 7124 7126 7127 7128 1.0 7129 en 7130 7131 urn:ietf:params:xml:ns:domain-1.0 7132 7133 7134 urn:ietf:params:xml:ns:contact-1.0 7135 7136 7137 urn:ietf:params:xml:ns:host-1.0 7138 7139 7140 urn:ietf:params:xml:ns:rgp-1.0 7141 7142 urn:ietf:params:xml:ns:secDNS-1.1 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7165 7166 7168 18. Example of Differential Deposit using the XML model 7170 Example of a Differential Deposit using the XML model: 7172 7173 7188 2019-10-17T00:00:00Z 7189 7190 1.0 7191 urn:ietf:params:xml:ns:rdeHeader-1.0 7192 7193 urn:ietf:params:xml:ns:rdeContact-1.0 7194 7195 urn:ietf:params:xml:ns:rdeHost-1.0 7196 7197 urn:ietf:params:xml:ns:rdeDomain-1.0 7198 7199 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7200 7201 urn:ietf:params:xml:ns:rdeIDN-1.0 7202 7203 urn:ietf:params:xml:ns:rdeNNDN-1.0 7204 7205 urn:ietf:params:xml:ns:rdeEppParams-1.0 7206 7207 7209 7210 7211 7212 example2.example 7213 7214 7216 7217 7218 7219 7220 test 7221 1 7223 7224 1 7226 7227 1 7229 7230 1 7232 7233 1 7235 7236 1 7238 7239 1 7241 7242 7243 7244 7246 19. Example of a Full Deposit using the CSV model 7248 Example of a Full Deposit using the CSV model: 7250 7251 7265 2019-10-18T00:00:00Z 7266 7267 1.0 7268 urn:ietf:params:xml:ns:csvDomain-1.0 7269 urn:ietf:params:xml:ns:csvHost-1.0 7270 urn:ietf:params:xml:ns:csvContact-1.0 7271 urn:ietf:params:xml:ns:csvRegistrar-1.0 7272 urn:ietf:params:xml:ns:csvIDN-1.0 7273 urn:ietf:params:xml:ns:csvNNDN-1.0 7274 urn:ietf:params:xml:ns:rdeEppParams-1.0 7275 7276 7277 7278 test 7279 7280 4 7281 7282 7283 6 7284 7285 7286 9 7287 7288 7289 3 7290 7291 7292 2 7293 7294 7295 2 7296 7297 7298 1 7299 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7322 domain-YYYYMMDD.csv 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7335 domainContacts-YYYYMMDD.csv 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7350 domainStatuses-YYYYMMDD.csv 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7362 domainNameServers-name-YYYYMMDD.csv 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7374 domainNameServers-roid-YYYYMMDD.csv 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7390 dnssec-ds-YYYYMMDD.csv 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7406 dnssec-key-YYYYMMDD.csv 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7425 domainTransfer-YYYYMMDD.csv 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7447 host-YYYYMMDD.csv 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7461 hostStatuses-YYYYMMDD.csv 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7474 hostAddresses-YYYYMMDD.csv 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7500 contact-YYYYMMDD.csv 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7514 contactStatuses-YYYYMMDD.csv 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7535 contactPostal-YYYYMMDD.csv 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7553 contactTransfer-YYYYMMDD.csv 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7574 contactDisclose-YYYYMMDD.csv 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 7600 7601 7602 7603 7604 7606 registrar-YYYYMMDD.csv 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7620 idnLanguage-YYYYMMDD.csv 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7638 NNDN-YYYYMMDD.csv 7639 7640 7641 7642 7643 7644 1.0 7645 en 7646 urn:ietf:params:xml:ns:domain-1.0 7647 7648 urn:ietf:params:xml:ns:host-1.0 7649 7650 urn:ietf:params:xml:ns:contact-1.0 7651 7652 7653 urn:ietf:params:xml:ns:secDNS-1.1 7654 7655 urn:ietf:params:xml:ns:rgp-1.0 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7682 20. Example of Differential Deposit using the CSV model 7684 Example of a Differential Deposit using the CSV model: 7686 7687 7701 2019-10-18T00:00:00Z 7702 7703 1.0 7704 urn:ietf:params:xml:ns:csvDomain-1.0 7705 urn:ietf:params:xml:ns:csvHost-1.0 7706 urn:ietf:params:xml:ns:csvContact-1.0 7707 urn:ietf:params:xml:ns:csvRegistrar-1.0 7708 urn:ietf:params:xml:ns:csvIDN-1.0 7709 7710 7711 7712 7713 7714 7715 7716 7717 7719 domain-delete-YYYYMMDD.csv 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7732 host-delete-YYYYMMDD.csv 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7745 contact-delete-YYYYMMDD.csv 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7758 registrar-delete-YYYYMMDD.csv 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7771 idnLanguage-delete-YYYYMMDD.csv 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7784 NNDN-delete-YYYYMMDD.csv 7785 7786 7787 7788 7789 7790 7791 7792 test 7793 7794 2 7795 7796 7797 2 7798 7799 7800 3 7801 7802 7803 1 7804 7805 7806 1 7807 7808 7809 1 7810 7811 7812 1 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7835 domain-YYYYMMDD.csv 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7848 domainContacts-YYYYMMDD.csv 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7863 domainStatuses-YYYYMMDD.csv 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7875 domainNameServers-name-YYYYMMDD.csv 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7887 domainNameServers-roid-YYYYMMDD.csv 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7903 dnssec-ds-YYYYMMDD.csv 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7919 dnssec-key-YYYYMMDD.csv 7920 7921 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7939 domainTransfer-YYYYMMDD.csv 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7961 host-YYYYMMDD.csv 7962 7963 7964 7965 7966 7967 7968 7969 7970 7972 7973 7974 7976 hostStatuses-YYYYMMDD.csv 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7989 hostAddresses-YYYYMMDD.csv 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8015 contact-YYYYMMDD.csv 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8029 contactStatuses-YYYYMMDD.csv 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8050 contactPostal-YYYYMMDD.csv 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8068 contactTransfer-YYYYMMDD.csv 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8089 contactDisclose-YYYYMMDD.csv 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 8115 8116 8117 8118 8119 8121 registrar-YYYYMMDD.csv 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8135 idnLanguage-YYYYMMDD.csv 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8153 NNDN-YYYYMMDD.csv 8154 8155 8156 8157 8158 8159 1.0 8160 en 8161 urn:ietf:params:xml:ns:domain-1.0 8162 8163 urn:ietf:params:xml:ns:host-1.0 8164 8165 urn:ietf:params:xml:ns:contact-1.0 8166 8167 8168 urn:ietf:params:xml:ns:secDNS-1.1 8169 8170 urn:ietf:params:xml:ns:rgp-1.0 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8194 8195 8197 21. References 8199 21.1. Normative References 8201 [BCP195] Sheffer, Y., Holz, R., and P. Saint-Andre, 8202 "Recommendations for Secure Use of Transport Layer 8203 Security (TLS) and Datagram Transport Layer Security 8204 (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 8205 2015, . 8207 [I-D.ietf-regext-data-escrow] 8208 Lozano, G., "Registry Data Escrow Specification", draft- 8209 ietf-regext-data-escrow-10 (work in progress), June 2020. 8211 [ISO-3166-1] 8212 3166, I. S., "Codes for the representation of names of 8213 countries and their subdivisions -- Part 1: Country 8214 codes", ISO Standard 3166, November 2006. 8216 [ITU-E164] 8217 International Telecommunication Union, "The international 8218 public telecommunication numbering plan", ITU-T 8219 Recommendation E.164, February 2005. 8221 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8222 DOI 10.17487/RFC0791, September 1981, 8223 . 8225 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8226 Requirement Levels", BCP 14, RFC 2119, 8227 DOI 10.17487/RFC2119, March 1997, 8228 . 8230 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8231 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8232 . 8234 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8235 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8236 DOI 10.17487/RFC3915, September 2004, 8237 . 8239 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8240 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8241 . 8243 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8244 Domain Name Mapping", STD 69, RFC 5731, 8245 DOI 10.17487/RFC5731, August 2009, 8246 . 8248 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8249 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8250 August 2009, . 8252 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8253 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8254 August 2009, . 8256 [RFC5891] Klensin, J., "Internationalized Domain Names in 8257 Applications (IDNA): Protocol", RFC 5891, 8258 DOI 10.17487/RFC5891, August 2010, 8259 . 8261 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8262 Security Extensions Mapping for the Extensible 8263 Provisioning Protocol (EPP)", RFC 5910, 8264 DOI 10.17487/RFC5910, May 2010, 8265 . 8267 [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 8268 Address Text Representation", RFC 5952, 8269 DOI 10.17487/RFC5952, August 2010, 8270 . 8272 [RFC6234] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms 8273 (SHA and SHA-based HMAC and HKDF)", RFC 6234, 8274 DOI 10.17487/RFC6234, May 2011, 8275 . 8277 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 8278 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 8279 May 2017, . 8281 [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS 8282 Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, 8283 January 2019, . 8285 [V42] International Telecommunication Union, "V.42 : Error- 8286 correcting procedures for DCEs using asynchronous-to- 8287 synchronous conversion", March 2002, 8288 . 8290 [W3C.REC-xml-20081126] 8291 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 8292 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 8293 Edition) REC-xml-20081126", November 2008, 8294 . 8296 [W3C.REC-xmlschema-1-20041028] 8297 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 8298 "XML Schema Part 1: Structures Second Edition REC- 8299 xmlschema-1-20041028", October 2004, 8300 . 8302 [W3C.REC-xmlschema-2-20041028] 8303 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 8304 Second Edition REC-xmlschema-2-20041028", October 2004, 8305 . 8307 [W3C.REC-xpath-31-20170321] 8308 Robie, J., Dyck, M., and J. Spiegel, "XML Path Language 8309 (XPath) 3.1", March 2017, 8310 . 8312 21.2. Informative References 8314 [ICANN-GTLD-AGB-20120604] 8315 ICANN, "gTLD Applicant Guidebook Version 2012-06-04", June 8316 2012, . 8319 [ICANN-GTLD-RA-20170731] 8320 ICANN, "Base Registry Agreement 2017-07-31", July 2017, 8321 . 8324 [RFC1952] Deutsch, P., "GZIP file format specification version 4.3", 8325 RFC 1952, DOI 10.17487/RFC1952, May 1996, 8326 . 8328 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, 8329 DOI 10.17487/RFC2818, May 2000, 8330 . 8332 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8333 DOI 10.17487/RFC3688, January 2004, 8334 . 8336 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8337 DOI 10.17487/RFC3912, September 2004, 8338 . 8340 [RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma- 8341 Separated Values (CSV) Files", RFC 4180, 8342 DOI 10.17487/RFC4180, October 2005, 8343 . 8345 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8346 Code: The Implementation Status Section", BCP 205, 8347 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8348 . 8350 [variantTLDsReport] 8351 Internet Corporation for Assigned Names and Numbers 8352 (ICANN), "A Study of Issues Related to the Management of 8353 IDN Variant TLDs", February 2012, 8354 . 8357 Authors' Addresses 8359 Gustavo Lozano 8360 Internet Corporation for Assigned Names and Numbers 8361 12025 Waterfront Drive, Suite 300 8362 Los Angeles 90292 8363 United States of America 8365 Phone: +1.310.823.9358 8366 Email: gustavo.lozano@icann.org 8368 James Gould 8369 VeriSign, Inc. 8370 12061 Bluemont Way 8371 Reston 20190 8372 United States of America 8374 Email: jgould@verisign.com 8376 Chethan Thippeswamy 8377 VeriSign, Inc. 8378 12061 Bluemont Way 8379 Reston 20190 8380 United States of America 8382 Email: cthippeswamy@verisign.com