8113
EXPERIMENTAL
Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations (Obsoleted)
Authors: M. Boucadair, C. Jacquenet
Date: March 2017
Area: rtg
Working Group: lisp
Stream: IETF
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.
RFC 8113
Obsoleted by: 9304 EXPERIMENTAL
Internet Engineering Task Force (IETF) M. Boucadair
Request for Comments: 8113 C. Jacquenet
Updates: <a href="./rfc6830">6830</a> Orange
Category: Experimental March 2017
ISSN: 2070-1721
<span class="h1">Locator/ID Separation Protocol (LISP):</span>
<span class="h1">Shared Extension Message & IANA Registry for Packet Type Allocations</span>
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 <a href="./rfc6830">RFC 6830</a>.
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 <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc8113">http://www.rfc-editor.org/info/rfc8113</a>.
<span class="grey">Boucadair & Jacquenet Experimental [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc8113">RFC 8113</a> LISP Packet Type Allocations March 2017</span>
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Requirements Language . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. LISP Shared Extension Message Type . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5.1">5.1</a>. LISP Packet Types . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5.2">5.2</a>. Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Locator/ID Separation Protocol (LISP) base specification,
[<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>], 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
[<a href="#ref-LISP-DDT" title=""LISP Delegated Database Tree"">LISP-DDT</a>], [<a href="#ref-LISP-MN-EXT">LISP-MN-EXT</a>], [<a href="#ref-LISP-BULK">LISP-BULK</a>], [<a href="#ref-NAT-LISP" title=""NAT traversal for LISP"">NAT-LISP</a>], or
[<a href="#ref-LISP-SUBSCRIBE">LISP-SUBSCRIBE</a>]. 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
<a href="#section-5">Section 5</a>).
Because of the limited type space [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>] 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 <a href="#section-3">Section 3</a>).
<span class="grey">Boucadair & Jacquenet Experimental [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc8113">RFC 8113</a> LISP Packet Type Allocations March 2017</span>
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.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language</span>
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 [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. LISP Shared Extension Message Type</span>
Figure 1 depicts the common format of the LISP shared extension
message. The type field MUST be set to 15 (see <a href="#section-5">Section 5</a>).
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
The "Sub-type" field conveys a unique identifier that MUST be
registered with IANA (see <a href="#section-5.2">Section 5.2</a>).
The exact structure of the 'extension-specific' portion of the
message is specified in the corresponding specification document.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document does not introduce any additional security issues other
than those discussed in [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>].
<span class="grey">Boucadair & Jacquenet Experimental [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc8113">RFC 8113</a> LISP Packet Type Allocations March 2017</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. LISP Packet Types</span>
IANA has created a new protocol registry for LISP Packet Types,
numbered 0-15. The registry is initially populated with the
following values:
Message Code Reference
================================= ==== ===============
Reserved 0 [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>]
LISP Map-Request 1 [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>]
LISP Map-Reply 2 [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>]
LISP Map-Register 3 [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>]
LISP Map-Notify 4 [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>]
LISP Encapsulated Control Message 8 [<a href="./rfc6830" title=""The Locator/ID Separation Protocol (LISP)"">RFC6830</a>]
LISP Shared Extension Message 15 [<a href="./rfc8113">RFC8113</a>]
The values in the ranges 5-7 and 9-14 can be assigned via Standards
Action [<a href="./rfc5226" title="">RFC5226</a>]. Documents that request for a new LISP packet type
may indicate a preferred value in the corresponding IANA sections.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Sub-Types</span>
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.
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.
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.
<span class="grey">Boucadair & Jacquenet Experimental [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc8113">RFC 8113</a> LISP Packet Type Allocations March 2017</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="https://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
DOI 10.17487/RFC5226, May 2008,
<<a href="https://www.rfc-editor.org/info/rfc5226">http://www.rfc-editor.org/info/rfc5226</a>>.
[<a id="ref-RFC6830">RFC6830</a>] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
Locator/ID Separation Protocol (LISP)", <a href="./rfc6830">RFC 6830</a>,
DOI 10.17487/RFC6830, January 2013,
<<a href="https://www.rfc-editor.org/info/rfc6830">http://www.rfc-editor.org/info/rfc6830</a>>.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-LISP-BULK">LISP-BULK</a>]
Boucadair, M. and C. Jacquenet, "LISP Mapping Bulk
Retrieval", Work in Progress,
<a href="./draft-boucadair-lisp-bulk-04">draft-boucadair-lisp-bulk-04</a>, February 2017.
[<a id="ref-LISP-DDT">LISP-DDT</a>] Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A.
Smirnov, "LISP Delegated Database Tree", Work in
Progress, <a href="./draft-ietf-lisp-ddt-09">draft-ietf-lisp-ddt-09</a>, January 2017.
[<a id="ref-LISP-MN-EXT">LISP-MN-EXT</a>]
Wang, J., Meng, Y., and N. Zhao, "LISP Mobile Node
extension", Work in Progress,
<a href="./draft-zhao-lisp-mn-extension-02">draft-zhao-lisp-mn-extension-02</a>, October 2011.
[<a id="ref-LISP-SUBSCRIBE">LISP-SUBSCRIBE</a>]
Boucadair, M. and C. Jacquenet, <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22LISP+Subscription%22'>"LISP Subscription"</a>, Work
in Progress, <a href="./draft-boucadair-lisp-subscribe-04">draft-boucadair-lisp-subscribe-04</a>, February
2017.
[<a id="ref-NAT-LISP">NAT-LISP</a>] Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino,
F., and C. White, "NAT traversal for LISP", Work in
Progress, <a href="./draft-ermagan-lisp-nat-traversal-11">draft-ermagan-lisp-nat-traversal-11</a>, August
2016.
<span class="grey">Boucadair & Jacquenet Experimental [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc8113">RFC 8113</a> LISP Packet Type Allocations March 2017</span>
Acknowledgments
This work is partly funded by ANR LISP-Lab project #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.
Authors' Addresses
Mohamed Boucadair
Orange
Rennes 35000
France
Email: [email protected]
Christian Jacquenet
Orange
Rennes 35000
France
Email: [email protected]
Boucadair & Jacquenet Experimental [Page 6]
Annotations
Select text to annotate