BGP Link-State extensions for Segment Routing
draft-gredler-bgp-ls-segment-routing-extensions-00

Document Type Replaced Internet-Draft (individual)
Last updated 2014-02-12
Replaced by draft-gredler-idr-bgp-ls-segment-routing-extension
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-gredler-idr-bgp-ls-segment-routing-extension
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-gredler-bgp-ls-segment-routing-extensions-00.txt

Abstract

Segment Routing (SR) allows for a flexible definition of end-to-end paths within link-state graphs by encoding paths as sequences of topological sub-paths, called "segments". The link-state routing protocols (IS-IS, OSPF and OSPFv3) have been extended to advertise the segments. But flooding based propagation of path segments using IGPs is limited by the perimeter of the IGP domain. For building paths which span across IGP domains (e.g. multiple ASes), the Border Gataway Protocol (BGP) is better suited as its propagation perimeter is not limited like the IGPs. This draft defines extensions to the BGP Link-state address-family to carry path segment information via BGP.

Authors

Hannes Gredler (hannes@juniper.net)
Saikat Ray (sairay@cisco.com)
Stefano Previdi (sprividi@cisco.com)
Clarence Filsfils (cfilsfil@cisco.com)
Mach Chen (mach.chen@huawei.com)
Jeff Tantsura (jeff.tantsura@ericsson.com)

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