Browse Prior Art Database

Requirements for Distributed Mobility Management (RFC7333)

IP.com Disclosure Number: IPCOM000238375D
Publication Date: 2014-Aug-21
Document File: 48 page(s) / 50K

Publishing Venue

The IP.com Prior Art Database

Related People

H. Chan: AUTHOR [+6]

Abstract

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 anchor. Such a mobility anchor may still have to reside in the subscriber's provider network even when the subscriber is roaming to

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

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