idnits 2.17.1 draft-ietf-regext-org-ext-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 (February 28, 2018) is 2249 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) ** Obsolete normative reference: RFC 6982 (Obsoleted by RFC 7942) ** Downref: Normative reference to an Informational RFC: RFC 7451 Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force L. Zhou 3 Internet-Draft N. Kong 4 Intended status: Standards Track J. Wei 5 Expires: September 1, 2018 X. Lee 6 CNNIC 7 J. Gould 8 VeriSign, Inc. 9 February 28, 2018 11 Organization Extension for the Extensible Provisioning Protocol (EPP) 12 draft-ietf-regext-org-ext-02 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 September 1, 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 . . . . . . . . . . . . . 18 84 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 85 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 18 86 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 18 87 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 88 8.1. CNNIC Implementation . . . . . . . . . . . . . . . . . . 19 89 8.2. Reseller Extension . . . . . . . . . . . . . . . . . . . 20 90 9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 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 the EPP domain name 152 mapping [RFC5731]. Only the new elements are 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 Example command: 192 C: 193 C: 194 C: 195 C: 196 C: 198 C: example.com 199 C: 200 C: fooBAR 201 C: 202 C: 203 C: 204 C: ngcl-mIFICBNP 205 C: 206 C: 208 When an command has been processed successfully, the EPP 209 element MUST contain child elements as described in the EPP 210 object extensions. In addition, the EPP element SHOULD 211 contain a child element that identifies the 212 extension namespace if the object has data associated with this 213 extension and based on its server policy. The 214 element contains the following child elements: 216 o One or more elements are allowed that contains the 217 identifier of the organization. An attribute "role" associated 218 with is used to represent the relationship an 219 organization would have. See Section 7.3 in 220 [ID.draft-ietf-regext-org] for a list of values. 222 Example response for an authorized client with multiple 223 organizations: 225 S: 226 S: 227 S: 228 S: 229 S: Command completed successfully 230 S: 231 S: 232 S: 234 S: example.com 235 S: EXAMPLE1-REP 236 S: 237 S: jd1234 238 S: sh8013 239 S: sh8013 240 S: sh8013 241 S: 242 S: ns1.example.com 243 S: 244 S: ClientX 245 S: ClientY 246 S: 2015-02-06T04:01:21.0Z 247 S: 2018-02-06T04:01:21.0Z 248 S: 249 S: 2fooBAR 250 S: 251 S: 252 S: 253 S: 254 S: 256 S: myreseller 257 S: myproxy 258 S: 259 S: 260 S: 261 S: ngcl-IvJjzMZc 262 S: test142AWQONJZ 263 S: 264 S: 265 S: 267 Example response for an authorized client with no 268 organization: 270 S: 271 S: 272 S: 273 S: 274 S: Command completed successfully 275 S: 276 S: 277 S: 279 S: example.com 280 S: EXAMPLE1-REP 281 S: 282 S: jd1234 283 S: sh8013 284 S: sh8013 285 S: sh8013 286 S: 287 S: ns1.example.com 288 S: 289 S: ClientX 290 S: ClientY 291 S: 2015-02-06T04:01:21.0Z 292 S: 2018-02-06T04:01:21.0Z 293 S: 294 S: 2fooBAR 295 S: 296 S: 297 S: 298 S: 299 S: 301 S: 302 S: 303 S: ngcl-IvJjzMZc 304 S: test142AWQONJZ 305 S: 306 S: 307 S: 309 An EPP error response MUST be returned if an command cannot be 310 processed for any reason. 312 4.1.3. EPP Command 314 This extension does not add any elements to the EPP 315 command or response described in the EPP domain name 316 mapping [RFC5731], host mapping [RFC5732] and contact mapping 317 [RFC5733]. 319 4.2. EPP Transform Commands 321 EPP provides five commands to transform domain objects: to 322 create an instance of a domain object, to delete an instance 323 of a domain object, to extend the validity period of a domain 324 object, to manage domain object sponsorship changes, and 325 to change information associated with a domain object. 327 4.2.1. EPP Command 329 This extension defines additional elements for the EPP 330 command described in the EPP object extensions. No additional 331 elements are defined for the EPP response. 333 The EPP command provides a transform operation that allows a 334 client to create an object. In addition to the EPP command elements 335 described in the EPP object extensions, the command MUST contain an 336 element, and the element MUST contain a child 337 element that identifies the extension namespace if 338 the client wants to associate data defined in this extension to the 339 object. The element contains the following child 340 elements: 342 o A element that contains the identifier of the 343 organization. An attribute "role" associated with is 344 used to represent the relationship an organization would have. 345 See Section 7.3 in [ID.draft-ietf-regext-org] for a list of 346 values. 348 Example Command with only one organization: 350 C: 351 C: 352 C: 353 C: 354 C: 356 C: example.com 357 C: 3 358 C: 359 C: ns1.example.com 360 C: 361 C: jd1234 362 C: sh8013 363 C: sh8013 364 C: sh8013 365 C: 366 C: fooBAR 367 C: 368 C: 369 C: 370 C: 371 C: 373 C: myreseller 374 C: 375 C: 376 C: ABC-12345 377 C: 378 C: 380 Example Command with multiple organizations: 382 C: 383 C: 384 C: 385 C: 386 C: 388 C: example.com 389 C: 3 390 C: 391 C: ns1.example.com 392 C: 393 C: jd1234 394 C: sh8013 395 C: sh8013 396 C: sh8013 397 C: 398 C: fooBAR 399 C: 400 C: 401 C: 402 C: 403 C: 405 C: myreseller 406 C: myproxy 407 C: 408 C: 409 C: ABC-12345 410 C: 411 C: 413 When a command has been processed successfully, the EPP 414 response is as described in the EPP object extension. 416 An EPP error response MUST be returned if a command cannot 417 be processed for any reason. 419 4.2.2. EPP Command 421 This extension does not add any elements to the EPP command 422 or response described in the EPP domain mapping [RFC5731], 423 host mapping [RFC5732] and contact mapping [RFC5733]. 425 4.2.3. EPP Command 427 This extension does not add any elements to the EPP command 428 or response described in the EPP domain mapping [RFC5731], 429 host mapping [RFC5732] and contact mapping [RFC5733]. 431 4.2.4. EPP Command 433 This extension does not add any elements to the EPP 434 command or response described in the EPP domain mapping 435 [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733], but 436 after a successful transfer of an object with an assigned 437 organization, the handling of the assigned organization is dependent 438 on the organization roles and server policy. 440 4.2.5. EPP Command 442 This extension defines additional elements for the EPP 443 command described in the EPP domain mapping [RFC5731], host mapping 444 [RFC5732] and contact mapping [RFC5733]. No additional elements are 445 defined for the EPP response. 447 The EPP command provides a transform operation that allows a 448 client to modify the attributes of a domain object. In addition to 449 the EPP command elements described in the EPP domain mapping, the 450 command MUST contain an element, and the 451 element MUST contain a child element that identifies 452 the extension namespace if the client wants to update the domain 453 object with data defined in this extension. The 454 element contains the following child elements: 456 o An OPTIONAL element that contains attribute values to 457 be added to the object. 459 o An OPTIONAL element that contains attribute values to 460 be removed from the object. 462 o An OPTIONAL element that contains attribute values to 463 be changed. 465 At least one and only one , or 466 element MUST be provided. The , and 467 elements contain the following child element: 469 o A element that contains the identifier of the 470 organization. An attribute "role" associated with is 471 used to represent the relationship an organization would have. 472 See Section 7.3 in [ID.draft-ietf-regext-org] for a list of 473 values. 475 Example command, adding a reseller: 477 C: 478 C: 479 C: 480 C: 481 C: 483 C: example.com 484 C: 485 C: 486 C: 487 C: 489 C: 490 C: myreseller 491 C: 492 C: 493 C: 494 C: ABC-12345 495 C: 496 C: 498 Example command, adding multiple organizations: 500 C: 501 C: 502 C: 503 C: 504 C: 506 C: example.com 507 C: 508 C: 509 C: 510 C: 512 C: 513 C: myreseller 514 C: myproxy 515 C: 516 C: 517 C: 518 C: ABC-12345 519 C: 520 C: 522 Example command, domain with no organization: 524 C: 525 C: 526 C: 527 C: 528 C: 530 C: example.com 531 C: 532 C: 533 C: 534 C: 536 C: 537 C: myreseller 538 C: myproxy 539 C: 540 C: 541 C: 542 C: ABC-12345 543 C: 544 C: 546 Example command, removing a reseller: 548 C: 549 C: 550 C: 551 C: 552 C: 554 C: example.com 555 C: 556 C: 557 C: 558 C: 560 C: 561 C: 562 C: 563 C: 564 C: 565 C: ABC-12345 566 C: 567 C: 569 Example command, removing multiple organizations: 571 C: 572 C: 573 C: 574 C: 575 C: 577 C: example.com 578 C: 579 C: 580 C: 581 C: 583 C: 584 C: 585 C: 586 C: 587 C: 588 C: 589 C: ABC-12345 590 C: 591 C: 593 Example command, updating reseller identifier: 595 C: 596 C: 597 C: 598 C: 599 C: 601 C: example.com 602 C: 603 C: 604 C: 605 C: 607 C: 608 C: myreseller 609 C: 610 C: 611 C: 612 C: ABC-12345 613 C: 614 C: 616 Example command, updating multiple organization identifiers: 618 C: 619 C: 620 C: 621 C: 622 C: 624 C: example.com 625 C: 626 C: 627 C: 628 C: 630 C: 631 C: myreseller 632 C: myproxy 633 C: 634 C: 635 C: 636 C: ABC-12345 637 C: 638 C: 640 When an extended command has been processed successfully, 641 the EPP response is as described in the EPP object extension. 643 5. Formal Syntax 645 An EPP object mapping is specified in XML Schema notation. The 646 formal syntax presented here is a complete schema representation of 647 the object mapping suitable for automated validation of EPP XML 648 instances. The BEGIN and END tags are not part of the schema; they 649 are used to note the beginning and ending of the schema for URI 650 registration purposes. 652 BEGIN 653 655 662 663 664 Extensible Provisioning Protocol v1.0 665 Organization Extension Schema v1.0 666 667 669 670 673 677 680 681 682 683 687 688 689 691 695 696 697 699 703 704 706 709 710 711 715 719 723 724 726 727 728 730 735 736 738 739 743 744 745 746 748 753 754 756 757 758 END 760 6. Internationalization Considerations 762 EPP is represented in XML, which provides native support for encoding 763 information using the Unicode character set and its more compact 764 representations including UTF-8. Conformant XML processors recognize 765 both UTF-8 and UTF-16. Though XML includes provisions to identify 766 and use other character encodings through use of an "encoding" 767 attribute in an declaration, use of UTF-8 is RECOMMENDED. 769 As an extension of the EPP domain name mapping, the elements, element 770 content described in this document MUST inherit the 771 internationalization conventions used to represent higher-layer 772 domain and core protocol structures present in an XML instance that 773 includes this extension. 775 7. IANA Considerations 777 7.1. XML Namespace 779 This document uses URNs to describe XML namespaces and XML schemas 780 conforming to a registry mechanism described in [RFC3688]. IANA is 781 requested to assignment the following URI. 783 Registration request for the organization namespace: 785 o URI: urn:ietf:params:xml:ns:orgext-1.0 787 o Registrant Contact: See the "Author's Address" section of this 788 document. 790 o XML: See the "Formal Syntax" section of this document. 792 7.2. EPP Extension Registry 794 The EPP extension described in this document should be registered by 795 the IANA in the EPP Extension Registry described in [RFC7451]. The 796 details of the registration are as follows: 798 Name of Extension: Organization Extension 800 Document status: Standards Track 802 Reference: (insert reference to RFC version of this document) 804 Registrant Name and Email Address: See the "Author's Address" section 805 of this document. 807 TLDs: any 808 IPR Disclosure: none 810 Status: active 812 Notes: none 814 8. Implementation Status 816 Note to RFC Editor: Please remove this section and the reference to 817 [RFC6982] before publication. This section records the status of 818 known implementations of the protocol defined by this specification 819 at the time of posting of this Internet-Draft, and is based on a 820 proposal described in [RFC6982]. The description of implementations 821 in this section is intended to assist the IETF in its decision 822 processes in progressing drafts to RFCs. Please note that the 823 listing of any individual implementation here does not imply 824 endorsement by the IETF. Furthermore, no effort has been spent to 825 verify the information presented here that was supplied by IETF 826 contributors. This is not intended as, and must not be construed to 827 be, a catalog of available implementations or their features. 828 Readers are advised to note that other implementations may exist. 830 According to [RFC6982], "this will allow reviewers and working groups 831 to assign due consideration to documents that have the benefit of 832 running code, which may serve as evidence of valuable experimentation 833 and feedback that have made the implemented protocols more mature. 834 It is up to the individual working groups to use this information as 835 they see fit". 837 CNNIC is in the process of development research to update 838 organization extension from reseller extension. Verisign is also 839 planning to implement this extension. 841 8.1. CNNIC Implementation 843 Organization: CNNIC 845 Name: Organization Extension for EPP 847 Description: CNNIC is trying to update organization extension from 848 previous reseller extension according to this document. 850 Level of maturity: Research. 852 Coverage: Organization extension for EPP. 854 Contact: zhouguiqing@cnnic.cn 856 8.2. Reseller Extension 858 This document was updated from draft-ietf-regext-reseller-ext. 859 CNNIC, Verisign and Net::DRI (Patrick Mevzek) have already 860 implemented this extension. 862 9. Security Considerations 864 The object mapping extension described in this document does not 865 provide any other security services or introduce any additional 866 considerations beyond those described by [RFC5730], [RFC5731], 867 [RFC5732] and [RFC5733] or those caused by the protocol layers used 868 by EPP. 870 10. Acknowledgment 872 The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick 873 Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful 874 review and valuable comments. 876 11. References 878 11.1. Normative References 880 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 881 Requirement Levels", BCP 14, RFC 2119, 882 DOI 10.17487/RFC2119, March 1997, 883 . 885 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 886 DOI 10.17487/RFC3688, January 2004, 887 . 889 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 890 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 891 . 893 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 894 Domain Name Mapping", STD 69, RFC 5731, 895 DOI 10.17487/RFC5731, August 2009, 896 . 898 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 899 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 900 August 2009, . 902 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 903 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 904 August 2009, . 906 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 907 Code: The Implementation Status Section", RFC 6982, 908 DOI 10.17487/RFC6982, July 2013, 909 . 911 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 912 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 913 February 2015, . 915 [W3C.REC-xml-20040204] 916 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 917 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 918 Edition)", World Wide Web Consortium FirstEdition REC-xml- 919 20040204", February 2004, 920 . 922 [W3C.REC-xmlschema-1-20041028] 923 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 924 ""XML Schema Part 1: Structures Second Edition", World 925 Wide Web Consortium Recommendation REC-xmlschema- 926 1-20041028", October 2004, 927 . 929 [W3C.REC-xmlschema-2-20041028] 930 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 931 Second Edition", World Wide Web Consortium Recommendation 932 REC-xmlschema-2-20041028", October 2004, 933 . 935 11.2. Informative References 937 [ID.draft-ietf-regext-org] 938 Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, 939 "Extensible Provisioning Protocol (EPP) Reseller Mapping", 940 Feb 2018, 941 . 943 Appendix A. Change Log 945 Initial -00: Individual document submitted. 947 -01: 949 * Updated abstract and introduction. 951 * Revised typos in info response. 953 * Added explanations on how to process reseller extension after 954 successful transfer operation. 956 * Modified explanation. 958 * Deleted reseller name element in and 959 commands. 961 * Removed some inaccurate comments from xml schema. 963 * Modified the element name of reseller id and reseller name. 965 -02: 967 * Changed author information. 969 * Updated xml typos to 970 in response. 972 -03: 974 * Changed author information. 976 * Updated section 3.1. 978 * Removed reseller name element in response. 980 * Added acknowledgment. 982 * Revised the typo "resellerr" to "resellerext". 984 WG document-00: WG document submitted 986 WG document-01: Keep document alive for further discussion. The 987 requirement of reseller information is clear for both registrar 988 and registry. What we should reach a consensus is whether the 989 extension should support only a name or ID and name. 991 Organization WG document-00: Change to a generic organization object 992 extension. 994 Organization WG document-01: Added "Implementation Status" section. 996 Organization WG document-02: Accepted some of the feedbacks on the 997 mailing list. Modified the examples in the document. 999 Authors' Addresses 1001 Linlin Zhou 1002 CNNIC 1003 4 South 4th Street, Zhongguancun, Haidian District 1004 Beijing, Beijing 100190 1005 China 1007 Phone: +86 10 5881 2677 1008 Email: zhoulinlin@cnnic.cn 1010 Ning Kong 1011 CNNIC 1012 4 South 4th Street, Zhongguancun, Haidian District 1013 Beijing, Beijing 100190 1014 China 1016 Phone: +86 10 5881 3147 1017 Email: nkong@cnnic.cn 1019 Junkai Wei 1020 CNNIC 1021 4 South 4th Street, Zhongguancun, Haidian District 1022 Beijing, Beijing 100190 1023 China 1025 Phone: +86 10 5881 3494 1026 Email: weijunkai@cnnic.cn 1028 Xiaodong Lee 1029 CNNIC 1030 4 South 4th Street, Zhongguancun, Haidian District 1031 Beijing, Beijing 100190 1032 China 1034 Phone: +86 10 5881 3020 1035 Email: xl@cnnic.cn 1036 James Gould 1037 VeriSign, Inc. 1038 12061 Bluemont Way 1039 Reston, VA 20190 1040 US 1042 Email: jgould@verisign.com