idnits 2.17.1 draft-arias-noguchi-dnrd-objects-mapping-01.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 21, 2012) is 4177 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 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: April 24, 2013 S. Noguchi 6 JPRS 7 October 21, 2012 9 Domain Name Registration Data (DNRD) Objects Mapping 10 draft-arias-noguchi-dnrd-objects-mapping-01 12 Abstract 14 This document specifies the format and contents of Domain Name 15 Registration Data (DNRD) Escrow deposits. Specified in Extensible 16 Markup Language (XML), the mapping defines Registration Data Escrow 17 (RDE) deposit syntax and semantics. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 24, 2013. 36 Copyright Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. General Conventions . . . . . . . . . . . . . . . . . . . . . 3 56 3.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 3 57 3.2. Country names . . . . . . . . . . . . . . . . . . . . . . 4 58 3.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 4 59 3.4. IP addresses . . . . . . . . . . . . . . . . . . . . . . . 4 60 4. Object Description . . . . . . . . . . . . . . . . . . . . . . 4 61 4.1. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 4 62 4.2. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 9 63 4.3. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 11 64 4.4. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 15 65 4.5. RDE IDN Table Reference . . . . . . . . . . . . . . . . . 18 66 4.6. RDE NNDN . . . . . . . . . . . . . . . . . . . . . . . . . 19 67 4.7. RDE EPP Parameters object . . . . . . . . . . . . . . . . 21 68 5. RDE IDN Variants Handling . . . . . . . . . . . . . . . . . . 23 69 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 23 70 6.1. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 23 71 6.2. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 27 72 6.3. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 29 73 6.4. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 32 74 6.5. RDE IDN Table Reference Objects . . . . . . . . . . . . . 35 75 6.6. RDE NNDN Objects . . . . . . . . . . . . . . . . . . . . . 37 76 6.7. EPP Parameters Object . . . . . . . . . . . . . . . . . . 40 77 7. Internationalization Considerations . . . . . . . . . . . . . 42 78 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42 79 9. Security Considerations . . . . . . . . . . . . . . . . . . . 45 80 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 46 81 11. Change History . . . . . . . . . . . . . . . . . . . . . . . . 46 82 11.1. Changes from 83 draft-arias-noguchi-registry-data-escrow-02 to 84 -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . . 46 85 11.2. Changes from version 00 to 01 . . . . . . . . . . . . . . 46 86 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 47 87 12.1. Normative References . . . . . . . . . . . . . . . . . . . 47 88 12.2. Informative References . . . . . . . . . . . . . . . . . . 48 89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 48 91 1. Introduction 93 This document specifies a format and contents of Domain Name 94 Registration Data Escrow deposits. 96 TBD 98 2. Terminology 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in BCP 14, [RFC2119]. 104 REGISTRY. In the context of this draft the definition will be 105 overloaded (from the definition in the base protocol) to indicate an 106 organization providing Registry Services for a REGISTRY-CLASS DOMAIN 107 NAME. 109 REGISTRY-CLASS DOMAIN NAME (RCDN): Refers to a top-level domain (TLD) 110 or any other domain name at any level in the DNS tree for which a 111 Registry (either directly or through and affiliate company) provides 112 Registry Services for other organizations or individuals. For 113 example: .COM, .ORG, .BIZ, .CO.JP, .ORG.MX. 115 REGISTRY SERVICES. Services offered by the Registry critical to the 116 following tasks: the provisioning of domain names on receipt of 117 requests and data from registrars; responding to registrar queries 118 for status information relating to the DNS servers for the RCDN; 119 dissemination of RCDN zone files; operation of the Registry DNS 120 servers; and responding to queries for contact and other information 121 concerning DNS registrations in the RCDN. Any other products or 122 services that only a Registry is capable of providing, by reason of 123 its designation as the Registry. Typical examples of Registry 124 Services are: DNS resolution for the RCDN, WHOIS and EPP. 126 3. General Conventions 128 3.1. Date and Time 130 Numerous fields indicate "dates", such as the creation and expiry 131 dates for domain names. These fields SHALL contain timestamps 132 indicating the date and time in UTC as specified in [RFC3339], with 133 no offset from the zero meridian. 135 3.2. Country names 137 Country identifiers SHALL be represented using two character 138 identifiers as specified in [ISO-3166-1]. 140 3.3. Telephone numbers 142 Telephone numbers (both voice and fax) SHALL be formatted based on 143 structures defined in [ITU-E164]. Telephone numbers described in 144 this specification are character strings that MUST begin with a plus 145 sign ("+", ASCII value 0x002B), followed by a country code defined in 146 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 147 a sequence of digits representing the telephone number. 149 3.4. IP addresses 151 IP addresses syntax MUST conform either to, Internet Protocol 152 [RFC0791], for IPv4 addresses, or IP Version 6 Addressing 153 Architecture [RFC4291], for IPv6 addresses. 155 4. Object Description 157 This section describes the base objects defined in EPP: domains, 158 hosts and contacts with the addition of registrars, IDN Table 159 References, NNDNs and EPP parameters. 161 4.1. RDE Domain Object 163 The RDE domain object is based on the EPP domain name mapping 164 specified in [RFC5731]. There are two elements used in this format 165 related to domains: the domain object per se, used inside the 166 element and the object used inside the 167 element. 169 4.1.1. object 171 The domain element is based on the EPP domain response for an 172 authorized client (see Section 3.1.2. of [RFC5731]) with some 173 additions, including the data from an EPP Query Response, 174 see Section 3.1.3. of [RFC5731], RGP status from [RFC3915], and data 175 from the EPP command, see Section 5.2.1. of 176 [RFC5910]. 178 The element contains the following child elements: 180 o A element that contains the fully qualified name of the 181 domain name object. 183 o A element that contains the repository object identifier 184 assigned to the domain name object when it was created. 186 o One or more elements that contain the current status 187 descriptors associated with the domain name. 189 o Zero or more OPTIONAL element to represent the 190 different states that a domain name can be in as a result of grace 191 period processing as specified in [RFC3915]. 193 o An OPTIONAL element that contain the identifier for 194 the human or organizational social information object associated 195 as the holder of the domain name object. 197 o Zero or more OPTIONAL elements that contain identifiers 198 for the human or organizational social information objects 199 associated with the domain name object. 201 o An OPTIONAL element that contains the fully qualified names 202 of the delegated host objects or host attributes (name servers) 203 associated with the domain name object. See Section 1.1 of 204 [RFC5731] for a description of the elements used to specify host 205 objects or host attributes. 207 o A element that contains the identifier of the sponsoring 208 registrar. 210 o A element that contains the identifier of the registrar 211 that created the domain name object. 213 o An OPTIONAL element that contains the date and time of 214 the domain name object creation. 216 o An OPTIONAL element that contains the date and time 217 identifying the end (expiration) of the domain name object's 218 registration period. 220 o An element that contains the identifier of the registrar 221 that last updated the domain name object. This element MUST NOT 222 be present if the domain has never been modified. 224 o An element that contains the date and time of the most 225 recent domain-name-object modification. This element MUST NOT be 226 present if the domain name object has never been modified. 228 o An element that contains the date and time of the most 229 recent domain object successful transfer. This element MUST NOT 230 be present if the domain name object has never been transfered. 232 o A element that contains the deletion date for the domain. 233 This element is used by registries that support the Domain 234 Registry Grace Period as specified in [RFC3915]. This element 235 MUST be present if the domain name has been deleted, but not yet 236 purged from the registry repository. 238 o An element that contains authorization information 239 associated with the domain name object. 241 o An OPTIONAL element that contains the public key 242 information associated with Domain Name System security (DNSSEC) 243 extensions for the domain name as specified in [RFC5910]. 245 o An OPTIONAL element that references the IDN Table 246 used for the IDN. This corresponds to the "id" attribute of the 247 element. This element MUST be present if the domain 248 name object is an IDN or variantGenerator is present. 250 o An OPTIONAL element that can be used to specify 251 algorithmically generated variants, e.g., when the number of 252 variants is so big that is unpractical to list them explicitly. A 253 defaultState attribute can be used to specify the default state 254 for the generated variants: blocked, withheld or allocated. If 255 the LGR does not specify the state of the generated variants then 256 the default_state attribute is used. The LGR defined IDN variant 257 state takes precedence over the default_state attribute. 259 o An OPTIONAL element that contains the following child 260 elements related to the last transfer request of the domain name 261 object. This element MUST NOT be present if a transfer request 262 for the domain name has never been created. 264 * A element that contains the state of the most recent 265 transfer request. 267 * A element that contains the identifier of the registrar 268 that requested the domain name object transfer. 270 * A element that contains the date and time that the 271 transfer was requested. 273 * An element that contains the identifier of the registrar 274 that SHOULD act upon a PENDING transfer request. For all other 275 status types, the value identifies the registrar that took the 276 indicated action. 278 * An element that contains the date and time of a 279 required or completed response. For a PENDING request, the 280 value identifies the date and time by which a response is 281 required before an automated response action will be taken by 282 the registry. For all other status types, the value identifies 283 the date and time when the request was completed. 285 * An element that contains the end of the domain name 286 object's validity period (expiry date) if the transfer caused 287 or causes a change in the validity period. 289 Example of a domain object: 291 ... 292 293 pinguino.test 294 Dpinguino-TEST 295 296 297 jd1234 298 sh8013 299 sh8013 300 301 ns1.example.com 302 ns1.example.net 303 304 clientX 305 clientY 306 1999-04-03T22:00:00.0Z 307 2015-04-03T22:00:00.0Z 308 2015-04-01T22:00:00.0Z 309 clientX 310 2009-12-03T09:05:00.0Z 311 312 2fooBAR 313 314 315 604800 316 317 12345 318 7 319 1 320 321 93358db22e956a451eb5ae8d2ec39526ca6a87b9 322 323 324 325 326 pending 327 clientW 328 2011-03-08T19:38:00.0Z 329 clientX 330 2011-03-13T23:59:59.0Z 331 2016-04-03T22:00:00.0Z 332 333 334 ... 336 4.1.2. object 338 The element contains the fully qualified domain 339 name that was deleted and purged. 341 Example of object: 343 ... 344 345 ... 346 347 foo.test 348 bar.test 349 350 ... 351 352 ... 354 4.2. RDE Host Object 356 The RDE host object is based on the EPP host name mapping in 357 [RFC5732]. There are two elements used in this format related to 358 hosts: the host object per se, used inside the element and 359 the object used inside the element. 361 4.2.1. object 363 The RDE host object is based on the EPP host response for an 364 authorized client (see Section 3.1.2. of [RFC5732]). 366 The OPTIONAL element contains the following child elements: 368 o A element that contains the fully qualified name of the 369 host object. 371 o A element that contains the repository object identifier 372 assigned to the host object when the object was created. 374 o One or more elements that describe the status of the host 375 object. 377 o Zero or more elements that contain the IP addresses 378 associated with the host object. 380 o A element that contains the identifier of the sponsoring 381 registrar. 383 o A element that contains the identifier of the registrar 384 that created the host object. 386 o A element that contains the date and time of host-object 387 creation. 389 o An element that contains the identifier of the registrar 390 that last updated the host object. This element MUST NOT be 391 present if the host object has never been modified. 393 o An element that contains the date and time of the most 394 recent host-object modification. This element MUST NOT be present 395 if the host object has never been modified. 397 Example of object: 399 ... 400 401 ns1.example.test 402 Hns1_example_test-TEST 403 404 405 192.0.2.2 406 192.0.2.29 407 1080:0:0:0:8:800:200C:417A 408 clientY 409 clientX 410 1999-05-08T12:10:00.0Z 411 clientX 412 2009-10-03T09:34:00.0Z 413 414 ... 416 4.2.2. object 418 The element contains the fully qualified domain name 419 of a host that was deleted. 421 Example of object: 423 ... 424 425 ... 426 427 ns1.example.test 428 429 ... 430 431 ... 433 4.3. RDE Contact Object 435 The RDE contact object is based on the EPP contact name mapping in 436 [RFC5733]. There are two elements used in this format related to 437 contacts: the contact object per se, used inside the 438 element and the object used inside the 439 element. 441 4.3.1. object 443 The contact object is based on the EPP contact response for an 444 authorized client (see Section 3.1.2. of [RFC5733]) with some 445 additions including the data from an EPP Query Response, 446 see Section 3.1.3. of [RFC5733]. 448 The OPTIONAL element contains the following child elements: 450 o An element that contains the repository object identifier 451 assigned to the contact object when the object was created. 453 o One or more elements that describe the status of the 454 contact object. 456 o One or two elements that contain postal-address 457 information. Two elements are provided so that address 458 information can be provided in both internationalized and 459 localized forms; a "type" attribute is used to identify the two 460 forms. If an internationalized form (type="int") is provided, 461 element content MUST be represented in a subset of UTF-8 that can 462 be represented in the 7-bit US-ASCII character set. If a 463 localized form (type="loc") is provided, element content MAY be 464 represented in unrestricted UTF-8. The element 465 contains the following child elements: 467 * A element that contains the name of the individual or 468 role represented by the contact. 470 * An OPTIONAL element that contains the name of the 471 organization with which the contact is affiliated. 473 * An element that contains address information associated 474 with the contact. An element contains the following 475 child elements: 477 + One, two, or three OPTIONAL elements that contain 478 the contact's street address. 480 + A element that contains the contact's city. 482 + An OPTIONAL element that contains the contact's state 483 or province. 485 + An OPTIONAL element that contains the contact's postal 486 code. 488 + A element that contains the contact's two-letter 489 country code. 491 o An OPTIONAL element that contains the contact's voice 492 telephone number. 494 o An OPTIONAL element that contains the contact's facsimile 495 telephone number. 497 o An element that contains the contact's email address. 499 o A element that contains the identifier of the sponsoring 500 registrar. 502 o A element that contains the identifier of the registrar 503 that created the contact object. 505 o A element that contains the date and time of contact- 506 object creation. 508 o An element that contains the identifier of the registrar 509 that last updated the contact object. This element MUST NOT be 510 present if the contact has never been modified. 512 o An element that contains the date and time of the most 513 recent contact-object modification. This element MUST NOT be 514 present if the contact object has never been modified. 516 o An element that contains the date and time of the most 517 recent contact object sucessful transfer. This element MUST NOT 518 be present if the contact object has never been transfered. 520 o An element that contains authorization information 521 associated with the contact object. 523 o An OPTIONAL element that identifies elements that 524 require exceptional server-operator handling to allow or restrict 525 disclosure to third parties. See Section 2.9 of [RFC5733] for a 526 description of the child elements contained within the 527 element. 529 o A element that contains the following child elements 530 related to the last transfer request of the contact object: 532 * A element that contains the state of the most recent 533 transfer request. 535 * A element that contains the identifier of the registrar 536 that requested the domain name object transfer. 538 * A element that contains the date and time that the 539 transfer was requested. 541 * An element that contains the identifier of the registrar 542 that SHOULD act upon a PENDING transfer request. For all other 543 status types, the value identifies the registrar that took the 544 indicated action. 546 * An element that contains the date and time of a 547 required or completed response. For a PENDING request, the 548 value identifies the date and time by which a response is 549 required before an automated response action will be taken by 550 the registry. For all other status types, the value identifies 551 the date and time when the request was completed. 553 Example object: 555 ... 556 557 sh8013 558 Csh8013-TEST 559 560 561 562 John Doe 563 Example Inc. 564 565 123 Example Dr. 566 Suite 100 567 Dulles 568 VA 569 20166-6503 570 US 571 572 573 +1.7035555555 574 +1.7035555556 575 jdoe@example.test 576 clientY 577 clientX 578 2009-09-13T08:01:00.0Z 579 clientX 580 2009-11-26T09:10:00.0Z 581 582 2fooBAR 583 584 585 586 587 588 2009-12-03T09:05:00.0Z 589 590 pending 591 clientW 592 2011-03-08T19:38:00.0Z 593 clientX 594 2011-03-13T23:59:59.0Z 595 596 597 ... 599 4.3.2. object 601 The element contains the id of a contact that was 602 deleted. 604 Example of object: 606 ... 607 608 ... 609 610 sh8013-TEST 611 co8013-TEST 612 613 ... 614 615 ... 617 4.4. RDE Registrar Object 619 The RDE registrar object is based on the EPP contact name mapping 620 previously described. There are two elements used in this format 621 related to registrars: the registrar object per se, used inside the 622 element and the object used inside 623 the element. 625 4.4.1. object 627 The element contains the following child elements: 629 o An element that contains the Registry-unique identifier of 630 the registrar object. This has a superordinate relationship 631 to a subordinate , or of domain, contact and 632 host objects. 634 o An OPTIONAL element that contains the ID assigned by 635 ICANN. 637 o One or two elements that contain postal- address 638 information. Two elements are provided so that address 639 information can be provided in both internationalized and 640 localized forms; a "type" attribute is used to identify the two 641 forms. If an internationalized form (type="int") is provided, 642 element content MUST be represented in a subset of UTF-8 that can 643 be represented in the 7-bit US-ASCII character set. If a 644 localized form (type="loc") is provided, element content MAY be 645 represented in unrestricted UTF-8. The element 646 contains the following child elements: 648 * An OPTIONAL element that contains the name of the 649 organization with which the registrar is affiliated. 651 * A element that contains address information associated 652 with the registrar. The element contains the following 653 child elements: 655 + One, two, or three OPTIONAL elements that contain 656 the registrar's street address. 658 + A element that contains the registrar's city. 660 + An OPTIONAL element that contains the registrar's state 661 or province. 663 + An OPTIONAL element that contains the registrar's 664 postal code. 666 + A element that contains the registrar's country code. 668 o An OPTIONAL element that contains the registrar's voice 669 telephone number. 671 o An OPTIONAL element that contains the registrar's facsimile 672 telephone number. 674 o An element that contains the registrar's email address. 676 o An OPTIONAL element that contains the registrar's URL. 678 o An OPTIONAL elements that contains whois information. 679 The element contains the following child elements: 681 * An OPTIONAL element that contains the name of the 682 registrar WHOIS server listenin on TCP port 43 as specified in 683 [RFC3912]. 685 * An OPTIONAL element that contains the name of the 686 registrar WHOIS server listenin on TCP port 80/443. 688 o Zero or more OPTIONAL elements that contain identifiers 689 for the human or organizational social information objects 690 associated with the registrar object. 692 o A element that contains the date and time of registrar- 693 object creation. 695 o An OPTIONAL element that contains the date and time of 696 the most recent RDE registrar-object modification. This element 697 MUST NOT be present if the rdeRegistrar object has never been 698 modified. 700 o An OPTIONAL element that contains authorization 701 information associated with the registar object to allow access to 702 registry systems. This specification describes password-based 703 authorization information, though other mechanisms are possible. 705 Example of object: 707 ... 708 709 clientX 710 RclientX-TEST 711 123 712 713 John Doe 714 Example Inc. 715 716 123 Example Dr. 717 Suite 100 718 Dulles 719 VA 720 20166-6503 721 US 722 723 724 +1.7035555555 725 +1.7035555556 726 jdoe@example.test 727 http://www.example.test 728 729 whois.example.test 730 http://whois.example.test 731 https://whois.example.test 732 733 rr0013 734 rr0012 735 2005-04-23T11:49:00.0Z 736 2009-02-17T17:51:00.0Z 737 738 tHisaPaSSw 739 740 741 ... 743 4.4.2. object 745 The element contains the id of a registrar that 746 was deleted. 748 Example of object: 750 ... 751 752 ... 753 754 agnt0001-TEST 755 756 ... 757 758 ... 760 4.5. RDE IDN Table Reference 762 The RDE Internationalized Domain Names (IDN) Table reference is a 763 pseudobject that is used to provide a short reference to the IDN 764 Table used in IDN registrations. The element has an 765 "id" attribute that is used to uniquely identify an IDN Table stored 766 externally. 768 4.5.1. object 770 The OPTIONAL contains the following elements: 772 o An element that contains the URL of the IDN table that is 773 being referenced. 775 o An element that contains the type of representation of the 776 Label Generation Ruleset (LGR). Allowed values are: [RFC3743], 777 [RFC4290] and draft-davies-idntables. 779 Example of object: 781 ... 782 783 784 http://www.iana.org/domains/idn-tables/tables/cn_zh-cn_4.0.html 785 786 RFC3743 787 788 ... 790 4.6. RDE NNDN 792 4.6.1. NNDN's not domain name 794 A NNDN (NNDN's not domain name) does not exist as a domain object; it 795 is stored in the SRS database and precludes the coexistence of an 796 homonimous domain object. NNDNs can be used to store registry 797 reserved names or IDN variant handling. A NNDN of state withheld and 798 blocked can be created because of IDN variant handling or for other 799 purposes like a list of reserved names. An allocated NNDN can only 800 be created if it is an IDN variant. 802 4.6.2. object 804 The OPTIONAL element contains the following child elements: 806 o An element that contains the ASCII Compatible Encoding 807 (ACE) of the NNDN. 809 o An OPTIONAL element that contains the name of the NNDN in 810 Unicode character set. It MUST be provided if available. 812 o A element that indicates the state of the NNDN: 813 blocked, withheld and allocated. 815 * If a NNDN is considered undesirable for registration (i.e., 816 unavailable for allocation to anyone), then the NNDN will be 817 tagged as "blocked". 819 * If a NNDN is created to allow the registration of a domain 820 object to a particular registrant then the NNDN will be tagged 821 as "withheld". 823 * If a NNDN is created to replicate the exact information from 824 the canonical name, then the NNDN will be tagged "allocated". 825 A NNDN of state "allocated" reflect the same information from 826 the canonical domain. E.g. If the canonical domain is present 827 in the DNS zone, then the NNDN is going to be present in the 828 DNS zone. 830 o An OPTIONAL element that references the IDN Table in 831 case the NNDN is an IDN variant. This corresponds to the "id" 832 attribute of the element. 834 o A element that contains the date and time of the NNDN 835 object creation. 837 o An OPTIONAL element that MUST be present when 838 state is withheld or allocated. One of the following elements 839 MUST be present. 841 * An OPTIONAL element that contains the 842 repository object identifier of the canonical domain name. An 843 IDN variant generated NNDN MUST be associated to a canonical 844 domain name. 846 * An OPTIONAL element that contain the identifier 847 for the human or organizational social information object 848 allowed to register the domain name. The element 849 takes precedence over the registrant of the 850 domain name in case and are 851 present. 853 Example of object: 855 ... 856 857 xn--pingino-q2a.test 858 pingueino.test 859 allocated 860 cl-es 861 2005-04-23T11:49:00.0Z 862 Dpinguino-TEST 863 864 ... 866 4.6.3. object 868 The element contains the ACE of a NNDN that was 869 deleted, i.e., the . 871 Example of object: 873 ... 874 875 ... 876 877 xn--pingino-q2a.test 878 879 ... 880 881 ... 883 4.7. RDE EPP Parameters object 885 An OPTIONAL element contains some EPP parameters that may 886 be helpful when rebuilding a registry from the escrow deposits. The 887 element SHOULD be included in Deposits if the registry uses EPP. 889 The syntax and content of the children elements is as 890 explained in section 2.4 of [RFC5730]. The children of the 891 are as follows: 893 o One or more elements that indicate the EPP versions 894 supported by the registry. 896 o One or more elements that indicate the identifiers of the 897 text response languages supported by the registry's EPP server. 899 o One or more elements that contain namespace URIs 900 representing the objects that the registry's EPP server is capable 901 of managing. 903 o An OPTIONAL element that contains one or more 904 elements that contain namespace URIs representing object 905 extensions supported by the registry's EPP server. 907 o A element that contains child elements used to describe the 908 server's privacy policy for data collection and management. See 909 section 2.4 of [RFC5730] for more details. 911 Example of element object: 913 914 918 ... 919 920 921 1.0 922 en 923 924 urn:ietf:params:xml:ns:domain-1.0 925 926 927 urn:ietf:params:xml:ns:contact-1.0 928 929 930 urn:ietf:params:xml:ns:host-1.0 931 932 933 934 urn:ietf:params:xml:ns:rgp-1.0 935 936 937 urn:ietf:params:xml:ns:secDNS-1.1 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 ... 958 959 ... 960 962 5. RDE IDN Variants Handling 964 Depending on the Registration Policy of the Registry; for a 965 particular domain name there may be multiple variant names. See 966 [variantTLDsReport] for further detail on IDN variants. 968 A registry could choose to create IDN variants as domain or NNDN 969 objects. 971 A LGR could be used to compute IDN variants in real-time by the 972 registry instead of creating domain or NNDN objects. 974 A NNDN or a domain name are explicit representations of an IDN 975 variant while an IDN variant computed based on a LGR is an implicit 976 representation. Explicit representation of an IDN variant takes 977 precedence over an implicit representation. 979 6. Formal Syntax 981 Seven schemas are presented here. The first schema is the base RDE 982 schema. The second schema defines domain object for RDE. The third 983 schema defines host object for RDE. The fourth schema defines 984 contact object for RDE. The fifth schema defines registrar object 985 for RDE. The sixth schema defines the idnTableRef and IDN objects. 986 The last schema defines the eppParams objects. 988 6.1. RDE Domain Object 990 Copyright (c) 2011 IETF Trust and the persons identified as authors 991 of the code. All rights reserved. 993 Redistribution and use in source and binary forms, with or without 994 modification, are permitted provided that the following conditions 995 are met: 997 o Redistributions of source code must retain the above copyright 998 notice, this list of conditions and the following disclaimer. 1000 o Redistributions in binary form must reproduce the above copyright 1001 notice, this list of conditions and the following disclaimer in 1002 the documentation and/or other materials provided with the 1003 distribution. 1005 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1006 names of specific contributors, may be used to endorse or promote 1007 products derived from this software without specific prior written 1008 permission. 1010 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1011 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1012 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1013 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1014 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1015 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1016 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1017 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1018 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1019 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1020 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1022 BEGIN 1023 1025 1035 1038 1040 1042 1044 1046 1049 1050 1051 Registry Data Escrow Domain provisioning schema 1052 1053 1055 1058 1061 1062 1063 1064 1065 1067 1070 1073 1074 1075 1076 1077 1078 1079 1081 1083 1085 1087 1089 1090 1092 1094 1096 1098 1100 1102 1104 1107 1109 1111 1113 1114 1115 1116 1118 1119 1120 1121 1122 1123 1124 1125 1127 1128 1130 1133 1136 1137 1138 1139 1140 1142 1143 1144 1145 1147 1150 1151 END 1153 6.2. RDE Host Object 1155 Copyright (c) 2011 IETF Trust and the persons identified as authors 1156 of the code. All rights reserved. 1158 Redistribution and use in source and binary forms, with or without 1159 modification, are permitted provided that the following conditions 1160 are met: 1162 o Redistributions of source code must retain the above copyright 1163 notice, this list of conditions and the following disclaimer. 1165 o Redistributions in binary form must reproduce the above copyright 1166 notice, this list of conditions and the following disclaimer in 1167 the documentation and/or other materials provided with the 1168 distribution. 1170 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1171 names of specific contributors, may be used to endorse or promote 1172 products derived from this software without specific prior written 1173 permission. 1175 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1176 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1177 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1178 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1179 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1180 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1181 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1182 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1183 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1184 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1185 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1187 BEGIN 1188 1190 1198 1201 1203 1205 1208 1209 1210 Registry Data Escrow host provisioning schema 1211 1212 1214 1217 1220 1221 1222 1223 1224 1226 1229 1232 1233 1234 1235 1236 1237 1238 1240 1242 1243 1244 1245 1247 1250 1251 1252 1253 1255 1258 1261 1262 1263 1264 1265 1267 1268 1269 1270 1272 1275 1276 END 1278 6.3. RDE Contact Object 1280 Copyright (c) 2011 IETF Trust and the persons identified as authors 1281 of the code. All rights reserved. 1283 Redistribution and use in source and binary forms, with or without 1284 modification, are permitted provided that the following conditions 1285 are met: 1287 o Redistributions of source code must retain the above copyright 1288 notice, this list of conditions and the following disclaimer. 1290 o Redistributions in binary form must reproduce the above copyright 1291 notice, this list of conditions and the following disclaimer in 1292 the documentation and/or other materials provided with the 1293 distribution. 1295 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1296 names of specific contributors, may be used to endorse or promote 1297 products derived from this software without specific prior written 1298 permission. 1300 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1301 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1302 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1303 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1304 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1305 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1306 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1307 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1308 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1309 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1310 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1312 BEGIN 1313 1315 1323 1326 1328 1330 1333 1334 1335 Registry Data Escrow contact provisioning schema 1336 1337 1339 1342 1345 1346 1347 1348 1349 1351 1354 1357 1358 1359 1360 1361 1362 1363 1365 1367 1369 1371 1372 1373 1374 1375 1377 1379 1381 1383 1385 1387 1388 1389 1390 1392 1393 1394 1395 1396 1397 1398 1399 1400 1402 1405 1408 1409 1410 1411 1412 1414 1415 1416 1417 1419 1422 1423 END 1425 6.4. RDE Registrar Object 1427 Copyright (c) 2011 IETF Trust and the persons identified as authors 1428 of the code. All rights reserved. 1430 Redistribution and use in source and binary forms, with or without 1431 modification, are permitted provided that the following conditions 1432 are met: 1434 o Redistributions of source code must retain the above copyright 1435 notice, this list of conditions and the following disclaimer. 1437 o Redistributions in binary form must reproduce the above copyright 1438 notice, this list of conditions and the following disclaimer in 1439 the documentation and/or other materials provided with the 1440 distribution. 1442 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1443 names of specific contributors, may be used to endorse or promote 1444 products derived from this software without specific prior written 1445 permission. 1447 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1448 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1449 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1450 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1451 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1452 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1453 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1454 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1455 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1456 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1457 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1459 BEGIN 1460 1462 1471 1474 1476 1478 1480 1483 1484 1485 Registry Data Escrow registrar provisioning schema 1486 1487 1489 1492 1495 1496 1497 1498 1499 1501 1504 1507 1508 1509 1510 1511 1512 1513 1515 1517 1519 1521 1523 1525 1527 1529 1530 1532 1534 1535 1536 1537 1538 1539 1540 1542 1544 1545 1547 1550 1553 1554 1555 1556 1557 1559 1560 1561 1562 1564 1567 1568 END 1570 6.5. RDE IDN Table Reference Objects 1572 Copyright (c) 2011 IETF Trust and the persons identified as authors 1573 of the code. All rights reserved. 1575 Redistribution and use in source and binary forms, with or without 1576 modification, are permitted provided that the following conditions 1577 are met: 1579 o Redistributions of source code must retain the above copyright 1580 notice, this list of conditions and the following disclaimer. 1582 o Redistributions in binary form must reproduce the above copyright 1583 notice, this list of conditions and the following disclaimer in 1584 the documentation and/or other materials provided with the 1585 distribution. 1587 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1588 names of specific contributors, may be used to endorse or promote 1589 products derived from this software without specific prior written 1590 permission. 1592 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1593 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1594 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1595 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1596 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1597 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1598 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1599 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1600 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1601 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1602 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1604 BEGIN 1605 1607 1614 1617 1619 1622 1623 1624 Registry Data Escrow IDN provisioning schema 1625 1626 1628 1631 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1645 1646 1647 1648 1649 1650 1651 1653 1656 1657 END 1659 6.6. RDE NNDN Objects 1661 Copyright (c) 2011 IETF Trust and the persons identified as authors 1662 of the code. All rights reserved. 1664 Redistribution and use in source and binary forms, with or without 1665 modification, are permitted provided that the following conditions 1666 are met: 1668 o Redistributions of source code must retain the above copyright 1669 notice, this list of conditions and the following disclaimer. 1671 o Redistributions in binary form must reproduce the above copyright 1672 notice, this list of conditions and the following disclaimer in 1673 the documentation and/or other materials provided with the 1674 distribution. 1676 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1677 names of specific contributors, may be used to endorse or promote 1678 products derived from this software without specific prior written 1679 permission. 1681 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1682 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1683 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1684 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1685 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1686 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1687 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1688 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1689 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1690 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1691 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1693 BEGIN 1694 1696 1703 1706 1708 1711 1712 1713 Registry Data Escrow NNDN provisioning schema 1714 1715 1717 1720 1723 1724 1725 1726 1727 1729 1732 1735 1736 1737 1738 1739 1740 1742 1743 1744 1746 1747 1749 1750 1751 1752 1754 1755 1756 1757 1758 1759 1760 1762 1763 1764 1766 1768 1769 1771 1774 1777 1778 1779 1780 1781 1783 1784 1785 1786 1788 1791 1792 END 1794 6.7. EPP Parameters Object 1796 Copyright (c) 2011 IETF Trust and the persons identified as authors 1797 of the code. All rights reserved. 1799 Redistribution and use in source and binary forms, with or without 1800 modification, are permitted provided that the following conditions 1801 are met: 1803 o Redistributions of source code must retain the above copyright 1804 notice, this list of conditions and the following disclaimer. 1806 o Redistributions in binary form must reproduce the above copyright 1807 notice, this list of conditions and the following disclaimer in 1808 the documentation and/or other materials provided with the 1809 distribution. 1811 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1812 names of specific contributors, may be used to endorse or promote 1813 products derived from this software without specific prior written 1814 permission. 1816 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1817 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1818 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1819 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1820 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1821 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1822 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1823 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1824 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1825 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1826 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1828 BEGIN 1829 1831 1839 1842 1844 1846 1849 1850 1851 Registry Data Escrow EPP Parameters schema 1852 1853 1855 1858 1861 1862 1863 1864 1865 1867 1870 1873 1874 1875 1876 1877 1879 1881 1883 1885 1886 1887 1888 1889 1891 1894 1895 END 1897 7. Internationalization Considerations 1899 Data Escrow deposits are represented in XML, which provides native 1900 support for encoding information using the Unicode character set and 1901 its more compact representations including UTF-8. Conformant XML 1902 processors recognize both UTF-8 and UTF-16. Though XML includes 1903 provisions to identify and use other character encodings through use 1904 of an "encoding" attribute in an declaration, use of UTF-8 is 1905 RECOMMENDED. 1907 8. IANA Considerations 1909 This document uses URNs to describe XML namespaces and XML schemas 1910 conforming to a registry mechanism described in [RFC3688]. Fourteen 1911 URI assignments have been registered by the IANA. 1913 Registration request for the RDE namespace: 1915 URI: urn:ietf:params:xml:ns:rde-1.0 1917 Registrant Contact: See the "Author's Address" section of this 1918 document. 1920 XML: None. Namespace URIs do not represent an XML specification. 1922 Registration request for the RDE XML schema: 1924 URI: urn:ietf:params:xml:schema:rde-1.0 1926 Registrant Contact: See the "Author's Address" section of this 1927 document. 1929 See the "Formal Syntax" section of this document. 1931 Registration request for the RDE domain namespace: 1933 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 1935 Registrant Contact: See the "Author's Address" section of this 1936 document. 1938 XML: None. Namespace URIs do not represent an XML specification. 1940 Registration request for the RDE domain XML schema: 1942 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 1944 Registrant Contact: See the "Author's Address" section of this 1945 document. 1947 See the "Formal Syntax" section of this document. 1949 Registration request for the RDE host namespace: 1951 URI: urn:ietf:params:xml:ns:rdeHost-1.0 1953 Registrant Contact: See the "Author's Address" section of this 1954 document. 1956 XML: None. Namespace URIs do not represent an XML specification. 1958 Registration request for the RDE host XML schema: 1960 URI: urn:ietf:params:xml:schema:rdeHost-1.0 1962 Registrant Contact: See the "Author's Address" section of this 1963 document. 1965 See the "Formal Syntax" section of this document. 1967 Registration request for the RDE contact namespace: 1969 URI: urn:ietf:params:xml:ns:rdeContact-1.0 1971 Registrant Contact: See the "Author's Address" section of this 1972 document. 1974 XML: None. Namespace URIs do not represent an XML specification. 1976 Registration request for the RDE contact XML schema: 1978 URI: urn:ietf:params:xml:schema:rdeContact-1.0 1980 Registrant Contact: See the "Author's Address" section of this 1981 document. 1983 See the "Formal Syntax" section of this document. 1985 Registration request for the RDE registrar namespace: 1987 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 1989 Registrant Contact: See the "Author's Address" section of this 1990 document. 1992 XML: None. Namespace URIs do not represent an XML specification. 1994 Registration request for the RDE registrar XML schema: 1996 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 1998 Registrant Contact: See the "Author's Address" section of this 1999 document. 2001 See the "Formal Syntax" section of this document. 2003 Registration request for the RDE IDN namespace: 2005 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 2007 Registrant Contact: See the "Author's Address" section of this 2008 document. 2010 XML: None. Namespace URIs do not represent an XML specification. 2012 Registration request for the RDE IDN XML schema: 2014 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 2015 Registrant Contact: See the "Author's Address" section of this 2016 document. 2018 See the "Formal Syntax" section of this document. 2020 Registration request for the RDE EPP parameters namespace: 2022 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 2024 Registrant Contact: See the "Author's Address" section of this 2025 document. 2027 XML: None. Namespace URIs do not represent an XML specification. 2029 Registration request for the RDE EPP parameters XML schema: 2031 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 2033 Registrant Contact: See the "Author's Address" section of this 2034 document. 2036 See the "Formal Syntax" section of this document. 2038 9. Security Considerations 2040 This specification does not define the security mechanisms to be used 2041 in the transmission of the data escrow deposits, since it only 2042 specifies the minimum necessary to enable the rebuilding of a 2043 Registry from deposits without intervention from the original 2044 Registry. 2046 Depending on local policies, some elements or most likely, the whole 2047 deposit will be considered confidential. As such the Registry 2048 transmitting the data to the Escrow Agent SHOULD take all the 2049 necessary precautions like encrypting the data itself and/or the 2050 transport channel to avoid inadvertent disclosure of private data. 2052 It is also of the utmost importance the authentication of the parties 2053 passing data escrow deposit files. The Escrow Agent SHOULD properly 2054 authenticate the identity of the Registry before accepting data 2055 escrow deposits. In a similar manner, the Registry SHOULD 2056 authenticate the identity of the Escrow Agent before submitting any 2057 data. 2059 Additionally, the Registry and the Escrow Agent SHOULD use integrity 2060 checking mechanisms to ensure the data transmitted is what the source 2061 intended. Validation of the contents by the Escrow Agent is 2062 RECOMMENDED to ensure not only the file was transmitted correctly 2063 from the Registry, but also the contents are also "meaningful". 2065 10. Acknowledgments 2067 Parts of this document are based on EPP [RFC5730] and related RFCs by 2068 Scott Hollenbeck. 2070 TBD 2072 11. Change History 2074 [[RFC Editor: Please remove this section.]] 2076 11.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to 2077 -dnrd-objects-mapping-00 2079 1. Added definition for child elements under the element. 2081 2. Added definition for child elements under the element. 2083 3. Added definition for child elements under the element. 2085 4. Rewrote the IDN Variants Handling section to use the variant 2086 states as described in ICANN's Study of Issues Related to the 2087 Management of IDN Variant TLDs. 2089 5. Renamed to in the . 2091 6. Renamed to in the element. 2093 7. Renamed to in the element. 2095 8. Added element under element. 2097 9. Fixed some typographical errors and omissions. 2099 11.2. Changes from version 00 to 01 2101 1. Specify OPTIONAL elements in the draft. 2103 2. Added NNDN object to support list of reserved names and different 2104 IDN variants models. 2106 3. Removed subordinated host element from the domain object. 2108 4. Added eppParams object. 2110 5. Added variantGenerator element to the domain object. 2112 6. Added lgr to the IDN table object. 2114 12. References 2116 12.1. Normative References 2118 [ISO-3166-1] 2119 International Organization for Standardization, "Codes for 2120 the representation of names of countries and their 2121 subdivisions -- Part 1: Country codes", ISO Standard 3166, 2122 November 2006. 2124 [ITU-E164] 2125 International Telecommunication Union, "The international 2126 public telecommunication numbering plan", ITU-T 2127 Recommendation E.164, February 2005. 2129 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2130 Requirement Levels", BCP 14, RFC 2119, March 1997. 2132 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 2133 Internet: Timestamps", RFC 3339, July 2002. 2135 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 2136 the Extensible Provisioning Protocol (EPP)", RFC 3915, 2137 September 2004. 2139 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2140 Domain Name Mapping", STD 69, RFC 5731, August 2009. 2142 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2143 Host Mapping", STD 69, RFC 5732, August 2009. 2145 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2146 Contact Mapping", STD 69, RFC 5733, August 2009. 2148 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 2149 Security Extensions Mapping for the Extensible 2150 Provisioning Protocol (EPP)", RFC 5910, May 2010. 2152 12.2. Informative References 2154 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 2155 September 1981. 2157 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2158 January 2004. 2160 [RFC3743] Konishi, K., Huang, K., Qian, H., and Y. Ko, "Joint 2161 Engineering Team (JET) Guidelines for Internationalized 2162 Domain Names (IDN) Registration and Administration for 2163 Chinese, Japanese, and Korean", RFC 3743, April 2004. 2165 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 2166 September 2004. 2168 [RFC4290] Klensin, J., "Suggested Practices for Registration of 2169 Internationalized Domain Names (IDN)", RFC 4290, 2170 December 2005. 2172 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2173 Architecture", RFC 4291, February 2006. 2175 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2176 STD 69, RFC 5730, August 2009. 2178 [variantTLDsReport] 2179 Internet Corporation for Assigned Names and Numbers 2180 (ICANN), "A Study of Issues Related to the Management of 2181 IDN Variant TLDs", February 2012, . 2185 Authors' Addresses 2187 Francisco Arias 2188 Internet Corporation for Assigned Names and Numbers 2189 12025 Waterfront Drive, Suite 300 2190 Los Angeles 90292 2191 United States of America 2193 Phone: +1.310.823.9358 2194 Email: francisco.arias@icann.org 2195 Gustavo Lozano 2196 Internet Corporation for Assigned Names and Numbers 2197 12025 Waterfront Drive, Suite 300 2198 Los Angeles 90292 2199 United States of America 2201 Phone: +1.310.823.9358 2202 Email: gustavo.lozano@icann.org 2204 Shoji Noguchi 2205 Japan Registry Services Co., Ltd. 2206 Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda 2207 Chiyoda-ku, Tokyo 101-0065 2208 Japan 2210 Phone: +81.3.5215.8451 2211 Email: noguchi@jprs.co.jp