The BGP Tunnel Encapsulation Attribute
RFC 9012
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2021-07-28
|
(System) | IANA registries were updated to include RFC9012 |
|
2021-04-30
|
Bernie Volz | Closed request for Telechat review by INTDIR with state 'Overtaken by Events' |
|
2021-04-30
|
Bernie Volz | Closed request for Telechat review by INTDIR with state 'Overtaken by Events' |
|
2021-04-27
|
(System) | Received changes through RFC Editor sync (created alias RFC 9012, changed abstract to 'This document defines a BGP path attribute known as the "Tunnel … Received changes through RFC Editor sync (created alias RFC 9012, changed abstract to '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.', changed pages to 41, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-04-27, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-idr-tunnel-encaps and RFC 5512, created obsoletes relation between draft-ietf-idr-tunnel-encaps and RFC 5566, created updates relation between draft-ietf-idr-tunnel-encaps and RFC 5640) |
|
2021-04-27
|
(System) | RFC published |