HIP Enabled ID/Loc separation for fast 5GPP IP mobility
draft-moskowitz-hip-based-5gpp-ip-mobility-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-12-28 (latest revision 2017-06-26) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-moskowitz-hip-based-5gpp-ip-mobility-02.txt
Abstract
HIP [RFC7401] stands alone in providing a secure Endpoint ID for decoupling the Internetworking and Transport protocol layers. The addition of a secure rendezvous service to facilitate mobility will form the cornerstones for this 5GPP mobility technology. This document will describe complete mobility environment and the additional components needed.
Authors
Robert Moskowitz
(rgm@labs.htt-consult.com)
Xiaohu Xu
(xuxiaohu@huawei.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)