From exim@www1.ietf.org Mon Jan 12 18:46:26 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29949 for ; Mon, 12 Jan 2004 18:46:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgBkt-0002II-O3 for rmt-archive@odin.ietf.org; Mon, 12 Jan 2004 18:46:00 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0CNjxOu008812 for rmt-archive@odin.ietf.org; Mon, 12 Jan 2004 18:45:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgBkt-0002I3-KX for rmt-web-archive@optimus.ietf.org; Mon, 12 Jan 2004 18:45:59 -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 SAA29908 for ; Mon, 12 Jan 2004 18:45:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgBkq-0001tv-00 for rmt-web-archive@ietf.org; Mon, 12 Jan 2004 18:45:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgBiw-0001oL-00 for rmt-web-archive@ietf.org; Mon, 12 Jan 2004 18:43:59 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AgBh2-0001iS-00 for rmt-web-archive@ietf.org; Mon, 12 Jan 2004 18:42:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgBh3-0002AJ-0R; Mon, 12 Jan 2004 18:42:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgBgz-0002A0-2n for rmt@optimus.ietf.org; Mon, 12 Jan 2004 18:41:57 -0500 Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29792 for ; Mon, 12 Jan 2004 18:41:52 -0500 (EST) Received: from apache by asgard.ietf.org with local (Exim 4.14) id 1AgBgJ-0000s7-JF; Mon, 12 Jan 2004 18:41:15 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce:; Cc: Internet Architecture Board , RFC Editor , Message-Id: Date: Mon, 12 Jan 2004 18:41:15 -0500 Subject: [Rmt] Document Action: 'Wave and Equation Based Rate Control building block' to Experimental RFC Sender: rmt-admin@ietf.org Errors-To: rmt-admin@ietf.org X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Reliable Multicast Transport List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 The IESG has approved the following document: - 'Wave and Equation Based Rate Control building block ' as an Experimental RFC This document is the product of the Reliable Multicast Transport Working Group. The IESG contact persons are Allison Mankin and Jon Peterson. _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Tue Jan 20 15:47:14 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21164 for ; Tue, 20 Jan 2004 15:47:14 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2lp-0000Lp-LI for rmt-archive@odin.ietf.org; Tue, 20 Jan 2004 15:46:45 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0KKkjMN001348 for rmt-archive@odin.ietf.org; Tue, 20 Jan 2004 15:46:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2lp-0000Lf-I4 for rmt-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 15:46:45 -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 PAA21125 for ; Tue, 20 Jan 2004 15:46:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aj2lo-0000gZ-00 for rmt-web-archive@ietf.org; Tue, 20 Jan 2004 15:46:44 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aj2kv-0000bo-00 for rmt-web-archive@ietf.org; Tue, 20 Jan 2004 15:45:50 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Aj2kE-0000Wz-00 for rmt-web-archive@ietf.org; Tue, 20 Jan 2004 15:45:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2kF-0008Dv-7j; Tue, 20 Jan 2004 15:45:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2k6-0008CI-TS for rmt@optimus.ietf.org; Tue, 20 Jan 2004 15:44:59 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20828; Tue, 20 Jan 2004 15:44:56 -0500 (EST) Message-Id: <200401202044.PAA20828@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: rmt@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 20 Jan 2004 15:44:55 -0500 Subject: [Rmt] I-D ACTION:draft-ietf-rmt-pi-norm-09.txt,.ps,.pdf Sender: rmt-admin@ietf.org Errors-To: rmt-admin@ietf.org X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Reliable Multicast Transport List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Reliable Multicast Transport Working Group of the IETF. Title : NACK-Oriented Reliable Multicast Protocol (NORM) Author(s) : B. Adamson, C. Bormann, M. Handley, J. Macker Filename : draft-ietf-rmt-pi-norm-09.txt,.ps,.pdf Pages : 69 Date : 2004-1-20 This document describes the messages and procedures of the Negative- acknowledgement (NACK) Oriented Reliable Multicast (NORM) protocol. This protocol is designed to provide end-to-end reliable transport of bulk data objects or streams over generic IP multicast routing and forwarding services. NORM uses a selective, negative acknowledgement mechanism for transport reliability and offers additional protocol mechanisms to conduct reliable multicast sessions with limited 'a priori' coordination among senders and receivers. A congestion control scheme is specified to allow the NORM protocol fairly share available network bandwidth with other transport protocols such as Transmission Control Protocol (TCP). It is capable of operating with both reciprocal multicast routing among senders and receivers and with asymmetric connectivity (possibly a unicast return path) from the senders to receivers. The protocol offers a number of features to allow different types of applications or possibly other higher level transport protocols to utilize its service in different ways. The protocol leverages the use of FEC-based repair and other IETF reliable multicast transport (RMT) building blocks in its design. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rmt-pi-norm-09.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rmt-pi-norm-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rmt-pi-norm-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-1-20142933.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rmt-pi-norm-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rmt-pi-norm-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-1-20142933.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt