BGP vector routing.
draft-patel-raszuk-bgp-vector-routing-07

Document Type Expired Internet-Draft (individual)
Last updated 2016-12-02 (latest revision 2016-05-31)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-patel-raszuk-bgp-vector-routing-07.txt

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 transit nodes (e.g. 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 (robert@raszuk.net)
Keyur Patel (keyupate@cisco.com)
Burjiz (bpithaw@cisco.com)
Ali Sajassi (sajassi@cisco.com)
eric.osborne@level3.com (eric.osborne@level3.com)
Luay Jalil (luay.jalil@verizon.com)
Jim Uttaro (uttaro@att.com)

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