Asymmetric Extended Route Optimization (AERO)
draft-templin-aero-10

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rtg area)
Last updated 2012-04-26 (latest revision 2012-03-07)
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Needs a YES.
Responsible AD Stewart Bryant
Send notices to fltemplin@acm.org, draft-templin-aero@tools.ietf.org
Network Working Group                                    F. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Intended status: Experimental                              March 6, 2012
Expires: September 7, 2012

             Asymmetric Extended Route Optimization (AERO)
                       draft-templin-aero-10.txt

Abstract

   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 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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 7, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the

Templin                 Expires September 7, 2012               [Page 1]
Internet-Draft                    AERO                        March 2012

   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  6
   3.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  7
   4.  Asymmetric Extended Route Optimization (AERO)  . . . . . . . .  8
     4.1.  AERO Link Dynamic Routing  . . . . . . . . . . . . . . . .  8
     4.2.  AERO Node Behavior . . . . . . . . . . . . . . . . . . . .  8
       4.2.1.  AERO Node Types  . . . . . . . . . . . . . . . . . . .  8
       4.2.2.  AERO Host Behavior . . . . . . . . . . . . . . . . . .  8
       4.2.3.  Edge AERO Router Behavior  . . . . . . . . . . . . . .  9
       4.2.4.  Intermediate AERO Router Behavior  . . . . . . . . . .  9
     4.3.  AERO Reference Operational Scenario  . . . . . . . . . . . 10
     4.4.  AERO Specification . . . . . . . . . . . . . . . . . . . . 12
       4.4.1.  Classical Redirection Approaches . . . . . . . . . . . 12
       4.4.2.  AERO Concept of Operations . . . . . . . . . . . . . . 13
       4.4.3.  Conceptual Data Structures and Protocol Constants  . . 14
       4.4.4.  Data Origin Authentication . . . . . . . . . . . . . . 14
       4.4.5.  AERO Redirection Message Format  . . . . . . . . . . . 15
       4.4.6.  Sending Predirects . . . . . . . . . . . . . . . . . . 16
       4.4.7.  Processing Predirects and Sending Redirects  . . . . . 17
       4.4.8.  Relaying Redirects . . . . . . . . . . . . . . . . . . 19
       4.4.9.  Processing Redirects . . . . . . . . . . . . . . . . . 19
       4.4.10. Sending Periodic Predirect Keepalives  . . . . . . . . 20
       4.4.11. Reachability Considerations  . . . . . . . . . . . . . 22
       4.4.12. Mobility Considerations  . . . . . . . . . . . . . . . 22
       4.4.13. Prefix Re-Provisioning Considerations  . . . . . . . . 24
Show full document text