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

Document Type Active Internet-Draft (drip WG)
Authors Stuart Card  , Adam Wiethuechter  , Robert Moskowitz  , Andrei Gurtov 
Last updated 2021-02-18 (latest revision 2021-02-17)
Replaces draft-card-drip-reqs
Stream IETF
Intended RFC status Informational
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state Submitted to IESG for Publication (wg milestones: May 2020 - Requirements and arc..., Sep 2020 - Requirements and arc... )
Document shepherd Mohamed Boucadair
Shepherd write-up Show (last changed 2021-02-18)
IESG IESG state AD Evaluation
Action Holders
(None)
Consensus Boilerplate Yes
Telechat date
Responsible AD Éric Vyncke
Send notices to tm-rid@ietf.org, mohamed.boucadair@orange.com
DRIP                                                        S. Card, Ed.
Internet-Draft                                           A. Wiethuechter
Intended status: Informational                             AX Enterprize
Expires: 21 August 2021                                     R. Moskowitz
                                                          HTT Consulting
                                                               A. Gurtov
                                                    Linköping University
                                                        17 February 2021

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

Abstract

   This document defines terminology and requirements for Drone Remote
   Identification Protocol (DRIP) Working Group solutions to support
   Unmanned Aircraft System Remote Identification and tracking (UAS RID)
   for security, safety, 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 RID and to enable enhanced related services, and
   will enable online and offline verification that 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 21 August 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Card, et al.             Expires 21 August 2021                 [Page 1]
Internet-Draft              DRIP Requirements              February 2021

   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
     1.1.  Motivation and External Influences  . . . . . . . . . . .   2
     1.2.  Concerns and Constraints  . . . . . . . . . . . . . . . .   7
     1.3.  DRIP Scope  . . . . . . . . . . . . . . . . . . . . . . .   9
     1.4.  Document Scope  . . . . . . . . . . . . . . . . . . . . .  10
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .  10
     2.1.  Requirements Terminology  . . . . . . . . . . . . . . . .  10
     2.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .  11
   3.  UAS RID Problem Space . . . . . . . . . . . . . . . . . . . .  18
     3.1.  Network RID . . . . . . . . . . . . . . . . . . . . . . .  20
     3.2.  Broadcast RID . . . . . . . . . . . . . . . . . . . . . .  23
     3.3.  USS in UTM and RID  . . . . . . . . . . . . . . . . . . .  26
     3.4.  DRIP Focus  . . . . . . . . . . . . . . . . . . . . . . .  27
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .  28
     4.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .  28
     4.2.  Identifier  . . . . . . . . . . . . . . . . . . . . . . .  30
     4.3.  Privacy . . . . . . . . . . . . . . . . . . . . . . . . .  31
     4.4.  Registries  . . . . . . . . . . . . . . . . . . . . . . .  33
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  34
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  34
   7.  Privacy and Transparency Considerations . . . . . . . . . . .  35
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  36
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  36
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  36
   Appendix A.  Discussion and Limitations . . . . . . . . . . . . .  39
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  41
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  41

1.  Introduction

1.1.  Motivation and External Influences

   Many considerations (especially safety and security) necessitate
   Unmanned Aircraft Systems (UAS) Remote Identification and tracking
Show full document text