RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Rejected (1)

RFC 9218, "Extensible Prioritization Scheme for HTTP", June 2022

Source of RFC: httpbis (wit)

Errata ID: 7556
Status: Rejected
Type: Technical
Publication Format(s) : TEXT, PDF, HTML

Reported By: Mo Zanaty
Date Reported: 2023-06-29
Rejected by: Murray Kucherawy
Date Rejected: 2023-07-17

Section 4.1 says:

The urgency (u) parameter value is Integer (see Section 3.3.1 of
[STRUCTURED-FIELDS]), between 0 and 7 inclusive, in descending order
of priority.

It should say:

The urgency (u) parameter value is Integer (see Section 3.3.1 of
[STRUCTURED-FIELDS]), between 0 and 7 inclusive, in ASCENDING order
of priority.

Notes:

The very next paragraph indicates ASCENDING order of priority:
"The smaller the value, the higher the precedence."
Minor nit: It is confusing and unnecessary to use "precedence" and "urgency" as aliases for "priority". Readers can be misled to think these are intended to be distinct properties rather than aliases.

[AD response] The operative phrase to me is "between 0 and 7 inclusive, in descending order of priority". I read that as a set of ordered values from 0 to 7 where the first value has the highest priority, the second value is down a notch, etc., hence, descending. The later phrase "The smaller the value, the higher the precedence" affirms this interpretation.
--VERIFIER NOTES--

Report New Errata



Advanced Search