BGP Flow-Spec Redirect to Tunnel Action
draft-hao-idr-flowspec-redirect-tunnel-01

Document Type Expired Internet-Draft (idr WG)
Last updated 2016-09-19 (latest revision 2016-03-18)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hao-idr-flowspec-redirect-tunnel-01.txt

Abstract

This draft defines a new flow-spec action, Redirect-to-Tunnel, and a new sub-TLV for Redirect-to-Tunnel extended community. A BGP UPDATE for a flow-spec NLRI can contain the extended community. When activated, the corresponding flow packets will be encapsulated and carried via a tunnel. The redirect tunnel information is encoded in BGP Path Attribute or extended community [TUNNELENCAPS][MPP] that is carried in the BGP flow-spec UPDATE. The draft expends the tunnel encapsulation attribute [TUNNELENCAPS] to apply to flow-spec SAFI, i.e., 133 and 134.

Authors

Hao Weiguo (haoweiguo@huawei.com)
Zhenbin Li (lizhenbin@huawei.com)
Lucy Yong (lucy.yong@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)