Subject: [Drip] Re: draft-ietf-drip-dki
From: Stu Card <[email-masked]>
To: "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>
Date: Thu, 6 Feb 2025 19:56:56 +0000
List-Id: Drone Remote Identification Protocol <tm-rid.ietf.org>

Bob, whom cam you recruit from IOTOPS and/or elsewhere to assist you with this draft, and whom beyond those few to review it?

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: [email-masked] <[email-masked]>
Sent: Thursday, February 6, 2025 10:21:03 AM
To: Stu Card <[email-masked]>; [email-masked] <[email-masked]>; [email-masked] <[email-masked]>
Subject: RE: draft-ietf-drip-dki

Hi Stu,

(as Chair this time)

The WG can always reconsider that decision, but I’m afraid that we will need to show there is enough energy to work on this.

IOTOPS may have more eyes to look into this.

Cheers,

Med

De : Stu Card <[email-masked]>
Envoyé : jeudi 6 février 2025 15:59
À : BOUCADAIR Mohamed INNOV/NET <[email-masked]>; [email-masked]; [email-masked]
Objet : Re: draft-ietf-drip-dki

To facilitate adoption of DRIP by the aviation, law enforcement, physical security and public safety communities, who are largely ignorant of the organizational structure (indeed, largely of the existence) of IETF, our WG may want to reconsider DKI publication as part of a coherent set of DRIP RFCs.

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________

From: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Sent: Thursday, February 6, 2025 9:52:28 AM
To: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>; [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Subject: draft-ietf-drip-dki

Hi Bob, all,

We adopted draft-ietf-drip-dki in the past to meet the following milestone:

“Adopt a support document for operationalizing DRIP (Informational; not necessarily for publication as RFC)”

The draft was tagged with “Adopted for WG Info Only” [1]

The authors may want to socialize the draft in iotops or even target continuing developing it there. FWIW, IOTOPS charter has the following in the charter:

“The IETF works on a number of technologies related to IoT. This includes, but is not limited to work done in ACE, ANIMA, CBOR, CORE, DRIP, LAKE, LPWAN, LWIG, ROLL, SUIT, TEEP, 6LO, 6TISCH, and other working groups. IOTOPS is intended to be a discussion venue where people can discuss how various IoT-related technologies fit together.”

Cheers,

Med

(as a contributor)

[1] see more about this state at https://datatracker.ietf.org/doc/help/state/draft-stream-ietf/

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.