Re: [6tisch-security] bar bof at IETF101, Re: enrollment roadmap

[peter van der Stok <[e-mail]>]

bar-boffin is a bit too much for me.
Prefer wine to beer, but can bring my own bottle (glass).

Is the suggestion to connect all this to IoT-T2TRG keying cycles work?

Peter

Michael Richardson schreef op 2018-01-26 23:16:
> Eliot Lear <[e-mail]> wrote:
>     >    That's a nice working doc.  I've been thinking along the same 
> lines.
>     > In particular, what I really like about your diagram, chaotic as 
> may
>     > make the world appear, is that while we have umpteen processes 
> for
>     > registration, at the end of the day, we can probably boil down to
>     > precisely two gazoutas, assuming I'm understanding OSCORE 
> correctly.
>     > That in itself is worth capturing.
> 
> Yes-ish.  Since the OSCORE vs DTLS is a session keying issue, that 
> difference
> is not seen beyond the JRC.  What is seen from pledge<--JRC-->MASA is 
> the
> voucher, which may be {CBOR,JSON} X {CMS-signed,COSE-signed}
> 
>     >    I do not yet believe we have all the necessary flows in focus. 
>  I
>     > have some thoughts on that I will share separately in due course, 
> but
>     > perhaps this is worth a bar bof at the IETF?
> 
> Yes. A real bar bof, where we just find chairs and beer and chat, or 
> one of
> these new-fangled IESG/AD mediated ones where we can get meetecho, but 
> no beer.
> 
> I'm trying to remember what the bar at the Metropole looked like, and 
> I'm not
> able to.  Maybe I never found it in the maze?
> 
> Or maybe we can just use that sign-up-for-this-room bit.
> I think that they are doing that again.  Yes, lets do that.
> I wonder what happens if we try to order pizza or schwarama in :-)
> 
> Would someone like to reply to this and coordinate a time among those 
> who
> want to participate?
> 
> Probably, at this point, the CC list is a bad idea since not everyone 
> is
> interested.  Noting the Reply-To set, which also makes this suitably 
> public.
> (I realize not everyone is on the 6tisch-security list, but you could 
> be)