idnits 2.17.1 draft-ietf-regext-org-ext-03.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 (April 27, 2018) is 2189 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: October 29, 2018 X. Lee 6 CNNIC 7 J. Gould 8 VeriSign, Inc. 9 April 27, 2018 11 Organization Extension for the Extensible Provisioning Protocol (EPP) 12 draft-ietf-regext-org-ext-03 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 October 29, 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 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 Command 296 This extension does not add any elements to the EPP 297 command or 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 element 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 element 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, domain with no organization: 504 505 506 507 508 510 example.com 511 512 513 514 516 517 518 519 ABC-12345 520 521 522 C: 524 Example command, removing a reseller: 526 C: 527 C: 528 C: 529 C: 530 C: 532 C: example.com 533 C: 534 C: 535 C: 536 C: 538 C: 539 C: 540 C: 541 C: 542 C: 543 C: ABC-12345 544 C: 545 C: 547 Example command, removing multiple organizations: 549 C: 550 C: 551 C: 552 C: 553 C: 555 C: example.com 556 C: 557 C: 558 C: 559 C: 561 C: 562 C: 563 C: 564 C: 565 C: 566 C: 567 C: ABC-12345 568 C: 569 C: 571 Example command, updating reseller identifier: 573 C: 574 C: 575 C: 576 C: 577 C: 579 C: example.com 580 C: 581 C: 582 C: 583 C: 585 C: 586 C: myreseller 587 C: 588 C: 589 C: 590 C: ABC-12345 591 C: 592 C: 594 Example command, updating multiple organization identifiers: 596 C: 597 C: 598 C: 599 C: 600 C: 602 C: example.com 603 C: 604 C: 605 C: 606 C: 608 C: 609 C: myreseller 610 C: myproxy 611 C: 612 C: 613 C: 614 C: ABC-12345 615 C: 616 C: 618 When an extended command has been processed successfully, 619 the EPP response is as described in the EPP object extension. 621 5. Formal Syntax 623 An EPP object mapping is specified in XML Schema notation. The 624 formal syntax presented here is a complete schema representation of 625 the object mapping suitable for automated validation of EPP XML 626 instances. The BEGIN and END tags are not part of the schema; they 627 are used to note the beginning and ending of the schema for URI 628 registration purposes. 630 BEGIN 631 633 640 641 642 Extensible Provisioning Protocol v1.0 643 Organization Extension Schema v1.0 644 645 647 648 651 655 658 659 660 661 665 666 667 669 673 674 675 677 681 682 684 687 688 689 693 697 701 702 704 705 706 708 712 713 715 716 720 721 722 723 725 730 731 733 734 735 END 737 6. Internationalization Considerations 739 EPP is represented in XML, which provides native support for encoding 740 information using the Unicode character set and its more compact 741 representations including UTF-8. Conformant XML processors recognize 742 both UTF-8 and UTF-16. Though XML includes provisions to identify 743 and use other character encodings through use of an "encoding" 744 attribute in an declaration, use of UTF-8 is RECOMMENDED. 746 As an extension of the EPP domain name mapping, the elements, element 747 content described in this document MUST inherit the 748 internationalization conventions used to represent higher-layer 749 domain and core protocol structures present in an XML instance that 750 includes this extension. 752 7. IANA Considerations 754 7.1. XML Namespace 756 This document uses URNs to describe XML namespaces and XML schemas 757 conforming to a registry mechanism described in [RFC3688]. IANA is 758 requested to assignment the following URI. 760 Registration request for the organization namespace: 762 o URI: urn:ietf:params:xml:ns:orgext-1.0 764 o Registrant Contact: See the "Author's Address" section of this 765 document. 767 o XML: See the "Formal Syntax" section of this document. 769 7.2. EPP Extension Registry 771 The EPP extension described in this document should be registered by 772 the IANA in the EPP Extension Registry described in [RFC7451]. The 773 details of the registration are as follows: 775 Name of Extension: Organization Extension 777 Document status: Standards Track 779 Reference: (insert reference to RFC version of this document) 781 Registrant Name and Email Address: IESG 783 TLDs: any 784 IPR Disclosure: none 786 Status: active 788 Notes: none 790 8. Implementation Status 792 Note to RFC Editor: Please remove this section and the reference to 793 [RFC6982] before publication. This section records the status of 794 known implementations of the protocol defined by this specification 795 at the time of posting of this Internet-Draft, and is based on a 796 proposal described in [RFC6982]. The description of implementations 797 in this section is intended to assist the IETF in its decision 798 processes in progressing drafts to RFCs. Please note that the 799 listing of any individual implementation here does not imply 800 endorsement by the IETF. Furthermore, no effort has been spent to 801 verify the information presented here that was supplied by IETF 802 contributors. This is not intended as, and must not be construed to 803 be, a catalog of available implementations or their features. 804 Readers are advised to note that other implementations may exist. 806 According to [RFC6982], "this will allow reviewers and working groups 807 to assign due consideration to documents that have the benefit of 808 running code, which may serve as evidence of valuable experimentation 809 and feedback that have made the implemented protocols more mature. 810 It is up to the individual working groups to use this information as 811 they see fit". 813 VeriSign has already implemented this extension. CNNIC and Net::DRI 814 (Patrick Mevzek) are in the process of development research to update 815 organization extension from reseller extension. Dns Belgium is 816 planning to implement it after the publication of this document. 818 8.1. CNNIC Implementation 820 Organization: CNNIC 822 Name: Organization Extension for EPP 824 Description: CNNIC is trying to update organization extension from 825 previous reseller extension according to this document. 827 Level of maturity: Research. 829 Coverage: Organization extension for EPP. 831 Contact: zhouguiqing@cnnic.cn 833 8.2. Reseller Extension 835 This document was updated from draft-ietf-regext-reseller-ext. 836 CNNIC, VeriSign and Net::DRI (Patrick Mevzek) have already 837 implemented this extension. 839 9. Security Considerations 841 The object mapping extension described in this document does not 842 provide any other security services or introduce any additional 843 considerations beyond those described by [RFC5730], [RFC5731], 844 [RFC5732] and [RFC5733] or those caused by the protocol layers used 845 by EPP. 847 10. Acknowledgment 849 The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick 850 Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful 851 review and valuable comments. 853 11. References 855 11.1. Normative References 857 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 858 Requirement Levels", BCP 14, RFC 2119, 859 DOI 10.17487/RFC2119, March 1997, 860 . 862 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 863 DOI 10.17487/RFC3688, January 2004, 864 . 866 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 867 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 868 . 870 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 871 Domain Name Mapping", STD 69, RFC 5731, 872 DOI 10.17487/RFC5731, August 2009, 873 . 875 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 876 Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732, 877 August 2009, . 879 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 880 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 881 August 2009, . 883 [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 884 Code: The Implementation Status Section", RFC 6982, 885 DOI 10.17487/RFC6982, July 2013, 886 . 888 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 889 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 890 February 2015, . 892 [W3C.REC-xml-20040204] 893 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 894 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 895 Edition)", World Wide Web Consortium FirstEdition REC-xml- 896 20040204", February 2004, 897 . 899 [W3C.REC-xmlschema-1-20041028] 900 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 901 ""XML Schema Part 1: Structures Second Edition", World 902 Wide Web Consortium Recommendation REC-xmlschema- 903 1-20041028", October 2004, 904 . 906 [W3C.REC-xmlschema-2-20041028] 907 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 908 Second Edition", World Wide Web Consortium Recommendation 909 REC-xmlschema-2-20041028", October 2004, 910 . 912 11.2. Informative References 914 [ID.draft-ietf-regext-org] 915 Zhou, L., Kong, N., Zhou, G., Lee, X., and J. Gould, 916 "Extensible Provisioning Protocol (EPP) Reseller Mapping", 917 Feb 2018, 918 . 920 Appendix A. Change Log 922 Initial -00: Individual document submitted. 924 -01: 926 * Updated abstract and introduction. 928 * Revised typos in info response. 930 * Added explanations on how to process reseller extension after 931 successful transfer operation. 933 * Modified explanation. 935 * Deleted reseller name element in and 936 commands. 938 * Removed some inaccurate comments from xml schema. 940 * Modified the element name of reseller id and reseller name. 942 -02: 944 * Changed author information. 946 * Updated xml typos to 947 in response. 949 -03: 951 * Changed author information. 953 * Updated section 3.1. 955 * Removed reseller name element in response. 957 * Added acknowledgment. 959 * Revised the typo "resellerr" to "resellerext". 961 WG document-00: WG document submitted 963 WG document-01: Keep document alive for further discussion. The 964 requirement of reseller information is clear for both registrar 965 and registry. What we should reach a consensus is whether the 966 extension should support only a name or ID and name. 968 Organization WG document-00: Change to a generic organization object 969 extension. 971 Organization WG document-01: Added "Implementation Status" section. 973 Organization WG document-02: Accepted some of the feedbacks on the 974 mailing list. Modified the examples in the document. 976 Organization WG document-03: 978 * Updated typos. 980 * Changed some descriptions about and role attribute. 982 * Modified the example of "domain with no organization". 984 * Updated section 8, adding implementation status of VeriSign. 986 Authors' Addresses 988 Linlin Zhou 989 CNNIC 990 4 South 4th Street, Zhongguancun, Haidian District 991 Beijing, Beijing 100190 992 China 994 Phone: +86 10 5881 2677 995 Email: zhoulinlin@cnnic.cn 997 Ning Kong 998 CNNIC 999 4 South 4th Street, Zhongguancun, Haidian District 1000 Beijing, Beijing 100190 1001 China 1003 Phone: +86 10 5881 3147 1004 Email: nkong@cnnic.cn 1006 Junkai Wei 1007 CNNIC 1008 4 South 4th Street, Zhongguancun, Haidian District 1009 Beijing, Beijing 100190 1010 China 1012 Phone: +86 10 5881 3494 1013 Email: weijunkai@cnnic.cn 1014 Xiaodong Lee 1015 CNNIC 1016 4 South 4th Street, Zhongguancun, Haidian District 1017 Beijing, Beijing 100190 1018 China 1020 Phone: +86 10 5881 3020 1021 Email: xl@cnnic.cn 1023 James Gould 1024 VeriSign, Inc. 1025 12061 Bluemont Way 1026 Reston, VA 20190 1027 US 1029 Email: jgould@verisign.com