idnits 2.17.1 draft-ietf-regext-org-ext-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 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 9, 2018) is 2178 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: 0 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 J. Wei 5 Expires: November 10, 2018 X. Lee 6 CNNIC 7 J. Gould 8 Verisign, Inc. 9 May 9, 2018 11 Organization Extension for the Extensible Provisioning Protocol (EPP) 12 draft-ietf-regext-org-ext-06 14 Abstract 16 This mapping which is an extension to EPP object mappings, is 17 designed to support assigning an organization to any existing object 18 (domain, host, contact) as well as any future objects. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on November 10, 2018. 37 Copyright Notice 39 Copyright (c) 2018 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 This document may contain material from IETF Documents or IETF 53 Contributions published or made publicly available before November 54 10, 2008. The person(s) controlling the copyright in some of this 55 material may not have granted the IETF Trust the right to allow 56 modifications of such material outside the IETF Standards Process. 57 Without obtaining an adequate license from the person(s) controlling 58 the copyright in such materials, this document may not be modified 59 outside the IETF Standards Process, and derivative works of it may 60 not be created outside the IETF Standards Process, except to format 61 it for publication as an RFC or to translate it into languages other 62 than English. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 67 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 68 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 69 3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4 70 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 71 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4 72 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 73 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 4 74 4.1.3. EPP Query Command . . . . . . . . . . . . 7 75 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 76 4.2.1. EPP Command . . . . . . . . . . . . . . . . 8 77 4.2.2. EPP Command . . . . . . . . . . . . . . . . 10 78 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 10 79 4.2.4. EPP Command . . . . . . . . . . . . . . . 11 80 4.2.5. EPP Command . . . . . . . . . . . . . . . . 11 81 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15 82 6. Internationalization Considerations . . . . . . . . . . . . . 17 83 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 84 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 85 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 86 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 87 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19 88 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19 89 9. Security Considerations . . . . . . . . . . . . . . . . . . . 19 90 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20 91 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 92 11.1. Normative References . . . . . . . . . . . . . . . . . . 20 93 11.2. Informative References . . . . . . . . . . . . . . . . . 21 94 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 97 1. Introduction 99 In the business model of domain registration, we usually have 3 roles 100 of entities, a registrant, a registrar and a registry. There may be 101 other roles of entities involved in the domain registration process 102 which are not formally defined, such as resellers, DNS service 103 operators, privacy proxy, etc. 105 A domain reseller is an individual or a company that acts as a agent 106 for accredited registrars. A third-party DNS service operator is 107 responsible for a zone where the operator is neither the registrant 108 nor the registrar of record for the delegation. A privacy proxy is 109 an entity used for domain registrations to protect the private 110 information of the individuals and organizations. These kind of 111 entities are defined as "organizations" with different role types in 112 this document. 114 In order to facilitate provisioning and management of organization 115 information in a shared central repository, this document proposes an 116 organization extension mapping for any EPP object like domain names 117 in [RFC5731], hosts in [RFC5732] and contacts in [RFC5733]. The 118 examples provided in this document are used for the domain object for 119 illustration purpose. The host and contact object could be extended 120 in the same way with the domain object. 122 An organization mapping object defined in [ID.draft-ietf-regext-org] 123 SHOULD be created first. The organization information specified in 124 this document MUST reference the existing organization identifier. 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 orgext-1.0 in this document is used as an abbreviation for 146 urn:ietf:params:xml:ns:orgext-1.0. 148 3. Object Attributes 150 This extension adds additional elements to EPP object mappings like 151 the EPP domain name mapping [RFC5731]. Only the new elements are 152 described here. 154 3.1. Organization Identifier 156 Organization identifier provides the ID of an organization. Its 157 corresponding element is which refers to the 158 element defined in [ID.draft-ietf-regext-org]. All 159 organization objects are identified by a server-unique identifier. 161 4. EPP Command Mapping 163 A detailed description of the EPP syntax and semantics can be found 164 in the EPP core protocol specification [RFC5730]. The command 165 mappings described here are specifically for use in provisioning and 166 managing organization information via EPP. 168 4.1. EPP Query Commands 170 EPP provides three commands to retrieve domain information: 171 to determine if a domain object can be provisioned within a 172 repository, to retrieve detailed information associated with a 173 domain object, and to retrieve domain-object transfer 174 status information. 176 4.1.1. EPP Command 178 This extension does not add any elements to the EPP command 179 or response described in the EPP domain name mapping 180 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733]. 182 4.1.2. EPP Command 184 This extension does not add any element to the EPP command 185 described in the EPP domain mapping [RFC5731], host mapping [RFC5732] 186 and contact mapping [RFC5733]. However, additional elements are 187 defined for the response in the EPP domain mapping [RFC5731], 188 host mapping [RFC5732] and contact mapping [RFC5733]. 190 When an command has been processed successfully, the EPP 191 element MUST contain child elements as described in the EPP 192 object extensions. In addition, the EPP element SHOULD 193 contain a child element that identifies the 194 extension namespace if the object has data associated with this 195 extension and based on server policy. The element 196 contains the following child elements: 198 o Zero or more elements are allowed that contains the 199 identifier of the organization. The "role" attribute is used to 200 represent the relationship that the organization has to the 201 object. See Section 7.3 in [ID.draft-ietf-regext-org] for a list 202 of values. 204 Example response for an authorized client with multiple 205 organizations: 207 S: 208 S: 209 S: 210 S: 211 S: Command completed successfully 212 S: 213 S: 214 S: 216 S: example.com 217 S: EXAMPLE1-REP 218 S: 219 S: jd1234 220 S: sh8013 221 S: sh8013 222 S: sh8013 223 S: 224 S: ns1.example.com 225 S: 226 S: ClientX 227 S: ClientY 228 S: 2015-02-06T04:01:21.0Z 229 S: 2018-02-06T04:01:21.0Z 230 S: 231 S: 2fooBAR 232 S: 233 S: 234 S: 235 S: 236 S: 238 S: myreseller 239 S: myproxy 240 S: 241 S: 242 S: 243 S: ngcl-IvJjzMZc 244 S: test142AWQONJZ 245 S: 246 S: 247 S: 249 Example response for an authorized client with no 250 organization: 252 S: 253 S: 254 S: 255 S: 256 S: Command completed successfully 257 S: 258 S: 259 S: 261 S: example.com 262 S: EXAMPLE1-REP 263 S: 264 S: jd1234 265 S: sh8013 266 S: sh8013 267 S: sh8013 268 S: 269 S: ns1.example.com 270 S: 271 S: ClientX 272 S: ClientY 273 S: 2015-02-06T04:01:21.0Z 274 S: 2018-02-06T04:01:21.0Z 275 S: 276 S: 2fooBAR 277 S: 278 S: 279 S: 280 S: 281 S: 283 S: 284 S: 285 S: ngcl-IvJjzMZc 286 S: test142AWQONJZ 287 S: 288 S: 289 S: 291 An EPP error response MUST be returned if an command cannot be 292 processed for any reason. 294 4.1.3. EPP Query Command 296 This extension does not add any elements to the EPP query 297 command or query response described in the EPP domain name 298 mapping [RFC5731], host mapping [RFC5732] and contact mapping 299 [RFC5733]. 301 4.2. EPP Transform Commands 303 EPP provides five commands to transform domain objects: to 304 create an instance of a domain object, to delete an instance 305 of a domain object, to extend the validity period of a domain 306 object, to manage domain object sponsorship changes, and 307 to change information associated with a domain object. 309 4.2.1. EPP Command 311 This extension defines additional elements for the EPP 312 command described in the EPP object extensions. No additional 313 elements are defined for the EPP response. 315 The EPP command provides a transform operation that allows a 316 client to create an object. In addition to the EPP command elements 317 described in the EPP object extensions, the command MUST contain an 318 element, and the element MUST contain a child 319 element that identifies the extension namespace if 320 the client wants to associate data defined in this extension to the 321 object. The element contains the following child 322 elements: 324 o One or more elements that contains the identifier of 325 the organization. The "role" attribute is used to represent the 326 relationship that the organization has to the object. See 327 Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. 329 Example Command with only one organization: 331 C: 332 C: 333 C: 334 C: 335 C: 337 C: example.com 338 C: 3 339 C: 340 C: ns1.example.com 341 C: 342 C: jd1234 343 C: sh8013 344 C: sh8013 345 C: sh8013 346 C: 347 C: fooBAR 348 C: 349 C: 350 C: 351 C: 352 C: 354 C: myreseller 355 C: 356 C: 357 C: ABC-12345 358 C: 359 C: 361 Example Command with multiple organizations: 363 C: 364 C: 365 C: 366 C: 367 C: 369 C: example.com 370 C: 3 371 C: 372 C: ns1.example.com 373 C: 374 C: jd1234 375 C: sh8013 376 C: sh8013 377 C: sh8013 378 C: 379 C: fooBAR 380 C: 381 C: 382 C: 383 C: 384 C: 386 C: myreseller 387 C: myproxy 388 C: 389 C: 390 C: ABC-12345 391 C: 392 C: 394 When a command has been processed successfully, the EPP 395 response is as described in the EPP object extension. 397 An EPP error response MUST be returned if a command cannot 398 be processed for any reason. 400 4.2.2. EPP Command 402 This extension does not add any elements to the EPP command 403 or response described in the EPP domain mapping [RFC5731], 404 host mapping [RFC5732] and contact mapping [RFC5733]. 406 4.2.3. EPP Command 408 This extension does not add any elements to the EPP command 409 or response described in the EPP domain mapping [RFC5731], 410 host mapping [RFC5732] and contact mapping [RFC5733]. 412 4.2.4. EPP Command 414 This extension does not add any elements to the EPP 415 command or response described in the EPP domain mapping 416 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733], but 417 after a successful transfer of an object with an assigned 418 organization, the handling of the assigned organization is dependent 419 on the organization roles and server policy. 421 4.2.5. EPP Command 423 This extension defines additional elements for the EPP 424 command described in the EPP domain mapping [RFC5731], host mapping 425 [RFC5732] and contact mapping [RFC5733]. No additional elements are 426 defined for the EPP response. 428 The EPP command provides a transform operation that allows a 429 client to modify the attribute of an object. In addition to the EPP 430 command elements, the command MUST contain an 431 element, and the element MUST contain a child 432 element that identifies the extension namespace if 433 the client wants to update the object with data defined in this 434 extension. The element contains the following child 435 elements: 437 o An OPTIONAL element that contains attribute values to 438 be added to the object. 440 o An OPTIONAL element that contains attribute values to 441 be removed from the object. 443 o An OPTIONAL element that contains attribute values to 444 be changed. 446 At least one and only one , or 447 element MUST be provided. The , and 448 elements contain the following child element: 450 o One or more elements that contains the identifier of 451 the organization. The "role" attribute is used to represent the 452 relationship that the organization has to the object. See 453 Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. 455 Example command, adding a reseller: 457 C: 458 C: 459 C: 460 C: 461 C: 463 C: example.com 464 C: 465 C: 466 C: 467 C: 469 C: 470 C: myreseller 471 C: 472 C: 473 C: 474 C: ABC-12345 475 C: 476 C: 478 Example command, adding multiple organizations: 480 C: 481 C: 482 C: 483 C: 484 C: 486 C: example.com 487 C: 488 C: 489 C: 490 C: 492 C: 493 C: myreseller 494 C: myproxy 495 C: 496 C: 497 C: 498 C: ABC-12345 499 C: 500 C: 502 Example command, removing a reseller: 504 C: 505 C: 506 C: 507 C: 508 C: 510 C: example.com 511 C: 512 C: 513 C: 514 C: 516 C: 517 C: 518 C: 519 C: 520 C: 521 C: ABC-12345 522 C: 523 C: 525 Example command, removing multiple organizations: 527 C: 528 C: 529 C: 530 C: 531 C: 533 C: example.com 534 C: 535 C: 536 C: 537 C: 539 C: 540 C: 541 C: 542 C: 543 C: 544 C: 545 C: ABC-12345 546 C: 547 C: 549 Example command, updating reseller identifier: 551 C: 552 C: 553 C: 554 C: 555 C: 557 C: example.com 558 C: 559 C: 560 C: 561 C: 563 C: 564 C: myreseller 565 C: 566 C: 567 C: 568 C: ABC-12345 569 C: 570 C: 572 Example command, updating multiple organization identifiers: 574 C: 575 C: 576 C: 577 C: 578 C: 580 C: example.com 581 C: 582 C: 583 C: 584 C: 586 C: 587 C: myreseller 588 C: myproxy 589 C: 590 C: 591 C: 592 C: ABC-12345 593 C: 594 C: 596 When an extended command has been processed successfully, 597 the EPP response is as described in the EPP object extension. 599 5. Formal Syntax 601 An EPP object mapping is specified in XML Schema notation. The 602 formal syntax presented here is a complete schema representation of 603 the object mapping suitable for automated validation of EPP XML 604 instances. The BEGIN and END tags are not part of the schema; they 605 are used to note the beginning and ending of the schema for URI 606 registration purposes. 608 BEGIN 609 611 618 619 620 Extensible Provisioning Protocol v1.0 621 Organization Extension Schema v1.0 622 623 625 626 629 633 636 637 638 639 643 644 645 646 650 651 652 654 658 659 661 664 665 666 671 676 681 682 684 685 686 688 692 693 694 695 699 700 701 702 704 709 710 712 713 714 END 716 6. Internationalization Considerations 718 EPP is represented in XML, which provides native support for encoding 719 information using the Unicode character set and its more compact 720 representations including UTF-8. Conformant XML processors recognize 721 both UTF-8 and UTF-16. Though XML includes provisions to identify 722 and use other character encodings through use of an "encoding" 723 attribute in an declaration, use of UTF-8 is RECOMMENDED. 725 As an extension of the EPP domain name mapping, the elements, element 726 content described in this document MUST inherit the 727 internationalization conventions used to represent higher-layer 728 domain and core protocol structures present in an XML instance that 729 includes this extension. 731 7. IANA Considerations 733 7.1. XML Namespace 735 This document uses URNs to describe XML namespaces and XML schemas 736 conforming to a registry mechanism described in [RFC3688]. IANA is 737 requested to assignment the following URI. 739 Registration request for the organization namespace: 741 URI: urn:ietf:params:xml:ns:orgext-1.0 742 Registrant Contact: IESG 744 XML: See the "Formal Syntax" section of this document. 746 7.2. EPP Extension Registry 748 The EPP extension described in this document should be registered by 749 the IANA in the EPP Extension Registry described in [RFC7451]. The 750 details of the registration are as follows: 752 Name of Extension: Organization Extension for the Extensible 753 Provisioning Protocol (EPP) 755 Registrant Name and Email Address: IESG, iesg@ietf.org 757 TLDs: Any 759 IPR Disclosure: None 761 Status: Active 763 Notes: None 765 8. Implementation Status 767 Note to RFC Editor: Please remove this section and the reference to 768 [RFC7942] before publication. This section records the status of 769 known implementations of the protocol defined by this specification 770 at the time of posting of this Internet-Draft, and is based on a 771 proposal described in [RFC7942]. The description of implementations 772 in this section is intended to assist the IETF in its decision 773 processes in progressing drafts to RFCs. Please note that the 774 listing of any individual implementation here does not imply 775 endorsement by the IETF. Furthermore, no effort has been spent to 776 verify the information presented here that was supplied by IETF 777 contributors. This is not intended as, and must not be construed to 778 be, a catalog of available implementations or their features. 779 Readers are advised to note that other implementations may exist. 781 According to [RFC7942], "this will allow reviewers and working groups 782 to assign due consideration to documents that have the benefit of 783 running code, which may serve as evidence of valuable experimentation 784 and feedback that have made the implemented protocols more mature. 785 It is up to the individual working groups to use this information as 786 they see fit". 788 8.1. Verisign EPP SDK 790 Organization: Verisign Inc. 792 Name: Verisign EPP SDK 794 Description: The Verisign EPP SDK includes both a full client 795 implementation and a full server stub implementation of draft-ietf- 796 regext-org-ext. 798 Level of maturity: Development 800 Coverage: All aspects of the protocol are implemented. 802 Licensing: GNU Lesser General Public License 804 Contact: jgould@verisign.com 806 URL: https://www.verisign.com/en_US/channel-resources/domain- 807 registry-products/epp-sdks 809 8.2. CNNIC Implementation 811 Organization: CNNIC 813 Name: Organization Extension for EPP 815 Description: CNNIC is trying to update organization extension from 816 previous reseller extension according to this document. 818 Level of maturity: Development 820 Coverage: Organization extension for EPP 822 Contact: zhouguiqing@cnnic.cn 824 9. Security Considerations 826 The object mapping extension described in this document does not 827 provide any other security services or introduce any additional 828 considerations beyond those described by [RFC5730], [RFC5731], 829 [RFC5732] and [RFC5733] or those caused by the protocol layers used 830 by EPP. 832 10. Acknowledgment 834 The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick 835 Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful 836 review and valuable comments. 838 11. References 840 11.1. Normative References 842 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 843 Requirement Levels", BCP 14, RFC 2119, 844 DOI 10.17487/RFC2119, March 1997, 845 . 847 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 848 DOI 10.17487/RFC3688, January 2004, 849 . 851 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 852 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 853 . 855 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 856 Domain Name Mapping", STD 69, RFC 5731, 857 DOI 10.17487/RFC5731, August 2009, 858 . 860 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 861 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 862 August 2009, . 864 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 865 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 866 August 2009, . 868 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 869 Code: The Implementation Status Section", BCP 205, 870 RFC 7942, DOI 10.17487/RFC7942, July 2016, 871 . 873 [W3C.REC-xml-20040204] 874 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 875 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 876 Edition)", World Wide Web Consortium FirstEdition REC-xml- 877 20040204", February 2004, 878 . 880 [W3C.REC-xmlschema-1-20041028] 881 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 882 ""XML Schema Part 1: Structures Second Edition", World 883 Wide Web Consortium Recommendation REC-xmlschema- 884 1-20041028", October 2004, 885 . 887 [W3C.REC-xmlschema-2-20041028] 888 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 889 Second Edition", World Wide Web Consortium Recommendation 890 REC-xmlschema-2-20041028", October 2004, 891 . 893 11.2. Informative References 895 [ID.draft-ietf-regext-org] 896 Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, 897 "Extensible Provisioning Protocol (EPP) Reseller Mapping", 898 Apr 2018, 899 . 901 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 902 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 903 February 2015, . 905 Appendix A. Change Log 907 Initial -00: Individual document submitted. 909 -01: 911 * Updated abstract and introduction. 913 * Revised typos in info response. 915 * Added explanations on how to process reseller extension after 916 successful transfer operation. 918 * Modified explanation. 920 * Deleted reseller name element in and 921 commands. 923 * Removed some inaccurate comments from xml schema. 925 * Modified the element name of reseller id and reseller name. 927 -02: 929 * Changed author information. 931 * Updated xml typos to 932 in response. 934 -03: 936 * Changed author information. 938 * Updated section 3.1. 940 * Removed reseller name element in response. 942 * Added acknowledgment. 944 * Revised the typo "resellerr" to "resellerext". 946 WG document-00: WG document submitted 948 WG document-01: Keep document alive for further discussion. The 949 requirement of reseller information is clear for both registrar 950 and registry. What we should reach a consensus is whether the 951 extension should support only a name or ID and name. 953 Organization WG document-00: Change to a generic organization object 954 extension. 956 Organization WG document-01: Added "Implementation Status" section. 958 Organization WG document-02: Accepted some of the feedbacks on the 959 mailing list. Modified the examples in the document. 961 Organization WG document-03: 963 * Updated typos. 965 * Changed some descriptions about and role attribute. 967 * Modified the example of "domain with no organization". 969 * Updated section 8, adding implementation status of Verisign. 971 Organization WG document-04: 973 * Updated typos. 975 * Removed the example of command, domain with no 976 organization. 978 * Updated references. 980 * Updated section 8 of implementation status. 982 Organization WG document-05: 984 * Removed the minOccurs="0" from the addRemChgType type of the 985 XML schema 987 * Removed the third paragraph of "Implementation Status". 989 * Remove the Informative Reference to draft-ietf-regext-reseller- 990 ext from the draft. 992 Organization WG document-06: 994 * Updated "Abstraction". 996 * Added "Query" for " Query Command". 998 * Change "Registrant Contact" to IESG in section 7.1. 1000 * Modified section 7.2. 1002 Authors' Addresses 1004 Linlin Zhou 1005 CNNIC 1006 4 South 4th Street, Zhongguancun, Haidian District 1007 Beijing, Beijing 100190 1008 China 1010 Phone: +86 10 5881 2677 1011 Email: zhoulinlin@cnnic.cn 1013 Ning Kong 1014 CNNIC 1015 4 South 4th Street, Zhongguancun, Haidian District 1016 Beijing, Beijing 100190 1017 China 1019 Phone: +86 10 5881 3147 1020 Email: nkong@cnnic.cn 1021 Junkai Wei 1022 CNNIC 1023 4 South 4th Street, Zhongguancun, Haidian District 1024 Beijing, Beijing 100190 1025 China 1027 Phone: +86 10 5881 3494 1028 Email: weijunkai@cnnic.cn 1030 Xiaodong Lee 1031 CNNIC 1032 4 South 4th Street, Zhongguancun, Haidian District 1033 Beijing, Beijing 100190 1034 China 1036 Email: xl@cnnic.cn 1038 James Gould 1039 Verisign, Inc. 1040 12061 Bluemont Way 1041 Reston, VA 20190 1042 US 1044 Email: jgould@verisign.com