Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
draft-ietf-lisp-rfc8113bis-03

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03

LISP                                                        M. Boucadair
Internet-Draft                                              C. Jacquenet
Obsoletes: 8113 (if approved)                                     Orange
Intended status: Standards Track                        January 25, 2019
Expires: July 29, 2019

 Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA
                  Registry for Packet Type Allocations
                     draft-ietf-lisp-rfc8113bis-03

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.

   This document obsoletes RFC 8113.

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 https://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 July 29, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Boucadair & Jacquenet     Expires July 29, 2019                 [Page 1]
Internet-Draft        LISP Packet Type Allocations          January 2019

   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
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  LISP Shared Extension Message Type  . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     5.1.  LISP Packet Types . . . . . . . . . . . . . . . . . . . .   3
     5.2.  Sub-Types . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Changes from RFC 8113 . . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The Locator/ID Separation Protocol (LISP) base specification,
   [I-D.ietf-lisp-rfc6833bis], defines a set of primitives that are
   identified with a packet type code.  Several extensions have been
   proposed to add more LISP functionalities.  It is expected that
   additional LISP extensions will be proposed in the future.

   The "LISP Packet Types" IANA registry (see Section 5) is used to ease
   the tracking of LISP message types.

   Because of the limited type space [I-D.ietf-lisp-rfc6833bis] and the
   need to conduct experiments to assess new LISP extensions, this
   document specifies a shared LISP extension message type and describes
   a procedure for registering LISP shared extension sub-types (see
   Section 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.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119][RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Boucadair & Jacquenet     Expires July 29, 2019                 [Page 2]
Internet-Draft        LISP Packet Type Allocations          January 2019

3.  LISP Shared Extension Message Type

   Figure 1 depicts the common format of the LISP shared extension
   message.  The type field MUST be set to 15 (see Section 5).

        0                   1                   2                   3