Network Working Group B. Hoeneisen
Request for Comments: 5076 SWITCH
Category: Standards Track December 2007
Network Working Group B. Hoeneisen
Request for Comments: 5076 SWITCH
Category: Standards Track December 2007
ENUM Validation Information Mapping for the Extensible Provisioning Protocol
可扩展资源调配协议的枚举验证信息映射
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Abstract
摘要
This document describes an Extensible Provisioning Protocol (EPP) extension framework for mapping information about the validation process that has been applied for the E.164 number (or number range) that the E.164 Number Mapping (ENUM) domain name is based on. Specified in the Extensible Markup Language (XML), this mapping extends the EPP domain name mapping to provide an additional feature required for the provisioning of ENUM Domain Names.
本文档描述了一个可扩展配置协议（EPP）扩展框架，用于映射有关已应用于E.164数字映射（ENUM）域名所基于的E.164数字（或数字范围）的验证过程的信息。在可扩展标记语言（XML）中指定，此映射扩展了EPP域名映射，以提供提供枚举域名配置所需的附加功能。
Table of Contents
1. Introduction ....................................................2
2. Terminology .....................................................3
3. Requirements ....................................................4
4. Object Attributes ...............................................4
4.1. ENUM Domain Names ..........................................4
4.2. Validation Information Commands ............................4
4.3. Id .........................................................4
4.4. Validation Information .....................................5
4.5. Validation Elements in the Example .........................5
4.5.1. Method Identifier ...................................5
4.5.2. Validation Entity Identifier ........................5
4.5.3. Registrar Identifier ................................5
4.5.4. Execution Date ......................................6
4.5.5. Expiration Date .....................................6
5. EPP Command Mapping .............................................6
5.1. EPP Query Commands .........................................6
5.1.1. EPP <check> Command .................................6
5.1.2. EPP <info> Command ..................................6
5.1.3. EPP <transfer> Command ..............................8
5.2. EPP Transform Commands .....................................9
5.2.1. EPP <create> Command ................................9
5.2.2. EPP <delete> Command ...............................11
5.2.3. EPP <renew> Command ................................11
5.2.4. EPP <transfer> Command .............................13
5.2.5. EPP <update> Command ...............................15
6. Formal Syntax ..................................................16
7. IANA Considerations ............................................21
8. Security Considerations ........................................21
9. Acknowledgements ...............................................22
10. References ....................................................22
10.1. Normative References .....................................22
10.2. Informative References ...................................23
Table of Contents
1. Introduction ....................................................2
2. Terminology .....................................................3
3. Requirements ....................................................4
4. Object Attributes ...............................................4
4.1. ENUM Domain Names ..........................................4
4.2. Validation Information Commands ............................4
4.3. Id .........................................................4
4.4. Validation Information .....................................5
4.5. Validation Elements in the Example .........................5
4.5.1. Method Identifier ...................................5
4.5.2. Validation Entity Identifier ........................5
4.5.3. Registrar Identifier ................................5
4.5.4. Execution Date ......................................6
4.5.5. Expiration Date .....................................6
5. EPP Command Mapping .............................................6
5.1. EPP Query Commands .........................................6
5.1.1. EPP <check> Command .................................6
5.1.2. EPP <info> Command ..................................6
5.1.3. EPP <transfer> Command ..............................8
5.2. EPP Transform Commands .....................................9
5.2.1. EPP <create> Command ................................9
5.2.2. EPP <delete> Command ...............................11
5.2.3. EPP <renew> Command ................................11
5.2.4. EPP <transfer> Command .............................13
5.2.5. EPP <update> Command ...............................15
6. Formal Syntax ..................................................16
7. IANA Considerations ............................................21
8. Security Considerations ........................................21
9. Acknowledgements ...............................................22
10. References ....................................................22
10.1. Normative References .....................................22
10.2. Informative References ...................................23
This document describes a framework for an ENUM [2] validation information mapping for version 1.0 of EPP [3]. This mapping, an extension of the EPP domain name mapping described in [4], is specified using XML 1.0, as described in [5], and XML Schema notation, as described in [6] and [7].
本文档描述了EPP[3]版本1.0的枚举[2]验证信息映射框架。该映射是[4]中描述的EPP域名映射的扩展，使用XML 1.0（如[5]中所述）和XML模式表示法（如[6]和[7]中所述）指定。
The EPP core protocol specification [3] provides a complete description of EPP command and response structures. A thorough understanding of the base protocol specification is necessary to understand the mapping described in this document.
EPP核心协议规范[3]提供了EPP命令和响应结构的完整描述。要理解本文档中描述的映射，必须彻底理解基本协议规范。
ENUM [2] describes how the Domain Name System (DNS) can be used to identify services associated with an E.164 number.
枚举[2]描述了如何使用域名系统（DNS）识别与E.164号码相关的服务。
As described in RFC 4725 [9], usually only the Assignee of the E.164 number (or number range) has the right to register the corresponding ENUM domain name. Therefore, an ENUM validation process has to be applied before the ENUM domain name can be inserted into the DNS. The validation process shall ensure that the holder of the ENUM domain name coincides with the Assignee of the corresponding E.164 number (or number range). However, the details of the ENUM validation methods are beyond the scope of this document.
如RFC 4725[9]所述，通常只有E.164编号（或编号范围）的受让人有权注册相应的ENUM域名。因此，在将枚举域名插入DNS之前，必须应用枚举验证过程。验证过程应确保ENUM域名持有人与相应E.164编号（或编号范围）的受让人一致。但是，枚举验证方法的详细信息超出了本文档的范围。
The EPP extension described in this document specifies a framework for the mapping of information about the ENUM validation process. As the local legislation or the validation procedures may vary, the content of the validation information itself is not part of this specification.
本文档中描述的EPP扩展指定了一个框架，用于映射有关枚举验证过程的信息。由于当地法规或验证程序可能有所不同，验证信息本身的内容不属于本规范的一部分。
However, this document contains a working example (including XML schema) to show how the validation information could look. This example could even be used for a lightweight validation process. In fact, it has been an integral part of the Swiss ENUM trial.
但是，本文档包含一个工作示例（包括XML模式），以显示验证信息的外观。这个例子甚至可以用于轻量级的验证过程。事实上，这是瑞士ENUM试验的一个组成部分。
Using this extension framework, the content of the validation information can be specified according to the local requirements. Such an extension is specified in [10].
使用此扩展框架，可以根据本地需求指定验证信息的内容。[10]中规定了此类扩展。
More background information concerning the validation can be found in RFC 4725 [9], which also describes a typical basic role model for the ENUM registration process.
有关验证的更多背景信息，请参见RFC 4725[9]，其中还描述了枚举注册过程的典型基本角色模型。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [1].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[1]中所述进行解释。
In examples, "C:" represents lines sent by a protocol client and "S:" represents lines returned by a protocol server. Indentation and white space in examples are provided only to illustrate element relationships and are not REQUIRED features of this specification.
在示例中，“C:”表示协议客户端发送的行，“S:”表示协议服务器返回的行。示例中的缩进和空白仅用于说明元素关系，不是本规范所要求的特征。
XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented to develop a conforming implementation.
XML区分大小写。除非另有说明，否则本文档中提供的XML规范和示例必须按照提供的字符大小写进行解释，以开发一致的实现。
The following requirements are the basis for this work:
以下要求是本工作的基础：
1. The design shall allow multiple policies and validation procedures.
1. 设计应允许多种政策和验证程序。
2. It shall be possible to transmit validation information with EPP domain object requests and responses.
2. 应能够通过EPP域对象请求和响应传输验证信息。
3. It shall be possible to add, modify, and remove validation information.
3. 应能够添加、修改和删除验证信息。
4. It shall be possible to retrieve validation information stored in the ENUM Registry.
4. 应能够检索存储在ENUM注册表中的验证信息。
This extension adds additional elements to the EPP domain name mapping [4]. Only new element descriptions are listed here.
此扩展将向EPP域名映射添加其他元素[4]。此处仅列出新元素说明。
An ENUM Domain Name is a representation of an E.164 number that has been translated to conform to domain name syntax as described in the ENUM specification [2].
ENUM域名是E.164编号的表示形式，该编号已翻译为符合ENUM规范[2]中所述的域名语法。
The following commands are defined for handling validation information at the registry:
为在注册表中处理验证信息定义了以下命令：
o add: to add new validation information
o 添加：添加新的验证信息
o rem: to revoke validation information
o rem：撤销验证信息
o chg: to change stored validation information
o 更改：更改存储的验证信息
o inf: to get information about stored validation information
o inf：获取有关存储的验证信息的信息
The "id" attribute, used to identify the validation, is represented in this mapping using a character string. It MUST be unique at least within the same ENUM Domain Name. To ensure uniqueness even after a transfer of an ENUM Domain Name, it is RECOMMENDED that the "id" attribute be unique per ENUM Registry.
用于标识验证的“id”属性在此映射中使用字符串表示。它必须至少在同一枚举域名内是唯一的。为了确保即使在传输枚举域名后也具有唯一性，建议每个枚举注册表的“id”属性都是唯一的。
The "id" attribute, usually assigned by the ENUM Registrar, is required for revoking or changing stored validation information and appears in the Validation Information Command elements (see Section 4.2).
“id”属性通常由枚举注册器分配，用于撤销或更改存储的验证信息，并出现在验证信息命令元素中（参见第4.2节）。
The <validationInfo> element can contain any element containing validation information that is documented adequately. It is represented in this mapping using the XML schema <any> element and therefore, is extensible.
<validationInfo>元素可以包含任何包含充分记录的验证信息的元素。它在这个映射中使用xmlschema<any>元素表示，因此是可扩展的。
The number of <validationInfo> elements permitted per domain object is subject to local policy.
每个域对象允许的<validationInfo>元素数取决于本地策略。
As described above, this document includes an example for a possible content of validation information that is used in the EPP examples throughout this document.
如上所述，本文件包括本文件中EPP示例中使用的验证信息的可能内容示例。
This example is an optional part of this specification, i.e., a fully compliant RFC 5076 implementation does not need to implement this example.
此示例是本规范的可选部分，即完全兼容的RFC 5076实现不需要实现此示例。
The <methodID> element is represented in this mapping using a character string with a maximum length of 63 characters. It contains an identifier for the method used for the validation. As stated in Section 1, the details of the ENUM validation methods are beyond the scope of this document.
<methodID>元素在此映射中使用最大长度为63个字符的字符串表示。它包含用于验证的方法的标识符。如第1节所述，枚举验证方法的详细信息超出了本文件的范围。
The <validationEntityID> element is represented in this mapping using a character string with a length of 3 to 16 characters. It contains an identifier assigned to the ENUM Validation Entity, e.g., by the ENUM Registry.
<validationEntityID>元素在此映射中使用长度为3到16个字符的字符串表示。它包含分配给枚举验证实体的标识符，例如由枚举注册表分配的标识符。
The <registrarID> element is represented in this mapping using a character string with a length of 3 to 16 characters. It contains an identifier assigned to the ENUM Registrar by the ENUM Registry.
<registarid>元素在此映射中使用长度为3到16个字符的字符串表示。它包含由枚举注册表分配给枚举注册器的标识符。
The <executionDate> element, the execution date of the validation, is represented in this mapping using the XML Schema 'date' data type.
<executionDate>元素，即验证的执行日期，在此映射中使用XML模式“date”数据类型表示。
The <expirationDate> element, the expiration date of the validation, is represented in this mapping using the XML Schema 'date' data type.
<expirationDate>元素，即验证的过期日期，在此映射中使用XML模式“date”数据类型表示。
A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [3], and the EPP domain name mapping is described in [4]. The command mappings described here are specifically for use in implementing ENUM validation information provisioning processes via EPP.
EPP语法和语义的详细描述见EPP核心协议规范[3]，EPP域名映射见[4]。这里描述的命令映射专门用于通过EPP实现枚举验证信息供应过程。
Note: Whether or not this extension is included into an EPP request or response depends on local policy. For example, a local Registry policy might require the use of this extension for EPP <create>, <update>, and <info> commands, but not support it for EPP <transfer> and <renew> commands. Therefore, this is beyond the scope of this document.
注意：此扩展是否包含在EPP请求或响应中取决于本地策略。例如，本地注册表策略可能要求对EPP<create>、<update>和<info>命令使用此扩展，但对EPP<transfer>和<renew>命令不支持此扩展。因此，这超出了本文件的范围。
EPP provides three commands to retrieve object information: <check> to determine if an object is known to the server, <info> to retrieve detailed information associated with an object, and <transfer> to retrieve object transfer status information.
EPP提供了三个命令来检索对象信息：<check>来确定服务器是否知道对象，<info>来检索与对象相关的详细信息，<transfer>来检索对象传输状态信息。
This extension does not add any elements to the EPP <check> command or <check> response described in the EPP domain mapping [4].
此扩展不向EPP域映射[4]中描述的EPP<check>命令或<check>响应添加任何元素。
This extension does not add any elements to the EPP <info> command described in the EPP domain mapping [4]. Additional elements are defined for the <info> response.
此扩展不向EPP域映射[4]中描述的EPP<info>命令添加任何元素。为<info>响应定义了其他元素。
When an <info> command has been processed successfully, the EPP
<resData> element MUST contain child elements as described in the EPP
domain mapping [4]. In addition, the EPP <extension> element MUST
contain an <e164val:infData> element that identifies the extension
namespace. The <e164val:infData> element contains one or more
When an <info> command has been processed successfully, the EPP
<resData> element MUST contain child elements as described in the EPP
domain mapping [4]. In addition, the EPP <extension> element MUST
contain an <e164val:infData> element that identifies the extension
namespace. The <e164val:infData> element contains one or more
<e164val:inf> elements, each with an "id" attribute identifying the validation. Each <e164val:inf> element contains an <e164val: validationInfo> element, which contains the validation information as child element.
<e164val:inf>元素，每个元素都有一个标识验证的“id”属性。每个<e164val:inf>元素都包含一个<e164val:validationInfo>元素，该元素包含作为子元素的验证信息。
In the example below, the validation information consists of a <valex:simpleVal> element that identifies the extension namespace. The <valex:simpleVal> element contains the following child elements:
在下面的示例中，验证信息由标识扩展名称空间的<valex:simpleVal>元素组成。<valex:simpleVal>元素包含以下子元素：
o An <e164val:methodID> element that contains an identifier of the validation method.
o 包含验证方法标识符的<e164val:methodID>元素。
o An OPTIONAL <e164val:validationEntityID> element that contains an identifier assigned to the ENUM Validation Entity.
o 可选的<e164val:validationEntityID>元素，包含分配给枚举验证实体的标识符。
o An OPTIONAL <e164val:registrarID> element that contains an identifier assigned to the ENUM Registrar by the ENUM Registry.
o 可选的<e164val:registerid>元素，包含枚举注册表分配给枚举注册器的标识符。
o An <e164val:executionDate> element that contains the date that the validation was performed.
o 包含执行验证日期的<e164val:executionDate>元素。
o An OPTIONAL <e164val:expirationDate> element that contains the date that the validation expires.
o 可选的<e164val:expirationDate>元素，包含验证过期的日期。
Example for <info> response:
<info>响应示例：
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
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>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="ok"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns2.example.com</domain:hostObj>
S: </domain:ns>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
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>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="ok"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns2.example.com</domain:hostObj>
S: </domain:ns>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:upID>ClientX</domain:upID>
S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate>
S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <e164val:infData
S: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
S: <e164val:inf id="EK77">
S: <e164val:validationInfo>
S: <valex:simpleVal
S: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
S: <valex:methodID>Validation-X</valex:methodID>
S: <valex:validationEntityID>VE-NMQ</valex:validationEntityID>
S: <valex:registrarID>Client-X</valex:registrarID>
S: <valex:executionDate>2004-04-08</valex:executionDate>
S: <valex:expirationDate>2004-10-07</valex:expirationDate>
S: </valex:simpleVal>
S: </e164val:validationInfo>
S: </e164val:inf>
S: </e164val:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-23456</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:upID>ClientX</domain:upID>
S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate>
S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <e164val:infData
S: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
S: <e164val:inf id="EK77">
S: <e164val:validationInfo>
S: <valex:simpleVal
S: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
S: <valex:methodID>Validation-X</valex:methodID>
S: <valex:validationEntityID>VE-NMQ</valex:validationEntityID>
S: <valex:registrarID>Client-X</valex:registrarID>
S: <valex:executionDate>2004-04-08</valex:executionDate>
S: <valex:expirationDate>2004-10-07</valex:expirationDate>
S: </valex:simpleVal>
S: </e164val:validationInfo>
S: </e164val:inf>
S: </e164val:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-23456</clTRID>
S: <svTRID>54321-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
Figure 1
图1
This extension does not add any elements to the EPP <transfer> command or <transfer> response described in the EPP domain mapping [4].
此扩展不向EPP域映射[4]中描述的EPP<transfer>命令或<transfer>响应添加任何元素。
EPP provides five commands to transform objects: <create> to create an instance of an object, <delete> to delete an instance of an object, <renew> to extend the validity period of an object, <transfer> to manage object sponsorship changes, and <update> to change information associated with an object.
EPP提供了五个转换对象的命令：<create>创建对象实例，<delete>删除对象实例，<renew>延长对象有效期，<transfer>管理对象更改，以及<update>更改与对象关联的信息。
This extension defines additional elements for the EPP <create> command described in the EPP domain mapping [4]. No additional elements are defined for the EPP <create> response.
此扩展为EPP域映射[4]中描述的EPP<create>命令定义了其他元素。没有为EPP<create>响应定义其他元素。
The EPP <create> command provides a transform operation that allows a client to create a domain object. In addition to the EPP command elements described in the EPP domain mapping [4], the command MUST contain an <extension> element. The <extension> element MUST contain an <e164val:create> element that identifies the extension namespace. The <e164val:create> element contains one or more <e164val:add> elements, each with an "id" attribute identifying the validation. Each <e164val:add> element contains an <e164val:validationInfo> element, which contains the validation information as child element.
EPP<create>命令提供一个转换操作，允许客户端创建域对象。除了EPP域映射[4]中描述的EPP命令元素外，该命令还必须包含<extension>元素。<extension>元素必须包含标识扩展命名空间的<e164val:create>元素。<e164val:create>元素包含一个或多个<e164val:add>元素，每个元素都具有标识验证的“id”属性。每个<e164val:add>元素都包含一个<e164val:validationInfo>元素，该元素包含作为子元素的验证信息。
In the example below, the validation information consists of a <valex:simpleVal> element that identifies the extension namespace. The <valex:simpleVal> element contains the following child elements:
在下面的示例中，验证信息由标识扩展名称空间的<valex:simpleVal>元素组成。<valex:simpleVal>元素包含以下子元素：
o An <e164val:methodID> element that contains an identifier of the validation method.
o 包含验证方法标识符的<e164val:methodID>元素。
o An OPTIONAL <e164val:validationEntityID> element that contains an identifier assigned to the ENUM Validation Entity.
o 可选的<e164val:validationEntityID>元素，包含分配给枚举验证实体的标识符。
o An OPTIONAL <e164val:registrarID> element that contains an identifier assigned to the ENUM Registrar by the ENUM Registry.
o 可选的<e164val:registerid>元素，包含枚举注册表分配给枚举注册器的标识符。
o An <e164val:executionDate> element that contains the date that the validation was performed.
o 包含执行验证日期的<e164val:executionDate>元素。
o An OPTIONAL <e164val:expirationDate> element that contains the date that the validation expires.
o 可选的<e164val:expirationDate>元素，包含验证过期的日期。
Example for <create> command:
<create>命令示例：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
C: <command>
C: <create>
C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
C: <domain:period unit="y">1</domain:period>
C: <domain:ns>
C: <domain:hostObj>ns1.example.com</domain:hostObj>
C: <domain:hostObj>ns2.example.com</domain:hostObj>
C: </domain:ns>
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: <e164val:create
C: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
C: <e164val:add id="EK77">
C: <e164val:validationInfo>
C: <valex:simpleVal
C: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
C: <valex:methodID>Validation-X</valex:methodID>
C: <valex:validationEntityID>VE-NMQ</valex:validationEntityID>
C: <valex:registrarID>Client-X</valex:registrarID>
C: <valex:executionDate>2004-04-08</valex:executionDate>
C: <valex:expirationDate>2004-10-07</valex:expirationDate>
C: </valex:simpleVal>
C: </e164val:validationInfo>
C: </e164val:add>
C: </e164val: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: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
C: <command>
C: <create>
C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
C: <domain:period unit="y">1</domain:period>
C: <domain:ns>
C: <domain:hostObj>ns1.example.com</domain:hostObj>
C: <domain:hostObj>ns2.example.com</domain:hostObj>
C: </domain:ns>
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: <e164val:create
C: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
C: <e164val:add id="EK77">
C: <e164val:validationInfo>
C: <valex:simpleVal
C: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
C: <valex:methodID>Validation-X</valex:methodID>
C: <valex:validationEntityID>VE-NMQ</valex:validationEntityID>
C: <valex:registrarID>Client-X</valex:registrarID>
C: <valex:executionDate>2004-04-08</valex:executionDate>
C: <valex:expirationDate>2004-10-07</valex:expirationDate>
C: </valex:simpleVal>
C: </e164val:validationInfo>
C: </e164val:add>
C: </e164val:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
Figure 2
图2
When an extended <create> command has been processed successfully, the EPP response is as described in the EPP domain mapping [4].
成功处理扩展的<create>命令后，EPP响应如EPP域映射[4]中所述。
This extension does not add any elements to the EPP <delete> command or <delete> response described in the EPP domain mapping [4].
此扩展不向EPP域映射[4]中描述的EPP<delete>命令或<delete>响应添加任何元素。
This extension defines additional elements for the EPP <renew> command described in the EPP domain mapping [4]. No additional elements are defined for the EPP <renew> response.
此扩展为EPP域映射[4]中描述的EPP<renew>命令定义了其他元素。没有为EPP<renew>响应定义其他元素。
The EPP <renew> command provides a transform operation that allows a client to extend the validity period of a domain object. In addition to the EPP command elements described in the EPP domain mapping [4], the <renew> command MUST contain an <extension> element. The <extension> element MUST contain an <e164val:renew> element that identifies the extension namespace. The <e164val:renew> element contains one or more <e164val:add> elements, each with an "id" attribute identifying the validation. Each <e164val:add> element contains an <e164val:validationInfo> element, which contains the validation information as child element.
EPP<renew>命令提供转换操作，允许客户端延长域对象的有效期。除了EPP域映射[4]中描述的EPP命令元素外，<renew>命令必须包含<extension>元素。<extension>元素必须包含标识扩展命名空间的<e164val:renew>元素。<e164val:renew>元素包含一个或多个<e164val:add>元素，每个元素都具有标识验证的“id”属性。每个<e164val:add>元素都包含一个<e164val:validationInfo>元素，该元素包含作为子元素的验证信息。
In the example below, the validation information consists of a <valex:simpleVal> element that identifies the extension namespace. The <valex:simpleVal> contains the following child elements:
在下面的示例中，验证信息由标识扩展名称空间的<valex:simpleVal>元素组成。<valex:simpleVal>包含以下子元素：
o An <e164val:methodID> element that contains an identifier of the validation method.
o 包含验证方法标识符的<e164val:methodID>元素。
o An OPTIONAL <e164val:validationEntityID> element that contains an identifier assigned to the ENUM Validation Entity.
o 可选的<e164val:validationEntityID>元素，包含分配给枚举验证实体的标识符。
o An OPTIONAL <e164val:registrarID> element that contains an identifier assigned to the ENUM Registrar by the ENUM Registry.
o 可选的<e164val:registerid>元素，包含枚举注册表分配给枚举注册器的标识符。
o An <e164val:executionDate> element that contains the date that the validation was performed.
o 包含执行验证日期的<e164val:executionDate>元素。
o An OPTIONAL <e164val:expirationDate> element that contains the date that the validation expires.
o 可选的<e164val:expirationDate>元素，包含验证过期的日期。
Example for <renew> command:
<renew>命令示例：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
C: <command>
C: <renew>
C: <domain:renew
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
C: <domain:curExpDate>2005-04-09</domain:curExpDate>
C: <domain:period unit="y">1</domain:period>
C: </domain:renew>
C: </renew>
C: <extension>
C: <e164val:renew
C: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
C: <e164val:add id="CAB176">
C: <e164val:validationInfo>
C: <valex:simpleVal
C: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
C: <valex:methodID>Validation-X</valex:methodID>
C: <valex:validationEntityID>VE-NMQ</valex:validationEntityID>
C: <valex:registrarID>Client-X</valex:registrarID>
C: <valex:executionDate>2005-03-30</valex:executionDate>
C: <valex:expirationDate>2005-09-29</valex:expirationDate>
C: </valex:simpleVal>
C: </e164val:validationInfo>
C: </e164val:add>
C: </e164val:renew>
C: </extension>
C: <clTRID>ABC-45678</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: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
C: <command>
C: <renew>
C: <domain:renew
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
C: <domain:curExpDate>2005-04-09</domain:curExpDate>
C: <domain:period unit="y">1</domain:period>
C: </domain:renew>
C: </renew>
C: <extension>
C: <e164val:renew
C: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
C: <e164val:add id="CAB176">
C: <e164val:validationInfo>
C: <valex:simpleVal
C: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
C: <valex:methodID>Validation-X</valex:methodID>
C: <valex:validationEntityID>VE-NMQ</valex:validationEntityID>
C: <valex:registrarID>Client-X</valex:registrarID>
C: <valex:executionDate>2005-03-30</valex:executionDate>
C: <valex:expirationDate>2005-09-29</valex:expirationDate>
C: </valex:simpleVal>
C: </e164val:validationInfo>
C: </e164val:add>
C: </e164val:renew>
C: </extension>
C: <clTRID>ABC-45678</clTRID>
C: </command>
C:</epp>
Figure 3
图3
When an extended <renew> command has been processed successfully, the EPP response is as described in the EPP domain mapping [4].
成功处理扩展的<renew>命令后，EPP响应如EPP域映射[4]中所述。
This extension defines additional elements for the EPP <transfer> command described in the EPP domain mapping [4]. No additional elements are defined for the EPP <transfer> response.
此扩展为EPP域映射[4]中描述的EPP<transfer>命令定义了其他元素。没有为EPP<transfer>响应定义其他元素。
The EPP <transfer> command provides a transform operation that allows a client to manage requests to transfer the sponsorship of a domain object. Clients can initiate, cancel, approve, and reject a transfer request.
EPP<transfer>命令提供了一个转换操作，该操作允许客户端管理传输域对象赞助的请求。客户可以发起、取消、批准和拒绝转账请求。
In case of a transfer request, in addition to the EPP command elements described in the EPP domain mapping [4], the command MUST contain an <extension> element. The <extension> element MUST contain an <e164val:transfer> element that identifies the extension namespace. The <e164val:transfer> element contains one or more <e164val:add> elements, each with an "id" attribute identifying the validation. Each <e164val:add> element contains an <e164val: validationInfo> element, which contains the validation information as child element.
在传输请求的情况下，除了EPP域映射[4]中描述的EPP命令元素外，该命令还必须包含<extension>元素。<extension>元素必须包含标识扩展命名空间的<e164val:transfer>元素。<e164val:transfer>元素包含一个或多个<e164val:add>元素，每个元素都具有标识验证的“id”属性。每个<e164val:add>元素都包含一个<e164val:validationInfo>元素，该元素包含作为子元素的验证信息。
In the example below, the validation information consists of a <valex:simpleVal> element that identifies the extension namespace. The <valex:simpleVal> contains the following child elements:
在下面的示例中，验证信息由标识扩展名称空间的<valex:simpleVal>元素组成。<valex:simpleVal>包含以下子元素：
o An <e164val:methodID> element that contains an identifier of the validation method.
o 包含验证方法标识符的<e164val:methodID>元素。
o An OPTIONAL <e164val:validationEntityID> element that contains an identifier assigned to the ENUM Validation Entity.
o 可选的<e164val:validationEntityID>元素，包含分配给枚举验证实体的标识符。
o An OPTIONAL <e164val:registrarID> element that contains an identifier assigned to the ENUM Registrar by the ENUM Registry.
o 可选的<e164val:registerid>元素，包含枚举注册表分配给枚举注册器的标识符。
o An <e164val:executionDate> element that contains the date that the validation was performed.
o 包含执行验证日期的<e164val:executionDate>元素。
o An OPTIONAL <e164val:expirationDate> element that contains the date that the validation expires.
o 可选的<e164val:expirationDate>元素，包含验证过期的日期。
Example for <transfer> command:
<transfer>命令的示例：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
C: <command>
C: <transfer op="request">
C: <domain:transfer
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
C: <domain:authInfo>
C: <domain:pw roid="HB1973-ZUE">2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:transfer>
C: </transfer>
C: <extension>
C: <e164val:transfer
C: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
C: <e164val:add id="LJ1126">
C: <e164val:validationInfo>
C: <valex:simpleVal
C: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
C: <valex:methodID>Validation-Y</valex:methodID>
C: <valex:validationEntityID>VE2-LMQ</valex:validationEntityID>
C: <valex:registrarID>Client-Y</valex:registrarID>
C: <valex:executionDate>2005-01-22</valex:executionDate>
C: <valex:expirationDate>2005-07-21</valex:expirationDate>
C: </valex:simpleVal>
C: </e164val:validationInfo>
C: </e164val:add>
C: </e164val:transfer>
C: </extension>
C: <clTRID>XYZ-54789</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: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
C: <command>
C: <transfer op="request">
C: <domain:transfer
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
C: <domain:authInfo>
C: <domain:pw roid="HB1973-ZUE">2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:transfer>
C: </transfer>
C: <extension>
C: <e164val:transfer
C: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
C: <e164val:add id="LJ1126">
C: <e164val:validationInfo>
C: <valex:simpleVal
C: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
C: <valex:methodID>Validation-Y</valex:methodID>
C: <valex:validationEntityID>VE2-LMQ</valex:validationEntityID>
C: <valex:registrarID>Client-Y</valex:registrarID>
C: <valex:executionDate>2005-01-22</valex:executionDate>
C: <valex:expirationDate>2005-07-21</valex:expirationDate>
C: </valex:simpleVal>
C: </e164val:validationInfo>
C: </e164val:add>
C: </e164val:transfer>
C: </extension>
C: <clTRID>XYZ-54789</clTRID>
C: </command>
C:</epp>
Figure 4
图4
When an extended <transfer> command has been processed successfully, the EPP response is as described in the EPP domain mapping [4].
成功处理扩展的<transfer>命令后，EPP响应如EPP域映射[4]中所述。
This extension defines additional elements for the EPP <update> command described in the EPP domain mapping [4]. No additional elements are defined for the EPP <update> response. The EPP <update> command provides a transform operation that allows a client to change the state of a domain object. In addition to the EPP command elements described in the EPP domain mapping [4], the <update> command MUST contain an <extension> element. The <extension> element MUST contain an <e164val:update> element that identifies the extension namespace. The <e164val:update> element contains one or more <e164val:add>, <e164val:rem>, or <e164val:chg> elements, each with an "id" attribute identifying the validation. Each <e164val:add> and <e164val:chg> element contains an <e164val: validationInfo> element, which contains the validation information as child element. <e164val:rem> elements do not have child elements.
此扩展为EPP域映射[4]中描述的EPP<update>命令定义了其他元素。没有为EPP<update>响应定义其他元素。EPP<update>命令提供转换操作，允许客户端更改域对象的状态。除了EPP域映射[4]中描述的EPP命令元素外，<update>命令必须包含<extension>元素。<extension>元素必须包含标识扩展命名空间的<e164val:update>元素。<e164val:update>元素包含一个或多个<e164val:add>、<e164val:rem>或<e164val:chg>元素，每个元素都具有标识验证的“id”属性。每个<e164val:add>和<e164val:chg>元素都包含一个<e164val:validationInfo>元素，该元素包含作为子元素的验证信息<e164val:rem>元素没有子元素。
In the example below, the validation information consists of a <valex:simpleVal> element that identifies the extension namespace. The <valex:simpleVal> contains the following child elements:
在下面的示例中，验证信息由标识扩展名称空间的<valex:simpleVal>元素组成。<valex:simpleVal>包含以下子元素：
o An <e164val:methodID> element that contains an identifier of the validation method.
o 包含验证方法标识符的<e164val:methodID>元素。
o An OPTIONAL <e164val:validationEntityID> element that contains an identifier assigned to the ENUM Validation Entity.
o 可选的<e164val:validationEntityID>元素，包含分配给枚举验证实体的标识符。
o An OPTIONAL <e164val:registrarID> element that contains an identifier assigned to the ENUM Registrar by the ENUM Registry.
o 可选的<e164val:registerid>元素，包含枚举注册表分配给枚举注册器的标识符。
o An <e164val:executionDate> element that contains the date that the validation was performed.
o 包含执行验证日期的<e164val:executionDate>元素。
o An OPTIONAL <e164val:expirationDate> element that contains the date that the validation expires.
o 可选的<e164val:expirationDate>元素，包含验证过期的日期。
Example for <update> command:
<update>命令的示例：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
C: </domain:update>
C: </update>
C: <extension>
C: <e164val:update
C: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
C: <e164val:add id="EK2510">
C: <e164val:validationInfo>
C: <valex:simpleVal
C: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
C: <valex:methodID>Validation-X</valex:methodID>
C: <valex:validationEntityID>VE-NMQ</valex:validationEntityID>
C: <valex:registrarID>Client-X</valex:registrarID>
C: <valex:executionDate>2004-10-02</valex:executionDate>
C: <valex:expirationDate>2005-04-01</valex:expirationDate>
C: </valex:simpleVal>
C: </e164val:validationInfo>
C: </e164val:add>
C: <e164val:rem id="EK77"/>
C: </e164val:update>
C: </extension>
C: <clTRID>ABC-34567</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: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>5.1.5.1.8.6.2.4.4.1.4.e164.arpa</domain:name>
C: </domain:update>
C: </update>
C: <extension>
C: <e164val:update
C: xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0">
C: <e164val:add id="EK2510">
C: <e164val:validationInfo>
C: <valex:simpleVal
C: xmlns:valex="urn:ietf:params:xml:ns:e164valex-1.1">
C: <valex:methodID>Validation-X</valex:methodID>
C: <valex:validationEntityID>VE-NMQ</valex:validationEntityID>
C: <valex:registrarID>Client-X</valex:registrarID>
C: <valex:executionDate>2004-10-02</valex:executionDate>
C: <valex:expirationDate>2005-04-01</valex:expirationDate>
C: </valex:simpleVal>
C: </e164val:validationInfo>
C: </e164val:add>
C: <e164val:rem id="EK77"/>
C: </e164val:update>
C: </extension>
C: <clTRID>ABC-34567</clTRID>
C: </command>
C:</epp>
Figure 5
图5
When an extended <update> command has been processed successfully, the EPP response is as described in the EPP domain mapping [4].
成功处理扩展的<update>命令后，EPP响应如EPP域映射[4]中所述。
An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schemas; they are used to note the beginning and ending of the schema for URI registration purposes.
EPP对象映射是用XML模式表示法指定的。这里给出的形式语法是对象映射的完整模式表示，适合于自动验证EPP XML实例。开始和结束标记不是模式的一部分；它们用于记录模式的开始和结束，以便进行URI注册。
Formal syntax for Framework:
框架的形式语法：
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:e164val-1.0"
xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-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:e164val-1.0"
xmlns:e164val="urn:ietf:params:xml:ns:e164val-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!--
Import common element types.
-->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd"/>
<!--
Import common element types.
-->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd"/>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name extension schema for framework for
provisioning of E.164 number validation information.
</documentation>
</annotation>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name extension schema for framework for
provisioning of E.164 number validation information.
</documentation>
</annotation>
<!--
Child elements found in EPP commands.
-->
<element name="create" type="e164val:insertType"/>
<element name="update" type="e164val:updateType"/>
<element name="renew" type="e164val:insertType"/>
<element name="transfer" type="e164val:insertType"/>
<!--
Child elements found in EPP commands.
-->
<element name="create" type="e164val:insertType"/>
<element name="update" type="e164val:updateType"/>
<element name="renew" type="e164val:insertType"/>
<element name="transfer" type="e164val:insertType"/>
<!--
Child elements of the <create>, <renew>, and <update> commands.
-->
<complexType name="insertType">
<sequence>
<element name="add" type="e164val:addType"
maxOccurs="unbounded" />
</sequence>
</complexType>
<!--
Child elements of the <create>, <renew>, and <update> commands.
-->
<complexType name="insertType">
<sequence>
<element name="add" type="e164val:addType"
maxOccurs="unbounded" />
</sequence>
</complexType>
<!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="add" type="e164val:addType"
<!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="add" type="e164val:addType"
minOccurs="0"
maxOccurs="unbounded"/>
<element name="rem" type="e164val:remType"
minOccurs="0"
maxOccurs="unbounded"/>
<element name="chg" type="e164val:chgType"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</complexType>
minOccurs="0"
maxOccurs="unbounded"/>
<element name="rem" type="e164val:remType"
minOccurs="0"
maxOccurs="unbounded"/>
<element name="chg" type="e164val:chgType"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Data elements for add, chg and rem.
-->
<complexType name="addType">
<sequence>
<element ref="e164val:validationInfo"/>
</sequence>
<attribute name="id" type="eppcom:minTokenType"
use="required"/>
</complexType>
<!--
Data elements for add, chg and rem.
-->
<complexType name="addType">
<sequence>
<element ref="e164val:validationInfo"/>
</sequence>
<attribute name="id" type="eppcom:minTokenType"
use="required"/>
</complexType>
<complexType name="chgType">
<sequence>
<element ref="e164val:validationInfo"/>
</sequence>
<attribute name="id" type="eppcom:minTokenType"
use="required"/>
</complexType>
<complexType name="chgType">
<sequence>
<element ref="e164val:validationInfo"/>
</sequence>
<attribute name="id" type="eppcom:minTokenType"
use="required"/>
</complexType>
<complexType name="remType">
<attribute name="id" type="eppcom:minTokenType"
use="required"/>
</complexType>
<complexType name="remType">
<attribute name="id" type="eppcom:minTokenType"
use="required"/>
</complexType>
<!--
Child elements found in EPP responses
-->
<element name="infData" type="e164val:infDataType"/>
<!--
Child elements found in EPP responses
-->
<element name="infData" type="e164val:infDataType"/>
<!--
child elements of the <info> response.
-->
<complexType name="infDataType">
<sequence>
<element name="inf" type="e164val:infType"
minOccurs="0"
<!--
child elements of the <info> response.
-->
<complexType name="infDataType">
<sequence>
<element name="inf" type="e164val:infType"
minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</complexType>
maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Data elements for inf
-->
<complexType name="infType">
<sequence>
<element ref="e164val:validationInfo"/>
</sequence>
<attribute name="id" type="eppcom:minTokenType"
use="required"/>
</complexType>
<!--
Data elements for inf
-->
<complexType name="infType">
<sequence>
<element ref="e164val:validationInfo"/>
</sequence>
<attribute name="id" type="eppcom:minTokenType"
use="required"/>
</complexType>
<!--
Global elements.
-->
<element name="validationInfo" type="e164val:ValidationInfoType" />
<!--
Global elements.
-->
<element name="validationInfo" type="e164val:ValidationInfoType" />
<!--
Extension framework types.
-->
<complexType name="ValidationInfoType">
<sequence>
<any namespace="##other"/>
</sequence>
</complexType>
<!--
Extension framework types.
-->
<complexType name="ValidationInfoType">
<sequence>
<any namespace="##other"/>
</sequence>
</complexType>
<!-- End of schema. --> </schema> END
<!-- 架构结束。--></架构>结束
Figure 6
图6
Formal syntax for a simple validation (example):
用于简单验证的正式语法（示例）：
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:e164valex-1.1"
xmlns:e164valex="urn:ietf:params:xml:ns:e164valex-1.1"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-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:e164valex-1.1"
xmlns:e164valex="urn:ietf:params:xml:ns:e164valex-1.1"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!--
Import common element types.
-->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd"/>
<!--
Import common element types.
-->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
schemaLocation="eppcom-1.0.xsd"/>
<annotation>
<documentation>
Example for E.164 number validation information.
</documentation>
</annotation>
<annotation>
<documentation>
Example for E.164 number validation information.
</documentation>
</annotation>
<element name="simpleVal" type="e164valex:simpleValType"/>
<element name="simpleVal" type="e164valex:simpleValType"/>
<complexType name="simpleValType">
<sequence>
<element name="methodID" type="e164valex:methodIdType"/>
<element name="validationEntityID" type="eppcom:clIDType"
minOccurs="0"/>
<element name="registrarID" type="eppcom:clIDType"
minOccurs="0"/>
<element name="executionDate" type="date"/>
<element name="expirationDate" type="date"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="simpleValType">
<sequence>
<element name="methodID" type="e164valex:methodIdType"/>
<element name="validationEntityID" type="eppcom:clIDType"
minOccurs="0"/>
<element name="registrarID" type="eppcom:clIDType"
minOccurs="0"/>
<element name="executionDate" type="date"/>
<element name="expirationDate" type="date"
minOccurs="0"/>
</sequence>
</complexType>
<simpleType name="methodIdType">
<restriction base="token">
<minLength value="1"/>
<maxLength value="63"/>
</restriction>
</simpleType>
<simpleType name="methodIdType">
<restriction base="token">
<minLength value="1"/>
<maxLength value="63"/>
</restriction>
</simpleType>
<!-- End of schema. --> </schema> END
<!-- 架构结束。--></架构>结束
Figure 7
图7
This document uses Uniform Resource Names (URNs) to describe XML namespaces and XML schemas conforming to the registry mechanism described in RFC 3688 [8]. Four URI assignments have been made:
本文档使用统一资源名（URN）来描述符合RFC 3688[8]中描述的注册表机制的XML名称空间和XML模式。已分配了四个URI：
1. Registration for the extension namespace: * URI: urn:ietf:params:xml:ns:e164val-1.0 * Registrant Contact: See the "Author's Address" section of this document. * XML: None. Namespace URIs do not represent an XML specification.
1. 注册扩展命名空间：*URI:urn:ietf:params:xml:ns:e164val-1.0*注册人联系人：请参阅本文档的“作者地址”部分。*XML：没有。命名空间URI不表示XML规范。
2. Registration for the extension XML schema: * URI: urn:ietf:params:xml:schema:e164val-1.0 * Registrant Contact: See the "Author's Address" section of this document. * XML: See Section 6, "Formal Syntax", of this document.
2. 注册扩展XML架构：*URI:urn:ietf:params:XML:schema:e164val-1.0*注册人联系人：请参阅本文档的“作者地址”部分。*XML：参见本文档第6节“形式语法”。
3. Registration for the extension namespace: * URI: urn:ietf:params:xml:ns:e164valex-1.1 * Registrant Contact: See the "Author's Address" section of this document. * XML: None. Namespace URIs do not represent an XML specification.
3. 注册扩展命名空间：*URI:urn:ietf:params:xml:ns:e164valex-1.1*注册人联系人：请参阅本文档的“作者地址”部分。*XML：没有。命名空间URI不表示XML规范。
4. Registration for the extension XML schema: * URI: urn:ietf:params:xml:schema:e164valex-1.1 * Registrant Contact: See the "Author's Address" section of this document. * XML: See Section 6, "Formal Syntax", of this document.
4. 注册扩展XML架构：*URI:urn:ietf:params:XML:schema:e164valex-1.1*注册人联系人：请参阅本文档的“作者地址”部分。*XML：参见本文档第6节“形式语法”。
The mapping extensions described in this document do not provide any security services beyond those described by EPP [3], the EPP domain name mapping [4], and protocol layers used by EPP. Security considerations related to ENUM are described in the "Security Considerations" section of the ENUM specification [2]. The security considerations described in these other specifications apply to this specification as well.
本文档中描述的映射扩展不提供EPP[3]、EPP域名映射[4]和EPP使用的协议层之外的任何安全服务。ENUM规范[2]的“安全注意事项”部分描述了与ENUM相关的安全注意事项。这些其他规范中描述的安全注意事项也适用于本规范。
Validation information often contains sensitive personal information. It is RECOMMENDED that validation information in the <info> response is only provided to the sponsoring client.
验证信息通常包含敏感的个人信息。建议仅向赞助客户提供<info>响应中的验证信息。
The author would like to thank the following people who have provided feedback or significant contributions to the development of this document: Alfred Hoenes, Helena Malmborg, Alexander Mayrhofer, Andrew Newton, Marcel Parodi, Patrik Schaefer, and Patrick Zenklusen.
作者要感谢以下为本文件的编写提供反馈或重大贡献的人士：阿尔弗雷德·霍恩斯、海伦娜·马尔姆博格、亚历山大·梅尔霍夫、安德鲁·牛顿、马塞尔·帕罗迪、帕特里克·谢弗和帕特里克·曾克卢森。
RFC 4114 [11] has been used as a template for this document. The structure and those paragraphs that apply to both documents have been taken over from [11]. The author would like to thank Scott Hollenbeck for this great spadework.
RFC 4114[11]已被用作本文件的模板。适用于这两份文件的结构和段落已由[11]取代。作者要感谢Scott Hollenbeck所做的这项伟大的工作。
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004.
[2] Faltstrom，P.和M.Mealling，“E.164到统一资源标识符（URI）动态委托发现系统（DDDS）应用程序（ENUM）”，RFC 3761，2004年4月。
[3] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", RFC 3730, March 2004.
[3] Hollenbeck，S.，“可扩展资源调配协议（EPP）”，RFC3730，2004年3月。
[4] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", RFC 3731, March 2004.
[4] Hollenbeck，S.，“可扩展供应协议（EPP）域名映射”，RFC 37312004年3月。
[5] Paoli, J., Maler, E., Bray, T., and C. Sperberg-McQueen, "Extensible Markup Language (XML) 1.0 (Second Edition)", World Wide Web Consortium FirstEdition REC-xml-20001006, October 2000, <http://www.w3.org/TR/2000/REC-xml-20001006>.
[5] Paoli，J.，Maler，E.，Bray，T.，和C.Sperberg McQueen，“可扩展标记语言（XML）1.0（第二版）”，万维网联盟第一版REC-XML-20001006，2000年10月<http://www.w3.org/TR/2000/REC-xml-20001006>.
[6] Thompson, H., Maloney, M., Mendelsohn, N., and D. Beech, "XML Schema Part 1: Structures Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-1-20041028, October 2004, <http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
[6] Thompson，H.，Maloney，M.，Mendelsohn，N.，和D.Beech，“XML模式第1部分：结构第二版”，万维网联盟建议REC-xmlschema-1-20041028，2004年10月<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
[7] Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-2-20041028, October 2004, <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
[7] Biron，P.和A.Malhotra，“XML模式第2部分：数据类型第二版”，万维网联盟建议REC-xmlschema-2-20041028，2004年10月<http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.
[8] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[8] Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[9] Mayrhofer, A. and B. Hoeneisen, "ENUM Validation Architecture", RFC 4725, November 2006.
[9] Mayrhofer，A.和B.Hoeneisen，“枚举验证体系结构”，RFC 47252006年11月。
[10] Lendl, O., "ENUM Validation Token Format Definition", Work in Progress.
[10] Lendl，O.，“枚举验证令牌格式定义”，正在进行中。
[11] Hollenbeck, S., "E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)", RFC 4114, June 2005.
[11] Hollenbeck，S.，“可扩展供应协议（EPP）的E.164数字映射”，RFC 4114，2005年6月。
Author's Address
作者地址
Bernie Hoeneisen SWITCH Werdstrasse 2 CH-8004 Zuerich Switzerland
Bernie Hoeneisen SWITCH Werdstrasse 2 CH-8004 Zuerich SWITCH瑞士
Phone: +41 44 268 1515
EMail: bernhard.hoeneisen@switch.ch, bernie@ietf.hoeneisen.ch
URI: http://www.switch.ch/
Phone: +41 44 268 1515
EMail: bernhard.hoeneisen@switch.ch, bernie@ietf.hoeneisen.ch
URI: http://www.switch.ch/
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.