idnits 2.17.1 draft-ietf-regext-org-ext-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 : ---------------------------------------------------------------------------- ** 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 4, 2018) is 2156 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 5, 2018 X. Lee 6 CNNIC 7 J. Gould 8 Verisign, Inc. 9 May 4, 2018 11 Organization Extension for the Extensible Provisioning Protocol (EPP) 12 draft-ietf-regext-org-ext-04 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 5, 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 8.3. Reseller Extension . . . . . . . . . . . . . . . . . . . 20 91 9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 92 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20 93 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 94 11.1. Normative References . . . . . . . . . . . . . . . . . . 20 95 11.2. Informative References . . . . . . . . . . . . . . . . . 21 96 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 22 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 99 1. Introduction 101 In the business model of domain registration, we usually have 3 roles 102 of entities, a registrant, a registrar and a registry. There may 103 have some other roles of entities involved in the domain registration 104 process which are not formally defined, such as resellers, DNS 105 service operators, privacy proxy, etc. 107 A domain reseller is an individual or a company that acts as a agent 108 for accredited registrars. A third-party DNS service operator is 109 responsible for a zone where the operator is neither the registrant 110 nor the registrar of records for the delegation. And a privacy proxy 111 is an entity that provides with individuals or organizations domain 112 registration without exposing their private information. These kind 113 of entities are defined as "organizations" with different role types 114 in this document. 116 In order to facilitate provisioning and management of organization 117 information in a shared central repository, this document proposes an 118 organization extension mapping for any EPP object like domain names 119 in [RFC5731], hosts in [RFC5732] and contacts in [RFC5733]. The 120 examples provided in this document are used for the domain object for 121 illustration purpose. The host and contact object could be extended 122 in the same way with the domain object. 124 An organization mapping object defined in [ID.draft-ietf-regext-org] 125 SHOULD be created first. The organization information specified in 126 this document MUST reference the existing organization identifier. 128 This document is specified using the XML 1.0 as described in 129 [W3C.REC-xml-20040204] and XML Schema notation as described in 130 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. 132 2. Conventions Used in This Document 134 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 135 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 136 document are to be interpreted as described in [RFC2119]. 138 In examples, "C:" represents lines sent by a protocol client and "S:" 139 represents lines returned by a protocol server. Indentation and 140 white space in examples are provided only to illustrate element 141 relationships and are not a REQUIRED feature of this specification. 143 XML is case sensitive. Unless stated otherwise, XML specifications 144 and examples provided in this document MUST be interpreted in the 145 character case presented to develop a conforming implementation. 147 orgext-1.0 in this document is used as an abbreviation for 148 urn:ietf:params:xml:ns:orgext-1.0. 150 3. Object Attributes 152 This extension adds additional elements to EPP object mappings like 153 the EPP domain name mapping [RFC5731]. Only the new elements are 154 described here. 156 3.1. Organization Identifier 158 Organization identifier provides the ID of an organization. Its 159 corresponding element is which refers to the 160 element defined in [ID.draft-ietf-regext-org]. All 161 organization objects are identified by a server-unique identifier. 163 4. EPP Command Mapping 165 A detailed description of the EPP syntax and semantics can be found 166 in the EPP core protocol specification [RFC5730]. The command 167 mappings described here are specifically for use in provisioning and 168 managing organization information via EPP. 170 4.1. EPP Query Commands 172 EPP provides three commands to retrieve domain information: 173 to determine if a domain object can be provisioned within a 174 repository, to retrieve detailed information associated with a 175 domain object, and to retrieve domain-object transfer 176 status information. 178 4.1.1. EPP Command 180 This extension does not add any elements to the EPP command 181 or response described in the EPP domain name mapping 182 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733]. 184 4.1.2. EPP Command 186 This extension does not add any element to the EPP command 187 described in the EPP domain mapping [RFC5731], host mapping [RFC5732] 188 and contact mapping [RFC5733]. However, additional elements are 189 defined for the response in the EPP domain mapping [RFC5731], 190 host mapping [RFC5732] and contact mapping [RFC5733]. 192 When an command has been processed successfully, the EPP 193 element MUST contain child elements as described in the EPP 194 object extensions. In addition, the EPP element SHOULD 195 contain a child element that identifies the 196 extension namespace if the object has data associated with this 197 extension and based on server policy. The element 198 contains the following child elements: 200 o Zero or more elements are allowed that contains the 201 identifier of the organization. The "role" attribute is used to 202 represent the relationship that the organization has to the 203 object. See Section 7.3 in [ID.draft-ietf-regext-org] for a list 204 of values. 206 Example response for an authorized client with multiple 207 organizations: 209 S: 210 S: 211 S: 212 S: 213 S: Command completed successfully 214 S: 215 S: 216 S: 218 S: example.com 219 S: EXAMPLE1-REP 220 S: 221 S: jd1234 222 S: sh8013 223 S: sh8013 224 S: sh8013 225 S: 226 S: ns1.example.com 227 S: 228 S: ClientX 229 S: ClientY 230 S: 2015-02-06T04:01:21.0Z 231 S: 2018-02-06T04:01:21.0Z 232 S: 233 S: 2fooBAR 234 S: 235 S: 236 S: 237 S: 238 S: 240 S: myreseller 241 S: myproxy 242 S: 243 S: 244 S: 245 S: ngcl-IvJjzMZc 246 S: test142AWQONJZ 247 S: 248 S: 249 S: 251 Example response for an authorized client with no 252 organization: 254 S: 255 S: 256 S: 257 S: 258 S: Command completed successfully 259 S: 260 S: 261 S: 263 S: example.com 264 S: EXAMPLE1-REP 265 S: 266 S: jd1234 267 S: sh8013 268 S: sh8013 269 S: sh8013 270 S: 271 S: ns1.example.com 272 S: 273 S: ClientX 274 S: ClientY 275 S: 2015-02-06T04:01:21.0Z 276 S: 2018-02-06T04:01:21.0Z 277 S: 278 S: 2fooBAR 279 S: 280 S: 281 S: 282 S: 283 S: 285 S: 286 S: 287 S: ngcl-IvJjzMZc 288 S: test142AWQONJZ 289 S: 290 S: 291 S: 293 An EPP error response MUST be returned if an command cannot be 294 processed for any reason. 296 4.1.3. EPP Command 298 This extension does not add any elements to the EPP 299 command or response described in the EPP domain name 300 mapping [RFC5731], host mapping [RFC5732] and contact mapping 301 [RFC5733]. 303 4.2. EPP Transform Commands 305 EPP provides five commands to transform domain objects: to 306 create an instance of a domain object, to delete an instance 307 of a domain object, to extend the validity period of a domain 308 object, to manage domain object sponsorship changes, and 309 to change information associated with a domain object. 311 4.2.1. EPP Command 313 This extension defines additional elements for the EPP 314 command described in the EPP object extensions. No additional 315 elements are defined for the EPP response. 317 The EPP command provides a transform operation that allows a 318 client to create an object. In addition to the EPP command elements 319 described in the EPP object extensions, the command MUST contain an 320 element, and the element MUST contain a child 321 element that identifies the extension namespace if 322 the client wants to associate data defined in this extension to the 323 object. The element contains the following child 324 elements: 326 o One or more elements that contains the identifier of 327 the organization. The "role" attribute is used to represent the 328 relationship that the organization has to the object. See 329 Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. 331 Example Command with only one organization: 333 C: 334 C: 335 C: 336 C: 337 C: 339 C: example.com 340 C: 3 341 C: 342 C: ns1.example.com 343 C: 344 C: jd1234 345 C: sh8013 346 C: sh8013 347 C: sh8013 348 C: 349 C: fooBAR 350 C: 351 C: 352 C: 353 C: 354 C: 356 C: myreseller 357 C: 358 C: 359 C: ABC-12345 360 C: 361 C: 363 Example Command with multiple organizations: 365 C: 366 C: 367 C: 368 C: 369 C: 371 C: example.com 372 C: 3 373 C: 374 C: ns1.example.com 375 C: 376 C: jd1234 377 C: sh8013 378 C: sh8013 379 C: sh8013 380 C: 381 C: fooBAR 382 C: 383 C: 384 C: 385 C: 386 C: 388 C: myreseller 389 C: myproxy 390 C: 391 C: 392 C: ABC-12345 393 C: 394 C: 396 When a command has been processed successfully, the EPP 397 response is as described in the EPP object extension. 399 An EPP error response MUST be returned if a command cannot 400 be processed for any reason. 402 4.2.2. EPP Command 404 This extension does not add any elements to the EPP command 405 or response described in the EPP domain mapping [RFC5731], 406 host mapping [RFC5732] and contact mapping [RFC5733]. 408 4.2.3. EPP Command 410 This extension does not add any elements to the EPP command 411 or response described in the EPP domain mapping [RFC5731], 412 host mapping [RFC5732] and contact mapping [RFC5733]. 414 4.2.4. EPP Command 416 This extension does not add any elements to the EPP 417 command or response described in the EPP domain mapping 418 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733], but 419 after a successful transfer of an object with an assigned 420 organization, the handling of the assigned organization is dependent 421 on the organization roles and server policy. 423 4.2.5. EPP Command 425 This extension defines additional elements for the EPP 426 command described in the EPP domain mapping [RFC5731], host mapping 427 [RFC5732] and contact mapping [RFC5733]. No additional elements are 428 defined for the EPP response. 430 The EPP command provides a transform operation that allows a 431 client to modify the attribute of an object. In addition to the EPP 432 command elements, the command MUST contain an 433 element, and the element MUST contain a child 434 element that identifies the extension namespace if 435 the client wants to update the object with data defined in this 436 extension. The element contains the following child 437 elements: 439 o An OPTIONAL element that contains attribute values to 440 be added to the object. 442 o An OPTIONAL element that contains attribute values to 443 be removed from the object. 445 o An OPTIONAL element that contains attribute values to 446 be changed. 448 At least one and only one , or 449 element MUST be provided. The , and 450 elements contain the following child element: 452 o One or more element that contains the identifier of 453 the organization. The "role" attribute is used to represent the 454 relationship that the organization has to the object. See 455 Section 7.3 in [ID.draft-ietf-regext-org] for a list of values. 457 Example command, adding a reseller: 459 C: 460 C: 461 C: 462 C: 463 C: 465 C: example.com 466 C: 467 C: 468 C: 469 C: 471 C: 472 C: myreseller 473 C: 474 C: 475 C: 476 C: ABC-12345 477 C: 478 C: 480 Example command, adding multiple organizations: 482 C: 483 C: 484 C: 485 C: 486 C: 488 C: example.com 489 C: 490 C: 491 C: 492 C: 494 C: 495 C: myreseller 496 C: myproxy 497 C: 498 C: 499 C: 500 C: ABC-12345 501 C: 502 C: 504 Example command, removing a reseller: 506 C: 507 C: 508 C: 509 C: 510 C: 512 C: example.com 513 C: 514 C: 515 C: 516 C: 518 C: 519 C: 520 C: 521 C: 522 C: 523 C: ABC-12345 524 C: 525 C: 527 Example command, removing multiple organizations: 529 C: 530 C: 531 C: 532 C: 533 C: 535 C: example.com 536 C: 537 C: 538 C: 539 C: 541 C: 542 C: 543 C: 544 C: 545 C: 546 C: 547 C: ABC-12345 548 C: 549 C: 551 Example command, updating reseller identifier: 553 C: 554 C: 555 C: 556 C: 557 C: 559 C: example.com 560 C: 561 C: 562 C: 563 C: 565 C: 566 C: myreseller 567 C: 568 C: 569 C: 570 C: ABC-12345 571 C: 572 C: 574 Example command, updating multiple organization identifiers: 576 C: 577 C: 578 C: 579 C: 580 C: 582 C: example.com 583 C: 584 C: 585 C: 586 C: 588 C: 589 C: myreseller 590 C: myproxy 591 C: 592 C: 593 C: 594 C: ABC-12345 595 C: 596 C: 598 When an extended command has been processed successfully, 599 the EPP response is as described in the EPP object extension. 601 5. Formal Syntax 603 An EPP object mapping is specified in XML Schema notation. The 604 formal syntax presented here is a complete schema representation of 605 the object mapping suitable for automated validation of EPP XML 606 instances. The BEGIN and END tags are not part of the schema; they 607 are used to note the beginning and ending of the schema for URI 608 registration purposes. 610 BEGIN 611 613 620 621 622 Extensible Provisioning Protocol v1.0 623 Organization Extension Schema v1.0 624 625 627 628 631 635 638 639 640 641 645 646 647 648 652 653 654 656 660 661 663 666 667 668 673 678 683 684 686 687 688 690 695 697 699 700 704 705 706 707 709 714 715 717 718 719 END 721 6. Internationalization Considerations 723 EPP is represented in XML, which provides native support for encoding 724 information using the Unicode character set and its more compact 725 representations including UTF-8. Conformant XML processors recognize 726 both UTF-8 and UTF-16. Though XML includes provisions to identify 727 and use other character encodings through use of an "encoding" 728 attribute in an declaration, use of UTF-8 is RECOMMENDED. 730 As an extension of the EPP domain name mapping, the elements, element 731 content described in this document MUST inherit the 732 internationalization conventions used to represent higher-layer 733 domain and core protocol structures present in an XML instance that 734 includes this extension. 736 7. IANA Considerations 738 7.1. XML Namespace 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 URI. 744 Registration request for the organization namespace: 746 URI: urn:ietf:params:xml:ns:orgext-1.0 748 Registrant Contact: See the "Author's Address" section of this 749 document. 751 XML: See the "Formal Syntax" section of this document. 753 7.2. EPP Extension Registry 755 The EPP extension described in this document should be registered by 756 the IANA in the EPP Extension Registry described in [RFC7451]. The 757 details of the registration are as follows: 759 Name of Extension: Organization Extension 761 Document status: Standards Track 763 Reference: (insert reference to RFC version of this document) 765 Registrant Name and Email Address: IESG 767 TLDs: any 769 IPR Disclosure: none 771 Status: active 773 Notes: none 775 8. Implementation Status 777 Note to RFC Editor: Please remove this section and the reference to 778 [RFC7942] before publication. This section records the status of 779 known implementations of the protocol defined by this specification 780 at the time of posting of this Internet-Draft, and is based on a 781 proposal described in [RFC7942]. The description of implementations 782 in this section is intended to assist the IETF in its decision 783 processes in progressing drafts to RFCs. Please note that the 784 listing of any individual implementation here does not imply 785 endorsement by the IETF. Furthermore, no effort has been spent to 786 verify the information presented here that was supplied by IETF 787 contributors. This is not intended as, and must not be construed to 788 be, a catalog of available implementations or their features. 789 Readers are advised to note that other implementations may exist. 791 According to [RFC7942], "this will allow reviewers and working groups 792 to assign due consideration to documents that have the benefit of 793 running code, which may serve as evidence of valuable experimentation 794 and feedback that have made the implemented protocols more mature. 795 It is up to the individual working groups to use this information as 796 they see fit". 798 Verisign has already implemented this extension. CNNIC and Net::DRI 799 (Patrick Mevzek) are in the process of development research to update 800 organization extension from reseller extension. Dns Belgium is 801 planning to implement it after the publication of this document. 803 8.1. Verisign EPP SDK 805 Organization: Verisign Inc. 807 Name: Verisign EPP SDK 809 Description: The Verisign EPP SDK includes both a full client 810 implementation and a full server stub implementation of draft-ietf- 811 regext-org-ext. 813 Level of maturity: Development 815 Coverage: All aspects of the protocol are implemented. 817 Licensing: GNU Lesser General Public License 819 Contact: jgould@verisign.com 821 URL: https://www.verisign.com/en_US/channel-resources/domain- 822 registry-products/epp-sdks 824 8.2. CNNIC Implementation 826 Organization: CNNIC 828 Name: Organization Extension for EPP 830 Description: CNNIC is trying to update organization extension from 831 previous reseller extension according to this document. 833 Level of maturity: Development 835 Coverage: Organization extension for EPP 837 Contact: zhouguiqing@cnnic.cn 839 8.3. Reseller Extension 841 This document was updated from [ID.draft-ietf-regext-reseller-ext]. 842 CNNIC, Verisign and Net::DRI (Patrick Mevzek) have already 843 implemented this extension. 845 9. Security Considerations 847 The object mapping extension described in this document does not 848 provide any other security services or introduce any additional 849 considerations beyond those described by [RFC5730], [RFC5731], 850 [RFC5732] and [RFC5733] or those caused by the protocol layers used 851 by EPP. 853 10. Acknowledgment 855 The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick 856 Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful 857 review and valuable comments. 859 11. References 861 11.1. Normative References 863 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 864 Requirement Levels", BCP 14, RFC 2119, 865 DOI 10.17487/RFC2119, March 1997, 866 . 868 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 869 DOI 10.17487/RFC3688, January 2004, 870 . 872 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 873 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 874 . 876 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 877 Domain Name Mapping", STD 69, RFC 5731, 878 DOI 10.17487/RFC5731, August 2009, 879 . 881 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 882 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 883 August 2009, . 885 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 886 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 887 August 2009, . 889 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 890 Code: The Implementation Status Section", BCP 205, 891 RFC 7942, DOI 10.17487/RFC7942, July 2016, 892 . 894 [W3C.REC-xml-20040204] 895 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 896 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 897 Edition)", World Wide Web Consortium FirstEdition REC-xml- 898 20040204", February 2004, 899 . 901 [W3C.REC-xmlschema-1-20041028] 902 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 903 ""XML Schema Part 1: Structures Second Edition", World 904 Wide Web Consortium Recommendation REC-xmlschema- 905 1-20041028", October 2004, 906 . 908 [W3C.REC-xmlschema-2-20041028] 909 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 910 Second Edition", World Wide Web Consortium Recommendation 911 REC-xmlschema-2-20041028", October 2004, 912 . 914 11.2. Informative References 916 [ID.draft-ietf-regext-org] 917 Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, 918 "Extensible Provisioning Protocol (EPP) Reseller Mapping", 919 Apr 2018, 920 . 922 [ID.draft-ietf-regext-reseller-ext] 923 Zhou, L., Kong, N., Wei, J., Lee, X., and J. Gould, 924 "Extensible Provisioning Protocol (EPP) Reseller Mapping", 925 Dec 2016, . 928 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 929 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 930 February 2015, . 932 Appendix A. Change Log 934 Initial -00: Individual document submitted. 936 -01: 938 * Updated abstract and introduction. 940 * Revised typos in info response. 942 * Added explanations on how to process reseller extension after 943 successful transfer operation. 945 * Modified explanation. 947 * Deleted reseller name element in and 948 commands. 950 * Removed some inaccurate comments from xml schema. 952 * Modified the element name of reseller id and reseller name. 954 -02: 956 * Changed author information. 958 * Updated xml typos to 959 in response. 961 -03: 963 * Changed author information. 965 * Updated section 3.1. 967 * Removed reseller name element in response. 969 * Added acknowledgment. 971 * Revised the typo "resellerr" to "resellerext". 973 WG document-00: WG document submitted 975 WG document-01: Keep document alive for further discussion. The 976 requirement of reseller information is clear for both registrar 977 and registry. What we should reach a consensus is whether the 978 extension should support only a name or ID and name. 980 Organization WG document-00: Change to a generic organization object 981 extension. 983 Organization WG document-01: Added "Implementation Status" section. 985 Organization WG document-02: Accepted some of the feedbacks on the 986 mailing list. Modified the examples in the document. 988 Organization WG document-03: 990 * Updated typos. 992 * Changed some descriptions about and role attribute. 994 * Modified the example of "domain with no organization". 996 * Updated section 8, adding implementation status of Verisign. 998 Organization WG document-04: 1000 * Updated typos. 1002 * Removed the example of command, domain with no 1003 organization. 1005 * Updated references. 1007 * Updated section 8 of implementation status. 1009 Authors' Addresses 1011 Linlin Zhou 1012 CNNIC 1013 4 South 4th Street, Zhongguancun, Haidian District 1014 Beijing, Beijing 100190 1015 China 1017 Phone: +86 10 5881 2677 1018 Email: zhoulinlin@cnnic.cn 1019 Ning Kong 1020 CNNIC 1021 4 South 4th Street, Zhongguancun, Haidian District 1022 Beijing, Beijing 100190 1023 China 1025 Phone: +86 10 5881 3147 1026 Email: nkong@cnnic.cn 1028 Junkai Wei 1029 CNNIC 1030 4 South 4th Street, Zhongguancun, Haidian District 1031 Beijing, Beijing 100190 1032 China 1034 Phone: +86 10 5881 3494 1035 Email: weijunkai@cnnic.cn 1037 Xiaodong Lee 1038 CNNIC 1039 4 South 4th Street, Zhongguancun, Haidian District 1040 Beijing, Beijing 100190 1041 China 1043 Phone: +86 10 5881 3020 1044 Email: xl@cnnic.cn 1046 James Gould 1047 Verisign, Inc. 1048 12061 Bluemont Way 1049 Reston, VA 20190 1050 US 1052 Email: jgould@verisign.com