IS-IS TE Attributes per application
draft-ginsberg-isis-te-app-03
| Document | Type | Replaced Internet-Draft (isis WG) | |
|---|---|---|---|
| Last updated | 2017-08-17 (latest revision 2017-06-20) | ||
| Replaced by | draft-ietf-isis-te-app | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-isis-te-app | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ginsberg-isis-te-app-03.txt
Abstract
Existing traffic engineering related link attribute advertisements have been defined and are used in RSVP-TE deployments. In cases where multiple applications wish to make use of these link attributes the current advertisements do not support application specific values for a given attribute nor do they support indication of which applications are using the advertised value for a given link. This draft introduces new link attribute advertisements which address both of these shortcomings. It also discusses backwards compatibility issues and how to minimize duplicate advertisements in the presence of routers which do not support the extensions defined in this document.
Authors
Les Ginsberg
(ginsberg@cisco.com)
Peter Psenak
(ppsenak@cisco.com)
Stefano Previdi
(stefano@previdi.net)
Wim Henderickx
(wim.henderickx@nokia.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)