BGP vector routing.
draft-patel-raszuk-bgp-vector-routing-06
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Robert Raszuk , Keyur Patel , Burjiz , Ali Sajassi , eric.osborne@level3.com , Luay Jalil , Jim Uttaro | ||
Last updated | 2016-05-25 (Latest revision 2015-11-22) | ||
RFC stream | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Network architectures have begun to shift from pure destination based routing to service aware routing. Operator requirements in this space include forcing traffic through particular service nodes (e.g. firewall, NAT) or segments. This document proposes an enhancement to BGP to accommodate these new requirements. This document proposes a pure control plane solution which allows traffic to be routed via an ordered set of transit points (links, nodes or services) on the way to traffic's destination, with no change in the forwarding plane. This approach is in contrast to other proposal in this space which provide similar capabilities via modifications to the forwarding plane.
Authors
Robert Raszuk
Keyur Patel
Burjiz
Ali Sajassi
eric.osborne@level3.com
Luay Jalil
Jim Uttaro
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)