Skip to main content

DRIP Entity Tag (DET) for Unmanned Aircraft System Remote ID (UAS RID)
draft-ietf-drip-rid-37

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-drip-rid@ietf.org, drip-chairs@ietf.org, evyncke@cisco.com, mohamed.boucadair@orange.com, rfc-editor@rfc-editor.org, tm-rid@ietf.org
Subject: Protocol Action: 'DRIP Entity Tag (DET) for Unmanned Aircraft System Remote ID (UAS RID)' to Proposed Standard (draft-ietf-drip-rid-37.txt)

The IESG has approved the following document:
- 'DRIP Entity Tag (DET) for Unmanned Aircraft System Remote ID (UAS RID)'
  (draft-ietf-drip-rid-37.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-rid/


Ballot Text

Technical Summary
 
   This document specifies DRIP Entity Tags (DETs) that are used for
   drone identification purposes (a.k.a., UAS Remote ID). DETs rely
   upon Hierarchical Host Identity Tags (HHITs) which are defined as
   self-asserting IPv6 addresses. Also, these HHITs include explicit
   hierarchy to enable DNS queries and discovery of specific registrars
   for 3rd-party identification attestation purposes.

Working Group Summary

   This document ran 8 versions before adoption by the WG (including a
   version that passed surprisingly through without any validation and
   published as draft-ietf-drip-*).

   Regular slots were dedicated to this draft in several WG meetings.
   The authors implemented the outcomes of the discussions held in these
   meetings and the mailing list. 

   The doc shepherd has prepared a very detailed WG summary in his
   write-up, so, please refer to this write-up for more details.

Document Quality

   The various reviews helped to enhance the quality of the document.

   There are two implementations but the interoperation is yet to be tested:

    1) Linköping University is developing a prototype of DRIP implementation based on OpenHIP and OpenDroneID. They aim to make it available open-source after additional development and interop tests.
    2) one implementation AX Enterprize is involved in.


Personnel

   The document shepherd is Mohamed Boucadair <mohamed.boucadair@orange.com>

   The Responsible Area Director is Eric Vyncke <evyncke@cisco.com>

   The IANA Expert(s) for the registries in this document are:

- Robert Moskowitz <rgm@labs.htt-consult.com>
- adam.wiethuechter@axenterprize.com <adam.wiethuechter@axenterprize.com>

IANA Note

IANA is requested to allocate a new 28-bit prefix out of the IANA IPv6 Special Purpose Address Block.

This document requests IANA to create a new registry titled "Drone Remote ID Protocol" registry.  The following two subregistries should be created under that registry:

* Hierarchical HIT (HHIT) Prefixes (expert review)
* Hierarchical HIT (HHIT) Suite ID (IETF review)

IANA is requested to add a context to the "CGA Extension Type Tags" registry.

IANA is requested to add a change to the "Host Identity Protocol (HIP) Parameters" registry, "IPSECKEY Resource Record Parameters"  registry, and "HIT Suite ID" subregistry of the "Host Identity Protocol (HIP) Parameters" registry.

IANA is requested to create a subregistry "EdDSA Curve Label" (IETF review).





RFC Editor Note