idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-03.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 : ---------------------------------------------------------------------------- == There are 9 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (Nov 26, 2019) is 1613 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) -- Looks like a reference, but probably isn't: '1' on line 8356 -- 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 (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track J. Gould 5 Expires: May 29, 2020 C. Thippeswamy 6 VeriSign 7 Nov 26, 2019 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-03 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 May 29, 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 55 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5 56 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 5 57 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6 58 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 59 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6 60 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6 61 4.6. CSV Parent Child Relationship . . . . . . . . . . . . . . 6 62 4.7. CSV elements . . . . . . . . . . . . . . . . . . . . . . 7 63 4.8. Internationalized and Localized Elements . . . . . . . . 12 64 5. Object Description . . . . . . . . . . . . . . . . . . . . . 14 65 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 14 66 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 33 67 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 43 68 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 61 69 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 69 70 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 73 71 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 78 72 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 80 73 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 80 74 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 83 75 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 76 8. Data escrow agent extended verification process . . . . . . . 84 77 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 85 78 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 85 79 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 95 80 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98 81 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 103 82 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 105 83 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 108 84 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 111 85 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 117 86 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 121 87 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 125 88 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 127 89 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 129 90 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 131 91 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 133 92 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 136 93 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 137 94 10. Internationalization Considerations . . . . . . . . . . . . . 139 95 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 139 96 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 145 97 12.1. Implementation in the gTLD space . . . . . . . . . . . . 145 99 13. Security Considerations . . . . . . . . . . . . . . . . . . . 146 100 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 146 101 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 146 102 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 147 103 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 104 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 147 105 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 147 106 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 148 107 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 148 108 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 148 109 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 150 110 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 150 111 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 151 112 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 151 113 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 151 114 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 151 115 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 151 116 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 151 117 16.14. Changes REGEXT 01 to REGEXT 02 . . . . . . . . . . . . . 151 118 16.15. Changes REGEXT 02 to REGEXT 03 . . . . . . . . . . . . . 153 119 17. Example of a full deposit using the XML model . . . . . . . . 153 120 18. Example of differential deposit using the XML model . . . . . 159 121 19. Example of a full deposit using the CSV model . . . . . . . . 160 122 20. Example of differential deposit using the CSV model . . . . . 169 123 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 180 124 21.1. Normative References . . . . . . . . . . . . . . . . . . 180 125 21.2. Informative References . . . . . . . . . . . . . . . . . 181 126 21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 182 127 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 182 129 1. Introduction 131 This document defines the data escrow structure of the standard set 132 of objects for a Domain Name Registry which include: 134 o Domain: Internet domain names that are typically provisioned in a 135 Domain Name Registry using the EPP domain name mapping [RFC5731]. 136 The attributes defined in the EPP domain name mapping [RFC5731] 137 are fully supported by this document. 139 o Host: Internet host names that are typically provisioned in a 140 Domain Name Registry using the EPP host mapping [RFC5732]. The 141 attributes defined in the EPP host mapping [RFC5732] are fully 142 supported by this document. 144 o Contact: Individual or organization social information provisioned 145 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 147 The attributes defined in the EPP contact mapping [RFC5733] are 148 fully supported by this document. 150 o Registrar: The organization that sponsors objects like domains, 151 hosts, and contacts in a Domain Name Registry. 153 o NNDN (NNDN's not domain name): A lightweight domain-like object 154 that is not linked to a Registrar. 156 This document defines the following pseudo-objects: 158 o IDN Table Reference: Internationalized Domain Names (IDN) included 159 in the Domain Object Data Escrow include references to the IDN 160 Table and Policy used in IDN registration. 162 o EPP parameters: Definition of the specific EPP parameters 163 supported by the Registry Operator. 165 o Header: Used to specify counters of objects in the database at a 166 certain point in time (watermark). 168 o Policy: Used to specify OPTIONAL elements from this specification 169 that are REQUIRED based on the business model of the registry. 171 2. Models 173 This document defines two different models that can be used to 174 deposit data escrow objects: 176 o XML: The XML model includes all the deposit information (meta-data 177 and data) in an XML document. The definition of the XML format is 178 fully defined in the XML schemas. As a convention, the objects 179 represented using the XML model are referenced using RDE and an 180 XML namespace that is prefixed with "rde". For example, the 181 Domain Name object represented using the XML model can be referred 182 to as the RDE Domain Name with the XML namespace including 183 rdeDomain (urn:ietf:params:xml:ns:rdeDomain-1.0). 185 o CSV: The CSV model uses XML to define the data escrow format of 186 the data contained in referenced Comma-Separated Values (CSV) 187 files. As a convention, the objects represented using the CSV 188 model is referenced using CSV and an XML namespace that is 189 prefixed with "csv". For example, the Domain Name object 190 represented using the CSV model can be referred to as the CSV 191 Domain Name with the XML namespace including csvDomain 192 (urn:ietf:params:xml:ns:csvDomain-1.0). 194 The data escrow deposit MAY contain a mix of both models but an 195 object MUST be escrowed only in one model. 197 3. Terminology 199 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 200 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 201 "OPTIONAL" in this document are to be interpreted as described in BCP 202 14 [RFC2119] [RFC8174] when, and only when, they appear in all 203 capitals, as shown here. 205 REGISTRY. In the context of this draft the definition will be 206 overloaded (from the definition in the base protocol) to indicate an 207 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 208 NAME. 210 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 211 or any other domain name at any level in the DNS tree for which a 212 Registry (either directly or through and affiliate company) provides 213 Registry Services for other organizations or individuals. For 214 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 216 REGISTRY SERVICES. Services offered by the Registry critical to the 217 following tasks: the provisioning of domain names on receipt of 218 requests and data from registrars; responding to registrar queries 219 for status information relating to the DNS servers for the RCDN; 220 dissemination of RCDN zone files; operation of the Registry DNS 221 servers; and responding to queries for contact and other information 222 concerning DNS registrations in the RCDN. Any other products or 223 services that only a Registry is capable of providing, by reason of 224 its designation as the Registry. Typical examples of Registry 225 Services are: DNS resolution for the RCDN, WHOIS and EPP. 227 ALLOCATED. A status of some label with respect to a zone, whereby 228 the label is associated administratively to some entity that has 229 requested the label. This term (and its cognates "allocation" and 230 "to allocate") may represents the first step on the way to delegation 231 in the DNS. 233 4. General Conventions 235 4.1. Date and Time 237 Numerous fields indicate "dates", such as the creation and expiry 238 dates for domain names. These fields SHALL contain timestamps 239 indicating the date and time in UTC as specified in [RFC3339], with 240 no offset from the zero meridian. 242 4.2. Country names 244 Country identifiers SHALL be represented using two character 245 identifiers as specified in [ISO-3166-1]. 247 4.3. Telephone numbers 249 Telephone numbers (both voice and facsimile) SHALL be formatted based 250 on structures defined in [ITU-E164]. Telephone numbers described in 251 this specification are character strings that MUST begin with a plus 252 sign ("+", ASCII value 0x002B), followed by a country code defined in 253 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 254 a sequence of digits representing the telephone number. 256 4.4. Checksum 258 Checksum of the CSV data escrow files MUST use CRC32, that is the 259 algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of 260 ITU-T recommendation V.42. 262 4.5. IP addresses 264 IP addresses syntax MUST conform to the text representation of either 265 of, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 266 Addressing Architecture [RFC4291], for IPv6 addresses. 268 4.6. CSV Parent Child Relationship 270 The CSV model represents a relational model, where the CSV files 271 represent relational tables, the fields of the CSV files represent 272 columns of the tables, and each line of the CSV file represents a 273 record. As in a relational model, the CSV files can have 274 relationships utilizing primary keys in the parent CSV file 275 definitions and foreign keys in the child CSV file definitions for a 276 1-to-many relationship. The primary keys are not explicitly defined, 277 but the foreign keys are using the boolean "parent" field attribute 278 in the child CSV file. The relationships between the CSV files are 279 used to support a cascade replace or cascade delete of records 280 starting from the parent record in differential and incremental 281 deposits. 283 The following is an example of the CSV file definitions for a Sample 284 object consisting of a parent "sample" CSV File Definition and a 285 child "sampleStatuses" CSV File Definition. The primary key for the 286 Sample object is the field that is used as the 287 foreign key in the "sampleStatuses" CSV File Definition by specifying 288 the "parent=true" attribute. If a Sample record is updated or 289 deleted in a differential or incremental deposit, it should cascade 290 replace the data using the records included in the child 291 "sampleStatuses" CSV File Definition or cascade delete the existing 292 records in the child "sampleStatuses" CSV File Definition, 293 respectively. 295 296 ... 297 298 299 300 301 302 303 304 305 306 307 308 309 310 312 sample-YYYYMMDD.csv 313 314 315 316 317 318 319 320 321 322 323 324 326 sampleStatuses-YYYYMMDD.csv 327 328 329 330 ... 331 333 4.7. CSV elements 334 4.7.1. element 336 To support a CSV model with the Registry Data Escrow Specification 337 [1], an element is defined for each object that substitutes for the 338 element and for the element, that contains 339 one or more elements. For example, the Domain Name 340 Object (Section 5.1) defines the element, that 341 substitutes for the element, and the 342 element, that substitutes for the 343 element. Both the element and the 344 elements contain one or more 345 elements. The element has the following child elements: 347 Ordered list of CSV fields used in the CSV files. 348 There is one or more child elements that substitute for the 349 abstract element. Each element defines the format 350 of the CSV field contained in the CSV files. The 351 elements support the "type" attribute that defines the XML simple 352 data type of the field element. The elements 353 support the "isRequired" attribute, with a default value of 354 "false", when set to "true" indicates that the field must be non- 355 empty in the CSV files and when set to "false" indicates that the 356 field MAY be empty in the CSV files. The "isRequired" attribute 357 MAY be specifically set for the field elements within the XML 358 schema and MAY be overridden when specifying the fields under the 359 element. The element supports an 360 OPTIONAL "parent" attribute that identifies the field as a 361 reference to a parent object, as defined in CSV Parent Child 362 Relationship (Section 4.6). For example, the field SHOULD set the 364 "parent" attribute to "true" to identify it as the parent domain 365 name of the domain status. 367 A list of one or more CSV files using the 368 child element. The child element 369 defines a reference to the CSV file name and has the following 370 optional attributes: 372 compression If the CSV file is compressed, the "compression" 373 attribute defines the compression format like "gzip" or "zip". 375 encoding Defines the encoding of the CSV file with the default 376 encoding of "UTF-8". 378 cksum Defines the checksum of the CSV file using CRC32, as 379 defined in Section 4.4. This attribute is used to validate 380 that the full CSV file exists and has not been tampered with. 382 The elements requires a "name" attribute that defines 383 the purpose of the CSV file with values like "domain", "host", 384 "contact". The supported "name" attribute values are defined for 385 each object type. The OPTIONAL "sep" attribute defines the CSV 386 separator character with the default separator character of ",". 388 The following is an example of the 389 element for domain name records where the is set 390 as required with isRequired="true". 392 393 ... 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 413 domain-YYYYMMDD.csv 414 415 416 417 ... 418 420 The following is example of the "domain-YYYYMMDD.csv" file with one 421 record matching the definition. 423 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 424 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 425 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 426 The following is an example of the 427 element for domain name records. 429 430 ... 431 432 433 434 435 436 438 domain-delete-YYYYMMDD.csv 439 440 441 442 ... 443 445 The following is example of the "domain-delete-YYYYMMDD.csv" file 446 with three records that matches the single field. 448 domain1.test 449 domain2.test 450 domainN.test 452 4.7.2. CSV common field elements 454 The element defined in the element 455 (Section 4.7.1) section has child elements that substitute for the 456 abstract element. By convention 457 elements include an 'f' prefix to identify them as field definition 458 elements. There are a set of common field elements that are used 459 across multiple data escrow objects. The common field elements are 460 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 461 using the "rdeCsv" sample namespace prefix. The CSV common field 462 elements include: 464 UTF-8 encoded name field with 465 type="eppcom:labelType". 467 Repository Object IDentifier (ROID) field with 468 type="eppcom:roidType" and isRequired="true". 470 Registrant contact identifier with 471 type="eppcom:clIDType". 473 The object status description, which is 474 free form text describing the rationale for the status, with 475 type="normalizedString". 477 Identifier of the client (registrar) that sponsors 478 the object with type="eppcom:clIDType" and isRequired="true". 480 Identifier of the registrar, defined in Section 5.4, 481 of the client that created the object with type="eppcom:clIDType". 483 Identifier of the client that created the object with 484 type="eppcom:clIDType". 486 Identifier of the registrar, defined in Section 5.4, 487 of the client that updated the object with type="eppcom:clIDType". 489 Identifier of the client that updated the object with 490 type="eppcom:clIDType". 492 Identifier of the registrar, defined in Section 5.4, 493 of the client that requested the transfer with 494 type="eppcom:clIDType" and isRequired="true". 496 Identifier of the client that requested the transfer 497 with type="eppcom:clIDType". 499 Identifier of the registrar, defined in Section 5.4, 500 of the client that should take or took action with 501 type="eppcom:clIDType" and isRequired="true". 503 Identifier of the client that should take or took 504 action for transfer with type="eppcom:clIDType". 506 Created date of object with type="dateTime". 508 Updated date of object with type="dateTime". 510 Expiration date of object with type="dateTime". 512 Date that transfer was requested with 513 type="dateTime" and isRequired="true". 515 Date that transfer action should be taken or has 516 been taken with type="dateTime" and isRequired="true". 518 Date of last transfer with type="dateTime". 520 State of the most recent transfer request with 521 type="eppcom:trStatusType" and isRequired="true". 523 General token field with type="token". 525 General language field with type="language". 527 IDN Table Identifier used for IDN domain names 528 with type="token". 530 General positive integer field with 531 type="positiveInteger". 533 Contains the URL of an object like a registrar object 534 with type="anyURI". 536 Custom field with name attribute that defines the 537 custom field name" with type="token". 539 4.8. Internationalized and Localized Elements 541 Some elements MAY be provided in either internationalized form 542 ("int") or provided in localized form ("loc"). Those elements use a 543 field value or "isLoc" attribute to specify the form used. If an 544 "isLoc" attribute is used, a value of "true" indicates the use of the 545 localized form and a value of "false" indicates the use of the 546 internationalized form. This MAY override the form specified for a 547 parent element. A value of "int" is used to indicate the 548 internationalized form and a value of "loc" is used to indicate the 549 localized form. When the internalized form ("int") is provided, the 550 field value MUST be represented in a subset of UTF-8 that can be 551 represented in the 7-bit US-ASCII character set. When the localized 552 form ("loc") is provided, the field value MAY be represented in 553 unrestricted UTF-8. 555 The field elements below of the "registrar" 556 element specify the internationalized form with the 557 isLoc="false" attribute. 559 ... 560 561 ... 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 593 registrar-YYYYMMDD.csv 594 595 596 597 ... 598 599 ... 601 The following is an example of using the 602 field value to define the internationalized or localized form of the 603 remainder of the "contactPostal" field values. 605 ... 606 607 ... 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 625 contactPostal-YYYYMMDD.csv 626 627 628 629 ... 630 631 ... 633 5. Object Description 635 This section describes the base objects supported by this 636 specification: 638 5.1. Domain Name Object 640 The domain name object is based on the EPP domain name mapping 641 specified in [RFC5731]. The domain name object supports both the XML 642 Model and the CSV Model, defined in the Models (Section 2) section. 643 The elements used for both models are defined in the following 644 sections. 646 5.1.1. XML Model 648 There are two elements used in the data escrow of the domain name 649 objects for the XML model including the , under the 650 element, and the element, under the 651 element. 653 5.1.1.1. object 655 The domain element is based on the EPP domain response for an 656 authorized client (see Section 3.1.2. of [RFC5731]) with additional 657 data from an EPP Query Response, see Section 3.1.3. of 658 [RFC5731], RGP status from [RFC3915], and data from the EPP 659 command, see Section 5.2.1. of [RFC5910]. 661 A element substitutes for the abstract 662 element to define a concrete definition of a domain. The 663 element can be replaced by other domain definitions 664 using the XML schema substitution groups feature. 666 The element contains the following child elements: 668 o A element that contains the fully qualified name of the 669 domain name object. If the domain name is an IDN, the ASCII 670 Compatible Encoding (ACE) MUST be used. 672 o A element that contains the repository object identifier 673 assigned to the domain name object when it was created. 675 o An OPTIONAL element that contains the fully qualified name 676 of the domain name in Unicode character set. It MUST be provided 677 if available. 679 o An OPTIONAL element that references the IDN 680 Table used for the IDN. This corresponds to the "id" attribute of 681 the element. This element MUST be present if the 682 domain name is an IDN. 684 o An OPTIONAL element is used to indicate that the 685 domain name is an IDN variant. This element contains the domain 686 name used to generate the IDN variant. 688 o One or more elements that contain the current status 689 descriptors associated with the domain name. 691 o Zero or more OPTIONAL element to represent 692 "pendingDelete" sub-statuses, including "redemptionPeriod", 693 "pendingRestore", and "pendingDelete", that a domain name can be 694 in as a result of grace period processing as specified in 695 [RFC3915]. 697 o An OPTIONAL element that contain the identifier for 698 the human or organizational social information object associated 699 as the holder of the domain name object. 701 o Zero or more OPTIONAL elements that contain identifiers 702 for the human or organizational social information objects 703 associated with the domain name object. 705 o An OPTIONAL element that contains the fully qualified names 706 of the delegated host objects or host attributes (name servers) 707 associated with the domain name object. See Section 1.1 of 708 [RFC5731] for a description of the elements used to specify host 709 objects or host attributes. 711 o A element that contains the identifier of the sponsoring 712 registrar. 714 o An OPTIONAL element that contains the identifier of the 715 registrar that created the domain name object. An OPTIONAL client 716 attribute is used to specify the client that performed the 717 operation. 719 o An OPTIONAL element that contains the date and time of 720 the domain name object creation. This element MUST be present if 721 the domain name has been allocated. 723 o An OPTIONAL element that contains the date and time 724 identifying the end (expiration) of the domain name object's 725 registration period. This element MUST be present if the domain 726 name has been allocated. 728 o An OPTIONAL element that contains the identifier of the 729 registrar that last updated the domain name object. This element 730 MUST NOT be present if the domain has never been modified. An 731 OPTIONAL client attribute is used to specify the client that 732 performed the operation. 734 o An OPTIONAL element that contains the date and time of 735 the most recent domain-name-object modification. This element 736 MUST NOT be present if the domain name object has never been 737 modified. 739 o An OPTIONAL element that contains the public key 740 information associated with Domain Name System security (DNSSEC) 741 extensions for the domain name as specified in [RFC5910]. 743 o An OPTIONAL element that contains the date and time of 744 the most recent domain object successful transfer. This element 745 MUST NOT be present if the domain name object has never been 746 transferred. 748 o An OPTIONAL element that contains the following child 749 elements related to the last transfer request of the domain name 750 object. This element MUST NOT be present if a transfer request 751 for the domain name has never been created. 753 * A element that contains the state of the most recent 754 transfer request. 756 * A element that contains the identifier of the registrar 757 that requested the domain name object transfer. An OPTIONAL 758 client attribute is used to specify the client that performed 759 the operation. 761 * A element that contains the date and time that the 762 transfer was requested. 764 * An element that contains the identifier of the registrar 765 that SHOULD act upon a PENDING transfer request. For all other 766 status types, the value identifies the registrar that took the 767 indicated action. An OPTIONAL client attribute is used to 768 specify the client that performed the operation. 770 * An element that contains the date and time of a 771 required or completed response. For a PENDING request, the 772 value identifies the date and time by which a response is 773 required before an automated response action will be taken by 774 the registry. For all other status types, the value identifies 775 the date and time when the request was completed. 777 * An OPTIONAL element that contains the end of the 778 domain name object's validity period (expiry date) if the 779 transfer caused or causes a change in the validity period. 781 Example of a domain object: 783 ... 784 785 example1.test 786 Dexample1-TEST 787 788 jd1234 789 sh8013 790 sh8013 791 792 ns1.example.com 793 ns1.example1.test 794 795 RegistrarX 796 RegistrarX 797 1999-04-03T22:00:00.0Z 798 2015-04-03T22:00:00.0Z 799 800 ... 802 5.1.1.2. object 804 The element contains the fully qualified domain 805 name that was deleted and purged. 807 Example of object: 809 ... 810 811 ... 812 813 foo.test 814 bar.test 815 816 ... 817 818 ... 820 5.1.2. CSV Model 822 For the CSV Model of the domain name object, the 823 child element of the element is used to hold the new 824 or updated domain name objects for the deposit. The 825 child element of the element is 826 used to hold the deleted or purged domain name objects for the 827 deposit. Both the and 828 elements contain one or more elements with a set of 829 named CSV file definitions using the "name" attribute. 831 Differential and incremental deposits are based on changes to the 832 domain name objects. The updated domain name object data under the 833 element is a cascade replace down all of the 834 domain name CSV files starting with the parent "domain" CSV File 835 Definition (Section 5.1.2.1.1). The child CSV file definitions 836 include a field. All the child CSV 837 file definition data for the domain name objects in the parent 838 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 839 deleted and then set using the data in the child CSV files. The 840 deleted domain name object data under the element 841 is a cascade delete starting from the "domain" Deletes CSV File 842 Definition (Section 5.1.2.2.1). 844 5.1.2.1. 846 The is used to hold the new or updated domain 847 name object information for the deposit. The is 848 split into separate CSV file definitions using named 849 elements with the "name" attribute. The following sections include 850 the supported domain name CSV file definitions: 852 5.1.2.1.1. "domain" CSV File Definition 854 The "domain" CSV File Definition defines the fields and CSV file 855 references used for the parent domain name object records. All the 856 other domain name CSV file definitions are child CSV files based on 857 the inclusion of the field. 859 The following "csvDomain" field elements MUST be used in the "domain" 860 element: 862 Domain name field with type="eppcom:labelType" and 863 isRequired="true". 865 The following "csvDomain" field elements MAY be used in the "domain" 866 element: 868 Fully qualified name of the original IDN 869 domain name object related to the variant domain name object with 870 type="eppcom:labelType". 872 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 873 "domain" element: 875 Registry Object IDentifier (ROID) for the domain name 876 object with isRequired="true". 878 or A choice of: 880 Identifier of the sponsoring client with 881 isRequired="true". 883 Contains the ID assigned by ICANN with 884 type="positiveInteger". The attribute "isRequired" MUST equal 885 "true". 887 The following "rdeCsv" fields, defined in section CSV common field 888 elements (Section 4.7.2), MAY be used in the "domain" 889 element: 891 Identifier of the registrar, defined in Section 5.4, 892 of the client that created the object. 894 Identifier of the client that created the domain name 895 object. 897 Identifier of the registrar, defined in Section 5.4, 898 of the client that updated the object. 900 Identifier of the client that last updated the domain 901 name object. 903 UTF8 encoded domain name for the 904 field element. 906 IDN Table Identifier used for the IDN domain 907 name object that MUST match a field element 908 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 910 Registrant contact identifier for the domain 911 name object. 913 Created date and time of the domain name object. 915 Date and time of the last update to the domain name 916 object. 918 Expiration date and time for the domain name 919 object. 921 Date and time of the last transfer for the domain 922 name object. 924 Example of a "domain" element. 926 ... 927 928 ... 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 948 domain-YYYYMMDD.csv 949 950 951 952 ... 953 954 ... 956 Example of the corresponding domain-YYYYMMDD.csv file. The file 957 contains four records (two active ASCII domains, original IDN with 958 LANG-1 language rules, and variant IDN with LANG-1 language rules). 960 domain1.test,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 961 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 962 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 963 domain2.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 964 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 965 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 966 xn--abc123.test,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 967 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 968 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 969 xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--abc123.test, 970 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 971 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 973 5.1.2.1.2. "domainContacts" CSV File Definition 975 The "domainContacts" CSV File Definition defines the fields and CSV 976 file references used for the domain name object link records to 977 contact objects, as described in Contact Object (Section 5.3). 979 The following "csvDomain" field elements, defined for the "domain" 980 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 981 "domainContacts" element: 983 The name of the domain object that is linked to 984 the contact object with isRequired="true". 986 The contact type for the contact object 987 link with type="domain:contactAttrType" and isRequired="true". 988 The supported contact type values include "admin" for the 989 administration contact, "billing" for the billing contact, and 990 "tech" for the technical contact. 992 The following "csvContact" fields, defined for the "contact" CSV File 993 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 994 element: 996 The server-unique contact identifier with 997 isRequired="true". 999 Example of a "domainContacts" 1000 element. 1002 ... 1003 1004 ... 1005 1006 1007 1008 1009 1010 1011 1012 1014 domainContacts-YYYYMMDD.csv 1015 1016 1017 1018 ... 1019 1020 ... 1022 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1023 file contains an admin, tech, and billing contact for the four domain 1024 names domain1.test, domain2.test, xn--abc123.test and xn-- 1025 abc321.test. 1027 domain1.test,domain1admin,admin 1028 domain1.test,domain1tech,tech 1029 domain1.test,domain1billing,billing 1030 domain2.test,domain2admin,admin 1031 domain2.test,domain2tech,tech 1032 domain2.test,domain2billing,billing 1033 xn--abc123.test,xnabc123admin,admin 1034 xn--abc123.test,xnabc123tech,tech 1035 xn--abc123.test,xnabc123billing,billing 1036 xn--abc321.test,xnabc123admin,admin 1037 xn--abc321.test,xnabc123tech,tech 1038 xn--abc321.test,xnabc123billing,billing 1040 5.1.2.1.3. "domainStatuses" CSV File Definition 1042 The "domainStatuses" CSV File Definition defines the fields and CSV 1043 file references used for the domain name object statuses. 1045 The following "csvDomain" fields, defined for the "domain" CSV File 1046 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1047 element: 1049 Domain name of status with isRequired="true". 1051 The status of the domain name with 1052 type="domain:statusValueType" and isRequired="true". 1054 The Registry Grace Period (RGP) status, as a 1055 sub-status of the "pendingDelete" status 1056 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1058 The following "rdeCsv" fields, defined in section CSV common field 1059 elements (Section 4.7.2), MAY be used in the "domainStatuses" 1060 element: 1062 Domain object status description which 1063 is free form text describing the rationale for the status. 1065 Language of the field. 1067 Example of a "domainStatuses" 1068 element. 1070 ... 1071 1072 ... 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1084 domainStatuses-YYYYMMDD.csv 1085 1086 1087 1088 ... 1089 1090 ... 1092 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1093 file contains the statuses for the four domain names domain1.test, 1094 domain2.test, xn--abc123.test and xn--abc321.test. 1096 domain1.test,clientUpdateProhibited,"Disallow update", 1097 en, 1098 domain1.test,clientDeleteProhibited,"Disallow delete", 1099 en, 1100 domain2.test,ok,,, 1101 xn--abc123.test,ok,,, 1102 xn--abc321.test,ok,,, 1104 5.1.2.1.4. "domainNameServers" CSV File Definition 1106 The "domainNameServers" CSV File Definition defines the fields and 1107 CSV file references used for the domain name delegated hosts (name 1108 servers). The "domainNameServers" CSV files define the relationship 1109 between a domain name object and a delegated host. The 1110 "domainNameServers" CSV File is used to support the 1111 model, defined in [RFC5731]. 1113 The following "csvDomain" fields, defined for the "domain" CSV File 1114 Definition (Section 5.1.2.1.1), MUST be used in the 1115 "domainNameServers" element: 1117 Domain name using the delegated host with 1118 isRequired="true". 1120 The following "csvHost" and "rdeCsv" field elements MUST be used in 1121 the "domainNameServers" element: 1123 or A choice of: 1125 Host name field with type="eppcom:labelType" and 1126 isRequired="true". 1128 Host object Registry Object IDentifier (ROID) 1129 assigned to the host object with isRequired="true". 1131 Example of a "domainNameServers" 1132 element. 1134 ... 1135 1136 ... 1137 1138 1139 1140 1141 1142 1143 1145 domainNameServers-YYYYMMDD.csv 1146 1147 1148 1149 ... 1150 1151 ... 1153 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1154 The file contains the delegated hosts (name servers) for the four 1155 domain names domain1.test, domain2.test, xn--abc123.test and xn-- 1156 abc321.test referenced via the field element. 1158 domain1.test,Hns1_domain1_test-TEST 1159 domain1.test,Hns2_domain1_test-TEST 1160 domain2.test,Hns1_domain2_test-TEST 1161 domain2.test,Hns2_domain2_test-TEST 1162 xn--abc123.test,Hns1_example_test-TEST 1163 xn--abc123.test,Hns2_example_test-TEST 1164 xn--abc321.test,Hns1_example_test-TEST 1165 xn--abc321.test,Hns2_example_test-TEST 1167 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1169 The "domainNameServersAddresses" CSV File Definition defines the 1170 fields and CSV file references used for supporting the host as domain 1171 attributes model. 1173 The following "csvDomain" fields, defined for the "domain" CSV File 1174 Definition (Section 5.1.2.1.1), MUST be used in the 1175 "domainNameServersAddresses" element: 1177 Domain name using the delegated host with host 1178 and isRequired="true". 1180 The following "rdeCsv" fields, defined in section Host CSV model 1181 elements (Section 5.2.2), MUST be used in the 1182 "domainNameServersAddresses" element: 1184 Host name field with type="eppcom:labelType" and 1185 isRequired="true". 1187 The following "csvHost" fields, defined in section Host CSV model 1188 elements (Section 5.2.2), MAY be used in the 1189 "domainNameServersAddresses" element: 1191 IP addresses associated with the host object with 1192 type="host:addrStringType". 1194 IP addresses version associated with the host 1195 object with type="host:ipType". "host:ipType" has the enumerated 1196 values of "v4" or "v6". 1198 Example of a "domainNameServersAddresses" 1199 element. 1201 ... 1202 1203 ... 1204 1205 1206 1207 1208 1209 1210 1211 1212 1214 domainNameServersAddresses-YYYYMMDD.csv 1215 1216 1217 1218 ... 1219 1220 ... 1222 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1223 file. The file contains the delegated hosts (name servers) for the 1224 four domain names domain1.test, domain2.test, xn--abc123.test and 1225 xn--abc321.test. 1227 domain1.test,ns1.domain1.test,192.0.2.1,v4 1228 domain1.test,ns2.domain1.test,2001:DB8::1,v6 1229 domain2.test,ns1.domain2.test2,192.0.2.2,v4 1230 domain2.test,ns2.domain2.test2,2001:DB8::2,v6 1231 xn--abc123.test,ns1.example.example,, 1232 xn--abc123.test,ns2.example.example,, 1233 xn--abc321.test,ns1.example.example,, 1234 xn--abc321.test,ns2.example.example,, 1236 5.1.2.1.6. "dnssec" CSV File Definition 1238 The "dnssec" CSV File Definition defines the fields and CSV file 1239 references used for the domain name object DNSSEC records (DS or Key 1240 Data). 1242 The following "csvDomain" field elements MUST be used in the "dnssec" 1243 element when the DS Data Interface per 1244 [RFC5910] is used: 1246 Contains the DS key tag value per [RFC5910] with 1247 type="unsignedShort" and isRequired="true". 1249 Contains the DS algorithm value per [RFC5910] 1250 with type="unsignedByte" and isRequired="true". 1252 Contains the DS digest type value per 1253 [RFC5910] with type="unsignedByte" and isRequired="true". 1255 Contains the DS digest value per [RFC5910] with 1256 type="hexBinary" and isRequired="true". 1258 The following "csvDomain" field elements MUST be used in the "dnssec" 1259 element when the Key Data Interface per 1260 [RFC5910] is used and MAY be used in the "dnssec" 1261 element when the DS Data Interface per [RFC5910] is 1262 used: 1264 Contains the flags field value per [RFC5910] with 1265 type="unsignedShort" and isRequired="true". 1267 Contains the Key protocol value per [RFC5910] 1268 with type="unsignedByte" and isRequired="true". 1270 Contains the Key algorithm value per [RFC5910] 1271 with type="unsignedByte" and isRequired="true". 1273 Contains the public key value per [RFC5910] with 1274 type="secDNS:keyType" and isRequired="true". 1276 The following "csvDomain" field elements MAY be used in the "dnssec" 1277 element: 1279 Indicates a child's preference for the 1280 number of seconds after signature generation when the parent's 1281 signature on the DS information provided by the child will expire 1282 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1284 The following "domain" fields, defined for the "domain" CSV File 1285 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1286 element: 1288 Domain name of the domain object associated with 1289 the DNSSEC record and isRequired="true". 1291 Example of a "dnssec" element with 1292 the DS Data Interface of [RFC5910]: 1294 1295 ... 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1308 dnssec-ds-YYYYMMDD.csv 1309 1310 1311 1312 ... 1313 1314 ... 1316 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1317 contains two DS records for domain1.test. 1319 domain1.test,604800,12345,3,1,49FD46E6C4B45C55D4AC 1320 domain1.test,604800,12346,3,1,38EC35D5B3A34B44C39B 1321 Example of a "dnssec" element with 1322 the Key Data Interface of [RFC5910]: 1324 1325 ... 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1338 dnssec-key-YYYYMMDD.csv 1339 1340 1341 1342 ... 1343 1344 ... 1346 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1347 contains two key records for domain1.test. 1349 domain1.test,604800,257,3,1,AQPJ////4Q== 1350 domain1.test,604800,257,3,1,AQPJ////4QQQ 1352 5.1.2.1.7. "domainTransfer" CSV File Definition 1354 The "domainTransfer" CSV File Definition defines the fields and CSV 1355 file references used for the domain name object pending and completed 1356 transfer records. No additional field elements were added for use in 1357 the "domainTransfer" element. 1359 The following "rdeCsv" fields, defined in section CSV common field 1360 elements (Section 4.7.2), MUST be used in the "domainTransfer" 1361 element: 1363 State of the most recent transfer request with 1364 isRequired="true". 1366 Identifier of the registrar, defined in Section 5.4, 1367 of the client that requested the transfer with isRequired="true". 1369 Date and time that the transfer was requested with 1370 isRequired="true". 1372 Identifier of the registrar, defined in Section 5.4, 1373 of the client that should take or took action with 1374 isRequired="true". 1376 Date and time that the transfer action should be 1377 taken or has been taken with isRequired="true". 1379 The following "rdeCsv" fields, defined in section CSV common field 1380 elements (Section 4.7.2), MAY be used in the "domainTransfer" 1381 element: 1383 Expiration date if the transfer command caused or 1384 causes a change in the validity period. 1386 Identifier of the client that requested the transfer. 1388 Identifier of the client that should take or took 1389 action for transfer. 1391 The following "csvDomain" fields, defined for the "domain" CSV File 1392 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1393 element: 1395 Domain name of the domain object involved in the 1396 transfer with isRequired="true". 1398 Example of a "domainTransfer" 1399 element. 1401 ... 1402 1403 ... 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1419 domainTransfer-YYYYMMDD.csv 1420 1421 1422 1423 ... 1424 1425 ... 1427 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1428 file contains one domain transfer record with a pending status. 1430 domain1.test,pending,registrarX,clientY, 1431 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1432 2016-04-03T22:00:00.0Z 1434 5.1.2.2. 1436 The is used to hold the deleted domain name 1437 objects in a differential or incremental deposit. All the domain 1438 name object data is deleted as part of a cascade delete. The 1439 is split into separate CSV file definitions using 1440 named elements with the "name" attribute. The following 1441 section defines the supported domain name deletes CSV file 1442 definition. 1444 5.1.2.2.1. "domain" Deletes CSV File Definition 1446 The following "csvDomain" field elements MUST be used in the deletes 1447 "domain" element: 1449 Domain name field with type="eppcom:labelType" and 1450 isRequired="true". 1452 Example of a "domain" element: 1454 ... 1455 1456 ... 1457 1458 1459 1460 1461 1462 1464 domain-delete-YYYYMMDD.csv 1465 1466 1467 1468 ... 1469 1470 ... 1472 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1473 file contains two domain name records. 1475 domain1.test 1476 domain2.test 1478 5.2. Host Object 1480 The host object is based on the EPP host name mapping in [RFC5732]. 1481 The host object supports both the XML Model and the CSV Model, 1482 defined in Models (Section 2) section. The elements used for both 1483 models are defined in the following sections. Both the 1484 and elements contain one or more 1485 elements with a set of named CSV file definitions using 1486 the "name" attribute. 1488 5.2.1. XML Model 1490 There are two elements used in the data escrow of the host objects 1491 for the XML model including the , under the 1492 element, and the element, under 1493 the element. 1495 A element substitutes for the 1496 abstract element to define a concrete definition of a host. The 1497 element can be replaced by other host 1498 definitions using the XML schema substitution groups feature. 1500 5.2.1.1. element 1502 The RDE host object is based on the EPP host response for an 1503 authorized client (Section 3.1.2. of [RFC5732]). 1505 The OPTIONAL element contains the following child elements: 1507 o A element that contains the fully qualified name of the 1508 host object. 1510 o A element that contains the repository object identifier 1511 assigned to the host object when the object was created. 1513 o One or more elements that describe the status of the host 1514 object. 1516 o Zero or more elements that contain the IP addresses 1517 associated with the host object. 1519 o A element that contains the identifier of the sponsoring 1520 registrar. 1522 o An OPTIONAL element that contains the identifier of the 1523 registrar that created the host object. An OPTIONAL client 1524 attribute is used to specify the client that performed the 1525 operation. 1527 o An OPTIONAL element that contains the date and time of 1528 host-object creation. 1530 o An OPTIONAL element that contains the identifier of the 1531 registrar that last updated the host object. This element MUST 1532 NOT be present if the host object has never been modified. An 1533 OPTIONAL client attribute is used to specify the client that 1534 performed the operation. 1536 o An OPTIONAL element that contains the date and time of 1537 the most recent host-object modification. This element MUST NOT 1538 be present if the host object has never been modified. 1540 o An OPTIONAL element that contains the date and time of 1541 the most recent host object successful transfer. This element 1542 MUST NOT be present if the domain name object has never been 1543 transfered. 1545 Example of object: 1547 ... 1548 1549 ns1.example1.test 1550 Hns1_example_test-TEST 1551 1552 1553 192.0.2.2 1554 192.0.2.29 1555 1080:0:0:0:8:800:200C:417A 1556 RegistrarX 1557 RegistrarX 1558 1999-05-08T12:10:00.0Z 1559 RegistrarX 1560 2009-10-03T09:34:00.0Z 1561 1562 ... 1564 5.2.1.2. object 1566 The element contains the fully qualified domain name 1567 of a host that was deleted. The element also 1568 supports host removal based on roid to support SRS systems in which 1569 different hosts with the same fully qualified domain name are active 1570 at the same time. 1572 Example of object: 1574 ... 1575 1576 ... 1577 1578 ns1.example.test 1579 1580 ... 1581 1582 ... 1584 5.2.2. CSV Model 1586 For the CSV Model of the host object, the child 1587 element of the element is used to hold the new or 1588 updated host objects for the deposit. The child 1589 element of the element is used to hold the deleted or 1590 purged host objects for the deposit. 1592 Differential and incremental deposits are based on changes to the 1593 host objects. The updated host object data under the 1594 element is a cascade replace down all of the host 1595 CSV files starting with the parent "host" CSV File Definition 1596 (Section 5.2.2.1.1). The child CSV file definitions include a 1597 field. All the child CSV file 1598 definition data for the host objects in the parent "host" CSV File 1599 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1600 using the data in the child CSV files. The deleted host object data 1601 under the element is a cascade delete starting from 1602 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1604 5.2.2.1. 1606 The is used to hold the new or updated host object 1607 information for the deposit. The is split into 1608 separate CSV file definitions using named elements with 1609 the "name" attribute. The following sections include the supported 1610 host CSV file definitions. 1612 5.2.2.1.1. "host" CSV File Definition 1614 The "host" CSV File Definition defines the fields and CSV file 1615 references used for the host object records. 1617 The following "csvHost" field elements MUST be used in the "host" 1618 element: 1620 Host name field with type="eppcom:labelType" and 1621 isRequired="true". 1623 The following "rdeCsv" fields, defined in section CSV common field 1624 elements (Section 4.7.2), MUST be used in the "host" 1625 element: 1627 Repository Object IDentifier (ROID) assigned to the 1628 host object with isRequired="true". 1630 The following "rdeCsv" and "csvRegistrar" fields, MAY be used in the 1631 "host" element: 1633 or A choice of: 1635 Identifier of the sponsoring client with 1636 isRequired="true". 1638 Contains the ID assigned by ICANN with 1639 type="positiveInteger". The attribute "isRequired" MUST equal 1640 "true". 1642 Identifier of the registrar, defined in Section 5.4, 1643 of the client that created the object. 1645 Identifier of the client that created the host 1646 object. 1648 Identifier of the registrar, defined in Section 5.4, 1649 of the client that updated the object. 1651 Identifier of the client that last updated the host 1652 object. 1654 Date and time that the host object was created. 1656 Date and time that the host object was last 1657 updated. 1659 Date and time that the host was last transferred. 1661 Example of a "host" element. 1663 ... 1664 1665 ... 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1682 host-YYYYMMDD.csv 1683 1684 1685 1686 ... 1687 1688 ... 1690 Example of the corresponding host-YYYYMMDD.csv file. The file 1691 contains six host records with four being internal hosts and two 1692 being external hosts. 1694 ns1.domain1.test,Hns1_example_test-TEST,registrarX,registrarX, 1695 clientY,1999-05-08T12:10:00.0Z,registrarX, 1696 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1697 ns2.domain1.test,Hns2_domain1_test-TEST,registrarX,registrarX, 1698 clientY,1999-05-08T12:10:00.0Z,registrarX, 1699 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1700 ns1.domain2.test,Hns1_domain2_test-TEST,registrarX,registrarX, 1701 clientY,1999-05-08T12:10:00.0Z,registrarX, 1702 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1703 ns2.domain2.test,Hns2_domain2_test-TEST,registrarX,registrarX, 1704 clientY,1999-05-08T12:10:00.0Z,registrarX, 1705 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1706 ns1.example.example,Hns1_example_test-TEST,registrarX,registrarX, 1707 clientY,1999-05-08T12:10:00.0Z,registrarX, 1708 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1709 ns2.example.example,Hns2_example_test-TEST,registrarX,registrarX, 1710 clientY,1999-05-08T12:10:00.0Z,registrarX, 1711 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1713 5.2.2.1.2. "hostStatuses" CSV File Definition 1715 The "hostStatuses" CSV File Definition defines the fields and CSV 1716 file references used for the host object statuses. 1718 The following "csvHost" fields, defined for the "host" CSV File 1719 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1720 element: 1722 The status of the host with 1723 type="host:statusValueType" and isRequired="true". 1725 The following "rdeCsv" fields, defined in section CSV common field 1726 elements (Section 4.7.2), MUST be used in the "hostStatuses" 1727 element: 1729 Host object Registry Object IDentifier (ROID) 1730 assigned to the host object with isRequired="true". 1732 The following "rdeCsv" fields, defined in section CSV common field 1733 elements (Section 4.7.2), MAY be used in the "hostStatuses" 1734 element: 1736 Host object status description which is 1737 free form text describing the rationale for the status. The 1738 attribute "isRequired" MUST equal "true". 1740 Language of the field. 1742 Example of a "hostStatuses" element. 1744 ... 1745 1746 ... 1747 1748 1749 1750 1751 1752 1753 1754 1755 1757 hostStatuses-YYYYMMDD.csv 1758 1759 1760 1761 ... 1762 1763 ... 1765 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1766 file contains the statuses for the six host names ns1.domain1.test, 1767 ns2.domain1.test, ns1.domain2.test, ns2.domain2.test, 1768 ns1.example.example and ns2.example.example. 1770 Hns1_domain1_test-TEST,ok,, 1771 Hns2_domain1_test-TEST,ok,, 1772 Hns1_domain2_test-TEST,ok,, 1773 Hns2_domain2_test-TEST,ok,, 1774 Hns1_example_test-TEST,ok,, 1775 Hns2_example_test-TEST,ok,, 1777 5.2.2.1.3. "hostAddresses" CSV File Definition 1779 The "hostAddresses" CSV File Definition defines the fields and CSV 1780 file references used for the host object IP addresses. 1782 The following "csvHost" field elements MUST be used in the 1783 "hostAddresses" element: 1785 IP addresses associated with the host object with 1786 type="host:addrStringType". The attribute "isRequired" MUST equal 1787 "true". 1789 IP addresses version associated with the host 1790 object with type="host:ipType". "host:ipType" has the enumerated 1791 values of "v4" or "v6". The attribute "isRequired" MUST equal 1792 "true". 1794 The following "rdeCsv" fields, defined in section CSV common field 1795 elements (Section 4.7.2), MUST be used in the "hostAddresses" 1796 element: 1798 Host object Registry Object IDentifier (ROID) 1799 assigned to the host object with isRequired="true". 1801 Example of a "hostAddresses" element. 1803 ... 1804 1805 ... 1806 1807 1808 1809 1810 1811 1812 1813 1815 hostAddresses-YYYYMMDD.csv 1816 1817 1818 1819 ... 1820 1821 ... 1823 Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The 1824 file contains the IP addresses for the host names ns1.domain1.test, 1825 ns2.domain1.test, ns1.domain2.test and ns2.domain2.test. 1827 Hns1_domain1_test-TEST,192.0.2.1,v4 1828 Hns2_domain1_test-TEST,2001:DB8::1,v6 1829 Hns1_domain2_test-TEST,192.0.2.2,v4 1830 Hns2_domain2_test-TEST,2001:DB8::2,v6 1832 5.2.2.2. 1834 The is used to hold the deleted host objects in a 1835 differential or incremental deposit. All the host object data is 1836 deleted as part of a cascade delete. The is split 1837 into separate CSV file definitions using named elements 1838 with the "name" attribute. The following section defines the 1839 supported host deletes CSV file definition. 1841 5.2.2.2.1. "host" Deletes CSV File Definition 1843 The following "rdeCsv" fields, defined in section CSV common field 1844 elements (Section 4.7.2), MUST be used in the "host" 1845 element: 1847 Repository Object IDentifier (ROID) assigned to the 1848 host object with isRequired="true". 1850 Example of a "host" element. 1852 ... 1853 1854 ... 1855 1856 1857 1858 1859 1860 1862 host-delete-YYYYMMDD.csv 1863 1864 1865 1866 ... 1867 1868 ... 1870 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1871 host records. 1873 Hns1_domain1_test-TEST 1874 Hns2_domain1_test-TEST 1875 Hns1_domain2_test-TEST 1876 Hns2_domain2_test-TEST 1878 5.3. Contact Object 1880 The contact object is based on the EPP contact name mapping in 1881 [RFC5733]. The contact object supports both the XML Model and the 1882 CSV Model, defined in Models (Section 2) section. The elements used 1883 for both models are defined in the following sections. 1885 5.3.1. XML Model 1887 There are two elements used in the data escrow of the contact objects 1888 for the XML model including the , under the 1889 element, and the element, 1890 under the element. 1892 A element substitutes for the abstract 1893 element to define a concrete definition of a contact. The 1894 element can be replaced by other contact 1895 definitions using the XML schema substitution groups feature. 1897 5.3.1.1. object 1899 The contact object is based on the EPP contact response for an 1900 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1901 including the data from an EPP Query Response, see 1902 Section 3.1.3. of [RFC5733]. 1904 The OPTIONAL element contains the following child elements: 1906 o A element that contains the server-unique identifier of the 1907 contact object 1909 o A element that contains the Repository Object IDentifier 1910 assigned to the contact object when the object was created. 1912 o One or more elements that describe the status of the 1913 contact object. 1915 o One or two elements that contain postal-address 1916 information. Two elements are provided so that address 1917 information can be provided in both internationalized and 1918 localized forms; a "type" attribute is used to identify the two 1919 forms. If an internationalized form (type="int") is provided, 1920 element content MUST be represented in a subset of UTF-8 that can 1921 be represented in the 7-bit US-ASCII character set. If a 1922 localized form (type="loc") is provided, element content MAY be 1923 represented in unrestricted UTF-8. The element 1924 contains the following child elements: 1926 * A element that contains the name of the individual or 1927 role represented by the contact. 1929 * An OPTIONAL element that contains the name of the 1930 organization with which the contact is affiliated. 1932 * An element that contains address information associated 1933 with the contact. An element contains the following 1934 child elements: 1936 + One, two, or three OPTIONAL elements that contain 1937 the contact's street address. 1939 + A element that contains the contact's city. 1941 + An OPTIONAL element that contains the contact's state 1942 or province. 1944 + An OPTIONAL element that contains the contact's postal 1945 code. 1947 + A element that contains the contact's two-letter 1948 country code. 1950 o An OPTIONAL element that contains the contact's voice 1951 telephone number. 1953 o An OPTIONAL element that contains the contact's facsimile 1954 telephone number. 1956 o An element that contains the contact's email address. 1958 o A element that contains the identifier of the sponsoring 1959 registrar. 1961 o An OPTIONAL element that contains the identifier of the 1962 registrar that created the contact object. An OPTIONAL client 1963 attribute is used to specify the client that performed the 1964 operation. 1966 o An OPTIONAL element that contains the date and time of 1967 contact-object creation. 1969 o An OPTIONAL element that contains the identifier of the 1970 registrar that last updated the contact object. This element MUST 1971 NOT be present if the contact has never been modified. An 1972 OPTIONAL client attribute is used to specify the client that 1973 performed the operation. 1975 o An OPTIONAL element that contains the date and time of 1976 the most recent contact-object modification. This element MUST 1977 NOT be present if the contact object has never been modified. 1979 o An OPTIONAL element that contains the date and time of 1980 the most recent contact object successful transfer. This element 1981 MUST NOT be present if the contact object has never been 1982 transferred. 1984 o An OPTIONAL element that contains the following child 1985 elements related to the last transfer request of the contact 1986 object: 1988 * A element that contains the state of the most recent 1989 transfer request. 1991 * A element that contains the identifier of the registrar 1992 that requested the domain name object transfer. An OPTIONAL 1993 client attribute is used to specify the client that performed 1994 the operation. 1996 * An element that contains the identifier of the registrar 1997 that SHOULD act upon a PENDING transfer request. For all other 1998 status types, the value identifies the registrar that took the 1999 indicated action. An OPTIONAL client attribute is used to 2000 specify the client that performed the operation. 2002 * A element that contains the date and time that the 2003 transfer was requested. 2005 * An element that contains the date and time of a 2006 required or completed response. For a PENDING request, the 2007 value identifies the date and time by which a response is 2008 required before an automated response action will be taken by 2009 the registry. For all other status types, the value identifies 2010 the date and time when the request was completed. 2012 o An OPTIONAL element that identifies elements that 2013 requiring exceptional server-operator handling to allow or 2014 restrict disclosure to third parties. See Section 2.9 of 2015 [RFC5733] for a description of the child elements contained within 2016 the element. 2018 Example object: 2020 ... 2021 2022 sh8013 2023 Csh8013-TEST 2024 2025 2026 2027 John Doe 2028 Example Inc. 2029 2030 123 Example Dr. 2031 Suite 100 2032 Dulles 2033 VA 2034 20166-6503 2035 US 2036 2037 2038 +1.7035555555 2039 +1.7035555556 2040 jdoe@example.test 2041 RegistrarX 2042 RegistrarX 2043 2009-09-13T08:01:00.0Z 2044 RegistrarX 2045 2009-11-26T09:10:00.0Z 2046 2009-12-03T09:05:00.0Z 2047 2048 pending 2049 clientW 2050 2011-03-08T19:38:00.0Z 2051 RegistrarX 2052 2011-03-13T23:59:59.0Z 2053 2054 2055 2056 2057 2058 2059 ... 2061 5.3.1.2. object 2063 The element contains the id of a contact that was 2064 deleted. 2066 Example of object: 2068 ... 2069 2070 ... 2071 2072 sh8013-TEST 2073 co8013-TEST 2074 2075 ... 2076 2077 ... 2079 5.3.2. CSV Model 2081 For the CSV Model of the contact object, the 2082 child element of the element is used to hold the new 2083 or updated contacts objects for the deposit. The 2084 child element of the element is 2085 used to hold the deleted or purged contact objects for the deposit. 2086 Both the and elements 2087 contain one or more elements with a set of named CSV 2088 file definitions using the "name" attribute. 2090 Differential and incremental deposits are based on changes to the 2091 contact objects. The updated contact object data under the 2092 element is a cascade replace down all of the 2093 contact CSV files starting with the parent "contact" CSV File 2094 Definition (Section 5.3.2.1.1). The child CSV file definitions 2095 include a field. All the child CSV 2096 file definition data for the contact objects in the parent "contact" 2097 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2098 then set using the data in the child CSV files. The deleted contact 2099 object data under the element is a cascade 2100 delete starting from the "contact" Deletes CSV File Definition 2101 (Section 5.3.2.2.1). 2103 5.3.2.1. 2105 The is used to hold the new or updated contact 2106 object information for the deposit. The is 2107 split into separate CSV file definitions using named 2108 elements with the "name" attribute. The following sections include 2109 the supported contact CSV file definitions. 2111 5.3.2.1.1. "contact" CSV File Definition 2113 The "contact" CSV File Definition defines the fields and CSV file 2114 references used for the contact object records. 2116 The following "csvContact" field elements MUST be used in the 2117 "contact" element: 2119 Contains the server-unique contact identifier with 2120 type="eppcom:clIDType" and isRequired="true". 2122 Contains the contact's email address with 2123 type="eppcom:minTokenType" and isRequired="true". 2125 The following field elements MAY be used in the "contact" 2126 element: 2128 Contains the contact's voice telephone number 2129 with type="contact:e164StringType". 2131 Contains the contact's voice telephone number 2132 extension with type="token". 2134 Contains the contact's facsimile telephone number 2135 with type="contact:e164StringType". 2137 Contains the contact's facsimile telephone 2138 number extension with type="token". 2140 The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the 2141 "contact" element: 2143 The Registry Object IDentifier (ROID) for the contact 2144 object with isRequired="true". 2146 or A choice of: 2148 Identifier of the sponsoring client with 2149 isRequired="true". 2151 Contains the ID assigned by ICANN with 2152 type="positiveInteger". The attribute "isRequired" MUST equal 2153 "true". 2155 The following "rdeCsv" fields, defined in section CSV common field 2156 elements (Section 4.7.2), MAY be used in the "contact" 2157 element: 2159 Identifier of the registrar, defined in Section 5.4, 2160 of the client that created the object. 2162 Identifier of the client that created the contact 2163 object. 2165 Identifier of the registrar, defined in Section 5.4, 2166 of the client that updated the object. 2168 Identifier of the client that last updated the 2169 contact object. 2171 Created date and time of the contact object. 2173 Date and time of the last update to the contact 2174 object. 2176 Date and time of the last transfer for the contact 2177 object. 2179 Example of a "contact" element. 2181 ... 2182 2183 ... 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2204 contact-YYYYMMDD.csv 2205 2206 2207 2208 ... 2209 2210 ... 2212 Example of the contact-YYYYMMDD.csv file. The file contains nine 2213 object contact records. 2215 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2216 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2217 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2218 2009-11-26T09:10:00.0Z 2219 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2220 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2221 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2222 2009-11-26T09:10:00.0Z 2223 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2224 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2225 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2226 2009-11-26T09:10:00.0Z 2227 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2228 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2229 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2230 2009-11-26T09:10:00.0Z 2231 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2232 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2233 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2234 2009-11-26T09:10:00.0Z 2235 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2236 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2237 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2238 2009-11-26T09:10:00.0Z 2239 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2240 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2241 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2242 2009-11-26T09:10:00.0Z 2243 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2244 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2245 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2246 2009-11-26T09:10:00.0Z 2247 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2248 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2249 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2250 2009-11-26T09:10:00.0Z 2252 5.3.2.1.2. "contactStatuses" CSV File Definition 2254 The "contactStatuses" CSV File Definition defines the fields and CSV 2255 file references used for the contact object statuses. 2257 The following "csvContact" field elements, defined for the "contact" 2258 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2259 "contactStatuses" element: 2261 Server-unique contact identifier of status with 2262 isRequired="true". 2264 The status of the contact with 2265 type="contact:statusValueType" and isRequired="true". 2267 The following "rdeCsv" fields, defined in section CSV common field 2268 elements (Section 4.7.2), MAY be used in the "contactStatuses" 2269 element: 2271 The contact object status description 2272 which is free form text describing the rationale for the status. 2274 Language of the field. 2276 Example of a "contactStatuses" 2277 element. 2279 ... 2280 2281 ... 2282 2283 2284 2285 2286 2287 2288 2289 2290 2292 contactStatuses-YYYYMMDD.csv 2293 2294 2295 2296 ... 2297 2298 ... 2300 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2301 file contains the statuses for the nine contact identifiers. 2303 domain1admin,ok,, 2304 domain1tech,ok,, 2305 domain1billing,ok,, 2306 domain2admin,ok,, 2307 domain2tech,ok,, 2308 domain2billing,ok,, 2309 xnabc123admin,ok,, 2310 xnabc123tech,ok,, 2311 xnabc123billing,ok,, 2313 5.3.2.1.3. "contactPostal" CSV File Definition 2315 The "contactPostal" CSV File Definition defines the fields and CSV 2316 file references used for the contact postal info object records. 2318 The following "csvContact" field elements MUST be used in the 2319 "contactPostal" element: 2321 Contains the form of the postal-address 2322 information with type="contact:postalLineType" and 2323 isRequired="true". This field specifies the form ("int" or 2324 "loc"), as defined in Section 4.8, of the , 2325 , , , 2326 , , fields. 2328 Contains the contact's name of the individual or 2329 role represented by the contact with type="contact:postalLineType" 2330 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2331 indicate the localized or internationalized form as defined in 2332 section Section 4.8. 2334 Contains the contact's contact's street address 2335 line with type="contact:fPostalLineType". An index attribute is 2336 required to indicate which street address line the field 2337 represents with index "0" for the first line and index "2" for the 2338 last line. An OPTIONAL "isLoc" attribute to used to indicate the 2339 localized or internationalized form as defined in section 2340 Section 4.8. 2342 Contains the contact's city with 2343 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2344 "isLoc" attribute to used to indicate the localized or 2345 internationalized form as defined in section Section 4.8. 2347 Contains the contact's country code with 2348 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2349 attribute to used to indicate the localized or internationalized 2350 form as defined in section Section 4.8. 2352 The following "csvContact" field elements MAY be used in the 2353 "contactPostal" element: 2355 Contains the name of the organization with which 2356 the contact is affiliated with type="contact:optPostalLineType". 2357 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2358 internationalized form as defined in section Section 4.8. 2360 Contains the contact's state or province with 2361 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2362 to used to indicate the localized or internationalized form as 2363 defined in section Section 4.8. 2365 Contains the contact's postal code with 2366 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2367 indicate the localized or internationalized form as defined in 2368 section Section 4.8. 2370 The following "csvContact" fields, defined for the "contact" CSV File 2371 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2372 element: 2374 Server-unique contact identifier for the contact 2375 object with isRequired="true". 2377 Example of a "contactPostal" 2378 element. 2380 ... 2381 2382 ... 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2400 contactPostal-YYYYMMDD.csv 2401 2402 2403 2404 ... 2405 2406 ... 2408 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2409 nine contact postal records. 2411 domain1admin,int,"John Doe","Example Inc.", 2412 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2413 domain1tech,int,"John Doe","Example Inc.", 2414 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2415 domain1billing,int,"John Doe","Example Inc.", 2416 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2417 domain2admin,int,"John Doe","Example Inc.", 2418 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2419 domain2tech,int,"John Doe","Example Inc.", 2420 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2421 domain2billing,int,"John Doe","Example Inc.", 2422 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2423 xnabc123admin,int,"John Doe","Example Inc.", 2424 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2425 xnabc123tech,int,"John Doe","Example Inc.", 2426 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2427 xnabc123billing,int,"John Doe","Example Inc.", 2428 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2430 5.3.2.1.4. "contactTransfer" CSV File Definition 2432 The "contactTransfer" CSV File Definition defines the fields and CSV 2433 file references used for the contact object pending and completed 2434 transfer records. No additional field elements were added for use in 2435 the "contactTransfer" element. The 2436 following "rdeCsv" fields, defined in section CSV common field 2437 elements (Section 4.7.2), MUST be used in the "contactTransfer" 2438 element: 2440 State of the most recent transfer request with 2441 isRequired="true". 2443 Identifier of the registrar, defined in Section 5.4, 2444 of the client that requested the transfer with isRequired="true". 2446 Date and time that the transfer was requested with 2447 isRequired="true". 2449 Identifier of the registrar, defined in Section 5.4, 2450 of the client that should take or took action with 2451 isRequired="true". 2453 Date and time that the transfer action should be 2454 taken or has been taken with isRequired="true". 2456 The following "rdeCsv" fields, defined in section CSV common field 2457 elements (Section 4.7.2), MAY be used in the "contactTransfer" 2458 element: 2460 Identifier of the client that requested the transfer. 2462 Identifier of the client that should take or took 2463 action for transfer. 2465 The following "csvContact" fields, defined for the "contact" CSV File 2466 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2467 element: 2469 Server-unique contact identifier for the contact 2470 object with isRequired="true". 2472 Example of a "contactTransfer" 2473 element. 2475 ... 2476 2477 ... 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2492 contactTransfer-YYYYMMDD.csv 2493 2494 2495 2496 ... 2497 2498 ... 2500 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2501 one contact transfer record in pending status. 2503 xnabc123admin,clientApproved,registrarX,clientX, 2504 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2506 5.3.2.1.5. "contactDisclose" CSV File Definition 2508 The "contactDisclose" CSV File Definition defines the fields and CSV 2509 file references used for the contact disclose object records. 2511 The following "csvContact" field elements MAY be used in the 2512 "contactDisclose" element: 2514 Contains flag with a value of "true" or 2515 "1" (one) notes the preference to allow disclosure of the 2516 specified elements as an exception to the stated data-collection 2517 policy. A value of "false" or "0" (zero) notes a client 2518 preference to not allow disclosure of the specified elements as an 2519 exception to the stated data-collection policy with 2520 type="boolean". The additional fields define specific exceptional 2521 disclosure preferences based on the 2522 field. 2524 Exceptional disclosure preference flag 2525 for the localized form of the contact name with type="boolean". 2527 Exceptional disclosure preference flag 2528 for the internationalized form of the contact name with 2529 type="boolean". 2531 Exceptional disclosure preference flag 2532 for the localized form of the contact organization with 2533 type="boolean". 2535 Exceptional disclosure preference flag 2536 for the internationalized form of the contact organization with 2537 type="boolean". 2539 Exceptional disclosure preference flag 2540 for the localized form of the contact address with type="boolean". 2542 Exceptional disclosure preference flag 2543 for the internationalized form of the contact address with 2544 type="boolean". 2546 Exceptional disclosure preference flag 2547 of the contact voice telephone number with type="boolean". 2549 Exceptional disclosure preference flag of 2550 the contact facsimile telephone number with type="boolean". 2552 Exceptional disclosure preference flag 2553 of the contact email address with type="boolean". 2555 The following "csvContact" fields, defined for the "contact" CSV File 2556 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2557 element: 2559 Server-unique contact identifier for the contact 2560 object with isRequired="true". 2562 Example of a "contactDisclose" 2563 element. 2565 ... 2566 2567 ... 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2585 contactDisclose-YYYYMMDD.csv 2586 2587 2588 2589 ... 2590 2591 ... 2593 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2594 one disclosure records, disabling disclosure of voice, fax, and 2595 email. 2597 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2599 5.3.2.2. 2601 The is used to hold the deleted contact objects 2602 in a differential or incremental deposit. All the contact object 2603 data is deleted as part of a cascade delete. The 2604 is split into separate CSV file definitions 2605 using named elements with the "name" attribute. The 2606 following section defines the supported contact deletes CSV file 2607 definition. 2609 5.3.2.2.1. "contact" Deletes CSV File Definition 2611 The following "csvContact" field elements MUST be used in the deletes 2612 "contact" element: 2614 Contains the server-unique contact identifier with 2615 type="eppcom:clIDType" and isRequired="true". 2617 Example of a "contact" element. 2619 ... 2620 2621 ... 2622 2623 2624 2625 2626 2627 2629 contact-delete-YYYYMMDD.csv 2630 2631 2632 2633 ... 2634 2635 ... 2637 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2638 six contact records. 2640 domain1admin 2641 domain1tech 2642 domain1billing 2643 domain2admin 2644 domain2tech 2645 domain2billing 2647 5.4. Registrar Object 2649 The registrar object represents the sponsoring client for other 2650 objects, for operational purposes MAY be the registry operator. The 2651 registrar object supports both the XML Model and the CSV Model, 2652 defined in Section 2. The elements used for both models are defined 2653 in the following sections. 2655 5.4.1. XML Model 2657 There are two elements used in the data escrow of the registrar 2658 objects for the XML model including the , 2659 under the element, and the 2660 element, under the element. 2662 A element substitutes for the 2663 abstract element to define a 2664 concrete definition of a registrar. The 2665 element can be replaced by other 2666 domain definitions using the XML schema substitution groups feature. 2668 5.4.1.1. element 2670 The element contains the following child elements: 2672 o An element that contains the Registry-unique identifier of 2673 the registrar object. This has a superordinate relationship 2674 to a subordinate , or of domain, contact and 2675 host objects. 2677 o An element that contains the name of the registrar. 2679 o An OPTIONAL element that contains the ID assigned by 2680 ICANN. 2682 o An OPTIONAL element that contains the operational status 2683 of the registrar. Possible values are: ok, readonly and 2684 terminated. 2686 o Zero or two OPTIONAL elements that contain postal- 2687 address information. Two elements are provided so that address 2688 information can be provided in both internationalized and 2689 localized forms; a "type" attribute is used to identify the two 2690 forms. If an internationalized form (type="int") is provided, 2691 element content MUST be represented in a subset of UTF-8 that can 2692 be represented in the 7-bit US-ASCII character set. If a 2693 localized form (type="loc") is provided, element content MAY be 2694 represented in unrestricted UTF-8. The element 2695 contains the following child elements: 2697 * A element that contains address information associated 2698 with the registrar. The element contains the following 2699 child elements: 2701 + One, two, or three OPTIONAL elements that contain 2702 the registrar's street address. 2704 + A element that contains the registrar's city. 2706 + An OPTIONAL element that contains the registrar's state 2707 or province. 2709 + An OPTIONAL element that contains the registrar's 2710 postal code. 2712 + A element that contains the registrar's country code. 2714 o An OPTIONAL element that contains the registrar's voice 2715 telephone number. 2717 o An OPTIONAL element that contains the registrar's facsimile 2718 telephone number. 2720 o An OPTIONAL element that contains the registrar's email 2721 address. 2723 o An OPTIONAL element that contains the registrar's URL. 2725 o An OPTIONAL elements that contains whois information. 2726 The element contains the following child elements: 2728 * An OPTIONAL element that contains the name of the 2729 registrar WHOIS server listening on TCP port 43 as specified in 2730 [RFC3912]. 2732 * An OPTIONAL element that contains the name of the 2733 registrar WHOIS server listening on TCP port 80/443. 2735 o An OPTIONAL element that contains the date and time of 2736 registrar-object creation. 2738 o An OPTIONAL element that contains the date and time of 2739 the most recent RDE registrar-object modification. This element 2740 MUST NOT be present if the rdeRegistrar object has never been 2741 modified. 2743 Example of object: 2745 ... 2746 2747 RegistrarX 2748 Registrar X 2749 123 2750 ok 2751 2752 2753 123 Example Dr. 2754 Suite 100 2755 Dulles 2756 VA 2757 20166-6503 2758 US 2759 2760 2761 +1.7035555555 2762 +1.7035555556 2763 jdoe@example.test 2764 http://www.example.test 2765 2766 whois.example.test 2767 http://whois.example.test 2768 2769 2005-04-23T11:49:00.0Z 2770 2009-02-17T17:51:00.0Z 2771 2772 ... 2774 5.4.1.2. object 2776 The element contains the id of a registrar that 2777 was deleted. 2779 Example of object: 2781 ... 2782 2783 ... 2784 2785 agnt0001-TEST 2786 2787 ... 2788 2789 ... 2791 5.4.2. CSV Model 2793 For the CSV Model of the registrar object, the 2794 child element of the element 2795 is used to hold the new or updated registrar objects for the deposit. 2796 The child element of the element 2797 is used to hold the deleted or purged registrar objects for the 2798 deposit. Both the and 2799 elements contain one or more elements with a set of 2800 named CSV file definitions using the "name" attribute. 2802 Differential and incremental deposits are based on changes to the 2803 registrar objects. The updated registrar object data under the 2804 element is a cascade replace down all of the 2805 registrar CSV files starting with the parent "registrar" CSV File 2806 Definition (Section 5.4.2.1.1). The child CSV file definitions 2807 include a field. All the child CSV 2808 file definition data for the registrar objects in the parent 2809 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2810 deleted and then set using the data in the child CSV files. The 2811 deleted registrar object data under the 2812 element is a cascade delete starting from the "registrar" Deletes CSV 2813 File Definition (Section 5.4.2.2.1). 2815 5.4.2.1. 2817 The is used to hold the new or updated 2818 registrar object information for the deposit. The 2819 is split into separate CSV file definitions 2820 using named elements with the "name" attribute. The 2821 following sections include the supported contact CSV file 2822 definitions. 2824 5.4.2.1.1. "registrar" CSV File Definition 2826 The "registrar" CSV File Definition defines the fields and CSV file 2827 references used for the registrar object records. 2829 The following "csvRegistrar" field elements MUST be used in the 2830 "registrar" element: 2832 or A choice of: 2834 Contains the server-unique registrar 2835 identifier with type="eppcom:clIDType" and isRequired="true". 2837 Contains the ID assigned by ICANN with 2838 type="positiveInteger". The attribute "isRequired" MUST equal 2839 "true". 2841 Contains the name of the registrar with 2842 type="normalizedString" and isRequired="true". 2844 The following field elements MAY be used in the "registrar" 2845 element: 2847 Contains the status of the registrar with 2848 type="csvRegistrar:statusValueType". 2850 Contains the ID assigned by ICANN with 2851 type="positiveInteger". This field is included in this section in 2852 addition to the section above to support optionally providing the 2853 field when the field is 2854 used. 2856 Contains the Whois URL of the registrar 2857 with type="anyURI". 2859 The following "rdeCsv" fields, defined in section CSV common field 2860 elements (Section 4.7.2), MAY be used in the "registrar" 2861 element: 2863 Created date and time of the registrar object. 2865 Date and time of the last update to the registrar 2866 object. 2868 URL for the registrar web home page. 2870 The following "csvContact" fields, defined in section Contact Object 2871 (Section 5.3), MAY be used in the "registrar" 2872 element: 2874 Registrar street address line with an "index" 2875 attribute that represents the order of the street address line 2876 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2877 indicate the localized or internationalized form, as defined in 2878 Section 4.8. 2880 Registrar city with an OPTIONAL "isLoc" attribute 2881 that is used to indicate the localized or internationalized form, 2882 as defined in Section 4.8. 2884 Registrar country code with an OPTIONAL "isLoc" 2885 attribute that is used to indicate the localized or 2886 internationalized form, as defined in Section 4.8. 2888 Registrar email address. The attribute 2889 "isRequired" MUST equal "false". 2891 Registrar state or province with an OPTIONAL 2892 "isLoc" attribute that is used to indicate the localized or 2893 internationalized form, as defined in Section 4.8. 2895 Registrar postal code with an OPTIONAL "isLoc" 2896 attribute that is used to indicate the localized or 2897 internationalized form, as defined in Section 4.8. 2899 Registrar voice telephone number. 2901 Registrar voice telephone number extension. 2903 Registrar facsimile telephone number. 2905 Registrar facsimile telephone number extension. 2907 Example of a "registrar" 2908 element. 2910 ... 2911 2912 ... 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2939 registrar-YYYYMMDD.csv 2940 2941 2942 2943 ... 2944 2945 ... 2947 Example of the registrar-YYYYMMDD.csv file. The file contains three 2948 registrar records. 2950 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 2951 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2952 +1.7035555556,,jdoe@example.test,http://www.example.test, 2953 http://whois.example.test,2005-04-23T11:49:00.0Z, 2954 2009-02-17T17:51:00.0Z 2955 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 2956 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2957 +1.7035555556,,jdoe@example.test,http://www.example.test, 2958 http://whois.example.test,2005-04-23T11:49:00.0Z, 2959 2009-02-17T17:51:00.0Z 2960 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 2961 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2962 +1.7035555556,,jdoe@example.test,http://www.example.test, 2963 http://whois.example.test,2005-04-23T11:49:00.0Z, 2964 2009-02-17T17:51:00.0Z 2966 5.4.2.2. 2968 The is used to hold the deleted registrar 2969 objects in a differential or incremental deposit. All the registrar 2970 object data is deleted as part of a cascade delete. The 2971 is split into separate CSV file definitions 2972 using named elements with the "name" attribute. The 2973 following section defines the supported registrar deletes CSV file 2974 definition. 2976 5.4.2.2.1. "registrar" Deletes CSV File Definition 2978 The following "csvRegistrar" field elements MUST be used in the 2979 deletes "registrar" element: 2981 or A choice of: 2983 Contains the server-unique registrar 2984 identifier with type="eppcom:clIDType" and isRequired="true". 2986 Contains the ID assigned by ICANN with 2987 type="positiveInteger". The attribute "isRequired" MUST equal 2988 "true". 2990 Example of a "registrar" element. 2992 ... 2993 2994 ... 2995 2996 2997 2998 2999 3000 3002 registrar-delete-YYYYMMDD.csv 3003 3004 3005 3006 ... 3007 3008 ... 3010 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 3011 one registrar record. 3013 registrarZ 3015 5.5. IDN Table Reference Object 3017 The Internationalized Domain Names (IDN) table reference object is a 3018 pseudo-object that is used to provide a short reference to the IDN 3019 Table and Policy used in IDN registrations. The IDN reference object 3020 supports both the XML and the CSV Model, defined in the Models 3021 (Section 2) section. The elements used for both models are defined 3022 in the following sections. 3024 5.5.1. XML Model 3026 There is one element used in the data escrow of the IDN table 3027 reference objects for the XML model that is the , 3028 under the element. 3030 5.5.1.1. object 3032 The contains the following elements. An "id" 3033 attribute is used to specify an identifier for the IDN table. 3035 o An element that contains the URL of the IDN table that is 3036 being referenced. 3038 o A element that contains the URL of the IDN policy 3039 document. If IDN variants are generated algorithmically, the 3040 policy document MUST define the algorithm and the state of the 3041 implicit generated IDN variants. For a list of suggested states 3042 for implicit IDN variants, please see [variantTLDsReport]. 3044 Example of object: 3046 ... 3047 3048 3049 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3050 3051 3052 http://registro.br/dominio/regras.html 3053 3054 3055 ... 3057 5.5.2. CSV Model 3059 The IDN domain names, defined in Section 5.1, MAY have references to 3060 the IDN language identifier using the field 3061 element. The IDN table reference object defines the mapping of a 3062 language identifier to a language table URL. The language table URL 3063 defines the character code points that can be used for the language 3064 identifier. The elements used for the IDN table reference object is 3065 defined in this section. The child element of the 3066 element is used to hold the new or updated IDN table 3067 reference objects for the deposit. The child 3068 element of the element is used to hold the deleted or 3069 purged IDN table reference objects for the deposit. Both the 3070 and elements contain one or more 3071 elements with a set of named CSV file definitions using 3072 the "name" attribute. 3074 5.5.2.1. 3076 The is used to hold the new or updated IDN table 3077 reference object information for the deposit. The 3078 is split into separate CSV file definitions using named 3079 elements with the "name" attribute. The following sections include 3080 the supported IDN table reference CSV file definitions. 3082 5.5.2.1.1. "idnLanguage" CSV File Definition 3084 The "idnLanguage" CSV File Definition defines the fields and CSV file 3085 references used for the IDN table reference object records. 3087 The following "rdeCsv" fields, defined in Section 4.7.2, MUST be used 3088 in the "idnLanguage" element: 3090 The language identifier that matches the values 3091 for the field element in the "domain" CSV 3092 File Definition (Section 5.1.2.1.1) files. The attribute 3093 "isRequired" MUST equal "true". 3095 URL that defines the character code points that can be 3096 used for the language defined by the field element. 3097 The attribute "isRequired" MUST equal "true". 3099 Example of a "idnLanguage" element. 3101 ... 3102 3103 ... 3104 3105 , 3106 3107 3108 3109 3110 3111 3113 idnLanguage-YYYYMMDD.csv 3114 3115 3116 3117 ... 3118 3119 ... 3121 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3122 contains two IDN language records. 3124 LANG-1, 3125 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3126 LANG-2, 3127 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3129 5.5.2.2. 3131 The is used to hold the deleted IDN table reference 3132 objects in a differential or incremental deposit. The 3133 is split into separate CSV file definitions using 3134 named elements with the "name" attribute. The following 3135 section defines the supported IDN table reference deletes CSV file 3136 definition. 3138 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3140 The following "idnLanguage" field elements MUST be used in the 3141 deletes "idnLanguage" element: 3143 The language identifier that matches the values 3144 for the field element in the "domain" CSV 3145 File Definition (Section 5.1.2.1.1) files. The attribute 3146 "isRequired" MUST equal "true". 3148 Example of a "idnLanguage" element. 3150 ... 3151 3152 ... 3153 3154 3155 3156 3157 3158 3160 idnLanguage-delete-YYYYMMDD.csv 3161 3162 3163 3164 ... 3165 3166 ... 3168 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3169 contains one IDN language record. 3171 LANG-2 3173 5.6. NNDN Object 3175 A NNDN (NNDN's not domain name) can be used to store registry 3176 reserved names or (blocked, withheld or mirrored) IDN variants. 3178 A NNDN is a lightweight domain-like object that is not linked 3179 directly to a Registrar (a mirroring NNDN is linked to a Registrar 3180 via the original name). 3182 A domain name can only exist as a domain name object or NNDN object, 3183 but not both. 3185 The NNDN object supports both the XML and the CSV Model, defined in 3186 the Models (Section 2) section. The elements used for both models 3187 are defined in the following sections. 3189 5.6.1. XML Model 3191 There are two elements used in the data escrow of the NNDN objects 3192 for the XML model including the , under the 3193 element, and the element, under the 3194 element. 3196 A element substitutes for the 3197 abstract element to define a concrete definition of a NNDN. The 3198 element can be replaced by other NNDN 3199 definitions using the XML schema substitution groups feature. 3201 5.6.1.1. object 3203 The element contains the following child elements: 3205 o An element that contains the fully qualified name of the 3206 NNDN. If the NNDN is an IDN, the ASCII Compatible Encoding (ACE) 3207 MUST be used. 3209 o An OPTIONAL element that contains the fully qualified name 3210 of the NNDN in Unicode character set. It MUST be provided if 3211 available. 3213 o An OPTIONAL element that references the IDN 3214 Table used for the NNDN. This corresponds to the "id" attribute 3215 of the element. This element MUST be present if the 3216 NNDN is an IDN. 3218 o An OPTIONAL element is used to indicate that the 3219 NNDN is used for an IDN variant. This element contains the domain 3220 name used to generate the IDN variant. 3222 o A element that indicates the state of the NNDN: 3223 blocked, withheld or mirrored. 3225 * If a NNDN is considered undesirable for registration (i.e., 3226 unavailable for allocation to anyone), then the NNDN will be 3227 tagged as "blocked". 3229 * If a NNDN is considered a potential registration of a domain 3230 object for a registrant, then the NNDN will be tagged as 3231 "withheld". This status is only used when the NNDN is used for 3232 an IDN variant. 3234 * If a NNDN is considered a mirrored IDN variant of a domain 3235 object, then the NNDN will be tagged as "mirrored". A 3236 mirroringNS attribute is used to specify if the mirrored IDN 3237 variant use the NS mirror mechanism. The default value of 3238 mirroringNS is true. If another mechanism such as DNAME is 3239 used, the value of mirroringNS attribute MUST be false. 3241 o An OPTIONAL element that contains the date and time of 3242 the NNDN object creation. 3244 Example of object: 3246 ... 3247 3248 xn--exampl-gva.test 3249 pt-BR 3250 example1.test 3251 withheld 3252 2005-04-23T11:49:00.0Z 3253 3254 ... 3256 5.6.1.2. object 3258 The element contains the ACE of a NNDN that was 3259 deleted, i.e., the . 3261 Example of object: 3263 ... 3264 3265 ... 3266 3267 xn--pingino-q2a.test 3268 3269 ... 3270 3271 ... 3273 5.6.2. CSV Model 3275 For the CSV Model of the NNDN object, the child 3276 element of the element is used to hold the new or 3277 updated NNDN objects for the deposit. The child 3278 element of the element is used to hold the deleted or 3279 purged NNDN objects for the deposit. Both the and 3280 elements contain one or more elements 3281 with a set of named CSV file definitions using the 3282 "name" attribute. 3284 5.6.2.1. 3286 The is used to hold the new or updated NNDN object 3287 information for the deposit. The is split into 3288 separate CSV file definitions using named elements with 3289 the "name" attribute. The following sections include the supported 3290 NNDN CSV file definitions. 3292 5.6.2.1.1. "NNDN" CSV File Definition 3294 The "NNDN" CSV File Definition defines the fields and CSV file 3295 references used for the NNDN object records. 3297 The following "csvNNDN" field elements MUST be used in the "NNDN" 3298 element: 3300 ASCII Compatible Encoding (ACE) field of the NNDN 3301 with type="eppcom:labelType" and isRequired="true". 3303 State of the NNDN: blocked or withheld with 3304 type="rdeNNDN:nameState" and isRequired="true". See 3305 Section 5.6.1.1 for a description of the possible values for the 3306 element. 3308 The following field elements MAY be used in the "NNDN" 3309 element: 3311 Domain name used to generate the IDN variant 3312 with type="eppcom:labelType". 3314 Defines whether the "mirroring" 3315 uses the NS mirror mechanism, as described 3316 for the "mirroringNS" attribute in 3317 Section 5.6.1.1, with type="boolean". If the field element is not 3318 defined the default value is "true". 3320 The following "rdeCsv" fields, defined in section CSV common field 3321 elements (Section 4.7.2), MAY be used in the "NNDN" 3322 element: 3324 Created date and time of the NNDN object. 3326 Name of the NNDN in Unicode character set for the 3327 field element. 3329 IDN Table Identifier for the NNDN that matches 3330 an IDN Table Reference Object record, as defined in Section 5.5.2. 3332 Example of a "NNDN" element: 3334 ... 3335 3336 ... 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3349 NNDN-YYYYMMDD.csv 3350 3351 3352 3353 ... 3354 3355 ... 3357 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3358 contains two NNDN records for an IDN with one blocked variant and one 3359 mirrored variant. 3361 xn--abc456.test,LANG-1,xn--abc123.test, 3362 blocked,,2005-04-23T11:49:00.0Z 3363 xn--abc789.test,LANG-1,xn--abc123.test, 3364 mirrored,1,2005-04-23T11:49:00.0Z 3366 5.6.2.2. 3368 The is used to hold the deleted NNDN objects in a 3369 differential or incremental deposit. The is split 3370 into separate CSV file definitions using named elements 3371 with the "name" attribute. The following section defines the 3372 supported NNDN deletes CSV file definition. 3374 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3376 The following "NNDN" field elements MUST be used in the deletes 3377 "NNDN" element: 3379 ASCII Compatible Encoding (ACE) field of the NNDN 3380 with type="eppcom:labelType" and isRequired="true". 3382 Example of a "NNDN" element. 3384 ... 3385 3386 ... 3387 3388 3389 3390 3391 3392 3394 NNDN-delete-YYYYMMDD.csv 3395 3396 3397 3398 ... 3399 3400 ... 3402 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3403 contains one NNDN records. 3405 xn--abc456.test 3407 5.7. EPP Parameters Object 3409 The EPP Parameters Object is a pseudo-object that defines the set of 3410 object and object extension services supported by the registry, as 3411 defined in [RFC5730]. The EPP Parameters Object is only defined as 3412 XML but could be used in the XML model or CSV model. The EPP 3413 Parameters Object is defined using the 3414 element. The EPP Parameters Object SHOULD be included if the 3415 registry supports EPP. Only one EPP Parameters Object MUST exist at 3416 a certain point in time (watermark). 3418 The syntax and content of the children 3419 elements is as explained in section 2.4 of [RFC5730]. The children 3420 of the are as follows: 3422 o One or more elements that indicate the EPP versions 3423 supported by the registry. 3425 o One or more elements that indicate the identifiers of the 3426 text response languages supported by the registry's EPP server. 3428 o One or more elements that contain namespace URIs 3429 representing the objects that the registry's EPP server is capable 3430 of managing. 3432 o An OPTIONAL element that contains one or more 3433 elements that contain namespace URIs representing object 3434 extensions supported by the registry's EPP server. 3436 o A element that contains child elements used to describe the 3437 server's privacy policy for data collection and management. See 3438 section 2.4 of [RFC5730] for more details. 3440 Example of element object: 3442 ... 3443 3444 1.0 3445 en 3446 urn:ietf:params:xml:ns:domain-1.0 3447 3448 urn:ietf:params:xml:ns:contact-1.0 3449 3450 urn:ietf:params:xml:ns:host-1.0 3451 3452 3453 urn:ietf:params:xml:ns:rgp-1.0 3454 urn:ietf:params:xml:ns:secDNS-1.1 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 ... 3475 5.8. Policy Object 3477 The Policy object is a pseudo-object that is used to specify which 3478 OPTIONAL elements from the XML Model are REQUIRED based on the 3479 business model of the registry. For the CSV Model, the OPTIONAL 3480 "isRequired" attribute of the elements, defined in 3481 Section 4.7.1, is used to specify which OPTIONAL fields are REQUIRED 3482 based on the business model of the registry. 3484 5.8.1. object 3486 The OPTIONAL contains the following attributes: 3488 o An that defines that the referenced is 3489 REQUIRED. 3491 o that defines the XPath of the element referenced by 3492 . 3494 Example of object: 3496 ... 3497 3499 ... 3501 5.9. Header Object 3503 The Header Object is a pseudo-object that is used to specify the 3504 number of objects in the repository at a specific point in time 3505 (watermark) regardless of the type of deposit: differential, full or 3506 incremental. The Header Object may also be used to provide 3507 additional information on the contents of the deposit. The Header 3508 Object is only defined as XML but one header object MUST always be 3509 present per escrow deposit regardless of using XML Model or CSV 3510 Model. The Header Object is defined using the 3511 element. 3513 5.9.1. object 3515 The contains the following elements: 3517 o A choice of one of the elements defined in the 3518 "repositoryTypeGroup" group element that indicates the unique 3519 identifier for the repository being escrowed. Possible elements 3520 are: 3522 * A element that defines TLD or the REGISTRY- 3523 CLASS DOMAIN NAME (RCDN) being escrowed in the case of a 3524 Registry data escrow deposit. For IDNs the A-Label is used 3525 [RFC5891]. 3527 * A element that defines the Registrar ID 3528 corresponding to a Registrar data escrow deposit. In the case 3529 of an ICANN-accredited Registrar, the 3530 element MUST be the IANA Registrar ID assigned by ICANN. 3532 * A element that defines the provider ID 3533 corresponding to a Privacy and Proxy Services Provider data 3534 escrow deposit. In the case of an ICANN-accredited Privacy and 3535 Proxy Services Provider, the element MUST be 3536 the unique ID assigned by ICANN. 3538 * A element that defines the provider ID 3539 corresponding to a Reseller data escrow deposit. 3541 o A element that contains the number of objects in the SRS 3542 at a specific point in time (watermark) regardless of the type of 3543 deposit: differential, full or incremental. The element 3544 supports the following attributes: 3546 * A "uri" attribute reflects the XML namespace URI of the primary 3547 objects for the XML Model and CSV Model. For example, the 3548 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3549 domain name objects using the XML Model, and the "uri" is set 3550 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3551 objects using the CSV Model. 3553 * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS 3554 DOMAIN NAME (RCDN) of the objects included in the 3555 element. For IDNs the A-Label is used [RFC5891]. If the 3556 "rcdn" attribute is present, the value of the element 3557 must include only objects related to registrations in the same 3558 and lower levels. For example in a data escrow deposit for the 3559 .EXAMPLE TLD, a value of "example" in the "rcdn" attribute 3560 within the element indicates the number of objects in 3561 the TLD including objects in other RCDNs within the TLD, 3562 whereas a value of "com.example" indicates the number of 3563 elements for objects under "com.example" and lower levels. 3564 Omitting the "rcdn" attribute indicates that the total includes 3565 all objects of the specified "uri" in the repository (e.g. the 3566 TLD, Registrar, or PPSP). 3568 * An OPTIONAL "registrarId" attribute indicates the identifier of 3569 the sponsoring Registrar of the objects included in the 3570 element. In the case of an ICANN-accredited Registrar, the 3571 value MUST be the IANA Registrar ID assigned by ICANN. 3573 o An OPTIONAL element that contains a tag that defines 3574 the expected content in the deposit. The producer and consumer of 3575 the deposits will coordinate the set of possible 3576 element values. 3578 Example of object referencing only the XML Model 3579 objects: 3581 ... 3582 3583 test 3584 2 3586 1 3588 1 3590 1 3592 3593 1 3595 1 3597 1 3599 3600 3601 ... 3603 Example of object referencing the CSV and XML 3604 Model objects: 3606 ... 3607 3608 test 3609 2 3611 1 3613 1 3615 1 3617 3618 1 3620 1 3622 1 3624 3625 3626 ... 3628 6. RDE IDN Variants handling 3630 Depending on the Registration Policy of the Registry; for a domain 3631 name there may be multiple variant names. See [variantTLDsReport] 3632 for further detail on IDN variants. 3634 A registry could choose to escrow IDN variants as domains or NNDN 3635 objects. A specific IDN variant can be represented in the escrow 3636 deposit, as a domain or as a NNDN object, but not both. 3638 If using domain objects to represent IDN variants, the normal 3639 behavior during restoration of a SRS based on an escrow deposit is to 3640 restore the IDN variants as a mirrored variant. If the registration 3641 data of the IDN variant is different from the original name, the 3642 details of this specific implementation MUST be described in the IDN 3643 policy document. 3645 A NNDN or a domain name are explicit representations of an IDN 3646 variant while an IDN variant computed based on an algorithm is an 3647 implicit representation. Explicit representation of an IDN variant 3648 takes precedence over an implicit representation. 3650 7. Profile 3652 Different business models of registries exist, therefore the registry 3653 is responsible to define a profile that matches its particular 3654 business model. The profile mechanism allows a registry to extend 3655 this specification. 3657 A profile is the process of: 3659 1. Extending base objects with the mechanisms defined for XML and 3660 CSV models. 3662 * In the case of the XML model, abstract elements could be use 3663 to extend the following objects: , , , 3664 and using XML schema substitution groups 3665 feature. 3667 2. Defining a object to specify which OPTIONAL elements of 3668 this base specification is required based on the business model 3669 of the registry. An example is the element that is 3670 usually REQUIRED but it is specified as OPTIONAL in this 3671 specification to support existing business models. 3673 3. Adding new escrowed objects using the and 3674 elements. 3676 4. Providing the XML schemas to third parties that require them to 3677 validate the escrow deposits. 3679 8. Data escrow agent extended verification process 3681 A Data Escrow Agent SHOULD perform an extended verification process 3682 that starts by creating a dataset to be tested. 3684 o If a full deposit is to be tested, the full deposit is the 3685 dataset. 3687 o If an incremental deposit is to be tested, the dataset is created 3688 by using the incremental plus the last previous full deposit. 3690 o If a differential deposit is to be tested, the dataset is created 3691 by using the differential deposit plus all the required deposits 3692 leading to the last previous full deposit. 3694 The following are the minimum suggested tests on the dataset: 3696 o Validate the escrow deposits using the definition agreed with the 3697 registry. 3699 * In the case of the XML model, the contents of the escrow 3700 deposits MUST be validated using the XML schemas of the 3701 profile. 3703 o Count the objects and validate that the number of objects is equal 3704 to the number objects reported in the
element of the 3705 escrow deposit of that point in time (watermark). 3707 o All contact objects linked to domain names MUST be present. 3709 o All registrars objects linked to other objects MUST be present. 3711 o A domain name exists as a domain name or NNDN, but not both. 3713 o The elements listed as required in the element MUST be 3714 present. 3716 o All idnTableRef definitions linked from other objects MUST be 3717 present. 3719 o If an EPP Parameters Object was escrowed in the past, one and only 3720 one EPP Parameters Object MUST be present. 3722 o The watermark is not in the future. 3724 9. Formal Syntax 3726 Schemas are presented here. 3728 9.1. RDE CSV Schema 3730 Copyright (c) 2012 IETF Trust and the persons identified as authors 3731 of the code. All rights reserved. 3733 Redistribution and use in source and binary forms, with or without 3734 modification, are permitted provided that the following conditions 3735 are met: 3737 o Redistributions of source code must retain the above copyright 3738 notice, this list of conditions and the following disclaimer. 3740 o Redistributions in binary form must reproduce the above copyright 3741 notice, this list of conditions and the following disclaimer in 3742 the documentation and/or other materials provided with the 3743 distribution. 3745 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3746 names of specific contributors, may be used to endorse or promote 3747 products derived from this software without specific prior written 3748 permission. 3750 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3751 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3752 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3753 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3754 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3755 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3756 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3757 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3758 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3759 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3760 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3762 BEGIN 3763 3765 3772 3775 3777 3780 3781 3782 Registry Data Escrow Comma-Seperated Values (CSV) 3783 3784 3786 3787 3789 3790 3791 3792 3793 3794 3795 3796 3797 3799 3800 3801 3802 3803 3804 3805 3807 3808 3811 3812 3813 3815 3816 3817 3818 3819 3820 3822 3824 3825 3826 3828 3829 3830 3831 3832 3833 3835 3837 3838 3839 3841 3842 3843 3845 3846 3847 3848 3849 3851 3852 3853 3854 3855 3856 3857 3858 3860 3861 3862 3864 3865 3867 3868 3869 3870 3871 3873 3874 3875 3877 3878 3880 3881 3882 3883 3884 3886 3887 3888 3889 3890 3894 3895 3896 3898 3900 3902 3903 3905 3907 3909 3910 3912 3914 3916 3918 3920 3922 3924 3926 3928 3929 3930 3931 3932 3934 3935 3936 3937 3938 3939 3940 3941 3943 3944 3945 3947 3948 3950 3952 3954 3955 3957 3958 3960 3962 3963 3964 3965 3966 3968 3969 3970 3971 3972 3973 3974 3975 3977 3978 3979 3981 3982 3983 3984 3985 3986 3988 3989 3990 3991 3992 3993 3994 3995 3997 3998 3999 4001 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 4064 4065 4066 4067 4068 4070 4071 4072 4074 4075 4078 4079 4081 4082 4083 4084 4085 4087 4088 4089 4091 4092 4093 4094 4095 4096 4098 4099 4100 4102 4103 4104 4105 4106 4107 4109 4110 4111 4113 4114 4115 4116 4117 4118 4120 4121 4122 4124 4125 4127 4128 4129 4130 4131 4132 4134 4135 4136 4138 4139 4140 4141 4142 4143 4145 4146 4147 4148 4150 4151 4153 4154 4155 4156 4157 4158 4160 4161 4162 4163 4165 4166 4168 4169 4170 4171 4172 4175 4176 4177 4179 4182 4183 END 4185 9.2. RDE Domain Object 4187 Copyright (c) 2019 IETF Trust and the persons identified as authors 4188 of the code. All rights reserved. 4190 Redistribution and use in source and binary forms, with or without 4191 modification, are permitted provided that the following conditions 4192 are met: 4194 o Redistributions of source code must retain the above copyright 4195 notice, this list of conditions and the following disclaimer. 4197 o Redistributions in binary form must reproduce the above copyright 4198 notice, this list of conditions and the following disclaimer in 4199 the documentation and/or other materials provided with the 4200 distribution. 4202 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4203 names of specific contributors, may be used to endorse or promote 4204 products derived from this software without specific prior written 4205 permission. 4207 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4208 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4209 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4210 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4211 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4212 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4213 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4214 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4215 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4216 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4217 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4219 BEGIN 4220 4221 4232 4233 4234 4235 4236 4237 4239 4240 4241 Registry Data Escrow Domain provisioning schema 4242 4243 4245 4248 4250 4254 4255 4256 4257 4258 4259 4261 4263 4265 4267 4269 4272 4275 4277 4280 4282 4284 4286 4288 4290 4292 4294 4296 4298 4301 4302 4303 4304 4306 4307 4308 4310 4312 4314 4316 4318 4321 4322 4324 4325 4326 4327 4328 4329 4332 4333 4334 4335 4336 4337 END 4339 9.3. CSV Domain Object 4341 Copyright (c) 2012 IETF Trust and the persons identified as authors 4342 of the code. All rights reserved. 4344 Redistribution and use in source and binary forms, with or without 4345 modification, are permitted provided that the following conditions 4346 are met: 4348 o Redistributions of source code must retain the above copyright 4349 notice, this list of conditions and the following disclaimer. 4351 o Redistributions in binary form must reproduce the above copyright 4352 notice, this list of conditions and the following disclaimer in 4353 the documentation and/or other materials provided with the 4354 distribution. 4356 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4357 names of specific contributors, may be used to endorse or promote 4358 products derived from this software without specific prior written 4359 permission. 4361 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4362 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4363 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4364 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4365 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4366 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4367 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4368 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4369 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4370 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4371 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4373 BEGIN 4374 4376 4387 4390 4392 4394 4396 4398 4400 4403 4404 4405 Domain Name Comma-Separated Values (CSV) Object 4406 4407 4409 4412 4415 4416 4417 4418 4419 4420 4421 4422 4423 4425 4428 4431 4432 4433 4434 4435 4436 4437 4438 4439 4441 4442 4445 4446 4449 4450 4451 4452 4453 4455 4456 4457 4459 4460 4463 4464 4465 4466 4467 4469 4470 4471 4473 4475 4476 4478 4479 4480 4481 4482 4484 4485 4486 4488 4489 4492 4493 4496 4497 4500 4501 4504 4505 4508 4509 4512 4513 4516 4517 4519 4520 4521 4522 4523 4525 4526 4527 4529 4530 4533 4534 4538 4539 4542 4543 4544 4545 4546 4547 4549 4550 4551 4553 4556 4557 END 4559 9.4. RDE Host Object 4561 Copyright (c) 2019 IETF Trust and the persons identified as authors 4562 of the code. All rights reserved. 4564 Redistribution and use in source and binary forms, with or without 4565 modification, are permitted provided that the following conditions 4566 are met: 4568 o Redistributions of source code must retain the above copyright 4569 notice, this list of conditions and the following disclaimer. 4571 o Redistributions in binary form must reproduce the above copyright 4572 notice, this list of conditions and the following disclaimer in 4573 the documentation and/or other materials provided with the 4574 distribution. 4576 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4577 names of specific contributors, may be used to endorse or promote 4578 products derived from this software without specific prior written 4579 permission. 4581 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4582 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4583 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4584 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4585 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4586 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4587 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4588 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4589 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4590 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4591 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4593 BEGIN 4594 4595 4603 4604 4605 4606 4607 4608 Registry Data Escrow Host provisioning schema 4609 4610 4612 4614 4615 4618 4619 4620 4621 4622 4623 4625 4627 4629 4632 4634 4636 4638 4640 4642 4644 4645 4646 4647 4649 4650 4651 4652 4653 4654 4656 4658 4659 4660 4661 4662 4663 END 4665 9.5. CSV Host Object 4667 Copyright (c) 2012 IETF Trust and the persons identified as authors 4668 of the code. All rights reserved. 4670 Redistribution and use in source and binary forms, with or without 4671 modification, are permitted provided that the following conditions 4672 are met: 4674 o Redistributions of source code must retain the above copyright 4675 notice, this list of conditions and the following disclaimer. 4677 o Redistributions in binary form must reproduce the above copyright 4678 notice, this list of conditions and the following disclaimer in 4679 the documentation and/or other materials provided with the 4680 distribution. 4682 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4683 names of specific contributors, may be used to endorse or promote 4684 products derived from this software without specific prior written 4685 permission. 4687 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4688 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4689 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4690 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4691 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4692 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4693 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4694 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4695 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4696 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4697 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4699 BEGIN 4700 4701 4710 4713 4715 4717 4719 4722 4723 4724 Host Comma-Separated Values (CSV) Object 4725 4726 4728 4731 4734 4735 4736 4737 4738 4739 4740 4741 4742 4744 4747 4749 4750 4751 4752 4753 4754 4755 4756 4757 4759 4760 4763 4764 4766 4767 4768 4769 4770 4772 4773 4774 4776 4777 4779 4780 4781 4782 4783 4785 4786 4787 4789 4790 4793 4794 4795 4796 4797 4798 4800 4801 4802 4804 4807 4808 END 4810 9.6. RDE Contact Object 4812 Copyright (c) 2019 IETF Trust and the persons identified as authors 4813 of the code. All rights reserved. 4815 Redistribution and use in source and binary forms, with or without 4816 modification, are permitted provided that the following conditions 4817 are met: 4819 o Redistributions of source code must retain the above copyright 4820 notice, this list of conditions and the following disclaimer. 4822 o Redistributions in binary form must reproduce the above copyright 4823 notice, this list of conditions and the following disclaimer in 4824 the documentation and/or other materials provided with the 4825 distribution. 4827 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4828 names of specific contributors, may be used to endorse or promote 4829 products derived from this software without specific prior written 4830 permission. 4832 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4833 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4834 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4835 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4836 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4837 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4838 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4839 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4840 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4841 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4842 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4844 BEGIN 4845 4846 4854 4855 4856 4857 4859 4860 4861 Registry Data Escrow contact provisioning schema 4862 4863 4865 4868 4870 4874 4875 4876 4877 4878 4879 4881 4883 4885 4887 4889 4891 4893 4895 4897 4899 4901 4903 4905 4907 4909 4910 4911 4912 4914 4915 4916 4917 4918 4919 4920 4921 4922 4924 4925 4926 4927 4928 4929 4932 4933 4934 4935 4936 4937 END 4939 9.7. CSV Contact Object 4941 Copyright (c) 2012 IETF Trust and the persons identified as authors 4942 of the code. All rights reserved. 4944 Redistribution and use in source and binary forms, with or without 4945 modification, are permitted provided that the following conditions 4946 are met: 4948 o Redistributions of source code must retain the above copyright 4949 notice, this list of conditions and the following disclaimer. 4951 o Redistributions in binary form must reproduce the above copyright 4952 notice, this list of conditions and the following disclaimer in 4953 the documentation and/or other materials provided with the 4954 distribution. 4956 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4957 names of specific contributors, may be used to endorse or promote 4958 products derived from this software without specific prior written 4959 permission. 4961 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4962 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4963 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4964 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4965 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4966 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4967 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4968 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4969 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4970 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4971 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4973 BEGIN 4974 4976 4985 4989 4991 4993 4995 4998 4999 5000 Contact Comma-Separated Values (CSV) Object 5001 5002 5004 5007 5010 5011 5012 5013 5014 5015 5016 5017 5018 5020 5023 5026 5027 5028 5029 5030 5031 5032 5033 5034 5036 5037 5039 5040 5041 5042 5043 5045 5046 5047 5049 5050 5054 5055 5057 5059 5060 5061 5062 5063 5065 5066 5067 5069 5070 5072 5075 5076 5078 5079 5080 5081 5082 5084 5085 5086 5088 5092 5094 5095 5096 5097 5098 5100 5101 5102 5104 5105 5106 5107 5108 5109 5111 5112 5113 5114 5116 5117 5118 5119 5120 5121 5123 5124 5125 5126 5127 5128 5131 5132 5135 5136 5137 5139 5140 5141 5142 5143 5145 5146 5147 5149 5150 5153 5154 5157 5158 5160 5161 5162 5163 5164 5166 5167 5168 5169 5171 5172 5174 5175 5176 5177 5178 5180 5181 5182 5183 5185 5186 5188 5190 5192 5194 5196 5198 5200 5202 5204 5206 5208 5210 5212 5214 5216 5218 5220 5222 5224 5226 5227 5228 5229 5230 5232 5233 5234 5236 5237 5240 5241 5242 5243 5244 5245 5247 5248 5249 5251 5254 5255 END 5257 9.8. RDE Registrar Object 5259 Copyright (c) 2019 IETF Trust and the persons identified as authors 5260 of the code. All rights reserved. 5262 Redistribution and use in source and binary forms, with or without 5263 modification, are permitted provided that the following conditions 5264 are met: 5266 o Redistributions of source code must retain the above copyright 5267 notice, this list of conditions and the following disclaimer. 5269 o Redistributions in binary form must reproduce the above copyright 5270 notice, this list of conditions and the following disclaimer in 5271 the documentation and/or other materials provided with the 5272 distribution. 5274 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5275 names of specific contributors, may be used to endorse or promote 5276 products derived from this software without specific prior written 5277 permission. 5279 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5280 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5281 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5282 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5283 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5284 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5285 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5286 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5287 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5288 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5289 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5291 BEGIN 5292 5293 5302 5303 5304 5305 5306 5308 5309 5310 Registry Data Escrow registrar provisioning schema 5311 5312 5314 5318 5320 5323 5324 5325 5326 5327 5328 5330 5332 5334 5336 5339 5341 5343 5345 5347 5349 5351 5353 5354 5355 5356 5358 5359 5360 5361 5362 5363 5365 5366 5367 5368 5369 5370 5371 5373 5374 5375 5377 5378 5381 5383 5384 5385 5386 5387 5388 5390 5391 5392 5395 5397 5400 5402 5404 5405 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5419 5420 5421 5422 5423 5425 5426 5427 5428 5429 5431 5432 5433 5435 5437 5438 5440 5441 5442 5443 5444 5445 5448 5449 5450 5451 5452 5453 END 5455 9.9. CSV Registrar Object 5457 Copyright (c) 2012 IETF Trust and the persons identified as authors 5458 of the code. All rights reserved. 5460 Redistribution and use in source and binary forms, with or without 5461 modification, are permitted provided that the following conditions 5462 are met: 5464 o Redistributions of source code must retain the above copyright 5465 notice, this list of conditions and the following disclaimer. 5467 o Redistributions in binary form must reproduce the above copyright 5468 notice, this list of conditions and the following disclaimer in 5469 the documentation and/or other materials provided with the 5470 distribution. 5472 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5473 names of specific contributors, may be used to endorse or promote 5474 products derived from this software without specific prior written 5475 permission. 5477 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5478 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5479 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5480 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5481 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5482 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5483 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5484 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5485 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5486 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5487 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5489 BEGIN 5490 5492 5502 5505 5507 5509 5511 5513 5516 5517 5518 Registar Comma-Separated Values (CSV) Object 5519 5520 5522 5525 5528 5529 5530 5531 5532 5533 5534 5535 5536 5538 5541 5544 5545 5546 5547 5548 5549 5550 5551 5552 5554 5555 5558 5559 5562 5563 5564 5565 5566 5567 5569 5570 5571 5572 5574 5575 5579 5580 5582 5584 5585 5586 5587 5588 5590 5591 5592 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5611 5612 5616 5619 5620 END 5622 9.10. RDE IDN Table Reference Objects 5624 Copyright (c) 2019 IETF Trust and the persons identified as authors 5625 of the code. All rights reserved. 5627 Redistribution and use in source and binary forms, with or without 5628 modification, are permitted provided that the following conditions 5629 are met: 5631 o Redistributions of source code must retain the above copyright 5632 notice, this list of conditions and the following disclaimer. 5634 o Redistributions in binary form must reproduce the above copyright 5635 notice, this list of conditions and the following disclaimer in 5636 the documentation and/or other materials provided with the 5637 distribution. 5639 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5640 names of specific contributors, may be used to endorse or promote 5641 products derived from this software without specific prior written 5642 permission. 5644 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5645 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5646 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5647 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5648 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5649 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5650 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5651 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5652 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5653 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5654 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5656 BEGIN 5657 5658 5664 5666 5667 5668 Registry Data Escrow IDN provisioning schema 5669 5670 5672 5674 5677 5678 5679 5680 5681 5682 5683 5684 5685 5686 5687 5688 5690 5691 5692 5693 5694 5695 5696 5698 5699 5701 5702 5703 5704 5705 5706 5707 5709 5710 END 5712 9.11. CSV IDN Language Object 5714 Copyright (c) 2012 IETF Trust and the persons identified as authors 5715 of the code. All rights reserved. 5717 Redistribution and use in source and binary forms, with or without 5718 modification, are permitted provided that the following conditions 5719 are met: 5721 o Redistributions of source code must retain the above copyright 5722 notice, this list of conditions and the following disclaimer. 5724 o Redistributions in binary form must reproduce the above copyright 5725 notice, this list of conditions and the following disclaimer in 5726 the documentation and/or other materials provided with the 5727 distribution. 5729 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5730 names of specific contributors, may be used to endorse or promote 5731 products derived from this software without specific prior written 5732 permission. 5734 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5735 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5736 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5737 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5738 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5739 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5740 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5741 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5742 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5743 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5744 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5746 BEGIN 5747 5749 5756 5759 5761 5764 5765 5766 IDN Language Comma-Separated Values (CSV) Object 5767 5768 5770 5773 5776 5777 5778 5779 5780 5781 5782 5783 5784 5786 5789 5792 5793 5794 5795 5796 5797 5798 5799 5800 5802 5805 5806 END 5808 9.12. EPP Parameters Object 5810 Copyright (c) 2019 IETF Trust and the persons identified as authors 5811 of the code. All rights reserved. 5813 Redistribution and use in source and binary forms, with or without 5814 modification, are permitted provided that the following conditions 5815 are met: 5817 o Redistributions of source code must retain the above copyright 5818 notice, this list of conditions and the following disclaimer. 5820 o Redistributions in binary form must reproduce the above copyright 5821 notice, this list of conditions and the following disclaimer in 5822 the documentation and/or other materials provided with the 5823 distribution. 5825 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5826 names of specific contributors, may be used to endorse or promote 5827 products derived from this software without specific prior written 5828 permission. 5830 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5831 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5832 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5833 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5834 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5835 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5836 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5837 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5838 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5839 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5840 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5842 BEGIN 5843 5844 5852 5853 5854 5856 5857 5858 Registry Data Escrow EPP Parameters schema 5859 5860 5862 5863 5866 5867 5870 5871 5872 5873 5874 5876 5878 5880 5883 5885 5886 5887 5888 5889 5890 END 5892 9.13. NNDN Object 5894 Copyright (c) 2019 IETF Trust and the persons identified as authors 5895 of the code. All rights reserved. 5897 Redistribution and use in source and binary forms, with or without 5898 modification, are permitted provided that the following conditions 5899 are met: 5901 o Redistributions of source code must retain the above copyright 5902 notice, this list of conditions and the following disclaimer. 5904 o Redistributions in binary form must reproduce the above copyright 5905 notice, this list of conditions and the following disclaimer in 5906 the documentation and/or other materials provided with the 5907 distribution. 5909 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5910 names of specific contributors, may be used to endorse or promote 5911 products derived from this software without specific prior written 5912 permission. 5914 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5915 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5916 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5917 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5918 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5919 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5920 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5921 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5922 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5923 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5924 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5926 BEGIN 5927 5928 5936 5937 5938 5940 5941 5942 Registry Data Escrow NNDN provisioning schema 5943 5944 5946 5948 5949 5952 5953 5954 5955 5956 5957 5959 5961 5963 5965 5967 5969 5970 5971 5972 5974 5975 5976 5977 5978 5979 5980 5982 5983 5984 5985 5987 5988 5989 5991 5992 5993 5994 5995 5996 5999 6000 6001 6002 6003 6004 END 6006 9.14. CSV NNDN Object 6008 Copyright (c) 2013 IETF Trust and the persons identified as authors 6009 of the code. All rights reserved. 6011 Redistribution and use in source and binary forms, with or without 6012 modification, are permitted provided that the following conditions 6013 are met: 6015 o Redistributions of source code must retain the above copyright 6016 notice, this list of conditions and the following disclaimer. 6018 o Redistributions in binary form must reproduce the above copyright 6019 notice, this list of conditions and the following disclaimer in 6020 the documentation and/or other materials provided with the 6021 distribution. 6023 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6024 names of specific contributors, may be used to endorse or promote 6025 products derived from this software without specific prior written 6026 permission. 6028 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6029 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6030 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6031 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6032 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6033 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6034 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6035 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6036 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6037 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6038 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6040 BEGIN 6041 6043 6051 6054 6056 6058 6061 6062 6063 NNDN (NNDN's not domain name) (CSV) Object 6064 6065 6067 6070 6073 6074 6075 6076 6077 6078 6079 6080 6081 6082 6085 6088 6089 6090 6091 6092 6093 6094 6095 6096 6098 6099 6102 6103 6106 6107 6111 6112 6115 6116 6117 6118 6119 6121 6122 6123 6125 6126 6129 6132 6133 END 6135 9.15. Policy Object 6137 Copyright (c) 2019 IETF Trust and the persons identified as authors 6138 of the code. All rights reserved. 6140 Redistribution and use in source and binary forms, with or without 6141 modification, are permitted provided that the following conditions 6142 are met: 6144 o Redistributions of source code must retain the above copyright 6145 notice, this list of conditions and the following disclaimer. 6147 o Redistributions in binary form must reproduce the above copyright 6148 notice, this list of conditions and the following disclaimer in 6149 the documentation and/or other materials provided with the 6150 distribution. 6152 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6153 names of specific contributors, may be used to endorse or promote 6154 products derived from this software without specific prior written 6155 permission. 6157 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6158 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6159 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6160 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6161 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6162 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6163 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6164 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6165 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6166 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6167 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6169 BEGIN 6170 6171 6177 6178 6179 Registry Data Escrow Policy schema 6180 6181 6183 6184 6187 6188 6189 6190 6191 6192 6193 6194 6195 6196 END 6198 9.16. Header Object 6200 Copyright (c) 2019 IETF Trust and the persons identified as authors 6201 of the code. All rights reserved. 6203 Redistribution and use in source and binary forms, with or without 6204 modification, are permitted provided that the following conditions 6205 are met: 6207 o Redistributions of source code must retain the above copyright 6208 notice, this list of conditions and the following disclaimer. 6210 o Redistributions in binary form must reproduce the above copyright 6211 notice, this list of conditions and the following disclaimer in 6212 the documentation and/or other materials provided with the 6213 distribution. 6215 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6216 names of specific contributors, may be used to endorse or promote 6217 products derived from this software without specific prior written 6218 permission. 6220 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6221 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6222 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6223 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6224 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6225 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6226 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6227 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6228 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6229 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6230 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6232 BEGIN 6233 6234 6241 6242 6244 6245 6246 Data Escrow Deposit Header schema 6247 6248 6250 6251 6254 6255 6256 6257 6258 6259 6260 6262 6264 6266 6267 6268 6270 6271 6272 6273 6274 6275 6276 6277 6279 6280 6281 6282 6283 6284 6285 6286 6287 6289 6290 END 6292 10. Internationalization Considerations 6294 Data Escrow deposits are represented in XML, which provides native 6295 support for encoding information using the Unicode character set and 6296 its more compact representations including UTF-8. Conformant XML 6297 processors recognize both UTF-8 and UTF-16. Though XML includes 6298 provisions to identify and use other character encodings through use 6299 of an "encoding" attribute in an declaration, use of UTF-8 is 6300 RECOMMENDED. 6302 11. IANA Considerations 6304 This document uses URNs to describe XML namespaces and XML schemas 6305 conforming to a registry mechanism described in [RFC3688]. Fourteen 6306 URI assignments have been registered by the IANA. 6308 Registration request for the RDE CSV namespace: 6310 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6312 Registrant Contact: See the "Author's Address" section of this 6313 document. 6315 XML: None. Namespace URIs do not represent an XML specification. 6317 Registration request for the RDE CSV XML schema: 6319 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6321 Registrant Contact: See the "Author's Address" section of this 6322 document. 6324 See the "Formal Syntax" section of this document. 6326 Registration request for the RDE domain namespace: 6328 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6330 Registrant Contact: See the "Author's Address" section of this 6331 document. 6333 XML: None. Namespace URIs do not represent an XML specification. 6335 Registration request for the RDE domain XML schema: 6337 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6339 Registrant Contact: See the "Author's Address" section of this 6340 document. 6342 See the "Formal Syntax" section of this document. 6344 Registration request for the CSV domain namespace: 6346 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6348 Registrant Contact: See the "Author's Address" section of this 6349 document. 6351 XML: None. Namespace URIs do not represent an XML specification. 6353 Registration request for the CSV domain XML schema: 6355 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6357 Registrant Contact: See the "Author's Address" section of this 6358 document. 6360 See the "Formal Syntax" section of this document. 6362 Registration request for the RDE host namespace: 6364 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6366 Registrant Contact: See the "Author's Address" section of this 6367 document. 6369 XML: None. Namespace URIs do not represent an XML specification. 6371 Registration request for the RDE host XML schema: 6373 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6375 Registrant Contact: See the "Author's Address" section of this 6376 document. 6378 See the "Formal Syntax" section of this document. 6380 Registration request for the CSV host namespace: 6382 URI: urn:ietf:params:xml:ns:csvHost-1.0 6384 Registrant Contact: See the "Author's Address" section of this 6385 document. 6387 XML: None. Namespace URIs do not represent an XML specification. 6389 Registration request for the CSV host XML schema: 6391 URI: urn:ietf:params:xml:schema:csvHost-1.0 6393 Registrant Contact: See the "Author's Address" section of this 6394 document. 6396 See the "Formal Syntax" section of this document. 6398 Registration request for the RDE contact namespace: 6400 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6402 Registrant Contact: See the "Author's Address" section of this 6403 document. 6405 XML: None. Namespace URIs do not represent an XML specification. 6407 Registration request for the RDE contact XML schema: 6409 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6410 Registrant Contact: See the "Author's Address" section of this 6411 document. 6413 See the "Formal Syntax" section of this document. 6415 Registration request for the CSV contact namespace: 6417 URI: urn:ietf:params:xml:ns:csvContact-1.0 6419 Registrant Contact: See the "Author's Address" section of this 6420 document. 6422 XML: None. Namespace URIs do not represent an XML specification. 6424 Registration request for the CSV contact XML schema: 6426 URI: urn:ietf:params:xml:schema:csvContact-1.0 6428 Registrant Contact: See the "Author's Address" section of this 6429 document. 6431 See the "Formal Syntax" section of this document. 6433 Registration request for the RDE registrar namespace: 6435 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6437 Registrant Contact: See the "Author's Address" section of this 6438 document. 6440 XML: None. Namespace URIs do not represent an XML specification. 6442 Registration request for the RDE registrar XML schema: 6444 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6446 Registrant Contact: See the "Author's Address" section of this 6447 document. 6449 See the "Formal Syntax" section of this document. 6451 Registration request for the CSV registrar namespace: 6453 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6455 Registrant Contact: See the "Author's Address" section of this 6456 document. 6458 XML: None. Namespace URIs do not represent an XML specification. 6460 Registration request for the CSV registrar XML schema: 6462 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6464 Registrant Contact: See the "Author's Address" section of this 6465 document. 6467 See the "Formal Syntax" section of this document. 6469 Registration request for the RDE IDN namespace: 6471 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6473 Registrant Contact: See the "Author's Address" section of this 6474 document. 6476 XML: None. Namespace URIs do not represent an XML specification. 6478 Registration request for the RDE IDN XML schema: 6480 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6482 Registrant Contact: See the "Author's Address" section of this 6483 document. 6485 See the "Formal Syntax" section of this document. 6487 Registration request for the CSV IDN namespace: 6489 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6491 Registrant Contact: See the "Author's Address" section of this 6492 document. 6494 XML: None. Namespace URIs do not represent an XML specification. 6496 Registration request for the CSV IDN XML schema: 6498 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6500 Registrant Contact: See the "Author's Address" section of this 6501 document. 6503 See the "Formal Syntax" section of this document. 6505 Registration request for the RDE NNDN namespace: 6507 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6509 Registrant Contact: See the "Author's Address" section of this 6510 document. 6512 XML: None. Namespace URIs do not represent an XML specification. 6514 Registration request for the RDE NNDN XML schema: 6516 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6518 Registrant Contact: See the "Author's Address" section of this 6519 document. 6521 See the "Formal Syntax" section of this document. 6523 Registration request for the CSV NNDN namespace: 6525 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6527 Registrant Contact: See the "Author's Address" section of this 6528 document. 6530 XML: None. Namespace URIs do not represent an XML specification. 6532 Registration request for the CSV NNDN XML schema: 6534 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6536 Registrant Contact: See the "Author's Address" section of this 6537 document. 6539 See the "Formal Syntax" section of this document. 6541 Registration request for the RDE EPP parameters namespace: 6543 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6545 Registrant Contact: See the "Author's Address" section of this 6546 document. 6548 XML: None. Namespace URIs do not represent an XML specification. 6550 Registration request for the RDE EPP parameters XML schema: 6552 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6553 Registrant Contact: See the "Author's Address" section of this 6554 document. 6556 See the "Formal Syntax" section of this document. 6558 12. Implementation Status 6560 Note to RFC Editor: Please remove this section and the reference to 6561 RFC 7942 [RFC7942] before publication. 6563 This section records the status of known implementations of the 6564 protocol defined by this specification at the time of posting of this 6565 Internet-Draft, and is based on a proposal described in RFC 7942 6566 [RFC7942]. The description of implementations in this section is 6567 intended to assist the IETF in its decision processes in progressing 6568 drafts to RFCs. Please note that the listing of any individual 6569 implementation here does not imply endorsement by the IETF. 6570 Furthermore, no effort has been spent to verify the information 6571 presented here that was supplied by IETF contributors. This is not 6572 intended as, and must not be construed to be, a catalog of available 6573 implementations or their features. Readers are advised to note that 6574 other implementations may exist. 6576 According to RFC 7942 [RFC7942], "this will allow reviewers and 6577 working groups to assign due consideration to documents that have the 6578 benefit of running code, which may serve as evidence of valuable 6579 experimentation and feedback that have made the implemented protocols 6580 more mature. It is up to the individual working groups to use this 6581 information as they see fit". 6583 12.1. Implementation in the gTLD space 6585 Organization: ICANN 6587 Name: ICANN Registry Agreement 6589 Description: the ICANN Base Registry Agreement requires Registries, 6590 Data Escrow Agents, and ICANN to implement this specification. ICANN 6591 receives daily notifications from Data Escrow Agents confirming that 6592 more than 1,200 gTLDs are sending deposits that comply with this 6593 specification. ICANN receives on a weekly basis per gTLD, from more 6594 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6595 also complies with this specification. In addition, ICANN is aware 6596 of Registry Service Provider transitions using data files that 6597 conform to this specification. 6599 Level of maturity: production. 6601 Coverage: all aspects of this specification are implemented. 6603 Version compatibility: versions 03 - 08 are known to be implemented. 6605 Contact: gustavo.lozano@icann.org 6607 URL: https://www.icann.org/resources/pages/registries/registries- 6608 agreements-en 6610 13. Security Considerations 6612 This specification does not define the security mechanisms to be used 6613 in the transmission of the data escrow deposits, since it only 6614 specifies the minimum necessary to enable the rebuilding of a 6615 Registry from deposits without intervention from the original 6616 Registry. 6618 Depending on local policies, some elements or most likely, the whole 6619 deposit will be considered confidential. As such the Registry 6620 transmitting the data to the Escrow Agent SHOULD take all the 6621 necessary precautions like encrypting the data itself and/or the 6622 transport channel to avoid inadvertent disclosure of private data. 6624 It is also of the utmost importance the authentication of the parties 6625 passing data escrow deposit files. The Escrow Agent SHOULD properly 6626 authenticate the identity of the Registry before accepting data 6627 escrow deposits. In a similar manner, the Registry SHOULD 6628 authenticate the identity of the Escrow Agent before submitting any 6629 data. 6631 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6632 checking mechanisms to ensure the data transmitted is what the source 6633 intended. Validation of the contents by the Escrow Agent is 6634 RECOMMENDED to ensure not only the file was transmitted correctly 6635 from the Registry, but also the contents are also "meaningful". 6637 14. Privacy Considerations 6639 This specification defines a format that may be used to escrow 6640 personal data. The process of data escrow is governed by a legal 6641 document agreed by the parties, and such legal document must regulate 6642 the particularities regarding the protection of personal data. 6644 15. Acknowledgments 6646 Parts of this document are based on EPP [RFC5730] and related RFCs by 6647 Scott Hollenbeck. 6649 Special suggestions that have been incorporated into this document 6650 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6651 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6652 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6653 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6654 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6655 Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. 6657 Shoji Noguchi and Francisco Arias participated as co-authors until 6658 version 05 providing invaluable support for this document. 6660 16. Change History 6662 [[RFC Editor: Please remove this section.]] 6664 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6665 dnrd-objects-mapping-00 6667 1. Added definition for child elements under the element. 6669 2. Added definition for child elements under the element. 6671 3. Added definition for child elements under the element. 6673 4. Rewrote the IDN Variants Handling section to use the variant 6674 states as described in ICANN's Study of Issues Related to the 6675 Management of IDN Variant TLDs. 6677 5. Renamed to in the . 6679 6. Renamed to in the element. 6681 7. Renamed to in the element. 6683 8. Added element under element. 6685 9. Fixed some typographical errors and omissions. 6687 16.2. Changes from 00 to 01 6689 1. Specify OPTIONAL elements in the draft. 6691 2. Added NNDN object to support list of reserved names and different 6692 IDN variants models. 6694 3. Removed subordinated host element from the domain object. 6696 4. Added eppParams object. 6698 5. Added variantGenerator element to the domain object. 6700 6. Added lgr to the IDN table object. 6702 16.3. Changes from 01 to 02 6704 1. Updates to the all objects based on feedback from the list. 6706 2. Start of XML and CSV drafts merge. 6708 3. Added header object. 6710 4. Added report object. 6712 5. Added notification object. 6714 6. Added Data Escrow Agent Extended Verification Process section. 6716 7. Added Notifications from Registries to Third Parties. 6718 8. Added Notifications from Data Escrow Agents to Third Parties. 6720 9. Added FULL, DIFF deposit examples using the XML model only. 6722 16.4. Changes from 02 to 03 6724 1. Remove authinfo from the XML Schema. 6726 2. Resend attribute is now an element 6728 3. Scope attribute added to policy object. 6730 16.5. Changes from 03 to 04 6732 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6733 arias-noguchi-dnrd-objects-mapping-02. 6735 2. Changed the cksum attribute of to use CRC32 and 6736 changed all of the sample cksum values to use CRC32, based on 6737 feedback from David Kipling. 6739 3. Changed the optional element to be an optional 6740 "sep" attribute value of the element with a default 6741 value of "," based on feedback from David Kipling. 6743 4. Added support for the optional "parent" attribute for the to the 6744 CSV fields to indicate a field as a reference to a parent 6745 object, based on feedback from David Kipling. 6747 5. Added support for the CSV model for the NNDN. 6749 6. Added support to delete hosts based on roid. 6751 7. Added mirrored state to NNDN 6753 8. Minor fixes to XML XSDs. 6755 9. The Report and Notification objects were moved to draft-lozano- 6756 icann-registry-interfaces 6758 10. The section Data escrow notifications was moved to draft-lozano- 6759 icann-registry-interfaces 6761 11. Removed references to the , , and 6762 from the "hostStatuses" and "hostAddresses" CSV 6763 files. 6765 12. Removed references to the , , and 6766 from the "contactStatuses" CSV file. 6768 13. Removed references to the , , and 6769 from the "domainContacts", "domainStatuses", 6770 and "domainNameServers" CSV files. 6772 14. Changed to . 6774 15. Replaced use of to new field 6775 in the "domain", "idnLanguage", and "NNDN" CSV files. 6777 16. Replaced use of with in the 6778 "host" element. 6780 17. Changed the foreign key of the hosts to use 6781 instead of and removed use of in 6782 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6783 files. 6785 18. Added use of the MUST keyword for CSV fields that are required 6786 to be supported in an EPP based system. 6788 19. Removed use of the field element for the 6789 "registrar" CSV file. 6791 20. Added definition of field element. 6793 16.6. Changes from 04 to 05 6795 1. Updated the examples of the full and differential deposits using 6796 the CSV and XML model. 6798 2. Made optional for the "domainTransfer" CSV file 6799 to match the XML definition. 6801 3. Made optional for the "domain" CSV file 6802 to match the XML definition. 6804 4. Made optional for the "domain" and "contact" CSV 6805 files to match the XML definition. 6807 5. Change from IDREF to idType. 6809 6. Minor editorial changes. 6811 16.7. Changes from 05 to 06 6813 1. Revised the differential and incremental deposits for the CSV 6814 format to use cascade update / replace and delete from the parent 6815 object to be consistent with the XML format. 6817 2. Revised the structure of the CSV format sections to utilize sub- 6818 sections instead of a list for the CSV file definitions. 6820 3. Added the "CSV Parent Child Relationship" section to describe the 6821 concept of parent child relationships across CSV file 6822 definitions. 6824 4. Added the "domainNameServersAddresses" CSV File Definition 6825 section to support the domain host attributes model of [RFC5731]. 6827 5. Made the required fields in the CSV format consistent with the 6828 XML format. The CSV fields updated to be required include: 6829 , , , 6830 , , , 6831 , , , 6832 , , , 6833 , , 6834 , , , 6835 , , 6836 , and . 6838 6. Revised the CSV examples to use a more realistic set of records. 6840 16.8. Changes from 06 to 07 6842 1. Created "repositoryTypeGroup" group element in the rdeHeader 6843 including the , and 6844 elements. 6846 2. Added the optional "rcdn" and "registrarId" attributes to the 6847 element 6849 16.9. Changes from 07 to 08 6851 1. The following registrar elements were made optional to support 6852 greater flexibility for the implementation of policies: status, 6853 postalInfo, email and crDate. 6855 2. The following domain name elements were made optional to support 6856 greater flexibility for the implementation of policies: crRr. 6858 16.10. Changes from 08 to 09 6860 1. Implementation Status section was added 6862 16.11. Changes from 09 to 10 6864 1. Editorial changes in section Section 5.1.2.1.6. 6866 2. Added MAY clause when the DS Data Interface is used in section 6867 Section 5.1.2.1.6. 6869 16.12. Changes from 10 to REGEXT 00 6871 1. Internet Draft (I-D) adopted by the REGEXT WG. 6873 16.13. Changes REGEXT 00 to REGEXT 01 6875 1. Added the element to the 6876 "repositoryTypeGroup" group element in the rdeHeader. 6878 2. Privacy consideration section was added 6880 3. Updates on section 8 6882 16.14. Changes REGEXT 01 to REGEXT 02 6884 1. Added a choice between the use of the or 6885 fields in the CSV "domain", "host", and 6886 "contact" definitions. 6888 2. Added a choice between the use of the or 6889 fields in the CSV "domainNameServers" 6890 definition. 6892 3. Changed "of client" to "of the client" throughout the document. 6894 4. Modified all references of 'The attribute isRequired MUST equal 6895 "true".' to 'The attribute "isRequired" MUST equal "true".' 6897 5. Combined the and 6898 fields in a single required list for the CSV "domainContacts" 6899 definition. 6901 6. Combined the , , and 6902 fields in a single required list for the 6903 CSV "domainStatuses" definition. 6905 7. Moved the the fields to the MAY 6906 list for the CSV "domain", "host", and "contact" definitions. 6908 8. Made the order of the , , 6909 , and fields more consistent in the 6910 CSV lists. 6912 9. Fixed an error in the order of the object example. 6914 10. Changed to be optional to match being 6915 optional in the XML model, by having it use type 6916 rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and 6917 ensuring that is included in the MAY field 6918 lists and not the MUST field lists. 6920 11. Made optional for the "domain" CSV definition 6921 to be consistent with the XML model, by removing the sentence 6922 'The attribute "isRequired" MUST equal "true".' from the 6923 description and moving the field to the MAY field list. 6925 12. Made optional for the "domain" and "contact" 6926 CSV definitions to be consistent with the XML model, by moving 6927 the field to the MAY field list. 6929 13. Made optional to be consistent with the XML 6930 model, by having it use type rdeCsv:fClIDType instead of 6931 rdeCsv:fClIDRequiredType. 6933 14. Made required to be consistent with the XML 6934 model, by having it use type rdeCsv:fClIDRequiredType instead of 6935 rdeCsv:fClIDType. 6937 15. Made the field in the "host", "contact", 6938 and "registrar" CSV definitions required explicitly by removing 6939 'and isRequired="true"' and adding the sentence 'The attribute 6940 isRequired MUST equal "true".', when it is chosen as the primary 6941 field. 6943 16. Removed extra '/>.' at the end of the field 6944 description in the "hostStatuses" CSV definition. 6946 17. Made the field optional to be consistent 6947 with the XML model, by having csvRegistrar:fStatusType extend 6948 rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType. 6950 18. Made the field for the "registrar" CSV 6951 definition explicitly optional to be consistent with the XML 6952 model, by adding the sentence 'The attribute isRequired MUST 6953 equal "false".' to the field description and including the 6954 definition of isRequired="false" in the "registrar" CSV 6955 definition examples. 6957 19. Added the choice between the use of the and 6958 fields in the deletes "registrar" CSV 6959 definition to be consistent with the "registrar" CSV definition. 6961 20. Made the and elements optional for the host and 6962 contact objects in the XML model to be consistent with the 6963 domain object. 6965 16.15. Changes REGEXT 02 to REGEXT 03 6967 1. Added the optional element contentTag in the header object. 6969 2. Editorial updates 6971 17. Example of a full deposit using the XML model 6973 Example of a full deposit using the XML model: 6975 6976 6992 2010-10-17T00:00:00Z 6993 6994 1.0 6995 urn:ietf:params:xml:ns:rdeHeader-1.0 6996 6997 urn:ietf:params:xml:ns:rdeContact-1.0 6998 6999 urn:ietf:params:xml:ns:rdeHost-1.0 7000 7001 urn:ietf:params:xml:ns:rdeDomain-1.0 7002 7003 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7004 7005 urn:ietf:params:xml:ns:rdeIDN-1.0 7006 7007 urn:ietf:params:xml:ns:rdeNNDN-1.0 7008 7009 urn:ietf:params:xml:ns:rdeEppParams-1.0 7010 7011 7013 7014 7015 7016 7017 test 7018 2 7020 7021 1 7023 7024 1 7026 7027 1 7029 7030 1 7032 7034 1 7036 7037 1 7039 7040 7042 7043 7044 example1.test 7045 Dexample1-TEST 7046 7047 jd1234 7048 sh8013 7049 sh8013 7050 7051 ns1.example.com 7052 ns1.example1.test 7053 7054 RegistrarX 7055 RegistrarX 7056 1999-04-03T22:00:00.0Z 7057 2015-04-03T22:00:00.0Z 7058 7060 7061 7062 example2.test 7063 Dexample2-TEST 7064 7065 7066 jd1234 7067 sh8013 7068 sh8013 7069 RegistrarX 7070 RegistrarX 7071 1999-04-03T22:00:00.0Z 7072 2015-04-03T22:00:00.0Z 7073 7075 7076 7077 ns1.example1.test 7078 Hns1_example_test-TEST 7079 7080 7081 192.0.2.2 7082 192.0.2.29 7083 1080:0:0:0:8:800:200C:417A 7084 7085 RegistrarX 7086 RegistrarX 7087 1999-05-08T12:10:00.0Z 7088 RegistrarX 7089 2009-10-03T09:34:00.0Z 7090 7092 7093 7094 sh8013 7095 Csh8013-TEST 7096 7097 7098 7099 John Doe 7100 Example Inc. 7101 7102 123 Example Dr. 7103 Suite 100 7104 Dulles 7105 VA 7106 20166-6503 7107 US 7108 7109 7110 +1.7035555555 7111 7112 +1.7035555556 7113 7114 jdoe@example.test 7115 7116 RegistrarX 7117 RegistrarX 7118 7119 2009-09-13T08:01:00.0Z 7120 7121 RegistrarX 7122 7123 2009-11-26T09:10:00.0Z 7124 7125 2009-12-03T09:05:00.0Z 7126 7127 7128 7129 7131 7132 7134 7135 7136 RegistrarX 7137 Registrar X 7138 123 7139 ok 7140 7141 7142 123 Example Dr. 7143 7144 Suite 100 7145 7146 Dulles 7147 VA 7148 20166-6503 7149 US 7150 7151 7152 +1.7035555555 7153 7154 +1.7035555556 7155 7156 jdoe@example.test 7157 7158 http://www.example.test 7159 7160 7161 whois.example.test 7162 7163 http://whois.example.test 7164 7165 7166 2005-04-23T11:49:00.0Z 7167 7168 2009-02-17T17:51:00.0Z 7169 7170 7172 7173 7174 7175 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 7176 7177 7178 http://registro.br/dominio/regras.html 7180 7181 7183 7184 7185 xn--exampl-gva.test 7186 pt-BR 7187 example1.test 7188 withheld 7189 2005-04-23T11:49:00.0Z 7190 7192 7193 7194 1.0 7195 en 7196 7197 urn:ietf:params:xml:ns:domain-1.0 7198 7199 7200 urn:ietf:params:xml:ns:contact-1.0 7201 7202 7203 urn:ietf:params:xml:ns:host-1.0 7204 7205 7206 urn:ietf:params:xml:ns:rgp-1.0 7207 7208 urn:ietf:params:xml:ns:secDNS-1.1 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7229 7232 7233 7235 18. Example of differential deposit using the XML model 7237 Example of a differential deposit using the XML model: 7239 7240 7255 2010-10-17T00:00:00Z 7256 7257 1.0 7258 urn:ietf:params:xml:ns:rdeHeader-1.0 7259 7260 urn:ietf:params:xml:ns:rdeContact-1.0 7261 7262 urn:ietf:params:xml:ns:rdeHost-1.0 7263 7264 urn:ietf:params:xml:ns:rdeDomain-1.0 7265 7266 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7267 7268 urn:ietf:params:xml:ns:rdeIDN-1.0 7269 7270 urn:ietf:params:xml:ns:rdeNNDN-1.0 7271 7272 urn:ietf:params:xml:ns:rdeEppParams-1.0 7273 7274 7276 7277 7278 7279 example2.test 7280 7281 7283 7284 7285 7286 7287 test 7288 1 7290 7291 1 7293 7294 1 7296 7297 1 7299 7300 1 7302 7303 1 7305 7306 1 7308 7309 7310 7311 7313 19. Example of a full deposit using the CSV model 7315 Example of a full deposit using the CSV model: 7317 7318 7332 2010-10-18T00:00:00Z 7333 7334 1.0 7335 urn:ietf:params:xml:ns:csvDomain-1.0 7336 urn:ietf:params:xml:ns:csvHost-1.0 7337 urn:ietf:params:xml:ns:csvContact-1.0 7338 urn:ietf:params:xml:ns:csvRegistrar-1.0 7339 urn:ietf:params:xml:ns:csvIDN-1.0 7340 urn:ietf:params:xml:ns:csvNNDN-1.0 7341 urn:ietf:params:xml:ns:rdeEppParams-1.0 7342 7343 7344 7345 test 7346 7347 4 7348 7349 7350 6 7351 7352 7353 9 7354 7355 7356 3 7357 7358 7359 2 7360 7361 7362 2 7363 7364 7365 1 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7388 domain-YYYYMMDD.csv 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7401 domainContacts-YYYYMMDD.csv 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7416 domainStatuses-YYYYMMDD.csv 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7428 domainNameServers-name-YYYYMMDD.csv 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7440 domainNameServers-roid-YYYYMMDD.csv 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7456 dnssec-ds-YYYYMMDD.csv 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7472 dnssec-key-YYYYMMDD.csv 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7491 domainTransfer-YYYYMMDD.csv 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7513 host-YYYYMMDD.csv 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7527 hostStatuses-YYYYMMDD.csv 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7540 hostAddresses-YYYYMMDD.csv 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7566 contact-YYYYMMDD.csv 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7580 contactStatuses-YYYYMMDD.csv 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7601 contactPostal-YYYYMMDD.csv 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7619 contactTransfer-YYYYMMDD.csv 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7640 contactDisclose-YYYYMMDD.csv 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7672 registrar-YYYYMMDD.csv 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7686 idnLanguage-YYYYMMDD.csv 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7704 NNDN-YYYYMMDD.csv 7705 7706 7707 7708 7709 7710 1.0 7711 en 7712 urn:ietf:params:xml:ns:domain-1.0 7713 7714 urn:ietf:params:xml:ns:host-1.0 7715 7716 urn:ietf:params:xml:ns:contact-1.0 7717 7718 7719 urn:ietf:params:xml:ns:secDNS-1.1 7720 7721 urn:ietf:params:xml:ns:rgp-1.0 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7748 20. Example of differential deposit using the CSV model 7750 Example of a differential deposit using the CSV model: 7752 7753 7767 2010-10-18T00:00:00Z 7768 7769 1.0 7770 urn:ietf:params:xml:ns:csvDomain-1.0 7771 urn:ietf:params:xml:ns:csvHost-1.0 7772 urn:ietf:params:xml:ns:csvContact-1.0 7773 urn:ietf:params:xml:ns:csvRegistrar-1.0 7774 urn:ietf:params:xml:ns:csvIDN-1.0 7775 7776 7777 7778 7779 7780 7781 7782 7783 7785 domain-delete-YYYYMMDD.csv 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7798 host-delete-YYYYMMDD.csv 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7811 contact-delete-YYYYMMDD.csv 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7824 registrar-delete-YYYYMMDD.csv 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7837 idnLanguage-delete-YYYYMMDD.csv 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7850 NNDN-delete-YYYYMMDD.csv 7851 7852 7854 7855 7856 7857 7858 7859 test 7860 7861 2 7862 7863 7864 2 7865 7866 7867 3 7868 7869 7870 1 7871 7872 7873 1 7874 7875 7876 1 7877 7878 7879 1 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7902 domain-YYYYMMDD.csv 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7915 domainContacts-YYYYMMDD.csv 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7930 domainStatuses-YYYYMMDD.csv 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7942 domainNameServers-name-YYYYMMDD.csv 7943 7944 7945 7946 7947 7948 7949 7951 7952 7953 7955 domainNameServers-roid-YYYYMMDD.csv 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7971 dnssec-ds-YYYYMMDD.csv 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7987 dnssec-key-YYYYMMDD.csv 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8006 domainTransfer-YYYYMMDD.csv 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8028 host-YYYYMMDD.csv 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8042 hostStatuses-YYYYMMDD.csv 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8055 hostAddresses-YYYYMMDD.csv 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8081 contact-YYYYMMDD.csv 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8095 contactStatuses-YYYYMMDD.csv 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8116 contactPostal-YYYYMMDD.csv 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8134 contactTransfer-YYYYMMDD.csv 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8155 contactDisclose-YYYYMMDD.csv 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8187 registrar-YYYYMMDD.csv 8188 8189 8190 8192 8193 8194 8195 8196 8197 8198 8199 8200 8202 idnLanguage-YYYYMMDD.csv 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8220 NNDN-YYYYMMDD.csv 8221 8222 8223 8224 8225 8226 1.0 8227 en 8228 urn:ietf:params:xml:ns:domain-1.0 8229 8230 urn:ietf:params:xml:ns:host-1.0 8231 8232 urn:ietf:params:xml:ns:contact-1.0 8233 8234 8235 urn:ietf:params:xml:ns:secDNS-1.1 8236 8237 urn:ietf:params:xml:ns:rgp-1.0 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8264 21. References 8266 21.1. Normative References 8268 [ISO-3166-1] 8269 3166, I. S., "Codes for the representation of names of 8270 countries and their subdivisions -- Part 1: Country 8271 codes", ISO Standard 3166, November 2006. 8273 [ITU-E164] 8274 International Telecommunication Union, "The international 8275 public telecommunication numbering plan", ITU-T 8276 Recommendation E.164, February 2005. 8278 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8279 Requirement Levels", BCP 14, RFC 2119, 8280 DOI 10.17487/RFC2119, March 1997, 8281 . 8283 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8284 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8285 . 8287 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8288 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8289 DOI 10.17487/RFC3915, September 2004, 8290 . 8292 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8293 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8294 . 8296 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8297 Domain Name Mapping", STD 69, RFC 5731, 8298 DOI 10.17487/RFC5731, August 2009, 8299 . 8301 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8302 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8303 August 2009, . 8305 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8306 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8307 August 2009, . 8309 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8310 Security Extensions Mapping for the Extensible 8311 Provisioning Protocol (EPP)", RFC 5910, 8312 DOI 10.17487/RFC5910, May 2010, 8313 . 8315 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 8316 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 8317 May 2017, . 8319 21.2. Informative References 8321 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8322 DOI 10.17487/RFC0791, September 1981, 8323 . 8325 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8326 DOI 10.17487/RFC3688, January 2004, 8327 . 8329 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8330 DOI 10.17487/RFC3912, September 2004, 8331 . 8333 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8334 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8335 2006, . 8337 [RFC5891] Klensin, J., "Internationalized Domain Names in 8338 Applications (IDNA): Protocol", RFC 5891, 8339 DOI 10.17487/RFC5891, August 2010, 8340 . 8342 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8343 Code: The Implementation Status Section", BCP 205, 8344 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8345 . 8347 [variantTLDsReport] 8348 Internet Corporation for Assigned Names and Numbers 8349 (ICANN), "A Study of Issues Related to the Management of 8350 IDN Variant TLDs", February 2012, 8351 . 8354 21.3. URIs 8356 [1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data- 8357 escrow-05.txt 8359 Authors' Addresses 8361 Gustavo Lozano 8362 Internet Corporation for Assigned Names and Numbers 8363 12025 Waterfront Drive, Suite 300 8364 Los Angeles 90292 8365 United States of America 8367 Phone: +1.310.823.9358 8368 Email: gustavo.lozano@icann.org 8370 James Gould 8371 VeriSign, Inc. 8372 12061 Bluemont Way 8373 Reston 20190 8374 United States of America 8376 Email: jgould@verisign.com 8377 Chethan Thippeswamy 8378 VeriSign, Inc. 8379 12061 Bluemont Way 8380 Reston 20190 8381 United States of America 8383 Email: cthippeswamy@verisign.com