Network Working Group S. Hollenbeck
Request for Comments: 4114 VeriSign, Inc.
Category: Standards Track June 2005
Network Working Group S. Hollenbeck
Request for Comments: 4114 VeriSign, Inc.
Category: Standards Track June 2005
E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)
E.164可扩展资源调配协议（EPP）的编号映射
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of E.164 numbers that represent domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of E.164 numbers.
本文档描述了可扩展资源调配协议（EPP）扩展映射，用于调配和管理代表存储在共享中央存储库中的域名的E.164号。在XML中指定，此映射扩展了EPP域名映射，以提供提供E.164号码所需的其他功能。
Table of Contents
目录
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. E.164 Domain Names . . . . . . . . . . . . . . . . . . . . 3
2.2. NAPTR Fields . . . . . . . . . . . . . . . . . . . . . . . 3
2.2.1. Order . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.2. Preference. . . . . . . . . . . . . . . . . . . . . 4
2.2.3. Flags . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.4. Service . . . . . . . . . . . . . . . . . . . . . . 4
2.2.5. Regular Expression. . . . . . . . . . . . . . . . . 4
2.2.6. Replacement . . . . . . . . . . . . . . . . . . . . 4
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . . 4
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 5
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . 5
3.1.2. EPP <info> Command. . . . . . . . . . . . . . . . . 5
3.1.3. EPP <transfer> Command. . . . . . . . . . . . . . . 7
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 7
3.2.1. EPP <create> Command. . . . . . . . . . . . . . . . 7
3.2.2. EPP <delete> Command. . . . . . . . . . . . . . . . 9
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . 9
3.2.4. EPP <transfer> Command. . . . . . . . . . . . . . . 9
3.2.5. EPP <update> Command. . . . . . . . . . . . . . . . 9
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 11
5. Internationalization Considerations . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . 15
9. References. . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 16
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. E.164 Domain Names . . . . . . . . . . . . . . . . . . . . 3
2.2. NAPTR Fields . . . . . . . . . . . . . . . . . . . . . . . 3
2.2.1. Order . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.2. Preference. . . . . . . . . . . . . . . . . . . . . 4
2.2.3. Flags . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.4. Service . . . . . . . . . . . . . . . . . . . . . . 4
2.2.5. Regular Expression. . . . . . . . . . . . . . . . . 4
2.2.6. Replacement . . . . . . . . . . . . . . . . . . . . 4
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . . 4
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 5
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . 5
3.1.2. EPP <info> Command. . . . . . . . . . . . . . . . . 5
3.1.3. EPP <transfer> Command. . . . . . . . . . . . . . . 7
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 7
3.2.1. EPP <create> Command. . . . . . . . . . . . . . . . 7
3.2.2. EPP <delete> Command. . . . . . . . . . . . . . . . 9
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . 9
3.2.4. EPP <transfer> Command. . . . . . . . . . . . . . . 9
3.2.5. EPP <update> Command. . . . . . . . . . . . . . . . 9
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 11
5. Internationalization Considerations . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . 15
9. References. . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 16
This document describes an E.164 number mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This mapping, an extension of the domain name mapping described in [1], is specified using the Extensible Markup Language (XML) 1.0, as described in [2], and XML Schema notation, as described in [3] and [4].
本文档描述了可扩展资源调配协议（EPP）1.0版的E.164编号映射。此映射是[1]中所述域名映射的扩展，使用[2]中所述的可扩展标记语言（XML）1.0和[3]和[4]中所述的XML模式表示法指定。
The EPP core protocol specification [5] 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核心协议规范[5]提供了EPP命令和响应结构的完整描述。要理解本文档中描述的映射，必须彻底理解基本协议规范。
ENUM [6] describes how the Domain Name System (DNS) can be used to identify services associated with an E.164 number. The EPP mapping described in this document specifies a mechanism for the provisioning and management of E.164 numbers stored in a shared central repository. Information exchanged via this mapping can be extracted from the repository and used to publish DNS resource records as described in ENUM [6]. Examples used in this document were chosen specifically to illustrate provisioning concepts for the example resource records described in the ENUM specification.
ENUM[6]描述了如何使用域名系统（DNS）识别与E.164号码关联的服务。本文档中描述的EPP映射指定了一种机制，用于提供和管理存储在共享中央存储库中的E.164编号。通过此映射交换的信息可以从存储库中提取，并用于发布DNS资源记录，如ENUM[6]中所述。本文档中使用的示例专门用于说明枚举规范中描述的示例资源记录的配置概念。
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 [7].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[7]中所述进行解释。
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 only provided to illustrate element relationships and are not a REQUIRED feature of this specification.
在示例中，“C:”表示协议客户端发送的行，“S:”表示协议服务器返回的行。示例中的缩进和空白仅用于说明元素关系，不是本规范的必需特征。
XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented to develop a conforming implementation.
XML区分大小写。除非另有说明，否则本文档中提供的XML规范和示例必须按照提供的字符大小写进行解释，以开发一致的实现。
This extension adds elements to the EPP domain name mapping [1]. Only new element descriptions are described here.
此扩展将元素添加到EPP域名映射[1]。这里只描述新元素描述。
An E.164 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 [6]. The labels used to describe the name space of an E.164 domain name are a policy matter that is beyond the scope of this document.
E.164域名是E.164编号的表示形式，该编号已翻译为符合域名语法，如ENUM规范[6]所述。用于描述E.164域名的名称空间的标签属于政策事项，超出了本文档的范围。
According to ENUM [6], Naming Authority Pointer (NAPTR) resource records are used to identify available ways for contacting a specific node identified by a domain name created from the translation of an E.164 number. The basic NAPTR record format is described in RFC 3403 [8]. Rules for structuring and using NAPTR records for use with ENUM are described in RFC 3761 [6].
根据ENUM[6]，命名机构指针（NAPTR）资源记录用于确定联系特定节点的可用方式，该节点由通过翻译E.164号码创建的域名标识。RFC 3403[8]中描述了基本NAPTR记录格式。RFC 3761[6]中描述了用于枚举的NAPTR记录的结构和使用规则。
Several NAPTR field values are optional per RFC 3403. RFC 3761 describes processing rules that require the presence of certain NAPTR field values. This document describes field value requirements that correspond to RFC 3761.
根据RFC 3403，几个NAPTR字段值是可选的。RFC 3761描述了需要存在某些NAPTR字段值的处理规则。本文件描述了与RFC 3761相对应的字段值要求。
The NAPTR order field, a 16-bit unsigned integer, is represented in this mapping using the XML Schema "unsignedShort" data type.
NAPTR order字段是一个16位无符号整数，在此映射中使用XML模式“unsignedShort”数据类型表示。
The NAPTR preference field, a 16-bit unsigned integer, is represented in this mapping using the XML Schema "unsignedShort" data type.
NAPTR首选项字段是一个16位无符号整数，在此映射中使用XML模式“unsignedShort”数据类型表示。
The NAPTR flags field is represented in this mapping using a single character. The case of the flag character is not significant.
NAPTR flags字段在此映射中使用单个字符表示。标志字符的大小写不重要。
The NAPTR service field is represented in this mapping using a character string with an unspecified maximum length. Valid values are application-dependent.
NAPTR服务字段在此映射中使用未指定最大长度的字符串表示。有效值取决于应用程序。
The NAPTR regexp field is represented in this mapping using a character string with an unspecified maximum length. This field can contain numerous backslashes and should thus be treated with care.
NAPTR regexp字段在此映射中使用未指定最大长度的字符串表示。此字段可能包含许多反斜杠，因此应小心处理。
The NAPTR replacement field, whose value is a domain name, is represented in this mapping using a character string with a maximum length of 255 characters.
NAPTR替换字段（其值为域名）在此映射中使用最大长度为255个字符的字符串表示。
A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [5]. The command mappings described here are specifically for use in implementing ENUM provisioning processes via EPP.
EPP语法和语义的详细描述见EPP核心协议规范[5]。这里描述的命令映射专门用于通过EPP实现枚举资源调配过程。
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 [1].
此扩展不向EPP域映射[1]中描述的EPP<check>命令或<check>响应添加任何元素。
This extension does not add any elements to the EPP <info> command described in the EPP domain mapping [1]. Additional elements are defined for the <info> response.
此扩展不向EPP域映射[1]中描述的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 [1]. In addition, the EPP <extension> element MUST contain a child <e164:infData> element that identifies the extension namespace and the location of the extension schema. The <e164: infData> element contains one or more <e164:naptr> elements that contain the following child elements:
成功处理<info>命令后，EPP<resData>元素必须包含EPP域映射[1]中所述的子元素。此外，EPP<extension>元素必须包含一个子<e164:infData>元素，该元素标识扩展名称空间和扩展架构的位置。<e164:infData>元素包含一个或多个包含以下子元素的<e164:naptr>元素：
- An <e164:order> element that contains a NAPTR order value.
- 包含NAPTR order值的<e164:order>元素。
- An <e164:pref> element that contains a NAPTR preference value.
- 包含NAPTR首选项值的<e164:pref>元素。
- An OPTIONAL <e164:flags> element that contains a NAPTR flags value.
- 包含NAPTR flags值的可选<e164:flags>元素。
- An <e164:svc> element that contains a NAPTR service value.
- 包含NAPTR服务值的<e164:svc>元素。
- An OPTIONAL <e164:regex> element that contains a NAPTR regular expression value.
- 包含NAPTR正则表达式值的可选<e164:regex>元素。
- An OPTIONAL <e164:replacement> element that contains a NAPTR replacement value.
- 包含NAPTR替换值的可选<e164:replacement>元素。
Example <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: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
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: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S: domain-1.0.xsd">
S: <domain:name>3.8.0.0.6.9.2.3.6.1.4.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:host>ns1.example.com</domain:host>
S: <domain:host>ns2.example.com</domain:host>
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: <e164:infData xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:e164epp-1.0
S: e164epp-1.0.xsd">
S: <e164:naptr>
S: <e164:order>10</e164:order>
S: <e164:pref>100</e164:pref>
S: <e164:flags>u</e164:flags>
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: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
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: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S: domain-1.0.xsd">
S: <domain:name>3.8.0.0.6.9.2.3.6.1.4.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:host>ns1.example.com</domain:host>
S: <domain:host>ns2.example.com</domain:host>
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: <e164:infData xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:e164epp-1.0
S: e164epp-1.0.xsd">
S: <e164:naptr>
S: <e164:order>10</e164:order>
S: <e164:pref>100</e164:pref>
S: <e164:flags>u</e164:flags>
S: <e164:svc>E2U+sip</e164:svc>
S: <e164:regex>"!^.*$!sip:info@example.com!"</e164:regex>
S: </e164:naptr>
S: <e164:naptr>
S: <e164:order>10</e164:order>
S: <e164:pref>102</e164:pref>
S: <e164:flags>u</e164:flags>
S: <e164:svc>E2U+msg</e164:svc>
S: <e164:regex>"!^.*$!mailto:info@example.com!"</e164:regex>
S: </e164:naptr>
S: </e164:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
S: <e164:svc>E2U+sip</e164:svc>
S: <e164:regex>"!^.*$!sip:info@example.com!"</e164:regex>
S: </e164:naptr>
S: <e164:naptr>
S: <e164:order>10</e164:order>
S: <e164:pref>102</e164:pref>
S: <e164:flags>u</e164:flags>
S: <e164:svc>E2U+msg</e164:svc>
S: <e164:regex>"!^.*$!mailto:info@example.com!"</e164:regex>
S: </e164:naptr>
S: </e164:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>
An EPP error response MUST be returned if an extended <info> command can not be processed for any reason.
如果由于任何原因无法处理扩展的<info>命令，则必须返回EPP错误响应。
This extension does not add any elements to the EPP <transfer> command or <transfer> response described in the EPP domain mapping [1].
此扩展不向EPP域映射[1]中描述的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 [1]. No additional elements are defined for the EPP <create> response.
此扩展为EPP域映射[1]中描述的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 [1], the command MUST
contain an <extension> element. The <extension> element MUST contain
a child <e164:create> element that identifies the extension namespace
and the location of the extension schema. The <e164:create> element
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 [1], the command MUST
contain an <extension> element. The <extension> element MUST contain
a child <e164:create> element that identifies the extension namespace
and the location of the extension schema. The <e164:create> element
contains one or more <e164:naptr> elements that contain the following child elements:
包含一个或多个<e164:naptr>元素，这些元素包含以下子元素：
- An <e164:order> element that contains a NAPTR order value.
- 包含NAPTR order值的<e164:order>元素。
- An <e164:pref> element that contains a NAPTR preference value.
- 包含NAPTR首选项值的<e164:pref>元素。
- An OPTIONAL <e164:flags> element that contains a NAPTR flags value.
- 包含NAPTR flags值的可选<e164:flags>元素。
- An <e164:svc> element that contains a NAPTR service value.
- 包含NAPTR服务值的<e164:svc>元素。
- An OPTIONAL <e164:regex> element that contains a NAPTR regular expression value.
- 包含NAPTR正则表达式值的可选<e164:regex>元素。
- An OPTIONAL <e164:replacement> element that contains a NAPTR replacement value.
- 包含NAPTR替换值的可选<e164:replacement>元素。
Example <create> command:
示例<create>命令：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <create>
C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa</domain:name>
C: <domain:period unit="y">2</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: <e164:create
C: xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
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: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <create>
C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa</domain:name>
C: <domain:period unit="y">2</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: <e164:create
C: xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:e164epp-1.0
C: e164epp-1.0.xsd">
C: <e164:naptr>
C: <e164:order>10</e164:order>
C: <e164:pref>100</e164:pref>
C: <e164:flags>u</e164:flags>
C: <e164:svc>E2U+sip</e164:svc>
C: <e164:regex>"!^.*$!sip:info@example.com!"</e164:regex>
C: </e164:naptr>
C: <e164:naptr>
C: <e164:order>10</e164:order>
C: <e164:pref>102</e164:pref>
C: <e164:flags>u</e164:flags>
C: <e164:svc>E2U+msg</e164:svc>
C: <e164:regex>"!^.*$!mailto:info@example.com!"</e164:regex>
C: </e164:naptr>
C: </e164:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
C: xsi:schemaLocation="urn:ietf:params:xml:ns:e164epp-1.0
C: e164epp-1.0.xsd">
C: <e164:naptr>
C: <e164:order>10</e164:order>
C: <e164:pref>100</e164:pref>
C: <e164:flags>u</e164:flags>
C: <e164:svc>E2U+sip</e164:svc>
C: <e164:regex>"!^.*$!sip:info@example.com!"</e164:regex>
C: </e164:naptr>
C: <e164:naptr>
C: <e164:order>10</e164:order>
C: <e164:pref>102</e164:pref>
C: <e164:flags>u</e164:flags>
C: <e164:svc>E2U+msg</e164:svc>
C: <e164:regex>"!^.*$!mailto:info@example.com!"</e164:regex>
C: </e164:naptr>
C: </e164:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When an extended <create> command has been processed successfully, the EPP response is as described in the EPP domain mapping [1].
成功处理扩展的<create>命令后，EPP响应如EPP域映射[1]中所述。
This extension does not add any elements to the EPP <delete> command or <delete> response described in the EPP domain mapping [1].
此扩展不向EPP域映射[1]中描述的EPP<delete>命令或<delete>响应添加任何元素。
This extension does not add any elements to the EPP <renew> command or <renew> response described in the EPP domain mapping [1].
此扩展不向EPP域映射[1]中描述的EPP<renew>命令或<renew>响应添加任何元素。
This extension does not add any elements to the EPP <transfer> command or <transfer> response described in the EPP domain mapping [1].
此扩展不向EPP域映射[1]中描述的EPP<transfer>命令或<transfer>响应添加任何元素。
This extension defines additional elements for the EPP <update> command described in the EPP domain mapping [1]. No additional elements are defined for the EPP <update> response.
此扩展为EPP域映射[1]中描述的EPP<update>命令定义了其他元素。没有为EPP<update>响应定义其他元素。
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 [1], the <update> command MUST contain an <extension> element. The <extension> element MUST contain a child <e164:update> element that identifies the extension namespace and the location of the extension schema. The <e164:update> element contains one or more <e164:add> or <e164:rem> elements. Each <e164:add> and <e164:rem> element contains an <e164:naptr> element that contains the following child elements:
EPP<update>命令提供转换操作，允许客户端更改域对象的状态。除了EPP域映射[1]中描述的EPP命令元素外，<update>命令必须包含<extension>元素。<extension>元素必须包含一个子<e164:update>元素，该元素标识扩展名称空间和扩展架构的位置。<e164:update>元素包含一个或多个<e164:add>或<e164:rem>元素。每个<e164:add>和<e164:rem>元素都包含一个<e164:naptr>元素，该元素包含以下子元素：
- An <e164:order> element that contains a NAPTR order value.
- 包含NAPTR order值的<e164:order>元素。
- An <e164:pref> element that contains a NAPTR preference value.
- 包含NAPTR首选项值的<e164:pref>元素。
- An OPTIONAL <e164:flags> element that contains a NAPTR flags value.
- 包含NAPTR flags值的可选<e164:flags>元素。
- An <e164:svc> element that contains a NAPTR service value.
- 包含NAPTR服务值的<e164:svc>元素。
- An OPTIONAL <e164:regex> element that contains a NAPTR regular expression value.
- 包含NAPTR正则表达式值的可选<e164:regex>元素。
- An OPTIONAL <e164:replacement> element that contains a NAPTR replacement value.
- 包含NAPTR替换值的可选<e164:replacement>元素。
Example <update> command:
示例<update>命令：
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa</domain:name>
C: </domain:update>
C: </update>
C: <extension>
C: <e164:update xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:e164epp-1.0
C: e164epp-1.0.xsd">
C: <e164:rem>
C: <e164:naptr>
C: <e164:order>10</e164:order>
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: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa</domain:name>
C: </domain:update>
C: </update>
C: <extension>
C: <e164:update xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:e164epp-1.0
C: e164epp-1.0.xsd">
C: <e164:rem>
C: <e164:naptr>
C: <e164:order>10</e164:order>
C: <e164:pref>102</e164:pref>
C: <e164:flags>u</e164:flags>
C: <e164:svc>E2U+msg</e164:svc>
C: <e164:regex>"!^.*$!mailto:info@example.com!"</e164:regex>
C: </e164:naptr>
C: </e164:rem>
C: </e164:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
C: <e164:pref>102</e164:pref>
C: <e164:flags>u</e164:flags>
C: <e164:svc>E2U+msg</e164:svc>
C: <e164:regex>"!^.*$!mailto:info@example.com!"</e164:regex>
C: </e164:naptr>
C: </e164:rem>
C: </e164:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>
When an extended <update> command has been processed successfully, the EPP response is as described in the EPP domain mapping [1].
成功处理扩展的<update>命令后，EPP响应如EPP域映射[1]中所述。
An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes.
EPP对象映射是用XML模式表示法指定的。这里给出的形式语法是对象映射的完整模式表示，适合于自动验证EPP XML实例。开始和结束标记不是模式的一部分；它们用于记录模式的开始和结束，以便进行URI注册。
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:e164epp-1.0"
xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<schema targetNamespace="urn:ietf:params:xml:ns:e164epp-1.0"
xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name extension schema for E.164 number provisioning.
</documentation>
</annotation>
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name extension schema for E.164 number provisioning.
</documentation>
</annotation>
<!--
Child elements found in EPP commands.
-->
<element name="create" type="e164:createType"/>
<element name="update" type="e164:updateType"/>
<!--
Child elements found in EPP commands.
-->
<element name="create" type="e164:createType"/>
<element name="update" type="e164:updateType"/>
<!--
Global elements.
-->
<element name="naptr" type="e164:naptrType"/>
<!--
Global elements.
-->
<element name="naptr" type="e164:naptrType"/>
<!--
Child elements of the <create> command.
-->
<complexType name="createType">
<sequence>
<element ref="e164:naptr" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Child elements of the <create> command.
-->
<complexType name="createType">
<sequence>
<element ref="e164:naptr" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="naptrType">
<sequence>
<element name="order" type="unsignedShort"/>
<element name="pref" type="unsignedShort"/>
<element name="flags" type="e164:flagsType"
minOccurs="0"/>
<element name="svc" type="e164:svcType"/>
<element name="regex" type="e164:regexType"
minOccurs="0"/>
<element name="repl" type="e164:replType"
minOccurs="0"/>
</sequence>
</complexType>
<complexType name="naptrType">
<sequence>
<element name="order" type="unsignedShort"/>
<element name="pref" type="unsignedShort"/>
<element name="flags" type="e164:flagsType"
minOccurs="0"/>
<element name="svc" type="e164:svcType"/>
<element name="regex" type="e164:regexType"
minOccurs="0"/>
<element name="repl" type="e164:replType"
minOccurs="0"/>
</sequence>
</complexType>
<simpleType name="flagsType">
<restriction base="token">
<pattern value="[A-Z]|[a-z]|[0-9]"/>
<length value="1"/>
</restriction>
</simpleType>
<simpleType name="flagsType">
<restriction base="token">
<pattern value="[A-Z]|[a-z]|[0-9]"/>
<length value="1"/>
</restriction>
</simpleType>
<simpleType name="svcType">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<simpleType name="svcType">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<simpleType name="regexType">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<simpleType name="regexType">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<simpleType name="replType">
<restriction base="token">
<minLength value="1"/>
<maxLength value="255"/>
</restriction>
</simpleType>
<simpleType name="replType">
<restriction base="token">
<minLength value="1"/>
<maxLength value="255"/>
</restriction>
</simpleType>
<!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="add" type="e164:addRemType"
minOccurs="0"/>
<element name="rem" type="e164:addRemType"
minOccurs="0"/>
</sequence>
</complexType>
<!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="add" type="e164:addRemType"
minOccurs="0"/>
<element name="rem" type="e164:addRemType"
minOccurs="0"/>
</sequence>
</complexType>
<!--
Data elements that can be added or removed.
-->
<complexType name="addRemType">
<sequence>
<element ref="e164:naptr" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Data elements that can be added or removed.
-->
<complexType name="addRemType">
<sequence>
<element ref="e164:naptr" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Child response elements.
-->
<element name="infData" type="e164:infDataType"/>
<!--
Child response elements.
-->
<element name="infData" type="e164:infDataType"/>
<!--
<info> response elements.
-->
<complexType name="infDataType">
<sequence>
<element ref="e164:naptr" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
<info> response elements.
-->
<complexType name="infDataType">
<sequence>
<element ref="e164:naptr" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!-- End of schema. --> </schema> END
<!-- 架构结束。--></架构>结束
EPP is represented in XML, which provides native support for encoding information using the Unicode character set and its more compact representations, including UTF-8 [10]. Conformant XML processors recognize both UTF-8 and UTF-16 [11]. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED in environments where parser encoding support incompatibility exists.
EPP用XML表示，它为使用Unicode字符集及其更紧凑的表示（包括UTF-8[10]）编码信息提供了本机支持。一致性XML处理器同时识别UTF-8和UTF-16[11]。尽管XML包含通过在<？XML？>声明中使用“encoding”属性来识别和使用其他字符编码的规定，但在解析器编码支持不兼容的环境中，建议使用UTF-8。
As an extension of the EPP domain mapping [1], the elements, element content, attributes, and attribute values described in this document MUST inherit the internationalization conventions used to represent higher-layer domain and core protocol structures present in an XML instance that includes this extension.
作为EPP域映射[1]的扩展，本文档中描述的元素、元素内容、属性和属性值必须继承用于表示包含此扩展的XML实例中存在的更高层域和核心协议结构的国际化约定。
This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in RFC 3688 [9]. Two URI assignments have been completed by the IANA:
本文档使用URN来描述符合RFC 3688[9]中描述的注册表机制的XML名称空间和XML模式。IANA已完成两个URI分配：
Registration for the extension namespace:
注册扩展命名空间：
URI: urn:ietf:params:xml:ns:e164epp-1.0
URI: urn:ietf:params:xml:ns:e164epp-1.0
Registrant Contact: IESG
注册联系人：IESG
XML: None. Namespace URIs do not represent an XML specification.
XML：没有。命名空间URI不表示XML规范。
Registration for the extension XML schema:
注册扩展XML架构：
URI: urn:ietf:params:xml:schema:e164epp-1.0
URI: urn:ietf:params:xml:schema:e164epp-1.0
Registrant Contact: IESG
注册联系人：IESG
XML: See the "Formal Syntax" section of this document.
XML：请参阅本文档的“正式语法”部分。
The mapping extensions described in this document do not provide any security services beyond those described by EPP [5], the EPP domain name mapping [1], and protocol layers used by EPP. Security considerations related to ENUM are described in the "Security Considerations" section of the ENUM specification [6]; security considerations related to the Dynamic Delegation Discovery System and NAPTR records are described in the "Security Considerations" section
本文档中描述的映射扩展不提供EPP[5]、EPP域名映射[1]和EPP使用的协议层之外的任何安全服务。ENUM规范[6]的“安全注意事项”部分描述了与ENUM相关的安全注意事项；与动态委派发现系统和NAPTR记录相关的安全注意事项在“安全注意事项”部分中介绍
of RFC 3403 [8]. The security considerations described in these specifications apply to this specification as well.
RFC 3403[8]的第1部分。这些规范中描述的安全注意事项也适用于本规范。
As with other domain object transforms, the EPP transform operations described in this document MUST be restricted to the sponsoring client as authenticated using the mechanisms described in sections 2.9.1.1 and 7 of RFC 3730 [5]. Any attempt to perform a transform operation on a domain object by any client other than the sponsoring client MUST be rejected with an appropriate EPP authorization error.
与其他域对象转换一样，本文档中描述的EPP转换操作必须限于使用RFC 3730[5]第2.9.1.1和7节中描述的机制进行身份验证的发起客户端。必须拒绝发起客户端以外的任何客户端对域对象执行转换操作的任何尝试，并显示相应的EPP授权错误。
The author would like to thank the following people who have provided significant contributions to the development of this document:
作者要感谢为本文件的编写做出重大贡献的以下人员：
Lawrence Conroy, Edward Lewis, Michael Mealling, Allison Mankin, Chip Sharp, and James Yu.
劳伦斯·康罗伊、爱德华·刘易斯、迈克尔·米林、埃里森·曼金、奇普·夏普和詹姆斯·余。
[1] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", RFC 3731, March 2004.
[1] Hollenbeck，S.，“可扩展供应协议（EPP）域名映射”，RFC 37312004年3月。
[2] Paoli, J., Sperberg-McQueen, C., Bray, T., and E. Maler, "Extensible Markup Language (XML) 1.0 (Second Edition)", W3C FirstEdition REC-xml-20001006, October 2000.
[2] Paoli，J.，Sperberg McQueen，C.，Bray，T.，和E.Maler，“可扩展标记语言（XML）1.0（第二版）”，W3C第一版REC-XML-20001006，2000年10月。
[3] Maloney, M., Beech, D., Mendelsohn, N., and H. Thompson, "XML Schema Part 1: Structures", W3C REC REC-xmlschema-1-20010502, May 2001.
[3] Maloney，M.，Beech，D.，Mendelsohn，N.，和H.Thompson，“XML模式第1部分：结构”，W3C REC-xmlschema-1-20010502，2001年5月。
[4] Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes", W3C REC REC-xmlschema-2-20010502, May 2001.
[4] Malhotra，A.和P.Biron，“XML模式第2部分：数据类型”，W3C REC-xmlschema-2-20010502，2001年5月。
[5] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", RFC 3730, March 2004.
[5] Hollenbeck，S.，“可扩展资源调配协议（EPP）”，RFC3730，2004年3月。
[6] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004.
[6] Faltstrom，P.和M.Mealling，“E.164到统一资源标识符（URI）动态委托发现系统（DDDS）应用程序（ENUM）”，RFC 3761，2004年4月。
[7] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[7] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[8] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403, October 2002.
[8] Mealling，M.“动态委托发现系统（DDDS）第三部分：域名系统（DNS）数据库”，RFC3403，2002年10月。
[9] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[9] Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[10] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[10] Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，2003年11月。
[11] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646", RFC 2781, February 2000.
[11] Hoffman，P.和F.Yergeau，“UTF-16，ISO 10646编码”，RFC 2781，2000年2月。
Author's Address
作者地址
Scott Hollenbeck VeriSign, Inc. 21345 Ridgetop Circle Dulles, VA 20166-6503 US
Scott Hollenbeck VeriSign，Inc.美国弗吉尼亚州杜勒斯Ridgetop Circle 21345，邮编20166-6503
EMail: shollenbeck@verisign.com
EMail: shollenbeck@verisign.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
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 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。