[Technical Errata Reported] RFC9218 (7556)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 29 June 2023 22:38 UTC
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <wwwrun@rfcpa.amsl.com>) id 1qF0Hq-00GO1f-30 for ietf-http-wg@listhub.w3.org; Thu, 29 Jun 2023 22:38:50 +0000
Received: from [50.223.129.200] (helo=rfcpa.amsl.com) by mimas.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <wwwrun@rfcpa.amsl.com>) id 1qF0Ho-00H3PS-GK for ietf-http-wg@w3.org; Thu, 29 Jun 2023 22:38:49 +0000
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 6107B7FDE8; 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
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mzanaty@cisco.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230629223842.6107B7FDE8@rfcpa.amsl.com>
Date: Thu, 29 Jun 2023 15:38:42 -0700
Received-SPF: pass client-ip=50.223.129.200; envelope-from=wwwrun@rfcpa.amsl.com; helo=rfcpa.amsl.com
X-W3C-Hub-Spam-Status: No, score=-6.2
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1qF0Ho-00H3PS-GK 5f597197ae75d337a422ca6c33fe4b2b
X-Original-To: ietf-http-wg@w3.org
Subject: [Technical Errata Reported] RFC9218 (7556)
Archived-At: <https://www.w3.org/mid/20230629223842.6107B7FDE8@rfcpa.amsl.com>
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
- [Technical Errata Reported] RFC9218 (7556) RFC Errata System
- Re: [Technical Errata Reported] RFC9218 (7556) Lucas Pardue
- Re: [Technical Errata Reported] RFC9218 (7556) Mark Nottingham
- Re: [Technical Errata Reported] RFC9218 (7556) Lucas Pardue