Validity of SR Policy Candidate Path
draft-chen-spring-sr-policy-cp-validity-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ran Chen , Yisong Liu , Ketan Talaulikar , Samuel Sidor , Detao Zhao , Changwang Lin , Zafar Ali | ||
| Last updated | 2025-01-22 (Latest revision 2024-07-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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
An SR Policy comprises one or more candidate paths (CP) of which at a given time one and only one may be active (i.e., installed in forwarding and usable for steering of traffic). Each CP in turn may have one or more SID-List of which one or more may be active; when multiple SID-List are active then traffic is load balanced over them. However, a candidate path is valid when at least one SID-List is active. This candidate path validity criterion cannot meet the needs of some scenarios. This document defines the new candidate path validity criterion.
Authors
Ran Chen
Yisong Liu
Ketan Talaulikar
Samuel Sidor
Detao Zhao
Changwang Lin
Zafar Ali
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)