API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 5512
[SUPERSEDED]

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

Metadata

Publisher
IETF
Doc Type
Standard
Pages
13
Abstract
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]
Publication Date
2009-04-01
Status Note
Proposed Standard
DOI
10.17487/RFC5512
Link
https://doi.org/10.17487/RFC5512
Author(s)
Prodosh Mohapatra
Eric C. Rosen
Keyword(s)
BGP, Encapsulation, Encap SAFI, Tunnel, Softwire, 4over6, 6over4
Latest version of IETF RFC 5512

Document Versions — IETF RFC 5512

  • ▶ IETF RFC 5512 (2009-04-01)
    THIS DOC [SUPERSEDED] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5512.json

Superseded by:
RFC9012 NOT IN REGISTRY

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5512, The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute. Available at https://doi.org/10.17487/RFC5512
Snippet:
IETF RFC 5512, The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute. Available at https://doi.org/10.17487/RFC5512

HTML (ISO 690 compliant)

Preview:
IETF RFC 5512, The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute. Available at https://doi.org/10.17487/RFC5512
Snippet:
<span class="citation"><cite>IETF RFC 5512</cite>, The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute. Available at <a href="https://doi.org/10.17487/RFC5512" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5512</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5512, The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute
doi: 10.17487/RFC5512
url: https://doi.org/10.17487/RFC5512
Snippet:
<li>
<cite id="bib-rfc5512">IETF RFC 5512</cite>, The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute
<span class="doi">10.17487/RFC5512</span>
</li>

Referenced By