Internet Engineering Task Force (IETF) L. Zhou
Request for Comments: 8543 CNNIC
Category: Standards Track N. Kong
ISSN: 2070-1721 Consultant
J. Yao
CNNIC
J. Gould
VeriSign, Inc.
G. Zhou
March 2019
Internet Engineering Task Force (IETF) L. Zhou
Request for Comments: 8543 CNNIC
Category: Standards Track N. Kong
ISSN: 2070-1721 Consultant
J. Yao
CNNIC
J. Gould
VeriSign, Inc.
G. Zhou
March 2019
Extensible Provisioning Protocol (EPP) Organization Mapping
可扩展资源调配协议（EPP）组织映射
Abstract
摘要
This document describes an Extensible Provisioning Protocol (EPP) mapping for provisioning and management of organization objects stored in a shared central repository.
本文档描述了可扩展资源调配协议（EPP）映射，用于对存储在共享中央存储库中的组织对象进行资源调配和管理。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8543.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8543.
Copyright Notice
版权公告
Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.
版权（c）2019 IETF信托基金和被确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(https://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4
3.2. Organization Roles . . . . . . . . . . . . . . . . . . . 4
3.2.1. Role Type . . . . . . . . . . . . . . . . . . . . . . 4
3.2.2. Role Status . . . . . . . . . . . . . . . . . . . . . 4
3.2.3. Role Identifier . . . . . . . . . . . . . . . . . . . 4
3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5
3.4. Organization Status Values . . . . . . . . . . . . . . . 5
3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 7
3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 7
3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.8. Dates and Times . . . . . . . . . . . . . . . . . . . . . 8
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 8
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 8
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 10
4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 15
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 16
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 20
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 21
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 21
4.3. Offline Review of Requested Actions . . . . . . . . . . . 25
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 27
6. Internationalization Considerations . . . . . . . . . . . . . 36
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 36
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 37
7.3. Role Type Values Registry . . . . . . . . . . . . . . . . 37
7.3.1. Registration Template . . . . . . . . . . . . . . . . 37
7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 38
8. Security Considerations . . . . . . . . . . . . . . . . . . . 38
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1. Normative References . . . . . . . . . . . . . . . . . . 39
9.2. Informative References . . . . . . . . . . . . . . . . . 40
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Organization Identifier . . . . . . . . . . . . . . . . . 4
3.2. Organization Roles . . . . . . . . . . . . . . . . . . . 4
3.2.1. Role Type . . . . . . . . . . . . . . . . . . . . . . 4
3.2.2. Role Status . . . . . . . . . . . . . . . . . . . . . 4
3.2.3. Role Identifier . . . . . . . . . . . . . . . . . . . 4
3.3. Contact and Client Identifiers . . . . . . . . . . . . . 5
3.4. Organization Status Values . . . . . . . . . . . . . . . 5
3.5. Role Status Values . . . . . . . . . . . . . . . . . . . 7
3.6. Parent Identifier . . . . . . . . . . . . . . . . . . . . 7
3.7. URL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.8. Dates and Times . . . . . . . . . . . . . . . . . . . . . 8
4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8
4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 8
4.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 8
4.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . 10
4.1.3. EPP <transfer> Query Command . . . . . . . . . . . . 15
4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 16
4.2.1. EPP <create> Command . . . . . . . . . . . . . . . . 16
4.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . 20
4.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21
4.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . 21
4.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 21
4.3. Offline Review of Requested Actions . . . . . . . . . . . 25
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 27
6. Internationalization Considerations . . . . . . . . . . . . . 36
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 36
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 37
7.3. Role Type Values Registry . . . . . . . . . . . . . . . . 37
7.3.1. Registration Template . . . . . . . . . . . . . . . . 37
7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 38
8. Security Considerations . . . . . . . . . . . . . . . . . . . 38
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1. Normative References . . . . . . . . . . . . . . . . . . 39
9.2. Informative References . . . . . . . . . . . . . . . . . 40
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41
There are many entities, such as registrars, resellers, DNS service operators, and privacy proxies, involved in the domain registration business. These kinds of entities have not been formally defined as having an object in Extensible Provisioning Protocol (EPP). This document provides a way to specify them as "organization" entities.
有许多实体，如注册商、转销商、DNS服务运营商和隐私代理，参与了域注册业务。在可扩展资源调配协议（EPP）中，这些类型的实体尚未正式定义为具有对象。本文档提供了将它们指定为“组织”实体的方法。
This document describes an organization object mapping for version 1.0 of the EPP [RFC5730]. This mapping is specified using XML 1.0 as described in [W3C.REC-xml-20081126] and XML Schema notation as described in [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028].
本文档描述了EPP[RFC5730]版本1.0的组织对象映射。使用[W3C.REC-XML-20081126]中所述的XML 1.0和[W3C.REC-xmlschema-1-20041028]和[W3C.REC-xmlschema-2-20041028]中所述的XML模式表示法指定此映射。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”在所有大写字母出现时（如图所示）应按照BCP 14[RFC2119][RFC8174]所述进行解释。
In examples, "C:" represents lines sent by a protocol client, and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not a required feature of this specification.
在示例中，“C:”表示协议客户端发送的行，“S:”表示协议服务器返回的行。示例中的缩进和空白仅用于说明元素关系，不是本规范的必需特征。
XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented.
XML区分大小写。除非另有说明，否则本文档中提供的XML规范和示例必须以所提供的字符大小写进行解释。
The XML namespace prefix "org" is used for the namespace "urn:ietf:params:xml:ns:epp:org-1.0", but implementations MUST NOT depend on it; instead, they should employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.
XML名称空间前缀“org”用于名称空间“urn:ietf:params:XML:ns:epp:org-1.0”，但实现不能依赖于它；相反，他们应该使用适当的名称空间感知XML解析器和序列化程序来解释和输出XML文档。
An EPP organization object has attributes and associated values that can be viewed and modified by the sponsoring client or the server. This section describes each attribute type in detail. The formal syntax for the attribute values described here can be found in the "Formal Syntax" section of this document and in the appropriate normative references.
EPP组织对象具有发起客户端或服务器可以查看和修改的属性和关联值。本节详细描述了每种属性类型。此处描述的属性值的正式语法可在本文件的“正式语法”部分和相应的规范性参考文件中找到。
All EPP organizations are identified by a server-unique identifier. Organization identifiers are character strings with a specified minimum length, a specified maximum length, and a specified format. Organization identifiers use the "clIDType" client identifier syntax described in [RFC5730]. The corresponding element is <org:id>.
所有EPP组织都由服务器唯一标识符标识。组织标识符是具有指定最小长度、指定最大长度和指定格式的字符串。组织标识符使用[RFC5730]中描述的“clIDType”客户端标识符语法。相应的元素是<org:id>。
The organization roles are used to represent the relationship an organization could have. The corresponding element is <org:role>. An organization object MUST always have at least one associated role. Roles can be set only by the client that sponsors an organization object. A client can change the role of an organization object using the EPP <update> command (see Section 4.2.5).
组织角色用于表示组织可能具有的关系。相应的元素是<org:role>。组织对象必须始终至少有一个关联角色。角色只能由发起组织对象的客户端设置。客户端可以使用EPP<update>命令更改组织对象的角色（参见第4.2.5节）。
An organization role MUST have a type field, which may have any of the values listed in Section 7.3. The corresponding element is <org:type>. An organization could have multiple roles with different role types.
组织角色必须具有类型字段，该字段可以具有第7.3节中列出的任何值。相应的元素是<org:type>。一个组织可以有多个具有不同角色类型的角色。
A role of an organization object MAY have its own statuses. The corresponding element is <org:status>. The possible values for the role status are defined in Section 3.5.
组织对象的角色可能有自己的状态。相应的元素是<org:status>。角色状态的可能值在第3.5节中定义。
A role MAY have a third-party-assigned identifier such as the IANA ID for registrars. The corresponding element is <org:roleID>.
角色可以具有第三方分配的标识符，例如注册者的IANA ID。相应的元素是<org:roleID>。
Example of organization role identifier:
组织角色标识符的示例：
<org:role>
<org:type>registrar</org:type>
<org:status>ok</org:status>
<org:status>linked</org:status>
<org:roleID>1362</org:roleID>
</org:role>
<org:role>
<org:type>registrar</org:type>
<org:status>ok</org:status>
<org:status>linked</org:status>
<org:roleID>1362</org:roleID>
</org:role>
All EPP contacts are identified by server-unique identifiers. Contact identifiers are character strings with a specified minimum length, a specified maximum length, and a specified format. Contact identifiers use the "clIDType" client identifier syntax described in [RFC5730].
所有EPP联系人都由服务器唯一标识符标识。联系人标识符是具有指定最小长度、指定最大长度和指定格式的字符串。联系人标识符使用[RFC5730]中描述的“clIDType”客户端标识符语法。
An organization object MUST always have at least one associated status value. Status values can be set only by the client that sponsors an organization object and by the server on which the object resides. A client can change the status of an organization object using the EPP <update> command. Each status value MAY be accompanied by a string of human-readable text that describes the rationale for the status applied to the object.
组织对象必须始终至少有一个关联的状态值。状态值只能由发起组织对象的客户端和对象所在的服务器设置。客户端可以使用EPP<update>命令更改组织对象的状态。每个状态值可能伴随着一个人类可读文本字符串，该字符串描述了应用于对象的状态的基本原理。
A client MUST NOT alter server status values set by the server. A server MAY alter or override status values set by a client, subject to local server policies. The status of an object MAY change as a result of either a client-initiated transform command or an action performed by a server operator.
客户端不得更改服务器设置的服务器状态值。根据本地服务器策略，服务器可以更改或覆盖客户端设置的状态值。对象的状态可能会因客户端启动的转换命令或服务器操作员执行的操作而改变。
Status values that can be added or removed by a client are prefixed with "client". Corresponding server status values that can be added or removed by a server are prefixed with "server". The "hold" and "terminated" status values are server managed when the organization has no parent identifier (Section 3.6) and otherwise MAY be client managed based on server policy. Other status values that do not begin with either "client" or "server" are server managed.
客户端可以添加或删除的状态值以“客户端”作为前缀。可由服务器添加或删除的相应服务器状态值以“服务器”作为前缀。当组织没有父标识符（第3.6节）时，“保持”和“终止”状态值由服务器管理，否则可根据服务器策略由客户端管理。其他不以“客户端”或“服务器”开头的状态值由服务器管理。
Status Value Descriptions:
状态值说明：
o ok: This is the normal status value for an object that has no operations pending or active prohibitions. This value is set and removed by the server as other status values are added or removed.
o 确定：这是没有操作挂起或活动禁止的对象的正常状态值。当添加或删除其他状态值时，服务器将设置和删除此值。
o hold: Organization transform commands and new links MUST be rejected.
o 保留：必须拒绝组织转换命令和新链接。
o terminated: The organization that has been terminated MUST NOT be linked. Organization transform commands and new links MUST be rejected.
o 已终止：不能链接已终止的组织。必须拒绝组织转换命令和新链接。
o linked: The organization object has at least one active association with another object. The "linked" status is not explicitly set by the client. Servers should provide services to determine existing object associations.
o 链接：组织对象与另一个对象至少有一个活动关联。客户端未明确设置“链接”状态。服务器应提供确定现有对象关联的服务。
o clientLinkProhibited, serverLinkProhibited: Requests to add new links to the organization MUST be rejected.
o ClientLinkProbited、ServerLinkProbited：必须拒绝向组织添加新链接的请求。
o clientUpdateProhibited, serverUpdateProhibited: Requests to update the object (other than to remove this status) MUST be rejected.
o clientUpdateProhibited、serverUpdateProhibited：必须拒绝更新对象（而不是删除此状态）的请求。
o clientDeleteProhibited, serverDeleteProhibited: Requests to delete the object MUST be rejected.
o ClientDelete禁止，ServerDelete禁止：删除对象的请求必须被拒绝。
o pendingCreate, pendingUpdate, pendingDelete: A transform command has been processed for the object, but the action has not been completed by the server. Server operators can delay action completion for a variety of reasons, such as to allow for human review or third-party action. A transform command that is processed, but whose requested action is pending, is noted with response code 1001.
o pendingCreate、pendingUpdate、pendingDelete：已为对象处理转换命令，但服务器尚未完成该操作。服务器操作员可以出于各种原因延迟操作完成，例如允许人工审核或第三方操作。已处理但其请求的操作处于挂起状态的转换命令用响应代码1001表示。
"pendingCreate", "ok", "hold", and "terminated" are mutually exclusive statuses. An organization MUST have exactly one of these statuses set.
“pendingCreate”、“ok”、“hold”和“terminated”是相互排斥的状态。组织必须恰好设置了其中一种状态。
"ok" status MAY only be combined with "linked" status.
“确定”状态只能与“链接”状态组合。
A client or server MAY combine "linked" with either "clientLinkProhibited" or "serverLinkProhibited" if new links must be prohibited.
如果必须禁止新链接，则客户端或服务器可以将“链接”与“ClientLinkProbited”或“ServerLinkProbited”组合。
"pendingDelete" status MUST NOT be combined with either "clientDeleteProhibited" or "serverDeleteProhibited" status.
“pendingDelete”状态不能与“ClientDelete禁止”或“ServerDelete禁止”状态组合。
The "pendingCreate", "pendingDelete", and "pendingUpdate" status values MUST NOT be combined with each other.
“pendingCreate”、“pendingDelete”和“pendingUpdate”状态值不得相互组合。
If "clientUpdateProhibited" or "serverUpdateProhibited" is set, the client will not be able to update the object. For "clientUpdateProhibited", the client will first need to remove "clientUpdateProhibited" prior to attempting to update the object. The server can modify the object at any time.
如果设置了“clientUpdateProhibited”或“serverUpdateProhibited”，则客户端将无法更新对象。对于“clientUpdateProhibited”，在尝试更新对象之前，客户端首先需要删除“clientUpdateProhibited”。服务器可以随时修改对象。
A role SHOULD have at least one associated status value. Valid values include "ok", "linked", "clientLinkProhibited", and "serverLinkProhibited".
角色应至少具有一个关联的状态值。有效值包括“ok”、“linked”、“ClientLinkProbited”和“ServerLinkProbited”。
Status Value Descriptions:
状态值说明：
o ok: This is the normal status value for a role that has no operations pending or active prohibitions. This value is set and removed by the server as other status values are added or removed.
o 确定：这是没有操作挂起或活动禁止的角色的正常状态值。当添加或删除其他状态值时，服务器将设置和删除此值。
o linked: The role of an organization object has at least one active association with another object. The "linked" status is not explicitly set by the client. Servers SHOULD provide services to determine existing object associations.
o 链接：组织对象的角色至少与另一个对象有一个活动关联。客户端未明确设置“链接”状态。服务器应提供确定现有对象关联的服务。
o clientLinkProhibited, serverLinkProhibited: Requests to add new links to the role MUST be rejected.
o ClientLinkProbited、ServerLinkProbited：必须拒绝向角色添加新链接的请求。
Organizations can have more than one layer. The parent identifier, as defined with the <org:parentId> element, represents the parent organization identifier in a child organization.
组织可以有多个层。父标识符由<org:parentId>元素定义，表示子组织中的父组织标识符。
The case of reseller organizations provides an example. The parent identifier is not defined for the top-level reseller, namely the registrar of the registry. An N-tier reseller has a parent reseller and at least one child reseller. A reseller customer has a parent reseller and no child resellers.
分销商组织的案例就是一个例子。没有为顶级分销商（即注册中心的注册商）定义父标识符。N级转销商有父转销商和至少一个子转销商。转销商客户有父转销商，没有子转销商。
Loops MUST be prohibited. For example: if organization A has organization B as its parent identifier, organization B cannot have organization A as its parent identifier. The same is true for larger loops involving three or more organizations.
必须禁止循环。例如：如果组织A将组织B作为其父标识符，则组织B不能将组织A作为其父标识符。对于涉及三个或更多组织的较大循环也是如此。
The URL represents the organization web home page, as defined with the <org:url> element.
URL表示组织web主页，如<org:URL>元素所定义。
Date and time attribute values MUST be represented in Coordinated Universal Time (UTC) using the Gregorian calendar. The extended date-time form using uppercase "T" and "Z" characters defined in [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time values, as XML Schema does not support truncated date-time forms or lowercase "T" and "Z" characters.
日期和时间属性值必须使用公历以协调世界时（UTC）表示。必须使用[W3C.REC-xmlschema-2-20041028]中定义的大写“T”和“Z”字符的扩展日期时间形式来表示日期时间值，因为XML模式不支持截断日期时间形式或小写“T”和“Z”字符。
A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in provisioning and managing organization information via EPP.
EPP语法和语义的详细描述可在EPP核心协议规范[RFC5730]中找到。这里描述的命令映射专门用于通过EPP提供和管理组织信息。
EPP provides two commands to retrieve organization information: <check> to determine if an organization object can be provisioned within a repository and <info> to retrieve detailed information associated with an organization object. This document does not define a mapping for the EPP <transfer> command to retrieve organization-object transfer status information.
EPP提供了两个用于检索组织信息的命令：<check>用于确定是否可以在存储库中配置组织对象，以及<info>用于检索与组织对象关联的详细信息。本文档未定义用于检索组织对象转移状态信息的EPP<transfer>命令的映射。
The EPP <check> command is used to determine if an object can be provisioned within a repository. It provides a hint that allows a client to anticipate the success or failure of provisioning an object using the <create> command, as object-provisioning requirements are ultimately a matter of server policy.
EPP<check>命令用于确定是否可以在存储库中配置对象。它提供了一个提示，允许客户端预测使用<create>命令设置对象的成功或失败，因为对象设置要求最终取决于服务器策略。
In addition to the standard EPP command elements, the <check> command MUST contain an <org:check> element. This element or its ancestor element MUST identify the organization namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:check> element contains the following child elements:
除了标准的EPP命令元素外，<check>命令还必须包含<org:check>元素。此元素或其祖先元素必须标识组织名称空间“urn:ietf:params:xml:ns:epp:org-1.0”。<org:check>元素包含以下子元素：
o One or more <org:id> elements that contain the server-unique identifier of the organization objects to be queried.
o 包含要查询的组织对象的服务器唯一标识符的一个或多个<org:id>元素。
Example <check> command:
示例<check>命令：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <check>
C: <org:check
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: <org:id>re1523</org:id>
C: <org:id>1523res</org:id>
C: </org:check>
C: </check>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <check>
C: <org:check
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: <org:id>re1523</org:id>
C: <org:id>1523res</org:id>
C: </org:check>
C: </check>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When a <check> command has been processed successfully, the EPP <resData> element MUST contain a child <org:chkData> element. This element or its ancestor element MUST identify the organization namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:chkData> element contains one or more <org:cd> elements that contain the following child elements:
成功处理<check>命令后，EPP<resData>元素必须包含一个子<org:chkData>元素。此元素或其祖先元素必须标识组织名称空间“urn:ietf:params:xml:ns:epp:org-1.0”。<org:chkData>元素包含一个或多个<org:cd>元素，这些元素包含以下子元素：
o An <org:id> element that identifies the queried object. This element MUST contain an "avail" attribute whose value indicates object availability (can it be provisioned or not) at the moment the <check> command was completed. A value of "1" or "true" means that the object can be provisioned. A value of "0" or "false" means that the object cannot be provisioned.
o 标识查询对象的<org:id>元素。此元素必须包含一个“avail”属性，该属性的值表示在<check>命令完成时对象的可用性（是否可以设置）。值“1”或“true”表示可以设置对象。值“0”或“false”表示无法设置对象。
o An OPTIONAL <org:reason> element that may be provided when an object cannot be provisioned. If present, this element contains server-specific text to help explain why the object cannot be provisioned. This text MUST be represented in the response language previously negotiated with the client; an OPTIONAL "lang" attribute as defined in [RFC5646] may be present to identify the language if the negotiated value is something other than the default value of "en"(English).
o 一个可选的<org:reason>元素，当无法设置对象时可以提供该元素。如果存在，此元素包含特定于服务器的文本，以帮助解释无法设置对象的原因。该文本必须以之前与客户协商的回复语言表示；如果协商值不是默认值“en”（英语），则可能存在[RFC5646]中定义的可选“lang”属性来标识语言。
Example <check> response:
示例<check>响应：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <resData>
S: <org:chkData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:cd>
S: <org:id avail="1">res1523</org:id>
S: </org:cd>
S: <org:cd>
S: <org:id avail="0">re1523</org:id>
S: <org:reason lang="en">In use</org:reason>
S: </org:cd>
S: <org:cd>
S: <org:id avail="1">1523res</org:id>
S: </org:cd>
S: </org:chkData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <resData>
S: <org:chkData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:cd>
S: <org:id avail="1">res1523</org:id>
S: </org:cd>
S: <org:cd>
S: <org:id avail="0">re1523</org:id>
S: <org:reason lang="en">In use</org:reason>
S: </org:cd>
S: <org:cd>
S: <org:id avail="1">1523res</org:id>
S: </org:cd>
S: </org:chkData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
An EPP error response MUST be returned if a <check> command cannot be processed for any reason.
如果由于任何原因无法处理<check>命令，则必须返回EPP错误响应。
The EPP <info> command is used to retrieve information associated with an organization object. In addition to the standard EPP command elements, the <info> command MUST contain an <org:info> element. This element or its ancestor element MUST identify the organization namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:info> element contains the following child element:
EPP<info>命令用于检索与组织对象关联的信息。除了标准的EPP命令元素外，<info>命令还必须包含<org:info>元素。此元素或其祖先元素必须标识组织名称空间“urn:ietf:params:xml:ns:epp:org-1.0”。<org:info>元素包含以下子元素：
o An <org:id> element that contains the server-unique identifier of the organization object to be queried.
o 包含要查询的组织对象的服务器唯一标识符的<org:id>元素。
Example <info> command:
示例<info>命令：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <info>
C: <org:info
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: </org:info>
C: </info>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <info>
C: <org:info
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: </org:info>
C: </info>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When an <info> command has been processed successfully, the EPP <resData> element MUST contain a child <org:infData> element. This element or its ancestor element MUST identify the organization namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:infData> element contains the following child elements:
成功处理<info>命令后，EPP<resData>元素必须包含子<org:infData>元素。此元素或其祖先元素必须标识组织名称空间“urn:ietf:params:xml:ns:epp:org-1.0”。<org:infData>元素包含以下子元素：
o An <org:id> element that contains the server-unique identifier of the organization object, as defined in Section 3.1.
o 一个<org:id>元素，包含组织对象的服务器唯一标识符，如第3.1节所定义。
o An <org:roid> element that contains the Repository Object Identifier assigned to the organization object when the object was created.
o 一个<org:roid>元素，包含创建对象时分配给组织对象的存储库对象标识符。
o One or more <org:role> elements that contain the role type, role statuses, and optional role ID of the organization.
o 包含组织的角色类型、角色状态和可选角色ID的一个或多个<org:role>元素。
* An <org:type> element that contains the type of the organization, as defined in Section 3.2.
* 一个<org:type>元素，包含第3.2节中定义的组织类型。
* One or more <org:status> elements that contain the role statuses. The values of the role status are defined in Section 3.5.
* 包含角色状态的一个或多个<org:status>元素。角色状态的值在第3.5节中定义。
* An OPTIONAL <org:roleID> element that contains a third-party-assigned identifier, such as IANA ID for registrars, as defined in Section 3.2.3.
* 一个可选的<org:roleID>元素，包含第三方分配的标识符，如第3.2.3节中定义的注册者的IANA ID。
o One or more <org:status> elements that contain the operational status of the organization, as defined in Section 3.4.
o 一个或多个<org:status>元素，包含第3.4节中定义的组织运行状态。
o An OPTIONAL <org:parentId> element that contains the identifier of the parent object, as defined in Section 3.6.
o 一个可选的<org:parentId>元素，包含父对象的标识符，如第3.6节所定义。
o Zero to two <org:postalInfo> elements that contain postal-address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, element content MUST be represented in a subset of Unicode [UNICODE] in the range U+0020 - U+007E. If a localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The <org:postalInfo> element contains the following child elements:
o 零到两个包含邮政地址信息的<org:postalInfo>元素。提供了两个元素，以便以国际化和本地化形式提供地址信息；“type”属性用于标识这两种形式。如果提供了国际化表单（type=“int”），则元素内容必须在U+0020-U+007E范围内的Unicode[Unicode]子集中表示。如果提供了本地化形式（type=“loc”），元素内容可以用不受限制的UTF-8表示。<org:postalInfo>元素包含以下子元素：
* An <org:name> element that contains the name of the organization.
* 包含组织名称的<org:name>元素。
* An OPTIONAL <org:addr> element that contains address information associated with the organization. An <org:addr> element contains the following child elements:
* 可选的<org:addr>元素，包含与组织关联的地址信息。<org:addr>元素包含以下子元素：
+ One, two, or three <org:street> elements that contain the organization's street address.
+ 包含组织街道地址的一个、两个或三个<org:street>元素。
+ An <org:city> element that contains the organization's city.
+ 包含组织所在城市的<org:city>元素。
+ An OPTIONAL <org:sp> element that contains the organization's state or province.
+ 可选的<org:sp>元素，包含组织的州或省。
+ An OPTIONAL <org:pc> element that contains the organization's postal code.
+ 包含组织邮政编码的可选<org:pc>元素。
+ An <org:cc> element that contains the alpha-2 organization's country code. The detailed format of this element is described in Section 2.4.3 of [RFC5733].
+ 包含alpha-2组织的国家代码的<org:cc>元素。[RFC5733]第2.4.3节描述了该元素的详细格式。
o An OPTIONAL <org:voice> element that contains the organization's voice telephone number. The detailed format of this element is described in Section 2.5 of [RFC5733].
o 可选的<org:voice>元素，包含组织的语音电话号码。[RFC5733]第2.5节描述了该元素的详细格式。
o An OPTIONAL <org:fax> element that contains the organization's facsimile telephone number. The detailed format of this element is described in Section 2.5 of [RFC5733].
o 包含组织传真电话号码的可选<org:fax>元素。[RFC5733]第2.5节描述了该元素的详细格式。
o An OPTIONAL <org:email> element that contains the organization's email address. The detailed format of this element is described in [RFC5322].
o 包含组织电子邮件地址的可选<org:email>元素。[RFC5322]中描述了该元素的详细格式。
o An OPTIONAL <org:url> element that contains the URL to the website of the organization. The detailed format of this element is described in [RFC3986].
o 可选的<org:url>元素，包含指向组织网站的url。[RFC3986]中描述了该元素的详细格式。
o Zero or more <org:contact> elements that contain identifiers for the contact objects to be associated with the organization object. Contact object identifiers MUST be known to the server before the contact object can be associated with the organization object. The required "type" is used to represent contact types. The type values include "admin", "tech", "billing", "abuse", and "custom". The OPTIONAL "typeName" attribute is used to define the name of a "custom" type.
o 零个或多个<org:contact>元素，其中包含要与组织对象关联的联系人对象的标识符。在联系人对象与组织对象关联之前，服务器必须知道联系人对象标识符。所需的“类型”用于表示触点类型。类型值包括“管理”、“技术”、“计费”、“滥用”和“自定义”。可选的“typeName”属性用于定义“自定义”类型的名称。
o An OPTIONAL <org:clID> element that contains the organization identifier of the sponsoring client. There is no <org:clID> element if the organization is managed by the registry.
o 一个可选的<org:clID>元素，包含发起客户端的组织标识符。如果组织由注册表管理，则没有<org:clID>元素。
o An <org:crID> element that contains the identifier of the client that created the organization object.
o 包含创建组织对象的客户端标识符的<org:crID>元素。
o An <org:crDate> element that contains the date and time of organization object creation.
o 包含组织对象创建日期和时间的<org:crDate>元素。
o An <org:upID> element that contains the identifier of the client that last updated the organization object. This element MUST NOT be present if the organization has never been modified.
o 包含上次更新组织对象的客户端标识符的<org:upID>元素。如果从未修改过组织，则此元素不得存在。
o An <org:upDate> element that contains the date and time of the most recent organization object modification. This element MUST NOT be present if the organization object has never been modified.
o 一个<org:upDate>元素，包含最近一次组织对象修改的日期和时间。如果从未修改过组织对象，则此元素不得存在。
Example <info> response for "Example Registrar Inc." organization object with identifier "registrar1362":
标识符为“registrar1362”的“Example Registrator Inc.”组织对象的响应示例：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <resData>
S: <org:infData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>registrar1362</org:id>
S: <org:roid>registrar1362-REP</org:roid>
S: <org:role>
S: <org:type>registrar</org:type>
S: <org:status>ok</org:status>
S: <org:status>linked</org:status>
S: <org:roleID>1362</org:roleID>
S: </org:role>
S: <org:status>ok</org:status>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <resData>
S: <org:infData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>registrar1362</org:id>
S: <org:roid>registrar1362-REP</org:roid>
S: <org:role>
S: <org:type>registrar</org:type>
S: <org:status>ok</org:status>
S: <org:status>linked</org:status>
S: <org:roleID>1362</org:roleID>
S: </org:role>
S: <org:status>ok</org:status>
S: <org:postalInfo type="int">
S: <org:name>Example Registrar Inc.</org:name>
S: <org:addr>
S: <org:street>123 Example Dr.</org:street>
S: <org:street>Suite 100</org:street>
S: <org:city>Dulles</org:city>
S: <org:sp>VA</org:sp>
S: <org:pc>20166-6503</org:pc>
S: <org:cc>US</org:cc>
S: </org:addr>
S: </org:postalInfo>
S: <org:voice x="1234">+1.7035555555</org:voice>
S: <org:fax>+1.7035555556</org:fax>
S: <org:email>contact@organization.example</org:email>
S: <org:url>https://organization.example</org:url>
S: <org:contact type="admin">sh8013</org:contact>
S: <org:contact type="billing">sh8013</org:contact>
S: <org:contact type="custom"
S: typeName="legal">sh8013</org:contact>
S: <org:crID>ClientX</org:crID>
S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: <org:upID>ClientX</org:upID>
S: <org:upDate>2018-12-03T09:00:00.0Z</org:upDate>
S: </org:infData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S: <org:postalInfo type="int">
S: <org:name>Example Registrar Inc.</org:name>
S: <org:addr>
S: <org:street>123 Example Dr.</org:street>
S: <org:street>Suite 100</org:street>
S: <org:city>Dulles</org:city>
S: <org:sp>VA</org:sp>
S: <org:pc>20166-6503</org:pc>
S: <org:cc>US</org:cc>
S: </org:addr>
S: </org:postalInfo>
S: <org:voice x="1234">+1.7035555555</org:voice>
S: <org:fax>+1.7035555556</org:fax>
S: <org:email>contact@organization.example</org:email>
S: <org:url>https://organization.example</org:url>
S: <org:contact type="admin">sh8013</org:contact>
S: <org:contact type="billing">sh8013</org:contact>
S: <org:contact type="custom"
S: typeName="legal">sh8013</org:contact>
S: <org:crID>ClientX</org:crID>
S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: <org:upID>ClientX</org:upID>
S: <org:upDate>2018-12-03T09:00:00.0Z</org:upDate>
S: </org:infData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
Example <info> response for "Example Reseller Inc." organization object of reseller type managed by identifier "registrar1362":
由标识符“registrar1362”管理的经销商类型的“示例经销商公司”组织对象的示例<info>响应：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <resData>
S: <org:infData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>reseller1523</org:id>
S: <org:roid>reseller1523-REP</org:roid>
S: <org:role>
S: <org:type>reseller</org:type>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <resData>
S: <org:infData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>reseller1523</org:id>
S: <org:roid>reseller1523-REP</org:roid>
S: <org:role>
S: <org:type>reseller</org:type>
S: <org:status>ok</org:status>
S: <org:status>linked</org:status>
S: </org:role>
S: <org:status>ok</org:status>
S: <org:parentId>registrar1362</org:parentId>
S: <org:postalInfo type="int">
S: <org:name>Example Reseller Inc.</org:name>
S: <org:addr>
S: <org:street>123 Example Dr.</org:street>
S: <org:street>Suite 100</org:street>
S: <org:city>Dulles</org:city>
S: <org:sp>VA</org:sp>
S: <org:pc>20166-6503</org:pc>
S: <org:cc>US</org:cc>
S: </org:addr>
S: </org:postalInfo>
S: <org:fax>+1.7035555556</org:fax>
S: <org:url>https://organization.example</org:url>
S: <org:contact type="admin">sh8013</org:contact>
S: <org:clID>1362</org:clID>
S: <org:crID>ClientX</org:crID>
S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: <org:upID>ClientX</org:upID>
S: <org:upDate>2018-12-03T09:00:00.0Z</org:upDate>
S: </org:infData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S: <org:status>ok</org:status>
S: <org:status>linked</org:status>
S: </org:role>
S: <org:status>ok</org:status>
S: <org:parentId>registrar1362</org:parentId>
S: <org:postalInfo type="int">
S: <org:name>Example Reseller Inc.</org:name>
S: <org:addr>
S: <org:street>123 Example Dr.</org:street>
S: <org:street>Suite 100</org:street>
S: <org:city>Dulles</org:city>
S: <org:sp>VA</org:sp>
S: <org:pc>20166-6503</org:pc>
S: <org:cc>US</org:cc>
S: </org:addr>
S: </org:postalInfo>
S: <org:fax>+1.7035555556</org:fax>
S: <org:url>https://organization.example</org:url>
S: <org:contact type="admin">sh8013</org:contact>
S: <org:clID>1362</org:clID>
S: <org:crID>ClientX</org:crID>
S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: <org:upID>ClientX</org:upID>
S: <org:upDate>2018-12-03T09:00:00.0Z</org:upDate>
S: </org:infData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
An EPP error response MUST be returned if an <info> command cannot be processed for any reason.
如果由于任何原因无法处理<info>命令，则必须返回EPP错误响应。
The transfer semantics do not apply to organization objects. No EPP <transfer> query command is defined in this document.
传输语义不适用于组织对象。本文档中未定义EPP<transfer>查询命令。
This document provides three commands to transform organization object information: <create> to create an instance of an organization object, <delete> to delete an instance of an organization object, and <update> to change information associated with an organization object. This document does not define a mapping for the EPP <transfer> and <renew> command.
本文档提供了三个用于转换组织对象信息的命令：<create>用于创建组织对象的实例，<delete>用于删除组织对象的实例，以及<update>用于更改与组织对象关联的信息。本文档未定义EPP<transfer>和<renew>命令的映射。
Transform commands are typically processed and completed in real time. Server operators MAY receive and process transform commands but defer completing the requested action if human or third-party review is required before the requested action can be completed. In such situations, the server MUST return a 1001 response code to the client to note that the command has been received and processed but that the requested action is pending. The server MUST also manage the status of the object that is the subject of the command to reflect the initiation and completion of the requested action. Once the action has been completed, the client MUST be notified using a service message that the action has been completed and the status of the object has changed. Other notification methods MAY be used in addition to the required service message.
转换命令通常是实时处理和完成的。服务器操作员可以接收和处理转换命令，但如果在完成请求的操作之前需要人工或第三方审核，则推迟完成请求的操作。在这种情况下，服务器必须向客户端返回1001响应代码，以注意命令已被接收和处理，但请求的操作处于挂起状态。服务器还必须管理作为命令主题的对象的状态，以反映请求操作的启动和完成。操作完成后，必须使用服务消息通知客户端操作已完成且对象的状态已更改。除了所需的服务消息之外，还可以使用其他通知方法。
The EPP <create> command provides a transform operation that allows a client to create an organization object. In addition to the standard EPP command elements, the <create> command MUST contain an <org:create> element. This element or its ancestor element MUST identify the organization namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:create> element contains the following child elements:
EPP<create>命令提供了一个转换操作，允许客户端创建组织对象。除了标准的EPP命令元素外，<create>命令还必须包含<org:create>元素。此元素或其祖先元素必须标识组织名称空间“urn:ietf:params:xml:ns:epp:org-1.0”。<org:create>元素包含以下子元素：
o An <org:id> element that contains the desired server-unique identifier for the organization to be created, as defined in Section 3.1.
o 一个<org:id>元素，包含要创建的组织所需的服务器唯一标识符，如第3.1节所定义。
o One or more <org:role> elements that contain the role type, role statuses, and optional role ID of the organization.
o 包含组织的角色类型、角色状态和可选角色ID的一个或多个<org:role>元素。
* An <org:type> element that contains the type of the organization, as defined in Section 3.2.
* 一个<org:type>元素，包含第3.2节中定义的组织类型。
* Zero or more <org:status> elements that contain the role statuses. The possible values of the role statuses are defined in Section 3.5.
* 零个或多个包含角色状态的<org:status>元素。第3.5节定义了角色状态的可能值。
* An OPTIONAL <org:roleID> element that contains a third-party-assigned identifier, such as IANA ID for registrars, as defined in Section 3.2.3.
* 一个可选的<org:roleID>元素，包含第三方分配的标识符，如第3.2.3节中定义的注册者的IANA ID。
o Zero or more <org:status> elements that contain the operational status of the organization, as defined in Section 3.4.
o 零个或多个<org:status>元素，包含第3.4节中定义的组织运行状态。
o An OPTIONAL <org:parentId> element that contains the identifier of the parent object, as defined in Section 3.6.
o 一个可选的<org:parentId>元素，包含父对象的标识符，如第3.6节所定义。
o Zero to two <org:postalInfo> elements that contain postal-address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, element content MUST be represented in a subset of Unicode [UNICODE] in the range U+0020 - U+007E. If a localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The <org:postalInfo> element contains the following child elements:
o 零到两个包含邮政地址信息的<org:postalInfo>元素。提供了两个元素，以便以国际化和本地化形式提供地址信息；“type”属性用于标识这两种形式。如果提供了国际化表单（type=“int”），则元素内容必须在U+0020-U+007E范围内的Unicode[Unicode]子集中表示。如果提供了本地化形式（type=“loc”），元素内容可以用不受限制的UTF-8表示。<org:postalInfo>元素包含以下子元素：
* An <org:name> element that contains the name of the organization.
* 包含组织名称的<org:name>元素。
* An OPTIONAL <org:addr> element that contains address information associated with the organization. An <org:addr> element contains the following child elements:
* 可选的<org:addr>元素，包含与组织关联的地址信息。<org:addr>元素包含以下子元素：
+ One, two, or three <org:street> elements that contain the organization's street address.
+ 包含组织街道地址的一个、两个或三个<org:street>元素。
+ An <org:city> element that contains the organization's city.
+ 包含组织所在城市的<org:city>元素。
+ An OPTIONAL <org:sp> element that contains the organization's state or province.
+ 可选的<org:sp>元素，包含组织的州或省。
+ An OPTIONAL <org:pc> element that contains the organization's postal code.
+ 包含组织邮政编码的可选<org:pc>元素。
+ An <org:cc> element that contains the alpha-2 organization's country code. The detailed format of this element is described in Section 2.4.3 of [RFC5733].
+ 包含alpha-2组织的国家代码的<org:cc>元素。[RFC5733]第2.4.3节描述了该元素的详细格式。
o An OPTIONAL <org:voice> element that contains the organization's voice telephone number. The detailed format of this element is described in Section 2.5 of [RFC5733].
o 可选的<org:voice>元素，包含组织的语音电话号码。[RFC5733]第2.5节描述了该元素的详细格式。
o An OPTIONAL <org:fax> element that contains the organization's facsimile telephone number. The detailed format of this element is described in Section 2.5 of [RFC5733].
o 包含组织传真电话号码的可选<org:fax>元素。[RFC5733]第2.5节描述了该元素的详细格式。
o An OPTIONAL <org:email> element that contains the organization's email address. The detailed format of this element is described of [RFC5322].
o 包含组织电子邮件地址的可选<org:email>元素。[RFC5322]中描述了该元素的详细格式。
o An OPTIONAL <org:url> element that contains the URL to the website of the organization. The detailed format of this element is described in [RFC3986].
o 可选的<org:url>元素，包含指向组织网站的url。[RFC3986]中描述了该元素的详细格式。
o Zero or more <org:contact> elements that contain identifiers for the contact objects associated with the organization object.
o 零个或多个<org:contact>元素，其中包含与组织对象关联的联系人对象的标识符。
Example <create> command:
示例<create>命令：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <create>
C: <org:create
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: <org:role>
C: <org:type>reseller</org:type>
C: </org:role>
C: <org:parentId>1523res</org:parentId>
C: <org:postalInfo type="int">
C: <org:name>Example Organization Inc.</org:name>
C: <org:addr>
C: <org:street>123 Example Dr.</org:street>
C: <org:street>Suite 100</org:street>
C: <org:city>Dulles</org:city>
C: <org:sp>VA</org:sp>
C: <org:pc>20166-6503</org:pc>
C: <org:cc>US</org:cc>
C: </org:addr>
C: </org:postalInfo>
C: <org:voice x="1234">+1.7035555555</org:voice>
C: <org:fax>+1.7035555556</org:fax>
C: <org:email>contact@organization.example</org:email>
C: <org:url>https://organization.example</org:url>
C: <org:contact type="admin">sh8013</org:contact>
C: <org:contact type="billing">sh8013</org:contact>
C: </org:create>
C: </create>
C: <clTRID>ABC-12345</clTRID>
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <create>
C: <org:create
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: <org:role>
C: <org:type>reseller</org:type>
C: </org:role>
C: <org:parentId>1523res</org:parentId>
C: <org:postalInfo type="int">
C: <org:name>Example Organization Inc.</org:name>
C: <org:addr>
C: <org:street>123 Example Dr.</org:street>
C: <org:street>Suite 100</org:street>
C: <org:city>Dulles</org:city>
C: <org:sp>VA</org:sp>
C: <org:pc>20166-6503</org:pc>
C: <org:cc>US</org:cc>
C: </org:addr>
C: </org:postalInfo>
C: <org:voice x="1234">+1.7035555555</org:voice>
C: <org:fax>+1.7035555556</org:fax>
C: <org:email>contact@organization.example</org:email>
C: <org:url>https://organization.example</org:url>
C: <org:contact type="admin">sh8013</org:contact>
C: <org:contact type="billing">sh8013</org:contact>
C: </org:create>
C: </create>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
C: </command>
C:</epp>
When a <create> command has been processed successfully, the EPP <resData> element MUST contain a child <org:creData> element. This element or its ancestor element MUST identify the organization namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:creData> element contains the following child elements:
成功处理<create>命令后，EPP<resData>元素必须包含一个子<org:creData>元素。此元素或其祖先元素必须标识组织名称空间“urn:ietf:params:xml:ns:epp:org-1.0”。<org:creData>元素包含以下子元素：
o An <org:id> element that contains the server-unique identifier for the created organization, as defined in Section 3.1.
o 一个<org:id>元素，包含所创建组织的服务器唯一标识符，如第3.1节所定义。
o An <org:crDate> element that contains the date and time of organization-object creation.
o 包含组织对象创建日期和时间的<org:crDate>元素。
Example <create> response:
示例<create>响应：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <resData>
S: <org:creData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>res1523</org:id>
S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: </org:creData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <resData>
S: <org:creData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>res1523</org:id>
S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: </org:creData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
An EPP error response MUST be returned if a <create> command cannot be processed for any reason.
如果由于任何原因无法处理<create>命令，则必须返回EPP错误响应。
The EPP <delete> command provides a transform operation that allows a client to delete an organization object. In addition to the standard EPP command elements, the <delete> command MUST contain an <org:delete> element. This element or its ancestor element MUST identify the organization namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:delete> element MUST contain the following child element:
EPP<delete>命令提供了一个转换操作，允许客户端删除组织对象。除了标准的EPP命令元素外，<delete>命令还必须包含<org:delete>元素。此元素或其祖先元素必须标识组织名称空间“urn:ietf:params:xml:ns:epp:org-1.0”。<org:delete>元素必须包含以下子元素：
o An <org:id> element that contains the server-unique identifier of the organization object to be deleted, as defined in Section 3.1.
o 一个<org:id>元素，包含要删除的组织对象的服务器唯一标识符，如第3.1节所定义。
An organization object MUST NOT be deleted if it is associated with other known objects. An associated organization MUST NOT be deleted until associations with other known objects have been broken. A server MUST notify clients that object relationships exist by sending a 2305 error response code when a <delete> command is attempted and fails due to existing object relationships.
如果组织对象与其他已知对象关联，则不能将其删除。在与其他已知对象的关联被破坏之前，不得删除关联的组织。当尝试执行<delete>命令并且由于现有对象关系而失败时，服务器必须通过发送2305错误响应代码来通知客户端存在对象关系。
Example <delete> command:
示例<delete>命令：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <delete>
C: <org:delete
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: </org:delete>
C: </delete>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <delete>
C: <org:delete
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: </org:delete>
C: </delete>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When a <delete> command has been processed successfully, a server MUST respond with an EPP response with no <resData> element.
成功处理<delete>命令后，服务器必须使用不带<resData>元素的EPP响应进行响应。
Example <delete> response:
示例<delete>响应：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
An EPP error response MUST be returned if a <delete> command cannot be processed for any reason.
如果由于任何原因无法处理<delete>命令，则必须返回EPP错误响应。
Renewal semantics do not apply to organization objects, so there is no mapping defined for the EPP <renew> command.
更新语义不适用于组织对象，因此没有为EPP<renew>命令定义映射。
Transfer semantics do not apply to organization objects, so there is no mapping defined for the EPP <transfer> command.
传输语义不适用于组织对象，因此没有为EPP<Transfer>命令定义映射。
The EPP <update> command provides a transform operation that allows a client to modify the attributes of an organization object. In addition to the standard EPP command elements, the <update> command MUST contain an <org:update> element. This element or its ancestor element MUST identify the organization namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:update> element contains the following child elements:
EPP<update>命令提供转换操作，允许客户端修改组织对象的属性。除了标准EPP命令元素外，<update>命令还必须包含<org:update>元素。此元素或其祖先元素必须标识组织名称空间“urn:ietf:params:xml:ns:epp:org-1.0”。<org:update>元素包含以下子元素：
o An <org:id> element that contains the server-unique identifier of the organization object to be updated, as defined in Section 3.1.
o 一个<org:id>元素，包含要更新的组织对象的服务器唯一标识符，如第3.1节所定义。
o An OPTIONAL <org:add> element that contains attribute values to be added to the object.
o 可选的<org:add>元素，包含要添加到对象的属性值。
o An OPTIONAL <org:rem> element that contains attribute values to be removed from the object.
o 可选的<org:rem>元素，包含要从对象中删除的属性值。
o An OPTIONAL <org:chg> element that contains attribute values to be changed.
o 可选的<org:chg>元素，包含要更改的属性值。
At least one <org:add>, <org:rem>, or <org:chg> element MUST be provided if the command is not being extended. All of these elements MAY be omitted if an <update> extension is present. The OPTIONAL <org:add> and <org:rem> elements contain the following child elements:
如果命令未扩展，则必须至少提供一个<org:add>、<org:rem>或<org:chg>元素。如果存在<update>扩展，则可以省略所有这些元素。可选的<org:add>和<org:rem>元素包含以下子元素：
o Zero or more <org:contact> elements that contain the identifiers for contact objects to be associated with or removed from the organization object. Contact object identifiers MUST be known to the server before the contact object can be associated with the organization object.
o 零个或多个<org:contact>元素，其中包含要与组织对象关联或从组织对象中删除的联系人对象的标识符。在联系人对象与组织对象关联之前，服务器必须知道联系人对象标识符。
o Zero or more <org:role> elements that contain the role type, role statuses, and optional role ID of the organization.
o 零个或多个<org:role>元素，其中包含组织的角色类型、角色状态和可选角色ID。
* An <org:type> element that contains the role type of the organization, as defined in Section 3.2. The role type uniquely identifies the role to update.
* 包含组织角色类型的<org:type>元素，如第3.2节所定义。角色类型唯一标识要更新的角色。
* Zero or more <org:status> elements that contain the role statuses. The values of the role status are defined in Section 3.5.
* 零个或多个包含角色状态的<org:status>元素。角色状态的值在第3.5节中定义。
* An OPTIONAL <org:roleID> element that contains a third-party-assigned identifier, such as IANA ID for registrars, as defined in Section 3.2.3.
* 一个可选的<org:roleID>元素，包含第三方分配的标识符，如第3.2.3节中定义的注册者的IANA ID。
o Zero or more <org:status> elements that contain the operational status of the organization.
o 零个或多个<org:status>元素包含组织的运行状态。
An OPTIONAL <org:chg> element contains the following child elements, where at least one child element MUST be present:
可选的<org:chg>元素包含以下子元素，其中至少必须存在一个子元素：
o An OPTIONAL <org:parentId> element that contains the identifier of the parent object.
o 包含父对象标识符的可选<org:parentId>元素。
o Zero to two <org:postalInfo> elements that contain postal-address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, element content MUST be represented in a subset of Unicode [UNICODE] in the range U+0020 - U+007E. If a localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The change of the postal info is defined as a
o 零到两个包含邮政地址信息的<org:postalInfo>元素。提供了两个元素，以便以国际化和本地化形式提供地址信息；“type”属性用于标识这两种形式。如果提供了国际化表单（type=“int”），则元素内容必须在U+0020-U+007E范围内的Unicode[Unicode]子集中表示。如果提供了本地化形式（type=“loc”），元素内容可以用不受限制的UTF-8表示。邮政信息的更改被定义为
replacement of that postal info element with the contents of the sub-elements included in the <update> command. An empty <org:postalInfo> element is supported to allow a type of postal info to be removed. The <org:postalInfo> element contains the following child elements:
用<update>命令中包含的子元素的内容替换邮政信息元素。支持空的<org:postalInfo>元素以允许删除一种类型的邮政信息。<org:postalInfo>元素包含以下子元素：
* An <org:name> element that contains the name of the organization.
* 包含组织名称的<org:name>元素。
* An OPTIONAL <org:addr> element that contains address information associated with the organization. An <org:addr> element contains the following child elements:
* 可选的<org:addr>元素，包含与组织关联的地址信息。<org:addr>元素包含以下子元素：
+ One, two, or three <org:street> elements that contain the organization's street address.
+ 包含组织街道地址的一个、两个或三个<org:street>元素。
+ An <org:city> element that contains the organization's city.
+ 包含组织所在城市的<org:city>元素。
+ An OPTIONAL <org:sp> element that contains the organization's state or province.
+ 可选的<org:sp>元素，包含组织的州或省。
+ An OPTIONAL <org:pc> element that contains the organization's postal code.
+ 包含组织邮政编码的可选<org:pc>元素。
+ An <org:cc> element that contains the alpha-2 organization's country code. The detailed format of this element is described in Section 2.4.3 of [RFC5733].
+ 包含alpha-2组织的国家代码的<org:cc>元素。[RFC5733]第2.4.3节描述了该元素的详细格式。
o An OPTIONAL <org:voice> element that contains the organization's voice telephone number. The detailed format of this element is described in Section 2.5 of [RFC5733].
o 可选的<org:voice>元素，包含组织的语音电话号码。[RFC5733]第2.5节描述了该元素的详细格式。
o An OPTIONAL <org:fax> element that contains the organization's facsimile telephone number. The detailed format of this element is described in Section 2.5 of [RFC5733].
o 包含组织传真电话号码的可选<org:fax>元素。[RFC5733]第2.5节描述了该元素的详细格式。
o An OPTIONAL <org:email> element that contains the organization's email address. The detailed format of this element is described in [RFC5322].
o 包含组织电子邮件地址的可选<org:email>元素。[RFC5322]中描述了该元素的详细格式。
o An OPTIONAL <org:url> element that contains the URL to the website of the organization. The detailed format of this element is described in [RFC3986].
o 可选的<org:url>元素，包含指向组织网站的url。[RFC3986]中描述了该元素的详细格式。
Example <update> command:
示例<update>命令：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <update>
C: <org:update
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: <org:add>
C: <org:contact type="tech">sh8013</org:contact>
C: <org:role>
C: <org:type>privacyproxy</org:type>
C: <org:status>clientLinkProhibited</org:status>
C: </org:role>
C: <org:status>clientLinkProhibited</org:status>
C: </org:add>
C: <org:rem>
C: <org:contact type="billing">sh8014</org:contact>
C: <org:role>
C: <org:type>reseller</org:type>
C: </org:role>
C: </org:rem>
C: <org:chg>
C: <org:postalInfo type="int">
C: <org:addr>
C: <org:street>124 Example Dr.</org:street>
C: <org:street>Suite 200</org:street>
C: <org:city>Dulles</org:city>
C: <org:sp>VA</org:sp>
C: <org:pc>20166-6503</org:pc>
C: <org:cc>US</org:cc>
C: </org:addr>
C: </org:postalInfo>
C: <org:voice>+1.7034444444</org:voice>
C: <org:fax/>
C: </org:chg>
C: </org:update>
C: </update>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <update>
C: <org:update
C: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
C: <org:id>res1523</org:id>
C: <org:add>
C: <org:contact type="tech">sh8013</org:contact>
C: <org:role>
C: <org:type>privacyproxy</org:type>
C: <org:status>clientLinkProhibited</org:status>
C: </org:role>
C: <org:status>clientLinkProhibited</org:status>
C: </org:add>
C: <org:rem>
C: <org:contact type="billing">sh8014</org:contact>
C: <org:role>
C: <org:type>reseller</org:type>
C: </org:role>
C: </org:rem>
C: <org:chg>
C: <org:postalInfo type="int">
C: <org:addr>
C: <org:street>124 Example Dr.</org:street>
C: <org:street>Suite 200</org:street>
C: <org:city>Dulles</org:city>
C: <org:sp>VA</org:sp>
C: <org:pc>20166-6503</org:pc>
C: <org:cc>US</org:cc>
C: </org:addr>
C: </org:postalInfo>
C: <org:voice>+1.7034444444</org:voice>
C: <org:fax/>
C: </org:chg>
C: </org:update>
C: </update>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When an <update> command has been processed successfully, a server MUST respond with an EPP response with no <resData> element.
成功处理<update>命令后，服务器必须使用不带<resData>元素的EPP响应进行响应。
Example <update> response:
示例<update>响应：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg lang="en">Command completed successfully</msg>
S: </result>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
An EPP error response MUST be returned if an <update> command cannot be processed for any reason.
如果由于任何原因无法处理<update>命令，则必须返回EPP错误响应。
Commands are processed by a server in the order they are received from a client. Though an immediate response confirming receipt and processing of the command is produced by the server, a server operator MAY perform an offline review of requested transform commands before completing the requested action. In such situations, the response from the server MUST clearly note that the transform command has been received and processed, but the requested action is pending. The status in the response of the corresponding object MUST clearly reflect processing of the pending action. The server MUST notify the client when offline processing of the action has been completed.
服务器按照从客户端接收命令的顺序处理命令。虽然服务器会生成确认接收和处理命令的即时响应，但服务器操作员可以在完成请求的操作之前对请求的转换命令执行脱机检查。在这种情况下，来自服务器的响应必须清楚地注意到已接收并处理转换命令，但请求的操作处于挂起状态。相应对象响应中的状态必须清楚地反映挂起操作的处理。当操作的脱机处理完成时，服务器必须通知客户端。
Examples describing a <create> command that requires offline review are included here. Note the result code and message returned in response to the <create> command.
此处包括描述需要脱机检查的<create>命令的示例。注意响应<create>命令返回的结果代码和消息。
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1001">
S: <msg lang="en">Command completed successfully;
S: action pending</msg>
S: </result>
S: <resData>
S: <org:creData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>res1523</org:id>
S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1001">
S: <msg lang="en">Command completed successfully;
S: action pending</msg>
S: </result>
S: <resData>
S: <org:creData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id>res1523</org:id>
S: <org:crDate>2018-04-03T22:00:00.0Z</org:crDate>
S: </org:creData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S: </org:creData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
The status of the organization object after returning this response MUST include "pendingCreate". The server operator reviews the request offline and informs the client of the outcome of the review by queuing a service message for retrieval via the <poll> command; it MAY additionally use an out-of-band mechanism to inform the client of the outcome.
返回此响应后组织对象的状态必须包括“pendingCreate”。服务器操作员离线审查请求，并通过通过<poll>命令将服务消息排队以供检索，从而将审查结果通知客户端；它还可以使用带外机制将结果通知客户。
The service message MUST contain text that describes the notification in the child <msg> element of the response <msgQ> element. In addition, the EPP <resData> element MUST contain a child <org:panData> element. This element or its ancestor element MUST identify the organization namespace "urn:ietf:params:xml:ns:epp:org-1.0". The <org:panData> element contains the following child elements:
服务消息必须包含描述响应<msgQ>元素的子<msg>元素中通知的文本。此外，EPP<resData>元素必须包含一个子<org:panData>元素。此元素或其祖先元素必须标识组织名称空间“urn:ietf:params:xml:ns:epp:org-1.0”。<org:panData>元素包含以下子元素：
o An <org:id> element that contains the server-unique identifier of the organization object. The <org:id> element contains a REQUIRED "paResult" attribute. A positive boolean value indicates that the request has been approved and completed. A negative boolean value indicates that the request has been denied and the requested action has not been taken.
o 包含组织对象的服务器唯一标识符的<org:id>元素。<org:id>元素包含一个必需的“paResult”属性。正布尔值表示请求已被批准并完成。负布尔值表示请求已被拒绝，且未采取请求的操作。
o An <org:paTRID> element that contains the client transaction identifier and server transaction identifier returned with the original response to process the command. The client transaction identifier is OPTIONAL and will only be returned if the client provided an identifier with the original <create> command.
o 一个<org:patid>元素，包含处理命令的原始响应返回的客户端事务标识符和服务器事务标识符。客户端事务标识符是可选的，仅当客户端使用原始的<create>命令提供了标识符时才会返回。
o An <org:paDate> element that contains the date and time describing when review of the requested action was completed.
o 一个<org:paDate>元素，包含日期和时间，描述请求操作的审核何时完成。
Example "review completed" service message:
“审阅完成”服务消息示例：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1301">
S: <msg lang="en">Command completed successfully;
S: ack to dequeue</msg>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1301">
S: <msg lang="en">Command completed successfully;
S: ack to dequeue</msg>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>2018-04-04T22:01:00.0Z</qDate>
S: <msg>Pending action completed successfully.</msg>
S: </msgQ>
S: <resData>
S: <org:panData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id paResult="1">res1523</org:id>
S: <org:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </org:paTRID>
S: <org:paDate>2018-04-04T22:00:00.0Z</org:paDate>
S: </org:panData>
S: </resData>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID>
S: </trID>
S: </response>
S:</epp>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>2018-04-04T22:01:00.0Z</qDate>
S: <msg>Pending action completed successfully.</msg>
S: </msgQ>
S: <resData>
S: <org:panData
S: xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
S: <org:id paResult="1">res1523</org:id>
S: <org:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </org:paTRID>
S: <org:paDate>2018-04-04T22:00:00.0Z</org:paDate>
S: </org:panData>
S: </resData>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID>
S: </trID>
S: </response>
S:</epp>
An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes.
EPP对象映射是用XML模式表示法指定的。这里给出的形式语法是对象映射的完整模式表示，适合于自动验证EPP XML实例。开始和结束标记不是模式的一部分；它们用于记录模式的开始和结束，以便进行URI注册。
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:epp:org-1.0"
xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<schema targetNamespace="urn:ietf:params:xml:ns:epp:org-1.0"
xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!--
Import common element types.
-->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"/>
<!--
Import common element types.
-->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:epp-1.0"/>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
organization provisioning schema.
</documentation>
</annotation>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
organization provisioning schema.
</documentation>
</annotation>
<!--
Child elements found in EPP commands.
-->
<element name="create" type="org:createType"/>
<element name="delete" type="org:sIDType"/>
<element name="update" type="org:updateType"/>
<element name="check" type="org:mIDType"/>
<element name="info" type="org:infoType"/>
<element name="panData" type="org:panDataType"/>
<!--
Child elements found in EPP commands.
-->
<element name="create" type="org:createType"/>
<element name="delete" type="org:sIDType"/>
<element name="update" type="org:updateType"/>
<element name="check" type="org:mIDType"/>
<element name="info" type="org:infoType"/>
<element name="panData" type="org:panDataType"/>
<!--
Utility types.
-->
<simpleType name="statusType">
<restriction base="token">
<enumeration value="ok"/>
<enumeration value="hold"/>
<enumeration value="terminated"/>
<enumeration value="clientDeleteProhibited"/>
<enumeration value="clientUpdateProhibited"/>
<enumeration value="clientLinkProhibited"/>
<enumeration value="linked"/>
<enumeration value="pendingCreate"/>
<enumeration value="pendingUpdate"/>
<enumeration value="pendingDelete"/>
<enumeration value="serverDeleteProhibited"/>
<enumeration value="serverUpdateProhibited"/>
<enumeration value="serverLinkProhibited"/>
</restriction>
</simpleType>
<!--
Utility types.
-->
<simpleType name="statusType">
<restriction base="token">
<enumeration value="ok"/>
<enumeration value="hold"/>
<enumeration value="terminated"/>
<enumeration value="clientDeleteProhibited"/>
<enumeration value="clientUpdateProhibited"/>
<enumeration value="clientLinkProhibited"/>
<enumeration value="linked"/>
<enumeration value="pendingCreate"/>
<enumeration value="pendingUpdate"/>
<enumeration value="pendingDelete"/>
<enumeration value="serverDeleteProhibited"/>
<enumeration value="serverUpdateProhibited"/>
<enumeration value="serverLinkProhibited"/>
</restriction>
</simpleType>
<simpleType name="roleStatusType">
<restriction base="token">
<enumeration value="ok"/>
<enumeration value="clientLinkProhibited"/>
<enumeration value="linked"/>
<enumeration value="serverLinkProhibited"/>
</restriction>
</simpleType>
<simpleType name="roleStatusType">
<restriction base="token">
<enumeration value="ok"/>
<enumeration value="clientLinkProhibited"/>
<enumeration value="linked"/>
<enumeration value="serverLinkProhibited"/>
</restriction>
</simpleType>
<complexType name="roleType">
<complexType name="roleType">
<sequence>
<element name="type" type="token"/>
<element name="status" type="org:roleStatusType"
minOccurs="0" maxOccurs="3"/>
<element name="roleID" type="token" minOccurs="0"/>
</sequence>
</complexType>
<sequence>
<element name="type" type="token"/>
<element name="status" type="org:roleStatusType"
minOccurs="0" maxOccurs="3"/>
<element name="roleID" type="token" minOccurs="0"/>
</sequence>
</complexType>
<complexType name="postalInfoType">
<sequence>
<element name="name"
type="org:postalLineType"/>
<element name="addr"
type="org:addrType" minOccurs="0"/>
</sequence>
<attribute name="type"
type="org:postalInfoEnumType"
use="required"/>
</complexType>
<complexType name="postalInfoType">
<sequence>
<element name="name"
type="org:postalLineType"/>
<element name="addr"
type="org:addrType" minOccurs="0"/>
</sequence>
<attribute name="type"
type="org:postalInfoEnumType"
use="required"/>
</complexType>
<complexType name="contactType">
<simpleContent>
<extension base="eppcom:clIDType">
<attribute name="type" type="org:contactAttrType"
use="required"/>
<attribute name="typeName" type="token"/>
</extension>
</simpleContent>
</complexType>
<complexType name="contactType">
<simpleContent>
<extension base="eppcom:clIDType">
<attribute name="type" type="org:contactAttrType"
use="required"/>
<attribute name="typeName" type="token"/>
</extension>
</simpleContent>
</complexType>
<simpleType name="contactAttrType">
<restriction base="token">
<enumeration value="admin"/>
<enumeration value="billing"/>
<enumeration value="tech"/>
<enumeration value="abuse"/>
<enumeration value="custom"/>
</restriction>
</simpleType>
<simpleType name="contactAttrType">
<restriction base="token">
<enumeration value="admin"/>
<enumeration value="billing"/>
<enumeration value="tech"/>
<enumeration value="abuse"/>
<enumeration value="custom"/>
</restriction>
</simpleType>
<complexType name="e164Type">
<simpleContent>
<extension base="org:e164StringType">
<attribute name="x" type="token"/>
</extension>
</simpleContent>
</complexType>
<complexType name="e164Type">
<simpleContent>
<extension base="org:e164StringType">
<attribute name="x" type="token"/>
</extension>
</simpleContent>
</complexType>
<simpleType name="e164StringType">
<restriction base="token">
<pattern value="(\+[0-9]{1,3}\.[0-9]{1,14})?"/>
<maxLength value="17"/>
</restriction>
</simpleType>
<simpleType name="e164StringType">
<restriction base="token">
<pattern value="(\+[0-9]{1,3}\.[0-9]{1,14})?"/>
<maxLength value="17"/>
</restriction>
</simpleType>
<simpleType name="postalLineType">
<restriction base="normalizedString">
<minLength value="1"/>
<maxLength value="255"/>
</restriction>
</simpleType>
<simpleType name="postalLineType">
<restriction base="normalizedString">
<minLength value="1"/>
<maxLength value="255"/>
</restriction>
</simpleType>
<simpleType name="optPostalLineType">
<restriction base="normalizedString">
<maxLength value="255"/>
</restriction>
</simpleType>
<simpleType name="optPostalLineType">
<restriction base="normalizedString">
<maxLength value="255"/>
</restriction>
</simpleType>
<simpleType name="pcType">
<restriction base="token">
<maxLength value="16"/>
</restriction>
</simpleType>
<simpleType name="pcType">
<restriction base="token">
<maxLength value="16"/>
</restriction>
</simpleType>
<simpleType name="ccType">
<restriction base="token">
<length value="2"/>
</restriction>
</simpleType>
<simpleType name="ccType">
<restriction base="token">
<length value="2"/>
</restriction>
</simpleType>
<complexType name="addrType">
<sequence>
<element name="street" type="org:optPostalLineType"
minOccurs="0" maxOccurs="3"/>
<element name="city" type="org:postalLineType"/>
<element name="sp" type="org:optPostalLineType"
minOccurs="0"/>
<element name="pc" type="org:pcType"
minOccurs="0"/>
<element name="cc" type="org:ccType"/>
</sequence>
</complexType>
<complexType name="addrType">
<sequence>
<element name="street" type="org:optPostalLineType"
minOccurs="0" maxOccurs="3"/>
<element name="city" type="org:postalLineType"/>
<element name="sp" type="org:optPostalLineType"
minOccurs="0"/>
<element name="pc" type="org:pcType"
minOccurs="0"/>
<element name="cc" type="org:ccType"/>
</sequence>
</complexType>
<simpleType name="postalInfoEnumType">
<restriction base="token">
<enumeration value="loc"/>
<simpleType name="postalInfoEnumType">
<restriction base="token">
<enumeration value="loc"/>
<enumeration value="int"/>
</restriction>
</simpleType>
<enumeration value="int"/>
</restriction>
</simpleType>
<!--
Child element of commands that require only an identifier.
-->
<complexType name="sIDType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
</sequence>
</complexType>
<!--
Child element of commands that require only an identifier.
-->
<complexType name="sIDType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
</sequence>
</complexType>
<!--
Child element of commands that accept multiple identifiers.
-->
<complexType name="mIDType">
<sequence>
<element name="id"
type="eppcom:clIDType" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Child element of commands that accept multiple identifiers.
-->
<complexType name="mIDType">
<sequence>
<element name="id"
type="eppcom:clIDType" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Pending action notification response elements.
-->
<complexType name="panDataType">
<sequence>
<element name="id" type="org:paCLIDType"/>
<element name="paTRID" type="epp:trIDType"/>
<element name="paDate" type="dateTime"/>
</sequence>
</complexType>
<!--
Pending action notification response elements.
-->
<complexType name="panDataType">
<sequence>
<element name="id" type="org:paCLIDType"/>
<element name="paTRID" type="epp:trIDType"/>
<element name="paDate" type="dateTime"/>
</sequence>
</complexType>
<complexType name="paCLIDType">
<simpleContent>
<extension base="eppcom:clIDType">
<attribute name="paResult" type="boolean"
use="required"/>
</extension>
</simpleContent>
</complexType>
<complexType name="paCLIDType">
<simpleContent>
<extension base="eppcom:clIDType">
<attribute name="paResult" type="boolean"
use="required"/>
</extension>
</simpleContent>
</complexType>
<!--
Child elements of the <info> commands.
-->
<complexType name="infoType">
<sequence>
<!--
Child elements of the <info> commands.
-->
<complexType name="infoType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
</sequence>
</complexType>
<element name="id"
type="eppcom:clIDType"/>
</sequence>
</complexType>
<!--
Child elements of the <create> command.
-->
<complexType name="createType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="role"
type="org:roleType" maxOccurs="unbounded"/>
<element name="status"
type="org:statusType" minOccurs="0" maxOccurs="4"/>
<element name="parentId"
type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo"
type="org:postalInfoType" minOccurs="0" maxOccurs="2"/>
<element name="voice"
type="org:e164Type" minOccurs="0"/>
<element name="fax"
type="org:e164Type" minOccurs="0"/>
<element name="email"
type="eppcom:minTokenType" minOccurs="0"/>
<element name="url"
type="anyURI" minOccurs="0"/>
<element name="contact"
type="org:contactType"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Child elements of the <create> command.
-->
<complexType name="createType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="role"
type="org:roleType" maxOccurs="unbounded"/>
<element name="status"
type="org:statusType" minOccurs="0" maxOccurs="4"/>
<element name="parentId"
type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo"
type="org:postalInfoType" minOccurs="0" maxOccurs="2"/>
<element name="voice"
type="org:e164Type" minOccurs="0"/>
<element name="fax"
type="org:e164Type" minOccurs="0"/>
<element name="email"
type="eppcom:minTokenType" minOccurs="0"/>
<element name="url"
type="anyURI" minOccurs="0"/>
<element name="contact"
type="org:contactType"
minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="add"
type="org:addRemType" minOccurs="0"/>
<element name="rem"
type="org:addRemType" minOccurs="0"/>
<element name="chg"
type="org:chgType" minOccurs="0"/>
</sequence>
<!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="add"
type="org:addRemType" minOccurs="0"/>
<element name="rem"
type="org:addRemType" minOccurs="0"/>
<element name="chg"
type="org:chgType" minOccurs="0"/>
</sequence>
</complexType>
</complexType>
<!--
Data elements that can be added or removed.
-->
<complexType name="addRemType">
<sequence>
<element name="contact"
type="org:contactType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="role" type="org:roleType"
minOccurs="0" maxOccurs="unbounded"/>
<element name="status" type="org:statusType"
minOccurs="0" maxOccurs="9"/>
</sequence>
</complexType>
<!--
Data elements that can be added or removed.
-->
<complexType name="addRemType">
<sequence>
<element name="contact"
type="org:contactType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="role" type="org:roleType"
minOccurs="0" maxOccurs="unbounded"/>
<element name="status" type="org:statusType"
minOccurs="0" maxOccurs="9"/>
</sequence>
</complexType>
<!--
Data elements that can be changed.
-->
<complexType name="chgType">
<sequence>
<element name="parentId"
type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo"
type="org:chgPostalInfoType"
minOccurs="0" maxOccurs="2"/>
<element name="voice"
type="org:e164Type" minOccurs="0"/>
<element name="fax"
type="org:e164Type" minOccurs="0"/>
<element name="email"
type="eppcom:minTokenType" minOccurs="0"/>
<element name="url"
type="anyURI" minOccurs="0"/>
</sequence>
</complexType>
<!--
Data elements that can be changed.
-->
<complexType name="chgType">
<sequence>
<element name="parentId"
type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo"
type="org:chgPostalInfoType"
minOccurs="0" maxOccurs="2"/>
<element name="voice"
type="org:e164Type" minOccurs="0"/>
<element name="fax"
type="org:e164Type" minOccurs="0"/>
<element name="email"
type="eppcom:minTokenType" minOccurs="0"/>
<element name="url"
type="anyURI" minOccurs="0"/>
</sequence>
</complexType>
<complexType name="chgPostalInfoType">
<sequence>
<element name="name"
type="org:postalLineType" minOccurs="0"/>
<element name="addr"
type="org:addrType" minOccurs="0"/>
</sequence>
<attribute name="type"
type="org:postalInfoEnumType" use="required"/>
</complexType>
<complexType name="chgPostalInfoType">
<sequence>
<element name="name"
type="org:postalLineType" minOccurs="0"/>
<element name="addr"
type="org:addrType" minOccurs="0"/>
</sequence>
<attribute name="type"
type="org:postalInfoEnumType" use="required"/>
</complexType>
<!--
Child response elements.
-->
<element name="chkData" type="org:chkDataType"/>
<element name="creData" type="org:creDataType"/>
<element name="infData" type="org:infDataType"/>
<!--
Child response elements.
-->
<element name="chkData" type="org:chkDataType"/>
<element name="creData" type="org:creDataType"/>
<element name="infData" type="org:infDataType"/>
<!--
<check> response elements.
-->
<complexType name="chkDataType">
<sequence>
<element name="cd" type="org:checkType"
maxOccurs="unbounded" />
</sequence>
</complexType>
<!--
<check> response elements.
-->
<complexType name="chkDataType">
<sequence>
<element name="cd" type="org:checkType"
maxOccurs="unbounded" />
</sequence>
</complexType>
<complexType name="checkType">
<sequence>
<element name="id" type="org:checkIDType"/>
<element name="reason" type="eppcom:reasonType"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="checkType">
<sequence>
<element name="id" type="org:checkIDType"/>
<element name="reason" type="eppcom:reasonType"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="checkIDType">
<simpleContent>
<extension base="eppcom:clIDType">
<attribute name="avail" type="boolean"
use="required"/>
</extension>
</simpleContent>
</complexType>
<complexType name="checkIDType">
<simpleContent>
<extension base="eppcom:clIDType">
<attribute name="avail" type="boolean"
use="required"/>
</extension>
</simpleContent>
</complexType>
<!--
<info> response elements.
-->
<!--
<info> response elements.
-->
<complexType name="infDataType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="roid"
type="eppcom:roidType"/>
<element name="role"
type="org:roleType" maxOccurs="unbounded"/>
<element name="status"
type="org:statusType" maxOccurs="9"/>
<complexType name="infDataType">
<sequence>
<element name="id"
type="eppcom:clIDType"/>
<element name="roid"
type="eppcom:roidType"/>
<element name="role"
type="org:roleType" maxOccurs="unbounded"/>
<element name="status"
type="org:statusType" maxOccurs="9"/>
<element name="parentId"
type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo"
type="org:postalInfoType" minOccurs="0" maxOccurs="2"/>
<element name="voice"
type="org:e164Type" minOccurs="0"/>
<element name="fax"
type="org:e164Type" minOccurs="0"/>
<element name="email"
type="eppcom:minTokenType" minOccurs="0"/>
<element name="url"
type="anyURI" minOccurs="0"/>
<element name="contact"
type="org:contactType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="clID"
type="eppcom:clIDType" minOccurs="0"/>
<element name="crID"
type="eppcom:clIDType"/>
<element name="crDate"
type="dateTime"/>
<element name="upID"
type="eppcom:clIDType" minOccurs="0"/>
<element name="upDate"
type="dateTime" minOccurs="0"/>
</sequence>
</complexType>
<!--
<create> response elements.
-->
<complexType name="creDataType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="crDate" type="dateTime"/>
</sequence>
</complexType>
<element name="parentId"
type="eppcom:clIDType" minOccurs="0"/>
<element name="postalInfo"
type="org:postalInfoType" minOccurs="0" maxOccurs="2"/>
<element name="voice"
type="org:e164Type" minOccurs="0"/>
<element name="fax"
type="org:e164Type" minOccurs="0"/>
<element name="email"
type="eppcom:minTokenType" minOccurs="0"/>
<element name="url"
type="anyURI" minOccurs="0"/>
<element name="contact"
type="org:contactType" minOccurs="0"
maxOccurs="unbounded"/>
<element name="clID"
type="eppcom:clIDType" minOccurs="0"/>
<element name="crID"
type="eppcom:clIDType"/>
<element name="crDate"
type="dateTime"/>
<element name="upID"
type="eppcom:clIDType" minOccurs="0"/>
<element name="upDate"
type="dateTime" minOccurs="0"/>
</sequence>
</complexType>
<!--
<create> response elements.
-->
<complexType name="creDataType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="crDate" type="dateTime"/>
</sequence>
</complexType>
<!--
<!--
End of schema. --> </schema> END
架构结束。--></架构>结束
EPP is represented in XML, which provides native support for encoding information using the Unicode character set [UNICODE] and its more compact representations, including UTF-8. Conformant XML processors recognize both UTF-8 [RFC3629] and UTF-16 [RFC2781]. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED.
EPP用XML表示，它为使用Unicode字符集[Unicode]及其更紧凑的表示（包括UTF-8）编码信息提供了本机支持。一致性XML处理器同时识别UTF-8[RFC3629]和UTF-16[RFC2781]。尽管XML包含通过在<？XML？>声明中使用“encoding”属性来识别和使用其他字符编码的规定，但建议使用UTF-8。
As an extension of the EPP organization object mapping, the elements and element content described in this document MUST inherit the internationalization conventions used to represent higher-layer domain and core protocol structures present in an XML instance that includes this extension.
作为EPP组织对象映射的扩展，本文档中描述的元素和元素内容必须继承用于表示包含此扩展的XML实例中存在的更高层域和核心协议结构的国际化约定。
This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. IANA has assigned the following URI.
本文档使用URN来描述符合[RFC3688]中描述的注册表机制的XML名称空间和XML模式。IANA已分配以下URI。
The organization namespace:
组织名称空间：
URI: urn:ietf:params:xml:ns:epp:org-1.0
URI: urn:ietf:params:xml:ns:epp:org-1.0
Registrant Contact: IESG
注册联系人：IESG
XML: None. Namespace URIs do not represent an XML specification.
XML：没有。命名空间URI不表示XML规范。
The organization XML schema:
组织XML架构：
URI: urn:ietf:params:xml:schema:epp:org-1.0
URI: urn:ietf:params:xml:schema:epp:org-1.0
Registrant Contact: IESG
注册联系人：IESG
XML: See the "Formal Syntax" section of RFC 8543 (this document).
XML：请参阅RFC8543（本文档）的“形式语法”部分。
The EPP extension described in this document has been registered by IANA in the "Extensions for the Extensible Provisioning Protocol (EPP)" registry described in [RFC7451]. The details of the registration are as follows:
本文档中描述的EPP扩展已由IANA在[RFC7451]中描述的“可扩展资源调配协议（EPP）扩展”注册表中注册。注册详情如下：
Name of Extension: Extensible Provisioning Protocol (EPP) Organization Mapping
扩展名：可扩展资源调配协议（EPP）组织映射
Document status: Standards Track
文档状态：标准跟踪
Reference: RFC 8543
参考：RFC 8543
Registrant Name and Email Address: IESG, iesg@ietf.org
注册人姓名和电子邮件地址：IESG，iesg@ietf.org
TLDs: Any
TLDs：有吗
IPR Disclosure: None
知识产权披露：无
Status: Active
状态：活动
Notes: None
注：无
IANA has created a new category of protocol registry for values of the organization roles. The name of this registry is "EPP Organization Role Values". The registration policy for this registry is "Expert Review" [RFC8126].
IANA为组织角色的值创建了一个新的协议注册类别。此注册表的名称为“EPP组织角色值”。该注册中心的注册政策为“专家评审”[RFC8126]。
Value: The string value being registered.
值：正在注册的字符串值。
Description: Brief description of the organization role values.
描述：组织角色值的简要描述。
Registrant Name: For RFC specifications, state "IESG". For other specifications, give the name of the responsible party.
注册人姓名：对于RFC规范，请注明“IESG”。对于其他规格，请提供责任方的名称。
Registrant Contact Information: An email address, postal address, or some other information to be used to contact the registrant.
注册人联系信息：用于联系注册人的电子邮件地址、邮政地址或其他信息。
The following are the initial registry contents:
以下是初始注册表内容：
Value: registrar
价值：注册主任
Description: The entity object instance represents the authority responsible for the registration in the registry.
描述：实体对象实例表示负责在注册表中注册的机构。
Registrant: IESG, iesg@ietf.org
注册人：IESG，iesg@ietf.org
Value: reseller
价值：经销商
Description: The entity object instance represents a third party through which the registration was conducted (i.e., not the registry or registrar).
描述：实体对象实例表示进行注册的第三方（即，不是注册中心或注册中心）。
Registrant: IESG, iesg@ietf.org
注册人：IESG，iesg@ietf.org
Value: privacyproxy
值：privacyproxy
Description: The entity object instance represents a third party who could help to register a domain without exposing the registrants' private information.
描述：实体对象实例代表第三方，该第三方可以帮助注册域，而不公开注册者的私人信息。
Registrant: IESG, iesg@ietf.org
注册人：IESG，iesg@ietf.org
Value: dns-operator
值：dns操作员
Description: The entity object instance represents a third-party DNS operator that maintains the name servers and zone data on behalf of a registrant.
描述：实体对象实例表示代表注册人维护名称服务器和区域数据的第三方DNS运营商。
Registrant: IESG, iesg@ietf.org
注册人：IESG，iesg@ietf.org
The organization object may have personally identifiable information, such as <org:contact>. This information is not a required element in this document that can be provided on a voluntary basis. If it is provided, both client and server MUST ensure that authorization information is stored and exchanged with high-grade encryption mechanisms to provide privacy services, which are specified in [RFC5733]. The security considerations described in [RFC5730] or those caused by the protocol layers used by EPP will apply to this specification as well.
组织对象可能具有个人可识别信息，例如<org:contact>。该信息不是本文件中可自愿提供的必要内容。如果提供，客户端和服务器必须确保使用高级加密机制存储和交换授权信息，以提供[RFC5733]中规定的隐私服务。[RFC5730]中描述的安全注意事项或EPP使用的协议层引起的安全注意事项也适用于本规范。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<https://www.rfc-editor.org/info/rfc2119>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 2003, <https://www.rfc-editor.org/info/rfc3629>.
[RFC3629]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，DOI 10.17487/RFC3629，2003年11月<https://www.rfc-editor.org/info/rfc3629>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-editor.org/info/rfc3688>.
[RFC3688]Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，DOI 10.17487/RFC3688，2004年1月<https://www.rfc-editor.org/info/rfc3688>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, <https://www.rfc-editor.org/info/rfc3986>.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，DOI 10.17487/RFC3986，2005年1月<https://www.rfc-editor.org/info/rfc3986>.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, DOI 10.17487/RFC5322, October 2008, <https://www.rfc-editor.org/info/rfc5322>.
[RFC5322]Resnick，P.，Ed.，“互联网信息格式”，RFC 5322，DOI 10.17487/RFC5322，2008年10月<https://www.rfc-editor.org/info/rfc5322>.
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, September 2009, <https://www.rfc-editor.org/info/rfc5646>.
[RFC5646]Phillips，A.，Ed.和M.Davis，Ed.，“识别语言的标签”，BCP 47，RFC 5646，DOI 10.17487/RFC5646，2009年9月<https://www.rfc-editor.org/info/rfc5646>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, <https://www.rfc-editor.org/info/rfc5730>.
[RFC5730]Hollenbeck，S.，“可扩展资源调配协议（EPP）”，STD 69，RFC 5730，DOI 10.17487/RFC5730，2009年8月<https://www.rfc-editor.org/info/rfc5730>.
[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733, August 2009, <https://www.rfc-editor.org/info/rfc5733>.
[RFC5733]Hollenbeck，S.，“可扩展供应协议（EPP）联系人映射”，STD 69，RFC 5733，DOI 10.17487/RFC5733，2009年8月<https://www.rfc-editor.org/info/rfc5733>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, <https://www.rfc-editor.org/info/rfc8126>.
[RFC8126]Cotton，M.，Leiba，B.，和T.Narten，“在RFC中编写IANA考虑事项部分的指南”，BCP 26，RFC 8126，DOI 10.17487/RFC8126，2017年6月<https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8174]Leiba，B.，“RFC 2119关键词中大写与小写的歧义”，BCP 14，RFC 8174，DOI 10.17487/RFC8174，2017年5月<https://www.rfc-editor.org/info/rfc8174>.
[UNICODE] The Unicode Consortium, "The Unicode Standard", <http://www.unicode.org/versions/latest/>.
[UNICODE]UNICODE联盟，“UNICODE标准”<http://www.unicode.org/versions/latest/>.
[W3C.REC-xml-20081126] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", World Wide Web Consortium Recommendation REC-xml-20081126, November 2008, <https://www.w3.org/TR/xml/>.
[W3C.REC-xml-20081126]Bray，T.，Paoli，J.，Sperberg McQueen，C.，Maler，E.，和F.Yergeau，“可扩展标记语言（xml）1.0（第五版）”，万维网联盟建议REC-xml-20081126，2008年11月<https://www.w3.org/TR/xml/>.
[W3C.REC-xmlschema-1-20041028] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, "XML Schema Part 1: Structures Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-1-20041028, October 2004, <http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
[W3C.REC-xmlschema-1-20041028]Thompson，H.，Beech，D.，Maloney，M.，和N.Mendelsohn，“XML模式第1部分：结构第二版”，万维网联盟建议REC-xmlschema-1-20041028，2004年10月<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
[W3C.REC-xmlschema-2-20041028] Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-2-20041028, October 2004, <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
[W3C.REC-xmlschema-2-20041028]Biron，P.和A.Malhotra，“XML模式第2部分：数据类型第二版”，万维网联盟建议REC-xmlschema-2-20041028，2004年10月<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
[RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646", RFC 2781, DOI 10.17487/RFC2781, February 2000, <https://www.rfc-editor.org/info/rfc2781>.
[RFC2781]Hoffman，P.和F.Yergeau，“UTF-16，ISO 10646编码”，RFC 2781，DOI 10.17487/RFC2781，2000年2月<https://www.rfc-editor.org/info/rfc2781>.
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, <https://www.rfc-editor.org/info/rfc7451>.
[RFC7451]Hollenbeck，S.，“可扩展供应协议的扩展注册表”，RFC 7451，DOI 10.17487/RFC7451，2015年2月<https://www.rfc-editor.org/info/rfc7451>.
Acknowledgments
致谢
The authors would like to thank Rik Ribbers, Marc Groeneweg, Patrick Mevzek, Antoin Verschuren, and Scott Hollenbeck for their careful review and valuable comments.
作者要感谢Rik Ribbers、Marc Groeneweg、Patrick Mevzek、Antoin Verschuren和Scott Hollenbeck的仔细审查和宝贵评论。
Authors' Addresses
作者地址
Linlin Zhou CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China
中国北京市海淀区中关村南四街4号林林洲CNNIC 100190
Email: zhoulinlin@cnnic.cn
Email: zhoulinlin@cnnic.cn
Ning Kong Consultant
宁港顾问
Email: ietfing@gmail.com
Email: ietfing@gmail.com
Jiankang Yao CNNIC 4 South 4th Street, Zhongguancun, Haidian District Beijing, Beijing 100190 China
中国北京市海淀区中关村南四街4号建康姚CNNIC 100190
Email: yaojk@cnnic.cn
Email: yaojk@cnnic.cn
James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 United States of America
James Gould VeriSign，Inc.美国弗吉尼亚州布鲁蒙特路莱斯顿12061号，邮编：20190
Email: jgould@verisign.com
URI: http://www.verisign.com
Email: jgould@verisign.com
URI: http://www.verisign.com
Guiqing Zhou
周桂青
Email: qing.joe@gmail.com
Email: qing.joe@gmail.com