LISP Experimental Message & IANA Registry for LISP Packet Type Allocations
draft-ietf-lisp-type-iana-01

Abstract

This document defines a registry for LISP Packet Type allocations. It also specifies a shared LISP message type for experimentation purposes.

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

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on March 12, 2017.

Copyright Notice

Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.

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.

Table of Contents

• 1. Introduction
• 2. LISP Message Type for Experimentations
• 3. Security Considerations
• 4. IANA Considerations
• 4.1. LISP Packet Types
• 4.2. Sub-Types
• 5. Acknowledgments
• 6. References
• 6.1. Normative references
• 6.2. Informative References
• Authors' Addresses

1. Introduction

The Locator/ID Separation Protocol (LISP, [RFC6830] ) base specification 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 [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-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 4).

Because of the limited type space [RFC6830], this document specifies a shared LISP message type for experimentation purposes and proposes a procedure for registering LISP experiment sub-types (see Section 2) that make use of additional LISP capabilities associated with this message type. Concretely, one single LISP message type code is dedicated to experiments; sub-types are used to uniquely identify a given LISP experimental message. These identifiers are selected by the author(s) of the corresponding LISP specification that introduces a new experimental message type.

2. LISP Message Type for Experimentations

Figure 1 depicts a common LISP experimental message type. The type field MUST be set to 15 (see Section 4).

        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       |  experiment-specific          |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       //                   experiment-specific                       //
       //                                                             //
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

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 Experimental Message         15   [This document]