RFC 8802 on The Quality for Service (Q4S) Protocol
rfc-editor@rfc-editor.org Wed, 29 July 2020 13:51 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 874BC3A0B3A for <ietf-announce@ietfa.amsl.com>; Wed, 29 Jul 2020 06:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.473
X-Spam-Level:
X-Spam-Status: No, score=-1.473 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.427, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZLH_yAc8mawj for <ietf-announce@ietfa.amsl.com>; Wed, 29 Jul 2020 06:51:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44F963A0B33 for <ietf-announce@ietf.org>; Wed, 29 Jul 2020 06:51:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5A405F4071D; Wed, 29 Jul 2020 06:51:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8802 on The Quality for Service (Q4S) Protocol
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200729135105.5A405F4071D@rfc-editor.org>
Date: Wed, 29 Jul 2020 06:51:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/3VhHfboo1t35XtdOm4l7Q7S8AOs>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 29 Jul 2020 13:51:34 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8802 Title: The Quality for Service (Q4S) Protocol Author: J.J. Aranda, M. Cortes, J. SalvachĂșa, M. Narganes, I. MartĂnez-Sarriegui Status: Informational Stream: Independent Date: July 2020 Mailbox: jose_javier.garcia_aranda@nokia.com, monica.cortes_sack@nokia.com, Joaquin.salvachua@upm.es, maribel.narganes@tecnalia.com, inaki.martinez@optivamedia.com Pages: 73 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-aranda-dispatch-q4s-10.txt URL: https://www.rfc-editor.org/info/rfc8802 DOI: 10.17487/RFC8802 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. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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