SR Policy Implementation and Deployment Considerations
draft-filsfils-spring-sr-policy-considerations-07
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Clarence Filsfils , Ketan Talaulikar , Przemysław Gniewomir Król , Martin Horneffer , Paul Mattes | ||
| Last updated | 2021-10-06 (Latest revision 2021-04-04) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 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
Ketan Talaulikar
Przemysław Gniewomir Król
Martin Horneffer
Paul Mattes
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)