RFC 5306: Restart Signaling for IS-IS
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8706.
Current document in this lineage: 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 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 3847. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5306
- Published
- October 2008
- Authors
- M. Shand; L. Ginsberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
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) ✓
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 5304IS-IS Cryptographic AuthenticationUpdated
October 2008
- RFC 5307IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2008
- RFC 5305IS-IS Extensions for Traffic EngineeringUpdated
October 2008
- RFC 5308Routing IPv6 with IS-ISUpdated
October 2008
- RFC 5303Three-Way Handshake for IS-IS Point-to-Point AdjacenciesCurrent
October 2008
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-ISCurrent
October 2008
- RFC 5301Dynamic Hostname Exchange Mechanism for IS-ISUpdated
October 2008
- RFC 5286Basic Specification for IP Fast Reroute: Loop-Free AlternatesUpdated
September 2008
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?