Requirements for Distributed Mobility Management
RFC 7333
|
| Document |
Type |
|
RFC - Informational
(August 2014; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-chan-dmm-requirements
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Pete McCann
|
|
Shepherd write-up |
|
Show
(last changed 2014-01-09)
|
| IESG |
IESG state |
|
RFC 7333 (Informational)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Brian Haberman
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
No IC
|
Internet Engineering Task Force (IETF) H. Chan, Ed.
Request for Comments: 7333 Huawei Technologies
Category: Informational D. Liu
ISSN: 2070-1721 China Mobile
P. Seite
Orange
H. Yokota
Landis+Gyr
J. Korhonen
Broadcom Communications
August 2014
Requirements for Distributed Mobility Management
Abstract
This document defines the requirements for Distributed Mobility
Management (DMM) at the network layer. The hierarchical structure in
traditional wireless networks has led primarily to centrally deployed
mobility anchors. As some wireless networks are evolving away from
the hierarchical structure, it can be useful to have a distributed
model for mobility management in which traffic does not need to
traverse centrally deployed mobility anchors far from the optimal
route. The motivation and the problems addressed by each requirement
are also described.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7333.
Chan, et al. Informational [Page 1]
RFC 7333 DMM-Reqs August 2014
Copyright Notice
Copyright (c) 2014 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. Introduction ....................................................2
2. Conventions Used in This Document ...............................4
2.1. Requirements Language ......................................4
2.2. Terminology ................................................4
3. Centralized versus Distributed Mobility Management ..............5
3.1. Centralized Mobility Management ............................6
3.2. Distributed Mobility Management ............................7
4. Problem Statement ...............................................8
5. Requirements ...................................................10
6. Security Considerations ........................................16
7. Contributors ...................................................17
8. References .....................................................20
8.1. Normative References ......................................20
8.2. Informative References ....................................21
1. Introduction
In the past decade, a fair number of network-layer mobility protocols
have been standardized [RFC6275] [RFC5944] [RFC5380] [RFC6301]
[RFC5213]. Although these protocols differ in terms of functions and
associated message formats, they all employ a mobility anchor to
allow a mobile node to remain reachable after it has moved to a
different network. Among other tasks that the anchor point performs,
the anchor point ensures connectivity by forwarding packets destined
to, or sent from, the mobile node. It is a centrally deployed
mobility anchor in the sense that the deployed architectures today
have a small number of these anchors and the traffic of millions of
mobile nodes in an operator network is typically managed by the same
Show full document text