-
https://cbor.io/spec.html states that [RFC-8949](https://www.rfc-editor.org/rfc/rfc8949.html) is a new edition of RFC-7049 that describes the _same_ format, but with more explanation of topics that ha…
-
There is maybe some question/concern about number representation in SenML format.
The [RFC 8428 - Sensor Measurement Lists (SenML)](https://tools.ietf.org/html/rfc8428) says that [`value`](https:/…
-
I am successfully using openconnect-sso on Debian stable (10/buster) on multiple computers doing SSO. However, on Debian testing when I'm trying to connect the web browser window opens up but is empty…
-
It would be really handy to be able to know how to use and know which implementations support canonical encoding.
-
Hi,
Love your project, have been using it for a while. For a project, I spotted that this library also supports CBOR conversions.
But I couldn't find which RFC's are used, could you elaborate. I a…
-
Data validation should add this rule:
Reject CBOR primitives (major type 7) with additional info 24 if value (next byte) is < 32.
BTW, always verify with RFC 7049 because there's incorrect info ab…
-
```
9F 00 77 73 72 63 2F 73 74 6D 33 32 66 31 30 33 2F 73 79 73 74 65 6D 2F 70 69 FB 40 09 21 FB 54 2F E9 38 FF D2 1D
```
Parsing fails with
```
/tinycbor/src/cbor.h:626: CborError cbor_value_ge…
-
> Last very minor/cosmetic comment about this document as well to the oAuth terminology: using "refresh tokens" sounds weird to me, I would have preferred "permanent tokens" or "long-term tokens", but…
-
- [x] 1. -----
As noted by the shepherd, the document should point to 3205 in the abstract and in the introduction to mention it obsoletes it. From https://www.ietf.org/standards/ids/checklist/: "I…
-
Currently we use JSON SenML for device messaging. Using JSON for telemetry messages for embedded devices is heavy and unsuitable for several reasons:
- JSON encoding is not simple for embedded device…