idnits 2.17.1 draft-yao-regext-bundling-registration-06.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 (June 3, 2021) is 1051 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Yao 3 Internet-Draft L. Zhou 4 Intended status: Informational H. Li 5 Expires: December 6, 2021 CNNIC 6 N. Kong 7 Consultant 8 W. Tan 9 Cloud Registry 10 J. Xie 11 June 3, 2021 13 Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for 14 Strict Bundling Registration 15 draft-yao-regext-bundling-registration-06 17 Abstract 19 This document describes an extension of Extensible Provisioning 20 Protocol (EPP) domain name mapping for the provisioning and 21 management of strict bundling registration of domain names. 22 Specified in XML, this mapping extends the EPP domain name mapping to 23 provide additional features required for the provisioning of bundled 24 domain names. This is a non-standard proprietary extension. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on December 6, 2021. 43 Copyright Notice 45 Copyright (c) 2021 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 4. Requirement for Bundling Registration of Names . . . . . . . 6 64 5. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 7 65 5.1. RDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 66 5.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 67 6. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 68 6.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 69 6.1.1. EPP Command . . . . . . . . . . . . . . . . . 8 70 6.1.2. EPP Command . . . . . . . . . . . . . . . . . 9 71 6.1.3. EPP Query Command . . . . . . . . . . . . 10 72 6.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 10 73 6.2.1. EPP Command . . . . . . . . . . . . . . . . 11 74 6.2.2. EPP Command . . . . . . . . . . . . . . . . 13 75 6.2.3. EPP Command . . . . . . . . . . . . . . . . . 14 76 6.2.4. EPP Command . . . . . . . . . . . . . . . 15 77 6.2.5. EPP Command . . . . . . . . . . . . . . . . 16 78 7. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 17 79 8. Internationalization Considerations . . . . . . . . . . . . . 19 80 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 81 9.1. XML Namespace and XML Schema . . . . . . . . . . . . . . 19 82 9.1.1. BDN Namespace . . . . . . . . . . . . . . . . . . . . 20 83 9.1.2. BDN XML Schema . . . . . . . . . . . . . . . . . . . 20 84 9.2. EPP Extension . . . . . . . . . . . . . . . . . . . . . . 20 85 10. Security Considerations . . . . . . . . . . . . . . . . . . . 21 86 11. Implementation Status and some clarifications . . . . . . . . 21 87 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 88 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 89 13.1. Normative References . . . . . . . . . . . . . . . . . . 22 90 13.2. Informative References . . . . . . . . . . . . . . . . . 23 91 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 93 1. Introduction 95 In RFC4290 [RFC4290], the "variant(s)" are character(s) and/or 96 string(s) that are treated as equivalent to the base character. In 97 this document, variants are those strings that are treated to be 98 equivalent to each other according to the domain name registration 99 policy. Bundled domain names are those which share the same Top 100 Level Domain (TLD) but whose second level labels are variants, or 101 those which have identical second level labels for which certain 102 parameters are shared in different TLDs. For example, Public 103 Interest Registry has requested to implement bundling of second level 104 domains for .NGO and .ONG. So we have two kinds of bundled domain 105 names. The first one is in the form of "V-label.TLD" in which the 106 second level label (V-label) is a variant sharing the same TLD; The 107 second one is in the form of "LABEL.V-tld" in which the second level 108 label (LABEL) remains the same but ending with a different TLD 109 (V-tld), and these different V-tlds are managed by the same entity. 111 Bundled domain names normally share some attributes. Policy-wise 112 bundling can be implemented in three ways. The first one is strict 113 bundling, which requires all bundled names to share many of the same 114 attributes. When creating, updating, or transferring any of the 115 bundled domain names, all bundled domain names will be created, 116 updated or transferred atomically. The second one is partial 117 bundling, which requires the bundled domain names to be registered by 118 the same registrant. The third one is relaxed bundling, which has no 119 specific requirements on the domain registration. This document 120 mainly addresses the strict bundling name registration. 122 For the name variants, different registries have different policies. 123 Some registries adopt the policy that variant Internationalized 124 Domain Name (IDNs) should be blocked. But some registries adopt the 125 policy that variant IDNs which are identified as equivalent are 126 allocated or delegated to the same registrant. For example, most 127 registries offering Chinese Domain Name (CDN) adopt a registration 128 policy whereby a registrant can apply for an original CDN in any 129 forms: Simplified Chinese (SC) form, Traditional Chinese (TC) form, 130 or other variant forms, then the corresponding variant CDN in SC form 131 and that in TC form will also be delegated to the same registrant. 132 All variant names in the same TLD share a common set of attributes. 133 This document mainly discuss the situation that variant IDNs which 134 are identified as equivalent are allocated or delegated to the same 135 registrant. 137 The basic Extensible Provisioning Protocol (EPP) domain name mapping 138 [RFC5731] provides the facility for single domain name registration. 139 It does not specify how to register the strict bundled names which 140 share many of the attributes. 142 In order to meet the above requirements of strict bundled name 143 registration, this document describes an extension of the EPP domain 144 name mapping [RFC5731] for the provisioning and management of bundled 145 names. This document describes a non-standard proprietary extension. 146 This extension is especially useful for registries of practicing 147 Chinese domain name registration. This method is also useful for 148 other language domain names that have similar issues with Chinese 149 domain names. This document is specified using Extensible Markup 150 Language (XML) 1.0 as described in [W3C.REC-xml-20040204] and XML 151 Schema notation as described in [W3C.REC-xmlschema-1-20041028] and 152 [W3C.REC-xmlschema-2-20041028]. 154 The EPP core protocol specification [RFC5730] provides a complete 155 description of EPP command and response structures. A thorough 156 understanding of the base protocol specification is necessary to 157 understand the extension mapping described in this document. 159 This document uses many IDN concepts, so a thorough understanding of 160 the IDNs for Application (IDNA, described in [RFC5890], [RFC5891], 161 and [RFC5892]) and the variant approach discussed in [RFC4290] is 162 assumed. 164 2. Terminology 166 Variants in this document are those strings that are treated to be 167 equivalent to each other according to the domain name registration 168 policy for certain TLDs. 170 Bundled domain names are bundled together according to the domain 171 name registration policy. For example, many Chinese domain name 172 registries follow the principle described in RFC3743[RFC3743]. 173 Bundled domain names should belong to the same owner. If bundled 174 domain names are under different TLDs, those TLDs should be managed 175 by the same entity. 177 The terms Registered Domain Name(RDN) and Bundled Domain Name(BDN) 178 are used in this document. RDN represents the valid domain name that 179 registrants submitted for the initial registration. BDN represents 180 the bundled domain name produced according to the bundled domain name 181 registration policy. In current practice, the number of BDNs is 182 usually be kept to one according to the registration policy set by 183 the registry. Both RDN and BDN specified in this document will be 184 registered via EPP. All other domain names related to the RDN will 185 be blocked. 187 uLabel in this document is used to express the U-label of an 188 internationalized domain name as a series of characters where non- 189 ASCII characters will be represented in the format of "&#xXXXX;" 190 where XXXX is a UNICODE point by using the XML escaping mechanism. 191 U-Label is defined in [RFC5890]. This document chooses this format 192 of literal HTML ampersand codes, not the expected UNICODE native 193 characters, is because of that the UNICODE native characters may not 194 be displayed correctly in some text file readers while literal HTML 195 ampersand codes are easy for HTML processors. The implementation 196 following this document should use UNICODE native characters 197 directly. 199 This document uses the prefix "b-dn" for the namespace 200 "urn:ietf:params:xml:ns:epp:b-dn" throughout. Implementations cannot 201 assume that any particular prefix is used, and must employ a 202 namespace-aware XML parser and serializer to interpret and output the 203 XML documents. 205 In examples, "C:" represents lines sent by a protocol client and "S:" 206 represents lines returned by a protocol server. Indentation and 207 white space in examples are provided only to illustrate element 208 relationships and are not a required feature of this specification. 210 XML is case sensitive. Unless stated otherwise, XML specifications 211 and examples provided in this document must be interpreted in the 212 character case presented to develop a conforming implementation. 214 3. Overview 216 Domain registries have traditionally adopted a registration model 217 whereby metadata relating to a domain name, such as its expiration 218 date and sponsoring registrar, are stored as properties of the domain 219 object. The domain object is then considered an atomic unit of 220 registration, on which operations such as update, renewal and 221 deletion may be performed. 223 Bundled names brought about the need for multiple domain names to be 224 registered and managed as a single package. In this model, the 225 registry typically accepts a domain registration request (i.e. EPP 226 domain command) containing the domain name to be registered. 227 This domain name is referred to as the RDN in this document. As part 228 of the processing of the registration request, the registry generates 229 a set of bundled names that are related to the RDN, either 230 programmatically or with the guidance of registration policies, and 231 places them in the registration package together with the RDN. 233 The bundled names share many properties, such as expiration date and 234 sponsoring registrar, by sharing the same domain object. So when 235 registrants update any property of a domain object within a bundle 236 package, that property will be updated at the same time for all other 237 domain objects in the bundle package. 239 4. Requirement for Bundling Registration of Names 241 The bundled names whether they are in the form of "V-label.TLD" or in 242 the form of "LABEL.V-tld" should share some parameters or attributes 243 associated with domain names. Typically, bundled names will share 244 the following parameters or attributes: 246 o Registrar Ownership 248 o Registration and Expiry Dates 250 o Registrant, Admin, Billing, and Technical Contacts 252 o Name Server Association 254 o Domain Status 256 o Applicable grace periods (Add Grace Period, Renewal Grace Period, 257 Auto-Renewal Grace Period, Transfer Grace Period, and Redemption 258 Grace Period) 260 Because the domain names are bundled and share the same parameters or 261 attributes, the EPP command should do some processing for these 262 requirements: 264 o When performing a Domain Check, either BDN or RDN can be queried 265 for the EPP command, and will return the same response. 267 o When performing a Domain Info, either BDN or RDN can be queried, 268 the same response will include both BDN and RDN information with 269 the same attributes. 271 o When performing a Domain Create, if the domain name is available, 272 both BDN and RDN will be registered. 274 o When performing a Domain Delete, either BDN or RDN will be 275 accepted. If the domain name is registered, both BDN and RDN will 276 be deleted. 278 o When performing a Domain Renew, either BDN or RDN will be 279 accepted. Upon a successful domain renewal, both BDN and RDN will 280 have their expiry date extended by the requested term. Upon a 281 successful domain renewal, both BDN and RDN will conform to the 282 same renew grace period. 284 o When performing a Domain Transfer, either BDN or RDN will be 285 accepted. Upon successful completion of a domain transfer 286 request, both BDN and RDN will enter a pendingTransfer status. 288 Upon approval of the transfer request, both BDN and RDN will be 289 owned and managed by the same new registrant. 291 o When performing a Domain Update, either BDN or RDN will be 292 accepted. Any modifications to contact associations, name server 293 associations, domain status values and authorization information 294 will be applied to both BDN and RDN. 296 5. Object Attributes 298 This extension defines following additional elements to the EPP 299 domain name mapping [RFC5731]. All of these additional elements are 300 returned from command. 302 5.1. RDN 304 The RDN is an ASCII name or an IDN with the A-label [RFC5890] form. 305 In this document, its corresponding element is . An 306 optional attribute "uLabel" associated with is used to 307 represent the U-label [RFC5890] form. 309 For example: xn-- 310 fsq270a.example 312 5.2. BDN 314 The BDN is an ASCII name or an IDN with the A-label [RFC5890] form 315 which is converted from the corresponding BDN. In this document, its 316 corresponding element is . An optional attribute "uLabel" 317 associated with is used to represent the U-label [RFC5890] 318 form. 320 For example: xn-- 321 fsqz41a.example 323 6. EPP Command Mapping 325 A detailed description of the EPP syntax and semantics can be found 326 in the EPP core protocol specification [RFC5730]. The command 327 mappings described here are specifically for use in provisioning and 328 managing bundled names via EPP. 330 6.1. EPP Query Commands 332 EPP provides three commands to retrieve domain information: 333 to determine if a domain object can be provisioned within a 334 repository, to retrieve detailed information associated with a 335 domain object, and to retrieve domain-object transfer 336 status information. 338 6.1.1. EPP Command 340 This extension does not add any element to the EPP command or 341 response described in the EPP domain name mapping [RFC5731]. 342 However, when either RDN or BDN is sent for check, response should 343 contain both RDN and BDN information, which may also give some 344 explanation in the reason field to tell the registrant that the 345 associated domain name is a produced name according to some bundle 346 domain name policy. 348 Example response: 349 S: 350 S: 351 S: 352 S: 353 S: Command completed successfully 354 S: 355 S: 356 S: 358 S: 359 S: 360 S: xn--fsq270a.example 361 S: 362 S: 363 S: 364 S: xn--fsqz41a.example 365 S: 366 S: This associated domain name is 367 S: a produced name based on bundle name policy. 368 S: 369 S: 370 S: 371 S: 372 S: 373 S: ABC-12345 374 S: 54322-XYZ 375 S: 376 S: 377 S: 379 6.1.2. EPP Command 381 This extension does not add any element to the EPP command 382 described in the EPP domain mapping [RFC5731]. However, additional 383 elements are defined for the response. 385 When an command has been processed successfully, the EPP 386 element must contain child elements as described in the EPP 387 domain mapping [RFC5731]. In addition, unless some registration 388 policy has some special processing, the EPP element 389 should contain a child element that identifies the 390 extension namespace if the domain object has data associated with 391 this extension and based on its registration policy. The 392 element contains the which has the 393 following child elements: 395 o An element that contains the RDN, along with the 396 attribute described below. 398 o An optional element that contains the BDN, along with 399 the attribute described below. 401 The above elements contain the following attribute: 403 o An optional "uLabel" attribute represents the U-label of the 404 element. 406 Example response for an authorized client: 408 S: 409 S: 410 S: 411 S: 412 S: Command completed successfully 413 S: 414 S: 415 S: 417 S: xn--fsq270a.example 418 S: 58812678-domain 419 S: 420 S: 123 421 S: 123 422 S: 123 423 S: 424 S: ns1.example.cn 425 S: 426 S: 427 S: ClientX 428 S: ClientY 429 S: 2019-04-03T22:00:00.0Z 430 S: 431 S: 2022-04-03T22:00:00.0Z 432 S: 433 S: 434 S: 2fooBAR 435 S: 436 S: 437 S: 438 S: 439 S: 441 S: 442 S: 443 S: xn--fsq270a.example 444 S: 445 S: 446 S: xn--fsqz41a.example 447 S: 448 S: 449 S: 450 S: 451 S: 452 S: ABC-12345 453 S: 54322-XYZ 454 S: 455 S: 456 S: 458 Response for the unauthorized client has not been changed, see 459 [RFC5731] for detail. 461 An EPP error response must be returned if an command cannot be 462 processed for any reason. 464 6.1.3. EPP Query Command 466 This extension does not add any element to the EPP command 467 or response described in the EPP domain mapping [RFC5731]. 469 6.2. EPP Transform Commands 471 EPP provides five commands to transform domain objects: to 472 create an instance of a domain object, to delete an instance 473 of a domain object, to extend the validity period of a domain 474 object, to manage domain object sponsorship changes, and 475 to change information associated with a domain object. 477 When theses commands have been processed successfully, the EPP 478 element must contain child elements as described in the EPP 479 domain mapping [RFC5731]. Unless some registration policy has some 480 special processing, this EPP element should contain the 481 which has the following child elements: 483 o An element that contains the RDN, along with the 484 attribute described below. 486 o An optional element that contains the BDN, along with 487 the attribute described below. 489 The above elements contain the following attribute: 491 o An optional "uLabel" attribute represents the U-label of the 492 element. 494 6.2.1. EPP Command 496 This extension defines additional elements to extend the EPP 497 command described in the EPP domain name mapping [RFC5731] for 498 bundled names registration. 500 In addition to the EPP command elements described in the EPP domain 501 mapping [RFC5731], the command shall contain an 502 element. Unless some registration policy has some special 503 processing, the element should contain a child 504 element that identifies the bundle namespace, and a 505 child element that identifies the U-Label form of the 506 registered domain name with the uLabel attribute. U-Label is used 507 for easy reading by the registrants and easy debugging by the 508 registrars and the registries. 510 Example command: 512 C: 513 C: 514 C: 515 C: 516 C: 518 C: xn--fsq270a.example 519 C: 2 520 C: 123 521 C: 123 522 C: 123 523 C: 524 C: 2fooBAR 525 C: 526 C: 527 C: 528 C: 529 C: 531 C: 532 C: xn--fsq270a.example 533 C: 534 C: 535 C: 536 C: ABC-12345 537 C: 538 C: 540 When a command has been processed successfully, the EPP 541 element must contain child elements as described in the EPP 542 domain mapping [RFC5731]. In addition, unless some registration 543 policy has some special processing, the EPP element 544 should contain a child element that identifies the 545 extension namespace if the domain object has data associated with 546 this extension and based on its registration policy. The 547 element contains the element. 549 Example response: 551 S: 552 S: 553 S: 554 S: 555 S: Command completed successfully 556 S: 557 S: 558 S: 560 S: xn--fsq270a.example 561 S: 2019-04-03T22:00:00.0Z 562 S: 2021-04-03T22:00:00.0Z 563 S: 564 S: 565 S: 566 S: 568 S: 569 S: 570 S: xn--fsq270a.example 571 S: 572 S: 573 S: xn--fsqz41a.example 574 S: 575 S: 576 S: 577 S: 578 S: 579 S: ABC-12345 580 S: 54322-XYZ 581 S: 582 S: 583 S: 585 An EPP error response must be returned if an command cannot 586 be processed for any reason. 588 6.2.2. EPP Command 590 This extension does not add any element to the EPP command 591 described in the EPP domain mapping [RFC5731]. However, additional 592 elements are defined for the response. 594 When a command has been processed successfully, the EPP 595 element must contain child elements as described in the EPP 596 domain mapping [RFC5731]. In addition, unless some registration 597 policy has some special processing, the EPP element 598 should contain a child element that identifies the 599 extension namespace if the domain object has data associated with 600 this extension and based on its registration policy. The 601 element should contain the element. 603 Example response: 605 S: 606 S: 607 S: 608 S: 609 S: Command completed successfully 610 S: 611 S: 612 S: 614 S: 615 S: 616 S: xn--fsq270a.example 617 S: 618 S: 619 S: xn--fsqz41a.example 620 S: 621 S: 622 S: 623 S: 624 S: 625 S: ABC-12345 626 S: 54321-XYZ 627 S: 628 S: 629 S: 631 An EPP error response must be returned if a command cannot 632 be processed for any reason. 634 6.2.3. EPP Command 636 This extension does not add any element to the EPP command 637 described in the EPP domain name mapping [RFC5731]. However, when 638 either RDN or BDN is sent for renew, response should contain both RDN 639 and BDN information. When the command has been processed 640 successfully, the EPP element shall be contained in the 641 response if the domain object has data associated with bundled names. 642 Unless some registration policy has some special processing, this EPP 643 element should contain the which contains 644 element. 646 Example response: 648 S: 649 S: 650 S: 651 S: 652 S: Command completed successfully 653 S: 654 S: 655 S: 657 S: xn--fsq270a.example 658 S: 2022-04-03T22:00:00.0Z 659 S: 660 S: 661 S: 662 S: 664 S: 665 S: 666 S: xn--fsq270a.example 667 S: 668 S: 669 S: xn--fsqz41a.example 670 S: 671 S: 672 S: 673 S: 674 S: 675 S: ABC-12345 676 S: 54322-XYZ 677 S: 678 S: 679 S: 681 6.2.4. EPP Command 683 This extension does not add any element to the EPP command 684 described in the EPP domain name mapping [RFC5731]. However, 685 additional elements are defined for the response in the 686 EPP object mapping. When the command has been processed 687 successfully, the EPP element shall be contained in the 688 response if the domain object has data associated with bundled names. 689 Unless some registration policy has some special processing, this EPP 690 element should contain the which contains 691 element. 693 Example response: 695 S: 696 S: 697 S: 698 S: 699 S: Command completed successfully; action pending 700 S: 701 S: 702 S: 704 S: xn--fsq270a.example 705 S: pending 706 S: ClientX 707 S: 2021-04-03T22:00:00.0Z 708 S: ClientY 709 S: 2021-04-08T22:00:00.0Z 710 S: 2022-04-03T22:00:00.0Z 711 S: 712 S: 713 S: 714 S: 716 S: 717 S: 718 S: xn--fsq270a.example 719 S: 720 S: 721 S: xn--fsqz41a.example 722 S: 723 S: 724 S: 725 S: 726 S: 727 S: ABC-12345 728 S: 54322-XYZ 729 S: 730 S: 731 S: 733 6.2.5. EPP Command 735 This extension does not add any element to the EPP command 736 described in the EPP domain name mapping [RFC5731]. However, 737 additional elements are defined for the response in the EPP 738 object mapping. When the command has been processed successfully, 739 the EPP element shall be contained in the response if the 740 domain object has data associated with bundled names. Unless some 741 registration policy has some special processing, this EPP 742 element should contain the which contains 743 element. 745 Example response: 747 S: 748 S: 749 S: 750 S: 751 S: Command completed successfully 752 S: 753 S: 754 S: 756 S: 757 S: 758 S: xn--fsq270a.example 759 S: 760 S: 761 S: xn--fsqz41a.example 762 S: 763 S: 764 S: 765 S: 766 S: 767 S: ABC-12345 768 S: 54322-XYZ 769 S: 770 S: 771 S: 773 7. Formal Syntax 775 An EPP object name mapping extension for bundled names is specified 776 in XML Schema notation. The formal syntax presented here is a 777 complete schema representation of the object mapping suitable for 778 automated validation of EPP XML instances. The BEGIN and END tags 779 are not part of the schema; they are used to note the beginning and 780 ending of the schema for URI registration purposes. 782 BEGIN 783 785 791 794 796 797 798 Extensible Provisioning Protocol v1.0 799 Bundle Domain Extension Schema v1.0 800 801 803 806 808 812 813 814 816 817 819 823 824 825 826 827 828 830 831 832 833 834 836 837 838 839 841 842 844 845 846 847 848 849 850 852 855 857 END 859 8. Internationalization Considerations 861 EPP is represented in XML, which provides native support for encoding 862 information using the Unicode character set and its more compact 863 representations including UTF-8. Conformant XML processors recognize 864 both UTF-8 and UTF-16. Though XML includes provisions to identify 865 and use other character encodings through use of an "encoding" 866 attribute in an declaration, use of UTF-8 is recommended. 868 As an extension of the EPP domain name mapping, the elements, and 869 element content described in this document must inherit the 870 internationalization conventions used to represent higher-layer 871 domain and core protocol structures present in an XML instance that 872 includes this extension. 874 9. IANA Considerations 876 9.1. XML Namespace and XML Schema 878 This document uses URNs to describe XML namespaces and XML schemas 879 conforming to a registry mechanism described in [RFC3688]. 881 9.1.1. BDN Namespace 883 IANA is requested to make an assignment from the IETF XML Registry 884 "ns" registry as follows for the BDN namespace with this document as 885 the reference: 887 o URI: urn:ietf:params:xml:ns:epp:b-dn 889 o Registrant Contact: See the "Author's Address" section of this 890 document. 892 o XML: None. Namespace URI does not represent an XML specification. 894 9.1.2. BDN XML Schema 896 IANA is requested to make an assignment from the IETF XML Registry 897 "schema" registry as follows for the BDN XML schema with this 898 document as the reference: 900 o URI: urn:ietf:params:xml:schema:epp:b-dn 902 o Registrant Contact: See the "Author's Address" section of this 903 document. 905 o XML: See the "Formal Syntax" section of this document. 907 9.2. EPP Extension 909 The EPP extension described in this document should be registered by 910 IANA in the "Extensions for the Extensible Provisioning Protocol 911 (EPP)" registry described in [RFC7451]. The details of the 912 registration are as follows: 914 o Name of Extension: "Domain Name Mapping Extension for Strict 915 Bundling Registration" 917 o Document status: Informational 919 o Reference: This document 921 o Registrant Name and Email Address: See the "Author's Address" 922 section of this document. 924 o Top-Level Domains (TLDs): Any 926 o IPR Disclosure: https://datatracker.ietf.org/ipr/2479 928 o Status: Active 929 o Notes: None 931 10. Security Considerations 933 Normally, the EPP server will only be connected by the authorized EPP 934 client which knows whether the EPP server supports the extension 935 described in this document via out of band service. The EPP client 936 should avoid to send this extension to the unimplemented EPP server. 937 In case that a client that supports this document sends a request to 938 a server that does not support this document, the server will return 939 the result code 2103 according to the section 3 of RFC5730[RFC5730]. 940 Section 3 of RFC5730[RFC5730] has the following information for 941 result code 2103. 943 2103 "Unimplemented extension" 945 This response code must be returned when a server receives 946 a valid EPP command element that contains a protocol 947 command extension that is not implemented by the server. 949 Some registries and registrars have more than 15 years experience of 950 the bundled registration of domain names (especially Chinese domain 951 names). They have not found any significant security issues. One 952 principle that the registry and registrar should let the registrants 953 know is that bundled registered domain names will be created, 954 transferred, updated, and deleted together as a group. The 955 registrants for bundled domain names should remember this principle 956 when doing some operations to these domain names. [RFC5730] also 957 introduces some security consideration. 959 This document does not take a position regarding whether or not the 960 bundled domain names share a DS/DNSKEY key. The DNS administrator 961 can choose whether DS/DNSKEY information can be shared or not. If a 962 DS/DNSKEY key is shared, then the bundled domain names share fate if 963 there is a key compromise. 965 11. Implementation Status and some clarifications 967 Note to RFC Editor: Please remove this section before publication. 969 o The Chinese Domain Name Consortium(CDNC) including CNNIC, TWNIC, 970 HKIRC, MONIC, SGNIC and more have followed the principles defined 971 in this document for many years. 973 o CNNIC and TELEINFO have implemented this extension in their EPP 974 based Chinese domain name registration system. 976 o Public Interest Registry, has requested to implement technical 977 bundling of second level domains for .NGO and .ONG. This means 978 that by registering and purchasing a domain in the .ngo TLD, for 979 an example, the NGO registrant is also registering and purchasing 980 the corresponding name in the .ong TLD (and vice-versa for 981 registrations in .ong). 983 o Patrick Mevzek has released a new version of Net::DRI, an EPP 984 client (Perl library, free software) implementing this extension. 986 o The idea and main texts of this document has passed IETF REGEXT WG 987 review. 989 12. Acknowledgements 991 The authors especially thank the authors of [RFC5730] and [RFC5731] 992 and the following ones of CNNIC: Weiping Yang, Chao Qi. 994 Useful comments were made by John Klensin, Scott Hollenbeck, Patrick 995 Mevzek, Edward Lewis,and Adrian Farrel. 997 13. References 999 13.1. Normative References 1001 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1002 DOI 10.17487/RFC3688, January 2004, 1003 . 1005 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1006 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1007 . 1009 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1010 Domain Name Mapping", STD 69, RFC 5731, 1011 DOI 10.17487/RFC5731, August 2009, 1012 . 1014 [RFC5890] Klensin, J., "Internationalized Domain Names for 1015 Applications (IDNA): Definitions and Document Framework", 1016 RFC 5890, DOI 10.17487/RFC5890, August 2010, 1017 . 1019 [RFC5891] Klensin, J., "Internationalized Domain Names in 1020 Applications (IDNA): Protocol", RFC 5891, 1021 DOI 10.17487/RFC5891, August 2010, 1022 . 1024 [RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and 1025 Internationalized Domain Names for Applications (IDNA)", 1026 RFC 5892, DOI 10.17487/RFC5892, August 2010, 1027 . 1029 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1030 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 1031 February 2015, . 1033 [W3C.REC-xml-20040204] 1034 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 1035 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 1036 Edition)", World Wide Web Consortium FirstEdition REC-xml- 1037 20040204", February 2004, 1038 . 1040 [W3C.REC-xmlschema-1-20041028] 1041 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 1042 ""XML Schema Part 1: Structures Second Edition", World 1043 Wide Web Consortium Recommendation REC-xmlschema- 1044 1-20041028", October 2004, 1045 . 1047 [W3C.REC-xmlschema-2-20041028] 1048 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 1049 Second Edition", World Wide Web Consortium Recommendation 1050 REC-xmlschema-2-20041028", October 2004, 1051 . 1053 13.2. Informative References 1055 [RFC3743] Konishi, K., Huang, K., Qian, H., and Y. Ko, "Joint 1056 Engineering Team (JET) Guidelines for Internationalized 1057 Domain Names (IDN) Registration and Administration for 1058 Chinese, Japanese, and Korean", RFC 3743, 1059 DOI 10.17487/RFC3743, April 2004, 1060 . 1062 [RFC4290] Klensin, J., "Suggested Practices for Registration of 1063 Internationalized Domain Names (IDN)", RFC 4290, 1064 DOI 10.17487/RFC4290, December 2005, 1065 . 1067 Authors' Addresses 1068 Jiankang Yao 1069 CNNIC 1070 4 South 4th Street,Zhongguancun,Haidian District 1071 Beijing, Beijing 100190 1072 China 1074 Phone: +86 10 5881 3007 1075 Email: yaojk@cnnic.cn 1077 Linlin Zhou 1078 CNNIC 1079 4 South 4th Street,Zhongguancun,Haidian District 1080 Beijing, Beijing 100190 1081 China 1083 Phone: +86 10 5881 2677 1084 Email: zhoulinlin@cnnic.cn 1086 Hongtao Li 1087 CNNIC 1088 4 South 4th Street,Zhongguancun,Haidian District 1089 Beijing, Beijing 100190 1090 China 1092 Email: lihongtao@cnnic.cn 1094 Ning Kong 1095 Consultant 1097 Email: ietfing@gmail.com 1099 Wil Tan 1100 Cloud Registry 1101 Suite 32 Seabridge House, 377 Kent St 1102 Sydney, NSW 2000 1103 Australia 1105 Phone: +61 414 710899 1106 Email: wil@cloudregistry.net 1108 Jiagui Xie 1110 Email: jiagui1984@163.com