OSPF Application-Specific Link Attributes
draft-ppsenak-lsr-rfc8920bis-02
| Document | Type |
Replaced Internet-Draft
(lsr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Peter Psenak , Les Ginsberg , Wim Henderickx , Jeff Tantsura , John Drake | ||
| Last updated | 2022-10-23 (Latest revision 2022-07-24) | ||
| Replaced by | draft-ietf-lsr-rfc8920bis | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-lsr-rfc8920bis | |
| Consensus boilerplate | Yes | ||
| 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
Existing traffic-engineering-related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case was defined, additional applications (e.g., Segment Routing Policy and Loop-Free Alternates) that also make use of the link attribute advertisements have been defined. 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 document introduces new link attribute advertisements in OSPFv2 and OSPFv3 that address both of these shortcomings. This document obsoletes RFC 8920.
Authors
Peter Psenak
Les Ginsberg
Wim Henderickx
Jeff Tantsura
John Drake
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)