Browse Prior Art Database

Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations (RFC8113)

IP.com Disclosure Number: IPCOM000249637D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-10
Document File: 12 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Boucadair: AUTHOR [+2]

Abstract

The Locator/ID Separation Protocol (LISP) base specification, [RFC6830], 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 [LISP-DDT], [LISP-MN-EXT], [LISP-BULK], [NAT-LISP], or [LISP-SUBSCRIBE]. It is expected that additional LISP extensions will be proposed in the future.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 25% of the total text.

Internet Engineering Task Force (IETF)                      M. Boucadair Request for Comments: 8113                                  C. Jacquenet Updates: 6830                                                     Orange Category: Experimental                                        March 2017 ISSN: 2070-1721

                  Locator/ID Separation Protocol (LISP):   Shared Extension Message & IANA Registry for Packet Type Allocations

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.

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 Section 2 of RFC 7841.

   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.

 Boucadair & Jacquenet         Experimental                      [Page 1]
 RFC 8113              LISP Packet Type Allocations            March 2017

 Copyright Notice

   Copyright (c) 2017 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    2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3    3.  LISP Shared Extension Message Type  . . . . . . . . . . . . .   3    4.  Security Considerations...