RFC 5566: BGP IPsec 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
The BGP Encapsulation Subsequent Address Family Identifier (SAFI) provides a method for the dynamic exchange of encapsulation information and for the indication of encapsulation protocol types to be used for different next hops. Currently, support for Generic Routing Encapsulation (GRE), Layer 2 Tunneling Protocol (L2TPv3), and IP in IP tunnel types are defined. This document defines support for IPsec tunnel types. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5566
- Published
- June 2009
- Authors
- L. Berger; R. White; E. Rosen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- 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.
- 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 5640Load-Balancing for Mesh SoftwiresUpdated
August 2009
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 56684-Octet AS Specific BGP Extended CommunityCurrent
October 2009
- RFC 5701IPv6 Address Specific BGP Extended Community AttributeUpdated
November 2009
- RFC 5292Address-Prefix-Based Outbound Route Filter for BGP-4Current
August 2008
- RFC 5065Autonomous System Confederations for BGPUpdated
August 2007
- RFC 5004Avoid BGP Best Path Transitions from One External to AnotherCurrent
September 2007
- RFC 4893BGP Support for Four-octet AS Number SpaceObsoleted
May 2007
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?