FW: New Version Notification for draft-ginsberg-isis-te-app-02.txt
"Les Ginsberg (ginsberg)" <[email protected]>
| Newsgroups | gmane.ietf.isis |
|---|---|
| Message-ID | <[email protected]> |
Folks - In response to comments received a new version of the draft has been posted. This defines variable length application bit masks for both Standard Applications and User Defined Applications. It also clarifies the relationship between link attribute advertisements and application enablement on a link (none implied). Les -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, June 07, 2017 10:45 PM To: Wim Henderickx; Stefano Previdi; Peter Psenak (ppsenak); Les Ginsberg (ginsberg) Subject: New Version Notification for draft-ginsberg-isis-te-app-02.txt A new version of I-D, draft-ginsberg-isis-te-app-02.txt has been successfully submitted by Les Ginsberg and posted to the IETF repository. Name: draft-ginsberg-isis-te-app Revision: 02 Title: IS-IS TE Attributes per application Document date: 2017-06-07 Group: Individual Submission Pages: 14 URL: https://www.ietf.org/internet-drafts/draft-ginsberg-isis-te-app-02.txt Status: https://datatracker.ietf.org/doc/draft-ginsberg-isis-te-app/ Htmlized: https://tools.ietf.org/html/draft-ginsberg-isis-te-app-02 Htmlized: https://datatracker.ietf.org/doc/html/draft-ginsberg-isis-te-app-02 Diff: https://www.ietf.org/rfcdiff?url2=draft-ginsberg-isis-te-app-02 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. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat