DRIP Registries
draft-wiethuechter-drip-registries-00

Document Type Active Internet-Draft (individual)
Authors Adam Wiethuechter  , Stuart Card  , Robert Moskowitz 
Last updated 2021-02-22
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) 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)
drip Working Group                                       A. Wiethuechter
Internet-Draft                                                   S. Card
Intended status: Standards Track                      AX Enterprize, LLC
Expires: 26 August 2021                                     R. Moskowitz
                                                          HTT Consulting
                                                        22 February 2021

                            DRIP Registries
                 draft-wiethuechter-drip-registries-00

Abstract

   TODO

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 26 August 2021.

Copyright Notice

   Copyright (c) 2021 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
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Wiethuechter, et al.     Expires 26 August 2021                 [Page 1]
Internet-Draft                 registries                  February 2021

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Required Terminology  . . . . . . . . . . . . . . . . . .   2
     2.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Provisioning  . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Overview of Transactions  . . . . . . . . . . . . . . . .   3
     3.2.  HHIT Delegation . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Manufacturer  . . . . . . . . . . . . . . . . . . . . . .   4
     3.4.  Registry  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.5.  Operator  . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.6.  Aircraft  . . . . . . . . . . . . . . . . . . . . . . . .   6
       3.6.1.  Standard Provisioning . . . . . . . . . . . . . . . .   7
       3.6.2.  Operator Assisted Provisioning  . . . . . . . . . . .   9
       3.6.3.  Initial Provisioning  . . . . . . . . . . . . . . . .  10
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     5.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   TODO

2.  Terminology

2.1.  Required Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.2.  Definitions

   See [drip-requirements] for common DRIP terms.

   HDA:  Hierarchial HIT Domain Authority.  The 16 bit field identifying
      the HIT Domain Authority under a RAA.

   HID:  Hierarchy ID.  The 32 bit field providing the HIT Hierarchy ID.

   RAA:  Registered Assigning Authority.  The 16 bit field identifying
      the Hierarchical HIT Assigning Authority.

Wiethuechter, et al.     Expires 26 August 2021                 [Page 2]
Internet-Draft                 registries                  February 2021

3.  Provisioning

   Under DRIP UAS RID a special provisioning procedure is required to
   properly generate and distribute the certificates and attestations to
   all parties in the USS/UTM ecosystem using DRIP RID.

   Keypairs are expected to be generated on the device hardware it will
   be used on.  Due to hardware limitations (see Section 4) and
   connectivity it is acceptable under DRIP RID to generate keypairs for
   the Aircraft on Operator devices and later securely inject them into
   the Aircraft (as defined in Section 3.6.2).  The methods to securely
Show full document text