RFC 9218 on Extensible Prioritization Scheme for HTTP
rfc-editor@rfc-editor.org Mon, 06 June 2022 20:09 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 998A4C15AAD1 for <ietf-announce@ietfa.amsl.com>; Mon, 6 Jun 2022 13:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level:
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1zDlbM5KUVQC for <ietf-announce@ietfa.amsl.com>; Mon, 6 Jun 2022 13:09:06 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55747C15AAD4 for <ietf-announce@ietf.org>; Mon, 6 Jun 2022 13:06:53 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3AB1E32F68; Mon, 6 Jun 2022 13:06:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9218 on Extensible Prioritization Scheme for HTTP
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ietf-http-wg@w3.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220606200653.3AB1E32F68@rfcpa.amsl.com>
Date: Mon, 06 Jun 2022 13:06:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/7B85lUhRdzgXeP7x6DPJYB6yD00>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2022 20:09:06 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9218
Title: Extensible Prioritization Scheme for HTTP
Author: K. Oku,
L. Pardue
Status: Standards Track
Stream: IETF
Date: June 2022
Mailbox: kazuhooku@gmail.com,
lucaspardue.24.7@gmail.com
Pages: 21
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-httpbis-priority-12.txt
URL: https://www.rfc-editor.org/info/rfc9218
DOI: 10.17487/RFC9218
This document describes a scheme that allows an HTTP client to
communicate its preferences for how the upstream server prioritizes
responses to its requests, and also allows a server to hint to a
downstream intermediary how its responses should be prioritized when
they are forwarded. This document defines the Priority header field
for communicating the initial priority in an HTTP version-independent
manner, as well as HTTP/2 and HTTP/3 frames for reprioritizing
responses. These share a common format structure that is designed to
provide future extensibility.
This document is a product of the HTTP Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC