Network Working Group S. Hollenbeck
Request for Comments: 4933 VeriSign, Inc.
Obsoletes: 3733 May 2007
Category: Standards Track
Network Working Group S. Hollenbeck
Request for Comments: 4933 VeriSign, Inc.
Obsoletes: 3733 May 2007
Category: Standards Track
Extensible Provisioning Protocol (EPP) Contact Mapping
可扩展资源调配协议（EPP）联系人映射
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
Abstract
摘要
This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of individual or organizational social information identifiers (known as "contacts") stored in a shared central repository. Specified in Extensible Markup Language (XML), the mapping defines EPP command syntax and semantics as applied to contacts. This document obsoletes RFC 3733.
本文档描述了可扩展资源调配协议（EPP）映射，用于调配和管理存储在共享中央存储库中的个人或组织社会信息标识符（称为“联系人”）。在可扩展标记语言（XML）中指定，映射定义应用于联系人的EPP命令语法和语义。本文件淘汰了RFC 3733。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Contact and Client Identifiers . . . . . . . . . . . . . . 3
2.2. Status Values . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Individual and Organizational Names . . . . . . . . . . . 5
2.4. Address . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4.1. Street, City, and State or Province . . . . . . . . . 6
2.4.2. Postal Code . . . . . . . . . . . . . . . . . . . . . 6
2.4.3. Country . . . . . . . . . . . . . . . . . . . . . . . 6
2.5. Telephone Numbers . . . . . . . . . . . . . . . . . . . . 6
2.6. Email Addresses . . . . . . . . . . . . . . . . . . . . . 6
2.7. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6
2.8. Authorization Information . . . . . . . . . . . . . . . . 7
2.9. Disclosure of Data Elements and Attributes . . . . . . . . 7
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 8
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 9
3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . . 11
3.1.3. EPP <transfer> Query Command . . . . . . . . . . . . . 14
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 16
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . . 17
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . . 20
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . . 22
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . . 23
3.3. Offline Review of Requested Actions . . . . . . . . . . . 27
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 29
5. Internationalization Considerations . . . . . . . . . . . . . 38
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
7. Security Considerations . . . . . . . . . . . . . . . . . . . 39
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1. Normative References . . . . . . . . . . . . . . . . . . . 39
9.2. Informative References . . . . . . . . . . . . . . . . . . 40
Appendix A. Changes from RFC 3733 . . . . . . . . . . . . . . . . 41
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Contact and Client Identifiers . . . . . . . . . . . . . . 3
2.2. Status Values . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Individual and Organizational Names . . . . . . . . . . . 5
2.4. Address . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4.1. Street, City, and State or Province . . . . . . . . . 6
2.4.2. Postal Code . . . . . . . . . . . . . . . . . . . . . 6
2.4.3. Country . . . . . . . . . . . . . . . . . . . . . . . 6
2.5. Telephone Numbers . . . . . . . . . . . . . . . . . . . . 6
2.6. Email Addresses . . . . . . . . . . . . . . . . . . . . . 6
2.7. Dates and Times . . . . . . . . . . . . . . . . . . . . . 6
2.8. Authorization Information . . . . . . . . . . . . . . . . 7
2.9. Disclosure of Data Elements and Attributes . . . . . . . . 7
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 8
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 8
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . . 9
3.1.2. EPP <info> Command . . . . . . . . . . . . . . . . . . 11
3.1.3. EPP <transfer> Query Command . . . . . . . . . . . . . 14
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 16
3.2.1. EPP <create> Command . . . . . . . . . . . . . . . . . 17
3.2.2. EPP <delete> Command . . . . . . . . . . . . . . . . . 20
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . . 21
3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . . 22
3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . . 23
3.3. Offline Review of Requested Actions . . . . . . . . . . . 27
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 29
5. Internationalization Considerations . . . . . . . . . . . . . 38
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
7. Security Considerations . . . . . . . . . . . . . . . . . . . 39
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1. Normative References . . . . . . . . . . . . . . . . . . . 39
9.2. Informative References . . . . . . . . . . . . . . . . . . 40
Appendix A. Changes from RFC 3733 . . . . . . . . . . . . . . . . 41
This document describes a personal and organizational identifier mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This mapping is specified using the Extensible Markup Language (XML) 1.0 as described in [W3C.REC-xml-20040204] and XML Schema notation as described in [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. This document obsoletes RFC 3733 [RFC3733].
本文档描述了可扩展资源调配协议（EPP）1.0版的个人和组织标识符映射。此映射是使用[W3C.REC-XML-20040204]中所述的可扩展标记语言（XML）1.0和[W3C.REC-xmlschema-1-20041028]和[W3C.REC-xmlschema-2-20041028]中所述的XML模式表示法指定的。本文件废除了RFC 3733[RFC3733]。
[RFC4930] provides a complete description of EPP command and response structures. A thorough understanding of the base protocol specification is necessary to understand the mapping described in this document.
[RFC4930]提供了EPP命令和响应结构的完整描述。要理解本文档中描述的映射，必须彻底理解基本协议规范。
XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented to develop a conforming implementation.
XML区分大小写。除非另有说明，否则本文档中提供的XML规范和示例必须按照提供的字符大小写进行解释，以开发一致的实现。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
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 protocol.
在示例中，“C:”表示协议客户端发送的行，“S:”表示协议服务器返回的行。示例中的缩进和空白仅用于说明元素关系，不是本协议的必需功能。
An EPP contact 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 contacts are identified by a server-unique identifier. 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 [RFC4930].
所有EPP联系人都由服务器唯一标识符标识。联系人标识符是具有指定最小长度、指定最大长度和指定格式的字符串。联系人标识符使用[RFC4930]中描述的“clIDType”客户端标识符语法。
A contact object MUST always have at least one associated status value. Status values can be set only by the client that sponsors a contact object and by the server on which the object resides. A client can change the status of a contact 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 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 status values that can be added or removed by a server are prefixed with "server". Status values that do not begin with either "client" or "server" are server-managed.
客户端可以添加或删除的状态值以“客户端”作为前缀。可由服务器添加或删除的相应状态值以“服务器”作为前缀。不以“客户端”或“服务器”开头的状态值由服务器管理。
Status Value Descriptions:
状态值说明：
- clientDeleteProhibited, serverDeleteProhibited
- 客户端删除禁止，服务器删除禁止
Requests to delete the object MUST be rejected.
必须拒绝删除对象的请求。
- clientTransferProhibited, serverTransferProhibited
- 客户端传输禁止，服务器传输禁止
Requests to transfer the object MUST be rejected.
必须拒绝传输对象的请求。
- clientUpdateProhibited, serverUpdateProhibited
- clientUpdateProhibited，serverUpdateProhibited
Requests to update the object (other than to remove this status) MUST be rejected.
必须拒绝更新对象（而不是删除此状态）的请求。
- linked
- 联系
The contact object has at least one active association with another object, such as a domain object. Servers SHOULD provide services to determine existing object associations.
联系人对象与另一个对象（如域对象）至少有一个活动关联。服务器应提供确定现有对象关联的服务。
- ok
- 好啊
This is the normal status value for an object that has no pending operations or prohibitions. This value is set and removed by the server as other status values are added or removed.
这是没有挂起操作或禁止的对象的正常状态值。当添加或删除其他状态值时，服务器将设置和删除此值。
- pendingCreate, pendingDelete, pendingRenew, pendingTransfer, pendingUpdate
- pendingCreate、pendingDelete、pendingRenew、pendingTransfer、pendingUpdate
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.
已为对象处理转换命令，但服务器尚未完成该操作。服务器操作员可以出于各种原因延迟操作完成，例如允许人工审核或第三方操作。已处理但其请求的操作处于挂起状态的转换命令用响应代码1001表示。
When the requested action has been completed, the pendingCreate, pendingDelete, pendingTransfer, or pendingUpdate status value MUST be removed. All clients involved in the transaction MUST be notified using a service message that the action has been completed and that the status of the object has changed.
完成请求的操作后，必须删除pendingCreate、pendingDelete、pendingTransfer或pendingUpdate状态值。必须使用服务消息通知事务中涉及的所有客户端操作已完成，并且对象的状态已更改。
"ok" status MAY only be combined with "linked" status.
“确定”状态只能与“链接”状态组合。
"linked" status MAY be combined with any status.
“链接”状态可以与任何状态组合。
"pendingDelete" status MUST NOT be combined with either "clientDeleteProhibited" or "serverDeleteProhibited" status.
“pendingDelete”状态不能与“ClientDelete禁止”或“ServerDelete禁止”状态组合。
"pendingTransfer" status MUST NOT be combined with either "clientTransferProhibited" or "serverTransferProhibited" status. "pendingUpdate" status MUST NOT be combined with either "clientUpdateProhibited" or "serverUpdateProhibited" status.
“pendingTransfer”状态不得与“ClientTransferProbited”或“ServerTransferProbited”状态组合。“pendingUpdate”状态不能与“clientUpdateProhibited”或“serverUpdateProhibited”状态组合。
The pendingCreate, pendingDelete, pendingTransfer, and pendingUpdate status values MUST NOT be combined with each other.
pendingCreate、pendingDelete、pendingTransfer和pendingUpdate状态值不得相互组合。
Other status combinations not expressly prohibited MAY be used.
可以使用未明确禁止的其他状态组合。
Individual and organizational names associated with a contact are represented using character strings. These strings have a specified minimum length and a specified maximum length. Individual and organizational names MAY be provided in both UTF-8 [RFC3629] and a subset of UTF-8 that can be represented in 7-bit ASCII depending on local needs.
与联系人关联的个人和组织名称使用字符串表示。这些字符串具有指定的最小长度和指定的最大长度。UTF-8[RFC3629]和UTF-8的子集中都可以提供个人和组织名称，这些名称可以根据本地需要以7位ASCII表示。
Every contact has associated postal address information. A postal address contains OPTIONAL street information, city information, OPTIONAL state/province information, an OPTIONAL postal code, and a country identifier. Address information MAY be provided in both
每个联系人都有相关的邮政地址信息。邮政地址包含可选的街道信息、城市信息、可选的州/省信息、可选的邮政编码和国家标识符。地址信息可以以两种方式提供
UTF-8 and a subset of UTF-8 that can be represented in 7-bit ASCII depending on local needs.
UTF-8和UTF-8的子集，可根据本地需要以7位ASCII表示。
Contact street, city, and state or province information is represented using character strings. These strings have a specified minimum length and a specified maximum length.
联系人街道、城市和州或省信息使用字符串表示。这些字符串具有指定的最小长度和指定的最大长度。
Contact postal codes are represented using character strings. These strings have a specified minimum length and a specified maximum length.
联系人邮政编码使用字符串表示。这些字符串具有指定的最小长度和指定的最大长度。
Contact country identifiers are represented using two-character identifiers specified in [ISO.3166.1997].
联系国标识符使用[ISO.3166.1997]中规定的两个字符标识符表示。
Contact telephone number structure is derived from structures defined in [ITU.E164.2005]. Telephone numbers described in this mapping are character strings that MUST begin with a plus sign ("+", ASCII value 0x002B), followed by a country code defined in [ITU.E164.2005], followed by a dot (".", ASCII value 0x002E), followed by a sequence of digits representing the telephone number. An optional "x" attribute is provided to note telephone extension information.
联系人电话号码结构源自[ITU.E164.2005]中定义的结构。此映射中描述的电话号码是字符串，必须以加号（“+”，ASCII值0x002B）开头，后跟[ITU.E164.2005]中定义的国家代码，后跟点（“.”，ASCII值0x002E），后跟表示电话号码的数字序列。提供了可选的“x”属性来记录电话分机信息。
Email address syntax is defined in [RFC0822]. This mapping does not prescribe minimum or maximum lengths for character strings used to represent email addresses.
[RFC0822]中定义了电子邮件地址语法。此映射不规定用于表示电子邮件地址的字符串的最小或最大长度。
Date and time attribute values MUST be represented in Universal Coordinated Time (UTC) using the Gregorian calendar. The extended date-time form using upper case "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 lower case "T" and "Z" characters.
日期和时间属性值必须使用公历以世界协调时间（UTC）表示。必须使用[W3C.REC-xmlschema-2-20041028]中定义的大写“T”和“Z”字符的扩展日期时间表单来表示日期时间值，因为XML模式不支持截断日期时间表单或小写“T”和“Z”字符。
Authorization information is associated with contact objects to facilitate transfer operations. Authorization information is assigned when a contact object is created, and it might be updated in the future. This specification describes password-based authorization information, though other mechanisms are possible.
授权信息与联系人对象关联，以便于传输操作。授权信息是在创建联系人对象时分配的，将来可能会更新。本规范描述了基于密码的授权信息，但也可以使用其他机制。
The EPP core protocol requires a server operator to announce data collection policies to clients; see Section 2.4 of [RFC4930]. In conjunction with this disclosure requirement, this mapping includes data elements that allow a client to identify elements that require exceptional server operator handling to allow or restrict disclosure to third parties.
EPP核心协议要求服务器操作员向客户端宣布数据收集策略；参见[RFC4930]第2.4节。结合本披露要求，此映射包括允许客户端识别需要特殊服务器操作员处理的元素的数据元素，以允许或限制向第三方披露。
A server operator announces a default disclosure policy when establishing a session with a client. When an object is created or updated, the client can specify contact attributes that require exceptional disclosure handling using an OPTIONAL <contact:disclose> element. Once set, disclosure preferences can be reviewed using a contact information query. A server operator MUST reject any transaction that requests disclosure practices that do not conform to the announced data collection policy with a 2308 error response code.
服务器操作员在与客户端建立会话时宣布默认的公开策略。创建或更新对象时，客户端可以使用可选的<contact:expose>元素指定需要异常公开处理的联系人属性。设置后，可以使用联系人信息查询查看披露首选项。服务器运营商必须以2308错误响应代码拒绝任何要求披露不符合公布的数据收集策略的做法的交易。
If present, the <contact:disclose> element MUST contain a "flag" attribute. The "flag" attribute contains an XML Schema boolean value. A value of "true" or "1" (one) notes a client preference to allow disclosure of the specified elements as an exception to the stated data collection policy. A value of "false" or "0" (zero) notes a client preference to not allow disclosure of the specified elements as an exception to the stated data collection policy.
如果存在，<contact:expose>元素必须包含一个“flag”属性。“flag”属性包含一个XML模式布尔值。值为“真”或“1”（一）表示客户偏好，允许披露指定元素，作为所述数据收集策略的例外。值为“false”或“0”（零）表示客户端首选项不允许披露指定元素，作为所述数据收集策略的例外。
The <contact:disclose> element MUST contain at least one of the following child elements:
<contact:expose>元素必须至少包含以下子元素之一：
<contact:name type="int"/>
<contact:name type="loc"/>
<contact:org type="int"/>
<contact:org type="loc"/>
<contact:addr type="int"/>
<contact:addr type="loc"/>
<contact:voice/>
<contact:fax/>
<contact:email/>
<contact:name type="int"/>
<contact:name type="loc"/>
<contact:org type="int"/>
<contact:org type="loc"/>
<contact:addr type="int"/>
<contact:addr type="loc"/>
<contact:voice/>
<contact:fax/>
<contact:email/>
Example <contact:disclose> element, flag="0":
示例<contact:expose>元素，flag=“0”：
<contact:disclose flag="0">
<contact:email/>
<contact:voice/>
</contact:disclose>
<contact:disclose flag="0">
<contact:email/>
<contact:voice/>
</contact:disclose>
In this example, the contact email address and voice telephone number cannot be disclosed. All other elements are subject to disclosure in accordance with the server's data collection policy.
在此示例中，联系人电子邮件地址和语音电话号码不能公开。根据服务器的数据收集策略，所有其他元素都可能被披露。
Example <contact:disclose> element, flag="1":
示例<contact:expose>元素，flag=“1”：
<contact:disclose flag="1">
<contact:name type="int"/>
<contact:org type="int"/>
<contact:addr type="int"/>
</contact:disclose>
<contact:disclose flag="1">
<contact:name type="int"/>
<contact:org type="int"/>
<contact:addr type="int"/>
</contact:disclose>
In this example, the internationalized contact name, organization, and address information can be disclosed. All other elements are subject to disclosure in accordance with the server's data collection policy.
在此示例中，可以公开国际化联系人姓名、组织和地址信息。根据服务器的数据收集策略，所有其他元素都可能被披露。
Client identification features provided by the EPP <login> command and contact authorization information are used to determine if a client is authorized to perform contact information query commands. These features also determine if a client is authorized to receive data that is otherwise marked for non-disclosure in a query response.
EPP<login>命令和联系人授权信息提供的客户识别功能用于确定客户是否有权执行联系人信息查询命令。这些特性还确定客户机是否有权接收在查询响应中以其他方式标记为不公开的数据。
A detailed description of the EPP syntax and semantics can be found in [RFC4930]. The command mappings described here are specifically for use in provisioning and managing contact objects via EPP.
有关EPP语法和语义的详细说明，请参见[RFC4930]。这里描述的命令映射专门用于通过EPP配置和管理联系人对象。
EPP provides three commands to retrieve contact information: <check> to determine if a contact object can be provisioned within a repository, <info> to retrieve detailed information associated with a contact object, and <transfer> to retrieve contact object transfer status information.
EPP提供了三个用于检索联系人信息的命令：<check>用于确定是否可以在存储库中配置联系人对象，<info>用于检索与联系人对象关联的详细信息，<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 a <contact:check> element that identifies the contact namespace. The <contact:check> element contains the following child elements:
除了标准的EPP命令元素外，<check>命令还必须包含标识联系人名称空间的<contact:check>元素。<contact:check>元素包含以下子元素：
- One or more <contact:id> elements that contain the server-unique identifier of the contact objects to be queried.
- 包含要查询的联系人对象的服务器唯一标识符的一个或多个<contact: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: <contact:check
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:id>sah8013</contact:id>
C: <contact:id>8013sah</contact:id>
C: </contact: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: <contact:check
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:id>sah8013</contact:id>
C: <contact:id>8013sah</contact:id>
C: </contact: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 <contact:chkData> element that identifies the contact namespace. The <contact:chkData> element contains one or more <contact:cd> elements that contain the following child elements:
成功处理<check>命令后，EPP<resData>元素必须包含标识联系人命名空间的子<contact:chkData>元素。<contact:chkData>元素包含一个或多个<contact:cd>元素，这些元素包含以下子元素：
- A <contact: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.
- 标识查询对象的<contact:id>元素。此元素必须包含一个“avail”属性，该属性的值表示在<check>命令完成时对象的可用性（是否可以设置）。值“1”或“true”表示可以设置对象。值“0”或“false”表示无法设置对象。
- An OPTIONAL <contact: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 MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English).
- 一个可选的<contact:reason>元素，当无法设置对象时可以提供该元素。如果存在，此元素包含特定于服务器的文本，以帮助解释无法设置对象的原因。该文本必须以之前与客户协商的回复语言表示；如果协商值不是默认值“en”（英语），则可能存在可选的“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>Command completed successfully</msg>
S: </result>
S: <resData>
S: <contact:chkData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:cd>
S: <contact:id avail="1">sh8013</contact:id>
S: </contact:cd>
S: <contact:cd>
S: <contact:id avail="0">sah8013</contact:id>
S: <contact:reason>In use</contact:reason>
S: </contact:cd>
S: <contact:cd>
S: <contact:id avail="1">8013sah</contact:id>
S: </contact:cd>
S: </contact: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>Command completed successfully</msg>
S: </result>
S: <resData>
S: <contact:chkData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:cd>
S: <contact:id avail="1">sh8013</contact:id>
S: </contact:cd>
S: <contact:cd>
S: <contact:id avail="0">sah8013</contact:id>
S: <contact:reason>In use</contact:reason>
S: </contact:cd>
S: <contact:cd>
S: <contact:id avail="1">8013sah</contact:id>
S: </contact:cd>
S: </contact: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 a contact object. In addition to the standard EPP command elements, the <info> command MUST contain a <contact:info> element that identifies the contact namespace. The <contact:info> element contains the following child elements:
EPP<info>命令用于检索与联系人对象关联的信息。除了标准EPP命令元素外，<info>命令还必须包含标识联系人名称空间的<contact:info>元素。<contact:info>元素包含以下子元素：
- A <contact:id> element that contains the server-unique identifier of the contact object to be queried.
- 包含要查询的联系人对象的服务器唯一标识符的<contact:id>元素。
- An OPTIONAL <contact:authInfo> element that contains authorization information associated with the contact object. If this element is not provided or if the authorization information is invalid, server policy determines if the command is rejected or if response information will be returned to the client.
- 可选的<contact:authInfo>元素，包含与联系人对象关联的授权信息。如果未提供此元素或授权信息无效，服务器策略将确定命令是否被拒绝或响应信息是否将返回给客户端。
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: <contact:info
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: </contact: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: <contact:info
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: </contact: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 <contact:infData> element that identifies the contact namespace. The <contact:infData> element contains the following child elements:
成功处理<info>命令后，EPP<resData>元素必须包含标识联系人命名空间的子<contact:infData>元素。<contact:infData>元素包含以下子元素：
- A <contact:id> element that contains the server-unique identifier of the contact object.
- 包含联系人对象的服务器唯一标识符的<contact:id>元素。
- A <contact:roid> element that contains the Repository Object IDentifier assigned to the contact object when the object was created.
- 一个<contact:roid>元素，包含创建联系人对象时分配给该联系人对象的存储库对象标识符。
- One or more <contact:status> elements that describe the status of the contact object.
- 描述接触对象状态的一个或多个<contact:status>元素。
- One or two <contact: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 UTF-8 that can be represented in the 7-bit US-ASCII character set. If a localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The <contact:postalInfo> element contains the following child elements:
- 包含邮政地址信息的一个或两个<contact:postalInfo>元素。提供了两个元素，以便以国际化和本地化形式提供地址信息；“type”属性用于标识这两种形式。如果提供了国际化表单（type=“int”），则元素内容必须以UTF-8的子集表示，该子集可以用7位US-ASCII字符集表示。如果提供了本地化形式（type=“loc”），元素内容可以用不受限制的UTF-8表示。<contact:postalInfo>元素包含以下子元素：
- A <contact:name> element that contains the name of the individual or role represented by the contact.
- 包含联系人所代表的个人或角色的名称的<contact:name>元素。
- An OPTIONAL <contact:org> element that contains the name of the organization with which the contact is affiliated.
- 可选的<contact:org>元素，包含联系人所属组织的名称。
- A <contact:addr> element that contains address information associated with the contact. A <contact:addr> element contains the following child elements:
- 包含与联系人关联的地址信息的<contact:addr>元素。<contact:addr>元素包含以下子元素：
- One, two, or three OPTIONAL <contact:street> elements that contain the contact's street address.
- 包含联系人街道地址的一个、两个或三个可选<contact:street>元素。
- A <contact:city> element that contains the contact's city.
- 包含联系人所在城市的<contact:city>元素。
- An OPTIONAL <contact:sp> element that contains the contact's state or province.
- 包含联系人所在州或省的可选<contact:sp>元素。
- An OPTIONAL <contact:pc> element that contains the contact's postal code.
- 包含联系人邮政编码的可选<contact:pc>元素。
- A <contact:cc> element that contains the contact's country code.
- 包含联系人国家代码的<contact:cc>元素。
- An OPTIONAL <contact:voice> element that contains the contact's voice telephone number.
- 包含联系人语音电话号码的可选<contact:voice>元素。
- An OPTIONAL <contact:fax> element that contains the contact's facsimile telephone number.
- 包含联系人传真电话号码的可选<contact:fax>元素。
- A <contact:email> element that contains the contact's email address.
- 包含联系人电子邮件地址的<contact:email>元素。
- A <contact:clID> element that contains the identifier of the sponsoring client.
- 包含发起客户端标识符的<contact:clID>元素。
- A <contact:crID> element that contains the identifier of the client that created the contact object.
- 包含创建联系人对象的客户端标识符的<contact:crID>元素。
- A <contact:crDate> element that contains the date and time of contact object creation.
- 包含联系人对象创建日期和时间的<contact:crDate>元素。
- A <contact:upID> element that contains the identifier of the client that last updated the contact object. This element MUST NOT be present if the contact has never been modified.
- 包含上次更新联系人对象的客户端标识符的<contact:upID>元素。如果从未修改过触点，则不得存在此元素。
- A <contact:upDate> element that contains the date and time of the most recent contact object modification. This element MUST NOT be present if the contact object has never been modified.
- 包含最近修改联系人对象的日期和时间的<contact:upDate>元素。如果从未修改过contact对象，则此元素不得存在。
- A <contact:trDate> element that contains the date and time of the most recent successful contact object transfer. This element MUST NOT be provided if the contact object has never been transferred.
- 一个<contact:trDate>元素，包含最近一次成功的联系人对象传输的日期和时间。如果从未传输接触对象，则不得提供此元素。
- A <contact:authInfo> element that contains authorization information associated with the contact object. This element MUST NOT be provided if the querying client is not the current sponsoring client.
- 包含与联系人对象关联的授权信息的<contact:authInfo>元素。如果查询客户端不是当前发起客户端，则不得提供此元素。
- An OPTIONAL <contact:disclose> element that identifies elements that require exceptional server operator handling to allow or restrict disclosure to third parties. See Section 2.9 for a description of the child elements contained within the <contact: disclose> element.
- 可选的<contact:expose>元素，用于标识需要特殊服务器操作员处理的元素，以允许或限制向第三方披露。参见第2.9节，了解<contact:discover>元素中包含的子元素的描述。
Example <info> response for an authorized client:
授权客户的<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>Command completed successfully</msg>
S: </result>
S: <resData>
S: <contact:infData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:roid>SH8013-REP</contact:roid>
S: <contact:status s="linked"/>
S: <contact:status s="clientDeleteProhibited"/>
S: <contact:postalInfo type="int">
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>Command completed successfully</msg>
S: </result>
S: <resData>
S: <contact:infData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:roid>SH8013-REP</contact:roid>
S: <contact:status s="linked"/>
S: <contact:status s="clientDeleteProhibited"/>
S: <contact:postalInfo type="int">
S: <contact:name>John Doe</contact:name>
S: <contact:org>Example Inc.</contact:org>
S: <contact:addr>
S: <contact:street>123 Example Dr.</contact:street>
S: <contact:street>Suite 100</contact:street>
S: <contact:city>Dulles</contact:city>
S: <contact:sp>VA</contact:sp>
S: <contact:pc>20166-6503</contact:pc>
S: <contact:cc>US</contact:cc>
S: </contact:addr>
S: </contact:postalInfo>
S: <contact:voice x="1234">+1.7035555555</contact:voice>
S: <contact:fax>+1.7035555556</contact:fax>
S: <contact:email>jdoe@example.com</contact:email>
S: <contact:clID>ClientY</contact:clID>
S: <contact:crID>ClientX</contact:crID>
S: <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
S: <contact:upID>ClientX</contact:upID>
S: <contact:upDate>1999-12-03T09:00:00.0Z</contact:upDate>
S: <contact:trDate>2000-04-08T09:00:00.0Z</contact:trDate>
S: <contact:authInfo>
S: <contact:pw>2fooBAR</contact:pw>
S: </contact:authInfo>
S: <contact:disclose flag="0">
S: <contact:voice/>
S: <contact:email/>
S: </contact:disclose>
S: </contact:infData>
S: </resData>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S: <contact:name>John Doe</contact:name>
S: <contact:org>Example Inc.</contact:org>
S: <contact:addr>
S: <contact:street>123 Example Dr.</contact:street>
S: <contact:street>Suite 100</contact:street>
S: <contact:city>Dulles</contact:city>
S: <contact:sp>VA</contact:sp>
S: <contact:pc>20166-6503</contact:pc>
S: <contact:cc>US</contact:cc>
S: </contact:addr>
S: </contact:postalInfo>
S: <contact:voice x="1234">+1.7035555555</contact:voice>
S: <contact:fax>+1.7035555556</contact:fax>
S: <contact:email>jdoe@example.com</contact:email>
S: <contact:clID>ClientY</contact:clID>
S: <contact:crID>ClientX</contact:crID>
S: <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
S: <contact:upID>ClientX</contact:upID>
S: <contact:upDate>1999-12-03T09:00:00.0Z</contact:upDate>
S: <contact:trDate>2000-04-08T09:00:00.0Z</contact:trDate>
S: <contact:authInfo>
S: <contact:pw>2fooBAR</contact:pw>
S: </contact:authInfo>
S: <contact:disclose flag="0">
S: <contact:voice/>
S: <contact:email/>
S: </contact:disclose>
S: </contact: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 EPP <transfer> command provides a query operation that allows a client to determine real-time status of pending and completed transfer requests. In addition to the standard EPP command elements, the <transfer> command MUST contain an "op" attribute with value "query", and a <contact:transfer> element that identifies the contact namespace. The <contact:transfer> element MUST contain the following child elements:
EPP<transfer>命令提供一个查询操作，允许客户端确定挂起和完成的传输请求的实时状态。除了标准的EPP命令元素外，<transfer>命令必须包含一个值为“query”的“op”属性和一个标识联系人名称空间的<contact:transfer>元素。<contact:transfer>元素必须包含以下子元素：
- A <contact:id> element that contains the server-unique identifier of the contact object to be queried.
- 包含要查询的联系人对象的服务器唯一标识符的<contact:id>元素。
- An OPTIONAL <contact:authInfo> element that contains authorization information associated with the contact object. If this element is not provided or if the authorization information is invalid, server policy determines whether the command is rejected or the response information will be returned to the client.
- 可选的<contact:authInfo>元素，包含与联系人对象关联的授权信息。如果未提供此元素或授权信息无效，服务器策略将确定是拒绝该命令还是将响应信息返回给客户端。
Example <transfer> query command:
示例<transfer>查询命令：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <transfer op="query">
C: <contact:transfer
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: </contact:transfer>
C: </transfer>
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: <transfer op="query">
C: <contact:transfer
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: </contact:transfer>
C: </transfer>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When a <transfer> query command has been processed successfully, the EPP <resData> element MUST contain a child <contact:trnData> element that identifies the contact namespace. The <contact:trnData> element contains the following child elements:
成功处理<transfer>查询命令后，EPP<resData>元素必须包含标识联系人命名空间的子<contact:trnda>元素。<contact:trnda>元素包含以下子元素：
- A <contact:id> element that contains the server-unique identifier for the queried contact.
- 包含所查询联系人的服务器唯一标识符的<contact:id>元素。
- A <contact:trStatus> element that contains the state of the most recent transfer request.
- 包含最近传输请求状态的<contact:trStatus>元素。
- A <contact:reID> element that contains the identifier of the client that requested the object transfer.
- 包含请求对象传输的客户端标识符的<contact:reID>元素。
- A <contact:reDate> element that contains the date and time that the transfer was requested.
- 包含请求传输的日期和时间的<contact:reDate>元素。
- A <contact:acID> element that contains the identifier of the client that SHOULD act upon a PENDING transfer request. For all other status types, the value identifies the client that took the indicated action.
- 一个<contact:acID>元素，包含应根据挂起的传输请求进行操作的客户端的标识符。对于所有其他状态类型，该值标识执行指定操作的客户端。
- A <contact:acDate> element that contains the date and time of a required or completed response. For a pending request, the value identifies the date and time by which a response is required before an automated response action SHOULD be taken by the server. For all other status types, the value identifies the date and time when the request was completed.
- 包含所需或完成响应的日期和时间的<contact:acDate>元素。对于挂起的请求，该值标识在服务器执行自动响应操作之前需要响应的日期和时间。对于所有其他状态类型，该值标识请求完成的日期和时间。
Example <transfer> query response:
示例<transfer>查询响应：
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>Command completed successfully</msg>
S: </result>
S: <resData>
S: <contact:trnData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:trStatus>pending</contact:trStatus>
S: <contact:reID>ClientX</contact:reID>
S: <contact:reDate>2000-06-06T22:00:00.0Z</contact:reDate>
S: <contact:acID>ClientY</contact:acID>
S: <contact:acDate>2000-06-11T22:00:00.0Z</contact:acDate>
S: </contact:trnData>
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>Command completed successfully</msg>
S: </result>
S: <resData>
S: <contact:trnData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:trStatus>pending</contact:trStatus>
S: <contact:reID>ClientX</contact:reID>
S: <contact:reDate>2000-06-06T22:00:00.0Z</contact:reDate>
S: <contact:acID>ClientY</contact:acID>
S: <contact:acDate>2000-06-11T22:00:00.0Z</contact:acDate>
S: </contact:trnData>
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 <transfer> query command cannot be processed for any reason.
如果由于任何原因无法处理<transfer>查询命令，则必须返回EPP错误响应。
EPP provides four commands to transform contact object information: <create> to create an instance of a contact object, <delete> to delete an instance of a contact object, <transfer> to manage contact object sponsorship changes, and <update> to change information associated with a contact object. This document does not define a mapping for the EPP <renew> command.
EPP提供四个命令来转换联系人对象信息：<create>创建联系人对象实例，<delete>删除联系人对象实例，<transfer>管理联系人对象赞助更改，以及<update>更改与联系人对象相关联的信息。本文档未定义EPP<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 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, all clients involved in the transaction MUST be notified using a service message that the action has been completed and that the status of the object has changed.
在完成请求的操作之前，需要进行审查。在这种情况下，服务器必须向客户端返回1001响应代码，以说明命令已被接收和处理，但请求的操作处于挂起状态。服务器还必须管理作为命令主题的对象的状态，以反映请求操作的启动和完成。操作完成后，必须使用服务消息通知事务中涉及的所有客户端操作已完成，并且对象的状态已更改。
The EPP <create> command provides a transform operation that allows a client to create a contact object. In addition to the standard EPP command elements, the <create> command MUST contain a <contact: create> element that identifies the contact namespace. The <contact: create> element contains the following child elements:
EPP<create>命令提供一个转换操作，允许客户端创建联系人对象。除了标准的EPP命令元素外，<create>命令还必须包含标识联系人名称空间的<contact:create>元素。<contact:create>元素包含以下子元素：
- A <contact:id> element that contains the desired server-unique identifier for the contact to be created.
- 包含要创建的联系人所需的服务器唯一标识符的<contact:id>元素。
- One or two <contact: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 UTF-8 that can be represented in the 7-bit US-ASCII character set. If a localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The <contact:postalInfo> element contains the following child elements:
- 包含邮政地址信息的一个或两个<contact:postalInfo>元素。提供了两个元素，以便以国际化和本地化形式提供地址信息；“type”属性用于标识这两种形式。如果提供了国际化表单（type=“int”），则元素内容必须以UTF-8的子集表示，该子集可以用7位US-ASCII字符集表示。如果提供了本地化形式（type=“loc”），元素内容可以用不受限制的UTF-8表示。<contact:postalInfo>元素包含以下子元素：
- A <contact:name> element that contains the name of the individual or role represented by the contact.
- 包含联系人所代表的个人或角色的名称的<contact:name>元素。
- An OPTIONAL <contact:org> element that contains the name of the organization with which the contact is affiliated.
- 可选的<contact:org>元素，包含联系人所属组织的名称。
- A <contact:addr> element that contains address information associated with the contact. A <contact:addr> element contains the following child elements:
- 包含与联系人关联的地址信息的<contact:addr>元素。<contact:addr>元素包含以下子元素：
- One, two, or three OPTIONAL <contact:street> elements that contain the contact's street address.
- 包含联系人街道地址的一个、两个或三个可选<contact:street>元素。
- A <contact:city> element that contains the contact's city.
- 包含联系人所在城市的<contact:city>元素。
- An OPTIONAL <contact:sp> element that contains the contact's state or province.
- 包含联系人所在州或省的可选<contact:sp>元素。
- An OPTIONAL <contact:pc> element that contains the contact's postal code.
- 包含联系人邮政编码的可选<contact:pc>元素。
- A <contact:cc> element that contains the contact's country code.
- 包含联系人国家代码的<contact:cc>元素。
- An OPTIONAL <contact:voice> element that contains the contact's voice telephone number.
- 包含联系人语音电话号码的可选<contact:voice>元素。
- An OPTIONAL <contact:fax> element that contains the contact's facsimile telephone number.
- 包含联系人传真电话号码的可选<contact:fax>元素。
- A <contact:email> element that contains the contact's email address.
- 包含联系人电子邮件地址的<contact:email>元素。
- A <contact:authInfo> element that contains authorization information to be associated with the contact object. This mapping includes a password-based authentication mechanism, but the schema allows new mechanisms to be defined in new schemas.
- 包含要与联系人对象关联的授权信息的<contact:authInfo>元素。此映射包括基于密码的身份验证机制，但模式允许在新模式中定义新机制。
- An OPTIONAL <contact:disclose> element that allows a client to identify elements that require exceptional server operator handling to allow or restrict disclosure to third parties. See Section 2.9 for a description of the child elements contained within the <contact:disclose> element.
- 可选的<contact:expose>元素，允许客户端识别需要特殊服务器操作员处理的元素，以允许或限制向第三方披露。参见第2.9节，了解<contact:discover>元素中包含的子元素的描述。
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: <contact:create
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:postalInfo type="int">
C: <contact:name>John Doe</contact:name>
C: <contact:org>Example Inc.</contact:org>
C: <contact:addr>
C: <contact:street>123 Example Dr.</contact:street>
C: <contact:street>Suite 100</contact:street>
C: <contact:city>Dulles</contact:city>
C: <contact:sp>VA</contact:sp>
C: <contact:pc>20166-6503</contact:pc>
C: <contact:cc>US</contact:cc>
C: </contact:addr>
C: </contact:postalInfo>
C: <contact:voice x="1234">+1.7035555555</contact:voice>
C: <contact:fax>+1.7035555556</contact:fax>
C: <contact:email>jdoe@example.com</contact:email>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: <contact:disclose flag="0">
C: <contact:voice/>
C: <contact:email/>
C: </contact:disclose>
C: </contact:create>
C: </create>
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: <create>
C: <contact:create
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:postalInfo type="int">
C: <contact:name>John Doe</contact:name>
C: <contact:org>Example Inc.</contact:org>
C: <contact:addr>
C: <contact:street>123 Example Dr.</contact:street>
C: <contact:street>Suite 100</contact:street>
C: <contact:city>Dulles</contact:city>
C: <contact:sp>VA</contact:sp>
C: <contact:pc>20166-6503</contact:pc>
C: <contact:cc>US</contact:cc>
C: </contact:addr>
C: </contact:postalInfo>
C: <contact:voice x="1234">+1.7035555555</contact:voice>
C: <contact:fax>+1.7035555556</contact:fax>
C: <contact:email>jdoe@example.com</contact:email>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: <contact:disclose flag="0">
C: <contact:voice/>
C: <contact:email/>
C: </contact:disclose>
C: </contact:create>
C: </create>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When a <create> command has been processed successfully, the EPP <resData> element MUST contain a child <contact:creData> element that identifies the contact namespace. The <contact:creData> element contains the following child elements:
成功处理<create>命令后，EPP<resData>元素必须包含标识联系人命名空间的子<contact:creData>元素。<contact:creData>元素包含以下子元素：
- A <contact:id> element that contains the server-unique identifier for the created contact.
- 包含所创建联系人的服务器唯一标识符的<contact:id>元素。
- A <contact:crDate> element that contains the date and time of contact object creation.
- 包含联系人对象创建日期和时间的<contact: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>Command completed successfully</msg>
S: </result>
S: <resData>
S: <contact:creData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
S: </contact: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>Command completed successfully</msg>
S: </result>
S: <resData>
S: <contact:creData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
S: </contact: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 a contact object. In addition to the standard EPP command elements, the <delete> command MUST contain a <contact: delete> element that identifies the contact namespace. The <contact: delete> element MUST contain the following child element:
EPP<delete>命令提供一个转换操作，允许客户端删除联系人对象。除了标准EPP命令元素外，<delete>命令还必须包含标识联系人名称空间的<contact:delete>元素。<contact:delete>元素必须包含以下子元素：
- A <contact:id> element that contains the server-unique identifier of the contact object to be deleted.
- 包含要删除的联系人对象的服务器唯一标识符的<contact:id>元素。
A contact object SHOULD NOT be deleted if it is associated with other known objects. An associated contact SHOULD NOT be deleted until associations with other known objects have been broken. A server SHOULD notify clients of object relationships when a <delete> command is attempted and fails due to existing object relationships.
如果联系人对象与其他已知对象关联，则不应将其删除。在与其他已知对象的关联被破坏之前，不应删除关联的联系人。当尝试执行<delete>命令并且由于现有对象关系而失败时，服务器应通知客户端对象关系。
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: <contact:delete
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: </contact: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: <contact:delete
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: </contact: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>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>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 contact objects, so there is no mapping defined for the EPP <renew> command.
更新语义不适用于联系人对象，因此没有为EPP<renew>命令定义映射。
The EPP <transfer> command provides a transform operation that allows a client to manage requests to transfer the sponsorship of a contact object. In addition to the standard EPP command elements, the <transfer> command MUST contain a <contact:transfer> element that identifies the contact namespace. The <contact:transfer> element contains the following child elements:
EPP<transfer>命令提供了一个转换操作，允许客户端管理请求以传输联系人对象的赞助。除了标准EPP命令元素外，<transfer>命令还必须包含标识联系人名称空间的<contact:transfer>元素。<contact:transfer>元素包含以下子元素：
- A <contact:id> element that contains the server-unique identifier of the contact object for which a transfer request is to be created, approved, rejected, or cancelled.
- 一个<contact:id>元素，包含要为其创建、批准、拒绝或取消传输请求的联系人对象的服务器唯一标识符。
- A <contact:authInfo> element that contains authorization information associated with the contact object.
- 包含与联系人对象关联的授权信息的<contact:authInfo>元素。
Every EPP <transfer> command MUST contain an "op" attribute that identifies the transfer operation to be performed as defined in [RFC4930].
每个EPP<transfer>命令都必须包含一个“op”属性，该属性标识了[RFC4930]中定义的要执行的传输操作。
Example <transfer> request command:
示例<transfer>请求命令：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <transfer op="request">
C: <contact:transfer
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: </contact:transfer>
C: </transfer>
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: <transfer op="request">
C: <contact:transfer
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: </contact:transfer>
C: </transfer>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When a <transfer> command has been processed successfully, the EPP <resData> element MUST contain a child <contact:trnData> element that identifies the contact namespace. The <contact:trnData> element contains the same child elements defined for a <transfer> query response.
成功处理<transfer>命令后，EPP<resData>元素必须包含标识联系人命名空间的子<contact:trnda>元素。<contact:trnda>元素包含为<transfer>查询响应定义的相同子元素。
Example <transfer> response:
示例<transfer>响应：
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>Command completed successfully; action pending</msg>
S: </result>
S: <resData>
S: <contact:trnData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:trStatus>pending</contact:trStatus>
S: <contact:reID>ClientX</contact:reID>
S: <contact:reDate>2000-06-08T22:00:00.0Z</contact:reDate>
S: <contact:acID>ClientY</contact:acID>
S: <contact:acDate>2000-06-13T22:00:00.0Z</contact:acDate>
S: </contact:trnData>
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="1001">
S: <msg>Command completed successfully; action pending</msg>
S: </result>
S: <resData>
S: <contact:trnData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:trStatus>pending</contact:trStatus>
S: <contact:reID>ClientX</contact:reID>
S: <contact:reDate>2000-06-08T22:00:00.0Z</contact:reDate>
S: <contact:acID>ClientY</contact:acID>
S: <contact:acDate>2000-06-13T22:00:00.0Z</contact:acDate>
S: </contact:trnData>
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 <transfer> command cannot be processed for any reason.
如果由于任何原因无法处理<transfer>命令，则必须返回EPP错误响应。
The EPP <update> command provides a transform operation that allows a client to modify the attributes of a contact object. In addition to the standard EPP command elements, the <update> command MUST contain a <contact:update> element that identifies the contact namespace. The <contact:update> element contains the following child elements:
EPP<update>命令提供一个转换操作，允许客户端修改联系人对象的属性。除了标准的EPP命令元素外，<update>命令还必须包含标识联系人名称空间的<contact:update>元素。<contact:update>元素包含以下子元素：
- A <contact:id> element that contains the server-unique identifier of the contact object to be updated.
- 包含要更新的联系人对象的服务器唯一标识符的<contact:id>元素。
- An OPTIONAL <contact:add> element that contains attribute values to be added to the object.
- 可选的<contact:add>元素，包含要添加到对象的属性值。
- An OPTIONAL <contact:rem> element that contains attribute values to be removed from the object.
- 可选的<contact:rem>元素，包含要从对象中删除的属性值。
- An OPTIONAL <contact:chg> element that contains object attribute values to be changed.
- 可选的<contact:chg>元素，包含要更改的对象属性值。
At least one <contact:add>, <contact:rem>, or <contact: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 <contact:add> and <contact:rem> elements contain the following child elements:
如果命令未扩展，则必须至少提供一个<contact:add>、<contact:rem>或<contact:chg>元素。如果存在<update>扩展，则可以省略所有这些元素。<contact:add>和<contact:rem>元素包含以下子元素：
- One or more <contact:status> elements that contain status values to be associated with or removed from the object. When specifying a value to be removed, only the attribute value is significant; element text is not required to match a value for removal.
- 一个或多个<contact:status>元素，其中包含要与对象关联或从对象中删除的状态值。指定要删除的值时，只有属性值有效；元素文本不需要与要删除的值匹配。
A <contact:chg> element contains the following OPTIONAL child elements. At least one child element MUST be present:
<contact:chg>元素包含以下可选子元素。必须至少存在一个子元素：
- One or two <contact: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 UTF-8 that can be represented in the 7-bit US-ASCII character set. If a localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8. The <contact:postalInfo> element contains the following OPTIONAL child elements:
- 包含邮政地址信息的一个或两个<contact:postalInfo>元素。提供了两个元素，以便以国际化和本地化形式提供地址信息；“type”属性用于标识这两种形式。如果提供了国际化表单（type=“int”），则元素内容必须以UTF-8的子集表示，该子集可以用7位US-ASCII字符集表示。如果提供了本地化形式（type=“loc”），元素内容可以用不受限制的UTF-8表示。<contact:postalInfo>元素包含以下可选子元素：
- A <contact:name> element that contains the name of the individual or role represented by the contact.
- 包含联系人所代表的个人或角色的名称的<contact:name>元素。
- A <contact:org> element that contains the name of the organization with which the contact is affiliated.
- 包含联系人所属组织名称的<contact:org>元素。
- A <contact:addr> element that contains address information associated with the contact. A <contact:addr> element contains the following child elements:
- 包含与联系人关联的地址信息的<contact:addr>元素。<contact:addr>元素包含以下子元素：
- One, two, or three OPTIONAL <contact:street> elements that contain the contact's street address.
- 包含联系人街道地址的一个、两个或三个可选<contact:street>元素。
- A <contact:city> element that contains the contact's city.
- 包含联系人所在城市的<contact:city>元素。
- An OPTIONAL <contact:sp> element that contains the contact's state or province.
- 包含联系人所在州或省的可选<contact:sp>元素。
- An OPTIONAL <contact:pc> element that contains the contact's postal code.
- 包含联系人邮政编码的可选<contact:pc>元素。
- A <contact:cc> element that contains the contact's country code.
- 包含联系人国家代码的<contact:cc>元素。
- A <contact:voice> element that contains the contact's voice telephone number.
- 包含联系人语音电话号码的<contact:voice>元素。
- A <contact:fax> element that contains the contact's facsimile telephone number.
- 包含联系人传真电话号码的<contact:fax>元素。
- A <contact:email> element that contains the contact's email address.
- 包含联系人电子邮件地址的<contact:email>元素。
- A <contact:authInfo> element that contains authorization information associated with the contact object. This mapping includes a password-based authentication mechanism, but the schema allows new mechanisms to be defined in new schemas.
- 包含与联系人对象关联的授权信息的<contact:authInfo>元素。此映射包括基于密码的身份验证机制，但模式允许在新模式中定义新机制。
- A <contact:disclose> element that allows a client to identify elements that require exceptional server operator handling to allow or restrict disclosure to third parties. See Section 2.9 for a description of the child elements contained within the <contact:disclose> element.
- 一个<contact:discover>元素，允许客户端识别需要特殊服务器操作员处理的元素，以允许或限制向第三方披露。参见第2.9节，了解<contact:discover>元素中包含的子元素的描述。
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: <contact:update
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:add>
C: <contact:status s="clientDeleteProhibited"/>
C: </contact:add>
C: <contact:chg>
C: <contact:postalInfo type="int">
C: <contact:org/>
C: <contact:addr>
C: <contact:street>124 Example Dr.</contact:street>
C: <contact:street>Suite 200</contact:street>
C: <contact:city>Dulles</contact:city>
C: <contact:sp>VA</contact:sp>
C: <contact:pc>20166-6503</contact:pc>
C: <contact:cc>US</contact:cc>
C: </contact:addr>
C: </contact:postalInfo>
C: <contact:voice>+1.7034444444</contact:voice>
C: <contact:fax/>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: <contact:disclose flag="1">
C: <contact:voice/>
C: <contact:email/>
C: </contact:disclose>
C: </contact:chg>
C: </contact: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: <contact:update
C: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
C: <contact:id>sh8013</contact:id>
C: <contact:add>
C: <contact:status s="clientDeleteProhibited"/>
C: </contact:add>
C: <contact:chg>
C: <contact:postalInfo type="int">
C: <contact:org/>
C: <contact:addr>
C: <contact:street>124 Example Dr.</contact:street>
C: <contact:street>Suite 200</contact:street>
C: <contact:city>Dulles</contact:city>
C: <contact:sp>VA</contact:sp>
C: <contact:pc>20166-6503</contact:pc>
C: <contact:cc>US</contact:cc>
C: </contact:addr>
C: </contact:postalInfo>
C: <contact:voice>+1.7034444444</contact:voice>
C: <contact:fax/>
C: <contact:authInfo>
C: <contact:pw>2fooBAR</contact:pw>
C: </contact:authInfo>
C: <contact:disclose flag="1">
C: <contact:voice/>
C: <contact:email/>
C: </contact:disclose>
C: </contact:chg>
C: </contact: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>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>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 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>Command completed successfully; action pending</msg>
S: </result>
S: <resData>
S: <contact:creData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
S: </contact: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="1001">
S: <msg>Command completed successfully; action pending</msg>
S: </result>
S: <resData>
S: <contact:creData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id>sh8013</contact:id>
S: <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
S: </contact: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 contact 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 either by queuing a service message for retrieval via the <poll> command or by using an out-of-band mechanism to inform the client of the request.
返回此响应后，联系人对象的状态必须包括“pendingCreate”。服务器操作员脱机审查请求，并通过通过<poll>命令将服务消息排队以供检索，或通过使用带外机制将审查结果通知客户端。
The service message MUST contain text in the <response>, <msgQ>, <msg> element that describes the notification. In addition, the EPP <resData> element MUST contain a child <contact:panData> element that identifies the contact namespace. The <contact:panData> element contains the following child elements:
服务消息必须包含描述通知的<response>，<msgQ>，<msg>元素中的文本。此外，EPP<resData>元素必须包含标识联系人命名空间的子元素<contact:panData>。<contact:panData>元素包含以下子元素：
- A <contact:id> element that contains the server-unique identifier of the contact object. The <contact: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.
- 包含联系人对象的服务器唯一标识符的<contact:id>元素。<contact:id>元素包含必需的“paResult”属性。正布尔值表示请求已被批准并完成。负布尔值表示请求已被拒绝，且未采取请求的操作。
- A <contact: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.
- 一个<contact:patid>元素，包含处理命令的原始响应返回的客户端事务标识符和服务器事务标识符。客户端事务标识符是可选的，仅当客户端使用原始的<create>命令提供了标识符时才会返回。
- A <contact:paDate> element that contains the date and time describing when review of the requested action was completed.
- 包含日期和时间的<contact: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>Command completed successfully; ack to dequeue</msg>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>1999-04-04T22:01:00.0Z</qDate>
S: <msg>Pending action completed successfully.</msg>
S: </msgQ>
S: <resData>
S: <contact:panData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id paResult="1">sh8013</contact:id>
S: <contact:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </contact:paTRID>
S: <contact:paDate>1999-04-04T22:00:00.0Z</contact:paDate>
S: </contact:panData>
S: </resData>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</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="1301">
S: <msg>Command completed successfully; ack to dequeue</msg>
S: </result>
S: <msgQ count="5" id="12345">
S: <qDate>1999-04-04T22:01:00.0Z</qDate>
S: <msg>Pending action completed successfully.</msg>
S: </msgQ>
S: <resData>
S: <contact:panData
S: xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
S: <contact:id paResult="1">sh8013</contact:id>
S: <contact:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </contact:paTRID>
S: <contact:paDate>1999-04-04T22:00:00.0Z</contact:paDate>
S: </contact: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:contact-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-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:contact-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-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
contact provisioning schema.
</documentation>
</annotation>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
contact provisioning schema.
</documentation>
</annotation>
<!--
Child elements found in EPP commands.
-->
<element name="check" type="contact:mIDType"/>
<element name="create" type="contact:createType"/>
<element name="delete" type="contact:sIDType"/>
<element name="info" type="contact:authIDType"/>
<element name="transfer" type="contact:authIDType"/>
<element name="update" type="contact:updateType"/>
<!--
Child elements found in EPP commands.
-->
<element name="check" type="contact:mIDType"/>
<element name="create" type="contact:createType"/>
<element name="delete" type="contact:sIDType"/>
<element name="info" type="contact:authIDType"/>
<element name="transfer" type="contact:authIDType"/>
<element name="update" type="contact:updateType"/>
<!--
Utility types.
-->
<simpleType name="ccType">
<restriction base="token">
<length value="2"/>
</restriction>
</simpleType>
<!--
Utility types.
-->
<simpleType name="ccType">
<restriction base="token">
<length value="2"/>
</restriction>
</simpleType>
<complexType name="e164Type">
<simpleContent>
<extension base="contact:e164StringType">
<attribute name="x" type="token"/>
</extension>
</simpleContent>
</complexType>
<complexType name="e164Type">
<simpleContent>
<extension base="contact: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="pcType">
<simpleType name="pcType">
<restriction base="token">
<maxLength value="16"/>
</restriction>
</simpleType>
<restriction base="token">
<maxLength value="16"/>
</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>
<!--
Child elements of the <create> command.
-->
<complexType name="createType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="postalInfo" type="contact:postalInfoType"
maxOccurs="2"/>
<element name="voice" type="contact:e164Type"
minOccurs="0"/>
<element name="fax" type="contact:e164Type"
minOccurs="0"/>
<element name="email" type="eppcom:minTokenType"/>
<element name="authInfo" type="contact:authInfoType"/>
<element name="disclose" type="contact:discloseType"
minOccurs="0"/>
</sequence>
</complexType>
<!--
Child elements of the <create> command.
-->
<complexType name="createType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="postalInfo" type="contact:postalInfoType"
maxOccurs="2"/>
<element name="voice" type="contact:e164Type"
minOccurs="0"/>
<element name="fax" type="contact:e164Type"
minOccurs="0"/>
<element name="email" type="eppcom:minTokenType"/>
<element name="authInfo" type="contact:authInfoType"/>
<element name="disclose" type="contact:discloseType"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="postalInfoType">
<sequence>
<element name="name" type="contact:postalLineType"/>
<element name="org" type="contact:optPostalLineType"
minOccurs="0"/>
<element name="addr" type="contact:addrType"/>
</sequence>
<attribute name="type" type="contact:postalInfoEnumType"
use="required"/>
</complexType>
<complexType name="postalInfoType">
<sequence>
<element name="name" type="contact:postalLineType"/>
<element name="org" type="contact:optPostalLineType"
minOccurs="0"/>
<element name="addr" type="contact:addrType"/>
</sequence>
<attribute name="type" type="contact:postalInfoEnumType"
use="required"/>
</complexType>
<simpleType name="postalInfoEnumType">
<restriction base="token">
<enumeration value="loc"/>
<enumeration value="int"/>
</restriction>
</simpleType>
<simpleType name="postalInfoEnumType">
<restriction base="token">
<enumeration value="loc"/>
<enumeration value="int"/>
</restriction>
</simpleType>
<complexType name="addrType">
<sequence>
<element name="street" type="contact:optPostalLineType"
minOccurs="0" maxOccurs="3"/>
<element name="city" type="contact:postalLineType"/>
<element name="sp" type="contact:optPostalLineType"
minOccurs="0"/>
<element name="pc" type="contact:pcType"
minOccurs="0"/>
<element name="cc" type="contact:ccType"/>
</sequence>
</complexType>
<complexType name="addrType">
<sequence>
<element name="street" type="contact:optPostalLineType"
minOccurs="0" maxOccurs="3"/>
<element name="city" type="contact:postalLineType"/>
<element name="sp" type="contact:optPostalLineType"
minOccurs="0"/>
<element name="pc" type="contact:pcType"
minOccurs="0"/>
<element name="cc" type="contact:ccType"/>
</sequence>
</complexType>
<complexType name="authInfoType">
<choice>
<element name="pw" type="eppcom:pwAuthInfoType"/>
<element name="ext" type="eppcom:extAuthInfoType"/>
</choice>
</complexType>
<complexType name="authInfoType">
<choice>
<element name="pw" type="eppcom:pwAuthInfoType"/>
<element name="ext" type="eppcom:extAuthInfoType"/>
</choice>
</complexType>
<complexType name="discloseType">
<sequence>
<element name="name" type="contact:intLocType"
minOccurs="0" maxOccurs="2"/>
<element name="org" type="contact:intLocType"
minOccurs="0" maxOccurs="2"/>
<element name="addr" type="contact:intLocType"
minOccurs="0" maxOccurs="2"/>
<element name="voice" minOccurs="0"/>
<element name="fax" minOccurs="0"/>
<element name="email" minOccurs="0"/>
</sequence>
<attribute name="flag" type="boolean" use="required"/>
</complexType>
<complexType name="discloseType">
<sequence>
<element name="name" type="contact:intLocType"
minOccurs="0" maxOccurs="2"/>
<element name="org" type="contact:intLocType"
minOccurs="0" maxOccurs="2"/>
<element name="addr" type="contact:intLocType"
minOccurs="0" maxOccurs="2"/>
<element name="voice" minOccurs="0"/>
<element name="fax" minOccurs="0"/>
<element name="email" minOccurs="0"/>
</sequence>
<attribute name="flag" type="boolean" use="required"/>
</complexType>
<complexType name="intLocType">
<attribute name="type" type="contact:postalInfoEnumType"
use="required"/>
</complexType>
<complexType name="intLocType">
<attribute name="type" type="contact:postalInfoEnumType"
use="required"/>
</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 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>
<!--
Child elements of the <info> and <transfer> commands.
-->
<complexType name="authIDType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="authInfo" type="contact:authInfoType"
minOccurs="0"/>
</sequence>
</complexType>
<!--
Child elements of the <info> and <transfer> commands.
-->
<complexType name="authIDType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="authInfo" type="contact:authInfoType"
minOccurs="0"/>
</sequence>
</complexType>
<!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="add" type="contact:addRemType"
minOccurs="0"/>
<element name="rem" type="contact:addRemType"
minOccurs="0"/>
<element name="chg" type="contact:chgType"
minOccurs="0"/>
</sequence>
</complexType>
<!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="add" type="contact:addRemType"
minOccurs="0"/>
<element name="rem" type="contact:addRemType"
minOccurs="0"/>
<element name="chg" type="contact:chgType"
minOccurs="0"/>
</sequence>
</complexType>
<!-- Data elements that can be added or removed. -->
<!-- 可以添加或删除的数据元素。-->
<complexType name="addRemType">
<sequence>
<element name="status" type="contact:statusType"
maxOccurs="7"/>
</sequence>
</complexType>
<complexType name="addRemType">
<sequence>
<element name="status" type="contact:statusType"
maxOccurs="7"/>
</sequence>
</complexType>
<!--
Data elements that can be changed.
-->
<complexType name="chgType">
<sequence>
<element name="postalInfo" type="contact:chgPostalInfoType"
minOccurs="0" maxOccurs="2"/>
<element name="voice" type="contact:e164Type"
minOccurs="0"/>
<element name="fax" type="contact:e164Type"
minOccurs="0"/>
<element name="email" type="eppcom:minTokenType"
minOccurs="0"/>
<element name="authInfo" type="contact:authInfoType"
minOccurs="0"/>
<element name="disclose" type="contact:discloseType"
minOccurs="0"/>
</sequence>
</complexType>
<!--
Data elements that can be changed.
-->
<complexType name="chgType">
<sequence>
<element name="postalInfo" type="contact:chgPostalInfoType"
minOccurs="0" maxOccurs="2"/>
<element name="voice" type="contact:e164Type"
minOccurs="0"/>
<element name="fax" type="contact:e164Type"
minOccurs="0"/>
<element name="email" type="eppcom:minTokenType"
minOccurs="0"/>
<element name="authInfo" type="contact:authInfoType"
minOccurs="0"/>
<element name="disclose" type="contact:discloseType"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="chgPostalInfoType">
<sequence>
<element name="name" type="contact:postalLineType"
minOccurs="0"/>
<element name="org" type="contact:optPostalLineType"
minOccurs="0"/>
<element name="addr" type="contact:addrType"
minOccurs="0"/>
</sequence>
<attribute name="type" type="contact:postalInfoEnumType"
use="required"/>
</complexType>
<complexType name="chgPostalInfoType">
<sequence>
<element name="name" type="contact:postalLineType"
minOccurs="0"/>
<element name="org" type="contact:optPostalLineType"
minOccurs="0"/>
<element name="addr" type="contact:addrType"
minOccurs="0"/>
</sequence>
<attribute name="type" type="contact:postalInfoEnumType"
use="required"/>
</complexType>
<!--
Child response elements.
-->
<element name="chkData" type="contact:chkDataType"/>
<element name="creData" type="contact:creDataType"/>
<element name="infData" type="contact:infDataType"/>
<element name="panData" type="contact:panDataType"/>
<element name="trnData" type="contact:trnDataType"/>
<!--
Child response elements.
-->
<element name="chkData" type="contact:chkDataType"/>
<element name="creData" type="contact:creDataType"/>
<element name="infData" type="contact:infDataType"/>
<element name="panData" type="contact:panDataType"/>
<element name="trnData" type="contact:trnDataType"/>
<!--
<check> response elements.
-->
<complexType name="chkDataType">
<sequence>
<element name="cd" type="contact:checkType"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
<check> response elements.
-->
<complexType name="chkDataType">
<sequence>
<element name="cd" type="contact:checkType"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="checkType">
<sequence>
<element name="id" type="contact:checkIDType"/>
<element name="reason" type="eppcom:reasonType"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="checkType">
<sequence>
<element name="id" type="contact: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>
<!--
<create> response elements.
-->
<complexType name="creDataType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="crDate" type="dateTime"/>
</sequence>
</complexType>
<!--
<create> response elements.
-->
<complexType name="creDataType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="crDate" type="dateTime"/>
</sequence>
</complexType>
<!--
<info> response elements.
-->
<complexType name="infDataType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="roid" type="eppcom:roidType"/>
<element name="status" type="contact:statusType"
maxOccurs="7"/>
<element name="postalInfo" type="contact:postalInfoType"
maxOccurs="2"/>
<!--
<info> response elements.
-->
<complexType name="infDataType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="roid" type="eppcom:roidType"/>
<element name="status" type="contact:statusType"
maxOccurs="7"/>
<element name="postalInfo" type="contact:postalInfoType"
maxOccurs="2"/>
<element name="voice" type="contact:e164Type"
minOccurs="0"/>
<element name="fax" type="contact:e164Type"
minOccurs="0"/>
<element name="email" type="eppcom:minTokenType"/>
<element name="clID" type="eppcom:clIDType"/>
<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"/>
<element name="trDate" type="dateTime"
minOccurs="0"/>
<element name="authInfo" type="contact:authInfoType"
minOccurs="0"/>
<element name="disclose" type="contact:discloseType"
minOccurs="0"/>
</sequence>
</complexType>
<element name="voice" type="contact:e164Type"
minOccurs="0"/>
<element name="fax" type="contact:e164Type"
minOccurs="0"/>
<element name="email" type="eppcom:minTokenType"/>
<element name="clID" type="eppcom:clIDType"/>
<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"/>
<element name="trDate" type="dateTime"
minOccurs="0"/>
<element name="authInfo" type="contact:authInfoType"
minOccurs="0"/>
<element name="disclose" type="contact:discloseType"
minOccurs="0"/>
</sequence>
</complexType>
<!--
Status is a combination of attributes and an optional human-readable
message that may be expressed in languages other than English.
-->
<complexType name="statusType">
<simpleContent>
<extension base="normalizedString">
<attribute name="s" type="contact:statusValueType"
use="required"/>
<attribute name="lang" type="language"
default="en"/>
</extension>
</simpleContent>
</complexType>
<!--
Status is a combination of attributes and an optional human-readable
message that may be expressed in languages other than English.
-->
<complexType name="statusType">
<simpleContent>
<extension base="normalizedString">
<attribute name="s" type="contact:statusValueType"
use="required"/>
<attribute name="lang" type="language"
default="en"/>
</extension>
</simpleContent>
</complexType>
<simpleType name="statusValueType">
<restriction base="token">
<enumeration value="clientDeleteProhibited"/>
<enumeration value="clientTransferProhibited"/>
<enumeration value="clientUpdateProhibited"/>
<enumeration value="linked"/>
<enumeration value="ok"/>
<enumeration value="pendingCreate"/>
<enumeration value="pendingDelete"/>
<enumeration value="pendingTransfer"/>
<enumeration value="pendingUpdate"/>
<enumeration value="serverDeleteProhibited"/>
<simpleType name="statusValueType">
<restriction base="token">
<enumeration value="clientDeleteProhibited"/>
<enumeration value="clientTransferProhibited"/>
<enumeration value="clientUpdateProhibited"/>
<enumeration value="linked"/>
<enumeration value="ok"/>
<enumeration value="pendingCreate"/>
<enumeration value="pendingDelete"/>
<enumeration value="pendingTransfer"/>
<enumeration value="pendingUpdate"/>
<enumeration value="serverDeleteProhibited"/>
<enumeration value="serverTransferProhibited"/>
<enumeration value="serverUpdateProhibited"/>
</restriction>
</simpleType>
<enumeration value="serverTransferProhibited"/>
<enumeration value="serverUpdateProhibited"/>
</restriction>
</simpleType>
<!--
Pending action notification response elements.
-->
<complexType name="panDataType">
<sequence>
<element name="id" type="contact: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="contact: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>
<!--
<transfer> response elements.
-->
<complexType name="trnDataType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="trStatus" type="eppcom:trStatusType"/>
<element name="reID" type="eppcom:clIDType"/>
<element name="reDate" type="dateTime"/>
<element name="acID" type="eppcom:clIDType"/>
<element name="acDate" type="dateTime"/>
</sequence>
</complexType>
<!--
<transfer> response elements.
-->
<complexType name="trnDataType">
<sequence>
<element name="id" type="eppcom:clIDType"/>
<element name="trStatus" type="eppcom:trStatusType"/>
<element name="reID" type="eppcom:clIDType"/>
<element name="reDate" type="dateTime"/>
<element name="acID" type="eppcom:clIDType"/>
<element name="acDate" 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 and its more compact representations, including UTF-8. Conformant XML processors recognize both UTF-8 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 REQUIRED with this specification.
EPP用XML表示，它为使用Unicode字符集及其更紧凑的表示（包括UTF-8）编码信息提供了本机支持。一致性XML处理器同时识别UTF-8和UTF-16[RFC2781]。尽管XML包含通过在<？XML？>声明中使用“encoding”属性来识别和使用其他字符编码的规定，但本规范要求使用UTF-8。
All date-time values presented via EPP MUST be expressed in Universal Coordinated Time using the Gregorian calendar. The XML Schema allows use of time zone identifiers to indicate offsets from the zero meridian, but this option MUST NOT be used with EPP. The extended date-time form using upper case "T" and "Z" characters defined in [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time values as the XML Schema does not support truncated date-time forms or lower case "T" and "Z" characters.
通过EPP提供的所有日期时间值必须使用公历以全球协调时间表示。XML模式允许使用时区标识符来指示从零子午线的偏移，但此选项不得与EPP一起使用。必须使用[W3C.REC-xmlschema-2-20041028]中定义的大写“T”和“Z”字符的扩展日期时间表单来表示日期时间值，因为XML模式不支持截断日期时间表单或小写“T”和“Z”字符。
Humans, organizations, and other entities often need to represent social information in both a commonly understood character set and a locally optimized character set. This specification provides features allowing representation of social information in both a subset of UTF-8 for broad readability and unrestricted UTF-8 for local optimization.
人类、组织和其他实体通常需要在通常理解的字符集和局部优化的字符集中表示社会信息。本规范提供了允许在UTF-8子集中表示社交信息的功能，以实现广泛的可读性，并允许在不受限制的UTF-8中表示局部优化。
This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. Two URI assignments have been registered by the IANA.
本文档使用URN来描述符合[RFC3688]中描述的注册表机制的XML名称空间和XML模式。IANA已经注册了两个URI分配。
Registration request for the contact namespace:
联系人命名空间的注册请求：
URI: urn:ietf:params:xml:ns:contact-1.0
URI: urn:ietf:params:xml:ns:contact-1.0
Registrant Contact: See the "Author's Address" section of this document.
注册人联系人：请参阅本文件的“作者地址”部分。
XML: None. Namespace URIs do not represent an XML specification.
XML：没有。命名空间URI不表示XML规范。
Registration request for the contact XML schema:
联系人XML架构的注册请求：
URI: urn:ietf:params:xml:schema:contact-1.0
URI: urn:ietf:params:xml:schema:contact-1.0
Registrant Contact: See the "Author's Address" section of this document.
注册人联系人：请参阅本文件的“作者地址”部分。
XML: See the "Formal Syntax" section of this document.
XML：请参阅本文档的“正式语法”部分。
Authorization information as described in Section 2.8 is REQUIRED to create a contact object. This information is used in some query and transfer operations as an additional means of determining client authorization to perform the command. Failure to protect authorization information from inadvertent disclosure can result in unauthorized transfer operations and unauthorized information release. Both client and server MUST ensure that authorization information is stored and exchanged with high-grade encryption mechanisms to provide privacy services.
创建联系人对象需要第2.8节所述的授权信息。此信息在某些查询和传输操作中用作确定执行命令的客户端授权的附加手段。未能保护授权信息不被无意中泄露可能会导致未经授权的传输操作和未经授权的信息发布。客户端和服务器都必须确保使用高级加密机制存储和交换授权信息，以提供隐私服务。
The object mapping described in this document does not provide any other security services or introduce any additional considerations beyond those described by [RFC4930] and protocol layers used by EPP.
本文档中描述的对象映射不提供任何其他安全服务，也不引入任何超出[RFC4930]和EPP使用的协议层所描述的其他注意事项。
This document was originally written as an individual submission Internet-Draft. The PROVREG working group later adopted it as a working group document and provided many invaluable comments and suggested improvements. The author wishes to acknowledge the efforts of WG chairs Edward Lewis and Jaap Akkerhuis for their process and editorial contributions.
本文件最初是作为个人提交的互联网草案编写的。PROVREG工作组后来将其作为工作组文件通过，并提出了许多宝贵的意见和改进建议。作者希望感谢工作组主席Edward Lewis和Jaap Akkerhuis的工作过程和编辑贡献。
Specific suggestions that have been incorporated into this document were provided by Chris Bason, Eric Brunner-Williams, Jordyn Buchanan, Robert Burbidge, Dave Crocker, Ayesha Damaraju, Anthony Eden, Sheer El-Showk, Dipankar Ghosh, Klaus Malorny, Dan Manley, Michael Mealling, Patrick Mevzek, Asbjorn Steira, and Rick Wesson.
已纳入本文件的具体建议由克里斯·巴森、埃里克·布伦纳·威廉姆斯、乔丹·布坎南、罗伯特·伯比奇、戴夫·克罗克、阿伊莎·达马拉朱、安东尼·伊登、希尔·艾尔·肖克、迪潘卡尔·戈什、克劳斯·马洛尼、丹·曼利、迈克尔·米林、帕特里克·梅夫泽克、阿斯比约恩·施泰拉和里克·韦森提供。
[ISO.3166.1997] International Organization for Standardization, "Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes", ISO Standard 3166, October 1997.
[ISO.3166.1997]国际标准化组织，“国家及其分支机构名称表示代码——第1部分：国家代码”，ISO标准3166，1997年10月。
[ITU.E164.2005] International Telecommunication Union, "The international public telecommunication numbering plan", ITU-T Recommendation E.164, February 2005.
[ITU.E164.2005]国际电信联盟，“国际公共电信编号计划”，ITU-T建议E.164，2005年2月。
[RFC0822] Crocker, D., "Standard for the format of ARPA Internet text messages", STD 11, RFC 822, August 1982.
[RFC0822]Crocker，D.，“ARPA互联网文本信息格式标准”，STD 11，RFC 822，1982年8月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[RFC3629]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，2003年11月。
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[RFC3688]Mealling，M.“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[RFC4930] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", RFC 4930, May 2007.
[RFC4930]Hollenbeck，S.，“可扩展资源调配协议（EPP）”，RFC 4930，2007年5月。
[W3C.REC-xml-20040204] Yergeau, F., Maler, E., Sperberg-McQueen, C., Bray, T., and J. Paoli, "Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium FirstEdition REC-xml-20040204, February 2004, <http://www.w3.org/TR/2004/REC-xml-20040204>.
[W3C.REC-xml-20040204]Yergeau，F.，Maler，E.，Sperberg McQueen，C.，Bray，T.，和J.Paoli，“可扩展标记语言（xml）1.0（第三版）”，万维网联盟第一版REC-xml-20040204，2004年2月<http://www.w3.org/TR/2004/REC-xml-20040204>.
[W3C.REC-xmlschema-1-20041028] Thompson, H., Maloney, M., Mendelsohn, N., and D. Beech, "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.，Maloney，M.，Mendelsohn，N.，和D.Beech，“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, February 2000.
[RFC2781]Hoffman，P.和F.Yergeau，“UTF-16，ISO 10646编码”，RFC 2781，2000年2月。
[RFC3733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Contact Mapping", RFC 3733, March 2004.
[RFC3733]Hollenbeck，S.，“可扩展资源调配协议（EPP）联系人映射”，RFC 37332004年3月。
1. Minor reformatting as a result of converting I-D source format from nroff to XML.
1. 由于将I-D源格式从nroff转换为XML，因此需要进行较小的重新格式化。
2. Removed this text from Section 2.2:
2. 从第2.2节中删除此文本：
"With one exception, transform commands MUST be rejected when a pendingCreate, pendingDelete, pendingTransfer, or pendingUpdate status is set. The only exception is that a <transfer> command to approve, reject, or cancel a transfer MAY be processed while an object is in "pendingTransfer" status."
只有一个例外，当设置pendingCreate、pendingDelete、pendingTransfer或pendingUpdate状态时，必须拒绝转换命令。唯一的例外是，当对象处于“pendingTransfer”状态时，可以处理批准、拒绝或取消传输的<transfer>命令
3. Fixed examples in Section 2.9 (added missing "/" characters).
3. 修复了第2.9节中的示例（添加了缺少的“/”字符）。
4. Changed text in Section 3.1.3 from "A <contact:acID> element that contains the identifier of the client that SHOULD act upon the transfer request" to "A <contact:acID> element that contains the identifier of the client that SHOULD act upon a PENDING transfer request. For all other status types, the value identifies the client that took the indicated action".
4. 将第3.1.3节中的文本从“包含应根据转移请求采取行动的客户标识符的<contact:acID>元素”更改为“一个<contact:acID>元素，包含应根据挂起的传输请求进行操作的客户端的标识符。对于所有其他状态类型，该值标识执行指定操作的客户端”。
5. Fixed the example response in Section 3.2.4 to use the correct response code and response text.
5. 修复了第3.2.4节中的示例响应，以使用正确的响应代码和响应文本。
6. Changed text in Section 3.2.5 from "At least one <contact:add>, <contact:rem>, or <contact:chg> element MUST be provided." to "At least one <contact:add>, <contact:rem>, or <contact: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."
6. 将第3.2.5节中的文本从“必须提供至少一个<contact:add>、<contact:rem>或<contact:chg>元素”更改为“如果命令未扩展，则必须提供至少一个<contact:add>、<contact:rem>或<contact:chg>元素。如果存在<update>扩展，则可以省略所有这些元素。”
7. Changed text in Section 3.3 (old Section 3.2.6) from this:
7. 将第3.3节（旧的第3.2.6节）中的文本更改为：
"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."
服务器操作员脱机审查请求，并通过<poll>命令将服务消息排队以供检索，从而将审查结果通知客户端
to this:
为此：
"The server operator reviews the request offline, and informs the client of the outcome of the review either by queuing a service message for retrieval via the <poll> command or by using an out-of-band mechanism to inform the client of the request."
服务器操作员脱机审查请求，并通过将服务消息排队等待通过<poll>命令检索或使用带外机制通知客户端该请求，将审查结果通知客户端
8. Removed text describing use of the XML Schema schemaLocation attribute. This is an optional attribute that doesn't need to be mandated for use in EPP.
8. 已删除描述使用XML架构schemaLocation属性的文本。这是一个可选属性，不需要强制在EPP中使用。
9. Updated text describing a requirement to use UTF-8 encoding in the "Internationalization Considerations" section.
9. “国际化注意事项”部分中描述使用UTF-8编码要求的更新文本。
10. Removed references to RFC 3339 and replaced them with references to the W3C XML Schema specification.
10. 删除了对RFC 3339的引用，并将其替换为对W3C XML模式规范的引用。
11. Updated the E.164 reference.
11. 更新了E.164参考。
12. Updated EPP and XML references. Updated reference from RFC 2279 to RFC 3629.
12. 更新了EPP和XML引用。将参考资料从RFC 2279更新为RFC 3629。
Author's Address
作者地址
Scott Hollenbeck VeriSign, Inc. 21345 Ridgetop Circle Dulles, VA 20166-6503 US
Scott Hollenbeck VeriSign，Inc.美国弗吉尼亚州杜勒斯Ridgetop Circle 21345，邮编20166-6503
EMail: shollenbeck@verisign.com
EMail: shollenbeck@verisign.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。