RFC 4971: Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7981.
Current version: RFC 7981 — IS-IS Extensions for Advertising Router Information
In plain English — editorial summary, not part of the RFC
This document defines a new optional Intermediate System to Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple sub-TLVs, which allows a router to announce its capabilities within an IS-IS level or the entire routing domain. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4971
- Published
- July 2007
- Authors
- JP. Vasseur; N. Shen; R. Aggarwal
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
- Obsoleted by:
- RFC 7981
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
- RFC 4974Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of CallsUpdated
August 2007
- RFC 4990Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) NetworksCurrent
September 2007
- RFC 4951Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover"Current
August 2007
- RFC 4950ICMP Extensions for Multiprotocol Label SwitchingCurrent
August 2007
- RFC 4940IANA Considerations for OSPFCurrent
July 2007
- RFC 5003Attachment Individual Identifier (AII) Types for AggregationCurrent
September 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?