idnits 2.17.1 draft-arias-noguchi-dnrd-objects-mapping-03.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 (April 04, 2013) is 4039 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 2949, but no explicit reference was found in the text == Unused Reference: 'RFC4290' is defined on line 2957, 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: October 6, 2013 S. Noguchi 6 JPRS 7 J. Gould 8 C. Thippeswamy 9 VeriSign 10 April 04, 2013 12 Domain Name Registration Data (DNRD) Objects Mapping 13 draft-arias-noguchi-dnrd-objects-mapping-03 15 Abstract 17 This document specifies the format, contents and semantics of Domain 18 Name Registration Data (DNRD) Escrow deposits for a Domain Name 19 Registry. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on October 6, 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. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 25 76 8.1. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 25 77 8.2. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 28 78 8.3. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 30 79 8.4. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 32 80 8.5. RDE IDN and IDN Table Reference Objects . . . . . . . . . 36 81 8.6. EPP Parameters Object . . . . . . . . . . . . . . . . . . 38 82 8.7. NNDN Object . . . . . . . . . . . . . . . . . . . . . . . 41 83 8.8. Policy Object . . . . . . . . . . . . . . . . . . . . . . 43 84 8.9. Header Object . . . . . . . . . . . . . . . . . . . . . . 44 85 8.10. Report Object . . . . . . . . . . . . . . . . . . . . . . 47 86 8.11. Notification Object . . . . . . . . . . . . . . . . . . . 48 87 9. Internationalization Considerations . . . . . . . . . . . . . 50 88 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 89 11. Security Considerations . . . . . . . . . . . . . . . . . . . 53 90 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 54 91 13. Change History . . . . . . . . . . . . . . . . . . . . . . . . 54 92 13.1. Changes from 93 draft-arias-noguchi-registry-data-escrow-02 to 94 -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . . 54 95 13.2. Changes from version 00 to 01 . . . . . . . . . . . . . . 54 96 13.3. Changes from version 01 to 02 . . . . . . . . . . . . . . 55 97 13.4. Changes from version 02 to 03 . . . . . . . . . . . . . . 55 98 14. Example of a full deposit using the XML model only . . . . . . 55 99 15. Example of differential deposit using the XML model only . . . 60 100 16. Data escrow agent extended verification process . . . . . . . 62 101 17. Data escrow notifications . . . . . . . . . . . . . . . . . . 62 102 17.1. Notifications from Registry Operators to Third Parties . . 62 103 17.2. Notifications from Data Escrow Agents to Third Parties . . 64 104 18. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66 105 18.1. Normative References . . . . . . . . . . . . . . . . . . . 66 106 18.2. Informative References . . . . . . . . . . . . . . . . . . 67 107 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 68 109 1. Introduction 111 This document defines the data escrow structure of the standard set 112 of objects for a Domain Name Registry which include: 114 o Domain: Internet domain names that are typically provisioned in a 115 Domain Name Registry using the EPP domain name mapping [RFC5731]. 116 The attributes defined in the EPP domain name mapping [RFC5731] 117 are fully supported by this document. 119 o Host: Internet host names that are typically provisioned in a 120 Domain Name Registry using the EPP host mapping [RFC5732]. The 121 attributes defined in the EPP host mapping [RFC5732] are fully 122 supported by this document. 124 o Contact: Individual or organization social information provisioned 125 in a Domain Name Registry using the EPP contact mapping [RFC5733]. 126 The attributes defined in the EPP contact mapping [RFC5733] are 127 fully supported by this document. 129 o Registrar: The organization that sponsors objects like domains, 130 hosts, and contacts in a Domain Name Registry. 132 o NNDN (NNDN's not domain name): A lightweight domain-like object 133 that is not linked to a Registrar. 135 This document defines the following pseudo-objects: 137 o IDN practices: Internationalized Domain Names (IDN) included in 138 the Domain Object Data Escrow include references to the languages 139 rules that define the set of character code points allowed for a 140 specific language. 142 o EPP parameters: Definition of the specific EPP parameters 143 supported by the Registry Operator. 145 o Header: Used to specify counters of objects in the SRS database at 146 a certain point in time (watermark). 148 o Policy: Used to specify OPTIONAL elements from this specification 149 that are REQUIRED based on the business model of the registry. 151 2. Models 153 This document defines two different models that can be used to 154 deposit data escrow objects: 156 o XML: The XML model includes all of the deposit information (meta- 157 data and data) in an XML document. The definition of the XML 158 format is fully defined in the XML schemas. 160 o CSV: The CSV model uses XML to define the data escrow format of 161 the data contained in referenced Comma-Separated Values (CSV) 162 files. 164 The data escrow deposit MAY contain a mix of both models but an 165 object MUST be escrowed only in one model. 167 3. Terminology 169 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 170 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 171 document are to be interpreted as described in BCP 14, [RFC2119]. 173 REGISTRY. In the context of this draft the definition will be 174 overloaded (from the definition in the base protocol) to indicate an 175 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 176 NAME. 178 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 179 or any other domain name at any level in the DNS tree for which a 180 Registry (either directly or through and affiliate company) provides 181 Registry Services for other organizations or individuals. For 182 example: .COM, .ORG, .BIZ, .CO.JP, .B.BR. 184 REGISTRY SERVICES. Services offered by the Registry critical to the 185 following tasks: the provisioning of domain names on receipt of 186 requests and data from registrars; responding to registrar queries 187 for status information relating to the DNS servers for the RCDN; 188 dissemination of RCDN zone files; operation of the Registry DNS 189 servers; and responding to queries for contact and other information 190 concerning DNS registrations in the RCDN. Any other products or 191 services that only a Registry is capable of providing, by reason of 192 its designation as the Registry. Typical examples of Registry 193 Services are: DNS resolution for the RCDN, WHOIS and EPP. 195 ALLOCATED. A status of some label with respect to a zone, whereby 196 the label is associated administratively to some entity that has 197 requested the label. This term (and its cognates "allocation" and 198 "to allocate") may represents the first step on the way to delegation 199 in the DNS. 201 4. General Conventions 203 4.1. Date and Time 205 Numerous fields indicate "dates", such as the creation and expiry 206 dates for domain names. These fields SHALL contain timestamps 207 indicating the date and time in UTC as specified in [RFC3339], with 208 no offset from the zero meridian. 210 4.2. Country names 212 Country identifiers SHALL be represented using two character 213 identifiers as specified in [ISO-3166-1]. 215 4.3. Telephone numbers 217 Telephone numbers (both voice and facsimile) SHALL be formatted based 218 on structures defined in [ITU-E164]. Telephone numbers described in 219 this specification are character strings that MUST begin with a plus 220 sign ("+", ASCII value 0x002B), followed by a country code defined in 221 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 222 a sequence of digits representing the telephone number. 224 4.4. IP addresses 226 IP addresses syntax MUST conform to the text representation of either 227 of, Internet Protocol [RFC0791], for IPv4 addresses, or IP Version 6 228 Addressing Architecture [RFC4291], for IPv6 addresses. 230 5. Object Description 232 This section describes the base objects supported by this 233 specification: 235 5.1. RDE Domain object 237 The RDE domain object is based on the EPP domain name mapping 238 specified in [RFC5731]. There are two elements used in this format 239 related to domains: the domain object per se, used inside the 240 element and the object used inside the 241 element. 243 5.1.1. object 245 The domain element is based on the EPP domain response for an 246 authorized client (see Section 3.1.2. of [RFC5731]) with additional 247 data from an EPP Query Response, see Section 3.1.3. of 249 [RFC5731], RGP status from [RFC3915], and data from the EPP command, see Section 5.2.1. of [RFC5910]. 252 A element substitutes for the abstract 253 element to define a concrete definition of a domain. The 254 element can be replaced by other domain definitions 255 using the XML schema substitution groups feature. 257 The element contains the following child elements: 259 o A element that contains the fully qualified name of the 260 domain name object. 262 o A element that contains the repository object identifier 263 assigned to the domain name object when it was created. 265 o An OPTIONAL element that contains the name of the domain 266 name in Unicode character set. It MUST be provided if available. 268 o An OPTIONAL element that references the IDN Table 269 used for the IDN. This corresponds to the "id" attribute of the 270 element. This element MUST be present if the domain 271 name is an IDN. 273 o An OPTIONAL element is used to indicate that the 274 domain name is an IDN variant. This element contains the domain 275 name used to generate the IDN variant. 277 o One or more elements that contain the current status 278 descriptors associated with the domain name. 280 o Zero or more OPTIONAL element to represent 281 "pendingDelete" sub-statuses, including "redemptionPeriod", 282 "pendingRestore", and "pendingDelete", that a domain name can be 283 in as a result of grace period processing as specified in 284 [RFC3915]. 286 o An OPTIONAL element that contain the identifier for 287 the human or organizational social information object associated 288 as the holder of the domain name object. 290 o Zero or more OPTIONAL elements that contain identifiers 291 for the human or organizational social information objects 292 associated with the domain name object. 294 o An OPTIONAL element that contains the fully qualified names 295 of the delegated host objects or host attributes (name servers) 296 associated with the domain name object. See Section 1.1 of 298 [RFC5731] for a description of the elements used to specify host 299 objects or host attributes. 301 o A element that contains the identifier of the sponsoring 302 registrar. 304 o A element that contains the identifier of the registrar 305 that created the domain name object. An OPTIONAL client attribute 306 is used to specify the client that performed the operation. 308 o An OPTIONAL element that contains the date and time of 309 the domain name object creation. This element MUST be present if 310 the domain name has been allocated. 312 o An OPTIONAL element that contains the date and time 313 identifying the end (expiration) of the domain name object's 314 registration period. This element MUST be present if the domain 315 name has been allocated. 317 o An OPTIONAL element that contains the identifier of the 318 registrar that last updated the domain name object. This element 319 MUST NOT be present if the domain has never been modified. An 320 OPTIONAL client attribute is used to specify the client that 321 performed the operation. 323 o An OPTIONAL element that contains the date and time of 324 the most recent domain-name-object modification. This element 325 MUST NOT be present if the domain name object has never been 326 modified. 328 o An OPTIONAL element that contains the public key 329 information associated with Domain Name System security (DNSSEC) 330 extensions for the domain name as specified in [RFC5910]. 332 o An OPTIONAL element that contains the date and time of 333 the most recent domain object successful transfer. This element 334 MUST NOT be present if the domain name object has never been 335 transfered. 337 o An OPTIONAL element that contains the following child 338 elements related to the last transfer request of the domain name 339 object. This element MUST NOT be present if a transfer request 340 for the domain name has never been created. 342 * A element that contains the state of the most recent 343 transfer request. 345 * A element that contains the identifier of the registrar 346 that requested the domain name object transfer. An OPTIONAL 347 client attribute is used to specify the client that performed 348 the operation. 350 * A element that contains the date and time that the 351 transfer was requested. 353 * An element that contains the identifier of the registrar 354 that SHOULD act upon a PENDING transfer request. For all other 355 status types, the value identifies the registrar that took the 356 indicated action. An OPTIONAL client attribute is used to 357 specify the client that performed the operation. 359 * An element that contains the date and time of a 360 required or completed response. For a PENDING request, the 361 value identifies the date and time by which a response is 362 required before an automated response action will be taken by 363 the registry. For all other status types, the value identifies 364 the date and time when the request was completed. 366 * An OPTIONAL element that contains the end of the 367 domain name object's validity period (expiry date) if the 368 transfer caused or causes a change in the validity period. 370 Example of a domain object: 372 ... 373 374 example1.test 375 Dexample1-TEST 376 377 jd1234 378 sh8013 379 sh8013 380 381 ns1.example.com 382 ns1.example1.test 383 384 RegistrarX 385 RegistrarX 386 1999-04-03T22:00:00.0Z 387 2015-04-03T22:00:00.0Z 388 389 ... 391 5.1.2. object 393 The element contains the fully qualified domain 394 name that was deleted and purged. 396 Example of object: 398 ... 399 400 ... 401 402 foo.test 403 bar.test 404 405 ... 406 407 ... 409 5.2. RDE Host object 411 The RDE host object is based on the EPP host name mapping in 412 [RFC5732]. There are two elements used in this format related to 413 hosts: the host object per se, used inside the element and 414 the object used inside the element. 416 A element substitutes for the abstract element 417 to define a concrete definition of a host. The 418 element can be replaced by other host definitions using the XML 419 schema substitution groups feature. 421 5.2.1. object 423 The RDE host object is based on the EPP host response for an 424 authorized client (Section 3.1.2. of [RFC5732]). 426 The OPTIONAL element contains the following child elements: 428 o A element that contains the fully qualified name of the 429 host object. 431 o A element that contains the repository object identifier 432 assigned to the host object when the object was created. 434 o One or more elements that describe the status of the host 435 object. 437 o Zero or more elements that contain the IP addresses 438 associated with the host object. 440 o A element that contains the identifier of the sponsoring 441 registrar. 443 o A element that contains the identifier of the registrar 444 that created the host object. An OPTIONAL client attribute is 445 used to specify the client that performed the operation. 447 o A element that contains the date and time of host-object 448 creation. 450 o An OPTIONAL element that contains the identifier of the 451 registrar that last updated the host object. This element MUST 452 NOT be present if the host object has never been modified. An 453 OPTIONAL client attribute is used to specify the client that 454 performed the operation. 456 o An OPTIONAL element that contains the date and time of 457 the most recent host-object modification. This element MUST NOT 458 be present if the host object has never been modified. 460 o An OPTIONAL element that contains the date and time of 461 the most recent host object successful transfer. This element 462 MUST NOT be present if the domain name object has never been 463 transfered. 465 Example of object: 467 ... 468 469 ns1.example1.test 470 Hns1_example_test-TEST 471 472 473 192.0.2.2 474 192.0.2.29 475 1080:0:0:0:8:800:200C:417A 476 RegistrarX 477 RegistrarX 478 1999-05-08T12:10:00.0Z 479 RegistrarX 480 2009-10-03T09:34:00.0Z 481 482 ... 484 5.2.2. object 486 The element contains the fully qualified domain name 487 of a host that was deleted. 489 Example of object: 491 ... 492 493 ... 494 495 ns1.example.test 496 497 ... 498 499 ... 501 5.3. RDE Contact object 503 The RDE contact object is based on the EPP contact name mapping in 504 [RFC5733]. There are two elements used in this format related to 505 contacts: the contact object per se, used inside the 506 element and the object used inside the 507 element. 509 A element substitutes for the abstract 510 element to define a concrete definition of a contact. The 511 element can be replaced by other contact 512 definitions using the XML schema substitution groups feature. 514 5.3.1. object 516 The contact object is based on the EPP contact response for an 517 authorized client (Section 3.1.2. of [RFC5733]) with some additions 518 including the data from an EPP Query Response, see Section 519 3.1.3. of [RFC5733]. 521 The OPTIONAL element contains the following child elements: 523 o A element that contains the server-unique identifier of the 524 contact object 526 o A element that contains the Repository Object IDentifier 527 assigned to the contact object when the object was created. 529 o One or more elements that describe the status of the 530 contact object. 532 o One or two elements that contain postal-address 533 information. Two elements are provided so that address 534 information can be provided in both internationalized and 535 localized forms; a "type" attribute is used to identify the two 536 forms. If an internationalized form (type="int") is provided, 537 element content MUST be represented in a subset of UTF-8 that can 538 be represented in the 7-bit US-ASCII character set. If a 539 localized form (type="loc") is provided, element content MAY be 540 represented in unrestricted UTF-8. The element 541 contains the following child elements: 543 * A element that contains the name of the individual or 544 role represented by the contact. 546 * An OPTIONAL element that contains the name of the 547 organization with which the contact is affiliated. 549 * An element that contains address information associated 550 with the contact. An element contains the following 551 child elements: 553 + One, two, or three OPTIONAL elements that contain 554 the contact's street address. 556 + A element that contains the contact's city. 558 + An OPTIONAL element that contains the contact's state 559 or province. 561 + An OPTIONAL element that contains the contact's postal 562 code. 564 + A element that contains the contact's two-letter 565 country code. 567 o An OPTIONAL element that contains the contact's voice 568 telephone number. 570 o An OPTIONAL element that contains the contact's facsimile 571 telephone number. 573 o An element that contains the contact's email address. 575 o A element that contains the identifier of the sponsoring 576 registrar. 578 o A element that contains the identifier of the registrar 579 that created the contact object. An OPTIONAL client attribute is 580 used to specify the client that performed the operation. 582 o A element that contains the date and time of contact- 583 object creation. 585 o An OPTIONAL element that contains the identifier of the 586 registrar that last updated the contact object. This element MUST 587 NOT be present if the contact has never been modified. An 588 OPTIONAL client attribute is used to specify the client that 589 performed the operation. 591 o An OPTIONAL element that contains the date and time of 592 the most recent contact-object modification. This element MUST 593 NOT be present if the contact object has never been modified. 595 o An OPTIONAL element that contains the date and time of 596 the most recent contact object successful transfer. This element 597 MUST NOT be present if the contact object has never been 598 transferred. 600 o An OPTIONAL element that contains the following child 601 elements related to the last transfer request of the contact 602 object: 604 * A element that contains the state of the most recent 605 transfer request. 607 * A element that contains the identifier of the registrar 608 that requested the domain name object transfer. An OPTIONAL 609 client attribute is used to specify the client that performed 610 the operation. 612 * An element that contains the identifier of the registrar 613 that SHOULD act upon a PENDING transfer request. For all other 614 status types, the value identifies the registrar that took the 615 indicated action. An OPTIONAL client attribute is used to 616 specify the client that performed the operation. 618 * A element that contains the date and time that the 619 transfer was requested. 621 * An element that contains the date and time of a 622 required or completed response. For a PENDING request, the 623 value identifies the date and time by which a response is 624 required before an automated response action will be taken by 625 the registry. For all other status types, the value identifies 626 the date and time when the request was completed. 628 o An OPTIONAL element that identifies elements that 629 requiring exceptional server-operator handling to allow or 630 restrict disclosure to third parties. See Section 2.9 of 631 [RFC5733] for a description of the child elements contained within 632 the element. 634 Example object: 636 ... 637 638 Csh8013-TEST 639 sh8013 640 641 642 643 John Doe 644 Example Inc. 645 646 123 Example Dr. 647 Suite 100 648 Dulles 649 VA 650 20166-6503 651 US 652 653 654 +1.7035555555 655 +1.7035555556 656 jdoe@example.test 657 RegistrarX 658 RegistrarX 659 2009-09-13T08:01:00.0Z 660 RegistrarX 661 2009-11-26T09:10:00.0Z 662 2009-12-03T09:05:00.0Z 663 664 pending 665 clientW 666 2011-03-08T19:38:00.0Z 667 RegistrarX 668 2011-03-13T23:59:59.0Z 669 670 671 672 673 674 675 ... 677 5.3.2. object 679 The element contains the id of a contact that was 680 deleted. 682 Example of object: 684 ... 685 686 ... 687 688 sh8013-TEST 689 co8013-TEST 690 691 ... 692 693 ... 695 5.4. RDE Registrar object 697 The RDE registrar object is the sponsoring client of other RDE 698 objects, for operational purposes MAY be the registry operator. 699 There are two elements used in this format related to registrars: the 700 registrar object per se, used inside the element and the 701 object used inside the element. 703 A element substitutes for the 704 abstract element to define a concrete definition of a registrar. The 705 element can be replaced by other domain 706 definitions using the XML schema substitution groups feature. 708 5.4.1. object 710 The element contains the following child elements: 712 o An element that contains the Registry-unique identifier of 713 the registrar object. This has a superordinate relationship 714 to a subordinate , or of domain, contact and 715 host objects. 717 o An element that contains the name of the registrar. 719 o An OPTIONAL element that contains the ID assigned by 720 ICANN. 722 o A element that contains the operational status of the 723 registrar. Possible values are: ok, readonly and terminated. 725 o One or two elements that contain postal- address 726 information. Two elements are provided so that address 727 information can be provided in both internationalized and 728 localized forms; a "type" attribute is used to identify the two 729 forms. If an internationalized form (type="int") is provided, 730 element content MUST be represented in a subset of UTF-8 that can 731 be represented in the 7-bit US-ASCII character set. If a 732 localized form (type="loc") is provided, element content MAY be 733 represented in unrestricted UTF-8. The element 734 contains the following child elements: 736 * A element that contains address information associated 737 with the registrar. The element contains the following 738 child elements: 740 + One, two, or three OPTIONAL elements that contain 741 the registrar's street address. 743 + A element that contains the registrar's city. 745 + An OPTIONAL element that contains the registrar's state 746 or province. 748 + An OPTIONAL element that contains the registrar's 749 postal code. 751 + A element that contains the registrar's country code. 753 o An OPTIONAL element that contains the registrar's voice 754 telephone number. 756 o An OPTIONAL element that contains the registrar's facsimile 757 telephone number. 759 o An element that contains the registrar's email address. 761 o An OPTIONAL element that contains the registrar's URL. 763 o An OPTIONAL elements that contains whois information. 764 The element contains the following child elements: 766 * An OPTIONAL element that contains the name of the 767 registrar WHOIS server listening on TCP port 43 as specified in 768 [RFC3912]. 770 * An OPTIONAL element that contains the name of the 771 registrar WHOIS server listening on TCP port 80/443. 773 o A element that contains the date and time of registrar- 774 object creation. 776 o An OPTIONAL element that contains the date and time of 777 the most recent RDE registrar-object modification. This element 778 MUST NOT be present if the rdeRegistrar object has never been 779 modified. 781 Example of object: 783 ... 784 785 RegistrarX 786 Registrar X 787 123 788 ok 789 790 791 123 Example Dr. 792 Suite 100 793 Dulles 794 VA 795 20166-6503 796 US 797 798 799 +1.7035555555 800 +1.7035555556 801 jdoe@example.test 802 http://www.example.test 803 804 whois.example.test 805 http://whois.example.test 806 807 2005-04-23T11:49:00.0Z 808 2009-02-17T17:51:00.0Z 809 810 ... 812 5.4.2. object 814 The element contains the id of a registrar that 815 was deleted. 817 Example of object: 819 ... 820 821 ... 822 823 agnt0001-TEST 824 825 ... 826 827 ... 829 5.5. RDE IDN Practices 831 The RDE Internationalized Domain Names (IDN) Practices reference is a 832 pseudo-object that is used to provide a short reference to the IDN 833 Table and Policy used in IDN registrations. The 834 element has an "id" attribute that is used to uniquely identify an 835 IDN Table stored externally. 837 5.5.1. object 839 The OPTIONAL contains the following elements. An id 840 attribute is used to specify an identifier for the IDN table. 842 o An element that contains the URL of the IDN table that is 843 being referenced. 845 o A element that contains the URL of the IDN policy 846 document. If IDN variants are generated algorithmically, the 847 policy document MUST define the algorithm and the state of the 848 implicit generated IDN variants. For a list of suggested states 849 for implicit IDN variants, please see [variantTLDsReport]. 851 Example of object: 853 ... 854 855 856 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 857 858 859 http://registro.br/dominio/regras.html 860 861 862 ... 864 5.6. RDE NNDN 866 A NNDN (NNDN's not domain name) does not exist as a domain object, 867 however it is stored in the SRS database. NNDNs can optionally be 868 used to store registry reserved names or (blocked or withheld) IDN 869 variants. A NNDN is a lightweight domain-like object that is not 870 linked to a Registrar. A FQDN can only exists as a domain name or 871 NNDN, but not both. 873 A element substitutes for the abstract element 874 to define a concrete definition of a NNDN. The 875 element can be replaced by other NNDN definitions using the XML 876 schema substitution groups feature. 878 5.6.1. object 880 The OPTIONAL element contains the following child elements: 882 o An element that contains the A-label of the NNDN. 884 o An OPTIONAL element that contains the name of the NNDN in 885 Unicode character set. It MUST be provided if available. 887 o An OPTIONAL element that references the IDN Table 888 used for the NNDN. This corresponds to the "id" attribute of the 889 element. This element MUST be present if the NNDN 890 is an IDN. 892 o An OPTIONAL element is used to indicate that the 893 NNDN is an IDN variant. This element contains the domain name 894 used to generate the IDN variant. 896 o A element that indicates the state of the NNDN: 897 blocked or withheld. 899 * If a NNDN is considered undesirable for registration (i.e., 900 unavailable for allocation to anyone), then the NNDN will be 901 tagged as "blocked". 903 * If a NNDN is considered a potential registration of a domain 904 object for a particular registrant then the NNDN will be tagged 905 as "withheld". 907 o A element that contains the date and time of the NNDN 908 object creation. 910 Example of object: 912 ... 913 914 xn--exampl-gva.test 915 pt-BR 916 Dexample1-TEST 917 withheld 918 2005-04-23T11:49:00.0Z 919 920 ... 922 5.6.2. object 924 The element contains the ACE of a NNDN that was 925 deleted, i.e., the . 927 Example of object: 929 ... 930 931 ... 932 933 xn--pingino-q2a.test 934 935 ... 936 937 ... 939 5.7. RDE EPP Parameters object 941 An OPTIONAL element contains some EPP parameters that may 942 be helpful when rebuilding a registry from the escrow deposits. The 943 element SHOULD be included in Deposits if the registry uses EPP. 945 The syntax and content of the children elements is as 946 explained in section 2.4 of [RFC5730]. The children of the 947 are as follows: 949 o One or more elements that indicate the EPP versions 950 supported by the registry. 952 o One or more elements that indicate the identifiers of the 953 text response languages supported by the registry's EPP server. 955 o One or more elements that contain namespace URIs 956 representing the objects that the registry's EPP server is capable 957 of managing. 959 o An OPTIONAL element that contains one or more 960 elements that contain namespace URIs representing object 961 extensions supported by the registry's EPP server. 963 o A element that contains child elements used to describe the 964 server's privacy policy for data collection and management. See 965 section 2.4 of [RFC5730] for more details. 967 Example of element object: 969 ... 970 971 1.0 972 en 973 urn:ietf:params:xml:ns:domain-1.0 974 975 urn:ietf:params:xml:ns:contact-1.0 976 977 urn:ietf:params:xml:ns:host-1.0 978 979 980 urn:ietf:params:xml:ns:rgp-1.0 981 urn:ietf:params:xml:ns:secDNS-1.1 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 ... 1002 5.8. RDE Policy object 1004 The RDE Policy is a pseudo-object that is used to specify which 1005 OPTIONAL elements from this specification are REQUIRED based on the 1006 business model of the registry. 1008 5.8.1. object 1010 The OPTIONAL contains the following attributes: 1012 o that defines that the referenced is REQUIRED. 1014 o that defines the XPath of the element referenced by 1015 . 1017 Example of object: 1019 ... 1020 1022 ... 1024 5.9. Header object 1026 The RDE Header is a pseudo-object that is used to specify the number 1027 of objects in the SRS at a specific point in time (watermark) 1028 regardless of the type of deposit: differential, full or incremental. 1030 5.9.1.
object 1032 The
contains the following attributes: 1034 o A element that defines TLD being escrowed. 1036 o A element that number of objects being escrowed. An uri 1037 attribute is used to define the type of object. 1039 Example of
object: 1041 ... 1042 1043 test 1044 2 1046 1 1048 1 1050 1 1052 1053 1 1055 1 1057 1 1059 1060 1061 ... 1063 6. RDE IDN Variants handling 1065 Depending on the Registration Policy of the Registry; for a 1066 particular domain name there may be multiple variant names. See 1067 [variantTLDsReport] for further detail on IDN variants. 1069 A registry could choose to escrow IDN variants as domains or NNDN 1070 objects. 1072 A NNDN or a domain name are explicit representations of an IDN 1073 variant while an IDN variant computed based on an algorithm is an 1074 implicit representation. Explicit representation of an IDN variant 1075 takes precedence over an implicit representation. 1077 7. Profile 1079 Different business models of registries exist, therefore the registry 1080 is responsible to define a profile that matches its particular 1081 business model. The profile mechanism allows a registry to extend 1082 this specification. 1084 A profile is the process of: 1086 1. Extending base objects with the mechanisms defined for XML and 1087 CSV models. 1089 * In the case of the XML model, abstract elements could be use 1090 to extend the following objects: , , , 1091 and using XML schema substitution groups 1092 feature. 1094 2. Defining a object to specify which OPTIONAL elements of 1095 this base specification are required based on the business model 1096 of the registry. An example is the element that is 1097 usually REQUIRED but it is specified as OPTIONAL in this 1098 specification to support existing business models. 1100 3. Adding new escrowed objects using the and elements. 1103 4. Providing the XML schemas to third parties that require them to 1104 validate the escrow deposits. 1106 8. Formal Syntax 1108 Seven schemas are presented here. The first schema is the base RDE 1109 schema. The second schema defines domain object for RDE. The third 1110 schema defines host object for RDE. The fourth schema defines 1111 contact object for RDE. The fifth schema defines registrar object 1112 for RDE. The sixth schema defines the idnTableRef and IDN objects. 1113 The last schema defines the eppParams objects. 1115 8.1. RDE Domain Object 1117 Copyright (c) 2011 IETF Trust and the persons identified as authors 1118 of the code. All rights reserved. 1120 Redistribution and use in source and binary forms, with or without 1121 modification, are permitted provided that the following conditions 1122 are met: 1124 o Redistributions of source code must retain the above copyright 1125 notice, this list of conditions and the following disclaimer. 1127 o Redistributions in binary form must reproduce the above copyright 1128 notice, this list of conditions and the following disclaimer in 1129 the documentation and/or other materials provided with the 1130 distribution. 1132 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1133 names of specific contributors, may be used to endorse or promote 1134 products derived from this software without specific prior written 1135 permission. 1137 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1138 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1139 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1140 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1141 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1142 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1143 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1144 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1145 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1146 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1147 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1149 BEGIN 1150 1151 1161 1163 1165 1167 1169 1172 1173 1174 Registry Data Escrow Domain provisioning schema 1175 1176 1178 1181 1182 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1196 1198 1200 1202 1204 1205 1206 1207 1208 1209 1210 1211 1213 1214 1216 1217 1218 1219 1221 1222 1223 1224 1225 1226 1227 1228 1230 1231 1233 1234 1235 1236 1237 1238 1240 1241 1242 1243 1244 1245 END 1247 8.2. RDE Host Object 1249 Copyright (c) 2011 IETF Trust and the persons identified as authors 1250 of the code. All rights reserved. 1252 Redistribution and use in source and binary forms, with or without 1253 modification, are permitted provided that the following conditions 1254 are met: 1256 o Redistributions of source code must retain the above copyright 1257 notice, this list of conditions and the following disclaimer. 1259 o Redistributions in binary form must reproduce the above copyright 1260 notice, this list of conditions and the following disclaimer in 1261 the documentation and/or other materials provided with the 1262 distribution. 1264 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1265 names of specific contributors, may be used to endorse or promote 1266 products derived from this software without specific prior written 1267 permission. 1269 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1270 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1271 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1272 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1273 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1274 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1275 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1276 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1277 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1278 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1279 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1281 BEGIN 1282 1283 1291 1293 1295 1298 1299 1300 Registry Data Escrow Host provisioning schema 1301 1302 1304 1306 1309 1310 1311 1312 1313 1314 1315 1316 1317 1319 1320 1321 1322 1323 1324 1325 1327 1328 1329 1331 1332 1333 1334 1335 1336 1338 1339 1340 1341 1342 1343 END 1345 8.3. RDE Contact Object 1347 Copyright (c) 2011 IETF Trust and the persons identified as authors 1348 of the code. All rights reserved. 1350 Redistribution and use in source and binary forms, with or without 1351 modification, are permitted provided that the following conditions 1352 are met: 1354 o Redistributions of source code must retain the above copyright 1355 notice, this list of conditions and the following disclaimer. 1357 o Redistributions in binary form must reproduce the above copyright 1358 notice, this list of conditions and the following disclaimer in 1359 the documentation and/or other materials provided with the 1360 distribution. 1362 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1363 names of specific contributors, may be used to endorse or promote 1364 products derived from this software without specific prior written 1365 permission. 1367 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1368 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1369 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1370 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1371 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1372 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1373 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1374 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1375 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1376 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1377 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1379 BEGIN 1380 1381 1389 1390 1392 1394 1397 1398 1399 Registry Data Escrow contact provisioning schema 1400 1401 1403 1405 1407 1410 1411 1412 1413 1414 1415 1416 1417 1419 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1432 1434 1435 1436 1437 1439 1440 1441 1442 1443 1444 1445 1446 1447 1449 1450 1451 1452 1453 1454 1456 1457 1458 1459 1460 1461 END 1463 8.4. RDE Registrar Object 1465 Copyright (c) 2011 IETF Trust and the persons identified as authors 1466 of the code. All rights reserved. 1468 Redistribution and use in source and binary forms, with or without 1469 modification, are permitted provided that the following conditions 1470 are met: 1472 o Redistributions of source code must retain the above copyright 1473 notice, this list of conditions and the following disclaimer. 1475 o Redistributions in binary form must reproduce the above copyright 1476 notice, this list of conditions and the following disclaimer in 1477 the documentation and/or other materials provided with the 1478 distribution. 1480 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1481 names of specific contributors, may be used to endorse or promote 1482 products derived from this software without specific prior written 1483 permission. 1485 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1486 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1487 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1488 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1489 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1490 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1491 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1492 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1493 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1494 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1495 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1497 BEGIN 1498 1499 1508 1509 1511 1513 1515 1518 1519 1520 Registry Data Escrow registrar provisioning schema 1521 1522 1524 1527 1529 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1543 1544 1545 1546 1547 1549 1550 1551 1552 1553 1554 1556 1557 1558 1559 1560 1561 1563 1564 1565 1566 1567 1568 1569 1571 1572 1573 1574 1575 1577 1579 1580 1581 1582 1583 1584 1586 1587 1588 1590 1591 1593 1594 1595 1596 1598 1599 1600 1601 1602 1603 1605 1606 1607 1608 1609 1611 1612 1613 1615 1616 1618 1619 1620 1621 1622 1624 1625 1626 1627 1628 1629 1631 1632 1633 1634 1635 1636 1638 1639 1640 1641 1642 1643 END 1645 8.5. RDE IDN and IDN Table Reference Objects 1647 Copyright (c) 2011 IETF Trust and the persons identified as authors 1648 of the code. All rights reserved. 1650 Redistribution and use in source and binary forms, with or without 1651 modification, are permitted provided that the following conditions 1652 are met: 1654 o Redistributions of source code must retain the above copyright 1655 notice, this list of conditions and the following disclaimer. 1657 o Redistributions in binary form must reproduce the above copyright 1658 notice, this list of conditions and the following disclaimer in 1659 the documentation and/or other materials provided with the 1660 distribution. 1662 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1663 names of specific contributors, may be used to endorse or promote 1664 products derived from this software without specific prior written 1665 permission. 1667 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1668 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1669 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1670 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1671 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1672 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1673 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1674 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1675 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1676 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1677 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1679 BEGIN 1680 1681 1687 1690 1691 1692 Registry Data Escrow IDN provisioning schema 1693 1694 1696 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1712 1713 1714 1715 1716 1718 1719 END 1721 8.6. EPP Parameters Object 1723 Copyright (c) 2011 IETF Trust and the persons identified as authors 1724 of the code. All rights reserved. 1726 Redistribution and use in source and binary forms, with or without 1727 modification, are permitted provided that the following conditions 1728 are met: 1730 o Redistributions of source code must retain the above copyright 1731 notice, this list of conditions and the following disclaimer. 1733 o Redistributions in binary form must reproduce the above copyright 1734 notice, this list of conditions and the following disclaimer in 1735 the documentation and/or other materials provided with the 1736 distribution. 1738 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1739 names of specific contributors, may be used to endorse or promote 1740 products derived from this software without specific prior written 1741 permission. 1743 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1744 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1745 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1746 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1747 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1748 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1749 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1750 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1751 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1752 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1753 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1755 BEGIN 1756 1757 1765 1767 1769 1772 1773 1774 Registry Data Escrow EPP Parameters schema 1775 1776 1778 1779 1782 1783 1786 1787 1788 1789 1790 1792 1793 1794 1796 1797 1798 1799 1800 1801 1802 END 1804 8.7. NNDN Object 1806 Copyright (c) 2011 IETF Trust and the persons identified as authors 1807 of the code. All rights reserved. 1809 Redistribution and use in source and binary forms, with or without 1810 modification, are permitted provided that the following conditions 1811 are met: 1813 o Redistributions of source code must retain the above copyright 1814 notice, this list of conditions and the following disclaimer. 1816 o Redistributions in binary form must reproduce the above copyright 1817 notice, this list of conditions and the following disclaimer in 1818 the documentation and/or other materials provided with the 1819 distribution. 1821 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1822 names of specific contributors, may be used to endorse or promote 1823 products derived from this software without specific prior written 1824 permission. 1826 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1827 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1828 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1829 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1830 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1831 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1832 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1833 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1834 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1835 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1836 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1838 BEGIN 1839 1840 1847 1849 1852 1853 1854 Registry Data Escrow NNDN provisioning schema 1855 1856 1858 1860 1861 1864 1865 1866 1867 1868 1869 1870 1871 1872 1874 1875 1876 1877 1878 1879 1881 1882 1883 1884 1885 1886 1888 1889 1890 1891 1892 1893 1895 1896 1897 1898 1899 1900 END 1902 8.8. Policy Object 1904 Copyright (c) 2011 IETF Trust and the persons identified as authors 1905 of the code. All rights reserved. 1907 Redistribution and use in source and binary forms, with or without 1908 modification, are permitted provided that the following conditions 1909 are met: 1911 o Redistributions of source code must retain the above copyright 1912 notice, this list of conditions and the following disclaimer. 1914 o Redistributions in binary form must reproduce the above copyright 1915 notice, this list of conditions and the following disclaimer in 1916 the documentation and/or other materials provided with the 1917 distribution. 1919 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1920 names of specific contributors, may be used to endorse or promote 1921 products derived from this software without specific prior written 1922 permission. 1924 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1925 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1926 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1927 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1928 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1929 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1930 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1931 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1932 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1933 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1934 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1936 BEGIN 1937 1938 1944 1945 1946 Registry Data Escrow Policy schema 1947 1948 1950 1953 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 END 1967 8.9. Header Object 1969 Copyright (c) 2011 IETF Trust and the persons identified as authors 1970 of the code. All rights reserved. 1972 Redistribution and use in source and binary forms, with or without 1973 modification, are permitted provided that the following conditions 1974 are met: 1976 o Redistributions of source code must retain the above copyright 1977 notice, this list of conditions and the following disclaimer. 1979 o Redistributions in binary form must reproduce the above copyright 1980 notice, this list of conditions and the following disclaimer in 1981 the documentation and/or other materials provided with the 1982 distribution. 1984 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1985 names of specific contributors, may be used to endorse or promote 1986 products derived from this software without specific prior written 1987 permission. 1989 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1990 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1991 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1992 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1993 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1994 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1995 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1996 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1997 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1998 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1999 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2001 BEGIN 2002 2003 2010 2012 2015 2016 2017 Registry Data Escrow Header schema 2018 2019 2021 2022 2025 2026 2027 2028 2029 2030 2031 2033 2034 2035 2036 2038 2039 2040 2041 2042 2043 2044 2045 2046 END 2048 8.10. Report Object 2050 Copyright (c) 2011 IETF Trust and the persons identified as authors 2051 of the code. All rights reserved. 2053 Redistribution and use in source and binary forms, with or without 2054 modification, are permitted provided that the following conditions 2055 are met: 2057 o Redistributions of source code must retain the above copyright 2058 notice, this list of conditions and the following disclaimer. 2060 o Redistributions in binary form must reproduce the above copyright 2061 notice, this list of conditions and the following disclaimer in 2062 the documentation and/or other materials provided with the 2063 distribution. 2065 o Neither the name of Internet Society, IETF or IETF Trust, nor the 2066 names of specific contributors, may be used to endorse or promote 2067 products derived from this software without specific prior written 2068 permission. 2070 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2071 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2072 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2073 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2074 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2075 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2076 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2077 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2078 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2079 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2080 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2082 BEGIN 2083 2084 2091 2093 2096 2097 2098 Registry Data Escrow Report schema 2099 2100 2102 2103 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 END 2121 8.11. Notification Object 2123 Copyright (c) 2011 IETF Trust and the persons identified as authors 2124 of the code. All rights reserved. 2126 Redistribution and use in source and binary forms, with or without 2127 modification, are permitted provided that the following conditions 2128 are met: 2130 o Redistributions of source code must retain the above copyright 2131 notice, this list of conditions and the following disclaimer. 2133 o Redistributions in binary form must reproduce the above copyright 2134 notice, this list of conditions and the following disclaimer in 2135 the documentation and/or other materials provided with the 2136 distribution. 2138 o Neither the name of Internet Society, IETF or IETF Trust, nor the 2139 names of specific contributors, may be used to endorse or promote 2140 products derived from this software without specific prior written 2141 permission. 2143 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 2144 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 2145 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 2146 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 2147 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 2148 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 2149 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 2150 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 2151 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 2152 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 2153 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 2155 BEGIN 2156 2157 2163 2166 2167 2168 Registry Data Escrow Notification schema 2169 2170 2172 2173 2175 2176 2177 2178 2179 2180 2181 2182 2184 2185 2186 2187 2188 2189 2190 2191 2192 END 2194 9. Internationalization Considerations 2196 Data Escrow deposits are represented in XML, which provides native 2197 support for encoding information using the Unicode character set and 2198 its more compact representations including UTF-8. Conformant XML 2199 processors recognize both UTF-8 and UTF-16. Though XML includes 2200 provisions to identify and use other character encodings through use 2201 of an "encoding" attribute in an declaration, use of UTF-8 is 2202 RECOMMENDED. 2204 10. IANA Considerations 2206 This document uses URNs to describe XML namespaces and XML schemas 2207 conforming to a registry mechanism described in [RFC3688]. Fourteen 2208 URI assignments have been registered by the IANA. 2210 Registration request for the RDE domain namespace: 2212 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 2214 Registrant Contact: See the "Author's Address" section of this 2215 document. 2217 XML: None. Namespace URIs do not represent an XML specification. 2219 Registration request for the RDE domain XML schema: 2221 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 2223 Registrant Contact: See the "Author's Address" section of this 2224 document. 2226 See the "Formal Syntax" section of this document. 2228 Registration request for the RDE host namespace: 2230 URI: urn:ietf:params:xml:ns:rdeHost-1.0 2232 Registrant Contact: See the "Author's Address" section of this 2233 document. 2235 XML: None. Namespace URIs do not represent an XML specification. 2237 Registration request for the RDE host XML schema: 2239 URI: urn:ietf:params:xml:schema:rdeHost-1.0 2241 Registrant Contact: See the "Author's Address" section of this 2242 document. 2244 See the "Formal Syntax" section of this document. 2246 Registration request for the RDE contact namespace: 2248 URI: urn:ietf:params:xml:ns:rdeContact-1.0 2250 Registrant Contact: See the "Author's Address" section of this 2251 document. 2253 XML: None. Namespace URIs do not represent an XML specification. 2255 Registration request for the RDE contact XML schema: 2257 URI: urn:ietf:params:xml:schema:rdeContact-1.0 2259 Registrant Contact: See the "Author's Address" section of this 2260 document. 2262 See the "Formal Syntax" section of this document. 2264 Registration request for the RDE registrar namespace: 2266 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 2268 Registrant Contact: See the "Author's Address" section of this 2269 document. 2271 XML: None. Namespace URIs do not represent an XML specification. 2273 Registration request for the RDE registrar XML schema: 2275 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 2277 Registrant Contact: See the "Author's Address" section of this 2278 document. 2280 See the "Formal Syntax" section of this document. 2282 Registration request for the RDE IDN namespace: 2284 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 2286 Registrant Contact: See the "Author's Address" section of this 2287 document. 2289 XML: None. Namespace URIs do not represent an XML specification. 2291 Registration request for the RDE IDN XML schema: 2293 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 2294 Registrant Contact: See the "Author's Address" section of this 2295 document. 2297 See the "Formal Syntax" section of this document. 2299 Registration request for the RDE EPP parameters namespace: 2301 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 2303 Registrant Contact: See the "Author's Address" section of this 2304 document. 2306 XML: None. Namespace URIs do not represent an XML specification. 2308 Registration request for the RDE EPP parameters XML schema: 2310 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 2312 Registrant Contact: See the "Author's Address" section of this 2313 document. 2315 See the "Formal Syntax" section of this document. 2317 11. Security Considerations 2319 This specification does not define the security mechanisms to be used 2320 in the transmission of the data escrow deposits, since it only 2321 specifies the minimum necessary to enable the rebuilding of a 2322 Registry from deposits without intervention from the original 2323 Registry. 2325 Depending on local policies, some elements or most likely, the whole 2326 deposit will be considered confidential. As such the Registry 2327 transmitting the data to the Escrow Agent SHOULD take all the 2328 necessary precautions like encrypting the data itself and/or the 2329 transport channel to avoid inadvertent disclosure of private data. 2331 It is also of the utmost importance the authentication of the parties 2332 passing data escrow deposit files. The Escrow Agent SHOULD properly 2333 authenticate the identity of the Registry before accepting data 2334 escrow deposits. In a similar manner, the Registry SHOULD 2335 authenticate the identity of the Escrow Agent before submitting any 2336 data. 2338 Additionally, the Registry and the Escrow Agent SHOULD use integrity 2339 checking mechanisms to ensure the data transmitted is what the source 2340 intended. Validation of the contents by the Escrow Agent is 2341 RECOMMENDED to ensure not only the file was transmitted correctly 2342 from the Registry, but also the contents are also "meaningful". 2344 12. Acknowledgments 2346 Parts of this document are based on EPP [RFC5730] and related RFCs by 2347 Scott Hollenbeck. 2349 TBD 2351 13. Change History 2353 [[RFC Editor: Please remove this section.]] 2355 13.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to 2356 -dnrd-objects-mapping-00 2358 1. Added definition for child elements under the element. 2360 2. Added definition for child elements under the element. 2362 3. Added definition for child elements under the element. 2364 4. Rewrote the IDN Variants Handling section to use the variant 2365 states as described in ICANN's Study of Issues Related to the 2366 Management of IDN Variant TLDs. 2368 5. Renamed to in the . 2370 6. Renamed to in the element. 2372 7. Renamed to in the element. 2374 8. Added element under element. 2376 9. Fixed some typographical errors and omissions. 2378 13.2. Changes from version 00 to 01 2380 1. Specify OPTIONAL elements in the draft. 2382 2. Added NNDN object to support list of reserved names and different 2383 IDN variants models. 2385 3. Removed subordinated host element from the domain object. 2387 4. Added eppParams object. 2389 5. Added variantGenerator element to the domain object. 2391 6. Added lgr to the IDN table object. 2393 13.3. Changes from version 01 to 02 2395 1. Updates to the all objects based on feedback from the list. 2397 2. Start of XML and CSV drafts merge. 2399 3. Added header object. 2401 4. Added report object. 2403 5. Added notification object. 2405 6. Added Data Escrow Agent Extended Verification Process section. 2407 7. Added Notifications from Registries to Third Parties. 2409 8. Added Notifications from Data Escrow Agents to Third Parties. 2411 9. Added FULL, DIFF deposit examples using the XML model only. 2413 13.4. Changes from version 02 to 03 2415 1. Remove authinfo from the XML Schema. 2417 2. Resend attribute is now an element 2419 3. Scope attribute added to policy object. 2421 14. Example of a full deposit using the XML model only 2423 Example of a full deposit using the XML model only: 2425 2426 2442 2010-10-17T00:00:00Z 2443 2444 1.0 2445 urn:ietf:params:xml:ns:rdeHeader-1.0 2446 urn:ietf:params:xml:ns:rdeContact-1.0 2447 urn:ietf:params:xml:ns:rdeHost-1.0 2448 urn:ietf:params:xml:ns:rdeDomain-1.0 2449 urn:ietf:params:xml:ns:rdeRegistrar-1.0 2450 urn:ietf:params:xml:ns:rdeIDN-1.0 2451 urn:ietf:params:xml:ns:rdeNNDN-1.0 2452 urn:ietf:params:xml:ns:rdeEppParams-1.0 2453 2455 2456 2457 2458 2459 test 2460 2 2462 1 2464 1 2466 1 2468 2469 1 2471 1 2473 1 2475 2476 2478 2479 2480 example1.test 2481 Dexample1-TEST 2482 2483 jd1234 2484 sh8013 2485 sh8013 2486 2487 ns1.example.com 2488 ns1.example1.test 2489 2490 RegistrarX 2491 RegistrarX 2492 1999-04-03T22:00:00.0Z 2493 2015-04-03T22:00:00.0Z 2494 2496 2497 2498 example2.test 2499 Dexample2-TEST 2500 2501 2502 jd1234 2503 sh8013 2504 sh8013 2505 RegistrarX 2506 RegistrarX 2507 1999-04-03T22:00:00.0Z 2508 2015-04-03T22:00:00.0Z 2509 2511 2512 2513 ns1.example1.test 2514 Hns1_example_test-TEST 2515 2516 2517 192.0.2.2 2518 192.0.2.29 2519 1080:0:0:0:8:800:200C:417A 2520 RegistrarX 2521 RegistrarX 2522 1999-05-08T12:10:00.0Z 2523 RegistrarX 2524 2009-10-03T09:34:00.0Z 2525 2527 2528 2529 sh8013 2530 Csh8013-TEST 2531 2532 2533 2534 John Doe 2535 Example Inc. 2536 2537 123 Example Dr. 2538 Suite 100 2539 Dulles 2540 VA 2541 20166-6503 2542 US 2543 2544 2545 +1.7035555555 2546 +1.7035555556 2547 jdoe@example.test 2548 RegistrarX 2549 RegistrarX 2550 2009-09-13T08:01:00.0Z 2551 RegistrarX 2552 2009-11-26T09:10:00.0Z 2553 2009-12-03T09:05:00.0Z 2554 2555 2556 2557 2558 2560 2561 2562 RegistrarX 2563 Registrar X 2564 123 2565 ok 2566 2567 2568 123 Example Dr. 2569 Suite 100 2570 Dulles 2571 VA 2572 20166-6503 2573 US 2574 2575 2576 +1.7035555555 2577 +1.7035555556 2578 jdoe@example.test 2579 http://www.example.test 2580 2581 whois.example.test 2582 http://whois.example.test 2583 2584 2005-04-23T11:49:00.0Z 2585 2009-02-17T17:51:00.0Z 2586 2588 2589 2590 2591 http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html 2592 2593 2594 http://registro.br/dominio/regras.html 2595 2596 2598 2599 2600 xn--exampl-gva.test 2601 pt-BR 2602 Dexample1-TEST 2603 withheld 2604 2005-04-23T11:49:00.0Z 2605 2607 2608 2609 1.0 2610 en 2611 2612 urn:ietf:params:xml:ns:domain-1.0 2613 2614 2615 urn:ietf:params:xml:ns:contact-1.0 2616 2617 2618 urn:ietf:params:xml:ns:host-1.0 2619 2620 2621 urn:ietf:params:xml:ns:rgp-1.0 2622 urn:ietf:params:xml:ns:secDNS-1.1 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2644 2645 2647 15. Example of differential deposit using the XML model only 2649 Example of a differential deposit using the XML model only: 2651 2652 2667 2010-10-17T00:00:00Z 2668 2669 1.0 2670 urn:ietf:params:xml:ns:rdeHeader-1.0 2671 urn:ietf:params:xml:ns:rdeContact-1.0 2672 urn:ietf:params:xml:ns:rdeHost-1.0 2673 urn:ietf:params:xml:ns:rdeDomain-1.0 2674 urn:ietf:params:xml:ns:rdeRegistrar-1.0 2675 urn:ietf:params:xml:ns:rdeIDN-1.0 2676 urn:ietf:params:xml:ns:rdeNNDN-1.0 2677 urn:ietf:params:xml:ns:rdeEppParams-1.0 2678 2680 2681 2682 2683 example2.test 2684 2685 2687 2688 2689 2690 2691 test 2692 1 2694 1 2696 1 2698 1 2700 2701 1 2703 1 2705 1 2707 2708 2709 2710 2712 16. Data escrow agent extended verification process 2714 The Data Escrow Agent MAY perform a extended verification process 2715 using the contents of data escrow deposits to a point in time 2716 (watermark), last full plus all differentials or last full plus last 2717 incremental escrow deposits. The following are the minimum suggested 2718 tests: 2720 o Validate the escrow deposits using the definition agreed with the 2721 registry. 2723 * In the case of the XML model, the contents of the escrow 2724 deposits MUST be validated using the XML schemas of the 2725 profile. 2727 o Count the objects and validate that number of objects is equal to 2728 the number objects reported in the
element of the escrow 2729 deposit of that point in time (watermark). 2731 o All contacts linked to domain names are present. 2733 o All registrars linked to other objects are present. 2735 o A name exists only as a domain name or NNDN. 2737 o The elements listed in the element are present. 2739 o All idnTableRef definitions linked from other objects are present. 2741 17. Data escrow notifications 2743 Data escrowing involves several parties interacting with the 2744 objective of restoring the operations of a Domain Registry in case of 2745 an emergency. The following section defines several notifications 2746 that are suggested to be sent between the interacting parties. The 2747 parties based on the notification can know the status of the data 2748 escrow deposit even if no access to the data escrow deposit file is 2749 available. 2751 17.1. Notifications from Registry Operators to Third Parties 2753 Registry Operators may need to notify Third Parties that a data 2754 escrow deposit file was sent to the Data Escrow Agent depending on 2755 local policy or contractual requirements. 2757 17.1.1. object 2759 The object is used by Registry Operator to notify Third 2760 Parties about successful delivery of a data escrow deposit to a Data 2761 Escrow Agent. 2763 The element contains the following child elements: 2765 o An element contains the identifier assigned to this report. 2766 It is recommended that the report identifier be the same as the 2767 data escrow deposit identifier. 2769 o An OPTIONAL element that contains to the value of the 2770 resend attribute of the rde deposit. 2772 o A element contains the date and time that the data escrow 2773 deposit was successful received by the data escrow agent. 2775 o An OPTIONAL element contains the date and time that the 2776 data escrow deposit was successfully validated by the data escrow 2777 agent. 2779 o A element is used to identify the kind of deposit: FULL, 2780 INCR (Incremental) or DIFF (Differential). 2782 o A element contains the date and time of the last 2783 FULL data escrow deposit that was successfully validated by the 2784 data escrow agent. 2786 o A element contains the data-time corresponding to the 2787 Timeline Watermark of the deposit. 2789 o A
element contains the header of the data escrow deposit. 2791 Example object: 2793 2794 2797 20101017001 2798 0 2799 2010-10-17T01:51:10.0Z 2800 2010-10-17T02:51:10.0Z 2801 FULL 2802 2010-10-16 2803 2010-10-17T00:00:00Z 2804 2805 test 2806 2 2808 1 2810 1 2812 1 2814 2815 1 2817 1 2819 1 2821 2822 2823 2825 17.2. Notifications from Data Escrow Agents to Third Parties 2827 Data Escrow Agents may need to notify Third Parties that a data 2828 escrow deposit file was received or it is missing for a specific date 2829 depending on local policy or contractual requirements. 2831 17.2.1. object 2833 The object is used by Data Escrow Agents to notify 2834 Third Parties about successful reception/validation of a data escrow 2835 deposit. If multiple deposits are received in a day, a notification 2836 MUST be generated for each deposit that was successfully received 2837 regardless of the result of the verification process performed by the 2838 Data Escrow Agent. 2840 The element contains the following child elements: 2842 o An element contains the reported date. 2844 o A element is used to specify the status of . The 2845 possible values of status are: valid, invalid and missing. 2847 * Valid: The last received data escrow deposit for the specified 2848 date in was successfully validated. 2850 * Invalid: The last received data escrow deposit for the 2851 specified date in was not successfully validated. 2853 * Missing: No data escrow deposit was received on the date 2854 specified in . 2856 o A element it is used by the data escrow agent to provide 2857 extended information about the data escrow deposit. The
2858 element MUST be generated by the data escrow agent for a certain 2859 point in time (watermark) based on the contents of the escrow 2860 deposits. The last full plus all differentials or last full plus 2861 last incremental escrow deposits MUST be used to generate
2862 element. 2864 Example object: 2866 2867 2871 2010-10-17 2872 valid 2873 2874 20101017001 2875 0 2876 2010-10-17T02:51:10.0Z 2877 2010-10-17T01:51:10.0Z 2878 FULL 2879 2010-10-16 2880 2010-10-17T00:00:00Z 2881 2882 test 2883 2 2885 1 2887 1 2889 1 2891 2892 1 2894 1 2896 1 2898 2899 2900 2901 2903 18. References 2905 18.1. Normative References 2907 [ISO-3166-1] 2908 International Organization for Standardization, "Codes for 2909 the representation of names of countries and their 2910 subdivisions -- Part 1: Country codes", ISO Standard 3166, 2911 November 2006. 2913 [ITU-E164] 2914 International Telecommunication Union, "The international 2915 public telecommunication numbering plan", ITU-T 2916 Recommendation E.164, February 2005. 2918 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2919 Requirement Levels", BCP 14, RFC 2119, March 1997. 2921 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 2922 Internet: Timestamps", RFC 3339, July 2002. 2924 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 2925 the Extensible Provisioning Protocol (EPP)", RFC 3915, 2926 September 2004. 2928 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2929 Domain Name Mapping", STD 69, RFC 5731, August 2009. 2931 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2932 Host Mapping", STD 69, RFC 5732, August 2009. 2934 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2935 Contact Mapping", STD 69, RFC 5733, August 2009. 2937 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 2938 Security Extensions Mapping for the Extensible 2939 Provisioning Protocol (EPP)", RFC 5910, May 2010. 2941 18.2. Informative References 2943 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 2944 September 1981. 2946 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2947 January 2004. 2949 [RFC3743] Konishi, K., Huang, K., Qian, H., and Y. Ko, "Joint 2950 Engineering Team (JET) Guidelines for Internationalized 2951 Domain Names (IDN) Registration and Administration for 2952 Chinese, Japanese, and Korean", RFC 3743, April 2004. 2954 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 2955 September 2004. 2957 [RFC4290] Klensin, J., "Suggested Practices for Registration of 2958 Internationalized Domain Names (IDN)", RFC 4290, 2959 December 2005. 2961 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2962 Architecture", RFC 4291, February 2006. 2964 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2965 STD 69, RFC 5730, August 2009. 2967 [variantTLDsReport] 2968 Internet Corporation for Assigned Names and Numbers 2969 (ICANN), "A Study of Issues Related to the Management of 2970 IDN Variant TLDs", February 2012, . 2974 Authors' Addresses 2976 Francisco Arias 2977 Internet Corporation for Assigned Names and Numbers 2978 12025 Waterfront Drive, Suite 300 2979 Los Angeles 90292 2980 United States of America 2982 Phone: +1.310.823.9358 2983 Email: francisco.arias@icann.org 2985 Gustavo Lozano 2986 Internet Corporation for Assigned Names and Numbers 2987 12025 Waterfront Drive, Suite 300 2988 Los Angeles 90292 2989 United States of America 2991 Phone: +1.310.823.9358 2992 Email: gustavo.lozano@icann.org 2994 Shoji Noguchi 2995 Japan Registry Services Co., Ltd. 2996 Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda 2997 Chiyoda-ku, Tokyo 101-0065 2998 Japan 3000 Phone: +81.3.5215.8451 3001 Email: noguchi@jprs.co.jp 3002 James Gould 3003 VeriSign, Inc. 3004 12061 Bluemont Way 3005 Reston 20190 3006 United States of America 3008 Email: jgould@verisign.com 3010 Chethan Thippeswamy 3011 VeriSign, Inc. 3012 12061 Bluemont Way 3013 Reston 20190 3014 United States of America 3016 Email: cthippeswamy@verisign.com