idnits 2.17.1 draft-ietf-regext-bundling-registration-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 24 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 14, 2018) is 2082 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC 5890' is mentioned on line 173, but not defined Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force N. Kong 3 Internet-Draft Consultant 4 Intended status: Informational J. Yao, Ed. 5 Expires: February 15, 2019 L. Zhou 6 CNNIC 7 W. Tan 8 Cloud Registry 9 J. Xie 10 August 14, 2018 12 Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for 13 Strict Bundling Registration 14 draft-ietf-regext-bundling-registration-04 16 Abstract 18 This document describes an extension of Extensible Provisioning 19 Protocol (EPP) domain name mapping for the provisioning and 20 management of strict bundling registration of domain names. 21 Specified in XML, this mapping extends the EPP domain name mapping to 22 provide additional features required for the provisioning of bundled 23 domain names. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at https://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on February 15, 2019. 42 Copyright Notice 44 Copyright (c) 2018 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (https://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 This document may contain material from IETF Documents or IETF 58 Contributions published or made publicly available before November 59 10, 2008. The person(s) controlling the copyright in some of this 60 material may not have granted the IETF Trust the right to allow 61 modifications of such material outside the IETF Standards Process. 62 Without obtaining an adequate license from the person(s) controlling 63 the copyright in such materials, this document may not be modified 64 outside the IETF Standards Process, and derivative works of it may 65 not be created outside the IETF Standards Process, except to format 66 it for publication as an RFC or to translate it into languages other 67 than English. 69 Table of Contents 71 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 72 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 74 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5 75 5. Requirement for Bundling Registration of Names . . . . . . . 5 76 6. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 6 77 6.1. RDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 78 6.2. BDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 79 7. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 80 7.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 81 7.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 82 7.1.2. EPP Command . . . . . . . . . . . . . . . . . 8 83 7.1.3. EPP Query Command . . . . . . . . . . . . 10 84 7.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 10 85 7.2.1. EPP Command . . . . . . . . . . . . . . . . 11 86 7.2.2. EPP Command . . . . . . . . . . . . . . . . 12 87 7.2.3. EPP Command . . . . . . . . . . . . . . . . . 13 88 7.2.4. EPP Command . . . . . . . . . . . . . . . 14 89 7.2.5. EPP Command . . . . . . . . . . . . . . . . 14 90 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 14 91 9. Internationalization Considerations . . . . . . . . . . . . . 16 92 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 93 11. Security Considerations . . . . . . . . . . . . . . . . . . . 17 94 12. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 95 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 96 14. Change History . . . . . . . . . . . . . . . . . . . . . . . 18 97 14.1. draft-kong-epp-bundle-mapping: Version 00 . . . . . . . 18 98 14.2. draft-kong-epp-bundle-mapping: Version 01 . . . . . . . 18 99 14.3. draft-kong-epp-bundle-mapping: Version 02 . . . . . . . 18 100 14.4. draft-ietf-regext-bundle-mapping: Version 00 . . . . . . 18 101 14.5. draft-ietf-regext-bundle-mapping: Version 01 . . . . . . 18 102 14.6. draft-ietf-regext-bundle-mapping: Version 02 . . . . . . 18 103 14.7. draft-ietf-regext-bundle-mapping: Version 03 . . . . . . 18 104 14.8. draft-ietf-regext-bundle-mapping: Version 04 . . . . . . 18 105 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 106 15.1. Normative References . . . . . . . . . . . . . . . . . . 19 107 15.2. Informative References . . . . . . . . . . . . . . . . . 20 108 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 110 1. Introduction 112 Bundled domain names are those which share the same TLD but whose 113 second level labels are variants, or those which has identical second 114 level labels for which certain parameters are shared in different 115 TLDs. For example, Public Interest Registry, request to implement 116 technical bundling of second level domains for .NGO and .ONG. So we 117 have two kinds of bundled domain names. First one is in the form of 118 "V-label.TLD" in which the second level labels (V-label) are variants 119 sharing the same TLD; Second one is in the form of "LABEL.V-tld" in 120 which the second level labels(LABEL) are same ending with the 121 different TLDs (V-tld); 123 Bundled domain names normally share some attributes. There are three 124 types of bundling. First one is strict bundling, which requires all 125 bundled names to share many same attributes. When creating, 126 updating, or transferring of any of the bundled domain names, all 127 bundled domain names will be created, updated or transferred. Second 128 one is partial bundling, which requires that at least the bundled 129 domain names if registered should be registered by the same 130 registrant. Third one is relax bundling, which has not specific 131 requirements to the domain registration. This document mainly focus 132 on strict bundling names registration. 134 For the name variants, some registries adopt the policy that variant 135 IDNs which are identified as equivalent are allocated or delegated to 136 the same registrant. For example, the specified registration policy 137 of Chinese Domain Name (CDN) is that a registrant can apply an 138 original CDN in any forms: Simplified Chinese (SC) form, Traditional 139 Chinese (TC) form, or other variant forms, then the corresponding 140 variant CDN in SC form and that in TC form will also be delegated to 141 the same registrant. All variant names in the same TLD contain same 142 attributes. 144 The basic Extensible Provisioning Protocol (EPP) domain name mapping 145 [RFC5731] provides the domain name registration one by one. It does 146 not specify how to register the strict bundled names which share many 147 same attributes. 149 In order to meet above requirements of the strict bundled names 150 registration, this document describes an extension of the EPP domain 151 name mapping [RFC5731] for the provisioning and management of bundled 152 names.This document is specified using the Extensible Markup Language 153 (XML) 1.0 as described in [W3C.REC-xml-20040204] and XML Schema 154 notation as described in [W3C.REC-xmlschema-1-20041028] and 155 [W3C.REC-xmlschema-2-20041028]. 157 The EPP core protocol specification [RFC5730] provides a complete 158 description of EPP command and response structures. A thorough 159 understanding of the base protocol specification is necessary to 160 understand the extension of mapping described in this document. 162 This document uses lots of the concepts of the IDN, so a thorough 163 understanding of the IDNs for Application (IDNA, described in 164 [RFC5890], [RFC5891], and [RFC5892]) and a thorough understanding of 165 variant approach discussed in [RFC4290] are both required. 167 2. Terminology 169 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 170 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 171 document are to be interpreted as described in [RFC2119]. 173 uLable is defined in [RFC 5890]. uLabel is expressed in this document 174 as a number of characters with the format of U+XXXX where XXXX is a 175 UNICODE point. 177 "b-dn-1.0" in this document is used as an abbreviation for 178 urn:ietf:params:xml:ns:b-dn-1.0. 180 In examples, "C:" represents lines sent by a protocol client and "S:" 181 represents lines returned by a protocol server. Indentation and 182 white space in examples are provided only to illustrate element 183 relationships and are not a REQUIRED feature of this specification. 185 XML is case sensitive. Unless stated otherwise, XML specifications 186 and examples provided in this document MUST be interpreted in the 187 character case presented to develop a conforming implementation. 189 3. Definitions 191 The following definitions are used in this document: 193 o Registered Domain Name (RDN), represents the valid domain name 194 that users submitted for registration by the first time. 196 o Bundled Domain Name (BDN), represents the bundled domain name 197 produced according to the bundled domain name registration policy. 199 4. Overview 201 Domain registries have traditionally adopted a registration model 202 whereby metadata relating to a domain name, such as its expiration 203 date and sponsoring registrar, are stored as properties of the domain 204 object. The domain object is then considered an atomic unit of 205 registration, on which operations such as update, renewal and 206 deletion may be performed. 208 Bundled names, brought about the need for multiple domain names to be 209 registered and managed as a single package. In this model, the 210 registry typically accepts a domain registration request (i.e. EPP 211 domain command) containing the domain name to be registered. 212 This domain name is referred to as the RDN in this document. As part 213 of the processing of the registration request, the registry generates 214 a set of bundled names that are related to the RDN, either 215 programmatically or with the guidance of registration policies, and 216 place them in the registration package together with the RDN. 218 The bundled names share many same properties, such as expiration date 219 and sponsoring registrar, by sharing one domain object. So when 220 users update any property of a domain object within a bundle package, 221 that property of all other domain objects in the bundle package will 222 be updated at the same time. 224 5. Requirement for Bundling Registration of Names 226 The bundled names whether they are in the form of "V-label.TLD" or in 227 the form of "LABEL.V-tld" should share some parameter or attributes 228 assoicated with domain names. Typically, Bundled names will share 229 the following parameters or attributes: 230 o Registrar Ownership 231 o Registration and Expiry Dates 232 o Registrant, Admin, Billing, and Technical Contacts 233 o Name Server Association 234 o Domain Status 235 o Applicable grace periods (Add Grace Period, Renewal Grace Period, 236 Auto-Renewal Grace Period, Transfer Grace Period, and Redemption 237 Grace Period) 239 Because the domain names are bundled and share the same parameters or 240 attributes, the EPP command should do some processing for these 241 requirements: 242 o When performing a domain check, either BDN or RDN can be queried 243 for the EPP command, and will return the same response. 244 o When performing a domain info, either BDN or RDN can be queried, 245 the same response will include both BDN and RDN information with the 246 same attributes. 247 o When performing a domain Create, either BDN or RDN will be 248 accepted. If the domain name is available, both BDN and RDN will be 249 registered. 250 o When performing a domain Delete, either BDN or RDN will be 251 accepted. If the domain name is available, both BDN and RDN will be 252 deleted. 253 o When performing a domain renew, either BDN or RDN will be accepted. 254 Upon a successful domain renewal,both BDN and RDN will have their 255 expiry date extended by the requested term. Upon a successful domain 256 renewal, both BDN and RDN will conform to the same renew grace 257 period. 258 o When performing a domain transfer, either BDN or RDN will be 259 accepted. Upon successful completion of a domain transfer request, 260 both BDN and RDN will enter a pendingTransfer status. Upon approval 261 of the transfer request, both BDN and RDN will be owned and managed 262 by the same new registrant. 263 o When performing a domain update, either BDN or RDN will be 264 accepted. Any modifications to contact associations, name server 265 associations, domain status values and authorization information will 266 be applied to both BDN and RDN. 268 6. Object Attributes 270 This extension defines following additional elements to the EPP 271 domain name mapping [RFC5731]. All of these additional elements can 272 be got from command. 274 6.1. RDN 276 The RDN is an ASCII name or an IDN with the A-label [RFC5890] form. 277 In this document, its corresponding element is . An 278 optional attribute "uLabel" associated with is used to 279 represent the U-label [RFC5890] form. An optional boolean 280 "activated" attribute, with a default true value, is used to indicate 281 the presence of the label in the zone file. 283 For example: xn-- 284 fsq270a.example 286 6.2. BDN 288 The BDN is an ASCII name or an IDN with the A-label [RFC5890] form 289 which is converted from the corresponding BDN. In this document, its 290 corresponding element is . An optional attribute "uLabel" 291 associated with is used to represent the U-label [RFC5890] 292 form. 294 For example: xn-- 295 fsqz41a.example 297 7. EPP Command Mapping 299 A detailed description of the EPP syntax and semantics can be found 300 in the EPP core protocol specification [RFC5730]. The command 301 mappings described here are specifically for use in provisioning and 302 managing bundled names via EPP. 304 7.1. EPP Query Commands 306 EPP provides three commands to retrieve domain information: 307 to determine if a domain object can be provisioned within a 308 repository, to retrieve detailed information associated with a 309 domain object, and to retrieve domain-object transfer 310 status information. 312 7.1.1. EPP Command 314 This extension does not add any element to the EPP command or 315 response described in the EPP domain name mapping [RFC5731]. 316 However, when either RDN or BDN is sent for check, response SHOULD 317 contain both RDN and BDN information, which may also give some 318 explanation in the reason field to tell the user that the associated 319 domain name is a produced name according to some bundle domain name 320 policy. 322 Example Response for an authorized client: 324 S: 325 S: 326 S: 327 S: 328 S: Command completed successfully 329 S: 330 S: 331 S: 333 S: 334 S: 335 xn--fsq270a.example 336 S: 337 S: 338 S: 339 xn--fsqz41a.example 340 S: This associated domain name is 341 a produced name 342 based on bundle name policy. 343 S: 344 S: 345 S: 346 S: 347 S: ABC-12345 348 S: 54322-XYZ 349 S: 350 S: 351 S: 353 7.1.2. EPP Command 355 This extension does not add any element to the EPP command 356 described in the EPP domain mapping [RFC5731]. However, additional 357 elements are defined for the response. 359 When an command has been processed successfully, the EPP 360 element MUST contain child elements as described in the EPP 361 domain mapping [RFC5731]. In addition, the EPP element 362 SHOULD contain a child element that identifies the 363 extension namespace if the domain object has data associated with 364 this extension and based on its service policy. The 365 element contains the which has the following child 366 elements: 368 o An element that contains the RDN, along with the 369 attributes described below. 371 o An OPTIONAL element that contains the BDN, along with 372 the attributes described below. 374 The above elements contain the following attributes: 376 o An optional "uLabel" attribute represents the U-label of the 377 element. 379 Example Response for an authorized client: 381 S: 382 S: 383 S: 384 S: 385 S: Command completed successfully 386 S: 387 S: 388 S: 390 S: xn--fsq270a.example 391 S: 58812678-domain 392 S: 393 S: 123 394 S: 123 395 S: 123 396 S: 397 S: ns1.example.cn 398 399 S: 400 S: ClientX 401 S: ClientY 402 S: 2011-04-03T22:00:00.0Z 403 404 S: 2012-04-03T22:00:00.0Z 405 406 S: 407 S: 2fooBAR 408 S: 409 S: 410 S: 411 S: 412 S: 414 S: 415 S: xn--fsq270a.example 417 S: xn--fsqz41a.example 419 S: 420 S: 421 S: 422 S: 423 S: ABC-12345 424 S: 54322-XYZ 425 S: 426 S: 427 S: 429 Response for the unauthorized client has not been changed,see 430 [RFC5731] for detail. 432 An EPP error response MUST be returned if an command cannot be 433 processed for any reason. 435 7.1.3. EPP Query Command 437 This extension does not add any element to the EPP command 438 or reponse described in the EPP domain mapping [RFC5731]. 440 7.2. EPP Transform Commands 442 EPP provides five commands to transform domain objects: to 443 create an instance of a domain object, to delete an instance 444 of a domain object, to extend the validity period of a domain 445 object, to manage domain object sponsorship changes, and 446 to change information associated with a domain object. 448 When theses commands have been processed successfully, the EPP 449 element MUST contain child elements as described in the EPP 450 domain mapping [RFC5731]. This EPP element SHOULD 451 contain the which has the following child elements: 453 o An element that contains the RDN, along with the 454 attributes described below. 456 o An OPTIONAL element that contains the BDN, along with 457 the attributes described below. 459 The above elements contain the following attribute: 461 o An optional "uLabel" attribute represents the U-label of the 462 element. 464 7.2.1. EPP Command 466 This extension defines additional elements to extend the EPP 467 command described in the EPP domain name mapping [RFC5731] for 468 bundled names registration. 470 In addition to the EPP command elements described in the EPP domain 471 mapping [RFC5731], the command SHALL contain an 472 element. The element SHOULD contain a child 473 element that identifies the bundle namespace and the 474 location of the bundle name schema. 476 Example command: 478 C: 479 C: 480 C: 481 C: 482 C: 484 C: xn--fsq270a.example 485 C: 2 486 C: 123 487 C: 123 488 C: 123 489 C: 490 C: 2fooBAR 491 C: 492 C: 493 C: 494 C: 495 C: 497 C: 498 C: xn--fsq270a.example 499 C: 500 C: 501 C: ABC-12345 502 C: 503 C: 505 When an command has been processed successfully, the EPP 506 element MUST contain child elements as described in the EPP 507 domain mapping [RFC5731]. In addition, the EPP element 508 SHOULD contain a child element that identifies the 509 extension namespace if the domain object has data associated with 510 this extension and based on its service policy. The 511 element contains the element. 513 Example Response for an authorized client: 515 S: 516 S: 517 S: 518 S: 519 S: Command completed successfully 520 S: 521 S: 522 S: 524 S: xn--fsq270a.example 525 S: 1999-04-03T22:00:00.0Z 526 S: 2001-04-03T22:00:00.0Z 527 S: 528 S: 529 S: 530 S: 532 S: 533 S: xn--fsq270a.example 535 S: xn--fsqz41a.example 537 S: 538 S: 539 S: 540 S: 541 S: ABC-12345 542 S: 54322-XYZ 543 S: 544 S: 545 S: 547 Response for the unauthorized client has not been 548 changed,see [RFC5731] for detail. 550 An EPP error response MUST be returned if an command cannot 551 be processed for any reason. 553 7.2.2. EPP Command 555 This extension does not add any element to the EPP command 556 described in the EPP domain mapping [RFC5731]. However, additional 557 elements are defined for the response. 559 When a command has been processed successfully, the EPP 560 element MUST contain child elements as described in the EPP 561 domain mapping [RFC5731]. In addition, the EPP element 562 SHOULD contain a child element that identifies the 563 extension namespace if the domain object has data associated with 564 this extension and based on its service policy. The 565 element SHOULD contain the element. 567 Example response: 569 S: 570 S: 571 S: 572 S: 573 S: Command completed successfully 574 S: 575 S: 576 S: 578 S: 579 S: xn--fsq270a.example 580 S: xn--fsqz41a.example 581 S: 582 S: 583 S: 584 S: 585 S: ABC-12345 586 S: 54321-XYZ 587 S: 588 S: 589 S: 591 An EPP error response MUST be returned if a command cannot 592 be processed for any reason. 594 7.2.3. EPP Command 596 This extension does not add any element to the EPP command 597 described in the EPP domain name mapping [RFC5731]. However, when 598 either RDN or BDN is sent for renew, response SHOULD contain both RDN 599 and BDN information. When the command has been processed 600 successfully, the EPP element MUST contain child elements 601 as described in the EPP domain mapping [RFC5731]. This EPP 602 element SHOULD contain the which contains 603 element. 605 7.2.4. EPP Command 607 This extension does not add any element to the EPP command 608 described in the EPP domain name mapping [RFC5731]. When the command 609 has been processed successfully, the EPP element MUST 610 contain child elements as described in the EPP domain mapping 611 [RFC5731]. This EPP element SHOULD contain the 612 which contains element. 614 7.2.5. EPP Command 616 This extension does not add any element to the EPP command 617 described in the EPP domain name mapping [RFC5731]. When the command 618 has been processed successfully, the EPP element MUST 619 contain child elements as described in the EPP domain mapping 620 [RFC5731]. This EPP element SHOULD contain the 621 which contains element. 623 8. Formal Syntax 625 An EPP object name mapping extension for bundled names is specified 626 in XML Schema notation. The formal syntax presented here is a 627 complete schema representation of the object mapping suitable for 628 automated validation of EPP XML instances. The BEGIN and END tags 629 are not part of the schema; they are used to note the beginning and 630 ending of the schema for URI registration purposes. 632 BEGIN 633 635 642 645 647 649 650 651 Extensible Provisioning Protocol v1.0 652 Bundle Domain Extension Schema v1.0 654 655 657 660 662 666 667 668 670 671 673 678 681 682 683 684 685 686 688 689 690 691 692 694 698 699 700 701 704 705 707 708 709 710 712 713 714 716 719 721 END 723 9. Internationalization Considerations 725 EPP is represented in XML, which provides native support for encoding 726 information using the Unicode character set and its more compact 727 representations including UTF-8. Conformant XML processors recognize 728 both UTF-8 and UTF-16. Though XML includes provisions to identify 729 and use other character encodings through use of an "encoding" 730 attribute in an declaration, use of UTF-8 is RECOMMENDED. 732 As an extension of the EPP domain name mapping, the elements, element 733 content described in this document MUST inherit the 734 internationalization conventions used to represent higher-layer 735 domain and core protocol structures present in an XML instance that 736 includes this extension. 738 10. IANA Considerations 740 This document uses URNs to describe XML namespaces and XML schemas 741 conforming to a registry mechanism described in [RFC3688]. IANA is 742 requested to assignment the following two URIs. 744 Registration request for the IDN namespace: 746 o URI: urn:ietf:params:xml:ns:b-dn-1.0 747 o Registrant Contact: See the "Author's Address" section of this 748 document. 750 o XML: None. Namespace URI does not represent an XML specification. 752 Registration request for the IDN XML schema: 754 o URI: urn:ietf:params:xml:schema:b-dn-1.0 756 o Registrant Contact: See the "Author's Address" section of this 757 document. 759 o XML: See the "Formal Syntax" section of this document. 761 11. Security Considerations 763 The object mapping extension described in this document does not 764 provide any other security services or introduce any additional 765 considerations beyond those described by [RFC5730] or those caused by 766 the protocol layers used by EPP. 768 12. Implementation Status 770 Note to RFC Editor: Please remove this section before publication. 772 o The Chinese Domain Name Consortium(CDNC) including CNNIC, TWNIC, 773 HKIRC, MONIC, SGNIC and more have followed the principles defined 774 in this document for many years. 776 o CNNIC and TELEINFO have implemented this extension in their EPP 777 based Chinese domain name registration system. 779 o Public Interest Registry, has requested to implement technical 780 bundling of second level domains for .NGO and .ONG. This means 781 that by registering and purchasing a domain in the .ngo TLD, for 782 example, the NGO registrant is also registering and purchasing the 783 corresponding name in the .ong TLD (and vice-versa for 784 registrations in .ong). 786 o Patrick Mevzek has released a new version of Net::DRI, an EPP 787 client (Perl library, free software) implementing this extension. 789 13. Acknowledgements 791 The authors especially thank the authors of [RFC5730] and [RFC5731] 792 and the following ones of CNNIC: Weiping Yang, Chao Qi. This draft 793 extends the draft draft-kong-epp-idn-variants-mapping to support both 794 forms of bundled names: V-label.TLD and LABEL.V-tld. 796 Useful comments were made by John Klensin, Scott Hollenbeck, Patrick 797 Mevzek and Edward Lewis. 799 14. Change History 801 RFC Editor: Please remove this section. 803 14.1. draft-kong-epp-bundle-mapping: Version 00 805 o EPP extensiton for bundled domain name registrations. 807 14.2. draft-kong-epp-bundle-mapping: Version 01 809 o Change the proposed category from EXP to STD. 811 o Add the section of Implementation Status. 813 o Refine the text, and update the examples. 815 14.3. draft-kong-epp-bundle-mapping: Version 02 817 o Refine the texts. 819 14.4. draft-ietf-regext-bundle-mapping: Version 00 821 o accepted as WG document. 823 14.5. draft-ietf-regext-bundle-mapping: Version 01 825 o make this document to focus on the restrict bundled domain name 826 registration. 828 14.6. draft-ietf-regext-bundle-mapping: Version 02 830 o Update the section of implementation status. 832 14.7. draft-ietf-regext-bundle-mapping: Version 03 834 o This document is changed to informational category. 836 o Refine the text. 838 14.8. draft-ietf-regext-bundle-mapping: Version 04 840 o Update the implementation section. 842 o Refine the text. 844 15. References 846 15.1. Normative References 848 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 849 Requirement Levels", BCP 14, RFC 2119, 850 DOI 10.17487/RFC2119, March 1997, 851 . 853 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 854 DOI 10.17487/RFC3688, January 2004, 855 . 857 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 858 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 859 . 861 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 862 Domain Name Mapping", STD 69, RFC 5731, 863 DOI 10.17487/RFC5731, August 2009, 864 . 866 [RFC5890] Klensin, J., "Internationalized Domain Names for 867 Applications (IDNA): Definitions and Document Framework", 868 RFC 5890, DOI 10.17487/RFC5890, August 2010, 869 . 871 [RFC5891] Klensin, J., "Internationalized Domain Names in 872 Applications (IDNA): Protocol", RFC 5891, 873 DOI 10.17487/RFC5891, August 2010, 874 . 876 [RFC5892] Faltstrom, P., Ed., "The Unicode Code Points and 877 Internationalized Domain Names for Applications (IDNA)", 878 RFC 5892, DOI 10.17487/RFC5892, August 2010, 879 . 881 [W3C.REC-xml-20040204] 882 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 883 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 884 Edition)", World Wide Web Consortium FirstEdition REC-xml- 885 20040204", February 2004, 886 . 888 [W3C.REC-xmlschema-1-20041028] 889 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 890 ""XML Schema Part 1: Structures Second Edition", World 891 Wide Web Consortium Recommendation REC-xmlschema- 892 1-20041028", October 2004, 893 . 895 [W3C.REC-xmlschema-2-20041028] 896 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 897 Second Edition", World Wide Web Consortium Recommendation 898 REC-xmlschema-2-20041028", October 2004, 899 . 901 15.2. Informative References 903 [bundle.name] 904 ICANN, "Registry Services Technical Evaluation Panel 905 (RSTEP) Report on Public Interest Registry's Request to 906 Implement Technical Bundling in .NGO and .ONG", July 2014, 907 . 910 [Final.Integrated.Issues.Report] 911 ICANN, "The IDN Variant Issues Project: A Study of Issues 912 Related to the Management of IDN Variant TLDs", February 913 2012, . 916 [RFC4290] Klensin, J., "Suggested Practices for Registration of 917 Internationalized Domain Names (IDN)", RFC 4290, 918 DOI 10.17487/RFC4290, December 2005, 919 . 921 Authors' Addresses 923 Ning Kong 924 Consultant 926 Email: ietfing@gmail.com 927 Jiankang Yao (editor) 928 CNNIC 929 4 South 4th Street,Zhongguancun,Haidian District 930 Beijing, Beijing 100190 931 China 933 Phone: +86 10 5881 3007 934 Email: yaojk@cnnic.cn 936 Linlin Zhou 937 CNNIC 938 4 South 4th Street,Zhongguancun,Haidian District 939 Beijing, Beijing 100190 940 China 942 Phone: +86 10 5881 2677 943 Email: zhoulinlin@cnnic.cn 945 Wil Tan 946 Cloud Registry 947 Suite 32 Seabridge House, 377 Kent St 948 Sydney, NSW 2000 949 Australia 951 Phone: +61 414 710899 952 Email: wil@cloudregistry.net 954 Jiagui Xie 956 Email: jiagui1984@163.com