idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-00.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 (Jun 18, 2019) is 1767 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 8194 -- 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: December 20, 2019 C. Thippeswamy 6 VeriSign 7 Jun 18, 2019 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-00 12 Abstract 14 This document specifies the format, contents and semantics of Domain 15 Name Registration Data (DNRD) Escrow deposits for a Domain Name 16 Registry. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on December 20, 2019. 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 . . . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . . . . 60 69 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 68 70 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 72 71 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 77 72 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 79 73 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 79 74 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 82 75 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 76 8. Data escrow agent extended verification process . . . . . . . 83 77 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 84 78 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 84 79 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 94 80 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 97 81 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 101 82 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 104 83 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 107 84 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 110 85 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116 86 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 120 87 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 124 88 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 126 89 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 128 90 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 130 91 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 132 92 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 135 93 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 136 94 10. Internationalization Considerations . . . . . . . . . . . . . 138 95 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 138 96 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 144 97 12.1. Implementation in the gTLD space . . . . . . . . . . . . 144 99 13. Security Considerations . . . . . . . . . . . . . . . . . . . 145 100 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 145 101 15. Change History . . . . . . . . . . . . . . . . . . . . . . . 145 102 15.1. Changes from draft-arias-noguchi-registry-data-escrow-02 103 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 146 104 15.2. Changes from version 00 to 01 . . . . . . . . . . . . . 146 105 15.3. Changes from version 01 to 02 . . . . . . . . . . . . . 146 106 15.4. Changes from version 02 to 03 . . . . . . . . . . . . . 147 107 15.5. Changes from version 03 to 04 . . . . . . . . . . . . . 147 108 15.6. Changes from version 04 to 05 . . . . . . . . . . . . . 148 109 15.7. Changes from version 05 to 06 . . . . . . . . . . . . . 149 110 15.8. Changes from version 06 to 07 . . . . . . . . . . . . . 149 111 15.9. Changes from version 07 to 08 . . . . . . . . . . . . . 149 112 15.10. Changes from version 08 to 09 . . . . . . . . . . . . . 150 113 15.11. Changes from version 09 to 10 . . . . . . . . . . . . . 150 114 15.12. Changes from version 10 to 00 . . . . . . . . . . . . . 150 115 16. Example of a full deposit using the XML model . . . . . . . . 150 116 17. Example of differential deposit using the XML model . . . . . 155 117 18. Example of a full deposit using the CSV model . . . . . . . . 157 118 19. Example of differential deposit using the CSV model . . . . . 166 119 20. References . . . . . . . . . . . . . . . . . . . . . . . . . 177 120 20.1. Normative References . . . . . . . . . . . . . . . . . . 177 121 20.2. Informative References . . . . . . . . . . . . . . . . . 178 122 20.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 179 123 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 179 125 1. Introduction 127 This document defines the data escrow structure of the standard set 128 of objects for a Domain Name Registry which include: 130 o Domain: Internet domain names that are typically provisioned in a 131 Domain Name Registry using the EPP domain name mapping [RFC5731]. 132 The attributes defined in the EPP domain name mapping [RFC5731] 133 are fully supported by this document. 135 o Host: Internet host names that are typically provisioned in a 136 Domain Name Registry using the EPP host mapping [RFC5732]. The 137 attributes defined in the EPP host mapping [RFC5732] are fully 138 supported by this document. 140 o Contact: Individual or organization social information provisioned 141 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 142 The attributes defined in the EPP contact mapping [RFC5733] are 143 fully supported by this document. 145 o Registrar: The organization that sponsors objects like domains, 146 hosts, and contacts in a Domain Name Registry. 148 o NNDN (NNDN's not domain name): A lightweight domain-like object 149 that is not linked to a Registrar. 151 This document defines the following pseudo-objects: 153 o IDN Table Reference: Internationalized Domain Names (IDN) included 154 in the Domain Object Data Escrow include references to the IDN 155 Table and Policy used in IDN registration. 157 o EPP parameters: Definition of the specific EPP parameters 158 supported by the Registry Operator. 160 o Header: Used to specify counters of objects in the database at a 161 certain point in time (watermark). 163 o Policy: Used to specify OPTIONAL elements from this specification 164 that are REQUIRED based on the business model of the registry. 166 2. Models 168 This document defines two different models that can be used to 169 deposit data escrow objects: 171 o XML: The XML model includes all the deposit information (meta-data 172 and data) in an XML document. The definition of the XML format is 173 fully defined in the XML schemas. As a convention, the objects 174 represented using the XML model are referenced using RDE and an 175 XML namespace that is prefixed with "rde". For example, the 176 Domain Name object represented using the XML model can be referred 177 to as the RDE Domain Name with the XML namespace including 178 rdeDomain (urn:ietf:params:xml:ns:rdeDomain-1.0). 180 o CSV: The CSV model uses XML to define the data escrow format of 181 the data contained in referenced Comma-Separated Values (CSV) 182 files. As a convention, the objects represented using the CSV 183 model is referenced using CSV and an XML namespace that is 184 prefixed with "csv". For example, the Domain Name object 185 represented using the CSV model can be referred to as the CSV 186 Domain Name with the XML namespace including csvDomain 187 (urn:ietf:params:xml:ns:csvDomain-1.0). 189 The data escrow deposit MAY contain a mix of both models but an 190 object MUST be escrowed only in one model. 192 3. Terminology 194 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 195 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 196 document are to be interpreted as described in BCP 14, [RFC2119]. 198 REGISTRY. In the context of this draft the definition will be 199 overloaded (from the definition in the base protocol) to indicate an 200 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 201 NAME. 203 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 204 or any other domain name at any level in the DNS tree for which a 205 Registry (either directly or through and affiliate company) provides 206 Registry Services for other organizations or individuals. For 207 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 209 REGISTRY SERVICES. Services offered by the Registry critical to the 210 following tasks: the provisioning of domain names on receipt of 211 requests and data from registrars; responding to registrar queries 212 for status information relating to the DNS servers for the RCDN; 213 dissemination of RCDN zone files; operation of the Registry DNS 214 servers; and responding to queries for contact and other information 215 concerning DNS registrations in the RCDN. Any other products or 216 services that only a Registry is capable of providing, by reason of 217 its designation as the Registry. Typical examples of Registry 218 Services are: DNS resolution for the RCDN, WHOIS and EPP. 220 ALLOCATED. A status of some label with respect to a zone, whereby 221 the label is associated administratively to some entity that has 222 requested the label. This term (and its cognates "allocation" and 223 "to allocate") may represents the first step on the way to delegation 224 in the DNS. 226 4. General Conventions 228 4.1. Date and Time 230 Numerous fields indicate "dates", such as the creation and expiry 231 dates for domain names. These fields SHALL contain timestamps 232 indicating the date and time in UTC as specified in [RFC3339], with 233 no offset from the zero meridian. 235 4.2. Country names 237 Country identifiers SHALL be represented using two character 238 identifiers as specified in [ISO-3166-1]. 240 4.3. Telephone numbers 242 Telephone numbers (both voice and facsimile) SHALL be formatted based 243 on structures defined in [ITU-E164]. Telephone numbers described in 244 this specification are character strings that MUST begin with a plus 245 sign ("+", ASCII value 0x002B), followed by a country code defined in 246 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 247 a sequence of digits representing the telephone number. 249 4.4. Checksum 251 Checksum of the CSV data escrow files MUST use CRC32, that is the 252 algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of 253 ITU-T recommendation V.42. 255 4.5. IP addresses 257 IP addresses syntax MUST conform to the text representation of either 258 of, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 259 Addressing Architecture [RFC4291], for IPv6 addresses. 261 4.6. CSV Parent Child Relationship 263 The CSV model represents a relational model, where the CSV files 264 represent relational tables, the fields of the CSV files represent 265 columns of the tables, and each line of the CSV file represents a 266 record. As in a relational model, the CSV files can have 267 relationships utilizing primary keys in the parent CSV file 268 definitions and foreign keys in the child CSV file definitions for a 269 1-to-many relationship. The primary keys are not explicitly defined, 270 but the foreign keys are using the boolean "parent" field attribute 271 in the child CSV file. The relationships between the CSV files are 272 used to support a cascade replace or cascade delete of records 273 starting from the parent record in differential and incremental 274 deposits. 276 The following is an example of the CSV file definitions for a Sample 277 object consisting of a parent "sample" CSV File Definition and a 278 child "sampleStatuses" CSV File Definition. The primary key for the 279 Sample object is the field that is used as the 280 foreign key in the "sampleStatuses" CSV File Definition by specifying 281 the "parent=true" attribute. If a Sample record is updated or 282 deleted in a differential or incremental deposit, it should cascade 283 replace the data using the records included in the child 284 "sampleStatuses" CSV File Definition or cascade delete the existing 285 records in the child "sampleStatuses" CSV File Definition, 286 respectively. 288 289 ... 290 291 292 293 294 295 296 297 298 299 300 301 302 303 305 sample-YYYYMMDD.csv 306 307 308 309 310 311 312 313 314 315 316 317 319 sampleStatuses-YYYYMMDD.csv 320 321 322 323 ... 324 326 4.7. CSV elements 328 4.7.1. element 330 To support a CSV model with the Registry Data Escrow Specification 331 [1], an element is defined for each object that substitutes for the 332 element and for the element, that contains 333 one or more elements. For example, the Domain Name 334 Object (Section 5.1) defines the element, that 335 substitutes for the element, and the 336 element, that substitutes for the 337 element. Both the element and the 338 elements contain one or more 339 elements. The element has the following child elements: 341 Ordered list of CSV fields used in the CSV files. 342 There is one or more child elements that substitute for the 343 abstract element. Each element defines the format 344 of the CSV field contained in the CSV files. The 345 elements support the "type" attribute that defines the XML simple 346 data type of the field element. The elements 347 support the "isRequired" attribute, with a default value of 348 "false", when set to "true" indicates that the field must be non- 349 empty in the CSV files and when set to "false" indicates that the 350 field MAY be empty in the CSV files. The "isRequired" attribute 351 MAY be specifically set for the field elements within the XML 352 schema and MAY be overridden when specifying the fields under the 353 element. The element supports an 354 OPTIONAL "parent" attribute that identifies the field as a 355 reference to a parent object, as defined in CSV Parent Child 356 Relationship (Section 4.6). For example, the field SHOULD set the 358 "parent" attribute to "true" to identify it as the parent domain 359 name of the domain status. 361 A list of one or more CSV files using the 362 child element. The child element 363 defines a reference to the CSV file name and has the following 364 optional attributes: 366 compression If the CSV file is compressed, the "compression" 367 attribute defines the compression format like "gzip" or "zip". 369 encoding Defines the encoding of the CSV file with the default 370 encoding of "UTF-8". 372 cksum Defines the checksum of the CSV file using CRC32, as 373 defined in Section 4.4. This attribute is used to validate 374 that the full CSV file exists and has not been tampered with. 376 The elements requires a "name" attribute that defines 377 the purpose of the CSV file with values like "domain", "host", 378 "contact". The supported "name" attribute values are defined for 379 each object type. The OPTIONAL "sep" attribute defines the CSV 380 separator character with the default separator character of ",". 382 The following is an example of the 383 element for domain name records where the is set 384 as required with isRequired="true". 386 387 ... 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 407 domain-YYYYMMDD.csv 408 409 410 411 ... 412 414 The following is example of the "domain-YYYYMMDD.csv" file with one 415 record matching the definition. 417 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 418 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 419 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 420 The following is an example of the 421 element for domain name records. 423 424 ... 425 426 427 428 429 430 432 domain-delete-YYYYMMDD.csv 433 434 435 436 ... 437 439 The following is example of the "domain-delete-YYYYMMDD.csv" file 440 with three records that matches the single field. 442 domain1.test 443 domain2.test 444 domainN.test 446 4.7.2. CSV common field elements 448 The element defined in the element 449 (Section 4.7.1) section has child elements that substitute for the 450 abstract element. By convention 451 elements include an 'f' prefix to identify them as field definition 452 elements. There are a set of common field elements that are used 453 across multiple data escrow objects. The common field elements are 454 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 455 using the "rdeCsv" sample namespace prefix. The CSV common field 456 elements include: 458 UTF-8 encoded name field with 459 type="eppcom:labelType". 461 Repository Object IDentifier (ROID) field with 462 type="eppcom:roidType" and isRequired="true". 464 Registrant contact identifier with 465 type="eppcom:clIDType". 467 The object status description, which is 468 free form text describing the rationale for the status, with 469 type="normalizedString". 471 Identifier of client (registrar) that sponsors the 472 object with type="eppcom:clIDType" and isRequired="true". 474 Identifier of the registrar, defined in Section 5.4, 475 of the client that created the object with type="eppcom:clIDType". 477 Identifier of client that created the object with 478 type="eppcom:clIDType". 480 Identifier of the registrar, defined in Section 5.4, 481 of the client that updated the object with type="eppcom:clIDType". 483 Identifier of client that updated the object with 484 type="eppcom:clIDType". 486 Identifier of the registrar, defined in Section 5.4, 487 of the client that requested the transfer with 488 type="eppcom:clIDType" and isRequired="true". 490 Identifier of client that requested the transfer with 491 type="eppcom:clIDType". 493 Identifier of the registrar, defined in Section 5.4, 494 of the client that should take or took action with 495 type="eppcom:clIDType" and isRequired="true". 497 Identifier of client that should take or took action 498 for transfer with type="eppcom:clIDType". 500 Created date of object with type="dateTime" and 501 isRequired="true". 503 Updated date of object with type="dateTime". 505 Expiration date of object with type="dateTime". 507 Date that transfer was requested with 508 type="dateTime" and isRequired="true". 510 Date that transfer action should be taken or has 511 been taken with type="dateTime" and isRequired="true". 513 Date of last transfer with type="dateTime". 515 State of the most recent transfer request with 516 type="eppcom:trStatusType" and isRequired="true". 518 General token field with type="token". 520 General language field with type="language". 522 IDN Table Identifier used for IDN domain names 523 with type="token". 525 General positive integer field with 526 type="positiveInteger". 528 Contains the URL of an object like a registrar object 529 with type="anyURI". 531 Custom field with name attribute that defines the 532 custom field name" with type="token". 534 4.8. Internationalized and Localized Elements 536 Some elements MAY be provided in either internationalized form 537 ("int") or provided in localized form ("loc"). Those elements use a 538 field value or "isLoc" attribute to specify the form used. If an 539 "isLoc" attribute is used, a value of "true" indicates the use of the 540 localized form and a value of "false" indicates the use of the 541 internationalized form. This MAY override the form specified for a 542 parent element. A value of "int" is used to indicate the 543 internationalized form and a value of "loc" is used to indicate the 544 localized form. When the internalized form ("int") is provided, the 545 field value MUST be represented in a subset of UTF-8 that can be 546 represented in the 7-bit US-ASCII character set. When the localized 547 form ("loc") is provided, the field value MAY be represented in 548 unrestricted UTF-8. 550 The field elements below of the "registrar" 551 element specify the internationalized form with the 552 isLoc="false" attribute. 554 ... 555 556 ... 557 558 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 588 registrar-YYYYMMDD.csv 589 590 591 592 ... 593 594 ... 596 The following is an example of using the 597 field value to define the internationalized or localized form of the 598 remainder of the "contactPostal" field values. 600 ... 601 602 ... 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 620 contactPostal-YYYYMMDD.csv 621 622 623 624 ... 625 626 ... 628 5. Object Description 630 This section describes the base objects supported by this 631 specification: 633 5.1. Domain Name Object 635 The domain name object is based on the EPP domain name mapping 636 specified in [RFC5731]. The domain name object supports both the XML 637 Model and the CSV Model, defined in the Models (Section 2) section. 638 The elements used for both models are defined in the following 639 sections. 641 5.1.1. XML Model 643 There are two elements used in the data escrow of the domain name 644 objects for the XML model including the , under the 645 element, and the element, under the 646 element. 648 5.1.1.1. object 650 The domain element is based on the EPP domain response for an 651 authorized client (see Section 3.1.2. of [RFC5731]) with additional 652 data from an EPP Query Response, see Section 3.1.3. of 653 [RFC5731], RGP status from [RFC3915], and data from the EPP 654 command, see Section 5.2.1. of [RFC5910]. 656 A element substitutes for the abstract 657 element to define a concrete definition of a domain. The 658 element can be replaced by other domain definitions 659 using the XML schema substitution groups feature. 661 The element contains the following child elements: 663 o A element that contains the fully qualified name of the 664 domain name object. If the domain name is an IDN, the ASCII 665 Compatible Encoding (ACE) MUST be used. 667 o A element that contains the repository object identifier 668 assigned to the domain name object when it was created. 670 o An OPTIONAL element that contains the fully qualified name 671 of the domain name in Unicode character set. It MUST be provided 672 if available. 674 o An OPTIONAL element that references the IDN 675 Table used for the IDN. This corresponds to the "id" attribute of 676 the element. This element MUST be present if the 677 domain name is an IDN. 679 o An OPTIONAL element is used to indicate that the 680 domain name is an IDN variant. This element contains the domain 681 name used to generate the IDN variant. 683 o One or more elements that contain the current status 684 descriptors associated with the domain name. 686 o Zero or more OPTIONAL element to represent 687 "pendingDelete" sub-statuses, including "redemptionPeriod", 688 "pendingRestore", and "pendingDelete", that a domain name can be 689 in as a result of grace period processing as specified in 690 [RFC3915]. 692 o An OPTIONAL element that contain the identifier for 693 the human or organizational social information object associated 694 as the holder of the domain name object. 696 o Zero or more OPTIONAL elements that contain identifiers 697 for the human or organizational social information objects 698 associated with the domain name object. 700 o An OPTIONAL element that contains the fully qualified names 701 of the delegated host objects or host attributes (name servers) 702 associated with the domain name object. See Section 1.1 of 703 [RFC5731] for a description of the elements used to specify host 704 objects or host attributes. 706 o A element that contains the identifier of the sponsoring 707 registrar. 709 o An OPTIONAL element that contains the identifier of the 710 registrar that created the domain name object. An OPTIONAL client 711 attribute is used to specify the client that performed the 712 operation. 714 o An OPTIONAL element that contains the date and time of 715 the domain name object creation. This element MUST be present if 716 the domain name has been allocated. 718 o An OPTIONAL element that contains the date and time 719 identifying the end (expiration) of the domain name object's 720 registration period. This element MUST be present if the domain 721 name has been allocated. 723 o An OPTIONAL element that contains the identifier of the 724 registrar that last updated the domain name object. This element 725 MUST NOT be present if the domain has never been modified. An 726 OPTIONAL client attribute is used to specify the client that 727 performed the operation. 729 o An OPTIONAL element that contains the date and time of 730 the most recent domain-name-object modification. This element 731 MUST NOT be present if the domain name object has never been 732 modified. 734 o An OPTIONAL element that contains the public key 735 information associated with Domain Name System security (DNSSEC) 736 extensions for the domain name as specified in [RFC5910]. 738 o An OPTIONAL element that contains the date and time of 739 the most recent domain object successful transfer. This element 740 MUST NOT be present if the domain name object has never been 741 transferred. 743 o An OPTIONAL element that contains the following child 744 elements related to the last transfer request of the domain name 745 object. This element MUST NOT be present if a transfer request 746 for the domain name has never been created. 748 * A element that contains the state of the most recent 749 transfer request. 751 * A element that contains the identifier of the registrar 752 that requested the domain name object transfer. An OPTIONAL 753 client attribute is used to specify the client that performed 754 the operation. 756 * A element that contains the date and time that the 757 transfer was requested. 759 * An element that contains the identifier of the registrar 760 that SHOULD act upon a PENDING transfer request. For all other 761 status types, the value identifies the registrar that took the 762 indicated action. An OPTIONAL client attribute is used to 763 specify the client that performed the operation. 765 * An element that contains the date and time of a 766 required or completed response. For a PENDING request, the 767 value identifies the date and time by which a response is 768 required before an automated response action will be taken by 769 the registry. For all other status types, the value identifies 770 the date and time when the request was completed. 772 * An OPTIONAL element that contains the end of the 773 domain name object's validity period (expiry date) if the 774 transfer caused or causes a change in the validity period. 776 Example of a domain object: 778 ... 779 780 example1.test 781 Dexample1-TEST 782 783 jd1234 784 sh8013 785 sh8013 786 787 ns1.example.com 788 ns1.example1.test 789 790 RegistrarX 791 RegistrarX 792 1999-04-03T22:00:00.0Z 793 2015-04-03T22:00:00.0Z 794 795 ... 797 5.1.1.2. object 799 The element contains the fully qualified domain 800 name that was deleted and purged. 802 Example of object: 804 ... 805 806 ... 807 808 foo.test 809 bar.test 810 811 ... 812 813 ... 815 5.1.2. CSV Model 817 For the CSV Model of the domain name object, the 818 child element of the element is used to hold the new 819 or updated domain name objects for the deposit. The 820 child element of the element is 821 used to hold the deleted or purged domain name objects for the 822 deposit. Both the and 823 elements contain one or more elements with a set of 824 named CSV file definitions using the "name" attribute. 826 Differential and incremental deposits are based on changes to the 827 domain name objects. The updated domain name object data under the 828 element is a cascade replace down all of the 829 domain name CSV files starting with the parent "domain" CSV File 830 Definition (Section 5.1.2.1.1). The child CSV file definitions 831 include a field. All the child CSV 832 file definition data for the domain name objects in the parent 833 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 834 deleted and then set using the data in the child CSV files. The 835 deleted domain name object data under the element 836 is a cascade delete starting from the "domain" Deletes CSV File 837 Definition (Section 5.1.2.2.1). 839 5.1.2.1. 841 The is used to hold the new or updated domain 842 name object information for the deposit. The is 843 split into separate CSV file definitions using named 844 elements with the "name" attribute. The following sections include 845 the supported domain name CSV file definitions: 847 5.1.2.1.1. "domain" CSV File Definition 849 The "domain" CSV File Definition defines the fields and CSV file 850 references used for the parent domain name object records. All the 851 other domain name CSV file definitions are child CSV files based on 852 the inclusion of the field. 854 The following "csvDomain" field elements MUST be used in the "domain" 855 element: 857 Domain name field with type="eppcom:labelType" and 858 isRequired="true". 860 The following "csvDomain" field elements MAY be used in the "domain" 861 element: 863 Fully qualified name of the original IDN 864 domain name object related to the variant domain name object with 865 type="eppcom:labelType". 867 The following "rdeCsv" fields, defined in section CSV common field 868 elements (Section 4.7.2), MUST be used in the "domain" 869 element: 871 Registry Object IDentifier (ROID) for the domain name 872 object with isRequired="true". 874 Identifier of client that sponsors the domain name 875 object with isRequired="true". 877 Created date and time of the domain name object 878 with isRequired="true". 880 Identifier of the registrar, defined in Section 5.4, 881 of the client that updated the object. 883 Date and time of the last update to the domain name 884 object. 886 Expiration date and time for the domain name 887 object. The attribute isRequired MUST equal "true". 889 The following "rdeCsv" fields, defined in section CSV common field 890 elements (Section 4.7.2), MAY be used in the "domain" 891 element: 893 Identifier of the registrar, defined in Section 5.4, 894 of the client that created the object. 896 UTF8 encoded domain name for the 897 field element. 899 IDN Table Identifier used for the IDN domain 900 name object that MUST match a field element 901 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 903 Registrant contact identifier for the domain 904 name object. 906 Identifier of client that created the domain name 907 object. 909 Identifier of the client that last updated the domain 910 name object. 912 Date and time of the last transfer for the domain 913 name object. 915 Example of a "domain" element. 917 ... 918 919 ... 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 939 domain-YYYYMMDD.csv 940 941 942 943 ... 944 945 ... 947 Example of the corresponding domain-YYYYMMDD.csv file. The file 948 contains four records (two active ASCII domains, original IDN with 949 LANG-1 language rules, and variant IDN with LANG-1 language rules). 951 domain1.test,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 952 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 953 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 954 domain2.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 955 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 956 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 957 xn--abc123.test,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 958 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 959 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 960 xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--abc123.test, 961 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 962 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 964 5.1.2.1.2. "domainContacts" CSV File Definition 966 The "domainContacts" CSV File Definition defines the fields and CSV 967 file references used for the domain name object link records to 968 contact objects, as described in Contact Object (Section 5.3). 970 The following "csvDomain" field elements MUST be used in the 971 "domainContacts" element: 973 The contact type for the contact object 974 link with type="domain:contactAttrType" and isRequired="true". 975 The supported contact type values include "admin" for the 976 administration contact, "billing" for the billing contact, and 977 "tech" for the technical contact. 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 following "csvContact" fields, defined for the "contact" CSV File 987 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 988 element: 990 The server-unique contact identifier with 991 isRequired="true". 993 Example of a "domainContacts" 994 element. 996 ... 997 998 ... 999 1000 1001 1002 1003 1004 1005 1006 1008 domainContacts-YYYYMMDD.csv 1009 1010 1011 1012 ... 1013 1014 ... 1016 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1017 file contains an admin, tech, and billing contact for the four domain 1018 names domain1.test, domain2.test, xn--abc123.test and xn-- 1019 abc321.test. 1021 domain1.test,domain1admin,admin 1022 domain1.test,domain1tech,tech 1023 domain1.test,domain1billing,billing 1024 domain2.test,domain2admin,admin 1025 domain2.test,domain2tech,tech 1026 domain2.test,domain2billing,billing 1027 xn--abc123.test,xnabc123admin,admin 1028 xn--abc123.test,xnabc123tech,tech 1029 xn--abc123.test,xnabc123billing,billing 1030 xn--abc321.test,xnabc123admin,admin 1031 xn--abc321.test,xnabc123tech,tech 1032 xn--abc321.test,xnabc123billing,billing 1034 5.1.2.1.3. "domainStatuses" CSV File Definition 1036 The "domainStatuses" CSV File Definition defines the fields and CSV 1037 file references used for the domain name object statuses. 1039 The following "csvDomain" field elements MUST be used in the 1040 "domainStatuses" element: 1042 The status of the domain name with 1043 type="domain:statusValueType" and isRequired="true". 1045 The Registry Grace Period (RGP) status, as a 1046 sub-status of the "pendingDelete" status 1047 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1049 The following "csvDomain" fields, defined for the "domain" CSV File 1050 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1051 element: 1053 Domain name of status with isRequired="true". 1055 The following "rdeCsv" fields, defined in section CSV common field 1056 elements (Section 4.7.2), MAY be used in the "domainStatuses" 1057 element: 1059 Domain object status description which 1060 is free form text describing the rationale for the status. 1062 Language of the field. 1064 Example of a "domainStatuses" 1065 element. 1067 ... 1068 1069 ... 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1081 domainStatuses-YYYYMMDD.csv 1082 1083 1084 1085 ... 1086 1087 ... 1089 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1090 file contains the statuses for the four domain names domain1.test, 1091 domain2.test, xn--abc123.test and xn--abc321.test. 1093 domain1.test,clientUpdateProhibited,"Disallow update", 1094 en, 1095 domain1.test,clientDeleteProhibited,"Disallow delete", 1096 en, 1097 domain2.test,ok,,, 1098 xn--abc123.test,ok,,, 1099 xn--abc321.test,ok,,, 1101 5.1.2.1.4. "domainNameServers" CSV File Definition 1103 The "domainNameServers" CSV File Definition defines the fields and 1104 CSV file references used for the domain name delegated hosts (name 1105 servers). The "domainNameServers" CSV files define the relationship 1106 between a domain name object and a delegated host. The 1107 "domainNameServers" CSV File is used to support the 1108 model, defined in [RFC5731]. 1110 The following "csvDomain" fields, defined for the "domain" CSV File 1111 Definition (Section 5.1.2.1.1), MUST be used in the 1112 "domainNameServers" element: 1114 Domain name using the delegated host with host 1115 and isRequired="true". 1117 The following "rdeCsv" fields, defined in section CSV common field 1118 elements (Section 4.7.2), MUST be used in the "domainNameServers" 1119 element: 1121 Registry Object IDentifier (ROID) used to uniquely 1122 reference a delegated host record with isRequired="true". 1124 Example of a "domainNameServers" 1125 element. 1127 ... 1128 1129 ... 1130 1131 1132 1133 1134 1135 1136 1138 domainNameServers-YYYYMMDD.csv 1139 1140 1141 1142 ... 1143 1144 ... 1146 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1147 The file contains the delegated hosts (name servers) for the four 1148 domain names domain1.test, domain2.test, xn--abc123.test and xn-- 1149 abc321.test referenced via the field element. 1151 domain1.test,Hns1_domain1_test-TEST 1152 domain1.test,Hns2_domain1_test-TEST 1153 domain2.test,Hns1_domain2_test-TEST 1154 domain2.test,Hns2_domain2_test-TEST 1155 xn--abc123.test,Hns1_example_test-TEST 1156 xn--abc123.test,Hns2_example_test-TEST 1157 xn--abc321.test,Hns1_example_test-TEST 1158 xn--abc321.test,Hns2_example_test-TEST 1160 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1162 The "domainNameServersAddresses" CSV File Definition defines the 1163 fields and CSV file references used for supporting the host as domain 1164 attributes model. 1166 The following "csvDomain" fields, defined for the "domain" CSV File 1167 Definition (Section 5.1.2.1.1), MUST be used in the 1168 "domainNameServersAddresses" element: 1170 Domain name using the delegated host with host 1171 and isRequired="true". 1173 The following "rdeCsv" fields, defined in section Host CSV model 1174 elements (Section 5.2.2), MUST be used in the 1175 "domainNameServersAddresses" element: 1177 Host name field with type="eppcom:labelType" and 1178 isRequired="true". 1180 The following "csvHost" fields, defined in section Host CSV model 1181 elements (Section 5.2.2), MAY be used in the 1182 "domainNameServersAddresses" element: 1184 IP addresses associated with the host object with 1185 type="host:addrStringType". 1187 IP addresses version associated with the host 1188 object with type="host:ipType". "host:ipType" has the enumerated 1189 values of "v4" or "v6". 1191 Example of a "domainNameServersAddresses" 1192 element. 1194 ... 1195 1196 ... 1197 1198 1199 1200 1201 1202 1203 1204 1205 1207 domainNameServersAddresses-YYYYMMDD.csv 1208 1209 1210 1211 ... 1212 1213 ... 1215 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1216 file. The file contains the delegated hosts (name servers) for the 1217 four domain names domain1.test, domain2.test, xn--abc123.test and 1218 xn--abc321.test. 1220 domain1.test,ns1.domain1.test,192.0.2.1,v4 1221 domain1.test,ns2.domain1.test,2001:DB8::1,v6 1222 domain2.test,ns1.domain2.test2,192.0.2.2,v4 1223 domain2.test,ns2.domain2.test2,2001:DB8::2,v6 1224 xn--abc123.test,ns1.example.example,, 1225 xn--abc123.test,ns2.example.example,, 1226 xn--abc321.test,ns1.example.example,, 1227 xn--abc321.test,ns2.example.example,, 1229 5.1.2.1.6. "dnssec" CSV File Definition 1231 The "dnssec" CSV File Definition defines the fields and CSV file 1232 references used for the domain name object DNSSEC records (DS or Key 1233 Data). 1235 The following "csvDomain" field elements MUST be used in the "dnssec" 1236 element when the DS Data Interface per 1237 [RFC5910] is used: 1239 Contains the DS key tag value per [RFC5910] with 1240 type="unsignedShort" and isRequired="true". 1242 Contains the DS algorithm value per [RFC5910] 1243 with type="unsignedByte" and isRequired="true". 1245 Contains the DS digest type value per 1246 [RFC5910] with type="unsignedByte" and isRequired="true". 1248 Contains the DS digest value per [RFC5910] with 1249 type="hexBinary" and isRequired="true". 1251 The following "csvDomain" field elements MUST be used in the "dnssec" 1252 element when the Key Data Interface per 1253 [RFC5910] is used and MAY be used in the "dnssec" 1254 element when the DS Data Interface per [RFC5910] is 1255 used: 1257 Contains the flags field value per [RFC5910] with 1258 type="unsignedShort" and isRequired="true". 1260 Contains the Key protocol value per [RFC5910] 1261 with type="unsignedByte" and isRequired="true". 1263 Contains the Key algorithm value per [RFC5910] 1264 with type="unsignedByte" and isRequired="true". 1266 Contains the public key value per [RFC5910] with 1267 type="secDNS:keyType" and isRequired="true". 1269 The following "csvDomain" field elements MAY be used in the "dnssec" 1270 element: 1272 Indicates a child's preference for the 1273 number of seconds after signature generation when the parent's 1274 signature on the DS information provided by the child will expire 1275 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1277 The following "domain" fields, defined for the "domain" CSV File 1278 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1279 element: 1281 Domain name of the domain object associated with 1282 the DNSSEC record and isRequired="true". 1284 Example of a "dnssec" element with 1285 the DS Data Interface of [RFC5910]: 1287 1288 ... 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1301 dnssec-ds-YYYYMMDD.csv 1302 1303 1304 1305 ... 1306 1307 ... 1309 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1310 contains two DS records for domain1.test. 1312 domain1.test,604800,12345,3,1,49FD46E6C4B45C55D4AC 1313 domain1.test,604800,12346,3,1,38EC35D5B3A34B44C39B 1315 Example of a "dnssec" element with 1316 the Key Data Interface of [RFC5910]: 1318 1319 ... 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1332 dnssec-key-YYYYMMDD.csv 1333 1334 1335 1336 ... 1337 1338 ... 1340 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1341 contains two key records for domain1.test. 1343 domain1.test,604800,257,3,1,AQPJ////4Q== 1344 domain1.test,604800,257,3,1,AQPJ////4QQQ 1346 5.1.2.1.7. "domainTransfer" CSV File Definition 1348 The "domainTransfer" CSV File Definition defines the fields and CSV 1349 file references used for the domain name object pending and completed 1350 transfer records. No additional field elements were added for use in 1351 the "domainTransfer" element. 1353 The following "rdeCsv" fields, defined in section CSV common field 1354 elements (Section 4.7.2), MUST be used in the "domainTransfer" 1355 element: 1357 State of the most recent transfer request with 1358 isRequired="true". 1360 Identifier of the registrar, defined in Section 5.4, 1361 of the client that requested the transfer with isRequired="true". 1363 Date and time that the transfer was requested with 1364 isRequired="true". 1366 Identifier of the registrar, defined in Section 5.4, 1367 of the client that should take or took action with 1368 isRequired="true". 1370 Date and time that the transfer action should be 1371 taken or has been taken with isRequired="true". 1373 The following "rdeCsv" fields, defined in section CSV common field 1374 elements (Section 4.7.2), MAY be used in the "domainTransfer" 1375 element: 1377 Expiration date if the transfer command caused or 1378 causes a change in the validity period. 1380 Identifier of client that requested the transfer. 1382 Identifier of client that should take or took action 1383 for transfer. 1385 The following "csvDomain" fields, defined for the "domain" CSV File 1386 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1387 element: 1389 Domain name of the domain object involved in the 1390 transfer with isRequired="true". 1392 Example of a "domainTransfer" 1393 element. 1395 ... 1396 1397 ... 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1413 domainTransfer-YYYYMMDD.csv 1414 1415 1416 1417 ... 1418 1419 ... 1421 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1422 file contains one domain transfer record with a pending status. 1424 domain1.test,pending,registrarX,clientY, 1425 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1426 2016-04-03T22:00:00.0Z 1428 5.1.2.2. 1430 The is used to hold the deleted domain name 1431 objects in a differential or incremental deposit. All the domain 1432 name object data is deleted as part of a cascade delete. The 1433 is split into separate CSV file definitions using 1434 named elements with the "name" attribute. The following 1435 section defines the supported domain name deletes CSV file 1436 definition. 1438 5.1.2.2.1. "domain" Deletes CSV File Definition 1440 The following "csvDomain" field elements MUST be used in the deletes 1441 "domain" element: 1443 Domain name field with type="eppcom:labelType" and 1444 isRequired="true". 1446 Example of a "domain" element: 1448 ... 1449 1450 ... 1451 1452 1453 1454 1455 1456 1458 domain-delete-YYYYMMDD.csv 1459 1460 1461 1462 ... 1463 1464 ... 1466 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1467 file contains two domain name records. 1469 domain1.test 1470 domain2.test 1472 5.2. Host Object 1474 The host object is based on the EPP host name mapping in [RFC5732]. 1475 The host object supports both the XML Model and the CSV Model, 1476 defined in Models (Section 2) section. The elements used for both 1477 models are defined in the following sections. Both the 1478 and elements contain one or more 1479 elements with a set of named CSV file definitions using 1480 the "name" attribute. 1482 5.2.1. XML Model 1484 There are two elements used in the data escrow of the host objects 1485 for the XML model including the , under the 1486 element, and the element, under 1487 the element. 1489 A element substitutes for the 1490 abstract element to define a concrete definition of a host. The 1491 element can be replaced by other host 1492 definitions using the XML schema substitution groups feature. 1494 5.2.1.1. element 1496 The RDE host object is based on the EPP host response for an 1497 authorized client (Section 3.1.2. of [RFC5732]). 1499 The OPTIONAL element contains the following child elements: 1501 o A element that contains the fully qualified name of the 1502 host object. 1504 o A element that contains the repository object identifier 1505 assigned to the host object when the object was created. 1507 o One or more elements that describe the status of the host 1508 object. 1510 o Zero or more elements that contain the IP addresses 1511 associated with the host object. 1513 o A element that contains the identifier of the sponsoring 1514 registrar. 1516 o A element that contains the identifier of the registrar 1517 that created the host object. An OPTIONAL client attribute is 1518 used to specify the client that performed the operation. 1520 o A element that contains the date and time of host-object 1521 creation. 1523 o An OPTIONAL element that contains the identifier of the 1524 registrar that last updated the host object. This element MUST 1525 NOT be present if the host object has never been modified. An 1526 OPTIONAL client attribute is used to specify the client that 1527 performed the operation. 1529 o An OPTIONAL element that contains the date and time of 1530 the most recent host-object modification. This element MUST NOT 1531 be present if the host object has never been modified. 1533 o An OPTIONAL element that contains the date and time of 1534 the most recent host object successful transfer. This element 1535 MUST NOT be present if the domain name object has never been 1536 transfered. 1538 Example of object: 1540 ... 1541 1542 ns1.example1.test 1543 Hns1_example_test-TEST 1544 1545 1546 192.0.2.2 1547 192.0.2.29 1548 1080:0:0:0:8:800:200C:417A 1549 RegistrarX 1550 RegistrarX 1551 1999-05-08T12:10:00.0Z 1552 RegistrarX 1553 2009-10-03T09:34:00.0Z 1554 1555 ... 1557 5.2.1.2. object 1559 The element contains the fully qualified domain name 1560 of a host that was deleted. The element also 1561 supports host removal based on roid to support SRS systems in which 1562 different hosts with the same fully qualified domain name are active 1563 at the same time. 1565 Example of object: 1567 ... 1568 1569 ... 1570 1571 ns1.example.test 1572 1573 ... 1574 1575 ... 1577 5.2.2. CSV Model 1579 For the CSV Model of the host object, the child 1580 element of the element is used to hold the new or 1581 updated host objects for the deposit. The child 1582 element of the element is used to hold the deleted or 1583 purged host objects for the deposit. 1585 Differential and incremental deposits are based on changes to the 1586 host objects. The updated host object data under the 1587 element is a cascade replace down all of the host 1588 CSV files starting with the parent "host" CSV File Definition 1589 (Section 5.2.2.1.1). The child CSV file definitions include a 1590 field. All the child CSV file 1591 definition data for the host objects in the parent "host" CSV File 1592 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1593 using the data in the child CSV files. The deleted host object data 1594 under the element is a cascade delete starting from 1595 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1597 5.2.2.1. 1599 The is used to hold the new or updated host object 1600 information for the deposit. The is split into 1601 separate CSV file definitions using named elements with 1602 the "name" attribute. The following sections include the supported 1603 host CSV file definitions. 1605 5.2.2.1.1. "host" CSV File Definition 1607 The "host" CSV File Definition defines the fields and CSV file 1608 references used for the host object records. 1610 The following "csvHost" field elements MUST be used in the "host" 1611 element: 1613 Host name field with type="eppcom:labelType" and 1614 isRequired="true". 1616 The following "rdeCsv" fields, defined in section CSV common field 1617 elements (Section 4.7.2), MUST be used in the "host" 1618 element: 1620 Repository Object IDentifier (ROID) assigned to the 1621 host object with isRequired="true". 1623 The following "rdeCsv" fields, defined in section CSV common field 1624 elements (Section 4.7.2), MAY be used in the "host" 1625 element: 1627 Identifier of the sponsoring client with 1628 isRequired="true". 1630 Identifier of the registrar, defined in Section 5.4, 1631 of the client that created the object with isRequired="true". 1633 Identifier of client that created the host object. 1635 Date and time that the host object was created with 1636 isRequired="true". 1638 Identifier of the registrar, defined in Section 5.4, 1639 of the client that updated the object. 1641 Identifier of client that last updated the host 1642 object. 1644 Date and time that the host object was last 1645 updated. 1647 Date and time that the host was last transferred. 1649 Example of a "host" element. 1651 ... 1652 1653 ... 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1670 host-YYYYMMDD.csv 1671 1672 1673 1674 ... 1675 1676 ... 1678 Example of the corresponding host-YYYYMMDD.csv file. The file 1679 contains six host records with four being internal hosts and two 1680 being external hosts. 1682 ns1.domain1.test,Hns1_example_test-TEST,registrarX,registrarX, 1683 clientY,1999-05-08T12:10:00.0Z,registrarX, 1684 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1685 ns2.domain1.test,Hns2_domain1_test-TEST,registrarX,registrarX, 1686 clientY,1999-05-08T12:10:00.0Z,registrarX, 1687 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1688 ns1.domain2.test,Hns1_domain2_test-TEST,registrarX,registrarX, 1689 clientY,1999-05-08T12:10:00.0Z,registrarX, 1690 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1691 ns2.domain2.test,Hns2_domain2_test-TEST,registrarX,registrarX, 1692 clientY,1999-05-08T12:10:00.0Z,registrarX, 1693 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1694 ns1.example.example,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.example.example,Hns2_example_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 1701 5.2.2.1.2. "hostStatuses" CSV File Definition 1703 The "hostStatuses" CSV File Definition defines the fields and CSV 1704 file references used for the host object statuses. 1706 The following "csvHost" fields, defined for the "host" CSV File 1707 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1708 element: 1710 The status of the host with 1711 type="host:statusValueType" and isRequired="true"./>. 1713 The following "rdeCsv" fields, defined in section CSV common field 1714 elements (Section 4.7.2), MUST be used in the "hostStatuses" 1715 element: 1717 Host object Registry Object IDentifier (ROID) 1718 assigned to the host object with isRequired="true". 1720 The following "rdeCsv" fields, defined in section CSV common field 1721 elements (Section 4.7.2), MAY be used in the "hostStatuses" 1722 element: 1724 Host object status description which is 1725 free form text describing the rationale for the status. The 1726 attribute isRequired MUST equal "true". 1728 Language of the field. 1730 Example of a "hostStatuses" element. 1732 ... 1733 1734 ... 1735 1736 1737 1738 1739 1740 1741 1742 1743 1745 hostStatuses-YYYYMMDD.csv 1746 1747 1748 1749 ... 1750 1751 ... 1753 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1754 file contains the statuses for the six host names ns1.domain1.test, 1755 ns2.domain1.test, ns1.domain2.test, ns2.domain2.test, 1756 ns1.example.example and ns2.example.example. 1758 Hns1_domain1_test-TEST,ok,, 1759 Hns2_domain1_test-TEST,ok,, 1760 Hns1_domain2_test-TEST,ok,, 1761 Hns2_domain2_test-TEST,ok,, 1762 Hns1_example_test-TEST,ok,, 1763 Hns2_example_test-TEST,ok,, 1765 5.2.2.1.3. "hostAddresses" CSV File Definition 1767 The "hostAddresses" CSV File Definition defines the fields and CSV 1768 file references used for the host object IP addresses. 1770 The following "csvHost" field elements MUST be used in the 1771 "hostAddresses" element: 1773 IP addresses associated with the host object with 1774 type="host:addrStringType". The attribute isRequired MUST equal 1775 "true". 1777 IP addresses version associated with the host 1778 object with type="host:ipType". "host:ipType" has the enumerated 1779 values of "v4" or "v6". The attribute isRequired MUST equal 1780 "true". 1782 The following "rdeCsv" fields, defined in section CSV common field 1783 elements (Section 4.7.2), MUST be used in the "hostAddresses" 1784 element: 1786 Host object Registry Object IDentifier (ROID) 1787 assigned to the host object. 1789 Example of a "hostAddresses" element. 1791 ... 1792 1793 ... 1794 1795 1796 1797 1798 1799 1800 1801 1803 hostAddresses-YYYYMMDD.csv 1804 1805 1806 1807 ... 1808 1809 ... 1811 Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The 1812 file contains the IP addresses for the host names ns1.domain1.test, 1813 ns2.domain1.test, ns1.domain2.test and ns2.domain2.test. 1815 Hns1_domain1_test-TEST,192.0.2.1,v4 1816 Hns2_domain1_test-TEST,2001:DB8::1,v6 1817 Hns1_domain2_test-TEST,192.0.2.2,v4 1818 Hns2_domain2_test-TEST,2001:DB8::2,v6 1820 5.2.2.2. 1822 The is used to hold the deleted host objects in a 1823 differential or incremental deposit. All the host object data is 1824 deleted as part of a cascade delete. The is split 1825 into separate CSV file definitions using named elements 1826 with the "name" attribute. The following section defines the 1827 supported host deletes CSV file definition. 1829 5.2.2.2.1. "host" Deletes CSV File Definition 1831 The following "rdeCsv" fields, defined in section CSV common field 1832 elements (Section 4.7.2), MUST be used in the "host" 1833 element: 1835 Repository Object IDentifier (ROID) assigned to the 1836 host object with isRequired="true". 1838 Example of a "host" element. 1840 ... 1841 1842 ... 1843 1844 1845 1846 1847 1848 1850 host-delete-YYYYMMDD.csv 1851 1852 1853 1854 ... 1855 1856 ... 1858 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1859 host records. 1861 Hns1_domain1_test-TEST 1862 Hns2_domain1_test-TEST 1863 Hns1_domain2_test-TEST 1864 Hns2_domain2_test-TEST 1866 5.3. Contact Object 1868 The contact object is based on the EPP contact name mapping in 1869 [RFC5733]. The contact object supports both the XML Model and the 1870 CSV Model, defined in Models (Section 2) section. The elements used 1871 for both models are defined in the following sections. 1873 5.3.1. XML Model 1875 There are two elements used in the data escrow of the contact objects 1876 for the XML model including the , under the 1877 element, and the element, 1878 under the element. 1880 A element substitutes for the abstract 1881 element to define a concrete definition of a contact. The 1882 element can be replaced by other contact 1883 definitions using the XML schema substitution groups feature. 1885 5.3.1.1. object 1887 The contact object is based on the EPP contact response for an 1888 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1889 including the data from an EPP Query Response, see 1890 Section 3.1.3. of [RFC5733]. 1892 The OPTIONAL element contains the following child elements: 1894 o A element that contains the server-unique identifier of the 1895 contact object 1897 o A element that contains the Repository Object IDentifier 1898 assigned to the contact object when the object was created. 1900 o One or more elements that describe the status of the 1901 contact object. 1903 o One or two elements that contain postal-address 1904 information. Two elements are provided so that address 1905 information can be provided in both internationalized and 1906 localized forms; a "type" attribute is used to identify the two 1907 forms. If an internationalized form (type="int") is provided, 1908 element content MUST be represented in a subset of UTF-8 that can 1909 be represented in the 7-bit US-ASCII character set. If a 1910 localized form (type="loc") is provided, element content MAY be 1911 represented in unrestricted UTF-8. The element 1912 contains the following child elements: 1914 * A element that contains the name of the individual or 1915 role represented by the contact. 1917 * An OPTIONAL element that contains the name of the 1918 organization with which the contact is affiliated. 1920 * An element that contains address information associated 1921 with the contact. An element contains the following 1922 child elements: 1924 + One, two, or three OPTIONAL elements that contain 1925 the contact's street address. 1927 + A element that contains the contact's city. 1929 + An OPTIONAL element that contains the contact's state 1930 or province. 1932 + An OPTIONAL element that contains the contact's postal 1933 code. 1935 + A element that contains the contact's two-letter 1936 country code. 1938 o An OPTIONAL element that contains the contact's voice 1939 telephone number. 1941 o An OPTIONAL element that contains the contact's facsimile 1942 telephone number. 1944 o An element that contains the contact's email address. 1946 o A element that contains the identifier of the sponsoring 1947 registrar. 1949 o A element that contains the identifier of the registrar 1950 that created the contact object. An OPTIONAL client attribute is 1951 used to specify the client that performed the operation. 1953 o A element that contains the date and time of contact- 1954 object creation. 1956 o An OPTIONAL element that contains the identifier of the 1957 registrar that last updated the contact object. This element MUST 1958 NOT be present if the contact has never been modified. An 1959 OPTIONAL client attribute is used to specify the client that 1960 performed the operation. 1962 o An OPTIONAL element that contains the date and time of 1963 the most recent contact-object modification. This element MUST 1964 NOT be present if the contact object has never been modified. 1966 o An OPTIONAL element that contains the date and time of 1967 the most recent contact object successful transfer. This element 1968 MUST NOT be present if the contact object has never been 1969 transferred. 1971 o An OPTIONAL element that contains the following child 1972 elements related to the last transfer request of the contact 1973 object: 1975 * A element that contains the state of the most recent 1976 transfer request. 1978 * A element that contains the identifier of the registrar 1979 that requested the domain name object transfer. An OPTIONAL 1980 client attribute is used to specify the client that performed 1981 the operation. 1983 * An element that contains the identifier of the registrar 1984 that SHOULD act upon a PENDING transfer request. For all other 1985 status types, the value identifies the registrar that took the 1986 indicated action. An OPTIONAL client attribute is used to 1987 specify the client that performed the operation. 1989 * A element that contains the date and time that the 1990 transfer was requested. 1992 * An element that contains the date and time of a 1993 required or completed response. For a PENDING request, the 1994 value identifies the date and time by which a response is 1995 required before an automated response action will be taken by 1996 the registry. For all other status types, the value identifies 1997 the date and time when the request was completed. 1999 o An OPTIONAL element that identifies elements that 2000 requiring exceptional server-operator handling to allow or 2001 restrict disclosure to third parties. See Section 2.9 of 2002 [RFC5733] for a description of the child elements contained within 2003 the element. 2005 Example object: 2007 ... 2008 2009 Csh8013-TEST 2010 sh8013 2011 2012 2013 2014 John Doe 2015 Example Inc. 2016 2017 123 Example Dr. 2018 Suite 100 2019 Dulles 2020 VA 2021 20166-6503 2022 US 2023 2024 2025 +1.7035555555 2026 +1.7035555556 2027 jdoe@example.test 2028 RegistrarX 2029 RegistrarX 2030 2009-09-13T08:01:00.0Z 2031 RegistrarX 2032 2009-11-26T09:10:00.0Z 2033 2009-12-03T09:05:00.0Z 2034 2035 pending 2036 clientW 2037 2011-03-08T19:38:00.0Z 2038 RegistrarX 2039 2011-03-13T23:59:59.0Z 2040 2041 2042 2043 2044 2045 2046 ... 2048 5.3.1.2. object 2050 The element contains the id of a contact that was 2051 deleted. 2053 Example of object: 2055 ... 2056 2057 ... 2058 2059 sh8013-TEST 2060 co8013-TEST 2061 2062 ... 2063 2064 ... 2066 5.3.2. CSV Model 2068 For the CSV Model of the contact object, the 2069 child element of the element is used to hold the new 2070 or updated contacts objects for the deposit. The 2071 child element of the element is 2072 used to hold the deleted or purged contact objects for the deposit. 2073 Both the and elements 2074 contain one or more elements with a set of named CSV 2075 file definitions using the "name" attribute. 2077 Differential and incremental deposits are based on changes to the 2078 contact objects. The updated contact object data under the 2079 element is a cascade replace down all of the 2080 contact CSV files starting with the parent "contact" CSV File 2081 Definition (Section 5.3.2.1.1). The child CSV file definitions 2082 include a field. All the child CSV 2083 file definition data for the contact objects in the parent "contact" 2084 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2085 then set using the data in the child CSV files. The deleted contact 2086 object data under the element is a cascade 2087 delete starting from the "contact" Deletes CSV File Definition 2088 (Section 5.3.2.2.1). 2090 5.3.2.1. 2092 The is used to hold the new or updated contact 2093 object information for the deposit. The is 2094 split into separate CSV file definitions using named 2095 elements with the "name" attribute. The following sections include 2096 the supported contact CSV file definitions. 2098 5.3.2.1.1. "contact" CSV File Definition 2100 The "contact" CSV File Definition defines the fields and CSV file 2101 references used for the contact object records. 2103 The following "csvContact" field elements MUST be used in the 2104 "contact" element: 2106 Contains the server-unique contact identifier with 2107 type="eppcom:clIDType" and isRequired="true". 2109 Contains the contact's email address with 2110 type="eppcom:minTokenType" and isRequired="true". 2112 The following field elements MAY be used in the "contact" 2113 element: 2115 Contains the contact's voice telephone number 2116 with type="contact:e164StringType". 2118 Contains the contact's voice telephone number 2119 extension with type="token". 2121 Contains the contact's facsimile telephone number 2122 with type="contact:e164StringType". 2124 Contains the contact's facsimile telephone 2125 number extension with type="token". 2127 The following "rdeCsv" fields, defined in section CSV common field 2128 elements (Section 4.7.2), MUST be used in the "contact" 2129 element: 2131 The Registry Object IDentifier (ROID) for the contact 2132 object with isRequired="true". 2134 Identifier of client (registrar) that sponsors the 2135 contact object with isRequired="true". 2137 Identifier of the registrar, defined in Section 5.4, 2138 of the client that created the object with isRequired="true". 2140 Created date and time of the contact object with 2141 isRequired="true". 2143 Identifier of the registrar, defined in Section 5.4, 2144 of the client that updated the object. 2146 Date and time of the last update to the contact 2147 object. 2149 The following "rdeCsv" fields, defined in section CSV common field 2150 elements (Section 4.7.2), MAY be used in the "contact" 2151 element: 2153 Identifier of client that created the contact object. 2155 Identifier of the client that last updated the 2156 contact object. 2158 Date and time of the last transfer for the contact 2159 object. 2161 Example of a "contact" element. 2163 ... 2164 2165 ... 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2186 contact-YYYYMMDD.csv 2187 2188 2189 2190 ... 2191 2192 ... 2194 Example of the contact-YYYYMMDD.csv file. The file contains nine 2195 object contact records. 2197 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2198 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2199 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2200 2009-11-26T09:10:00.0Z 2201 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2202 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2203 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2204 2009-11-26T09:10:00.0Z 2205 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2206 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2207 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2208 2009-11-26T09:10:00.0Z 2209 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2210 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2211 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2212 2009-11-26T09:10:00.0Z 2213 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2214 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2215 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2216 2009-11-26T09:10:00.0Z 2217 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2218 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2219 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2220 2009-11-26T09:10:00.0Z 2221 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2222 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2223 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2224 2009-11-26T09:10:00.0Z 2225 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2226 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2227 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2228 2009-11-26T09:10:00.0Z 2229 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2230 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2231 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2232 2009-11-26T09:10:00.0Z 2234 5.3.2.1.2. "contactStatuses" CSV File Definition 2236 The "contactStatuses" CSV File Definition defines the fields and CSV 2237 file references used for the contact object statuses. 2239 The following "csvContact" field elements, defined for the "contact" 2240 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2241 "contactStatuses" element: 2243 Server-unique contact identifier of status with 2244 isRequired="true". 2246 The status of the contact with 2247 type="contact:statusValueType" and isRequired="true". 2249 The following "rdeCsv" fields, defined in section CSV common field 2250 elements (Section 4.7.2), MAY be used in the "contactStatuses" 2251 element: 2253 The contact object status description 2254 which is free form text describing the rationale for the status. 2256 Language of the field. 2258 Example of a "contactStatuses" 2259 element. 2261 ... 2262 2263 ... 2264 2265 2266 2267 2268 2269 2270 2271 2272 2274 contactStatuses-YYYYMMDD.csv 2275 2276 2277 2278 ... 2279 2280 ... 2282 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2283 file contains the statuses for the nine contact identifiers. 2285 domain1admin,ok,, 2286 domain1tech,ok,, 2287 domain1billing,ok,, 2288 domain2admin,ok,, 2289 domain2tech,ok,, 2290 domain2billing,ok,, 2291 xnabc123admin,ok,, 2292 xnabc123tech,ok,, 2293 xnabc123billing,ok,, 2295 5.3.2.1.3. "contactPostal" CSV File Definition 2297 The "contactPostal" CSV File Definition defines the fields and CSV 2298 file references used for the contact postal info object records. 2300 The following "csvContact" field elements MUST be used in the 2301 "contactPostal" element: 2303 Contains the form of the postal-address 2304 information with type="contact:postalLineType" and 2305 isRequired="true". This field specifies the form ("int" or 2306 "loc"), as defined in Section 4.8, of the , 2307 , , , 2308 , , fields. 2310 Contains the contact's name of the individual or 2311 role represented by the contact with type="contact:postalLineType" 2312 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2313 indicate the localized or internationalized form as defined in 2314 section Section 4.8. 2316 Contains the contact's contact's street address 2317 line with type="contact:fPostalLineType". An index attribute is 2318 required to indicate which street address line the field 2319 represents with index "0" for the first line and index "2" for the 2320 last line. An OPTIONAL "isLoc" attribute to used to indicate the 2321 localized or internationalized form as defined in section 2322 Section 4.8. 2324 Contains the contact's city with 2325 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2326 "isLoc" attribute to used to indicate the localized or 2327 internationalized form as defined in section Section 4.8. 2329 Contains the contact's country code with 2330 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2331 attribute to used to indicate the localized or internationalized 2332 form as defined in section Section 4.8. 2334 The following "csvContact" field elements MAY be used in the 2335 "contactPostal" element: 2337 Contains the name of the organization with which 2338 the contact is affiliated with type="contact:optPostalLineType". 2339 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2340 internationalized form as defined in section Section 4.8. 2342 Contains the contact's state or province with 2343 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2344 to used to indicate the localized or internationalized form as 2345 defined in section Section 4.8. 2347 Contains the contact's postal code with 2348 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2349 indicate the localized or internationalized form as defined in 2350 section Section 4.8. 2352 The following "csvContact" fields, defined for the "contact" CSV File 2353 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2354 element: 2356 Server-unique contact identifier for the contact 2357 object with isRequired="true". 2359 Example of a "contactPostal" 2360 element. 2362 ... 2363 2364 ... 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2382 contactPostal-YYYYMMDD.csv 2383 2384 2385 2386 ... 2387 2388 ... 2390 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2391 nine contact postal records. 2393 domain1admin,int,"John Doe","Example Inc.", 2394 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2395 domain1tech,int,"John Doe","Example Inc.", 2396 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2397 domain1billing,int,"John Doe","Example Inc.", 2398 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2399 domain2admin,int,"John Doe","Example Inc.", 2400 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2401 domain2tech,int,"John Doe","Example Inc.", 2402 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2403 domain2billing,int,"John Doe","Example Inc.", 2404 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2405 xnabc123admin,int,"John Doe","Example Inc.", 2406 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2407 xnabc123tech,int,"John Doe","Example Inc.", 2408 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2409 xnabc123billing,int,"John Doe","Example Inc.", 2410 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2412 5.3.2.1.4. "contactTransfer" CSV File Definition 2414 The "contactTransfer" CSV File Definition defines the fields and CSV 2415 file references used for the contact object pending and completed 2416 transfer records. No additional field elements were added for use in 2417 the "contactTransfer" element. The 2418 following "rdeCsv" fields, defined in section CSV common field 2419 elements (Section 4.7.2), MUST be used in the "contactTransfer" 2420 element: 2422 State of the most recent transfer request with 2423 isRequired="true". 2425 Identifier of the registrar, defined in Section 5.4, 2426 of the client that requested the transfer with isRequired="true". 2428 Date and time that the transfer was requested with 2429 isRequired="true". 2431 Identifier of the registrar, defined in Section 5.4, 2432 of the client that should take or took action with 2433 isRequired="true". 2435 Date and time that the transfer action should be 2436 taken or has been taken with isRequired="true". 2438 The following "rdeCsv" fields, defined in section CSV common field 2439 elements (Section 4.7.2), MAY be used in the "contactTransfer" 2440 element: 2442 Identifier of client that requested the transfer. 2444 Identifier of client that should take or took action 2445 for transfer. 2447 The following "csvContact" fields, defined for the "contact" CSV File 2448 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2449 element: 2451 Server-unique contact identifier for the contact 2452 object with isRequired="true". 2454 Example of a "contactTransfer" 2455 element. 2457 ... 2458 2459 ... 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2474 contactTransfer-YYYYMMDD.csv 2475 2476 2477 2478 ... 2479 2480 ... 2482 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2483 one contact transfer record in pending status. 2485 xnabc123admin,clientApproved,registrarX,clientX, 2486 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2488 5.3.2.1.5. "contactDisclose" CSV File Definition 2490 The "contactDisclose" CSV File Definition defines the fields and CSV 2491 file references used for the contact disclose object records. 2493 The following "csvContact" field elements MAY be used in the 2494 "contactDisclose" element: 2496 Contains flag with a value of "true" or 2497 "1" (one) notes the preference to allow disclosure of the 2498 specified elements as an exception to the stated data-collection 2499 policy. A value of "false" or "0" (zero) notes a client 2500 preference to not allow disclosure of the specified elements as an 2501 exception to the stated data-collection policy with 2502 type="boolean". The additional fields define specific exceptional 2503 disclosure preferences based on the 2504 field. 2506 Exceptional disclosure preference flag 2507 for the localized form of the contact name with type="boolean". 2509 Exceptional disclosure preference flag 2510 for the internationalized form of the contact name with 2511 type="boolean". 2513 Exceptional disclosure preference flag 2514 for the localized form of the contact organization with 2515 type="boolean". 2517 Exceptional disclosure preference flag 2518 for the internationalized form of the contact organization with 2519 type="boolean". 2521 Exceptional disclosure preference flag 2522 for the localized form of the contact address with type="boolean". 2524 Exceptional disclosure preference flag 2525 for the internationalized form of the contact address with 2526 type="boolean". 2528 Exceptional disclosure preference flag 2529 of the contact voice telephone number with type="boolean". 2531 Exceptional disclosure preference flag of 2532 the contact facsimile telephone number with type="boolean". 2534 Exceptional disclosure preference flag 2535 of the contact email address with type="boolean". 2537 The following "csvContact" fields, defined for the "contact" CSV File 2538 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2539 element: 2541 Server-unique contact identifier for the contact 2542 object with isRequired="true". 2544 Example of a "contactDisclose" 2545 element. 2547 ... 2548 2549 ... 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2567 contactDisclose-YYYYMMDD.csv 2568 2569 2570 2571 ... 2572 2573 ... 2575 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2576 one disclosure records, disabling disclosure of voice, fax, and 2577 email. 2579 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2581 5.3.2.2. 2583 The is used to hold the deleted contact objects 2584 in a differential or incremental deposit. All the contact object 2585 data is deleted as part of a cascade delete. The 2586 is split into separate CSV file definitions 2587 using named elements with the "name" attribute. The 2588 following section defines the supported contact deletes CSV file 2589 definition. 2591 5.3.2.2.1. "contact" Deletes CSV File Definition 2593 The following "csvContact" field elements MUST be used in the deletes 2594 "contact" element: 2596 Contains the server-unique contact identifier with 2597 type="eppcom:clIDType" and isRequired="true". 2599 Example of a "contact" element. 2601 ... 2602 2603 ... 2604 2605 2606 2607 2608 2609 2611 contact-delete-YYYYMMDD.csv 2612 2613 2614 2615 ... 2616 2617 ... 2619 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2620 six contact records. 2622 domain1admin 2623 domain1tech 2624 domain1billing 2625 domain2admin 2626 domain2tech 2627 domain2billing 2629 5.4. Registrar Object 2631 The registrar object represents the sponsoring client for other 2632 objects, for operational purposes MAY be the registry operator. The 2633 registrar object supports both the XML Model and the CSV Model, 2634 defined in Section 2. The elements used for both models are defined 2635 in the following sections. 2637 5.4.1. XML Model 2639 There are two elements used in the data escrow of the registrar 2640 objects for the XML model including the , 2641 under the element, and the 2642 element, under the element. 2644 A element substitutes for the 2645 abstract element to define a 2646 concrete definition of a registrar. The 2647 element can be replaced by other 2648 domain definitions using the XML schema substitution groups feature. 2650 5.4.1.1. element 2652 The element contains the following child elements: 2654 o An element that contains the Registry-unique identifier of 2655 the registrar object. This has a superordinate relationship 2656 to a subordinate , or of domain, contact and 2657 host objects. 2659 o An element that contains the name of the registrar. 2661 o An OPTIONAL element that contains the ID assigned by 2662 ICANN. 2664 o An OPTIONAL element that contains the operational status 2665 of the registrar. Possible values are: ok, readonly and 2666 terminated. 2668 o Zero or two OPTIONAL elements that contain postal- 2669 address information. Two elements are provided so that address 2670 information can be provided in both internationalized and 2671 localized forms; a "type" attribute is used to identify the two 2672 forms. If an internationalized form (type="int") is provided, 2673 element content MUST be represented in a subset of UTF-8 that can 2674 be represented in the 7-bit US-ASCII character set. If a 2675 localized form (type="loc") is provided, element content MAY be 2676 represented in unrestricted UTF-8. The element 2677 contains the following child elements: 2679 * A element that contains address information associated 2680 with the registrar. The element contains the following 2681 child elements: 2683 + One, two, or three OPTIONAL elements that contain 2684 the registrar's street address. 2686 + A element that contains the registrar's city. 2688 + An OPTIONAL element that contains the registrar's state 2689 or province. 2691 + An OPTIONAL element that contains the registrar's 2692 postal code. 2694 + A element that contains the registrar's country code. 2696 o An OPTIONAL element that contains the registrar's voice 2697 telephone number. 2699 o An OPTIONAL element that contains the registrar's facsimile 2700 telephone number. 2702 o An OPTIONAL element that contains the registrar's email 2703 address. 2705 o An OPTIONAL element that contains the registrar's URL. 2707 o An OPTIONAL elements that contains whois information. 2708 The element contains the following child elements: 2710 * An OPTIONAL element that contains the name of the 2711 registrar WHOIS server listening on TCP port 43 as specified in 2712 [RFC3912]. 2714 * An OPTIONAL element that contains the name of the 2715 registrar WHOIS server listening on TCP port 80/443. 2717 o An OPTIONAL element that contains the date and time of 2718 registrar-object creation. 2720 o An OPTIONAL element that contains the date and time of 2721 the most recent RDE registrar-object modification. This element 2722 MUST NOT be present if the rdeRegistrar object has never been 2723 modified. 2725 Example of object: 2727 ... 2728 2729 RegistrarX 2730 Registrar X 2731 123 2732 ok 2733 2734 2735 123 Example Dr. 2736 Suite 100 2737 Dulles 2738 VA 2739 20166-6503 2740 US 2741 2742 2743 +1.7035555555 2744 +1.7035555556 2745 jdoe@example.test 2746 http://www.example.test 2747 2748 whois.example.test 2749 http://whois.example.test 2750 2751 2005-04-23T11:49:00.0Z 2752 2009-02-17T17:51:00.0Z 2753 2754 ... 2756 5.4.1.2. object 2758 The element contains the id of a registrar that 2759 was deleted. 2761 Example of object: 2763 ... 2764 2765 ... 2766 2767 agnt0001-TEST 2768 2769 ... 2770 2771 ... 2773 5.4.2. CSV Model 2775 For the CSV Model of the registrar object, the 2776 child element of the element 2777 is used to hold the new or updated registrar objects for the deposit. 2778 The child element of the element 2779 is used to hold the deleted or purged registrar objects for the 2780 deposit. Both the and 2781 elements contain one or more elements with a set of 2782 named CSV file definitions using the "name" attribute. 2784 Differential and incremental deposits are based on changes to the 2785 registrar objects. The updated registrar object data under the 2786 element is a cascade replace down all of the 2787 registrar CSV files starting with the parent "registrar" CSV File 2788 Definition (Section 5.4.2.1.1). The child CSV file definitions 2789 include a field. All the child CSV 2790 file definition data for the registrar objects in the parent 2791 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2792 deleted and then set using the data in the child CSV files. The 2793 deleted registrar object data under the 2794 element is a cascade delete starting from the "registrar" Deletes CSV 2795 File Definition (Section 5.4.2.2.1). 2797 5.4.2.1. 2799 The is used to hold the new or updated 2800 registrar object information for the deposit. The 2801 is split into separate CSV file definitions 2802 using named elements with the "name" attribute. The 2803 following sections include the supported contact CSV file 2804 definitions. 2806 5.4.2.1.1. "registrar" CSV File Definition 2808 The "registrar" CSV File Definition defines the fields and CSV file 2809 references used for the registrar object records. 2811 The following "csvRegistrar" field elements MUST be used in the 2812 "registrar" element: 2814 Contains the server-unique registrar identifier 2815 with type="eppcom:clIDType" and isRequired="true". 2817 Contains the name of the registrar with 2818 type="normalizedString" and isRequired="true". 2820 The following field elements MAY be used in the "registrar" 2821 element: 2823 Contains the status of the registrar with 2824 type="csvRegistrar:statusValueType". 2826 Contains the ID assigned by ICANN with 2827 type="positiveInteger". 2829 Contains the Whois URL of the registrar 2830 with type="anyURI". 2832 The following "rdeCsv" fields, defined in section CSV common field 2833 elements (Section 4.7.2), MAY be used in the "registrar" 2834 element: 2836 Created date and time of the registrar object. 2838 Date and time of the last update to the registrar 2839 object. 2841 URL for the registrar web home page. 2843 The following "csvContact" fields, defined in section Contact Object 2844 (Section 5.3), MAY be used in the "registrar" 2845 element: 2847 Registrar street address line with an "index" 2848 attribute that represents the order of the street address line 2849 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2850 indicate the localized or internationalized form, as defined in 2851 Section 4.8. 2853 Registrar city with an OPTIONAL "isLoc" attribute 2854 that is used to indicate the localized or internationalized form, 2855 as defined in Section 4.8. 2857 Registrar country code with an OPTIONAL "isLoc" 2858 attribute that is used to indicate the localized or 2859 internationalized form, as defined in Section 4.8. 2861 Registrar email address. 2863 Registrar state or province with an OPTIONAL 2864 "isLoc" attribute that is used to indicate the localized or 2865 internationalized form, as defined in Section 4.8. 2867 Registrar postal code with an OPTIONAL "isLoc" 2868 attribute that is used to indicate the localized or 2869 internationalized form, as defined in Section 4.8. 2871 Registrar voice telephone number. 2873 Registrar voice telephone number extension. 2875 Registrar facsimile telephone number. 2877 Registrar facsimile telephone number extension. 2879 Example of a "registrar" 2880 element. 2882 ... 2883 2884 ... 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2911 registrar-YYYYMMDD.csv 2912 2913 2914 2915 ... 2916 2917 ... 2919 Example of the registrar-YYYYMMDD.csv file. The file contains three 2920 registrar records. 2922 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 2923 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2924 +1.7035555556,,jdoe@example.test,http://www.example.test, 2925 http://whois.example.test,2005-04-23T11:49:00.0Z, 2926 2009-02-17T17:51:00.0Z 2927 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 2928 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2929 +1.7035555556,,jdoe@example.test,http://www.example.test, 2930 http://whois.example.test,2005-04-23T11:49:00.0Z, 2931 2009-02-17T17:51:00.0Z 2932 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 2933 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2934 +1.7035555556,,jdoe@example.test,http://www.example.test, 2935 http://whois.example.test,2005-04-23T11:49:00.0Z, 2936 2009-02-17T17:51:00.0Z 2938 5.4.2.2. 2940 The is used to hold the deleted registrar 2941 objects in a differential or incremental deposit. All the registrar 2942 object data is deleted as part of a cascade delete. The 2943 is split into separate CSV file definitions 2944 using named elements with the "name" attribute. The 2945 following section defines the supported registrar deletes CSV file 2946 definition. 2948 5.4.2.2.1. "registrar" Deletes CSV File Definition 2950 The following "csvRegistrar" field elements MUST be used in the 2951 deletes "registrar" element: 2953 Contains the server-unique registrar identifier 2954 with type="eppcom:clIDType" and isRequired="true". 2956 Example of a "registrar" element. 2958 ... 2959 2960 ... 2961 2962 2963 2964 2965 2966 2968 registrar-delete-YYYYMMDD.csv 2969 2970 2971 2972 ... 2973 2974 ... 2976 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 2977 one registrar record. 2979 registrarZ 2981 5.5. IDN Table Reference Object 2983 The Internationalized Domain Names (IDN) table reference object is a 2984 pseudo-object that is used to provide a short reference to the IDN 2985 Table and Policy used in IDN registrations. The IDN reference object 2986 supports both the XML and the CSV Model, defined in the Models 2987 (Section 2) section. The elements used for both models are defined 2988 in the following sections. 2990 5.5.1. XML Model 2992 There is one element used in the data escrow of the IDN table 2993 reference objects for the XML model that is the , 2994 under the element. 2996 5.5.1.1. object 2998 The contains the following elements. An "id" 2999 attribute is used to specify an identifier for the IDN table. 3001 o An element that contains the URL of the IDN table that is 3002 being referenced. 3004 o A element that contains the URL of the IDN policy 3005 document. If IDN variants are generated algorithmically, the 3006 policy document MUST define the algorithm and the state of the 3007 implicit generated IDN variants. For a list of suggested states 3008 for implicit IDN variants, please see [variantTLDsReport]. 3010 Example of object: 3012 ... 3013 3014 3015 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3016 3017 3018 http://registro.br/dominio/regras.html 3019 3020 3021 ... 3023 5.5.2. CSV Model 3025 The IDN domain names, defined in Section 5.1, MAY have references to 3026 the IDN language identifier using the field 3027 element. The IDN table reference object defines the mapping of a 3028 language identifier to a language table URL. The language table URL 3029 defines the character code points that can be used for the language 3030 identifier. The elements used for the IDN table reference object is 3031 defined in this section. The child element of the 3032 element is used to hold the new or updated IDN table 3033 reference objects for the deposit. The child 3034 element of the element is used to hold the deleted or 3035 purged IDN table reference objects for the deposit. Both the 3036 and elements contain one or more 3037 elements with a set of named CSV file definitions using 3038 the "name" attribute. 3040 5.5.2.1. 3042 The is used to hold the new or updated IDN table 3043 reference object information for the deposit. The 3044 is split into separate CSV file definitions using named 3045 elements with the "name" attribute. The following sections include 3046 the supported IDN table reference CSV file definitions. 3048 5.5.2.1.1. "idnLanguage" CSV File Definition 3050 The "idnLanguage" CSV File Definition defines the fields and CSV file 3051 references used for the IDN table reference object records. 3053 The following "rdeCsv" fields, defined in Section 4.7.2, MUST be used 3054 in the "idnLanguage" element: 3056 The language identifier that matches the values 3057 for the field element in the "domain" CSV 3058 File Definition (Section 5.1.2.1.1) files. The attribute 3059 isRequired MUST equal "true". 3061 URL that defines the character code points that can be 3062 used for the language defined by the field element. 3063 The attribute isRequired MUST equal "true". 3065 Example of a "idnLanguage" element. 3067 ... 3068 3069 ... 3070 3071 , 3072 3073 3074 3075 3076 3077 3079 idnLanguage-YYYYMMDD.csv 3080 3081 3082 3083 ... 3084 3085 ... 3087 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3088 contains two IDN language records. 3090 LANG-1, 3091 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3092 LANG-2, 3093 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3095 5.5.2.2. 3097 The is used to hold the deleted IDN table reference 3098 objects in a differential or incremental deposit. The 3099 is split into separate CSV file definitions using 3100 named elements with the "name" attribute. The following 3101 section defines the supported IDN table reference deletes CSV file 3102 definition. 3104 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3106 The following "idnLanguage" field elements MUST be used in the 3107 deletes "idnLanguage" element: 3109 The language identifier that matches the values 3110 for the field element in the "domain" CSV 3111 File Definition (Section 5.1.2.1.1) files. The attribute 3112 isRequired MUST equal "true". 3114 Example of a "idnLanguage" element. 3116 ... 3117 3118 ... 3119 3120 3121 3122 3123 3124 3126 idnLanguage-delete-YYYYMMDD.csv 3127 3128 3129 3130 ... 3131 3132 ... 3134 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3135 contains one IDN language record. 3137 LANG-2 3139 5.6. NNDN Object 3141 A NNDN (NNDN's not domain name) can be used to store registry 3142 reserved names or (blocked, withheld or mirrored) IDN variants. 3144 A NNDN is a lightweight domain-like object that is not linked 3145 directly to a Registrar (a mirroring NNDN is linked to a Registrar 3146 via the original name). 3148 A domain name can only exist as a domain name object or NNDN object, 3149 but not both. 3151 The NNDN object supports both the XML and the CSV Model, defined in 3152 the Models (Section 2) section. The elements used for both models 3153 are defined in the following sections. 3155 5.6.1. XML Model 3157 There are two elements used in the data escrow of the NNDN objects 3158 for the XML model including the , under the 3159 element, and the element, under the 3160 element. 3162 A element substitutes for the 3163 abstract element to define a concrete definition of a NNDN. The 3164 element can be replaced by other NNDN 3165 definitions using the XML schema substitution groups feature. 3167 5.6.1.1. object 3169 The element contains the following child elements: 3171 o An element that contains the fully qualified name of the 3172 NNDN. If the NNDN is an IDN, the ASCII Compatible Encoding (ACE) 3173 MUST be used. 3175 o An OPTIONAL element that contains the fully qualified name 3176 of the NNDN in Unicode character set. It MUST be provided if 3177 available. 3179 o An OPTIONAL element that references the IDN 3180 Table used for the NNDN. This corresponds to the "id" attribute 3181 of the element. This element MUST be present if the 3182 NNDN is an IDN. 3184 o An OPTIONAL element is used to indicate that the 3185 NNDN is used for an IDN variant. This element contains the domain 3186 name used to generate the IDN variant. 3188 o A element that indicates the state of the NNDN: 3189 blocked, withheld or mirrored. 3191 * If a NNDN is considered undesirable for registration (i.e., 3192 unavailable for allocation to anyone), then the NNDN will be 3193 tagged as "blocked". 3195 * If a NNDN is considered a potential registration of a domain 3196 object for a registrant, then the NNDN will be tagged as 3197 "withheld". This status is only used when the NNDN is used for 3198 an IDN variant. 3200 * If a NNDN is considered a mirrored IDN variant of a domain 3201 object, then the NNDN will be tagged as "mirrored". A 3202 mirroringNS attribute is used to specify if the mirrored IDN 3203 variant use the NS mirror mechanism. The default value of 3204 mirroringNS is true. If another mechanism such as DNAME is 3205 used, the value of mirroringNS attribute MUST be false. 3207 o A element that contains the date and time of the NNDN 3208 object creation. 3210 Example of object: 3212 ... 3213 3214 xn--exampl-gva.test 3215 pt-BR 3216 example1.test 3217 withheld 3218 2005-04-23T11:49:00.0Z 3219 3220 ... 3222 5.6.1.2. object 3224 The element contains the ACE of a NNDN that was 3225 deleted, i.e., the . 3227 Example of object: 3229 ... 3230 3231 ... 3232 3233 xn--pingino-q2a.test 3234 3235 ... 3236 3237 ... 3239 5.6.2. CSV Model 3241 For the CSV Model of the NNDN object, the child 3242 element of the element is used to hold the new or 3243 updated NNDN objects for the deposit. The child 3244 element of the element is used to hold the deleted or 3245 purged NNDN objects for the deposit. Both the and 3246 elements contain one or more elements 3247 with a set of named CSV file definitions using the 3248 "name" attribute. 3250 5.6.2.1. 3252 The is used to hold the new or updated NNDN object 3253 information for the deposit. The is split into 3254 separate CSV file definitions using named elements with 3255 the "name" attribute. The following sections include the supported 3256 NNDN CSV file definitions. 3258 5.6.2.1.1. "NNDN" CSV File Definition 3260 The "NNDN" CSV File Definition defines the fields and CSV file 3261 references used for the NNDN object records. 3263 The following "csvNNDN" field elements MUST be used in the "NNDN" 3264 element: 3266 ASCII Compatible Encoding (ACE) field of the NNDN 3267 with type="eppcom:labelType" and isRequired="true". 3269 State of the NNDN: blocked or withheld with 3270 type="rdeNNDN:nameState" and isRequired="true". See 3271 Section 5.6.1.1 for a description of the possible values for the 3272 element. 3274 The following field elements MAY be used in the "NNDN" 3275 element: 3277 Domain name used to generate the IDN variant 3278 with type="eppcom:labelType". 3280 Defines whether the "mirroring" 3281 uses the NS mirror mechanism, as described 3282 for the "mirroringNS" attribute in 3283 Section 5.6.1.1, with type="boolean". If the field element is not 3284 defined the default value is "true". 3286 The following "rdeCsv" fields, defined in section CSV common field 3287 elements (Section 4.7.2), MUST be used in the "domain" 3288 element: 3290 Created date and time of the NNDN object with 3291 isRequired="true". 3293 The following "rdeCsv" fields, defined in section CSV common field 3294 elements (Section 4.7.2), MAY be used in the "domain" 3295 element: 3297 Name of the NNDN in Unicode character set for the 3298 field element. 3300 IDN Table Identifier for the NNDN that matches 3301 an IDN Table Reference Object record, as defined in Section 5.5.2. 3303 Example of a "NNDN" element: 3305 ... 3306 3307 ... 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3320 NNDN-YYYYMMDD.csv 3321 3322 3323 3324 ... 3325 3326 ... 3328 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3329 contains two NNDN records for an IDN with one blocked variant and one 3330 mirrored variant. 3332 xn--abc456.test,LANG-1,xn--abc123.test, 3333 blocked,,2005-04-23T11:49:00.0Z 3334 xn--abc789.test,LANG-1,xn--abc123.test, 3335 mirrored,1,2005-04-23T11:49:00.0Z 3337 5.6.2.2. 3339 The is used to hold the deleted NNDN objects in a 3340 differential or incremental deposit. The is split 3341 into separate CSV file definitions using named elements 3342 with the "name" attribute. The following section defines the 3343 supported NNDN deletes CSV file definition. 3345 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3347 The following "NNDN" field elements MUST be used in the deletes 3348 "NNDN" element: 3350 ASCII Compatible Encoding (ACE) field of the NNDN 3351 with type="eppcom:labelType" and isRequired="true". 3353 Example of a "NNDN" element. 3355 ... 3356 3357 ... 3358 3359 3360 3361 3362 3363 3365 NNDN-delete-YYYYMMDD.csv 3366 3367 3368 3369 ... 3370 3371 ... 3373 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3374 contains one NNDN records. 3376 xn--abc456.test 3378 5.7. EPP Parameters Object 3380 The EPP Parameters Object is a pseudo-object that defines the set of 3381 object and object extension services supported by the registry, as 3382 defined in [RFC5730]. The EPP Parameters Object is only defined as 3383 XML but could be used in the XML model or CSV model. The EPP 3384 Parameters Object is defined using the 3385 element. The EPP Parameters Object SHOULD be included if the 3386 registry supports EPP. Only one EPP Parameters Object MUST exist at 3387 a certain point in time (watermark). 3389 The syntax and content of the children 3390 elements is as explained in section 2.4 of [RFC5730]. The children 3391 of the are as follows: 3393 o One or more elements that indicate the EPP versions 3394 supported by the registry. 3396 o One or more elements that indicate the identifiers of the 3397 text response languages supported by the registry's EPP server. 3399 o One or more elements that contain namespace URIs 3400 representing the objects that the registry's EPP server is capable 3401 of managing. 3403 o An OPTIONAL element that contains one or more 3404 elements that contain namespace URIs representing object 3405 extensions supported by the registry's EPP server. 3407 o A element that contains child elements used to describe the 3408 server's privacy policy for data collection and management. See 3409 section 2.4 of [RFC5730] for more details. 3411 Example of element object: 3413 ... 3414 3415 1.0 3416 en 3417 urn:ietf:params:xml:ns:domain-1.0 3418 3419 urn:ietf:params:xml:ns:contact-1.0 3420 3421 urn:ietf:params:xml:ns:host-1.0 3422 3423 3424 urn:ietf:params:xml:ns:rgp-1.0 3425 urn:ietf:params:xml:ns:secDNS-1.1 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 ... 3446 5.8. Policy Object 3448 The Policy object is a pseudo-object that is used to specify which 3449 OPTIONAL elements from the XML Model are REQUIRED based on the 3450 business model of the registry. For the CSV Model, the OPTIONAL 3451 "isRequired" attribute of the elements, defined in 3452 Section 4.7.1, is used to specify which OPTIONAL fields are REQUIRED 3453 based on the business model of the registry. 3455 5.8.1. object 3457 The OPTIONAL contains the following attributes: 3459 o An that defines that the referenced is 3460 REQUIRED. 3462 o that defines the XPath of the element referenced by 3463 . 3465 Example of object: 3467 ... 3468 3470 ... 3472 5.9. Header Object 3474 The Header Object is a pseudo-object that is used to specify the 3475 number of objects in the repository at a specific point in time 3476 (watermark) regardless of the type of deposit: differential, full or 3477 incremental. The Header Object is only defined as XML but one header 3478 object MUST always be present per escrow deposit regardless of using 3479 XML Model or CSV Model. The Header Object is defined using the 3480 element. 3482 5.9.1. object 3484 The contains the following elements: 3486 o A choice of one of the elements defined in the 3487 "repositoryTypeGroup" group element that indicates the unique 3488 identifier for the repository being escrowed. Possible elements 3489 are: 3491 * A element that defines TLD or the REGISTRY- 3492 CLASS DOMAIN NAME (RCDN) being escrowed in the case of a 3493 Registry data escrow deposit. For IDNs the A-Label is used 3494 [RFC5891]. 3496 * A element that defines the Registrar ID 3497 corresponding to a Registrar data escrow deposit. In the case 3498 of an ICANN-accredited Registrar, the 3499 element MUST be the IANA Registrar ID assigned by ICANN. 3501 * A element that defines the provider ID 3502 corresponding to a Privacy and Proxy Services Provider data 3503 escrow deposit. In the case of an ICANN-accredited Privacy and 3504 Proxy Services Provider, the element MUST be 3505 the unique ID assigned by ICANN. 3507 o A element that contains the number of objects in the SRS 3508 at a specific point in time (watermark) regardless of the type of 3509 deposit: differential, full or incremental. The element 3510 supports the following attributes: 3512 * A "uri" attribute reflects the XML namespace URI of the primary 3513 objects for the XML Model and CSV Model. For example, the 3514 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3515 domain name objects using the XML Model, and the "uri" is set 3516 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3517 objects using the CSV Model. 3519 * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS 3520 DOMAIN NAME (RCDN) of the objects included in the 3521 element. For IDNs the A-Label is used [RFC5891]. If the 3522 "rcdn" attribute is present, the value of the element 3523 must include only objects related to registrations in the same 3524 and lower levels. For example in a data escrow deposit for the 3525 .EXAMPLE TLD, a value of "example" in the "rcdn" attribute 3526 within the element indicates the number of objects in 3527 the TLD including objects in other RCDNs within the TLD, 3528 whereas a value of "com.example" indicates the number of 3529 elements for objects under "com.example" and lower levels. 3530 Omitting the "rcdn" attribute indicates that the total includes 3531 all objects of the specified "uri" in the repository (e.g. the 3532 TLD, Registrar, or PPSP). 3534 * An OPTIONAL "registrarId" attribute indicates the identifier of 3535 the sponsoring Registrar of the objects included in the 3536 element. In the case of an ICANN-accredited Registrar, the 3537 value MUST be the IANA Registrar ID assigned by ICANN. 3539 Example of object referencing only the XML Model 3540 objects: 3542 ... 3543 3544 test 3545 2 3547 1 3549 1 3551 1 3553 3554 1 3556 1 3558 1 3560 3561 3562 ... 3564 Example of object referencing the CSV and XML 3565 Model objects: 3567 ... 3568 3569 test 3570 2 3572 1 3574 1 3576 1 3578 3579 1 3581 1 3583 1 3585 3586 3587 ... 3589 6. RDE IDN Variants handling 3591 Depending on the Registration Policy of the Registry; for a domain 3592 name there may be multiple variant names. See [variantTLDsReport] 3593 for further detail on IDN variants. 3595 A registry could choose to escrow IDN variants as domains or NNDN 3596 objects. A specific IDN variant can be represented in the escrow 3597 deposit, as a domain or as a NNDN object, but not both. 3599 If using domain objects to represent IDN variants, the normal 3600 behavior during restoration of a SRS based on an escrow deposit is to 3601 restore the IDN variants as a mirrored variant. If the registration 3602 data of the IDN variant is different from the original name, the 3603 details of this specific implementation MUST be described in the IDN 3604 policy document. 3606 A NNDN or a domain name are explicit representations of an IDN 3607 variant while an IDN variant computed based on an algorithm is an 3608 implicit representation. Explicit representation of an IDN variant 3609 takes precedence over an implicit representation. 3611 7. Profile 3613 Different business models of registries exist, therefore the registry 3614 is responsible to define a profile that matches its particular 3615 business model. The profile mechanism allows a registry to extend 3616 this specification. 3618 A profile is the process of: 3620 1. Extending base objects with the mechanisms defined for XML and 3621 CSV models. 3623 * In the case of the XML model, abstract elements could be use 3624 to extend the following objects: , , , 3625 and using XML schema substitution groups 3626 feature. 3628 2. Defining a object to specify which OPTIONAL elements of 3629 this base specification is required based on the business model 3630 of the registry. An example is the element that is 3631 usually REQUIRED but it is specified as OPTIONAL in this 3632 specification to support existing business models. 3634 3. Adding new escrowed objects using the and 3635 elements. 3637 4. Providing the XML schemas to third parties that require them to 3638 validate the escrow deposits. 3640 8. Data escrow agent extended verification process 3642 The Data Escrow Agent MUST perform a extended verification process 3643 using the contents of the data escrow deposits to a point in time 3644 (watermark), last full plus all differentials or last full plus last 3645 incremental escrow deposits. The following are the minimum suggested 3646 tests: 3648 o Validate the escrow deposits using the definition agreed with the 3649 registry. 3651 * In the case of the XML model, the contents of the escrow 3652 deposits MUST be validated using the XML schemas of the 3653 profile. 3655 o Count the objects and validate that the number of objects is equal 3656 to the number objects reported in the
element of the 3657 escrow deposit of that point in time (watermark). 3659 o All contact objects linked to domain names MUST be present. 3661 o All registrars objects linked to other objects MUST be present. 3663 o A domain name exists as a domain name or NNDN, but not both. 3665 o The elements listed as required in the element MUST be 3666 present. 3668 o All idnTableRef definitions linked from other objects MUST be 3669 present. 3671 o If an EPP Parameters Object was escrowed in the past, one and only 3672 one EPP Parameters Object MUST be present. 3674 o The watermark is not in the future. 3676 9. Formal Syntax 3678 Schemas are presented here. 3680 9.1. RDE CSV Schema 3682 Copyright (c) 2012 IETF Trust and the persons identified as authors 3683 of the code. All rights reserved. 3685 Redistribution and use in source and binary forms, with or without 3686 modification, are permitted provided that the following conditions 3687 are met: 3689 o Redistributions of source code must retain the above copyright 3690 notice, this list of conditions and the following disclaimer. 3692 o Redistributions in binary form must reproduce the above copyright 3693 notice, this list of conditions and the following disclaimer in 3694 the documentation and/or other materials provided with the 3695 distribution. 3697 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3698 names of specific contributors, may be used to endorse or promote 3699 products derived from this software without specific prior written 3700 permission. 3702 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3703 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3704 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3705 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3706 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3707 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3708 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3709 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3710 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3711 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3712 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3714 BEGIN 3715 3717 3724 3727 3729 3732 3733 3734 Registry Data Escrow Comma-Seperated Values (CSV) 3735 3736 3738 3739 3741 3742 3743 3744 3745 3746 3747 3748 3749 3751 3752 3753 3754 3755 3756 3757 3759 3760 3763 3764 3765 3767 3768 3769 3770 3771 3772 3774 3776 3777 3778 3780 3781 3782 3783 3784 3785 3787 3789 3790 3791 3793 3795 3796 3798 3799 3800 3801 3802 3804 3805 3806 3807 3808 3809 3810 3811 3813 3814 3815 3817 3818 3820 3821 3822 3823 3824 3826 3827 3828 3830 3831 3833 3834 3835 3836 3837 3839 3840 3841 3843 3844 3848 3849 3850 3852 3854 3856 3857 3859 3861 3863 3864 3866 3868 3870 3872 3874 3876 3878 3880 3882 3883 3884 3885 3886 3888 3889 3890 3891 3892 3893 3894 3895 3898 3899 3900 3902 3903 3905 3907 3909 3910 3912 3913 3915 3917 3918 3919 3920 3921 3923 3924 3925 3926 3927 3928 3929 3930 3932 3933 3934 3936 3937 3938 3939 3940 3941 3943 3945 3946 3947 3948 3949 3950 3951 3953 3954 3955 3957 3958 3959 3960 3961 3962 3964 3965 3966 3967 3968 3969 3970 3971 3973 3974 3975 3977 3978 3979 3980 3981 3982 3984 3985 3986 3987 3988 3989 3990 3991 3994 3995 3996 3998 3999 4000 4001 4002 4003 4005 4006 4007 4008 4009 4010 4011 4012 4014 4015 4016 4018 4019 4021 4022 4023 4024 4025 4027 4028 4029 4031 4032 4035 4036 4038 4039 4040 4041 4042 4044 4045 4046 4048 4049 4050 4051 4052 4053 4055 4056 4057 4059 4060 4061 4062 4063 4064 4066 4067 4068 4070 4071 4072 4073 4074 4075 4077 4078 4079 4081 4082 4084 4085 4086 4087 4088 4089 4091 4092 4093 4095 4096 4097 4098 4099 4100 4102 4103 4104 4105 4107 4108 4110 4111 4112 4113 4114 4115 4117 4118 4119 4120 4122 4123 4125 4126 4127 4128 4129 4131 4132 4133 4135 4138 4139 END 4141 9.2. RDE Domain Object 4143 Copyright (c) 2011 IETF Trust and the persons identified as authors 4144 of the code. All rights reserved. 4146 Redistribution and use in source and binary forms, with or without 4147 modification, are permitted provided that the following conditions 4148 are met: 4150 o Redistributions of source code must retain the above copyright 4151 notice, this list of conditions and the following disclaimer. 4153 o Redistributions in binary form must reproduce the above copyright 4154 notice, this list of conditions and the following disclaimer in 4155 the documentation and/or other materials provided with the 4156 distribution. 4158 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4159 names of specific contributors, may be used to endorse or promote 4160 products derived from this software without specific prior written 4161 permission. 4163 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4164 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4165 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4166 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4167 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4168 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4169 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4170 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4171 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4172 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4173 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4175 BEGIN 4176 4177 4188 4189 4190 4191 4192 4193 4195 4196 4197 Registry Data Escrow Domain provisioning schema 4198 4199 4201 4204 4206 4210 4211 4212 4213 4214 4215 4217 4219 4221 4223 4225 4227 4230 4233 4236 4238 4240 4242 4244 4246 4248 4250 4252 4254 4257 4258 4259 4260 4262 4263 4264 4266 4268 4270 4272 4274 4276 4277 4279 4280 4281 4282 4283 4284 4287 4288 4289 4290 4291 4292 END 4294 9.3. CSV Domain Object 4296 Copyright (c) 2012 IETF Trust and the persons identified as authors 4297 of the code. All rights reserved. 4299 Redistribution and use in source and binary forms, with or without 4300 modification, are permitted provided that the following conditions 4301 are met: 4303 o Redistributions of source code must retain the above copyright 4304 notice, this list of conditions and the following disclaimer. 4306 o Redistributions in binary form must reproduce the above copyright 4307 notice, this list of conditions and the following disclaimer in 4308 the documentation and/or other materials provided with the 4309 distribution. 4311 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4312 names of specific contributors, may be used to endorse or promote 4313 products derived from this software without specific prior written 4314 permission. 4316 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4317 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4318 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4319 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4320 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4321 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4322 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4323 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4324 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4325 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4326 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4328 BEGIN 4329 4331 4342 4345 4347 4349 4351 4353 4355 4358 4359 4360 Domain Name Comma-Separated Values (CSV) Object 4361 4362 4364 4367 4370 4371 4372 4373 4374 4375 4376 4378 4379 4381 4384 4387 4388 4389 4390 4391 4392 4393 4394 4395 4397 4398 4401 4402 4405 4406 4407 4408 4409 4411 4412 4413 4415 4416 4419 4420 4421 4422 4423 4425 4426 4427 4429 4431 4432 4434 4435 4436 4437 4438 4440 4441 4442 4444 4445 4448 4449 4452 4453 4456 4457 4460 4461 4464 4465 4468 4469 4472 4473 4475 4476 4477 4478 4479 4481 4482 4483 4485 4486 4489 4490 4494 4495 4498 4499 4500 4501 4502 4503 4505 4506 4507 4509 4512 4513 END 4515 9.4. RDE Host Object 4517 Copyright (c) 2011 IETF Trust and the persons identified as authors 4518 of the code. All rights reserved. 4520 Redistribution and use in source and binary forms, with or without 4521 modification, are permitted provided that the following conditions 4522 are met: 4524 o Redistributions of source code must retain the above copyright 4525 notice, this list of conditions and the following disclaimer. 4527 o Redistributions in binary form must reproduce the above copyright 4528 notice, this list of conditions and the following disclaimer in 4529 the documentation and/or other materials provided with the 4530 distribution. 4532 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4533 names of specific contributors, may be used to endorse or promote 4534 products derived from this software without specific prior written 4535 permission. 4537 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4538 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4539 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4540 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4541 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4542 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4543 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4544 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4545 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4546 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4547 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4549 BEGIN 4550 4551 4559 4560 4561 4563 4564 4565 Registry Data Escrow Host provisioning schema 4566 4567 4568 4570 4571 4574 4575 4576 4577 4578 4579 4581 4583 4585 4588 4590 4592 4594 4596 4598 4600 4601 4602 4603 4605 4606 4607 4608 4609 4610 4612 4614 4615 4617 4618 4619 4620 END 4622 9.5. CSV Host Object 4624 Copyright (c) 2012 IETF Trust and the persons identified as authors 4625 of the code. All rights reserved. 4627 Redistribution and use in source and binary forms, with or without 4628 modification, are permitted provided that the following conditions 4629 are met: 4631 o Redistributions of source code must retain the above copyright 4632 notice, this list of conditions and the following disclaimer. 4634 o Redistributions in binary form must reproduce the above copyright 4635 notice, this list of conditions and the following disclaimer in 4636 the documentation and/or other materials provided with the 4637 distribution. 4639 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4640 names of specific contributors, may be used to endorse or promote 4641 products derived from this software without specific prior written 4642 permission. 4644 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4645 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4646 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4647 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4648 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4649 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4650 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4651 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4652 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4653 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4654 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4656 BEGIN 4657 4659 4668 4671 4673 4675 4677 4680 4681 4682 Host Comma-Separated Values (CSV) Object 4683 4684 4686 4689 4692 4693 4694 4695 4696 4697 4698 4699 4700 4702 4705 4708 4709 4710 4711 4712 4714 4715 4716 4717 4719 4720 4723 4724 4726 4727 4728 4729 4730 4732 4733 4734 4736 4737 4739 4740 4741 4742 4743 4745 4746 4747 4749 4750 4753 4754 4755 4756 4757 4758 4761 4762 4763 4765 4768 4769 END 4771 9.6. RDE Contact Object 4773 Copyright (c) 2011 IETF Trust and the persons identified as authors 4774 of the code. All rights reserved. 4776 Redistribution and use in source and binary forms, with or without 4777 modification, are permitted provided that the following conditions 4778 are met: 4780 o Redistributions of source code must retain the above copyright 4781 notice, this list of conditions and the following disclaimer. 4783 o Redistributions in binary form must reproduce the above copyright 4784 notice, this list of conditions and the following disclaimer in 4785 the documentation and/or other materials provided with the 4786 distribution. 4788 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4789 names of specific contributors, may be used to endorse or promote 4790 products derived from this software without specific prior written 4791 permission. 4793 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4794 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4795 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4796 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4797 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4798 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4799 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4800 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4801 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4802 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4803 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4805 BEGIN 4806 4807 4815 4816 4817 4818 4820 4821 4822 Registry Data Escrow contact provisioning schema 4823 4824 4826 4829 4831 4835 4836 4837 4838 4839 4840 4842 4844 4846 4848 4850 4852 4854 4856 4858 4860 4862 4864 4866 4868 4870 4871 4872 4873 4875 4876 4877 4878 4879 4880 4881 4882 4883 4885 4886 4887 4888 4889 4890 4893 4894 4895 4896 4897 4898 END 4900 9.7. CSV Contact Object 4902 Copyright (c) 2012 IETF Trust and the persons identified as authors 4903 of the code. All rights reserved. 4905 Redistribution and use in source and binary forms, with or without 4906 modification, are permitted provided that the following conditions 4907 are met: 4909 o Redistributions of source code must retain the above copyright 4910 notice, this list of conditions and the following disclaimer. 4912 o Redistributions in binary form must reproduce the above copyright 4913 notice, this list of conditions and the following disclaimer in 4914 the documentation and/or other materials provided with the 4915 distribution. 4917 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4918 names of specific contributors, may be used to endorse or promote 4919 products derived from this software without specific prior written 4920 permission. 4922 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4923 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4924 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4925 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4926 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4927 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4928 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4929 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4930 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4931 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4932 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4934 BEGIN 4935 4937 4946 4950 4952 4954 4956 4959 4960 4961 Contact Comma-Separated Values (CSV) Object 4962 4963 4965 4968 4971 4972 4973 4974 4975 4976 4977 4978 4979 4981 4984 4987 4988 4989 4990 4991 4992 4993 4994 4995 4997 4998 5000 5001 5002 5003 5004 5006 5007 5008 5010 5011 5015 5016 5018 5020 5021 5022 5023 5024 5026 5027 5028 5030 5031 5033 5036 5037 5039 5040 5041 5042 5043 5045 5046 5047 5049 5053 5055 5056 5057 5058 5059 5061 5062 5063 5065 5066 5067 5068 5069 5070 5072 5073 5074 5075 5077 5078 5079 5080 5081 5082 5084 5085 5086 5087 5088 5089 5092 5093 5096 5097 5098 5100 5101 5102 5103 5104 5106 5107 5108 5110 5111 5114 5115 5118 5119 5121 5122 5123 5124 5125 5127 5128 5129 5130 5132 5133 5135 5136 5137 5138 5139 5141 5142 5143 5144 5146 5147 5149 5151 5153 5155 5157 5159 5161 5163 5165 5167 5169 5171 5173 5175 5177 5179 5181 5183 5185 5187 5188 5189 5190 5191 5193 5194 5195 5197 5198 5201 5202 5203 5204 5205 5206 5208 5209 5210 5212 5215 5216 END 5218 9.8. RDE Registrar Object 5220 Copyright (c) 2011 IETF Trust and the persons identified as authors 5221 of the code. All rights reserved. 5223 Redistribution and use in source and binary forms, with or without 5224 modification, are permitted provided that the following conditions 5225 are met: 5227 o Redistributions of source code must retain the above copyright 5228 notice, this list of conditions and the following disclaimer. 5230 o Redistributions in binary form must reproduce the above copyright 5231 notice, this list of conditions and the following disclaimer in 5232 the documentation and/or other materials provided with the 5233 distribution. 5235 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5236 names of specific contributors, may be used to endorse or promote 5237 products derived from this software without specific prior written 5238 permission. 5240 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5241 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5242 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5243 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5244 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5245 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5246 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5247 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5248 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5249 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5250 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5252 BEGIN 5253 5254 5263 5264 5265 5266 5267 5269 5270 5271 Registry Data Escrow registrar provisioning schema 5272 5273 5275 5279 5281 5284 5285 5286 5287 5288 5289 5291 5293 5295 5297 5300 5302 5304 5306 5308 5310 5312 5314 5315 5316 5317 5319 5320 5321 5322 5323 5324 5326 5327 5328 5329 5330 5331 5332 5334 5335 5336 5338 5339 5342 5344 5345 5346 5347 5348 5349 5351 5352 5353 5356 5358 5361 5363 5365 5366 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 5378 5380 5381 5382 5383 5384 5386 5387 5388 5389 5390 5392 5393 5394 5396 5398 5399 5401 5402 5403 5404 5405 5406 5409 5410 5411 5412 5413 5414 END 5416 9.9. CSV Registrar Object 5418 Copyright (c) 2012 IETF Trust and the persons identified as authors 5419 of the code. All rights reserved. 5421 Redistribution and use in source and binary forms, with or without 5422 modification, are permitted provided that the following conditions 5423 are met: 5425 o Redistributions of source code must retain the above copyright 5426 notice, this list of conditions and the following disclaimer. 5428 o Redistributions in binary form must reproduce the above copyright 5429 notice, this list of conditions and the following disclaimer in 5430 the documentation and/or other materials provided with the 5431 distribution. 5433 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5434 names of specific contributors, may be used to endorse or promote 5435 products derived from this software without specific prior written 5436 permission. 5438 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5439 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5440 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5441 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5442 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5443 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5444 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5445 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5446 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5447 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5448 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5450 BEGIN 5451 5453 5463 5466 5468 5470 5472 5474 5477 5478 5479 Registar Comma-Separated Values (CSV) Object 5480 5481 5483 5486 5489 5490 5491 5492 5493 5494 5495 5496 5497 5499 5502 5505 5506 5507 5508 5509 5510 5511 5512 5513 5515 5516 5519 5520 5523 5524 5525 5526 5527 5528 5530 5531 5532 5533 5535 5536 5540 5541 5543 5545 5546 5547 5548 5549 5551 5552 5553 5555 5556 5557 5558 5559 5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 5570 5572 5573 5577 5580 5581 END 5583 9.10. RDE IDN Table Reference Objects 5585 Copyright (c) 2011 IETF Trust and the persons identified as authors 5586 of the code. All rights reserved. 5588 Redistribution and use in source and binary forms, with or without 5589 modification, are permitted provided that the following conditions 5590 are met: 5592 o Redistributions of source code must retain the above copyright 5593 notice, this list of conditions and the following disclaimer. 5595 o Redistributions in binary form must reproduce the above copyright 5596 notice, this list of conditions and the following disclaimer in 5597 the documentation and/or other materials provided with the 5598 distribution. 5600 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5601 names of specific contributors, may be used to endorse or promote 5602 products derived from this software without specific prior written 5603 permission. 5605 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5606 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5607 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5608 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5609 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5610 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5611 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5612 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5613 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5614 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5615 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5617 BEGIN 5618 5619 5625 5627 5628 5629 Registry Data Escrow IDN provisioning schema 5630 5631 5633 5635 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5651 5652 5653 5654 5655 5656 5657 5659 5660 5662 5663 5664 5665 5666 5667 5668 5670 5671 END 5673 9.11. CSV IDN Language Object 5675 Copyright (c) 2012 IETF Trust and the persons identified as authors 5676 of the code. All rights reserved. 5678 Redistribution and use in source and binary forms, with or without 5679 modification, are permitted provided that the following conditions 5680 are met: 5682 o Redistributions of source code must retain the above copyright 5683 notice, this list of conditions and the following disclaimer. 5685 o Redistributions in binary form must reproduce the above copyright 5686 notice, this list of conditions and the following disclaimer in 5687 the documentation and/or other materials provided with the 5688 distribution. 5690 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5691 names of specific contributors, may be used to endorse or promote 5692 products derived from this software without specific prior written 5693 permission. 5695 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5696 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5697 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5698 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5699 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5700 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5701 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5702 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5703 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5704 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5705 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5707 BEGIN 5708 5710 5717 5720 5722 5725 5726 5727 IDN Language Comma-Separated Values (CSV) Object 5728 5729 5731 5734 5737 5738 5739 5740 5741 5742 5743 5744 5745 5747 5750 5753 5754 5755 5756 5757 5758 5759 5760 5761 5763 5766 5767 END 5769 9.12. EPP Parameters Object 5771 Copyright (c) 2011 IETF Trust and the persons identified as authors 5772 of the code. All rights reserved. 5774 Redistribution and use in source and binary forms, with or without 5775 modification, are permitted provided that the following conditions 5776 are met: 5778 o Redistributions of source code must retain the above copyright 5779 notice, this list of conditions and the following disclaimer. 5781 o Redistributions in binary form must reproduce the above copyright 5782 notice, this list of conditions and the following disclaimer in 5783 the documentation and/or other materials provided with the 5784 distribution. 5786 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5787 names of specific contributors, may be used to endorse or promote 5788 products derived from this software without specific prior written 5789 permission. 5791 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5792 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5793 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5794 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5795 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5796 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5797 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5798 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5799 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5800 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5801 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5803 BEGIN 5804 5805 5813 5814 5815 5817 5818 5819 Registry Data Escrow EPP Parameters schema 5820 5821 5823 5824 5827 5828 5831 5832 5833 5834 5835 5837 5839 5841 5844 5846 5847 5848 5849 5850 5851 END 5853 9.13. NNDN Object 5855 Copyright (c) 2011 IETF Trust and the persons identified as authors 5856 of the code. All rights reserved. 5858 Redistribution and use in source and binary forms, with or without 5859 modification, are permitted provided that the following conditions 5860 are met: 5862 o Redistributions of source code must retain the above copyright 5863 notice, this list of conditions and the following disclaimer. 5865 o Redistributions in binary form must reproduce the above copyright 5866 notice, this list of conditions and the following disclaimer in 5867 the documentation and/or other materials provided with the 5868 distribution. 5870 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5871 names of specific contributors, may be used to endorse or promote 5872 products derived from this software without specific prior written 5873 permission. 5875 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5876 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5877 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5878 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5879 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5880 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5881 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5882 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5883 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5884 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5885 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5887 BEGIN 5888 5889 5897 5898 5899 5901 5902 5903 Registry Data Escrow NNDN provisioning schema 5904 5905 5907 5909 5910 5913 5914 5915 5916 5917 5918 5920 5922 5924 5926 5928 5930 5931 5932 5933 5935 5936 5937 5938 5939 5940 5941 5943 5944 5945 5946 5948 5949 5950 5952 5953 5954 5955 5956 5957 5960 5961 5962 5963 5964 5965 END 5967 9.14. CSV NNDN Object 5969 Copyright (c) 2013 IETF Trust and the persons identified as authors 5970 of the code. All rights reserved. 5972 Redistribution and use in source and binary forms, with or without 5973 modification, are permitted provided that the following conditions 5974 are met: 5976 o Redistributions of source code must retain the above copyright 5977 notice, this list of conditions and the following disclaimer. 5979 o Redistributions in binary form must reproduce the above copyright 5980 notice, this list of conditions and the following disclaimer in 5981 the documentation and/or other materials provided with the 5982 distribution. 5984 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5985 names of specific contributors, may be used to endorse or promote 5986 products derived from this software without specific prior written 5987 permission. 5989 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5990 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5991 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5992 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5993 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5994 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5995 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5996 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5997 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5998 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5999 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6001 BEGIN 6002 6004 6012 6015 6017 6019 6022 6023 6024 NNDN (NNDN's not domain name) (CSV) Object 6025 6026 6028 6031 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6046 6049 6050 6051 6052 6053 6054 6055 6056 6057 6059 6060 6063 6064 6067 6068 6072 6073 6076 6077 6078 6079 6080 6082 6083 6084 6086 6087 6090 6093 6094 END 6096 9.15. Policy Object 6098 Copyright (c) 2011 IETF Trust and the persons identified as authors 6099 of the code. All rights reserved. 6101 Redistribution and use in source and binary forms, with or without 6102 modification, are permitted provided that the following conditions 6103 are met: 6105 o Redistributions of source code must retain the above copyright 6106 notice, this list of conditions and the following disclaimer. 6108 o Redistributions in binary form must reproduce the above copyright 6109 notice, this list of conditions and the following disclaimer in 6110 the documentation and/or other materials provided with the 6111 distribution. 6113 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6114 names of specific contributors, may be used to endorse or promote 6115 products derived from this software without specific prior written 6116 permission. 6118 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6119 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6120 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6121 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6122 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6123 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6124 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6125 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6126 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6127 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6128 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6130 BEGIN 6131 6132 6138 6139 6140 Registry Data Escrow Policy schema 6141 6142 6144 6145 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 END 6159 9.16. Header Object 6161 Copyright (c) 2011 IETF Trust and the persons identified as authors 6162 of the code. All rights reserved. 6164 Redistribution and use in source and binary forms, with or without 6165 modification, are permitted provided that the following conditions 6166 are met: 6168 o Redistributions of source code must retain the above copyright 6169 notice, this list of conditions and the following disclaimer. 6171 o Redistributions in binary form must reproduce the above copyright 6172 notice, this list of conditions and the following disclaimer in 6173 the documentation and/or other materials provided with the 6174 distribution. 6176 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6177 names of specific contributors, may be used to endorse or promote 6178 products derived from this software without specific prior written 6179 permission. 6181 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6182 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6183 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6184 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6185 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6186 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6187 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6188 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6189 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6190 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6191 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6193 BEGIN 6194 6195 6202 6203 6205 6206 6207 Data Escrow Deposit Header schema 6208 6209 6211 6212 6215 6216 6217 6218 6219 6220 6221 6223 6224 6225 6227 6229 6230 6231 6232 6233 6234 6235 6237 6238 6239 6240 6241 6242 6243 6244 6245 6247 6248 END 6250 10. Internationalization Considerations 6252 Data Escrow deposits are represented in XML, which provides native 6253 support for encoding information using the Unicode character set and 6254 its more compact representations including UTF-8. Conformant XML 6255 processors recognize both UTF-8 and UTF-16. Though XML includes 6256 provisions to identify and use other character encodings through use 6257 of an "encoding" attribute in an declaration, use of UTF-8 is 6258 RECOMMENDED. 6260 11. IANA Considerations 6262 This document uses URNs to describe XML namespaces and XML schemas 6263 conforming to a registry mechanism described in [RFC3688]. Fourteen 6264 URI assignments have been registered by the IANA. 6266 Registration request for the RDE CSV namespace: 6268 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6270 Registrant Contact: See the "Author's Address" section of this 6271 document. 6273 XML: None. Namespace URIs do not represent an XML specification. 6275 Registration request for the RDE CSV XML schema: 6277 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6279 Registrant Contact: See the "Author's Address" section of this 6280 document. 6282 See the "Formal Syntax" section of this document. 6284 Registration request for the RDE domain namespace: 6286 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6288 Registrant Contact: See the "Author's Address" section of this 6289 document. 6291 XML: None. Namespace URIs do not represent an XML specification. 6293 Registration request for the RDE domain XML schema: 6295 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6297 Registrant Contact: See the "Author's Address" section of this 6298 document. 6300 See the "Formal Syntax" section of this document. 6302 Registration request for the CSV domain namespace: 6304 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6306 Registrant Contact: See the "Author's Address" section of this 6307 document. 6309 XML: None. Namespace URIs do not represent an XML specification. 6311 Registration request for the CSV domain XML schema: 6313 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6315 Registrant Contact: See the "Author's Address" section of this 6316 document. 6318 See the "Formal Syntax" section of this document. 6320 Registration request for the RDE host namespace: 6322 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6323 Registrant Contact: See the "Author's Address" section of this 6324 document. 6326 XML: None. Namespace URIs do not represent an XML specification. 6328 Registration request for the RDE host XML schema: 6330 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6332 Registrant Contact: See the "Author's Address" section of this 6333 document. 6335 See the "Formal Syntax" section of this document. 6337 Registration request for the CSV host namespace: 6339 URI: urn:ietf:params:xml:ns:csvHost-1.0 6341 Registrant Contact: See the "Author's Address" section of this 6342 document. 6344 XML: None. Namespace URIs do not represent an XML specification. 6346 Registration request for the CSV host XML schema: 6348 URI: urn:ietf:params:xml:schema:csvHost-1.0 6350 Registrant Contact: See the "Author's Address" section of this 6351 document. 6353 See the "Formal Syntax" section of this document. 6355 Registration request for the RDE contact namespace: 6357 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6359 Registrant Contact: See the "Author's Address" section of this 6360 document. 6362 XML: None. Namespace URIs do not represent an XML specification. 6364 Registration request for the RDE contact XML schema: 6366 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6368 Registrant Contact: See the "Author's Address" section of this 6369 document. 6371 See the "Formal Syntax" section of this document. 6373 Registration request for the CSV contact namespace: 6375 URI: urn:ietf:params:xml:ns:csvContact-1.0 6377 Registrant Contact: See the "Author's Address" section of this 6378 document. 6380 XML: None. Namespace URIs do not represent an XML specification. 6382 Registration request for the CSV contact XML schema: 6384 URI: urn:ietf:params:xml:schema:csvContact-1.0 6386 Registrant Contact: See the "Author's Address" section of this 6387 document. 6389 See the "Formal Syntax" section of this document. 6391 Registration request for the RDE registrar namespace: 6393 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6395 Registrant Contact: See the "Author's Address" section of this 6396 document. 6398 XML: None. Namespace URIs do not represent an XML specification. 6400 Registration request for the RDE registrar XML schema: 6402 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6404 Registrant Contact: See the "Author's Address" section of this 6405 document. 6407 See the "Formal Syntax" section of this document. 6409 Registration request for the CSV registrar namespace: 6411 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6413 Registrant Contact: See the "Author's Address" section of this 6414 document. 6416 XML: None. Namespace URIs do not represent an XML specification. 6418 Registration request for the CSV registrar XML schema: 6420 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6422 Registrant Contact: See the "Author's Address" section of this 6423 document. 6425 See the "Formal Syntax" section of this document. 6427 Registration request for the RDE IDN namespace: 6429 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6431 Registrant Contact: See the "Author's Address" section of this 6432 document. 6434 XML: None. Namespace URIs do not represent an XML specification. 6436 Registration request for the RDE IDN XML schema: 6438 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6440 Registrant Contact: See the "Author's Address" section of this 6441 document. 6443 See the "Formal Syntax" section of this document. 6445 Registration request for the CSV IDN namespace: 6447 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6449 Registrant Contact: See the "Author's Address" section of this 6450 document. 6452 XML: None. Namespace URIs do not represent an XML specification. 6454 Registration request for the CSV IDN XML schema: 6456 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6458 Registrant Contact: See the "Author's Address" section of this 6459 document. 6461 See the "Formal Syntax" section of this document. 6463 Registration request for the RDE NNDN namespace: 6465 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6466 Registrant Contact: See the "Author's Address" section of this 6467 document. 6469 XML: None. Namespace URIs do not represent an XML specification. 6471 Registration request for the RDE NNDN XML schema: 6473 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6475 Registrant Contact: See the "Author's Address" section of this 6476 document. 6478 See the "Formal Syntax" section of this document. 6480 Registration request for the CSV NNDN namespace: 6482 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6484 Registrant Contact: See the "Author's Address" section of this 6485 document. 6487 XML: None. Namespace URIs do not represent an XML specification. 6489 Registration request for the CSV NNDN XML schema: 6491 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6493 Registrant Contact: See the "Author's Address" section of this 6494 document. 6496 See the "Formal Syntax" section of this document. 6498 Registration request for the RDE EPP parameters namespace: 6500 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6502 Registrant Contact: See the "Author's Address" section of this 6503 document. 6505 XML: None. Namespace URIs do not represent an XML specification. 6507 Registration request for the RDE EPP parameters XML schema: 6509 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6511 Registrant Contact: See the "Author's Address" section of this 6512 document. 6514 See the "Formal Syntax" section of this document. 6516 12. Implementation Status 6518 Note to RFC Editor: Please remove this section and the reference to 6519 RFC 7942 [RFC7942] before publication. 6521 This section records the status of known implementations of the 6522 protocol defined by this specification at the time of posting of this 6523 Internet-Draft, and is based on a proposal described in RFC 7942 6524 [RFC7942]. The description of implementations in this section is 6525 intended to assist the IETF in its decision processes in progressing 6526 drafts to RFCs. Please note that the listing of any individual 6527 implementation here does not imply endorsement by the IETF. 6528 Furthermore, no effort has been spent to verify the information 6529 presented here that was supplied by IETF contributors. This is not 6530 intended as, and must not be construed to be, a catalog of available 6531 implementations or their features. Readers are advised to note that 6532 other implementations may exist. 6534 According to RFC 7942 [RFC7942], "this will allow reviewers and 6535 working groups to assign due consideration to documents that have the 6536 benefit of running code, which may serve as evidence of valuable 6537 experimentation and feedback that have made the implemented protocols 6538 more mature. It is up to the individual working groups to use this 6539 information as they see fit". 6541 12.1. Implementation in the gTLD space 6543 Organization: ICANN 6545 Name: ICANN Registry Agreement 6547 Description: the ICANN Base Registry Agreement requires Registries, 6548 Data Escrow Agents, and ICANN to implement this specification. ICANN 6549 receives daily notifications from Data Escrow Agents confirming that 6550 more than 1,200 gTLDs are sending deposits that comply with this 6551 specification. ICANN receives on a weekly basis per gTLD, from more 6552 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6553 also complies with this specification. In addition, ICANN is aware 6554 of Registry Service Provider transitions using data files that 6555 conform to this specification. 6557 Level of maturity: production. 6559 Coverage: all aspects of this specification are implemented. 6561 Version compatibility: versions 03 - 08 are known to be implemented. 6563 Contact: gustavo.lozano@icann.org 6565 URL: https://www.icann.org/resources/pages/registries/registries- 6566 agreements-en 6568 13. Security Considerations 6570 This specification does not define the security mechanisms to be used 6571 in the transmission of the data escrow deposits, since it only 6572 specifies the minimum necessary to enable the rebuilding of a 6573 Registry from deposits without intervention from the original 6574 Registry. 6576 Depending on local policies, some elements or most likely, the whole 6577 deposit will be considered confidential. As such the Registry 6578 transmitting the data to the Escrow Agent SHOULD take all the 6579 necessary precautions like encrypting the data itself and/or the 6580 transport channel to avoid inadvertent disclosure of private data. 6582 It is also of the utmost importance the authentication of the parties 6583 passing data escrow deposit files. The Escrow Agent SHOULD properly 6584 authenticate the identity of the Registry before accepting data 6585 escrow deposits. In a similar manner, the Registry SHOULD 6586 authenticate the identity of the Escrow Agent before submitting any 6587 data. 6589 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6590 checking mechanisms to ensure the data transmitted is what the source 6591 intended. Validation of the contents by the Escrow Agent is 6592 RECOMMENDED to ensure not only the file was transmitted correctly 6593 from the Registry, but also the contents are also "meaningful". 6595 14. Acknowledgments 6597 Parts of this document are based on EPP [RFC5730] and related RFCs by 6598 Scott Hollenbeck. 6600 Shoji Noguchi and Francisco Arias participated as co-authors until 6601 version 05 providing invaluable support for this document. 6603 15. Change History 6605 [[RFC Editor: Please remove this section.]] 6607 15.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6608 dnrd-objects-mapping-00 6610 1. Added definition for child elements under the element. 6612 2. Added definition for child elements under the element. 6614 3. Added definition for child elements under the element. 6616 4. Rewrote the IDN Variants Handling section to use the variant 6617 states as described in ICANN's Study of Issues Related to the 6618 Management of IDN Variant TLDs. 6620 5. Renamed to in the . 6622 6. Renamed to in the element. 6624 7. Renamed to in the element. 6626 8. Added element under element. 6628 9. Fixed some typographical errors and omissions. 6630 15.2. Changes from version 00 to 01 6632 1. Specify OPTIONAL elements in the draft. 6634 2. Added NNDN object to support list of reserved names and different 6635 IDN variants models. 6637 3. Removed subordinated host element from the domain object. 6639 4. Added eppParams object. 6641 5. Added variantGenerator element to the domain object. 6643 6. Added lgr to the IDN table object. 6645 15.3. Changes from version 01 to 02 6647 1. Updates to the all objects based on feedback from the list. 6649 2. Start of XML and CSV drafts merge. 6651 3. Added header object. 6653 4. Added report object. 6655 5. Added notification object. 6657 6. Added Data Escrow Agent Extended Verification Process section. 6659 7. Added Notifications from Registries to Third Parties. 6661 8. Added Notifications from Data Escrow Agents to Third Parties. 6663 9. Added FULL, DIFF deposit examples using the XML model only. 6665 15.4. Changes from version 02 to 03 6667 1. Remove authinfo from the XML Schema. 6669 2. Resend attribute is now an element 6671 3. Scope attribute added to policy object. 6673 15.5. Changes from version 03 to 04 6675 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6676 arias-noguchi-dnrd-objects-mapping-02. 6678 2. Changed the cksum attribute of to use CRC32 and 6679 changed all of the sample cksum values to use CRC32, based on 6680 feedback from David Kipling. 6682 3. Changed the optional element to be an optional 6683 "sep" attribute value of the element with a default 6684 value of "," based on feedback from David Kipling. 6686 4. Added support for the optional "parent" attribute for the to the 6687 CSV fields to indicate a field as a reference to a parent 6688 object, based on feedback from David Kipling. 6690 5. Added support for the CSV model for the NNDN. 6692 6. Added support to delete hosts based on roid. 6694 7. Added mirrored state to NNDN 6696 8. Minor fixes to XML XSDs. 6698 9. The Report and Notification objects were moved to draft-lozano- 6699 icann-registry-interfaces 6701 10. The section Data escrow notifications was moved to draft-lozano- 6702 icann-registry-interfaces 6704 11. Removed references to the , , and 6705 from the "hostStatuses" and "hostAddresses" CSV 6706 files. 6708 12. Removed references to the , , and 6709 from the "contactStatuses" CSV file. 6711 13. Removed references to the , , and 6712 from the "domainContacts", "domainStatuses", 6713 and "domainNameServers" CSV files. 6715 14. Changed to . 6717 15. Replaced use of to new field 6718 in the "domain", "idnLanguage", and "NNDN" CSV files. 6720 16. Replaced use of with in the 6721 "host" element. 6723 17. Changed the foreign key of the hosts to use 6724 instead of and removed use of in 6725 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6726 files. 6728 18. Added use of the MUST keyword for CSV fields that are required 6729 to be supported in an EPP based system. 6731 19. Removed use of the field element for the 6732 "registrar" CSV file. 6734 20. Added definition of field element. 6736 15.6. Changes from version 04 to 05 6738 1. Updated the examples of the full and differential deposits using 6739 the CSV and XML model. 6741 2. Made optional for the "domainTransfer" CSV file 6742 to match the XML definition. 6744 3. Made optional for the "domain" CSV file 6745 to match the XML definition. 6747 4. Made optional for the "domain" and "contact" CSV 6748 files to match the XML definition. 6750 5. Change from IDREF to idType. 6752 6. Minor editorial changes. 6754 15.7. Changes from version 05 to 06 6756 1. Revised the differential and incremental deposits for the CSV 6757 format to use cascade update / replace and delete from the parent 6758 object to be consistent with the XML format. 6760 2. Revised the structure of the CSV format sections to utilize sub- 6761 sections instead of a list for the CSV file definitions. 6763 3. Added the "CSV Parent Child Relationship" section to describe the 6764 concept of parent child relationships across CSV file 6765 definitions. 6767 4. Added the "domainNameServersAddresses" CSV File Definition 6768 section to support the domain host attributes model of [RFC5731]. 6770 5. Made the required fields in the CSV format consistent with the 6771 XML format. The CSV fields updated to be required include: 6772 , , , 6773 , , , 6774 , , , 6775 , , , 6776 , , 6777 , , , 6778 , , 6779 , and . 6781 6. Revised the CSV examples to use a more realistic set of records. 6783 15.8. Changes from version 06 to 07 6785 1. Created "repositoryTypeGroup" group element in the rdeHeader 6786 including the , and 6787 elements. 6789 2. Added the optional "rcdn" and "registrarId" attributes to the 6790 element 6792 15.9. Changes from version 07 to 08 6794 1. The following registrar elements were made optional to support 6795 greater flexibility for the implementation of policies: status, 6796 postalInfo, email and crDate. 6798 2. The following domain name elements were made optional to support 6799 greater flexibility for the implementation of policies: crRr. 6801 15.10. Changes from version 08 to 09 6803 1. Implementation Status section was added 6805 15.11. Changes from version 09 to 10 6807 1. Editorial changes in section Section 5.1.2.1.6. 6809 2. Added MAY clause when the DS Data Interface is used in section 6810 Section 5.1.2.1.6. 6812 15.12. Changes from version 10 to 00 6814 1. Internet Draft (I-D) adopted by the REGEXT WG. 6816 16. Example of a full deposit using the XML model 6818 Example of a full deposit using the XML model: 6820 6821 6837 2010-10-17T00:00:00Z 6838 6839 1.0 6840 urn:ietf:params:xml:ns:rdeHeader-1.0 6841 6842 urn:ietf:params:xml:ns:rdeContact-1.0 6843 6844 urn:ietf:params:xml:ns:rdeHost-1.0 6845 6846 urn:ietf:params:xml:ns:rdeDomain-1.0 6847 6848 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6849 6850 urn:ietf:params:xml:ns:rdeIDN-1.0 6851 6852 urn:ietf:params:xml:ns:rdeNNDN-1.0 6853 6854 urn:ietf:params:xml:ns:rdeEppParams-1.0 6855 6856 6858 6859 6860 6861 6862 test 6863 2 6865 6866 1 6868 6869 1 6871 6872 1 6874 6875 1 6877 6878 1 6880 6881 1 6883 6884 6886 6887 6888 example1.test 6889 Dexample1-TEST 6890 6891 jd1234 6892 sh8013 6893 sh8013 6894 6895 ns1.example.com 6896 ns1.example1.test 6898 6899 RegistrarX 6900 RegistrarX 6901 1999-04-03T22:00:00.0Z 6902 2015-04-03T22:00:00.0Z 6903 6905 6906 6907 example2.test 6908 Dexample2-TEST 6909 6910 6911 jd1234 6912 sh8013 6913 sh8013 6914 RegistrarX 6915 RegistrarX 6916 1999-04-03T22:00:00.0Z 6917 2015-04-03T22:00:00.0Z 6918 6920 6921 6922 ns1.example1.test 6923 Hns1_example_test-TEST 6924 6925 6926 192.0.2.2 6927 192.0.2.29 6928 1080:0:0:0:8:800:200C:417A 6929 6930 RegistrarX 6931 RegistrarX 6932 1999-05-08T12:10:00.0Z 6933 RegistrarX 6934 2009-10-03T09:34:00.0Z 6935 6937 6938 6939 sh8013 6940 Csh8013-TEST 6941 6942 6943 6944 John Doe 6945 Example Inc. 6946 6947 123 Example Dr. 6948 Suite 100 6949 Dulles 6950 VA 6951 20166-6503 6952 US 6953 6954 6955 +1.7035555555 6956 6957 +1.7035555556 6958 6959 jdoe@example.test 6960 6961 RegistrarX 6962 RegistrarX 6963 6964 2009-09-13T08:01:00.0Z 6965 6966 RegistrarX 6967 6968 2009-11-26T09:10:00.0Z 6969 6970 2009-12-03T09:05:00.0Z 6971 6972 6973 6974 6975 6976 6978 6979 6980 RegistrarX 6981 Registrar X 6982 123 6983 ok 6984 6985 6986 123 Example Dr. 6987 6988 Suite 100 6989 6990 Dulles 6991 VA 6992 20166-6503 6993 US 6995 6996 6997 +1.7035555555 6998 6999 +1.7035555556 7000 7001 jdoe@example.test 7002 7003 http://www.example.test 7004 7005 7006 whois.example.test 7007 7008 http://whois.example.test 7009 7010 7011 2005-04-23T11:49:00.0Z 7012 7013 2009-02-17T17:51:00.0Z 7014 7015 7017 7018 7019 7020 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 7021 7022 7023 http://registro.br/dominio/regras.html 7024 7025 7027 7028 7029 xn--exampl-gva.test 7030 pt-BR 7031 example1.test 7032 withheld 7033 2005-04-23T11:49:00.0Z 7034 7036 7037 7038 1.0 7039 en 7040 7041 urn:ietf:params:xml:ns:domain-1.0 7042 7043 7044 urn:ietf:params:xml:ns:contact-1.0 7045 7046 7047 urn:ietf:params:xml:ns:host-1.0 7048 7049 7050 urn:ietf:params:xml:ns:rgp-1.0 7051 7052 urn:ietf:params:xml:ns:secDNS-1.1 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7075 7076 7078 17. Example of differential deposit using the XML model 7080 Example of a differential deposit using the XML model: 7082 7083 7098 2010-10-17T00:00:00Z 7099 7100 1.0 7101 urn:ietf:params:xml:ns:rdeHeader-1.0 7102 7103 urn:ietf:params:xml:ns:rdeContact-1.0 7104 7105 urn:ietf:params:xml:ns:rdeHost-1.0 7106 7107 urn:ietf:params:xml:ns:rdeDomain-1.0 7108 7109 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7110 7111 urn:ietf:params:xml:ns:rdeIDN-1.0 7112 7113 urn:ietf:params:xml:ns:rdeNNDN-1.0 7114 7115 urn:ietf:params:xml:ns:rdeEppParams-1.0 7116 7117 7119 7120 7121 7122 example2.test 7123 7124 7126 7127 7128 7129 7130 test 7131 1 7133 7134 1 7136 7137 1 7139 7140 1 7142 7143 1 7145 7146 1 7148 7149 1 7151 7152 7153 7154 7156 18. Example of a full deposit using the CSV model 7158 Example of a full deposit using the CSV model: 7160 7161 7175 2010-10-18T00:00:00Z 7176 7177 1.0 7178 urn:ietf:params:xml:ns:csvDomain-1.0 7179 urn:ietf:params:xml:ns:csvHost-1.0 7180 urn:ietf:params:xml:ns:csvContact-1.0 7181 urn:ietf:params:xml:ns:csvRegistrar-1.0 7182 urn:ietf:params:xml:ns:csvIDN-1.0 7183 urn:ietf:params:xml:ns:csvNNDN-1.0 7184 urn:ietf:params:xml:ns:rdeEppParams-1.0 7185 7186 7187 7188 test 7189 7190 4 7191 7192 7193 6 7194 7195 7196 9 7197 7198 7199 3 7200 7201 7202 2 7203 7204 7205 2 7206 7207 7208 1 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7231 domain-YYYYMMDD.csv 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7244 domainContacts-YYYYMMDD.csv 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7259 domainStatuses-YYYYMMDD.csv 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7271 domainNameServers-name-YYYYMMDD.csv 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7283 domainNameServers-roid-YYYYMMDD.csv 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7299 dnssec-ds-YYYYMMDD.csv 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7315 dnssec-key-YYYYMMDD.csv 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7334 domainTransfer-YYYYMMDD.csv 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7356 host-YYYYMMDD.csv 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7370 hostStatuses-YYYYMMDD.csv 7371 7372 7373 7374 7375 7376 7377 7378 7380 7381 7382 7384 hostAddresses-YYYYMMDD.csv 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7410 contact-YYYYMMDD.csv 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7424 contactStatuses-YYYYMMDD.csv 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7445 contactPostal-YYYYMMDD.csv 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7463 contactTransfer-YYYYMMDD.csv 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7484 contactDisclose-YYYYMMDD.csv 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7516 registrar-YYYYMMDD.csv 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7530 idnLanguage-YYYYMMDD.csv 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7548 NNDN-YYYYMMDD.csv 7549 7550 7551 7552 7553 7554 1.0 7555 en 7556 urn:ietf:params:xml:ns:domain-1.0 7557 7558 urn:ietf:params:xml:ns:host-1.0 7559 7560 urn:ietf:params:xml:ns:contact-1.0 7561 7562 7563 urn:ietf:params:xml:ns:secDNS-1.1 7564 7565 urn:ietf:params:xml:ns:rgp-1.0 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7592 19. Example of differential deposit using the CSV model 7594 Example of a differential deposit using the CSV model: 7596 7597 7611 2010-10-18T00:00:00Z 7612 7613 1.0 7614 urn:ietf:params:xml:ns:csvDomain-1.0 7615 urn:ietf:params:xml:ns:csvHost-1.0 7616 urn:ietf:params:xml:ns:csvContact-1.0 7617 urn:ietf:params:xml:ns:csvRegistrar-1.0 7618 urn:ietf:params:xml:ns:csvIDN-1.0 7619 7620 7621 7622 7623 7624 7625 7626 7627 7629 domain-delete-YYYYMMDD.csv 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7642 host-delete-YYYYMMDD.csv 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7655 contact-delete-YYYYMMDD.csv 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7668 registrar-delete-YYYYMMDD.csv 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7681 idnLanguage-delete-YYYYMMDD.csv 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7694 NNDN-delete-YYYYMMDD.csv 7695 7696 7697 7698 7699 7700 7701 7702 test 7703 7704 2 7705 7706 7707 2 7708 7709 7710 3 7711 7712 7713 1 7714 7715 7716 1 7717 7718 7719 1 7720 7721 7722 1 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7745 domain-YYYYMMDD.csv 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7758 domainContacts-YYYYMMDD.csv 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7773 domainStatuses-YYYYMMDD.csv 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7785 domainNameServers-name-YYYYMMDD.csv 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7797 domainNameServers-roid-YYYYMMDD.csv 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7813 dnssec-ds-YYYYMMDD.csv 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7829 dnssec-key-YYYYMMDD.csv 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7848 domainTransfer-YYYYMMDD.csv 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7870 host-YYYYMMDD.csv 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7884 hostStatuses-YYYYMMDD.csv 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7897 hostAddresses-YYYYMMDD.csv 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7923 contact-YYYYMMDD.csv 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7937 contactStatuses-YYYYMMDD.csv 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7958 contactPostal-YYYYMMDD.csv 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7976 contactTransfer-YYYYMMDD.csv 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7997 contactDisclose-YYYYMMDD.csv 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8029 registrar-YYYYMMDD.csv 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8043 idnLanguage-YYYYMMDD.csv 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8061 NNDN-YYYYMMDD.csv 8062 8063 8064 8065 8066 8067 1.0 8068 en 8069 urn:ietf:params:xml:ns:domain-1.0 8070 8071 urn:ietf:params:xml:ns:host-1.0 8072 8073 urn:ietf:params:xml:ns:contact-1.0 8074 8075 8076 urn:ietf:params:xml:ns:secDNS-1.1 8077 8078 urn:ietf:params:xml:ns:rgp-1.0 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8101 8102 8103 8104 8106 20. References 8108 20.1. Normative References 8110 [ISO-3166-1] 8111 3166, I. S., "Codes for the representation of names of 8112 countries and their subdivisions -- Part 1: Country 8113 codes", ISO Standard 3166, November 2006. 8115 [ITU-E164] 8116 International Telecommunication Union, "The international 8117 public telecommunication numbering plan", ITU-T 8118 Recommendation E.164, February 2005. 8120 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8121 Requirement Levels", BCP 14, RFC 2119, 8122 DOI 10.17487/RFC2119, March 1997, 8123 . 8125 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8126 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8127 . 8129 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8130 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8131 DOI 10.17487/RFC3915, September 2004, 8132 . 8134 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8135 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8136 . 8138 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8139 Domain Name Mapping", STD 69, RFC 5731, 8140 DOI 10.17487/RFC5731, August 2009, 8141 . 8143 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8144 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8145 August 2009, . 8147 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8148 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8149 August 2009, . 8151 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8152 Security Extensions Mapping for the Extensible 8153 Provisioning Protocol (EPP)", RFC 5910, 8154 DOI 10.17487/RFC5910, May 2010, 8155 . 8157 20.2. Informative References 8159 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8160 DOI 10.17487/RFC0791, September 1981, 8161 . 8163 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8164 DOI 10.17487/RFC3688, January 2004, 8165 . 8167 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8168 DOI 10.17487/RFC3912, September 2004, 8169 . 8171 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8172 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8173 2006, . 8175 [RFC5891] Klensin, J., "Internationalized Domain Names in 8176 Applications (IDNA): Protocol", RFC 5891, 8177 DOI 10.17487/RFC5891, August 2010, 8178 . 8180 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8181 Code: The Implementation Status Section", BCP 205, 8182 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8183 . 8185 [variantTLDsReport] 8186 Internet Corporation for Assigned Names and Numbers 8187 (ICANN), "A Study of Issues Related to the Management of 8188 IDN Variant TLDs", February 2012, 8189 . 8192 20.3. URIs 8194 [1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data- 8195 escrow-05.txt 8197 Authors' Addresses 8199 Gustavo Lozano 8200 Internet Corporation for Assigned Names and Numbers 8201 12025 Waterfront Drive, Suite 300 8202 Los Angeles 90292 8203 United States of America 8205 Phone: +1.310.823.9358 8206 Email: gustavo.lozano@icann.org 8208 James Gould 8209 VeriSign, Inc. 8210 12061 Bluemont Way 8211 Reston 20190 8212 United States of America 8214 Email: jgould@verisign.com 8216 Chethan Thippeswamy 8217 VeriSign, Inc. 8218 12061 Bluemont Way 8219 Reston 20190 8220 United States of America 8222 Email: cthippeswamy@verisign.com