RFC 9218 - Extensible Prioritization Scheme for HTTP
Publication Date: June 2022
Status: Standards Track
Authors: K. Oku (Fastly), L. Pardue (Cloudflare)
Abstract
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.
Table of Contents
- 1. Introduction
- 1.1 Notational Conventions
- 2. Motivation for Replacing RFC 7540 Stream Priorities
- 2.1 Disabling RFC 7540 Stream Priorities
- 2.1.1 Advice when Using Extensible Priorities as the Alternative
- 3. Applicability of the Extensible Priority Scheme
- 4. Priority Parameters
- 4.1 Urgency
- 4.2 Incremental
- 4.3 Defining New Priority Parameters
- 4.3.1 Registration
- 5. The Priority HTTP Header Field
- 6. Reprioritization
- 7. The PRIORITY_UPDATE Frame
- 7.1 HTTP/2 PRIORITY_UPDATE Frame
- 7.2 HTTP/3 PRIORITY_UPDATE Frame
- 8. Merging Client- and Server-Driven Priority Parameters
- 9. Client Scheduling
- 10. Server Scheduling
- 10.1 Intermediaries with Multiple Backend Connections
- 11. Scheduling and the CONNECT Method
- 12. Retransmission Scheduling
- 13. Fairness
- 13.1 Coalescing Intermediaries
- 13.2 HTTP/1.x Back Ends
- 13.3 Intentional Introduction of Unfairness
- 14. Why Use an End-to-End Header Field?
- 15. Security Considerations
- 16. IANA Considerations
- 17. References
- 17.1 Normative References
- 17.2 Informative References
- Acknowledgements
- Authors' Addresses
Related Resources
- Official Text: ````https://www.rfc-editor.org/rfc/rfc9218.txt\````
- Official Page: ````https://datatracker.ietf.org/doc/html/rfc9218\````
- Errata: ````https://www.rfc-editor.org/errata_search.php?rfc=9218\````