draft-rosen-idr-tunnel-encaps-01.txt   draft-rosen-idr-tunnel-encaps-02.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
IDR Working Group E. Rosen, Ed. IDR Working Group E. Rosen, Ed.
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Updates: 5512 (if approved) K. Patel Updates: 5512 (if approved) K. Patel
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: January 7, 2016 G. Van de Velde Expires: January 7, 2016 G. Van de Velde
Alcatel-Lucent Alcatel-Lucent
July 6, 2015 July 6, 2015
Using the BGP Tunnel Encapsulation Attribute without the BGP Using the BGP Tunnel Encapsulation Attribute without the BGP
Encapsulation SAFI Encapsulation SAFI
draft-rosen-idr-tunnel-encaps-01 draft-rosen-idr-tunnel-encaps-02
Abstract Abstract
RFC 5512 defines a BGP Path Attribute known as the "Tunnel RFC 5512 defines a BGP Path Attribute known as the "Tunnel
Encapsulation Attribute". This attribute allows one to specify a set Encapsulation Attribute". This attribute allows one to specify a set
of tunnels. For each such tunnel, the attribute can provide of tunnels. For each such tunnel, the attribute can provide
additional information used to create a tunnel and the corresponding additional information used to create a tunnel and the corresponding
encapsulation header, and can also provide information that aids in encapsulation header, and can also provide information that aids in
choosing whether a particular packet is to be sent through a choosing whether a particular packet is to be sent through a
particular tunnel. RFC 5512 states that the attribute is only particular tunnel. RFC 5512 states that the attribute is only
skipping to change at page 2, line 52 skipping to change at page 2, line 52
7. Use of Virtual Network Identifiers and Embedded Labels 7. Use of Virtual Network Identifiers and Embedded Labels
when Imposing a Tunnel Encapsulation . . . . . . . . . . . . 19 when Imposing a Tunnel Encapsulation . . . . . . . . . . . . 19
7.1. Unlabeled Address Families . . . . . . . . . . . . . . . 20 7.1. Unlabeled Address Families . . . . . . . . . . . . . . . 20
7.2. Labeled Address Families . . . . . . . . . . . . . . . . 20 7.2. Labeled Address Families . . . . . . . . . . . . . . . . 20
7.2.1. When a Valid VNID has been Signaled . . . . . . . . . 20 7.2.1. When a Valid VNID has been Signaled . . . . . . . . . 20
7.2.2. When a Valid VNID has not been Signaled . . . . . . . 21 7.2.2. When a Valid VNID has not been Signaled . . . . . . . 21
7.2.3. Applicability Restrictions . . . . . . . . . . . . . 21 7.2.3. Applicability Restrictions . . . . . . . . . . . . . 21
8. Scoping . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 8. Scoping . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 22 9. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 22
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
11. Security Considerations . . . . . . . . . . . . . . . . . . . 24 11. Security Considerations . . . . . . . . . . . . . . . . . . . 25
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 26
13. Contributor Addresses . . . . . . . . . . . . . . . . . . . . 25 13. Contributor Addresses . . . . . . . . . . . . . . . . . . . . 26
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 26 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
14.1. Normative References . . . . . . . . . . . . . . . . . . 26 14.1. Normative References . . . . . . . . . . . . . . . . . . 26
14.2. Informative References . . . . . . . . . . . . . . . . . 26 14.2. Informative References . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
[RFC5512] defines a BGP Path Attribute known as the Tunnel [RFC5512] defines a BGP Path Attribute known as the Tunnel
Encapsulation attribute. This attribute consists of one or more Encapsulation attribute. This attribute consists of one or more
TLVs. Each TLV identifies a particular type of tunnel. Each TLV TLVs. Each TLV identifies a particular type of tunnel. Each TLV
also contains one or more sub-TLVs. Some of the sub-TLVs, e.g., the also contains one or more sub-TLVs. Some of the sub-TLVs, e.g., the
"Encapsulation sub-TLV", contain information that may be used to form "Encapsulation sub-TLV", contain information that may be used to form
the encapsulation header for the specified tunnel type. Other sub- the encapsulation header for the specified tunnel type. Other sub-
TLVs, e.g., the "color sub-TLV" and the "protocol sub-TLV", contain TLVs, e.g., the "color sub-TLV" and the "protocol sub-TLV", contain
skipping to change at page 24, line 12 skipping to change at page 24, line 12
before the route carrying the Tunnel Encapsulation attribute is before the route carrying the Tunnel Encapsulation attribute is
redistributed. redistributed.
There is no significance to the order in which the TLVs occur within There is no significance to the order in which the TLVs occur within
the Tunnel Encapsulation attribute. Multiple TLVs may occur for a the Tunnel Encapsulation attribute. Multiple TLVs may occur for a
given tunnel type; each such TLV is regarded as describing a given tunnel type; each such TLV is regarded as describing a
different tunnel. different tunnel.
10. IANA Considerations 10. IANA Considerations
IANA is requested to change the registration policy of the "BGP
Tunnel Encapsulation Attribute Sub-TLVs" registry to the following:
o The values 0 and 255 are reserved.
o The values in the range 1-127 are to be allocated using the
"Standards Action" registration procedure.
o The values in the range 128-251 are to be allocated using the
"First Come, First Served" registration procedure.
o The values in the range 252-254 are reserved for experimental use;
IANA shall not allocate values from this range.
IANA is requested to assign a codepoint from the "BGP Tunnel IANA is requested to assign a codepoint from the "BGP Tunnel
Encapsulation Attribute Sub-TLVs" registry for "Remote Endpoint", Encapsulation Attribute Sub-TLVs" registry for "Remote Endpoint",
with this document being the reference. with this document being the reference.
IANA is requested to assign a codepoint from the "BGP Tunnel IANA is requested to assign a codepoint from the "BGP Tunnel
Encapsulation Attribute Sub-TLVs" registry for "IPv4 DS Field", with Encapsulation Attribute Sub-TLVs" registry for "IPv4 DS Field", with
this document being the reference. this document being the reference.
IANA is requested to assign a codepoint from the "BGP Tunnel IANA is requested to assign a codepoint from the "BGP Tunnel
Encapsulation Attribute Sub-TLVs" registry for "UDP Destination Encapsulation Attribute Sub-TLVs" registry for "UDP Destination
Port", with this document being the reference. Port", with this document being the reference.
IANA is requested to assign a codepoint from the "BGP Tunnel IANA is requested to assign a codepoint from the "BGP Tunnel
Encapsulation Attribute Sub-TLVs" registry for "Embedded Label Encapsulation Attribute Sub-TLVs" registry for "Embedded Label
Handling", with this document being the reference. Handling", with this document being the reference.
IANA is requested to assign a codepoint from the "BGP Tunnel
Encapsulation Tunnel Types" registry for "GTP".
IANA is requested to add this document as a reference for tunnel IANA is requested to add this document as a reference for tunnel
types 8-13 in the "BGP Tunnel Encapsulation Tunnel Types" registry. types 8 (VXLAN), 9 (NVGRE), 11 (MPLS-in-GRE), and 12 (VXLAN-GPE) in
the "BGP Tunnel Encapsulation Tunnel Types" registry.
11. Security Considerations 11. Security Considerations
The Tunnel Encapsulation attribute can cause traffic to be diverted The Tunnel Encapsulation attribute can cause traffic to be diverted
from its normal path, especially when the Remote Endpoint sub-TLV is from its normal path, especially when the Remote Endpoint sub-TLV is
used. This can have serious consequences if the attribute is added used. This can have serious consequences if the attribute is added
or modified illegitimately, as it enables traffic to be "hijacked". or modified illegitimately, as it enables traffic to be "hijacked".
The Remote Endpoint sub-TLV contains both an IP address and an AS The Remote Endpoint sub-TLV contains both an IP address and an AS
number. BGP Origin Validation [RFC6811] can be used to obtain number. BGP Origin Validation [RFC6811] can be used to obtain
 End of changes. 6 change blocks. 
7 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/