datatracker.ietf.org
Sign In
Version 4.45, 2013-05-14
Report a bug

Flow Binding Support for Mobile IPv4
draft-ietf-mip4-multiple-tunnel-support-05

Active Internet-Draft (mip4 WG)
Document Stream: IETF
Last updated: 2013-01-31
Replaces: draft-gundavelli-mip4-multiple-tunnel-support
Intended RFC status: (None)
Other versions: plain text, pdf, html

IETF State: WG Document (mip4)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Mobility for IPv4 Working Group                       S. Gundavelli, Ed.
Internet-Draft                                                  K. Leung
Intended status: Standards Track                                   Cisco
Expires: August 4, 2013                                      G. Tsirtsis
                                                                Qualcomm
                                                              H. Soliman
                                                    Elevate Technologies
                                                             A. Petrescu
                                                                CEA LIST
                                                        January 31, 2013

                  Flow Binding Support for Mobile IPv4
             draft-ietf-mip4-multiple-tunnel-support-05.txt

Abstract

   This specification defines extensions to Mobile IPv4 protocol for
   allowing a mobile node with multiple interfaces to register a care-of
   address for each of its network interfaces and to simultaneously
   establish multiple Mobile IP tunnels with its home agent.  This
   essentially allows the mobile node to utilize all the available
   network interfaces and build an higher aggregated data pipe with the
   home agent for its home address traffic.  Furthermore, these
   extensions also allow the mobile node and the home agent to negotiate
   flow policies for binding individual traffic flows with the
   registered care-of addresses.

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 August 4, 2013.

Copyright Notice

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

Gundavelli, et al.       Expires August 4, 2013                 [Page 1]
Internet-Draft    Flow Binding Support for Mobile IPv4      January 2013

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions & Terminology  . . . . . . . . . . . . . . . . . .  3
     2.1.  Conventions  . . . . . . . . . . . . . . . . . . . . . . .  3
     2.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Message Extensions . . . . . . . . . . . . . . . . . . . . . .  5
     4.1.  Alternate-CoA Extension  . . . . . . . . . . . . . . . . .  5
     4.2.  Flow Identification Extension  . . . . . . . . . . . . . .  7
   5.  Protocol Operation . . . . . . . . . . . . . . . . . . . . . . 16
     5.1.  Mobile Node Considerations . . . . . . . . . . . . . . . . 17
       5.1.1.  Using the Alternate-CoA extension  . . . . . . . . . . 17
       5.1.2.  Using the Flow Identification Extension  . . . . . . . 18
     5.2.  Home Agent Considerations  . . . . . . . . . . . . . . . . 19
       5.2.1.  Handling Alternate-CoA extensions  . . . . . . . . . . 19
       5.2.2.  Handling Flow Identification Extensions  . . . . . . . 20
   6.  Routing Considerations . . . . . . . . . . . . . . . . . . . . 23
   7.  Protocol Configuration Variables . . . . . . . . . . . . . . . 23
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 24
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 24
   10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 24
   11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 25
     12.2. Informative References . . . . . . . . . . . . . . . . . . 25