Segment Routing Traffic Engineering Policy using BGP
draft-sreekantiah-idr-segment-routing-te-00

Document Type Replaced Internet-Draft (individual)
Last updated 2017-02-22 (latest revision 2015-10-16)
Replaced by draft-previdi-idr-segment-routing-te-policy
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
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
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-sreekantiah-idr-segment-routing-te-00.txt

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 (asreekan@cisco.com)
Clarence Filsfils (cfilsfil@cisco.com)
Stefano Previdi (sprevidi@cisco.com)
Siva Sivabalan (msiva@cisco.com)
Paul Mattes (pamattes@microsoft.com)
Steven Lin (slin@microsoft.com)

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