RFC 9805: Deprecation of the IPv6 Router Alert Option for New Protocols
In plain English — editorial summary, not part of the RFC
This document deprecates the IPv6 Router Alert option. Protocols that use the IPv6 Router Alert option may continue to do so, even in future versions. However, new protocols that are standardized in the future must not use the IPv6 Router Alert option. This document updates RFC 2711.
Document record
- Document ID
- RFC9805
- Published
- June 2025
- Authors
- R. Bonica
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 2711
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9837The IPv6 VPN Service Destination OptionCurrent
August 2025
- RFC 9762Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to ClientsCurrent
June 2025
- RFC 9915Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
January 2026
- RFC 9686Registering Self-Generated IPv6 Addresses Using DHCPv6Current
December 2024
- RFC 9631The IPv6 Compact Routing Header (CRH)Current
August 2024
- RFC 9428Transmission of IPv6 Packets over Near Field CommunicationCurrent
July 2023
- RFC 9363A YANG Data Model for Static Context Header Compression (SCHC)Updated
March 2023
- RFC 9243A YANG Data Model for DHCPv6 ConfigurationCurrent
June 2022
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?