DRIP Entity Tag Authentication Formats and Protocols for Broadcast Remote Identification
RFC 9575, “DRIP Entity Tag Authentication Formats and Protocols for Broadcast Remote Identification”, is a Proposed Standard document published in June 2024 by A. Wiethuechter, S. Card, R. Moskowitz. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9575 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9574 Optimized Ingress Replication Solution for Ethernet VPNs
- RFC 9576 The Privacy Pass Architecture
- RFC 9573 MVPN/EVPN Tunnel Aggregation with Common Labels
- RFC 9577 The Privacy Pass HTTP Authentication Scheme
- RFC 9572 Updates to EVPN Broadcast, Unknown Unicast, or Multicast Procedures
- RFC 9578 Privacy Pass Issuance Protocols
- RFC 9571 Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels
- RFC 9579 Use of Password-Based Message Authentication Code 1 in PKCS #12 Syntax