The point that came up in the discussion is how deterministic encoding would
work with the extension points.
I said that it is easy to isolate extension points via encapsulation of an
encoded CBOR data item in a byte string — that causes a generic decoder to hand
up that byte string (which can
On 2020-07-31, at 09:25, Aura Tuomas wrote:
>
> That is, my biggest concern with both JSON and CBOR is (4) the lack of
> canonical binary serialization. IN EAP-NOOB, we need to receive a serialized
> data message, extract some fields and subtrees, compose an HMAC input out of
> these parts of
; iot-director...@ietf.org
Subject: Re: [Emu] [Iot-directorate] Iotdir early review of
draft-ietf-emu-eap-noob-01
Importance: High
Hi Mohit,
> On 2020-07-11, at 15:27, Mohit Sethi M
> wrote:
>
> Hi Michael,
>
> Thanks for the input. This is indeed something we sho
On Sat, Jul 11, 2020 at 03:40:25PM +0200, Carsten Bormann wrote:
> Hi Mohit,
>
>
> > On 2020-07-11, at 15:27, Mohit Sethi M
> > wrote:
> >
> > EAP-NOOB also relies on the JWK specification for encoding public keys.
> > While CBOR equivalent is defined in RFC 8152, it is a rather large documen
Thanks Carsten. This is very valuable input for the working group before
it makes a critical decision.
--Mohit
On 7/11/20 4:40 PM, Carsten Bormann wrote:
> Hi Mohit,
>
>
>> On 2020-07-11, at 15:27, Mohit Sethi M
>> wrote:
>>
>> Hi Michael,
>>
>> Thanks for the input. This is indeed something w
Hi Mohit,
> On 2020-07-11, at 15:27, Mohit Sethi M
> wrote:
>
> Hi Michael,
>
> Thanks for the input. This is indeed something we should discuss at the
> upcoming virtual EMU meeting.
>
> Some colleagues (Ingles Sanchez et al.) have also investigated and documented
> the savings that migh
Hi Michael,
Thanks for the input. This is indeed something we should discuss at the
upcoming virtual EMU meeting.
Some colleagues (Ingles Sanchez et al.) have also investigated and documented
the savings that might result from the use of CBOR in EAP-NOOB:
https://hal.archives-ouvertes.fr/hal-0
Speaking as a WG participant.
Dave Thaler via Datatracker wrote:
> 3) Section 3.3.2 says:
>> The in-band messages are formatted as JSON objects [RFC8259]
> So this limits applicability to constrained IoT devices, since JSON can be
> verbose compared to, say, CBOR, and if the IoT
