The BGP Tunnel Encapsulation Attribute
draft-ietf-idr-tunnel-encaps-20
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 | 2020-12-03 (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::Revised I-D Needed | |
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 | IANA OK - Actions Needed |
IDR Working Group K. Patel Internet-Draft Arrcus, Inc Obsoletes: 5512, 5566, 5640 (if G. Van de Velde approved) Nokia Intended status: Standards Track S. Sangli Expires: May 14, 2021 J. Scudder Juniper Networks November 10, 2020 The BGP Tunnel Encapsulation Attribute draft-ietf-idr-tunnel-encaps-20 Abstract RFC 5512 defines a BGP Path Attribute known as the "Tunnel Encapsulation Attribute". This attribute allows one to specify a set of tunnels. For each such tunnel, the attribute can provide the information needed to create the tunnel and the corresponding encapsulation header. The attribute can also provide information that aids in choosing whether a particular packet is to be sent through a particular tunnel. RFC 5512 states that the attribute is only carried in BGP UPDATEs that use the "Encapsulation Subsequent Address Family (Encapsulation SAFI)". This document deprecates the Encapsulation SAFI (which has never been used in production), and specifies semantics for the attribute when it is carried in UPDATEs of certain other SAFIs. This document adds support for additional Tunnel Types, and allows a remote tunnel endpoint address to be specified for each tunnel. This document also provides support for specifying fields of any inner or outer encapsulations that may be used by a particular tunnel. This document obsoletes RFC 5512. Since RFCs 5566 and 5640 rely on RFC 5512, they are likewise obsoleted. 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 Patel, et al. Expires May 14, 2021 [Page 1] Internet-Draft Tunnel Encapsulation Attribute November 2020 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 May 14, 2021. Copyright Notice Copyright (c) 2020 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. Effects of Obsoleting RFCs 5566 and 5640 . . . . . . . . 7 2. The Tunnel Encapsulation Attribute . . . . . . . . . . . . . 8 3. Tunnel Encapsulation Attribute Sub-TLVs . . . . . . . . . . . 9 3.1. The Tunnel Egress Endpoint Sub-TLV . . . . . . . . . . . 9 3.1.1. Validating the Address Field . . . . . . . . . . . . 11 3.2. Encapsulation Sub-TLVs for Particular Tunnel Types . . . 12 3.2.1. VXLAN . . . . . . . . . . . . . . . . . . . . . . . . 12 3.2.2. NVGRE . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3. L2TPv3 . . . . . . . . . . . . . . . . . . . . . . . 16 3.2.4. GRE . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.2.5. MPLS-in-GRE . . . . . . . . . . . . . . . . . . . . . 17 3.3. Outer Encapsulation Sub-TLVs . . . . . . . . . . . . . . 17 3.3.1. DS Field . . . . . . . . . . . . . . . . . . . . . . 18 3.3.2. UDP Destination Port . . . . . . . . . . . . . . . . 18 3.4. Sub-TLVs for Aiding Tunnel Selection . . . . . . . . . . 18 3.4.1. Protocol Type Sub-TLV . . . . . . . . . . . . . . . . 19Show full document text