UAS Remote ID
draft-ietf-drip-rid-04

Document Type Active Internet-Draft (drip WG)
Authors Robert Moskowitz  , Stuart Card  , Adam Wiethuechter  , Andrei Gurtov 
Last updated 2020-11-01
Replaces draft-ietf-drip-uas-rid
Stream IETF
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document (wg milestone: Sep 2020 - Solution space docum... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
DRIP                                                        R. Moskowitz
Internet-Draft                                            HTT Consulting
Updates: 7401, 7343 (if approved)                                S. Card
Intended status: Standards Track                         A. Wiethuechter
Expires: May 5, 2021                                  AX Enterprize, LLC
                                                               A. Gurtov
                                                    Linköping University
                                                        November 1, 2020

                             UAS Remote ID
                         draft-ietf-drip-rid-04

Abstract

   This document describes the use of Hierarchical Host Identity Tags
   (HHITs) as self-asserting IPv6 addresses and thereby a trustable
   Identifier for use as the UAS Remote ID.  HHITs self-attest to the
   included explicit hierarchy that provides Registrar discovery for
   3rd-party ID attestation.

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 May 5, 2021.

Copyright Notice

   Copyright (c) 2020 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

Moskowitz, et al.          Expires May 5, 2021                  [Page 1]
Internet-Draft                UAS Remote ID                November 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Nontransferablity of HHITs  . . . . . . . . . . . . . . .   3
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Terminology  . . . . . . . . . . . . . . . .   3
     2.2.  Notation  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Hierarchical HITs as Remote ID  . . . . . . . . . . . . . . .   5
     3.1.  Remote ID as one class of Hierarchical HITs . . . . . . .   5
     3.2.  Hierarchy in ORCHID Generation  . . . . . . . . . . . . .   5
     3.3.  Hierarchical HIT Registry . . . . . . . . . . . . . . . .   6
     3.4.  Remote ID Authentication using HHITs  . . . . . . . . . .   6
   4.  UAS ID HHIT in DNS  . . . . . . . . . . . . . . . . . . . . .   6
   5.  Other UTM uses of HHITs . . . . . . . . . . . . . . . . . . .   7
   6.  DRIP Requirements addressed . . . . . . . . . . . . . . . . .   7
   7.  ASTM Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
     9.1.  Hierarchical HIT Trust  . . . . . . . . . . . . . . . . .   9
     9.2.  Collision risks with Hierarchical HITs  . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Appendix A.  EU U-Space RID Privacy Considerations  . . . . . . .  12
   Appendix B.  The Hierarchical Host Identity Tag (HHIT)  . . . . .  13
     B.1.  HHIT prefix . . . . . . . . . . . . . . . . . . . . . . .  13
     B.2.  HHIT Suite IDs  . . . . . . . . . . . . . . . . . . . . .  13
       B.2.1.  8 bit HIT Suite IDs . . . . . . . . . . . . . . . . .  14
     B.3.  The Hierarchy ID (HID)  . . . . . . . . . . . . . . . . .  14
       B.3.1.  The Registered Assigning Authority (RAA)  . . . . . .  14
       B.3.2.  The Hierarchical HIT Domain Authority (HDA) . . . . .  15
   Appendix C.  ORCHIDs for Hierarchical HITs  . . . . . . . . . . .  15
     C.1.  Adding additional information to the ORCHID . . . . . . .  15
     C.2.  ORCHID Encoding . . . . . . . . . . . . . . . . . . . . .  17
       C.2.1.  Encoding ORCHIDs for HITv2  . . . . . . . . . . . . .  17
Show full document text