RFC 9096: Improving the Reaction of Customer Edge Routers to IPv6 Renumbering Events
In plain English — editorial summary, not part of the RFC
This document specifies improvements to Customer Edge routers that help mitigate the problems that may arise when network configuration information becomes invalid without any explicit signaling of that condition to the local nodes. This document updates RFC 7084.
Document record
- Document ID
- RFC9096
- Published
- August 2021
- Authors
- F. Gont; J. Žorž; R. Patterson; B. Volz
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- BCP234
- Updates:
- RFC 7084
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 9243A YANG Data Model for DHCPv6 ConfigurationCurrent
June 2022
- RFC 8168DHCPv6 Prefix-Length Hint IssuesCurrent
May 2017
- RFC 9818DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANsCurrent
July 2025
- RFC 4864Local Network Protection for IPv6Current
May 2007
- RFC 2365Administratively Scoped IP MulticastCurrent
July 1998
- RFC 9686Registering Self-Generated IPv6 Addresses Using DHCPv6Current
December 2024
- RFC 8415Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2018
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?