HIP Enabled ID/Loc separation for fast 5GPP IP mobility
draft-moskowitz-hip-based-5gpp-ip-mobility-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-06-26
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
HIP R. Moskowitz
Internet-Draft X. Xu
Intended status: Standards Track B. Liu
Expires: December 28, 2017 Huawei
June 26, 2017
HIP Enabled ID/Loc separation for fast 5GPP IP mobility
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 28, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Moskowitz, et al. Expires December 28, 2017 [Page 1]
Internet-Draft HIP enabled 5GPP IP Mobility June 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirements Terminology . . . . . . . . . . . . . . . . 3
2.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 3
3. The components to a HIP-based Mobile world . . . . . . . . . 3
3.1. Service to HIT mapping by device/owner name . . . . . . . 3
3.2. HIT to IP mapping service . . . . . . . . . . . . . . . . 3
3.3. Shortest Path Routing support . . . . . . . . . . . . . . 4
4. Providing services to meet mobility needs . . . . . . . . . . 4
4.1. Scaleable HITs . . . . . . . . . . . . . . . . . . . . . 4
4.2. Additional services associated with the HDA RVS . . . . . 4
4.3. Preparing to use an HHIT . . . . . . . . . . . . . . . . 5
4.4. Protecting privacy of an HHIT . . . . . . . . . . . . . . 5
4.5. Contacting a device based on its HHIT . . . . . . . . . . 5
4.6. Intra-HDA peering agreements . . . . . . . . . . . . . . 5
4.7. Maintaining the HIP session through all mobility events . 6
5. HIP proxies to Legacy (non-HIP) hosts . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . 6
Appendix A. Calculating Collision Probabilities . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
IP mobility in the next generation cellular networks will demand
shortest path routing, transportation of data secure from a laundry
list of attacks, minimal cost infrastructure, and a viable business
model for the providers of the 5GPP infrastructure.
Infrastructure costs for the 5GPP network come in many forms. Costs
can arise from the cost to support network services, or costs to
encapsulate data, or network over-provisioning costs to reduce
network delays. At the heart of all the 3GPP mobility costs is the
Show full document text