RFC 9575 on DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID)

A new Request for Comments is now available in online RFC libraries.

        RFC 9575

        Title:      DRIP Entity Tag (DET) Authentication 
                    Formats and Protocols for Broadcast Remote 
                    Identification (RID) 
        Author:     A. Wiethuechter, Ed.,
                    S. Card,
                    R. Moskowitz
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2024
        Mailbox:    adam.wiethuechter@axenterprize.com,
                    stu.card@axenterprize.com,
                    rgm@labs.htt-consult.com
        Pages:      43
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-drip-auth-49.txt

        URL:        https://www.rfc-editor.org/info/rfc9575

        DOI:        10.17487/RFC9575

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.

This document is a product of the Drone Remote ID Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC