RFC 9153: Drone Remote Identification Protocol (DRIP) Requirements and Terminology
In plain English — editorial summary, not part of the RFC
This document defines terminology and requirements for solutions produced by the Drone Remote Identification Protocol (DRIP) Working Group. These solutions will support Unmanned Aircraft System Remote Identification and tracking (UAS RID) for security, safety, and other purposes (e.g., initiation of identity-based network sessions supporting UAS applications). DRIP will facilitate use of existing Internet resources to support RID and to enable enhanced related services, and it will enable online and offline verification that RID information is trustworthy.
Document record
- Document ID
- RFC9153
- Published
- February 2022
- Authors
- S. Card; A. Wiethuechter; R. Moskowitz; A. Gurtov
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9434Drone Remote Identification Protocol (DRIP) ArchitectureCurrent
July 2023
- RFC 9159IPv6 Mesh over BLUETOOTH(R) Low Energy Using the Internet Protocol Support Profile (IPSP)Current
December 2021
- RFC 9171Bundle Protocol Version 7Updated
January 2022
- RFC 9172Bundle Protocol Security (BPSec)Current
January 2022
- RFC 9173Default Security Contexts for Bundle Protocol Security (BPSec)Current
January 2022
- RFC 9174Delay-Tolerant Networking TCP Convergence-Layer Protocol Version 4Current
January 2022
- RFC 9131Gratuitous Neighbor Discovery: Creating Neighbor Cache Entries on First-Hop RoutersCurrent
October 2021
- RFC 9178Building Power-Efficient Constrained Application Protocol (CoAP) Devices for Cellular NetworksCurrent
May 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?