Validity of SR Policy Candidate Path
draft-chen-spring-sr-policy-cp-validity-07
| Document | Type |
Replaced Internet-Draft
(spring WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ran Chen , Yisong Liu , Ketan Talaulikar , Detao Zhao , Zafar Ali | ||
| Last updated | 2026-04-24 (Latest revision 2026-02-02) | ||
| Replaced by | draft-ietf-spring-sr-policy-cp-validity | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-spring-sr-policy-cp-validity | |
| Consensus boilerplate | Unknown | ||
| 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 of which at a given time one and only one may be active (i.e., installed in forwarding plane and usable for steering of traffic). Each candidate path, in turn, may have one or more segment lists of which one or more may be active. When multiple segment lists are active, traffic is load balanced over them. Currently, a candidate path is valid as long as at least one of its segment lists is active. However, this default validity criterion does not meet the requirements of some scenarios. This document defines the new candidate path validity criterion.
Authors
Ran Chen
Yisong Liu
Ketan Talaulikar
Detao Zhao
Zafar Ali
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)