| CARVIEW |
Select Language
HTTP/2 200
date: Sun, 12 Oct 2025 06:54:25 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=l0aiv425p4o3qgvbrv94vnmde8; path=/
set-cookie: __cf_bm=B.vOFRPCjkqsJxkSbLzYnGPR2KO8iCaIjB559f3MZKg-1760252065-1.0.1.1-QYEGgcnnKfPutCxqGEWCp5hGiVrWQwaO0WozK4IgRy52jS9uubbvSHdZ0AxRKHSgBEmjxnnLwy647er7yfr3H2NJp5X9bwyTb57XlU9WPUk; path=/; expires=Sun, 12-Oct-25 07:24:25 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 98d4af887a31a9b7-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
Found 1 record.
Status: Reported (1)
RFC 8949, "Concise Binary Object Representation (CBOR)", December 2020
Source of RFC: cbor (art)
Errata ID: 8589
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Joe Hildebrand
Date Reported: 2025-10-01
Section 5.6.1 says:
...for the purpose of map key equivalence, NaN values are equivalent if they have the same significand after zero-extending both significands at the right to 64 bits.
It should say:
...for the purpose of map key equivalence, NaN values are equivalent if they have the same sign bit and significand after zero-extending both significands at the right to 64 bits, and ensuring that the exponent bits are all ones in both values.
Notes:
The sign bit is significant to the distinctness check.
Without the exponent bits being all ones, the zero-extension will not be a NaN.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us