Mobility Practices and DMM Gap Analysis
draft-zuniga-dmm-gap-analysis-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Juan-Carlos Zúñiga , Carlos J. Bernardos , Telemaco Melia , Charles E. Perkins | ||
| Last updated | 2013-06-22 (Latest revision 2012-12-19) | ||
| 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
This document describes practices for the deployment of existing mobility protocols in a distributed mobility management (DMM) environment, and identifies the limitations in the current practices with respect to providing the expected DMM functionality. The practices description and gap analysis are performed for IP-based mobility protocols, dividing them into three main families: IP client-based, IP network-based, and 3GPP mobility solutions.
Authors
Juan-Carlos Zúñiga
Carlos J. Bernardos
Telemaco Melia
Charles E. Perkins
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)