Folks -
Please note that V1 of the RFC8920bis draft has been posted.
Les
-----Original Message-----
From: [email protected] <[email protected]>
Sent: Monday, June 20, 2022 8:24 PM
To: Jeff Tantsura <[email protected]>; John Drake <[email protected]>;
Les Ginsberg (ginsberg) <[email protected]>; Peter Psenak (ppsenak)
<[email protected]>; Wim Henderickx <[email protected]>
Subject: New Version Notification for draft-ppsenak-lsr-rfc8920bis-01.txt
A new version of I-D, draft-ppsenak-lsr-rfc8920bis-01.txt
has been successfully submitted by Les Ginsberg and posted to the
IETF repository.
Name: draft-ppsenak-lsr-rfc8920bis
Revision: 01
Title: OSPF Application-Specific Link Attributes
Document date: 2022-06-20
Group: Individual Submission
Pages: 23
URL:
https://www.ietf.org/archive/id/draft-ppsenak-lsr-rfc8920bis-01.txt
Status: https://datatracker.ietf.org/doc/draft-ppsenak-lsr-rfc8920bis/
Html:
https://www.ietf.org/archive/id/draft-ppsenak-lsr-rfc8920bis-01.html
Htmlized:
https://datatracker.ietf.org/doc/html/draft-ppsenak-lsr-rfc8920bis
Diff:
https://www.ietf.org/rfcdiff?url2=draft-ppsenak-lsr-rfc8920bis-01
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.
The IETF Secretariat
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
