[Drip] Protocol Action: 'DRIP Entity Tag Authentication Formats & Protocols for Broadcast Remote ID' to Proposed Standard (draft-ietf-drip-auth-49.txt)
The IESG <iesg-secretary@ietf.org> Thu, 22 February 2024 14:26 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: tm-rid@ietf.org
Delivered-To: tm-rid@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 29467C1524DC; Thu, 22 Feb 2024 06:26:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.5.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, draft-ietf-drip-auth@ietf.org, drip-chairs@ietf.org, evyncke@cisco.com, mohamed.boucadair@orange.com, rfc-editor@rfc-editor.org, tm-rid@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Message-ID: <170861201916.19631.463617531432217826@ietfa.amsl.com>
Date: Thu, 22 Feb 2024 06:26:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/PoXdzTMxTHsA7qHFuNLUSnFZ6_s>
Subject: [Drip] Protocol Action: 'DRIP Entity Tag Authentication Formats & Protocols for Broadcast Remote ID' to Proposed Standard (draft-ietf-drip-auth-49.txt)
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Drone Remote Identification Protocol <tm-rid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tm-rid/>
List-Post: <mailto:tm-rid@ietf.org>
List-Help: <mailto:tm-rid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2024 14:26:59 -0000
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: https://datatracker.ietf.org/doc/draft-ietf-drip-auth/ # 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 disclosed: * Implementation by Linköping University - https://mailarchive.ietf.org/arch/msg/tm-rid/SGIgyJz4HjXkOkBzPIpoJXX_OsU/ - https://play.google.com/store/apps/details?id=org.securedroneid.android&pli=1 * DRIP Importer https://github.com/openutm/verification/tree/main/flight_blender_e2e_integration/ietf-drip 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.