idnits 2.17.1 draft-ietf-regext-org-ext-05.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 : ---------------------------------------------------------------------------- ** 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 (May 7, 2018) is 2173 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) No issues found here. Summary: 1 error (**), 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 J. Wei 5 Expires: November 8, 2018 X. Lee 6 CNNIC 7 J. Gould 8 Verisign, Inc. 9 May 7, 2018 11 Organization Extension for the Extensible Provisioning Protocol (EPP) 12 draft-ietf-regext-org-ext-05 14 Abstract 16 This mapping, an extension to EPP object mappings like the EPP domain 17 name mapping [RFC5731], to support assigning an organization to any 18 existing object (domain, host, contact) as well as any future 19 objects. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on November 8, 2018. 38 Copyright Notice 40 Copyright (c) 2018 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 This document may contain material from IETF Documents or IETF 54 Contributions published or made publicly available before November 55 10, 2008. The person(s) controlling the copyright in some of this 56 material may not have granted the IETF Trust the right to allow 57 modifications of such material outside the IETF Standards Process. 58 Without obtaining an adequate license from the person(s) controlling 59 the copyright in such materials, this document may not be modified 60 outside the IETF Standards Process, and derivative works of it may 61 not be created outside the IETF Standards Process, except to format 62 it for publication as an RFC or to translate it into languages other 63 than English. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 69 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 70 3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4 71 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 72 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4 73 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 74 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 4 75 4.1.3. EPP Command . . . . . . . . . . . . . . . 7 76 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 77 4.2.1. EPP Command . . . . . . . . . . . . . . . . 8 78 4.2.2. EPP Command . . . . . . . . . . . . . . . . 10 79 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 10 80 4.2.4. EPP Command . . . . . . . . . . . . . . . 11 81 4.2.5. EPP Command . . . . . . . . . . . . . . . . 11 82 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15 83 6. Internationalization Considerations . . . . . . . . . . . . . 17 84 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 85 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 86 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 87 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 88 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19 89 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19 90 9. Security Considerations . . . . . . . . . . . . . . . . . . . 19 91 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20 92 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 93 11.1. Normative References . . . . . . . . . . . . . . . . . . 20 94 11.2. Informative References . . . . . . . . . . . . . . . . . 21 95 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21 96 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 98 1. Introduction 100 In the business model of domain registration, we usually have 3 roles 101 of entities, a registrant, a registrar and a registry. There may 102 have some other roles of entities involved in the domain registration 103 process which are not formally defined, such as resellers, DNS 104 service operators, privacy proxy, etc. 106 A domain reseller is an individual or a company that acts as a agent 107 for accredited registrars. A third-party DNS service operator is 108 responsible for a zone where the operator is neither the registrant 109 nor the registrar of records for the delegation. And a privacy proxy 110 is an entity that provides with individuals or organizations domain 111 registration without exposing their private information. These kind 112 of entities are defined as "organizations" with different role types 113 in this document. 115 In order to facilitate provisioning and management of organization 116 information in a shared central repository, this document proposes an 117 organization extension mapping for any EPP object like domain names 118 in [RFC5731], hosts in [RFC5732] and contacts in [RFC5733]. The 119 examples provided in this document are used for the domain object for 120 illustration purpose. The host and contact object could be extended 121 in the same way with the domain object. 123 An organization mapping object defined in [ID.draft-ietf-regext-org] 124 SHOULD be created first. The organization information specified in 125 this document MUST reference the existing organization identifier. 127 This document is specified using the XML 1.0 as described in 128 [W3C.REC-xml-20040204] and XML Schema notation as described in 129 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. 131 2. Conventions Used in This Document 133 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 134 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 135 document are to be interpreted as described in [RFC2119]. 137 In examples, "C:" represents lines sent by a protocol client and "S:" 138 represents lines returned by a protocol server. Indentation and 139 white space in examples are provided only to illustrate element 140 relationships and are not a REQUIRED feature of this specification. 142 XML is case sensitive. Unless stated otherwise, XML specifications 143 and examples provided in this document MUST be interpreted in the 144 character case presented to develop a conforming implementation. 146 orgext-1.0 in this document is used as an abbreviation for 147 urn:ietf:params:xml:ns:orgext-1.0. 149 3. Object Attributes 151 This extension adds additional elements to EPP object mappings like 152 the EPP domain name mapping [RFC5731]. Only the new elements are 153 described here. 155 3.1. Organization Identifier 157 Organization identifier provides the ID of an organization. Its 158 corresponding element is which refers to the 159 element defined in [ID.draft-ietf-regext-org]. All 160 organization objects are identified by a server-unique identifier. 162 4. EPP Command Mapping 164 A detailed description of the EPP syntax and semantics can be found 165 in the EPP core protocol specification [RFC5730]. The command 166 mappings described here are specifically for use in provisioning and 167 managing organization information via EPP. 169 4.1. EPP Query Commands 171 EPP provides three commands to retrieve domain information: 172 to determine if a domain object can be provisioned within a 173 repository, to retrieve detailed information associated with a 174 domain object, and to retrieve domain-object transfer 175 status information. 177 4.1.1. EPP Command 179 This extension does not add any elements to the EPP command 180 or response described in the EPP domain name mapping 181 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733]. 183 4.1.2. EPP Command 185 This extension does not add any element to the EPP command 186 described in the EPP domain mapping [RFC5731], host mapping [RFC5732] 187 and contact mapping [RFC5733]. However, additional elements are 188 defined for the response in the EPP domain mapping [RFC5731], 189 host mapping [RFC5732] and contact mapping [RFC5733]. 191 When an command has been processed successfully, the EPP 192 element MUST contain child elements as described in the EPP 193 object extensions. In addition, the EPP element SHOULD 194 contain a child element that identifies the 195 extension namespace if the object has data associated with this 196 extension and based on server policy. The element 197 contains the following child elements: 199 o Zero or more elements are allowed that contains the 200 identifier of the organization. The "role" attribute is used to 201 represent the relationship that the organization has to the 202 object. See Section 7.3 in [ID.draft-ietf-regext-org] for a list 203 of values. 205 Example response for an authorized client with multiple 206 organizations: 208 S: 209 S: 210 S: 211 S: 212 S: Command completed successfully 213 S: 214 S: 215 S: 217 S: example.com 218 S: EXAMPLE1-REP 219 S: 220 S: jd1234 221 S: sh8013 222 S: sh8013 223 S: sh8013 224 S: 225 S: ns1.example.com 226 S: 227 S: ClientX 228 S: ClientY 229 S: 2015-02-06T04:01:21.0Z 230 S: 2018-02-06T04:01:21.0Z 231 S: 232 S: 2fooBAR 233 S: 234 S: 235 S: 236 S: 237 S: 239 S: myreseller 240 S: myproxy 241 S: 242 S: 243 S: 244 S: ngcl-IvJjzMZc 245 S: test142AWQONJZ 246 S: 247 S: 248 S: 250 Example response for an authorized client with no 251 organization: 253 S: 254 S: 255 S: 256 S: 257 S: Command completed successfully 258 S: 259 S: 260 S: 262 S: example.com 263 S: EXAMPLE1-REP 264 S: 265 S: jd1234 266 S: sh8013 267 S: sh8013 268 S: sh8013 269 S: 270 S: ns1.example.com 271 S: 272 S: ClientX 273 S: ClientY 274 S: 2015-02-06T04:01:21.0Z 275 S: 2018-02-06T04:01:21.0Z 276 S: 277 S: 2fooBAR 278 S: 279 S: 280 S: 281 S: 282 S: 284 S: 285 S: 286 S: ngcl-IvJjzMZc 287 S: test142AWQONJZ 288 S: 289 S: 290 S: 292 An EPP error response MUST be returned if an command cannot be 293 processed for any reason. 295 4.1.3. EPP Command 297 This extension does not add any elements to the EPP 298 command or response described in the EPP domain name 299 mapping [RFC5731], host mapping [RFC5732] and contact mapping 300 [RFC5733]. 302 4.2. EPP Transform Commands 304 EPP provides five commands to transform domain objects: to 305 create an instance of a domain object, to delete an instance 306 of a domain object, to extend the validity period of a domain 307 object, to manage domain object sponsorship changes, and 308 to change information associated with a domain object. 310 4.2.1. EPP Command 312 This extension defines additional elements for the EPP 313 command described in the EPP object extensions. No additional 314 elements are defined for the EPP response. 316 The EPP command provides a transform operation that allows a 317 client to create an object. In addition to the EPP command elements 318 described in the EPP object extensions, the command MUST contain an 319 element, and the element MUST contain a child 320 element that identifies the extension namespace if 321 the client wants to associate data defined in this extension to the 322 object. The element contains the following child 323 elements: 325 o One or more elements that contains the identifier of 326 the organization. The "role" attribute is used to represent the 327 relationship that the organization has to the object. See 328 Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. 330 Example Command with only one organization: 332 C: 333 C: 334 C: 335 C: 336 C: 338 C: example.com 339 C: 3 340 C: 341 C: ns1.example.com 342 C: 343 C: jd1234 344 C: sh8013 345 C: sh8013 346 C: sh8013 347 C: 348 C: fooBAR 349 C: 350 C: 351 C: 352 C: 353 C: 355 C: myreseller 356 C: 357 C: 358 C: ABC-12345 359 C: 360 C: 362 Example Command with multiple organizations: 364 C: 365 C: 366 C: 367 C: 368 C: 370 C: example.com 371 C: 3 372 C: 373 C: ns1.example.com 374 C: 375 C: jd1234 376 C: sh8013 377 C: sh8013 378 C: sh8013 379 C: 380 C: fooBAR 381 C: 382 C: 383 C: 384 C: 385 C: 387 C: myreseller 388 C: myproxy 389 C: 390 C: 391 C: ABC-12345 392 C: 393 C: 395 When a command has been processed successfully, the EPP 396 response is as described in the EPP object extension. 398 An EPP error response MUST be returned if a command cannot 399 be processed for any reason. 401 4.2.2. EPP Command 403 This extension does not add any elements to the EPP command 404 or response described in the EPP domain mapping [RFC5731], 405 host mapping [RFC5732] and contact mapping [RFC5733]. 407 4.2.3. EPP Command 409 This extension does not add any elements to the EPP command 410 or response described in the EPP domain mapping [RFC5731], 411 host mapping [RFC5732] and contact mapping [RFC5733]. 413 4.2.4. EPP Command 415 This extension does not add any elements to the EPP 416 command or response described in the EPP domain mapping 417 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733], but 418 after a successful transfer of an object with an assigned 419 organization, the handling of the assigned organization is dependent 420 on the organization roles and server policy. 422 4.2.5. EPP Command 424 This extension defines additional elements for the EPP 425 command described in the EPP domain mapping [RFC5731], host mapping 426 [RFC5732] and contact mapping [RFC5733]. No additional elements are 427 defined for the EPP response. 429 The EPP command provides a transform operation that allows a 430 client to modify the attribute of an object. In addition to the EPP 431 command elements, the command MUST contain an 432 element, and the element MUST contain a child 433 element that identifies the extension namespace if 434 the client wants to update the object with data defined in this 435 extension. The element contains the following child 436 elements: 438 o An OPTIONAL element that contains attribute values to 439 be added to the object. 441 o An OPTIONAL element that contains attribute values to 442 be removed from the object. 444 o An OPTIONAL element that contains attribute values to 445 be changed. 447 At least one and only one , or 448 element MUST be provided. The , and 449 elements contain the following child element: 451 o One or more elements that contains the identifier of 452 the organization. The "role" attribute is used to represent the 453 relationship that the organization has to the object. See 454 Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. 456 Example command, adding a reseller: 458 C: 459 C: 460 C: 461 C: 462 C: 464 C: example.com 465 C: 466 C: 467 C: 468 C: 470 C: 471 C: myreseller 472 C: 473 C: 474 C: 475 C: ABC-12345 476 C: 477 C: 479 Example command, adding multiple organizations: 481 C: 482 C: 483 C: 484 C: 485 C: 487 C: example.com 488 C: 489 C: 490 C: 491 C: 493 C: 494 C: myreseller 495 C: myproxy 496 C: 497 C: 498 C: 499 C: ABC-12345 500 C: 501 C: 503 Example command, removing a reseller: 505 C: 506 C: 507 C: 508 C: 509 C: 511 C: example.com 512 C: 513 C: 514 C: 515 C: 517 C: 518 C: 519 C: 520 C: 521 C: 522 C: ABC-12345 523 C: 524 C: 526 Example command, removing multiple organizations: 528 C: 529 C: 530 C: 531 C: 532 C: 534 C: example.com 535 C: 536 C: 537 C: 538 C: 540 C: 541 C: 542 C: 543 C: 544 C: 545 C: 546 C: ABC-12345 547 C: 548 C: 550 Example command, updating reseller identifier: 552 C: 553 C: 554 C: 555 C: 556 C: 558 C: example.com 559 C: 560 C: 561 C: 562 C: 564 C: 565 C: myreseller 566 C: 567 C: 568 C: 569 C: ABC-12345 570 C: 571 C: 573 Example command, updating multiple organization identifiers: 575 C: 576 C: 577 C: 578 C: 579 C: 581 C: example.com 582 C: 583 C: 584 C: 585 C: 587 C: 588 C: myreseller 589 C: myproxy 590 C: 591 C: 592 C: 593 C: ABC-12345 594 C: 595 C: 597 When an extended command has been processed successfully, 598 the EPP response is as described in the EPP object extension. 600 5. Formal Syntax 602 An EPP object mapping is specified in XML Schema notation. The 603 formal syntax presented here is a complete schema representation of 604 the object mapping suitable for automated validation of EPP XML 605 instances. The BEGIN and END tags are not part of the schema; they 606 are used to note the beginning and ending of the schema for URI 607 registration purposes. 609 BEGIN 610 612 619 620 621 Extensible Provisioning Protocol v1.0 622 Organization Extension Schema v1.0 623 624 626 627 630 634 637 638 639 640 644 645 646 647 651 652 653 655 659 660 662 665 666 667 672 677 682 683 685 686 687 689 693 694 695 696 700 701 702 703 705 710 711 713 714 715 END 717 6. Internationalization Considerations 719 EPP is represented in XML, which provides native support for encoding 720 information using the Unicode character set and its more compact 721 representations including UTF-8. Conformant XML processors recognize 722 both UTF-8 and UTF-16. Though XML includes provisions to identify 723 and use other character encodings through use of an "encoding" 724 attribute in an declaration, use of UTF-8 is RECOMMENDED. 726 As an extension of the EPP domain name mapping, the elements, element 727 content described in this document MUST inherit the 728 internationalization conventions used to represent higher-layer 729 domain and core protocol structures present in an XML instance that 730 includes this extension. 732 7. IANA Considerations 734 7.1. XML Namespace 736 This document uses URNs to describe XML namespaces and XML schemas 737 conforming to a registry mechanism described in [RFC3688]. IANA is 738 requested to assignment the following URI. 740 Registration request for the organization namespace: 742 URI: urn:ietf:params:xml:ns:orgext-1.0 743 Registrant Contact: See the "Author's Address" section of this 744 document. 746 XML: See the "Formal Syntax" section of this document. 748 7.2. EPP Extension Registry 750 The EPP extension described in this document should be registered by 751 the IANA in the EPP Extension Registry described in [RFC7451]. The 752 details of the registration are as follows: 754 Name of Extension: Organization Extension 756 Document status: Standards Track 758 Reference: (insert reference to RFC version of this document) 760 Registrant Name and Email Address: IESG 762 TLDs: any 764 IPR Disclosure: none 766 Status: active 768 Notes: none 770 8. Implementation Status 772 Note to RFC Editor: Please remove this section and the reference to 773 [RFC7942] before publication. This section records the status of 774 known implementations of the protocol defined by this specification 775 at the time of posting of this Internet-Draft, and is based on a 776 proposal described in [RFC7942]. The description of implementations 777 in this section is intended to assist the IETF in its decision 778 processes in progressing drafts to RFCs. Please note that the 779 listing of any individual implementation here does not imply 780 endorsement by the IETF. Furthermore, no effort has been spent to 781 verify the information presented here that was supplied by IETF 782 contributors. This is not intended as, and must not be construed to 783 be, a catalog of available implementations or their features. 784 Readers are advised to note that other implementations may exist. 786 According to [RFC7942], "this will allow reviewers and working groups 787 to assign due consideration to documents that have the benefit of 788 running code, which may serve as evidence of valuable experimentation 789 and feedback that have made the implemented protocols more mature. 791 It is up to the individual working groups to use this information as 792 they see fit". 794 8.1. Verisign EPP SDK 796 Organization: Verisign Inc. 798 Name: Verisign EPP SDK 800 Description: The Verisign EPP SDK includes both a full client 801 implementation and a full server stub implementation of draft-ietf- 802 regext-org-ext. 804 Level of maturity: Development 806 Coverage: All aspects of the protocol are implemented. 808 Licensing: GNU Lesser General Public License 810 Contact: jgould@verisign.com 812 URL: https://www.verisign.com/en_US/channel-resources/domain- 813 registry-products/epp-sdks 815 8.2. CNNIC Implementation 817 Organization: CNNIC 819 Name: Organization Extension for EPP 821 Description: CNNIC is trying to update organization extension from 822 previous reseller extension according to this document. 824 Level of maturity: Development 826 Coverage: Organization extension for EPP 828 Contact: zhouguiqing@cnnic.cn 830 9. Security Considerations 832 The object mapping extension described in this document does not 833 provide any other security services or introduce any additional 834 considerations beyond those described by [RFC5730], [RFC5731], 835 [RFC5732] and [RFC5733] or those caused by the protocol layers used 836 by EPP. 838 10. Acknowledgment 840 The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick 841 Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful 842 review and valuable comments. 844 11. References 846 11.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 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 867 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 868 August 2009, . 870 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 871 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 872 August 2009, . 874 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 875 Code: The Implementation Status Section", BCP 205, 876 RFC 7942, DOI 10.17487/RFC7942, July 2016, 877 . 879 [W3C.REC-xml-20040204] 880 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 881 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 882 Edition)", World Wide Web Consortium FirstEdition REC-xml- 883 20040204", February 2004, 884 . 886 [W3C.REC-xmlschema-1-20041028] 887 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 888 ""XML Schema Part 1: Structures Second Edition", World 889 Wide Web Consortium Recommendation REC-xmlschema- 890 1-20041028", October 2004, 891 . 893 [W3C.REC-xmlschema-2-20041028] 894 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 895 Second Edition", World Wide Web Consortium Recommendation 896 REC-xmlschema-2-20041028", October 2004, 897 . 899 11.2. Informative References 901 [ID.draft-ietf-regext-org] 902 Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, 903 "Extensible Provisioning Protocol (EPP) Reseller Mapping", 904 Apr 2018, 905 . 907 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 908 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 909 February 2015, . 911 Appendix A. Change Log 913 Initial -00: Individual document submitted. 915 -01: 917 * Updated abstract and introduction. 919 * Revised typos in info response. 921 * Added explanations on how to process reseller extension after 922 successful transfer operation. 924 * Modified explanation. 926 * Deleted reseller name element in and 927 commands. 929 * Removed some inaccurate comments from xml schema. 931 * Modified the element name of reseller id and reseller name. 933 -02: 935 * Changed author information. 937 * Updated xml typos to 938 in response. 940 -03: 942 * Changed author information. 944 * Updated section 3.1. 946 * Removed reseller name element in response. 948 * Added acknowledgment. 950 * Revised the typo "resellerr" to "resellerext". 952 WG document-00: WG document submitted 954 WG document-01: Keep document alive for further discussion. The 955 requirement of reseller information is clear for both registrar 956 and registry. What we should reach a consensus is whether the 957 extension should support only a name or ID and name. 959 Organization WG document-00: Change to a generic organization object 960 extension. 962 Organization WG document-01: Added "Implementation Status" section. 964 Organization WG document-02: Accepted some of the feedbacks on the 965 mailing list. Modified the examples in the document. 967 Organization WG document-03: 969 * Updated typos. 971 * Changed some descriptions about and role attribute. 973 * Modified the example of "domain with no organization". 975 * Updated section 8, adding implementation status of Verisign. 977 Organization WG document-04: 979 * Updated typos. 981 * Removed the example of command, domain with no 982 organization. 984 * Updated references. 986 * Updated section 8 of implementation status. 988 Organization WG document-05: 990 * Removed the minOccurs="0" from the addRemChgType type of the 991 XML schema 993 * Removed the third paragraph of "Implementation Status". 995 * Remove the Informative Reference to draft-ietf-regext-reseller- 996 ext from the draft. 998 Authors' Addresses 1000 Linlin Zhou 1001 CNNIC 1002 4 South 4th Street, Zhongguancun, Haidian District 1003 Beijing, Beijing 100190 1004 China 1006 Phone: +86 10 5881 2677 1007 Email: zhoulinlin@cnnic.cn 1009 Ning Kong 1010 CNNIC 1011 4 South 4th Street, Zhongguancun, Haidian District 1012 Beijing, Beijing 100190 1013 China 1015 Phone: +86 10 5881 3147 1016 Email: nkong@cnnic.cn 1018 Junkai Wei 1019 CNNIC 1020 4 South 4th Street, Zhongguancun, Haidian District 1021 Beijing, Beijing 100190 1022 China 1024 Phone: +86 10 5881 3494 1025 Email: weijunkai@cnnic.cn 1026 Xiaodong Lee 1027 CNNIC 1028 4 South 4th Street, Zhongguancun, Haidian District 1029 Beijing, Beijing 100190 1030 China 1032 Phone: +86 10 5881 3020 1033 Email: xl@cnnic.cn 1035 James Gould 1036 Verisign, Inc. 1037 12061 Bluemont Way 1038 Reston, VA 20190 1039 US 1041 Email: jgould@verisign.com