Preferred Path Routing (PPR) in OSPF
draft-chunduri-lsr-ospf-preferred-path-routing-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Uma Chunduri , Yingzhen Qu , Russ White , Jeff Tantsura , Luis M. Contreras | ||
| Last updated | 2020-09-09 (Latest revision 2020-03-08) | ||
| 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
This document specifies a Preferred Path Routing (PPR), a routing protocol mechanism to simplify the path description of data plane traffic in Segment Routing (SR) deployments with OSPFv2 and OSPFv3 protocols. PPR aims to mitigate the MTU and data plane processing issues that may result from SR packet overheads; and also supports further extensions along the paths. Preferred path routing is achieved through the addition of path descriptions to the OSPF advertised prefixes, and mapping those to a PPR data-plane identifier.
Authors
Uma Chunduri
Yingzhen Qu
Russ White
Jeff Tantsura
Luis M. Contreras
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)