A Distributed Mobility Management Solution in LISP networks
draft-zhang-dmm-lisp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Hongke Zhang | ||
| Last updated | 2013-03-11 (Latest revision 2012-09-03) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In traditional Internet architectures, current centralized mobility management solutions face scalability issues due to the creation of network bottlenecks and a single mobility agent of failures. To address these issues, we propose a Distributed Mobility Management solution in Locator/ID Separation Protocol (DMMLISP). We divide the network into many domains according to the area of Autonomous Systems (ASs). Each domain consists of a Mapping Server and several Tunnel Routers (xTRs). The Mapping Server stores global mappings between EID (Endpoint Identifier) prefixes and AS Numbers (ASNs) to lookup the mobile nodes'(MNs') home domain. Meanwhile, the Mapping Server also contains ASN-to-xTR mappings so that it can forward Map- Register and Map-Request messages to any xTR of the MN's home domain, thus enhancing reliability. In addition, the xTRs in each domain constitute one-hop DHT (Distributed Hash Table). Moreover, any xTR in the MN's home domain may be the home agent of MNs, and the MNs' EID-to-RLOC (Routing Locator) mapping is stored in two xTRs using two hash functions. In this way, it not only supports quick lookup but also improves scalability and survivability.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)