RFC 3738 on Wave and Equation Based Rate Control (WEBRC) Building Block
rfc-editor@rfc-editor.org Fri, 23 April 2004 19:00 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28403 for <ietf-announce-archive@odin.ietf.org>; Fri, 23 Apr 2004 15:00:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH5eg-00031X-Bf for ietf-announce-archive@odin.ietf.org; Fri, 23 Apr 2004 14:44:08 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NIi63f011589 for ietf-announce-archive@odin.ietf.org; Fri, 23 Apr 2004 14:44:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH5Ga-0000xB-1D; Fri, 23 Apr 2004 14:19:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH4yz-0003xH-P1 for ietf-announce@optimus.ietf.org; Fri, 23 Apr 2004 14:01:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23722 for <ietf-announce@ietf.org>; Fri, 23 Apr 2004 14:00:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BH4yx-0000u3-DB for ietf-announce@ietf.org; Fri, 23 Apr 2004 14:00:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BH4xB-0000cj-00 for ietf-announce@ietf.org; Fri, 23 Apr 2004 13:59:10 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BH4w5-00009p-00; Fri, 23 Apr 2004 13:58:01 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i3NHujN06267; Fri, 23 Apr 2004 10:56:45 -0700 (PDT)
Message-Id: <200404231756.i3NHujN06267@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3738 on Wave and Equation Based Rate Control (WEBRC) Building Block
Cc: rfc-editor@rfc-editor.org, rmt@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 23 Apr 2004 10:56:45 -0700
X-ISI-4-28-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
A new Request for Comments is now available in online RFC libraries. RFC 3738 Title: Wave and Equation Based Rate Control (WEBRC) Building Block Author(s): M. Luby, V. Goyal Status: Experimental Date: April 2004 Mailbox: luby@digitalfountain.com, v.goyal@ieee.org Pages: 32 Characters: 82584 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rmt-bb-webrc-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3738.txt This document specifies Wave and Equation Based Rate Control (WEBRC), which provides rate and congestion control for data delivery. WEBRC is specifically designed to support protocols using IP multicast. It provides multiple-rate, congestion-controlled delivery to receivers, i.e., different receivers joined to the same session may be receiving packets at different rates depending on the bandwidths of their individual connections to the sender and on competing traffic along these connections. WEBRC requires no feedback from receivers to the sender, i.e., it is a completely receiver-driven congestion control protocol. Thus, it is designed to scale to potentially massive numbers of receivers attached to a session from a single sender. Furthermore, because each individual receiver adjusts to the available bandwidth between the sender and that receiver, there is the potential to deliver data to each individual receiver at the fastest possible rate for that receiver, even in a highly heterogeneous network architecture, using a single sender. This document is a product of the Reliable Multicast Transport Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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.