Dear all,
At the virtual IETF 108 meeting, we will have a 50 minute session on
Friday, July 31, between 13:00 - 13:50 UTC.
Please send Joe and I (emu-cha...@ietf.org) requests for presentation
slots.
Don't forget to include the title of your presentation, related drafts,
and the approximate a
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
Rene, Russ, and I had an offline email exchange about this issue. I think we
are now in agreement that the public key for the NIST P-256 curve requires at
least 33 bytes (in the compressed format).
Thus, we should update the draft to reflect the correct key size. Adding a
reference to
https://
Arghh. I feel very protected with unreadable URLs of fireeye. Fixed pointer to
the reference:
https://www.secg.org/SEC2-Ver-1.0.pdf
The relevant section is 2.7.1.
--Mohit
On 7/9/20 9:45 AM, Mohit Sethi M wrote:
Rene, Russ, and I had an offline email exchange about this issue. I think we
are
