idnits 2.17.1 draft-arias-noguchi-dnrd-objects-mapping-05.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 (September 26, 2013) is 3865 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: March 30, 2014 S. Noguchi 6 JPRS 7 J. Gould 8 C. Thippeswamy 9 VeriSign 10 September 26, 2013 12 Domain Name Registration Data (DNRD) Objects Mapping 13 draft-arias-noguchi-dnrd-objects-mapping-05 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 March 30, 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 . . . . . . . . . . . . . . . . . . . . . . . 36 69 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 45 70 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 64 71 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 72 72 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 75 73 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 80 74 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 82 75 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 82 76 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 84 77 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 78 8. Data escrow agent extended verification process . . . . . . . 85 79 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 86 80 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 86 81 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 95 82 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 98 83 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 102 84 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 104 85 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 108 86 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 110 87 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 117 88 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 121 89 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 125 90 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 127 91 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 129 92 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 130 93 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 133 94 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 135 95 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 137 97 10. Internationalization Considerations . . . . . . . . . . . . . 140 98 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 140 99 12. Security Considerations . . . . . . . . . . . . . . . . . . . 145 100 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 146 101 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 146 102 14.1. Changes from 103 draft-arias-noguchi-registry-data-escrow-02 to 104 -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . 146 105 14.2. Changes from version 00 to 01 . . . . . . . . . . . . . . 147 106 14.3. Changes from version 01 to 02 . . . . . . . . . . . . . . 147 107 14.4. Changes from version 02 to 03 . . . . . . . . . . . . . . 147 108 14.5. Changes from version 03 to 04 . . . . . . . . . . . . . . 147 109 14.6. Changes from version 04 to 05 . . . . . . . . . . . . . . 149 110 15. Example of a full deposit using the XML model . . . . . . . . 149 111 16. Example of differential deposit using the XML model . . . . . 155 112 17. Example of a full deposit using the CSV model . . . . . . . . 156 113 18. Example of differential deposit using the CSV model . . . . . 165 114 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 174 115 19.1. Normative References . . . . . . . . . . . . . . . . . . 174 116 19.2. Informative References . . . . . . . . . . . . . . . . . 175 117 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 175 119 1. Introduction 121 This document defines the data escrow structure of the standard set 122 of objects for a Domain Name Registry which include: 124 o Domain: Internet domain names that are typically provisioned in a 125 Domain Name Registry using the EPP domain name mapping [RFC5731]. 126 The attributes defined in the EPP domain name mapping [RFC5731] 127 are fully supported by this document. 129 o Host: Internet host names that are typically provisioned in a 130 Domain Name Registry using the EPP host mapping [RFC5732]. The 131 attributes defined in the EPP host mapping [RFC5732] are fully 132 supported by this document. 134 o Contact: Individual or organization social information provisioned 135 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 136 The attributes defined in the EPP contact mapping [RFC5733] are 137 fully supported by this document. 139 o Registrar: The organization that sponsors objects like domains, 140 hosts, and contacts in a Domain Name Registry. 142 o NNDN (NNDN's not domain name): A lightweight domain-like object 143 that is not linked to a Registrar. 145 This document defines the following pseudo-objects: 147 o IDN Table Reference: Internationalized Domain Names (IDN) included 148 in the Domain Object Data Escrow include references to the IDN 149 Table and Policy used in IDN registration. 151 o EPP parameters: Definition of the specific EPP parameters 152 supported by the Registry Operator. 154 o Header: Used to specify counters of objects in the database at a 155 certain point in time (watermark). 157 o Policy: Used to specify OPTIONAL elements from this specification 158 that are REQUIRED based on the business model of the registry. 160 2. Models 162 This document defines two different models that can be used to 163 deposit data escrow objects: 165 o XML: The XML model includes all of the deposit information (meta- 166 data and data) in an XML document. The definition of the XML 167 format is fully defined in the XML schemas. As a convention, the 168 objects represented using the XML model are referenced using RDE 169 and an XML namespace that is prefixed with "rde". For example, 170 the Domain Name object represented using the XML model can be 171 referred to as the RDE Domain Name with the XML namespace 172 including rdeDomain (urn:ietf:params:xml:ns:rdeDomain-1.0). 174 o CSV: The CSV model uses XML to define the data escrow format of 175 the data contained in referenced Comma-Separated Values (CSV) 176 files. As a convention, the objects represented using the CSV 177 model are referenced using CSV and an XML namespace that is 178 prefixed with "csv". For example, the Domain Name object 179 represented using the CSV model can be referred to as the CSV 180 Domain Name with the XML namespace including csvDomain 181 (urn:ietf:params:xml:ns:csvDomain-1.0). 183 The data escrow deposit MAY contain a mix of both models but an 184 object MUST be escrowed only in one model. 186 3. Terminology 188 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 189 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 190 document are to be interpreted as described in BCP 14, [RFC2119]. 192 REGISTRY. In the context of this draft the definition will be 193 overloaded (from the definition in the base protocol) to indicate an 194 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 195 NAME. 197 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 198 or any other domain name at any level in the DNS tree for which a 199 Registry (either directly or through and affiliate company) provides 200 Registry Services for other organizations or individuals. For 201 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 203 REGISTRY SERVICES. Services offered by the Registry critical to the 204 following tasks: the provisioning of domain names on receipt of 205 requests and data from registrars; responding to registrar queries 206 for status information relating to the DNS servers for the RCDN; 207 dissemination of RCDN zone files; operation of the Registry DNS 208 servers; and responding to queries for contact and other information 209 concerning DNS registrations in the RCDN. Any other products or 210 services that only a Registry is capable of providing, by reason of 211 its designation as the Registry. Typical examples of Registry 212 Services are: DNS resolution for the RCDN, WHOIS and EPP. 214 ALLOCATED. A status of some label with respect to a zone, whereby 215 the label is associated administratively to some entity that has 216 requested the label. This term (and its cognates "allocation" and 217 "to allocate") may represents the first step on the way to delegation 218 in the DNS. 220 4. General Conventions 222 4.1. Date and Time 224 Numerous fields indicate "dates", such as the creation and expiry 225 dates for domain names. These fields SHALL contain timestamps 226 indicating the date and time in UTC as specified in [RFC3339], with 227 no offset from the zero meridian. 229 4.2. Country names 231 Country identifiers SHALL be represented using two character 232 identifiers as specified in [ISO-3166-1]. 234 4.3. Telephone numbers 236 Telephone numbers (both voice and facsimile) SHALL be formatted based 237 on structures defined in [ITU-E164]. Telephone numbers described in 238 this specification are character strings that MUST begin with a plus 239 sign ("+", ASCII value 0x002B), followed by a country code defined in 240 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 241 a sequence of digits representing the telephone number. 243 4.4. Checksum 245 Checksum of the CSV data escrow files MUST use CRC32, that is the 246 algorithm used in the ISO 3309 standard and in section 8.1.1.6.2 of 247 ITU-T recommendation V.42. 249 4.5. IP addresses 251 IP addresses syntax MUST conform to the text representation of either 252 of, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 253 Addressing Architecture [RFC4291], for IPv6 addresses. 255 4.6. CSV elements 256 4.6.1. element 258 To support a CSV model with the Registry Data Escrow 259 Specification [1], an element is defined for each object that 260 substitutes for the element and for the 261 element, that contains one or more elements. For 262 example, the Domain Name Object (Section 5.1) defines the element, that substitutes for the element, 264 and the element, that substitutes for the element. Both the element and the 266 elements contain one or more 267 elements. The element has the following child elements: 269 Ordered list of CSV fields used in the CSV files. 270 There is one or more child elements that substitute for the 271 abstract element. Each element defines the format 272 of the CSV field contained in the CSV files. The 273 elements support the "type" attribute that defines the XML simple 274 data type of the field element. The elements 275 support the "isRequired" attribute, with a default value of 276 "false", when set to "true" indicates that the field must be non- 277 empty in the CSV files and when set to "false" indicates that the 278 field MAY be empty in the CSV files. The "isRequired" attribute 279 MAY be specifically set for the field elements within the XML 280 schema and MAY be overridden when specifying the fields under the 281 element. The element supports an 282 OPTIONAL "parent" attribute that identifies the field as a 283 reference to a parent object. For example, the field SHOULD set the 285 "parent" attribute to "true" to identify it as the parent domain 286 name of the domain status. 288 A list of one or more CSV files using the child element. The child element defines a 290 reference to the CSV file name and has the following optional 291 attributes: 293 compression If the CSV file is compressed, the "compression" 294 attribute defines the compression format like "gzip" or "zip". 296 encoding Defines the encoding of the CSV file with the default 297 encoding of "UTF-8". 299 cksum Defines the checksum of the CSV file using CRC32, as 300 defined in Section 4.4. This attribute is used to validate 301 that the full CSV file exists and has not been tampered with. 303 The elements requires a "name" attribute that defines 304 the purpose of the CSV file with values like "domain", "host", 305 "contact". The supported "name" attribute values are defined for 306 each object type. The OPTIONAL "sep" attribute defines the CSV 307 separator character with the default separator character of ",". 309 The following is an example of the 310 element for domain name records where the is set 311 as required with isRequired="true". 313 314 ... 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 334 domain-YYYYMMDD.csv 335 336 337 338 ... 339 341 The following is example of the "domain-YYYYMMDD.csv" file with one 342 record matching the definition. 344 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 345 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 346 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 348 The following is an example of the 349 element for domain name records. 351 352 ... 353 354 355 356 357 358 360 domain-delete-YYYYMMDD.csv 361 362 363 364 ... 365 367 The following is example of the "domain-delete-YYYYMMDD.csv" file 368 with three records that matches the single field. 370 domain1.test 371 domain2.test 372 domainN.test 374 4.6.2. CSV common field elements 376 The element defined in the element 377 (Section 4.6.1) section has child elements that substitute for the 378 abstract element. By convention 379 elements include an 'f' prefix to identify them as field definition 380 elements. There are a set of common field elements that are used 381 across multiple data escrow objects. The common field elements are 382 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 383 using the "rdeCsv" sample namespace prefix. The CSV common field 384 elements include: 386 UTF-8 encoded name field with type="eppcom: 387 labelType". 389 Repository Object IDentifier (ROID) field with 390 type="eppcom:roidType" and isRequired="true". 392 Registrant contact identifier with 393 type="eppcom:clIDType". 395 The object status description, which is 396 free form text describing the rationale for the status, with 397 type="normalizedString". 399 Identifier of client (registrar) that sponsors the 400 object with type="eppcom:clIDType" and isRequired="true". 402 Identifier of the registrar, defined in Section 5.4, 403 of the client that created the object with type="eppcom:clIDType". 405 Identifier of client that created the object with 406 type="eppcom:clIDType". 408 Identifier of the registrar, defined in Section 5.4, 409 of the client that updated the object with type="eppcom:clIDType". 411 Identifier of client that updated the object with 412 type="eppcom:clIDType". 414 Identifier of the registrar, defined in Section 5.4, 415 of the client that requested the transfer with type="eppcom: 416 clIDType". 418 Identifier of client that requested the transfer with 419 type="eppcom:clIDType". 421 Identifier of the registrar, defined in Section 5.4, 422 of the client that should take or took action with type="eppcom: 423 clIDType". 425 Identifier of client that should take or took action 426 for transfer with type="eppcom:clIDType". 428 Created date of object with type="dateTime". 430 Updated date of object with type="dateTime". 432 Expiration date of object with type="dateTime". 434 Date that transfer was requested with 435 type="dateTime". 437 Date that transfer action should be taken or has 438 been taken with type="dateTime". 440 Date of last transfer with type="dateTime". 442 State of the most recent transfer request with 443 type="eppcom:trStatusType". 445 General token field with type="token". 447 General language field with type="language". 449 IDN Table Identifier used for IDN domain names 450 with type="token". 452 General positive integer field with 453 type="positiveInteger". 455 Contains the URL of an object like a registrar object 456 with type="anyURI". 458 Custom field with name attribute that defines the 459 custom field name" with type="token". 461 4.7. Internationalized and Localized Elements 463 Some elements MAY be provided in either internationalized form 464 ("int") or provided in localized form ("loc"). Those elements use a 465 field value or "isLoc" attribute to specify the form used. If an 466 "isLoc" attribute is used, a value of "true" indicates the use of the 467 localized form and a value of "false" indicates the use of the 468 internationalized form. This MAY override the form specified for a 469 parent element. A value of "int" is used to indicate the 470 internationalized form and a value of "loc" is used to indicate the 471 localized form. When the internalized form ("int") is provided, the 472 field value MUST be represented in a subset of UTF-8 that can be 473 represented in the 7-bit US-ASCII character set. When the localized 474 form ("loc") is provided, the field value MAY be represented in 475 unrestricted UTF-8. Some of the field elements below of the 476 "registrar" element specify the 477 internationalized form with the isLoc="false" attribute: 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 511 513 registrar-YYYYMMDD.csv 514 515 516 517 ... 518 519 ... 521 The following is an example of using the 522 field value to define the internationalized or localized form of the 523 remainder of the "contactPostal" field values. 525 ... 526 527 ... 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 545 contactPostal-YYYYMMDD.csv 546 547 548 549 ... 550 551 ... 553 5. Object Description 555 This section describes the base objects supported by this 556 specification: 558 5.1. Domain Name Object 560 The domain name object is based on the EPP domain name mapping 561 specified in [RFC5731]. The domain name object supports both the XML 562 Model and the CSV Model, defined in the Models (Section 2) section. 563 The elements used for both models are defined in the following 564 sections. 566 5.1.1. XML Model 568 There are two elements used in the data escrow of the domain name 569 objects for the XML model including the , under the 570 element, and the element, under the 571 element. 573 5.1.1.1. object 575 The domain element is based on the EPP domain response for an 576 authorized client (see Section 3.1.2. of [RFC5731]) with additional 577 data from an EPP Query Response, see Section 3.1.3. of 578 [RFC5731], RGP status from [RFC3915], and data from the EPP command, see Section 5.2.1. of [RFC5910]. 581 A element substitutes for the abstract 582 element to define a concrete definition of a domain. The 583 element can be replaced by other domain definitions 584 using the XML schema substitution groups feature. 586 The element contains the following child elements: 588 o A element that contains the fully qualified name of the 589 domain name object. If the domain name is an IDN, the ASCII 590 Compatible Encoding (ACE) MUST be used. 592 o A element that contains the repository object identifier 593 assigned to the domain name object when it was created. 595 o An OPTIONAL element that contains the fully qualified name 596 of the domain name in Unicode character set. It MUST be provided 597 if available. 599 o An OPTIONAL element that references the IDN Table 600 used for the IDN. This corresponds to the "id" attribute of the 601 element. This element MUST be present if the domain 602 name is an IDN. 604 o An OPTIONAL element is used to indicate that the 605 domain name is an IDN variant. This element contains the domain 606 name used to generate the IDN variant. 608 o One or more elements that contain the current status 609 descriptors associated with the domain name. 611 o Zero or more OPTIONAL element to represent 612 "pendingDelete" sub-statuses, including "redemptionPeriod", 613 "pendingRestore", and "pendingDelete", that a domain name can be 614 in as a result of grace period processing as specified in 615 [RFC3915]. 617 o An OPTIONAL element that contain the identifier for 618 the human or organizational social information object associated 619 as the holder of the domain name object. 621 o Zero or more OPTIONAL elements that contain identifiers 622 for the human or organizational social information objects 623 associated with the domain name object. 625 o An OPTIONAL element that contains the fully qualified names 626 of the delegated host objects or host attributes (name servers) 627 associated with the domain name object. See Section 1.1 of 628 [RFC5731] for a description of the elements used to specify host 629 objects or host attributes. 631 o A element that contains the identifier of the sponsoring 632 registrar. 634 o A element that contains the identifier of the registrar 635 that created the domain name object. An OPTIONAL client attribute 636 is used to specify the client that performed the operation. 638 o An OPTIONAL element that contains the date and time of 639 the domain name object creation. This element MUST be present if 640 the domain name has been allocated. 642 o An OPTIONAL element that contains the date and time 643 identifying the end (expiration) of the domain name object's 644 registration period. This element MUST be present if the domain 645 name has been allocated. 647 o An OPTIONAL element that contains the identifier of the 648 registrar that last updated the domain name object. This element 649 MUST NOT be present if the domain has never been modified. An 650 OPTIONAL client attribute is used to specify the client that 651 performed the operation. 653 o An OPTIONAL element that contains the date and time of 654 the most recent domain-name-object modification. This element 655 MUST NOT be present if the domain name object has never been 656 modified. 658 o An OPTIONAL element that contains the public key 659 information associated with Domain Name System security (DNSSEC) 660 extensions for the domain name as specified in [RFC5910]. 662 o An OPTIONAL element that contains the date and time of 663 the most recent domain object successful transfer. This element 664 MUST NOT be present if the domain name object has never been 665 transfered. 667 o An OPTIONAL element that contains the following child 668 elements related to the last transfer request of the domain name 669 object. This element MUST NOT be present if a transfer request 670 for the domain name has never been created. 672 * A element that contains the state of the most recent 673 transfer request. 675 * A element that contains the identifier of the registrar 676 that requested the domain name object transfer. An OPTIONAL 677 client attribute is used to specify the client that performed 678 the operation. 680 * A element that contains the date and time that the 681 transfer was requested. 683 * An element that contains the identifier of the registrar 684 that SHOULD act upon a PENDING transfer request. For all other 685 status types, the value identifies the registrar that took the 686 indicated action. An OPTIONAL client attribute is used to 687 specify the client that performed the operation. 689 * An element that contains the date and time of a 690 required or completed response. For a PENDING request, the 691 value identifies the date and time by which a response is 692 required before an automated response action will be taken by 693 the registry. For all other status types, the value identifies 694 the date and time when the request was completed. 696 * An OPTIONAL element that contains the end of the 697 domain name object's validity period (expiry date) if the 698 transfer caused or causes a change in the validity period. 700 Example of a domain object: 702 ... 703 704 example1.test 705 Dexample1-TEST 706 707 jd1234 708 sh8013 709 sh8013 710 711 ns1.example.com 712 ns1.example1.test 713 714 RegistrarX 715 RegistrarX 716 1999-04-03T22:00:00.0Z 717 2015-04-03T22:00:00.0Z 718 719 ... 721 5.1.1.2. object 723 The element contains the fully qualified domain 724 name that was deleted and purged. 726 Example of object: 728 ... 729 730 ... 731 732 foo.test 733 bar.test 734 735 ... 736 737 ... 739 5.1.2. CSV Model 741 For the CSV Model of the domain name object, the 742 child element of the element is used to hold the new 743 or updated domain name objects for the deposit. The child element of the element is used to hold 745 the deleted or purged domain name objects for the deposit. Both the 746 and elements contain one or 747 more elements with the following supported "name" 748 attribute values: 750 "domain" Defines the fields and CSV file references used for the 751 domain name object records. 753 The following "csvDomain" field elements, defined for the "domain" 754 element, MUST be used in the "domain" 755 element: 757 Domain name field with type="eppcom:labelType" 758 and isRequired="true". 760 "domain" Defines the fields and CSV file references used for the 761 domain name object records. 763 The following "csvDomain" field elements, defined for the "domain" 764 element, MAY be used in the "domain" 765 element: 767 Fully qualified name of the original 768 IDN domain name object related to the variant domain name 769 object with type="eppcom:labelType". 771 The following "rdeCsv" fields, defined in section CSV common field 772 elements (Section 4.6.2), MUST be used in the "domain" element: 775 Registry Object IDentifier (ROID) for the domain 776 name object. 778 Identifier of client that sponsors the domain name 779 object. 781 Identifier of the registrar, defined in 782 Section 5.4, of the client that created the object. 784 Created date and time of the domain name object. 786 Identifier of the registrar, defined in 787 Section 5.4, of the client that updated the object. 789 Date and time of the last update to the domain 790 name object. 792 Expiration date and time for the domain name 793 object. 795 The following "rdeCsv" fields, defined in section CSV common field 796 elements (Section 4.6.2), MAY be used in the "domain" 797 element: 799 UTF8 encoded domain name for the field element. 802 IDN Table Identifier used for the IDN domain 803 name object that MUST match a field 804 element in the "idnLanguage" CSV files, as defined in 805 Section 5.5.2. 807 Registrant contact identifier for the domain 808 name object. 810 Identifier of client that created the domain name 811 object. 813 Identifier of the client that last updated the 814 domain name object. 816 Date and time of the last transfer for the 817 domain name object. 819 Example of a "domain" element: 821 ... 822 823 ... 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 843 domain-YYYYMMDD.csv 844 845 846 847 ... 848 849 ... 851 Example of the corresponding domain-YYYYMMDD.csv file. The file 852 contains four records (active ASCII domain, pendingDelete domain, 853 original IDN with LANG-1 language rules, and variant IDN with 854 LANG-1 language rules). 856 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 857 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 858 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 859 domain2.test,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 860 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 861 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 862 xn--abc123.test,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 863 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 864 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 865 xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--cbc321.test, 866 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 867 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 869 Example of a "domain" element: 871 ... 872 873 ... 874 875 876 877 878 879 881 domain-delete-YYYYMMDD.csv 882 883 884 885 ... 886 887 ... 889 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 890 file contains three domain name records. 892 domain1.test 893 domain2.test 894 domainN.test 896 "domainContacts" Defines the fields and CSV file references used for 897 the domain name object link records to contact objects, as 898 described in Section 5.3. 900 The following "csvDomain" field elements, defined for the 901 "domainContacts" element, MUST be 902 used in the "domainContacts" element: 904 The contact type for the contact object 905 link with type="domain:contactAttrType". The supported contact 906 type values include "admin" for the administration contact, 907 "billing" for the billing contact, and "tech" for the technical 908 contact. 910 The following "csvDomain" field elements, defined for the "domain" 911 element, MUST be used in the 912 "domainContacts" element: 914 The name of the domain object that is linked to 915 the contact object. 917 The following "csvContact" fields, defined for the "contact" 918 element, MUST be used in the 919 "domainContacts" element: 921 The server-unique contact identifier. 923 Example of a "domainContacts" 924 element: 926 ... 927 928 ... 929 930 931 932 933 934 935 936 938 domainContacts-YYYYMMDD.csv 939 940 941 942 ... 943 944 ... 946 Example of the corresponding domainContacts-YYYYMMDD.csv file. 947 The file contains an admin, tech, and billing contact for the two 948 domain names domain1.test and domain2.test. 950 domain1.test,sh8013,admin 951 domain1.test,mycontactid,tech 952 domain1.test,mycontactid,billing 953 domain2.test,mycontactid,admin 954 domain2.test,sh8013,tech 955 domain2.test,mycontactid,billing 957 Example of a "domainContacts" 958 element: 960 ... 961 962 ... 963 964 965 966 967 968 969 970 972 domainContacts-delete-YYYYMMDD.csv 973 974 975 976 ... 977 978 ... 980 Example of the corresponding domainContacts-delete-YYYYMMDD.csv 981 file. The file contains two tech contact records. 983 domain1.test,mycontactid,tech 984 domain2.test,sh8013,tech 986 "domainStatuses" Defines the fields and CSV file references used for 987 the domain name object statuses. 989 The following "csvDomain" field elements, defined for the 990 "domainStatuses" element, MUST be 991 used in the "domainStatuses" element: 993 The status of the domain name with 994 type="domain:statusValueType". 996 The Registry Grace Period (RGP) status, as 997 a sub-status of the "pendingDelete" status 998 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1000 The following "csvDomain" fields, defined for the "domain" 1001 element, MUST be used in the 1002 "domainStatuses" element: 1004 Domain name of status. 1006 The following "rdeCsv" fields, defined in section CSV common field 1007 elements (Section 4.6.2), MAY be used in the "domainStatuses" 1008 element: 1010 Domain object status description 1011 which is free form text describing the rationale for the 1012 status. 1014 Language of the field. 1016 Example of a "domainStatuses" 1017 element: 1019 ... 1020 1021 ... 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1033 domainStatuses-YYYYMMDD.csv 1034 1035 1036 1037 ... 1038 1039 ... 1041 Example of the corresponding domainStatuses-YYYYMMDD.csv file. 1042 The file contains the statuses for the two domain names 1043 domain1.test and domain2.test. 1045 domain1.test,clientUpdateProhibited,"Disallow update", 1046 en, 1047 domain1.test,clientDeleteProhibited,"Disallow delete", 1048 en, 1049 domain2.test,clientUpdateProhibited,"Disallow update", 1050 en, 1051 domain2.test,pendingDelete,,, 1052 redemptionPeriod 1054 Example of a "domainStatuses" 1055 element: 1057 ... 1058 1059 ... 1060 1061 1062 1063 1064 1065 1066 1068 domainStatuses-delete-YYYYMMDD.csv 1069 1070 1071 1072 ... 1073 1074 ... 1076 Example of the corresponding domainStatuses-delete-YYYYMMDD.csv 1077 file. The file contains two status records. 1079 domain1.test,clientUpdateProhibited 1080 domain2.test,pendingDelete 1082 "domainNameServers" Defines the fields and CSV file references used 1083 for the domain name delegated hosts (name servers). The 1084 "domainNameServers" CSV files define the relationship between a 1085 domain name object and a delegated host. To support both the 1086 and the model, defined in 1087 [RFC5731], the host field element is used to 1088 reference the host. 1090 The following "csvDomain" fields, defined for the "domain" 1091 element, MUST be used in the 1092 "domainNameServers" element: 1094 Domain name using the delegated host with host 1095 . 1097 The following "rdeCsv" fields, defined in section CSV common field 1098 elements (Section 4.6.2), MUST be used in the "domainNameServers" 1099 element: 1101 Registry Object IDentifier (ROID) used to uniquely 1102 reference a delegated host record. 1104 Example of a "domainNameServers" 1105 element. 1107 ... 1108 1109 ... 1110 1111 1112 1113 1114 1115 1116 1118 domainNameServers-YYYYMMDD.csv 1119 1120 1121 1122 ... 1123 1124 ... 1126 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1127 The file contains the delegated hosts (name servers) for the two 1128 domain names domain1.test and domain2.test referenced via the 1129 field element. 1131 domain1.test,Dns1domain2test-TEST 1132 domain1.test,Dns2domain2test-TEST 1133 domain2.test,Dns1domainexample-TEST 1134 domain2.test,Dns2domainexample-TEST 1135 Example of a "domainNameServers" 1136 element. 1138 ... 1139 1140 ... 1141 1142 1143 1144 1145 1146 1147 1149 domainNameServers-delete-YYYYMMDD.csv 1150 1151 1152 1153 ... 1154 1155 ... 1157 Example of the corresponding domainNameServers-delete-YYYYMMDD.csv 1158 file. The file contains two records. 1160 domain1.test,Dns1domain2test-TEST 1161 domain1.test,Dns2domain2test-TEST 1162 domain2.test,Dns1domainexample-TEST 1163 domain2.test,Dns2domainexample-TEST 1165 "dnssec" Defines the fields and CSV file references used for the 1166 domain name object DNSSEC records (DS or Key Data). 1168 The following "csvDomain" field elements, defined for the "dnssec" 1169 element, MUST be used in the "dnssec" 1170 rdeCsv:fields> element when the DS Data Interface per 1171 [RFC5910] is used: 1173 Contains the DS key tag value per [RFC5910] 1174 with type="unsignedShort". 1176 Contains the DS algorithm value per [RFC5910] 1177 with type="unsignedByte". 1179 Contains the DS digest type value per 1180 [RFC5910] with type="unsignedByte". 1182 Contains the DS digest value per [RFC5910] 1183 with type="hexBinary". 1185 The following "csvDomain" field elements, defined for the "dnssec" 1186 element, MUST be used in the "dnssec" 1187 rdeCsv:fields> element when the Key Data Interface 1188 per [RFC5910] is used: 1190 Contains the flags field value per [RFC5910] 1191 with type="unsignedShort". 1193 Contains the Key protocol value per 1194 [RFC5910] with type="unsignedByte". 1196 Contains the Key algorithm value per 1197 [RFC5910] with type="unsignedByte". 1199 Contains the public key value per [RFC5910] 1200 with type="secDNS:keyType". 1202 The following "csvDomain" field elements, defined for the "dnssec" 1203 element, MAY be used in the "dnssec" 1204 rdeCsv:fields> element: 1206 Indicates a child's preference for the 1207 number of seconds after signature generation when the parent's 1208 signature on the DS information provided by the child will 1209 expire with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1211 The following "domain" fields, defined for the "domain" element, MUST be used in the "dnssec" 1213 element: 1215 Domain name of the domain object associated 1216 with the DNSSEC record. 1218 Example of a "dnssec" element 1219 with the DS Data Interface of [RFC5910]: 1221 1222 ... 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1235 dnssec-ds-YYYYMMDD.csv 1236 1237 1238 1239 ... 1240 1241 ... 1243 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The 1244 file contains two DS records for domain1.test. 1246 domain1.test,604800,12345,3,1,49FD46E6C4B45C55D4AC 1247 domain1.test,604800,12346,3,1,38EC35D5B3A34B44C39B 1249 Example of a "dnssec" element 1250 with the Key Data Interface of [RFC5910]: 1252 1253 ... 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1266 dnssec-key-YYYYMMDD.csv 1267 1268 1269 1270 ... 1271 1272 ... 1274 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The 1275 file contains two key records for domain1.test. 1277 domain1.test,604800,257,3,1,AQPJ////4Q== 1278 domain1.test,604800,257,3,1,AQPJ////4QQQ 1280 Example of a "dnssec" element 1281 with the DS Data Interface of [RFC5910]: 1283 ... 1284 1285 ... 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1297 dnssec-ds-delete-YYYYMMDD.csv 1298 1299 1300 1301 ... 1302 1303 ... 1305 Example of the corresponding dnssec-ds-delete-YYYYMMDD.csv file. 1306 The file contains two DS records for domain1.test. 1308 domain1.test,12345,3,1,49FD46E6C4B45C55D4AC 1309 domain1.test,12346,3,1,38EC35D5B3A34B44C39B 1311 Example of a "dnssec" element 1312 with the Key Data Interface of [RFC5910]: 1314 ... 1315 1316 ... 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1328 dnssec-key-delete-YYYYMMDD.csv 1329 1330 1331 1332 ... 1333 1334 ... 1336 Example of the corresponding dnssec-key-delete-YYYYMMDD.csv file. 1337 The file contains two key records for domain1.test. 1339 domain1.test,257,3,1,AQPJ////4Q== 1340 domain1.test,257,3,1,AQPJ////4QQQ 1342 "domainTransfer" Defines the fields and CSV file references used for 1343 the domain name object pending and completed transfer records. No 1344 additional field elements were added for use in the 1345 "domainTransfer" element. 1347 The following "rdeCsv" fields, defined in section CSV common field 1348 elements (Section 4.6.2), MUST be used in the "domainTransfer" 1349 element: 1351 State of the most recent transfer request. 1353 Identifier of the registrar, defined in 1354 Section 5.4, of the client that requested the transfer. 1356 Date and time that the transfer was requested. 1358 Identifier of the registrar, defined in 1359 Section 5.4, of the client that should take or took action. 1361 Date and time that the transfer action should be 1362 taken or has been taken. 1364 The following "rdeCsv" fields, defined in section CSV common field 1365 elements (Section 4.6.2), MAY be used in the "domainTransfer" 1366 element: 1368 Expiration date if the transfer command caused 1369 or causes a change in the validity period. 1371 Identifier of client that requested the transfer. 1373 Identifier of client that should take or took 1374 action for transfer. 1376 The following "csvDomain" fields, defined for the "domain" 1377 element, MUST be used in the 1378 "domainTransfer" element: 1380 Domain name of the domain object involved in 1381 the transfer. 1383 Example of a "domainTransfer" 1384 element: 1386 ... 1387 1388 ... 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1404 domainTransfer-YYYYMMDD.csv 1405 1406 1407 1408 ... 1409 1410 ... 1412 Example of the corresponding domainTransfer-YYYYMMDD.csv file. 1413 The file contains two domain transfer records, with one in pending 1414 status and the second in clientApproved status. 1416 domain1.test,pending,registrarX,clientY, 1417 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1418 2016-04-03T22:00:00.0Z 1419 domain2.test,clientApproved,registrarX,clientY, 1420 2012-03-08T19:38:00.0Z,registrarY,clientY, 1421 2012-03-09T23:59:59.0Z,2016-05-04T23:00:00.0Z 1423 Example of a "domainTransfer" 1424 element: 1426 ... 1427 1428 ... 1429 1430 1431 1432 1433 1434 1435 1437 domainTransfer-delete-YYYYMMDD.csv 1438 1439 1440 1441 ... 1442 1443 ... 1445 Example of the corresponding domainTransfer-delete-YYYYMMDD.csv 1446 file. The file contains two domain transfer records. 1448 domain1.test,2011-03-08T19:38:00.0Z 1449 domain2.test,2012-03-08T19:38:00.0Z 1451 5.2. Host Object 1453 The host object is based on the EPP host name mapping in [RFC5732]. 1454 The host object supports both the XML Model and the CSV Model, 1455 defined in Models (Section 2) section. The elements used for both 1456 models are defined in the following sections. 1458 5.2.1. XML Model 1460 There are two elements used in the data escrow of the host objects 1461 for the XML model including the , under the element, and the element, under the element. 1465 A element substitutes for the 1466 abstract element to define a concrete definition of a host. The 1467 element can be replaced by other host 1468 definitions using the XML schema substitution groups feature. 1470 5.2.1.1. element 1472 The RDE host object is based on the EPP host response for an 1473 authorized client (Section 3.1.2. of [RFC5732]). 1475 The OPTIONAL element contains the following child elements: 1477 o A element that contains the fully qualified name of the 1478 host object. 1480 o A element that contains the repository object identifier 1481 assigned to the host object when the object was created. 1483 o One or more elements that describe the status of the host 1484 object. 1486 o Zero or more elements that contain the IP addresses 1487 associated with the host object. 1489 o A element that contains the identifier of the sponsoring 1490 registrar. 1492 o A element that contains the identifier of the registrar 1493 that created the host object. An OPTIONAL client attribute is 1494 used to specify the client that performed the operation. 1496 o A element that contains the date and time of host-object 1497 creation. 1499 o An OPTIONAL element that contains the identifier of the 1500 registrar that last updated the host object. This element MUST 1501 NOT be present if the host object has never been modified. An 1502 OPTIONAL client attribute is used to specify the client that 1503 performed the operation. 1505 o An OPTIONAL element that contains the date and time of 1506 the most recent host-object modification. This element MUST NOT 1507 be present if the host object has never been modified. 1509 o An OPTIONAL element that contains the date and time of 1510 the most recent host object successful transfer. This element 1511 MUST NOT be present if the domain name object has never been 1512 transfered. 1514 Example of object: 1516 ... 1517 1518 ns1.example1.test 1519 Hns1_example_test-TEST 1520 1521 1522 192.0.2.2 1523 192.0.2.29 1524 1080:0:0:0:8:800:200C:417A 1525 RegistrarX 1526 RegistrarX 1527 1999-05-08T12:10:00.0Z 1528 RegistrarX 1529 2009-10-03T09:34:00.0Z 1530 1531 ... 1533 5.2.1.2. object 1535 The element contains the fully qualified domain name 1536 of a host that was deleted. The element also 1537 supports host removal based on roid to support SRS systems in which 1538 different hosts with the same fully qualified domain name are active 1539 at the same time. 1541 Example of object: 1543 ... 1544 1545 ... 1546 1547 ns1.example.test 1548 1549 ... 1550 1551 ... 1553 5.2.1.3. CSV Model 1555 For the CSV Model of the host object, the child 1556 element of the element is used to hold the new or 1557 updated host objects for the deposit. The child 1558 element of the element is used to hold the deleted or 1559 purged host objects for the deposit. Both the and 1560 elements contain one or more elements 1561 with the following supported "name" attribute values: 1563 "host" Defines the fields and CSV file references used for the host 1564 object records. 1566 The following "csvHost" field elements, defined for the "host" 1567 element, MUST be used in the "host" 1568 element: 1570 Host name field with type="eppcom:labelType" and 1571 isRequired="true". 1573 The following "rdeCsv" fields, defined in section CSV common field 1574 elements (Section 4.6.2), MUST be used in the "host" 1575 element: 1577 Repository Object IDentifier (ROID) assigned to 1578 the host object. 1580 The following "rdeCsv" fields, defined in section CSV common field 1581 elements (Section 4.6.2), MAY be used in the "host" 1582 element: 1584 Identifier of the sponsoring client. 1586 Identifier of the registrar, defined in 1587 Section 5.4, of the client that created the object. 1589 Identifier of client that created the host object. 1591 Date and time that the host object was created. 1593 Identifier of the registrar, defined in 1594 Section 5.4, of the client that updated the object. 1596 Identifier of client that last updated the host 1597 object. 1599 Date and time that the host object was last 1600 updated. 1602 Date and time that the host was last 1603 transferred. 1605 Example of a "host" element: 1607 ... 1608 1609 ... 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1626 host-YYYYMMDD.csv 1627 1628 1629 1630 ... 1631 1632 ... 1634 Example of the corresponding host-YYYYMMDD.csv file. The file 1635 contains two host records with one being an internal host and the 1636 second being an external host. 1638 ns1.example.test,Hns1_example_test-TEST,registrarX,registrarX, 1639 clientY,1999-05-08T12:10:00.0Z,registrarX, 1640 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1641 ns1.example.test2,Hns1_example_test2-TEST,clientY, 1642 clientX,2009-05-08T12:10:00.0Z,clientX, 1643 2010-10-03T09:34:00.0Z, 1644 Example of a "host" element: 1646 ... 1647 1648 ... 1649 1650 1651 1652 1653 1654 1656 host-delete-YYYYMMDD.csv 1657 1658 1659 1660 ... 1661 1662 ... 1664 Example of the host-delete-YYYYMMDD.csv file. The file contains 1665 two host records. 1667 Hns1_example_test-TEST 1668 Hns1_example_test2-TEST 1670 "hostStatuses" Defines the fields and CSV file references used for 1671 the host object statuses. 1673 The following "csvHost" fields, defined for the "host" element, MUST be used in the "hostStatuses" 1675 element: 1677 The status of the host with type="host: 1678 statusValueType"/>. 1680 The following "rdeCsv" fields, defined in section CSV common field 1681 elements (Section 4.6.2), MUST be used in the "hostStatuses" 1682 element: 1684 Host object Registry Object IDentifier (ROID) 1685 assigned to the host object. 1687 The following "rdeCsv" fields, defined in section CSV common field 1688 elements (Section 4.6.2), MAY be used in the "hostStatuses" 1689 element: 1691 Host object status description which 1692 is free form text describing the rationale for the status. 1694 Language of the field. 1696 Example of a "hostStatuses" 1697 element: 1699 ... 1700 1701 ... 1702 1703 1704 1705 1706 1707 1708 1709 1710 1712 hostStatuses-YYYYMMDD.csv 1713 1714 1715 1716 ... 1717 1718 ... 1720 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1721 file contains the statuses for the two host names ns1.domain1.test 1722 and ns1.domain2.test. 1724 ns1domain1test-TEST,clientUpdateProhibited,"Disallow update",en 1725 ns1domain1test-TEST,clientDeleteProhibited,"Disallow delete",en 1726 ns1domain2test-TEST,ok,, 1728 Example of a "hostStatuses" 1729 element: 1731 ... 1732 1733 ... 1734 1735 1736 1737 1738 1739 1740 1742 hostStatuses-delete-YYYYMMDD.csv 1743 1744 1745 1746 ... 1747 1748 ... 1750 Example of the corresponding hostStatuses-delete-YYYYMMDD.csv 1751 file. The file contains two status records. 1753 ns1domain1test-TEST,clientUpdateProhibited 1754 ns1domain1test-TEST,clientDeleteProhibited 1756 "hostAddresses" Defines the fields and CSV file references used for 1757 the host object IP addresses. 1759 The following "csvHost" field elements, defined for the 1760 "hostAddresses" rdeCsv:fields> element, MUST be used 1761 in the "hostAddresses" element: 1763 IP addresses associated with the host object with 1764 type="host:addrStringType". 1766 IP addresses version associated with the 1767 host object with type="host:ipType". "host:ipType" has the 1768 enumerated values of "v4" or "v6". 1770 The following "rdeCsv" fields, defined in section CSV common field 1771 elements (Section 4.6.2), MUST be used in the "hostAddresses" 1772 element: 1774 Host object Registry Object IDentifier (ROID) 1775 assigned to the host object. 1777 Example of a "hostAddresses" 1778 element. 1780 ... 1781 1782 ... 1783 1784 1785 1786 1787 1788 1789 1790 1792 hostAddresses-YYYYMMDD.csv 1793 1794 1795 1796 ... 1797 1798 ... 1800 Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. 1801 The file contains the IP addresses for the host name 1802 ns1.domain1.test. 1804 ns1domain1test-TEST,192.0.2.2,v4 1805 ns1domain1test-TEST,192.0.2.29,v4 1806 ns1domain1test-TEST,1080:0:0:0:8:800:200C:417A,v6 1808 Example of a "hostAddresses" 1809 element: 1811 ... 1812 1813 ... 1814 1815 1816 1817 1818 1819 1820 1822 hostAddresses-delete-YYYYMMDD.csv 1823 1824 1825 1826 ... 1827 1828 ... 1830 Example of the corresponding hostAddresses-delete-YYYYMMDD.csv 1831 file. The file contains three IP address records. 1833 ns1domain1test-TEST,192.0.2.2 1834 ns1domain1test-TEST,192.0.2.29 1835 ns1domain1test-TEST,1080:0:0:0:8:800:200C:417A 1837 5.3. Contact Object 1839 The contact object is based on the EPP contact name mapping in 1840 [RFC5733]. The contact object supports both the XML Model and the 1841 CSV Model, defined in Models (Section 2) section. The elements used 1842 for both models are defined in the following sections. 1844 5.3.1. XML Model 1846 There are two elements used in the data escrow of the contact objects 1847 for the XML model including the , under the 1848 element, and the element, 1849 under the element. 1851 A element substitutes for the abstract 1852 element to define a concrete definition of a contact. The 1853 element can be replaced by other contact 1854 definitions using the XML schema substitution groups feature. 1856 5.3.1.1. object 1858 The contact object is based on the EPP contact response for an 1859 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1860 including the data from an EPP Query Response, see Section 1861 3.1.3. of [RFC5733]. 1863 The OPTIONAL element contains the following child elements: 1865 o A element that contains the server-unique identifier of the 1866 contact object 1868 o A element that contains the Repository Object IDentifier 1869 assigned to the contact object when the object was created. 1871 o One or more elements that describe the status of the 1872 contact object. 1874 o One or two elements that contain postal-address 1875 information. Two elements are provided so that address 1876 information can be provided in both internationalized and 1877 localized forms; a "type" attribute is used to identify the two 1878 forms. If an internationalized form (type="int") is provided, 1879 element content MUST be represented in a subset of UTF-8 that can 1880 be represented in the 7-bit US-ASCII character set. If a 1881 localized form (type="loc") is provided, element content MAY be 1882 represented in unrestricted UTF-8. The element 1883 contains the following child elements: 1885 * A element that contains the name of the individual or 1886 role represented by the contact. 1888 * An OPTIONAL element that contains the name of the 1889 organization with which the contact is affiliated. 1891 * An element that contains address information associated 1892 with the contact. An element contains the following 1893 child elements: 1895 + One, two, or three OPTIONAL elements that contain 1896 the contact's street address. 1898 + A element that contains the contact's city. 1900 + An OPTIONAL element that contains the contact's state 1901 or province. 1903 + An OPTIONAL element that contains the contact's postal 1904 code. 1906 + A element that contains the contact's two-letter 1907 country code. 1909 o An OPTIONAL element that contains the contact's voice 1910 telephone number. 1912 o An OPTIONAL element that contains the contact's facsimile 1913 telephone number. 1915 o An element that contains the contact's email address. 1917 o A element that contains the identifier of the sponsoring 1918 registrar. 1920 o A element that contains the identifier of the registrar 1921 that created the contact object. An OPTIONAL client attribute is 1922 used to specify the client that performed the operation. 1924 o A element that contains the date and time of contact- 1925 object creation. 1927 o An OPTIONAL element that contains the identifier of the 1928 registrar that last updated the contact object. This element MUST 1929 NOT be present if the contact has never been modified. An 1930 OPTIONAL client attribute is used to specify the client that 1931 performed the operation. 1933 o An OPTIONAL element that contains the date and time of 1934 the most recent contact-object modification. This element MUST 1935 NOT be present if the contact object has never been modified. 1937 o An OPTIONAL element that contains the date and time of 1938 the most recent contact object successful transfer. This element 1939 MUST NOT be present if the contact object has never been 1940 transferred. 1942 o An OPTIONAL element that contains the following child 1943 elements related to the last transfer request of the contact 1944 object: 1946 * A element that contains the state of the most recent 1947 transfer request. 1949 * A element that contains the identifier of the registrar 1950 that requested the domain name object transfer. An OPTIONAL 1951 client attribute is used to specify the client that performed 1952 the operation. 1954 * An element that contains the identifier of the registrar 1955 that SHOULD act upon a PENDING transfer request. For all other 1956 status types, the value identifies the registrar that took the 1957 indicated action. An OPTIONAL client attribute is used to 1958 specify the client that performed the operation. 1960 * A element that contains the date and time that the 1961 transfer was requested. 1963 * An element that contains the date and time of a 1964 required or completed response. For a PENDING request, the 1965 value identifies the date and time by which a response is 1966 required before an automated response action will be taken by 1967 the registry. For all other status types, the value identifies 1968 the date and time when the request was completed. 1970 o An OPTIONAL element that identifies elements that 1971 requiring exceptional server-operator handling to allow or 1972 restrict disclosure to third parties. See Section 2.9 of 1973 [RFC5733] for a description of the child elements contained within 1974 the element. 1976 Example object: 1978 ... 1979 1980 Csh8013-TEST 1981 sh8013 1982 1983 1984 1985 John Doe 1986 Example Inc. 1987 1988 123 Example Dr. 1989 Suite 100 1990 Dulles 1991 VA 1992 20166-6503 1993 US 1994 1995 1996 +1.7035555555 1997 +1.7035555556 1998 jdoe@example.test 1999 RegistrarX 2000 RegistrarX 2001 2009-09-13T08:01:00.0Z 2002 RegistrarX 2003 2009-11-26T09:10:00.0Z 2004 2009-12-03T09:05:00.0Z 2005 2006 pending 2007 clientW 2008 2011-03-08T19:38:00.0Z 2009 RegistrarX 2010 2011-03-13T23:59:59.0Z 2011 2012 2013 2014 2015 2016 2017 ... 2019 5.3.1.2. object 2021 The element contains the id of a contact that was 2022 deleted. 2024 Example of object: 2026 ... 2027 2028 ... 2029 2030 sh8013-TEST 2031 co8013-TEST 2032 2033 ... 2034 2035 ... 2037 5.3.2. CSV Model 2039 For the CSV Model of the contact object, the 2040 child element of the element is used to hold the new 2041 or updated contact objects for the deposit. The 2042 child element of the element is used to hold the 2043 deleted or purged contact objects for the deposit. Both the 2044 and elements contain one 2045 or more elements with the following supported "name" 2046 attribute values: 2048 "contact" Defines the fields and CSV file references used for the 2049 contact object records. 2051 The following "csvContact" field elements, defined for the 2052 "contact" element, MUST be used in 2053 the "contact" element: 2055 Contains the server-unique contact identifier 2056 with type="eppcom:clIDType" and isRequired="true". 2058 Contains the contact's email address with 2059 type="eppcom:minTokenType" and isRequired="true". 2061 The following field elements MAY be used in the "contact" element: 2064 Contains the contact's voice telephone number 2065 with type="contact:e164StringType". 2067 Contains the contact's voice telephone 2068 number extension with type="token". 2070 Contains the contact's facsimile telephone 2071 number with type="contact:e164StringType". 2073 Contains the contact's facsimile telephone 2074 number extension with type="token". 2076 The following "rdeCsv" fields, defined in section CSV common field 2077 elements (Section 4.6.2), MUST be used in the "contact" element: 2080 The Registry Object IDentifier (ROID) for the 2081 contact object. 2083 Identifier of client (registrar) that sponsors the 2084 contact object. 2086 Identifier of the registrar, defined in 2087 Section 5.4, of the client that created the object. 2089 Created date and time of the contact object 2091 Identifier of the registrar, defined in 2092 Section 5.4, of the client that updated the object. 2094 Date and time of the last update to the contact 2095 object. 2097 The following "rdeCsv" fields, defined in section CSV common field 2098 elements (Section 4.6.2), MAY be used in the "contact" element: 2101 Identifier of client that created the contact 2102 object. 2104 Identifier of the client that last updated the 2105 contact object. 2107 Date and time of the last transfer for the 2108 contact object. 2110 Example of a "contact" element: 2112 ... 2113 2114 ... 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2135 contact-YYYYMMDD.csv 2136 2137 2138 2139 ... 2140 2141 ... 2143 Example of the contact-YYYYMMDD.csv file. The file contains two 2144 object contact records. 2146 sh8013,Csh8013-TEST,+1.7035555555,1234,+1.7035555556,, 2147 jdoe@example.test,registrarX,registarX, 2148 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2149 2009-11-26T09:10:00.0Z 2150 mycontactid,Cmycontactid-TEST,+1.7034444444,1234, 2151 +1.7033333333,,jsmith@example.test,registrarX,registarX,clientY, 2152 2010-09-13T08:01:00.0Z,registarX,clientY,2011-11-26T09:10:00.0Z 2153 Example of a "contact" element: 2155 ... 2156 2157 ... 2158 2159 2160 2161 2162 2163 2165 contact-delete-YYYYMMDD.csv 2166 2167 2168 2169 ... 2170 2171 ... 2173 Example of the contact-delete-YYYYMMDD.csv file. The file 2174 contains two contact records. 2176 sh8013 2177 mycontactid 2179 "contactStatuses" Defines the fields and CSV file references used 2180 for the contact object statuses. 2182 The following "csvContact" field elements, defined for the 2183 "contact" element, MUST be used in 2184 the "contactStatuses" element: 2186 Server-unique contact identifier of status. 2188 The status of the contact with 2189 type="contact:statusValueType". 2191 The following "rdeCsv" fields, defined in section CSV common field 2192 elements (Section 4.6.2), MAY be used in the "contactStatuses" 2193 element: 2195 The contact object status description 2196 which is free form text describing the rationale for the 2197 status. 2199 Language of the field. 2201 Example of a "contactStatuses" 2202 element: 2204 ... 2205 2206 ... 2207 2208 2209 2210 2211 2212 2213 2214 2215 2217 contactStatuses-YYYYMMDD.csv 2218 2219 2220 2221 ... 2222 2223 ... 2225 Example of the corresponding contactStatuses-YYYYMMDD.csv file. 2226 The file contains the statuses for the two contact identifiers 2227 sh8013 and mycontactid. 2229 sh8013,clientUpdateProhibited,"Disallow update",en 2230 sh8013,clientDeleteProhibited,"Disallow delete",en 2231 mycontactid,ok,, 2232 Example of a "contactStatuses" 2233 element: 2235 ... 2236 2237 ... 2238 2239 2240 2241 2242 2243 2244 2246 contactStatuses-delete-YYYYMMDD.csv 2247 2248 2249 2250 ... 2251 2252 ... 2254 Example of the corresponding contactStatuses-delete-YYYYMMDD.csv 2255 file. The file contains two status records. 2257 sh8013,clientUpdateProhibited 2258 sh8013,clientDeleteProhibited 2260 "contactPostal" Defines the fields and CSV file references used for 2261 the contact postal info object records. 2263 The following "csvContact" field elements, defined for the 2264 "contactPostal" element, MUST be used 2265 in the "contactPostal" element: 2267 Contains the contact's name of the individual 2268 or role represented by the contact with type="contact: 2269 postalLineType" and isRequired="true". An OPTIONAL "isLoc" 2270 attribute to used to indicate the localized or 2271 internationalized form as defined in section Section 4.7. 2273 Contains the contact's contact's street 2274 address line with type="contact:fPostalLineType". An index 2275 attribute is required to indicate which street address line the 2276 field represents with index "0" for the first line and index 2277 "2" for the last line. An OPTIONAL "isLoc" attribute to used 2278 to indicate the localized or internationalized form as defined 2279 in section Section 4.7. 2281 Contains the contact's city with 2282 type="contact:postalLineType" and isRequired="true". An 2283 OPTIONAL "isLoc" attribute to used to indicate the localized or 2284 internationalized form as defined in section Section 4.7. 2286 Contains the contact's country code with 2287 type="contact:ccType". An OPTIONAL "isLoc" attribute to used 2288 to indicate the localized or internationalized form as defined 2289 in section Section 4.7. 2291 "contactPostal" Defines the fields and CSV file references used for 2292 the contact postal info object records. 2294 The following "csvContact" field elements, defined for the 2295 "contactPostal" element, MAY be used 2296 in the "contactPostal" element: 2298 Contains the form of the postal-address 2299 information with type="contact:postalLineType". This field 2300 specifies the form ("int" or "loc"), as defined in Section 4.7, 2301 of the , , , , , , fields. 2305 Contains the name of the organization with 2306 which the contact is affiliated with type="contact: 2307 optPostalLineType". An OPTIONAL "isLoc" attribute to used to 2308 indicate the localized or internationalized form as defined in 2309 section Section 4.7. 2311 Contains the contact's state or province with 2312 type="contact:optPostalLineType". An OPTIONAL "isLoc" 2313 attribute to used to indicate the localized or 2314 internationalized form as defined in section Section 4.7. 2316 Contains the contact's postal code with 2317 type="contact:pcType". An OPTIONAL "isLoc" attribute to used 2318 to indicate the localized or internationalized form as defined 2319 in section Section 4.7. 2321 The following "csvContact" fields, defined for the "contact" 2322 element, MUST be used in the 2323 "contactPostal" element: 2325 Server-unique contact identifier for the contact 2326 object. 2328 Example of a "contactPostal" 2329 element: 2331 ... 2332 2333 ... 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2351 contactPostal-YYYYMMDD.csv 2352 2353 2354 2355 ... 2356 2357 ... 2359 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2360 two contact postal records. 2362 sh8013,int,"John Doe","Example Inc.", 2363 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2364 mycontactid,int,"John Smith","Acme Inc.", 2365 "123 Sample Dr.",,,Reston,VA,20190,US 2367 Example of a "contactPostal" 2368 element: 2370 ... 2371 2372 ... 2373 2374 2375 2376 2377 2378 2379 2381 contactPostal-delete-YYYYMMDD.csv 2382 2383 2384 2385 ... 2386 2387 ... 2389 Example of the contactPostal-delete-YYYYMMDD.csv file. The file 2390 contains two contact postal records. 2392 sh8013,int 2393 mycontactid,int 2395 "contactTransfer" Defines the fields and CSV file references used 2396 for the contact object pending and completed transfer records. No 2397 additional field elements were added for use in the 2398 "contactTransfer" element. The 2399 following "rdeCsv" fields, defined in section CSV common field 2400 elements (Section 4.6.2), MUST be used in the "contactTransfer" 2401 element: 2403 State of the most recent transfer request. 2405 Identifier of the registrar, defined in 2406 Section 5.4, of the client that requested the transfer. 2408 Date and time that the transfer was requested. 2410 Identifier of the registrar, defined in 2411 Section 5.4, of the client that should take or took action. 2413 Date and time that the transfer action should be 2414 taken or has been taken 2416 The following "rdeCsv" fields, defined in section CSV common field 2417 elements (Section 4.6.2), MAY be used in the "contactTransfer" 2418 element: 2420 Identifier of client that requested the transfer. 2422 Identifier of client that should take or took 2423 action for transfer. 2425 The following "csvContact" fields, defined for the "contact" 2426 element, MUST be used in the 2427 "contactTransfer" element: 2429 Server-unique contact identifier for the contact 2430 object. 2432 Example of a "contactTransfer" 2433 element: 2435 ... 2436 2437 ... 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2452 contactTransfer-YYYYMMDD.csv 2453 2454 2455 2456 ... 2457 2458 ... 2460 Example of the contactTransfer-YYYYMMDD.csv file. The file 2461 contains two contact transfer records with one in pending status 2462 and the second in clientApproved status. 2464 sh8013,pending,registrarX,clientX,2011-03-08T19:38:00.0Z, 2465 registrarY,,2011-03-13T23:59:59.0Z 2466 mycontactid,clientApproved,registrarX,clientX,2011-04-08T19:38:00.0Z, 2467 registrarY,clientY,2011-04-09T20:38:00.0Z 2469 Example of a "contactTransfer" 2470 element: 2472 ... 2473 2474 ... 2475 2476 2477 2478 2479 2480 2481 2483 contactTransfer-delete-YYYYMMDD.csv 2484 2485 2486 2487 ... 2488 2489 ... 2491 Example of the contactTransfer-delete-YYYYMMDD.csv file. The file 2492 contains two contact transfer records. 2494 sh8013,2011-03-08T19:38:00.0Z 2495 mycontactid,2011-04-08T19:38:00.0Z 2497 "contactDisclose" Defines the fields and CSV file references used 2498 for the contact disclose object records. 2500 The following "csvContact" field elements, defined for the 2501 "contactDisclose" element, MAY be 2502 used in the "contactDisclose" 2503 element: 2505 Contains flag with a value of "true" 2506 or "1" (one) notes the preference to allow disclosure of the 2507 specified elements as an exception to the stated data- 2508 collection policy. A value of "false" or "0" (zero) notes a 2509 client preference to not allow disclosure of the specified 2510 elements as an exception to the stated data-collection policy 2511 with type="boolean". The additional fields define specific 2512 exceptional disclosure preferences based on the field. 2515 Exceptional disclosure preference 2516 flag for the localized form of the contact name with 2517 type="boolean". 2519 Exceptional disclosure preference 2520 flag for the internationalized form of the contact name with 2521 type="boolean". 2523 Exceptional disclosure preference 2524 flag for the localized form of the contact organization with 2525 type="boolean". with type="boolean". 2527 Exceptional disclosure preference 2528 flag for the internationalized form of the contact organization 2529 with type="boolean". with type="boolean". 2531 Exceptional disclosure preference 2532 flag for the localized form of the contact address with 2533 type="boolean". 2535 Exceptional disclosure preference 2536 flag for the internationalized form of the contact address with 2537 type="boolean". 2539 Exceptional disclosure preference 2540 flag of the contact voice telephone number with type="boolean". 2542 Exceptional disclosure preference flag 2543 of the contact facsimile telephone number with type="boolean". 2545 Exceptional disclosure preference 2546 flag of the contact email address with type="boolean". 2548 The following "csvContact" fields, defined for the "contact" 2549 element, is used in the 2550 "contactDisclose" element: 2552 Server-unique contact identifier for the contact 2553 object. 2555 Example of a "contactDisclose" 2556 element: 2558 ... 2559 2560 ... 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2578 contactDisclose-YYYYMMDD.csv 2579 2580 2581 2582 ... 2583 2584 ... 2586 Example of the contactDisclose-YYYYMMDD.csv file. The file 2587 contains two disclosure records. The first contact disables 2588 disclosure of voice, fax, and email. The second contact enables 2589 disclosure of the localized and internationalized form of the 2590 name. 2592 sh8013,0,0,0,0,0,0,0,1,1,1 2593 mycontactid,1,1,1,0,0,0,0,0,0,0 2595 Example of a "contactDisclose" 2596 element: 2598 ... 2599 2600 ... 2601 2602 2603 2604 2605 2606 2608 contactDisclose-delete-YYYYMMDD.csv 2609 2610 2611 2612 ... 2613 2614 ... 2616 Example of the contactDisclose-delete-YYYYMMDD.csv file. The file 2617 contains two disclosure records. 2619 sh8013 2620 mycontactid 2622 5.4. Registrar Object 2624 The registrar object represents the sponsoring client for other 2625 objects, for operational purposes MAY be the registry operator. The 2626 registrar object supports both the XML Model and the CSV Model, 2627 defined in Section 2. The elements used for both models are defined 2628 in the following sections. 2630 5.4.1. XML Model 2632 There are two elements used in the data escrow of the registrar 2633 objects for the XML model including the , 2634 under the element, and the element, under the element. 2637 A element substitutes for the abstract element to define a concrete definition 2639 of a registrar. The element can be 2640 replaced by other domain definitions using the XML schema 2641 substitution groups feature. 2643 5.4.1.1. element 2645 The element contains the following child elements: 2647 o An element that contains the Registry-unique identifier of 2648 the registrar object. This has a superordinate relationship 2649 to a subordinate , or of domain, contact and 2650 host objects. 2652 o An element that contains the name of the registrar. 2654 o An OPTIONAL element that contains the ID assigned by 2655 ICANN. 2657 o A element that contains the operational status of the 2658 registrar. Possible values are: ok, readonly and terminated. 2660 o One or two elements that contain postal- address 2661 information. Two elements are provided so that address 2662 information can be provided in both internationalized and 2663 localized forms; a "type" attribute is used to identify the two 2664 forms. If an internationalized form (type="int") is provided, 2665 element content MUST be represented in a subset of UTF-8 that can 2666 be represented in the 7-bit US-ASCII character set. If a 2667 localized form (type="loc") is provided, element content MAY be 2668 represented in unrestricted UTF-8. The element 2669 contains the following child elements: 2671 * A element that contains address information associated 2672 with the registrar. The element contains the following 2673 child elements: 2675 + One, two, or three OPTIONAL elements that contain 2676 the registrar's street address. 2678 + A element that contains the registrar's city. 2680 + An OPTIONAL element that contains the registrar's state 2681 or province. 2683 + An OPTIONAL element that contains the registrar's 2684 postal code. 2686 + A element that contains the registrar's country code. 2688 o An OPTIONAL element that contains the registrar's voice 2689 telephone number. 2691 o An OPTIONAL element that contains the registrar's facsimile 2692 telephone number. 2694 o An element that contains the registrar's email address. 2696 o An OPTIONAL element that contains the registrar's URL. 2698 o An OPTIONAL elements that contains whois information. 2699 The element contains the following child elements: 2701 * An OPTIONAL element that contains the name of the 2702 registrar WHOIS server listening on TCP port 43 as specified in 2703 [RFC3912]. 2705 * An OPTIONAL element that contains the name of the 2706 registrar WHOIS server listening on TCP port 80/443. 2708 o A element that contains the date and time of registrar- 2709 object creation. 2711 o An OPTIONAL element that contains the date and time of 2712 the most recent RDE registrar-object modification. This element 2713 MUST NOT be present if the rdeRegistrar object has never been 2714 modified. 2716 Example of object: 2718 ... 2719 2720 RegistrarX 2721 Registrar X 2722 123 2723 ok 2724 2725 2726 123 Example Dr. 2727 Suite 100 2728 Dulles 2729 VA 2730 20166-6503 2731 US 2732 2733 2734 +1.7035555555 2735 +1.7035555556 2736 jdoe@example.test 2737 http://www.example.test 2738 2739 whois.example.test 2740 http://whois.example.test 2741 2742 2005-04-23T11:49:00.0Z 2743 2009-02-17T17:51:00.0Z 2744 2745 ... 2747 5.4.1.2. object 2749 The element contains the id of a registrar that 2750 was deleted. 2752 Example of object: 2754 ... 2755 2756 ... 2757 2758 agnt0001-TEST 2759 2760 ... 2761 2762 ... 2764 5.4.2. CSV Model 2766 For the CSV Model of the registrar object, The child element of the element is used to hold 2768 the new or updated registrar objects for the deposit. The 2769 child element of the element is 2770 used to hold the deleted or purged registrar objects for the deposit. 2771 Both the and elements 2772 contain one or more elements with the following 2773 supported "name" attribute values: 2775 "registrar" Defines the fields and CSV file references used for the 2776 registrar object records. 2778 The following "csvRegistrar" field elements, defined for the 2779 "registrar" element, MUST be used in 2780 the "registrar" element: 2782 Contains the server-unique registrar 2783 identifier with type="eppcom:clIDType" and isRequired="true". 2785 Contains the name of the registrar with 2786 type="normalizedString" and isRequired="true". 2788 Contains the status of the registrar with 2789 type="csvRegistrar:statusValueType". 2791 The following field elements MAY be used in the "registrar" 2792 element: 2794 Contains the ID assigned by ICANN with 2795 type="positiveInteger". 2797 Contains the Whois URL of the registrar 2798 with type="anyURI". 2800 The following "rdeCsv" fields, defined in section CSV common field 2801 elements (Section 4.6.2), MUST be used in the "registrar" element: 2804 Created date and time of the registrar object. 2806 Date and time of the last update to the 2807 registrar object. 2809 URL for the registrar web home page. 2811 The following "csvContact" fields, defined in section Section 5.3, 2812 MUST be used in the "registrar" 2813 element: 2815 Registrar street address line with an 2816 "index" attribute that represents the order of the street 2817 address line from "0" to "2". An OPTIONAL "isLoc" attribute 2818 that is used to indicate the localized or internationalized 2819 form, as defined in Section 4.7. 2821 Registrar city with an OPTIONAL "isLoc" 2822 attribute that is used to indicate the localized or 2823 internationalized form, as defined in Section 4.7. 2825 Registrar country code with an OPTIONAL "isLoc" 2826 attribute that is used to indicate the localized or 2827 internationalized form, as defined in Section 4.7. 2829 Registrar email address. 2831 The following "csvContact" fields, defined in section Section 5.3, 2832 MAY be used in the "registrar" 2833 element: 2835 Registrar state or province with an OPTIONAL 2836 "isLoc" attribute that is used to indicate the localized or 2837 internationalized form, as defined in Section 4.7. 2839 Registrar postal code with an OPTIONAL "isLoc" 2840 attribute that is used to indicate the localized or 2841 internationalized form, as defined in Section 4.7. 2843 Registrar voice telephone number. 2845 Registrar voice telephone number 2846 extension. 2848 Registrar facsimile telephone number. 2850 Registrar facsimile telephone number 2851 extension. 2853 Example of a "registrar" 2854 element. 2856 ... 2857 2858 ... 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2885 registrar-YYYYMMDD.csv 2886 2887 2888 2889 ... 2890 2891 ... 2893 Example of the registrar-YYYYMMDD.csv file. The file contains one 2894 registrar record. 2896 EXAMPLE,"Example Inc.",1234,ok,"123 Example Dr.", 2897 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2898 +1.7035555556,,jdoe@example.test,http://www.example.test, 2899 http://whois.example.test,2005-04-23T11:49:00.0Z, 2900 2009-02-17T17:51:00.0Z 2902 Example of a "registrar" 2903 element: 2905 ... 2906 2907 ... 2908 2909 2910 2911 2912 2913 2915 registrar-delete-YYYYMMDD.csv 2916 2917 2918 2919 ... 2920 2921 ... 2923 Example of the registrar-delete-YYYYMMDD.csv file. The file 2924 contains two registrar records. 2926 EXAMPLE 2927 EXAMPLE2 2929 5.5. IDN Table Reference Object 2931 The Internationalized Domain Names (IDN) table reference object is a 2932 pseudo-object that is used to provide a short reference to the IDN 2933 Table and Policy used in IDN registrations. The IDN reference object 2934 supports both the XML and the CSV Model, defined in the Models 2935 (Section 2) section. The elements used for both models are defined 2936 in the following sections. 2938 5.5.1. XML Model 2940 There is one element used in the data escrow of the IDN table 2941 reference objects for the XML model that is the , 2942 under the element. 2944 5.5.1.1. object 2946 The contains the following elements. An "id" 2947 attribute is used to specify an identifier for the IDN table. 2949 o An element that contains the URL of the IDN table that is 2950 being referenced. 2952 o A element that contains the URL of the IDN policy 2953 document. If IDN variants are generated algorithmically, the 2954 policy document MUST define the algorithm and the state of the 2955 implicit generated IDN variants. For a list of suggested states 2956 for implicit IDN variants, please see [variantTLDsReport]. 2958 Example of object: 2960 ... 2961 2962 2963 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 2964 2965 2966 http://registro.br/dominio/regras.html 2967 2968 2969 ... 2971 5.5.2. CSV Model 2973 The IDN domain names, defined in Section 5.1, MAY have references to 2974 the IDN language identifier using the field 2975 element. The IDN table reference object defines the mapping of a 2976 language identifier to a language table URL. The language table URL 2977 defines the character code points that can be used for the language 2978 identifier. The elements used for the IDN table reference object is 2979 defined in this section. The child element of the 2980 element is used to hold the new or updated IDN table 2981 reference objects for the deposit. The child 2982 element of the element is used to hold the deleted or 2983 purged IDN table reference objects for the deposit. Both the 2984 and elements contain one or more 2985 elements with the following supported "name" attribute 2986 values: 2988 "idnLanguage" Defines the fields and CSV file references used for 2989 the IDN table reference object records. 2991 The following "rdeCsv" fields, defined in Section 4.6.2, MUST be 2992 used in the "idnLanguage" element: 2994 The language identifier that matches the 2995 values for the field element in the 2996 "domain" CSV files, as defined in Section 5.1. 2998 URL that defines the character code points that can 2999 be used for the language defined by the field 3000 element. 3002 Example of a "idnLanguage" element: 3004 ... 3005 3006 ... 3007 3008 , 3009 3010 3011 3012 3013 3014 3016 idnLanguage-YYYYMMDD.csv 3017 3018 3019 3020 ... 3021 3022 ... 3024 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The 3025 file contains two IDN language records. 3027 LANG-1, 3028 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3029 LANG-2, 3030 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3032 Example of a "idnLanguage" element: 3034 ... 3035 3036 ... 3037 3038 3039 3040 3041 3042 3044 idnLanguage-delete-YYYYMMDD.csv 3045 3046 3047 3048 ... 3049 3050 ... 3052 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3053 contains two IDN language records. 3055 LANG-1 3056 LANG-2 3058 5.6. NNDN Object 3060 A NNDN (NNDN's not domain name) can be used to store registry 3061 reserved names or (blocked, withheld or mirrored) IDN variants. 3063 A NNDN is a lightweight domain-like object that is not linked 3064 directly to a Registrar (a mirroring NNDN is linked to a Registrar 3065 via the original name). 3067 A domain name can only exist as a domain name object or NNDN object, 3068 but not both. 3070 The NNDN object supports both the XML and the CSV Model, defined in 3071 the Models (Section 2) section. The elements used for both models 3072 are defined in the following sections. 3074 5.6.1. XML Model 3076 There are two elements used in the data escrow of the NNDN objects 3077 for the XML model including the , under the element, and the element, under the element. 3081 A element substitutes for the 3082 abstract element to define a concrete definition of a NNDN. The 3083 element can be replaced by other NNDN 3084 definitions using the XML schema substitution groups feature. 3086 5.6.1.1. object 3088 The element contains the following child elements: 3090 o An element that contains the fully qualified name of the 3091 NNDN. If the NNDN is an IDN, the ASCII Compatible Encoding (ACE) 3092 MUST be used. 3094 o An OPTIONAL element that contains the fully qualified name 3095 of the NNDN in Unicode character set. It MUST be provided if 3096 available. 3098 o An OPTIONAL element that references the IDN Table 3099 used for the NNDN. This corresponds to the "id" attribute of the 3100 element. This element MUST be present if the NNDN 3101 is an IDN. 3103 o An OPTIONAL element is used to indicate that the 3104 NNDN is used for an IDN variant. This element contains the domain 3105 name used to generate the IDN variant. 3107 o A element that indicates the state of the NNDN: 3108 blocked, withheld or mirrored. 3110 * If a NNDN is considered undesirable for registration (i.e., 3111 unavailable for allocation to anyone), then the NNDN will be 3112 tagged as "blocked". 3114 * If a NNDN is considered a potential registration of a domain 3115 object for a particular registrant, then the NNDN will be 3116 tagged as "withheld". This status is only used when the NNDN 3117 is used for an IDN variant. 3119 * If a NNDN is considered a mirrored IDN variant of a domain 3120 object, then the NNDN will be tagged as "mirrored". A 3121 mirroringNS attribute is used to specify if the mirrored IDN 3122 variant use the NS mirror mechanism. The default value of 3123 mirroringNS is true. If another mechanism such as DNAME is 3124 used, the value of mirroringNS attribute MUST be false. 3126 o A element that contains the date and time of the NNDN 3127 object creation. 3129 Example of object: 3131 ... 3132 3133 xn--exampl-gva.test 3134 pt-BR 3135 example1.test 3136 withheld 3137 2005-04-23T11:49:00.0Z 3138 3139 ... 3141 5.6.1.2. object 3143 The element contains the ACE of a NNDN that was 3144 deleted, i.e., the . 3146 Example of object: 3148 ... 3149 3150 ... 3151 3152 xn--pingino-q2a.test 3153 3154 ... 3155 3156 ... 3158 5.6.2. CSV Model 3160 For the CSV Model of the NNDN object, the child 3161 element of the element is used to hold the new or 3162 updated NNDN objects for the deposit. The child 3163 element of the element is used to hold the deleted or 3164 purged NNDN objects for the deposit. Both the and 3165 elements contain one or more elements 3166 with the following supported "name" attribute values: 3168 "NNDN" Defines the fields and CSV file references used for the NNDN 3169 object records. 3171 The following "csvNNDN" field elements, defined for the "NNDN" 3172 element, MUST be used in the "NNDN" 3173 element: 3175 ASCII Compatible Encoding (ACE) field of the 3176 NNDN with type="eppcom:labelType" and isRequired="true". 3178 Domain name used to generate the IDN 3179 variant with type="eppcom:labelType". 3181 State of the NNDN: blocked or withheld with 3182 type="rdeNNDN:nameState". See Section 5.6.1.1 for a 3183 description of the possible values for the 3184 element. 3186 The following field elements MAY be used in the "NNDN" element: 3189 Domain name used to generate the IDN 3190 variant with type="eppcom:labelType". 3192 Defines whether the "mirroring" uses the NS mirror mechanism, as described for the 3194 "mirroringNS" attribute in Section 5.6.1.1, 3195 with type="boolean". If the field element is not defined the 3196 default value is "true". 3198 The following "rdeCsv" fields, defined in section CSV common field 3199 elements (Section 4.6.2), MUST be used in the "domain" element: 3202 Created date and time of the domain name object. 3204 The following "rdeCsv" fields, defined in section CSV common field 3205 elements (Section 4.6.2), MAY be used in the "domain" 3206 element: 3208 Name of the NNDN in Unicode character set for the 3209 field element. 3211 IDN Table Identifier for the NNDN that 3212 matches an IDN Table Reference Object record, as defined in 3213 Section 5.5.2. 3215 Example of a "NNDN" element: 3217 ... 3218 3219 ... 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3232 NNDN-YYYYMMDD.csv 3233 3234 3235 3236 ... 3237 3238 ... 3240 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3241 contains two NNDN records for an IDN with one blocked variant and 3242 one mirrored variant. 3244 xn--exampl-gva.test,pt-BR,xn--exampl.test, 3245 blocked,,2005-04-23T11:49:00.0Z 3246 xn--exampl2-gva.test,pt-BR,xn--exampl.test, 3247 mirrored,1,2005-04-23T11:49:00.0Z 3249 Example of a "NNDN" element: 3251 ... 3252 3253 ... 3254 3255 3256 3257 3258 3259 3261 NNDN-delete-YYYYMMDD.csv 3262 3263 3264 3265 ... 3266 3267 ... 3269 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The 3270 file contains one NNDN record. 3272 xn--pingino-q2a.test 3274 5.7. EPP Parameters Object 3276 The EPP Parameters Object is a pseudo-object that defines the set of 3277 object and object extension services supported by the registry, as 3278 defined in [RFC5730]. The EPP Parameters Object is only defined as 3279 XML but could be used in the the XML model or CSV model. The EPP 3280 Parameters Object is defined using the the 3281 element. The EPP Parameters Object SHOULD be included if the 3282 registry supports EPP. Only one EPP Parameters Object MUST exist at 3283 a certain point in time (watermark). 3285 The syntax and content of the children 3286 elements is as explained in section 2.4 of [RFC5730]. The children 3287 of the are as follows: 3289 o One or more elements that indicate the EPP versions 3290 supported by the registry. 3292 o One or more elements that indicate the identifiers of the 3293 text response languages supported by the registry's EPP server. 3295 o One or more elements that contain namespace URIs 3296 representing the objects that the registry's EPP server is capable 3297 of managing. 3299 o An OPTIONAL element that contains one or more 3300 elements that contain namespace URIs representing object 3301 extensions supported by the registry's EPP server. 3303 o A element that contains child elements used to describe the 3304 server's privacy policy for data collection and management. See 3305 section 2.4 of [RFC5730] for more details. 3307 Example of element object: 3309 ... 3310 3311 1.0 3312 en 3313 urn:ietf:params:xml:ns:domain-1.0 3314 3315 urn:ietf:params:xml:ns:contact-1.0 3316 3317 urn:ietf:params:xml:ns:host-1.0 3318 3319 3320 urn:ietf:params:xml:ns:rgp-1.0 3321 urn:ietf:params:xml:ns:secDNS-1.1 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 ... 3342 5.8. Policy Object 3344 The Policy object is a pseudo-object that is used to specify which 3345 OPTIONAL elements from the XML Model are REQUIRED based on the 3346 business model of the registry. For the CSV Model, the OPTIONAL 3347 "isRequired" attribute of the elements, defined in 3348 Section 4.6.1, is used to specify which OPTIONAL fields are REQUIRED 3349 based on the business model of the registry. 3351 5.8.1. object 3353 The OPTIONAL contains the following attributes: 3355 o An that defines that the referenced is 3356 REQUIRED. 3358 o that defines the XPath of the element referenced by 3359 . 3361 Example of object: 3363 ... 3364 3366 ... 3368 5.9. Header Object 3370 The Header Object is a pseudo-object that is used to specify the 3371 number of objects in the SRS at a specific point in time (watermark) 3372 regardless of the type of deposit: differential, full or incremental. 3373 The Header Object is only defined as XML but one header object MUST 3374 always be present per escrow deposit regardless of using XML Model or 3375 CSV Model. The Header Object is defined using the 3376 element. 3378 5.9.1. object 3380 The contains the following attributes: 3382 o A element that defines TLD being escrowed. 3384 o A element that contains the number of objects in the SRS 3385 at a specific point in time (watermark) regardless of the type of 3386 deposit: differential, full or incremental. The "uri" attributes 3387 reflects the XML namespace URI of the primary objects for the XML 3388 Model and CSV Model. For example, the "uri" is set to 3389 "urn:ietf:params:xml:ns:rdeDomain-1.0" for domain name objects 3390 using the XML Model, and the "uri" is set to 3391 "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name objects 3392 using the CSV Model. 3394 Example of object referencing only the XML Model 3395 objects: 3397 ... 3398 3399 test 3400 2 3402 1 3404 1 3406 1 3408 3409 1 3411 1 3413 1 3415 3416 3417 ... 3419 Example of object referencing the CSV and XML 3420 Model objects: 3422 ... 3423 3424 test 3425 2 3427 1 3429 1 3431 1 3433 3434 1 3436 1 3438 1 3440 3441 3442 ... 3444 6. RDE IDN Variants handling 3446 Depending on the Registration Policy of the Registry; for a 3447 particular domain name there may be multiple variant names. See 3448 [variantTLDsReport] for further detail on IDN variants. 3450 A registry could choose to escrow IDN variants as domains or NNDN 3451 objects. An specific IDN variant can be represented in the escrow 3452 deposit, as a domain or as a NNDN object, but not both. 3454 If using domain objects to represent IDN variants, the normal 3455 behavior during restoration of a SRS based on an escrow deposit is to 3456 restore the IDN variants as a mirrored variant. If the registration 3457 data of the IDN variant is different from the original name, the 3458 details of this specific implementation MUST be described in the IDN 3459 policy document. 3461 A NNDN or a domain name are explicit representations of an IDN 3462 variant while an IDN variant computed based on an algorithm is an 3463 implicit representation. Explicit representation of an IDN variant 3464 takes precedence over an implicit representation. 3466 7. Profile 3468 Different business models of registries exist, therefore the registry 3469 is responsible to define a profile that matches its particular 3470 business model. The profile mechanism allows a registry to extend 3471 this specification. 3473 A profile is the process of: 3475 1. Extending base objects with the mechanisms defined for XML and 3476 CSV models. 3478 * In the case of the XML model, abstract elements could be use 3479 to extend the following objects: , , , 3480 and using XML schema substitution groups 3481 feature. 3483 2. Defining a object to specify which OPTIONAL elements of 3484 this base specification are required based on the business model 3485 of the registry. An example is the element that is 3486 usually REQUIRED but it is specified as OPTIONAL in this 3487 specification to support existing business models. 3489 3. Adding new escrowed objects using the and elements. 3492 4. Providing the XML schemas to third parties that require them to 3493 validate the escrow deposits. 3495 8. Data escrow agent extended verification process 3497 The Data Escrow Agent MUST perform a extended verification process 3498 using the contents of the data escrow deposits to a point in time 3499 (watermark), last full plus all differentials or last full plus last 3500 incremental escrow deposits. The following are the minimum suggested 3501 tests: 3503 o Validate the escrow deposits using the definition agreed with the 3504 registry. 3506 * In the case of the XML model, the contents of the escrow 3507 deposits MUST be validated using the XML schemas of the 3508 profile. 3510 o Count the objects and validate that the number of objects is equal 3511 to the number objects reported in the
element of the 3512 escrow deposit of that point in time (watermark). 3514 o All contacts objects linked to domain names MUST be present. 3516 o All registrars objects linked to other objects MUST be present. 3518 o A domain name exists as a domain name or NNDN, but not both. 3520 o The elements listed as required in the element MUST be 3521 present. 3523 o All idnTableRef definitions linked from other objects MUST be 3524 present. 3526 o If an EPP Parameters Object was escrowed in the past, one and only 3527 one EPP Parameters Object MUST be present. 3529 o The watermark is not in the future. 3531 9. Formal Syntax 3533 Schemas are presented here. 3535 9.1. RDE CSV Schema 3537 Copyright (c) 2012 IETF Trust and the persons identified as authors 3538 of the code. All rights reserved. 3540 Redistribution and use in source and binary forms, with or without 3541 modification, are permitted provided that the following conditions 3542 are met: 3544 o Redistributions of source code must retain the above copyright 3545 notice, this list of conditions and the following disclaimer. 3547 o Redistributions in binary form must reproduce the above copyright 3548 notice, this list of conditions and the following disclaimer in 3549 the documentation and/or other materials provided with the 3550 distribution. 3552 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3553 names of specific contributors, may be used to endorse or promote 3554 products derived from this software without specific prior written 3555 permission. 3557 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3558 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3559 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3560 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3561 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3562 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3563 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3564 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3565 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3566 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3567 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3569 BEGIN 3570 3572 3579 3582 3584 3587 3588 3589 Registry Data Escrow Comma-Seperated Values (CSV) 3590 3591 3593 3594 3596 3597 3598 3599 3600 3601 3602 3603 3604 3606 3607 3610 3611 3612 3614 3615 3616 3617 3618 3619 3621 3622 3623 3624 3626 3627 3628 3629 3630 3631 3633 3634 3635 3636 3638 3640 3641 3643 3644 3645 3646 3647 3649 3650 3651 3652 3653 3654 3655 3656 3658 3659 3660 3662 3663 3665 3666 3667 3668 3669 3671 3672 3673 3675 3676 3678 3679 3680 3681 3682 3684 3685 3686 3688 3689 3693 3694 3695 3697 3699 3702 3703 3705 3707 3709 3710 3712 3714 3716 3718 3720 3722 3724 3726 3728 3729 3730 3731 3732 3734 3735 3736 3737 3738 3739 3740 3741 3743 3744 3745 3747 3748 3750 3752 3754 3755 3757 3758 3760 3762 3763 3764 3765 3766 3768 3769 3770 3772 3773 3774 3775 3776 3777 3779 3780 3781 3783 3784 3785 3786 3787 3788 3790 3791 3792 3794 3795 3796 3797 3798 3799 3801 3802 3803 3805 3806 3807 3808 3809 3810 3812 3813 3814 3816 3817 3819 3820 3821 3822 3823 3825 3826 3827 3829 3830 3833 3834 3836 3837 3838 3839 3840 3842 3843 3845 3847 3848 3849 3850 3851 3852 3854 3855 3856 3858 3859 3860 3861 3862 3863 3865 3866 3867 3869 3870 3871 3872 3873 3874 3876 3877 3878 3880 3881 3883 3884 3885 3886 3887 3888 3890 3891 3892 3893 3894 3895 3896 3897 3898 3900 3901 3902 3903 3905 3906 3908 3909 3910 3911 3912 3913 3915 3916 3917 3918 3920 3921 3923 3924 3925 3926 3927 3929 3930 3931 3933 3936 3937 END 3939 9.2. RDE Domain Object 3941 Copyright (c) 2011 IETF Trust and the persons identified as authors 3942 of the code. All rights reserved. 3944 Redistribution and use in source and binary forms, with or without 3945 modification, are permitted provided that the following conditions 3946 are met: 3948 o Redistributions of source code must retain the above copyright 3949 notice, this list of conditions and the following disclaimer. 3951 o Redistributions in binary form must reproduce the above copyright 3952 notice, this list of conditions and the following disclaimer in 3953 the documentation and/or other materials provided with the 3954 distribution. 3956 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3957 names of specific contributors, may be used to endorse or promote 3958 products derived from this software without specific prior written 3959 permission. 3961 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3962 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3963 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3964 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3965 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3966 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3967 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3968 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3969 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3970 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3971 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3973 BEGIN 3974 3975 3986 3987 3988 3989 3990 3991 3993 3994 3995 Registry Data Escrow Domain provisioning schema 3996 3997 3999 4002 4004 4008 4009 4010 4011 4012 4013 4015 4017 4019 4021 4023 4025 4028 4030 4033 4036 4038 4040 4042 4044 4046 4048 4050 4052 4055 4056 4057 4058 4060 4061 4062 4064 4066 4068 4070 4072 4074 4075 4077 4078 4079 4080 4081 4082 4085 4086 4087 4088 4089 4090 END 4092 9.3. CSV Domain Object 4094 Copyright (c) 2012 IETF Trust and the persons identified as authors 4095 of the code. All rights reserved. 4097 Redistribution and use in source and binary forms, with or without 4098 modification, are permitted provided that the following conditions 4099 are met: 4101 o Redistributions of source code must retain the above copyright 4102 notice, this list of conditions and the following disclaimer. 4104 o Redistributions in binary form must reproduce the above copyright 4105 notice, this list of conditions and the following disclaimer in 4106 the documentation and/or other materials provided with the 4107 distribution. 4109 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4110 names of specific contributors, may be used to endorse or promote 4111 products derived from this software without specific prior written 4112 permission. 4114 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4115 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4116 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4117 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4118 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4119 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4120 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4121 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4122 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4123 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4124 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4126 BEGIN 4127 4129 4140 4143 4145 4147 4149 4151 4153 4156 4157 4158 Domain Name Comma-Separated Values (CSV) Object 4159 4160 4162 4165 4168 4169 4170 4171 4172 4173 4174 4175 4176 4178 4181 4184 4185 4186 4187 4188 4189 4190 4191 4192 4194 4195 4198 4199 4202 4203 4204 4205 4206 4208 4209 4210 4212 4213 4216 4217 4218 4219 4220 4222 4223 4224 4225 4227 4228 4230 4231 4232 4233 4234 4236 4237 4238 4240 4241 4244 4245 4248 4249 4252 4253 4256 4257 4260 4261 4264 4265 4268 4269 4271 4272 4273 4274 4275 4277 4278 4279 4281 4282 4285 4286 4289 4290 4291 4292 4293 4294 4296 4297 4298 4300 4303 4304 END 4306 9.4. RDE Host Object 4308 Copyright (c) 2011 IETF Trust and the persons identified as authors 4309 of the code. All rights reserved. 4311 Redistribution and use in source and binary forms, with or without 4312 modification, are permitted provided that the following conditions 4313 are met: 4315 o Redistributions of source code must retain the above copyright 4316 notice, this list of conditions and the following disclaimer. 4318 o Redistributions in binary form must reproduce the above copyright 4319 notice, this list of conditions and the following disclaimer in 4320 the documentation and/or other materials provided with the 4321 distribution. 4323 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4324 names of specific contributors, may be used to endorse or promote 4325 products derived from this software without specific prior written 4326 permission. 4328 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4329 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4330 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4331 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4332 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4333 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4334 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4335 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4336 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4337 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4338 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4340 BEGIN 4341 4342 4350 4351 4352 4354 4355 4356 Registry Data Escrow Host provisioning schema 4357 4358 4360 4362 4363 4366 4367 4368 4369 4370 4371 4373 4375 4377 4380 4382 4384 4386 4388 4390 4392 4393 4394 4395 4397 4398 4399 4400 4401 4402 4404 4406 4407 4408 4409 4410 4411 END 4413 9.5. CSV Host Object 4415 Copyright (c) 2012 IETF Trust and the persons identified as authors 4416 of the code. All rights reserved. 4418 Redistribution and use in source and binary forms, with or without 4419 modification, are permitted provided that the following conditions 4420 are met: 4422 o Redistributions of source code must retain the above copyright 4423 notice, this list of conditions and the following disclaimer. 4425 o Redistributions in binary form must reproduce the above copyright 4426 notice, this list of conditions and the following disclaimer in 4427 the documentation and/or other materials provided with the 4428 distribution. 4430 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4431 names of specific contributors, may be used to endorse or promote 4432 products derived from this software without specific prior written 4433 permission. 4435 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4436 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4437 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4438 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4439 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4440 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4441 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4442 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4443 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4444 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4445 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4447 BEGIN 4448 4450 4459 4462 4464 4467 4469 4472 4473 4474 Host Comma-Separated Values (CSV) Object 4475 4476 4478 4481 4484 4485 4486 4487 4488 4489 4490 4491 4492 4494 4497 4500 4501 4502 4503 4504 4505 4506 4507 4508 4510 4511 4514 4515 4517 4518 4519 4520 4521 4523 4524 4525 4527 4528 4530 4531 4532 4533 4534 4536 4537 4538 4540 4541 4544 4545 4546 4547 4548 4549 4551 4552 4553 4555 4558 4559 END 4561 9.6. RDE Contact Object 4563 Copyright (c) 2011 IETF Trust and the persons identified as authors 4564 of the code. All rights reserved. 4566 Redistribution and use in source and binary forms, with or without 4567 modification, are permitted provided that the following conditions 4568 are met: 4570 o Redistributions of source code must retain the above copyright 4571 notice, this list of conditions and the following disclaimer. 4573 o Redistributions in binary form must reproduce the above copyright 4574 notice, this list of conditions and the following disclaimer in 4575 the documentation and/or other materials provided with the 4576 distribution. 4578 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4579 names of specific contributors, may be used to endorse or promote 4580 products derived from this software without specific prior written 4581 permission. 4583 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4584 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4585 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4586 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4587 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4588 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4589 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4590 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4591 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4592 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4593 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4595 BEGIN 4596 4597 4605 4606 4607 4608 4609 4610 4611 Registry Data Escrow contact provisioning schema 4612 4613 4615 4618 4620 4624 4625 4626 4627 4628 4629 4631 4633 4635 4637 4639 4641 4643 4645 4647 4649 4651 4653 4655 4658 4660 4661 4662 4663 4665 4666 4667 4668 4669 4670 4671 4672 4673 4675 4676 4677 4678 4679 4680 4683 4684 4685 4686 4687 4688 END 4690 9.7. CSV Contact Object 4692 Copyright (c) 2012 IETF Trust and the persons identified as authors 4693 of the code. All rights reserved. 4695 Redistribution and use in source and binary forms, with or without 4696 modification, are permitted provided that the following conditions 4697 are met: 4699 o Redistributions of source code must retain the above copyright 4700 notice, this list of conditions and the following disclaimer. 4702 o Redistributions in binary form must reproduce the above copyright 4703 notice, this list of conditions and the following disclaimer in 4704 the documentation and/or other materials provided with the 4705 distribution. 4707 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4708 names of specific contributors, may be used to endorse or promote 4709 products derived from this software without specific prior written 4710 permission. 4712 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4713 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4714 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4715 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4716 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4717 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4718 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4719 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4720 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4721 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4722 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4724 BEGIN 4725 4727 4736 4739 4741 4743 4745 4748 4749 4750 Contact Comma-Separated Values (CSV) Object 4751 4752 4753 4756 4759 4760 4761 4762 4763 4764 4765 4766 4767 4769 4772 4775 4776 4777 4778 4779 4780 4781 4782 4783 4785 4786 4788 4789 4790 4791 4792 4794 4795 4796 4798 4799 4803 4804 4806 4808 4809 4810 4811 4812 4814 4815 4816 4818 4819 4821 4824 4825 4827 4828 4829 4830 4831 4833 4834 4835 4837 4841 4843 4844 4845 4846 4847 4849 4850 4851 4853 4854 4855 4856 4857 4858 4860 4861 4862 4863 4865 4866 4867 4868 4869 4870 4872 4873 4874 4875 4877 4878 4881 4882 4885 4886 4887 4889 4890 4891 4892 4893 4895 4896 4897 4899 4900 4903 4904 4907 4908 4910 4911 4912 4913 4914 4916 4917 4918 4919 4921 4922 4924 4925 4926 4927 4928 4930 4931 4932 4933 4935 4936 4939 4941 4943 4945 4947 4949 4951 4953 4955 4957 4959 4961 4963 4965 4967 4969 4971 4973 4975 4977 4978 4979 4980 4981 4983 4984 4985 4986 4987 4990 4991 4992 4993 4994 4995 4997 4998 4999 5001 5004 5005 END 5007 9.8. RDE Registrar Object 5009 Copyright (c) 2011 IETF Trust and the persons identified as authors 5010 of the code. All rights reserved. 5012 Redistribution and use in source and binary forms, with or without 5013 modification, are permitted provided that the following conditions 5014 are met: 5016 o Redistributions of source code must retain the above copyright 5017 notice, this list of conditions and the following disclaimer. 5019 o Redistributions in binary form must reproduce the above copyright 5020 notice, this list of conditions and the following disclaimer in 5021 the documentation and/or other materials provided with the 5022 distribution. 5024 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5025 names of specific contributors, may be used to endorse or promote 5026 products derived from this software without specific prior written 5027 permission. 5029 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5030 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5031 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5032 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5033 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5034 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5035 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5036 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5037 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5038 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5039 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5041 BEGIN 5042 5043 5052 5053 5054 5055 5056 5058 5059 5060 Registry Data Escrow registrar provisioning schema 5061 5062 5064 5067 5069 5072 5073 5074 5075 5076 5077 5079 5082 5084 5086 5089 5091 5093 5095 5097 5099 5101 5103 5104 5105 5106 5108 5109 5110 5111 5112 5113 5115 5116 5117 5118 5119 5120 5121 5123 5124 5125 5127 5128 5131 5133 5134 5135 5136 5137 5138 5140 5141 5142 5145 5147 5150 5152 5154 5155 5157 5158 5159 5160 5161 5162 5164 5165 5166 5167 5168 5170 5171 5172 5173 5174 5176 5177 5178 5179 5180 5182 5183 5184 5186 5188 5189 5191 5192 5193 5194 5195 5196 5199 5200 5201 5202 5203 5204 END 5206 9.9. CSV Registrar Object 5208 Copyright (c) 2012 IETF Trust and the persons identified as authors 5209 of the code. All rights reserved. 5211 Redistribution and use in source and binary forms, with or without 5212 modification, are permitted provided that the following conditions 5213 are met: 5215 o Redistributions of source code must retain the above copyright 5216 notice, this list of conditions and the following disclaimer. 5218 o Redistributions in binary form must reproduce the above copyright 5219 notice, this list of conditions and the following disclaimer in 5220 the documentation and/or other materials provided with the 5221 distribution. 5223 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5224 names of specific contributors, may be used to endorse or promote 5225 products derived from this software without specific prior written 5226 permission. 5228 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5229 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5230 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5231 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5232 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5233 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5234 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5235 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5236 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5237 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5238 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5240 BEGIN 5241 5243 5253 5256 5258 5260 5262 5264 5267 5268 5269 Registar Comma-Separated Values (CSV) Object 5270 5271 5273 5276 5279 5280 5281 5282 5283 5284 5285 5286 5287 5289 5292 5295 5296 5297 5298 5299 5300 5301 5302 5303 5305 5306 5309 5310 5313 5314 5315 5316 5317 5318 5320 5322 5323 5324 5326 5327 5331 5332 5334 5336 5337 5338 5339 5340 5342 5343 5344 5346 5347 5348 5349 5350 5351 5352 5353 5355 5356 5357 5358 5359 5360 5361 5362 5364 5365 5368 5371 5372 END 5374 9.10. RDE IDN Table Reference Objects 5376 Copyright (c) 2011 IETF Trust and the persons identified as authors 5377 of the code. All rights reserved. 5379 Redistribution and use in source and binary forms, with or without 5380 modification, are permitted provided that the following conditions 5381 are met: 5383 o Redistributions of source code must retain the above copyright 5384 notice, this list of conditions and the following disclaimer. 5386 o Redistributions in binary form must reproduce the above copyright 5387 notice, this list of conditions and the following disclaimer in 5388 the documentation and/or other materials provided with the 5389 distribution. 5391 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5392 names of specific contributors, may be used to endorse or promote 5393 products derived from this software without specific prior written 5394 permission. 5396 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5397 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5398 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5399 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5400 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5401 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5402 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5403 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5404 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5405 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5406 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5408 BEGIN 5409 5410 5415 5417 5418 5419 Registry Data Escrow IDN provisioning schema 5420 5421 5423 5425 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5441 5442 5443 5444 5445 5446 5447 5448 5449 5451 5452 5453 5454 5455 5456 5457 5459 5460 END 5462 9.11. CSV IDN Language Object 5464 Copyright (c) 2012 IETF Trust and the persons identified as authors 5465 of the code. All rights reserved. 5467 Redistribution and use in source and binary forms, with or without 5468 modification, are permitted provided that the following conditions 5469 are met: 5471 o Redistributions of source code must retain the above copyright 5472 notice, this list of conditions and the following disclaimer. 5474 o Redistributions in binary form must reproduce the above copyright 5475 notice, this list of conditions and the following disclaimer in 5476 the documentation and/or other materials provided with the 5477 distribution. 5479 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5480 names of specific contributors, may be used to endorse or promote 5481 products derived from this software without specific prior written 5482 permission. 5484 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5485 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5486 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5487 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5488 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5489 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5490 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5491 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5492 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5493 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5494 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5496 BEGIN 5497 5499 5506 5509 5511 5514 5515 5516 IDN Language Comma-Separated Values (CSV) Object 5517 5518 5520 5523 5526 5527 5528 5529 5530 5531 5532 5533 5534 5536 5539 5542 5543 5544 5545 5546 5547 5548 5549 5550 5552 5555 5556 END 5558 9.12. EPP Parameters Object 5560 Copyright (c) 2011 IETF Trust and the persons identified as authors 5561 of the code. All rights reserved. 5563 Redistribution and use in source and binary forms, with or without 5564 modification, are permitted provided that the following conditions 5565 are met: 5567 o Redistributions of source code must retain the above copyright 5568 notice, this list of conditions and the following disclaimer. 5570 o Redistributions in binary form must reproduce the above copyright 5571 notice, this list of conditions and the following disclaimer in 5572 the documentation and/or other materials provided with the 5573 distribution. 5575 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5576 names of specific contributors, may be used to endorse or promote 5577 products derived from this software without specific prior written 5578 permission. 5580 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5581 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5582 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5583 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5584 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5585 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5586 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5587 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5588 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5589 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5590 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5592 BEGIN 5593 5594 5602 5603 5604 5605 5606 5607 Registry Data Escrow EPP Parameters schema 5608 5609 5611 5612 5615 5616 5619 5620 5621 5622 5623 5625 5627 5629 5632 5634 5635 5636 5637 5638 5639 END 5641 9.13. NNDN Object 5643 Copyright (c) 2011 IETF Trust and the persons identified as authors 5644 of the code. All rights reserved. 5646 Redistribution and use in source and binary forms, with or without 5647 modification, are permitted provided that the following conditions 5648 are met: 5650 o Redistributions of source code must retain the above copyright 5651 notice, this list of conditions and the following disclaimer. 5653 o Redistributions in binary form must reproduce the above copyright 5654 notice, this list of conditions and the following disclaimer in 5655 the documentation and/or other materials provided with the 5656 distribution. 5658 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5659 names of specific contributors, may be used to endorse or promote 5660 products derived from this software without specific prior written 5661 permission. 5663 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5664 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5665 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5666 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5667 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5668 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5669 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5670 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5671 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5672 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5673 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5675 BEGIN 5676 5677 5685 5686 5687 5689 5690 5691 Registry Data Escrow NNDN provisioning schema 5692 5693 5695 5697 5698 5701 5702 5703 5704 5705 5706 5708 5710 5712 5714 5716 5718 5719 5720 5721 5723 5724 5725 5726 5727 5728 5729 5731 5732 5733 5734 5736 5737 5738 5740 5741 5742 5743 5744 5745 5748 5750 5751 5752 5753 5754 END 5756 9.14. CSV NNDN Object 5758 Copyright (c) 2013 IETF Trust and the persons identified as authors 5759 of the code. All rights reserved. 5761 Redistribution and use in source and binary forms, with or without 5762 modification, are permitted provided that the following conditions 5763 are met: 5765 o Redistributions of source code must retain the above copyright 5766 notice, this list of conditions and the following disclaimer. 5768 o Redistributions in binary form must reproduce the above copyright 5769 notice, this list of conditions and the following disclaimer in 5770 the documentation and/or other materials provided with the 5771 distribution. 5773 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5774 names of specific contributors, may be used to endorse or promote 5775 products derived from this software without specific prior written 5776 permission. 5778 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5779 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5780 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5781 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5782 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5783 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5784 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5785 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5786 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5787 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5788 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5790 BEGIN 5791 5793 5801 5804 5806 5808 5811 5812 5813 NNDN (NNDN's not domain name) (CSV) Object 5814 5815 5817 5820 5823 5824 5825 5826 5827 5828 5829 5830 5831 5833 5836 5839 5840 5841 5842 5843 5844 5845 5847 5848 5850 5851 5854 5855 5858 5859 5862 5863 5864 5865 5866 5868 5869 5870 5872 5873 5877 5880 5881 END 5883 9.15. Policy Object 5885 Copyright (c) 2011 IETF Trust and the persons identified as authors 5886 of the code. All rights reserved. 5888 Redistribution and use in source and binary forms, with or without 5889 modification, are permitted provided that the following conditions 5890 are met: 5892 o Redistributions of source code must retain the above copyright 5893 notice, this list of conditions and the following disclaimer. 5895 o Redistributions in binary form must reproduce the above copyright 5896 notice, this list of conditions and the following disclaimer in 5897 the documentation and/or other materials provided with the 5898 distribution. 5900 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5901 names of specific contributors, may be used to endorse or promote 5902 products derived from this software without specific prior written 5903 permission. 5905 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5906 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5907 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5908 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5909 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5910 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5911 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5912 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5913 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5914 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5915 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5917 BEGIN 5918 5919 5925 5926 5927 Registry Data Escrow Policy schema 5928 5929 5931 5932 5935 5936 5937 5938 5939 5940 5941 5942 5943 5944 END 5946 9.16. Header Object 5948 Copyright (c) 2011 IETF Trust and the persons identified as authors 5949 of the code. All rights reserved. 5951 Redistribution and use in source and binary forms, with or without 5952 modification, are permitted provided that the following conditions 5953 are met: 5955 o Redistributions of source code must retain the above copyright 5956 notice, this list of conditions and the following disclaimer. 5958 o Redistributions in binary form must reproduce the above copyright 5959 notice, this list of conditions and the following disclaimer in 5960 the documentation and/or other materials provided with the 5961 distribution. 5963 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5964 names of specific contributors, may be used to endorse or promote 5965 products derived from this software without specific prior written 5966 permission. 5968 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5969 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5970 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5971 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5972 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5973 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5974 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5975 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5976 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5977 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5978 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5980 BEGIN 5981 5982 5989 5990 5992 5993 5994 Registry Data Escrow Header schema 5995 5996 5998 5999 6002 6003 6004 6005 6006 6007 6008 6010 6011 6012 6013 6015 6016 6017 6018 6019 6020 6021 6022 6023 END 6025 10. Internationalization Considerations 6027 Data Escrow deposits are represented in XML, which provides native 6028 support for encoding information using the Unicode character set and 6029 its more compact representations including UTF-8. Conformant XML 6030 processors recognize both UTF-8 and UTF-16. Though XML includes 6031 provisions to identify and use other character encodings through use 6032 of an "encoding" attribute in an declaration, use of UTF-8 is 6033 RECOMMENDED. 6035 11. IANA Considerations 6037 This document uses URNs to describe XML namespaces and XML schemas 6038 conforming to a registry mechanism described in [RFC3688]. Fourteen 6039 URI assignments have been registered by the IANA. 6041 Registration request for the RDE CSV namespace: 6043 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6045 Registrant Contact: See the "Author's Address" section of this 6046 document. 6048 XML: None. Namespace URIs do not represent an XML specification. 6050 Registration request for the RDE CSV XML schema: 6052 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6054 Registrant Contact: See the "Author's Address" section of this 6055 document. 6057 See the "Formal Syntax" section of this document. 6059 Registration request for the RDE domain namespace: 6061 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6063 Registrant Contact: See the "Author's Address" section of this 6064 document. 6066 XML: None. Namespace URIs do not represent an XML specification. 6068 Registration request for the RDE domain XML schema: 6070 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6071 Registrant Contact: See the "Author's Address" section of this 6072 document. 6074 See the "Formal Syntax" section of this document. 6076 Registration request for the CSV domain namespace: 6078 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6080 Registrant Contact: See the "Author's Address" section of this 6081 document. 6083 XML: None. Namespace URIs do not represent an XML specification. 6085 Registration request for the CSV domain XML schema: 6087 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6089 Registrant Contact: See the "Author's Address" section of this 6090 document. 6092 See the "Formal Syntax" section of this document. 6094 Registration request for the RDE host namespace: 6096 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6098 Registrant Contact: See the "Author's Address" section of this 6099 document. 6101 XML: None. Namespace URIs do not represent an XML specification. 6103 Registration request for the RDE host XML schema: 6105 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6107 Registrant Contact: See the "Author's Address" section of this 6108 document. 6110 See the "Formal Syntax" section of this document. 6112 Registration request for the CSV host namespace: 6114 URI: urn:ietf:params:xml:ns:csvHost-1.0 6116 Registrant Contact: See the "Author's Address" section of this 6117 document. 6119 XML: None. Namespace URIs do not represent an XML specification. 6121 Registration request for the CSV host XML schema: 6123 URI: urn:ietf:params:xml:schema:csvHost-1.0 6125 Registrant Contact: See the "Author's Address" section of this 6126 document. 6128 See the "Formal Syntax" section of this document. 6130 Registration request for the RDE contact namespace: 6132 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6134 Registrant Contact: See the "Author's Address" section of this 6135 document. 6137 XML: None. Namespace URIs do not represent an XML specification. 6139 Registration request for the RDE contact XML schema: 6141 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6143 Registrant Contact: See the "Author's Address" section of this 6144 document. 6146 See the "Formal Syntax" section of this document. 6148 Registration request for the CSV contact namespace: 6150 URI: urn:ietf:params:xml:ns:csvContact-1.0 6152 Registrant Contact: See the "Author's Address" section of this 6153 document. 6155 XML: None. Namespace URIs do not represent an XML specification. 6157 Registration request for the CSV contact XML schema: 6159 URI: urn:ietf:params:xml:schema:csvContact-1.0 6161 Registrant Contact: See the "Author's Address" section of this 6162 document. 6164 See the "Formal Syntax" section of this document. 6166 Registration request for the RDE registrar namespace: 6168 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6170 Registrant Contact: See the "Author's Address" section of this 6171 document. 6173 XML: None. Namespace URIs do not represent an XML specification. 6175 Registration request for the RDE registrar XML schema: 6177 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6179 Registrant Contact: See the "Author's Address" section of this 6180 document. 6182 See the "Formal Syntax" section of this document. 6184 Registration request for the CSV registrar namespace: 6186 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6188 Registrant Contact: See the "Author's Address" section of this 6189 document. 6191 XML: None. Namespace URIs do not represent an XML specification. 6193 Registration request for the CSV registrar XML schema: 6195 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6197 Registrant Contact: See the "Author's Address" section of this 6198 document. 6200 See the "Formal Syntax" section of this document. 6202 Registration request for the RDE IDN namespace: 6204 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6206 Registrant Contact: See the "Author's Address" section of this 6207 document. 6209 XML: None. Namespace URIs do not represent an XML specification. 6211 Registration request for the RDE IDN XML schema: 6213 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6214 Registrant Contact: See the "Author's Address" section of this 6215 document. 6217 See the "Formal Syntax" section of this document. 6219 Registration request for the CSV IDN namespace: 6221 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6223 Registrant Contact: See the "Author's Address" section of this 6224 document. 6226 XML: None. Namespace URIs do not represent an XML specification. 6228 Registration request for the CSV IDN XML schema: 6230 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6232 Registrant Contact: See the "Author's Address" section of this 6233 document. 6235 See the "Formal Syntax" section of this document. 6237 Registration request for the RDE NNDN namespace: 6239 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6241 Registrant Contact: See the "Author's Address" section of this 6242 document. 6244 XML: None. Namespace URIs do not represent an XML specification. 6246 Registration request for the RDE NNDN XML schema: 6248 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6250 Registrant Contact: See the "Author's Address" section of this 6251 document. 6253 See the "Formal Syntax" section of this document. 6255 Registration request for the CSV NNDN namespace: 6257 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6259 Registrant Contact: See the "Author's Address" section of this 6260 document. 6262 XML: None. Namespace URIs do not represent an XML specification. 6264 Registration request for the CSV NNDN XML schema: 6266 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6268 Registrant Contact: See the "Author's Address" section of this 6269 document. 6271 See the "Formal Syntax" section of this document. 6273 Registration request for the RDE EPP parameters namespace: 6275 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6277 Registrant Contact: See the "Author's Address" section of this 6278 document. 6280 XML: None. Namespace URIs do not represent an XML specification. 6282 Registration request for the RDE EPP parameters XML schema: 6284 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6286 Registrant Contact: See the "Author's Address" section of this 6287 document. 6289 See the "Formal Syntax" section of this document. 6291 12. Security Considerations 6293 This specification does not define the security mechanisms to be used 6294 in the transmission of the data escrow deposits, since it only 6295 specifies the minimum necessary to enable the rebuilding of a 6296 Registry from deposits without intervention from the original 6297 Registry. 6299 Depending on local policies, some elements or most likely, the whole 6300 deposit will be considered confidential. As such the Registry 6301 transmitting the data to the Escrow Agent SHOULD take all the 6302 necessary precautions like encrypting the data itself and/or the 6303 transport channel to avoid inadvertent disclosure of private data. 6305 It is also of the utmost importance the authentication of the parties 6306 passing data escrow deposit files. The Escrow Agent SHOULD properly 6307 authenticate the identity of the Registry before accepting data 6308 escrow deposits. In a similar manner, the Registry SHOULD 6309 authenticate the identity of the Escrow Agent before submitting any 6310 data. 6312 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6313 checking mechanisms to ensure the data transmitted is what the source 6314 intended. Validation of the contents by the Escrow Agent is 6315 RECOMMENDED to ensure not only the file was transmitted correctly 6316 from the Registry, but also the contents are also "meaningful". 6318 13. Acknowledgments 6320 Parts of this document are based on EPP [RFC5730] and related RFCs by 6321 Scott Hollenbeck. 6323 TBD 6325 14. Change History 6327 [[RFC Editor: Please remove this section.]] 6329 14.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to 6330 -dnrd-objects-mapping-00 6332 1. Added definition for child elements under the element. 6334 2. Added definition for child elements under the element. 6336 3. Added definition for child elements under the element. 6338 4. Rewrote the IDN Variants Handling section to use the variant 6339 states as described in ICANN's Study of Issues Related to the 6340 Management of IDN Variant TLDs. 6342 5. Renamed to in the . 6344 6. Renamed to in the element. 6346 7. Renamed to in the element. 6348 8. Added element under element. 6350 9. Fixed some typographical errors and omissions. 6352 14.2. Changes from version 00 to 01 6354 1. Specify OPTIONAL elements in the draft. 6356 2. Added NNDN object to support list of reserved names and different 6357 IDN variants models. 6359 3. Removed subordinated host element from the domain object. 6361 4. Added eppParams object. 6363 5. Added variantGenerator element to the domain object. 6365 6. Added lgr to the IDN table object. 6367 14.3. Changes from version 01 to 02 6369 1. Updates to the all objects based on feedback from the list. 6371 2. Start of XML and CSV drafts merge. 6373 3. Added header object. 6375 4. Added report object. 6377 5. Added notification object. 6379 6. Added Data Escrow Agent Extended Verification Process section. 6381 7. Added Notifications from Registries to Third Parties. 6383 8. Added Notifications from Data Escrow Agents to Third Parties. 6385 9. Added FULL, DIFF deposit examples using the XML model only. 6387 14.4. Changes from version 02 to 03 6389 1. Remove authinfo from the XML Schema. 6391 2. Resend attribute is now an element 6393 3. Scope attribute added to policy object. 6395 14.5. Changes from version 03 to 04 6397 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into 6398 draft-arias-noguchi-dnrd-objects-mapping-02. 6400 2. Changed the cksum attribute of to use CRC32 and 6401 changed all of the sample cksum values to use CRC32, based on 6402 feedback from David Kipling. 6404 3. Changed the optional element to be an optional 6405 "sep" attribute value of the element with a default 6406 value of "," based on feedback from David Kipling. 6408 4. Added support for the optional "parent" attribute for the to the 6409 CSV fields to indicate a field as a reference to a parent 6410 object, based on feedback from David Kipling. 6412 5. Added support for the CSV model for the NNDN. 6414 6. Added support to delete hosts based on roid. 6416 7. Added mirrored state to NNDN 6418 8. Minor fixes to XML XSDs. 6420 9. The Report and Notification objects were moved to 6421 draft-lozano-icann-registry-interfaces 6423 10. The section Data escrow notifications was moved to 6424 draft-lozano-icann-registry-interfaces 6426 11. Removed references to the , , and 6427 from the "hostStatuses" and "hostAddresses" CSV 6428 files. 6430 12. Removed references to the , , and 6431 from the "contactStatuses" CSV file. 6433 13. Removed references to the , , and 6434 from the "domainContacts", "domainStatuses", 6435 and "domainNameServers" CSV files. 6437 14. Changed to . 6439 15. Replaced use of to new field 6440 in the "domain", "idnLanguage", and "NNDN" CSV files. 6442 16. Replaced use of with in the 6443 "host" element. 6445 17. Changed the foreign key of the hosts to use 6446 instead of and removed use of in 6447 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6448 files. 6450 18. Added use of the MUST keyword for CSV fields that are required 6451 to be supported in an EPP based system. 6453 19. Removed use of the field element for the 6454 "registrar" CSV file. 6456 20. Added definition of field element. 6458 14.6. Changes from version 04 to 05 6460 1. Updated the examples of the full and differential deposits using 6461 the CSV and XML model. 6463 2. Made optional for the "domainTransfer" CSV file 6464 to match the XML definition. 6466 3. Made optional for the "domain" CSV file 6467 to match the XML definition. 6469 4. Made optional for the "domain" and "contact" CSV 6470 files to match the XML definition. 6472 5. Change from IDREF to idType. 6474 6. Minor editorial changes. 6476 15. Example of a full deposit using the XML model 6478 Example of a full deposit using the XML model: 6480 6481 6497 2010-10-17T00:00:00Z 6498 6499 1.0 6500 urn:ietf:params:xml:ns:rdeHeader-1.0 6501 6502 urn:ietf:params:xml:ns:rdeContact-1.0 6503 6504 urn:ietf:params:xml:ns:rdeHost-1.0 6505 6506 urn:ietf:params:xml:ns:rdeDomain-1.0 6507 6508 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6509 6510 urn:ietf:params:xml:ns:rdeIDN-1.0 6511 6512 urn:ietf:params:xml:ns:rdeNNDN-1.0 6513 6514 urn:ietf:params:xml:ns:rdeEppParams-1.0 6515 6516 6518 6519 6520 6521 6522 test 6523 2 6525 6526 1 6528 6529 1 6531 6532 1 6534 6535 1 6537 6538 1 6540 6541 1 6543 6544 6546 6547 6548 example1.test 6549 Dexample1-TEST 6550 6551 jd1234 6552 sh8013 6553 sh8013 6554 6555 ns1.example.com 6556 ns1.example1.test 6557 6558 RegistrarX 6559 RegistrarX 6560 1999-04-03T22:00:00.0Z 6561 2015-04-03T22:00:00.0Z 6562 6564 6565 6566 example2.test 6567 Dexample2-TEST 6568 6569 6570 jd1234 6571 sh8013 6572 sh8013 6573 RegistrarX 6574 RegistrarX 6575 1999-04-03T22:00:00.0Z 6576 2015-04-03T22:00:00.0Z 6577 6579 6580 6581 ns1.example1.test 6582 Hns1_example_test-TEST 6583 6584 6585 192.0.2.2 6586 192.0.2.29 6587 1080:0:0:0:8:800:200C:417A 6588 6589 RegistrarX 6590 RegistrarX 6591 1999-05-08T12:10:00.0Z 6592 RegistrarX 6593 2009-10-03T09:34:00.0Z 6594 6596 6597 6598 sh8013 6599 Csh8013-TEST 6600 6601 6602 6603 John Doe 6604 Example Inc. 6605 6606 123 Example Dr. 6607 Suite 100 6608 Dulles 6609 VA 6610 20166-6503 6611 US 6612 6613 6614 +1.7035555555 6615 6616 +1.7035555556 6617 6618 jdoe@example.test 6619 6620 RegistrarX 6621 RegistrarX 6622 6623 2009-09-13T08:01:00.0Z 6624 6625 RegistrarX 6626 6627 2009-11-26T09:10:00.0Z 6628 6629 2009-12-03T09:05:00.0Z 6630 6631 6632 6633 6634 6635 6637 6638 6639 RegistrarX 6640 Registrar X 6641 123 6642 ok 6643 6644 6645 123 Example Dr. 6646 6647 Suite 100 6648 6649 Dulles 6650 VA 6651 20166-6503 6652 US 6653 6654 6655 +1.7035555555 6656 6657 +1.7035555556 6658 6659 jdoe@example.test 6660 6661 http://www.example.test 6662 6663 6664 whois.example.test 6665 6666 http://whois.example.test 6667 6668 6669 2005-04-23T11:49:00.0Z 6670 6671 2009-02-17T17:51:00.0Z 6672 6673 6675 6676 6677 6678 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 6679 6680 6681 http://registro.br/dominio/regras.html 6682 6683 6685 6686 6687 xn--exampl-gva.test 6688 pt-BR 6689 example1.test 6690 withheld 6691 2005-04-23T11:49:00.0Z 6692 6694 6695 6696 1.0 6697 en 6698 6699 urn:ietf:params:xml:ns:domain-1.0 6700 6701 6702 urn:ietf:params:xml:ns:contact-1.0 6703 6704 6705 urn:ietf:params:xml:ns:host-1.0 6706 6707 6708 urn:ietf:params:xml:ns:rgp-1.0 6709 6710 urn:ietf:params:xml:ns:secDNS-1.1 6711 6712 6713 6714 6715 6716 6717 6718 6719 6720 6721 6722 6723 6724 6725 6726 6727 6728 6729 6730 6733 6735 6737 16. Example of differential deposit using the XML model 6739 Example of a differential deposit using the XML model: 6741 6742 6757 2010-10-17T00:00:00Z 6758 6759 1.0 6760 urn:ietf:params:xml:ns:rdeHeader-1.0 6761 6762 urn:ietf:params:xml:ns:rdeContact-1.0 6763 6764 urn:ietf:params:xml:ns:rdeHost-1.0 6765 6766 urn:ietf:params:xml:ns:rdeDomain-1.0 6767 6768 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6769 6770 urn:ietf:params:xml:ns:rdeIDN-1.0 6771 6772 urn:ietf:params:xml:ns:rdeNNDN-1.0 6773 6774 urn:ietf:params:xml:ns:rdeEppParams-1.0 6775 6776 6778 6779 6780 6781 example2.test 6782 6783 6785 6786 6787 6788 6789 test 6790 1 6792 6793 1 6795 6796 1 6798 6799 1 6801 6802 1 6804 6805 1 6807 6808 1 6810 6811 6812 6813 6815 17. Example of a full deposit using the CSV model 6817 Example of a full deposit using the CSV model: 6819 6820 6846 2010-10-18T00:00:00Z 6847 6848 1.0 6849 urn:ietf:params:xml:ns:csvDomain-1.0 6850 urn:ietf:params:xml:ns:csvHost-1.0 6851 urn:ietf:params:xml:ns:csvContact-1.0 6852 urn:ietf:params:xml:ns:csvRegistrar-1.0 6853 urn:ietf:params:xml:ns:csvIDN-1.0 6854 urn:ietf:params:xml:ns:csvNNDN-1.0 6855 urn:ietf:params:xml:ns:rdeEppParams-1.0 6856 6857 6858 6859 test 6860 6861 4 6862 6863 6864 2 6865 6866 6867 2 6868 6869 6870 1 6871 6872 6873 2 6874 6875 6876 2 6877 6878 6879 1 6880 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6902 domain-YYYYMMDD.csv 6903 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 6915 domainContacts-YYYYMMDD.csv 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925 6926 6927 6928 6930 domainStatuses-YYYYMMDD.csv 6931 6932 6933 6934 6935 6936 6937 6938 6939 6940 6942 domainNameServers-YYYYMMDD.csv 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6958 dnssec-ds-YYYYMMDD.csv 6959 6960 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6974 dnssec-key-YYYYMMDD.csv 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6993 domainTransfer-YYYYMMDD.csv 6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010 7011 7012 7013 7015 host-YYYYMMDD.csv 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7029 hostStatuses-YYYYMMDD.csv 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7042 hostAddresses-YYYYMMDD.csv 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7066 7068 contact-YYYYMMDD.csv 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7082 contactStatuses-YYYYMMDD.csv 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 7103 contactPostal-YYYYMMDD.csv 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7121 contactTransfer-YYYYMMDD.csv 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7142 contactDisclose-YYYYMMDD.csv 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7174 registrar-YYYYMMDD.csv 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7188 idnLanguage-YYYYMMDD.csv 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7206 NNDN-YYYYMMDD.csv 7207 7208 7209 7210 7211 7212 1.0 7213 en 7214 urn:ietf:params:xml:ns:domain-1.0 7215 7216 urn:ietf:params:xml:ns:host-1.0 7217 7218 urn:ietf:params:xml:ns:contact-1.0 7219 7220 7221 urn:ietf:params:xml:ns:secDNS-1.1 7222 7223 urn:ietf:params:xml:ns:rgp-1.0 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7250 18. Example of differential deposit using the CSV model 7252 Example of a differential deposit using the CSV model: 7254 7255 7281 2010-10-18T00:00:00Z 7282 7283 1.0 7284 urn:ietf:params:xml:ns:csvDomain-1.0 7285 urn:ietf:params:xml:ns:csvHost-1.0 7286 urn:ietf:params:xml:ns:csvContact-1.0 7287 urn:ietf:params:xml:ns:csvRegistrar-1.0 7288 urn:ietf:params:xml:ns:csvIDN-1.0 7289 7290 7291 7292 7293 7294 7295 7296 7297 7299 NNDN-delete-YYYYMMDD.csv 7300 7301 7302 7303 7304 7305 7306 7307 test 7308 7309 4 7310 7311 7312 2 7313 7314 7315 2 7316 7317 7318 1 7319 7320 7321 2 7322 7323 7324 2 7325 7326 7327 1 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7350 domain-YYYYMMDD.csv 7351 7352 7354 7355 7356 7357 7358 7359 7360 7361 7362 7364 domainContacts-YYYYMMDD.csv 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7379 domainStatuses-YYYYMMDD.csv 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7391 domainNameServers-YYYYMMDD.csv 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7407 dnssec-YYYYMMDD.csv 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7426 domainTransfer-YYYYMMDD.csv 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7448 host-YYYYMMDD.csv 7449 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7463 hostStatuses-YYYYMMDD.csv 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7476 hostAddresses-YYYYMMDD.csv 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7502 contact-YYYYMMDD.csv 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7516 contactStatuses-YYYYMMDD.csv 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7537 contactPostal-YYYYMMDD.csv 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7555 contactTransfer-YYYYMMDD.csv 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7576 contactDisclose-YYYYMMDD.csv 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7608 registrar-YYYYMMDD.csv 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7622 idnLanguage-YYYYMMDD.csv 7623 7624 7625 7626 7627 7628 1.0 7629 en 7630 urn:ietf:params:xml:ns:domain-1.0 7631 7632 urn:ietf:params:xml:ns:host-1.0 7633 7634 urn:ietf:params:xml:ns:contact-1.0 7635 7636 7637 urn:ietf:params:xml:ns:secDNS-1.1 7638 7639 urn:ietf:params:xml:ns:rgp-1.0 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7666 19. References 7668 19.1. Normative References 7670 [ISO-3166-1] 7671 International Organization for Standardization, "Codes for 7672 the representation of names of countries and their 7673 subdivisions -- Part 1: Country codes", ISO Standard 3166, 7674 November 2006. 7676 [ITU-E164] 7677 International Telecommunication Union, "The international 7678 public telecommunication numbering plan", ITU-T 7679 Recommendation E.164, February 2005. 7681 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 7682 Requirement Levels", BCP 14, RFC 2119, March 1997. 7684 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 7685 Internet: Timestamps", RFC 3339, July 2002. 7687 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 7688 the Extensible Provisioning Protocol (EPP)", RFC 3915, 7689 September 2004. 7691 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 7692 STD 69, RFC 5730, August 2009. 7694 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 7695 Domain Name Mapping", STD 69, RFC 5731, August 2009. 7697 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 7698 Host Mapping", STD 69, RFC 5732, August 2009. 7700 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 7701 Contact Mapping", STD 69, RFC 5733, August 2009. 7703 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 7704 Security Extensions Mapping for the Extensible 7705 Provisioning Protocol (EPP)", RFC 5910, May 2010. 7707 19.2. Informative References 7709 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 7710 September 1981. 7712 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 7713 January 2004. 7715 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 7716 September 2004. 7718 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 7719 Architecture", RFC 4291, February 2006. 7721 [variantTLDsReport] 7722 Internet Corporation for Assigned Names and Numbers 7723 (ICANN), "A Study of Issues Related to the Management of 7724 IDN Variant TLDs", February 2012, . 7728 URIs 7730 [1] 7733 Authors' Addresses 7735 Francisco Arias 7736 Internet Corporation for Assigned Names and Numbers 7737 12025 Waterfront Drive, Suite 300 7738 Los Angeles 90292 7739 United States of America 7741 Phone: +1.310.823.9358 7742 Email: francisco.arias@icann.org 7744 Gustavo Lozano 7745 Internet Corporation for Assigned Names and Numbers 7746 12025 Waterfront Drive, Suite 300 7747 Los Angeles 90292 7748 United States of America 7750 Phone: +1.310.823.9358 7751 Email: gustavo.lozano@icann.org 7753 Shoji Noguchi 7754 Japan Registry Services Co., Ltd. 7755 Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda 7756 Chiyoda-ku, Tokyo 101-0065 7757 Japan 7759 Phone: +81.3.5215.8451 7760 Email: noguchi@jprs.co.jp 7762 James Gould 7763 VeriSign, Inc. 7764 12061 Bluemont Way 7765 Reston 20190 7766 United States of America 7768 Email: jgould@verisign.com 7769 Chethan Thippeswamy 7770 VeriSign, Inc. 7771 12061 Bluemont Way 7772 Reston 20190 7773 United States of America 7775 Email: cthippeswamy@verisign.com