RFC 9575

DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID), June 2024

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
A. Wiethuechter, Ed.
S. Card
R. Moskowitz
drip (int)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9575

Discuss this RFC: Send questions or comments to the mailing list tm-rid@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9575


The Drone Remote Identification Protocol (DRIP), plus trust policies and periodic access to registries, augments Unmanned Aircraft System (UAS) Remote Identification (RID), enabling local real-time assessment of trustworthiness of received RID messages and observed UAS, even by Observers lacking Internet access. This document defines DRIP message types and formats to be sent in Broadcast RID Authentication Messages to verify that attached and recently detached messages were signed by the registered owner of the DRIP Entity Tag (DET) claimed.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search