Skip to main content

DRIP Entity Tag Authentication Formats & Protocols for Broadcast Remote ID

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: The IESG <>,,,,,,
Subject: Protocol Action: 'DRIP Entity Tag Authentication Formats & Protocols for Broadcast Remote ID' to Proposed Standard (draft-ietf-drip-auth-49.txt)

The IESG has approved the following document:
- 'DRIP Entity Tag Authentication Formats & Protocols for Broadcast
   Remote ID'
  (draft-ietf-drip-auth-49.txt) as Proposed Standard

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

The IESG contact persons are Erik Kline and Éric Vyncke.

A URL of this Internet-Draft is:

Ballot Text

# Technical Summary

   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 then lacking Internet access.  This document
   defines DRIP message types and formats to be sent in Broadcast RID
   Authentication Messages to verify that attached and recent detached
   messages were signed by the registered owner of the DRIP Entity Tag
   (DET) claimed.

# Working Group Summary

There is clear consensus in the DRIP WG to progress this specification.

The document went into 3 WGLCs. No controversy was raised during the development
of this specification, except the issue related to the code points to be
used for identifying the various authentication messages given that the process
for assigning and managing that space was not in place. The issue is now fixed
and the IETF has formally requested the allocation of 4 code points.
The codepoints will be echoed in an IANA registry (checked with IANA).

# Document Quality

In addition to a proprietary implementation, the following ones were

* Implementation by Linköping University 

* DRIP Importer

Some key directorate reviews were arranged by the Chairs early in the process
to tag and fix security issues, in particular. The IETF Last Call generated 
additional reviews (dnsdir, tsvart, IANA) with comments incorporated in the -44 revision.

Also, LSs were sent to ASTM and ICAO about the SAM codepoints to identify DRIP
authentication messages. ASTM and ICAO representatives attended many of DRIP
meetings (including interims [21]). No technical issue was raised by ASTM/ICAO,
but the main blocking point was the management of the SAP codepoints.
Codepoints are not formally assigned to the IETF. As per the discussion with
IANA, it is OK to mirror these codes in the IANA DRIP registry.

# Personnel

   The Document Shepherd for this document is Mohamed Boucadair. The
   Responsible Area Director is Éric Vyncke.

# IANA Note

This document requests two new registries, for DRIP SAM Type and DRIP Frame Type, under the DRIP registry group. 
The former is actually a mirror of ASTM/ICAO registry.

RFC Editor Note