idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-05.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 (Jan 09, 2020) is 1568 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-10) exists of draft-ietf-regext-data-escrow-04 -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track J. Gould 5 Expires: July 12, 2020 C. Thippeswamy 6 VeriSign 7 Jan 09, 2020 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-05 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 July 12, 2020. 35 Copyright Notice 37 Copyright (c) 2020 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 54 2.1. XML Model . . . . . . . . . . . . . . . . . . . . . . . . 5 55 2.2. CSV Model . . . . . . . . . . . . . . . . . . . . . . . . 5 56 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6 58 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 59 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6 60 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 61 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 7 62 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 7 63 4.6. Conventions applicable to the CSV Model . . . . . . . . . 7 64 5. Object Description . . . . . . . . . . . . . . . . . . . . . 15 65 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 15 66 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 34 67 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 44 68 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 62 69 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 70 70 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 74 71 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 79 72 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 81 73 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 81 74 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 84 75 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 76 8. Data escrow agent extended verification process . . . . . . . 85 77 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 86 78 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 86 79 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 96 80 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 99 81 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 104 82 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 106 83 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 109 84 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 112 85 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 118 86 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 122 87 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 126 88 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 128 89 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 130 90 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 132 91 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 134 92 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 137 93 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 138 94 10. Internationalization Considerations . . . . . . . . . . . . . 140 95 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 140 96 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 146 97 12.1. Implementation in the gTLD space . . . . . . . . . . . . 146 99 13. Security Considerations . . . . . . . . . . . . . . . . . . . 147 100 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 147 101 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 147 102 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 148 103 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 104 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 148 105 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 148 106 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 149 107 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 149 108 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 149 109 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 151 110 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 151 111 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 152 112 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 152 113 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 152 114 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 152 115 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 152 116 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 152 117 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 152 118 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 154 119 16.16. Changes REGEXT 03 to REGEXT 04 . . . . . . . . . . . . . 154 120 16.17. Changes REGEXT 04 to REGEXT 05 . . . . . . . . . . . . . 155 121 17. Example of a full deposit using the XML model . . . . . . . . 155 122 18. Example of differential deposit using the XML model . . . . . 161 123 19. Example of a full deposit using the CSV model . . . . . . . . 162 124 20. Example of differential deposit using the CSV model . . . . . 171 125 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 182 126 21.1. Normative References . . . . . . . . . . . . . . . . . . 182 127 21.2. Informative References . . . . . . . . . . . . . . . . . 183 128 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 184 130 1. Introduction 132 Registry Data Escrow is the process by which a registry periodically 133 submits data deposits to a third-party called an escrow agent. These 134 deposits comprise the minimum data needed by a third-party to resume 135 operations if the registry cannot function and is unable or unwilling 136 to facilitate an orderly transfer of service. For example, for a 137 domain name registry or registrar, the data to be deposited would 138 include all the objects related to registered domain names, e.g., 139 names, contacts, name servers, etc. 141 The goal of data escrow is higher resiliency of registration 142 services, for the benefit of Internet users. The beneficiaries of a 143 registry are not just those registering information there, but all 144 relying parties that need to identify the owners of objects. 146 In the context of domain name registries, registration data escrow is 147 a requirement for generic top-level domains and some country code 148 top-level domain managers are also currently escrowing data. There 149 is also a similar requirement for ICANN-accredited domain registrars. 151 This document defines the standard set of objects for a Domain Name 152 Registry that uses the Registry Data Escrow Specification described 153 in [I-D.ietf-regext-data-escrow] for escrow. The set of objects 154 include: 156 o Domain: Internet domain names that are typically provisioned in a 157 Domain Name Registry using the EPP domain name mapping [RFC5731]. 158 The attributes defined in the EPP domain name mapping [RFC5731] 159 are fully supported by this document. 161 o Host: Internet host names that are typically provisioned in a 162 Domain Name Registry using the EPP host mapping [RFC5732]. The 163 attributes defined in the EPP host mapping [RFC5732] are fully 164 supported by this document. 166 o Contact: Individual or organization social information provisioned 167 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 168 The attributes defined in the EPP contact mapping [RFC5733] are 169 fully supported by this document. 171 o Registrar: The organization that sponsors objects like domains, 172 hosts, and contacts in a Domain Name Registry. 174 o NNDN (NNDN's not domain name): Domain Name Registries may maintain 175 domain names without them being persisted as domain objects in the 176 registry system, for example, a list of reserved names not 177 available for registration. The NNDN is a lightweight domain-like 178 object that is used to escrow domain names not maintained as 179 domain name objects. 181 This document defines the following pseudo-objects: 183 o IDN Table Reference: Internationalized Domain Names (IDN) included 184 in the Domain Object Data Escrow include references to the IDN 185 Table and Policy used in IDN registration. 187 o EPP parameters: Definition of the specific EPP parameters 188 supported by the Registry Operator. 190 o Header: Used to specify counters of objects in the database at a 191 certain point in time (watermark). 193 o Policy: Used to specify OPTIONAL elements from this specification 194 that are REQUIRED based on the business model of the registry. 196 2. Models 198 This document defines two different models that can be used to 199 deposit data escrow objects: XML and CSV. 201 The data escrow deposit MAY contain a mix of both models but an 202 object MUST be escrowed only in one model. 204 This document does not suggest the use of a particular model, and 205 both are equivalent. A Domain Name Registry may choose the model 206 that is more appropriate for the peculiarities of its systems. For 207 example, a registry may use the CSV-export functionality of the RDBMS 208 for escrow; therefore, the CSV model may be more appropriate. 209 Another registry may use the code developed for EPP to implement 210 escrow. 212 2.1. XML Model 214 XML: The XML model includes all the deposit information (meta-data 215 and data) in an XML document. The definition of the XML format is 216 fully defined in the XML schemas. As a convention, the objects 217 represented using the XML model are referenced using RDE and an XML 218 namespace that is prefixed with "rde". For example, the Domain Name 219 object represented using the XML model can be referred to as the RDE 220 Domain Name with the XML namespace including rdeDomain 221 (urn:ietf:params:xml:ns:rdeDomain-1.0). 223 2.2. CSV Model 225 CSV: The CSV model uses XML to define the data escrow format of the 226 data contained in referenced Comma-Separated Values (CSV) files. As 227 a convention, the objects represented using the CSV model is 228 referenced using CSV and an XML namespace that is prefixed with 229 "csv". For example, the Domain Name object represented using the CSV 230 model can be referred to as the CSV Domain Name with the XML 231 namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). 233 3. Terminology 235 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 236 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 237 "OPTIONAL" in this document are to be interpreted as described in BCP 238 14 [RFC2119] [RFC8174] when, and only when, they appear in all 239 capitals, as shown here. 241 REGISTRY. In the context of this draft the definition will be 242 overloaded (from the definition in the base protocol) to indicate an 243 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 244 NAME. 246 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 247 or any other domain name at any level in the DNS tree for which a 248 Registry (either directly or through and affiliate company) provides 249 Registry Services for other organizations or individuals. For 250 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 252 REGISTRY SERVICES. Services offered by the Registry critical to the 253 following tasks: the provisioning of domain names on receipt of 254 requests and data from registrars; responding to registrar queries 255 for status information relating to the DNS servers for the RCDN; 256 dissemination of RCDN zone files; operation of the Registry DNS 257 servers; and responding to queries for contact and other information 258 concerning DNS registrations in the RCDN. Any other products or 259 services that only a Registry is capable of providing, by reason of 260 its designation as the Registry. Typical examples of Registry 261 Services are: DNS resolution for the RCDN, WHOIS and EPP. 263 ALLOCATED. A status of some label with respect to a zone, whereby 264 the label is associated administratively to some entity that has 265 requested the label. This term (and its cognates "allocation" and 266 "to allocate") may represents the first step on the way to delegation 267 in the DNS. 269 4. General Conventions 271 4.1. Date and Time 273 Numerous fields indicate "dates", such as the creation and expiry 274 dates for domain names. These fields SHALL contain timestamps 275 indicating the date and time in UTC as specified in [RFC3339], with 276 no offset from the zero meridian. 278 4.2. Country names 280 Country identifiers SHALL be represented using two character 281 identifiers as specified in [ISO-3166-1]. 283 4.3. Telephone numbers 285 Telephone numbers (both voice and facsimile) SHALL be formatted based 286 on structures defined in [ITU-E164]. Telephone numbers described in 287 this specification are character strings that MUST begin with a plus 288 sign ("+", ASCII value 0x002B), followed by a country code defined in 290 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 291 a sequence of digits representing the telephone number. 293 4.4. Checksum 295 Checksum of the CSV data escrow files MUST use CRC32, that is the 296 algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of 297 ITU-T recommendation V.42. 299 4.5. IP addresses 301 IP addresses syntax MUST conform to the text representation of either 302 Internet Protocol Version 4 [RFC0791] or Internet Protocol Version 6 303 [RFC4291]. 305 4.6. Conventions applicable to the CSV Model 307 4.6.1. CSV Parent Child Relationship 309 The CSV model represents a relational model, where the CSV files 310 represent relational tables, the fields of the CSV files represent 311 columns of the tables, and each line of the CSV file represents a 312 record. As in a relational model, the CSV files can have 313 relationships utilizing primary keys in the parent CSV file 314 definitions and foreign keys in the child CSV file definitions for a 315 1-to-many relationship. The primary keys are not explicitly defined, 316 but the foreign keys are using the boolean "parent" field attribute 317 in the child CSV file. The relationships between the CSV files are 318 used to support a cascade replace or cascade delete of records 319 starting from the parent record in differential and incremental 320 deposits. 322 The following is an example of the CSV file definitions for a Sample 323 object consisting of a parent "sample" CSV File Definition and a 324 child "sampleStatuses" CSV File Definition. The primary key for the 325 Sample object is the field that is used as the 326 foreign key in the "sampleStatuses" CSV File Definition by specifying 327 the "parent=true" attribute. If a Sample record is updated or 328 deleted in a differential or incremental deposit, it should cascade 329 replace the data using the records included in the child 330 "sampleStatuses" CSV File Definition or cascade delete the existing 331 records in the child "sampleStatuses" CSV File Definition, 332 respectively. 334 335 ... 336 337 338 339 340 341 342 343 344 345 346 347 348 349 351 sample-YYYYMMDD.csv 352 353 354 355 356 357 358 359 360 361 362 363 365 sampleStatuses-YYYYMMDD.csv 366 367 368 369 ... 370 372 4.6.2. CSV elements 374 4.6.2.1. element 376 To support the CSV model, an element is defined for each object that 377 substitutes for the element and for the 378 element, that contains one or more elements. For 379 example, the Domain Name Object (Section 5.1) defines the 380 element, that substitutes for the 381 element, and the element, that substitutes for 382 the element. Both the element and 383 the elements contain one or more 384 elements. The element has the following child elements: 386 Ordered list of CSV fields used in the CSV files. 387 There is one or more child elements that substitute for the 388 abstract element. Each element defines the format 389 of the CSV field contained in the CSV files. The 390 elements support the "type" attribute that defines the XML simple 391 data type of the field element. The elements 392 support the "isRequired" attribute, with a default value of 393 "false", when set to "true" indicates that the field must be non- 394 empty in the CSV files and when set to "false" indicates that the 395 field MAY be empty in the CSV files. The "isRequired" attribute 396 MAY be specifically set for the field elements within the XML 397 schema and MAY be overridden when specifying the fields under the 398 element. The element supports an 399 OPTIONAL "parent" attribute that identifies the field as a 400 reference to a parent object, as defined in CSV Parent Child 401 Relationship (Section 4.6.1). For example, the field SHOULD set the 403 "parent" attribute to "true" to identify it as the parent domain 404 name of the domain status. 406 A list of one or more CSV files using the 407 child element. The child element 408 defines a reference to the CSV file name and has the following 409 optional attributes: 411 compression If the CSV file is compressed, the "compression" 412 attribute defines the compression format like "gzip" or "zip". 414 encoding Defines the encoding of the CSV file with the default 415 encoding of "UTF-8". 417 cksum Defines the checksum of the CSV file using CRC32, as 418 defined in Section 4.4. This attribute is used to validate 419 that the full CSV file exists and has not been tampered with. 421 The elements requires a "name" attribute that defines 422 the purpose of the CSV file with values like "domain", "host", 423 "contact". The supported "name" attribute values are defined for 424 each object type. The OPTIONAL "sep" attribute defines the CSV 425 separator character with the default separator character of ",". 427 The following is an example of the 428 element for domain name records where the is set 429 as required with isRequired="true". 431 432 ... 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 452 domain-YYYYMMDD.csv 453 454 455 456 ... 457 459 The following is example of the "domain-YYYYMMDD.csv" file with one 460 record matching the definition. 462 domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 463 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 464 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 465 The following is an example of the 466 element for domain name records. 468 469 ... 470 471 472 473 474 475 477 domain-delete-YYYYMMDD.csv 478 479 480 481 ... 482 484 The following is example of the "domain-delete-YYYYMMDD.csv" file 485 with three records that matches the single field. 487 domain1.example 488 domain2.example 489 domainN.example 491 4.6.2.2. CSV common field elements 493 The element defined in the element 494 (Section 4.6.2.1) section has child elements that substitute for the 495 abstract element. By convention 496 elements include an 'f' prefix to identify them as field definition 497 elements. There are a set of common field elements that are used 498 across multiple data escrow objects. The common field elements are 499 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 500 using the "rdeCsv" sample namespace prefix. The CSV common field 501 elements include: 503 UTF-8 encoded name field with 504 type="eppcom:labelType". 506 Repository Object IDentifier (ROID) field with 507 type="eppcom:roidType" and isRequired="true". 509 Registrant contact identifier with 510 type="eppcom:clIDType". 512 The object status description, which is 513 free form text describing the rationale for the status, with 514 type="normalizedString". 516 Identifier of the client (registrar) that sponsors 517 the object with type="eppcom:clIDType" and isRequired="true". 519 Identifier of the registrar, defined in Section 5.4, 520 of the client that created the object with type="eppcom:clIDType". 522 Identifier of the client that created the object with 523 type="eppcom:clIDType". 525 Identifier of the registrar, defined in Section 5.4, 526 of the client that updated the object with type="eppcom:clIDType". 528 Identifier of the client that updated the object with 529 type="eppcom:clIDType". 531 Identifier of the registrar, defined in Section 5.4, 532 of the client that requested the transfer with 533 type="eppcom:clIDType" and isRequired="true". 535 Identifier of the client that requested the transfer 536 with type="eppcom:clIDType". 538 Identifier of the registrar, defined in Section 5.4, 539 of the client that should take or took action with 540 type="eppcom:clIDType" and isRequired="true". 542 Identifier of the client that should take or took 543 action for transfer with type="eppcom:clIDType". 545 Created date of object with type="dateTime". 547 Updated date of object with type="dateTime". 549 Expiration date of object with type="dateTime". 551 Date that transfer was requested with 552 type="dateTime" and isRequired="true". 554 Date that transfer action should be taken or has 555 been taken with type="dateTime" and isRequired="true". 557 Date of last transfer with type="dateTime". 559 State of the most recent transfer request with 560 type="eppcom:trStatusType" and isRequired="true". 562 General token field with type="token". 564 General language field with type="language". 566 IDN Table Identifier used for IDN domain names 567 with type="token". 569 General positive integer field with 570 type="positiveInteger". 572 Contains the URL of an object like a registrar object 573 with type="anyURI". 575 Custom field with name attribute that defines the 576 custom field name" with type="token". 578 4.6.3. Internationalized and Localized Elements 580 Some elements MAY be provided in either internationalized form 581 ("int") or provided in localized form ("loc"). Those elements use a 582 field value or "isLoc" attribute to specify the form used. If an 583 "isLoc" attribute is used, a value of "true" indicates the use of the 584 localized form and a value of "false" indicates the use of the 585 internationalized form. This MAY override the form specified for a 586 parent element. A value of "int" is used to indicate the 587 internationalized form and a value of "loc" is used to indicate the 588 localized form. When the internalized form ("int") is provided, the 589 field value MUST be represented in a subset of UTF-8 that can be 590 represented in the 7-bit US-ASCII character set. When the localized 591 form ("loc") is provided, the field value MAY be represented in 592 unrestricted UTF-8. 594 The field elements below of the "registrar" 595 element specify the internationalized form with the 596 isLoc="false" attribute. 598 ... 599 600 ... 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 632 registrar-YYYYMMDD.csv 633 634 635 636 ... 637 638 ... 640 The following is an example of using the 641 field value to define the internationalized or localized form of the 642 remainder of the "contactPostal" field values. 644 ... 645 646 ... 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 664 contactPostal-YYYYMMDD.csv 665 666 667 668 ... 669 670 ... 672 5. Object Description 674 This section describes the base objects supported by this 675 specification: 677 5.1. Domain Name Object 679 The domain name object is based on the EPP domain name mapping 680 specified in [RFC5731]. The domain name object supports both the XML 681 Model and the CSV Model, defined in the Models (Section 2) section. 682 The elements used for both models are defined in the following 683 sections. 685 5.1.1. XML Model 687 There are two elements used in the data escrow of the domain name 688 objects for the XML model including the , under the 689 element, and the element, under the 690 element. 692 5.1.1.1. object 694 The domain element is based on the EPP domain response for an 695 authorized client (see Section 3.1.2. of [RFC5731]) with additional 696 data from an EPP Query Response, see Section 3.1.3. of 697 [RFC5731], RGP status from [RFC3915], and data from the EPP 698 command, see Section 5.2.1. of [RFC5910]. 700 A element substitutes for the abstract 701 element to define a concrete definition of a domain. The 702 element can be replaced by other domain definitions 703 using the XML schema substitution groups feature. 705 The element contains the following child elements: 707 o A element that contains the fully qualified name of the 708 domain name object. If the domain name is an IDN, the ASCII 709 Compatible Encoding (ACE) MUST be used. 711 o A element that contains the repository object identifier 712 assigned to the domain name object when it was created. 714 o An OPTIONAL element that contains the fully qualified name 715 of the domain name in Unicode character set. It MUST be provided 716 if available. 718 o An OPTIONAL element that references the IDN 719 Table used for the IDN. This corresponds to the "id" attribute of 720 the element. This element MUST be present if the 721 domain name is an IDN. 723 o An OPTIONAL element is used to indicate that the 724 domain name is an IDN variant. This element contains the domain 725 name used to generate the IDN variant. 727 o One or more elements that contain the current status 728 descriptors associated with the domain name. 730 o Zero or more OPTIONAL element to represent 731 "pendingDelete" sub-statuses, including "redemptionPeriod", 732 "pendingRestore", and "pendingDelete", that a domain name can be 733 in as a result of grace period processing as specified in 734 [RFC3915]. 736 o An OPTIONAL element that contain the identifier for 737 the human or organizational social information object associated 738 as the holder of the domain name object. 740 o Zero or more OPTIONAL elements that contain identifiers 741 for the human or organizational social information objects 742 associated with the domain name object. 744 o An OPTIONAL element that contains the fully qualified names 745 of the delegated host objects or host attributes (name servers) 746 associated with the domain name object. See Section 1.1 of 747 [RFC5731] for a description of the elements used to specify host 748 objects or host attributes. 750 o A element that contains the identifier of the sponsoring 751 registrar. 753 o An OPTIONAL element that contains the identifier of the 754 registrar that created the domain name object. An OPTIONAL client 755 attribute is used to specify the client that performed the 756 operation. 758 o An OPTIONAL element that contains the date and time of 759 the domain name object creation. This element MUST be present if 760 the domain name has been allocated. 762 o An OPTIONAL element that contains the date and time 763 identifying the end (expiration) of the domain name object's 764 registration period. This element MUST be present if the domain 765 name has been allocated. 767 o An OPTIONAL element that contains the identifier of the 768 registrar that last updated the domain name object. This element 769 MUST NOT be present if the domain has never been modified. An 770 OPTIONAL client attribute is used to specify the client that 771 performed the operation. 773 o An OPTIONAL element that contains the date and time of 774 the most recent domain-name-object modification. This element 775 MUST NOT be present if the domain name object has never been 776 modified. 778 o An OPTIONAL element that contains the public key 779 information associated with Domain Name System security (DNSSEC) 780 extensions for the domain name as specified in [RFC5910]. 782 o An OPTIONAL element that contains the date and time of 783 the most recent domain object successful transfer. This element 784 MUST NOT be present if the domain name object has never been 785 transferred. 787 o An OPTIONAL element that contains the following child 788 elements related to the last transfer request of the domain name 789 object. This element MUST NOT be present if a transfer request 790 for the domain name has never been created. 792 * A element that contains the state of the most recent 793 transfer request. 795 * A element that contains the identifier of the registrar 796 that requested the domain name object transfer. An OPTIONAL 797 client attribute is used to specify the client that performed 798 the operation. 800 * A element that contains the date and time that the 801 transfer was requested. 803 * An element that contains the identifier of the registrar 804 that SHOULD act upon a PENDING transfer request. For all other 805 status types, the value identifies the registrar that took the 806 indicated action. An OPTIONAL client attribute is used to 807 specify the client that performed the operation. 809 * An element that contains the date and time of a 810 required or completed response. For a PENDING request, the 811 value identifies the date and time by which a response is 812 required before an automated response action will be taken by 813 the registry. For all other status types, the value identifies 814 the date and time when the request was completed. 816 * An OPTIONAL element that contains the end of the 817 domain name object's validity period (expiry date) if the 818 transfer caused or causes a change in the validity period. 820 Example of a domain object: 822 ... 823 824 example1.example 825 Dexample1-TEST 826 827 jd1234 828 sh8013 829 sh8013 830 831 ns1.example.com 832 ns1.example1.example 833 834 RegistrarX 835 RegistrarX 836 1999-04-03T22:00:00.0Z 837 2015-04-03T22:00:00.0Z 838 839 ... 841 5.1.1.2. object 843 The element contains the fully qualified domain 844 name that was deleted and purged. 846 Example of object: 848 ... 849 850 ... 851 852 foo.example 853 bar.example 854 855 ... 856 857 ... 859 5.1.2. CSV Model 861 For the CSV Model of the domain name object, the 862 child element of the element is used to hold the new 863 or updated domain name objects for the deposit. The 864 child element of the element is 865 used to hold the deleted or purged domain name objects for the 866 deposit. Both the and 867 elements contain one or more elements with a set of 868 named CSV file definitions using the "name" attribute. 870 Differential and incremental deposits are based on changes to the 871 domain name objects. The updated domain name object data under the 872 element is a cascade replace down all of the 873 domain name CSV files starting with the parent "domain" CSV File 874 Definition (Section 5.1.2.1.1). The child CSV file definitions 875 include a field. All the child CSV 876 file definition data for the domain name objects in the parent 877 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 878 deleted and then set using the data in the child CSV files. The 879 deleted domain name object data under the element 880 is a cascade delete starting from the "domain" Deletes CSV File 881 Definition (Section 5.1.2.2.1). 883 5.1.2.1. 885 The is used to hold the new or updated domain 886 name object information for the deposit. The is 887 split into separate CSV file definitions using named 888 elements with the "name" attribute. The following sections include 889 the supported domain name CSV file definitions: 891 5.1.2.1.1. "domain" CSV File Definition 893 The "domain" CSV File Definition defines the fields and CSV file 894 references used for the parent domain name object records. All the 895 other domain name CSV file definitions are child CSV files based on 896 the inclusion of the field. 898 The following "csvDomain" field elements MUST be used in the "domain" 899 element: 901 Domain name field with type="eppcom:labelType" and 902 isRequired="true". 904 The following "csvDomain" field elements MAY be used in the "domain" 905 element: 907 Fully qualified name of the original IDN 908 domain name object related to the variant domain name object with 909 type="eppcom:labelType". 911 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 912 "domain" element: 914 Registry Object IDentifier (ROID) for the domain name 915 object with isRequired="true". 917 or A choice of: 919 Identifier of the sponsoring client with 920 isRequired="true". 922 Contains the ID assigned by ICANN with 923 type="positiveInteger". The attribute "isRequired" MUST equal 924 "true". 926 The following "rdeCsv" fields, defined in section CSV common field 927 elements (Section 4.6.2.2), MAY be used in the "domain" 928 element: 930 Identifier of the registrar, defined in Section 5.4, 931 of the client that created the object. 933 Identifier of the client that created the domain name 934 object. 936 Identifier of the registrar, defined in Section 5.4, 937 of the client that updated the object. 939 Identifier of the client that last updated the domain 940 name object. 942 UTF8 encoded domain name for the 943 field element. 945 IDN Table Identifier used for the IDN domain 946 name object that MUST match a field element 947 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 949 Registrant contact identifier for the domain 950 name object. 952 Created date and time of the domain name object. 954 Date and time of the last update to the domain name 955 object. 957 Expiration date and time for the domain name 958 object. 960 Date and time of the last transfer for the domain 961 name object. 963 Example of a "domain" element. 965 ... 966 967 ... 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 987 domain-YYYYMMDD.csv 988 989 990 991 ... 992 993 ... 995 Example of the corresponding domain-YYYYMMDD.csv file. The file 996 contains four records (two active ASCII domains, original IDN with 997 LANG-1 language rules, and variant IDN with LANG-1 language rules). 999 domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 1000 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1001 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1002 domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 1003 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 1004 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1005 xn--abc123.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 1006 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1007 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1008 xn--abc321.example,Dxnabc321-TEST,LANG-1,xn--abc123.example, 1009 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 1010 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1012 5.1.2.1.2. "domainContacts" CSV File Definition 1014 The "domainContacts" CSV File Definition defines the fields and CSV 1015 file references used for the domain name object link records to 1016 contact objects, as described in Contact Object (Section 5.3). 1018 The following "csvDomain" field elements, defined for the "domain" 1019 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 1020 "domainContacts" element: 1022 The name of the domain object that is linked to 1023 the contact object with isRequired="true". 1025 The contact type for the contact object 1026 link with type="domain:contactAttrType" and isRequired="true". 1027 The supported contact type values include "admin" for the 1028 administration contact, "billing" for the billing contact, and 1029 "tech" for the technical contact. 1031 The following "csvContact" fields, defined for the "contact" CSV File 1032 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 1033 element: 1035 The server-unique contact identifier with 1036 isRequired="true". 1038 Example of a "domainContacts" 1039 element. 1041 ... 1042 1043 ... 1044 1045 1046 1047 1048 1049 1050 1051 1053 domainContacts-YYYYMMDD.csv 1054 1055 1056 1057 ... 1058 1059 ... 1061 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1062 file contains an admin, tech, and billing contact for the four domain 1063 names domain1.example, domain2.example, xn--abc123.example and xn-- 1064 abc321.example. 1066 domain1.example,domain1admin,admin 1067 domain1.example,domain1tech,tech 1068 domain1.example,domain1billing,billing 1069 domain2.example,domain2admin,admin 1070 domain2.example,domain2tech,tech 1071 domain2.example,domain2billing,billing 1072 xn--abc123.example,xnabc123admin,admin 1073 xn--abc123.example,xnabc123tech,tech 1074 xn--abc123.example,xnabc123billing,billing 1075 xn--abc321.example,xnabc123admin,admin 1076 xn--abc321.example,xnabc123tech,tech 1077 xn--abc321.example,xnabc123billing,billing 1079 5.1.2.1.3. "domainStatuses" CSV File Definition 1081 The "domainStatuses" CSV File Definition defines the fields and CSV 1082 file references used for the domain name object statuses. 1084 The following "csvDomain" fields, defined for the "domain" CSV File 1085 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1086 element: 1088 Domain name of status with isRequired="true". 1090 The status of the domain name with 1091 type="domain:statusValueType" and isRequired="true". 1093 The Registry Grace Period (RGP) status, as a 1094 sub-status of the "pendingDelete" status 1095 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1097 The following "rdeCsv" fields, defined in section CSV common field 1098 elements (Section 4.6.2.2), MAY be used in the "domainStatuses" 1099 element: 1101 Domain object status description which 1102 is free form text describing the rationale for the status. 1104 Language of the field. 1106 Example of a "domainStatuses" 1107 element. 1109 ... 1110 1111 ... 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1123 domainStatuses-YYYYMMDD.csv 1124 1125 1126 1127 ... 1128 1129 ... 1131 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1132 file contains the statuses for the four domain names domain1.example, 1133 domain2.example, xn--abc123.example and xn--abc321.example. 1135 domain1.example,clientUpdateProhibited,"Disallow update", 1136 en, 1137 domain1.example,clientDeleteProhibited,"Disallow delete", 1138 en, 1139 domain2.example,ok,,, 1140 xn--abc123.example,ok,,, 1141 xn--abc321.example,ok,,, 1143 5.1.2.1.4. "domainNameServers" CSV File Definition 1145 The "domainNameServers" CSV File Definition defines the fields and 1146 CSV file references used for the domain name delegated hosts (name 1147 servers). The "domainNameServers" CSV files define the relationship 1148 between a domain name object and a delegated host. The 1149 "domainNameServers" CSV File is used to support the 1150 model, defined in [RFC5731]. 1152 The following "csvDomain" fields, defined for the "domain" CSV File 1153 Definition (Section 5.1.2.1.1), MUST be used in the 1154 "domainNameServers" element: 1156 Domain name using the delegated host with 1157 isRequired="true". 1159 The following "csvHost" and "rdeCsv" field elements MUST be used in 1160 the "domainNameServers" element: 1162 or A choice of: 1164 Host name field with type="eppcom:labelType" and 1165 isRequired="true". 1167 Host object Registry Object IDentifier (ROID) 1168 assigned to the host object with isRequired="true". 1170 Example of a "domainNameServers" 1171 element. 1173 ... 1174 1175 ... 1176 1177 1178 1179 1180 1181 1182 1184 domainNameServers-YYYYMMDD.csv 1185 1186 1187 1188 ... 1189 1190 ... 1192 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1193 The file contains the delegated hosts (name servers) for the four 1194 domain names domain1.example, domain2.example, xn--abc123.example and 1195 xn--abc321.example referenced via the field element. 1197 domain1.example,Hns1_domain1_test-TEST 1198 domain1.example,Hns2_domain1_test-TEST 1199 domain2.example,Hns1_domain2_test-TEST 1200 domain2.example,Hns2_domain2_test-TEST 1201 xn--abc123.example,Hns1_example_test-TEST 1202 xn--abc123.example,Hns2_example_test-TEST 1203 xn--abc321.example,Hns1_example_test-TEST 1204 xn--abc321.example,Hns2_example_test-TEST 1206 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1208 The "domainNameServersAddresses" CSV File Definition defines the 1209 fields and CSV file references used for supporting the host as domain 1210 attributes model. 1212 The following "csvDomain" fields, defined for the "domain" CSV File 1213 Definition (Section 5.1.2.1.1), MUST be used in the 1214 "domainNameServersAddresses" element: 1216 Domain name using the delegated host with host 1217 and isRequired="true". 1219 The following "rdeCsv" fields, defined in section Host CSV model 1220 elements (Section 5.2.2), MUST be used in the 1221 "domainNameServersAddresses" element: 1223 Host name field with type="eppcom:labelType" and 1224 isRequired="true". 1226 The following "csvHost" fields, defined in section Host CSV model 1227 elements (Section 5.2.2), MAY be used in the 1228 "domainNameServersAddresses" element: 1230 IP addresses associated with the host object with 1231 type="host:addrStringType". 1233 IP addresses version associated with the host 1234 object with type="host:ipType". "host:ipType" has the enumerated 1235 values of "v4" or "v6". 1237 Example of a "domainNameServersAddresses" 1238 element. 1240 ... 1241 1242 ... 1243 1244 1245 1246 1247 1248 1249 1250 1251 1253 domainNameServersAddresses-YYYYMMDD.csv 1254 1255 1256 1257 ... 1258 1259 ... 1261 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1262 file. The file contains the delegated hosts (name servers) for the 1263 four domain names domain1.example, domain2.example, xn-- 1264 abc123.example and xn--abc321.example. 1266 domain1.example,ns1.domain1.example,192.0.2.1,v4 1267 domain1.example,ns2.domain1.example,2001:DB8::1,v6 1268 domain2.example,ns1.example.net,, 1269 domain2.example,ns2.example.net,, 1270 xn--abc123.example,ns1.example.net,, 1271 xn--abc123.example,ns2.example.net,, 1272 xn--abc321.example,ns1.example.net,, 1273 xn--abc321.example,ns2.example.net,, 1275 5.1.2.1.6. "dnssec" CSV File Definition 1277 The "dnssec" CSV File Definition defines the fields and CSV file 1278 references used for the domain name object DNSSEC records (DS or Key 1279 Data). 1281 The following "csvDomain" field elements MUST be used in the "dnssec" 1282 element when the DS Data Interface per 1283 [RFC5910] is used: 1285 Contains the DS key tag value per [RFC5910] with 1286 type="unsignedShort" and isRequired="true". 1288 Contains the DS algorithm value per [RFC5910] 1289 with type="unsignedByte" and isRequired="true". 1291 Contains the DS digest type value per 1292 [RFC5910] with type="unsignedByte" and isRequired="true". 1294 Contains the DS digest value per [RFC5910] with 1295 type="hexBinary" and isRequired="true". 1297 The following "csvDomain" field elements MUST be used in the "dnssec" 1298 element when the Key Data Interface per 1299 [RFC5910] is used and MAY be used in the "dnssec" 1300 element when the DS Data Interface per [RFC5910] is 1301 used: 1303 Contains the flags field value per [RFC5910] with 1304 type="unsignedShort" and isRequired="true". 1306 Contains the Key protocol value per [RFC5910] 1307 with type="unsignedByte" and isRequired="true". 1309 Contains the Key algorithm value per [RFC5910] 1310 with type="unsignedByte" and isRequired="true". 1312 Contains the public key value per [RFC5910] with 1313 type="secDNS:keyType" and isRequired="true". 1315 The following "csvDomain" field elements MAY be used in the "dnssec" 1316 element: 1318 Indicates a child's preference for the 1319 number of seconds after signature generation when the parent's 1320 signature on the DS information provided by the child will expire 1321 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1323 The following "domain" fields, defined for the "domain" CSV File 1324 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1325 element: 1327 Domain name of the domain object associated with 1328 the DNSSEC record and isRequired="true". 1330 Example of a "dnssec" element with 1331 the DS Data Interface of [RFC5910]: 1333 1334 ... 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1347 dnssec-ds-YYYYMMDD.csv 1348 1349 1350 1351 ... 1352 1353 ... 1355 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1356 contains two DS records for domain1.example. 1358 domain1.example,604800,12345,3,1,49FD46E6C4B45C55D4AC 1359 domain1.example,604800,12346,3,1,38EC35D5B3A34B44C39B 1360 Example of a "dnssec" element with 1361 the Key Data Interface of [RFC5910]: 1363 1364 ... 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1377 dnssec-key-YYYYMMDD.csv 1378 1379 1380 1381 ... 1382 1383 ... 1385 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1386 contains two key records for domain1.example. 1388 domain1.example,604800,257,3,1,AQPJ////4Q== 1389 domain1.example,604800,257,3,1,AQPJ////4QQQ 1391 5.1.2.1.7. "domainTransfer" CSV File Definition 1393 The "domainTransfer" CSV File Definition defines the fields and CSV 1394 file references used for the domain name object pending and completed 1395 transfer records. No additional field elements were added for use in 1396 the "domainTransfer" element. 1398 The following "rdeCsv" fields, defined in section CSV common field 1399 elements (Section 4.6.2.2), MUST be used in the "domainTransfer" 1400 element: 1402 State of the most recent transfer request with 1403 isRequired="true". 1405 Identifier of the registrar, defined in Section 5.4, 1406 of the client that requested the transfer with isRequired="true". 1408 Date and time that the transfer was requested with 1409 isRequired="true". 1411 Identifier of the registrar, defined in Section 5.4, 1412 of the client that should take or took action with 1413 isRequired="true". 1415 Date and time that the transfer action should be 1416 taken or has been taken with isRequired="true". 1418 The following "rdeCsv" fields, defined in section CSV common field 1419 elements (Section 4.6.2.2), MAY be used in the "domainTransfer" 1420 element: 1422 Expiration date if the transfer command caused or 1423 causes a change in the validity period. 1425 Identifier of the client that requested the transfer. 1427 Identifier of the client that should take or took 1428 action for transfer. 1430 The following "csvDomain" fields, defined for the "domain" CSV File 1431 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1432 element: 1434 Domain name of the domain object involved in the 1435 transfer with isRequired="true". 1437 Example of a "domainTransfer" 1438 element. 1440 ... 1441 1442 ... 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1458 domainTransfer-YYYYMMDD.csv 1459 1460 1461 1462 ... 1463 1464 ... 1466 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1467 file contains one domain transfer record with a pending status. 1469 domain1.example,pending,registrarX,clientY, 1470 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1471 2016-04-03T22:00:00.0Z 1473 5.1.2.2. 1475 The is used to hold the deleted domain name 1476 objects in a differential or incremental deposit. All the domain 1477 name object data is deleted as part of a cascade delete. The 1478 is split into separate CSV file definitions using 1479 named elements with the "name" attribute. The following 1480 section defines the supported domain name deletes CSV file 1481 definition. 1483 5.1.2.2.1. "domain" Deletes CSV File Definition 1485 The following "csvDomain" field elements MUST be used in the deletes 1486 "domain" element: 1488 Domain name field with type="eppcom:labelType" and 1489 isRequired="true". 1491 Example of a "domain" element: 1493 ... 1494 1495 ... 1496 1497 1498 1499 1500 1501 1503 domain-delete-YYYYMMDD.csv 1504 1505 1506 1507 ... 1508 1509 ... 1511 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1512 file contains two domain name records. 1514 domain1.example 1515 domain2.example 1517 5.2. Host Object 1519 The host object is based on the EPP host name mapping in [RFC5732]. 1520 The host object supports both the XML Model and the CSV Model, 1521 defined in Models (Section 2) section. The elements used for both 1522 models are defined in the following sections. Both the 1523 and elements contain one or more 1524 elements with a set of named CSV file definitions using 1525 the "name" attribute. 1527 5.2.1. XML Model 1529 There are two elements used in the data escrow of the host objects 1530 for the XML model including the , under the 1531 element, and the element, under 1532 the element. 1534 A element substitutes for the 1535 abstract element to define a concrete definition of a host. The 1536 element can be replaced by other host 1537 definitions using the XML schema substitution groups feature. 1539 5.2.1.1. element 1541 The RDE host object is based on the EPP host response for an 1542 authorized client (Section 3.1.2. of [RFC5732]). 1544 The OPTIONAL element contains the following child elements: 1546 o A element that contains the fully qualified name of the 1547 host object. 1549 o A element that contains the repository object identifier 1550 assigned to the host object when the object was created. 1552 o One or more elements that describe the status of the host 1553 object. 1555 o Zero or more elements that contain the IP addresses 1556 associated with the host object. 1558 o A element that contains the identifier of the sponsoring 1559 registrar. 1561 o An OPTIONAL element that contains the identifier of the 1562 registrar that created the host object. An OPTIONAL client 1563 attribute is used to specify the client that performed the 1564 operation. 1566 o An OPTIONAL element that contains the date and time of 1567 host-object creation. 1569 o An OPTIONAL element that contains the identifier of the 1570 registrar that last updated the host object. This element MUST 1571 NOT be present if the host object has never been modified. An 1572 OPTIONAL client attribute is used to specify the client that 1573 performed the operation. 1575 o An OPTIONAL element that contains the date and time of 1576 the most recent host-object modification. This element MUST NOT 1577 be present if the host object has never been modified. 1579 o An OPTIONAL element that contains the date and time of 1580 the most recent host object successful transfer. This element 1581 MUST NOT be present if the domain name object has never been 1582 transfered. 1584 Example of object: 1586 ... 1587 1588 ns1.example1.example 1589 Hns1_example_test-TEST 1590 1591 1592 192.0.2.2 1593 192.0.2.29 1594 1080:0:0:0:8:800:200C:417A 1595 RegistrarX 1596 RegistrarX 1597 1999-05-08T12:10:00.0Z 1598 RegistrarX 1599 2009-10-03T09:34:00.0Z 1600 1601 ... 1603 5.2.1.2. object 1605 The element contains the fully qualified domain name 1606 of a host that was deleted. The element also 1607 supports host removal based on roid to support SRS systems in which 1608 different hosts with the same fully qualified domain name are active 1609 at the same time. 1611 Example of object: 1613 ... 1614 1615 ... 1616 1617 ns1.example.example 1618 1619 ... 1620 1621 ... 1623 5.2.2. CSV Model 1625 For the CSV Model of the host object, the child 1626 element of the element is used to hold the new or 1627 updated host objects for the deposit. The child 1628 element of the element is used to hold the deleted or 1629 purged host objects for the deposit. 1631 Differential and incremental deposits are based on changes to the 1632 host objects. The updated host object data under the 1633 element is a cascade replace down all of the host 1634 CSV files starting with the parent "host" CSV File Definition 1635 (Section 5.2.2.1.1). The child CSV file definitions include a 1636 field. All the child CSV file 1637 definition data for the host objects in the parent "host" CSV File 1638 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1639 using the data in the child CSV files. The deleted host object data 1640 under the element is a cascade delete starting from 1641 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1643 5.2.2.1. 1645 The is used to hold the new or updated host object 1646 information for the deposit. The is split into 1647 separate CSV file definitions using named elements with 1648 the "name" attribute. The following sections include the supported 1649 host CSV file definitions. 1651 5.2.2.1.1. "host" CSV File Definition 1653 The "host" CSV File Definition defines the fields and CSV file 1654 references used for the host object records. 1656 The following "csvHost" field elements MUST be used in the "host" 1657 element: 1659 Host name field with type="eppcom:labelType" and 1660 isRequired="true". 1662 The following "rdeCsv" fields, defined in section CSV common field 1663 elements (Section 4.6.2.2), MUST be used in the "host" 1664 element: 1666 Repository Object IDentifier (ROID) assigned to the 1667 host object with isRequired="true". 1669 The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the 1670 "host" element: 1672 or A choice of: 1674 Identifier of the sponsoring client with 1675 isRequired="true". 1677 Contains the ID assigned by ICANN with 1678 type="positiveInteger". The attribute "isRequired" MUST equal 1679 "true". 1681 Identifier of the registrar, defined in Section 5.4, 1682 of the client that created the object. 1684 Identifier of the client that created the host 1685 object. 1687 Identifier of the registrar, defined in Section 5.4, 1688 of the client that updated the object. 1690 Identifier of the client that last updated the host 1691 object. 1693 Date and time that the host object was created. 1695 Date and time that the host object was last 1696 updated. 1698 Date and time that the host was last transferred. 1700 Example of a "host" element. 1702 ... 1703 1704 ... 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1721 host-YYYYMMDD.csv 1722 1723 1724 1725 ... 1726 1727 ... 1729 Example of the corresponding host-YYYYMMDD.csv file. The file 1730 contains six host records with four being internal hosts and two 1731 being external hosts. 1733 ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX, 1734 clientY,1999-05-08T12:10:00.0Z,registrarX, 1735 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1736 ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX, 1737 clientY,1999-05-08T12:10:00.0Z,registrarX, 1738 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1739 ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX, 1740 clientY,1999-05-08T12:10:00.0Z,registrarX, 1741 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1742 ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, 1743 clientY,1999-05-08T12:10:00.0Z,registrarX, 1744 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1745 ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, 1746 clientY,1999-05-08T12:10:00.0Z,registrarX, 1747 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1748 ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, 1749 clientY,1999-05-08T12:10:00.0Z,registrarX, 1750 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1752 5.2.2.1.2. "hostStatuses" CSV File Definition 1754 The "hostStatuses" CSV File Definition defines the fields and CSV 1755 file references used for the host object statuses. 1757 The following "csvHost" fields, defined for the "host" CSV File 1758 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1759 element: 1761 The status of the host with 1762 type="host:statusValueType" and isRequired="true". 1764 The following "rdeCsv" fields, defined in section CSV common field 1765 elements (Section 4.6.2.2), MUST be used in the "hostStatuses" 1766 element: 1768 Host object Registry Object IDentifier (ROID) 1769 assigned to the host object with isRequired="true". 1771 The following "rdeCsv" fields, defined in section CSV common field 1772 elements (Section 4.6.2.2), MAY be used in the "hostStatuses" 1773 element: 1775 Host object status description which is 1776 free form text describing the rationale for the status. The 1777 attribute "isRequired" MUST equal "true". 1779 Language of the field. 1781 Example of a "hostStatuses" element. 1783 ... 1784 1785 ... 1786 1787 1788 1789 1790 1791 1792 1793 1794 1796 hostStatuses-YYYYMMDD.csv 1797 1798 1799 1800 ... 1801 1802 ... 1804 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1805 file contains the statuses for the six host names 1806 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example, 1807 ns2.domain2.example, ns1.example.net and ns2.example.net. 1809 Hns1_domain1_test-TEST,ok,, 1810 Hns2_domain1_test-TEST,ok,, 1811 Hns1_domain2_test-TEST,ok,, 1812 Hns2_domain2_test-TEST,ok,, 1813 Hns1_example_test-TEST,ok,, 1814 Hns2_example_test-TEST,ok,, 1816 5.2.2.1.3. "hostAddresses" CSV File Definition 1818 The "hostAddresses" CSV File Definition defines the fields and CSV 1819 file references used for the host object IP addresses. 1821 The following "csvHost" field elements MUST be used in the 1822 "hostAddresses" element: 1824 IP addresses associated with the host object with 1825 type="host:addrStringType". The attribute "isRequired" MUST equal 1826 "true". 1828 IP addresses version associated with the host 1829 object with type="host:ipType". "host:ipType" has the enumerated 1830 values of "v4" or "v6". The attribute "isRequired" MUST equal 1831 "true". 1833 The following "rdeCsv" fields, defined in section CSV common field 1834 elements (Section 4.6.2.2), MUST be used in the "hostAddresses" 1835 element: 1837 Host object Registry Object IDentifier (ROID) 1838 assigned to the host object with isRequired="true". 1840 Example of a "hostAddresses" element. 1842 ... 1843 1844 ... 1845 1846 1847 1848 1849 1850 1851 1852 1854 hostAddresses-YYYYMMDD.csv 1855 1856 1857 1858 ... 1859 1860 ... 1862 Example of the corresponding hostAddresses-YYYYMMDD.csv file. The 1863 file contains the IP addresses for the host names 1864 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and 1865 ns2.domain2.example. 1867 Hns1_domain1_test-TEST,192.0.2.1,v4 1868 Hns2_domain1_test-TEST,2001:DB8::1,v6 1869 Hns1_domain2_test-TEST,192.0.2.2,v4 1870 Hns2_domain2_test-TEST,2001:DB8::2,v6 1872 5.2.2.2. 1874 The is used to hold the deleted host objects in a 1875 differential or incremental deposit. All the host object data is 1876 deleted as part of a cascade delete. The is split 1877 into separate CSV file definitions using named elements 1878 with the "name" attribute. The following section defines the 1879 supported host deletes CSV file definition. 1881 5.2.2.2.1. "host" Deletes CSV File Definition 1883 The following "rdeCsv" fields, defined in section CSV common field 1884 elements (Section 4.6.2.2), MUST be used in the "host" 1885 element: 1887 Repository Object IDentifier (ROID) assigned to the 1888 host object with isRequired="true". 1890 Example of a "host" element. 1892 ... 1893 1894 ... 1895 1896 1897 1898 1899 1900 1902 host-delete-YYYYMMDD.csv 1903 1904 1905 1906 ... 1907 1908 ... 1910 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1911 host records. 1913 Hns1_domain1_test-TEST 1914 Hns2_domain1_test-TEST 1915 Hns1_domain2_test-TEST 1916 Hns2_domain2_test-TEST 1918 5.3. Contact Object 1920 The contact object is based on the EPP contact name mapping in 1921 [RFC5733]. The contact object supports both the XML Model and the 1922 CSV Model, defined in Models (Section 2) section. The elements used 1923 for both models are defined in the following sections. 1925 5.3.1. XML Model 1927 There are two elements used in the data escrow of the contact objects 1928 for the XML model including the , under the 1929 element, and the element, 1930 under the element. 1932 A element substitutes for the abstract 1933 element to define a concrete definition of a contact. The 1934 element can be replaced by other contact 1935 definitions using the XML schema substitution groups feature. 1937 5.3.1.1. object 1939 The contact object is based on the EPP contact response for an 1940 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1941 including the data from an EPP Query Response, see 1942 Section 3.1.3. of [RFC5733]. 1944 The OPTIONAL element contains the following child elements: 1946 o A element that contains the server-unique identifier of the 1947 contact object 1949 o A element that contains the Repository Object IDentifier 1950 assigned to the contact object when the object was created. 1952 o One or more elements that describe the status of the 1953 contact object. 1955 o One or two elements that contain postal-address 1956 information. Two elements are provided so that address 1957 information can be provided in both internationalized and 1958 localized forms; a "type" attribute is used to identify the two 1959 forms. If an internationalized form (type="int") is provided, 1960 element content MUST be represented in a subset of UTF-8 that can 1961 be represented in the 7-bit US-ASCII character set. If a 1962 localized form (type="loc") is provided, element content MAY be 1963 represented in unrestricted UTF-8. The element 1964 contains the following child elements: 1966 * A element that contains the name of the individual or 1967 role represented by the contact. 1969 * An OPTIONAL element that contains the name of the 1970 organization with which the contact is affiliated. 1972 * An element that contains address information associated 1973 with the contact. An element contains the following 1974 child elements: 1976 + One, two, or three OPTIONAL elements that contain 1977 the contact's street address. 1979 + A element that contains the contact's city. 1981 + An OPTIONAL element that contains the contact's state 1982 or province. 1984 + An OPTIONAL element that contains the contact's postal 1985 code. 1987 + A element that contains the contact's two-letter 1988 country code. 1990 o An OPTIONAL element that contains the contact's voice 1991 telephone number. 1993 o An OPTIONAL element that contains the contact's facsimile 1994 telephone number. 1996 o An element that contains the contact's email address. 1998 o A element that contains the identifier of the sponsoring 1999 registrar. 2001 o An OPTIONAL element that contains the identifier of the 2002 registrar that created the contact object. An OPTIONAL client 2003 attribute is used to specify the client that performed the 2004 operation. 2006 o An OPTIONAL element that contains the date and time of 2007 contact-object creation. 2009 o An OPTIONAL element that contains the identifier of the 2010 registrar that last updated the contact object. This element MUST 2011 NOT be present if the contact has never been modified. An 2012 OPTIONAL client attribute is used to specify the client that 2013 performed the operation. 2015 o An OPTIONAL element that contains the date and time of 2016 the most recent contact-object modification. This element MUST 2017 NOT be present if the contact object has never been modified. 2019 o An OPTIONAL element that contains the date and time of 2020 the most recent contact object successful transfer. This element 2021 MUST NOT be present if the contact object has never been 2022 transferred. 2024 o An OPTIONAL element that contains the following child 2025 elements related to the last transfer request of the contact 2026 object: 2028 * A element that contains the state of the most recent 2029 transfer request. 2031 * A element that contains the identifier of the registrar 2032 that requested the domain name object transfer. An OPTIONAL 2033 client attribute is used to specify the client that performed 2034 the operation. 2036 * An element that contains the identifier of the registrar 2037 that SHOULD act upon a PENDING transfer request. For all other 2038 status types, the value identifies the registrar that took the 2039 indicated action. An OPTIONAL client attribute is used to 2040 specify the client that performed the operation. 2042 * A element that contains the date and time that the 2043 transfer was requested. 2045 * An element that contains the date and time of a 2046 required or completed response. For a PENDING request, the 2047 value identifies the date and time by which a response is 2048 required before an automated response action will be taken by 2049 the registry. For all other status types, the value identifies 2050 the date and time when the request was completed. 2052 o An OPTIONAL element that identifies elements that 2053 requiring exceptional server-operator handling to allow or 2054 restrict disclosure to third parties. See Section 2.9 of 2055 [RFC5733] for a description of the child elements contained within 2056 the element. 2058 Example object: 2060 ... 2061 2062 sh8013 2063 Csh8013-TEST 2064 2065 2066 2067 John Doe 2068 Example Inc. 2069 2070 123 Example Dr. 2071 Suite 100 2072 Dulles 2073 VA 2074 20166-6503 2075 US 2076 2077 2078 +1.7035555555 2079 +1.7035555556 2080 jdoe@example.example 2081 RegistrarX 2082 RegistrarX 2083 2009-09-13T08:01:00.0Z 2084 RegistrarX 2085 2009-11-26T09:10:00.0Z 2086 2009-12-03T09:05:00.0Z 2087 2088 pending 2089 clientW 2090 2011-03-08T19:38:00.0Z 2091 RegistrarX 2092 2011-03-13T23:59:59.0Z 2093 2094 2095 2096 2097 2098 2099 ... 2101 5.3.1.2. object 2103 The element contains the id of a contact that was 2104 deleted. 2106 Example of object: 2108 ... 2109 2110 ... 2111 2112 sh8013-TEST 2113 co8013-TEST 2114 2115 ... 2116 2117 ... 2119 5.3.2. CSV Model 2121 For the CSV Model of the contact object, the 2122 child element of the element is used to hold the new 2123 or updated contacts objects for the deposit. The 2124 child element of the element is 2125 used to hold the deleted or purged contact objects for the deposit. 2126 Both the and elements 2127 contain one or more elements with a set of named CSV 2128 file definitions using the "name" attribute. 2130 Differential and incremental deposits are based on changes to the 2131 contact objects. The updated contact object data under the 2132 element is a cascade replace down all of the 2133 contact CSV files starting with the parent "contact" CSV File 2134 Definition (Section 5.3.2.1.1). The child CSV file definitions 2135 include a field. All the child CSV 2136 file definition data for the contact objects in the parent "contact" 2137 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2138 then set using the data in the child CSV files. The deleted contact 2139 object data under the element is a cascade 2140 delete starting from the "contact" Deletes CSV File Definition 2141 (Section 5.3.2.2.1). 2143 5.3.2.1. 2145 The is used to hold the new or updated contact 2146 object information for the deposit. The is 2147 split into separate CSV file definitions using named 2148 elements with the "name" attribute. The following sections include 2149 the supported contact CSV file definitions. 2151 5.3.2.1.1. "contact" CSV File Definition 2153 The "contact" CSV File Definition defines the fields and CSV file 2154 references used for the contact object records. 2156 The following "csvContact" field elements MUST be used in the 2157 "contact" element: 2159 Contains the server-unique contact identifier with 2160 type="eppcom:clIDType" and isRequired="true". 2162 Contains the contact's email address with 2163 type="eppcom:minTokenType" and isRequired="true". 2165 The following field elements MAY be used in the "contact" 2166 element: 2168 Contains the contact's voice telephone number 2169 with type="contact:e164StringType". 2171 Contains the contact's voice telephone number 2172 extension with type="token". 2174 Contains the contact's facsimile telephone number 2175 with type="contact:e164StringType". 2177 Contains the contact's facsimile telephone 2178 number extension with type="token". 2180 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 2181 "contact" element: 2183 The Registry Object IDentifier (ROID) for the contact 2184 object with isRequired="true". 2186 or A choice of: 2188 Identifier of the sponsoring client with 2189 isRequired="true". 2191 Contains the ID assigned by ICANN with 2192 type="positiveInteger". The attribute "isRequired" MUST equal 2193 "true". 2195 The following "rdeCsv" fields, defined in section CSV common field 2196 elements (Section 4.6.2.2), MAY be used in the "contact" 2197 element: 2199 Identifier of the registrar, defined in Section 5.4, 2200 of the client that created the object. 2202 Identifier of the client that created the contact 2203 object. 2205 Identifier of the registrar, defined in Section 5.4, 2206 of the client that updated the object. 2208 Identifier of the client that last updated the 2209 contact object. 2211 Created date and time of the contact object. 2213 Date and time of the last update to the contact 2214 object. 2216 Date and time of the last transfer for the contact 2217 object. 2219 Example of a "contact" element. 2221 ... 2222 2223 ... 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2244 contact-YYYYMMDD.csv 2245 2246 2247 2248 ... 2249 2250 ... 2252 Example of the contact-YYYYMMDD.csv file. The file contains nine 2253 object contact records. 2255 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2256 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2257 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2258 2009-11-26T09:10:00.0Z 2259 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2260 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2261 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2262 2009-11-26T09:10:00.0Z 2263 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2264 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2265 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2266 2009-11-26T09:10:00.0Z 2267 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2268 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2269 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2270 2009-11-26T09:10:00.0Z 2271 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2272 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2273 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2274 2009-11-26T09:10:00.0Z 2275 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2276 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2277 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2278 2009-11-26T09:10:00.0Z 2279 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2280 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2281 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2282 2009-11-26T09:10:00.0Z 2283 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2284 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2285 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2286 2009-11-26T09:10:00.0Z 2287 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2288 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2289 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2290 2009-11-26T09:10:00.0Z 2292 5.3.2.1.2. "contactStatuses" CSV File Definition 2294 The "contactStatuses" CSV File Definition defines the fields and CSV 2295 file references used for the contact object statuses. 2297 The following "csvContact" field elements, defined for the "contact" 2298 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2299 "contactStatuses" element: 2301 Server-unique contact identifier of status with 2302 isRequired="true". 2304 The status of the contact with 2305 type="contact:statusValueType" and isRequired="true". 2307 The following "rdeCsv" fields, defined in section CSV common field 2308 elements (Section 4.6.2.2), MAY be used in the "contactStatuses" 2309 element: 2311 The contact object status description 2312 which is free form text describing the rationale for the status. 2314 Language of the field. 2316 Example of a "contactStatuses" 2317 element. 2319 ... 2320 2321 ... 2322 2323 2324 2325 2326 2327 2328 2329 2330 2332 contactStatuses-YYYYMMDD.csv 2333 2334 2335 2336 ... 2337 2338 ... 2340 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2341 file contains the statuses for the nine contact identifiers. 2343 domain1admin,ok,, 2344 domain1tech,ok,, 2345 domain1billing,ok,, 2346 domain2admin,ok,, 2347 domain2tech,ok,, 2348 domain2billing,ok,, 2349 xnabc123admin,ok,, 2350 xnabc123tech,ok,, 2351 xnabc123billing,ok,, 2353 5.3.2.1.3. "contactPostal" CSV File Definition 2355 The "contactPostal" CSV File Definition defines the fields and CSV 2356 file references used for the contact postal info object records. 2358 The following "csvContact" field elements MUST be used in the 2359 "contactPostal" element: 2361 Contains the form of the postal-address 2362 information with type="contact:postalLineType" and 2363 isRequired="true". This field specifies the form ("int" or 2364 "loc"), as defined in Section 4.6.3, of the , 2365 , , , 2366 , , fields. 2368 Contains the contact's name of the individual or 2369 role represented by the contact with type="contact:postalLineType" 2370 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2371 indicate the localized or internationalized form as defined in 2372 section Section 4.6.3. 2374 Contains the contact's contact's street address 2375 line with type="contact:fPostalLineType". An index attribute is 2376 required to indicate which street address line the field 2377 represents with index "0" for the first line and index "2" for the 2378 last line. An OPTIONAL "isLoc" attribute to used to indicate the 2379 localized or internationalized form as defined in section 2380 Section 4.6.3. 2382 Contains the contact's city with 2383 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2384 "isLoc" attribute to used to indicate the localized or 2385 internationalized form as defined in section Section 4.6.3. 2387 Contains the contact's country code with 2388 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2389 attribute to used to indicate the localized or internationalized 2390 form as defined in section Section 4.6.3. 2392 The following "csvContact" field elements MAY be used in the 2393 "contactPostal" element: 2395 Contains the name of the organization with which 2396 the contact is affiliated with type="contact:optPostalLineType". 2397 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2398 internationalized form as defined in section Section 4.6.3. 2400 Contains the contact's state or province with 2401 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2402 to used to indicate the localized or internationalized form as 2403 defined in section Section 4.6.3. 2405 Contains the contact's postal code with 2406 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2407 indicate the localized or internationalized form as defined in 2408 section Section 4.6.3. 2410 The following "csvContact" fields, defined for the "contact" CSV File 2411 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2412 element: 2414 Server-unique contact identifier for the contact 2415 object with isRequired="true". 2417 Example of a "contactPostal" 2418 element. 2420 ... 2421 2422 ... 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2440 contactPostal-YYYYMMDD.csv 2441 2442 2443 2444 ... 2445 2446 ... 2448 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2449 nine contact postal records. 2451 domain1admin,int,"John Doe","Example Inc.", 2452 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2453 domain1tech,int,"John Doe","Example Inc.", 2454 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2455 domain1billing,int,"John Doe","Example Inc.", 2456 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2457 domain2admin,int,"John Doe","Example Inc.", 2458 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2459 domain2tech,int,"John Doe","Example Inc.", 2460 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2461 domain2billing,int,"John Doe","Example Inc.", 2462 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2463 xnabc123admin,int,"John Doe","Example Inc.", 2464 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2465 xnabc123tech,int,"John Doe","Example Inc.", 2466 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2467 xnabc123billing,int,"John Doe","Example Inc.", 2468 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2470 5.3.2.1.4. "contactTransfer" CSV File Definition 2472 The "contactTransfer" CSV File Definition defines the fields and CSV 2473 file references used for the contact object pending and completed 2474 transfer records. No additional field elements were added for use in 2475 the "contactTransfer" element. The 2476 following "rdeCsv" fields, defined in section CSV common field 2477 elements (Section 4.6.2.2), MUST be used in the "contactTransfer" 2478 element: 2480 State of the most recent transfer request with 2481 isRequired="true". 2483 Identifier of the registrar, defined in Section 5.4, 2484 of the client that requested the transfer with isRequired="true". 2486 Date and time that the transfer was requested with 2487 isRequired="true". 2489 Identifier of the registrar, defined in Section 5.4, 2490 of the client that should take or took action with 2491 isRequired="true". 2493 Date and time that the transfer action should be 2494 taken or has been taken with isRequired="true". 2496 The following "rdeCsv" fields, defined in section CSV common field 2497 elements (Section 4.6.2.2), MAY be used in the "contactTransfer" 2498 element: 2500 Identifier of the client that requested the transfer. 2502 Identifier of the client that should take or took 2503 action for transfer. 2505 The following "csvContact" fields, defined for the "contact" CSV File 2506 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2507 element: 2509 Server-unique contact identifier for the contact 2510 object with isRequired="true". 2512 Example of a "contactTransfer" 2513 element. 2515 ... 2516 2517 ... 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2532 contactTransfer-YYYYMMDD.csv 2533 2534 2535 2536 ... 2537 2538 ... 2540 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2541 one contact transfer record in pending status. 2543 xnabc123admin,clientApproved,registrarX,clientX, 2544 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2546 5.3.2.1.5. "contactDisclose" CSV File Definition 2548 The "contactDisclose" CSV File Definition defines the fields and CSV 2549 file references used for the contact disclose object records. 2551 The following "csvContact" field elements MAY be used in the 2552 "contactDisclose" element: 2554 Contains flag with a value of "true" or 2555 "1" (one) notes the preference to allow disclosure of the 2556 specified elements as an exception to the stated data-collection 2557 policy. A value of "false" or "0" (zero) notes a client 2558 preference to not allow disclosure of the specified elements as an 2559 exception to the stated data-collection policy with 2560 type="boolean". The additional fields define specific exceptional 2561 disclosure preferences based on the 2562 field. 2564 Exceptional disclosure preference flag 2565 for the localized form of the contact name with type="boolean". 2567 Exceptional disclosure preference flag 2568 for the internationalized form of the contact name with 2569 type="boolean". 2571 Exceptional disclosure preference flag 2572 for the localized form of the contact organization with 2573 type="boolean". 2575 Exceptional disclosure preference flag 2576 for the internationalized form of the contact organization with 2577 type="boolean". 2579 Exceptional disclosure preference flag 2580 for the localized form of the contact address with type="boolean". 2582 Exceptional disclosure preference flag 2583 for the internationalized form of the contact address with 2584 type="boolean". 2586 Exceptional disclosure preference flag 2587 of the contact voice telephone number with type="boolean". 2589 Exceptional disclosure preference flag of 2590 the contact facsimile telephone number with type="boolean". 2592 Exceptional disclosure preference flag 2593 of the contact email address with type="boolean". 2595 The following "csvContact" fields, defined for the "contact" CSV File 2596 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2597 element: 2599 Server-unique contact identifier for the contact 2600 object with isRequired="true". 2602 Example of a "contactDisclose" 2603 element. 2605 ... 2606 2607 ... 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2625 contactDisclose-YYYYMMDD.csv 2626 2627 2628 2629 ... 2630 2631 ... 2633 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2634 one disclosure records, disabling disclosure of voice, fax, and 2635 email. 2637 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2639 5.3.2.2. 2641 The is used to hold the deleted contact objects 2642 in a differential or incremental deposit. All the contact object 2643 data is deleted as part of a cascade delete. The 2644 is split into separate CSV file definitions 2645 using named elements with the "name" attribute. The 2646 following section defines the supported contact deletes CSV file 2647 definition. 2649 5.3.2.2.1. "contact" Deletes CSV File Definition 2651 The following "csvContact" field elements MUST be used in the deletes 2652 "contact" element: 2654 Contains the server-unique contact identifier with 2655 type="eppcom:clIDType" and isRequired="true". 2657 Example of a "contact" element. 2659 ... 2660 2661 ... 2662 2663 2664 2665 2666 2667 2669 contact-delete-YYYYMMDD.csv 2670 2671 2672 2673 ... 2674 2675 ... 2677 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2678 six contact records. 2680 domain1admin 2681 domain1tech 2682 domain1billing 2683 domain2admin 2684 domain2tech 2685 domain2billing 2687 5.4. Registrar Object 2689 The registrar object represents the sponsoring client for other 2690 objects, for operational purposes MAY be the registry operator. The 2691 registrar object supports both the XML Model and the CSV Model, 2692 defined in Section 2. The elements used for both models are defined 2693 in the following sections. 2695 5.4.1. XML Model 2697 There are two elements used in the data escrow of the registrar 2698 objects for the XML model including the , 2699 under the element, and the 2700 element, under the element. 2702 A element substitutes for the 2703 abstract element to define a 2704 concrete definition of a registrar. The 2705 element can be replaced by other 2706 domain definitions using the XML schema substitution groups feature. 2708 5.4.1.1. element 2710 The element contains the following child elements: 2712 o An element that contains the Registry-unique identifier of 2713 the registrar object. This has a superordinate relationship 2714 to a subordinate , or of domain, contact and 2715 host objects. 2717 o An element that contains the name of the registrar. 2719 o An OPTIONAL element that contains the ID assigned by 2720 ICANN. 2722 o An OPTIONAL element that contains the operational status 2723 of the registrar. Possible values are: ok, readonly and 2724 terminated. 2726 o Zero or two OPTIONAL elements that contain postal- 2727 address information. Two elements are provided so that address 2728 information can be provided in both internationalized and 2729 localized forms; a "type" attribute is used to identify the two 2730 forms. If an internationalized form (type="int") is provided, 2731 element content MUST be represented in a subset of UTF-8 that can 2732 be represented in the 7-bit US-ASCII character set. If a 2733 localized form (type="loc") is provided, element content MAY be 2734 represented in unrestricted UTF-8. The element 2735 contains the following child elements: 2737 * A element that contains address information associated 2738 with the registrar. The element contains the following 2739 child elements: 2741 + One, two, or three OPTIONAL elements that contain 2742 the registrar's street address. 2744 + A element that contains the registrar's city. 2746 + An OPTIONAL element that contains the registrar's state 2747 or province. 2749 + An OPTIONAL element that contains the registrar's 2750 postal code. 2752 + A element that contains the registrar's country code. 2754 o An OPTIONAL element that contains the registrar's voice 2755 telephone number. 2757 o An OPTIONAL element that contains the registrar's facsimile 2758 telephone number. 2760 o An OPTIONAL element that contains the registrar's email 2761 address. 2763 o An OPTIONAL element that contains the registrar's URL. 2765 o An OPTIONAL elements that contains whois information. 2766 The element contains the following child elements: 2768 * An OPTIONAL element that contains the name of the 2769 registrar WHOIS server listening on TCP port 43 as specified in 2770 [RFC3912]. 2772 * An OPTIONAL element that contains the name of the 2773 registrar WHOIS server listening on TCP port 80/443. 2775 o An OPTIONAL element that contains the date and time of 2776 registrar-object creation. 2778 o An OPTIONAL element that contains the date and time of 2779 the most recent RDE registrar-object modification. This element 2780 MUST NOT be present if the rdeRegistrar object has never been 2781 modified. 2783 Example of object: 2785 ... 2786 2787 RegistrarX 2788 Registrar X 2789 123 2790 ok 2791 2792 2793 123 Example Dr. 2794 Suite 100 2795 Dulles 2796 VA 2797 20166-6503 2798 US 2799 2800 2801 +1.7035555555 2802 +1.7035555556 2803 jdoe@example.example 2804 http://www.example.example 2805 2806 whois.example.example 2807 http://whois.example.example 2808 2809 2005-04-23T11:49:00.0Z 2810 2009-02-17T17:51:00.0Z 2811 2812 ... 2814 5.4.1.2. object 2816 The element contains the id of a registrar that 2817 was deleted. 2819 Example of object: 2821 ... 2822 2823 ... 2824 2825 agnt0001-TEST 2826 2827 ... 2828 2829 ... 2831 5.4.2. CSV Model 2833 For the CSV Model of the registrar object, the 2834 child element of the element 2835 is used to hold the new or updated registrar objects for the deposit. 2836 The child element of the element 2837 is used to hold the deleted or purged registrar objects for the 2838 deposit. Both the and 2839 elements contain one or more elements with a set of 2840 named CSV file definitions using the "name" attribute. 2842 Differential and incremental deposits are based on changes to the 2843 registrar objects. The updated registrar object data under the 2844 element is a cascade replace down all of the 2845 registrar CSV files starting with the parent "registrar" CSV File 2846 Definition (Section 5.4.2.1.1). The child CSV file definitions 2847 include a field. All the child CSV 2848 file definition data for the registrar objects in the parent 2849 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2850 deleted and then set using the data in the child CSV files. The 2851 deleted registrar object data under the 2852 element is a cascade delete starting from the "registrar" Deletes CSV 2853 File Definition (Section 5.4.2.2.1). 2855 5.4.2.1. 2857 The is used to hold the new or updated 2858 registrar object information for the deposit. The 2859 is split into separate CSV file definitions 2860 using named elements with the "name" attribute. The 2861 following sections include the supported contact CSV file 2862 definitions. 2864 5.4.2.1.1. "registrar" CSV File Definition 2866 The "registrar" CSV File Definition defines the fields and CSV file 2867 references used for the registrar object records. 2869 The following "csvRegistrar" field elements MUST be used in the 2870 "registrar" element: 2872 or A choice of: 2874 Contains the server-unique registrar 2875 identifier with type="eppcom:clIDType" and isRequired="true". 2877 Contains the ID assigned by ICANN with 2878 type="positiveInteger". The attribute "isRequired" MUST equal 2879 "true". 2881 Contains the name of the registrar with 2882 type="normalizedString" and isRequired="true". 2884 The following field elements MAY be used in the "registrar" 2885 element: 2887 Contains the status of the registrar with 2888 type="csvRegistrar:statusValueType". 2890 Contains the ID assigned by ICANN with 2891 type="positiveInteger". This field is included in this section in 2892 addition to the section above to support optionally providing the 2893 field when the field is 2894 used. 2896 Contains the Whois URL of the registrar 2897 with type="anyURI". 2899 The following "rdeCsv" fields, defined in section CSV common field 2900 elements (Section 4.6.2.2), MAY be used in the "registrar" 2901 element: 2903 Created date and time of the registrar object. 2905 Date and time of the last update to the registrar 2906 object. 2908 URL for the registrar web home page. 2910 The following "csvContact" fields, defined in section Contact Object 2911 (Section 5.3), MAY be used in the "registrar" 2912 element: 2914 Registrar street address line with an "index" 2915 attribute that represents the order of the street address line 2916 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2917 indicate the localized or internationalized form, as defined in 2918 Section 4.6.3. 2920 Registrar city with an OPTIONAL "isLoc" attribute 2921 that is used to indicate the localized or internationalized form, 2922 as defined in Section 4.6.3. 2924 Registrar country code with an OPTIONAL "isLoc" 2925 attribute that is used to indicate the localized or 2926 internationalized form, as defined in Section 4.6.3. 2928 Registrar email address. The attribute 2929 "isRequired" MUST equal "false". 2931 Registrar state or province with an OPTIONAL 2932 "isLoc" attribute that is used to indicate the localized or 2933 internationalized form, as defined in Section 4.6.3. 2935 Registrar postal code with an OPTIONAL "isLoc" 2936 attribute that is used to indicate the localized or 2937 internationalized form, as defined in Section 4.6.3. 2939 Registrar voice telephone number. 2941 Registrar voice telephone number extension. 2943 Registrar facsimile telephone number. 2945 Registrar facsimile telephone number extension. 2947 Example of a "registrar" 2948 element. 2950 ... 2951 2952 ... 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2979 registrar-YYYYMMDD.csv 2980 2981 2982 2983 ... 2984 2985 ... 2987 Example of the registrar-YYYYMMDD.csv file. The file contains three 2988 registrar records. 2990 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 2991 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2992 +1.7035555556,,jdoe@example.example,http://www.example.example, 2993 http://whois.example.example,2005-04-23T11:49:00.0Z, 2994 2009-02-17T17:51:00.0Z 2995 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 2996 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2997 +1.7035555556,,jdoe@example.example,http://www.example.example, 2998 http://whois.example.example,2005-04-23T11:49:00.0Z, 2999 2009-02-17T17:51:00.0Z 3000 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 3001 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3002 +1.7035555556,,jdoe@example.example,http://www.example.example, 3003 http://whois.example.example,2005-04-23T11:49:00.0Z, 3004 2009-02-17T17:51:00.0Z 3006 5.4.2.2. 3008 The is used to hold the deleted registrar 3009 objects in a differential or incremental deposit. All the registrar 3010 object data is deleted as part of a cascade delete. The 3011 is split into separate CSV file definitions 3012 using named elements with the "name" attribute. The 3013 following section defines the supported registrar deletes CSV file 3014 definition. 3016 5.4.2.2.1. "registrar" Deletes CSV File Definition 3018 The following "csvRegistrar" field elements MUST be used in the 3019 deletes "registrar" element: 3021 or A choice of: 3023 Contains the server-unique registrar 3024 identifier with type="eppcom:clIDType" and isRequired="true". 3026 Contains the ID assigned by ICANN with 3027 type="positiveInteger". The attribute "isRequired" MUST equal 3028 "true". 3030 Example of a "registrar" element. 3032 ... 3033 3034 ... 3035 3036 3037 3038 3039 3040 3042 registrar-delete-YYYYMMDD.csv 3043 3044 3045 3046 ... 3047 3048 ... 3050 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 3051 one registrar record. 3053 registrarZ 3055 5.5. IDN Table Reference Object 3057 The Internationalized Domain Names (IDN) table reference object is a 3058 pseudo-object that is used to provide a short reference to the IDN 3059 Table and Policy used in IDN registrations. The IDN reference object 3060 supports both the XML and the CSV Model, defined in the Models 3061 (Section 2) section. The elements used for both models are defined 3062 in the following sections. 3064 5.5.1. XML Model 3066 There is one element used in the data escrow of the IDN table 3067 reference objects for the XML model that is the , 3068 under the element. 3070 5.5.1.1. object 3072 The contains the following elements. An "id" 3073 attribute is used to specify an identifier for the IDN table. 3075 o An element that contains the URL of the IDN table that is 3076 being referenced. 3078 o A element that contains the URL of the IDN policy 3079 document. If IDN variants are generated algorithmically, the 3080 policy document MUST define the algorithm and the state of the 3081 implicit generated IDN variants. For a list of suggested states 3082 for implicit IDN variants, please see [variantTLDsReport]. 3084 Example of object: 3086 ... 3087 3088 3089 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3090 3091 3092 http://registro.br/dominio/regras.html 3093 3094 3095 ... 3097 5.5.2. CSV Model 3099 The IDN domain names, defined in Section 5.1, MAY have references to 3100 the IDN language identifier using the field 3101 element. The IDN table reference object defines the mapping of a 3102 language identifier to a language table URL. The language table URL 3103 defines the character code points that can be used for the language 3104 identifier. The elements used for the IDN table reference object is 3105 defined in this section. The child element of the 3106 element is used to hold the new or updated IDN table 3107 reference objects for the deposit. The child 3108 element of the element is used to hold the deleted or 3109 purged IDN table reference objects for the deposit. Both the 3110 and elements contain one or more 3111 elements with a set of named CSV file definitions using 3112 the "name" attribute. 3114 5.5.2.1. 3116 The is used to hold the new or updated IDN table 3117 reference object information for the deposit. The 3118 is split into separate CSV file definitions using named 3119 elements with the "name" attribute. The following sections include 3120 the supported IDN table reference CSV file definitions. 3122 5.5.2.1.1. "idnLanguage" CSV File Definition 3124 The "idnLanguage" CSV File Definition defines the fields and CSV file 3125 references used for the IDN table reference object records. 3127 The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be 3128 used in the "idnLanguage" element: 3130 The language identifier that matches the values 3131 for the field element in the "domain" CSV 3132 File Definition (Section 5.1.2.1.1) files. The attribute 3133 "isRequired" MUST equal "true". 3135 URL that defines the character code points that can be 3136 used for the language defined by the field element. 3137 The attribute "isRequired" MUST equal "true". 3139 Example of a "idnLanguage" element. 3141 ... 3142 3143 ... 3144 3145 3146 3147 3148 3149 3150 3152 idnLanguage-YYYYMMDD.csv 3153 3154 3155 3156 ... 3157 3158 ... 3160 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3161 contains two IDN language records. 3163 LANG-1, 3164 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3165 LANG-2, 3166 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3168 5.5.2.2. 3170 The is used to hold the deleted IDN table reference 3171 objects in a differential or incremental deposit. The 3172 is split into separate CSV file definitions using 3173 named elements with the "name" attribute. The following 3174 section defines the supported IDN table reference deletes CSV file 3175 definition. 3177 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3179 The following "idnLanguage" field elements MUST be used in the 3180 deletes "idnLanguage" element: 3182 The language identifier that matches the values 3183 for the field element in the "domain" CSV 3184 File Definition (Section 5.1.2.1.1) files. The attribute 3185 "isRequired" MUST equal "true". 3187 Example of a "idnLanguage" element. 3189 ... 3190 3191 ... 3192 3193 3194 3195 3196 3197 3199 idnLanguage-delete-YYYYMMDD.csv 3200 3201 3202 3203 ... 3204 3205 ... 3207 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3208 contains one IDN language record. 3210 LANG-2 3212 5.6. NNDN Object 3214 A NNDN (NNDN's not domain name) can be used to store registry 3215 reserved names or (blocked, withheld or mirrored) IDN variants. 3217 Domain Name Registries may maintain domain names without them being 3218 persisted as domain objects in the registry system, for example, a 3219 list of reserved names not available for registration. The NNDN is a 3220 lightweight domain-like object that is used to escrow domain names 3221 not maintained as domain name objects. 3223 A domain name can only exist as a domain name object or NNDN object, 3224 but not both. 3226 The NNDN object supports both the XML and the CSV Model, defined in 3227 the Models (Section 2) section. The elements used for both models 3228 are defined in the following sections. 3230 5.6.1. XML Model 3232 There are two elements used in the data escrow of the NNDN objects 3233 for the XML model including the , under the 3234 element, and the element, under the 3235 element. 3237 A element substitutes for the 3238 abstract element to define a concrete definition of a NNDN. The 3239 element can be replaced by other NNDN 3240 definitions using the XML schema substitution groups feature. 3242 5.6.1.1. object 3244 The element contains the following child elements: 3246 o An element that contains the fully qualified name of the 3247 NNDN. If the NNDN is an IDN, the ASCII Compatible Encoding (ACE) 3248 MUST be used. 3250 o An OPTIONAL element that contains the fully qualified name 3251 of the NNDN in Unicode character set. It MUST be provided if 3252 available. 3254 o An OPTIONAL element that references the IDN 3255 Table used for the NNDN. This corresponds to the "id" attribute 3256 of the element. This element MUST be present if the 3257 NNDN is an IDN. 3259 o An OPTIONAL element is used to indicate that the 3260 NNDN is used for an IDN variant. This element contains the domain 3261 name used to generate the IDN variant. 3263 o A element that indicates the state of the NNDN: 3264 blocked, withheld or mirrored. 3266 * If a NNDN is considered undesirable for registration (i.e., 3267 unavailable for allocation to anyone), then the NNDN will be 3268 tagged as "blocked". 3270 * If a NNDN is considered a potential registration of a domain 3271 object for a registrant, then the NNDN will be tagged as 3272 "withheld". This status is only used when the NNDN is used for 3273 an IDN variant. 3275 * If a NNDN is considered a mirrored IDN variant of a domain 3276 object, then the NNDN will be tagged as "mirrored". A 3277 mirroringNS attribute is used to specify if the mirrored IDN 3278 variant use the NS mirror mechanism. The default value of 3279 mirroringNS is true. If another mechanism such as DNAME is 3280 used, the value of mirroringNS attribute MUST be false. 3282 o An OPTIONAL element that contains the date and time of 3283 the NNDN object creation. 3285 Example of object: 3287 ... 3288 3289 xn--exampl-gva.example 3290 pt-BR 3291 example1.example 3292 withheld 3293 2005-04-23T11:49:00.0Z 3294 3295 ... 3297 5.6.1.2. object 3299 The element contains the ACE of a NNDN that was 3300 deleted, i.e., the . 3302 Example of object: 3304 ... 3305 3306 ... 3307 3308 xn--pingino-q2a.example 3309 3310 ... 3311 3312 ... 3314 5.6.2. CSV Model 3316 For the CSV Model of the NNDN object, the child 3317 element of the element is used to hold the new or 3318 updated NNDN objects for the deposit. The child 3319 element of the element is used to hold the deleted or 3320 purged NNDN objects for the deposit. Both the and 3321 elements contain one or more elements 3322 with a set of named CSV file definitions using the 3323 "name" attribute. 3325 5.6.2.1. 3327 The is used to hold the new or updated NNDN object 3328 information for the deposit. The is split into 3329 separate CSV file definitions using named elements with 3330 the "name" attribute. The following sections include the supported 3331 NNDN CSV file definitions. 3333 5.6.2.1.1. "NNDN" CSV File Definition 3335 The "NNDN" CSV File Definition defines the fields and CSV file 3336 references used for the NNDN object records. 3338 The following "csvNNDN" field elements MUST be used in the "NNDN" 3339 element: 3341 ASCII Compatible Encoding (ACE) field of the NNDN 3342 with type="eppcom:labelType" and isRequired="true". 3344 State of the NNDN: blocked or withheld with 3345 type="rdeNNDN:nameState" and isRequired="true". See 3346 Section 5.6.1.1 for a description of the possible values for the 3347 element. 3349 The following field elements MAY be used in the "NNDN" 3350 element: 3352 Domain name used to generate the IDN variant 3353 with type="eppcom:labelType". 3355 Defines whether the "mirroring" 3356 uses the NS mirror mechanism, as described 3357 for the "mirroringNS" attribute in 3358 Section 5.6.1.1, with type="boolean". If the field element is not 3359 defined the default value is "true". 3361 The following "rdeCsv" fields, defined in section CSV common field 3362 elements (Section 4.6.2.2), MAY be used in the "NNDN" 3363 element: 3365 Created date and time of the NNDN object. 3367 Name of the NNDN in Unicode character set for the 3368 field element. 3370 IDN Table Identifier for the NNDN that matches 3371 an IDN Table Reference Object record, as defined in Section 5.5.2. 3373 Example of a "NNDN" element: 3375 ... 3376 3377 ... 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3390 NNDN-YYYYMMDD.csv 3391 3392 3393 3394 ... 3395 3396 ... 3398 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3399 contains two NNDN records for an IDN with one blocked variant and one 3400 mirrored variant. 3402 xn--abc456.example,LANG-1,xn--abc123.example, 3403 blocked,,2005-04-23T11:49:00.0Z 3404 xn--abc789.example,LANG-1,xn--abc123.example, 3405 mirrored,1,2005-04-23T11:49:00.0Z 3407 5.6.2.2. 3409 The is used to hold the deleted NNDN objects in a 3410 differential or incremental deposit. The is split 3411 into separate CSV file definitions using named elements 3412 with the "name" attribute. The following section defines the 3413 supported NNDN deletes CSV file definition. 3415 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3417 The following "NNDN" field elements MUST be used in the deletes 3418 "NNDN" element: 3420 ASCII Compatible Encoding (ACE) field of the NNDN 3421 with type="eppcom:labelType" and isRequired="true". 3423 Example of a "NNDN" element. 3425 ... 3426 3427 ... 3428 3429 3430 3431 3432 3433 3435 NNDN-delete-YYYYMMDD.csv 3436 3437 3438 3439 ... 3440 3441 ... 3443 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3444 contains one NNDN records. 3446 xn--abc456.example 3448 5.7. EPP Parameters Object 3450 The EPP Parameters Object is a pseudo-object that defines the set of 3451 object and object extension services supported by the registry, as 3452 defined in [RFC5730]. The EPP Parameters Object is only defined as 3453 XML but could be used in the XML model or CSV model. The EPP 3454 Parameters Object is defined using the 3455 element. The EPP Parameters Object SHOULD be included if the 3456 registry supports EPP. Only one EPP Parameters Object MUST exist at 3457 a certain point in time (watermark). 3459 The syntax and content of the children 3460 elements is as explained in section 2.4 of [RFC5730]. The children 3461 of the are as follows: 3463 o One or more elements that indicate the EPP versions 3464 supported by the registry. 3466 o One or more elements that indicate the identifiers of the 3467 text response languages supported by the registry's EPP server. 3469 o One or more elements that contain namespace URIs 3470 representing the objects that the registry's EPP server is capable 3471 of managing. 3473 o An OPTIONAL element that contains one or more 3474 elements that contain namespace URIs representing object 3475 extensions supported by the registry's EPP server. 3477 o A element that contains child elements used to describe the 3478 server's privacy policy for data collection and management. See 3479 section 2.4 of [RFC5730] for more details. 3481 Example of element object: 3483 ... 3484 3485 1.0 3486 en 3487 urn:ietf:params:xml:ns:domain-1.0 3488 3489 urn:ietf:params:xml:ns:contact-1.0 3490 3491 urn:ietf:params:xml:ns:host-1.0 3492 3493 3494 urn:ietf:params:xml:ns:rgp-1.0 3495 urn:ietf:params:xml:ns:secDNS-1.1 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 ... 3516 5.8. Policy Object 3518 The Policy object is a pseudo-object that is used to specify which 3519 OPTIONAL elements from the XML Model are REQUIRED based on the 3520 business model of the registry. For the CSV Model, the OPTIONAL 3521 "isRequired" attribute of the elements, defined in 3522 Section 4.6.2.1, is used to specify which OPTIONAL fields are 3523 REQUIRED based on the business model of the registry. 3525 5.8.1. object 3527 The OPTIONAL contains the following attributes: 3529 o An that defines that the referenced is 3530 REQUIRED. 3532 o that defines the XPath of the element referenced by 3533 . 3535 Example of object: 3537 ... 3538 3540 ... 3542 5.9. Header Object 3544 The Header Object is a pseudo-object that is used to specify the 3545 number of objects in the repository at a specific point in time 3546 (watermark) regardless of the type of deposit: differential, full or 3547 incremental. The Header Object may also be used to provide 3548 additional information on the contents of the deposit. The Header 3549 Object is only defined as XML but one header object MUST always be 3550 present per escrow deposit regardless of using XML Model or CSV 3551 Model. The Header Object is defined using the 3552 element. 3554 5.9.1. object 3556 The contains the following elements: 3558 o A choice of one of the elements defined in the 3559 "repositoryTypeGroup" group element that indicates the unique 3560 identifier for the repository being escrowed. Possible elements 3561 are: 3563 * A element that defines TLD or the REGISTRY- 3564 CLASS DOMAIN NAME (RCDN) being escrowed in the case of a 3565 Registry data escrow deposit. For IDNs the A-Label is used 3566 [RFC5891]. 3568 * A element that defines the Registrar ID 3569 corresponding to a Registrar data escrow deposit. In the case 3570 of an ICANN-accredited Registrar, the 3571 element MUST be the IANA Registrar ID assigned by ICANN. 3573 * A element that defines the provider ID 3574 corresponding to a Privacy and Proxy Services Provider data 3575 escrow deposit. In the case of an ICANN-accredited Privacy and 3576 Proxy Services Provider, the element MUST be 3577 the unique ID assigned by ICANN. 3579 * A element that defines the provider ID 3580 corresponding to a Reseller data escrow deposit. 3582 o A element that contains the number of objects in the SRS 3583 at a specific point in time (watermark) regardless of the type of 3584 deposit: differential, full or incremental. The element 3585 supports the following attributes: 3587 * A "uri" attribute reflects the XML namespace URI of the primary 3588 objects for the XML Model and CSV Model. For example, the 3589 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3590 domain name objects using the XML Model, and the "uri" is set 3591 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3592 objects using the CSV Model. 3594 * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS 3595 DOMAIN NAME (RCDN) of the objects included in the 3596 element. For IDNs the A-Label is used [RFC5891]. If the 3597 "rcdn" attribute is present, the value of the element 3598 must include only objects related to registrations in the same 3599 and lower levels. For example in a data escrow deposit for the 3600 .EXAMPLE TLD, a value of "example" in the "rcdn" attribute 3601 within the element indicates the number of objects in 3602 the TLD including objects in other RCDNs within the TLD, 3603 whereas a value of "com.example" indicates the number of 3604 elements for objects under "com.example" and lower levels. 3605 Omitting the "rcdn" attribute indicates that the total includes 3606 all objects of the specified "uri" in the repository (e.g. the 3607 TLD, Registrar, or PPSP). 3609 * An OPTIONAL "registrarId" attribute indicates the identifier of 3610 the sponsoring Registrar of the objects included in the 3611 element. In the case of an ICANN-accredited Registrar, the 3612 value MUST be the IANA Registrar ID assigned by ICANN. 3614 o An OPTIONAL element that contains a tag that defines 3615 the expected content in the deposit. The producer and consumer of 3616 the deposits will coordinate the set of possible 3617 element values. 3619 Example of object referencing only the XML Model 3620 objects: 3622 ... 3623 3624 test 3625 2 3627 1 3629 1 3631 1 3633 3634 1 3636 1 3638 1 3640 3641 3642 ... 3644 Example of object referencing the CSV and XML 3645 Model objects: 3647 ... 3648 3649 test 3650 2 3652 1 3654 1 3656 1 3658 3659 1 3661 1 3663 1 3665 3666 3667 ... 3669 6. RDE IDN Variants handling 3671 Depending on the Registration Policy of the Registry; for a domain 3672 name there may be multiple variant names. See [variantTLDsReport] 3673 for further detail on IDN variants. 3675 A registry could choose to escrow IDN variants as domains or NNDN 3676 objects. A specific IDN variant can be represented in the escrow 3677 deposit, as a domain or as a NNDN object, but not both. 3679 If using domain objects to represent IDN variants, the normal 3680 behavior during restoration of a SRS based on an escrow deposit is to 3681 restore the IDN variants as a mirrored variant. If the registration 3682 data of the IDN variant is different from the original name, the 3683 details of this specific implementation MUST be described in the IDN 3684 policy document. 3686 A NNDN or a domain name are explicit representations of an IDN 3687 variant while an IDN variant computed based on an algorithm is an 3688 implicit representation. Explicit representation of an IDN variant 3689 takes precedence over an implicit representation. 3691 7. Profile 3693 Different business models of registries exist, therefore the registry 3694 is responsible to define a profile that matches its particular 3695 business model. The profile mechanism allows a registry to extend 3696 this specification. 3698 A profile is the process of: 3700 1. Extending base objects with the mechanisms defined for XML and 3701 CSV models. 3703 * In the case of the XML model, abstract elements could be use 3704 to extend the following objects: , , , 3705 and using XML schema substitution groups 3706 feature. 3708 2. Defining a object to specify which OPTIONAL elements of 3709 this base specification is required based on the business model 3710 of the registry. An example is the element that is 3711 usually REQUIRED but it is specified as OPTIONAL in this 3712 specification to support existing business models. 3714 3. Adding new escrowed objects using the and 3715 elements. 3717 4. Providing the XML schemas to third parties that require them to 3718 validate the escrow deposits. 3720 8. Data escrow agent extended verification process 3722 A Data Escrow Agent SHOULD perform an extended verification process 3723 that starts by creating a dataset to be tested. 3725 o If a full deposit is to be tested, the full deposit is the 3726 dataset. 3728 o If an incremental deposit is to be tested, the dataset is created 3729 by using the incremental plus the last previous full deposit. 3731 o If a differential deposit is to be tested, the dataset is created 3732 by using the differential deposit plus all the required deposits 3733 leading to the last previous full deposit. 3735 The following are the minimum suggested tests on the dataset: 3737 o Validate the escrow deposits using the definition agreed with the 3738 registry. 3740 * In the case of the XML model, the contents of the escrow 3741 deposits MUST be validated using the XML schemas of the 3742 profile. 3744 o Count the objects and validate that the number of objects is equal 3745 to the number objects reported in the
element of the 3746 escrow deposit of that point in time (watermark). 3748 o All contact objects linked to domain names MUST be present. 3750 o All registrars objects linked to other objects MUST be present. 3752 o A domain name exists as a domain name or NNDN, but not both. 3754 o The elements listed as required in the element MUST be 3755 present. 3757 o All idnTableRef definitions linked from other objects MUST be 3758 present. 3760 o If an EPP Parameters Object was escrowed in the past, one and only 3761 one EPP Parameters Object MUST be present. 3763 o The watermark is not in the future. 3765 9. Formal Syntax 3767 Schemas are presented here. 3769 9.1. RDE CSV Schema 3771 Copyright (c) 2012 IETF Trust and the persons identified as authors 3772 of the code. All rights reserved. 3774 Redistribution and use in source and binary forms, with or without 3775 modification, are permitted provided that the following conditions 3776 are met: 3778 o Redistributions of source code must retain the above copyright 3779 notice, this list of conditions and the following disclaimer. 3781 o Redistributions in binary form must reproduce the above copyright 3782 notice, this list of conditions and the following disclaimer in 3783 the documentation and/or other materials provided with the 3784 distribution. 3786 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3787 names of specific contributors, may be used to endorse or promote 3788 products derived from this software without specific prior written 3789 permission. 3791 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3792 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3793 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3794 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3795 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3796 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3797 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3798 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3799 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3800 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3801 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3803 BEGIN 3804 3806 3813 3816 3818 3821 3822 3823 Registry Data Escrow Comma-Seperated Values (CSV) 3824 3825 3827 3828 3830 3831 3832 3833 3834 3835 3836 3837 3838 3840 3841 3842 3843 3844 3845 3846 3848 3849 3852 3853 3854 3856 3857 3858 3859 3860 3861 3863 3865 3866 3867 3869 3870 3871 3872 3873 3874 3876 3878 3879 3880 3882 3883 3884 3886 3887 3888 3889 3890 3892 3893 3894 3895 3896 3897 3898 3899 3901 3902 3903 3905 3906 3908 3909 3910 3911 3912 3914 3915 3916 3918 3919 3921 3922 3923 3924 3925 3927 3928 3929 3930 3931 3935 3936 3937 3939 3941 3943 3944 3946 3948 3950 3951 3953 3955 3957 3959 3961 3963 3965 3967 3969 3970 3971 3972 3973 3975 3976 3977 3978 3979 3980 3981 3982 3984 3985 3986 3988 3989 3991 3993 3995 3996 3998 3999 4001 4003 4004 4005 4006 4007 4009 4010 4011 4012 4013 4014 4015 4016 4018 4019 4020 4022 4023 4024 4025 4026 4027 4029 4030 4031 4032 4033 4034 4035 4036 4038 4039 4040 4042 4043 4044 4045 4046 4047 4049 4050 4051 4052 4053 4054 4055 4056 4058 4059 4060 4062 4063 4064 4065 4066 4067 4069 4070 4071 4072 4073 4074 4075 4076 4078 4079 4080 4082 4083 4084 4085 4086 4087 4089 4090 4091 4092 4093 4094 4095 4096 4098 4099 4100 4102 4103 4105 4106 4107 4108 4109 4111 4112 4113 4115 4116 4119 4120 4122 4123 4124 4125 4126 4128 4129 4130 4132 4133 4134 4135 4136 4137 4139 4140 4141 4143 4144 4145 4146 4147 4148 4150 4151 4152 4154 4155 4156 4157 4158 4159 4161 4162 4163 4165 4166 4168 4169 4170 4171 4172 4173 4175 4176 4177 4179 4180 4181 4182 4183 4184 4186 4187 4188 4189 4191 4192 4194 4195 4196 4197 4198 4199 4201 4202 4203 4204 4206 4207 4209 4210 4211 4212 4213 4216 4217 4218 4220 4223 4224 END 4226 9.2. RDE Domain Object 4228 Copyright (c) 2019 IETF Trust and the persons identified as authors 4229 of the code. All rights reserved. 4231 Redistribution and use in source and binary forms, with or without 4232 modification, are permitted provided that the following conditions 4233 are met: 4235 o Redistributions of source code must retain the above copyright 4236 notice, this list of conditions and the following disclaimer. 4238 o Redistributions in binary form must reproduce the above copyright 4239 notice, this list of conditions and the following disclaimer in 4240 the documentation and/or other materials provided with the 4241 distribution. 4243 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4244 names of specific contributors, may be used to endorse or promote 4245 products derived from this software without specific prior written 4246 permission. 4248 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4249 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4250 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4251 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4252 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4253 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4254 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4255 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4256 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4257 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4258 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4260 BEGIN 4261 4262 4273 4274 4275 4276 4277 4278 4280 4281 4282 Registry Data Escrow Domain provisioning schema 4283 4284 4286 4289 4291 4295 4296 4297 4298 4299 4300 4302 4304 4306 4308 4310 4313 4316 4318 4321 4323 4325 4327 4329 4331 4333 4335 4337 4339 4342 4343 4344 4345 4347 4348 4349 4351 4353 4355 4357 4359 4362 4363 4365 4366 4367 4368 4369 4370 4373 4374 4375 4376 4377 4378 END 4380 9.3. CSV Domain Object 4382 Copyright (c) 2012 IETF Trust and the persons identified as authors 4383 of the code. All rights reserved. 4385 Redistribution and use in source and binary forms, with or without 4386 modification, are permitted provided that the following conditions 4387 are met: 4389 o Redistributions of source code must retain the above copyright 4390 notice, this list of conditions and the following disclaimer. 4392 o Redistributions in binary form must reproduce the above copyright 4393 notice, this list of conditions and the following disclaimer in 4394 the documentation and/or other materials provided with the 4395 distribution. 4397 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4398 names of specific contributors, may be used to endorse or promote 4399 products derived from this software without specific prior written 4400 permission. 4402 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4403 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4404 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4405 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4406 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4407 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4408 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4409 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4410 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4411 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4412 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4414 BEGIN 4415 4417 4428 4431 4433 4435 4437 4439 4441 4444 4445 4446 Domain Name Comma-Separated Values (CSV) Object 4447 4448 4450 4453 4456 4457 4458 4459 4460 4461 4462 4463 4464 4466 4469 4472 4473 4474 4475 4476 4477 4478 4479 4480 4482 4483 4486 4487 4490 4491 4492 4493 4494 4496 4497 4498 4500 4501 4504 4505 4506 4507 4508 4510 4511 4512 4514 4516 4517 4519 4520 4521 4522 4523 4525 4526 4527 4529 4530 4533 4534 4537 4538 4541 4542 4545 4546 4549 4550 4553 4554 4557 4558 4560 4561 4562 4563 4564 4566 4567 4568 4570 4571 4574 4575 4579 4580 4583 4584 4585 4586 4587 4588 4590 4591 4592 4594 4597 4598 END 4600 9.4. RDE Host Object 4602 Copyright (c) 2019 IETF Trust and the persons identified as authors 4603 of the code. All rights reserved. 4605 Redistribution and use in source and binary forms, with or without 4606 modification, are permitted provided that the following conditions 4607 are met: 4609 o Redistributions of source code must retain the above copyright 4610 notice, this list of conditions and the following disclaimer. 4612 o Redistributions in binary form must reproduce the above copyright 4613 notice, this list of conditions and the following disclaimer in 4614 the documentation and/or other materials provided with the 4615 distribution. 4617 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4618 names of specific contributors, may be used to endorse or promote 4619 products derived from this software without specific prior written 4620 permission. 4622 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4623 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4624 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4625 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4626 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4627 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4628 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4629 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4630 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4631 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4632 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4634 BEGIN 4635 4636 4644 4645 4646 4647 4648 4649 Registry Data Escrow Host provisioning schema 4650 4651 4653 4655 4656 4659 4660 4661 4662 4663 4664 4666 4668 4670 4673 4675 4677 4679 4681 4683 4685 4686 4687 4688 4690 4691 4692 4693 4694 4695 4697 4699 4700 4701 4702 4703 4704 END 4706 9.5. CSV Host Object 4708 Copyright (c) 2012 IETF Trust and the persons identified as authors 4709 of the code. All rights reserved. 4711 Redistribution and use in source and binary forms, with or without 4712 modification, are permitted provided that the following conditions 4713 are met: 4715 o Redistributions of source code must retain the above copyright 4716 notice, this list of conditions and the following disclaimer. 4718 o Redistributions in binary form must reproduce the above copyright 4719 notice, this list of conditions and the following disclaimer in 4720 the documentation and/or other materials provided with the 4721 distribution. 4723 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4724 names of specific contributors, may be used to endorse or promote 4725 products derived from this software without specific prior written 4726 permission. 4728 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4729 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4730 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4731 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4732 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4733 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4734 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4735 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4736 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4737 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4738 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4740 BEGIN 4741 4742 4751 4754 4756 4758 4760 4763 4764 4765 Host Comma-Separated Values (CSV) Object 4766 4767 4769 4772 4775 4776 4777 4778 4779 4780 4781 4782 4783 4785 4788 4790 4791 4792 4793 4794 4795 4796 4797 4798 4800 4801 4804 4805 4807 4808 4809 4810 4811 4813 4814 4815 4817 4818 4820 4821 4822 4823 4824 4826 4827 4828 4830 4831 4834 4835 4836 4837 4838 4839 4841 4842 4843 4845 4848 4849 END 4851 9.6. RDE Contact Object 4853 Copyright (c) 2019 IETF Trust and the persons identified as authors 4854 of the code. All rights reserved. 4856 Redistribution and use in source and binary forms, with or without 4857 modification, are permitted provided that the following conditions 4858 are met: 4860 o Redistributions of source code must retain the above copyright 4861 notice, this list of conditions and the following disclaimer. 4863 o Redistributions in binary form must reproduce the above copyright 4864 notice, this list of conditions and the following disclaimer in 4865 the documentation and/or other materials provided with the 4866 distribution. 4868 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4869 names of specific contributors, may be used to endorse or promote 4870 products derived from this software without specific prior written 4871 permission. 4873 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4874 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4875 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4876 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4877 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4878 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4879 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4880 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4881 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4882 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4883 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4885 BEGIN 4886 4887 4895 4896 4897 4898 4900 4901 4902 Registry Data Escrow contact provisioning schema 4903 4904 4906 4909 4911 4915 4916 4917 4918 4919 4920 4922 4924 4926 4928 4930 4932 4934 4936 4938 4940 4942 4944 4946 4948 4950 4951 4952 4953 4955 4956 4957 4958 4959 4960 4961 4962 4963 4965 4966 4967 4968 4969 4970 4973 4974 4975 4976 4977 4978 END 4980 9.7. CSV Contact Object 4982 Copyright (c) 2012 IETF Trust and the persons identified as authors 4983 of the code. All rights reserved. 4985 Redistribution and use in source and binary forms, with or without 4986 modification, are permitted provided that the following conditions 4987 are met: 4989 o Redistributions of source code must retain the above copyright 4990 notice, this list of conditions and the following disclaimer. 4992 o Redistributions in binary form must reproduce the above copyright 4993 notice, this list of conditions and the following disclaimer in 4994 the documentation and/or other materials provided with the 4995 distribution. 4997 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4998 names of specific contributors, may be used to endorse or promote 4999 products derived from this software without specific prior written 5000 permission. 5002 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5003 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5004 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5005 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5006 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5007 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5008 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5009 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5010 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5011 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5012 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5014 BEGIN 5015 5017 5026 5030 5032 5034 5036 5039 5040 5041 Contact Comma-Separated Values (CSV) Object 5042 5043 5045 5048 5051 5052 5053 5054 5055 5056 5057 5058 5059 5061 5064 5067 5068 5069 5070 5071 5072 5073 5074 5075 5077 5078 5080 5081 5082 5083 5084 5086 5087 5088 5090 5091 5095 5096 5098 5100 5101 5102 5103 5104 5106 5107 5108 5110 5111 5113 5116 5117 5119 5120 5121 5122 5123 5125 5126 5127 5129 5133 5135 5136 5137 5138 5139 5141 5142 5143 5145 5146 5147 5148 5149 5150 5152 5153 5154 5155 5157 5158 5159 5160 5161 5162 5164 5165 5166 5167 5168 5169 5172 5173 5176 5177 5178 5180 5181 5182 5183 5184 5186 5187 5188 5190 5191 5194 5195 5198 5199 5201 5202 5203 5204 5205 5207 5208 5209 5210 5212 5213 5215 5216 5217 5218 5219 5221 5222 5223 5224 5226 5227 5229 5231 5233 5235 5237 5239 5241 5243 5245 5247 5249 5251 5253 5255 5257 5259 5261 5263 5265 5267 5268 5269 5270 5271 5273 5274 5275 5277 5278 5281 5282 5283 5284 5285 5286 5288 5289 5290 5292 5295 5296 END 5298 9.8. RDE Registrar Object 5300 Copyright (c) 2019 IETF Trust and the persons identified as authors 5301 of the code. All rights reserved. 5303 Redistribution and use in source and binary forms, with or without 5304 modification, are permitted provided that the following conditions 5305 are met: 5307 o Redistributions of source code must retain the above copyright 5308 notice, this list of conditions and the following disclaimer. 5310 o Redistributions in binary form must reproduce the above copyright 5311 notice, this list of conditions and the following disclaimer in 5312 the documentation and/or other materials provided with the 5313 distribution. 5315 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5316 names of specific contributors, may be used to endorse or promote 5317 products derived from this software without specific prior written 5318 permission. 5320 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5321 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5322 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5323 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5324 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5325 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5326 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5327 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5328 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5329 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5330 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5332 BEGIN 5333 5334 5343 5344 5345 5346 5347 5349 5350 5351 Registry Data Escrow registrar provisioning schema 5352 5353 5355 5359 5361 5364 5365 5366 5367 5368 5369 5371 5373 5375 5377 5380 5382 5384 5386 5388 5390 5392 5394 5395 5396 5397 5399 5400 5401 5402 5403 5404 5406 5407 5408 5409 5410 5411 5412 5414 5415 5416 5418 5419 5422 5424 5425 5426 5427 5428 5429 5431 5432 5433 5436 5438 5441 5443 5445 5446 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 5460 5461 5462 5463 5464 5466 5467 5468 5469 5470 5472 5473 5474 5476 5478 5479 5481 5482 5483 5484 5485 5486 5489 5490 5491 5492 5493 5494 END 5496 9.9. CSV Registrar Object 5498 Copyright (c) 2012 IETF Trust and the persons identified as authors 5499 of the code. All rights reserved. 5501 Redistribution and use in source and binary forms, with or without 5502 modification, are permitted provided that the following conditions 5503 are met: 5505 o Redistributions of source code must retain the above copyright 5506 notice, this list of conditions and the following disclaimer. 5508 o Redistributions in binary form must reproduce the above copyright 5509 notice, this list of conditions and the following disclaimer in 5510 the documentation and/or other materials provided with the 5511 distribution. 5513 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5514 names of specific contributors, may be used to endorse or promote 5515 products derived from this software without specific prior written 5516 permission. 5518 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5519 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5520 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5521 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5522 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5523 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5524 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5525 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5526 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5527 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5528 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5530 BEGIN 5531 5533 5543 5546 5548 5550 5552 5554 5557 5558 5559 Registar Comma-Separated Values (CSV) Object 5560 5561 5563 5566 5569 5570 5571 5572 5573 5574 5575 5576 5577 5579 5582 5585 5586 5587 5588 5589 5590 5591 5592 5593 5595 5596 5599 5600 5603 5604 5605 5606 5607 5608 5610 5611 5612 5613 5615 5616 5620 5621 5623 5625 5626 5627 5628 5629 5631 5632 5633 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5650 5652 5653 5657 5660 5661 END 5663 9.10. RDE IDN Table Reference Objects 5665 Copyright (c) 2019 IETF Trust and the persons identified as authors 5666 of the code. All rights reserved. 5668 Redistribution and use in source and binary forms, with or without 5669 modification, are permitted provided that the following conditions 5670 are met: 5672 o Redistributions of source code must retain the above copyright 5673 notice, this list of conditions and the following disclaimer. 5675 o Redistributions in binary form must reproduce the above copyright 5676 notice, this list of conditions and the following disclaimer in 5677 the documentation and/or other materials provided with the 5678 distribution. 5680 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5681 names of specific contributors, may be used to endorse or promote 5682 products derived from this software without specific prior written 5683 permission. 5685 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5686 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5687 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5688 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5689 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5690 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5691 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5692 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5693 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5694 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5695 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5697 BEGIN 5698 5699 5705 5707 5708 5709 Registry Data Escrow IDN provisioning schema 5710 5711 5713 5715 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5731 5732 5733 5734 5735 5736 5737 5739 5740 5742 5743 5744 5745 5746 5747 5748 5750 5751 END 5753 9.11. CSV IDN Language Object 5755 Copyright (c) 2012 IETF Trust and the persons identified as authors 5756 of the code. All rights reserved. 5758 Redistribution and use in source and binary forms, with or without 5759 modification, are permitted provided that the following conditions 5760 are met: 5762 o Redistributions of source code must retain the above copyright 5763 notice, this list of conditions and the following disclaimer. 5765 o Redistributions in binary form must reproduce the above copyright 5766 notice, this list of conditions and the following disclaimer in 5767 the documentation and/or other materials provided with the 5768 distribution. 5770 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5771 names of specific contributors, may be used to endorse or promote 5772 products derived from this software without specific prior written 5773 permission. 5775 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5776 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5777 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5778 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5779 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5780 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5781 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5782 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5783 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5784 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5785 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5787 BEGIN 5788 5790 5797 5800 5802 5805 5806 5807 IDN Language Comma-Separated Values (CSV) Object 5808 5809 5811 5814 5817 5818 5819 5820 5821 5822 5823 5824 5825 5827 5830 5833 5834 5835 5836 5837 5838 5839 5840 5841 5843 5846 5847 END 5849 9.12. EPP Parameters Object 5851 Copyright (c) 2019 IETF Trust and the persons identified as authors 5852 of the code. All rights reserved. 5854 Redistribution and use in source and binary forms, with or without 5855 modification, are permitted provided that the following conditions 5856 are met: 5858 o Redistributions of source code must retain the above copyright 5859 notice, this list of conditions and the following disclaimer. 5861 o Redistributions in binary form must reproduce the above copyright 5862 notice, this list of conditions and the following disclaimer in 5863 the documentation and/or other materials provided with the 5864 distribution. 5866 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5867 names of specific contributors, may be used to endorse or promote 5868 products derived from this software without specific prior written 5869 permission. 5871 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5872 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5873 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5874 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5875 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5876 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5877 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5878 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5879 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5880 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5881 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5883 BEGIN 5884 5885 5893 5894 5895 5897 5898 5899 Registry Data Escrow EPP Parameters schema 5900 5901 5903 5904 5907 5908 5911 5912 5913 5914 5915 5917 5919 5921 5924 5926 5927 5928 5929 5930 5931 END 5933 9.13. NNDN Object 5935 Copyright (c) 2019 IETF Trust and the persons identified as authors 5936 of the code. All rights reserved. 5938 Redistribution and use in source and binary forms, with or without 5939 modification, are permitted provided that the following conditions 5940 are met: 5942 o Redistributions of source code must retain the above copyright 5943 notice, this list of conditions and the following disclaimer. 5945 o Redistributions in binary form must reproduce the above copyright 5946 notice, this list of conditions and the following disclaimer in 5947 the documentation and/or other materials provided with the 5948 distribution. 5950 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5951 names of specific contributors, may be used to endorse or promote 5952 products derived from this software without specific prior written 5953 permission. 5955 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5956 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5957 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5958 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5959 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5960 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5961 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5962 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5963 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5964 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5965 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5967 BEGIN 5968 5969 5977 5978 5979 5981 5982 5983 Registry Data Escrow NNDN provisioning schema 5984 5985 5987 5989 5990 5993 5994 5995 5996 5997 5998 6000 6002 6004 6006 6008 6010 6011 6012 6013 6015 6016 6017 6018 6019 6020 6021 6023 6024 6025 6026 6028 6029 6030 6032 6033 6034 6035 6036 6037 6040 6041 6042 6043 6044 6045 END 6047 9.14. CSV NNDN Object 6049 Copyright (c) 2013 IETF Trust and the persons identified as authors 6050 of the code. All rights reserved. 6052 Redistribution and use in source and binary forms, with or without 6053 modification, are permitted provided that the following conditions 6054 are met: 6056 o Redistributions of source code must retain the above copyright 6057 notice, this list of conditions and the following disclaimer. 6059 o Redistributions in binary form must reproduce the above copyright 6060 notice, this list of conditions and the following disclaimer in 6061 the documentation and/or other materials provided with the 6062 distribution. 6064 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6065 names of specific contributors, may be used to endorse or promote 6066 products derived from this software without specific prior written 6067 permission. 6069 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6070 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6071 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6072 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6073 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6074 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6075 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6076 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6077 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6078 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6079 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6081 BEGIN 6082 6084 6092 6095 6097 6099 6102 6103 6104 NNDN (NNDN's not domain name) (CSV) Object 6105 6106 6108 6111 6114 6115 6116 6117 6118 6119 6120 6121 6122 6123 6126 6129 6130 6131 6132 6133 6134 6135 6136 6137 6139 6140 6143 6144 6147 6148 6152 6153 6156 6157 6158 6159 6160 6162 6163 6164 6166 6167 6170 6173 6174 END 6176 9.15. Policy Object 6178 Copyright (c) 2019 IETF Trust and the persons identified as authors 6179 of the code. All rights reserved. 6181 Redistribution and use in source and binary forms, with or without 6182 modification, are permitted provided that the following conditions 6183 are met: 6185 o Redistributions of source code must retain the above copyright 6186 notice, this list of conditions and the following disclaimer. 6188 o Redistributions in binary form must reproduce the above copyright 6189 notice, this list of conditions and the following disclaimer in 6190 the documentation and/or other materials provided with the 6191 distribution. 6193 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6194 names of specific contributors, may be used to endorse or promote 6195 products derived from this software without specific prior written 6196 permission. 6198 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6199 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6200 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6201 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6202 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6203 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6204 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6205 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6206 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6207 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6208 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6210 BEGIN 6211 6212 6218 6219 6220 Registry Data Escrow Policy schema 6221 6222 6224 6225 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237 END 6239 9.16. Header Object 6241 Copyright (c) 2019 IETF Trust and the persons identified as authors 6242 of the code. All rights reserved. 6244 Redistribution and use in source and binary forms, with or without 6245 modification, are permitted provided that the following conditions 6246 are met: 6248 o Redistributions of source code must retain the above copyright 6249 notice, this list of conditions and the following disclaimer. 6251 o Redistributions in binary form must reproduce the above copyright 6252 notice, this list of conditions and the following disclaimer in 6253 the documentation and/or other materials provided with the 6254 distribution. 6256 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6257 names of specific contributors, may be used to endorse or promote 6258 products derived from this software without specific prior written 6259 permission. 6261 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6262 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6263 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6264 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6265 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6266 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6267 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6268 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6269 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6270 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6271 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6273 BEGIN 6274 6275 6282 6283 6285 6286 6287 Data Escrow Deposit Header schema 6288 6289 6291 6292 6295 6296 6297 6298 6299 6300 6301 6303 6305 6307 6308 6309 6311 6312 6313 6314 6315 6316 6317 6318 6320 6321 6322 6323 6324 6325 6326 6327 6328 6330 6331 END 6333 10. Internationalization Considerations 6335 Data Escrow deposits are represented in XML, which provides native 6336 support for encoding information using the Unicode character set and 6337 its more compact representations including UTF-8. Conformant XML 6338 processors recognize both UTF-8 and UTF-16. Though XML includes 6339 provisions to identify and use other character encodings through use 6340 of an "encoding" attribute in an declaration, use of UTF-8 is 6341 RECOMMENDED. 6343 11. IANA Considerations 6345 This document uses URNs to describe XML namespaces and XML schemas 6346 conforming to a registry mechanism described in [RFC3688]. Fourteen 6347 URI assignments have been registered by the IANA. 6349 Registration request for the RDE CSV namespace: 6351 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6353 Registrant Contact: See the "Author's Address" section of this 6354 document. 6356 XML: None. Namespace URIs do not represent an XML specification. 6358 Registration request for the RDE CSV XML schema: 6360 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6362 Registrant Contact: See the "Author's Address" section of this 6363 document. 6365 See the "Formal Syntax" section of this document. 6367 Registration request for the RDE domain namespace: 6369 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6371 Registrant Contact: See the "Author's Address" section of this 6372 document. 6374 XML: None. Namespace URIs do not represent an XML specification. 6376 Registration request for the RDE domain XML schema: 6378 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6380 Registrant Contact: See the "Author's Address" section of this 6381 document. 6383 See the "Formal Syntax" section of this document. 6385 Registration request for the CSV domain namespace: 6387 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6389 Registrant Contact: See the "Author's Address" section of this 6390 document. 6392 XML: None. Namespace URIs do not represent an XML specification. 6394 Registration request for the CSV domain XML schema: 6396 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6398 Registrant Contact: See the "Author's Address" section of this 6399 document. 6401 See the "Formal Syntax" section of this document. 6403 Registration request for the RDE host namespace: 6405 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6407 Registrant Contact: See the "Author's Address" section of this 6408 document. 6410 XML: None. Namespace URIs do not represent an XML specification. 6412 Registration request for the RDE host XML schema: 6414 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6416 Registrant Contact: See the "Author's Address" section of this 6417 document. 6419 See the "Formal Syntax" section of this document. 6421 Registration request for the CSV host namespace: 6423 URI: urn:ietf:params:xml:ns:csvHost-1.0 6425 Registrant Contact: See the "Author's Address" section of this 6426 document. 6428 XML: None. Namespace URIs do not represent an XML specification. 6430 Registration request for the CSV host XML schema: 6432 URI: urn:ietf:params:xml:schema:csvHost-1.0 6434 Registrant Contact: See the "Author's Address" section of this 6435 document. 6437 See the "Formal Syntax" section of this document. 6439 Registration request for the RDE contact namespace: 6441 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6443 Registrant Contact: See the "Author's Address" section of this 6444 document. 6446 XML: None. Namespace URIs do not represent an XML specification. 6448 Registration request for the RDE contact XML schema: 6450 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6451 Registrant Contact: See the "Author's Address" section of this 6452 document. 6454 See the "Formal Syntax" section of this document. 6456 Registration request for the CSV contact namespace: 6458 URI: urn:ietf:params:xml:ns:csvContact-1.0 6460 Registrant Contact: See the "Author's Address" section of this 6461 document. 6463 XML: None. Namespace URIs do not represent an XML specification. 6465 Registration request for the CSV contact XML schema: 6467 URI: urn:ietf:params:xml:schema:csvContact-1.0 6469 Registrant Contact: See the "Author's Address" section of this 6470 document. 6472 See the "Formal Syntax" section of this document. 6474 Registration request for the RDE registrar namespace: 6476 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6478 Registrant Contact: See the "Author's Address" section of this 6479 document. 6481 XML: None. Namespace URIs do not represent an XML specification. 6483 Registration request for the RDE registrar XML schema: 6485 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6487 Registrant Contact: See the "Author's Address" section of this 6488 document. 6490 See the "Formal Syntax" section of this document. 6492 Registration request for the CSV registrar namespace: 6494 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6496 Registrant Contact: See the "Author's Address" section of this 6497 document. 6499 XML: None. Namespace URIs do not represent an XML specification. 6501 Registration request for the CSV registrar XML schema: 6503 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6505 Registrant Contact: See the "Author's Address" section of this 6506 document. 6508 See the "Formal Syntax" section of this document. 6510 Registration request for the RDE IDN namespace: 6512 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6514 Registrant Contact: See the "Author's Address" section of this 6515 document. 6517 XML: None. Namespace URIs do not represent an XML specification. 6519 Registration request for the RDE IDN XML schema: 6521 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6523 Registrant Contact: See the "Author's Address" section of this 6524 document. 6526 See the "Formal Syntax" section of this document. 6528 Registration request for the CSV IDN namespace: 6530 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6532 Registrant Contact: See the "Author's Address" section of this 6533 document. 6535 XML: None. Namespace URIs do not represent an XML specification. 6537 Registration request for the CSV IDN XML schema: 6539 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6541 Registrant Contact: See the "Author's Address" section of this 6542 document. 6544 See the "Formal Syntax" section of this document. 6546 Registration request for the RDE NNDN namespace: 6548 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6550 Registrant Contact: See the "Author's Address" section of this 6551 document. 6553 XML: None. Namespace URIs do not represent an XML specification. 6555 Registration request for the RDE NNDN XML schema: 6557 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6559 Registrant Contact: See the "Author's Address" section of this 6560 document. 6562 See the "Formal Syntax" section of this document. 6564 Registration request for the CSV NNDN namespace: 6566 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6568 Registrant Contact: See the "Author's Address" section of this 6569 document. 6571 XML: None. Namespace URIs do not represent an XML specification. 6573 Registration request for the CSV NNDN XML schema: 6575 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6577 Registrant Contact: See the "Author's Address" section of this 6578 document. 6580 See the "Formal Syntax" section of this document. 6582 Registration request for the RDE EPP parameters namespace: 6584 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6586 Registrant Contact: See the "Author's Address" section of this 6587 document. 6589 XML: None. Namespace URIs do not represent an XML specification. 6591 Registration request for the RDE EPP parameters XML schema: 6593 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6594 Registrant Contact: See the "Author's Address" section of this 6595 document. 6597 See the "Formal Syntax" section of this document. 6599 12. Implementation Status 6601 Note to RFC Editor: Please remove this section and the reference to 6602 RFC 7942 [RFC7942] before publication. 6604 This section records the status of known implementations of the 6605 protocol defined by this specification at the time of posting of this 6606 Internet-Draft, and is based on a proposal described in RFC 7942 6607 [RFC7942]. The description of implementations in this section is 6608 intended to assist the IETF in its decision processes in progressing 6609 drafts to RFCs. Please note that the listing of any individual 6610 implementation here does not imply endorsement by the IETF. 6611 Furthermore, no effort has been spent to verify the information 6612 presented here that was supplied by IETF contributors. This is not 6613 intended as, and must not be construed to be, a catalog of available 6614 implementations or their features. Readers are advised to note that 6615 other implementations may exist. 6617 According to RFC 7942 [RFC7942], "this will allow reviewers and 6618 working groups to assign due consideration to documents that have the 6619 benefit of running code, which may serve as evidence of valuable 6620 experimentation and feedback that have made the implemented protocols 6621 more mature. It is up to the individual working groups to use this 6622 information as they see fit". 6624 12.1. Implementation in the gTLD space 6626 Organization: ICANN 6628 Name: ICANN Registry Agreement 6630 Description: the ICANN Base Registry Agreement requires Registries, 6631 Data Escrow Agents, and ICANN to implement this specification. ICANN 6632 receives daily notifications from Data Escrow Agents confirming that 6633 more than 1,200 gTLDs are sending deposits that comply with this 6634 specification. ICANN receives on a weekly basis per gTLD, from more 6635 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6636 also complies with this specification. In addition, ICANN is aware 6637 of Registry Service Provider transitions using data files that 6638 conform to this specification. 6640 Level of maturity: production. 6642 Coverage: all aspects of this specification are implemented. 6644 Version compatibility: versions 03 - 08 are known to be implemented. 6646 Contact: gustavo.lozano@icann.org 6648 URL: https://www.icann.org/resources/pages/registries/registries- 6649 agreements-en 6651 13. Security Considerations 6653 This specification does not define the security mechanisms to be used 6654 in the transmission of the data escrow deposits, since it only 6655 specifies the minimum necessary to enable the rebuilding of a 6656 Registry from deposits without intervention from the original 6657 Registry. 6659 Depending on local policies, some elements or most likely, the whole 6660 deposit will be considered confidential. As such the Registry 6661 transmitting the data to the Escrow Agent SHOULD take all the 6662 necessary precautions like encrypting the data itself and/or the 6663 transport channel to avoid inadvertent disclosure of private data. 6665 It is also of the utmost importance the authentication of the parties 6666 passing data escrow deposit files. The Escrow Agent SHOULD properly 6667 authenticate the identity of the Registry before accepting data 6668 escrow deposits. In a similar manner, the Registry SHOULD 6669 authenticate the identity of the Escrow Agent before submitting any 6670 data. 6672 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6673 checking mechanisms to ensure the data transmitted is what the source 6674 intended. Validation of the contents by the Escrow Agent is 6675 RECOMMENDED to ensure not only the file was transmitted correctly 6676 from the Registry, but also the contents are also "meaningful". 6678 14. Privacy Considerations 6680 This specification defines a format that may be used to escrow 6681 personal data. The process of data escrow is governed by a legal 6682 document agreed by the parties, and such legal document must regulate 6683 the particularities regarding the protection of personal data. 6685 15. Acknowledgments 6687 Parts of this document are based on EPP [RFC5730] and related RFCs by 6688 Scott Hollenbeck. 6690 Special suggestions that have been incorporated into this document 6691 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6692 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6693 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6694 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6695 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6696 Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. 6698 Shoji Noguchi and Francisco Arias participated as co-authors until 6699 version 05 providing invaluable support for this document. 6701 16. Change History 6703 [[RFC Editor: Please remove this section.]] 6705 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6706 dnrd-objects-mapping-00 6708 1. Added definition for child elements under the element. 6710 2. Added definition for child elements under the element. 6712 3. Added definition for child elements under the element. 6714 4. Rewrote the IDN Variants Handling section to use the variant 6715 states as described in ICANN's Study of Issues Related to the 6716 Management of IDN Variant TLDs. 6718 5. Renamed to in the . 6720 6. Renamed to in the element. 6722 7. Renamed to in the element. 6724 8. Added element under element. 6726 9. Fixed some typographical errors and omissions. 6728 16.2. Changes from 00 to 01 6730 1. Specify OPTIONAL elements in the draft. 6732 2. Added NNDN object to support list of reserved names and different 6733 IDN variants models. 6735 3. Removed subordinated host element from the domain object. 6737 4. Added eppParams object. 6739 5. Added variantGenerator element to the domain object. 6741 6. Added lgr to the IDN table object. 6743 16.3. Changes from 01 to 02 6745 1. Updates to the all objects based on feedback from the list. 6747 2. Start of XML and CSV drafts merge. 6749 3. Added header object. 6751 4. Added report object. 6753 5. Added notification object. 6755 6. Added Data Escrow Agent Extended Verification Process section. 6757 7. Added Notifications from Registries to Third Parties. 6759 8. Added Notifications from Data Escrow Agents to Third Parties. 6761 9. Added FULL, DIFF deposit examples using the XML model only. 6763 16.4. Changes from 02 to 03 6765 1. Remove authinfo from the XML Schema. 6767 2. Resend attribute is now an element 6769 3. Scope attribute added to policy object. 6771 16.5. Changes from 03 to 04 6773 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6774 arias-noguchi-dnrd-objects-mapping-02. 6776 2. Changed the cksum attribute of to use CRC32 and 6777 changed all of the sample cksum values to use CRC32, based on 6778 feedback from David Kipling. 6780 3. Changed the optional element to be an optional 6781 "sep" attribute value of the element with a default 6782 value of "," based on feedback from David Kipling. 6784 4. Added support for the optional "parent" attribute for the to the 6785 CSV fields to indicate a field as a reference to a parent 6786 object, based on feedback from David Kipling. 6788 5. Added support for the CSV model for the NNDN. 6790 6. Added support to delete hosts based on roid. 6792 7. Added mirrored state to NNDN 6794 8. Minor fixes to XML XSDs. 6796 9. The Report and Notification objects were moved to draft-lozano- 6797 icann-registry-interfaces 6799 10. The section Data escrow notifications was moved to draft-lozano- 6800 icann-registry-interfaces 6802 11. Removed references to the , , and 6803 from the "hostStatuses" and "hostAddresses" CSV 6804 files. 6806 12. Removed references to the , , and 6807 from the "contactStatuses" CSV file. 6809 13. Removed references to the , , and 6810 from the "domainContacts", "domainStatuses", 6811 and "domainNameServers" CSV files. 6813 14. Changed to . 6815 15. Replaced use of to new field 6816 in the "domain", "idnLanguage", and "NNDN" CSV files. 6818 16. Replaced use of with in the 6819 "host" element. 6821 17. Changed the foreign key of the hosts to use 6822 instead of and removed use of in 6823 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6824 files. 6826 18. Added use of the MUST keyword for CSV fields that are required 6827 to be supported in an EPP based system. 6829 19. Removed use of the field element for the 6830 "registrar" CSV file. 6832 20. Added definition of field element. 6834 16.6. Changes from 04 to 05 6836 1. Updated the examples of the full and differential deposits using 6837 the CSV and XML model. 6839 2. Made optional for the "domainTransfer" CSV file 6840 to match the XML definition. 6842 3. Made optional for the "domain" CSV file 6843 to match the XML definition. 6845 4. Made optional for the "domain" and "contact" CSV 6846 files to match the XML definition. 6848 5. Change from IDREF to idType. 6850 6. Minor editorial changes. 6852 16.7. Changes from 05 to 06 6854 1. Revised the differential and incremental deposits for the CSV 6855 format to use cascade update / replace and delete from the parent 6856 object to be consistent with the XML format. 6858 2. Revised the structure of the CSV format sections to utilize sub- 6859 sections instead of a list for the CSV file definitions. 6861 3. Added the "CSV Parent Child Relationship" section to describe the 6862 concept of parent child relationships across CSV file 6863 definitions. 6865 4. Added the "domainNameServersAddresses" CSV File Definition 6866 section to support the domain host attributes model of [RFC5731]. 6868 5. Made the required fields in the CSV format consistent with the 6869 XML format. The CSV fields updated to be required include: 6870 , , , 6871 , , , 6872 , , , 6873 , , , 6874 , , 6875 , , , 6876 , , 6877 , and . 6879 6. Revised the CSV examples to use a more realistic set of records. 6881 16.8. Changes from 06 to 07 6883 1. Created "repositoryTypeGroup" group element in the rdeHeader 6884 including the , and 6885 elements. 6887 2. Added the optional "rcdn" and "registrarId" attributes to the 6888 element 6890 16.9. Changes from 07 to 08 6892 1. The following registrar elements were made optional to support 6893 greater flexibility for the implementation of policies: status, 6894 postalInfo, email and crDate. 6896 2. The following domain name elements were made optional to support 6897 greater flexibility for the implementation of policies: crRr. 6899 16.10. Changes from 08 to 09 6901 1. Implementation Status section was added 6903 16.11. Changes from 09 to 10 6905 1. Editorial changes in section Section 5.1.2.1.6. 6907 2. Added MAY clause when the DS Data Interface is used in section 6908 Section 5.1.2.1.6. 6910 16.12. Changes from 10 to REGEXT 00 6912 1. Internet Draft (I-D) adopted by the REGEXT WG. 6914 16.13. Changes REGEXT 00 to REGEXT 01 6916 1. Added the element to the 6917 "repositoryTypeGroup" group element in the rdeHeader. 6919 2. Privacy consideration section was added 6921 3. Updates on section 8 6923 16.14. Changes REGEXT 01 to REGEXT 02 6925 1. Added a choice between the use of the or 6926 fields in the CSV "domain", "host", and 6927 "contact" definitions. 6929 2. Added a choice between the use of the or 6930 fields in the CSV "domainNameServers" 6931 definition. 6933 3. Changed "of client" to "of the client" throughout the document. 6935 4. Modified all references of 'The attribute isRequired MUST equal 6936 "true".' to 'The attribute "isRequired" MUST equal "true".' 6938 5. Combined the and 6939 fields in a single required list for the CSV "domainContacts" 6940 definition. 6942 6. Combined the , , and 6943 fields in a single required list for the 6944 CSV "domainStatuses" definition. 6946 7. Moved the the fields to the MAY 6947 list for the CSV "domain", "host", and "contact" definitions. 6949 8. Made the order of the , , 6950 , and fields more consistent in the 6951 CSV lists. 6953 9. Fixed an error in the order of the object example. 6955 10. Changed to be optional to match being 6956 optional in the XML model, by having it use type 6957 rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and 6958 ensuring that is included in the MAY field 6959 lists and not the MUST field lists. 6961 11. Made optional for the "domain" CSV definition 6962 to be consistent with the XML model, by removing the sentence 6963 'The attribute "isRequired" MUST equal "true".' from the 6964 description and moving the field to the MAY field list. 6966 12. Made optional for the "domain" and "contact" 6967 CSV definitions to be consistent with the XML model, by moving 6968 the field to the MAY field list. 6970 13. Made optional to be consistent with the XML 6971 model, by having it use type rdeCsv:fClIDType instead of 6972 rdeCsv:fClIDRequiredType. 6974 14. Made required to be consistent with the XML 6975 model, by having it use type rdeCsv:fClIDRequiredType instead of 6976 rdeCsv:fClIDType. 6978 15. Made the field in the "host", "contact", 6979 and "registrar" CSV definitions required explicitly by removing 6980 'and isRequired="true"' and adding the sentence 'The attribute 6981 isRequired MUST equal "true".', when it is chosen as the primary 6982 field. 6984 16. Removed extra '/>.' at the end of the field 6985 description in the "hostStatuses" CSV definition. 6987 17. Made the field optional to be consistent 6988 with the XML model, by having csvRegistrar:fStatusType extend 6989 rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. 6991 18. Made the field for the "registrar" CSV 6992 definition explicitly optional to be consistent with the XML 6993 model, by adding the sentence 'The attribute isRequired MUST 6994 equal "false".' to the field description and including the 6995 definition of isRequired="false" in the "registrar" CSV 6996 definition examples. 6998 19. Added the choice between the use of the and 6999 fields in the deletes "registrar" CSV 7000 definition to be consistent with the "registrar" CSV definition. 7002 20. Made the and elements optional for the host and 7003 contact objects in the XML model to be consistent with the 7004 domain object. 7006 16.15. Changes REGEXT 02 to REGEXT 03 7008 1. Added the optional element contentTag in the header object. 7010 2. Editorial updates. 7012 16.16. Changes REGEXT 03 to REGEXT 04 7014 1. Note: Updates from version REGEXT 03 to REGEXT 04 attend the 7015 feedback provided during the document shepherd review. 7017 2. Editorial updates. 7019 3. Examples now use domain names from the .example TLD. 7021 4. The introduction was enhanced by explaining the need for data 7022 escrow and the proposed solution. 7024 5. Explanation regarding NNDN was improved. 7026 6. Explanation regarding the CSV and XML model was improved. 7028 7. Section 4.5 updated to make the text clearer. 7030 8. draft-arias-noguchi-registry-data-escrow is now referenced from 7031 the I-D repository. 7033 9. The XML prefix "rdeDomain" is now consistently used. 7035 10. The prevID attribute was removed from the examples of full 7036 deposits. 7038 11. The examples were updated to use present dates. 7040 16.17. Changes REGEXT 04 to REGEXT 05 7042 1. draft-ietf-regext-data-escrow (version 04) is now referenced from 7043 the I-D repository. 7045 2. The example in idnLanguage CSV file definition updated to use the 7046 sep attribute. 7048 3. The reference in the example in hostAddresses CSV file definition 7049 was updated. 7051 4. Moved [RFC0791] and [RFC4291] to the Normative References 7052 section. 7054 17. Example of a full deposit using the XML model 7056 Example of a full deposit using the XML model: 7058 7059 7074 2019-10-17T00:00:00Z 7075 7076 1.0 7077 urn:ietf:params:xml:ns:rdeHeader-1.0 7078 7079 urn:ietf:params:xml:ns:rdeContact-1.0 7080 7081 urn:ietf:params:xml:ns:rdeHost-1.0 7082 7083 urn:ietf:params:xml:ns:rdeDomain-1.0 7084 7085 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7086 7087 urn:ietf:params:xml:ns:rdeIDN-1.0 7088 7089 urn:ietf:params:xml:ns:rdeNNDN-1.0 7090 7091 urn:ietf:params:xml:ns:rdeEppParams-1.0 7092 7093 7095 7096 7097 7098 7099 test 7100 2 7102 7103 1 7105 7106 1 7108 7109 1 7111 7112 1 7114 7115 1 7117 7118 1 7120 7121 7122 7123 7124 example1.example 7125 Dexample1-TEST 7126 7127 jd1234 7128 sh8013 7129 sh8013 7130 7131 ns1.example.com 7132 ns1.example1.example 7133 7134 RegistrarX 7135 RegistrarX 7136 1999-04-03T22:00:00.0Z 7137 2015-04-03T22:00:00.0Z 7138 7140 7141 7142 example2.example 7143 Dexample2-TEST 7144 7145 7146 jd1234 7147 sh8013 7148 sh8013 7149 RegistrarX 7150 RegistrarX 7151 1999-04-03T22:00:00.0Z 7152 2015-04-03T22:00:00.0Z 7153 7155 7156 7157 ns1.example1.example 7158 Hns1_example_test-TEST 7159 7160 7161 192.0.2.2 7162 192.0.2.29 7163 1080:0:0:0:8:800:200C:417A 7164 7165 RegistrarX 7166 RegistrarX 7167 1999-05-08T12:10:00.0Z 7168 RegistrarX 7169 2009-10-03T09:34:00.0Z 7171 7173 7174 7175 sh8013 7176 Csh8013-TEST 7177 7178 7179 7180 John Doe 7181 Example Inc. 7182 7183 123 Example Dr. 7184 Suite 100 7185 Dulles 7186 VA 7187 20166-6503 7188 US 7189 7190 7191 +1.7035555555 7192 7193 +1.7035555556 7194 7195 jdoe@example.example 7196 7197 RegistrarX 7198 RegistrarX 7199 7200 2009-09-13T08:01:00.0Z 7201 7202 RegistrarX 7203 7204 2009-11-26T09:10:00.0Z 7205 7206 2009-12-03T09:05:00.0Z 7207 7208 7209 7210 7211 7212 7214 7215 7216 RegistrarX 7217 Registrar X 7218 123 7219 ok 7220 7221 7222 123 Example Dr. 7223 7224 Suite 100 7225 7226 Dulles 7227 VA 7228 20166-6503 7229 US 7230 7231 7232 +1.7035555555 7233 7234 +1.7035555556 7235 7236 jdoe@example.example 7237 7238 http://www.example.example 7239 7240 7241 whois.example.example 7242 7243 http://whois.example.example 7244 7245 7246 2005-04-23T11:49:00.0Z 7247 7248 2009-02-17T17:51:00.0Z 7249 7250 7252 7253 7254 7255 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 7256 7257 7258 http://registro.br/dominio/regras.html 7259 7260 7262 7263 7264 xn--exampl-gva.example 7265 pt-BR 7266 example1.example 7267 withheld 7268 2005-04-23T11:49:00.0Z 7269 7271 7272 7273 1.0 7274 en 7275 7276 urn:ietf:params:xml:ns:domain-1.0 7277 7278 7279 urn:ietf:params:xml:ns:contact-1.0 7280 7281 7282 urn:ietf:params:xml:ns:host-1.0 7283 7284 7285 urn:ietf:params:xml:ns:rgp-1.0 7286 7287 urn:ietf:params:xml:ns:secDNS-1.1 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7310 7311 7313 18. Example of differential deposit using the XML model 7315 Example of a differential deposit using the XML model: 7317 7318 7333 2019-10-17T00:00:00Z 7334 7335 1.0 7336 urn:ietf:params:xml:ns:rdeHeader-1.0 7337 7338 urn:ietf:params:xml:ns:rdeContact-1.0 7339 7340 urn:ietf:params:xml:ns:rdeHost-1.0 7341 7342 urn:ietf:params:xml:ns:rdeDomain-1.0 7343 7344 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7345 7346 urn:ietf:params:xml:ns:rdeIDN-1.0 7347 7348 urn:ietf:params:xml:ns:rdeNNDN-1.0 7349 7350 urn:ietf:params:xml:ns:rdeEppParams-1.0 7351 7352 7354 7355 7356 7357 example2.example 7358 7359 7360 7361 7362 7363 7364 test 7365 1 7367 7368 1 7370 7371 1 7373 7374 1 7376 7377 1 7379 7380 1 7382 7383 1 7385 7386 7387 7388 7390 19. Example of a full deposit using the CSV model 7392 Example of a full deposit using the CSV model: 7394 7395 7410 2019-10-18T00:00:00Z 7411 7412 1.0 7413 urn:ietf:params:xml:ns:csvDomain-1.0 7414 urn:ietf:params:xml:ns:csvHost-1.0 7415 urn:ietf:params:xml:ns:csvContact-1.0 7416 urn:ietf:params:xml:ns:csvRegistrar-1.0 7417 urn:ietf:params:xml:ns:csvIDN-1.0 7418 urn:ietf:params:xml:ns:csvNNDN-1.0 7419 urn:ietf:params:xml:ns:rdeEppParams-1.0 7420 7421 7422 7423 test 7424 7425 4 7426 7427 7428 6 7429 7430 7431 9 7432 7433 7434 3 7435 7436 7437 2 7438 7439 7440 2 7441 7442 7443 1 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7466 domain-YYYYMMDD.csv 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7479 domainContacts-YYYYMMDD.csv 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7494 domainStatuses-YYYYMMDD.csv 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7506 domainNameServers-name-YYYYMMDD.csv 7507 7508 7509 7510 7511 7512 7513 7514 7515 7516 7518 domainNameServers-roid-YYYYMMDD.csv 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7534 dnssec-ds-YYYYMMDD.csv 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7550 dnssec-key-YYYYMMDD.csv 7551 7552 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7570 domainTransfer-YYYYMMDD.csv 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7592 host-YYYYMMDD.csv 7593 7594 7595 7596 7597 7598 7599 7600 7601 7603 7604 7605 7607 hostStatuses-YYYYMMDD.csv 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7620 hostAddresses-YYYYMMDD.csv 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7646 contact-YYYYMMDD.csv 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7660 contactStatuses-YYYYMMDD.csv 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7681 contactPostal-YYYYMMDD.csv 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7699 contactTransfer-YYYYMMDD.csv 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7720 contactDisclose-YYYYMMDD.csv 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7752 registrar-YYYYMMDD.csv 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7766 idnLanguage-YYYYMMDD.csv 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7784 NNDN-YYYYMMDD.csv 7785 7786 7787 7788 7789 7790 1.0 7791 en 7792 urn:ietf:params:xml:ns:domain-1.0 7793 7794 urn:ietf:params:xml:ns:host-1.0 7795 7796 urn:ietf:params:xml:ns:contact-1.0 7797 7798 7799 urn:ietf:params:xml:ns:secDNS-1.1 7800 7801 urn:ietf:params:xml:ns:rgp-1.0 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7828 20. Example of differential deposit using the CSV model 7830 Example of a differential deposit using the CSV model: 7832 7833 7847 2019-10-18T00:00:00Z 7848 7849 1.0 7850 urn:ietf:params:xml:ns:csvDomain-1.0 7851 urn:ietf:params:xml:ns:csvHost-1.0 7852 urn:ietf:params:xml:ns:csvContact-1.0 7853 urn:ietf:params:xml:ns:csvRegistrar-1.0 7854 urn:ietf:params:xml:ns:csvIDN-1.0 7855 7856 7857 7858 7859 7860 7861 7862 7863 7865 domain-delete-YYYYMMDD.csv 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7878 host-delete-YYYYMMDD.csv 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7891 contact-delete-YYYYMMDD.csv 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7904 registrar-delete-YYYYMMDD.csv 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7917 idnLanguage-delete-YYYYMMDD.csv 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7930 NNDN-delete-YYYYMMDD.csv 7931 7932 7933 7934 7935 7936 7937 7938 test 7939 7940 2 7941 7942 7943 2 7944 7945 7946 3 7947 7948 7949 1 7950 7951 7952 1 7953 7954 7955 1 7956 7957 7958 1 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7981 domain-YYYYMMDD.csv 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7994 domainContacts-YYYYMMDD.csv 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8009 domainStatuses-YYYYMMDD.csv 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8021 domainNameServers-name-YYYYMMDD.csv 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8033 domainNameServers-roid-YYYYMMDD.csv 8034 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8050 dnssec-ds-YYYYMMDD.csv 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8066 dnssec-key-YYYYMMDD.csv 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8085 domainTransfer-YYYYMMDD.csv 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8107 host-YYYYMMDD.csv 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8121 hostStatuses-YYYYMMDD.csv 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8134 hostAddresses-YYYYMMDD.csv 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8160 contact-YYYYMMDD.csv 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8174 contactStatuses-YYYYMMDD.csv 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8195 contactPostal-YYYYMMDD.csv 8196 8197 8198 8199 8200 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8213 contactTransfer-YYYYMMDD.csv 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8234 contactDisclose-YYYYMMDD.csv 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264 8266 registrar-YYYYMMDD.csv 8267 8268 8269 8270 8271 8272 8273 8274 8275 8277 8278 8279 8281 idnLanguage-YYYYMMDD.csv 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8299 NNDN-YYYYMMDD.csv 8300 8301 8302 8303 8304 8305 1.0 8306 en 8307 urn:ietf:params:xml:ns:domain-1.0 8308 8309 urn:ietf:params:xml:ns:host-1.0 8310 8311 urn:ietf:params:xml:ns:contact-1.0 8312 8313 8314 urn:ietf:params:xml:ns:secDNS-1.1 8315 8316 urn:ietf:params:xml:ns:rgp-1.0 8317 8318 8319 8320 8321 8322 8323 8324 8325 8326 8327 8328 8329 8330 8331 8332 8333 8334 8335 8336 8337 8338 8339 8340 8341 8343 21. References 8345 21.1. Normative References 8347 [I-D.ietf-regext-data-escrow] 8348 Lozano, G., "Registry Data Escrow Specification", draft- 8349 ietf-regext-data-escrow-04 (work in progress), January 8350 2020. 8352 [ISO-3166-1] 8353 3166, I. S., "Codes for the representation of names of 8354 countries and their subdivisions -- Part 1: Country 8355 codes", ISO Standard 3166, November 2006. 8357 [ITU-E164] 8358 International Telecommunication Union, "The international 8359 public telecommunication numbering plan", ITU-T 8360 Recommendation E.164, February 2005. 8362 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8363 DOI 10.17487/RFC0791, September 1981, 8364 . 8366 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8367 Requirement Levels", BCP 14, RFC 2119, 8368 DOI 10.17487/RFC2119, March 1997, 8369 . 8371 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8372 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8373 . 8375 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8376 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8377 DOI 10.17487/RFC3915, September 2004, 8378 . 8380 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8381 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8382 2006, . 8384 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8385 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8386 . 8388 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8389 Domain Name Mapping", STD 69, RFC 5731, 8390 DOI 10.17487/RFC5731, August 2009, 8391 . 8393 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8394 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8395 August 2009, . 8397 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8398 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8399 August 2009, . 8401 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8402 Security Extensions Mapping for the Extensible 8403 Provisioning Protocol (EPP)", RFC 5910, 8404 DOI 10.17487/RFC5910, May 2010, 8405 . 8407 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 8408 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 8409 May 2017, . 8411 21.2. Informative References 8413 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8414 DOI 10.17487/RFC3688, January 2004, 8415 . 8417 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8418 DOI 10.17487/RFC3912, September 2004, 8419 . 8421 [RFC5891] Klensin, J., "Internationalized Domain Names in 8422 Applications (IDNA): Protocol", RFC 5891, 8423 DOI 10.17487/RFC5891, August 2010, 8424 . 8426 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8427 Code: The Implementation Status Section", BCP 205, 8428 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8429 . 8431 [variantTLDsReport] 8432 Internet Corporation for Assigned Names and Numbers 8433 (ICANN), "A Study of Issues Related to the Management of 8434 IDN Variant TLDs", February 2012, 8435 . 8438 Authors' Addresses 8440 Gustavo Lozano 8441 Internet Corporation for Assigned Names and Numbers 8442 12025 Waterfront Drive, Suite 300 8443 Los Angeles 90292 8444 United States of America 8446 Phone: +1.310.823.9358 8447 Email: gustavo.lozano@icann.org 8449 James Gould 8450 VeriSign, Inc. 8451 12061 Bluemont Way 8452 Reston 20190 8453 United States of America 8455 Email: jgould@verisign.com 8456 Chethan Thippeswamy 8457 VeriSign, Inc. 8458 12061 Bluemont Way 8459 Reston 20190 8460 United States of America 8462 Email: cthippeswamy@verisign.com