RFC 6213: IS-IS BFD-Enabled TLV
In plain English — editorial summary, not part of the RFC
This document describes a type-length-value (TLV) for use in the IS-IS routing protocol that allows for the proper use of the Bidirectional Forwarding Detection (BFD) protocol. There exist certain scenarios in which IS-IS will not react appropriately to a BFD-detected forwarding plane failure without use of either this TLV or some other method. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6213
- Published
- April 2011
- Authors
- C. Hopps; L. Ginsberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6215MPLS Transport Profile User-to-Network and Network-to-Network InterfacesCurrent
April 2011
- RFC 6206The Trickle AlgorithmCurrent
March 2011
- RFC 6205Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching RoutersUpdated
March 2011
- RFC 6226PIM Group-to-Rendezvous-Point MappingCurrent
May 2011
- RFC 6232Purge Originator Identification TLV for IS-ISUpdated
May 2011
- RFC 6233IS-IS Registry Extension for PurgesCurrent
May 2011
- RFC 6240Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP) MIB Using SMIv2Current
May 2011
- RFC 6246Virtual Private LAN Service (VPLS) Interoperability with Customer Edge (CE) BridgesCurrent
June 2011
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?