RFC 8802: The Quality for Service (Q4S) Protocol
In plain English — editorial summary, not part of the RFC
This memo describes an application-level protocol for the communication of end-to-end QoS compliance information based on the HyperText Transfer Protocol (HTTP) and the Session Description Protocol (SDP). The Quality for Service (Q4S) protocol provides a mechanism to negotiate and monitor latency, jitter, bandwidth, and packet loss, and to alert whenever one of the negotiated conditions is violated. Implementation details on the actions to be triggered upon reception/detection of QoS alerts exchanged by the protocol are out of scope of this document; it is either application dependent (e.g., act to increase quality or reduce bit-rate) or network dependent (e.g., change connection's quality profile). This protocol specification is the product of research conducted over a number of years; it is presented here as a permanent record and to offer a foundation for future similar work. It does not represent a standard protocol and does not have IETF consensus.
Document record
- Document ID
- RFC8802
- Published
- July 2020
- Authors
- J.J. Aranda; M. Cortes; J. Salvachúa; M. Narganes; I. Martínez-Sarriegui
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 73
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9957The DOCSIS Queue Protection Algorithm to Preserve Low LatencyCurrent
May 2026
- RFC 9330Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: ArchitectureCurrent
January 2023
- RFC 9331The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9332Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)Current
January 2023
- RFC 9506Explicit Host-to-Network Flow Measurements TechniquesCurrent
October 2023
- RFC 8034Active Queue Management (AQM) Based on Proportional Integral Controller Enhanced (PIE) for Data-Over-Cable Service Interface Specifications (DOCSIS) Cable ModemsCurrent
February 2017
- RFC 9693Benchmarking Methodology for Stateful NATxy GatewaysCurrent
January 2025
- RFC 7901CHAIN Query Requests in DNSCurrent
June 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?