draft-ietf-lisp-type-iana-03.txt   draft-ietf-lisp-type-iana-04.txt 
Network Working Group M. Boucadair Network Working Group M. Boucadair
Internet-Draft C. Jacquenet Internet-Draft C. Jacquenet
Intended status: Standards Track Orange Intended status: Experimental Orange
Expires: April 23, 2017 October 20, 2016 Expires: June 3, 2017 November 30, 2016
LISP Experimental Message & IANA Registry for LISP Packet Type LISP Shared Extension Message & IANA Registry for LISP Packet Type
Allocations Allocations
draft-ietf-lisp-type-iana-03 draft-ietf-lisp-type-iana-04
Abstract Abstract
This document defines a registry for LISP Packet Type allocations. This document defines a registry for LISP Packet Type allocations.
It also specifies a shared LISP message type for experimentation It also specifies a LISP shared message type for defining future
purposes. extensions and conducting experiments without consuming a LISP packet
type codepoint for each extension.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. 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 Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 39 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 23, 2017. This Internet-Draft will expire on June 3, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 Message Type for Experimentations . . . . . . . . . . . 3 2. LISP Shared Extension Message Type . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
4.1. LISP Packet Types . . . . . . . . . . . . . . . . . . . . 3 4.1. LISP Packet Types . . . . . . . . . . . . . . . . . . . . 3
4.2. Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Sub-Types . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative references . . . . . . . . . . . . . . . . . . 4 6.1. Normative references . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
skipping to change at page 2, line 39 skipping to change at page 2, line 40
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], [I-D.ietf-lisp-ddt], [I-D.zhao-lisp-mn-extension],
[I-D.boucadair-lisp-bulk], [I-D.ermagan-lisp-nat-traversal], or [I-D.boucadair-lisp-bulk], [I-D.ermagan-lisp-nat-traversal], or
[I-D.boucadair-lisp-subscribe]. It is expected that additional LISP [I-D.boucadair-lisp-subscribe]. It is expected that additional LISP
extensions 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 4).
Because of the limited type space [RFC6830], this document specifies Because of the limited type space [RFC6830] and the need to conduct
a shared LISP message type for experimentation purposes and proposes experiments to assess new LISP extensions, this document specifies a
a procedure for registering LISP experiment sub-types (see Section 2) shared LISP extension message type and proposes a procedure for
that make use of additional LISP capabilities associated with this registering LISP shared extension sub-types (see Section 2).
message type. Concretely, one single LISP message type code is Concretely, one single LISP message type code is dedicated to future
dedicated to experiments; sub-types are used to uniquely identify a LISP extensions; sub-types are used to uniquely identify a given LISP
given LISP experimental message. These identifiers are selected by extension making use of the shared LISP extension message type.
the author(s) of the corresponding LISP specification that introduces These identifiers are selected by the author(s) of the corresponding
a new experimental message type. LISP specification that introduces a new LISP extension message type.
2. LISP Message Type for Experimentations 2. LISP Shared Extension Message Type
Figure 1 depicts a common LISP experimental message type. The type Figure 1 depicts the common format of the LISP shared extension
field MUST be set to 15 (see Section 4). message. The type field MUST be set to 15 (see Section 4).
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 | experiment-specific | |Type=15| Sub-type | extension-specific |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// experiment-specific // // extension-specific //
// // // //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Common LISP Experimental Message Type Figure 1: LISP Shared Extension Message Type
The "Sub-type" field conveys a unique identifier that is assigned on The "Sub-type" field conveys a unique identifier that is assigned on
a First Come, First Served (FCFS) basis [RFC5226]. These identifiers a First Come, First Served (FCFS) basis [RFC5226]. These identifiers
are registered with IANA (see Section 4.2). are registered with IANA (see Section 4.2).
The exact structure of the 'experiment-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 3. 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 4. IANA Considerations
4.1. LISP Packet Types 4.1. LISP Packet Types
skipping to change at page 3, line 49 skipping to change at page 3, line 49
the following values: the 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 Experimental Message 15 [This document] LISP Shared Extension Message 15 [This document]
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.
The value 15 is reserved for Experimental Use [RFC5226]. The value 15 is reserved for Experimental Use [RFC5226].
4.2. Sub-Types 4.2. Sub-Types
IANA is requested to create a "LISP Experimental Message Sub-types" IANA is requested to create a "LISP Shared Extension Message type
registry. No initial values are assigned at the creation of the Sub-types" registry. No initial values are assigned at the creation
registry; (0-4095) are available for future assignments. of the registry; (0-4095) are available for future assignments.
Entries are assigned on a FCFS basis. Entries are assigned on a FCFS basis.
The registration procedure should provide IANA with the desired The registration procedure should provide IANA with the desired
codepoint and a point of contact. Providing a short description codepoint and a point of contact. Providing a short description
(together with an acronym, if relevant) of the foreseen usage of the (together with an acronym, if relevant) of the foreseen usage of the
experimental message is also encouraged. extension message is also encouraged.
5. Acknowledgments 5. Acknowledgments
This work is partly funded by ANR LISP-Lab project #ANR-13-INFR- This work is partly funded by ANR LISP-Lab project #ANR-13-INFR-
009-X. 009-X.
Many thanks to Luigi Iannone and Dino Farinacci for the review. Many thanks to Luigi Iannone and Dino Farinacci 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
 End of changes. 17 change blocks. 
29 lines changed or deleted 32 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/