RFC 8978: Reaction of IPv6 Stateless Address Autoconfiguration (SLAAC) to Flash-Renumbering Events
In plain English — editorial summary, not part of the RFC
In scenarios where network configuration information related to IPv6 prefixes becomes invalid without any explicit and reliable signaling of that condition (such as when a Customer Edge router crashes and reboots without knowledge of the previously employed prefixes), hosts on the local network may continue using stale prefixes for an unacceptably long time (on the order of several days), thus resulting in connectivity problems. This document describes this issue and discusses operational workarounds that may help to improve network robustness. Additionally, it highlights areas where further work may be needed.
Document record
- Document ID
- RFC8978
- Published
- March 2021
- Authors
- F. Gont; J. Žorž; R. Patterson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8977Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and PagingCurrent
January 2021
- RFC 8976Message Digest for DNS ZonesCurrent
February 2021
- RFC 8982Registration Data Access Protocol (RDAP) Partial ResponseCurrent
February 2021
- RFC 8972Simple Two-Way Active Measurement Protocol Optional ExtensionsCurrent
January 2021
- RFC 8969A Framework for Automating Service and Network Management with YANGCurrent
January 2021
- RFC 8990GeneRic Autonomic Signaling Protocol (GRASP)Current
May 2021
- RFC 8991GeneRic Autonomic Signaling Protocol Application Program Interface (GRASP API)Current
May 2021
- RFC 8992Autonomic IPv6 Edge Prefix Management in Large-Scale NetworksCurrent
May 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?