LISP Generic Protocol Extension
draft-ietf-lisp-gpe-03

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

• Versions
• 00
• 01
• 02
• 03

Internet Engineering Task Force                            F. Maino, Ed.
Internet-Draft                                                     Cisco
Intended status: Standards Track                                J. Lemon
Expires: October 7, 2018                                        Broadcom
                                                              P. Agarwal
                                                                Innovium
                                                                D. Lewis
                                                                M. Smith
                                                                   Cisco
                                                           April 5, 2018

                    LISP Generic Protocol Extension
                         draft-ietf-lisp-gpe-03

Abstract

   This document describes extending the Locator/ID Separation Protocol
   (LISP) Data-Plane, via changes to the LISP header, to support multi-
   protocol encapsulation.

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 October 7, 2018.

Copyright Notice

   Copyright (c) 2018 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

Maino, et al.            Expires October 7, 2018                [Page 1]
Internet-Draft       LISP Generic Protocol Extension          April 2018

   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
     1.1.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Definition of Terms . . . . . . . . . . . . . . . . . . .   3
   2.  LISP Header Without Protocol Extensions . . . . . . . . . . .   3
   3.  Generic Protocol Extension for LISP (LISP-GPE)  . . . . . . .   3
   4.  Backward Compatibility  . . . . . . . . . . . . . . . . . . .   4
     4.1.  Use of "Multiple Data-Planes" LCAF to Determine ETR
           Capabilities  . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Type of Service . . . . . . . . . . . . . . . . . . . . .   6
     4.3.  VLAN Identifier (VID) . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgements and Contributors . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   LISP Data-Plane, as defined in in [I-D.ietf-lisp-rfc6830bis], defines
   an encapsulation format that carries IPv4 or IPv6 (henceforth
   referred to as IP) packets in a LISP header and outer UDP/IP
   transport.

   The LISP Data-Plane header does not specify the protocol being
   encapsulated and therefore is currently limited to encapsulating only
   IP packet payloads.  Other protocols, most notably VXLAN [RFC7348]
   (which defines a similar header format to LISP), are used to
   encapsulate L2 protocols such as Ethernet.

   This document defines an extension for the LISP header, as defined in
   [I-D.ietf-lisp-rfc6830bis], to indicate the inner protocol, enabling
   the encapsulation of Ethernet, IP or any other desired protocol all
   the while ensuring compatibility with existing LISP deployments.

   A flag in the LISP header, called the P-bit, is used to signal the
   presence of the 8-bit Next Protocol field.  The Next Protocol field,
   when present, uses 8 bits of the field allocated to the echo-noncing
   and map-versioning features.  The two features are still available,
   albeit with a reduced length of Nonce and Map-Version.