RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (1)

RFC 8392, "CBOR Web Token (CWT)", May 2018

Source of RFC: ace (sec)

Errata ID: 5710
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Felipe Gasper
Date Reported: 2019-04-29

Section 1.1 says:

In JSON, maps are called objects and only have one kind of map key: a
   string.  CBOR uses strings, negative integers, and unsigned integers
   as map keys.

It should say:

In JSON, maps are called objects and only have one kind of map key:
a string.  CBOR allows other data types, such as strings, negative
integers, and unsigned integers, as map keys.

Notes:

The text as it stands risks an interpretation that CBOR limits map keys to integers and strings; per discussion on the CBOR mailing list, this is not the case.

Status: Held for Document Update (1)

RFC 8392, "CBOR Web Token (CWT)", May 2018

Source of RFC: ace (sec)

Errata ID: 5852
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Laurence Lundblade
Date Reported: 2019-09-03
Held for Document Update by: Benjamin Kaduk
Date Held: 2019-09-05

Section A.3 says:

   d28443a10126a104524173796d6d657472696345434453413235365850a701756
   36f61703a2f2f61732e6578616d706c652e636f6d02656572696b77037818636f
   61703a2f2f6c696768742e6578616d706c652e636f6d041a5612aeb0051a5610d
   9f0061a5610d9f007420b7158405427c1ff28d23fbad1f29c4c7c6a555e601d6f
   a29f9179bc3d7438bacaca5acd08c8d4d4f96131680c429a01f85951ecee743a5
   2b9b63632c57209120e1c9e30

It should say:

   d28443a10126a104524173796d6d657472696345434453413235365850a70175
   636f61703a2f2f61732e6578616d706c652e636f6d02656572696b7703781863
   6f61703a2f2f6c696768742e6578616d706c652e636f6d041a5612aeb0051a56
   10d9f0061a5610d9f007420b7158405427c1ff28d23fbad1f29c4c7c6a555e60
   1d6fa29f9179bc3d7438bacaca5acd08c8d4d4f96131680c429a01f85951ecee
   743a52b9b63632c57209120e1c9e30

Notes:

The ASCII representation of binary bytes in Figure 10 is wrapped
on an odd number of ASCII characters. Since there are two ASCII
characters per binary bytes this splits the last byte over two
lines.

The CBOR playground (http://cbor.me) cannot handle this and
errors out.

This is slightly confusing for readers.

The actual bytes values are correct by all the checks I did.

Report New Errata