rfc9153v5.txt   rfc9153.txt 
Internet Engineering Task Force (IETF) S. Card, Ed. Internet Engineering Task Force (IETF) S. Card, Ed.
Request for Comments: 9153 A. Wiethuechter Request for Comments: 9153 A. Wiethuechter
Category: Informational AX Enterprize Category: Informational AX Enterprize
ISSN: 2070-1721 R. Moskowitz ISSN: 2070-1721 R. Moskowitz
HTT Consulting HTT Consulting
A. Gurtov A. Gurtov
Linköping University Linköping University
January 2022 February 2022
Drone Remote Identification Protocol (DRIP) Requirements and Terminology Drone Remote Identification Protocol (DRIP) Requirements and Terminology
Abstract Abstract
This document defines terminology and requirements for solutions This document defines terminology and requirements for solutions
produced by the Drone Remote Identification Protocol (DRIP) Working produced by the Drone Remote Identification Protocol (DRIP) Working
Group. These solutions will support Unmanned Aircraft System Remote Group. These solutions will support Unmanned Aircraft System Remote
Identification and tracking (UAS RID) for security, safety, and other Identification and tracking (UAS RID) for security, safety, and other
purposes (e.g., initiation of identity-based network sessions purposes (e.g., initiation of identity-based network sessions
skipping to change at line 538 skipping to change at line 538
and other potential applications, UAS RID is the urgent motivation and other potential applications, UAS RID is the urgent motivation
and clear initial focus of DRIP. Existing Internet resources and clear initial focus of DRIP. Existing Internet resources
(protocol standards, services, infrastructure, and business models) (protocol standards, services, infrastructure, and business models)
should be leveraged. should be leveraged.
1.4. Document Scope 1.4. Document Scope
This document describes the problem space for UAS RID conforming to This document describes the problem space for UAS RID conforming to
proposed regulations and external technical standards, defines common proposed regulations and external technical standards, defines common
terminology, specifies numbered requirements for DRIP, identifies terminology, specifies numbered requirements for DRIP, identifies
some important considerations (IANA, security, privacy and some important considerations (IANA, security, privacy, and
transparency), and discusses limitations. transparency), and discusses limitations.
A natural Internet-based approach to meet these requirements is A natural Internet-based approach to meet these requirements is
described in a companion architecture document [DRIP-ARCH] and described in a companion architecture document [DRIP-ARCH] and
elaborated in other DRIP documents. elaborated in other DRIP documents.
2. Terms and Definitions 2. Terms and Definitions
2.1. Requirements Terminology 2.1. Requirements Terminology
skipping to change at line 1403 skipping to change at line 1403
least one USS. Each UAS is registered by its operator in at least least one USS. Each UAS is registered by its operator in at least
one USS. Each operational intent is submitted to one USS; if one USS. Each operational intent is submitted to one USS; if
approved, that UAS and operator can commence that operation. During approved, that UAS and operator can commence that operation. During
the operation, status and location of that UAS must be reported to the operation, status and location of that UAS must be reported to
that USS, which, in turn, provides information as needed about that that USS, which, in turn, provides information as needed about that
operator, UAS, and operation into the UTM system and to Observers via operator, UAS, and operation into the UTM system and to Observers via
Network RID. Network RID.
USS provide services not limited to Network RID; indeed, the primary USS provide services not limited to Network RID; indeed, the primary
USS function is deconfliction of airspace usage between different UAS USS function is deconfliction of airspace usage between different UAS
(and their operators). It will occassionally deconflict UAS from (and their operators). It will occasionally deconflict UAS from non-
non-UAS operations, such as manned aircraft and rocket launch. Most UAS operations, such as manned aircraft and rocket launch. Most
deconfliction involving a given operation is hoped to be completed deconfliction involving a given operation is hoped to be completed
prior to commencing that operation; this is called "strategic prior to commencing that operation; this is called "strategic
deconfliction". If that fails, "tactical deconfliction" comes into deconfliction". If that fails, "tactical deconfliction" comes into
play; AirBorne DAA (ABDAA) may not involve USS, but Ground-Based DAA play; AirBorne DAA (ABDAA) may not involve USS, but Ground-Based DAA
(GBDAA) likely will. Dynamic constraints, formerly called "UAS (GBDAA) likely will. Dynamic constraints, formerly called "UAS
Volume Restrictions (UVRs)", can be necessitated by circumstances Volume Restrictions (UVRs)", can be necessitated by circumstances
such as local emergencies and extreme weather, specified by such as local emergencies and extreme weather, specified by
authorities on the ground, and propagated in UTM. authorities on the ground, and propagated in UTM.
No role for USS in Broadcast RID is currently specified by regulators No role for USS in Broadcast RID is currently specified by regulators
skipping to change at line 2055 skipping to change at line 2055
European Parliament and Council, "Commission Delegated European Parliament and Council, "Commission Delegated
Regulation (EU) 2019/945 of 12 March 2019 on unmanned Regulation (EU) 2019/945 of 12 March 2019 on unmanned
aircraft systems and on third-country operators of aircraft systems and on third-country operators of
unmanned aircraft systems", March 2019, unmanned aircraft systems", March 2019,
<https://eur-lex.europa.eu/eli/reg_del/2019/945/oj>. <https://eur-lex.europa.eu/eli/reg_del/2019/945/oj>.
[DRIP-ARCH] [DRIP-ARCH]
Card, S., Wiethuechter, A., Moskowitz, R., Zhao, S., Ed., Card, S., Wiethuechter, A., Moskowitz, R., Zhao, S., Ed.,
and A. Gurtov, "Drone Remote Identification Protocol and A. Gurtov, "Drone Remote Identification Protocol
(DRIP) Architecture", Work in Progress, Internet-Draft, (DRIP) Architecture", Work in Progress, Internet-Draft,
draft-ietf-drip-arch-18, 15 December 2021, draft-ietf-drip-arch-20, 28 January 2022,
<https://datatracker.ietf.org/doc/html/draft-ietf-drip- <https://datatracker.ietf.org/doc/html/draft-ietf-drip-
arch-18>. arch-20>.
[ENISACSIRT] [ENISACSIRT]
European Union Agency for Cybersecurity (ENISA), European Union Agency for Cybersecurity (ENISA),
"Actionable information for Security Incident Response", "Actionable information for Security Incident Response",
November 2014, <https://www.enisa.europa.eu/topics/csirt- November 2014, <https://www.enisa.europa.eu/topics/csirt-
cert-services/reactive-services/copy_of_actionable- cert-services/reactive-services/copy_of_actionable-
information/actionable-information>. information/actionable-information>.
[EU2018] European Parliament and Council, "2015/0277 (COD) PE-CONS [EU2018] European Parliament and Council, "2015/0277 (COD) PE-CONS
2/18", June 2018, 2/18", June 2018,
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/