Internet Engineering Task Force (IETF) L. Iannone
Request for Comments: 7955 Telecom ParisTech
Category: Informational R. Jorgensen
ISSN: 2070-1721 Bredbandsfylket Troms
D. Conrad
Virtualized, LLC
G. Huston
APNIC
September 2016
Internet Engineering Task Force (IETF) L. Iannone
Request for Comments: 7955 Telecom ParisTech
Category: Informational R. Jorgensen
ISSN: 2070-1721 Bredbandsfylket Troms
D. Conrad
Virtualized, LLC
G. Huston
APNIC
September 2016
Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
定位器/ID分离协议（LISP）端点标识符（EID）块的管理指南
Abstract
摘要
This document proposes a framework for the management of the Locator/ ID Separation Protocol (LISP) Endpoint Identifier (EID) address block. The framework described relies on hierarchical distribution of the address space, granting temporary usage of prefixes of such space to requesting organizations.
本文档提出了一个管理定位器/ID分离协议（LISP）端点标识符（EID）地址块的框架。所描述的框架依赖于地址空间的分层分布，允许请求组织临时使用此类空间的前缀。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7955.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7955.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
4. EID Prefix Registration Policy . . . . . . . . . . . . . . . 3
5. EID Prefixes Registration Requirements . . . . . . . . . . . 4
6. EID Prefix Request Template . . . . . . . . . . . . . . . . . 4
7. Policy Validity Period . . . . . . . . . . . . . . . . . . . 6
8. Security Considerations . . . . . . . . . . . . . . . . . . . 6
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
10. Procedures to be Followed by RIPE NCC . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . 8
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
4. EID Prefix Registration Policy . . . . . . . . . . . . . . . 3
5. EID Prefixes Registration Requirements . . . . . . . . . . . 4
6. EID Prefix Request Template . . . . . . . . . . . . . . . . . 4
7. Policy Validity Period . . . . . . . . . . . . . . . . . . . 6
8. Security Considerations . . . . . . . . . . . . . . . . . . . 6
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
10. Procedures to be Followed by RIPE NCC . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . 8
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
The Locator/ID Separation Protocol (LISP [RFC6830]) and related mechanisms ([RFC6831], [RFC6832], [RFC6833], [RFC6834], [RFC6835], [RFC6836], [RFC6837]) separate the IP addressing space into two logical spaces, the Endpoint Identifier (EID) space and the Routing Locator (RLOC) space. The first space is used to identify communication endpoints, while the second is used to locate EIDs in the Internet routing infrastructure topology.
定位器/ID分离协议（LISP[RFC6830]）和相关机制（[RFC6831]、[RFC6832]、[RFC6833]、[RFC6834]、[RFC6835]、[RFC6836]、[RFC6837]）将IP寻址空间分为两个逻辑空间，即端点标识符（EID）空间和路由定位器（RLOC）空间。第一个空间用于标识通信端点，而第二个空间用于在Internet路由基础结构拓扑中定位EID。
[RFC7954] requests an IPv6 address block reservation exclusively for use as EID prefixes in the LISP experiment. The rationale, intent, size, and usage of the EID address block are described in [RFC7954].
[RFC7954]请求一个IPv6地址块保留，专门用作LISP实验中的EID前缀。EID地址块的基本原理、用途、大小和用法见[RFC7954]。
This document proposes a management framework for the registration of EID prefixes from that block, allowing the requesting organization exclusive use of those EID prefixes limited to the duration of the LISP experiment.
本文档提出了一个管理框架，用于从该块注册EID前缀，允许请求组织在LISP实验期间独占使用这些EID前缀。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
This document does not introduce any new terms related to the set of LISP Specifications ([RFC6830], [RFC6831], [RFC6832], [RFC6833], [RFC6834], [RFC6835], [RFC6836], [RFC6837]), but assumes that the reader is familiar with the LISP terminology. [INTRO] provides an introduction to the LISP technology, including its terminology.
本文档不介绍任何与LISP规范集相关的新术语（[RFC6830]、[RFC6831]、[RFC6832]、[RFC6833]、[RFC6834]、[RFC6835]、[RFC6836]、[RFC6837]），但假设读者熟悉LISP术语。[简介]介绍LISP技术，包括其术语。
The request for registration of EID prefixes MUST be done under the following policies:
必须根据以下策略请求注册EID前缀：
1. EID prefixes are made available in the reserved space on a temporary basis and for experimental uses. The requester of an experimental prefix MUST provide a short description of the intended use or experiment that will be carried out (see Section 6). If the prefix will be used for activities not documented in the original description, renewal of the registration may be denied.
1. EID前缀在保留空间中临时可用，用于实验用途。实验前缀的请求者必须提供将要进行的预期用途或实验的简短描述（见第6节）。如果前缀将用于原始描述中未记录的活动，则注册的续期可能会被拒绝。
2. EID prefix registrations MUST be renewed on a regular basis to ensure their use by active participants in the experiment. The registration period is 12 months. A renewal SHOULD NOT cause a change in the EID prefix registered in the previous request. The conditions of registration renewal are to be the same as the conditions of the first EID prefix registration request.
2. EID前缀注册必须定期更新，以确保实验中的积极参与者使用它们。注册期为12个月。续订不应导致在上一个请求中注册的EID前缀发生更改。注册续展的条件应与第一个EID前缀注册请求的条件相同。
3. It is preferable that EID prefixes whose registrations have expired not be reused. When an EID prefix registration is removed from the registry, then the reuse of the EID prefix in a subsequent registration on behalf of a different end user should be avoided where possible. If the considerations of overall usage of the EID block prefix requires reuse of a previously registered EID prefix, then a minimum delay of at least one week between removal and subsequent registration SHOULD be applied by the registry operator.
3. 最好不要重用注册已过期的EID前缀。如果从注册表中删除EID前缀注册，则应尽可能避免在后续注册中代表其他最终用户重复使用EID前缀。如果考虑到EID块前缀的总体使用情况，需要重新使用以前注册的EID前缀，则注册表操作员应在删除和后续注册之间至少延迟一周。
4. When the reserved experimental LISP EID block expires, all EID prefix registrations expire as well. The further disposition of these prefixes and the associated registry entries are to be specified in the announcement of the cessation of this experiment.
4. 当保留的实验LISP EID块过期时，所有EID前缀注册也将过期。这些前缀和相关注册表项的进一步处理将在本实验停止的公告中规定。
All EID prefix registrations MUST satisfy the following requirements:
所有EID前缀注册必须满足以下要求：
1. All EID prefix registrations MUST use a globally unique EID prefix.
1. 所有EID前缀注册必须使用全局唯一的EID前缀。
2. The EID prefix registration information, as specified in Section 6, MUST be collected upon initial registration and renewal, and made publicly available through interfaces allowing both the retrieval of specific registration details (search) and the enumeration of the entire registry contents (e.g., RDAP ([RFC7481]), WHOIS, HTTP, or similar access methods).
2. 第6节中规定的EID前缀注册信息必须在初始注册和续订时收集，并通过允许检索特定注册详细信息（搜索）和枚举整个注册内容（例如RDAP（[RFC7481]）的接口公开、WHOIS、HTTP或类似的访问方法）。
3. The registry operator MUST permit the delegation of EID prefixes in the reverse DNS space to holders of registered EID prefixes.
3. 注册表操作员必须允许将反向DNS空间中的EID前缀委托给已注册EID前缀的持有者。
4. Anyone can obtain an entry in the EID prefix registry, on the understanding that the prefix so registered is for the exclusive use in the LISP experimental network, and that their registration details (as specified in Section 6) are openly published in the EID prefix registry.
4. 任何人都可以在EID前缀注册表中获得条目，前提是这样注册的前缀仅供LISP实验网络使用，并且他们的注册详细信息（如第6节所述）在EID前缀注册表中公开发布。
The following is a basic request template for prefix registration to ensure a uniform process. This template is inspired by IANA's online "Private Enterprise Number (PEN) Request" form <http://pen.iana.org/pen/PenApplication.page>.
以下是前缀注册的基本请求模板，以确保统一的过程。此模板的灵感来源于IANA的在线“私人企业编号（PEN）申请”表格<http://pen.iana.org/pen/PenApplication.page>.
Note that all details in this registration become part of the registry and will be published in the LISP EID Prefix Registry managed by RIPE NCC.
请注意，此注册中的所有详细信息都将成为注册表的一部分，并将在NCC管理的LISP EID前缀注册表中发布。
The EID Prefix Request template MUST at a minimum contain:
EID前缀请求模板必须至少包含：
1. Organization (In the case of individuals requesting an EID prefix, this section can be left empty)
1. 组织（在个人请求EID前缀的情况下，此部分可以留空）
(a) Organization Name
(a) 机构名称
(b) Organization Address
(b) 组织地址
(c) Organization Phone
(c) 组织电话
(d) Organization Website
(d) 组织网站
2. Contact Person (Mandatory)
2. 联系人（必填）
(a) Name
(a) 名称
(b) Address
(b) 住址
(c) Phone
(c) 电话
(d) Fax (optional)
(d) 传真（可选）
(e) Email
(e) 电子邮件
3. EID Prefix Request (Mandatory)
3. EID前缀请求（强制）
(a) Prefix Size
(a) 前缀尺寸
+ Expressed as an address prefix length.
+ 表示为地址前缀长度。
(b) Prefix Size Rationale
(b) 前缀大小原理
(c) Lease Period
(c) 租赁期
+ Note well: All EID Prefix registrations will be valid until the earlier date of 12 months from the date of registration or August 2019.
+ 请注意：所有EID前缀注册的有效期为自注册之日起12个月或2019年8月。
+ All registrations may be renewed by the applicant for further 12-month periods, ending on August 2019.
+ 申请人可将所有注册续期12个月，至2019年8月。
+ According to the 3+3 year experimentation plan, defined in [RFC7954], all registrations MUST end by August 2019, unless the IETF community decides to grant a permanent LISP EID address block. In the latter case, registrations following the present document policy MUST end by August 2022 and a new policy (to be decided -- see Section 7) will apply thereafter.
+ 根据[RFC7954]中定义的3+3年试验计划，所有注册必须在2019年8月结束，除非IETF社区决定授予永久LISP EID地址块。在后一种情况下，按照现行文件政策进行的注册必须在2022年8月结束，此后将适用新政策（待定——见第7节）。
4. Experiment Description
4. 实验说明
(a) Experiment and Deployment Description
(a) 实验和部署描述
(b) Interoperability with Existing LISP Deployments
(b) 与现有LISP部署的互操作性
(c) Interoperability with Legacy Internet
(c) 与传统Internet的互操作性
5. Reverse DNS Servers (Optional)
5. 反向DNS服务器（可选）
(a) Name Server Name
(a) 名称服务器名称
(b) Name Server Address
(b) 名称服务器地址
(c) Name Server Name
(c) 名称服务器名称
(d) Name Server Address
(d) 名称服务器地址
(Repeat if necessary)
（必要时重复）
The policy outlined in the present document is tied to the existence of the experimental LISP EID block requested in [RFC7954] and is valid until August 2019.
本文件中概述的政策与[RFC7954]中要求的实验性LISP EID块的存在有关，有效期至2019年8月。
If the IETF decides to transform the block into a permanent allocation, the usage period reserved for the LISP EID block will be extended for three years (until August 2022) to allow time for the IETF to define, following the policies outlined in [RFC5226], the final size of the EID block and create a transition plan, while the policy in the present document will still apply.
如果IETF决定将块转换为永久分配，则为LISP EID块保留的使用期将延长三年（至2022年8月），以便IETF有时间根据[RFC5226]中概述的政策定义EID块的最终大小并创建转换计划，而本文件中的政策仍将适用。
Note that, as stated in [RFC7954], the transition of the EID block into a permanent allocation has the potential to pose policy issues (as recognized in [RFC2860], Section 4.3); hence, discussion with the IANA, the Regional Internet Registry (RIR) communities, and the IETF community will be necessary to determine the appropriate policy for permanent EID prefix management, which will be effective after August 2022.
请注意，如[RFC7954]所述，EID区块转换为永久分配可能会引起政策问题（如[RFC2860]第4.3节所述）；因此，有必要与IANA、区域互联网注册（RIR）社区和IETF社区进行讨论，以确定永久EID前缀管理的适当政策，该政策将在2022年8月后生效。
This document does not introduce new security threats in the LISP architecture nor in the Legacy Internet architecture.
本文档不会在LISP体系结构或传统Internet体系结构中引入新的安全威胁。
For accountability reasons and in line with the security considerations in [RFC7020], each registration request MUST contain accurate information about the requesting entity (company, institution, individual, etc.) and valid and accurate contact information of a referral person (see Section 6).
出于问责原因并符合[RFC7020]中的安全考虑，每份注册申请必须包含关于申请实体（公司、机构、个人等）的准确信息以及转介人的有效准确联系信息（见第6节）。
IANA allocated the following IPv6 address block for experimental use as the LISP EID prefix [RFC7954]:
IANA分配了以下IPv6地址块作为LISP EID前缀[RFC7954]供实验使用：
o Address Block: 2001:5::/32
o 地址栏：2001:5:：/32
o Name: EID Space for LISP
o 名称：用于LISP的EID空间
o RFC: [RFC7954]
o RFC:[RFC7954]
o Further details are at: www.iana.org/assignments/iana-ipv6- special-registry
o 更多详细信息请访问：www.iana.org/assignments/iana-ipv6-特殊注册中心
To grant requesting organizations and individuals exclusive use of EID prefixes out of this reserved block (limited to the duration of the LISP experiment as outlined in Section 7), there is an operational requirement for an EID registration service.
为了允许提出请求的组织和个人在该保留块之外独占使用EID前缀（限于第7节中概述的LISP实验的持续时间），需要EID注册服务的操作要求。
Provided that the policies and requirements outlined in Sections 4, 5, and 6 are satisfied, EID prefix registration is accorded based on a "First Come First Served" basis.
如果满足第4、5和6节中概述的政策和要求，EID前缀注册将基于“先到先得”的原则。
There is no hard limit to the number of registrations an organization or individual can submit, as long as the information described in Section 6 is provided, in particular point 4: "Experiment Description".
只要提供第6节所述信息，特别是第4点：“实验说明”，组织或个人可以提交的注册数量没有硬性限制。
For the duration defined in [RFC7954], RIPE NCC will manage the LISP EID prefix as described herein. Therefore, this document has no IANA actions.
在[RFC7954]中定义的持续时间内，NCC将按照本文所述管理LISP EID前缀。因此，本文件没有IANA行动。
RIPE NCC will provide the registration service following the EID Prefix Registration Policy (Section 4) and the EID Prefix Registration Requirements (Section 5) provided in this document. The request form provided by RIPE NCC will include at least the information from the template in Section 6. RIPE NCC will make all received requests publicly available. While this document does not suggest any minimum allocation size; RIPE NCC is allowed to introduce such a minimum size for management purposes.
RIME NCC将按照本文件中提供的EID前缀注册政策（第4节）和EID前缀注册要求（第5节）提供注册服务。NCC提供的申请表将至少包括第6节模板中的信息。成熟的NCC将公开所有收到的请求。虽然本文件未建议任何最低分配规模；成熟的NCC允许为管理目的引入这样的最小规模。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, DOI 10.17487/RFC5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，DOI 10.17487/RFC5226，2008年5月<http://www.rfc-editor.org/info/rfc5226>.
[RFC7954] Iannone, L., Lewis, D., Meyer, D., and V. Fuller, "Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block", RFC 7954, DOI 10.17487/RFC7954, September 2016, <http://www.rfc-editor.org/info/rfc7954>.
[RFC7954]Iannone，L.，Lewis，D.，Meyer，D.，和V.Fuller，“定位器/ID分离协议（LISP）端点标识符（EID）块”，RFC 7954，DOI 10.17487/RFC7954，2016年9月<http://www.rfc-editor.org/info/rfc7954>.
[INTRO] Cabellos-Aparicio, A. and D. Saucez, "An Architectural Introduction to the Locator/ID Separation Protocol (LISP)", Work in Progress, draft-ietf-lisp-introduction-13, April 2015.
[INTRO]Cabellos Aparicio，A.和D.Saucez，“定位器/ID分离协议（LISP）的体系结构介绍”，正在进行的工作，草稿-ietf-LISP-Introduction-13，2015年4月。
[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority", RFC 2860, DOI 10.17487/RFC2860, June 2000, <http://www.rfc-editor.org/info/rfc2860>.
[RFC2860]Carpenter，B.，Baker，F.和M.Roberts，“关于互联网分配号码管理局技术工作的谅解备忘录”，RFC 2860，DOI 10.17487/RFC2860，2000年6月<http://www.rfc-editor.org/info/rfc2860>.
[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The Locator/ID Separation Protocol (LISP)", RFC 6830, DOI 10.17487/RFC6830, January 2013, <http://www.rfc-editor.org/info/rfc6830>.
[RFC6830]Farinaci，D.，Fuller，V.，Meyer，D.，和D.Lewis，“定位器/身份分离协议（LISP）”，RFC 6830，DOI 10.17487/RFC6830，2013年1月<http://www.rfc-editor.org/info/rfc6830>.
[RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The Locator/ID Separation Protocol (LISP) for Multicast Environments", RFC 6831, DOI 10.17487/RFC6831, January 2013, <http://www.rfc-editor.org/info/rfc6831>.
[RFC6831]Farinaci，D.，Meyer，D.，Zwiebel，J.，和S.Venaas，“用于多播环境的定位器/ID分离协议（LISP）”，RFC 6831，DOI 10.17487/RFC6831，2013年1月<http://www.rfc-editor.org/info/rfc6831>.
[RFC6832] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller, "Interworking between Locator/ID Separation Protocol (LISP) and Non-LISP Sites", RFC 6832, DOI 10.17487/RFC6832, January 2013, <http://www.rfc-editor.org/info/rfc6832>.
[RFC6832]Lewis，D.，Meyer，D.，Farinaci，D.，和V.Fuller，“定位器/ID分离协议（LISP）和非LISP站点之间的互通”，RFC 6832，DOI 10.17487/RFC6832，2013年1月<http://www.rfc-editor.org/info/rfc6832>.
[RFC6833] Fuller, V. and D. Farinacci, "Locator/ID Separation Protocol (LISP) Map-Server Interface", RFC 6833, DOI 10.17487/RFC6833, January 2013, <http://www.rfc-editor.org/info/rfc6833>.
[RFC6833]Fuller，V.和D.Farinaci，“定位器/ID分离协议（LISP）地图服务器接口”，RFC 6833，DOI 10.17487/RFC6833，2013年1月<http://www.rfc-editor.org/info/rfc6833>.
[RFC6834] Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID Separation Protocol (LISP) Map-Versioning", RFC 6834, DOI 10.17487/RFC6834, January 2013, <http://www.rfc-editor.org/info/rfc6834>.
[RFC6834]Iannone，L.，Saucez，D.，和O.Bonaventure，“定位器/ID分离协议（LISP）地图版本控制”，RFC 6834，DOI 10.17487/RFC6834，2013年1月<http://www.rfc-editor.org/info/rfc6834>.
[RFC6835] Farinacci, D. and D. Meyer, "The Locator/ID Separation Protocol Internet Groper (LIG)", RFC 6835, DOI 10.17487/RFC6835, January 2013, <http://www.rfc-editor.org/info/rfc6835>.
[RFC6835]Farinaci，D.和D.Meyer，“定位器/身份分离协议互联网格罗珀（LIG）”，RFC 6835，DOI 10.17487/RFC6835，2013年1月<http://www.rfc-editor.org/info/rfc6835>.
[RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis, "Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836, January 2013, <http://www.rfc-editor.org/info/rfc6836>.
[RFC6836]Fuller，V.，Farinaci，D.，Meyer，D.，和D.Lewis，“定位器/ID分离协议替代逻辑拓扑（LISP+ALT）”，RFC 6836，DOI 10.17487/RFC6836，2013年1月<http://www.rfc-editor.org/info/rfc6836>.
[RFC6837] Lear, E., "NERD: A Not-so-novel Endpoint ID (EID) to Routing Locator (RLOC) Database", RFC 6837, DOI 10.17487/RFC6837, January 2013, <http://www.rfc-editor.org/info/rfc6837>.
[RFC6837]李尔，E.“NERD：路由定位器（RLOC）数据库的一个不太新颖的端点ID（EID）”，RFC 6837，DOI 10.17487/RFC6837，2013年1月<http://www.rfc-editor.org/info/rfc6837>.
[RFC7020] Housley, R., Curran, J., Huston, G., and D. Conrad, "The Internet Numbers Registry System", RFC 7020, DOI 10.17487/RFC7020, August 2013, <http://www.rfc-editor.org/info/rfc7020>.
[RFC7020]Housley，R.，Curran，J.，Huston，G.，和D.Conrad，“互联网号码注册系统”，RFC 7020，DOI 10.17487/RFC7020，2013年8月<http://www.rfc-editor.org/info/rfc7020>.
[RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the Registration Data Access Protocol (RDAP)", RFC 7481, DOI 10.17487/RFC7481, March 2015, <http://www.rfc-editor.org/info/rfc7481>.
[RFC7481]Hollenbeck，S.和N.Kong，“注册数据访问协议（RDAP）的安全服务”，RFC 7481，DOI 10.17487/RFC7481，2015年3月<http://www.rfc-editor.org/info/rfc7481>.
Acknowledgments
致谢
Thanks to A. Retana, J. Arkko, P. Yee, A. de la Haye, A. Cima, A. Pawlik, J. Curran, A. Severin, B. Haberman, T. Manderson, D. Lewis, D. Farinacci, M. Binderberger, D. Saucez, E. Lear, for their helpful comments.
感谢A.Retana、J.Arkko、P.Yee、A.de la Haye、A.Cima、A.Pawlik、J.Curran、A.Severin、B.Haberman、T.Manderson、D.Lewis、D.Farinaci、M.Binderberger、D.Saucez、E.Lear的有益评论。
The work of Luigi Iannone has been partially supported by the ANR-13-INFR-0009 LISP-Lab Project <www.lisp-lab.org> and the EIT KIC ICT-Labs SOFNETS Project.
Luigi Iannone的工作得到了ANR-13-INFR-0009 LISP实验室项目<www.LISP-Lab.org>和EIT KIC ICT实验室SOFnet项目的部分支持。
Authors' Addresses
作者地址
Luigi Iannone Telecom ParisTech France
法国巴黎电信公司路易吉·伊安诺
Email: ggx@gigix.net
Email: ggx@gigix.net
Roger Jorgensen Bredbandsfylket Troms Norway
罗杰·乔根森·布雷班德斯菲克特·特罗姆斯挪威
Email: rogerj@gmail.com
Email: rogerj@gmail.com
David Conrad Virtualized, LLC United States
美国David Conrad虚拟化有限责任公司
Email: drc@virtualized.org
Email: drc@virtualized.org
Geoff Huston Asia Pacific Network Information Centre (APNIC) Australia
澳大利亚杰夫休斯顿亚太网络信息中心（APNIC）
Email: gih@apnic.net
Email: gih@apnic.net