Re: [Secdispatch] Request for session at IETF 113

[Chris Inacio <[e-mail]>]

Henk,

Just a quick comment before the start of the actual SECDISPATCH session: signing an ML algorithm isn’t all that interesting, _maybe_ signing the model is a bit more interesting.  What’s really interesting is the data used to create the model, and that is where a lot of work in adversarial AI happens.  But they don’t call it big data for nothing, and I’m not sure the logistics of transparent (big) data, or the privacy impact of that are reasonable.

So maybe a different example may be appropriate.


--
Chris Inacio
[e-mail]

-----Original Message-----
From: Henk Birkholz <[e-mail]>
Date: March 9, 2022 at 5:40:11 PM
To: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject:  [Secdispatch] Request for session at IETF 113

> Hi secdispatch,
> (hi scitt),
>  
> emerging work on the topic of Supply Chain Integrity, Transparency,
> Trust has taken some shape recently.
>  
> The work combines existing IETF building blocks to facilitate useful
> Internet-based support of global supply chain interoperability.
>  
> Current contributions focus on the definition of Transparency Services
> based on Internet technology (using CBOR/CDDL/COSE) to achieve
> unambiguous, scaleable, and resilient integration with common devops and
> secops requirements.
>  
> I'd like to request secdispatch agenda time for two documents that are
> currently submitted:
> > https://datatracker.ietf.org/doc/draft-birkholz-scitt-architecture/
>  
> and
>  
> > https://datatracker.ietf.org/doc/draft-birkholz-scitt-receipts/
>  
> These two contributions are in -00 state. Yet, they already address
> essential requirements, such as, air-gapped validation when being
> offline, integration of remote attestation, efficient and crypto-agile
> signing prescriptions for out-of-the-box interoperability, and - in
> essence - long-long-term guarantees in support of various types of
> supply chains requirements.
>  
> We’d be happy to present this emerging work in secdispatch with the goal
> of discussing whether it might fit into the IETF space and how to
> progress it together.
>  
> Viele Grüße,
>  
> Henk
>  
> On 26.02.22 02:29, "IETF Secretariat" wrote:
> > Dear Mohit Sethi,
> >
> > The session(s) that you have requested have been scheduled.
> > Below is the scheduled session information followed by
> > the original request.
> >
> >
> > secdispatch Session 1 (2:00 requested)
> > Tuesday, 22 March 2022, Afternoon Session II 1430-1630
> > Room Name: Grand Park Hall 3 size: 250
> > ---------------------------------------------
> >
> >
> > iCalendar: https://datatracker.ietf.org/meeting/113/sessions/secdispatch.ics  
> >
> > Request Information:
> >
> >
> > ---------------------------------------------------------
> > Working Group Name: Security Dispatch
> > Area Name: Security Area
> > Session Requester: Mohit Sethi
> >
> >
> > Number of Sessions: 1
> > Length of Session(s):
> > Number of Attendees: 200
> > Conflicts to Avoid:
> >
> >
> >
> >
> > People who must be present:
> > Benjamin Kaduk
> > Kathleen Moriarty
> > Mohit Sethi
> > Paul Wouters
> > Richard Barnes
> > Roman Danyliw
> >
> > Resources Requested:
> >
> > Special Requests:
> > Please avoid conflict with any Security related BoF.
> > ---------------------------------------------------------
> >
> >
> > _______________________________________________
> > Secdispatch mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/secdispatch
>  
> _______________________________________________
> Secdispatch mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/secdispatch
>