idnits 2.17.1 draft-arias-noguchi-dnrd-objects-mapping-06.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 (June 09, 2017) is 2505 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 8046 -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track J. Gould 5 Expires: December 11, 2017 C. Thippeswamy 6 VeriSign 7 June 09, 2017 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-arias-noguchi-dnrd-objects-mapping-06 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 http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on December 11, 2017. 35 Copyright Notice 37 Copyright (c) 2017 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 (http://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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5 56 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 5 57 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 5 58 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . . 81 75 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 76 8. Data escrow agent extended verification process . . . . . . . 82 77 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 83 78 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 83 79 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 93 80 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 96 81 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 100 82 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 103 83 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 106 84 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 109 85 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 115 86 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 119 87 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 123 88 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 125 89 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 127 90 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 129 91 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 131 92 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 134 93 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 135 94 10. Internationalization Considerations . . . . . . . . . . . . . 138 95 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 138 96 12. Security Considerations . . . . . . . . . . . . . . . . . . . 143 97 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 144 98 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 144 99 14.1. Changes from draft-arias-noguchi-registry-data-escrow-02 100 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 144 101 14.2. Changes from version 00 to 01 . . . . . . . . . . . . . 145 102 14.3. Changes from version 01 to 02 . . . . . . . . . . . . . 145 103 14.4. Changes from version 02 to 03 . . . . . . . . . . . . . 145 104 14.5. Changes from version 03 to 04 . . . . . . . . . . . . . 145 105 14.6. Changes from version 04 to 05 . . . . . . . . . . . . . 147 106 14.7. Changes from version 05 to 06 . . . . . . . . . . . . . 147 107 15. Example of a full deposit using the XML model . . . . . . . . 148 108 16. Example of differential deposit using the XML model . . . . . 153 109 17. Example of a full deposit using the CSV model . . . . . . . . 155 110 18. Example of differential deposit using the CSV model . . . . . 164 111 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 175 112 19.1. Normative References . . . . . . . . . . . . . . . . . . 175 113 19.2. Informative References . . . . . . . . . . . . . . . . . 176 114 19.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 176 115 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 176 117 1. Introduction 119 This document defines the data escrow structure of the standard set 120 of objects for a Domain Name Registry which include: 122 o Domain: Internet domain names that are typically provisioned in a 123 Domain Name Registry using the EPP domain name mapping [RFC5731]. 124 The attributes defined in the EPP domain name mapping [RFC5731] 125 are fully supported by this document. 127 o Host: Internet host names that are typically provisioned in a 128 Domain Name Registry using the EPP host mapping [RFC5732]. The 129 attributes defined in the EPP host mapping [RFC5732] are fully 130 supported by this document. 132 o Contact: Individual or organization social information provisioned 133 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 134 The attributes defined in the EPP contact mapping [RFC5733] are 135 fully supported by this document. 137 o Registrar: The organization that sponsors objects like domains, 138 hosts, and contacts in a Domain Name Registry. 140 o NNDN (NNDN's not domain name): A lightweight domain-like object 141 that is not linked to a Registrar. 143 This document defines the following pseudo-objects: 145 o IDN Table Reference: Internationalized Domain Names (IDN) included 146 in the Domain Object Data Escrow include references to the IDN 147 Table and Policy used in IDN registration. 149 o EPP parameters: Definition of the specific EPP parameters 150 supported by the Registry Operator. 152 o Header: Used to specify counters of objects in the database at a 153 certain point in time (watermark). 155 o Policy: Used to specify OPTIONAL elements from this specification 156 that are REQUIRED based on the business model of the registry. 158 2. Models 160 This document defines two different models that can be used to 161 deposit data escrow objects: 163 o XML: The XML model includes all the deposit information (meta-data 164 and data) in an XML document. The definition of the XML format is 165 fully defined in the XML schemas. As a convention, the objects 166 represented using the XML model are referenced using RDE and an 167 XML namespace that is prefixed with "rde". For example, the 168 Domain Name object represented using the XML model can be referred 169 to as the RDE Domain Name with the XML namespace including 170 rdeDomain (urn:ietf:params:xml:ns:rdeDomain-1.0). 172 o CSV: The CSV model uses XML to define the data escrow format of 173 the data contained in referenced Comma-Separated Values (CSV) 174 files. As a convention, the objects represented using the CSV 175 model is referenced using CSV and an XML namespace that is 176 prefixed with "csv". For example, the Domain Name object 177 represented using the CSV model can be referred to as the CSV 178 Domain Name with the XML namespace including csvDomain 179 (urn:ietf:params:xml:ns:csvDomain-1.0). 181 The data escrow deposit MAY contain a mix of both models but an 182 object MUST be escrowed only in one model. 184 3. Terminology 186 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 187 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 188 document are to be interpreted as described in BCP 14, [RFC2119]. 190 REGISTRY. In the context of this draft the definition will be 191 overloaded (from the definition in the base protocol) to indicate an 192 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 193 NAME. 195 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 196 or any other domain name at any level in the DNS tree for which a 197 Registry (either directly or through and affiliate company) provides 198 Registry Services for other organizations or individuals. For 199 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 201 REGISTRY SERVICES. Services offered by the Registry critical to the 202 following tasks: the provisioning of domain names on receipt of 203 requests and data from registrars; responding to registrar queries 204 for status information relating to the DNS servers for the RCDN; 205 dissemination of RCDN zone files; operation of the Registry DNS 206 servers; and responding to queries for contact and other information 207 concerning DNS registrations in the RCDN. Any other products or 208 services that only a Registry is capable of providing, by reason of 209 its designation as the Registry. Typical examples of Registry 210 Services are: DNS resolution for the RCDN, WHOIS and EPP. 212 ALLOCATED. A status of some label with respect to a zone, whereby 213 the label is associated administratively to some entity that has 214 requested the label. This term (and its cognates "allocation" and 215 "to allocate") may represents the first step on the way to delegation 216 in the DNS. 218 4. General Conventions 220 4.1. Date and Time 222 Numerous fields indicate "dates", such as the creation and expiry 223 dates for domain names. These fields SHALL contain timestamps 224 indicating the date and time in UTC as specified in [RFC3339], with 225 no offset from the zero meridian. 227 4.2. Country names 229 Country identifiers SHALL be represented using two character 230 identifiers as specified in [ISO-3166-1]. 232 4.3. Telephone numbers 234 Telephone numbers (both voice and facsimile) SHALL be formatted based 235 on structures defined in [ITU-E164]. Telephone numbers described in 236 this specification are character strings that MUST begin with a plus 237 sign ("+", ASCII value 0x002B), followed by a country code defined in 238 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 239 a sequence of digits representing the telephone number. 241 4.4. Checksum 243 Checksum of the CSV data escrow files MUST use CRC32, that is the 244 algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of 245 ITU-T recommendation V.42. 247 4.5. IP addresses 249 IP addresses syntax MUST conform to the text representation of either 250 of, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 251 Addressing Architecture [RFC4291], for IPv6 addresses. 253 4.6. CSV Parent Child Relationship 255 The CSV model represents a relational model, where the CSV files 256 represent relational tables, the fields of the CSV files represent 257 columns of the tables, and each line of the CSV file represents a 258 record. As in a relational model, the CSV files can have 259 relationships utilizing primary keys in the parent CSV file 260 definitions and foreign keys in the child CSV file definitions for a 261 1-to-many relationship. The primary keys are not explicitly defined, 262 but the foreign keys are using the boolean "parent" field attribute 263 in the child CSV file. The relationships between the CSV files are 264 used to support a cascade replace or cascade delete of records 265 starting from the parent record in differential and incremental 266 deposits. 268 The following is an example of the CSV file definitions for a Sample 269 object consisting of a parent "sample" CSV File Definition and a 270 child "sampleStatuses" CSV File Definition. The primary key for the 271 Sample object is the field that is used as the 272 foreign key in the "sampleStatuses" CSV File Definition by specifying 273 the "parent=true" attribute. If a Sample record is updated or 274 deleted in a differential or incremental deposit, it should cascade 275 replace the data using the records included in the child 276 "sampleStatuses" CSV File Definition or cascade delete the existing 277 records in the child "sampleStatuses" CSV File Definition, 278 respectively. 280 281 ... 282 283 284 285 286 287 288 289 290 291 292 293 294 295 297 sample-YYYYMMDD.csv 298 299 300 301 302 303 304 305 306 307 308 309 311 sampleStatuses-YYYYMMDD.csv 312 313 314 315 ... 316 318 4.7. CSV elements 320 4.7.1. element 322 To support a CSV model with the Registry Data Escrow Specification 323 [1], an element is defined for each object that substitutes for the 324 element and for the element, that contains 325 one or more elements. For example, the Domain Name 326 Object (Section 5.1) defines the element, that 327 substitutes for the element, and the 328 element, that substitutes for the 329 element. Both the element and the 330 elements contain one or more 331 elements. The element has the following child elements: 333 Ordered list of CSV fields used in the CSV files. 334 There is one or more child elements that substitute for the 335 abstract element. Each element defines the format 336 of the CSV field contained in the CSV files. The 337 elements support the "type" attribute that defines the XML simple 338 data type of the field element. The elements 339 support the "isRequired" attribute, with a default value of 340 "false", when set to "true" indicates that the field must be non- 341 empty in the CSV files and when set to "false" indicates that the 342 field MAY be empty in the CSV files. The "isRequired" attribute 343 MAY be specifically set for the field elements within the XML 344 schema and MAY be overridden when specifying the fields under the 345 element. The element supports an 346 OPTIONAL "parent" attribute that identifies the field as a 347 reference to a parent object, as defined in CSV Parent Child 348 Relationship (Section 4.6). For example, the field SHOULD set the 350 "parent" attribute to "true" to identify it as the parent domain 351 name of the domain status. 353 A list of one or more CSV files using the 354 child element. The child element 355 defines a reference to the CSV file name and has the following 356 optional attributes: 358 compression If the CSV file is compressed, the "compression" 359 attribute defines the compression format like "gzip" or "zip". 361 encoding Defines the encoding of the CSV file with the default 362 encoding of "UTF-8". 364 cksum Defines the checksum of the CSV file using CRC32, as 365 defined in Section 4.4. This attribute is used to validate 366 that the full CSV file exists and has not been tampered with. 368 The elements requires a "name" attribute that defines 369 the purpose of the CSV file with values like "domain", "host", 370 "contact". The supported "name" attribute values are defined for 371 each object type. The OPTIONAL "sep" attribute defines the CSV 372 separator character with the default separator character of ",". 374 The following is an example of the 375 element for domain name records where the is set 376 as required with isRequired="true". 378 379 ... 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 399 domain-YYYYMMDD.csv 400 401 402 403 ... 404 406 The following is example of the "domain-YYYYMMDD.csv" file with one 407 record matching the definition. 409 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 410 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 411 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 412 The following is an example of the 413 element for domain name records. 415 416 ... 417 418 419 420 421 422 424 domain-delete-YYYYMMDD.csv 425 426 427 428 ... 429 431 The following is example of the "domain-delete-YYYYMMDD.csv" file 432 with three records that matches the single field. 434 domain1.test 435 domain2.test 436 domainN.test 438 4.7.2. CSV common field elements 440 The element defined in the element 441 (Section 4.7.1) section has child elements that substitute for the 442 abstract element. By convention 443 elements include an 'f' prefix to identify them as field definition 444 elements. There are a set of common field elements that are used 445 across multiple data escrow objects. The common field elements are 446 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 447 using the "rdeCsv" sample namespace prefix. The CSV common field 448 elements include: 450 UTF-8 encoded name field with 451 type="eppcom:labelType". 453 Repository Object IDentifier (ROID) field with 454 type="eppcom:roidType" and isRequired="true". 456 Registrant contact identifier with 457 type="eppcom:clIDType". 459 The object status description, which is 460 free form text describing the rationale for the status, with 461 type="normalizedString". 463 Identifier of client (registrar) that sponsors the 464 object with type="eppcom:clIDType" and isRequired="true". 466 Identifier of the registrar, defined in Section 5.4, 467 of the client that created the object with type="eppcom:clIDType" 468 and isRequired="true". 470 Identifier of client that created the object with 471 type="eppcom:clIDType". 473 Identifier of the registrar, defined in Section 5.4, 474 of the client that updated the object with type="eppcom:clIDType". 476 Identifier of client that updated the object with 477 type="eppcom:clIDType". 479 Identifier of the registrar, defined in Section 5.4, 480 of the client that requested the transfer with 481 type="eppcom:clIDType" and isRequired="true". 483 Identifier of client that requested the transfer with 484 type="eppcom:clIDType". 486 Identifier of the registrar, defined in Section 5.4, 487 of the client that should take or took action with 488 type="eppcom:clIDType" and isRequired="true". 490 Identifier of client that should take or took action 491 for transfer with type="eppcom:clIDType". 493 Created date of object with type="dateTime" and 494 isRequired="true". 496 Updated date of object with type="dateTime". 498 Expiration date of object with type="dateTime". 500 Date that transfer was requested with 501 type="dateTime" and isRequired="true". 503 Date that transfer action should be taken or has 504 been taken with type="dateTime" and isRequired="true". 506 Date of last transfer with type="dateTime". 508 State of the most recent transfer request with 509 type="eppcom:trStatusType" and isRequired="true". 511 General token field with type="token". 513 General language field with type="language". 515 IDN Table Identifier used for IDN domain names 516 with type="token". 518 General positive integer field with 519 type="positiveInteger". 521 Contains the URL of an object like a registrar object 522 with type="anyURI". 524 Custom field with name attribute that defines the 525 custom field name" with type="token". 527 4.8. Internationalized and Localized Elements 529 Some elements MAY be provided in either internationalized form 530 ("int") or provided in localized form ("loc"). Those elements use a 531 field value or "isLoc" attribute to specify the form used. If an 532 "isLoc" attribute is used, a value of "true" indicates the use of the 533 localized form and a value of "false" indicates the use of the 534 internationalized form. This MAY override the form specified for a 535 parent element. A value of "int" is used to indicate the 536 internationalized form and a value of "loc" is used to indicate the 537 localized form. When the internalized form ("int") is provided, the 538 field value MUST be represented in a subset of UTF-8 that can be 539 represented in the 7-bit US-ASCII character set. When the localized 540 form ("loc") is provided, the field value MAY be represented in 541 unrestricted UTF-8. 543 The field elements below of the "registrar" 544 element specify the internationalized form with the 545 isLoc="false" attribute. 547 ... 548 549 ... 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 581 registrar-YYYYMMDD.csv 582 583 584 585 ... 586 587 ... 589 The following is an example of using the 590 field value to define the internationalized or localized form of the 591 remainder of the "contactPostal" field values. 593 ... 594 595 ... 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 613 contactPostal-YYYYMMDD.csv 614 615 616 617 ... 618 619 ... 621 5. Object Description 623 This section describes the base objects supported by this 624 specification: 626 5.1. Domain Name Object 628 The domain name object is based on the EPP domain name mapping 629 specified in [RFC5731]. The domain name object supports both the XML 630 Model and the CSV Model, defined in the Models (Section 2) section. 631 The elements used for both models are defined in the following 632 sections. 634 5.1.1. XML Model 636 There are two elements used in the data escrow of the domain name 637 objects for the XML model including the , under the 638 element, and the element, under the 639 element. 641 5.1.1.1. object 643 The domain element is based on the EPP domain response for an 644 authorized client (see Section 3.1.2. of [RFC5731]) with additional 645 data from an EPP Query Response, see Section 3.1.3. of 646 [RFC5731], RGP status from [RFC3915], and data from the EPP 647 command, see Section 5.2.1. of [RFC5910]. 649 A element substitutes for the abstract 650 element to define a concrete definition of a domain. The 651 element can be replaced by other domain definitions 652 using the XML schema substitution groups feature. 654 The element contains the following child elements: 656 o A element that contains the fully qualified name of the 657 domain name object. If the domain name is an IDN, the ASCII 658 Compatible Encoding (ACE) MUST be used. 660 o A element that contains the repository object identifier 661 assigned to the domain name object when it was created. 663 o An OPTIONAL element that contains the fully qualified name 664 of the domain name in Unicode character set. It MUST be provided 665 if available. 667 o An OPTIONAL element that references the IDN 668 Table used for the IDN. This corresponds to the "id" attribute of 669 the element. This element MUST be present if the 670 domain name is an IDN. 672 o An OPTIONAL element is used to indicate that the 673 domain name is an IDN variant. This element contains the domain 674 name used to generate the IDN variant. 676 o One or more elements that contain the current status 677 descriptors associated with the domain name. 679 o Zero or more OPTIONAL element to represent 680 "pendingDelete" sub-statuses, including "redemptionPeriod", 681 "pendingRestore", and "pendingDelete", that a domain name can be 682 in as a result of grace period processing as specified in 683 [RFC3915]. 685 o An OPTIONAL element that contain the identifier for 686 the human or organizational social information object associated 687 as the holder of the domain name object. 689 o Zero or more OPTIONAL elements that contain identifiers 690 for the human or organizational social information objects 691 associated with the domain name object. 693 o An OPTIONAL element that contains the fully qualified names 694 of the delegated host objects or host attributes (name servers) 695 associated with the domain name object. See Section 1.1 of 696 [RFC5731] for a description of the elements used to specify host 697 objects or host attributes. 699 o A element that contains the identifier of the sponsoring 700 registrar. 702 o A element that contains the identifier of the registrar 703 that created the domain name object. An OPTIONAL client attribute 704 is used to specify the client that performed the operation. 706 o An OPTIONAL element that contains the date and time of 707 the domain name object creation. This element MUST be present if 708 the domain name has been allocated. 710 o An OPTIONAL element that contains the date and time 711 identifying the end (expiration) of the domain name object's 712 registration period. This element MUST be present if the domain 713 name has been allocated. 715 o An OPTIONAL element that contains the identifier of the 716 registrar that last updated the domain name object. This element 717 MUST NOT be present if the domain has never been modified. An 718 OPTIONAL client attribute is used to specify the client that 719 performed the operation. 721 o An OPTIONAL element that contains the date and time of 722 the most recent domain-name-object modification. This element 723 MUST NOT be present if the domain name object has never been 724 modified. 726 o An OPTIONAL element that contains the public key 727 information associated with Domain Name System security (DNSSEC) 728 extensions for the domain name as specified in [RFC5910]. 730 o An OPTIONAL element that contains the date and time of 731 the most recent domain object successful transfer. This element 732 MUST NOT be present if the domain name object has never been 733 transferred. 735 o An OPTIONAL element that contains the following child 736 elements related to the last transfer request of the domain name 737 object. This element MUST NOT be present if a transfer request 738 for the domain name has never been created. 740 * A element that contains the state of the most recent 741 transfer request. 743 * A element that contains the identifier of the registrar 744 that requested the domain name object transfer. An OPTIONAL 745 client attribute is used to specify the client that performed 746 the operation. 748 * A element that contains the date and time that the 749 transfer was requested. 751 * An element that contains the identifier of the registrar 752 that SHOULD act upon a PENDING transfer request. For all other 753 status types, the value identifies the registrar that took the 754 indicated action. An OPTIONAL client attribute is used to 755 specify the client that performed the operation. 757 * An element that contains the date and time of a 758 required or completed response. For a PENDING request, the 759 value identifies the date and time by which a response is 760 required before an automated response action will be taken by 761 the registry. For all other status types, the value identifies 762 the date and time when the request was completed. 764 * An OPTIONAL element that contains the end of the 765 domain name object's validity period (expiry date) if the 766 transfer caused or causes a change in the validity period. 768 Example of a domain object: 770 ... 771 772 example1.test 773 Dexample1-TEST 774 775 jd1234 776 sh8013 777 sh8013 778 779 ns1.example.com 780 ns1.example1.test 781 782 RegistrarX 783 RegistrarX 784 1999-04-03T22:00:00.0Z 785 2015-04-03T22:00:00.0Z 786 787 ... 789 5.1.1.2. object 791 The element contains the fully qualified domain 792 name that was deleted and purged. 794 Example of object: 796 ... 797 798 ... 799 800 foo.test 801 bar.test 802 803 ... 804 805 ... 807 5.1.2. CSV Model 809 For the CSV Model of the domain name object, the 810 child element of the element is used to hold the new 811 or updated domain name objects for the deposit. The 812 child element of the element is 813 used to hold the deleted or purged domain name objects for the 814 deposit. Both the and 815 elements contain one or more elements with a set of 816 named CSV file definitions using the "name" attribute. 818 Differential and incremental deposits are based on changes to the 819 domain name objects. The updated domain name object data under the 820 element is a cascade replace down all of the 821 domain name CSV files starting with the parent "domain" CSV File 822 Definition (Section 5.1.2.1.1). The child CSV file definitions 823 include a field. All the child CSV 824 file definition data for the domain name objects in the parent 825 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 826 deleted and then set using the data in the child CSV files. The 827 deleted domain name object data under the element 828 is a cascade delete starting from the "domain" Deletes CSV File 829 Definition (Section 5.1.2.2.1). 831 5.1.2.1. 833 The is used to hold the new or updated domain 834 name object information for the deposit. The is 835 split into separate CSV file definitions using named 836 elements with the "name" attribute. The following sections include 837 the supported domain name CSV file definitions: 839 5.1.2.1.1. "domain" CSV File Definition 841 The "domain" CSV File Definition defines the fields and CSV file 842 references used for the parent domain name object records. All the 843 other domain name CSV file definitions are child CSV files based on 844 the inclusion of the field. 846 The following "csvDomain" field elements MUST be used in the "domain" 847 element: 849 Domain name field with type="eppcom:labelType" and 850 isRequired="true". 852 The following "csvDomain" field elements MAY be used in the "domain" 853 element: 855 Fully qualified name of the original IDN 856 domain name object related to the variant domain name object with 857 type="eppcom:labelType". 859 The following "rdeCsv" fields, defined in section CSV common field 860 elements (Section 4.7.2), MUST be used in the "domain" 861 element: 863 Registry Object IDentifier (ROID) for the domain name 864 object with isRequired="true". 866 Identifier of client that sponsors the domain name 867 object with isRequired="true". 869 Identifier of the registrar, defined in Section 5.4, 870 of the client that created the object with isRequired="true". 872 Created date and time of the domain name object 873 with isRequired="true". 875 Identifier of the registrar, defined in Section 5.4, 876 of the client that updated the object. 878 Date and time of the last update to the domain name 879 object. 881 Expiration date and time for the domain name 882 object. The attribute isRequired MUST equal "true". 884 The following "rdeCsv" fields, defined in section CSV common field 885 elements (Section 4.7.2), MAY be used in the "domain" 886 element: 888 UTF8 encoded domain name for the 889 field element. 891 IDN Table Identifier used for the IDN domain 892 name object that MUST match a field element 893 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 895 Registrant contact identifier for the domain 896 name object. 898 Identifier of client that created the domain name 899 object. 901 Identifier of the client that last updated the domain 902 name object. 904 Date and time of the last transfer for the domain 905 name object. 907 Example of a "domain" element. 909 ... 910 911 ... 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 931 domain-YYYYMMDD.csv 932 933 934 935 ... 936 937 ... 939 Example of the corresponding domain-YYYYMMDD.csv file. The file 940 contains four records (two active ASCII domains, original IDN with 941 LANG-1 language rules, and variant IDN with LANG-1 language rules). 943 domain1.test,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 944 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 945 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 946 domain2.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 947 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 948 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 949 xn--abc123.test,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 950 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 951 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 952 xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--abc123.test, 953 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 954 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 956 5.1.2.1.2. "domainContacts" CSV File Definition 958 The "domainContacts" CSV File Definition defines the fields and CSV 959 file references used for the domain name object link records to 960 contact objects, as described in Contact Object (Section 5.3). 962 The following "csvDomain" field elements MUST be used in the 963 "domainContacts" element: 965 The contact type for the contact object 966 link with type="domain:contactAttrType" and isRequired="true". 967 The supported contact type values include "admin" for the 968 administration contact, "billing" for the billing contact, and 969 "tech" for the technical contact. 971 The following "csvDomain" field elements, defined for the "domain" 972 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 973 "domainContacts" element: 975 The name of the domain object that is linked to 976 the contact object with isRequired="true". 978 The following "csvContact" fields, defined for the "contact" CSV File 979 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 980 element: 982 The server-unique contact identifier with 983 isRequired="true". 985 Example of a "domainContacts" 986 element. 988 ... 989 990 ... 991 992 993 994 995 996 997 998 1000 domainContacts-YYYYMMDD.csv 1001 1002 1003 1004 ... 1005 1006 ... 1008 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1009 file contains an admin, tech, and billing contact for the four domain 1010 names domain1.test, domain2.test, xn--abc123.test and xn-- 1011 abc321.test. 1013 domain1.test,domain1admin,admin 1014 domain1.test,domain1tech,tech 1015 domain1.test,domain1billing,billing 1016 domain2.test,domain2admin,admin 1017 domain2.test,domain2tech,tech 1018 domain2.test,domain2billing,billing 1019 xn--abc123.test,xnabc123admin,admin 1020 xn--abc123.test,xnabc123tech,tech 1021 xn--abc123.test,xnabc123billing,billing 1022 xn--abc321.test,xnabc123admin,admin 1023 xn--abc321.test,xnabc123tech,tech 1024 xn--abc321.test,xnabc123billing,billing 1026 5.1.2.1.3. "domainStatuses" CSV File Definition 1028 The "domainStatuses" CSV File Definition defines the fields and CSV 1029 file references used for the domain name object statuses. 1031 The following "csvDomain" field elements MUST be used in the 1032 "domainStatuses" element: 1034 The status of the domain name with 1035 type="domain:statusValueType" and isRequired="true". 1037 The Registry Grace Period (RGP) status, as a 1038 sub-status of the "pendingDelete" status 1039 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1041 The following "csvDomain" fields, defined for the "domain" CSV File 1042 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1043 element: 1045 Domain name of status with isRequired="true". 1047 The following "rdeCsv" fields, defined in section CSV common field 1048 elements (Section 4.7.2), MAY be used in the "domainStatuses" 1049 element: 1051 Domain object status description which 1052 is free form text describing the rationale for the status. 1054 Language of the field. 1056 Example of a "domainStatuses" 1057 element. 1059 ... 1060 1061 ... 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1073 domainStatuses-YYYYMMDD.csv 1074 1075 1076 1077 ... 1078 1079 ... 1081 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1082 file contains the statuses for the four domain names domain1.test, 1083 domain2.test, xn--abc123.test and xn--abc321.test. 1085 domain1.test,clientUpdateProhibited,"Disallow update", 1086 en, 1087 domain1.test,clientDeleteProhibited,"Disallow delete", 1088 en, 1089 domain2.test,ok,,, 1090 xn--abc123.test,ok,,, 1091 xn--abc321.test,ok,,, 1093 5.1.2.1.4. "domainNameServers" CSV File Definition 1095 The "domainNameServers" CSV File Definition defines the fields and 1096 CSV file references used for the domain name delegated hosts (name 1097 servers). The "domainNameServers" CSV files define the relationship 1098 between a domain name object and a delegated host. The 1099 "domainNameServers" CSV File is used to support the 1100 model, defined in [RFC5731]. 1102 The following "csvDomain" fields, defined for the "domain" CSV File 1103 Definition (Section 5.1.2.1.1), MUST be used in the 1104 "domainNameServers" element: 1106 Domain name using the delegated host with host 1107 and isRequired="true". 1109 The following "rdeCsv" fields, defined in section CSV common field 1110 elements (Section 4.7.2), MUST be used in the "domainNameServers" 1111 element: 1113 Registry Object IDentifier (ROID) used to uniquely 1114 reference a delegated host record with isRequired="true". 1116 Example of a "domainNameServers" 1117 element. 1119 ... 1120 1121 ... 1122 1123 1124 1125 1126 1127 1128 1130 domainNameServers-YYYYMMDD.csv 1131 1132 1133 1134 ... 1135 1136 ... 1138 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1139 The file contains the delegated hosts (name servers) for the four 1140 domain names domain1.test, domain2.test, xn--abc123.test and xn-- 1141 abc321.test referenced via the field element. 1143 domain1.test,Hns1_domain1_test-TEST 1144 domain1.test,Hns2_domain1_test-TEST 1145 domain2.test,Hns1_domain2_test-TEST 1146 domain2.test,Hns2_domain2_test-TEST 1147 xn--abc123.test,Hns1_example_test-TEST 1148 xn--abc123.test,Hns2_example_test-TEST 1149 xn--abc321.test,Hns1_example_test-TEST 1150 xn--abc321.test,Hns2_example_test-TEST 1152 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1154 The "domainNameServersAddresses" CSV File Definition defines the 1155 fields and CSV file references used for supporting the host as domain 1156 attributes model. 1158 The following "csvDomain" fields, defined for the "domain" CSV File 1159 Definition (Section 5.1.2.1.1), MUST be used in the 1160 "domainNameServersAddresses" element: 1162 Domain name using the delegated host with host 1163 and isRequired="true". 1165 The following "rdeCsv" fields, defined in section Host CSV model 1166 elements (Section 5.2.2), MUST be used in the 1167 "domainNameServersAddresses" element: 1169 Host name field with type="eppcom:labelType" and 1170 isRequired="true". 1172 The following "csvHost" fields, defined in section Host CSV model 1173 elements (Section 5.2.2), MAY be used in the 1174 "domainNameServersAddresses" element: 1176 IP addresses associated with the host object with 1177 type="host:addrStringType". 1179 IP addresses version associated with the host 1180 object with type="host:ipType". "host:ipType" has the enumerated 1181 values of "v4" or "v6". 1183 Example of a "domainNameServersAddresses" 1184 element. 1186 ... 1187 1188 ... 1189 1190 1191 1192 1193 1194 1195 1196 1197 1199 domainNameServersAddresses-YYYYMMDD.csv 1200 1201 1202 1203 ... 1204 1205 ... 1207 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1208 file. The file contains the delegated hosts (name servers) for the 1209 four domain names domain1.test, domain2.test, xn--abc123.test and 1210 xn--abc321.test. 1212 domain1.test,ns1.domain1.test,192.0.2.1,v4 1213 domain1.test,ns2.domain1.test,2001:DB8::1,v6 1214 domain2.test,ns1.domain2.test2,192.0.2.2,v4 1215 domain2.test,ns2.domain2.test2,2001:DB8::2,v6 1216 xn--abc123.test,ns1.example.example,, 1217 xn--abc123.test,ns2.example.example,, 1218 xn--abc321.test,ns1.example.example,, 1219 xn--abc321.test,ns2.example.example,, 1221 5.1.2.1.6. "dnssec" CSV File Definition 1223 The "dnssec" CSV File Definition defines the fields and CSV file 1224 references used for the domain name object DNSSEC records (DS or Key 1225 Data). 1227 The following "csvDomain" field elements MUST be used in the "dnssec" 1228 rdeCsv:fields> element when the DS Data Interface per 1229 [RFC5910] is used: 1231 Contains the DS key tag value per [RFC5910] with 1232 type="unsignedShort" and isRequired="true". 1234 Contains the DS algorithm value per [RFC5910] 1235 with type="unsignedByte" and isRequired="true". 1237 Contains the DS digest type value per 1238 [RFC5910] with type="unsignedByte" and isRequired="true". 1240 Contains the DS digest value per [RFC5910] with 1241 type="hexBinary" and isRequired="true". 1243 The following "csvDomain" field elements MUST be used in the "dnssec" 1244 rdeCsv:fields> element when the Key Data Interface per 1245 [RFC5910] is used: 1247 Contains the flags field value per [RFC5910] with 1248 type="unsignedShort" and isRequired="true". 1250 Contains the Key protocol value per [RFC5910] 1251 with type="unsignedByte" and isRequired="true". 1253 Contains the Key algorithm value per [RFC5910] 1254 with type="unsignedByte" and isRequired="true". 1256 Contains the public key value per [RFC5910] with 1257 type="secDNS:keyType" and isRequired="true". 1259 The following "csvDomain" field elements MAY be used in the "dnssec" 1260 rdeCsv:fields> element: 1262 Indicates a child's preference for the 1263 number of seconds after signature generation when the parent's 1264 signature on the DS information provided by the child will expire 1265 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1267 The following "domain" fields, defined for the "domain" CSV File 1268 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1269 element: 1271 Domain name of the domain object associated with 1272 the DNSSEC record and isRequired="true". 1274 Example of a "dnssec" element with 1275 the DS Data Interface of [RFC5910]: 1277 1278 ... 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1291 dnssec-ds-YYYYMMDD.csv 1292 1293 1294 1295 ... 1296 1297 ... 1299 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1300 contains two DS records for domain1.test. 1302 domain1.test,604800,12345,3,1,49FD46E6C4B45C55D4AC 1303 domain1.test,604800,12346,3,1,38EC35D5B3A34B44C39B 1304 Example of a "dnssec" element with 1305 the Key Data Interface of [RFC5910]: 1307 1308 ... 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1321 dnssec-key-YYYYMMDD.csv 1322 1323 1324 1325 ... 1326 1327 ... 1329 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1330 contains two key records for domain1.test. 1332 domain1.test,604800,257,3,1,AQPJ////4Q== 1333 domain1.test,604800,257,3,1,AQPJ////4QQQ 1335 5.1.2.1.7. "domainTransfer" CSV File Definition 1337 The "domainTransfer" CSV File Definition defines the fields and CSV 1338 file references used for the domain name object pending and completed 1339 transfer records. No additional field elements were added for use in 1340 the "domainTransfer" element. 1342 The following "rdeCsv" fields, defined in section CSV common field 1343 elements (Section 4.7.2), MUST be used in the "domainTransfer" 1344 element: 1346 State of the most recent transfer request with 1347 isRequired="true". 1349 Identifier of the registrar, defined in Section 5.4, 1350 of the client that requested the transfer with isRequired="true". 1352 Date and time that the transfer was requested with 1353 isRequired="true". 1355 Identifier of the registrar, defined in Section 5.4, 1356 of the client that should take or took action with 1357 isRequired="true". 1359 Date and time that the transfer action should be 1360 taken or has been taken with isRequired="true". 1362 The following "rdeCsv" fields, defined in section CSV common field 1363 elements (Section 4.7.2), MAY be used in the "domainTransfer" 1364 element: 1366 Expiration date if the transfer command caused or 1367 causes a change in the validity period. 1369 Identifier of client that requested the transfer. 1371 Identifier of client that should take or took action 1372 for transfer. 1374 The following "csvDomain" fields, defined for the "domain" CSV File 1375 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1376 element: 1378 Domain name of the domain object involved in the 1379 transfer with isRequired="true". 1381 Example of a "domainTransfer" 1382 element. 1384 ... 1385 1386 ... 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1402 domainTransfer-YYYYMMDD.csv 1403 1404 1405 1406 ... 1407 1408 ... 1410 Example of the corresponding domainTransfer-YYYYMMDD.csv file. The 1411 file contains one domain transfer record with a pending status. 1413 domain1.test,pending,registrarX,clientY, 1414 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1415 2016-04-03T22:00:00.0Z 1417 5.1.2.2. 1419 The is used to hold the deleted domain name 1420 objects in a differential or incremental deposit. All the domain 1421 name object data is deleted as part of a cascade delete. The 1422 is split into separate CSV file definitions using 1423 named elements with the "name" attribute. The following 1424 section defines the supported domain name deletes CSV file 1425 definition. 1427 5.1.2.2.1. "domain" Deletes CSV File Definition 1429 The following "csvDomain" field elements MUST be used in the deletes 1430 "domain" element: 1432 Domain name field with type="eppcom:labelType" and 1433 isRequired="true". 1435 Example of a "domain" element: 1437 ... 1438 1439 ... 1440 1441 1442 1443 1444 1445 1447 domain-delete-YYYYMMDD.csv 1448 1449 1450 1451 ... 1452 1453 ... 1455 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1456 file contains two domain name records. 1458 domain1.test 1459 domain2.test 1461 5.2. Host Object 1463 The host object is based on the EPP host name mapping in [RFC5732]. 1464 The host object supports both the XML Model and the CSV Model, 1465 defined in Models (Section 2) section. The elements used for both 1466 models are defined in the following sections. Both the 1467 and elements contain one or more 1468 elements with a set of named CSV file definitions using 1469 the "name" attribute. 1471 5.2.1. XML Model 1473 There are two elements used in the data escrow of the host objects 1474 for the XML model including the , under the 1475 element, and the element, under 1476 the element. 1478 A element substitutes for the 1479 abstract element to define a concrete definition of a host. The 1480 element can be replaced by other host 1481 definitions using the XML schema substitution groups feature. 1483 5.2.1.1. element 1485 The RDE host object is based on the EPP host response for an 1486 authorized client (Section 3.1.2. of [RFC5732]). 1488 The OPTIONAL element contains the following child elements: 1490 o A element that contains the fully qualified name of the 1491 host object. 1493 o A element that contains the repository object identifier 1494 assigned to the host object when the object was created. 1496 o One or more elements that describe the status of the host 1497 object. 1499 o Zero or more elements that contain the IP addresses 1500 associated with the host object. 1502 o A element that contains the identifier of the sponsoring 1503 registrar. 1505 o A element that contains the identifier of the registrar 1506 that created the host object. An OPTIONAL client attribute is 1507 used to specify the client that performed the operation. 1509 o A element that contains the date and time of host-object 1510 creation. 1512 o An OPTIONAL element that contains the identifier of the 1513 registrar that last updated the host object. This element MUST 1514 NOT be present if the host object has never been modified. An 1515 OPTIONAL client attribute is used to specify the client that 1516 performed the operation. 1518 o An OPTIONAL element that contains the date and time of 1519 the most recent host-object modification. This element MUST NOT 1520 be present if the host object has never been modified. 1522 o An OPTIONAL element that contains the date and time of 1523 the most recent host object successful transfer. This element 1524 MUST NOT be present if the domain name object has never been 1525 transfered. 1527 Example of object: 1529 ... 1530 1531 ns1.example1.test 1532 Hns1_example_test-TEST 1533 1534 1535 192.0.2.2 1536 192.0.2.29 1537 1080:0:0:0:8:800:200C:417A 1538 RegistrarX 1539 RegistrarX 1540 1999-05-08T12:10:00.0Z 1541 RegistrarX 1542 2009-10-03T09:34:00.0Z 1543 1544 ... 1546 5.2.1.2. object 1548 The element contains the fully qualified domain name 1549 of a host that was deleted. The element also 1550 supports host removal based on roid to support SRS systems in which 1551 different hosts with the same fully qualified domain name are active 1552 at the same time. 1554 Example of object: 1556 ... 1557 1558 ... 1559 1560 ns1.example.test 1561 1562 ... 1563 1564 ... 1566 5.2.2. CSV Model 1568 For the CSV Model of the host object, the child 1569 element of the element is used to hold the new or 1570 updated host objects for the deposit. The child 1571 element of the element is used to hold the deleted or 1572 purged host objects for the deposit. 1574 Differential and incremental deposits are based on changes to the 1575 host objects. The updated host object data under the 1576 element is a cascade replace down all of the host 1577 CSV files starting with the parent "host" CSV File Definition 1578 (Section 5.2.2.1.1). The child CSV file definitions include a 1579 field. All the child CSV file 1580 definition data for the host objects in the parent "host" CSV File 1581 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1582 using the data in the child CSV files. The deleted host object data 1583 under the element is a cascade delete starting from 1584 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1586 5.2.2.1. 1588 The is used to hold the new or updated host object 1589 information for the deposit. The is split into 1590 separate CSV file definitions using named elements with 1591 the "name" attribute. The following sections include the supported 1592 host CSV file definitions. 1594 5.2.2.1.1. "host" CSV File Definition 1596 The "host" CSV File Definition defines the fields and CSV file 1597 references used for the host object records. 1599 The following "csvHost" field elements MUST be used in the "host" 1600 element: 1602 Host name field with type="eppcom:labelType" and 1603 isRequired="true". 1605 The following "rdeCsv" fields, defined in section CSV common field 1606 elements (Section 4.7.2), MUST be used in the "host" 1607 element: 1609 Repository Object IDentifier (ROID) assigned to the 1610 host object with isRequired="true". 1612 The following "rdeCsv" fields, defined in section CSV common field 1613 elements (Section 4.7.2), MAY be used in the "host" 1614 element: 1616 Identifier of the sponsoring client with 1617 isRequired="true". 1619 Identifier of the registrar, defined in Section 5.4, 1620 of the client that created the object with isRequired="true". 1622 Identifier of client that created the host object. 1624 Date and time that the host object was created with 1625 isRequired="true". 1627 Identifier of the registrar, defined in Section 5.4, 1628 of the client that updated the object. 1630 Identifier of client that last updated the host 1631 object. 1633 Date and time that the host object was last 1634 updated. 1636 Date and time that the host was last transferred. 1638 Example of a "host" element. 1640 ... 1641 1642 ... 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1659 host-YYYYMMDD.csv 1660 1661 1662 1663 ... 1664 1665 ... 1667 Example of the corresponding host-YYYYMMDD.csv file. The file 1668 contains six host records with four being internal hosts and two 1669 being external hosts. 1671 ns1.domain1.test,Hns1_example_test-TEST,registrarX,registrarX, 1672 clientY,1999-05-08T12:10:00.0Z,registrarX, 1673 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1674 ns2.domain1.test,Hns2_domain1_test-TEST,registrarX,registrarX, 1675 clientY,1999-05-08T12:10:00.0Z,registrarX, 1676 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1677 ns1.domain2.test,Hns1_domain2_test-TEST,registrarX,registrarX, 1678 clientY,1999-05-08T12:10:00.0Z,registrarX, 1679 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1680 ns2.domain2.test,Hns2_domain2_test-TEST,registrarX,registrarX, 1681 clientY,1999-05-08T12:10:00.0Z,registrarX, 1682 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1683 ns1.example.example,Hns1_example_test-TEST,registrarX,registrarX, 1684 clientY,1999-05-08T12:10:00.0Z,registrarX, 1685 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1686 ns2.example.example,Hns2_example_test-TEST,registrarX,registrarX, 1687 clientY,1999-05-08T12:10:00.0Z,registrarX, 1688 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1690 5.2.2.1.2. "hostStatuses" CSV File Definition 1692 The "hostStatuses" CSV File Definition defines the fields and CSV 1693 file references used for the host object statuses. 1695 The following "csvHost" fields, defined for the "host" CSV File 1696 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1697 element: 1699 The status of the host with 1700 type="host:statusValueType" and isRequired="true"./>. 1702 The following "rdeCsv" fields, defined in section CSV common field 1703 elements (Section 4.7.2), MUST be used in the "hostStatuses" 1704 element: 1706 Host object Registry Object IDentifier (ROID) 1707 assigned to the host object with isRequired="true". 1709 The following "rdeCsv" fields, defined in section CSV common field 1710 elements (Section 4.7.2), MAY be used in the "hostStatuses" 1711 element: 1713 Host object status description which is 1714 free form text describing the rationale for the status. The 1715 attribute isRequired MUST equal "true". 1717 Language of the field. 1719 Example of a "hostStatuses" element. 1721 ... 1722 1723 ... 1724 1725 1726 1727 1728 1729 1730 1731 1732 1734 hostStatuses-YYYYMMDD.csv 1735 1736 1737 1738 ... 1739 1740 ... 1742 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1743 file contains the statuses for the six host names ns1.domain1.test, 1744 ns2.domain1.test, ns1.domain2.test, ns2.domain2.test, 1745 ns1.example.example and ns2.example.example. 1747 Hns1_domain1_test-TEST,ok,, 1748 Hns2_domain1_test-TEST,ok,, 1749 Hns1_domain2_test-TEST,ok,, 1750 Hns2_domain2_test-TEST,ok,, 1751 Hns1_example_test-TEST,ok,, 1752 Hns2_example_test-TEST,ok,, 1754 5.2.2.1.3. "hostAddresses" CSV File Definition 1756 The "hostAddresses" CSV File Definition defines the fields and CSV 1757 file references used for the host object IP addresses. 1759 The following "csvHost" field elements MUST be used in the 1760 "hostAddresses" element: 1762 IP addresses associated with the host object with 1763 type="host:addrStringType". The attribute isRequired MUST equal 1764 "true". 1766 IP addresses version associated with the host 1767 object with type="host:ipType". "host:ipType" has the enumerated 1768 values of "v4" or "v6". The attribute isRequired MUST equal 1769 "true". 1771 The following "rdeCsv" fields, defined in section CSV common field 1772 elements (Section 4.7.2), MUST be used in the "hostAddresses" 1773 element: 1775 Host object Registry Object IDentifier (ROID) 1776 assigned to the host object. 1778 Example of a "hostAddresses" element. 1780 ... 1781 1782 ... 1783 1784 1785 1786 1787 1788 1789 1790 1792 hostAddresses-YYYYMMDD.csv 1793 1794 1795 1796 ... 1797 1798 ... 1800 Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The 1801 file contains the IP addresses for the host names ns1.domain1.test, 1802 ns2.domain1.test, ns1.domain2.test and ns2.domain2.test. 1804 Hns1_domain1_test-TEST,192.0.2.1,v4 1805 Hns2_domain1_test-TEST,2001:DB8::1,v6 1806 Hns1_domain2_test-TEST,192.0.2.2,v4 1807 Hns2_domain2_test-TEST,2001:DB8::2,v6 1809 5.2.2.2. 1811 The is used to hold the deleted host objects in a 1812 differential or incremental deposit. All the host object data is 1813 deleted as part of a cascade delete. The is split 1814 into separate CSV file definitions using named elements 1815 with the "name" attribute. The following section defines the 1816 supported host deletes CSV file definition. 1818 5.2.2.2.1. "host" Deletes CSV File Definition 1820 The following "rdeCsv" fields, defined in section CSV common field 1821 elements (Section 4.7.2), MUST be used in the "host" 1822 element: 1824 Repository Object IDentifier (ROID) assigned to the 1825 host object with isRequired="true". 1827 Example of a "host" element. 1829 ... 1830 1831 ... 1832 1833 1834 1835 1836 1837 1839 host-delete-YYYYMMDD.csv 1840 1841 1842 1843 ... 1844 1845 ... 1847 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1848 host records. 1850 Hns1_domain1_test-TEST 1851 Hns2_domain1_test-TEST 1852 Hns1_domain2_test-TEST 1853 Hns2_domain2_test-TEST 1855 5.3. Contact Object 1857 The contact object is based on the EPP contact name mapping in 1858 [RFC5733]. The contact object supports both the XML Model and the 1859 CSV Model, defined in Models (Section 2) section. The elements used 1860 for both models are defined in the following sections. 1862 5.3.1. XML Model 1864 There are two elements used in the data escrow of the contact objects 1865 for the XML model including the , under the 1866 element, and the element, 1867 under the element. 1869 A element substitutes for the abstract 1870 element to define a concrete definition of a contact. The 1871 element can be replaced by other contact 1872 definitions using the XML schema substitution groups feature. 1874 5.3.1.1. object 1876 The contact object is based on the EPP contact response for an 1877 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1878 including the data from an EPP Query Response, see 1879 Section 3.1.3. of [RFC5733]. 1881 The OPTIONAL element contains the following child elements: 1883 o A element that contains the server-unique identifier of the 1884 contact object 1886 o A element that contains the Repository Object IDentifier 1887 assigned to the contact object when the object was created. 1889 o One or more elements that describe the status of the 1890 contact object. 1892 o One or two elements that contain postal-address 1893 information. Two elements are provided so that address 1894 information can be provided in both internationalized and 1895 localized forms; a "type" attribute is used to identify the two 1896 forms. If an internationalized form (type="int") is provided, 1897 element content MUST be represented in a subset of UTF-8 that can 1898 be represented in the 7-bit US-ASCII character set. If a 1899 localized form (type="loc") is provided, element content MAY be 1900 represented in unrestricted UTF-8. The element 1901 contains the following child elements: 1903 * A element that contains the name of the individual or 1904 role represented by the contact. 1906 * An OPTIONAL element that contains the name of the 1907 organization with which the contact is affiliated. 1909 * An element that contains address information associated 1910 with the contact. An element contains the following 1911 child elements: 1913 + One, two, or three OPTIONAL elements that contain 1914 the contact's street address. 1916 + A element that contains the contact's city. 1918 + An OPTIONAL element that contains the contact's state 1919 or province. 1921 + An OPTIONAL element that contains the contact's postal 1922 code. 1924 + A element that contains the contact's two-letter 1925 country code. 1927 o An OPTIONAL element that contains the contact's voice 1928 telephone number. 1930 o An OPTIONAL element that contains the contact's facsimile 1931 telephone number. 1933 o An element that contains the contact's email address. 1935 o A element that contains the identifier of the sponsoring 1936 registrar. 1938 o A element that contains the identifier of the registrar 1939 that created the contact object. An OPTIONAL client attribute is 1940 used to specify the client that performed the operation. 1942 o A element that contains the date and time of contact- 1943 object creation. 1945 o An OPTIONAL element that contains the identifier of the 1946 registrar that last updated the contact object. This element MUST 1947 NOT be present if the contact has never been modified. An 1948 OPTIONAL client attribute is used to specify the client that 1949 performed the operation. 1951 o An OPTIONAL element that contains the date and time of 1952 the most recent contact-object modification. This element MUST 1953 NOT be present if the contact object has never been modified. 1955 o An OPTIONAL element that contains the date and time of 1956 the most recent contact object successful transfer. This element 1957 MUST NOT be present if the contact object has never been 1958 transferred. 1960 o An OPTIONAL element that contains the following child 1961 elements related to the last transfer request of the contact 1962 object: 1964 * A element that contains the state of the most recent 1965 transfer request. 1967 * A element that contains the identifier of the registrar 1968 that requested the domain name object transfer. An OPTIONAL 1969 client attribute is used to specify the client that performed 1970 the operation. 1972 * An element that contains the identifier of the registrar 1973 that SHOULD act upon a PENDING transfer request. For all other 1974 status types, the value identifies the registrar that took the 1975 indicated action. An OPTIONAL client attribute is used to 1976 specify the client that performed the operation. 1978 * A element that contains the date and time that the 1979 transfer was requested. 1981 * An element that contains the date and time of a 1982 required or completed response. For a PENDING request, the 1983 value identifies the date and time by which a response is 1984 required before an automated response action will be taken by 1985 the registry. For all other status types, the value identifies 1986 the date and time when the request was completed. 1988 o An OPTIONAL element that identifies elements that 1989 requiring exceptional server-operator handling to allow or 1990 restrict disclosure to third parties. See Section 2.9 of 1991 [RFC5733] for a description of the child elements contained within 1992 the element. 1994 Example object: 1996 ... 1997 1998 Csh8013-TEST 1999 sh8013 2000 2001 2002 2003 John Doe 2004 Example Inc. 2005 2006 123 Example Dr. 2007 Suite 100 2008 Dulles 2009 VA 2010 20166-6503 2011 US 2012 2013 2014 +1.7035555555 2015 +1.7035555556 2016 jdoe@example.test 2017 RegistrarX 2018 RegistrarX 2019 2009-09-13T08:01:00.0Z 2020 RegistrarX 2021 2009-11-26T09:10:00.0Z 2022 2009-12-03T09:05:00.0Z 2023 2024 pending 2025 clientW 2026 2011-03-08T19:38:00.0Z 2027 RegistrarX 2028 2011-03-13T23:59:59.0Z 2029 2030 2031 2032 2033 2034 2035 ... 2037 5.3.1.2. object 2039 The element contains the id of a contact that was 2040 deleted. 2042 Example of object: 2044 ... 2045 2046 ... 2047 2048 sh8013-TEST 2049 co8013-TEST 2050 2051 ... 2052 2053 ... 2055 5.3.2. CSV Model 2057 For the CSV Model of the contact object, the 2058 child element of the element is used to hold the new 2059 or updated contacts objects for the deposit. The 2060 child element of the element is 2061 used to hold the deleted or purged contact objects for the deposit. 2062 Both the and elements 2063 contain one or more elements with a set of named CSV 2064 file definitions using the "name" attribute. 2066 Differential and incremental deposits are based on changes to the 2067 contact objects. The updated contact object data under the 2068 element is a cascade replace down all of the 2069 contact CSV files starting with the parent "contact" CSV File 2070 Definition (Section 5.3.2.1.1). The child CSV file definitions 2071 include a field. All the child CSV 2072 file definition data for the contact objects in the parent "contact" 2073 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2074 then set using the data in the child CSV files. The deleted contact 2075 object data under the element is a cascade 2076 delete starting from the "contact" Deletes CSV File Definition 2077 (Section 5.3.2.2.1). 2079 5.3.2.1. 2081 The is used to hold the new or updated contact 2082 object information for the deposit. The is 2083 split into separate CSV file definitions using named 2084 elements with the "name" attribute. The following sections include 2085 the supported contact CSV file definitions. 2087 5.3.2.1.1. "contact" CSV File Definition 2089 The "contact" CSV File Definition defines the fields and CSV file 2090 references used for the contact object records. 2092 The following "csvContact" field elements MUST be used in the 2093 "contact" element: 2095 Contains the server-unique contact identifier with 2096 type="eppcom:clIDType" and isRequired="true". 2098 Contains the contact's email address with 2099 type="eppcom:minTokenType" and isRequired="true". 2101 The following field elements MAY be used in the "contact" 2102 element: 2104 Contains the contact's voice telephone number 2105 with type="contact:e164StringType". 2107 Contains the contact's voice telephone number 2108 extension with type="token". 2110 Contains the contact's facsimile telephone number 2111 with type="contact:e164StringType". 2113 Contains the contact's facsimile telephone 2114 number extension with type="token". 2116 The following "rdeCsv" fields, defined in section CSV common field 2117 elements (Section 4.7.2), MUST be used in the "contact" 2118 element: 2120 The Registry Object IDentifier (ROID) for the contact 2121 object with isRequired="true". 2123 Identifier of client (registrar) that sponsors the 2124 contact object with isRequired="true". 2126 Identifier of the registrar, defined in Section 5.4, 2127 of the client that created the object with isRequired="true". 2129 Created date and time of the contact object with 2130 isRequired="true". 2132 Identifier of the registrar, defined in Section 5.4, 2133 of the client that updated the object. 2135 Date and time of the last update to the contact 2136 object. 2138 The following "rdeCsv" fields, defined in section CSV common field 2139 elements (Section 4.7.2), MAY be used in the "contact" 2140 element: 2142 Identifier of client that created the contact object. 2144 Identifier of the client that last updated the 2145 contact object. 2147 Date and time of the last transfer for the contact 2148 object. 2150 Example of a "contact" element. 2152 ... 2153 2154 ... 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2175 contact-YYYYMMDD.csv 2176 2177 2178 2179 ... 2180 2181 ... 2183 Example of the contact-YYYYMMDD.csv file. The file contains nine 2184 object contact records. 2186 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2187 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2188 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2189 2009-11-26T09:10:00.0Z 2190 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2191 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2192 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2193 2009-11-26T09:10:00.0Z 2194 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2195 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2196 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2197 2009-11-26T09:10:00.0Z 2198 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2199 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2200 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2201 2009-11-26T09:10:00.0Z 2202 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2203 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2204 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2205 2009-11-26T09:10:00.0Z 2206 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2207 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2208 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2209 2009-11-26T09:10:00.0Z 2210 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2211 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2212 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2213 2009-11-26T09:10:00.0Z 2214 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2215 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2216 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2217 2009-11-26T09:10:00.0Z 2218 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2219 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2220 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2221 2009-11-26T09:10:00.0Z 2223 5.3.2.1.2. "contactStatuses" CSV File Definition 2225 The "contactStatuses" CSV File Definition defines the fields and CSV 2226 file references used for the contact object statuses. 2228 The following "csvContact" field elements, defined for the "contact" 2229 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2230 "contactStatuses" element: 2232 Server-unique contact identifier of status with 2233 isRequired="true". 2235 The status of the contact with 2236 type="contact:statusValueType" and isRequired="true". 2238 The following "rdeCsv" fields, defined in section CSV common field 2239 elements (Section 4.7.2), MAY be used in the "contactStatuses" 2240 element: 2242 The contact object status description 2243 which is free form text describing the rationale for the status. 2245 Language of the field. 2247 Example of a "contactStatuses" 2248 element. 2250 ... 2251 2252 ... 2253 2254 2255 2256 2257 2258 2259 2260 2261 2263 contactStatuses-YYYYMMDD.csv 2264 2265 2266 2267 ... 2268 2269 ... 2271 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2272 file contains the statuses for the nine contact identifiers. 2274 domain1admin,ok,, 2275 domain1tech,ok,, 2276 domain1billing,ok,, 2277 domain2admin,ok,, 2278 domain2tech,ok,, 2279 domain2billing,ok,, 2280 xnabc123admin,ok,, 2281 xnabc123tech,ok,, 2282 xnabc123billing,ok,, 2284 5.3.2.1.3. "contactPostal" CSV File Definition 2286 The "contactPostal" CSV File Definition defines the fields and CSV 2287 file references used for the contact postal info object records. 2289 The following "csvContact" field elements MUST be used in the 2290 "contactPostal" element: 2292 Contains the form of the postal-address 2293 information with type="contact:postalLineType" and 2294 isRequired="true". This field specifies the form ("int" or 2295 "loc"), as defined in Section 4.8, of the , 2296 , , , 2297 , , fields. 2299 Contains the contact's name of the individual or 2300 role represented by the contact with type="contact:postalLineType" 2301 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2302 indicate the localized or internationalized form as defined in 2303 section Section 4.8. 2305 Contains the contact's contact's street address 2306 line with type="contact:fPostalLineType". An index attribute is 2307 required to indicate which street address line the field 2308 represents with index "0" for the first line and index "2" for the 2309 last line. An OPTIONAL "isLoc" attribute to used to indicate the 2310 localized or internationalized form as defined in section 2311 Section 4.8. 2313 Contains the contact's city with 2314 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2315 "isLoc" attribute to used to indicate the localized or 2316 internationalized form as defined in section Section 4.8. 2318 Contains the contact's country code with 2319 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2320 attribute to used to indicate the localized or internationalized 2321 form as defined in section Section 4.8. 2323 The following "csvContact" field elements MAY be used in the 2324 "contactPostal" element: 2326 Contains the name of the organization with which 2327 the contact is affiliated with type="contact:optPostalLineType". 2328 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2329 internationalized form as defined in section Section 4.8. 2331 Contains the contact's state or province with 2332 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2333 to used to indicate the localized or internationalized form as 2334 defined in section Section 4.8. 2336 Contains the contact's postal code with 2337 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2338 indicate the localized or internationalized form as defined in 2339 section Section 4.8. 2341 The following "csvContact" fields, defined for the "contact" CSV File 2342 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2343 element: 2345 Server-unique contact identifier for the contact 2346 object with isRequired="true". 2348 Example of a "contactPostal" 2349 element. 2351 ... 2352 2353 ... 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2371 contactPostal-YYYYMMDD.csv 2372 2373 2374 2375 ... 2376 2377 ... 2379 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2380 nine contact postal records. 2382 domain1admin,int,"John Doe","Example Inc.", 2383 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2384 domain1tech,int,"John Doe","Example Inc.", 2385 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2386 domain1billing,int,"John Doe","Example Inc.", 2387 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2388 domain2admin,int,"John Doe","Example Inc.", 2389 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2390 domain2tech,int,"John Doe","Example Inc.", 2391 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2392 domain2billing,int,"John Doe","Example Inc.", 2393 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2394 xnabc123admin,int,"John Doe","Example Inc.", 2395 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2396 xnabc123tech,int,"John Doe","Example Inc.", 2397 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2398 xnabc123billing,int,"John Doe","Example Inc.", 2399 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2401 5.3.2.1.4. "contactTransfer" CSV File Definition 2403 The "contactTransfer" CSV File Definition defines the fields and CSV 2404 file references used for the contact object pending and completed 2405 transfer records. No additional field elements were added for use in 2406 the "contactTransfer" element. The 2407 following "rdeCsv" fields, defined in section CSV common field 2408 elements (Section 4.7.2), MUST be used in the "contactTransfer" 2409 element: 2411 State of the most recent transfer request with 2412 isRequired="true". 2414 Identifier of the registrar, defined in Section 5.4, 2415 of the client that requested the transfer with isRequired="true". 2417 Date and time that the transfer was requested with 2418 isRequired="true". 2420 Identifier of the registrar, defined in Section 5.4, 2421 of the client that should take or took action with 2422 isRequired="true". 2424 Date and time that the transfer action should be 2425 taken or has been taken with isRequired="true". 2427 The following "rdeCsv" fields, defined in section CSV common field 2428 elements (Section 4.7.2), MAY be used in the "contactTransfer" 2429 element: 2431 Identifier of client that requested the transfer. 2433 Identifier of client that should take or took action 2434 for transfer. 2436 The following "csvContact" fields, defined for the "contact" CSV File 2437 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2438 element: 2440 Server-unique contact identifier for the contact 2441 object with isRequired="true". 2443 Example of a "contactTransfer" 2444 element. 2446 ... 2447 2448 ... 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2463 contactTransfer-YYYYMMDD.csv 2464 2465 2466 2467 ... 2468 2469 ... 2471 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2472 one contact transfer record in pending status. 2474 xnabc123admin,clientApproved,registrarX,clientX, 2475 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2477 5.3.2.1.5. "contactDisclose" CSV File Definition 2479 The "contactDisclose" CSV File Definition defines the fields and CSV 2480 file references used for the contact disclose object records. 2482 The following "csvContact" field elements MAY be used in the 2483 "contactDisclose" element: 2485 Contains flag with a value of "true" or 2486 "1" (one) notes the preference to allow disclosure of the 2487 specified elements as an exception to the stated data-collection 2488 policy. A value of "false" or "0" (zero) notes a client 2489 preference to not allow disclosure of the specified elements as an 2490 exception to the stated data-collection policy with 2491 type="boolean". The additional fields define specific exceptional 2492 disclosure preferences based on the 2493 field. 2495 Exceptional disclosure preference flag 2496 for the localized form of the contact name with type="boolean". 2498 Exceptional disclosure preference flag 2499 for the internationalized form of the contact name with 2500 type="boolean". 2502 Exceptional disclosure preference flag 2503 for the localized form of the contact organization with 2504 type="boolean". 2506 Exceptional disclosure preference flag 2507 for the internationalized form of the contact organization with 2508 type="boolean". 2510 Exceptional disclosure preference flag 2511 for the localized form of the contact address with type="boolean". 2513 Exceptional disclosure preference flag 2514 for the internationalized form of the contact address with 2515 type="boolean". 2517 Exceptional disclosure preference flag 2518 of the contact voice telephone number with type="boolean". 2520 Exceptional disclosure preference flag of 2521 the contact facsimile telephone number with type="boolean". 2523 Exceptional disclosure preference flag 2524 of the contact email address with type="boolean". 2526 The following "csvContact" fields, defined for the "contact" CSV File 2527 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2528 element: 2530 Server-unique contact identifier for the contact 2531 object with isRequired="true". 2533 Example of a "contactDisclose" 2534 element. 2536 ... 2537 2538 ... 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2556 contactDisclose-YYYYMMDD.csv 2557 2558 2559 2560 ... 2561 2562 ... 2564 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2565 one disclosure records, disabling disclosure of voice, fax, and 2566 email. 2568 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2570 5.3.2.2. 2572 The is used to hold the deleted contact objects 2573 in a differential or incremental deposit. All the contact object 2574 data is deleted as part of a cascade delete. The 2575 is split into separate CSV file definitions 2576 using named elements with the "name" attribute. The 2577 following section defines the supported contact deletes CSV file 2578 definition. 2580 5.3.2.2.1. "contact" Deletes CSV File Definition 2582 The following "csvContact" field elements MUST be used in the deletes 2583 "contact" element: 2585 Contains the server-unique contact identifier with 2586 type="eppcom:clIDType" and isRequired="true". 2588 Example of a "contact" element. 2590 ... 2591 2592 ... 2593 2594 2595 2596 2597 2598 2600 contact-delete-YYYYMMDD.csv 2601 2602 2603 2604 ... 2605 2606 ... 2608 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2609 six contact records. 2611 domain1admin 2612 domain1tech 2613 domain1billing 2614 domain2admin 2615 domain2tech 2616 domain2billing 2618 5.4. Registrar Object 2620 The registrar object represents the sponsoring client for other 2621 objects, for operational purposes MAY be the registry operator. The 2622 registrar object supports both the XML Model and the CSV Model, 2623 defined in Section 2. The elements used for both models are defined 2624 in the following sections. 2626 5.4.1. XML Model 2628 There are two elements used in the data escrow of the registrar 2629 objects for the XML model including the , 2630 under the element, and the 2631 element, under the element. 2633 A element substitutes for the 2634 abstract element to define a 2635 concrete definition of a registrar. The 2636 element can be replaced by other 2637 domain definitions using the XML schema substitution groups feature. 2639 5.4.1.1. element 2641 The element contains the following child elements: 2643 o An element that contains the Registry-unique identifier of 2644 the registrar object. This has a superordinate relationship 2645 to a subordinate , or of domain, contact and 2646 host objects. 2648 o An element that contains the name of the registrar. 2650 o An OPTIONAL element that contains the ID assigned by 2651 ICANN. 2653 o A element that contains the operational status of the 2654 registrar. Possible values are: ok, readonly and terminated. 2656 o One or two elements that contain postal- address 2657 information. Two elements are provided so that address 2658 information can be provided in both internationalized and 2659 localized forms; a "type" attribute is used to identify the two 2660 forms. If an internationalized form (type="int") is provided, 2661 element content MUST be represented in a subset of UTF-8 that can 2662 be represented in the 7-bit US-ASCII character set. If a 2663 localized form (type="loc") is provided, element content MAY be 2664 represented in unrestricted UTF-8. The element 2665 contains the following child elements: 2667 * A element that contains address information associated 2668 with the registrar. The element contains the following 2669 child elements: 2671 + One, two, or three OPTIONAL elements that contain 2672 the registrar's street address. 2674 + A element that contains the registrar's city. 2676 + An OPTIONAL element that contains the registrar's state 2677 or province. 2679 + An OPTIONAL element that contains the registrar's 2680 postal code. 2682 + A element that contains the registrar's country code. 2684 o An OPTIONAL element that contains the registrar's voice 2685 telephone number. 2687 o An OPTIONAL element that contains the registrar's facsimile 2688 telephone number. 2690 o An element that contains the registrar's email address. 2692 o An OPTIONAL element that contains the registrar's URL. 2694 o An OPTIONAL elements that contains whois information. 2695 The element contains the following child elements: 2697 * An OPTIONAL element that contains the name of the 2698 registrar WHOIS server listening on TCP port 43 as specified in 2699 [RFC3912]. 2701 * An OPTIONAL element that contains the name of the 2702 registrar WHOIS server listening on TCP port 80/443. 2704 o A element that contains the date and time of registrar- 2705 object creation. 2707 o An OPTIONAL element that contains the date and time of 2708 the most recent RDE registrar-object modification. This element 2709 MUST NOT be present if the rdeRegistrar object has never been 2710 modified. 2712 Example of object: 2714 ... 2715 2716 RegistrarX 2717 Registrar X 2718 123 2719 ok 2720 2721 2722 123 Example Dr. 2723 Suite 100 2724 Dulles 2725 VA 2726 20166-6503 2727 US 2728 2729 2730 +1.7035555555 2731 +1.7035555556 2732 jdoe@example.test 2733 http://www.example.test 2734 2735 whois.example.test 2736 http://whois.example.test 2737 2738 2005-04-23T11:49:00.0Z 2739 2009-02-17T17:51:00.0Z 2740 2741 ... 2743 5.4.1.2. object 2745 The element contains the id of a registrar that 2746 was deleted. 2748 Example of object: 2750 ... 2751 2752 ... 2753 2754 agnt0001-TEST 2755 2756 ... 2757 2758 ... 2760 5.4.2. CSV Model 2762 For the CSV Model of the registrar object, the 2763 child element of the element 2764 is used to hold the new or updated registrar objects for the deposit. 2765 The child element of the element 2766 is used to hold the deleted or purged registrar objects for the 2767 deposit. Both the and 2768 elements contain one or more elements with a set of 2769 named CSV file definitions using the "name" attribute. 2771 Differential and incremental deposits are based on changes to the 2772 registrar objects. The updated registrar object data under the 2773 element is a cascade replace down all of the 2774 registrar CSV files starting with the parent "registrar" CSV File 2775 Definition (Section 5.4.2.1.1). The child CSV file definitions 2776 include a field. All the child CSV 2777 file definition data for the registrar objects in the parent 2778 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2779 deleted and then set using the data in the child CSV files. The 2780 deleted registrar object data under the 2781 element is a cascade delete starting from the "registrar" Deletes CSV 2782 File Definition (Section 5.4.2.2.1). 2784 5.4.2.1. 2786 The is used to hold the new or updated 2787 registrar object information for the deposit. The 2788 is split into separate CSV file definitions 2789 using named elements with the "name" attribute. The 2790 following sections include the supported contact CSV file 2791 definitions. 2793 5.4.2.1.1. "registrar" CSV File Definition 2795 The "registrar" CSV File Definition defines the fields and CSV file 2796 references used for the registrar object records. 2798 The following "csvRegistrar" field elements MUST be used in the 2799 "registrar" element: 2801 Contains the server-unique registrar identifier 2802 with type="eppcom:clIDType" and isRequired="true". 2804 Contains the name of the registrar with 2805 type="normalizedString" and isRequired="true". 2807 Contains the status of the registrar with 2808 type="csvRegistrar:statusValueType" and isRequired="true". 2810 The following field elements MAY be used in the "registrar" 2811 element: 2813 Contains the ID assigned by ICANN with 2814 type="positiveInteger". 2816 Contains the Whois URL of the registrar 2817 with type="anyURI". 2819 The following "rdeCsv" fields, defined in section CSV common field 2820 elements (Section 4.7.2), MUST be used in the "registrar" 2821 element: 2823 Created date and time of the registrar object with 2824 isRequired="true". 2826 Date and time of the last update to the registrar 2827 object. 2829 URL for the registrar web home page. 2831 The following "csvContact" fields, defined in section Contact Object 2832 (Section 5.3), MUST be used in the "registrar" 2833 element: 2835 Registrar street address line with an "index" 2836 attribute that represents the order of the street address line 2837 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2838 indicate the localized or internationalized form, as defined in 2839 Section 4.8. 2841 Registrar city with an OPTIONAL "isLoc" attribute 2842 that is used to indicate the localized or internationalized form, 2843 as defined in Section 4.8 with isRequired="true". 2845 Registrar country code with an OPTIONAL "isLoc" 2846 attribute that is used to indicate the localized or 2847 internationalized form, as defined in Section 4.8 with 2848 isRequired="true". 2850 Registrar email address with isRequired="true". 2852 The following "csvContact" fields, defined in section Contact Object 2853 (Section 5.3), MAY be used in the "registrar" 2854 element: 2856 Registrar state or province with an OPTIONAL 2857 "isLoc" attribute that is used to indicate the localized or 2858 internationalized form, as defined in Section 4.8. 2860 Registrar postal code with an OPTIONAL "isLoc" 2861 attribute that is used to indicate the localized or 2862 internationalized form, as defined in Section 4.8. 2864 Registrar voice telephone number. 2866 Registrar voice telephone number extension. 2868 Registrar facsimile telephone number. 2870 Registrar facsimile telephone number extension. 2872 Example of a "registrar" 2873 element. 2875 ... 2876 2877 ... 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2904 registrar-YYYYMMDD.csv 2905 2906 2907 2908 ... 2909 2910 ... 2912 Example of the registrar-YYYYMMDD.csv file. The file contains three 2913 registrar records. 2915 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 2916 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2917 +1.7035555556,,jdoe@example.test,http://www.example.test, 2918 http://whois.example.test,2005-04-23T11:49:00.0Z, 2919 2009-02-17T17:51:00.0Z 2920 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 2921 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2922 +1.7035555556,,jdoe@example.test,http://www.example.test, 2923 http://whois.example.test,2005-04-23T11:49:00.0Z, 2924 2009-02-17T17:51:00.0Z 2925 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 2926 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2927 +1.7035555556,,jdoe@example.test,http://www.example.test, 2928 http://whois.example.test,2005-04-23T11:49:00.0Z, 2929 2009-02-17T17:51:00.0Z 2931 5.4.2.2. 2933 The is used to hold the deleted registrar 2934 objects in a differential or incremental deposit. All the registrar 2935 object data is deleted as part of a cascade delete. The 2936 is split into separate CSV file definitions 2937 using named elements with the "name" attribute. The 2938 following section defines the supported registrar deletes CSV file 2939 definition. 2941 5.4.2.2.1. "registrar" Deletes CSV File Definition 2943 The following "csvRegistrar" field elements MUST be used in the 2944 deletes "registrar" element: 2946 Contains the server-unique registrar identifier 2947 with type="eppcom:clIDType" and isRequired="true". 2949 Example of a "registrar" element. 2951 ... 2952 2953 ... 2954 2955 2956 2957 2958 2959 2961 registrar-delete-YYYYMMDD.csv 2962 2963 2964 2965 ... 2966 2967 ... 2969 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 2970 one registrar record. 2972 registrarZ 2974 5.5. IDN Table Reference Object 2976 The Internationalized Domain Names (IDN) table reference object is a 2977 pseudo-object that is used to provide a short reference to the IDN 2978 Table and Policy used in IDN registrations. The IDN reference object 2979 supports both the XML and the CSV Model, defined in the Models 2980 (Section 2) section. The elements used for both models are defined 2981 in the following sections. 2983 5.5.1. XML Model 2985 There is one element used in the data escrow of the IDN table 2986 reference objects for the XML model that is the , 2987 under the element. 2989 5.5.1.1. object 2991 The contains the following elements. An "id" 2992 attribute is used to specify an identifier for the IDN table. 2994 o An element that contains the URL of the IDN table that is 2995 being referenced. 2997 o A element that contains the URL of the IDN policy 2998 document. If IDN variants are generated algorithmically, the 2999 policy document MUST define the algorithm and the state of the 3000 implicit generated IDN variants. For a list of suggested states 3001 for implicit IDN variants, please see [variantTLDsReport]. 3003 Example of object: 3005 ... 3006 3007 3008 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3009 3010 3011 http://registro.br/dominio/regras.html 3012 3013 3014 ... 3016 5.5.2. CSV Model 3018 The IDN domain names, defined in Section 5.1, MAY have references to 3019 the IDN language identifier using the field 3020 element. The IDN table reference object defines the mapping of a 3021 language identifier to a language table URL. The language table URL 3022 defines the character code points that can be used for the language 3023 identifier. The elements used for the IDN table reference object is 3024 defined in this section. The child element of the 3025 element is used to hold the new or updated IDN table 3026 reference objects for the deposit. The child 3027 element of the element is used to hold the deleted or 3028 purged IDN table reference objects for the deposit. Both the 3029 and elements contain one or more 3030 elements with a set of named CSV file definitions using 3031 the "name" attribute. 3033 5.5.2.1. 3035 The is used to hold the new or updated IDN table 3036 reference object information for the deposit. The 3037 is split into separate CSV file definitions using named 3038 elements with the "name" attribute. The following sections include 3039 the supported IDN table reference CSV file definitions. 3041 5.5.2.1.1. "idnLanguage" CSV File Definition 3043 The "idnLanguage" CSV File Definition defines the fields and CSV file 3044 references used for the IDN table reference object records. 3046 The following "rdeCsv" fields, defined in Section 4.7.2, MUST be used 3047 in the "idnLanguage" element: 3049 The language identifier that matches the values 3050 for the field element in the "domain" CSV 3051 File Definition (Section 5.1.2.1.1) files. The attribute 3052 isRequired MUST equal "true". 3054 URL that defines the character code points that can be 3055 used for the language defined by the field element. 3056 The attribute isRequired MUST equal "true". 3058 Example of a "idnLanguage" element. 3060 ... 3061 3062 ... 3063 3064 , 3065 3066 3067 3068 3069 3070 3072 idnLanguage-YYYYMMDD.csv 3073 3074 3075 3076 ... 3077 3078 ... 3080 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3081 contains two IDN language records. 3083 LANG-1, 3084 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3085 LANG-2, 3086 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3088 5.5.2.2. 3090 The is used to hold the deleted IDN table reference 3091 objects in a differential or incremental deposit. The 3092 is split into separate CSV file definitions using 3093 named elements with the "name" attribute. The following 3094 section defines the supported IDN table reference deletes CSV file 3095 definition. 3097 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3099 The following "idnLanguage" field elements MUST be used in the 3100 deletes "idnLanguage" element: 3102 The language identifier that matches the values 3103 for the field element in the "domain" CSV 3104 File Definition (Section 5.1.2.1.1) files. The attribute 3105 isRequired MUST equal "true". 3107 Example of a "idnLanguage" element. 3109 ... 3110 3111 ... 3112 3113 3114 3115 3116 3117 3119 idnLanguage-delete-YYYYMMDD.csv 3120 3121 3122 3123 ... 3124 3125 ... 3127 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3128 contains one IDN language record. 3130 LANG-2 3132 5.6. NNDN Object 3134 A NNDN (NNDN's not domain name) can be used to store registry 3135 reserved names or (blocked, withheld or mirrored) IDN variants. 3137 A NNDN is a lightweight domain-like object that is not linked 3138 directly to a Registrar (a mirroring NNDN is linked to a Registrar 3139 via the original name). 3141 A domain name can only exist as a domain name object or NNDN object, 3142 but not both. 3144 The NNDN object supports both the XML and the CSV Model, defined in 3145 the Models (Section 2) section. The elements used for both models 3146 are defined in the following sections. 3148 5.6.1. XML Model 3150 There are two elements used in the data escrow of the NNDN objects 3151 for the XML model including the , under the 3152 element, and the element, under the 3153 element. 3155 A element substitutes for the 3156 abstract element to define a concrete definition of a NNDN. The 3157 element can be replaced by other NNDN 3158 definitions using the XML schema substitution groups feature. 3160 5.6.1.1. object 3162 The element contains the following child elements: 3164 o An element that contains the fully qualified name of the 3165 NNDN. If the NNDN is an IDN, the ASCII Compatible Encoding (ACE) 3166 MUST be used. 3168 o An OPTIONAL element that contains the fully qualified name 3169 of the NNDN in Unicode character set. It MUST be provided if 3170 available. 3172 o An OPTIONAL element that references the IDN 3173 Table used for the NNDN. This corresponds to the "id" attribute 3174 of the element. This element MUST be present if the 3175 NNDN is an IDN. 3177 o An OPTIONAL element is used to indicate that the 3178 NNDN is used for an IDN variant. This element contains the domain 3179 name used to generate the IDN variant. 3181 o A element that indicates the state of the NNDN: 3182 blocked, withheld or mirrored. 3184 * If a NNDN is considered undesirable for registration (i.e., 3185 unavailable for allocation to anyone), then the NNDN will be 3186 tagged as "blocked". 3188 * If a NNDN is considered a potential registration of a domain 3189 object for a registrant, then the NNDN will be tagged as 3190 "withheld". This status is only used when the NNDN is used for 3191 an IDN variant. 3193 * If a NNDN is considered a mirrored IDN variant of a domain 3194 object, then the NNDN will be tagged as "mirrored". A 3195 mirroringNS attribute is used to specify if the mirrored IDN 3196 variant use the NS mirror mechanism. The default value of 3197 mirroringNS is true. If another mechanism such as DNAME is 3198 used, the value of mirroringNS attribute MUST be false. 3200 o A element that contains the date and time of the NNDN 3201 object creation. 3203 Example of object: 3205 ... 3206 3207 xn--exampl-gva.test 3208 pt-BR 3209 example1.test 3210 withheld 3211 2005-04-23T11:49:00.0Z 3212 3213 ... 3215 5.6.1.2. object 3217 The element contains the ACE of a NNDN that was 3218 deleted, i.e., the . 3220 Example of object: 3222 ... 3223 3224 ... 3225 3226 xn--pingino-q2a.test 3227 3228 ... 3229 3230 ... 3232 5.6.2. CSV Model 3234 For the CSV Model of the NNDN object, the child 3235 element of the element is used to hold the new or 3236 updated NNDN objects for the deposit. The child 3237 element of the element is used to hold the deleted or 3238 purged NNDN objects for the deposit. Both the and 3239 elements contain one or more elements 3240 with a set of named CSV file definitions using the 3241 "name" attribute. 3243 5.6.2.1. 3245 The is used to hold the new or updated NNDN object 3246 information for the deposit. The is split into 3247 separate CSV file definitions using named elements with 3248 the "name" attribute. The following sections include the supported 3249 NNDN CSV file definitions. 3251 5.6.2.1.1. "NNDN" CSV File Definition 3253 The "NNDN" CSV File Definition defines the fields and CSV file 3254 references used for the NNDN object records. 3256 The following "csvNNDN" field elements MUST be used in the "NNDN" 3257 element: 3259 ASCII Compatible Encoding (ACE) field of the NNDN 3260 with type="eppcom:labelType" and isRequired="true". 3262 State of the NNDN: blocked or withheld with 3263 type="rdeNNDN:nameState" and isRequired="true". See 3264 Section 5.6.1.1 for a description of the possible values for the 3265 element. 3267 The following field elements MAY be used in the "NNDN" 3268 element: 3270 Domain name used to generate the IDN variant 3271 with type="eppcom:labelType". 3273 Defines whether the "mirroring" 3274 uses the NS mirror mechanism, as described 3275 for the "mirroringNS" attribute in 3276 Section 5.6.1.1, with type="boolean". If the field element is not 3277 defined the default value is "true". 3279 The following "rdeCsv" fields, defined in section CSV common field 3280 elements (Section 4.7.2), MUST be used in the "domain" 3281 element: 3283 Created date and time of the NNDN object with 3284 isRequired="true". 3286 The following "rdeCsv" fields, defined in section CSV common field 3287 elements (Section 4.7.2), MAY be used in the "domain" 3288 element: 3290 Name of the NNDN in Unicode character set for the 3291 field element. 3293 IDN Table Identifier for the NNDN that matches 3294 an IDN Table Reference Object record, as defined in Section 5.5.2. 3296 Example of a "NNDN" element: 3298 ... 3299 3300 ... 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3313 NNDN-YYYYMMDD.csv 3314 3315 3316 3317 ... 3318 3319 ... 3321 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3322 contains two NNDN records for an IDN with one blocked variant and one 3323 mirrored variant. 3325 xn--abc456.test,LANG-1,xn--abc123.test, 3326 blocked,,2005-04-23T11:49:00.0Z 3327 xn--abc789.test,LANG-1,xn--abc123.test, 3328 mirrored,1,2005-04-23T11:49:00.0Z 3330 5.6.2.2. 3332 The is used to hold the deleted NNDN objects in a 3333 differential or incremental deposit. The is split 3334 into separate CSV file definitions using named elements 3335 with the "name" attribute. The following section defines the 3336 supported NNDN deletes CSV file definition. 3338 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3340 The following "NNDN" field elements MUST be used in the deletes 3341 "NNDN" element: 3343 ASCII Compatible Encoding (ACE) field of the NNDN 3344 with type="eppcom:labelType" and isRequired="true". 3346 Example of a "NNDN" element. 3348 ... 3349 3350 ... 3351 3352 3353 3354 3355 3356 3358 NNDN-delete-YYYYMMDD.csv 3359 3360 3361 3362 ... 3363 3364 ... 3366 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3367 contains one NNDN records. 3369 xn--abc456.test 3371 5.7. EPP Parameters Object 3373 The EPP Parameters Object is a pseudo-object that defines the set of 3374 object and object extension services supported by the registry, as 3375 defined in [RFC5730]. The EPP Parameters Object is only defined as 3376 XML but could be used in the XML model or CSV model. The EPP 3377 Parameters Object is defined using the 3378 element. The EPP Parameters Object SHOULD be included if the 3379 registry supports EPP. Only one EPP Parameters Object MUST exist at 3380 a certain point in time (watermark). 3382 The syntax and content of the children 3383 elements is as explained in section 2.4 of [RFC5730]. The children 3384 of the are as follows: 3386 o One or more elements that indicate the EPP versions 3387 supported by the registry. 3389 o One or more elements that indicate the identifiers of the 3390 text response languages supported by the registry's EPP server. 3392 o One or more elements that contain namespace URIs 3393 representing the objects that the registry's EPP server is capable 3394 of managing. 3396 o An OPTIONAL element that contains one or more 3397 elements that contain namespace URIs representing object 3398 extensions supported by the registry's EPP server. 3400 o A element that contains child elements used to describe the 3401 server's privacy policy for data collection and management. See 3402 section 2.4 of [RFC5730] for more details. 3404 Example of element object: 3406 ... 3407 3408 1.0 3409 en 3410 urn:ietf:params:xml:ns:domain-1.0 3411 3412 urn:ietf:params:xml:ns:contact-1.0 3413 3414 urn:ietf:params:xml:ns:host-1.0 3415 3416 3417 urn:ietf:params:xml:ns:rgp-1.0 3418 urn:ietf:params:xml:ns:secDNS-1.1 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 ... 3439 5.8. Policy Object 3441 The Policy object is a pseudo-object that is used to specify which 3442 OPTIONAL elements from the XML Model are REQUIRED based on the 3443 business model of the registry. For the CSV Model, the OPTIONAL 3444 "isRequired" attribute of the elements, defined in 3445 Section 4.7.1, is used to specify which OPTIONAL fields are REQUIRED 3446 based on the business model of the registry. 3448 5.8.1. object 3450 The OPTIONAL contains the following attributes: 3452 o An that defines that the referenced is 3453 REQUIRED. 3455 o that defines the XPath of the element referenced by 3456 . 3458 Example of object: 3460 ... 3461 3463 ... 3465 5.9. Header Object 3467 The Header Object is a pseudo-object that is used to specify the 3468 number of objects in the SRS at a specific point in time (watermark) 3469 regardless of the type of deposit: differential, full or incremental. 3470 The Header Object is only defined as XML but one header object MUST 3471 always be present per escrow deposit regardless of using XML Model or 3472 CSV Model. The Header Object is defined using the 3473 element. 3475 5.9.1. object 3477 The contains the following attributes: 3479 o A element that defines TLD being escrowed. 3481 o A element that contains the number of objects in the SRS 3482 at a specific point in time (watermark) regardless of the type of 3483 deposit: differential, full or incremental. The "uri" attributes 3484 reflects the XML namespace URI of the primary objects for the XML 3485 Model and CSV Model. For example, the "uri" is set to 3486 "urn:ietf:params:xml:ns:rdeDomain-1.0" for domain name objects 3487 using the XML Model, and the "uri" is set to 3488 "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name objects 3489 using the CSV Model. 3491 Example of object referencing only the XML Model 3492 objects: 3494 ... 3495 3496 test 3497 2 3499 1 3501 1 3503 1 3505 3506 1 3508 1 3510 1 3512 3513 3514 ... 3516 Example of object referencing the CSV and XML 3517 Model objects: 3519 ... 3520 3521 test 3522 2 3524 1 3526 1 3528 1 3530 3531 1 3533 1 3535 1 3537 3538 3539 ... 3541 6. RDE IDN Variants handling 3543 Depending on the Registration Policy of the Registry; for a domain 3544 name there may be multiple variant names. See [variantTLDsReport] 3545 for further detail on IDN variants. 3547 A registry could choose to escrow IDN variants as domains or NNDN 3548 objects. A specific IDN variant can be represented in the escrow 3549 deposit, as a domain or as a NNDN object, but not both. 3551 If using domain objects to represent IDN variants, the normal 3552 behavior during restoration of a SRS based on an escrow deposit is to 3553 restore the IDN variants as a mirrored variant. If the registration 3554 data of the IDN variant is different from the original name, the 3555 details of this specific implementation MUST be described in the IDN 3556 policy document. 3558 A NNDN or a domain name are explicit representations of an IDN 3559 variant while an IDN variant computed based on an algorithm is an 3560 implicit representation. Explicit representation of an IDN variant 3561 takes precedence over an implicit representation. 3563 7. Profile 3565 Different business models of registries exist, therefore the registry 3566 is responsible to define a profile that matches its particular 3567 business model. The profile mechanism allows a registry to extend 3568 this specification. 3570 A profile is the process of: 3572 1. Extending base objects with the mechanisms defined for XML and 3573 CSV models. 3575 * In the case of the XML model, abstract elements could be use 3576 to extend the following objects: , , , 3577 and using XML schema substitution groups 3578 feature. 3580 2. Defining a object to specify which OPTIONAL elements of 3581 this base specification is required based on the business model 3582 of the registry. An example is the element that is 3583 usually REQUIRED but it is specified as OPTIONAL in this 3584 specification to support existing business models. 3586 3. Adding new escrowed objects using the and 3587 elements. 3589 4. Providing the XML schemas to third parties that require them to 3590 validate the escrow deposits. 3592 8. Data escrow agent extended verification process 3594 The Data Escrow Agent MUST perform a extended verification process 3595 using the contents of the data escrow deposits to a point in time 3596 (watermark), last full plus all differentials or last full plus last 3597 incremental escrow deposits. The following are the minimum suggested 3598 tests: 3600 o Validate the escrow deposits using the definition agreed with the 3601 registry. 3603 * In the case of the XML model, the contents of the escrow 3604 deposits MUST be validated using the XML schemas of the 3605 profile. 3607 o Count the objects and validate that the number of objects is equal 3608 to the number objects reported in the
element of the 3609 escrow deposit of that point in time (watermark). 3611 o All contact objects linked to domain names MUST be present. 3613 o All registrars objects linked to other objects MUST be present. 3615 o A domain name exists as a domain name or NNDN, but not both. 3617 o The elements listed as required in the element MUST be 3618 present. 3620 o All idnTableRef definitions linked from other objects MUST be 3621 present. 3623 o If an EPP Parameters Object was escrowed in the past, one and only 3624 one EPP Parameters Object MUST be present. 3626 o The watermark is not in the future. 3628 9. Formal Syntax 3630 Schemas are presented here. 3632 9.1. RDE CSV Schema 3634 Copyright (c) 2012 IETF Trust and the persons identified as authors 3635 of the code. All rights reserved. 3637 Redistribution and use in source and binary forms, with or without 3638 modification, are permitted provided that the following conditions 3639 are met: 3641 o Redistributions of source code must retain the above copyright 3642 notice, this list of conditions and the following disclaimer. 3644 o Redistributions in binary form must reproduce the above copyright 3645 notice, this list of conditions and the following disclaimer in 3646 the documentation and/or other materials provided with the 3647 distribution. 3649 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3650 names of specific contributors, may be used to endorse or promote 3651 products derived from this software without specific prior written 3652 permission. 3654 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3655 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3656 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3657 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3658 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3659 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3660 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3661 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3662 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3663 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3664 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3666 BEGIN 3667 3669 3676 3679 3681 3684 3685 3686 Registry Data Escrow Comma-Seperated Values (CSV) 3687 3688 3690 3691 3693 3694 3695 3696 3697 3698 3699 3700 3701 3703 3704 3705 3706 3707 3708 3709 3711 3712 3715 3716 3717 3719 3720 3721 3722 3723 3724 3726 3728 3729 3730 3732 3733 3734 3735 3736 3737 3739 3741 3742 3743 3745 3747 3748 3750 3751 3752 3753 3754 3756 3757 3758 3759 3760 3761 3762 3763 3765 3766 3767 3769 3770 3772 3773 3774 3775 3776 3778 3779 3780 3782 3783 3785 3786 3787 3788 3789 3791 3792 3793 3795 3796 3800 3801 3802 3804 3806 3808 3809 3811 3813 3815 3816 3818 3820 3822 3824 3826 3828 3830 3832 3834 3835 3836 3837 3838 3840 3841 3842 3843 3844 3845 3846 3847 3850 3851 3852 3854 3855 3857 3859 3861 3862 3864 3865 3867 3869 3870 3871 3872 3873 3875 3876 3877 3878 3879 3880 3881 3882 3884 3885 3886 3888 3889 3890 3891 3892 3893 3895 3897 3898 3899 3900 3901 3902 3903 3905 3906 3907 3909 3910 3911 3912 3913 3914 3916 3917 3918 3919 3920 3921 3922 3923 3925 3926 3927 3929 3930 3931 3932 3933 3934 3936 3937 3938 3939 3940 3941 3942 3943 3946 3947 3948 3950 3951 3952 3953 3954 3955 3957 3958 3959 3960 3961 3962 3963 3964 3966 3967 3968 3970 3971 3973 3974 3975 3976 3977 3979 3980 3981 3983 3984 3987 3988 3990 3991 3992 3993 3994 3996 3997 3998 4000 4001 4002 4003 4004 4005 4007 4008 4009 4011 4012 4013 4014 4015 4016 4018 4019 4020 4022 4023 4024 4025 4026 4027 4029 4030 4031 4033 4034 4036 4037 4038 4039 4040 4041 4043 4044 4045 4047 4048 4049 4050 4051 4052 4054 4055 4056 4057 4059 4060 4062 4063 4064 4065 4066 4067 4069 4070 4071 4072 4074 4075 4077 4078 4079 4080 4081 4083 4084 4085 4087 4090 4091 END 4093 9.2. RDE Domain Object 4095 Copyright (c) 2011 IETF Trust and the persons identified as authors 4096 of the code. All rights reserved. 4098 Redistribution and use in source and binary forms, with or without 4099 modification, are permitted provided that the following conditions 4100 are met: 4102 o Redistributions of source code must retain the above copyright 4103 notice, this list of conditions and the following disclaimer. 4105 o Redistributions in binary form must reproduce the above copyright 4106 notice, this list of conditions and the following disclaimer in 4107 the documentation and/or other materials provided with the 4108 distribution. 4110 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4111 names of specific contributors, may be used to endorse or promote 4112 products derived from this software without specific prior written 4113 permission. 4115 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4116 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4117 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4118 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4119 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4120 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4121 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4122 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4123 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4124 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4125 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4127 BEGIN 4128 4129 4140 4141 4142 4143 4144 4145 4147 4148 4149 Registry Data Escrow Domain provisioning schema 4150 4151 4153 4156 4158 4162 4163 4164 4165 4166 4167 4169 4171 4173 4175 4177 4179 4182 4185 4188 4190 4192 4194 4196 4198 4200 4202 4204 4206 4209 4210 4211 4212 4214 4215 4216 4218 4220 4222 4224 4226 4228 4229 4231 4232 4233 4234 4235 4236 4239 4240 4241 4242 4243 4244 END 4246 9.3. CSV Domain Object 4248 Copyright (c) 2012 IETF Trust and the persons identified as authors 4249 of the code. All rights reserved. 4251 Redistribution and use in source and binary forms, with or without 4252 modification, are permitted provided that the following conditions 4253 are met: 4255 o Redistributions of source code must retain the above copyright 4256 notice, this list of conditions and the following disclaimer. 4258 o Redistributions in binary form must reproduce the above copyright 4259 notice, this list of conditions and the following disclaimer in 4260 the documentation and/or other materials provided with the 4261 distribution. 4263 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4264 names of specific contributors, may be used to endorse or promote 4265 products derived from this software without specific prior written 4266 permission. 4268 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4269 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4270 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4271 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4272 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4273 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4274 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4275 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4276 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4277 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4278 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4280 BEGIN 4281 4283 4294 4297 4299 4301 4303 4305 4307 4310 4311 4312 Domain Name Comma-Separated Values (CSV) Object 4313 4314 4316 4319 4322 4323 4324 4325 4326 4327 4328 4330 4331 4333 4336 4339 4340 4341 4342 4343 4344 4345 4346 4347 4349 4350 4353 4354 4357 4358 4359 4360 4361 4363 4364 4365 4367 4368 4371 4372 4373 4374 4375 4377 4378 4379 4381 4383 4384 4386 4387 4388 4389 4390 4392 4393 4394 4396 4397 4400 4401 4404 4405 4408 4409 4412 4413 4416 4417 4420 4421 4424 4425 4427 4428 4429 4430 4431 4433 4434 4435 4437 4438 4441 4442 4446 4447 4450 4451 4452 4453 4454 4455 4457 4458 4459 4461 4464 4465 END 4467 9.4. RDE Host Object 4469 Copyright (c) 2011 IETF Trust and the persons identified as authors 4470 of the code. All rights reserved. 4472 Redistribution and use in source and binary forms, with or without 4473 modification, are permitted provided that the following conditions 4474 are met: 4476 o Redistributions of source code must retain the above copyright 4477 notice, this list of conditions and the following disclaimer. 4479 o Redistributions in binary form must reproduce the above copyright 4480 notice, this list of conditions and the following disclaimer in 4481 the documentation and/or other materials provided with the 4482 distribution. 4484 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4485 names of specific contributors, may be used to endorse or promote 4486 products derived from this software without specific prior written 4487 permission. 4489 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4490 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4491 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4492 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4493 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4494 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4495 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4496 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4497 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4498 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4499 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4501 BEGIN 4502 4503 4511 4512 4513 4515 4516 4517 Registry Data Escrow Host provisioning schema 4518 4519 4520 4522 4523 4526 4527 4528 4529 4530 4531 4533 4535 4537 4540 4542 4544 4546 4548 4550 4552 4553 4554 4555 4557 4558 4559 4560 4561 4562 4564 4566 4567 4569 4570 4571 4572 END 4574 9.5. CSV Host Object 4576 Copyright (c) 2012 IETF Trust and the persons identified as authors 4577 of the code. All rights reserved. 4579 Redistribution and use in source and binary forms, with or without 4580 modification, are permitted provided that the following conditions 4581 are met: 4583 o Redistributions of source code must retain the above copyright 4584 notice, this list of conditions and the following disclaimer. 4586 o Redistributions in binary form must reproduce the above copyright 4587 notice, this list of conditions and the following disclaimer in 4588 the documentation and/or other materials provided with the 4589 distribution. 4591 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4592 names of specific contributors, may be used to endorse or promote 4593 products derived from this software without specific prior written 4594 permission. 4596 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4597 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4598 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4599 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4600 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4601 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4602 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4603 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4604 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4605 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4606 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4608 BEGIN 4609 4611 4620 4623 4625 4627 4629 4632 4633 4634 Host Comma-Separated Values (CSV) Object 4635 4636 4638 4641 4644 4645 4646 4647 4648 4649 4650 4651 4652 4654 4657 4660 4661 4662 4663 4664 4666 4667 4668 4669 4671 4672 4675 4676 4678 4679 4680 4681 4682 4684 4685 4686 4688 4689 4691 4692 4693 4694 4695 4697 4698 4699 4701 4702 4705 4706 4707 4708 4709 4710 4713 4714 4715 4717 4720 4721 END 4723 9.6. RDE Contact Object 4725 Copyright (c) 2011 IETF Trust and the persons identified as authors 4726 of the code. All rights reserved. 4728 Redistribution and use in source and binary forms, with or without 4729 modification, are permitted provided that the following conditions 4730 are met: 4732 o Redistributions of source code must retain the above copyright 4733 notice, this list of conditions and the following disclaimer. 4735 o Redistributions in binary form must reproduce the above copyright 4736 notice, this list of conditions and the following disclaimer in 4737 the documentation and/or other materials provided with the 4738 distribution. 4740 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4741 names of specific contributors, may be used to endorse or promote 4742 products derived from this software without specific prior written 4743 permission. 4745 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4746 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4747 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4748 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4749 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4750 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4751 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4752 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4753 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4754 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4755 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4757 BEGIN 4758 4759 4767 4768 4769 4770 4772 4773 4774 Registry Data Escrow contact provisioning schema 4775 4776 4778 4781 4783 4787 4788 4789 4790 4791 4792 4794 4796 4798 4800 4802 4804 4806 4808 4810 4812 4814 4816 4818 4820 4822 4823 4824 4825 4827 4828 4829 4830 4831 4832 4833 4834 4835 4837 4838 4839 4840 4841 4842 4845 4846 4847 4848 4849 4850 END 4852 9.7. CSV Contact Object 4854 Copyright (c) 2012 IETF Trust and the persons identified as authors 4855 of the code. All rights reserved. 4857 Redistribution and use in source and binary forms, with or without 4858 modification, are permitted provided that the following conditions 4859 are met: 4861 o Redistributions of source code must retain the above copyright 4862 notice, this list of conditions and the following disclaimer. 4864 o Redistributions in binary form must reproduce the above copyright 4865 notice, this list of conditions and the following disclaimer in 4866 the documentation and/or other materials provided with the 4867 distribution. 4869 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4870 names of specific contributors, may be used to endorse or promote 4871 products derived from this software without specific prior written 4872 permission. 4874 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4875 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4876 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4877 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4878 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4879 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4880 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4881 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4882 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4883 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4884 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4886 BEGIN 4887 4889 4898 4902 4904 4906 4908 4911 4912 4913 Contact Comma-Separated Values (CSV) Object 4914 4915 4917 4920 4923 4924 4925 4926 4927 4928 4929 4930 4931 4933 4936 4939 4940 4941 4942 4943 4944 4945 4946 4947 4949 4950 4952 4953 4954 4955 4956 4958 4959 4960 4962 4963 4967 4968 4970 4972 4973 4974 4975 4976 4978 4979 4980 4982 4983 4985 4988 4989 4991 4992 4993 4994 4995 4997 4998 4999 5001 5005 5007 5008 5009 5010 5011 5013 5014 5015 5017 5018 5019 5020 5021 5022 5024 5025 5026 5027 5029 5030 5031 5032 5033 5034 5036 5037 5038 5039 5040 5041 5044 5045 5048 5049 5050 5052 5053 5054 5055 5056 5058 5059 5060 5062 5063 5066 5067 5070 5071 5073 5074 5075 5076 5077 5079 5080 5081 5082 5084 5085 5087 5088 5089 5090 5091 5093 5094 5095 5096 5098 5099 5101 5103 5105 5107 5109 5111 5113 5115 5117 5119 5121 5123 5125 5127 5129 5131 5133 5135 5137 5139 5140 5141 5142 5143 5145 5146 5147 5149 5150 5153 5154 5155 5156 5157 5158 5160 5161 5162 5164 5167 5168 END 5170 9.8. RDE Registrar Object 5172 Copyright (c) 2011 IETF Trust and the persons identified as authors 5173 of the code. All rights reserved. 5175 Redistribution and use in source and binary forms, with or without 5176 modification, are permitted provided that the following conditions 5177 are met: 5179 o Redistributions of source code must retain the above copyright 5180 notice, this list of conditions and the following disclaimer. 5182 o Redistributions in binary form must reproduce the above copyright 5183 notice, this list of conditions and the following disclaimer in 5184 the documentation and/or other materials provided with the 5185 distribution. 5187 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5188 names of specific contributors, may be used to endorse or promote 5189 products derived from this software without specific prior written 5190 permission. 5192 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5193 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5194 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5195 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5196 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5197 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5198 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5199 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5200 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5201 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5202 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5204 BEGIN 5205 5206 5215 5216 5217 5218 5219 5221 5222 5223 Registry Data Escrow registrar provisioning schema 5224 5225 5227 5231 5233 5236 5237 5238 5239 5240 5241 5243 5245 5247 5249 5252 5254 5256 5258 5260 5262 5264 5266 5267 5268 5269 5271 5272 5273 5274 5275 5276 5278 5279 5280 5281 5282 5283 5284 5286 5287 5288 5290 5291 5294 5296 5297 5298 5299 5300 5301 5303 5304 5305 5308 5310 5313 5315 5317 5318 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5332 5333 5334 5335 5336 5338 5339 5340 5341 5342 5344 5345 5346 5348 5350 5351 5353 5354 5355 5356 5357 5358 5361 5362 5363 5364 5365 5366 END 5368 9.9. CSV Registrar Object 5370 Copyright (c) 2012 IETF Trust and the persons identified as authors 5371 of the code. All rights reserved. 5373 Redistribution and use in source and binary forms, with or without 5374 modification, are permitted provided that the following conditions 5375 are met: 5377 o Redistributions of source code must retain the above copyright 5378 notice, this list of conditions and the following disclaimer. 5380 o Redistributions in binary form must reproduce the above copyright 5381 notice, this list of conditions and the following disclaimer in 5382 the documentation and/or other materials provided with the 5383 distribution. 5385 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5386 names of specific contributors, may be used to endorse or promote 5387 products derived from this software without specific prior written 5388 permission. 5390 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5391 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5392 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5393 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5394 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5395 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5396 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5397 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5398 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5399 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5400 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5402 BEGIN 5403 5405 5415 5418 5420 5422 5424 5426 5429 5430 5431 Registar Comma-Separated Values (CSV) Object 5432 5433 5435 5438 5441 5442 5443 5444 5445 5446 5447 5448 5449 5451 5454 5457 5458 5459 5460 5461 5462 5463 5464 5465 5467 5468 5471 5472 5475 5476 5477 5478 5479 5480 5482 5483 5484 5485 5487 5488 5492 5493 5495 5497 5498 5499 5500 5501 5503 5504 5505 5507 5508 5509 5510 5511 5512 5513 5514 5515 5516 5517 5518 5519 5520 5521 5522 5524 5525 5529 5532 5533 END 5535 9.10. RDE IDN Table Reference Objects 5537 Copyright (c) 2011 IETF Trust and the persons identified as authors 5538 of the code. All rights reserved. 5540 Redistribution and use in source and binary forms, with or without 5541 modification, are permitted provided that the following conditions 5542 are met: 5544 o Redistributions of source code must retain the above copyright 5545 notice, this list of conditions and the following disclaimer. 5547 o Redistributions in binary form must reproduce the above copyright 5548 notice, this list of conditions and the following disclaimer in 5549 the documentation and/or other materials provided with the 5550 distribution. 5552 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5553 names of specific contributors, may be used to endorse or promote 5554 products derived from this software without specific prior written 5555 permission. 5557 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5558 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5559 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5560 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5561 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5562 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5563 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5564 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5565 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5566 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5567 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5569 BEGIN 5570 5571 5577 5579 5580 5581 Registry Data Escrow IDN provisioning schema 5582 5583 5585 5587 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5603 5604 5605 5606 5607 5608 5609 5611 5612 5614 5615 5616 5617 5618 5619 5620 5622 5623 END 5625 9.11. CSV IDN Language Object 5627 Copyright (c) 2012 IETF Trust and the persons identified as authors 5628 of the code. All rights reserved. 5630 Redistribution and use in source and binary forms, with or without 5631 modification, are permitted provided that the following conditions 5632 are met: 5634 o Redistributions of source code must retain the above copyright 5635 notice, this list of conditions and the following disclaimer. 5637 o Redistributions in binary form must reproduce the above copyright 5638 notice, this list of conditions and the following disclaimer in 5639 the documentation and/or other materials provided with the 5640 distribution. 5642 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5643 names of specific contributors, may be used to endorse or promote 5644 products derived from this software without specific prior written 5645 permission. 5647 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5648 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5649 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5650 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5651 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5652 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5653 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5654 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5655 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5656 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5657 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5659 BEGIN 5660 5662 5669 5672 5674 5677 5678 5679 IDN Language Comma-Separated Values (CSV) Object 5680 5681 5683 5686 5689 5690 5691 5692 5693 5694 5695 5696 5697 5699 5702 5705 5706 5707 5708 5709 5710 5711 5712 5713 5715 5718 5719 END 5721 9.12. EPP Parameters Object 5723 Copyright (c) 2011 IETF Trust and the persons identified as authors 5724 of the code. All rights reserved. 5726 Redistribution and use in source and binary forms, with or without 5727 modification, are permitted provided that the following conditions 5728 are met: 5730 o Redistributions of source code must retain the above copyright 5731 notice, this list of conditions and the following disclaimer. 5733 o Redistributions in binary form must reproduce the above copyright 5734 notice, this list of conditions and the following disclaimer in 5735 the documentation and/or other materials provided with the 5736 distribution. 5738 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5739 names of specific contributors, may be used to endorse or promote 5740 products derived from this software without specific prior written 5741 permission. 5743 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5744 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5745 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5746 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5747 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5748 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5749 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5750 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5751 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5752 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5753 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5755 BEGIN 5756 5757 5765 5766 5767 5769 5770 5771 Registry Data Escrow EPP Parameters schema 5772 5773 5775 5776 5779 5780 5783 5784 5785 5786 5787 5789 5791 5793 5796 5798 5799 5800 5801 5802 5803 END 5805 9.13. NNDN Object 5807 Copyright (c) 2011 IETF Trust and the persons identified as authors 5808 of the code. All rights reserved. 5810 Redistribution and use in source and binary forms, with or without 5811 modification, are permitted provided that the following conditions 5812 are met: 5814 o Redistributions of source code must retain the above copyright 5815 notice, this list of conditions and the following disclaimer. 5817 o Redistributions in binary form must reproduce the above copyright 5818 notice, this list of conditions and the following disclaimer in 5819 the documentation and/or other materials provided with the 5820 distribution. 5822 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5823 names of specific contributors, may be used to endorse or promote 5824 products derived from this software without specific prior written 5825 permission. 5827 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5828 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5829 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5830 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5831 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5832 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5833 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5834 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5835 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5836 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5837 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5839 BEGIN 5840 5841 5849 5850 5851 5853 5854 5855 Registry Data Escrow NNDN provisioning schema 5856 5857 5859 5861 5862 5865 5866 5867 5868 5869 5870 5872 5874 5876 5878 5880 5882 5883 5884 5885 5887 5888 5889 5890 5891 5892 5893 5895 5896 5897 5898 5900 5901 5902 5904 5905 5906 5907 5908 5909 5912 5913 5914 5915 5916 5917 END 5919 9.14. CSV NNDN Object 5921 Copyright (c) 2013 IETF Trust and the persons identified as authors 5922 of the code. All rights reserved. 5924 Redistribution and use in source and binary forms, with or without 5925 modification, are permitted provided that the following conditions 5926 are met: 5928 o Redistributions of source code must retain the above copyright 5929 notice, this list of conditions and the following disclaimer. 5931 o Redistributions in binary form must reproduce the above copyright 5932 notice, this list of conditions and the following disclaimer in 5933 the documentation and/or other materials provided with the 5934 distribution. 5936 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5937 names of specific contributors, may be used to endorse or promote 5938 products derived from this software without specific prior written 5939 permission. 5941 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5942 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5943 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5944 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5945 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5946 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5947 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5948 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5949 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5950 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5951 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5953 BEGIN 5954 5956 5964 5967 5969 5971 5974 5975 5976 NNDN (NNDN's not domain name) (CSV) Object 5977 5978 5980 5983 5986 5987 5988 5989 5990 5991 5992 5993 5994 5995 5998 6001 6002 6003 6004 6005 6006 6007 6008 6009 6011 6012 6015 6016 6019 6020 6024 6025 6028 6029 6030 6031 6032 6034 6035 6036 6038 6039 6042 6045 6046 END 6048 9.15. Policy Object 6050 Copyright (c) 2011 IETF Trust and the persons identified as authors 6051 of the code. All rights reserved. 6053 Redistribution and use in source and binary forms, with or without 6054 modification, are permitted provided that the following conditions 6055 are met: 6057 o Redistributions of source code must retain the above copyright 6058 notice, this list of conditions and the following disclaimer. 6060 o Redistributions in binary form must reproduce the above copyright 6061 notice, this list of conditions and the following disclaimer in 6062 the documentation and/or other materials provided with the 6063 distribution. 6065 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6066 names of specific contributors, may be used to endorse or promote 6067 products derived from this software without specific prior written 6068 permission. 6070 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6071 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6072 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6073 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6074 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6075 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6076 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6077 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6078 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6079 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6080 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6082 BEGIN 6083 6084 6090 6091 6092 Registry Data Escrow Policy schema 6093 6094 6096 6097 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 END 6111 9.16. Header Object 6113 Copyright (c) 2011 IETF Trust and the persons identified as authors 6114 of the code. All rights reserved. 6116 Redistribution and use in source and binary forms, with or without 6117 modification, are permitted provided that the following conditions 6118 are met: 6120 o Redistributions of source code must retain the above copyright 6121 notice, this list of conditions and the following disclaimer. 6123 o Redistributions in binary form must reproduce the above copyright 6124 notice, this list of conditions and the following disclaimer in 6125 the documentation and/or other materials provided with the 6126 distribution. 6128 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6129 names of specific contributors, may be used to endorse or promote 6130 products derived from this software without specific prior written 6131 permission. 6133 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6134 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6135 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6136 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6137 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6138 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6139 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6140 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6141 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6142 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6143 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6145 BEGIN 6146 6147 6154 6155 6157 6158 6159 Registry Data Escrow Header schema 6160 6161 6163 6164 6167 6168 6169 6170 6171 6172 6173 6175 6176 6177 6178 6180 6181 6182 6183 6184 6185 6186 6187 6188 END 6190 10. Internationalization Considerations 6192 Data Escrow deposits are represented in XML, which provides native 6193 support for encoding information using the Unicode character set and 6194 its more compact representations including UTF-8. Conformant XML 6195 processors recognize both UTF-8 and UTF-16. Though XML includes 6196 provisions to identify and use other character encodings through use 6197 of an "encoding" attribute in an declaration, use of UTF-8 is 6198 RECOMMENDED. 6200 11. IANA Considerations 6202 This document uses URNs to describe XML namespaces and XML schemas 6203 conforming to a registry mechanism described in [RFC3688]. Fourteen 6204 URI assignments have been registered by the IANA. 6206 Registration request for the RDE CSV namespace: 6208 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6210 Registrant Contact: See the "Author's Address" section of this 6211 document. 6213 XML: None. Namespace URIs do not represent an XML specification. 6215 Registration request for the RDE CSV XML schema: 6217 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6219 Registrant Contact: See the "Author's Address" section of this 6220 document. 6222 See the "Formal Syntax" section of this document. 6224 Registration request for the RDE domain namespace: 6226 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6228 Registrant Contact: See the "Author's Address" section of this 6229 document. 6231 XML: None. Namespace URIs do not represent an XML specification. 6233 Registration request for the RDE domain XML schema: 6235 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6236 Registrant Contact: See the "Author's Address" section of this 6237 document. 6239 See the "Formal Syntax" section of this document. 6241 Registration request for the CSV domain namespace: 6243 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6245 Registrant Contact: See the "Author's Address" section of this 6246 document. 6248 XML: None. Namespace URIs do not represent an XML specification. 6250 Registration request for the CSV domain XML schema: 6252 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6254 Registrant Contact: See the "Author's Address" section of this 6255 document. 6257 See the "Formal Syntax" section of this document. 6259 Registration request for the RDE host namespace: 6261 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6263 Registrant Contact: See the "Author's Address" section of this 6264 document. 6266 XML: None. Namespace URIs do not represent an XML specification. 6268 Registration request for the RDE host XML schema: 6270 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6272 Registrant Contact: See the "Author's Address" section of this 6273 document. 6275 See the "Formal Syntax" section of this document. 6277 Registration request for the CSV host namespace: 6279 URI: urn:ietf:params:xml:ns:csvHost-1.0 6281 Registrant Contact: See the "Author's Address" section of this 6282 document. 6284 XML: None. Namespace URIs do not represent an XML specification. 6286 Registration request for the CSV host XML schema: 6288 URI: urn:ietf:params:xml:schema:csvHost-1.0 6290 Registrant Contact: See the "Author's Address" section of this 6291 document. 6293 See the "Formal Syntax" section of this document. 6295 Registration request for the RDE contact namespace: 6297 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6299 Registrant Contact: See the "Author's Address" section of this 6300 document. 6302 XML: None. Namespace URIs do not represent an XML specification. 6304 Registration request for the RDE contact XML schema: 6306 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6308 Registrant Contact: See the "Author's Address" section of this 6309 document. 6311 See the "Formal Syntax" section of this document. 6313 Registration request for the CSV contact namespace: 6315 URI: urn:ietf:params:xml:ns:csvContact-1.0 6317 Registrant Contact: See the "Author's Address" section of this 6318 document. 6320 XML: None. Namespace URIs do not represent an XML specification. 6322 Registration request for the CSV contact XML schema: 6324 URI: urn:ietf:params:xml:schema:csvContact-1.0 6326 Registrant Contact: See the "Author's Address" section of this 6327 document. 6329 See the "Formal Syntax" section of this document. 6331 Registration request for the RDE registrar namespace: 6333 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6335 Registrant Contact: See the "Author's Address" section of this 6336 document. 6338 XML: None. Namespace URIs do not represent an XML specification. 6340 Registration request for the RDE registrar XML schema: 6342 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6344 Registrant Contact: See the "Author's Address" section of this 6345 document. 6347 See the "Formal Syntax" section of this document. 6349 Registration request for the CSV registrar namespace: 6351 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6353 Registrant Contact: See the "Author's Address" section of this 6354 document. 6356 XML: None. Namespace URIs do not represent an XML specification. 6358 Registration request for the CSV registrar XML schema: 6360 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6362 Registrant Contact: See the "Author's Address" section of this 6363 document. 6365 See the "Formal Syntax" section of this document. 6367 Registration request for the RDE IDN namespace: 6369 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6371 Registrant Contact: See the "Author's Address" section of this 6372 document. 6374 XML: None. Namespace URIs do not represent an XML specification. 6376 Registration request for the RDE IDN XML schema: 6378 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6379 Registrant Contact: See the "Author's Address" section of this 6380 document. 6382 See the "Formal Syntax" section of this document. 6384 Registration request for the CSV IDN namespace: 6386 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6388 Registrant Contact: See the "Author's Address" section of this 6389 document. 6391 XML: None. Namespace URIs do not represent an XML specification. 6393 Registration request for the CSV IDN XML schema: 6395 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6397 Registrant Contact: See the "Author's Address" section of this 6398 document. 6400 See the "Formal Syntax" section of this document. 6402 Registration request for the RDE NNDN namespace: 6404 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6406 Registrant Contact: See the "Author's Address" section of this 6407 document. 6409 XML: None. Namespace URIs do not represent an XML specification. 6411 Registration request for the RDE NNDN XML schema: 6413 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6415 Registrant Contact: See the "Author's Address" section of this 6416 document. 6418 See the "Formal Syntax" section of this document. 6420 Registration request for the CSV NNDN namespace: 6422 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6424 Registrant Contact: See the "Author's Address" section of this 6425 document. 6427 XML: None. Namespace URIs do not represent an XML specification. 6429 Registration request for the CSV NNDN XML schema: 6431 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6433 Registrant Contact: See the "Author's Address" section of this 6434 document. 6436 See the "Formal Syntax" section of this document. 6438 Registration request for the RDE EPP parameters namespace: 6440 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6442 Registrant Contact: See the "Author's Address" section of this 6443 document. 6445 XML: None. Namespace URIs do not represent an XML specification. 6447 Registration request for the RDE EPP parameters XML schema: 6449 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6451 Registrant Contact: See the "Author's Address" section of this 6452 document. 6454 See the "Formal Syntax" section of this document. 6456 12. Security Considerations 6458 This specification does not define the security mechanisms to be used 6459 in the transmission of the data escrow deposits, since it only 6460 specifies the minimum necessary to enable the rebuilding of a 6461 Registry from deposits without intervention from the original 6462 Registry. 6464 Depending on local policies, some elements or most likely, the whole 6465 deposit will be considered confidential. As such the Registry 6466 transmitting the data to the Escrow Agent SHOULD take all the 6467 necessary precautions like encrypting the data itself and/or the 6468 transport channel to avoid inadvertent disclosure of private data. 6470 It is also of the utmost importance the authentication of the parties 6471 passing data escrow deposit files. The Escrow Agent SHOULD properly 6472 authenticate the identity of the Registry before accepting data 6473 escrow deposits. In a similar manner, the Registry SHOULD 6474 authenticate the identity of the Escrow Agent before submitting any 6475 data. 6477 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6478 checking mechanisms to ensure the data transmitted is what the source 6479 intended. Validation of the contents by the Escrow Agent is 6480 RECOMMENDED to ensure not only the file was transmitted correctly 6481 from the Registry, but also the contents are also "meaningful". 6483 13. Acknowledgments 6485 Parts of this document are based on EPP [RFC5730] and related RFCs by 6486 Scott Hollenbeck. 6488 Shoji Noguchi and Francisco Arias participated as co-authors until 6489 version 05 providing invaluable support for this document. 6491 14. Change History 6493 [[RFC Editor: Please remove this section.]] 6495 14.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6496 dnrd-objects-mapping-00 6498 1. Added definition for child elements under the element. 6500 2. Added definition for child elements under the element. 6502 3. Added definition for child elements under the element. 6504 4. Rewrote the IDN Variants Handling section to use the variant 6505 states as described in ICANN's Study of Issues Related to the 6506 Management of IDN Variant TLDs. 6508 5. Renamed to in the . 6510 6. Renamed to in the element. 6512 7. Renamed to in the element. 6514 8. Added element under element. 6516 9. Fixed some typographical errors and omissions. 6518 14.2. Changes from version 00 to 01 6520 1. Specify OPTIONAL elements in the draft. 6522 2. Added NNDN object to support list of reserved names and different 6523 IDN variants models. 6525 3. Removed subordinated host element from the domain object. 6527 4. Added eppParams object. 6529 5. Added variantGenerator element to the domain object. 6531 6. Added lgr to the IDN table object. 6533 14.3. Changes from version 01 to 02 6535 1. Updates to the all objects based on feedback from the list. 6537 2. Start of XML and CSV drafts merge. 6539 3. Added header object. 6541 4. Added report object. 6543 5. Added notification object. 6545 6. Added Data Escrow Agent Extended Verification Process section. 6547 7. Added Notifications from Registries to Third Parties. 6549 8. Added Notifications from Data Escrow Agents to Third Parties. 6551 9. Added FULL, DIFF deposit examples using the XML model only. 6553 14.4. Changes from version 02 to 03 6555 1. Remove authinfo from the XML Schema. 6557 2. Resend attribute is now an element 6559 3. Scope attribute added to policy object. 6561 14.5. Changes from version 03 to 04 6563 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6564 arias-noguchi-dnrd-objects-mapping-02. 6566 2. Changed the cksum attribute of to use CRC32 and 6567 changed all of the sample cksum values to use CRC32, based on 6568 feedback from David Kipling. 6570 3. Changed the optional element to be an optional 6571 "sep" attribute value of the element with a default 6572 value of "," based on feedback from David Kipling. 6574 4. Added support for the optional "parent" attribute for the to the 6575 CSV fields to indicate a field as a reference to a parent 6576 object, based on feedback from David Kipling. 6578 5. Added support for the CSV model for the NNDN. 6580 6. Added support to delete hosts based on roid. 6582 7. Added mirrored state to NNDN 6584 8. Minor fixes to XML XSDs. 6586 9. The Report and Notification objects were moved to draft-lozano- 6587 icann-registry-interfaces 6589 10. The section Data escrow notifications was moved to draft-lozano- 6590 icann-registry-interfaces 6592 11. Removed references to the , , and 6593 from the "hostStatuses" and "hostAddresses" CSV 6594 files. 6596 12. Removed references to the , , and 6597 from the "contactStatuses" CSV file. 6599 13. Removed references to the , , and 6600 from the "domainContacts", "domainStatuses", 6601 and "domainNameServers" CSV files. 6603 14. Changed to . 6605 15. Replaced use of to new field 6606 in the "domain", "idnLanguage", and "NNDN" CSV files. 6608 16. Replaced use of with in the 6609 "host" element. 6611 17. Changed the foreign key of the hosts to use 6612 instead of and removed use of in 6613 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6614 files. 6616 18. Added use of the MUST keyword for CSV fields that are required 6617 to be supported in an EPP based system. 6619 19. Removed use of the field element for the 6620 "registrar" CSV file. 6622 20. Added definition of field element. 6624 14.6. Changes from version 04 to 05 6626 1. Updated the examples of the full and differential deposits using 6627 the CSV and XML model. 6629 2. Made optional for the "domainTransfer" CSV file 6630 to match the XML definition. 6632 3. Made optional for the "domain" CSV file 6633 to match the XML definition. 6635 4. Made optional for the "domain" and "contact" CSV 6636 files to match the XML definition. 6638 5. Change from IDREF to idType. 6640 6. Minor editorial changes. 6642 14.7. Changes from version 05 to 06 6644 1. Revised the differential and incremental deposits for the CSV 6645 format to use cascade update / replace and delete from the parent 6646 object to be consistent with the XML format. 6648 2. Revised the structure of the CSV format sections to utilize sub- 6649 sections instead of a list for the CSV file definitions. 6651 3. Added the "CSV Parent Child Relationship" section to describe the 6652 concept of parent child relationships across CSV file 6653 definitions. 6655 4. Added the "domainNameServersAddresses" CSV File Definition 6656 section to support the domain host attributes model of [RFC5731]. 6658 5. Made the required fields in the CSV format consistent with the 6659 XML format. The CSV fields updated to be required include: 6660 , , , 6661 , , , 6662 , , , 6663 , , , 6664 , , 6665 , , , 6666 , , 6667 , and . 6669 6. Revised the CSV examples to use a more realistic set of records. 6671 15. Example of a full deposit using the XML model 6673 Example of a full deposit using the XML model: 6675 6676 6692 2010-10-17T00:00:00Z 6693 6694 1.0 6695 urn:ietf:params:xml:ns:rdeHeader-1.0 6696 6697 urn:ietf:params:xml:ns:rdeContact-1.0 6698 6699 urn:ietf:params:xml:ns:rdeHost-1.0 6700 6701 urn:ietf:params:xml:ns:rdeDomain-1.0 6702 6703 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6704 6705 urn:ietf:params:xml:ns:rdeIDN-1.0 6706 6707 urn:ietf:params:xml:ns:rdeNNDN-1.0 6708 6709 urn:ietf:params:xml:ns:rdeEppParams-1.0 6710 6711 6713 6714 6715 6716 6717 test 6718 2 6720 6721 1 6723 6724 1 6726 6727 1 6729 6730 1 6732 6733 1 6735 6736 1 6738 6739 6741 6742 6743 example1.test 6744 Dexample1-TEST 6745 6746 jd1234 6747 sh8013 6748 sh8013 6749 6750 ns1.example.com 6751 ns1.example1.test 6752 6753 RegistrarX 6754 RegistrarX 6755 1999-04-03T22:00:00.0Z 6756 2015-04-03T22:00:00.0Z 6758 6760 6761 6762 example2.test 6763 Dexample2-TEST 6764 6765 6766 jd1234 6767 sh8013 6768 sh8013 6769 RegistrarX 6770 RegistrarX 6771 1999-04-03T22:00:00.0Z 6772 2015-04-03T22:00:00.0Z 6773 6775 6776 6777 ns1.example1.test 6778 Hns1_example_test-TEST 6779 6780 6781 192.0.2.2 6782 192.0.2.29 6783 1080:0:0:0:8:800:200C:417A 6784 6785 RegistrarX 6786 RegistrarX 6787 1999-05-08T12:10:00.0Z 6788 RegistrarX 6789 2009-10-03T09:34:00.0Z 6790 6792 6793 6794 sh8013 6795 Csh8013-TEST 6796 6797 6798 6799 John Doe 6800 Example Inc. 6801 6802 123 Example Dr. 6803 Suite 100 6804 Dulles 6805 VA 6806 20166-6503 6807 US 6808 6809 6810 +1.7035555555 6811 6812 +1.7035555556 6813 6814 jdoe@example.test 6815 6816 RegistrarX 6817 RegistrarX 6818 6819 2009-09-13T08:01:00.0Z 6820 6821 RegistrarX 6822 6823 2009-11-26T09:10:00.0Z 6824 6825 2009-12-03T09:05:00.0Z 6826 6827 6828 6829 6830 6831 6833 6834 6835 RegistrarX 6836 Registrar X 6837 123 6838 ok 6839 6840 6841 123 Example Dr. 6842 6843 Suite 100 6844 6845 Dulles 6846 VA 6847 20166-6503 6848 US 6849 6850 6851 +1.7035555555 6852 6853 +1.7035555556 6854 6855 jdoe@example.test 6856 6857 http://www.example.test 6858 6859 6860 whois.example.test 6861 6862 http://whois.example.test 6863 6864 6865 2005-04-23T11:49:00.0Z 6866 6867 2009-02-17T17:51:00.0Z 6868 6869 6871 6872 6873 6874 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 6875 6876 6877 http://registro.br/dominio/regras.html 6878 6879 6881 6882 6883 xn--exampl-gva.test 6884 pt-BR 6885 example1.test 6886 withheld 6887 2005-04-23T11:49:00.0Z 6888 6890 6891 6892 1.0 6893 en 6894 6895 urn:ietf:params:xml:ns:domain-1.0 6896 6897 6898 urn:ietf:params:xml:ns:contact-1.0 6899 6900 6901 urn:ietf:params:xml:ns:host-1.0 6903 6904 6905 urn:ietf:params:xml:ns:rgp-1.0 6906 6907 urn:ietf:params:xml:ns:secDNS-1.1 6908 6909 6910 6911 6912 6913 6914 6915 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925 6926 6927 6930 6931 6933 16. Example of differential deposit using the XML model 6935 Example of a differential deposit using the XML model: 6937 6938 6953 2010-10-17T00:00:00Z 6954 6955 1.0 6956 urn:ietf:params:xml:ns:rdeHeader-1.0 6957 6958 urn:ietf:params:xml:ns:rdeContact-1.0 6959 6960 urn:ietf:params:xml:ns:rdeHost-1.0 6961 6962 urn:ietf:params:xml:ns:rdeDomain-1.0 6963 6964 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6965 6966 urn:ietf:params:xml:ns:rdeIDN-1.0 6967 6968 urn:ietf:params:xml:ns:rdeNNDN-1.0 6969 6970 urn:ietf:params:xml:ns:rdeEppParams-1.0 6971 6972 6974 6975 6976 6977 example2.test 6978 6979 6981 6982 6983 6984 6985 test 6986 1 6988 6989 1 6991 6992 1 6994 6995 1 6997 6998 1 7000 7001 1 7003 7004 1 7006 7007 7008 7009 7011 17. Example of a full deposit using the CSV model 7013 Example of a full deposit using the CSV model: 7015 7016 7030 2010-10-18T00:00:00Z 7031 7032 1.0 7033 urn:ietf:params:xml:ns:csvDomain-1.0 7034 urn:ietf:params:xml:ns:csvHost-1.0 7035 urn:ietf:params:xml:ns:csvContact-1.0 7036 urn:ietf:params:xml:ns:csvRegistrar-1.0 7037 urn:ietf:params:xml:ns:csvIDN-1.0 7038 urn:ietf:params:xml:ns:csvNNDN-1.0 7039 urn:ietf:params:xml:ns:rdeEppParams-1.0 7040 7041 7042 7043 test 7044 7045 4 7046 7047 7048 6 7049 7050 7051 9 7052 7053 7054 3 7055 7056 7057 2 7058 7059 7060 2 7061 7062 7063 1 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7081 7082 7083 7084 7086 domain-YYYYMMDD.csv 7087 7088 7089 7090 7091 7092 7093 7094 7096 7097 7098 7100 domainContacts-YYYYMMDD.csv 7101 7102 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7115 domainStatuses-YYYYMMDD.csv 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7127 domainNameServers-name-YYYYMMDD.csv 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7139 domainNameServers-roid-YYYYMMDD.csv 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7155 dnssec-ds-YYYYMMDD.csv 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7171 dnssec-key-YYYYMMDD.csv 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7190 domainTransfer-YYYYMMDD.csv 7191 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7213 host-YYYYMMDD.csv 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7227 hostStatuses-YYYYMMDD.csv 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7240 hostAddresses-YYYYMMDD.csv 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7267 contact-YYYYMMDD.csv 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 7281 contactStatuses-YYYYMMDD.csv 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7302 contactPostal-YYYYMMDD.csv 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7320 contactTransfer-YYYYMMDD.csv 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7341 contactDisclose-YYYYMMDD.csv 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7373 registrar-YYYYMMDD.csv 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7387 idnLanguage-YYYYMMDD.csv 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7405 NNDN-YYYYMMDD.csv 7406 7407 7408 7409 7410 7411 1.0 7412 en 7413 urn:ietf:params:xml:ns:domain-1.0 7414 7415 urn:ietf:params:xml:ns:host-1.0 7416 7417 urn:ietf:params:xml:ns:contact-1.0 7418 7419 7420 urn:ietf:params:xml:ns:secDNS-1.1 7421 7422 urn:ietf:params:xml:ns:rgp-1.0 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7450 18. Example of differential deposit using the CSV model 7452 Example of a differential deposit using the CSV model: 7454 7455 7469 2010-10-18T00:00:00Z 7470 7471 1.0 7472 urn:ietf:params:xml:ns:csvDomain-1.0 7473 urn:ietf:params:xml:ns:csvHost-1.0 7474 urn:ietf:params:xml:ns:csvContact-1.0 7475 urn:ietf:params:xml:ns:csvRegistrar-1.0 7476 urn:ietf:params:xml:ns:csvIDN-1.0 7477 7478 7479 7480 7481 7482 7484 7485 7486 7488 domain-delete-YYYYMMDD.csv 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7501 host-delete-YYYYMMDD.csv 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7514 contact-delete-YYYYMMDD.csv 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7527 registrar-delete-YYYYMMDD.csv 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7540 idnLanguage-delete-YYYYMMDD.csv 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7553 NNDN-delete-YYYYMMDD.csv 7554 7555 7556 7557 7558 7559 7560 7561 test 7562 7563 2 7564 7565 7566 2 7567 7568 7569 3 7570 7571 7572 1 7573 7574 7575 1 7576 7577 7578 1 7579 7580 7581 1 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7604 domain-YYYYMMDD.csv 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7617 domainContacts-YYYYMMDD.csv 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7629 7630 7631 7633 domainStatuses-YYYYMMDD.csv 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7645 domainNameServers-name-YYYYMMDD.csv 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7657 domainNameServers-roid-YYYYMMDD.csv 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7673 dnssec-ds-YYYYMMDD.csv 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7689 dnssec-key-YYYYMMDD.csv 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7708 domainTransfer-YYYYMMDD.csv 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7730 host-YYYYMMDD.csv 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7744 hostStatuses-YYYYMMDD.csv 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7757 hostAddresses-YYYYMMDD.csv 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7783 contact-YYYYMMDD.csv 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7797 contactStatuses-YYYYMMDD.csv 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7818 contactPostal-YYYYMMDD.csv 7819 7820 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7837 contactTransfer-YYYYMMDD.csv 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7858 contactDisclose-YYYYMMDD.csv 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7890 registrar-YYYYMMDD.csv 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7904 idnLanguage-YYYYMMDD.csv 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7919 7920 7921 7923 NNDN-YYYYMMDD.csv 7924 7925 7926 7927 7928 7929 1.0 7930 en 7931 urn:ietf:params:xml:ns:domain-1.0 7932 7933 urn:ietf:params:xml:ns:host-1.0 7934 7935 urn:ietf:params:xml:ns:contact-1.0 7936 7937 7938 urn:ietf:params:xml:ns:secDNS-1.1 7939 7940 urn:ietf:params:xml:ns:rgp-1.0 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7967 19. References 7969 19.1. Normative References 7971 [ISO-3166-1] 7972 International Organization for Standardization, "Codes for 7973 the representation of names of countries and their 7974 subdivisions -- Part 1: Country codes", ISO Standard 3166, 7975 November 2006. 7977 [ITU-E164] 7978 International Telecommunication Union, "The international 7979 public telecommunication numbering plan", ITU-T 7980 Recommendation E.164, February 2005. 7982 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 7983 Requirement Levels", BCP 14, RFC 2119, 7984 DOI 10.17487/RFC2119, March 1997, 7985 . 7987 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 7988 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 7989 . 7991 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 7992 the Extensible Provisioning Protocol (EPP)", RFC 3915, 7993 DOI 10.17487/RFC3915, September 2004, 7994 . 7996 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 7997 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 7998 . 8000 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8001 Domain Name Mapping", STD 69, RFC 5731, 8002 DOI 10.17487/RFC5731, August 2009, 8003 . 8005 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8006 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8007 August 2009, . 8009 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8010 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8011 August 2009, . 8013 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8014 Security Extensions Mapping for the Extensible 8015 Provisioning Protocol (EPP)", RFC 5910, 8016 DOI 10.17487/RFC5910, May 2010, 8017 . 8019 19.2. Informative References 8021 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8022 DOI 10.17487/RFC0791, September 1981, 8023 . 8025 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8026 DOI 10.17487/RFC3688, January 2004, 8027 . 8029 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8030 DOI 10.17487/RFC3912, September 2004, 8031 . 8033 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8034 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8035 2006, . 8037 [variantTLDsReport] 8038 Internet Corporation for Assigned Names and Numbers 8039 (ICANN), "A Study of Issues Related to the Management of 8040 IDN Variant TLDs", February 2012, 8041 . 8044 19.3. URIs 8046 [1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data- 8047 escrow-05.txt 8049 Authors' Addresses 8051 Gustavo Lozano 8052 Internet Corporation for Assigned Names and Numbers 8053 12025 Waterfront Drive, Suite 300 8054 Los Angeles 90292 8055 United States of America 8057 Phone: +1.310.823.9358 8058 Email: gustavo.lozano@icann.org 8059 James Gould 8060 VeriSign, Inc. 8061 12061 Bluemont Way 8062 Reston 20190 8063 United States of America 8065 Email: jgould@verisign.com 8067 Chethan Thippeswamy 8068 VeriSign, Inc. 8069 12061 Bluemont Way 8070 Reston 20190 8071 United States of America 8073 Email: cthippeswamy@verisign.com