idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-09.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 (Aug 12, 2020) is 1353 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' ** Obsolete normative reference: RFC 8499 (Obsoleted by RFC 9499) -- Possible downref: Non-RFC (?) normative reference: ref. 'V42' -- Obsolete informational reference (is this intentional?): RFC 7525 (Obsoleted by RFC 9325) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track J. Gould 5 Expires: February 13, 2021 C. Thippeswamy 6 VeriSign 7 Aug 12, 2020 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-09 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 February 13, 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 . . . . . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . . . . . . 7 61 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 7 62 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 8 63 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 8 64 4.6. Conventions applicable to the CSV Model . . . . . . . . . 8 65 5. Object Description . . . . . . . . . . . . . . . . . . . . . 16 66 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 16 67 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 35 68 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 45 69 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 63 70 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 71 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 . . . . . . . . . . . . . . . . . . . . . 88 81 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 97 82 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 99 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 . . . . . . . . . . . . . . . . . . . 109 87 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 115 88 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 118 89 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 121 90 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 122 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 . . . . . . . . . . . . . . . . . . . . . . 129 96 9.17. DNRD Common Objects . . . . . . . . . . . . . . . . . . . 131 97 10. Internationalization Considerations . . . . . . . . . . . . . 131 98 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 131 99 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 139 100 12.1. Implementation in the gTLD space . . . . . . . . . . . . 140 101 13. Security Considerations . . . . . . . . . . . . . . . . . . . 140 102 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 141 103 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 141 104 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 142 105 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 106 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 142 107 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 142 108 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 142 109 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 143 110 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 143 111 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 144 112 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 145 113 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 145 114 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 146 115 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 146 116 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 146 117 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 146 118 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 146 119 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 146 120 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 148 121 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 148 122 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 149 123 16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 149 124 16.19. Changes REGEXT 06 to REGEXT 07 . . . . . . . . . . . . . 149 125 16.20. Changes REGEXT 07 to REGEXT 08 . . . . . . . . . . . . . 149 126 16.21. Changes REGEXT 08 to REGEXT 09 . . . . . . . . . . . . . 150 127 17. Example of a Full Deposit using the XML model . . . . . . . . 150 128 18. Example of Differential Deposit using the XML model . . . . . 155 129 19. Example of a Full Deposit using the CSV model . . . . . . . . 157 130 20. Example of Differential Deposit using the CSV model . . . . . 166 131 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 176 132 21.1. Normative References . . . . . . . . . . . . . . . . . . 177 133 21.2. Informative References . . . . . . . . . . . . . . . . . 179 134 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 180 136 1. Introduction 138 Registry Data Escrow is the process by which a registry periodically 139 submits data deposits to a third-party called an escrow agent. These 140 deposits comprise the minimum data needed by a third-party to resume 141 operations if the registry cannot function and is unable or unwilling 142 to facilitate an orderly transfer of service. For example, for a 143 domain name registry or registrar, the data to be deposited would 144 include all the objects related to registered domain names, e.g., 145 names, contacts, name servers, etc. 147 The goal of data escrow is higher resiliency of registration 148 services, for the benefit of Internet users. The beneficiaries of a 149 registry are not just those registering information there, but also 150 the users of services relying on the registry data. 152 In the context of domain name registries, registration data escrow is 153 a requirement for generic top-level domains (e.g., Specification 2 of 154 the ICANN Base Registry Agreement, see [ICANN-GTLD-RA-20170731]) and 155 some country code top-level domain managers are also currently 156 escrowing data. There is also a similar requirement for ICANN- 157 accredited domain registrars. 159 This document defines the standard set of objects for a Domain Name 160 Registry that uses the Registry Data Escrow Specification described 161 in [I-D.ietf-regext-data-escrow] for escrow. The set of objects 162 include: 164 o Domain: Internet domain names that are typically provisioned in a 165 Domain Name Registry using the EPP domain name mapping [RFC5731]. 166 The attributes defined in the EPP domain name mapping [RFC5731] 167 are fully supported by this document. 169 o Host: Internet host names that are typically provisioned in a 170 Domain Name Registry using the EPP host mapping [RFC5732]. The 171 attributes defined in the EPP host mapping [RFC5732] are fully 172 supported by this document. 174 o Contact: Individual or organization social information provisioned 175 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 176 The attributes defined in the EPP contact mapping [RFC5733] are 177 fully supported by this document. 179 o Registrar: The organization that sponsors objects like domains, 180 hosts, and contacts in a Domain Name Registry. 182 o NNDN (NNDN's not domain name): Domain Name Registries may maintain 183 domain names without being persisted as domain objects in the 184 registry system, for example, a list of reserved names not 185 available for registration. The NNDN is a lightweight domain-like 186 object that is used to escrow domain names not maintained as 187 domain name objects. 189 This document defines the following pseudo-objects: 191 o IDN Table Reference: Internationalized Domain Names (IDN) included 192 in the Domain Object Data Escrow include references to the IDN 193 Table and Policy used in IDN registration. 195 o EPP parameters: Definition of the specific EPP parameters 196 supported by the Registry Operator. 198 o Header: Used to specify counters of objects in the database at a 199 certain point in time (watermark). 201 o Policy: Used to specify OPTIONAL elements from this specification 202 that are REQUIRED based on the business model of the registry. 204 Extensible Markup Language (XML) 1.0 as described in 205 [W3C.REC-xml-20081126] and XML Schema notation as described in 206 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028] are 207 used in this specification. 209 2. Models 211 This document defines two different models that can be used to 212 deposit data escrow objects: XML and CSV. 214 The data escrow deposit MAY contain a mix of both models but an 215 object MUST be escrowed only in one model. 217 This document does not suggest the use of a particular model, and 218 both are equivalent. A Domain Name Registry may choose the model 219 that is more appropriate for the peculiarities of its systems. For 220 example, a registry may use the CSV-export functionality of the 221 Relational Database Management System (RDBMS) for escrow; therefore, 222 the CSV model may be more appropriate. Another registry may use the 223 code developed for EPP to implement escrow. 225 2.1. XML Model 227 XML: The XML model includes all the deposit information (meta-data 228 and data) in an XML document. The definition of the XML format is 229 fully defined in the XML schemas. As a convention, the objects 230 represented using the XML model are referenced using RDE and an XML 231 namespace that is prefixed with "rde". For example, the Domain Name 232 object represented using the XML model can be referred to as the RDE 233 Domain Name with the XML namespace including rdeDomain 234 (urn:ietf:params:xml:ns:rdeDomain-1.0). 236 2.2. CSV Model 238 CSV: The CSV model uses XML to define the data escrow format of the 239 data contained in referenced Comma-Separated Values (CSV) files. As 240 a convention, the objects represented using the CSV model is 241 referenced using CSV and an XML namespace that is prefixed with 242 "csv". For example, the Domain Name object represented using the CSV 243 model can be referred to as the CSV Domain Name with the XML 244 namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). 246 3. Terminology 248 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 249 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 250 "OPTIONAL" in this document are to be interpreted as described in BCP 251 14 [RFC2119] [RFC8174] when, and only when, they appear in all 252 capitals, as shown here. 254 3.1. Glossary 256 In the following section, the most common terms are briefly 257 explained: 259 o Allocated: a status of some label with respect to a zone, whereby 260 the label is associated administratively to some entity that has 261 requested the label. This term (and its cognates "allocation" and 262 "to allocate") may represent the first step on the way to 263 delegation in the DNS. 265 o Comma-Separated Values (CSV), see [RFC4180]. 267 o Domain name: see definition of Domain name in [RFC8499]. 269 o Extensible Provisioning Protocol (EPP), see definition of the 270 Extensible Provisioning Protocol in [RFC8499]. 272 o Fully-Qualified Domain Name (FQDN), see definition of FQDN in 273 [RFC8499]. 275 o Internationalized Domain Name (IDN), see definition of 276 Internationalized Domain Name in [RFC8499]. 278 o Label: see definition of Label in [RFC8499]. 280 o Registrant: see definition of Registrant in [RFC8499]. 282 o Registrar: see definition of Registrar in [RFC8499]. 284 o Registry: see definition of Registry in [RFC8499]. 286 o Registry-class domain name (RCDN): refers to a top-level domain 287 (TLD) or any other domain name at any level in the DNS tree for 288 which a Registry (either directly or through an affiliate company) 289 provides Registry Services for other organizations or individuals. 290 For example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 292 o Registry Data Escrow (RDE): registry data escrow is the process by 293 which a registry periodically submits data deposits to a third- 294 party called an escrow agent. These deposits comprise the minimum 295 data needed by a third-party to resume operations if the registry 296 cannot function and is unable or unwilling to facilitate an 297 orderly transfer of service. 299 o Registry services: services offered by the Registry critical to 300 the following tasks: the provisioning of domain names on receipt 301 of requests and data from registrars; responding to registrar 302 queries for status information relating to the DNS servers for the 303 RCDN; dissemination of RCDN zone files; operation of the Registry 304 DNS servers; responding to queries for contact and other 305 information concerning DNS registrations in the RCDN; and any 306 other products or services that only a Registry is capable of 307 providing, by reason of its designation as the Registry. Typical 308 examples of Registry Services are DNS resolution for the RCDN, 309 WHOIS and EPP. 311 o SRS: Shared Registration System, see also 312 [ICANN-GTLD-AGB-20120604]. 314 o Top-Level Domain Name (TLD), see definition of Top-Level Domain in 315 [RFC8499]. 317 o UTC: Coordinated Universal Time, as maintained by the Bureau 318 International des Poids et Mesures (BIPM); see also [RFC3339]. 320 4. Conventions Used in This Document 322 4.1. Date and Time 324 Numerous fields indicate "dates", such as the creation and expiry 325 dates for domain names. These fields SHALL contain timestamps 326 indicating the date and time in UTC as specified in [RFC3339], with 327 no offset from the zero meridian. 329 4.2. Country names 331 Country identifiers SHALL be represented using two character 332 identifiers as specified in [ISO-3166-1]. 334 4.3. Telephone numbers 336 Telephone numbers (both voice and facsimile) SHALL be formatted based 337 on structures defined in [ITU-E164]. Telephone numbers described in 338 this specification are character strings that MUST begin with a plus 339 sign ("+", ASCII value 0x002B), followed by a country code defined in 341 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 342 a sequence of digits representing the telephone number. 344 4.4. Checksum 346 A checksum MAY be used to verify the integrity of the CSV files, for 347 example, if another layer (i.e., encryption of an archive containing 348 the deposit files) does not provide integrity. By default the CRC32 349 algorithm (see, 8.1.1.6.2 of [V42]) is used. A stronger algorithm, 350 such as SHA-256 (see, [RFC6234]) MAY be specified for enhanced 351 security if required. 353 4.5. IP addresses 355 The syntax of IP addresses MUST conform to the text representation of 356 either Internet Protocol Version 4 [RFC0791] or Internet Protocol 357 Version 6 [RFC4291]. 359 4.6. Conventions applicable to the CSV Model 361 4.6.1. CSV Parent Child Relationship 363 The CSV model represents a relational model, where the CSV files 364 represent relational tables, the fields of the CSV files represent 365 columns of the tables, and each line of the CSV file represents a 366 record. As in a relational model, the CSV files can have 367 relationships utilizing primary keys in the parent CSV file 368 definitions and foreign keys in the child CSV file definitions for a 369 1-to-many relationship. The primary keys are not explicitly defined, 370 but the foreign keys are using the boolean "parent" field attribute 371 in the child CSV file. The relationships between the CSV files are 372 used to support a cascade replace or cascade delete of records 373 starting from the parent record in Differential and Incremental 374 Deposits (see [I-D.ietf-regext-data-escrow]). 376 The following is an example of the CSV file definitions for a Sample 377 object consisting of a parent "sample" CSV File Definition and a 378 child "sampleStatuses" CSV File Definition. The primary key for the 379 Sample object is the field that is used as the 380 foreign key in the "sampleStatuses" CSV File Definition by specifying 381 the "parent=true" attribute. If a Sample record is updated or 382 deleted in a Differential or Incremental Deposit, it should cascade 383 replace the data using the records included in the child 384 "sampleStatuses" CSV File Definition or cascade delete the existing 385 records in the child "sampleStatuses" CSV File Definition, 386 respectively. 388 389 ... 390 391 392 393 394 395 396 397 398 399 400 401 402 403 405 sample-YYYYMMDD.csv 406 407 408 409 410 411 412 413 414 415 416 417 419 sampleStatuses-YYYYMMDD.csv 420 421 422 423 ... 424 426 4.6.2. CSV elements 428 4.6.2.1. element 430 To support the CSV model, an element is defined for each object that 431 substitutes for the element and for the 432 element, that contains one or more elements. For 433 example, the Domain Name Object (Section 5.1) defines the 434 element, that substitutes for the 435 element, and the element, that substitutes for 436 the element. Both the element and 437 the elements contain one or more 438 elements. The element has the following child elements: 440 Ordered list of CSV fields used in the CSV files. 441 There are one or more child elements that substitute for the 442 abstract element. Each element defines the format 443 of the CSV field contained in the CSV files. The 444 elements support the "type" attribute that defines the XML simple 445 data type of the field element. The elements 446 support the "isRequired" attribute, with a default value of 447 "false", when set to "true" indicates that the field must be non- 448 empty in the CSV files and when set to "false" indicates that the 449 field MAY be empty in the CSV files. The "isRequired" attribute 450 MAY be specifically set for the field elements within the XML 451 schema and MAY be overridden when specifying the fields under the 452 element. The element supports an 453 OPTIONAL "parent" attribute that identifies the field as a 454 reference to a parent object, as defined in CSV Parent Child 455 Relationship (Section 4.6.1). For example, the field SHOULD set the 457 "parent" attribute to "true" to identify it as the parent domain 458 name of the domain status. 460 A list of one or more CSV files using the 461 child element. The child element 462 defines a reference to the CSV file name and has the following 463 optional attributes: 465 compression If the CSV file is compressed, the "compression" 466 attribute defines the compression format. For example, setting 467 this attribute to "gzip" signals that the CSV file is 468 compressed using the GZIP file format (see, [RFC1952]). The 469 supported compression formats are negotiated out-of-band. 471 encoding Defines the encoding of the CSV file with the default 472 encoding of "UTF-8". 474 cksum Defines the checksum of the CSV file, as described in 475 Section 4.4, using the algorithm defined by the "cksumAlg" 476 attribute. If the "cksumAlg" attribute is not present, the 477 checksum is calculated using "CRC32". 479 cksumAlg Defines the checksum algorithm used to calculate the 480 "cksum" attribute, with the default value of "CRC32". If this 481 attribute is present, the "cksum" attribute MUST also be 482 present. The supported checksum algorithms are negotiated out- 483 of-band. 485 The element requires a "name" attribute that defines the 486 purpose of the CSV file with values like "domain", "host", "contact". 487 The supported "name" attribute values are defined for each object 488 type. The OPTIONAL "sep" attribute defines the CSV separator 489 character with the default separator character of ",". 491 The following is an example of the 492 element for domain name records where the is set 493 as required with isRequired="true". 495 496 ... 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 516 domain-YYYYMMDD.csv 517 518 519 520 ... 521 523 The following is example of the "domain-YYYYMMDD.csv" file with one 524 record matching the definition. 526 domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 527 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 528 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 529 The following is an example of the 530 element for domain name records. 532 533 ... 534 535 536 537 538 539 541 domain-delete-YYYYMMDD.csv 542 543 544 545 ... 546 548 The following is example of the "domain-delete-YYYYMMDD.csv" file 549 with three records that matches the single field. 551 domain1.example 552 domain2.example 553 domainN.example 555 4.6.2.2. CSV common field elements 557 The element defined in the element 558 (Section 4.6.2.1) section has child elements that substitute for the 559 abstract element. By convention 560 elements include an 'f' prefix to identify them as field definition 561 elements. There are a set of common field elements that are used 562 across multiple data escrow objects. The common field elements are 563 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 564 using the "rdeCsv" sample namespace prefix. The CSV common field 565 elements include: 567 UTF-8 encoded name field with 568 type="eppcom:labelType". 570 Repository Object IDentifier (ROID) field with 571 type="eppcom:roidType" and isRequired="true". 573 Registrant contact identifier with 574 type="eppcom:clIDType". 576 The object status description, which is 577 free form text describing the rationale for the status, with 578 type="normalizedString". 580 Identifier of the client (registrar) that sponsors 581 the object with type="eppcom:clIDType" and isRequired="true". 583 Identifier of the registrar, defined in Section 5.4, 584 of the client that created the object with type="eppcom:clIDType". 586 Identifier of the client that created the object with 587 type="eppcom:clIDType". 589 Identifier of the registrar, defined in Section 5.4, 590 of the client that updated the object with type="eppcom:clIDType". 592 Identifier of the client that updated the object with 593 type="eppcom:clIDType". 595 Identifier of the registrar, defined in Section 5.4, 596 of the client that requested the transfer with 597 type="eppcom:clIDType" and isRequired="true". 599 Identifier of the client that requested the transfer 600 with type="eppcom:clIDType". 602 Identifier of the registrar, defined in Section 5.4, 603 of the client that should take or took action with 604 type="eppcom:clIDType" and isRequired="true". 606 Identifier of the client that should take or took 607 action for transfer with type="eppcom:clIDType". 609 Created date of object with type="dateTime". 611 Updated date of object with type="dateTime". 613 Expiration date of object with type="dateTime". 615 Date that transfer was requested with 616 type="dateTime" and isRequired="true". 618 Date that transfer action should be taken or has 619 been taken with type="dateTime" and isRequired="true". 621 Date of last transfer with type="dateTime". 623 State of the most recent transfer request with 624 type="eppcom:trStatusType" and isRequired="true". 626 General token field with type="token". 628 General language field with type="language". 630 IDN Table Identifier used for IDN domain names 631 with type="token". 633 General positive integer field with 634 type="positiveInteger". 636 Contains the URL of an object like a registrar object 637 with type="anyURI". 639 Custom field with name attribute that defines the 640 custom field name" with type="token". 642 4.6.3. Internationalized and Localized Elements 644 Some elements MAY be provided in either internationalized form 645 ("int") or localized form ("loc"). Those elements use a field value 646 or "isLoc" attribute to specify the form used. If an "isLoc" 647 attribute is used, a value of "true" indicates the use of the 648 localized form and a value of "false" indicates the use of the 649 internationalized form. This MAY override the form specified for a 650 parent element. A value of "int" is used to indicate the 651 internationalized form and a value of "loc" is used to indicate the 652 localized form. When the internalized form ("int") is provided, the 653 field value MUST be represented in a subset of UTF-8 that can be 654 represented in the 7-bit US-ASCII character set. When the localized 655 form ("loc") is provided, the field value MAY be represented in 656 unrestricted UTF-8. 658 The field elements below of the "registrar" 659 element specify the internationalized form with the 660 isLoc="false" attribute. 662 ... 663 664 ... 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 696 registrar-YYYYMMDD.csv 697 698 699 700 ... 701 702 ... 704 The following is an example of using the 705 field value to define the internationalized or localized form of the 706 remainder of the "contactPostal" field values. 708 ... 709 710 ... 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 728 contactPostal-YYYYMMDD.csv 729 730 731 732 ... 733 734 ... 736 5. Object Description 738 This section describes the base objects supported by this 739 specification: 741 5.1. Domain Name Object 743 The domain name object is based on the EPP domain name mapping 744 specified in [RFC5731]. The domain name object supports both the XML 745 Model and the CSV Model, defined in the Models (Section 2) section. 746 The elements used for both models are defined in the following 747 sections. 749 5.1.1. XML Model 751 There are two elements used in the data escrow of the domain name 752 objects for the XML model including the , under the 753 element, and the element, under the 754 element. 756 5.1.1.1. object 758 The domain element is based on the EPP domain response for an 759 authorized client (see Section 3.1.2. of [RFC5731]) with additional 760 data from an EPP Query Response, see Section 3.1.3. of 761 [RFC5731], Registry Grace Period (RGP) status from [RFC3915], and 762 data from the EPP command, see Section 5.2.1. of 763 [RFC5910]. 765 A element substitutes for the abstract 766 element to define a concrete definition of a domain. The 767 element can be replaced by other domain definitions 768 using the XML schema substitution groups feature. 770 The element contains the following child elements: 772 o A element that contains the fully-qualified name of the 773 domain name object. For IDNs the A-Label is used (see [RFC5891], 774 Section 4.4). 776 o A element that contains the repository object identifier 777 assigned to the domain name object when it was created. 779 o An OPTIONAL element that contains the fully-qualified 780 domain name in Unicode character set. It MUST be provided if 781 available. 783 o An OPTIONAL element that references the IDN 784 Table used for the IDN. This corresponds to the "id" attribute of 785 the element. This element MUST be present if the 786 domain name is an IDN. 788 o An OPTIONAL element is used to indicate that the 789 domain name is an IDN variant. This element contains the domain 790 name used to generate the IDN variant. 792 o One or more elements that contain the current status 793 descriptors associated with the domain name. 795 o Zero or more OPTIONAL elements to represent 796 "pendingDelete" sub-statuses, including "redemptionPeriod", 797 "pendingRestore", and "pendingDelete", that a domain name can be 798 in as a result of grace period processing as specified in 799 [RFC3915]. 801 o An OPTIONAL element that contains the identifier for 802 the human or organizational social information object associated 803 as the holder of the domain name object. 805 o Zero or more OPTIONAL elements that contain identifiers 806 for the human or organizational social information objects 807 associated with the domain name object. 809 o An OPTIONAL element that contains the fully-qualified names 810 of the delegated host objects or host attributes (name servers) 811 associated with the domain name object. See Section 1.1 of 812 [RFC5731] for a description of the elements used to specify host 813 objects or host attributes. 815 o A element that contains the identifier of the sponsoring 816 registrar. 818 o An OPTIONAL element that contains the identifier of the 819 registrar that created the domain name object. An OPTIONAL client 820 attribute is used to specify the client that performed the 821 operation. 823 o An OPTIONAL element that contains the date and time of 824 the domain name object creation. This element MUST be present if 825 the domain name has been allocated. 827 o An OPTIONAL element that contains the date and time 828 identifying the end (expiration) of the domain name object's 829 registration period. This element MUST be present if the domain 830 name has been allocated. 832 o An OPTIONAL element that contains the identifier of the 833 registrar that last updated the domain name object. This element 834 MUST NOT be present if the domain has never been modified. An 835 OPTIONAL client attribute is used to specify the client that 836 performed the operation. 838 o An OPTIONAL element that contains the date and time of 839 the most recent domain-name-object modification. This element 840 MUST NOT be present if the domain name object has never been 841 modified. 843 o An OPTIONAL element that contains the public key 844 information associated with Domain Name System security (DNSSEC) 845 extensions for the domain name as specified in [RFC5910]. 847 o An OPTIONAL element that contains the date and time of 848 the most recent domain object successful transfer. This element 849 MUST NOT be present if the domain name object has never been 850 transferred. 852 o An OPTIONAL element that contains the following child 853 elements related to the last transfer request of the domain name 854 object. This element MUST NOT be present if a transfer request 855 for the domain name has never been created. 857 * A element that contains the state of the most recent 858 transfer request. 860 * A element that contains the identifier of the registrar 861 that requested the domain name object transfer. An OPTIONAL 862 client attribute is used to specify the client that performed 863 the operation. 865 * A element that contains the date and time that the 866 transfer was requested. 868 * An element that contains the identifier of the registrar 869 that should act upon a PENDING transfer request. For all other 870 status types, the value identifies the registrar that took the 871 indicated action. An OPTIONAL client attribute is used to 872 specify the client that performed the operation. 874 * An element that contains the date and time of a 875 required or completed response. For a PENDING request, the 876 value identifies the date and time by which a response is 877 required before an automated response action will be taken by 878 the registry. For all other status types, the value identifies 879 the date and time when the request was completed. 881 * An OPTIONAL element that contains the end of the 882 domain name object's validity period (expiry date) if the 883 transfer caused or causes a change in the validity period. 885 Example of a domain object: 887 ... 888 889 xn--exampl-gva.example 890 Dexample1-TEST 891 pt-BR 892 example.example 893 894 jd1234 895 sh8013 896 sh8013 897 898 ns1.example.com 899 ns1.example1.example 900 901 RegistrarX 902 RegistrarX 903 1999-04-03T22:00:00.0Z 904 2015-04-03T22:00:00.0Z 905 906 ... 908 5.1.1.2. object 910 The element contains the fully-qualified domain 911 name that was deleted and purged. 913 Example of object: 915 ... 916 917 ... 918 919 foo.example 920 bar.example 921 922 ... 923 924 ... 926 5.1.2. CSV Model 928 For the CSV Model of the domain name object, the 929 child element of the element is used to hold the new 930 or updated domain name objects for the deposit. The 931 child element of the element is 932 used to hold the deleted or purged domain name objects for the 933 deposit. Both the and 934 elements contain one or more elements with a set of 935 named CSV file definitions using the "name" attribute. 937 Differential and Incremental Deposits are based on changes to the 938 domain name objects. The updated domain name object data under the 939 element is a cascade replace down all of the 940 domain name CSV files starting with the parent "domain" CSV File 941 Definition (Section 5.1.2.1.1). The child CSV file definitions 942 include a field. All the child CSV 943 file definition data for the domain name objects in the parent 944 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 945 deleted and then set using the data in the child CSV files. The 946 deleted domain name object data under the element 947 is a cascade delete starting from the "domain" Deletes CSV File 948 Definition (Section 5.1.2.2.1). 950 5.1.2.1. 952 The is used to hold the new or updated domain 953 name object information for the deposit. The is 954 split into separate CSV file definitions using named 955 elements with the "name" attribute. The following sections include 956 the supported domain name CSV file definitions: 958 5.1.2.1.1. "domain" CSV File Definition 960 The "domain" CSV File Definition defines the fields and CSV file 961 references used for the parent domain name object records. All the 962 other domain name CSV file definitions are child CSV files based on 963 the inclusion of the field. 965 The following "csvDomain" field elements MUST be used in the "domain" 966 element: 968 Domain name field with type="eppcom:labelType" and 969 isRequired="true". 971 The following "csvDomain" field elements MAY be used in the "domain" 972 element: 974 Fully-qualified name of the original IDN 975 domain name object related to the variant domain name object with 976 type="eppcom:labelType". 978 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 979 "domain" element: 981 Registry Object IDentifier (ROID) for the domain name 982 object with isRequired="true". 984 or A choice of: 986 Identifier of the sponsoring client with 987 isRequired="true". 989 Contains the ID assigned by ICANN with 990 type="positiveInteger". The attribute "isRequired" MUST equal 991 "true". 993 The following "rdeCsv" fields, defined in section CSV common field 994 elements (Section 4.6.2.2), MAY be used in the "domain" 995 element: 997 Identifier of the registrar, defined in Section 5.4, 998 of the client that created the object. 1000 Identifier of the client that created the domain name 1001 object. 1003 Identifier of the registrar, defined in Section 5.4, 1004 of the client that updated the object. 1006 Identifier of the client that last updated the domain 1007 name object. 1009 UTF8 encoded domain name for the 1010 field element. 1012 IDN Table Identifier used for the IDN domain 1013 name object that MUST match a field element 1014 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 1016 Registrant contact identifier for the domain 1017 name object. 1019 Created date and time of the domain name object. 1021 Date and time of the last update to the domain name 1022 object. 1024 Expiration date and time for the domain name 1025 object. 1027 Date and time of the last transfer for the domain 1028 name object. 1030 Example of a "domain" element. 1032 ... 1033 1034 ... 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1054 domain-YYYYMMDD.csv 1055 1056 1057 1058 ... 1059 1060 ... 1062 Example of the corresponding domain-YYYYMMDD.csv file. The file 1063 contains four records (two active ASCII domains, original IDN with 1064 LANG-1 language rules, and variant IDN with LANG-1 language rules). 1066 domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 1067 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1068 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1069 domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 1070 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 1071 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1072 xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 1073 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1074 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1075 xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example, 1076 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 1077 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1079 5.1.2.1.2. "domainContacts" CSV File Definition 1081 The "domainContacts" CSV File Definition defines the fields and CSV 1082 file references used for the domain name object link records to 1083 contact objects, as described in Contact Object (Section 5.3). 1085 The following "csvDomain" field elements, defined for the "domain" 1086 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 1087 "domainContacts" element: 1089 The name of the domain object that is linked to 1090 the contact object with isRequired="true". 1092 The contact type for the contact object 1093 link with type="domain:contactAttrType" and isRequired="true". 1094 The supported contact type values include "admin" for the 1095 administration contact, "billing" for the billing contact, and 1096 "tech" for the technical contact. 1098 The following "csvContact" fields, defined for the "contact" CSV File 1099 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 1100 element: 1102 The server-unique contact identifier with 1103 isRequired="true". 1105 Example of a "domainContacts" 1106 element. 1108 ... 1109 1110 ... 1111 1112 1113 1114 1115 1116 1117 1118 1120 domainContacts-YYYYMMDD.csv 1121 1122 1123 1124 ... 1125 1126 ... 1128 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1129 file contains an admin, tech, and billing contact for the four domain 1130 names domain1.example, domain2.example, xn--bc123-3ve.example and 1131 xn--bc321-3ve.example. 1133 domain1.example,domain1admin,admin 1134 domain1.example,domain1tech,tech 1135 domain1.example,domain1billing,billing 1136 domain2.example,domain2admin,admin 1137 domain2.example,domain2tech,tech 1138 domain2.example,domain2billing,billing 1139 xn--bc123-3ve.example,xnabc123admin,admin 1140 xn--bc123-3ve.example,xnabc123tech,tech 1141 xn--bc123-3ve.example,xnabc123billing,billing 1142 xn--bc321-3ve.example,xnabc123admin,admin 1143 xn--bc321-3ve.example,xnabc123tech,tech 1144 xn--bc321-3ve.example,xnabc123billing,billing 1146 5.1.2.1.3. "domainStatuses" CSV File Definition 1148 The "domainStatuses" CSV File Definition defines the fields and CSV 1149 file references used for the domain name object statuses. 1151 The following "csvDomain" fields, defined for the "domain" CSV File 1152 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1153 element: 1155 Domain name of status with isRequired="true". 1157 The status of the domain name with 1158 type="domain:statusValueType" and isRequired="true". 1160 The RGP status, as a sub-status of the 1161 "pendingDelete" status value, with 1162 type="rgp:statusValueType" as defined in [RFC3915]. 1164 The following "rdeCsv" fields, defined in section CSV common field 1165 elements (Section 4.6.2.2), MAY be used in the "domainStatuses" 1166 element: 1168 Domain object status description which 1169 is free form text describing the rationale for the status. 1171 Language of the field. 1173 Example of a "domainStatuses" 1174 element. 1176 ... 1177 1178 ... 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1190 domainStatuses-YYYYMMDD.csv 1191 1192 1193 1194 ... 1195 1196 ... 1198 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1199 file contains the statuses for the four domain names domain1.example, 1200 domain2.example, xn--bc123-3ve.example and xn--bc321-3ve.example. 1202 domain1.example,clientUpdateProhibited,"Disallow update", 1203 en, 1204 domain1.example,clientDeleteProhibited,"Disallow delete", 1205 en, 1206 domain2.example,ok,,, 1207 xn--bc123-3ve.example,ok,,, 1208 xn--bc321-3ve.example,ok,,, 1210 5.1.2.1.4. "domainNameServers" CSV File Definition 1212 The "domainNameServers" CSV File Definition defines the fields and 1213 CSV file references used for the domain name delegated hosts (name 1214 servers). The "domainNameServers" CSV files define the relationship 1215 between a domain name object and a delegated host. The 1216 "domainNameServers" CSV File is used to support the 1217 model, defined in [RFC5731]. 1219 The following "csvDomain" fields, defined for the "domain" CSV File 1220 Definition (Section 5.1.2.1.1), MUST be used in the 1221 "domainNameServers" element: 1223 Domain name using the delegated host with 1224 isRequired="true". 1226 The following "csvHost" and "rdeCsv" field elements MUST be used in 1227 the "domainNameServers" element: 1229 or A choice of: 1231 Host name field with type="eppcom:labelType" and 1232 isRequired="true". 1234 Host object Registry Object IDentifier (ROID) 1235 assigned to the host object with isRequired="true". 1237 Example of a "domainNameServers" 1238 element. 1240 ... 1241 1242 ... 1243 1244 1245 1246 1247 1248 1249 1251 domainNameServers-YYYYMMDD.csv 1252 1253 1254 1255 ... 1256 1257 ... 1259 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1260 The file contains the delegated hosts (name servers) for the four 1261 domain names domain1.example, domain2.example, xn--bc123-3ve.example 1262 and xn--bc321-3ve.example referenced via the field 1263 element. 1265 domain1.example,Hns1_domain1_test-TEST 1266 domain1.example,Hns2_domain1_test-TEST 1267 domain2.example,Hns1_domain2_test-TEST 1268 domain2.example,Hns2_domain2_test-TEST 1269 xn--bc123-3ve.example,Hns1_example_test-TEST 1270 xn--bc123-3ve.example,Hns2_example_test-TEST 1271 xn--bc321-3ve.example,Hns1_example_test-TEST 1272 xn--bc321-3ve.example,Hns2_example_test-TEST 1274 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1276 The "domainNameServersAddresses" CSV File Definition defines the 1277 fields and CSV file references used for supporting the host as domain 1278 attributes model. 1280 The following "csvDomain" fields, defined for the "domain" CSV File 1281 Definition (Section 5.1.2.1.1), MUST be used in the 1282 "domainNameServersAddresses" element: 1284 Domain name using the delegated host with host 1285 and isRequired="true". 1287 The following "rdeCsv" fields, defined in section Host CSV model 1288 elements (Section 5.2.2), MUST be used in the 1289 "domainNameServersAddresses" element: 1291 Host name field with type="eppcom:labelType" and 1292 isRequired="true". 1294 The following "csvHost" fields, defined in section Host CSV model 1295 elements (Section 5.2.2), MAY be used in the 1296 "domainNameServersAddresses" element: 1298 IP addresses associated with the host object with 1299 type="host:addrStringType". 1301 IP addresses version associated with the host 1302 object with type="host:ipType". "host:ipType" has the enumerated 1303 values of "v4" or "v6". 1305 Example of a "domainNameServersAddresses" 1306 element. 1308 ... 1309 1310 ... 1311 1312 1313 1314 1315 1316 1317 1318 1319 1321 domainNameServersAddresses-YYYYMMDD.csv 1322 1323 1324 1325 ... 1326 1327 ... 1329 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1330 file. The file contains the delegated hosts (name servers) for the 1331 four domain names domain1.example, domain2.example, xn-- 1332 bc123-3ve.example and xn--bc321-3ve.example. 1334 domain1.example,ns1.domain1.example,192.0.2.1,v4 1335 domain1.example,ns2.domain1.example,2001:DB8::1,v6 1336 domain2.example,ns1.example.net,, 1337 domain2.example,ns2.example.net,, 1338 xn--bc123-3ve.example,ns1.example.net,, 1339 xn--bc123-3ve.example,ns2.example.net,, 1340 xn--bc321-3ve.example,ns1.example.net,, 1341 xn--bc321-3ve.example,ns2.example.net,, 1343 5.1.2.1.6. "dnssec" CSV File Definition 1345 The "dnssec" CSV File Definition defines the fields and CSV file 1346 references used for the domain name object DNSSEC records (DS or Key 1347 Data). 1349 The following "csvDomain" field elements MUST be used in the "dnssec" 1350 element when the DS Data Interface per 1351 [RFC5910] is used: 1353 Contains the DS key tag value per [RFC5910] with 1354 type="unsignedShort" and isRequired="true". 1356 Contains the DS algorithm value per [RFC5910] 1357 with type="unsignedByte" and isRequired="true". 1359 Contains the DS digest type value per 1360 [RFC5910] with type="unsignedByte" and isRequired="true". 1362 Contains the DS digest value per [RFC5910] with 1363 type="hexBinary" and isRequired="true". 1365 The following "csvDomain" field elements MUST be used in the "dnssec" 1366 element when the Key Data Interface per 1367 [RFC5910] is used and MAY be used in the "dnssec" 1368 element when the DS Data Interface per [RFC5910] is 1369 used: 1371 Contains the flags field value per [RFC5910] with 1372 type="unsignedShort" and isRequired="true". 1374 Contains the Key protocol value per [RFC5910] 1375 with type="unsignedByte" and isRequired="true". 1377 Contains the Key algorithm value per [RFC5910] 1378 with type="unsignedByte" and isRequired="true". 1380 Contains the public key value per [RFC5910] with 1381 type="secDNS:keyType" and isRequired="true". 1383 The following "csvDomain" field elements MAY be used in the "dnssec" 1384 element: 1386 Indicates a child's preference for the 1387 number of seconds after signature generation when the parent's 1388 signature on the DS information provided by the child will expire 1389 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1391 The following "domain" fields, defined for the "domain" CSV File 1392 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1393 element: 1395 Domain name of the domain object associated with 1396 the DNSSEC record and isRequired="true". 1398 Example of a "dnssec" element with 1399 the DS Data Interface of [RFC5910]: 1401 1402 ... 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1415 dnssec-ds-YYYYMMDD.csv 1416 1417 1418 1419 ... 1420 1421 ... 1423 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1424 contains two DS records for domain1.example. 1426 domain1.example,604800,12345,3,1,49FD46E6C4B45C55D4AC 1427 domain1.example,604800,12346,3,1,38EC35D5B3A34B44C39B 1428 Example of a "dnssec" element with 1429 the Key Data Interface of [RFC5910]: 1431 1432 ... 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1445 dnssec-key-YYYYMMDD.csv 1446 1447 1448 1449 ... 1450 1451 ... 1453 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1454 contains two key records for domain1.example. 1456 domain1.example,604800,257,3,1,AQPJ////4Q== 1457 domain1.example,604800,257,3,1,AQPJ////4QQQ 1459 5.1.2.1.7. "domainTransfer" CSV File Definition 1461 The "domainTransfer" CSV File Definition defines the fields and CSV 1462 file references used for the domain name object pending and completed 1463 transfer records. No additional field elements were added for use in 1464 the "domainTransfer" element. 1466 The following "rdeCsv" fields, defined in section CSV common field 1467 elements (Section 4.6.2.2), MUST be used in the "domainTransfer" 1468 element: 1470 State of the most recent transfer request with 1471 isRequired="true". 1473 Identifier of the registrar, defined in Section 5.4, 1474 of the client that requested the transfer with isRequired="true". 1476 Date and time that the transfer was requested with 1477 isRequired="true". 1479 Identifier of the registrar, defined in Section 5.4, 1480 of the client that should take or took action with 1481 isRequired="true". 1483 Date and time that the transfer action should be 1484 taken or has been taken with isRequired="true". 1486 The following "rdeCsv" fields, defined in section CSV common field 1487 elements (Section 4.6.2.2), MAY be used in the "domainTransfer" 1488 element: 1490 Expiration date if the transfer command caused or 1491 causes a change in the validity period. 1493 Identifier of the client that requested the transfer. 1495 Identifier of the client that should take or took 1496 action for transfer. 1498 The following "csvDomain" fields, defined for the "domain" CSV File 1499 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1500 element: 1502 Domain name of the domain object involved in the 1503 transfer with isRequired="true". 1505 Example of a "domainTransfer" 1506 element. 1508 ... 1509 1510 ... 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1526 domainTransfer-YYYYMMDD.csv 1527 1528 1529 1530 ... 1531 1532 ... 1534 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1535 file contains one domain transfer record with a pending status. 1537 domain1.example,pending,registrarX,clientY, 1538 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1539 2016-04-03T22:00:00.0Z 1541 5.1.2.2. 1543 The is used to hold the deleted domain name 1544 objects in a Differential or Incremental Deposit. All the domain 1545 name object data is deleted as part of a cascade delete. The 1546 is split into separate CSV file definitions using 1547 named elements with the "name" attribute. The following 1548 section defines the supported domain name deletes CSV file 1549 definition. 1551 5.1.2.2.1. "domain" Deletes CSV File Definition 1553 The following "csvDomain" field elements MUST be used in the deletes 1554 "domain" element: 1556 Domain name field with type="eppcom:labelType" and 1557 isRequired="true". 1559 Example of a "domain" element: 1561 ... 1562 1563 ... 1564 1565 1566 1567 1568 1569 1571 domain-delete-YYYYMMDD.csv 1572 1573 1574 1575 ... 1576 1577 ... 1579 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1580 file contains two domain name records. 1582 domain1.example 1583 domain2.example 1585 5.2. Host Object 1587 The host object is based on the EPP host name mapping in [RFC5732]. 1588 The host object supports both the XML Model and the CSV Model, 1589 defined in Models (Section 2) section. The elements used for both 1590 models are defined in the following sections. Both the 1591 and elements contain one or more 1592 elements with a set of named CSV file definitions using 1593 the "name" attribute. 1595 5.2.1. XML Model 1597 There are two elements used in the data escrow of the host objects 1598 for the XML model including the , under the 1599 element, and the element, under 1600 the element. 1602 A element substitutes for the 1603 abstract element to define a concrete definition of a host. The 1604 element can be replaced by other host 1605 definitions using the XML schema substitution groups feature. 1607 5.2.1.1. element 1609 The RDE host object is based on the EPP host response for an 1610 authorized client (Section 3.1.2. of [RFC5732]). 1612 The OPTIONAL element contains the following child elements: 1614 o A element that contains the fully-qualified name of the 1615 host object. 1617 o A element that contains the repository object identifier 1618 assigned to the host object when the object was created. 1620 o One or more elements that describe the status of the host 1621 object. 1623 o Zero or more elements that contain the IP addresses 1624 associated with the host object. 1626 o A element that contains the identifier of the sponsoring 1627 registrar. 1629 o An OPTIONAL element that contains the identifier of the 1630 registrar that created the host object. An OPTIONAL client 1631 attribute is used to specify the client that performed the 1632 operation. 1634 o An OPTIONAL element that contains the date and time of 1635 host-object creation. 1637 o An OPTIONAL element that contains the identifier of the 1638 registrar that last updated the host object. This element MUST 1639 NOT be present if the host object has never been modified. An 1640 OPTIONAL client attribute is used to specify the client that 1641 performed the operation. 1643 o An OPTIONAL element that contains the date and time of 1644 the most recent host-object modification. This element MUST NOT 1645 be present if the host object has never been modified. 1647 o An OPTIONAL element that contains the date and time of 1648 the most recent host object successful transfer. This element 1649 MUST NOT be present if the domain name object has never been 1650 transfered. 1652 Example of object: 1654 ... 1655 1656 ns1.example1.example 1657 Hns1_example_test-TEST 1658 1659 1660 192.0.2.2 1661 192.0.2.29 1662 2001:DB8:1::1 1663 RegistrarX 1664 RegistrarX 1665 1999-05-08T12:10:00.0Z 1666 RegistrarX 1667 2009-10-03T09:34:00.0Z 1668 1669 ... 1671 5.2.1.2. object 1673 The element contains the fully-qualified domain name 1674 of a host that was deleted. The element also 1675 supports host removal based on roid to support SRS systems in which 1676 different hosts with the same fully-qualified domain name are active 1677 at the same time. 1679 Example of object: 1681 ... 1682 1683 ... 1684 1685 ns1.example.example 1686 1687 ... 1688 1689 ... 1691 5.2.2. CSV Model 1693 For the CSV Model of the host object, the child 1694 element of the element is used to hold the new or 1695 updated host objects for the deposit. The child 1696 element of the element is used to hold the deleted or 1697 purged host objects for the deposit. 1699 Differential and Incremental Deposits are based on changes to the 1700 host objects. The updated host object data under the 1701 element is a cascade replace down all of the host 1702 CSV files starting with the parent "host" CSV File Definition 1703 (Section 5.2.2.1.1). The child CSV file definitions include a 1704 field. All the child CSV file 1705 definition data for the host objects in the parent "host" CSV File 1706 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1707 using the data in the child CSV files. The deleted host object data 1708 under the element is a cascade delete starting from 1709 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1711 5.2.2.1. 1713 The is used to hold the new or updated host object 1714 information for the deposit. The is split into 1715 separate CSV file definitions using named elements with 1716 the "name" attribute. The following sections include the supported 1717 host CSV file definitions. 1719 5.2.2.1.1. "host" CSV File Definition 1721 The "host" CSV File Definition defines the fields and CSV file 1722 references used for the host object records. 1724 The following "csvHost" field elements MUST be used in the "host" 1725 element: 1727 Host name field with type="eppcom:labelType" and 1728 isRequired="true". 1730 The following "rdeCsv" fields, defined in section CSV common field 1731 elements (Section 4.6.2.2), MUST be used in the "host" 1732 element: 1734 Repository Object IDentifier (ROID) assigned to the 1735 host object with isRequired="true". 1737 The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the 1738 "host" element: 1740 or A choice of: 1742 Identifier of the sponsoring client with 1743 isRequired="true". 1745 Contains the ID assigned by ICANN with 1746 type="positiveInteger". The attribute "isRequired" MUST equal 1747 "true". 1749 Identifier of the registrar, defined in Section 5.4, 1750 of the client that created the object. 1752 Identifier of the client that created the host 1753 object. 1755 Identifier of the registrar, defined in Section 5.4, 1756 of the client that updated the object. 1758 Identifier of the client that last updated the host 1759 object. 1761 Date and time that the host object was created. 1763 Date and time that the host object was last 1764 updated. 1766 Date and time that the host was last transferred. 1768 Example of a "host" element. 1770 ... 1771 1772 ... 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1789 host-YYYYMMDD.csv 1790 1791 1792 1793 ... 1794 1795 ... 1797 Example of the corresponding host-YYYYMMDD.csv file. The file 1798 contains six host records with four being internal hosts and two 1799 being external hosts. 1801 ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX, 1802 clientY,1999-05-08T12:10:00.0Z,registrarX, 1803 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1804 ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX, 1805 clientY,1999-05-08T12:10:00.0Z,registrarX, 1806 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1807 ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX, 1808 clientY,1999-05-08T12:10:00.0Z,registrarX, 1809 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1810 ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, 1811 clientY,1999-05-08T12:10:00.0Z,registrarX, 1812 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1813 ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, 1814 clientY,1999-05-08T12:10:00.0Z,registrarX, 1815 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1816 ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, 1817 clientY,1999-05-08T12:10:00.0Z,registrarX, 1818 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1820 5.2.2.1.2. "hostStatuses" CSV File Definition 1822 The "hostStatuses" CSV File Definition defines the fields and CSV 1823 file references used for the host object statuses. 1825 The following "csvHost" fields, defined for the "host" CSV File 1826 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1827 element: 1829 The status of the host with 1830 type="host:statusValueType" and isRequired="true". 1832 The following "rdeCsv" fields, defined in section CSV common field 1833 elements (Section 4.6.2.2), MUST be used in the "hostStatuses" 1834 element: 1836 Host object Registry Object IDentifier (ROID) 1837 assigned to the host object with isRequired="true". 1839 The following "rdeCsv" fields, defined in section CSV common field 1840 elements (Section 4.6.2.2), MAY be used in the "hostStatuses" 1841 element: 1843 Host object status description which is 1844 free form text describing the rationale for the status. The 1845 attribute "isRequired" MUST equal "true". 1847 Language of the field. 1849 Example of a "hostStatuses" element. 1851 ... 1852 1853 ... 1854 1855 1856 1857 1858 1859 1860 1861 1862 1864 hostStatuses-YYYYMMDD.csv 1865 1866 1867 1868 ... 1869 1870 ... 1872 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1873 file contains the statuses for the six host names 1874 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example, 1875 ns2.domain2.example, ns1.example.net and ns2.example.net. 1877 Hns1_domain1_test-TEST,ok,, 1878 Hns2_domain1_test-TEST,ok,, 1879 Hns1_domain2_test-TEST,ok,, 1880 Hns2_domain2_test-TEST,ok,, 1881 Hns1_example_test-TEST,ok,, 1882 Hns2_example_test-TEST,ok,, 1884 5.2.2.1.3. "hostAddresses" CSV File Definition 1886 The "hostAddresses" CSV File Definition defines the fields and CSV 1887 file references used for the host object IP addresses. 1889 The following "csvHost" field elements MUST be used in the 1890 "hostAddresses" element: 1892 IP addresses associated with the host object with 1893 type="host:addrStringType". The attribute "isRequired" MUST equal 1894 "true". 1896 IP addresses version associated with the host 1897 object with type="host:ipType". "host:ipType" has the enumerated 1898 values of "v4" or "v6". The attribute "isRequired" MUST equal 1899 "true". 1901 The following "rdeCsv" fields, defined in section CSV common field 1902 elements (Section 4.6.2.2), MUST be used in the "hostAddresses" 1903 element: 1905 Host object Registry Object IDentifier (ROID) 1906 assigned to the host object with isRequired="true". 1908 Example of a "hostAddresses" element. 1910 ... 1911 1912 ... 1913 1914 1915 1916 1917 1918 1919 1920 1922 hostAddresses-YYYYMMDD.csv 1923 1924 1925 1926 ... 1927 1928 ... 1930 Example of the corresponding hostAddresses-YYYYMMDD.csv file. The 1931 file contains the IP addresses for the host names 1932 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and 1933 ns2.domain2.example. 1935 Hns1_domain1_test-TEST,192.0.2.1,v4 1936 Hns2_domain1_test-TEST,2001:DB8::1,v6 1937 Hns1_domain2_test-TEST,192.0.2.2,v4 1938 Hns2_domain2_test-TEST,2001:DB8::2,v6 1940 5.2.2.2. 1942 The is used to hold the deleted host objects in a 1943 Differential or Incremental Deposit. All the host object data is 1944 deleted as part of a cascade delete. The is split 1945 into separate CSV file definitions using named elements 1946 with the "name" attribute. The following section defines the 1947 supported host deletes CSV file definition. 1949 5.2.2.2.1. "host" Deletes CSV File Definition 1951 The following "rdeCsv" fields, defined in section CSV common field 1952 elements (Section 4.6.2.2), MUST be used in the "host" 1953 element: 1955 Repository Object IDentifier (ROID) assigned to the 1956 host object with isRequired="true". 1958 Example of a "host" element. 1960 ... 1961 1962 ... 1963 1964 1965 1966 1967 1968 1970 host-delete-YYYYMMDD.csv 1971 1972 1973 1974 ... 1975 1976 ... 1978 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1979 host records. 1981 Hns1_domain1_test-TEST 1982 Hns2_domain1_test-TEST 1983 Hns1_domain2_test-TEST 1984 Hns2_domain2_test-TEST 1986 5.3. Contact Object 1988 The contact object is based on the EPP contact name mapping in 1989 [RFC5733]. The contact object supports both the XML Model and the 1990 CSV Model, defined in Models (Section 2) section. The elements used 1991 for both models are defined in the following sections. 1993 5.3.1. XML Model 1995 There are two elements used in the data escrow of the contact objects 1996 for the XML model including the , under the 1997 element, and the element, 1998 under the element. 2000 A element substitutes for the abstract 2001 element to define a concrete definition of a contact. The 2002 element can be replaced by other contact 2003 definitions using the XML schema substitution groups feature. 2005 5.3.1.1. object 2007 The contact object is based on the EPP contact response for an 2008 authorized client (Section 3.1.2. of [RFC5733]) with some additions 2009 including the data from an EPP Query Response, see 2010 Section 3.1.3. of [RFC5733]. 2012 The OPTIONAL element contains the following child elements: 2014 o A element that contains the server-unique identifier of the 2015 contact object 2017 o A element that contains the Repository Object IDentifier 2018 assigned to the contact object when the object was created. 2020 o One or more elements that describe the status of the 2021 contact object. 2023 o One or two elements that contain postal-address 2024 information. Two elements are provided so that address 2025 information can be provided in both internationalized and 2026 localized forms; a "type" attribute is used to identify the two 2027 forms. If an internationalized form (type="int") is provided, 2028 element content MUST be represented in a subset of UTF-8 that can 2029 be represented in the 7-bit US-ASCII character set. If a 2030 localized form (type="loc") is provided, element content MAY be 2031 represented in unrestricted UTF-8. The element 2032 contains the following child elements: 2034 * A element that contains the name of the individual or 2035 role represented by the contact. 2037 * An OPTIONAL element that contains the name of the 2038 organization with which the contact is affiliated. 2040 * An element that contains address information associated 2041 with the contact. An element contains the following 2042 child elements: 2044 + One, two, or three OPTIONAL elements that contain 2045 the contact's street address. 2047 + A element that contains the contact's city. 2049 + An OPTIONAL element that contains the contact's state 2050 or province. 2052 + An OPTIONAL element that contains the contact's postal 2053 code. 2055 + A element that contains the contact's two-letter 2056 country code. 2058 o An OPTIONAL element that contains the contact's voice 2059 telephone number. 2061 o An OPTIONAL element that contains the contact's facsimile 2062 telephone number. 2064 o An element that contains the contact's email address. 2066 o A element that contains the identifier of the sponsoring 2067 registrar. 2069 o An OPTIONAL element that contains the identifier of the 2070 registrar that created the contact object. An OPTIONAL client 2071 attribute is used to specify the client that performed the 2072 operation. 2074 o An OPTIONAL element that contains the date and time of 2075 contact-object creation. 2077 o An OPTIONAL element that contains the identifier of the 2078 registrar that last updated the contact object. This element MUST 2079 NOT be present if the contact has never been modified. An 2080 OPTIONAL client attribute is used to specify the client that 2081 performed the operation. 2083 o An OPTIONAL element that contains the date and time of 2084 the most recent contact-object modification. This element MUST 2085 NOT be present if the contact object has never been modified. 2087 o An OPTIONAL element that contains the date and time of 2088 the most recent contact object successful transfer. This element 2089 MUST NOT be present if the contact object has never been 2090 transferred. 2092 o An OPTIONAL element that contains the following child 2093 elements related to the last transfer request of the contact 2094 object: 2096 * A element that contains the state of the most recent 2097 transfer request. 2099 * A element that contains the identifier of the registrar 2100 that requested the domain name object transfer. An OPTIONAL 2101 client attribute is used to specify the client that performed 2102 the operation. 2104 * An element that contains the identifier of the registrar 2105 that should act upon a PENDING transfer request. For all other 2106 status types, the value identifies the registrar that took the 2107 indicated action. An OPTIONAL client attribute is used to 2108 specify the client that performed the operation. 2110 * A element that contains the date and time that the 2111 transfer was requested. 2113 * An element that contains the date and time of a 2114 required or completed response. For a PENDING request, the 2115 value identifies the date and time by which a response is 2116 required before an automated response action will be taken by 2117 the registry. For all other status types, the value identifies 2118 the date and time when the request was completed. 2120 o An OPTIONAL element that identifies elements that 2121 requiring exceptional server-operator handling to allow or 2122 restrict disclosure to third parties. See Section 2.9 of 2123 [RFC5733] for a description of the child elements contained within 2124 the element. 2126 Example object: 2128 ... 2129 2130 sh8013 2131 Csh8013-TEST 2132 2133 2134 2135 John Doe 2136 Example Inc. 2137 2138 123 Example Dr. 2139 Suite 100 2140 Dulles 2141 VA 2142 20166-6503 2143 US 2144 2145 2146 +1.7035555555 2147 +1.7035555556 2148 jdoe@example.example 2149 RegistrarX 2150 RegistrarX 2151 2009-09-13T08:01:00.0Z 2152 RegistrarX 2153 2009-11-26T09:10:00.0Z 2154 2009-12-03T09:05:00.0Z 2155 2156 pending 2157 clientW 2158 2011-03-08T19:38:00.0Z 2159 RegistrarX 2160 2011-03-13T23:59:59.0Z 2161 2162 2163 2164 2165 2166 2167 ... 2169 5.3.1.2. object 2171 The element contains the id of a contact that was 2172 deleted. 2174 Example of object: 2176 ... 2177 2178 ... 2179 2180 sh8013-TEST 2181 co8013-TEST 2182 2183 ... 2184 2185 ... 2187 5.3.2. CSV Model 2189 For the CSV Model of the contact object, the 2190 child element of the element is used to hold the new 2191 or updated contacts objects for the deposit. The 2192 child element of the element is 2193 used to hold the deleted or purged contact objects for the deposit. 2194 Both the and elements 2195 contain one or more elements with a set of named CSV 2196 file definitions using the "name" attribute. 2198 Differential and Incremental Deposits are based on changes to the 2199 contact objects. The updated contact object data under the 2200 element is a cascade replace down all of the 2201 contact CSV files starting with the parent "contact" CSV File 2202 Definition (Section 5.3.2.1.1). The child CSV file definitions 2203 include a field. All the child CSV 2204 file definition data for the contact objects in the parent "contact" 2205 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2206 then set using the data in the child CSV files. The deleted contact 2207 object data under the element is a cascade 2208 delete starting from the "contact" Deletes CSV File Definition 2209 (Section 5.3.2.2.1). 2211 5.3.2.1. 2213 The is used to hold the new or updated contact 2214 object information for the deposit. The is 2215 split into separate CSV file definitions using named 2216 elements with the "name" attribute. The following sections include 2217 the supported contact CSV file definitions. 2219 5.3.2.1.1. "contact" CSV File Definition 2221 The "contact" CSV File Definition defines the fields and CSV file 2222 references used for the contact object records. 2224 The following "csvContact" field elements MUST be used in the 2225 "contact" element: 2227 Contains the server-unique contact identifier with 2228 type="eppcom:clIDType" and isRequired="true". 2230 Contains the contact's email address with 2231 type="eppcom:minTokenType" and isRequired="true". 2233 The following field elements MAY be used in the "contact" 2234 element: 2236 Contains the contact's voice telephone number 2237 with type="contact:e164StringType". 2239 Contains the contact's voice telephone number 2240 extension with type="token". 2242 Contains the contact's facsimile telephone number 2243 with type="contact:e164StringType". 2245 Contains the contact's facsimile telephone 2246 number extension with type="token". 2248 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 2249 "contact" element: 2251 The Registry Object IDentifier (ROID) for the contact 2252 object with isRequired="true". 2254 or A choice of: 2256 Identifier of the sponsoring client with 2257 isRequired="true". 2259 Contains the ID assigned by ICANN with 2260 type="positiveInteger". The attribute "isRequired" MUST equal 2261 "true". 2263 The following "rdeCsv" fields, defined in section CSV common field 2264 elements (Section 4.6.2.2), MAY be used in the "contact" 2265 element: 2267 Identifier of the registrar, defined in Section 5.4, 2268 of the client that created the object. 2270 Identifier of the client that created the contact 2271 object. 2273 Identifier of the registrar, defined in Section 5.4, 2274 of the client that updated the object. 2276 Identifier of the client that last updated the 2277 contact object. 2279 Created date and time of the contact object. 2281 Date and time of the last update to the contact 2282 object. 2284 Date and time of the last transfer for the contact 2285 object. 2287 Example of a "contact" element. 2289 ... 2290 2291 ... 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2312 contact-YYYYMMDD.csv 2313 2314 2315 2316 ... 2317 2318 ... 2320 Example of the contact-YYYYMMDD.csv file. The file contains nine 2321 object contact records. 2323 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2324 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2325 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2326 2009-11-26T09:10:00.0Z 2327 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2328 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2329 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2330 2009-11-26T09:10:00.0Z 2331 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2332 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2333 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2334 2009-11-26T09:10:00.0Z 2335 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2336 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2337 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2338 2009-11-26T09:10:00.0Z 2339 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2340 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2341 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2342 2009-11-26T09:10:00.0Z 2343 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2344 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2345 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2346 2009-11-26T09:10:00.0Z 2347 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2348 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2349 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2350 2009-11-26T09:10:00.0Z 2351 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2352 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2353 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2354 2009-11-26T09:10:00.0Z 2355 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2356 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2357 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2358 2009-11-26T09:10:00.0Z 2360 5.3.2.1.2. "contactStatuses" CSV File Definition 2362 The "contactStatuses" CSV File Definition defines the fields and CSV 2363 file references used for the contact object statuses. 2365 The following "csvContact" field elements, defined for the "contact" 2366 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2367 "contactStatuses" element: 2369 Server-unique contact identifier of status with 2370 isRequired="true". 2372 The status of the contact with 2373 type="contact:statusValueType" and isRequired="true". 2375 The following "rdeCsv" fields, defined in section CSV common field 2376 elements (Section 4.6.2.2), MAY be used in the "contactStatuses" 2377 element: 2379 The contact object status description 2380 which is free form text describing the rationale for the status. 2382 Language of the field. 2384 Example of a "contactStatuses" 2385 element. 2387 ... 2388 2389 ... 2390 2391 2392 2393 2394 2395 2396 2397 2398 2400 contactStatuses-YYYYMMDD.csv 2401 2402 2403 2404 ... 2405 2406 ... 2408 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2409 file contains the statuses for the nine contact identifiers. 2411 domain1admin,ok,, 2412 domain1tech,ok,, 2413 domain1billing,ok,, 2414 domain2admin,ok,, 2415 domain2tech,ok,, 2416 domain2billing,ok,, 2417 xnabc123admin,ok,, 2418 xnabc123tech,ok,, 2419 xnabc123billing,ok,, 2421 5.3.2.1.3. "contactPostal" CSV File Definition 2423 The "contactPostal" CSV File Definition defines the fields and CSV 2424 file references used for the contact postal info object records. 2426 The following "csvContact" field elements MUST be used in the 2427 "contactPostal" element: 2429 Contains the form of the postal-address 2430 information with type="contact:postalLineType" and 2431 isRequired="true". This field specifies the form ("int" or 2432 "loc"), as defined in Section 4.6.3, of the , 2433 , , , 2434 , , fields. 2436 Contains the contact's name of the individual or 2437 role represented by the contact with type="contact:postalLineType" 2438 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2439 indicate the localized or internationalized form as defined in 2440 section Section 4.6.3. 2442 Contains the contact's street address line with 2443 type="contact:fPostalLineType". An index attribute is required to 2444 indicate which street address line the field represents with index 2445 "0" for the first line and index "2" for the last line. An 2446 OPTIONAL "isLoc" attribute to used to indicate the localized or 2447 internationalized form as defined in section Section 4.6.3. 2449 Contains the contact's city with 2450 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2451 "isLoc" attribute to used to indicate the localized or 2452 internationalized form as defined in section Section 4.6.3. 2454 Contains the contact's country code with 2455 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2456 attribute to used to indicate the localized or internationalized 2457 form as defined in section Section 4.6.3. 2459 The following "csvContact" field elements MAY be used in the 2460 "contactPostal" element: 2462 Contains the name of the organization with which 2463 the contact is affiliated with type="contact:optPostalLineType". 2464 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2465 internationalized form as defined in section Section 4.6.3. 2467 Contains the contact's state or province with 2468 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2469 to used to indicate the localized or internationalized form as 2470 defined in section Section 4.6.3. 2472 Contains the contact's postal code with 2473 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2474 indicate the localized or internationalized form as defined in 2475 section Section 4.6.3. 2477 The following "csvContact" fields, defined for the "contact" CSV File 2478 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2479 element: 2481 Server-unique contact identifier for the contact 2482 object with isRequired="true". 2484 Example of a "contactPostal" 2485 element. 2487 ... 2488 2489 ... 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2507 contactPostal-YYYYMMDD.csv 2508 2509 2510 2511 ... 2512 2513 ... 2515 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2516 nine contact postal records. 2518 domain1admin,int,"John Doe","Example Inc.", 2519 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2520 domain1tech,int,"John Doe","Example Inc.", 2521 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2522 domain1billing,int,"John Doe","Example Inc.", 2523 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2524 domain2admin,int,"John Doe","Example Inc.", 2525 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2526 domain2tech,int,"John Doe","Example Inc.", 2527 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2528 domain2billing,int,"John Doe","Example Inc.", 2529 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2530 xnabc123admin,int,"John Doe","Example Inc.", 2531 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2532 xnabc123tech,int,"John Doe","Example Inc.", 2533 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2534 xnabc123billing,int,"John Doe","Example Inc.", 2535 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2537 5.3.2.1.4. "contactTransfer" CSV File Definition 2539 The "contactTransfer" CSV File Definition defines the fields and CSV 2540 file references used for the contact object pending and completed 2541 transfer records. No additional field elements were added for use in 2542 the "contactTransfer" element. The 2543 following "rdeCsv" fields, defined in section CSV common field 2544 elements (Section 4.6.2.2), MUST be used in the "contactTransfer" 2545 element: 2547 State of the most recent transfer request with 2548 isRequired="true". 2550 Identifier of the registrar, defined in Section 5.4, 2551 of the client that requested the transfer with isRequired="true". 2553 Date and time that the transfer was requested with 2554 isRequired="true". 2556 Identifier of the registrar, defined in Section 5.4, 2557 of the client that should take or took action with 2558 isRequired="true". 2560 Date and time that the transfer action should be 2561 taken or has been taken with isRequired="true". 2563 The following "rdeCsv" fields, defined in section CSV common field 2564 elements (Section 4.6.2.2), MAY be used in the "contactTransfer" 2565 element: 2567 Identifier of the client that requested the transfer. 2569 Identifier of the client that should take or took 2570 action for transfer. 2572 The following "csvContact" fields, defined for the "contact" CSV File 2573 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2574 element: 2576 Server-unique contact identifier for the contact 2577 object with isRequired="true". 2579 Example of a "contactTransfer" 2580 element. 2582 ... 2583 2584 ... 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2599 contactTransfer-YYYYMMDD.csv 2600 2601 2602 2603 ... 2604 2605 ... 2607 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2608 one contact transfer record in pending status. 2610 xnabc123admin,clientApproved,registrarX,clientX, 2611 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2613 5.3.2.1.5. "contactDisclose" CSV File Definition 2615 The "contactDisclose" CSV File Definition defines the fields and CSV 2616 file references used for the contact disclose object records. 2618 The following "csvContact" field elements MAY be used in the 2619 "contactDisclose" element: 2621 Contains flag with a value of "true" or 2622 "1" (one) notes the preference to allow disclosure of the 2623 specified elements as an exception to the stated data-collection 2624 policy. A value of "false" or "0" (zero) notes a client 2625 preference to not allow disclosure of the specified elements as an 2626 exception to the stated data-collection policy with 2627 type="boolean". The additional fields define specific exceptional 2628 disclosure preferences based on the 2629 field. 2631 Exceptional disclosure preference flag 2632 for the localized form of the contact name with type="boolean". 2634 Exceptional disclosure preference flag 2635 for the internationalized form of the contact name with 2636 type="boolean". 2638 Exceptional disclosure preference flag 2639 for the localized form of the contact organization with 2640 type="boolean". 2642 Exceptional disclosure preference flag 2643 for the internationalized form of the contact organization with 2644 type="boolean". 2646 Exceptional disclosure preference flag 2647 for the localized form of the contact address with type="boolean". 2649 Exceptional disclosure preference flag 2650 for the internationalized form of the contact address with 2651 type="boolean". 2653 Exceptional disclosure preference flag 2654 of the contact voice telephone number with type="boolean". 2656 Exceptional disclosure preference flag of 2657 the contact facsimile telephone number with type="boolean". 2659 Exceptional disclosure preference flag 2660 of the contact email address with type="boolean". 2662 The following "csvContact" fields, defined for the "contact" CSV File 2663 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2664 element: 2666 Server-unique contact identifier for the contact 2667 object with isRequired="true". 2669 Example of a "contactDisclose" 2670 element. 2672 ... 2673 2674 ... 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2692 contactDisclose-YYYYMMDD.csv 2693 2694 2695 2696 ... 2697 2698 ... 2700 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2701 one disclosure records, disabling disclosure of voice, fax, and 2702 email. 2704 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2706 5.3.2.2. 2708 The is used to hold the deleted contact objects 2709 in a Differential or Incremental Deposit. All the contact object 2710 data is deleted as part of a cascade delete. The 2711 is split into separate CSV file definitions 2712 using named elements with the "name" attribute. The 2713 following section defines the supported contact deletes CSV file 2714 definition. 2716 5.3.2.2.1. "contact" Deletes CSV File Definition 2718 The following "csvContact" field elements MUST be used in the deletes 2719 "contact" element: 2721 Contains the server-unique contact identifier with 2722 type="eppcom:clIDType" and isRequired="true". 2724 Example of a "contact" element. 2726 ... 2727 2728 ... 2729 2730 2731 2732 2733 2734 2736 contact-delete-YYYYMMDD.csv 2737 2738 2739 2740 ... 2741 2742 ... 2744 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2745 six contact records. 2747 domain1admin 2748 domain1tech 2749 domain1billing 2750 domain2admin 2751 domain2tech 2752 domain2billing 2754 5.4. Registrar Object 2756 The registrar object represents the sponsoring client for other 2757 objects, and is typically referred to as the sponsoring registrar. 2758 The registrar object supports both the XML Model and the CSV Model, 2759 defined in Section 2. The elements used for both models are defined 2760 in the following sections. 2762 5.4.1. XML Model 2764 There are two elements used in the data escrow of the registrar 2765 objects for the XML model including the , 2766 under the element, and the 2767 element, under the element. 2769 A element substitutes for the 2770 abstract element to define a 2771 concrete definition of a registrar. The 2772 element can be replaced by other 2773 domain definitions using the XML schema substitution groups feature. 2775 5.4.1.1. element 2777 The element contains the following child elements: 2779 o An element that contains the Registry-unique identifier of 2780 the registrar object. This has a superordinate relationship 2781 to a subordinate , or of domain, contact and 2782 host objects. 2784 o An element that contains the name of the registrar. 2786 o An OPTIONAL element that contains the ID assigned by 2787 ICANN. 2789 o An OPTIONAL element that contains the operational status 2790 of the registrar. Possible values are: ok, readonly and 2791 terminated. 2793 o One or two OPTIONAL elements that contain postal- 2794 address information. Two elements are provided so that address 2795 information can be provided in both internationalized and 2796 localized forms; a "type" attribute is used to identify the two 2797 forms. If an internationalized form (type="int") is provided, 2798 element content MUST be represented in a subset of UTF-8 that can 2799 be represented in the 7-bit US-ASCII character set. If a 2800 localized form (type="loc") is provided, element content MAY be 2801 represented in unrestricted UTF-8. The element 2802 contains the following child elements: 2804 * A element that contains address information associated 2805 with the registrar. The element contains the following 2806 child elements: 2808 + One, two, or three OPTIONAL elements that contain 2809 the registrar's street address. 2811 + A element that contains the registrar's city. 2813 + An OPTIONAL element that contains the registrar's state 2814 or province. 2816 + An OPTIONAL element that contains the registrar's 2817 postal code. 2819 + A element that contains the registrar's country code. 2821 o An OPTIONAL element that contains the registrar's voice 2822 telephone number. 2824 o An OPTIONAL element that contains the registrar's facsimile 2825 telephone number. 2827 o An OPTIONAL element that contains the registrar's email 2828 address. 2830 o An OPTIONAL element that contains the registrar's URL. 2832 o An OPTIONAL elements that contains whois information. 2833 The element contains the following child elements: 2835 * An OPTIONAL element that contains the name of the 2836 registrar WHOIS server listening on TCP port 43 as specified in 2837 [RFC3912]. 2839 * An OPTIONAL element that contains the name of the 2840 registrar WHOIS server listening on TCP port 80/443. 2842 o An OPTIONAL element that contains the date and time of 2843 registrar-object creation. 2845 o An OPTIONAL element that contains the date and time of 2846 the most recent RDE registrar-object modification. This element 2847 MUST NOT be present if the rdeRegistrar object has never been 2848 modified. 2850 Example of object: 2852 ... 2853 2854 RegistrarX 2855 Registrar X 2856 123 2857 ok 2858 2859 2860 123 Example Dr. 2861 Suite 100 2862 Dulles 2863 VA 2864 20166-6503 2865 US 2866 2867 2868 +1.7035555555 2869 +1.7035555556 2870 jdoe@example.example 2871 http://www.example.example 2872 2873 whois.example.example 2874 http://whois.example.example 2875 2876 2005-04-23T11:49:00.0Z 2877 2009-02-17T17:51:00.0Z 2878 2879 ... 2881 5.4.1.2. object 2883 The element contains the id of a registrar that 2884 was deleted. 2886 Example of object: 2888 ... 2889 2890 ... 2891 2892 agnt0001-TEST 2893 2894 ... 2895 2896 ... 2898 5.4.2. CSV Model 2900 For the CSV Model of the registrar object, the 2901 child element of the element 2902 is used to hold the new or updated registrar objects for the deposit. 2903 The child element of the element 2904 is used to hold the deleted or purged registrar objects for the 2905 deposit. Both the and 2906 elements contain one or more elements with a set of 2907 named CSV file definitions using the "name" attribute. 2909 Differential and Incremental Deposits are based on changes to the 2910 registrar objects. The updated registrar object data under the 2911 element is a cascade replace down all of the 2912 registrar CSV files starting with the parent "registrar" CSV File 2913 Definition (Section 5.4.2.1.1). The child CSV file definitions 2914 include a field. All the child CSV 2915 file definition data for the registrar objects in the parent 2916 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2917 deleted and then set using the data in the child CSV files. The 2918 deleted registrar object data under the 2919 element is a cascade delete starting from the "registrar" Deletes CSV 2920 File Definition (Section 5.4.2.2.1). 2922 5.4.2.1. 2924 The is used to hold the new or updated 2925 registrar object information for the deposit. The 2926 is split into separate CSV file definitions 2927 using named elements with the "name" attribute. The 2928 following sections include the supported contact CSV file 2929 definitions. 2931 5.4.2.1.1. "registrar" CSV File Definition 2933 The "registrar" CSV File Definition defines the fields and CSV file 2934 references used for the registrar object records. 2936 The following "csvRegistrar" field elements MUST be used in the 2937 "registrar" element: 2939 or A choice of: 2941 Contains the server-unique registrar 2942 identifier with type="eppcom:clIDType" and isRequired="true". 2944 Contains the ID assigned by ICANN with 2945 type="positiveInteger". The attribute "isRequired" MUST equal 2946 "true". 2948 Contains the name of the registrar with 2949 type="normalizedString" and isRequired="true". 2951 The following field elements MAY be used in the "registrar" 2952 element: 2954 Contains the status of the registrar with 2955 type="csvRegistrar:statusValueType". 2957 Contains the ID assigned by ICANN with 2958 type="positiveInteger". This field is included in this section in 2959 addition to the section above to support optionally providing the 2960 field when the field is 2961 used. 2963 Contains the Whois URL of the registrar 2964 with type="anyURI". 2966 The following "rdeCsv" fields, defined in section CSV common field 2967 elements (Section 4.6.2.2), MAY be used in the "registrar" 2968 element: 2970 Created date and time of the registrar object. 2972 Date and time of the last update to the registrar 2973 object. 2975 URL for the registrar web home page. 2977 The following "csvContact" fields, defined in section Contact Object 2978 (Section 5.3), MAY be used in the "registrar" 2979 element: 2981 Registrar street address line with an "index" 2982 attribute that represents the order of the street address line 2983 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2984 indicate the localized or internationalized form, as defined in 2985 Section 4.6.3. 2987 Registrar city with an OPTIONAL "isLoc" attribute 2988 that is used to indicate the localized or internationalized form, 2989 as defined in Section 4.6.3. 2991 Registrar country code with an OPTIONAL "isLoc" 2992 attribute that is used to indicate the localized or 2993 internationalized form, as defined in Section 4.6.3. 2995 Registrar email address. The attribute 2996 "isRequired" MUST equal "false". 2998 Registrar state or province with an OPTIONAL 2999 "isLoc" attribute that is used to indicate the localized or 3000 internationalized form, as defined in Section 4.6.3. 3002 Registrar postal code with an OPTIONAL "isLoc" 3003 attribute that is used to indicate the localized or 3004 internationalized form, as defined in Section 4.6.3. 3006 Registrar voice telephone number. 3008 Registrar voice telephone number extension. 3010 Registrar facsimile telephone number. 3012 Registrar facsimile telephone number extension. 3014 Example of a "registrar" 3015 element. 3017 ... 3018 3019 ... 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3046 registrar-YYYYMMDD.csv 3047 3048 3049 3050 ... 3051 3052 ... 3054 Example of the registrar-YYYYMMDD.csv file. The file contains three 3055 registrar records. 3057 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 3058 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3059 +1.7035555556,,jdoe@example.example,http://www.example.example, 3060 http://whois.example.example,2005-04-23T11:49:00.0Z, 3061 2009-02-17T17:51:00.0Z 3062 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 3063 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3064 +1.7035555556,,jdoe@example.example,http://www.example.example, 3065 http://whois.example.example,2005-04-23T11:49:00.0Z, 3066 2009-02-17T17:51:00.0Z 3067 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 3068 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3069 +1.7035555556,,jdoe@example.example,http://www.example.example, 3070 http://whois.example.example,2005-04-23T11:49:00.0Z, 3071 2009-02-17T17:51:00.0Z 3073 5.4.2.2. 3075 The is used to hold the deleted registrar 3076 objects in a Differential or Incremental Deposit. All the registrar 3077 object data is deleted as part of a cascade delete. The 3078 is split into separate CSV file definitions 3079 using named elements with the "name" attribute. The 3080 following section defines the supported registrar deletes CSV file 3081 definition. 3083 5.4.2.2.1. "registrar" Deletes CSV File Definition 3085 The following "csvRegistrar" field elements MUST be used in the 3086 deletes "registrar" element: 3088 or A choice of: 3090 Contains the server-unique registrar 3091 identifier with type="eppcom:clIDType" and isRequired="true". 3093 Contains the ID assigned by ICANN with 3094 type="positiveInteger". The attribute "isRequired" MUST equal 3095 "true". 3097 Example of a "registrar" element. 3099 ... 3100 3101 ... 3102 3103 3104 3105 3106 3107 3109 registrar-delete-YYYYMMDD.csv 3110 3111 3112 3113 ... 3114 3115 ... 3117 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 3118 one registrar record. 3120 registrarZ 3122 5.5. IDN Table Reference Object 3124 The Internationalized Domain Names (IDN) table reference object is a 3125 pseudo-object that is used to provide a short reference to the IDN 3126 Table and Policy used in IDN registrations. The IDN reference object 3127 supports both the XML and the CSV Model, defined in the Models 3128 (Section 2) section. The elements used for both models are defined 3129 in the following sections. 3131 5.5.1. XML Model 3133 There is one element used in the data escrow of the IDN table 3134 reference objects for the XML model that is the , 3135 under the element. 3137 5.5.1.1. object 3139 The contains the following elements. An "id" 3140 attribute is used to specify an identifier for the IDN table. 3142 o An element that contains the URL of the IDN table that is 3143 being referenced. 3145 o A element that contains the URL of the IDN policy 3146 document. If IDN variants are generated algorithmically, the 3147 policy document MUST define the algorithm and the state of the 3148 implicit generated IDN variants. For a list of suggested states 3149 for implicit IDN variants, please see [variantTLDsReport]. 3151 Example of object: 3153 ... 3154 3155 3156 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3157 3158 3159 http://registro.br/dominio/regras.html 3160 3161 3162 ... 3164 5.5.2. CSV Model 3166 The IDN domain names, defined in Section 5.1, MAY have references to 3167 the IDN language identifier using the field 3168 element. The IDN table reference object defines the mapping of a 3169 language identifier to a language table URL. The language table URL 3170 defines the character code points that can be used for the language 3171 identifier. The elements used for the IDN table reference object is 3172 defined in this section. The child element of the 3173 element is used to hold the new or updated IDN table 3174 reference objects for the deposit. The child 3175 element of the element is used to hold the deleted or 3176 purged IDN table reference objects for the deposit. Both the 3177 and elements contain one or more 3178 elements with a set of named CSV file definitions using 3179 the "name" attribute. 3181 5.5.2.1. 3183 The is used to hold the new or updated IDN table 3184 reference object information for the deposit. The 3185 is split into separate CSV file definitions using named 3186 elements with the "name" attribute. The following sections include 3187 the supported IDN table reference CSV file definitions. 3189 5.5.2.1.1. "idnLanguage" CSV File Definition 3191 The "idnLanguage" CSV File Definition defines the fields and CSV file 3192 references used for the IDN table reference object records. 3194 The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be 3195 used in the "idnLanguage" element: 3197 The language identifier that matches the values 3198 for the field element in the "domain" CSV 3199 File Definition (Section 5.1.2.1.1) files. The attribute 3200 "isRequired" MUST equal "true". 3202 URL that defines the character code points that can be 3203 used for the language defined by the field element. 3204 The attribute "isRequired" MUST equal "true". 3206 Example of a "idnLanguage" element. 3208 ... 3209 3210 ... 3211 3212 3213 3214 3215 3216 3217 3219 idnLanguage-YYYYMMDD.csv 3220 3221 3222 3223 ... 3224 3225 ... 3227 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3228 contains two IDN language records. 3230 LANG-1, 3231 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3232 LANG-2, 3233 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3235 5.5.2.2. 3237 The is used to hold the deleted IDN table reference 3238 objects in a Differential or Incremental Deposit. The 3239 is split into separate CSV file definitions using 3240 named elements with the "name" attribute. The following 3241 section defines the supported IDN table reference deletes CSV file 3242 definition. 3244 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3246 The following "idnLanguage" field elements MUST be used in the 3247 deletes "idnLanguage" element: 3249 The language identifier that matches the values 3250 for the field element in the "domain" CSV 3251 File Definition (Section 5.1.2.1.1) files. The attribute 3252 "isRequired" MUST equal "true". 3254 Example of a "idnLanguage" element. 3256 ... 3257 3258 ... 3259 3260 3261 3262 3263 3264 3266 idnLanguage-delete-YYYYMMDD.csv 3267 3268 3269 3270 ... 3271 3272 ... 3274 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3275 contains one IDN language record. 3277 LANG-2 3279 5.6. NNDN Object 3281 An NNDN (NNDN's not domain name) can be used to store registry 3282 reserved names or (blocked, withheld or mirrored) IDN variants. 3284 Domain Name Registries may maintain domain names without their being 3285 persisted as domain objects in the registry system, for example, a 3286 list of reserved names not available for registration. The NNDN is a 3287 lightweight domain-like object that is used to escrow domain names 3288 not maintained as domain name objects. 3290 A domain name can only exist as a domain name object or an NNDN 3291 object, but not both. 3293 The NNDN object supports both the XML and the CSV Model, defined in 3294 the Models (Section 2) section. The elements used for both models 3295 are defined in the following sections. 3297 5.6.1. XML Model 3299 There are two elements used in the data escrow of the NNDN objects 3300 for the XML model including the , under the 3301 element, and the element, under the 3302 element. 3304 A element substitutes for the 3305 abstract element to define a concrete definition of an NNDN. The 3306 element can be replaced by other NNDN 3307 definitions using the XML schema substitution groups feature. 3309 5.6.1.1. object 3311 The element contains the following child elements: 3313 o An element that contains the fully-qualified qualified 3314 name of the NNDN. For IDNs the A-Label is used (see [RFC5891], 3315 Section 4.4). 3317 o An OPTIONAL element that contains the fully-qualified name 3318 of the NNDN in Unicode character set. It MUST be provided if 3319 available. 3321 o An OPTIONAL element that references the IDN 3322 Table used for the NNDN. This corresponds to the "id" attribute 3323 of the element. This element MUST be present if the 3324 NNDN is an IDN. 3326 o An OPTIONAL element is used to indicate that the 3327 NNDN is used for an IDN variant. This element contains the domain 3328 name used to generate the IDN variant. 3330 o A element that indicates the state of the NNDN: 3331 blocked, withheld or mirrored. 3333 * If an NNDN is considered undesirable for registration (i.e., 3334 unavailable for allocation to anyone), then the NNDN will be 3335 tagged as "blocked". 3337 * If an NNDN is considered a potential registration of a domain 3338 object for a registrant, then the NNDN will be tagged as 3339 "withheld". This status is only used when the NNDN is used for 3340 an IDN variant. 3342 * If an NNDN is considered a mirrored IDN variant of a domain 3343 object, then the NNDN will be tagged as "mirrored". A 3344 mirroringNS attribute is used to specify if the mirrored IDN 3345 variant use the NS mirror mechanism. The default value of 3346 mirroringNS is true. If another mechanism such as DNAME is 3347 used, the value of mirroringNS attribute MUST be false. 3349 o An OPTIONAL element that contains the date and time of 3350 the NNDN object creation. 3352 Example of an object: 3354 ... 3355 3356 xn--exampl-gva.example 3357 pt-BR 3358 example.example 3359 withheld 3360 2005-04-23T11:49:00.0Z 3361 3362 ... 3364 5.6.1.2. object 3366 The element contains the NNDN that was deleted, 3367 i.e., the . 3369 Example of an object: 3371 ... 3372 3373 ... 3374 3375 xn--pingino-q2a.example 3376 3377 ... 3378 3379 ... 3381 5.6.2. CSV Model 3383 For the CSV Model of the NNDN object, the child 3384 element of the element is used to hold the new or 3385 updated NNDN objects for the deposit. The child 3386 element of the element is used to hold the deleted or 3387 purged NNDN objects for the deposit. Both the and 3388 elements contain one or more elements 3389 with a set of named CSV file definitions using the 3390 "name" attribute. 3392 5.6.2.1. 3394 The is used to hold the new or updated NNDN object 3395 information for the deposit. The is split into 3396 separate CSV file definitions using named elements with 3397 the "name" attribute. The following sections include the supported 3398 NNDN CSV file definitions. 3400 5.6.2.1.1. "NNDN" CSV File Definition 3402 The "NNDN" CSV File Definition defines the fields and CSV file 3403 references used for the NNDN object records. 3405 The following "csvNNDN" field elements MUST be used in the "NNDN" 3406 element: 3408 Fully-qualified name of the NNDN with 3409 type="eppcom:labelType" and isRequired="true". For IDNs the 3410 A-Label is used (see [RFC5891], Section 4.4). 3412 State of the NNDN: blocked or withheld with 3413 type="rdeNNDN:nameState" and isRequired="true". See 3414 Section 5.6.1.1 for a description of the possible values for the 3415 element. 3417 The following field elements MAY be used in the "NNDN" 3418 element: 3420 Domain name used to generate the IDN variant 3421 with type="eppcom:labelType". 3423 Defines whether the "mirroring" 3424 uses the NS mirror mechanism, as described 3425 for the "mirroringNS" attribute in 3426 Section 5.6.1.1, with type="boolean". If the field element is not 3427 defined the default value is "true". 3429 The following "rdeCsv" fields, defined in section CSV common field 3430 elements (Section 4.6.2.2), MAY be used in the "NNDN" 3431 element: 3433 Created date and time of the NNDN object. 3435 Name of the NNDN in Unicode character set for the 3436 field element. 3438 IDN Table Identifier for the NNDN that matches 3439 an IDN Table Reference Object record, as defined in Section 5.5.2. 3441 Example of an "NNDN" element: 3443 ... 3444 3445 ... 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3458 NNDN-YYYYMMDD.csv 3459 3460 3461 3462 ... 3463 3464 ... 3466 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3467 contains two NNDN records for an IDN with one blocked variant and one 3468 mirrored variant. 3470 xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example, 3471 blocked,,2005-04-23T11:49:00.0Z 3472 xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example, 3473 mirrored,1,2005-04-23T11:49:00.0Z 3475 5.6.2.2. 3477 The is used to hold the deleted NNDN objects in a 3478 Differential or Incremental Deposit. The is split 3479 into separate CSV file definitions using named elements 3480 with the "name" attribute. The following section defines the 3481 supported NNDN deletes CSV file definition. 3483 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3485 The following "NNDN" field elements MUST be used in the deletes 3486 "NNDN" element: 3488 Fully-qualified name of the NNDN with 3489 type="eppcom:labelType" and isRequired="true". 3491 Example of an "NNDN" element. 3493 ... 3494 3495 ... 3496 3497 3498 3499 3500 3501 3503 NNDN-delete-YYYYMMDD.csv 3504 3505 3506 3507 ... 3508 3509 ... 3511 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3512 contains one NNDN records. 3514 xn--bc456-3ve.example 3516 5.7. EPP Parameters Object 3518 The EPP Parameters Object is a pseudo-object that defines the set of 3519 object and object extension services supported by the registry, as 3520 defined in [RFC5730]. The EPP Parameters Object is only defined as 3521 XML but could be used in the XML model or CSV model. The EPP 3522 Parameters Object is defined using the 3523 element. The EPP Parameters Object SHOULD be included if the 3524 registry supports EPP. Only one EPP Parameters Object MUST exist at 3525 a certain point in time (watermark). 3527 The syntax and content of the children 3528 elements is as explained in section 2.4 of [RFC5730]. The children 3529 of the are as follows: 3531 o One or more elements that indicate the EPP versions 3532 supported by the registry. 3534 o One or more elements that indicate the identifiers of the 3535 text response languages supported by the registry's EPP server. 3537 o One or more elements that contain namespace URIs 3538 representing the objects that the registry's EPP server is capable 3539 of managing. 3541 o An OPTIONAL element that contains one or more 3542 elements that contain namespace URIs representing object 3543 extensions supported by the registry's EPP server. 3545 o A element that contains child elements used to describe the 3546 server's privacy policy for data collection and management. See 3547 section 2.4 of [RFC5730] for more details. 3549 Example of element object: 3551 ... 3552 3553 1.0 3554 en 3555 urn:ietf:params:xml:ns:domain-1.0 3556 3557 urn:ietf:params:xml:ns:contact-1.0 3558 3559 urn:ietf:params:xml:ns:host-1.0 3560 3561 3562 urn:ietf:params:xml:ns:rgp-1.0 3563 urn:ietf:params:xml:ns:secDNS-1.1 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 ... 3584 5.8. Policy Object 3586 The Policy object is a pseudo-object that is used to specify which 3587 OPTIONAL elements from the XML Model are REQUIRED based on the 3588 business model of the registry. For the CSV Model, the OPTIONAL 3589 "isRequired" attribute of the elements, defined in 3590 Section 4.6.2.1, is used to specify which OPTIONAL fields are 3591 REQUIRED based on the business model of the registry. 3593 5.8.1. object 3595 The OPTIONAL contains the following attributes: 3597 o An that defines that the referenced is 3598 REQUIRED. 3600 o that defines the XPath of the element referenced by 3601 . 3603 Example of object: 3605 ... 3606 3608 ... 3610 5.9. Header Object 3612 The Header Object is a pseudo-object that is used to specify the 3613 number of objects in the repository at a specific point in time 3614 (watermark) regardless of the type of deposit: Differential, Full or 3615 Incremental Deposit. The Header Object may also be used to provide 3616 additional information on the contents of the deposit. The Header 3617 Object is only defined as XML but one header object MUST always be 3618 present per escrow deposit regardless of using XML Model or CSV 3619 Model. The Header Object is defined using the 3620 element. 3622 5.9.1. object 3624 The contains the following elements: 3626 o A choice of one of the elements defined in the 3627 "repositoryTypeGroup" group element that indicates the unique 3628 identifier for the repository being escrowed. Possible elements 3629 are: 3631 * A element that defines TLD or the RCDN being 3632 escrowed in the case of a Registry data escrow deposit. For 3633 IDNs the A-Label is used (see [RFC5891], Section 4.4). 3635 * A element that defines the Registrar ID 3636 corresponding to a Registrar data escrow deposit. In the case 3637 of an ICANN-accredited Registrar, the 3638 element MUST be the IANA Registrar ID assigned by ICANN. 3640 * A element that defines the provider ID 3641 corresponding to a Privacy and Proxy Services Provider data 3642 escrow deposit. In the case of an ICANN-accredited Privacy and 3643 Proxy Services Provider, the element MUST be 3644 the unique ID assigned by ICANN. 3646 * A element that defines the provider ID 3647 corresponding to a Reseller data escrow deposit. 3649 o A element that contains the number of objects in the SRS 3650 at a specific point in time (watermark) regardless of the type of 3651 deposit: Differential, Full or Incremental. The element 3652 supports the following attributes: 3654 * A "uri" attribute reflects the XML namespace URI of the primary 3655 objects for the XML Model and CSV Model. For example, the 3656 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3657 domain name objects using the XML Model, and the "uri" is set 3658 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3659 objects using the CSV Model. 3661 * An OPTIONAL "rcdn" attribute indicates the RCDN of the objects 3662 included in the element. For IDNs the A-Label is used 3663 [RFC5891], Section 4.4. If the "rcdn" attribute is present, 3664 the value of the element must include only objects 3665 related to registrations in the same and lower levels. For 3666 example in a data escrow deposit for the .EXAMPLE TLD, a value 3667 of "example" in the "rcdn" attribute within the element 3668 indicates the number of objects in the TLD including objects in 3669 other RCDNs within the TLD, whereas a value of "com.example" 3670 indicates the number of elements for objects under 3671 "com.example" and lower levels. Omitting the "rcdn" attribute 3672 indicates that the total includes all objects of the specified 3673 "uri" in the repository (e.g. the TLD, Registrar, or PPSP). 3675 * An OPTIONAL "registrarId" attribute indicates the identifier of 3676 the sponsoring Registrar of the objects included in the 3677 element. In the case of an ICANN-accredited Registrar, the 3678 value MUST be the IANA Registrar ID assigned by ICANN. 3680 o An OPTIONAL element that contains a tag that defines 3681 the expected content in the deposit. The producer and consumer of 3682 the deposits will coordinate the set of possible 3683 element values. 3685 Example of object referencing only the XML Model 3686 objects: 3688 ... 3689 3690 test 3691 2 3693 1 3695 1 3697 1 3699 3700 1 3702 1 3704 1 3706 3707 3708 ... 3710 Example of object referencing the CSV and XML 3711 Model objects: 3713 ... 3714 3715 test 3716 2 3718 1 3720 1 3722 1 3724 3725 1 3727 1 3729 1 3731 3732 3733 ... 3735 5.10. DNRD Common Objects Collection 3737 The DNRD Common Objects Collection contains data structures 3738 referenced by two or more of the main objects in the XML model. 3740 6. RDE IDN Variants handling 3742 Depending on the Registration Policy of the Registry, for a domain 3743 name there may be multiple variant names. See [variantTLDsReport] 3744 for further detail on IDN variants. 3746 A registry could choose to escrow IDN variants as domains or NNDN 3747 objects. A specific IDN variant can be represented in the escrow 3748 deposit, as a domain or as an NNDN object, but not both. 3750 If using domain objects to represent IDN variants, the normal 3751 behavior during restoration of an SRS based on an escrow deposit is 3752 to restore the IDN variants as a mirrored variant. If the 3753 registration data of the IDN variant is different from the original 3754 name, the details of this specific implementation MUST be described 3755 in the IDN policy document. 3757 An NNDN or a domain name are explicit representations of an IDN 3758 variant while an IDN variant computed based on an algorithm is an 3759 implicit representation. Explicit representation of an IDN variant 3760 takes precedence over an implicit representation. 3762 7. Profile 3764 Different business models of registries exist, therefore the registry 3765 is responsible for defining a profile that matches its particular 3766 business model. The profile mechanism allows a registry to extend 3767 this specification. 3769 A profile is the process of: 3771 1. Extending base objects with the mechanisms defined for XML and 3772 CSV models. 3774 * In the case of the XML model, abstract elements could be use 3775 to extend the following objects: , , , 3776 and using XML schema substitution groups 3777 feature. 3779 2. Defining a object to specify which OPTIONAL elements of 3780 this base specification is required based on the business model 3781 of the registry. An example is the element that is 3782 usually REQUIRED but it is specified as OPTIONAL in this 3783 specification to support some existing business models. 3785 3. Adding new escrowed objects using the and 3786 elements. 3788 4. Providing the XML schemas to third parties that require them to 3789 validate the escrow deposits. 3791 8. Data escrow agent extended verification process 3793 A Data Escrow Agent SHOULD perform an extended verification process 3794 that starts by creating a dataset to be tested. 3796 o If a Full Deposit is to be tested, the Full Deposit is the 3797 dataset. 3799 o If an Incremental Deposit is to be tested, the dataset is created 3800 by using the Incremental Deposit plus the last previous Full 3801 Deposit. 3803 o If a Differential Deposit is to be tested, the dataset is created 3804 by using the Differential Deposit plus all the required deposits 3805 leading to the last previous Full Deposit. 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 BEGIN and END tags are not part of the schema; they are used to 3844 note the beginning and ending of the schema for URI registration 3845 purposes. 3847 9.1. RDE CSV Schema 3849 BEGIN 3850 3852 3859 3862 3863 3865 3866 3867 Registry Data Escrow Comma-Seperated Values (CSV) 3868 3869 3871 3872 3874 3875 3876 3877 3878 3879 3880 3881 3882 3884 3885 3886 3887 3888 3889 3890 3892 3893 3896 3897 3898 3900 3901 3902 3903 3904 3905 3907 3909 3910 3911 3913 3914 3915 3916 3917 3918 3920 3922 3923 3924 3926 3928 3929 3931 3932 3933 3934 3935 3937 3938 3939 3940 3941 3942 3943 3944 3946 3947 3948 3950 3951 3953 3954 3955 3956 3957 3959 3960 3961 3963 3964 3966 3967 3968 3969 3970 3972 3973 3974 3976 3977 3981 3982 3983 3985 3987 3989 3990 3992 3994 3996 3997 3999 4001 4003 4005 4007 4009 4011 4013 4015 4016 4017 4018 4019 4021 4022 4023 4024 4025 4026 4027 4028 4030 4031 4032 4034 4035 4038 4040 4042 4043 4045 4046 4048 4050 4051 4052 4053 4054 4056 4057 4058 4059 4060 4061 4062 4063 4065 4066 4067 4069 4070 4071 4072 4073 4074 4076 4077 4078 4079 4080 4081 4082 4083 4086 4087 4088 4090 4091 4092 4093 4094 4095 4097 4098 4099 4100 4101 4102 4103 4104 4106 4107 4108 4110 4111 4112 4113 4114 4115 4117 4118 4119 4120 4121 4122 4123 4124 4126 4127 4128 4130 4131 4132 4133 4134 4135 4137 4138 4139 4140 4141 4142 4143 4144 4146 4147 4148 4150 4151 4153 4154 4155 4156 4157 4159 4160 4161 4163 4164 4167 4168 4170 4171 4172 4173 4174 4176 4177 4178 4179 4180 4181 4182 4183 4184 4186 4187 4188 4190 4191 4192 4193 4194 4195 4197 4198 4199 4201 4202 4203 4204 4205 4206 4208 4209 4210 4212 4213 4215 4216 4217 4218 4219 4220 4222 4223 4224 4226 4227 4228 4229 4230 4231 4233 4234 4235 4236 4238 4239 4241 4242 4243 4244 4245 4246 4248 4249 4251 4252 4253 4255 4256 4258 4259 4260 4261 4262 4264 4265 4266 4268 4271 4272 END 4274 9.2. RDE Domain Object 4276 BEGIN 4277 4278 4290 4291 4292 4293 4294 4295 4296 4298 4299 4300 Registry Data Escrow Domain provisioning schema 4301 4302 4304 4307 4309 4313 4314 4315 4316 4317 4318 4320 4322 4324 4326 4328 4330 4333 4335 4338 4340 4342 4344 4346 4348 4350 4352 4354 4356 4359 4360 4361 4362 4364 4365 4366 4368 4370 4372 4374 4376 4378 4379 4381 4382 4383 4384 4385 4386 4389 4390 4391 4392 4393 4394 END 4396 9.3. CSV Domain Object 4398 BEGIN 4399 4401 4412 4415 4416 4417 4418 4419 4420 4422 4423 4424 Domain Name Comma-Separated Values (CSV) Object 4425 4426 4428 4431 4434 4435 4436 4437 4438 4439 4440 4441 4442 4444 4447 4450 4451 4452 4453 4454 4455 4456 4457 4458 4460 4461 4464 4465 4468 4469 4470 4471 4472 4474 4475 4476 4478 4479 4482 4483 4484 4485 4486 4488 4489 4490 4492 4494 4495 4497 4498 4499 4500 4501 4503 4504 4505 4507 4508 4511 4512 4515 4516 4519 4520 4523 4524 4527 4528 4531 4532 4535 4536 4538 4539 4540 4541 4542 4544 4545 4546 4548 4549 4552 4553 4557 4558 4561 4562 4563 4564 4565 4566 4568 4569 4570 4572 4575 4576 END 4578 9.4. RDE Host Object 4580 BEGIN 4581 4582 4591 4592 4593 4594 4596 4597 4598 Registry Data Escrow Host provisioning schema 4599 4600 4602 4604 4605 4608 4609 4610 4611 4612 4613 4615 4617 4619 4622 4624 4626 4628 4630 4632 4634 4635 4636 4637 4639 4640 4641 4642 4643 4644 4646 4648 4649 4650 4651 4652 4653 END 4655 9.5. CSV Host Object 4657 BEGIN 4658 4660 4669 4672 4673 4674 4675 4677 4678 4679 Host Comma-Separated Values (CSV) Object 4680 4681 4683 4686 4689 4690 4691 4692 4693 4694 4695 4696 4697 4699 4702 4705 4706 4707 4708 4709 4710 4711 4712 4713 4715 4716 4719 4720 4722 4723 4724 4725 4726 4728 4729 4730 4732 4733 4735 4736 4737 4738 4739 4741 4742 4743 4745 4746 4749 4750 4751 4752 4753 4754 4756 4757 4758 4760 4763 4764 END 4766 9.6. RDE Contact Object 4768 BEGIN 4769 4770 4779 4780 4781 4782 4783 4785 4786 4787 Registry Data Escrow contact provisioning schema 4788 4789 4791 4794 4796 4800 4801 4802 4803 4804 4805 4807 4809 4811 4813 4815 4817 4819 4821 4823 4825 4827 4829 4831 4833 4835 4836 4837 4838 4840 4841 4842 4843 4844 4845 4846 4847 4848 4850 4851 4852 4853 4854 4855 4858 4859 4860 4861 4862 4863 END 4865 9.7. CSV Contact Object 4867 BEGIN 4868 4870 4879 4882 4883 4884 4885 4887 4888 4889 Contact Comma-Separated Values (CSV) Object 4890 4891 4892 4895 4898 4899 4900 4901 4902 4903 4904 4905 4906 4908 4911 4914 4915 4916 4917 4918 4919 4920 4921 4922 4924 4925 4927 4928 4929 4930 4931 4933 4934 4935 4937 4938 4942 4943 4945 4947 4948 4949 4950 4951 4953 4954 4955 4957 4958 4960 4963 4964 4966 4967 4968 4969 4970 4972 4973 4974 4976 4980 4982 4983 4984 4985 4986 4988 4989 4990 4992 4993 4994 4995 4996 4997 4999 5000 5001 5002 5004 5005 5006 5007 5008 5009 5011 5012 5013 5014 5016 5017 5020 5021 5024 5025 5026 5028 5029 5030 5031 5032 5034 5035 5036 5038 5039 5042 5043 5046 5047 5049 5050 5051 5052 5053 5055 5056 5057 5058 5060 5061 5063 5064 5065 5066 5067 5069 5070 5071 5072 5074 5075 5078 5080 5082 5084 5086 5088 5090 5092 5094 5096 5098 5100 5102 5104 5106 5108 5110 5112 5114 5116 5117 5118 5119 5120 5122 5123 5124 5125 5126 5129 5130 5131 5132 5133 5134 5136 5137 5138 5140 5143 5144 END 5146 9.8. RDE Registrar Object 5148 BEGIN 5149 5150 5159 5160 5161 5162 5163 5165 5166 5167 Registry Data Escrow registrar provisioning schema 5168 5169 5171 5174 5176 5179 5180 5181 5182 5183 5184 5186 5188 5190 5192 5195 5197 5199 5201 5203 5205 5207 5209 5210 5211 5212 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5228 5229 5230 5232 5233 5236 5238 5239 5240 5241 5242 5243 5245 5246 5247 5250 5252 5255 5257 5259 5260 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5274 5275 5276 5277 5278 5280 5281 5282 5283 5284 5286 5287 5288 5290 5292 5293 5295 5296 5297 5298 5299 5300 5303 5304 5305 5306 5307 5308 END 5310 9.9. CSV Registrar Object 5312 BEGIN 5313 5315 5325 5328 5329 5330 5331 5332 5334 5335 5336 Registar Comma-Separated Values (CSV) Object 5337 5338 5340 5343 5346 5347 5348 5349 5350 5351 5352 5353 5354 5356 5359 5362 5363 5364 5365 5366 5367 5368 5369 5370 5372 5373 5376 5377 5380 5381 5382 5383 5384 5385 5387 5388 5389 5390 5392 5393 5397 5398 5400 5402 5403 5404 5405 5406 5408 5409 5411 5413 5414 5415 5416 5417 5418 5419 5420 5422 5423 5424 5425 5426 5427 5428 5429 5431 5432 5436 5439 5440 END 5442 9.10. RDE IDN Table Reference Objects 5444 BEGIN 5445 5446 5452 5454 5455 5456 Registry Data Escrow IDN provisioning schema 5457 5459 5461 5463 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5479 5480 5481 5482 5483 5484 5485 5486 5487 5489 5490 5491 5492 5493 5494 5495 5497 5498 END 5500 9.11. CSV IDN Language Object 5502 BEGIN 5503 5505 5512 5515 5516 5518 5519 5520 IDN Language Comma-Separated Values (CSV) Object 5521 5522 5524 5527 5530 5531 5532 5533 5534 5535 5536 5537 5538 5540 5543 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5558 5559 END 5561 9.12. EPP Parameters Object 5563 BEGIN 5564 5565 5573 5574 5575 5577 5578 5579 Registry Data Escrow EPP Parameters schema 5580 5581 5583 5584 5587 5588 5591 5592 5593 5594 5595 5597 5599 5601 5604 5606 5607 5608 5609 5610 5611 END 5613 9.13. NNDN Object 5615 BEGIN 5616 5617 5625 5626 5627 5629 5630 5631 Registry Data Escrow NNDN provisioning schema 5632 5633 5635 5637 5638 5641 5642 5643 5644 5645 5646 5648 5650 5652 5654 5656 5658 5659 5660 5661 5663 5664 5665 5666 5667 5668 5669 5671 5672 5673 5674 5676 5677 5678 5680 5681 5682 5683 5684 5685 5688 5689 5690 5691 5692 5693 END 5695 9.14. CSV NNDN Object 5697 BEGIN 5698 5700 5708 5711 5712 5713 5715 5716 5717 NNDN (NNDN's not domain name) (CSV) Object 5718 5719 5721 5724 5727 5728 5729 5730 5731 5732 5733 5734 5735 5737 5740 5742 5743 5744 5745 5746 5747 5748 5749 5750 5752 5753 5756 5757 5760 5761 5765 5766 5769 5770 5771 5772 5773 5775 5776 5777 5779 5780 5784 5787 5788 END 5790 9.15. Policy Object 5792 BEGIN 5793 5794 5800 5801 5802 Registry Data Escrow Policy schema 5803 5804 5806 5807 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 END 5821 9.16. Header Object 5823 BEGIN 5824 5825 5832 5833 5835 5836 5837 Data Escrow Deposit Header schema 5839 5840 5842 5843 5846 5847 5848 5849 5850 5851 5852 5854 5856 5857 5858 5859 5861 5862 5863 5864 5865 5866 5867 5868 5870 5871 5872 5873 5874 5875 5876 5877 5878 5880 5881 END 5883 9.17. DNRD Common Objects 5885 BEGIN 5886 5887 5893 5895 5896 5897 Data Escrow Deposit Common Objects schema 5898 5899 5901 5902 5903 5904 5905 5906 5907 5909 5910 END 5912 10. Internationalization Considerations 5914 Data Escrow deposits are represented in XML, which provides native 5915 support for encoding information using the Unicode character set and 5916 its more compact representations including UTF-8. Conformant XML 5917 processors recognize both UTF-8 and UTF-16. Though XML includes 5918 provisions to identify and use other character encodings through use 5919 of an "encoding" attribute in an declaration, use of UTF-8 is 5920 RECOMMENDED. 5922 11. IANA Considerations 5924 This document uses URNs to describe XML namespaces and XML schemas 5925 conforming to a registry mechanism described in [RFC3688]. Fourteen 5926 URI assignments have been registered by the IANA. 5928 Registration request for the RDE CSV namespace: 5930 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 5931 Registrant Contact: IESG 5933 Note to RFC Editor: Please remove the email address from the RFC 5934 after IANA records it. 5936 XML: None. Namespace URIs do not represent an XML specification. 5938 Registration request for the RDE CSV XML schema: 5940 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 5942 Registrant Contact: IESG 5944 Note to RFC Editor: Please remove the email address from the RFC 5945 after IANA records it. 5947 See section Section 9.1 of this document. 5949 Registration request for the RDE domain namespace: 5951 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 5953 Registrant Contact: IESG 5955 Note to RFC Editor: Please remove the email address from the RFC 5956 after IANA records it. 5958 XML: None. Namespace URIs do not represent an XML specification. 5960 Registration request for the RDE domain XML schema: 5962 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 5964 Registrant Contact: IESG 5966 Note to RFC Editor: Please remove the email address from the RFC 5967 after IANA records it. 5969 See section Section 9.2 of this document. 5971 Registration request for the CSV domain namespace: 5973 URI: urn:ietf:params:xml:ns:csvDomain-1.0 5975 Registrant Contact: IESG 5977 Note to RFC Editor: Please remove the email address from the RFC 5978 after IANA records it. 5980 XML: None. Namespace URIs do not represent an XML specification. 5982 Registration request for the CSV domain XML schema: 5984 URI: urn:ietf:params:xml:schema:csvDomain-1.0 5986 Registrant Contact: IESG 5988 Note to RFC Editor: Please remove the email address from the RFC 5989 after IANA records it. 5991 See section Section 9.3 of this document. 5993 Registration request for the RDE host namespace: 5995 URI: urn:ietf:params:xml:ns:rdeHost-1.0 5997 Registrant Contact: IESG 5999 Note to RFC Editor: Please remove the email address from the RFC 6000 after IANA records it. 6002 XML: None. Namespace URIs do not represent an XML specification. 6004 Registration request for the RDE host XML schema: 6006 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6008 Registrant Contact: IESG 6010 Note to RFC Editor: Please remove the email address from the RFC 6011 after IANA records it. 6013 See section Section 9.4 of this document. 6015 Registration request for the CSV host namespace: 6017 URI: urn:ietf:params:xml:ns:csvHost-1.0 6019 Registrant Contact: IESG 6021 Note to RFC Editor: Please remove the email address from the RFC 6022 after IANA records it. 6024 XML: None. Namespace URIs do not represent an XML specification. 6026 Registration request for the CSV host XML schema: 6028 URI: urn:ietf:params:xml:schema:csvHost-1.0 6030 Registrant Contact: IESG 6032 Note to RFC Editor: Please remove the email address from the RFC 6033 after IANA records it. 6035 See section Section 9.5 of this document. 6037 Registration request for the RDE contact namespace: 6039 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6041 Registrant Contact: IESG 6043 Note to RFC Editor: Please remove the email address from the RFC 6044 after IANA records it. 6046 XML: None. Namespace URIs do not represent an XML specification. 6048 Registration request for the RDE contact XML schema: 6050 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6052 Registrant Contact: IESG 6054 Note to RFC Editor: Please remove the email address from the RFC 6055 after IANA records it. 6057 See section Section 9.6 of this document. 6059 Registration request for the CSV contact namespace: 6061 URI: urn:ietf:params:xml:ns:csvContact-1.0 6063 Registrant Contact: IESG 6065 Note to RFC Editor: Please remove the email address from the RFC 6066 after IANA records it. 6068 XML: None. Namespace URIs do not represent an XML specification. 6070 Registration request for the CSV contact XML schema: 6072 URI: urn:ietf:params:xml:schema:csvContact-1.0 6074 Registrant Contact: IESG 6075 Note to RFC Editor: Please remove the email address from the RFC 6076 after IANA records it. 6078 See section Section 9.7 of this document. 6080 Registration request for the RDE registrar namespace: 6082 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6084 Registrant Contact: IESG 6086 Note to RFC Editor: Please remove the email address from the RFC 6087 after IANA records it. 6089 XML: None. Namespace URIs do not represent an XML specification. 6091 Registration request for the RDE registrar XML schema: 6093 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6095 Registrant Contact: IESG 6097 Note to RFC Editor: Please remove the email address from the RFC 6098 after IANA records it. 6100 See section Section 9.8 of this document. 6102 Registration request for the CSV registrar namespace: 6104 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6106 Registrant Contact: IESG 6108 Note to RFC Editor: Please remove the email address from the RFC 6109 after IANA records it. 6111 XML: None. Namespace URIs do not represent an XML specification. 6113 Registration request for the CSV registrar XML schema: 6115 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6117 Registrant Contact: IESG 6119 Note to RFC Editor: Please remove the email address from the RFC 6120 after IANA records it. 6122 See section Section 9.9 of this document. 6124 Registration request for the RDE IDN namespace: 6126 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6128 Registrant Contact: IESG 6130 Note to RFC Editor: Please remove the email address from the RFC 6131 after IANA records it. 6133 XML: None. Namespace URIs do not represent an XML specification. 6135 Registration request for the RDE IDN XML schema: 6137 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6139 Registrant Contact: IESG 6141 Note to RFC Editor: Please remove the email address from the RFC 6142 after IANA records it. 6144 See section Section 9.10 of this document. 6146 Registration request for the CSV IDN namespace: 6148 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6150 Registrant Contact: IESG 6152 Note to RFC Editor: Please remove the email address from the RFC 6153 after IANA records it. 6155 XML: None. Namespace URIs do not represent an XML specification. 6157 Registration request for the CSV IDN XML schema: 6159 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6161 Registrant Contact: IESG 6163 Note to RFC Editor: Please remove the email address from the RFC 6164 after IANA records it. 6166 See section Section 9.11 of this document. 6168 Registration request for the RDE EPP parameters namespace: 6170 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6171 Registrant Contact: IESG 6173 Note to RFC Editor: Please remove the email address from the RFC 6174 after IANA records it. 6176 XML: None. Namespace URIs do not represent an XML specification. 6178 Registration request for the RDE EPP parameters XML schema: 6180 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6182 Registrant Contact: IESG 6184 Note to RFC Editor: Please remove the email address from the RFC 6185 after IANA records it. 6187 See section Section 9.12 of this document. 6189 Registration request for the RDE NNDN namespace: 6191 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6193 Registrant Contact: IESG 6195 Note to RFC Editor: Please remove the email address from the RFC 6196 after IANA records it. 6198 XML: None. Namespace URIs do not represent an XML specification. 6200 Registration request for the RDE NNDN XML schema: 6202 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6204 Registrant Contact: IESG 6206 Note to RFC Editor: Please remove the email address from the RFC 6207 after IANA records it. 6209 See section Section 9.13 of this document. 6211 Registration request for the CSV NNDN namespace: 6213 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6215 Registrant Contact: IESG 6217 Note to RFC Editor: Please remove the email address from the RFC 6218 after IANA records it. 6220 XML: None. Namespace URIs do not represent an XML specification. 6222 Registration request for the CSV NNDN XML schema: 6224 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6226 Registrant Contact: IESG 6228 Note to RFC Editor: Please remove the email address from the RFC 6229 after IANA records it. 6231 See section Section 9.14 of this document. 6233 Registration request for the RDE Policy namespace: 6235 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6237 Registrant Contact: IESG 6239 Note to RFC Editor: Please remove the email address from the RFC 6240 after IANA records it. 6242 XML: None. Namespace URIs do not represent an XML specification. 6244 Registration request for the RDE Policy XML schema: 6246 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6248 Registrant Contact: IESG 6250 Note to RFC Editor: Please remove the email address from the RFC 6251 after IANA records it. 6253 See section Section 9.15 of this document. 6255 Registration request for the RDE Header namespace: 6257 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6259 Registrant Contact: IESG 6261 Note to RFC Editor: Please remove the email address from the RFC 6262 after IANA records it. 6264 XML: None. Namespace URIs do not represent an XML specification. 6266 Registration request for the RDE Header XML schema: 6268 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6270 Registrant Contact: IESG 6272 Note to RFC Editor: Please remove the email address from the RFC 6273 after IANA records it. 6275 See section Section 9.16 of this document. 6277 Registration request for the RDE Common Objects namespace: 6279 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6281 Registrant Contact: IESG 6283 Note to RFC Editor: Please remove the email address from the RFC 6284 after IANA records it. 6286 XML: None. Namespace URIs do not represent an XML specification. 6288 Registration request for the RDE Common Objects XML schema: 6290 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6292 Registrant Contact: IESG 6294 Note to RFC Editor: Please remove the email address from the RFC 6295 after IANA records it. 6297 See section Section 9.17 of this document. 6299 12. Implementation Status 6301 Note to RFC Editor: Please remove this section and the reference to 6302 RFC 7942 [RFC7942] before publication. 6304 This section records the status of known implementations of the 6305 protocol defined by this specification at the time of posting of this 6306 Internet-Draft, and is based on a proposal described in RFC 7942 6307 [RFC7942]. The description of implementations in this section is 6308 intended to assist the IETF in its decision processes in progressing 6309 drafts to RFCs. Please note that the listing of any individual 6310 implementation here does not imply endorsement by the IETF. 6311 Furthermore, no effort has been spent to verify the information 6312 presented here that was supplied by IETF contributors. This is not 6313 intended as, and must not be construed to be, a catalog of available 6314 implementations or their features. Readers are advised to note that 6315 other implementations may exist. 6317 According to RFC 7942 [RFC7942], "this will allow reviewers and 6318 working groups to assign due consideration to documents that have the 6319 benefit of running code, which may serve as evidence of valuable 6320 experimentation and feedback that have made the implemented protocols 6321 more mature. It is up to the individual working groups to use this 6322 information as they see fit". 6324 12.1. Implementation in the gTLD space 6326 Organization: ICANN 6328 Name: ICANN Registry Agreement 6330 Description: the ICANN Base Registry Agreement requires Registries, 6331 Data Escrow Agents, and ICANN to implement this specification. ICANN 6332 receives daily notifications from Data Escrow Agents confirming that 6333 more than 1,200 gTLDs are sending deposits that comply with this 6334 specification. ICANN receives on a weekly basis per gTLD, from more 6335 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6336 also complies with this specification. In addition, ICANN is aware 6337 of Registry Service Provider transitions using data files that 6338 conform to this specification. 6340 Level of maturity: production. 6342 Coverage: all aspects of this specification are implemented. 6344 Version compatibility: versions 03 - 08 are known to be implemented. 6346 Contact: gustavo.lozano@icann.org 6348 URL: https://www.icann.org/resources/pages/registries/registries- 6349 agreements-en 6351 13. Security Considerations 6353 This specification does not define the security mechanisms to be used 6354 in the transmission of the data escrow deposits, since it only 6355 specifies the minimum necessary to enable the rebuilding of a 6356 registry from deposits without intervention from the original 6357 registry. 6359 Depending on local policies, some elements, or, most likely, the 6360 whole deposit will be considered confidential. As such, the parties 6361 SHOULD take all the necessary precautions such as encrypting the data 6362 at rest and in transit to avoid inadvertent disclosure of private 6363 data. Regardless of the precautions taken by the parties regarding 6364 data at rest and in transit, authentication credentials MUST NOT be 6365 escrowed. 6367 Authentication of the parties passing data escrow deposit files is 6368 also of the utmost importance. The escrow agent MUST properly 6369 authenticate the identity of the registry before accepting data 6370 escrow deposits. In a similar manner, the registry MUST authenticate 6371 the identity of the escrow agent before submitting any data. 6373 Additionally, the registry and the escrow agent MUST use integrity 6374 checking mechanisms to ensure the data transmitted is what the source 6375 intended. Validation of the contents by the escrow agent is 6376 RECOMMENDED to ensure not only that the file was transmitted 6377 correctly from the registry, but also that the contents are 6378 "meaningful". 6380 Note: if Transport Layer Security (TLS) is used when providing an 6381 escrow services, the recommendations in [RFC7525] MUST be 6382 implemented. 6384 14. Privacy Considerations 6386 This specification defines a format that may be used to escrow 6387 personal data. The process of data escrow is governed by a legal 6388 document agreed by the parties, and such legal document must ensure 6389 that privacy-sensitive and/or personal data receives the required 6390 protection. 6392 15. Acknowledgments 6394 Parts of this document are based on EPP [RFC5730] and related RFCs by 6395 Scott Hollenbeck. 6397 Special suggestions that have been incorporated into this document 6398 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6399 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6400 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6401 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6402 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6403 Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. 6405 Shoji Noguchi and Francisco Arias participated as co-authors until 6406 version 05 providing invaluable support for this document. 6408 16. Change History 6410 [[RFC Editor: Please remove this section.]] 6412 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6413 dnrd-objects-mapping-00 6415 1. Added definition for child elements under the element. 6417 2. Added definition for child elements under the element. 6419 3. Added definition for child elements under the element. 6421 4. Rewrote the IDN Variants Handling section to use the variant 6422 states as described in ICANN's Study of Issues Related to the 6423 Management of IDN Variant TLDs. 6425 5. Renamed to in the . 6427 6. Renamed to in the element. 6429 7. Renamed to in the element. 6431 8. Added element under element. 6433 9. Fixed some typographical errors and omissions. 6435 16.2. Changes from 00 to 01 6437 1. Specify OPTIONAL elements in the draft. 6439 2. Added NNDN object to support list of reserved names and different 6440 IDN variants models. 6442 3. Removed subordinated host element from the domain object. 6444 4. Added eppParams object. 6446 5. Added variantGenerator element to the domain object. 6448 6. Added lgr to the IDN table object. 6450 16.3. Changes from 01 to 02 6452 1. Updates to the all objects based on feedback from the list. 6454 2. Start of XML and CSV drafts merge. 6456 3. Added header object. 6458 4. Added report object. 6460 5. Added notification object. 6462 6. Added Data Escrow Agent Extended Verification Process section. 6464 7. Added Notifications from Registries to Third Parties. 6466 8. Added Notifications from Data Escrow Agents to Third Parties. 6468 9. Added FULL, DIFF deposit examples using the XML model only. 6470 16.4. Changes from 02 to 03 6472 1. Remove authinfo from the XML Schema. 6474 2. Resend attribute is now an element 6476 3. Scope attribute added to policy object. 6478 16.5. Changes from 03 to 04 6480 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6481 arias-noguchi-dnrd-objects-mapping-02. 6483 2. Changed the cksum attribute of to use CRC32 and 6484 changed all of the sample cksum values to use CRC32, based on 6485 feedback from David Kipling. 6487 3. Changed the optional element to be an optional 6488 "sep" attribute value of the element with a default 6489 value of "," based on feedback from David Kipling. 6491 4. Added support for the optional "parent" attribute for the to the 6492 CSV fields to indicate a field as a reference to a parent 6493 object, based on feedback from David Kipling. 6495 5. Added support for the CSV model for the NNDN. 6497 6. Added support to delete hosts based on roid. 6499 7. Added mirrored state to NNDN 6501 8. Minor fixes to XML XSDs. 6503 9. The Report and Notification objects were moved to draft-lozano- 6504 icann-registry-interfaces 6506 10. The section Data escrow notifications was moved to draft-lozano- 6507 icann-registry-interfaces 6509 11. Removed references to the , , and 6510 from the "hostStatuses" and "hostAddresses" CSV 6511 files. 6513 12. Removed references to the , , and 6514 from the "contactStatuses" CSV file. 6516 13. Removed references to the , , and 6517 from the "domainContacts", "domainStatuses", 6518 and "domainNameServers" CSV files. 6520 14. Changed to . 6522 15. Replaced use of to new field 6523 in the "domain", "idnLanguage", and "NNDN" CSV files. 6525 16. Replaced use of with in the 6526 "host" element. 6528 17. Changed the foreign key of the hosts to use 6529 instead of and removed use of in 6530 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6531 files. 6533 18. Added use of the MUST keyword for CSV fields that are required 6534 to be supported in an EPP based system. 6536 19. Removed use of the field element for the 6537 "registrar" CSV file. 6539 20. Added definition of field element. 6541 16.6. Changes from 04 to 05 6543 1. Updated the examples of the full and differential deposits using 6544 the CSV and XML model. 6546 2. Made optional for the "domainTransfer" CSV file 6547 to match the XML definition. 6549 3. Made optional for the "domain" CSV file 6550 to match the XML definition. 6552 4. Made optional for the "domain" and "contact" CSV 6553 files to match the XML definition. 6555 5. Change from IDREF to idType. 6557 6. Minor editorial changes. 6559 16.7. Changes from 05 to 06 6561 1. Revised the differential and incremental deposits for the CSV 6562 format to use cascade update / replace and delete from the parent 6563 object to be consistent with the XML format. 6565 2. Revised the structure of the CSV format sections to utilize sub- 6566 sections instead of a list for the CSV file definitions. 6568 3. Added the "CSV Parent Child Relationship" section to describe the 6569 concept of parent child relationships across CSV file 6570 definitions. 6572 4. Added the "domainNameServersAddresses" CSV File Definition 6573 section to support the domain host attributes model of [RFC5731]. 6575 5. Made the required fields in the CSV format consistent with the 6576 XML format. The CSV fields updated to be required include: 6577 , , , 6578 , , , 6579 , , , 6580 , , , 6581 , , 6582 , , , 6583 , , 6584 , and . 6586 6. Revised the CSV examples to use a more realistic set of records. 6588 16.8. Changes from 06 to 07 6590 1. Created "repositoryTypeGroup" group element in the rdeHeader 6591 including the , and 6592 elements. 6594 2. Added the optional "rcdn" and "registrarId" attributes to the 6595 element 6597 16.9. Changes from 07 to 08 6599 1. The following registrar elements were made optional to support 6600 greater flexibility for the implementation of policies: status, 6601 postalInfo, email and crDate. 6603 2. The following domain name elements were made optional to support 6604 greater flexibility for the implementation of policies: crRr. 6606 16.10. Changes from 08 to 09 6608 1. Implementation Status section was added 6610 16.11. Changes from 09 to 10 6612 1. Editorial changes in section Section 5.1.2.1.6. 6614 2. Added MAY clause when the DS Data Interface is used in section 6615 Section 5.1.2.1.6. 6617 16.12. Changes from 10 to REGEXT 00 6619 1. Internet Draft (I-D) adopted by the REGEXT WG. 6621 16.13. Changes REGEXT 00 to REGEXT 01 6623 1. Added the element to the 6624 "repositoryTypeGroup" group element in the rdeHeader. 6626 2. Privacy consideration section was added 6628 3. Updates on section 8 6630 16.14. Changes REGEXT 01 to REGEXT 02 6632 1. Added a choice between the use of the or 6633 fields in the CSV "domain", "host", and 6634 "contact" definitions. 6636 2. Added a choice between the use of the or 6637 fields in the CSV "domainNameServers" 6638 definition. 6640 3. Changed "of client" to "of the client" throughout the document. 6642 4. Modified all references of 'The attribute isRequired MUST equal 6643 "true".' to 'The attribute "isRequired" MUST equal "true".' 6645 5. Combined the and 6646 fields in a single required list for the CSV "domainContacts" 6647 definition. 6649 6. Combined the , , and 6650 fields in a single required list for the 6651 CSV "domainStatuses" definition. 6653 7. Moved the the fields to the MAY 6654 list for the CSV "domain", "host", and "contact" definitions. 6656 8. Made the order of the , , 6657 , and fields more consistent in the 6658 CSV lists. 6660 9. Fixed an error in the order of the object example. 6662 10. Changed to be optional to match being 6663 optional in the XML model, by having it use type 6664 rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and 6665 ensuring that is included in the MAY field 6666 lists and not the MUST field lists. 6668 11. Made optional for the "domain" CSV definition 6669 to be consistent with the XML model, by removing the sentence 6670 'The attribute "isRequired" MUST equal "true".' from the 6671 description and moving the field to the MAY field list. 6673 12. Made optional for the "domain" and "contact" 6674 CSV definitions to be consistent with the XML model, by moving 6675 the field to the MAY field list. 6677 13. Made optional to be consistent with the XML 6678 model, by having it use type rdeCsv:fClIDType instead of 6679 rdeCsv:fClIDRequiredType. 6681 14. Made required to be consistent with the XML 6682 model, by having it use type rdeCsv:fClIDRequiredType instead of 6683 rdeCsv:fClIDType. 6685 15. Made the field in the "host", "contact", 6686 and "registrar" CSV definitions required explicitly by removing 6687 'and isRequired="true"' and adding the sentence 'The attribute 6688 isRequired MUST equal "true".', when it is chosen as the primary 6689 field. 6691 16. Removed extra '/>.' at the end of the field 6692 description in the "hostStatuses" CSV definition. 6694 17. Made the field optional to be consistent 6695 with the XML model, by having csvRegistrar:fStatusType extend 6696 rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. 6698 18. Made the field for the "registrar" CSV 6699 definition explicitly optional to be consistent with the XML 6700 model, by adding the sentence 'The attribute isRequired MUST 6701 equal "false".' to the field description and including the 6702 definition of isRequired="false" in the "registrar" CSV 6703 definition examples. 6705 19. Added the choice between the use of the and 6706 fields in the deletes "registrar" CSV 6707 definition to be consistent with the "registrar" CSV definition. 6709 20. Made the and elements optional for the host and 6710 contact objects in the XML model to be consistent with the 6711 domain object. 6713 16.15. Changes REGEXT 02 to REGEXT 03 6715 1. Added the optional element contentTag in the header object. 6717 2. Editorial updates. 6719 16.16. Changes REGEXT 03 to REGEXT 04 6721 1. Note: Updates from version REGEXT 03 to REGEXT 04 attend the 6722 feedback provided during the document shepherd review. 6724 2. Editorial updates. 6726 3. Examples now use domain names from the .example TLD. 6728 4. The introduction was enhanced by explaining the need for data 6729 escrow and the proposed solution. 6731 5. Explanation regarding NNDN was improved. 6733 6. Explanation regarding the CSV and XML model was improved. 6735 7. Section 4.5 updated to make the text clearer. 6737 8. draft-arias-noguchi-registry-data-escrow is now referenced from 6738 the I-D repository. 6740 9. The XML prefix "rdeDomain" is now consistently used. 6742 10. The prevID attribute was removed from the examples of full 6743 deposits. 6745 11. The examples were updated to use present dates. 6747 16.17. Changes REGEXT 04 to REGEXT 05 6749 1. draft-ietf-regext-data-escrow (version 04) is now referenced from 6750 the I-D repository. 6752 2. The example in idnLanguage CSV file definition updated to use the 6753 sep attribute. 6755 3. The reference in the example in hostAddresses CSV file definition 6756 was updated. 6758 4. Moved [RFC0791] and [RFC4291] to the Normative References 6759 section. 6761 16.18. Changes REGEXT 05 to REGEXT 06 6763 1. Changes based on the feedback provided here: 6764 https://mailarchive.ietf.org/arch/msg/regext/ 6765 nA8eTYIrXJ44_6ullQlRLW6T74s 6767 16.19. Changes REGEXT 06 to REGEXT 07 6769 1. Changes based on the feedback provided here: 6770 https://mailarchive.ietf.org/arch/msg/regext/hDLz2ym4oR-ukA4Fm- 6771 QJ8FzaxxE 6773 2. Changes based on the feedback provided here: 6774 https://mailarchive.ietf.org/arch/msg/regext/780Xw- 6775 z1RMRb79nmZ6ABmRTo1fU 6777 16.20. Changes REGEXT 07 to REGEXT 08 6779 1. Changes based on the feedback provided here: 6780 https://mailarchive.ietf.org/arch/msg/regext/ 6781 UaMNvl1xh60ldjpqHHYc3TNsfhg 6783 2. Changes based on the feedback provided here: 6784 https://mailarchive.ietf.org/arch/msg/regext/ 6785 B3QTxUCWUE4R_QharAQlA3041j0 6787 16.21. Changes REGEXT 08 to REGEXT 09 6789 1. Changes based on the feedback provided here: 6790 https://mailarchive.ietf.org/arch/msg/regext/ 6791 EmKW32exlPgLbBUIbS8OjdYUJWc 6793 17. Example of a Full Deposit using the XML model 6795 Example of a Full Deposit using the XML model: 6797 6798 6814 2019-10-17T00:00:00Z 6815 6816 1.0 6817 urn:ietf:params:xml:ns:rdeHeader-1.0 6818 6819 urn:ietf:params:xml:ns:rdeContact-1.0 6820 6821 urn:ietf:params:xml:ns:rdeHost-1.0 6822 6823 urn:ietf:params:xml:ns:rdeDomain-1.0 6824 6825 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6826 6827 urn:ietf:params:xml:ns:rdeIDN-1.0 6828 6829 urn:ietf:params:xml:ns:rdeNNDN-1.0 6830 6831 urn:ietf:params:xml:ns:rdeEppParams-1.0 6832 6833 6834 6835 6836 6837 6838 test 6839 2 6841 6842 1 6844 6845 1 6847 6848 1 6850 6851 1 6853 6854 1 6856 6857 1 6859 6860 6862 6863 6864 example1.example 6865 Dexample1-TEST 6866 6867 jd1234 6868 sh8013 6869 sh8013 6870 6871 ns1.example.com 6872 ns1.example1.example 6873 6874 RegistrarX 6875 RegistrarX 6876 1999-04-03T22:00:00.0Z 6877 2015-04-03T22:00:00.0Z 6878 6880 6881 6882 example2.example 6883 Dexample2-TEST 6884 6885 6886 jd1234 6887 sh8013 6888 sh8013 6889 RegistrarX 6890 RegistrarX 6891 1999-04-03T22:00:00.0Z 6892 2015-04-03T22:00:00.0Z 6893 6895 6896 6897 ns1.example1.example 6898 Hns1_example_test-TEST 6899 6900 6901 192.0.2.2 6902 192.0.2.29 6903 2001:DB8:1::1 6904 RegistrarX 6905 RegistrarX 6906 1999-05-08T12:10:00.0Z 6907 RegistrarX 6908 2009-10-03T09:34:00.0Z 6909 6911 6912 6913 sh8013 6914 Csh8013-TEST 6915 6916 6917 6918 John Doe 6919 Example Inc. 6920 6921 123 Example Dr. 6922 Suite 100 6923 Dulles 6924 VA 6925 20166-6503 6926 US 6927 6928 6929 +1.7035555555 6930 6931 +1.7035555556 6932 6933 jdoe@example.example 6934 6935 RegistrarX 6936 RegistrarX 6937 6938 2009-09-13T08:01:00.0Z 6939 6940 RegistrarX 6941 6942 2009-11-26T09:10:00.0Z 6943 6944 2009-12-03T09:05:00.0Z 6945 6946 6947 6948 6949 6950 6952 6953 6954 RegistrarX 6955 Registrar X 6956 123 6957 ok 6958 6959 6960 123 Example Dr. 6961 6962 Suite 100 6963 6964 Dulles 6965 VA 6966 20166-6503 6967 US 6968 6969 6970 +1.7035555555 6971 6972 +1.7035555556 6973 6974 jdoe@example.example 6975 6976 http://www.example.example 6977 6978 6979 whois.example.example 6980 6981 http://whois.example.example 6982 6983 6984 2005-04-23T11:49:00.0Z 6985 6986 2009-02-17T17:51:00.0Z 6987 6988 6990 6991 6992 6993 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 6994 6995 6996 http://registro.br/dominio/regras.html 6997 6998 7000 7001 7002 xn--exampl-gva.example 7003 pt-BR 7004 example1.example 7005 withheld 7006 2005-04-23T11:49:00.0Z 7007 7009 7010 7011 1.0 7012 en 7013 7014 urn:ietf:params:xml:ns:domain-1.0 7015 7016 7017 urn:ietf:params:xml:ns:contact-1.0 7018 7019 7020 urn:ietf:params:xml:ns:host-1.0 7021 7022 7023 urn:ietf:params:xml:ns:rgp-1.0 7024 7025 urn:ietf:params:xml:ns:secDNS-1.1 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 7042 7043 7044 7045 7048 7049 7051 18. Example of Differential Deposit using the XML model 7053 Example of a Differential Deposit using the XML model: 7055 7056 7071 2019-10-17T00:00:00Z 7072 7073 1.0 7074 urn:ietf:params:xml:ns:rdeHeader-1.0 7075 7076 urn:ietf:params:xml:ns:rdeContact-1.0 7077 7078 urn:ietf:params:xml:ns:rdeHost-1.0 7079 7080 urn:ietf:params:xml:ns:rdeDomain-1.0 7081 7082 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7083 7084 urn:ietf:params:xml:ns:rdeIDN-1.0 7085 7086 urn:ietf:params:xml:ns:rdeNNDN-1.0 7087 7088 urn:ietf:params:xml:ns:rdeEppParams-1.0 7089 7090 7092 7093 7094 7095 example2.example 7096 7097 7099 7100 7101 7102 7103 test 7104 1 7106 7107 1 7109 7110 1 7112 7113 1 7115 7116 1 7118 7119 1 7121 7123 1 7125 7126 7127 7128 7130 19. Example of a Full Deposit using the CSV model 7132 Example of a Full Deposit using the CSV model: 7134 7135 7149 2019-10-18T00:00:00Z 7150 7151 1.0 7152 urn:ietf:params:xml:ns:csvDomain-1.0 7153 urn:ietf:params:xml:ns:csvHost-1.0 7154 urn:ietf:params:xml:ns:csvContact-1.0 7155 urn:ietf:params:xml:ns:csvRegistrar-1.0 7156 urn:ietf:params:xml:ns:csvIDN-1.0 7157 urn:ietf:params:xml:ns:csvNNDN-1.0 7158 urn:ietf:params:xml:ns:rdeEppParams-1.0 7159 7160 7161 7162 test 7163 7164 4 7165 7166 7167 6 7168 7169 7170 9 7171 7172 7173 3 7174 7175 7176 2 7177 7178 7179 2 7180 7181 7182 1 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7205 domain-YYYYMMDD.csv 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7218 domainContacts-YYYYMMDD.csv 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7234 domainStatuses-YYYYMMDD.csv 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7246 domainNameServers-name-YYYYMMDD.csv 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7258 domainNameServers-roid-YYYYMMDD.csv 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7274 dnssec-ds-YYYYMMDD.csv 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7290 dnssec-key-YYYYMMDD.csv 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7309 domainTransfer-YYYYMMDD.csv 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7331 host-YYYYMMDD.csv 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7345 hostStatuses-YYYYMMDD.csv 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7358 hostAddresses-YYYYMMDD.csv 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7384 contact-YYYYMMDD.csv 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7398 contactStatuses-YYYYMMDD.csv 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7419 contactPostal-YYYYMMDD.csv 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7437 contactTransfer-YYYYMMDD.csv 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7458 contactDisclose-YYYYMMDD.csv 7459 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7491 registrar-YYYYMMDD.csv 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7505 idnLanguage-YYYYMMDD.csv 7506 7507 7508 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7524 NNDN-YYYYMMDD.csv 7525 7526 7527 7528 7529 7530 1.0 7531 en 7532 urn:ietf:params:xml:ns:domain-1.0 7533 7534 urn:ietf:params:xml:ns:host-1.0 7535 7536 urn:ietf:params:xml:ns:contact-1.0 7537 7538 7539 urn:ietf:params:xml:ns:secDNS-1.1 7540 7541 urn:ietf:params:xml:ns:rgp-1.0 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7559 7560 7561 7562 7563 7564 7565 7566 7567 7569 20. Example of Differential Deposit using the CSV model 7571 Example of a Differential Deposit using the CSV model: 7573 7574 7588 2019-10-18T00:00:00Z 7589 7590 1.0 7591 urn:ietf:params:xml:ns:csvDomain-1.0 7592 urn:ietf:params:xml:ns:csvHost-1.0 7593 urn:ietf:params:xml:ns:csvContact-1.0 7594 urn:ietf:params:xml:ns:csvRegistrar-1.0 7595 urn:ietf:params:xml:ns:csvIDN-1.0 7596 7597 7598 7599 7600 7601 7602 7603 7604 7606 domain-delete-YYYYMMDD.csv 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7620 host-delete-YYYYMMDD.csv 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7633 contact-delete-YYYYMMDD.csv 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7646 registrar-delete-YYYYMMDD.csv 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7659 idnLanguage-delete-YYYYMMDD.csv 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7672 NNDN-delete-YYYYMMDD.csv 7673 7674 7675 7676 7677 7678 7679 7680 test 7681 7682 2 7683 7684 7685 2 7686 7687 7688 3 7689 7690 7691 1 7692 7693 7694 1 7695 7696 7697 1 7698 7699 7700 1 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7723 domain-YYYYMMDD.csv 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7736 domainContacts-YYYYMMDD.csv 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7751 domainStatuses-YYYYMMDD.csv 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7764 domainNameServers-name-YYYYMMDD.csv 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7776 domainNameServers-roid-YYYYMMDD.csv 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7792 dnssec-ds-YYYYMMDD.csv 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7808 dnssec-key-YYYYMMDD.csv 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7827 domainTransfer-YYYYMMDD.csv 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7849 host-YYYYMMDD.csv 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7863 hostStatuses-YYYYMMDD.csv 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7876 hostAddresses-YYYYMMDD.csv 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7902 contact-YYYYMMDD.csv 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7916 contactStatuses-YYYYMMDD.csv 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7937 contactPostal-YYYYMMDD.csv 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7955 contactTransfer-YYYYMMDD.csv 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7976 contactDisclose-YYYYMMDD.csv 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8008 registrar-YYYYMMDD.csv 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8022 idnLanguage-YYYYMMDD.csv 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8040 NNDN-YYYYMMDD.csv 8042 8043 8044 8045 8046 8047 1.0 8048 en 8049 urn:ietf:params:xml:ns:domain-1.0 8050 8051 urn:ietf:params:xml:ns:host-1.0 8052 8053 urn:ietf:params:xml:ns:contact-1.0 8054 8055 8056 urn:ietf:params:xml:ns:secDNS-1.1 8057 8058 urn:ietf:params:xml:ns:rgp-1.0 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8085 21. References 8086 21.1. Normative References 8088 [I-D.ietf-regext-data-escrow] 8089 Lozano, G., "Registry Data Escrow Specification", draft- 8090 ietf-regext-data-escrow-10 (work in progress), June 2020. 8092 [ISO-3166-1] 8093 3166, I. S., "Codes for the representation of names of 8094 countries and their subdivisions -- Part 1: Country 8095 codes", ISO Standard 3166, November 2006. 8097 [ITU-E164] 8098 International Telecommunication Union, "The international 8099 public telecommunication numbering plan", ITU-T 8100 Recommendation E.164, February 2005. 8102 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8103 DOI 10.17487/RFC0791, September 1981, 8104 . 8106 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8107 Requirement Levels", BCP 14, RFC 2119, 8108 DOI 10.17487/RFC2119, March 1997, 8109 . 8111 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8112 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8113 . 8115 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8116 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8117 DOI 10.17487/RFC3915, September 2004, 8118 . 8120 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8121 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8122 2006, . 8124 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8125 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8126 . 8128 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8129 Domain Name Mapping", STD 69, RFC 5731, 8130 DOI 10.17487/RFC5731, August 2009, 8131 . 8133 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8134 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8135 August 2009, . 8137 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8138 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8139 August 2009, . 8141 [RFC5891] Klensin, J., "Internationalized Domain Names in 8142 Applications (IDNA): Protocol", RFC 5891, 8143 DOI 10.17487/RFC5891, August 2010, 8144 . 8146 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8147 Security Extensions Mapping for the Extensible 8148 Provisioning Protocol (EPP)", RFC 5910, 8149 DOI 10.17487/RFC5910, May 2010, 8150 . 8152 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 8153 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 8154 May 2017, . 8156 [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS 8157 Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, 8158 January 2019, . 8160 [V42] International Telecommunication Union, "V.42 : Error- 8161 correcting procedures for DCEs using asynchronous-to- 8162 synchronous conversion", March 2002, 8163 . 8165 [W3C.REC-xml-20081126] 8166 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 8167 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 8168 Edition) REC-xml-20081126", November 2008, 8169 . 8171 [W3C.REC-xmlschema-1-20041028] 8172 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 8173 "XML Schema Part 1: Structures Second Edition REC- 8174 xmlschema-1-20041028", October 2004, 8175 . 8177 [W3C.REC-xmlschema-2-20041028] 8178 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 8179 Second Edition REC-xmlschema-2-20041028", October 2004, 8180 . 8182 21.2. Informative References 8184 [ICANN-GTLD-AGB-20120604] 8185 ICANN, "gTLD Applicant Guidebook Version 2012-06-04", June 8186 2012, . 8189 [ICANN-GTLD-RA-20170731] 8190 ICANN, "Base Registry Agreement 2017-07-31", July 2017, 8191 . 8194 [RFC1952] Deutsch, P., "GZIP file format specification version 4.3", 8195 RFC 1952, DOI 10.17487/RFC1952, May 1996, 8196 . 8198 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8199 DOI 10.17487/RFC3688, January 2004, 8200 . 8202 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8203 DOI 10.17487/RFC3912, September 2004, 8204 . 8206 [RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma- 8207 Separated Values (CSV) Files", RFC 4180, 8208 DOI 10.17487/RFC4180, October 2005, 8209 . 8211 [RFC6234] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms 8212 (SHA and SHA-based HMAC and HKDF)", RFC 6234, 8213 DOI 10.17487/RFC6234, May 2011, 8214 . 8216 [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, 8217 "Recommendations for Secure Use of Transport Layer 8218 Security (TLS) and Datagram Transport Layer Security 8219 (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 8220 2015, . 8222 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8223 Code: The Implementation Status Section", BCP 205, 8224 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8225 . 8227 [variantTLDsReport] 8228 Internet Corporation for Assigned Names and Numbers 8229 (ICANN), "A Study of Issues Related to the Management of 8230 IDN Variant TLDs", February 2012, 8231 . 8234 Authors' Addresses 8236 Gustavo Lozano 8237 Internet Corporation for Assigned Names and Numbers 8238 12025 Waterfront Drive, Suite 300 8239 Los Angeles 90292 8240 United States of America 8242 Phone: +1.310.823.9358 8243 Email: gustavo.lozano@icann.org 8245 James Gould 8246 VeriSign, Inc. 8247 12061 Bluemont Way 8248 Reston 20190 8249 United States of America 8251 Email: jgould@verisign.com 8253 Chethan Thippeswamy 8254 VeriSign, Inc. 8255 12061 Bluemont Way 8256 Reston 20190 8257 United States of America 8259 Email: cthippeswamy@verisign.com