Hierarchical HITs for HIPv2
draft-moskowitz-hip-hierarchical-hit-01

Document Type Active Internet-Draft (individual)
Last updated 2019-10-16
Replaces draft-moskowitz-hierarchical-hip
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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                                            HTT Consulting
Intended status: Standards Track                                 S. Card
Expires: 18 April 2020                                   A. Wiethuechter
                                                           AX Enterprize
                                                         16 October 2019

                      Hierarchical HITs for HIPv2
                draft-moskowitz-hip-hierarchical-hit-01

Abstract

   This document describes using a hierarchical HIT to facilitate large
   deployments of managed devices.  Hierarchical HITs differ from HIPv2
   flat HITs by only using 64 bits for mapping the Host Identity,
   freeing 32 bits to bind in a hierarchy of Registering Entities that
   provide services to the consumers of hierarchical HITs.

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 https://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 18 April 2020.

Copyright Notice

   Copyright (c) 2019 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 (https://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

Moskowitz, et al.         Expires 18 April 2020                 [Page 1]
Internet-Draft              Hierarchical HITs               October 2019

   as described in Section 4.e of 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.  Problem Space . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Meeting the future of Mobile Devices in a public
           space . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Semi-permanency of Identities . . . . . . . . . . . . . .   4
     3.3.  Managing a large flat address space . . . . . . . . . . .   4
     3.4.  Defense against fraudulent HITs . . . . . . . . . . . . .   4
   4.  The Hierarchical Host Identity Tag (HHIT) . . . . . . . . . .   4
     4.1.  HHIT prefix . . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  HHIT Suite IDs  . . . . . . . . . . . . . . . . . . . . .   5
     4.3.  The Hierarchy ID (HID)  . . . . . . . . . . . . . . . . .   5
       4.3.1.  The Registered Assigning Authority (RAA)  . . . . . .   5
       4.3.2.  The Hierarchical HIT Domain Authority (HDA) . . . . .   6
       4.3.3.  Example of the HID DNS  . . . . . . . . . . . . . . .   6
       4.3.4.  HHIT DNS  . . . . . . . . . . . . . . . . . . . . . .   6
       4.3.5.  Changes to ORCHIDv2 to support Hierarchical
               HITs  . . . . . . . . . . . . . . . . . . . . . . . .   7
       4.3.6.  Collision risks with Hierarchical HITs  . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Calculating Collision Probabilities  . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   This document expands on HIPv2 [RFC7401] to describe the structure of
   a hierarchical HIT (HHIT).  Some of the challenges for large scale
   deployment addressed by HHITs are presented.  The basics for the
   hierarchical HIT registries are defined here.

   Separate documents will further expand on the registry service and
   how a device can advertise its availability and services provided.

Show full document text