Internet Engineering Task Force (IETF) M. Boucadair
Request for Comments: 8113 C. Jacquenet
Updates: 6830 Orange
Category: Experimental March 2017
ISSN: 2070-1721
Internet Engineering Task Force (IETF) M. Boucadair
Request for Comments: 8113 C. Jacquenet
Updates: 6830 Orange
Category: Experimental March 2017
ISSN: 2070-1721
Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
定位器/ID分离协议（LISP）：用于数据包类型分配的共享扩展消息和IANA注册表
Abstract
摘要
This document specifies a Locator/ID Separation Protocol (LISP) shared message type for defining future extensions and conducting experiments without consuming a LISP packet type codepoint for each extension. It also defines a registry for LISP Packet Type allocations, thus updating RFC 6830.
本文档指定了定位器/ID分离协议（LISP）共享消息类型，用于定义未来的扩展并进行实验，而无需为每个扩展使用LISP数据包类型的代码点。它还为LISP数据包类型分配定义了一个注册表，从而更新RFC6830。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.
本文件不是互联网标准跟踪规范；它是为检查、实验实施和评估而发布的。
This document defines an Experimental Protocol for the Internet community. 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/rfc8113.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc8113.
Copyright Notice
版权公告
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2017 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 Language . . . . . . . . . . . . . . . . . . . . 3
3. LISP Shared Extension Message Type . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5.1. LISP Packet Types . . . . . . . . . . . . . . . . . . . . 4
5.2. Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. LISP Shared Extension Message Type . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5.1. LISP Packet Types . . . . . . . . . . . . . . . . . . . . 4
5.2. Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
The Locator/ID Separation Protocol (LISP) base specification,
[RFC6830], defines a set of primitives that are identified with a
packet type code. Several extensions have been proposed to add more
LISP functionalities. For example, new message types are proposed in
[LISP-DDT], [LISP-MN-EXT], [LISP-BULK], [NAT-LISP], or
[LISP-SUBSCRIBE]. It is expected that additional LISP extensions
will be proposed in the future.
The Locator/ID Separation Protocol (LISP) base specification,
[RFC6830], defines a set of primitives that are identified with a
packet type code. Several extensions have been proposed to add more
LISP functionalities. For example, new message types are proposed in
[LISP-DDT], [LISP-MN-EXT], [LISP-BULK], [NAT-LISP], or
[LISP-SUBSCRIBE]. It is expected that additional LISP extensions
will be proposed in the future.
In order to ease the tracking of LISP message types, this document proposes to create a "LISP Packet Types" IANA registry (see Section 5).
为了便于跟踪LISP消息类型，本文档建议创建一个“LISP数据包类型”IANA注册表（见第5节）。
Because of the limited type space [RFC6830] and the need to conduct experiments to assess new LISP extensions, this document specifies a shared LISP extension message type and proposes a procedure for registering LISP shared extension sub-types (see Section 3).
由于有限的类型空间[RFC6830]以及需要进行实验以评估新的LISP扩展，本文档指定了共享LISP扩展消息类型，并提出了注册LISP共享扩展子类型的过程（见第3节）。
Concretely, one single LISP message type code is dedicated to future LISP extensions; sub-types are used to uniquely identify a given LISP extension making use of the shared LISP extension message type. These identifiers are selected by the author(s) of the corresponding LISP specification that introduces a new LISP extension message type.
具体来说，一个单一的LISP消息类型代码专用于未来的LISP扩展；子类型用于使用共享LISP扩展消息类型唯一标识给定的LISP扩展。这些标识符由引入新LISP扩展消息类型的相应LISP规范的作者选择。
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]中所述进行解释。
Figure 1 depicts the common format of the LISP shared extension message. The type field MUST be set to 15 (see Section 5).
图1描述了LISP共享扩展消息的通用格式。类型字段必须设置为15（参见第5节）。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Type=15| Sub-type | extension-specific |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// extension-specific //
// //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Type=15| Sub-type | extension-specific |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// extension-specific //
// //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: LISP Shared Extension Message Type
图1:LISP共享扩展消息类型
The "Sub-type" field conveys a unique identifier that MUST be registered with IANA (see Section 5.2).
“子类型”字段表示必须向IANA注册的唯一标识符（见第5.2节）。
The exact structure of the 'extension-specific' portion of the message is specified in the corresponding specification document.
消息的“扩展特定”部分的确切结构在相应的规范文档中指定。
This document does not introduce any additional security issues other than those discussed in [RFC6830].
除[RFC6830]中讨论的安全问题外，本文件不引入任何其他安全问题。
IANA has created a new protocol registry for LISP Packet Types, numbered 0-15. The registry is initially populated with the following values:
IANA为LISP数据包类型创建了一个新的协议注册表，编号为0-15。注册表最初由以下值填充：
Message Code Reference
================================= ==== ===============
Reserved 0 [RFC6830]
LISP Map-Request 1 [RFC6830]
LISP Map-Reply 2 [RFC6830]
LISP Map-Register 3 [RFC6830]
LISP Map-Notify 4 [RFC6830]
LISP Encapsulated Control Message 8 [RFC6830]
LISP Shared Extension Message 15 [RFC8113]
Message Code Reference
================================= ==== ===============
Reserved 0 [RFC6830]
LISP Map-Request 1 [RFC6830]
LISP Map-Reply 2 [RFC6830]
LISP Map-Register 3 [RFC6830]
LISP Map-Notify 4 [RFC6830]
LISP Encapsulated Control Message 8 [RFC6830]
LISP Shared Extension Message 15 [RFC8113]
The values in the ranges 5-7 and 9-14 can be assigned via Standards Action [RFC5226]. Documents that request for a new LISP packet type may indicate a preferred value in the corresponding IANA sections.
范围5-7和9-14中的值可通过标准操作[RFC5226]分配。请求新LISP数据包类型的文档可能会在相应的IANA部分中指出首选值。
IANA has created the "LISP Shared Extension Message Type Sub-types" registry. No initial values are assigned at the creation of the registry; (0-4095) are available for future assignments.
IANA已经创建了“LISP共享扩展消息类型子类型”注册表。创建注册表时未指定初始值；（0-4095）可供将来分配。
The values in the range 0-1023 are assigned via Standards Action. This range is provisioned to anticipate, in particular, the exhaustion of the LISP Packet types.
0-1023范围内的值通过标准操作分配。设置此范围是为了预测LISP数据包类型的耗尽。
The values in the range 1024-4095 are assigned on a First Come, First Served (FCFS) basis. The registration procedure should provide IANA with the desired codepoint and a point of contact; providing a short description (together with an acronym, if relevant) of the foreseen usage of the extension message is also encouraged.
1024-4095范围内的值以先到先得（FCFS）的方式分配。注册程序应为IANA提供所需的代码点和联络点；还鼓励对扩展消息的预期用途进行简短描述（如果相关，还应提供首字母缩略词）。
[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>.
[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>.
[LISP-BULK] Boucadair, M. and C. Jacquenet, "LISP Mapping Bulk Retrieval", Work in Progress, draft-boucadair-lisp-bulk-04, February 2017.
[LISP-BULK]Boucadair，M.和C.Jacquenet，“LISP映射批量检索”，正在进行的工作，草稿-Boucadair-LISP-BULK-042017年2月。
[LISP-DDT] Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A. Smirnov, "LISP Delegated Database Tree", Work in Progress, draft-ietf-lisp-ddt-09, January 2017.
[LISP-DDT]Fuller，V.，Lewis，D.，Ermagan，V.，Jain，A.，和A.Smirnov，“LISP委托数据库树”，正在进行的工作，草案-ietf-LISP-DDT-092017年1月。
[LISP-MN-EXT] Wang, J., Meng, Y., and N. Zhao, "LISP Mobile Node extension", Work in Progress, draft-zhao-lisp-mn-extension-02, October 2011.
[LISP-MN-EXT]Wang，J.，Meng，Y.，和N.Zhao，“LISP移动节点扩展”，正在进行的工作，草稿-Zhao-LISP-MN-extension-022011年10月。
[LISP-SUBSCRIBE] Boucadair, M. and C. Jacquenet, "LISP Subscription", Work in Progress, draft-boucadair-lisp-subscribe-04, February 2017.
[LISP-SUBSCRIBE]Boucadair，M.和C.Jacquenet，“LISP订阅”，正在进行的工作，草稿-Boucadair-LISP-SUBSCRIBE-042017年2月。
[NAT-LISP] Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino, F., and C. White, "NAT traversal for LISP", Work in Progress, draft-ermagan-lisp-nat-traversal-11, August 2016.
[NAT-LISP]Ermagan，V.，Farinaci，D.，Lewis，D.，Skriver，J.，Maino，F.，和C.White，“LISP的NAT遍历”，正在进行的工作，草稿-Ermagan-LISP-NAT-traversal-112016年8月。
Acknowledgments
致谢
This work is partly funded by ANR LISP-Lab project #ANR-13-INFR-009-X.
这项工作的部分资金来自ANR LISP实验室项目#ANR-13-INFR-009-X。
Many thanks to Luigi Iannone, Dino Farinacci, and Alvaro Retana for the review.
非常感谢路易吉·伊安诺、迪诺·法里纳奇和阿尔瓦罗·雷塔纳的评论。
Thanks to Geoff Huston for the RtgDir directorate review.
感谢Geoff Huston对RtgDir董事会的审查。
Authors' Addresses
作者地址
Mohamed Boucadair Orange Rennes 35000 France
穆罕默德·布卡代尔·奥兰治·雷恩35000法国
Email: mohamed.boucadair@orange.com
Email: mohamed.boucadair@orange.com
Christian Jacquenet Orange Rennes 35000 France
克里斯蒂安·雅克内特·奥兰治·雷恩35000法国
Email: christian.jacquenet@orange.com
Email: christian.jacquenet@orange.com