Hi Les, I'm afraid I don't see how this revision resolves my DISCUSS point, which is that Section 7.5 creates a registry under "Expert Review" terms; BCP 26 pushes the point that such a registry definition should include guidance to the Designated Expert about how to handle new applications, but Section 7.5 doesn't.
On the other hand, Section 7.3 gets this right; note its last paragraph. For that matter, BCP 26 recommends including a "Change Controller" column, but neither registry created here does so. Is that intentional? https://tools.ietf.org/html/bcp26#section-4.5 -MSK On Thu, Jun 11, 2020 at 10:16 AM Les Ginsberg (ginsberg) <[email protected]> wrote: > > Folks - > > This update to the draft addresses comments from the following IESG reviewers: > > Murray Kucherawy > Martin Duke > Rob Wilton > Roman Danyliw > Deborah Brungard > Benjamin Kaduk > > It also includes grammatical corrections related to the use of "which/that". > > A special thank you to Acee Lindem for his tireless efforts to improve my > grammar. > > Les > > > -----Original Message----- > > From: Lsr <[email protected]> On Behalf Of [email protected] > > Sent: Thursday, June 11, 2020 10:06 AM > > To: [email protected] > > Cc: [email protected] > > Subject: [Lsr] I-D Action: draft-ietf-isis-te-app-15.txt > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > This draft is a work item of the Link State Routing WG of the IETF. > > > > Title : IS-IS TE Attributes per application > > Authors : Les Ginsberg > > Peter Psenak > > Stefano Previdi > > Wim Henderickx > > John Drake > > Filename : draft-ietf-isis-te-app-15.txt > > Pages : 21 > > Date : 2020-06-11 > > > > 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, Loop Free Alternate) 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 that address > > both of these shortcomings. > > > > > > > > The IETF datatracker status page for this draft is: > > https://datatracker.ietf.org/doc/draft-ietf-isis-te-app/ > > > > There are also htmlized versions available at: > > https://tools.ietf.org/html/draft-ietf-isis-te-app-15 > > https://datatracker.ietf.org/doc/html/draft-ietf-isis-te-app-15 > > > > A diff from the previous version is available at: > > https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-te-app-15 > > > > > > 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. > > > > Internet-Drafts are also available by anonymous FTP at: > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > _______________________________________________ > > Lsr mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/lsr _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
