RFC 9575: DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9575
- Published
- June 2024
- Authors
- A. Wiethuechter; S. Card; R. Moskowitz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 43
- 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 7039Source Address Validation Improvement (SAVI) FrameworkCurrent
October 2013
- RFC 9602Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing ArchitectureCurrent
October 2024
- RFC 9606DNS Resolver InformationCurrent
June 2024
- RFC 9542IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 ParametersCurrent
April 2024
- RFC 9539Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNSCurrent
February 2024
- RFC 9527DHCPv6 Options for the Homenet Naming AuthorityCurrent
January 2024
- RFC 9526Simple Provisioning of Public Names for Residential NetworksCurrent
January 2024
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?