RFC Errata
Found 2 records.
Status: Held for Document Update (2)
RFC 7541, "HPACK: Header Compression for HTTP/2", May 2015
Source of RFC: httpbis (wit)
Errata ID: 4574
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Christian Parpart
Date Reported: 2015-12-31
Held for Document Update by: Barry Leiba
Date Held: 2015-12-31
Section Appendix A. says:
Table 1 lists the predefined header fields that make up the static table and gives the index of each entry.
It should say:
Table 1 lists the predefined header fields that make up the static table and gives the index of each entry. This list of predefined header fields is NOT sorted.
Notes:
The list of header fields actually is sorted except for one field. The field with index 19 should be between the fields with index 14 and 15).
That is why it gives the false impression that an implementer may use binary search algorithm to look up for header fields (while encoding) in order to retrieve their index numbers.
I highly encourage to at either move that field up or at least clarify that this list (even though it looks sorted), it is not.
Errata ID: 5094
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Xue Fei
Date Reported: 2017-08-24
Held for Document Update by: Alexey Melnikov
Date Held: 2017-09-21
Section 5.1 says:
Integers are used to represent name indexes, header field indexes, or string lengths.
It should say:
Integers are used to represent name indexes, header field indexes, string lengths, or dynamic table size.
Notes:
Section 5.1 says, Integer encodings that exceed implementation limits — in value or octet length — MUST be treated as decoding errors.
Section 6.3 is using HPACK integer to represent value of dynamic table size. This size can be more larger than index or string length.
This change make user who implement integer encoding/decoding can figure out a proper integer value limit for each condition.