-
Hi,
The BCR-2020-005 paper says (about CBOR byte strings)
"If the encoded byte string has 65536..2^32-1 bytes, it is preceded by (0x60, b1, b2, b3, b4) where b(n) is the big-endian four byte len…
-
spec-data/readonly/biblio/biblio-rf.data does not have an entry for eg RFC8949, yet the latter exists in https://www.specref.org/?q=8949
-
I think there is difference between undefined in javascript and undefined type in cbor (https://tools.ietf.org/html/rfc7049#section-3.8). In cbor it means rather item with encoding problem, but in jav…
-
This is current draft.
```
# Ciphersuites {#ciphersuite}
A ciphersuite consists of an AEAD algorithm, an HMAC algorithm, and a signature
algorithm.
Each ciphersuite is identified with an intege…
-
The CBOR Spec (RFC7049) defines Major type 2 as a byte string. This is different than Major type 4, and array of data items.
I have an application where the client need a string transported as a …
-
As per the RFC-7049, it is possible to use the Major Type 7 (0b111) to pass values with no content :
https://tools.ietf.org/html/rfc7049#section-2.3
However, passing one of these value in a CBOR …
-
I suspect that many of us will generate source code from the JSON schema. In places where a date and time is represented the is expressed as follows in the JSON schema:
```
"dts": …
-
I finally found some time to analyze the canonicalization algorithm in the DagCBOR section. That section currently states:
> DagCBOR requires that there exist a single way of encoding any given obj…
-
Hi Leshan Team
I'm trying out the AVSystem's Coiote LwM2M stack (both bootstrap and device management) using Leshan client demo.
When I connect the client to the bootstrap server, I get this error…
-
I have major concerns regarding the direction of this did spec registries and how there is an expectation that someone will create the CBOR equivalent of what is in essence new cryptographic methods a…