SR Policy Implementation and Deployment Considerations
draft-filsfils-spring-sr-policy-considerations-03

The information below is for an old version of the document
Document Type None Internet-Draft (individual)
Last updated 2019-04-16
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Unknown state
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-sr-policy-considerations-03.txt

Abstract

Segment Routing (SR) allows a headend node to steer a packet flow along any path. Intermediate per-flow states are eliminated thanks to source routing. SR Policy framework enables the instantiation and the management of necessary state on the headend node for flows along a source routed paths using an ordered list of segments associated with their specific SR Policies. This document describes some of the implementation and deployment aspects that are useful for operationalizing the SR Policy architecture.

Authors

Clarence Filsfils (cfilsfil@cisco.com)
Ketan Talaulikar (ketant@cisco.com)
Przemysław Król (pkrol@google.com)
Martin Horneffer (Martin.Horneffer@telekom.de)
Paul Mattes (pamattes@microsoft.com)

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