RFC 6706: Asymmetric Extended Route Optimization (AERO)
In plain English — editorial summary, not part of the RFC
Nodes attached to common multi-access link types (e.g., multicast- capable, shared media, non-broadcast multiple access (NBMA), etc.) can exchange packets as neighbors on the link, but they may not always be provisioned with sufficient routing information for optimal neighbor selection. Such nodes should therefore be able to discover a trusted intermediate router on the link that provides both forwarding services to reach off-link destinations and redirection services to inform the node of an on-link neighbor that is closer to the final destination. This redirection can provide a useful route optimization, since the triangular path from the ingress link neighbor, to the intermediate router, and finally to the egress link neighbor may be considerably longer than the direct path from ingress to egress. However, ordinary redirection may lead to operational issues on certain link types and/or in certain deployment scenarios. This document therefore introduces an Asymmetric Extended Route Optimization (AERO) capability that addresses the issues. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6706
- Published
- August 2012
- Authors
- F. Templin
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1364BGP OSPF InteractionObsoleted
September 1992
- RFC 6145IP/ICMP Translation AlgorithmObsoleted
April 2011
- RFC 6041Forwarding and Control Element Separation (ForCES) Applicability StatementCurrent
October 2010
- RFC 7915IP/ICMP Translation AlgorithmCurrent
June 2016
- RFC 8200Internet Protocol, Version 6 (IPv6) SpecificationUpdated
July 2017
- RFC 8201Path MTU Discovery for IP version 6Current
July 2017
- RFC 5172Negotiation for IPv6 Datagram Compression Using IPv6 Control ProtocolCurrent
March 2008
- RFC 5072IP Version 6 over PPPUpdated
September 2007
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?