idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-07.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 (Apr 28, 2020) is 1459 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-10) exists of draft-ietf-regext-data-escrow-08 -- 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 (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track J. Gould 5 Expires: October 30, 2020 C. Thippeswamy 6 VeriSign 7 Apr 28, 2020 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-07 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 October 30, 2020. 35 Copyright Notice 37 Copyright (c) 2020 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 54 2.1. XML Model . . . . . . . . . . . . . . . . . . . . . . . . 5 55 2.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . . . 5 56 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 4. Conventions Used in This Document . . . . . . . . . . . . . . 6 58 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 59 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . . . . . 140 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 . . . . . . . . . . . . . . . . . 144 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 17. Example of a Full Deposit using the XML model . . . . . . . . 148 125 18. Example of Differential Deposit using the XML model . . . . . 154 126 19. Example of a Full Deposit using the CSV model . . . . . . . . 155 127 20. Example of Differential Deposit using the CSV model . . . . . 164 128 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 175 129 21.1. Normative References . . . . . . . . . . . . . . . . . . 175 130 21.2. Informative References . . . . . . . . . . . . . . . . . 177 131 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 178 133 1. Introduction 135 Registry Data Escrow is the process by which a registry periodically 136 submits data deposits to a third-party called an escrow agent. These 137 deposits comprise the minimum data needed by a third-party to resume 138 operations if the registry cannot function and is unable or unwilling 139 to facilitate an orderly transfer of service. For example, for a 140 domain name registry or registrar, the data to be deposited would 141 include all the objects related to registered domain names, e.g., 142 names, contacts, name servers, etc. 144 The goal of data escrow is higher resiliency of registration 145 services, for the benefit of Internet users. The beneficiaries of a 146 registry are not just those registering information there, but all 147 relying parties that need to identify the owners of objects. 149 In the context of domain name registries, registration data escrow is 150 a requirement for generic top-level domains and some country code 151 top-level domain managers are also currently escrowing data. There 152 is also a similar requirement for ICANN-accredited domain registrars. 154 This document defines the standard set of objects for a Domain Name 155 Registry that uses the Registry Data Escrow Specification described 156 in [I-D.ietf-regext-data-escrow] for escrow. The set of objects 157 include: 159 o Domain: Internet domain names that are typically provisioned in a 160 Domain Name Registry using the EPP domain name mapping [RFC5731]. 161 The attributes defined in the EPP domain name mapping [RFC5731] 162 are fully supported by this document. 164 o Host: Internet host names that are typically provisioned in a 165 Domain Name Registry using the EPP host mapping [RFC5732]. The 166 attributes defined in the EPP host mapping [RFC5732] are fully 167 supported by this document. 169 o Contact: Individual or organization social information provisioned 170 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 171 The attributes defined in the EPP contact mapping [RFC5733] are 172 fully supported by this document. 174 o Registrar: The organization that sponsors objects like domains, 175 hosts, and contacts in a Domain Name Registry. 177 o NNDN (NNDN's not domain name): Domain Name Registries may maintain 178 domain names without their being persisted as domain objects in 179 the registry system, for example, a list of reserved names not 180 available for registration. The NNDN is a lightweight domain-like 181 object that is used to escrow domain names not maintained as 182 domain name objects. 184 This document defines the following pseudo-objects: 186 o IDN Table Reference: Internationalized Domain Names (IDN) included 187 in the Domain Object Data Escrow include references to the IDN 188 Table and Policy used in IDN registration. 190 o EPP parameters: Definition of the specific EPP parameters 191 supported by the Registry Operator. 193 o Header: Used to specify counters of objects in the database at a 194 certain point in time (watermark). 196 o Policy: Used to specify OPTIONAL elements from this specification 197 that are REQUIRED based on the business model of the registry. 199 2. Models 201 This document defines two different models that can be used to 202 deposit data escrow objects: XML and CSV. 204 The data escrow deposit MAY contain a mix of both models but an 205 object MUST be escrowed only in one model. 207 This document does not suggest the use of a particular model, and 208 both are equivalent. A Domain Name Registry may choose the model 209 that is more appropriate for the peculiarities of its systems. For 210 example, a registry may use the CSV-export functionality of the RDBMS 211 for escrow; therefore, the CSV model may be more appropriate. 212 Another registry may use the code developed for EPP to implement 213 escrow. 215 2.1. XML Model 217 XML: The XML model includes all the deposit information (meta-data 218 and data) in an XML document. The definition of the XML format is 219 fully defined in the XML schemas. As a convention, the objects 220 represented using the XML model are referenced using RDE and an XML 221 namespace that is prefixed with "rde". For example, the Domain Name 222 object represented using the XML model can be referred to as the RDE 223 Domain Name with the XML namespace including rdeDomain 224 (urn:ietf:params:xml:ns:rdeDomain-1.0). 226 2.2. CSV Model 228 CSV: The CSV model uses XML to define the data escrow format of the 229 data contained in referenced Comma-Separated Values (CSV) files. As 230 a convention, the objects represented using the CSV model is 231 referenced using CSV and an XML namespace that is prefixed with 232 "csv". For example, the Domain Name object represented using the CSV 233 model can be referred to as the CSV Domain Name with the XML 234 namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). 236 3. Terminology 238 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 239 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 240 "OPTIONAL" in this document are to be interpreted as described in BCP 241 14 [RFC2119] [RFC8174] when, and only when, they appear in all 242 capitals, as shown here. 244 REGISTRY. In the context of this draft the definition will be 245 overloaded (from the definition in the base protocol) to indicate an 246 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 247 NAME. 249 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 250 or any other domain name at any level in the DNS tree for which a 251 Registry (either directly or through an affiliate company) provides 252 Registry Services for other organizations or individuals. For 253 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 255 REGISTRY SERVICES. Services offered by the Registry critical to the 256 following tasks: the provisioning of domain names on receipt of 257 requests and data from registrars; responding to registrar queries 258 for status information relating to the DNS servers for the RCDN; 259 dissemination of RCDN zone files; operation of the Registry DNS 260 servers; responding to queries for contact and other information 261 concerning DNS registrations in the RCDN; and any other products or 262 services that only a Registry is capable of providing, by reason of 263 its designation as the Registry. Typical examples of Registry 264 Services are DNS resolution for the RCDN, WHOIS and EPP. 266 ALLOCATED. A status of some label with respect to a zone, whereby 267 the label is associated administratively to some entity that has 268 requested the label. This term (and its cognates "allocation" and 269 "to allocate") may represent the first step on the way to delegation 270 in the DNS. 272 4. Conventions Used in This Document 274 4.1. Date and Time 276 Numerous fields indicate "dates", such as the creation and expiry 277 dates for domain names. These fields SHALL contain timestamps 278 indicating the date and time in UTC as specified in [RFC3339], with 279 no offset from the zero meridian. 281 4.2. Country names 283 Country identifiers SHALL be represented using two character 284 identifiers as specified in [ISO-3166-1]. 286 4.3. Telephone numbers 288 Telephone numbers (both voice and facsimile) SHALL be formatted based 289 on structures defined in [ITU-E164]. Telephone numbers described in 290 this specification are character strings that MUST begin with a plus 291 sign ("+", ASCII value 0x002B), followed by a country code defined in 292 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 293 a sequence of digits representing the telephone number. 295 4.4. Checksum 297 The checksum of the CSV data escrow files MUST use CRC32, which is 298 the algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 299 of ITU-T recommendation V.42. 301 4.5. IP addresses 303 The syntax of IP addresses MUST conform to the text representation of 304 either Internet Protocol Version 4 [RFC0791] or Internet Protocol 305 Version 6 [RFC4291]. 307 4.6. Conventions applicable to the CSV Model 309 4.6.1. CSV Parent Child Relationship 311 The CSV model represents a relational model, where the CSV files 312 represent relational tables, the fields of the CSV files represent 313 columns of the tables, and each line of the CSV file represents a 314 record. As in a relational model, the CSV files can have 315 relationships utilizing primary keys in the parent CSV file 316 definitions and foreign keys in the child CSV file definitions for a 317 1-to-many relationship. The primary keys are not explicitly defined, 318 but the foreign keys are using the boolean "parent" field attribute 319 in the child CSV file. The relationships between the CSV files are 320 used to support a cascade replace or cascade delete of records 321 starting from the parent record in Differential and Incremental 322 Deposits (see [I-D.ietf-regext-data-escrow]). 324 The following is an example of the CSV file definitions for a Sample 325 object consisting of a parent "sample" CSV File Definition and a 326 child "sampleStatuses" CSV File Definition. The primary key for the 327 Sample object is the field that is used as the 328 foreign key in the "sampleStatuses" CSV File Definition by specifying 329 the "parent=true" attribute. If a Sample record is updated or 330 deleted in a Differential or Incremental Deposit, it should cascade 331 replace the data using the records included in the child 332 "sampleStatuses" CSV File Definition or cascade delete the existing 333 records in the child "sampleStatuses" CSV File Definition, 334 respectively. 336 337 ... 338 339 340 341 342 343 344 345 346 347 348 349 350 351 353 sample-YYYYMMDD.csv 354 355 356 357 358 359 360 361 362 363 364 365 367 sampleStatuses-YYYYMMDD.csv 368 369 370 371 ... 372 374 4.6.2. CSV elements 376 4.6.2.1. element 378 To support the CSV model, an element is defined for each object that 379 substitutes for the element and for the 380 element, that contains one or more elements. For 381 example, the Domain Name Object (Section 5.1) defines the 382 element, that substitutes for the 383 element, and the element, that substitutes for 384 the element. Both the element and 385 the elements contain one or more 386 elements. The element has the following child elements: 388 Ordered list of CSV fields used in the CSV files. 389 There are one or more child elements that substitute for the 390 abstract element. Each element defines the format 391 of the CSV field contained in the CSV files. The 392 elements support the "type" attribute that defines the XML simple 393 data type of the field element. The elements 394 support the "isRequired" attribute, with a default value of 395 "false", when set to "true" indicates that the field must be non- 396 empty in the CSV files and when set to "false" indicates that the 397 field MAY be empty in the CSV files. The "isRequired" attribute 398 MAY be specifically set for the field elements within the XML 399 schema and MAY be overridden when specifying the fields under the 400 element. The element supports an 401 OPTIONAL "parent" attribute that identifies the field as a 402 reference to a parent object, as defined in CSV Parent Child 403 Relationship (Section 4.6.1). For example, the field SHOULD set the 405 "parent" attribute to "true" to identify it as the parent domain 406 name of the domain status. 408 A list of one or more CSV files using the 409 child element. The child element 410 defines a reference to the CSV file name and has the following 411 optional attributes: 413 compression If the CSV file is compressed, the "compression" 414 attribute defines the compression format like "gzip" or "zip". 416 encoding Defines the encoding of the CSV file with the default 417 encoding of "UTF-8". 419 cksum Defines the checksum of the CSV file using CRC32, as 420 defined in Section 4.4. This attribute is used to validate 421 that the full CSV file exists and has not been tampered with. 423 The element requires a "name" attribute that defines the 424 purpose of the CSV file with values like "domain", "host", "contact". 425 The supported "name" attribute values are defined for each object 426 type. The OPTIONAL "sep" attribute defines the CSV separator 427 character with the default separator character of ",". 429 The following is an example of the 430 element for domain name records where the is set 431 as required with isRequired="true". 433 434 ... 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 454 domain-YYYYMMDD.csv 455 456 457 458 ... 459 461 The following is example of the "domain-YYYYMMDD.csv" file with one 462 record matching the definition. 464 domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 465 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 466 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 467 The following is an example of the 468 element for domain name records. 470 471 ... 472 473 474 475 476 477 479 domain-delete-YYYYMMDD.csv 480 481 482 483 ... 484 486 The following is example of the "domain-delete-YYYYMMDD.csv" file 487 with three records that matches the single field. 489 domain1.example 490 domain2.example 491 domainN.example 493 4.6.2.2. CSV common field elements 495 The element defined in the element 496 (Section 4.6.2.1) section has child elements that substitute for the 497 abstract element. By convention 498 elements include an 'f' prefix to identify them as field definition 499 elements. There are a set of common field elements that are used 500 across multiple data escrow objects. The common field elements are 501 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 502 using the "rdeCsv" sample namespace prefix. The CSV common field 503 elements include: 505 UTF-8 encoded name field with 506 type="eppcom:labelType". 508 Repository Object IDentifier (ROID) field with 509 type="eppcom:roidType" and isRequired="true". 511 Registrant contact identifier with 512 type="eppcom:clIDType". 514 The object status description, which is 515 free form text describing the rationale for the status, with 516 type="normalizedString". 518 Identifier of the client (registrar) that sponsors 519 the object with type="eppcom:clIDType" and isRequired="true". 521 Identifier of the registrar, defined in Section 5.4, 522 of the client that created the object with type="eppcom:clIDType". 524 Identifier of the client that created the object with 525 type="eppcom:clIDType". 527 Identifier of the registrar, defined in Section 5.4, 528 of the client that updated the object with type="eppcom:clIDType". 530 Identifier of the client that updated the object with 531 type="eppcom:clIDType". 533 Identifier of the registrar, defined in Section 5.4, 534 of the client that requested the transfer with 535 type="eppcom:clIDType" and isRequired="true". 537 Identifier of the client that requested the transfer 538 with type="eppcom:clIDType". 540 Identifier of the registrar, defined in Section 5.4, 541 of the client that should take or took action with 542 type="eppcom:clIDType" and isRequired="true". 544 Identifier of the client that should take or took 545 action for transfer with type="eppcom:clIDType". 547 Created date of object with type="dateTime". 549 Updated date of object with type="dateTime". 551 Expiration date of object with type="dateTime". 553 Date that transfer was requested with 554 type="dateTime" and isRequired="true". 556 Date that transfer action should be taken or has 557 been taken with type="dateTime" and isRequired="true". 559 Date of last transfer with type="dateTime". 561 State of the most recent transfer request with 562 type="eppcom:trStatusType" and isRequired="true". 564 General token field with type="token". 566 General language field with type="language". 568 IDN Table Identifier used for IDN domain names 569 with type="token". 571 General positive integer field with 572 type="positiveInteger". 574 Contains the URL of an object like a registrar object 575 with type="anyURI". 577 Custom field with name attribute that defines the 578 custom field name" with type="token". 580 4.6.3. Internationalized and Localized Elements 582 Some elements MAY be provided in either internationalized form 583 ("int") or localized form ("loc"). Those elements use a field value 584 or "isLoc" attribute to specify the form used. If an "isLoc" 585 attribute is used, a value of "true" indicates the use of the 586 localized form and a value of "false" indicates the use of the 587 internationalized form. This MAY override the form specified for a 588 parent element. A value of "int" is used to indicate the 589 internationalized form and a value of "loc" is used to indicate the 590 localized form. When the internalized form ("int") is provided, the 591 field value MUST be represented in a subset of UTF-8 that can be 592 represented in the 7-bit US-ASCII character set. When the localized 593 form ("loc") is provided, the field value MAY be represented in 594 unrestricted UTF-8. 596 The field elements below of the "registrar" 597 element specify the internationalized form with the 598 isLoc="false" attribute. 600 ... 601 602 ... 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 634 registrar-YYYYMMDD.csv 635 636 637 638 ... 639 640 ... 642 The following is an example of using the 643 field value to define the internationalized or localized form of the 644 remainder of the "contactPostal" field values. 646 ... 647 648 ... 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 666 contactPostal-YYYYMMDD.csv 667 668 669 670 ... 671 672 ... 674 5. Object Description 676 This section describes the base objects supported by this 677 specification: 679 5.1. Domain Name Object 681 The domain name object is based on the EPP domain name mapping 682 specified in [RFC5731]. The domain name object supports both the XML 683 Model and the CSV Model, defined in the Models (Section 2) section. 684 The elements used for both models are defined in the following 685 sections. 687 5.1.1. XML Model 689 There are two elements used in the data escrow of the domain name 690 objects for the XML model including the , under the 691 element, and the element, under the 692 element. 694 5.1.1.1. object 696 The domain element is based on the EPP domain response for an 697 authorized client (see Section 3.1.2. of [RFC5731]) with additional 698 data from an EPP Query Response, see Section 3.1.3. of 699 [RFC5731], RGP status from [RFC3915], and data from the EPP 700 command, see Section 5.2.1. of [RFC5910]. 702 A element substitutes for the abstract 703 element to define a concrete definition of a domain. The 704 element can be replaced by other domain definitions 705 using the XML schema substitution groups feature. 707 The element contains the following child elements: 709 o A element that contains the fully qualified name of the 710 domain name object. For IDNs the A-Label is used (see [RFC5891], 711 Section 4.4). 713 o A element that contains the repository object identifier 714 assigned to the domain name object when it was created. 716 o An OPTIONAL element that contains the fully qualified 717 domain name in Unicode character set. It MUST be provided if 718 available. 720 o An OPTIONAL element that references the IDN 721 Table used for the IDN. This corresponds to the "id" attribute of 722 the element. This element MUST be present if the 723 domain name is an IDN. 725 o An OPTIONAL element is used to indicate that the 726 domain name is an IDN variant. This element contains the domain 727 name used to generate the IDN variant. 729 o One or more elements that contain the current status 730 descriptors associated with the domain name. 732 o Zero or more OPTIONAL elements to represent 733 "pendingDelete" sub-statuses, including "redemptionPeriod", 734 "pendingRestore", and "pendingDelete", that a domain name can be 735 in as a result of grace period processing as specified in 736 [RFC3915]. 738 o An OPTIONAL element that contains the identifier for 739 the human or organizational social information object associated 740 as the holder of the domain name object. 742 o Zero or more OPTIONAL elements that contain identifiers 743 for the human or organizational social information objects 744 associated with the domain name object. 746 o An OPTIONAL element that contains the fully qualified names 747 of the delegated host objects or host attributes (name servers) 748 associated with the domain name object. See Section 1.1 of 749 [RFC5731] for a description of the elements used to specify host 750 objects or host attributes. 752 o A element that contains the identifier of the sponsoring 753 registrar. 755 o An OPTIONAL element that contains the identifier of the 756 registrar that created the domain name object. An OPTIONAL client 757 attribute is used to specify the client that performed the 758 operation. 760 o An OPTIONAL element that contains the date and time of 761 the domain name object creation. This element MUST be present if 762 the domain name has been allocated. 764 o An OPTIONAL element that contains the date and time 765 identifying the end (expiration) of the domain name object's 766 registration period. This element MUST be present if the domain 767 name has been allocated. 769 o An OPTIONAL element that contains the identifier of the 770 registrar that last updated the domain name object. This element 771 MUST NOT be present if the domain has never been modified. An 772 OPTIONAL client attribute is used to specify the client that 773 performed the operation. 775 o An OPTIONAL element that contains the date and time of 776 the most recent domain-name-object modification. This element 777 MUST NOT be present if the domain name object has never been 778 modified. 780 o An OPTIONAL element that contains the public key 781 information associated with Domain Name System security (DNSSEC) 782 extensions for the domain name as specified in [RFC5910]. 784 o An OPTIONAL element that contains the date and time of 785 the most recent domain object successful transfer. This element 786 MUST NOT be present if the domain name object has never been 787 transferred. 789 o An OPTIONAL element that contains the following child 790 elements related to the last transfer request of the domain name 791 object. This element MUST NOT be present if a transfer request 792 for the domain name has never been created. 794 * A element that contains the state of the most recent 795 transfer request. 797 * A element that contains the identifier of the registrar 798 that requested the domain name object transfer. An OPTIONAL 799 client attribute is used to specify the client that performed 800 the operation. 802 * A element that contains the date and time that the 803 transfer was requested. 805 * An element that contains the identifier of the registrar 806 that should act upon a PENDING transfer request. For all other 807 status types, the value identifies the registrar that took the 808 indicated action. An OPTIONAL client attribute is used to 809 specify the client that performed the operation. 811 * An element that contains the date and time of a 812 required or completed response. For a PENDING request, the 813 value identifies the date and time by which a response is 814 required before an automated response action will be taken by 815 the registry. For all other status types, the value identifies 816 the date and time when the request was completed. 818 * An OPTIONAL element that contains the end of the 819 domain name object's validity period (expiry date) if the 820 transfer caused or causes a change in the validity period. 822 Example of a domain object: 824 ... 825 826 xn--exampl-gva.example 827 Dexample1-TEST 828 pt-BR 829 example.example 830 831 jd1234 832 sh8013 833 sh8013 834 835 ns1.example.com 836 ns1.example1.example 837 838 RegistrarX 839 RegistrarX 840 1999-04-03T22:00:00.0Z 841 2015-04-03T22:00:00.0Z 842 843 ... 845 5.1.1.2. object 847 The element contains the fully qualified domain 848 name that was deleted and purged. 850 Example of object: 852 ... 853 854 ... 855 856 foo.example 857 bar.example 858 859 ... 860 861 ... 863 5.1.2. CSV Model 865 For the CSV Model of the domain name object, the 866 child element of the element is used to hold the new 867 or updated domain name objects for the deposit. The 868 child element of the element is 869 used to hold the deleted or purged domain name objects for the 870 deposit. Both the and 871 elements contain one or more elements with a set of 872 named CSV file definitions using the "name" attribute. 874 Differential and Incremental Deposits are based on changes to the 875 domain name objects. The updated domain name object data under the 876 element is a cascade replace down all of the 877 domain name CSV files starting with the parent "domain" CSV File 878 Definition (Section 5.1.2.1.1). The child CSV file definitions 879 include a field. All the child CSV 880 file definition data for the domain name objects in the parent 881 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 882 deleted and then set using the data in the child CSV files. The 883 deleted domain name object data under the element 884 is a cascade delete starting from the "domain" Deletes CSV File 885 Definition (Section 5.1.2.2.1). 887 5.1.2.1. 889 The is used to hold the new or updated domain 890 name object information for the deposit. The is 891 split into separate CSV file definitions using named 892 elements with the "name" attribute. The following sections include 893 the supported domain name CSV file definitions: 895 5.1.2.1.1. "domain" CSV File Definition 897 The "domain" CSV File Definition defines the fields and CSV file 898 references used for the parent domain name object records. All the 899 other domain name CSV file definitions are child CSV files based on 900 the inclusion of the field. 902 The following "csvDomain" field elements MUST be used in the "domain" 903 element: 905 Domain name field with type="eppcom:labelType" and 906 isRequired="true". 908 The following "csvDomain" field elements MAY be used in the "domain" 909 element: 911 Fully qualified name of the original IDN 912 domain name object related to the variant domain name object with 913 type="eppcom:labelType". 915 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 916 "domain" element: 918 Registry Object IDentifier (ROID) for the domain name 919 object with isRequired="true". 921 or A choice of: 923 Identifier of the sponsoring client with 924 isRequired="true". 926 Contains the ID assigned by ICANN with 927 type="positiveInteger". The attribute "isRequired" MUST equal 928 "true". 930 The following "rdeCsv" fields, defined in section CSV common field 931 elements (Section 4.6.2.2), MAY be used in the "domain" 932 element: 934 Identifier of the registrar, defined in Section 5.4, 935 of the client that created the object. 937 Identifier of the client that created the domain name 938 object. 940 Identifier of the registrar, defined in Section 5.4, 941 of the client that updated the object. 943 Identifier of the client that last updated the domain 944 name object. 946 UTF8 encoded domain name for the 947 field element. 949 IDN Table Identifier used for the IDN domain 950 name object that MUST match a field element 951 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 953 Registrant contact identifier for the domain 954 name object. 956 Created date and time of the domain name object. 958 Date and time of the last update to the domain name 959 object. 961 Expiration date and time for the domain name 962 object. 964 Date and time of the last transfer for the domain 965 name object. 967 Example of a "domain" element. 969 ... 970 971 ... 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 991 domain-YYYYMMDD.csv 992 993 994 995 ... 996 997 ... 999 Example of the corresponding domain-YYYYMMDD.csv file. The file 1000 contains four records (two active ASCII domains, original IDN with 1001 LANG-1 language rules, and variant IDN with LANG-1 language rules). 1003 domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 1004 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1005 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1006 domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 1007 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 1008 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1009 xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 1010 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1011 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1012 xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example, 1013 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 1014 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1016 5.1.2.1.2. "domainContacts" CSV File Definition 1018 The "domainContacts" CSV File Definition defines the fields and CSV 1019 file references used for the domain name object link records to 1020 contact objects, as described in Contact Object (Section 5.3). 1022 The following "csvDomain" field elements, defined for the "domain" 1023 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 1024 "domainContacts" element: 1026 The name of the domain object that is linked to 1027 the contact object with isRequired="true". 1029 The contact type for the contact object 1030 link with type="domain:contactAttrType" and isRequired="true". 1031 The supported contact type values include "admin" for the 1032 administration contact, "billing" for the billing contact, and 1033 "tech" for the technical contact. 1035 The following "csvContact" fields, defined for the "contact" CSV File 1036 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 1037 element: 1039 The server-unique contact identifier with 1040 isRequired="true". 1042 Example of a "domainContacts" 1043 element. 1045 ... 1046 1047 ... 1048 1049 1050 1051 1052 1053 1054 1055 1057 domainContacts-YYYYMMDD.csv 1058 1059 1060 1061 ... 1062 1063 ... 1065 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1066 file contains an admin, tech, and billing contact for the four domain 1067 names domain1.example, domain2.example, xn--bc123-3ve.example and 1068 xn--bc321-3ve.example. 1070 domain1.example,domain1admin,admin 1071 domain1.example,domain1tech,tech 1072 domain1.example,domain1billing,billing 1073 domain2.example,domain2admin,admin 1074 domain2.example,domain2tech,tech 1075 domain2.example,domain2billing,billing 1076 xn--bc123-3ve.example,xnabc123admin,admin 1077 xn--bc123-3ve.example,xnabc123tech,tech 1078 xn--bc123-3ve.example,xnabc123billing,billing 1079 xn--bc321-3ve.example,xnabc123admin,admin 1080 xn--bc321-3ve.example,xnabc123tech,tech 1081 xn--bc321-3ve.example,xnabc123billing,billing 1083 5.1.2.1.3. "domainStatuses" CSV File Definition 1085 The "domainStatuses" CSV File Definition defines the fields and CSV 1086 file references used for the domain name object statuses. 1088 The following "csvDomain" fields, defined for the "domain" CSV File 1089 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1090 element: 1092 Domain name of status with isRequired="true". 1094 The status of the domain name with 1095 type="domain:statusValueType" and isRequired="true". 1097 The Registry Grace Period (RGP) status, as a 1098 sub-status of the "pendingDelete" status 1099 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1101 The following "rdeCsv" fields, defined in section CSV common field 1102 elements (Section 4.6.2.2), MAY be used in the "domainStatuses" 1103 element: 1105 Domain object status description which 1106 is free form text describing the rationale for the status. 1108 Language of the field. 1110 Example of a "domainStatuses" 1111 element. 1113 ... 1114 1115 ... 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1127 domainStatuses-YYYYMMDD.csv 1128 1129 1130 1131 ... 1132 1133 ... 1135 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1136 file contains the statuses for the four domain names domain1.example, 1137 domain2.example, xn--bc123-3ve.example and xn--bc321-3ve.example. 1139 domain1.example,clientUpdateProhibited,"Disallow update", 1140 en, 1141 domain1.example,clientDeleteProhibited,"Disallow delete", 1142 en, 1143 domain2.example,ok,,, 1144 xn--bc123-3ve.example,ok,,, 1145 xn--bc321-3ve.example,ok,,, 1147 5.1.2.1.4. "domainNameServers" CSV File Definition 1149 The "domainNameServers" CSV File Definition defines the fields and 1150 CSV file references used for the domain name delegated hosts (name 1151 servers). The "domainNameServers" CSV files define the relationship 1152 between a domain name object and a delegated host. The 1153 "domainNameServers" CSV File is used to support the 1154 model, defined in [RFC5731]. 1156 The following "csvDomain" fields, defined for the "domain" CSV File 1157 Definition (Section 5.1.2.1.1), MUST be used in the 1158 "domainNameServers" element: 1160 Domain name using the delegated host with 1161 isRequired="true". 1163 The following "csvHost" and "rdeCsv" field elements MUST be used in 1164 the "domainNameServers" element: 1166 or A choice of: 1168 Host name field with type="eppcom:labelType" and 1169 isRequired="true". 1171 Host object Registry Object IDentifier (ROID) 1172 assigned to the host object with isRequired="true". 1174 Example of a "domainNameServers" 1175 element. 1177 ... 1178 1179 ... 1180 1181 1182 1183 1184 1185 1186 1188 domainNameServers-YYYYMMDD.csv 1189 1190 1191 1192 ... 1193 1194 ... 1196 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1197 The file contains the delegated hosts (name servers) for the four 1198 domain names domain1.example, domain2.example, xn--bc123-3ve.example 1199 and xn--bc321-3ve.example referenced via the field 1200 element. 1202 domain1.example,Hns1_domain1_test-TEST 1203 domain1.example,Hns2_domain1_test-TEST 1204 domain2.example,Hns1_domain2_test-TEST 1205 domain2.example,Hns2_domain2_test-TEST 1206 xn--bc123-3ve.example,Hns1_example_test-TEST 1207 xn--bc123-3ve.example,Hns2_example_test-TEST 1208 xn--bc321-3ve.example,Hns1_example_test-TEST 1209 xn--bc321-3ve.example,Hns2_example_test-TEST 1211 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1213 The "domainNameServersAddresses" CSV File Definition defines the 1214 fields and CSV file references used for supporting the host as domain 1215 attributes model. 1217 The following "csvDomain" fields, defined for the "domain" CSV File 1218 Definition (Section 5.1.2.1.1), MUST be used in the 1219 "domainNameServersAddresses" element: 1221 Domain name using the delegated host with host 1222 and isRequired="true". 1224 The following "rdeCsv" fields, defined in section Host CSV model 1225 elements (Section 5.2.2), MUST be used in the 1226 "domainNameServersAddresses" element: 1228 Host name field with type="eppcom:labelType" and 1229 isRequired="true". 1231 The following "csvHost" fields, defined in section Host CSV model 1232 elements (Section 5.2.2), MAY be used in the 1233 "domainNameServersAddresses" element: 1235 IP addresses associated with the host object with 1236 type="host:addrStringType". 1238 IP addresses version associated with the host 1239 object with type="host:ipType". "host:ipType" has the enumerated 1240 values of "v4" or "v6". 1242 Example of a "domainNameServersAddresses" 1243 element. 1245 ... 1246 1247 ... 1248 1249 1250 1251 1252 1253 1254 1255 1256 1258 domainNameServersAddresses-YYYYMMDD.csv 1259 1260 1261 1262 ... 1263 1264 ... 1266 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1267 file. The file contains the delegated hosts (name servers) for the 1268 four domain names domain1.example, domain2.example, xn-- 1269 bc123-3ve.example and xn--bc321-3ve.example. 1271 domain1.example,ns1.domain1.example,192.0.2.1,v4 1272 domain1.example,ns2.domain1.example,2001:DB8::1,v6 1273 domain2.example,ns1.example.net,, 1274 domain2.example,ns2.example.net,, 1275 xn--bc123-3ve.example,ns1.example.net,, 1276 xn--bc123-3ve.example,ns2.example.net,, 1277 xn--bc321-3ve.example,ns1.example.net,, 1278 xn--bc321-3ve.example,ns2.example.net,, 1280 5.1.2.1.6. "dnssec" CSV File Definition 1282 The "dnssec" CSV File Definition defines the fields and CSV file 1283 references used for the domain name object DNSSEC records (DS or Key 1284 Data). 1286 The following "csvDomain" field elements MUST be used in the "dnssec" 1287 element when the DS Data Interface per 1288 [RFC5910] is used: 1290 Contains the DS key tag value per [RFC5910] with 1291 type="unsignedShort" and isRequired="true". 1293 Contains the DS algorithm value per [RFC5910] 1294 with type="unsignedByte" and isRequired="true". 1296 Contains the DS digest type value per 1297 [RFC5910] with type="unsignedByte" and isRequired="true". 1299 Contains the DS digest value per [RFC5910] with 1300 type="hexBinary" and isRequired="true". 1302 The following "csvDomain" field elements MUST be used in the "dnssec" 1303 element when the Key Data Interface per 1304 [RFC5910] is used and MAY be used in the "dnssec" 1305 element when the DS Data Interface per [RFC5910] is 1306 used: 1308 Contains the flags field value per [RFC5910] with 1309 type="unsignedShort" and isRequired="true". 1311 Contains the Key protocol value per [RFC5910] 1312 with type="unsignedByte" and isRequired="true". 1314 Contains the Key algorithm value per [RFC5910] 1315 with type="unsignedByte" and isRequired="true". 1317 Contains the public key value per [RFC5910] with 1318 type="secDNS:keyType" and isRequired="true". 1320 The following "csvDomain" field elements MAY be used in the "dnssec" 1321 element: 1323 Indicates a child's preference for the 1324 number of seconds after signature generation when the parent's 1325 signature on the DS information provided by the child will expire 1326 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1328 The following "domain" fields, defined for the "domain" CSV File 1329 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1330 element: 1332 Domain name of the domain object associated with 1333 the DNSSEC record and isRequired="true". 1335 Example of a "dnssec" element with 1336 the DS Data Interface of [RFC5910]: 1338 1339 ... 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1352 dnssec-ds-YYYYMMDD.csv 1353 1354 1355 1356 ... 1357 1358 ... 1360 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1361 contains two DS records for domain1.example. 1363 domain1.example,604800,12345,3,1,49FD46E6C4B45C55D4AC 1364 domain1.example,604800,12346,3,1,38EC35D5B3A34B44C39B 1365 Example of a "dnssec" element with 1366 the Key Data Interface of [RFC5910]: 1368 1369 ... 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1382 dnssec-key-YYYYMMDD.csv 1383 1384 1385 1386 ... 1387 1388 ... 1390 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1391 contains two key records for domain1.example. 1393 domain1.example,604800,257,3,1,AQPJ////4Q== 1394 domain1.example,604800,257,3,1,AQPJ////4QQQ 1396 5.1.2.1.7. "domainTransfer" CSV File Definition 1398 The "domainTransfer" CSV File Definition defines the fields and CSV 1399 file references used for the domain name object pending and completed 1400 transfer records. No additional field elements were added for use in 1401 the "domainTransfer" element. 1403 The following "rdeCsv" fields, defined in section CSV common field 1404 elements (Section 4.6.2.2), MUST be used in the "domainTransfer" 1405 element: 1407 State of the most recent transfer request with 1408 isRequired="true". 1410 Identifier of the registrar, defined in Section 5.4, 1411 of the client that requested the transfer with isRequired="true". 1413 Date and time that the transfer was requested with 1414 isRequired="true". 1416 Identifier of the registrar, defined in Section 5.4, 1417 of the client that should take or took action with 1418 isRequired="true". 1420 Date and time that the transfer action should be 1421 taken or has been taken with isRequired="true". 1423 The following "rdeCsv" fields, defined in section CSV common field 1424 elements (Section 4.6.2.2), MAY be used in the "domainTransfer" 1425 element: 1427 Expiration date if the transfer command caused or 1428 causes a change in the validity period. 1430 Identifier of the client that requested the transfer. 1432 Identifier of the client that should take or took 1433 action for transfer. 1435 The following "csvDomain" fields, defined for the "domain" CSV File 1436 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1437 element: 1439 Domain name of the domain object involved in the 1440 transfer with isRequired="true". 1442 Example of a "domainTransfer" 1443 element. 1445 ... 1446 1447 ... 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1463 domainTransfer-YYYYMMDD.csv 1464 1465 1466 1467 ... 1468 1469 ... 1471 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1472 file contains one domain transfer record with a pending status. 1474 domain1.example,pending,registrarX,clientY, 1475 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1476 2016-04-03T22:00:00.0Z 1478 5.1.2.2. 1480 The is used to hold the deleted domain name 1481 objects in a Differential or Incremental Deposit. All the domain 1482 name object data is deleted as part of a cascade delete. The 1483 is split into separate CSV file definitions using 1484 named elements with the "name" attribute. The following 1485 section defines the supported domain name deletes CSV file 1486 definition. 1488 5.1.2.2.1. "domain" Deletes CSV File Definition 1490 The following "csvDomain" field elements MUST be used in the deletes 1491 "domain" element: 1493 Domain name field with type="eppcom:labelType" and 1494 isRequired="true". 1496 Example of a "domain" element: 1498 ... 1499 1500 ... 1501 1502 1503 1504 1505 1506 1508 domain-delete-YYYYMMDD.csv 1509 1510 1511 1512 ... 1513 1514 ... 1516 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1517 file contains two domain name records. 1519 domain1.example 1520 domain2.example 1522 5.2. Host Object 1524 The host object is based on the EPP host name mapping in [RFC5732]. 1525 The host object supports both the XML Model and the CSV Model, 1526 defined in Models (Section 2) section. The elements used for both 1527 models are defined in the following sections. Both the 1528 and elements contain one or more 1529 elements with a set of named CSV file definitions using 1530 the "name" attribute. 1532 5.2.1. XML Model 1534 There are two elements used in the data escrow of the host objects 1535 for the XML model including the , under the 1536 element, and the element, under 1537 the element. 1539 A element substitutes for the 1540 abstract element to define a concrete definition of a host. The 1541 element can be replaced by other host 1542 definitions using the XML schema substitution groups feature. 1544 5.2.1.1. element 1546 The RDE host object is based on the EPP host response for an 1547 authorized client (Section 3.1.2. of [RFC5732]). 1549 The OPTIONAL element contains the following child elements: 1551 o A element that contains the fully qualified name of the 1552 host object. 1554 o A element that contains the repository object identifier 1555 assigned to the host object when the object was created. 1557 o One or more elements that describe the status of the host 1558 object. 1560 o Zero or more elements that contain the IP addresses 1561 associated with the host object. 1563 o A element that contains the identifier of the sponsoring 1564 registrar. 1566 o An OPTIONAL element that contains the identifier of the 1567 registrar that created the host object. An OPTIONAL client 1568 attribute is used to specify the client that performed the 1569 operation. 1571 o An OPTIONAL element that contains the date and time of 1572 host-object creation. 1574 o An OPTIONAL element that contains the identifier of the 1575 registrar that last updated the host object. This element MUST 1576 NOT be present if the host object has never been modified. An 1577 OPTIONAL client attribute is used to specify the client that 1578 performed the operation. 1580 o An OPTIONAL element that contains the date and time of 1581 the most recent host-object modification. This element MUST NOT 1582 be present if the host object has never been modified. 1584 o An OPTIONAL element that contains the date and time of 1585 the most recent host object successful transfer. This element 1586 MUST NOT be present if the domain name object has never been 1587 transfered. 1589 Example of object: 1591 ... 1592 1593 ns1.example1.example 1594 Hns1_example_test-TEST 1595 1596 1597 192.0.2.2 1598 192.0.2.29 1599 1080:0:0:0:8:800:200C:417A 1600 RegistrarX 1601 RegistrarX 1602 1999-05-08T12:10:00.0Z 1603 RegistrarX 1604 2009-10-03T09:34:00.0Z 1605 1606 ... 1608 5.2.1.2. object 1610 The element contains the fully qualified domain name 1611 of a host that was deleted. The element also 1612 supports host removal based on roid to support SRS systems in which 1613 different hosts with the same fully qualified domain name are active 1614 at the same time. 1616 Example of object: 1618 ... 1619 1620 ... 1621 1622 ns1.example.example 1623 1624 ... 1625 1626 ... 1628 5.2.2. CSV Model 1630 For the CSV Model of the host object, the child 1631 element of the element is used to hold the new or 1632 updated host objects for the deposit. The child 1633 element of the element is used to hold the deleted or 1634 purged host objects for the deposit. 1636 Differential and Incremental Deposits are based on changes to the 1637 host objects. The updated host object data under the 1638 element is a cascade replace down all of the host 1639 CSV files starting with the parent "host" CSV File Definition 1640 (Section 5.2.2.1.1). The child CSV file definitions include a 1641 field. All the child CSV file 1642 definition data for the host objects in the parent "host" CSV File 1643 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1644 using the data in the child CSV files. The deleted host object data 1645 under the element is a cascade delete starting from 1646 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1648 5.2.2.1. 1650 The is used to hold the new or updated host object 1651 information for the deposit. The is split into 1652 separate CSV file definitions using named elements with 1653 the "name" attribute. The following sections include the supported 1654 host CSV file definitions. 1656 5.2.2.1.1. "host" CSV File Definition 1658 The "host" CSV File Definition defines the fields and CSV file 1659 references used for the host object records. 1661 The following "csvHost" field elements MUST be used in the "host" 1662 element: 1664 Host name field with type="eppcom:labelType" and 1665 isRequired="true". 1667 The following "rdeCsv" fields, defined in section CSV common field 1668 elements (Section 4.6.2.2), MUST be used in the "host" 1669 element: 1671 Repository Object IDentifier (ROID) assigned to the 1672 host object with isRequired="true". 1674 The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the 1675 "host" element: 1677 or A choice of: 1679 Identifier of the sponsoring client with 1680 isRequired="true". 1682 Contains the ID assigned by ICANN with 1683 type="positiveInteger". The attribute "isRequired" MUST equal 1684 "true". 1686 Identifier of the registrar, defined in Section 5.4, 1687 of the client that created the object. 1689 Identifier of the client that created the host 1690 object. 1692 Identifier of the registrar, defined in Section 5.4, 1693 of the client that updated the object. 1695 Identifier of the client that last updated the host 1696 object. 1698 Date and time that the host object was created. 1700 Date and time that the host object was last 1701 updated. 1703 Date and time that the host was last transferred. 1705 Example of a "host" element. 1707 ... 1708 1709 ... 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1726 host-YYYYMMDD.csv 1727 1728 1729 1730 ... 1731 1732 ... 1734 Example of the corresponding host-YYYYMMDD.csv file. The file 1735 contains six host records with four being internal hosts and two 1736 being external hosts. 1738 ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX, 1739 clientY,1999-05-08T12:10:00.0Z,registrarX, 1740 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1741 ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX, 1742 clientY,1999-05-08T12:10:00.0Z,registrarX, 1743 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1744 ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX, 1745 clientY,1999-05-08T12:10:00.0Z,registrarX, 1746 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1747 ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, 1748 clientY,1999-05-08T12:10:00.0Z,registrarX, 1749 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1750 ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, 1751 clientY,1999-05-08T12:10:00.0Z,registrarX, 1752 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1753 ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, 1754 clientY,1999-05-08T12:10:00.0Z,registrarX, 1755 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1757 5.2.2.1.2. "hostStatuses" CSV File Definition 1759 The "hostStatuses" CSV File Definition defines the fields and CSV 1760 file references used for the host object statuses. 1762 The following "csvHost" fields, defined for the "host" CSV File 1763 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1764 element: 1766 The status of the host with 1767 type="host:statusValueType" and isRequired="true". 1769 The following "rdeCsv" fields, defined in section CSV common field 1770 elements (Section 4.6.2.2), MUST be used in the "hostStatuses" 1771 element: 1773 Host object Registry Object IDentifier (ROID) 1774 assigned to the host object with isRequired="true". 1776 The following "rdeCsv" fields, defined in section CSV common field 1777 elements (Section 4.6.2.2), MAY be used in the "hostStatuses" 1778 element: 1780 Host object status description which is 1781 free form text describing the rationale for the status. The 1782 attribute "isRequired" MUST equal "true". 1784 Language of the field. 1786 Example of a "hostStatuses" element. 1788 ... 1789 1790 ... 1791 1792 1793 1794 1795 1796 1797 1798 1799 1801 hostStatuses-YYYYMMDD.csv 1802 1803 1804 1805 ... 1806 1807 ... 1809 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1810 file contains the statuses for the six host names 1811 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example, 1812 ns2.domain2.example, ns1.example.net and ns2.example.net. 1814 Hns1_domain1_test-TEST,ok,, 1815 Hns2_domain1_test-TEST,ok,, 1816 Hns1_domain2_test-TEST,ok,, 1817 Hns2_domain2_test-TEST,ok,, 1818 Hns1_example_test-TEST,ok,, 1819 Hns2_example_test-TEST,ok,, 1821 5.2.2.1.3. "hostAddresses" CSV File Definition 1823 The "hostAddresses" CSV File Definition defines the fields and CSV 1824 file references used for the host object IP addresses. 1826 The following "csvHost" field elements MUST be used in the 1827 "hostAddresses" element: 1829 IP addresses associated with the host object with 1830 type="host:addrStringType". The attribute "isRequired" MUST equal 1831 "true". 1833 IP addresses version associated with the host 1834 object with type="host:ipType". "host:ipType" has the enumerated 1835 values of "v4" or "v6". The attribute "isRequired" MUST equal 1836 "true". 1838 The following "rdeCsv" fields, defined in section CSV common field 1839 elements (Section 4.6.2.2), MUST be used in the "hostAddresses" 1840 element: 1842 Host object Registry Object IDentifier (ROID) 1843 assigned to the host object with isRequired="true". 1845 Example of a "hostAddresses" element. 1847 ... 1848 1849 ... 1850 1851 1852 1853 1854 1855 1856 1857 1859 hostAddresses-YYYYMMDD.csv 1860 1861 1862 1863 ... 1864 1865 ... 1867 Example of the corresponding hostAddresses-YYYYMMDD.csv file. The 1868 file contains the IP addresses for the host names 1869 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and 1870 ns2.domain2.example. 1872 Hns1_domain1_test-TEST,192.0.2.1,v4 1873 Hns2_domain1_test-TEST,2001:DB8::1,v6 1874 Hns1_domain2_test-TEST,192.0.2.2,v4 1875 Hns2_domain2_test-TEST,2001:DB8::2,v6 1877 5.2.2.2. 1879 The is used to hold the deleted host objects in a 1880 Differential or Incremental Deposit. All the host object data is 1881 deleted as part of a cascade delete. The is split 1882 into separate CSV file definitions using named elements 1883 with the "name" attribute. The following section defines the 1884 supported host deletes CSV file definition. 1886 5.2.2.2.1. "host" Deletes CSV File Definition 1888 The following "rdeCsv" fields, defined in section CSV common field 1889 elements (Section 4.6.2.2), MUST be used in the "host" 1890 element: 1892 Repository Object IDentifier (ROID) assigned to the 1893 host object with isRequired="true". 1895 Example of a "host" element. 1897 ... 1898 1899 ... 1900 1901 1902 1903 1904 1905 1907 host-delete-YYYYMMDD.csv 1908 1909 1910 1911 ... 1912 1913 ... 1915 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1916 host records. 1918 Hns1_domain1_test-TEST 1919 Hns2_domain1_test-TEST 1920 Hns1_domain2_test-TEST 1921 Hns2_domain2_test-TEST 1923 5.3. Contact Object 1925 The contact object is based on the EPP contact name mapping in 1926 [RFC5733]. The contact object supports both the XML Model and the 1927 CSV Model, defined in Models (Section 2) section. The elements used 1928 for both models are defined in the following sections. 1930 5.3.1. XML Model 1932 There are two elements used in the data escrow of the contact objects 1933 for the XML model including the , under the 1934 element, and the element, 1935 under the element. 1937 A element substitutes for the abstract 1938 element to define a concrete definition of a contact. The 1939 element can be replaced by other contact 1940 definitions using the XML schema substitution groups feature. 1942 5.3.1.1. object 1944 The contact object is based on the EPP contact response for an 1945 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1946 including the data from an EPP Query Response, see 1947 Section 3.1.3. of [RFC5733]. 1949 The OPTIONAL element contains the following child elements: 1951 o A element that contains the server-unique identifier of the 1952 contact object 1954 o A element that contains the Repository Object IDentifier 1955 assigned to the contact object when the object was created. 1957 o One or more elements that describe the status of the 1958 contact object. 1960 o One or two elements that contain postal-address 1961 information. Two elements are provided so that address 1962 information can be provided in both internationalized and 1963 localized forms; a "type" attribute is used to identify the two 1964 forms. If an internationalized form (type="int") is provided, 1965 element content MUST be represented in a subset of UTF-8 that can 1966 be represented in the 7-bit US-ASCII character set. If a 1967 localized form (type="loc") is provided, element content MAY be 1968 represented in unrestricted UTF-8. The element 1969 contains the following child elements: 1971 * A element that contains the name of the individual or 1972 role represented by the contact. 1974 * An OPTIONAL element that contains the name of the 1975 organization with which the contact is affiliated. 1977 * An element that contains address information associated 1978 with the contact. An element contains the following 1979 child elements: 1981 + One, two, or three OPTIONAL elements that contain 1982 the contact's street address. 1984 + A element that contains the contact's city. 1986 + An OPTIONAL element that contains the contact's state 1987 or province. 1989 + An OPTIONAL element that contains the contact's postal 1990 code. 1992 + A element that contains the contact's two-letter 1993 country code. 1995 o An OPTIONAL element that contains the contact's voice 1996 telephone number. 1998 o An OPTIONAL element that contains the contact's facsimile 1999 telephone number. 2001 o An element that contains the contact's email address. 2003 o A element that contains the identifier of the sponsoring 2004 registrar. 2006 o An OPTIONAL element that contains the identifier of the 2007 registrar that created the contact object. An OPTIONAL client 2008 attribute is used to specify the client that performed the 2009 operation. 2011 o An OPTIONAL element that contains the date and time of 2012 contact-object creation. 2014 o An OPTIONAL element that contains the identifier of the 2015 registrar that last updated the contact object. This element MUST 2016 NOT be present if the contact has never been modified. An 2017 OPTIONAL client attribute is used to specify the client that 2018 performed the operation. 2020 o An OPTIONAL element that contains the date and time of 2021 the most recent contact-object modification. This element MUST 2022 NOT be present if the contact object has never been modified. 2024 o An OPTIONAL element that contains the date and time of 2025 the most recent contact object successful transfer. This element 2026 MUST NOT be present if the contact object has never been 2027 transferred. 2029 o An OPTIONAL element that contains the following child 2030 elements related to the last transfer request of the contact 2031 object: 2033 * A element that contains the state of the most recent 2034 transfer request. 2036 * A element that contains the identifier of the registrar 2037 that requested the domain name object transfer. An OPTIONAL 2038 client attribute is used to specify the client that performed 2039 the operation. 2041 * An element that contains the identifier of the registrar 2042 that should act upon a PENDING transfer request. For all other 2043 status types, the value identifies the registrar that took the 2044 indicated action. An OPTIONAL client attribute is used to 2045 specify the client that performed the operation. 2047 * A element that contains the date and time that the 2048 transfer was requested. 2050 * An element that contains the date and time of a 2051 required or completed response. For a PENDING request, the 2052 value identifies the date and time by which a response is 2053 required before an automated response action will be taken by 2054 the registry. For all other status types, the value identifies 2055 the date and time when the request was completed. 2057 o An OPTIONAL element that identifies elements that 2058 requiring exceptional server-operator handling to allow or 2059 restrict disclosure to third parties. See Section 2.9 of 2060 [RFC5733] for a description of the child elements contained within 2061 the element. 2063 Example object: 2065 ... 2066 2067 sh8013 2068 Csh8013-TEST 2069 2070 2071 2072 John Doe 2073 Example Inc. 2074 2075 123 Example Dr. 2076 Suite 100 2077 Dulles 2078 VA 2079 20166-6503 2080 US 2081 2082 2083 +1.7035555555 2084 +1.7035555556 2085 jdoe@example.example 2086 RegistrarX 2087 RegistrarX 2088 2009-09-13T08:01:00.0Z 2089 RegistrarX 2090 2009-11-26T09:10:00.0Z 2091 2009-12-03T09:05:00.0Z 2092 2093 pending 2094 clientW 2095 2011-03-08T19:38:00.0Z 2096 RegistrarX 2097 2011-03-13T23:59:59.0Z 2098 2099 2100 2101 2102 2103 2104 ... 2106 5.3.1.2. object 2108 The element contains the id of a contact that was 2109 deleted. 2111 Example of object: 2113 ... 2114 2115 ... 2116 2117 sh8013-TEST 2118 co8013-TEST 2119 2120 ... 2121 2122 ... 2124 5.3.2. CSV Model 2126 For the CSV Model of the contact object, the 2127 child element of the element is used to hold the new 2128 or updated contacts objects for the deposit. The 2129 child element of the element is 2130 used to hold the deleted or purged contact objects for the deposit. 2131 Both the and elements 2132 contain one or more elements with a set of named CSV 2133 file definitions using the "name" attribute. 2135 Differential and Incremental Deposits are based on changes to the 2136 contact objects. The updated contact object data under the 2137 element is a cascade replace down all of the 2138 contact CSV files starting with the parent "contact" CSV File 2139 Definition (Section 5.3.2.1.1). The child CSV file definitions 2140 include a field. All the child CSV 2141 file definition data for the contact objects in the parent "contact" 2142 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2143 then set using the data in the child CSV files. The deleted contact 2144 object data under the element is a cascade 2145 delete starting from the "contact" Deletes CSV File Definition 2146 (Section 5.3.2.2.1). 2148 5.3.2.1. 2150 The is used to hold the new or updated contact 2151 object information for the deposit. The is 2152 split into separate CSV file definitions using named 2153 elements with the "name" attribute. The following sections include 2154 the supported contact CSV file definitions. 2156 5.3.2.1.1. "contact" CSV File Definition 2158 The "contact" CSV File Definition defines the fields and CSV file 2159 references used for the contact object records. 2161 The following "csvContact" field elements MUST be used in the 2162 "contact" element: 2164 Contains the server-unique contact identifier with 2165 type="eppcom:clIDType" and isRequired="true". 2167 Contains the contact's email address with 2168 type="eppcom:minTokenType" and isRequired="true". 2170 The following field elements MAY be used in the "contact" 2171 element: 2173 Contains the contact's voice telephone number 2174 with type="contact:e164StringType". 2176 Contains the contact's voice telephone number 2177 extension with type="token". 2179 Contains the contact's facsimile telephone number 2180 with type="contact:e164StringType". 2182 Contains the contact's facsimile telephone 2183 number extension with type="token". 2185 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 2186 "contact" element: 2188 The Registry Object IDentifier (ROID) for the contact 2189 object with isRequired="true". 2191 or A choice of: 2193 Identifier of the sponsoring client with 2194 isRequired="true". 2196 Contains the ID assigned by ICANN with 2197 type="positiveInteger". The attribute "isRequired" MUST equal 2198 "true". 2200 The following "rdeCsv" fields, defined in section CSV common field 2201 elements (Section 4.6.2.2), MAY be used in the "contact" 2202 element: 2204 Identifier of the registrar, defined in Section 5.4, 2205 of the client that created the object. 2207 Identifier of the client that created the contact 2208 object. 2210 Identifier of the registrar, defined in Section 5.4, 2211 of the client that updated the object. 2213 Identifier of the client that last updated the 2214 contact object. 2216 Created date and time of the contact object. 2218 Date and time of the last update to the contact 2219 object. 2221 Date and time of the last transfer for the contact 2222 object. 2224 Example of a "contact" element. 2226 ... 2227 2228 ... 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2249 contact-YYYYMMDD.csv 2250 2251 2252 2253 ... 2254 2255 ... 2257 Example of the contact-YYYYMMDD.csv file. The file contains nine 2258 object contact records. 2260 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2261 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2262 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2263 2009-11-26T09:10:00.0Z 2264 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2265 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2266 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2267 2009-11-26T09:10:00.0Z 2268 domain1billing,Cdomain1billing-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 domain2admin,Cdomain2admin-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 domain2tech,Cdomain2tech-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 domain2billing,Cdomain2billing-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 xnabc123admin,Cxnabc123admin-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 xnabc123tech,Cxnabc123tech-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 xnabc123billing,Cxnabc123billing-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 2297 5.3.2.1.2. "contactStatuses" CSV File Definition 2299 The "contactStatuses" CSV File Definition defines the fields and CSV 2300 file references used for the contact object statuses. 2302 The following "csvContact" field elements, defined for the "contact" 2303 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2304 "contactStatuses" element: 2306 Server-unique contact identifier of status with 2307 isRequired="true". 2309 The status of the contact with 2310 type="contact:statusValueType" and isRequired="true". 2312 The following "rdeCsv" fields, defined in section CSV common field 2313 elements (Section 4.6.2.2), MAY be used in the "contactStatuses" 2314 element: 2316 The contact object status description 2317 which is free form text describing the rationale for the status. 2319 Language of the field. 2321 Example of a "contactStatuses" 2322 element. 2324 ... 2325 2326 ... 2327 2328 2329 2330 2331 2332 2333 2334 2335 2337 contactStatuses-YYYYMMDD.csv 2338 2339 2340 2341 ... 2342 2343 ... 2345 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2346 file contains the statuses for the nine contact identifiers. 2348 domain1admin,ok,, 2349 domain1tech,ok,, 2350 domain1billing,ok,, 2351 domain2admin,ok,, 2352 domain2tech,ok,, 2353 domain2billing,ok,, 2354 xnabc123admin,ok,, 2355 xnabc123tech,ok,, 2356 xnabc123billing,ok,, 2358 5.3.2.1.3. "contactPostal" CSV File Definition 2360 The "contactPostal" CSV File Definition defines the fields and CSV 2361 file references used for the contact postal info object records. 2363 The following "csvContact" field elements MUST be used in the 2364 "contactPostal" element: 2366 Contains the form of the postal-address 2367 information with type="contact:postalLineType" and 2368 isRequired="true". This field specifies the form ("int" or 2369 "loc"), as defined in Section 4.6.3, of the , 2370 , , , 2371 , , fields. 2373 Contains the contact's name of the individual or 2374 role represented by the contact with type="contact:postalLineType" 2375 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2376 indicate the localized or internationalized form as defined in 2377 section Section 4.6.3. 2379 Contains the contact's street address line with 2380 type="contact:fPostalLineType". An index attribute is required to 2381 indicate which street address line the field represents with index 2382 "0" for the first line and index "2" for the last line. An 2383 OPTIONAL "isLoc" attribute to used to indicate the localized or 2384 internationalized form as defined in section Section 4.6.3. 2386 Contains the contact's city with 2387 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2388 "isLoc" attribute to used to indicate the localized or 2389 internationalized form as defined in section Section 4.6.3. 2391 Contains the contact's country code with 2392 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2393 attribute to used to indicate the localized or internationalized 2394 form as defined in section Section 4.6.3. 2396 The following "csvContact" field elements MAY be used in the 2397 "contactPostal" element: 2399 Contains the name of the organization with which 2400 the contact is affiliated with type="contact:optPostalLineType". 2401 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2402 internationalized form as defined in section Section 4.6.3. 2404 Contains the contact's state or province with 2405 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2406 to used to indicate the localized or internationalized form as 2407 defined in section Section 4.6.3. 2409 Contains the contact's postal code with 2410 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2411 indicate the localized or internationalized form as defined in 2412 section Section 4.6.3. 2414 The following "csvContact" fields, defined for the "contact" CSV File 2415 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2416 element: 2418 Server-unique contact identifier for the contact 2419 object with isRequired="true". 2421 Example of a "contactPostal" 2422 element. 2424 ... 2425 2426 ... 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2444 contactPostal-YYYYMMDD.csv 2445 2446 2447 2448 ... 2449 2450 ... 2452 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2453 nine contact postal records. 2455 domain1admin,int,"John Doe","Example Inc.", 2456 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2457 domain1tech,int,"John Doe","Example Inc.", 2458 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2459 domain1billing,int,"John Doe","Example Inc.", 2460 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2461 domain2admin,int,"John Doe","Example Inc.", 2462 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2463 domain2tech,int,"John Doe","Example Inc.", 2464 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2465 domain2billing,int,"John Doe","Example Inc.", 2466 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2467 xnabc123admin,int,"John Doe","Example Inc.", 2468 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2469 xnabc123tech,int,"John Doe","Example Inc.", 2470 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2471 xnabc123billing,int,"John Doe","Example Inc.", 2472 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2474 5.3.2.1.4. "contactTransfer" CSV File Definition 2476 The "contactTransfer" CSV File Definition defines the fields and CSV 2477 file references used for the contact object pending and completed 2478 transfer records. No additional field elements were added for use in 2479 the "contactTransfer" element. The 2480 following "rdeCsv" fields, defined in section CSV common field 2481 elements (Section 4.6.2.2), MUST be used in the "contactTransfer" 2482 element: 2484 State of the most recent transfer request with 2485 isRequired="true". 2487 Identifier of the registrar, defined in Section 5.4, 2488 of the client that requested the transfer with isRequired="true". 2490 Date and time that the transfer was requested with 2491 isRequired="true". 2493 Identifier of the registrar, defined in Section 5.4, 2494 of the client that should take or took action with 2495 isRequired="true". 2497 Date and time that the transfer action should be 2498 taken or has been taken with isRequired="true". 2500 The following "rdeCsv" fields, defined in section CSV common field 2501 elements (Section 4.6.2.2), MAY be used in the "contactTransfer" 2502 element: 2504 Identifier of the client that requested the transfer. 2506 Identifier of the client that should take or took 2507 action for transfer. 2509 The following "csvContact" fields, defined for the "contact" CSV File 2510 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2511 element: 2513 Server-unique contact identifier for the contact 2514 object with isRequired="true". 2516 Example of a "contactTransfer" 2517 element. 2519 ... 2520 2521 ... 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2536 contactTransfer-YYYYMMDD.csv 2537 2538 2539 2540 ... 2541 2542 ... 2544 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2545 one contact transfer record in pending status. 2547 xnabc123admin,clientApproved,registrarX,clientX, 2548 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2550 5.3.2.1.5. "contactDisclose" CSV File Definition 2552 The "contactDisclose" CSV File Definition defines the fields and CSV 2553 file references used for the contact disclose object records. 2555 The following "csvContact" field elements MAY be used in the 2556 "contactDisclose" element: 2558 Contains flag with a value of "true" or 2559 "1" (one) notes the preference to allow disclosure of the 2560 specified elements as an exception to the stated data-collection 2561 policy. A value of "false" or "0" (zero) notes a client 2562 preference to not allow disclosure of the specified elements as an 2563 exception to the stated data-collection policy with 2564 type="boolean". The additional fields define specific exceptional 2565 disclosure preferences based on the 2566 field. 2568 Exceptional disclosure preference flag 2569 for the localized form of the contact name with type="boolean". 2571 Exceptional disclosure preference flag 2572 for the internationalized form of the contact name with 2573 type="boolean". 2575 Exceptional disclosure preference flag 2576 for the localized form of the contact organization with 2577 type="boolean". 2579 Exceptional disclosure preference flag 2580 for the internationalized form of the contact organization with 2581 type="boolean". 2583 Exceptional disclosure preference flag 2584 for the localized form of the contact address with type="boolean". 2586 Exceptional disclosure preference flag 2587 for the internationalized form of the contact address with 2588 type="boolean". 2590 Exceptional disclosure preference flag 2591 of the contact voice telephone number with type="boolean". 2593 Exceptional disclosure preference flag of 2594 the contact facsimile telephone number with type="boolean". 2596 Exceptional disclosure preference flag 2597 of the contact email address with type="boolean". 2599 The following "csvContact" fields, defined for the "contact" CSV File 2600 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2601 element: 2603 Server-unique contact identifier for the contact 2604 object with isRequired="true". 2606 Example of a "contactDisclose" 2607 element. 2609 ... 2610 2611 ... 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2629 contactDisclose-YYYYMMDD.csv 2630 2631 2632 2633 ... 2634 2635 ... 2637 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2638 one disclosure records, disabling disclosure of voice, fax, and 2639 email. 2641 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2643 5.3.2.2. 2645 The is used to hold the deleted contact objects 2646 in a Differential or Incremental Deposit. All the contact object 2647 data is deleted as part of a cascade delete. The 2648 is split into separate CSV file definitions 2649 using named elements with the "name" attribute. The 2650 following section defines the supported contact deletes CSV file 2651 definition. 2653 5.3.2.2.1. "contact" Deletes CSV File Definition 2655 The following "csvContact" field elements MUST be used in the deletes 2656 "contact" element: 2658 Contains the server-unique contact identifier with 2659 type="eppcom:clIDType" and isRequired="true". 2661 Example of a "contact" element. 2663 ... 2664 2665 ... 2666 2667 2668 2669 2670 2671 2673 contact-delete-YYYYMMDD.csv 2674 2675 2676 2677 ... 2678 2679 ... 2681 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2682 six contact records. 2684 domain1admin 2685 domain1tech 2686 domain1billing 2687 domain2admin 2688 domain2tech 2689 domain2billing 2691 5.4. Registrar Object 2693 The registrar object represents the sponsoring client for other 2694 objects, and is typically referred to as the sponsoring registrar. 2695 The registrar object supports both the XML Model and the CSV Model, 2696 defined in Section 2. The elements used for both models are defined 2697 in the following sections. 2699 5.4.1. XML Model 2701 There are two elements used in the data escrow of the registrar 2702 objects for the XML model including the , 2703 under the element, and the 2704 element, under the element. 2706 A element substitutes for the 2707 abstract element to define a 2708 concrete definition of a registrar. The 2709 element can be replaced by other 2710 domain definitions using the XML schema substitution groups feature. 2712 5.4.1.1. element 2714 The element contains the following child elements: 2716 o An element that contains the Registry-unique identifier of 2717 the registrar object. This has a superordinate relationship 2718 to a subordinate , or of domain, contact and 2719 host objects. 2721 o An element that contains the name of the registrar. 2723 o An OPTIONAL element that contains the ID assigned by 2724 ICANN. 2726 o An OPTIONAL element that contains the operational status 2727 of the registrar. Possible values are: ok, readonly and 2728 terminated. 2730 o One or two OPTIONAL elements that contain postal- 2731 address information. Two elements are provided so that address 2732 information can be provided in both internationalized and 2733 localized forms; a "type" attribute is used to identify the two 2734 forms. If an internationalized form (type="int") is provided, 2735 element content MUST be represented in a subset of UTF-8 that can 2736 be represented in the 7-bit US-ASCII character set. If a 2737 localized form (type="loc") is provided, element content MAY be 2738 represented in unrestricted UTF-8. The element 2739 contains the following child elements: 2741 * A element that contains address information associated 2742 with the registrar. The element contains the following 2743 child elements: 2745 + One, two, or three OPTIONAL elements that contain 2746 the registrar's street address. 2748 + A element that contains the registrar's city. 2750 + An OPTIONAL element that contains the registrar's state 2751 or province. 2753 + An OPTIONAL element that contains the registrar's 2754 postal code. 2756 + A element that contains the registrar's country code. 2758 o An OPTIONAL element that contains the registrar's voice 2759 telephone number. 2761 o An OPTIONAL element that contains the registrar's facsimile 2762 telephone number. 2764 o An OPTIONAL element that contains the registrar's email 2765 address. 2767 o An OPTIONAL element that contains the registrar's URL. 2769 o An OPTIONAL elements that contains whois information. 2770 The element contains the following child elements: 2772 * An OPTIONAL element that contains the name of the 2773 registrar WHOIS server listening on TCP port 43 as specified in 2774 [RFC3912]. 2776 * An OPTIONAL element that contains the name of the 2777 registrar WHOIS server listening on TCP port 80/443. 2779 o An OPTIONAL element that contains the date and time of 2780 registrar-object creation. 2782 o An OPTIONAL element that contains the date and time of 2783 the most recent RDE registrar-object modification. This element 2784 MUST NOT be present if the rdeRegistrar object has never been 2785 modified. 2787 Example of object: 2789 ... 2790 2791 RegistrarX 2792 Registrar X 2793 123 2794 ok 2795 2796 2797 123 Example Dr. 2798 Suite 100 2799 Dulles 2800 VA 2801 20166-6503 2802 US 2803 2804 2805 +1.7035555555 2806 +1.7035555556 2807 jdoe@example.example 2808 http://www.example.example 2809 2810 whois.example.example 2811 http://whois.example.example 2812 2813 2005-04-23T11:49:00.0Z 2814 2009-02-17T17:51:00.0Z 2815 2816 ... 2818 5.4.1.2. object 2820 The element contains the id of a registrar that 2821 was deleted. 2823 Example of object: 2825 ... 2826 2827 ... 2828 2829 agnt0001-TEST 2830 2831 ... 2832 2833 ... 2835 5.4.2. CSV Model 2837 For the CSV Model of the registrar object, the 2838 child element of the element 2839 is used to hold the new or updated registrar objects for the deposit. 2840 The child element of the element 2841 is used to hold the deleted or purged registrar objects for the 2842 deposit. Both the and 2843 elements contain one or more elements with a set of 2844 named CSV file definitions using the "name" attribute. 2846 Differential and Incremental Deposits are based on changes to the 2847 registrar objects. The updated registrar object data under the 2848 element is a cascade replace down all of the 2849 registrar CSV files starting with the parent "registrar" CSV File 2850 Definition (Section 5.4.2.1.1). The child CSV file definitions 2851 include a field. All the child CSV 2852 file definition data for the registrar objects in the parent 2853 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2854 deleted and then set using the data in the child CSV files. The 2855 deleted registrar object data under the 2856 element is a cascade delete starting from the "registrar" Deletes CSV 2857 File Definition (Section 5.4.2.2.1). 2859 5.4.2.1. 2861 The is used to hold the new or updated 2862 registrar object information for the deposit. The 2863 is split into separate CSV file definitions 2864 using named elements with the "name" attribute. The 2865 following sections include the supported contact CSV file 2866 definitions. 2868 5.4.2.1.1. "registrar" CSV File Definition 2870 The "registrar" CSV File Definition defines the fields and CSV file 2871 references used for the registrar object records. 2873 The following "csvRegistrar" field elements MUST be used in the 2874 "registrar" element: 2876 or A choice of: 2878 Contains the server-unique registrar 2879 identifier with type="eppcom:clIDType" and isRequired="true". 2881 Contains the ID assigned by ICANN with 2882 type="positiveInteger". The attribute "isRequired" MUST equal 2883 "true". 2885 Contains the name of the registrar with 2886 type="normalizedString" and isRequired="true". 2888 The following field elements MAY be used in the "registrar" 2889 element: 2891 Contains the status of the registrar with 2892 type="csvRegistrar:statusValueType". 2894 Contains the ID assigned by ICANN with 2895 type="positiveInteger". This field is included in this section in 2896 addition to the section above to support optionally providing the 2897 field when the field is 2898 used. 2900 Contains the Whois URL of the registrar 2901 with type="anyURI". 2903 The following "rdeCsv" fields, defined in section CSV common field 2904 elements (Section 4.6.2.2), MAY be used in the "registrar" 2905 element: 2907 Created date and time of the registrar object. 2909 Date and time of the last update to the registrar 2910 object. 2912 URL for the registrar web home page. 2914 The following "csvContact" fields, defined in section Contact Object 2915 (Section 5.3), MAY be used in the "registrar" 2916 element: 2918 Registrar street address line with an "index" 2919 attribute that represents the order of the street address line 2920 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2921 indicate the localized or internationalized form, as defined in 2922 Section 4.6.3. 2924 Registrar city with an OPTIONAL "isLoc" attribute 2925 that is used to indicate the localized or internationalized form, 2926 as defined in Section 4.6.3. 2928 Registrar country code with an OPTIONAL "isLoc" 2929 attribute that is used to indicate the localized or 2930 internationalized form, as defined in Section 4.6.3. 2932 Registrar email address. The attribute 2933 "isRequired" MUST equal "false". 2935 Registrar state or province with an OPTIONAL 2936 "isLoc" attribute that is used to indicate the localized or 2937 internationalized form, as defined in Section 4.6.3. 2939 Registrar postal code with an OPTIONAL "isLoc" 2940 attribute that is used to indicate the localized or 2941 internationalized form, as defined in Section 4.6.3. 2943 Registrar voice telephone number. 2945 Registrar voice telephone number extension. 2947 Registrar facsimile telephone number. 2949 Registrar facsimile telephone number extension. 2951 Example of a "registrar" 2952 element. 2954 ... 2955 2956 ... 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2983 registrar-YYYYMMDD.csv 2984 2985 2986 2987 ... 2988 2989 ... 2991 Example of the registrar-YYYYMMDD.csv file. The file contains three 2992 registrar records. 2994 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 2995 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2996 +1.7035555556,,jdoe@example.example,http://www.example.example, 2997 http://whois.example.example,2005-04-23T11:49:00.0Z, 2998 2009-02-17T17:51:00.0Z 2999 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 3000 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3001 +1.7035555556,,jdoe@example.example,http://www.example.example, 3002 http://whois.example.example,2005-04-23T11:49:00.0Z, 3003 2009-02-17T17:51:00.0Z 3004 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 3005 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3006 +1.7035555556,,jdoe@example.example,http://www.example.example, 3007 http://whois.example.example,2005-04-23T11:49:00.0Z, 3008 2009-02-17T17:51:00.0Z 3010 5.4.2.2. 3012 The is used to hold the deleted registrar 3013 objects in a Differential or Incremental Deposit. All the registrar 3014 object data is deleted as part of a cascade delete. The 3015 is split into separate CSV file definitions 3016 using named elements with the "name" attribute. The 3017 following section defines the supported registrar deletes CSV file 3018 definition. 3020 5.4.2.2.1. "registrar" Deletes CSV File Definition 3022 The following "csvRegistrar" field elements MUST be used in the 3023 deletes "registrar" element: 3025 or A choice of: 3027 Contains the server-unique registrar 3028 identifier with type="eppcom:clIDType" and isRequired="true". 3030 Contains the ID assigned by ICANN with 3031 type="positiveInteger". The attribute "isRequired" MUST equal 3032 "true". 3034 Example of a "registrar" element. 3036 ... 3037 3038 ... 3039 3040 3041 3042 3043 3044 3046 registrar-delete-YYYYMMDD.csv 3047 3048 3049 3050 ... 3051 3052 ... 3054 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 3055 one registrar record. 3057 registrarZ 3059 5.5. IDN Table Reference Object 3061 The Internationalized Domain Names (IDN) table reference object is a 3062 pseudo-object that is used to provide a short reference to the IDN 3063 Table and Policy used in IDN registrations. The IDN reference object 3064 supports both the XML and the CSV Model, defined in the Models 3065 (Section 2) section. The elements used for both models are defined 3066 in the following sections. 3068 5.5.1. XML Model 3070 There is one element used in the data escrow of the IDN table 3071 reference objects for the XML model that is the , 3072 under the element. 3074 5.5.1.1. object 3076 The contains the following elements. An "id" 3077 attribute is used to specify an identifier for the IDN table. 3079 o An element that contains the URL of the IDN table that is 3080 being referenced. 3082 o A element that contains the URL of the IDN policy 3083 document. If IDN variants are generated algorithmically, the 3084 policy document MUST define the algorithm and the state of the 3085 implicit generated IDN variants. For a list of suggested states 3086 for implicit IDN variants, please see [variantTLDsReport]. 3088 Example of object: 3090 ... 3091 3092 3093 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3094 3095 3096 http://registro.br/dominio/regras.html 3097 3098 3099 ... 3101 5.5.2. CSV Model 3103 The IDN domain names, defined in Section 5.1, MAY have references to 3104 the IDN language identifier using the field 3105 element. The IDN table reference object defines the mapping of a 3106 language identifier to a language table URL. The language table URL 3107 defines the character code points that can be used for the language 3108 identifier. The elements used for the IDN table reference object is 3109 defined in this section. The child element of the 3110 element is used to hold the new or updated IDN table 3111 reference objects for the deposit. The child 3112 element of the element is used to hold the deleted or 3113 purged IDN table reference objects for the deposit. Both the 3114 and elements contain one or more 3115 elements with a set of named CSV file definitions using 3116 the "name" attribute. 3118 5.5.2.1. 3120 The is used to hold the new or updated IDN table 3121 reference object information for the deposit. The 3122 is split into separate CSV file definitions using named 3123 elements with the "name" attribute. The following sections include 3124 the supported IDN table reference CSV file definitions. 3126 5.5.2.1.1. "idnLanguage" CSV File Definition 3128 The "idnLanguage" CSV File Definition defines the fields and CSV file 3129 references used for the IDN table reference object records. 3131 The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be 3132 used in the "idnLanguage" element: 3134 The language identifier that matches the values 3135 for the field element in the "domain" CSV 3136 File Definition (Section 5.1.2.1.1) files. The attribute 3137 "isRequired" MUST equal "true". 3139 URL that defines the character code points that can be 3140 used for the language defined by the field element. 3141 The attribute "isRequired" MUST equal "true". 3143 Example of a "idnLanguage" element. 3145 ... 3146 3147 ... 3148 3149 3150 3151 3152 3153 3154 3156 idnLanguage-YYYYMMDD.csv 3157 3158 3159 3160 ... 3161 3162 ... 3164 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3165 contains two IDN language records. 3167 LANG-1, 3168 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3169 LANG-2, 3170 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3172 5.5.2.2. 3174 The is used to hold the deleted IDN table reference 3175 objects in a Differential or Incremental Deposit. The 3176 is split into separate CSV file definitions using 3177 named elements with the "name" attribute. The following 3178 section defines the supported IDN table reference deletes CSV file 3179 definition. 3181 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3183 The following "idnLanguage" field elements MUST be used in the 3184 deletes "idnLanguage" element: 3186 The language identifier that matches the values 3187 for the field element in the "domain" CSV 3188 File Definition (Section 5.1.2.1.1) files. The attribute 3189 "isRequired" MUST equal "true". 3191 Example of a "idnLanguage" element. 3193 ... 3194 3195 ... 3196 3197 3198 3199 3200 3201 3203 idnLanguage-delete-YYYYMMDD.csv 3204 3205 3206 3207 ... 3208 3209 ... 3211 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3212 contains one IDN language record. 3214 LANG-2 3216 5.6. NNDN Object 3218 An NNDN (NNDN's not domain name) can be used to store registry 3219 reserved names or (blocked, withheld or mirrored) IDN variants. 3221 Domain Name Registries may maintain domain names without their being 3222 persisted as domain objects in the registry system, for example, a 3223 list of reserved names not available for registration. The NNDN is a 3224 lightweight domain-like object that is used to escrow domain names 3225 not maintained as domain name objects. 3227 A domain name can only exist as a domain name object or an NNDN 3228 object, but not both. 3230 The NNDN object supports both the XML and the CSV Model, defined in 3231 the Models (Section 2) section. The elements used for both models 3232 are defined in the following sections. 3234 5.6.1. XML Model 3236 There are two elements used in the data escrow of the NNDN objects 3237 for the XML model including the , under the 3238 element, and the element, under the 3239 element. 3241 A element substitutes for the 3242 abstract element to define a concrete definition of an NNDN. The 3243 element can be replaced by other NNDN 3244 definitions using the XML schema substitution groups feature. 3246 5.6.1.1. object 3248 The element contains the following child elements: 3250 o An element that contains the fully qualified name of the 3251 NNDN. For IDNs the A-Label is used (see [RFC5891], Section 4.4). 3253 o An OPTIONAL element that contains the fully qualified name 3254 of the NNDN in Unicode character set. It MUST be provided if 3255 available. 3257 o An OPTIONAL element that references the IDN 3258 Table used for the NNDN. This corresponds to the "id" attribute 3259 of the element. This element MUST be present if the 3260 NNDN is an IDN. 3262 o An OPTIONAL element is used to indicate that the 3263 NNDN is used for an IDN variant. This element contains the domain 3264 name used to generate the IDN variant. 3266 o A element that indicates the state of the NNDN: 3267 blocked, withheld or mirrored. 3269 * If an NNDN is considered undesirable for registration (i.e., 3270 unavailable for allocation to anyone), then the NNDN will be 3271 tagged as "blocked". 3273 * If an NNDN is considered a potential registration of a domain 3274 object for a registrant, then the NNDN will be tagged as 3275 "withheld". This status is only used when the NNDN is used for 3276 an IDN variant. 3278 * If an NNDN is considered a mirrored IDN variant of a domain 3279 object, then the NNDN will be tagged as "mirrored". A 3280 mirroringNS attribute is used to specify if the mirrored IDN 3281 variant use the NS mirror mechanism. The default value of 3282 mirroringNS is true. If another mechanism such as DNAME is 3283 used, the value of mirroringNS attribute MUST be false. 3285 o An OPTIONAL element that contains the date and time of 3286 the NNDN object creation. 3288 Example of an object: 3290 ... 3291 3292 xn--exampl-gva.example 3293 pt-BR 3294 example.example 3295 withheld 3296 2005-04-23T11:49:00.0Z 3297 3298 ... 3300 5.6.1.2. object 3302 The element contains the NNDN that was deleted, 3303 i.e., the . 3305 Example of an object: 3307 ... 3308 3309 ... 3310 3311 xn--pingino-q2a.example 3312 3313 ... 3314 3315 ... 3317 5.6.2. CSV Model 3319 For the CSV Model of the NNDN object, the child 3320 element of the element is used to hold the new or 3321 updated NNDN objects for the deposit. The child 3322 element of the element is used to hold the deleted or 3323 purged NNDN objects for the deposit. Both the and 3324 elements contain one or more elements 3325 with a set of named CSV file definitions using the 3326 "name" attribute. 3328 5.6.2.1. 3330 The is used to hold the new or updated NNDN object 3331 information for the deposit. The is split into 3332 separate CSV file definitions using named elements with 3333 the "name" attribute. The following sections include the supported 3334 NNDN CSV file definitions. 3336 5.6.2.1.1. "NNDN" CSV File Definition 3338 The "NNDN" CSV File Definition defines the fields and CSV file 3339 references used for the NNDN object records. 3341 The following "csvNNDN" field elements MUST be used in the "NNDN" 3342 element: 3344 Fully qualified name of the NNDN with 3345 type="eppcom:labelType" and isRequired="true". For IDNs the 3346 A-Label is used (see [RFC5891], Section 4.4). 3348 State of the NNDN: blocked or withheld with 3349 type="rdeNNDN:nameState" and isRequired="true". See 3350 Section 5.6.1.1 for a description of the possible values for the 3351 element. 3353 The following field elements MAY be used in the "NNDN" 3354 element: 3356 Domain name used to generate the IDN variant 3357 with type="eppcom:labelType". 3359 Defines whether the "mirroring" 3360 uses the NS mirror mechanism, as described 3361 for the "mirroringNS" attribute in 3362 Section 5.6.1.1, with type="boolean". If the field element is not 3363 defined the default value is "true". 3365 The following "rdeCsv" fields, defined in section CSV common field 3366 elements (Section 4.6.2.2), MAY be used in the "NNDN" 3367 element: 3369 Created date and time of the NNDN object. 3371 Name of the NNDN in Unicode character set for the 3372 field element. 3374 IDN Table Identifier for the NNDN that matches 3375 an IDN Table Reference Object record, as defined in Section 5.5.2. 3377 Example of an "NNDN" element: 3379 ... 3380 3381 ... 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3394 NNDN-YYYYMMDD.csv 3395 3396 3397 3398 ... 3399 3400 ... 3402 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3403 contains two NNDN records for an IDN with one blocked variant and one 3404 mirrored variant. 3406 xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example, 3407 blocked,,2005-04-23T11:49:00.0Z 3408 xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example, 3409 mirrored,1,2005-04-23T11:49:00.0Z 3411 5.6.2.2. 3413 The is used to hold the deleted NNDN objects in a 3414 Differential or Incremental Deposit. The is split 3415 into separate CSV file definitions using named elements 3416 with the "name" attribute. The following section defines the 3417 supported NNDN deletes CSV file definition. 3419 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3421 The following "NNDN" field elements MUST be used in the deletes 3422 "NNDN" element: 3424 Fully qualified name of the NNDN with 3425 type="eppcom:labelType" and isRequired="true". 3427 Example of an "NNDN" element. 3429 ... 3430 3431 ... 3432 3433 3434 3435 3436 3437 3439 NNDN-delete-YYYYMMDD.csv 3440 3441 3442 3443 ... 3444 3445 ... 3447 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3448 contains one NNDN records. 3450 xn--bc456-3ve.example 3452 5.7. EPP Parameters Object 3454 The EPP Parameters Object is a pseudo-object that defines the set of 3455 object and object extension services supported by the registry, as 3456 defined in [RFC5730]. The EPP Parameters Object is only defined as 3457 XML but could be used in the XML model or CSV model. The EPP 3458 Parameters Object is defined using the 3459 element. The EPP Parameters Object SHOULD be included if the 3460 registry supports EPP. Only one EPP Parameters Object MUST exist at 3461 a certain point in time (watermark). 3463 The syntax and content of the children 3464 elements is as explained in section 2.4 of [RFC5730]. The children 3465 of the are as follows: 3467 o One or more elements that indicate the EPP versions 3468 supported by the registry. 3470 o One or more elements that indicate the identifiers of the 3471 text response languages supported by the registry's EPP server. 3473 o One or more elements that contain namespace URIs 3474 representing the objects that the registry's EPP server is capable 3475 of managing. 3477 o An OPTIONAL element that contains one or more 3478 elements that contain namespace URIs representing object 3479 extensions supported by the registry's EPP server. 3481 o A element that contains child elements used to describe the 3482 server's privacy policy for data collection and management. See 3483 section 2.4 of [RFC5730] for more details. 3485 Example of element object: 3487 ... 3488 3489 1.0 3490 en 3491 urn:ietf:params:xml:ns:domain-1.0 3492 3493 urn:ietf:params:xml:ns:contact-1.0 3494 3495 urn:ietf:params:xml:ns:host-1.0 3496 3497 3498 urn:ietf:params:xml:ns:rgp-1.0 3499 urn:ietf:params:xml:ns:secDNS-1.1 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 ... 3520 5.8. Policy Object 3522 The Policy object is a pseudo-object that is used to specify which 3523 OPTIONAL elements from the XML Model are REQUIRED based on the 3524 business model of the registry. For the CSV Model, the OPTIONAL 3525 "isRequired" attribute of the elements, defined in 3526 Section 4.6.2.1, is used to specify which OPTIONAL fields are 3527 REQUIRED based on the business model of the registry. 3529 5.8.1. object 3531 The OPTIONAL contains the following attributes: 3533 o An that defines that the referenced is 3534 REQUIRED. 3536 o that defines the XPath of the element referenced by 3537 . 3539 Example of object: 3541 ... 3542 3544 ... 3546 5.9. Header Object 3548 The Header Object is a pseudo-object that is used to specify the 3549 number of objects in the repository at a specific point in time 3550 (watermark) regardless of the type of deposit: Differential, Full or 3551 Incremental Deposit. The Header Object may also be used to provide 3552 additional information on the contents of the deposit. The Header 3553 Object is only defined as XML but one header object MUST always be 3554 present per escrow deposit regardless of using XML Model or CSV 3555 Model. The Header Object is defined using the 3556 element. 3558 5.9.1. object 3560 The contains the following elements: 3562 o A choice of one of the elements defined in the 3563 "repositoryTypeGroup" group element that indicates the unique 3564 identifier for the repository being escrowed. Possible elements 3565 are: 3567 * A element that defines TLD or the REGISTRY- 3568 CLASS DOMAIN NAME (RCDN) being escrowed in the case of a 3569 Registry data escrow deposit. For IDNs the A-Label is used 3570 (see [RFC5891], Section 4.4). 3572 * A element that defines the Registrar ID 3573 corresponding to a Registrar data escrow deposit. In the case 3574 of an ICANN-accredited Registrar, the 3575 element MUST be the IANA Registrar ID assigned by ICANN. 3577 * A element that defines the provider ID 3578 corresponding to a Privacy and Proxy Services Provider data 3579 escrow deposit. In the case of an ICANN-accredited Privacy and 3580 Proxy Services Provider, the element MUST be 3581 the unique ID assigned by ICANN. 3583 * A element that defines the provider ID 3584 corresponding to a Reseller data escrow deposit. 3586 o A element that contains the number of objects in the SRS 3587 at a specific point in time (watermark) regardless of the type of 3588 deposit: Differential, Full or Incremental. The element 3589 supports the following attributes: 3591 * A "uri" attribute reflects the XML namespace URI of the primary 3592 objects for the XML Model and CSV Model. For example, the 3593 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3594 domain name objects using the XML Model, and the "uri" is set 3595 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3596 objects using the CSV Model. 3598 * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS 3599 DOMAIN NAME (RCDN) of the objects included in the 3600 element. For IDNs the A-Label is used [RFC5891], Section 4.4. 3601 If the "rcdn" attribute is present, the value of the 3602 element must include only objects related to registrations in 3603 the same and lower levels. For example in a data escrow 3604 deposit for the .EXAMPLE TLD, a value of "example" in the 3605 "rcdn" attribute within the element indicates the 3606 number of objects in the TLD including objects in other RCDNs 3607 within the TLD, whereas a value of "com.example" indicates the 3608 number of elements for objects under "com.example" and lower 3609 levels. Omitting the "rcdn" attribute indicates that the total 3610 includes all objects of the specified "uri" in the repository 3611 (e.g. the TLD, Registrar, or PPSP). 3613 * An OPTIONAL "registrarId" attribute indicates the identifier of 3614 the sponsoring Registrar of the objects included in the 3615 element. In the case of an ICANN-accredited Registrar, the 3616 value MUST be the IANA Registrar ID assigned by ICANN. 3618 o An OPTIONAL element that contains a tag that defines 3619 the expected content in the deposit. The producer and consumer of 3620 the deposits will coordinate the set of possible 3621 element values. 3623 Example of object referencing only the XML Model 3624 objects: 3626 ... 3627 3628 test 3629 2 3631 1 3633 1 3635 1 3637 3638 1 3640 1 3642 1 3644 3645 3646 ... 3648 Example of object referencing the CSV and XML 3649 Model objects: 3651 ... 3652 3653 test 3654 2 3656 1 3658 1 3660 1 3662 3663 1 3665 1 3667 1 3669 3670 3671 ... 3673 5.10. DNRD Common Objects Collection 3675 The DNRD Common Objects Collection contains data structures 3676 referenced by two or more of the main objects in the XML model. 3678 6. RDE IDN Variants handling 3680 Depending on the Registration Policy of the Registry, for a domain 3681 name there may be multiple variant names. See [variantTLDsReport] 3682 for further detail on IDN variants. 3684 A registry could choose to escrow IDN variants as domains or NNDN 3685 objects. A specific IDN variant can be represented in the escrow 3686 deposit, as a domain or as an NNDN object, but not both. 3688 If using domain objects to represent IDN variants, the normal 3689 behavior during restoration of an SRS based on an escrow deposit is 3690 to restore the IDN variants as a mirrored variant. If the 3691 registration data of the IDN variant is different from the original 3692 name, the details of this specific implementation MUST be described 3693 in the IDN policy document. 3695 An NNDN or a domain name are explicit representations of an IDN 3696 variant while an IDN variant computed based on an algorithm is an 3697 implicit representation. Explicit representation of an IDN variant 3698 takes precedence over an implicit representation. 3700 7. Profile 3702 Different business models of registries exist, therefore the registry 3703 is responsible for defining a profile that matches its particular 3704 business model. The profile mechanism allows a registry to extend 3705 this specification. 3707 A profile is the process of: 3709 1. Extending base objects with the mechanisms defined for XML and 3710 CSV models. 3712 * In the case of the XML model, abstract elements could be use 3713 to extend the following objects: , , , 3714 and using XML schema substitution groups 3715 feature. 3717 2. Defining a object to specify which OPTIONAL elements of 3718 this base specification is required based on the business model 3719 of the registry. An example is the element that is 3720 usually REQUIRED but it is specified as OPTIONAL in this 3721 specification to support some existing business models. 3723 3. Adding new escrowed objects using the and 3724 elements. 3726 4. Providing the XML schemas to third parties that require them to 3727 validate the escrow deposits. 3729 8. Data escrow agent extended verification process 3731 A Data Escrow Agent SHOULD perform an extended verification process 3732 that starts by creating a dataset to be tested. 3734 o If a Full Deposit is to be tested, the Full Deposit is the 3735 dataset. 3737 o If an Incremental Deposit is to be tested, the dataset is created 3738 by using the Incremental Deposit plus the last previous Full 3739 Deposit. 3741 o If a Differential Deposit is to be tested, the dataset is created 3742 by using the Differential Deposit plus all the required deposits 3743 leading to the last previous Full Deposit. 3745 The following are the minimum suggested tests on the dataset: 3747 o Validate the escrow deposits using the definition agreed with the 3748 registry. 3750 * In the case of the XML model, the contents of the escrow 3751 deposits MUST be validated using the XML schemas of the 3752 profile. 3754 o Count the objects and validate that the number of objects is equal 3755 to the number objects reported in the
element of the 3756 escrow deposit of that point in time (watermark). 3758 o All contact objects linked to domain names MUST be present. 3760 o All registrars objects linked to other objects MUST be present. 3762 o No domain name exists as both a domain name and an NNDN. 3764 o The elements listed as required in the element MUST be 3765 present. 3767 o All idnTableRef definitions linked from other objects MUST be 3768 present. 3770 o If an EPP Parameters Object was escrowed in the past, one and only 3771 one EPP Parameters Object MUST be present. 3773 o The watermark is not in the future. 3775 9. Formal Syntax 3777 This standard is specified in XML Schema notation. The formal syntax 3778 presented here is a complete schema representation suitable for 3779 automated validation. 3781 The BEGIN and END tags are not part of the schema; they are used to 3782 note the beginning and ending of the schema for URI registration 3783 purposes. 3785 9.1. RDE CSV Schema 3787 BEGIN 3788 3790 3797 3800 3801 3803 3804 3805 Registry Data Escrow Comma-Seperated Values (CSV) 3806 3807 3809 3810 3812 3813 3814 3815 3816 3817 3818 3819 3820 3822 3823 3824 3825 3826 3827 3828 3830 3831 3834 3835 3836 3838 3839 3840 3841 3842 3843 3845 3847 3848 3849 3851 3852 3853 3854 3855 3856 3858 3860 3861 3862 3864 3866 3867 3869 3870 3871 3872 3873 3875 3876 3877 3878 3879 3880 3881 3882 3884 3885 3886 3888 3889 3891 3892 3893 3894 3895 3897 3898 3899 3901 3902 3904 3905 3906 3907 3908 3910 3911 3912 3914 3915 3919 3920 3921 3923 3925 3927 3928 3930 3932 3934 3935 3937 3939 3941 3943 3945 3947 3949 3951 3953 3954 3955 3956 3957 3959 3960 3961 3962 3963 3964 3965 3966 3968 3969 3970 3972 3973 3976 3978 3980 3981 3983 3984 3986 3988 3989 3990 3991 3992 3994 3995 3996 3997 3998 3999 4000 4001 4003 4004 4005 4007 4008 4009 4010 4011 4012 4014 4015 4016 4017 4018 4019 4020 4021 4024 4025 4026 4028 4029 4030 4031 4032 4033 4035 4036 4037 4038 4039 4040 4041 4042 4044 4045 4046 4048 4049 4050 4051 4052 4053 4055 4056 4057 4058 4059 4060 4061 4062 4064 4065 4066 4068 4069 4070 4071 4072 4073 4075 4076 4077 4078 4079 4080 4081 4082 4084 4085 4086 4088 4089 4091 4092 4093 4094 4095 4097 4098 4099 4101 4102 4105 4106 4108 4109 4110 4111 4112 4114 4115 4116 4117 4118 4119 4120 4121 4122 4124 4125 4126 4128 4129 4130 4131 4132 4133 4135 4136 4137 4139 4140 4141 4142 4143 4144 4146 4147 4148 4150 4151 4153 4154 4155 4156 4157 4158 4160 4161 4162 4164 4165 4166 4167 4168 4169 4171 4172 4173 4174 4176 4177 4179 4180 4181 4182 4183 4184 4186 4187 4188 4189 4191 4192 4194 4195 4196 4197 4198 4200 4201 4202 4204 4207 4208 END 4210 9.2. RDE Domain Object 4212 BEGIN 4213 4214 4226 4227 4228 4229 4230 4231 4232 4234 4235 4236 Registry Data Escrow Domain provisioning schema 4237 4238 4240 4243 4245 4249 4250 4251 4252 4253 4254 4256 4258 4260 4262 4264 4266 4269 4271 4274 4276 4278 4280 4282 4284 4286 4288 4290 4292 4295 4296 4297 4298 4300 4301 4302 4304 4306 4308 4310 4312 4314 4315 4317 4318 4319 4320 4321 4322 4325 4326 4327 4328 4329 4330 END 4332 9.3. CSV Domain Object 4334 BEGIN 4335 4337 4348 4351 4352 4353 4354 4355 4356 4358 4359 4360 Domain Name Comma-Separated Values (CSV) Object 4361 4362 4364 4367 4370 4371 4372 4373 4374 4375 4376 4377 4378 4380 4383 4386 4387 4388 4389 4390 4391 4392 4393 4394 4396 4397 4400 4401 4404 4405 4406 4407 4408 4410 4411 4412 4414 4415 4418 4419 4420 4421 4422 4424 4425 4426 4428 4430 4431 4433 4434 4435 4436 4437 4439 4440 4441 4443 4444 4447 4448 4451 4452 4455 4456 4459 4460 4463 4464 4467 4468 4471 4472 4474 4475 4476 4477 4478 4480 4481 4482 4484 4485 4488 4489 4493 4494 4497 4498 4499 4500 4501 4502 4504 4505 4506 4508 4511 4512 END 4514 9.4. RDE Host Object 4516 BEGIN 4517 4518 4527 4528 4529 4530 4532 4533 4534 Registry Data Escrow Host provisioning schema 4535 4536 4538 4540 4541 4544 4545 4546 4547 4548 4549 4551 4553 4555 4558 4560 4562 4564 4566 4568 4570 4571 4572 4573 4575 4576 4577 4578 4579 4580 4582 4584 4585 4586 4587 4588 4589 END 4591 9.5. CSV Host Object 4593 BEGIN 4594 4596 4605 4608 4609 4610 4611 4613 4614 4615 Host Comma-Separated Values (CSV) Object 4616 4617 4619 4622 4625 4626 4627 4628 4629 4630 4631 4632 4633 4635 4638 4641 4642 4643 4644 4645 4646 4647 4648 4649 4651 4652 4655 4656 4658 4659 4660 4661 4662 4664 4665 4666 4668 4669 4671 4672 4673 4674 4675 4677 4678 4679 4681 4682 4685 4686 4687 4688 4689 4690 4692 4693 4694 4696 4699 4700 END 4702 9.6. RDE Contact Object 4704 BEGIN 4705 4706 4715 4716 4717 4718 4719 4721 4722 4723 Registry Data Escrow contact provisioning schema 4724 4725 4727 4730 4732 4736 4737 4738 4739 4740 4741 4743 4745 4747 4749 4751 4753 4755 4757 4759 4761 4763 4765 4767 4769 4771 4772 4773 4774 4776 4777 4778 4779 4780 4781 4782 4783 4784 4786 4787 4788 4789 4790 4791 4794 4795 4796 4797 4798 4799 END 4801 9.7. CSV Contact Object 4803 BEGIN 4804 4806 4815 4818 4819 4820 4821 4823 4824 4825 Contact Comma-Separated Values (CSV) Object 4826 4827 4828 4831 4834 4835 4836 4837 4838 4839 4840 4841 4842 4844 4847 4850 4851 4852 4853 4854 4855 4856 4857 4858 4860 4861 4863 4864 4865 4866 4867 4869 4870 4871 4873 4874 4878 4879 4881 4883 4884 4885 4886 4887 4889 4890 4891 4893 4894 4896 4899 4900 4902 4903 4904 4905 4906 4908 4909 4910 4912 4916 4918 4919 4920 4921 4922 4924 4925 4926 4928 4929 4930 4931 4932 4933 4935 4936 4937 4938 4940 4941 4942 4943 4944 4945 4947 4948 4949 4950 4952 4953 4956 4957 4960 4961 4962 4964 4965 4966 4967 4968 4970 4971 4972 4974 4975 4978 4979 4982 4983 4985 4986 4987 4988 4989 4991 4992 4993 4994 4996 4997 4999 5000 5001 5002 5003 5005 5006 5007 5008 5010 5011 5014 5016 5018 5020 5022 5024 5026 5028 5030 5032 5034 5036 5038 5040 5042 5044 5046 5048 5050 5052 5053 5054 5055 5056 5058 5059 5060 5061 5062 5065 5066 5067 5068 5069 5070 5072 5073 5074 5076 5079 5080 END 5082 9.8. RDE Registrar Object 5084 BEGIN 5085 5086 5095 5096 5097 5098 5099 5101 5102 5103 Registry Data Escrow registrar provisioning schema 5104 5105 5107 5110 5112 5115 5116 5117 5118 5119 5120 5122 5124 5126 5128 5131 5133 5135 5137 5139 5141 5143 5145 5146 5147 5148 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5164 5165 5166 5168 5169 5172 5174 5175 5176 5177 5178 5179 5181 5182 5183 5186 5188 5191 5193 5195 5196 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5210 5211 5212 5213 5214 5216 5217 5218 5219 5220 5222 5223 5224 5226 5228 5229 5231 5232 5233 5234 5235 5236 5239 5240 5241 5242 5243 5244 END 5246 9.9. CSV Registrar Object 5248 BEGIN 5249 5251 5261 5264 5265 5266 5267 5268 5270 5271 5272 Registar Comma-Separated Values (CSV) Object 5273 5274 5276 5279 5282 5283 5284 5285 5286 5287 5288 5289 5290 5292 5295 5298 5299 5300 5301 5302 5303 5304 5305 5306 5308 5309 5312 5313 5316 5317 5318 5319 5320 5321 5323 5324 5325 5326 5328 5329 5333 5334 5336 5338 5339 5340 5341 5342 5344 5345 5347 5349 5350 5351 5352 5353 5354 5355 5356 5358 5359 5360 5361 5362 5363 5364 5365 5367 5368 5372 5375 5376 END 5378 9.10. RDE IDN Table Reference Objects 5380 BEGIN 5381 5382 5388 5390 5391 5392 Registry Data Escrow IDN provisioning schema 5393 5395 5397 5399 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5415 5416 5417 5418 5419 5420 5421 5422 5423 5425 5426 5427 5428 5429 5430 5431 5433 5434 END 5436 9.11. CSV IDN Language Object 5438 BEGIN 5439 5441 5448 5451 5452 5454 5455 5456 IDN Language Comma-Separated Values (CSV) Object 5457 5458 5460 5463 5466 5467 5468 5469 5470 5471 5472 5473 5474 5476 5479 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5494 5495 END 5497 9.12. EPP Parameters Object 5499 BEGIN 5500 5501 5509 5510 5511 5513 5514 5515 Registry Data Escrow EPP Parameters schema 5516 5517 5519 5520 5523 5524 5527 5528 5529 5530 5531 5533 5535 5537 5540 5542 5543 5544 5545 5546 5547 END 5549 9.13. NNDN Object 5551 BEGIN 5552 5553 5561 5562 5563 5565 5566 5567 Registry Data Escrow NNDN provisioning schema 5568 5569 5571 5573 5574 5577 5578 5579 5580 5581 5582 5584 5586 5588 5590 5592 5594 5595 5596 5597 5599 5600 5601 5602 5603 5604 5605 5607 5608 5609 5610 5612 5613 5614 5616 5617 5618 5619 5620 5621 5624 5625 5626 5627 5628 5629 END 5631 9.14. CSV NNDN Object 5633 BEGIN 5634 5636 5644 5647 5648 5649 5651 5652 5653 NNDN (NNDN's not domain name) (CSV) Object 5654 5655 5657 5660 5663 5664 5665 5666 5667 5668 5669 5670 5671 5673 5676 5678 5679 5680 5681 5682 5683 5684 5685 5686 5688 5689 5692 5693 5696 5697 5701 5702 5705 5706 5707 5708 5709 5711 5712 5713 5715 5716 5720 5723 5724 END 5726 9.15. Policy Object 5728 BEGIN 5729 5730 5736 5737 5738 Registry Data Escrow Policy schema 5739 5740 5742 5743 5746 5747 5748 5749 5750 5751 5752 5753 5754 5755 END 5757 9.16. Header Object 5759 BEGIN 5760 5761 5768 5769 5771 5772 5773 Data Escrow Deposit Header schema 5775 5776 5778 5779 5782 5783 5784 5785 5786 5787 5788 5790 5792 5793 5794 5795 5797 5798 5799 5800 5801 5802 5803 5804 5806 5807 5808 5809 5810 5811 5812 5813 5814 5816 5817 END 5819 9.17. DNRD Common Objects 5821 BEGIN 5822 5823 5829 5831 5832 5833 Data Escrow Deposit Common Objects schema 5834 5835 5837 5838 5839 5840 5841 5842 5843 5845 5846 END 5848 10. Internationalization Considerations 5850 Data Escrow deposits are represented in XML, which provides native 5851 support for encoding information using the Unicode character set and 5852 its more compact representations including UTF-8. Conformant XML 5853 processors recognize both UTF-8 and UTF-16. Though XML includes 5854 provisions to identify and use other character encodings through use 5855 of an "encoding" attribute in an declaration, use of UTF-8 is 5856 RECOMMENDED. 5858 11. IANA Considerations 5860 This document uses URNs to describe XML namespaces and XML schemas 5861 conforming to a registry mechanism described in [RFC3688]. Fourteen 5862 URI assignments have been registered by the IANA. 5864 Registration request for the RDE CSV namespace: 5866 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 5867 Registrant Contact: IESG 5869 Note to RFC Editor: Please remove the email address from the RFC 5870 after IANA records it. 5872 XML: None. Namespace URIs do not represent an XML specification. 5874 Registration request for the RDE CSV XML schema: 5876 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 5878 Registrant Contact: IESG 5880 Note to RFC Editor: Please remove the email address from the RFC 5881 after IANA records it. 5883 See section Section 9.1 of this document. 5885 Registration request for the RDE domain namespace: 5887 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 5889 Registrant Contact: IESG 5891 Note to RFC Editor: Please remove the email address from the RFC 5892 after IANA records it. 5894 XML: None. Namespace URIs do not represent an XML specification. 5896 Registration request for the RDE domain XML schema: 5898 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 5900 Registrant Contact: IESG 5902 Note to RFC Editor: Please remove the email address from the RFC 5903 after IANA records it. 5905 See section Section 9.2 of this document. 5907 Registration request for the CSV domain namespace: 5909 URI: urn:ietf:params:xml:ns:csvDomain-1.0 5911 Registrant Contact: IESG 5913 Note to RFC Editor: Please remove the email address from the RFC 5914 after IANA records it. 5916 XML: None. Namespace URIs do not represent an XML specification. 5918 Registration request for the CSV domain XML schema: 5920 URI: urn:ietf:params:xml:schema:csvDomain-1.0 5922 Registrant Contact: IESG 5924 Note to RFC Editor: Please remove the email address from the RFC 5925 after IANA records it. 5927 See section Section 9.3 of this document. 5929 Registration request for the RDE host namespace: 5931 URI: urn:ietf:params:xml:ns:rdeHost-1.0 5933 Registrant Contact: IESG 5935 Note to RFC Editor: Please remove the email address from the RFC 5936 after IANA records it. 5938 XML: None. Namespace URIs do not represent an XML specification. 5940 Registration request for the RDE host XML schema: 5942 URI: urn:ietf:params:xml:schema:rdeHost-1.0 5944 Registrant Contact: IESG 5946 Note to RFC Editor: Please remove the email address from the RFC 5947 after IANA records it. 5949 See section Section 9.4 of this document. 5951 Registration request for the CSV host namespace: 5953 URI: urn:ietf:params:xml:ns:csvHost-1.0 5955 Registrant Contact: IESG 5957 Note to RFC Editor: Please remove the email address from the RFC 5958 after IANA records it. 5960 XML: None. Namespace URIs do not represent an XML specification. 5962 Registration request for the CSV host XML schema: 5964 URI: urn:ietf:params:xml:schema:csvHost-1.0 5966 Registrant Contact: IESG 5968 Note to RFC Editor: Please remove the email address from the RFC 5969 after IANA records it. 5971 See section Section 9.5 of this document. 5973 Registration request for the RDE contact namespace: 5975 URI: urn:ietf:params:xml:ns:rdeContact-1.0 5977 Registrant Contact: IESG 5979 Note to RFC Editor: Please remove the email address from the RFC 5980 after IANA records it. 5982 XML: None. Namespace URIs do not represent an XML specification. 5984 Registration request for the RDE contact XML schema: 5986 URI: urn:ietf:params:xml:schema:rdeContact-1.0 5988 Registrant Contact: IESG 5990 Note to RFC Editor: Please remove the email address from the RFC 5991 after IANA records it. 5993 See section Section 9.6 of this document. 5995 Registration request for the CSV contact namespace: 5997 URI: urn:ietf:params:xml:ns:csvContact-1.0 5999 Registrant Contact: IESG 6001 Note to RFC Editor: Please remove the email address from the RFC 6002 after IANA records it. 6004 XML: None. Namespace URIs do not represent an XML specification. 6006 Registration request for the CSV contact XML schema: 6008 URI: urn:ietf:params:xml:schema:csvContact-1.0 6010 Registrant Contact: IESG 6011 Note to RFC Editor: Please remove the email address from the RFC 6012 after IANA records it. 6014 See section Section 9.7 of this document. 6016 Registration request for the RDE registrar namespace: 6018 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6020 Registrant Contact: IESG 6022 Note to RFC Editor: Please remove the email address from the RFC 6023 after IANA records it. 6025 XML: None. Namespace URIs do not represent an XML specification. 6027 Registration request for the RDE registrar XML schema: 6029 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6031 Registrant Contact: IESG 6033 Note to RFC Editor: Please remove the email address from the RFC 6034 after IANA records it. 6036 See section Section 9.8 of this document. 6038 Registration request for the CSV registrar namespace: 6040 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6042 Registrant Contact: IESG 6044 Note to RFC Editor: Please remove the email address from the RFC 6045 after IANA records it. 6047 XML: None. Namespace URIs do not represent an XML specification. 6049 Registration request for the CSV registrar XML schema: 6051 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6053 Registrant Contact: IESG 6055 Note to RFC Editor: Please remove the email address from the RFC 6056 after IANA records it. 6058 See section Section 9.9 of this document. 6060 Registration request for the RDE IDN namespace: 6062 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6064 Registrant Contact: IESG 6066 Note to RFC Editor: Please remove the email address from the RFC 6067 after IANA records it. 6069 XML: None. Namespace URIs do not represent an XML specification. 6071 Registration request for the RDE IDN XML schema: 6073 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6075 Registrant Contact: IESG 6077 Note to RFC Editor: Please remove the email address from the RFC 6078 after IANA records it. 6080 See section Section 9.10 of this document. 6082 Registration request for the CSV IDN namespace: 6084 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6086 Registrant Contact: IESG 6088 Note to RFC Editor: Please remove the email address from the RFC 6089 after IANA records it. 6091 XML: None. Namespace URIs do not represent an XML specification. 6093 Registration request for the CSV IDN XML schema: 6095 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6097 Registrant Contact: IESG 6099 Note to RFC Editor: Please remove the email address from the RFC 6100 after IANA records it. 6102 See section Section 9.11 of this document. 6104 Registration request for the RDE EPP parameters namespace: 6106 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6107 Registrant Contact: IESG 6109 Note to RFC Editor: Please remove the email address from the RFC 6110 after IANA records it. 6112 XML: None. Namespace URIs do not represent an XML specification. 6114 Registration request for the RDE EPP parameters XML schema: 6116 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6118 Registrant Contact: IESG 6120 Note to RFC Editor: Please remove the email address from the RFC 6121 after IANA records it. 6123 See section Section 9.12 of this document. 6125 Registration request for the RDE NNDN namespace: 6127 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6129 Registrant Contact: IESG 6131 Note to RFC Editor: Please remove the email address from the RFC 6132 after IANA records it. 6134 XML: None. Namespace URIs do not represent an XML specification. 6136 Registration request for the RDE NNDN XML schema: 6138 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6140 Registrant Contact: IESG 6142 Note to RFC Editor: Please remove the email address from the RFC 6143 after IANA records it. 6145 See section Section 9.13 of this document. 6147 Registration request for the CSV NNDN namespace: 6149 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6151 Registrant Contact: IESG 6153 Note to RFC Editor: Please remove the email address from the RFC 6154 after IANA records it. 6156 XML: None. Namespace URIs do not represent an XML specification. 6158 Registration request for the CSV NNDN XML schema: 6160 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6162 Registrant Contact: IESG 6164 Note to RFC Editor: Please remove the email address from the RFC 6165 after IANA records it. 6167 See section Section 9.14 of this document. 6169 Registration request for the RDE Policy namespace: 6171 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6173 Registrant Contact: IESG 6175 Note to RFC Editor: Please remove the email address from the RFC 6176 after IANA records it. 6178 XML: None. Namespace URIs do not represent an XML specification. 6180 Registration request for the RDE Policy XML schema: 6182 URI: urn:ietf:params:xml:ns:rdePolicy-1.0 6184 Registrant Contact: IESG 6186 Note to RFC Editor: Please remove the email address from the RFC 6187 after IANA records it. 6189 See section Section 9.15 of this document. 6191 Registration request for the RDE Header namespace: 6193 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6195 Registrant Contact: IESG 6197 Note to RFC Editor: Please remove the email address from the RFC 6198 after IANA records it. 6200 XML: None. Namespace URIs do not represent an XML specification. 6202 Registration request for the RDE Header XML schema: 6204 URI: urn:ietf:params:xml:ns:rdeHeader-1.0 6206 Registrant Contact: IESG 6208 Note to RFC Editor: Please remove the email address from the RFC 6209 after IANA records it. 6211 See section Section 9.16 of this document. 6213 Registration request for the RDE Common Objects namespace: 6215 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6217 Registrant Contact: IESG 6219 Note to RFC Editor: Please remove the email address from the RFC 6220 after IANA records it. 6222 XML: None. Namespace URIs do not represent an XML specification. 6224 Registration request for the RDE Common Objects XML schema: 6226 URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0 6228 Registrant Contact: IESG 6230 Note to RFC Editor: Please remove the email address from the RFC 6231 after IANA records it. 6233 See section Section 9.17 of this document. 6235 12. Implementation Status 6237 Note to RFC Editor: Please remove this section and the reference to 6238 RFC 7942 [RFC7942] before publication. 6240 This section records the status of known implementations of the 6241 protocol defined by this specification at the time of posting of this 6242 Internet-Draft, and is based on a proposal described in RFC 7942 6243 [RFC7942]. The description of implementations in this section is 6244 intended to assist the IETF in its decision processes in progressing 6245 drafts to RFCs. Please note that the listing of any individual 6246 implementation here does not imply endorsement by the IETF. 6247 Furthermore, no effort has been spent to verify the information 6248 presented here that was supplied by IETF contributors. This is not 6249 intended as, and must not be construed to be, a catalog of available 6250 implementations or their features. Readers are advised to note that 6251 other implementations may exist. 6253 According to RFC 7942 [RFC7942], "this will allow reviewers and 6254 working groups to assign due consideration to documents that have the 6255 benefit of running code, which may serve as evidence of valuable 6256 experimentation and feedback that have made the implemented protocols 6257 more mature. It is up to the individual working groups to use this 6258 information as they see fit". 6260 12.1. Implementation in the gTLD space 6262 Organization: ICANN 6264 Name: ICANN Registry Agreement 6266 Description: the ICANN Base Registry Agreement requires Registries, 6267 Data Escrow Agents, and ICANN to implement this specification. ICANN 6268 receives daily notifications from Data Escrow Agents confirming that 6269 more than 1,200 gTLDs are sending deposits that comply with this 6270 specification. ICANN receives on a weekly basis per gTLD, from more 6271 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6272 also complies with this specification. In addition, ICANN is aware 6273 of Registry Service Provider transitions using data files that 6274 conform to this specification. 6276 Level of maturity: production. 6278 Coverage: all aspects of this specification are implemented. 6280 Version compatibility: versions 03 - 08 are known to be implemented. 6282 Contact: gustavo.lozano@icann.org 6284 URL: https://www.icann.org/resources/pages/registries/registries- 6285 agreements-en 6287 13. Security Considerations 6289 This specification does not define the security mechanisms to be used 6290 in the transmission of the data escrow deposits, since it only 6291 specifies the minimum necessary to enable the rebuilding of a 6292 registry from deposits without intervention from the original 6293 registry. 6295 Depending on local policies, some elements or, most likely, the whole 6296 deposit will be considered confidential. As such, the registry 6297 transmitting the data to the escrow agent SHOULD take all the 6298 necessary precautions such as encrypting the data itself and/or the 6299 transport channel to avoid inadvertent disclosure of private data. 6301 Authentication of the parties passing data escrow deposit files is 6302 also of the utmost importance. The escrow agent MUST properly 6303 authenticate the identity of the registry before accepting data 6304 escrow deposits. In a similar manner, the registry MUST authenticate 6305 the identity of the escrow agent before submitting any data. 6307 Additionally, the registry and the escrow agent MUST use integrity 6308 checking mechanisms to ensure the data transmitted is what the source 6309 intended. Validation of the contents by the escrow agent is 6310 RECOMMENDED to ensure not only that the file was transmitted 6311 correctly from the registry, but also that the contents are 6312 "meaningful". 6314 Note: if Transport Layer Security (TLS) is used when providing an 6315 escrow services, the recommendations in [RFC7525] MUST be 6316 implemented. 6318 14. Privacy Considerations 6320 This specification defines a format that may be used to escrow 6321 personal data. The process of data escrow is governed by a legal 6322 document agreed by the parties, and such legal document must ensure 6323 that privacy-sensitive and/or personal data receives the required 6324 protection. 6326 15. Acknowledgments 6328 Parts of this document are based on EPP [RFC5730] and related RFCs by 6329 Scott Hollenbeck. 6331 Special suggestions that have been incorporated into this document 6332 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6333 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6334 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6335 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6336 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6337 Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. 6339 Shoji Noguchi and Francisco Arias participated as co-authors until 6340 version 05 providing invaluable support for this document. 6342 16. Change History 6344 [[RFC Editor: Please remove this section.]] 6346 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6347 dnrd-objects-mapping-00 6349 1. Added definition for child elements under the element. 6351 2. Added definition for child elements under the element. 6353 3. Added definition for child elements under the element. 6355 4. Rewrote the IDN Variants Handling section to use the variant 6356 states as described in ICANN's Study of Issues Related to the 6357 Management of IDN Variant TLDs. 6359 5. Renamed to in the . 6361 6. Renamed to in the element. 6363 7. Renamed to in the element. 6365 8. Added element under element. 6367 9. Fixed some typographical errors and omissions. 6369 16.2. Changes from 00 to 01 6371 1. Specify OPTIONAL elements in the draft. 6373 2. Added NNDN object to support list of reserved names and different 6374 IDN variants models. 6376 3. Removed subordinated host element from the domain object. 6378 4. Added eppParams object. 6380 5. Added variantGenerator element to the domain object. 6382 6. Added lgr to the IDN table object. 6384 16.3. Changes from 01 to 02 6386 1. Updates to the all objects based on feedback from the list. 6388 2. Start of XML and CSV drafts merge. 6390 3. Added header object. 6392 4. Added report object. 6394 5. Added notification object. 6396 6. Added Data Escrow Agent Extended Verification Process section. 6398 7. Added Notifications from Registries to Third Parties. 6400 8. Added Notifications from Data Escrow Agents to Third Parties. 6402 9. Added FULL, DIFF deposit examples using the XML model only. 6404 16.4. Changes from 02 to 03 6406 1. Remove authinfo from the XML Schema. 6408 2. Resend attribute is now an element 6410 3. Scope attribute added to policy object. 6412 16.5. Changes from 03 to 04 6414 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6415 arias-noguchi-dnrd-objects-mapping-02. 6417 2. Changed the cksum attribute of to use CRC32 and 6418 changed all of the sample cksum values to use CRC32, based on 6419 feedback from David Kipling. 6421 3. Changed the optional element to be an optional 6422 "sep" attribute value of the element with a default 6423 value of "," based on feedback from David Kipling. 6425 4. Added support for the optional "parent" attribute for the to the 6426 CSV fields to indicate a field as a reference to a parent 6427 object, based on feedback from David Kipling. 6429 5. Added support for the CSV model for the NNDN. 6431 6. Added support to delete hosts based on roid. 6433 7. Added mirrored state to NNDN 6435 8. Minor fixes to XML XSDs. 6437 9. The Report and Notification objects were moved to draft-lozano- 6438 icann-registry-interfaces 6440 10. The section Data escrow notifications was moved to draft-lozano- 6441 icann-registry-interfaces 6443 11. Removed references to the , , and 6444 from the "hostStatuses" and "hostAddresses" CSV 6445 files. 6447 12. Removed references to the , , and 6448 from the "contactStatuses" CSV file. 6450 13. Removed references to the , , and 6451 from the "domainContacts", "domainStatuses", 6452 and "domainNameServers" CSV files. 6454 14. Changed to . 6456 15. Replaced use of to new field 6457 in the "domain", "idnLanguage", and "NNDN" CSV files. 6459 16. Replaced use of with in the 6460 "host" element. 6462 17. Changed the foreign key of the hosts to use 6463 instead of and removed use of in 6464 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6465 files. 6467 18. Added use of the MUST keyword for CSV fields that are required 6468 to be supported in an EPP based system. 6470 19. Removed use of the field element for the 6471 "registrar" CSV file. 6473 20. Added definition of field element. 6475 16.6. Changes from 04 to 05 6477 1. Updated the examples of the full and differential deposits using 6478 the CSV and XML model. 6480 2. Made optional for the "domainTransfer" CSV file 6481 to match the XML definition. 6483 3. Made optional for the "domain" CSV file 6484 to match the XML definition. 6486 4. Made optional for the "domain" and "contact" CSV 6487 files to match the XML definition. 6489 5. Change from IDREF to idType. 6491 6. Minor editorial changes. 6493 16.7. Changes from 05 to 06 6495 1. Revised the differential and incremental deposits for the CSV 6496 format to use cascade update / replace and delete from the parent 6497 object to be consistent with the XML format. 6499 2. Revised the structure of the CSV format sections to utilize sub- 6500 sections instead of a list for the CSV file definitions. 6502 3. Added the "CSV Parent Child Relationship" section to describe the 6503 concept of parent child relationships across CSV file 6504 definitions. 6506 4. Added the "domainNameServersAddresses" CSV File Definition 6507 section to support the domain host attributes model of [RFC5731]. 6509 5. Made the required fields in the CSV format consistent with the 6510 XML format. The CSV fields updated to be required include: 6511 , , , 6512 , , , 6513 , , , 6514 , , , 6515 , , 6516 , , , 6517 , , 6518 , and . 6520 6. Revised the CSV examples to use a more realistic set of records. 6522 16.8. Changes from 06 to 07 6524 1. Created "repositoryTypeGroup" group element in the rdeHeader 6525 including the , and 6526 elements. 6528 2. Added the optional "rcdn" and "registrarId" attributes to the 6529 element 6531 16.9. Changes from 07 to 08 6533 1. The following registrar elements were made optional to support 6534 greater flexibility for the implementation of policies: status, 6535 postalInfo, email and crDate. 6537 2. The following domain name elements were made optional to support 6538 greater flexibility for the implementation of policies: crRr. 6540 16.10. Changes from 08 to 09 6542 1. Implementation Status section was added 6544 16.11. Changes from 09 to 10 6546 1. Editorial changes in section Section 5.1.2.1.6. 6548 2. Added MAY clause when the DS Data Interface is used in section 6549 Section 5.1.2.1.6. 6551 16.12. Changes from 10 to REGEXT 00 6553 1. Internet Draft (I-D) adopted by the REGEXT WG. 6555 16.13. Changes REGEXT 00 to REGEXT 01 6557 1. Added the element to the 6558 "repositoryTypeGroup" group element in the rdeHeader. 6560 2. Privacy consideration section was added 6562 3. Updates on section 8 6564 16.14. Changes REGEXT 01 to REGEXT 02 6566 1. Added a choice between the use of the or 6567 fields in the CSV "domain", "host", and 6568 "contact" definitions. 6570 2. Added a choice between the use of the or 6571 fields in the CSV "domainNameServers" 6572 definition. 6574 3. Changed "of client" to "of the client" throughout the document. 6576 4. Modified all references of 'The attribute isRequired MUST equal 6577 "true".' to 'The attribute "isRequired" MUST equal "true".' 6579 5. Combined the and 6580 fields in a single required list for the CSV "domainContacts" 6581 definition. 6583 6. Combined the , , and 6584 fields in a single required list for the 6585 CSV "domainStatuses" definition. 6587 7. Moved the the fields to the MAY 6588 list for the CSV "domain", "host", and "contact" definitions. 6590 8. Made the order of the , , 6591 , and fields more consistent in the 6592 CSV lists. 6594 9. Fixed an error in the order of the object example. 6596 10. Changed to be optional to match being 6597 optional in the XML model, by having it use type 6598 rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and 6599 ensuring that is included in the MAY field 6600 lists and not the MUST field lists. 6602 11. Made optional for the "domain" CSV definition 6603 to be consistent with the XML model, by removing the sentence 6604 'The attribute "isRequired" MUST equal "true".' from the 6605 description and moving the field to the MAY field list. 6607 12. Made optional for the "domain" and "contact" 6608 CSV definitions to be consistent with the XML model, by moving 6609 the field to the MAY field list. 6611 13. Made optional to be consistent with the XML 6612 model, by having it use type rdeCsv:fClIDType instead of 6613 rdeCsv:fClIDRequiredType. 6615 14. Made required to be consistent with the XML 6616 model, by having it use type rdeCsv:fClIDRequiredType instead of 6617 rdeCsv:fClIDType. 6619 15. Made the field in the "host", "contact", 6620 and "registrar" CSV definitions required explicitly by removing 6621 'and isRequired="true"' and adding the sentence 'The attribute 6622 isRequired MUST equal "true".', when it is chosen as the primary 6623 field. 6625 16. Removed extra '/>.' at the end of the field 6626 description in the "hostStatuses" CSV definition. 6628 17. Made the field optional to be consistent 6629 with the XML model, by having csvRegistrar:fStatusType extend 6630 rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. 6632 18. Made the field for the "registrar" CSV 6633 definition explicitly optional to be consistent with the XML 6634 model, by adding the sentence 'The attribute isRequired MUST 6635 equal "false".' to the field description and including the 6636 definition of isRequired="false" in the "registrar" CSV 6637 definition examples. 6639 19. Added the choice between the use of the and 6640 fields in the deletes "registrar" CSV 6641 definition to be consistent with the "registrar" CSV definition. 6643 20. Made the and elements optional for the host and 6644 contact objects in the XML model to be consistent with the 6645 domain object. 6647 16.15. Changes REGEXT 02 to REGEXT 03 6649 1. Added the optional element contentTag in the header object. 6651 2. Editorial updates. 6653 16.16. Changes REGEXT 03 to REGEXT 04 6655 1. Note: Updates from version REGEXT 03 to REGEXT 04 attend the 6656 feedback provided during the document shepherd review. 6658 2. Editorial updates. 6660 3. Examples now use domain names from the .example TLD. 6662 4. The introduction was enhanced by explaining the need for data 6663 escrow and the proposed solution. 6665 5. Explanation regarding NNDN was improved. 6667 6. Explanation regarding the CSV and XML model was improved. 6669 7. Section 4.5 updated to make the text clearer. 6671 8. draft-arias-noguchi-registry-data-escrow is now referenced from 6672 the I-D repository. 6674 9. The XML prefix "rdeDomain" is now consistently used. 6676 10. The prevID attribute was removed from the examples of full 6677 deposits. 6679 11. The examples were updated to use present dates. 6681 16.17. Changes REGEXT 04 to REGEXT 05 6683 1. draft-ietf-regext-data-escrow (version 04) is now referenced from 6684 the I-D repository. 6686 2. The example in idnLanguage CSV file definition updated to use the 6687 sep attribute. 6689 3. The reference in the example in hostAddresses CSV file definition 6690 was updated. 6692 4. Moved [RFC0791] and [RFC4291] to the Normative References 6693 section. 6695 16.18. Changes REGEXT 05 to REGEXT 06 6697 1. Changes based on the feedback provided here: 6698 https://mailarchive.ietf.org/arch/msg/regext/ 6699 nA8eTYIrXJ44_6ullQlRLW6T74s 6701 16.19. Changes REGEXT 06 to REGEXT 07 6703 1. Changes based on the feedback provided here: 6704 https://mailarchive.ietf.org/arch/msg/regext/hDLz2ym4oR-ukA4Fm- 6705 QJ8FzaxxE 6707 2. Changes based on the feedback provided here: 6708 https://mailarchive.ietf.org/arch/msg/regext/780Xw- 6709 z1RMRb79nmZ6ABmRTo1fU 6711 17. Example of a Full Deposit using the XML model 6713 Example of a Full Deposit using the XML model: 6715 6716 6732 2019-10-17T00:00:00Z 6733 6734 1.0 6735 urn:ietf:params:xml:ns:rdeHeader-1.0 6736 6737 urn:ietf:params:xml:ns:rdeContact-1.0 6738 6739 urn:ietf:params:xml:ns:rdeHost-1.0 6740 6741 urn:ietf:params:xml:ns:rdeDomain-1.0 6742 6743 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6744 6745 urn:ietf:params:xml:ns:rdeIDN-1.0 6746 6747 urn:ietf:params:xml:ns:rdeNNDN-1.0 6748 6749 urn:ietf:params:xml:ns:rdeEppParams-1.0 6750 6751 6753 6754 6755 6756 6757 test 6758 2 6760 6761 1 6763 6764 1 6766 6767 1 6769 6770 1 6772 6773 1 6775 6776 1 6778 6779 6781 6782 6783 example1.example 6784 Dexample1-TEST 6785 6786 jd1234 6787 sh8013 6788 sh8013 6789 6790 ns1.example.com 6791 ns1.example1.example 6792 6793 RegistrarX 6794 RegistrarX 6795 1999-04-03T22:00:00.0Z 6796 2015-04-03T22:00:00.0Z 6797 6799 6800 6801 example2.example 6802 Dexample2-TEST 6803 6804 6805 jd1234 6806 sh8013 6807 sh8013 6808 RegistrarX 6809 RegistrarX 6810 1999-04-03T22:00:00.0Z 6811 2015-04-03T22:00:00.0Z 6812 6814 6815 6816 ns1.example1.example 6817 Hns1_example_test-TEST 6818 6819 6820 192.0.2.2 6821 192.0.2.29 6822 1080:0:0:0:8:800:200C:417A 6823 6824 RegistrarX 6825 RegistrarX 6826 1999-05-08T12:10:00.0Z 6827 RegistrarX 6828 2009-10-03T09:34:00.0Z 6829 6831 6832 6833 sh8013 6834 Csh8013-TEST 6835 6836 6837 6838 John Doe 6839 Example Inc. 6840 6841 123 Example Dr. 6842 Suite 100 6843 Dulles 6844 VA 6845 20166-6503 6846 US 6847 6848 6849 +1.7035555555 6850 6851 +1.7035555556 6852 6853 jdoe@example.example 6854 6855 RegistrarX 6856 RegistrarX 6857 6858 2009-09-13T08:01:00.0Z 6859 6860 RegistrarX 6861 6862 2009-11-26T09:10:00.0Z 6863 6864 2009-12-03T09:05:00.0Z 6865 6866 6867 6868 6869 6870 6872 6873 6874 RegistrarX 6875 Registrar X 6876 123 6877 ok 6878 6879 6880 123 Example Dr. 6881 6882 Suite 100 6883 6884 Dulles 6885 VA 6886 20166-6503 6887 US 6888 6889 6890 +1.7035555555 6891 6892 +1.7035555556 6893 6894 jdoe@example.example 6895 6896 http://www.example.example 6897 6898 6899 whois.example.example 6900 6901 http://whois.example.example 6902 6903 6904 2005-04-23T11:49:00.0Z 6905 6906 2009-02-17T17:51:00.0Z 6907 6908 6910 6911 6912 6913 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 6914 6915 6916 http://registro.br/dominio/regras.html 6917 6918 6920 6921 6922 xn--exampl-gva.example 6923 pt-BR 6924 example1.example 6925 withheld 6926 2005-04-23T11:49:00.0Z 6927 6929 6930 6931 1.0 6932 en 6933 6934 urn:ietf:params:xml:ns:domain-1.0 6935 6936 6937 urn:ietf:params:xml:ns:contact-1.0 6938 6939 6940 urn:ietf:params:xml:ns:host-1.0 6941 6942 6943 urn:ietf:params:xml:ns:rgp-1.0 6944 6945 urn:ietf:params:xml:ns:secDNS-1.1 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6968 6970 6972 18. Example of Differential Deposit using the XML model 6974 Example of a Differential Deposit using the XML model: 6976 6977 6992 2019-10-17T00:00:00Z 6993 6994 1.0 6995 urn:ietf:params:xml:ns:rdeHeader-1.0 6996 6997 urn:ietf:params:xml:ns:rdeContact-1.0 6998 6999 urn:ietf:params:xml:ns:rdeHost-1.0 7000 7001 urn:ietf:params:xml:ns:rdeDomain-1.0 7002 7003 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7004 7005 urn:ietf:params:xml:ns:rdeIDN-1.0 7006 7007 urn:ietf:params:xml:ns:rdeNNDN-1.0 7008 7009 urn:ietf:params:xml:ns:rdeEppParams-1.0 7010 7011 7013 7014 7015 7016 example2.example 7017 7019 7021 7022 7023 7024 7025 test 7026 1 7028 7029 1 7031 7032 1 7034 7035 1 7037 7038 1 7040 7041 1 7043 7044 1 7046 7047 7048 7049 7051 19. Example of a Full Deposit using the CSV model 7053 Example of a Full Deposit using the CSV model: 7055 7056 7070 2019-10-18T00:00:00Z 7071 7072 1.0 7073 urn:ietf:params:xml:ns:csvDomain-1.0 7074 urn:ietf:params:xml:ns:csvHost-1.0 7075 urn:ietf:params:xml:ns:csvContact-1.0 7076 urn:ietf:params:xml:ns:csvRegistrar-1.0 7077 urn:ietf:params:xml:ns:csvIDN-1.0 7078 urn:ietf:params:xml:ns:csvNNDN-1.0 7079 urn:ietf:params:xml:ns:rdeEppParams-1.0 7080 7081 7082 7083 test 7084 7085 4 7086 7087 7088 6 7089 7090 7091 9 7092 7093 7094 3 7095 7096 7097 2 7098 7099 7100 2 7101 7102 7103 1 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7126 domain-YYYYMMDD.csv 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7139 domainContacts-YYYYMMDD.csv 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7154 domainStatuses-YYYYMMDD.csv 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7166 domainNameServers-name-YYYYMMDD.csv 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7178 domainNameServers-roid-YYYYMMDD.csv 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7194 dnssec-ds-YYYYMMDD.csv 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7210 dnssec-key-YYYYMMDD.csv 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7230 domainTransfer-YYYYMMDD.csv 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7252 host-YYYYMMDD.csv 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7266 hostStatuses-YYYYMMDD.csv 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7279 hostAddresses-YYYYMMDD.csv 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7305 contact-YYYYMMDD.csv 7306 7307 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7320 contactStatuses-YYYYMMDD.csv 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7341 contactPostal-YYYYMMDD.csv 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7359 contactTransfer-YYYYMMDD.csv 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7380 contactDisclose-YYYYMMDD.csv 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7412 registrar-YYYYMMDD.csv 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7426 idnLanguage-YYYYMMDD.csv 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7444 NNDN-YYYYMMDD.csv 7445 7446 7447 7448 7449 7450 1.0 7451 en 7452 urn:ietf:params:xml:ns:domain-1.0 7453 7454 urn:ietf:params:xml:ns:host-1.0 7455 7456 urn:ietf:params:xml:ns:contact-1.0 7457 7458 7459 urn:ietf:params:xml:ns:secDNS-1.1 7460 7461 urn:ietf:params:xml:ns:rgp-1.0 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7488 20. Example of Differential Deposit using the CSV model 7490 Example of a Differential Deposit using the CSV model: 7492 7493 7507 2019-10-18T00:00:00Z 7508 7509 1.0 7510 urn:ietf:params:xml:ns:csvDomain-1.0 7511 urn:ietf:params:xml:ns:csvHost-1.0 7512 urn:ietf:params:xml:ns:csvContact-1.0 7513 urn:ietf:params:xml:ns:csvRegistrar-1.0 7514 urn:ietf:params:xml:ns:csvIDN-1.0 7515 7516 7517 7518 7519 7520 7521 7522 7523 7525 domain-delete-YYYYMMDD.csv 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7538 host-delete-YYYYMMDD.csv 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7551 contact-delete-YYYYMMDD.csv 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7564 registrar-delete-YYYYMMDD.csv 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7577 idnLanguage-delete-YYYYMMDD.csv 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7590 NNDN-delete-YYYYMMDD.csv 7591 7592 7593 7594 7595 7596 7597 7598 test 7599 7600 2 7601 7602 7603 2 7604 7605 7606 3 7607 7608 7609 1 7610 7611 7612 1 7613 7614 7615 1 7616 7617 7618 1 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7641 domain-YYYYMMDD.csv 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7654 domainContacts-YYYYMMDD.csv 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7669 domainStatuses-YYYYMMDD.csv 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7681 domainNameServers-name-YYYYMMDD.csv 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7693 domainNameServers-roid-YYYYMMDD.csv 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7709 dnssec-ds-YYYYMMDD.csv 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7725 dnssec-key-YYYYMMDD.csv 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7744 domainTransfer-YYYYMMDD.csv 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7766 host-YYYYMMDD.csv 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7780 hostStatuses-YYYYMMDD.csv 7781 7782 7783 7784 7785 7786 7787 7788 7790 7791 7792 7794 hostAddresses-YYYYMMDD.csv 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7820 contact-YYYYMMDD.csv 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7834 contactStatuses-YYYYMMDD.csv 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7855 contactPostal-YYYYMMDD.csv 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7873 contactTransfer-YYYYMMDD.csv 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7894 contactDisclose-YYYYMMDD.csv 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7926 registrar-YYYYMMDD.csv 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7940 idnLanguage-YYYYMMDD.csv 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7958 NNDN-YYYYMMDD.csv 7959 7960 7961 7962 7963 7964 1.0 7965 en 7966 urn:ietf:params:xml:ns:domain-1.0 7967 7968 urn:ietf:params:xml:ns:host-1.0 7969 7970 urn:ietf:params:xml:ns:contact-1.0 7971 7972 7973 urn:ietf:params:xml:ns:secDNS-1.1 7974 7975 urn:ietf:params:xml:ns:rgp-1.0 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8002 21. References 8004 21.1. Normative References 8006 [I-D.ietf-regext-data-escrow] 8007 Lozano, G., "Registry Data Escrow Specification", draft- 8008 ietf-regext-data-escrow-08 (work in progress), April 2020. 8010 [ISO-3166-1] 8011 3166, I. S., "Codes for the representation of names of 8012 countries and their subdivisions -- Part 1: Country 8013 codes", ISO Standard 3166, November 2006. 8015 [ITU-E164] 8016 International Telecommunication Union, "The international 8017 public telecommunication numbering plan", ITU-T 8018 Recommendation E.164, February 2005. 8020 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8021 DOI 10.17487/RFC0791, September 1981, 8022 . 8024 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8025 Requirement Levels", BCP 14, RFC 2119, 8026 DOI 10.17487/RFC2119, March 1997, 8027 . 8029 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8030 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8031 . 8033 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8034 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8035 DOI 10.17487/RFC3915, September 2004, 8036 . 8038 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8039 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8040 2006, . 8042 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8043 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8044 . 8046 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8047 Domain Name Mapping", STD 69, RFC 5731, 8048 DOI 10.17487/RFC5731, August 2009, 8049 . 8051 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8052 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8053 August 2009, . 8055 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8056 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8057 August 2009, . 8059 [RFC5891] Klensin, J., "Internationalized Domain Names in 8060 Applications (IDNA): Protocol", RFC 5891, 8061 DOI 10.17487/RFC5891, August 2010, 8062 . 8064 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8065 Security Extensions Mapping for the Extensible 8066 Provisioning Protocol (EPP)", RFC 5910, 8067 DOI 10.17487/RFC5910, May 2010, 8068 . 8070 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 8071 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 8072 May 2017, . 8074 [W3C.REC-xml-20081126] 8075 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 8076 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 8077 Edition) REC-xml-20081126", November 2008, 8078 . 8080 [W3C.REC-xmlschema-1-20041028] 8081 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 8082 "XML Schema Part 1: Structures Second Edition REC- 8083 xmlschema-1-20041028", October 2004, 8084 . 8086 [W3C.REC-xmlschema-2-20041028] 8087 Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes 8088 Second Edition REC-xmlschema-2-20041028", October 2004, 8089 . 8091 21.2. Informative References 8093 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8094 DOI 10.17487/RFC3688, January 2004, 8095 . 8097 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8098 DOI 10.17487/RFC3912, September 2004, 8099 . 8101 [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, 8102 "Recommendations for Secure Use of Transport Layer 8103 Security (TLS) and Datagram Transport Layer Security 8104 (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 8105 2015, . 8107 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8108 Code: The Implementation Status Section", BCP 205, 8109 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8110 . 8112 [variantTLDsReport] 8113 Internet Corporation for Assigned Names and Numbers 8114 (ICANN), "A Study of Issues Related to the Management of 8115 IDN Variant TLDs", February 2012, 8116 . 8119 Authors' Addresses 8121 Gustavo Lozano 8122 Internet Corporation for Assigned Names and Numbers 8123 12025 Waterfront Drive, Suite 300 8124 Los Angeles 90292 8125 United States of America 8127 Phone: +1.310.823.9358 8128 Email: gustavo.lozano@icann.org 8130 James Gould 8131 VeriSign, Inc. 8132 12061 Bluemont Way 8133 Reston 20190 8134 United States of America 8136 Email: jgould@verisign.com 8138 Chethan Thippeswamy 8139 VeriSign, Inc. 8140 12061 Bluemont Way 8141 Reston 20190 8142 United States of America 8144 Email: cthippeswamy@verisign.com