RFC Errata
Found 2 records.
Status: Verified (1)
RFC 8536, "The Time Zone Information Format (TZif)", February 2019
Source of RFC: IETF - NON WORKING GROUP
Errata ID: 6435
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Julian Reschke
Date Reported: 2021-02-20
Verifier Name: Barry Leiba
Date Verified: 2021-02-21
Section 5.2 says:
>> Response << HTTP/1.1 200 OK Date: Fri, 01 Jun 2018 14:52:23 GMT Content-Type: application/json; charset="utf-8" Content-Length: xxxx
It should say:
>> Response << HTTP/1.1 200 OK Date: Fri, 01 Jun 2018 14:52:23 GMT Content-Type: application/json Content-Length: xxxx
Notes:
There is no charset parameter on application/json. See https://tools.ietf.org/html/rfc8259#section-11 (last sentence).
Status: Reported (1)
RFC 8536, "The Time Zone Information Format (TZif)", February 2019
Source of RFC: IETF - NON WORKING GROUP
Errata ID: 6757
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Carl Gay
Date Reported: 2021-11-28
Section B.3 says:
| 064 | 00 00 00 03 | isutccnt | 1 | | 068 | 00 00 00 03 | isstdcnt | 1 | | 072 | 00 00 00 00 | isleapcnt | 0 | | 076 | 00 00 00 03 | timecnt | 1 | | 080 | 00 00 00 03 | typecnt | 1 | | 084 | 00 00 00 08 | charcnt | 4 |
It should say:
| 064 | 00 00 00 01 | isutccnt | 1 | | 068 | 00 00 00 01 | isstdcnt | 1 | | 072 | 00 00 00 00 | isleapcnt | 0 | | 076 | 00 00 00 01 | timecnt | 1 | | 080 | 00 00 00 01 | typecnt | 1 | | 084 | 00 00 00 04 | charcnt | 4 |
Notes:
The numbers 1 and 4 are incorrectly encoded as big-endian 32-bit integer values. I'm guessing that the example originally used more data and was then trimmed down (from 3 to 1 for isutccnt, isstdcnt, timecnt, and typecnt, and from 8 to 4 for charcnt) but the integer encodings were never updated.