[Secdispatch] Re: Outcomes from the joint art and sec dispatch session @ IETF 123

[Debra Petta <[e-mail]>]

Hi Dispatch -

I have a question regarding the formation of a BOF.  If my outcome is to have a BOF, is it necessary for me to submit a BOF proposal as outlined in https://www.ietf.org/process/bofs/,
or because that was already the agreed-upon outcome should I just start the formation of my BOF?

Should my BOF just be through an online group discussion using the assigned IETF mailing list or do I need to also request time at the next IETF meeting?

Thanks in advance for the clarification.

-Debra

From: Pengshuping (Peng Shuping) <pengshuping=[e-mail]>
Sent: Thursday, July 24, 2025 5:37 AM
To: [e-mail]; [e-mail]
Cc: [e-mail]; [e-mail]
Subject: [Secdispatch] Outcomes from the joint art and sec dispatch session @ IETF 123


Hi,



Please find a summary of the dispatch outcomes of the joint dispatch session of sec and art.



### ART Topics

1. Open Cloud Mesh

A WG-Forming BoF

2. RFC 4130 Specification Update (AS2 EDIINT)

A BOF and make sure to engage people who are willing to do work

3. JSON Challenger

To work with CBOR chairs and ADs to see the CBOR rechartering possibilities

4. The agent:// Protocol -- A URI-Based Framework for Interoperable Agents

A non-WG-Forming BoF



### Joint ART/SEC Topics

1. JSContact/EARL Peer-to-Peer Security Scheme

CALEXT WG for the JSContact and JOSE or a BoF for the crypto part

2. Unobtrusive End-to-End Email Signatures

MAILMAINT or a side meeting



### SEC Topics

1. Merkle Tree Certificates

A BoF with a narrow scope and a mailing list before BoF

2. PSI based on ECDH

Not clear now. More offline discussions.



The meeting minutes are here for your reference. Many thanks to our note taker Bron Gondwana!

https://datatracker.ietf.org/doc/minutes-123-dispatch-202507210730/



Thank you and Cheers!



Best Regards,

Shuping on behalf of the joint dispatch co-Chairs