idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-04.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 (Dec 16, 2019) is 1593 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-02 -- 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: June 18, 2020 C. Thippeswamy 6 VeriSign 7 Dec 16, 2019 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-04 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 June 18, 2020. 35 Copyright Notice 37 Copyright (c) 2019 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 17. Example of a full deposit using the XML model . . . . . . . . 155 121 18. Example of differential deposit using the XML model . . . . . 160 122 19. Example of a full deposit using the CSV model . . . . . . . . 162 123 20. Example of differential deposit using the CSV model . . . . . 171 124 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 182 125 21.1. Normative References . . . . . . . . . . . . . . . . . . 182 126 21.2. Informative References . . . . . . . . . . . . . . . . . 183 127 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 184 129 1. Introduction 131 Registry Data Escrow is the process by which a registry periodically 132 submits data deposits to a third-party called an escrow agent. These 133 deposits comprise the minimum data needed by a third-party to resume 134 operations if the registry cannot function and is unable or unwilling 135 to facilitate an orderly transfer of service. For example, for a 136 domain name registry or registrar, the data to be deposited would 137 include all the objects related to registered domain names, e.g., 138 names, contacts, name servers, etc. 140 The goal of data escrow is higher resiliency of registration 141 services, for the benefit of Internet users. The beneficiaries of a 142 registry are not just those registering information there, but all 143 relying parties that need to identify the owners of objects. 145 In the context of domain name registries, registration data escrow is 146 a requirement for generic top-level domains and some country code 147 top-level domain managers are also currently escrowing data. There 148 is also a similar requirement for ICANN-accredited domain registrars. 150 This document defines the standard set of objects for a Domain Name 151 Registry that uses the Registry Data Escrow Specification described 152 in [I-D.ietf-regext-data-escrow] for escrow. The set of objects 153 include: 155 o Domain: Internet domain names that are typically provisioned in a 156 Domain Name Registry using the EPP domain name mapping [RFC5731]. 157 The attributes defined in the EPP domain name mapping [RFC5731] 158 are fully supported by this document. 160 o Host: Internet host names that are typically provisioned in a 161 Domain Name Registry using the EPP host mapping [RFC5732]. The 162 attributes defined in the EPP host mapping [RFC5732] are fully 163 supported by this document. 165 o Contact: Individual or organization social information provisioned 166 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 167 The attributes defined in the EPP contact mapping [RFC5733] are 168 fully supported by this document. 170 o Registrar: The organization that sponsors objects like domains, 171 hosts, and contacts in a Domain Name Registry. 173 o NNDN (NNDN's not domain name): Domain Name Registries may maintain 174 domain names without them being persisted as domain objects in the 175 registry system, for example, a list of reserved names not 176 available for registration. The NNDN is a lightweight domain-like 177 object that is used to escrow domain names not maintained as 178 domain name objects. 180 This document defines the following pseudo-objects: 182 o IDN Table Reference: Internationalized Domain Names (IDN) included 183 in the Domain Object Data Escrow include references to the IDN 184 Table and Policy used in IDN registration. 186 o EPP parameters: Definition of the specific EPP parameters 187 supported by the Registry Operator. 189 o Header: Used to specify counters of objects in the database at a 190 certain point in time (watermark). 192 o Policy: Used to specify OPTIONAL elements from this specification 193 that are REQUIRED based on the business model of the registry. 195 2. Models 197 This document defines two different models that can be used to 198 deposit data escrow objects: XML and CSV. 200 The data escrow deposit MAY contain a mix of both models but an 201 object MUST be escrowed only in one model. 203 This document does not suggest the use of a particular model, and 204 both are equivalent. A Domain Name Registry may choose the model 205 that is more appropriate for the peculiarities of its systems. For 206 example, a registry may use the CSV-export functionality of the RDBMS 207 for escrow; therefore, the CSV model may be more appropriate. 208 Another registry may use the code developed for EPP to implement 209 escrow. 211 2.1. XML Model 213 XML: The XML model includes all the deposit information (meta-data 214 and data) in an XML document. The definition of the XML format is 215 fully defined in the XML schemas. As a convention, the objects 216 represented using the XML model are referenced using RDE and an XML 217 namespace that is prefixed with "rde". For example, the Domain Name 218 object represented using the XML model can be referred to as the RDE 219 Domain Name with the XML namespace including rdeDomain 220 (urn:ietf:params:xml:ns:rdeDomain-1.0). 222 2.2. CSV Model 224 CSV: The CSV model uses XML to define the data escrow format of the 225 data contained in referenced Comma-Separated Values (CSV) files. As 226 a convention, the objects represented using the CSV model is 227 referenced using CSV and an XML namespace that is prefixed with 228 "csv". For example, the Domain Name object represented using the CSV 229 model can be referred to as the CSV Domain Name with the XML 230 namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). 232 3. Terminology 234 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 235 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 236 "OPTIONAL" in this document are to be interpreted as described in BCP 237 14 [RFC2119] [RFC8174] when, and only when, they appear in all 238 capitals, as shown here. 240 REGISTRY. In the context of this draft the definition will be 241 overloaded (from the definition in the base protocol) to indicate an 242 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 243 NAME. 245 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 246 or any other domain name at any level in the DNS tree for which a 247 Registry (either directly or through and affiliate company) provides 248 Registry Services for other organizations or individuals. For 249 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 251 REGISTRY SERVICES. Services offered by the Registry critical to the 252 following tasks: the provisioning of domain names on receipt of 253 requests and data from registrars; responding to registrar queries 254 for status information relating to the DNS servers for the RCDN; 255 dissemination of RCDN zone files; operation of the Registry DNS 256 servers; and responding to queries for contact and other information 257 concerning DNS registrations in the RCDN. Any other products or 258 services that only a Registry is capable of providing, by reason of 259 its designation as the Registry. Typical examples of Registry 260 Services are: DNS resolution for the RCDN, WHOIS and EPP. 262 ALLOCATED. A status of some label with respect to a zone, whereby 263 the label is associated administratively to some entity that has 264 requested the label. This term (and its cognates "allocation" and 265 "to allocate") may represents the first step on the way to delegation 266 in the DNS. 268 4. General Conventions 270 4.1. Date and Time 272 Numerous fields indicate "dates", such as the creation and expiry 273 dates for domain names. These fields SHALL contain timestamps 274 indicating the date and time in UTC as specified in [RFC3339], with 275 no offset from the zero meridian. 277 4.2. Country names 279 Country identifiers SHALL be represented using two character 280 identifiers as specified in [ISO-3166-1]. 282 4.3. Telephone numbers 284 Telephone numbers (both voice and facsimile) SHALL be formatted based 285 on structures defined in [ITU-E164]. Telephone numbers described in 286 this specification are character strings that MUST begin with a plus 287 sign ("+", ASCII value 0x002B), followed by a country code defined in 288 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 289 a sequence of digits representing the telephone number. 291 4.4. Checksum 293 Checksum of the CSV data escrow files MUST use CRC32, that is the 294 algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of 295 ITU-T recommendation V.42. 297 4.5. IP addresses 299 IP addresses syntax MUST conform to the text representation of either 300 Internet Protocol Version 4 [RFC0791] or Internet Protocol Version 6 301 [RFC4291]. 303 4.6. Conventions applicable to the CSV Model 305 4.6.1. CSV Parent Child Relationship 307 The CSV model represents a relational model, where the CSV files 308 represent relational tables, the fields of the CSV files represent 309 columns of the tables, and each line of the CSV file represents a 310 record. As in a relational model, the CSV files can have 311 relationships utilizing primary keys in the parent CSV file 312 definitions and foreign keys in the child CSV file definitions for a 313 1-to-many relationship. The primary keys are not explicitly defined, 314 but the foreign keys are using the boolean "parent" field attribute 315 in the child CSV file. The relationships between the CSV files are 316 used to support a cascade replace or cascade delete of records 317 starting from the parent record in differential and incremental 318 deposits. 320 The following is an example of the CSV file definitions for a Sample 321 object consisting of a parent "sample" CSV File Definition and a 322 child "sampleStatuses" CSV File Definition. The primary key for the 323 Sample object is the field that is used as the 324 foreign key in the "sampleStatuses" CSV File Definition by specifying 325 the "parent=true" attribute. If a Sample record is updated or 326 deleted in a differential or incremental deposit, it should cascade 327 replace the data using the records included in the child 328 "sampleStatuses" CSV File Definition or cascade delete the existing 329 records in the child "sampleStatuses" CSV File Definition, 330 respectively. 332 333 ... 334 335 336 337 338 339 340 341 342 343 344 345 346 347 349 sample-YYYYMMDD.csv 350 351 352 353 354 355 356 357 358 359 360 361 363 sampleStatuses-YYYYMMDD.csv 364 365 366 367 ... 368 370 4.6.2. CSV elements 372 4.6.2.1. element 374 To support the CSV model, an element is defined for each object that 375 substitutes for the element and for the 376 element, that contains one or more elements. For 377 example, the Domain Name Object (Section 5.1) defines the 378 element, that substitutes for the 379 element, and the element, that substitutes for 380 the element. Both the element and 381 the elements contain one or more 382 elements. The element has the following child elements: 384 Ordered list of CSV fields used in the CSV files. 385 There is one or more child elements that substitute for the 386 abstract element. Each element defines the format 387 of the CSV field contained in the CSV files. The 388 elements support the "type" attribute that defines the XML simple 389 data type of the field element. The elements 390 support the "isRequired" attribute, with a default value of 391 "false", when set to "true" indicates that the field must be non- 392 empty in the CSV files and when set to "false" indicates that the 393 field MAY be empty in the CSV files. The "isRequired" attribute 394 MAY be specifically set for the field elements within the XML 395 schema and MAY be overridden when specifying the fields under the 396 element. The element supports an 397 OPTIONAL "parent" attribute that identifies the field as a 398 reference to a parent object, as defined in CSV Parent Child 399 Relationship (Section 4.6.1). For example, the field SHOULD set the 401 "parent" attribute to "true" to identify it as the parent domain 402 name of the domain status. 404 A list of one or more CSV files using the 405 child element. The child element 406 defines a reference to the CSV file name and has the following 407 optional attributes: 409 compression If the CSV file is compressed, the "compression" 410 attribute defines the compression format like "gzip" or "zip". 412 encoding Defines the encoding of the CSV file with the default 413 encoding of "UTF-8". 415 cksum Defines the checksum of the CSV file using CRC32, as 416 defined in Section 4.4. This attribute is used to validate 417 that the full CSV file exists and has not been tampered with. 419 The elements requires a "name" attribute that defines 420 the purpose of the CSV file with values like "domain", "host", 421 "contact". The supported "name" attribute values are defined for 422 each object type. The OPTIONAL "sep" attribute defines the CSV 423 separator character with the default separator character of ",". 425 The following is an example of the 426 element for domain name records where the is set 427 as required with isRequired="true". 429 430 ... 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 450 domain-YYYYMMDD.csv 451 452 453 454 ... 455 457 The following is example of the "domain-YYYYMMDD.csv" file with one 458 record matching the definition. 460 domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 461 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 462 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 463 The following is an example of the 464 element for domain name records. 466 467 ... 468 469 470 471 472 473 475 domain-delete-YYYYMMDD.csv 476 477 478 479 ... 480 482 The following is example of the "domain-delete-YYYYMMDD.csv" file 483 with three records that matches the single field. 485 domain1.example 486 domain2.example 487 domainN.example 489 4.6.2.2. CSV common field elements 491 The element defined in the element 492 (Section 4.6.2.1) section has child elements that substitute for the 493 abstract element. By convention 494 elements include an 'f' prefix to identify them as field definition 495 elements. There are a set of common field elements that are used 496 across multiple data escrow objects. The common field elements are 497 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 498 using the "rdeCsv" sample namespace prefix. The CSV common field 499 elements include: 501 UTF-8 encoded name field with 502 type="eppcom:labelType". 504 Repository Object IDentifier (ROID) field with 505 type="eppcom:roidType" and isRequired="true". 507 Registrant contact identifier with 508 type="eppcom:clIDType". 510 The object status description, which is 511 free form text describing the rationale for the status, with 512 type="normalizedString". 514 Identifier of the client (registrar) that sponsors 515 the object with type="eppcom:clIDType" and isRequired="true". 517 Identifier of the registrar, defined in Section 5.4, 518 of the client that created the object with type="eppcom:clIDType". 520 Identifier of the client that created the object with 521 type="eppcom:clIDType". 523 Identifier of the registrar, defined in Section 5.4, 524 of the client that updated the object with type="eppcom:clIDType". 526 Identifier of the client that updated the object with 527 type="eppcom:clIDType". 529 Identifier of the registrar, defined in Section 5.4, 530 of the client that requested the transfer with 531 type="eppcom:clIDType" and isRequired="true". 533 Identifier of the client that requested the transfer 534 with type="eppcom:clIDType". 536 Identifier of the registrar, defined in Section 5.4, 537 of the client that should take or took action with 538 type="eppcom:clIDType" and isRequired="true". 540 Identifier of the client that should take or took 541 action for transfer with type="eppcom:clIDType". 543 Created date of object with type="dateTime". 545 Updated date of object with type="dateTime". 547 Expiration date of object with type="dateTime". 549 Date that transfer was requested with 550 type="dateTime" and isRequired="true". 552 Date that transfer action should be taken or has 553 been taken with type="dateTime" and isRequired="true". 555 Date of last transfer with type="dateTime". 557 State of the most recent transfer request with 558 type="eppcom:trStatusType" and isRequired="true". 560 General token field with type="token". 562 General language field with type="language". 564 IDN Table Identifier used for IDN domain names 565 with type="token". 567 General positive integer field with 568 type="positiveInteger". 570 Contains the URL of an object like a registrar object 571 with type="anyURI". 573 Custom field with name attribute that defines the 574 custom field name" with type="token". 576 4.6.3. Internationalized and Localized Elements 578 Some elements MAY be provided in either internationalized form 579 ("int") or provided in localized form ("loc"). Those elements use a 580 field value or "isLoc" attribute to specify the form used. If an 581 "isLoc" attribute is used, a value of "true" indicates the use of the 582 localized form and a value of "false" indicates the use of the 583 internationalized form. This MAY override the form specified for a 584 parent element. A value of "int" is used to indicate the 585 internationalized form and a value of "loc" is used to indicate the 586 localized form. When the internalized form ("int") is provided, the 587 field value MUST be represented in a subset of UTF-8 that can be 588 represented in the 7-bit US-ASCII character set. When the localized 589 form ("loc") is provided, the field value MAY be represented in 590 unrestricted UTF-8. 592 The field elements below of the "registrar" 593 element specify the internationalized form with the 594 isLoc="false" attribute. 596 ... 597 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 630 registrar-YYYYMMDD.csv 631 632 633 634 ... 635 636 ... 638 The following is an example of using the 639 field value to define the internationalized or localized form of the 640 remainder of the "contactPostal" field values. 642 ... 643 644 ... 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 662 contactPostal-YYYYMMDD.csv 663 664 665 666 ... 667 668 ... 670 5. Object Description 672 This section describes the base objects supported by this 673 specification: 675 5.1. Domain Name Object 677 The domain name object is based on the EPP domain name mapping 678 specified in [RFC5731]. The domain name object supports both the XML 679 Model and the CSV Model, defined in the Models (Section 2) section. 680 The elements used for both models are defined in the following 681 sections. 683 5.1.1. XML Model 685 There are two elements used in the data escrow of the domain name 686 objects for the XML model including the , under the 687 element, and the element, under the 688 element. 690 5.1.1.1. object 692 The domain element is based on the EPP domain response for an 693 authorized client (see Section 3.1.2. of [RFC5731]) with additional 694 data from an EPP Query Response, see Section 3.1.3. of 695 [RFC5731], RGP status from [RFC3915], and data from the EPP 696 command, see Section 5.2.1. of [RFC5910]. 698 A element substitutes for the abstract 699 element to define a concrete definition of a domain. The 700 element can be replaced by other domain definitions 701 using the XML schema substitution groups feature. 703 The element contains the following child elements: 705 o A element that contains the fully qualified name of the 706 domain name object. If the domain name is an IDN, the ASCII 707 Compatible Encoding (ACE) MUST be used. 709 o A element that contains the repository object identifier 710 assigned to the domain name object when it was created. 712 o An OPTIONAL element that contains the fully qualified name 713 of the domain name in Unicode character set. It MUST be provided 714 if available. 716 o An OPTIONAL element that references the IDN 717 Table used for the IDN. This corresponds to the "id" attribute of 718 the element. This element MUST be present if the 719 domain name is an IDN. 721 o An OPTIONAL element is used to indicate that the 722 domain name is an IDN variant. This element contains the domain 723 name used to generate the IDN variant. 725 o One or more elements that contain the current status 726 descriptors associated with the domain name. 728 o Zero or more OPTIONAL element to represent 729 "pendingDelete" sub-statuses, including "redemptionPeriod", 730 "pendingRestore", and "pendingDelete", that a domain name can be 731 in as a result of grace period processing as specified in 732 [RFC3915]. 734 o An OPTIONAL element that contain the identifier for 735 the human or organizational social information object associated 736 as the holder of the domain name object. 738 o Zero or more OPTIONAL elements that contain identifiers 739 for the human or organizational social information objects 740 associated with the domain name object. 742 o An OPTIONAL element that contains the fully qualified names 743 of the delegated host objects or host attributes (name servers) 744 associated with the domain name object. See Section 1.1 of 745 [RFC5731] for a description of the elements used to specify host 746 objects or host attributes. 748 o A element that contains the identifier of the sponsoring 749 registrar. 751 o An OPTIONAL element that contains the identifier of the 752 registrar that created the domain name object. An OPTIONAL client 753 attribute is used to specify the client that performed the 754 operation. 756 o An OPTIONAL element that contains the date and time of 757 the domain name object creation. This element MUST be present if 758 the domain name has been allocated. 760 o An OPTIONAL element that contains the date and time 761 identifying the end (expiration) of the domain name object's 762 registration period. This element MUST be present if the domain 763 name has been allocated. 765 o An OPTIONAL element that contains the identifier of the 766 registrar that last updated the domain name object. This element 767 MUST NOT be present if the domain has never been modified. An 768 OPTIONAL client attribute is used to specify the client that 769 performed the operation. 771 o An OPTIONAL element that contains the date and time of 772 the most recent domain-name-object modification. This element 773 MUST NOT be present if the domain name object has never been 774 modified. 776 o An OPTIONAL element that contains the public key 777 information associated with Domain Name System security (DNSSEC) 778 extensions for the domain name as specified in [RFC5910]. 780 o An OPTIONAL element that contains the date and time of 781 the most recent domain object successful transfer. This element 782 MUST NOT be present if the domain name object has never been 783 transferred. 785 o An OPTIONAL element that contains the following child 786 elements related to the last transfer request of the domain name 787 object. This element MUST NOT be present if a transfer request 788 for the domain name has never been created. 790 * A element that contains the state of the most recent 791 transfer request. 793 * A element that contains the identifier of the registrar 794 that requested the domain name object transfer. An OPTIONAL 795 client attribute is used to specify the client that performed 796 the operation. 798 * A element that contains the date and time that the 799 transfer was requested. 801 * An element that contains the identifier of the registrar 802 that SHOULD act upon a PENDING transfer request. For all other 803 status types, the value identifies the registrar that took the 804 indicated action. An OPTIONAL client attribute is used to 805 specify the client that performed the operation. 807 * An element that contains the date and time of a 808 required or completed response. For a PENDING request, the 809 value identifies the date and time by which a response is 810 required before an automated response action will be taken by 811 the registry. For all other status types, the value identifies 812 the date and time when the request was completed. 814 * An OPTIONAL element that contains the end of the 815 domain name object's validity period (expiry date) if the 816 transfer caused or causes a change in the validity period. 818 Example of a domain object: 820 ... 821 822 example1.example 823 Dexample1-TEST 824 825 jd1234 826 sh8013 827 sh8013 828 829 ns1.example.com 830 ns1.example1.example 831 832 RegistrarX 833 RegistrarX 834 1999-04-03T22:00:00.0Z 835 2015-04-03T22:00:00.0Z 836 837 ... 839 5.1.1.2. object 841 The element contains the fully qualified domain 842 name that was deleted and purged. 844 Example of object: 846 ... 847 848 ... 849 850 foo.example 851 bar.example 852 853 ... 854 855 ... 857 5.1.2. CSV Model 859 For the CSV Model of the domain name object, the 860 child element of the element is used to hold the new 861 or updated domain name objects for the deposit. The 862 child element of the element is 863 used to hold the deleted or purged domain name objects for the 864 deposit. Both the and 865 elements contain one or more elements with a set of 866 named CSV file definitions using the "name" attribute. 868 Differential and incremental deposits are based on changes to the 869 domain name objects. The updated domain name object data under the 870 element is a cascade replace down all of the 871 domain name CSV files starting with the parent "domain" CSV File 872 Definition (Section 5.1.2.1.1). The child CSV file definitions 873 include a field. All the child CSV 874 file definition data for the domain name objects in the parent 875 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 876 deleted and then set using the data in the child CSV files. The 877 deleted domain name object data under the element 878 is a cascade delete starting from the "domain" Deletes CSV File 879 Definition (Section 5.1.2.2.1). 881 5.1.2.1. 883 The is used to hold the new or updated domain 884 name object information for the deposit. The is 885 split into separate CSV file definitions using named 886 elements with the "name" attribute. The following sections include 887 the supported domain name CSV file definitions: 889 5.1.2.1.1. "domain" CSV File Definition 891 The "domain" CSV File Definition defines the fields and CSV file 892 references used for the parent domain name object records. All the 893 other domain name CSV file definitions are child CSV files based on 894 the inclusion of the field. 896 The following "csvDomain" field elements MUST be used in the "domain" 897 element: 899 Domain name field with type="eppcom:labelType" and 900 isRequired="true". 902 The following "csvDomain" field elements MAY be used in the "domain" 903 element: 905 Fully qualified name of the original IDN 906 domain name object related to the variant domain name object with 907 type="eppcom:labelType". 909 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 910 "domain" element: 912 Registry Object IDentifier (ROID) for the domain name 913 object with isRequired="true". 915 or A choice of: 917 Identifier of the sponsoring client with 918 isRequired="true". 920 Contains the ID assigned by ICANN with 921 type="positiveInteger". The attribute "isRequired" MUST equal 922 "true". 924 The following "rdeCsv" fields, defined in section CSV common field 925 elements (Section 4.6.2.2), MAY be used in the "domain" 926 element: 928 Identifier of the registrar, defined in Section 5.4, 929 of the client that created the object. 931 Identifier of the client that created the domain name 932 object. 934 Identifier of the registrar, defined in Section 5.4, 935 of the client that updated the object. 937 Identifier of the client that last updated the domain 938 name object. 940 UTF8 encoded domain name for the 941 field element. 943 IDN Table Identifier used for the IDN domain 944 name object that MUST match a field element 945 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 947 Registrant contact identifier for the domain 948 name object. 950 Created date and time of the domain name object. 952 Date and time of the last update to the domain name 953 object. 955 Expiration date and time for the domain name 956 object. 958 Date and time of the last transfer for the domain 959 name object. 961 Example of a "domain" element. 963 ... 964 965 ... 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 985 domain-YYYYMMDD.csv 986 987 988 989 ... 990 991 ... 993 Example of the corresponding domain-YYYYMMDD.csv file. The file 994 contains four records (two active ASCII domains, original IDN with 995 LANG-1 language rules, and variant IDN with LANG-1 language rules). 997 domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 998 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 999 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1000 domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 1001 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 1002 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1003 xn--abc123.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 1004 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 1005 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1006 xn--abc321.example,Dxnabc321-TEST,LANG-1,xn--abc123.example, 1007 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 1008 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 1010 5.1.2.1.2. "domainContacts" CSV File Definition 1012 The "domainContacts" CSV File Definition defines the fields and CSV 1013 file references used for the domain name object link records to 1014 contact objects, as described in Contact Object (Section 5.3). 1016 The following "csvDomain" field elements, defined for the "domain" 1017 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 1018 "domainContacts" element: 1020 The name of the domain object that is linked to 1021 the contact object with isRequired="true". 1023 The contact type for the contact object 1024 link with type="domain:contactAttrType" and isRequired="true". 1025 The supported contact type values include "admin" for the 1026 administration contact, "billing" for the billing contact, and 1027 "tech" for the technical contact. 1029 The following "csvContact" fields, defined for the "contact" CSV File 1030 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 1031 element: 1033 The server-unique contact identifier with 1034 isRequired="true". 1036 Example of a "domainContacts" 1037 element. 1039 ... 1040 1041 ... 1042 1043 1044 1045 1046 1047 1048 1049 1051 domainContacts-YYYYMMDD.csv 1052 1053 1054 1055 ... 1056 1057 ... 1059 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1060 file contains an admin, tech, and billing contact for the four domain 1061 names domain1.example, domain2.example, xn--abc123.example and xn-- 1062 abc321.example. 1064 domain1.example,domain1admin,admin 1065 domain1.example,domain1tech,tech 1066 domain1.example,domain1billing,billing 1067 domain2.example,domain2admin,admin 1068 domain2.example,domain2tech,tech 1069 domain2.example,domain2billing,billing 1070 xn--abc123.example,xnabc123admin,admin 1071 xn--abc123.example,xnabc123tech,tech 1072 xn--abc123.example,xnabc123billing,billing 1073 xn--abc321.example,xnabc123admin,admin 1074 xn--abc321.example,xnabc123tech,tech 1075 xn--abc321.example,xnabc123billing,billing 1077 5.1.2.1.3. "domainStatuses" CSV File Definition 1079 The "domainStatuses" CSV File Definition defines the fields and CSV 1080 file references used for the domain name object statuses. 1082 The following "csvDomain" fields, defined for the "domain" CSV File 1083 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1084 element: 1086 Domain name of status with isRequired="true". 1088 The status of the domain name with 1089 type="domain:statusValueType" and isRequired="true". 1091 The Registry Grace Period (RGP) status, as a 1092 sub-status of the "pendingDelete" status 1093 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1095 The following "rdeCsv" fields, defined in section CSV common field 1096 elements (Section 4.6.2.2), MAY be used in the "domainStatuses" 1097 element: 1099 Domain object status description which 1100 is free form text describing the rationale for the status. 1102 Language of the field. 1104 Example of a "domainStatuses" 1105 element. 1107 ... 1108 1109 ... 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1121 domainStatuses-YYYYMMDD.csv 1122 1123 1124 1125 ... 1126 1127 ... 1129 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1130 file contains the statuses for the four domain names domain1.example, 1131 domain2.example, xn--abc123.example and xn--abc321.example. 1133 domain1.example,clientUpdateProhibited,"Disallow update", 1134 en, 1135 domain1.example,clientDeleteProhibited,"Disallow delete", 1136 en, 1137 domain2.example,ok,,, 1138 xn--abc123.example,ok,,, 1139 xn--abc321.example,ok,,, 1141 5.1.2.1.4. "domainNameServers" CSV File Definition 1143 The "domainNameServers" CSV File Definition defines the fields and 1144 CSV file references used for the domain name delegated hosts (name 1145 servers). The "domainNameServers" CSV files define the relationship 1146 between a domain name object and a delegated host. The 1147 "domainNameServers" CSV File is used to support the 1148 model, defined in [RFC5731]. 1150 The following "csvDomain" fields, defined for the "domain" CSV File 1151 Definition (Section 5.1.2.1.1), MUST be used in the 1152 "domainNameServers" element: 1154 Domain name using the delegated host with 1155 isRequired="true". 1157 The following "csvHost" and "rdeCsv" field elements MUST be used in 1158 the "domainNameServers" element: 1160 or A choice of: 1162 Host name field with type="eppcom:labelType" and 1163 isRequired="true". 1165 Host object Registry Object IDentifier (ROID) 1166 assigned to the host object with isRequired="true". 1168 Example of a "domainNameServers" 1169 element. 1171 ... 1172 1173 ... 1174 1175 1176 1177 1178 1179 1180 1182 domainNameServers-YYYYMMDD.csv 1183 1184 1185 1186 ... 1187 1188 ... 1190 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1191 The file contains the delegated hosts (name servers) for the four 1192 domain names domain1.example, domain2.example, xn--abc123.example and 1193 xn--abc321.example referenced via the field element. 1195 domain1.example,Hns1_domain1_test-TEST 1196 domain1.example,Hns2_domain1_test-TEST 1197 domain2.example,Hns1_domain2_test-TEST 1198 domain2.example,Hns2_domain2_test-TEST 1199 xn--abc123.example,Hns1_example_test-TEST 1200 xn--abc123.example,Hns2_example_test-TEST 1201 xn--abc321.example,Hns1_example_test-TEST 1202 xn--abc321.example,Hns2_example_test-TEST 1204 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1206 The "domainNameServersAddresses" CSV File Definition defines the 1207 fields and CSV file references used for supporting the host as domain 1208 attributes model. 1210 The following "csvDomain" fields, defined for the "domain" CSV File 1211 Definition (Section 5.1.2.1.1), MUST be used in the 1212 "domainNameServersAddresses" element: 1214 Domain name using the delegated host with host 1215 and isRequired="true". 1217 The following "rdeCsv" fields, defined in section Host CSV model 1218 elements (Section 5.2.2), MUST be used in the 1219 "domainNameServersAddresses" element: 1221 Host name field with type="eppcom:labelType" and 1222 isRequired="true". 1224 The following "csvHost" fields, defined in section Host CSV model 1225 elements (Section 5.2.2), MAY be used in the 1226 "domainNameServersAddresses" element: 1228 IP addresses associated with the host object with 1229 type="host:addrStringType". 1231 IP addresses version associated with the host 1232 object with type="host:ipType". "host:ipType" has the enumerated 1233 values of "v4" or "v6". 1235 Example of a "domainNameServersAddresses" 1236 element. 1238 ... 1239 1240 ... 1241 1242 1243 1244 1245 1246 1247 1248 1249 1251 domainNameServersAddresses-YYYYMMDD.csv 1252 1253 1254 1255 ... 1256 1257 ... 1259 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1260 file. The file contains the delegated hosts (name servers) for the 1261 four domain names domain1.example, domain2.example, xn-- 1262 abc123.example and xn--abc321.example. 1264 domain1.example,ns1.domain1.example,192.0.2.1,v4 1265 domain1.example,ns2.domain1.example,2001:DB8::1,v6 1266 domain2.example,ns1.example.net,, 1267 domain2.example,ns2.example.net,, 1268 xn--abc123.example,ns1.example.net,, 1269 xn--abc123.example,ns2.example.net,, 1270 xn--abc321.example,ns1.example.net,, 1271 xn--abc321.example,ns2.example.net,, 1273 5.1.2.1.6. "dnssec" CSV File Definition 1275 The "dnssec" CSV File Definition defines the fields and CSV file 1276 references used for the domain name object DNSSEC records (DS or Key 1277 Data). 1279 The following "csvDomain" field elements MUST be used in the "dnssec" 1280 element when the DS Data Interface per 1281 [RFC5910] is used: 1283 Contains the DS key tag value per [RFC5910] with 1284 type="unsignedShort" and isRequired="true". 1286 Contains the DS algorithm value per [RFC5910] 1287 with type="unsignedByte" and isRequired="true". 1289 Contains the DS digest type value per 1290 [RFC5910] with type="unsignedByte" and isRequired="true". 1292 Contains the DS digest value per [RFC5910] with 1293 type="hexBinary" and isRequired="true". 1295 The following "csvDomain" field elements MUST be used in the "dnssec" 1296 element when the Key Data Interface per 1297 [RFC5910] is used and MAY be used in the "dnssec" 1298 element when the DS Data Interface per [RFC5910] is 1299 used: 1301 Contains the flags field value per [RFC5910] with 1302 type="unsignedShort" and isRequired="true". 1304 Contains the Key protocol value per [RFC5910] 1305 with type="unsignedByte" and isRequired="true". 1307 Contains the Key algorithm value per [RFC5910] 1308 with type="unsignedByte" and isRequired="true". 1310 Contains the public key value per [RFC5910] with 1311 type="secDNS:keyType" and isRequired="true". 1313 The following "csvDomain" field elements MAY be used in the "dnssec" 1314 element: 1316 Indicates a child's preference for the 1317 number of seconds after signature generation when the parent's 1318 signature on the DS information provided by the child will expire 1319 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1321 The following "domain" fields, defined for the "domain" CSV File 1322 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1323 element: 1325 Domain name of the domain object associated with 1326 the DNSSEC record and isRequired="true". 1328 Example of a "dnssec" element with 1329 the DS Data Interface of [RFC5910]: 1331 1332 ... 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1345 dnssec-ds-YYYYMMDD.csv 1346 1347 1348 1349 ... 1350 1351 ... 1353 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1354 contains two DS records for domain1.example. 1356 domain1.example,604800,12345,3,1,49FD46E6C4B45C55D4AC 1357 domain1.example,604800,12346,3,1,38EC35D5B3A34B44C39B 1358 Example of a "dnssec" element with 1359 the Key Data Interface of [RFC5910]: 1361 1362 ... 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1375 dnssec-key-YYYYMMDD.csv 1376 1377 1378 1379 ... 1380 1381 ... 1383 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1384 contains two key records for domain1.example. 1386 domain1.example,604800,257,3,1,AQPJ////4Q== 1387 domain1.example,604800,257,3,1,AQPJ////4QQQ 1389 5.1.2.1.7. "domainTransfer" CSV File Definition 1391 The "domainTransfer" CSV File Definition defines the fields and CSV 1392 file references used for the domain name object pending and completed 1393 transfer records. No additional field elements were added for use in 1394 the "domainTransfer" element. 1396 The following "rdeCsv" fields, defined in section CSV common field 1397 elements (Section 4.6.2.2), MUST be used in the "domainTransfer" 1398 element: 1400 State of the most recent transfer request with 1401 isRequired="true". 1403 Identifier of the registrar, defined in Section 5.4, 1404 of the client that requested the transfer with isRequired="true". 1406 Date and time that the transfer was requested with 1407 isRequired="true". 1409 Identifier of the registrar, defined in Section 5.4, 1410 of the client that should take or took action with 1411 isRequired="true". 1413 Date and time that the transfer action should be 1414 taken or has been taken with isRequired="true". 1416 The following "rdeCsv" fields, defined in section CSV common field 1417 elements (Section 4.6.2.2), MAY be used in the "domainTransfer" 1418 element: 1420 Expiration date if the transfer command caused or 1421 causes a change in the validity period. 1423 Identifier of the client that requested the transfer. 1425 Identifier of the client that should take or took 1426 action for transfer. 1428 The following "csvDomain" fields, defined for the "domain" CSV File 1429 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1430 element: 1432 Domain name of the domain object involved in the 1433 transfer with isRequired="true". 1435 Example of a "domainTransfer" 1436 element. 1438 ... 1439 1440 ... 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1456 domainTransfer-YYYYMMDD.csv 1457 1458 1459 1460 ... 1461 1462 ... 1464 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1465 file contains one domain transfer record with a pending status. 1467 domain1.example,pending,registrarX,clientY, 1468 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1469 2016-04-03T22:00:00.0Z 1471 5.1.2.2. 1473 The is used to hold the deleted domain name 1474 objects in a differential or incremental deposit. All the domain 1475 name object data is deleted as part of a cascade delete. The 1476 is split into separate CSV file definitions using 1477 named elements with the "name" attribute. The following 1478 section defines the supported domain name deletes CSV file 1479 definition. 1481 5.1.2.2.1. "domain" Deletes CSV File Definition 1483 The following "csvDomain" field elements MUST be used in the deletes 1484 "domain" element: 1486 Domain name field with type="eppcom:labelType" and 1487 isRequired="true". 1489 Example of a "domain" element: 1491 ... 1492 1493 ... 1494 1495 1496 1497 1498 1499 1501 domain-delete-YYYYMMDD.csv 1502 1503 1504 1505 ... 1506 1507 ... 1509 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1510 file contains two domain name records. 1512 domain1.example 1513 domain2.example 1515 5.2. Host Object 1517 The host object is based on the EPP host name mapping in [RFC5732]. 1518 The host object supports both the XML Model and the CSV Model, 1519 defined in Models (Section 2) section. The elements used for both 1520 models are defined in the following sections. Both the 1521 and elements contain one or more 1522 elements with a set of named CSV file definitions using 1523 the "name" attribute. 1525 5.2.1. XML Model 1527 There are two elements used in the data escrow of the host objects 1528 for the XML model including the , under the 1529 element, and the element, under 1530 the element. 1532 A element substitutes for the 1533 abstract element to define a concrete definition of a host. The 1534 element can be replaced by other host 1535 definitions using the XML schema substitution groups feature. 1537 5.2.1.1. element 1539 The RDE host object is based on the EPP host response for an 1540 authorized client (Section 3.1.2. of [RFC5732]). 1542 The OPTIONAL element contains the following child elements: 1544 o A element that contains the fully qualified name of the 1545 host object. 1547 o A element that contains the repository object identifier 1548 assigned to the host object when the object was created. 1550 o One or more elements that describe the status of the host 1551 object. 1553 o Zero or more elements that contain the IP addresses 1554 associated with the host object. 1556 o A element that contains the identifier of the sponsoring 1557 registrar. 1559 o An OPTIONAL element that contains the identifier of the 1560 registrar that created the host object. An OPTIONAL client 1561 attribute is used to specify the client that performed the 1562 operation. 1564 o An OPTIONAL element that contains the date and time of 1565 host-object creation. 1567 o An OPTIONAL element that contains the identifier of the 1568 registrar that last updated the host object. This element MUST 1569 NOT be present if the host object has never been modified. An 1570 OPTIONAL client attribute is used to specify the client that 1571 performed the operation. 1573 o An OPTIONAL element that contains the date and time of 1574 the most recent host-object modification. This element MUST NOT 1575 be present if the host object has never been modified. 1577 o An OPTIONAL element that contains the date and time of 1578 the most recent host object successful transfer. This element 1579 MUST NOT be present if the domain name object has never been 1580 transfered. 1582 Example of object: 1584 ... 1585 1586 ns1.example1.example 1587 Hns1_example_test-TEST 1588 1589 1590 192.0.2.2 1591 192.0.2.29 1592 1080:0:0:0:8:800:200C:417A 1593 RegistrarX 1594 RegistrarX 1595 1999-05-08T12:10:00.0Z 1596 RegistrarX 1597 2009-10-03T09:34:00.0Z 1598 1599 ... 1601 5.2.1.2. object 1603 The element contains the fully qualified domain name 1604 of a host that was deleted. The element also 1605 supports host removal based on roid to support SRS systems in which 1606 different hosts with the same fully qualified domain name are active 1607 at the same time. 1609 Example of object: 1611 ... 1612 1613 ... 1614 1615 ns1.example.example 1616 1617 ... 1618 1619 ... 1621 5.2.2. CSV Model 1623 For the CSV Model of the host object, the child 1624 element of the element is used to hold the new or 1625 updated host objects for the deposit. The child 1626 element of the element is used to hold the deleted or 1627 purged host objects for the deposit. 1629 Differential and incremental deposits are based on changes to the 1630 host objects. The updated host object data under the 1631 element is a cascade replace down all of the host 1632 CSV files starting with the parent "host" CSV File Definition 1633 (Section 5.2.2.1.1). The child CSV file definitions include a 1634 field. All the child CSV file 1635 definition data for the host objects in the parent "host" CSV File 1636 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1637 using the data in the child CSV files. The deleted host object data 1638 under the element is a cascade delete starting from 1639 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1641 5.2.2.1. 1643 The is used to hold the new or updated host object 1644 information for the deposit. The is split into 1645 separate CSV file definitions using named elements with 1646 the "name" attribute. The following sections include the supported 1647 host CSV file definitions. 1649 5.2.2.1.1. "host" CSV File Definition 1651 The "host" CSV File Definition defines the fields and CSV file 1652 references used for the host object records. 1654 The following "csvHost" field elements MUST be used in the "host" 1655 element: 1657 Host name field with type="eppcom:labelType" and 1658 isRequired="true". 1660 The following "rdeCsv" fields, defined in section CSV common field 1661 elements (Section 4.6.2.2), MUST be used in the "host" 1662 element: 1664 Repository Object IDentifier (ROID) assigned to the 1665 host object with isRequired="true". 1667 The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the 1668 "host" element: 1670 or A choice of: 1672 Identifier of the sponsoring client with 1673 isRequired="true". 1675 Contains the ID assigned by ICANN with 1676 type="positiveInteger". The attribute "isRequired" MUST equal 1677 "true". 1679 Identifier of the registrar, defined in Section 5.4, 1680 of the client that created the object. 1682 Identifier of the client that created the host 1683 object. 1685 Identifier of the registrar, defined in Section 5.4, 1686 of the client that updated the object. 1688 Identifier of the client that last updated the host 1689 object. 1691 Date and time that the host object was created. 1693 Date and time that the host object was last 1694 updated. 1696 Date and time that the host was last transferred. 1698 Example of a "host" element. 1700 ... 1701 1702 ... 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1719 host-YYYYMMDD.csv 1720 1721 1722 1723 ... 1724 1725 ... 1727 Example of the corresponding host-YYYYMMDD.csv file. The file 1728 contains six host records with four being internal hosts and two 1729 being external hosts. 1731 ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX, 1732 clientY,1999-05-08T12:10:00.0Z,registrarX, 1733 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1734 ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX, 1735 clientY,1999-05-08T12:10:00.0Z,registrarX, 1736 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1737 ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX, 1738 clientY,1999-05-08T12:10:00.0Z,registrarX, 1739 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1740 ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, 1741 clientY,1999-05-08T12:10:00.0Z,registrarX, 1742 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1743 ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, 1744 clientY,1999-05-08T12:10:00.0Z,registrarX, 1745 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1746 ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, 1747 clientY,1999-05-08T12:10:00.0Z,registrarX, 1748 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1750 5.2.2.1.2. "hostStatuses" CSV File Definition 1752 The "hostStatuses" CSV File Definition defines the fields and CSV 1753 file references used for the host object statuses. 1755 The following "csvHost" fields, defined for the "host" CSV File 1756 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1757 element: 1759 The status of the host with 1760 type="host:statusValueType" and isRequired="true". 1762 The following "rdeCsv" fields, defined in section CSV common field 1763 elements (Section 4.6.2.2), MUST be used in the "hostStatuses" 1764 element: 1766 Host object Registry Object IDentifier (ROID) 1767 assigned to the host object with isRequired="true". 1769 The following "rdeCsv" fields, defined in section CSV common field 1770 elements (Section 4.6.2.2), MAY be used in the "hostStatuses" 1771 element: 1773 Host object status description which is 1774 free form text describing the rationale for the status. The 1775 attribute "isRequired" MUST equal "true". 1777 Language of the field. 1779 Example of a "hostStatuses" element. 1781 ... 1782 1783 ... 1784 1785 1786 1787 1788 1789 1790 1791 1792 1794 hostStatuses-YYYYMMDD.csv 1795 1796 1797 1798 ... 1799 1800 ... 1802 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1803 file contains the statuses for the six host names 1804 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example, 1805 ns2.domain2.example, ns1.example.net and ns2.example.net. 1807 Hns1_domain1_test-TEST,ok,, 1808 Hns2_domain1_test-TEST,ok,, 1809 Hns1_domain2_test-TEST,ok,, 1810 Hns2_domain2_test-TEST,ok,, 1811 Hns1_example_test-TEST,ok,, 1812 Hns2_example_test-TEST,ok,, 1814 5.2.2.1.3. "hostAddresses" CSV File Definition 1816 The "hostAddresses" CSV File Definition defines the fields and CSV 1817 file references used for the host object IP addresses. 1819 The following "csvHost" field elements MUST be used in the 1820 "hostAddresses" element: 1822 IP addresses associated with the host object with 1823 type="host:addrStringType". The attribute "isRequired" MUST equal 1824 "true". 1826 IP addresses version associated with the host 1827 object with type="host:ipType". "host:ipType" has the enumerated 1828 values of "v4" or "v6". The attribute "isRequired" MUST equal 1829 "true". 1831 The following "rdeCsv" fields, defined in section CSV common field 1832 elements (Section 4.6.2.2), MUST be used in the "hostAddresses" 1833 element: 1835 Host object Registry Object IDentifier (ROID) 1836 assigned to the host object with isRequired="true". 1838 Example of a "hostAddresses" element. 1840 ... 1841 1842 ... 1843 1844 1845 1846 1847 1848 1849 1850 1852 hostAddresses-YYYYMMDD.csv 1853 1854 1855 1856 ... 1857 1858 ... 1860 Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The 1861 file contains the IP addresses for the host names 1862 ns1.domain1.example, ns2.domain1.example, ns1.domain2.example and 1863 ns2.domain2.example. 1865 Hns1_domain1_test-TEST,192.0.2.1,v4 1866 Hns2_domain1_test-TEST,2001:DB8::1,v6 1867 Hns1_domain2_test-TEST,192.0.2.2,v4 1868 Hns2_domain2_test-TEST,2001:DB8::2,v6 1870 5.2.2.2. 1872 The is used to hold the deleted host objects in a 1873 differential or incremental deposit. All the host object data is 1874 deleted as part of a cascade delete. The is split 1875 into separate CSV file definitions using named elements 1876 with the "name" attribute. The following section defines the 1877 supported host deletes CSV file definition. 1879 5.2.2.2.1. "host" Deletes CSV File Definition 1881 The following "rdeCsv" fields, defined in section CSV common field 1882 elements (Section 4.6.2.2), MUST be used in the "host" 1883 element: 1885 Repository Object IDentifier (ROID) assigned to the 1886 host object with isRequired="true". 1888 Example of a "host" element. 1890 ... 1891 1892 ... 1893 1894 1895 1896 1897 1898 1900 host-delete-YYYYMMDD.csv 1901 1902 1903 1904 ... 1905 1906 ... 1908 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1909 host records. 1911 Hns1_domain1_test-TEST 1912 Hns2_domain1_test-TEST 1913 Hns1_domain2_test-TEST 1914 Hns2_domain2_test-TEST 1916 5.3. Contact Object 1918 The contact object is based on the EPP contact name mapping in 1919 [RFC5733]. The contact object supports both the XML Model and the 1920 CSV Model, defined in Models (Section 2) section. The elements used 1921 for both models are defined in the following sections. 1923 5.3.1. XML Model 1925 There are two elements used in the data escrow of the contact objects 1926 for the XML model including the , under the 1927 element, and the element, 1928 under the element. 1930 A element substitutes for the abstract 1931 element to define a concrete definition of a contact. The 1932 element can be replaced by other contact 1933 definitions using the XML schema substitution groups feature. 1935 5.3.1.1. object 1937 The contact object is based on the EPP contact response for an 1938 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1939 including the data from an EPP Query Response, see 1940 Section 3.1.3. of [RFC5733]. 1942 The OPTIONAL element contains the following child elements: 1944 o A element that contains the server-unique identifier of the 1945 contact object 1947 o A element that contains the Repository Object IDentifier 1948 assigned to the contact object when the object was created. 1950 o One or more elements that describe the status of the 1951 contact object. 1953 o One or two elements that contain postal-address 1954 information. Two elements are provided so that address 1955 information can be provided in both internationalized and 1956 localized forms; a "type" attribute is used to identify the two 1957 forms. If an internationalized form (type="int") is provided, 1958 element content MUST be represented in a subset of UTF-8 that can 1959 be represented in the 7-bit US-ASCII character set. If a 1960 localized form (type="loc") is provided, element content MAY be 1961 represented in unrestricted UTF-8. The element 1962 contains the following child elements: 1964 * A element that contains the name of the individual or 1965 role represented by the contact. 1967 * An OPTIONAL element that contains the name of the 1968 organization with which the contact is affiliated. 1970 * An element that contains address information associated 1971 with the contact. An element contains the following 1972 child elements: 1974 + One, two, or three OPTIONAL elements that contain 1975 the contact's street address. 1977 + A element that contains the contact's city. 1979 + An OPTIONAL element that contains the contact's state 1980 or province. 1982 + An OPTIONAL element that contains the contact's postal 1983 code. 1985 + A element that contains the contact's two-letter 1986 country code. 1988 o An OPTIONAL element that contains the contact's voice 1989 telephone number. 1991 o An OPTIONAL element that contains the contact's facsimile 1992 telephone number. 1994 o An element that contains the contact's email address. 1996 o A element that contains the identifier of the sponsoring 1997 registrar. 1999 o An OPTIONAL element that contains the identifier of the 2000 registrar that created the contact object. An OPTIONAL client 2001 attribute is used to specify the client that performed the 2002 operation. 2004 o An OPTIONAL element that contains the date and time of 2005 contact-object creation. 2007 o An OPTIONAL element that contains the identifier of the 2008 registrar that last updated the contact object. This element MUST 2009 NOT be present if the contact has never been modified. An 2010 OPTIONAL client attribute is used to specify the client that 2011 performed the operation. 2013 o An OPTIONAL element that contains the date and time of 2014 the most recent contact-object modification. This element MUST 2015 NOT be present if the contact object has never been modified. 2017 o An OPTIONAL element that contains the date and time of 2018 the most recent contact object successful transfer. This element 2019 MUST NOT be present if the contact object has never been 2020 transferred. 2022 o An OPTIONAL element that contains the following child 2023 elements related to the last transfer request of the contact 2024 object: 2026 * A element that contains the state of the most recent 2027 transfer request. 2029 * A element that contains the identifier of the registrar 2030 that requested the domain name object transfer. An OPTIONAL 2031 client attribute is used to specify the client that performed 2032 the operation. 2034 * An element that contains the identifier of the registrar 2035 that SHOULD act upon a PENDING transfer request. For all other 2036 status types, the value identifies the registrar that took the 2037 indicated action. An OPTIONAL client attribute is used to 2038 specify the client that performed the operation. 2040 * A element that contains the date and time that the 2041 transfer was requested. 2043 * An element that contains the date and time of a 2044 required or completed response. For a PENDING request, the 2045 value identifies the date and time by which a response is 2046 required before an automated response action will be taken by 2047 the registry. For all other status types, the value identifies 2048 the date and time when the request was completed. 2050 o An OPTIONAL element that identifies elements that 2051 requiring exceptional server-operator handling to allow or 2052 restrict disclosure to third parties. See Section 2.9 of 2053 [RFC5733] for a description of the child elements contained within 2054 the element. 2056 Example object: 2058 ... 2059 2060 sh8013 2061 Csh8013-TEST 2062 2063 2064 2065 John Doe 2066 Example Inc. 2067 2068 123 Example Dr. 2069 Suite 100 2070 Dulles 2071 VA 2072 20166-6503 2073 US 2074 2075 2076 +1.7035555555 2077 +1.7035555556 2078 jdoe@example.example 2079 RegistrarX 2080 RegistrarX 2081 2009-09-13T08:01:00.0Z 2082 RegistrarX 2083 2009-11-26T09:10:00.0Z 2084 2009-12-03T09:05:00.0Z 2085 2086 pending 2087 clientW 2088 2011-03-08T19:38:00.0Z 2089 RegistrarX 2090 2011-03-13T23:59:59.0Z 2091 2092 2093 2094 2095 2096 2097 ... 2099 5.3.1.2. object 2101 The element contains the id of a contact that was 2102 deleted. 2104 Example of object: 2106 ... 2107 2108 ... 2109 2110 sh8013-TEST 2111 co8013-TEST 2112 2113 ... 2114 2115 ... 2117 5.3.2. CSV Model 2119 For the CSV Model of the contact object, the 2120 child element of the element is used to hold the new 2121 or updated contacts objects for the deposit. The 2122 child element of the element is 2123 used to hold the deleted or purged contact objects for the deposit. 2124 Both the and elements 2125 contain one or more elements with a set of named CSV 2126 file definitions using the "name" attribute. 2128 Differential and incremental deposits are based on changes to the 2129 contact objects. The updated contact object data under the 2130 element is a cascade replace down all of the 2131 contact CSV files starting with the parent "contact" CSV File 2132 Definition (Section 5.3.2.1.1). The child CSV file definitions 2133 include a field. All the child CSV 2134 file definition data for the contact objects in the parent "contact" 2135 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2136 then set using the data in the child CSV files. The deleted contact 2137 object data under the element is a cascade 2138 delete starting from the "contact" Deletes CSV File Definition 2139 (Section 5.3.2.2.1). 2141 5.3.2.1. 2143 The is used to hold the new or updated contact 2144 object information for the deposit. The is 2145 split into separate CSV file definitions using named 2146 elements with the "name" attribute. The following sections include 2147 the supported contact CSV file definitions. 2149 5.3.2.1.1. "contact" CSV File Definition 2151 The "contact" CSV File Definition defines the fields and CSV file 2152 references used for the contact object records. 2154 The following "csvContact" field elements MUST be used in the 2155 "contact" element: 2157 Contains the server-unique contact identifier with 2158 type="eppcom:clIDType" and isRequired="true". 2160 Contains the contact's email address with 2161 type="eppcom:minTokenType" and isRequired="true". 2163 The following field elements MAY be used in the "contact" 2164 element: 2166 Contains the contact's voice telephone number 2167 with type="contact:e164StringType". 2169 Contains the contact's voice telephone number 2170 extension with type="token". 2172 Contains the contact's facsimile telephone number 2173 with type="contact:e164StringType". 2175 Contains the contact's facsimile telephone 2176 number extension with type="token". 2178 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 2179 "contact" element: 2181 The Registry Object IDentifier (ROID) for the contact 2182 object with isRequired="true". 2184 or A choice of: 2186 Identifier of the sponsoring client with 2187 isRequired="true". 2189 Contains the ID assigned by ICANN with 2190 type="positiveInteger". The attribute "isRequired" MUST equal 2191 "true". 2193 The following "rdeCsv" fields, defined in section CSV common field 2194 elements (Section 4.6.2.2), MAY be used in the "contact" 2195 element: 2197 Identifier of the registrar, defined in Section 5.4, 2198 of the client that created the object. 2200 Identifier of the client that created the contact 2201 object. 2203 Identifier of the registrar, defined in Section 5.4, 2204 of the client that updated the object. 2206 Identifier of the client that last updated the 2207 contact object. 2209 Created date and time of the contact object. 2211 Date and time of the last update to the contact 2212 object. 2214 Date and time of the last transfer for the contact 2215 object. 2217 Example of a "contact" element. 2219 ... 2220 2221 ... 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2242 contact-YYYYMMDD.csv 2243 2244 2245 2246 ... 2247 2248 ... 2250 Example of the contact-YYYYMMDD.csv file. The file contains nine 2251 object contact records. 2253 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2254 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2255 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2256 2009-11-26T09:10:00.0Z 2257 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2258 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2259 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2260 2009-11-26T09:10:00.0Z 2261 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2262 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2263 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2264 2009-11-26T09:10:00.0Z 2265 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2266 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2267 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2268 2009-11-26T09:10:00.0Z 2269 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2270 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2271 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2272 2009-11-26T09:10:00.0Z 2273 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2274 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2275 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2276 2009-11-26T09:10:00.0Z 2277 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2278 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2279 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2280 2009-11-26T09:10:00.0Z 2281 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2282 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2283 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2284 2009-11-26T09:10:00.0Z 2285 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2286 +1.7035555556,,jdoe@example.example,registrarX,registarX, 2287 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2288 2009-11-26T09:10:00.0Z 2290 5.3.2.1.2. "contactStatuses" CSV File Definition 2292 The "contactStatuses" CSV File Definition defines the fields and CSV 2293 file references used for the contact object statuses. 2295 The following "csvContact" field elements, defined for the "contact" 2296 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2297 "contactStatuses" element: 2299 Server-unique contact identifier of status with 2300 isRequired="true". 2302 The status of the contact with 2303 type="contact:statusValueType" and isRequired="true". 2305 The following "rdeCsv" fields, defined in section CSV common field 2306 elements (Section 4.6.2.2), MAY be used in the "contactStatuses" 2307 element: 2309 The contact object status description 2310 which is free form text describing the rationale for the status. 2312 Language of the field. 2314 Example of a "contactStatuses" 2315 element. 2317 ... 2318 2319 ... 2320 2321 2322 2323 2324 2325 2326 2327 2328 2330 contactStatuses-YYYYMMDD.csv 2331 2332 2333 2334 ... 2335 2336 ... 2338 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2339 file contains the statuses for the nine contact identifiers. 2341 domain1admin,ok,, 2342 domain1tech,ok,, 2343 domain1billing,ok,, 2344 domain2admin,ok,, 2345 domain2tech,ok,, 2346 domain2billing,ok,, 2347 xnabc123admin,ok,, 2348 xnabc123tech,ok,, 2349 xnabc123billing,ok,, 2351 5.3.2.1.3. "contactPostal" CSV File Definition 2353 The "contactPostal" CSV File Definition defines the fields and CSV 2354 file references used for the contact postal info object records. 2356 The following "csvContact" field elements MUST be used in the 2357 "contactPostal" element: 2359 Contains the form of the postal-address 2360 information with type="contact:postalLineType" and 2361 isRequired="true". This field specifies the form ("int" or 2362 "loc"), as defined in Section 4.6.3, of the , 2363 , , , 2364 , , fields. 2366 Contains the contact's name of the individual or 2367 role represented by the contact with type="contact:postalLineType" 2368 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2369 indicate the localized or internationalized form as defined in 2370 section Section 4.6.3. 2372 Contains the contact's contact's street address 2373 line with type="contact:fPostalLineType". An index attribute is 2374 required to indicate which street address line the field 2375 represents with index "0" for the first line and index "2" for the 2376 last line. An OPTIONAL "isLoc" attribute to used to indicate the 2377 localized or internationalized form as defined in section 2378 Section 4.6.3. 2380 Contains the contact's city with 2381 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2382 "isLoc" attribute to used to indicate the localized or 2383 internationalized form as defined in section Section 4.6.3. 2385 Contains the contact's country code with 2386 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2387 attribute to used to indicate the localized or internationalized 2388 form as defined in section Section 4.6.3. 2390 The following "csvContact" field elements MAY be used in the 2391 "contactPostal" element: 2393 Contains the name of the organization with which 2394 the contact is affiliated with type="contact:optPostalLineType". 2395 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2396 internationalized form as defined in section Section 4.6.3. 2398 Contains the contact's state or province with 2399 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2400 to used to indicate the localized or internationalized form as 2401 defined in section Section 4.6.3. 2403 Contains the contact's postal code with 2404 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2405 indicate the localized or internationalized form as defined in 2406 section Section 4.6.3. 2408 The following "csvContact" fields, defined for the "contact" CSV File 2409 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2410 element: 2412 Server-unique contact identifier for the contact 2413 object with isRequired="true". 2415 Example of a "contactPostal" 2416 element. 2418 ... 2419 2420 ... 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2438 contactPostal-YYYYMMDD.csv 2439 2440 2441 2442 ... 2443 2444 ... 2446 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2447 nine contact postal records. 2449 domain1admin,int,"John Doe","Example Inc.", 2450 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2451 domain1tech,int,"John Doe","Example Inc.", 2452 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2453 domain1billing,int,"John Doe","Example Inc.", 2454 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2455 domain2admin,int,"John Doe","Example Inc.", 2456 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2457 domain2tech,int,"John Doe","Example Inc.", 2458 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2459 domain2billing,int,"John Doe","Example Inc.", 2460 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2461 xnabc123admin,int,"John Doe","Example Inc.", 2462 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2463 xnabc123tech,int,"John Doe","Example Inc.", 2464 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2465 xnabc123billing,int,"John Doe","Example Inc.", 2466 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2468 5.3.2.1.4. "contactTransfer" CSV File Definition 2470 The "contactTransfer" CSV File Definition defines the fields and CSV 2471 file references used for the contact object pending and completed 2472 transfer records. No additional field elements were added for use in 2473 the "contactTransfer" element. The 2474 following "rdeCsv" fields, defined in section CSV common field 2475 elements (Section 4.6.2.2), MUST be used in the "contactTransfer" 2476 element: 2478 State of the most recent transfer request with 2479 isRequired="true". 2481 Identifier of the registrar, defined in Section 5.4, 2482 of the client that requested the transfer with isRequired="true". 2484 Date and time that the transfer was requested with 2485 isRequired="true". 2487 Identifier of the registrar, defined in Section 5.4, 2488 of the client that should take or took action with 2489 isRequired="true". 2491 Date and time that the transfer action should be 2492 taken or has been taken with isRequired="true". 2494 The following "rdeCsv" fields, defined in section CSV common field 2495 elements (Section 4.6.2.2), MAY be used in the "contactTransfer" 2496 element: 2498 Identifier of the client that requested the transfer. 2500 Identifier of the client that should take or took 2501 action for transfer. 2503 The following "csvContact" fields, defined for the "contact" CSV File 2504 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2505 element: 2507 Server-unique contact identifier for the contact 2508 object with isRequired="true". 2510 Example of a "contactTransfer" 2511 element. 2513 ... 2514 2515 ... 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2530 contactTransfer-YYYYMMDD.csv 2531 2532 2533 2534 ... 2535 2536 ... 2538 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2539 one contact transfer record in pending status. 2541 xnabc123admin,clientApproved,registrarX,clientX, 2542 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2544 5.3.2.1.5. "contactDisclose" CSV File Definition 2546 The "contactDisclose" CSV File Definition defines the fields and CSV 2547 file references used for the contact disclose object records. 2549 The following "csvContact" field elements MAY be used in the 2550 "contactDisclose" element: 2552 Contains flag with a value of "true" or 2553 "1" (one) notes the preference to allow disclosure of the 2554 specified elements as an exception to the stated data-collection 2555 policy. A value of "false" or "0" (zero) notes a client 2556 preference to not allow disclosure of the specified elements as an 2557 exception to the stated data-collection policy with 2558 type="boolean". The additional fields define specific exceptional 2559 disclosure preferences based on the 2560 field. 2562 Exceptional disclosure preference flag 2563 for the localized form of the contact name with type="boolean". 2565 Exceptional disclosure preference flag 2566 for the internationalized form of the contact name with 2567 type="boolean". 2569 Exceptional disclosure preference flag 2570 for the localized form of the contact organization with 2571 type="boolean". 2573 Exceptional disclosure preference flag 2574 for the internationalized form of the contact organization with 2575 type="boolean". 2577 Exceptional disclosure preference flag 2578 for the localized form of the contact address with type="boolean". 2580 Exceptional disclosure preference flag 2581 for the internationalized form of the contact address with 2582 type="boolean". 2584 Exceptional disclosure preference flag 2585 of the contact voice telephone number with type="boolean". 2587 Exceptional disclosure preference flag of 2588 the contact facsimile telephone number with type="boolean". 2590 Exceptional disclosure preference flag 2591 of the contact email address with type="boolean". 2593 The following "csvContact" fields, defined for the "contact" CSV File 2594 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2595 element: 2597 Server-unique contact identifier for the contact 2598 object with isRequired="true". 2600 Example of a "contactDisclose" 2601 element. 2603 ... 2604 2605 ... 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2623 contactDisclose-YYYYMMDD.csv 2624 2625 2626 2627 ... 2628 2629 ... 2631 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2632 one disclosure records, disabling disclosure of voice, fax, and 2633 email. 2635 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2637 5.3.2.2. 2639 The is used to hold the deleted contact objects 2640 in a differential or incremental deposit. All the contact object 2641 data is deleted as part of a cascade delete. The 2642 is split into separate CSV file definitions 2643 using named elements with the "name" attribute. The 2644 following section defines the supported contact deletes CSV file 2645 definition. 2647 5.3.2.2.1. "contact" Deletes CSV File Definition 2649 The following "csvContact" field elements MUST be used in the deletes 2650 "contact" element: 2652 Contains the server-unique contact identifier with 2653 type="eppcom:clIDType" and isRequired="true". 2655 Example of a "contact" element. 2657 ... 2658 2659 ... 2660 2661 2662 2663 2664 2665 2667 contact-delete-YYYYMMDD.csv 2668 2669 2670 2671 ... 2672 2673 ... 2675 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2676 six contact records. 2678 domain1admin 2679 domain1tech 2680 domain1billing 2681 domain2admin 2682 domain2tech 2683 domain2billing 2685 5.4. Registrar Object 2687 The registrar object represents the sponsoring client for other 2688 objects, for operational purposes MAY be the registry operator. The 2689 registrar object supports both the XML Model and the CSV Model, 2690 defined in Section 2. The elements used for both models are defined 2691 in the following sections. 2693 5.4.1. XML Model 2695 There are two elements used in the data escrow of the registrar 2696 objects for the XML model including the , 2697 under the element, and the 2698 element, under the element. 2700 A element substitutes for the 2701 abstract element to define a 2702 concrete definition of a registrar. The 2703 element can be replaced by other 2704 domain definitions using the XML schema substitution groups feature. 2706 5.4.1.1. element 2708 The element contains the following child elements: 2710 o An element that contains the Registry-unique identifier of 2711 the registrar object. This has a superordinate relationship 2712 to a subordinate , or of domain, contact and 2713 host objects. 2715 o An element that contains the name of the registrar. 2717 o An OPTIONAL element that contains the ID assigned by 2718 ICANN. 2720 o An OPTIONAL element that contains the operational status 2721 of the registrar. Possible values are: ok, readonly and 2722 terminated. 2724 o Zero or two OPTIONAL elements that contain postal- 2725 address information. Two elements are provided so that address 2726 information can be provided in both internationalized and 2727 localized forms; a "type" attribute is used to identify the two 2728 forms. If an internationalized form (type="int") is provided, 2729 element content MUST be represented in a subset of UTF-8 that can 2730 be represented in the 7-bit US-ASCII character set. If a 2731 localized form (type="loc") is provided, element content MAY be 2732 represented in unrestricted UTF-8. The element 2733 contains the following child elements: 2735 * A element that contains address information associated 2736 with the registrar. The element contains the following 2737 child elements: 2739 + One, two, or three OPTIONAL elements that contain 2740 the registrar's street address. 2742 + A element that contains the registrar's city. 2744 + An OPTIONAL element that contains the registrar's state 2745 or province. 2747 + An OPTIONAL element that contains the registrar's 2748 postal code. 2750 + A element that contains the registrar's country code. 2752 o An OPTIONAL element that contains the registrar's voice 2753 telephone number. 2755 o An OPTIONAL element that contains the registrar's facsimile 2756 telephone number. 2758 o An OPTIONAL element that contains the registrar's email 2759 address. 2761 o An OPTIONAL element that contains the registrar's URL. 2763 o An OPTIONAL elements that contains whois information. 2764 The element contains the following child elements: 2766 * An OPTIONAL element that contains the name of the 2767 registrar WHOIS server listening on TCP port 43 as specified in 2768 [RFC3912]. 2770 * An OPTIONAL element that contains the name of the 2771 registrar WHOIS server listening on TCP port 80/443. 2773 o An OPTIONAL element that contains the date and time of 2774 registrar-object creation. 2776 o An OPTIONAL element that contains the date and time of 2777 the most recent RDE registrar-object modification. This element 2778 MUST NOT be present if the rdeRegistrar object has never been 2779 modified. 2781 Example of object: 2783 ... 2784 2785 RegistrarX 2786 Registrar X 2787 123 2788 ok 2789 2790 2791 123 Example Dr. 2792 Suite 100 2793 Dulles 2794 VA 2795 20166-6503 2796 US 2797 2798 2799 +1.7035555555 2800 +1.7035555556 2801 jdoe@example.example 2802 http://www.example.example 2803 2804 whois.example.example 2805 http://whois.example.example 2806 2807 2005-04-23T11:49:00.0Z 2808 2009-02-17T17:51:00.0Z 2809 2810 ... 2812 5.4.1.2. object 2814 The element contains the id of a registrar that 2815 was deleted. 2817 Example of object: 2819 ... 2820 2821 ... 2822 2823 agnt0001-TEST 2824 2825 ... 2826 2827 ... 2829 5.4.2. CSV Model 2831 For the CSV Model of the registrar object, the 2832 child element of the element 2833 is used to hold the new or updated registrar objects for the deposit. 2834 The child element of the element 2835 is used to hold the deleted or purged registrar objects for the 2836 deposit. Both the and 2837 elements contain one or more elements with a set of 2838 named CSV file definitions using the "name" attribute. 2840 Differential and incremental deposits are based on changes to the 2841 registrar objects. The updated registrar object data under the 2842 element is a cascade replace down all of the 2843 registrar CSV files starting with the parent "registrar" CSV File 2844 Definition (Section 5.4.2.1.1). The child CSV file definitions 2845 include a field. All the child CSV 2846 file definition data for the registrar objects in the parent 2847 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2848 deleted and then set using the data in the child CSV files. The 2849 deleted registrar object data under the 2850 element is a cascade delete starting from the "registrar" Deletes CSV 2851 File Definition (Section 5.4.2.2.1). 2853 5.4.2.1. 2855 The is used to hold the new or updated 2856 registrar object information for the deposit. The 2857 is split into separate CSV file definitions 2858 using named elements with the "name" attribute. The 2859 following sections include the supported contact CSV file 2860 definitions. 2862 5.4.2.1.1. "registrar" CSV File Definition 2864 The "registrar" CSV File Definition defines the fields and CSV file 2865 references used for the registrar object records. 2867 The following "csvRegistrar" field elements MUST be used in the 2868 "registrar" element: 2870 or A choice of: 2872 Contains the server-unique registrar 2873 identifier with type="eppcom:clIDType" and isRequired="true". 2875 Contains the ID assigned by ICANN with 2876 type="positiveInteger". The attribute "isRequired" MUST equal 2877 "true". 2879 Contains the name of the registrar with 2880 type="normalizedString" and isRequired="true". 2882 The following field elements MAY be used in the "registrar" 2883 element: 2885 Contains the status of the registrar with 2886 type="csvRegistrar:statusValueType". 2888 Contains the ID assigned by ICANN with 2889 type="positiveInteger". This field is included in this section in 2890 addition to the section above to support optionally providing the 2891 field when the field is 2892 used. 2894 Contains the Whois URL of the registrar 2895 with type="anyURI". 2897 The following "rdeCsv" fields, defined in section CSV common field 2898 elements (Section 4.6.2.2), MAY be used in the "registrar" 2899 element: 2901 Created date and time of the registrar object. 2903 Date and time of the last update to the registrar 2904 object. 2906 URL for the registrar web home page. 2908 The following "csvContact" fields, defined in section Contact Object 2909 (Section 5.3), MAY be used in the "registrar" 2910 element: 2912 Registrar street address line with an "index" 2913 attribute that represents the order of the street address line 2914 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2915 indicate the localized or internationalized form, as defined in 2916 Section 4.6.3. 2918 Registrar city with an OPTIONAL "isLoc" attribute 2919 that is used to indicate the localized or internationalized form, 2920 as defined in Section 4.6.3. 2922 Registrar country code with an OPTIONAL "isLoc" 2923 attribute that is used to indicate the localized or 2924 internationalized form, as defined in Section 4.6.3. 2926 Registrar email address. The attribute 2927 "isRequired" MUST equal "false". 2929 Registrar state or province with an OPTIONAL 2930 "isLoc" attribute that is used to indicate the localized or 2931 internationalized form, as defined in Section 4.6.3. 2933 Registrar postal code with an OPTIONAL "isLoc" 2934 attribute that is used to indicate the localized or 2935 internationalized form, as defined in Section 4.6.3. 2937 Registrar voice telephone number. 2939 Registrar voice telephone number extension. 2941 Registrar facsimile telephone number. 2943 Registrar facsimile telephone number extension. 2945 Example of a "registrar" 2946 element. 2948 ... 2949 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 2977 registrar-YYYYMMDD.csv 2978 2979 2980 2981 ... 2982 2983 ... 2985 Example of the registrar-YYYYMMDD.csv file. The file contains three 2986 registrar records. 2988 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 2989 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2990 +1.7035555556,,jdoe@example.example,http://www.example.example, 2991 http://whois.example.example,2005-04-23T11:49:00.0Z, 2992 2009-02-17T17:51:00.0Z 2993 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 2994 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2995 +1.7035555556,,jdoe@example.example,http://www.example.example, 2996 http://whois.example.example,2005-04-23T11:49:00.0Z, 2997 2009-02-17T17:51:00.0Z 2998 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 2999 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 3000 +1.7035555556,,jdoe@example.example,http://www.example.example, 3001 http://whois.example.example,2005-04-23T11:49:00.0Z, 3002 2009-02-17T17:51:00.0Z 3004 5.4.2.2. 3006 The is used to hold the deleted registrar 3007 objects in a differential or incremental deposit. All the registrar 3008 object data is deleted as part of a cascade delete. The 3009 is split into separate CSV file definitions 3010 using named elements with the "name" attribute. The 3011 following section defines the supported registrar deletes CSV file 3012 definition. 3014 5.4.2.2.1. "registrar" Deletes CSV File Definition 3016 The following "csvRegistrar" field elements MUST be used in the 3017 deletes "registrar" element: 3019 or A choice of: 3021 Contains the server-unique registrar 3022 identifier with type="eppcom:clIDType" and isRequired="true". 3024 Contains the ID assigned by ICANN with 3025 type="positiveInteger". The attribute "isRequired" MUST equal 3026 "true". 3028 Example of a "registrar" element. 3030 ... 3031 3032 ... 3033 3034 3035 3036 3037 3038 3040 registrar-delete-YYYYMMDD.csv 3041 3042 3043 3044 ... 3045 3046 ... 3048 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 3049 one registrar record. 3051 registrarZ 3053 5.5. IDN Table Reference Object 3055 The Internationalized Domain Names (IDN) table reference object is a 3056 pseudo-object that is used to provide a short reference to the IDN 3057 Table and Policy used in IDN registrations. The IDN reference object 3058 supports both the XML and the CSV Model, defined in the Models 3059 (Section 2) section. The elements used for both models are defined 3060 in the following sections. 3062 5.5.1. XML Model 3064 There is one element used in the data escrow of the IDN table 3065 reference objects for the XML model that is the , 3066 under the element. 3068 5.5.1.1. object 3070 The contains the following elements. An "id" 3071 attribute is used to specify an identifier for the IDN table. 3073 o An element that contains the URL of the IDN table that is 3074 being referenced. 3076 o A element that contains the URL of the IDN policy 3077 document. If IDN variants are generated algorithmically, the 3078 policy document MUST define the algorithm and the state of the 3079 implicit generated IDN variants. For a list of suggested states 3080 for implicit IDN variants, please see [variantTLDsReport]. 3082 Example of object: 3084 ... 3085 3086 3087 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3088 3089 3090 http://registro.br/dominio/regras.html 3091 3092 3093 ... 3095 5.5.2. CSV Model 3097 The IDN domain names, defined in Section 5.1, MAY have references to 3098 the IDN language identifier using the field 3099 element. The IDN table reference object defines the mapping of a 3100 language identifier to a language table URL. The language table URL 3101 defines the character code points that can be used for the language 3102 identifier. The elements used for the IDN table reference object is 3103 defined in this section. The child element of the 3104 element is used to hold the new or updated IDN table 3105 reference objects for the deposit. The child 3106 element of the element is used to hold the deleted or 3107 purged IDN table reference objects for the deposit. Both the 3108 and elements contain one or more 3109 elements with a set of named CSV file definitions using 3110 the "name" attribute. 3112 5.5.2.1. 3114 The is used to hold the new or updated IDN table 3115 reference object information for the deposit. The 3116 is split into separate CSV file definitions using named 3117 elements with the "name" attribute. The following sections include 3118 the supported IDN table reference CSV file definitions. 3120 5.5.2.1.1. "idnLanguage" CSV File Definition 3122 The "idnLanguage" CSV File Definition defines the fields and CSV file 3123 references used for the IDN table reference object records. 3125 The following "rdeCsv" fields, defined in Section 4.6.2.2, MUST be 3126 used in the "idnLanguage" element: 3128 The language identifier that matches the values 3129 for the field element in the "domain" CSV 3130 File Definition (Section 5.1.2.1.1) files. The attribute 3131 "isRequired" MUST equal "true". 3133 URL that defines the character code points that can be 3134 used for the language defined by the field element. 3135 The attribute "isRequired" MUST equal "true". 3137 Example of a "idnLanguage" element. 3139 ... 3140 3141 ... 3142 3143 , 3144 3145 3146 3147 3148 3149 3151 idnLanguage-YYYYMMDD.csv 3152 3153 3154 3155 ... 3156 3157 ... 3159 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3160 contains two IDN language records. 3162 LANG-1, 3163 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3164 LANG-2, 3165 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3167 5.5.2.2. 3169 The is used to hold the deleted IDN table reference 3170 objects in a differential or incremental deposit. The 3171 is split into separate CSV file definitions using 3172 named elements with the "name" attribute. The following 3173 section defines the supported IDN table reference deletes CSV file 3174 definition. 3176 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3178 The following "idnLanguage" field elements MUST be used in the 3179 deletes "idnLanguage" element: 3181 The language identifier that matches the values 3182 for the field element in the "domain" CSV 3183 File Definition (Section 5.1.2.1.1) files. The attribute 3184 "isRequired" MUST equal "true". 3186 Example of a "idnLanguage" element. 3188 ... 3189 3190 ... 3191 3192 3193 3194 3195 3196 3198 idnLanguage-delete-YYYYMMDD.csv 3199 3200 3201 3202 ... 3203 3204 ... 3206 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3207 contains one IDN language record. 3209 LANG-2 3211 5.6. NNDN Object 3213 A NNDN (NNDN's not domain name) can be used to store registry 3214 reserved names or (blocked, withheld or mirrored) IDN variants. 3216 Domain Name Registries may maintain domain names without them being 3217 persisted as domain objects in the registry system, for example, a 3218 list of reserved names not available for registration. The NNDN is a 3219 lightweight domain-like object that is used to escrow domain names 3220 not maintained as domain name objects. 3222 A domain name can only exist as a domain name object or NNDN object, 3223 but not both. 3225 The NNDN object supports both the XML and the CSV Model, defined in 3226 the Models (Section 2) section. The elements used for both models 3227 are defined in the following sections. 3229 5.6.1. XML Model 3231 There are two elements used in the data escrow of the NNDN objects 3232 for the XML model including the , under the 3233 element, and the element, under the 3234 element. 3236 A element substitutes for the 3237 abstract element to define a concrete definition of a NNDN. The 3238 element can be replaced by other NNDN 3239 definitions using the XML schema substitution groups feature. 3241 5.6.1.1. object 3243 The element contains the following child elements: 3245 o An element that contains the fully qualified name of the 3246 NNDN. If the NNDN is an IDN, the ASCII Compatible Encoding (ACE) 3247 MUST be used. 3249 o An OPTIONAL element that contains the fully qualified name 3250 of the NNDN in Unicode character set. It MUST be provided if 3251 available. 3253 o An OPTIONAL element that references the IDN 3254 Table used for the NNDN. This corresponds to the "id" attribute 3255 of the element. This element MUST be present if the 3256 NNDN is an IDN. 3258 o An OPTIONAL element is used to indicate that the 3259 NNDN is used for an IDN variant. This element contains the domain 3260 name used to generate the IDN variant. 3262 o A element that indicates the state of the NNDN: 3263 blocked, withheld or mirrored. 3265 * If a NNDN is considered undesirable for registration (i.e., 3266 unavailable for allocation to anyone), then the NNDN will be 3267 tagged as "blocked". 3269 * If a NNDN is considered a potential registration of a domain 3270 object for a registrant, then the NNDN will be tagged as 3271 "withheld". This status is only used when the NNDN is used for 3272 an IDN variant. 3274 * If a NNDN is considered a mirrored IDN variant of a domain 3275 object, then the NNDN will be tagged as "mirrored". A 3276 mirroringNS attribute is used to specify if the mirrored IDN 3277 variant use the NS mirror mechanism. The default value of 3278 mirroringNS is true. If another mechanism such as DNAME is 3279 used, the value of mirroringNS attribute MUST be false. 3281 o An OPTIONAL element that contains the date and time of 3282 the NNDN object creation. 3284 Example of object: 3286 ... 3287 3288 xn--exampl-gva.example 3289 pt-BR 3290 example1.example 3291 withheld 3292 2005-04-23T11:49:00.0Z 3293 3294 ... 3296 5.6.1.2. object 3298 The element contains the ACE of a NNDN that was 3299 deleted, i.e., the . 3301 Example of object: 3303 ... 3304 3305 ... 3306 3307 xn--pingino-q2a.example 3308 3309 ... 3310 3311 ... 3313 5.6.2. CSV Model 3315 For the CSV Model of the NNDN object, the child 3316 element of the element is used to hold the new or 3317 updated NNDN objects for the deposit. The child 3318 element of the element is used to hold the deleted or 3319 purged NNDN objects for the deposit. Both the and 3320 elements contain one or more elements 3321 with a set of named CSV file definitions using the 3322 "name" attribute. 3324 5.6.2.1. 3326 The is used to hold the new or updated NNDN object 3327 information for the deposit. The is split into 3328 separate CSV file definitions using named elements with 3329 the "name" attribute. The following sections include the supported 3330 NNDN CSV file definitions. 3332 5.6.2.1.1. "NNDN" CSV File Definition 3334 The "NNDN" CSV File Definition defines the fields and CSV file 3335 references used for the NNDN object records. 3337 The following "csvNNDN" field elements MUST be used in the "NNDN" 3338 element: 3340 ASCII Compatible Encoding (ACE) field of the NNDN 3341 with type="eppcom:labelType" and isRequired="true". 3343 State of the NNDN: blocked or withheld with 3344 type="rdeNNDN:nameState" and isRequired="true". See 3345 Section 5.6.1.1 for a description of the possible values for the 3346 element. 3348 The following field elements MAY be used in the "NNDN" 3349 element: 3351 Domain name used to generate the IDN variant 3352 with type="eppcom:labelType". 3354 Defines whether the "mirroring" 3355 uses the NS mirror mechanism, as described 3356 for the "mirroringNS" attribute in 3357 Section 5.6.1.1, with type="boolean". If the field element is not 3358 defined the default value is "true". 3360 The following "rdeCsv" fields, defined in section CSV common field 3361 elements (Section 4.6.2.2), MAY be used in the "NNDN" 3362 element: 3364 Created date and time of the NNDN object. 3366 Name of the NNDN in Unicode character set for the 3367 field element. 3369 IDN Table Identifier for the NNDN that matches 3370 an IDN Table Reference Object record, as defined in Section 5.5.2. 3372 Example of a "NNDN" element: 3374 ... 3375 3376 ... 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3389 NNDN-YYYYMMDD.csv 3390 3391 3392 3393 ... 3394 3395 ... 3397 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3398 contains two NNDN records for an IDN with one blocked variant and one 3399 mirrored variant. 3401 xn--abc456.example,LANG-1,xn--abc123.example, 3402 blocked,,2005-04-23T11:49:00.0Z 3403 xn--abc789.example,LANG-1,xn--abc123.example, 3404 mirrored,1,2005-04-23T11:49:00.0Z 3406 5.6.2.2. 3408 The is used to hold the deleted NNDN objects in a 3409 differential or incremental deposit. The is split 3410 into separate CSV file definitions using named elements 3411 with the "name" attribute. The following section defines the 3412 supported NNDN deletes CSV file definition. 3414 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3416 The following "NNDN" field elements MUST be used in the deletes 3417 "NNDN" element: 3419 ASCII Compatible Encoding (ACE) field of the NNDN 3420 with type="eppcom:labelType" and isRequired="true". 3422 Example of a "NNDN" element. 3424 ... 3425 3426 ... 3427 3428 3429 3430 3431 3432 3434 NNDN-delete-YYYYMMDD.csv 3435 3436 3437 3438 ... 3439 3440 ... 3442 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3443 contains one NNDN records. 3445 xn--abc456.example 3447 5.7. EPP Parameters Object 3449 The EPP Parameters Object is a pseudo-object that defines the set of 3450 object and object extension services supported by the registry, as 3451 defined in [RFC5730]. The EPP Parameters Object is only defined as 3452 XML but could be used in the XML model or CSV model. The EPP 3453 Parameters Object is defined using the 3454 element. The EPP Parameters Object SHOULD be included if the 3455 registry supports EPP. Only one EPP Parameters Object MUST exist at 3456 a certain point in time (watermark). 3458 The syntax and content of the children 3459 elements is as explained in section 2.4 of [RFC5730]. The children 3460 of the are as follows: 3462 o One or more elements that indicate the EPP versions 3463 supported by the registry. 3465 o One or more elements that indicate the identifiers of the 3466 text response languages supported by the registry's EPP server. 3468 o One or more elements that contain namespace URIs 3469 representing the objects that the registry's EPP server is capable 3470 of managing. 3472 o An OPTIONAL element that contains one or more 3473 elements that contain namespace URIs representing object 3474 extensions supported by the registry's EPP server. 3476 o A element that contains child elements used to describe the 3477 server's privacy policy for data collection and management. See 3478 section 2.4 of [RFC5730] for more details. 3480 Example of element object: 3482 ... 3483 3484 1.0 3485 en 3486 urn:ietf:params:xml:ns:domain-1.0 3487 3488 urn:ietf:params:xml:ns:contact-1.0 3489 3490 urn:ietf:params:xml:ns:host-1.0 3491 3492 3493 urn:ietf:params:xml:ns:rgp-1.0 3494 urn:ietf:params:xml:ns:secDNS-1.1 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 ... 3515 5.8. Policy Object 3517 The Policy object is a pseudo-object that is used to specify which 3518 OPTIONAL elements from the XML Model are REQUIRED based on the 3519 business model of the registry. For the CSV Model, the OPTIONAL 3520 "isRequired" attribute of the elements, defined in 3521 Section 4.6.2.1, is used to specify which OPTIONAL fields are 3522 REQUIRED based on the business model of the registry. 3524 5.8.1. object 3526 The OPTIONAL contains the following attributes: 3528 o An that defines that the referenced is 3529 REQUIRED. 3531 o that defines the XPath of the element referenced by 3532 . 3534 Example of object: 3536 ... 3537 3539 ... 3541 5.9. Header Object 3543 The Header Object is a pseudo-object that is used to specify the 3544 number of objects in the repository at a specific point in time 3545 (watermark) regardless of the type of deposit: differential, full or 3546 incremental. The Header Object may also be used to provide 3547 additional information on the contents of the deposit. The Header 3548 Object is only defined as XML but one header object MUST always be 3549 present per escrow deposit regardless of using XML Model or CSV 3550 Model. The Header Object is defined using the 3551 element. 3553 5.9.1. object 3555 The contains the following elements: 3557 o A choice of one of the elements defined in the 3558 "repositoryTypeGroup" group element that indicates the unique 3559 identifier for the repository being escrowed. Possible elements 3560 are: 3562 * A element that defines TLD or the REGISTRY- 3563 CLASS DOMAIN NAME (RCDN) being escrowed in the case of a 3564 Registry data escrow deposit. For IDNs the A-Label is used 3565 [RFC5891]. 3567 * A element that defines the Registrar ID 3568 corresponding to a Registrar data escrow deposit. In the case 3569 of an ICANN-accredited Registrar, the 3570 element MUST be the IANA Registrar ID assigned by ICANN. 3572 * A element that defines the provider ID 3573 corresponding to a Privacy and Proxy Services Provider data 3574 escrow deposit. In the case of an ICANN-accredited Privacy and 3575 Proxy Services Provider, the element MUST be 3576 the unique ID assigned by ICANN. 3578 * A element that defines the provider ID 3579 corresponding to a Reseller data escrow deposit. 3581 o A element that contains the number of objects in the SRS 3582 at a specific point in time (watermark) regardless of the type of 3583 deposit: differential, full or incremental. The element 3584 supports the following attributes: 3586 * A "uri" attribute reflects the XML namespace URI of the primary 3587 objects for the XML Model and CSV Model. For example, the 3588 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3589 domain name objects using the XML Model, and the "uri" is set 3590 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3591 objects using the CSV Model. 3593 * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS 3594 DOMAIN NAME (RCDN) of the objects included in the 3595 element. For IDNs the A-Label is used [RFC5891]. If the 3596 "rcdn" attribute is present, the value of the element 3597 must include only objects related to registrations in the same 3598 and lower levels. For example in a data escrow deposit for the 3599 .EXAMPLE TLD, a value of "example" in the "rcdn" attribute 3600 within the element indicates the number of objects in 3601 the TLD including objects in other RCDNs within the TLD, 3602 whereas a value of "com.example" indicates the number of 3603 elements for objects under "com.example" and lower levels. 3604 Omitting the "rcdn" attribute indicates that the total includes 3605 all objects of the specified "uri" in the repository (e.g. the 3606 TLD, Registrar, or PPSP). 3608 * An OPTIONAL "registrarId" attribute indicates the identifier of 3609 the sponsoring Registrar of the objects included in the 3610 element. In the case of an ICANN-accredited Registrar, the 3611 value MUST be the IANA Registrar ID assigned by ICANN. 3613 o An OPTIONAL element that contains a tag that defines 3614 the expected content in the deposit. The producer and consumer of 3615 the deposits will coordinate the set of possible 3616 element values. 3618 Example of object referencing only the XML Model 3619 objects: 3621 ... 3622 3623 test 3624 2 3626 1 3628 1 3630 1 3632 3633 1 3635 1 3637 1 3639 3640 3641 ... 3643 Example of object referencing the CSV and XML 3644 Model objects: 3646 ... 3647 3648 test 3649 2 3651 1 3653 1 3655 1 3657 3658 1 3660 1 3662 1 3664 3665 3666 ... 3668 6. RDE IDN Variants handling 3670 Depending on the Registration Policy of the Registry; for a domain 3671 name there may be multiple variant names. See [variantTLDsReport] 3672 for further detail on IDN variants. 3674 A registry could choose to escrow IDN variants as domains or NNDN 3675 objects. A specific IDN variant can be represented in the escrow 3676 deposit, as a domain or as a NNDN object, but not both. 3678 If using domain objects to represent IDN variants, the normal 3679 behavior during restoration of a SRS based on an escrow deposit is to 3680 restore the IDN variants as a mirrored variant. If the registration 3681 data of the IDN variant is different from the original name, the 3682 details of this specific implementation MUST be described in the IDN 3683 policy document. 3685 A NNDN or a domain name are explicit representations of an IDN 3686 variant while an IDN variant computed based on an algorithm is an 3687 implicit representation. Explicit representation of an IDN variant 3688 takes precedence over an implicit representation. 3690 7. Profile 3692 Different business models of registries exist, therefore the registry 3693 is responsible to define a profile that matches its particular 3694 business model. The profile mechanism allows a registry to extend 3695 this specification. 3697 A profile is the process of: 3699 1. Extending base objects with the mechanisms defined for XML and 3700 CSV models. 3702 * In the case of the XML model, abstract elements could be use 3703 to extend the following objects: , , , 3704 and using XML schema substitution groups 3705 feature. 3707 2. Defining a object to specify which OPTIONAL elements of 3708 this base specification is required based on the business model 3709 of the registry. An example is the element that is 3710 usually REQUIRED but it is specified as OPTIONAL in this 3711 specification to support existing business models. 3713 3. Adding new escrowed objects using the and 3714 elements. 3716 4. Providing the XML schemas to third parties that require them to 3717 validate the escrow deposits. 3719 8. Data escrow agent extended verification process 3721 A Data Escrow Agent SHOULD perform an extended verification process 3722 that starts by creating a dataset to be tested. 3724 o If a full deposit is to be tested, the full deposit is the 3725 dataset. 3727 o If an incremental deposit is to be tested, the dataset is created 3728 by using the incremental plus the last previous full deposit. 3730 o If a differential deposit is to be tested, the dataset is created 3731 by using the differential deposit plus all the required deposits 3732 leading to the last previous full deposit. 3734 The following are the minimum suggested tests on the dataset: 3736 o Validate the escrow deposits using the definition agreed with the 3737 registry. 3739 * In the case of the XML model, the contents of the escrow 3740 deposits MUST be validated using the XML schemas of the 3741 profile. 3743 o Count the objects and validate that the number of objects is equal 3744 to the number objects reported in the
element of the 3745 escrow deposit of that point in time (watermark). 3747 o All contact objects linked to domain names MUST be present. 3749 o All registrars objects linked to other objects MUST be present. 3751 o A domain name exists as a domain name or NNDN, but not both. 3753 o The elements listed as required in the element MUST be 3754 present. 3756 o All idnTableRef definitions linked from other objects MUST be 3757 present. 3759 o If an EPP Parameters Object was escrowed in the past, one and only 3760 one EPP Parameters Object MUST be present. 3762 o The watermark is not in the future. 3764 9. Formal Syntax 3766 Schemas are presented here. 3768 9.1. RDE CSV Schema 3770 Copyright (c) 2012 IETF Trust and the persons identified as authors 3771 of the code. All rights reserved. 3773 Redistribution and use in source and binary forms, with or without 3774 modification, are permitted provided that the following conditions 3775 are met: 3777 o Redistributions of source code must retain the above copyright 3778 notice, this list of conditions and the following disclaimer. 3780 o Redistributions in binary form must reproduce the above copyright 3781 notice, this list of conditions and the following disclaimer in 3782 the documentation and/or other materials provided with the 3783 distribution. 3785 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3786 names of specific contributors, may be used to endorse or promote 3787 products derived from this software without specific prior written 3788 permission. 3790 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3791 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3792 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3793 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3794 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3795 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3796 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3797 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3798 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3799 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3800 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3802 BEGIN 3803 3805 3812 3815 3817 3820 3821 3822 Registry Data Escrow Comma-Seperated Values (CSV) 3823 3824 3826 3827 3829 3830 3831 3832 3833 3834 3835 3836 3837 3839 3840 3841 3842 3843 3844 3845 3847 3848 3851 3852 3853 3855 3856 3857 3858 3859 3860 3862 3864 3865 3866 3868 3869 3870 3871 3872 3873 3875 3877 3878 3879 3881 3882 3883 3885 3886 3887 3888 3889 3891 3892 3893 3894 3895 3896 3897 3898 3900 3901 3902 3904 3905 3907 3908 3909 3910 3911 3913 3914 3915 3917 3918 3920 3921 3922 3923 3924 3926 3927 3928 3929 3930 3934 3935 3936 3938 3940 3942 3943 3945 3947 3949 3950 3952 3954 3956 3958 3960 3962 3964 3966 3968 3969 3970 3971 3972 3974 3975 3976 3977 3978 3979 3980 3981 3983 3984 3985 3987 3988 3990 3992 3994 3995 3997 3998 4000 4002 4003 4004 4005 4006 4008 4009 4010 4011 4012 4013 4014 4015 4017 4018 4019 4021 4022 4023 4024 4025 4026 4028 4029 4030 4031 4032 4033 4034 4035 4037 4038 4039 4041 4042 4043 4044 4045 4046 4048 4049 4050 4051 4052 4053 4054 4055 4057 4058 4059 4061 4062 4063 4064 4065 4066 4068 4069 4070 4071 4072 4073 4074 4075 4077 4078 4079 4081 4082 4083 4084 4085 4086 4088 4089 4090 4091 4092 4093 4094 4095 4097 4098 4099 4101 4102 4104 4105 4106 4107 4108 4110 4111 4112 4114 4115 4118 4119 4121 4122 4123 4124 4125 4127 4128 4129 4131 4132 4133 4134 4135 4136 4138 4139 4140 4142 4143 4144 4145 4146 4147 4149 4150 4151 4153 4154 4155 4156 4157 4158 4160 4161 4162 4164 4165 4167 4168 4169 4170 4171 4172 4174 4175 4176 4178 4179 4180 4181 4182 4183 4185 4186 4187 4188 4190 4191 4193 4194 4195 4196 4197 4198 4200 4201 4202 4203 4205 4206 4208 4209 4210 4211 4212 4215 4216 4217 4219 4222 4223 END 4225 9.2. RDE Domain Object 4227 Copyright (c) 2019 IETF Trust and the persons identified as authors 4228 of the code. All rights reserved. 4230 Redistribution and use in source and binary forms, with or without 4231 modification, are permitted provided that the following conditions 4232 are met: 4234 o Redistributions of source code must retain the above copyright 4235 notice, this list of conditions and the following disclaimer. 4237 o Redistributions in binary form must reproduce the above copyright 4238 notice, this list of conditions and the following disclaimer in 4239 the documentation and/or other materials provided with the 4240 distribution. 4242 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4243 names of specific contributors, may be used to endorse or promote 4244 products derived from this software without specific prior written 4245 permission. 4247 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4248 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4249 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4250 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4251 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4252 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4253 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4254 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4255 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4256 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4257 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4259 BEGIN 4260 4261 4272 4273 4274 4275 4276 4277 4279 4280 4281 Registry Data Escrow Domain provisioning schema 4282 4283 4285 4288 4290 4294 4295 4296 4297 4298 4299 4301 4303 4305 4307 4309 4312 4315 4317 4320 4322 4324 4326 4328 4330 4332 4334 4336 4338 4341 4342 4343 4344 4346 4347 4348 4350 4352 4354 4356 4358 4361 4362 4364 4365 4366 4367 4368 4369 4372 4373 4374 4375 4376 4377 END 4379 9.3. CSV Domain Object 4381 Copyright (c) 2012 IETF Trust and the persons identified as authors 4382 of the code. All rights reserved. 4384 Redistribution and use in source and binary forms, with or without 4385 modification, are permitted provided that the following conditions 4386 are met: 4388 o Redistributions of source code must retain the above copyright 4389 notice, this list of conditions and the following disclaimer. 4391 o Redistributions in binary form must reproduce the above copyright 4392 notice, this list of conditions and the following disclaimer in 4393 the documentation and/or other materials provided with the 4394 distribution. 4396 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4397 names of specific contributors, may be used to endorse or promote 4398 products derived from this software without specific prior written 4399 permission. 4401 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4402 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4403 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4404 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4405 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4406 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4407 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4408 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4409 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4410 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4411 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4413 BEGIN 4414 4416 4427 4430 4432 4434 4436 4438 4440 4443 4444 4445 Domain Name Comma-Separated Values (CSV) Object 4446 4447 4449 4452 4455 4456 4457 4458 4459 4460 4461 4462 4463 4465 4468 4471 4472 4473 4474 4475 4476 4477 4478 4479 4481 4482 4485 4486 4489 4490 4491 4492 4493 4495 4496 4497 4499 4500 4503 4504 4505 4506 4507 4509 4510 4511 4513 4515 4516 4518 4519 4520 4521 4522 4524 4525 4526 4528 4529 4532 4533 4536 4537 4540 4541 4544 4545 4548 4549 4552 4553 4556 4557 4559 4560 4561 4562 4563 4565 4566 4567 4569 4570 4573 4574 4578 4579 4582 4583 4584 4585 4586 4587 4589 4590 4591 4593 4596 4597 END 4599 9.4. RDE Host Object 4601 Copyright (c) 2019 IETF Trust and the persons identified as authors 4602 of the code. All rights reserved. 4604 Redistribution and use in source and binary forms, with or without 4605 modification, are permitted provided that the following conditions 4606 are met: 4608 o Redistributions of source code must retain the above copyright 4609 notice, this list of conditions and the following disclaimer. 4611 o Redistributions in binary form must reproduce the above copyright 4612 notice, this list of conditions and the following disclaimer in 4613 the documentation and/or other materials provided with the 4614 distribution. 4616 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4617 names of specific contributors, may be used to endorse or promote 4618 products derived from this software without specific prior written 4619 permission. 4621 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4622 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4623 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4624 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4625 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4626 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4627 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4628 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4629 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4630 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4631 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4633 BEGIN 4634 4635 4643 4644 4645 4646 4647 4648 Registry Data Escrow Host provisioning schema 4649 4650 4652 4654 4655 4658 4659 4660 4661 4662 4663 4665 4667 4669 4672 4674 4676 4678 4680 4682 4684 4685 4686 4687 4689 4690 4691 4692 4693 4694 4696 4698 4699 4700 4701 4702 4703 END 4705 9.5. CSV Host Object 4707 Copyright (c) 2012 IETF Trust and the persons identified as authors 4708 of the code. All rights reserved. 4710 Redistribution and use in source and binary forms, with or without 4711 modification, are permitted provided that the following conditions 4712 are met: 4714 o Redistributions of source code must retain the above copyright 4715 notice, this list of conditions and the following disclaimer. 4717 o Redistributions in binary form must reproduce the above copyright 4718 notice, this list of conditions and the following disclaimer in 4719 the documentation and/or other materials provided with the 4720 distribution. 4722 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4723 names of specific contributors, may be used to endorse or promote 4724 products derived from this software without specific prior written 4725 permission. 4727 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4728 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4729 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4730 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4731 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4732 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4733 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4734 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4735 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4736 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4737 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4739 BEGIN 4740 4741 4750 4753 4755 4757 4759 4762 4763 4764 Host Comma-Separated Values (CSV) Object 4765 4766 4768 4771 4774 4775 4776 4777 4778 4779 4780 4781 4782 4784 4787 4789 4790 4791 4792 4793 4794 4795 4796 4797 4799 4800 4803 4804 4806 4807 4808 4809 4810 4812 4813 4814 4816 4817 4819 4820 4821 4822 4823 4825 4826 4827 4829 4830 4833 4834 4835 4836 4837 4838 4840 4841 4842 4844 4847 4848 END 4850 9.6. RDE Contact Object 4852 Copyright (c) 2019 IETF Trust and the persons identified as authors 4853 of the code. All rights reserved. 4855 Redistribution and use in source and binary forms, with or without 4856 modification, are permitted provided that the following conditions 4857 are met: 4859 o Redistributions of source code must retain the above copyright 4860 notice, this list of conditions and the following disclaimer. 4862 o Redistributions in binary form must reproduce the above copyright 4863 notice, this list of conditions and the following disclaimer in 4864 the documentation and/or other materials provided with the 4865 distribution. 4867 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4868 names of specific contributors, may be used to endorse or promote 4869 products derived from this software without specific prior written 4870 permission. 4872 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4873 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4874 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4875 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4876 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4877 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4878 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4879 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4880 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4881 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4882 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4884 BEGIN 4885 4886 4894 4895 4896 4897 4899 4900 4901 Registry Data Escrow contact provisioning schema 4902 4903 4905 4908 4910 4914 4915 4916 4917 4918 4919 4921 4923 4925 4927 4929 4931 4933 4935 4937 4939 4941 4943 4945 4947 4949 4950 4951 4952 4954 4955 4956 4957 4958 4959 4960 4961 4962 4964 4965 4966 4967 4968 4969 4972 4973 4974 4975 4976 4977 END 4979 9.7. CSV Contact Object 4981 Copyright (c) 2012 IETF Trust and the persons identified as authors 4982 of the code. All rights reserved. 4984 Redistribution and use in source and binary forms, with or without 4985 modification, are permitted provided that the following conditions 4986 are met: 4988 o Redistributions of source code must retain the above copyright 4989 notice, this list of conditions and the following disclaimer. 4991 o Redistributions in binary form must reproduce the above copyright 4992 notice, this list of conditions and the following disclaimer in 4993 the documentation and/or other materials provided with the 4994 distribution. 4996 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4997 names of specific contributors, may be used to endorse or promote 4998 products derived from this software without specific prior written 4999 permission. 5001 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5002 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5003 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5004 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5005 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5006 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5007 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5008 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5009 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5010 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5011 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5013 BEGIN 5014 5016 5025 5029 5031 5033 5035 5038 5039 5040 Contact Comma-Separated Values (CSV) Object 5041 5042 5044 5047 5050 5051 5052 5053 5054 5055 5056 5057 5058 5060 5063 5066 5067 5068 5069 5070 5071 5072 5073 5074 5076 5077 5079 5080 5081 5082 5083 5085 5086 5087 5089 5090 5094 5095 5097 5099 5100 5101 5102 5103 5105 5106 5107 5109 5110 5112 5115 5116 5118 5119 5120 5121 5122 5124 5125 5126 5128 5132 5134 5135 5136 5137 5138 5140 5141 5142 5144 5145 5146 5147 5148 5149 5151 5152 5153 5154 5156 5157 5158 5159 5160 5161 5163 5164 5165 5166 5167 5168 5171 5172 5175 5176 5177 5179 5180 5181 5182 5183 5185 5186 5187 5189 5190 5193 5194 5197 5198 5200 5201 5202 5203 5204 5206 5207 5208 5209 5211 5212 5214 5215 5216 5217 5218 5220 5221 5222 5223 5225 5226 5228 5230 5232 5234 5236 5238 5240 5242 5244 5246 5248 5250 5252 5254 5256 5258 5260 5262 5264 5266 5267 5268 5269 5270 5272 5273 5274 5276 5277 5280 5281 5282 5283 5284 5285 5287 5288 5289 5291 5294 5295 END 5297 9.8. RDE Registrar Object 5299 Copyright (c) 2019 IETF Trust and the persons identified as authors 5300 of the code. All rights reserved. 5302 Redistribution and use in source and binary forms, with or without 5303 modification, are permitted provided that the following conditions 5304 are met: 5306 o Redistributions of source code must retain the above copyright 5307 notice, this list of conditions and the following disclaimer. 5309 o Redistributions in binary form must reproduce the above copyright 5310 notice, this list of conditions and the following disclaimer in 5311 the documentation and/or other materials provided with the 5312 distribution. 5314 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5315 names of specific contributors, may be used to endorse or promote 5316 products derived from this software without specific prior written 5317 permission. 5319 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5320 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5321 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5322 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5323 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5324 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5325 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5326 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5327 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5328 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5329 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5331 BEGIN 5332 5333 5342 5343 5344 5345 5346 5348 5349 5350 Registry Data Escrow registrar provisioning schema 5351 5352 5354 5358 5360 5363 5364 5365 5366 5367 5368 5370 5372 5374 5376 5379 5381 5383 5385 5387 5389 5391 5393 5394 5395 5396 5398 5399 5400 5401 5402 5403 5405 5406 5407 5408 5409 5410 5411 5413 5414 5415 5417 5418 5421 5423 5424 5425 5426 5427 5428 5430 5431 5432 5435 5437 5440 5442 5444 5445 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5459 5460 5461 5462 5463 5465 5466 5467 5468 5469 5471 5472 5473 5475 5477 5478 5480 5481 5482 5483 5484 5485 5488 5489 5490 5491 5492 5493 END 5495 9.9. CSV Registrar Object 5497 Copyright (c) 2012 IETF Trust and the persons identified as authors 5498 of the code. All rights reserved. 5500 Redistribution and use in source and binary forms, with or without 5501 modification, are permitted provided that the following conditions 5502 are met: 5504 o Redistributions of source code must retain the above copyright 5505 notice, this list of conditions and the following disclaimer. 5507 o Redistributions in binary form must reproduce the above copyright 5508 notice, this list of conditions and the following disclaimer in 5509 the documentation and/or other materials provided with the 5510 distribution. 5512 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5513 names of specific contributors, may be used to endorse or promote 5514 products derived from this software without specific prior written 5515 permission. 5517 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5518 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5519 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5520 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5521 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5522 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5523 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5524 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5525 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5526 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5527 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5529 BEGIN 5530 5532 5542 5545 5547 5549 5551 5553 5556 5557 5558 Registar Comma-Separated Values (CSV) Object 5559 5560 5562 5565 5568 5569 5570 5571 5572 5573 5574 5575 5576 5578 5581 5584 5585 5586 5587 5588 5589 5590 5591 5592 5594 5595 5598 5599 5602 5603 5604 5605 5606 5607 5609 5610 5611 5612 5614 5615 5619 5620 5622 5624 5625 5626 5627 5628 5630 5631 5632 5634 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5651 5652 5656 5659 5660 END 5662 9.10. RDE IDN Table Reference Objects 5664 Copyright (c) 2019 IETF Trust and the persons identified as authors 5665 of the code. All rights reserved. 5667 Redistribution and use in source and binary forms, with or without 5668 modification, are permitted provided that the following conditions 5669 are met: 5671 o Redistributions of source code must retain the above copyright 5672 notice, this list of conditions and the following disclaimer. 5674 o Redistributions in binary form must reproduce the above copyright 5675 notice, this list of conditions and the following disclaimer in 5676 the documentation and/or other materials provided with the 5677 distribution. 5679 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5680 names of specific contributors, may be used to endorse or promote 5681 products derived from this software without specific prior written 5682 permission. 5684 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5685 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5686 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5687 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5688 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5689 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5690 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5691 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5692 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5693 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5694 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5696 BEGIN 5697 5698 5704 5706 5707 5708 Registry Data Escrow IDN provisioning schema 5709 5710 5712 5714 5717 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5730 5731 5732 5733 5734 5735 5736 5738 5739 5741 5742 5743 5744 5745 5746 5747 5749 5750 END 5752 9.11. CSV IDN Language Object 5754 Copyright (c) 2012 IETF Trust and the persons identified as authors 5755 of the code. All rights reserved. 5757 Redistribution and use in source and binary forms, with or without 5758 modification, are permitted provided that the following conditions 5759 are met: 5761 o Redistributions of source code must retain the above copyright 5762 notice, this list of conditions and the following disclaimer. 5764 o Redistributions in binary form must reproduce the above copyright 5765 notice, this list of conditions and the following disclaimer in 5766 the documentation and/or other materials provided with the 5767 distribution. 5769 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5770 names of specific contributors, may be used to endorse or promote 5771 products derived from this software without specific prior written 5772 permission. 5774 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5775 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5776 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5777 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5778 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5779 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5780 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5781 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5782 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5783 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5784 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5786 BEGIN 5787 5789 5796 5799 5801 5804 5805 5806 IDN Language Comma-Separated Values (CSV) Object 5807 5808 5810 5813 5816 5817 5818 5819 5820 5821 5822 5823 5824 5826 5829 5832 5833 5834 5835 5836 5837 5838 5839 5840 5842 5845 5846 END 5848 9.12. EPP Parameters Object 5850 Copyright (c) 2019 IETF Trust and the persons identified as authors 5851 of the code. All rights reserved. 5853 Redistribution and use in source and binary forms, with or without 5854 modification, are permitted provided that the following conditions 5855 are met: 5857 o Redistributions of source code must retain the above copyright 5858 notice, this list of conditions and the following disclaimer. 5860 o Redistributions in binary form must reproduce the above copyright 5861 notice, this list of conditions and the following disclaimer in 5862 the documentation and/or other materials provided with the 5863 distribution. 5865 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5866 names of specific contributors, may be used to endorse or promote 5867 products derived from this software without specific prior written 5868 permission. 5870 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5871 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5872 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5873 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5874 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5875 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5876 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5877 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5878 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5879 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5880 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5882 BEGIN 5883 5884 5892 5893 5894 5896 5897 5898 Registry Data Escrow EPP Parameters schema 5899 5900 5902 5903 5906 5907 5910 5911 5912 5913 5914 5916 5918 5920 5923 5925 5926 5927 5928 5929 5930 END 5932 9.13. NNDN Object 5934 Copyright (c) 2019 IETF Trust and the persons identified as authors 5935 of the code. All rights reserved. 5937 Redistribution and use in source and binary forms, with or without 5938 modification, are permitted provided that the following conditions 5939 are met: 5941 o Redistributions of source code must retain the above copyright 5942 notice, this list of conditions and the following disclaimer. 5944 o Redistributions in binary form must reproduce the above copyright 5945 notice, this list of conditions and the following disclaimer in 5946 the documentation and/or other materials provided with the 5947 distribution. 5949 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5950 names of specific contributors, may be used to endorse or promote 5951 products derived from this software without specific prior written 5952 permission. 5954 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5955 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5956 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5957 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5958 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5959 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5960 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5961 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5962 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5963 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5964 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5966 BEGIN 5967 5968 5976 5977 5978 5980 5981 5982 Registry Data Escrow NNDN provisioning schema 5983 5984 5986 5988 5989 5992 5993 5994 5995 5996 5997 5999 6001 6003 6005 6007 6009 6010 6011 6012 6014 6015 6016 6017 6018 6019 6020 6022 6023 6024 6025 6027 6028 6029 6031 6032 6033 6034 6035 6036 6039 6040 6041 6042 6043 6044 END 6046 9.14. CSV NNDN Object 6048 Copyright (c) 2013 IETF Trust and the persons identified as authors 6049 of the code. All rights reserved. 6051 Redistribution and use in source and binary forms, with or without 6052 modification, are permitted provided that the following conditions 6053 are met: 6055 o Redistributions of source code must retain the above copyright 6056 notice, this list of conditions and the following disclaimer. 6058 o Redistributions in binary form must reproduce the above copyright 6059 notice, this list of conditions and the following disclaimer in 6060 the documentation and/or other materials provided with the 6061 distribution. 6063 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6064 names of specific contributors, may be used to endorse or promote 6065 products derived from this software without specific prior written 6066 permission. 6068 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6069 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6070 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6071 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6072 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6073 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6074 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6075 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6076 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6077 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6078 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6080 BEGIN 6081 6083 6091 6094 6096 6098 6101 6102 6103 NNDN (NNDN's not domain name) (CSV) Object 6104 6105 6107 6110 6113 6114 6115 6116 6117 6118 6119 6120 6121 6122 6125 6128 6129 6130 6131 6132 6133 6134 6135 6136 6138 6139 6142 6143 6146 6147 6151 6152 6155 6156 6157 6158 6159 6161 6162 6163 6165 6166 6169 6172 6173 END 6175 9.15. Policy Object 6177 Copyright (c) 2019 IETF Trust and the persons identified as authors 6178 of the code. All rights reserved. 6180 Redistribution and use in source and binary forms, with or without 6181 modification, are permitted provided that the following conditions 6182 are met: 6184 o Redistributions of source code must retain the above copyright 6185 notice, this list of conditions and the following disclaimer. 6187 o Redistributions in binary form must reproduce the above copyright 6188 notice, this list of conditions and the following disclaimer in 6189 the documentation and/or other materials provided with the 6190 distribution. 6192 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6193 names of specific contributors, may be used to endorse or promote 6194 products derived from this software without specific prior written 6195 permission. 6197 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6198 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6199 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6200 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6201 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6202 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6203 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6204 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6205 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6206 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6207 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6209 BEGIN 6210 6211 6217 6218 6219 Registry Data Escrow Policy schema 6220 6221 6223 6224 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 END 6238 9.16. Header Object 6240 Copyright (c) 2019 IETF Trust and the persons identified as authors 6241 of the code. All rights reserved. 6243 Redistribution and use in source and binary forms, with or without 6244 modification, are permitted provided that the following conditions 6245 are met: 6247 o Redistributions of source code must retain the above copyright 6248 notice, this list of conditions and the following disclaimer. 6250 o Redistributions in binary form must reproduce the above copyright 6251 notice, this list of conditions and the following disclaimer in 6252 the documentation and/or other materials provided with the 6253 distribution. 6255 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6256 names of specific contributors, may be used to endorse or promote 6257 products derived from this software without specific prior written 6258 permission. 6260 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6261 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6262 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6263 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6264 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6265 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6266 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6267 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6268 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6269 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6270 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6272 BEGIN 6273 6274 6281 6282 6284 6285 6286 Data Escrow Deposit Header schema 6287 6288 6290 6291 6294 6295 6296 6297 6298 6299 6300 6302 6304 6306 6307 6308 6310 6311 6312 6313 6314 6315 6316 6317 6319 6320 6321 6322 6323 6324 6325 6326 6327 6329 6330 END 6332 10. Internationalization Considerations 6334 Data Escrow deposits are represented in XML, which provides native 6335 support for encoding information using the Unicode character set and 6336 its more compact representations including UTF-8. Conformant XML 6337 processors recognize both UTF-8 and UTF-16. Though XML includes 6338 provisions to identify and use other character encodings through use 6339 of an "encoding" attribute in an declaration, use of UTF-8 is 6340 RECOMMENDED. 6342 11. IANA Considerations 6344 This document uses URNs to describe XML namespaces and XML schemas 6345 conforming to a registry mechanism described in [RFC3688]. Fourteen 6346 URI assignments have been registered by the IANA. 6348 Registration request for the RDE CSV namespace: 6350 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6352 Registrant Contact: See the "Author's Address" section of this 6353 document. 6355 XML: None. Namespace URIs do not represent an XML specification. 6357 Registration request for the RDE CSV XML schema: 6359 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6361 Registrant Contact: See the "Author's Address" section of this 6362 document. 6364 See the "Formal Syntax" section of this document. 6366 Registration request for the RDE domain namespace: 6368 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6370 Registrant Contact: See the "Author's Address" section of this 6371 document. 6373 XML: None. Namespace URIs do not represent an XML specification. 6375 Registration request for the RDE domain XML schema: 6377 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6379 Registrant Contact: See the "Author's Address" section of this 6380 document. 6382 See the "Formal Syntax" section of this document. 6384 Registration request for the CSV domain namespace: 6386 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6388 Registrant Contact: See the "Author's Address" section of this 6389 document. 6391 XML: None. Namespace URIs do not represent an XML specification. 6393 Registration request for the CSV domain XML schema: 6395 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6397 Registrant Contact: See the "Author's Address" section of this 6398 document. 6400 See the "Formal Syntax" section of this document. 6402 Registration request for the RDE host namespace: 6404 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6406 Registrant Contact: See the "Author's Address" section of this 6407 document. 6409 XML: None. Namespace URIs do not represent an XML specification. 6411 Registration request for the RDE host XML schema: 6413 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6415 Registrant Contact: See the "Author's Address" section of this 6416 document. 6418 See the "Formal Syntax" section of this document. 6420 Registration request for the CSV host namespace: 6422 URI: urn:ietf:params:xml:ns:csvHost-1.0 6424 Registrant Contact: See the "Author's Address" section of this 6425 document. 6427 XML: None. Namespace URIs do not represent an XML specification. 6429 Registration request for the CSV host XML schema: 6431 URI: urn:ietf:params:xml:schema:csvHost-1.0 6433 Registrant Contact: See the "Author's Address" section of this 6434 document. 6436 See the "Formal Syntax" section of this document. 6438 Registration request for the RDE contact namespace: 6440 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6442 Registrant Contact: See the "Author's Address" section of this 6443 document. 6445 XML: None. Namespace URIs do not represent an XML specification. 6447 Registration request for the RDE contact XML schema: 6449 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6450 Registrant Contact: See the "Author's Address" section of this 6451 document. 6453 See the "Formal Syntax" section of this document. 6455 Registration request for the CSV contact namespace: 6457 URI: urn:ietf:params:xml:ns:csvContact-1.0 6459 Registrant Contact: See the "Author's Address" section of this 6460 document. 6462 XML: None. Namespace URIs do not represent an XML specification. 6464 Registration request for the CSV contact XML schema: 6466 URI: urn:ietf:params:xml:schema:csvContact-1.0 6468 Registrant Contact: See the "Author's Address" section of this 6469 document. 6471 See the "Formal Syntax" section of this document. 6473 Registration request for the RDE registrar namespace: 6475 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6477 Registrant Contact: See the "Author's Address" section of this 6478 document. 6480 XML: None. Namespace URIs do not represent an XML specification. 6482 Registration request for the RDE registrar XML schema: 6484 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6486 Registrant Contact: See the "Author's Address" section of this 6487 document. 6489 See the "Formal Syntax" section of this document. 6491 Registration request for the CSV registrar namespace: 6493 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6495 Registrant Contact: See the "Author's Address" section of this 6496 document. 6498 XML: None. Namespace URIs do not represent an XML specification. 6500 Registration request for the CSV registrar XML schema: 6502 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6504 Registrant Contact: See the "Author's Address" section of this 6505 document. 6507 See the "Formal Syntax" section of this document. 6509 Registration request for the RDE IDN namespace: 6511 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6513 Registrant Contact: See the "Author's Address" section of this 6514 document. 6516 XML: None. Namespace URIs do not represent an XML specification. 6518 Registration request for the RDE IDN XML schema: 6520 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6522 Registrant Contact: See the "Author's Address" section of this 6523 document. 6525 See the "Formal Syntax" section of this document. 6527 Registration request for the CSV IDN namespace: 6529 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6531 Registrant Contact: See the "Author's Address" section of this 6532 document. 6534 XML: None. Namespace URIs do not represent an XML specification. 6536 Registration request for the CSV IDN XML schema: 6538 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6540 Registrant Contact: See the "Author's Address" section of this 6541 document. 6543 See the "Formal Syntax" section of this document. 6545 Registration request for the RDE NNDN namespace: 6547 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6549 Registrant Contact: See the "Author's Address" section of this 6550 document. 6552 XML: None. Namespace URIs do not represent an XML specification. 6554 Registration request for the RDE NNDN XML schema: 6556 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6558 Registrant Contact: See the "Author's Address" section of this 6559 document. 6561 See the "Formal Syntax" section of this document. 6563 Registration request for the CSV NNDN namespace: 6565 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6567 Registrant Contact: See the "Author's Address" section of this 6568 document. 6570 XML: None. Namespace URIs do not represent an XML specification. 6572 Registration request for the CSV NNDN XML schema: 6574 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6576 Registrant Contact: See the "Author's Address" section of this 6577 document. 6579 See the "Formal Syntax" section of this document. 6581 Registration request for the RDE EPP parameters namespace: 6583 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6585 Registrant Contact: See the "Author's Address" section of this 6586 document. 6588 XML: None. Namespace URIs do not represent an XML specification. 6590 Registration request for the RDE EPP parameters XML schema: 6592 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6593 Registrant Contact: See the "Author's Address" section of this 6594 document. 6596 See the "Formal Syntax" section of this document. 6598 12. Implementation Status 6600 Note to RFC Editor: Please remove this section and the reference to 6601 RFC 7942 [RFC7942] before publication. 6603 This section records the status of known implementations of the 6604 protocol defined by this specification at the time of posting of this 6605 Internet-Draft, and is based on a proposal described in RFC 7942 6606 [RFC7942]. The description of implementations in this section is 6607 intended to assist the IETF in its decision processes in progressing 6608 drafts to RFCs. Please note that the listing of any individual 6609 implementation here does not imply endorsement by the IETF. 6610 Furthermore, no effort has been spent to verify the information 6611 presented here that was supplied by IETF contributors. This is not 6612 intended as, and must not be construed to be, a catalog of available 6613 implementations or their features. Readers are advised to note that 6614 other implementations may exist. 6616 According to RFC 7942 [RFC7942], "this will allow reviewers and 6617 working groups to assign due consideration to documents that have the 6618 benefit of running code, which may serve as evidence of valuable 6619 experimentation and feedback that have made the implemented protocols 6620 more mature. It is up to the individual working groups to use this 6621 information as they see fit". 6623 12.1. Implementation in the gTLD space 6625 Organization: ICANN 6627 Name: ICANN Registry Agreement 6629 Description: the ICANN Base Registry Agreement requires Registries, 6630 Data Escrow Agents, and ICANN to implement this specification. ICANN 6631 receives daily notifications from Data Escrow Agents confirming that 6632 more than 1,200 gTLDs are sending deposits that comply with this 6633 specification. ICANN receives on a weekly basis per gTLD, from more 6634 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6635 also complies with this specification. In addition, ICANN is aware 6636 of Registry Service Provider transitions using data files that 6637 conform to this specification. 6639 Level of maturity: production. 6641 Coverage: all aspects of this specification are implemented. 6643 Version compatibility: versions 03 - 08 are known to be implemented. 6645 Contact: gustavo.lozano@icann.org 6647 URL: https://www.icann.org/resources/pages/registries/registries- 6648 agreements-en 6650 13. Security Considerations 6652 This specification does not define the security mechanisms to be used 6653 in the transmission of the data escrow deposits, since it only 6654 specifies the minimum necessary to enable the rebuilding of a 6655 Registry from deposits without intervention from the original 6656 Registry. 6658 Depending on local policies, some elements or most likely, the whole 6659 deposit will be considered confidential. As such the Registry 6660 transmitting the data to the Escrow Agent SHOULD take all the 6661 necessary precautions like encrypting the data itself and/or the 6662 transport channel to avoid inadvertent disclosure of private data. 6664 It is also of the utmost importance the authentication of the parties 6665 passing data escrow deposit files. The Escrow Agent SHOULD properly 6666 authenticate the identity of the Registry before accepting data 6667 escrow deposits. In a similar manner, the Registry SHOULD 6668 authenticate the identity of the Escrow Agent before submitting any 6669 data. 6671 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6672 checking mechanisms to ensure the data transmitted is what the source 6673 intended. Validation of the contents by the Escrow Agent is 6674 RECOMMENDED to ensure not only the file was transmitted correctly 6675 from the Registry, but also the contents are also "meaningful". 6677 14. Privacy Considerations 6679 This specification defines a format that may be used to escrow 6680 personal data. The process of data escrow is governed by a legal 6681 document agreed by the parties, and such legal document must regulate 6682 the particularities regarding the protection of personal data. 6684 15. Acknowledgments 6686 Parts of this document are based on EPP [RFC5730] and related RFCs by 6687 Scott Hollenbeck. 6689 Special suggestions that have been incorporated into this document 6690 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6691 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6692 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6693 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6694 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6695 Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. 6697 Shoji Noguchi and Francisco Arias participated as co-authors until 6698 version 05 providing invaluable support for this document. 6700 16. Change History 6702 [[RFC Editor: Please remove this section.]] 6704 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6705 dnrd-objects-mapping-00 6707 1. Added definition for child elements under the element. 6709 2. Added definition for child elements under the element. 6711 3. Added definition for child elements under the element. 6713 4. Rewrote the IDN Variants Handling section to use the variant 6714 states as described in ICANN's Study of Issues Related to the 6715 Management of IDN Variant TLDs. 6717 5. Renamed to in the . 6719 6. Renamed to in the element. 6721 7. Renamed to in the element. 6723 8. Added element under element. 6725 9. Fixed some typographical errors and omissions. 6727 16.2. Changes from 00 to 01 6729 1. Specify OPTIONAL elements in the draft. 6731 2. Added NNDN object to support list of reserved names and different 6732 IDN variants models. 6734 3. Removed subordinated host element from the domain object. 6736 4. Added eppParams object. 6738 5. Added variantGenerator element to the domain object. 6740 6. Added lgr to the IDN table object. 6742 16.3. Changes from 01 to 02 6744 1. Updates to the all objects based on feedback from the list. 6746 2. Start of XML and CSV drafts merge. 6748 3. Added header object. 6750 4. Added report object. 6752 5. Added notification object. 6754 6. Added Data Escrow Agent Extended Verification Process section. 6756 7. Added Notifications from Registries to Third Parties. 6758 8. Added Notifications from Data Escrow Agents to Third Parties. 6760 9. Added FULL, DIFF deposit examples using the XML model only. 6762 16.4. Changes from 02 to 03 6764 1. Remove authinfo from the XML Schema. 6766 2. Resend attribute is now an element 6768 3. Scope attribute added to policy object. 6770 16.5. Changes from 03 to 04 6772 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6773 arias-noguchi-dnrd-objects-mapping-02. 6775 2. Changed the cksum attribute of to use CRC32 and 6776 changed all of the sample cksum values to use CRC32, based on 6777 feedback from David Kipling. 6779 3. Changed the optional element to be an optional 6780 "sep" attribute value of the element with a default 6781 value of "," based on feedback from David Kipling. 6783 4. Added support for the optional "parent" attribute for the to the 6784 CSV fields to indicate a field as a reference to a parent 6785 object, based on feedback from David Kipling. 6787 5. Added support for the CSV model for the NNDN. 6789 6. Added support to delete hosts based on roid. 6791 7. Added mirrored state to NNDN 6793 8. Minor fixes to XML XSDs. 6795 9. The Report and Notification objects were moved to draft-lozano- 6796 icann-registry-interfaces 6798 10. The section Data escrow notifications was moved to draft-lozano- 6799 icann-registry-interfaces 6801 11. Removed references to the , , and 6802 from the "hostStatuses" and "hostAddresses" CSV 6803 files. 6805 12. Removed references to the , , and 6806 from the "contactStatuses" CSV file. 6808 13. Removed references to the , , and 6809 from the "domainContacts", "domainStatuses", 6810 and "domainNameServers" CSV files. 6812 14. Changed to . 6814 15. Replaced use of to new field 6815 in the "domain", "idnLanguage", and "NNDN" CSV files. 6817 16. Replaced use of with in the 6818 "host" element. 6820 17. Changed the foreign key of the hosts to use 6821 instead of and removed use of in 6822 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6823 files. 6825 18. Added use of the MUST keyword for CSV fields that are required 6826 to be supported in an EPP based system. 6828 19. Removed use of the field element for the 6829 "registrar" CSV file. 6831 20. Added definition of field element. 6833 16.6. Changes from 04 to 05 6835 1. Updated the examples of the full and differential deposits using 6836 the CSV and XML model. 6838 2. Made optional for the "domainTransfer" CSV file 6839 to match the XML definition. 6841 3. Made optional for the "domain" CSV file 6842 to match the XML definition. 6844 4. Made optional for the "domain" and "contact" CSV 6845 files to match the XML definition. 6847 5. Change from IDREF to idType. 6849 6. Minor editorial changes. 6851 16.7. Changes from 05 to 06 6853 1. Revised the differential and incremental deposits for the CSV 6854 format to use cascade update / replace and delete from the parent 6855 object to be consistent with the XML format. 6857 2. Revised the structure of the CSV format sections to utilize sub- 6858 sections instead of a list for the CSV file definitions. 6860 3. Added the "CSV Parent Child Relationship" section to describe the 6861 concept of parent child relationships across CSV file 6862 definitions. 6864 4. Added the "domainNameServersAddresses" CSV File Definition 6865 section to support the domain host attributes model of [RFC5731]. 6867 5. Made the required fields in the CSV format consistent with the 6868 XML format. The CSV fields updated to be required include: 6869 , , , 6870 , , , 6871 , , , 6872 , , , 6873 , , 6874 , , , 6875 , , 6876 , and . 6878 6. Revised the CSV examples to use a more realistic set of records. 6880 16.8. Changes from 06 to 07 6882 1. Created "repositoryTypeGroup" group element in the rdeHeader 6883 including the , and 6884 elements. 6886 2. Added the optional "rcdn" and "registrarId" attributes to the 6887 element 6889 16.9. Changes from 07 to 08 6891 1. The following registrar elements were made optional to support 6892 greater flexibility for the implementation of policies: status, 6893 postalInfo, email and crDate. 6895 2. The following domain name elements were made optional to support 6896 greater flexibility for the implementation of policies: crRr. 6898 16.10. Changes from 08 to 09 6900 1. Implementation Status section was added 6902 16.11. Changes from 09 to 10 6904 1. Editorial changes in section Section 5.1.2.1.6. 6906 2. Added MAY clause when the DS Data Interface is used in section 6907 Section 5.1.2.1.6. 6909 16.12. Changes from 10 to REGEXT 00 6911 1. Internet Draft (I-D) adopted by the REGEXT WG. 6913 16.13. Changes REGEXT 00 to REGEXT 01 6915 1. Added the element to the 6916 "repositoryTypeGroup" group element in the rdeHeader. 6918 2. Privacy consideration section was added 6920 3. Updates on section 8 6922 16.14. Changes REGEXT 01 to REGEXT 02 6924 1. Added a choice between the use of the or 6925 fields in the CSV "domain", "host", and 6926 "contact" definitions. 6928 2. Added a choice between the use of the or 6929 fields in the CSV "domainNameServers" 6930 definition. 6932 3. Changed "of client" to "of the client" throughout the document. 6934 4. Modified all references of 'The attribute isRequired MUST equal 6935 "true".' to 'The attribute "isRequired" MUST equal "true".' 6937 5. Combined the and 6938 fields in a single required list for the CSV "domainContacts" 6939 definition. 6941 6. Combined the , , and 6942 fields in a single required list for the 6943 CSV "domainStatuses" definition. 6945 7. Moved the the fields to the MAY 6946 list for the CSV "domain", "host", and "contact" definitions. 6948 8. Made the order of the , , 6949 , and fields more consistent in the 6950 CSV lists. 6952 9. Fixed an error in the order of the object example. 6954 10. Changed to be optional to match being 6955 optional in the XML model, by having it use type 6956 rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and 6957 ensuring that is included in the MAY field 6958 lists and not the MUST field lists. 6960 11. Made optional for the "domain" CSV definition 6961 to be consistent with the XML model, by removing the sentence 6962 'The attribute "isRequired" MUST equal "true".' from the 6963 description and moving the field to the MAY field list. 6965 12. Made optional for the "domain" and "contact" 6966 CSV definitions to be consistent with the XML model, by moving 6967 the field to the MAY field list. 6969 13. Made optional to be consistent with the XML 6970 model, by having it use type rdeCsv:fClIDType instead of 6971 rdeCsv:fClIDRequiredType. 6973 14. Made required to be consistent with the XML 6974 model, by having it use type rdeCsv:fClIDRequiredType instead of 6975 rdeCsv:fClIDType. 6977 15. Made the field in the "host", "contact", 6978 and "registrar" CSV definitions required explicitly by removing 6979 'and isRequired="true"' and adding the sentence 'The attribute 6980 isRequired MUST equal "true".', when it is chosen as the primary 6981 field. 6983 16. Removed extra '/>.' at the end of the field 6984 description in the "hostStatuses" CSV definition. 6986 17. Made the field optional to be consistent 6987 with the XML model, by having csvRegistrar:fStatusType extend 6988 rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. 6990 18. Made the field for the "registrar" CSV 6991 definition explicitly optional to be consistent with the XML 6992 model, by adding the sentence 'The attribute isRequired MUST 6993 equal "false".' to the field description and including the 6994 definition of isRequired="false" in the "registrar" CSV 6995 definition examples. 6997 19. Added the choice between the use of the and 6998 fields in the deletes "registrar" CSV 6999 definition to be consistent with the "registrar" CSV definition. 7001 20. Made the and elements optional for the host and 7002 contact objects in the XML model to be consistent with the 7003 domain object. 7005 16.15. Changes REGEXT 02 to REGEXT 03 7007 1. Added the optional element contentTag in the header object. 7009 2. Editorial updates. 7011 16.16. Changes REGEXT 03 to REGEXT 04 7013 1. Note: Updates from version REGEXT 03 to REGEXT 04 attend the 7014 feedback provided during the document shepherd review. 7016 2. Editorial updates. 7018 3. Examples now use domain names from the .example TLD. 7020 4. The introduction was enhanced by explaining the need for data 7021 escrow and the proposed solution. 7023 5. Explanation regarding NNDN was improved. 7025 6. Explanation regarding the CSV and XML model was improved. 7027 7. Section 4.5 updated to make the text clearer. 7029 8. draft-arias-noguchi-registry-data-escrow is now referenced from 7030 the I-D repository. 7032 9. The XML prefix "rdeDomain" is now consistently used. 7034 10. The prevID attribute was removed from the examples of full 7035 deposits. 7037 11. The examples were updated to use present dates. 7039 17. Example of a full deposit using the XML model 7041 Example of a full deposit using the XML model: 7043 7044 7060 2019-10-17T00:00:00Z 7061 7062 1.0 7063 urn:ietf:params:xml:ns:rdeHeader-1.0 7064 7065 urn:ietf:params:xml:ns:rdeContact-1.0 7066 7067 urn:ietf:params:xml:ns:rdeHost-1.0 7068 7069 urn:ietf:params:xml:ns:rdeDomain-1.0 7070 7071 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7072 7073 urn:ietf:params:xml:ns:rdeIDN-1.0 7074 7075 urn:ietf:params:xml:ns:rdeNNDN-1.0 7076 7077 urn:ietf:params:xml:ns:rdeEppParams-1.0 7078 7079 7081 7082 7083 7084 7085 test 7086 2 7088 7089 1 7091 7092 1 7094 7095 1 7097 7098 1 7100 7101 1 7103 7104 1 7106 7107 7109 7110 7111 example1.example 7112 Dexample1-TEST 7113 7114 jd1234 7115 sh8013 7116 sh8013 7117 7118 ns1.example.com 7119 ns1.example1.example 7120 7121 RegistrarX 7122 RegistrarX 7123 1999-04-03T22:00:00.0Z 7124 2015-04-03T22:00:00.0Z 7125 7127 7128 7129 example2.example 7130 Dexample2-TEST 7131 7132 7133 jd1234 7134 sh8013 7135 sh8013 7136 RegistrarX 7137 RegistrarX 7138 1999-04-03T22:00:00.0Z 7139 2015-04-03T22:00:00.0Z 7140 7142 7143 7144 ns1.example1.example 7145 Hns1_example_test-TEST 7146 7147 7148 192.0.2.2 7149 192.0.2.29 7150 1080:0:0:0:8:800:200C:417A 7151 7152 RegistrarX 7153 RegistrarX 7154 1999-05-08T12:10:00.0Z 7155 RegistrarX 7156 2009-10-03T09:34:00.0Z 7157 7159 7160 7161 sh8013 7162 Csh8013-TEST 7163 7164 7165 7166 John Doe 7167 Example Inc. 7168 7169 123 Example Dr. 7170 Suite 100 7171 Dulles 7172 VA 7173 20166-6503 7174 US 7175 7176 7177 +1.7035555555 7178 7179 +1.7035555556 7180 7181 jdoe@example.example 7182 7183 RegistrarX 7184 RegistrarX 7185 7186 2009-09-13T08:01:00.0Z 7187 7188 RegistrarX 7189 7190 2009-11-26T09:10:00.0Z 7191 7192 2009-12-03T09:05:00.0Z 7193 7194 7195 7196 7197 7198 7200 7201 7202 RegistrarX 7203 Registrar X 7204 123 7205 ok 7206 7207 7208 123 Example Dr. 7209 7210 Suite 100 7211 7212 Dulles 7213 VA 7214 20166-6503 7215 US 7216 7218 7219 +1.7035555555 7220 7221 +1.7035555556 7222 7223 jdoe@example.example 7224 7225 http://www.example.example 7226 7227 7228 whois.example.example 7229 7230 http://whois.example.example 7231 7232 7233 2005-04-23T11:49:00.0Z 7234 7235 2009-02-17T17:51:00.0Z 7236 7237 7239 7240 7241 7242 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 7243 7244 7245 http://registro.br/dominio/regras.html 7246 7247 7249 7250 7251 xn--exampl-gva.example 7252 pt-BR 7253 example1.example 7254 withheld 7255 2005-04-23T11:49:00.0Z 7256 7258 7259 7260 1.0 7261 en 7262 7263 urn:ietf:params:xml:ns:domain-1.0 7264 7265 7266 urn:ietf:params:xml:ns:contact-1.0 7267 7268 7269 urn:ietf:params:xml:ns:host-1.0 7270 7271 7272 urn:ietf:params:xml:ns:rgp-1.0 7273 7274 urn:ietf:params:xml:ns:secDNS-1.1 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7297 7298 7300 18. Example of differential deposit using the XML model 7302 Example of a differential deposit using the XML model: 7304 7305 7320 2019-10-17T00:00:00Z 7321 7322 1.0 7323 urn:ietf:params:xml:ns:rdeHeader-1.0 7324 7325 urn:ietf:params:xml:ns:rdeContact-1.0 7326 7327 urn:ietf:params:xml:ns:rdeHost-1.0 7328 7329 urn:ietf:params:xml:ns:rdeDomain-1.0 7330 7331 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7332 7333 urn:ietf:params:xml:ns:rdeIDN-1.0 7334 7335 urn:ietf:params:xml:ns:rdeNNDN-1.0 7336 7337 urn:ietf:params:xml:ns:rdeEppParams-1.0 7338 7339 7341 7342 7343 7344 example2.example 7345 7346 7348 7349 7350 7351 7352 test 7353 1 7355 7356 1 7358 7359 1 7361 7363 1 7365 7366 1 7368 7369 1 7371 7372 1 7374 7375 7376 7377 7379 19. Example of a full deposit using the CSV model 7381 Example of a full deposit using the CSV model: 7383 7384 7398 2019-10-18T00:00:00Z 7399 7400 1.0 7401 urn:ietf:params:xml:ns:csvDomain-1.0 7402 urn:ietf:params:xml:ns:csvHost-1.0 7403 urn:ietf:params:xml:ns:csvContact-1.0 7404 urn:ietf:params:xml:ns:csvRegistrar-1.0 7405 urn:ietf:params:xml:ns:csvIDN-1.0 7406 urn:ietf:params:xml:ns:csvNNDN-1.0 7407 urn:ietf:params:xml:ns:rdeEppParams-1.0 7408 7409 7410 7411 test 7412 7413 4 7414 7415 7416 6 7417 7418 7419 9 7420 7421 7422 3 7423 7424 7425 2 7426 7427 7428 2 7429 7430 7431 1 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7454 domain-YYYYMMDD.csv 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7467 domainContacts-YYYYMMDD.csv 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7482 domainStatuses-YYYYMMDD.csv 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7494 domainNameServers-name-YYYYMMDD.csv 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7506 domainNameServers-roid-YYYYMMDD.csv 7508 7509 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7523 dnssec-ds-YYYYMMDD.csv 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7539 dnssec-key-YYYYMMDD.csv 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7558 domainTransfer-YYYYMMDD.csv 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7580 host-YYYYMMDD.csv 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7594 hostStatuses-YYYYMMDD.csv 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7607 hostAddresses-YYYYMMDD.csv 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7633 contact-YYYYMMDD.csv 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7647 contactStatuses-YYYYMMDD.csv 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7668 contactPostal-YYYYMMDD.csv 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7686 contactTransfer-YYYYMMDD.csv 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7707 contactDisclose-YYYYMMDD.csv 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7739 registrar-YYYYMMDD.csv 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7753 idnLanguage-YYYYMMDD.csv 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7771 NNDN-YYYYMMDD.csv 7772 7773 7774 7775 7776 7777 1.0 7778 en 7779 urn:ietf:params:xml:ns:domain-1.0 7780 7781 urn:ietf:params:xml:ns:host-1.0 7782 7783 urn:ietf:params:xml:ns:contact-1.0 7784 7785 7786 urn:ietf:params:xml:ns:secDNS-1.1 7787 7788 urn:ietf:params:xml:ns:rgp-1.0 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7815 20. Example of differential deposit using the CSV model 7817 Example of a differential deposit using the CSV model: 7819 7820 7834 2019-10-18T00:00:00Z 7835 7836 1.0 7837 urn:ietf:params:xml:ns:csvDomain-1.0 7838 urn:ietf:params:xml:ns:csvHost-1.0 7839 urn:ietf:params:xml:ns:csvContact-1.0 7840 urn:ietf:params:xml:ns:csvRegistrar-1.0 7841 urn:ietf:params:xml:ns:csvIDN-1.0 7842 7843 7844 7845 7846 7847 7848 7849 7850 7852 domain-delete-YYYYMMDD.csv 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7865 host-delete-YYYYMMDD.csv 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7878 contact-delete-YYYYMMDD.csv 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7891 registrar-delete-YYYYMMDD.csv 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7905 idnLanguage-delete-YYYYMMDD.csv 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7918 NNDN-delete-YYYYMMDD.csv 7919 7920 7921 7922 7923 7924 7925 7926 test 7927 7928 2 7929 7930 7931 2 7932 7933 7934 3 7935 7936 7937 1 7938 7939 7940 1 7941 7942 7943 1 7944 7945 7946 1 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7969 domain-YYYYMMDD.csv 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7982 domainContacts-YYYYMMDD.csv 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7997 domainStatuses-YYYYMMDD.csv 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8009 domainNameServers-name-YYYYMMDD.csv 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8021 domainNameServers-roid-YYYYMMDD.csv 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8037 dnssec-ds-YYYYMMDD.csv 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8053 dnssec-key-YYYYMMDD.csv 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8072 domainTransfer-YYYYMMDD.csv 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8094 host-YYYYMMDD.csv 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8108 hostStatuses-YYYYMMDD.csv 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8121 hostAddresses-YYYYMMDD.csv 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8147 contact-YYYYMMDD.csv 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8161 contactStatuses-YYYYMMDD.csv 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8182 contactPostal-YYYYMMDD.csv 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8194 8195 8196 8197 8198 8200 contactTransfer-YYYYMMDD.csv 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8221 contactDisclose-YYYYMMDD.csv 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8253 registrar-YYYYMMDD.csv 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264 8265 8267 idnLanguage-YYYYMMDD.csv 8268 8269 8270 8271 8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8285 NNDN-YYYYMMDD.csv 8286 8287 8288 8289 8290 8291 1.0 8292 en 8293 urn:ietf:params:xml:ns:domain-1.0 8294 8295 urn:ietf:params:xml:ns:host-1.0 8296 8297 urn:ietf:params:xml:ns:contact-1.0 8298 8299 8300 urn:ietf:params:xml:ns:secDNS-1.1 8301 8302 urn:ietf:params:xml:ns:rgp-1.0 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 8324 8326 8327 8328 8330 21. References 8332 21.1. Normative References 8334 [I-D.ietf-regext-data-escrow] 8335 Lozano, G., "Registry Data Escrow Specification", draft- 8336 ietf-regext-data-escrow-02 (work in progress), November 8337 2019. 8339 [ISO-3166-1] 8340 3166, I. S., "Codes for the representation of names of 8341 countries and their subdivisions -- Part 1: Country 8342 codes", ISO Standard 3166, November 2006. 8344 [ITU-E164] 8345 International Telecommunication Union, "The international 8346 public telecommunication numbering plan", ITU-T 8347 Recommendation E.164, February 2005. 8349 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8350 Requirement Levels", BCP 14, RFC 2119, 8351 DOI 10.17487/RFC2119, March 1997, 8352 . 8354 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8355 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8356 . 8358 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8359 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8360 DOI 10.17487/RFC3915, September 2004, 8361 . 8363 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8364 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8365 . 8367 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8368 Domain Name Mapping", STD 69, RFC 5731, 8369 DOI 10.17487/RFC5731, August 2009, 8370 . 8372 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8373 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8374 August 2009, . 8376 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8377 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8378 August 2009, . 8380 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8381 Security Extensions Mapping for the Extensible 8382 Provisioning Protocol (EPP)", RFC 5910, 8383 DOI 10.17487/RFC5910, May 2010, 8384 . 8386 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 8387 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 8388 May 2017, . 8390 21.2. Informative References 8392 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8393 DOI 10.17487/RFC0791, September 1981, 8394 . 8396 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8397 DOI 10.17487/RFC3688, January 2004, 8398 . 8400 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8401 DOI 10.17487/RFC3912, September 2004, 8402 . 8404 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8405 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8406 2006, . 8408 [RFC5891] Klensin, J., "Internationalized Domain Names in 8409 Applications (IDNA): Protocol", RFC 5891, 8410 DOI 10.17487/RFC5891, August 2010, 8411 . 8413 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8414 Code: The Implementation Status Section", BCP 205, 8415 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8416 . 8418 [variantTLDsReport] 8419 Internet Corporation for Assigned Names and Numbers 8420 (ICANN), "A Study of Issues Related to the Management of 8421 IDN Variant TLDs", February 2012, 8422 . 8425 Authors' Addresses 8427 Gustavo Lozano 8428 Internet Corporation for Assigned Names and Numbers 8429 12025 Waterfront Drive, Suite 300 8430 Los Angeles 90292 8431 United States of America 8433 Phone: +1.310.823.9358 8434 Email: gustavo.lozano@icann.org 8436 James Gould 8437 VeriSign, Inc. 8438 12061 Bluemont Way 8439 Reston 20190 8440 United States of America 8442 Email: jgould@verisign.com 8444 Chethan Thippeswamy 8445 VeriSign, Inc. 8446 12061 Bluemont Way 8447 Reston 20190 8448 United States of America 8450 Email: cthippeswamy@verisign.com