Drone Remote Identification Protocol (DRIP) Requirements
draft-ietf-drip-reqs-01

Document Type Active Internet-Draft (drip WG)
Last updated 2020-05-25
Replaces draft-card-drip-reqs
Stream IETF
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
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: 26 November 2020                                   R. Moskowitz
                                                          HTT Consulting
                                                               A. Gurtov
                                               Linköping University
                                                             25 May 2020

        Drone Remote Identification Protocol (DRIP) Requirements
                        draft-ietf-drip-reqs-01

Abstract

   This document defines the requirements for Drone Remote
   Identification Protocol (DRIP) Working Group protocols to support
   Unmanned Aircraft System Remote Identification and tracking (UAS RID)
   for safety, regulatory compliance and other purposes.

   Complementing external technical standards as regulator-accepted
   means of compliance with UAS RID regulations, DRIP will:

      facilitate use of existing Internet resources to support UAS RID
      and to enable enhanced related services;

      enable on-line and off-line verification that UAS RID information
      is trustworthy.

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

Card, et al.            Expires 26 November 2020                [Page 1]
Internet-Draft                  DRIP Reqs                       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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Requirements Terminology  . . . . . . . . . . . . . . . .   6
     2.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  UAS RID Problem Space . . . . . . . . . . . . . . . . . . . .  12
     3.1.  Network RID . . . . . . . . . . . . . . . . . . . . . . .  13
     3.2.  Broadcast RID . . . . . . . . . . . . . . . . . . . . . .  14
     3.3.  DRIP Focus  . . . . . . . . . . . . . . . . . . . . . . .  14
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .  15
     4.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .  16
     4.2.  Identifier  . . . . . . . . . . . . . . . . . . . . . . .  17
     4.3.  Privacy . . . . . . . . . . . . . . . . . . . . . . . . .  18
     4.4.  Registries  . . . . . . . . . . . . . . . . . . . . . . .  18
   5.  Discussion and Limitations  . . . . . . . . . . . . . . . . .  19
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  21
   References  . . . . . . . . . . . . . . . . . . . . . . . . . . .  21
     Normative References  . . . . . . . . . . . . . . . . . . . . .  21
     Informative References  . . . . . . . . . . . . . . . . . . . .  21
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23

1.  Introduction

   Many considerations (especially safety) dictate that UAS be remotely
   identifiable.  Any observer with responsibilities involving aircraft
   inherently must classify them situationally according to basic
   considerations, as illustrated notionally in Figure 1 below.

Card, et al.            Expires 26 November 2020                [Page 2]
Internet-Draft                  DRIP Reqs                       May 2020

                        xxxxxxx        +--------------+
Show full document text