Mobility challenges in virtualization environments
draft-bernardos-dmm-mobility-virtualization-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Carlos J. Bernardos , Alain Mourad | ||
| Last updated | 2023-07-25 (Latest revision 2023-01-12) | ||
| RFC stream | (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
Mobility is no longer restricted to physical end systems roaming among radio points of attachment. Current mobile network deployments do not only consider the traditional client-server model, but also include scenarios in which services are decomposed into functions that run on virtualized resources, thus becoming virtual functions. This opens the door for new scenarios in which mobility now includes: (i) the end-system mobility (traditional scenario), (ii) a physical resource hosting a virtual function (part of a service being consumed by a end-system) moving, and (iii) a virtual function part of a service moving (migrating) to a different physical resource. As these scenarios are expected to be more commonly deployed in the short future, this documents aims at presenting the new mobility- related scenarios and the potential gaps in terms of IETF protocols.
Authors
Carlos J. Bernardos
Alain Mourad
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)