idnits 2.17.1 draft-ietf-regext-org-ext-10.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 lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (November 30, 2018) is 1973 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 CNNIC 4 Intended status: Standards Track N. Kong 5 Expires: June 3, 2019 Consultant 6 J. Wei 7 J. Yao 8 CNNIC 9 J. Gould 10 Verisign, Inc. 11 November 30, 2018 13 Organization Extension for the Extensible Provisioning Protocol (EPP) 14 draft-ietf-regext-org-ext-10 16 Abstract 18 This document describes an extension to Extensible Provisioning 19 Protocol (EPP) object mappings, which is designed to support 20 assigning an organization to any existing object (domain, host, 21 contact) as well as any future objects. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on June 3, 2019. 40 Copyright Notice 42 Copyright (c) 2018 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 59 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 60 3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4 61 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 62 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 4 63 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 64 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 4 65 4.1.3. EPP Query Command . . . . . . . . . . . . 7 66 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 67 4.2.1. EPP Command . . . . . . . . . . . . . . . . 8 68 4.2.2. EPP Command . . . . . . . . . . . . . . . . 10 69 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 10 70 4.2.4. EPP Command . . . . . . . . . . . . . . . 11 71 4.2.5. EPP Command . . . . . . . . . . . . . . . . 11 72 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 15 73 6. Internationalization Considerations . . . . . . . . . . . . . 18 74 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 75 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18 76 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 77 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 78 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 19 79 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 20 80 9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 81 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 20 82 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 83 11.1. Normative References . . . . . . . . . . . . . . . . . . 20 84 11.2. Informative References . . . . . . . . . . . . . . . . . 22 85 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 22 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 88 1. Introduction 90 In the business model of domain registration, we usually have three 91 roles of entities: a registrant, a registrar and a registry. There 92 may be other roles of entities involved in the domain registration 93 process which are not formally defined yet, such as resellers, DNS 94 service operators, privacy proxies, etc. 96 A domain reseller is an individual or a company that acts as an agent 97 for accredited registrars. A third-party DNS service operator is 98 responsible for a zone where the operator is neither the registrant 99 nor the registrar of record for the delegation. A privacy proxy is 100 an entity used for domain registrations to protect the private 101 information of the individuals and organizations. These kind of 102 entities are defined as "organizations" with different role types in 103 this document. 105 In order to facilitate provisioning and management of organization 106 information in a shared central repository, this document proposes an 107 organization extension mapping for any Extensible Provisioning 108 Protocol (EPP) object like domain names in [RFC5731], hosts in 109 [RFC5732] and contacts in [RFC5733]. The examples provided in this 110 document are used for the domain object for illustration purpose. 111 The host and contact object could be extended in the same way with 112 the domain object. 114 Organization object identifiers defined in [ID.draft-ietf-regext-org] 115 MUST be known to the server before the organization object can be 116 associated with the EPP object. 118 This document is specified using the XML 1.0 as described in 119 [W3C.REC-xml-20040204] and XML Schema notation as described in 120 [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. 122 2. Conventions Used in This Document 124 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 125 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 126 document are to be interpreted as described in BCP 14 127 [RFC2119][RFC8174] when, and only when, they appear in all capitals, 128 as shown here. 130 In examples, "C:" represents lines sent by a protocol client and "S:" 131 represents lines returned by a protocol server. Indentation and 132 white space in examples are provided only to illustrate element 133 relationships and are not a required feature of this specification. 135 XML is case sensitive. Unless stated otherwise, XML specifications 136 and examples provided in this document MUST be interpreted in the 137 character case. 139 The XML namespace prefix "orgext" is used for the namespace 140 "urn:ietf:params:xml:ns:epp:orgext-1.0", but implementations MUST NOT 141 depend on it and instead employ a proper namespace-aware XML parser 142 and serializer to interpret and output the XML documents. 144 3. Object Attributes 146 This extension adds additional elements to EPP object mappings like 147 the EPP domain name mapping [RFC5731]. Only the new elements are 148 described here. 150 3.1. Organization Identifier 152 Organization identifier provides the ID of an organization. Its 153 corresponding element is which refers to the 154 element defined in [ID.draft-ietf-regext-org]. All organization 155 objects are identified by a server-unique identifier. A "role" 156 attribute is used to represent the relationship that the organization 157 has to the EPP object. Any given object MUST have at most one 158 associated organization ID for any given role value. 160 4. EPP Command Mapping 162 A detailed description of the EPP syntax and semantics can be found 163 in the EPP core protocol specification [RFC5730]. The command 164 mappings described here are specifically for assigning organizations 165 to EPP objects. 167 4.1. EPP Query Commands 169 EPP provides three commands to retrieve EPP object information: 170 to determine if an object can be provisioned within a 171 repository, to retrieve detailed information associated with 172 an object, and to retrieve object transfer status 173 information. 175 4.1.1. EPP Command 177 This extension does not add any elements to the EPP command 178 or response described in the EPP object mapping. 180 4.1.2. EPP Command 182 This extension does not add any elements to the EPP command 183 described in the EPP object mapping. However, additional elements 184 are defined for the response in the EPP object mapping. 186 When an command has been processed successfully, the EPP 187 element MUST contain child elements as described in the EPP 188 object extensions. In addition, the EPP element SHOULD 189 contain a child element. This element or its 190 ancestor element MUST identify the extension namespace 191 "urn:ietf:params:xml:ns:epp:orgext-1.0" if the object has data 192 associated with this extension and based on server policy. The 193 element contains the following child elements: 195 o Zero or more elements are allowed that contain the 196 identifier of the organization, as defined in Section 3.1. The 197 "role" attribute is used to represent the relationship that the 198 organization has to the object. See Section 7.3 in 199 [ID.draft-ietf-regext-org] for a list of values. 201 Example response for an authorized client with multiple 202 organizations: 204 S: 205 S: 206 S: 207 S: 208 S: Command completed successfully 209 S: 210 S: 211 S: 213 S: example.com 214 S: EXAMPLE1-REP 215 S: 216 S: jd1234 217 S: sh8013 218 S: sh8013 219 S: sh8013 220 S: 221 S: ns1.example.com 222 S: 223 S: ClientX 224 S: ClientY 225 S: 2015-02-06T04:01:21.0Z 226 S: 2018-02-06T04:01:21.0Z 227 S: 228 S: 2fooBAR 229 S: 230 S: 231 S: 232 S: 233 S: 235 S: reseller1523 236 S: proxy2935 237 S: 238 S: 239 S: 240 S: ngcl-IvJjzMZc 241 S: test142AWQONJZ 242 S: 243 S: 244 S: 246 Example response for an authorized client with no 247 organization: 249 S: 250 S: 251 S: 252 S: 253 S: Command completed successfully 254 S: 255 S: 256 S: 258 S: example.com 259 S: EXAMPLE1-REP 260 S: 261 S: jd1234 262 S: sh8013 263 S: sh8013 264 S: sh8013 265 S: 266 S: ns1.example.com 267 S: 268 S: ClientX 269 S: ClientY 270 S: 2015-02-06T04:01:21.0Z 271 S: 2018-02-06T04:01:21.0Z 272 S: 273 S: 2fooBAR 274 S: 275 S: 276 S: 277 S: 278 S: 280 S: 281 S: 282 S: ngcl-IvJjzMZc 283 S: test142AWQONJZ 284 S: 285 S: 286 S: 288 An EPP error response MUST be returned if an command cannot be 289 processed for any reason. 291 4.1.3. EPP Query Command 293 This extension does not add any elements to the EPP query 294 command or query response described in the EPP object 295 mapping. 297 4.2. EPP Transform Commands 299 EPP provides five commands to transform EPP objects: to 300 create an instance of an object, to delete an instance of an 301 object, to extend the validity period of an object, 302 to manage the object sponsorship changes, and to 303 change information associated with an object. 305 4.2.1. EPP Command 307 This extension defines additional elements for the EPP 308 command described in the EPP object extensions. No additional 309 elements are defined for the EPP response. 311 The EPP command provides a transform operation that allows a 312 client to create an object. In addition to the EPP command elements 313 described in the EPP object extensions, the command MUST contain an 314 element, and the element MUST contain a child 315 element. This element or its ancestor element MUST 316 identify the extension namespace "urn:ietf:params:xml:ns:epp:orgext- 317 1.0" if the client wants to associate data defined in this extension 318 to the object. The element contains the following 319 child elements: 321 o One or more elements that contain the identifier of 322 the organization, as defined in Section 3.1. The "role" attribute 323 is used to represent the relationship that the organization has to 324 the object. See Section 7.3 in [ID.draft-ietf-regext-org] for a 325 list of values. 327 Example Command with only one organization: 329 C: 330 C: 331 C: 332 C: 333 C: 335 C: example.com 336 C: 3 337 C: 338 C: ns1.example.com 339 C: 340 C: jd1234 341 C: sh8013 342 C: sh8013 343 C: sh8013 344 C: 345 C: fooBAR 346 C: 347 C: 348 C: 349 C: 350 C: 352 C: reseller1523 353 C: 354 C: 355 C: ABC-12345 356 C: 357 C: 359 Example Command with multiple organizations: 361 C: 362 C: 363 C: 364 C: 365 C: 367 C: example.com 368 C: 3 369 C: 370 C: ns1.example.com 371 C: 372 C: jd1234 373 C: sh8013 374 C: sh8013 375 C: sh8013 376 C: 377 C: fooBAR 378 C: 379 C: 380 C: 381 C: 382 C: 384 C: reseller1523 385 C: proxy2935 386 C: 387 C: 388 C: ABC-12345 389 C: 390 C: 392 When a command has been processed successfully, the EPP 393 response is as described in the EPP object extension. 395 An EPP error response MUST be returned if a command cannot 396 be processed for any reason. 398 4.2.2. EPP Command 400 This extension does not add any elements to the EPP command 401 or response described in the EPP object mapping. 403 4.2.3. EPP Command 405 This extension does not add any elements to the EPP command 406 or response described in the EPP object mapping. 408 4.2.4. EPP Command 410 This extension does not add any elements to the EPP 411 command or response described in the EPP object mapping, 412 but after a successful transfer of an object with an assigned 413 organization, the handling of the assigned organization is dependent 414 on the organization roles and server policy. 416 4.2.5. EPP Command 418 This extension defines additional elements for the EPP 419 command described in the EPP domain mapping [RFC5731], host mapping 420 [RFC5732] and contact mapping [RFC5733]. No additional elements are 421 defined for the EPP response. 423 The EPP command provides a transform operation that allows a 424 client to modify the attributes of an object. In addition to the EPP 425 command elements, the command MUST contain an 426 element, and the element MUST contain a child 427 element. This element or its ancestor element MUST 428 identify the extension namespace "urn:ietf:params:xml:ns:epp:orgext- 429 1.0" if the client wants to update the object with data defined in 430 this extension. The element contains the following 431 child elements: 433 o An OPTIONAL element that contains one or more 434 elements, as defined in Section 3.1, that add non- 435 existent organization roles to the object. The 436 element MUST have a non-empty organization identifier value. The 437 server SHOULD validate that the element role does not 438 exist. 440 o An OPTIONAL element that contains one or more 441 elements, as defined in Section 3.1, that remove 442 organization roles from the object. The element MAY 443 have an empty organization identifier value. The server SHOULD 444 validate the existence of the element role and the 445 organization identifier if provided. 447 o An OPTIONAL element that contains one or more 448 elements, as defined in Section 3.1, that change 449 organization role identifiers for the object. The existing 450 organization identifier value will be replaced for the defined 451 role. The server SHOULD validate the existence of the 452 element role. 454 At least one , or element MUST 455 be provided. 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: reseller1523 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: reseller1523 496 C: proxy2935 497 C: 498 C: 499 C: 500 C: ABC-12345 501 C: 502 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: 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: reseller1523 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: reseller1523 588 C: proxy2935 589 C: 590 C: 591 C: 592 C: ABC-12345 593 C: 594 C: 595 When an extended command has been processed successfully, 596 the EPP response is as described in the EPP object extension. 598 An EPP error response MUST be returned if an command cannot 599 be processed for any reason. An attempt to add one organization ID 600 or multiple organization IDs with a particular role value when at 601 least one of them already exists does not change the object at all. 602 A server SHOULD notify clients that object relationships exist by 603 sending a 2305 error response code. An attempt to remove an 604 organization ID or multiple organization IDs with a particular role 605 value when at least one of them does not exist does not change the 606 object at all. A server SHOULD notify clients that object 607 relationships does not exist by sending a 2305 error response code. 608 An attempt to change an organization ID or multiple organization IDs 609 with a particular role value when at least one of them does not exist 610 does not change the object at all. A server SHOULD notify clients 611 that object relationships does not exist by sending a 2305 error 612 response code. Response format with error value elements is defined 613 in Section 2.6 of [RFC5730]. 615 5. Formal Syntax 617 An EPP object mapping is specified in XML Schema notation. The 618 formal syntax presented here is a complete schema representation of 619 the object mapping suitable for automated validation of EPP XML 620 instances. The BEGIN and END tags are not part of the schema; they 621 are used to note the beginning and ending of the schema for URI 622 registration purposes. 624 BEGIN 625 627 634 635 636 Extensible Provisioning Protocol v1.0 637 Organization Extension Schema v1.0 638 639 641 642 645 649 652 653 654 655 659 660 661 663 667 668 669 671 675 676 678 681 682 683 688 693 698 699 701 702 703 705 709 710 712 713 717 718 719 720 722 727 728 730 731 732 END 734 6. Internationalization Considerations 736 EPP is represented in XML, which provides native support for encoding 737 information using the Unicode character set and its more compact 738 representations including UTF-8. Conformant XML processors recognize 739 both UTF-8 and UTF-16. Though XML includes provisions to identify 740 and use other character encodings through use of an "encoding" 741 attribute in an declaration, use of UTF-8 is RECOMMENDED. 743 As an extension of the EPP object mapping, the elements, element 744 content described in this document MUST inherit the 745 internationalization conventions used to represent higher-layer 746 domain and core protocol structures present in an XML instance that 747 includes this extension. 749 7. IANA Considerations 751 7.1. XML Namespace 753 This document uses URNs to describe XML namespaces and XML schemas 754 conforming to a registry mechanism described in [RFC3688]. IANA is 755 requested to assignment the following URI. 757 Registration request for the organization extension namespace: 759 URI: urn:ietf:params:xml:ns:epp:orgext-1.0 761 Registrant Contact: IESG 763 XML: None. Namespace URIs do not represent an XML specification. 765 Registration request for the organization XML schema: 767 URI: urn:ietf:params:xml:schema:epp:orgext-1.0 769 Registrant Contact: IESG 771 XML: See the "Formal Syntax" section of this document. 773 7.2. EPP Extension Registry 775 The EPP extension described in this document should be registered by 776 the IANA in the EPP Extension Registry described in [RFC7451]. The 777 details of the registration are as follows: 779 Name of Extension: Organization Extension for the Extensible 780 Provisioning Protocol (EPP) 781 Document status: Standards Track 783 Reference: RFCXXXX (please replace "XXXX" with the RFC number for 784 this document after a number is assigned by the RFC Editor) 786 Registrant Name and Email Address: IESG, iesg@ietf.org 788 TLDs: Any 790 IPR Disclosure: None 792 Status: Active 794 Notes: None 796 8. Implementation Status 798 Note to RFC Editor: Please remove this section and the reference to 799 [RFC7942] before publication. This section records the status of 800 known implementations of the protocol defined by this specification 801 at the time of posting of this Internet-Draft, and is based on a 802 proposal described in [RFC7942]. The description of implementations 803 in this section is intended to assist the IETF in its decision 804 processes in progressing drafts to RFCs. Please note that the 805 listing of any individual implementation here does not imply 806 endorsement by the IETF. Furthermore, no effort has been spent to 807 verify the information presented here that was supplied by IETF 808 contributors. This is not intended as, and must not be construed to 809 be, a catalog of available implementations or their features. 810 Readers are advised to note that other implementations may exist. 812 According to [RFC7942], "this will allow reviewers and working groups 813 to assign due consideration to documents that have the benefit of 814 running code, which may serve as evidence of valuable experimentation 815 and feedback that have made the implemented protocols more mature. 816 It is up to the individual working groups to use this information as 817 they see fit". 819 8.1. Verisign EPP SDK 821 Organization: Verisign Inc. 823 Name: Verisign EPP SDK 825 Description: The Verisign EPP SDK includes both a full client 826 implementation and a full server stub implementation of draft-ietf- 827 regext-org-ext. 829 Level of maturity: Development 831 Coverage: All aspects of the protocol are implemented. 833 Licensing: GNU Lesser General Public License 835 Contact: jgould@verisign.com 837 URL: https://www.verisign.com/en_US/channel-resources/domain- 838 registry-products/epp-sdks 840 8.2. CNNIC Implementation 842 Organization: CNNIC 844 Name: Organization Extension for EPP 846 Description: CNNIC is trying to update organization extension from 847 previous reseller extension according to this document. 849 Level of maturity: Development 851 Coverage: Organization extension for EPP 853 Contact: zhouguiqing@cnnic.cn 855 9. Security Considerations 857 The object mapping extension described in this document does not 858 provide any other security services or introduce any additional 859 considerations beyond those described by [RFC5730], [RFC5731], 860 [RFC5732] and [RFC5733] or those caused by the protocol layers used 861 by EPP. 863 10. Acknowledgment 865 The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick 866 Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful 867 review and valuable comments. 869 11. References 871 11.1. Normative References 873 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 874 Requirement Levels", BCP 14, RFC 2119, 875 DOI 10.17487/RFC2119, March 1997, 876 . 878 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 879 DOI 10.17487/RFC3688, January 2004, 880 . 882 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 883 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 884 . 886 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 887 Domain Name Mapping", STD 69, RFC 5731, 888 DOI 10.17487/RFC5731, August 2009, 889 . 891 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 892 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 893 August 2009, . 895 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 896 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 897 August 2009, . 899 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 900 Code: The Implementation Status Section", BCP 205, 901 RFC 7942, DOI 10.17487/RFC7942, July 2016, 902 . 904 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 905 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 906 May 2017, . 908 [W3C.REC-xml-20040204] 909 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 910 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 911 Edition)", World Wide Web Consortium FirstEdition REC-xml- 912 20040204", February 2004, 913 . 915 [W3C.REC-xmlschema-1-20041028] 916 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 917 ""XML Schema Part 1: Structures Second Edition", World 918 Wide Web Consortium Recommendation REC-xmlschema- 919 1-20041028", October 2004, 920 . 922 [W3C.REC-xmlschema-2-20041028] 923 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 924 Second Edition", World Wide Web Consortium Recommendation 925 REC-xmlschema-2-20041028", October 2004, 926 . 928 11.2. Informative References 930 [ID.draft-ietf-regext-org] 931 Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, 932 "Extensible Provisioning Protocol (EPP) Reseller Mapping", 933 Apr 2018, 934 . 936 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 937 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 938 February 2015, . 940 Appendix A. Change Log 942 Initial -00: Individual document submitted. 944 -01: 946 * Updated abstract and introduction. 948 * Revised typos in info response. 950 * Added explanations on how to process reseller extension after 951 successful transfer operation. 953 * Modified explanation. 955 * Deleted reseller name element in and 956 commands. 958 * Removed some inaccurate comments from xml schema. 960 * Modified the element name of reseller id and reseller name. 962 -02: 964 * Changed author information. 966 * Updated xml typos to 967 in response. 969 -03: 971 * Changed author information. 973 * Updated section 3.1. 975 * Removed reseller name element in response. 977 * Added acknowledgment. 979 * Revised the typo "resellerr" to "resellerext". 981 WG document-00: WG document submitted 983 WG document-01: Keep document alive for further discussion. The 984 requirement of reseller information is clear for both registrar 985 and registry. What we should reach a consensus is whether the 986 extension should support only a name or ID and name. 988 Organization WG document-00: Change to a generic organization object 989 extension. 991 Organization WG document-01: Added "Implementation Status" section. 993 Organization WG document-02: Accepted some of the feedbacks on the 994 mailing list. Modified the examples in the document. 996 Organization WG document-03: 998 * Updated typos. 1000 * Changed some descriptions about and role attribute. 1002 * Modified the example of "domain with no organization". 1004 * Updated section 8, adding implementation status of Verisign. 1006 Organization WG document-04: 1008 * Updated typos. 1010 * Removed the example of command, domain with no 1011 organization. 1013 * Updated references. 1015 * Updated section 8 of implementation status. 1017 Organization WG document-05: 1019 * Removed the minOccurs="0" from the addRemChgType type of the 1020 XML schema 1022 * Removed the third paragraph of "Implementation Status". 1024 * Remove the Informative Reference to draft-ietf-regext-reseller- 1025 ext from the draft. 1027 Organization WG document-06: 1029 * Updated "Abstraction". 1031 * Added "Query" for " Query Command". 1033 * Change "Registrant Contact" to IESG in section 7.1. 1035 * Modified section 7.2. 1037 Organization WG document-07: 1039 * Updated "Abstraction". 1041 Organization WG document-08: 1043 * Updated error codes of response. 1045 * Modified XML namespace and schema. 1047 Organization WG document-09: 1049 * Modified XML namespace and schema. 1051 * Changed "Exactly one" to "At least one" in section 4.2.5. 1053 Organization WG document-10: 1055 * Updated the reseller id and dns proxy id in the document. 1057 * Updated the full xml namespace. 1059 * Updated the text of EPP , and 1060 . 1062 * Added "Document satus" and "Reference" in section "EPP 1063 Extension Registry". 1065 Authors' Addresses 1067 Linlin Zhou 1068 CNNIC 1069 4 South 4th Street, Zhongguancun, Haidian District 1070 Beijing, Beijing 100190 1071 China 1073 Email: zhoulinlin@cnnic.cn 1075 Ning Kong 1076 Consultant 1078 Email: ietfing@gmail.com 1080 Junkai Wei 1081 CNNIC 1082 4 South 4th Street, Zhongguancun, Haidian District 1083 Beijing, Beijing 100190 1084 China 1086 Email: weijunkai@cnnic.cn 1088 Jiankang Yao 1089 CNNIC 1090 4 South 4th Street, Zhongguancun, Haidian District 1091 Beijing, Beijing 100190 1092 China 1094 Email: yaojk@cnnic.cn 1096 James Gould 1097 Verisign, Inc. 1098 12061 Bluemont Way 1099 Reston, VA 20190 1100 US 1102 Email: jgould@verisign.com