Circuit Style Segment Routing Policies
draft-schmutzer-pce-cs-sr-policy-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Schmutzer , Clarence Filsfils , Zafar Ali , Francois Clad , Praveen Maheshwari , Reza Rokui , Andrew Stone , Luay Jalil , Shuping Peng , Tarek Saad , Daniel Voyer | ||
| Last updated | 2022-05-05 | ||
| Replaced by | draft-schmutzer-spring-cs-sr-policy | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-schmutzer-spring-cs-sr-policy | |
| 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
This document describes how Segment Routing (SR) policies can be used to satisfy the requirements for strict bandwidth guarantees, end-to- end recovery and persistent paths within a segment routing network. SR policies satisfying these requirements are called "circuit-style" SR policies (CS-SR policies).
Authors
Christian Schmutzer
Clarence Filsfils
Zafar Ali
Francois Clad
Praveen Maheshwari
Reza Rokui
Andrew Stone
Luay Jalil
Shuping Peng
Tarek Saad
Daniel Voyer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)