idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-08.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 (Jun 3, 2020) is 1395 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' -- Obsolete informational reference (is this intentional?): RFC 7525 (Obsoleted by RFC 9325) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track J. Gould 5 Expires: December 5, 2020 C. Thippeswamy 6 VeriSign 7 Jun 3, 2020 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-08 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 December 5, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 6 57 4. Conventions Used in This Document . . . . . . . . . . . . . . 6 58 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 59 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 7 60 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 7 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 5.10. DNRD Common Objects Collection . . . . . . . . . . . . . 84 75 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 84 76 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 77 8. Data escrow agent extended verification process . . . . . . . 85 78 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 86 79 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 87 80 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 96 81 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98 82 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 102 83 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 104 84 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 106 85 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 108 86 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 114 87 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 117 88 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 120 89 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 121 90 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 123 91 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 124 92 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 126 93 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 128 94 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 128 95 9.17. DNRD Common Objects . . . . . . . . . . . . . . . . . . . 130 96 10. Internationalization Considerations . . . . . . . . . . . . . 130 97 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 130 98 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 138 99 12.1. Implementation in the gTLD space . . . . . . . . . . . . 139 100 13. Security Considerations . . . . . . . . . . . . . . . . . . . 139 101 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 140 102 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 140 103 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 141 104 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 105 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 141 106 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 141 107 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 141 108 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 142 109 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 142 110 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 143 111 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 144 112 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 144 113 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 145 114 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 145 115 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 145 116 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 145 117 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 145 118 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 145 119 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 147 120 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 147 121 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 148 122 16.18. Changes REGEXT 05 to REGEXT 06 . . . . . . . . . . . . . 148 123 16.19. Changes REGEXT 06 to REGEXT 07 . . . . . . . . . . . . . 148 124 16.20. Changes REGEXT 07 to REGEXT 08 . . . . . . . . . . . . . 148 125 17. Example of a Full Deposit using the XML model . . . . . . . . 149 126 18. Example of Differential Deposit using the XML model . . . . . 154 127 19. Example of a Full Deposit using the CSV model . . . . . . . . 156 128 20. Example of Differential Deposit using the CSV model . . . . . 165 129 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 175 130 21.1. Normative References . . . . . . . . . . . . . . . . . . 175 131 21.2. Informative References . . . . . . . . . . . . . . . . . 177 132 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 178 134 1. Introduction 136 Registry Data Escrow is the process by which a registry periodically 137 submits data deposits to a third-party called an escrow agent. These 138 deposits comprise the minimum data needed by a third-party to resume 139 operations if the registry cannot function and is unable or unwilling 140 to facilitate an orderly transfer of service. For example, for a 141 domain name registry or registrar, the data to be deposited would 142 include all the objects related to registered domain names, e.g., 143 names, contacts, name servers, etc. 145 The goal of data escrow is higher resiliency of registration 146 services, for the benefit of Internet users. The beneficiaries of a 147 registry are not just those registering information there, but also 148 the users of services relying on the registry data. 150 In the context of domain name registries, registration data escrow is 151 a requirement for generic top-level domains (e.g., Specification 2 of 152 the ICANN Base Registry Agreement, see [ICANN-GTLD-RA-20170731]) and 153 some country code top-level domain managers are also currently 154 escrowing data. There is also a similar requirement for ICANN- 155 accredited domain registrars. 157 This document defines the standard set of objects for a Domain Name 158 Registry that uses the Registry Data Escrow Specification described 159 in [I-D.ietf-regext-data-escrow] for escrow. The set of objects 160 include: 162 o Domain: Internet domain names that are typically provisioned in a 163 Domain Name Registry using the EPP domain name mapping [RFC5731]. 164 The attributes defined in the EPP domain name mapping [RFC5731] 165 are fully supported by this document. 167 o Host: Internet host names that are typically provisioned in a 168 Domain Name Registry using the EPP host mapping [RFC5732]. The 169 attributes defined in the EPP host mapping [RFC5732] are fully 170 supported by this document. 172 o Contact: Individual or organization social information provisioned 173 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 174 The attributes defined in the EPP contact mapping [RFC5733] are 175 fully supported by this document. 177 o Registrar: The organization that sponsors objects like domains, 178 hosts, and contacts in a Domain Name Registry. 180 o NNDN (NNDN's not domain name): Domain Name Registries may maintain 181 domain names without their being persisted as domain objects in 182 the registry system, for example, a list of reserved names not 183 available for registration. The NNDN is a lightweight domain-like 184 object that is used to escrow domain names not maintained as 185 domain name objects. 187 This document defines the following pseudo-objects: 189 o IDN Table Reference: Internationalized Domain Names (IDN) included 190 in the Domain Object Data Escrow include references to the IDN 191 Table and Policy used in IDN registration. 193 o EPP parameters: Definition of the specific EPP parameters 194 supported by the Registry Operator. 196 o Header: Used to specify counters of objects in the database at a 197 certain point in time (watermark). 199 o Policy: Used to specify OPTIONAL elements from this specification 200 that are REQUIRED based on the business model of the registry. 202 Extensible Markup Language (XML) 1.0 as described in 203 [W3C.REC-xml-20081126] and XML Schema notation as described in 204 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028] are 205 used in this specification. 207 2. Models 209 This document defines two different models that can be used to 210 deposit data escrow objects: XML and CSV. 212 The data escrow deposit MAY contain a mix of both models but an 213 object MUST be escrowed only in one model. 215 This document does not suggest the use of a particular model, and 216 both are equivalent. A Domain Name Registry may choose the model 217 that is more appropriate for the peculiarities of its systems. For 218 example, a registry may use the CSV-export functionality of the RDBMS 219 for escrow; therefore, the CSV model may be more appropriate. 220 Another registry may use the code developed for EPP to implement 221 escrow. 223 2.1. XML Model 225 XML: The XML model includes all the deposit information (meta-data 226 and data) in an XML document. The definition of the XML format is 227 fully defined in the XML schemas. As a convention, the objects 228 represented using the XML model are referenced using RDE and an XML 229 namespace that is prefixed with "rde". For example, the Domain Name 230 object represented using the XML model can be referred to as the RDE 231 Domain Name with the XML namespace including rdeDomain 232 (urn:ietf:params:xml:ns:rdeDomain-1.0). 234 2.2. CSV Model 236 CSV: The CSV model uses XML to define the data escrow format of the 237 data contained in referenced Comma-Separated Values (CSV) files. As 238 a convention, the objects represented using the CSV model is 239 referenced using CSV and an XML namespace that is prefixed with 240 "csv". For example, the Domain Name object represented using the CSV 241 model can be referred to as the CSV Domain Name with the XML 242 namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). 244 3. Terminology 246 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 247 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 248 "OPTIONAL" in this document are to be interpreted as described in BCP 249 14 [RFC2119] [RFC8174] when, and only when, they appear in all 250 capitals, as shown here. 252 REGISTRY. In the context of this draft the definition will be 253 overloaded (from the definition in the base protocol) to indicate an 254 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 255 NAME. 257 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 258 or any other domain name at any level in the DNS tree for which a 259 Registry (either directly or through an affiliate company) provides 260 Registry Services for other organizations or individuals. For 261 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 263 REGISTRY SERVICES. Services offered by the Registry critical to the 264 following tasks: the provisioning of domain names on receipt of 265 requests and data from registrars; responding to registrar queries 266 for status information relating to the DNS servers for the RCDN; 267 dissemination of RCDN zone files; operation of the Registry DNS 268 servers; responding to queries for contact and other information 269 concerning DNS registrations in the RCDN; and any other products or 270 services that only a Registry is capable of providing, by reason of 271 its designation as the Registry. Typical examples of Registry 272 Services are DNS resolution for the RCDN, WHOIS and EPP. 274 ALLOCATED. A status of some label with respect to a zone, whereby 275 the label is associated administratively to some entity that has 276 requested the label. This term (and its cognates "allocation" and 277 "to allocate") may represent the first step on the way to delegation 278 in the DNS. 280 4. Conventions Used in This Document 282 4.1. Date and Time 284 Numerous fields indicate "dates", such as the creation and expiry 285 dates for domain names. These fields SHALL contain timestamps 286 indicating the date and time in UTC as specified in [RFC3339], with 287 no offset from the zero meridian. 289 4.2. Country names 291 Country identifiers SHALL be represented using two character 292 identifiers as specified in [ISO-3166-1]. 294 4.3. Telephone numbers 296 Telephone numbers (both voice and facsimile) SHALL be formatted based 297 on structures defined in [ITU-E164]. Telephone numbers described in 298 this specification are character strings that MUST begin with a plus 299 sign ("+", ASCII value 0x002B), followed by a country code defined in 300 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 301 a sequence of digits representing the telephone number. 303 4.4. Checksum 305 The checksum of the CSV data escrow files MUST use CRC32, which is 306 the algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 307 of ITU-T recommendation V.42. 309 4.5. IP addresses 311 The syntax of IP addresses MUST conform to the text representation of 312 either Internet Protocol Version 4 [RFC0791] or Internet Protocol 313 Version 6 [RFC4291]. 315 4.6. Conventions applicable to the CSV Model 317 4.6.1. CSV Parent Child Relationship 319 The CSV model represents a relational model, where the CSV files 320 represent relational tables, the fields of the CSV files represent 321 columns of the tables, and each line of the CSV file represents a 322 record. As in a relational model, the CSV files can have 323 relationships utilizing primary keys in the parent CSV file 324 definitions and foreign keys in the child CSV file definitions for a 325 1-to-many relationship. The primary keys are not explicitly defined, 326 but the foreign keys are using the boolean "parent" field attribute 327 in the child CSV file. The relationships between the CSV files are 328 used to support a cascade replace or cascade delete of records 329 starting from the parent record in Differential and Incremental 330 Deposits (see [I-D.ietf-regext-data-escrow]). 332 The following is an example of the CSV file definitions for a Sample 333 object consisting of a parent "sample" CSV File Definition and a 334 child "sampleStatuses" CSV File Definition. The primary key for the 335 Sample object is the field that is used as the 336 foreign key in the "sampleStatuses" CSV File Definition by specifying 337 the "parent=true" attribute. If a Sample record is updated or 338 deleted in a Differential or Incremental Deposit, it should cascade 339 replace the data using the records included in the child 340 "sampleStatuses" CSV File Definition or cascade delete the existing 341 records in the child "sampleStatuses" CSV File Definition, 342 respectively. 344 345 ... 346 347 348 349 350 351 352 353 354 355 356 357 358 359 361 sample-YYYYMMDD.csv 362 363 364 365 366 367 368 369 370 371 372 373 375 sampleStatuses-YYYYMMDD.csv 376 377 378 379 ... 380 382 4.6.2. CSV elements 384 4.6.2.1. element 386 To support the CSV model, an element is defined for each object that 387 substitutes for the element and for the 388 element, that contains one or more elements. For 389 example, the Domain Name Object (Section 5.1) defines the 390 element, that substitutes for the 391 element, and the element, that substitutes for 392 the element. Both the element and 393 the elements contain one or more 394 elements. The element has the following child elements: 396 Ordered list of CSV fields used in the CSV files. 397 There are one or more child elements that substitute for the 398 abstract element. Each element defines the format 399 of the CSV field contained in the CSV files. The 400 elements support the "type" attribute that defines the XML simple 401 data type of the field element. The elements 402 support the "isRequired" attribute, with a default value of 403 "false", when set to "true" indicates that the field must be non- 404 empty in the CSV files and when set to "false" indicates that the 405 field MAY be empty in the CSV files. The "isRequired" attribute 406 MAY be specifically set for the field elements within the XML 407 schema and MAY be overridden when specifying the fields under the 408 element. The element supports an 409 OPTIONAL "parent" attribute that identifies the field as a 410 reference to a parent object, as defined in CSV Parent Child 411 Relationship (Section 4.6.1). For example, the field SHOULD set the 413 "parent" attribute to "true" to identify it as the parent domain 414 name of the domain status. 416 A list of one or more CSV files using the 417 child element. The child element 418 defines a reference to the CSV file name and has the following 419 optional attributes: 421 compression If the CSV file is compressed, the "compression" 422 attribute defines the compression format like "gzip" or "zip". 424 encoding Defines the encoding of the CSV file with the default 425 encoding of "UTF-8". 427 cksum Defines the checksum of the CSV file using CRC32, as 428 defined in Section 4.4. This attribute is used to validate 429 that the full CSV file exists and has not been tampered with. 431 The element requires a "name" attribute that defines the 432 purpose of the CSV file with values like "domain", "host", "contact". 433 The supported "name" attribute values are defined for each object 434 type. The OPTIONAL "sep" attribute defines the CSV separator 435 character with the default separator character of ",". 437 The following is an example of the 438 element for domain name records where the is set 439 as required with isRequired="true". 441 442 ... 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 462 domain-YYYYMMDD.csv 463 464 465 466 ... 467 469 The following is example of the "domain-YYYYMMDD.csv" file with one 470 record matching the definition. 472 domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 473 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 474 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 475 The following is an example of the 476 element for domain name records. 478 479 ... 480 481 482 483 484 485 487 domain-delete-YYYYMMDD.csv 488 489 490 491 ... 492 494 The following is example of the "domain-delete-YYYYMMDD.csv" file 495 with three records that matches the single field. 497 domain1.example 498 domain2.example 499 domainN.example 501 4.6.2.2. CSV common field elements 503 The element defined in the element 504 (Section 4.6.2.1) section has child elements that substitute for the 505 abstract element. By convention 506 elements include an 'f' prefix to identify them as field definition 507 elements. There are a set of common field elements that are used 508 across multiple data escrow objects. The common field elements are 509 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 510 using the "rdeCsv" sample namespace prefix. The CSV common field 511 elements include: 513 UTF-8 encoded name field with 514 type="eppcom:labelType". 516 Repository Object IDentifier (ROID) field with 517 type="eppcom:roidType" and isRequired="true". 519 Registrant contact identifier with 520 type="eppcom:clIDType". 522 The object status description, which is 523 free form text describing the rationale for the status, with 524 type="normalizedString". 526 Identifier of the client (registrar) that sponsors 527 the object with type="eppcom:clIDType" and isRequired="true". 529 Identifier of the registrar, defined in Section 5.4, 530 of the client that created the object with type="eppcom:clIDType". 532 Identifier of the client that created the object with 533 type="eppcom:clIDType". 535 Identifier of the registrar, defined in Section 5.4, 536 of the client that updated the object with type="eppcom:clIDType". 538 Identifier of the client that updated the object with 539 type="eppcom:clIDType". 541 Identifier of the registrar, defined in Section 5.4, 542 of the client that requested the transfer with 543 type="eppcom:clIDType" and isRequired="true". 545 Identifier of the client that requested the transfer 546 with type="eppcom:clIDType". 548 Identifier of the registrar, defined in Section 5.4, 549 of the client that should take or took action with 550 type="eppcom:clIDType" and isRequired="true". 552 Identifier of the client that should take or took 553 action for transfer with type="eppcom:clIDType". 555 Created date of object with type="dateTime". 557 Updated date of object with type="dateTime". 559 Expiration date of object with type="dateTime". 561 Date that transfer was requested with 562 type="dateTime" and isRequired="true". 564 Date that transfer action should be taken or has 565 been taken with type="dateTime" and isRequired="true". 567 Date of last transfer with type="dateTime". 569 State of the most recent transfer request with 570 type="eppcom:trStatusType" and isRequired="true". 572 General token field with type="token". 574 General language field with type="language". 576 IDN Table Identifier used for IDN domain names 577 with type="token". 579 General positive integer field with 580 type="positiveInteger". 582 Contains the URL of an object like a registrar object 583 with type="anyURI". 585 Custom field with name attribute that defines the 586 custom field name" with type="token". 588 4.6.3. Internationalized and Localized Elements 590 Some elements MAY be provided in either internationalized form 591 ("int") or localized form ("loc"). Those elements use a field value 592 or "isLoc" attribute to specify the form used. If an "isLoc" 593 attribute is used, a value of "true" indicates the use of the 594 localized form and a value of "false" indicates the use of the 595 internationalized form. This MAY override the form specified for a 596 parent element. A value of "int" is used to indicate the 597 internationalized form and a value of "loc" is used to indicate the 598 localized form. When the internalized form ("int") is provided, the 599 field value MUST be represented in a subset of UTF-8 that can be 600 represented in the 7-bit US-ASCII character set. When the localized 601 form ("loc") is provided, the field value MAY be represented in 602 unrestricted UTF-8. 604 The field elements below of the "registrar" 605 element specify the internationalized form with the 606 isLoc="false" attribute. 608 ... 609 610 ... 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 642 registrar-YYYYMMDD.csv 643 644 645 646 ... 647 648 ... 650 The following is an example of using the 651 field value to define the internationalized or localized form of the 652 remainder of the "contactPostal" field values. 654 ... 655 656 ... 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 674 contactPostal-YYYYMMDD.csv 675 676 677 678 ... 679 680 ... 682 5. Object Description 684 This section describes the base objects supported by this 685 specification: 687 5.1. Domain Name Object 689 The domain name object is based on the EPP domain name mapping 690 specified in [RFC5731]. The domain name object supports both the XML 691 Model and the CSV Model, defined in the Models (Section 2) section. 692 The elements used for both models are defined in the following 693 sections. 695 5.1.1. XML Model 697 There are two elements used in the data escrow of the domain name 698 objects for the XML model including the , under the 699 element, and the element, under the 700 element. 702 5.1.1.1. object 704 The domain element is based on the EPP domain response for an 705 authorized client (see Section 3.1.2. of [RFC5731]) with additional 706 data from an EPP Query Response, see Section 3.1.3. of 707 [RFC5731], RGP status from [RFC3915], and data from the EPP 708 command, see Section 5.2.1. of [RFC5910]. 710 A element substitutes for the abstract 711 element to define a concrete definition of a domain. The 712 element can be replaced by other domain definitions 713 using the XML schema substitution groups feature. 715 The element contains the following child elements: 717 o A element that contains the fully qualified name of the 718 domain name object. For IDNs the A-Label is used (see [RFC5891], 719 Section 4.4). 721 o A element that contains the repository object identifier 722 assigned to the domain name object when it was created. 724 o An OPTIONAL element that contains the fully qualified 725 domain name in Unicode character set. It MUST be provided if 726 available. 728 o An OPTIONAL element that references the IDN 729 Table used for the IDN. This corresponds to the "id" attribute of 730 the element. This element MUST be present if the 731 domain name is an IDN. 733 o An OPTIONAL element is used to indicate that the 734 domain name is an IDN variant. This element contains the domain 735 name used to generate the IDN variant. 737 o One or more elements that contain the current status 738 descriptors associated with the domain name. 740 o Zero or more OPTIONAL elements to represent 741 "pendingDelete" sub-statuses, including "redemptionPeriod", 742 "pendingRestore", and "pendingDelete", that a domain name can be 743 in as a result of grace period processing as specified in 744 [RFC3915]. 746 o An OPTIONAL element that contains the identifier for 747 the human or organizational social information object associated 748 as the holder of the domain name object. 750 o Zero or more OPTIONAL elements that contain identifiers 751 for the human or organizational social information objects 752 associated with the domain name object. 754 o An OPTIONAL element that contains the fully qualified names 755 of the delegated host objects or host attributes (name servers) 756 associated with the domain name object. See Section 1.1 of 757 [RFC5731] for a description of the elements used to specify host 758 objects or host attributes. 760 o A element that contains the identifier of the sponsoring 761 registrar. 763 o An OPTIONAL element that contains the identifier of the 764 registrar that created the domain name object. An OPTIONAL client 765 attribute is used to specify the client that performed the 766 operation. 768 o An OPTIONAL element that contains the date and time of 769 the domain name object creation. This element MUST be present if 770 the domain name has been allocated. 772 o An OPTIONAL element that contains the date and time 773 identifying the end (expiration) of the domain name object's 774 registration period. This element MUST be present if the domain 775 name has been allocated. 777 o An OPTIONAL element that contains the identifier of the 778 registrar that last updated the domain name object. This element 779 MUST NOT be present if the domain has never been modified. An 780 OPTIONAL client attribute is used to specify the client that 781 performed the operation. 783 o An OPTIONAL element that contains the date and time of 784 the most recent domain-name-object modification. This element 785 MUST NOT be present if the domain name object has never been 786 modified. 788 o An OPTIONAL element that contains the public key 789 information associated with Domain Name System security (DNSSEC) 790 extensions for the domain name as specified in [RFC5910]. 792 o An OPTIONAL element that contains the date and time of 793 the most recent domain object successful transfer. This element 794 MUST NOT be present if the domain name object has never been 795 transferred. 797 o An OPTIONAL element that contains the following child 798 elements related to the last transfer request of the domain name 799 object. This element MUST NOT be present if a transfer request 800 for the domain name has never been created. 802 * A element that contains the state of the most recent 803 transfer request. 805 * A element that contains the identifier of the registrar 806 that requested the domain name object transfer. An OPTIONAL 807 client attribute is used to specify the client that performed 808 the operation. 810 * A element that contains the date and time that the 811 transfer was requested. 813 * An element that contains the identifier of the registrar 814 that should act upon a PENDING transfer request. For all other 815 status types, the value identifies the registrar that took the 816 indicated action. An OPTIONAL client attribute is used to 817 specify the client that performed the operation. 819 * An element that contains the date and time of a 820 required or completed response. For a PENDING request, the 821 value identifies the date and time by which a response is 822 required before an automated response action will be taken by 823 the registry. For all other status types, the value identifies 824 the date and time when the request was completed. 826 * An OPTIONAL element that contains the end of the 827 domain name object's validity period (expiry date) if the 828 transfer caused or causes a change in the validity period. 830 Example of a domain object: 832 ... 833 834 xn--exampl-gva.example 835 Dexample1-TEST 836 pt-BR 837 example.example 838 839 jd1234 840 sh8013 841 sh8013 842 843 ns1.example.com 844 ns1.example1.example 845 846 RegistrarX 847 RegistrarX 848 1999-04-03T22:00:00.0Z 849 2015-04-03T22:00:00.0Z 850 851 ... 853 5.1.1.2. object 855 The element contains the fully qualified domain 856 name that was deleted and purged. 858 Example of object: 860 ... 861 862 ... 863 864 foo.example 865 bar.example 866 867 ... 868 869 ... 871 5.1.2. CSV Model 873 For the CSV Model of the domain name object, the 874 child element of the element is used to hold the new 875 or updated domain name objects for the deposit. The 876 child element of the element is 877 used to hold the deleted or purged domain name objects for the 878 deposit. Both the and 879 elements contain one or more elements with a set of 880 named CSV file definitions using the "name" attribute. 882 Differential and Incremental Deposits are based on changes to the 883 domain name objects. The updated domain name object data under the 884 element is a cascade replace down all of the 885 domain name CSV files starting with the parent "domain" CSV File 886 Definition (Section 5.1.2.1.1). The child CSV file definitions 887 include a field. All the child CSV 888 file definition data for the domain name objects in the parent 889 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 890 deleted and then set using the data in the child CSV files. The 891 deleted domain name object data under the element 892 is a cascade delete starting from the "domain" Deletes CSV File 893 Definition (Section 5.1.2.2.1). 895 5.1.2.1. 897 The is used to hold the new or updated domain 898 name object information for the deposit. The is 899 split into separate CSV file definitions using named 900 elements with the "name" attribute. The following sections include 901 the supported domain name CSV file definitions: 903 5.1.2.1.1. "domain" CSV File Definition 905 The "domain" CSV File Definition defines the fields and CSV file 906 references used for the parent domain name object records. All the 907 other domain name CSV file definitions are child CSV files based on 908 the inclusion of the field. 910 The following "csvDomain" field elements MUST be used in the "domain" 911 element: 913 Domain name field with type="eppcom:labelType" and 914 isRequired="true". 916 The following "csvDomain" field elements MAY be used in the "domain" 917 element: 919 Fully qualified name of the original IDN 920 domain name object related to the variant domain name object with 921 type="eppcom:labelType". 923 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 924 "domain" element: 926 Registry Object IDentifier (ROID) for the domain name 927 object with isRequired="true". 929 or A choice of: 931 Identifier of the sponsoring client with 932 isRequired="true". 934 Contains the ID assigned by ICANN with 935 type="positiveInteger". The attribute "isRequired" MUST equal 936 "true". 938 The following "rdeCsv" fields, defined in section CSV common field 939 elements (Section 4.6.2.2), MAY be used in the "domain" 940 element: 942 Identifier of the registrar, defined in Section 5.4, 943 of the client that created the object. 945 Identifier of the client that created the domain name 946 object. 948 Identifier of the registrar, defined in Section 5.4, 949 of the client that updated the object. 951 Identifier of the client that last updated the domain 952 name object. 954 UTF8 encoded domain name for the 955 field element. 957 IDN Table Identifier used for the IDN domain 958 name object that MUST match a field element 959 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 961 Registrant contact identifier for the domain 962 name object. 964 Created date and time of the domain name object. 966 Date and time of the last update to the domain name 967 object. 969 Expiration date and time for the domain name 970 object. 972 Date and time of the last transfer for the domain 973 name object. 975 Example of a "domain" element. 977 ... 978 979 ... 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 999 domain-YYYYMMDD.csv 1000 1001 1002 1003 ... 1004 1005 ... 1007 Example of the corresponding domain-YYYYMMDD.csv file. The file 1008 contains four records (two active ASCII domains, original IDN with 1009 LANG-1 language rules, and variant IDN with LANG-1 language rules). 1011 domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 1012 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1013 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1014 domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 1015 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 1016 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1017 xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 1018 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1019 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1020 xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example, 1021 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 1022 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1024 5.1.2.1.2. "domainContacts" CSV File Definition 1026 The "domainContacts" CSV File Definition defines the fields and CSV 1027 file references used for the domain name object link records to 1028 contact objects, as described in Contact Object (Section 5.3). 1030 The following "csvDomain" field elements, defined for the "domain" 1031 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 1032 "domainContacts" element: 1034 The name of the domain object that is linked to 1035 the contact object with isRequired="true". 1037 The contact type for the contact object 1038 link with type="domain:contactAttrType" and isRequired="true". 1039 The supported contact type values include "admin" for the 1040 administration contact, "billing" for the billing contact, and 1041 "tech" for the technical contact. 1043 The following "csvContact" fields, defined for the "contact" CSV File 1044 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 1045 element: 1047 The server-unique contact identifier with 1048 isRequired="true". 1050 Example of a "domainContacts" 1051 element. 1053 ... 1054 1055 ... 1056 1057 1058 1059 1060 1061 1062 1063 1065 domainContacts-YYYYMMDD.csv 1066 1067 1068 1069 ... 1070 1071 ... 1073 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1074 file contains an admin, tech, and billing contact for the four domain 1075 names domain1.example, domain2.example, xn--bc123-3ve.example and 1076 xn--bc321-3ve.example. 1078 domain1.example,domain1admin,admin 1079 domain1.example,domain1tech,tech 1080 domain1.example,domain1billing,billing 1081 domain2.example,domain2admin,admin 1082 domain2.example,domain2tech,tech 1083 domain2.example,domain2billing,billing 1084 xn--bc123-3ve.example,xnabc123admin,admin 1085 xn--bc123-3ve.example,xnabc123tech,tech 1086 xn--bc123-3ve.example,xnabc123billing,billing 1087 xn--bc321-3ve.example,xnabc123admin,admin 1088 xn--bc321-3ve.example,xnabc123tech,tech 1089 xn--bc321-3ve.example,xnabc123billing,billing 1091 5.1.2.1.3. "domainStatuses" CSV File Definition 1093 The "domainStatuses" CSV File Definition defines the fields and CSV 1094 file references used for the domain name object statuses. 1096 The following "csvDomain" fields, defined for the "domain" CSV File 1097 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1098 element: 1100 Domain name of status with isRequired="true". 1102 The status of the domain name with 1103 type="domain:statusValueType" and isRequired="true". 1105 The Registry Grace Period (RGP) status, as a 1106 sub-status of the "pendingDelete" status 1107 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1109 The following "rdeCsv" fields, defined in section CSV common field 1110 elements (Section 4.6.2.2), MAY be used in the "domainStatuses" 1111 element: 1113 Domain object status description which 1114 is free form text describing the rationale for the status. 1116 Language of the field. 1118 Example of a "domainStatuses" 1119 element. 1121 ... 1122 1123 ... 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1135 domainStatuses-YYYYMMDD.csv 1136 1137 1138 1139 ... 1140 1141 ... 1143 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1144 file contains the statuses for the four domain names domain1.example, 1145 domain2.example, xn--bc123-3ve.example and xn--bc321-3ve.example. 1147 domain1.example,clientUpdateProhibited,"Disallow update", 1148 en, 1149 domain1.example,clientDeleteProhibited,"Disallow delete", 1150 en, 1151 domain2.example,ok,,, 1152 xn--bc123-3ve.example,ok,,, 1153 xn--bc321-3ve.example,ok,,, 1155 5.1.2.1.4. "domainNameServers" CSV File Definition 1157 The "domainNameServers" CSV File Definition defines the fields and 1158 CSV file references used for the domain name delegated hosts (name 1159 servers). The "domainNameServers" CSV files define the relationship 1160 between a domain name object and a delegated host. The 1161 "domainNameServers" CSV File is used to support the 1162 model, defined in [RFC5731]. 1164 The following "csvDomain" fields, defined for the "domain" CSV File 1165 Definition (Section 5.1.2.1.1), MUST be used in the 1166 "domainNameServers" element: 1168 Domain name using the delegated host with 1169 isRequired="true". 1171 The following "csvHost" and "rdeCsv" field elements MUST be used in 1172 the "domainNameServers" element: 1174 or A choice of: 1176 Host name field with type="eppcom:labelType" and 1177 isRequired="true". 1179 Host object Registry Object IDentifier (ROID) 1180 assigned to the host object with isRequired="true". 1182 Example of a "domainNameServers" 1183 element. 1185 ... 1186 1187 ... 1188 1189 1190 1191 1192 1193 1194 1196 domainNameServers-YYYYMMDD.csv 1197 1198 1199 1200 ... 1201 1202 ... 1204 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1205 The file contains the delegated hosts (name servers) for the four 1206 domain names domain1.example, domain2.example, xn--bc123-3ve.example 1207 and xn--bc321-3ve.example referenced via the field 1208 element. 1210 domain1.example,Hns1_domain1_test-TEST 1211 domain1.example,Hns2_domain1_test-TEST 1212 domain2.example,Hns1_domain2_test-TEST 1213 domain2.example,Hns2_domain2_test-TEST 1214 xn--bc123-3ve.example,Hns1_example_test-TEST 1215 xn--bc123-3ve.example,Hns2_example_test-TEST 1216 xn--bc321-3ve.example,Hns1_example_test-TEST 1217 xn--bc321-3ve.example,Hns2_example_test-TEST 1219 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1221 The "domainNameServersAddresses" CSV File Definition defines the 1222 fields and CSV file references used for supporting the host as domain 1223 attributes model. 1225 The following "csvDomain" fields, defined for the "domain" CSV File 1226 Definition (Section 5.1.2.1.1), MUST be used in the 1227 "domainNameServersAddresses" element: 1229 Domain name using the delegated host with host 1230 and isRequired="true". 1232 The following "rdeCsv" fields, defined in section Host CSV model 1233 elements (Section 5.2.2), MUST be used in the 1234 "domainNameServersAddresses" element: 1236 Host name field with type="eppcom:labelType" and 1237 isRequired="true". 1239 The following "csvHost" fields, defined in section Host CSV model 1240 elements (Section 5.2.2), MAY be used in the 1241 "domainNameServersAddresses" element: 1243 IP addresses associated with the host object with 1244 type="host:addrStringType". 1246 IP addresses version associated with the host 1247 object with type="host:ipType". "host:ipType" has the enumerated 1248 values of "v4" or "v6". 1250 Example of a "domainNameServersAddresses" 1251 element. 1253 ... 1254 1255 ... 1256 1257 1258 1259 1260 1261 1262 1263 1264 1266 domainNameServersAddresses-YYYYMMDD.csv 1267 1268 1269 1270 ... 1271 1272 ... 1274 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1275 file. The file contains the delegated hosts (name servers) for the 1276 four domain names domain1.example, domain2.example, xn-- 1277 bc123-3ve.example and xn--bc321-3ve.example. 1279 domain1.example,ns1.domain1.example,192.0.2.1,v4 1280 domain1.example,ns2.domain1.example,2001:DB8::1,v6 1281 domain2.example,ns1.example.net,, 1282 domain2.example,ns2.example.net,, 1283 xn--bc123-3ve.example,ns1.example.net,, 1284 xn--bc123-3ve.example,ns2.example.net,, 1285 xn--bc321-3ve.example,ns1.example.net,, 1286 xn--bc321-3ve.example,ns2.example.net,, 1288 5.1.2.1.6. "dnssec" CSV File Definition 1290 The "dnssec" CSV File Definition defines the fields and CSV file 1291 references used for the domain name object DNSSEC records (DS or Key 1292 Data). 1294 The following "csvDomain" field elements MUST be used in the "dnssec" 1295 element when the DS Data Interface per 1296 [RFC5910] is used: 1298 Contains the DS key tag value per [RFC5910] with 1299 type="unsignedShort" and isRequired="true". 1301 Contains the DS algorithm value per [RFC5910] 1302 with type="unsignedByte" and isRequired="true". 1304 Contains the DS digest type value per 1305 [RFC5910] with type="unsignedByte" and isRequired="true". 1307 Contains the DS digest value per [RFC5910] with 1308 type="hexBinary" and isRequired="true". 1310 The following "csvDomain" field elements MUST be used in the "dnssec" 1311 element when the Key Data Interface per 1312 [RFC5910] is used and MAY be used in the "dnssec" 1313 element when the DS Data Interface per [RFC5910] is 1314 used: 1316 Contains the flags field value per [RFC5910] with 1317 type="unsignedShort" and isRequired="true". 1319 Contains the Key protocol value per [RFC5910] 1320 with type="unsignedByte" and isRequired="true". 1322 Contains the Key algorithm value per [RFC5910] 1323 with type="unsignedByte" and isRequired="true". 1325 Contains the public key value per [RFC5910] with 1326 type="secDNS:keyType" and isRequired="true". 1328 The following "csvDomain" field elements MAY be used in the "dnssec" 1329 element: 1331 Indicates a child's preference for the 1332 number of seconds after signature generation when the parent's 1333 signature on the DS information provided by the child will expire 1334 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1336 The following "domain" fields, defined for the "domain" CSV File 1337 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1338 element: 1340 Domain name of the domain object associated with 1341 the DNSSEC record and isRequired="true". 1343 Example of a "dnssec" element with 1344 the DS Data Interface of [RFC5910]: 1346 1347 ... 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1360 dnssec-ds-YYYYMMDD.csv 1361 1362 1363 1364 ... 1365 1366 ... 1368 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1369 contains two DS records for domain1.example. 1371 domain1.example,604800,12345,3,1,49FD46E6C4B45C55D4AC 1372 domain1.example,604800,12346,3,1,38EC35D5B3A34B44C39B 1373 Example of a "dnssec" element with 1374 the Key Data Interface of [RFC5910]: 1376 1377 ... 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1390 dnssec-key-YYYYMMDD.csv 1391 1392 1393 1394 ... 1395 1396 ... 1398 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1399 contains two key records for domain1.example. 1401 domain1.example,604800,257,3,1,AQPJ////4Q== 1402 domain1.example,604800,257,3,1,AQPJ////4QQQ 1404 5.1.2.1.7. "domainTransfer" CSV File Definition 1406 The "domainTransfer" CSV File Definition defines the fields and CSV 1407 file references used for the domain name object pending and completed 1408 transfer records. No additional field elements were added for use in 1409 the "domainTransfer" element. 1411 The following "rdeCsv" fields, defined in section CSV common field 1412 elements (Section 4.6.2.2), MUST be used in the "domainTransfer" 1413 element: 1415 State of the most recent transfer request with 1416 isRequired="true". 1418 Identifier of the registrar, defined in Section 5.4, 1419 of the client that requested the transfer with isRequired="true". 1421 Date and time that the transfer was requested with 1422 isRequired="true". 1424 Identifier of the registrar, defined in Section 5.4, 1425 of the client that should take or took action with 1426 isRequired="true". 1428 Date and time that the transfer action should be 1429 taken or has been taken with isRequired="true". 1431 The following "rdeCsv" fields, defined in section CSV common field 1432 elements (Section 4.6.2.2), MAY be used in the "domainTransfer" 1433 element: 1435 Expiration date if the transfer command caused or 1436 causes a change in the validity period. 1438 Identifier of the client that requested the transfer. 1440 Identifier of the client that should take or took 1441 action for transfer. 1443 The following "csvDomain" fields, defined for the "domain" CSV File 1444 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1445 element: 1447 Domain name of the domain object involved in the 1448 transfer with isRequired="true". 1450 Example of a "domainTransfer" 1451 element. 1453 ... 1454 1455 ... 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1471 domainTransfer-YYYYMMDD.csv 1472 1473 1474 1475 ... 1476 1477 ... 1479 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1480 file contains one domain transfer record with a pending status. 1482 domain1.example,pending,registrarX,clientY, 1483 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1484 2016-04-03T22:00:00.0Z 1486 5.1.2.2. 1488 The is used to hold the deleted domain name 1489 objects in a Differential or Incremental Deposit. All the domain 1490 name object data is deleted as part of a cascade delete. The 1491 is split into separate CSV file definitions using 1492 named elements with the "name" attribute. The following 1493 section defines the supported domain name deletes CSV file 1494 definition. 1496 5.1.2.2.1. "domain" Deletes CSV File Definition 1498 The following "csvDomain" field elements MUST be used in the deletes 1499 "domain" element: 1501 Domain name field with type="eppcom:labelType" and 1502 isRequired="true". 1504 Example of a "domain" element: 1506 ... 1507 1508 ... 1509 1510 1511 1512 1513 1514 1516 domain-delete-YYYYMMDD.csv 1517 1518 1519 1520 ... 1521 1522 ... 1524 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1525 file contains two domain name records. 1527 domain1.example 1528 domain2.example 1530 5.2. Host Object 1532 The host object is based on the EPP host name mapping in [RFC5732]. 1533 The host object supports both the XML Model and the CSV Model, 1534 defined in Models (Section 2) section. The elements used for both 1535 models are defined in the following sections. Both the 1536 and elements contain one or more 1537 elements with a set of named CSV file definitions using 1538 the "name" attribute. 1540 5.2.1. XML Model 1542 There are two elements used in the data escrow of the host objects 1543 for the XML model including the , under the 1544 element, and the element, under 1545 the element. 1547 A element substitutes for the 1548 abstract element to define a concrete definition of a host. The 1549 element can be replaced by other host 1550 definitions using the XML schema substitution groups feature. 1552 5.2.1.1. element 1554 The RDE host object is based on the EPP host response for an 1555 authorized client (Section 3.1.2. of [RFC5732]). 1557 The OPTIONAL element contains the following child elements: 1559 o A element that contains the fully qualified name of the 1560 host object. 1562 o A element that contains the repository object identifier 1563 assigned to the host object when the object was created. 1565 o One or more elements that describe the status of the host 1566 object. 1568 o Zero or more elements that contain the IP addresses 1569 associated with the host object. 1571 o A element that contains the identifier of the sponsoring 1572 registrar. 1574 o An OPTIONAL element that contains the identifier of the 1575 registrar that created the host object. An OPTIONAL client 1576 attribute is used to specify the client that performed the 1577 operation. 1579 o An OPTIONAL element that contains the date and time of 1580 host-object creation. 1582 o An OPTIONAL element that contains the identifier of the 1583 registrar that last updated the host object. This element MUST 1584 NOT be present if the host object has never been modified. An 1585 OPTIONAL client attribute is used to specify the client that 1586 performed the operation. 1588 o An OPTIONAL element that contains the date and time of 1589 the most recent host-object modification. This element MUST NOT 1590 be present if the host object has never been modified. 1592 o An OPTIONAL element that contains the date and time of 1593 the most recent host object successful transfer. This element 1594 MUST NOT be present if the domain name object has never been 1595 transfered. 1597 Example of object: 1599 ... 1600 1601 ns1.example1.example 1602 Hns1_example_test-TEST 1603 1604 1605 192.0.2.2 1606 192.0.2.29 1607 1080:0:0:0:8:800:200C:417A 1608 RegistrarX 1609 RegistrarX 1610 1999-05-08T12:10:00.0Z 1611 RegistrarX 1612 2009-10-03T09:34:00.0Z 1613 1614 ... 1616 5.2.1.2. object 1618 The element contains the fully qualified domain name 1619 of a host that was deleted. The element also 1620 supports host removal based on roid to support SRS systems in which 1621 different hosts with the same fully qualified domain name are active 1622 at the same time. 1624 Example of object: 1626 ... 1627 1628 ... 1629 1630 ns1.example.example 1631 1632 ... 1633 1634 ... 1636 5.2.2. CSV Model 1638 For the CSV Model of the host object, the child 1639 element of the element is used to hold the new or 1640 updated host objects for the deposit. The child 1641 element of the element is used to hold the deleted or 1642 purged host objects for the deposit. 1644 Differential and Incremental Deposits are based on changes to the 1645 host objects. The updated host object data under the 1646 element is a cascade replace down all of the host 1647 CSV files starting with the parent "host" CSV File Definition 1648 (Section 5.2.2.1.1). The child CSV file definitions include a 1649 field. All the child CSV file 1650 definition data for the host objects in the parent "host" CSV File 1651 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1652 using the data in the child CSV files. The deleted host object data 1653 under the element is a cascade delete starting from 1654 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1656 5.2.2.1. 1658 The is used to hold the new or updated host object 1659 information for the deposit. The is split into 1660 separate CSV file definitions using named elements with 1661 the "name" attribute. The following sections include the supported 1662 host CSV file definitions. 1664 5.2.2.1.1. "host" CSV File Definition 1666 The "host" CSV File Definition defines the fields and CSV file 1667 references used for the host object records. 1669 The following "csvHost" field elements MUST be used in the "host" 1670 element: 1672 Host name field with type="eppcom:labelType" and 1673 isRequired="true". 1675 The following "rdeCsv" fields, defined in section CSV common field 1676 elements (Section 4.6.2.2), MUST be used in the "host" 1677 element: 1679 Repository Object IDentifier (ROID) assigned to the 1680 host object with isRequired="true". 1682 The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the 1683 "host" element: 1685 or A choice of: 1687 Identifier of the sponsoring client with 1688 isRequired="true". 1690 Contains the ID assigned by ICANN with 1691 type="positiveInteger". The attribute "isRequired" MUST equal 1692 "true". 1694 Identifier of the registrar, defined in Section 5.4, 1695 of the client that created the object. 1697 Identifier of the client that created the host 1698 object. 1700 Identifier of the registrar, defined in Section 5.4, 1701 of the client that updated the object. 1703 Identifier of the client that last updated the host 1704 object. 1706 Date and time that the host object was created. 1708 Date and time that the host object was last 1709 updated. 1711 Date and time that the host was last transferred. 1713 Example of a "host" element. 1715 ... 1716 1717 ... 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1734 host-YYYYMMDD.csv 1735 1736 1737 1738 ... 1739 1740 ... 1742 Example of the corresponding host-YYYYMMDD.csv file. The file 1743 contains six host records with four being internal hosts and two 1744 being external hosts. 1746 ns1.domain1.example,Hns1_example_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 ns2.domain1.example,Hns2_domain1_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 ns1.domain2.example,Hns1_domain2_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 1755 ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, 1756 clientY,1999-05-08T12:10:00.0Z,registrarX, 1757 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1758 ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, 1759 clientY,1999-05-08T12:10:00.0Z,registrarX, 1760 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1761 ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, 1762 clientY,1999-05-08T12:10:00.0Z,registrarX, 1763 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1765 5.2.2.1.2. "hostStatuses" CSV File Definition 1767 The "hostStatuses" CSV File Definition defines the fields and CSV 1768 file references used for the host object statuses. 1770 The following "csvHost" fields, defined for the "host" CSV File 1771 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1772 element: 1774 The status of the host with 1775 type="host:statusValueType" and isRequired="true". 1777 The following "rdeCsv" fields, defined in section CSV common field 1778 elements (Section 4.6.2.2), MUST be used in the "hostStatuses" 1779 element: 1781 Host object Registry Object IDentifier (ROID) 1782 assigned to the host object with isRequired="true". 1784 The following "rdeCsv" fields, defined in section CSV common field 1785 elements (Section 4.6.2.2), MAY be used in the "hostStatuses" 1786 element: 1788 Host object status description which is 1789 free form text describing the rationale for the status. The 1790 attribute "isRequired" MUST equal "true". 1792 Language of the field. 1794 Example of a "hostStatuses" element. 1796 ... 1797 1798 ... 1799 1800 1801 1802 1803 1804 1805 1806 1807 1809 hostStatuses-YYYYMMDD.csv 1810 1811 1812 1813 ... 1814 1815 ... 1817 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1818 file contains the statuses for the six host names 1819 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example, 1820 ns2.domain2.example, ns1.example.net and ns2.example.net. 1822 Hns1_domain1_test-TEST,ok,, 1823 Hns2_domain1_test-TEST,ok,, 1824 Hns1_domain2_test-TEST,ok,, 1825 Hns2_domain2_test-TEST,ok,, 1826 Hns1_example_test-TEST,ok,, 1827 Hns2_example_test-TEST,ok,, 1829 5.2.2.1.3. "hostAddresses" CSV File Definition 1831 The "hostAddresses" CSV File Definition defines the fields and CSV 1832 file references used for the host object IP addresses. 1834 The following "csvHost" field elements MUST be used in the 1835 "hostAddresses" element: 1837 IP addresses associated with the host object with 1838 type="host:addrStringType". The attribute "isRequired" MUST equal 1839 "true". 1841 IP addresses version associated with the host 1842 object with type="host:ipType". "host:ipType" has the enumerated 1843 values of "v4" or "v6". The attribute "isRequired" MUST equal 1844 "true". 1846 The following "rdeCsv" fields, defined in section CSV common field 1847 elements (Section 4.6.2.2), MUST be used in the "hostAddresses" 1848 element: 1850 Host object Registry Object IDentifier (ROID) 1851 assigned to the host object with isRequired="true". 1853 Example of a "hostAddresses" element. 1855 ... 1856 1857 ... 1858 1859 1860 1861 1862 1863 1864 1865 1867 hostAddresses-YYYYMMDD.csv 1868 1869 1870 1871 ... 1872 1873 ... 1875 Example of the corresponding hostAddresses-YYYYMMDD.csv file. The 1876 file contains the IP addresses for the host names 1877 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and 1878 ns2.domain2.example. 1880 Hns1_domain1_test-TEST,192.0.2.1,v4 1881 Hns2_domain1_test-TEST,2001:DB8::1,v6 1882 Hns1_domain2_test-TEST,192.0.2.2,v4 1883 Hns2_domain2_test-TEST,2001:DB8::2,v6 1885 5.2.2.2. 1887 The is used to hold the deleted host objects in a 1888 Differential or Incremental Deposit. All the host object data is 1889 deleted as part of a cascade delete. The is split 1890 into separate CSV file definitions using named elements 1891 with the "name" attribute. The following section defines the 1892 supported host deletes CSV file definition. 1894 5.2.2.2.1. "host" Deletes CSV File Definition 1896 The following "rdeCsv" fields, defined in section CSV common field 1897 elements (Section 4.6.2.2), MUST be used in the "host" 1898 element: 1900 Repository Object IDentifier (ROID) assigned to the 1901 host object with isRequired="true". 1903 Example of a "host" element. 1905 ... 1906 1907 ... 1908 1909 1910 1911 1912 1913 1915 host-delete-YYYYMMDD.csv 1916 1917 1918 1919 ... 1920 1921 ... 1923 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1924 host records. 1926 Hns1_domain1_test-TEST 1927 Hns2_domain1_test-TEST 1928 Hns1_domain2_test-TEST 1929 Hns2_domain2_test-TEST 1931 5.3. Contact Object 1933 The contact object is based on the EPP contact name mapping in 1934 [RFC5733]. The contact object supports both the XML Model and the 1935 CSV Model, defined in Models (Section 2) section. The elements used 1936 for both models are defined in the following sections. 1938 5.3.1. XML Model 1940 There are two elements used in the data escrow of the contact objects 1941 for the XML model including the , under the 1942 element, and the element, 1943 under the element. 1945 A element substitutes for the abstract 1946 element to define a concrete definition of a contact. The 1947 element can be replaced by other contact 1948 definitions using the XML schema substitution groups feature. 1950 5.3.1.1. object 1952 The contact object is based on the EPP contact response for an 1953 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1954 including the data from an EPP Query Response, see 1955 Section 3.1.3. of [RFC5733]. 1957 The OPTIONAL element contains the following child elements: 1959 o A element that contains the server-unique identifier of the 1960 contact object 1962 o A element that contains the Repository Object IDentifier 1963 assigned to the contact object when the object was created. 1965 o One or more elements that describe the status of the 1966 contact object. 1968 o One or two elements that contain postal-address 1969 information. Two elements are provided so that address 1970 information can be provided in both internationalized and 1971 localized forms; a "type" attribute is used to identify the two 1972 forms. If an internationalized form (type="int") is provided, 1973 element content MUST be represented in a subset of UTF-8 that can 1974 be represented in the 7-bit US-ASCII character set. If a 1975 localized form (type="loc") is provided, element content MAY be 1976 represented in unrestricted UTF-8. The element 1977 contains the following child elements: 1979 * A element that contains the name of the individual or 1980 role represented by the contact. 1982 * An OPTIONAL element that contains the name of the 1983 organization with which the contact is affiliated. 1985 * An element that contains address information associated 1986 with the contact. An element contains the following 1987 child elements: 1989 + One, two, or three OPTIONAL elements that contain 1990 the contact's street address. 1992 + A element that contains the contact's city. 1994 + An OPTIONAL element that contains the contact's state 1995 or province. 1997 + An OPTIONAL element that contains the contact's postal 1998 code. 2000 + A element that contains the contact's two-letter 2001 country code. 2003 o An OPTIONAL element that contains the contact's voice 2004 telephone number. 2006 o An OPTIONAL element that contains the contact's facsimile 2007 telephone number. 2009 o An element that contains the contact's email address. 2011 o A element that contains the identifier of the sponsoring 2012 registrar. 2014 o An OPTIONAL element that contains the identifier of the 2015 registrar that created the contact object. An OPTIONAL client 2016 attribute is used to specify the client that performed the 2017 operation. 2019 o An OPTIONAL element that contains the date and time of 2020 contact-object creation. 2022 o An OPTIONAL element that contains the identifier of the 2023 registrar that last updated the contact object. This element MUST 2024 NOT be present if the contact has never been modified. An 2025 OPTIONAL client attribute is used to specify the client that 2026 performed the operation. 2028 o An OPTIONAL element that contains the date and time of 2029 the most recent contact-object modification. This element MUST 2030 NOT be present if the contact object has never been modified. 2032 o An OPTIONAL element that contains the date and time of 2033 the most recent contact object successful transfer. This element 2034 MUST NOT be present if the contact object has never been 2035 transferred. 2037 o An OPTIONAL element that contains the following child 2038 elements related to the last transfer request of the contact 2039 object: 2041 * A element that contains the state of the most recent 2042 transfer request. 2044 * A element that contains the identifier of the registrar 2045 that requested the domain name object transfer. An OPTIONAL 2046 client attribute is used to specify the client that performed 2047 the operation. 2049 * An element that contains the identifier of the registrar 2050 that should act upon a PENDING transfer request. For all other 2051 status types, the value identifies the registrar that took the 2052 indicated action. An OPTIONAL client attribute is used to 2053 specify the client that performed the operation. 2055 * A element that contains the date and time that the 2056 transfer was requested. 2058 * An element that contains the date and time of a 2059 required or completed response. For a PENDING request, the 2060 value identifies the date and time by which a response is 2061 required before an automated response action will be taken by 2062 the registry. For all other status types, the value identifies 2063 the date and time when the request was completed. 2065 o An OPTIONAL element that identifies elements that 2066 requiring exceptional server-operator handling to allow or 2067 restrict disclosure to third parties. See Section 2.9 of 2068 [RFC5733] for a description of the child elements contained within 2069 the element. 2071 Example object: 2073 ... 2074 2075 sh8013 2076 Csh8013-TEST 2077 2078 2079 2080 John Doe 2081 Example Inc. 2082 2083 123 Example Dr. 2084 Suite 100 2085 Dulles 2086 VA 2087 20166-6503 2088 US 2089 2090 2091 +1.7035555555 2092 +1.7035555556 2093 jdoe@example.example 2094 RegistrarX 2095 RegistrarX 2096 2009-09-13T08:01:00.0Z 2097 RegistrarX 2098 2009-11-26T09:10:00.0Z 2099 2009-12-03T09:05:00.0Z 2100 2101 pending 2102 clientW 2103 2011-03-08T19:38:00.0Z 2104 RegistrarX 2105 2011-03-13T23:59:59.0Z 2106 2107 2108 2109 2110 2111 2112 ... 2114 5.3.1.2. object 2116 The element contains the id of a contact that was 2117 deleted. 2119 Example of object: 2121 ... 2122 2123 ... 2124 2125 sh8013-TEST 2126 co8013-TEST 2127 2128 ... 2129 2130 ... 2132 5.3.2. CSV Model 2134 For the CSV Model of the contact object, the 2135 child element of the element is used to hold the new 2136 or updated contacts objects for the deposit. The 2137 child element of the element is 2138 used to hold the deleted or purged contact objects for the deposit. 2139 Both the and elements 2140 contain one or more elements with a set of named CSV 2141 file definitions using the "name" attribute. 2143 Differential and Incremental Deposits are based on changes to the 2144 contact objects. The updated contact object data under the 2145 element is a cascade replace down all of the 2146 contact CSV files starting with the parent "contact" CSV File 2147 Definition (Section 5.3.2.1.1). The child CSV file definitions 2148 include a field. All the child CSV 2149 file definition data for the contact objects in the parent "contact" 2150 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2151 then set using the data in the child CSV files. The deleted contact 2152 object data under the element is a cascade 2153 delete starting from the "contact" Deletes CSV File Definition 2154 (Section 5.3.2.2.1). 2156 5.3.2.1. 2158 The is used to hold the new or updated contact 2159 object information for the deposit. The is 2160 split into separate CSV file definitions using named 2161 elements with the "name" attribute. The following sections include 2162 the supported contact CSV file definitions. 2164 5.3.2.1.1. "contact" CSV File Definition 2166 The "contact" CSV File Definition defines the fields and CSV file 2167 references used for the contact object records. 2169 The following "csvContact" field elements MUST be used in the 2170 "contact" element: 2172 Contains the server-unique contact identifier with 2173 type="eppcom:clIDType" and isRequired="true". 2175 Contains the contact's email address with 2176 type="eppcom:minTokenType" and isRequired="true". 2178 The following field elements MAY be used in the "contact" 2179 element: 2181 Contains the contact's voice telephone number 2182 with type="contact:e164StringType". 2184 Contains the contact's voice telephone number 2185 extension with type="token". 2187 Contains the contact's facsimile telephone number 2188 with type="contact:e164StringType". 2190 Contains the contact's facsimile telephone 2191 number extension with type="token". 2193 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 2194 "contact" element: 2196 The Registry Object IDentifier (ROID) for the contact 2197 object with isRequired="true". 2199 or A choice of: 2201 Identifier of the sponsoring client with 2202 isRequired="true". 2204 Contains the ID assigned by ICANN with 2205 type="positiveInteger". The attribute "isRequired" MUST equal 2206 "true". 2208 The following "rdeCsv" fields, defined in section CSV common field 2209 elements (Section 4.6.2.2), MAY be used in the "contact" 2210 element: 2212 Identifier of the registrar, defined in Section 5.4, 2213 of the client that created the object. 2215 Identifier of the client that created the contact 2216 object. 2218 Identifier of the registrar, defined in Section 5.4, 2219 of the client that updated the object. 2221 Identifier of the client that last updated the 2222 contact object. 2224 Created date and time of the contact object. 2226 Date and time of the last update to the contact 2227 object. 2229 Date and time of the last transfer for the contact 2230 object. 2232 Example of a "contact" element. 2234 ... 2235 2236 ... 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2257 contact-YYYYMMDD.csv 2258 2259 2260 2261 ... 2262 2263 ... 2265 Example of the contact-YYYYMMDD.csv file. The file contains nine 2266 object contact records. 2268 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2269 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2270 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2271 2009-11-26T09:10:00.0Z 2272 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2273 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2274 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2275 2009-11-26T09:10:00.0Z 2276 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2277 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2278 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2279 2009-11-26T09:10:00.0Z 2280 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2281 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2282 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2283 2009-11-26T09:10:00.0Z 2284 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2285 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2286 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2287 2009-11-26T09:10:00.0Z 2288 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2289 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2290 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2291 2009-11-26T09:10:00.0Z 2292 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2293 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2294 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2295 2009-11-26T09:10:00.0Z 2296 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2297 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2298 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2299 2009-11-26T09:10:00.0Z 2300 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2301 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2302 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2303 2009-11-26T09:10:00.0Z 2305 5.3.2.1.2. "contactStatuses" CSV File Definition 2307 The "contactStatuses" CSV File Definition defines the fields and CSV 2308 file references used for the contact object statuses. 2310 The following "csvContact" field elements, defined for the "contact" 2311 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2312 "contactStatuses" element: 2314 Server-unique contact identifier of status with 2315 isRequired="true". 2317 The status of the contact with 2318 type="contact:statusValueType" and isRequired="true". 2320 The following "rdeCsv" fields, defined in section CSV common field 2321 elements (Section 4.6.2.2), MAY be used in the "contactStatuses" 2322 element: 2324 The contact object status description 2325 which is free form text describing the rationale for the status. 2327 Language of the field. 2329 Example of a "contactStatuses" 2330 element. 2332 ... 2333 2334 ... 2335 2336 2337 2338 2339 2340 2341 2342 2343 2345 contactStatuses-YYYYMMDD.csv 2346 2347 2348 2349 ... 2350 2351 ... 2353 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2354 file contains the statuses for the nine contact identifiers. 2356 domain1admin,ok,, 2357 domain1tech,ok,, 2358 domain1billing,ok,, 2359 domain2admin,ok,, 2360 domain2tech,ok,, 2361 domain2billing,ok,, 2362 xnabc123admin,ok,, 2363 xnabc123tech,ok,, 2364 xnabc123billing,ok,, 2366 5.3.2.1.3. "contactPostal" CSV File Definition 2368 The "contactPostal" CSV File Definition defines the fields and CSV 2369 file references used for the contact postal info object records. 2371 The following "csvContact" field elements MUST be used in the 2372 "contactPostal" element: 2374 Contains the form of the postal-address 2375 information with type="contact:postalLineType" and 2376 isRequired="true". This field specifies the form ("int" or 2377 "loc"), as defined in Section 4.6.3, of the , 2378 , , , 2379 , , fields. 2381 Contains the contact's name of the individual or 2382 role represented by the contact with type="contact:postalLineType" 2383 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2384 indicate the localized or internationalized form as defined in 2385 section Section 4.6.3. 2387 Contains the contact's street address line with 2388 type="contact:fPostalLineType". An index attribute is required to 2389 indicate which street address line the field represents with index 2390 "0" for the first line and index "2" for the last line. An 2391 OPTIONAL "isLoc" attribute to used to indicate the localized or 2392 internationalized form as defined in section Section 4.6.3. 2394 Contains the contact's city with 2395 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2396 "isLoc" attribute to used to indicate the localized or 2397 internationalized form as defined in section Section 4.6.3. 2399 Contains the contact's country code with 2400 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2401 attribute to used to indicate the localized or internationalized 2402 form as defined in section Section 4.6.3. 2404 The following "csvContact" field elements MAY be used in the 2405 "contactPostal" element: 2407 Contains the name of the organization with which 2408 the contact is affiliated with type="contact:optPostalLineType". 2409 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2410 internationalized form as defined in section Section 4.6.3. 2412 Contains the contact's state or province with 2413 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2414 to used to indicate the localized or internationalized form as 2415 defined in section Section 4.6.3. 2417 Contains the contact's postal code with 2418 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2419 indicate the localized or internationalized form as defined in 2420 section Section 4.6.3. 2422 The following "csvContact" fields, defined for the "contact" CSV File 2423 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2424 element: 2426 Server-unique contact identifier for the contact 2427 object with isRequired="true". 2429 Example of a "contactPostal" 2430 element. 2432 ... 2433 2434 ... 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2452 contactPostal-YYYYMMDD.csv 2453 2454 2455 2456 ... 2457 2458 ... 2460 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2461 nine contact postal records. 2463 domain1admin,int,"John Doe","Example Inc.", 2464 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2465 domain1tech,int,"John Doe","Example Inc.", 2466 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2467 domain1billing,int,"John Doe","Example Inc.", 2468 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2469 domain2admin,int,"John Doe","Example Inc.", 2470 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2471 domain2tech,int,"John Doe","Example Inc.", 2472 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2473 domain2billing,int,"John Doe","Example Inc.", 2474 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2475 xnabc123admin,int,"John Doe","Example Inc.", 2476 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2477 xnabc123tech,int,"John Doe","Example Inc.", 2478 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2479 xnabc123billing,int,"John Doe","Example Inc.", 2480 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2482 5.3.2.1.4. "contactTransfer" CSV File Definition 2484 The "contactTransfer" CSV File Definition defines the fields and CSV 2485 file references used for the contact object pending and completed 2486 transfer records. No additional field elements were added for use in 2487 the "contactTransfer" element. The 2488 following "rdeCsv" fields, defined in section CSV common field 2489 elements (Section 4.6.2.2), MUST be used in the "contactTransfer" 2490 element: 2492 State of the most recent transfer request with 2493 isRequired="true". 2495 Identifier of the registrar, defined in Section 5.4, 2496 of the client that requested the transfer with isRequired="true". 2498 Date and time that the transfer was requested with 2499 isRequired="true". 2501 Identifier of the registrar, defined in Section 5.4, 2502 of the client that should take or took action with 2503 isRequired="true". 2505 Date and time that the transfer action should be 2506 taken or has been taken with isRequired="true". 2508 The following "rdeCsv" fields, defined in section CSV common field 2509 elements (Section 4.6.2.2), MAY be used in the "contactTransfer" 2510 element: 2512 Identifier of the client that requested the transfer. 2514 Identifier of the client that should take or took 2515 action for transfer. 2517 The following "csvContact" fields, defined for the "contact" CSV File 2518 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2519 element: 2521 Server-unique contact identifier for the contact 2522 object with isRequired="true". 2524 Example of a "contactTransfer" 2525 element. 2527 ... 2528 2529 ... 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2544 contactTransfer-YYYYMMDD.csv 2545 2546 2547 2548 ... 2549 2550 ... 2552 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2553 one contact transfer record in pending status. 2555 xnabc123admin,clientApproved,registrarX,clientX, 2556 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2558 5.3.2.1.5. "contactDisclose" CSV File Definition 2560 The "contactDisclose" CSV File Definition defines the fields and CSV 2561 file references used for the contact disclose object records. 2563 The following "csvContact" field elements MAY be used in the 2564 "contactDisclose" element: 2566 Contains flag with a value of "true" or 2567 "1" (one) notes the preference to allow disclosure of the 2568 specified elements as an exception to the stated data-collection 2569 policy. A value of "false" or "0" (zero) notes a client 2570 preference to not allow disclosure of the specified elements as an 2571 exception to the stated data-collection policy with 2572 type="boolean". The additional fields define specific exceptional 2573 disclosure preferences based on the 2574 field. 2576 Exceptional disclosure preference flag 2577 for the localized form of the contact name with type="boolean". 2579 Exceptional disclosure preference flag 2580 for the internationalized form of the contact name with 2581 type="boolean". 2583 Exceptional disclosure preference flag 2584 for the localized form of the contact organization with 2585 type="boolean". 2587 Exceptional disclosure preference flag 2588 for the internationalized form of the contact organization with 2589 type="boolean". 2591 Exceptional disclosure preference flag 2592 for the localized form of the contact address with type="boolean". 2594 Exceptional disclosure preference flag 2595 for the internationalized form of the contact address with 2596 type="boolean". 2598 Exceptional disclosure preference flag 2599 of the contact voice telephone number with type="boolean". 2601 Exceptional disclosure preference flag of 2602 the contact facsimile telephone number with type="boolean". 2604 Exceptional disclosure preference flag 2605 of the contact email address with type="boolean". 2607 The following "csvContact" fields, defined for the "contact" CSV File 2608 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2609 element: 2611 Server-unique contact identifier for the contact 2612 object with isRequired="true". 2614 Example of a "contactDisclose" 2615 element. 2617 ... 2618 2619 ... 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2637 contactDisclose-YYYYMMDD.csv 2638 2639 2640 2641 ... 2642 2643 ... 2645 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2646 one disclosure records, disabling disclosure of voice, fax, and 2647 email. 2649 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2651 5.3.2.2. 2653 The is used to hold the deleted contact objects 2654 in a Differential or Incremental Deposit. All the contact object 2655 data is deleted as part of a cascade delete. The 2656 is split into separate CSV file definitions 2657 using named elements with the "name" attribute. The 2658 following section defines the supported contact deletes CSV file 2659 definition. 2661 5.3.2.2.1. "contact" Deletes CSV File Definition 2663 The following "csvContact" field elements MUST be used in the deletes 2664 "contact" element: 2666 Contains the server-unique contact identifier with 2667 type="eppcom:clIDType" and isRequired="true". 2669 Example of a "contact" element. 2671 ... 2672 2673 ... 2674 2675 2676 2677 2678 2679 2681 contact-delete-YYYYMMDD.csv 2682 2683 2684 2685 ... 2686 2687 ... 2689 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2690 six contact records. 2692 domain1admin 2693 domain1tech 2694 domain1billing 2695 domain2admin 2696 domain2tech 2697 domain2billing 2699 5.4. Registrar Object 2701 The registrar object represents the sponsoring client for other 2702 objects, and is typically referred to as the sponsoring registrar. 2703 The registrar object supports both the XML Model and the CSV Model, 2704 defined in Section 2. The elements used for both models are defined 2705 in the following sections. 2707 5.4.1. XML Model 2709 There are two elements used in the data escrow of the registrar 2710 objects for the XML model including the , 2711 under the element, and the 2712 element, under the element. 2714 A element substitutes for the 2715 abstract element to define a 2716 concrete definition of a registrar. The 2717 element can be replaced by other 2718 domain definitions using the XML schema substitution groups feature. 2720 5.4.1.1. element 2722 The element contains the following child elements: 2724 o An element that contains the Registry-unique identifier of 2725 the registrar object. This has a superordinate relationship 2726 to a subordinate , or of domain, contact and 2727 host objects. 2729 o An element that contains the name of the registrar. 2731 o An OPTIONAL element that contains the ID assigned by 2732 ICANN. 2734 o An OPTIONAL element that contains the operational status 2735 of the registrar. Possible values are: ok, readonly and 2736 terminated. 2738 o One or two OPTIONAL elements that contain postal- 2739 address information. Two elements are provided so that address 2740 information can be provided in both internationalized and 2741 localized forms; a "type" attribute is used to identify the two 2742 forms. If an internationalized form (type="int") is provided, 2743 element content MUST be represented in a subset of UTF-8 that can 2744 be represented in the 7-bit US-ASCII character set. If a 2745 localized form (type="loc") is provided, element content MAY be 2746 represented in unrestricted UTF-8. The element 2747 contains the following child elements: 2749 * A element that contains address information associated 2750 with the registrar. The element contains the following 2751 child elements: 2753 + One, two, or three OPTIONAL elements that contain 2754 the registrar's street address. 2756 + A element that contains the registrar's city. 2758 + An OPTIONAL element that contains the registrar's state 2759 or province. 2761 + An OPTIONAL element that contains the registrar's 2762 postal code. 2764 + A element that contains the registrar's country code. 2766 o An OPTIONAL element that contains the registrar's voice 2767 telephone number. 2769 o An OPTIONAL element that contains the registrar's facsimile 2770 telephone number. 2772 o An OPTIONAL element that contains the registrar's email 2773 address. 2775 o An OPTIONAL element that contains the registrar's URL. 2777 o An OPTIONAL elements that contains whois information. 2778 The element contains the following child elements: 2780 * An OPTIONAL element that contains the name of the 2781 registrar WHOIS server listening on TCP port 43 as specified in 2782 [RFC3912]. 2784 * An OPTIONAL element that contains the name of the 2785 registrar WHOIS server listening on TCP port 80/443. 2787 o An OPTIONAL element that contains the date and time of 2788 registrar-object creation. 2790 o An OPTIONAL element that contains the date and time of 2791 the most recent RDE registrar-object modification. This element 2792 MUST NOT be present if the rdeRegistrar object has never been 2793 modified. 2795 Example of object: 2797 ... 2798 2799 RegistrarX 2800 Registrar X 2801 123 2802 ok 2803 2804 2805 123 Example Dr. 2806 Suite 100 2807 Dulles 2808 VA 2809 20166-6503 2810 US 2811 2812 2813 +1.7035555555 2814 +1.7035555556 2815 jdoe@example.example 2816 http://www.example.example 2817 2818 whois.example.example 2819 http://whois.example.example 2820 2821 2005-04-23T11:49:00.0Z 2822 2009-02-17T17:51:00.0Z 2823 2824 ... 2826 5.4.1.2. object 2828 The element contains the id of a registrar that 2829 was deleted. 2831 Example of object: 2833 ... 2834 2835 ... 2836 2837 agnt0001-TEST 2838 2839 ... 2840 2841 ... 2843 5.4.2. CSV Model 2845 For the CSV Model of the registrar object, the 2846 child element of the element 2847 is used to hold the new or updated registrar objects for the deposit. 2848 The child element of the element 2849 is used to hold the deleted or purged registrar objects for the 2850 deposit. Both the and 2851 elements contain one or more elements with a set of 2852 named CSV file definitions using the "name" attribute. 2854 Differential and Incremental Deposits are based on changes to the 2855 registrar objects. The updated registrar object data under the 2856 element is a cascade replace down all of the 2857 registrar CSV files starting with the parent "registrar" CSV File 2858 Definition (Section 5.4.2.1.1). The child CSV file definitions 2859 include a field. All the child CSV 2860 file definition data for the registrar objects in the parent 2861 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2862 deleted and then set using the data in the child CSV files. The 2863 deleted registrar object data under the 2864 element is a cascade delete starting from the "registrar" Deletes CSV 2865 File Definition (Section 5.4.2.2.1). 2867 5.4.2.1. 2869 The is used to hold the new or updated 2870 registrar object information for the deposit. The 2871 is split into separate CSV file definitions 2872 using named elements with the "name" attribute. The 2873 following sections include the supported contact CSV file 2874 definitions. 2876 5.4.2.1.1. "registrar" CSV File Definition 2878 The "registrar" CSV File Definition defines the fields and CSV file 2879 references used for the registrar object records. 2881 The following "csvRegistrar" field elements MUST be used in the 2882 "registrar" element: 2884 or A choice of: 2886 Contains the server-unique registrar 2887 identifier with type="eppcom:clIDType" and isRequired="true". 2889 Contains the ID assigned by ICANN with 2890 type="positiveInteger". The attribute "isRequired" MUST equal 2891 "true". 2893 Contains the name of the registrar with 2894 type="normalizedString" and isRequired="true". 2896 The following field elements MAY be used in the "registrar" 2897 element: 2899 Contains the status of the registrar with 2900 type="csvRegistrar:statusValueType". 2902 Contains the ID assigned by ICANN with 2903 type="positiveInteger". This field is included in this section in 2904 addition to the section above to support optionally providing the 2905 field when the field is 2906 used. 2908 Contains the Whois URL of the registrar 2909 with type="anyURI". 2911 The following "rdeCsv" fields, defined in section CSV common field 2912 elements (Section 4.6.2.2), MAY be used in the "registrar" 2913 element: 2915 Created date and time of the registrar object. 2917 Date and time of the last update to the registrar 2918 object. 2920 URL for the registrar web home page. 2922 The following "csvContact" fields, defined in section Contact Object 2923 (Section 5.3), MAY be used in the "registrar" 2924 element: 2926 Registrar street address line with an "index" 2927 attribute that represents the order of the street address line 2928 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2929 indicate the localized or internationalized form, as defined in 2930 Section 4.6.3. 2932 Registrar city with an OPTIONAL "isLoc" attribute 2933 that is used to indicate the localized or internationalized form, 2934 as defined in Section 4.6.3. 2936 Registrar country code with an OPTIONAL "isLoc" 2937 attribute that is used to indicate the localized or 2938 internationalized form, as defined in Section 4.6.3. 2940 Registrar email address. The attribute 2941 "isRequired" MUST equal "false". 2943 Registrar state or province with an OPTIONAL 2944 "isLoc" attribute that is used to indicate the localized or 2945 internationalized form, as defined in Section 4.6.3. 2947 Registrar postal code with an OPTIONAL "isLoc" 2948 attribute that is used to indicate the localized or 2949 internationalized form, as defined in Section 4.6.3. 2951 Registrar voice telephone number. 2953 Registrar voice telephone number extension. 2955 Registrar facsimile telephone number. 2957 Registrar facsimile telephone number extension. 2959 Example of a "registrar" 2960 element. 2962 ... 2963 2964 ... 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2991 registrar-YYYYMMDD.csv 2992 2993 2994 2995 ... 2996 2997 ... 2999 Example of the registrar-YYYYMMDD.csv file. The file contains three 3000 registrar records. 3002 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 3003 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3004 +1.7035555556,,jdoe@example.example,http://www.example.example, 3005 http://whois.example.example,2005-04-23T11:49:00.0Z, 3006 2009-02-17T17:51:00.0Z 3007 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 3008 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3009 +1.7035555556,,jdoe@example.example,http://www.example.example, 3010 http://whois.example.example,2005-04-23T11:49:00.0Z, 3011 2009-02-17T17:51:00.0Z 3012 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 3013 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3014 +1.7035555556,,jdoe@example.example,http://www.example.example, 3015 http://whois.example.example,2005-04-23T11:49:00.0Z, 3016 2009-02-17T17:51:00.0Z 3018 5.4.2.2. 3020 The is used to hold the deleted registrar 3021 objects in a Differential or Incremental Deposit. All the registrar 3022 object data is deleted as part of a cascade delete. The 3023 is split into separate CSV file definitions 3024 using named elements with the "name" attribute. The 3025 following section defines the supported registrar deletes CSV file 3026 definition. 3028 5.4.2.2.1. "registrar" Deletes CSV File Definition 3030 The following "csvRegistrar" field elements MUST be used in the 3031 deletes "registrar" element: 3033 or A choice of: 3035 Contains the server-unique registrar 3036 identifier with type="eppcom:clIDType" and isRequired="true". 3038 Contains the ID assigned by ICANN with 3039 type="positiveInteger". The attribute "isRequired" MUST equal 3040 "true". 3042 Example of a "registrar" element. 3044 ... 3045 3046 ... 3047 3048 3049 3050 3051 3052 3054 registrar-delete-YYYYMMDD.csv 3055 3056 3057 3058 ... 3059 3060 ... 3062 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 3063 one registrar record. 3065 registrarZ 3067 5.5. IDN Table Reference Object 3069 The Internationalized Domain Names (IDN) table reference object is a 3070 pseudo-object that is used to provide a short reference to the IDN 3071 Table and Policy used in IDN registrations. The IDN reference object 3072 supports both the XML and the CSV Model, defined in the Models 3073 (Section 2) section. The elements used for both models are defined 3074 in the following sections. 3076 5.5.1. XML Model 3078 There is one element used in the data escrow of the IDN table 3079 reference objects for the XML model that is the , 3080 under the element. 3082 5.5.1.1. object 3084 The contains the following elements. An "id" 3085 attribute is used to specify an identifier for the IDN table. 3087 o An element that contains the URL of the IDN table that is 3088 being referenced. 3090 o A element that contains the URL of the IDN policy 3091 document. If IDN variants are generated algorithmically, the 3092 policy document MUST define the algorithm and the state of the 3093 implicit generated IDN variants. For a list of suggested states 3094 for implicit IDN variants, please see [variantTLDsReport]. 3096 Example of object: 3098 ... 3099 3100 3101 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3102 3103 3104 http://registro.br/dominio/regras.html 3105 3106 3107 ... 3109 5.5.2. CSV Model 3111 The IDN domain names, defined in Section 5.1, MAY have references to 3112 the IDN language identifier using the field 3113 element. The IDN table reference object defines the mapping of a 3114 language identifier to a language table URL. The language table URL 3115 defines the character code points that can be used for the language 3116 identifier. The elements used for the IDN table reference object is 3117 defined in this section. The child element of the 3118 element is used to hold the new or updated IDN table 3119 reference objects for the deposit. The child 3120 element of the element is used to hold the deleted or 3121 purged IDN table reference objects for the deposit. Both the 3122 and elements contain one or more 3123 elements with a set of named CSV file definitions using 3124 the "name" attribute. 3126 5.5.2.1. 3128 The is used to hold the new or updated IDN table 3129 reference object information for the deposit. The 3130 is split into separate CSV file definitions using named 3131 elements with the "name" attribute. The following sections include 3132 the supported IDN table reference CSV file definitions. 3134 5.5.2.1.1. "idnLanguage" CSV File Definition 3136 The "idnLanguage" CSV File Definition defines the fields and CSV file 3137 references used for the IDN table reference object records. 3139 The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be 3140 used in the "idnLanguage" element: 3142 The language identifier that matches the values 3143 for the field element in the "domain" CSV 3144 File Definition (Section 5.1.2.1.1) files. The attribute 3145 "isRequired" MUST equal "true". 3147 URL that defines the character code points that can be 3148 used for the language defined by the field element. 3149 The attribute "isRequired" MUST equal "true". 3151 Example of a "idnLanguage" element. 3153 ... 3154 3155 ... 3156 3157 3158 3159 3160 3161 3162 3164 idnLanguage-YYYYMMDD.csv 3165 3166 3167 3168 ... 3169 3170 ... 3172 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3173 contains two IDN language records. 3175 LANG-1, 3176 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3177 LANG-2, 3178 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3180 5.5.2.2. 3182 The is used to hold the deleted IDN table reference 3183 objects in a Differential or Incremental Deposit. The 3184 is split into separate CSV file definitions using 3185 named elements with the "name" attribute. The following 3186 section defines the supported IDN table reference deletes CSV file 3187 definition. 3189 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3191 The following "idnLanguage" field elements MUST be used in the 3192 deletes "idnLanguage" element: 3194 The language identifier that matches the values 3195 for the field element in the "domain" CSV 3196 File Definition (Section 5.1.2.1.1) files. The attribute 3197 "isRequired" MUST equal "true". 3199 Example of a "idnLanguage" element. 3201 ... 3202 3203 ... 3204 3205 3206 3207 3208 3209 3211 idnLanguage-delete-YYYYMMDD.csv 3212 3213 3214 3215 ... 3216 3217 ... 3219 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3220 contains one IDN language record. 3222 LANG-2 3224 5.6. NNDN Object 3226 An NNDN (NNDN's not domain name) can be used to store registry 3227 reserved names or (blocked, withheld or mirrored) IDN variants. 3229 Domain Name Registries may maintain domain names without their being 3230 persisted as domain objects in the registry system, for example, a 3231 list of reserved names not available for registration. The NNDN is a 3232 lightweight domain-like object that is used to escrow domain names 3233 not maintained as domain name objects. 3235 A domain name can only exist as a domain name object or an NNDN 3236 object, but not both. 3238 The NNDN object supports both the XML and the CSV Model, defined in 3239 the Models (Section 2) section. The elements used for both models 3240 are defined in the following sections. 3242 5.6.1. XML Model 3244 There are two elements used in the data escrow of the NNDN objects 3245 for the XML model including the , under the 3246 element, and the element, under the 3247 element. 3249 A element substitutes for the 3250 abstract element to define a concrete definition of an NNDN. The 3251 element can be replaced by other NNDN 3252 definitions using the XML schema substitution groups feature. 3254 5.6.1.1. object 3256 The element contains the following child elements: 3258 o An element that contains the fully qualified name of the 3259 NNDN. For IDNs the A-Label is used (see [RFC5891], Section 4.4). 3261 o An OPTIONAL element that contains the fully qualified name 3262 of the NNDN in Unicode character set. It MUST be provided if 3263 available. 3265 o An OPTIONAL element that references the IDN 3266 Table used for the NNDN. This corresponds to the "id" attribute 3267 of the element. This element MUST be present if the 3268 NNDN is an IDN. 3270 o An OPTIONAL element is used to indicate that the 3271 NNDN is used for an IDN variant. This element contains the domain 3272 name used to generate the IDN variant. 3274 o A element that indicates the state of the NNDN: 3275 blocked, withheld or mirrored. 3277 * If an NNDN is considered undesirable for registration (i.e., 3278 unavailable for allocation to anyone), then the NNDN will be 3279 tagged as "blocked". 3281 * If an NNDN is considered a potential registration of a domain 3282 object for a registrant, then the NNDN will be tagged as 3283 "withheld". This status is only used when the NNDN is used for 3284 an IDN variant. 3286 * If an NNDN is considered a mirrored IDN variant of a domain 3287 object, then the NNDN will be tagged as "mirrored". A 3288 mirroringNS attribute is used to specify if the mirrored IDN 3289 variant use the NS mirror mechanism. The default value of 3290 mirroringNS is true. If another mechanism such as DNAME is 3291 used, the value of mirroringNS attribute MUST be false. 3293 o An OPTIONAL element that contains the date and time of 3294 the NNDN object creation. 3296 Example of an object: 3298 ... 3299 3300 xn--exampl-gva.example 3301 pt-BR 3302 example.example 3303 withheld 3304 2005-04-23T11:49:00.0Z 3305 3306 ... 3308 5.6.1.2. object 3310 The element contains the NNDN that was deleted, 3311 i.e., the . 3313 Example of an object: 3315 ... 3316 3317 ... 3318 3319 xn--pingino-q2a.example 3320 3321 ... 3322 3323 ... 3325 5.6.2. CSV Model 3327 For the CSV Model of the NNDN object, the child 3328 element of the element is used to hold the new or 3329 updated NNDN objects for the deposit. The child 3330 element of the element is used to hold the deleted or 3331 purged NNDN objects for the deposit. Both the and 3332 elements contain one or more elements 3333 with a set of named CSV file definitions using the 3334 "name" attribute. 3336 5.6.2.1. 3338 The is used to hold the new or updated NNDN object 3339 information for the deposit. The is split into 3340 separate CSV file definitions using named elements with 3341 the "name" attribute. The following sections include the supported 3342 NNDN CSV file definitions. 3344 5.6.2.1.1. "NNDN" CSV File Definition 3346 The "NNDN" CSV File Definition defines the fields and CSV file 3347 references used for the NNDN object records. 3349 The following "csvNNDN" field elements MUST be used in the "NNDN" 3350 element: 3352 Fully qualified name of the NNDN with 3353 type="eppcom:labelType" and isRequired="true". For IDNs the 3354 A-Label is used (see [RFC5891], Section 4.4). 3356 State of the NNDN: blocked or withheld with 3357 type="rdeNNDN:nameState" and isRequired="true". See 3358 Section 5.6.1.1 for a description of the possible values for the 3359 element. 3361 The following field elements MAY be used in the "NNDN" 3362 element: 3364 Domain name used to generate the IDN variant 3365 with type="eppcom:labelType". 3367 Defines whether the "mirroring" 3368 uses the NS mirror mechanism, as described 3369 for the "mirroringNS" attribute in 3370 Section 5.6.1.1, with type="boolean". If the field element is not 3371 defined the default value is "true". 3373 The following "rdeCsv" fields, defined in section CSV common field 3374 elements (Section 4.6.2.2), MAY be used in the "NNDN" 3375 element: 3377 Created date and time of the NNDN object. 3379 Name of the NNDN in Unicode character set for the 3380 field element. 3382 IDN Table Identifier for the NNDN that matches 3383 an IDN Table Reference Object record, as defined in Section 5.5.2. 3385 Example of an "NNDN" element: 3387 ... 3388 3389 ... 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3402 NNDN-YYYYMMDD.csv 3403 3404 3405 3406 ... 3407 3408 ... 3410 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3411 contains two NNDN records for an IDN with one blocked variant and one 3412 mirrored variant. 3414 xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example, 3415 blocked,,2005-04-23T11:49:00.0Z 3416 xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example, 3417 mirrored,1,2005-04-23T11:49:00.0Z 3419 5.6.2.2. 3421 The is used to hold the deleted NNDN objects in a 3422 Differential or Incremental Deposit. The is split 3423 into separate CSV file definitions using named elements 3424 with the "name" attribute. The following section defines the 3425 supported NNDN deletes CSV file definition. 3427 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3429 The following "NNDN" field elements MUST be used in the deletes 3430 "NNDN" element: 3432 Fully qualified name of the NNDN with 3433 type="eppcom:labelType" and isRequired="true". 3435 Example of an "NNDN" element. 3437 ... 3438 3439 ... 3440 3441 3442 3443 3444 3445 3447 NNDN-delete-YYYYMMDD.csv 3448 3449 3450 3451 ... 3452 3453 ... 3455 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3456 contains one NNDN records. 3458 xn--bc456-3ve.example 3460 5.7. EPP Parameters Object 3462 The EPP Parameters Object is a pseudo-object that defines the set of 3463 object and object extension services supported by the registry, as 3464 defined in [RFC5730]. The EPP Parameters Object is only defined as 3465 XML but could be used in the XML model or CSV model. The EPP 3466 Parameters Object is defined using the 3467 element. The EPP Parameters Object SHOULD be included if the 3468 registry supports EPP. Only one EPP Parameters Object MUST exist at 3469 a certain point in time (watermark). 3471 The syntax and content of the children 3472 elements is as explained in section 2.4 of [RFC5730]. The children 3473 of the are as follows: 3475 o One or more elements that indicate the EPP versions 3476 supported by the registry. 3478 o One or more elements that indicate the identifiers of the 3479 text response languages supported by the registry's EPP server. 3481 o One or more elements that contain namespace URIs 3482 representing the objects that the registry's EPP server is capable 3483 of managing. 3485 o An OPTIONAL element that contains one or more 3486 elements that contain namespace URIs representing object 3487 extensions supported by the registry's EPP server. 3489 o A element that contains child elements used to describe the 3490 server's privacy policy for data collection and management. See 3491 section 2.4 of [RFC5730] for more details. 3493 Example of element object: 3495 ... 3496 3497 1.0 3498 en 3499 urn:ietf:params:xml:ns:domain-1.0 3500 3501 urn:ietf:params:xml:ns:contact-1.0 3502 3503 urn:ietf:params:xml:ns:host-1.0 3504 3505 3506 urn:ietf:params:xml:ns:rgp-1.0 3507 urn:ietf:params:xml:ns:secDNS-1.1 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 ... 3528 5.8. Policy Object 3530 The Policy object is a pseudo-object that is used to specify which 3531 OPTIONAL elements from the XML Model are REQUIRED based on the 3532 business model of the registry. For the CSV Model, the OPTIONAL 3533 "isRequired" attribute of the elements, defined in 3534 Section 4.6.2.1, is used to specify which OPTIONAL fields are 3535 REQUIRED based on the business model of the registry. 3537 5.8.1. object 3539 The OPTIONAL contains the following attributes: 3541 o An that defines that the referenced is 3542 REQUIRED. 3544 o that defines the XPath of the element referenced by 3545 . 3547 Example of object: 3549 ... 3550 3552 ... 3554 5.9. Header Object 3556 The Header Object is a pseudo-object that is used to specify the 3557 number of objects in the repository at a specific point in time 3558 (watermark) regardless of the type of deposit: Differential, Full or 3559 Incremental Deposit. The Header Object may also be used to provide 3560 additional information on the contents of the deposit. The Header 3561 Object is only defined as XML but one header object MUST always be 3562 present per escrow deposit regardless of using XML Model or CSV 3563 Model. The Header Object is defined using the 3564 element. 3566 5.9.1. object 3568 The contains the following elements: 3570 o A choice of one of the elements defined in the 3571 "repositoryTypeGroup" group element that indicates the unique 3572 identifier for the repository being escrowed. Possible elements 3573 are: 3575 * A element that defines TLD or the REGISTRY- 3576 CLASS DOMAIN NAME (RCDN) being escrowed in the case of a 3577 Registry data escrow deposit. For IDNs the A-Label is used 3578 (see [RFC5891], Section 4.4). 3580 * A element that defines the Registrar ID 3581 corresponding to a Registrar data escrow deposit. In the case 3582 of an ICANN-accredited Registrar, the 3583 element MUST be the IANA Registrar ID assigned by ICANN. 3585 * A element that defines the provider ID 3586 corresponding to a Privacy and Proxy Services Provider data 3587 escrow deposit. In the case of an ICANN-accredited Privacy and 3588 Proxy Services Provider, the element MUST be 3589 the unique ID assigned by ICANN. 3591 * A element that defines the provider ID 3592 corresponding to a Reseller data escrow deposit. 3594 o A element that contains the number of objects in the SRS 3595 at a specific point in time (watermark) regardless of the type of 3596 deposit: Differential, Full or Incremental. The element 3597 supports the following attributes: 3599 * A "uri" attribute reflects the XML namespace URI of the primary 3600 objects for the XML Model and CSV Model. For example, the 3601 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3602 domain name objects using the XML Model, and the "uri" is set 3603 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3604 objects using the CSV Model. 3606 * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS 3607 DOMAIN NAME (RCDN) of the objects included in the 3608 element. For IDNs the A-Label is used [RFC5891], Section 4.4. 3609 If the "rcdn" attribute is present, the value of the 3610 element must include only objects related to registrations in 3611 the same and lower levels. For example in a data escrow 3612 deposit for the .EXAMPLE TLD, a value of "example" in the 3613 "rcdn" attribute within the element indicates the 3614 number of objects in the TLD including objects in other RCDNs 3615 within the TLD, whereas a value of "com.example" indicates the 3616 number of elements for objects under "com.example" and lower 3617 levels. Omitting the "rcdn" attribute indicates that the total 3618 includes all objects of the specified "uri" in the repository 3619 (e.g. the TLD, Registrar, or PPSP). 3621 * An OPTIONAL "registrarId" attribute indicates the identifier of 3622 the sponsoring Registrar of the objects included in the 3623 element. In the case of an ICANN-accredited Registrar, the 3624 value MUST be the IANA Registrar ID assigned by ICANN. 3626 o An OPTIONAL element that contains a tag that defines 3627 the expected content in the deposit. The producer and consumer of 3628 the deposits will coordinate the set of possible 3629 element values. 3631 Example of object referencing only the XML Model 3632 objects: 3634 ... 3635 3636 test 3637 2 3639 1 3641 1 3643 1 3645 3646 1 3648 1 3650 1 3652 3653 3654 ... 3656 Example of object referencing the CSV and XML 3657 Model objects: 3659 ... 3660 3661 test 3662 2 3664 1 3666 1 3668 1 3670 3671 1 3673 1 3675 1 3677 3678 3679 ... 3681 5.10. DNRD Common Objects Collection 3683 The DNRD Common Objects Collection contains data structures 3684 referenced by two or more of the main objects in the XML model. 3686 6. RDE IDN Variants handling 3688 Depending on the Registration Policy of the Registry, for a domain 3689 name there may be multiple variant names. See [variantTLDsReport] 3690 for further detail on IDN variants. 3692 A registry could choose to escrow IDN variants as domains or NNDN 3693 objects. A specific IDN variant can be represented in the escrow 3694 deposit, as a domain or as an NNDN object, but not both. 3696 If using domain objects to represent IDN variants, the normal 3697 behavior during restoration of an SRS based on an escrow deposit is 3698 to restore the IDN variants as a mirrored variant. If the 3699 registration data of the IDN variant is different from the original 3700 name, the details of this specific implementation MUST be described 3701 in the IDN policy document. 3703 An NNDN or a domain name are explicit representations of an IDN 3704 variant while an IDN variant computed based on an algorithm is an 3705 implicit representation. Explicit representation of an IDN variant 3706 takes precedence over an implicit representation. 3708 7. Profile 3710 Different business models of registries exist, therefore the registry 3711 is responsible for defining a profile that matches its particular 3712 business model. The profile mechanism allows a registry to extend 3713 this specification. 3715 A profile is the process of: 3717 1. Extending base objects with the mechanisms defined for XML and 3718 CSV models. 3720 * In the case of the XML model, abstract elements could be use 3721 to extend the following objects: , , , 3722 and using XML schema substitution groups 3723 feature. 3725 2. Defining a object to specify which OPTIONAL elements of 3726 this base specification is required based on the business model 3727 of the registry. An example is the element that is 3728 usually REQUIRED but it is specified as OPTIONAL in this 3729 specification to support some existing business models. 3731 3. Adding new escrowed objects using the and 3732 elements. 3734 4. Providing the XML schemas to third parties that require them to 3735 validate the escrow deposits. 3737 8. Data escrow agent extended verification process 3739 A Data Escrow Agent SHOULD perform an extended verification process 3740 that starts by creating a dataset to be tested. 3742 o If a Full Deposit is to be tested, the Full Deposit is the 3743 dataset. 3745 o If an Incremental Deposit is to be tested, the dataset is created 3746 by using the Incremental Deposit plus the last previous Full 3747 Deposit. 3749 o If a Differential Deposit is to be tested, the dataset is created 3750 by using the Differential Deposit plus all the required deposits 3751 leading to the last previous Full Deposit. 3753 The following are the minimum suggested tests on the dataset: 3755 o Validate the escrow deposits using the definition agreed with the 3756 registry. 3758 * In the case of the XML model, the contents of the escrow 3759 deposits MUST be validated using the XML schemas of the 3760 profile. 3762 o Count the objects and validate that the number of objects is equal 3763 to the number objects reported in the
element of the 3764 escrow deposit of that point in time (watermark). 3766 o All contact objects linked to domain names MUST be present. 3768 o All registrars objects linked to other objects MUST be present. 3770 o No domain name exists as both a domain name and an NNDN. 3772 o The elements listed as required in the element MUST be 3773 present. 3775 o All idnTableRef definitions linked from other objects MUST be 3776 present. 3778 o If an EPP Parameters Object was escrowed in the past, one and only 3779 one EPP Parameters Object MUST be present. 3781 o The watermark is not in the future. 3783 9. Formal Syntax 3785 This standard is specified in XML Schema notation. The formal syntax 3786 presented here is a complete schema representation suitable for 3787 automated validation. 3789 The BEGIN and END tags are not part of the schema; they are used to 3790 note the beginning and ending of the schema for URI registration 3791 purposes. 3793 9.1. RDE CSV Schema 3795 BEGIN 3796 3798 3805 3808 3809 3811 3812 3813 Registry Data Escrow Comma-Seperated Values (CSV) 3814 3815 3817 3818 3820 3821 3822 3823 3824 3825 3826 3827 3828 3830 3831 3832 3833 3834 3835 3836 3838 3839 3842 3843 3844 3846 3847 3848 3849 3850 3851 3853 3855 3856 3857 3859 3860 3861 3862 3863 3864 3866 3868 3869 3870 3872 3874 3875 3877 3878 3879 3880 3881 3883 3884 3885 3886 3887 3888 3889 3890 3892 3893 3894 3896 3897 3899 3900 3901 3902 3903 3905 3906 3907 3909 3910 3912 3913 3914 3915 3916 3918 3919 3920 3922 3923 3927 3928 3929 3931 3933 3935 3936 3938 3940 3942 3943 3945 3947 3949 3951 3953 3955 3957 3959 3961 3962 3963 3964 3965 3967 3968 3969 3970 3971 3972 3973 3974 3976 3977 3978 3980 3981 3984 3986 3988 3989 3991 3992 3994 3996 3997 3998 3999 4000 4002 4003 4004 4005 4006 4007 4008 4009 4011 4012 4013 4015 4016 4017 4018 4019 4020 4022 4023 4024 4025 4026 4027 4028 4029 4032 4033 4034 4036 4037 4038 4039 4040 4041 4043 4044 4045 4046 4047 4048 4049 4050 4052 4053 4054 4056 4057 4058 4059 4060 4061 4063 4064 4065 4066 4067 4068 4069 4070 4072 4073 4074 4076 4077 4078 4079 4080 4081 4083 4084 4085 4086 4087 4088 4089 4090 4092 4093 4094 4096 4097 4099 4100 4101 4102 4103 4105 4106 4107 4109 4110 4113 4114 4116 4117 4118 4119 4120 4122 4123 4124 4125 4126 4127 4128 4129 4130 4132 4133 4134 4136 4137 4138 4139 4140 4141 4143 4144 4145 4147 4148 4149 4150 4151 4152 4154 4155 4156 4158 4159 4161 4162 4163 4164 4165 4166 4168 4169 4170 4172 4173 4174 4175 4176 4177 4179 4180 4181 4182 4184 4185 4187 4188 4189 4190 4191 4192 4194 4195 4196 4197 4199 4200 4202 4203 4204 4205 4206 4208 4209 4210 4212 4215 4216 END 4218 9.2. RDE Domain Object 4220 BEGIN 4221 4222 4234 4235 4236 4237 4238 4239 4240 4242 4243 4244 Registry Data Escrow Domain provisioning schema 4245 4246 4248 4251 4253 4257 4258 4259 4260 4261 4262 4264 4266 4268 4270 4272 4274 4277 4279 4282 4284 4286 4288 4290 4292 4294 4296 4298 4300 4303 4304 4305 4306 4308 4309 4310 4312 4314 4316 4318 4320 4322 4323 4325 4326 4327 4328 4329 4330 4333 4334 4335 4336 4337 4338 END 4340 9.3. CSV Domain Object 4342 BEGIN 4343 4345 4356 4359 4360 4361 4362 4363 4364 4366 4367 4368 Domain Name Comma-Separated Values (CSV) Object 4369 4370 4372 4375 4378 4379 4380 4381 4382 4383 4384 4385 4386 4388 4391 4394 4395 4396 4397 4398 4399 4400 4401 4402 4404 4405 4408 4409 4412 4413 4414 4415 4416 4418 4419 4420 4422 4423 4426 4427 4428 4429 4430 4432 4433 4434 4436 4438 4439 4441 4442 4443 4444 4445 4447 4448 4449 4451 4452 4455 4456 4459 4460 4463 4464 4467 4468 4471 4472 4475 4476 4479 4480 4482 4483 4484 4485 4486 4488 4489 4490 4492 4493 4496 4497 4501 4502 4505 4506 4507 4508 4509 4510 4512 4513 4514 4516 4519 4520 END 4522 9.4. RDE Host Object 4524 BEGIN 4525 4526 4535 4536 4537 4538 4540 4541 4542 Registry Data Escrow Host provisioning schema 4543 4544 4546 4548 4549 4552 4553 4554 4555 4556 4557 4559 4561 4563 4566 4568 4570 4572 4574 4576 4578 4579 4580 4581 4583 4584 4585 4586 4587 4588 4590 4592 4593 4594 4595 4596 4597 END 4599 9.5. CSV Host Object 4601 BEGIN 4602 4604 4613 4616 4617 4618 4619 4621 4622 4623 Host Comma-Separated Values (CSV) Object 4624 4625 4627 4630 4633 4634 4635 4636 4637 4638 4639 4640 4641 4643 4646 4649 4650 4651 4652 4653 4654 4655 4656 4657 4659 4660 4663 4664 4666 4667 4668 4669 4670 4672 4673 4674 4676 4677 4679 4680 4681 4682 4683 4685 4686 4687 4689 4690 4693 4694 4695 4696 4697 4698 4700 4701 4702 4704 4707 4708 END 4710 9.6. RDE Contact Object 4712 BEGIN 4713 4714 4723 4724 4725 4726 4727 4729 4730 4731 Registry Data Escrow contact provisioning schema 4732 4733 4735 4738 4740 4744 4745 4746 4747 4748 4749 4751 4753 4755 4757 4759 4761 4763 4765 4767 4769 4771 4773 4775 4777 4779 4780 4781 4782 4784 4785 4786 4787 4788 4789 4790 4791 4792 4794 4795 4796 4797 4798 4799 4802 4803 4804 4805 4806 4807 END 4809 9.7. CSV Contact Object 4811 BEGIN 4812 4814 4823 4826 4827 4828 4829 4831 4832 4833 Contact Comma-Separated Values (CSV) Object 4834 4835 4836 4839 4842 4843 4844 4845 4846 4847 4848 4849 4850 4852 4855 4858 4859 4860 4861 4862 4863 4864 4865 4866 4868 4869 4871 4872 4873 4874 4875 4877 4878 4879 4881 4882 4886 4887 4889 4891 4892 4893 4894 4895 4897 4898 4899 4901 4902 4904 4907 4908 4910 4911 4912 4913 4914 4916 4917 4918 4920 4924 4926 4927 4928 4929 4930 4932 4933 4934 4936 4937 4938 4939 4940 4941 4943 4944 4945 4946 4948 4949 4950 4951 4952 4953 4955 4956 4957 4958 4960 4961 4964 4965 4968 4969 4970 4972 4973 4974 4975 4976 4978 4979 4980 4982 4983 4986 4987 4990 4991 4993 4994 4995 4996 4997 4999 5000 5001 5002 5004 5005 5007 5008 5009 5010 5011 5013 5014 5015 5016 5018 5019 5022 5024 5026 5028 5030 5032 5034 5036 5038 5040 5042 5044 5046 5048 5050 5052 5054 5056 5058 5060 5061 5062 5063 5064 5066 5067 5068 5069 5070 5073 5074 5075 5076 5077 5078 5080 5081 5082 5084 5087 5088 END 5090 9.8. RDE Registrar Object 5092 BEGIN 5093 5094 5103 5104 5105 5106 5107 5109 5110 5111 Registry Data Escrow registrar provisioning schema 5112 5113 5115 5118 5120 5123 5124 5125 5126 5127 5128 5130 5132 5134 5136 5139 5141 5143 5145 5147 5149 5151 5153 5154 5155 5156 5158 5159 5160 5161 5162 5163 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 5212 5213 5214 5215 5216 5218 5219 5220 5221 5222 5224 5225 5226 5227 5228 5230 5231 5232 5234 5236 5237 5239 5240 5241 5242 5243 5244 5247 5248 5249 5250 5251 5252 END 5254 9.9. CSV Registrar Object 5256 BEGIN 5257 5259 5269 5272 5273 5274 5275 5276 5278 5279 5280 Registar Comma-Separated Values (CSV) Object 5281 5282 5284 5287 5290 5291 5292 5293 5294 5295 5296 5297 5298 5300 5303 5306 5307 5308 5309 5310 5311 5312 5313 5314 5316 5317 5320 5321 5324 5325 5326 5327 5328 5329 5331 5332 5333 5334 5336 5337 5341 5342 5344 5346 5347 5348 5349 5350 5352 5353 5355 5357 5358 5359 5360 5361 5362 5363 5364 5366 5367 5368 5369 5370 5371 5372 5373 5375 5376 5380 5383 5384 END 5386 9.10. RDE IDN Table Reference Objects 5388 BEGIN 5389 5390 5396 5398 5399 5400 Registry Data Escrow IDN provisioning schema 5401 5403 5405 5407 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5423 5424 5425 5426 5427 5428 5429 5430 5431 5433 5434 5435 5436 5437 5438 5439 5441 5442 END 5444 9.11. CSV IDN Language Object 5446 BEGIN 5447 5449 5456 5459 5460 5462 5463 5464 IDN Language Comma-Separated Values (CSV) Object 5465 5466 5468 5471 5474 5475 5476 5477 5478 5479 5480 5481 5482 5484 5487 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5502 5503 END 5505 9.12. EPP Parameters Object 5507 BEGIN 5508 5509 5517 5518 5519 5521 5522 5523 Registry Data Escrow EPP Parameters schema 5524 5525 5527 5528 5531 5532 5535 5536 5537 5538 5539 5541 5543 5545 5548 5550 5551 5552 5553 5554 5555 END 5557 9.13. NNDN Object 5559 BEGIN 5560 5561 5569 5570 5571 5573 5574 5575 Registry Data Escrow NNDN provisioning schema 5576 5577 5579 5581 5582 5585 5586 5587 5588 5589 5590 5592 5594 5596 5598 5600 5602 5603 5604 5605 5607 5608 5609 5610 5611 5612 5613 5615 5616 5617 5618 5620 5621 5622 5624 5625 5626 5627 5628 5629 5632 5633 5634 5635 5636 5637 END 5639 9.14. CSV NNDN Object 5641 BEGIN 5642 5644 5652 5655 5656 5657 5659 5660 5661 NNDN (NNDN's not domain name) (CSV) Object 5662 5663 5665 5668 5671 5672 5673 5674 5675 5676 5677 5678 5679 5681 5684 5686 5687 5688 5689 5690 5691 5692 5693 5694 5696 5697 5700 5701 5704 5705 5709 5710 5713 5714 5715 5716 5717 5719 5720 5721 5723 5724 5728 5731 5732 END 5734 9.15. Policy Object 5736 BEGIN 5737 5738 5744 5745 5746 Registry Data Escrow Policy schema 5747 5748 5750 5751 5754 5755 5756 5757 5758 5759 5760 5761 5762 5763 END 5765 9.16. Header Object 5767 BEGIN 5768 5769 5776 5777 5779 5780 5781 Data Escrow Deposit Header schema 5783 5784 5786 5787 5790 5791 5792 5793 5794 5795 5796 5798 5800 5801 5802 5803 5805 5806 5807 5808 5809 5810 5811 5812 5814 5815 5816 5817 5818 5819 5820 5821 5822 5824 5825 END 5827 9.17. DNRD Common Objects 5829 BEGIN 5830 5831 5837 5839 5840 5841 Data Escrow Deposit Common Objects schema 5842 5843 5845 5846 5847 5848 5849 5850 5851 5853 5854 END 5856 10. Internationalization Considerations 5858 Data Escrow deposits are represented in XML, which provides native 5859 support for encoding information using the Unicode character set and 5860 its more compact representations including UTF-8. Conformant XML 5861 processors recognize both UTF-8 and UTF-16. Though XML includes 5862 provisions to identify and use other character encodings through use 5863 of an "encoding" attribute in an declaration, use of UTF-8 is 5864 RECOMMENDED. 5866 11. IANA Considerations 5868 This document uses URNs to describe XML namespaces and XML schemas 5869 conforming to a registry mechanism described in [RFC3688]. Fourteen 5870 URI assignments have been registered by the IANA. 5872 Registration request for the RDE CSV namespace: 5874 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 5875 Registrant Contact: IESG 5877 Note to RFC Editor: Please remove the email address from the RFC 5878 after IANA records it. 5880 XML: None. Namespace URIs do not represent an XML specification. 5882 Registration request for the RDE CSV XML schema: 5884 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 5886 Registrant Contact: IESG 5888 Note to RFC Editor: Please remove the email address from the RFC 5889 after IANA records it. 5891 See section Section 9.1 of this document. 5893 Registration request for the RDE domain namespace: 5895 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 5897 Registrant Contact: IESG 5899 Note to RFC Editor: Please remove the email address from the RFC 5900 after IANA records it. 5902 XML: None. Namespace URIs do not represent an XML specification. 5904 Registration request for the RDE domain XML schema: 5906 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 5908 Registrant Contact: IESG 5910 Note to RFC Editor: Please remove the email address from the RFC 5911 after IANA records it. 5913 See section Section 9.2 of this document. 5915 Registration request for the CSV domain namespace: 5917 URI: urn:ietf:params:xml:ns:csvDomain-1.0 5919 Registrant Contact: IESG 5921 Note to RFC Editor: Please remove the email address from the RFC 5922 after IANA records it. 5924 XML: None. Namespace URIs do not represent an XML specification. 5926 Registration request for the CSV domain XML schema: 5928 URI: urn:ietf:params:xml:schema:csvDomain-1.0 5930 Registrant Contact: IESG 5932 Note to RFC Editor: Please remove the email address from the RFC 5933 after IANA records it. 5935 See section Section 9.3 of this document. 5937 Registration request for the RDE host namespace: 5939 URI: urn:ietf:params:xml:ns:rdeHost-1.0 5941 Registrant Contact: IESG 5943 Note to RFC Editor: Please remove the email address from the RFC 5944 after IANA records it. 5946 XML: None. Namespace URIs do not represent an XML specification. 5948 Registration request for the RDE host XML schema: 5950 URI: urn:ietf:params:xml:schema:rdeHost-1.0 5952 Registrant Contact: IESG 5954 Note to RFC Editor: Please remove the email address from the RFC 5955 after IANA records it. 5957 See section Section 9.4 of this document. 5959 Registration request for the CSV host namespace: 5961 URI: urn:ietf:params:xml:ns:csvHost-1.0 5963 Registrant Contact: IESG 5965 Note to RFC Editor: Please remove the email address from the RFC 5966 after IANA records it. 5968 XML: None. Namespace URIs do not represent an XML specification. 5970 Registration request for the CSV host XML schema: 5972 URI: urn:ietf:params:xml:schema:csvHost-1.0 5974 Registrant Contact: IESG 5976 Note to RFC Editor: Please remove the email address from the RFC 5977 after IANA records it. 5979 See section Section 9.5 of this document. 5981 Registration request for the RDE contact namespace: 5983 URI: urn:ietf:params:xml:ns:rdeContact-1.0 5985 Registrant Contact: IESG 5987 Note to RFC Editor: Please remove the email address from the RFC 5988 after IANA records it. 5990 XML: None. Namespace URIs do not represent an XML specification. 5992 Registration request for the RDE contact XML schema: 5994 URI: urn:ietf:params:xml:schema:rdeContact-1.0 5996 Registrant Contact: IESG 5998 Note to RFC Editor: Please remove the email address from the RFC 5999 after IANA records it. 6001 See section Section 9.6 of this document. 6003 Registration request for the CSV contact namespace: 6005 URI: urn:ietf:params:xml:ns:csvContact-1.0 6007 Registrant Contact: IESG 6009 Note to RFC Editor: Please remove the email address from the RFC 6010 after IANA records it. 6012 XML: None. Namespace URIs do not represent an XML specification. 6014 Registration request for the CSV contact XML schema: 6016 URI: urn:ietf:params:xml:schema:csvContact-1.0 6018 Registrant Contact: IESG 6019 Note to RFC Editor: Please remove the email address from the RFC 6020 after IANA records it. 6022 See section Section 9.7 of this document. 6024 Registration request for the RDE registrar namespace: 6026 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6028 Registrant Contact: IESG 6030 Note to RFC Editor: Please remove the email address from the RFC 6031 after IANA records it. 6033 XML: None. Namespace URIs do not represent an XML specification. 6035 Registration request for the RDE registrar XML schema: 6037 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6039 Registrant Contact: IESG 6041 Note to RFC Editor: Please remove the email address from the RFC 6042 after IANA records it. 6044 See section Section 9.8 of this document. 6046 Registration request for the CSV registrar namespace: 6048 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6050 Registrant Contact: IESG 6052 Note to RFC Editor: Please remove the email address from the RFC 6053 after IANA records it. 6055 XML: None. Namespace URIs do not represent an XML specification. 6057 Registration request for the CSV registrar XML schema: 6059 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6061 Registrant Contact: IESG 6063 Note to RFC Editor: Please remove the email address from the RFC 6064 after IANA records it. 6066 See section Section 9.9 of this document. 6068 Registration request for the RDE IDN namespace: 6070 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6072 Registrant Contact: IESG 6074 Note to RFC Editor: Please remove the email address from the RFC 6075 after IANA records it. 6077 XML: None. Namespace URIs do not represent an XML specification. 6079 Registration request for the RDE IDN XML schema: 6081 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6083 Registrant Contact: IESG 6085 Note to RFC Editor: Please remove the email address from the RFC 6086 after IANA records it. 6088 See section Section 9.10 of this document. 6090 Registration request for the CSV IDN namespace: 6092 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6094 Registrant Contact: IESG 6096 Note to RFC Editor: Please remove the email address from the RFC 6097 after IANA records it. 6099 XML: None. Namespace URIs do not represent an XML specification. 6101 Registration request for the CSV IDN XML schema: 6103 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6105 Registrant Contact: IESG 6107 Note to RFC Editor: Please remove the email address from the RFC 6108 after IANA records it. 6110 See section Section 9.11 of this document. 6112 Registration request for the RDE EPP parameters namespace: 6114 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6115 Registrant Contact: IESG 6117 Note to RFC Editor: Please remove the email address from the RFC 6118 after IANA records it. 6120 XML: None. Namespace URIs do not represent an XML specification. 6122 Registration request for the RDE EPP parameters XML schema: 6124 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6126 Registrant Contact: IESG 6128 Note to RFC Editor: Please remove the email address from the RFC 6129 after IANA records it. 6131 See section Section 9.12 of this document. 6133 Registration request for the RDE NNDN namespace: 6135 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6137 Registrant Contact: IESG 6139 Note to RFC Editor: Please remove the email address from the RFC 6140 after IANA records it. 6142 XML: None. Namespace URIs do not represent an XML specification. 6144 Registration request for the RDE NNDN XML schema: 6146 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6148 Registrant Contact: IESG 6150 Note to RFC Editor: Please remove the email address from the RFC 6151 after IANA records it. 6153 See section Section 9.13 of this document. 6155 Registration request for the CSV NNDN namespace: 6157 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6159 Registrant Contact: IESG 6161 Note to RFC Editor: Please remove the email address from the RFC 6162 after IANA records it. 6164 XML: None. Namespace URIs do not represent an XML specification. 6166 Registration request for the CSV NNDN XML schema: 6168 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6170 Registrant Contact: IESG 6172 Note to RFC Editor: Please remove the email address from the RFC 6173 after IANA records it. 6175 See section Section 9.14 of this document. 6177 Registration request for the RDE Policy namespace: 6179 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6181 Registrant Contact: IESG 6183 Note to RFC Editor: Please remove the email address from the RFC 6184 after IANA records it. 6186 XML: None. Namespace URIs do not represent an XML specification. 6188 Registration request for the RDE Policy XML schema: 6190 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6192 Registrant Contact: IESG 6194 Note to RFC Editor: Please remove the email address from the RFC 6195 after IANA records it. 6197 See section Section 9.15 of this document. 6199 Registration request for the RDE Header namespace: 6201 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6203 Registrant Contact: IESG 6205 Note to RFC Editor: Please remove the email address from the RFC 6206 after IANA records it. 6208 XML: None. Namespace URIs do not represent an XML specification. 6210 Registration request for the RDE Header XML schema: 6212 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6214 Registrant Contact: IESG 6216 Note to RFC Editor: Please remove the email address from the RFC 6217 after IANA records it. 6219 See section Section 9.16 of this document. 6221 Registration request for the RDE Common Objects namespace: 6223 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6225 Registrant Contact: IESG 6227 Note to RFC Editor: Please remove the email address from the RFC 6228 after IANA records it. 6230 XML: None. Namespace URIs do not represent an XML specification. 6232 Registration request for the RDE Common Objects XML schema: 6234 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6236 Registrant Contact: IESG 6238 Note to RFC Editor: Please remove the email address from the RFC 6239 after IANA records it. 6241 See section Section 9.17 of this document. 6243 12. Implementation Status 6245 Note to RFC Editor: Please remove this section and the reference to 6246 RFC 7942 [RFC7942] before publication. 6248 This section records the status of known implementations of the 6249 protocol defined by this specification at the time of posting of this 6250 Internet-Draft, and is based on a proposal described in RFC 7942 6251 [RFC7942]. The description of implementations in this section is 6252 intended to assist the IETF in its decision processes in progressing 6253 drafts to RFCs. Please note that the listing of any individual 6254 implementation here does not imply endorsement by the IETF. 6255 Furthermore, no effort has been spent to verify the information 6256 presented here that was supplied by IETF contributors. This is not 6257 intended as, and must not be construed to be, a catalog of available 6258 implementations or their features. Readers are advised to note that 6259 other implementations may exist. 6261 According to RFC 7942 [RFC7942], "this will allow reviewers and 6262 working groups to assign due consideration to documents that have the 6263 benefit of running code, which may serve as evidence of valuable 6264 experimentation and feedback that have made the implemented protocols 6265 more mature. It is up to the individual working groups to use this 6266 information as they see fit". 6268 12.1. Implementation in the gTLD space 6270 Organization: ICANN 6272 Name: ICANN Registry Agreement 6274 Description: the ICANN Base Registry Agreement requires Registries, 6275 Data Escrow Agents, and ICANN to implement this specification. ICANN 6276 receives daily notifications from Data Escrow Agents confirming that 6277 more than 1,200 gTLDs are sending deposits that comply with this 6278 specification. ICANN receives on a weekly basis per gTLD, from more 6279 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6280 also complies with this specification. In addition, ICANN is aware 6281 of Registry Service Provider transitions using data files that 6282 conform to this specification. 6284 Level of maturity: production. 6286 Coverage: all aspects of this specification are implemented. 6288 Version compatibility: versions 03 - 08 are known to be implemented. 6290 Contact: gustavo.lozano@icann.org 6292 URL: https://www.icann.org/resources/pages/registries/registries- 6293 agreements-en 6295 13. Security Considerations 6297 This specification does not define the security mechanisms to be used 6298 in the transmission of the data escrow deposits, since it only 6299 specifies the minimum necessary to enable the rebuilding of a 6300 registry from deposits without intervention from the original 6301 registry. 6303 Depending on local policies, some elements, or, most likely, the 6304 whole deposit will be considered confidential. As such, the parties 6305 SHOULD take all the necessary precautions such as encrypting the data 6306 at rest and in transit to avoid inadvertent disclosure of private 6307 data. Regardless of the precautions taken by the parties regarding 6308 data at rest and in transit, authentication credentials MUST NOT be 6309 escrowed. 6311 Authentication of the parties passing data escrow deposit files is 6312 also of the utmost importance. The escrow agent MUST properly 6313 authenticate the identity of the registry before accepting data 6314 escrow deposits. In a similar manner, the registry MUST authenticate 6315 the identity of the escrow agent before submitting any data. 6317 Additionally, the registry and the escrow agent MUST use integrity 6318 checking mechanisms to ensure the data transmitted is what the source 6319 intended. Validation of the contents by the escrow agent is 6320 RECOMMENDED to ensure not only that the file was transmitted 6321 correctly from the registry, but also that the contents are 6322 "meaningful". 6324 Note: if Transport Layer Security (TLS) is used when providing an 6325 escrow services, the recommendations in [RFC7525] MUST be 6326 implemented. 6328 14. Privacy Considerations 6330 This specification defines a format that may be used to escrow 6331 personal data. The process of data escrow is governed by a legal 6332 document agreed by the parties, and such legal document must ensure 6333 that privacy-sensitive and/or personal data receives the required 6334 protection. 6336 15. Acknowledgments 6338 Parts of this document are based on EPP [RFC5730] and related RFCs by 6339 Scott Hollenbeck. 6341 Special suggestions that have been incorporated into this document 6342 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6343 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6344 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6345 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6346 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6347 Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. 6349 Shoji Noguchi and Francisco Arias participated as co-authors until 6350 version 05 providing invaluable support for this document. 6352 16. Change History 6354 [[RFC Editor: Please remove this section.]] 6356 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6357 dnrd-objects-mapping-00 6359 1. Added definition for child elements under the element. 6361 2. Added definition for child elements under the element. 6363 3. Added definition for child elements under the element. 6365 4. Rewrote the IDN Variants Handling section to use the variant 6366 states as described in ICANN's Study of Issues Related to the 6367 Management of IDN Variant TLDs. 6369 5. Renamed to in the . 6371 6. Renamed to in the element. 6373 7. Renamed to in the element. 6375 8. Added element under element. 6377 9. Fixed some typographical errors and omissions. 6379 16.2. Changes from 00 to 01 6381 1. Specify OPTIONAL elements in the draft. 6383 2. Added NNDN object to support list of reserved names and different 6384 IDN variants models. 6386 3. Removed subordinated host element from the domain object. 6388 4. Added eppParams object. 6390 5. Added variantGenerator element to the domain object. 6392 6. Added lgr to the IDN table object. 6394 16.3. Changes from 01 to 02 6396 1. Updates to the all objects based on feedback from the list. 6398 2. Start of XML and CSV drafts merge. 6400 3. Added header object. 6402 4. Added report object. 6404 5. Added notification object. 6406 6. Added Data Escrow Agent Extended Verification Process section. 6408 7. Added Notifications from Registries to Third Parties. 6410 8. Added Notifications from Data Escrow Agents to Third Parties. 6412 9. Added FULL, DIFF deposit examples using the XML model only. 6414 16.4. Changes from 02 to 03 6416 1. Remove authinfo from the XML Schema. 6418 2. Resend attribute is now an element 6420 3. Scope attribute added to policy object. 6422 16.5. Changes from 03 to 04 6424 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6425 arias-noguchi-dnrd-objects-mapping-02. 6427 2. Changed the cksum attribute of to use CRC32 and 6428 changed all of the sample cksum values to use CRC32, based on 6429 feedback from David Kipling. 6431 3. Changed the optional element to be an optional 6432 "sep" attribute value of the element with a default 6433 value of "," based on feedback from David Kipling. 6435 4. Added support for the optional "parent" attribute for the to the 6436 CSV fields to indicate a field as a reference to a parent 6437 object, based on feedback from David Kipling. 6439 5. Added support for the CSV model for the NNDN. 6441 6. Added support to delete hosts based on roid. 6443 7. Added mirrored state to NNDN 6445 8. Minor fixes to XML XSDs. 6447 9. The Report and Notification objects were moved to draft-lozano- 6448 icann-registry-interfaces 6450 10. The section Data escrow notifications was moved to draft-lozano- 6451 icann-registry-interfaces 6453 11. Removed references to the , , and 6454 from the "hostStatuses" and "hostAddresses" CSV 6455 files. 6457 12. Removed references to the , , and 6458 from the "contactStatuses" CSV file. 6460 13. Removed references to the , , and 6461 from the "domainContacts", "domainStatuses", 6462 and "domainNameServers" CSV files. 6464 14. Changed to . 6466 15. Replaced use of to new field 6467 in the "domain", "idnLanguage", and "NNDN" CSV files. 6469 16. Replaced use of with in the 6470 "host" element. 6472 17. Changed the foreign key of the hosts to use 6473 instead of and removed use of in 6474 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6475 files. 6477 18. Added use of the MUST keyword for CSV fields that are required 6478 to be supported in an EPP based system. 6480 19. Removed use of the field element for the 6481 "registrar" CSV file. 6483 20. Added definition of field element. 6485 16.6. Changes from 04 to 05 6487 1. Updated the examples of the full and differential deposits using 6488 the CSV and XML model. 6490 2. Made optional for the "domainTransfer" CSV file 6491 to match the XML definition. 6493 3. Made optional for the "domain" CSV file 6494 to match the XML definition. 6496 4. Made optional for the "domain" and "contact" CSV 6497 files to match the XML definition. 6499 5. Change from IDREF to idType. 6501 6. Minor editorial changes. 6503 16.7. Changes from 05 to 06 6505 1. Revised the differential and incremental deposits for the CSV 6506 format to use cascade update / replace and delete from the parent 6507 object to be consistent with the XML format. 6509 2. Revised the structure of the CSV format sections to utilize sub- 6510 sections instead of a list for the CSV file definitions. 6512 3. Added the "CSV Parent Child Relationship" section to describe the 6513 concept of parent child relationships across CSV file 6514 definitions. 6516 4. Added the "domainNameServersAddresses" CSV File Definition 6517 section to support the domain host attributes model of [RFC5731]. 6519 5. Made the required fields in the CSV format consistent with the 6520 XML format. The CSV fields updated to be required include: 6521 , , , 6522 , , , 6523 , , , 6524 , , , 6525 , , 6526 , , , 6527 , , 6528 , and . 6530 6. Revised the CSV examples to use a more realistic set of records. 6532 16.8. Changes from 06 to 07 6534 1. Created "repositoryTypeGroup" group element in the rdeHeader 6535 including the , and 6536 elements. 6538 2. Added the optional "rcdn" and "registrarId" attributes to the 6539 element 6541 16.9. Changes from 07 to 08 6543 1. The following registrar elements were made optional to support 6544 greater flexibility for the implementation of policies: status, 6545 postalInfo, email and crDate. 6547 2. The following domain name elements were made optional to support 6548 greater flexibility for the implementation of policies: crRr. 6550 16.10. Changes from 08 to 09 6552 1. Implementation Status section was added 6554 16.11. Changes from 09 to 10 6556 1. Editorial changes in section Section 5.1.2.1.6. 6558 2. Added MAY clause when the DS Data Interface is used in section 6559 Section 5.1.2.1.6. 6561 16.12. Changes from 10 to REGEXT 00 6563 1. Internet Draft (I-D) adopted by the REGEXT WG. 6565 16.13. Changes REGEXT 00 to REGEXT 01 6567 1. Added the element to the 6568 "repositoryTypeGroup" group element in the rdeHeader. 6570 2. Privacy consideration section was added 6572 3. Updates on section 8 6574 16.14. Changes REGEXT 01 to REGEXT 02 6576 1. Added a choice between the use of the or 6577 fields in the CSV "domain", "host", and 6578 "contact" definitions. 6580 2. Added a choice between the use of the or 6581 fields in the CSV "domainNameServers" 6582 definition. 6584 3. Changed "of client" to "of the client" throughout the document. 6586 4. Modified all references of 'The attribute isRequired MUST equal 6587 "true".' to 'The attribute "isRequired" MUST equal "true".' 6589 5. Combined the and 6590 fields in a single required list for the CSV "domainContacts" 6591 definition. 6593 6. Combined the , , and 6594 fields in a single required list for the 6595 CSV "domainStatuses" definition. 6597 7. Moved the the fields to the MAY 6598 list for the CSV "domain", "host", and "contact" definitions. 6600 8. Made the order of the , , 6601 , and fields more consistent in the 6602 CSV lists. 6604 9. Fixed an error in the order of the object example. 6606 10. Changed to be optional to match being 6607 optional in the XML model, by having it use type 6608 rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and 6609 ensuring that is included in the MAY field 6610 lists and not the MUST field lists. 6612 11. Made optional for the "domain" CSV definition 6613 to be consistent with the XML model, by removing the sentence 6614 'The attribute "isRequired" MUST equal "true".' from the 6615 description and moving the field to the MAY field list. 6617 12. Made optional for the "domain" and "contact" 6618 CSV definitions to be consistent with the XML model, by moving 6619 the field to the MAY field list. 6621 13. Made optional to be consistent with the XML 6622 model, by having it use type rdeCsv:fClIDType instead of 6623 rdeCsv:fClIDRequiredType. 6625 14. Made required to be consistent with the XML 6626 model, by having it use type rdeCsv:fClIDRequiredType instead of 6627 rdeCsv:fClIDType. 6629 15. Made the field in the "host", "contact", 6630 and "registrar" CSV definitions required explicitly by removing 6631 'and isRequired="true"' and adding the sentence 'The attribute 6632 isRequired MUST equal "true".', when it is chosen as the primary 6633 field. 6635 16. Removed extra '/>.' at the end of the field 6636 description in the "hostStatuses" CSV definition. 6638 17. Made the field optional to be consistent 6639 with the XML model, by having csvRegistrar:fStatusType extend 6640 rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. 6642 18. Made the field for the "registrar" CSV 6643 definition explicitly optional to be consistent with the XML 6644 model, by adding the sentence 'The attribute isRequired MUST 6645 equal "false".' to the field description and including the 6646 definition of isRequired="false" in the "registrar" CSV 6647 definition examples. 6649 19. Added the choice between the use of the and 6650 fields in the deletes "registrar" CSV 6651 definition to be consistent with the "registrar" CSV definition. 6653 20. Made the and elements optional for the host and 6654 contact objects in the XML model to be consistent with the 6655 domain object. 6657 16.15. Changes REGEXT 02 to REGEXT 03 6659 1. Added the optional element contentTag in the header object. 6661 2. Editorial updates. 6663 16.16. Changes REGEXT 03 to REGEXT 04 6665 1. Note: Updates from version REGEXT 03 to REGEXT 04 attend the 6666 feedback provided during the document shepherd review. 6668 2. Editorial updates. 6670 3. Examples now use domain names from the .example TLD. 6672 4. The introduction was enhanced by explaining the need for data 6673 escrow and the proposed solution. 6675 5. Explanation regarding NNDN was improved. 6677 6. Explanation regarding the CSV and XML model was improved. 6679 7. Section 4.5 updated to make the text clearer. 6681 8. draft-arias-noguchi-registry-data-escrow is now referenced from 6682 the I-D repository. 6684 9. The XML prefix "rdeDomain" is now consistently used. 6686 10. The prevID attribute was removed from the examples of full 6687 deposits. 6689 11. The examples were updated to use present dates. 6691 16.17. Changes REGEXT 04 to REGEXT 05 6693 1. draft-ietf-regext-data-escrow (version 04) is now referenced from 6694 the I-D repository. 6696 2. The example in idnLanguage CSV file definition updated to use the 6697 sep attribute. 6699 3. The reference in the example in hostAddresses CSV file definition 6700 was updated. 6702 4. Moved [RFC0791] and [RFC4291] to the Normative References 6703 section. 6705 16.18. Changes REGEXT 05 to REGEXT 06 6707 1. Changes based on the feedback provided here: 6708 https://mailarchive.ietf.org/arch/msg/regext/ 6709 nA8eTYIrXJ44_6ullQlRLW6T74s 6711 16.19. Changes REGEXT 06 to REGEXT 07 6713 1. Changes based on the feedback provided here: 6714 https://mailarchive.ietf.org/arch/msg/regext/hDLz2ym4oR-ukA4Fm- 6715 QJ8FzaxxE 6717 2. Changes based on the feedback provided here: 6718 https://mailarchive.ietf.org/arch/msg/regext/780Xw- 6719 z1RMRb79nmZ6ABmRTo1fU 6721 16.20. Changes REGEXT 07 to REGEXT 08 6723 1. Changes based on the feedback provided here: 6724 https://mailarchive.ietf.org/arch/msg/regext/ 6725 UaMNvl1xh60ldjpqHHYc3TNsfhg 6727 2. Changes based on the feedback provided here: 6728 https://mailarchive.ietf.org/arch/msg/regext/ 6729 B3QTxUCWUE4R_QharAQlA3041j0 6731 17. Example of a Full Deposit using the XML model 6733 Example of a Full Deposit using the XML model: 6735 6736 6752 2019-10-17T00:00:00Z 6753 6754 1.0 6755 urn:ietf:params:xml:ns:rdeHeader-1.0 6756 6757 urn:ietf:params:xml:ns:rdeContact-1.0 6758 6759 urn:ietf:params:xml:ns:rdeHost-1.0 6760 6761 urn:ietf:params:xml:ns:rdeDomain-1.0 6762 6763 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6764 6765 urn:ietf:params:xml:ns:rdeIDN-1.0 6766 6767 urn:ietf:params:xml:ns:rdeNNDN-1.0 6768 6769 urn:ietf:params:xml:ns:rdeEppParams-1.0 6770 6771 6773 6774 6775 6776 6777 test 6778 2 6780 6781 1 6783 6784 1 6786 6787 1 6789 6790 1 6792 6793 1 6795 6796 1 6798 6799 6801 6802 6803 example1.example 6804 Dexample1-TEST 6805 6806 jd1234 6807 sh8013 6808 sh8013 6809 6810 ns1.example.com 6811 ns1.example1.example 6812 6813 RegistrarX 6814 RegistrarX 6815 1999-04-03T22:00:00.0Z 6816 2015-04-03T22:00:00.0Z 6817 6819 6820 6821 example2.example 6822 Dexample2-TEST 6823 6824 6825 jd1234 6826 sh8013 6827 sh8013 6828 RegistrarX 6829 RegistrarX 6830 1999-04-03T22:00:00.0Z 6831 2015-04-03T22:00:00.0Z 6832 6834 6835 6836 ns1.example1.example 6837 Hns1_example_test-TEST 6838 6839 6840 192.0.2.2 6841 192.0.2.29 6842 1080:0:0:0:8:800:200C:417A 6843 6844 RegistrarX 6845 RegistrarX 6846 1999-05-08T12:10:00.0Z 6847 RegistrarX 6848 2009-10-03T09:34:00.0Z 6849 6851 6852 6853 sh8013 6854 Csh8013-TEST 6855 6856 6857 6858 John Doe 6859 Example Inc. 6860 6861 123 Example Dr. 6862 Suite 100 6863 Dulles 6864 VA 6865 20166-6503 6866 US 6867 6868 6869 +1.7035555555 6870 6871 +1.7035555556 6872 6873 jdoe@example.example 6874 6875 RegistrarX 6876 RegistrarX 6877 6878 2009-09-13T08:01:00.0Z 6879 6880 RegistrarX 6881 6882 2009-11-26T09:10:00.0Z 6883 6884 2009-12-03T09:05:00.0Z 6885 6886 6887 6888 6889 6890 6892 6893 6894 RegistrarX 6895 Registrar X 6896 123 6897 ok 6898 6899 6900 123 Example Dr. 6901 6902 Suite 100 6903 6904 Dulles 6905 VA 6906 20166-6503 6907 US 6908 6909 6910 +1.7035555555 6911 6912 +1.7035555556 6913 6914 jdoe@example.example 6915 6916 http://www.example.example 6917 6918 6919 whois.example.example 6920 6921 http://whois.example.example 6922 6924 6925 2005-04-23T11:49:00.0Z 6926 6927 2009-02-17T17:51:00.0Z 6928 6929 6931 6932 6933 6934 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 6935 6936 6937 http://registro.br/dominio/regras.html 6938 6939 6941 6942 6943 xn--exampl-gva.example 6944 pt-BR 6945 example1.example 6946 withheld 6947 2005-04-23T11:49:00.0Z 6948 6950 6951 6952 1.0 6953 en 6954 6955 urn:ietf:params:xml:ns:domain-1.0 6956 6957 6958 urn:ietf:params:xml:ns:contact-1.0 6959 6960 6961 urn:ietf:params:xml:ns:host-1.0 6962 6963 6964 urn:ietf:params:xml:ns:rgp-1.0 6965 6966 urn:ietf:params:xml:ns:secDNS-1.1 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6985 6986 6989 6990 6992 18. Example of Differential Deposit using the XML model 6994 Example of a Differential Deposit using the XML model: 6996 6997 7012 2019-10-17T00:00:00Z 7013 7014 1.0 7015 urn:ietf:params:xml:ns:rdeHeader-1.0 7016 7017 urn:ietf:params:xml:ns:rdeContact-1.0 7018 7019 urn:ietf:params:xml:ns:rdeHost-1.0 7020 7021 urn:ietf:params:xml:ns:rdeDomain-1.0 7022 7023 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7024 7025 urn:ietf:params:xml:ns:rdeIDN-1.0 7026 7027 urn:ietf:params:xml:ns:rdeNNDN-1.0 7028 7029 urn:ietf:params:xml:ns:rdeEppParams-1.0 7030 7031 7033 7034 7035 7036 example2.example 7037 7038 7040 7041 7042 7043 7044 test 7045 1 7047 7048 1 7050 7051 1 7053 7054 1 7056 7057 1 7059 7060 1 7062 7063 1 7065 7066 7067 7069 7071 19. Example of a Full Deposit using the CSV model 7073 Example of a Full Deposit using the CSV model: 7075 7076 7090 2019-10-18T00:00:00Z 7091 7092 1.0 7093 urn:ietf:params:xml:ns:csvDomain-1.0 7094 urn:ietf:params:xml:ns:csvHost-1.0 7095 urn:ietf:params:xml:ns:csvContact-1.0 7096 urn:ietf:params:xml:ns:csvRegistrar-1.0 7097 urn:ietf:params:xml:ns:csvIDN-1.0 7098 urn:ietf:params:xml:ns:csvNNDN-1.0 7099 urn:ietf:params:xml:ns:rdeEppParams-1.0 7100 7101 7102 7103 test 7104 7105 4 7106 7107 7108 6 7109 7110 7111 9 7112 7113 7114 3 7115 7116 7117 2 7118 7119 7120 2 7121 7122 7123 1 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7146 domain-YYYYMMDD.csv 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7159 domainContacts-YYYYMMDD.csv 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7174 domainStatuses-YYYYMMDD.csv 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7186 domainNameServers-name-YYYYMMDD.csv 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7198 domainNameServers-roid-YYYYMMDD.csv 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7214 dnssec-ds-YYYYMMDD.csv 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7230 dnssec-key-YYYYMMDD.csv 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7249 domainTransfer-YYYYMMDD.csv 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7271 host-YYYYMMDD.csv 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7285 hostStatuses-YYYYMMDD.csv 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7298 hostAddresses-YYYYMMDD.csv 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7324 contact-YYYYMMDD.csv 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7338 contactStatuses-YYYYMMDD.csv 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7359 contactPostal-YYYYMMDD.csv 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7377 contactTransfer-YYYYMMDD.csv 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7398 contactDisclose-YYYYMMDD.csv 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7430 registrar-YYYYMMDD.csv 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7444 idnLanguage-YYYYMMDD.csv 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7462 NNDN-YYYYMMDD.csv 7463 7464 7465 7466 7467 7468 1.0 7469 en 7470 urn:ietf:params:xml:ns:domain-1.0 7471 7472 urn:ietf:params:xml:ns:host-1.0 7473 7474 urn:ietf:params:xml:ns:contact-1.0 7475 7476 7477 urn:ietf:params:xml:ns:secDNS-1.1 7478 7479 urn:ietf:params:xml:ns:rgp-1.0 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7502 7503 7504 7505 7507 20. Example of Differential Deposit using the CSV model 7509 Example of a Differential Deposit using the CSV model: 7511 7512 7526 2019-10-18T00:00:00Z 7527 7528 1.0 7529 urn:ietf:params:xml:ns:csvDomain-1.0 7530 urn:ietf:params:xml:ns:csvHost-1.0 7531 urn:ietf:params:xml:ns:csvContact-1.0 7532 urn:ietf:params:xml:ns:csvRegistrar-1.0 7533 urn:ietf:params:xml:ns:csvIDN-1.0 7534 7535 7536 7537 7538 7539 7540 7541 7542 7544 domain-delete-YYYYMMDD.csv 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7557 host-delete-YYYYMMDD.csv 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7570 contact-delete-YYYYMMDD.csv 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7583 registrar-delete-YYYYMMDD.csv 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7596 idnLanguage-delete-YYYYMMDD.csv 7597 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7610 NNDN-delete-YYYYMMDD.csv 7611 7612 7613 7614 7615 7616 7617 7618 test 7619 7620 2 7621 7622 7623 2 7624 7625 7626 3 7627 7628 7629 1 7630 7631 7632 1 7633 7634 7635 1 7636 7637 7638 1 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7661 domain-YYYYMMDD.csv 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7674 domainContacts-YYYYMMDD.csv 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7689 domainStatuses-YYYYMMDD.csv 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7701 domainNameServers-name-YYYYMMDD.csv 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7713 domainNameServers-roid-YYYYMMDD.csv 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7729 dnssec-ds-YYYYMMDD.csv 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7745 dnssec-key-YYYYMMDD.csv 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7764 domainTransfer-YYYYMMDD.csv 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7786 host-YYYYMMDD.csv 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7800 hostStatuses-YYYYMMDD.csv 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7813 hostAddresses-YYYYMMDD.csv 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7839 contact-YYYYMMDD.csv 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7853 contactStatuses-YYYYMMDD.csv 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7874 contactPostal-YYYYMMDD.csv 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7892 contactTransfer-YYYYMMDD.csv 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7913 contactDisclose-YYYYMMDD.csv 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7945 registrar-YYYYMMDD.csv 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7959 idnLanguage-YYYYMMDD.csv 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7977 NNDN-YYYYMMDD.csv 7978 7979 7980 7981 7982 7983 1.0 7984 en 7985 urn:ietf:params:xml:ns:domain-1.0 7986 7987 urn:ietf:params:xml:ns:host-1.0 7988 7989 urn:ietf:params:xml:ns:contact-1.0 7990 7991 7992 urn:ietf:params:xml:ns:secDNS-1.1 7993 7994 urn:ietf:params:xml:ns:rgp-1.0 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8021 21. References 8023 21.1. Normative References 8025 [I-D.ietf-regext-data-escrow] 8026 Lozano, G., "Registry Data Escrow Specification", draft- 8027 ietf-regext-data-escrow-10 (work in progress), June 2020. 8029 [ISO-3166-1] 8030 3166, I. S., "Codes for the representation of names of 8031 countries and their subdivisions -- Part 1: Country 8032 codes", ISO Standard 3166, November 2006. 8034 [ITU-E164] 8035 International Telecommunication Union, "The international 8036 public telecommunication numbering plan", ITU-T 8037 Recommendation E.164, February 2005. 8039 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8040 DOI 10.17487/RFC0791, September 1981, 8041 . 8043 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8044 Requirement Levels", BCP 14, RFC 2119, 8045 DOI 10.17487/RFC2119, March 1997, 8046 . 8048 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8049 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8050 . 8052 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8053 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8054 DOI 10.17487/RFC3915, September 2004, 8055 . 8057 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8058 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8059 2006, . 8061 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8062 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8063 . 8065 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8066 Domain Name Mapping", STD 69, RFC 5731, 8067 DOI 10.17487/RFC5731, August 2009, 8068 . 8070 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8071 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8072 August 2009, . 8074 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8075 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8076 August 2009, . 8078 [RFC5891] Klensin, J., "Internationalized Domain Names in 8079 Applications (IDNA): Protocol", RFC 5891, 8080 DOI 10.17487/RFC5891, August 2010, 8081 . 8083 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8084 Security Extensions Mapping for the Extensible 8085 Provisioning Protocol (EPP)", RFC 5910, 8086 DOI 10.17487/RFC5910, May 2010, 8087 . 8089 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 8090 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 8091 May 2017, . 8093 [W3C.REC-xml-20081126] 8094 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 8095 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 8096 Edition) REC-xml-20081126", November 2008, 8097 . 8099 [W3C.REC-xmlschema-1-20041028] 8100 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 8101 "XML Schema Part 1: Structures Second Edition REC- 8102 xmlschema-1-20041028", October 2004, 8103 . 8105 [W3C.REC-xmlschema-2-20041028] 8106 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 8107 Second Edition REC-xmlschema-2-20041028", October 2004, 8108 . 8110 21.2. Informative References 8112 [ICANN-GTLD-RA-20170731] 8113 ICANN, "Base Registry Agreement 2017-07-31", July 2017, 8114 . 8117 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8118 DOI 10.17487/RFC3688, January 2004, 8119 . 8121 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8122 DOI 10.17487/RFC3912, September 2004, 8123 . 8125 [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, 8126 "Recommendations for Secure Use of Transport Layer 8127 Security (TLS) and Datagram Transport Layer Security 8128 (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 8129 2015, . 8131 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8132 Code: The Implementation Status Section", BCP 205, 8133 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8134 . 8136 [variantTLDsReport] 8137 Internet Corporation for Assigned Names and Numbers 8138 (ICANN), "A Study of Issues Related to the Management of 8139 IDN Variant TLDs", February 2012, 8140 . 8143 Authors' Addresses 8145 Gustavo Lozano 8146 Internet Corporation for Assigned Names and Numbers 8147 12025 Waterfront Drive, Suite 300 8148 Los Angeles 90292 8149 United States of America 8151 Phone: +1.310.823.9358 8152 Email: gustavo.lozano@icann.org 8154 James Gould 8155 VeriSign, Inc. 8156 12061 Bluemont Way 8157 Reston 20190 8158 United States of America 8160 Email: jgould@verisign.com 8162 Chethan Thippeswamy 8163 VeriSign, Inc. 8164 12061 Bluemont Way 8165 Reston 20190 8166 United States of America 8168 Email: cthippeswamy@verisign.com