RFC 7049, "Concise Binary Object Representation (CBOR)", October 2013
Note: This RFC has been obsoleted by RFC 8949Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app
Errata ID: 5917
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Faye Amacker
Date Reported: 2019-11-24
Held for Document Update by: Barry Leiba
Date Held: 2019-11-24
Section Appendix A says:
simple(24) | 0xf818
This example violates RFC 7049 section 2.3 Floating-Point Numbers and Values with No Content.
The incorrect example in Appendix A clearly uses a value <32 which is not allowed.
First, RFC 7049 section 2.3 has a table that shows:
| 24 | Simple value (value 32..255 in following byte) |
Next, RFC 7049 section 2.3 says:
As with all other major types, the 5-bit value 24 signifies a single-
byte extension: it is followed by an additional byte to represent the
simple value. (To minimize confusion, only the values 32 to 255 are
Wikipedia is also currently incorrect by having an interpretation based on the incorrect example from RFC 7049 Appendix A instead of the text from RFC 7049 Section 2.3.
Credits: This problem was first reported at https://github.com/fxamacker/cbor/issues/46