From exim@www1.ietf.org Tue Jul 1 15:41:49 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14132 for ; Tue, 1 Jul 2003 15:41:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XR0C-0004aB-WD for rmt-archive@odin.ietf.org; Tue, 01 Jul 2003 15:41:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h61JfK1V017611 for rmt-archive@odin.ietf.org; Tue, 1 Jul 2003 15:41:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XR0C-0004Zy-TO for rmt-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 15:41:20 -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 PAA14100 for ; Tue, 1 Jul 2003 15:41:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XR0B-0007gz-00 for rmt-web-archive@ietf.org; Tue, 01 Jul 2003 15:41:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XR0A-0007gv-00 for rmt-web-archive@ietf.org; Tue, 01 Jul 2003 15:41:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQzu-0004TD-LH; Tue, 01 Jul 2003 15:41:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XQzh-0004SF-S6 for rmt@optimus.ietf.org; Tue, 01 Jul 2003 15:40:49 -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 PAA14077 for ; Tue, 1 Jul 2003 15:40:47 -0400 (EDT) From: floyd@aciri.org Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XQzg-0007gX-00 for rmt@ietf.org; Tue, 01 Jul 2003 15:40:48 -0400 Received: from mta1.lbl.gov ([128.3.41.24]) by ietf-mx with esmtp (Exim 4.12) id 19XQzf-0007gI-00 for rmt@ietf.org; Tue, 01 Jul 2003 15:40:47 -0400 Received: from mta1.lbl.gov (localhost [127.0.0.1]) by mta1.lbl.gov (8.12.9/8.12.9) with ESMTP id h61JeEIq023539 for ; Tue, 1 Jul 2003 12:40:14 -0700 (PDT) Received: from MSTAUFFER_LT (mail.atheros.com [65.212.155.130]) by mta1.lbl.gov (8.12.9/8.12.9) with ESMTP id h61JeDAs023512 for ; Tue, 1 Jul 2003 12:40:13 -0700 (PDT) Message-Id: <200307011940.h61JeDAs023512@mta1.lbl.gov> To: Date: Tue, 1 Jul 2003 12:40:12 --0700 Importance: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MSMail-Priority: Normal X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="CSmtpMsgPart123X456_000_00D33B23" X-Brightmail-Tracker: AAAAAQBXScI= Subject: [Rmt] [SUSPECTED SPAM] Re: Movie 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: , This is a multipart message in MIME format --CSmtpMsgPart123X456_000_00D33B23 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ------ NOTICE ------------ NOTICE ------------ NOTICE ------ 1. The LBNL VirusWall REMOVED a virus from this message. The message is now safe to open. 2. If you need help or have questions, contact the Help Desk at 510-486-HELP. 3. For information, please visit: http://www.lbl.gov/ITSD/Security/vulnerabilities/virus.html ------------------------------------------------------------ Found virus WORM_SOBIG.E in file details.pif (in your_details.zip) The uncleanable file your_details.zip is moved to /etc/iscan/virus_quarantine/virWJEPWayTK. --------------------------------------------------------- --CSmtpMsgPart123X456_000_00D33B23 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Please see the attached zip file for details. --CSmtpMsgPart123X456_000_00D33B23 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ------ NOTICE ------------ NOTICE ------------ NOTICE ------ 1. The LBNL VirusWall REMOVED a virus from this message. The message is now safe to open. 2. If you need help or have questions, contact the Help Desk at 510-486-HELP. 3. For information, please visit: http://www.lbl.gov/ITSD/Security/vulnerabilities/virus.html ------------------------------------------------------------ your_details.zip is removed from here because it contains a virus. --------------------------------------------------------- --CSmtpMsgPart123X456_000_00D33B23-- _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Wed Jul 2 06:57:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03310 for ; Wed, 2 Jul 2003 06:57:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfIP-00030i-DE for rmt-archive@odin.ietf.org; Wed, 02 Jul 2003 06:57:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62Av5Ch011568 for rmt-archive@odin.ietf.org; Wed, 2 Jul 2003 06:57:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfIP-00030V-AF for rmt-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 06:57:05 -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 GAA03130 for ; Wed, 2 Jul 2003 06:57:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XfIL-0001An-00 for rmt-web-archive@ietf.org; Wed, 02 Jul 2003 06:57:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XfIK-0001Ak-00 for rmt-web-archive@ietf.org; Wed, 02 Jul 2003 06:57:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfIN-0002wx-3D; Wed, 02 Jul 2003 06:57:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfI5-0002uc-DR for rmt@optimus.ietf.org; Wed, 02 Jul 2003 06:56:45 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03007; Wed, 2 Jul 2003 06:56:42 -0400 (EDT) Message-Id: <200307021056.GAA03007@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: Wed, 02 Jul 2003 06:56:41 -0400 Subject: [Rmt] I-D ACTION:draft-ietf-rmt-bb-pgmcc-02.txt,.ps 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: , --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 : PGMCC single rate multicast congestion control: Protocol Specification Author(s) : L. Rizzo, G. Iannaccone, L. Vicisano, M. Handley Filename : draft-ietf-rmt-bb-pgmcc-02.txt,.ps Pages : 22 Date : 2003-7-1 This document describes PGMCC, a single rate multicast congestion control scheme which is TCP-friendly and achieves scalability, stability and fast response to variations in network conditions. PGMCC is suitable for both non-reliable and reliable data transfers. It is mainly designed for NAK- based multicast protocols, and uses a window-based, TCP-like control loop using positive ACKs between one representative of the receiver group (the ACKER) and the sender. The ACKER is selected dynamically and may change over time. PGMCC is made of two components: a window-based control loop, which closely mimics TCP behaviour, and a fast and low- overhead procedure to select (and track changes of) the ACKER. The scheme is robust to measurement errors, and supports fast response to changes in the receiver set and/or network conditions. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-pgmcc-02.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-bb-pgmcc-02.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-bb-pgmcc-02.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: <2003-7-1134848.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rmt-bb-pgmcc-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rmt-bb-pgmcc-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-1134848.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Wed Jul 23 15:16:46 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25695 for ; Wed, 23 Jul 2003 15:16:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fP62-0001SK-K4 for rmt-archive@odin.ietf.org; Wed, 23 Jul 2003 15:16:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NJGIAe005592 for rmt-archive@odin.ietf.org; Wed, 23 Jul 2003 15:16:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fP61-0001Rq-2c for rmt-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 15:16:17 -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 PAA25570 for ; Wed, 23 Jul 2003 15:16:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fP5z-00076K-00 for rmt-web-archive@ietf.org; Wed, 23 Jul 2003 15:16:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fP5t-000760-00 for rmt-web-archive@ietf.org; Wed, 23 Jul 2003 15:16:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fP5m-0001JR-Es; Wed, 23 Jul 2003 15:16:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fP5Z-0001IN-GF for rmt@optimus.ietf.org; Wed, 23 Jul 2003 15:15:49 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25492; Wed, 23 Jul 2003 15:15:46 -0400 (EDT) Message-Id: <200307231915.PAA25492@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: Wed, 23 Jul 2003 15:15:46 -0400 Subject: [Rmt] I-D ACTION:draft-ietf-rmt-bb-tfmcc-02.txt,.ps 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: , --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 : TCP-Friendly Multicast Congestion Control (TFMCC):Protocol Specification Author(s) : J. Widmer, M. Handley Filename : draft-ietf-rmt-bb-tfmcc-02.txt,.ps Pages : 30 Date : 2003-7-23 This document specifies TCP-Friendly Multicast Congestion Control (TFMCC). TFMCC is a congestion control mechanism for multicast transmissions in a best-effort Internet environment. It is a single-rate congestion control scheme, where the sending rate is adapted to the receiver experiencing the worst network conditions. TFMCC is reasonably fair when competing for bandwidth with TCP flows and has a relatively low variation of throughput over time, making it suitable for applications such as streaming media where a relatively smooth sending rate is of importance. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-tfmcc-02.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-bb-tfmcc-02.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-bb-tfmcc-02.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: <2003-7-23151231.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rmt-bb-tfmcc-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rmt-bb-tfmcc-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-23151231.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Fri Jul 25 07:49:20 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02550 for ; Fri, 25 Jul 2003 07:49:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g149-00088S-72 for rmt-archive@odin.ietf.org; Fri, 25 Jul 2003 07:48:53 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6PBmrWE031268 for rmt-archive@odin.ietf.org; Fri, 25 Jul 2003 07:48:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g149-00088F-2o for rmt-web-archive@optimus.ietf.org; Fri, 25 Jul 2003 07:48:53 -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 HAA02544 for ; Fri, 25 Jul 2003 07:48:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g148-0007SR-00 for rmt-web-archive@ietf.org; Fri, 25 Jul 2003 07:48:52 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19g142-0007SL-00 for rmt-web-archive@ietf.org; Fri, 25 Jul 2003 07:48:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g13J-00082K-9A; Fri, 25 Jul 2003 07:48:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g12a-00081z-Sl for rmt@optimus.ietf.org; Fri, 25 Jul 2003 07:47:16 -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 HAA02529 for ; Fri, 25 Jul 2003 07:47:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g12a-0007Rz-00 for rmt@ietf.org; Fri, 25 Jul 2003 07:47:16 -0400 Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx with esmtp (Exim 4.12) id 19g12P-0007Rt-00 for rmt@ietf.org; Fri, 25 Jul 2003 07:47:05 -0400 Received: from FTRDMEL1.rd.francetelecom.fr ([10.193.117.152]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 25 Jul 2003 13:46:05 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C352A2.4645DF32" Date: Fri, 25 Jul 2003 13:45:41 +0200 Message-ID: Thread-Topic: PGMCC window manager computation Thread-Index: AcNSokY6T65qRL0OT02p/0amDtBkfA== From: =?iso-8859-1?Q?BABONNEAU_G=E9rard_FTRD/DMI/REN?= To: X-OriginalArrivalTime: 25 Jul 2003 11:46:05.0636 (UTC) FILETIME=[54BD0840:01C352A2] Subject: [Rmt] PGMCC window manager computation 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: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C352A2.4645DF32 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, =20 Algorithm in section 2.2 seems ambiguous. For "ACK RECEPTION, LOSS DETECTED", order is important: if I suppose = there are only one T variable and one W variable: =20 * If I compute first T =3D T - W/2, I use the previous value of W * If I compute T after W, I use the new value of W =20 The same problem exist also in the token computation without losses. =20 Is there something missing in the draft, or do I misunderstand? =20 Regards, G=E9rard BABONNEAU=20 france telecom R&D=20 4, rue du Clos Courtel - BP 59 - 35512 Cesson Sevign=E9 Cedex=20 Tel : +33 2 99 12 40 08 - Fax : +33 2 99 12 40 98=20 e-mail : gerard.babonneau@francetelecom.com=20 =20 ------_=_NextPart_001_01C352A2.4645DF32 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
Algorithm in section=20 2.2 seems ambiguous.
For = "ACK RECEPTION,=20 LOSS DETECTED", order is important: if I suppose there are only one T = variable=20 and one W variable:
 
  • If I = compute first=20 T =3D T - W/2, I use the previous value of W
  • If I = compute T=20 after W, I use the new value of W
 
