The BGP Tunnel Encapsulation Attribute
draft-ietf-idr-tunnel-encaps-21

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Authors Keyur Patel  , Gunter Van de Velde  , Srihari Sangli  , John Scudder 
Last updated 2021-01-07 (latest revision 2020-11-10)
Replaces draft-vandevelde-idr-remote-next-hop, draft-rosen-idr-tunnel-encaps
Stream Internent Engineering Task Force (IETF)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2020-11-13)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Alvaro Retana
Send notices to John Scudder <jgs@juniper.net>, aretana.ietf@gmail.com, Susan Hares <shares@ndzh.com>
IANA IANA review state Version Changed - Review Needed
IDR Working Group                                               K. Patel
Internet-Draft                                               Arrcus, Inc
Obsoletes: 5512, 5566 (if approved)                      G. Van de Velde
Updates: 5640 (if approved)                                        Nokia
Intended status: Standards Track                               S. Sangli
Expires: July 11, 2021                                        J. Scudder
                                                        Juniper Networks
                                                         January 7, 2021

                 The BGP Tunnel Encapsulation Attribute
                    draft-ietf-idr-tunnel-encaps-21

Abstract

   This document defines a BGP Path Attribute known as the "Tunnel
   Encapsulation Attribute", which can be used with BGP UPDATEs of
   various SAFIs to provide information needed to create tunnels and
   their corresponding encapsulation headers.  It provides encodings for
   a number of Tunnel Types along with procedures for choosing between
   alternate tunnels and routing packets into tunnels.

   This document obsoletes RFC 5512, which provided an earlier
   definition of the Tunnel Encapsulation Attribute.  RFC 5512 was never
   deployed in production.  Since RFC 5566 relies on RFC 5512, it is
   likewise obsoleted.  This document updates RFC 5640 by indicating
   that the Load-Balancing Block sub-TLV may be included in any Tunnel
   Encapsulation Attribute where load balancing is desired.

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 11, 2021.

Patel, et al.             Expires July 11, 2021                 [Page 1]
Internet-Draft       Tunnel Encapsulation Attribute         January 2021

Copyright Notice

   Copyright (c) 2021 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Brief Summary of RFC 5512 . . . . . . . . . . . . . . . .   4
     1.2.  Deficiencies in RFC 5512  . . . . . . . . . . . . . . . .   4
     1.3.  Use Case for The Tunnel Encapsulation Attribute . . . . .   5
     1.4.  Brief Summary of Changes from RFC 5512  . . . . . . . . .   6
     1.5.  Update to RFC 5640  . . . . . . . . . . . . . . . . . . .   7
     1.6.  Effects of Obsoleting RFC 5566  . . . . . . . . . . . . .   7
   2.  The Tunnel Encapsulation Attribute  . . . . . . . . . . . . .   8
   3.  Tunnel Encapsulation Attribute Sub-TLVs . . . . . . . . . . .   9
     3.1.  The Tunnel Egress Endpoint Sub-TLV (type code 6)  . . . .   9
       3.1.1.  Validating the Address Subfield . . . . . . . . . . .  11
     3.2.  Encapsulation Sub-TLVs for Particular Tunnel Types (type
           code 1) . . . . . . . . . . . . . . . . . . . . . . . . .  12
       3.2.1.  VXLAN (tunnel type 8) . . . . . . . . . . . . . . . .  12
       3.2.2.  NVGRE (tunnel type 9) . . . . . . . . . . . . . . . .  14
       3.2.3.  L2TPv3 (tunnel type 1)  . . . . . . . . . . . . . . .  16
       3.2.4.  GRE (tunnel type 2) . . . . . . . . . . . . . . . . .  16
       3.2.5.  MPLS-in-GRE (tunnel type 11)  . . . . . . . . . . . .  17
     3.3.  Outer Encapsulation Sub-TLVs  . . . . . . . . . . . . . .  17
       3.3.1.  DS Field (type code 7)  . . . . . . . . . . . . . . .  18
       3.3.2.  UDP Destination Port (type code 8)  . . . . . . . . .  18
     3.4.  Sub-TLVs for Aiding Tunnel Selection  . . . . . . . . . .  19
       3.4.1.  Protocol Type Sub-TLV (type code 2) . . . . . . . . .  19
       3.4.2.  Color Sub-TLV (type code 4) . . . . . . . . . . . . .  20
     3.5.  Embedded Label Handling Sub-TLV (type code 9) . . . . . .  20
     3.6.  MPLS Label Stack Sub-TLV (type code 10) . . . . . . . . .  21
     3.7.  Prefix-SID Sub-TLV (type code 11) . . . . . . . . . . . .  23
Show full document text