| rfc9012v3.txt | rfc9012.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) K. Patel | Internet Engineering Task Force (IETF) K. Patel | |||
| Request for Comments: 9012 Arrcus, Inc | Request for Comments: 9012 Arrcus, Inc | |||
| Obsoletes: 5512, 5566 G. Van de Velde | Obsoletes: 5512, 5566 G. Van de Velde | |||
| Updates: 5640 Nokia | Updates: 5640 Nokia | |||
| Category: Standards Track S. Sangli | Category: Standards Track S. Sangli | |||
| ISSN: 2070-1721 J. Scudder | ISSN: 2070-1721 J. Scudder | |||
| Juniper Networks | Juniper Networks | |||
| March 2021 | April 2021 | |||
| The BGP Tunnel Encapsulation Attribute | The BGP Tunnel Encapsulation Attribute | |||
| Abstract | Abstract | |||
| This document defines a BGP path attribute known as the "Tunnel | This document defines a BGP path attribute known as the "Tunnel | |||
| Encapsulation attribute", which can be used with BGP UPDATEs of | Encapsulation attribute", which can be used with BGP UPDATEs of | |||
| various Subsequent Address Family Identifiers (SAFIs) to provide | various Subsequent Address Family Identifiers (SAFIs) to provide | |||
| information needed to create tunnels and their corresponding | information needed to create tunnels and their corresponding | |||
| encapsulation headers. It provides encodings for a number of tunnel | encapsulation headers. It provides encodings for a number of tunnel | |||
| skipping to change at line 314 ¶ | skipping to change at line 314 ¶ | |||
| encapsulation header itself contains a "virtual network identifier". | encapsulation header itself contains a "virtual network identifier". | |||
| This document provides a mechanism that allows one to signal (by | This document provides a mechanism that allows one to signal (by | |||
| using sub-TLVs of the Tunnel Encapsulation attribute) how one wants | using sub-TLVs of the Tunnel Encapsulation attribute) how one wants | |||
| to use the embedded label when the tunnel encapsulation has its own | to use the embedded label when the tunnel encapsulation has its own | |||
| Virtual Network Identifier field. | Virtual Network Identifier field. | |||
| [RFC5512] defines an Encapsulation Extended Community that can be | [RFC5512] defines an Encapsulation Extended Community that can be | |||
| used instead of the Tunnel Encapsulation attribute under certain | used instead of the Tunnel Encapsulation attribute under certain | |||
| circumstances. This document describes how the Encapsulation | circumstances. This document describes how the Encapsulation | |||
| Extended Community can be used in a backwards-compatible fashion (see | Extended Community can be used in a backwards-compatible fashion (see | |||
| Section 4.1). It is possible to combine Tunnel Encapsulation | Section 4.1). It is possible to combine Encapsulation Extended | |||
| Extended Communities and Tunnel Encapsulation attributes in the same | Communities and Tunnel Encapsulation attributes in the same BGP | |||
| BGP UPDATE in this manner. | UPDATE in this manner. | |||
| 1.5. Update to RFC 5640 | 1.5. Update to RFC 5640 | |||
| This document updates [RFC5640] by indicating that the Load-Balancing | This document updates [RFC5640] by indicating that the Load-Balancing | |||
| Block sub-TLV MAY be included in any Tunnel Encapsulation attribute | Block sub-TLV MAY be included in any Tunnel Encapsulation attribute | |||
| where load balancing is desired. | where load balancing is desired. | |||
| 1.6. Effects of Obsoleting RFC 5566 | 1.6. Effects of Obsoleting RFC 5566 | |||
| This specification obsoletes RFC 5566. This has the effect of, in | This specification obsoletes RFC 5566. This has the effect of, in | |||
| skipping to change at line 1877 ¶ | skipping to change at line 1877 ¶ | |||
| +==============+=================+===========+ | +==============+=================+===========+ | |||
| | 0 | V (VN-ID) | RFC 9012 | | | 0 | V (VN-ID) | RFC 9012 | | |||
| +--------------+-----------------+-----------+ | +--------------+-----------------+-----------+ | |||
| | 1 | M (MAC Address) | RFC 9012 | | | 1 | M (MAC Address) | RFC 9012 | | |||
| +--------------+-----------------+-----------+ | +--------------+-----------------+-----------+ | |||
| Table 6 | Table 6 | |||
| 14.9. Embedded Label Handling Sub-TLV | 14.9. Embedded Label Handling Sub-TLV | |||
| IANA has create a registry named "Embedded Label Handling Sub-TLVs" | IANA has created a registry named "Embedded Label Handling Sub-TLVs" | |||
| under the "Border Gateway Protocol (BGP) Tunnel Encapsulation" | under the "Border Gateway Protocol (BGP) Tunnel Encapsulation" | |||
| grouping [IANA-BGP-TUNNEL-ENCAP]. The registration policy for this | grouping [IANA-BGP-TUNNEL-ENCAP]. The registration policy for this | |||
| registry is "Standards Action". The minimum possible value is 0, and | registry is "Standards Action". The minimum possible value is 0, and | |||
| the maximum is 255. | the maximum is 255. | |||
| The initial values for this new registry are indicated in Table 7. | The initial values for this new registry are indicated in Table 7. | |||
| +=======+=====================================+===========+ | +=======+=====================================+===========+ | |||
| | Value | Description | Reference | | | Value | Description | Reference | | |||
| +=======+=====================================+===========+ | +=======+=====================================+===========+ | |||
| End of changes. 3 change blocks. | ||||
| 5 lines changed or deleted | 5 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||