idnits 2.17.1 draft-arias-noguchi-dnrd-objects-mapping-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 6 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 (July 31, 2013) is 3922 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' == Outdated reference: A later version (-11) exists of draft-arias-noguchi-registry-data-escrow-05 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group F. Arias 3 Internet-Draft G. Lozano 4 Intended status: Standards Track ICANN 5 Expires: February 1, 2014 S. Noguchi 6 JPRS 7 J. Gould 8 C. Thippeswamy 9 VeriSign 10 July 31, 2013 12 Domain Name Registration Data (DNRD) Objects Mapping 13 draft-arias-noguchi-dnrd-objects-mapping-04 15 Abstract 17 This document specifies the format, contents and semantics of Domain 18 Name Registration Data (DNRD) Escrow deposits for a Domain Name 19 Registry. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on February 1, 2014. 38 Copyright Notice 40 Copyright (c) 2013 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 56 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 58 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6 59 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 60 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6 61 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 62 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6 63 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6 64 4.6. CSV elements . . . . . . . . . . . . . . . . . . . . . . 6 65 4.7. Internationalized and Localized Elements . . . . . . . . 11 66 5. Object Description . . . . . . . . . . . . . . . . . . . . . 13 67 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 13 68 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 35 69 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 44 70 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 63 71 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 71 72 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 74 73 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 79 74 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 81 75 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 81 76 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 83 77 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 78 8. Data escrow agent extended verification process . . . . . . . 84 79 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 85 80 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 85 81 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 93 82 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 97 83 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 101 84 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 103 85 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 106 86 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 109 87 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116 88 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 120 89 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 124 90 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 125 91 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 127 92 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 129 93 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 132 94 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 134 95 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 135 97 10. Internationalization Considerations . . . . . . . . . . . . . 138 98 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 138 99 12. Security Considerations . . . . . . . . . . . . . . . . . . . 143 100 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 144 101 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 144 102 14.1. Changes from 103 draft-arias-noguchi-registry-data-escrow-02 to 104 -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . 144 105 14.2. Changes from version 00 to 01 . . . . . . . . . . . . . . 145 106 14.3. Changes from version 01 to 02 . . . . . . . . . . . . . . 145 107 14.4. Changes from version 02 to 03 . . . . . . . . . . . . . . 145 108 14.5. Changes from version 03 to 04 . . . . . . . . . . . . . . 145 109 15. Example of a full deposit using the XML model . . . . . . . . 147 110 16. Example of differential deposit using the XML model . . . . . 152 111 17. Example of a full deposit using the CSV model . . . . . . . . 154 112 18. Example of differential deposit using the CSV model . . . . . 163 113 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 177 114 19.1. Normative References . . . . . . . . . . . . . . . . . . 177 115 19.2. Informative References . . . . . . . . . . . . . . . . . 177 116 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 178 118 1. Introduction 120 This document defines the data escrow structure of the standard set 121 of objects for a Domain Name Registry which include: 123 o Domain: Internet domain names that are typically provisioned in a 124 Domain Name Registry using the EPP domain name mapping [RFC5731]. 125 The attributes defined in the EPP domain name mapping [RFC5731] 126 are fully supported by this document. 128 o Host: Internet host names that are typically provisioned in a 129 Domain Name Registry using the EPP host mapping [RFC5732]. The 130 attributes defined in the EPP host mapping [RFC5732] are fully 131 supported by this document. 133 o Contact: Individual or organization social information provisioned 134 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 135 The attributes defined in the EPP contact mapping [RFC5733] are 136 fully supported by this document. 138 o Registrar: The organization that sponsors objects like domains, 139 hosts, and contacts in a Domain Name Registry. 141 o NNDN (NNDN's not domain name): A lightweight domain-like object 142 that is not linked to a Registrar. 144 This document defines the following pseudo-objects: 146 o IDN Table Reference: Internationalized Domain Names (IDN) included 147 in the Domain Object Data Escrow include references to the IDN 148 Table and Policy used in IDN registration. 150 o EPP parameters: Definition of the specific EPP parameters 151 supported by the Registry Operator. 153 o Header: Used to specify counters of objects in the database at a 154 certain point in time (watermark). 156 o Policy: Used to specify OPTIONAL elements from this specification 157 that are REQUIRED based on the business model of the registry. 159 2. Models 161 This document defines two different models that can be used to 162 deposit data escrow objects: 164 o XML: The XML model includes all of the deposit information (meta- 165 data and data) in an XML document. The definition of the XML 166 format is fully defined in the XML schemas. As a convention, the 167 objects represented using the XML model are referenced using RDE 168 and an XML namespace that is prefixed with "rde". For example, 169 the Domain Name object represented using the XML model can be 170 referred to as the RDE Domain Name with the XML namespace 171 including rdeDomain (urn:ietf:params:xml:ns:rdeDomain-1.0). 173 o CSV: The CSV model uses XML to define the data escrow format of 174 the data contained in referenced Comma-Separated Values (CSV) 175 files. As a convention, the objects represented using the CSV 176 model are referenced using CSV and an XML namespace that is 177 prefixed with "csv". For example, the Domain Name object 178 represented using the CSV model can be referred to as the CSV 179 Domain Name with the XML namespace including csvDomain 180 (urn:ietf:params:xml:ns:csvDomain-1.0). 182 The data escrow deposit MAY contain a mix of both models but an 183 object MUST be escrowed only in one model. 185 3. Terminology 187 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 188 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 189 document are to be interpreted as described in BCP 14, [RFC2119]. 191 REGISTRY. In the context of this draft the definition will be 192 overloaded (from the definition in the base protocol) to indicate an 193 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 194 NAME. 196 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 197 or any other domain name at any level in the DNS tree for which a 198 Registry (either directly or through and affiliate company) provides 199 Registry Services for other organizations or individuals. For 200 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 202 REGISTRY SERVICES. Services offered by the Registry critical to the 203 following tasks: the provisioning of domain names on receipt of 204 requests and data from registrars; responding to registrar queries 205 for status information relating to the DNS servers for the RCDN; 206 dissemination of RCDN zone files; operation of the Registry DNS 207 servers; and responding to queries for contact and other information 208 concerning DNS registrations in the RCDN. Any other products or 209 services that only a Registry is capable of providing, by reason of 210 its designation as the Registry. Typical examples of Registry 211 Services are: DNS resolution for the RCDN, WHOIS and EPP. 213 ALLOCATED. A status of some label with respect to a zone, whereby 214 the label is associated administratively to some entity that has 215 requested the label. This term (and its cognates "allocation" and 216 "to allocate") may represents the first step on the way to delegation 217 in the DNS. 219 4. General Conventions 221 4.1. Date and Time 223 Numerous fields indicate "dates", such as the creation and expiry 224 dates for domain names. These fields SHALL contain timestamps 225 indicating the date and time in UTC as specified in [RFC3339], with 226 no offset from the zero meridian. 228 4.2. Country names 230 Country identifiers SHALL be represented using two character 231 identifiers as specified in [ISO-3166-1]. 233 4.3. Telephone numbers 235 Telephone numbers (both voice and facsimile) SHALL be formatted based 236 on structures defined in [ITU-E164]. Telephone numbers described in 237 this specification are character strings that MUST begin with a plus 238 sign ("+", ASCII value 0x002B), followed by a country code defined in 239 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 240 a sequence of digits representing the telephone number. 242 4.4. Checksum 244 Checksum of the CSV data escrow files MUST use CRC32, that is the 245 algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of 246 ITU-T recommendation V.42. 248 4.5. IP addresses 250 IP addresses syntax MUST conform to the text representation of either 251 of, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 252 Addressing Architecture [RFC4291], for IPv6 addresses. 254 4.6. CSV elements 255 4.6.1. element 257 To support a CSV model with the Registry Data Escrow 258 Specification [1], an element is defined for each object that 259 substitutes for the element and for the 260 element, that contains one or more elements. For 261 example, the Domain Name Object (Section 5.1) defines the element, that substitutes for the element, 263 and the element, that substitutes for the element. Both the element and the 265 elements contain one or more 266 elements. The element has the following child elements: 268 Ordered list of CSV fields used in the CSV files. 269 There is one or more child elements that substitute for the 270 abstract element. Each element defines the format 271 of the CSV field contained in the CSV files. The 272 elements support the "type" attribute that defines the XML simple 273 data type of the field element. The elements 274 support the "isRequired" attribute, with a default value of 275 "false", when set to "true" indicates that the field must be non- 276 empty in the CSV files and when set to "false" indicates that the 277 field MAY be empty in the CSV files. The "isRequired" attribute 278 MAY be specifically set for the field elements within the XML 279 schema and MAY be overridden when specifying the fields under the 280 element. The element supports an 281 OPTIONAL "parent" attribute that identifies the field as a 282 reference to a parent object. For example, the field SHOULD set the 284 "parent" attribute to "true" to identify it as the parent domain 285 name of the domain status. 287 A list of one or more CSV files using the child element. The child element defines a 289 reference to the CSV file name and has the following optional 290 attributes: 292 compression If the CSV file is compressed, the "compression" 293 attribute defines the compression format like "gzip" or "zip". 295 encoding Defines the encoding of the CSV file with the default 296 encoding of "UTF-8". 298 cksum Defines the checksum of the CSV file using CRC32, as 299 defined in Section 4.4. This attribute is used to validate 300 that the full CSV file exists and has not been tampered with. 302 The elements requires a "name" attribute that defines 303 the purpose of the CSV file with values like "domain", "host", 304 "contact". The supported "name" attribute values are defined for 305 each object type. The OPTIONAL "sep" attribute defines the CSV 306 separator character with the default separator character of ",". 308 The following is an example of the 309 element for domain name records where the is set 310 as required with isRequired="true". 312 313 ... 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 333 domain-YYYYMMDD.csv 334 335 336 337 ... 338 340 The following is example of the "domain-YYYYMMDD.csv" file with one 341 record matching the definition. 343 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 344 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 345 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 347 The following is an example of the 348 element for domain name records. 350 351 ... 352 353 354 355 356 357 359 domain-delete-YYYYMMDD.csv 360 361 362 363 ... 364 366 The following is example of the "domain-delete-YYYYMMDD.csv" file 367 with three records that matches the single field. 369 domain1.test 370 domain2.test 371 domainN.test 373 4.6.2. CSV common field elements 375 The element defined in the element 376 (Section 4.6.1) section has child elements that substitute for the 377 abstract element. By convention 378 elements include an 'f' prefix to identify them as field definition 379 elements. There are a set of common field elements that are used 380 across multiple data escrow objects. The common field elements are 381 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 382 using the "rdeCsv" sample namespace prefix. The CSV common field 383 elements include: 385 UTF-8 encoded name field with type="eppcom: 386 labelType". 388 Repository Object IDentifier (ROID) field with 389 type="eppcom:roidType" and isRequired="true". 391 Registrant contact identifier with 392 type="eppcom:clIDType". 394 The object status description, which is 395 free form text describing the rationale for the status, with 396 type="normalizedString". 398 Identifier of client (registrar) that sponsors the 399 object with type="eppcom:clIDType" and isRequired="true". 401 Identifier of the registrar, defined in Section 5.4, 402 of the client that created the object with type="eppcom:clIDType". 404 Identifier of client that created the object with 405 type="eppcom:clIDType". 407 Identifier of the registrar, defined in Section 5.4, 408 of the client that updated the object with type="eppcom:clIDType". 410 Identifier of client that updated the object with 411 type="eppcom:clIDType". 413 Identifier of the registrar, defined in Section 5.4, 414 of the client that requested the transfer with type="eppcom: 415 clIDType". 417 Identifier of client that requested the transfer with 418 type="eppcom:clIDType". 420 Identifier of the registrar, defined in Section 5.4, 421 of the client that should take or took action with type="eppcom: 422 clIDType". 424 Identifier of client that should take or took action 425 for transfer with type="eppcom:clIDType". 427 Created date of object with type="dateTime". 429 Updated date of object with type="dateTime". 431 Expiration date of object with type="dateTime". 433 Date that transfer was requested with 434 type="dateTime". 436 Date that transfer action should be taken or has 437 been taken with type="dateTime". 439 Date of last transfer with type="dateTime". 441 State of the most recent transfer request with 442 type="eppcom:trStatusType". 444 General token field with type="token". 446 General language field with type="language". 448 IDN Table Identifier used for IDN domain names 449 with type="token". 451 General positive integer field with 452 type="positiveInteger". 454 Contains the URL of an object like a registrar object 455 with type="anyURI". 457 Custom field with name attribute that defines the 458 custom field name" with type="token". 460 4.7. Internationalized and Localized Elements 462 Some elements MAY be provided in either internationalized form 463 ("int") or provided in localized form ("loc"). Those elements use a 464 field value or "isLoc" attribute to specify the form used. If an 465 "isLoc" attribute is used, a value of "true" indicates the use of the 466 localized form and a value of "false" indicates the use of the 467 internationalized form. This MAY override the form specified for a 468 parent element. A value of "int" is used to indicate the 469 internationalized form and a value of "loc" is used to indicate the 470 localized form. When the internalized form ("int") is provided, the 471 field value MUST be represented in a subset of UTF-8 that can be 472 represented in the 7-bit US-ASCII character set. When the localized 473 form ("loc") is provided, the field value MAY be represented in 474 unrestricted UTF-8. Some of the field elements below of the 475 "registrar" element specify the 476 internationalized form with the isLoc="false" attribute: 478 ... 479 480 ... 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 512 registrar-YYYYMMDD.csv 513 514 515 516 ... 517 518 ... 520 The following is an example of using the 521 field value to define the internationalized or localized form of the 522 remainder of the "contactPostal" field values. 524 ... 525 526 ... 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 544 contactPostal-YYYYMMDD.csv 545 546 547 548 ... 549 550 ... 552 5. Object Description 554 This section describes the base objects supported by this 555 specification: 557 5.1. Domain Name Object 559 The domain name object is based on the EPP domain name mapping 560 specified in [RFC5731]. The domain name object supports both the XML 561 Model and the CSV Model, defined in the Models (Section 2) section. 562 The elements used for both models are defined in the following 563 sections. 565 5.1.1. XML Model 567 There are two elements used in the data escrow of the domain name 568 objects for the XML model including the , under the 569 element, and the element, under the 570 element. 572 5.1.1.1. object 574 The domain element is based on the EPP domain response for an 575 authorized client (see Section 3.1.2. of [RFC5731]) with additional 576 data from an EPP Query Response, see Section 3.1.3. of 577 [RFC5731], RGP status from [RFC3915], and data from the EPP command, see Section 5.2.1. of [RFC5910]. 580 A element substitutes for the abstract 581 element to define a concrete definition of a domain. The 582 element can be replaced by other domain definitions 583 using the XML schema substitution groups feature. 585 The element contains the following child elements: 587 o A element that contains the fully qualified name of the 588 domain name object. 590 o A element that contains the repository object identifier 591 assigned to the domain name object when it was created. 593 o An OPTIONAL element that contains the name of the domain 594 name in Unicode character set. It MUST be provided if available. 596 o An OPTIONAL element that references the IDN Table 597 used for the IDN. This corresponds to the "id" attribute of the 598 element. This element MUST be present if the domain 599 name is an IDN. 601 o An OPTIONAL element is used to indicate that the 602 domain name is an IDN variant. This element contains the domain 603 name used to generate the IDN variant. 605 o One or more elements that contain the current status 606 descriptors associated with the domain name. 608 o Zero or more OPTIONAL element to represent 609 "pendingDelete" sub-statuses, including "redemptionPeriod", 610 "pendingRestore", and "pendingDelete", that a domain name can be 611 in as a result of grace period processing as specified in 612 [RFC3915]. 614 o An OPTIONAL element that contain the identifier for 615 the human or organizational social information object associated 616 as the holder of the domain name object. 618 o Zero or more OPTIONAL elements that contain identifiers 619 for the human or organizational social information objects 620 associated with the domain name object. 622 o An OPTIONAL element that contains the fully qualified names 623 of the delegated host objects or host attributes (name servers) 624 associated with the domain name object. See Section 1.1 of 625 [RFC5731] for a description of the elements used to specify host 626 objects or host attributes. 628 o A element that contains the identifier of the sponsoring 629 registrar. 631 o A element that contains the identifier of the registrar 632 that created the domain name object. An OPTIONAL client attribute 633 is used to specify the client that performed the operation. 635 o An OPTIONAL element that contains the date and time of 636 the domain name object creation. This element MUST be present if 637 the domain name has been allocated. 639 o An OPTIONAL element that contains the date and time 640 identifying the end (expiration) of the domain name object's 641 registration period. This element MUST be present if the domain 642 name has been allocated. 644 o An OPTIONAL element that contains the identifier of the 645 registrar that last updated the domain name object. This element 646 MUST NOT be present if the domain has never been modified. An 647 OPTIONAL client attribute is used to specify the client that 648 performed the operation. 650 o An OPTIONAL element that contains the date and time of 651 the most recent domain-name-object modification. This element 652 MUST NOT be present if the domain name object has never been 653 modified. 655 o An OPTIONAL element that contains the public key 656 information associated with Domain Name System security (DNSSEC) 657 extensions for the domain name as specified in [RFC5910]. 659 o An OPTIONAL element that contains the date and time of 660 the most recent domain object successful transfer. This element 661 MUST NOT be present if the domain name object has never been 662 transfered. 664 o An OPTIONAL element that contains the following child 665 elements related to the last transfer request of the domain name 666 object. This element MUST NOT be present if a transfer request 667 for the domain name has never been created. 669 * A element that contains the state of the most recent 670 transfer request. 672 * A element that contains the identifier of the registrar 673 that requested the domain name object transfer. An OPTIONAL 674 client attribute is used to specify the client that performed 675 the operation. 677 * A element that contains the date and time that the 678 transfer was requested. 680 * An element that contains the identifier of the registrar 681 that SHOULD act upon a PENDING transfer request. For all other 682 status types, the value identifies the registrar that took the 683 indicated action. An OPTIONAL client attribute is used to 684 specify the client that performed the operation. 686 * An element that contains the date and time of a 687 required or completed response. For a PENDING request, the 688 value identifies the date and time by which a response is 689 required before an automated response action will be taken by 690 the registry. For all other status types, the value identifies 691 the date and time when the request was completed. 693 * An OPTIONAL element that contains the end of the 694 domain name object's validity period (expiry date) if the 695 transfer caused or causes a change in the validity period. 697 Example of a domain object: 699 ... 700 701 example1.test 702 Dexample1-TEST 703 704 jd1234 705 sh8013 706 sh8013 707 708 ns1.example.com 709 ns1.example1.test 710 711 RegistrarX 712 RegistrarX 713 1999-04-03T22:00:00.0Z 714 2015-04-03T22:00:00.0Z 715 716 ... 718 5.1.1.2. object 720 The element contains the fully qualified domain 721 name that was deleted and purged. 723 Example of object: 725 ... 726 727 ... 728 729 foo.test 730 bar.test 731 732 ... 733 734 ... 736 5.1.2. CSV Model 738 For the CSV Model of the domain name object, the 739 child element of the element is used to hold the new 740 or updated domain name objects for the deposit. The child element of the element is used to hold 742 the deleted or purged domain name objects for the deposit. Both the 743 and elements contain one or 744 more elements with the following supported "name" 745 attribute values: 747 "domain" Defines the fields and CSV file references used for the 748 domain name object records. 750 The following "csvDomain" field elements, defined for the "domain" 751 element, MUST be used in the "domain" 752 element: 754 Domain name field with type="eppcom:labelType" 755 and isRequired="true". 757 Fully qualified name of the original 758 IDN domain name object related to the variant domain name 759 object with type="eppcom:labelType". 761 The following "rdeCsv" fields, defined in section CSV common field 762 elements (Section 4.6.2), MUST be used in the "domain" element: 765 Registry Object IDentifier (ROID) for the domain 766 name object. 768 Identifier of client that sponsors the domain name 769 object. 771 Identifier of the registrar, defined in 772 Section 5.4, of the client that created the object. 774 Created date and time of the domain name object. 776 Identifier of the registrar, defined in 777 Section 5.4, of the client that updated the object. 779 Date and time of the last update to the domain 780 name object. 782 Expiration date and time for the domain name 783 object. 785 Date and time of the last transfer for the 786 domain name object. 788 The following "rdeCsv" fields, defined in section CSV common field 789 elements (Section 4.6.2), MAY be used in the "domain" 790 element: 792 UTF8 encoded domain name for the field element. 795 IDN Table Identifier used for the IDN domain 796 name object that MUST match a field 797 element in the "idnLanguage" CSV files, as defined in 798 Section 5.5.2. 800 Registrant contact identifier for the domain 801 name object. 803 Identifier of client that created the domain name 804 object. 806 Identifier of the client that last updated the 807 domain name object. 809 Example of a "domain" element: 811 ... 812 813 ... 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 833 domain-YYYYMMDD.csv 834 835 836 837 ... 838 839 ... 841 Example of the corresponding domain-YYYYMMDD.csv file. The file 842 contains four records (active ASCII domain, pendingDelete domain, 843 original IDN with LANG1 language rules, and variant IDN with LANG1 844 language rules). 846 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 847 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 848 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 849 domain2.test,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 850 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 851 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 852 xn--abc123.test,Dxnabc123-TEST,LANG1,,registrantid,registrarX, 853 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 854 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 855 xn--abc321.test,Dxnabc321-TEST,LANG1,xn--cbc321.test, 856 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 857 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 859 Example of a "domain" element: 861 ... 862 863 ... 864 865 866 867 868 869 871 domain-delete-YYYYMMDD.csv 872 873 874 875 ... 876 877 ... 879 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 880 file contains three domain name records. 882 domain1.test 883 domain2.test 884 domainN.test 885 "domainContacts" Defines the fields and CSV file references used for 886 the domain name object link records to contact objects, as 887 described in Section 5.3. 889 The following "csvDomain" field elements, defined for the 890 "domainContacts" element, MUST be 891 used in the "domainContacts" element: 893 The contact type for the contact object 894 link with type="domain:contactAttrType". The supported contact 895 type values include "admin" for the administration contact, 896 "billing" for the billing contact, and "tech" for the technical 897 contact. 899 The following "csvDomain" field elements, defined for the "domain" 900 element, MUST be used in the 901 "domainContacts" element: 903 The name of the domain object that is linked to 904 the contact object. 906 The following "csvContact" fields, defined for the "contact" 907 element, MUST be used in the 908 "domainContacts" element: 910 The server-unique contact identifier. 912 Example of a "domainContacts" 913 element: 915 ... 916 917 ... 918 919 920 921 922 923 924 925 927 domainContacts-YYYYMMDD.csv 928 929 930 931 ... 932 933 ... 935 Example of the corresponding domainContacts-YYYYMMDD.csv file. 936 The file contains an admin, tech, and billing contact for the two 937 domain names domain1.test and domain2.test. 939 domain1.test,sh8013,admin 940 domain1.test,mycontactid,tech 941 domain1.test,mycontactid,billing 942 domain2.test,mycontactid,admin 943 domain2.test,sh8013,tech 944 domain2.test,mycontactid,billing 946 Example of a "domainContacts" 947 element: 949 ... 950 951 ... 952 953 954 955 956 957 958 959 961 domainContacts-delete-YYYYMMDD.csv 962 963 964 965 ... 966 967 ... 969 Example of the corresponding domainContacts-delete-YYYYMMDD.csv 970 file. The file contains two tech contact records. 972 domain1.test,mycontactid,tech 973 domain2.test,sh8013,tech 975 "domainStatuses" Defines the fields and CSV file references used for 976 the domain name object statuses. 978 The following "csvDomain" field elements, defined for the 979 "domainStatuses" element, MUST be 980 used in the "domainStatuses" element: 982 The status of the domain name with 983 type="domain:statusValueType". 985 The Registry Grace Period (RGP) status, as 986 a sub-status of the "pendingDelete" status 987 value, with type="rgp:statusValueType" as defined in [RFC3915]. 989 The following "csvDomain" fields, defined for the "domain" 990 element, MUST be used in the 991 "domainStatuses" element: 993 Domain name of status. 995 The following "rdeCsv" fields, defined in section CSV common field 996 elements (Section 4.6.2), MAY be used in the "domainStatuses" 997 element: 999 Domain object status description 1000 which is free form text describing the rationale for the 1001 status. 1003 Language of the field. 1005 Example of a "domainStatuses" 1006 element: 1008 ... 1009 1010 ... 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1022 domainStatuses-YYYYMMDD.csv 1023 1024 1025 1026 ... 1027 1028 ... 1030 Example of the corresponding domainStatuses-YYYYMMDD.csv file. 1031 The file contains the statuses for the two domain names 1032 domain1.test and domain2.test. 1034 domain1.test,clientUpdateProhibited,"Disallow update", 1035 en, 1036 domain1.test,clientDeleteProhibited,"Disallow delete", 1037 en, 1038 domain2.test,clientUpdateProhibited,"Disallow update", 1039 en, 1040 domain2.test,pendingDelete,,, 1041 redemptionPeriod 1043 Example of a "domainStatuses" 1044 element: 1046 ... 1047 1048 ... 1049 1050 1051 1052 1053 1054 1055 1057 domainStatuses-delete-YYYYMMDD.csv 1058 1059 1060 1061 ... 1062 1063 ... 1065 Example of the corresponding domainStatuses-delete-YYYYMMDD.csv 1066 file. The file contains two status records. 1068 domain1.test,clientUpdateProhibited 1069 domain2.test,pendingDelete 1070 "domainNameServers" Defines the fields and CSV file references used 1071 for the domain name delegated hosts (name servers). The 1072 "domainNameServers" CSV files define the relationship between a 1073 domain name object and a delegated host. To support both the 1074 and the model, defined in 1075 [RFC5731], the host field element is used to 1076 reference the host. 1078 The following "csvDomain" fields, defined for the "domain" 1079 element, MUST be used in the 1080 "domainNameServers" element: 1082 Domain name using the delegated host with host 1083 . 1085 The following "rdeCsv" fields, defined in section CSV common field 1086 elements (Section 4.6.2), MUST be used in the "domainNameServers" 1087 element: 1089 Registry Object IDentifier (ROID) used to uniquely 1090 reference a delegated host record. 1092 Example of a "domainNameServers" 1093 element. 1095 ... 1096 1097 ... 1098 1099 1100 1101 1102 1103 1104 1106 domainNameServers-YYYYMMDD.csv 1107 1108 1109 1110 ... 1111 1112 ... 1114 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1115 The file contains the delegated hosts (name servers) for the two 1116 domain names domain1.test and domain2.test referenced via the 1117 field element. 1119 domain1.test,Dns1domain2test-TEST 1120 domain1.test,Dns2domain2test-TEST 1121 domain2.test,Dns1domainexample-TEST 1122 domain2.test,Dns2domainexample-TEST 1124 Example of a "domainNameServers" 1125 element. 1127 ... 1128 1129 ... 1130 1131 1132 1133 1134 1135 1136 1138 domainNameServers-delete-YYYYMMDD.csv 1139 1140 1141 1142 ... 1143 1144 ... 1146 Example of the corresponding domainNameServers-delete-YYYYMMDD.csv 1147 file. The file contains two records. 1149 domain1.test,Dns1domain2test-TEST 1150 domain1.test,Dns2domain2test-TEST 1151 domain2.test,Dns1domainexample-TEST 1152 domain2.test,Dns2domainexample-TEST 1153 "dnssec" Defines the fields and CSV file references used for the 1154 domain name object DNSSEC records (DS or Key Data). 1156 The following "csvDomain" field elements, defined for the "dnssec" 1157 element, MUST be used in the "dnssec" 1158 rdeCsv:fields> element when the DS Data Interface per 1159 [RFC5910] is used: 1161 Contains the DS key tag value per [RFC5910] 1162 with type="unsignedShort". 1164 Contains the DS algorithm value per [RFC5910] 1165 with type="unsignedByte". 1167 Contains the DS digest type value per 1168 [RFC5910] with type="unsignedByte". 1170 Contains the DS digest value per [RFC5910] 1171 with type="hexBinary". 1173 The following "csvDomain" field elements, defined for the "dnssec" 1174 element, MUST be used in the "dnssec" 1175 rdeCsv:fields> element when the Key Data Interface 1176 per [RFC5910] is used: 1178 Contains the flags field value per [RFC5910] 1179 with type="unsignedShort". 1181 Contains the Key protocol value per 1182 [RFC5910] with type="unsignedByte". 1184 Contains the Key algorithm value per 1185 [RFC5910] with type="unsignedByte". 1187 Contains the public key value per [RFC5910] 1188 with type="secDNS:keyType". 1190 The following "csvDomain" field elements, defined for the "dnssec" 1191 element, MAY be used in the "dnssec" 1192 rdeCsv:fields> element: 1194 Indicates a child's preference for the 1195 number of seconds after signature generation when the parent's 1196 signature on the DS information provided by the child will 1197 expire with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1199 The following "domain" fields, defined for the "domain" element, MUST be used in the "dnssec" 1201 element: 1203 Domain name of the domain object associated 1204 with the DNSSEC record. 1206 Example of a "dnssec" element 1207 with the DS Data Interface of [RFC5910]: 1209 1210 ... 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1223 dnssec-ds-YYYYMMDD.csv 1224 1225 1226 1227 ... 1228 1229 ... 1231 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The 1232 file contains two DS records for domain1.test. 1234 domain1.test,604800,12345,3,1,49FD46E6C4B45C55D4AC 1235 domain1.test,604800,12346,3,1,38EC35D5B3A34B44C39B 1237 Example of a "dnssec" element 1238 with the Key Data Interface of [RFC5910]: 1240 1241 ... 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1254 dnssec-key-YYYYMMDD.csv 1255 1256 1257 1258 ... 1259 1260 ... 1262 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The 1263 file contains two key records for domain1.test. 1265 domain1.test,604800,257,3,1,AQPJ////4Q== 1266 domain1.test,604800,257,3,1,AQPJ////4QQQ 1268 Example of a "dnssec" element 1269 with the DS Data Interface of [RFC5910]: 1271 ... 1272 1273 ... 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1285 dnssec-ds-delete-YYYYMMDD.csv 1286 1287 1288 1289 ... 1290 1291 ... 1293 Example of the corresponding dnssec-ds-delete-YYYYMMDD.csv file. 1294 The file contains two DS records for domain1.test. 1296 domain1.test,12345,3,1,49FD46E6C4B45C55D4AC 1297 domain1.test,12346,3,1,38EC35D5B3A34B44C39B 1299 Example of a "dnssec" element 1300 with the Key Data Interface of [RFC5910]: 1302 ... 1303 1304 ... 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1316 dnssec-key-delete-YYYYMMDD.csv 1317 1318 1319 1320 ... 1321 1322 ... 1324 Example of the corresponding dnssec-key-delete-YYYYMMDD.csv file. 1325 The file contains two key records for domain1.test. 1327 domain1.test,257,3,1,AQPJ////4Q== 1328 domain1.test,257,3,1,AQPJ////4QQQ 1330 "domainTransfer" Defines the fields and CSV file references used for 1331 the domain name object pending and completed transfer records. No 1332 additional field elements were added for use in the 1333 "domainTransfer" element. 1335 The following "rdeCsv" fields, defined in section CSV common field 1336 elements (Section 4.6.2), MUST be used in the "domainTransfer" 1337 element: 1339 State of the most recent transfer request. 1341 Identifier of the registrar, defined in 1342 Section 5.4, of the client that requested the transfer. 1344 Date and time that the transfer was requested. 1346 Identifier of the registrar, defined in 1347 Section 5.4, of the client that should take or took action. 1349 Date and time that the transfer action should be 1350 taken or has been taken. 1352 Expiration date if the transfer command caused 1353 or causes a change in the validity period. 1355 The following "rdeCsv" fields, defined in section CSV common field 1356 elements (Section 4.6.2), MAY be used in the "domainTransfer" 1357 element: 1359 Identifier of client that requested the transfer. 1361 Identifier of client that should take or took 1362 action for transfer. 1364 The following "csvDomain" fields, defined for the "domain" 1365 element, MUST be used in the 1366 "domainTransfer" element: 1368 Domain name of the domain object involved in 1369 the transfer. 1371 Example of a "domainTransfer" 1372 element: 1374 ... 1375 1376 ... 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1392 domainTransfer-YYYYMMDD.csv 1393 1394 1395 1396 ... 1397 1398 ... 1400 Example of the corresponding domainTransfer-YYYYMMDD.csv file. 1401 The file contains two domain transfer records, with one in pending 1402 status and the second in clientApproved status. 1404 domain1.test,pending,registrarX,clientY, 1405 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1406 2016-04-03T22:00:00.0Z 1407 domain2.test,clientApproved,registrarX,clientY, 1408 2012-03-08T19:38:00.0Z,registrarY,clientY, 1409 2012-03-09T23:59:59.0Z,2016-05-04T23:00:00.0Z 1411 Example of a "domainTransfer" 1412 element: 1414 ... 1415 1416 ... 1417 1418 1419 1420 1421 1422 1423 1425 domainTransfer-delete-YYYYMMDD.csv 1426 1427 1428 1429 ... 1430 1431 ... 1433 Example of the corresponding domainTransfer-delete-YYYYMMDD.csv 1434 file. The file contains two domain transfer records. 1436 domain1.test,2011-03-08T19:38:00.0Z 1437 domain2.test,2012-03-08T19:38:00.0Z 1439 5.2. Host Object 1441 The host object is based on the EPP host name mapping in [RFC5732]. 1442 The host object supports both the XML Model and the CSV Model, 1443 defined in Models (Section 2) section. The elements used for both 1444 models are defined in the following sections. 1446 5.2.1. XML Model 1448 There are two elements used in the data escrow of the host objects 1449 for the XML model including the , under the element, and the element, under the element. 1453 A element substitutes for the 1454 abstract element to define a concrete definition of a host. The 1455 element can be replaced by other host 1456 definitions using the XML schema substitution groups feature. 1458 5.2.1.1. element 1460 The RDE host object is based on the EPP host response for an 1461 authorized client (Section 3.1.2. of [RFC5732]). 1463 The OPTIONAL element contains the following child elements: 1465 o A element that contains the fully qualified name of the 1466 host object. 1468 o A element that contains the repository object identifier 1469 assigned to the host object when the object was created. 1471 o One or more elements that describe the status of the host 1472 object. 1474 o Zero or more elements that contain the IP addresses 1475 associated with the host object. 1477 o A element that contains the identifier of the sponsoring 1478 registrar. 1480 o A element that contains the identifier of the registrar 1481 that created the host object. An OPTIONAL client attribute is 1482 used to specify the client that performed the operation. 1484 o A element that contains the date and time of host-object 1485 creation. 1487 o An OPTIONAL element that contains the identifier of the 1488 registrar that last updated the host object. This element MUST 1489 NOT be present if the host object has never been modified. An 1490 OPTIONAL client attribute is used to specify the client that 1491 performed the operation. 1493 o An OPTIONAL element that contains the date and time of 1494 the most recent host-object modification. This element MUST NOT 1495 be present if the host object has never been modified. 1497 o An OPTIONAL element that contains the date and time of 1498 the most recent host object successful transfer. This element 1499 MUST NOT be present if the domain name object has never been 1500 transfered. 1502 Example of object: 1504 ... 1505 1506 ns1.example1.test 1507 Hns1_example_test-TEST 1508 1509 1510 192.0.2.2 1511 192.0.2.29 1512 1080:0:0:0:8:800:200C:417A 1513 RegistrarX 1514 RegistrarX 1515 1999-05-08T12:10:00.0Z 1516 RegistrarX 1517 2009-10-03T09:34:00.0Z 1518 1519 ... 1521 5.2.1.2. object 1523 The element contains the fully qualified domain name 1524 of a host that was deleted. The element also 1525 supports host removal based on roid to support SRS systems in which 1526 different hosts with the same fully qualified domain name are active 1527 at the same time. 1529 Example of object: 1531 ... 1532 1533 ... 1534 1535 ns1.example.test 1536 1537 ... 1538 1539 ... 1541 5.2.1.3. CSV Model 1543 For the CSV Model of the host object, the child 1544 element of the element is used to hold the new or 1545 updated host objects for the deposit. The child 1546 element of the element is used to hold the deleted or 1547 purged host objects for the deposit. Both the and 1548 elements contain one or more elements 1549 with the following supported "name" attribute values: 1551 "host" Defines the fields and CSV file references used for the host 1552 object records. 1554 The following "csvHost" field elements, defined for the "host" 1555 element, MUST be used in the "host" 1556 element: 1558 Host name field with type="eppcom:labelType" and 1559 isRequired="true". 1561 The following "rdeCsv" fields, defined in section CSV common field 1562 elements (Section 4.6.2), MUST be used in the "host" 1563 element: 1565 Repository Object IDentifier (ROID) assigned to 1566 the host object. 1568 The following "rdeCsv" fields, defined in section CSV common field 1569 elements (Section 4.6.2), MAY be used in the "host" 1570 element: 1572 Identifier of the sponsoring client. 1574 Identifier of the registrar, defined in 1575 Section 5.4, of the client that created the object. 1577 Identifier of client that created the host object. 1579 Date and time that the host object was created. 1581 Identifier of the registrar, defined in 1582 Section 5.4, of the client that updated the object. 1584 Identifier of client that last updated the host 1585 object. 1587 Date and time that the host object was last 1588 updated. 1590 Date and time that the host was last 1591 transferred. 1593 Example of a "host" element: 1595 ... 1596 1597 ... 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1614 host-YYYYMMDD.csv 1615 1616 1617 1618 ... 1619 1620 ... 1622 Example of the corresponding host-YYYYMMDD.csv file. The file 1623 contains two host records with one being an internal host and the 1624 second being an external host. 1626 ns1.example.test,Hns1_example_test-TEST,registrarX,registrarX, 1627 clientY,1999-05-08T12:10:00.0Z,registrarX, 1628 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1629 ns1.example.test2,Hns1_example_test2-TEST,clientY, 1630 clientX,2009-05-08T12:10:00.0Z,clientX, 1631 2010-10-03T09:34:00.0Z, 1632 Example of a "host" element: 1634 ... 1635 1636 ... 1637 1638 1639 1640 1641 1642 1644 host-delete-YYYYMMDD.csv 1645 1646 1647 1648 ... 1649 1650 ... 1652 Example of the host-delete-YYYYMMDD.csv file. The file contains 1653 two host records. 1655 Hns1_example_test-TEST 1656 Hns1_example_test2-TEST 1658 "hostStatuses" Defines the fields and CSV file references used for 1659 the host object statuses. 1661 The following "csvHost" fields, defined for the "host" element, MUST be used in the "hostStatuses" 1663 element: 1665 The status of the host with type="host: 1666 statusValueType"/>. 1668 The following "rdeCsv" fields, defined in section CSV common field 1669 elements (Section 4.6.2), MUST be used in the "hostStatuses" 1670 element: 1672 Host object Registry Object IDentifier (ROID) 1673 assigned to the host object. 1675 The following "rdeCsv" fields, defined in section CSV common field 1676 elements (Section 4.6.2), MAY be used in the "hostStatuses" 1677 element: 1679 Host object status description which 1680 is free form text describing the rationale for the status. 1682 Language of the field. 1684 Example of a "hostStatuses" 1685 element: 1687 ... 1688 1689 ... 1690 1691 1692 1693 1694 1695 1696 1697 1698 1700 hostStatuses-YYYYMMDD.csv 1701 1702 1703 1704 ... 1705 1706 ... 1708 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1709 file contains the statuses for the two host names ns1.domain1.test 1710 and ns1.domain2.test. 1712 ns1domain1test-TEST,clientUpdateProhibited,"Disallow update",en 1713 ns1domain1test-TEST,clientDeleteProhibited,"Disallow delete",en 1714 ns1domain2test-TEST,ok,, 1716 Example of a "hostStatuses" 1717 element: 1719 ... 1720 1721 ... 1722 1723 1724 1725 1726 1727 1728 1730 hostStatuses-delete-YYYYMMDD.csv 1731 1732 1733 1734 ... 1735 1736 ... 1738 Example of the corresponding hostStatuses-delete-YYYYMMDD.csv 1739 file. The file contains two status records. 1741 ns1domain1test-TEST,clientUpdateProhibited 1742 ns1domain1test-TEST,clientDeleteProhibited 1744 "hostAddresses" Defines the fields and CSV file references used for 1745 the host object IP addresses. 1747 The following "csvHost" field elements, defined for the 1748 "hostAddresses" rdeCsv:fields> element, MUST be used 1749 in the "hostAddresses" element: 1751 IP addresses associated with the host object with 1752 type="host:addrStringType". 1754 IP addresses version associated with the 1755 host object with type="host:ipType". "host:ipType" has the 1756 enumerated values of "v4" or "v6". 1758 The following "rdeCsv" fields, defined in section CSV common field 1759 elements (Section 4.6.2), MUST be used in the "hostAddresses" 1760 element: 1762 Host object Registry Object IDentifier (ROID) 1763 assigned to the host object. 1765 Example of a "hostAddresses" 1766 element. 1768 ... 1769 1770 ... 1771 1772 1773 1774 1775 1776 1777 1778 1780 hostAddresses-YYYYMMDD.csv 1781 1782 1783 1784 ... 1785 1786 ... 1788 Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. 1789 The file contains the IP addresses for the host name 1790 ns1.domain1.test. 1792 ns1domain1test-TEST,192.0.2.2,v4 1793 ns1domain1test-TEST,192.0.2.29,v4 1794 ns1domain1test-TEST,1080:0:0:0:8:800:200C:417A,v6 1796 Example of a "hostAddresses" 1797 element: 1799 ... 1800 1801 ... 1802 1803 1804 1805 1806 1807 1808 1810 hostAddresses-delete-YYYYMMDD.csv 1811 1812 1813 1814 ... 1815 1816 ... 1818 Example of the corresponding hostAddresses-delete-YYYYMMDD.csv 1819 file. The file contains three IP address records. 1821 ns1domain1test-TEST,192.0.2.2 1822 ns1domain1test-TEST,192.0.2.29 1823 ns1domain1test-TEST,1080:0:0:0:8:800:200C:417A 1825 5.3. Contact Object 1827 The contact object is based on the EPP contact name mapping in 1828 [RFC5733]. The contact object supports both the XML Model and the 1829 CSV Model, defined in Models (Section 2) section. The elements used 1830 for both models are defined in the following sections. 1832 5.3.1. XML Model 1834 There are two elements used in the data escrow of the contact objects 1835 for the XML model including the , under the 1836 element, and the element, 1837 under the element. 1839 A element substitutes for the abstract 1840 element to define a concrete definition of a contact. The 1841 element can be replaced by other contact 1842 definitions using the XML schema substitution groups feature. 1844 5.3.1.1. object 1846 The contact object is based on the EPP contact response for an 1847 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1848 including the data from an EPP Query Response, see Section 1849 3.1.3. of [RFC5733]. 1851 The OPTIONAL element contains the following child elements: 1853 o A element that contains the server-unique identifier of the 1854 contact object 1856 o A element that contains the Repository Object IDentifier 1857 assigned to the contact object when the object was created. 1859 o One or more elements that describe the status of the 1860 contact object. 1862 o One or two elements that contain postal-address 1863 information. Two elements are provided so that address 1864 information can be provided in both internationalized and 1865 localized forms; a "type" attribute is used to identify the two 1866 forms. If an internationalized form (type="int") is provided, 1867 element content MUST be represented in a subset of UTF-8 that can 1868 be represented in the 7-bit US-ASCII character set. If a 1869 localized form (type="loc") is provided, element content MAY be 1870 represented in unrestricted UTF-8. The element 1871 contains the following child elements: 1873 * A element that contains the name of the individual or 1874 role represented by the contact. 1876 * An OPTIONAL element that contains the name of the 1877 organization with which the contact is affiliated. 1879 * An element that contains address information associated 1880 with the contact. An element contains the following 1881 child elements: 1883 + One, two, or three OPTIONAL elements that contain 1884 the contact's street address. 1886 + A element that contains the contact's city. 1888 + An OPTIONAL element that contains the contact's state 1889 or province. 1891 + An OPTIONAL element that contains the contact's postal 1892 code. 1894 + A element that contains the contact's two-letter 1895 country code. 1897 o An OPTIONAL element that contains the contact's voice 1898 telephone number. 1900 o An OPTIONAL element that contains the contact's facsimile 1901 telephone number. 1903 o An element that contains the contact's email address. 1905 o A element that contains the identifier of the sponsoring 1906 registrar. 1908 o A element that contains the identifier of the registrar 1909 that created the contact object. An OPTIONAL client attribute is 1910 used to specify the client that performed the operation. 1912 o A element that contains the date and time of contact- 1913 object creation. 1915 o An OPTIONAL element that contains the identifier of the 1916 registrar that last updated the contact object. This element MUST 1917 NOT be present if the contact has never been modified. An 1918 OPTIONAL client attribute is used to specify the client that 1919 performed the operation. 1921 o An OPTIONAL element that contains the date and time of 1922 the most recent contact-object modification. This element MUST 1923 NOT be present if the contact object has never been modified. 1925 o An OPTIONAL element that contains the date and time of 1926 the most recent contact object successful transfer. This element 1927 MUST NOT be present if the contact object has never been 1928 transferred. 1930 o An OPTIONAL element that contains the following child 1931 elements related to the last transfer request of the contact 1932 object: 1934 * A element that contains the state of the most recent 1935 transfer request. 1937 * A element that contains the identifier of the registrar 1938 that requested the domain name object transfer. An OPTIONAL 1939 client attribute is used to specify the client that performed 1940 the operation. 1942 * An element that contains the identifier of the registrar 1943 that SHOULD act upon a PENDING transfer request. For all other 1944 status types, the value identifies the registrar that took the 1945 indicated action. An OPTIONAL client attribute is used to 1946 specify the client that performed the operation. 1948 * A element that contains the date and time that the 1949 transfer was requested. 1951 * An element that contains the date and time of a 1952 required or completed response. For a PENDING request, the 1953 value identifies the date and time by which a response is 1954 required before an automated response action will be taken by 1955 the registry. For all other status types, the value identifies 1956 the date and time when the request was completed. 1958 o An OPTIONAL element that identifies elements that 1959 requiring exceptional server-operator handling to allow or 1960 restrict disclosure to third parties. See Section 2.9 of 1961 [RFC5733] for a description of the child elements contained within 1962 the element. 1964 Example object: 1966 ... 1967 1968 Csh8013-TEST 1969 sh8013 1970 1971 1972 1973 John Doe 1974 Example Inc. 1975 1976 123 Example Dr. 1977 Suite 100 1978 Dulles 1979 VA 1980 20166-6503 1981 US 1982 1983 1984 +1.7035555555 1985 +1.7035555556 1986 jdoe@example.test 1987 RegistrarX 1988 RegistrarX 1989 2009-09-13T08:01:00.0Z 1990 RegistrarX 1991 2009-11-26T09:10:00.0Z 1992 2009-12-03T09:05:00.0Z 1993 1994 pending 1995 clientW 1996 2011-03-08T19:38:00.0Z 1997 RegistrarX 1998 2011-03-13T23:59:59.0Z 1999 2000 2001 2002 2003 2004 2005 ... 2007 5.3.1.2. object 2009 The element contains the id of a contact that was 2010 deleted. 2012 Example of object: 2014 ... 2015 2016 ... 2017 2018 sh8013-TEST 2019 co8013-TEST 2020 2021 ... 2022 2023 ... 2025 5.3.2. CSV Model 2027 For the CSV Model of the contact object, the 2028 child element of the element is used to hold the new 2029 or updated contact objects for the deposit. The 2030 child element of the element is used to hold the 2031 deleted or purged contact objects for the deposit. Both the 2032 and elements contain one 2033 or more elements with the following supported "name" 2034 attribute values: 2036 "contact" Defines the fields and CSV file references used for the 2037 contact object records. 2039 The following "csvContact" field elements, defined for the 2040 "contact" element, MUST be used in 2041 the "contact" element: 2043 Contains the server-unique contact identifier 2044 with type="eppcom:clIDType" and isRequired="true". 2046 Contains the contact's email address with 2047 type="eppcom:minTokenType" and isRequired="true". 2049 The following field elements MAY be used in the "contact" element: 2052 Contains the contact's voice telephone number 2053 with type="contact:e164StringType". 2055 Contains the contact's voice telephone 2056 number extension with type="token". 2058 Contains the contact's facsimile telephone 2059 number with type="contact:e164StringType". 2061 Contains the contact's facsimile telephone 2062 number extension with type="token". 2064 The following "rdeCsv" fields, defined in section CSV common field 2065 elements (Section 4.6.2), MUST be used in the "contact" element: 2068 The Registry Object IDentifier (ROID) for the 2069 contact object. 2071 Identifier of client (registrar) that sponsors the 2072 contact object. 2074 Identifier of the registrar, defined in 2075 Section 5.4, of the client that created the object. 2077 Created date and time of the contact object 2079 Identifier of the registrar, defined in 2080 Section 5.4, of the client that updated the object. 2082 Date and time of the last update to the contact 2083 object. 2085 Date and time of the last transfer for the 2086 contact object. 2088 The following "rdeCsv" fields, defined in section CSV common field 2089 elements (Section 4.6.2), MAY be used in the "contact" element: 2092 Identifier of client that created the contact 2093 object. 2095 Identifier of the client that last updated the 2096 contact object. 2098 Example of a "contact" element: 2100 ... 2101 2102 ... 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2123 contact-YYYYMMDD.csv 2124 2125 2126 2127 ... 2128 2129 ... 2131 Example of the contact-YYYYMMDD.csv file. The file contains two 2132 object contact records. 2134 sh8013,Csh8013-TEST,+1.7035555555,1234,+1.7035555556,, 2135 jdoe@example.test,registrarX,registarX, 2136 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2137 2009-11-26T09:10:00.0Z 2138 mycontactid,Cmycontactid-TEST,+1.7034444444,1234, 2139 +1.7033333333,,jsmith@example.test,registrarX,registarX,clientY, 2140 2010-09-13T08:01:00.0Z,registarX,clientY,2011-11-26T09:10:00.0Z 2141 Example of a "contact" element: 2143 ... 2144 2145 ... 2146 2147 2148 2149 2150 2151 2153 contact-delete-YYYYMMDD.csv 2154 2155 2156 2157 ... 2158 2159 ... 2161 Example of the contact-delete-YYYYMMDD.csv file. The file 2162 contains two contact records. 2164 sh8013 2165 mycontactid 2167 "contactStatuses" Defines the fields and CSV file references used 2168 for the contact object statuses. 2170 The following "csvContact" field elements, defined for the 2171 "contact" element, MUST be used in 2172 the "contactStatuses" element: 2174 Server-unique contact identifier of status. 2176 The status of the contact with 2177 type="contact:statusValueType". 2179 The following "rdeCsv" fields, defined in section CSV common field 2180 elements (Section 4.6.2), MAY be used in the "contactStatuses" 2181 element: 2183 The contact object status description 2184 which is free form text describing the rationale for the 2185 status. 2187 Language of the field. 2189 Example of a "contactStatuses" 2190 element: 2192 ... 2193 2194 ... 2195 2196 2197 2198 2199 2200 2201 2202 2203 2205 contactStatuses-YYYYMMDD.csv 2206 2207 2208 2209 ... 2210 2211 ... 2213 Example of the corresponding contactStatuses-YYYYMMDD.csv file. 2214 The file contains the statuses for the two contact identifiers 2215 sh8013 and mycontactid. 2217 sh8013,clientUpdateProhibited,"Disallow update",en 2218 sh8013,clientDeleteProhibited,"Disallow delete",en 2219 mycontactid,ok,, 2220 Example of a "contactStatuses" 2221 element: 2223 ... 2224 2225 ... 2226 2227 2228 2229 2230 2231 2232 2234 contactStatuses-delete-YYYYMMDD.csv 2235 2236 2237 2238 ... 2239 2240 ... 2242 Example of the corresponding contactStatuses-delete-YYYYMMDD.csv 2243 file. The file contains two status records. 2245 sh8013,clientUpdateProhibited 2246 sh8013,clientDeleteProhibited 2248 "contactPostal" Defines the fields and CSV file references used for 2249 the contact postal info object records. 2251 The following "csvContact" field elements, defined for the 2252 "contactPostal" element, MUST be used 2253 in the "contactPostal" element: 2255 Contains the contact's name of the individual 2256 or role represented by the contact with type="contact: 2257 postalLineType" and isRequired="true". An OPTIONAL "isLoc" 2258 attribute to used to indicate the localized or 2259 internationalized form as defined in section Section 4.7. 2261 Contains the contact's contact's street 2262 address line with type="contact:fPostalLineType". An index 2263 attribute is required to indicate which street address line the 2264 field represents with index "0" for the first line and index 2265 "2" for the last line. An OPTIONAL "isLoc" attribute to used 2266 to indicate the localized or internationalized form as defined 2267 in section Section 4.7. 2269 Contains the contact's city with 2270 type="contact:postalLineType" and isRequired="true". An 2271 OPTIONAL "isLoc" attribute to used to indicate the localized or 2272 internationalized form as defined in section Section 4.7. 2274 Contains the contact's country code with 2275 type="contact:ccType". An OPTIONAL "isLoc" attribute to used 2276 to indicate the localized or internationalized form as defined 2277 in section Section 4.7. 2279 "contactPostal" Defines the fields and CSV file references used for 2280 the contact postal info object records. 2282 The following "csvContact" field elements, defined for the 2283 "contactPostal" element, MAY be used 2284 in the "contactPostal" element: 2286 Contains the form of the postal-address 2287 information with type="contact:postalLineType". This field 2288 specifies the form ("int" or "loc"), as defined in Section 4.7, 2289 of the , , , , , , fields. 2293 Contains the name of the organization with 2294 which the contact is affiliated with type="contact: 2295 optPostalLineType". An OPTIONAL "isLoc" attribute to used to 2296 indicate the localized or internationalized form as defined in 2297 section Section 4.7. 2299 Contains the contact's state or province with 2300 type="contact:optPostalLineType". An OPTIONAL "isLoc" 2301 attribute to used to indicate the localized or 2302 internationalized form as defined in section Section 4.7. 2304 Contains the contact's postal code with 2305 type="contact:pcType". An OPTIONAL "isLoc" attribute to used 2306 to indicate the localized or internationalized form as defined 2307 in section Section 4.7. 2309 The following "csvContact" fields, defined for the "contact" 2310 element, MUST be used in the 2311 "contactPostal" element: 2313 Server-unique contact identifier for the contact 2314 object. 2316 Example of a "contactPostal" 2317 element: 2319 ... 2320 2321 ... 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2339 contactPostal-YYYYMMDD.csv 2340 2341 2342 2343 ... 2344 2345 ... 2347 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2348 two contact postal records. 2350 sh8013,int,"John Doe","Example Inc.", 2351 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2352 mycontactid,int,"John Smith","Acme Inc.", 2353 "123 Sample Dr.",,,Reston,VA,20190,US 2355 Example of a "contactPostal" 2356 element: 2358 ... 2359 2360 ... 2361 2362 2363 2364 2365 2366 2367 2369 contactPostal-delete-YYYYMMDD.csv 2370 2371 2372 2373 ... 2374 2375 ... 2377 Example of the contactPostal-delete-YYYYMMDD.csv file. The file 2378 contains two contact postal records. 2380 sh8013,int 2381 mycontactid,int 2383 "contactTransfer" Defines the fields and CSV file references used 2384 for the contact object pending and completed transfer records. No 2385 additional field elements were added for use in the 2386 "contactTransfer" element. The 2387 following "rdeCsv" fields, defined in section CSV common field 2388 elements (Section 4.6.2), MUST be used in the "contactTransfer" 2389 element: 2391 State of the most recent transfer request. 2393 Identifier of the registrar, defined in 2394 Section 5.4, of the client that requested the transfer. 2396 Date and time that the transfer was requested. 2398 Identifier of the registrar, defined in 2399 Section 5.4, of the client that should take or took action. 2401 Date and time that the transfer action should be 2402 taken or has been taken 2404 The following "rdeCsv" fields, defined in section CSV common field 2405 elements (Section 4.6.2), MAY be used in the "contactTransfer" 2406 element: 2408 Identifier of client that requested the transfer. 2410 Identifier of client that should take or took 2411 action for transfer. 2413 The following "csvContact" fields, defined for the "contact" 2414 element, MUST be used in the 2415 "contactTransfer" element: 2417 Server-unique contact identifier for the contact 2418 object. 2420 Example of a "contactTransfer" 2421 element: 2423 ... 2424 2425 ... 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2440 contactTransfer-YYYYMMDD.csv 2441 2442 2443 2444 ... 2445 2446 ... 2448 Example of the contactTransfer-YYYYMMDD.csv file. The file 2449 contains two contact transfer records with one in pending status 2450 and the second in clientApproved status. 2452 sh8013,pending,registrarX,clientX,2011-03-08T19:38:00.0Z, 2453 registrarY,,2011-03-13T23:59:59.0Z 2454 mycontactid,clientApproved,registrarX,clientX,2011-04-08T19:38:00.0Z, 2455 registrarY,clientY,2011-04-09T20:38:00.0Z 2457 Example of a "contactTransfer" 2458 element: 2460 ... 2461 2462 ... 2463 2464 2465 2466 2467 2468 2469 2471 contactTransfer-delete-YYYYMMDD.csv 2472 2473 2474 2475 ... 2476 2477 ... 2479 Example of the contactTransfer-delete-YYYYMMDD.csv file. The file 2480 contains two contact transfer records. 2482 sh8013,2011-03-08T19:38:00.0Z 2483 mycontactid,2011-04-08T19:38:00.0Z 2485 "contactDisclose" Defines the fields and CSV file references used 2486 for the contact disclose object records. 2488 The following "csvContact" field elements, defined for the 2489 "contactDisclose" element, MAY be 2490 used in the "contactDisclose" 2491 element: 2493 Contains flag with a value of "true" 2494 or "1" (one) notes the preference to allow disclosure of the 2495 specified elements as an exception to the stated data- 2496 collection policy. A value of "false" or "0" (zero) notes a 2497 client preference to not allow disclosure of the specified 2498 elements as an exception to the stated data-collection policy 2499 with type="boolean". The additional fields define specific 2500 exceptional disclosure preferences based on the field. 2503 Exceptional disclosure preference 2504 flag for the localized form of the contact name with 2505 type="boolean". 2507 Exceptional disclosure preference 2508 flag for the internationalized form of the contact name with 2509 type="boolean". 2511 Exceptional disclosure preference 2512 flag for the localized form of the contact organization with 2513 type="boolean". with type="boolean". 2515 Exceptional disclosure preference 2516 flag for the internationalized form of the contact organization 2517 with type="boolean". with type="boolean". 2519 Exceptional disclosure preference 2520 flag for the localized form of the contact address with 2521 type="boolean". 2523 Exceptional disclosure preference 2524 flag for the internationalized form of the contact address with 2525 type="boolean". 2527 Exceptional disclosure preference 2528 flag of the contact voice telephone number with type="boolean". 2530 Exceptional disclosure preference flag 2531 of the contact facsimile telephone number with type="boolean". 2533 Exceptional disclosure preference 2534 flag of the contact email address with type="boolean". 2536 The following "csvContact" fields, defined for the "contact" 2537 element, is used in the 2538 "contactDisclose" element: 2540 Server-unique contact identifier for the contact 2541 object. 2543 Example of a "contactDisclose" 2544 element: 2546 ... 2547 2548 ... 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2566 contactDisclose-YYYYMMDD.csv 2567 2568 2569 2570 ... 2571 2572 ... 2574 Example of the contactDisclose-YYYYMMDD.csv file. The file 2575 contains two disclosure records. The first contact disables 2576 disclosure of voice, fax, and email. The second contact enables 2577 disclosure of the localized and internationalized form of the 2578 name. 2580 sh8013,0,0,0,0,0,0,0,1,1,1 2581 mycontactid,1,1,1,0,0,0,0,0,0,0 2583 Example of a "contactDisclose" 2584 element: 2586 ... 2587 2588 ... 2589 2590 2591 2592 2593 2594 2596 contactDisclose-delete-YYYYMMDD.csv 2597 2598 2599 2600 ... 2601 2602 ... 2604 Example of the contactDisclose-delete-YYYYMMDD.csv file. The file 2605 contains two disclosure records. 2607 sh8013 2608 mycontactid 2610 5.4. Registrar Object 2612 The registrar object represents the sponsoring client for other 2613 objects, for operational purposes MAY be the registry operator. The 2614 registrar object supports both the XML Model and the CSV Model, 2615 defined in Section 2. The elements used for both models are defined 2616 in the following sections. 2618 5.4.1. XML Model 2620 There are two elements used in the data escrow of the registrar 2621 objects for the XML model including the , 2622 under the element, and the element, under the element. 2625 A element substitutes for the abstract element to define a concrete definition 2627 of a registrar. The element can be 2628 replaced by other domain definitions using the XML schema 2629 substitution groups feature. 2631 5.4.1.1. element 2633 The element contains the following child elements: 2635 o An element that contains the Registry-unique identifier of 2636 the registrar object. This has a superordinate relationship 2637 to a subordinate , or of domain, contact and 2638 host objects. 2640 o An element that contains the name of the registrar. 2642 o An OPTIONAL element that contains the ID assigned by 2643 ICANN. 2645 o A element that contains the operational status of the 2646 registrar. Possible values are: ok, readonly and terminated. 2648 o One or two elements that contain postal- address 2649 information. Two elements are provided so that address 2650 information can be provided in both internationalized and 2651 localized forms; a "type" attribute is used to identify the two 2652 forms. If an internationalized form (type="int") is provided, 2653 element content MUST be represented in a subset of UTF-8 that can 2654 be represented in the 7-bit US-ASCII character set. If a 2655 localized form (type="loc") is provided, element content MAY be 2656 represented in unrestricted UTF-8. The element 2657 contains the following child elements: 2659 * A element that contains address information associated 2660 with the registrar. The element contains the following 2661 child elements: 2663 + One, two, or three OPTIONAL elements that contain 2664 the registrar's street address. 2666 + A element that contains the registrar's city. 2668 + An OPTIONAL element that contains the registrar's state 2669 or province. 2671 + An OPTIONAL element that contains the registrar's 2672 postal code. 2674 + A element that contains the registrar's country code. 2676 o An OPTIONAL element that contains the registrar's voice 2677 telephone number. 2679 o An OPTIONAL element that contains the registrar's facsimile 2680 telephone number. 2682 o An element that contains the registrar's email address. 2684 o An OPTIONAL element that contains the registrar's URL. 2686 o An OPTIONAL elements that contains whois information. 2687 The element contains the following child elements: 2689 * An OPTIONAL element that contains the name of the 2690 registrar WHOIS server listening on TCP port 43 as specified in 2691 [RFC3912]. 2693 * An OPTIONAL element that contains the name of the 2694 registrar WHOIS server listening on TCP port 80/443. 2696 o A element that contains the date and time of registrar- 2697 object creation. 2699 o An OPTIONAL element that contains the date and time of 2700 the most recent RDE registrar-object modification. This element 2701 MUST NOT be present if the rdeRegistrar object has never been 2702 modified. 2704 Example of object: 2706 ... 2707 2708 RegistrarX 2709 Registrar X 2710 123 2711 ok 2712 2713 2714 123 Example Dr. 2715 Suite 100 2716 Dulles 2717 VA 2718 20166-6503 2719 US 2720 2721 2722 +1.7035555555 2723 +1.7035555556 2724 jdoe@example.test 2725 http://www.example.test 2726 2727 whois.example.test 2728 http://whois.example.test 2729 2730 2005-04-23T11:49:00.0Z 2731 2009-02-17T17:51:00.0Z 2732 2733 ... 2735 5.4.1.2. object 2737 The element contains the id of a registrar that 2738 was deleted. 2740 Example of object: 2742 ... 2743 2744 ... 2745 2746 agnt0001-TEST 2747 2748 ... 2749 2750 ... 2752 5.4.2. CSV Model 2754 For the CSV Model of the registrar object, The child element of the element is used to hold 2756 the new or updated registrar objects for the deposit. The 2757 child element of the element is 2758 used to hold the deleted or purged registrar objects for the deposit. 2759 Both the and elements 2760 contain one or more elements with the following 2761 supported "name" attribute values: 2763 "registrar" Defines the fields and CSV file references used for the 2764 registrar object records. 2766 The following "csvRegistrar" field elements, defined for the 2767 "registrar" element, MUST be used in 2768 the "registrar" element: 2770 Contains the server-unique registrar 2771 identifier with type="eppcom:clIDType" and isRequired="true". 2773 Contains the name of the registrar with 2774 type="normalizedString" and isRequired="true". 2776 Contains the status of the registrar with 2777 type="csvRegistrar:statusValueType". 2779 The following field elements MAY be used in the "registrar" 2780 element: 2782 Contains the ID assigned by ICANN with 2783 type="positiveInteger". 2785 Contains the Whois URL of the registrar 2786 with type="anyURI". 2788 The following "rdeCsv" fields, defined in section CSV common field 2789 elements (Section 4.6.2), MUST be used in the "registrar" element: 2792 Created date and time of the registrar object. 2794 Date and time of the last update to the 2795 registrar object. 2797 URL for the registrar web home page. 2799 The following "csvContact" fields, defined in section Section 5.3, 2800 MUST be used in the "registrar" 2801 element: 2803 Registrar street address line with an 2804 "index" attribute that represents the order of the street 2805 address line from "0" to "2". An OPTIONAL "isLoc" attribute 2806 that is used to indicate the localized or internationalized 2807 form, as defined in Section 4.7. 2809 Registrar city with an OPTIONAL "isLoc" 2810 attribute that is used to indicate the localized or 2811 internationalized form, as defined in Section 4.7. 2813 Registrar country code with an OPTIONAL "isLoc" 2814 attribute that is used to indicate the localized or 2815 internationalized form, as defined in Section 4.7. 2817 Registrar email address. 2819 The following "csvContact" fields, defined in section Section 5.3, 2820 MAY be used in the "registrar" 2821 element: 2823 Registrar state or province with an OPTIONAL 2824 "isLoc" attribute that is used to indicate the localized or 2825 internationalized form, as defined in Section 4.7. 2827 Registrar postal code with an OPTIONAL "isLoc" 2828 attribute that is used to indicate the localized or 2829 internationalized form, as defined in Section 4.7. 2831 Registrar voice telephone number. 2833 Registrar voice telephone number 2834 extension. 2836 Registrar facsimile telephone number. 2838 Registrar facsimile telephone number 2839 extension. 2841 Example of a "registrar" 2842 element. 2844 ... 2845 2846 ... 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2873 registrar-YYYYMMDD.csv 2874 2875 2876 2877 ... 2878 2879 ... 2881 Example of the registrar-YYYYMMDD.csv file. The file contains one 2882 registrar record. 2884 EXAMPLE,"Example Inc.",1234,ok,"123 Example Dr.", 2885 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2886 +1.7035555556,,jdoe@example.test,http://www.example.test, 2887 http://whois.example.test,2005-04-23T11:49:00.0Z, 2888 2009-02-17T17:51:00.0Z 2890 Example of a "registrar" 2891 element: 2893 ... 2894 2895 ... 2896 2897 2898 2899 2900 2901 2903 registrar-delete-YYYYMMDD.csv 2904 2905 2906 2907 ... 2908 2909 ... 2911 Example of the registrar-delete-YYYYMMDD.csv file. The file 2912 contains two registrar records. 2914 EXAMPLE 2915 EXAMPLE2 2917 5.5. IDN Table Reference Object 2919 The Internationalized Domain Names (IDN) table reference object is a 2920 pseudo-object that is used to provide a short reference to the IDN 2921 Table and Policy used in IDN registrations. The IDN reference object 2922 supports both the XML and the CSV Model, defined in the Models 2923 (Section 2) section. The elements used for both models are defined 2924 in the following sections. 2926 5.5.1. XML Model 2928 There is one element used in the data escrow of the IDN table 2929 reference objects for the XML model that is the , 2930 under the element. 2932 5.5.1.1. object 2934 The contains the following elements. An "id" 2935 attribute is used to specify an identifier for the IDN table. 2937 o An element that contains the URL of the IDN table that is 2938 being referenced. 2940 o A element that contains the URL of the IDN policy 2941 document. If IDN variants are generated algorithmically, the 2942 policy document MUST define the algorithm and the state of the 2943 implicit generated IDN variants. For a list of suggested states 2944 for implicit IDN variants, please see [variantTLDsReport]. 2946 Example of object: 2948 ... 2949 2950 2951 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 2952 2953 2954 http://registro.br/dominio/regras.html 2955 2956 2957 ... 2959 5.5.2. CSV Model 2961 The IDN domain names, defined in Section 5.1, MAY have references to 2962 the IDN language identifier using the field 2963 element. The IDN table reference object defines the mapping of a 2964 language identifier to a language table URL. The language table URL 2965 defines the character code points that can be used for the language 2966 identifier. The elements used for the IDN table reference object is 2967 defined in this section. The child element of the 2968 element is used to hold the new or updated IDN table 2969 reference objects for the deposit. The child 2970 element of the element is used to hold the deleted or 2971 purged IDN table reference objects for the deposit. Both the 2972 and elements contain one or more 2973 elements with the following supported "name" attribute 2974 values: 2976 "idnLanguage" Defines the fields and CSV file references used for 2977 the IDN table reference object records. 2979 The following "rdeCsv" fields, defined in Section 4.6.2, MUST be 2980 used in the "idnLanguage" element: 2982 The language identifier that matches the 2983 values for the field element in the 2984 "domain" CSV files, as defined in Section 5.1. 2986 URL that defines the character code points that can 2987 be used for the language defined by the field 2988 element. 2990 Example of a "idnLanguage" element: 2992 ... 2993 2994 ... 2995 2996 , 2997 2998 2999 3000 3001 3002 3004 idnLanguage-YYYYMMDD.csv 3005 3006 3007 3008 ... 3009 3010 ... 3012 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The 3013 file contains two IDN language records. 3015 LANG-1, 3016 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3017 LANG-2, 3018 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3020 Example of a "idnLanguage" element: 3022 ... 3023 3024 ... 3025 3026 3027 3028 3029 3030 3032 idnLanguage-delete-YYYYMMDD.csv 3033 3034 3035 3036 ... 3037 3038 ... 3040 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3041 contains two IDN language records. 3043 LANG1 3044 LANG2 3046 5.6. NNDN Object 3048 A NNDN (NNDN's not domain name) can be used to store registry 3049 reserved names or (blocked, withheld or mirrored) IDN variants. 3051 A NNDN is a lightweight domain-like object that is not linked 3052 directly to a Registrar (a mirroring NNDN is linked to a Registrar 3053 via the original name). 3055 A domain name can only exist as a domain name object or NNDN object, 3056 but not both. 3058 The NNDN object supports both the XML and the CSV Model, defined in 3059 the Models (Section 2) section. The elements used for both models 3060 are defined in the following sections. 3062 5.6.1. XML Model 3064 There are two elements used in the data escrow of the NNDN objects 3065 for the XML model including the , under the element, and the element, under the element. 3069 A element substitutes for the 3070 abstract element to define a concrete definition of a NNDN. The 3071 element can be replaced by other NNDN 3072 definitions using the XML schema substitution groups feature. 3074 5.6.1.1. object 3076 The element contains the following child elements: 3078 o An element that contains the ASCII Compatible Encoding 3079 (ACE) field of the NNDN. 3081 o An OPTIONAL element that contains the name of the NNDN in 3082 Unicode character set. It MUST be provided if available. 3084 o An OPTIONAL element that references the IDN Table 3085 used for the NNDN. This corresponds to the "id" attribute of the 3086 element. This element MUST be present if the NNDN 3087 is an IDN. 3089 o An OPTIONAL element is used to indicate that the 3090 NNDN is an IDN variant. This element contains the domain name 3091 used to generate the IDN variant. 3093 o A element that indicates the state of the NNDN: 3094 blocked, withheld or mirrored. 3096 * If a NNDN is considered undesirable for registration (i.e., 3097 unavailable for allocation to anyone), then the NNDN will be 3098 tagged as "blocked". 3100 * If a NNDN is considered a potential registration of a domain 3101 object for a particular registrant, then the NNDN will be 3102 tagged as "withheld". 3104 * If a NNDN is considered a mirrored IDN variant of a domain 3105 object, then the NNDN will be tagged as "mirrored". A 3106 mirroringNS attribute is used to specify if the mirrored IDN 3107 variant use the NS mirror mechanism. The default value of 3108 mirroringNS is true. If another mechanism such as DNAME is 3109 used, the value of mirroringNS attribute MUST be false. 3111 o A element that contains the date and time of the NNDN 3112 object creation. 3114 Example of object: 3116 ... 3117 3118 xn--exampl-gva.test 3119 pt-BR 3120 example1.test 3121 withheld 3122 2005-04-23T11:49:00.0Z 3123 3124 ... 3126 5.6.1.2. object 3128 The element contains the ACE of a NNDN that was 3129 deleted, i.e., the . 3131 Example of object: 3133 ... 3134 3135 ... 3136 3137 xn--pingino-q2a.test 3138 3139 ... 3140 3141 ... 3143 5.6.2. CSV Model 3145 For the CSV Model of the NNDN object, the child 3146 element of the element is used to hold the new or 3147 updated NNDN objects for the deposit. The child 3148 element of the element is used to hold the deleted or 3149 purged NNDN objects for the deposit. Both the and 3150 elements contain one or more elements 3151 with the following supported "name" attribute values: 3153 "NNDN" Defines the fields and CSV file references used for the NNDN 3154 object records. 3156 The following "csvNNDN" field elements, defined for the "NNDN" 3157 element, MUST be used in the "NNDN" 3158 element: 3160 ASCII Compatible Encoding (ACE) field of the 3161 NNDN with type="eppcom:labelType" and isRequired="true". 3163 Domain name used to generate the IDN 3164 variant with type="eppcom:labelType". 3166 State of the NNDN: blocked or withheld with 3167 type="rdeNNDN:nameState". See Section 5.6.1.1 for a 3168 description of the possible values for the 3169 element. 3171 The following field elements MAY be used in the "NNDN" element: 3174 Domain name used to generate the IDN 3175 variant with type="eppcom:labelType". 3177 Defines whether the "mirroring" uses the NS mirror mechanism, as described for the 3179 "mirroringNS" attribute in Section 5.6.1.1, 3180 with type="boolean". If the field element is not defined the 3181 default value is "true". 3183 The following "rdeCsv" fields, defined in section CSV common field 3184 elements (Section 4.6.2), MUST be used in the "domain" element: 3187 Created date and time of the domain name object. 3189 The following "rdeCsv" fields, defined in section CSV common field 3190 elements (Section 4.6.2), MAY be used in the "domain" 3191 element: 3193 Name of the NNDN in Unicode character set for the 3194 field element. 3196 IDN Table Identifier for the NNDN that 3197 matches an IDN Table Reference Object record, as defined in 3198 Section 5.5.2. 3200 Example of a "NNDN" element: 3202 ... 3203 3204 ... 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3217 NNDN-YYYYMMDD.csv 3218 3219 3220 3221 ... 3222 3223 ... 3225 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3226 contains two NNDN records for an IDN with one blocked variant and 3227 one mirrored variant. 3229 xn--exampl-gva.test,pt-BR,xn--exampl.test, 3230 blocked,,2005-04-23T11:49:00.0Z 3231 xn--exampl2-gva.test,pt-BR,xn--exampl.test, 3232 mirrored,1,2005-04-23T11:49:00.0Z 3234 Example of a "NNDN" element: 3236 ... 3237 3238 ... 3239 3240 3241 3242 3243 3244 3246 NNDN-delete-YYYYMMDD.csv 3247 3248 3249 3250 ... 3251 3252 ... 3254 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The 3255 file contains one NNDN record. 3257 xn--pingino-q2a.test 3259 5.7. EPP Parameters Object 3261 The EPP Parameters Object is a pseudo-object that defines the set of 3262 object and object extension services supported by the registry, as 3263 defined in [RFC5730]. The EPP Parameters Object is only defined as 3264 XML but could be used in the the XML model or CSV model. The EPP 3265 Parameters Object is defined using the the 3266 element. The EPP Parameters Object SHOULD be included if the 3267 registry supports EPP. Only one EPP Parameters Object MUST exist at 3268 a certain point in time (watermark). 3270 The syntax and content of the children 3271 elements is as explained in section 2.4 of [RFC5730]. The children 3272 of the are as follows: 3274 o One or more elements that indicate the EPP versions 3275 supported by the registry. 3277 o One or more elements that indicate the identifiers of the 3278 text response languages supported by the registry's EPP server. 3280 o One or more elements that contain namespace URIs 3281 representing the objects that the registry's EPP server is capable 3282 of managing. 3284 o An OPTIONAL element that contains one or more 3285 elements that contain namespace URIs representing object 3286 extensions supported by the registry's EPP server. 3288 o A element that contains child elements used to describe the 3289 server's privacy policy for data collection and management. See 3290 section 2.4 of [RFC5730] for more details. 3292 Example of element object: 3294 ... 3295 3296 1.0 3297 en 3298 urn:ietf:params:xml:ns:domain-1.0 3299 3300 urn:ietf:params:xml:ns:contact-1.0 3301 3302 urn:ietf:params:xml:ns:host-1.0 3303 3304 3305 urn:ietf:params:xml:ns:rgp-1.0 3306 urn:ietf:params:xml:ns:secDNS-1.1 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 ... 3327 5.8. Policy Object 3329 The Policy object is a pseudo-object that is used to specify which 3330 OPTIONAL elements from the XML Model are REQUIRED based on the 3331 business model of the registry. For the CSV Model, the OPTIONAL 3332 "isRequired" attribute of the elements, defined in 3333 Section 4.6.1, is used to specify which OPTIONAL fields are REQUIRED 3334 based on the business model of the registry. 3336 5.8.1. object 3338 The OPTIONAL contains the following attributes: 3340 o An that defines that the referenced is 3341 REQUIRED. 3343 o that defines the XPath of the element referenced by 3344 . 3346 Example of object: 3348 ... 3349 3351 ... 3353 5.9. Header Object 3355 The Header Object is a pseudo-object that is used to specify the 3356 number of objects in the SRS at a specific point in time (watermark) 3357 regardless of the type of deposit: differential, full or incremental. 3358 The Header Object is only defined as XML but one header object MUST 3359 always be present per escrow deposit regardless of using XML Model or 3360 CSV Model. The Header Object is defined using the 3361 element. 3363 5.9.1. object 3365 The contains the following attributes: 3367 o A element that defines TLD being escrowed. 3369 o A element that contains the number of objects in the SRS 3370 at a specific point in time (watermark) regardless of the type of 3371 deposit: differential, full or incremental. The "uri" attributes 3372 reflects the XML namespace URI of the primary objects for the XML 3373 Model and CSV Model. For example, the "uri" is set to 3374 "urn:ietf:params:xml:ns:rdeDomain-1.0" for domain name objects 3375 using the XML Model, and the "uri" is set to 3376 "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name objects 3377 using the CSV Model. 3379 Example of object referencing only the XML Model 3380 objects: 3382 ... 3383 3384 test 3385 2 3387 1 3389 1 3391 1 3393 3394 1 3396 1 3398 1 3400 3401 3402 ... 3404 Example of object referencing the CSV and XML 3405 Model objects: 3407 ... 3408 3409 test 3410 2 3412 1 3414 1 3416 1 3418 3419 1 3421 1 3423 1 3425 3426 3427 ... 3429 6. RDE IDN Variants handling 3431 Depending on the Registration Policy of the Registry; for a 3432 particular domain name there may be multiple variant names. See 3433 [variantTLDsReport] for further detail on IDN variants. 3435 A registry could choose to escrow IDN variants as domains or NNDN 3436 objects. An specific IDN variant can be represented in the escrow 3437 deposit, as a domain or as a NNDN object, but not both. 3439 If using domain objects to represent IDN variants, the normal 3440 behavior during restoration of a SRS based on an escrow deposit is to 3441 restore the IDN variants as a mirrored variant. If the registration 3442 data of the IDN variant is different from the original name, the 3443 details of this specific implementation MUST be described in the IDN 3444 policy document. 3446 A NNDN or a domain name are explicit representations of an IDN 3447 variant while an IDN variant computed based on an algorithm is an 3448 implicit representation. Explicit representation of an IDN variant 3449 takes precedence over an implicit representation. 3451 7. Profile 3453 Different business models of registries exist, therefore the registry 3454 is responsible to define a profile that matches its particular 3455 business model. The profile mechanism allows a registry to extend 3456 this specification. 3458 A profile is the process of: 3460 1. Extending base objects with the mechanisms defined for XML and 3461 CSV models. 3463 * In the case of the XML model, abstract elements could be use 3464 to extend the following objects: , , , 3465 and using XML schema substitution groups 3466 feature. 3468 2. Defining a object to specify which OPTIONAL elements of 3469 this base specification are required based on the business model 3470 of the registry. An example is the element that is 3471 usually REQUIRED but it is specified as OPTIONAL in this 3472 specification to support existing business models. 3474 3. Adding new escrowed objects using the and elements. 3477 4. Providing the XML schemas to third parties that require them to 3478 validate the escrow deposits. 3480 8. Data escrow agent extended verification process 3482 The Data Escrow Agent MUST perform a extended verification process 3483 using the contents of the data escrow deposits to a point in time 3484 (watermark), last full plus all differentials or last full plus last 3485 incremental escrow deposits. The following are the minimum suggested 3486 tests: 3488 o Validate the escrow deposits using the definition agreed with the 3489 registry. 3491 * In the case of the XML model, the contents of the escrow 3492 deposits MUST be validated using the XML schemas of the 3493 profile. 3495 o Count the objects and validate that the number of objects is equal 3496 to the number objects reported in the
element of the 3497 escrow deposit of that point in time (watermark). 3499 o All contacts objects linked to domain names MUST be present. 3501 o All registrars objects linked to other objects MUST be present. 3503 o A domain name exists as a domain name or NNDN, but not both. 3505 o The elements listed as required in the element MUST be 3506 present. 3508 o All idnTableRef definitions linked from other objects MUST be 3509 present. 3511 o If an EPP Parameters Object was escrowed in the past, one and only 3512 one EPP Parameters Object MUST be present. 3514 9. Formal Syntax 3516 Schemas are presented here. 3518 9.1. RDE CSV Schema 3520 Copyright (c) 2012 IETF Trust and the persons identified as authors 3521 of the code. All rights reserved. 3523 Redistribution and use in source and binary forms, with or without 3524 modification, are permitted provided that the following conditions 3525 are met: 3527 o Redistributions of source code must retain the above copyright 3528 notice, this list of conditions and the following disclaimer. 3530 o Redistributions in binary form must reproduce the above copyright 3531 notice, this list of conditions and the following disclaimer in 3532 the documentation and/or other materials provided with the 3533 distribution. 3535 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3536 names of specific contributors, may be used to endorse or promote 3537 products derived from this software without specific prior written 3538 permission. 3540 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3541 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3542 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3543 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3544 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3545 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3546 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3547 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3548 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3549 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3550 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3552 BEGIN 3553 3555 3562 3565 3567 3570 3571 3572 Registry Data Escrow Comma-Seperated Values (CSV) 3573 3574 3576 3577 3579 3580 3581 3582 3583 3584 3585 3586 3587 3589 3590 3593 3594 3595 3597 3598 3599 3600 3601 3602 3604 3605 3606 3607 3609 3610 3611 3612 3613 3614 3616 3617 3618 3619 3621 3623 3624 3626 3627 3628 3629 3630 3632 3633 3634 3635 3636 3637 3638 3639 3641 3642 3643 3645 3646 3648 3649 3650 3651 3652 3654 3655 3656 3658 3659 3661 3662 3663 3664 3665 3667 3668 3669 3671 3672 3676 3677 3678 3680 3682 3684 3685 3688 3690 3692 3693 3695 3697 3699 3701 3703 3705 3707 3709 3711 3712 3713 3714 3715 3717 3718 3719 3720 3721 3722 3723 3724 3726 3727 3728 3730 3731 3733 3736 3738 3739 3741 3742 3744 3746 3747 3748 3749 3750 3752 3753 3754 3756 3757 3758 3759 3760 3761 3763 3764 3765 3767 3768 3769 3770 3771 3772 3774 3775 3776 3778 3779 3780 3781 3782 3783 3785 3786 3787 3789 3790 3791 3792 3793 3794 3796 3797 3798 3800 3801 3803 3804 3805 3806 3807 3809 3810 3811 3813 3814 3817 3818 3820 3821 3822 3823 3824 3826 3827 3828 3830 3831 3832 3833 3834 3835 3837 3838 3839 3841 3842 3843 3844 3845 3846 3848 3849 3850 3852 3853 3854 3855 3856 3857 3859 3860 3861 3863 3864 3866 3867 3868 3869 3870 3871 3873 3874 3875 3877 3878 3879 3880 3881 3882 3884 3885 3886 3887 3889 3890 3892 3893 3894 3895 3896 3897 3899 3900 3901 3902 3904 3905 3907 3908 3909 3910 3911 3913 3914 3915 3917 3920 3921 END 3923 9.2. RDE Domain Object 3925 Copyright (c) 2011 IETF Trust and the persons identified as authors 3926 of the code. All rights reserved. 3928 Redistribution and use in source and binary forms, with or without 3929 modification, are permitted provided that the following conditions 3930 are met: 3932 o Redistributions of source code must retain the above copyright 3933 notice, this list of conditions and the following disclaimer. 3935 o Redistributions in binary form must reproduce the above copyright 3936 notice, this list of conditions and the following disclaimer in 3937 the documentation and/or other materials provided with the 3938 distribution. 3940 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3941 names of specific contributors, may be used to endorse or promote 3942 products derived from this software without specific prior written 3943 permission. 3945 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3946 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3947 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3948 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3949 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3950 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3951 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3952 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3953 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3954 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3955 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3957 BEGIN 3958 3959 3969 3970 3971 3972 3973 3975 3976 3977 Registry Data Escrow Domain provisioning schema 3978 3979 3981 3984 3986 3990 3991 3992 3993 3994 3995 3997 3999 4001 4003 4005 4007 4010 4012 4015 4017 4019 4021 4023 4025 4027 4029 4031 4033 4036 4037 4038 4039 4041 4042 4043 4045 4047 4049 4051 4053 4055 4056 4058 4059 4060 4061 4062 4063 4066 4067 4068 4069 4070 4071 END 4073 9.3. CSV Domain Object 4075 Copyright (c) 2012 IETF Trust and the persons identified as authors 4076 of the code. All rights reserved. 4078 Redistribution and use in source and binary forms, with or without 4079 modification, are permitted provided that the following conditions 4080 are met: 4082 o Redistributions of source code must retain the above copyright 4083 notice, this list of conditions and the following disclaimer. 4085 o Redistributions in binary form must reproduce the above copyright 4086 notice, this list of conditions and the following disclaimer in 4087 the documentation and/or other materials provided with the 4088 distribution. 4090 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4091 names of specific contributors, may be used to endorse or promote 4092 products derived from this software without specific prior written 4093 permission. 4095 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4096 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4097 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4098 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4099 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4100 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4101 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4102 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4103 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4104 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4105 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4107 BEGIN 4108 4110 4121 4124 4126 4128 4130 4132 4134 4137 4138 4139 Domain Name Comma-Separated Values (CSV) Object 4140 4141 4143 4146 4149 4150 4151 4152 4153 4154 4155 4156 4157 4159 4162 4165 4166 4167 4168 4169 4170 4171 4172 4173 4175 4176 4179 4180 4183 4184 4185 4186 4187 4189 4190 4191 4193 4194 4197 4198 4199 4200 4201 4203 4204 4205 4207 4209 4210 4212 4213 4214 4215 4216 4218 4219 4220 4222 4223 4226 4227 4230 4231 4234 4235 4238 4239 4242 4243 4246 4247 4250 4251 4253 4254 4255 4256 4257 4259 4260 4261 4262 4263 4266 4267 4270 4271 4272 4273 4274 4275 4277 4278 4279 4281 4284 4285 END 4287 9.4. RDE Host Object 4289 Copyright (c) 2011 IETF Trust and the persons identified as authors 4290 of the code. All rights reserved. 4292 Redistribution and use in source and binary forms, with or without 4293 modification, are permitted provided that the following conditions 4294 are met: 4296 o Redistributions of source code must retain the above copyright 4297 notice, this list of conditions and the following disclaimer. 4299 o Redistributions in binary form must reproduce the above copyright 4300 notice, this list of conditions and the following disclaimer in 4301 the documentation and/or other materials provided with the 4302 distribution. 4304 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4305 names of specific contributors, may be used to endorse or promote 4306 products derived from this software without specific prior written 4307 permission. 4309 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4310 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4311 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4312 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4313 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4314 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4315 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4316 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4317 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4318 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4319 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4321 BEGIN 4322 4323 4331 4332 4333 4335 4336 4337 Registry Data Escrow Host provisioning schema 4338 4339 4341 4343 4344 4347 4348 4349 4350 4351 4352 4354 4356 4359 4362 4364 4366 4368 4370 4372 4374 4375 4376 4377 4379 4380 4381 4382 4383 4384 4386 4388 4389 4390 4391 4392 4393 END 4395 9.5. CSV Host Object 4397 Copyright (c) 2012 IETF Trust and the persons identified as authors 4398 of the code. All rights reserved. 4400 Redistribution and use in source and binary forms, with or without 4401 modification, are permitted provided that the following conditions 4402 are met: 4404 o Redistributions of source code must retain the above copyright 4405 notice, this list of conditions and the following disclaimer. 4407 o Redistributions in binary form must reproduce the above copyright 4408 notice, this list of conditions and the following disclaimer in 4409 the documentation and/or other materials provided with the 4410 distribution. 4412 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4413 names of specific contributors, may be used to endorse or promote 4414 products derived from this software without specific prior written 4415 permission. 4417 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4418 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4419 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4420 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4421 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4422 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4423 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4424 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4425 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4426 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4427 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4429 BEGIN 4430 4432 4441 4444 4446 4448 4450 4453 4454 4455 Host Comma-Separated Values (CSV) Object 4456 4457 4459 4462 4465 4466 4467 4468 4469 4470 4471 4472 4473 4475 4478 4481 4482 4483 4484 4485 4486 4487 4488 4489 4491 4492 4495 4496 4498 4499 4500 4501 4502 4504 4505 4506 4508 4509 4511 4512 4513 4514 4515 4517 4518 4519 4521 4522 4525 4526 4527 4528 4529 4530 4532 4533 4534 4536 4539 4540 END 4542 9.6. RDE Contact Object 4544 Copyright (c) 2011 IETF Trust and the persons identified as authors 4545 of the code. All rights reserved. 4547 Redistribution and use in source and binary forms, with or without 4548 modification, are permitted provided that the following conditions 4549 are met: 4551 o Redistributions of source code must retain the above copyright 4552 notice, this list of conditions and the following disclaimer. 4554 o Redistributions in binary form must reproduce the above copyright 4555 notice, this list of conditions and the following disclaimer in 4556 the documentation and/or other materials provided with the 4557 distribution. 4559 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4560 names of specific contributors, may be used to endorse or promote 4561 products derived from this software without specific prior written 4562 permission. 4564 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4565 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4566 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4567 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4568 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4569 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4570 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4571 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4572 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4573 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4574 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4576 BEGIN 4577 4578 4586 4587 4588 4589 4591 4592 4593 Registry Data Escrow contact provisioning schema 4594 4595 4596 4599 4601 4605 4606 4607 4608 4609 4610 4612 4614 4616 4618 4620 4622 4624 4626 4628 4630 4632 4634 4636 4638 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4654 4655 4656 4657 4658 4659 4662 4663 4664 4665 4666 4667 END 4669 9.7. CSV Contact Object 4671 Copyright (c) 2012 IETF Trust and the persons identified as authors 4672 of the code. All rights reserved. 4674 Redistribution and use in source and binary forms, with or without 4675 modification, are permitted provided that the following conditions 4676 are met: 4678 o Redistributions of source code must retain the above copyright 4679 notice, this list of conditions and the following disclaimer. 4681 o Redistributions in binary form must reproduce the above copyright 4682 notice, this list of conditions and the following disclaimer in 4683 the documentation and/or other materials provided with the 4684 distribution. 4686 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4687 names of specific contributors, may be used to endorse or promote 4688 products derived from this software without specific prior written 4689 permission. 4691 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4692 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4693 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4694 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4695 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4696 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4697 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4698 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4699 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4700 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4701 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4703 BEGIN 4704 4706 4715 4718 4720 4722 4724 4727 4728 4729 Contact Comma-Separated Values (CSV) Object 4730 4731 4733 4736 4738 4739 4740 4741 4742 4743 4744 4745 4746 4748 4751 4754 4755 4756 4757 4758 4759 4760 4761 4762 4764 4765 4767 4768 4769 4770 4771 4773 4774 4775 4777 4778 4782 4783 4785 4787 4788 4789 4790 4791 4793 4794 4795 4797 4798 4800 4803 4804 4806 4807 4808 4809 4810 4812 4813 4814 4816 4820 4822 4823 4824 4825 4826 4828 4830 4831 4833 4834 4835 4836 4837 4838 4840 4841 4842 4843 4845 4846 4847 4848 4849 4850 4852 4853 4854 4855 4857 4858 4861 4862 4865 4866 4867 4869 4870 4871 4872 4873 4875 4877 4878 4880 4881 4884 4885 4888 4889 4891 4892 4893 4894 4895 4897 4898 4899 4900 4902 4903 4905 4906 4907 4908 4909 4911 4912 4913 4914 4916 4917 4919 4921 4923 4926 4928 4930 4932 4934 4936 4938 4940 4942 4944 4946 4948 4950 4952 4954 4956 4958 4959 4960 4961 4962 4964 4965 4966 4968 4969 4972 4973 4974 4975 4976 4977 4979 4980 4981 4983 4986 4987 END 4989 9.8. RDE Registrar Object 4991 Copyright (c) 2011 IETF Trust and the persons identified as authors 4992 of the code. All rights reserved. 4994 Redistribution and use in source and binary forms, with or without 4995 modification, are permitted provided that the following conditions 4996 are met: 4998 o Redistributions of source code must retain the above copyright 4999 notice, this list of conditions and the following disclaimer. 5001 o Redistributions in binary form must reproduce the above copyright 5002 notice, this list of conditions and the following disclaimer in 5003 the documentation and/or other materials provided with the 5004 distribution. 5006 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5007 names of specific contributors, may be used to endorse or promote 5008 products derived from this software without specific prior written 5009 permission. 5011 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5012 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5013 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5014 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5015 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5016 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5017 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5018 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5019 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5020 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5021 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5023 BEGIN 5024 5025 5034 5035 5036 5037 5038 5040 5041 5042 Registry Data Escrow registrar provisioning schema 5043 5044 5046 5049 5051 5054 5055 5056 5057 5058 5059 5061 5063 5065 5067 5070 5072 5074 5076 5078 5080 5082 5084 5085 5086 5087 5089 5090 5091 5092 5093 5094 5096 5097 5098 5099 5100 5101 5102 5104 5105 5106 5108 5109 5112 5114 5115 5116 5117 5118 5119 5121 5122 5123 5126 5128 5131 5133 5135 5136 5138 5139 5140 5141 5142 5143 5145 5146 5147 5148 5149 5151 5152 5153 5154 5155 5157 5158 5159 5160 5161 5163 5164 5165 5167 5169 5170 5172 5173 5174 5175 5176 5177 5180 5181 5182 5183 5184 5185 END 5187 9.9. CSV Registrar Object 5189 Copyright (c) 2012 IETF Trust and the persons identified as authors 5190 of the code. All rights reserved. 5192 Redistribution and use in source and binary forms, with or without 5193 modification, are permitted provided that the following conditions 5194 are met: 5196 o Redistributions of source code must retain the above copyright 5197 notice, this list of conditions and the following disclaimer. 5199 o Redistributions in binary form must reproduce the above copyright 5200 notice, this list of conditions and the following disclaimer in 5201 the documentation and/or other materials provided with the 5202 distribution. 5204 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5205 names of specific contributors, may be used to endorse or promote 5206 products derived from this software without specific prior written 5207 permission. 5209 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5210 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5211 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5212 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5213 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5214 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5215 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5216 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5217 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5218 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5219 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5221 BEGIN 5222 5224 5234 5237 5239 5241 5243 5245 5248 5249 5250 Registar Comma-Separated Values (CSV) Object 5251 5252 5254 5257 5260 5261 5262 5263 5264 5265 5266 5267 5268 5270 5273 5276 5277 5278 5279 5280 5281 5282 5283 5284 5286 5287 5290 5291 5294 5295 5296 5297 5298 5299 5301 5302 5303 5304 5306 5307 5311 5312 5314 5316 5317 5318 5319 5320 5322 5323 5324 5326 5327 5328 5329 5330 5331 5332 5333 5335 5336 5337 5338 5339 5340 5341 5342 5344 5345 5349 5352 5353 END 5355 9.10. RDE IDN Table Reference Objects 5357 Copyright (c) 2011 IETF Trust and the persons identified as authors 5358 of the code. All rights reserved. 5360 Redistribution and use in source and binary forms, with or without 5361 modification, are permitted provided that the following conditions 5362 are met: 5364 o Redistributions of source code must retain the above copyright 5365 notice, this list of conditions and the following disclaimer. 5367 o Redistributions in binary form must reproduce the above copyright 5368 notice, this list of conditions and the following disclaimer in 5369 the documentation and/or other materials provided with the 5370 distribution. 5372 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5373 names of specific contributors, may be used to endorse or promote 5374 products derived from this software without specific prior written 5375 permission. 5377 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5378 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5379 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5380 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5381 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5382 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5383 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5384 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5385 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5386 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5387 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5389 BEGIN 5390 5391 5397 5399 5400 5401 Registry Data Escrow IDN provisioning schema 5402 5403 5405 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5421 5422 5423 5424 5425 5427 5428 END 5430 9.11. CSV IDN Language Object 5432 Copyright (c) 2012 IETF Trust and the persons identified as authors 5433 of the code. All rights reserved. 5435 Redistribution and use in source and binary forms, with or without 5436 modification, are permitted provided that the following conditions 5437 are met: 5439 o Redistributions of source code must retain the above copyright 5440 notice, this list of conditions and the following disclaimer. 5442 o Redistributions in binary form must reproduce the above copyright 5443 notice, this list of conditions and the following disclaimer in 5444 the documentation and/or other materials provided with the 5445 distribution. 5447 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5448 names of specific contributors, may be used to endorse or promote 5449 products derived from this software without specific prior written 5450 permission. 5452 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5453 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5454 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5455 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5456 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5457 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5458 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5459 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5460 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5461 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5462 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5464 BEGIN 5465 5467 5474 5477 5479 5482 5483 5484 IDN Language Comma-Separated Values (CSV) Object 5486 5487 5489 5492 5495 5496 5497 5498 5499 5500 5501 5502 5503 5505 5508 5511 5512 5513 5514 5515 5516 5517 5518 5519 5521 5524 5525 END 5527 9.12. EPP Parameters Object 5529 Copyright (c) 2011 IETF Trust and the persons identified as authors 5530 of the code. All rights reserved. 5532 Redistribution and use in source and binary forms, with or without 5533 modification, are permitted provided that the following conditions 5534 are met: 5536 o Redistributions of source code must retain the above copyright 5537 notice, this list of conditions and the following disclaimer. 5539 o Redistributions in binary form must reproduce the above copyright 5540 notice, this list of conditions and the following disclaimer in 5541 the documentation and/or other materials provided with the 5542 distribution. 5544 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5545 names of specific contributors, may be used to endorse or promote 5546 products derived from this software without specific prior written 5547 permission. 5549 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5550 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5551 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5552 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5553 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5554 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5555 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5556 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5557 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5558 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5559 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5561 BEGIN 5562 5563 5571 5572 5573 5575 5576 5577 Registry Data Escrow EPP Parameters schema 5578 5579 5581 5582 5585 5586 5589 5590 5591 5592 5593 5595 5597 5599 5602 5604 5605 5606 5607 5608 5609 END 5611 9.13. NNDN Object 5613 Copyright (c) 2011 IETF Trust and the persons identified as authors 5614 of the code. All rights reserved. 5616 Redistribution and use in source and binary forms, with or without 5617 modification, are permitted provided that the following conditions 5618 are met: 5620 o Redistributions of source code must retain the above copyright 5621 notice, this list of conditions and the following disclaimer. 5623 o Redistributions in binary form must reproduce the above copyright 5624 notice, this list of conditions and the following disclaimer in 5625 the documentation and/or other materials provided with the 5626 distribution. 5628 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5629 names of specific contributors, may be used to endorse or promote 5630 products derived from this software without specific prior written 5631 permission. 5633 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5634 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5635 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5636 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5637 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5638 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5639 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5640 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5641 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5642 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5643 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5645 BEGIN 5646 5647 5654 5655 5657 5658 5659 Registry Data Escrow NNDN provisioning schema 5660 5661 5663 5665 5666 5669 5670 5671 5672 5673 5674 5676 5679 5681 5683 5685 5687 5688 5689 5690 5692 5693 5694 5695 5696 5697 5698 5700 5701 5702 5703 5705 5706 5707 5709 5710 5711 5712 5713 5714 5717 5718 5719 5720 5721 5722 END 5724 9.14. CSV NNDN Object 5726 Copyright (c) 2013 IETF Trust and the persons identified as authors 5727 of the code. All rights reserved. 5729 Redistribution and use in source and binary forms, with or without 5730 modification, are permitted provided that the following conditions 5731 are met: 5733 o Redistributions of source code must retain the above copyright 5734 notice, this list of conditions and the following disclaimer. 5736 o Redistributions in binary form must reproduce the above copyright 5737 notice, this list of conditions and the following disclaimer in 5738 the documentation and/or other materials provided with the 5739 distribution. 5741 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5742 names of specific contributors, may be used to endorse or promote 5743 products derived from this software without specific prior written 5744 permission. 5746 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5747 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5748 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5749 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5750 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5751 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5752 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5753 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5754 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5755 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5756 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5758 BEGIN 5759 5761 5769 5772 5774 5776 5779 5780 5781 NNDN (NNDN's not domain name) (CSV) Object 5782 5783 5785 5788 5791 5792 5793 5794 5795 5796 5797 5798 5799 5801 5804 5807 5808 5809 5810 5811 5812 5813 5814 5815 5817 5818 5821 5822 5825 5826 5829 5830 5831 5832 5833 5835 5836 5837 5839 5840 5844 5847 5848 END 5850 9.15. Policy Object 5852 Copyright (c) 2011 IETF Trust and the persons identified as authors 5853 of the code. All rights reserved. 5855 Redistribution and use in source and binary forms, with or without 5856 modification, are permitted provided that the following conditions 5857 are met: 5859 o Redistributions of source code must retain the above copyright 5860 notice, this list of conditions and the following disclaimer. 5862 o Redistributions in binary form must reproduce the above copyright 5863 notice, this list of conditions and the following disclaimer in 5864 the documentation and/or other materials provided with the 5865 distribution. 5867 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5868 names of specific contributors, may be used to endorse or promote 5869 products derived from this software without specific prior written 5870 permission. 5872 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5873 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5874 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5875 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5876 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5877 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5878 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5879 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5880 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5881 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5882 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5884 BEGIN 5885 5886 5892 5893 5894 Registry Data Escrow Policy schema 5895 5896 5898 5899 5902 5903 5904 5905 5906 5907 5908 5909 5910 5911 END 5913 9.16. Header Object 5915 Copyright (c) 2011 IETF Trust and the persons identified as authors 5916 of the code. All rights reserved. 5918 Redistribution and use in source and binary forms, with or without 5919 modification, are permitted provided that the following conditions 5920 are met: 5922 o Redistributions of source code must retain the above copyright 5923 notice, this list of conditions and the following disclaimer. 5925 o Redistributions in binary form must reproduce the above copyright 5926 notice, this list of conditions and the following disclaimer in 5927 the documentation and/or other materials provided with the 5928 distribution. 5930 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5931 names of specific contributors, may be used to endorse or promote 5932 products derived from this software without specific prior written 5933 permission. 5935 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5936 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5937 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5938 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5939 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5940 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5941 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5942 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5943 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5944 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5945 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5947 BEGIN 5948 5949 5956 5957 5959 5960 5961 Registry Data Escrow Header schema 5962 5963 5965 5966 5969 5970 5971 5972 5973 5974 5975 5977 5978 5979 5980 5982 5983 5984 5985 5986 5987 5988 5989 5990 END 5992 10. Internationalization Considerations 5994 Data Escrow deposits are represented in XML, which provides native 5995 support for encoding information using the Unicode character set and 5996 its more compact representations including UTF-8. Conformant XML 5997 processors recognize both UTF-8 and UTF-16. Though XML includes 5998 provisions to identify and use other character encodings through use 5999 of an "encoding" attribute in an declaration, use of UTF-8 is 6000 RECOMMENDED. 6002 11. IANA Considerations 6004 This document uses URNs to describe XML namespaces and XML schemas 6005 conforming to a registry mechanism described in [RFC3688]. Fourteen 6006 URI assignments have been registered by the IANA. 6008 Registration request for the RDE CSV namespace: 6010 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6012 Registrant Contact: See the "Author's Address" section of this 6013 document. 6015 XML: None. Namespace URIs do not represent an XML specification. 6017 Registration request for the RDE CSV XML schema: 6019 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6021 Registrant Contact: See the "Author's Address" section of this 6022 document. 6024 See the "Formal Syntax" section of this document. 6026 Registration request for the RDE domain namespace: 6028 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6030 Registrant Contact: See the "Author's Address" section of this 6031 document. 6033 XML: None. Namespace URIs do not represent an XML specification. 6035 Registration request for the RDE domain XML schema: 6037 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6038 Registrant Contact: See the "Author's Address" section of this 6039 document. 6041 See the "Formal Syntax" section of this document. 6043 Registration request for the CSV domain namespace: 6045 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6047 Registrant Contact: See the "Author's Address" section of this 6048 document. 6050 XML: None. Namespace URIs do not represent an XML specification. 6052 Registration request for the CSV domain XML schema: 6054 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6056 Registrant Contact: See the "Author's Address" section of this 6057 document. 6059 See the "Formal Syntax" section of this document. 6061 Registration request for the RDE host namespace: 6063 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6065 Registrant Contact: See the "Author's Address" section of this 6066 document. 6068 XML: None. Namespace URIs do not represent an XML specification. 6070 Registration request for the RDE host XML schema: 6072 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6074 Registrant Contact: See the "Author's Address" section of this 6075 document. 6077 See the "Formal Syntax" section of this document. 6079 Registration request for the CSV host namespace: 6081 URI: urn:ietf:params:xml:ns:csvHost-1.0 6083 Registrant Contact: See the "Author's Address" section of this 6084 document. 6086 XML: None. Namespace URIs do not represent an XML specification. 6088 Registration request for the CSV host XML schema: 6090 URI: urn:ietf:params:xml:schema:csvHost-1.0 6092 Registrant Contact: See the "Author's Address" section of this 6093 document. 6095 See the "Formal Syntax" section of this document. 6097 Registration request for the RDE contact namespace: 6099 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6101 Registrant Contact: See the "Author's Address" section of this 6102 document. 6104 XML: None. Namespace URIs do not represent an XML specification. 6106 Registration request for the RDE contact XML schema: 6108 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6110 Registrant Contact: See the "Author's Address" section of this 6111 document. 6113 See the "Formal Syntax" section of this document. 6115 Registration request for the CSV contact namespace: 6117 URI: urn:ietf:params:xml:ns:csvContact-1.0 6119 Registrant Contact: See the "Author's Address" section of this 6120 document. 6122 XML: None. Namespace URIs do not represent an XML specification. 6124 Registration request for the CSV contact XML schema: 6126 URI: urn:ietf:params:xml:schema:csvContact-1.0 6128 Registrant Contact: See the "Author's Address" section of this 6129 document. 6131 See the "Formal Syntax" section of this document. 6133 Registration request for the RDE registrar namespace: 6135 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6137 Registrant Contact: See the "Author's Address" section of this 6138 document. 6140 XML: None. Namespace URIs do not represent an XML specification. 6142 Registration request for the RDE registrar XML schema: 6144 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6146 Registrant Contact: See the "Author's Address" section of this 6147 document. 6149 See the "Formal Syntax" section of this document. 6151 Registration request for the CSV registrar namespace: 6153 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6155 Registrant Contact: See the "Author's Address" section of this 6156 document. 6158 XML: None. Namespace URIs do not represent an XML specification. 6160 Registration request for the CSV registrar XML schema: 6162 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6164 Registrant Contact: See the "Author's Address" section of this 6165 document. 6167 See the "Formal Syntax" section of this document. 6169 Registration request for the RDE IDN namespace: 6171 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6173 Registrant Contact: See the "Author's Address" section of this 6174 document. 6176 XML: None. Namespace URIs do not represent an XML specification. 6178 Registration request for the RDE IDN XML schema: 6180 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6181 Registrant Contact: See the "Author's Address" section of this 6182 document. 6184 See the "Formal Syntax" section of this document. 6186 Registration request for the CSV IDN namespace: 6188 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6190 Registrant Contact: See the "Author's Address" section of this 6191 document. 6193 XML: None. Namespace URIs do not represent an XML specification. 6195 Registration request for the CSV IDN XML schema: 6197 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6199 Registrant Contact: See the "Author's Address" section of this 6200 document. 6202 See the "Formal Syntax" section of this document. 6204 Registration request for the RDE NNDN namespace: 6206 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6208 Registrant Contact: See the "Author's Address" section of this 6209 document. 6211 XML: None. Namespace URIs do not represent an XML specification. 6213 Registration request for the RDE NNDN XML schema: 6215 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6217 Registrant Contact: See the "Author's Address" section of this 6218 document. 6220 See the "Formal Syntax" section of this document. 6222 Registration request for the CSV NNDN namespace: 6224 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6226 Registrant Contact: See the "Author's Address" section of this 6227 document. 6229 XML: None. Namespace URIs do not represent an XML specification. 6231 Registration request for the CSV NNDN XML schema: 6233 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6235 Registrant Contact: See the "Author's Address" section of this 6236 document. 6238 See the "Formal Syntax" section of this document. 6240 Registration request for the RDE EPP parameters namespace: 6242 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6244 Registrant Contact: See the "Author's Address" section of this 6245 document. 6247 XML: None. Namespace URIs do not represent an XML specification. 6249 Registration request for the RDE EPP parameters XML schema: 6251 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6253 Registrant Contact: See the "Author's Address" section of this 6254 document. 6256 See the "Formal Syntax" section of this document. 6258 12. Security Considerations 6260 This specification does not define the security mechanisms to be used 6261 in the transmission of the data escrow deposits, since it only 6262 specifies the minimum necessary to enable the rebuilding of a 6263 Registry from deposits without intervention from the original 6264 Registry. 6266 Depending on local policies, some elements or most likely, the whole 6267 deposit will be considered confidential. As such the Registry 6268 transmitting the data to the Escrow Agent SHOULD take all the 6269 necessary precautions like encrypting the data itself and/or the 6270 transport channel to avoid inadvertent disclosure of private data. 6272 It is also of the utmost importance the authentication of the parties 6273 passing data escrow deposit files. The Escrow Agent SHOULD properly 6274 authenticate the identity of the Registry before accepting data 6275 escrow deposits. In a similar manner, the Registry SHOULD 6276 authenticate the identity of the Escrow Agent before submitting any 6277 data. 6279 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6280 checking mechanisms to ensure the data transmitted is what the source 6281 intended. Validation of the contents by the Escrow Agent is 6282 RECOMMENDED to ensure not only the file was transmitted correctly 6283 from the Registry, but also the contents are also "meaningful". 6285 13. Acknowledgments 6287 Parts of this document are based on EPP [RFC5730] and related RFCs by 6288 Scott Hollenbeck. 6290 TBD 6292 14. Change History 6294 [[RFC Editor: Please remove this section.]] 6296 14.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to 6297 -dnrd-objects-mapping-00 6299 1. Added definition for child elements under the element. 6301 2. Added definition for child elements under the element. 6303 3. Added definition for child elements under the element. 6305 4. Rewrote the IDN Variants Handling section to use the variant 6306 states as described in ICANN's Study of Issues Related to the 6307 Management of IDN Variant TLDs. 6309 5. Renamed to in the . 6311 6. Renamed to in the element. 6313 7. Renamed to in the element. 6315 8. Added element under element. 6317 9. Fixed some typographical errors and omissions. 6319 14.2. Changes from version 00 to 01 6321 1. Specify OPTIONAL elements in the draft. 6323 2. Added NNDN object to support list of reserved names and different 6324 IDN variants models. 6326 3. Removed subordinated host element from the domain object. 6328 4. Added eppParams object. 6330 5. Added variantGenerator element to the domain object. 6332 6. Added lgr to the IDN table object. 6334 14.3. Changes from version 01 to 02 6336 1. Updates to the all objects based on feedback from the list. 6338 2. Start of XML and CSV drafts merge. 6340 3. Added header object. 6342 4. Added report object. 6344 5. Added notification object. 6346 6. Added Data Escrow Agent Extended Verification Process section. 6348 7. Added Notifications from Registries to Third Parties. 6350 8. Added Notifications from Data Escrow Agents to Third Parties. 6352 9. Added FULL, DIFF deposit examples using the XML model only. 6354 14.4. Changes from version 02 to 03 6356 1. Remove authinfo from the XML Schema. 6358 2. Resend attribute is now an element 6360 3. Scope attribute added to policy object. 6362 14.5. Changes from version 03 to 04 6364 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into 6365 draft-arias-noguchi-dnrd-objects-mapping-02. 6367 2. Changed the cksum attribute of to use CRC32 and 6368 changed all of the sample cksum values to use CRC32, based on 6369 feedback from David Kipling. 6371 3. Changed the optional element to be an optional 6372 "sep" attribute value of the element with a default 6373 value of "," based on feedback from David Kipling. 6375 4. Added support for the optional "parent" attribute for the to the 6376 CSV fields to indicate a field as a reference to a parent 6377 object, based on feedback from David Kipling. 6379 5. Added support for the CSV model for the NNDN. 6381 6. Added support to delete hosts based on roid. 6383 7. Added mirrored state to NNDN 6385 8. Minor fixes to XML XSDs. 6387 9. The Report and Notification objects were moved to 6388 draft-lozano-icann-registry-interfaces 6390 10. The section Data escrow notifications was moved to 6391 draft-lozano-icann-registry-interfaces 6393 11. Removed references to the , , and 6394 from the "hostStatuses" and "hostAddresses" CSV 6395 files. 6397 12. Removed references to the , , and 6398 from the "contactStatuses" CSV file. 6400 13. Removed references to the , , and 6401 from the "domainContacts", "domainStatuses", 6402 and "domainNameServers" CSV files. 6404 14. Changed to . 6406 15. Replaced use of to new field 6407 in the "domain", "idnLanguage", and "NNDN" CSV files. 6409 16. Replaced use of with in the 6410 "host" element. 6412 17. Changed the foreign key of the hosts to use 6413 instead of and removed use of in 6414 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6415 files. 6417 18. Added use of the MUST keyword for CSV fields that are required 6418 to be supported in an EPP based system. 6420 19. Removed use of the field element for the 6421 "registrar" CSV file. 6423 20. Added definition of field element. 6425 15. Example of a full deposit using the XML model 6427 Example of a full deposit using the XML model: 6429 6430 6446 2010-10-17T00:00:00Z 6447 6448 1.0 6449 urn:ietf:params:xml:ns:rdeHeader-1.0 6450 6451 urn:ietf:params:xml:ns:rdeContact-1.0 6452 6453 urn:ietf:params:xml:ns:rdeHost-1.0 6454 6455 urn:ietf:params:xml:ns:rdeDomain-1.0 6456 6457 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6458 6459 urn:ietf:params:xml:ns:rdeIDN-1.0 6460 6461 urn:ietf:params:xml:ns:rdeNNDN-1.0 6462 6463 urn:ietf:params:xml:ns:rdeEppParams-1.0 6464 6465 6467 6468 6469 6470 6471 test 6472 2 6474 6475 1 6477 6478 1 6480 6481 1 6483 6484 1 6486 6487 1 6489 6490 1 6492 6493 6495 6496 6497 example1.test 6498 Dexample1-TEST 6499 6500 jd1234 6501 sh8013 6502 sh8013 6503 6504 ns1.example.com 6505 ns1.example1.test 6506 6507 RegistrarX 6508 RegistrarX 6509 1999-04-03T22:00:00.0Z 6510 2015-04-03T22:00:00.0Z 6511 6513 6514 6515 example2.test 6516 Dexample2-TEST 6517 6518 6519 jd1234 6520 sh8013 6521 sh8013 6522 RegistrarX 6523 RegistrarX 6524 1999-04-03T22:00:00.0Z 6525 2015-04-03T22:00:00.0Z 6526 6528 6529 6530 ns1.example1.test 6531 Hns1_example_test-TEST 6532 6533 6534 192.0.2.2 6535 192.0.2.29 6536 1080:0:0:0:8:800:200C:417A 6537 6538 RegistrarX 6539 RegistrarX 6540 1999-05-08T12:10:00.0Z 6541 RegistrarX 6542 2009-10-03T09:34:00.0Z 6543 6545 6546 6547 sh8013 6548 Csh8013-TEST 6549 6550 6551 6552 John Doe 6553 Example Inc. 6554 6555 123 Example Dr. 6556 Suite 100 6557 Dulles 6558 VA 6559 20166-6503 6560 US 6561 6562 6563 +1.7035555555 6564 6565 +1.7035555556 6566 6567 jdoe@example.test 6568 6569 RegistrarX 6570 RegistrarX 6571 6572 2009-09-13T08:01:00.0Z 6573 6574 RegistrarX 6575 6576 2009-11-26T09:10:00.0Z 6577 6578 2009-12-03T09:05:00.0Z 6579 6580 6581 6582 6583 6584 6586 6587 6588 RegistrarX 6589 Registrar X 6590 123 6591 ok 6592 6593 6594 123 Example Dr. 6595 6596 Suite 100 6597 6598 Dulles 6599 VA 6600 20166-6503 6601 US 6602 6603 6604 +1.7035555555 6605 6606 +1.7035555556 6607 6608 jdoe@example.test 6609 6610 http://www.example.test 6611 6612 6613 whois.example.test 6614 6615 http://whois.example.test 6616 6617 6618 2005-04-23T11:49:00.0Z 6619 6620 2009-02-17T17:51:00.0Z 6621 6622 6624 6625 6626 6627 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 6628 6629 6630 http://registro.br/dominio/regras.html 6631 6632 6634 6635 6636 xn--exampl-gva.test 6637 pt-BR 6638 example1.test 6639 withheld 6640 2005-04-23T11:49:00.0Z 6641 6643 6644 6645 1.0 6646 en 6647 6648 urn:ietf:params:xml:ns:domain-1.0 6649 6650 6651 urn:ietf:params:xml:ns:contact-1.0 6653 6654 6655 urn:ietf:params:xml:ns:host-1.0 6656 6657 6658 urn:ietf:params:xml:ns:rgp-1.0 6659 6660 urn:ietf:params:xml:ns:secDNS-1.1 6661 6662 6663 6664 6665 6666 6667 6668 6669 6670 6671 6672 6673 6674 6675 6676 6677 6678 6679 6680 6683 6684 6686 16. Example of differential deposit using the XML model 6688 Example of a differential deposit using the XML model: 6690 6691 6706 2010-10-17T00:00:00Z 6707 6708 1.0 6709 urn:ietf:params:xml:ns:rdeHeader-1.0 6710 6711 urn:ietf:params:xml:ns:rdeContact-1.0 6712 6713 urn:ietf:params:xml:ns:rdeHost-1.0 6714 6715 urn:ietf:params:xml:ns:rdeDomain-1.0 6716 6717 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6718 6719 urn:ietf:params:xml:ns:rdeIDN-1.0 6720 6721 urn:ietf:params:xml:ns:rdeNNDN-1.0 6722 6723 urn:ietf:params:xml:ns:rdeEppParams-1.0 6724 6725 6727 6728 6729 6730 example2.test 6731 6732 6734 6735 6736 6737 6738 test 6739 1 6741 6742 1 6744 6745 1 6747 6748 1 6750 6751 1 6753 6754 1 6756 6757 1 6759 6760 6761 6762 6764 17. Example of a full deposit using the CSV model 6766 Example of a full deposit using the CSV model: 6768 6769 6791 2010-10-18T00:00:00Z 6792 6793 1.0 6794 urn:ietf:params:xml:ns:csvDomain-1.0 6795 urn:ietf:params:xml:ns:csvHost-1.0 6796 urn:ietf:params:xml:ns:csvContact-1.0 6797 urn:ietf:params:xml:ns:csvRegistrar-1.0 6798 urn:ietf:params:xml:ns:csvIDN-1.0 6799 urn:ietf:params:xml:ns:csvNNDN-1.0 6800 urn:ietf:params:xml:ns:rdeEppParams-1.0 6801 6802 6803 6804 test 6805 6806 4 6807 6808 6809 2 6810 6811 6812 2 6813 6814 6815 1 6816 6817 6818 2 6819 6820 6821 1 6822 6823 6824 1 6825 6826 6827 6828 6829 6830 6831 6832 6833 6834 6835 6836 6837 6838 6839 6840 6841 6842 6843 6844 6845 6847 domain-YYYYMMDD.csv 6848 6849 6850 6851 6852 6853 6854 6855 6856 6857 6858 6860 domainContacts-YYYYMMDD.csv 6861 6862 6863 6864 6865 6866 6867 6868 6869 6870 6871 6872 6873 6875 domainStatuses-YYYYMMDD.csv 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6887 domainNameServers-YYYYMMDD.csv 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6903 dnssec-ds-YYYYMMDD.csv 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 6914 6915 6916 6917 6919 dnssec-key-YYYYMMDD.csv 6920 6921 6922 6923 6924 6925 6926 6927 6928 6929 6930 6931 6932 6933 6934 6935 6936 6938 domainTransfer-YYYYMMDD.csv 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6960 host-YYYYMMDD.csv 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6974 hostStatuses-YYYYMMDD.csv 6975 6976 6977 6978 6979 6980 6981 6982 6984 6985 6986 6988 hostAddresses-YYYYMMDD.csv 6989 6990 6991 6992 6993 6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010 7011 7012 7014 contact-YYYYMMDD.csv 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7028 contactStatuses-YYYYMMDD.csv 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 7042 7043 7044 7045 7046 7047 7049 contactPostal-YYYYMMDD.csv 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7067 contactTransfer-YYYYMMDD.csv 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7081 7082 7083 7084 7085 7086 7088 contactDisclose-YYYYMMDD.csv 7089 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7120 registrar-YYYYMMDD.csv 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7134 idnLanguage-YYYYMMDD.csv 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7151 NNDN-YYYYMMDD.csv 7152 7153 7154 7155 7156 7157 1.0 7158 en 7159 urn:ietf:params:xml:ns:domain-1.0 7160 7161 urn:ietf:params:xml:ns:host-1.0 7162 7163 urn:ietf:params:xml:ns:contact-1.0 7164 7165 7166 urn:ietf:params:xml:ns:secDNS-1.1 7167 7168 urn:ietf:params:xml:ns:rgp-1.0 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7195 18. Example of differential deposit using the CSV model 7197 Example of a differential deposit using the CSV model: 7199 7200 7223 2010-10-18T00:00:00Z 7224 7225 1.0 7226 urn:ietf:params:xml:ns:csvDomain-1.0 7227 urn:ietf:params:xml:ns:csvHost-1.0 7228 urn:ietf:params:xml:ns:csvContact-1.0 7229 urn:ietf:params:xml:ns:csvRegistrar-1.0 7230 urn:ietf:params:xml:ns:csvIDN-1.0 7231 7232 7233 7234 7235 7236 7237 7238 7239 7241 domain-delete-YYYYMMDD.csv 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7254 domainContacts-delete-YYYYMMDD.csv 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7266 domainStatuses-delete-YYYYMMDD.csv 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7278 domainNameServers-delete-YYYYMMDD.csv 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7293 dnssec-ds-delete-YYYYMMDD.csv 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7308 dnssec-key-delete-YYYYMMDD.csv 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7320 domainTransfer-delete-YYYYMMDD.csv 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7333 host-delete-YYYYMMDD.csv 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7345 hostStatuses-delete-YYYYMMDD.csv 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7357 hostAddresses-delete-YYYYMMDD.csv 7358 7359 7360 7361 7362 7363 7364 7365 7367 7368 7369 7371 contact-delete-YYYYMMDD.csv 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7383 contactStatuses-delete-YYYYMMDD.csv 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7395 contactPostal-delete-YYYYMMDD.csv 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7407 contactTransfer-delete-YYYYMMDD.csv 7408 7409 7410 7411 7412 7413 7414 7415 7416 7418 contactDisclose-delete-YYYYMMDD.csv 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7431 registrar-delete-YYYYMMDD.csv 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7444 idnLanguage-delete-YYYYMMDD.csv 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7457 NNDN-delete-YYYYMMDD.csv 7458 7459 7460 7461 7462 7463 7464 7465 test 7466 7467 4 7468 7469 7470 2 7471 7472 7473 2 7474 7475 7476 1 7477 7478 7479 2 7480 7481 7482 1 7483 7484 7485 1 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7508 domain-YYYYMMDD.csv 7509 7510 7512 7513 7514 7515 7516 7517 7518 7519 7520 7522 domainContacts-YYYYMMDD.csv 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7537 domainStatuses-YYYYMMDD.csv 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7549 domainNameServers-YYYYMMDD.csv 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7565 dnssec-YYYYMMDD.csv 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7584 domainTransfer-YYYYMMDD.csv 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7606 host-YYYYMMDD.csv 7607 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7621 hostStatuses-YYYYMMDD.csv 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7634 hostAddresses-YYYYMMDD.csv 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7660 contact-YYYYMMDD.csv 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7674 contactStatuses-YYYYMMDD.csv 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7695 contactPostal-YYYYMMDD.csv 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7713 contactTransfer-YYYYMMDD.csv 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7734 contactDisclose-YYYYMMDD.csv 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7767 registrar-YYYYMMDD.csv 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7781 idnLanguage-YYYYMMDD.csv 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7798 NNDN-YYYYMMDD.csv 7799 7800 7802 7803 7804 7805 1.0 7806 en 7807 urn:ietf:params:xml:ns:domain-1.0 7808 7809 urn:ietf:params:xml:ns:host-1.0 7810 7811 urn:ietf:params:xml:ns:contact-1.0 7812 7813 7814 urn:ietf:params:xml:ns:secDNS-1.1 7815 7816 urn:ietf:params:xml:ns:rgp-1.0 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7843 19. References 7844 19.1. Normative References 7846 [ISO-3166-1] 7847 International Organization for Standardization, "Codes for 7848 the representation of names of countries and their 7849 subdivisions -- Part 1: Country codes", ISO Standard 3166, 7850 November 2006. 7852 [ITU-E164] 7853 International Telecommunication Union, "The international 7854 public telecommunication numbering plan", ITU-T 7855 Recommendation E.164, February 2005. 7857 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 7858 Requirement Levels", BCP 14, RFC 2119, March 1997. 7860 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 7861 Internet: Timestamps", RFC 3339, July 2002. 7863 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 7864 the Extensible Provisioning Protocol (EPP)", RFC 3915, 7865 September 2004. 7867 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 7868 STD 69, RFC 5730, August 2009. 7870 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 7871 Domain Name Mapping", STD 69, RFC 5731, August 2009. 7873 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 7874 Host Mapping", STD 69, RFC 5732, August 2009. 7876 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 7877 Contact Mapping", STD 69, RFC 5733, August 2009. 7879 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 7880 Security Extensions Mapping for the Extensible 7881 Provisioning Protocol (EPP)", RFC 5910, May 2010. 7883 19.2. Informative References 7885 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 7886 September 1981. 7888 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 7889 January 2004. 7891 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 7892 September 2004. 7894 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 7895 Architecture", RFC 4291, February 2006. 7897 [variantTLDsReport] 7898 Internet Corporation for Assigned Names and Numbers 7899 (ICANN), "A Study of Issues Related to the Management of 7900 IDN Variant TLDs", February 2012, . 7904 URIs 7906 [1] 7909 Authors' Addresses 7911 Francisco Arias 7912 Internet Corporation for Assigned Names and Numbers 7913 12025 Waterfront Drive, Suite 300 7914 Los Angeles 90292 7915 United States of America 7917 Phone: +1.310.823.9358 7918 Email: francisco.arias@icann.org 7920 Gustavo Lozano 7921 Internet Corporation for Assigned Names and Numbers 7922 12025 Waterfront Drive, Suite 300 7923 Los Angeles 90292 7924 United States of America 7926 Phone: +1.310.823.9358 7927 Email: gustavo.lozano@icann.org 7928 Shoji Noguchi 7929 Japan Registry Services Co., Ltd. 7930 Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda 7931 Chiyoda-ku, Tokyo 101-0065 7932 Japan 7934 Phone: +81.3.5215.8451 7935 Email: noguchi@jprs.co.jp 7937 James Gould 7938 VeriSign, Inc. 7939 12061 Bluemont Way 7940 Reston 20190 7941 United States of America 7943 Email: jgould@verisign.com 7945 Chethan Thippeswamy 7946 VeriSign, Inc. 7947 12061 Bluemont Way 7948 Reston 20190 7949 United States of America 7951 Email: cthippeswamy@verisign.com