Internet Engineering Task Force (IETF) J. Gould
Request for Comments: 8334 VeriSign, Inc.
Category: Standards Track W. Tan
ISSN: 2070-1721 Cloud Registry
G. Brown
CentralNic Ltd
March 2018
Internet Engineering Task Force (IETF) J. Gould
Request for Comments: 8334 VeriSign, Inc.
Category: Standards Track W. Tan
ISSN: 2070-1721 Cloud Registry
G. Brown
CentralNic Ltd
March 2018
Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
可扩展资源调配协议（EPP）的启动阶段映射
Abstract
摘要
This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of domain name registrations and applications during the launch of a domain name registry.
本文档描述了一个可扩展的资源调配协议（EPP）扩展映射，用于在启动域名注册期间对域名注册和应用程序进行资源调配和管理。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8334.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8334.
Copyright Notice
版权公告
Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2018 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(https://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Application Identifier . . . . . . . . . . . . . . . . . 4
2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5
2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 5
2.3.1. Trademark Claims Phase . . . . . . . . . . . . . . . 6
2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 9
2.4.1. State Transition . . . . . . . . . . . . . . . . . . 11
2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 12
2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 14
2.6.1. <launch:codeMark> Element . . . . . . . . . . . . . . 15
2.6.2. <mark:mark> Element . . . . . . . . . . . . . . . . . 16
2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 16
2.6.3.1. <smd:signedMark> Element . . . . . . . . . . . . 16
2.6.3.2. <smd:encodedSignedMark> Element . . . . . . . . . 16
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 17
3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 17
3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 17
3.1.2. Availability Check Form . . . . . . . . . . . . . . . 22
3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 23
3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 26
3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 30
3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 30
3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 36
3.3.3. General Create Form . . . . . . . . . . . . . . . . . 39
3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 40
3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 42
3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 43
3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 44
3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 46
3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 46
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 46
4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 46
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 54
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 55
6. Security Considerations . . . . . . . . . . . . . . . . . . . 55
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.1. Normative References . . . . . . . . . . . . . . . . . . 56
7.2. Informative References . . . . . . . . . . . . . . . . . 57
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 57
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Application Identifier . . . . . . . . . . . . . . . . . 4
2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5
2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 5
2.3.1. Trademark Claims Phase . . . . . . . . . . . . . . . 6
2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 9
2.4.1. State Transition . . . . . . . . . . . . . . . . . . 11
2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 12
2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 14
2.6.1. <launch:codeMark> Element . . . . . . . . . . . . . . 15
2.6.2. <mark:mark> Element . . . . . . . . . . . . . . . . . 16
2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 16
2.6.3.1. <smd:signedMark> Element . . . . . . . . . . . . 16
2.6.3.2. <smd:encodedSignedMark> Element . . . . . . . . . 16
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 17
3.1. EPP <check> Command . . . . . . . . . . . . . . . . . . . 17
3.1.1. Claims Check Form . . . . . . . . . . . . . . . . . . 17
3.1.2. Availability Check Form . . . . . . . . . . . . . . . 22
3.1.3. Trademark Check Form . . . . . . . . . . . . . . . . 23
3.2. EPP <info> Command . . . . . . . . . . . . . . . . . . . 26
3.3. EPP <create> Command . . . . . . . . . . . . . . . . . . 30
3.3.1. Sunrise Create Form . . . . . . . . . . . . . . . . . 30
3.3.2. Claims Create Form . . . . . . . . . . . . . . . . . 36
3.3.3. General Create Form . . . . . . . . . . . . . . . . . 39
3.3.4. Mixed Create Form . . . . . . . . . . . . . . . . . . 40
3.3.5. Create Response . . . . . . . . . . . . . . . . . . . 42
3.4. EPP <update> Command . . . . . . . . . . . . . . . . . . 43
3.5. EPP <delete> Command . . . . . . . . . . . . . . . . . . 44
3.6. EPP <renew> Command . . . . . . . . . . . . . . . . . . . 46
3.7. EPP <transfer> Command . . . . . . . . . . . . . . . . . 46
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 46
4.1. Launch Schema . . . . . . . . . . . . . . . . . . . . . . 46
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54
5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 54
5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 55
6. Security Considerations . . . . . . . . . . . . . . . . . . . 55
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.1. Normative References . . . . . . . . . . . . . . . . . . 56
7.2. Informative References . . . . . . . . . . . . . . . . . 57
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 57
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58
This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping specifies a flexible schema that can be used to implement several common use cases related to the provisioning and management of domain name registrations and applications during the launch of a domain name registry.
本文档描述了可扩展资源调配协议（EPP）[RFC5730]版本1.0的扩展映射。此EPP映射指定了一个灵活的模式，可用于在启动域名注册期间实现与域名注册和应用程序的供应和管理相关的几个常见用例。
It is typical for domain registries to operate in special modes as they begin operation to facilitate allocation of domain names, often according to special rules. This document uses the term "launch phase" and the shorter form "launch" to refer to such a period. Multiple launch phases and multiple models are supported to enable the launch of a domain name registry. Server policy determines what is supported and validated. Communication of the server policy is typically performed using an out-of-band mechanism that is not specified in this document.
通常情况下，域注册中心在开始运行以促进域名分配时会以特殊模式运行，通常是根据特殊规则。本文件使用术语“启动阶段”和较短形式的“启动”来指代这一时期。支持多个启动阶段和多个模型以启动域名注册中心。服务器策略确定支持和验证的内容。服务器策略的通信通常使用本文档中未指定的带外机制执行。
The EPP domain name mapping [RFC5731] is designed for the steady-state operation of a registry. During a launch period, the model in place may be different from what is defined in the EPP domain name mapping [RFC5731]. For example, registries often accept multiple applications for the same domain name during the "sunrise" launch phase, referred to as a Launch Application. A Launch Registration refers to a registration made during a launch phase when the server uses a "first-come, first-served" model. Even in a "first-come, first-served" model, additional steps and information might be required, such as trademark information. In addition, RFC 7848 [RFC7848] defines a registry interface for the Trademark Claims or "claims" launch phase that includes support for presenting a Trademark Claims Notice to the registrant. This document proposes an extension to the domain name mapping in order to provide a uniform interface for the management of Launch Applications and Launch Registrations in launch phases.
EPP域名映射[RFC5731]设计用于注册表的稳态操作。在启动期间，现有模型可能不同于EPP域名映射[RFC5731]中定义的模型。例如，注册中心通常在“sunrise”启动阶段（称为启动应用程序）接受同一域名的多个应用程序。启动注册是指在服务器使用“先到先得”模式的启动阶段进行的注册。即使在“先到先得”的模式中，也可能需要额外的步骤和信息，例如商标信息。此外，RFC 7848[RFC7848]定义了商标声明或“声明”启动阶段的注册接口，包括向注册人提交商标声明通知的支持。本文件建议对域名映射进行扩展，以便为发射阶段的发射应用程序和发射注册管理提供统一接口。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”在所有大写字母出现时（如图所示）应按照BCP 14[RFC2119][RFC8174]所述进行解释。
XML [W3C.REC-xml11-20060816] is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation.
XML[W3C.REC-xml11-20060816]区分大小写。除非另有说明，否则本文档中提供的XML规范和示例必须以所提供的字符大小写进行解释，以便开发一致的实现。
In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and whitespace in examples are provided only to illustrate element relationships and are not a REQUIRED feature of this protocol. The use of "..." is used as shorthand for elements defined outside this document.
在示例中，“C:”表示协议客户端发送的行，“S:”表示协议服务器返回的行。示例中的缩进和空格仅用于说明元素关系，不是本协议的必需功能。使用“…”作为本文件以外定义元素的简写。
A Launch Registration is a domain name registration during a launch phase when the server uses a "first-come, first-served" model. Only a single registration for a domain name can exist in the server at a time.
启动注册是在服务器使用“先到先得”模式的启动阶段进行的域名注册。一次只能在服务器中注册一个域名。
A Launch Application represents the intent to register a domain name during a launch phase when the server accepts multiple applications for a domain name, and the server later selects one of the applications to allocate as a registration. Many Launch Applications for a domain name can exist in the server at a time.
启动应用程序表示在启动阶段注册域名的意图，此时服务器接受多个域名应用程序，并且服务器稍后选择其中一个应用程序作为注册进行分配。一个域名的许多启动应用程序可以同时存在于服务器中。
The XML namespace prefix "launch" is used for the namespace "urn:ietf:params:xml:ns:launch-1.0", but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.
XML名称空间前缀“launch”用于名称空间“urn:ietf:params:XML:ns:launch-1.0”，但实现不能依赖于它，而是使用适当的名称空间感知XML解析器和序列化程序来解释和输出XML文档。
The XML namespace prefix "smd" is used for the namespace "urn:ietf:params:xml:ns:signedMark-1.0" [RFC7848], but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.
XML名称空间前缀“smd”用于名称空间“urn:ietf:params:XML:ns:signedMark-1.0”[RFC7848]，但实现不能依赖于它，而是使用适当的名称空间感知XML解析器和序列化程序来解释和输出XML文档。
The XML namespace prefix "mark" is used for the namespace "urn:ietf:params:xml:ns:mark-1.0" [RFC7848], but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents.
XML名称空间前缀“mark”用于名称空间“urn:ietf:params:XML:ns:mark-1.0”[RFC7848]，但实现不能依赖于它，而是使用适当的名称空间感知XML解析器和序列化程序来解释和输出XML文档。
This extension adds additional elements to the EPP domain name mapping [RFC5731]. Only those new elements are described here.
此扩展将向EPP域名映射[RFC5731]添加其他元素。这里只描述这些新元素。
Servers MAY allow multiple applications, referred to as a Launch Application, of the same domain name during its launch phase operations. Upon receiving a valid <domain:create> command to create a Launch Application, the server MUST create an application object corresponding to the request, assign an application identifier for the Launch Application, set the pendingCreate status [RFC5731], and return the application identifier to the client with the
服务器可能允许在其启动阶段操作期间使用同一域名的多个应用程序（称为启动应用程序）。在接收到创建启动应用程序的有效<domain:create>命令后，服务器必须创建与请求相对应的应用程序对象，为启动应用程序分配应用程序标识符，设置pendingCreate状态[RFC5731]，并将应用程序标识符返回给具有
<launch:applicationID> element. In order to facilitate correlation, all subsequent launch operations on the Launch Application MUST be qualified by the previously assigned application identifier using the <launch:applicationID> element.
<launch:applicationID>元素。为了便于关联，必须使用<launch:applicationID>元素通过先前分配的应用程序标识符对启动应用程序上的所有后续启动操作进行限定。
The Validator Identifier is unique to the server and is the identifier for a Trademark Validator, which validates marks and has a repository of validated marks. The OPTIONAL "validatorID" attribute is used to define the Validator Identifier of the Trademark Validator. Registries MAY support more than one third-party Trademark Validator. The unique set of Validator Identifier values supported by the server is up to server policy. The Internet Corporation for Assigned Names and Numbers (ICANN) Trademark Clearinghouse (TMCH) is the default Trademark Validator and is reserved for the Validator Identifier of "tmch". If the ICANN TMCH is not used or multiple Trademark Validators are used, the Validator Identifier MUST be defined using the "validatorID" attribute.
验证器标识符对于服务器是唯一的，并且是商标验证器的标识符，商标验证器用于验证标记，并具有已验证标记的存储库。可选的“validatorID”属性用于定义商标验证程序的验证程序标识符。注册中心可以支持多个第三方商标验证器。服务器支持的唯一验证程序标识符值集取决于服务器策略。互联网名称和数字分配公司（ICANN）商标交换所（TMCH）是默认的商标验证机构，保留给“TMCH”的验证机构标识符。如果未使用ICANN TMCH或使用多个商标验证器，则必须使用“validatorID”属性定义验证器标识符。
The Validator Identifier MAY be related to one or more issuer identifiers of the <mark:id> and <smd:id> elements defined in [RFC7848]. Both the Validator Identifier and the Issuer Identifier used MUST be unique in the server. If the ICANN TMCH is not used or multiple Trademark Validators are used, the server MUST define the list of supported validator identifiers and MUST make this information available to clients using a mutually acceptable, out-of-band mechanism.
验证器标识符可能与[RFC7848]中定义的<mark:id>和<smd:id>元素的一个或多个发行者标识符相关。所使用的验证程序标识符和颁发者标识符在服务器中必须是唯一的。如果未使用ICANN TMCH或使用了多个商标验证器，服务器必须定义支持的验证器标识符列表，并且必须使用相互接受的带外机制将此信息提供给客户端。
The Validator Identifier may define a non-Trademark Validator that supports a form of claims, where claims and a Validator Identifier can be used for purposes beyond trademarks.
验证器标识符可定义支持权利要求形式的非商标验证器，其中权利要求和验证器标识符可用于商标以外的目的。
The server MAY support multiple launch phases sequentially or simultaneously. The <launch:phase> element MUST be included by the client to define the target launch phase of the command. The server SHOULD validate the phase and MAY validate the sub-phase of the <launch:phase> element against the active phase and OPTIONAL sub-phase of the server, and return an EPP error result code of 2306 [RFC5730] if there is a mismatch.
服务器可以支持顺序或同时的多个启动阶段。客户端必须包含<launch:phase>元素，以定义命令的目标启动阶段。服务器应验证阶段，并可根据服务器的活动阶段和可选子阶段验证<launch:phase>元素的子阶段，如果不匹配，则返回2306[RFC5730]的EPP错误结果代码。
The following launch phase values are defined:
定义了以下启动阶段值：
sunrise: The phase during which trademark holders can submit registrations or applications with trademark information that can be validated by the server.
sunrise：商标持有人可以提交注册或申请的阶段，该阶段的商标信息可由服务器验证。
landrush: A post-"sunrise" launch phase when non-trademark holders are allowed to register domain names with steps taken to address a large volume of initial registrations.
landrush：后“日出”启动阶段，允许非商标持有人注册域名，并采取措施解决大量初始注册问题。
claims: The phase, as defined in Section 2.3.1, in which a claims notice must be displayed to a prospective registrant of a domain name that matches trademarks.
索赔：第2.3.1节定义的阶段，在此阶段，必须向与商标匹配的域名的潜在注册人显示索赔通知。
open: A phase that is also referred to as "steady state". Servers may require additional trademark protection during this phase.
打开：也称为“稳态”的阶段。在此阶段，服务器可能需要额外的商标保护。
custom: A custom server launch phase that is defined using the "name" attribute.
自定义：使用“name”属性定义的自定义服务器启动阶段。
For extensibility, the <launch:phase> element includes an OPTIONAL "name" attribute that can define a sub-phase or the full name of the phase when the <launch:phase> element has the "custom" value. For example, the "claims" launch phase could have two sub-phases that include "landrush" and "open".
为了扩展性，<launch:phase>元素包含一个可选的“name”属性，当<launch:phase>元素具有“custom”值时，该属性可以定义子阶段或阶段的全名。例如，“索赔”发射阶段可以有两个子阶段，包括“landrush”和“open”。
Launch phases MAY overlap to support the "claims" launch phase, defined in Section 2.3.1, and to support a traditional "landrush" launch phase. The overlap of the "claims" and "landrush" launch phases SHOULD be handled by setting "claims" as the <launch:phase> value and setting "landrush" as the sub-phase with the "name" attribute. For example, the <launch:phase> element should be <launch:phase name="landrush">claims</launch:phase>.
发射阶段可能重叠，以支持第2.3.1节中定义的“索赔”发射阶段，并支持传统的“landrush”发射阶段。应通过将“索赔”设置为<launch:phase>值并将“landrush”设置为具有“name”属性的子阶段来处理“索赔”和“landrush”启动阶段的重叠。例如，<launch:phase>元素应该是<launch:phase name=“landrush”>索赔</launch:phase>。
The Trademark Claims Phase is when a claims notice must be displayed to a prospective registrant of a domain name that matches trademarks. See [ICANN-TMCH] for additional details of trademark claims handling. The source of the trademarks is a Trademark Validator, and the source of the claims notice information is a Claims Notice Information Service (CNIS), which may be directly linked to a Trademark Validator. The client interfaces with 1) the server to determine if a trademark exists for a domain name, 2) a CNIS to get the claims notice information, and 3) the server to pass the claims notice acceptance information in a create command. This document supports the Trademark Claims Phase in two ways, including:
商标声明阶段是必须向与商标匹配的域名的潜在注册人显示声明通知的阶段。请参见[ICANN-TMCH]了解商标索赔处理的更多详细信息。商标的来源是商标验证器，索赔通知信息的来源是索赔通知信息服务（CNIS），该服务可以直接链接到商标验证器。客户端与1）服务器交互以确定域名是否存在商标，2）CNIS获取索赔通知信息，以及3）服务器通过create命令传递索赔通知接受信息。本文件以两种方式支持商标声明阶段，包括：
Claims Check Form: Is defined in Section 3.1.1 and is used to determine whether or not there are any matching trademarks for a domain name. If there is at least one matching trademark that exists for the domain name, a claims key is returned. The mapping of domain names and the claims keys is based on an out-of-band interface between the server and the Trademark Validator. The
索赔检查表：在第3.1.1节中定义，用于确定域名是否有任何匹配的商标。如果域名至少存在一个匹配的商标，则返回声明密钥。域名和声明密钥的映射基于服务器和商标验证程序之间的带外接口。这个
CNIS associated with the claims key Validator Identifier (Section 2.2) MUST accept the claims key as the basis for retrieving the claims information.
与索赔密钥验证器标识符（第2.2节）关联的CNI必须接受索赔密钥作为检索索赔信息的基础。
Claims Create Form: Is defined in Section 3.3.2 and is used to pass the claims notice acceptance information in a create command. The notice identifier (<launch:noticeID>) format, validation rules, and server processing is up to the interface between the server and the Trademark Validator. The CNIS associated with the Validator Identifier (Section 2.2) MUST generate a notice identifier compliant with the <launch:noticeID> element.
索赔创建表单：在第3.3.2节中定义，用于在Create命令中传递索赔通知受理信息。通知标识符（<launch:noticeID>）格式、验证规则和服务器处理取决于服务器和商标验证程序之间的接口。与验证器标识符（第2.2节）关联的CNI必须生成符合<launch:noticeID>元素的通知标识符。
The following shows the Trademark Claims Phase registration flow:
以下显示了商标声明阶段的注册流程：
.------------. .--------. .--------. .------.
| Registrant | | Client | | Server | | CNIS |
'------------' '--------' '--------' '------'
| Request Domain | | |
| Registration | | |
|--------------->| Domain Check | |
| |--------------------------->| |
| Domain | Domain Unavailable .------------. |
| Unavailable |<---------------------( Available? ) |
|<---------------| No '------------' |
| | Domain Available | Yes |
| |<---------------------------| |
| | Domain Claims Check | |
| |--------------------------->| |
| | .---------. |
| | Claims Don't Exist / Does \ |
| |<--------------------( Domain have ) |
| | No \ Claims? / |
| | '---------' |
| | Domain Create | | Yes |
| |--------------------------->| | |
| Domain | Domain Registered | | |
| Registered |<---------------------------| | |
|<---------------| | |
| | |
| | Claims Exist with Claims Keys | |
| |<------------------------------' |
| | |
.-----. | | Request Claims Info with Claims Key |
|Abort| | Display |-------------------------------------->|
'-----' | Claims | Return Claims Info |
^ | Notice |<--------------------------------------|
| No |<---------------| |
| .------. Yes | |
'-( Ack? )----------->| Domain Claims Create Form | |
'------' |--------------------------->| |
| Registration | Error .----------------------. |
| Error |<-----------( Validation Successful? ) |
|<---------------| No '----------------------' |
| | | Yes |
| Domain | Domain Registered | |
| Registered |<---------------------------| |
|<---------------| | |
.------------. .--------. .--------. .------.
| Registrant | | Client | | Server | | CNIS |
'------------' '--------' '--------' '------'
| Request Domain | | |
| Registration | | |
|--------------->| Domain Check | |
| |--------------------------->| |
| Domain | Domain Unavailable .------------. |
| Unavailable |<---------------------( Available? ) |
|<---------------| No '------------' |
| | Domain Available | Yes |
| |<---------------------------| |
| | Domain Claims Check | |
| |--------------------------->| |
| | .---------. |
| | Claims Don't Exist / Does \ |
| |<--------------------( Domain have ) |
| | No \ Claims? / |
| | '---------' |
| | Domain Create | | Yes |
| |--------------------------->| | |
| Domain | Domain Registered | | |
| Registered |<---------------------------| | |
|<---------------| | |
| | |
| | Claims Exist with Claims Keys | |
| |<------------------------------' |
| | |
.-----. | | Request Claims Info with Claims Key |
|Abort| | Display |-------------------------------------->|
'-----' | Claims | Return Claims Info |
^ | Notice |<--------------------------------------|
| No |<---------------| |
| .------. Yes | |
'-( Ack? )----------->| Domain Claims Create Form | |
'------' |--------------------------->| |
| Registration | Error .----------------------. |
| Error |<-----------( Validation Successful? ) |
|<---------------| No '----------------------' |
| | | Yes |
| Domain | Domain Registered | |
| Registered |<---------------------------| |
|<---------------| | |
Figure 1
图1
A Launch Application or Launch Registration object MAY have a launch status value. The <launch:status> element is used to convey the launch status pertaining to the object, beyond what is specified in the object mapping. A Launch Application or Launch Registration MUST set the "pendingCreate" status [RFC5731] if a launch status is supported and is not one of the final statuses ("allocated" and "rejected").
启动应用程序或启动注册对象可能具有启动状态值。<launch:status>元素用于传递对象的启动状态，超出对象映射中指定的范围。如果启动状态受支持且不是最终状态（“已分配”和“已拒绝”），则启动应用程序或启动注册必须设置“pendingCreate”状态[RFC5731]。
The following status values are defined using the required "s" attribute:
使用所需的“s”属性定义以下状态值：
pendingValidation: The initial state of a newly created application or registration object. The application or registration requires validation, but the validation process has not yet completed.
pendingValidation：新创建的应用程序或注册对象的初始状态。申请或注册需要验证，但验证过程尚未完成。
validated: The application or registration meets relevant registry rules.
已验证：申请或注册符合相关注册规则。
invalid: The application or registration does not validate according to registry rules. Server policies permitting, it may transition back into "pendingValidation" for revalidation, after modifications are made to ostensibly correct attributes that caused the validation failure.
无效：应用程序或注册未根据注册表规则进行验证。在服务器策略允许的情况下，在修改导致验证失败的表面上正确的属性后，它可能会转换回“pendingValidation”进行重新验证。
pendingAllocation: The allocation of the application or registration is pending based on the results of some out-of-band process (for example, an auction).
pendingAllocation：根据某些带外过程（例如拍卖）的结果，申请或注册的分配处于挂起状态。
allocated: The object corresponding to the application or registration has been provisioned. This is a possible end state of an application or registration object.
已分配：已设置与应用程序或注册对应的对象。这是应用程序或注册对象的可能结束状态。
rejected: The application or registration object was not provisioned. This is a possible end state of an application or registration object.
拒绝：未设置应用程序或注册对象。这是应用程序或注册对象的可能结束状态。
custom: A custom status that is defined using the "name" attribute.
自定义：使用“名称”属性定义的自定义状态。
Each status value MAY be accompanied by a string of human-readable text that describes the rationale for the status applied to the object. The OPTIONAL "lang" attribute, as defined in [RFC5646], MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English).
每个状态值可能伴随着一个人类可读文本字符串，该字符串描述了应用于对象的状态的基本原理。[RFC5646]中定义的可选“lang”属性可用于在协商值不是默认值“en”（英语）的情况下识别语言。
For extensibility, the <launch:status> element includes an OPTIONAL "name" attribute that can define a sub-status or the full name of the status when the status value is "custom". The server SHOULD use one of the non-"custom" status values.
为了扩展性，<launch:status>元素包含一个可选的“name”属性，当status值为“custom”时，该属性可以定义状态的子状态或全名。服务器应使用非“自定义”状态值之一。
Status values MAY be skipped. For example, an application or registration MAY immediately start at the "allocated" status, or an application or registration MAY skip the "pendingAllocation" status. If the launch phase does not require validation of a request, an application or registration MAY immediately skip to "pendingAllocation".
可以跳过状态值。例如，申请或注册可能会立即以“已分配”状态开始，或者申请或注册可能会跳过“待分配”状态。如果启动阶段不需要验证请求，则应用程序或注册可以立即跳到“pendingAllocation”。
The transitions between the states is a matter of server policy. This diagram defines one possible set of permitted transitions.
状态之间的转换取决于服务器策略。此图定义了一组可能的允许转换。
| request
|
| +--------------------------+
| | |
v v |
+-------------------+ |
| | |
| pendingValidation +--------------+ |
| | | |
+---------+---------+ | |
| | |
| | |
v v |
+-----------+ +---------+ |
| | | | |
| validated | | invalid +--+
| | | |
+-----+-----+ +----+----+
| |
| |
v |
+-------------------+ |
| | |
| pendingAllocation +-----------+ |
| | | |
+---------+---------+ | |
| | |
| | |
| | |
| | |
| | |
v v v
+---------+ +--------+
/ \ / \
| allocated | | rejected |
\ / \ /
+---------+ +--------+
| request
|
| +--------------------------+
| | |
v v |
+-------------------+ |
| | |
| pendingValidation +--------------+ |
| | | |
+---------+---------+ | |
| | |
| | |
v v |
+-----------+ +---------+ |
| | | | |
| validated | | invalid +--+
| | | |
+-----+-----+ +----+----+
| |
| |
v |
+-------------------+ |
| | |
| pendingAllocation +-----------+ |
| | | |
+---------+---------+ | |
| | |
| | |
| | |
| | |
| | |
v v v
+---------+ +--------+
/ \ / \
| allocated | | rejected |
\ / \ /
+---------+ +--------+
Figure 2
图2
A Launch Application MUST be handled as an EPP domain name object as specified in RFC 5731 [RFC5731], with the "pendingCreate" status and launch status values defined in Section 2.4. A Launch Registration MAY be handled as an EPP domain name object as specified in RFC 5731 [RFC5731], with the "pendingCreate" status and launch status values defined in Section 2.4. As a Launch Application or Launch Registration transitions between the status values defined in Section 2.4, the server SHOULD insert poll messages, per [RFC5730], for the applicable intermediate statuses, including the "pendingValidation", "validated", "pendingAllocation", and "invalid" statuses, using the <domain:infData> element with the <launch:infData> extension. The <domain:infData> element MAY contain non-mandatory information, like contact and name server information. Also, further extensions that would normally be included in the response of a <domain:info> command, per [RFC5731], MAY be included. For the final statuses, including the "allocated" and "rejected" statuses, the server MUST insert a <domain:panData> poll message, per [RFC5731], with the <launch:infData> extension.
必须按照RFC 5731[RFC5731]中的规定，将启动应用程序作为EPP域名对象处理，并在第2.4节中定义“pendingCreate”状态和启动状态值。按照RFC 5731[RFC5731]中的规定，启动注册可以作为EPP域名对象处理，其“pendingCreate”状态和启动状态值在第2.4节中定义。当启动应用程序或启动注册在第2.4节中定义的状态值之间转换时，服务器应根据[RFC5730]插入适用中间状态的轮询消息，包括“pendingValidation”、“validated”、“pendingAllocation”和“invalid”状态，使用<domain:infData>元素和<launch:infData>扩展名。<domain:infData>元素可能包含非强制性信息，如联系人和姓名服务器信息。此外，根据[RFC5731]，通常包括在<domain:info>命令响应中的进一步扩展也可以包括在内。对于最终状态，包括“已分配”和“已拒绝”状态，服务器必须按照[RFC5731]插入一条<domain:panData>轮询消息，扩展名为<launch:infData>。
The following is an example poll message for a Launch Application that has transitioned to the "pendingAllocation" state.
以下是已转换为“pendingAllocation”状态的启动应用程序的轮询消息示例。
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>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Application pendingAllocation.</msg>
S: </msgQ>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>domain.example</domain:name>
S: ...
S: </domain:infData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="pendingAllocation"/>
S: </launch:infData>
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>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Application pendingAllocation.</msg>
S: </msgQ>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>domain.example</domain:name>
S: ...
S: </domain:infData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="pendingAllocation"/>
S: </launch:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
The following is an example <domain:panData> poll message for an "allocated" Launch Application.
下面是“已分配”启动应用程序的轮询消息示例。
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>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Application successfully allocated.</msg>
S: </msgQ>
S: <resData>
S: <domain:panData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name paResult="1">domain.example</domain:name>
S: <domain:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="allocated"/>
S: </launch:infData>
S: </extension>
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>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Application successfully allocated.</msg>
S: </msgQ>
S: <resData>
S: <domain:panData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name paResult="1">domain.example</domain:name>
S: <domain:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="allocated"/>
S: </launch:infData>
S: </extension>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID>
S: </trID>
S: </response>
S:</epp>
The following is an example <domain:panData> poll message for an "allocated" Launch Registration.
下面是“已分配”启动注册的<domain:panData>轮询消息示例。
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>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Registration successfully allocated.</msg>
S: </msgQ>
S: <resData>
S: <domain:panData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name paResult="1">domain.example</domain:name>
S: <domain:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:status s="allocated"/>
S: </launch:infData>
S: </extension>
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>2013-04-04T22:01:00.0Z</qDate>
S: <msg>Registration successfully allocated.</msg>
S: </msgQ>
S: <resData>
S: <domain:panData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name paResult="1">domain.example</domain:name>
S: <domain:paTRID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </domain:paTRID>
S: <domain:paDate>2013-04-04T22:00:00.0Z</domain:paDate>
S: </domain:panData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:status s="allocated"/>
S: </launch:infData>
S: </extension>
S: <trID>
S: <clTRID>BCD-23456</clTRID>
S: <svTRID>65432-WXY</svTRID>
S: </trID>
S: </response>
S:</epp>
A server MUST support at least one of the following models for validating trademark information:
服务器必须至少支持以下一种型号以验证商标信息：
code: Use of a mark code by itself to validate that the mark matches the domain name. This model is supported using the <launch:codeMark> element with just the <launch:code> element.
代码：单独使用标记代码来验证标记是否与域名匹配。仅使用<launch:code>元素和<launch:code>元素支持此模型。
mark: The mark information is passed without any other validation element. The server will use some custom form of validation to validate that the mark information is authentic. This model is supported using the <launch:codeMark> element with just the <mark:mark> (Section 2.6.2) element.
标记：标记信息在没有任何其他验证元素的情况下传递。服务器将使用某种自定义形式的验证来验证标记信息是否真实。使用<launch:codeMark>元素和<mark:mark>（第2.6.2节）元素支持此模型。
code with mark: A code is used along with the mark information by the server to validate the mark utilizing an external party. The code represents some form of secret that matches the mark information passed. This model is supported using the <launch:codeMark> element that contains both the <launch:code> and the <mark:mark> (Section 2.6.2) elements.
带有标记的代码：服务器将代码与标记信息一起使用，以使用外部方验证标记。该代码表示与传递的标记信息相匹配的某种形式的秘密。使用包含<launch:code>和<mark:mark>（第2.6.2节）元素的<launch:code>元素支持此模型。
signed mark: The mark information is digitally signed as described in the Digital Signature section (Section 2.6.3). The digital signature can be directly validated by the server using the public key of the external party that created the signed mark using its private key. This model is supported using the <smd:signedMark> (Section 2.6.3.1) and <smd:encodedSignedMark> (Section 2.6.3.2) elements.
签名标记：按照数字签名部分（第2.6.3节）中的说明对标记信息进行数字签名。服务器可以使用使用私钥创建签名标记的外部方的公钥直接验证数字签名。使用<smd:signedMark>（第2.6.3.1节）和<smd:encodedSignedMark>（第2.6.3.2节）元素支持此模型。
More than one <launch:codeMark>, <smd:signedMark> (Section 2.6.3.1), or <smd:encodedSignedMark> (Section 2.6.3.2) element MAY be specified. The maximum number of marks per domain name is up to server policy.
可以指定多个<launch:codeMark>、<smd:signedMark>（第2.6.3.1节）或<smd:encodedSignedMark>（第2.6.3.2节）元素。每个域名的最大标记数取决于服务器策略。
The <launch:codeMark> element is used by the "code", "mark", and "code with mark" validation models and has the following child elements:
<launch:codeMark>元素由“code”、“mark”和“code with mark”验证模型使用，并具有以下子元素：
<launch:code>: OPTIONAL mark code used to validate the <mark:mark> (Section 2.6.2) information. The mark code is a mark-specific secret that the server can verify against a third party. The OPTIONAL "validatorID" attribute is the Validator Identifier (Section 2.2) whose value indicates which Trademark Validator the code originated from, with no default value.
<launch:code>：用于验证<mark:mark>（第2.6.2节）信息的可选标记代码。标记代码是特定于标记的机密，服务器可以针对第三方进行验证。可选的“validatorID”属性是验证器标识符（第2.2节），其值指示代码来自哪个商标验证器，没有默认值。
<mark:mark>: OPTIONAL mark information with child elements defined in the Mark section (Section 2.6.2).
<mark:mark>：可选的标记信息，带有标记部分（第2.6.2节）中定义的子元素。
The following is an example <launch:codeMark> element with both a <launch:code> and <mark:mark> (Section 2.6.2) element.
下面是一个包含<launch:code>和<mark:mark>（第2.6.2节）元素的<launch:codeMark>元素示例。
<launch:codeMark>
<launch:code validatorID="sample">
49FD46E6C4B45C55D4AC</launch:code>
<mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
...
</mark:mark>
</launch:codeMark>
<launch:codeMark>
<launch:code validatorID="sample">
49FD46E6C4B45C55D4AC</launch:code>
<mark:mark xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
...
</mark:mark>
</launch:codeMark>
A <mark:mark> element describes an applicant's prior right to a given domain name that is used with the "mark", "mark with code", and "signed mark" validation models. The <mark:mark> element is defined in [RFC7848]. A new mark format can be supported by creating a new XML schema for the mark that has an element that substitutes for the <mark:abstractMark> element from [RFC7848].
<mark:mark>元素描述了申请人对与“mark”、“mark with code”和“signed mark”验证模型一起使用的给定域名的优先权。<mark:mark>元素在[RFC7848]中定义。通过为标记创建一个新的XML模式，可以支持新的标记格式，该标记具有一个替换[RFC7848]中<mark:abstractMark>元素的元素。
Digital signatures MAY be used by the server to validate the mark information, when using the "signed mark" validation model with the <smd:signedMark> (Section 2.6.3.1) and <smd:encodedSignedMark> (Section 2.6.3.2) elements. When using digital signatures, the server MUST validate the digital signature.
当使用带有<smd:signedMark>（第2.6.3.1节）和<smd:encodedSignedMark>（第2.6.3.2节）元素的“签名标记”验证模型时，服务器可使用数字签名验证标记信息。使用数字签名时，服务器必须验证数字签名。
The <smd:signedMark> element contains the digitally signed mark information. The <smd:signedMark> element is defined in [RFC7848]. A new signed mark format can be supported by creating a new XML schema for the signed mark that has an element that substitutes for the <smd:abstractSignedMark> element from [RFC7848].
<smd:signedMark>元素包含数字签名的标记信息。[RFC7848]中定义了<smd:signedMark>元素。可以通过为签名标记创建新的XML模式来支持新的签名标记格式，该模式具有一个元素，该元素替代[RFC7848]中的<smd:abstractSignedMark>元素。
The <smd:encodedSignedMark> element contains an encoded form of the digitally signed <smd:signedMark> (Section 2.6.3.1) element. The <smd:encodedSignedMark> element is defined in [RFC7848]. A new encoded signed mark format can be supported by creating a new XML schema for the encoded signed mark that has an element that substitutes for the <smd:encodedSignedMark> element from [RFC7848].
<smd:encodedSignedMark>元素包含数字签名的<smd:signedMark>（第2.6.3.1节）元素的编码形式。[RFC7848]中定义了<smd:encodedSignedMark>元素。通过为编码的有符号标记创建一个新的XML模式，可以支持新的编码的有符号标记格式，该模式具有一个替换[RFC7848]中<smd:encodedSignedMark>元素的元素。
A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in the Launch Phase Extension.
EPP语法和语义的详细描述可在EPP核心协议规范[RFC5730]中找到。这里描述的命令映射专门用于启动阶段扩展。
This mapping is designed to be flexible, requiring only a minimum set of required elements.
此映射设计为灵活的，只需要最少的一组必需元素。
While it is meant to serve several use cases, it does not prescribe any interpretation by the client or server. Such processing is typically highly policy dependent and therefore specific to implementations.
虽然它旨在服务于多个用例，但它没有规定客户机或服务器的任何解释。这种处理通常高度依赖于策略，因此特定于实现。
Operations on application objects are done via one or more of the existing EPP commands defined in the EPP domain name mapping [RFC5731]. Registries MAY choose to support a subset of the operations.
对应用程序对象的操作通过EPP域名映射[RFC5731]中定义的一个或多个现有EPP命令完成。注册中心可以选择支持操作的子集。
There are three forms of the extension to the EPP <check> command: the Claims Check Form (Section 3.1.1), the Availability Check Form (Section 3.1.2), and the Trademark Check Form (Section 3.1.3). The <launch:check> element "type" attribute defines the form, with the value of "claims" for the Claims Check Form (Section 3.1.1), "avail" for the Availability Check Form (Section 3.1.2), and "trademark" for the Trademark Check Form (Section 3.1.3). The default value of the "type" attribute is "claims". The forms supported by the server is determined by server policy. The server MUST return an EPP error result code of 2307 [RFC5730] if it receives a check form that is not supported.
EPP<check>命令的扩展有三种形式：索赔检查表（第3.1.1节）、可用性检查表（第3.1.2节）和商标检查表（第3.1.3节）。<launch:check>元素的“type”属性定义了表单，对于索赔检查表单（第3.1.1节），“avail”用于可用性检查表单（第3.1.2节），而“商标”用于商标检查表单（第3.1.3节）。“type”属性的默认值是“claims”。服务器支持的表单由服务器策略决定。如果服务器收到不支持的检查表单，则必须返回2307[RFC5730]的EPP错误结果代码。
The Claims Check Form defines a new command called the Claims Check Command that is used to determine whether or not there are any matching trademarks, in the specified launch phase, for each domain name passed in the command, that require the use of the "Claims Create Form" on a Domain Create Command. The availability check information defined in the EPP domain name mapping [RFC5731] MUST NOT be returned for the Claims Check Command. This form is the default form and MAY be explicitly identified by setting the <launch:check> "type" attribute to "claims".
Claims Check Form定义了一个名为Claims Check command的新命令，用于确定在指定的启动阶段，对于在命令中传递的每个域名，是否存在需要在域创建命令上使用“Claims Create Form”的任何匹配商标。不得为Claims check命令返回EPP域名映射[RFC5731]中定义的可用性检查信息。此表单是默认表单，可以通过将<launch:check>“type”属性设置为“claims”来明确标识。
Instead of returning whether the domain name is available, the Claims Check Command will return whether or not at least one matching trademark exists for the domain name, which requires the use of the "Claims Create Form" on a Domain Create Command. If there is at least one matching trademark that exists for the domain name, a <launch:claimKey> element is returned. The client MAY then use the value of the <launch:claimKey> element to obtain information needed to generate the Trademark Claims Notice from the Trademark Validator based on the Validator Identifier (Section 2.2). The unique notice identifier of the Trademark Claims Notice MUST be passed in the <launch:noticeID> element of the extension to the Create Command (Section 3.3).
Claims Check命令不会返回域名是否可用，而是返回域名是否至少存在一个匹配商标，这需要在域创建命令上使用“Claims Create Form”。如果域名至少存在一个匹配商标，则返回<launch:claimKey>元素。然后，客户可以使用<launch:claimKey>元素的值，根据验证器标识符从商标验证器获取生成商标声明通知所需的信息（第2.2节）。商标声明通知的唯一通知标识符必须在Create命令（第3.3节）扩展的<launch:noticeID>元素中传递。
The <domain:name> elements in the EPP <check> command of EPP domain name mapping [RFC5731] define the domain names to check for matching trademarks. The <launch:check> element contains the following child element:
EPP域名映射[RFC5731]的EPP<check>命令中的<domain:name>元素定义要检查匹配商标的域名。<launch:check>元素包含以下子元素：
<launch:phase>: Contains the value of the active launch phase of the server. The server SHOULD validate the value according to Section 2.3.
<launch:phase>：包含服务器的活动启动阶段的值。服务器应根据第2.3节验证该值。
The following is an example Claims Check Command using the <check> domain command and the <launch:check> extension with the "type" explicitly set to "claims", to determine if "domain1.example", "domain2.example", and "domain3.example" require claims notices during the "claims" launch phase:
下面是一个索赔检查命令示例，使用<Check>域命令和<launch:Check>扩展，将“type”显式设置为“Claims”，以确定“domain1.example”、“domain2.example”和“domain3.example”在“索赔”启动阶段是否需要索赔通知：
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: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain1.example</domain:name>
C: <domain:name>domain2.example</domain:name>
C: <domain:name>domain3.example</domain:name>
C: </domain:check>
C: </check>
C: <extension>
C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="claims">
C: <launch:phase>claims</launch:phase>
C: </launch:check>
C: </extension>
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: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain1.example</domain:name>
C: <domain:name>domain2.example</domain:name>
C: <domain:name>domain3.example</domain:name>
C: </domain:check>
C: </check>
C: <extension>
C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="claims">
C: <launch:phase>claims</launch:phase>
C: </launch:check>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
If the <check> command has been processed successfully, the EPP <response> MUST contain an <extension> <launch:chkData> element that identifies the launch namespace. The <launch:chkData> element contains the following child elements:
如果已成功处理<check>命令，则EPP<response>必须包含标识启动命名空间的<extension><launch:chkData>元素。<launch:chkData>元素包含以下子元素：
<launch:phase>: The phase that mirrors the <launch:phase> element included in the <launch:check>.
<launch:phase>：镜像<launch:check>中包含的<launch:phase>元素的阶段。
<launch:cd>: One or more <launch:cd> elements that contain the following child elements:
<launch:cd>：包含以下子元素的一个或多个<launch:cd>元素：
<launch:name>: Contains the fully qualified name of the queried domain name. This element MUST contain an "exists" attribute whose value indicates if a matching trademark exists for the domain name that requires the use of the "Claims Create Form" on a Domain Create Command. A value of "1" (or "true") means that a matching trademark does exist and that the "Claims Create Form" is required on a Domain Create Command. A value
<launch:name>：包含查询域名的完全限定名。此元素必须包含一个“exists”属性，该属性的值指示是否存在需要在域创建命令上使用“Claims Create Form”的域名的匹配商标。值“1”（或“true”）表示匹配商标确实存在，并且域创建命令上需要“声明创建表单”。价值
of "0" (or "false") means that a matching trademark does not exist or that the "Claims Create Form" is NOT required on a Domain Create Command.
“0”（或“false”）表示匹配商标不存在，或者域创建命令不需要“声明创建表单”。
<launch:claimKey>: Zero or more OPTIONAL claim keys that MAY be passed to a third-party Trademark Validator such as the ICANN TMCH for querying the information needed to generate a Trademark Claims Notice. The <launch:claimKey> is used as the key for the query in place of the domain name to securely query the service without using a well-known value like a domain name. The OPTIONAL "validatorID" attribute is the Validator Identifier (Section 2.2) whose value indicates which Trademark Validator to query for the claims notice information, with the default being the ICANN TMCH. The "validatorID" attribute MAY reference a non-trademark claims clearinghouse identifier to support other forms of claims notices.
<launch:claimKey>：零个或多个可选的索赔密钥，可传递给第三方商标验证器，如ICANN TMCH，用于查询生成商标索赔通知所需的信息。<launch:claimKey>被用作查询的密钥而不是域名，以安全地查询服务，而不使用像域名这样的已知值。可选的“validatorID”属性是验证器标识符（第2.2节），其值指示要查询索赔通知信息的商标验证器，默认值为ICANN TMCH。“validatorID”属性可以引用非商标索赔清算所标识符来支持其他形式的索赔通知。
The following is an example Claims Check response when a claims notice for the "claims" launch phase is not required for the domain name domain1.example, is required for the domain name domain2.example in the "tmch", and is required for the domain name domain3.example in the "tmch" and "custom-tmch":
以下是当域名domain1.example不需要“索赔”启动阶段的索赔通知时的索赔检查响应示例，“tmch”中的域名domain2.example需要索赔通知，“tmch”和“custom tmch”中的域名domain3.example需要索赔通知时的索赔检查响应示例：
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: <extension>
S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>claims</launch:phase>
S: <launch:cd>
S: <launch:name exists="0">domain1.example</launch:name>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">domain2.example</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">domain3.example</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: <launch:claimKey validatorID="custom-tmch">
S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002
S: </launch:claimKey>
S: </launch:cd>
S: </launch:chkData>
S: </extension>
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: <extension>
S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>claims</launch:phase>
S: <launch:cd>
S: <launch:name exists="0">domain1.example</launch:name>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">domain2.example</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">domain3.example</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: <launch:claimKey validatorID="custom-tmch">
S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002
S: </launch:claimKey>
S: </launch:cd>
S: </launch:chkData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
The Availability Check Form defines additional elements to extend the EPP <check> command described in the EPP domain name mapping [RFC5731]. No additional elements are defined for the EPP <check> response. This form MUST be identified by setting the <launch:check> "type" attribute to "avail".
可用性检查表单定义了其他元素，以扩展EPP域名映射[RFC5731]中描述的EPP<Check>命令。没有为EPP<check>响应定义其他元素。必须通过将<launch:check>“type”属性设置为“avail”来标识此表单。
The EPP <check> command is used to determine if an object can be provisioned within a repository. Domain names may be made available only in unique launch phases, whilst remaining unavailable for concurrent launch phases. In addition to the elements expressed in the <domain:check>, the command is extended with the <launch:check> element that contains the following child element:
EPP<check>命令用于确定是否可以在存储库中配置对象。域名可能仅在独特的启动阶段可用，而在并行启动阶段不可用。除了在<domain:check>中表示的元素外，该命令还通过包含以下子元素的<launch:check>元素进行扩展：
<launch:phase>: The launch phase to which domain name availability should be determined. The server SHOULD validate the value and return an EPP error result code of 2306 [RFC5730] if it is invalid.
<launch:phase>：应确定域名可用性的启动阶段。如果该值无效，服务器应验证该值并返回一个EPP错误结果代码2306[RFC5730]。
The following is an example Availability Check Form Command using the <check> domain command and the <launch:check> extension with the "type" set to "avail", to determine the availability of two domain names in the "idn-release" custom launch phase:
下面是一个可用性检查表单命令示例，使用<Check>域命令和<launch:Check>扩展名，将“type”设置为“avail”，以确定“idn release”自定义启动阶段两个域名的可用性：
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: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain1.example</domain:name>
C: <domain:name>domain2.example</domain:name>
C: </domain:check>
C: </check>
C: <extension>
C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="avail">
C: <launch:phase name="idn-release">custom</launch:phase>
C: </launch:check>
C: </extension>
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: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain1.example</domain:name>
C: <domain:name>domain2.example</domain:name>
C: </domain:check>
C: </check>
C: <extension>
C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="avail">
C: <launch:phase name="idn-release">custom</launch:phase>
C: </launch:check>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
The Availability Check Form does not define any extension to the response of a <check> domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping [RFC5731].
可用性检查表单未定义对<Check>域命令响应的任何扩展。处理完该命令后，服务器将使用EPP域名映射[RFC5731]中定义的标准EPP响应进行响应。
The Trademark Check Form defines a new command called the Trademark Check Command that is used to determine whether or not there are any matching trademarks for each domain name passed in the command, independent of the active launch phase of the server and whether the "Claims Create Form" is required on a Domain Create Command. The availability check information defined in the EPP domain name mapping [RFC5731] MUST NOT be returned for the Trademark Check Command. This form MUST be identified by setting the <launch:check> "type" attribute to "trademark".
商标检查表单定义了一个名为商标检查命令的新命令，该命令用于确定该命令中传递的每个域名是否有任何匹配商标，与服务器的活动启动阶段无关，以及域创建命令是否需要“声明创建表单”。不得为商标检查命令返回EPP域名映射[RFC5731]中定义的可用性检查信息。必须通过将<launch:check>“type”属性设置为“商标”来标识此表单。
Instead of returning whether the domain name is available, the Trademark Check Command will return whether or not at least one matching trademark exists for the domain name. If there is at least one matching trademark that exists for the domain name, a <launch:claimKey> element is returned. The client MAY then use the value of the <launch:claimKey> element to obtain Trademark Claims Notice information from the Trademark Validator based on the Validator Identifier (Section 2.2).
商标检查命令将返回域名是否存在至少一个匹配商标，而不是返回域名是否可用。如果域名至少存在一个匹配商标，则返回<launch:claimKey>元素。然后，客户可以使用<launch:claimKey>元素的值，根据验证器标识符从商标验证器获取商标索赔通知信息（第2.2节）。
The <domain:name> elements in the EPP <check> command of EPP domain name mapping [RFC5731] define the domain names to check for matching trademarks. The <launch:check> element does not contain any child elements with the "Trademark Check Form":
EPP域名映射[RFC5731]的EPP<check>命令中的<domain:name>元素定义要检查匹配商标的域名。<launch:check>元素不包含任何带有“商标检查表单”的子元素：
The following is an example Trademark Check Command using the <check> domain command and the <launch:check> extension with the "type" set to "trademark", to determine if "domain1.example", "domain2.example", and "domain3.example" have any matching trademarks:
下面是一个商标检查命令示例，使用<Check>域命令和<launch:Check>扩展，将“type”设置为“商标”，以确定“domain1.example”、“domain2.example”和“domain3.example”是否有任何匹配的商标：
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: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain1.example</domain:name>
C: <domain:name>domain2.example</domain:name>
C: <domain:name>domain3.example</domain:name>
C: </domain:check>
C: </check>
C: <extension>
C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="trademark"/>
C: </extension>
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: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain1.example</domain:name>
C: <domain:name>domain2.example</domain:name>
C: <domain:name>domain3.example</domain:name>
C: </domain:check>
C: </check>
C: <extension>
C: <launch:check
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="trademark"/>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
If the <check> command has been processed successfully, the EPP <response> MUST contain an <extension> <launch:chkData> element that identifies the launch namespace. The <launch:chkData> element contains the following child elements:
如果已成功处理<check>命令，则EPP<response>必须包含标识启动命名空间的<extension><launch:chkData>元素。<launch:chkData>元素包含以下子元素：
<launch:cd>: One or more <launch:cd> elements that contain the following child elements:
<launch:cd>：包含以下子元素的一个或多个<launch:cd>元素：
<launch:name>: Contains the fully qualified name of the queried domain name. This element MUST contain an "exists" attribute whose value indicates if a matching trademark exists for the domain name. A value of "1" (or "true") means that a matching trademark does exist. A value of "0" (or "false") means that a matching trademark does not exist.
<launch:name>：包含查询域名的完全限定名。此元素必须包含一个“exists”属性，其值指示域名是否存在匹配的商标。值“1”（或“true”）表示存在匹配的商标。值“0”（或“false”）表示不存在匹配的商标。
<launch:claimKey>: Zero or more OPTIONAL claim keys that MAY be passed to a third-party Trademark Validator such as the ICANN TMCH for querying the information needed to generate a Trademark Claims Notice. The <launch:claimKey> is used as the key for the query in place of the domain name to securely query the service without using a well-known value like a domain name. The OPTIONAL "validatorID" attribute is the Validator Identifier (Section 2.2) whose value indicates
<launch:claimKey>：零个或多个可选的索赔密钥，可传递给第三方商标验证器，如ICANN TMCH，用于查询生成商标索赔通知所需的信息。<launch:claimKey>被用作查询的密钥而不是域名，以安全地查询服务，而不使用像域名这样的已知值。可选的“validatorID”属性是验证器标识符（第2.2节），其值指示
which Trademark Validator to query for the claims notice information, with the default being the ICANN TMCH. The "validatorID" attribute MAY reference a non-trademark claims clearinghouse identifier to support other forms of claims notices.
哪个商标验证器查询索赔通知信息，默认为ICANN TMCH。“validatorID”属性可以引用非商标索赔清算所标识符来支持其他形式的索赔通知。
The following is an example Trademark Check response for the "claims" launch phase when no matching trademarks are found for the domain name domain1.example, matching trademarks are found for the domain name domain2.example in the "tmch", and matching trademarks are found for domain name domain3.example in the "tmch" and "custom-tmch":
以下是“索赔”启动阶段的商标检查响应示例，其中未找到域名域的匹配商标1。示例，找到域名域的匹配商标2。示例，在“tmch”中，找到域名域的匹配商标3。示例，在“tmch”和“自定义tmch”中：
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: <extension>
S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:cd>
S: <launch:name exists="0">domain1.example</launch:name>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">domain2.example</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">domain3.example</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: <launch:claimKey validatorID="custom-tmch">
S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002
S: </launch:claimKey>
S: </launch:cd>
S: </launch:chkData>
S: </extension>
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: <extension>
S: <launch:chkData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:cd>
S: <launch:name exists="0">domain1.example</launch:name>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">domain2.example</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: </launch:cd>
S: <launch:cd>
S: <launch:name exists="1">domain3.example</launch:name>
S: <launch:claimKey validatorID="tmch">
S: 2013041500/2/6/9/rJ1NrDO92vDsAzf7EQzgjX4R0000000001
S: </launch:claimKey>
S: <launch:claimKey validatorID="custom-tmch">
S: 20140423200/1/2/3/rJ1Nr2vDsAzasdff7EasdfgjX4R000000002
S: </launch:claimKey>
S: </launch:cd>
S: </launch:chkData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
This extension defines additional elements to extend the EPP <info> command and response to be used in conjunction with the EPP domain name mapping [RFC5731].
此扩展定义了其他元素，以扩展EPP<info>命令和响应，以便与EPP域名映射[RFC5731]一起使用。
The EPP <info> command is used to retrieve information for a Launch Registration or Launch Application. The Application Identifier (Section 2.1) returned in the <launch:creData> element of the create response (Section 3.3) can be used for retrieving information for a Launch Application. A <launch:info> element is sent along with the regular <info> domain command. The <launch:info> element includes an OPTIONAL "includeMark" boolean attribute, with a default value of "false", to indicate whether or not to include the mark in the response. The <launch:info> element contains the following child elements:
EPP<info>命令用于检索启动注册或启动应用程序的信息。创建响应（第3.3节）的<launch:creData>元素中返回的应用程序标识符（第2.1节）可用于检索启动应用程序的信息。<launch:info>元素与常规的<info>域命令一起发送。<launch:info>元素包含一个可选的“includeMark”布尔属性，默认值为“false”，用于指示是否在响应中包含该标记。<launch:info>元素包含以下子元素：
<launch:phase>: The phase during which the application or registration was submitted or is associated with. Server policy defines the phases that are supported. The server SHOULD validate the value and return an EPP error result code of 2306 [RFC5730] if it is invalid.
<launch:phase>：提交申请或注册或与之关联的阶段。服务器策略定义支持的阶段。如果该值无效，服务器应验证该值并返回一个EPP错误结果代码2306[RFC5730]。
<launch:applicationID>: OPTIONAL application identifier of the Launch Application.
<launch:applicationID>：启动应用程序的可选应用程序标识符。
The following is an example <info> domain command with the <launch:info> extension to retrieve information for the sunrise application for domain.example and application identifier "abc123":
下面是一个带有<launch:info>扩展名的<info>域命令示例，用于检索域的sunrise应用程序的信息。示例和应用程序标识符“abc123”：
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: <domain:info
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: </domain:info>
C: </info>
C: <extension>
C: <launch:info
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: includeMark="true">
C: <launch:phase>sunrise</launch:phase>
C: <launch:applicationID>abc123</launch:applicationID>
C: </launch:info>
C: </extension>
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: <domain:info
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: </domain:info>
C: </info>
C: <extension>
C: <launch:info
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: includeMark="true">
C: <launch:phase>sunrise</launch:phase>
C: <launch:applicationID>abc123</launch:applicationID>
C: </launch:info>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
The following is an example <info> domain command with the <launch:info> extension to retrieve information for the sunrise registration for domain.example:
以下是带有<launch:info>扩展名的<info>domain命令示例，用于检索域的sunrise注册信息。示例：
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: <domain:info
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: </domain:info>
C: </info>
C: <extension>
C: <launch:info
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: </launch:info>
C: </extension>
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: <domain:info
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: </domain:info>
C: </info>
C: <extension>
C: <launch:info
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: </launch:info>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
If the query was successful, the server replies with a <launch:infData> element along with the regular EPP <resData>. The <launch:infData> contains the following child elements:
如果查询成功，服务器将使用<launch:infData>元素以及常规EPP<resData>进行响应。<launch:infData>包含以下子元素：
<launch:phase>: The phase during which the application was submitted or is associated with that matches the associated <info> command <launch:phase>.
<launch:phase>：提交应用程序或与之关联的阶段，该阶段与关联的<info>命令<launch:phase>相匹配。
<launch:applicationID>: OPTIONAL Application Identifier of the Launch Application.
<launch:applicationID>：启动应用程序的可选应用程序标识符。
<launch:status>: OPTIONAL status of the Launch Application using one of the supported status values (Section 2.4).
<launch:status>：使用支持的状态值之一的启动应用程序的可选状态（第2.4节）。
<mark:mark>: Zero or more <mark:mark> (Section 2.6.2) elements only if the "includeMark" attribute is "true" in the command.
<mark:mark>：仅当命令中的“includeMark”属性为“true”时，才允许零个或多个<mark:mark>（第2.6.2节）元素。
The following is an example <info> domain response using the <launch:infData> extension with the mark information:
以下是使用带有标记信息的<launch:infData>扩展名的<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: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>domain.example</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="pendingCreate"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>2012-04-03T22:00:00.0Z</domain:crDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="pendingValidation"/>
S: <mark:mark
S: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
S: ...
S: </mark:mark>
S: </launch:infData>
S: </extension>
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: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>domain.example</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="pendingCreate"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>2012-04-03T22:00:00.0Z</domain:crDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <launch:infData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>abc123</launch:applicationID>
S: <launch:status s="pendingValidation"/>
S: <mark:mark
S: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
S: ...
S: </mark:mark>
S: </launch:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
There are four forms of the extension to the EPP <create> command that include the Sunrise Create Form (Section 3.3.1), the Claims Create Form (Section 3.3.2), the General Create Form (Section 3.3.3), and the Mixed Create Form (Section 3.3.4). The form used is dependent on the supported launch phases (Section 2.3) as defined below.
EPP<create>命令有四种扩展形式，包括Sunrise创建形式（第3.3.1节）、索赔创建形式（第3.3.2节）、通用创建形式（第3.3.3节）和混合创建形式（第3.3.4节）。所使用的形式取决于支持的发射阶段（第2.3节），定义如下。
sunrise: The EPP <create> command with the "sunrise" launch phase is used to submit a registration with trademark information that can be verified by the server with the <domain:name> value. The Sunrise Create Form (Section 3.3.1) is used for the "sunrise" launch phase.
sunrise:EPP<create>命令和“sunrise”启动阶段用于提交注册商标信息，该信息可由服务器使用<domain:name>值进行验证。日出创建表单（第3.3.1节）用于“日出”发射阶段。
landrush: The EPP <create> command with the "landrush" launch phase MAY use the General Create Form (Section 3.3.3) to explicitly specify the phase and optionally define the expected type of object to create.
landrush：带有“landrush”启动阶段的EPP<create>命令可使用通用创建表单（第3.3.3节）明确指定阶段，并可选择定义要创建的预期对象类型。
claims: The EPP <create> command with the "claims" launch phase is used to pass the information associated with the presentation and acceptance of the claims notice. The Claims Create Form (Section 3.3.2) is used, and the General Create Form (Section 3.3.3) MAY be used for the "claims" launch phase.
索赔：带有“索赔”启动阶段的EPP<create>命令用于传递与索赔通知的提交和接受相关的信息。使用索赔创建表（第3.3.2节），一般创建表（第3.3.3节）可用于“索赔”启动阶段。
open: The EPP <create> command with the "open" launch phase is undefined, but the form supported is up to server policy. The Claims Create Form (Section 3.3.2) MAY be used to pass the information associated with the presentation and acceptance of the claims notice if required for the domain name.
打开：带有“打开”启动阶段的EPP<create>命令未定义，但支持的表单取决于服务器策略。如果域名需要，索赔创建表（第3.3.2节）可用于传递与提交和接受索赔通知相关的信息。
custom: The EPP <create> command with the "custom" launch phase is undefined, but the form supported is up to server policy.
自定义：带有“自定义”启动阶段的EPP<create>命令未定义，但支持的表单取决于服务器策略。
The Sunrise Create Form of the extension to the EPP domain name mapping [RFC5731] includes the verifiable trademark information that the server uses to match against the domain name to authorize the domain create. A server MUST support one of four models in Mark Validation Models (Section 2.6) to verify the trademark information passed by the client.
EPP域名映射[RFC5731]扩展的Sunrise Create表单包含可验证商标信息，服务器使用该信息与域名进行匹配，以授权域创建。服务器必须支持标记验证模型（第2.6节）中的四种模型之一，以验证客户端传递的商标信息。
A <launch:create> element is sent along with the regular <create>
domain command. The <launch:create> element has an OPTIONAL "type"
attribute that defines the expected type of object ("application" or
"registration") to create. The server SHOULD validate the "type"
A <launch:create> element is sent along with the regular <create>
domain command. The <launch:create> element has an OPTIONAL "type"
attribute that defines the expected type of object ("application" or
"registration") to create. The server SHOULD validate the "type"
attribute, when passed, against the type of object that will be created, and return an EPP error result code of 2306 [RFC5730] if the type is incorrect. The <launch:create> element contains the following child elements:
属性，如果类型不正确，则返回EPP错误结果代码2306[RFC5730]。<launch:create>元素包含以下子元素：
<launch:phase>: The identifier for the launch phase. The server SHOULD validate the value according to Section 2.3.
<launch:phase>：启动阶段的标识符。服务器应根据第2.3节验证该值。
<launch:codeMark> or <smd:signedMark> or <smd:encodedSignedMark>:
<launch:codeMark>或<smd:signedMark>或<smd:encodedSignedMark>：
<launch:codeMark>: Zero or more <launch:codeMark> elements. The <launch:codeMark> child elements are defined in "<launch:codeMark> Element" (Section 2.6.1).
<launch:codeMark>：零个或多个<launch:codeMark>元素。<launch:codeMark>子元素在“<launch:codeMark>元素”（第2.6.1节）中定义。
<smd:signedMark>: Zero or more <smd:signedMark> elements. The <smd:signedMark> child elements are defined in "<smd:signedMark> Element" (Section 2.6.3.1).
<smd:signedMark>：零个或多个<smd:signedMark>元素。<smd:signedMark>子元素在“<smd:signedMark>元素”（第2.6.3.1节）中定义。
<smd:encodedSignedMark>: Zero or more <smd:encodedSignedMark> elements. The <smd:encodedSignedMark> child elements are defined in "<smd:encodedSignedMark> Element" (Section 2.6.3.2).
<smd:encodedSignedMark>：零个或多个<smd:encodedSignedMark>元素。<smd:encodedSignedMark>子元素在“<smd:encodedSignedMark>元素”（第2.6.3.2节）中定义。
The following is an example <create> domain command using the <launch:create> extension, following the "code" validation model, with multiple sunrise codes:
下面是一个示例<create>域命令，使用<launch:create>扩展，遵循“code”验证模型，具有多个sunrise代码：
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:codeMark>
C: <launch:code validatorID="sample1">
C: 49FD46E6C4B45C55D4AC</launch:code>
C: </launch:codeMark>
C: <launch:codeMark>
C: <launch:code>49FD46E6C4B45C55D4AD</launch:code>
C: </launch:codeMark>
C: <launch:codeMark>
C: <launch:code validatorID="sample2">
C: 49FD46E6C4B45C55D4AE</launch:code>
C: </launch:codeMark>
C: </launch:create>
C: </extension>
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:codeMark>
C: <launch:code validatorID="sample1">
C: 49FD46E6C4B45C55D4AC</launch:code>
C: </launch:codeMark>
C: <launch:codeMark>
C: <launch:code>49FD46E6C4B45C55D4AD</launch:code>
C: </launch:codeMark>
C: <launch:codeMark>
C: <launch:code validatorID="sample2">
C: 49FD46E6C4B45C55D4AE</launch:code>
C: </launch:codeMark>
C: </launch:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
The following is an example <create> domain command using the <launch:create> extension, following the "mark" validation model, with the mark information:
下面是一个示例<create>域命令，使用<launch:create>扩展，遵循“mark”验证模型，并带有标记信息：
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:codeMark>
C: <mark:mark
C: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
C: ...
C: </mark:mark>
C: </launch:codeMark>
C: </launch:create>
C: </extension>
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:codeMark>
C: <mark:mark
C: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
C: ...
C: </mark:mark>
C: </launch:codeMark>
C: </launch:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
The following is an example <create> domain command using the <launch:create> extension, following the "code with mark" validation model, with the code and mark information:
下面是一个示例<create>域命令，使用<launch: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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:codeMark>
C: <launch:code validatorID="sample">
C: 49FD46E6C4B45C55D4AC</launch:code>
C: <mark:mark
C: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
C: ...
C: </mark:mark>
C: </launch:codeMark>
C: </launch:create>
C: </extension>
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:codeMark>
C: <launch:code validatorID="sample">
C: 49FD46E6C4B45C55D4AC</launch:code>
C: <mark:mark
C: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
C: ...
C: </mark:mark>
C: </launch:codeMark>
C: </launch:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
The following is an example <create> domain command using the <launch:create> extension, following the "signed mark" validation model, with the signed mark information for a sunrise application:
下面是一个使用<launch:create>扩展名的<create>域命令示例，该扩展名遵循“signed mark”验证模型，带有sunrise应用程序的signed mark信息：
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="application">
C: <launch:phase>sunrise</launch:phase>
C: <smd:signedMark id="signedMark"
C: xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
C: ...
C: </smd:signedMark>
C: </launch:create>
C: </extension>
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="application">
C: <launch:phase>sunrise</launch:phase>
C: <smd:signedMark id="signedMark"
C: xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
C: ...
C: </smd:signedMark>
C: </launch:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
The following is an example <create> domain command using the <launch:create> extension, following the "signed mark" validation model, with the base64-encoded signed mark information:
下面是一个示例<create>域命令，使用<launch:create>扩展，遵循“signed mark”验证模型，使用base64编码的signed mark信息：
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <smd:encodedSignedMark
C: xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
C: ...
C: </smd:encodedSignedMark>
C: </launch:create>
C: </extension>
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <smd:encodedSignedMark
C: xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
C: ...
C: </smd:encodedSignedMark>
C: </launch:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
The Claims Create Form of the extension to the EPP domain name mapping [RFC5731] includes the information related to the registrant's acceptance of the claims notice.
EPP域名映射[RFC5731]扩展的索赔创建表单包括注册人接受索赔通知的相关信息。
A <launch:create> element is sent along with the regular <create> domain command. The <launch:create> element has an OPTIONAL "type" attribute that defines the expected type of object ("application" or "registration") to create. The server SHOULD validate the "type" attribute, when passed, against the type of object that will be created, and return an EPP error result code of 2306 [RFC5730] if the type is incorrect. The <launch:create> element contains the following child elements:
一个<launch:create>元素与常规的<create>域命令一起发送。<launch:create>元素有一个可选的“type”属性，用于定义要创建的对象的预期类型（“应用程序”或“注册”）。当传递“type”属性时，服务器应根据将创建的对象类型验证该属性，如果类型不正确，则返回2306[RFC5730]的EPP错误结果代码。<launch:create>元素包含以下子元素：
<launch:phase>: Contains the value of the active launch phase of the server. The server SHOULD validate the value according to Section 2.3.
<launch:phase>：包含服务器的活动启动阶段的值。服务器应根据第2.3节验证该值。
<launch:notice>: One or more <launch:notice> elements that contain the following child elements:
<launch:notice>：包含以下子元素的一个或多个<launch:notice>元素：
<launch:noticeID>: Unique notice identifier for the claims notice. The <launch:noticeID> element has an OPTIONAL "validatorID" attribute that is used to define the Validator Identifier (Section 2.2); it's value indicates which Trademark Validator is the source of the claims notice, with the default being the ICANN TMCH.
<launch:noticeID>：索赔通知的唯一通知标识符。<launch:noticeID>元素有一个可选的“validatorID”属性，用于定义验证器标识符（第2.2节）；它的值表示哪个商标验证器是索赔通知的来源，默认为ICANN TMCH。
<launch:notAfter>: Expiry of the claims notice.
<launch:notAfter>：索赔通知到期。
<launch:acceptedDate>: Contains the date and time that the claims notice was accepted.
<launch:acceptedDate>：包含接受索赔通知的日期和时间。
The following is an example <create> domain command using the <launch:create> extension with the <launch:notice> information for the "tmch" and the "custom-tmch" validators, for the "claims" launch phase:
下面是一个示例<create>域命令，它使用<launch:create>扩展和<launch:notice>信息，用于“声明”启动阶段的“tmch”和“自定义tmch”验证器：
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>claims</launch:phase>
C: <launch:notice>
C: <launch:noticeID validatorID="tmch">
C: 370d0b7c9223372036854775807</launch:noticeID>
C: <launch:notAfter>2014-06-19T10:00:00.0Z
C: </launch:notAfter>
C: <launch:acceptedDate>2014-06-19T09:00:00.0Z
C: </launch:acceptedDate>
C: </launch:notice>
C: <launch:notice>
C: <launch:noticeID validatorID="custom-tmch">
C: 470d0b7c9223654313275808</launch:noticeID>
C: <launch:notAfter>2014-06-19T10:00:00.0Z
C: </launch:notAfter>
C: <launch:acceptedDate>2014-06-19T09:00:30.0Z
C: </launch:acceptedDate>
C: </launch:notice>
C: </launch:create>
C: </extension>
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>claims</launch:phase>
C: <launch:notice>
C: <launch:noticeID validatorID="tmch">
C: 370d0b7c9223372036854775807</launch:noticeID>
C: <launch:notAfter>2014-06-19T10:00:00.0Z
C: </launch:notAfter>
C: <launch:acceptedDate>2014-06-19T09:00:00.0Z
C: </launch:acceptedDate>
C: </launch:notice>
C: <launch:notice>
C: <launch:noticeID validatorID="custom-tmch">
C: 470d0b7c9223654313275808</launch:noticeID>
C: <launch:notAfter>2014-06-19T10:00:00.0Z
C: </launch:notAfter>
C: <launch:acceptedDate>2014-06-19T09:00:30.0Z
C: </launch:acceptedDate>
C: </launch:notice>
C: </launch:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
The General Create Form of the extension to the EPP domain name mapping [RFC5731] includes the launch phase and optionally the object type to create. The OPTIONAL "type" attribute defines the expected type of object ("application" or "registration") to create. The server SHOULD validate the "type" attribute, when passed, against the type of object that will be created, and return an EPP error result code of 2306 [RFC5730] if the type is incorrect.
EPP域名映射[RFC5731]扩展的一般创建形式包括启动阶段和要创建的对象类型（可选）。可选的“type”属性定义要创建的对象的预期类型（“应用程序”或“注册”）。当传递“type”属性时，服务器应根据将创建的对象类型验证该属性，如果类型不正确，则返回2306[RFC5730]的EPP错误结果代码。
A <launch:create> element is sent along with the regular <create> domain command. The <launch:create> element contains the following child element:
一个<launch:create>元素与常规的<create>域命令一起发送。<launch:create>元素包含以下子元素：
<launch:phase>: Contains the value of the active launch phase of the server. The server SHOULD validate the value according to Section 2.3.
<launch:phase>：包含服务器的活动启动阶段的值。服务器应根据第2.3节验证该值。
The following is an example <create> domain command using the <launch:create> extension for a "landrush" launch phase application:
以下是使用“landrush”启动阶段应用程序的<launch:create>扩展的<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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="application">
C: <launch:phase>landrush</launch:phase>
C: </launch:create>
C: </extension>
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="application">
C: <launch:phase>landrush</launch:phase>
C: </launch:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
The Mixed Create Form supports a mix of the create forms where, for example, the Sunrise Create Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2) MAY be supported in a single command by including both the verified trademark information and the information related to the registrant's acceptance of the claims notice. The server MAY support the Mixed Create Form. The "custom" launch phase SHOULD be used when using the Mixed Create Form.
混合创建表单支持创建表单的混合，例如，Sunrise创建表单（第3.3.1节）和权利要求创建表单（第3.3.2节）可以通过包含验证商标信息和与注册人接受权利要求通知相关的信息，在单个命令中得到支持。服务器可能支持混合创建表单。使用混合创建表单时，应使用“自定义”启动阶段。
The following is an example <create> domain command using the <launch:create> extension, with a mix of the Sunrise Create Form (Section 3.3.1) and the Claims Create Form (Section 3.3.2), including both a mark and a notice:
下面是一个使用<launch:create>扩展名的<create>域命令示例，它混合了Sunrise创建表单（第3.3.1节）和Claims创建表单（第3.3.2节），包括标记和通知：
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="application">
C: <launch:phase name="non-tmch-sunrise">custom</launch:phase>
C: <launch:codeMark>
C: <mark:mark
C: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
C: ...
C: </mark:mark>
C: </launch:codeMark>
C: <launch:notice>
C: <launch:noticeID validatorID="tmch">
C: 49FD46E6C4B45C55D4AC
C: </launch:noticeID>
C: <launch:notAfter>2012-06-19T10:00:10.0Z
C: </launch:notAfter>
C: <launch:acceptedDate>2012-06-19T09:01:30.0Z
C: </launch:acceptedDate>
C: </launch:notice>
C: </launch:create>
C: </extension>
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: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domainone.example</domain:name>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <launch:create
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
C: type="application">
C: <launch:phase name="non-tmch-sunrise">custom</launch:phase>
C: <launch:codeMark>
C: <mark:mark
C: xmlns:mark="urn:ietf:params:xml:ns:mark-1.0">
C: ...
C: </mark:mark>
C: </launch:codeMark>
C: <launch:notice>
C: <launch:noticeID validatorID="tmch">
C: 49FD46E6C4B45C55D4AC
C: </launch:noticeID>
C: <launch:notAfter>2012-06-19T10:00:10.0Z
C: </launch:notAfter>
C: <launch:acceptedDate>2012-06-19T09:01:30.0Z
C: </launch:acceptedDate>
C: </launch:notice>
C: </launch:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
If the create was successful, the server MAY add a <launch:creData> element to the regular EPP <resData> to indicate that the server generated an Application Identifier (Section 2.1), when multiple applications of a given domain name are supported; otherwise, no extension is included with the regular EPP <resData>. The <launch:creData> element contains the following child elements:
如果创建成功，服务器可以在常规EPP<resData>中添加<launch:creData>元素，以指示服务器在支持给定域名的多个应用程序时生成了应用程序标识符（第2.1节）；否则，常规EPP<resData>中不包含任何扩展。<launch:creData>元素包含以下子元素：
<launch:phase>: The phase of the application that mirrors the <launch:phase> element included in the <launch:create>.
<launch:phase>：反映<launch:create>中包含的<launch:phase>元素的应用程序阶段。
<launch:applicationID>: The application identifier of the application.
<launch:applicationID>：应用程序的应用程序标识符。
The following is an example response when multiple overlapping applications are supported by the server:
以下是服务器支持多个重叠应用程序时的响应示例：
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: <domain:creData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>domain.example</domain:name>
S: <domain:crDate>2010-08-10T15:38:26.623854Z</domain:crDate>
S: </domain:creData>
S: </resData>
S: <extension>
S: <launch:creData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>2393-9323-E08C-03B1
S: </launch:applicationID>
S: </launch:creData>
S: </extension>
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: <domain:creData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>domain.example</domain:name>
S: <domain:crDate>2010-08-10T15:38:26.623854Z</domain:crDate>
S: </domain:creData>
S: </resData>
S: <extension>
S: <launch:creData
S: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
S: <launch:phase>sunrise</launch:phase>
S: <launch:applicationID>2393-9323-E08C-03B1
S: </launch:applicationID>
S: </launch:creData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
This extension defines additional elements to extend the EPP <update> command to be used in conjunction with the domain name mapping.
此扩展定义了其他元素，以扩展与域名映射一起使用的EPP<update>命令。
When an EPP <update> command with the extension is sent to a server that does not support Launch Applications, it will fail. A server that does not support Launch Applications during its launch phase MUST return an EPP error result code of 2102 [RFC5730] when receiving an EPP <update> command with the extension.
当带有扩展名的EPP<update>命令发送到不支持启动应用程序的服务器时，它将失败。在启动阶段不支持启动应用程序的服务器在接收到带有扩展名的EPP<update>命令时，必须返回EPP错误结果代码2102[RFC5730]。
Registry policies permitting, clients may update an application object by submitting an EPP <update> command along with a <launch:update> element to indicate the application object to be updated. The <launch:update> element contains the following child elements:
在注册表策略允许的情况下，客户端可以通过提交EPP<update>命令以及<launch:update>元素来更新应用程序对象，以指示要更新的应用程序对象。<launch:update>元素包含以下子元素：
<launch:phase>: The phase during which the application was submitted or is associated with. The server SHOULD validate the value and return an EPP error result code of 2306 [RFC5730] if it is invalid.
<launch:phase>：提交申请或与之关联的阶段。如果该值无效，服务器应验证该值并返回一个EPP错误结果代码2306[RFC5730]。
<launch:applicationID>: The application identifier for which the client wishes to update.
<launch:applicationID>：客户端希望更新的应用程序标识符。
The following is an example <update> domain command with the <launch:update> extension to add and remove a name server of a sunrise application with the application identifier "abc123":
下面是一个带有<launch:update>扩展名的<update>域命令示例，用于添加和删除应用程序标识符为“abc123”的sunrise应用程序的名称服务器：
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: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:add>
C: <domain:ns>
C: <domain:hostObj>ns2.domain.example</domain:hostObj>
C: </domain:ns>
C: </domain:add>
C: <domain:rem>
C: <domain:ns>
C: <domain:hostObj>ns1.domain.example</domain:hostObj>
C: </domain:ns>
C: </domain:rem>
C: </domain:update>
C: </update>
C: <extension>
C: <launch:update
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:applicationID>abc123</launch:applicationID>
C: </launch:update>
C: </extension>
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: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: <domain:add>
C: <domain:ns>
C: <domain:hostObj>ns2.domain.example</domain:hostObj>
C: </domain:ns>
C: </domain:add>
C: <domain:rem>
C: <domain:ns>
C: <domain:hostObj>ns1.domain.example</domain:hostObj>
C: </domain:ns>
C: </domain:rem>
C: </domain:update>
C: </update>
C: <extension>
C: <launch:update
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:applicationID>abc123</launch:applicationID>
C: </launch:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
This extension does not define any extension to the response of an <update> domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping [RFC5731].
此扩展不定义对<update>域命令响应的任何扩展。处理完该命令后，服务器将使用EPP域名映射[RFC5731]中定义的标准EPP响应进行响应。
This extension defines additional elements to extend the EPP <delete> command to be used in conjunction with the domain name mapping.
此扩展定义了其他元素，以扩展与域名映射一起使用的EPP<delete>命令。
A client MUST NOT pass the extension on an EPP <delete> command to a server that does not support Launch Applications. A server that does
客户端不得将EPP<delete>命令上的扩展传递给不支持启动应用程序的服务器。服务器
not support Launch Applications during its launch phase MUST return an EPP error result code of 2102 [RFC5730] when receiving an EPP <delete> command with the extension.
不支持在启动阶段启动的应用程序在接收到带有扩展名的EPP<delete>命令时，必须返回EPP错误结果代码2102[RFC5730]。
Registry policies permitting, clients MAY withdraw an application by submitting an EPP <delete> command along with a <launch:delete> element to indicate the application object to be deleted. The <launch:delete> element contains the following child elements:
如果注册表策略允许，客户端可以通过提交EPP<delete>命令以及<launch:delete>元素来撤回应用程序，以指示要删除的应用程序对象。<launch:delete>元素包含以下子元素：
<launch:phase>: The phase during which the application was submitted or is associated with. The server SHOULD validate the value and return an EPP error result code of 2306 [RFC5730] if it is invalid.
<launch:phase>：提交申请或与之关联的阶段。如果该值无效，服务器应验证该值并返回一个EPP错误结果代码2306[RFC5730]。
<launch:applicationID>: The application identifier for which the client wishes to delete.
<launch:applicationID>：客户端希望删除的应用程序标识符。
The following is an example <delete> domain command with the <launch:delete> extension:
以下是带有<launch:delete>扩展名的<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: <domain:delete
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: </domain:delete>
C: </delete>
C: <extension>
C: <launch:delete
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:applicationID>abc123</launch:applicationID>
C: </launch:delete>
C: </extension>
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: <domain:delete
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>domain.example</domain:name>
C: </domain:delete>
C: </delete>
C: <extension>
C: <launch:delete
C: xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
C: <launch:phase>sunrise</launch:phase>
C: <launch:applicationID>abc123</launch:applicationID>
C: </launch:delete>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
This extension does not define any extension to the response of a <delete> domain command. After processing the command, the server replies with a standard EPP response as defined in the EPP domain name mapping [RFC5731].
此扩展不定义对<delete>域命令响应的任何扩展。处理完该命令后，服务器将使用EPP域名映射[RFC5731]中定义的标准EPP响应进行响应。
This extension does not define any extension to the EPP <renew> command or response described in the EPP domain name mapping [RFC5731].
此扩展不定义EPP域名映射[RFC5731]中描述的EPP<renew>命令或响应的任何扩展。
This extension does not define any extension to the EPP <transfer> command or response described in the EPP domain name mapping [RFC5731].
此扩展不定义EPP域名映射[RFC5731]中描述的EPP<transfer>命令或响应的任何扩展。
The EPP Launch Phase Mapping schema is presented in Section 4.1.
EPP启动阶段映射模式见第4.1节。
The formal syntax presented 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实例。开始和结束标记不是模式的一部分；它们用于记录模式的开始和结束，以便进行URI注册。
Copyright (c) 2018 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2018 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
在满足以下条件的情况下，允许以源代码和二进制格式重新分发和使用，无论是否修改：
o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
o 源代码的重新分发必须保留上述版权声明、此条件列表和以下免责声明。
o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
o 以二进制形式重新分发时，必须在分发时提供的文档和/或其他材料中复制上述版权声明、本条件列表和以下免责声明。
o Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission.
o 未经事先书面许可，不得使用互联网协会、IETF或IETF Trust的名称或特定贡献者的名称来认可或推广源自本软件的产品。
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
本软件由版权所有者和贡献者“按原样”提供，不承担任何明示或暗示的担保，包括但不限于对适销性和特定用途适用性的暗示担保。在任何情况下，版权
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
业主或出资人应对任何直接、间接、偶然、特殊、惩戒性或后果性损害（包括但不限于替代货物或服务的采购；使用、数据或利润的损失；或业务中断）负责，无论是合同、严格责任还是侵权行为，无论是何种原因造成的（包括疏忽或其他）在使用本软件过程中以任何方式产生的，即使告知可能发生此类损坏。
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema
targetNamespace="urn:ietf:params:xml:ns:launch-1.0"
xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema
targetNamespace="urn:ietf:params:xml:ns:launch-1.0"
xmlns:launch="urn:ietf:params:xml:ns:launch-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:mark="urn:ietf:params:xml:ns:mark-1.0"
xmlns:smd="urn:ietf:params:xml:ns:signedMark-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:mark-1.0"/>
<import namespace="urn:ietf:params:xml:ns:signedMark-1.0"/>
<!-- Import common element types -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"/>
<import namespace="urn:ietf:params:xml:ns:mark-1.0"/>
<import namespace="urn:ietf:params:xml:ns:signedMark-1.0"/>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name
extension schema
for the launch phase processing.
</documentation>
</annotation>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name
extension schema
for the launch phase processing.
</documentation>
</annotation>
<!-- Child elements found in EPP commands -->
<element
name="check"
type="launch:checkType"/>
<element
name="info"
type="launch:infoType"/>
<element
name="create"
type="launch:createType"/>
<element
name="update"
type="launch:idContainerType"/>
<element
name="delete"
<!-- Child elements found in EPP commands -->
<element
name="check"
type="launch:checkType"/>
<element
name="info"
type="launch:infoType"/>
<element
name="create"
type="launch:createType"/>
<element
name="update"
type="launch:idContainerType"/>
<element
name="delete"
type="launch:idContainerType"/>
type="launch:idContainerType"/>
<!-- Common container of id (identifier) element -->
<complexType name="idContainerType">
<sequence>
<element
name="phase"
type="launch:phaseType"/>
<element
name="applicationID"
type="launch:applicationIDType"/>
</sequence>
</complexType>
<!-- Common container of id (identifier) element -->
<complexType name="idContainerType">
<sequence>
<element
name="phase"
type="launch:phaseType"/>
<element
name="applicationID"
type="launch:applicationIDType"/>
</sequence>
</complexType>
<!-- Definition for application identifier -->
<simpleType name="applicationIDType">
<restriction base="token"/>
</simpleType>
<!-- Definition for application identifier -->
<simpleType name="applicationIDType">
<restriction base="token"/>
</simpleType>
<!-- Definition for launch phase. Name is an
optional attribute used to extend the phase type.
For example, when using the phase type value
of "custom", the "name" can be used to specify the
custom phase. -->
<complexType name="phaseType">
<simpleContent>
<extension base="launch:phaseTypeValue">
<attribute
name="name"
type="token"/>
</extension>
</simpleContent>
</complexType>
<!-- Definition for launch phase. Name is an
optional attribute used to extend the phase type.
For example, when using the phase type value
of "custom", the "name" can be used to specify the
custom phase. -->
<complexType name="phaseType">
<simpleContent>
<extension base="launch:phaseTypeValue">
<attribute
name="name"
type="token"/>
</extension>
</simpleContent>
</complexType>
<!-- Enumeration of launch phase values -->
<simpleType name="phaseTypeValue">
<restriction base="token">
<enumeration value="sunrise"/>
<enumeration value="landrush"/>
<enumeration value="claims"/>
<enumeration value="open"/>
<enumeration value="custom"/>
</restriction>
</simpleType>
<!-- Enumeration of launch phase values -->
<simpleType name="phaseTypeValue">
<restriction base="token">
<enumeration value="sunrise"/>
<enumeration value="landrush"/>
<enumeration value="claims"/>
<enumeration value="open"/>
<enumeration value="custom"/>
</restriction>
</simpleType>
<!-- Definition for the sunrise code -->
<simpleType name="codeValue">
<!-- Definition for the sunrise code -->
<simpleType name="codeValue">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<complexType name="codeType">
<simpleContent>
<extension base="launch:codeValue">
<attribute
name="validatorID"
type="launch:validatorIDType"
use="optional"/>
</extension>
</simpleContent>
</complexType>
<complexType name="codeType">
<simpleContent>
<extension base="launch:codeValue">
<attribute
name="validatorID"
type="launch:validatorIDType"
use="optional"/>
</extension>
</simpleContent>
</complexType>
<!-- Definition for the notice identifier -->
<simpleType name="noticeIDValue">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<!-- Definition for the notice identifier -->
<simpleType name="noticeIDValue">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<complexType name="noticeIDType">
<simpleContent>
<extension base="launch:noticeIDValue">
<attribute
name="validatorID"
type="launch:validatorIDType"
use="optional"/>
</extension>
</simpleContent>
</complexType>
<complexType name="noticeIDType">
<simpleContent>
<extension base="launch:noticeIDValue">
<attribute
name="validatorID"
type="launch:validatorIDType"
use="optional"/>
</extension>
</simpleContent>
</complexType>
<!-- Definition for the validator identifier -->
<simpleType name="validatorIDType">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<!-- Definition for the validator identifier -->
<simpleType name="validatorIDType">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<!-- Possible status values for sunrise application -->
<simpleType name="statusValueType">
<restriction base="token">
<enumeration value="pendingValidation"/>
<enumeration value="validated"/>
<enumeration value="invalid"/>
<enumeration value="pendingAllocation"/>
<!-- Possible status values for sunrise application -->
<simpleType name="statusValueType">
<restriction base="token">
<enumeration value="pendingValidation"/>
<enumeration value="validated"/>
<enumeration value="invalid"/>
<enumeration value="pendingAllocation"/>
<enumeration value="allocated"/>
<enumeration value="rejected"/>
<enumeration value="custom"/>
</restriction>
</simpleType>
<enumeration value="allocated"/>
<enumeration value="rejected"/>
<enumeration value="custom"/>
</restriction>
</simpleType>
<!-- Status type definition -->
<complexType name="statusType">
<simpleContent>
<extension base="normalizedString">
<attribute
name="s"
type="launch:statusValueType"
use="required"/>
<attribute
name="lang"
type="language"
default="en"/>
<attribute
name="name"
type="token"/>
</extension>
</simpleContent>
</complexType>
<!-- Status type definition -->
<complexType name="statusType">
<simpleContent>
<extension base="normalizedString">
<attribute
name="s"
type="launch:statusValueType"
use="required"/>
<attribute
name="lang"
type="language"
default="en"/>
<attribute
name="name"
type="token"/>
</extension>
</simpleContent>
</complexType>
<!-- codeMark Type that contains an optional
code with mark information -->
<complexType name="codeMarkType">
<sequence>
<element
name="code"
type="launch:codeType"
minOccurs="0"/>
<element
ref="mark:abstractMark"
minOccurs="0"/>
</sequence>
</complexType>
<!-- codeMark Type that contains an optional
code with mark information -->
<complexType name="codeMarkType">
<sequence>
<element
name="code"
type="launch:codeType"
minOccurs="0"/>
<element
ref="mark:abstractMark"
minOccurs="0"/>
</sequence>
</complexType>
<!-- Child elements for the create command -->
<complexType name="createType">
<sequence>
<element
name="phase"
type="launch:phaseType"/>
<choice minOccurs="0">
<element
name="codeMark"
<!-- Child elements for the create command -->
<complexType name="createType">
<sequence>
<element
name="phase"
type="launch:phaseType"/>
<choice minOccurs="0">
<element
name="codeMark"
type="launch:codeMarkType"
maxOccurs="unbounded"/>
<element
ref="smd:abstractSignedMark"
maxOccurs="unbounded"/>
<element
ref="smd:encodedSignedMark"
maxOccurs="unbounded"/>
</choice>
<element
name="notice"
type="launch:createNoticeType"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<attribute
name="type"
type="launch:objectType"/>
</complexType>
type="launch:codeMarkType"
maxOccurs="unbounded"/>
<element
ref="smd:abstractSignedMark"
maxOccurs="unbounded"/>
<element
ref="smd:encodedSignedMark"
maxOccurs="unbounded"/>
</choice>
<element
name="notice"
type="launch:createNoticeType"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
<attribute
name="type"
type="launch:objectType"/>
</complexType>
<!-- Type of launch object -->
<simpleType name="objectType">
<restriction base="token">
<enumeration value="application"/>
<enumeration value="registration"/>
</restriction>
</simpleType>
<!-- Type of launch object -->
<simpleType name="objectType">
<restriction base="token">
<enumeration value="application"/>
<enumeration value="registration"/>
</restriction>
</simpleType>
<!-- Child elements of the create notice element -->
<complexType name="createNoticeType">
<sequence>
<element
name="noticeID"
type="launch:noticeIDType"/>
<element
name="notAfter"
type="dateTime"/>
<element
name="acceptedDate"
type="dateTime"/>
</sequence>
</complexType>
<!-- Child elements of the create notice element -->
<complexType name="createNoticeType">
<sequence>
<element
name="noticeID"
type="launch:noticeIDType"/>
<element
name="notAfter"
type="dateTime"/>
<element
name="acceptedDate"
type="dateTime"/>
</sequence>
</complexType>
<!-- Child elements of check (Claims Check Command) -->
<complexType name="checkType">
<sequence>
<!-- Child elements of check (Claims Check Command) -->
<complexType name="checkType">
<sequence>
<element
name="phase"
type="launch:phaseType"
minOccurs="0"/>
</sequence>
<attribute
name="type"
type="launch:checkFormType"
default="claims"/>
</complexType>
<element
name="phase"
type="launch:phaseType"
minOccurs="0"/>
</sequence>
<attribute
name="type"
type="launch:checkFormType"
default="claims"/>
</complexType>
<!-- Type of check form (Claims Check or Availability Check) -->
<simpleType name="checkFormType">
<restriction base="token">
<enumeration value="claims"/>
<enumeration value="avail"/>
<enumeration value="trademark"/>
</restriction>
</simpleType>
<!-- Type of check form (Claims Check or Availability Check) -->
<simpleType name="checkFormType">
<restriction base="token">
<enumeration value="claims"/>
<enumeration value="avail"/>
<enumeration value="trademark"/>
</restriction>
</simpleType>
<!-- Child elements of info command -->
<complexType name="infoType">
<sequence>
<element
name="phase"
type="launch:phaseType"/>
<element
name="applicationID"
type="launch:applicationIDType"
minOccurs="0"/>
</sequence>
<attribute
name="includeMark"
type="boolean"
default="false"/>
</complexType>
<!-- Child elements of info command -->
<complexType name="infoType">
<sequence>
<element
name="phase"
type="launch:phaseType"/>
<element
name="applicationID"
type="launch:applicationIDType"
minOccurs="0"/>
</sequence>
<attribute
name="includeMark"
type="boolean"
default="false"/>
</complexType>
<!-- Child response elements -->
<element
name="chkData"
type="launch:chkDataType"/>
<element
name="creData"
type="launch:idContainerType"/>
<element
name="infData"
<!-- Child response elements -->
<element
name="chkData"
type="launch:chkDataType"/>
<element
name="creData"
type="launch:idContainerType"/>
<element
name="infData"
type="launch:infDataType"/>
type="launch:infDataType"/>
<!-- <check> response elements -->
<complexType name="chkDataType">
<sequence>
<element
name="phase"
type="launch:phaseType"
minOccurs="0"/>
<element
name="cd"
type="launch:cdType"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<!-- <check> response elements -->
<complexType name="chkDataType">
<sequence>
<element
name="phase"
type="launch:phaseType"
minOccurs="0"/>
<element
name="cd"
type="launch:cdType"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="cdType">
<sequence>
<element
name="name"
type="launch:cdNameType"/>
<element
name="claimKey"
type="launch:claimKeyType"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="cdType">
<sequence>
<element
name="name"
type="launch:cdNameType"/>
<element
name="claimKey"
type="launch:claimKeyType"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="cdNameType">
<simpleContent>
<extension base="eppcom:labelType">
<attribute
name="exists"
type="boolean"
use="required"/>
</extension>
</simpleContent>
</complexType>
<complexType name="cdNameType">
<simpleContent>
<extension base="eppcom:labelType">
<attribute
name="exists"
type="boolean"
use="required"/>
</extension>
</simpleContent>
</complexType>
<complexType name="claimKeyType">
<simpleContent>
<extension base="token">
<attribute
name="validatorID"
type="launch:validatorIDType"
use="optional"/>
</extension>
<complexType name="claimKeyType">
<simpleContent>
<extension base="token">
<attribute
name="validatorID"
type="launch:validatorIDType"
use="optional"/>
</extension>
</simpleContent>
</complexType>
</simpleContent>
</complexType>
<!-- <info> response elements -->
<complexType name="infDataType">
<sequence>
<element
name="phase"
type="launch:phaseType"/>
<element
name="applicationID"
type="launch:applicationIDType"
minOccurs="0"/>
<element
name="status"
type="launch:statusType"
minOccurs="0"/>
<element
ref="mark:abstractMark"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<!-- <info> response elements -->
<complexType name="infDataType">
<sequence>
<element
name="phase"
type="launch:phaseType"/>
<element
name="applicationID"
type="launch:applicationIDType"
minOccurs="0"/>
<element
name="status"
type="launch:statusType"
minOccurs="0"/>
<element
ref="mark:abstractMark"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</complexType>
</schema> END
</schema>END
This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688].
本文档使用URN来描述符合[RFC3688]中描述的注册表机制的XML名称空间和XML模式。
IANA has registered the launch namespace as follows:
IANA已注册启动命名空间，如下所示：
URI: urn:ietf:params:xml:ns:launch-1.0
URI: urn:ietf:params:xml:ns:launch-1.0
Registrant Contact: IESG
注册联系人：IESG
XML: None. Namespace URIs do not represent an XML specification.
XML：没有。命名空间URI不表示XML规范。
IANA has registered the launch XML schema as follows:
IANA已注册启动XML模式，如下所示：
URI: urn:ietf:params:xml:schema:launch-1.0
URI: urn:ietf:params:xml:schema:launch-1.0
Registrant Contact: IESG
注册联系人：IESG
XML: See the "Formal Syntax" section of this document.
XML：请参阅本文档的“正式语法”部分。
IANA has registered the EPP extension described in this document in the "Extensions for the Extensible Provisioning Protocol (EPP)" registry described in [RFC7451]. The details of the registration are as follows:
IANA已在[RFC7451]中所述的“可扩展资源调配协议（EPP）扩展”注册表中注册了本文档中所述的EPP扩展。注册详情如下：
Name of Extension: "Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)"
扩展名：“可扩展资源调配协议（EPP）的启动阶段映射”
Document Status: Standards Track
文档状态：标准跟踪
Reference: RFC 8334
参考：RFC 8334
Registrant Name and Email Address: IESG, <iesg@ietf.org>
Registrant Name and Email Address: IESG, <iesg@ietf.org>
TLDs: Any
TLDs：有吗
IPR Disclosure: None
知识产权披露：无
Status: Active
状态：活动
Notes: None
注：无
The mapping extensions described in this document do not provide any security services beyond those described by EPP [RFC5730], the EPP domain name mapping [RFC5731], and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well.
除EPP[RFC5730]、EPP域名映射[RFC5731]和EPP使用的协议层所述的安全服务外，本文档中描述的映射扩展不提供任何安全服务。这些其他规范中描述的安全注意事项也适用于本规范。
Updates to, and deletion of, an application object MUST be restricted to clients authorized to perform the said operation on the object.
对应用程序对象的更新和删除必须限于授权对该对象执行所述操作的客户端。
Information contained within an application, or even the mere fact that an application exists, may be confidential. Any attempt to operate on an application object by an unauthorized client MUST be rejected with an EPP 2201 (authorization error) return code. Server policy may allow an <info> operation with filtered output by clients
申请中包含的信息，甚至仅仅是申请存在的事实，都可能是机密的。必须使用EPP 2201（授权错误）返回代码拒绝未经授权的客户端对应用程序对象进行操作的任何尝试。服务器策略可能允许对客户端筛选的输出执行<info>操作
other than the sponsoring client, in which case the <domain:infData> and <launch:infData> responses SHOULD be filtered to include only fields that are publicly accessible.
除了发起客户端之外，在这种情况下，<domain:infData>和<launch:infData>响应应该被过滤，以仅包括可公开访问的字段。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-editor.org/info/rfc3688>.
[RFC3688]Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，DOI 10.17487/RFC3688，2004年1月<https://www.rfc-editor.org/info/rfc3688>.
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, September 2009, <https://www.rfc-editor.org/info/rfc5646>.
[RFC5646]Phillips，A.，Ed.和M.Davis，Ed.，“识别语言的标签”，BCP 47，RFC 5646，DOI 10.17487/RFC5646，2009年9月<https://www.rfc-editor.org/info/rfc5646>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, <https://www.rfc-editor.org/info/rfc5730>.
[RFC5730]Hollenbeck，S.，“可扩展资源调配协议（EPP）”，STD 69，RFC 5730，DOI 10.17487/RFC5730，2009年8月<https://www.rfc-editor.org/info/rfc5730>.
[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2009, <https://www.rfc-editor.org/info/rfc5731>.
[RFC5731]Hollenbeck，S.，“可扩展资源调配协议（EPP）域名映射”，STD 69，RFC 5731，DOI 10.17487/RFC5731，2009年8月<https://www.rfc-editor.org/info/rfc5731>.
[RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping", RFC 7848, DOI 10.17487/RFC7848, June 2016, <https://www.rfc-editor.org/info/rfc7848>.
[RFC7848]Lozano，G.“标记和签名标记对象映射”，RFC 7848，DOI 10.17487/RFC7848，2016年6月<https://www.rfc-editor.org/info/rfc7848>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8174]Leiba，B.，“RFC 2119关键词中大写与小写的歧义”，BCP 14，RFC 8174，DOI 10.17487/RFC8174，2017年5月<https://www.rfc-editor.org/info/rfc8174>.
[W3C.REC-xml11-20060816] Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., Yergeau, F., and J. Cowan, "Extensible Markup Language (XML) 1.1 (Second Edition)", World Wide Web Consortium Recommendation REC-xml11-20060816, August 2006, <http://www.w3.org/TR/2006/REC-xml11-20060816>.
[W3C.REC-xml11-20060816]Bray，T.，Paoli，J.，Sperberg McQueen，M.，Maler，E.，Yergeau，F.，和J.Cowan，“可扩展标记语言（XML）1.1（第二版）”，万维网联盟建议REC-xml11-20060816，2006年8月<http://www.w3.org/TR/2006/REC-xml11-20060816>.
[ICANN-TMCH] Lozano, G., "ICANN TMCH functional specifications", Work in Progress, draft-ietf-regext-tmch-func-spec-03, July 2017.
[ICANN-TMCH]Lozano，G.，“ICANN TMCH功能规范”，正在进行的工作，草稿-ietf-regext-TMCH-func-spec-032017年7月。
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, <https://www.rfc-editor.org/info/rfc7451>.
[RFC7451]Hollenbeck，S.，“可扩展供应协议的扩展注册表”，RFC 7451，DOI 10.17487/RFC7451，2015年2月<https://www.rfc-editor.org/info/rfc7451>.
Acknowledgements
致谢
The authors wish to acknowledge the efforts of the leading participants of the Community TMCH Model that led to many of the changes to this document, which include Chris Wright, Jeff Neuman, Jeff Eckhaus, and Will Shorter.
作者希望感谢社区TMCH模型的主要参与者的努力，这些参与者导致了本文件的许多变化，包括Chris Wright、Jeff Neuman、Jeff Eckhaus和Will Shorter。
Special suggestions that have been incorporated into this document were provided by Harald Alvestrand, Ben Campbell, Spencer Dawkins, Jothan Frakes, Keith Gaughan, Seth Goldman, Scott Hollenbeck, Michael Holloway, Jan Jansen, Rubens Kuhl, Mirja Kuehlewind, Warren Kumari, Ben Levac, Gustavo Lozano, Klaus Malorny, Alexander Mayrhofer, Alexey Melnikov, Patrick Mevzek, James Mitchell, Francisco Obispo, Mike O'Connell, Eric Rescorla, Bernhard Reutner-Fischer, Sabrina Tanamal, Trung Tran, Ulrich Wisser, and Sharon Wodjenski.
已纳入本文件的特别建议由Harald Alvestrand、Ben Campbell、Spencer Dawkins、Jothan Frakes、Keith Gaughan、Seth Goldman、Scott Hollenbeck、Michael Holloway、Jan Jansen、Rubens Kuhl、Mirja Kuehlewind、Warren Kumari、Ben Levac、Gustavo Lozano、Klaus Malorny、Alexander Mayrhofer、，阿列克西·梅尔尼科夫、帕特里克·梅夫泽克、詹姆斯·米切尔、弗朗西斯科·奥比斯波、迈克·奥康奈尔、埃里克·雷斯科拉、伯恩哈德·鲁特纳·费舍尔、萨布丽娜·塔纳马尔、特朗·特兰、乌尔里希·维瑟和莎伦·沃坚斯基。
Some of the description of the Trademark Claims Phase was based on the work done by Gustavo Lozano in the ICANN TMCH functional specifications.
商标声明阶段的一些描述基于Gustavo Lozano在ICANN TMCH功能规范中所做的工作。
Authors' Addresses
作者地址
James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 United States of America
James Gould VeriSign，Inc.美国弗吉尼亚州布鲁蒙特路莱斯顿12061号，邮编：20190
Email: jgould@verisign.com
URI: http://www.verisign.com
Email: jgould@verisign.com
URI: http://www.verisign.com
Wil Tan Cloud Registry Suite 32 Seabridge House 377 Kent St Sydney, NSW 2000 Australia
澳大利亚新南威尔士州悉尼肯特街377号Seabridge House 32号Wil Tan Cloud Registry套房，邮编：2000
Phone: +61 414 710899
Email: wil@cloudregistry.net
URI: http://www.cloudregistry.net
Phone: +61 414 710899
Email: wil@cloudregistry.net
URI: http://www.cloudregistry.net
Gavin Brown CentralNic Ltd 35-39 Mooregate London, England EC2R 6AR United Kingdom
加文·布朗中央有限公司35-39摩尔盖特英国伦敦EC2R 6AR英国
Phone: +44 20 33 88 0600
Email: gavin.brown@centralnic.com
URI: https://www.centralnic.com
Phone: +44 20 33 88 0600
Email: gavin.brown@centralnic.com
URI: https://www.centralnic.com