[Drip] Re: draft-ietf-drip-dki

[Robert Moskowitz <[e-mail]>]

I am also working with Western Michigan University and Embry-Riddle 
Aviation University.

WMU is further along. They have both an UA code base and an Observer 
code base (both IOS and Android) that is processing DRIP messages 
(principally Wrapper per 9575).  They are working with my first efforts 
on a DKI test per draft-ietf-drip-dki-03.

ERAU is doing catch up with WMU.  The professors (and dept chairs) meet 
early Feb at the ERAU Aviation Cyber Symposium.

Also nps.edu (Dr. Britta Hale of MLS work) is working away, but since 
they are DoD, they will probably move to Adam's test RAA when he gets 
that up and going.  Leapfrogging, as it were, over where I was with -03.

I expect that WMU will soon have a public github for others to leverage 
from.


On 2/7/25 7:32 AM, Andrei Gurtov wrote:
>
> Hello,
>
> Full WG adoption is a good idea. We are actively working with DRIP 
> research, implemented a recent version of -registries. I am planning 
> to upload a new version of Android app with its support.
>
> LiU got allocated a subdomain for issuing own DETs according to the draft.
>
> br Andrei
>
> On 2025-02-06 16:21, [e-mail] wrote:
>>
>> 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 <[e-mail]>
>> *Envoyé :* jeudi 6 février 2025 15:59
>> *À :* BOUCADAIR Mohamed INNOV/NET <[e-mail]>; 
>> [e-mail]; [e-mail]
>> *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:* [e-mail] <[e-mail]>
>> *Sent:* Thursday, February 6, 2025 9:52:28 AM
>> *To:* [e-mail] <[e-mail]>; [e-mail] 
>> <[e-mail]>
>> *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/ 
>> <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.
>>
>

-- 
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:[e-mail]

There's no limit to what can be accomplished if it doesn't matter who 
gets the credit