idnits 2.17.1 draft-ietf-regext-dnrd-objects-mapping-01.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 (Aug 26, 2019) is 1697 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 8226 -- 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: February 27, 2020 C. Thippeswamy 6 VeriSign 7 Aug 26, 2019 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-ietf-regext-dnrd-objects-mapping-01 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 February 27, 2020. 35 Copyright Notice 37 Copyright (c) 2019 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 55 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5 56 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 5 57 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . 102 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. Privacy Considerations . . . . . . . . . . . . . . . . . . . 145 101 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 145 102 16. Change History . . . . . . . . . . . . . . . . . . . . . . . 146 103 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 104 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 146 105 16.2. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 146 106 16.3. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 147 107 16.4. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 147 108 16.5. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 147 109 16.6. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 148 110 16.7. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 149 111 16.8. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 149 112 16.9. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 150 113 16.10. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 150 114 16.11. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 150 115 16.12. Changes from 10 to REGEXT 00 . . . . . . . . . . . . . . 150 116 16.13. Changes REGEXT 00 to REGEXT 01 . . . . . . . . . . . . . 150 117 17. Example of a full deposit using the XML model . . . . . . . . 150 118 18. Example of differential deposit using the XML model . . . . . 156 119 19. Example of a full deposit using the CSV model . . . . . . . . 157 120 20. Example of differential deposit using the CSV model . . . . . 166 121 21. References . . . . . . . . . . . . . . . . . . . . . . . . . 177 122 21.1. Normative References . . . . . . . . . . . . . . . . . . 177 123 21.2. Informative References . . . . . . . . . . . . . . . . . 178 124 21.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 179 125 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 179 127 1. Introduction 129 This document defines the data escrow structure of the standard set 130 of objects for a Domain Name Registry which include: 132 o Domain: Internet domain names that are typically provisioned in a 133 Domain Name Registry using the EPP domain name mapping [RFC5731]. 134 The attributes defined in the EPP domain name mapping [RFC5731] 135 are fully supported by this document. 137 o Host: Internet host names that are typically provisioned in a 138 Domain Name Registry using the EPP host mapping [RFC5732]. The 139 attributes defined in the EPP host mapping [RFC5732] are fully 140 supported by this document. 142 o Contact: Individual or organization social information provisioned 143 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 144 The attributes defined in the EPP contact mapping [RFC5733] are 145 fully supported by this document. 147 o Registrar: The organization that sponsors objects like domains, 148 hosts, and contacts in a Domain Name Registry. 150 o NNDN (NNDN's not domain name): A lightweight domain-like object 151 that is not linked to a Registrar. 153 This document defines the following pseudo-objects: 155 o IDN Table Reference: Internationalized Domain Names (IDN) included 156 in the Domain Object Data Escrow include references to the IDN 157 Table and Policy used in IDN registration. 159 o EPP parameters: Definition of the specific EPP parameters 160 supported by the Registry Operator. 162 o Header: Used to specify counters of objects in the database at a 163 certain point in time (watermark). 165 o Policy: Used to specify OPTIONAL elements from this specification 166 that are REQUIRED based on the business model of the registry. 168 2. Models 170 This document defines two different models that can be used to 171 deposit data escrow objects: 173 o XML: The XML model includes all the deposit information (meta-data 174 and data) in an XML document. The definition of the XML format is 175 fully defined in the XML schemas. As a convention, the objects 176 represented using the XML model are referenced using RDE and an 177 XML namespace that is prefixed with "rde". For example, the 178 Domain Name object represented using the XML model can be referred 179 to as the RDE Domain Name with the XML namespace including 180 rdeDomain (urn:ietf:params:xml:ns:rdeDomain-1.0). 182 o CSV: The CSV model uses XML to define the data escrow format of 183 the data contained in referenced Comma-Separated Values (CSV) 184 files. As a convention, the objects represented using the CSV 185 model is referenced using CSV and an XML namespace that is 186 prefixed with "csv". For example, the Domain Name object 187 represented using the CSV model can be referred to as the CSV 188 Domain Name with the XML namespace including csvDomain 189 (urn:ietf:params:xml:ns:csvDomain-1.0). 191 The data escrow deposit MAY contain a mix of both models but an 192 object MUST be escrowed only in one model. 194 3. Terminology 196 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 197 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 198 document are to be interpreted as described in BCP 14, [RFC2119]. 200 REGISTRY. In the context of this draft the definition will be 201 overloaded (from the definition in the base protocol) to indicate an 202 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 203 NAME. 205 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 206 or any other domain name at any level in the DNS tree for which a 207 Registry (either directly or through and affiliate company) provides 208 Registry Services for other organizations or individuals. For 209 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 211 REGISTRY SERVICES. Services offered by the Registry critical to the 212 following tasks: the provisioning of domain names on receipt of 213 requests and data from registrars; responding to registrar queries 214 for status information relating to the DNS servers for the RCDN; 215 dissemination of RCDN zone files; operation of the Registry DNS 216 servers; and responding to queries for contact and other information 217 concerning DNS registrations in the RCDN. Any other products or 218 services that only a Registry is capable of providing, by reason of 219 its designation as the Registry. Typical examples of Registry 220 Services are: DNS resolution for the RCDN, WHOIS and EPP. 222 ALLOCATED. A status of some label with respect to a zone, whereby 223 the label is associated administratively to some entity that has 224 requested the label. This term (and its cognates "allocation" and 225 "to allocate") may represents the first step on the way to delegation 226 in the DNS. 228 4. General Conventions 230 4.1. Date and Time 232 Numerous fields indicate "dates", such as the creation and expiry 233 dates for domain names. These fields SHALL contain timestamps 234 indicating the date and time in UTC as specified in [RFC3339], with 235 no offset from the zero meridian. 237 4.2. Country names 239 Country identifiers SHALL be represented using two character 240 identifiers as specified in [ISO-3166-1]. 242 4.3. Telephone numbers 244 Telephone numbers (both voice and facsimile) SHALL be formatted based 245 on structures defined in [ITU-E164]. Telephone numbers described in 246 this specification are character strings that MUST begin with a plus 247 sign ("+", ASCII value 0x002B), followed by a country code defined in 248 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 249 a sequence of digits representing the telephone number. 251 4.4. Checksum 253 Checksum of the CSV data escrow files MUST use CRC32, that is the 254 algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of 255 ITU-T recommendation V.42. 257 4.5. IP addresses 259 IP addresses syntax MUST conform to the text representation of either 260 of, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 261 Addressing Architecture [RFC4291], for IPv6 addresses. 263 4.6. CSV Parent Child Relationship 265 The CSV model represents a relational model, where the CSV files 266 represent relational tables, the fields of the CSV files represent 267 columns of the tables, and each line of the CSV file represents a 268 record. As in a relational model, the CSV files can have 269 relationships utilizing primary keys in the parent CSV file 270 definitions and foreign keys in the child CSV file definitions for a 271 1-to-many relationship. The primary keys are not explicitly defined, 272 but the foreign keys are using the boolean "parent" field attribute 273 in the child CSV file. The relationships between the CSV files are 274 used to support a cascade replace or cascade delete of records 275 starting from the parent record in differential and incremental 276 deposits. 278 The following is an example of the CSV file definitions for a Sample 279 object consisting of a parent "sample" CSV File Definition and a 280 child "sampleStatuses" CSV File Definition. The primary key for the 281 Sample object is the field that is used as the 282 foreign key in the "sampleStatuses" CSV File Definition by specifying 283 the "parent=true" attribute. If a Sample record is updated or 284 deleted in a differential or incremental deposit, it should cascade 285 replace the data using the records included in the child 286 "sampleStatuses" CSV File Definition or cascade delete the existing 287 records in the child "sampleStatuses" CSV File Definition, 288 respectively. 290 291 ... 292 293 294 295 296 297 298 299 300 301 302 303 304 305 307 sample-YYYYMMDD.csv 308 309 310 311 312 313 314 315 316 317 318 319 321 sampleStatuses-YYYYMMDD.csv 322 323 324 325 ... 326 328 4.7. CSV elements 330 4.7.1. element 332 To support a CSV model with the Registry Data Escrow Specification 333 [1], an element is defined for each object that substitutes for the 334 element and for the element, that contains 335 one or more elements. For example, the Domain Name 336 Object (Section 5.1) defines the element, that 337 substitutes for the element, and the 338 element, that substitutes for the 339 element. Both the element and the 340 elements contain one or more 341 elements. The element has the following child elements: 343 Ordered list of CSV fields used in the CSV files. 344 There is one or more child elements that substitute for the 345 abstract element. Each element defines the format 346 of the CSV field contained in the CSV files. The 347 elements support the "type" attribute that defines the XML simple 348 data type of the field element. The elements 349 support the "isRequired" attribute, with a default value of 350 "false", when set to "true" indicates that the field must be non- 351 empty in the CSV files and when set to "false" indicates that the 352 field MAY be empty in the CSV files. The "isRequired" attribute 353 MAY be specifically set for the field elements within the XML 354 schema and MAY be overridden when specifying the fields under the 355 element. The element supports an 356 OPTIONAL "parent" attribute that identifies the field as a 357 reference to a parent object, as defined in CSV Parent Child 358 Relationship (Section 4.6). For example, the field SHOULD set the 360 "parent" attribute to "true" to identify it as the parent domain 361 name of the domain status. 363 A list of one or more CSV files using the 364 child element. The child element 365 defines a reference to the CSV file name and has the following 366 optional attributes: 368 compression If the CSV file is compressed, the "compression" 369 attribute defines the compression format like "gzip" or "zip". 371 encoding Defines the encoding of the CSV file with the default 372 encoding of "UTF-8". 374 cksum Defines the checksum of the CSV file using CRC32, as 375 defined in Section 4.4. This attribute is used to validate 376 that the full CSV file exists and has not been tampered with. 378 The elements requires a "name" attribute that defines 379 the purpose of the CSV file with values like "domain", "host", 380 "contact". The supported "name" attribute values are defined for 381 each object type. The OPTIONAL "sep" attribute defines the CSV 382 separator character with the default separator character of ",". 384 The following is an example of the 385 element for domain name records where the is set 386 as required with isRequired="true". 388 389 ... 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 409 domain-YYYYMMDD.csv 410 411 412 413 ... 414 416 The following is example of the "domain-YYYYMMDD.csv" file with one 417 record matching the definition. 419 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 420 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 421 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 422 The following is an example of the 423 element for domain name records. 425 426 ... 427 428 429 430 431 432 434 domain-delete-YYYYMMDD.csv 435 436 437 438 ... 439 441 The following is example of the "domain-delete-YYYYMMDD.csv" file 442 with three records that matches the single field. 444 domain1.test 445 domain2.test 446 domainN.test 448 4.7.2. CSV common field elements 450 The element defined in the element 451 (Section 4.7.1) section has child elements that substitute for the 452 abstract element. By convention 453 elements include an 'f' prefix to identify them as field definition 454 elements. There are a set of common field elements that are used 455 across multiple data escrow objects. The common field elements are 456 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 457 using the "rdeCsv" sample namespace prefix. The CSV common field 458 elements include: 460 UTF-8 encoded name field with 461 type="eppcom:labelType". 463 Repository Object IDentifier (ROID) field with 464 type="eppcom:roidType" and isRequired="true". 466 Registrant contact identifier with 467 type="eppcom:clIDType". 469 The object status description, which is 470 free form text describing the rationale for the status, with 471 type="normalizedString". 473 Identifier of client (registrar) that sponsors the 474 object with type="eppcom:clIDType" and isRequired="true". 476 Identifier of the registrar, defined in Section 5.4, 477 of the client that created the object with type="eppcom:clIDType". 479 Identifier of client that created the object with 480 type="eppcom:clIDType". 482 Identifier of the registrar, defined in Section 5.4, 483 of the client that updated the object with type="eppcom:clIDType". 485 Identifier of client that updated the object with 486 type="eppcom:clIDType". 488 Identifier of the registrar, defined in Section 5.4, 489 of the client that requested the transfer with 490 type="eppcom:clIDType" and isRequired="true". 492 Identifier of client that requested the transfer with 493 type="eppcom:clIDType". 495 Identifier of the registrar, defined in Section 5.4, 496 of the client that should take or took action with 497 type="eppcom:clIDType" and isRequired="true". 499 Identifier of client that should take or took action 500 for transfer with type="eppcom:clIDType". 502 Created date of object with type="dateTime" and 503 isRequired="true". 505 Updated date of object with type="dateTime". 507 Expiration date of object with type="dateTime". 509 Date that transfer was requested with 510 type="dateTime" and isRequired="true". 512 Date that transfer action should be taken or has 513 been taken with type="dateTime" and isRequired="true". 515 Date of last transfer with type="dateTime". 517 State of the most recent transfer request with 518 type="eppcom:trStatusType" and isRequired="true". 520 General token field with type="token". 522 General language field with type="language". 524 IDN Table Identifier used for IDN domain names 525 with type="token". 527 General positive integer field with 528 type="positiveInteger". 530 Contains the URL of an object like a registrar object 531 with type="anyURI". 533 Custom field with name attribute that defines the 534 custom field name" with type="token". 536 4.8. Internationalized and Localized Elements 538 Some elements MAY be provided in either internationalized form 539 ("int") or provided in localized form ("loc"). Those elements use a 540 field value or "isLoc" attribute to specify the form used. If an 541 "isLoc" attribute is used, a value of "true" indicates the use of the 542 localized form and a value of "false" indicates the use of the 543 internationalized form. This MAY override the form specified for a 544 parent element. A value of "int" is used to indicate the 545 internationalized form and a value of "loc" is used to indicate the 546 localized form. When the internalized form ("int") is provided, the 547 field value MUST be represented in a subset of UTF-8 that can be 548 represented in the 7-bit US-ASCII character set. When the localized 549 form ("loc") is provided, the field value MAY be represented in 550 unrestricted UTF-8. 552 The field elements below of the "registrar" 553 element specify the internationalized form with the 554 isLoc="false" attribute. 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 587 588 590 registrar-YYYYMMDD.csv 591 592 593 594 ... 595 596 ... 598 The following is an example of using the 599 field value to define the internationalized or localized form of the 600 remainder of the "contactPostal" field values. 602 ... 603 604 ... 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 622 contactPostal-YYYYMMDD.csv 623 624 625 626 ... 627 628 ... 630 5. Object Description 632 This section describes the base objects supported by this 633 specification: 635 5.1. Domain Name Object 637 The domain name object is based on the EPP domain name mapping 638 specified in [RFC5731]. The domain name object supports both the XML 639 Model and the CSV Model, defined in the Models (Section 2) section. 640 The elements used for both models are defined in the following 641 sections. 643 5.1.1. XML Model 645 There are two elements used in the data escrow of the domain name 646 objects for the XML model including the , under the 647 element, and the element, under the 648 element. 650 5.1.1.1. object 652 The domain element is based on the EPP domain response for an 653 authorized client (see Section 3.1.2. of [RFC5731]) with additional 654 data from an EPP Query Response, see Section 3.1.3. of 655 [RFC5731], RGP status from [RFC3915], and data from the EPP 656 command, see Section 5.2.1. of [RFC5910]. 658 A element substitutes for the abstract 659 element to define a concrete definition of a domain. The 660 element can be replaced by other domain definitions 661 using the XML schema substitution groups feature. 663 The element contains the following child elements: 665 o A element that contains the fully qualified name of the 666 domain name object. If the domain name is an IDN, the ASCII 667 Compatible Encoding (ACE) MUST be used. 669 o A element that contains the repository object identifier 670 assigned to the domain name object when it was created. 672 o An OPTIONAL element that contains the fully qualified name 673 of the domain name in Unicode character set. It MUST be provided 674 if available. 676 o An OPTIONAL element that references the IDN 677 Table used for the IDN. This corresponds to the "id" attribute of 678 the element. This element MUST be present if the 679 domain name is an IDN. 681 o An OPTIONAL element is used to indicate that the 682 domain name is an IDN variant. This element contains the domain 683 name used to generate the IDN variant. 685 o One or more elements that contain the current status 686 descriptors associated with the domain name. 688 o Zero or more OPTIONAL element to represent 689 "pendingDelete" sub-statuses, including "redemptionPeriod", 690 "pendingRestore", and "pendingDelete", that a domain name can be 691 in as a result of grace period processing as specified in 692 [RFC3915]. 694 o An OPTIONAL element that contain the identifier for 695 the human or organizational social information object associated 696 as the holder of the domain name object. 698 o Zero or more OPTIONAL elements that contain identifiers 699 for the human or organizational social information objects 700 associated with the domain name object. 702 o An OPTIONAL element that contains the fully qualified names 703 of the delegated host objects or host attributes (name servers) 704 associated with the domain name object. See Section 1.1 of 705 [RFC5731] for a description of the elements used to specify host 706 objects or host attributes. 708 o A element that contains the identifier of the sponsoring 709 registrar. 711 o An OPTIONAL element that contains the identifier of the 712 registrar that created the domain name object. An OPTIONAL client 713 attribute is used to specify the client that performed the 714 operation. 716 o An OPTIONAL element that contains the date and time of 717 the domain name object creation. This element MUST be present if 718 the domain name has been allocated. 720 o An OPTIONAL element that contains the date and time 721 identifying the end (expiration) of the domain name object's 722 registration period. This element MUST be present if the domain 723 name has been allocated. 725 o An OPTIONAL element that contains the identifier of the 726 registrar that last updated the domain name object. This element 727 MUST NOT be present if the domain has never been modified. An 728 OPTIONAL client attribute is used to specify the client that 729 performed the operation. 731 o An OPTIONAL element that contains the date and time of 732 the most recent domain-name-object modification. This element 733 MUST NOT be present if the domain name object has never been 734 modified. 736 o An OPTIONAL element that contains the public key 737 information associated with Domain Name System security (DNSSEC) 738 extensions for the domain name as specified in [RFC5910]. 740 o An OPTIONAL element that contains the date and time of 741 the most recent domain object successful transfer. This element 742 MUST NOT be present if the domain name object has never been 743 transferred. 745 o An OPTIONAL element that contains the following child 746 elements related to the last transfer request of the domain name 747 object. This element MUST NOT be present if a transfer request 748 for the domain name has never been created. 750 * A element that contains the state of the most recent 751 transfer request. 753 * A element that contains the identifier of the registrar 754 that requested the domain name object transfer. An OPTIONAL 755 client attribute is used to specify the client that performed 756 the operation. 758 * A element that contains the date and time that the 759 transfer was requested. 761 * An element that contains the identifier of the registrar 762 that SHOULD act upon a PENDING transfer request. For all other 763 status types, the value identifies the registrar that took the 764 indicated action. An OPTIONAL client attribute is used to 765 specify the client that performed the operation. 767 * An element that contains the date and time of a 768 required or completed response. For a PENDING request, the 769 value identifies the date and time by which a response is 770 required before an automated response action will be taken by 771 the registry. For all other status types, the value identifies 772 the date and time when the request was completed. 774 * An OPTIONAL element that contains the end of the 775 domain name object's validity period (expiry date) if the 776 transfer caused or causes a change in the validity period. 778 Example of a domain object: 780 ... 781 782 example1.test 783 Dexample1-TEST 784 785 jd1234 786 sh8013 787 sh8013 788 789 ns1.example.com 790 ns1.example1.test 791 792 RegistrarX 793 RegistrarX 794 1999-04-03T22:00:00.0Z 795 2015-04-03T22:00:00.0Z 796 797 ... 799 5.1.1.2. object 801 The element contains the fully qualified domain 802 name that was deleted and purged. 804 Example of object: 806 ... 807 808 ... 809 810 foo.test 811 bar.test 812 813 ... 814 815 ... 817 5.1.2. CSV Model 819 For the CSV Model of the domain name object, the 820 child element of the element is used to hold the new 821 or updated domain name objects for the deposit. The 822 child element of the element is 823 used to hold the deleted or purged domain name objects for the 824 deposit. Both the and 825 elements contain one or more elements with a set of 826 named CSV file definitions using the "name" attribute. 828 Differential and incremental deposits are based on changes to the 829 domain name objects. The updated domain name object data under the 830 element is a cascade replace down all of the 831 domain name CSV files starting with the parent "domain" CSV File 832 Definition (Section 5.1.2.1.1). The child CSV file definitions 833 include a field. All the child CSV 834 file definition data for the domain name objects in the parent 835 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 836 deleted and then set using the data in the child CSV files. The 837 deleted domain name object data under the element 838 is a cascade delete starting from the "domain" Deletes CSV File 839 Definition (Section 5.1.2.2.1). 841 5.1.2.1. 843 The is used to hold the new or updated domain 844 name object information for the deposit. The is 845 split into separate CSV file definitions using named 846 elements with the "name" attribute. The following sections include 847 the supported domain name CSV file definitions: 849 5.1.2.1.1. "domain" CSV File Definition 851 The "domain" CSV File Definition defines the fields and CSV file 852 references used for the parent domain name object records. All the 853 other domain name CSV file definitions are child CSV files based on 854 the inclusion of the field. 856 The following "csvDomain" field elements MUST be used in the "domain" 857 element: 859 Domain name field with type="eppcom:labelType" and 860 isRequired="true". 862 The following "csvDomain" field elements MAY be used in the "domain" 863 element: 865 Fully qualified name of the original IDN 866 domain name object related to the variant domain name object with 867 type="eppcom:labelType". 869 The following "rdeCsv" fields, defined in section CSV common field 870 elements (Section 4.7.2), MUST be used in the "domain" 871 element: 873 Registry Object IDentifier (ROID) for the domain name 874 object with isRequired="true". 876 Identifier of client that sponsors the domain name 877 object with isRequired="true". 879 Created date and time of the domain name object 880 with isRequired="true". 882 Identifier of the registrar, defined in Section 5.4, 883 of the client that updated the object. 885 Date and time of the last update to the domain name 886 object. 888 Expiration date and time for the domain name 889 object. The attribute isRequired MUST equal "true". 891 The following "rdeCsv" fields, defined in section CSV common field 892 elements (Section 4.7.2), MAY be used in the "domain" 893 element: 895 Identifier of the registrar, defined in Section 5.4, 896 of the client that created the object. 898 UTF8 encoded domain name for the 899 field element. 901 IDN Table Identifier used for the IDN domain 902 name object that MUST match a field element 903 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 905 Registrant contact identifier for the domain 906 name object. 908 Identifier of client that created the domain name 909 object. 911 Identifier of the client that last updated the domain 912 name object. 914 Date and time of the last transfer for the domain 915 name object. 917 Example of a "domain" element. 919 ... 920 921 ... 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 941 domain-YYYYMMDD.csv 942 943 944 945 ... 946 947 ... 949 Example of the corresponding domain-YYYYMMDD.csv file. The file 950 contains four records (two active ASCII domains, original IDN with 951 LANG-1 language rules, and variant IDN with LANG-1 language rules). 953 domain1.test,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 954 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 955 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 956 domain2.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 957 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 958 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 959 xn--abc123.test,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 960 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 961 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 962 xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--abc123.test, 963 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 964 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 966 5.1.2.1.2. "domainContacts" CSV File Definition 968 The "domainContacts" CSV File Definition defines the fields and CSV 969 file references used for the domain name object link records to 970 contact objects, as described in Contact Object (Section 5.3). 972 The following "csvDomain" field elements MUST be used in the 973 "domainContacts" element: 975 The contact type for the contact object 976 link with type="domain:contactAttrType" and isRequired="true". 977 The supported contact type values include "admin" for the 978 administration contact, "billing" for the billing contact, and 979 "tech" for the technical contact. 981 The following "csvDomain" field elements, defined for the "domain" 982 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 983 "domainContacts" element: 985 The name of the domain object that is linked to 986 the contact object with isRequired="true". 988 The following "csvContact" fields, defined for the "contact" CSV File 989 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 990 element: 992 The server-unique contact identifier with 993 isRequired="true". 995 Example of a "domainContacts" 996 element. 998 ... 999 1000 ... 1001 1002 1003 1004 1005 1006 1007 1008 1010 domainContacts-YYYYMMDD.csv 1011 1012 1013 1014 ... 1015 1016 ... 1018 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1019 file contains an admin, tech, and billing contact for the four domain 1020 names domain1.test, domain2.test, xn--abc123.test and xn-- 1021 abc321.test. 1023 domain1.test,domain1admin,admin 1024 domain1.test,domain1tech,tech 1025 domain1.test,domain1billing,billing 1026 domain2.test,domain2admin,admin 1027 domain2.test,domain2tech,tech 1028 domain2.test,domain2billing,billing 1029 xn--abc123.test,xnabc123admin,admin 1030 xn--abc123.test,xnabc123tech,tech 1031 xn--abc123.test,xnabc123billing,billing 1032 xn--abc321.test,xnabc123admin,admin 1033 xn--abc321.test,xnabc123tech,tech 1034 xn--abc321.test,xnabc123billing,billing 1036 5.1.2.1.3. "domainStatuses" CSV File Definition 1038 The "domainStatuses" CSV File Definition defines the fields and CSV 1039 file references used for the domain name object statuses. 1041 The following "csvDomain" field elements MUST be used in the 1042 "domainStatuses" element: 1044 The status of the domain name with 1045 type="domain:statusValueType" and isRequired="true". 1047 The Registry Grace Period (RGP) status, as a 1048 sub-status of the "pendingDelete" status 1049 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1051 The following "csvDomain" fields, defined for the "domain" CSV File 1052 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1053 element: 1055 Domain name of status with isRequired="true". 1057 The following "rdeCsv" fields, defined in section CSV common field 1058 elements (Section 4.7.2), MAY be used in the "domainStatuses" 1059 element: 1061 Domain object status description which 1062 is free form text describing the rationale for the status. 1064 Language of the field. 1066 Example of a "domainStatuses" 1067 element. 1069 ... 1070 1071 ... 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1083 domainStatuses-YYYYMMDD.csv 1084 1085 1086 1087 ... 1088 1089 ... 1091 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1092 file contains the statuses for the four domain names domain1.test, 1093 domain2.test, xn--abc123.test and xn--abc321.test. 1095 domain1.test,clientUpdateProhibited,"Disallow update", 1096 en, 1097 domain1.test,clientDeleteProhibited,"Disallow delete", 1098 en, 1099 domain2.test,ok,,, 1100 xn--abc123.test,ok,,, 1101 xn--abc321.test,ok,,, 1103 5.1.2.1.4. "domainNameServers" CSV File Definition 1105 The "domainNameServers" CSV File Definition defines the fields and 1106 CSV file references used for the domain name delegated hosts (name 1107 servers). The "domainNameServers" CSV files define the relationship 1108 between a domain name object and a delegated host. The 1109 "domainNameServers" CSV File is used to support the 1110 model, defined in [RFC5731]. 1112 The following "csvDomain" fields, defined for the "domain" CSV File 1113 Definition (Section 5.1.2.1.1), MUST be used in the 1114 "domainNameServers" element: 1116 Domain name using the delegated host with host 1117 and isRequired="true". 1119 The following "rdeCsv" fields, defined in section CSV common field 1120 elements (Section 4.7.2), MUST be used in the "domainNameServers" 1121 element: 1123 Registry Object IDentifier (ROID) used to uniquely 1124 reference a delegated host record with isRequired="true". 1126 Example of a "domainNameServers" 1127 element. 1129 ... 1130 1131 ... 1132 1133 1134 1135 1136 1137 1138 1140 domainNameServers-YYYYMMDD.csv 1141 1142 1143 1144 ... 1145 1146 ... 1148 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1149 The file contains the delegated hosts (name servers) for the four 1150 domain names domain1.test, domain2.test, xn--abc123.test and xn-- 1151 abc321.test referenced via the field element. 1153 domain1.test,Hns1_domain1_test-TEST 1154 domain1.test,Hns2_domain1_test-TEST 1155 domain2.test,Hns1_domain2_test-TEST 1156 domain2.test,Hns2_domain2_test-TEST 1157 xn--abc123.test,Hns1_example_test-TEST 1158 xn--abc123.test,Hns2_example_test-TEST 1159 xn--abc321.test,Hns1_example_test-TEST 1160 xn--abc321.test,Hns2_example_test-TEST 1162 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1164 The "domainNameServersAddresses" CSV File Definition defines the 1165 fields and CSV file references used for supporting the host as domain 1166 attributes model. 1168 The following "csvDomain" fields, defined for the "domain" CSV File 1169 Definition (Section 5.1.2.1.1), MUST be used in the 1170 "domainNameServersAddresses" element: 1172 Domain name using the delegated host with host 1173 and isRequired="true". 1175 The following "rdeCsv" fields, defined in section Host CSV model 1176 elements (Section 5.2.2), MUST be used in the 1177 "domainNameServersAddresses" element: 1179 Host name field with type="eppcom:labelType" and 1180 isRequired="true". 1182 The following "csvHost" fields, defined in section Host CSV model 1183 elements (Section 5.2.2), MAY be used in the 1184 "domainNameServersAddresses" element: 1186 IP addresses associated with the host object with 1187 type="host:addrStringType". 1189 IP addresses version associated with the host 1190 object with type="host:ipType". "host:ipType" has the enumerated 1191 values of "v4" or "v6". 1193 Example of a "domainNameServersAddresses" 1194 element. 1196 ... 1197 1198 ... 1199 1200 1201 1202 1203 1204 1205 1206 1207 1209 domainNameServersAddresses-YYYYMMDD.csv 1210 1211 1212 1213 ... 1214 1215 ... 1217 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1218 file. The file contains the delegated hosts (name servers) for the 1219 four domain names domain1.test, domain2.test, xn--abc123.test and 1220 xn--abc321.test. 1222 domain1.test,ns1.domain1.test,192.0.2.1,v4 1223 domain1.test,ns2.domain1.test,2001:DB8::1,v6 1224 domain2.test,ns1.domain2.test2,192.0.2.2,v4 1225 domain2.test,ns2.domain2.test2,2001:DB8::2,v6 1226 xn--abc123.test,ns1.example.example,, 1227 xn--abc123.test,ns2.example.example,, 1228 xn--abc321.test,ns1.example.example,, 1229 xn--abc321.test,ns2.example.example,, 1231 5.1.2.1.6. "dnssec" CSV File Definition 1233 The "dnssec" CSV File Definition defines the fields and CSV file 1234 references used for the domain name object DNSSEC records (DS or Key 1235 Data). 1237 The following "csvDomain" field elements MUST be used in the "dnssec" 1238 element when the DS Data Interface per 1239 [RFC5910] is used: 1241 Contains the DS key tag value per [RFC5910] with 1242 type="unsignedShort" and isRequired="true". 1244 Contains the DS algorithm value per [RFC5910] 1245 with type="unsignedByte" and isRequired="true". 1247 Contains the DS digest type value per 1248 [RFC5910] with type="unsignedByte" and isRequired="true". 1250 Contains the DS digest value per [RFC5910] with 1251 type="hexBinary" and isRequired="true". 1253 The following "csvDomain" field elements MUST be used in the "dnssec" 1254 element when the Key Data Interface per 1255 [RFC5910] is used and MAY be used in the "dnssec" 1256 element when the DS Data Interface per [RFC5910] is 1257 used: 1259 Contains the flags field value per [RFC5910] with 1260 type="unsignedShort" and isRequired="true". 1262 Contains the Key protocol value per [RFC5910] 1263 with type="unsignedByte" and isRequired="true". 1265 Contains the Key algorithm value per [RFC5910] 1266 with type="unsignedByte" and isRequired="true". 1268 Contains the public key value per [RFC5910] with 1269 type="secDNS:keyType" and isRequired="true". 1271 The following "csvDomain" field elements MAY be used in the "dnssec" 1272 element: 1274 Indicates a child's preference for the 1275 number of seconds after signature generation when the parent's 1276 signature on the DS information provided by the child will expire 1277 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1279 The following "domain" fields, defined for the "domain" CSV File 1280 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1281 element: 1283 Domain name of the domain object associated with 1284 the DNSSEC record and isRequired="true". 1286 Example of a "dnssec" element with 1287 the DS Data Interface of [RFC5910]: 1289 1290 ... 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1303 dnssec-ds-YYYYMMDD.csv 1304 1305 1306 1307 ... 1308 1309 ... 1311 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1312 contains two DS records for domain1.test. 1314 domain1.test,604800,12345,3,1,49FD46E6C4B45C55D4AC 1315 domain1.test,604800,12346,3,1,38EC35D5B3A34B44C39B 1317 Example of a "dnssec" element with 1318 the Key Data Interface of [RFC5910]: 1320 1321 ... 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1334 dnssec-key-YYYYMMDD.csv 1335 1336 1337 1338 ... 1339 1340 ... 1342 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1343 contains two key records for domain1.test. 1345 domain1.test,604800,257,3,1,AQPJ////4Q== 1346 domain1.test,604800,257,3,1,AQPJ////4QQQ 1348 5.1.2.1.7. "domainTransfer" CSV File Definition 1350 The "domainTransfer" CSV File Definition defines the fields and CSV 1351 file references used for the domain name object pending and completed 1352 transfer records. No additional field elements were added for use in 1353 the "domainTransfer" element. 1355 The following "rdeCsv" fields, defined in section CSV common field 1356 elements (Section 4.7.2), MUST be used in the "domainTransfer" 1357 element: 1359 State of the most recent transfer request with 1360 isRequired="true". 1362 Identifier of the registrar, defined in Section 5.4, 1363 of the client that requested the transfer with isRequired="true". 1365 Date and time that the transfer was requested with 1366 isRequired="true". 1368 Identifier of the registrar, defined in Section 5.4, 1369 of the client that should take or took action with 1370 isRequired="true". 1372 Date and time that the transfer action should be 1373 taken or has been taken with isRequired="true". 1375 The following "rdeCsv" fields, defined in section CSV common field 1376 elements (Section 4.7.2), MAY be used in the "domainTransfer" 1377 element: 1379 Expiration date if the transfer command caused or 1380 causes a change in the validity period. 1382 Identifier of client that requested the transfer. 1384 Identifier of client that should take or took action 1385 for transfer. 1387 The following "csvDomain" fields, defined for the "domain" CSV File 1388 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1389 element: 1391 Domain name of the domain object involved in the 1392 transfer with isRequired="true". 1394 Example of a "domainTransfer" 1395 element. 1397 ... 1398 1399 ... 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1415 domainTransfer-YYYYMMDD.csv 1416 1417 1418 1419 ... 1420 1421 ... 1423 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1424 file contains one domain transfer record with a pending status. 1426 domain1.test,pending,registrarX,clientY, 1427 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1428 2016-04-03T22:00:00.0Z 1430 5.1.2.2. 1432 The is used to hold the deleted domain name 1433 objects in a differential or incremental deposit. All the domain 1434 name object data is deleted as part of a cascade delete. The 1435 is split into separate CSV file definitions using 1436 named elements with the "name" attribute. The following 1437 section defines the supported domain name deletes CSV file 1438 definition. 1440 5.1.2.2.1. "domain" Deletes CSV File Definition 1442 The following "csvDomain" field elements MUST be used in the deletes 1443 "domain" element: 1445 Domain name field with type="eppcom:labelType" and 1446 isRequired="true". 1448 Example of a "domain" element: 1450 ... 1451 1452 ... 1453 1454 1455 1456 1457 1458 1460 domain-delete-YYYYMMDD.csv 1461 1462 1463 1464 ... 1465 1466 ... 1468 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1469 file contains two domain name records. 1471 domain1.test 1472 domain2.test 1474 5.2. Host Object 1476 The host object is based on the EPP host name mapping in [RFC5732]. 1477 The host object supports both the XML Model and the CSV Model, 1478 defined in Models (Section 2) section. The elements used for both 1479 models are defined in the following sections. Both the 1480 and elements contain one or more 1481 elements with a set of named CSV file definitions using 1482 the "name" attribute. 1484 5.2.1. XML Model 1486 There are two elements used in the data escrow of the host objects 1487 for the XML model including the , under the 1488 element, and the element, under 1489 the element. 1491 A element substitutes for the 1492 abstract element to define a concrete definition of a host. The 1493 element can be replaced by other host 1494 definitions using the XML schema substitution groups feature. 1496 5.2.1.1. element 1498 The RDE host object is based on the EPP host response for an 1499 authorized client (Section 3.1.2. of [RFC5732]). 1501 The OPTIONAL element contains the following child elements: 1503 o A element that contains the fully qualified name of the 1504 host object. 1506 o A element that contains the repository object identifier 1507 assigned to the host object when the object was created. 1509 o One or more elements that describe the status of the host 1510 object. 1512 o Zero or more elements that contain the IP addresses 1513 associated with the host object. 1515 o A element that contains the identifier of the sponsoring 1516 registrar. 1518 o A element that contains the identifier of the registrar 1519 that created the host object. An OPTIONAL client attribute is 1520 used to specify the client that performed the operation. 1522 o A element that contains the date and time of host-object 1523 creation. 1525 o An OPTIONAL element that contains the identifier of the 1526 registrar that last updated the host object. This element MUST 1527 NOT be present if the host object has never been modified. An 1528 OPTIONAL client attribute is used to specify the client that 1529 performed the operation. 1531 o An OPTIONAL element that contains the date and time of 1532 the most recent host-object modification. This element MUST NOT 1533 be present if the host object has never been modified. 1535 o An OPTIONAL element that contains the date and time of 1536 the most recent host object successful transfer. This element 1537 MUST NOT be present if the domain name object has never been 1538 transfered. 1540 Example of object: 1542 ... 1543 1544 ns1.example1.test 1545 Hns1_example_test-TEST 1546 1547 1548 192.0.2.2 1549 192.0.2.29 1550 1080:0:0:0:8:800:200C:417A 1551 RegistrarX 1552 RegistrarX 1553 1999-05-08T12:10:00.0Z 1554 RegistrarX 1555 2009-10-03T09:34:00.0Z 1556 1557 ... 1559 5.2.1.2. object 1561 The element contains the fully qualified domain name 1562 of a host that was deleted. The element also 1563 supports host removal based on roid to support SRS systems in which 1564 different hosts with the same fully qualified domain name are active 1565 at the same time. 1567 Example of object: 1569 ... 1570 1571 ... 1572 1573 ns1.example.test 1574 1575 ... 1576 1577 ... 1579 5.2.2. CSV Model 1581 For the CSV Model of the host object, the child 1582 element of the element is used to hold the new or 1583 updated host objects for the deposit. The child 1584 element of the element is used to hold the deleted or 1585 purged host objects for the deposit. 1587 Differential and incremental deposits are based on changes to the 1588 host objects. The updated host object data under the 1589 element is a cascade replace down all of the host 1590 CSV files starting with the parent "host" CSV File Definition 1591 (Section 5.2.2.1.1). The child CSV file definitions include a 1592 field. All the child CSV file 1593 definition data for the host objects in the parent "host" CSV File 1594 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1595 using the data in the child CSV files. The deleted host object data 1596 under the element is a cascade delete starting from 1597 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1599 5.2.2.1. 1601 The is used to hold the new or updated host object 1602 information for the deposit. The is split into 1603 separate CSV file definitions using named elements with 1604 the "name" attribute. The following sections include the supported 1605 host CSV file definitions. 1607 5.2.2.1.1. "host" CSV File Definition 1609 The "host" CSV File Definition defines the fields and CSV file 1610 references used for the host object records. 1612 The following "csvHost" field elements MUST be used in the "host" 1613 element: 1615 Host name field with type="eppcom:labelType" and 1616 isRequired="true". 1618 The following "rdeCsv" fields, defined in section CSV common field 1619 elements (Section 4.7.2), MUST be used in the "host" 1620 element: 1622 Repository Object IDentifier (ROID) assigned to the 1623 host object with isRequired="true". 1625 The following "rdeCsv" fields, defined in section CSV common field 1626 elements (Section 4.7.2), MAY be used in the "host" 1627 element: 1629 Identifier of the sponsoring client with 1630 isRequired="true". 1632 Identifier of the registrar, defined in Section 5.4, 1633 of the client that created the object with isRequired="true". 1635 Identifier of client that created the host object. 1637 Date and time that the host object was created with 1638 isRequired="true". 1640 Identifier of the registrar, defined in Section 5.4, 1641 of the client that updated the object. 1643 Identifier of client that last updated the host 1644 object. 1646 Date and time that the host object was last 1647 updated. 1649 Date and time that the host was last transferred. 1651 Example of a "host" element. 1653 ... 1654 1655 ... 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1672 host-YYYYMMDD.csv 1673 1674 1675 1676 ... 1677 1678 ... 1680 Example of the corresponding host-YYYYMMDD.csv file. The file 1681 contains six host records with four being internal hosts and two 1682 being external hosts. 1684 ns1.domain1.test,Hns1_example_test-TEST,registrarX,registrarX, 1685 clientY,1999-05-08T12:10:00.0Z,registrarX, 1686 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1687 ns2.domain1.test,Hns2_domain1_test-TEST,registrarX,registrarX, 1688 clientY,1999-05-08T12:10:00.0Z,registrarX, 1689 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1690 ns1.domain2.test,Hns1_domain2_test-TEST,registrarX,registrarX, 1691 clientY,1999-05-08T12:10:00.0Z,registrarX, 1692 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1693 ns2.domain2.test,Hns2_domain2_test-TEST,registrarX,registrarX, 1694 clientY,1999-05-08T12:10:00.0Z,registrarX, 1695 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1696 ns1.example.example,Hns1_example_test-TEST,registrarX,registrarX, 1697 clientY,1999-05-08T12:10:00.0Z,registrarX, 1698 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1699 ns2.example.example,Hns2_example_test-TEST,registrarX,registrarX, 1700 clientY,1999-05-08T12:10:00.0Z,registrarX, 1701 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1703 5.2.2.1.2. "hostStatuses" CSV File Definition 1705 The "hostStatuses" CSV File Definition defines the fields and CSV 1706 file references used for the host object statuses. 1708 The following "csvHost" fields, defined for the "host" CSV File 1709 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1710 element: 1712 The status of the host with 1713 type="host:statusValueType" and isRequired="true"./>. 1715 The following "rdeCsv" fields, defined in section CSV common field 1716 elements (Section 4.7.2), MUST be used in the "hostStatuses" 1717 element: 1719 Host object Registry Object IDentifier (ROID) 1720 assigned to the host object with isRequired="true". 1722 The following "rdeCsv" fields, defined in section CSV common field 1723 elements (Section 4.7.2), MAY be used in the "hostStatuses" 1724 element: 1726 Host object status description which is 1727 free form text describing the rationale for the status. The 1728 attribute isRequired MUST equal "true". 1730 Language of the field. 1732 Example of a "hostStatuses" element. 1734 ... 1735 1736 ... 1737 1738 1739 1740 1741 1742 1743 1744 1745 1747 hostStatuses-YYYYMMDD.csv 1748 1749 1750 1751 ... 1752 1753 ... 1755 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1756 file contains the statuses for the six host names ns1.domain1.test, 1757 ns2.domain1.test, ns1.domain2.test, ns2.domain2.test, 1758 ns1.example.example and ns2.example.example. 1760 Hns1_domain1_test-TEST,ok,, 1761 Hns2_domain1_test-TEST,ok,, 1762 Hns1_domain2_test-TEST,ok,, 1763 Hns2_domain2_test-TEST,ok,, 1764 Hns1_example_test-TEST,ok,, 1765 Hns2_example_test-TEST,ok,, 1767 5.2.2.1.3. "hostAddresses" CSV File Definition 1769 The "hostAddresses" CSV File Definition defines the fields and CSV 1770 file references used for the host object IP addresses. 1772 The following "csvHost" field elements MUST be used in the 1773 "hostAddresses" element: 1775 IP addresses associated with the host object with 1776 type="host:addrStringType". The attribute isRequired MUST equal 1777 "true". 1779 IP addresses version associated with the host 1780 object with type="host:ipType". "host:ipType" has the enumerated 1781 values of "v4" or "v6". The attribute isRequired MUST equal 1782 "true". 1784 The following "rdeCsv" fields, defined in section CSV common field 1785 elements (Section 4.7.2), MUST be used in the "hostAddresses" 1786 element: 1788 Host object Registry Object IDentifier (ROID) 1789 assigned to the host object. 1791 Example of a "hostAddresses" element. 1793 ... 1794 1795 ... 1796 1797 1798 1799 1800 1801 1802 1803 1805 hostAddresses-YYYYMMDD.csv 1806 1807 1808 1809 ... 1810 1811 ... 1813 Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The 1814 file contains the IP addresses for the host names ns1.domain1.test, 1815 ns2.domain1.test, ns1.domain2.test and ns2.domain2.test. 1817 Hns1_domain1_test-TEST,192.0.2.1,v4 1818 Hns2_domain1_test-TEST,2001:DB8::1,v6 1819 Hns1_domain2_test-TEST,192.0.2.2,v4 1820 Hns2_domain2_test-TEST,2001:DB8::2,v6 1822 5.2.2.2. 1824 The is used to hold the deleted host objects in a 1825 differential or incremental deposit. All the host object data is 1826 deleted as part of a cascade delete. The is split 1827 into separate CSV file definitions using named elements 1828 with the "name" attribute. The following section defines the 1829 supported host deletes CSV file definition. 1831 5.2.2.2.1. "host" Deletes CSV File Definition 1833 The following "rdeCsv" fields, defined in section CSV common field 1834 elements (Section 4.7.2), MUST be used in the "host" 1835 element: 1837 Repository Object IDentifier (ROID) assigned to the 1838 host object with isRequired="true". 1840 Example of a "host" element. 1842 ... 1843 1844 ... 1845 1846 1847 1848 1849 1850 1852 host-delete-YYYYMMDD.csv 1853 1854 1855 1856 ... 1857 1858 ... 1860 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1861 host records. 1863 Hns1_domain1_test-TEST 1864 Hns2_domain1_test-TEST 1865 Hns1_domain2_test-TEST 1866 Hns2_domain2_test-TEST 1868 5.3. Contact Object 1870 The contact object is based on the EPP contact name mapping in 1871 [RFC5733]. The contact object supports both the XML Model and the 1872 CSV Model, defined in Models (Section 2) section. The elements used 1873 for both models are defined in the following sections. 1875 5.3.1. XML Model 1877 There are two elements used in the data escrow of the contact objects 1878 for the XML model including the , under the 1879 element, and the element, 1880 under the element. 1882 A element substitutes for the abstract 1883 element to define a concrete definition of a contact. The 1884 element can be replaced by other contact 1885 definitions using the XML schema substitution groups feature. 1887 5.3.1.1. object 1889 The contact object is based on the EPP contact response for an 1890 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1891 including the data from an EPP Query Response, see 1892 Section 3.1.3. of [RFC5733]. 1894 The OPTIONAL element contains the following child elements: 1896 o A element that contains the server-unique identifier of the 1897 contact object 1899 o A element that contains the Repository Object IDentifier 1900 assigned to the contact object when the object was created. 1902 o One or more elements that describe the status of the 1903 contact object. 1905 o One or two elements that contain postal-address 1906 information. Two elements are provided so that address 1907 information can be provided in both internationalized and 1908 localized forms; a "type" attribute is used to identify the two 1909 forms. If an internationalized form (type="int") is provided, 1910 element content MUST be represented in a subset of UTF-8 that can 1911 be represented in the 7-bit US-ASCII character set. If a 1912 localized form (type="loc") is provided, element content MAY be 1913 represented in unrestricted UTF-8. The element 1914 contains the following child elements: 1916 * A element that contains the name of the individual or 1917 role represented by the contact. 1919 * An OPTIONAL element that contains the name of the 1920 organization with which the contact is affiliated. 1922 * An element that contains address information associated 1923 with the contact. An element contains the following 1924 child elements: 1926 + One, two, or three OPTIONAL elements that contain 1927 the contact's street address. 1929 + A element that contains the contact's city. 1931 + An OPTIONAL element that contains the contact's state 1932 or province. 1934 + An OPTIONAL element that contains the contact's postal 1935 code. 1937 + A element that contains the contact's two-letter 1938 country code. 1940 o An OPTIONAL element that contains the contact's voice 1941 telephone number. 1943 o An OPTIONAL element that contains the contact's facsimile 1944 telephone number. 1946 o An element that contains the contact's email address. 1948 o A element that contains the identifier of the sponsoring 1949 registrar. 1951 o A element that contains the identifier of the registrar 1952 that created the contact object. An OPTIONAL client attribute is 1953 used to specify the client that performed the operation. 1955 o A element that contains the date and time of contact- 1956 object creation. 1958 o An OPTIONAL element that contains the identifier of the 1959 registrar that last updated the contact object. This element MUST 1960 NOT be present if the contact has never been modified. An 1961 OPTIONAL client attribute is used to specify the client that 1962 performed the operation. 1964 o An OPTIONAL element that contains the date and time of 1965 the most recent contact-object modification. This element MUST 1966 NOT be present if the contact object has never been modified. 1968 o An OPTIONAL element that contains the date and time of 1969 the most recent contact object successful transfer. This element 1970 MUST NOT be present if the contact object has never been 1971 transferred. 1973 o An OPTIONAL element that contains the following child 1974 elements related to the last transfer request of the contact 1975 object: 1977 * A element that contains the state of the most recent 1978 transfer request. 1980 * A element that contains the identifier of the registrar 1981 that requested the domain name object transfer. An OPTIONAL 1982 client attribute is used to specify the client that performed 1983 the operation. 1985 * An element that contains the identifier of the registrar 1986 that SHOULD act upon a PENDING transfer request. For all other 1987 status types, the value identifies the registrar that took the 1988 indicated action. An OPTIONAL client attribute is used to 1989 specify the client that performed the operation. 1991 * A element that contains the date and time that the 1992 transfer was requested. 1994 * An element that contains the date and time of a 1995 required or completed response. For a PENDING request, the 1996 value identifies the date and time by which a response is 1997 required before an automated response action will be taken by 1998 the registry. For all other status types, the value identifies 1999 the date and time when the request was completed. 2001 o An OPTIONAL element that identifies elements that 2002 requiring exceptional server-operator handling to allow or 2003 restrict disclosure to third parties. See Section 2.9 of 2004 [RFC5733] for a description of the child elements contained within 2005 the element. 2007 Example object: 2009 ... 2010 2011 Csh8013-TEST 2012 sh8013 2013 2014 2015 2016 John Doe 2017 Example Inc. 2018 2019 123 Example Dr. 2020 Suite 100 2021 Dulles 2022 VA 2023 20166-6503 2024 US 2025 2026 2027 +1.7035555555 2028 +1.7035555556 2029 jdoe@example.test 2030 RegistrarX 2031 RegistrarX 2032 2009-09-13T08:01:00.0Z 2033 RegistrarX 2034 2009-11-26T09:10:00.0Z 2035 2009-12-03T09:05:00.0Z 2036 2037 pending 2038 clientW 2039 2011-03-08T19:38:00.0Z 2040 RegistrarX 2041 2011-03-13T23:59:59.0Z 2042 2043 2044 2045 2046 2047 2048 ... 2050 5.3.1.2. object 2052 The element contains the id of a contact that was 2053 deleted. 2055 Example of object: 2057 ... 2058 2059 ... 2060 2061 sh8013-TEST 2062 co8013-TEST 2063 2064 ... 2065 2066 ... 2068 5.3.2. CSV Model 2070 For the CSV Model of the contact object, the 2071 child element of the element is used to hold the new 2072 or updated contacts objects for the deposit. The 2073 child element of the element is 2074 used to hold the deleted or purged contact objects for the deposit. 2075 Both the and elements 2076 contain one or more elements with a set of named CSV 2077 file definitions using the "name" attribute. 2079 Differential and incremental deposits are based on changes to the 2080 contact objects. The updated contact object data under the 2081 element is a cascade replace down all of the 2082 contact CSV files starting with the parent "contact" CSV File 2083 Definition (Section 5.3.2.1.1). The child CSV file definitions 2084 include a field. All the child CSV 2085 file definition data for the contact objects in the parent "contact" 2086 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2087 then set using the data in the child CSV files. The deleted contact 2088 object data under the element is a cascade 2089 delete starting from the "contact" Deletes CSV File Definition 2090 (Section 5.3.2.2.1). 2092 5.3.2.1. 2094 The is used to hold the new or updated contact 2095 object information for the deposit. The is 2096 split into separate CSV file definitions using named 2097 elements with the "name" attribute. The following sections include 2098 the supported contact CSV file definitions. 2100 5.3.2.1.1. "contact" CSV File Definition 2102 The "contact" CSV File Definition defines the fields and CSV file 2103 references used for the contact object records. 2105 The following "csvContact" field elements MUST be used in the 2106 "contact" element: 2108 Contains the server-unique contact identifier with 2109 type="eppcom:clIDType" and isRequired="true". 2111 Contains the contact's email address with 2112 type="eppcom:minTokenType" and isRequired="true". 2114 The following field elements MAY be used in the "contact" 2115 element: 2117 Contains the contact's voice telephone number 2118 with type="contact:e164StringType". 2120 Contains the contact's voice telephone number 2121 extension with type="token". 2123 Contains the contact's facsimile telephone number 2124 with type="contact:e164StringType". 2126 Contains the contact's facsimile telephone 2127 number extension with type="token". 2129 The following "rdeCsv" fields, defined in section CSV common field 2130 elements (Section 4.7.2), MUST be used in the "contact" 2131 element: 2133 The Registry Object IDentifier (ROID) for the contact 2134 object with isRequired="true". 2136 Identifier of client (registrar) that sponsors the 2137 contact object with isRequired="true". 2139 Identifier of the registrar, defined in Section 5.4, 2140 of the client that created the object with isRequired="true". 2142 Created date and time of the contact object with 2143 isRequired="true". 2145 Identifier of the registrar, defined in Section 5.4, 2146 of the client that updated the object. 2148 Date and time of the last update to the contact 2149 object. 2151 The following "rdeCsv" fields, defined in section CSV common field 2152 elements (Section 4.7.2), MAY be used in the "contact" 2153 element: 2155 Identifier of client that created the contact object. 2157 Identifier of the client that last updated the 2158 contact object. 2160 Date and time of the last transfer for the contact 2161 object. 2163 Example of a "contact" element. 2165 ... 2166 2167 ... 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2188 contact-YYYYMMDD.csv 2189 2190 2191 2192 ... 2193 2194 ... 2196 Example of the contact-YYYYMMDD.csv file. The file contains nine 2197 object contact records. 2199 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2200 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2201 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2202 2009-11-26T09:10:00.0Z 2203 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2204 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2205 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2206 2009-11-26T09:10:00.0Z 2207 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2208 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2209 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2210 2009-11-26T09:10:00.0Z 2211 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2212 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2213 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2214 2009-11-26T09:10:00.0Z 2215 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2216 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2217 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2218 2009-11-26T09:10:00.0Z 2219 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2220 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2221 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2222 2009-11-26T09:10:00.0Z 2223 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2224 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2225 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2226 2009-11-26T09:10:00.0Z 2227 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2228 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2229 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2230 2009-11-26T09:10:00.0Z 2231 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2232 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2233 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2234 2009-11-26T09:10:00.0Z 2236 5.3.2.1.2. "contactStatuses" CSV File Definition 2238 The "contactStatuses" CSV File Definition defines the fields and CSV 2239 file references used for the contact object statuses. 2241 The following "csvContact" field elements, defined for the "contact" 2242 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2243 "contactStatuses" element: 2245 Server-unique contact identifier of status with 2246 isRequired="true". 2248 The status of the contact with 2249 type="contact:statusValueType" and isRequired="true". 2251 The following "rdeCsv" fields, defined in section CSV common field 2252 elements (Section 4.7.2), MAY be used in the "contactStatuses" 2253 element: 2255 The contact object status description 2256 which is free form text describing the rationale for the status. 2258 Language of the field. 2260 Example of a "contactStatuses" 2261 element. 2263 ... 2264 2265 ... 2266 2267 2268 2269 2270 2271 2272 2273 2274 2276 contactStatuses-YYYYMMDD.csv 2277 2278 2279 2280 ... 2281 2282 ... 2284 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2285 file contains the statuses for the nine contact identifiers. 2287 domain1admin,ok,, 2288 domain1tech,ok,, 2289 domain1billing,ok,, 2290 domain2admin,ok,, 2291 domain2tech,ok,, 2292 domain2billing,ok,, 2293 xnabc123admin,ok,, 2294 xnabc123tech,ok,, 2295 xnabc123billing,ok,, 2297 5.3.2.1.3. "contactPostal" CSV File Definition 2299 The "contactPostal" CSV File Definition defines the fields and CSV 2300 file references used for the contact postal info object records. 2302 The following "csvContact" field elements MUST be used in the 2303 "contactPostal" element: 2305 Contains the form of the postal-address 2306 information with type="contact:postalLineType" and 2307 isRequired="true". This field specifies the form ("int" or 2308 "loc"), as defined in Section 4.8, of the , 2309 , , , 2310 , , fields. 2312 Contains the contact's name of the individual or 2313 role represented by the contact with type="contact:postalLineType" 2314 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2315 indicate the localized or internationalized form as defined in 2316 section Section 4.8. 2318 Contains the contact's contact's street address 2319 line with type="contact:fPostalLineType". An index attribute is 2320 required to indicate which street address line the field 2321 represents with index "0" for the first line and index "2" for the 2322 last line. An OPTIONAL "isLoc" attribute to used to indicate the 2323 localized or internationalized form as defined in section 2324 Section 4.8. 2326 Contains the contact's city with 2327 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2328 "isLoc" attribute to used to indicate the localized or 2329 internationalized form as defined in section Section 4.8. 2331 Contains the contact's country code with 2332 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2333 attribute to used to indicate the localized or internationalized 2334 form as defined in section Section 4.8. 2336 The following "csvContact" field elements MAY be used in the 2337 "contactPostal" element: 2339 Contains the name of the organization with which 2340 the contact is affiliated with type="contact:optPostalLineType". 2341 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2342 internationalized form as defined in section Section 4.8. 2344 Contains the contact's state or province with 2345 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2346 to used to indicate the localized or internationalized form as 2347 defined in section Section 4.8. 2349 Contains the contact's postal code with 2350 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2351 indicate the localized or internationalized form as defined in 2352 section Section 4.8. 2354 The following "csvContact" fields, defined for the "contact" CSV File 2355 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2356 element: 2358 Server-unique contact identifier for the contact 2359 object with isRequired="true". 2361 Example of a "contactPostal" 2362 element. 2364 ... 2365 2366 ... 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2384 contactPostal-YYYYMMDD.csv 2385 2386 2387 2388 ... 2389 2390 ... 2392 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2393 nine contact postal records. 2395 domain1admin,int,"John Doe","Example Inc.", 2396 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2397 domain1tech,int,"John Doe","Example Inc.", 2398 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2399 domain1billing,int,"John Doe","Example Inc.", 2400 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2401 domain2admin,int,"John Doe","Example Inc.", 2402 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2403 domain2tech,int,"John Doe","Example Inc.", 2404 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2405 domain2billing,int,"John Doe","Example Inc.", 2406 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2407 xnabc123admin,int,"John Doe","Example Inc.", 2408 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2409 xnabc123tech,int,"John Doe","Example Inc.", 2410 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2411 xnabc123billing,int,"John Doe","Example Inc.", 2412 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2414 5.3.2.1.4. "contactTransfer" CSV File Definition 2416 The "contactTransfer" CSV File Definition defines the fields and CSV 2417 file references used for the contact object pending and completed 2418 transfer records. No additional field elements were added for use in 2419 the "contactTransfer" element. The 2420 following "rdeCsv" fields, defined in section CSV common field 2421 elements (Section 4.7.2), MUST be used in the "contactTransfer" 2422 element: 2424 State of the most recent transfer request with 2425 isRequired="true". 2427 Identifier of the registrar, defined in Section 5.4, 2428 of the client that requested the transfer with isRequired="true". 2430 Date and time that the transfer was requested with 2431 isRequired="true". 2433 Identifier of the registrar, defined in Section 5.4, 2434 of the client that should take or took action with 2435 isRequired="true". 2437 Date and time that the transfer action should be 2438 taken or has been taken with isRequired="true". 2440 The following "rdeCsv" fields, defined in section CSV common field 2441 elements (Section 4.7.2), MAY be used in the "contactTransfer" 2442 element: 2444 Identifier of client that requested the transfer. 2446 Identifier of client that should take or took action 2447 for transfer. 2449 The following "csvContact" fields, defined for the "contact" CSV File 2450 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2451 element: 2453 Server-unique contact identifier for the contact 2454 object with isRequired="true". 2456 Example of a "contactTransfer" 2457 element. 2459 ... 2460 2461 ... 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2476 contactTransfer-YYYYMMDD.csv 2477 2478 2479 2480 ... 2481 2482 ... 2484 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2485 one contact transfer record in pending status. 2487 xnabc123admin,clientApproved,registrarX,clientX, 2488 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2490 5.3.2.1.5. "contactDisclose" CSV File Definition 2492 The "contactDisclose" CSV File Definition defines the fields and CSV 2493 file references used for the contact disclose object records. 2495 The following "csvContact" field elements MAY be used in the 2496 "contactDisclose" element: 2498 Contains flag with a value of "true" or 2499 "1" (one) notes the preference to allow disclosure of the 2500 specified elements as an exception to the stated data-collection 2501 policy. A value of "false" or "0" (zero) notes a client 2502 preference to not allow disclosure of the specified elements as an 2503 exception to the stated data-collection policy with 2504 type="boolean". The additional fields define specific exceptional 2505 disclosure preferences based on the 2506 field. 2508 Exceptional disclosure preference flag 2509 for the localized form of the contact name with type="boolean". 2511 Exceptional disclosure preference flag 2512 for the internationalized form of the contact name with 2513 type="boolean". 2515 Exceptional disclosure preference flag 2516 for the localized form of the contact organization with 2517 type="boolean". 2519 Exceptional disclosure preference flag 2520 for the internationalized form of the contact organization with 2521 type="boolean". 2523 Exceptional disclosure preference flag 2524 for the localized form of the contact address with type="boolean". 2526 Exceptional disclosure preference flag 2527 for the internationalized form of the contact address with 2528 type="boolean". 2530 Exceptional disclosure preference flag 2531 of the contact voice telephone number with type="boolean". 2533 Exceptional disclosure preference flag of 2534 the contact facsimile telephone number with type="boolean". 2536 Exceptional disclosure preference flag 2537 of the contact email address with type="boolean". 2539 The following "csvContact" fields, defined for the "contact" CSV File 2540 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2541 element: 2543 Server-unique contact identifier for the contact 2544 object with isRequired="true". 2546 Example of a "contactDisclose" 2547 element. 2549 ... 2550 2551 ... 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2569 contactDisclose-YYYYMMDD.csv 2570 2571 2572 2573 ... 2574 2575 ... 2577 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2578 one disclosure records, disabling disclosure of voice, fax, and 2579 email. 2581 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2583 5.3.2.2. 2585 The is used to hold the deleted contact objects 2586 in a differential or incremental deposit. All the contact object 2587 data is deleted as part of a cascade delete. The 2588 is split into separate CSV file definitions 2589 using named elements with the "name" attribute. The 2590 following section defines the supported contact deletes CSV file 2591 definition. 2593 5.3.2.2.1. "contact" Deletes CSV File Definition 2595 The following "csvContact" field elements MUST be used in the deletes 2596 "contact" element: 2598 Contains the server-unique contact identifier with 2599 type="eppcom:clIDType" and isRequired="true". 2601 Example of a "contact" element. 2603 ... 2604 2605 ... 2606 2607 2608 2609 2610 2611 2613 contact-delete-YYYYMMDD.csv 2614 2615 2616 2617 ... 2618 2619 ... 2621 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2622 six contact records. 2624 domain1admin 2625 domain1tech 2626 domain1billing 2627 domain2admin 2628 domain2tech 2629 domain2billing 2631 5.4. Registrar Object 2633 The registrar object represents the sponsoring client for other 2634 objects, for operational purposes MAY be the registry operator. The 2635 registrar object supports both the XML Model and the CSV Model, 2636 defined in Section 2. The elements used for both models are defined 2637 in the following sections. 2639 5.4.1. XML Model 2641 There are two elements used in the data escrow of the registrar 2642 objects for the XML model including the , 2643 under the element, and the 2644 element, under the element. 2646 A element substitutes for the 2647 abstract element to define a 2648 concrete definition of a registrar. The 2649 element can be replaced by other 2650 domain definitions using the XML schema substitution groups feature. 2652 5.4.1.1. element 2654 The element contains the following child elements: 2656 o An element that contains the Registry-unique identifier of 2657 the registrar object. This has a superordinate relationship 2658 to a subordinate , or of domain, contact and 2659 host objects. 2661 o An element that contains the name of the registrar. 2663 o An OPTIONAL element that contains the ID assigned by 2664 ICANN. 2666 o An OPTIONAL element that contains the operational status 2667 of the registrar. Possible values are: ok, readonly and 2668 terminated. 2670 o Zero or two OPTIONAL elements that contain postal- 2671 address information. Two elements are provided so that address 2672 information can be provided in both internationalized and 2673 localized forms; a "type" attribute is used to identify the two 2674 forms. If an internationalized form (type="int") is provided, 2675 element content MUST be represented in a subset of UTF-8 that can 2676 be represented in the 7-bit US-ASCII character set. If a 2677 localized form (type="loc") is provided, element content MAY be 2678 represented in unrestricted UTF-8. The element 2679 contains the following child elements: 2681 * A element that contains address information associated 2682 with the registrar. The element contains the following 2683 child elements: 2685 + One, two, or three OPTIONAL elements that contain 2686 the registrar's street address. 2688 + A element that contains the registrar's city. 2690 + An OPTIONAL element that contains the registrar's state 2691 or province. 2693 + An OPTIONAL element that contains the registrar's 2694 postal code. 2696 + A element that contains the registrar's country code. 2698 o An OPTIONAL element that contains the registrar's voice 2699 telephone number. 2701 o An OPTIONAL element that contains the registrar's facsimile 2702 telephone number. 2704 o An OPTIONAL element that contains the registrar's email 2705 address. 2707 o An OPTIONAL element that contains the registrar's URL. 2709 o An OPTIONAL elements that contains whois information. 2710 The element contains the following child elements: 2712 * An OPTIONAL element that contains the name of the 2713 registrar WHOIS server listening on TCP port 43 as specified in 2714 [RFC3912]. 2716 * An OPTIONAL element that contains the name of the 2717 registrar WHOIS server listening on TCP port 80/443. 2719 o An OPTIONAL element that contains the date and time of 2720 registrar-object creation. 2722 o An OPTIONAL element that contains the date and time of 2723 the most recent RDE registrar-object modification. This element 2724 MUST NOT be present if the rdeRegistrar object has never been 2725 modified. 2727 Example of object: 2729 ... 2730 2731 RegistrarX 2732 Registrar X 2733 123 2734 ok 2735 2736 2737 123 Example Dr. 2738 Suite 100 2739 Dulles 2740 VA 2741 20166-6503 2742 US 2743 2744 2745 +1.7035555555 2746 +1.7035555556 2747 jdoe@example.test 2748 http://www.example.test 2749 2750 whois.example.test 2751 http://whois.example.test 2752 2753 2005-04-23T11:49:00.0Z 2754 2009-02-17T17:51:00.0Z 2755 2756 ... 2758 5.4.1.2. object 2760 The element contains the id of a registrar that 2761 was deleted. 2763 Example of object: 2765 ... 2766 2767 ... 2768 2769 agnt0001-TEST 2770 2771 ... 2772 2773 ... 2775 5.4.2. CSV Model 2777 For the CSV Model of the registrar object, the 2778 child element of the element 2779 is used to hold the new or updated registrar objects for the deposit. 2780 The child element of the element 2781 is used to hold the deleted or purged registrar objects for the 2782 deposit. Both the and 2783 elements contain one or more elements with a set of 2784 named CSV file definitions using the "name" attribute. 2786 Differential and incremental deposits are based on changes to the 2787 registrar objects. The updated registrar object data under the 2788 element is a cascade replace down all of the 2789 registrar CSV files starting with the parent "registrar" CSV File 2790 Definition (Section 5.4.2.1.1). The child CSV file definitions 2791 include a field. All the child CSV 2792 file definition data for the registrar objects in the parent 2793 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2794 deleted and then set using the data in the child CSV files. The 2795 deleted registrar object data under the 2796 element is a cascade delete starting from the "registrar" Deletes CSV 2797 File Definition (Section 5.4.2.2.1). 2799 5.4.2.1. 2801 The is used to hold the new or updated 2802 registrar object information for the deposit. The 2803 is split into separate CSV file definitions 2804 using named elements with the "name" attribute. The 2805 following sections include the supported contact CSV file 2806 definitions. 2808 5.4.2.1.1. "registrar" CSV File Definition 2810 The "registrar" CSV File Definition defines the fields and CSV file 2811 references used for the registrar object records. 2813 The following "csvRegistrar" field elements MUST be used in the 2814 "registrar" element: 2816 Contains the server-unique registrar identifier 2817 with type="eppcom:clIDType" and isRequired="true". 2819 Contains the name of the registrar with 2820 type="normalizedString" and isRequired="true". 2822 The following field elements MAY be used in the "registrar" 2823 element: 2825 Contains the status of the registrar with 2826 type="csvRegistrar:statusValueType". 2828 Contains the ID assigned by ICANN with 2829 type="positiveInteger". 2831 Contains the Whois URL of the registrar 2832 with type="anyURI". 2834 The following "rdeCsv" fields, defined in section CSV common field 2835 elements (Section 4.7.2), MAY be used in the "registrar" 2836 element: 2838 Created date and time of the registrar object. 2840 Date and time of the last update to the registrar 2841 object. 2843 URL for the registrar web home page. 2845 The following "csvContact" fields, defined in section Contact Object 2846 (Section 5.3), MAY be used in the "registrar" 2847 element: 2849 Registrar street address line with an "index" 2850 attribute that represents the order of the street address line 2851 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2852 indicate the localized or internationalized form, as defined in 2853 Section 4.8. 2855 Registrar city with an OPTIONAL "isLoc" attribute 2856 that is used to indicate the localized or internationalized form, 2857 as defined in Section 4.8. 2859 Registrar country code with an OPTIONAL "isLoc" 2860 attribute that is used to indicate the localized or 2861 internationalized form, as defined in Section 4.8. 2863 Registrar email address. 2865 Registrar state or province with an OPTIONAL 2866 "isLoc" attribute that is used to indicate the localized or 2867 internationalized form, as defined in Section 4.8. 2869 Registrar postal code with an OPTIONAL "isLoc" 2870 attribute that is used to indicate the localized or 2871 internationalized form, as defined in Section 4.8. 2873 Registrar voice telephone number. 2875 Registrar voice telephone number extension. 2877 Registrar facsimile telephone number. 2879 Registrar facsimile telephone number extension. 2881 Example of a "registrar" 2882 element. 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 2910 2911 2913 registrar-YYYYMMDD.csv 2914 2915 2916 2917 ... 2918 2919 ... 2921 Example of the registrar-YYYYMMDD.csv file. The file contains three 2922 registrar records. 2924 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 2925 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2926 +1.7035555556,,jdoe@example.test,http://www.example.test, 2927 http://whois.example.test,2005-04-23T11:49:00.0Z, 2928 2009-02-17T17:51:00.0Z 2929 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 2930 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2931 +1.7035555556,,jdoe@example.test,http://www.example.test, 2932 http://whois.example.test,2005-04-23T11:49:00.0Z, 2933 2009-02-17T17:51:00.0Z 2934 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 2935 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2936 +1.7035555556,,jdoe@example.test,http://www.example.test, 2937 http://whois.example.test,2005-04-23T11:49:00.0Z, 2938 2009-02-17T17:51:00.0Z 2940 5.4.2.2. 2942 The is used to hold the deleted registrar 2943 objects in a differential or incremental deposit. All the registrar 2944 object data is deleted as part of a cascade delete. The 2945 is split into separate CSV file definitions 2946 using named elements with the "name" attribute. The 2947 following section defines the supported registrar deletes CSV file 2948 definition. 2950 5.4.2.2.1. "registrar" Deletes CSV File Definition 2952 The following "csvRegistrar" field elements MUST be used in the 2953 deletes "registrar" element: 2955 Contains the server-unique registrar identifier 2956 with type="eppcom:clIDType" and isRequired="true". 2958 Example of a "registrar" element. 2960 ... 2961 2962 ... 2963 2964 2965 2966 2967 2968 2970 registrar-delete-YYYYMMDD.csv 2971 2972 2973 2974 ... 2975 2976 ... 2978 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 2979 one registrar record. 2981 registrarZ 2983 5.5. IDN Table Reference Object 2985 The Internationalized Domain Names (IDN) table reference object is a 2986 pseudo-object that is used to provide a short reference to the IDN 2987 Table and Policy used in IDN registrations. The IDN reference object 2988 supports both the XML and the CSV Model, defined in the Models 2989 (Section 2) section. The elements used for both models are defined 2990 in the following sections. 2992 5.5.1. XML Model 2994 There is one element used in the data escrow of the IDN table 2995 reference objects for the XML model that is the , 2996 under the element. 2998 5.5.1.1. object 3000 The contains the following elements. An "id" 3001 attribute is used to specify an identifier for the IDN table. 3003 o An element that contains the URL of the IDN table that is 3004 being referenced. 3006 o A element that contains the URL of the IDN policy 3007 document. If IDN variants are generated algorithmically, the 3008 policy document MUST define the algorithm and the state of the 3009 implicit generated IDN variants. For a list of suggested states 3010 for implicit IDN variants, please see [variantTLDsReport]. 3012 Example of object: 3014 ... 3015 3016 3017 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3018 3019 3020 http://registro.br/dominio/regras.html 3021 3022 3023 ... 3025 5.5.2. CSV Model 3027 The IDN domain names, defined in Section 5.1, MAY have references to 3028 the IDN language identifier using the field 3029 element. The IDN table reference object defines the mapping of a 3030 language identifier to a language table URL. The language table URL 3031 defines the character code points that can be used for the language 3032 identifier. The elements used for the IDN table reference object is 3033 defined in this section. The child element of the 3034 element is used to hold the new or updated IDN table 3035 reference objects for the deposit. The child 3036 element of the element is used to hold the deleted or 3037 purged IDN table reference objects for the deposit. Both the 3038 and elements contain one or more 3039 elements with a set of named CSV file definitions using 3040 the "name" attribute. 3042 5.5.2.1. 3044 The is used to hold the new or updated IDN table 3045 reference object information for the deposit. The 3046 is split into separate CSV file definitions using named 3047 elements with the "name" attribute. The following sections include 3048 the supported IDN table reference CSV file definitions. 3050 5.5.2.1.1. "idnLanguage" CSV File Definition 3052 The "idnLanguage" CSV File Definition defines the fields and CSV file 3053 references used for the IDN table reference object records. 3055 The following "rdeCsv" fields, defined in Section 4.7.2, MUST be used 3056 in the "idnLanguage" element: 3058 The language identifier that matches the values 3059 for the field element in the "domain" CSV 3060 File Definition (Section 5.1.2.1.1) files. The attribute 3061 isRequired MUST equal "true". 3063 URL that defines the character code points that can be 3064 used for the language defined by the field element. 3065 The attribute isRequired MUST equal "true". 3067 Example of a "idnLanguage" element. 3069 ... 3070 3071 ... 3072 3073 , 3074 3075 3076 3077 3078 3079 3081 idnLanguage-YYYYMMDD.csv 3082 3083 3084 3085 ... 3086 3087 ... 3089 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3090 contains two IDN language records. 3092 LANG-1, 3093 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3094 LANG-2, 3095 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3097 5.5.2.2. 3099 The is used to hold the deleted IDN table reference 3100 objects in a differential or incremental deposit. The 3101 is split into separate CSV file definitions using 3102 named elements with the "name" attribute. The following 3103 section defines the supported IDN table reference deletes CSV file 3104 definition. 3106 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3108 The following "idnLanguage" field elements MUST be used in the 3109 deletes "idnLanguage" element: 3111 The language identifier that matches the values 3112 for the field element in the "domain" CSV 3113 File Definition (Section 5.1.2.1.1) files. The attribute 3114 isRequired MUST equal "true". 3116 Example of a "idnLanguage" element. 3118 ... 3119 3120 ... 3121 3122 3123 3124 3125 3126 3128 idnLanguage-delete-YYYYMMDD.csv 3129 3130 3131 3132 ... 3133 3134 ... 3136 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3137 contains one IDN language record. 3139 LANG-2 3141 5.6. NNDN Object 3143 A NNDN (NNDN's not domain name) can be used to store registry 3144 reserved names or (blocked, withheld or mirrored) IDN variants. 3146 A NNDN is a lightweight domain-like object that is not linked 3147 directly to a Registrar (a mirroring NNDN is linked to a Registrar 3148 via the original name). 3150 A domain name can only exist as a domain name object or NNDN object, 3151 but not both. 3153 The NNDN object supports both the XML and the CSV Model, defined in 3154 the Models (Section 2) section. The elements used for both models 3155 are defined in the following sections. 3157 5.6.1. XML Model 3159 There are two elements used in the data escrow of the NNDN objects 3160 for the XML model including the , under the 3161 element, and the element, under the 3162 element. 3164 A element substitutes for the 3165 abstract element to define a concrete definition of a NNDN. The 3166 element can be replaced by other NNDN 3167 definitions using the XML schema substitution groups feature. 3169 5.6.1.1. object 3171 The element contains the following child elements: 3173 o An element that contains the fully qualified name of the 3174 NNDN. If the NNDN is an IDN, the ASCII Compatible Encoding (ACE) 3175 MUST be used. 3177 o An OPTIONAL element that contains the fully qualified name 3178 of the NNDN in Unicode character set. It MUST be provided if 3179 available. 3181 o An OPTIONAL element that references the IDN 3182 Table used for the NNDN. This corresponds to the "id" attribute 3183 of the element. This element MUST be present if the 3184 NNDN is an IDN. 3186 o An OPTIONAL element is used to indicate that the 3187 NNDN is used for an IDN variant. This element contains the domain 3188 name used to generate the IDN variant. 3190 o A element that indicates the state of the NNDN: 3191 blocked, withheld or mirrored. 3193 * If a NNDN is considered undesirable for registration (i.e., 3194 unavailable for allocation to anyone), then the NNDN will be 3195 tagged as "blocked". 3197 * If a NNDN is considered a potential registration of a domain 3198 object for a registrant, then the NNDN will be tagged as 3199 "withheld". This status is only used when the NNDN is used for 3200 an IDN variant. 3202 * If a NNDN is considered a mirrored IDN variant of a domain 3203 object, then the NNDN will be tagged as "mirrored". A 3204 mirroringNS attribute is used to specify if the mirrored IDN 3205 variant use the NS mirror mechanism. The default value of 3206 mirroringNS is true. If another mechanism such as DNAME is 3207 used, the value of mirroringNS attribute MUST be false. 3209 o A element that contains the date and time of the NNDN 3210 object creation. 3212 Example of object: 3214 ... 3215 3216 xn--exampl-gva.test 3217 pt-BR 3218 example1.test 3219 withheld 3220 2005-04-23T11:49:00.0Z 3221 3222 ... 3224 5.6.1.2. object 3226 The element contains the ACE of a NNDN that was 3227 deleted, i.e., the . 3229 Example of object: 3231 ... 3232 3233 ... 3234 3235 xn--pingino-q2a.test 3236 3237 ... 3238 3239 ... 3241 5.6.2. CSV Model 3243 For the CSV Model of the NNDN object, the child 3244 element of the element is used to hold the new or 3245 updated NNDN objects for the deposit. The child 3246 element of the element is used to hold the deleted or 3247 purged NNDN objects for the deposit. Both the and 3248 elements contain one or more elements 3249 with a set of named CSV file definitions using the 3250 "name" attribute. 3252 5.6.2.1. 3254 The is used to hold the new or updated NNDN object 3255 information for the deposit. The is split into 3256 separate CSV file definitions using named elements with 3257 the "name" attribute. The following sections include the supported 3258 NNDN CSV file definitions. 3260 5.6.2.1.1. "NNDN" CSV File Definition 3262 The "NNDN" CSV File Definition defines the fields and CSV file 3263 references used for the NNDN object records. 3265 The following "csvNNDN" field elements MUST be used in the "NNDN" 3266 element: 3268 ASCII Compatible Encoding (ACE) field of the NNDN 3269 with type="eppcom:labelType" and isRequired="true". 3271 State of the NNDN: blocked or withheld with 3272 type="rdeNNDN:nameState" and isRequired="true". See 3273 Section 5.6.1.1 for a description of the possible values for the 3274 element. 3276 The following field elements MAY be used in the "NNDN" 3277 element: 3279 Domain name used to generate the IDN variant 3280 with type="eppcom:labelType". 3282 Defines whether the "mirroring" 3283 uses the NS mirror mechanism, as described 3284 for the "mirroringNS" attribute in 3285 Section 5.6.1.1, with type="boolean". If the field element is not 3286 defined the default value is "true". 3288 The following "rdeCsv" fields, defined in section CSV common field 3289 elements (Section 4.7.2), MUST be used in the "domain" 3290 element: 3292 Created date and time of the NNDN object with 3293 isRequired="true". 3295 The following "rdeCsv" fields, defined in section CSV common field 3296 elements (Section 4.7.2), MAY be used in the "domain" 3297 element: 3299 Name of the NNDN in Unicode character set for the 3300 field element. 3302 IDN Table Identifier for the NNDN that matches 3303 an IDN Table Reference Object record, as defined in Section 5.5.2. 3305 Example of a "NNDN" element: 3307 ... 3308 3309 ... 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3322 NNDN-YYYYMMDD.csv 3323 3324 3325 3326 ... 3327 3328 ... 3330 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3331 contains two NNDN records for an IDN with one blocked variant and one 3332 mirrored variant. 3334 xn--abc456.test,LANG-1,xn--abc123.test, 3335 blocked,,2005-04-23T11:49:00.0Z 3336 xn--abc789.test,LANG-1,xn--abc123.test, 3337 mirrored,1,2005-04-23T11:49:00.0Z 3339 5.6.2.2. 3341 The is used to hold the deleted NNDN objects in a 3342 differential or incremental deposit. The is split 3343 into separate CSV file definitions using named elements 3344 with the "name" attribute. The following section defines the 3345 supported NNDN deletes CSV file definition. 3347 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3349 The following "NNDN" field elements MUST be used in the deletes 3350 "NNDN" element: 3352 ASCII Compatible Encoding (ACE) field of the NNDN 3353 with type="eppcom:labelType" and isRequired="true". 3355 Example of a "NNDN" element. 3357 ... 3358 3359 ... 3360 3361 3362 3363 3364 3365 3367 NNDN-delete-YYYYMMDD.csv 3368 3369 3370 3371 ... 3372 3373 ... 3375 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3376 contains one NNDN records. 3378 xn--abc456.test 3380 5.7. EPP Parameters Object 3382 The EPP Parameters Object is a pseudo-object that defines the set of 3383 object and object extension services supported by the registry, as 3384 defined in [RFC5730]. The EPP Parameters Object is only defined as 3385 XML but could be used in the XML model or CSV model. The EPP 3386 Parameters Object is defined using the 3387 element. The EPP Parameters Object SHOULD be included if the 3388 registry supports EPP. Only one EPP Parameters Object MUST exist at 3389 a certain point in time (watermark). 3391 The syntax and content of the children 3392 elements is as explained in section 2.4 of [RFC5730]. The children 3393 of the are as follows: 3395 o One or more elements that indicate the EPP versions 3396 supported by the registry. 3398 o One or more elements that indicate the identifiers of the 3399 text response languages supported by the registry's EPP server. 3401 o One or more elements that contain namespace URIs 3402 representing the objects that the registry's EPP server is capable 3403 of managing. 3405 o An OPTIONAL element that contains one or more 3406 elements that contain namespace URIs representing object 3407 extensions supported by the registry's EPP server. 3409 o A element that contains child elements used to describe the 3410 server's privacy policy for data collection and management. See 3411 section 2.4 of [RFC5730] for more details. 3413 Example of element object: 3415 ... 3416 3417 1.0 3418 en 3419 urn:ietf:params:xml:ns:domain-1.0 3420 3421 urn:ietf:params:xml:ns:contact-1.0 3422 3423 urn:ietf:params:xml:ns:host-1.0 3424 3425 3426 urn:ietf:params:xml:ns:rgp-1.0 3427 urn:ietf:params:xml:ns:secDNS-1.1 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 ... 3448 5.8. Policy Object 3450 The Policy object is a pseudo-object that is used to specify which 3451 OPTIONAL elements from the XML Model are REQUIRED based on the 3452 business model of the registry. For the CSV Model, the OPTIONAL 3453 "isRequired" attribute of the elements, defined in 3454 Section 4.7.1, is used to specify which OPTIONAL fields are REQUIRED 3455 based on the business model of the registry. 3457 5.8.1. object 3459 The OPTIONAL contains the following attributes: 3461 o An that defines that the referenced is 3462 REQUIRED. 3464 o that defines the XPath of the element referenced by 3465 . 3467 Example of object: 3469 ... 3470 3472 ... 3474 5.9. Header Object 3476 The Header Object is a pseudo-object that is used to specify the 3477 number of objects in the repository at a specific point in time 3478 (watermark) regardless of the type of deposit: differential, full or 3479 incremental. The Header Object is only defined as XML but one header 3480 object MUST always be present per escrow deposit regardless of using 3481 XML Model or CSV Model. The Header Object is defined using the 3482 element. 3484 5.9.1. object 3486 The contains the following elements: 3488 o A choice of one of the elements defined in the 3489 "repositoryTypeGroup" group element that indicates the unique 3490 identifier for the repository being escrowed. Possible elements 3491 are: 3493 * A element that defines TLD or the REGISTRY- 3494 CLASS DOMAIN NAME (RCDN) being escrowed in the case of a 3495 Registry data escrow deposit. For IDNs the A-Label is used 3496 [RFC5891]. 3498 * A element that defines the Registrar ID 3499 corresponding to a Registrar data escrow deposit. In the case 3500 of an ICANN-accredited Registrar, the 3501 element MUST be the IANA Registrar ID assigned by ICANN. 3503 * A element that defines the provider ID 3504 corresponding to a Privacy and Proxy Services Provider data 3505 escrow deposit. In the case of an ICANN-accredited Privacy and 3506 Proxy Services Provider, the element MUST be 3507 the unique ID assigned by ICANN. 3509 * A element that defines the provider ID 3510 corresponding to a Reseller data escrow deposit. 3512 o A element that contains the number of objects in the SRS 3513 at a specific point in time (watermark) regardless of the type of 3514 deposit: differential, full or incremental. The element 3515 supports the following attributes: 3517 * A "uri" attribute reflects the XML namespace URI of the primary 3518 objects for the XML Model and CSV Model. For example, the 3519 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3520 domain name objects using the XML Model, and the "uri" is set 3521 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3522 objects using the CSV Model. 3524 * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS 3525 DOMAIN NAME (RCDN) of the objects included in the 3526 element. For IDNs the A-Label is used [RFC5891]. If the 3527 "rcdn" attribute is present, the value of the element 3528 must include only objects related to registrations in the same 3529 and lower levels. For example in a data escrow deposit for the 3530 .EXAMPLE TLD, a value of "example" in the "rcdn" attribute 3531 within the element indicates the number of objects in 3532 the TLD including objects in other RCDNs within the TLD, 3533 whereas a value of "com.example" indicates the number of 3534 elements for objects under "com.example" and lower levels. 3535 Omitting the "rcdn" attribute indicates that the total includes 3536 all objects of the specified "uri" in the repository (e.g. the 3537 TLD, Registrar, or PPSP). 3539 * An OPTIONAL "registrarId" attribute indicates the identifier of 3540 the sponsoring Registrar of the objects included in the 3541 element. In the case of an ICANN-accredited Registrar, the 3542 value MUST be the IANA Registrar ID assigned by ICANN. 3544 Example of object referencing only the XML Model 3545 objects: 3547 ... 3548 3549 test 3550 2 3552 1 3554 1 3556 1 3558 3559 1 3561 1 3563 1 3565 3566 3567 ... 3569 Example of object referencing the CSV and XML 3570 Model objects: 3572 ... 3573 3574 test 3575 2 3577 1 3579 1 3581 1 3583 3584 1 3586 1 3588 1 3590 3591 3592 ... 3594 6. RDE IDN Variants handling 3596 Depending on the Registration Policy of the Registry; for a domain 3597 name there may be multiple variant names. See [variantTLDsReport] 3598 for further detail on IDN variants. 3600 A registry could choose to escrow IDN variants as domains or NNDN 3601 objects. A specific IDN variant can be represented in the escrow 3602 deposit, as a domain or as a NNDN object, but not both. 3604 If using domain objects to represent IDN variants, the normal 3605 behavior during restoration of a SRS based on an escrow deposit is to 3606 restore the IDN variants as a mirrored variant. If the registration 3607 data of the IDN variant is different from the original name, the 3608 details of this specific implementation MUST be described in the IDN 3609 policy document. 3611 A NNDN or a domain name are explicit representations of an IDN 3612 variant while an IDN variant computed based on an algorithm is an 3613 implicit representation. Explicit representation of an IDN variant 3614 takes precedence over an implicit representation. 3616 7. Profile 3618 Different business models of registries exist, therefore the registry 3619 is responsible to define a profile that matches its particular 3620 business model. The profile mechanism allows a registry to extend 3621 this specification. 3623 A profile is the process of: 3625 1. Extending base objects with the mechanisms defined for XML and 3626 CSV models. 3628 * In the case of the XML model, abstract elements could be use 3629 to extend the following objects: , , , 3630 and using XML schema substitution groups 3631 feature. 3633 2. Defining a object to specify which OPTIONAL elements of 3634 this base specification is required based on the business model 3635 of the registry. An example is the element that is 3636 usually REQUIRED but it is specified as OPTIONAL in this 3637 specification to support existing business models. 3639 3. Adding new escrowed objects using the and 3640 elements. 3642 4. Providing the XML schemas to third parties that require them to 3643 validate the escrow deposits. 3645 8. Data escrow agent extended verification process 3647 A Data Escrow Agent SHOULD perform an extended verification process 3648 that starts by creating a dataset to be tested. 3650 o If a full deposit is to be tested, the full deposit is the 3651 dataset. 3653 o If an incremental deposit is to be tested, the dataset is created 3654 by using the incremental plus the last previous full deposit. 3656 o If a differential deposit is to be tested, the dataset is created 3657 by using the differential deposit plus all the required deposits 3658 leading to the last previous full deposit. 3660 The following are the minimum suggested tests on the dataset: 3662 o Validate the escrow deposits using the definition agreed with the 3663 registry. 3665 * In the case of the XML model, the contents of the escrow 3666 deposits MUST be validated using the XML schemas of the 3667 profile. 3669 o Count the objects and validate that the number of objects is equal 3670 to the number objects reported in the
element of the 3671 escrow deposit of that point in time (watermark). 3673 o All contact objects linked to domain names MUST be present. 3675 o All registrars objects linked to other objects MUST be present. 3677 o A domain name exists as a domain name or NNDN, but not both. 3679 o The elements listed as required in the element MUST be 3680 present. 3682 o All idnTableRef definitions linked from other objects MUST be 3683 present. 3685 o If an EPP Parameters Object was escrowed in the past, one and only 3686 one EPP Parameters Object MUST be present. 3688 o The watermark is not in the future. 3690 9. Formal Syntax 3692 Schemas are presented here. 3694 9.1. RDE CSV Schema 3696 Copyright (c) 2012 IETF Trust and the persons identified as authors 3697 of the code. All rights reserved. 3699 Redistribution and use in source and binary forms, with or without 3700 modification, are permitted provided that the following conditions 3701 are met: 3703 o Redistributions of source code must retain the above copyright 3704 notice, this list of conditions and the following disclaimer. 3706 o Redistributions in binary form must reproduce the above copyright 3707 notice, this list of conditions and the following disclaimer in 3708 the documentation and/or other materials provided with the 3709 distribution. 3711 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3712 names of specific contributors, may be used to endorse or promote 3713 products derived from this software without specific prior written 3714 permission. 3716 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3717 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3718 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3719 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3720 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3721 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3722 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3723 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3724 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3725 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3726 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3728 BEGIN 3729 3731 3738 3741 3743 3746 3747 3748 Registry Data Escrow Comma-Seperated Values (CSV) 3749 3750 3752 3753 3755 3756 3757 3758 3759 3760 3761 3762 3763 3765 3766 3767 3768 3769 3770 3771 3773 3774 3777 3778 3779 3781 3782 3783 3784 3785 3786 3788 3790 3791 3792 3794 3795 3796 3797 3798 3799 3801 3803 3804 3805 3807 3808 3809 3811 3812 3813 3814 3815 3817 3818 3819 3820 3821 3822 3823 3824 3826 3827 3828 3830 3831 3833 3834 3835 3836 3837 3839 3840 3841 3843 3844 3846 3847 3848 3849 3850 3852 3853 3854 3855 3856 3860 3861 3862 3864 3866 3868 3869 3871 3873 3875 3876 3878 3880 3882 3884 3886 3888 3890 3892 3894 3895 3896 3897 3898 3900 3901 3902 3903 3904 3905 3906 3907 3909 3910 3911 3913 3914 3916 3918 3920 3921 3923 3924 3926 3928 3929 3930 3931 3932 3934 3935 3936 3937 3938 3939 3940 3941 3943 3944 3945 3947 3948 3949 3950 3951 3952 3954 3955 3956 3957 3958 3959 3960 3961 3963 3964 3965 3967 3968 3969 3970 3971 3972 3974 3975 3976 3977 3978 3979 3980 3981 3983 3984 3985 3987 3988 3989 3990 3991 3992 3994 3995 3996 3997 3998 3999 4000 4001 4003 4004 4005 4007 4008 4009 4010 4011 4012 4014 4015 4016 4017 4018 4019 4020 4021 4023 4024 4025 4027 4028 4030 4031 4032 4033 4034 4036 4037 4038 4040 4041 4044 4045 4047 4048 4049 4050 4051 4053 4054 4055 4057 4058 4059 4060 4061 4062 4064 4065 4066 4068 4069 4070 4071 4072 4073 4075 4076 4077 4079 4080 4081 4082 4083 4084 4086 4087 4088 4090 4091 4093 4094 4095 4096 4097 4098 4100 4101 4102 4104 4105 4106 4107 4108 4109 4111 4112 4113 4114 4116 4117 4119 4120 4121 4122 4123 4124 4126 4127 4128 4129 4131 4132 4134 4135 4136 4137 4138 4141 4142 4143 4145 4148 4149 END 4151 9.2. RDE Domain Object 4153 Copyright (c) 2011 IETF Trust and the persons identified as authors 4154 of the code. All rights reserved. 4156 Redistribution and use in source and binary forms, with or without 4157 modification, are permitted provided that the following conditions 4158 are met: 4160 o Redistributions of source code must retain the above copyright 4161 notice, this list of conditions and the following disclaimer. 4163 o Redistributions in binary form must reproduce the above copyright 4164 notice, this list of conditions and the following disclaimer in 4165 the documentation and/or other materials provided with the 4166 distribution. 4168 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4169 names of specific contributors, may be used to endorse or promote 4170 products derived from this software without specific prior written 4171 permission. 4173 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4174 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4175 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4176 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4177 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4178 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4179 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4180 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4181 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4182 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4183 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4185 BEGIN 4186 4187 4198 4199 4200 4201 4202 4203 4205 4206 4207 Registry Data Escrow Domain provisioning schema 4208 4209 4211 4214 4216 4220 4221 4222 4223 4224 4225 4227 4229 4231 4233 4235 4238 4241 4243 4246 4248 4250 4252 4254 4256 4258 4260 4262 4264 4267 4268 4269 4270 4272 4273 4274 4276 4278 4280 4282 4284 4287 4288 4290 4291 4292 4293 4294 4295 4298 4299 4300 4301 4302 4303 END 4305 9.3. CSV Domain Object 4307 Copyright (c) 2012 IETF Trust and the persons identified as authors 4308 of the code. All rights reserved. 4310 Redistribution and use in source and binary forms, with or without 4311 modification, are permitted provided that the following conditions 4312 are met: 4314 o Redistributions of source code must retain the above copyright 4315 notice, this list of conditions and the following disclaimer. 4317 o Redistributions in binary form must reproduce the above copyright 4318 notice, this list of conditions and the following disclaimer in 4319 the documentation and/or other materials provided with the 4320 distribution. 4322 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4323 names of specific contributors, may be used to endorse or promote 4324 products derived from this software without specific prior written 4325 permission. 4327 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4328 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4329 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4330 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4331 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4332 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4333 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4334 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4335 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4336 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4337 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4339 BEGIN 4340 4342 4353 4356 4358 4360 4362 4364 4366 4369 4370 4371 Domain Name Comma-Separated Values (CSV) Object 4372 4373 4375 4378 4381 4382 4383 4384 4385 4386 4387 4388 4389 4391 4394 4397 4398 4399 4400 4401 4402 4403 4404 4405 4407 4408 4411 4412 4415 4416 4417 4418 4419 4421 4422 4423 4425 4426 4429 4430 4431 4432 4433 4435 4436 4437 4439 4441 4442 4444 4445 4446 4447 4448 4450 4451 4452 4454 4455 4458 4459 4462 4463 4466 4467 4470 4471 4474 4475 4478 4479 4482 4483 4485 4486 4487 4488 4489 4491 4492 4493 4495 4496 4499 4500 4504 4505 4508 4509 4510 4511 4512 4513 4515 4516 4517 4519 4522 4523 END 4525 9.4. RDE Host Object 4527 Copyright (c) 2011 IETF Trust and the persons identified as authors 4528 of the code. All rights reserved. 4530 Redistribution and use in source and binary forms, with or without 4531 modification, are permitted provided that the following conditions 4532 are met: 4534 o Redistributions of source code must retain the above copyright 4535 notice, this list of conditions and the following disclaimer. 4537 o Redistributions in binary form must reproduce the above copyright 4538 notice, this list of conditions and the following disclaimer in 4539 the documentation and/or other materials provided with the 4540 distribution. 4542 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4543 names of specific contributors, may be used to endorse or promote 4544 products derived from this software without specific prior written 4545 permission. 4547 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4548 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4549 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4550 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4551 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4552 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4553 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4554 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4555 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4556 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4557 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4559 BEGIN 4560 4561 4569 4570 4571 4572 4573 4574 Registry Data Escrow Host provisioning schema 4575 4576 4578 4580 4581 4584 4585 4586 4587 4588 4589 4591 4593 4595 4598 4600 4602 4604 4606 4608 4610 4611 4612 4613 4615 4616 4617 4618 4619 4620 4622 4624 4625 4626 4627 4628 4629 END 4631 9.5. CSV Host Object 4633 Copyright (c) 2012 IETF Trust and the persons identified as authors 4634 of the code. All rights reserved. 4636 Redistribution and use in source and binary forms, with or without 4637 modification, are permitted provided that the following conditions 4638 are met: 4640 o Redistributions of source code must retain the above copyright 4641 notice, this list of conditions and the following disclaimer. 4643 o Redistributions in binary form must reproduce the above copyright 4644 notice, this list of conditions and the following disclaimer in 4645 the documentation and/or other materials provided with the 4646 distribution. 4648 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4649 names of specific contributors, may be used to endorse or promote 4650 products derived from this software without specific prior written 4651 permission. 4653 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4654 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4655 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4656 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4657 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4658 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4659 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4660 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4661 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4662 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4663 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4665 BEGIN 4666 4667 4676 4679 4681 4683 4685 4688 4689 4690 Host Comma-Separated Values (CSV) Object 4691 4692 4694 4697 4700 4701 4702 4703 4704 4705 4706 4707 4708 4710 4713 4715 4716 4717 4718 4719 4720 4721 4722 4723 4725 4726 4729 4730 4732 4733 4734 4735 4736 4738 4739 4740 4742 4743 4745 4746 4747 4748 4749 4751 4752 4753 4755 4756 4759 4760 4761 4762 4763 4764 4766 4767 4768 4770 4773 4774 END 4776 9.6. RDE Contact Object 4778 Copyright (c) 2011 IETF Trust and the persons identified as authors 4779 of the code. All rights reserved. 4781 Redistribution and use in source and binary forms, with or without 4782 modification, are permitted provided that the following conditions 4783 are met: 4785 o Redistributions of source code must retain the above copyright 4786 notice, this list of conditions and the following disclaimer. 4788 o Redistributions in binary form must reproduce the above copyright 4789 notice, this list of conditions and the following disclaimer in 4790 the documentation and/or other materials provided with the 4791 distribution. 4793 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4794 names of specific contributors, may be used to endorse or promote 4795 products derived from this software without specific prior written 4796 permission. 4798 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4799 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4800 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4801 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4802 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4803 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4804 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4805 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4806 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4807 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4808 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4810 BEGIN 4811 4812 4820 4821 4822 4823 4825 4826 4827 Registry Data Escrow contact provisioning schema 4828 4829 4831 4834 4836 4840 4841 4842 4843 4844 4845 4847 4849 4851 4853 4855 4857 4859 4861 4863 4865 4867 4869 4871 4873 4875 4876 4877 4878 4880 4881 4882 4883 4884 4885 4886 4887 4888 4890 4891 4892 4893 4894 4895 4898 4899 4900 4901 4902 4903 END 4905 9.7. CSV Contact Object 4907 Copyright (c) 2012 IETF Trust and the persons identified as authors 4908 of the code. All rights reserved. 4910 Redistribution and use in source and binary forms, with or without 4911 modification, are permitted provided that the following conditions 4912 are met: 4914 o Redistributions of source code must retain the above copyright 4915 notice, this list of conditions and the following disclaimer. 4917 o Redistributions in binary form must reproduce the above copyright 4918 notice, this list of conditions and the following disclaimer in 4919 the documentation and/or other materials provided with the 4920 distribution. 4922 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4923 names of specific contributors, may be used to endorse or promote 4924 products derived from this software without specific prior written 4925 permission. 4927 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4928 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4929 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4930 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4931 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4932 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4933 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4934 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4935 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4936 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4937 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4939 BEGIN 4940 4942 4951 4955 4957 4959 4961 4964 4965 4966 Contact Comma-Separated Values (CSV) Object 4967 4968 4970 4973 4976 4977 4978 4979 4980 4981 4982 4983 4984 4986 4989 4992 4993 4994 4995 4996 4997 4998 4999 5000 5002 5003 5005 5006 5007 5008 5009 5011 5012 5013 5015 5016 5020 5021 5023 5025 5026 5027 5028 5029 5031 5032 5033 5035 5036 5038 5041 5042 5044 5045 5046 5047 5048 5050 5051 5052 5054 5058 5060 5061 5062 5063 5064 5066 5067 5068 5070 5071 5072 5073 5074 5075 5077 5078 5079 5080 5082 5083 5084 5085 5086 5087 5089 5090 5091 5092 5093 5094 5097 5098 5101 5102 5103 5105 5106 5107 5108 5109 5111 5112 5113 5115 5116 5119 5120 5123 5124 5126 5127 5128 5129 5130 5132 5133 5134 5135 5137 5138 5140 5141 5142 5143 5144 5146 5147 5148 5149 5151 5152 5154 5156 5158 5160 5162 5164 5166 5168 5170 5172 5174 5176 5178 5180 5182 5184 5186 5188 5190 5192 5193 5194 5195 5196 5198 5199 5200 5202 5203 5206 5207 5208 5209 5210 5211 5213 5214 5215 5217 5220 5221 END 5223 9.8. RDE Registrar Object 5225 Copyright (c) 2011 IETF Trust and the persons identified as authors 5226 of the code. All rights reserved. 5228 Redistribution and use in source and binary forms, with or without 5229 modification, are permitted provided that the following conditions 5230 are met: 5232 o Redistributions of source code must retain the above copyright 5233 notice, this list of conditions and the following disclaimer. 5235 o Redistributions in binary form must reproduce the above copyright 5236 notice, this list of conditions and the following disclaimer in 5237 the documentation and/or other materials provided with the 5238 distribution. 5240 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5241 names of specific contributors, may be used to endorse or promote 5242 products derived from this software without specific prior written 5243 permission. 5245 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5246 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5247 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5248 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5249 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5250 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5251 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5252 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5253 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5254 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5255 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5257 BEGIN 5258 5259 5268 5269 5270 5271 5272 5274 5275 5276 Registry Data Escrow registrar provisioning schema 5277 5278 5280 5284 5286 5289 5290 5291 5292 5293 5294 5296 5298 5300 5302 5305 5307 5309 5311 5313 5315 5317 5319 5320 5321 5322 5324 5325 5326 5327 5328 5329 5331 5332 5333 5334 5335 5336 5337 5339 5340 5341 5343 5344 5347 5349 5350 5351 5352 5353 5354 5356 5357 5358 5361 5363 5366 5368 5370 5371 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5385 5386 5387 5388 5389 5391 5392 5393 5394 5395 5397 5398 5399 5401 5403 5404 5406 5407 5408 5409 5410 5411 5414 5415 5416 5417 5418 5419 END 5421 9.9. CSV Registrar Object 5423 Copyright (c) 2012 IETF Trust and the persons identified as authors 5424 of the code. All rights reserved. 5426 Redistribution and use in source and binary forms, with or without 5427 modification, are permitted provided that the following conditions 5428 are met: 5430 o Redistributions of source code must retain the above copyright 5431 notice, this list of conditions and the following disclaimer. 5433 o Redistributions in binary form must reproduce the above copyright 5434 notice, this list of conditions and the following disclaimer in 5435 the documentation and/or other materials provided with the 5436 distribution. 5438 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5439 names of specific contributors, may be used to endorse or promote 5440 products derived from this software without specific prior written 5441 permission. 5443 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5444 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5445 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5446 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5447 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5448 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5449 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5450 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5451 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5452 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5453 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5455 BEGIN 5456 5458 5468 5471 5473 5475 5477 5479 5482 5483 5484 Registar Comma-Separated Values (CSV) Object 5485 5486 5488 5491 5494 5495 5496 5497 5498 5499 5500 5501 5502 5504 5507 5510 5511 5512 5513 5514 5515 5516 5517 5518 5520 5521 5524 5525 5528 5529 5530 5531 5532 5533 5535 5536 5537 5538 5540 5541 5545 5546 5548 5550 5551 5552 5553 5554 5556 5557 5558 5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5577 5578 5582 5585 5586 END 5588 9.10. RDE IDN Table Reference Objects 5590 Copyright (c) 2011 IETF Trust and the persons identified as authors 5591 of the code. All rights reserved. 5593 Redistribution and use in source and binary forms, with or without 5594 modification, are permitted provided that the following conditions 5595 are met: 5597 o Redistributions of source code must retain the above copyright 5598 notice, this list of conditions and the following disclaimer. 5600 o Redistributions in binary form must reproduce the above copyright 5601 notice, this list of conditions and the following disclaimer in 5602 the documentation and/or other materials provided with the 5603 distribution. 5605 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5606 names of specific contributors, may be used to endorse or promote 5607 products derived from this software without specific prior written 5608 permission. 5610 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5611 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5612 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5613 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5614 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5615 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5616 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5617 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5618 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5619 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5620 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5622 BEGIN 5623 5624 5630 5632 5633 5634 Registry Data Escrow IDN provisioning schema 5635 5636 5638 5640 5643 5644 5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5656 5657 5658 5659 5660 5661 5662 5664 5665 5667 5668 5669 5670 5671 5672 5673 5675 5676 END 5678 9.11. CSV IDN Language Object 5680 Copyright (c) 2012 IETF Trust and the persons identified as authors 5681 of the code. All rights reserved. 5683 Redistribution and use in source and binary forms, with or without 5684 modification, are permitted provided that the following conditions 5685 are met: 5687 o Redistributions of source code must retain the above copyright 5688 notice, this list of conditions and the following disclaimer. 5690 o Redistributions in binary form must reproduce the above copyright 5691 notice, this list of conditions and the following disclaimer in 5692 the documentation and/or other materials provided with the 5693 distribution. 5695 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5696 names of specific contributors, may be used to endorse or promote 5697 products derived from this software without specific prior written 5698 permission. 5700 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5701 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5702 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5703 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5704 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5705 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5706 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5707 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5708 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5709 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5710 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5712 BEGIN 5713 5715 5722 5725 5727 5730 5731 5732 IDN Language Comma-Separated Values (CSV) Object 5733 5734 5736 5739 5742 5743 5744 5745 5746 5747 5748 5749 5750 5752 5755 5758 5759 5760 5761 5762 5763 5764 5765 5766 5768 5771 5772 END 5774 9.12. EPP Parameters Object 5776 Copyright (c) 2011 IETF Trust and the persons identified as authors 5777 of the code. All rights reserved. 5779 Redistribution and use in source and binary forms, with or without 5780 modification, are permitted provided that the following conditions 5781 are met: 5783 o Redistributions of source code must retain the above copyright 5784 notice, this list of conditions and the following disclaimer. 5786 o Redistributions in binary form must reproduce the above copyright 5787 notice, this list of conditions and the following disclaimer in 5788 the documentation and/or other materials provided with the 5789 distribution. 5791 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5792 names of specific contributors, may be used to endorse or promote 5793 products derived from this software without specific prior written 5794 permission. 5796 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5797 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5798 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5799 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5800 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5801 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5802 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5803 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5804 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5805 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5806 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5808 BEGIN 5809 5810 5818 5819 5820 5822 5823 5824 Registry Data Escrow EPP Parameters schema 5825 5826 5828 5829 5832 5833 5836 5837 5838 5839 5840 5842 5844 5846 5849 5851 5852 5853 5854 5855 5856 END 5858 9.13. NNDN Object 5860 Copyright (c) 2011 IETF Trust and the persons identified as authors 5861 of the code. All rights reserved. 5863 Redistribution and use in source and binary forms, with or without 5864 modification, are permitted provided that the following conditions 5865 are met: 5867 o Redistributions of source code must retain the above copyright 5868 notice, this list of conditions and the following disclaimer. 5870 o Redistributions in binary form must reproduce the above copyright 5871 notice, this list of conditions and the following disclaimer in 5872 the documentation and/or other materials provided with the 5873 distribution. 5875 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5876 names of specific contributors, may be used to endorse or promote 5877 products derived from this software without specific prior written 5878 permission. 5880 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5881 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5882 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5883 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5884 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5885 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5886 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5887 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5888 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5889 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5890 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5892 BEGIN 5893 5894 5902 5903 5904 5906 5907 5908 Registry Data Escrow NNDN provisioning schema 5909 5910 5912 5914 5915 5918 5919 5920 5921 5922 5923 5925 5927 5929 5931 5933 5935 5936 5937 5938 5940 5941 5942 5943 5944 5945 5946 5948 5949 5950 5951 5953 5954 5955 5957 5958 5959 5960 5961 5962 5965 5966 5967 5968 5969 5970 END 5972 9.14. CSV NNDN Object 5974 Copyright (c) 2013 IETF Trust and the persons identified as authors 5975 of the code. All rights reserved. 5977 Redistribution and use in source and binary forms, with or without 5978 modification, are permitted provided that the following conditions 5979 are met: 5981 o Redistributions of source code must retain the above copyright 5982 notice, this list of conditions and the following disclaimer. 5984 o Redistributions in binary form must reproduce the above copyright 5985 notice, this list of conditions and the following disclaimer in 5986 the documentation and/or other materials provided with the 5987 distribution. 5989 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5990 names of specific contributors, may be used to endorse or promote 5991 products derived from this software without specific prior written 5992 permission. 5994 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5995 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5996 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5997 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5998 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5999 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6000 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6001 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6002 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6003 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6004 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6006 BEGIN 6007 6009 6017 6020 6022 6024 6027 6028 6029 NNDN (NNDN's not domain name) (CSV) Object 6030 6031 6033 6036 6039 6040 6041 6042 6043 6044 6045 6046 6047 6048 6051 6054 6055 6056 6057 6058 6059 6060 6061 6062 6064 6065 6068 6069 6072 6073 6077 6078 6081 6082 6083 6084 6085 6087 6088 6089 6091 6092 6095 6098 6099 END 6101 9.15. Policy Object 6103 Copyright (c) 2011 IETF Trust and the persons identified as authors 6104 of the code. All rights reserved. 6106 Redistribution and use in source and binary forms, with or without 6107 modification, are permitted provided that the following conditions 6108 are met: 6110 o Redistributions of source code must retain the above copyright 6111 notice, this list of conditions and the following disclaimer. 6113 o Redistributions in binary form must reproduce the above copyright 6114 notice, this list of conditions and the following disclaimer in 6115 the documentation and/or other materials provided with the 6116 distribution. 6118 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6119 names of specific contributors, may be used to endorse or promote 6120 products derived from this software without specific prior written 6121 permission. 6123 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6124 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6125 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6126 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6127 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6128 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6129 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6130 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6131 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6132 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6133 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6135 BEGIN 6136 6137 6143 6144 6145 Registry Data Escrow Policy schema 6146 6147 6149 6150 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 END 6164 9.16. Header Object 6166 Copyright (c) 2011 IETF Trust and the persons identified as authors 6167 of the code. All rights reserved. 6169 Redistribution and use in source and binary forms, with or without 6170 modification, are permitted provided that the following conditions 6171 are met: 6173 o Redistributions of source code must retain the above copyright 6174 notice, this list of conditions and the following disclaimer. 6176 o Redistributions in binary form must reproduce the above copyright 6177 notice, this list of conditions and the following disclaimer in 6178 the documentation and/or other materials provided with the 6179 distribution. 6181 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6182 names of specific contributors, may be used to endorse or promote 6183 products derived from this software without specific prior written 6184 permission. 6186 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6187 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6188 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6189 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6190 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6191 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6192 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6193 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6194 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6195 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6196 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6198 BEGIN 6199 6200 6207 6208 6210 6211 6212 Data Escrow Deposit Header schema 6213 6214 6216 6217 6220 6221 6222 6223 6224 6225 6226 6228 6229 6230 6232 6234 6235 6236 6237 6238 6239 6240 6241 6243 6244 6245 6246 6247 6248 6249 6250 6251 6253 6254 END 6256 10. Internationalization Considerations 6258 Data Escrow deposits are represented in XML, which provides native 6259 support for encoding information using the Unicode character set and 6260 its more compact representations including UTF-8. Conformant XML 6261 processors recognize both UTF-8 and UTF-16. Though XML includes 6262 provisions to identify and use other character encodings through use 6263 of an "encoding" attribute in an declaration, use of UTF-8 is 6264 RECOMMENDED. 6266 11. IANA Considerations 6268 This document uses URNs to describe XML namespaces and XML schemas 6269 conforming to a registry mechanism described in [RFC3688]. Fourteen 6270 URI assignments have been registered by the IANA. 6272 Registration request for the RDE CSV namespace: 6274 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6276 Registrant Contact: See the "Author's Address" section of this 6277 document. 6279 XML: None. Namespace URIs do not represent an XML specification. 6281 Registration request for the RDE CSV XML schema: 6283 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6285 Registrant Contact: See the "Author's Address" section of this 6286 document. 6288 See the "Formal Syntax" section of this document. 6290 Registration request for the RDE domain namespace: 6292 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6294 Registrant Contact: See the "Author's Address" section of this 6295 document. 6297 XML: None. Namespace URIs do not represent an XML specification. 6299 Registration request for the RDE domain XML schema: 6301 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6303 Registrant Contact: See the "Author's Address" section of this 6304 document. 6306 See the "Formal Syntax" section of this document. 6308 Registration request for the CSV domain namespace: 6310 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6312 Registrant Contact: See the "Author's Address" section of this 6313 document. 6315 XML: None. Namespace URIs do not represent an XML specification. 6317 Registration request for the CSV domain XML schema: 6319 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6321 Registrant Contact: See the "Author's Address" section of this 6322 document. 6324 See the "Formal Syntax" section of this document. 6326 Registration request for the RDE host namespace: 6328 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6329 Registrant Contact: See the "Author's Address" section of this 6330 document. 6332 XML: None. Namespace URIs do not represent an XML specification. 6334 Registration request for the RDE host XML schema: 6336 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6338 Registrant Contact: See the "Author's Address" section of this 6339 document. 6341 See the "Formal Syntax" section of this document. 6343 Registration request for the CSV host namespace: 6345 URI: urn:ietf:params:xml:ns:csvHost-1.0 6347 Registrant Contact: See the "Author's Address" section of this 6348 document. 6350 XML: None. Namespace URIs do not represent an XML specification. 6352 Registration request for the CSV host XML schema: 6354 URI: urn:ietf:params:xml:schema:csvHost-1.0 6356 Registrant Contact: See the "Author's Address" section of this 6357 document. 6359 See the "Formal Syntax" section of this document. 6361 Registration request for the RDE contact namespace: 6363 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6365 Registrant Contact: See the "Author's Address" section of this 6366 document. 6368 XML: None. Namespace URIs do not represent an XML specification. 6370 Registration request for the RDE contact XML schema: 6372 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6374 Registrant Contact: See the "Author's Address" section of this 6375 document. 6377 See the "Formal Syntax" section of this document. 6379 Registration request for the CSV contact namespace: 6381 URI: urn:ietf:params:xml:ns:csvContact-1.0 6383 Registrant Contact: See the "Author's Address" section of this 6384 document. 6386 XML: None. Namespace URIs do not represent an XML specification. 6388 Registration request for the CSV contact XML schema: 6390 URI: urn:ietf:params:xml:schema:csvContact-1.0 6392 Registrant Contact: See the "Author's Address" section of this 6393 document. 6395 See the "Formal Syntax" section of this document. 6397 Registration request for the RDE registrar namespace: 6399 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6401 Registrant Contact: See the "Author's Address" section of this 6402 document. 6404 XML: None. Namespace URIs do not represent an XML specification. 6406 Registration request for the RDE registrar XML schema: 6408 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6410 Registrant Contact: See the "Author's Address" section of this 6411 document. 6413 See the "Formal Syntax" section of this document. 6415 Registration request for the CSV registrar namespace: 6417 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6419 Registrant Contact: See the "Author's Address" section of this 6420 document. 6422 XML: None. Namespace URIs do not represent an XML specification. 6424 Registration request for the CSV registrar XML schema: 6426 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6428 Registrant Contact: See the "Author's Address" section of this 6429 document. 6431 See the "Formal Syntax" section of this document. 6433 Registration request for the RDE IDN namespace: 6435 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6437 Registrant Contact: See the "Author's Address" section of this 6438 document. 6440 XML: None. Namespace URIs do not represent an XML specification. 6442 Registration request for the RDE IDN XML schema: 6444 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6446 Registrant Contact: See the "Author's Address" section of this 6447 document. 6449 See the "Formal Syntax" section of this document. 6451 Registration request for the CSV IDN namespace: 6453 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6455 Registrant Contact: See the "Author's Address" section of this 6456 document. 6458 XML: None. Namespace URIs do not represent an XML specification. 6460 Registration request for the CSV IDN XML schema: 6462 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6464 Registrant Contact: See the "Author's Address" section of this 6465 document. 6467 See the "Formal Syntax" section of this document. 6469 Registration request for the RDE NNDN namespace: 6471 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6472 Registrant Contact: See the "Author's Address" section of this 6473 document. 6475 XML: None. Namespace URIs do not represent an XML specification. 6477 Registration request for the RDE NNDN XML schema: 6479 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6481 Registrant Contact: See the "Author's Address" section of this 6482 document. 6484 See the "Formal Syntax" section of this document. 6486 Registration request for the CSV NNDN namespace: 6488 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6490 Registrant Contact: See the "Author's Address" section of this 6491 document. 6493 XML: None. Namespace URIs do not represent an XML specification. 6495 Registration request for the CSV NNDN XML schema: 6497 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6499 Registrant Contact: See the "Author's Address" section of this 6500 document. 6502 See the "Formal Syntax" section of this document. 6504 Registration request for the RDE EPP parameters namespace: 6506 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6508 Registrant Contact: See the "Author's Address" section of this 6509 document. 6511 XML: None. Namespace URIs do not represent an XML specification. 6513 Registration request for the RDE EPP parameters XML schema: 6515 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6517 Registrant Contact: See the "Author's Address" section of this 6518 document. 6520 See the "Formal Syntax" section of this document. 6522 12. Implementation Status 6524 Note to RFC Editor: Please remove this section and the reference to 6525 RFC 7942 [RFC7942] before publication. 6527 This section records the status of known implementations of the 6528 protocol defined by this specification at the time of posting of this 6529 Internet-Draft, and is based on a proposal described in RFC 7942 6530 [RFC7942]. The description of implementations in this section is 6531 intended to assist the IETF in its decision processes in progressing 6532 drafts to RFCs. Please note that the listing of any individual 6533 implementation here does not imply endorsement by the IETF. 6534 Furthermore, no effort has been spent to verify the information 6535 presented here that was supplied by IETF contributors. This is not 6536 intended as, and must not be construed to be, a catalog of available 6537 implementations or their features. Readers are advised to note that 6538 other implementations may exist. 6540 According to RFC 7942 [RFC7942], "this will allow reviewers and 6541 working groups to assign due consideration to documents that have the 6542 benefit of running code, which may serve as evidence of valuable 6543 experimentation and feedback that have made the implemented protocols 6544 more mature. It is up to the individual working groups to use this 6545 information as they see fit". 6547 12.1. Implementation in the gTLD space 6549 Organization: ICANN 6551 Name: ICANN Registry Agreement 6553 Description: the ICANN Base Registry Agreement requires Registries, 6554 Data Escrow Agents, and ICANN to implement this specification. ICANN 6555 receives daily notifications from Data Escrow Agents confirming that 6556 more than 1,200 gTLDs are sending deposits that comply with this 6557 specification. ICANN receives on a weekly basis per gTLD, from more 6558 than 1,200 gTLD registries, a Bulk Registration Data Access file that 6559 also complies with this specification. In addition, ICANN is aware 6560 of Registry Service Provider transitions using data files that 6561 conform to this specification. 6563 Level of maturity: production. 6565 Coverage: all aspects of this specification are implemented. 6567 Version compatibility: versions 03 - 08 are known to be implemented. 6569 Contact: gustavo.lozano@icann.org 6571 URL: https://www.icann.org/resources/pages/registries/registries- 6572 agreements-en 6574 13. Security Considerations 6576 This specification does not define the security mechanisms to be used 6577 in the transmission of the data escrow deposits, since it only 6578 specifies the minimum necessary to enable the rebuilding of a 6579 Registry from deposits without intervention from the original 6580 Registry. 6582 Depending on local policies, some elements or most likely, the whole 6583 deposit will be considered confidential. As such the Registry 6584 transmitting the data to the Escrow Agent SHOULD take all the 6585 necessary precautions like encrypting the data itself and/or the 6586 transport channel to avoid inadvertent disclosure of private data. 6588 It is also of the utmost importance the authentication of the parties 6589 passing data escrow deposit files. The Escrow Agent SHOULD properly 6590 authenticate the identity of the Registry before accepting data 6591 escrow deposits. In a similar manner, the Registry SHOULD 6592 authenticate the identity of the Escrow Agent before submitting any 6593 data. 6595 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6596 checking mechanisms to ensure the data transmitted is what the source 6597 intended. Validation of the contents by the Escrow Agent is 6598 RECOMMENDED to ensure not only the file was transmitted correctly 6599 from the Registry, but also the contents are also "meaningful". 6601 14. Privacy Considerations 6603 This specification defines a format that may be used to escrow 6604 personal data. The process of data escrow is governed by a legal 6605 document agreed by the parties, and such legal document must regulate 6606 the particularities regarding the protection of personal data. 6608 15. Acknowledgments 6610 Parts of this document are based on EPP [RFC5730] and related RFCs by 6611 Scott Hollenbeck. 6613 Special suggestions that have been incorporated into this document 6614 were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc 6615 Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen 6616 Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul 6617 Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, 6618 Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James 6619 Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. 6621 Shoji Noguchi and Francisco Arias participated as co-authors until 6622 version 05 providing invaluable support for this document. 6624 16. Change History 6626 [[RFC Editor: Please remove this section.]] 6628 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6629 dnrd-objects-mapping-00 6631 1. Added definition for child elements under the element. 6633 2. Added definition for child elements under the element. 6635 3. Added definition for child elements under the element. 6637 4. Rewrote the IDN Variants Handling section to use the variant 6638 states as described in ICANN's Study of Issues Related to the 6639 Management of IDN Variant TLDs. 6641 5. Renamed to in the . 6643 6. Renamed to in the element. 6645 7. Renamed to in the element. 6647 8. Added element under element. 6649 9. Fixed some typographical errors and omissions. 6651 16.2. Changes from 00 to 01 6653 1. Specify OPTIONAL elements in the draft. 6655 2. Added NNDN object to support list of reserved names and different 6656 IDN variants models. 6658 3. Removed subordinated host element from the domain object. 6660 4. Added eppParams object. 6662 5. Added variantGenerator element to the domain object. 6664 6. Added lgr to the IDN table object. 6666 16.3. Changes from 01 to 02 6668 1. Updates to the all objects based on feedback from the list. 6670 2. Start of XML and CSV drafts merge. 6672 3. Added header object. 6674 4. Added report object. 6676 5. Added notification object. 6678 6. Added Data Escrow Agent Extended Verification Process section. 6680 7. Added Notifications from Registries to Third Parties. 6682 8. Added Notifications from Data Escrow Agents to Third Parties. 6684 9. Added FULL, DIFF deposit examples using the XML model only. 6686 16.4. Changes from 02 to 03 6688 1. Remove authinfo from the XML Schema. 6690 2. Resend attribute is now an element 6692 3. Scope attribute added to policy object. 6694 16.5. Changes from 03 to 04 6696 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6697 arias-noguchi-dnrd-objects-mapping-02. 6699 2. Changed the cksum attribute of to use CRC32 and 6700 changed all of the sample cksum values to use CRC32, based on 6701 feedback from David Kipling. 6703 3. Changed the optional element to be an optional 6704 "sep" attribute value of the element with a default 6705 value of "," based on feedback from David Kipling. 6707 4. Added support for the optional "parent" attribute for the to the 6708 CSV fields to indicate a field as a reference to a parent 6709 object, based on feedback from David Kipling. 6711 5. Added support for the CSV model for the NNDN. 6713 6. Added support to delete hosts based on roid. 6715 7. Added mirrored state to NNDN 6717 8. Minor fixes to XML XSDs. 6719 9. The Report and Notification objects were moved to draft-lozano- 6720 icann-registry-interfaces 6722 10. The section Data escrow notifications was moved to draft-lozano- 6723 icann-registry-interfaces 6725 11. Removed references to the , , and 6726 from the "hostStatuses" and "hostAddresses" CSV 6727 files. 6729 12. Removed references to the , , and 6730 from the "contactStatuses" CSV file. 6732 13. Removed references to the , , and 6733 from the "domainContacts", "domainStatuses", 6734 and "domainNameServers" CSV files. 6736 14. Changed to . 6738 15. Replaced use of to new field 6739 in the "domain", "idnLanguage", and "NNDN" CSV files. 6741 16. Replaced use of with in the 6742 "host" element. 6744 17. Changed the foreign key of the hosts to use 6745 instead of and removed use of in 6746 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6747 files. 6749 18. Added use of the MUST keyword for CSV fields that are required 6750 to be supported in an EPP based system. 6752 19. Removed use of the field element for the 6753 "registrar" CSV file. 6755 20. Added definition of field element. 6757 16.6. Changes from 04 to 05 6759 1. Updated the examples of the full and differential deposits using 6760 the CSV and XML model. 6762 2. Made optional for the "domainTransfer" CSV file 6763 to match the XML definition. 6765 3. Made optional for the "domain" CSV file 6766 to match the XML definition. 6768 4. Made optional for the "domain" and "contact" CSV 6769 files to match the XML definition. 6771 5. Change from IDREF to idType. 6773 6. Minor editorial changes. 6775 16.7. Changes from 05 to 06 6777 1. Revised the differential and incremental deposits for the CSV 6778 format to use cascade update / replace and delete from the parent 6779 object to be consistent with the XML format. 6781 2. Revised the structure of the CSV format sections to utilize sub- 6782 sections instead of a list for the CSV file definitions. 6784 3. Added the "CSV Parent Child Relationship" section to describe the 6785 concept of parent child relationships across CSV file 6786 definitions. 6788 4. Added the "domainNameServersAddresses" CSV File Definition 6789 section to support the domain host attributes model of [RFC5731]. 6791 5. Made the required fields in the CSV format consistent with the 6792 XML format. The CSV fields updated to be required include: 6793 , , , 6794 , , , 6795 , , , 6796 , , , 6797 , , 6798 , , , 6799 , , 6800 , and . 6802 6. Revised the CSV examples to use a more realistic set of records. 6804 16.8. Changes from 06 to 07 6806 1. Created "repositoryTypeGroup" group element in the rdeHeader 6807 including the , and 6808 elements. 6810 2. Added the optional "rcdn" and "registrarId" attributes to the 6811 element 6813 16.9. Changes from 07 to 08 6815 1. The following registrar elements were made optional to support 6816 greater flexibility for the implementation of policies: status, 6817 postalInfo, email and crDate. 6819 2. The following domain name elements were made optional to support 6820 greater flexibility for the implementation of policies: crRr. 6822 16.10. Changes from 08 to 09 6824 1. Implementation Status section was added 6826 16.11. Changes from 09 to 10 6828 1. Editorial changes in section Section 5.1.2.1.6. 6830 2. Added MAY clause when the DS Data Interface is used in section 6831 Section 5.1.2.1.6. 6833 16.12. Changes from 10 to REGEXT 00 6835 1. Internet Draft (I-D) adopted by the REGEXT WG. 6837 16.13. Changes REGEXT 00 to REGEXT 01 6839 1. Added the element to the 6840 "repositoryTypeGroup" group element in the rdeHeader. 6842 2. Privacy consideration section was added 6844 3. Updates on section 8 6846 17. Example of a full deposit using the XML model 6848 Example of a full deposit using the XML model: 6850 6851 6867 2010-10-17T00:00:00Z 6868 6869 1.0 6870 urn:ietf:params:xml:ns:rdeHeader-1.0 6871 6872 urn:ietf:params:xml:ns:rdeContact-1.0 6873 6874 urn:ietf:params:xml:ns:rdeHost-1.0 6875 6876 urn:ietf:params:xml:ns:rdeDomain-1.0 6877 6878 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6879 6880 urn:ietf:params:xml:ns:rdeIDN-1.0 6881 6882 urn:ietf:params:xml:ns:rdeNNDN-1.0 6883 6884 urn:ietf:params:xml:ns:rdeEppParams-1.0 6885 6886 6888 6889 6890 6891 6892 test 6893 2 6895 6896 1 6898 6899 1 6901 6902 1 6904 6905 1 6907 6908 1 6910 6911 1 6913 6914 6916 6917 6918 example1.test 6919 Dexample1-TEST 6920 6921 jd1234 6922 sh8013 6923 sh8013 6924 6925 ns1.example.com 6926 ns1.example1.test 6927 6928 RegistrarX 6929 RegistrarX 6930 1999-04-03T22:00:00.0Z 6931 2015-04-03T22:00:00.0Z 6932 6934 6935 6936 example2.test 6937 Dexample2-TEST 6938 6939 6940 jd1234 6941 sh8013 6942 sh8013 6943 RegistrarX 6944 RegistrarX 6945 1999-04-03T22:00:00.0Z 6946 2015-04-03T22:00:00.0Z 6947 6949 6950 6951 ns1.example1.test 6952 Hns1_example_test-TEST 6953 6954 6955 192.0.2.2 6956 192.0.2.29 6957 1080:0:0:0:8:800:200C:417A 6958 6959 RegistrarX 6960 RegistrarX 6961 1999-05-08T12:10:00.0Z 6962 RegistrarX 6963 2009-10-03T09:34:00.0Z 6964 6966 6967 6968 sh8013 6969 Csh8013-TEST 6970 6971 6972 6973 John Doe 6974 Example Inc. 6975 6976 123 Example Dr. 6977 Suite 100 6978 Dulles 6979 VA 6980 20166-6503 6981 US 6982 6983 6984 +1.7035555555 6985 6986 +1.7035555556 6987 6988 jdoe@example.test 6989 6990 RegistrarX 6991 RegistrarX 6992 6993 2009-09-13T08:01:00.0Z 6994 6995 RegistrarX 6996 6997 2009-11-26T09:10:00.0Z 6998 6999 2009-12-03T09:05:00.0Z 7000 7001 7002 7003 7004 7005 7007 7008 7009 RegistrarX 7010 Registrar X 7011 123 7012 ok 7013 7014 7015 123 Example Dr. 7016 7017 Suite 100 7018 7019 Dulles 7020 VA 7021 20166-6503 7022 US 7023 7024 7025 +1.7035555555 7026 7027 +1.7035555556 7028 7029 jdoe@example.test 7030 7031 http://www.example.test 7032 7033 7034 whois.example.test 7035 7036 http://whois.example.test 7037 7038 7039 2005-04-23T11:49:00.0Z 7040 7041 2009-02-17T17:51:00.0Z 7042 7043 7045 7046 7047 7048 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 7049 7050 7051 http://registro.br/dominio/regras.html 7052 7053 7055 7056 7057 xn--exampl-gva.test 7058 pt-BR 7059 example1.test 7060 withheld 7061 2005-04-23T11:49:00.0Z 7062 7064 7065 7066 1.0 7067 en 7068 7069 urn:ietf:params:xml:ns:domain-1.0 7070 7071 7072 urn:ietf:params:xml:ns:contact-1.0 7073 7074 7075 urn:ietf:params:xml:ns:host-1.0 7076 7077 7078 urn:ietf:params:xml:ns:rgp-1.0 7079 7080 urn:ietf:params:xml:ns:secDNS-1.1 7081 7082 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 7094 7095 7096 7097 7099 7100 7101 7104 7105 7107 18. Example of differential deposit using the XML model 7109 Example of a differential deposit using the XML model: 7111 7112 7127 2010-10-17T00:00:00Z 7128 7129 1.0 7130 urn:ietf:params:xml:ns:rdeHeader-1.0 7131 7132 urn:ietf:params:xml:ns:rdeContact-1.0 7133 7134 urn:ietf:params:xml:ns:rdeHost-1.0 7135 7136 urn:ietf:params:xml:ns:rdeDomain-1.0 7137 7138 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7139 7140 urn:ietf:params:xml:ns:rdeIDN-1.0 7141 7142 urn:ietf:params:xml:ns:rdeNNDN-1.0 7143 7144 urn:ietf:params:xml:ns:rdeEppParams-1.0 7145 7146 7147 7148 7149 7150 example2.test 7151 7152 7154 7155 7156 7157 7158 test 7159 1 7161 7162 1 7164 7165 1 7167 7168 1 7170 7171 1 7173 7174 1 7176 7177 1 7179 7180 7181 7182 7184 19. Example of a full deposit using the CSV model 7186 Example of a full deposit using the CSV model: 7188 7189 7203 2010-10-18T00:00:00Z 7204 7205 1.0 7206 urn:ietf:params:xml:ns:csvDomain-1.0 7207 urn:ietf:params:xml:ns:csvHost-1.0 7208 urn:ietf:params:xml:ns:csvContact-1.0 7209 urn:ietf:params:xml:ns:csvRegistrar-1.0 7210 urn:ietf:params:xml:ns:csvIDN-1.0 7211 urn:ietf:params:xml:ns:csvNNDN-1.0 7212 urn:ietf:params:xml:ns:rdeEppParams-1.0 7213 7214 7215 7216 test 7217 7218 4 7219 7220 7221 6 7222 7223 7224 9 7225 7226 7227 3 7228 7229 7230 2 7231 7232 7233 2 7234 7235 7236 1 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7259 domain-YYYYMMDD.csv 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7272 domainContacts-YYYYMMDD.csv 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7287 domainStatuses-YYYYMMDD.csv 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7299 domainNameServers-name-YYYYMMDD.csv 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7311 domainNameServers-roid-YYYYMMDD.csv 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7327 dnssec-ds-YYYYMMDD.csv 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7340 7341 7342 7344 dnssec-key-YYYYMMDD.csv 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7363 domainTransfer-YYYYMMDD.csv 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7385 host-YYYYMMDD.csv 7386 7387 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7400 hostStatuses-YYYYMMDD.csv 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7413 hostAddresses-YYYYMMDD.csv 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7439 contact-YYYYMMDD.csv 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7453 contactStatuses-YYYYMMDD.csv 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7474 contactPostal-YYYYMMDD.csv 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7492 contactTransfer-YYYYMMDD.csv 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7513 contactDisclose-YYYYMMDD.csv 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7545 registrar-YYYYMMDD.csv 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7559 idnLanguage-YYYYMMDD.csv 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7577 NNDN-YYYYMMDD.csv 7578 7579 7580 7582 7583 7584 1.0 7585 en 7586 urn:ietf:params:xml:ns:domain-1.0 7587 7588 urn:ietf:params:xml:ns:host-1.0 7589 7590 urn:ietf:params:xml:ns:contact-1.0 7591 7592 7593 urn:ietf:params:xml:ns:secDNS-1.1 7594 7595 urn:ietf:params:xml:ns:rgp-1.0 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7622 20. Example of differential deposit using the CSV model 7624 Example of a differential deposit using the CSV model: 7626 7627 7641 2010-10-18T00:00:00Z 7642 7643 1.0 7644 urn:ietf:params:xml:ns:csvDomain-1.0 7645 urn:ietf:params:xml:ns:csvHost-1.0 7646 urn:ietf:params:xml:ns:csvContact-1.0 7647 urn:ietf:params:xml:ns:csvRegistrar-1.0 7648 urn:ietf:params:xml:ns:csvIDN-1.0 7649 7650 7651 7652 7653 7654 7655 7656 7657 7659 domain-delete-YYYYMMDD.csv 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7672 host-delete-YYYYMMDD.csv 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7685 contact-delete-YYYYMMDD.csv 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7698 registrar-delete-YYYYMMDD.csv 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7711 idnLanguage-delete-YYYYMMDD.csv 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7724 NNDN-delete-YYYYMMDD.csv 7725 7727 7728 7729 7730 7731 7732 7733 test 7734 7735 2 7736 7737 7738 2 7739 7740 7741 3 7742 7743 7744 1 7745 7746 7747 1 7748 7749 7750 1 7751 7752 7753 1 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7776 domain-YYYYMMDD.csv 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7789 domainContacts-YYYYMMDD.csv 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7804 domainStatuses-YYYYMMDD.csv 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7816 domainNameServers-name-YYYYMMDD.csv 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7828 domainNameServers-roid-YYYYMMDD.csv 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7844 dnssec-ds-YYYYMMDD.csv 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7860 dnssec-key-YYYYMMDD.csv 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7879 domainTransfer-YYYYMMDD.csv 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7901 host-YYYYMMDD.csv 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7915 hostStatuses-YYYYMMDD.csv 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7928 hostAddresses-YYYYMMDD.csv 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7954 contact-YYYYMMDD.csv 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7968 contactStatuses-YYYYMMDD.csv 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7989 contactPostal-YYYYMMDD.csv 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8007 contactTransfer-YYYYMMDD.csv 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8028 contactDisclose-YYYYMMDD.csv 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8060 registrar-YYYYMMDD.csv 8061 8062 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8075 idnLanguage-YYYYMMDD.csv 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8093 NNDN-YYYYMMDD.csv 8094 8095 8096 8097 8098 8099 1.0 8100 en 8101 urn:ietf:params:xml:ns:domain-1.0 8102 8103 urn:ietf:params:xml:ns:host-1.0 8104 8105 urn:ietf:params:xml:ns:contact-1.0 8106 8107 8108 urn:ietf:params:xml:ns:secDNS-1.1 8109 8110 urn:ietf:params:xml:ns:rgp-1.0 8111 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8138 21. References 8140 21.1. Normative References 8142 [ISO-3166-1] 8143 3166, I. S., "Codes for the representation of names of 8144 countries and their subdivisions -- Part 1: Country 8145 codes", ISO Standard 3166, November 2006. 8147 [ITU-E164] 8148 International Telecommunication Union, "The international 8149 public telecommunication numbering plan", ITU-T 8150 Recommendation E.164, February 2005. 8152 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8153 Requirement Levels", BCP 14, RFC 2119, 8154 DOI 10.17487/RFC2119, March 1997, 8155 . 8157 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8158 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8159 . 8161 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8162 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8163 DOI 10.17487/RFC3915, September 2004, 8164 . 8166 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8167 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8168 . 8170 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8171 Domain Name Mapping", STD 69, RFC 5731, 8172 DOI 10.17487/RFC5731, August 2009, 8173 . 8175 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8176 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8177 August 2009, . 8179 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8180 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8181 August 2009, . 8183 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8184 Security Extensions Mapping for the Extensible 8185 Provisioning Protocol (EPP)", RFC 5910, 8186 DOI 10.17487/RFC5910, May 2010, 8187 . 8189 21.2. Informative References 8191 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8192 DOI 10.17487/RFC0791, September 1981, 8193 . 8195 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8196 DOI 10.17487/RFC3688, January 2004, 8197 . 8199 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8200 DOI 10.17487/RFC3912, September 2004, 8201 . 8203 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8204 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8205 2006, . 8207 [RFC5891] Klensin, J., "Internationalized Domain Names in 8208 Applications (IDNA): Protocol", RFC 5891, 8209 DOI 10.17487/RFC5891, August 2010, 8210 . 8212 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 8213 Code: The Implementation Status Section", BCP 205, 8214 RFC 7942, DOI 10.17487/RFC7942, July 2016, 8215 . 8217 [variantTLDsReport] 8218 Internet Corporation for Assigned Names and Numbers 8219 (ICANN), "A Study of Issues Related to the Management of 8220 IDN Variant TLDs", February 2012, 8221 . 8224 21.3. URIs 8226 [1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data- 8227 escrow-05.txt 8229 Authors' Addresses 8231 Gustavo Lozano 8232 Internet Corporation for Assigned Names and Numbers 8233 12025 Waterfront Drive, Suite 300 8234 Los Angeles 90292 8235 United States of America 8237 Phone: +1.310.823.9358 8238 Email: gustavo.lozano@icann.org 8240 James Gould 8241 VeriSign, Inc. 8242 12061 Bluemont Way 8243 Reston 20190 8244 United States of America 8246 Email: jgould@verisign.com 8247 Chethan Thippeswamy 8248 VeriSign, Inc. 8249 12061 Bluemont Way 8250 Reston 20190 8251 United States of America 8253 Email: cthippeswamy@verisign.com