RFC 3561: Ad hoc On-Demand Distance Vector (AODV) Routing
In plain English — editorial summary, not part of the RFC
The Ad hoc On-Demand Distance Vector (AODV) routing protocol is intended for use by mobile nodes in an ad hoc network. It offers quick adaptation to dynamic link conditions, low processing and memory overhead, low network utilization, and determines unicast routes to destinations within the ad hoc network. It uses destination sequence numbers to ensure loop freedom at all times (even in the face of anomalous delivery of routing control messages), avoiding problems (such as "counting to infinity") associated with classical distance vector protocols. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3561
- Published
- July 2003
- Authors
- C. Perkins; E. Belding-Royer; S. Das
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9854AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) RoutingCurrent
October 2025
- RFC 3513Internet Protocol Version 6 (IPv6) Addressing ArchitectureObsoleted
April 2003
- RFC 3448TCP Friendly Rate Control (TFRC): Protocol SpecificationObsoleted
January 2003
- RFC 3292General Switch Management Protocol (GSMP) V3Current
June 2002
- RFC 3849IPv6 Address Prefix Reserved for DocumentationUpdated
July 2004
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 2004
- RFC 3265Session Initiation Protocol (SIP)-Specific Event NotificationObsoleted
July 2002
- RFC 3264An Offer/Answer Model with Session Description Protocol (SDP)Updated
July 2002
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?