Network Working Group P. Seite
Internet-Draft P. Bertin
Intended status: Informational France Telecom - Orange
Expires: July 13, 2013 JH. Lee
Telecom Bretagne
January 9, 2013
Distributed Mobility Anchoring
draft-seite-dmm-dma-06.txt
Abstract
Most existing IP mobility solutions are derived from Mobile IP
principles where a given mobility anchor maintains Mobile Nodes (MNs)
binding up-to-date. Data traffic is then encapsulated between the
mobility anchor and the MN or its Access Router. These approaches
are usually implemented on a centralised architectures where both MN
context and traffic encapsulation need to be processed at a central
network entity, i.e. the mobility anchor. However, one of the trend
in mobile network evolution is to "flatten" mobility architecture by
confining mobility support in the access network, e.g. at the access
routers level, keeping the rest of the network unaware of the
mobility events and their support. This document discusses the
deployment of a Proxy Mobile IP approach in such a flat architecture.
The solution allows to dynamically distribute mobility functions
among access routers for an optimal routing management. The goal is
also to dynamically adapt the mobility support of the MN's needs by
applying traffic redirection only to MNs' flows when an IP handover
occurs.
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 July 13, 2013.
Seite, et al. Expires July 13, 2013 [Page 1]
Internet-Draft Distributed Mobility Anchoring January 2013
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Basics of Distributed Mobility Management . . . . . . . . . . 5
3.1. Fundamentals . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Considerations on Client based mobility management . . . . 6
3.3. Considerations on Network based mobility management . . . 8
4. Solution Overview for network based DMM . . . . . . . . . . . 8
4.1. Distributed and Dynamic Mobility Anchoring . . . . . . . . 8
4.2. Protocol sequence for handover management . . . . . . . . 11
4.3. Multiple Interfaces support . . . . . . . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Seite, et al. Expires July 13, 2013 [Page 2]
Internet-Draft Distributed Mobility Anchoring January 2013
1. Terminology
Proxy Mobile IPv6 inherited terminology
The following terms used in this document are to be interpreted as
datatracker.ietf.org