FW: New Version Notification for draft-ginsberg-isis-te-app-01.txt

FYI - an update to this draft has been posted.
It includes support for "User Defined Applications".

   Les


-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, May 31, 2017 1:11 PM
To: Stefano Previdi (sprevidi); Wim Henderickx; Peter Psenak (ppsenak); Les Ginsberg (ginsberg)
Subject: New Version Notification for draft-ginsberg-isis-te-app-01.txt


A new version of I-D, draft-ginsberg-isis-te-app-01.txt has been successfully submitted by Les Ginsberg and posted to the IETF repository.

Name:		draft-ginsberg-isis-te-app
Revision:	01
Title:		IS-IS TE Attributes per application
Document date:	2017-05-31
Group:		Individual Submission
Pages:		14
URL:            https://www.ietf.org/internet-drafts/draft-ginsberg-isis-te-app-01.txt
Status:         https://datatracker.ietf.org/doc/draft-ginsberg-isis-te-app/
Htmlized:       https://tools.ietf.org/html/draft-ginsberg-isis-te-app-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ginsberg-isis-te-app-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ginsberg-isis-te-app-01

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