Skip to main content

Segment Routing Egress Peer Engineering BGP-LS Extensions
draft-previdi-idr-bgpls-segment-routing-epe-03

Document Type Replaced Internet-Draft (idr WG)
Expired & archived
Authors Stefano Previdi , Clarence Filsfils , Saikat Ray , Keyur Patel , Jie Dong , Mach Chen
Last updated 2015-10-14 (Latest revision 2015-04-27)
Replaced by RFC 9086
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-idr-bgpls-segment-routing-epe
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) leverages source routing. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. A segment can represent any instruction, topological or service-based. SR allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node of the SR domain. The Segment Routing architecture can be directly applied to the MPLS dataplane with no change on the forwarding plane. It requires minor extension to the existing link-state routing protocols. This document outline a BGP-LS extension for exporting BGP egress point topology information (including its peers, interfaces and peering ASs) in a way that is exploitable in order to compute efficient Egress Point Engineering policies and strategies.

Authors

Stefano Previdi
Clarence Filsfils
Saikat Ray
Keyur Patel
Jie Dong
Mach Chen

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