Skip to main content

IS-IS Application-Specific Link Attributes

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: The IESG <>,,,,,,
Subject: Protocol Action: 'IS-IS Application-Specific Link Attributes' to Proposed Standard (draft-ietf-lsr-rfc8919bis-04.txt)

The IESG has approved the following document:
- 'IS-IS Application-Specific Link Attributes'
  (draft-ietf-lsr-rfc8919bis-04.txt) as Proposed Standard

This document is the product of the Link State Routing Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:

Ballot Text

Technical Summary

   This bis document is a narrowly-scoped update to RFC 8919. The 
   updates are outlined in Section 9, "Changes to RFC 8919".

   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
   that address both of these shortcomings.

   This document obsoletes RFC 8919.

Working Group Summary

   The document shepherd notes, "one person expressed dislike for the 
   base document; however, that was deemed out-of-scope as this is a 
   simple clarifying document update." In other respects the shepherd
   notes broad WG agreement to publish.

Document Quality

   The shepherd notes, "Implementations of the base document exist."
   The scope of the bis doesn't require specialized review.


   The Document Shepherd for this document is Christian Hopps. The
   Responsible Area Director is John Scudder.

RFC Editor Note