Include Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
draft-ali-teas-rsvp-te-include-route-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zafar Ali , George Swallow , Clarence Filsfils , Matt Hartley , Ori Gerstel , Kenji Kumaki , Ruediger Kunze | ||
| Last updated | 2016-01-07 (Latest revision 2015-07-06) | ||
| 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
There are scenarios that require two or more LSPs or segments of LSPs to follow same route in the network. This document specifies methods to communicate route inclusions along the loose hops during path setup using the Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) protocol.
Authors
Zafar Ali
George Swallow
Clarence Filsfils
Matt Hartley
Ori Gerstel
Kenji Kumaki
Ruediger Kunze
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)