idnits 2.17.1 draft-ietf-regext-org-12.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 1964 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 G. Zhou 7 J. Yao 8 CNNIC 9 J. Gould 10 Verisign, Inc. 11 November 30, 2018 13 Extensible Provisioning Protocol (EPP) Organization Mapping 14 draft-ietf-regext-org-12 16 Abstract 18 This document describes an Extensible Provisioning Protocol (EPP) 19 mapping for provisioning and management of organization objects 20 stored in a shared central repository. Specified in Extensible 21 Markup Language (XML), this extended mapping is applied to provide 22 additional features required for the provisioning of organizations. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on June 3, 2019. 41 Copyright Notice 43 Copyright (c) 2018 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 60 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 61 3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4 62 3.2. Organization Roles . . . . . . . . . . . . . . . . . . . 4 63 3.2.1. Role Type . . . . . . . . . . . . . . . . . . . . . . 4 64 3.2.2. Role Status . . . . . . . . . . . . . . . . . . . . . 4 65 3.2.3. Role Identifier . . . . . . . . . . . . . . . . . . . 4 66 3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5 67 3.4. Organization Status Values . . . . . . . . . . . . . . . 5 68 3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 6 69 3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 7 70 3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 71 3.8. Dates and Times . . . . . . . . . . . . . . . . . . . . . 7 72 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8 73 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 8 74 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 8 75 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 10 76 4.1.3. EPP Query Command . . . . . . . . . . . . 16 77 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16 78 4.2.1. EPP Command . . . . . . . . . . . . . . . . 16 79 4.2.2. EPP Command . . . . . . . . . . . . . . . . 20 80 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 21 81 4.2.4. EPP Command . . . . . . . . . . . . . . . 21 82 4.2.5. EPP Command . . . . . . . . . . . . . . . . 22 83 4.3. Offline Review of Requested Actions . . . . . . . . . . . 26 84 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 28 85 6. Internationalization Considerations . . . . . . . . . . . . . 37 86 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 87 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 37 88 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 38 89 7.3. Role Type Values Registry . . . . . . . . . . . . . . . . 38 90 7.3.1. Registration Template . . . . . . . . . . . . . . . . 38 91 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 38 92 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 39 93 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 40 94 8.2. CNNIC Implementation . . . . . . . . . . . . . . . . . . 40 95 9. Security Considerations . . . . . . . . . . . . . . . . . . . 41 96 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 41 97 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 41 98 11.1. Normative References . . . . . . . . . . . . . . . . . . 41 99 11.2. Informative References . . . . . . . . . . . . . . . . . 42 100 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 43 101 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46 103 1. Introduction 105 There are many entities, such as registrars, resellers, DNS service 106 operators, or privacy proxies involved in the domain registration 107 business. These kind of entities have not been formally defined as 108 having an object in Extensible Provisioning Protocol (EPP). This 109 document provides a way to specify them as "organization" entities. 111 This document describes an organization object mapping for version 112 1.0 of the EPP [RFC5730]. This mapping is specified using the XML 113 1.0 as described in [W3C.REC-xml-20040204] and XML Schema notation as 114 described in [W3C.REC-xmlschema-1-20041028] and 115 [W3C.REC-xmlschema-2-20041028]. 117 2. Conventions Used in This Document 119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 121 document are to be interpreted as described in BCP 14 122 [RFC2119][RFC8174] when, and only when, they appear in all capitals, 123 as shown here. 125 In examples, "C:" represents lines sent by a protocol client and "S:" 126 represents lines returned by a protocol server. Indentation and 127 white space in examples are provided only to illustrate element 128 relationships and are not a required feature of this specification. 130 XML is case sensitive. Unless stated otherwise, XML specifications 131 and examples provided in this document MUST be interpreted in the 132 character case presented. 134 The XML namespace prefix "org" is used for the namespace 135 "urn:ietf:params:xml:ns:epp:org-1.0", but implementations MUST NOT 136 depend on it and instead employ a proper namespace-aware XML parser 137 and serializer to interpret and output the XML documents. 139 3. Object Attributes 141 An EPP organization object has attributes and associated values that 142 can be viewed and modified by the sponsoring client or the server. 143 This section describes each attribute type in detail. The formal 144 syntax for the attribute values described here can be found in the 145 "Formal Syntax" section of this document and in the appropriate 146 normative references. 148 3.1. Organization Identifier 150 All EPP organizations are identified by a server-unique identifier. 151 Organization identifiers are character strings with a specified 152 minimum length, a specified maximum length, and a specified format. 153 Organization identifiers use the "clIDType" client identifier syntax 154 described in [RFC5730]. Its corresponding element is . 156 3.2. Organization Roles 158 The organization roles are used to represent the relationship an 159 organization could have. Its corresponding element is . 160 An organization object MUST always have at least one associated role. 161 Roles can be set only by the client that sponsors an organization 162 object. A client can change the role of an organization object using 163 the EPP command. 165 3.2.1. Role Type 167 An organization role MUST have a type field. This may have any of 168 the values listed in Section 7.3. An organization could have 169 multiple roles with different role types. Its corresponding element 170 is . 172 3.2.2. Role Status 174 A role of an organization object MAY have its own statuses. Its 175 corresponding element is . The values of the role status 176 are defined in Section 3.5. 178 3.2.3. Role Identifier 180 A role MAY have a third-party-assigned identifier such as the IANA ID 181 for registrars. Its corresponding element is . 183 Example of organization role identifier: 185 186 registrar 187 ok 188 linked 189 1362 190 192 3.3. Contact and Client Identifiers 194 All EPP contacts are identified by server-unique identifiers. 195 Contact identifiers are character strings with a specified minimum 196 length, a specified maximum length, and a specified format. Contact 197 identifiers use the "clIDType" client identifier syntax described in 198 [RFC5730]. 200 3.4. Organization Status Values 202 An organization object MUST always have at least one associated 203 status value. Status values can be set only by the client that 204 sponsors an organization object and by the server on which the object 205 resides. A client can change the status of an organization object 206 using the EPP command. Each status value MAY be accompanied 207 by a string of human-readable text that describes the rationale for 208 the status applied to the object. 210 A client MUST NOT alter server status values set by the server. A 211 server MAY alter or override status values set by a client, subject 212 to local server policies. The status of an object MAY change as a 213 result of either a client-initiated transform command or an action 214 performed by a server operator. 216 Status values that can be added or removed by a client are prefixed 217 with "client". Corresponding server status values that can be added 218 or removed by a server are prefixed with "server". The "hold" and 219 "terminated" status values are server-managed when the organization 220 has no parent identifier [Section 3.6] and otherwise MAY be client- 221 managed based on server policy. Other status values that do not 222 begin with either "client" or "server" are server-managed. 224 Status Value Descriptions: 226 o ok: This is the normal status value for an object that has no 227 operations pending or active prohibitions. This value is set and 228 removed by the server as other status values are added or removed. 230 o hold: Organization transform commands and new links MUST be 231 rejected. 233 o terminated: The organization which has been terminated MUST NOT be 234 linked. Organization transform commands and new links MUST be 235 rejected. 237 o linked: The organization object has at least one active 238 association with another object. The "linked" status is not 239 explicitly set by the client. Servers should provide services to 240 determine existing object associations. 242 o clientLinkProhibited, serverLinkProhibited: Requests to add new 243 links to the organization MUST be rejected. 245 o clientUpdateProhibited, serverUpdateProhibited: Requests to update 246 the object (other than to remove this status) MUST be rejected. 248 o clientDeleteProhibited, serverDeleteProhibited: Requests to delete 249 the object MUST be rejected. 251 o pendingCreate, pendingUpdate, pendingDelete: A transform command 252 has been processed for the object, but the action has not been 253 completed by the server. Server operators can delay action 254 completion for a variety of reasons, such as to allow for human 255 review or third-party action. A transform command that is 256 processed, but whose requested action is pending, is noted with 257 response code 1001. 259 "pendingCreate", "ok", "hold", and "terminated" are mutually 260 exclusive statuses. Organization MUST have exactly one of these 261 statuses set. 263 "ok" status MAY only be combined with "linked" status. 265 A client or server MAY combine "linked" with either 266 "clientLinkProhibited" or "serverLinkProhibited" if new links must be 267 prohibited. 269 "pendingDelete" status MUST NOT be combined with either 270 "clientDeleteProhibited" or "serverDeleteProhibited" status. 272 The pendingCreate, pendingDelete, and pendingUpdate status values 273 MUST NOT be combined with each other. 275 If "clientUpdateProhibited" or "serverUpdateProhibited" is set, the 276 client will not be able to update the object. For 277 "clientUpdateProhibited", the client will first need to remove 278 "clientUpdateProhibited" prior to attempting to update the object. 279 The server can modify the object at any time. 281 3.5. Role Status Values 283 A role SHOULD have at least one associated status value. Valid 284 values include "ok", "linked", "clientLinkProhibited", and 285 "serverLinkProhibited". 287 Status Value Descriptions: 289 o ok: This is the normal status value for an role that has no 290 operations pending or active prohibitions. This value is set and 291 removed by the server as other status values are added or removed. 293 o linked: The role of an organization object has at least one active 294 association with another object. The "linked" status is not 295 explicitly set by the client. Servers SHOULD provide services to 296 determine existing object associations. 298 o clientLinkProhibited, serverLinkProhibited: Requests to add new 299 links to the role MUST be rejected. 301 3.6. Parent Identifier 303 There can be more than one layer of organizations, such as a 304 reseller. The parent identifier, as defined with the 305 element, represents the parent organization identifier in a child 306 organization. 308 The case of reseller organizations provides an example. The parent 309 identifier is not defined for the top level reseller, namely the 310 registrar of the registry. An N-tier reseller has a parent reseller 311 and at least one child reseller. A reseller customer has a parent 312 reseller and no child resellers. 314 Loops MUST be prohibited. For example: if organization A has B as 315 its parent identifier, organization B cannot have organization A as 316 its parent identifier. The same is true for larger loops involving 317 three or more organizations. 319 3.7. URL 321 The URL represents the organization web home page, as defined with 322 the element. 324 3.8. Dates and Times 326 Date and time attribute values MUST be represented in Universal 327 Coordinated Time (UTC) using the Gregorian calendar. The extended 328 date-time form using upper case "T" and "Z" characters defined in 329 [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time 330 values, as XML Schema does not support truncated date-time forms or 331 lower case "T" and "Z" characters. 333 4. EPP Command Mapping 335 A detailed description of the EPP syntax and semantics can be found 336 in the EPP core protocol specification [RFC5730]. The command 337 mappings described here are specifically for use in provisioning and 338 managing organization information via EPP. 340 4.1. EPP Query Commands 342 EPP provides two commands to retrieve organization information: 343 to determine if an organization object can be provisioned 344 within a repository, and to retrieve detailed information 345 associated with an organization object. This document does not 346 define a mapping for the EPP command to retrieve 347 organization-object transfer status information. 349 4.1.1. EPP Command 351 The EPP command is used to determine if an object can be 352 provisioned within a repository. It provides a hint that allows a 353 client to anticipate the success or failure of provisioning an object 354 using the command, as object-provisioning requirements are 355 ultimately a matter of server policy. 357 In addition to the standard EPP command elements, the command 358 MUST contain an element. This element or its ancestor 359 element MUST identify the organization namespace 360 "urn:ietf:params:xml:ns:epp:org-1.0". The element 361 contains the following child elements: 363 o One or more elements that contain the server-unique 364 identifier of the organization objects to be queried. 366 Example command: 368 C: 369 C: 370 C: 371 C: 372 C: 374 C: res1523 375 C: re1523 376 C: 1523res 377 C: 378 C: 379 C: ABC-12345 380 C: 381 C: 383 When a command has been processed successfully, the EPP 384 element MUST contain a child element. This 385 element or its ancestor element MUST identify the organization 386 namespace "urn:ietf:params:xml:ns:epp:org-1.0". The 387 element contains one or more elements that contain the 388 following child elements: 390 o An element that identifies the queried object. This 391 element MUST contain an "avail" attribute whose value indicates 392 object availability (can it be provisioned or not) at the moment 393 the command was completed. A value of "1" or "true" means 394 that the object can be provisioned. A value of "0" or "false" 395 means that the object cannot be provisioned. 397 o An OPTIONAL element that may be provided when an 398 object cannot be provisioned. If present, this element contains 399 server-specific text to help explain why the object cannot be 400 provisioned. This text MUST be represented in the response 401 language previously negotiated with the client; an OPTIONAL "lang" 402 attribute as defined in [RFC5646] may be present to identify the 403 language if the negotiated value is something other than the 404 default value of "en"(English). 406 Example response: 408 S: 409 S: 410 S: 411 S: 412 S: Command completed successfully 413 S: 414 S: 415 S: 417 S: 418 S: res1523 419 S: 420 S: 421 S: re1523 422 S: In use 423 S: 424 S: 425 S: 1523res 426 S: 427 S: 428 S: 429 S: 430 S: ABC-12345 431 S: 54322-XYZ 432 S: 433 S: 434 S: 436 An EPP error response MUST be returned if a command cannot be 437 processed for any reason. 439 4.1.2. EPP Command 441 The EPP command is used to retrieve information associated 442 with an organization object. In addition to the standard EPP command 443 elements, the command MUST contain a element. This 444 element or its ancestor element MUST identify the organization 445 namespace "urn:ietf:params:xml:ns:epp:org-1.0". The 446 element contains the following child elements: 448 o An element that contains the server-unique identifier of 449 the organization object to be queried. 451 Example command: 453 C: 454 C: 455 C: 456 C: 457 C: 459 C: res1523 460 C: 461 C: 462 C: ABC-12345 463 C: 464 C: 466 When an command has been processed successfully, the EPP 467 element MUST contain a child element. This 468 element or its ancestor element MUST identify the organization 469 namespace "urn:ietf:params:xml:ns:epp:org-1.0". The 470 element contains the following child elements: 472 o An element that contains the server-unique identifier of 473 the organization object, as defined in Section 3.1. 475 o An element that contains the Repository Object 476 IDentifier assigned to the organization object when the object was 477 created. 479 o One or more elements that contain the role type, role 480 statuses and optional role id of the organization. 482 * An element that contains the type of the 483 organization, as defined in Section 3.2. 485 * One or more elements that contain the role 486 statuses. The values of the role status are defined in 487 Section 3.5. 489 * An OPTIONAL element that contains a third-party- 490 assigned identifier, such as IANA ID for registrars, as defined 491 in Section 3.2.3. 493 o One or more elements that contain the operational 494 status of the organization, as defined in Section 3.4. 496 o An OPTIONAL element that contains the identifier of 497 the parent object, as defined in Section 3.6. 499 o Zero to two elements that contain postal-address 500 information. Two elements are provided so that address 501 information can be provided in both internationalized and 502 localized forms; a "type" attribute is used to identify the two 503 forms. If an internationalized form (type="int") is provided, 504 element content MUST be represented in a subset of Unicode in the 505 range U+0020 - U+007E. If a localized form (type="loc") is 506 provided, element content MAY be represented in unrestricted UTF- 507 8. The element contains the following child 508 elements: 510 * An element that contains the name of the 511 organization. 513 * An OPTIONAL element that contains address 514 information associated with the organization. A 515 element contains the following child elements: 517 + One, two, or three elements that contain the 518 organization's street address. 520 + An element that contains the organization's city. 522 + An OPTIONAL element that contains the 523 organization's state or province. 525 + An OPTIONAL element that contains the 526 organization's postal code. 528 + An element that contains the alpha-2 organization's 529 country code. The detailed format of this element is 530 described in section 2.4.3 of [RFC5733]. 532 o An OPTIONAL element that contains the organization's 533 voice telephone number. The detailed format of this element is 534 described in Section 2.5 of [RFC5733]. 536 o An OPTIONAL element that contains the organization's 537 facsimile telephone number. 539 o An OPTIONAL element that contains the organization's 540 email address. The detailed format of this element is described 541 in section 2.6 of [RFC5733]. 543 o An OPTIONAL element that contains the URL to the website 544 of the organization. The detailed format of this element is 545 described in [RFC3986]. 547 o Zero or more elements that contain identifiers for 548 the contact objects to be associated with the organization object. 550 Contact object identifiers MUST be known to the server before the 551 contact object can be associated with the organization object. 552 The required "type" is used to represent contact types. The type 553 values include "admin", "tech", "billing", "abuse", and "custom". 554 The OPTIONAL "typeName" attribute is used to define the name of a 555 "custom" type. 557 o An OPTIONAL element that contains the organization 558 identifier of the sponsoring client. There is no 559 element if the organization is managed by the registry. 561 o An element that contains the identifier of the client 562 that created the organization object. 564 o An element that contains the date and time of 565 organization object creation. 567 o An element that contains the identifier of the client 568 that last updated the organization object. This element MUST NOT 569 be present if the organization has never been modified. 571 o An element that contains the date and time of the 572 most recent organization object modification. This element MUST 573 NOT be present if the organization object has never been modified. 575 Example response for "Example Registrar Inc." organization 576 organization object with identifier "registrar1362": 578 S: 579 S: 580 S: 581 S: 582 S: Command completed successfully 583 S: 584 S: 585 S: 587 S: registrar1362 588 S: registrar1362-REP 589 S: 590 S: registrar 591 S: ok 592 S: linked 593 S: 1362 594 S: 595 S: ok 596 S: 597 S: Example Registrar Inc. 598 S: 599 S: 123 Example Dr. 600 S: Suite 100 601 S: Dulles 602 S: VA 603 S: 20166-6503 604 S: US 605 S: 606 S: 607 S: +1.7035555555 608 S: +1.7035555556 609 S: contact@organization.example 610 S: https://organization.example 611 S: sh8013 612 S: sh8013 613 S: sh8013 615 S: ClientX 616 S: 1999-04-03T22:00:00.0Z 617 S: ClientX 618 S: 1999-12-03T09:00:00.0Z 619 S: 620 S: 621 S: 622 S: ABC-12345 623 S: 54322-XYZ 624 S: 625 S: 626 S: 628 Example response for "Example Reseller Inc." organization 629 object of reseller type managed by identifier "registrar1362": 631 S: 632 S: 633 S: 634 S: 635 S: Command completed successfully 636 S: 637 S: 638 S: 640 S: reseller1523 641 S: reseller1523-REP 642 S: 643 S: reseller 644 S: ok 645 S: linked 646 S: 647 S: ok 648 S: registrar1362 649 S: 650 S: Example Reseller Inc. 651 S: 652 S: 123 Example Dr. 653 S: Suite 100 654 S: Dulles 655 S: VA 656 S: 20166-6503 657 S: US 658 S: 659 S: 660 S: +1.7035555556 661 S: https://organization.example 662 S: sh8013 663 S: 1362 664 S: ClientX 665 S: 1999-04-03T22:00:00.0Z 666 S: ClientX 667 S: 1999-12-03T09:00:00.0Z 668 S: 669 S: 670 S: 671 S: ABC-12345 672 S: 54322-XYZ 673 S: 674 S: 675 S: 677 An EPP error response MUST be returned if an command cannot be 678 processed for any reason. 680 4.1.3. EPP Query Command 682 The transfer semantics does not apply to organization object. No EPP 683 query command is defined in this document. 685 4.2. EPP Transform Commands 687 This document provides three commands to transform organization 688 object information: to create an instance of an organization 689 object, to delete an instance of an organization object, and 690 to change information associated with an organization 691 object. This document does not define a mapping for the EPP 692 and command. 694 Transform commands are typically processed and completed in real 695 time. Server operators MAY receive and process transform commands 696 but defer completing the requested action if human or third-party 697 review is required before the requested action can be completed. In 698 such situations, the server MUST return a 1001 response code to the 699 client to note that the command has been received and processed but 700 that the requested action is pending. The server MUST also manage 701 the status of the object that is the subject of the command to 702 reflect the initiation and completion of the requested action. Once 703 the action has been completed, the client MUST be notified using a 704 service message that the action has been completed and that the 705 status of the object has changed. Other notification methods MAY be 706 used in addition to the required service message. 708 4.2.1. EPP Command 710 The EPP command provides a transform operation that allows a 711 client to create an organization object. In addition to the standard 712 EPP command elements, the command MUST contain a 713 element. This element or its ancestor element MUST 714 identify the organization namespace "urn:ietf:params:xml:ns:epp:org- 715 1.0". The element contains the following child 716 elements: 718 o An element that contains the desired server-unique 719 identifier for the organization to be created, as defined in 720 Section 3.1. 722 o One or more elements that contain the role type, role 723 statuses and optional role id of the organization. 725 * An element that contains the type of the 726 organization, as defined in Section 3.2. 728 * Zero or more elements that contain the role 729 statuses. The values of the role status are defined in 730 Section 3.5. 732 * An OPTIONAL element that contains a third-party- 733 assigned identifier, such as IANA ID for registrars, as defined 734 in Section 3.2.3. 736 o Zero or more elements that contain the operational 737 status of the organization, as defined in Section 3.4. 739 o An OPTIONAL element that contains the identifier of 740 the parent object, as defined in Section 3.6. 742 o Zero to two elements that contain postal-address 743 information. Two elements are provided so that address 744 information can be provided in both internationalized and 745 localized forms; a "type" attribute is used to identify the two 746 forms. If an internationalized form (type="int") is provided, 747 element content MUST be represented in a subset of Unicode in the 748 range U+0020 - U+007E. If a localized form (type="loc") is 749 provided, element content MAY be represented in unrestricted UTF- 750 8. The element contains the following child 751 elements: 753 * An element that contains the name of the 754 organization. 756 * An OPTIONAL element that contains address 757 information associated with the organization. A 758 element contains the following child elements: 760 + One, two, or three elements that contain the 761 organization's street address. 763 + An element that contains the organization's city. 765 + An OPTIONAL element that contains the 766 organization's state or province. 768 + An OPTIONAL element that contains the 769 organization's postal code. 771 + An element that contains the alpha-2 organization's 772 country code. The detailed format of this element is 773 described in section 2.4.3 of [RFC5733]. 775 o An OPTIONAL element that contains the organization's 776 voice telephone number. The detailed format of this element is 777 described in Section 2.5 of [RFC5733] 779 o An OPTIONAL element that contains the organization's 780 facsimile telephone number. 782 o An OPTIONAL element that contains the organization's 783 email address. The detailed format of this element is described 784 in section 2.6 of [RFC5733]. 786 o An OPTIONAL element that contains the URL to the website 787 of the organization. The detailed format of this element is 788 described in [RFC3986]. 790 o Zero or more elements that contain identifiers for 791 the contact objects associated with the organization object. 793 Example command: 795 C: 796 C: 797 C: 798 C: 799 C: 801 C: res1523 802 C: 803 C: reseller 804 C: 805 C: 1523res 806 C: 807 C: Example Organization Inc. 808 C: 809 C: 123 Example Dr. 810 C: Suite 100 811 C: Dulles 812 C: VA 813 C: 20166-6503 814 C: US 815 C: 816 C: 817 C: +1.7035555555 818 C: +1.7035555556 819 C: contact@organization.example 820 C: https://organization.example 821 C: sh8013 822 C: sh8013 823 C: 824 C: 825 C: ABC-12345 826 C: 827 C: 829 When a command has been processed successfully, the EPP 830 element MUST contain a child element. This 831 element or its ancestor element MUST identify the organization 832 namespace "urn:ietf:params:xml:ns:epp:org-1.0". The 833 element contains the following child elements: 835 o An element that contains the server-unique identifier for 836 the created organization, as defined in Section 3.1. 838 o An element that contains the date and time of 839 organization-object creation. 841 Example response: 843 S: 844 S: 845 S: 846 S: 847 S: Command completed successfully 848 S: 849 S: 850 S: 852 S: res1523 853 S: 1999-04-03T22:00:00.0Z 854 S: 855 S: 856 S: 857 S: ABC-12345 858 S: 54321-XYZ 859 S: 860 S: 861 S: 863 An EPP error response MUST be returned if a command cannot 864 be processed for any reason. 866 4.2.2. EPP Command 868 The EPP command provides a transform operation that allows a 869 client to delete an organization object. In addition to the standard 870 EPP command elements, the command MUST contain an 871 element. This element or its ancestor element MUST 872 identify the organization namespace "urn:ietf:params:xml:ns:epp:org- 873 1.0". The element MUST contain the following child 874 element: 876 o An element that contains the server-unique identifier of 877 the organization object to be deleted, as defined in Section 3.1. 879 An organization object MUST NOT be deleted if it is associated with 880 other known objects. An associated organization MUST NOT be deleted 881 until associations with other known objects have been broken. A 882 server MUST notify clients that object relationships exist by sending 883 a 2305 error response code when a command is attempted and 884 fails due to existing object relationships. 886 Example command: 888 C: 889 C: 890 C: 891 C: 892 C: 894 C: res1523 895 C: 896 C: 897 C: ABC-12345 898 C: 899 C: 901 When a command has been processed successfully, a server 902 MUST respond with an EPP response with no element. 904 Example response: 906 S: 907 S: 908 S: 909 S: 910 S: Command completed successfully 911 S: 912 S: 913 S: ABC-12345 914 S: 54321-XYZ 915 S: 916 S: 917 S: 919 An EPP error response MUST be returned if a command cannot 920 be processed for any reason. 922 4.2.3. EPP Command 924 Renewal semantics do not apply to organization objects, so there is 925 no mapping defined for the EPP command. 927 4.2.4. EPP Command 929 Transfer semantics do not apply to organization objects, so there is 930 no mapping defined for the EPP command. 932 4.2.5. EPP Command 934 The EPP command provides a transform operation that allows a 935 client to modify the attributes of an organization object. In 936 addition to the standard EPP command elements, the command 937 MUST contain a element. This element or its ancestor 938 element MUST identify the organization namespace 939 "urn:ietf:params:xml:ns:epp:org-1.0". The element 940 contains the following child elements: 942 o An element that contains the server-unique identifier of 943 the organization object to be updated, as defined in Section 3.1. 945 o An OPTIONAL element that contains attribute values to be 946 added to the object. 948 o An OPTIONAL element that contains attribute values to be 949 removed from the object. 951 o An OPTIONAL element that contains attribute values to be 952 changed. 954 At least one , or element MUST be 955 provided if the command is not being extended. All of these elements 956 MAY be omitted if an extension is present. The OPTIONAL 957 and elements contain the following child 958 elements: 960 o Zero or more elements that contain the identifiers 961 for contact objects to be associated with or removed from the 962 organization object. Contact object identifiers MUST be known to 963 the server before the contact object can be associated with the 964 organization object. 966 o Zero or more elements that contain the role type, role 967 statuses and optional role id of the organization. 969 * An element that contains the role type of the 970 organization, as defined in Section 3.2. The role type 971 uniquely identifies the role to update. 973 * Zero or more elements that contain the role 974 statuses. The values of the role status are defined in 975 Section 3.5. 977 * An OPTIONAL element that contains a third-party- 978 assigned identifier, such as IANA ID for registrars, as defined 979 in Section 3.2.3. 981 o Zero or more elements that contain the operational 982 status of the organization. 984 An OPTIONAL element contains the following child elements, 985 where at least one child element MUST be present: 987 o An OPTIONAL element that contains the identifier of 988 the parent object. 990 o Zero to two elements that contain postal-address 991 information. Two elements are provided so that address 992 information can be provided in both internationalized and 993 localized forms; a "type" attribute is used to identify the two 994 forms. If an internationalized form (type="int") is provided, 995 element content MUST be represented in a subset of Unicode in the 996 range U+0020 - U+007E. If a localized form (type="loc") is 997 provided, element content MAY be represented in unrestricted UTF- 998 8. The change of the postal info is defined as a replacement of 999 that postal info element with the contents of the sub-elements 1000 included in the update command. An empty element 1001 is supported to allow a type of postal info to be removed. The 1002 element contains the following child elements: 1004 * An element that contains the name of the 1005 organization. 1007 * An OPTIONAL element that contains address 1008 information associated with the organization. A 1009 element contains the following child elements: 1011 + One, two, or three elements that contain the 1012 organization's street address. 1014 + An element that contains the organization's city. 1016 + An OPTIONAL element that contains the 1017 organization's state or province. 1019 + An OPTIONAL element that contains the 1020 organization's postal code. 1022 + An element that contains the alpha-2 organization's 1023 country code. The detailed format of this element is 1024 described in section 2.4.3 of [RFC5733]. 1026 o An OPTIONAL element that contains the organization's 1027 voice telephone number. The detailed format of this element is 1028 described in Section 2.5 of [RFC5733] 1030 o An OPTIONAL element that contains the organization's 1031 facsimile telephone number. 1033 o An OPTIONAL element that contains the organization's 1034 email address. The detailed format of this element is described 1035 in section 2.6 of [RFC5733]. 1037 o An OPTIONAL element that contains the URL to the website 1038 of the organization. The detailed format of this element is 1039 described in [RFC3986] 1041 Example command: 1043 C: 1044 C: 1045 C: 1046 C: 1047 C: 1049 C: res1523 1050 C: 1051 C: sh8013 1052 C: 1053 C: privacyproxy 1054 C: clientLinkProhibited 1055 C: 1056 C: clientLinkProhibited 1057 C: 1058 C: 1059 C: sh8014 1060 C: 1061 C: reseller 1062 C: 1063 C: 1064 C: 1065 C: 1066 C: 1067 C: 124 Example Dr. 1068 C: Suite 200 1069 C: Dulles 1070 C: VA 1071 C: 20166-6503 1072 C: US 1073 C: 1074 C: 1075 C: +1.7034444444 1076 C: 1077 C: 1078 C: 1079 C: 1080 C: ABC-12345 1081 C: 1082 C: 1084 When an command has been processed successfully, a server 1085 MUST respond with an EPP response with no element. 1087 Example response: 1089 S: 1090 S: 1091 S: 1092 S: 1093 S: Command completed successfully 1094 S: 1095 S: 1096 S: ABC-12345 1097 S: 54321-XYZ 1098 S: 1099 S: 1100 S: 1102 An EPP error response MUST be returned if an command cannot 1103 be processed for any reason. 1105 4.3. Offline Review of Requested Actions 1107 Commands are processed by a server in the order they are received 1108 from a client. Though an immediate response confirming receipt and 1109 processing of the command is produced by the server, a server 1110 operator MAY perform an offline review of requested transform 1111 commands before completing the requested action. In such situations, 1112 the response from the server MUST clearly note that the transform 1113 command has been received and processed, but the requested action is 1114 pending. The status in the response of the corresponding object MUST 1115 clearly reflect processing of the pending action. The server MUST 1116 notify the client when offline processing of the action has been 1117 completed. 1119 Examples describing a command that requires offline review 1120 are included here. Note the result code and message returned in 1121 response to the command. 1123 S: 1124 S: 1125 S: 1126 S: 1127 S: Command completed successfully; 1128 S: action pending 1129 S: 1130 S: 1131 S: 1133 S: res1523 1134 S: 1999-04-03T22:00:00.0Z 1135 S: 1136 S: 1137 S: 1138 S: ABC-12345 1139 S: 54321-XYZ 1140 S: 1141 S: 1142 S: 1144 The status of the organization object after returning this response 1145 MUST include "pendingCreate". The server operator reviews the 1146 request offline, and informs the client of the outcome of the review 1147 by queuing a service message for retrieval via the command; it 1148 MAY additionally use an out-of-band mechanism to inform the client of 1149 the outcome. 1151 The service message MUST contain text that describes the notification 1152 in the child element of the response element. In 1153 addition, the EPP element MUST contain a child 1154 element. This element or its ancestor element MUST 1155 identify the organization namespace "urn:ietf:params:xml:ns:epp:org- 1156 1.0". The element contains the following child 1157 elements: 1159 o An element that contains the server-unique identifier of 1160 the organization object. The element contains a REQUIRED 1161 "paResult" attribute. A positive boolean value indicates that the 1162 request has been approved and completed. A negative boolean value 1163 indicates that the request has been denied and the requested 1164 action has not been taken. 1166 o An element that contains the client transaction 1167 identifier and server transaction identifier returned with the 1168 original response to process the command. The client transaction 1169 identifier is OPTIONAL and will only be returned if the client 1170 provided an identifier with the original command. 1172 o An element that contains the date and time describing 1173 when review of the requested action was completed. 1175 Example "review completed" service message: 1177 S: 1178 S: 1179 S: 1180 S: 1181 S: Command completed successfully; 1182 S: ack to dequeue 1183 S: 1184 S: 1185 S: 1999-04-04T22:01:00.0Z 1186 S: Pending action completed successfully. 1187 S: 1188 S: 1189 S: 1191 S: res1523 1192 S: 1193 S: ABC-12345 1194 S: 54321-XYZ 1195 S: 1196 S: 1999-04-04T22:00:00.0Z 1197 S: 1198 S: 1199 S: 1200 S: BCD-23456 1201 S: 65432-WXY 1202 S: 1203 S: 1204 S: 1206 5. Formal Syntax 1208 An EPP object mapping is specified in XML Schema notation. The 1209 formal syntax presented here is a complete schema representation of 1210 the object mapping suitable for automated validation of EPP XML 1211 instances. The BEGIN and END tags are not part of the schema; they 1212 are used to note the beginning and ending of the schema for URI 1213 registration purposes. 1215 BEGIN 1216 1218 1225 1228 1229 1231 1232 1233 Extensible Provisioning Protocol v1.0 1234 organization provisioning schema. 1235 1236 1238 1241 1242 1243 1244 1245 1246 1248 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1269 1270 1271 1272 1273 1274 1275 1276 1278 1279 1280 1281 1283 1284 1285 1287 1288 1289 1291 1293 1294 1297 1299 1300 1301 1302 1304 1305 1306 1307 1309 1310 1311 1312 1313 1314 1315 1316 1317 1319 1320 1321 1322 1323 1324 1325 1327 1328 1329 1330 1331 1332 1334 1335 1336 1337 1338 1339 1341 1342 1343 1344 1345 1347 1348 1349 1350 1351 1353 1354 1355 1356 1357 1358 1359 1360 1362 1363 1365 1367 1368 1369 1371 1372 1373 1374 1375 1376 1378 1381 1382 1383 1384 1385 1387 1390 1391 1392 1394 1395 1397 1400 1401 1402 1403 1404 1405 1407 1409 1410 1411 1412 1414 1415 1416 1418 1421 1422 1423 1425 1426 1428 1431 1432 1433 1435 1437 1439 1441 1443 1445 1447 1449 1451 1454 1456 1458 1461 1462 1463 1465 1467 1469 1471 1472 1474 1477 1478 1479 1481 1483 1485 1486 1488 1491 1492 1493 1495 1498 1500 1502 1505 1507 1508 1510 1511 1512 1514 1516 1517 1519 1521 1524 1525 1526 1528 1531 1532 1533 1535 1536 1538 1539 1540 1541 1543 1544 1546 1547 1548 1549 1551 1552 1554 1556 1559 1560 1561 1563 1565 1567 1569 1571 1573 1575 1577 1579 1581 1583 1585 1587 1589 1591 1593 1594 1595 1598 1599 1600 1601 1603 1604 1606 1609 1610 END 1612 6. Internationalization Considerations 1614 EPP is represented in XML, which provides native support for encoding 1615 information using the Unicode character set and its more compact 1616 representations including UTF-8. Conformant XML processors recognize 1617 both UTF-8 [RFC3629] and UTF-16 [RFC2781]. Though XML includes 1618 provisions to identify and use other character encodings through use 1619 of an "encoding" attribute in an declaration, use of UTF-8 is 1620 RECOMMENDED. 1622 As an extension of the EPP organization object mapping, the elements 1623 and element content described in this document MUST inherit the 1624 internationalization conventions used to represent higher-layer 1625 domain and core protocol structures present in an XML instance that 1626 includes this extension. 1628 7. IANA Considerations 1630 7.1. XML Namespace 1632 This document uses URNs to describe XML namespaces and XML schemas 1633 conforming to a registry mechanism described in [RFC3688]. IANA is 1634 requested to assignment the following URI. 1636 Registration request for the organization namespace: 1638 URI: urn:ietf:params:xml:ns:epp:org-1.0 1640 Registrant Contact: IESG 1642 XML: None. Namespace URIs do not represent an XML specification. 1644 Registration request for the organization XML schema: 1646 URI: urn:ietf:params:xml:schema:epp:org-1.0 1648 Registrant Contact: IESG 1650 XML: See the "Formal Syntax" section of this document. 1652 7.2. EPP Extension Registry 1654 The EPP extension described in this document should be registered by 1655 the IANA in the EPP Extension Registry described in [RFC7451]. The 1656 details of the registration are as follows: 1658 Name of Extension: Extensible Provisioning Protocol (EPP) 1659 Organization Mapping 1661 Document status: Standards Track 1663 Reference: RFCXXXX (please replace "XXXX" with the RFC number for 1664 this document after a number is assigned by the RFC Editor) 1666 Registrant Name and Email Address: IESG, iesg@ietf.org 1668 TLDs: Any 1670 IPR Disclosure: None 1672 Status: Active 1674 Notes: None 1676 7.3. Role Type Values Registry 1678 IANA has created a new category of protocol registry for values of 1679 the organization roles. The name of this registry is "EPP 1680 Organization Role Values". The registration policy for this registry 1681 is "Expert Review" [RFC8126]. 1683 7.3.1. Registration Template 1685 Value: the string value being registered. 1687 Description: Brief description of the organization role values. 1689 Registrant Name: For IETF RFCs, state "IESG". For others, give the 1690 name of the responsible party. 1692 Registrant Contact Information: an email address, postal address, or 1693 some other information to be used to contact the registrant. 1695 7.3.2. Initial Registry Contents 1697 Followings are the initial registry contents: 1699 Value: registrar 1700 Description: The entity object instance represents the authority 1701 responsible for the registration in the registry. 1703 Registrant Name: IESG 1705 Registrant Contact Information: iesg@ietf.org 1707 Value: reseller 1709 Description: The entity object instance represents a third party 1710 through which the registration was conducted (i.e., not the 1711 registry or registrar). 1713 Registrant Name: IESG 1715 Registrant Contact Information: iesg@ietf.org 1717 Value: privacyproxy 1719 Description: The entity object instance represents a third-party 1720 who could help to register a domain without exposing the 1721 registrants' private information. 1723 Registrant Name: IESG 1725 Registrant Contact Information: iesg@ietf.org 1727 Value: dns-operator 1729 Description: The entity object instance represents a third-party 1730 DNS operator that maintains the name servers and zone data on 1731 behalf of a registrant. 1733 Registrant Name: IESG 1735 Registrant Contact Information: iesg@ietf.org 1737 8. Implementation Status 1739 Note to RFC Editor: Please remove this section and the reference to 1740 [RFC7942] before publication. This section records the status of 1741 known implementations of the protocol defined by this specification 1742 at the time of posting of this Internet-Draft, and is based on a 1743 proposal described in [RFC7942]. The description of implementations 1744 in this section is intended to assist the IETF in its decision 1745 processes in progressing drafts to RFCs. Please note that the 1746 listing of any individual implementation here does not imply 1747 endorsement by the IETF. Furthermore, no effort has been spent to 1748 verify the information presented here that was supplied by IETF 1749 contributors. This is not intended as, and must not be construed to 1750 be, a catalog of available implementations or their features. 1751 Readers are advised to note that other implementations may exist. 1753 According to [RFC7942], "this will allow reviewers and working groups 1754 to assign due consideration to documents that have the benefit of 1755 running code, which may serve as evidence of valuable experimentation 1756 and feedback that have made the implemented protocols more mature. 1757 It is up to the individual working groups to use this information as 1758 they see fit". 1760 8.1. Verisign EPP SDK 1762 Organization: Verisign Inc. 1764 Name: Verisign EPP SDK 1766 Description: The Verisign EPP SDK includes both a full client 1767 implementation and a full server stub implementation of draft-ietf- 1768 regext-org. 1770 Level of maturity: Development 1772 Coverage: All aspects of the protocol are implemented. 1774 Licensing: GNU Lesser General Public License 1776 Contact: jgould@verisign.com 1778 URL: https://www.verisign.com/en_US/channel-resources/domain- 1779 registry-products/epp-sdks 1781 8.2. CNNIC Implementation 1783 Organization: CNNIC 1785 Name: EPP Organization Mapping 1787 Description: CNNIC is trying to update EPP organization mapping from 1788 previous reseller mapping according to this document. 1790 Level of maturity: Development 1792 Coverage: EPP organization mapping 1794 Contact: zhouguiqing@cnnic.cn 1796 9. Security Considerations 1798 The organization object may have personally identifiable information, 1799 such as . This information is not a required element in 1800 this document which can be provided on a voluntary basis. If it is 1801 provided, both client and server MUST ensure that authorization 1802 information is stored and exchanged with high-grade encryption 1803 mechanisms to provide privacy services, which is specified in 1804 [RFC5733]. The security considerations described in [RFC5730] or 1805 those caused by the protocol layers used by EPP will apply to this 1806 specification as well. 1808 10. Acknowledgment 1810 The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick 1811 Mevzek, Antoin Verschuren and Scott Hollenbeck for their careful 1812 review and valuable comments. 1814 11. References 1816 11.1. Normative References 1818 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1819 Requirement Levels", BCP 14, RFC 2119, 1820 DOI 10.17487/RFC2119, March 1997, 1821 . 1823 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 1824 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 1825 2003, . 1827 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1828 DOI 10.17487/RFC3688, January 2004, 1829 . 1831 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 1832 Resource Identifier (URI): Generic Syntax", STD 66, 1833 RFC 3986, DOI 10.17487/RFC3986, January 2005, 1834 . 1836 [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying 1837 Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, 1838 September 2009, . 1840 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1841 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1842 . 1844 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 1845 Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, 1846 August 2009, . 1848 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1849 Code: The Implementation Status Section", BCP 205, 1850 RFC 7942, DOI 10.17487/RFC7942, July 2016, 1851 . 1853 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1854 Writing an IANA Considerations Section in RFCs", BCP 26, 1855 RFC 8126, DOI 10.17487/RFC8126, June 2017, 1856 . 1858 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1859 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1860 May 2017, . 1862 [W3C.REC-xml-20040204] 1863 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 1864 F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third 1865 Edition)", World Wide Web Consortium FirstEdition REC-xml- 1866 20040204", February 2004, 1867 . 1869 [W3C.REC-xmlschema-1-20041028] 1870 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, 1871 ""XML Schema Part 1: Structures Second Edition", World 1872 Wide Web Consortium Recommendation REC-xmlschema- 1873 1-20041028", October 2004, 1874 . 1876 [W3C.REC-xmlschema-2-20041028] 1877 Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes 1878 Second Edition", World Wide Web Consortium Recommendation 1879 REC-xmlschema-2-20041028", October 2004, 1880 . 1882 11.2. Informative References 1884 [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 1885 10646", RFC 2781, DOI 10.17487/RFC2781, February 2000, 1886 . 1888 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1889 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 1890 February 2015, . 1892 Appendix A. Change Log 1894 Initial -00: Individual document submitted. 1896 -01: 1898 * Updated abstract text. 1900 * Added sentences to avoid loop of parent identifiers in section 1901 3.4. 1903 * Revised typos in section 3.6. 1905 * Added explanation of contact type attribute in section 4.1.2. 1907 * Updated responses. 1909 * Deleted description of command in section 4.1 and 1910 4.2. 1912 * Deleted whoisInfo disclose type in XML schema. 1914 * Deleted maxOccurs of addRemType. 1916 * Deleted extra "OPTIONAL" in section 4.2.5. 1918 * Updated typos in response. 1920 -02: 1922 * Changed author information. 1924 * Updated url definition. 1926 * Updated XML schema. 1928 -03: 1930 * Changed author information. 1932 * Updated section 3.1. 1934 * Refactoried the XSD file. Added element. 1936 * Added acknowledgment. 1938 WG document-00: WG document submitted 1939 WG document-01: Keep document alive for further discussion. 1940 Reseller object or entity object with multiple roles? 1942 Organization WG document-00: Change to a generic organization object 1943 mapping. 1945 Organization WG document-01: Added "Implementation Status" section. 1947 Organization WG document-02: Accepted some of the feedbacks on the 1948 mailing list. 1950 Organization WG document-03: 1952 * Updated section 3.2, changed the structure of organization 1953 role. 1955 * Updated section 4.2.5 for the "add", "rem" and "chg" example. 1957 * Updated section 5 of formal syntax. 1959 * Updated section 7.2 for the registration template and initial 1960 values. 1962 * Updated section 8 of implementation status. 1964 Organization WG document-04: 1966 * Updated section 3.2, changed the structure of organization 1967 role. 1969 * Updated references. 1971 * Updated section 8 of implementation status. 1973 Organization WG document-05: 1975 * Updated the description of of a role. 1977 * Removed the third paragraph of "Implementation Status". 1979 * Remove the Informative Reference to draft-ietf-regext-reseller 1980 from the draft. 1982 Organization WG document-06: 1984 * Updated typos. 1986 * Added "Query" for " Query Command". 1988 * Change "Registrant Contact" to IESG in section 7.1. 1990 * Modified section 7.2. 1992 Organization WG document-07: 1994 * Updated typos. 1996 * Added dns-operator in section 7.1. 1998 * Added "OPTIONAL" for 2000 Organization WG document-08: 2002 * Updated "Offline Review of Requested Actions". 2004 Organization WG document-09: 2006 * Updated "This element or its ancestor element MUST identify the 2007 organization namespace." in section 4.1.1 and other parts of 2008 this document. 2010 * Updated text in section 2 match RFC 8174. 2012 * Modified "roleid" to "roleID". 2014 * Updated text about loops in section 3.6. 2016 * Referred section 2.5 of RFC5733 for voice format. 2018 * Updated XML schema for the maxOccurs value of "reason" element. 2020 * Updated section 7.3. 2022 * Replaced "http" with "https" in the examples. 2024 * Updated writing typos. 2026 * Modified XML namespace and schema. 2028 Organization WG document-10: 2030 * Modified XML namespace and schema. 2032 * Removed the maxOccurs value of "reason" element. 2034 Organization WG document-11: 2036 * Typo of RFC2781 and moved this reference in "Informative 2037 References". 2039 * "Loops MUST be prohibited." in section 3.6. 2041 Organization WG document-12: 2043 * Removed "OPTIONAL" when "zero or more" or "zero to two" 2044 appears. 2046 * Updated the "Organization Status Values" text. 2048 * Updated the full xml namespace. 2050 * Updated the text in "Offline review". 2052 * Updated the text in "Security Considerations". 2054 * Added "Document satus" and "Reference" in section "EPP 2055 Extension Registry". 2057 * Added references of RFC3688,RFC3986 and RFC5646. 2059 Authors' Addresses 2061 Linlin Zhou 2062 CNNIC 2063 4 South 4th Street, Zhongguancun, Haidian District 2064 Beijing, Beijing 100190 2065 China 2067 Email: zhoulinlin@cnnic.cn 2069 Ning Kong 2070 Consultant 2072 Email: ietfing@gmail.com 2074 Guiqing Zhou 2075 CNNIC 2076 4 South 4th Street, Zhongguancun, Haidian District 2077 Beijing, Beijing 100190 2078 China 2080 Email: zhouguiqing@cnnic.cn 2081 Jiankang Yao 2082 CNNIC 2083 4 South 4th Street, Zhongguancun, Haidian District 2084 Beijing, Beijing 100190 2085 China 2087 Email: yaojk@cnnic.cn 2089 James Gould 2090 Verisign, Inc. 2091 12061 Bluemont Way 2092 Reston, VA 20190 2093 US 2095 Email: jgould@verisign.com