draft-ietf-lisp-type-iana-06.txt   rfc8113.txt 
Network Working Group M. Boucadair Internet Engineering Task Force (IETF) M. Boucadair
Internet-Draft C. Jacquenet Request for Comments: 8113 C. Jacquenet
Updates: 6830 (if approved) Orange Updates: 6830 Orange
Intended status: Experimental February 2, 2017 Category: Experimental March 2017
Expires: August 6, 2017 ISSN: 2070-1721
LISP Shared Extension Message & IANA Registry for LISP Packet Type Locator/ID Separation Protocol (LISP):
Allocations Shared Extension Message & IANA Registry for Packet Type Allocations
draft-ietf-lisp-type-iana-06
Abstract Abstract
This document defines a registry for Locator/ID Separation Protocol This document specifies a Locator/ID Separation Protocol (LISP)
(LISP) Packet Type allocations. It also specifies a LISP shared shared message type for defining future extensions and conducting
message type for defining future extensions and conducting
experiments without consuming a LISP packet type codepoint for each experiments without consuming a LISP packet type codepoint for each
extension. extension. It also defines a registry for LISP Packet Type
allocations, thus updating RFC 6830.
This document updates RFC6830 by defining a registry for LISP Packet
Types assignments.
Requirements Language
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 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for examination, experimental implementation, and
evaluation.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document defines an Experimental Protocol for the Internet
and may be updated, replaced, or obsoleted by other documents at any community. This document is a product of the Internet Engineering
time. It is inappropriate to use Internet-Drafts as reference Task Force (IETF). It represents the consensus of the IETF
material or to cite them other than as "work in progress." 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.
This Internet-Draft will expire on August 6, 2017. 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.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. LISP Shared Extension Message Type . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 3. LISP Shared Extension Message Type . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4.1. LISP Packet Types . . . . . . . . . . . . . . . . . . . . 3 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4.2. Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 4 5.1. LISP Packet Types . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 5.2. Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative references . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
The Locator/ID Separation Protocol (LISP, [RFC6830]) base The Locator/ID Separation Protocol (LISP) base specification,
specification defines a set of primitives that are identified with a [RFC6830], defines a set of primitives that are identified with a
packet type code. Several extensions have been proposed to add more packet type code. Several extensions have been proposed to add more
LISP functionalities. For example, new message types are proposed in LISP functionalities. For example, new message types are proposed in
[I-D.ietf-lisp-ddt], [I-D.zhao-lisp-mn-extension], [LISP-DDT], [LISP-MN-EXT], [LISP-BULK], [NAT-LISP], or
[I-D.boucadair-lisp-bulk], [I-D.ermagan-lisp-nat-traversal], or [LISP-SUBSCRIBE]. It is expected that additional LISP extensions
[I-D.boucadair-lisp-subscribe]. It is expected that additional LISP will be proposed in the future.
extensions will be proposed in the future.
In order to ease the tracking of LISP message types, this document In order to ease the tracking of LISP message types, this document
proposes to create a "LISP Packet Types" IANA registry (see proposes to create a "LISP Packet Types" IANA registry (see
Section 4). Section 5).
Because of the limited type space [RFC6830] and the need to conduct Because of the limited type space [RFC6830] and the need to conduct
experiments to assess new LISP extensions, this document specifies a experiments to assess new LISP extensions, this document specifies a
shared LISP extension message type and proposes a procedure for shared LISP extension message type and proposes a procedure for
registering LISP shared extension sub-types (see Section 2). registering LISP shared extension sub-types (see Section 3).
Concretely, one single LISP message type code is dedicated to future Concretely, one single LISP message type code is dedicated to future
LISP extensions; sub-types are used to uniquely identify a given LISP LISP extensions; sub-types are used to uniquely identify a given LISP
extension making use of the shared LISP extension message type. extension making use of the shared LISP extension message type.
These identifiers are selected by the author(s) of the corresponding These identifiers are selected by the author(s) of the corresponding
LISP specification that introduces a new LISP extension message type. LISP specification that introduces a new LISP extension message type.
2. LISP Shared Extension Message Type 2. Requirements Language
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].
3. LISP Shared Extension Message Type
Figure 1 depicts the common format of the LISP shared extension Figure 1 depicts the common format of the LISP shared extension
message. The type field MUST be set to 15 (see Section 4). message. The type field MUST be set to 15 (see Section 5).
0 1 2 3 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 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 | |Type=15| Sub-type | extension-specific |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// extension-specific // // extension-specific //
// // // //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: LISP Shared Extension Message Type Figure 1: LISP Shared Extension Message Type
The "Sub-type" field conveys a unique identifier that MUST be The "Sub-type" field conveys a unique identifier that MUST be
registered with IANA (see Section 4.2). registered with IANA (see Section 5.2).
The exact structure of the 'extension-specific' portion of the The exact structure of the 'extension-specific' portion of the
message is specified in the corresponding specification document. message is specified in the corresponding specification document.
3. Security Considerations 4. Security Considerations
This document does not introduce any additional security issues other This document does not introduce any additional security issues other
than those discussed in [RFC6830]. than those discussed in [RFC6830].
4. IANA Considerations 5. IANA Considerations
4.1. LISP Packet Types 5.1. LISP Packet Types
IANA is requested to create a new protocol registry for LISP Packet IANA has created a new protocol registry for LISP Packet Types,
Types, numbered 0-15. The registry must be initially populated with numbered 0-15. The registry is initially populated with the
the following values: following values:
Message Code Reference Message Code Reference
================================= ==== =============== ================================= ==== ===============
Reserved 0 [RFC6830] Reserved 0 [RFC6830]
LISP Map-Request 1 [RFC6830] LISP Map-Request 1 [RFC6830]
LISP Map-Reply 2 [RFC6830] LISP Map-Reply 2 [RFC6830]
LISP Map-Register 3 [RFC6830] LISP Map-Register 3 [RFC6830]
LISP Map-Notify 4 [RFC6830] LISP Map-Notify 4 [RFC6830]
LISP Encapsulated Control Message 8 [RFC6830] LISP Encapsulated Control Message 8 [RFC6830]
LISP Shared Extension Message 15 [This document] LISP Shared Extension Message 15 [RFC8113]
The values in the ranges 5-7 and 9-14 can be assigned via Standards 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 Action [RFC5226]. Documents that request for a new LISP packet type
may indicate a preferred value in the corresponding IANA sections. may indicate a preferred value in the corresponding IANA sections.
4.2. Sub-Types 5.2. Sub-Types
IANA is requested to create a "LISP Shared Extension Message type IANA has created the "LISP Shared Extension Message Type Sub-types"
Sub-types" registry. No initial values are assigned at the creation registry. No initial values are assigned at the creation of the
of the registry; (0-4095) are available for future assignments. registry; (0-4095) are available for future assignments.
The values in the range 0-1023 are assigned via Standards Action. The values in the range 0-1023 are assigned via Standards Action.
This range is provisioned to anticipate, in particular, the This range is provisioned to anticipate, in particular, the
exhaustion of the LISP Packet types. exhaustion of the LISP Packet types.
The values in 1024-4095 are assigned on a First Come, First Served The values in the range 1024-4095 are assigned on a First Come, First
(FCFS) basis. The registration procedure should provide IANA with Served (FCFS) basis. The registration procedure should provide IANA
the desired codepoint and a point of contact. Providing a short with the desired codepoint and a point of contact; providing a short
description (together with an acronym, if relevant) of the foreseen description (together with an acronym, if relevant) of the foreseen
usage of the extension message is also encouraged. usage of the extension message is also encouraged.
5. 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.
6. References 6. References
6.1. Normative references 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
Locator/ID Separation Protocol (LISP)", RFC 6830, Locator/ID Separation Protocol (LISP)", RFC 6830,
DOI 10.17487/RFC6830, January 2013, DOI 10.17487/RFC6830, January 2013,
<http://www.rfc-editor.org/info/rfc6830>. <http://www.rfc-editor.org/info/rfc6830>.
6.2. Informative References 6.2. Informative References
[I-D.boucadair-lisp-bulk] [LISP-BULK]
Boucadair, M. and C. Jacquenet, "LISP Mapping Bulk Boucadair, M. and C. Jacquenet, "LISP Mapping Bulk
Retrieval", draft-boucadair-lisp-bulk-03 (work in Retrieval", Work in Progress,
progress), July 2016. draft-boucadair-lisp-bulk-04, February 2017.
[I-D.boucadair-lisp-subscribe] [LISP-DDT] Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A.
Boucadair, M. and C. Jacquenet, "LISP Subscription", Smirnov, "LISP Delegated Database Tree", Work in
draft-boucadair-lisp-subscribe-03 (work in progress), July Progress, draft-ietf-lisp-ddt-09, January 2017.
[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-SUBSCRIBE]
Boucadair, M. and C. Jacquenet, "LISP Subscription", Work
in Progress, draft-boucadair-lisp-subscribe-04, February
2017.
[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. 2016.
[I-D.ermagan-lisp-nat-traversal] Acknowledgments
Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino,
F., and C. White, "NAT traversal for LISP", draft-ermagan-
lisp-nat-traversal-11 (work in progress), August 2016.
[I-D.ietf-lisp-ddt] This work is partly funded by ANR LISP-Lab project #ANR-13-INFR-
Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A. 009-X.
Smirnov, "LISP Delegated Database Tree", draft-ietf-lisp-
ddt-09 (work in progress), January 2017.
[I-D.zhao-lisp-mn-extension] Many thanks to Luigi Iannone, Dino Farinacci, and Alvaro Retana for
Wang, J., Meng, Y., and N. Zhao, "LISP Mobile Node the review.
extension", draft-zhao-lisp-mn-extension-02 (work in
progress), October 2011. Thanks to Geoff Huston for the RtgDir directorate review.
Authors' Addresses Authors' Addresses
Mohamed Boucadair Mohamed Boucadair
Orange Orange
Rennes 35000 Rennes 35000
France France
EMail: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
Christian Jacquenet Christian Jacquenet
Orange Orange
Rennes 35000 Rennes 35000
France France
EMail: christian.jacquenet@orange.com Email: christian.jacquenet@orange.com
 End of changes. 34 change blocks. 
97 lines changed or deleted 94 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/