- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Thu, 29 Jun 2023 15:38:42 -0700 (PDT)
- To: kazuhooku@gmail.com, lucaspardue.24.7@gmail.com, superuser@gmail.com, francesca.palombini@ericsson.com, mnot@mnot.net, tpauly@apple.com
- Cc: mzanaty@cisco.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been submitted for RFC9218, "Extensible Prioritization Scheme for HTTP". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7556 -------------------------------------- Type: Technical Reported by: Mo Zanaty <mzanaty@cisco.com> Section: 4.1 Original Text ------------- 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. Corrected Text -------------- 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. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC9218 (draft-ietf-httpbis-priority-12) -------------------------------------- Title : Extensible Prioritization Scheme for HTTP Publication Date : June 2022 Author(s) : K. Oku, L. Pardue Category : PROPOSED STANDARD Source : HTTP Area : Applications and Real-Time Stream : IETF Verifying Party : IESG
Received on Thursday, 29 June 2023 22:38:50 UTC