Segment Routing Traffic Engineering Policy using BGP
draft-sreekantiah-idr-segment-routing-te-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Arjun Sreekantiah , Clarence Filsfils , Stefano Previdi , Siva Sivabalan , Paul Mattes , Steven Lin | ||
| Last updated | 2017-02-22 (Latest revision 2015-10-16) | ||
| Replaced by | draft-previdi-idr-segment-routing-te-policy | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-previdi-idr-segment-routing-te-policy | |
| 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
This document describes mechanisms allowing advertising Segment Routing Traffic Engineering (SRTE) policies using BGP. Through the mechanisms described in this document, a BGP speaker has the ability to trigger, in a remote BGP node, the setup of a SR Encapsulation policy with specific characteristics and an explicit path. Steering mechanisms are also defined to enable the application of the policy on a per BGP route basis.
Authors
Arjun Sreekantiah
Clarence Filsfils
Stefano Previdi
Siva Sivabalan
Paul Mattes
Steven Lin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)