Resources for Preferred Path Routes in IGPs
draft-cls-ppr-te-attributes-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Uma Chunduri , Richard Li , Kevin Smith | ||
| Last updated | 2019-11-18 (Latest revision 2019-05-16) | ||
| 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
Preferred Path Routing (PPR) is concerned with setting up the route for a given prefix as specified in the path description along with a corresponding data plane/forwarding identifier PPR-ID. This document specifies an extension to PPR, a mechanism to perform resource reservations nodes on Preferred Path Routes (PPR) for IGPs (IS-IS, OSPFv2, OSPFv3). This is done by specifying the resources that need to be reserved along the path using PPR path attributes.
Authors
Uma Chunduri
Richard Li
Kevin Smith
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)