RFC 3714 on IAB Concerns Regarding Congestion Control for Voice Traffic in the Internet
rfc-editor@rfc-editor.org Sat, 27 March 2004 01:29 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01254 for <ietf-announce-archive@odin.ietf.org>; Fri, 26 Mar 2004 20:29:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1B72UJ-00059K-O0 for ietf-announce-list@asgard.ietf.org; Fri, 26 Mar 2004 20:19:51 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1B72Ry-0004vv-Ga for all-ietf@asgard.ietf.org; Fri, 26 Mar 2004 20:17:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00460 for <all-ietf@ietf.org>; Fri, 26 Mar 2004 20:17:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B72Rw-0005tU-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:17:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B72R1-0005q5-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:16:27 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1B72Q2-0005mW-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:15:26 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i2R1FQk27068; Fri, 26 Mar 2004 17:15:26 -0800 (PST)
Message-Id: <200403270115.i2R1FQk27068@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3714 on IAB Concerns Regarding Congestion Control for Voice Traffic in the Internet
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 26 Mar 2004 17:15:26 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.2 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3714 Title: IAB Concerns Regarding Congestion Control for Voice Traffic in the Internet Author(s): S. Floyd, J. Kempf, Eds. Status: Informational Date: March 2004 Mailbox: iab@iab.org Pages: 32 Characters: 81368 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-congestion-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3714.txt This document discusses IAB concerns about effective end-to-end congestion control for best-effort voice traffic in the Internet. These concerns have to do with fairness, user quality, and with the dangers of congestion collapse. The concerns are particularly relevant in light of the absence of a widespread Quality of Service (QoS) deployment in the Internet, and the likelihood that this situation will not change much in the near term. This document is not making any recommendations about deployment paths for Voice over Internet Protocol (VoIP) in terms of QoS support, and is not claiming that best-effort service can be relied upon to give acceptable performance for VoIP. We are merely observing that voice traffic is occasionally deployed as best-effort traffic over some links in the Internet, that we expect this occasional deployment to continue, and that we have concerns about the lack of effective end-to-end congestion control for this best-effort voice traffic. This document is a product of the IAB. 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.