idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-06.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 (Feb 20, 2020) is 1526 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-10) exists of draft-ietf-regext-data-escrow-04 -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 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: August 23, 2020 C. Thippeswamy 6 VeriSign 7 Feb 20, 2020 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-06 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 August 23, 2020. 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 . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6 58 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 59 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6 60 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 61 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 7 62 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 7 63 4.6. Conventions applicable to the CSV Model . . . . . . . . . 7 64 5. Object Description . . . . . . . . . . . . . . . . . . . . . 15 65 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 15 66 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 34 67 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 44 68 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 62 69 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 70 70 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 74 71 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 79 72 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 81 73 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 81 74 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 84 75 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 76 8. Data escrow agent extended verification process . . . . . . . 85 77 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 86 78 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 86 79 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 95 80 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98 81 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 102 82 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 103 83 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 106 84 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 108 85 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 114 86 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 117 87 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 120 88 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 121 89 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 123 90 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 124 91 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 125 92 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 128 93 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 128 94 10. Internationalization Considerations . . . . . . . . . . . . . 130 95 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 130 96 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 135 97 12.1. Implementation in the gTLD space . . . . . . . . . . . . 135 99 13. Security Considerations . . . . . . . . . . . . . . . . . . . 136 100 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 136 101 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 136 102 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 137 103 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 104 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 137 105 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 137 106 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 138 107 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 138 108 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 138 109 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 139 110 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 140 111 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 140 112 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 141 113 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 141 114 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 141 115 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 141 116 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 141 117 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 141 118 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 143 119 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 143 120 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 144 121 16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 144 122 17. Example of a Full Deposit using the XML model . . . . . . . . 144 123 18. Example of Differential Deposit using the XML model . . . . . 150 124 19. Example of a Full Deposit using the CSV model . . . . . . . . 151 125 20. Example of Differential Deposit using the CSV model . . . . . 160 126 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 171 127 21.1. Normative References . . . . . . . . . . . . . . . . . . 171 128 21.2. Informative References . . . . . . . . . . . . . . . . . 173 129 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 173 131 1. Introduction 133 Registry Data Escrow is the process by which a registry periodically 134 submits data deposits to a third-party called an escrow agent. These 135 deposits comprise the minimum data needed by a third-party to resume 136 operations if the registry cannot function and is unable or unwilling 137 to facilitate an orderly transfer of service. For example, for a 138 domain name registry or registrar, the data to be deposited would 139 include all the objects related to registered domain names, e.g., 140 names, contacts, name servers, etc. 142 The goal of data escrow is higher resiliency of registration 143 services, for the benefit of Internet users. The beneficiaries of a 144 registry are not just those registering information there, but all 145 relying parties that need to identify the owners of objects. 147 In the context of domain name registries, registration data escrow is 148 a requirement for generic top-level domains and some country code 149 top-level domain managers are also currently escrowing data. There 150 is also a similar requirement for ICANN-accredited domain registrars. 152 This document defines the standard set of objects for a Domain Name 153 Registry that uses the Registry Data Escrow Specification described 154 in [I-D.ietf-regext-data-escrow] for escrow. The set of objects 155 include: 157 o Domain: Internet domain names that are typically provisioned in a 158 Domain Name Registry using the EPP domain name mapping [RFC5731]. 159 The attributes defined in the EPP domain name mapping [RFC5731] 160 are fully supported by this document. 162 o Host: Internet host names that are typically provisioned in a 163 Domain Name Registry using the EPP host mapping [RFC5732]. The 164 attributes defined in the EPP host mapping [RFC5732] are fully 165 supported by this document. 167 o Contact: Individual or organization social information provisioned 168 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 169 The attributes defined in the EPP contact mapping [RFC5733] are 170 fully supported by this document. 172 o Registrar: The organization that sponsors objects like domains, 173 hosts, and contacts in a Domain Name Registry. 175 o NNDN (NNDN's not domain name): Domain Name Registries may maintain 176 domain names without their being persisted as domain objects in 177 the registry system, for example, a list of reserved names not 178 available for registration. The NNDN is a lightweight domain-like 179 object that is used to escrow domain names not maintained as 180 domain name objects. 182 This document defines the following pseudo-objects: 184 o IDN Table Reference: Internationalized Domain Names (IDN) included 185 in the Domain Object Data Escrow include references to the IDN 186 Table and Policy used in IDN registration. 188 o EPP parameters: Definition of the specific EPP parameters 189 supported by the Registry Operator. 191 o Header: Used to specify counters of objects in the database at a 192 certain point in time (watermark). 194 o Policy: Used to specify OPTIONAL elements from this specification 195 that are REQUIRED based on the business model of the registry. 197 2. Models 199 This document defines two different models that can be used to 200 deposit data escrow objects: XML and CSV. 202 The data escrow deposit MAY contain a mix of both models but an 203 object MUST be escrowed only in one model. 205 This document does not suggest the use of a particular model, and 206 both are equivalent. A Domain Name Registry may choose the model 207 that is more appropriate for the peculiarities of its systems. For 208 example, a registry may use the CSV-export functionality of the RDBMS 209 for escrow; therefore, the CSV model may be more appropriate. 210 Another registry may use the code developed for EPP to implement 211 escrow. 213 2.1. XML Model 215 XML: The XML model includes all the deposit information (meta-data 216 and data) in an XML document. The definition of the XML format is 217 fully defined in the XML schemas. As a convention, the objects 218 represented using the XML model are referenced using RDE and an XML 219 namespace that is prefixed with "rde". For example, the Domain Name 220 object represented using the XML model can be referred to as the RDE 221 Domain Name with the XML namespace including rdeDomain 222 (urn:ietf:params:xml:ns:rdeDomain-1.0). 224 2.2. CSV Model 226 CSV: The CSV model uses XML to define the data escrow format of the 227 data contained in referenced Comma-Separated Values (CSV) files. As 228 a convention, the objects represented using the CSV model is 229 referenced using CSV and an XML namespace that is prefixed with 230 "csv". For example, the Domain Name object represented using the CSV 231 model can be referred to as the CSV Domain Name with the XML 232 namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). 234 3. Terminology 236 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 237 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 238 "OPTIONAL" in this document are to be interpreted as described in BCP 239 14 [RFC2119] [RFC8174] when, and only when, they appear in all 240 capitals, as shown here. 242 REGISTRY. In the context of this draft the definition will be 243 overloaded (from the definition in the base protocol) to indicate an 244 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 245 NAME. 247 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 248 or any other domain name at any level in the DNS tree for which a 249 Registry (either directly or through an affiliate company) provides 250 Registry Services for other organizations or individuals. For 251 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 253 REGISTRY SERVICES. Services offered by the Registry critical to the 254 following tasks: the provisioning of domain names on receipt of 255 requests and data from registrars; responding to registrar queries 256 for status information relating to the DNS servers for the RCDN; 257 dissemination of RCDN zone files; operation of the Registry DNS 258 servers; responding to queries for contact and other information 259 concerning DNS registrations in the RCDN; and any other products or 260 services that only a Registry is capable of providing, by reason of 261 its designation as the Registry. Typical examples of Registry 262 Services are DNS resolution for the RCDN, WHOIS and EPP. 264 ALLOCATED. A status of some label with respect to a zone, whereby 265 the label is associated administratively to some entity that has 266 requested the label. This term (and its cognates "allocation" and 267 "to allocate") may represent the first step on the way to delegation 268 in the DNS. 270 4. General Conventions 272 4.1. Date and Time 274 Numerous fields indicate "dates", such as the creation and expiry 275 dates for domain names. These fields SHALL contain timestamps 276 indicating the date and time in UTC as specified in [RFC3339], with 277 no offset from the zero meridian. 279 4.2. Country names 281 Country identifiers SHALL be represented using two character 282 identifiers as specified in [ISO-3166-1]. 284 4.3. Telephone numbers 286 Telephone numbers (both voice and facsimile) SHALL be formatted based 287 on structures defined in [ITU-E164]. Telephone numbers described in 288 this specification are character strings that MUST begin with a plus 289 sign ("+", ASCII value 0x002B), followed by a country code defined in 291 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 292 a sequence of digits representing the telephone number. 294 4.4. Checksum 296 The checksum of the CSV data escrow files MUST use CRC32, which is 297 the algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 298 of ITU-T recommendation V.42. 300 4.5. IP addresses 302 The syntax of IP addresses MUST conform to the text representation of 303 either Internet Protocol Version 4 [RFC0791] or Internet Protocol 304 Version 6 [RFC4291]. 306 4.6. Conventions applicable to the CSV Model 308 4.6.1. CSV Parent Child Relationship 310 The CSV model represents a relational model, where the CSV files 311 represent relational tables, the fields of the CSV files represent 312 columns of the tables, and each line of the CSV file represents a 313 record. As in a relational model, the CSV files can have 314 relationships utilizing primary keys in the parent CSV file 315 definitions and foreign keys in the child CSV file definitions for a 316 1-to-many relationship. The primary keys are not explicitly defined, 317 but the foreign keys are using the boolean "parent" field attribute 318 in the child CSV file. The relationships between the CSV files are 319 used to support a cascade replace or cascade delete of records 320 starting from the parent record in Differential and Incremental 321 Deposits (see [I-D.ietf-regext-data-escrow]). 323 The following is an example of the CSV file definitions for a Sample 324 object consisting of a parent "sample" CSV File Definition and a 325 child "sampleStatuses" CSV File Definition. The primary key for the 326 Sample object is the field that is used as the 327 foreign key in the "sampleStatuses" CSV File Definition by specifying 328 the "parent=true" attribute. If a Sample record is updated or 329 deleted in a Differential or Incremental Deposit, it should cascade 330 replace the data using the records included in the child 331 "sampleStatuses" CSV File Definition or cascade delete the existing 332 records in the child "sampleStatuses" CSV File Definition, 333 respectively. 335 336 ... 337 338 339 340 341 342 343 344 345 346 347 348 349 350 352 sample-YYYYMMDD.csv 353 354 355 356 357 358 359 360 361 362 363 364 366 sampleStatuses-YYYYMMDD.csv 367 368 369 370 ... 371 373 4.6.2. CSV elements 375 4.6.2.1. element 377 To support the CSV model, an element is defined for each object that 378 substitutes for the element and for the 379 element, that contains one or more elements. For 380 example, the Domain Name Object (Section 5.1) defines the 381 element, that substitutes for the 382 element, and the element, that substitutes for 383 the element. Both the element and 384 the elements contain one or more 385 elements. The element has the following child elements: 387 Ordered list of CSV fields used in the CSV files. 388 There are one or more child elements that substitute for the 389 abstract element. Each element defines the format 390 of the CSV field contained in the CSV files. The 391 elements support the "type" attribute that defines the XML simple 392 data type of the field element. The elements 393 support the "isRequired" attribute, with a default value of 394 "false", when set to "true" indicates that the field must be non- 395 empty in the CSV files and when set to "false" indicates that the 396 field MAY be empty in the CSV files. The "isRequired" attribute 397 MAY be specifically set for the field elements within the XML 398 schema and MAY be overridden when specifying the fields under the 399 element. The element supports an 400 OPTIONAL "parent" attribute that identifies the field as a 401 reference to a parent object, as defined in CSV Parent Child 402 Relationship (Section 4.6.1). For example, the field SHOULD set the 404 "parent" attribute to "true" to identify it as the parent domain 405 name of the domain status. 407 A list of one or more CSV files using the 408 child element. The child element 409 defines a reference to the CSV file name and has the following 410 optional attributes: 412 compression If the CSV file is compressed, the "compression" 413 attribute defines the compression format like "gzip" or "zip". 415 encoding Defines the encoding of the CSV file with the default 416 encoding of "UTF-8". 418 cksum Defines the checksum of the CSV file using CRC32, as 419 defined in Section 4.4. This attribute is used to validate 420 that the full CSV file exists and has not been tampered with. 422 The element requires a "name" attribute that defines the 423 purpose of the CSV file with values like "domain", "host", "contact". 424 The supported "name" attribute values are defined for each object 425 type. The OPTIONAL "sep" attribute defines the CSV separator 426 character with the default separator character of ",". 428 The following is an example of the 429 element for domain name records where the is set 430 as required with isRequired="true". 432 433 ... 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 453 domain-YYYYMMDD.csv 454 455 456 457 ... 458 460 The following is example of the "domain-YYYYMMDD.csv" file with one 461 record matching the definition. 463 domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 464 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 465 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 466 The following is an example of the 467 element for domain name records. 469 470 ... 471 472 473 474 475 476 478 domain-delete-YYYYMMDD.csv 479 480 481 482 ... 483 485 The following is example of the "domain-delete-YYYYMMDD.csv" file 486 with three records that matches the single field. 488 domain1.example 489 domain2.example 490 domainN.example 492 4.6.2.2. CSV common field elements 494 The element defined in the element 495 (Section 4.6.2.1) section has child elements that substitute for the 496 abstract element. By convention 497 elements include an 'f' prefix to identify them as field definition 498 elements. There are a set of common field elements that are used 499 across multiple data escrow objects. The common field elements are 500 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 501 using the "rdeCsv" sample namespace prefix. The CSV common field 502 elements include: 504 UTF-8 encoded name field with 505 type="eppcom:labelType". 507 Repository Object IDentifier (ROID) field with 508 type="eppcom:roidType" and isRequired="true". 510 Registrant contact identifier with 511 type="eppcom:clIDType". 513 The object status description, which is 514 free form text describing the rationale for the status, with 515 type="normalizedString". 517 Identifier of the client (registrar) that sponsors 518 the object with type="eppcom:clIDType" and isRequired="true". 520 Identifier of the registrar, defined in Section 5.4, 521 of the client that created the object with type="eppcom:clIDType". 523 Identifier of the client that created the object with 524 type="eppcom:clIDType". 526 Identifier of the registrar, defined in Section 5.4, 527 of the client that updated the object with type="eppcom:clIDType". 529 Identifier of the client that updated the object with 530 type="eppcom:clIDType". 532 Identifier of the registrar, defined in Section 5.4, 533 of the client that requested the transfer with 534 type="eppcom:clIDType" and isRequired="true". 536 Identifier of the client that requested the transfer 537 with type="eppcom:clIDType". 539 Identifier of the registrar, defined in Section 5.4, 540 of the client that should take or took action with 541 type="eppcom:clIDType" and isRequired="true". 543 Identifier of the client that should take or took 544 action for transfer with type="eppcom:clIDType". 546 Created date of object with type="dateTime". 548 Updated date of object with type="dateTime". 550 Expiration date of object with type="dateTime". 552 Date that transfer was requested with 553 type="dateTime" and isRequired="true". 555 Date that transfer action should be taken or has 556 been taken with type="dateTime" and isRequired="true". 558 Date of last transfer with type="dateTime". 560 State of the most recent transfer request with 561 type="eppcom:trStatusType" and isRequired="true". 563 General token field with type="token". 565 General language field with type="language". 567 IDN Table Identifier used for IDN domain names 568 with type="token". 570 General positive integer field with 571 type="positiveInteger". 573 Contains the URL of an object like a registrar object 574 with type="anyURI". 576 Custom field with name attribute that defines the 577 custom field name" with type="token". 579 4.6.3. Internationalized and Localized Elements 581 Some elements MAY be provided in either internationalized form 582 ("int") or localized form ("loc"). Those elements use a field value 583 or "isLoc" attribute to specify the form used. If an "isLoc" 584 attribute is used, a value of "true" indicates the use of the 585 localized form and a value of "false" indicates the use of the 586 internationalized form. This MAY override the form specified for a 587 parent element. A value of "int" is used to indicate the 588 internationalized form and a value of "loc" is used to indicate the 589 localized form. When the internalized form ("int") is provided, the 590 field value MUST be represented in a subset of UTF-8 that can be 591 represented in the 7-bit US-ASCII character set. When the localized 592 form ("loc") is provided, the field value MAY be represented in 593 unrestricted UTF-8. 595 The field elements below of the "registrar" 596 element specify the internationalized form with the 597 isLoc="false" attribute. 599 ... 600 601 ... 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 633 registrar-YYYYMMDD.csv 634 635 636 637 ... 638 639 ... 641 The following is an example of using the 642 field value to define the internationalized or localized form of the 643 remainder of the "contactPostal" field values. 645 ... 646 647 ... 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 665 contactPostal-YYYYMMDD.csv 666 667 668 669 ... 670 671 ... 673 5. Object Description 675 This section describes the base objects supported by this 676 specification: 678 5.1. Domain Name Object 680 The domain name object is based on the EPP domain name mapping 681 specified in [RFC5731]. The domain name object supports both the XML 682 Model and the CSV Model, defined in the Models (Section 2) section. 683 The elements used for both models are defined in the following 684 sections. 686 5.1.1. XML Model 688 There are two elements used in the data escrow of the domain name 689 objects for the XML model including the , under the 690 element, and the element, under the 691 element. 693 5.1.1.1. object 695 The domain element is based on the EPP domain response for an 696 authorized client (see Section 3.1.2. of [RFC5731]) with additional 697 data from an EPP Query Response, see Section 3.1.3. of 698 [RFC5731], RGP status from [RFC3915], and data from the EPP 699 command, see Section 5.2.1. of [RFC5910]. 701 A element substitutes for the abstract 702 element to define a concrete definition of a domain. The 703 element can be replaced by other domain definitions 704 using the XML schema substitution groups feature. 706 The element contains the following child elements: 708 o A element that contains the fully qualified name of the 709 domain name object. For IDNs the A-Label is used (see [RFC5891], 710 Section 4.4). 712 o A element that contains the repository object identifier 713 assigned to the domain name object when it was created. 715 o An OPTIONAL element that contains the fully qualified 716 domain name in Unicode character set. It MUST be provided if 717 available. 719 o An OPTIONAL element that references the IDN 720 Table used for the IDN. This corresponds to the "id" attribute of 721 the element. This element MUST be present if the 722 domain name is an IDN. 724 o An OPTIONAL element is used to indicate that the 725 domain name is an IDN variant. This element contains the domain 726 name used to generate the IDN variant. 728 o One or more elements that contain the current status 729 descriptors associated with the domain name. 731 o Zero or more OPTIONAL elements to represent 732 "pendingDelete" sub-statuses, including "redemptionPeriod", 733 "pendingRestore", and "pendingDelete", that a domain name can be 734 in as a result of grace period processing as specified in 735 [RFC3915]. 737 o An OPTIONAL element that contains the identifier for 738 the human or organizational social information object associated 739 as the holder of the domain name object. 741 o Zero or more OPTIONAL elements that contain identifiers 742 for the human or organizational social information objects 743 associated with the domain name object. 745 o An OPTIONAL element that contains the fully qualified names 746 of the delegated host objects or host attributes (name servers) 747 associated with the domain name object. See Section 1.1 of 748 [RFC5731] for a description of the elements used to specify host 749 objects or host attributes. 751 o A element that contains the identifier of the sponsoring 752 registrar. 754 o An OPTIONAL element that contains the identifier of the 755 registrar that created the domain name object. An OPTIONAL client 756 attribute is used to specify the client that performed the 757 operation. 759 o An OPTIONAL element that contains the date and time of 760 the domain name object creation. This element MUST be present if 761 the domain name has been allocated. 763 o An OPTIONAL element that contains the date and time 764 identifying the end (expiration) of the domain name object's 765 registration period. This element MUST be present if the domain 766 name has been allocated. 768 o An OPTIONAL element that contains the identifier of the 769 registrar that last updated the domain name object. This element 770 MUST NOT be present if the domain has never been modified. An 771 OPTIONAL client attribute is used to specify the client that 772 performed the operation. 774 o An OPTIONAL element that contains the date and time of 775 the most recent domain-name-object modification. This element 776 MUST NOT be present if the domain name object has never been 777 modified. 779 o An OPTIONAL element that contains the public key 780 information associated with Domain Name System security (DNSSEC) 781 extensions for the domain name as specified in [RFC5910]. 783 o An OPTIONAL element that contains the date and time of 784 the most recent domain object successful transfer. This element 785 MUST NOT be present if the domain name object has never been 786 transferred. 788 o An OPTIONAL element that contains the following child 789 elements related to the last transfer request of the domain name 790 object. This element MUST NOT be present if a transfer request 791 for the domain name has never been created. 793 * A element that contains the state of the most recent 794 transfer request. 796 * A element that contains the identifier of the registrar 797 that requested the domain name object transfer. An OPTIONAL 798 client attribute is used to specify the client that performed 799 the operation. 801 * A element that contains the date and time that the 802 transfer was requested. 804 * An element that contains the identifier of the registrar 805 that should act upon a PENDING transfer request. For all other 806 status types, the value identifies the registrar that took the 807 indicated action. An OPTIONAL client attribute is used to 808 specify the client that performed the operation. 810 * An element that contains the date and time of a 811 required or completed response. For a PENDING request, the 812 value identifies the date and time by which a response is 813 required before an automated response action will be taken by 814 the registry. For all other status types, the value identifies 815 the date and time when the request was completed. 817 * An OPTIONAL element that contains the end of the 818 domain name object's validity period (expiry date) if the 819 transfer caused or causes a change in the validity period. 821 Example of a domain object: 823 ... 824 825 xn--exampl-gva.example 826 Dexample1-TEST 827 pt-BR 828 example.example 829 830 jd1234 831 sh8013 832 sh8013 833 834 ns1.example.com 835 ns1.example1.example 836 837 RegistrarX 838 RegistrarX 839 1999-04-03T22:00:00.0Z 840 2015-04-03T22:00:00.0Z 841 842 ... 844 5.1.1.2. object 846 The element contains the fully qualified domain 847 name that was deleted and purged. 849 Example of object: 851 ... 852 853 ... 854 855 foo.example 856 bar.example 857 858 ... 859 860 ... 862 5.1.2. CSV Model 864 For the CSV Model of the domain name object, the 865 child element of the element is used to hold the new 866 or updated domain name objects for the deposit. The 867 child element of the element is 868 used to hold the deleted or purged domain name objects for the 869 deposit. Both the and 870 elements contain one or more elements with a set of 871 named CSV file definitions using the "name" attribute. 873 Differential and Incremental Deposits are based on changes to the 874 domain name objects. The updated domain name object data under the 875 element is a cascade replace down all of the 876 domain name CSV files starting with the parent "domain" CSV File 877 Definition (Section 5.1.2.1.1). The child CSV file definitions 878 include a field. All the child CSV 879 file definition data for the domain name objects in the parent 880 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 881 deleted and then set using the data in the child CSV files. The 882 deleted domain name object data under the element 883 is a cascade delete starting from the "domain" Deletes CSV File 884 Definition (Section 5.1.2.2.1). 886 5.1.2.1. 888 The is used to hold the new or updated domain 889 name object information for the deposit. The is 890 split into separate CSV file definitions using named 891 elements with the "name" attribute. The following sections include 892 the supported domain name CSV file definitions: 894 5.1.2.1.1. "domain" CSV File Definition 896 The "domain" CSV File Definition defines the fields and CSV file 897 references used for the parent domain name object records. All the 898 other domain name CSV file definitions are child CSV files based on 899 the inclusion of the field. 901 The following "csvDomain" field elements MUST be used in the "domain" 902 element: 904 Domain name field with type="eppcom:labelType" and 905 isRequired="true". 907 The following "csvDomain" field elements MAY be used in the "domain" 908 element: 910 Fully qualified name of the original IDN 911 domain name object related to the variant domain name object with 912 type="eppcom:labelType". 914 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 915 "domain" element: 917 Registry Object IDentifier (ROID) for the domain name 918 object with isRequired="true". 920 or A choice of: 922 Identifier of the sponsoring client with 923 isRequired="true". 925 Contains the ID assigned by ICANN with 926 type="positiveInteger". The attribute "isRequired" MUST equal 927 "true". 929 The following "rdeCsv" fields, defined in section CSV common field 930 elements (Section 4.6.2.2), MAY be used in the "domain" 931 element: 933 Identifier of the registrar, defined in Section 5.4, 934 of the client that created the object. 936 Identifier of the client that created the domain name 937 object. 939 Identifier of the registrar, defined in Section 5.4, 940 of the client that updated the object. 942 Identifier of the client that last updated the domain 943 name object. 945 UTF8 encoded domain name for the 946 field element. 948 IDN Table Identifier used for the IDN domain 949 name object that MUST match a field element 950 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 952 Registrant contact identifier for the domain 953 name object. 955 Created date and time of the domain name object. 957 Date and time of the last update to the domain name 958 object. 960 Expiration date and time for the domain name 961 object. 963 Date and time of the last transfer for the domain 964 name object. 966 Example of a "domain" element. 968 ... 969 970 ... 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 990 domain-YYYYMMDD.csv 991 992 993 994 ... 995 996 ... 998 Example of the corresponding domain-YYYYMMDD.csv file. The file 999 contains four records (two active ASCII domains, original IDN with 1000 LANG-1 language rules, and variant IDN with LANG-1 language rules). 1002 domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 1003 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1004 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1005 domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 1006 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 1007 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1008 xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 1009 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1010 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1011 xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example, 1012 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 1013 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1015 5.1.2.1.2. "domainContacts" CSV File Definition 1017 The "domainContacts" CSV File Definition defines the fields and CSV 1018 file references used for the domain name object link records to 1019 contact objects, as described in Contact Object (Section 5.3). 1021 The following "csvDomain" field elements, defined for the "domain" 1022 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 1023 "domainContacts" element: 1025 The name of the domain object that is linked to 1026 the contact object with isRequired="true". 1028 The contact type for the contact object 1029 link with type="domain:contactAttrType" and isRequired="true". 1030 The supported contact type values include "admin" for the 1031 administration contact, "billing" for the billing contact, and 1032 "tech" for the technical contact. 1034 The following "csvContact" fields, defined for the "contact" CSV File 1035 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 1036 element: 1038 The server-unique contact identifier with 1039 isRequired="true". 1041 Example of a "domainContacts" 1042 element. 1044 ... 1045 1046 ... 1047 1048 1049 1050 1051 1052 1053 1054 1056 domainContacts-YYYYMMDD.csv 1057 1058 1059 1060 ... 1061 1062 ... 1064 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1065 file contains an admin, tech, and billing contact for the four domain 1066 names domain1.example, domain2.example, xn--bc123-3ve.example and 1067 xn--bc321-3ve.example. 1069 domain1.example,domain1admin,admin 1070 domain1.example,domain1tech,tech 1071 domain1.example,domain1billing,billing 1072 domain2.example,domain2admin,admin 1073 domain2.example,domain2tech,tech 1074 domain2.example,domain2billing,billing 1075 xn--bc123-3ve.example,xnabc123admin,admin 1076 xn--bc123-3ve.example,xnabc123tech,tech 1077 xn--bc123-3ve.example,xnabc123billing,billing 1078 xn--bc321-3ve.example,xnabc123admin,admin 1079 xn--bc321-3ve.example,xnabc123tech,tech 1080 xn--bc321-3ve.example,xnabc123billing,billing 1082 5.1.2.1.3. "domainStatuses" CSV File Definition 1084 The "domainStatuses" CSV File Definition defines the fields and CSV 1085 file references used for the domain name object statuses. 1087 The following "csvDomain" fields, defined for the "domain" CSV File 1088 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1089 element: 1091 Domain name of status with isRequired="true". 1093 The status of the domain name with 1094 type="domain:statusValueType" and isRequired="true". 1096 The Registry Grace Period (RGP) status, as a 1097 sub-status of the "pendingDelete" status 1098 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1100 The following "rdeCsv" fields, defined in section CSV common field 1101 elements (Section 4.6.2.2), MAY be used in the "domainStatuses" 1102 element: 1104 Domain object status description which 1105 is free form text describing the rationale for the status. 1107 Language of the field. 1109 Example of a "domainStatuses" 1110 element. 1112 ... 1113 1114 ... 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1126 domainStatuses-YYYYMMDD.csv 1127 1128 1129 1130 ... 1131 1132 ... 1134 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1135 file contains the statuses for the four domain names domain1.example, 1136 domain2.example, xn--bc123-3ve.example and xn--bc321-3ve.example. 1138 domain1.example,clientUpdateProhibited,"Disallow update", 1139 en, 1140 domain1.example,clientDeleteProhibited,"Disallow delete", 1141 en, 1142 domain2.example,ok,,, 1143 xn--bc123-3ve.example,ok,,, 1144 xn--bc321-3ve.example,ok,,, 1146 5.1.2.1.4. "domainNameServers" CSV File Definition 1148 The "domainNameServers" CSV File Definition defines the fields and 1149 CSV file references used for the domain name delegated hosts (name 1150 servers). The "domainNameServers" CSV files define the relationship 1151 between a domain name object and a delegated host. The 1152 "domainNameServers" CSV File is used to support the 1153 model, defined in [RFC5731]. 1155 The following "csvDomain" fields, defined for the "domain" CSV File 1156 Definition (Section 5.1.2.1.1), MUST be used in the 1157 "domainNameServers" element: 1159 Domain name using the delegated host with 1160 isRequired="true". 1162 The following "csvHost" and "rdeCsv" field elements MUST be used in 1163 the "domainNameServers" element: 1165 or A choice of: 1167 Host name field with type="eppcom:labelType" and 1168 isRequired="true". 1170 Host object Registry Object IDentifier (ROID) 1171 assigned to the host object with isRequired="true". 1173 Example of a "domainNameServers" 1174 element. 1176 ... 1177 1178 ... 1179 1180 1181 1182 1183 1184 1185 1187 domainNameServers-YYYYMMDD.csv 1188 1189 1190 1191 ... 1192 1193 ... 1195 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1196 The file contains the delegated hosts (name servers) for the four 1197 domain names domain1.example, domain2.example, xn--bc123-3ve.example 1198 and xn--bc321-3ve.example referenced via the field 1199 element. 1201 domain1.example,Hns1_domain1_test-TEST 1202 domain1.example,Hns2_domain1_test-TEST 1203 domain2.example,Hns1_domain2_test-TEST 1204 domain2.example,Hns2_domain2_test-TEST 1205 xn--bc123-3ve.example,Hns1_example_test-TEST 1206 xn--bc123-3ve.example,Hns2_example_test-TEST 1207 xn--bc321-3ve.example,Hns1_example_test-TEST 1208 xn--bc321-3ve.example,Hns2_example_test-TEST 1210 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1212 The "domainNameServersAddresses" CSV File Definition defines the 1213 fields and CSV file references used for supporting the host as domain 1214 attributes model. 1216 The following "csvDomain" fields, defined for the "domain" CSV File 1217 Definition (Section 5.1.2.1.1), MUST be used in the 1218 "domainNameServersAddresses" element: 1220 Domain name using the delegated host with host 1221 and isRequired="true". 1223 The following "rdeCsv" fields, defined in section Host CSV model 1224 elements (Section 5.2.2), MUST be used in the 1225 "domainNameServersAddresses" element: 1227 Host name field with type="eppcom:labelType" and 1228 isRequired="true". 1230 The following "csvHost" fields, defined in section Host CSV model 1231 elements (Section 5.2.2), MAY be used in the 1232 "domainNameServersAddresses" element: 1234 IP addresses associated with the host object with 1235 type="host:addrStringType". 1237 IP addresses version associated with the host 1238 object with type="host:ipType". "host:ipType" has the enumerated 1239 values of "v4" or "v6". 1241 Example of a "domainNameServersAddresses" 1242 element. 1244 ... 1245 1246 ... 1247 1248 1249 1250 1251 1252 1253 1254 1255 1257 domainNameServersAddresses-YYYYMMDD.csv 1258 1259 1260 1261 ... 1262 1263 ... 1265 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1266 file. The file contains the delegated hosts (name servers) for the 1267 four domain names domain1.example, domain2.example, xn-- 1268 bc123-3ve.example and xn--bc321-3ve.example. 1270 domain1.example,ns1.domain1.example,192.0.2.1,v4 1271 domain1.example,ns2.domain1.example,2001:DB8::1,v6 1272 domain2.example,ns1.example.net,, 1273 domain2.example,ns2.example.net,, 1274 xn--bc123-3ve.example,ns1.example.net,, 1275 xn--bc123-3ve.example,ns2.example.net,, 1276 xn--bc321-3ve.example,ns1.example.net,, 1277 xn--bc321-3ve.example,ns2.example.net,, 1279 5.1.2.1.6. "dnssec" CSV File Definition 1281 The "dnssec" CSV File Definition defines the fields and CSV file 1282 references used for the domain name object DNSSEC records (DS or Key 1283 Data). 1285 The following "csvDomain" field elements MUST be used in the "dnssec" 1286 element when the DS Data Interface per 1287 [RFC5910] is used: 1289 Contains the DS key tag value per [RFC5910] with 1290 type="unsignedShort" and isRequired="true". 1292 Contains the DS algorithm value per [RFC5910] 1293 with type="unsignedByte" and isRequired="true". 1295 Contains the DS digest type value per 1296 [RFC5910] with type="unsignedByte" and isRequired="true". 1298 Contains the DS digest value per [RFC5910] with 1299 type="hexBinary" and isRequired="true". 1301 The following "csvDomain" field elements MUST be used in the "dnssec" 1302 element when the Key Data Interface per 1303 [RFC5910] is used and MAY be used in the "dnssec" 1304 element when the DS Data Interface per [RFC5910] is 1305 used: 1307 Contains the flags field value per [RFC5910] with 1308 type="unsignedShort" and isRequired="true". 1310 Contains the Key protocol value per [RFC5910] 1311 with type="unsignedByte" and isRequired="true". 1313 Contains the Key algorithm value per [RFC5910] 1314 with type="unsignedByte" and isRequired="true". 1316 Contains the public key value per [RFC5910] with 1317 type="secDNS:keyType" and isRequired="true". 1319 The following "csvDomain" field elements MAY be used in the "dnssec" 1320 element: 1322 Indicates a child's preference for the 1323 number of seconds after signature generation when the parent's 1324 signature on the DS information provided by the child will expire 1325 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1327 The following "domain" fields, defined for the "domain" CSV File 1328 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1329 element: 1331 Domain name of the domain object associated with 1332 the DNSSEC record and isRequired="true". 1334 Example of a "dnssec" element with 1335 the DS Data Interface of [RFC5910]: 1337 1338 ... 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1351 dnssec-ds-YYYYMMDD.csv 1352 1353 1354 1355 ... 1356 1357 ... 1359 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1360 contains two DS records for domain1.example. 1362 domain1.example,604800,12345,3,1,49FD46E6C4B45C55D4AC 1363 domain1.example,604800,12346,3,1,38EC35D5B3A34B44C39B 1364 Example of a "dnssec" element with 1365 the Key Data Interface of [RFC5910]: 1367 1368 ... 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1381 dnssec-key-YYYYMMDD.csv 1382 1383 1384 1385 ... 1386 1387 ... 1389 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1390 contains two key records for domain1.example. 1392 domain1.example,604800,257,3,1,AQPJ////4Q== 1393 domain1.example,604800,257,3,1,AQPJ////4QQQ 1395 5.1.2.1.7. "domainTransfer" CSV File Definition 1397 The "domainTransfer" CSV File Definition defines the fields and CSV 1398 file references used for the domain name object pending and completed 1399 transfer records. No additional field elements were added for use in 1400 the "domainTransfer" element. 1402 The following "rdeCsv" fields, defined in section CSV common field 1403 elements (Section 4.6.2.2), MUST be used in the "domainTransfer" 1404 element: 1406 State of the most recent transfer request with 1407 isRequired="true". 1409 Identifier of the registrar, defined in Section 5.4, 1410 of the client that requested the transfer with isRequired="true". 1412 Date and time that the transfer was requested with 1413 isRequired="true". 1415 Identifier of the registrar, defined in Section 5.4, 1416 of the client that should take or took action with 1417 isRequired="true". 1419 Date and time that the transfer action should be 1420 taken or has been taken with isRequired="true". 1422 The following "rdeCsv" fields, defined in section CSV common field 1423 elements (Section 4.6.2.2), MAY be used in the "domainTransfer" 1424 element: 1426 Expiration date if the transfer command caused or 1427 causes a change in the validity period. 1429 Identifier of the client that requested the transfer. 1431 Identifier of the client that should take or took 1432 action for transfer. 1434 The following "csvDomain" fields, defined for the "domain" CSV File 1435 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1436 element: 1438 Domain name of the domain object involved in the 1439 transfer with isRequired="true". 1441 Example of a "domainTransfer" 1442 element. 1444 ... 1445 1446 ... 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1462 domainTransfer-YYYYMMDD.csv 1463 1464 1465 1466 ... 1467 1468 ... 1470 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1471 file contains one domain transfer record with a pending status. 1473 domain1.example,pending,registrarX,clientY, 1474 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1475 2016-04-03T22:00:00.0Z 1477 5.1.2.2. 1479 The is used to hold the deleted domain name 1480 objects in a Differential or Incremental Deposit. All the domain 1481 name object data is deleted as part of a cascade delete. The 1482 is split into separate CSV file definitions using 1483 named elements with the "name" attribute. The following 1484 section defines the supported domain name deletes CSV file 1485 definition. 1487 5.1.2.2.1. "domain" Deletes CSV File Definition 1489 The following "csvDomain" field elements MUST be used in the deletes 1490 "domain" element: 1492 Domain name field with type="eppcom:labelType" and 1493 isRequired="true". 1495 Example of a "domain" element: 1497 ... 1498 1499 ... 1500 1501 1502 1503 1504 1505 1507 domain-delete-YYYYMMDD.csv 1508 1509 1510 1511 ... 1512 1513 ... 1515 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1516 file contains two domain name records. 1518 domain1.example 1519 domain2.example 1521 5.2. Host Object 1523 The host object is based on the EPP host name mapping in [RFC5732]. 1524 The host object supports both the XML Model and the CSV Model, 1525 defined in Models (Section 2) section. The elements used for both 1526 models are defined in the following sections. Both the 1527 and elements contain one or more 1528 elements with a set of named CSV file definitions using 1529 the "name" attribute. 1531 5.2.1. XML Model 1533 There are two elements used in the data escrow of the host objects 1534 for the XML model including the , under the 1535 element, and the element, under 1536 the element. 1538 A element substitutes for the 1539 abstract element to define a concrete definition of a host. The 1540 element can be replaced by other host 1541 definitions using the XML schema substitution groups feature. 1543 5.2.1.1. element 1545 The RDE host object is based on the EPP host response for an 1546 authorized client (Section 3.1.2. of [RFC5732]). 1548 The OPTIONAL element contains the following child elements: 1550 o A element that contains the fully qualified name of the 1551 host object. 1553 o A element that contains the repository object identifier 1554 assigned to the host object when the object was created. 1556 o One or more elements that describe the status of the host 1557 object. 1559 o Zero or more elements that contain the IP addresses 1560 associated with the host object. 1562 o A element that contains the identifier of the sponsoring 1563 registrar. 1565 o An OPTIONAL element that contains the identifier of the 1566 registrar that created the host object. An OPTIONAL client 1567 attribute is used to specify the client that performed the 1568 operation. 1570 o An OPTIONAL element that contains the date and time of 1571 host-object creation. 1573 o An OPTIONAL element that contains the identifier of the 1574 registrar that last updated the host object. This element MUST 1575 NOT be present if the host object has never been modified. An 1576 OPTIONAL client attribute is used to specify the client that 1577 performed the operation. 1579 o An OPTIONAL element that contains the date and time of 1580 the most recent host-object modification. This element MUST NOT 1581 be present if the host object has never been modified. 1583 o An OPTIONAL element that contains the date and time of 1584 the most recent host object successful transfer. This element 1585 MUST NOT be present if the domain name object has never been 1586 transfered. 1588 Example of object: 1590 ... 1591 1592 ns1.example1.example 1593 Hns1_example_test-TEST 1594 1595 1596 192.0.2.2 1597 192.0.2.29 1598 1080:0:0:0:8:800:200C:417A 1599 RegistrarX 1600 RegistrarX 1601 1999-05-08T12:10:00.0Z 1602 RegistrarX 1603 2009-10-03T09:34:00.0Z 1604 1605 ... 1607 5.2.1.2. object 1609 The element contains the fully qualified domain name 1610 of a host that was deleted. The element also 1611 supports host removal based on roid to support SRS systems in which 1612 different hosts with the same fully qualified domain name are active 1613 at the same time. 1615 Example of object: 1617 ... 1618 1619 ... 1620 1621 ns1.example.example 1622 1623 ... 1624 1625 ... 1627 5.2.2. CSV Model 1629 For the CSV Model of the host object, the child 1630 element of the element is used to hold the new or 1631 updated host objects for the deposit. The child 1632 element of the element is used to hold the deleted or 1633 purged host objects for the deposit. 1635 Differential and Incremental Deposits are based on changes to the 1636 host objects. The updated host object data under the 1637 element is a cascade replace down all of the host 1638 CSV files starting with the parent "host" CSV File Definition 1639 (Section 5.2.2.1.1). The child CSV file definitions include a 1640 field. All the child CSV file 1641 definition data for the host objects in the parent "host" CSV File 1642 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1643 using the data in the child CSV files. The deleted host object data 1644 under the element is a cascade delete starting from 1645 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1647 5.2.2.1. 1649 The is used to hold the new or updated host object 1650 information for the deposit. The is split into 1651 separate CSV file definitions using named elements with 1652 the "name" attribute. The following sections include the supported 1653 host CSV file definitions. 1655 5.2.2.1.1. "host" CSV File Definition 1657 The "host" CSV File Definition defines the fields and CSV file 1658 references used for the host object records. 1660 The following "csvHost" field elements MUST be used in the "host" 1661 element: 1663 Host name field with type="eppcom:labelType" and 1664 isRequired="true". 1666 The following "rdeCsv" fields, defined in section CSV common field 1667 elements (Section 4.6.2.2), MUST be used in the "host" 1668 element: 1670 Repository Object IDentifier (ROID) assigned to the 1671 host object with isRequired="true". 1673 The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the 1674 "host" element: 1676 or A choice of: 1678 Identifier of the sponsoring client with 1679 isRequired="true". 1681 Contains the ID assigned by ICANN with 1682 type="positiveInteger". The attribute "isRequired" MUST equal 1683 "true". 1685 Identifier of the registrar, defined in Section 5.4, 1686 of the client that created the object. 1688 Identifier of the client that created the host 1689 object. 1691 Identifier of the registrar, defined in Section 5.4, 1692 of the client that updated the object. 1694 Identifier of the client that last updated the host 1695 object. 1697 Date and time that the host object was created. 1699 Date and time that the host object was last 1700 updated. 1702 Date and time that the host was last transferred. 1704 Example of a "host" element. 1706 ... 1707 1708 ... 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1725 host-YYYYMMDD.csv 1726 1727 1728 1729 ... 1730 1731 ... 1733 Example of the corresponding host-YYYYMMDD.csv file. The file 1734 contains six host records with four being internal hosts and two 1735 being external hosts. 1737 ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX, 1738 clientY,1999-05-08T12:10:00.0Z,registrarX, 1739 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1740 ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX, 1741 clientY,1999-05-08T12:10:00.0Z,registrarX, 1742 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1743 ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX, 1744 clientY,1999-05-08T12:10:00.0Z,registrarX, 1745 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1746 ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, 1747 clientY,1999-05-08T12:10:00.0Z,registrarX, 1748 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1749 ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, 1750 clientY,1999-05-08T12:10:00.0Z,registrarX, 1751 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1752 ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, 1753 clientY,1999-05-08T12:10:00.0Z,registrarX, 1754 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1756 5.2.2.1.2. "hostStatuses" CSV File Definition 1758 The "hostStatuses" CSV File Definition defines the fields and CSV 1759 file references used for the host object statuses. 1761 The following "csvHost" fields, defined for the "host" CSV File 1762 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1763 element: 1765 The status of the host with 1766 type="host:statusValueType" and isRequired="true". 1768 The following "rdeCsv" fields, defined in section CSV common field 1769 elements (Section 4.6.2.2), MUST be used in the "hostStatuses" 1770 element: 1772 Host object Registry Object IDentifier (ROID) 1773 assigned to the host object with isRequired="true". 1775 The following "rdeCsv" fields, defined in section CSV common field 1776 elements (Section 4.6.2.2), MAY be used in the "hostStatuses" 1777 element: 1779 Host object status description which is 1780 free form text describing the rationale for the status. The 1781 attribute "isRequired" MUST equal "true". 1783 Language of the field. 1785 Example of a "hostStatuses" element. 1787 ... 1788 1789 ... 1790 1791 1792 1793 1794 1795 1796 1797 1798 1800 hostStatuses-YYYYMMDD.csv 1801 1802 1803 1804 ... 1805 1806 ... 1808 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1809 file contains the statuses for the six host names 1810 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example, 1811 ns2.domain2.example, ns1.example.net and ns2.example.net. 1813 Hns1_domain1_test-TEST,ok,, 1814 Hns2_domain1_test-TEST,ok,, 1815 Hns1_domain2_test-TEST,ok,, 1816 Hns2_domain2_test-TEST,ok,, 1817 Hns1_example_test-TEST,ok,, 1818 Hns2_example_test-TEST,ok,, 1820 5.2.2.1.3. "hostAddresses" CSV File Definition 1822 The "hostAddresses" CSV File Definition defines the fields and CSV 1823 file references used for the host object IP addresses. 1825 The following "csvHost" field elements MUST be used in the 1826 "hostAddresses" element: 1828 IP addresses associated with the host object with 1829 type="host:addrStringType". The attribute "isRequired" MUST equal 1830 "true". 1832 IP addresses version associated with the host 1833 object with type="host:ipType". "host:ipType" has the enumerated 1834 values of "v4" or "v6". The attribute "isRequired" MUST equal 1835 "true". 1837 The following "rdeCsv" fields, defined in section CSV common field 1838 elements (Section 4.6.2.2), MUST be used in the "hostAddresses" 1839 element: 1841 Host object Registry Object IDentifier (ROID) 1842 assigned to the host object with isRequired="true". 1844 Example of a "hostAddresses" element. 1846 ... 1847 1848 ... 1849 1850 1851 1852 1853 1854 1855 1856 1858 hostAddresses-YYYYMMDD.csv 1859 1860 1861 1862 ... 1863 1864 ... 1866 Example of the corresponding hostAddresses-YYYYMMDD.csv file. The 1867 file contains the IP addresses for the host names 1868 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and 1869 ns2.domain2.example. 1871 Hns1_domain1_test-TEST,192.0.2.1,v4 1872 Hns2_domain1_test-TEST,2001:DB8::1,v6 1873 Hns1_domain2_test-TEST,192.0.2.2,v4 1874 Hns2_domain2_test-TEST,2001:DB8::2,v6 1876 5.2.2.2. 1878 The is used to hold the deleted host objects in a 1879 Differential or Incremental Deposit. All the host object data is 1880 deleted as part of a cascade delete. The is split 1881 into separate CSV file definitions using named elements 1882 with the "name" attribute. The following section defines the 1883 supported host deletes CSV file definition. 1885 5.2.2.2.1. "host" Deletes CSV File Definition 1887 The following "rdeCsv" fields, defined in section CSV common field 1888 elements (Section 4.6.2.2), MUST be used in the "host" 1889 element: 1891 Repository Object IDentifier (ROID) assigned to the 1892 host object with isRequired="true". 1894 Example of a "host" element. 1896 ... 1897 1898 ... 1899 1900 1901 1902 1903 1904 1906 host-delete-YYYYMMDD.csv 1907 1908 1909 1910 ... 1911 1912 ... 1914 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1915 host records. 1917 Hns1_domain1_test-TEST 1918 Hns2_domain1_test-TEST 1919 Hns1_domain2_test-TEST 1920 Hns2_domain2_test-TEST 1922 5.3. Contact Object 1924 The contact object is based on the EPP contact name mapping in 1925 [RFC5733]. The contact object supports both the XML Model and the 1926 CSV Model, defined in Models (Section 2) section. The elements used 1927 for both models are defined in the following sections. 1929 5.3.1. XML Model 1931 There are two elements used in the data escrow of the contact objects 1932 for the XML model including the , under the 1933 element, and the element, 1934 under the element. 1936 A element substitutes for the abstract 1937 element to define a concrete definition of a contact. The 1938 element can be replaced by other contact 1939 definitions using the XML schema substitution groups feature. 1941 5.3.1.1. object 1943 The contact object is based on the EPP contact response for an 1944 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1945 including the data from an EPP Query Response, see 1946 Section 3.1.3. of [RFC5733]. 1948 The OPTIONAL element contains the following child elements: 1950 o A element that contains the server-unique identifier of the 1951 contact object 1953 o A element that contains the Repository Object IDentifier 1954 assigned to the contact object when the object was created. 1956 o One or more elements that describe the status of the 1957 contact object. 1959 o One or two elements that contain postal-address 1960 information. Two elements are provided so that address 1961 information can be provided in both internationalized and 1962 localized forms; a "type" attribute is used to identify the two 1963 forms. If an internationalized form (type="int") is provided, 1964 element content MUST be represented in a subset of UTF-8 that can 1965 be represented in the 7-bit US-ASCII character set. If a 1966 localized form (type="loc") is provided, element content MAY be 1967 represented in unrestricted UTF-8. The element 1968 contains the following child elements: 1970 * A element that contains the name of the individual or 1971 role represented by the contact. 1973 * An OPTIONAL element that contains the name of the 1974 organization with which the contact is affiliated. 1976 * An element that contains address information associated 1977 with the contact. An element contains the following 1978 child elements: 1980 + One, two, or three OPTIONAL elements that contain 1981 the contact's street address. 1983 + A element that contains the contact's city. 1985 + An OPTIONAL element that contains the contact's state 1986 or province. 1988 + An OPTIONAL element that contains the contact's postal 1989 code. 1991 + A element that contains the contact's two-letter 1992 country code. 1994 o An OPTIONAL element that contains the contact's voice 1995 telephone number. 1997 o An OPTIONAL element that contains the contact's facsimile 1998 telephone number. 2000 o An element that contains the contact's email address. 2002 o A element that contains the identifier of the sponsoring 2003 registrar. 2005 o An OPTIONAL element that contains the identifier of the 2006 registrar that created the contact object. An OPTIONAL client 2007 attribute is used to specify the client that performed the 2008 operation. 2010 o An OPTIONAL element that contains the date and time of 2011 contact-object creation. 2013 o An OPTIONAL element that contains the identifier of the 2014 registrar that last updated the contact object. This element MUST 2015 NOT be present if the contact has never been modified. An 2016 OPTIONAL client attribute is used to specify the client that 2017 performed the operation. 2019 o An OPTIONAL element that contains the date and time of 2020 the most recent contact-object modification. This element MUST 2021 NOT be present if the contact object has never been modified. 2023 o An OPTIONAL element that contains the date and time of 2024 the most recent contact object successful transfer. This element 2025 MUST NOT be present if the contact object has never been 2026 transferred. 2028 o An OPTIONAL element that contains the following child 2029 elements related to the last transfer request of the contact 2030 object: 2032 * A element that contains the state of the most recent 2033 transfer request. 2035 * A element that contains the identifier of the registrar 2036 that requested the domain name object transfer. An OPTIONAL 2037 client attribute is used to specify the client that performed 2038 the operation. 2040 * An element that contains the identifier of the registrar 2041 that should act upon a PENDING transfer request. For all other 2042 status types, the value identifies the registrar that took the 2043 indicated action. An OPTIONAL client attribute is used to 2044 specify the client that performed the operation. 2046 * A element that contains the date and time that the 2047 transfer was requested. 2049 * An element that contains the date and time of a 2050 required or completed response. For a PENDING request, the 2051 value identifies the date and time by which a response is 2052 required before an automated response action will be taken by 2053 the registry. For all other status types, the value identifies 2054 the date and time when the request was completed. 2056 o An OPTIONAL element that identifies elements that 2057 requiring exceptional server-operator handling to allow or 2058 restrict disclosure to third parties. See Section 2.9 of 2059 [RFC5733] for a description of the child elements contained within 2060 the element. 2062 Example object: 2064 ... 2065 2066 sh8013 2067 Csh8013-TEST 2068 2069 2070 2071 John Doe 2072 Example Inc. 2073 2074 123 Example Dr. 2075 Suite 100 2076 Dulles 2077 VA 2078 20166-6503 2079 US 2080 2081 2082 +1.7035555555 2083 +1.7035555556 2084 jdoe@example.example 2085 RegistrarX 2086 RegistrarX 2087 2009-09-13T08:01:00.0Z 2088 RegistrarX 2089 2009-11-26T09:10:00.0Z 2090 2009-12-03T09:05:00.0Z 2091 2092 pending 2093 clientW 2094 2011-03-08T19:38:00.0Z 2095 RegistrarX 2096 2011-03-13T23:59:59.0Z 2097 2098 2099 2100 2101 2102 2103 ... 2105 5.3.1.2. object 2107 The element contains the id of a contact that was 2108 deleted. 2110 Example of object: 2112 ... 2113 2114 ... 2115 2116 sh8013-TEST 2117 co8013-TEST 2118 2119 ... 2120 2121 ... 2123 5.3.2. CSV Model 2125 For the CSV Model of the contact object, the 2126 child element of the element is used to hold the new 2127 or updated contacts objects for the deposit. The 2128 child element of the element is 2129 used to hold the deleted or purged contact objects for the deposit. 2130 Both the and elements 2131 contain one or more elements with a set of named CSV 2132 file definitions using the "name" attribute. 2134 Differential and Incremental Deposits are based on changes to the 2135 contact objects. The updated contact object data under the 2136 element is a cascade replace down all of the 2137 contact CSV files starting with the parent "contact" CSV File 2138 Definition (Section 5.3.2.1.1). The child CSV file definitions 2139 include a field. All the child CSV 2140 file definition data for the contact objects in the parent "contact" 2141 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2142 then set using the data in the child CSV files. The deleted contact 2143 object data under the element is a cascade 2144 delete starting from the "contact" Deletes CSV File Definition 2145 (Section 5.3.2.2.1). 2147 5.3.2.1. 2149 The is used to hold the new or updated contact 2150 object information for the deposit. The is 2151 split into separate CSV file definitions using named 2152 elements with the "name" attribute. The following sections include 2153 the supported contact CSV file definitions. 2155 5.3.2.1.1. "contact" CSV File Definition 2157 The "contact" CSV File Definition defines the fields and CSV file 2158 references used for the contact object records. 2160 The following "csvContact" field elements MUST be used in the 2161 "contact" element: 2163 Contains the server-unique contact identifier with 2164 type="eppcom:clIDType" and isRequired="true". 2166 Contains the contact's email address with 2167 type="eppcom:minTokenType" and isRequired="true". 2169 The following field elements MAY be used in the "contact" 2170 element: 2172 Contains the contact's voice telephone number 2173 with type="contact:e164StringType". 2175 Contains the contact's voice telephone number 2176 extension with type="token". 2178 Contains the contact's facsimile telephone number 2179 with type="contact:e164StringType". 2181 Contains the contact's facsimile telephone 2182 number extension with type="token". 2184 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 2185 "contact" element: 2187 The Registry Object IDentifier (ROID) for the contact 2188 object with isRequired="true". 2190 or A choice of: 2192 Identifier of the sponsoring client with 2193 isRequired="true". 2195 Contains the ID assigned by ICANN with 2196 type="positiveInteger". The attribute "isRequired" MUST equal 2197 "true". 2199 The following "rdeCsv" fields, defined in section CSV common field 2200 elements (Section 4.6.2.2), MAY be used in the "contact" 2201 element: 2203 Identifier of the registrar, defined in Section 5.4, 2204 of the client that created the object. 2206 Identifier of the client that created the contact 2207 object. 2209 Identifier of the registrar, defined in Section 5.4, 2210 of the client that updated the object. 2212 Identifier of the client that last updated the 2213 contact object. 2215 Created date and time of the contact object. 2217 Date and time of the last update to the contact 2218 object. 2220 Date and time of the last transfer for the contact 2221 object. 2223 Example of a "contact" element. 2225 ... 2226 2227 ... 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2248 contact-YYYYMMDD.csv 2249 2250 2251 2252 ... 2253 2254 ... 2256 Example of the contact-YYYYMMDD.csv file. The file contains nine 2257 object contact records. 2259 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2260 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2261 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2262 2009-11-26T09:10:00.0Z 2263 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2264 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2265 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2266 2009-11-26T09:10:00.0Z 2267 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2268 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2269 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2270 2009-11-26T09:10:00.0Z 2271 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2272 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2273 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2274 2009-11-26T09:10:00.0Z 2275 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2276 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2277 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2278 2009-11-26T09:10:00.0Z 2279 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2280 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2281 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2282 2009-11-26T09:10:00.0Z 2283 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2284 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2285 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2286 2009-11-26T09:10:00.0Z 2287 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2288 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2289 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2290 2009-11-26T09:10:00.0Z 2291 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2292 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2293 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2294 2009-11-26T09:10:00.0Z 2296 5.3.2.1.2. "contactStatuses" CSV File Definition 2298 The "contactStatuses" CSV File Definition defines the fields and CSV 2299 file references used for the contact object statuses. 2301 The following "csvContact" field elements, defined for the "contact" 2302 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2303 "contactStatuses" element: 2305 Server-unique contact identifier of status with 2306 isRequired="true". 2308 The status of the contact with 2309 type="contact:statusValueType" and isRequired="true". 2311 The following "rdeCsv" fields, defined in section CSV common field 2312 elements (Section 4.6.2.2), MAY be used in the "contactStatuses" 2313 element: 2315 The contact object status description 2316 which is free form text describing the rationale for the status. 2318 Language of the field. 2320 Example of a "contactStatuses" 2321 element. 2323 ... 2324 2325 ... 2326 2327 2328 2329 2330 2331 2332 2333 2334 2336 contactStatuses-YYYYMMDD.csv 2337 2338 2339 2340 ... 2341 2342 ... 2344 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2345 file contains the statuses for the nine contact identifiers. 2347 domain1admin,ok,, 2348 domain1tech,ok,, 2349 domain1billing,ok,, 2350 domain2admin,ok,, 2351 domain2tech,ok,, 2352 domain2billing,ok,, 2353 xnabc123admin,ok,, 2354 xnabc123tech,ok,, 2355 xnabc123billing,ok,, 2357 5.3.2.1.3. "contactPostal" CSV File Definition 2359 The "contactPostal" CSV File Definition defines the fields and CSV 2360 file references used for the contact postal info object records. 2362 The following "csvContact" field elements MUST be used in the 2363 "contactPostal" element: 2365 Contains the form of the postal-address 2366 information with type="contact:postalLineType" and 2367 isRequired="true". This field specifies the form ("int" or 2368 "loc"), as defined in Section 4.6.3, of the , 2369 , , , 2370 , , fields. 2372 Contains the contact's name of the individual or 2373 role represented by the contact with type="contact:postalLineType" 2374 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2375 indicate the localized or internationalized form as defined in 2376 section Section 4.6.3. 2378 Contains the contact's street address line with 2379 type="contact:fPostalLineType". An index attribute is required to 2380 indicate which street address line the field represents with index 2381 "0" for the first line and index "2" for the last line. An 2382 OPTIONAL "isLoc" attribute to used to indicate the localized or 2383 internationalized form as defined in section Section 4.6.3. 2385 Contains the contact's city with 2386 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2387 "isLoc" attribute to used to indicate the localized or 2388 internationalized form as defined in section Section 4.6.3. 2390 Contains the contact's country code with 2391 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2392 attribute to used to indicate the localized or internationalized 2393 form as defined in section Section 4.6.3. 2395 The following "csvContact" field elements MAY be used in the 2396 "contactPostal" element: 2398 Contains the name of the organization with which 2399 the contact is affiliated with type="contact:optPostalLineType". 2400 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2401 internationalized form as defined in section Section 4.6.3. 2403 Contains the contact's state or province with 2404 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2405 to used to indicate the localized or internationalized form as 2406 defined in section Section 4.6.3. 2408 Contains the contact's postal code with 2409 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2410 indicate the localized or internationalized form as defined in 2411 section Section 4.6.3. 2413 The following "csvContact" fields, defined for the "contact" CSV File 2414 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2415 element: 2417 Server-unique contact identifier for the contact 2418 object with isRequired="true". 2420 Example of a "contactPostal" 2421 element. 2423 ... 2424 2425 ... 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2443 contactPostal-YYYYMMDD.csv 2444 2445 2446 2447 ... 2448 2449 ... 2451 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2452 nine contact postal records. 2454 domain1admin,int,"John Doe","Example Inc.", 2455 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2456 domain1tech,int,"John Doe","Example Inc.", 2457 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2458 domain1billing,int,"John Doe","Example Inc.", 2459 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2460 domain2admin,int,"John Doe","Example Inc.", 2461 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2462 domain2tech,int,"John Doe","Example Inc.", 2463 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2464 domain2billing,int,"John Doe","Example Inc.", 2465 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2466 xnabc123admin,int,"John Doe","Example Inc.", 2467 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2468 xnabc123tech,int,"John Doe","Example Inc.", 2469 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2470 xnabc123billing,int,"John Doe","Example Inc.", 2471 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2473 5.3.2.1.4. "contactTransfer" CSV File Definition 2475 The "contactTransfer" CSV File Definition defines the fields and CSV 2476 file references used for the contact object pending and completed 2477 transfer records. No additional field elements were added for use in 2478 the "contactTransfer" element. The 2479 following "rdeCsv" fields, defined in section CSV common field 2480 elements (Section 4.6.2.2), MUST be used in the "contactTransfer" 2481 element: 2483 State of the most recent transfer request with 2484 isRequired="true". 2486 Identifier of the registrar, defined in Section 5.4, 2487 of the client that requested the transfer with isRequired="true". 2489 Date and time that the transfer was requested with 2490 isRequired="true". 2492 Identifier of the registrar, defined in Section 5.4, 2493 of the client that should take or took action with 2494 isRequired="true". 2496 Date and time that the transfer action should be 2497 taken or has been taken with isRequired="true". 2499 The following "rdeCsv" fields, defined in section CSV common field 2500 elements (Section 4.6.2.2), MAY be used in the "contactTransfer" 2501 element: 2503 Identifier of the client that requested the transfer. 2505 Identifier of the client that should take or took 2506 action for transfer. 2508 The following "csvContact" fields, defined for the "contact" CSV File 2509 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2510 element: 2512 Server-unique contact identifier for the contact 2513 object with isRequired="true". 2515 Example of a "contactTransfer" 2516 element. 2518 ... 2519 2520 ... 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2535 contactTransfer-YYYYMMDD.csv 2536 2537 2538 2539 ... 2540 2541 ... 2543 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2544 one contact transfer record in pending status. 2546 xnabc123admin,clientApproved,registrarX,clientX, 2547 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2549 5.3.2.1.5. "contactDisclose" CSV File Definition 2551 The "contactDisclose" CSV File Definition defines the fields and CSV 2552 file references used for the contact disclose object records. 2554 The following "csvContact" field elements MAY be used in the 2555 "contactDisclose" element: 2557 Contains flag with a value of "true" or 2558 "1" (one) notes the preference to allow disclosure of the 2559 specified elements as an exception to the stated data-collection 2560 policy. A value of "false" or "0" (zero) notes a client 2561 preference to not allow disclosure of the specified elements as an 2562 exception to the stated data-collection policy with 2563 type="boolean". The additional fields define specific exceptional 2564 disclosure preferences based on the 2565 field. 2567 Exceptional disclosure preference flag 2568 for the localized form of the contact name with type="boolean". 2570 Exceptional disclosure preference flag 2571 for the internationalized form of the contact name with 2572 type="boolean". 2574 Exceptional disclosure preference flag 2575 for the localized form of the contact organization with 2576 type="boolean". 2578 Exceptional disclosure preference flag 2579 for the internationalized form of the contact organization with 2580 type="boolean". 2582 Exceptional disclosure preference flag 2583 for the localized form of the contact address with type="boolean". 2585 Exceptional disclosure preference flag 2586 for the internationalized form of the contact address with 2587 type="boolean". 2589 Exceptional disclosure preference flag 2590 of the contact voice telephone number with type="boolean". 2592 Exceptional disclosure preference flag of 2593 the contact facsimile telephone number with type="boolean". 2595 Exceptional disclosure preference flag 2596 of the contact email address with type="boolean". 2598 The following "csvContact" fields, defined for the "contact" CSV File 2599 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2600 element: 2602 Server-unique contact identifier for the contact 2603 object with isRequired="true". 2605 Example of a "contactDisclose" 2606 element. 2608 ... 2609 2610 ... 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2628 contactDisclose-YYYYMMDD.csv 2629 2630 2631 2632 ... 2633 2634 ... 2636 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2637 one disclosure records, disabling disclosure of voice, fax, and 2638 email. 2640 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2642 5.3.2.2. 2644 The is used to hold the deleted contact objects 2645 in a Differential or Incremental Deposit. All the contact object 2646 data is deleted as part of a cascade delete. The 2647 is split into separate CSV file definitions 2648 using named elements with the "name" attribute. The 2649 following section defines the supported contact deletes CSV file 2650 definition. 2652 5.3.2.2.1. "contact" Deletes CSV File Definition 2654 The following "csvContact" field elements MUST be used in the deletes 2655 "contact" element: 2657 Contains the server-unique contact identifier with 2658 type="eppcom:clIDType" and isRequired="true". 2660 Example of a "contact" element. 2662 ... 2663 2664 ... 2665 2666 2667 2668 2669 2670 2672 contact-delete-YYYYMMDD.csv 2673 2674 2675 2676 ... 2677 2678 ... 2680 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2681 six contact records. 2683 domain1admin 2684 domain1tech 2685 domain1billing 2686 domain2admin 2687 domain2tech 2688 domain2billing 2690 5.4. Registrar Object 2692 The registrar object represents the sponsoring client for other 2693 objects, and is typically referred to as the sponsoring registrar. 2694 The registrar object supports both the XML Model and the CSV Model, 2695 defined in Section 2. The elements used for both models are defined 2696 in the following sections. 2698 5.4.1. XML Model 2700 There are two elements used in the data escrow of the registrar 2701 objects for the XML model including the , 2702 under the element, and the 2703 element, under the element. 2705 A element substitutes for the 2706 abstract element to define a 2707 concrete definition of a registrar. The 2708 element can be replaced by other 2709 domain definitions using the XML schema substitution groups feature. 2711 5.4.1.1. element 2713 The element contains the following child elements: 2715 o An element that contains the Registry-unique identifier of 2716 the registrar object. This has a superordinate relationship 2717 to a subordinate , or of domain, contact and 2718 host objects. 2720 o An element that contains the name of the registrar. 2722 o An OPTIONAL element that contains the ID assigned by 2723 ICANN. 2725 o An OPTIONAL element that contains the operational status 2726 of the registrar. Possible values are: ok, readonly and 2727 terminated. 2729 o One or two OPTIONAL elements that contain postal- 2730 address information. Two elements are provided so that address 2731 information can be provided in both internationalized and 2732 localized forms; a "type" attribute is used to identify the two 2733 forms. If an internationalized form (type="int") is provided, 2734 element content MUST be represented in a subset of UTF-8 that can 2735 be represented in the 7-bit US-ASCII character set. If a 2736 localized form (type="loc") is provided, element content MAY be 2737 represented in unrestricted UTF-8. The element 2738 contains the following child elements: 2740 * A element that contains address information associated 2741 with the registrar. The element contains the following 2742 child elements: 2744 + One, two, or three OPTIONAL elements that contain 2745 the registrar's street address. 2747 + A element that contains the registrar's city. 2749 + An OPTIONAL element that contains the registrar's state 2750 or province. 2752 + An OPTIONAL element that contains the registrar's 2753 postal code. 2755 + A element that contains the registrar's country code. 2757 o An OPTIONAL element that contains the registrar's voice 2758 telephone number. 2760 o An OPTIONAL element that contains the registrar's facsimile 2761 telephone number. 2763 o An OPTIONAL element that contains the registrar's email 2764 address. 2766 o An OPTIONAL element that contains the registrar's URL. 2768 o An OPTIONAL elements that contains whois information. 2769 The element contains the following child elements: 2771 * An OPTIONAL element that contains the name of the 2772 registrar WHOIS server listening on TCP port 43 as specified in 2773 [RFC3912]. 2775 * An OPTIONAL element that contains the name of the 2776 registrar WHOIS server listening on TCP port 80/443. 2778 o An OPTIONAL element that contains the date and time of 2779 registrar-object creation. 2781 o An OPTIONAL element that contains the date and time of 2782 the most recent RDE registrar-object modification. This element 2783 MUST NOT be present if the rdeRegistrar object has never been 2784 modified. 2786 Example of object: 2788 ... 2789 2790 RegistrarX 2791 Registrar X 2792 123 2793 ok 2794 2795 2796 123 Example Dr. 2797 Suite 100 2798 Dulles 2799 VA 2800 20166-6503 2801 US 2802 2803 2804 +1.7035555555 2805 +1.7035555556 2806 jdoe@example.example 2807 http://www.example.example 2808 2809 whois.example.example 2810 http://whois.example.example 2811 2812 2005-04-23T11:49:00.0Z 2813 2009-02-17T17:51:00.0Z 2814 2815 ... 2817 5.4.1.2. object 2819 The element contains the id of a registrar that 2820 was deleted. 2822 Example of object: 2824 ... 2825 2826 ... 2827 2828 agnt0001-TEST 2829 2830 ... 2831 2832 ... 2834 5.4.2. CSV Model 2836 For the CSV Model of the registrar object, the 2837 child element of the element 2838 is used to hold the new or updated registrar objects for the deposit. 2839 The child element of the element 2840 is used to hold the deleted or purged registrar objects for the 2841 deposit. Both the and 2842 elements contain one or more elements with a set of 2843 named CSV file definitions using the "name" attribute. 2845 Differential and Incremental Deposits are based on changes to the 2846 registrar objects. The updated registrar object data under the 2847 element is a cascade replace down all of the 2848 registrar CSV files starting with the parent "registrar" CSV File 2849 Definition (Section 5.4.2.1.1). The child CSV file definitions 2850 include a field. All the child CSV 2851 file definition data for the registrar objects in the parent 2852 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2853 deleted and then set using the data in the child CSV files. The 2854 deleted registrar object data under the 2855 element is a cascade delete starting from the "registrar" Deletes CSV 2856 File Definition (Section 5.4.2.2.1). 2858 5.4.2.1. 2860 The is used to hold the new or updated 2861 registrar object information for the deposit. The 2862 is split into separate CSV file definitions 2863 using named elements with the "name" attribute. The 2864 following sections include the supported contact CSV file 2865 definitions. 2867 5.4.2.1.1. "registrar" CSV File Definition 2869 The "registrar" CSV File Definition defines the fields and CSV file 2870 references used for the registrar object records. 2872 The following "csvRegistrar" field elements MUST be used in the 2873 "registrar" element: 2875 or A choice of: 2877 Contains the server-unique registrar 2878 identifier with type="eppcom:clIDType" and isRequired="true". 2880 Contains the ID assigned by ICANN with 2881 type="positiveInteger". The attribute "isRequired" MUST equal 2882 "true". 2884 Contains the name of the registrar with 2885 type="normalizedString" and isRequired="true". 2887 The following field elements MAY be used in the "registrar" 2888 element: 2890 Contains the status of the registrar with 2891 type="csvRegistrar:statusValueType". 2893 Contains the ID assigned by ICANN with 2894 type="positiveInteger". This field is included in this section in 2895 addition to the section above to support optionally providing the 2896 field when the field is 2897 used. 2899 Contains the Whois URL of the registrar 2900 with type="anyURI". 2902 The following "rdeCsv" fields, defined in section CSV common field 2903 elements (Section 4.6.2.2), MAY be used in the "registrar" 2904 element: 2906 Created date and time of the registrar object. 2908 Date and time of the last update to the registrar 2909 object. 2911 URL for the registrar web home page. 2913 The following "csvContact" fields, defined in section Contact Object 2914 (Section 5.3), MAY be used in the "registrar" 2915 element: 2917 Registrar street address line with an "index" 2918 attribute that represents the order of the street address line 2919 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2920 indicate the localized or internationalized form, as defined in 2921 Section 4.6.3. 2923 Registrar city with an OPTIONAL "isLoc" attribute 2924 that is used to indicate the localized or internationalized form, 2925 as defined in Section 4.6.3. 2927 Registrar country code with an OPTIONAL "isLoc" 2928 attribute that is used to indicate the localized or 2929 internationalized form, as defined in Section 4.6.3. 2931 Registrar email address. The attribute 2932 "isRequired" MUST equal "false". 2934 Registrar state or province with an OPTIONAL 2935 "isLoc" attribute that is used to indicate the localized or 2936 internationalized form, as defined in Section 4.6.3. 2938 Registrar postal code with an OPTIONAL "isLoc" 2939 attribute that is used to indicate the localized or 2940 internationalized form, as defined in Section 4.6.3. 2942 Registrar voice telephone number. 2944 Registrar voice telephone number extension. 2946 Registrar facsimile telephone number. 2948 Registrar facsimile telephone number extension. 2950 Example of a "registrar" 2951 element. 2953 ... 2954 2955 ... 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2982 registrar-YYYYMMDD.csv 2983 2984 2985 2986 ... 2987 2988 ... 2990 Example of the registrar-YYYYMMDD.csv file. The file contains three 2991 registrar records. 2993 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 2994 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2995 +1.7035555556,,jdoe@example.example,http://www.example.example, 2996 http://whois.example.example,2005-04-23T11:49:00.0Z, 2997 2009-02-17T17:51:00.0Z 2998 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 2999 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3000 +1.7035555556,,jdoe@example.example,http://www.example.example, 3001 http://whois.example.example,2005-04-23T11:49:00.0Z, 3002 2009-02-17T17:51:00.0Z 3003 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 3004 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3005 +1.7035555556,,jdoe@example.example,http://www.example.example, 3006 http://whois.example.example,2005-04-23T11:49:00.0Z, 3007 2009-02-17T17:51:00.0Z 3009 5.4.2.2. 3011 The is used to hold the deleted registrar 3012 objects in a Differential or Incremental Deposit. All the registrar 3013 object data is deleted as part of a cascade delete. The 3014 is split into separate CSV file definitions 3015 using named elements with the "name" attribute. The 3016 following section defines the supported registrar deletes CSV file 3017 definition. 3019 5.4.2.2.1. "registrar" Deletes CSV File Definition 3021 The following "csvRegistrar" field elements MUST be used in the 3022 deletes "registrar" element: 3024 or A choice of: 3026 Contains the server-unique registrar 3027 identifier with type="eppcom:clIDType" and isRequired="true". 3029 Contains the ID assigned by ICANN with 3030 type="positiveInteger". The attribute "isRequired" MUST equal 3031 "true". 3033 Example of a "registrar" element. 3035 ... 3036 3037 ... 3038 3039 3040 3041 3042 3043 3045 registrar-delete-YYYYMMDD.csv 3046 3047 3048 3049 ... 3050 3051 ... 3053 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 3054 one registrar record. 3056 registrarZ 3058 5.5. IDN Table Reference Object 3060 The Internationalized Domain Names (IDN) table reference object is a 3061 pseudo-object that is used to provide a short reference to the IDN 3062 Table and Policy used in IDN registrations. The IDN reference object 3063 supports both the XML and the CSV Model, defined in the Models 3064 (Section 2) section. The elements used for both models are defined 3065 in the following sections. 3067 5.5.1. XML Model 3069 There is one element used in the data escrow of the IDN table 3070 reference objects for the XML model that is the , 3071 under the element. 3073 5.5.1.1. object 3075 The contains the following elements. An "id" 3076 attribute is used to specify an identifier for the IDN table. 3078 o An element that contains the URL of the IDN table that is 3079 being referenced. 3081 o A element that contains the URL of the IDN policy 3082 document. If IDN variants are generated algorithmically, the 3083 policy document MUST define the algorithm and the state of the 3084 implicit generated IDN variants. For a list of suggested states 3085 for implicit IDN variants, please see [variantTLDsReport]. 3087 Example of object: 3089 ... 3090 3091 3092 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3093 3094 3095 http://registro.br/dominio/regras.html 3096 3097 3098 ... 3100 5.5.2. CSV Model 3102 The IDN domain names, defined in Section 5.1, MAY have references to 3103 the IDN language identifier using the field 3104 element. The IDN table reference object defines the mapping of a 3105 language identifier to a language table URL. The language table URL 3106 defines the character code points that can be used for the language 3107 identifier. The elements used for the IDN table reference object is 3108 defined in this section. The child element of the 3109 element is used to hold the new or updated IDN table 3110 reference objects for the deposit. The child 3111 element of the element is used to hold the deleted or 3112 purged IDN table reference objects for the deposit. Both the 3113 and elements contain one or more 3114 elements with a set of named CSV file definitions using 3115 the "name" attribute. 3117 5.5.2.1. 3119 The is used to hold the new or updated IDN table 3120 reference object information for the deposit. The 3121 is split into separate CSV file definitions using named 3122 elements with the "name" attribute. The following sections include 3123 the supported IDN table reference CSV file definitions. 3125 5.5.2.1.1. "idnLanguage" CSV File Definition 3127 The "idnLanguage" CSV File Definition defines the fields and CSV file 3128 references used for the IDN table reference object records. 3130 The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be 3131 used in the "idnLanguage" element: 3133 The language identifier that matches the values 3134 for the field element in the "domain" CSV 3135 File Definition (Section 5.1.2.1.1) files. The attribute 3136 "isRequired" MUST equal "true". 3138 URL that defines the character code points that can be 3139 used for the language defined by the field element. 3140 The attribute "isRequired" MUST equal "true". 3142 Example of a "idnLanguage" element. 3144 ... 3145 3146 ... 3147 3148 3149 3150 3151 3152 3153 3155 idnLanguage-YYYYMMDD.csv 3156 3157 3158 3159 ... 3160 3161 ... 3163 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3164 contains two IDN language records. 3166 LANG-1, 3167 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3168 LANG-2, 3169 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3171 5.5.2.2. 3173 The is used to hold the deleted IDN table reference 3174 objects in a Differential or Incremental Deposit. The 3175 is split into separate CSV file definitions using 3176 named elements with the "name" attribute. The following 3177 section defines the supported IDN table reference deletes CSV file 3178 definition. 3180 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3182 The following "idnLanguage" field elements MUST be used in the 3183 deletes "idnLanguage" element: 3185 The language identifier that matches the values 3186 for the field element in the "domain" CSV 3187 File Definition (Section 5.1.2.1.1) files. The attribute 3188 "isRequired" MUST equal "true". 3190 Example of a "idnLanguage" element. 3192 ... 3193 3194 ... 3195 3196 3197 3198 3199 3200 3202 idnLanguage-delete-YYYYMMDD.csv 3203 3204 3205 3206 ... 3207 3208 ... 3210 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3211 contains one IDN language record. 3213 LANG-2 3215 5.6. NNDN Object 3217 An NNDN (NNDN's not domain name) can be used to store registry 3218 reserved names or (blocked, withheld or mirrored) IDN variants. 3220 Domain Name Registries may maintain domain names without their being 3221 persisted as domain objects in the registry system, for example, a 3222 list of reserved names not available for registration. The NNDN is a 3223 lightweight domain-like object that is used to escrow domain names 3224 not maintained as domain name objects. 3226 A domain name can only exist as a domain name object or an NNDN 3227 object, but not both. 3229 The NNDN object supports both the XML and the CSV Model, defined in 3230 the Models (Section 2) section. The elements used for both models 3231 are defined in the following sections. 3233 5.6.1. XML Model 3235 There are two elements used in the data escrow of the NNDN objects 3236 for the XML model including the , under the 3237 element, and the element, under the 3238 element. 3240 A element substitutes for the 3241 abstract element to define a concrete definition of an NNDN. The 3242 element can be replaced by other NNDN 3243 definitions using the XML schema substitution groups feature. 3245 5.6.1.1. object 3247 The element contains the following child elements: 3249 o An element that contains the fully qualified name of the 3250 NNDN. For IDNs the A-Label is used (see [RFC5891], Section 4.4). 3252 o An OPTIONAL element that contains the fully qualified name 3253 of the NNDN in Unicode character set. It MUST be provided if 3254 available. 3256 o An OPTIONAL element that references the IDN 3257 Table used for the NNDN. This corresponds to the "id" attribute 3258 of the element. This element MUST be present if the 3259 NNDN is an IDN. 3261 o An OPTIONAL element is used to indicate that the 3262 NNDN is used for an IDN variant. This element contains the domain 3263 name used to generate the IDN variant. 3265 o A element that indicates the state of the NNDN: 3266 blocked, withheld or mirrored. 3268 * If an NNDN is considered undesirable for registration (i.e., 3269 unavailable for allocation to anyone), then the NNDN will be 3270 tagged as "blocked". 3272 * If an NNDN is considered a potential registration of a domain 3273 object for a registrant, then the NNDN will be tagged as 3274 "withheld". This status is only used when the NNDN is used for 3275 an IDN variant. 3277 * If an NNDN is considered a mirrored IDN variant of a domain 3278 object, then the NNDN will be tagged as "mirrored". A 3279 mirroringNS attribute is used to specify if the mirrored IDN 3280 variant use the NS mirror mechanism. The default value of 3281 mirroringNS is true. If another mechanism such as DNAME is 3282 used, the value of mirroringNS attribute MUST be false. 3284 o An OPTIONAL element that contains the date and time of 3285 the NNDN object creation. 3287 Example of an object: 3289 ... 3290 3291 xn--exampl-gva.example 3292 pt-BR 3293 example.example 3294 withheld 3295 2005-04-23T11:49:00.0Z 3296 3297 ... 3299 5.6.1.2. object 3301 The element contains the NNDN that was deleted, 3302 i.e., the . 3304 Example of an object: 3306 ... 3307 3308 ... 3309 3310 xn--pingino-q2a.example 3311 3312 ... 3313 3314 ... 3316 5.6.2. CSV Model 3318 For the CSV Model of the NNDN object, the child 3319 element of the element is used to hold the new or 3320 updated NNDN objects for the deposit. The child 3321 element of the element is used to hold the deleted or 3322 purged NNDN objects for the deposit. Both the and 3323 elements contain one or more elements 3324 with a set of named CSV file definitions using the 3325 "name" attribute. 3327 5.6.2.1. 3329 The is used to hold the new or updated NNDN object 3330 information for the deposit. The is split into 3331 separate CSV file definitions using named elements with 3332 the "name" attribute. The following sections include the supported 3333 NNDN CSV file definitions. 3335 5.6.2.1.1. "NNDN" CSV File Definition 3337 The "NNDN" CSV File Definition defines the fields and CSV file 3338 references used for the NNDN object records. 3340 The following "csvNNDN" field elements MUST be used in the "NNDN" 3341 element: 3343 Fully qualified name of the NNDN with 3344 type="eppcom:labelType" and isRequired="true". For IDNs the 3345 A-Label is used (see [RFC5891], Section 4.4). 3347 State of the NNDN: blocked or withheld with 3348 type="rdeNNDN:nameState" and isRequired="true". See 3349 Section 5.6.1.1 for a description of the possible values for the 3350 element. 3352 The following field elements MAY be used in the "NNDN" 3353 element: 3355 Domain name used to generate the IDN variant 3356 with type="eppcom:labelType". 3358 Defines whether the "mirroring" 3359 uses the NS mirror mechanism, as described 3360 for the "mirroringNS" attribute in 3361 Section 5.6.1.1, with type="boolean". If the field element is not 3362 defined the default value is "true". 3364 The following "rdeCsv" fields, defined in section CSV common field 3365 elements (Section 4.6.2.2), MAY be used in the "NNDN" 3366 element: 3368 Created date and time of the NNDN object. 3370 Name of the NNDN in Unicode character set for the 3371 field element. 3373 IDN Table Identifier for the NNDN that matches 3374 an IDN Table Reference Object record, as defined in Section 5.5.2. 3376 Example of an "NNDN" element: 3378 ... 3379 3380 ... 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3393 NNDN-YYYYMMDD.csv 3394 3395 3396 3397 ... 3398 3399 ... 3401 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3402 contains two NNDN records for an IDN with one blocked variant and one 3403 mirrored variant. 3405 xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example, 3406 blocked,,2005-04-23T11:49:00.0Z 3407 xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example, 3408 mirrored,1,2005-04-23T11:49:00.0Z 3410 5.6.2.2. 3412 The is used to hold the deleted NNDN objects in a 3413 Differential or Incremental Deposit. The is split 3414 into separate CSV file definitions using named elements 3415 with the "name" attribute. The following section defines the 3416 supported NNDN deletes CSV file definition. 3418 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3420 The following "NNDN" field elements MUST be used in the deletes 3421 "NNDN" element: 3423 Fully qualified name of the NNDN with 3424 type="eppcom:labelType" and isRequired="true". 3426 Example of an "NNDN" element. 3428 ... 3429 3430 ... 3431 3432 3433 3434 3435 3436 3438 NNDN-delete-YYYYMMDD.csv 3439 3440 3441 3442 ... 3443 3444 ... 3446 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3447 contains one NNDN records. 3449 xn--bc456-3ve.example 3451 5.7. EPP Parameters Object 3453 The EPP Parameters Object is a pseudo-object that defines the set of 3454 object and object extension services supported by the registry, as 3455 defined in [RFC5730]. The EPP Parameters Object is only defined as 3456 XML but could be used in the XML model or CSV model. The EPP 3457 Parameters Object is defined using the 3458 element. The EPP Parameters Object SHOULD be included if the 3459 registry supports EPP. Only one EPP Parameters Object MUST exist at 3460 a certain point in time (watermark). 3462 The syntax and content of the children 3463 elements is as explained in section 2.4 of [RFC5730]. The children 3464 of the are as follows: 3466 o One or more elements that indicate the EPP versions 3467 supported by the registry. 3469 o One or more elements that indicate the identifiers of the 3470 text response languages supported by the registry's EPP server. 3472 o One or more elements that contain namespace URIs 3473 representing the objects that the registry's EPP server is capable 3474 of managing. 3476 o An OPTIONAL element that contains one or more 3477 elements that contain namespace URIs representing object 3478 extensions supported by the registry's EPP server. 3480 o A element that contains child elements used to describe the 3481 server's privacy policy for data collection and management. See 3482 section 2.4 of [RFC5730] for more details. 3484 Example of element object: 3486 ... 3487 3488 1.0 3489 en 3490 urn:ietf:params:xml:ns:domain-1.0 3491 3492 urn:ietf:params:xml:ns:contact-1.0 3493 3494 urn:ietf:params:xml:ns:host-1.0 3495 3496 3497 urn:ietf:params:xml:ns:rgp-1.0 3498 urn:ietf:params:xml:ns:secDNS-1.1 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 ... 3519 5.8. Policy Object 3521 The Policy object is a pseudo-object that is used to specify which 3522 OPTIONAL elements from the XML Model are REQUIRED based on the 3523 business model of the registry. For the CSV Model, the OPTIONAL 3524 "isRequired" attribute of the elements, defined in 3525 Section 4.6.2.1, is used to specify which OPTIONAL fields are 3526 REQUIRED based on the business model of the registry. 3528 5.8.1. object 3530 The OPTIONAL contains the following attributes: 3532 o An that defines that the referenced is 3533 REQUIRED. 3535 o that defines the XPath of the element referenced by 3536 . 3538 Example of object: 3540 ... 3541 3543 ... 3545 5.9. Header Object 3547 The Header Object is a pseudo-object that is used to specify the 3548 number of objects in the repository at a specific point in time 3549 (watermark) regardless of the type of deposit: Differential, Full or 3550 Incremental Deposit. The Header Object may also be used to provide 3551 additional information on the contents of the deposit. The Header 3552 Object is only defined as XML but one header object MUST always be 3553 present per escrow deposit regardless of using XML Model or CSV 3554 Model. The Header Object is defined using the 3555 element. 3557 5.9.1. object 3559 The contains the following elements: 3561 o A choice of one of the elements defined in the 3562 "repositoryTypeGroup" group element that indicates the unique 3563 identifier for the repository being escrowed. Possible elements 3564 are: 3566 * A element that defines TLD or the REGISTRY- 3567 CLASS DOMAIN NAME (RCDN) being escrowed in the case of a 3568 Registry data escrow deposit. For IDNs the A-Label is used 3569 (see [RFC5891], Section 4.4). 3571 * A element that defines the Registrar ID 3572 corresponding to a Registrar data escrow deposit. In the case 3573 of an ICANN-accredited Registrar, the 3574 element MUST be the IANA Registrar ID assigned by ICANN. 3576 * A element that defines the provider ID 3577 corresponding to a Privacy and Proxy Services Provider data 3578 escrow deposit. In the case of an ICANN-accredited Privacy and 3579 Proxy Services Provider, the element MUST be 3580 the unique ID assigned by ICANN. 3582 * A element that defines the provider ID 3583 corresponding to a Reseller data escrow deposit. 3585 o A element that contains the number of objects in the SRS 3586 at a specific point in time (watermark) regardless of the type of 3587 deposit: Differential, Full or Incremental. The element 3588 supports the following attributes: 3590 * A "uri" attribute reflects the XML namespace URI of the primary 3591 objects for the XML Model and CSV Model. For example, the 3592 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3593 domain name objects using the XML Model, and the "uri" is set 3594 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3595 objects using the CSV Model. 3597 * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS 3598 DOMAIN NAME (RCDN) of the objects included in the 3599 element. For IDNs the A-Label is used [RFC5891], Section 4.4. 3600 If the "rcdn" attribute is present, the value of the 3601 element must include only objects related to registrations in 3602 the same and lower levels. For example in a data escrow 3603 deposit for the .EXAMPLE TLD, a value of "example" in the 3604 "rcdn" attribute within the element indicates the 3605 number of objects in the TLD including objects in other RCDNs 3606 within the TLD, whereas a value of "com.example" indicates the 3607 number of elements for objects under "com.example" and lower 3608 levels. Omitting the "rcdn" attribute indicates that the total 3609 includes all objects of the specified "uri" in the repository 3610 (e.g. the TLD, Registrar, or PPSP). 3612 * An OPTIONAL "registrarId" attribute indicates the identifier of 3613 the sponsoring Registrar of the objects included in the 3614 element. In the case of an ICANN-accredited Registrar, the 3615 value MUST be the IANA Registrar ID assigned by ICANN. 3617 o An OPTIONAL element that contains a tag that defines 3618 the expected content in the deposit. The producer and consumer of 3619 the deposits will coordinate the set of possible 3620 element values. 3622 Example of object referencing only the XML Model 3623 objects: 3625 ... 3626 3627 test 3628 2 3630 1 3632 1 3634 1 3636 3637 1 3639 1 3641 1 3643 3644 3645 ... 3647 Example of object referencing the CSV and XML 3648 Model objects: 3650 ... 3651 3652 test 3653 2 3655 1 3657 1 3659 1 3661 3662 1 3664 1 3666 1 3668 3669 3670 ... 3672 6. RDE IDN Variants handling 3674 Depending on the Registration Policy of the Registry, for a domain 3675 name there may be multiple variant names. See [variantTLDsReport] 3676 for further detail on IDN variants. 3678 A registry could choose to escrow IDN variants as domains or NNDN 3679 objects. A specific IDN variant can be represented in the escrow 3680 deposit, as a domain or as an NNDN object, but not both. 3682 If using domain objects to represent IDN variants, the normal 3683 behavior during restoration of an SRS based on an escrow deposit is 3684 to restore the IDN variants as a mirrored variant. If the 3685 registration data of the IDN variant is different from the original 3686 name, the details of this specific implementation MUST be described 3687 in the IDN policy document. 3689 An NNDN or a domain name are explicit representations of an IDN 3690 variant while an IDN variant computed based on an algorithm is an 3691 implicit representation. Explicit representation of an IDN variant 3692 takes precedence over an implicit representation. 3694 7. Profile 3696 Different business models of registries exist, therefore the registry 3697 is responsible for defining a profile that matches its particular 3698 business model. The profile mechanism allows a registry to extend 3699 this specification. 3701 A profile is the process of: 3703 1. Extending base objects with the mechanisms defined for XML and 3704 CSV models. 3706 * In the case of the XML model, abstract elements could be use 3707 to extend the following objects: , , , 3708 and using XML schema substitution groups 3709 feature. 3711 2. Defining a object to specify which OPTIONAL elements of 3712 this base specification is required based on the business model 3713 of the registry. An example is the element that is 3714 usually REQUIRED but it is specified as OPTIONAL in this 3715 specification to support some existing business models. 3717 3. Adding new escrowed objects using the and 3718 elements. 3720 4. Providing the XML schemas to third parties that require them to 3721 validate the escrow deposits. 3723 8. Data escrow agent extended verification process 3725 A Data Escrow Agent SHOULD perform an extended verification process 3726 that starts by creating a dataset to be tested. 3728 o If a Full Deposit is to be tested, the Full Deposit is the 3729 dataset. 3731 o If an Incremental Deposit is to be tested, the dataset is created 3732 by using the Incremental Deposit plus the last previous Full 3733 Deposit. 3735 o If a Differential Deposit is to be tested, the dataset is created 3736 by using the Differential Deposit plus all the required deposits 3737 leading to the last previous Full Deposit. 3739 The following are the minimum suggested tests on the dataset: 3741 o Validate the escrow deposits using the definition agreed with the 3742 registry. 3744 * In the case of the XML model, the contents of the escrow 3745 deposits MUST be validated using the XML schemas of the 3746 profile. 3748 o Count the objects and validate that the number of objects is equal 3749 to the number objects reported in the
element of the 3750 escrow deposit of that point in time (watermark). 3752 o All contact objects linked to domain names MUST be present. 3754 o All registrars objects linked to other objects MUST be present. 3756 o No domain name exists as both a domain name and an NNDN. 3758 o The elements listed as required in the element MUST be 3759 present. 3761 o All idnTableRef definitions linked from other objects MUST be 3762 present. 3764 o If an EPP Parameters Object was escrowed in the past, one and only 3765 one EPP Parameters Object MUST be present. 3767 o The watermark is not in the future. 3769 9. Formal Syntax 3771 Schemas are presented here. 3773 9.1. RDE CSV Schema 3775 BEGIN 3776 3778 3785 3788 3790 3793 3794 3795 Registry Data Escrow Comma-Seperated Values (CSV) 3796 3797 3799 3800 3802 3803 3804 3805 3806 3807 3808 3809 3810 3812 3813 3814 3815 3816 3817 3818 3820 3821 3824 3825 3826 3828 3829 3830 3831 3832 3833 3835 3838 3839 3840 3842 3843 3844 3845 3846 3847 3849 3851 3852 3853 3855 3857 3858 3860 3861 3862 3863 3864 3866 3867 3868 3869 3870 3871 3872 3873 3875 3876 3877 3879 3880 3882 3883 3884 3885 3886 3888 3889 3890 3892 3893 3895 3896 3897 3898 3899 3901 3902 3903 3905 3906 3910 3911 3912 3914 3916 3918 3919 3921 3923 3925 3926 3928 3930 3933 3935 3937 3939 3941 3943 3945 3946 3947 3948 3949 3951 3952 3953 3954 3955 3956 3957 3958 3960 3961 3962 3964 3965 3967 3969 3971 3972 3974 3975 3977 3979 3980 3981 3982 3983 3985 3986 3987 3988 3989 3990 3991 3992 3994 3995 3996 3998 3999 4000 4001 4002 4003 4005 4006 4007 4008 4009 4010 4011 4012 4014 4015 4016 4018 4019 4020 4021 4022 4023 4025 4026 4028 4029 4030 4031 4032 4033 4035 4036 4037 4039 4040 4041 4042 4043 4044 4046 4047 4048 4049 4050 4051 4052 4053 4055 4056 4057 4059 4060 4061 4062 4063 4064 4066 4067 4068 4069 4070 4071 4072 4073 4076 4077 4078 4080 4081 4083 4084 4085 4086 4087 4089 4090 4091 4093 4094 4097 4098 4100 4101 4102 4103 4104 4106 4107 4108 4110 4111 4112 4113 4114 4115 4117 4118 4119 4121 4122 4123 4124 4125 4126 4128 4129 4130 4132 4133 4134 4135 4136 4137 4139 4140 4141 4143 4144 4146 4147 4148 4149 4150 4151 4153 4154 4155 4157 4158 4159 4160 4161 4162 4164 4165 4166 4167 4169 4170 4171 4172 4173 4174 4175 4176 4178 4179 4180 4181 4183 4184 4186 4187 4188 4189 4190 4192 4193 4194 4196 4199 4200 END 4202 9.2. RDE Domain Object 4204 BEGIN 4205 4206 4217 4218 4219 4220 4221 4222 4224 4225 4226 Registry Data Escrow Domain provisioning schema 4227 4228 4230 4233 4235 4239 4240 4241 4242 4243 4244 4246 4248 4250 4252 4254 4256 4259 4261 4264 4266 4268 4270 4272 4274 4276 4278 4280 4282 4285 4286 4287 4288 4290 4291 4292 4294 4296 4298 4300 4302 4304 4305 4307 4308 4309 4310 4311 4312 4316 4317 4318 4319 4320 4321 END 4323 9.3. CSV Domain Object 4325 BEGIN 4326 4328 4339 4342 4344 4346 4348 4350 4352 4355 4356 4357 Domain Name Comma-Separated Values (CSV) Object 4358 4359 4361 4364 4367 4368 4369 4370 4371 4372 4373 4374 4375 4377 4380 4383 4384 4385 4386 4387 4388 4389 4390 4391 4393 4394 4397 4398 4401 4402 4403 4404 4405 4407 4408 4410 4412 4413 4416 4417 4418 4419 4420 4422 4423 4424 4426 4428 4429 4431 4432 4433 4434 4435 4437 4438 4439 4441 4442 4445 4446 4449 4450 4453 4454 4457 4458 4461 4462 4465 4466 4469 4470 4472 4473 4474 4475 4476 4478 4479 4480 4482 4483 4486 4487 4491 4492 4495 4496 4497 4498 4499 4500 4502 4503 4504 4505 4508 4509 END 4511 9.4. RDE Host Object 4513 BEGIN 4514 4515 4523 4524 4525 4527 4528 4529 Registry Data Escrow Host provisioning schema 4530 4531 4533 4535 4536 4539 4540 4541 4542 4543 4544 4546 4548 4550 4554 4556 4558 4560 4562 4564 4566 4567 4568 4569 4571 4572 4573 4574 4575 4576 4578 4580 4581 4582 4583 4584 4585 END 4587 9.5. CSV Host Object 4589 BEGIN 4590 4592 4601 4604 4606 4608 4610 4613 4614 4615 Host Comma-Separated Values (CSV) Object 4616 4617 4619 4622 4625 4626 4627 4628 4629 4630 4631 4632 4633 4635 4638 4641 4642 4643 4644 4645 4646 4647 4648 4649 4651 4652 4655 4656 4658 4659 4660 4661 4662 4664 4665 4666 4668 4669 4671 4672 4673 4674 4675 4677 4678 4679 4681 4682 4685 4686 4687 4688 4689 4690 4692 4693 4694 4696 4700 4701 END 4703 9.6. RDE Contact Object 4705 BEGIN 4706 4707 4715 4716 4717 4718 4720 4721 4722 Registry Data Escrow contact provisioning schema 4723 4724 4726 4729 4731 4735 4736 4737 4738 4739 4740 4742 4744 4746 4748 4750 4752 4754 4756 4758 4760 4762 4764 4766 4768 4770 4771 4772 4773 4775 4776 4777 4778 4779 4780 4781 4782 4783 4785 4786 4787 4788 4789 4790 4793 4795 4796 4797 4798 4799 END 4801 9.7. CSV Contact Object 4803 BEGIN 4804 4806 4815 4818 4820 4822 4824 4827 4828 4829 Contact Comma-Separated Values (CSV) Object 4830 4831 4833 4836 4839 4840 4841 4842 4843 4844 4845 4846 4847 4849 4852 4855 4856 4857 4858 4859 4860 4861 4862 4863 4865 4866 4868 4869 4870 4871 4872 4874 4875 4876 4878 4879 4883 4884 4886 4889 4890 4891 4892 4893 4895 4896 4897 4899 4900 4902 4905 4906 4908 4909 4910 4911 4912 4914 4915 4916 4918 4922 4924 4925 4926 4927 4928 4930 4931 4932 4934 4935 4936 4937 4938 4939 4941 4942 4943 4944 4946 4947 4948 4949 4950 4951 4953 4954 4955 4956 4958 4959 4962 4963 4966 4967 4968 4970 4971 4972 4973 4974 4976 4977 4978 4980 4981 4984 4985 4988 4989 4991 4992 4993 4994 4995 4997 4998 4999 5000 5002 5003 5005 5006 5007 5008 5009 5011 5012 5013 5014 5016 5017 5019 5021 5023 5025 5027 5030 5032 5034 5036 5038 5040 5042 5044 5046 5048 5050 5052 5054 5056 5058 5059 5060 5061 5062 5064 5065 5066 5068 5069 5072 5073 5074 5075 5076 5077 5079 5080 5081 5083 5086 5087 END 5089 9.8. RDE Registrar Object 5091 BEGIN 5092 5093 5102 5103 5104 5105 5106 5108 5109 5110 Registry Data Escrow registrar provisioning schema 5111 5112 5114 5117 5119 5122 5123 5124 5125 5126 5127 5129 5131 5133 5135 5138 5140 5142 5144 5146 5148 5150 5152 5153 5154 5155 5157 5158 5159 5160 5161 5162 5164 5165 5166 5167 5168 5169 5170 5172 5173 5174 5176 5177 5180 5182 5183 5184 5185 5186 5187 5189 5190 5191 5194 5196 5199 5201 5203 5204 5206 5207 5208 5209 5210 5211 5213 5214 5215 5216 5217 5219 5220 5221 5222 5223 5225 5226 5227 5228 5229 5231 5232 5233 5235 5237 5238 5240 5241 5242 5243 5244 5245 5248 5249 5250 5251 5252 5253 END 5255 9.9. CSV Registrar Object 5257 BEGIN 5258 5260 5270 5273 5275 5277 5279 5281 5284 5285 5286 Registar Comma-Separated Values (CSV) Object 5287 5288 5290 5293 5296 5297 5298 5299 5300 5301 5302 5303 5304 5306 5309 5312 5313 5314 5315 5316 5317 5319 5320 5321 5323 5324 5327 5328 5331 5332 5333 5334 5335 5336 5338 5339 5340 5341 5343 5344 5348 5349 5351 5353 5354 5355 5356 5357 5359 5360 5361 5363 5364 5365 5366 5367 5368 5369 5370 5372 5373 5374 5375 5376 5377 5378 5379 5381 5382 5386 5389 5390 END 5392 9.10. RDE IDN Table Reference Objects 5394 BEGIN 5395 5396 5402 5404 5405 5406 Registry Data Escrow IDN provisioning schema 5407 5408 5410 5413 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5429 5430 5431 5432 5433 5434 5435 5436 5437 5439 5440 5441 5442 5443 5444 5445 5447 5448 END 5450 9.11. CSV IDN Language Object 5452 BEGIN 5453 5455 5462 5465 5467 5470 5471 5472 IDN Language Comma-Separated Values (CSV) Object 5473 5474 5476 5479 5482 5483 5484 5485 5486 5487 5488 5489 5490 5492 5495 5498 5499 5500 5501 5502 5503 5504 5505 5506 5508 5512 5513 END 5515 9.12. EPP Parameters Object 5517 BEGIN 5518 5519 5527 5528 5529 5531 5532 5533 Registry Data Escrow EPP Parameters schema 5534 5535 5537 5538 5541 5542 5545 5546 5547 5548 5549 5551 5553 5555 5558 5560 5561 5562 5563 5564 5565 END 5567 9.13. NNDN Object 5569 BEGIN 5570 5571 5579 5580 5581 5583 5584 5585 Registry Data Escrow NNDN provisioning schema 5586 5587 5589 5591 5592 5595 5596 5597 5598 5599 5600 5602 5604 5606 5608 5610 5612 5613 5614 5615 5617 5618 5619 5620 5621 5622 5623 5625 5626 5627 5628 5630 5631 5632 5634 5635 5636 5637 5638 5639 5642 5643 5644 5645 5646 5647 END 5649 9.14. CSV NNDN Object 5651 BEGIN 5652 5654 5662 5665 5667 5669 5672 5673 5674 NNDN (NNDN's not domain name) (CSV) Object 5675 5676 5678 5681 5684 5685 5686 5687 5688 5689 5690 5691 5692 5694 5697 5700 5701 5702 5703 5704 5705 5706 5707 5708 5710 5711 5714 5715 5718 5719 5723 5724 5727 5728 5729 5730 5731 5733 5734 5735 5737 5738 5742 5745 5746 END 5748 9.15. Policy Object 5750 BEGIN 5751 5752 5758 5759 5760 Registry Data Escrow Policy schema 5761 5762 5764 5765 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 END 5779 9.16. Header Object 5781 BEGIN 5782 5783 5790 5791 5793 5794 5795 Data Escrow Deposit Header schema 5797 5798 5800 5801 5804 5805 5806 5807 5808 5809 5810 5812 5814 5815 5816 5817 5819 5820 5821 5822 5823 5824 5825 5826 5828 5829 5830 5831 5832 5833 5834 5835 5836 5838 5839 END 5841 10. Internationalization Considerations 5843 Data Escrow deposits are represented in XML, which provides native 5844 support for encoding information using the Unicode character set and 5845 its more compact representations including UTF-8. Conformant XML 5846 processors recognize both UTF-8 and UTF-16. Though XML includes 5847 provisions to identify and use other character encodings through use 5848 of an "encoding" attribute in an declaration, use of UTF-8 is 5849 RECOMMENDED. 5851 11. IANA Considerations 5853 This document uses URNs to describe XML namespaces and XML schemas 5854 conforming to a registry mechanism described in [RFC3688]. Fourteen 5855 URI assignments have been registered by the IANA. 5857 Registration request for the RDE CSV namespace: 5859 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 5861 Registrant Contact: IETF 5863 XML: None. Namespace URIs do not represent an XML specification. 5865 Registration request for the RDE CSV XML schema: 5867 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 5869 Registrant Contact: IETF 5871 See section Section 9.1 of this document. 5873 Registration request for the RDE domain namespace: 5875 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 5877 Registrant Contact: IETF 5879 XML: None. Namespace URIs do not represent an XML specification. 5881 Registration request for the RDE domain XML schema: 5883 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 5885 Registrant Contact: IETF 5887 See section Section 9.2 of this document. 5889 Registration request for the CSV domain namespace: 5891 URI: urn:ietf:params:xml:ns:csvDomain-1.0 5893 Registrant Contact: IETF 5895 XML: None. Namespace URIs do not represent an XML specification. 5897 Registration request for the CSV domain XML schema: 5899 URI: urn:ietf:params:xml:schema:csvDomain-1.0 5901 Registrant Contact: IETF 5903 See section Section 9.3 of this document. 5905 Registration request for the RDE host namespace: 5907 URI: urn:ietf:params:xml:ns:rdeHost-1.0 5909 Registrant Contact: IETF 5911 XML: None. Namespace URIs do not represent an XML specification. 5913 Registration request for the RDE host XML schema: 5915 URI: urn:ietf:params:xml:schema:rdeHost-1.0 5917 Registrant Contact: IETF 5919 See section Section 9.4 of this document. 5921 Registration request for the CSV host namespace: 5923 URI: urn:ietf:params:xml:ns:csvHost-1.0 5925 Registrant Contact: IETF 5927 XML: None. Namespace URIs do not represent an XML specification. 5929 Registration request for the CSV host XML schema: 5931 URI: urn:ietf:params:xml:schema:csvHost-1.0 5933 Registrant Contact: IETF 5935 See section Section 9.5 of this document. 5937 Registration request for the RDE contact namespace: 5939 URI: urn:ietf:params:xml:ns:rdeContact-1.0 5941 Registrant Contact: IETF 5943 XML: None. Namespace URIs do not represent an XML specification. 5945 Registration request for the RDE contact XML schema: 5947 URI: urn:ietf:params:xml:schema:rdeContact-1.0 5949 Registrant Contact: IETF 5951 See section Section 9.6 of this document. 5953 Registration request for the CSV contact namespace: 5955 URI: urn:ietf:params:xml:ns:csvContact-1.0 5957 Registrant Contact: IETF 5959 XML: None. Namespace URIs do not represent an XML specification. 5961 Registration request for the CSV contact XML schema: 5963 URI: urn:ietf:params:xml:schema:csvContact-1.0 5965 Registrant Contact: IETF 5967 See section Section 9.7 of this document. 5969 Registration request for the RDE registrar namespace: 5971 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 5973 Registrant Contact: IETF 5975 XML: None. Namespace URIs do not represent an XML specification. 5977 Registration request for the RDE registrar XML schema: 5979 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 5981 Registrant Contact: IETF 5983 See section Section 9.8 of this document. 5985 Registration request for the CSV registrar namespace: 5987 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 5989 Registrant Contact: IETF 5991 XML: None. Namespace URIs do not represent an XML specification. 5993 Registration request for the CSV registrar XML schema: 5995 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 5997 Registrant Contact: IETF 5999 See section Section 9.9 of this document. 6001 Registration request for the RDE IDN namespace: 6003 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6005 Registrant Contact: IETF 6007 XML: None. Namespace URIs do not represent an XML specification. 6009 Registration request for the RDE IDN XML schema: 6011 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6013 Registrant Contact: IETF 6015 See section Section 9.10 of this document. 6017 Registration request for the CSV IDN namespace: 6019 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6021 Registrant Contact: IETF 6023 XML: None. Namespace URIs do not represent an XML specification. 6025 Registration request for the CSV IDN XML schema: 6027 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6029 Registrant Contact: IETF 6031 See section Section 9.11 of this document. 6033 Registration request for the RDE NNDN namespace: 6035 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6037 Registrant Contact: IETF 6039 XML: None. Namespace URIs do not represent an XML specification. 6041 Registration request for the RDE NNDN XML schema: 6043 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6045 Registrant Contact: IETF 6047 See section Section 9.13 of this document. 6049 Registration request for the CSV NNDN namespace: 6051 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6053 Registrant Contact: IETF 6055 XML: None. Namespace URIs do not represent an XML specification. 6057 Registration request for the CSV NNDN XML schema: 6059 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6061 Registrant Contact: IETF 6063 See section Section 9.14 of this document. 6065 Registration request for the RDE EPP parameters namespace: 6067 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6069 Registrant Contact: IETF 6071 XML: None. Namespace URIs do not represent an XML specification. 6073 Registration request for the RDE EPP parameters XML schema: 6075 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6077 Registrant Contact: IETF 6079 See section Section 9.12 of this document. 6081 12. Implementation Status 6083 Note to RFC Editor: Please remove this section and the reference to 6084 RFC 7942 [RFC7942] before publication. 6086 This section records the status of known implementations of the 6087 protocol defined by this specification at the time of posting of this 6088 Internet-Draft, and is based on a proposal described in RFC 7942 6089 [RFC7942]. The description of implementations in this section is 6090 intended to assist the IETF in its decision processes in progressing 6091 drafts to RFCs. Please note that the listing of any individual 6092 implementation here does not imply endorsement by the IETF. 6093 Furthermore, no effort has been spent to verify the information 6094 presented here that was supplied by IETF contributors. This is not 6095 intended as, and must not be construed to be, a catalog of available 6096 implementations or their features. Readers are advised to note that 6097 other implementations may exist. 6099 According to RFC 7942 [RFC7942], "this will allow reviewers and 6100 working groups to assign due consideration to documents that have the 6101 benefit of running code, which may serve as evidence of valuable 6102 experimentation and feedback that have made the implemented protocols 6103 more mature. It is up to the individual working groups to use this 6104 information as they see fit". 6106 12.1. Implementation in the gTLD space 6108 Organization: ICANN 6110 Name: ICANN Registry Agreement 6112 Description: the ICANN Base Registry Agreement requires Registries, 6113 Data Escrow Agents, and ICANN to implement this specification. ICANN 6114 receives daily notifications from Data Escrow Agents confirming that 6115 more than 1,200 gTLDs are sending deposits that comply with this 6116 specification. ICANN receives on a weekly basis per gTLD, from more 6117 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6118 also complies with this specification. In addition, ICANN is aware 6119 of Registry Service Provider transitions using data files that 6120 conform to this specification. 6122 Level of maturity: production. 6124 Coverage: all aspects of this specification are implemented. 6126 Version compatibility: versions 03 - 08 are known to be implemented. 6128 Contact: gustavo.lozano@icann.org 6129 URL: https://www.icann.org/resources/pages/registries/registries- 6130 agreements-en 6132 13. Security Considerations 6134 This specification does not define the security mechanisms to be used 6135 in the transmission of the data escrow deposits, since it only 6136 specifies the minimum necessary to enable the rebuilding of a 6137 Registry from deposits without intervention from the original 6138 Registry. 6140 Depending on local policies, some elements or, most likely, the whole 6141 deposit will be considered confidential. As such, the Registry 6142 transmitting the data to the Escrow Agent should take all the 6143 necessary precautions such as encrypting the data itself and/or the 6144 transport channel to avoid inadvertent disclosure of private data. 6146 Authentication of the parties passing data escrow deposit files is 6147 also of the utmost importance. The Escrow Agent SHOULD properly 6148 authenticate the identity of the Registry before accepting data 6149 escrow deposits. In a similar manner, the Registry SHOULD 6150 authenticate the identity of the Escrow Agent before submitting any 6151 data. 6153 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6154 checking mechanisms to ensure the data transmitted is what the source 6155 intended. Validation of the contents by the Escrow Agent is 6156 RECOMMENDED to ensure not only that the file was transmitted 6157 correctly from the Registry, but also that the contents are 6158 "meaningful". 6160 14. Privacy Considerations 6162 This specification defines a format that may be used to escrow 6163 personal data. The process of data escrow is governed by a legal 6164 document agreed by the parties, and such legal document must regulate 6165 the particularities regarding the protection of personal data. 6167 15. Acknowledgments 6169 Parts of this document are based on EPP [RFC5730] and related RFCs by 6170 Scott Hollenbeck. 6172 Special suggestions that have been incorporated into this document 6173 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6174 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6175 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6176 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6177 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6178 Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. 6180 Shoji Noguchi and Francisco Arias participated as co-authors until 6181 version 05 providing invaluable support for this document. 6183 16. Change History 6185 [[RFC Editor: Please remove this section.]] 6187 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6188 dnrd-objects-mapping-00 6190 1. Added definition for child elements under the element. 6192 2. Added definition for child elements under the element. 6194 3. Added definition for child elements under the element. 6196 4. Rewrote the IDN Variants Handling section to use the variant 6197 states as described in ICANN's Study of Issues Related to the 6198 Management of IDN Variant TLDs. 6200 5. Renamed to in the . 6202 6. Renamed to in the element. 6204 7. Renamed to in the element. 6206 8. Added element under element. 6208 9. Fixed some typographical errors and omissions. 6210 16.2. Changes from 00 to 01 6212 1. Specify OPTIONAL elements in the draft. 6214 2. Added NNDN object to support list of reserved names and different 6215 IDN variants models. 6217 3. Removed subordinated host element from the domain object. 6219 4. Added eppParams object. 6221 5. Added variantGenerator element to the domain object. 6223 6. Added lgr to the IDN table object. 6225 16.3. Changes from 01 to 02 6227 1. Updates to the all objects based on feedback from the list. 6229 2. Start of XML and CSV drafts merge. 6231 3. Added header object. 6233 4. Added report object. 6235 5. Added notification object. 6237 6. Added Data Escrow Agent Extended Verification Process section. 6239 7. Added Notifications from Registries to Third Parties. 6241 8. Added Notifications from Data Escrow Agents to Third Parties. 6243 9. Added FULL, DIFF deposit examples using the XML model only. 6245 16.4. Changes from 02 to 03 6247 1. Remove authinfo from the XML Schema. 6249 2. Resend attribute is now an element 6251 3. Scope attribute added to policy object. 6253 16.5. Changes from 03 to 04 6255 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6256 arias-noguchi-dnrd-objects-mapping-02. 6258 2. Changed the cksum attribute of to use CRC32 and 6259 changed all of the sample cksum values to use CRC32, based on 6260 feedback from David Kipling. 6262 3. Changed the optional element to be an optional 6263 "sep" attribute value of the element with a default 6264 value of "," based on feedback from David Kipling. 6266 4. Added support for the optional "parent" attribute for the to the 6267 CSV fields to indicate a field as a reference to a parent 6268 object, based on feedback from David Kipling. 6270 5. Added support for the CSV model for the NNDN. 6272 6. Added support to delete hosts based on roid. 6274 7. Added mirrored state to NNDN 6276 8. Minor fixes to XML XSDs. 6278 9. The Report and Notification objects were moved to draft-lozano- 6279 icann-registry-interfaces 6281 10. The section Data escrow notifications was moved to draft-lozano- 6282 icann-registry-interfaces 6284 11. Removed references to the , , and 6285 from the "hostStatuses" and "hostAddresses" CSV 6286 files. 6288 12. Removed references to the , , and 6289 from the "contactStatuses" CSV file. 6291 13. Removed references to the , , and 6292 from the "domainContacts", "domainStatuses", 6293 and "domainNameServers" CSV files. 6295 14. Changed to . 6297 15. Replaced use of to new field 6298 in the "domain", "idnLanguage", and "NNDN" CSV files. 6300 16. Replaced use of with in the 6301 "host" element. 6303 17. Changed the foreign key of the hosts to use 6304 instead of and removed use of in 6305 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6306 files. 6308 18. Added use of the MUST keyword for CSV fields that are required 6309 to be supported in an EPP based system. 6311 19. Removed use of the field element for the 6312 "registrar" CSV file. 6314 20. Added definition of field element. 6316 16.6. Changes from 04 to 05 6318 1. Updated the examples of the full and differential deposits using 6319 the CSV and XML model. 6321 2. Made optional for the "domainTransfer" CSV file 6322 to match the XML definition. 6324 3. Made optional for the "domain" CSV file 6325 to match the XML definition. 6327 4. Made optional for the "domain" and "contact" CSV 6328 files to match the XML definition. 6330 5. Change from IDREF to idType. 6332 6. Minor editorial changes. 6334 16.7. Changes from 05 to 06 6336 1. Revised the differential and incremental deposits for the CSV 6337 format to use cascade update / replace and delete from the parent 6338 object to be consistent with the XML format. 6340 2. Revised the structure of the CSV format sections to utilize sub- 6341 sections instead of a list for the CSV file definitions. 6343 3. Added the "CSV Parent Child Relationship" section to describe the 6344 concept of parent child relationships across CSV file 6345 definitions. 6347 4. Added the "domainNameServersAddresses" CSV File Definition 6348 section to support the domain host attributes model of [RFC5731]. 6350 5. Made the required fields in the CSV format consistent with the 6351 XML format. The CSV fields updated to be required include: 6352 , , , 6353 , , , 6354 , , , 6355 , , , 6356 , , 6357 , , , 6358 , , 6359 , and . 6361 6. Revised the CSV examples to use a more realistic set of records. 6363 16.8. Changes from 06 to 07 6365 1. Created "repositoryTypeGroup" group element in the rdeHeader 6366 including the , and 6367 elements. 6369 2. Added the optional "rcdn" and "registrarId" attributes to the 6370 element 6372 16.9. Changes from 07 to 08 6374 1. The following registrar elements were made optional to support 6375 greater flexibility for the implementation of policies: status, 6376 postalInfo, email and crDate. 6378 2. The following domain name elements were made optional to support 6379 greater flexibility for the implementation of policies: crRr. 6381 16.10. Changes from 08 to 09 6383 1. Implementation Status section was added 6385 16.11. Changes from 09 to 10 6387 1. Editorial changes in section Section 5.1.2.1.6. 6389 2. Added MAY clause when the DS Data Interface is used in section 6390 Section 5.1.2.1.6. 6392 16.12. Changes from 10 to REGEXT 00 6394 1. Internet Draft (I-D) adopted by the REGEXT WG. 6396 16.13. Changes REGEXT 00 to REGEXT 01 6398 1. Added the element to the 6399 "repositoryTypeGroup" group element in the rdeHeader. 6401 2. Privacy consideration section was added 6403 3. Updates on section 8 6405 16.14. Changes REGEXT 01 to REGEXT 02 6407 1. Added a choice between the use of the or 6408 fields in the CSV "domain", "host", and 6409 "contact" definitions. 6411 2. Added a choice between the use of the or 6412 fields in the CSV "domainNameServers" 6413 definition. 6415 3. Changed "of client" to "of the client" throughout the document. 6417 4. Modified all references of 'The attribute isRequired MUST equal 6418 "true".' to 'The attribute "isRequired" MUST equal "true".' 6420 5. Combined the and 6421 fields in a single required list for the CSV "domainContacts" 6422 definition. 6424 6. Combined the , , and 6425 fields in a single required list for the 6426 CSV "domainStatuses" definition. 6428 7. Moved the the fields to the MAY 6429 list for the CSV "domain", "host", and "contact" definitions. 6431 8. Made the order of the , , 6432 , and fields more consistent in the 6433 CSV lists. 6435 9. Fixed an error in the order of the object example. 6437 10. Changed to be optional to match being 6438 optional in the XML model, by having it use type 6439 rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and 6440 ensuring that is included in the MAY field 6441 lists and not the MUST field lists. 6443 11. Made optional for the "domain" CSV definition 6444 to be consistent with the XML model, by removing the sentence 6445 'The attribute "isRequired" MUST equal "true".' from the 6446 description and moving the field to the MAY field list. 6448 12. Made optional for the "domain" and "contact" 6449 CSV definitions to be consistent with the XML model, by moving 6450 the field to the MAY field list. 6452 13. Made optional to be consistent with the XML 6453 model, by having it use type rdeCsv:fClIDType instead of 6454 rdeCsv:fClIDRequiredType. 6456 14. Made required to be consistent with the XML 6457 model, by having it use type rdeCsv:fClIDRequiredType instead of 6458 rdeCsv:fClIDType. 6460 15. Made the field in the "host", "contact", 6461 and "registrar" CSV definitions required explicitly by removing 6462 'and isRequired="true"' and adding the sentence 'The attribute 6463 isRequired MUST equal "true".', when it is chosen as the primary 6464 field. 6466 16. Removed extra '/>.' at the end of the field 6467 description in the "hostStatuses" CSV definition. 6469 17. Made the field optional to be consistent 6470 with the XML model, by having csvRegistrar:fStatusType extend 6471 rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. 6473 18. Made the field for the "registrar" CSV 6474 definition explicitly optional to be consistent with the XML 6475 model, by adding the sentence 'The attribute isRequired MUST 6476 equal "false".' to the field description and including the 6477 definition of isRequired="false" in the "registrar" CSV 6478 definition examples. 6480 19. Added the choice between the use of the and 6481 fields in the deletes "registrar" CSV 6482 definition to be consistent with the "registrar" CSV definition. 6484 20. Made the and elements optional for the host and 6485 contact objects in the XML model to be consistent with the 6486 domain object. 6488 16.15. Changes REGEXT 02 to REGEXT 03 6490 1. Added the optional element contentTag in the header object. 6492 2. Editorial updates. 6494 16.16. Changes REGEXT 03 to REGEXT 04 6496 1. Note: Updates from version REGEXT 03 to REGEXT 04 attend the 6497 feedback provided during the document shepherd review. 6499 2. Editorial updates. 6501 3. Examples now use domain names from the .example TLD. 6503 4. The introduction was enhanced by explaining the need for data 6504 escrow and the proposed solution. 6506 5. Explanation regarding NNDN was improved. 6508 6. Explanation regarding the CSV and XML model was improved. 6510 7. Section 4.5 updated to make the text clearer. 6512 8. draft-arias-noguchi-registry-data-escrow is now referenced from 6513 the I-D repository. 6515 9. The XML prefix "rdeDomain" is now consistently used. 6517 10. The prevID attribute was removed from the examples of full 6518 deposits. 6520 11. The examples were updated to use present dates. 6522 16.17. Changes REGEXT 04 to REGEXT 05 6524 1. draft-ietf-regext-data-escrow (version 04) is now referenced from 6525 the I-D repository. 6527 2. The example in idnLanguage CSV file definition updated to use the 6528 sep attribute. 6530 3. The reference in the example in hostAddresses CSV file definition 6531 was updated. 6533 4. Moved [RFC0791] and [RFC4291] to the Normative References 6534 section. 6536 16.18. Changes REGEXT 05 to REGEXT 06 6538 1. Changes based on the feedback provided here: 6539 https://mailarchive.ietf.org/arch/msg/regext/ 6540 nA8eTYIrXJ44_6ullQlRLW6T74s 6542 17. Example of a Full Deposit using the XML model 6544 Example of a Full Deposit using the XML model: 6546 6547 6562 2019-10-17T00:00:00Z 6563 6564 1.0 6565 urn:ietf:params:xml:ns:rdeHeader-1.0 6566 6567 urn:ietf:params:xml:ns:rdeContact-1.0 6568 6569 urn:ietf:params:xml:ns:rdeHost-1.0 6570 6571 urn:ietf:params:xml:ns:rdeDomain-1.0 6572 6573 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6574 6575 urn:ietf:params:xml:ns:rdeIDN-1.0 6576 6577 urn:ietf:params:xml:ns:rdeNNDN-1.0 6578 6579 urn:ietf:params:xml:ns:rdeEppParams-1.0 6580 6581 6583 6584 6585 6586 6587 test 6588 2 6590 6591 1 6593 6594 1 6596 6597 1 6599 6600 1 6602 6603 1 6605 6606 1 6608 6609 6610 6611 6612 example1.example 6613 Dexample1-TEST 6614 6615 jd1234 6616 sh8013 6617 sh8013 6618 6619 ns1.example.com 6620 ns1.example1.example 6621 6622 RegistrarX 6623 RegistrarX 6624 1999-04-03T22:00:00.0Z 6625 2015-04-03T22:00:00.0Z 6626 6628 6629 6630 example2.example 6631 Dexample2-TEST 6632 6633 6634 jd1234 6635 sh8013 6636 sh8013 6637 RegistrarX 6638 RegistrarX 6639 1999-04-03T22:00:00.0Z 6640 2015-04-03T22:00:00.0Z 6641 6643 6644 6645 ns1.example1.example 6646 Hns1_example_test-TEST 6647 6648 6649 192.0.2.2 6650 192.0.2.29 6651 1080:0:0:0:8:800:200C:417A 6652 6653 RegistrarX 6654 RegistrarX 6655 1999-05-08T12:10:00.0Z 6656 RegistrarX 6657 2009-10-03T09:34:00.0Z 6659 6661 6662 6663 sh8013 6664 Csh8013-TEST 6665 6666 6667 6668 John Doe 6669 Example Inc. 6670 6671 123 Example Dr. 6672 Suite 100 6673 Dulles 6674 VA 6675 20166-6503 6676 US 6677 6678 6679 +1.7035555555 6680 6681 +1.7035555556 6682 6683 jdoe@example.example 6684 6685 RegistrarX 6686 RegistrarX 6687 6688 2009-09-13T08:01:00.0Z 6689 6690 RegistrarX 6691 6692 2009-11-26T09:10:00.0Z 6693 6694 2009-12-03T09:05:00.0Z 6695 6696 6697 6698 6699 6700 6702 6703 6704 RegistrarX 6705 Registrar X 6706 123 6707 ok 6708 6709 6710 123 Example Dr. 6711 6712 Suite 100 6713 6714 Dulles 6715 VA 6716 20166-6503 6717 US 6718 6719 6720 +1.7035555555 6721 6722 +1.7035555556 6723 6724 jdoe@example.example 6725 6726 http://www.example.example 6727 6728 6729 whois.example.example 6730 6731 http://whois.example.example 6732 6733 6734 2005-04-23T11:49:00.0Z 6735 6736 2009-02-17T17:51:00.0Z 6737 6738 6740 6741 6742 6743 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 6744 6745 6746 http://registro.br/dominio/regras.html 6747 6748 6750 6751 6752 xn--exampl-gva.example 6753 pt-BR 6754 example1.example 6755 withheld 6756 2005-04-23T11:49:00.0Z 6757 6759 6760 6761 1.0 6762 en 6763 6764 urn:ietf:params:xml:ns:domain-1.0 6765 6766 6767 urn:ietf:params:xml:ns:contact-1.0 6768 6769 6770 urn:ietf:params:xml:ns:host-1.0 6771 6772 6773 urn:ietf:params:xml:ns:rgp-1.0 6774 6775 urn:ietf:params:xml:ns:secDNS-1.1 6776 6777 6778 6779 6780 6781 6782 6783 6784 6785 6786 6787 6788 6789 6790 6791 6792 6793 6794 6795 6798 6799 6801 18. Example of Differential Deposit using the XML model 6803 Example of a Differential Deposit using the XML model: 6805 6806 6821 2019-10-17T00:00:00Z 6822 6823 1.0 6824 urn:ietf:params:xml:ns:rdeHeader-1.0 6825 6826 urn:ietf:params:xml:ns:rdeContact-1.0 6827 6828 urn:ietf:params:xml:ns:rdeHost-1.0 6829 6830 urn:ietf:params:xml:ns:rdeDomain-1.0 6831 6832 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6833 6834 urn:ietf:params:xml:ns:rdeIDN-1.0 6835 6836 urn:ietf:params:xml:ns:rdeNNDN-1.0 6837 6838 urn:ietf:params:xml:ns:rdeEppParams-1.0 6839 6840 6842 6843 6844 6845 example2.example 6846 6847 6848 6849 6850 6851 6852 test 6853 1 6855 6856 1 6858 6859 1 6861 6862 1 6864 6865 1 6867 6868 1 6870 6871 1 6873 6874 6875 6876 6878 19. Example of a Full Deposit using the CSV model 6880 Example of a Full Deposit using the CSV model: 6882 6883 6898 2019-10-18T00:00:00Z 6899 6900 1.0 6901 urn:ietf:params:xml:ns:csvDomain-1.0 6902 urn:ietf:params:xml:ns:csvHost-1.0 6903 urn:ietf:params:xml:ns:csvContact-1.0 6904 urn:ietf:params:xml:ns:csvRegistrar-1.0 6905 urn:ietf:params:xml:ns:csvIDN-1.0 6906 urn:ietf:params:xml:ns:csvNNDN-1.0 6907 urn:ietf:params:xml:ns:rdeEppParams-1.0 6908 6909 6910 6911 test 6912 6913 4 6914 6915 6916 6 6917 6918 6919 9 6920 6921 6922 3 6923 6924 6925 2 6926 6927 6928 2 6929 6930 6931 1 6932 6933 6934 6935 6936 6937 6938 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6954 domain-YYYYMMDD.csv 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6967 domainContacts-YYYYMMDD.csv 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980 6982 domainStatuses-YYYYMMDD.csv 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6994 domainNameServers-name-YYYYMMDD.csv 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7006 domainNameServers-roid-YYYYMMDD.csv 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020 7022 dnssec-ds-YYYYMMDD.csv 7023 7024 7025 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7038 dnssec-key-YYYYMMDD.csv 7039 7040 7042 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7058 domainTransfer-YYYYMMDD.csv 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7080 host-YYYYMMDD.csv 7081 7082 7083 7084 7085 7086 7087 7088 7089 7091 7092 7093 7095 hostStatuses-YYYYMMDD.csv 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7108 hostAddresses-YYYYMMDD.csv 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7134 contact-YYYYMMDD.csv 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7148 contactStatuses-YYYYMMDD.csv 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7169 contactPostal-YYYYMMDD.csv 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7187 contactTransfer-YYYYMMDD.csv 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7208 contactDisclose-YYYYMMDD.csv 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7240 registrar-YYYYMMDD.csv 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7254 idnLanguage-YYYYMMDD.csv 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7272 NNDN-YYYYMMDD.csv 7273 7274 7275 7276 7277 7278 1.0 7279 en 7280 urn:ietf:params:xml:ns:domain-1.0 7281 7282 urn:ietf:params:xml:ns:host-1.0 7283 7284 urn:ietf:params:xml:ns:contact-1.0 7285 7286 7287 urn:ietf:params:xml:ns:secDNS-1.1 7288 7289 urn:ietf:params:xml:ns:rgp-1.0 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7316 20. Example of Differential Deposit using the CSV model 7318 Example of a Differential Deposit using the CSV model: 7320 7321 7335 2019-10-18T00:00:00Z 7336 7337 1.0 7338 urn:ietf:params:xml:ns:csvDomain-1.0 7339 urn:ietf:params:xml:ns:csvHost-1.0 7340 urn:ietf:params:xml:ns:csvContact-1.0 7341 urn:ietf:params:xml:ns:csvRegistrar-1.0 7342 urn:ietf:params:xml:ns:csvIDN-1.0 7343 7344 7345 7346 7347 7348 7349 7350 7351 7353 domain-delete-YYYYMMDD.csv 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7366 host-delete-YYYYMMDD.csv 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7379 contact-delete-YYYYMMDD.csv 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7392 registrar-delete-YYYYMMDD.csv 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7405 idnLanguage-delete-YYYYMMDD.csv 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7418 NNDN-delete-YYYYMMDD.csv 7419 7420 7421 7422 7423 7424 7425 7426 test 7427 7428 2 7429 7430 7431 2 7432 7433 7434 3 7435 7436 7437 1 7438 7439 7440 1 7441 7442 7443 1 7444 7445 7446 1 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7469 domain-YYYYMMDD.csv 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7482 domainContacts-YYYYMMDD.csv 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7497 domainStatuses-YYYYMMDD.csv 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7509 domainNameServers-name-YYYYMMDD.csv 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7521 domainNameServers-roid-YYYYMMDD.csv 7522 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7538 dnssec-ds-YYYYMMDD.csv 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7554 dnssec-key-YYYYMMDD.csv 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7573 domainTransfer-YYYYMMDD.csv 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7595 host-YYYYMMDD.csv 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7609 hostStatuses-YYYYMMDD.csv 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7622 hostAddresses-YYYYMMDD.csv 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7648 contact-YYYYMMDD.csv 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7662 contactStatuses-YYYYMMDD.csv 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7683 contactPostal-YYYYMMDD.csv 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7701 contactTransfer-YYYYMMDD.csv 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7722 contactDisclose-YYYYMMDD.csv 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7754 registrar-YYYYMMDD.csv 7755 7756 7757 7758 7759 7760 7761 7762 7763 7765 7766 7767 7769 idnLanguage-YYYYMMDD.csv 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7787 NNDN-YYYYMMDD.csv 7788 7789 7790 7791 7792 7793 1.0 7794 en 7795 urn:ietf:params:xml:ns:domain-1.0 7796 7797 urn:ietf:params:xml:ns:host-1.0 7798 7799 urn:ietf:params:xml:ns:contact-1.0 7800 7801 7802 urn:ietf:params:xml:ns:secDNS-1.1 7803 7804 urn:ietf:params:xml:ns:rgp-1.0 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7831 21. References 7833 21.1. Normative References 7835 [I-D.ietf-regext-data-escrow] 7836 Lozano, G., "Registry Data Escrow Specification", draft- 7837 ietf-regext-data-escrow-04 (work in progress), January 7838 2020. 7840 [ISO-3166-1] 7841 3166, I. S., "Codes for the representation of names of 7842 countries and their subdivisions -- Part 1: Country 7843 codes", ISO Standard 3166, November 2006. 7845 [ITU-E164] 7846 International Telecommunication Union, "The international 7847 public telecommunication numbering plan", ITU-T 7848 Recommendation E.164, February 2005. 7850 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 7851 DOI 10.17487/RFC0791, September 1981, 7852 . 7854 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 7855 Requirement Levels", BCP 14, RFC 2119, 7856 DOI 10.17487/RFC2119, March 1997, 7857 . 7859 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 7860 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 7861 . 7863 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 7864 the Extensible Provisioning Protocol (EPP)", RFC 3915, 7865 DOI 10.17487/RFC3915, September 2004, 7866 . 7868 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 7869 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 7870 2006, . 7872 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 7873 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 7874 . 7876 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 7877 Domain Name Mapping", STD 69, RFC 5731, 7878 DOI 10.17487/RFC5731, August 2009, 7879 . 7881 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 7882 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 7883 August 2009, . 7885 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 7886 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 7887 August 2009, . 7889 [RFC5891] Klensin, J., "Internationalized Domain Names in 7890 Applications (IDNA): Protocol", RFC 5891, 7891 DOI 10.17487/RFC5891, August 2010, 7892 . 7894 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 7895 Security Extensions Mapping for the Extensible 7896 Provisioning Protocol (EPP)", RFC 5910, 7897 DOI 10.17487/RFC5910, May 2010, 7898 . 7900 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 7901 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 7902 May 2017, . 7904 21.2. Informative References 7906 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 7907 DOI 10.17487/RFC3688, January 2004, 7908 . 7910 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 7911 DOI 10.17487/RFC3912, September 2004, 7912 . 7914 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 7915 Code: The Implementation Status Section", BCP 205, 7916 RFC 7942, DOI 10.17487/RFC7942, July 2016, 7917 . 7919 [variantTLDsReport] 7920 Internet Corporation for Assigned Names and Numbers 7921 (ICANN), "A Study of Issues Related to the Management of 7922 IDN Variant TLDs", February 2012, 7923 . 7926 Authors' Addresses 7928 Gustavo Lozano 7929 Internet Corporation for Assigned Names and Numbers 7930 12025 Waterfront Drive, Suite 300 7931 Los Angeles 90292 7932 United States of America 7934 Phone: +1.310.823.9358 7935 Email: gustavo.lozano@icann.org 7937 James Gould 7938 VeriSign, Inc. 7939 12061 Bluemont Way 7940 Reston 20190 7941 United States of America 7943 Email: jgould@verisign.com 7944 Chethan Thippeswamy 7945 VeriSign, Inc. 7946 12061 Bluemont Way 7947 Reston 20190 7948 United States of America 7950 Email: cthippeswamy@verisign.com