RFC 9012: The BGP Tunnel Encapsulation Attribute
In plain English — editorial summary, not part of the RFC
This document defines a BGP path attribute known as the "Tunnel Encapsulation attribute", which can be used with BGP UPDATEs of various Subsequent Address Family Identifiers (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.
Document record
- Document ID
- RFC9012
- Published
- April 2021
- Authors
- K. Patel; G. Van de Velde; S. Sangli; J. Scudder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 41
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 5512 (2009)
- RFC 5566 (2009)
- RFC 9012 (2021)
Read the full history of The BGP Tunnel Encapsulation Attribute →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9013OSPF Advertisement of Tunnel EncapsulationsCurrent
April 2021
- RFC 9003Extended BGP Administrative Shutdown CommunicationCurrent
January 2021
- RFC 9072Extended Optional Parameters Length for BGP OPEN MessageCurrent
July 2021
- RFC 8950Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next HopCurrent
November 2020
- RFC 9086Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing BGP Egress Peer EngineeringCurrent
August 2021
- RFC 9125Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment RoutingCurrent
August 2021
- RFC 9127YANG Data Model for Bidirectional Forwarding Detection (BFD)Updated
October 2021
- RFC 9234Route Leak Prevention and Detection Using Roles in UPDATE and OPEN MessagesCurrent
May 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?