Problem Statement for Network-Based Localized Mobility Management (NETLMM)
RFC 4830

 
Document Type RFC - Informational (April 2007; No errata)
Last updated 2013-03-02
Replaces draft-kempf-netlmm-nohost-ps
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4830 (Informational)
Telechat date
Responsible AD Jari Arkko
Send notices to netlmm-chairs@ietf.org

Email authors IPR References Referenced by Nits Search lists

Network Working Group                                      J. Kempf, Ed.
Request for Comments: 4830                               DoCoMo USA Labs
Category: Informational                                       April 2007

             Problem Statement for Network-Based Localized
                      Mobility Management (NETLMM)

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   Localized mobility management is a well-understood concept in the
   IETF, with a number of solutions already available.  This document
   looks at the principal shortcomings of the existing solutions, all of
   which involve the host in mobility management, and makes a case for
   network-based local mobility management.

Table of Contents

   1. Introduction ....................................................2
      1.1. Terminology ................................................3
   2. The Local Mobility Problem ......................................4
   3. Scenarios for Localized Mobility Management .....................7
      3.1. Large Campus ...............................................7
      3.2. Advanced Cellular Network ..................................7
      3.3. Picocellular Network with Small But Node-Dense Last
           Hop Links ..................................................8
   4. Problems with Existing Solutions ................................8
   5. Advantages of Network-based Localized Mobility Management .......9
   6. Security Considerations ........................................10
   7. Informative References .........................................10
   8. Acknowledgements ...............................................11
   9. Contributors ...................................................12

Kempf                        Informational                      [Page 1]
RFC 4830                NETLMM Problem Statement              April 2007

1.  Introduction

   Localized mobility management has been the topic of much work in the
   IETF.  The experimental protocols developed from previous works,
   namely Fast-Handovers for Mobile IPv6 (FMIPv6) [13] and Hierarchical
   Mobile IPv6 (HMIPv6) [18], involve host-based solutions that require
   host involvement at the IP layer similar to, or in addition to, that
   required by Mobile IPv6 [10] for global mobility management.
   However, recent developments in the IETF and the Wireless LAN (WLAN)
   infrastructure market suggest that it may be time to take a fresh
   look at localized mobility management.

   First, new IETF work on global mobility management protocols that are
   not Mobile IPv6, such as Host Identity Protocol (HIP) [16] and IKEv2
   Mobility and Multihoming (MOBIKE) [4], suggests that future wireless
   IP nodes may support a more diverse set of global mobility protocols.
   While it is possible that existing localized mobility management
   protocols could be used with HIP and MOBIKE, some would require
   additional effort to implement, deploy, or in some cases, even
   specify in a non-Mobile IPv6 mobile environment.

   Second, the success in the WLAN infrastructure market of WLAN
   switches, which perform localized management without any host stack
   involvement, suggests a possible paradigm that could be used to
   accommodate other global mobility options on the mobile node while
   reducing host stack software complexity, expanding the range of
   mobile nodes that could be accommodated.

   This document briefly describes the general local mobility problem
   and scenarios where localized mobility management would be desirable.
   Then problems with existing or proposed IETF localized mobility
   management protocols are briefly discussed.  The network-based
   mobility management architecture and a short description of how it
   solves these problems are presented.  A more detailed discussion of
   goals for a network-based, localized mobility management protocol and
   gap analysis for existing protocols can be found in [11].  Note that
   IPv6 and wireless links are considered to be the initial scope for a
   network-based localized mobility management, so the language in this
   document reflects that scope.  However, the conclusions of this
   document apply equally to IPv4 and wired links, where nodes are
   disconnecting and reconnecting.

Kempf                        Informational                      [Page 2]
RFC 4830                NETLMM Problem Statement              April 2007

1.1.  Terminology

   Mobility terminology in this document follows that in RFC 3753 [14],
Show full document text