Hierarchical HITs for HIPv2
draft-moskowitz-hierarchical-hip-03
|
| 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
Hierarchical HITs for HIPv2
draft-moskowitz-hierarchical-hip-03.txt
Abstract
This document describes using a hierarchical HIT to facilitate large
deployments in mobile networks.
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
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Moskowitz, et al. Expires December 28, 2017 [Page 1]
Internet-Draft Hierarchical HITs June 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirements Terminology . . . . . . . . . . . . . . . . 3
2.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 3
3. Problem Space . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Meeting the future of Mobile Networking . . . . . . . . . 3
3.2. Semi-permanency of Identities . . . . . . . . . . . . . . 4
3.3. Managing a large flat address space . . . . . . . . . . . 4
3.4. Defense against fraudulent HITs . . . . . . . . . . . . . 4
3.5. Desire for administrative control by RVS providers . . . 4
4. The Hierarchical Host Identity Tag (HIT) . . . . . . . . . . 5
4.1. The Hierarchy ID (HID) . . . . . . . . . . . . . . . . . 5
4.1.1. The Registered Assigning Authority (RAA) . . . . . . 5
4.1.2. The Hierarchical HIT Domain Authority (HDA) . . . . . 5
4.1.3. Example of the HID DNS . . . . . . . . . . . . . . . 6
4.1.4. Changes to ORCHIDv2 to support Hierarchical HITs . . 6
4.1.5. Collision risks with Hierarchical HITs . . . . . . . 7
5. HIP Parameters . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. HIT_SUITE_LIST . . . . . . . . . . . . . . . . . . . . . 7
5.2. CLIENT_INFO . . . . . . . . . . . . . . . . . . . . . . . 8
6. HHIT Registry services to support hierarchical HITs . . . . . 8
6.1. Hierarchical HIT Registration using X.509 Certificates . 8
6.2. Hierarchical HIT Registration using a PSK . . . . . . . . 9
6.3. Hierarchical HIT Registration Type . . . . . . . . . . . 9
6.4. Hierarchical HIT Registration Failure Type . . . . . . . 9
6.5. Registration failure behavior . . . . . . . . . . . . . . 9
6.5.1. Example of a simple HDA policy . . . . . . . . . . . 10
7. Using hierarchical HITs . . . . . . . . . . . . . . . . . . . 10
7.1. Contacting a HIP client . . . . . . . . . . . . . . . . . 10
7.2. Defense against fraudulent HITs . . . . . . . . . . . . . 11
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
9. RAA Management Organization Considerations . . . . . . . . . 11
10. Security Considerations . . . . . . . . . . . . . . . . . . . 11
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
12.1. Normative References . . . . . . . . . . . . . . . . . . 12
12.2. Informative References . . . . . . . . . . . . . . . . . 12
Show full document text