metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 5512: The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9012.

Current document in this lineage: RFC 9012 — The BGP Tunnel Encapsulation Attribute

In plain English — editorial summary, not part of the RFC

In certain situations, transporting a packet from one Border Gateway Protocol (BGP) speaker to another (the BGP next hop) requires that the packet be encapsulated by the first BGP speaker and decapsulated by the second. To support these situations, there needs to be some agreement between the two BGP speakers with regard to the "encapsulation information", i.e., the format of the encapsulation header as well as the contents of various fields of the header. The encapsulation information need not be signaled for all encapsulation types. In cases where signaling is required (such as Layer Two Tunneling Protocol - Version 3 (L2TPv3) or Generic Routing Encapsulation (GRE) with key), this document specifies a method by which BGP speakers can signal encapsulation information to each other. The signaling is done by sending BGP updates using the Encapsulation Subsequent Address Family Identifier (SAFI) and the IPv4 or IPv6 Address Family Identifier (AFI). In cases where no encapsulation information needs to be signaled (such as GRE without key), this document specifies a BGP extended community that can be attached to BGP UPDATE messages that carry payload prefixes in order to indicate the encapsulation protocol type to be used. [STANDARDS-TRACK]

Document record

Document ID
RFC5512
Published
April 2009
Authors
P. Mohapatra; E. Rosen
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
13
Also known as
—
Obsoleted by:
RFC 9012

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 5512 (2009)
  2. RFC 5566 (2009)
  3. 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.

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?

canonical URL: /rfc/5512-the-bgp-encapsulation-subsequent-address-family-identifier-safi-and-the-bgp-tunn