RFC 8706: Restart Signaling for IS-IS
In plain English — editorial summary, not part of the RFC
This document describes a mechanism for a restarting router to signal to its neighbors that it is restarting, allowing them to reestablish their adjacencies without cycling through the DOWN state while still correctly initiating database synchronization. This document additionally describes a mechanism for a router to signal its neighbors that it is preparing to initiate a restart while maintaining forwarding-plane state. This allows the neighbors to maintain their adjacencies until the router has restarted but also allows the neighbors to bring the adjacencies down in the event of other topology changes. This document additionally describes a mechanism for a restarting router to determine when it has achieved Link State Protocol Data Unit (LSP) database synchronization with its neighbors and a mechanism to optimize LSP database synchronization while minimizing transient routing disruption when a router starts. This document obsoletes RFC 5306.
Document record
- Document ID
- RFC8706
- Published
- February 2020
- Authors
- L. Ginsberg; P. Wells
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
- Obsoletes:
- RFC 5306
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3847 (2004)
- RFC 5306 (2008)
- RFC 8706 (2020)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8667IS-IS Extensions for Segment RoutingCurrent
December 2019
- RFC 8666OSPFv3 Extensions for Segment RoutingCurrent
December 2019
- RFC 8665OSPF Extensions for Segment RoutingCurrent
December 2019
- RFC 8570IS-IS Traffic Engineering (TE) Metric ExtensionsCurrent
March 2019
- RFC 8518Selection of Loop-Free Alternates for Multi-Homed PrefixesCurrent
March 2019
- RFC 8510OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID AdvertisementCurrent
January 2019
- RFC 8500IS-IS Routing with Reverse MetricCurrent
February 2019
- RFC 8965Applicability of the Babel Routing ProtocolCurrent
January 2021
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?