Drone Remote Identification Protocol (DRIP) Architecture
draft-ietf-drip-arch-00

The information below is for an old version of the document
Document Type Active Internet-Draft (drip WG)
Last updated 2020-05-22 (latest revision 2020-05-18)
Replaces draft-card-drip-arch
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document (wg milestones: May 2020 - Requirements and arc..., Jul 2020 - Requirements and arc... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD √Čric Vyncke
Send notices to (None)
DRIP                                                        S. Card, Ed.
Internet-Draft                                           A. Wiethuechter
Intended status: Informational                             AX Enterprize
Expires: 19 November 2020                                   R. Moskowitz
                                                          HTT Consulting
                                                                 S. Zhao
                                                                 Tencent
                                                             18 May 2020

        Drone Remote Identification Protocol (DRIP) Architecture
                        draft-ietf-drip-arch-00

Abstract

   This document defines an architecture for Drone Remote Identification
   Protocol (DRIP) Working Group protocols and services to support
   Unmanned Aircraft System Remote Identification (UAS RID) and RID-
   related communications, including its building blocks and their
   interfaces, all to be standardized.

   CAVEAT LECTOR: This draft version is undergoing substantial
   restructuring and is submitted to the DRIP WG only to spark
   discussion on architecture and to be adopted as a placeholder if
   there is consensus that there should be an architecture document
   (however far from any future consensus on that architecture this
   draft may be).

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 19 November 2020.

Card, et al.            Expires 19 November 2020                [Page 1]
Internet-Draft                  DRIP Arch                       May 2020

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
   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.  UAS RID Uses  . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  UAS RID Design Considerations . . . . . . . . . . . . . .   5
     1.3.  DRIP Goals  . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Requirements Terminology  . . . . . . . . . . . . . . . .   6
     2.2.  Additional Definitions  . . . . . . . . . . . . . . . . .   6
   3.  Entities and their Interfaces . . . . . . . . . . . . . . . .   7
     3.1.  Private Information Registry  . . . . . . . . . . . . . .   7
       3.1.1.  Background  . . . . . . . . . . . . . . . . . . . . .   7
       3.1.2.  Proposed Approach . . . . . . . . . . . . . . . . . .   7
     3.2.  Public Information Registry . . . . . . . . . . . . . . .   8
       3.2.1.  Background  . . . . . . . . . . . . . . . . . . . . .   8
       3.2.2.  Proposed Approach . . . . . . . . . . . . . . . . . .   8
     3.3.  CS-RID concept  . . . . . . . . . . . . . . . . . . . . .   8
       3.3.1.  Proposed optional CS-RID SDSP . . . . . . . . . . . .   8
       3.3.2.  Proposed optional CS-RID Finder . . . . . . . . . . .   9
   4.  Identifiers . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Background  . . . . . . . . . . . . . . . . . . . . . . .   9
     4.2.  Proposed Approach . . . . . . . . . . . . . . . . . . . .  10
   5.  Proposed Transactions . . . . . . . . . . . . . . . . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Appendix A.  Overview of Unmanned Aircraft Systems (UAS) Traffic
Show full document text