Hi Toerless, all, I won't be joining the IETF meeting this time, correct.
Main open issues to discuss for Constrained BRSKI are * Is application/voucher-cose+cbor a correct name? https://github.com/anima-wg/constrained-voucher/issues/264 -> proposal is to change name to application/voucher+cose and register '+cose" as a structured syntax suffix. A request has been informally approved by mediaman WG; and it was decided to include the formal request in the draft since that's the best procedure for it. * Proposed simplification and streamlining of Constrained BRSKI https://github.com/anima-wg/constrained-voucher/issues/269 -> proposal is to simplify and streamline the draft per the PR linked to this issue. It separates better the default (basics) needed and optional Pledge features (like discovering multiple protocols/formats/etc and the RPK variant) Maybe Michael is available to lead the discussion ... ? Esko -----Original Message----- From: Toerless Eckert <t...@cs.fau.de> Sent: Wednesday, July 19, 2023 03:08 To: Esko Dijk <esko.d...@iotconsultancy.nl> Cc: anima@ietf.org Subject: Re: [Anima] New Version Notification for draft-ietf-anima-constrained-voucher-21.txt Thanks, Esko! It looks as if you are not registered for IETF117... I think to remember something about PTO. Are the specific issues you would like to be discussed (even in your absence) during the WG meeting, maybe one of the co-authors could lead ? Cheers Toerless On Fri, Jul 07, 2023 at 08:42:34AM +0000, Esko Dijk wrote: > Hi all, > > This latest version of draft-ietf-anima-constrained-voucher fixes a couple of > minor issues and has editorial improvements. > There are some open work items that will have a larger impact on the text; > but these are not concluded yet so will be integrated into a future version. > (Overview here: https://github.com/anima-wg/constrained-voucher/issues) > > Full details of the commits and PRs applied can be found here: > https://github.com/anima-wg/constrained-voucher/commits/master > > best regards > Esko > > -----Original Message----- > From: internet-dra...@ietf.org <internet-dra...@ietf.org> > Sent: Friday, July 7, 2023 10:36 > To: Esko Dijk <esko.d...@iotconsultancy.nl>; Michael Richardson > <mcr+i...@sandelman.ca>; Panos Kampanakis <pkamp...@cisco.com>; Peter van der > Stok <stokc...@bbhmail.nl> > Subject: New Version Notification for > draft-ietf-anima-constrained-voucher-21.txt > > > A new version of I-D, draft-ietf-anima-constrained-voucher-21.txt > has been successfully submitted by Esko Dijk and posted to the > IETF repository. > > Name: draft-ietf-anima-constrained-voucher > Revision: 21 > Title: Constrained Bootstrapping Remote Secure Key > Infrastructure (BRSKI) > Document date: 2023-07-07 > Group: anima > Pages: 84 > URL: > https://www.ietf.org/archive/id/draft-ietf-anima-constrained-voucher-21.txt > Status: > https://datatracker.ietf.org/doc/draft-ietf-anima-constrained-voucher/ > Html: > https://www.ietf.org/archive/id/draft-ietf-anima-constrained-voucher-21.html > Htmlized: > https://datatracker.ietf.org/doc/html/draft-ietf-anima-constrained-voucher > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-anima-constrained-voucher-21 > > Abstract: > This document defines the Constrained Bootstrapping Remote Secure Key > Infrastructure (Constrained BRSKI) protocol, which provides a > solution for secure zero-touch bootstrapping of resource-constrained > (IoT) devices into the network of a domain owner. This protocol is > designed for constrained networks, which may have limited data > throughput or may experience frequent packet loss. Constrained BRSKI > is a variant of the BRSKI protocol, which uses an artifact signed by > the device manufacturer called the "voucher" which enables a new > device and the owner's network to mutually authenticate. While the > BRSKI voucher is typically encoded in JSON, Constrained BRSKI uses a > compact CBOR-encoded voucher. The BRSKI voucher is extended with new > data types that allow for smaller voucher sizes. The Enrollment over > Secure Transport (EST) protocol, used in BRSKI, is replaced with EST- > over-CoAPS; and HTTPS used in BRSKI is replaced with CoAPS. This > document Updates RFC 8366 and RFC 8995. > > > > > > The IETF Secretariat > > -- --- t...@cs.fau.de _______________________________________________ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
