Using the BGP Tunnel Encapsulation Attribute without the BGP Encapsulation SAFI
draft-ietf-idr-tunnel-encaps-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (idr WG)
|
|
Last updated |
|
2015-08-19
|
|
Replaces |
|
draft-rosen-idr-tunnel-encaps
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
IDR Working Group E. Rosen, Ed.
Internet-Draft Juniper Networks, Inc.
Updates: 5512 (if approved) K. Patel
Intended status: Standards Track Cisco Systems
Expires: February 20, 2016 G. Van de Velde
Alcatel-Lucent
August 19, 2015
Using the BGP Tunnel Encapsulation Attribute without the BGP
Encapsulation SAFI
draft-ietf-idr-tunnel-encaps-00
Abstract
RFC 5512 defines a BGP Path Attribute known as the "Tunnel
Encapsulation Attribute". This attribute allows one to specify a set
of tunnels. For each such tunnel, the attribute can provide
additional information used to create a tunnel and the corresponding
encapsulation header, and can also provide information that aids in
choosing whether a particular packet is to be sent through a
particular tunnel. RFC 5512 states that the attribute is only
carried in BGP UPDATEs that have the "Encapsulation Subsequent
Address Family (Encapsulation SAFI)". This document updates RFC 5512
by deprecating the Encapsulation SAFI (which has never been used),and
by specifying semantics for the attribute when it is carried in
UPDATEs of certain other SAFIs. This document also extends the
attribute by enabling it to carry additional information needed to
create the encapsulation headers additional tunnel types not
mentioned in RFC 5512. Finally, this document also extends the
attribute by allowing it to specify a remote tunnel endpoint address
for each tunnel.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
Rosen, et al. Expires February 20, 2016 [Page 1]
Internet-Draft Tunnel Encapsulation Attribute August 2015
This Internet-Draft will expire on February 20, 2016.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Tunnel Encapsulation Attribute Sub-TLVs . . . . . . . . . . . 5
2.1. The Remote Endpoint Sub-TLV . . . . . . . . . . . . . . . 5
2.2. Encapsulation Sub-TLVs for Particular Tunnel Types . . . 8
2.2.1. VXLAN . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2.2. VXLAN-GPE . . . . . . . . . . . . . . . . . . . . . . 9
2.2.3. NVGRE . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.4. GTP . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.5. MPLS-in-GRE . . . . . . . . . . . . . . . . . . . . . 12
2.3. Outer Encapsulation Sub-TLVs . . . . . . . . . . . . . . 13
2.3.1. IPv4 DS Field . . . . . . . . . . . . . . . . . . . . 13
2.3.2. UDP Destination Port . . . . . . . . . . . . . . . . 13
2.4. Embedded Label Handling Sub-TLV . . . . . . . . . . . . . 14
3. Tunnel Encapsulation Extended Community . . . . . . . . . . . 15
4. Semantics and Usage of the Tunnel Encapsulation
attribute . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5. Routing Considerations . . . . . . . . . . . . . . . . . . . 18
5.1. No Impact on BGP Decision Process . . . . . . . . . . . . 18
5.2. Looping, Infinite Stacking, Etc. . . . . . . . . . . . . 19
6. Recursive Next Hop Resolution . . . . . . . . . . . . . . . . 19
7. Use of Virtual Network Identifiers and Embedded Labels
when Imposing a Tunnel Encapsulation . . . . . . . . . . . . 20
7.1. Unlabeled Address Families . . . . . . . . . . . . . . . 20
Show full document text