RFC 5130: A Policy Control Mechanism in IS-IS Using Administrative Tags
In plain English — editorial summary, not part of the RFC
This document describes an extension to the IS-IS protocol to add operational capabilities that allow for ease of management and control over IP prefix distribution within an IS-IS domain. This document enhances the IS-IS protocol by extending the information that an Intermediate System (IS) router can place in Link State Protocol (LSP) Data Units for policy use. This extension will provide operators with a mechanism to control IP prefix distribution throughout multi-level IS-IS domains. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5130
- Published
- February 2008
- Authors
- S. Previdi; M. Shand; C. Martin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3784Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)Obsoleted
June 2004
- RFC 5150Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE)Current
February 2008
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 5330A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a LinkCurrent
October 2008
- RFC 4920Crankback Signaling Extensions for MPLS and GMPLS RSVP-TECurrent
July 2007
- RFC 5439An Analysis of Scaling Issues in MPLS-TE Core NetworksCurrent
February 2009
- RFC 4726A Framework for Inter-Domain Multiprotocol Label Switching Traffic EngineeringCurrent
November 2006
- RFC 4687Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS NetworksCurrent
September 2006
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?