idnits 2.17.1 draft-arias-noguchi-dnrd-objects-mapping-00.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 (March 6, 2012) is 4433 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: 'I-D.arias-noguchi-registry-data-escrow' is defined on line 1967, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-arias-noguchi-registry-data-escrow-02 -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group F. Arias 3 Internet-Draft ICANN 4 Intended status: Standards Track S. Noguchi 5 Expires: September 7, 2012 JPRS 6 March 6, 2012 8 Domain Name Registration Data (DNRD) Objects Mapping 9 draft-arias-noguchi-dnrd-objects-mapping-00 11 Abstract 13 This document specifies the format and contents of Domain Name 14 Registration Data (DNRD) Escrow deposits. Specified in Extensible 15 Markup Language (XML), the mapping defines Registration Data Escrow 16 (RDE) deposit syntax and semantics. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on September 7, 2012. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. General Conventions . . . . . . . . . . . . . . . . . . . . . 3 55 3.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 3 56 3.2. Country names . . . . . . . . . . . . . . . . . . . . . . 3 57 3.3. Telephone numbers . . . . . . . . . . . . . . . . . . . . 3 58 3.4. IP addresses . . . . . . . . . . . . . . . . . . . . . . . 3 59 4. Object Description . . . . . . . . . . . . . . . . . . . . . . 4 60 4.1. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 4 61 4.2. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 8 62 4.3. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 10 63 4.4. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 14 64 4.5. RDE IDN Table Reference . . . . . . . . . . . . . . . . . 17 65 4.6. RDE IDN object . . . . . . . . . . . . . . . . . . . . . . 17 66 4.7. RDE EPP Parameters object . . . . . . . . . . . . . . . . 19 67 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 22 68 5.1. RDE Domain Object . . . . . . . . . . . . . . . . . . . . 22 69 5.2. RDE Host Object . . . . . . . . . . . . . . . . . . . . . 25 70 5.3. RDE Contact Object . . . . . . . . . . . . . . . . . . . . 28 71 5.4. RDE Registrar Object . . . . . . . . . . . . . . . . . . . 31 72 5.5. RDE IDN and IDN Table Reference Objects . . . . . . . . . 34 73 5.6. EPP Parameters Object . . . . . . . . . . . . . . . . . . 37 74 6. Extension Guidelines . . . . . . . . . . . . . . . . . . . . . 39 75 7. Internationalization Considerations . . . . . . . . . . . . . 39 76 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39 77 9. Security Considerations . . . . . . . . . . . . . . . . . . . 42 78 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 43 79 11. Change History . . . . . . . . . . . . . . . . . . . . . . . . 43 80 11.1. Changes from 81 draft-arias-noguchi-registry-data-escrow-02 to 82 -dnrd-objects-mapping-00 . . . . . . . . . . . . . . . . . 43 83 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43 84 12.1. Normative References . . . . . . . . . . . . . . . . . . . 43 85 12.2. Informative References . . . . . . . . . . . . . . . . . . 44 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 45 88 1. Introduction 90 This document specifies a format and contents of Domain Name 91 Registration Data Escrow deposits. 93 TBD 95 2. Terminology 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in BCP 14, RFC 2119 100 [RFC2119]. 102 3. General Conventions 104 3.1. Date and Time 106 Numerous fields indicate "dates", such as the creation and expiry 107 dates for domain names. These fields SHALL contain timestamps 108 indicating the date and time in UTC as specified in [RFC3339], with 109 no offset from the zero meridian. 111 3.2. Country names 113 Country identifiers SHALL be represented using two character 114 identifiers as specified in [ISO-3166-1]. 116 3.3. Telephone numbers 118 Telephone numbers (both voice and fax) SHALL be formatted based on 119 structures defined in [ITU-E164]. Telephone numbers described in 120 this specification are character strings that MUST begin with a plus 121 sign ("+", ASCII value 0x002B), followed by a country code defined in 122 [ITU-E164], followed by a dot (".", ASCII value 0x002E), followed by 123 a sequence of digits representing the telephone number. 125 3.4. IP addresses 127 IP addresses syntax MUST conform either to, Internet Protocol 128 [RFC0791], for IPv4 addresses, or IP Version 6 Addressing 129 Architecture [RFC4291], for IPv6 addresses. 131 4. Object Description 133 This section describes the base objects defined in EPP: domains, 134 hosts and contacts with the addition of registrars, IDN Table 135 References, IDNs and EPP parameters. 137 4.1. RDE Domain Object 139 The RDE domain object is based on the EPP domain name mapping 140 specified in [RFC5731]. There are two elements used in this format 141 related to domains: the domain object per se, used inside the 142 element and the object used inside the 143 element. 145 4.1.1. object 147 The domain element is based on the EPP domain response for an 148 authorized client (see Section 3.1.2. of [RFC5731]) with some 149 additions, including the data from an EPP Query Response, 150 see Section 3.1.3. of [RFC5731], RGP status from [RFC3915], and data 151 from the EPP command, see Section 5.2.1. of 152 [RFC5910]. 154 The element contains the following child elements: 156 o A element that contains the fully qualified name of the 157 domain name object. 159 o A element that contains the repository object identifier 160 assigned to the domain name object when it was created. 162 o One or more elements that contain the current status 163 descriptors associated with the domain name. 165 o Zero or more element to represent the different states 166 that a domain name can be in as a result of grace period 167 processing as specified in [RFC3915]. 169 o A element that contain the identifier for the human 170 or organizational social information object associated as the 171 holder of the domain name object. 173 o One or more elements that contain identifiers for the 174 human or organizational social information objects associated with 175 the domain name object. 177 o An element that contains the fully qualified names of the 178 delegated host objects or host attributes (name servers) 179 associated with the domain name object. See Section 1.1 of 180 [RFC5731] for a description of the elements used to specify host 181 objects or host attributes. 183 o Zero or more elements that contain the fully qualified 184 names of the subordinate host objects that exist under this 185 superordinate domain name object. 187 o A element that contains the identifier of the sponsoring 188 registrar. 190 o A element that contains the identifier of the registrar 191 that created the domain name object. 193 o A element that contains the date and time of the domain 194 name object creation. 196 o An element that contains the identifier of the registrar 197 that last updated the domain name object. This element MUST NOT 198 be present if the domain has never been modified. 200 o An element that contains the date and time of the most 201 recent domain-name-object modification. This element MUST NOT be 202 present if the domain name object has never been modified. 204 o An element that contains the date and time identifying 205 the end (expiration) of the domain name object's registration 206 period. 208 o A element that contains the deletion date for the domain. 209 This element is used by registries that support the Domain 210 Registry Grace Period as specified in [RFC3915]. This element 211 MUST be present if the domain name has been deleted, but not yet 212 purged from the registry repository. 214 o An element that contains authorization information 215 associated with the domain name object. 217 o A element that contains the public key information 218 associated with Domain Name System security (DNSSEC) extensions 219 for the domain name as specified in [RFC5910]. 221 o A element that contains the following child elements 222 related to the last transfer request of the domain name object: 224 * A element that contains the state of the most recent 225 transfer request. 227 * A element that contains the identifier of the registrar 228 that requested the domain name object transfer. 230 * A element that contains the date and time that the 231 transfer was requested. 233 * An element that contains the identifier of the registrar 234 that SHOULD act upon a PENDING transfer request. For all other 235 status types, the value identifies the registrar that took the 236 indicated action. 238 * An element that contains the date and time of a 239 required or completed response. For a PENDING request, the 240 value identifies the date and time by which a response is 241 required before an automated response action will be taken by 242 the registry. For all other status types, the value identifies 243 the date and time when the request was completed. 245 * An element that contains the end of the domain name 246 object's validity period (expiry date) if the transfer caused 247 or causes a change in the validity period. 249 Example of a domain object: 251 ... 252 253 pinguino.test 254 Dpinguino-TEST 255 256 257 jd1234 258 sh8013 259 sh8013 260 261 ns1.example.com 262 ns1.example.net 263 264 ns1.pinguino.test 265 ns2.pinguino.test 266 clientX 267 clientY 268 1999-04-03T22:00:00.0Z 269 clientX 270 2009-12-03T09:05:00.0Z 271 2015-04-03T22:00:00.0Z 272 273 2fooBAR 274 275 276 604800 277 278 12345 279 7 280 1 281 282 93358db22e956a451eb5ae8d2ec39526ca6a87b9 283 284 285 286 287 pending 288 clientW 289 2011-03-08T19:38:00.0Z 290 clientX 291 2011-03-13T23:59:59.0Z 292 2016-04-03T22:00:00.0Z 293 294 295 ... 297 4.1.2. object 299 The element contains the fully qualified domain 300 name that was deleted and purged. 302 Example of object: 304 ... 305 306 ... 307 308 foo.test 309 bar.test 310 311 ... 312 313 ... 315 4.2. RDE Host Object 317 The RDE host object is based on the EPP host name mapping in 318 [RFC5732]. There are two elements used in this format related to 319 hosts: the host object per se, used inside the element and 320 the object used inside the element. 322 4.2.1. object 324 The RDE host object is based on the EPP host response for an 325 authorized client (see Section 3.1.2. of [RFC5732]). 327 The element contains the following child elements: 329 o A element that contains the fully qualified name of the 330 host object. 332 o A element that contains the repository object identifier 333 assigned to the host object when the object was created. 335 o One or more elements that describe the status of the host 336 object. 338 o Zero or more elements that contain the IP addresses 339 associated with the host object. 341 o A element that contains the identifier of the sponsoring 342 registrar. 344 o A element that contains the identifier of the registrar 345 that created the host object. 347 o A element that contains the date and time of host-object 348 creation. 350 o An element that contains the identifier of the registrar 351 that last updated the host object. This element MUST NOT be 352 present if the host object has never been modified. 354 o An element that contains the date and time of the most 355 recent host-object modification. This element MUST NOT be present 356 if the host object has never been modified. 358 o A element that contains the date and time of the most 359 recent successful host-object transfer. This element MUST NOT be 360 present if the host object has never been transferred. Note that 361 host objects are not transferred directly; host objects are 362 transferred implicitly when the host object's superordinate domain 363 object is transferred. Host objects that are subject to transfer 364 when transferring a domain object are listed in the element 365 subordinate to the element described above. 367 Example of object: 369 ... 370 371 ns1.example.test 372 Hns1_example_test-TEST 373 374 375 192.0.2.2 376 192.0.2.29 377 1080:0:0:0:8:800:200C:417A 378 clientY 379 clientX 380 1999-05-08T12:10:00.0Z 381 clientX 382 2009-10-03T09:34:00.0Z 383 2007-01-08T09:19:00.0Z 384 385 ... 387 4.2.2. object 389 The element contains the fully qualified domain name 390 of a host that was deleted. 392 Example of object: 394 ... 395 396 ... 397 398 ns1.example.test 399 400 ... 401 402 ... 404 4.3. RDE Contact Object 406 The RDE contact object is based on the EPP contact name mapping in 407 [RFC5733]. There are two elements used in this format related to 408 contacts: the contact object per se, used inside the 409 element and the object used inside the 410 element. 412 4.3.1. object 414 The contact object is based on the EPP contact response for an 415 authorized client (see Section 3.1.2. of [RFC5733]) with some 416 additions including the data from an EPP Query Response, 417 see Section 3.1.3. of [RFC5733]. 419 The element contains the following child elements: 421 o An element that contains the repository object identifier 422 assigned to the contact object when the object was created. 424 o One or more elements that describe the status of the 425 contact object. 427 o One or two elements that contain postal-address 428 information. Two elements are provided so that address 429 information can be provided in both internationalized and 430 localized forms; a "type" attribute is used to identify the two 431 forms. If an internationalized form (type="int") is provided, 432 element content MUST be represented in a subset of UTF-8 that can 433 be represented in the 7-bit US-ASCII character set. If a 434 localized form (type="loc") is provided, element content MAY be 435 represented in unrestricted UTF-8. The element 436 contains the following child elements: 438 * A element that contains the name of the individual or 439 role represented by the contact. 441 * An element that contains the name of the organization 442 with which the contact is affiliated. 444 * An element that contains address information associated 445 with the contact. An element contains the following 446 child elements: 448 + One, two, or three elements that contain the 449 contact's street address. 451 + A element that contains the contact's city. 453 + A element that contains the contact's state or 454 province. 456 + A element that contains the contact's postal code. 458 + A element that contains the contact's two-letter 459 country code. 461 o A element that contains the contact's voice telephone 462 number. 464 o A element that contains the contact's facsimile telephone 465 number. 467 o An element that contains the contact's email address. 469 o A element that contains the identifier of the sponsoring 470 registrar. 472 o A element that contains the identifier of the registrar 473 that created the contact object. 475 o A element that contains the date and time of contact- 476 object creation. 478 o An element that contains the identifier of the registrar 479 that last updated the contact object. This element MUST NOT be 480 present if the contact has never been modified. 482 o An element that contains the date and time of the most 483 recent contact-object modification. This element MUST NOT be 484 present if the contact object has never been modified. 486 o An element that contains authorization information 487 associated with the contact object. 489 o A element that identifies elements that require 490 exceptional server-operator handling to allow or restrict 491 disclosure to third parties. See Section 2.9 of [RFC5733] for a 492 description of the child elements contained within the 493 element. 495 o A element that contains the following child elements 496 related to the last transfer request of the contact object: 498 * A element that contains the state of the most recent 499 transfer request. 501 * A element that contains the identifier of the registrar 502 that requested the domain name object transfer. 504 * A element that contains the date and time that the 505 transfer was requested. 507 * An element that contains the identifier of the registrar 508 that SHOULD act upon a PENDING transfer request. For all other 509 status types, the value identifies the registrar that took the 510 indicated action. 512 * An element that contains the date and time of a 513 required or completed response. For a PENDING request, the 514 value identifies the date and time by which a response is 515 required before an automated response action will be taken by 516 the registry. For all other status types, the value identifies 517 the date and time when the request was completed. 519 Example object: 521 ... 522 523 sh8013 524 Csh8013-TEST 525 526 527 528 John Doe 529 Example Inc. 530 531 123 Example Dr. 532 Suite 100 533 Dulles 534 VA 535 20166-6503 536 US 537 538 539 +1.7035555555 540 +1.7035555556 541 jdoe@example.test 542 clientY 543 clientX 544 2009-09-13T08:01:00.0Z 545 clientX 546 2009-11-26T09:10:00.0Z 547 548 2fooBAR 549 550 551 552 553 554 555 pending 556 clientW 557 2011-03-08T19:38:00.0Z 558 clientX 559 2011-03-13T23:59:59.0Z 560 561 562 ... 564 4.3.2. object 566 The element contains the id of a contact that was 567 deleted. 569 Example of object: 571 ... 572 573 ... 574 575 sh8013-TEST 576 co8013-TEST 577 578 ... 579 580 ... 582 4.4. RDE Registrar Object 584 The RDE registrar object is based on the EPP contact name mapping 585 previously described. There are two elements used in this format 586 related to registrars: the registrar object per se, used inside the 587 element and the object used inside 588 the element. 590 4.4.1. object 592 The element contains the following child elements: 594 o An element that contains the Registry-unique identifier of 595 the registrar object. This has a superordinate relationship 596 to a subordinate , or of domain, contact and 597 host objects. 599 o An OPTIONAL element that contains the ID assigned by 600 ICANN. 602 o One or two elements that contain postal- address 603 information. Two elements are provided so that address 604 information can be provided in both internationalized and 605 localized forms; a "type" attribute is used to identify the two 606 forms. If an internationalized form (type="int") is provided, 607 element content MUST be represented in a subset of UTF-8 that can 608 be represented in the 7-bit US-ASCII character set. If a 609 localized form (type="loc") is provided, element content MAY be 610 represented in unrestricted UTF-8. The element 611 contains the following child elements: 613 * An OPTIONAL element that contains the name of the 614 organization with which the registrar is affiliated. 616 * A element that contains address information associated 617 with the registrar. The element contains the following 618 child elements: 620 + One, two, or three OPTIONAL elements that contain 621 the registrar's street address. 623 + A element that contains the registrar's city. 625 + An OPTIONAL element that contains the registrar's state 626 or province. 628 + An OPTIONAL element that contains the registrar's 629 postal code. 631 + A element that contains the registrar's country code. 633 o An OPTIONAL element that contains the registrar's voice 634 telephone number. 636 o An OPTIONAL element that contains the registrar's facsimile 637 telephone number. 639 o An element that contains the registrar's email address. 641 o A element that contains the registrar's URL. 643 o An OPTIONAL elements that contains whois information. 644 The element contains the following child elements: 646 * An OPTIONAL element that contains the name of the 647 registrar WHOIS server listenin on TCP port 43 as specified in 648 [RFC3912]. 650 * An OPTIONAL element that contains the name of the 651 registrar WHOIS server listenin on TCP port 80/443. 653 o One or more OPTIONAL elements that contain identifiers 654 for the human or organizational social information objects 655 associated with the registrar object. 657 o A element that contains the date and time of registrar- 658 object creation. 660 o A element that contains the date and time of the most 661 recent RDE registrar-object modification. This element MUST NOT 662 be present if the rdeRegistrar object has never been modified. 664 o An OPTIONAL element that contains authorization 665 information associated with the registar object to allow access to 666 registry systems. This specification describes password-based 667 authorization information, though other mechanisms are possible. 669 Example of object: 671 ... 672 673 clientX 674 RclientX-TEST 675 123 676 677 John Doe 678 Example Inc. 679 680 123 Example Dr. 681 Suite 100 682 Dulles 683 VA 684 20166-6503 685 US 686 687 688 +1.7035555555 689 +1.7035555556 690 jdoe@example.test 691 http://www.example.test 692 693 whois.example.test 694 http://whois.example.test 695 https://whois.example.test 696 697 rr0013 698 rr0012 699 2005-04-23T11:49:00.0Z 700 2009-02-17T17:51:00.0Z 701 702 tHisaPaSSw 703 704 705 ... 707 4.4.2. object 709 The element contains the id of a registrar that 710 was deleted. 712 Example of object: 714 ... 715 716 ... 717 718 agnt0001-TEST 719 720 ... 721 722 ... 724 4.5. RDE IDN Table Reference 726 The RDE Internationalized Domain Names (IDN) Table reference is a 727 pseudobject that is used to provide a short reference to the IDN 728 Table used in IDN registrations. The element has an 729 "id" attribute that is used to uniquely identify an IDN Table stored 730 externally. 732 The has only one child element, that contains the 733 URL of the IDN table that is being referenced. 735 Example of object: 737 ... 738 739 740 http://www.iana.org/domains/idn-tables/tables/cl_latn_1.0.html 741 742 743 ... 745 4.6. RDE IDN object 747 4.6.1. IDN Variants Handling 749 Depending on the Registration Policy in place in the Registry; for a 750 particular IDN there may be multiple variant names either canonical, 751 blocked, withheld, allocated, mirrored, or delegated. See Section 5 752 of [variantTLDsReport] for further detail on variant name states. 753 IDN variant names will be tagged as follows: 755 1. If the IDN is considered to be the base or primary string upon 756 which the IDN variants are formed, the IDN object will be tagged 757 as "canonical". 759 2. If the IDN variant is considered undesirable for registration 760 (i.e., unavailable for allocation to anyone), the variant will be 761 tagged as "blocked". 763 3. If only the holder of the canonical domain name is allowed to 764 register the IDN variant but it is not currently allocated, the 765 variant will be tagged as "withheld". 767 4. If the IDN variant is allocated to the holder of the canonical 768 domain name though, it is not active in the DNS, the variant will 769 be tagged as "allocated". 771 5. If the IDN variant is allocated to the holder of the canonical 772 domain name, it is active in the DNS, and also has a mirroring 773 requirement, the variant will be tagged as "mirrored". 775 6. If the IDN variant is allocated to the holder of the cannonical 776 domain name, it has been delegated, but there is no requirement 777 for the two names to be mirrored, the variant will be tagged as 778 "delegated". 780 IDN variants tagged as "blocked" or "withheld" SHOULD be escrowed if 781 explicitly declared and known. All other variants MUST be escrowed. 783 4.6.2. object 785 The element contains the following child elements: 787 o An element that contains the ASCII Compatible Encoding 788 (ACE) of an IDN. 790 o An element that contains the name of the IDN in Unicode 791 character set. It MUST be provided if available. 793 o A element that indicates the type of variant this IDN is: 794 canonical, blocked, withheld, allocated, mirrored, or delegated. 795 See Section 4.6.1 above. 797 o An element that references the IDN Table used for the 798 IDN. This corresponds to the "id" attribute of the 799 element. 801 o A element that contains the repository object identifier of 802 the corresponding domain object, if there is one. It MUST be 803 provided if the domain object exists. 805 o A element that contains the repository object 806 identifier of the canonical domain name. It MUST be provided if 807 the IDN is NOT the canonical domain name. 809 Example of object: 811 ... 812 813 xn--pingino-q2a.test 814 pingueino.test 815 withheld 816 cl-es 817 Dpinguino-TEST 818 819 ... 821 4.6.3. object 823 The element contains the ACE of an IDN that was 824 deleted, i.e., the . 826 Example of object: 828 ... 829 830 ... 831 832 xn--pingino-q2a.test 833 834 ... 835 836 ... 838 4.7. RDE EPP Parameters object 840 An OPTIONAL element contains some EPP parameters that may 841 be helpful when rebuilding a registry from the escrow deposits. The 842 element SHOULD be included in Deposits if the registry uses EPP. 844 The syntax and content of the children elements is as 845 explained in section 2.4 of [RFC5730]. The children of the 846 are as follows: 848 o One or more elements that indicate the EPP versions 849 supported by the registry. 851 o One or more elements that indicate the identifiers of the 852 text response languages supported by the registry's EPP server. 854 o One or more elements that contain namespace URIs 855 representing the objects that the registry's EPP server is capable 856 of managing. 858 o An OPTIONAL element that contains one or more 859 elements that contain namespace URIs representing object 860 extensions supported by the registry's EPP server. 862 o A element that contains child elements used to describe the 863 server's privacy policy for data collection and management. See 864 section 2.4 of [RFC5730] for more details. 866 Example of element object: 868 869 873 ... 874 875 876 1.0 877 en 878 879 urn:ietf:params:xml:ns:domain-1.0 880 881 882 urn:ietf:params:xml:ns:contact-1.0 883 884 885 urn:ietf:params:xml:ns:host-1.0 886 887 888 889 urn:ietf:params:xml:ns:rgp-1.0 890 891 892 urn:ietf:params:xml:ns:secDNS-1.1 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 ... 913 914 ... 915 917 5. Formal Syntax 919 Seven schemas are presented here. The first schema is the base RDE 920 schema. The second schema defines domain object for RDE. The third 921 schema defines host object for RDE. The fourth schema defines 922 contact object for RDE. The fifth schema defines registrar object 923 for RDE. The sixth schema defines the idnTableRef and IDN objects. 924 The last schema defines the eppParams objects. 926 5.1. RDE Domain Object 928 Copyright (c) 2011 IETF Trust and the persons identified as authors 929 of the code. All rights reserved. 931 Redistribution and use in source and binary forms, with or without 932 modification, are permitted provided that the following conditions 933 are met: 935 o Redistributions of source code must retain the above copyright 936 notice, this list of conditions and the following disclaimer. 938 o Redistributions in binary form must reproduce the above copyright 939 notice, this list of conditions and the following disclaimer in 940 the documentation and/or other materials provided with the 941 distribution. 943 o Neither the name of Internet Society, IETF or IETF Trust, nor the 944 names of specific contributors, may be used to endorse or promote 945 products derived from this software without specific prior written 946 permission. 948 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 949 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 950 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 951 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 952 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 953 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 954 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 955 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 956 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 957 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 958 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 960 BEGIN 961 963 973 976 978 980 982 984 987 988 989 Registry Data Escrow Domain provisioning schema 990 991 993 996 999 1000 1001 1002 1003 1005 1008 1011 1012 1013 1014 1015 1016 1017 1019 1021 1023 1025 1027 1029 1030 1032 1034 1036 1038 1040 1042 1044 1046 1048 1049 1050 1051 1053 1054 1055 1056 1057 1058 1059 1060 1062 1063 1065 1068 1071 1072 1073 1074 1075 1077 1078 1079 1080 1082 1085 1086 END 1088 5.2. RDE Host Object 1090 Copyright (c) 2011 IETF Trust and the persons identified as authors 1091 of the code. All rights reserved. 1093 Redistribution and use in source and binary forms, with or without 1094 modification, are permitted provided that the following conditions 1095 are met: 1097 o Redistributions of source code must retain the above copyright 1098 notice, this list of conditions and the following disclaimer. 1100 o Redistributions in binary form must reproduce the above copyright 1101 notice, this list of conditions and the following disclaimer in 1102 the documentation and/or other materials provided with the 1103 distribution. 1105 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1106 names of specific contributors, may be used to endorse or promote 1107 products derived from this software without specific prior written 1108 permission. 1110 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1111 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1112 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1113 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1114 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1115 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1116 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1117 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1118 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1119 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1120 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1122 BEGIN 1123 1125 1133 1136 1138 1140 1143 1144 1145 Registry Data Escrow host provisioning schema 1146 1147 1149 1152 1155 1156 1157 1159 1160 1162 1165 1168 1169 1170 1171 1172 1173 1174 1176 1178 1179 1180 1181 1183 1185 1187 1188 1189 1190 1192 1195 1198 1199 1200 1201 1202 1204 1205 1206 1208 1210 1213 1214 END 1216 5.3. RDE Contact Object 1218 Copyright (c) 2011 IETF Trust and the persons identified as authors 1219 of the code. All rights reserved. 1221 Redistribution and use in source and binary forms, with or without 1222 modification, are permitted provided that the following conditions 1223 are met: 1225 o Redistributions of source code must retain the above copyright 1226 notice, this list of conditions and the following disclaimer. 1228 o Redistributions in binary form must reproduce the above copyright 1229 notice, this list of conditions and the following disclaimer in 1230 the documentation and/or other materials provided with the 1231 distribution. 1233 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1234 names of specific contributors, may be used to endorse or promote 1235 products derived from this software without specific prior written 1236 permission. 1238 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1239 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1240 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1241 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1242 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1243 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1244 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1245 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1246 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1247 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1248 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1250 BEGIN 1251 1253 1261 1264 1266 1268 1271 1272 1273 Registry Data Escrow contact provisioning schema 1274 1275 1277 1280 1283 1284 1285 1286 1287 1289 1292 1295 1296 1297 1298 1299 1300 1301 1303 1305 1307 1309 1310 1311 1312 1313 1315 1317 1319 1321 1323 1324 1325 1326 1328 1329 1330 1331 1332 1333 1334 1335 1336 1338 1341 1344 1345 1346 1347 1348 1350 1351 1353 1354 1356 1359 1360 END 1362 5.4. RDE Registrar Object 1364 Copyright (c) 2011 IETF Trust and the persons identified as authors 1365 of the code. All rights reserved. 1367 Redistribution and use in source and binary forms, with or without 1368 modification, are permitted provided that the following conditions 1369 are met: 1371 o Redistributions of source code must retain the above copyright 1372 notice, this list of conditions and the following disclaimer. 1374 o Redistributions in binary form must reproduce the above copyright 1375 notice, this list of conditions and the following disclaimer in 1376 the documentation and/or other materials provided with the 1377 distribution. 1379 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1380 names of specific contributors, may be used to endorse or promote 1381 products derived from this software without specific prior written 1382 permission. 1384 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1385 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1386 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1387 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1388 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1389 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1390 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1391 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1392 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1393 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1394 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1396 BEGIN 1397 1399 1408 1411 1413 1415 1417 1420 1421 1422 Registry Data Escrow registrar provisioning schema 1423 1424 1426 1429 1432 1433 1434 1435 1436 1438 1441 1444 1445 1446 1447 1448 1449 1450 1452 1454 1456 1458 1460 1462 1464 1466 1467 1469 1471 1472 1473 1474 1476 1477 1478 1480 1482 1483 1485 1488 1491 1492 1493 1494 1495 1498 1499 1500 1501 1503 1506 1507 END 1509 5.5. RDE IDN and IDN Table Reference Objects 1511 Copyright (c) 2011 IETF Trust and the persons identified as authors 1512 of the code. All rights reserved. 1514 Redistribution and use in source and binary forms, with or without 1515 modification, are permitted provided that the following conditions 1516 are met: 1518 o Redistributions of source code must retain the above copyright 1519 notice, this list of conditions and the following disclaimer. 1521 o Redistributions in binary form must reproduce the above copyright 1522 notice, this list of conditions and the following disclaimer in 1523 the documentation and/or other materials provided with the 1524 distribution. 1526 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1527 names of specific contributors, may be used to endorse or promote 1528 products derived from this software without specific prior written 1529 permission. 1531 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1532 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1533 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1534 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1535 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1536 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1537 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1538 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1539 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1540 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1541 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1543 BEGIN 1544 1545 1552 1555 1557 1560 1561 1562 Registry Data Escrow IDN provisioning schema 1563 1564 1566 1569 1572 1573 1574 1575 1576 1578 1581 1584 1585 1586 1587 1588 1589 1591 1592 1593 1595 1597 1598 1599 1600 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1613 1616 1619 1620 1621 1622 1623 1625 1626 1627 1628 1630 1633 1636 1637 1638 1639 1640 1642 1643 1644 1645 1646 1648 1651 1652 END 1654 5.6. EPP Parameters Object 1656 Copyright (c) 2011 IETF Trust and the persons identified as authors 1657 of the code. All rights reserved. 1659 Redistribution and use in source and binary forms, with or without 1660 modification, are permitted provided that the following conditions 1661 are met: 1663 o Redistributions of source code must retain the above copyright 1664 notice, this list of conditions and the following disclaimer. 1666 o Redistributions in binary form must reproduce the above copyright 1667 notice, this list of conditions and the following disclaimer in 1668 the documentation and/or other materials provided with the 1669 distribution. 1671 o Neither the name of Internet Society, IETF or IETF Trust, nor the 1672 names of specific contributors, may be used to endorse or promote 1673 products derived from this software without specific prior written 1674 permission. 1676 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 1677 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 1678 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 1679 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 1680 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 1681 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 1682 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 1683 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 1684 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 1685 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 1686 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1688 BEGIN 1689 1690 1698 1701 1703 1705 1708 1709 1710 Registry Data Escrow EPP Parameters schema 1711 1712 1714 1717 1720 1721 1722 1723 1724 1726 1729 1732 1733 1734 1735 1736 1739 1741 1743 1745 1746 1747 1748 1749 1751 1754 1755 END 1757 6. Extension Guidelines 1759 TBD 1761 7. Internationalization Considerations 1763 Data Escrow deposits are represented in XML, which provides native 1764 support for encoding information using the Unicode character set and 1765 its more compact representations including UTF-8. Conformant XML 1766 processors recognize both UTF-8 and UTF-16. Though XML includes 1767 provisions to identify and use other character encodings through use 1768 of an "encoding" attribute in an declaration, use of UTF-8 is 1769 RECOMMENDED. 1771 8. IANA Considerations 1773 This document uses URNs to describe XML namespaces and XML schemas 1774 conforming to a registry mechanism described in [RFC3688]. Fourteen 1775 URI assignments have been registered by the IANA. 1777 Registration request for the RDE namespace: 1779 URI: urn:ietf:params:xml:ns:rde-1.0 1781 Registrant Contact: See the "Author's Address" section of this 1782 document. 1784 XML: None. Namespace URIs do not represent an XML specification. 1786 Registration request for the RDE XML schema: 1788 URI: urn:ietf:params:xml:schema:rde-1.0 1790 Registrant Contact: See the "Author's Address" section of this 1791 document. 1793 See the "Formal Syntax" section of this document. 1795 Registration request for the RDE domain namespace: 1797 URI: urn:ietf:params:xml:ns:rdeDomain-1.0 1799 Registrant Contact: See the "Author's Address" section of this 1800 document. 1802 XML: None. Namespace URIs do not represent an XML specification. 1804 Registration request for the RDE domain XML schema: 1806 URI: urn:ietf:params:xml:schema:rdeDomain-1.0 1808 Registrant Contact: See the "Author's Address" section of this 1809 document. 1811 See the "Formal Syntax" section of this document. 1813 Registration request for the RDE host namespace: 1815 URI: urn:ietf:params:xml:ns:rdeHost-1.0 1817 Registrant Contact: See the "Author's Address" section of this 1818 document. 1820 XML: None. Namespace URIs do not represent an XML specification. 1822 Registration request for the RDE host XML schema: 1824 URI: urn:ietf:params:xml:schema:rdeHost-1.0 1826 Registrant Contact: See the "Author's Address" section of this 1827 document. 1829 See the "Formal Syntax" section of this document. 1831 Registration request for the RDE contact namespace: 1833 URI: urn:ietf:params:xml:ns:rdeContact-1.0 1835 Registrant Contact: See the "Author's Address" section of this 1836 document. 1838 XML: None. Namespace URIs do not represent an XML specification. 1840 Registration request for the RDE contact XML schema: 1842 URI: urn:ietf:params:xml:schema:rdeContact-1.0 1844 Registrant Contact: See the "Author's Address" section of this 1845 document. 1847 See the "Formal Syntax" section of this document. 1849 Registration request for the RDE registrar namespace: 1851 URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0 1853 Registrant Contact: See the "Author's Address" section of this 1854 document. 1856 XML: None. Namespace URIs do not represent an XML specification. 1858 Registration request for the RDE registrar XML schema: 1860 URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0 1862 Registrant Contact: See the "Author's Address" section of this 1863 document. 1865 See the "Formal Syntax" section of this document. 1867 Registration request for the RDE IDN namespace: 1869 URI: urn:ietf:params:xml:ns:rdeIDN-1.0 1871 Registrant Contact: See the "Author's Address" section of this 1872 document. 1874 XML: None. Namespace URIs do not represent an XML specification. 1876 Registration request for the RDE IDN XML schema: 1878 URI: urn:ietf:params:xml:schema:rdeIDN-1.0 1879 Registrant Contact: See the "Author's Address" section of this 1880 document. 1882 See the "Formal Syntax" section of this document. 1884 Registration request for the RDE EPP parameters namespace: 1886 URI: urn:ietf:params:xml:ns:rdeEppParams-1.0 1888 Registrant Contact: See the "Author's Address" section of this 1889 document. 1891 XML: None. Namespace URIs do not represent an XML specification. 1893 Registration request for the RDE EPP parameters XML schema: 1895 URI: urn:ietf:params:xml:schema:rdeEppParams-1.0 1897 Registrant Contact: See the "Author's Address" section of this 1898 document. 1900 See the "Formal Syntax" section of this document. 1902 9. Security Considerations 1904 This specification does not define the security mechanisms to be used 1905 in the transmission of the data escrow deposits, since it only 1906 specifies the minimum necessary to enable the rebuilding of a 1907 Registry from deposits without intervention from the original 1908 Registry. 1910 Depending on local policies, some elements or most likely, the whole 1911 deposit will be considered confidential. As such the Registry 1912 transmitting the data to the Escrow Agent SHOULD take all the 1913 necessary precautions like encrypting the data itself and/or the 1914 transport channel to avoid inadvertent disclosure of private data. 1916 It is also of the utmost importance the authentication of the parties 1917 passing data escrow deposit files. The Escrow Agent SHOULD properly 1918 authenticate the identity of the Registry before accepting data 1919 escrow deposits. In a similar manner, the Registry SHOULD 1920 authenticate the identity of the Escrow Agent before submitting any 1921 data. 1923 Additionally, the Registry and the Escrow Agent SHOULD use integrity 1924 checking mechanisms to ensure the data transmitted is what the source 1925 intended. Validation of the contents by the Escrow Agent is 1926 RECOMMENDED to ensure not only the file was transmitted correctly 1927 from the Registry, but also the contents are also "meaningful". 1929 10. Acknowledgments 1931 Parts of this document are based on EPP [RFC5730] and related RFCs by 1932 Scott Hollenbeck. 1934 TBD 1936 11. Change History 1938 [[RFC Editor: Please remove this section.]] 1940 11.1. Changes from draft-arias-noguchi-registry-data-escrow-02 to 1941 -dnrd-objects-mapping-00 1943 1. Added definition for child elements under the element. 1945 2. Added definition for child elements under the element. 1947 3. Added definition for child elements under the element. 1949 4. Rewrote the IDN Variants Handling section to use the variant 1950 states as described in ICANN's Study of Issues Related to the 1951 Management of IDN Variant TLDs. 1953 5. Renamed to in the . 1955 6. Renamed to in the element. 1957 7. Renamed to in the element. 1959 8. Added element under element. 1961 9. Fixed some typographical errors and omissions. 1963 12. References 1965 12.1. Normative References 1967 [I-D.arias-noguchi-registry-data-escrow] 1968 Arias, F. and S. Noguchi, "Domain Name Data Escrow 1969 Specification", 1970 draft-arias-noguchi-registry-data-escrow-02 (work in 1971 progress), March 2011. 1973 [ISO-3166-1] 1974 International Organization for Standardization, "Codes for 1975 the representation of names of countries and their 1976 subdivisions -- Part 1: Country codes", ISO Standard 3166, 1977 November 2006. 1979 [ITU-E164] 1980 International Telecommunication Union, "The international 1981 public telecommunication numbering plan", ITU-T 1982 Recommendation E.164, February 2005. 1984 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1985 Requirement Levels", BCP 14, RFC 2119, March 1997. 1987 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 1988 Internet: Timestamps", RFC 3339, July 2002. 1990 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 1991 the Extensible Provisioning Protocol (EPP)", RFC 3915, 1992 September 2004. 1994 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1995 Domain Name Mapping", STD 69, RFC 5731, August 2009. 1997 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1998 Host Mapping", STD 69, RFC 5732, August 2009. 2000 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 2001 Contact Mapping", STD 69, RFC 5733, August 2009. 2003 [RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS) 2004 Security Extensions Mapping for the Extensible 2005 Provisioning Protocol (EPP)", RFC 5910, May 2010. 2007 12.2. Informative References 2009 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 2010 September 1981. 2012 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2013 January 2004. 2015 [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, 2016 September 2004. 2018 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2019 Architecture", RFC 4291, February 2006. 2021 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 2022 STD 69, RFC 5730, August 2009. 2024 [variantTLDsReport] 2025 Internet Corporation for Assigned Names and Numbers 2026 (ICANN), "A Study of Issues Related to the Management of 2027 IDN Variant TLDs", February 2012, . 2031 Authors' Addresses 2033 Francisco Arias 2034 Internet Corporation for Assigned Names and Numbers 2035 4676 Admiralty Way, Suite 330 2036 Marina del Rey 90292 2037 United States of America 2039 Phone: +1.310.823.9358 2040 Email: francisco.arias@icann.org 2042 Shoji Noguchi 2043 Japan Registry Services Co., Ltd. 2044 Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda 2045 Chiyoda-ku, Tokyo 101-0065 2046 Japan 2048 Phone: +81.3.5215.8451 2049 Email: noguchi@jprs.co.jp