idnits 2.17.1 draft-arias-noguchi-dnrd-objects-mapping-02.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 1 instance 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 (March 12, 2013) is 4057 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) == Unused Reference: 'RFC3743' is defined on line 2919, but no explicit reference was found in the text == Unused Reference: 'RFC4290' is defined on line 2927, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group F. Arias 3 Internet-Draft G. Lozano 4 Intended status: Standards Track ICANN 5 Expires: September 13, 2013 S. Noguchi 6 JPRS 7 J. Gould 8 C. Thippeswamy 9 VeriSign 10 March 12, 2013 12 Domain Name Registration Data (DNRD) Objects Mapping 13 draft-arias-noguchi-dnrd-objects-mapping-02 15 Abstract 17 This document specifies the format, contents and semantics of Domain 18 Name Registration Data (DNRD) Escrow deposits for a Domain Name 19 Registry. It includes the following objects: 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on September 13, 2013. 38 Copyright Notice 40 Copyright (c) 2013 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 2. Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 58 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6 59 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 60 4.2. Country names . . . . . . . . . . . . . . . . . . . . . . 6 61 4.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 6 62 4.4. IP addresses . . . . . . . . . . . . . . . . . . . . . . . 6 63 5. Object Description . . . . . . . . . . . . . . . . . . . . . . 6 64 5.1. RDE Domain object . . . . . . . . . . . . . . . . . . . . 6 65 5.2. RDE Host object . . . . . . . . . . . . . . . . . . . . . 10 66 5.3. RDE Contact object . . . . . . . . . . . . . . . . . . . . 12 67 5.4. RDE Registrar object . . . . . . . . . . . . . . . . . . . 16 68 5.5. RDE IDN Practices . . . . . . . . . . . . . . . . . . . . 19 69 5.6. RDE NNDN . . . . . . . . . . . . . . . . . . . . . . . . . 20 70 5.7. RDE EPP Parameters object . . . . . . . . . . . . . . . . 21 71 5.8. RDE Policy object . . . . . . . . . . . . . . . . . . . . 23 72 5.9. Header object . . . . . . . . . . . . . . . . . . . . . . 23 73 6. RDE IDN Variants handling . . . . . . . . . . . . . . . . . . 24 74 7. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 75 8. Appendix A. Example of a full deposit using the XML model 76 only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 77 9. Appendix B. Example of differential deposit using the XML 78 model only . . . . . . . . . . . . . . . . . . . . . . . . . . 30 79 10. Appendix C. Data escrow agent extended verification process . 31 80 11. Appendix D. Data escrow notifications . . . . . . . . . . . . 32 81 11.1. Notifications from Registry Operators to Third Parties . . 32 82 11.2. Notifications from Data Escrow Agents to Third Parties . . 34 83 11.3. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . 35 84 11.4. Policy Object . . . . . . . . . . . . . . . . . . . . . . 58 85 12. Internationalization Considerations . . . . . . . . . . . . . 60 86 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 87 14. Security Considerations . . . . . . . . . . . . . . . . . . . 63 88 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 63 89 16. Change History . . . . . . . . . . . . . . . . . . . . . . . . 64 90 16.1. Changes from 91 draft-arias-noguchi-registry-data-escrow-02 to 92 -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . . 64 93 16.2. Changes from version 00 to 01 . . . . . . . . . . . . . . 64 94 16.3. Changes from version 01 to 02 . . . . . . . . . . . . . . 65 95 17. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65 96 17.1. Normative References . . . . . . . . . . . . . . . . . . . 65 97 17.2. Informative References . . . . . . . . . . . . . . . . . . 66 98 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 66 100 1. Introduction 102 This document defines the data escrow structure of the standard set 103 of objects for a Domain Name Registry which include: 105 o Domain: Internet domain names that are typically provisioned in a 106 Domain Name Registry using the EPP domain name mapping [RFC5731]. 107 The attributes defined in the EPP domain name mapping [RFC5731] 108 are fully supported by this document. 110 o Host: Internet host names that are typically provisioned in a 111 Domain Name Registry using the EPP host mapping [RFC5732]. The 112 attributes defined in the EPP host mapping [RFC5732] are fully 113 supported by this document. 115 o Contact: Individual or organization social information provisioned 116 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 117 The attributes defined in the EPP contact mapping [RFC5733] are 118 fully supported by this document. 120 o Registrar: The organization that sponsors objects like domains, 121 hosts, and contacts in a Domain Name Registry. 123 o NNDN: A lightweight domain object that is not linked to a 124 Registrar. 126 This document defines the following pseudo-objects: 128 o IDN practices: Internationalized Domain Names (IDN) included in 129 the Domain Object Data Escrow include references to the languages 130 rules that define the set of character code points allowed for a 131 specific language. 133 o EPP parameters: Definition of the specific EPP parameters 134 supported by the Registry Operator. 136 o Header: Used to specify counters of objects in the SRS database at 137 a certain point in time (watermark). 139 o Policy: Used to specify OPTIONAL elements from this specification 140 that are REQUIRED based on the business model of the registry. 142 2. Models 144 This document defines two different models that can be used to 145 deposit data escrow objects: 147 o XML: The XML model includes all of the deposit information (meta- 148 data and data) in an XML document. The definition of the XML 149 format is fully defined in the XML schemas. 151 o CSV: The CSV model uses XML to define the data escrow format of 152 the data contained in referenced Comma-Separated Values (CSV) 153 files. 155 The data escrow deposit MAY contain a mix of both models but an 156 object MUST be escrowed only in one model. 158 3. Terminology 160 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 161 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 162 document are to be interpreted as described in BCP 14, [RFC2119]. 164 REGISTRY. In the context of this draft the definition will be 165 overloaded (from the definition in the base protocol) to indicate an 166 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 167 NAME. 169 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 170 or any other domain name at any level in the DNS tree for which a 171 Registry (either directly or through and affiliate company) provides 172 Registry Services for other organizations or individuals. For 173 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 175 REGISTRY SERVICES. Services offered by the Registry critical to the 176 following tasks: the provisioning of domain names on receipt of 177 requests and data from registrars; responding to registrar queries 178 for status information relating to the DNS servers for the RCDN; 179 dissemination of RCDN zone files; operation of the Registry DNS 180 servers; and responding to queries for contact and other information 181 concerning DNS registrations in the RCDN. Any other products or 182 services that only a Registry is capable of providing, by reason of 183 its designation as the Registry. Typical examples of Registry 184 Services are: DNS resolution for the RCDN, WHOIS and EPP. 186 ALLOCATED. A status of some label with respect to a zone, whereby 187 the label is associated administratively to some entity that has 188 requested the label. This term (and its cognates "allocation" and 189 "to allocate") may represents the first step on the way to delegation 190 in the DNS. 192 4. General Conventions 194 4.1. Date and Time 196 Numerous fields indicate "dates", such as the creation and expiry 197 dates for domain names. These fields SHALL contain timestamps 198 indicating the date and time in UTC as specified in [RFC3339], with 199 no offset from the zero meridian. 201 4.2. Country names 203 Country identifiers SHALL be represented using two character 204 identifiers as specified in [ISO-3166-1]. 206 4.3. Telephone numbers 208 Telephone numbers (both voice and fascimile) SHALL be formatted based 209 on structures defined in [ITU-E164]. Telephone numbers described in 210 this specification are character strings that MUST begin with a plus 211 sign ("+", ASCII value 0x002B), followed by a country code defined in 212 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 213 a sequence of digits representing the telephone number. 215 4.4. IP addresses 217 IP addresses syntax MUST conform either to, Internet Protocol 218 [RFC0791], for IPv4 addresses, or IP Version 6 Addressing 219 Architecture [RFC4291], for IPv6 addresses. 221 5. Object Description 223 This section describes the base objects supported by this 224 specification: 226 5.1. RDE Domain object 228 The RDE domain object is based on the EPP domain name mapping 229 specified in [RFC5731]. There are two elements used in this format 230 related to domains: the domain object per se, used inside the 231 element and the object used inside the 232 element. 234 5.1.1. object 236 The domain element is based on the EPP domain response for an 237 authorized client (see Section 3.1.2. of [RFC5731]) with additional 238 data from an EPP Query Response, see Section 3.1.3. of 240 [RFC5731], RGP status from [RFC3915], and data from the EPP command, see Section 5.2.1. of [RFC5910]. 243 A element substitutes for the abstract 244 element to define a concrete definition of a domain. The 245 element can be replaced by other domain definitions 246 using the XML schema substitution groups feature. 248 The element contains the following child elements: 250 o A element that contains the fully qualified name of the 251 domain name object. 253 o A element that contains the repository object identifier 254 assigned to the domain name object when it was created. 256 o An OPTIONAL element that contains the name of the domain 257 name in Unicode character set. It MUST be provided if available. 259 o An OPTIONAL element that references the IDN Table 260 used for the IDN. This corresponds to the "id" attribute of the 261 element. This element MUST be present if the domain 262 name is an IDN. 264 o An OPTIONAL element is used to indicate that the 265 domain name is an IDN variant. This element contains the domain 266 name used to generate the IDN variant. 268 o One or more elements that contain the current status 269 descriptors associated with the domain name. 271 o Zero or more OPTIONAL element to represent 272 "pendingDelete" sub-statuses, including "redemptionPeriod", 273 "pendingRestore", and "pendingDelete", that a domain name can be 274 in as a result of grace period processing as specified in 275 [RFC3915]. 277 o An OPTIONAL element that contain the identifier for 278 the human or organizational social information object associated 279 as the holder of the domain name object. 281 o Zero or more OPTIONAL elements that contain identifiers 282 for the human or organizational social information objects 283 associated with the domain name object. 285 o An OPTIONAL element that contains the fully qualified names 286 of the delegated host objects or host attributes (name servers) 287 associated with the domain name object. See Section 1.1 of 289 [RFC5731] for a description of the elements used to specify host 290 objects or host attributes. 292 o A element that contains the identifier of the sponsoring 293 registrar. 295 o A element that contains the identifier of the registrar 296 that created the domain name object. An OPTIONAL client attribute 297 is used to specify the client that performed the operation. 299 o An OPTIONAL element that contains the date and time of 300 the domain name object creation. This element MUST be present if 301 the domain name has been allocated. 303 o An OPTIONAL element that contains the date and time 304 identifying the end (expiration) of the domain name object's 305 registration period. This element MUST be present if the domain 306 name has been allocated. 308 o An OPTIONAL element that contains the identifier of the 309 registrar that last updated the domain name object. This element 310 MUST NOT be present if the domain has never been modified. An 311 OPTIONAL client attribute is used to specify the client that 312 performed the operation. 314 o An OPTIONAL element that contains the date and time of 315 the most recent domain-name-object modification. This element 316 MUST NOT be present if the domain name object has never been 317 modified. 319 o An OPTIONAL element that contains the public key 320 information associated with Domain Name System security (DNSSEC) 321 extensions for the domain name as specified in [RFC5910]. 323 o An OPTIONAL element that contains the date and time of 324 the most recent domain object successful transfer. This element 325 MUST NOT be present if the domain name object has never been 326 transfered. 328 o An OPTIONAL element that contains the following child 329 elements related to the last transfer request of the domain name 330 object. This element MUST NOT be present if a transfer request 331 for the domain name has never been created. 333 * A element that contains the state of the most recent 334 transfer request. 336 * A element that contains the identifier of the registrar 337 that requested the domain name object transfer. An OPTIONAL 338 client attribute is used to specify the client that performed 339 the operation. 341 * A element that contains the date and time that the 342 transfer was requested. 344 * An element that contains the identifier of the registrar 345 that SHOULD act upon a PENDING transfer request. For all other 346 status types, the value identifies the registrar that took the 347 indicated action. An OPTIONAL client attribute is used to 348 specify the client that performed the operation. 350 * An element that contains the date and time of a 351 required or completed response. For a PENDING request, the 352 value identifies the date and time by which a response is 353 required before an automated response action will be taken by 354 the registry. For all other status types, the value identifies 355 the date and time when the request was completed. 357 * An OPTIONAL element that contains the end of the 358 domain name object's validity period (expiry date) if the 359 transfer caused or causes a change in the validity period. 361 Example of a domain object: 363 ... 364 365 example1.test 366 Dexample1-TEST 367 368 jd1234 369 sh8013 370 sh8013 371 372 ns1.example.com 373 ns1.example1.test 374 375 RegistrarX 376 RegistrarX 377 1999-04-03T22:00:00.0Z 378 2015-04-03T22:00:00.0Z 379 380 ... 382 5.1.2. object 384 The element contains the fully qualified domain 385 name that was deleted and purged. 387 Example of object: 389 ... 390 391 ... 392 393 foo.test 394 bar.test 395 396 ... 397 398 ... 400 5.2. RDE Host object 402 The RDE host object is based on the EPP host name mapping in 403 [RFC5732]. There are two elements used in this format related to 404 hosts: the host object per se, used inside the element and 405 the object used inside the element. 407 A element substitutes for the abstract element 408 to define a concrete definition of a host. The 409 element can be replaced by other host definitions using the XML 410 schema substitution groups feature. 412 5.2.1. object 414 The RDE host object is based on the EPP host response for an 415 authorized client (Section 3.1.2. of [RFC5732]). 417 The OPTIONAL element contains the following child elements: 419 o A element that contains the fully qualified name of the 420 host object. 422 o A element that contains the repository object identifier 423 assigned to the host object when the object was created. 425 o One or more elements that describe the status of the host 426 object. 428 o Zero or more elements that contain the IP addresses 429 associated with the host object. 431 o A element that contains the identifier of the sponsoring 432 registrar. 434 o A element that contains the identifier of the registrar 435 that created the host object. An OPTIONAL client attribute is 436 used to specify the client that performed the operation. 438 o A element that contains the date and time of host-object 439 creation. 441 o An OPTIONAL element that contains the identifier of the 442 registrar that last updated the host object. This element MUST 443 NOT be present if the host object has never been modified. An 444 OPTIONAL client attribute is used to specify the client that 445 performed the operation. 447 o An OPTIONAL element that contains the date and time of 448 the most recent host-object modification. This element MUST NOT 449 be present if the host object has never been modified. 451 o An OPTIONAL element that contains the date and time of 452 the most recent host object successful transfer. This element 453 MUST NOT be present if the domain name object has never been 454 transfered. 456 Example of object: 458 ... 459 460 ns1.example1.test 461 Hns1_example_test-TEST 462 463 464 192.0.2.2 465 192.0.2.29 466 1080:0:0:0:8:800:200C:417A 467 RegistrarX 468 RegistrarX 469 1999-05-08T12:10:00.0Z 470 RegistrarX 471 2009-10-03T09:34:00.0Z 472 473 ... 475 5.2.2. object 477 The element contains the fully qualified domain name 478 of a host that was deleted. 480 Example of object: 482 ... 483 484 ... 485 486 ns1.example.test 487 488 ... 489 490 ... 492 5.3. RDE Contact object 494 The RDE contact object is based on the EPP contact name mapping in 495 [RFC5733]. There are two elements used in this format related to 496 contacts: the contact object per se, used inside the 497 element and the object used inside the 498 element. 500 A element substitutes for the abstract 501 element to define a concrete definition of a contact. The 502 element can be replaced by other contact 503 definitions using the XML schema substitution groups feature. 505 5.3.1. object 507 The contact object is based on the EPP contact response for an 508 authorized client (Section 3.1.2. of [RFC5733]) with some additions 509 including the data from an EPP Query Response, see Section 510 3.1.3. of [RFC5733]. 512 The OPTIONAL element contains the following child elements: 514 o An element that contains the repository object identifier 515 assigned to the contact object when the object was created. 517 o A element that contains the repository object identifier 518 assigned to the contact object when it was created. 520 o One or more elements that describe the status of the 521 contact object. 523 o One or two elements that contain postal-address 524 information. Two elements are provided so that address 525 information can be provided in both internationalized and 526 localized forms; a "type" attribute is used to identify the two 527 forms. If an internationalized form (type="int") is provided, 528 element content MUST be represented in a subset of UTF-8 that can 529 be represented in the 7-bit US-ASCII character set. If a 530 localized form (type="loc") is provided, element content MAY be 531 represented in unrestricted UTF-8. The element 532 contains the following child elements: 534 * A element that contains the name of the individual or 535 role represented by the contact. 537 * An OPTIONAL element that contains the name of the 538 organization with which the contact is affiliated. 540 * An element that contains address information associated 541 with the contact. An element contains the following 542 child elements: 544 + One, two, or three OPTIONAL elements that contain 545 the contact's street address. 547 + A element that contains the contact's city. 549 + An OPTIONAL element that contains the contact's state 550 or province. 552 + An OPTIONAL element that contains the contact's postal 553 code. 555 + A element that contains the contact's two-letter 556 country code. 558 o An OPTIONAL element that contains the contact's voice 559 telephone number. 561 o An OPTIONAL element that contains the contact's facsimile 562 telephone number. 564 o An element that contains the contact's email address. 566 o A element that contains the identifier of the sponsoring 567 registrar. 569 o A element that contains the identifier of the registrar 570 that created the contact object. An OPTIONAL client attribute is 571 used to specify the client that performed the operation. 573 o A element that contains the date and time of contact- 574 object creation. 576 o An OPTIONAL element that contains the identifier of the 577 registrar that last updated the contact object. This element MUST 578 NOT be present if the contact has never been modified. An 579 OPTIONAL client attribute is used to specify the client that 580 performed the operation. 582 o An OPTIONAL element that contains the date and time of 583 the most recent contact-object modification. This element MUST 584 NOT be present if the contact object has never been modified. 586 o An OPTIONAL element that contains the date and time of 587 the most recent contact object successful transfer. This element 588 MUST NOT be present if the contact object has never been 589 transferred. 591 o An OPTIONAL element that contains the following child 592 elements related to the last transfer request of the contact 593 object: 595 * A element that contains the state of the most recent 596 transfer request. 598 * A element that contains the identifier of the registrar 599 that requested the domain name object transfer. An OPTIONAL 600 client attribute is used to specify the client that performed 601 the operation. 603 * An element that contains the identifier of the registrar 604 that SHOULD act upon a PENDING transfer request. For all other 605 status types, the value identifies the registrar that took the 606 indicated action. An OPTIONAL client attribute is used to 607 specify the client that performed the operation. 609 * A element that contains the date and time that the 610 transfer was requested. 612 * An element that contains the date and time of a 613 required or completed response. For a PENDING request, the 614 value identifies the date and time by which a response is 615 required before an automated response action will be taken by 616 the registry. For all other status types, the value identifies 617 the date and time when the request was completed. 619 o An OPTIONAL element that identifies elements that 620 requiring exceptional server-operator handling to allow or 621 restrict disclosure to third parties. See Section 2.9 of 622 [RFC5733] for a description of the child elements contained within 623 the element. 625 Example object: 627 ... 628 629 sh8013 630 Csh8013-TEST 631 632 633 634 John Doe 635 Example Inc. 636 637 123 Example Dr. 638 Suite 100 639 Dulles 640 VA 641 20166-6503 642 US 643 644 645 +1.7035555555 646 +1.7035555556 647 jdoe@example.test 648 RegistrarX 649 RegistrarX 650 2009-09-13T08:01:00.0Z 651 RegistrarX 652 2009-11-26T09:10:00.0Z 653 2009-12-03T09:05:00.0Z 654 655 pending 656 clientW 657 2011-03-08T19:38:00.0Z 658 RegistrarX 659 2011-03-13T23:59:59.0Z 660 661 662 663 664 665 666 ... 668 5.3.2. object 670 The element contains the id of a contact that was 671 deleted. 673 Example of object: 675 ... 676 677 ... 678 679 sh8013-TEST 680 co8013-TEST 681 682 ... 683 684 ... 686 5.4. RDE Registrar object 688 The RDE registrar object is the sponsoring client of other RDE 689 objects, for operational purposes MAY be the registry operator. 690 There are two elements used in this format related to registrars: the 691 registrar object per se, used inside the element and the 692 object used inside the element. 694 A element substitutes for the 695 abstract element to define a concrete definition of a registrar. The 696 element can be replaced by other domain 697 definitions using the XML schema substitution groups feature. 699 5.4.1. object 701 The element contains the following child elements: 703 o An element that contains the Registry-unique identifier of 704 the registrar object. This has a superordinate relationship 705 to a subordinate , or of domain, contact and 706 host objects. 708 o An element that contains the name of the registrar. 710 o An OPTIONAL element that contains the ID assigned by 711 ICANN. 713 o A element that contains the operational status of the 714 registrar. Possible values are: ok, readonly and terminated. 716 o One or two elements that contain postal- address 717 information. Two elements are provided so that address 718 information can be provided in both internationalized and 719 localized forms; a "type" attribute is used to identify the two 720 forms. If an internationalized form (type="int") is provided, 721 element content MUST be represented in a subset of UTF-8 that can 722 be represented in the 7-bit US-ASCII character set. If a 723 localized form (type="loc") is provided, element content MAY be 724 represented in unrestricted UTF-8. The element 725 contains the following child elements: 727 * A element that contains address information associated 728 with the registrar. The element contains the following 729 child elements: 731 + One, two, or three OPTIONAL elements that contain 732 the registrar's street address. 734 + A element that contains the registrar's city. 736 + An OPTIONAL element that contains the registrar's state 737 or province. 739 + An OPTIONAL element that contains the registrar's 740 postal code. 742 + A element that contains the registrar's country code. 744 o An OPTIONAL element that contains the registrar's voice 745 telephone number. 747 o An OPTIONAL element that contains the registrar's facsimile 748 telephone number. 750 o An element that contains the registrar's email address. 752 o An OPTIONAL element that contains the registrar's URL. 754 o An OPTIONAL elements that contains whois information. 755 The element contains the following child elements: 757 * An OPTIONAL element that contains the name of the 758 registrar WHOIS server listening on TCP port 43 as specified in 759 [RFC3912]. 761 * An OPTIONAL element that contains the name of the 762 registrar WHOIS server listening on TCP port 80/443. 764 o A element that contains the date and time of registrar- 765 object creation. 767 o An OPTIONAL element that contains the date and time of 768 the most recent RDE registrar-object modification. This element 769 MUST NOT be present if the rdeRegistrar object has never been 770 modified. 772 Example of object: 774 ... 775 776 RegistrarX 777 Registrar X 778 123 779 ok 780 781 782 123 Example Dr. 783 Suite 100 784 Dulles 785 VA 786 20166-6503 787 US 788 789 790 +1.7035555555 791 +1.7035555556 792 jdoe@example.test 793 http://www.example.test 794 795 whois.example.test 796 http://whois.example.test 797 798 2005-04-23T11:49:00.0Z 799 2009-02-17T17:51:00.0Z 800 801 ... 803 5.4.2. object 805 The element contains the id of a registrar that 806 was deleted. 808 Example of object: 810 ... 811 812 ... 813 814 agnt0001-TEST 815 816 ... 817 818 ... 820 5.5. RDE IDN Practices 822 The RDE Internationalized Domain Names (IDN) Practices reference is a 823 pseudo-object that is used to provide a short reference to the IDN 824 Table and Policy used in IDN registrations. The 825 element has an "id" attribute that is used to uniquely identify an 826 IDN Table stored externally. 828 5.5.1. object 830 The OPTIONAL contains the following elements. An id 831 attribute is used to specify an identifier for the IDN table. 833 o An element that contains the URL of the IDN table that is 834 being referenced. 836 o A element that contains the URL of the IDN policy 837 document. If IDN variants are generated algorithmically, the 838 policy document MUST define the algorithm and the state of the 839 implicit generated IDN variants. For a list of suggested states 840 for implicit IDN variants, please see [variantTLDsReport]. 842 Example of object: 844 ... 845 846 847 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 848 849 850 http://registro.br/dominio/regras.html 851 852 853 ... 855 5.6. RDE NNDN 857 A NNDN (NNDN's not domain name) does not exist as a domain object; it 858 is stored in the SRS database. NNDNs can optionally be used to store 859 registry reserved names or IDN variant handling (blocked and 860 withheld). A NNDN is a lightweight domain object that is not linked 861 to a Registrar. A FQDN can only exist as a domain name or NNDN, but 862 not both. 864 A element substitutes for the abstract element 865 to define a concrete definition of a NNDN. The 866 element can be replaced by other NNDN definitions using the XML 867 schema substitution groups feature. 869 5.6.1. object 871 The OPTIONAL element contains the following child elements: 873 o An element that contains the ASCII Compatible Encoding 874 (ACE) of the NNDN. 876 o An OPTIONAL element that contains the name of the NNDN in 877 Unicode character set. It MUST be provided if available. 879 o An OPTIONAL element that references the IDN Table 880 used for the NNDN. This corresponds to the "id" attribute of the 881 element. This element MUST be present if the NNDN 882 is an IDN. 884 o An OPTIONAL element is used to indicate that the 885 NNDN is an IDN variant. This element contains the domain name 886 used to generate the IDN variant. 888 o A element that indicates the state of the NNDN: 889 blocked or withheld. 891 * If a NNDN is considered undesirable for registration (i.e., 892 unavailable for allocation to anyone), then the NNDN will be 893 tagged as "blocked". 895 * If a NNDN is created to allow the registration of a domain 896 object to a particular registrant then the NNDN will be tagged 897 as "withheld". 899 o A element that contains the date and time of the NNDN 900 object creation. 902 Example of object: 904 ... 905 906 xn--exampl-gva.test 907 pt-BR 908 Dexample1-TEST 909 withheld 910 2005-04-23T11:49:00.0Z 911 912 ... 914 5.6.2. object 916 The element contains the ACE of a NNDN that was 917 deleted, i.e., the . 919 Example of object: 921 ... 922 923 ... 924 925 xn--pingino-q2a.test 926 927 ... 928 929 ... 931 5.7. RDE EPP Parameters object 933 An OPTIONAL element contains some EPP parameters that may 934 be helpful when rebuilding a registry from the escrow deposits. The 935 element SHOULD be included in Deposits if the registry uses EPP. 937 The syntax and content of the children elements is as 938 explained in section 2.4 of [RFC5730]. The children of the 939 are as follows: 941 o One or more elements that indicate the EPP versions 942 supported by the registry. 944 o One or more elements that indicate the identifiers of the 945 text response languages supported by the registry's EPP server. 947 o One or more elements that contain namespace URIs 948 representing the objects that the registry's EPP server is capable 949 of managing. 951 o An OPTIONAL element that contains one or more 952 elements that contain namespace URIs representing object 953 extensions supported by the registry's EPP server. 955 o A element that contains child elements used to describe the 956 server's privacy policy for data collection and management. See 957 section 2.4 of [RFC5730] for more details. 959 Example of element object: 961 ... 962 963 1.0 964 en 965 urn:ietf:params:xml:ns:domain-1.0 966 967 urn:ietf:params:xml:ns:contact-1.0 968 969 urn:ietf:params:xml:ns:host-1.0 970 971 972 urn:ietf:params:xml:ns:rgp-1.0 973 urn:ietf:params:xml:ns:secDNS-1.1 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 ... 994 5.8. RDE Policy object 996 The RDE Policy is a pseudo-object that is used to specify which 997 OPTIONAL elements from this specification are REQUIRED based on the 998 business model of the registry. 1000 5.8.1. object 1002 The OPTIONAL contains the following attributes: 1004 o An that defines that the referenced is 1005 REQUIRED. 1007 Example of object: 1009 ... 1010 1011 ... 1013 5.9. Header object 1015 The RDE Header is a pseudo-object that is used to specify the number 1016 of objects in the SRS at a specific point in time (watermark) 1017 regardless of the type of deposit: differential, full or incremental. 1019 5.9.1.
object 1021 The
contains the following attributes: 1023 o A element that defines TLD being escrowed. 1025 o A element that number of objects being escrowed. An uri 1026 attribute is used to define the type of object. 1028 Example of
object: 1030 ... 1031 1032 test 1033 2 1035 1 1037 1 1039 1 1041 1042 1 1044 1 1046 1 1048 1049 1050 ... 1052 6. RDE IDN Variants handling 1054 Depending on the Registration Policy of the Registry; for a 1055 particular domain name there may be multiple variant names. See 1056 [variantTLDsReport] for further detail on IDN variants. 1058 A registry could choose to escrow IDN variants as domains or NNDN 1059 objects. 1061 A NNDN or a domain name are explicit representations of an IDN 1062 variant while an IDN variant computed based on an algorithm is an 1063 implicit representation. Explicit representation of an IDN variant 1064 takes precedence over an implicit representation. 1066 7. Profile 1068 Different business models of registries exist, therefore the registry 1069 is responsible to define a profile that matches its particular 1070 business model. The profile mechanism allows a registry to extend 1071 this specification. 1073 A profile is the process of: 1075 1. Extending base objects with the mechanisms defined for XML and 1076 CSV models. 1078 * In the case of the XML model, abstract elements could be use 1079 to extend the following objects: , , , 1080 and using XML schema substitution groups 1081 feature. 1083 2. Defining a object to specify which OPTIONAL elements of 1084 this base specification are required based on the business model 1085 of the registry. An example is the element that is 1086 usually REQUIRED but it is specified as OPTIONAL in this 1087 specification to accomodate existing business models. 1089 3. Adding new escrowed objects using the and elements. 1092 4. Providing the XML schemas to third parties that require them to 1093 validate the escrow deposits. 1095 8. Appendix A. Example of a full deposit using the XML model only 1097 Example of a full deposit using the XML model only: 1099 1100 1116 2010-10-17T00:00:00Z 1117 1118 1.0 1119 urn:ietf:params:xml:ns:rdeHeader-1.0 1120 urn:ietf:params:xml:ns:rdeContact-1.0 1121 urn:ietf:params:xml:ns:rdeHost-1.0 1122 urn:ietf:params:xml:ns:rdeDomain-1.0 1123 urn:ietf:params:xml:ns:rdeRegistrar-1.0 1124 urn:ietf:params:xml:ns:rdeIDN-1.0 1125 urn:ietf:params:xml:ns:rdeNNDN-1.0 1126 urn:ietf:params:xml:ns:rdeEppParams-1.0 1127 1129 1130 1131 1132 1133 test 1134 2 1136 1 1138 1 1140 1 1142 1143 1 1145 1 1147 1 1149 1150 1152 1153 1154 example1.test 1155 Dexample1-TEST 1156 1157 jd1234 1158 sh8013 1159 sh8013 1160 1161 ns1.example.com 1162 ns1.example1.test 1163 1164 RegistrarX 1165 RegistrarX 1166 1999-04-03T22:00:00.0Z 1167 2015-04-03T22:00:00.0Z 1168 1169 1170 1171 example2.test 1172 Dexample2-TEST 1173 1174 1175 jd1234 1176 sh8013 1177 sh8013 1178 RegistrarX 1179 RegistrarX 1180 1999-04-03T22:00:00.0Z 1181 2015-04-03T22:00:00.0Z 1182 1184 1185 1186 ns1.example1.test 1187 Hns1_example_test-TEST 1188 1189 1190 192.0.2.2 1191 192.0.2.29 1192 1080:0:0:0:8:800:200C:417A 1193 RegistrarX 1194 RegistrarX 1195 1999-05-08T12:10:00.0Z 1196 RegistrarX 1197 2009-10-03T09:34:00.0Z 1198 1200 1201 1202 sh8013 1203 Csh8013-TEST 1204 1205 1206 1207 John Doe 1208 Example Inc. 1209 1210 123 Example Dr. 1211 Suite 100 1212 Dulles 1213 VA 1214 20166-6503 1215 US 1217 1218 1219 +1.7035555555 1220 +1.7035555556 1221 jdoe@example.test 1222 RegistrarX 1223 RegistrarX 1224 2009-09-13T08:01:00.0Z 1225 RegistrarX 1226 2009-11-26T09:10:00.0Z 1227 2009-12-03T09:05:00.0Z 1228 1229 1230 1231 1232 1234 1235 1236 RegistrarX 1237 Registrar X 1238 123 1239 ok 1240 1241 1242 123 Example Dr. 1243 Suite 100 1244 Dulles 1245 VA 1246 20166-6503 1247 US 1248 1249 1250 +1.7035555555 1251 +1.7035555556 1252 jdoe@example.test 1253 http://www.example.test 1254 1255 whois.example.test 1256 http://whois.example.test 1257 1258 2005-04-23T11:49:00.0Z 1259 2009-02-17T17:51:00.0Z 1260 1262 1263 1264 1265 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 1266 1267 1268 http://registro.br/dominio/regras.html 1269 1270 1272 1273 1274 xn--exampl-gva.test 1275 pt-BR 1276 Dexample1-TEST 1277 withheld 1278 2005-04-23T11:49:00.0Z 1279 1281 1282 1283 1.0 1284 en 1285 1286 urn:ietf:params:xml:ns:domain-1.0 1287 1288 1289 urn:ietf:params:xml:ns:contact-1.0 1290 1291 1292 urn:ietf:params:xml:ns:host-1.0 1293 1294 1295 urn:ietf:params:xml:ns:rgp-1.0 1296 urn:ietf:params:xml:ns:secDNS-1.1 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1314 1315 1316 1317 1318 1320 9. Appendix B. Example of differential deposit using the XML model only 1322 Example of a differential deposit using the XML model only: 1324 1325 1340 2010-10-17T00:00:00Z 1341 1342 1.0 1343 urn:ietf:params:xml:ns:rdeHeader-1.0 1344 urn:ietf:params:xml:ns:rdeContact-1.0 1345 urn:ietf:params:xml:ns:rdeHost-1.0 1346 urn:ietf:params:xml:ns:rdeDomain-1.0 1347 urn:ietf:params:xml:ns:rdeRegistrar-1.0 1348 urn:ietf:params:xml:ns:rdeIDN-1.0 1349 urn:ietf:params:xml:ns:rdeNNDN-1.0 1350 urn:ietf:params:xml:ns:rdeEppParams-1.0 1351 1353 1354 1355 1356 example2.test 1357 1358 1359 1360 1361 1362 1363 test 1364 1 1366 1 1368 1 1370 1 1372 1373 1 1375 1 1377 1 1379 1380 1381 1382 1384 10. Appendix C. Data escrow agent extended verification process 1386 The Data Escrow Agent MAY perform a extended verification process 1387 using the contents of data escrow deposits to a point in time 1388 (watermark), last full plus all differentials or last full plus last 1389 incremental escrow deposits. The following are the minimum suggested 1390 tests: 1392 o Validate the escrow deposits using the definition agreed with the 1393 registry. 1395 * In the case of the XML model, the contents of the escrow 1396 deposits MUST be validated using the XML schemas of the 1397 profile. 1399 o Count the objects and validate that number of objects is equal to 1400 the number objects reported in the
element of the escrow 1401 deposit of that point in time (watermark). 1403 o All contacts linked to domain names are present. 1405 o All registrars linked to other objects are present. 1407 o An FQDN exists only as a domain name or NNDN. 1409 o The elements listed in the element are present. 1411 o All idnTableRef definitions linked from other objects are present. 1413 11. Appendix D. Data escrow notifications 1415 Data escrowing involves several parties interacting with the 1416 objective of restoring the operations of a Domain Registry in case of 1417 an emergency. The following section defines several notifications 1418 that are suggested to be sent between the interacting parties. The 1419 parties based on the notification can know the status of the data 1420 escrow deposit even if no access to the data escrow deposit file is 1421 available. 1423 11.1. Notifications from Registry Operators to Third Parties 1425 Registry Operators MAY notify Third Parties that a data escrow 1426 deposit file was sent to the Data Escrow Agent. 1428 11.1.1. object 1430 The object is used by Registry Operator to notify Third 1431 Parties about successful delivery of a data escrow deposit to a Data 1432 Escrow Agent. 1434 The element contains the following child elements: 1436 o An element contains the identifier assigned to this report. 1437 An OPTIONAL resend attribute is used to specify the number of 1438 retries needed for a successful reception/validator of the data 1439 escrow deposit by the data escrow agent. It is recommended that 1440 the report identifier be the same as the data escrow deposit 1441 identifier. 1443 o A element contains the date and time that the data escrow 1444 deposit was successful received by the data escrow agent. 1446 o An OPTIONAL element contains the date and time that the 1447 data escrow deposit was successfuly validated by the data escrow 1448 agent. 1450 o A element is used to identify the kind of deposit: FULL, 1451 INCR (Incremental) or DIFF (Differential). 1453 o A element contains the date and time of the last 1454 FULL data escrow deposit that was successfuly validated by the 1455 data escrow agent. 1457 o A element contains the data-time corresponding to the 1458 Timeline Watermark of the deposit. 1460 o A
element contains the header of the data escrow deposit. 1462 Example object: 1464 1465 1468 20101017001 1469 2010-10-17T01:51:10.0Z 1470 2010-10-17T02:51:10.0Z 1471 FULL 1472 2010-10-16 1473 2010-10-17T00:00:00Z 1474 1475 test 1476 2 1478 1 1480 1 1482 1 1484 1485 1 1487 1 1489 1 1491 1492 1493 1495 11.2. Notifications from Data Escrow Agents to Third Parties 1497 Data Escrow Agents MAY notify Third Parties that a data escrow 1498 deposit file was received or it is missing for a specific date. 1500 11.2.1. object 1502 The object is used by Data Escrow Agents to notify 1503 Third Parties about sucessful reception/validation of a data escrow 1504 deposit for a specific date. If multiple deposits are received in a 1505 day, the latest received deposit MUST be used to generate the 1506 notification. 1508 The element contains the following child elements: 1510 o An element contains the reported date. 1512 o A element is used to specify the status of . The 1513 possible values of status are: valid, invalid and missing. 1515 * Valid: The last received data escrow deposit for the specified 1516 date in was successfully validated. 1518 * Invalid: The last received data escrow deposit for the 1519 specified date in was not successfully validated. 1521 * Missing: No data escrow deposit was received on the date 1522 specified in . 1524 o A element it is used by the data escrow agent to provide 1525 extended information about the data escrow deposit. The
1526 element MUST be generated by the data escrow agent for a certain 1527 point in time (watermark) based on the contents of the escrow 1528 deposits. The last full plus all differentials or last full plus 1529 last incremental escrow deposits MUST be used to generate
1530 element. 1532 Example object: 1534 1535 1539 2010-10-17 1540 valid 1541 1542 20101017001 1543 2010-10-17T02:51:10.0Z 1544 2010-10-17T01:51:10.0Z 1545 FULL 1546 2010-10-16 1547 2010-10-17T00:00:00Z 1548 1549 test 1550 2 1552 1 1554 1 1556 1 1558 1559 1 1561 1 1563 1 1565 1566 1567 1568 1570 11.3. Formal Syntax 1572 Seven schemas are presented here. The first schema is the base RDE 1573 schema. The second schema defines domain object for RDE. The third 1574 schema defines host object for RDE. The fourth schema defines 1575 contact object for RDE. The fifth schema defines registrar object 1576 for RDE. The sixth schema defines the idnTableRef and IDN objects. 1577 The last schema defines the eppParams objects. 1579 11.3.1. RDE Domain Object 1581 Copyright (c) 2011 IETF Trust and the persons identified as authors 1582 of the code. All rights reserved. 1584 Redistribution and use in source and binary forms, with or without 1585 modification, are permitted provided that the following conditions 1586 are met: 1588 o Redistributions of source code must retain the above copyright 1589 notice, this list of conditions and the following disclaimer. 1591 o Redistributions in binary form must reproduce the above copyright 1592 notice, this list of conditions and the following disclaimer in 1593 the documentation and/or other materials provided with the 1594 distribution. 1596 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1597 names of specific contributors, may be used to endorse or promote 1598 products derived from this software without specific prior written 1599 permission. 1601 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1602 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1603 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1604 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1605 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1606 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1607 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1608 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1609 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1610 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1611 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1613 BEGIN 1614 1615 1625 1628 1630 1632 1634 1637 1638 1639 Registry Data Escrow Domain provisioning schema 1640 1641 1643 1645 1646 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1660 1662 1664 1666 1668 1669 1670 1671 1672 1673 1674 1675 1677 1678 1680 1682 1683 1684 1685 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1698 1699 1700 1701 1702 1703 1705 1706 1707 1708 1709 1710 END 1712 11.3.2. RDE Host Object 1714 Copyright (c) 2011 IETF Trust and the persons identified as authors 1715 of the code. All rights reserved. 1717 Redistribution and use in source and binary forms, with or without 1718 modification, are permitted provided that the following conditions 1719 are met: 1721 o Redistributions of source code must retain the above copyright 1722 notice, this list of conditions and the following disclaimer. 1724 o Redistributions in binary form must reproduce the above copyright 1725 notice, this list of conditions and the following disclaimer in 1726 the documentation and/or other materials provided with the 1727 distribution. 1729 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1730 names of specific contributors, may be used to endorse or promote 1731 products derived from this software without specific prior written 1732 permission. 1734 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1735 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1736 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1737 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1738 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1739 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1740 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1741 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1742 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1743 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1744 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1746 BEGIN 1747 1748 1756 1758 1760 1763 1764 1765 Registry Data Escrow Host provisioning schema 1766 1767 1769 1771 1774 1775 1776 1777 1778 1779 1780 1781 1782 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1795 1796 1797 1798 1799 1800 1802 1803 1804 1805 1806 1807 END 1809 11.3.3. RDE Contact Object 1811 Copyright (c) 2011 IETF Trust and the persons identified as authors 1812 of the code. All rights reserved. 1814 Redistribution and use in source and binary forms, with or without 1815 modification, are permitted provided that the following conditions 1816 are met: 1818 o Redistributions of source code must retain the above copyright 1819 notice, this list of conditions and the following disclaimer. 1821 o Redistributions in binary form must reproduce the above copyright 1822 notice, this list of conditions and the following disclaimer in 1823 the documentation and/or other materials provided with the 1824 distribution. 1826 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1827 names of specific contributors, may be used to endorse or promote 1828 products derived from this software without specific prior written 1829 permission. 1831 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1832 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1833 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1834 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1835 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1836 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1837 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1838 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1839 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1840 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1841 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1843 BEGIN 1844 1845 1853 1854 1856 1858 1861 1862 1863 Registry Data Escrow contact provisioning schema 1864 1865 1866 1868 1870 1873 1874 1875 1876 1877 1878 1879 1880 1882 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1895 1897 1898 1899 1900 1902 1903 1904 1905 1906 1907 1908 1909 1910 1912 1913 1914 1915 1916 1917 1919 1920 1921 1922 1923 1924 END 1926 11.3.4. RDE Registrar Object 1928 Copyright (c) 2011 IETF Trust and the persons identified as authors 1929 of the code. All rights reserved. 1931 Redistribution and use in source and binary forms, with or without 1932 modification, are permitted provided that the following conditions 1933 are met: 1935 o Redistributions of source code must retain the above copyright 1936 notice, this list of conditions and the following disclaimer. 1938 o Redistributions in binary form must reproduce the above copyright 1939 notice, this list of conditions and the following disclaimer in 1940 the documentation and/or other materials provided with the 1941 distribution. 1943 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1944 names of specific contributors, may be used to endorse or promote 1945 products derived from this software without specific prior written 1946 permission. 1948 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1949 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1950 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1951 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1952 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1953 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1954 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1955 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1956 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1957 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1958 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1960 BEGIN 1961 1962 1971 1972 1974 1976 1978 1981 1982 1983 Registry Data Escrow registrar provisioning schema 1984 1985 1987 1990 1992 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2006 2007 2008 2009 2010 2012 2013 2014 2015 2016 2017 2019 2020 2021 2022 2023 2024 2026 2027 2028 2029 2030 2031 2032 2034 2035 2036 2037 2038 2040 2042 2043 2044 2045 2046 2047 2049 2050 2051 2053 2054 2056 2057 2058 2059 2061 2062 2063 2064 2065 2066 2068 2069 2070 2071 2072 2074 2075 2076 2077 2078 2080 2081 2082 2083 2084 2086 2087 2088 2089 2090 2091 2093 2094 2095 2096 2097 2098 2100 2101 2102 2103 2104 2105 END 2107 11.3.5. RDE IDN and IDN Table Reference Objects 2109 Copyright (c) 2011 IETF Trust and the persons identified as authors 2110 of the code. All rights reserved. 2112 Redistribution and use in source and binary forms, with or without 2113 modification, are permitted provided that the following conditions 2114 are met: 2116 o Redistributions of source code must retain the above copyright 2117 notice, this list of conditions and the following disclaimer. 2119 o Redistributions in binary form must reproduce the above copyright 2120 notice, this list of conditions and the following disclaimer in 2121 the documentation and/or other materials provided with the 2122 distribution. 2124 o Neither the name of Internet Society, IETF or IETF Trust, nor the 2125 names of specific contributors, may be used to endorse or promote 2126 products derived from this software without specific prior written 2127 permission. 2129 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2130 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2131 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2132 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2133 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2134 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2135 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2136 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2137 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2138 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2139 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2141 BEGIN 2142 2143 2149 2152 2153 2154 Registry Data Escrow IDN provisioning schema 2155 2156 2158 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2174 2175 2176 2177 2178 2180 2181 END 2183 11.3.6. EPP Parameters Object 2185 Copyright (c) 2011 IETF Trust and the persons identified as authors 2186 of the code. All rights reserved. 2188 Redistribution and use in source and binary forms, with or without 2189 modification, are permitted provided that the following conditions 2190 are met: 2192 o Redistributions of source code must retain the above copyright 2193 notice, this list of conditions and the following disclaimer. 2195 o Redistributions in binary form must reproduce the above copyright 2196 notice, this list of conditions and the following disclaimer in 2197 the documentation and/or other materials provided with the 2198 distribution. 2200 o Neither the name of Internet Society, IETF or IETF Trust, nor the 2201 names of specific contributors, may be used to endorse or promote 2202 products derived from this software without specific prior written 2203 permission. 2205 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2206 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2207 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2208 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2209 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2210 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2211 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2212 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2213 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2214 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2215 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2217 BEGIN 2218 2219 2227 2229 2231 2234 2235 2236 Registry Data Escrow EPP Parameters schema 2237 2238 2240 2241 2244 2245 2248 2249 2250 2251 2252 2254 2255 2256 2258 2259 2260 2261 2262 2263 2264 END 2266 11.3.7. NNDN Object 2268 Copyright (c) 2011 IETF Trust and the persons identified as authors 2269 of the code. All rights reserved. 2271 Redistribution and use in source and binary forms, with or without 2272 modification, are permitted provided that the following conditions 2273 are met: 2275 o Redistributions of source code must retain the above copyright 2276 notice, this list of conditions and the following disclaimer. 2278 o Redistributions in binary form must reproduce the above copyright 2279 notice, this list of conditions and the following disclaimer in 2280 the documentation and/or other materials provided with the 2281 distribution. 2283 o Neither the name of Internet Society, IETF or IETF Trust, nor the 2284 names of specific contributors, may be used to endorse or promote 2285 products derived from this software without specific prior written 2286 permission. 2288 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2289 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2290 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2291 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2292 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2293 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2294 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2295 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2296 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2297 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2298 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2300 BEGIN 2301 2302 2309 2311 2314 2315 2316 Registry Data Escrow NNDN provisioning schema 2317 2318 2320 2322 2323 2326 2327 2328 2329 2330 2331 2332 2333 2334 2336 2337 2338 2339 2340 2341 2343 2344 2345 2346 2347 2348 2350 2351 2352 2353 2354 2355 2357 2358 2359 2360 2361 2362 END 2364 11.3.8. Header Object 2366 Copyright (c) 2011 IETF Trust and the persons identified as authors 2367 of the code. All rights reserved. 2369 Redistribution and use in source and binary forms, with or without 2370 modification, are permitted provided that the following conditions 2371 are met: 2373 o Redistributions of source code must retain the above copyright 2374 notice, this list of conditions and the following disclaimer. 2376 o Redistributions in binary form must reproduce the above copyright 2377 notice, this list of conditions and the following disclaimer in 2378 the documentation and/or other materials provided with the 2379 distribution. 2381 o Neither the name of Internet Society, IETF or IETF Trust, nor the 2382 names of specific contributors, may be used to endorse or promote 2383 products derived from this software without specific prior written 2384 permission. 2386 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2387 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2388 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2389 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2390 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2391 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2392 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2393 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2394 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2395 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2396 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2398 BEGIN 2399 2400 2407 2409 2412 2413 2414 Registry Data Escrow Header schema 2415 2416 2418 2419 2422 2423 2424 2425 2426 2427 2428 2430 2431 2432 2433 2435 2436 2437 2438 2439 2440 2441 2442 2443 END 2445 11.3.9. Report Object 2447 Copyright (c) 2011 IETF Trust and the persons identified as authors 2448 of the code. All rights reserved. 2450 Redistribution and use in source and binary forms, with or without 2451 modification, are permitted provided that the following conditions 2452 are met: 2454 o Redistributions of source code must retain the above copyright 2455 notice, this list of conditions and the following disclaimer. 2457 o Redistributions in binary form must reproduce the above copyright 2458 notice, this list of conditions and the following disclaimer in 2459 the documentation and/or other materials provided with the 2460 distribution. 2462 o Neither the name of Internet Society, IETF or IETF Trust, nor the 2463 names of specific contributors, may be used to endorse or promote 2464 products derived from this software without specific prior written 2465 permission. 2467 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2468 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2469 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2470 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2471 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2472 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2473 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2474 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2475 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2476 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2477 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2479 BEGIN 2480 2481 2488 2490 2493 2494 2495 Registry Data Escrow Report schema 2496 2497 2499 2500 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 END 2517 11.3.10. Notifiaction Object 2519 Copyright (c) 2011 IETF Trust and the persons identified as authors 2520 of the code. All rights reserved. 2522 Redistribution and use in source and binary forms, with or without 2523 modification, are permitted provided that the following conditions 2524 are met: 2526 o Redistributions of source code must retain the above copyright 2527 notice, this list of conditions and the following disclaimer. 2529 o Redistributions in binary form must reproduce the above copyright 2530 notice, this list of conditions and the following disclaimer in 2531 the documentation and/or other materials provided with the 2532 distribution. 2534 o Neither the name of Internet Society, IETF or IETF Trust, nor the 2535 names of specific contributors, may be used to endorse or promote 2536 products derived from this software without specific prior written 2537 permission. 2539 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2540 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2541 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2542 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2543 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2544 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2545 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2546 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2547 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2548 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2549 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2551 BEGIN 2552 2553 2559 2562 2563 2564 Registry Data Escrow Notification schema 2565 2566 2568 2569 2571 2572 2573 2574 2575 2576 2577 2578 2580 2581 2582 2583 2584 2585 2586 2587 2588 END 2590 11.4. Policy Object 2592 Copyright (c) 2011 IETF Trust and the persons identified as authors 2593 of the code. All rights reserved. 2595 Redistribution and use in source and binary forms, with or without 2596 modification, are permitted provided that the following conditions 2597 are met: 2599 o Redistributions of source code must retain the above copyright 2600 notice, this list of conditions and the following disclaimer. 2602 o Redistributions in binary form must reproduce the above copyright 2603 notice, this list of conditions and the following disclaimer in 2604 the documentation and/or other materials provided with the 2605 distribution. 2607 o Neither the name of Internet Society, IETF or IETF Trust, nor the 2608 names of specific contributors, may be used to endorse or promote 2609 products derived from this software without specific prior written 2610 permission. 2612 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2613 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2614 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2615 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2616 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2617 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2618 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2619 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2620 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2621 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2622 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2624 BEGIN 2625 2626 2632 2633 2634 Registry Data Escrow Policy schema 2635 2636 2638 2641 2644 2645 2646 2647 2648 2649 2650 2651 2652 END 2654 12. Internationalization Considerations 2656 Data Escrow deposits are represented in XML, which provides native 2657 support for encoding information using the Unicode character set and 2658 its more compact representations including UTF-8. Conformant XML 2659 processors recognize both UTF-8 and UTF-16. Though XML includes 2660 provisions to identify and use other character encodings through use 2661 of an "encoding" attribute in an declaration, use of UTF-8 is 2662 RECOMMENDED. 2664 13. IANA Considerations 2666 This document uses URNs to describe XML namespaces and XML schemas 2667 conforming to a registry mechanism described in [RFC3688]. Fourteen 2668 URI assignments have been registered by the IANA. 2670 Registration request for the RDE domain namespace: 2672 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 2674 Registrant Contact: See the "Author's Address" section of this 2675 document. 2677 XML: None. Namespace URIs do not represent an XML specification. 2679 Registration request for the RDE domain XML schema: 2681 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 2683 Registrant Contact: See the "Author's Address" section of this 2684 document. 2686 See the "Formal Syntax" section of this document. 2688 Registration request for the RDE host namespace: 2690 URI: urn:ietf:params:xml:ns:rdeHost-1.0 2692 Registrant Contact: See the "Author's Address" section of this 2693 document. 2695 XML: None. Namespace URIs do not represent an XML specification. 2697 Registration request for the RDE host XML schema: 2699 URI: urn:ietf:params:xml:schema:rdeHost-1.0 2701 Registrant Contact: See the "Author's Address" section of this 2702 document. 2704 See the "Formal Syntax" section of this document. 2706 Registration request for the RDE contact namespace: 2708 URI: urn:ietf:params:xml:ns:rdeContact-1.0 2710 Registrant Contact: See the "Author's Address" section of this 2711 document. 2713 XML: None. Namespace URIs do not represent an XML specification. 2715 Registration request for the RDE contact XML schema: 2717 URI: urn:ietf:params:xml:schema:rdeContact-1.0 2719 Registrant Contact: See the "Author's Address" section of this 2720 document. 2722 See the "Formal Syntax" section of this document. 2724 Registration request for the RDE registrar namespace: 2726 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 2728 Registrant Contact: See the "Author's Address" section of this 2729 document. 2731 XML: None. Namespace URIs do not represent an XML specification. 2733 Registration request for the RDE registrar XML schema: 2735 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 2737 Registrant Contact: See the "Author's Address" section of this 2738 document. 2740 See the "Formal Syntax" section of this document. 2742 Registration request for the RDE IDN namespace: 2744 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 2746 Registrant Contact: See the "Author's Address" section of this 2747 document. 2749 XML: None. Namespace URIs do not represent an XML specification. 2751 Registration request for the RDE IDN XML schema: 2753 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 2755 Registrant Contact: See the "Author's Address" section of this 2756 document. 2758 See the "Formal Syntax" section of this document. 2760 Registration request for the RDE EPP parameters namespace: 2762 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 2763 Registrant Contact: See the "Author's Address" section of this 2764 document. 2766 XML: None. Namespace URIs do not represent an XML specification. 2768 Registration request for the RDE EPP parameters XML schema: 2770 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 2772 Registrant Contact: See the "Author's Address" section of this 2773 document. 2775 See the "Formal Syntax" section of this document. 2777 14. Security Considerations 2779 This specification does not define the security mechanisms to be used 2780 in the transmission of the data escrow deposits, since it only 2781 specifies the minimum necessary to enable the rebuilding of a 2782 Registry from deposits without intervention from the original 2783 Registry. 2785 Depending on local policies, some elements or most likely, the whole 2786 deposit will be considered confidential. As such the Registry 2787 transmitting the data to the Escrow Agent SHOULD take all the 2788 necessary precautions like encrypting the data itself and/or the 2789 transport channel to avoid inadvertent disclosure of private data. 2791 It is also of the utmost importance the authentication of the parties 2792 passing data escrow deposit files. The Escrow Agent SHOULD properly 2793 authenticate the identity of the Registry before accepting data 2794 escrow deposits. In a similar manner, the Registry SHOULD 2795 authenticate the identity of the Escrow Agent before submitting any 2796 data. 2798 Additionally, the Registry and the Escrow Agent SHOULD use integrity 2799 checking mechanisms to ensure the data transmitted is what the source 2800 intended. Validation of the contents by the Escrow Agent is 2801 RECOMMENDED to ensure not only the file was transmitted correctly 2802 from the Registry, but also the contents are also "meaningful". 2804 15. Acknowledgments 2806 Parts of this document are based on EPP [RFC5730] and related RFCs by 2807 Scott Hollenbeck. 2809 TBD 2811 16. Change History 2813 [[RFC Editor: Please remove this section.]] 2815 16.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to 2816 -dnrd-objects-mapping-00 2818 1. Added definition for child elements under the element. 2820 2. Added definition for child elements under the element. 2822 3. Added definition for child elements under the element. 2824 4. Rewrote the IDN Variants Handling section to use the variant 2825 states as described in ICANN's Study of Issues Related to the 2826 Management of IDN Variant TLDs. 2828 5. Renamed to in the . 2830 6. Renamed to in the element. 2832 7. Renamed to in the element. 2834 8. Added element under element. 2836 9. Fixed some typographical errors and omissions. 2838 16.2. Changes from version 00 to 01 2840 1. Specify OPTIONAL elements in the draft. 2842 2. Added NNDN object to support list of reserved names and different 2843 IDN variants models. 2845 3. Removed subordinated host element from the domain object. 2847 4. Added eppParams object. 2849 5. Added variantGenerator element to the domain object. 2851 6. Added lgr to the IDN table object. 2853 16.3. Changes from version 01 to 02 2855 1. Updates to the all objects based on feedback from the list. 2857 2. Start of XML and CSV drafts merge. 2859 3. Added header object. 2861 4. Added report object. 2863 5. Added notification object. 2865 6. Added Data Escrow Agent Extended Verification Process section. 2867 7. Added Notifications from Registries to Third Parties. 2869 8. Added Notifications from Data Escrow Agents to Third Parties. 2871 9. Added FULL, DIFF deposit examples using the XML model only. 2873 17. References 2875 17.1. Normative References 2877 [ISO-3166-1] 2878 International Organization for Standardization, "Codes for 2879 the representation of names of countries and their 2880 subdivisions -- Part 1: Country codes", ISO Standard 3166, 2881 November 2006. 2883 [ITU-E164] 2884 International Telecommunication Union, "The international 2885 public telecommunication numbering plan", ITU-T 2886 Recommendation E.164, February 2005. 2888 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2889 Requirement Levels", BCP 14, RFC 2119, March 1997. 2891 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 2892 Internet: Timestamps", RFC 3339, July 2002. 2894 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 2895 the Extensible Provisioning Protocol (EPP)", RFC 3915, 2896 September 2004. 2898 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2899 Domain Name Mapping", STD 69, RFC 5731, August 2009. 2901 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2902 Host Mapping", STD 69, RFC 5732, August 2009. 2904 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2905 Contact Mapping", STD 69, RFC 5733, August 2009. 2907 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 2908 Security Extensions Mapping for the Extensible 2909 Provisioning Protocol (EPP)", RFC 5910, May 2010. 2911 17.2. Informative References 2913 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 2914 September 1981. 2916 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2917 January 2004. 2919 [RFC3743] Konishi, K., Huang, K., Qian, H., and Y. Ko, "Joint 2920 Engineering Team (JET) Guidelines for Internationalized 2921 Domain Names (IDN) Registration and Administration for 2922 Chinese, Japanese, and Korean", RFC 3743, April 2004. 2924 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 2925 September 2004. 2927 [RFC4290] Klensin, J., "Suggested Practices for Registration of 2928 Internationalized Domain Names (IDN)", RFC 4290, 2929 December 2005. 2931 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2932 Architecture", RFC 4291, February 2006. 2934 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2935 STD 69, RFC 5730, August 2009. 2937 [variantTLDsReport] 2938 Internet Corporation for Assigned Names and Numbers 2939 (ICANN), "A Study of Issues Related to the Management of 2940 IDN Variant TLDs", February 2012, . 2944 Authors' Addresses 2946 Francisco Arias 2947 Internet Corporation for Assigned Names and Numbers 2948 12025 Waterfront Drive, Suite 300 2949 Los Angeles 90292 2950 United States of America 2952 Phone: +1.310.823.9358 2953 Email: francisco.arias@icann.org 2955 Gustavo Lozano 2956 Internet Corporation for Assigned Names and Numbers 2957 12025 Waterfront Drive, Suite 300 2958 Los Angeles 90292 2959 United States of America 2961 Phone: +1.310.823.9358 2962 Email: gustavo.lozano@icann.org 2964 Shoji Noguchi 2965 Japan Registry Services Co., Ltd. 2966 Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda 2967 Chiyoda-ku, Tokyo 101-0065 2968 Japan 2970 Phone: +81.3.5215.8451 2971 Email: noguchi@jprs.co.jp 2973 James Gould 2974 VeriSign, Inc. 2975 12061 Bluemont Way 2976 Reston 20190 2977 United States of America 2979 Email: jgould@verisign.com 2980 Chethan Thippeswamy 2981 VeriSign, Inc. 2982 12061 Bluemont Way 2983 Reston 20190 2984 United States of America 2986 Email: cthippeswamy@verisign.com