-
- [x] Sec. 2: some terms are capitalized, some aren't.
- [x] NSPE: I would add "applications", e.g. operating systems, applications and general hardware.
- [x] Add the term "target environment".
- …
-
EDN implementations use the wide-spread convention to use NR2/NR3 syntax to notate floating point values and only NR1 to notate integer values; RFC 8949 uses this convention in Appendix A without expl…
cabo updated
11 months ago
-
Hi. I need help with encoding bytes as rfc8949.
For example UT with expects value `1903e8` while default HEXLOWER returns `1900000000000003e8`.
Would appreciate any help.
-
In some tests with CBOR I have noticed that reflect-cpp adds a significant overhead over tinycbor. This makes it less appealing to use this library in performance critical environments.
E.g., a min…
-
During testing of the [D-CBOR](https://github.com/cyberphone/D-CBOR) concept I ported a Java encoder to C. Just for fun I adjusted it a bit to test with the QCBOR test suite. However, "DoubleAsSmall…
-
CBOR is a modern alternative to earlier data formats such as JSON, GOB, MessagePack, etc. Some comparisons between CBOR and other binary formats were published by IETF:
- RFC 8949 CBOR, Appendix E: …
-
## The dependency [next](https://github.com/zeit/next.js) was updated from `9.0.5` to `9.0.6`.
🚨 [View failing branch](https://github.com/skdigital/tec-2000-nextjs/compare/master...skdigital:greenke…
-
Hello!
I am new to cbor and recently looking into [`cbor`](https://pypi.org/project/cbor/) and `cbor2`, and having a question about what benefits `cbor2` brings that `cbor` does not have?
I exp…
-
See https://mailarchive.ietf.org/arch/msg/rats/Bmlxnu0GmnRMsP6WEq3CBjLVm0k/
-
[General]
* Replace RFC 7049 with RFC 8949
* Replace RFC 8152 with RFC 9052 and RFC 9053
* When mentioning DTLS and referring to RFC 6347, refer also to RFC 9147
* As expected, the draft f…