Segment Routing Centralized Egress Peer Engineering
draft-filsfils-spring-segment-routing-central-epe-05

Document Type Replaced Internet-Draft (individual)
Last updated 2015-08-29
Replaced by draft-ietf-spring-segment-routing-central-epe
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-spring-segment-routing-central-epe
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-filsfils-spring-segment-routing-central-epe-05.txt

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 illustrates the application of Segment Routing to solve the Egress Peer Engineering (EPE) requirement. The SR-based EPE solution allows a centralized (SDN) controller to program any egress peer policy at ingress border routers or at hosts within the domain. This document is on the informational track.

Authors

Clarence Filsfils (cfilsfil@cisco.com)
Stefano Previdi (sprevidi@cisco.com)
Keyur Patel (keyupate@cisco.com)
Ebben Aries (exa@fb.com)
Steve Shaw (shaw@dropbox.com)
Daniel Ginsburg (dbg@yandex-team.ru)
Dmitry Afanasiev (fl0w@yandex-team.ru)

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