idnits 2.17.1 draft-arias-noguchi-dnrd-objects-mapping-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 9 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 22, 2018) is 2159 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 8111 -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Lozano 3 Internet-Draft ICANN 4 Intended status: Standards Track J. Gould 5 Expires: November 23, 2018 C. Thippeswamy 6 VeriSign 7 May 22, 2018 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-arias-noguchi-dnrd-objects-mapping-08 12 Abstract 14 This document specifies the format, contents and semantics of Domain 15 Name Registration Data (DNRD) Escrow deposits for a Domain Name 16 Registry. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on November 23, 2018. 35 Copyright Notice 37 Copyright (c) 2018 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5 56 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 5 57 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 5 58 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 5 59 4.4. Checksum . . . . . . . . . . . . . . . . . . . . . . . . 6 60 4.5. IP addresses . . . . . . . . . . . . . . . . . . . . . . 6 61 4.6. CSV Parent Child Relationship . . . . . . . . . . . . . . 6 62 4.7. CSV elements . . . . . . . . . . . . . . . . . . . . . . 7 63 4.8. Internationalized and Localized Elements . . . . . . . . 12 64 5. Object Description . . . . . . . . . . . . . . . . . . . . . 14 65 5.1. Domain Name Object . . . . . . . . . . . . . . . . . . . 14 66 5.2. Host Object . . . . . . . . . . . . . . . . . . . . . . . 33 67 5.3. Contact Object . . . . . . . . . . . . . . . . . . . . . 43 68 5.4. Registrar Object . . . . . . . . . . . . . . . . . . . . 60 69 5.5. IDN Table Reference Object . . . . . . . . . . . . . . . 68 70 5.6. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 72 71 5.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 77 72 5.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 79 73 5.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 79 74 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 82 75 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 76 8. Data escrow agent extended verification process . . . . . . . 83 77 9. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 84 78 9.1. RDE CSV Schema . . . . . . . . . . . . . . . . . . . . . 84 79 9.2. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 94 80 9.3. CSV Domain Object . . . . . . . . . . . . . . . . . . . . 97 81 9.4. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 101 82 9.5. CSV Host Object . . . . . . . . . . . . . . . . . . . . . 104 83 9.6. RDE Contact Object . . . . . . . . . . . . . . . . . . . 107 84 9.7. CSV Contact Object . . . . . . . . . . . . . . . . . . . 110 85 9.8. RDE Registrar Object . . . . . . . . . . . . . . . . . . 116 86 9.9. CSV Registrar Object . . . . . . . . . . . . . . . . . . 120 87 9.10. RDE IDN Table Reference Objects . . . . . . . . . . . . . 124 88 9.11. CSV IDN Language Object . . . . . . . . . . . . . . . . . 126 89 9.12. EPP Parameters Object . . . . . . . . . . . . . . . . . . 128 90 9.13. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 130 91 9.14. CSV NNDN Object . . . . . . . . . . . . . . . . . . . . . 132 92 9.15. Policy Object . . . . . . . . . . . . . . . . . . . . . . 135 93 9.16. Header Object . . . . . . . . . . . . . . . . . . . . . . 136 94 10. Internationalization Considerations . . . . . . . . . . . . . 138 95 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 138 96 12. Security Considerations . . . . . . . . . . . . . . . . . . . 144 97 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 144 98 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 144 99 14.1. Changes from draft-arias-noguchi-registry-data-escrow-02 100 to -dnrd-objects-mapping-00 . . . . . . . . . . . . . . 144 101 14.2. Changes from version 00 to 01 . . . . . . . . . . . . . 145 102 14.3. Changes from version 01 to 02 . . . . . . . . . . . . . 145 103 14.4. Changes from version 02 to 03 . . . . . . . . . . . . . 146 104 14.5. Changes from version 03 to 04 . . . . . . . . . . . . . 146 105 14.6. Changes from version 04 to 05 . . . . . . . . . . . . . 147 106 14.7. Changes from version 05 to 06 . . . . . . . . . . . . . 147 107 14.8. Changes from version 06 to 07 . . . . . . . . . . . . . 148 108 14.9. Changes from version 07 to 08 . . . . . . . . . . . . . 148 109 15. Example of a full deposit using the XML model . . . . . . . . 148 110 16. Example of differential deposit using the XML model . . . . . 154 111 17. Example of a full deposit using the CSV model . . . . . . . . 155 112 18. Example of differential deposit using the CSV model . . . . . 165 113 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 175 114 19.1. Normative References . . . . . . . . . . . . . . . . . . 175 115 19.2. Informative References . . . . . . . . . . . . . . . . . 176 116 19.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 177 117 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 177 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 the deposit information (meta-data 166 and data) in an XML document. The definition of the XML format is 167 fully defined in the XML schemas. As a convention, the objects 168 represented using the XML model are referenced using RDE and an 169 XML namespace that is prefixed with "rde". For example, the 170 Domain Name object represented using the XML model can be referred 171 to as the RDE Domain Name with the XML namespace including 172 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 is 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 Parent Child Relationship 257 The CSV model represents a relational model, where the CSV files 258 represent relational tables, the fields of the CSV files represent 259 columns of the tables, and each line of the CSV file represents a 260 record. As in a relational model, the CSV files can have 261 relationships utilizing primary keys in the parent CSV file 262 definitions and foreign keys in the child CSV file definitions for a 263 1-to-many relationship. The primary keys are not explicitly defined, 264 but the foreign keys are using the boolean "parent" field attribute 265 in the child CSV file. The relationships between the CSV files are 266 used to support a cascade replace or cascade delete of records 267 starting from the parent record in differential and incremental 268 deposits. 270 The following is an example of the CSV file definitions for a Sample 271 object consisting of a parent "sample" CSV File Definition and a 272 child "sampleStatuses" CSV File Definition. The primary key for the 273 Sample object is the field that is used as the 274 foreign key in the "sampleStatuses" CSV File Definition by specifying 275 the "parent=true" attribute. If a Sample record is updated or 276 deleted in a differential or incremental deposit, it should cascade 277 replace the data using the records included in the child 278 "sampleStatuses" CSV File Definition or cascade delete the existing 279 records in the child "sampleStatuses" CSV File Definition, 280 respectively. 282 283 ... 284 285 286 287 288 289 290 291 292 293 294 295 296 297 299 sample-YYYYMMDD.csv 300 301 302 303 304 305 306 307 308 309 310 311 313 sampleStatuses-YYYYMMDD.csv 314 315 316 317 ... 318 320 4.7. CSV elements 322 4.7.1. element 324 To support a CSV model with the Registry Data Escrow Specification 325 [1], an element is defined for each object that substitutes for the 326 element and for the element, that contains 327 one or more elements. For example, the Domain Name 328 Object (Section 5.1) defines the element, that 329 substitutes for the element, and the 330 element, that substitutes for the 331 element. Both the element and the 332 elements contain one or more 333 elements. The element has the following child elements: 335 Ordered list of CSV fields used in the CSV files. 336 There is one or more child elements that substitute for the 337 abstract element. Each element defines the format 338 of the CSV field contained in the CSV files. The 339 elements support the "type" attribute that defines the XML simple 340 data type of the field element. The elements 341 support the "isRequired" attribute, with a default value of 342 "false", when set to "true" indicates that the field must be non- 343 empty in the CSV files and when set to "false" indicates that the 344 field MAY be empty in the CSV files. The "isRequired" attribute 345 MAY be specifically set for the field elements within the XML 346 schema and MAY be overridden when specifying the fields under the 347 element. The element supports an 348 OPTIONAL "parent" attribute that identifies the field as a 349 reference to a parent object, as defined in CSV Parent Child 350 Relationship (Section 4.6). For example, the field SHOULD set the 352 "parent" attribute to "true" to identify it as the parent domain 353 name of the domain status. 355 A list of one or more CSV files using the 356 child element. The child element 357 defines a reference to the CSV file name and has the following 358 optional attributes: 360 compression If the CSV file is compressed, the "compression" 361 attribute defines the compression format like "gzip" or "zip". 363 encoding Defines the encoding of the CSV file with the default 364 encoding of "UTF-8". 366 cksum Defines the checksum of the CSV file using CRC32, as 367 defined in Section 4.4. This attribute is used to validate 368 that the full CSV file exists and has not been tampered with. 370 The elements requires a "name" attribute that defines 371 the purpose of the CSV file with values like "domain", "host", 372 "contact". The supported "name" attribute values are defined for 373 each object type. The OPTIONAL "sep" attribute defines the CSV 374 separator character with the default separator character of ",". 376 The following is an example of the 377 element for domain name records where the is set 378 as required with isRequired="true". 380 381 ... 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 401 domain-YYYYMMDD.csv 402 403 404 405 ... 406 408 The following is example of the "domain-YYYYMMDD.csv" file with one 409 record matching the definition. 411 domain1.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 412 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 413 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 414 The following is an example of the 415 element for domain name records. 417 418 ... 419 420 421 422 423 424 426 domain-delete-YYYYMMDD.csv 427 428 429 430 ... 431 433 The following is example of the "domain-delete-YYYYMMDD.csv" file 434 with three records that matches the single field. 436 domain1.test 437 domain2.test 438 domainN.test 440 4.7.2. CSV common field elements 442 The element defined in the element 443 (Section 4.7.1) section has child elements that substitute for the 444 abstract element. By convention 445 elements include an 'f' prefix to identify them as field definition 446 elements. There are a set of common field elements that are used 447 across multiple data escrow objects. The common field elements are 448 defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and 449 using the "rdeCsv" sample namespace prefix. The CSV common field 450 elements include: 452 UTF-8 encoded name field with 453 type="eppcom:labelType". 455 Repository Object IDentifier (ROID) field with 456 type="eppcom:roidType" and isRequired="true". 458 Registrant contact identifier with 459 type="eppcom:clIDType". 461 The object status description, which is 462 free form text describing the rationale for the status, with 463 type="normalizedString". 465 Identifier of client (registrar) that sponsors the 466 object with type="eppcom:clIDType" and isRequired="true". 468 Identifier of the registrar, defined in Section 5.4, 469 of the client that created the object with type="eppcom:clIDType". 471 Identifier of client that created the object with 472 type="eppcom:clIDType". 474 Identifier of the registrar, defined in Section 5.4, 475 of the client that updated the object with type="eppcom:clIDType". 477 Identifier of client that updated the object with 478 type="eppcom:clIDType". 480 Identifier of the registrar, defined in Section 5.4, 481 of the client that requested the transfer with 482 type="eppcom:clIDType" and isRequired="true". 484 Identifier of client that requested the transfer with 485 type="eppcom:clIDType". 487 Identifier of the registrar, defined in Section 5.4, 488 of the client that should take or took action with 489 type="eppcom:clIDType" and isRequired="true". 491 Identifier of client that should take or took action 492 for transfer with type="eppcom:clIDType". 494 Created date of object with type="dateTime" and 495 isRequired="true". 497 Updated date of object with type="dateTime". 499 Expiration date of object with type="dateTime". 501 Date that transfer was requested with 502 type="dateTime" and isRequired="true". 504 Date that transfer action should be taken or has 505 been taken with type="dateTime" and isRequired="true". 507 Date of last transfer with type="dateTime". 509 State of the most recent transfer request with 510 type="eppcom:trStatusType" and isRequired="true". 512 General token field with type="token". 514 General language field with type="language". 516 IDN Table Identifier used for IDN domain names 517 with type="token". 519 General positive integer field with 520 type="positiveInteger". 522 Contains the URL of an object like a registrar object 523 with type="anyURI". 525 Custom field with name attribute that defines the 526 custom field name" with type="token". 528 4.8. Internationalized and Localized Elements 530 Some elements MAY be provided in either internationalized form 531 ("int") or provided in localized form ("loc"). Those elements use a 532 field value or "isLoc" attribute to specify the form used. If an 533 "isLoc" attribute is used, a value of "true" indicates the use of the 534 localized form and a value of "false" indicates the use of the 535 internationalized form. This MAY override the form specified for a 536 parent element. A value of "int" is used to indicate the 537 internationalized form and a value of "loc" is used to indicate the 538 localized form. When the internalized form ("int") is provided, the 539 field value MUST be represented in a subset of UTF-8 that can be 540 represented in the 7-bit US-ASCII character set. When the localized 541 form ("loc") is provided, the field value MAY be represented in 542 unrestricted UTF-8. 544 The field elements below of the "registrar" 545 element specify the internationalized form with the 546 isLoc="false" attribute. 548 ... 549 550 ... 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 582 registrar-YYYYMMDD.csv 583 584 585 586 ... 587 588 ... 590 The following is an example of using the 591 field value to define the internationalized or localized form of the 592 remainder of the "contactPostal" field values. 594 ... 595 596 ... 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 614 contactPostal-YYYYMMDD.csv 615 616 617 618 ... 619 620 ... 622 5. Object Description 624 This section describes the base objects supported by this 625 specification: 627 5.1. Domain Name Object 629 The domain name object is based on the EPP domain name mapping 630 specified in [RFC5731]. The domain name object supports both the XML 631 Model and the CSV Model, defined in the Models (Section 2) section. 632 The elements used for both models are defined in the following 633 sections. 635 5.1.1. XML Model 637 There are two elements used in the data escrow of the domain name 638 objects for the XML model including the , under the 639 element, and the element, under the 640 element. 642 5.1.1.1. object 644 The domain element is based on the EPP domain response for an 645 authorized client (see Section 3.1.2. of [RFC5731]) with additional 646 data from an EPP Query Response, see Section 3.1.3. of 647 [RFC5731], RGP status from [RFC3915], and data from the EPP 648 command, see Section 5.2.1. of [RFC5910]. 650 A element substitutes for the abstract 651 element to define a concrete definition of a domain. The 652 element can be replaced by other domain definitions 653 using the XML schema substitution groups feature. 655 The element contains the following child elements: 657 o A element that contains the fully qualified name of the 658 domain name object. If the domain name is an IDN, the ASCII 659 Compatible Encoding (ACE) MUST be used. 661 o A element that contains the repository object identifier 662 assigned to the domain name object when it was created. 664 o An OPTIONAL element that contains the fully qualified name 665 of the domain name in Unicode character set. It MUST be provided 666 if available. 668 o An OPTIONAL element that references the IDN 669 Table used for the IDN. This corresponds to the "id" attribute of 670 the element. This element MUST be present if the 671 domain name is an IDN. 673 o An OPTIONAL element is used to indicate that the 674 domain name is an IDN variant. This element contains the domain 675 name used to generate the IDN variant. 677 o One or more elements that contain the current status 678 descriptors associated with the domain name. 680 o Zero or more OPTIONAL element to represent 681 "pendingDelete" sub-statuses, including "redemptionPeriod", 682 "pendingRestore", and "pendingDelete", that a domain name can be 683 in as a result of grace period processing as specified in 684 [RFC3915]. 686 o An OPTIONAL element that contain the identifier for 687 the human or organizational social information object associated 688 as the holder of the domain name object. 690 o Zero or more OPTIONAL elements that contain identifiers 691 for the human or organizational social information objects 692 associated with the domain name object. 694 o An OPTIONAL element that contains the fully qualified names 695 of the delegated host objects or host attributes (name servers) 696 associated with the domain name object. See Section 1.1 of 697 [RFC5731] for a description of the elements used to specify host 698 objects or host attributes. 700 o A element that contains the identifier of the sponsoring 701 registrar. 703 o An OPTIONAL element that contains the identifier of the 704 registrar that created the domain name object. An OPTIONAL client 705 attribute is used to specify the client that performed the 706 operation. 708 o An OPTIONAL element that contains the date and time of 709 the domain name object creation. This element MUST be present if 710 the domain name has been allocated. 712 o An OPTIONAL element that contains the date and time 713 identifying the end (expiration) of the domain name object's 714 registration period. This element MUST be present if the domain 715 name has been allocated. 717 o An OPTIONAL element that contains the identifier of the 718 registrar that last updated the domain name object. This element 719 MUST NOT be present if the domain has never been modified. An 720 OPTIONAL client attribute is used to specify the client that 721 performed the operation. 723 o An OPTIONAL element that contains the date and time of 724 the most recent domain-name-object modification. This element 725 MUST NOT be present if the domain name object has never been 726 modified. 728 o An OPTIONAL element that contains the public key 729 information associated with Domain Name System security (DNSSEC) 730 extensions for the domain name as specified in [RFC5910]. 732 o An OPTIONAL element that contains the date and time of 733 the most recent domain object successful transfer. This element 734 MUST NOT be present if the domain name object has never been 735 transferred. 737 o An OPTIONAL element that contains the following child 738 elements related to the last transfer request of the domain name 739 object. This element MUST NOT be present if a transfer request 740 for the domain name has never been created. 742 * A element that contains the state of the most recent 743 transfer request. 745 * A element that contains the identifier of the registrar 746 that requested the domain name object transfer. An OPTIONAL 747 client attribute is used to specify the client that performed 748 the operation. 750 * A element that contains the date and time that the 751 transfer was requested. 753 * An element that contains the identifier of the registrar 754 that SHOULD act upon a PENDING transfer request. For all other 755 status types, the value identifies the registrar that took the 756 indicated action. An OPTIONAL client attribute is used to 757 specify the client that performed the operation. 759 * An element that contains the date and time of a 760 required or completed response. For a PENDING request, the 761 value identifies the date and time by which a response is 762 required before an automated response action will be taken by 763 the registry. For all other status types, the value identifies 764 the date and time when the request was completed. 766 * An OPTIONAL element that contains the end of the 767 domain name object's validity period (expiry date) if the 768 transfer caused or causes a change in the validity period. 770 Example of a domain object: 772 ... 773 774 example1.test 775 Dexample1-TEST 776 777 jd1234 778 sh8013 779 sh8013 780 781 ns1.example.com 782 ns1.example1.test 783 784 RegistrarX 785 RegistrarX 786 1999-04-03T22:00:00.0Z 787 2015-04-03T22:00:00.0Z 788 789 ... 791 5.1.1.2. object 793 The element contains the fully qualified domain 794 name that was deleted and purged. 796 Example of object: 798 ... 799 800 ... 801 802 foo.test 803 bar.test 804 805 ... 806 807 ... 809 5.1.2. CSV Model 811 For the CSV Model of the domain name object, the 812 child element of the element is used to hold the new 813 or updated domain name objects for the deposit. The 814 child element of the element is 815 used to hold the deleted or purged domain name objects for the 816 deposit. Both the and 817 elements contain one or more elements with a set of 818 named CSV file definitions using the "name" attribute. 820 Differential and incremental deposits are based on changes to the 821 domain name objects. The updated domain name object data under the 822 element is a cascade replace down all of the 823 domain name CSV files starting with the parent "domain" CSV File 824 Definition (Section 5.1.2.1.1). The child CSV file definitions 825 include a field. All the child CSV 826 file definition data for the domain name objects in the parent 827 "domain" CSV File Definition (Section 5.1.2.1.1) MUST first be 828 deleted and then set using the data in the child CSV files. The 829 deleted domain name object data under the element 830 is a cascade delete starting from the "domain" Deletes CSV File 831 Definition (Section 5.1.2.2.1). 833 5.1.2.1. 835 The is used to hold the new or updated domain 836 name object information for the deposit. The is 837 split into separate CSV file definitions using named 838 elements with the "name" attribute. The following sections include 839 the supported domain name CSV file definitions: 841 5.1.2.1.1. "domain" CSV File Definition 843 The "domain" CSV File Definition defines the fields and CSV file 844 references used for the parent domain name object records. All the 845 other domain name CSV file definitions are child CSV files based on 846 the inclusion of the field. 848 The following "csvDomain" field elements MUST be used in the "domain" 849 element: 851 Domain name field with type="eppcom:labelType" and 852 isRequired="true". 854 The following "csvDomain" field elements MAY be used in the "domain" 855 element: 857 Fully qualified name of the original IDN 858 domain name object related to the variant domain name object with 859 type="eppcom:labelType". 861 The following "rdeCsv" fields, defined in section CSV common field 862 elements (Section 4.7.2), MUST be used in the "domain" 863 element: 865 Registry Object IDentifier (ROID) for the domain name 866 object with isRequired="true". 868 Identifier of client that sponsors the domain name 869 object with isRequired="true". 871 Created date and time of the domain name object 872 with isRequired="true". 874 Identifier of the registrar, defined in Section 5.4, 875 of the client that updated the object. 877 Date and time of the last update to the domain name 878 object. 880 Expiration date and time for the domain name 881 object. The attribute isRequired MUST equal "true". 883 The following "rdeCsv" fields, defined in section CSV common field 884 elements (Section 4.7.2), MAY be used in the "domain" 885 element: 887 Identifier of the registrar, defined in Section 5.4, 888 of the client that created the object. 890 UTF8 encoded domain name for the 891 field element. 893 IDN Table Identifier used for the IDN domain 894 name object that MUST match a field element 895 in the "idnLanguage" CSV files, as defined in Section 5.5.2. 897 Registrant contact identifier for the domain 898 name object. 900 Identifier of client that created the domain name 901 object. 903 Identifier of the client that last updated the domain 904 name object. 906 Date and time of the last transfer for the domain 907 name object. 909 Example of a "domain" element. 911 ... 912 913 ... 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 933 domain-YYYYMMDD.csv 934 935 936 937 ... 938 939 ... 941 Example of the corresponding domain-YYYYMMDD.csv file. The file 942 contains four records (two active ASCII domains, original IDN with 943 LANG-1 language rules, and variant IDN with LANG-1 language rules). 945 domain1.test,Ddomain1-TEST,,,registrantid,registrarX,registrarX, 946 clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 947 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 948 domain2.test,Ddomain2-TEST,,,registrantid,registrarX,registrarX, 949 clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 950 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 951 xn--abc123.test,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, 952 registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 953 2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 954 xn--abc321.test,Dxnabc321-TEST,LANG-1,xn--abc123.test, 955 registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, 956 registrarX,clientY,2009-12-03T09:05:00.0Z,2015-04-03T22:00:00.0Z 958 5.1.2.1.2. "domainContacts" CSV File Definition 960 The "domainContacts" CSV File Definition defines the fields and CSV 961 file references used for the domain name object link records to 962 contact objects, as described in Contact Object (Section 5.3). 964 The following "csvDomain" field elements MUST be used in the 965 "domainContacts" element: 967 The contact type for the contact object 968 link with type="domain:contactAttrType" and isRequired="true". 969 The supported contact type values include "admin" for the 970 administration contact, "billing" for the billing contact, and 971 "tech" for the technical contact. 973 The following "csvDomain" field elements, defined for the "domain" 974 CSV File Definition (Section 5.1.2.1.1), MUST be used in the 975 "domainContacts" element: 977 The name of the domain object that is linked to 978 the contact object with isRequired="true". 980 The following "csvContact" fields, defined for the "contact" CSV File 981 Definition (Section 5.3.2.1.1), MUST be used in the "domainContacts" 982 element: 984 The server-unique contact identifier with 985 isRequired="true". 987 Example of a "domainContacts" 988 element. 990 ... 991 992 ... 993 994 995 996 997 998 999 1000 1002 domainContacts-YYYYMMDD.csv 1003 1004 1005 1006 ... 1007 1008 ... 1010 Example of the corresponding domainContacts-YYYYMMDD.csv file. The 1011 file contains an admin, tech, and billing contact for the four domain 1012 names domain1.test, domain2.test, xn--abc123.test and xn-- 1013 abc321.test. 1015 domain1.test,domain1admin,admin 1016 domain1.test,domain1tech,tech 1017 domain1.test,domain1billing,billing 1018 domain2.test,domain2admin,admin 1019 domain2.test,domain2tech,tech 1020 domain2.test,domain2billing,billing 1021 xn--abc123.test,xnabc123admin,admin 1022 xn--abc123.test,xnabc123tech,tech 1023 xn--abc123.test,xnabc123billing,billing 1024 xn--abc321.test,xnabc123admin,admin 1025 xn--abc321.test,xnabc123tech,tech 1026 xn--abc321.test,xnabc123billing,billing 1028 5.1.2.1.3. "domainStatuses" CSV File Definition 1030 The "domainStatuses" CSV File Definition defines the fields and CSV 1031 file references used for the domain name object statuses. 1033 The following "csvDomain" field elements MUST be used in the 1034 "domainStatuses" element: 1036 The status of the domain name with 1037 type="domain:statusValueType" and isRequired="true". 1039 The Registry Grace Period (RGP) status, as a 1040 sub-status of the "pendingDelete" status 1041 value, with type="rgp:statusValueType" as defined in [RFC3915]. 1043 The following "csvDomain" fields, defined for the "domain" CSV File 1044 Definition (Section 5.1.2.1.1), MUST be used in the "domainStatuses" 1045 element: 1047 Domain name of status with isRequired="true". 1049 The following "rdeCsv" fields, defined in section CSV common field 1050 elements (Section 4.7.2), MAY be used in the "domainStatuses" 1051 element: 1053 Domain object status description which 1054 is free form text describing the rationale for the status. 1056 Language of the field. 1058 Example of a "domainStatuses" 1059 element. 1061 ... 1062 1063 ... 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1075 domainStatuses-YYYYMMDD.csv 1076 1077 1078 1079 ... 1080 1081 ... 1083 Example of the corresponding domainStatuses-YYYYMMDD.csv file. The 1084 file contains the statuses for the four domain names domain1.test, 1085 domain2.test, xn--abc123.test and xn--abc321.test. 1087 domain1.test,clientUpdateProhibited,"Disallow update", 1088 en, 1089 domain1.test,clientDeleteProhibited,"Disallow delete", 1090 en, 1091 domain2.test,ok,,, 1092 xn--abc123.test,ok,,, 1093 xn--abc321.test,ok,,, 1095 5.1.2.1.4. "domainNameServers" CSV File Definition 1097 The "domainNameServers" CSV File Definition defines the fields and 1098 CSV file references used for the domain name delegated hosts (name 1099 servers). The "domainNameServers" CSV files define the relationship 1100 between a domain name object and a delegated host. The 1101 "domainNameServers" CSV File is used to support the 1102 model, defined in [RFC5731]. 1104 The following "csvDomain" fields, defined for the "domain" CSV File 1105 Definition (Section 5.1.2.1.1), MUST be used in the 1106 "domainNameServers" element: 1108 Domain name using the delegated host with host 1109 and isRequired="true". 1111 The following "rdeCsv" fields, defined in section CSV common field 1112 elements (Section 4.7.2), MUST be used in the "domainNameServers" 1113 element: 1115 Registry Object IDentifier (ROID) used to uniquely 1116 reference a delegated host record with isRequired="true". 1118 Example of a "domainNameServers" 1119 element. 1121 ... 1122 1123 ... 1124 1125 1126 1127 1128 1129 1130 1132 domainNameServers-YYYYMMDD.csv 1133 1134 1135 1136 ... 1137 1138 ... 1140 Example of the corresponding domainNameServers-YYYYMMDD.csv file. 1141 The file contains the delegated hosts (name servers) for the four 1142 domain names domain1.test, domain2.test, xn--abc123.test and xn-- 1143 abc321.test referenced via the field element. 1145 domain1.test,Hns1_domain1_test-TEST 1146 domain1.test,Hns2_domain1_test-TEST 1147 domain2.test,Hns1_domain2_test-TEST 1148 domain2.test,Hns2_domain2_test-TEST 1149 xn--abc123.test,Hns1_example_test-TEST 1150 xn--abc123.test,Hns2_example_test-TEST 1151 xn--abc321.test,Hns1_example_test-TEST 1152 xn--abc321.test,Hns2_example_test-TEST 1154 5.1.2.1.5. "domainNameServersAddresses" CSV File Definition 1156 The "domainNameServersAddresses" CSV File Definition defines the 1157 fields and CSV file references used for supporting the host as domain 1158 attributes model. 1160 The following "csvDomain" fields, defined for the "domain" CSV File 1161 Definition (Section 5.1.2.1.1), MUST be used in the 1162 "domainNameServersAddresses" element: 1164 Domain name using the delegated host with host 1165 and isRequired="true". 1167 The following "rdeCsv" fields, defined in section Host CSV model 1168 elements (Section 5.2.2), MUST be used in the 1169 "domainNameServersAddresses" element: 1171 Host name field with type="eppcom:labelType" and 1172 isRequired="true". 1174 The following "csvHost" fields, defined in section Host CSV model 1175 elements (Section 5.2.2), MAY be used in the 1176 "domainNameServersAddresses" element: 1178 IP addresses associated with the host object with 1179 type="host:addrStringType". 1181 IP addresses version associated with the host 1182 object with type="host:ipType". "host:ipType" has the enumerated 1183 values of "v4" or "v6". 1185 Example of a "domainNameServersAddresses" 1186 element. 1188 ... 1189 1190 ... 1191 1192 1193 1194 1195 1196 1197 1198 1199 1201 domainNameServersAddresses-YYYYMMDD.csv 1202 1203 1204 1205 ... 1206 1207 ... 1209 Example of the corresponding domainNameServersAddresses-YYYYMMDD.csv 1210 file. The file contains the delegated hosts (name servers) for the 1211 four domain names domain1.test, domain2.test, xn--abc123.test and 1212 xn--abc321.test. 1214 domain1.test,ns1.domain1.test,192.0.2.1,v4 1215 domain1.test,ns2.domain1.test,2001:DB8::1,v6 1216 domain2.test,ns1.domain2.test2,192.0.2.2,v4 1217 domain2.test,ns2.domain2.test2,2001:DB8::2,v6 1218 xn--abc123.test,ns1.example.example,, 1219 xn--abc123.test,ns2.example.example,, 1220 xn--abc321.test,ns1.example.example,, 1221 xn--abc321.test,ns2.example.example,, 1223 5.1.2.1.6. "dnssec" CSV File Definition 1225 The "dnssec" CSV File Definition defines the fields and CSV file 1226 references used for the domain name object DNSSEC records (DS or Key 1227 Data). 1229 The following "csvDomain" field elements MUST be used in the "dnssec" 1230 rdeCsv:fields> element when the DS Data Interface per 1231 [RFC5910] is used: 1233 Contains the DS key tag value per [RFC5910] with 1234 type="unsignedShort" and isRequired="true". 1236 Contains the DS algorithm value per [RFC5910] 1237 with type="unsignedByte" and isRequired="true". 1239 Contains the DS digest type value per 1240 [RFC5910] with type="unsignedByte" and isRequired="true". 1242 Contains the DS digest value per [RFC5910] with 1243 type="hexBinary" and isRequired="true". 1245 The following "csvDomain" field elements MUST be used in the "dnssec" 1246 rdeCsv:fields> element when the Key Data Interface per 1247 [RFC5910] is used: 1249 Contains the flags field value per [RFC5910] with 1250 type="unsignedShort" and isRequired="true". 1252 Contains the Key protocol value per [RFC5910] 1253 with type="unsignedByte" and isRequired="true". 1255 Contains the Key algorithm value per [RFC5910] 1256 with type="unsignedByte" and isRequired="true". 1258 Contains the public key value per [RFC5910] with 1259 type="secDNS:keyType" and isRequired="true". 1261 The following "csvDomain" field elements MAY be used in the "dnssec" 1262 rdeCsv:fields> element: 1264 Indicates a child's preference for the 1265 number of seconds after signature generation when the parent's 1266 signature on the DS information provided by the child will expire 1267 with type="secDNS:maxSigLifeType" defined in [RFC5910]. 1269 The following "domain" fields, defined for the "domain" CSV File 1270 Definition (Section 5.1.2.1.1), MUST be used in the "dnssec" 1271 element: 1273 Domain name of the domain object associated with 1274 the DNSSEC record and isRequired="true". 1276 Example of a "dnssec" element with 1277 the DS Data Interface of [RFC5910]: 1279 1280 ... 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1293 dnssec-ds-YYYYMMDD.csv 1294 1295 1296 1297 ... 1298 1299 ... 1301 Example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file 1302 contains two DS records for domain1.test. 1304 domain1.test,604800,12345,3,1,49FD46E6C4B45C55D4AC 1305 domain1.test,604800,12346,3,1,38EC35D5B3A34B44C39B 1306 Example of a "dnssec" element with 1307 the Key Data Interface of [RFC5910]: 1309 1310 ... 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1323 dnssec-key-YYYYMMDD.csv 1324 1325 1326 1327 ... 1328 1329 ... 1331 Example of the corresponding dnssec-key-YYYYMMDD.csv file. The file 1332 contains two key records for domain1.test. 1334 domain1.test,604800,257,3,1,AQPJ////4Q== 1335 domain1.test,604800,257,3,1,AQPJ////4QQQ 1337 5.1.2.1.7. "domainTransfer" CSV File Definition 1339 The "domainTransfer" CSV File Definition defines the fields and CSV 1340 file references used for the domain name object pending and completed 1341 transfer records. No additional field elements were added for use in 1342 the "domainTransfer" element. 1344 The following "rdeCsv" fields, defined in section CSV common field 1345 elements (Section 4.7.2), MUST be used in the "domainTransfer" 1346 element: 1348 State of the most recent transfer request with 1349 isRequired="true". 1351 Identifier of the registrar, defined in Section 5.4, 1352 of the client that requested the transfer with isRequired="true". 1354 Date and time that the transfer was requested with 1355 isRequired="true". 1357 Identifier of the registrar, defined in Section 5.4, 1358 of the client that should take or took action with 1359 isRequired="true". 1361 Date and time that the transfer action should be 1362 taken or has been taken with isRequired="true". 1364 The following "rdeCsv" fields, defined in section CSV common field 1365 elements (Section 4.7.2), MAY be used in the "domainTransfer" 1366 element: 1368 Expiration date if the transfer command caused or 1369 causes a change in the validity period. 1371 Identifier of client that requested the transfer. 1373 Identifier of client that should take or took action 1374 for transfer. 1376 The following "csvDomain" fields, defined for the "domain" CSV File 1377 Definition (Section 5.1.2.1.1), MUST be used in the "domainTransfer" 1378 element: 1380 Domain name of the domain object involved in the 1381 transfer with isRequired="true". 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. The 1413 file contains one domain transfer record with a pending status. 1415 domain1.test,pending,registrarX,clientY, 1416 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 1417 2016-04-03T22:00:00.0Z 1419 5.1.2.2. 1421 The is used to hold the deleted domain name 1422 objects in a differential or incremental deposit. All the domain 1423 name object data is deleted as part of a cascade delete. The 1424 is split into separate CSV file definitions using 1425 named elements with the "name" attribute. The following 1426 section defines the supported domain name deletes CSV file 1427 definition. 1429 5.1.2.2.1. "domain" Deletes CSV File Definition 1431 The following "csvDomain" field elements MUST be used in the deletes 1432 "domain" element: 1434 Domain name field with type="eppcom:labelType" and 1435 isRequired="true". 1437 Example of a "domain" element: 1439 ... 1440 1441 ... 1442 1443 1444 1445 1446 1447 1449 domain-delete-YYYYMMDD.csv 1450 1451 1452 1453 ... 1454 1455 ... 1457 Example of the corresponding domain-delete-YYYYMMDD.csv file. The 1458 file contains two domain name records. 1460 domain1.test 1461 domain2.test 1463 5.2. Host Object 1465 The host object is based on the EPP host name mapping in [RFC5732]. 1466 The host object supports both the XML Model and the CSV Model, 1467 defined in Models (Section 2) section. The elements used for both 1468 models are defined in the following sections. Both the 1469 and elements contain one or more 1470 elements with a set of named CSV file definitions using 1471 the "name" attribute. 1473 5.2.1. XML Model 1475 There are two elements used in the data escrow of the host objects 1476 for the XML model including the , under the 1477 element, and the element, under 1478 the element. 1480 A element substitutes for the 1481 abstract element to define a concrete definition of a host. The 1482 element can be replaced by other host 1483 definitions using the XML schema substitution groups feature. 1485 5.2.1.1. element 1487 The RDE host object is based on the EPP host response for an 1488 authorized client (Section 3.1.2. of [RFC5732]). 1490 The OPTIONAL element contains the following child elements: 1492 o A element that contains the fully qualified name of the 1493 host object. 1495 o A element that contains the repository object identifier 1496 assigned to the host object when the object was created. 1498 o One or more elements that describe the status of the host 1499 object. 1501 o Zero or more elements that contain the IP addresses 1502 associated with the host object. 1504 o A element that contains the identifier of the sponsoring 1505 registrar. 1507 o A element that contains the identifier of the registrar 1508 that created the host object. An OPTIONAL client attribute is 1509 used to specify the client that performed the operation. 1511 o A element that contains the date and time of host-object 1512 creation. 1514 o An OPTIONAL element that contains the identifier of the 1515 registrar that last updated the host object. This element MUST 1516 NOT be present if the host object has never been modified. An 1517 OPTIONAL client attribute is used to specify the client that 1518 performed the operation. 1520 o An OPTIONAL element that contains the date and time of 1521 the most recent host-object modification. This element MUST NOT 1522 be present if the host object has never been modified. 1524 o An OPTIONAL element that contains the date and time of 1525 the most recent host object successful transfer. This element 1526 MUST NOT be present if the domain name object has never been 1527 transfered. 1529 Example of object: 1531 ... 1532 1533 ns1.example1.test 1534 Hns1_example_test-TEST 1535 1536 1537 192.0.2.2 1538 192.0.2.29 1539 1080:0:0:0:8:800:200C:417A 1540 RegistrarX 1541 RegistrarX 1542 1999-05-08T12:10:00.0Z 1543 RegistrarX 1544 2009-10-03T09:34:00.0Z 1545 1546 ... 1548 5.2.1.2. object 1550 The element contains the fully qualified domain name 1551 of a host that was deleted. The element also 1552 supports host removal based on roid to support SRS systems in which 1553 different hosts with the same fully qualified domain name are active 1554 at the same time. 1556 Example of object: 1558 ... 1559 1560 ... 1561 1562 ns1.example.test 1563 1564 ... 1565 1566 ... 1568 5.2.2. CSV Model 1570 For the CSV Model of the host object, the child 1571 element of the element is used to hold the new or 1572 updated host objects for the deposit. The child 1573 element of the element is used to hold the deleted or 1574 purged host objects for the deposit. 1576 Differential and incremental deposits are based on changes to the 1577 host objects. The updated host object data under the 1578 element is a cascade replace down all of the host 1579 CSV files starting with the parent "host" CSV File Definition 1580 (Section 5.2.2.1.1). The child CSV file definitions include a 1581 field. All the child CSV file 1582 definition data for the host objects in the parent "host" CSV File 1583 Definition (Section 5.2.2.1.1) MUST first be deleted and then set 1584 using the data in the child CSV files. The deleted host object data 1585 under the element is a cascade delete starting from 1586 the "host" Deletes CSV File Definition (Section 5.2.2.2.1). 1588 5.2.2.1. 1590 The is used to hold the new or updated host object 1591 information for the deposit. The is split into 1592 separate CSV file definitions using named elements with 1593 the "name" attribute. The following sections include the supported 1594 host CSV file definitions. 1596 5.2.2.1.1. "host" CSV File Definition 1598 The "host" CSV File Definition defines the fields and CSV file 1599 references used for the host object records. 1601 The following "csvHost" field elements MUST be used in the "host" 1602 element: 1604 Host name field with type="eppcom:labelType" and 1605 isRequired="true". 1607 The following "rdeCsv" fields, defined in section CSV common field 1608 elements (Section 4.7.2), MUST be used in the "host" 1609 element: 1611 Repository Object IDentifier (ROID) assigned to the 1612 host object with isRequired="true". 1614 The following "rdeCsv" fields, defined in section CSV common field 1615 elements (Section 4.7.2), MAY be used in the "host" 1616 element: 1618 Identifier of the sponsoring client with 1619 isRequired="true". 1621 Identifier of the registrar, defined in Section 5.4, 1622 of the client that created the object with isRequired="true". 1624 Identifier of client that created the host object. 1626 Date and time that the host object was created with 1627 isRequired="true". 1629 Identifier of the registrar, defined in Section 5.4, 1630 of the client that updated the object. 1632 Identifier of client that last updated the host 1633 object. 1635 Date and time that the host object was last 1636 updated. 1638 Date and time that the host was last transferred. 1640 Example of a "host" element. 1642 ... 1643 1644 ... 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1661 host-YYYYMMDD.csv 1662 1663 1664 1665 ... 1666 1667 ... 1669 Example of the corresponding host-YYYYMMDD.csv file. The file 1670 contains six host records with four being internal hosts and two 1671 being external hosts. 1673 ns1.domain1.test,Hns1_example_test-TEST,registrarX,registrarX, 1674 clientY,1999-05-08T12:10:00.0Z,registrarX, 1675 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1676 ns2.domain1.test,Hns2_domain1_test-TEST,registrarX,registrarX, 1677 clientY,1999-05-08T12:10:00.0Z,registrarX, 1678 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1679 ns1.domain2.test,Hns1_domain2_test-TEST,registrarX,registrarX, 1680 clientY,1999-05-08T12:10:00.0Z,registrarX, 1681 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1682 ns2.domain2.test,Hns2_domain2_test-TEST,registrarX,registrarX, 1683 clientY,1999-05-08T12:10:00.0Z,registrarX, 1684 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1685 ns1.example.example,Hns1_example_test-TEST,registrarX,registrarX, 1686 clientY,1999-05-08T12:10:00.0Z,registrarX, 1687 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1688 ns2.example.example,Hns2_example_test-TEST,registrarX,registrarX, 1689 clientY,1999-05-08T12:10:00.0Z,registrarX, 1690 clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z 1692 5.2.2.1.2. "hostStatuses" CSV File Definition 1694 The "hostStatuses" CSV File Definition defines the fields and CSV 1695 file references used for the host object statuses. 1697 The following "csvHost" fields, defined for the "host" CSV File 1698 Definition (Section 5.2.2.1.1), MUST be used in the "hostStatuses" 1699 element: 1701 The status of the host with 1702 type="host:statusValueType" and isRequired="true"./>. 1704 The following "rdeCsv" fields, defined in section CSV common field 1705 elements (Section 4.7.2), MUST be used in the "hostStatuses" 1706 element: 1708 Host object Registry Object IDentifier (ROID) 1709 assigned to the host object with isRequired="true". 1711 The following "rdeCsv" fields, defined in section CSV common field 1712 elements (Section 4.7.2), MAY be used in the "hostStatuses" 1713 element: 1715 Host object status description which is 1716 free form text describing the rationale for the status. The 1717 attribute isRequired MUST equal "true". 1719 Language of the field. 1721 Example of a "hostStatuses" element. 1723 ... 1724 1725 ... 1726 1727 1728 1729 1730 1731 1732 1733 1734 1736 hostStatuses-YYYYMMDD.csv 1737 1738 1739 1740 ... 1741 1742 ... 1744 Example of the corresponding hostStatuses-YYYYMMDD.csv file. The 1745 file contains the statuses for the six host names ns1.domain1.test, 1746 ns2.domain1.test, ns1.domain2.test, ns2.domain2.test, 1747 ns1.example.example and ns2.example.example. 1749 Hns1_domain1_test-TEST,ok,, 1750 Hns2_domain1_test-TEST,ok,, 1751 Hns1_domain2_test-TEST,ok,, 1752 Hns2_domain2_test-TEST,ok,, 1753 Hns1_example_test-TEST,ok,, 1754 Hns2_example_test-TEST,ok,, 1756 5.2.2.1.3. "hostAddresses" CSV File Definition 1758 The "hostAddresses" CSV File Definition defines the fields and CSV 1759 file references used for the host object IP addresses. 1761 The following "csvHost" field elements MUST be used in the 1762 "hostAddresses" element: 1764 IP addresses associated with the host object with 1765 type="host:addrStringType". The attribute isRequired MUST equal 1766 "true". 1768 IP addresses version associated with the host 1769 object with type="host:ipType". "host:ipType" has the enumerated 1770 values of "v4" or "v6". The attribute isRequired MUST equal 1771 "true". 1773 The following "rdeCsv" fields, defined in section CSV common field 1774 elements (Section 4.7.2), MUST be used in the "hostAddresses" 1775 element: 1777 Host object Registry Object IDentifier (ROID) 1778 assigned to the host object. 1780 Example of a "hostAddresses" element. 1782 ... 1783 1784 ... 1785 1786 1787 1788 1789 1790 1791 1792 1794 hostAddresses-YYYYMMDD.csv 1795 1796 1797 1798 ... 1799 1800 ... 1802 Example of the corresponding hostAddressesObj-YYYYMMDD.csv file. The 1803 file contains the IP addresses for the host names ns1.domain1.test, 1804 ns2.domain1.test, ns1.domain2.test and ns2.domain2.test. 1806 Hns1_domain1_test-TEST,192.0.2.1,v4 1807 Hns2_domain1_test-TEST,2001:DB8::1,v6 1808 Hns1_domain2_test-TEST,192.0.2.2,v4 1809 Hns2_domain2_test-TEST,2001:DB8::2,v6 1811 5.2.2.2. 1813 The is used to hold the deleted host objects in a 1814 differential or incremental deposit. All the host object data is 1815 deleted as part of a cascade delete. The is split 1816 into separate CSV file definitions using named elements 1817 with the "name" attribute. The following section defines the 1818 supported host deletes CSV file definition. 1820 5.2.2.2.1. "host" Deletes CSV File Definition 1822 The following "rdeCsv" fields, defined in section CSV common field 1823 elements (Section 4.7.2), MUST be used in the "host" 1824 element: 1826 Repository Object IDentifier (ROID) assigned to the 1827 host object with isRequired="true". 1829 Example of a "host" element. 1831 ... 1832 1833 ... 1834 1835 1836 1837 1838 1839 1841 host-delete-YYYYMMDD.csv 1842 1843 1844 1845 ... 1846 1847 ... 1849 Example of the host-delete-YYYYMMDD.csv file. The file contains four 1850 host records. 1852 Hns1_domain1_test-TEST 1853 Hns2_domain1_test-TEST 1854 Hns1_domain2_test-TEST 1855 Hns2_domain2_test-TEST 1857 5.3. Contact Object 1859 The contact object is based on the EPP contact name mapping in 1860 [RFC5733]. The contact object supports both the XML Model and the 1861 CSV Model, defined in Models (Section 2) section. The elements used 1862 for both models are defined in the following sections. 1864 5.3.1. XML Model 1866 There are two elements used in the data escrow of the contact objects 1867 for the XML model including the , under the 1868 element, and the element, 1869 under the element. 1871 A element substitutes for the abstract 1872 element to define a concrete definition of a contact. The 1873 element can be replaced by other contact 1874 definitions using the XML schema substitution groups feature. 1876 5.3.1.1. object 1878 The contact object is based on the EPP contact response for an 1879 authorized client (Section 3.1.2. of [RFC5733]) with some additions 1880 including the data from an EPP Query Response, see 1881 Section 3.1.3. of [RFC5733]. 1883 The OPTIONAL element contains the following child elements: 1885 o A element that contains the server-unique identifier of the 1886 contact object 1888 o A element that contains the Repository Object IDentifier 1889 assigned to the contact object when the object was created. 1891 o One or more elements that describe the status of the 1892 contact object. 1894 o One or two elements that contain postal-address 1895 information. Two elements are provided so that address 1896 information can be provided in both internationalized and 1897 localized forms; a "type" attribute is used to identify the two 1898 forms. If an internationalized form (type="int") is provided, 1899 element content MUST be represented in a subset of UTF-8 that can 1900 be represented in the 7-bit US-ASCII character set. If a 1901 localized form (type="loc") is provided, element content MAY be 1902 represented in unrestricted UTF-8. The element 1903 contains the following child elements: 1905 * A element that contains the name of the individual or 1906 role represented by the contact. 1908 * An OPTIONAL element that contains the name of the 1909 organization with which the contact is affiliated. 1911 * An element that contains address information associated 1912 with the contact. An element contains the following 1913 child elements: 1915 + One, two, or three OPTIONAL elements that contain 1916 the contact's street address. 1918 + A element that contains the contact's city. 1920 + An OPTIONAL element that contains the contact's state 1921 or province. 1923 + An OPTIONAL element that contains the contact's postal 1924 code. 1926 + A element that contains the contact's two-letter 1927 country code. 1929 o An OPTIONAL element that contains the contact's voice 1930 telephone number. 1932 o An OPTIONAL element that contains the contact's facsimile 1933 telephone number. 1935 o An element that contains the contact's email address. 1937 o A element that contains the identifier of the sponsoring 1938 registrar. 1940 o A element that contains the identifier of the registrar 1941 that created the contact object. An OPTIONAL client attribute is 1942 used to specify the client that performed the operation. 1944 o A element that contains the date and time of contact- 1945 object creation. 1947 o An OPTIONAL element that contains the identifier of the 1948 registrar that last updated the contact object. This element MUST 1949 NOT be present if the contact has never been modified. An 1950 OPTIONAL client attribute is used to specify the client that 1951 performed the operation. 1953 o An OPTIONAL element that contains the date and time of 1954 the most recent contact-object modification. This element MUST 1955 NOT be present if the contact object has never been modified. 1957 o An OPTIONAL element that contains the date and time of 1958 the most recent contact object successful transfer. This element 1959 MUST NOT be present if the contact object has never been 1960 transferred. 1962 o An OPTIONAL element that contains the following child 1963 elements related to the last transfer request of the contact 1964 object: 1966 * A element that contains the state of the most recent 1967 transfer request. 1969 * A element that contains the identifier of the registrar 1970 that requested the domain name object transfer. An OPTIONAL 1971 client attribute is used to specify the client that performed 1972 the operation. 1974 * An element that contains the identifier of the registrar 1975 that SHOULD act upon a PENDING transfer request. For all other 1976 status types, the value identifies the registrar that took the 1977 indicated action. An OPTIONAL client attribute is used to 1978 specify the client that performed the operation. 1980 * A element that contains the date and time that the 1981 transfer was requested. 1983 * An element that contains the date and time of a 1984 required or completed response. For a PENDING request, the 1985 value identifies the date and time by which a response is 1986 required before an automated response action will be taken by 1987 the registry. For all other status types, the value identifies 1988 the date and time when the request was completed. 1990 o An OPTIONAL element that identifies elements that 1991 requiring exceptional server-operator handling to allow or 1992 restrict disclosure to third parties. See Section 2.9 of 1993 [RFC5733] for a description of the child elements contained within 1994 the element. 1996 Example object: 1998 ... 1999 2000 Csh8013-TEST 2001 sh8013 2002 2003 2004 2005 John Doe 2006 Example Inc. 2007 2008 123 Example Dr. 2009 Suite 100 2010 Dulles 2011 VA 2012 20166-6503 2013 US 2014 2015 2016 +1.7035555555 2017 +1.7035555556 2018 jdoe@example.test 2019 RegistrarX 2020 RegistrarX 2021 2009-09-13T08:01:00.0Z 2022 RegistrarX 2023 2009-11-26T09:10:00.0Z 2024 2009-12-03T09:05:00.0Z 2025 2026 pending 2027 clientW 2028 2011-03-08T19:38:00.0Z 2029 RegistrarX 2030 2011-03-13T23:59:59.0Z 2031 2032 2033 2034 2035 2036 2037 ... 2039 5.3.1.2. object 2041 The element contains the id of a contact that was 2042 deleted. 2044 Example of object: 2046 ... 2047 2048 ... 2049 2050 sh8013-TEST 2051 co8013-TEST 2052 2053 ... 2054 2055 ... 2057 5.3.2. CSV Model 2059 For the CSV Model of the contact object, the 2060 child element of the element is used to hold the new 2061 or updated contacts objects for the deposit. The 2062 child element of the element is 2063 used to hold the deleted or purged contact objects for the deposit. 2064 Both the and elements 2065 contain one or more elements with a set of named CSV 2066 file definitions using the "name" attribute. 2068 Differential and incremental deposits are based on changes to the 2069 contact objects. The updated contact object data under the 2070 element is a cascade replace down all of the 2071 contact CSV files starting with the parent "contact" CSV File 2072 Definition (Section 5.3.2.1.1). The child CSV file definitions 2073 include a field. All the child CSV 2074 file definition data for the contact objects in the parent "contact" 2075 CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and 2076 then set using the data in the child CSV files. The deleted contact 2077 object data under the element is a cascade 2078 delete starting from the "contact" Deletes CSV File Definition 2079 (Section 5.3.2.2.1). 2081 5.3.2.1. 2083 The is used to hold the new or updated contact 2084 object information for the deposit. The is 2085 split into separate CSV file definitions using named 2086 elements with the "name" attribute. The following sections include 2087 the supported contact CSV file definitions. 2089 5.3.2.1.1. "contact" CSV File Definition 2091 The "contact" CSV File Definition defines the fields and CSV file 2092 references used for the contact object records. 2094 The following "csvContact" field elements MUST be used in the 2095 "contact" element: 2097 Contains the server-unique contact identifier with 2098 type="eppcom:clIDType" and isRequired="true". 2100 Contains the contact's email address with 2101 type="eppcom:minTokenType" and isRequired="true". 2103 The following field elements MAY be used in the "contact" 2104 element: 2106 Contains the contact's voice telephone number 2107 with type="contact:e164StringType". 2109 Contains the contact's voice telephone number 2110 extension with type="token". 2112 Contains the contact's facsimile telephone number 2113 with type="contact:e164StringType". 2115 Contains the contact's facsimile telephone 2116 number extension with type="token". 2118 The following "rdeCsv" fields, defined in section CSV common field 2119 elements (Section 4.7.2), MUST be used in the "contact" 2120 element: 2122 The Registry Object IDentifier (ROID) for the contact 2123 object with isRequired="true". 2125 Identifier of client (registrar) that sponsors the 2126 contact object with isRequired="true". 2128 Identifier of the registrar, defined in Section 5.4, 2129 of the client that created the object with isRequired="true". 2131 Created date and time of the contact object with 2132 isRequired="true". 2134 Identifier of the registrar, defined in Section 5.4, 2135 of the client that updated the object. 2137 Date and time of the last update to the contact 2138 object. 2140 The following "rdeCsv" fields, defined in section CSV common field 2141 elements (Section 4.7.2), MAY be used in the "contact" 2142 element: 2144 Identifier of client that created the contact object. 2146 Identifier of the client that last updated the 2147 contact object. 2149 Date and time of the last transfer for the contact 2150 object. 2152 Example of a "contact" element. 2154 ... 2155 2156 ... 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2177 contact-YYYYMMDD.csv 2178 2179 2180 2181 ... 2182 2183 ... 2185 Example of the contact-YYYYMMDD.csv file. The file contains nine 2186 object contact records. 2188 domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, 2189 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2190 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2191 2009-11-26T09:10:00.0Z 2192 domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, 2193 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2194 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2195 2009-11-26T09:10:00.0Z 2196 domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, 2197 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2198 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2199 2009-11-26T09:10:00.0Z 2200 domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, 2201 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2202 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2203 2009-11-26T09:10:00.0Z 2204 domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, 2205 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2206 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2207 2009-11-26T09:10:00.0Z 2208 domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, 2209 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2210 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2211 2009-11-26T09:10:00.0Z 2212 xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, 2213 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2214 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2215 2009-11-26T09:10:00.0Z 2216 xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, 2217 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2218 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2219 2009-11-26T09:10:00.0Z 2220 xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, 2221 +1.7035555556,,jdoe@example.test,registrarX,registarX, 2222 clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2223 2009-11-26T09:10:00.0Z 2225 5.3.2.1.2. "contactStatuses" CSV File Definition 2227 The "contactStatuses" CSV File Definition defines the fields and CSV 2228 file references used for the contact object statuses. 2230 The following "csvContact" field elements, defined for the "contact" 2231 CSV File Definition (Section 5.3.2.1.1), MUST be used in the 2232 "contactStatuses" element: 2234 Server-unique contact identifier of status with 2235 isRequired="true". 2237 The status of the contact with 2238 type="contact:statusValueType" and isRequired="true". 2240 The following "rdeCsv" fields, defined in section CSV common field 2241 elements (Section 4.7.2), MAY be used in the "contactStatuses" 2242 element: 2244 The contact object status description 2245 which is free form text describing the rationale for the status. 2247 Language of the field. 2249 Example of a "contactStatuses" 2250 element. 2252 ... 2253 2254 ... 2255 2256 2257 2258 2259 2260 2261 2262 2263 2265 contactStatuses-YYYYMMDD.csv 2266 2267 2268 2269 ... 2270 2271 ... 2273 Example of the corresponding contactStatuses-YYYYMMDD.csv file. The 2274 file contains the statuses for the nine contact identifiers. 2276 domain1admin,ok,, 2277 domain1tech,ok,, 2278 domain1billing,ok,, 2279 domain2admin,ok,, 2280 domain2tech,ok,, 2281 domain2billing,ok,, 2282 xnabc123admin,ok,, 2283 xnabc123tech,ok,, 2284 xnabc123billing,ok,, 2286 5.3.2.1.3. "contactPostal" CSV File Definition 2288 The "contactPostal" CSV File Definition defines the fields and CSV 2289 file references used for the contact postal info object records. 2291 The following "csvContact" field elements MUST be used in the 2292 "contactPostal" element: 2294 Contains the form of the postal-address 2295 information with type="contact:postalLineType" and 2296 isRequired="true". This field specifies the form ("int" or 2297 "loc"), as defined in Section 4.8, of the , 2298 , , , 2299 , , fields. 2301 Contains the contact's name of the individual or 2302 role represented by the contact with type="contact:postalLineType" 2303 and isRequired="true". An OPTIONAL "isLoc" attribute to used to 2304 indicate the localized or internationalized form as defined in 2305 section Section 4.8. 2307 Contains the contact's contact's street address 2308 line with type="contact:fPostalLineType". An index attribute is 2309 required to indicate which street address line the field 2310 represents with index "0" for the first line and index "2" for the 2311 last line. An OPTIONAL "isLoc" attribute to used to indicate the 2312 localized or internationalized form as defined in section 2313 Section 4.8. 2315 Contains the contact's city with 2316 type="contact:postalLineType" and isRequired="true". An OPTIONAL 2317 "isLoc" attribute to used to indicate the localized or 2318 internationalized form as defined in section Section 4.8. 2320 Contains the contact's country code with 2321 type="contact:ccType" and isRequired="true". An OPTIONAL "isLoc" 2322 attribute to used to indicate the localized or internationalized 2323 form as defined in section Section 4.8. 2325 The following "csvContact" field elements MAY be used in the 2326 "contactPostal" element: 2328 Contains the name of the organization with which 2329 the contact is affiliated with type="contact:optPostalLineType". 2330 An OPTIONAL "isLoc" attribute to used to indicate the localized or 2331 internationalized form as defined in section Section 4.8. 2333 Contains the contact's state or province with 2334 type="contact:optPostalLineType". An OPTIONAL "isLoc" attribute 2335 to used to indicate the localized or internationalized form as 2336 defined in section Section 4.8. 2338 Contains the contact's postal code with 2339 type="contact:pcType". An OPTIONAL "isLoc" attribute to used to 2340 indicate the localized or internationalized form as defined in 2341 section Section 4.8. 2343 The following "csvContact" fields, defined for the "contact" CSV File 2344 Definition (Section 5.3.2.1.1), MUST be used in the "contactPostal" 2345 element: 2347 Server-unique contact identifier for the contact 2348 object with isRequired="true". 2350 Example of a "contactPostal" 2351 element. 2353 ... 2354 2355 ... 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2373 contactPostal-YYYYMMDD.csv 2374 2375 2376 2377 ... 2378 2379 ... 2381 Example of the contactPostal-YYYYMMDD.csv file. The file contains 2382 nine contact postal records. 2384 domain1admin,int,"John Doe","Example Inc.", 2385 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2386 domain1tech,int,"John Doe","Example Inc.", 2387 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2388 domain1billing,int,"John Doe","Example Inc.", 2389 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2390 domain2admin,int,"John Doe","Example Inc.", 2391 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2392 domain2tech,int,"John Doe","Example Inc.", 2393 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2394 domain2billing,int,"John Doe","Example Inc.", 2395 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2396 xnabc123admin,int,"John Doe","Example Inc.", 2397 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2398 xnabc123tech,int,"John Doe","Example Inc.", 2399 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2400 xnabc123billing,int,"John Doe","Example Inc.", 2401 "123 Example Dr.","Suite 100",,Reston,VA,20190,US 2403 5.3.2.1.4. "contactTransfer" CSV File Definition 2405 The "contactTransfer" CSV File Definition defines the fields and CSV 2406 file references used for the contact object pending and completed 2407 transfer records. No additional field elements were added for use in 2408 the "contactTransfer" element. The 2409 following "rdeCsv" fields, defined in section CSV common field 2410 elements (Section 4.7.2), MUST be used in the "contactTransfer" 2411 element: 2413 State of the most recent transfer request with 2414 isRequired="true". 2416 Identifier of the registrar, defined in Section 5.4, 2417 of the client that requested the transfer with isRequired="true". 2419 Date and time that the transfer was requested with 2420 isRequired="true". 2422 Identifier of the registrar, defined in Section 5.4, 2423 of the client that should take or took action with 2424 isRequired="true". 2426 Date and time that the transfer action should be 2427 taken or has been taken with isRequired="true". 2429 The following "rdeCsv" fields, defined in section CSV common field 2430 elements (Section 4.7.2), MAY be used in the "contactTransfer" 2431 element: 2433 Identifier of client that requested the transfer. 2435 Identifier of client that should take or took action 2436 for transfer. 2438 The following "csvContact" fields, defined for the "contact" CSV File 2439 Definition (Section 5.3.2.1.1), MUST be used in the "contactTransfer" 2440 element: 2442 Server-unique contact identifier for the contact 2443 object with isRequired="true". 2445 Example of a "contactTransfer" 2446 element. 2448 ... 2449 2450 ... 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2465 contactTransfer-YYYYMMDD.csv 2466 2467 2468 2469 ... 2470 2471 ... 2473 Example of the contactTransfer-YYYYMMDD.csv file. The file contains 2474 one contact transfer record in pending status. 2476 xnabc123admin,clientApproved,registrarX,clientX, 2477 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z 2479 5.3.2.1.5. "contactDisclose" CSV File Definition 2481 The "contactDisclose" CSV File Definition defines the fields and CSV 2482 file references used for the contact disclose object records. 2484 The following "csvContact" field elements MAY be used in the 2485 "contactDisclose" element: 2487 Contains flag with a value of "true" or 2488 "1" (one) notes the preference to allow disclosure of the 2489 specified elements as an exception to the stated data-collection 2490 policy. A value of "false" or "0" (zero) notes a client 2491 preference to not allow disclosure of the specified elements as an 2492 exception to the stated data-collection policy with 2493 type="boolean". The additional fields define specific exceptional 2494 disclosure preferences based on the 2495 field. 2497 Exceptional disclosure preference flag 2498 for the localized form of the contact name with type="boolean". 2500 Exceptional disclosure preference flag 2501 for the internationalized form of the contact name with 2502 type="boolean". 2504 Exceptional disclosure preference flag 2505 for the localized form of the contact organization with 2506 type="boolean". 2508 Exceptional disclosure preference flag 2509 for the internationalized form of the contact organization with 2510 type="boolean". 2512 Exceptional disclosure preference flag 2513 for the localized form of the contact address with type="boolean". 2515 Exceptional disclosure preference flag 2516 for the internationalized form of the contact address with 2517 type="boolean". 2519 Exceptional disclosure preference flag 2520 of the contact voice telephone number with type="boolean". 2522 Exceptional disclosure preference flag of 2523 the contact facsimile telephone number with type="boolean". 2525 Exceptional disclosure preference flag 2526 of the contact email address with type="boolean". 2528 The following "csvContact" fields, defined for the "contact" CSV File 2529 Definition (Section 5.3.2.1.1), MUST be used in the "contactDisclose" 2530 element: 2532 Server-unique contact identifier for the contact 2533 object with isRequired="true". 2535 Example of a "contactDisclose" 2536 element. 2538 ... 2539 2540 ... 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2558 contactDisclose-YYYYMMDD.csv 2559 2560 2561 2562 ... 2563 2564 ... 2566 Example of the contactDisclose-YYYYMMDD.csv file. The file contains 2567 one disclosure records, disabling disclosure of voice, fax, and 2568 email. 2570 xnabc123admin,0,0,0,0,0,0,0,1,1,1 2572 5.3.2.2. 2574 The is used to hold the deleted contact objects 2575 in a differential or incremental deposit. All the contact object 2576 data is deleted as part of a cascade delete. The 2577 is split into separate CSV file definitions 2578 using named elements with the "name" attribute. The 2579 following section defines the supported contact deletes CSV file 2580 definition. 2582 5.3.2.2.1. "contact" Deletes CSV File Definition 2584 The following "csvContact" field elements MUST be used in the deletes 2585 "contact" element: 2587 Contains the server-unique contact identifier with 2588 type="eppcom:clIDType" and isRequired="true". 2590 Example of a "contact" element. 2592 ... 2593 2594 ... 2595 2596 2597 2598 2599 2600 2602 contact-delete-YYYYMMDD.csv 2603 2604 2605 2606 ... 2607 2608 ... 2610 Example of the contact-delete-YYYYMMDD.csv file. The file contains 2611 six contact records. 2613 domain1admin 2614 domain1tech 2615 domain1billing 2616 domain2admin 2617 domain2tech 2618 domain2billing 2620 5.4. Registrar Object 2622 The registrar object represents the sponsoring client for other 2623 objects, for operational purposes MAY be the registry operator. The 2624 registrar object supports both the XML Model and the CSV Model, 2625 defined in Section 2. The elements used for both models are defined 2626 in the following sections. 2628 5.4.1. XML Model 2630 There are two elements used in the data escrow of the registrar 2631 objects for the XML model including the , 2632 under the element, and the 2633 element, under the element. 2635 A element substitutes for the 2636 abstract element to define a 2637 concrete definition of a registrar. The 2638 element can be replaced by other 2639 domain definitions using the XML schema substitution groups feature. 2641 5.4.1.1. element 2643 The element contains the following child elements: 2645 o An element that contains the Registry-unique identifier of 2646 the registrar object. This has a superordinate relationship 2647 to a subordinate , or of domain, contact and 2648 host objects. 2650 o An element that contains the name of the registrar. 2652 o An OPTIONAL element that contains the ID assigned by 2653 ICANN. 2655 o An OPTIONAL element that contains the operational status 2656 of the registrar. Possible values are: ok, readonly and 2657 terminated. 2659 o Zero or two OPTIONAL elements that contain postal- 2660 address information. Two elements are provided so that address 2661 information can be provided in both internationalized and 2662 localized forms; a "type" attribute is used to identify the two 2663 forms. If an internationalized form (type="int") is provided, 2664 element content MUST be represented in a subset of UTF-8 that can 2665 be represented in the 7-bit US-ASCII character set. If a 2666 localized form (type="loc") is provided, element content MAY be 2667 represented in unrestricted UTF-8. The element 2668 contains the following child elements: 2670 * A element that contains address information associated 2671 with the registrar. The element contains the following 2672 child elements: 2674 + One, two, or three OPTIONAL elements that contain 2675 the registrar's street address. 2677 + A element that contains the registrar's city. 2679 + An OPTIONAL element that contains the registrar's state 2680 or province. 2682 + An OPTIONAL element that contains the registrar's 2683 postal code. 2685 + A element that contains the registrar's country code. 2687 o An OPTIONAL element that contains the registrar's voice 2688 telephone number. 2690 o An OPTIONAL element that contains the registrar's facsimile 2691 telephone number. 2693 o An OPTIONAL element that contains the registrar's email 2694 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 An OPTIONAL element that contains the date and time of 2709 registrar-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 2767 child element of the element 2768 is used to hold the new or updated registrar objects for the deposit. 2769 The child element of the element 2770 is used to hold the deleted or purged registrar objects for the 2771 deposit. Both the and 2772 elements contain one or more elements with a set of 2773 named CSV file definitions using the "name" attribute. 2775 Differential and incremental deposits are based on changes to the 2776 registrar objects. The updated registrar object data under the 2777 element is a cascade replace down all of the 2778 registrar CSV files starting with the parent "registrar" CSV File 2779 Definition (Section 5.4.2.1.1). The child CSV file definitions 2780 include a field. All the child CSV 2781 file definition data for the registrar objects in the parent 2782 "registrar" CSV File Definition (Section 5.4.2.1.1) MUST first be 2783 deleted and then set using the data in the child CSV files. The 2784 deleted registrar object data under the 2785 element is a cascade delete starting from the "registrar" Deletes CSV 2786 File Definition (Section 5.4.2.2.1). 2788 5.4.2.1. 2790 The is used to hold the new or updated 2791 registrar object information for the deposit. The 2792 is split into separate CSV file definitions 2793 using named elements with the "name" attribute. The 2794 following sections include the supported contact CSV file 2795 definitions. 2797 5.4.2.1.1. "registrar" CSV File Definition 2799 The "registrar" CSV File Definition defines the fields and CSV file 2800 references used for the registrar object records. 2802 The following "csvRegistrar" field elements MUST be used in the 2803 "registrar" element: 2805 Contains the server-unique registrar identifier 2806 with type="eppcom:clIDType" and isRequired="true". 2808 Contains the name of the registrar with 2809 type="normalizedString" and isRequired="true". 2811 The following field elements MAY be used in the "registrar" 2812 element: 2814 Contains the status of the registrar with 2815 type="csvRegistrar:statusValueType". 2817 Contains the ID assigned by ICANN with 2818 type="positiveInteger". 2820 Contains the Whois URL of the registrar 2821 with type="anyURI". 2823 The following "rdeCsv" fields, defined in section CSV common field 2824 elements (Section 4.7.2), MAY be used in the "registrar" 2825 element: 2827 Created date and time of the registrar object. 2829 Date and time of the last update to the registrar 2830 object. 2832 URL for the registrar web home page. 2834 The following "csvContact" fields, defined in section Contact Object 2835 (Section 5.3), MAY be used in the "registrar" 2836 element: 2838 Registrar street address line with an "index" 2839 attribute that represents the order of the street address line 2840 from "0" to "2". An OPTIONAL "isLoc" attribute that is used to 2841 indicate the localized or internationalized form, as defined in 2842 Section 4.8. 2844 Registrar city with an OPTIONAL "isLoc" attribute 2845 that is used to indicate the localized or internationalized form, 2846 as defined in Section 4.8. 2848 Registrar country code with an OPTIONAL "isLoc" 2849 attribute that is used to indicate the localized or 2850 internationalized form, as defined in Section 4.8. 2852 Registrar email address. 2854 Registrar state or province with an OPTIONAL 2855 "isLoc" attribute that is used to indicate the localized or 2856 internationalized form, as defined in Section 4.8. 2858 Registrar postal code with an OPTIONAL "isLoc" 2859 attribute that is used to indicate the localized or 2860 internationalized form, as defined in Section 4.8. 2862 Registrar voice telephone number. 2864 Registrar voice telephone number extension. 2866 Registrar facsimile telephone number. 2868 Registrar facsimile telephone number extension. 2870 Example of a "registrar" 2871 element. 2873 ... 2874 2875 ... 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2902 registrar-YYYYMMDD.csv 2903 2904 2905 2906 ... 2907 2908 ... 2910 Example of the registrar-YYYYMMDD.csv file. The file contains three 2911 registrar records. 2913 registrarX,"Example Inc.",1234,ok,"123 Example Dr.", 2914 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2915 +1.7035555556,,jdoe@example.test,http://www.example.test, 2916 http://whois.example.test,2005-04-23T11:49:00.0Z, 2917 2009-02-17T17:51:00.0Z 2918 registrarY,"Example2 Inc.",1234,ok,"123 Example Dr.", 2919 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2920 +1.7035555556,,jdoe@example.test,http://www.example.test, 2921 http://whois.example.test,2005-04-23T11:49:00.0Z, 2922 2009-02-17T17:51:00.0Z 2923 registrarZ,"Example2 Inc.",1234,ok,"123 Example Dr.", 2924 "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, 2925 +1.7035555556,,jdoe@example.test,http://www.example.test, 2926 http://whois.example.test,2005-04-23T11:49:00.0Z, 2927 2009-02-17T17:51:00.0Z 2929 5.4.2.2. 2931 The is used to hold the deleted registrar 2932 objects in a differential or incremental deposit. All the registrar 2933 object data is deleted as part of a cascade delete. The 2934 is split into separate CSV file definitions 2935 using named elements with the "name" attribute. The 2936 following section defines the supported registrar deletes CSV file 2937 definition. 2939 5.4.2.2.1. "registrar" Deletes CSV File Definition 2941 The following "csvRegistrar" field elements MUST be used in the 2942 deletes "registrar" element: 2944 Contains the server-unique registrar identifier 2945 with type="eppcom:clIDType" and isRequired="true". 2947 Example of a "registrar" element. 2949 ... 2950 2951 ... 2952 2953 2954 2955 2956 2957 2959 registrar-delete-YYYYMMDD.csv 2960 2961 2962 2963 ... 2964 2965 ... 2967 Example of the registrar-delete-YYYYMMDD.csv file. The file contains 2968 one registrar record. 2970 registrarZ 2972 5.5. IDN Table Reference Object 2974 The Internationalized Domain Names (IDN) table reference object is a 2975 pseudo-object that is used to provide a short reference to the IDN 2976 Table and Policy used in IDN registrations. The IDN reference object 2977 supports both the XML and the CSV Model, defined in the Models 2978 (Section 2) section. The elements used for both models are defined 2979 in the following sections. 2981 5.5.1. XML Model 2983 There is one element used in the data escrow of the IDN table 2984 reference objects for the XML model that is the , 2985 under the element. 2987 5.5.1.1. object 2989 The contains the following elements. An "id" 2990 attribute is used to specify an identifier for the IDN table. 2992 o An element that contains the URL of the IDN table that is 2993 being referenced. 2995 o A element that contains the URL of the IDN policy 2996 document. If IDN variants are generated algorithmically, the 2997 policy document MUST define the algorithm and the state of the 2998 implicit generated IDN variants. For a list of suggested states 2999 for implicit IDN variants, please see [variantTLDsReport]. 3001 Example of object: 3003 ... 3004 3005 3006 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 3007 3008 3009 http://registro.br/dominio/regras.html 3010 3011 3012 ... 3014 5.5.2. CSV Model 3016 The IDN domain names, defined in Section 5.1, MAY have references to 3017 the IDN language identifier using the field 3018 element. The IDN table reference object defines the mapping of a 3019 language identifier to a language table URL. The language table URL 3020 defines the character code points that can be used for the language 3021 identifier. The elements used for the IDN table reference object is 3022 defined in this section. The child element of the 3023 element is used to hold the new or updated IDN table 3024 reference objects for the deposit. The child 3025 element of the element is used to hold the deleted or 3026 purged IDN table reference objects for the deposit. Both the 3027 and elements contain one or more 3028 elements with a set of named CSV file definitions using 3029 the "name" attribute. 3031 5.5.2.1. 3033 The is used to hold the new or updated IDN table 3034 reference object information for the deposit. The 3035 is split into separate CSV file definitions using named 3036 elements with the "name" attribute. The following sections include 3037 the supported IDN table reference CSV file definitions. 3039 5.5.2.1.1. "idnLanguage" CSV File Definition 3041 The "idnLanguage" CSV File Definition defines the fields and CSV file 3042 references used for the IDN table reference object records. 3044 The following "rdeCsv" fields, defined in Section 4.7.2, MUST be used 3045 in the "idnLanguage" element: 3047 The language identifier that matches the values 3048 for the field element in the "domain" CSV 3049 File Definition (Section 5.1.2.1.1) files. The attribute 3050 isRequired MUST equal "true". 3052 URL that defines the character code points that can be 3053 used for the language defined by the field element. 3054 The attribute isRequired MUST equal "true". 3056 Example of a "idnLanguage" element. 3058 ... 3059 3060 ... 3061 3062 , 3063 3064 3065 3066 3067 3068 3070 idnLanguage-YYYYMMDD.csv 3071 3072 3073 3074 ... 3075 3076 ... 3078 Example of the corresponding idnLanguage-YYYYMMDD.csv file. The file 3079 contains two IDN language records. 3081 LANG-1, 3082 http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt 3083 LANG-2, 3084 http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt 3086 5.5.2.2. 3088 The is used to hold the deleted IDN table reference 3089 objects in a differential or incremental deposit. The 3090 is split into separate CSV file definitions using 3091 named elements with the "name" attribute. The following 3092 section defines the supported IDN table reference deletes CSV file 3093 definition. 3095 5.5.2.2.1. "idnLanguage" Deletes CSV File Definition 3097 The following "idnLanguage" field elements MUST be used in the 3098 deletes "idnLanguage" element: 3100 The language identifier that matches the values 3101 for the field element in the "domain" CSV 3102 File Definition (Section 5.1.2.1.1) files. The attribute 3103 isRequired MUST equal "true". 3105 Example of a "idnLanguage" element. 3107 ... 3108 3109 ... 3110 3111 3112 3113 3114 3115 3117 idnLanguage-delete-YYYYMMDD.csv 3118 3119 3120 3121 ... 3122 3123 ... 3125 Example of the idnLanguage-delete-YYYYMMDD.csv file. The file 3126 contains one IDN language record. 3128 LANG-2 3130 5.6. NNDN Object 3132 A NNDN (NNDN's not domain name) can be used to store registry 3133 reserved names or (blocked, withheld or mirrored) IDN variants. 3135 A NNDN is a lightweight domain-like object that is not linked 3136 directly to a Registrar (a mirroring NNDN is linked to a Registrar 3137 via the original name). 3139 A domain name can only exist as a domain name object or NNDN object, 3140 but not both. 3142 The NNDN object supports both the XML and the CSV Model, defined in 3143 the Models (Section 2) section. The elements used for both models 3144 are defined in the following sections. 3146 5.6.1. XML Model 3148 There are two elements used in the data escrow of the NNDN objects 3149 for the XML model including the , under the 3150 element, and the element, under the 3151 element. 3153 A element substitutes for the 3154 abstract element to define a concrete definition of a NNDN. The 3155 element can be replaced by other NNDN 3156 definitions using the XML schema substitution groups feature. 3158 5.6.1.1. object 3160 The element contains the following child elements: 3162 o An element that contains the fully qualified name of the 3163 NNDN. If the NNDN is an IDN, the ASCII Compatible Encoding (ACE) 3164 MUST be used. 3166 o An OPTIONAL element that contains the fully qualified name 3167 of the NNDN in Unicode character set. It MUST be provided if 3168 available. 3170 o An OPTIONAL element that references the IDN 3171 Table used for the NNDN. This corresponds to the "id" attribute 3172 of the element. This element MUST be present if the 3173 NNDN is an IDN. 3175 o An OPTIONAL element is used to indicate that the 3176 NNDN is used for an IDN variant. This element contains the domain 3177 name used to generate the IDN variant. 3179 o A element that indicates the state of the NNDN: 3180 blocked, withheld or mirrored. 3182 * If a NNDN is considered undesirable for registration (i.e., 3183 unavailable for allocation to anyone), then the NNDN will be 3184 tagged as "blocked". 3186 * If a NNDN is considered a potential registration of a domain 3187 object for a registrant, then the NNDN will be tagged as 3188 "withheld". This status is only used when the NNDN is used for 3189 an IDN variant. 3191 * If a NNDN is considered a mirrored IDN variant of a domain 3192 object, then the NNDN will be tagged as "mirrored". A 3193 mirroringNS attribute is used to specify if the mirrored IDN 3194 variant use the NS mirror mechanism. The default value of 3195 mirroringNS is true. If another mechanism such as DNAME is 3196 used, the value of mirroringNS attribute MUST be false. 3198 o A element that contains the date and time of the NNDN 3199 object creation. 3201 Example of object: 3203 ... 3204 3205 xn--exampl-gva.test 3206 pt-BR 3207 example1.test 3208 withheld 3209 2005-04-23T11:49:00.0Z 3210 3211 ... 3213 5.6.1.2. object 3215 The element contains the ACE of a NNDN that was 3216 deleted, i.e., the . 3218 Example of object: 3220 ... 3221 3222 ... 3223 3224 xn--pingino-q2a.test 3225 3226 ... 3227 3228 ... 3230 5.6.2. CSV Model 3232 For the CSV Model of the NNDN object, the child 3233 element of the element is used to hold the new or 3234 updated NNDN objects for the deposit. The child 3235 element of the element is used to hold the deleted or 3236 purged NNDN objects for the deposit. Both the and 3237 elements contain one or more elements 3238 with a set of named CSV file definitions using the 3239 "name" attribute. 3241 5.6.2.1. 3243 The is used to hold the new or updated NNDN object 3244 information for the deposit. The is split into 3245 separate CSV file definitions using named elements with 3246 the "name" attribute. The following sections include the supported 3247 NNDN CSV file definitions. 3249 5.6.2.1.1. "NNDN" CSV File Definition 3251 The "NNDN" CSV File Definition defines the fields and CSV file 3252 references used for the NNDN object records. 3254 The following "csvNNDN" field elements MUST be used in the "NNDN" 3255 element: 3257 ASCII Compatible Encoding (ACE) field of the NNDN 3258 with type="eppcom:labelType" and isRequired="true". 3260 State of the NNDN: blocked or withheld with 3261 type="rdeNNDN:nameState" and isRequired="true". See 3262 Section 5.6.1.1 for a description of the possible values for the 3263 element. 3265 The following field elements MAY be used in the "NNDN" 3266 element: 3268 Domain name used to generate the IDN variant 3269 with type="eppcom:labelType". 3271 Defines whether the "mirroring" 3272 uses the NS mirror mechanism, as described 3273 for the "mirroringNS" attribute in 3274 Section 5.6.1.1, with type="boolean". If the field element is not 3275 defined the default value is "true". 3277 The following "rdeCsv" fields, defined in section CSV common field 3278 elements (Section 4.7.2), MUST be used in the "domain" 3279 element: 3281 Created date and time of the NNDN object with 3282 isRequired="true". 3284 The following "rdeCsv" fields, defined in section CSV common field 3285 elements (Section 4.7.2), MAY be used in the "domain" 3286 element: 3288 Name of the NNDN in Unicode character set for the 3289 field element. 3291 IDN Table Identifier for the NNDN that matches 3292 an IDN Table Reference Object record, as defined in Section 5.5.2. 3294 Example of a "NNDN" element: 3296 ... 3297 3298 ... 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3311 NNDN-YYYYMMDD.csv 3312 3313 3314 3315 ... 3316 3317 ... 3319 Example of the corresponding NNDN-YYYYMMDD.csv file. The file 3320 contains two NNDN records for an IDN with one blocked variant and one 3321 mirrored variant. 3323 xn--abc456.test,LANG-1,xn--abc123.test, 3324 blocked,,2005-04-23T11:49:00.0Z 3325 xn--abc789.test,LANG-1,xn--abc123.test, 3326 mirrored,1,2005-04-23T11:49:00.0Z 3328 5.6.2.2. 3330 The is used to hold the deleted NNDN objects in a 3331 differential or incremental deposit. The is split 3332 into separate CSV file definitions using named elements 3333 with the "name" attribute. The following section defines the 3334 supported NNDN deletes CSV file definition. 3336 5.6.2.2.1. "NNDN" Deletes CSV File Definition 3338 The following "NNDN" field elements MUST be used in the deletes 3339 "NNDN" element: 3341 ASCII Compatible Encoding (ACE) field of the NNDN 3342 with type="eppcom:labelType" and isRequired="true". 3344 Example of a "NNDN" element. 3346 ... 3347 3348 ... 3349 3350 3351 3352 3353 3354 3356 NNDN-delete-YYYYMMDD.csv 3357 3358 3359 3360 ... 3361 3362 ... 3364 Example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file 3365 contains one NNDN records. 3367 xn--abc456.test 3369 5.7. EPP Parameters Object 3371 The EPP Parameters Object is a pseudo-object that defines the set of 3372 object and object extension services supported by the registry, as 3373 defined in [RFC5730]. The EPP Parameters Object is only defined as 3374 XML but could be used in the XML model or CSV model. The EPP 3375 Parameters Object is defined using the 3376 element. The EPP Parameters Object SHOULD be included if the 3377 registry supports EPP. Only one EPP Parameters Object MUST exist at 3378 a certain point in time (watermark). 3380 The syntax and content of the children 3381 elements is as explained in section 2.4 of [RFC5730]. The children 3382 of the are as follows: 3384 o One or more elements that indicate the EPP versions 3385 supported by the registry. 3387 o One or more elements that indicate the identifiers of the 3388 text response languages supported by the registry's EPP server. 3390 o One or more elements that contain namespace URIs 3391 representing the objects that the registry's EPP server is capable 3392 of managing. 3394 o An OPTIONAL element that contains one or more 3395 elements that contain namespace URIs representing object 3396 extensions supported by the registry's EPP server. 3398 o A element that contains child elements used to describe the 3399 server's privacy policy for data collection and management. See 3400 section 2.4 of [RFC5730] for more details. 3402 Example of element object: 3404 ... 3405 3406 1.0 3407 en 3408 urn:ietf:params:xml:ns:domain-1.0 3409 3410 urn:ietf:params:xml:ns:contact-1.0 3411 3412 urn:ietf:params:xml:ns:host-1.0 3413 3414 3415 urn:ietf:params:xml:ns:rgp-1.0 3416 urn:ietf:params:xml:ns:secDNS-1.1 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 ... 3437 5.8. Policy Object 3439 The Policy object is a pseudo-object that is used to specify which 3440 OPTIONAL elements from the XML Model are REQUIRED based on the 3441 business model of the registry. For the CSV Model, the OPTIONAL 3442 "isRequired" attribute of the elements, defined in 3443 Section 4.7.1, is used to specify which OPTIONAL fields are REQUIRED 3444 based on the business model of the registry. 3446 5.8.1. object 3448 The OPTIONAL contains the following attributes: 3450 o An that defines that the referenced is 3451 REQUIRED. 3453 o that defines the XPath of the element referenced by 3454 . 3456 Example of object: 3458 ... 3459 3461 ... 3463 5.9. Header Object 3465 The Header Object is a pseudo-object that is used to specify the 3466 number of objects in the repository at a specific point in time 3467 (watermark) regardless of the type of deposit: differential, full or 3468 incremental. The Header Object is only defined as XML but one header 3469 object MUST always be present per escrow deposit regardless of using 3470 XML Model or CSV Model. The Header Object is defined using the 3471 element. 3473 5.9.1. object 3475 The contains the following elements: 3477 o A choice of one of the elements defined in the 3478 "repositoryTypeGroup" group element that indicates the unique 3479 identifier for the repository being escrowed. Possible elements 3480 are: 3482 * A element that defines TLD or the REGISTRY- 3483 CLASS DOMAIN NAME (RCDN) being escrowed in the case of a 3484 Registry data escrow deposit. For IDNs the A-Label is used 3485 [RFC5891]. 3487 * A element that defines the Registrar ID 3488 corresponding to a Registrar data escrow deposit. In the case 3489 of an ICANN-accredited Registrar, the 3490 element MUST be the IANA Registrar ID assigned by ICANN. 3492 * A element that defines the provider ID 3493 corresponding to a Privacy and Proxy Services Provider data 3494 escrow deposit. In the case of an ICANN-accredited Privacy and 3495 Proxy Services Provider, the element MUST be 3496 the unique ID assigned by ICANN. 3498 o A element that contains the number of objects in the SRS 3499 at a specific point in time (watermark) regardless of the type of 3500 deposit: differential, full or incremental. The element 3501 supports the following attributes: 3503 * A "uri" attribute reflects the XML namespace URI of the primary 3504 objects for the XML Model and CSV Model. For example, the 3505 "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for 3506 domain name objects using the XML Model, and the "uri" is set 3507 to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name 3508 objects using the CSV Model. 3510 * An OPTIONAL "rcdn" attribute indicates the REGISTRY-CLASS 3511 DOMAIN NAME (RCDN) of the objects included in the 3512 element. For IDNs the A-Label is used [RFC5891]. If the 3513 "rcdn" attribute is present, the value of the element 3514 must include only objects related to registrations in the same 3515 and lower levels. For example in a data escrow deposit for the 3516 .EXAMPLE TLD, a value of "example" in the "rcdn" attribute 3517 within the element indicates the number of objects in 3518 the TLD including objects in other RCDNs within the TLD, 3519 whereas a value of "com.example" indicates the number of 3520 elements for objects under "com.example" and lower levels. 3521 Omitting the "rcdn" attribute indicates that the total includes 3522 all objects of the specified "uri" in the repository (e.g. the 3523 TLD, Registrar, or PPSP). 3525 * An OPTIONAL "registrarId" attribute indicates the identifier of 3526 the sponsoring Registrar of the objects included in the 3527 element. In the case of an ICANN-accredited Registrar, the 3528 value MUST be the IANA Registrar ID assigned by ICANN. 3530 Example of object referencing only the XML Model 3531 objects: 3533 ... 3534 3535 test 3536 2 3538 1 3540 1 3542 1 3544 3545 1 3547 1 3549 1 3551 3552 3553 ... 3555 Example of object referencing the CSV and XML 3556 Model objects: 3558 ... 3559 3560 test 3561 2 3563 1 3565 1 3567 1 3569 3570 1 3572 1 3574 1 3576 3577 3578 ... 3580 6. RDE IDN Variants handling 3582 Depending on the Registration Policy of the Registry; for a domain 3583 name there may be multiple variant names. See [variantTLDsReport] 3584 for further detail on IDN variants. 3586 A registry could choose to escrow IDN variants as domains or NNDN 3587 objects. A specific IDN variant can be represented in the escrow 3588 deposit, as a domain or as a NNDN object, but not both. 3590 If using domain objects to represent IDN variants, the normal 3591 behavior during restoration of a SRS based on an escrow deposit is to 3592 restore the IDN variants as a mirrored variant. If the registration 3593 data of the IDN variant is different from the original name, the 3594 details of this specific implementation MUST be described in the IDN 3595 policy document. 3597 A NNDN or a domain name are explicit representations of an IDN 3598 variant while an IDN variant computed based on an algorithm is an 3599 implicit representation. Explicit representation of an IDN variant 3600 takes precedence over an implicit representation. 3602 7. Profile 3604 Different business models of registries exist, therefore the registry 3605 is responsible to define a profile that matches its particular 3606 business model. The profile mechanism allows a registry to extend 3607 this specification. 3609 A profile is the process of: 3611 1. Extending base objects with the mechanisms defined for XML and 3612 CSV models. 3614 * In the case of the XML model, abstract elements could be use 3615 to extend the following objects: , , , 3616 and using XML schema substitution groups 3617 feature. 3619 2. Defining a object to specify which OPTIONAL elements of 3620 this base specification is required based on the business model 3621 of the registry. An example is the element that is 3622 usually REQUIRED but it is specified as OPTIONAL in this 3623 specification to support existing business models. 3625 3. Adding new escrowed objects using the and 3626 elements. 3628 4. Providing the XML schemas to third parties that require them to 3629 validate the escrow deposits. 3631 8. Data escrow agent extended verification process 3633 The Data Escrow Agent MUST perform a extended verification process 3634 using the contents of the data escrow deposits to a point in time 3635 (watermark), last full plus all differentials or last full plus last 3636 incremental escrow deposits. The following are the minimum suggested 3637 tests: 3639 o Validate the escrow deposits using the definition agreed with the 3640 registry. 3642 * In the case of the XML model, the contents of the escrow 3643 deposits MUST be validated using the XML schemas of the 3644 profile. 3646 o Count the objects and validate that the number of objects is equal 3647 to the number objects reported in the
element of the 3648 escrow deposit of that point in time (watermark). 3650 o All contact objects linked to domain names MUST be present. 3652 o All registrars objects linked to other objects MUST be present. 3654 o A domain name exists as a domain name or NNDN, but not both. 3656 o The elements listed as required in the element MUST be 3657 present. 3659 o All idnTableRef definitions linked from other objects MUST be 3660 present. 3662 o If an EPP Parameters Object was escrowed in the past, one and only 3663 one EPP Parameters Object MUST be present. 3665 o The watermark is not in the future. 3667 9. Formal Syntax 3669 Schemas are presented here. 3671 9.1. RDE CSV Schema 3673 Copyright (c) 2012 IETF Trust and the persons identified as authors 3674 of the code. All rights reserved. 3676 Redistribution and use in source and binary forms, with or without 3677 modification, are permitted provided that the following conditions 3678 are met: 3680 o Redistributions of source code must retain the above copyright 3681 notice, this list of conditions and the following disclaimer. 3683 o Redistributions in binary form must reproduce the above copyright 3684 notice, this list of conditions and the following disclaimer in 3685 the documentation and/or other materials provided with the 3686 distribution. 3688 o Neither the name of Internet Society, IETF or IETF Trust, nor the 3689 names of specific contributors, may be used to endorse or promote 3690 products derived from this software without specific prior written 3691 permission. 3693 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3694 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3695 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3696 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3697 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3698 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3699 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3700 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3701 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3702 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3703 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3705 BEGIN 3706 3708 3715 3718 3720 3723 3724 3725 Registry Data Escrow Comma-Seperated Values (CSV) 3726 3727 3729 3730 3732 3733 3734 3735 3736 3737 3738 3739 3740 3742 3743 3744 3745 3746 3747 3748 3750 3751 3754 3755 3756 3758 3759 3760 3761 3762 3763 3765 3767 3768 3769 3771 3772 3773 3774 3775 3776 3778 3780 3781 3782 3784 3786 3787 3789 3790 3791 3792 3793 3795 3796 3797 3798 3799 3800 3801 3802 3804 3805 3806 3808 3809 3811 3812 3813 3814 3815 3817 3818 3819 3821 3822 3824 3825 3826 3827 3828 3830 3831 3832 3834 3835 3839 3840 3841 3843 3845 3847 3848 3850 3852 3854 3855 3857 3859 3861 3863 3865 3867 3869 3871 3873 3874 3875 3876 3877 3879 3880 3881 3882 3883 3884 3885 3886 3889 3890 3891 3893 3894 3896 3898 3900 3901 3903 3904 3906 3908 3909 3910 3911 3912 3914 3915 3916 3917 3918 3919 3920 3921 3923 3924 3925 3927 3928 3929 3930 3931 3932 3934 3936 3937 3938 3939 3940 3941 3942 3944 3945 3946 3948 3949 3950 3951 3952 3953 3955 3956 3957 3958 3959 3960 3961 3962 3964 3965 3966 3968 3969 3970 3971 3972 3973 3975 3976 3977 3978 3979 3980 3981 3982 3985 3986 3987 3989 3990 3991 3992 3993 3994 3996 3997 3998 3999 4000 4001 4002 4003 4005 4006 4007 4009 4010 4012 4013 4014 4015 4016 4018 4019 4020 4022 4023 4026 4027 4029 4030 4031 4032 4033 4035 4036 4037 4039 4040 4041 4042 4043 4044 4046 4047 4048 4050 4051 4052 4053 4054 4055 4057 4058 4059 4061 4062 4063 4064 4065 4066 4068 4069 4070 4072 4073 4075 4076 4077 4078 4079 4080 4082 4083 4084 4086 4087 4088 4089 4090 4091 4093 4094 4095 4096 4098 4099 4101 4102 4103 4104 4105 4106 4108 4109 4110 4111 4113 4114 4116 4117 4118 4119 4120 4122 4123 4124 4126 4129 4130 END 4132 9.2. RDE Domain Object 4134 Copyright (c) 2011 IETF Trust and the persons identified as authors 4135 of the code. All rights reserved. 4137 Redistribution and use in source and binary forms, with or without 4138 modification, are permitted provided that the following conditions 4139 are met: 4141 o Redistributions of source code must retain the above copyright 4142 notice, this list of conditions and the following disclaimer. 4144 o Redistributions in binary form must reproduce the above copyright 4145 notice, this list of conditions and the following disclaimer in 4146 the documentation and/or other materials provided with the 4147 distribution. 4149 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4150 names of specific contributors, may be used to endorse or promote 4151 products derived from this software without specific prior written 4152 permission. 4154 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4155 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4156 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4157 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4158 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4159 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4160 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4161 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4162 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4163 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4164 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4166 BEGIN 4167 4168 4179 4180 4181 4182 4183 4184 4186 4187 4188 Registry Data Escrow Domain provisioning schema 4189 4190 4192 4195 4197 4201 4202 4203 4204 4205 4206 4208 4210 4212 4214 4216 4218 4221 4224 4227 4229 4231 4233 4235 4237 4239 4241 4243 4245 4248 4249 4250 4251 4253 4254 4255 4257 4259 4261 4263 4265 4267 4268 4270 4271 4272 4273 4274 4275 4278 4279 4280 4281 4282 4283 END 4285 9.3. CSV Domain Object 4287 Copyright (c) 2012 IETF Trust and the persons identified as authors 4288 of the code. All rights reserved. 4290 Redistribution and use in source and binary forms, with or without 4291 modification, are permitted provided that the following conditions 4292 are met: 4294 o Redistributions of source code must retain the above copyright 4295 notice, this list of conditions and the following disclaimer. 4297 o Redistributions in binary form must reproduce the above copyright 4298 notice, this list of conditions and the following disclaimer in 4299 the documentation and/or other materials provided with the 4300 distribution. 4302 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4303 names of specific contributors, may be used to endorse or promote 4304 products derived from this software without specific prior written 4305 permission. 4307 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4308 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4309 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4310 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4311 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4312 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4313 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4314 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4315 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4316 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4317 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4319 BEGIN 4320 4322 4333 4336 4338 4340 4342 4344 4346 4349 4350 4351 Domain Name Comma-Separated Values (CSV) Object 4352 4353 4355 4358 4361 4362 4363 4364 4365 4366 4367 4369 4370 4372 4375 4378 4379 4380 4381 4382 4383 4384 4385 4386 4388 4389 4392 4393 4396 4397 4398 4399 4400 4402 4403 4404 4406 4407 4410 4411 4412 4413 4414 4416 4417 4418 4420 4422 4423 4425 4426 4427 4428 4429 4431 4432 4433 4435 4436 4439 4440 4443 4444 4447 4448 4451 4452 4455 4456 4459 4460 4463 4464 4466 4467 4468 4469 4470 4472 4473 4474 4476 4477 4480 4481 4485 4486 4489 4490 4491 4492 4493 4494 4496 4497 4498 4500 4503 4504 END 4506 9.4. RDE Host Object 4508 Copyright (c) 2011 IETF Trust and the persons identified as authors 4509 of the code. All rights reserved. 4511 Redistribution and use in source and binary forms, with or without 4512 modification, are permitted provided that the following conditions 4513 are met: 4515 o Redistributions of source code must retain the above copyright 4516 notice, this list of conditions and the following disclaimer. 4518 o Redistributions in binary form must reproduce the above copyright 4519 notice, this list of conditions and the following disclaimer in 4520 the documentation and/or other materials provided with the 4521 distribution. 4523 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4524 names of specific contributors, may be used to endorse or promote 4525 products derived from this software without specific prior written 4526 permission. 4528 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4529 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4530 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4531 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4532 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4533 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4534 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4535 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4536 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4537 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4538 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4540 BEGIN 4541 4542 4550 4551 4552 4554 4555 4556 Registry Data Escrow Host provisioning schema 4557 4558 4559 4561 4562 4565 4566 4567 4568 4569 4570 4572 4574 4576 4579 4581 4583 4585 4587 4589 4591 4592 4593 4594 4596 4597 4598 4599 4600 4601 4603 4605 4606 4608 4609 4610 4611 END 4613 9.5. CSV Host Object 4615 Copyright (c) 2012 IETF Trust and the persons identified as authors 4616 of the code. All rights reserved. 4618 Redistribution and use in source and binary forms, with or without 4619 modification, are permitted provided that the following conditions 4620 are met: 4622 o Redistributions of source code must retain the above copyright 4623 notice, this list of conditions and the following disclaimer. 4625 o Redistributions in binary form must reproduce the above copyright 4626 notice, this list of conditions and the following disclaimer in 4627 the documentation and/or other materials provided with the 4628 distribution. 4630 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4631 names of specific contributors, may be used to endorse or promote 4632 products derived from this software without specific prior written 4633 permission. 4635 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4636 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4637 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4638 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4639 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4640 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4641 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4642 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4643 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4644 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4645 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4647 BEGIN 4648 4650 4659 4662 4664 4666 4668 4671 4672 4673 Host Comma-Separated Values (CSV) Object 4674 4675 4677 4680 4683 4684 4685 4686 4687 4688 4689 4690 4691 4693 4696 4699 4700 4701 4702 4703 4705 4706 4707 4708 4710 4711 4714 4715 4717 4718 4719 4720 4721 4723 4724 4725 4727 4728 4730 4731 4732 4733 4734 4736 4737 4738 4740 4741 4744 4745 4746 4747 4748 4749 4752 4753 4754 4756 4759 4760 END 4762 9.6. RDE Contact Object 4764 Copyright (c) 2011 IETF Trust and the persons identified as authors 4765 of the code. All rights reserved. 4767 Redistribution and use in source and binary forms, with or without 4768 modification, are permitted provided that the following conditions 4769 are met: 4771 o Redistributions of source code must retain the above copyright 4772 notice, this list of conditions and the following disclaimer. 4774 o Redistributions in binary form must reproduce the above copyright 4775 notice, this list of conditions and the following disclaimer in 4776 the documentation and/or other materials provided with the 4777 distribution. 4779 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4780 names of specific contributors, may be used to endorse or promote 4781 products derived from this software without specific prior written 4782 permission. 4784 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4785 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4786 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4787 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4788 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4789 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4790 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4791 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4792 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4793 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4794 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4796 BEGIN 4797 4798 4806 4807 4808 4809 4811 4812 4813 Registry Data Escrow contact provisioning schema 4814 4815 4817 4820 4822 4826 4827 4828 4829 4830 4831 4833 4835 4837 4839 4841 4843 4845 4847 4849 4851 4853 4855 4857 4859 4861 4862 4863 4864 4866 4867 4868 4869 4870 4871 4872 4873 4874 4876 4877 4878 4879 4880 4881 4884 4885 4886 4887 4888 4889 END 4891 9.7. CSV Contact Object 4893 Copyright (c) 2012 IETF Trust and the persons identified as authors 4894 of the code. All rights reserved. 4896 Redistribution and use in source and binary forms, with or without 4897 modification, are permitted provided that the following conditions 4898 are met: 4900 o Redistributions of source code must retain the above copyright 4901 notice, this list of conditions and the following disclaimer. 4903 o Redistributions in binary form must reproduce the above copyright 4904 notice, this list of conditions and the following disclaimer in 4905 the documentation and/or other materials provided with the 4906 distribution. 4908 o Neither the name of Internet Society, IETF or IETF Trust, nor the 4909 names of specific contributors, may be used to endorse or promote 4910 products derived from this software without specific prior written 4911 permission. 4913 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 4914 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 4915 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 4916 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 4917 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4918 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4919 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 4920 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 4921 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 4922 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 4923 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 4925 BEGIN 4926 4928 4937 4941 4943 4945 4947 4950 4951 4952 Contact Comma-Separated Values (CSV) Object 4953 4954 4956 4959 4962 4963 4964 4965 4966 4967 4968 4969 4970 4972 4975 4978 4979 4980 4981 4982 4983 4984 4985 4986 4988 4989 4991 4992 4993 4994 4995 4997 4998 4999 5001 5002 5006 5007 5009 5011 5012 5013 5014 5015 5017 5018 5019 5021 5022 5024 5027 5028 5030 5031 5032 5033 5034 5036 5037 5038 5040 5044 5046 5047 5048 5049 5050 5052 5053 5054 5056 5057 5058 5059 5060 5061 5063 5064 5065 5066 5068 5069 5070 5071 5072 5073 5075 5076 5077 5078 5079 5080 5083 5084 5087 5088 5089 5091 5092 5093 5094 5095 5097 5098 5099 5101 5102 5105 5106 5109 5110 5112 5113 5114 5115 5116 5118 5119 5120 5121 5123 5124 5126 5127 5128 5129 5130 5132 5133 5134 5135 5137 5138 5140 5142 5144 5146 5148 5150 5152 5154 5156 5158 5160 5162 5164 5166 5168 5170 5172 5174 5176 5178 5179 5180 5181 5182 5184 5185 5186 5188 5189 5192 5193 5194 5195 5196 5197 5199 5200 5201 5203 5206 5207 END 5209 9.8. RDE Registrar Object 5211 Copyright (c) 2011 IETF Trust and the persons identified as authors 5212 of the code. All rights reserved. 5214 Redistribution and use in source and binary forms, with or without 5215 modification, are permitted provided that the following conditions 5216 are met: 5218 o Redistributions of source code must retain the above copyright 5219 notice, this list of conditions and the following disclaimer. 5221 o Redistributions in binary form must reproduce the above copyright 5222 notice, this list of conditions and the following disclaimer in 5223 the documentation and/or other materials provided with the 5224 distribution. 5226 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5227 names of specific contributors, may be used to endorse or promote 5228 products derived from this software without specific prior written 5229 permission. 5231 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5232 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5233 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5234 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5235 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5236 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5237 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5238 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5239 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5240 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5241 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5243 BEGIN 5244 5245 5254 5255 5256 5257 5258 5260 5261 5262 Registry Data Escrow registrar provisioning schema 5263 5264 5266 5270 5272 5275 5276 5277 5278 5279 5280 5282 5284 5286 5288 5291 5293 5295 5297 5299 5301 5303 5305 5306 5307 5308 5310 5311 5312 5313 5314 5315 5317 5318 5319 5320 5321 5322 5323 5325 5326 5327 5329 5330 5333 5335 5336 5337 5338 5339 5340 5342 5343 5344 5347 5349 5352 5354 5356 5357 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5371 5372 5373 5374 5375 5377 5378 5379 5380 5381 5383 5384 5385 5387 5389 5390 5392 5393 5394 5395 5396 5397 5400 5401 5402 5403 5404 5405 END 5407 9.9. CSV Registrar Object 5409 Copyright (c) 2012 IETF Trust and the persons identified as authors 5410 of the code. All rights reserved. 5412 Redistribution and use in source and binary forms, with or without 5413 modification, are permitted provided that the following conditions 5414 are met: 5416 o Redistributions of source code must retain the above copyright 5417 notice, this list of conditions and the following disclaimer. 5419 o Redistributions in binary form must reproduce the above copyright 5420 notice, this list of conditions and the following disclaimer in 5421 the documentation and/or other materials provided with the 5422 distribution. 5424 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5425 names of specific contributors, may be used to endorse or promote 5426 products derived from this software without specific prior written 5427 permission. 5429 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5430 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5431 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5432 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5433 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5434 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5435 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5436 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5437 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5438 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5439 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5441 BEGIN 5442 5444 5454 5457 5459 5461 5463 5465 5468 5469 5470 Registar Comma-Separated Values (CSV) Object 5471 5472 5474 5477 5480 5481 5482 5483 5484 5485 5486 5487 5488 5490 5493 5496 5497 5498 5499 5500 5501 5502 5503 5504 5506 5507 5510 5511 5514 5515 5516 5517 5518 5519 5521 5522 5523 5524 5526 5527 5531 5532 5534 5536 5537 5538 5539 5540 5542 5543 5544 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557 5558 5559 5560 5561 5563 5564 5568 5571 5572 END 5574 9.10. RDE IDN Table Reference Objects 5576 Copyright (c) 2011 IETF Trust and the persons identified as authors 5577 of the code. All rights reserved. 5579 Redistribution and use in source and binary forms, with or without 5580 modification, are permitted provided that the following conditions 5581 are met: 5583 o Redistributions of source code must retain the above copyright 5584 notice, this list of conditions and the following disclaimer. 5586 o Redistributions in binary form must reproduce the above copyright 5587 notice, this list of conditions and the following disclaimer in 5588 the documentation and/or other materials provided with the 5589 distribution. 5591 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5592 names of specific contributors, may be used to endorse or promote 5593 products derived from this software without specific prior written 5594 permission. 5596 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5597 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5598 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5599 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5600 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5601 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5602 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5603 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5604 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5605 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5606 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5608 BEGIN 5609 5610 5616 5618 5619 5620 Registry Data Escrow IDN provisioning schema 5621 5622 5624 5626 5629 5630 5631 5632 5633 5634 5635 5636 5637 5638 5639 5640 5642 5643 5644 5645 5646 5647 5648 5650 5651 5653 5654 5655 5656 5657 5658 5659 5661 5662 END 5664 9.11. CSV IDN Language Object 5666 Copyright (c) 2012 IETF Trust and the persons identified as authors 5667 of the code. All rights reserved. 5669 Redistribution and use in source and binary forms, with or without 5670 modification, are permitted provided that the following conditions 5671 are met: 5673 o Redistributions of source code must retain the above copyright 5674 notice, this list of conditions and the following disclaimer. 5676 o Redistributions in binary form must reproduce the above copyright 5677 notice, this list of conditions and the following disclaimer in 5678 the documentation and/or other materials provided with the 5679 distribution. 5681 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5682 names of specific contributors, may be used to endorse or promote 5683 products derived from this software without specific prior written 5684 permission. 5686 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5687 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5688 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5689 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5690 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5691 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5692 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5693 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5694 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5695 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5696 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5698 BEGIN 5699 5701 5708 5711 5713 5716 5717 5718 IDN Language Comma-Separated Values (CSV) Object 5719 5720 5722 5725 5728 5729 5730 5731 5732 5733 5734 5735 5736 5738 5741 5744 5745 5746 5747 5748 5749 5750 5751 5752 5754 5757 5758 END 5760 9.12. EPP Parameters Object 5762 Copyright (c) 2011 IETF Trust and the persons identified as authors 5763 of the code. All rights reserved. 5765 Redistribution and use in source and binary forms, with or without 5766 modification, are permitted provided that the following conditions 5767 are met: 5769 o Redistributions of source code must retain the above copyright 5770 notice, this list of conditions and the following disclaimer. 5772 o Redistributions in binary form must reproduce the above copyright 5773 notice, this list of conditions and the following disclaimer in 5774 the documentation and/or other materials provided with the 5775 distribution. 5777 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5778 names of specific contributors, may be used to endorse or promote 5779 products derived from this software without specific prior written 5780 permission. 5782 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5783 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5784 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5785 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5786 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5787 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5788 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5789 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5790 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5791 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5792 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5794 BEGIN 5795 5796 5804 5805 5806 5808 5809 5810 Registry Data Escrow EPP Parameters schema 5811 5812 5814 5815 5818 5819 5822 5823 5824 5825 5826 5828 5830 5832 5835 5837 5838 5839 5840 5841 5842 END 5844 9.13. NNDN Object 5846 Copyright (c) 2011 IETF Trust and the persons identified as authors 5847 of the code. All rights reserved. 5849 Redistribution and use in source and binary forms, with or without 5850 modification, are permitted provided that the following conditions 5851 are met: 5853 o Redistributions of source code must retain the above copyright 5854 notice, this list of conditions and the following disclaimer. 5856 o Redistributions in binary form must reproduce the above copyright 5857 notice, this list of conditions and the following disclaimer in 5858 the documentation and/or other materials provided with the 5859 distribution. 5861 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5862 names of specific contributors, may be used to endorse or promote 5863 products derived from this software without specific prior written 5864 permission. 5866 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5867 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5868 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5869 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5870 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5871 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5872 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5873 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5874 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5875 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5876 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5878 BEGIN 5879 5880 5888 5889 5890 5892 5893 5894 Registry Data Escrow NNDN provisioning schema 5895 5896 5898 5900 5901 5904 5905 5906 5907 5908 5909 5911 5913 5915 5917 5919 5921 5922 5923 5924 5926 5927 5928 5929 5930 5931 5932 5934 5935 5936 5937 5939 5940 5941 5943 5944 5945 5946 5947 5948 5951 5952 5953 5954 5955 5956 END 5958 9.14. CSV NNDN Object 5960 Copyright (c) 2013 IETF Trust and the persons identified as authors 5961 of the code. All rights reserved. 5963 Redistribution and use in source and binary forms, with or without 5964 modification, are permitted provided that the following conditions 5965 are met: 5967 o Redistributions of source code must retain the above copyright 5968 notice, this list of conditions and the following disclaimer. 5970 o Redistributions in binary form must reproduce the above copyright 5971 notice, this list of conditions and the following disclaimer in 5972 the documentation and/or other materials provided with the 5973 distribution. 5975 o Neither the name of Internet Society, IETF or IETF Trust, nor the 5976 names of specific contributors, may be used to endorse or promote 5977 products derived from this software without specific prior written 5978 permission. 5980 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 5981 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 5982 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 5983 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 5984 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 5985 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 5986 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 5987 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 5988 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 5989 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 5990 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5992 BEGIN 5993 5995 6003 6006 6008 6010 6013 6014 6015 NNDN (NNDN's not domain name) (CSV) Object 6016 6017 6019 6022 6025 6026 6027 6028 6029 6030 6031 6032 6033 6034 6037 6040 6041 6042 6043 6044 6045 6046 6047 6048 6050 6051 6054 6055 6058 6059 6063 6064 6067 6068 6069 6070 6071 6073 6074 6075 6077 6078 6081 6084 6085 END 6087 9.15. Policy Object 6089 Copyright (c) 2011 IETF Trust and the persons identified as authors 6090 of the code. All rights reserved. 6092 Redistribution and use in source and binary forms, with or without 6093 modification, are permitted provided that the following conditions 6094 are met: 6096 o Redistributions of source code must retain the above copyright 6097 notice, this list of conditions and the following disclaimer. 6099 o Redistributions in binary form must reproduce the above copyright 6100 notice, this list of conditions and the following disclaimer in 6101 the documentation and/or other materials provided with the 6102 distribution. 6104 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6105 names of specific contributors, may be used to endorse or promote 6106 products derived from this software without specific prior written 6107 permission. 6109 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6110 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6111 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6112 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6113 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6114 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6115 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6116 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6117 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6118 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6119 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6121 BEGIN 6122 6123 6129 6130 6131 Registry Data Escrow Policy schema 6132 6133 6135 6136 6139 6140 6141 6142 6143 6144 6145 6146 6147 6148 END 6150 9.16. Header Object 6152 Copyright (c) 2011 IETF Trust and the persons identified as authors 6153 of the code. All rights reserved. 6155 Redistribution and use in source and binary forms, with or without 6156 modification, are permitted provided that the following conditions 6157 are met: 6159 o Redistributions of source code must retain the above copyright 6160 notice, this list of conditions and the following disclaimer. 6162 o Redistributions in binary form must reproduce the above copyright 6163 notice, this list of conditions and the following disclaimer in 6164 the documentation and/or other materials provided with the 6165 distribution. 6167 o Neither the name of Internet Society, IETF or IETF Trust, nor the 6168 names of specific contributors, may be used to endorse or promote 6169 products derived from this software without specific prior written 6170 permission. 6172 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 6173 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 6174 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 6175 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 6176 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 6177 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 6178 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 6179 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 6180 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 6181 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 6182 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 6184 BEGIN 6185 6186 6193 6194 6196 6197 6198 Data Escrow Deposit Header schema 6199 6200 6202 6203 6206 6207 6208 6209 6210 6211 6212 6214 6215 6216 6218 6220 6221 6222 6223 6224 6225 6226 6228 6229 6230 6231 6232 6233 6234 6235 6236 6238 6239 END 6241 10. Internationalization Considerations 6243 Data Escrow deposits are represented in XML, which provides native 6244 support for encoding information using the Unicode character set and 6245 its more compact representations including UTF-8. Conformant XML 6246 processors recognize both UTF-8 and UTF-16. Though XML includes 6247 provisions to identify and use other character encodings through use 6248 of an "encoding" attribute in an declaration, use of UTF-8 is 6249 RECOMMENDED. 6251 11. IANA Considerations 6253 This document uses URNs to describe XML namespaces and XML schemas 6254 conforming to a registry mechanism described in [RFC3688]. Fourteen 6255 URI assignments have been registered by the IANA. 6257 Registration request for the RDE CSV namespace: 6259 URI: urn:ietf:params:xml:ns:rdeCsv-1.0 6261 Registrant Contact: See the "Author's Address" section of this 6262 document. 6264 XML: None. Namespace URIs do not represent an XML specification. 6266 Registration request for the RDE CSV XML schema: 6268 URI: urn:ietf:params:xml:schema:rdeCsv-1.0 6270 Registrant Contact: See the "Author's Address" section of this 6271 document. 6273 See the "Formal Syntax" section of this document. 6275 Registration request for the RDE domain namespace: 6277 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 6279 Registrant Contact: See the "Author's Address" section of this 6280 document. 6282 XML: None. Namespace URIs do not represent an XML specification. 6284 Registration request for the RDE domain XML schema: 6286 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 6288 Registrant Contact: See the "Author's Address" section of this 6289 document. 6291 See the "Formal Syntax" section of this document. 6293 Registration request for the CSV domain namespace: 6295 URI: urn:ietf:params:xml:ns:csvDomain-1.0 6297 Registrant Contact: See the "Author's Address" section of this 6298 document. 6300 XML: None. Namespace URIs do not represent an XML specification. 6302 Registration request for the CSV domain XML schema: 6304 URI: urn:ietf:params:xml:schema:csvDomain-1.0 6306 Registrant Contact: See the "Author's Address" section of this 6307 document. 6309 See the "Formal Syntax" section of this document. 6311 Registration request for the RDE host namespace: 6313 URI: urn:ietf:params:xml:ns:rdeHost-1.0 6314 Registrant Contact: See the "Author's Address" section of this 6315 document. 6317 XML: None. Namespace URIs do not represent an XML specification. 6319 Registration request for the RDE host XML schema: 6321 URI: urn:ietf:params:xml:schema:rdeHost-1.0 6323 Registrant Contact: See the "Author's Address" section of this 6324 document. 6326 See the "Formal Syntax" section of this document. 6328 Registration request for the CSV host namespace: 6330 URI: urn:ietf:params:xml:ns:csvHost-1.0 6332 Registrant Contact: See the "Author's Address" section of this 6333 document. 6335 XML: None. Namespace URIs do not represent an XML specification. 6337 Registration request for the CSV host XML schema: 6339 URI: urn:ietf:params:xml:schema:csvHost-1.0 6341 Registrant Contact: See the "Author's Address" section of this 6342 document. 6344 See the "Formal Syntax" section of this document. 6346 Registration request for the RDE contact namespace: 6348 URI: urn:ietf:params:xml:ns:rdeContact-1.0 6350 Registrant Contact: See the "Author's Address" section of this 6351 document. 6353 XML: None. Namespace URIs do not represent an XML specification. 6355 Registration request for the RDE contact XML schema: 6357 URI: urn:ietf:params:xml:schema:rdeContact-1.0 6359 Registrant Contact: See the "Author's Address" section of this 6360 document. 6362 See the "Formal Syntax" section of this document. 6364 Registration request for the CSV contact namespace: 6366 URI: urn:ietf:params:xml:ns:csvContact-1.0 6368 Registrant Contact: See the "Author's Address" section of this 6369 document. 6371 XML: None. Namespace URIs do not represent an XML specification. 6373 Registration request for the CSV contact XML schema: 6375 URI: urn:ietf:params:xml:schema:csvContact-1.0 6377 Registrant Contact: See the "Author's Address" section of this 6378 document. 6380 See the "Formal Syntax" section of this document. 6382 Registration request for the RDE registrar namespace: 6384 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 6386 Registrant Contact: See the "Author's Address" section of this 6387 document. 6389 XML: None. Namespace URIs do not represent an XML specification. 6391 Registration request for the RDE registrar XML schema: 6393 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 6395 Registrant Contact: See the "Author's Address" section of this 6396 document. 6398 See the "Formal Syntax" section of this document. 6400 Registration request for the CSV registrar namespace: 6402 URI: urn:ietf:params:xml:ns:csvRegistrar-1.0 6404 Registrant Contact: See the "Author's Address" section of this 6405 document. 6407 XML: None. Namespace URIs do not represent an XML specification. 6409 Registration request for the CSV registrar XML schema: 6411 URI: urn:ietf:params:xml:schema:csvRegistrar-1.0 6413 Registrant Contact: See the "Author's Address" section of this 6414 document. 6416 See the "Formal Syntax" section of this document. 6418 Registration request for the RDE IDN namespace: 6420 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 6422 Registrant Contact: See the "Author's Address" section of this 6423 document. 6425 XML: None. Namespace URIs do not represent an XML specification. 6427 Registration request for the RDE IDN XML schema: 6429 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 6431 Registrant Contact: See the "Author's Address" section of this 6432 document. 6434 See the "Formal Syntax" section of this document. 6436 Registration request for the CSV IDN namespace: 6438 URI: urn:ietf:params:xml:ns:csvIDN-1.0 6440 Registrant Contact: See the "Author's Address" section of this 6441 document. 6443 XML: None. Namespace URIs do not represent an XML specification. 6445 Registration request for the CSV IDN XML schema: 6447 URI: urn:ietf:params:xml:schema:csvIDN-1.0 6449 Registrant Contact: See the "Author's Address" section of this 6450 document. 6452 See the "Formal Syntax" section of this document. 6454 Registration request for the RDE NNDN namespace: 6456 URI: urn:ietf:params:xml:ns:rdeNNDN-1.0 6457 Registrant Contact: See the "Author's Address" section of this 6458 document. 6460 XML: None. Namespace URIs do not represent an XML specification. 6462 Registration request for the RDE NNDN XML schema: 6464 URI: urn:ietf:params:xml:schema:rdeNNDN-1.0 6466 Registrant Contact: See the "Author's Address" section of this 6467 document. 6469 See the "Formal Syntax" section of this document. 6471 Registration request for the CSV NNDN namespace: 6473 URI: urn:ietf:params:xml:ns:csvNNDN-1.0 6475 Registrant Contact: See the "Author's Address" section of this 6476 document. 6478 XML: None. Namespace URIs do not represent an XML specification. 6480 Registration request for the CSV NNDN XML schema: 6482 URI: urn:ietf:params:xml:schema:csvNNDN-1.0 6484 Registrant Contact: See the "Author's Address" section of this 6485 document. 6487 See the "Formal Syntax" section of this document. 6489 Registration request for the RDE EPP parameters namespace: 6491 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 6493 Registrant Contact: See the "Author's Address" section of this 6494 document. 6496 XML: None. Namespace URIs do not represent an XML specification. 6498 Registration request for the RDE EPP parameters XML schema: 6500 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 6502 Registrant Contact: See the "Author's Address" section of this 6503 document. 6505 See the "Formal Syntax" section of this document. 6507 12. Security Considerations 6509 This specification does not define the security mechanisms to be used 6510 in the transmission of the data escrow deposits, since it only 6511 specifies the minimum necessary to enable the rebuilding of a 6512 Registry from deposits without intervention from the original 6513 Registry. 6515 Depending on local policies, some elements or most likely, the whole 6516 deposit will be considered confidential. As such the Registry 6517 transmitting the data to the Escrow Agent SHOULD take all the 6518 necessary precautions like encrypting the data itself and/or the 6519 transport channel to avoid inadvertent disclosure of private data. 6521 It is also of the utmost importance the authentication of the parties 6522 passing data escrow deposit files. The Escrow Agent SHOULD properly 6523 authenticate the identity of the Registry before accepting data 6524 escrow deposits. In a similar manner, the Registry SHOULD 6525 authenticate the identity of the Escrow Agent before submitting any 6526 data. 6528 Additionally, the Registry and the Escrow Agent SHOULD use integrity 6529 checking mechanisms to ensure the data transmitted is what the source 6530 intended. Validation of the contents by the Escrow Agent is 6531 RECOMMENDED to ensure not only the file was transmitted correctly 6532 from the Registry, but also the contents are also "meaningful". 6534 13. Acknowledgments 6536 Parts of this document are based on EPP [RFC5730] and related RFCs by 6537 Scott Hollenbeck. 6539 Shoji Noguchi and Francisco Arias participated as co-authors until 6540 version 05 providing invaluable support for this document. 6542 14. Change History 6544 [[RFC Editor: Please remove this section.]] 6546 14.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to - 6547 dnrd-objects-mapping-00 6549 1. Added definition for child elements under the element. 6551 2. Added definition for child elements under the element. 6553 3. Added definition for child elements under the element. 6555 4. Rewrote the IDN Variants Handling section to use the variant 6556 states as described in ICANN's Study of Issues Related to the 6557 Management of IDN Variant TLDs. 6559 5. Renamed to in the . 6561 6. Renamed to in the element. 6563 7. Renamed to in the element. 6565 8. Added element under element. 6567 9. Fixed some typographical errors and omissions. 6569 14.2. Changes from version 00 to 01 6571 1. Specify OPTIONAL elements in the draft. 6573 2. Added NNDN object to support list of reserved names and different 6574 IDN variants models. 6576 3. Removed subordinated host element from the domain object. 6578 4. Added eppParams object. 6580 5. Added variantGenerator element to the domain object. 6582 6. Added lgr to the IDN table object. 6584 14.3. Changes from version 01 to 02 6586 1. Updates to the all objects based on feedback from the list. 6588 2. Start of XML and CSV drafts merge. 6590 3. Added header object. 6592 4. Added report object. 6594 5. Added notification object. 6596 6. Added Data Escrow Agent Extended Verification Process section. 6598 7. Added Notifications from Registries to Third Parties. 6600 8. Added Notifications from Data Escrow Agents to Third Parties. 6602 9. Added FULL, DIFF deposit examples using the XML model only. 6604 14.4. Changes from version 02 to 03 6606 1. Remove authinfo from the XML Schema. 6608 2. Resend attribute is now an element 6610 3. Scope attribute added to policy object. 6612 14.5. Changes from version 03 to 04 6614 1. Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 into draft- 6615 arias-noguchi-dnrd-objects-mapping-02. 6617 2. Changed the cksum attribute of to use CRC32 and 6618 changed all of the sample cksum values to use CRC32, based on 6619 feedback from David Kipling. 6621 3. Changed the optional element to be an optional 6622 "sep" attribute value of the element with a default 6623 value of "," based on feedback from David Kipling. 6625 4. Added support for the optional "parent" attribute for the to the 6626 CSV fields to indicate a field as a reference to a parent 6627 object, based on feedback from David Kipling. 6629 5. Added support for the CSV model for the NNDN. 6631 6. Added support to delete hosts based on roid. 6633 7. Added mirrored state to NNDN 6635 8. Minor fixes to XML XSDs. 6637 9. The Report and Notification objects were moved to draft-lozano- 6638 icann-registry-interfaces 6640 10. The section Data escrow notifications was moved to draft-lozano- 6641 icann-registry-interfaces 6643 11. Removed references to the , , and 6644 from the "hostStatuses" and "hostAddresses" CSV 6645 files. 6647 12. Removed references to the , , and 6648 from the "contactStatuses" CSV file. 6650 13. Removed references to the , , and 6651 from the "domainContacts", "domainStatuses", 6652 and "domainNameServers" CSV files. 6654 14. Changed to . 6656 15. Replaced use of to new field 6657 in the "domain", "idnLanguage", and "NNDN" CSV files. 6659 16. Replaced use of with in the 6660 "host" element. 6662 17. Changed the foreign key of the hosts to use 6663 instead of and removed use of in 6664 the "domainNameServers", "hostStatuses", and "hostAddresses" CSV 6665 files. 6667 18. Added use of the MUST keyword for CSV fields that are required 6668 to be supported in an EPP based system. 6670 19. Removed use of the field element for the 6671 "registrar" CSV file. 6673 20. Added definition of field element. 6675 14.6. Changes from version 04 to 05 6677 1. Updated the examples of the full and differential deposits using 6678 the CSV and XML model. 6680 2. Made optional for the "domainTransfer" CSV file 6681 to match the XML definition. 6683 3. Made optional for the "domain" CSV file 6684 to match the XML definition. 6686 4. Made optional for the "domain" and "contact" CSV 6687 files to match the XML definition. 6689 5. Change from IDREF to idType. 6691 6. Minor editorial changes. 6693 14.7. Changes from version 05 to 06 6695 1. Revised the differential and incremental deposits for the CSV 6696 format to use cascade update / replace and delete from the parent 6697 object to be consistent with the XML format. 6699 2. Revised the structure of the CSV format sections to utilize sub- 6700 sections instead of a list for the CSV file definitions. 6702 3. Added the "CSV Parent Child Relationship" section to describe the 6703 concept of parent child relationships across CSV file 6704 definitions. 6706 4. Added the "domainNameServersAddresses" CSV File Definition 6707 section to support the domain host attributes model of [RFC5731]. 6709 5. Made the required fields in the CSV format consistent with the 6710 XML format. The CSV fields updated to be required include: 6711 , , , 6712 , , , 6713 , , , 6714 , , , 6715 , , 6716 , , , 6717 , , 6718 , and . 6720 6. Revised the CSV examples to use a more realistic set of records. 6722 14.8. Changes from version 06 to 07 6724 1. Created "repositoryTypeGroup" group element in the rdeHeader 6725 including the , and 6726 elements. 6728 2. Added the optional "rcdn" and "registrarId" attributes to the 6729 element 6731 14.9. Changes from version 07 to 08 6733 1. The following registrar elements were made optional to support 6734 greater flexibility for the implementation of policies: status, 6735 postalInfo, email and crDate. 6737 2. The following domain name elements were made optional to support 6738 greater flexibility for the implementation of policies: crRr. 6740 15. Example of a full deposit using the XML model 6742 Example of a full deposit using the XML model: 6744 6745 6761 2010-10-17T00:00:00Z 6762 6763 1.0 6764 urn:ietf:params:xml:ns:rdeHeader-1.0 6765 6766 urn:ietf:params:xml:ns:rdeContact-1.0 6767 6768 urn:ietf:params:xml:ns:rdeHost-1.0 6769 6770 urn:ietf:params:xml:ns:rdeDomain-1.0 6771 6772 urn:ietf:params:xml:ns:rdeRegistrar-1.0 6773 6774 urn:ietf:params:xml:ns:rdeIDN-1.0 6775 6776 urn:ietf:params:xml:ns:rdeNNDN-1.0 6777 6778 urn:ietf:params:xml:ns:rdeEppParams-1.0 6779 6780 6782 6783 6784 6785 6786 test 6787 2 6789 6790 1 6792 6793 1 6795 6796 1 6798 6799 1 6801 6802 1 6804 6805 1 6807 6808 6810 6811 6812 example1.test 6813 Dexample1-TEST 6814 6815 jd1234 6816 sh8013 6817 sh8013 6818 6819 ns1.example.com 6820 ns1.example1.test 6821 6822 RegistrarX 6823 RegistrarX 6824 1999-04-03T22:00:00.0Z 6825 2015-04-03T22:00:00.0Z 6826 6828 6829 6830 example2.test 6831 Dexample2-TEST 6832 6833 6834 jd1234 6835 sh8013 6836 sh8013 6837 RegistrarX 6838 RegistrarX 6839 1999-04-03T22:00:00.0Z 6840 2015-04-03T22:00:00.0Z 6841 6842 6843 6844 ns1.example1.test 6845 Hns1_example_test-TEST 6846 6847 6848 192.0.2.2 6849 192.0.2.29 6850 1080:0:0:0:8:800:200C:417A 6851 6852 RegistrarX 6853 RegistrarX 6854 1999-05-08T12:10:00.0Z 6855 RegistrarX 6856 2009-10-03T09:34:00.0Z 6857 6859 6860 6861 sh8013 6862 Csh8013-TEST 6863 6864 6865 6866 John Doe 6867 Example Inc. 6868 6869 123 Example Dr. 6870 Suite 100 6871 Dulles 6872 VA 6873 20166-6503 6874 US 6875 6876 6877 +1.7035555555 6878 6879 +1.7035555556 6880 6881 jdoe@example.test 6882 6883 RegistrarX 6884 RegistrarX 6885 6886 2009-09-13T08:01:00.0Z 6887 6888 RegistrarX 6889 6890 2009-11-26T09:10:00.0Z 6891 6892 2009-12-03T09:05:00.0Z 6893 6894 6895 6896 6897 6898 6900 6901 6902 RegistrarX 6903 Registrar X 6904 123 6905 ok 6906 6907 6908 123 Example Dr. 6909 6910 Suite 100 6911 6912 Dulles 6913 VA 6914 20166-6503 6915 US 6916 6917 6918 +1.7035555555 6919 6920 +1.7035555556 6921 6922 jdoe@example.test 6923 6924 http://www.example.test 6925 6926 6927 whois.example.test 6928 6929 http://whois.example.test 6930 6931 6932 2005-04-23T11:49:00.0Z 6933 6934 2009-02-17T17:51:00.0Z 6935 6936 6937 6938 6939 6940 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 6941 6942 6943 http://registro.br/dominio/regras.html 6944 6945 6947 6948 6949 xn--exampl-gva.test 6950 pt-BR 6951 example1.test 6952 withheld 6953 2005-04-23T11:49:00.0Z 6954 6956 6957 6958 1.0 6959 en 6960 6961 urn:ietf:params:xml:ns:domain-1.0 6962 6963 6964 urn:ietf:params:xml:ns:contact-1.0 6965 6966 6967 urn:ietf:params:xml:ns:host-1.0 6968 6969 6970 urn:ietf:params:xml:ns:rgp-1.0 6971 6972 urn:ietf:params:xml:ns:secDNS-1.1 6973 6974 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6986 6987 6988 6989 6990 6991 6992 6993 6996 6997 6999 16. Example of differential deposit using the XML model 7001 Example of a differential deposit using the XML model: 7003 7004 7019 2010-10-17T00:00:00Z 7020 7021 1.0 7022 urn:ietf:params:xml:ns:rdeHeader-1.0 7023 7024 urn:ietf:params:xml:ns:rdeContact-1.0 7025 7026 urn:ietf:params:xml:ns:rdeHost-1.0 7027 7028 urn:ietf:params:xml:ns:rdeDomain-1.0 7029 7030 urn:ietf:params:xml:ns:rdeRegistrar-1.0 7031 7032 urn:ietf:params:xml:ns:rdeIDN-1.0 7033 7034 urn:ietf:params:xml:ns:rdeNNDN-1.0 7035 7036 urn:ietf:params:xml:ns:rdeEppParams-1.0 7037 7038 7040 7041 7042 7043 example2.test 7044 7045 7047 7048 7049 7050 7051 test 7052 1 7054 7055 1 7057 7058 1 7060 7061 1 7063 7064 1 7066 7067 1 7069 7070 1 7072 7073 7074 7075 7077 17. Example of a full deposit using the CSV model 7079 Example of a full deposit using the CSV model: 7081 7082 7096 2010-10-18T00:00:00Z 7097 7098 1.0 7099 urn:ietf:params:xml:ns:csvDomain-1.0 7100 urn:ietf:params:xml:ns:csvHost-1.0 7101 urn:ietf:params:xml:ns:csvContact-1.0 7102 urn:ietf:params:xml:ns:csvRegistrar-1.0 7103 urn:ietf:params:xml:ns:csvIDN-1.0 7104 urn:ietf:params:xml:ns:csvNNDN-1.0 7105 urn:ietf:params:xml:ns:rdeEppParams-1.0 7106 7107 7108 7109 test 7110 7111 4 7112 7113 7114 6 7115 7116 7117 9 7118 7119 7120 3 7121 7122 7123 2 7124 7125 7126 2 7127 7128 7129 1 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7152 domain-YYYYMMDD.csv 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7165 domainContacts-YYYYMMDD.csv 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7180 domainStatuses-YYYYMMDD.csv 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7192 domainNameServers-name-YYYYMMDD.csv 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7204 domainNameServers-roid-YYYYMMDD.csv 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7220 dnssec-ds-YYYYMMDD.csv 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7236 dnssec-key-YYYYMMDD.csv 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7255 domainTransfer-YYYYMMDD.csv 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7277 host-YYYYMMDD.csv 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7291 hostStatuses-YYYYMMDD.csv 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7304 hostAddresses-YYYYMMDD.csv 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7330 contact-YYYYMMDD.csv 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7344 contactStatuses-YYYYMMDD.csv 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7365 contactPostal-YYYYMMDD.csv 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7383 contactTransfer-YYYYMMDD.csv 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7404 contactDisclose-YYYYMMDD.csv 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7436 registrar-YYYYMMDD.csv 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7450 idnLanguage-YYYYMMDD.csv 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7468 NNDN-YYYYMMDD.csv 7469 7470 7471 7472 7473 7474 1.0 7475 en 7476 urn:ietf:params:xml:ns:domain-1.0 7477 7478 urn:ietf:params:xml:ns:host-1.0 7479 7480 urn:ietf:params:xml:ns:contact-1.0 7481 7482 7483 urn:ietf:params:xml:ns:secDNS-1.1 7484 7485 urn:ietf:params:xml:ns:rgp-1.0 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7512 18. Example of differential deposit using the CSV model 7514 Example of a differential deposit using the CSV model: 7516 7517 7531 2010-10-18T00:00:00Z 7532 7533 1.0 7534 urn:ietf:params:xml:ns:csvDomain-1.0 7535 urn:ietf:params:xml:ns:csvHost-1.0 7536 urn:ietf:params:xml:ns:csvContact-1.0 7537 urn:ietf:params:xml:ns:csvRegistrar-1.0 7538 urn:ietf:params:xml:ns:csvIDN-1.0 7539 7540 7541 7542 7543 7544 7545 7546 7547 7549 domain-delete-YYYYMMDD.csv 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7562 host-delete-YYYYMMDD.csv 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7575 contact-delete-YYYYMMDD.csv 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7588 registrar-delete-YYYYMMDD.csv 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7601 idnLanguage-delete-YYYYMMDD.csv 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7614 NNDN-delete-YYYYMMDD.csv 7615 7616 7617 7618 7619 7620 7621 7622 test 7623 7624 2 7625 7626 7627 2 7628 7629 7630 3 7631 7632 7633 1 7634 7635 7636 1 7637 7638 7639 1 7640 7641 7642 1 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7665 domain-YYYYMMDD.csv 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7678 domainContacts-YYYYMMDD.csv 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7693 domainStatuses-YYYYMMDD.csv 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7705 domainNameServers-name-YYYYMMDD.csv 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7717 domainNameServers-roid-YYYYMMDD.csv 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7733 dnssec-ds-YYYYMMDD.csv 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7749 dnssec-key-YYYYMMDD.csv 7750 7751 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7769 domainTransfer-YYYYMMDD.csv 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7791 host-YYYYMMDD.csv 7792 7793 7794 7795 7796 7797 7798 7799 7800 7802 7803 7804 7806 hostStatuses-YYYYMMDD.csv 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7819 hostAddresses-YYYYMMDD.csv 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7845 contact-YYYYMMDD.csv 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7859 contactStatuses-YYYYMMDD.csv 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7880 contactPostal-YYYYMMDD.csv 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7898 contactTransfer-YYYYMMDD.csv 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7919 contactDisclose-YYYYMMDD.csv 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7951 registrar-YYYYMMDD.csv 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7965 idnLanguage-YYYYMMDD.csv 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7983 NNDN-YYYYMMDD.csv 7984 7985 7986 7987 7988 7989 1.0 7990 en 7991 urn:ietf:params:xml:ns:domain-1.0 7992 7993 urn:ietf:params:xml:ns:host-1.0 7994 7995 urn:ietf:params:xml:ns:contact-1.0 7996 7997 7998 urn:ietf:params:xml:ns:secDNS-1.1 7999 8000 urn:ietf:params:xml:ns:rgp-1.0 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8027 19. References 8029 19.1. Normative References 8031 [ISO-3166-1] 8032 International Organization for Standardization, "Codes for 8033 the representation of names of countries and their 8034 subdivisions -- Part 1: Country codes", ISO Standard 3166, 8035 November 2006. 8037 [ITU-E164] 8038 International Telecommunication Union, "The international 8039 public telecommunication numbering plan", ITU-T 8040 Recommendation E.164, February 2005. 8042 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8043 Requirement Levels", BCP 14, RFC 2119, 8044 DOI 10.17487/RFC2119, March 1997, 8045 . 8047 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 8048 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 8049 . 8051 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 8052 the Extensible Provisioning Protocol (EPP)", RFC 3915, 8053 DOI 10.17487/RFC3915, September 2004, 8054 . 8056 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 8057 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 8058 . 8060 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8061 Domain Name Mapping", STD 69, RFC 5731, 8062 DOI 10.17487/RFC5731, August 2009, 8063 . 8065 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8066 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 8067 August 2009, . 8069 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 8070 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 8071 August 2009, . 8073 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 8074 Security Extensions Mapping for the Extensible 8075 Provisioning Protocol (EPP)", RFC 5910, 8076 DOI 10.17487/RFC5910, May 2010, 8077 . 8079 19.2. Informative References 8081 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 8082 DOI 10.17487/RFC0791, September 1981, 8083 . 8085 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 8086 DOI 10.17487/RFC3688, January 2004, 8087 . 8089 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 8090 DOI 10.17487/RFC3912, September 2004, 8091 . 8093 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 8094 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 8095 2006, . 8097 [RFC5891] Klensin, J., "Internationalized Domain Names in 8098 Applications (IDNA): Protocol", RFC 5891, 8099 DOI 10.17487/RFC5891, August 2010, 8100 . 8102 [variantTLDsReport] 8103 Internet Corporation for Assigned Names and Numbers 8104 (ICANN), "A Study of Issues Related to the Management of 8105 IDN Variant TLDs", February 2012, 8106 . 8109 19.3. URIs 8111 [1] http://tools.ietf.org/id/draft-arias-noguchi-registry-data- 8112 escrow-05.txt 8114 Authors' Addresses 8116 Gustavo Lozano 8117 Internet Corporation for Assigned Names and Numbers 8118 12025 Waterfront Drive, Suite 300 8119 Los Angeles 90292 8120 United States of America 8122 Phone: +1.310.823.9358 8123 Email: gustavo.lozano@icann.org 8125 James Gould 8126 VeriSign, Inc. 8127 12061 Bluemont Way 8128 Reston 20190 8129 United States of America 8131 Email: jgould@verisign.com 8132 Chethan Thippeswamy 8133 VeriSign, Inc. 8134 12061 Bluemont Way 8135 Reston 20190 8136 United States of America 8138 Email: cthippeswamy@verisign.com