{
  "draft": "draft-ietf-lsr-rfc8919bis-04",
  "doc_id": "RFC9479",
  "title": "IS-IS Application-Specific Link Attributes",
  "authors": [
    "L. Ginsberg",
    "P. Psenak",
    "S. Previdi",
    "W. Henderickx",
    "J. Drake"
  ],
  "format": [
    "XML",
    "TEXT",
    "HTML",
    "PDF"
  ],
  "page_count": "21",
  "pub_status": "PROPOSED STANDARD",
  "status": "PROPOSED STANDARD",
  "source": "Link State Routing",
  "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 an indication of which applications are using the advertised value for a given link. This document introduces link attribute advertisements that address both of these shortcomings.\n\n This document obsoletes RFC 8919.",
  "pub_date": "October 2023",
  "keywords": [],
  "obsoletes": [
    "RFC8919"
  ],
  "obsoleted_by": [],
  "updates": [],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC9479",
  "errata_url": null
}