The = same problem=20 exist also in the token computation without losses.
 
Is = there something=20 missing in the draft, or do I misunderstand?
 
Regards,

G=E9rard = BABONNEAU=20

france = telecom = R&D=20
4, rue du Clos Courtel - BP 59 - = 35512 Cesson=20 Sevign=E9 Cedex
Tel : +33 2 99 = 12 40=20 08  -  Fax : +33 2 99 12 40 98
e-mail : gerard.babonneau@francetelecom.com



 
------_=_NextPart_001_01C352A2.4645DF32-- _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Mon Jul 28 11:46:49 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08309 for ; Mon, 28 Jul 2003 11:46:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hACc-0003V2-Pw for rmt-archive@odin.ietf.org; Mon, 28 Jul 2003 11:46:23 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6SFkMTk013448 for rmt-archive@odin.ietf.org; Mon, 28 Jul 2003 11:46:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hACc-0003Up-Mr for rmt-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 11:46:22 -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 LAA08262 for ; Mon, 28 Jul 2003 11:46:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hACb-0004TF-00 for rmt-web-archive@ietf.org; Mon, 28 Jul 2003 11:46:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hACa-0004T7-00 for rmt-web-archive@ietf.org; Mon, 28 Jul 2003 11:46:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hACH-0003SI-Mp; Mon, 28 Jul 2003 11:46:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hABR-0003Qo-TW for rmt@optimus.ietf.org; Mon, 28 Jul 2003 11:45:09 -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 LAA08173 for ; Mon, 28 Jul 2003 11:45:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hABQ-0004RB-00 for rmt@ietf.org; Mon, 28 Jul 2003 11:45:08 -0400 Received: from smtp-out.sprintlabs.com ([208.30.172.76]) by ietf-mx with esmtp (Exim 4.12) id 19hABP-0004QP-00 for rmt@ietf.org; Mon, 28 Jul 2003 11:45:07 -0400 Received: from mailman.sprintlabs.com (mx.sprintlabs.com [199.2.53.192]) by smtp-out.sprintlabs.com (Postfix) with ESMTP id 13BE9B8093; Mon, 28 Jul 2003 08:45:37 -0700 (PDT) Received: by mailman.sprintlabs.com with Internet Mail Service (5.5.2656.59) id ; Mon, 28 Jul 2003 08:44:37 -0700 Message-ID: <49D9473417F1234C9C86886EE8353FAAEFF706@mailman.sprintlabs.com> From: Gianluca Iannaccone To: =?iso-8859-1?Q?=27BABONNEAU_G=E9rard_FTRD/DMI/REN=27?= , "'rmt@ietf.org'" Subject: RE: [Rmt] PGMCC window manager computation Date: Mon, 28 Jul 2003 08:44:32 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable 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: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable gerard, the order is certainly important and the draft reads:=20 T =3D T - W/2, W =3D W/2=20 where the comma indicates the order. so a sender decreases the tokens by half-window and then cuts by half the current window size.=20 however, if it makes the draft more readable we could use=20 two lines: T =3D T - W/2; W =3D W/2;=20 cheers,=20 gianluca =20 ---------------------------------------------------------- Gianluca Iannaccone ' gianluca@sprintlabs.com Sprint ATL ' tel +1 (650) 375-4198 1 Adrian Court ' fax +1 (650) 375-4079 Burlingame, CA 94010 ' www.sprintlabs.com/~gianluca -----Original Message----- From: BABONNEAU G=E9rard FTRD/DMI/REN [mailto:gerard.babonneau@rd.francetelecom.com]=20 Sent: Friday, July 25, 2003 4:46 AM To: rmt@ietf.org Subject: [Rmt] PGMCC window manager computation Hi, Algorithm in section 2.2 seems ambiguous. For "ACK RECEPTION, = LOSS DETECTED", order is important: if I suppose there are only one T = variable and one W variable: =20 If I compute first T =3D T - W/2, I use the previous value of W=20 If I compute T after W, I use the new value of W The same problem exist also in the token computation without losses. = Is there something missing in the draft, or do I misunderstand? Regards, = G=E9rard BABONNEAU=20 france telecom R&D=20 4, rue du Clos Courtel - BP 59 - 35512 Cesson Sevign=E9 Cedex=20 Tel : +33 2 99 12 40 08 - Fax : +33 2 99 12 40 98=20 e-mail : gerard.babonneau@francetelecom.com=20 =20 _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Tue Jul 29 18:29:44 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13485 for ; Tue, 29 Jul 2003 18:29:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hcy8-0001sY-8M for rmt-archive@odin.ietf.org; Tue, 29 Jul 2003 18:29:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TMTKVH007222 for rmt-archive@odin.ietf.org; Tue, 29 Jul 2003 18:29:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hcy8-0001sP-3k for rmt-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 18:29:20 -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 SAA13473 for ; Tue, 29 Jul 2003 18:29:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hcy5-0002Xq-00 for rmt-web-archive@ietf.org; Tue, 29 Jul 2003 18:29:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hcy4-0002Xm-00 for rmt-web-archive@ietf.org; Tue, 29 Jul 2003 18:29:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hcxp-0001pt-7B; Tue, 29 Jul 2003 18:29:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hcxC-0001pU-Pk for rmt@optimus.ietf.org; Tue, 29 Jul 2003 18:28:22 -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 SAA13436; Tue, 29 Jul 2003 18:28:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hcx9-0002XI-00; Tue, 29 Jul 2003 18:28:19 -0400 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19hcx8-0002X7-00; Tue, 29 Jul 2003 18:28:19 -0400 Received: from cisco.com (171.68.223.137) by sj-iport-3.cisco.com with ESMTP; 29 Jul 2003 15:27:48 -0700 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h6TMRbuG021609; Tue, 29 Jul 2003 15:27:38 -0700 (PDT) Received: (from lorenzo@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id PAA10557; Tue, 29 Jul 2003 15:27:37 -0700 (PDT) Date: Tue, 29 Jul 2003 15:27:36 -0700 From: Lorenzo Vicisano To: rmt@ietf.org, minutes@ietf.org Cc: Allison Mankin , jon.peterson@neustar.biz, Roger Kermode , Lorenzo Vicisano Message-ID: <20030729152736.F4580@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Subject: [Rmt] RMT minutes, 57th IETF, Vienna 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: , Please find attached the meeting minutes. thank you, the chairs Reliable Multicast Transport 57th IETF, Vienna Monday, July 14th 15:30 - 16:15 ===================== Opening Remarks Chairs ====================== - Charter was updated: * removed TRACK as per WG consensus * GRA is still in, but to be discussed (see next) - GRA discussion: no interested party answered to the call for editors/requirements issued after the last IETF. The proposal is to discontinue the GRA work at this time. To be decided on the mailing list. NACK Oriented Reliable Multicast (NORM) Update Joe Macker for Brian Adamson draft-ietf-rmt-pi-norm-07 draft-ietf-rmt-bb-norm-06 ============================================== NORM BB updated 06 to 07 - http://norm.pf.itd.nrl.navy.mil has open source - changes to make doc more compliant with TFMRC PI doc updated from 05 to 06 - modularized - Vincent Roca has provided feedback. In particular a header extension options is currently being considered to coordinate with the FLUTE spec. - added congestion control fields - Next steps, open source will continue to mature further experimentations and simulations will be performed - Need to decide whether we want a new WG last call for the NORM drafts, or just go to the IESG. - Need to solve the header extension and FLUTE issue. FLUTE, File Delivery over Undirectional Transport Tony Paila draft-ietf-rmt-flute-00 ========== - 00 WG draft, derived from FDALC individual submission - FDALC specify a particular application (usage profile) of ALC for file delivery over unidirectional links - Toni is editor, added 3 new authors - believes that new draft meets requirements from last meeting - Proceed providing updates: * FDT content, XML schema from FDT syntax, * FDT encap streamlined, cross checked with ALC/LCT RFCs * how to use multiple channels, etc * how to describe file delivery session using SDP is now info chapter * receiver operation is now informational chapter * security considerations elaborated further - discussion on whether part of the SDP section should be normative instead. Lorenzo to provide comments on this. - propose to hold last call in September and maybe add this a charter milestone. - two genetically independent implementations to be ready by November with some interop testing, at least one will be open source PGMCC Update Gianluca Iannaccone draft-ietf-rmt-bb-pgmcc-02 ==================== Security considerations One issue addressed: Session hijacking - session hijacking solved out authentications - can drive the sender to flood the network - breaks the election mechanism The rest is transport protocol responsibility - authentication - deal with the denial of service problem Recommendations - PGMCC sender should compare ACK stream with reported loss rate and RTT info reports to prevent DOS attacks - if violation mark acker has ineligible - believer ready for last call Lorenzo: TFMCC and PGMCC both look like they are ready for last call...need to check with TFMCC authors Lorenzo: discussed with Allison about potential outside reviews of TF/PGM CC drafts form people not involved with them...would be an additional step before submission to the IESG Pullman: have done some experiments with TFMCC and it appears to work well. _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Tue Jul 29 19:21:44 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14988 for ; Tue, 29 Jul 2003 19:21:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hdmR-0004fB-G7 for rmt-archive@odin.ietf.org; Tue, 29 Jul 2003 19:21:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TNLJq9017919 for rmt-archive@odin.ietf.org; Tue, 29 Jul 2003 19:21:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hdmR-0004ew-Bs for rmt-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 19:21:19 -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 TAA14945 for ; Tue, 29 Jul 2003 19:21:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hdmP-0002rP-00 for rmt-web-archive@ietf.org; Tue, 29 Jul 2003 19:21:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hdmP-0002rM-00 for rmt-web-archive@ietf.org; Tue, 29 Jul 2003 19:21:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hdm9-0004Vf-Im; Tue, 29 Jul 2003 19:21:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hdm5-0004Ub-Ul for rmt@optimus.ietf.org; Tue, 29 Jul 2003 19:20:57 -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 TAA14906 for ; Tue, 29 Jul 2003 19:20:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hdm4-0002r3-00 for rmt@ietf.org; Tue, 29 Jul 2003 19:20:56 -0400 Received: from sj-core-4.cisco.com ([171.68.223.138]) by ietf-mx with esmtp (Exim 4.12) id 19hdm3-0002qx-00 for rmt@ietf.org; Tue, 29 Jul 2003 19:20:55 -0400 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h6TNKNpp014493; Tue, 29 Jul 2003 16:20:24 -0700 (PDT) Received: (from lorenzo@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id QAA26189; Tue, 29 Jul 2003 16:20:23 -0700 (PDT) Date: Tue, 29 Jul 2003 16:20:23 -0700 From: Lorenzo Vicisano To: rmt@ietf.org Cc: Roger.Kermode@motorola.com, Lorenzo Vicisano Message-ID: <20030729162023.G4580@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Subject: [Rmt] GRA work to be dropped ? 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: , Hi, At the San Francisco IETF meeting, the removal of GRA from the proposed milestone list prompted some RMT participants to express interest in continuing the work (please see the minutes). However since then we haven't seen any concrete sign of interest, hence we are proposing again to remove GRA from the RMT milestones. If you object to this, are able to commit your time to contribute to GRA and see realistic applications for it, please reply to this email within the next few days. thank you, the chairs. _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt