idnits 2.17.1 draft-zhou-eppext-reseller-02.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 14 instances of too long lines in the document, the longest one being 16 characters in excess of 72. ** The abstract seems to contain references ([RFC5731]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 (October 12, 2015) is 3091 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) ** Downref: Normative reference to an Informational RFC: RFC 7451 Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force L. Zhou 3 Internet-Draft N. Kong 4 Intended status: Standards Track CNNIC 5 Expires: April 14, 2016 C. Qi 6 Teleinfo 7 X. Lee 8 CNNIC 9 J. Gould 10 VeriSign, Inc. 11 October 12, 2015 13 Reseller Extension for the Extensible Provisioning Protocol (EPP) 14 draft-zhou-eppext-reseller-02 16 Abstract 18 This mapping, an extension to EPP object mappings like the EPP domain 19 name mapping [RFC5731], to support assigning a reseller to any 20 existing object (domain, host, contact) as well as any future 21 objects. Specified in Extensible Markup Language (XML), this 22 extended mapping is applied to provide additional features required 23 for the provisioning of resellers. 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 http://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 April 14, 2016. 42 Copyright Notice 44 Copyright (c) 2015 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 (http://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. Conventions Used in This Document . . . . . . . . . . . . . . 3 73 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 74 3.1. Reseller Identifier . . . . . . . . . . . . . . . . . . . 4 75 3.2. Reseller Name . . . . . . . . . . . . . . . . . . . . . . 4 76 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 77 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4 78 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 79 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 4 80 4.1.3. EPP Command . . . . . . . . . . . . . . . 7 81 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 7 82 4.2.1. EPP Command . . . . . . . . . . . . . . . . 7 83 4.2.2. EPP Command . . . . . . . . . . . . . . . . 8 84 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 8 85 4.2.4. EPP Command . . . . . . . . . . . . . . . 9 86 4.2.5. EPP Command . . . . . . . . . . . . . . . . 9 87 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 11 88 6. Internationalization Considerations . . . . . . . . . . . . . 13 89 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 90 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 13 91 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 14 92 8. Security Considerations . . . . . . . . . . . . . . . . . . . 14 93 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 94 9.1. Normative References . . . . . . . . . . . . . . . . . . 14 95 9.2. Informative References . . . . . . . . . . . . . . . . . 16 96 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 99 1. Introduction 101 Domain resellers are the individuals or companies act as agents for 102 ICANN accredited registrars. A domain name registrar may have 103 several resellers to help them sell domain names to end users. 105 Generally speaking, resellers provide domain registration information 106 via registrar's EPP client without reseller information. On one 107 hand, registrars are concerned about how to identify resellers. On 108 the other hand, end users would also be confused by the WHOIS service 109 without corresponding reseller information. This requirement imposes 110 a challenge for the domain registries since there is no definition of 111 resellers in the existing EPP domain name mapping. Out of band 112 method could solve this problem but may increase extra cost. 114 In order to facilitate provisioning and management of reseller 115 information in a shared central repository, this document proposes a 116 reseller extension of [RFC5731], [RFC5732] and [RFC5733]. The 117 examples provided in this document are used for the domain object for 118 illustration purposes. The host and contact object could be extended 119 in the same way with the domain object. 121 A reseller mapping object defined in 122 [ID.draft-zhou-eppext-reseller-mapping] SHOULD be created first. The 123 reseller information specified in this document SHOULD reference the 124 existing reseller identifier and reseller name. 126 This document is specified using the XML 1.0 as described in 127 [W3C.REC-xml-20040204] and XML Schema notation as described in 128 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. 130 2. Conventions Used in This Document 132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 134 document are to be interpreted as described in [RFC2119]. 136 In examples, "C:" represents lines sent by a protocol client and "S:" 137 represents lines returned by a protocol server. Indentation and 138 white space in examples are provided only to illustrate element 139 relationships and are not a REQUIRED feature of this specification. 141 XML is case sensitive. Unless stated otherwise, XML specifications 142 and examples provided in this document MUST be interpreted in the 143 character case presented to develop a conforming implementation. 145 resellerext-1.0 in this document is used as an abbreviation for 146 urn:ietf:params:xml:ns:resellerext-1.0. 148 3. Object Attributes 150 This extension adds additional elements to the EPP domain name 151 mapping [RFC5731]. Only the new elements are described here. 153 3.1. Reseller Identifier 155 Reseller identifier provides the ID of the reseller of a sponsoring 156 registrar. Its corresponding element is which 157 refers to the element defined in 158 [ID.draft-zhou-eppext-reseller-mapping]. 160 3.2. Reseller Name 162 Reseller name provides the name of the reseller of a sponsoring 163 registrar. Its corresponding element is which 164 refers to the element defined in 165 [ID.draft-zhou-eppext-reseller-mapping]. 167 4. EPP Command Mapping 169 A detailed description of the EPP syntax and semantics can be found 170 in the EPP core protocol specification [RFC5730]. The command 171 mappings described here are specifically for use in provisioning and 172 managing reseller information via EPP. 174 4.1. EPP Query Commands 176 EPP provides three commands to retrieve domain information: 177 to determine if a domain object can be provisioned within a 178 repository, to retrieve detailed information associated with a 179 domain object, and to retrieve domain-object transfer 180 status information. 182 4.1.1. EPP Command 184 This extension does not add any elements to the EPP command 185 or response described in the EPP domain name mapping 186 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733]. 188 4.1.2. EPP Command 190 This extension does not add any element to the EPP command 191 described in the EPP domain mapping [RFC5731], host mapping [RFC5732] 192 and contact mapping [RFC5733]. However, additional elements are 193 defined for the response. 195 Example command: 197 C: 198 C: 199 C: 200 C: 201 C: 202 C: example.com 203 C: 204 C: fooBAR 205 C: 206 C: 207 C: 208 C: ngcl-mIFICBNP 209 C: 210 C: 212 When an command has been processed successfully, the EPP 213 element MUST contain child elements as described in the EPP 214 domain mapping [RFC5731], host mapping [RFC5732] and contact mapping 215 [RFC5733]. In addition, the EPP element SHOULD contain a 216 child element that identifies the extension 217 namespace if the domain object has data associated with this 218 extension and based on its service policy. The 219 element contains the following child elements: 221 o A element that contains the identifier of the 222 reseller of a sponsoring registrar. 224 o An OPTIONAL element that contains the name of 225 the reseller of a sponsoring registrar. 227 Example response for an authorized client: 229 S: 230 S: 231 S: 232 S: 233 S: Command completed successfully 234 S: 235 S: 236 S: 237 S: example.com 238 S: EXAMPLE1-REP 239 S: 240 S: jd1234 241 S: sh8013 242 S: sh8013 243 S: sh8013 244 S: 245 S: ns1.example.com 246 S: 247 S: ClientX 248 S: ClientY 249 S: 2015-02-06T04:01:21.0Z 250 S: 2018-02-06T04:01:21.0Z 251 S: 252 S: 2fooBAR 253 S: 254 S: 255 S: 256 S: 257 S: 258 S: 259 S: 260 S: 261 S: myreseller 262 S: example 263 S: 264 S: 265 S: 266 S: ngcl-IvJjzMZc 267 S: test142AWQONJZ 268 S: 269 S: 270 S: 272 response for the unauthorized client has not been changed, see 273 [RFC5731], [RFC5732] and [RFC5733]for detail. 275 An EPP error response MUST be returned if an command cannot be 276 processed for any reason. 278 4.1.3. EPP Command 280 This extension does not add any elements to the EPP 281 command or response described in the EPP domain name 282 mapping [RFC5731], host mapping [RFC5732] and contact mapping 283 [RFC5733]. 285 4.2. EPP Transform Commands 287 EPP provides five commands to transform domain objects: to 288 create an instance of a domain object, to delete an instance 289 of a domain object, to extend the validity period of a domain 290 object, to manage domain object sponsorship changes, and 291 to change information associated with a domain object. 293 4.2.1. EPP Command 295 This extension defines additional elements for the EPP 296 command described in the EPP domain mapping [RFC5731], host mapping 297 [RFC5732] and contact mapping [RFC5733]. No additional elements are 298 defined for the EPP response. 300 The EPP command provides a transform operation that allows a 301 client to create a domain object. In addition to the EPP command 302 elements described in the EPP domain mapping [RFC5731], host mapping 303 [RFC5732] and contact mapping [RFC5733], the command MUST contain an 304 element, and the element MUST contain a child 305 element that identifies the extension namespace 306 if the client wants to associate data defined in this extension to 307 the domain object. The element contains the 308 following child elements: 310 o A element that contains the identifier of the 311 reseller of a sponsoring registrar. 313 Example Command: 315 C: 316 C: 317 C: 318 C: 319 C: 320 C: example.com 321 C: 3 322 C: 323 C: ns1.example.com 324 C: 325 C: jd1234 326 C: sh8013 327 C: sh8013 328 C: sh8013 329 C: 330 C: fooBAR 331 C: 332 C: 333 C: 334 C: 335 C: 336 C: myreseller 337 C: 338 C: 339 C: ABC-12345 340 C: 341 C: 343 When a command has been processed successfully, the EPP 344 response is as described in the EPP domain mapping [RFC5731], host 345 mapping [RFC5732] and contact mapping [RFC5733]. 347 An EPP error response MUST be returned if a command cannot 348 be processed for any reason. 350 4.2.2. EPP Command 352 This extension does not add any elements to the EPP command 353 or response described in the EPP domain mapping [RFC5731], 354 host mapping [RFC5732] and contact mapping [RFC5733]. 356 4.2.3. EPP Command 358 This extension does not add any elements to the EPP command 359 or response described in the EPP domain mapping [RFC5731], 360 host mapping [RFC5732] and contact mapping [RFC5733]. 362 4.2.4. EPP Command 364 This extension does not add any elements to the EPP 365 command or response described in the EPP domain mapping 366 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733], but 367 after a successful transfer of an object with an assigned reseller, 368 the server SHOULD clear the assigned reseller value. 370 4.2.5. EPP Command 372 This extension defines additional elements for the EPP 373 command described in the EPP domain mapping [RFC5731], host mapping 374 [RFC5732] and contact mapping [RFC5733]. No additional elements are 375 defined for the EPP response. 377 The EPP command provides a transform operation that allows a 378 client to modify the attributes of a domain object. In addition to 379 the EPP command elements described in the EPP domain mapping, the 380 command MUST contain an element, and the 381 element MUST contain a child element that 382 identifies the extension namespace if the client wants to update the 383 domain object with data defined in this extension. The 384 element contains the following child elements: 386 o An OPTIONAL element that contains attribute 387 values to be added to the object. 389 o An OPTIONAL element that contains attribute 390 values to be removed from the object. 392 o An OPTIONAL element that contains attribute 393 values to be changed. 395 At least one and only one , or 396 element MUST be provided. The , 397 and elements contain the 398 following child element: 400 o A element that contains the identifier of the 401 reseller of a sponsoring registrar. 403 Example command, adding a reseller: 405 C: 406 C: 407 C: 408 C: 409 C: 410 C: example.com 411 C: 412 C: 413 C: 414 C: 415 C: 416 C: myreseller 417 C: 418 C: 419 C: 420 C: ABC-12345 421 C: 422 C: 424 Example command, removing a reseller: 426 C: 427 C: 428 C: 429 C: 430 C: 431 C: example.com 432 C: 433 C: 434 C: 435 C: 436 C: 437 C: myreseller 438 C: 439 C: 440 C: 441 C: ABC-12345 442 C: 443 C: 445 Example command, updating reseller identifier: 447 C: 448 C: 449 C: 450 C: 451 C: 452 C: example.com 453 C: 454 C: 455 C: 456 C: 457 C: 458 C: myreseller 459 C: 460 C: 461 C: 462 C: ABC-12345 463 C: 464 C: 466 When an extended command has been processed successfully, 467 the EPP response is as described in the EPP domain name mapping 468 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733]. 470 5. Formal Syntax 472 An EPP object mapping is specified in XML Schema notation. The 473 formal syntax presented here is a complete schema representation of 474 the object mapping suitable for automated validation of EPP XML 475 instances. The BEGIN and END tags are not part of the schema; they 476 are used to note the beginning and ending of the schema for URI 477 registration purposes. 479 BEGIN 480 482 489 492 494 497 498 499 Extensible Provisioning Protocol v1.0 500 Domain Reseller Extension Schema v1.0 501 502 504 505 506 508 509 510 511 512 513 514 516 519 520 521 522 523 524 526 530 531 532 533 534 535 536 538 539 540 541 542 543 545 547 549 551 552 553 554 555 556 557 558 560 561 562 END 564 6. Internationalization Considerations 566 EPP is represented in XML, which provides native support for encoding 567 information using the Unicode character set and its more compact 568 representations including UTF-8. Conformant XML processors recognize 569 both UTF-8 and UTF-16. Though XML includes provisions to identify 570 and use other character encodings through use of an "encoding" 571 attribute in an declaration, use of UTF-8 is RECOMMENDED. 573 As an extension of the EPP domain name mapping, the elements, element 574 content described in this document MUST inherit the 575 internationalization conventions used to represent higher-layer 576 domain and core protocol structures present in an XML instance that 577 includes this extension. 579 7. IANA Considerations 581 7.1. XML Namespace 583 This document uses URNs to describe XML namespaces and XML schemas 584 conforming to a registry mechanism described in [RFC3688]. IANA is 585 requested to assignment the following URI. 587 Registration request for the reseller namespace: 589 o URI: urn:ietf:params:xml:ns:reseller-1.0 591 o Registrant Contact: See the "Author's Address" section of this 592 document. 594 o XML: See the "Formal Syntax" section of this document. 596 7.2. EPP Extension Registry 598 The EPP extension described in this document should be registered by 599 the IANA in the EPP Extension Registry described in [RFC7451]. The 600 details of the registration are as follows: 602 Name of Extension: Domain Reseller Extension 604 Document status: Standards Track 606 Reference: (insert reference to RFC version of this document) 608 Registrant Name and Email Address: See the "Author's Address" section 609 of this document. 611 TLDs: any 613 IPR Disclosure: none 615 Status: active 617 Notes: none 619 8. Security Considerations 621 The object mapping extension described in this document does not 622 provide any other security services or introduce any additional 623 considerations beyond those described by [RFC5730], [RFC5731], 624 [RFC5732] and [RFC5733] or those caused by the protocol layers used 625 by EPP. 627 9. References 629 9.1. Normative References 631 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 632 Requirement Levels", BCP 14, RFC 2119, 633 DOI 10.17487/RFC2119, March 1997, 634 . 636 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 637 DOI 10.17487/RFC3688, January 2004, 638 . 640 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 641 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 642 . 644 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 645 Domain Name Mapping", STD 69, RFC 5731, 646 DOI 10.17487/RFC5731, August 2009, 647 . 649 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 650 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 651 August 2009, . 653 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 654 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 655 August 2009, . 657 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 658 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 659 February 2015, . 661 [W3C.REC-xml-20040204] 662 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 663 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 664 Edition)", World Wide Web Consortium FirstEdition REC-xml- 665 20040204", February 2004, 666 . 668 [W3C.REC-xmlschema-1-20041028] 669 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 670 ""XML Schema Part 1: Structures Second Edition", World 671 Wide Web Consortium Recommendation REC-xmlschema- 672 1-20041028", October 2004, 673 . 675 [W3C.REC-xmlschema-2-20041028] 676 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 677 Second Edition", World Wide Web Consortium Recommendation 678 REC-xmlschema-2-20041028", October 2004, 679 . 681 9.2. Informative References 683 [ID.draft-zhou-eppext-reseller-mapping] 684 Zhou, L., Kong, N., Qi, C., Lee, X., and J. Gould, 685 "Extensible Provisioning Protocol (EPP) Reseller Mapping", 686 Oct 2015, . 689 Appendix A. Change Log 691 Initial -00: Individual document submitted. 693 -01: 695 * Updated abstract and introduction. 697 * Revised typos in info response. 699 * Added explanations on how to process reseller extension after 700 successful transfer operation. 702 * Modified explanation. 704 * Deleted reseller name element in and 705 commands. 707 * Removed some inaccurate comments from xml schema. 709 * Modified the element name of reseller id and reseller name. 711 -02: 713 * Changed author information. 715 * Updated xml typos to 716 in response. 718 Authors' Addresses 720 Linlin Zhou 721 CNNIC 722 4 South 4th Street, Zhongguancun, Haidian District 723 Beijing, Beijing 100190 724 China 726 Phone: +86 10 5881 2677 727 Email: zhoulinlin@cnnic.cn 728 Ning Kong 729 CNNIC 730 4 South 4th Street, Zhongguancun, Haidian District 731 Beijing, Beijing 100190 732 China 734 Phone: +86 10 5881 3147 735 Email: nkong@cnnic.cn 737 Chao Qi 738 Teleinfo 740 Email: qichao911@163.com 742 Xiaodong Lee 743 CNNIC 744 4 South 4th Street, Zhongguancun, Haidian District 745 Beijing, Beijing 100190 746 China 748 Phone: +86 10 5881 3020 749 Email: xl@cnnic.cn 751 James Gould 752 VeriSign, Inc. 753 12061 Bluemont Way 754 Reston, VA 20190 755 US 757 Email: jgould@verisign.com