RFC 9854: AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) Routing
In plain English — editorial summary, not part of the RFC
Route discovery for symmetric and asymmetric Peer-to-Peer (P2P) traffic flows is a desirable feature in Low-Power and Lossy Networks (LLNs). For that purpose, this document specifies AODV-RPL -- the Routing Protocol for Low-Power and Lossy Networks (RPL) based on Ad hoc On-demand Distance Vector (AODV) routing. AODV-RPL is a reactive P2P route discovery mechanism for both hop-by-hop routes and source routing. Paired instances are used to construct directional paths for cases where there are asymmetric links between source and target nodes.
Document record
- Document ID
- RFC9854
- Published
- October 2025
- Authors
- C.E. Perkins; S.V.R. Anand; S. Anamalamudi; B. Liu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9135Integrated Routing and Bridging in Ethernet VPN (EVPN)Current
October 2021
- RFC 3561Ad hoc On-Demand Distance Vector (AODV) RoutingCurrent
July 2003
- RFC 8387Practical Considerations and Implementation Experiences in Securing Smart Object NetworksCurrent
May 2018
- RFC 9855Topology Independent Fast Reroute Using Segment RoutingCurrent
October 2025
- RFC 9856Multicast Source Redundancy in EVPNsCurrent
September 2025
- RFC 9857Advertisement of Segment Routing Policies Using BGP - Link StateCurrent
October 2025
- RFC 9860Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast RerouteCurrent
October 2025
- RFC 9862Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing (SR) Policy Candidate PathsCurrent
October 2025
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?