Skip to main content

BGP Link-State extensions for Segment Routing
draft-gredler-idr-bgp-ls-segment-routing-extension-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Hannes Gredler , Saikat Ray , Stefano Previdi , Clarence Filsfils , Mach Chen , Jeff Tantsura
Last updated 2015-04-19 (Latest revision 2014-10-16)
Replaces draft-gredler-bgp-ls-segment-routing-extensions
Replaced by draft-gredler-idr-bgp-ls-segment-routing-ext
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Stream WG state (None)
Document shepherd (None)
IESG IESG state Replaced by draft-gredler-idr-bgp-ls-segment-routing-ext
Consensus boilerplate Unknown
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

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 Gateway 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
Saikat Ray
Stefano Previdi
Clarence Filsfils
Mach Chen
Jeff Tantsura

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