From exim@www1.ietf.org Tue Feb 17 20:28:05 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21627 for ; Tue, 17 Feb 2004 20:28:05 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtGUy-0004tM-Hx for rmt-archive@odin.ietf.org; Tue, 17 Feb 2004 20:27:37 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1I1Ra5Q018798 for rmt-archive@odin.ietf.org; Tue, 17 Feb 2004 20:27:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtGUy-0004t7-CB for rmt-web-archive@optimus.ietf.org; Tue, 17 Feb 2004 20:27:36 -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 UAA21610 for ; Tue, 17 Feb 2004 20:27:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtGUw-0003WJ-00 for rmt-web-archive@ietf.org; Tue, 17 Feb 2004 20:27:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtGU3-0003Rt-00 for rmt-web-archive@ietf.org; Tue, 17 Feb 2004 20:26:40 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AtGTQ-0003Nt-00 for rmt-web-archive@ietf.org; Tue, 17 Feb 2004 20:26:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtGTR-0004e3-Qz; Tue, 17 Feb 2004 20:26:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtGSw-0004Zi-Lu for rmt@optimus.ietf.org; Tue, 17 Feb 2004 20:25:30 -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 UAA21536 for ; Tue, 17 Feb 2004 20:25:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtGSu-0003Me-00 for rmt@ietf.org; Tue, 17 Feb 2004 20:25:28 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtGS0-0003KD-00 for rmt@ietf.org; Tue, 17 Feb 2004 20:24:32 -0500 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AtGRQ-0003GF-00 for rmt@ietf.org; Tue, 17 Feb 2004 20:23:56 -0500 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1I1NP1m016318 for ; Tue, 17 Feb 2004 17:23:25 -0800 (PST) Received: (from lorenzo@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id RAA04925; Tue, 17 Feb 2004 17:23:24 -0800 (PST) Date: Tue, 17 Feb 2004 17:23:24 -0800 From: Lorenzo Vicisano To: rmt@ietf.org Message-ID: <20040217172324.C18523@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Subject: [Rmt] agenda items for 59th IETF 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.0 required=5.0 tests=none autolearn=no version=2.60 If you have discussion items that you would like to include in the agenda please let us know. thank you, the chairs. _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Wed Feb 18 18:22:08 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01089 for ; Wed, 18 Feb 2004 18:22:08 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atb0f-0001bj-U7 for rmt-archive@odin.ietf.org; Wed, 18 Feb 2004 18:21:42 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1INLfQm006171 for rmt-archive@odin.ietf.org; Wed, 18 Feb 2004 18:21:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atb0f-0001bN-Oz for rmt-web-archive@optimus.ietf.org; Wed, 18 Feb 2004 18:21:41 -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 SAA01063 for ; Wed, 18 Feb 2004 18:21:37 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atb0c-0001QG-00 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 18:21:38 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atazl-0001Oj-00 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 18:20:45 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Ataz6-0001Mh-00 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 18:20:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ataz7-0000tv-EA; Wed, 18 Feb 2004 18:20:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atayw-0000qu-BL for rmt@optimus.ietf.org; Wed, 18 Feb 2004 18:19:54 -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 SAA00919 for ; Wed, 18 Feb 2004 18:19:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atayt-0001M7-00 for rmt@ietf.org; Wed, 18 Feb 2004 18:19:51 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atay3-0001JO-00 for rmt@ietf.org; Wed, 18 Feb 2004 18:19:00 -0500 Received: from venus.open.ac.uk ([194.66.147.160]) by ietf-mx with esmtp (Exim 4.12) id 1Ataxc-0001EC-00 for rmt@ietf.org; Wed, 18 Feb 2004 18:18:32 -0500 Received: from oufcnt2.open.ac.uk (actually host halley.open.ac.uk) by venus.open.ac.uk via SMTP Local (Mailer 3.1) with ESMTP; Wed, 18 Feb 2004 23:17:55 +0000 Message-id: Date: Wed, 18 Feb 2004 23:17:54 +0000 Subject: Re: [Rmt] agenda items for 59th IETF To: Lorenzo Vicisano Cc: rmt@ietf.org From: Andrew Marlow References: <20040217172324.C18523@cisco.com> In-Reply-To: <20040217172324.C18523@cisco.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit 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.9 required=5.0 tests=FROM_ENDS_IN_NUMS autolearn=no version=2.60 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Lorenzo Vicisano writes: >If you have discussion items that you would like >to include in the agenda please let us know. > > thank you, > the chairs. Yes, what's the status of the reference implementation please? Also I just want to point out that most of the recent attention seems to have been focused on flute rather than norm. Does this mean the norm spec is complete? Regards, Andrew Marlow ---- There is an emerald here the size of a plover's egg! _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Wed Feb 18 19:07:37 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03442 for ; Wed, 18 Feb 2004 19:07:37 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atbii-0005at-2i for rmt-archive@odin.ietf.org; Wed, 18 Feb 2004 19:07:12 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J07BQn021495 for rmt-archive@odin.ietf.org; Wed, 18 Feb 2004 19:07:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atbih-0005aU-LN for rmt-web-archive@optimus.ietf.org; Wed, 18 Feb 2004 19:07:11 -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 TAA03321 for ; Wed, 18 Feb 2004 19:07:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atbie-00040F-00 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 19:07:08 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atbhc-0003pu-00 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 19:06:04 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Atbgo-0003kj-00 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 19:05:14 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by mx2.foretec.com with esmtp (Exim 4.24) id 1AtbXu-0007dE-H9 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 18:56:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtbXt-0004PQ-Mv; Wed, 18 Feb 2004 18:56:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtbXh-0004Oj-Ak for rmt@optimus.ietf.org; Wed, 18 Feb 2004 18:55:49 -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 SAA02989 for ; Wed, 18 Feb 2004 18:55:44 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtbXe-0003Tw-00 for rmt@ietf.org; Wed, 18 Feb 2004 18:55:46 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtbWk-0003SY-00 for rmt@ietf.org; Wed, 18 Feb 2004 18:54:51 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1AtbVu-0003OU-00 for rmt@ietf.org; Wed, 18 Feb 2004 18:53:59 -0500 Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 18 Feb 2004 15:53:36 -0800 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i1INrPcw005869; Wed, 18 Feb 2004 15:53:26 -0800 (PST) Received: (from lorenzo@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id PAA27837; Wed, 18 Feb 2004 15:53:25 -0800 (PST) Date: Wed, 18 Feb 2004 15:53:25 -0800 From: Lorenzo Vicisano To: Andrew Marlow Cc: rmt@ietf.org Subject: Re: [Rmt] agenda items for 59th IETF Message-ID: <20040218155325.A25276@cisco.com> References: <20040217172324.C18523@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i 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.0 required=5.0 tests=none autolearn=no version=2.60 Andrew, > Yes, what's the status of the reference implementation please? Although most of the RMT specs are implemented in some publicly available piece of software, generally speaking we have no official "reference implementations". I believe that the closest we come to this is in NORM (http://norm.pf.itd.nrl.navy.mil/) In the past a number of people have posted pointers to their implementations, I'm thinking that it would be useful to compile a list of them.. I'll start a separate thread for this. Depending on the result of this poll we can consider including presentation of the results in the meeting agenda. > Also I just want to point out that most of the recent attention > seems to have been focused on flute rather than norm. > Does this mean the norm spec is complete? yes: the norm BB and PI specs have been submitted to the IESG for publication and are currently in IETF "last call". thanks, Lorenzo > > Regards, > > Andrew Marlow > ---- > There is an emerald here the size of a plover's egg! > _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Wed Feb 18 19:25:35 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04027 for ; Wed, 18 Feb 2004 19:25:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atc04-0006fy-36 for rmt-archive@odin.ietf.org; Wed, 18 Feb 2004 19:25:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J0P8Za025662 for rmt-archive@odin.ietf.org; Wed, 18 Feb 2004 19:25:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atc03-0006fp-Vc for rmt-web-archive@optimus.ietf.org; Wed, 18 Feb 2004 19:25:08 -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 TAA03956 for ; Wed, 18 Feb 2004 19:25:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atc02-0004fu-00 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 19:25:06 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtbzJ-0004Zz-00 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 19:24:22 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Atbxy-0004TF-04 for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 19:22:58 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by mx2.foretec.com with esmtp (Exim 4.24) id 1AtbkS-0007xA-FE for rmt-web-archive@ietf.org; Wed, 18 Feb 2004 19:09:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtbkT-0005wg-BP; Wed, 18 Feb 2004 19:09:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtbjW-0005sx-Uo for rmt@optimus.ietf.org; Wed, 18 Feb 2004 19:08:02 -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 TAA03501 for ; Wed, 18 Feb 2004 19:07:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtbjT-00047X-00 for rmt@ietf.org; Wed, 18 Feb 2004 19:07:59 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atbir-000423-00 for rmt@ietf.org; Wed, 18 Feb 2004 19:07:21 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1Atbhr-0003nN-00 for rmt@ietf.org; Wed, 18 Feb 2004 19:06:19 -0500 Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 18 Feb 2004 16:05:58 -0800 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i1J05mcw013720 for ; Wed, 18 Feb 2004 16:05:48 -0800 (PST) Received: (from lorenzo@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id QAA02627 for rmt@ietf.org; Wed, 18 Feb 2004 16:05:47 -0800 (PST) Date: Wed, 18 Feb 2004 16:05:47 -0800 From: Lorenzo Vicisano To: rmt@ietf.org Message-ID: <20040218160547.B25276@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Subject: [Rmt] implementations of RMT specs 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.0 required=5.0 tests=none autolearn=no version=2.60 Following the recent request from Andrew Marlow, I believe it would be of general interest to collect a list of publicly available implementations of RMT protocols. If you like to contribute, please post a pointer to your implementation with a brief description including: - the protocol (BB, PI) implemented - the relevant specs - is implementation current (if not which draft version is used) ? - is the implementation complete ? - has it been tested for interoperability ? It would probably be useful to hear about commercial, non public-domain implementations too. thank you, Lorenzo _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Thu Feb 19 01:03:22 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15618 for ; Thu, 19 Feb 2004 01:03:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AthGv-0008Ok-7G for rmt-archive@odin.ietf.org; Thu, 19 Feb 2004 01:02:53 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J62reY032278 for rmt-archive@odin.ietf.org; Thu, 19 Feb 2004 01:02:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AthGv-0008OX-3Q for rmt-web-archive@optimus.ietf.org; Thu, 19 Feb 2004 01:02:53 -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 BAA15600 for ; Thu, 19 Feb 2004 01:02:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AthGs-0004tm-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 01:02:50 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AthFw-0004r2-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 01:01:53 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AthF5-0004oE-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 01:00:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AthF6-0008Bb-Kz; Thu, 19 Feb 2004 01:01:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AthEx-0008B4-It for rmt@optimus.ietf.org; Thu, 19 Feb 2004 01:00:51 -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 BAA15558 for ; Thu, 19 Feb 2004 01:00:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AthEu-0004mg-00 for rmt@ietf.org; Thu, 19 Feb 2004 01:00:48 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AthDw-0004kT-00 for rmt@ietf.org; Thu, 19 Feb 2004 00:59:49 -0500 Received: from huiluvaris.cs.tut.fi ([130.230.4.16] helo=mail2.cs.tut.fi ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1AthD6-0004iD-00 for rmt@ietf.org; Thu, 19 Feb 2004 00:58:56 -0500 Received: from samipelt (samipelt.atm.tut.fi [130.230.52.31]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail2.cs.tut.fi (Postfix) with ESMTP id 465934BC80; Thu, 19 Feb 2004 07:58:55 +0200 (EET) From: "Sami Peltotalo" To: "Rmt" Subject: RE: [Rmt] implementations of RMT specs Date: Thu, 19 Feb 2004 07:59:31 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <20040218160547.B25276@cisco.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit 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.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi all, We have implemented FLUTE, so we have also implemented ALC/LCT protocols. FLUTE is based on latest 07-draft and ALC/LCT are based on the RFCs. Implementation is quite complete but new features are still going to be added. We have done interoperability tests with other FLUTE implementations and those have succeeded quite well. Link to our site is http://www.atm.tut.fi/mad Cheers, Sami > > Following the recent request from Andrew Marlow, I believe > it would be of general interest to collect a list of publicly > available implementations of RMT protocols. > > If you like to contribute, please post a pointer to your > implementation with a brief description including: > > - the protocol (BB, PI) implemented > - the relevant specs > - is implementation current (if not which draft version > is used) ? > - is the implementation complete ? > - has it been tested for interoperability ? > > It would probably be useful to hear about commercial, non > public-domain implementations too. > > thank you, > Lorenzo _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Thu Feb 19 01:54:25 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17053 for ; Thu, 19 Feb 2004 01:54:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ati4L-0003Zw-C6 for rmt-archive@odin.ietf.org; Thu, 19 Feb 2004 01:53:57 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J6rvpw013750 for rmt-archive@odin.ietf.org; Thu, 19 Feb 2004 01:53:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ati4L-0003Zh-8o for rmt-web-archive@optimus.ietf.org; Thu, 19 Feb 2004 01:53:57 -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 BAA17032 for ; Thu, 19 Feb 2004 01:53:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ati4H-0007D0-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 01:53:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ati3K-00079P-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 01:52:55 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Ati2R-00077L-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 01:51:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ati2T-0003T8-FL; Thu, 19 Feb 2004 01:52:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ati2O-0003Sv-Hh for rmt@optimus.ietf.org; Thu, 19 Feb 2004 01:51:56 -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 BAA17007 for ; Thu, 19 Feb 2004 01:51:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ati2L-00076S-00 for rmt@ietf.org; Thu, 19 Feb 2004 01:51:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ati1Q-00074h-00 for rmt@ietf.org; Thu, 19 Feb 2004 01:50:56 -0500 Received: from mx.webfountain.com ([63.161.54.39]) by ietf-mx with smtp (Exim 4.12) id 1Ati0U-00071e-00 for rmt@ietf.org; Thu, 19 Feb 2004 01:49:58 -0500 Received: (qmail 8822 invoked from network); 19 Feb 2004 06:49:19 -0000 Received: from mail.intranet (10.1.1.37) by mx.webfountain.com with SMTP; 19 Feb 2004 06:49:19 -0000 Received: by mail.intranet (8.12.1/8.12.1/Debian -5) with SMTP id i1J6oo8f009230; Wed, 18 Feb 2004 22:50:50 -0800 From: "Michael Luby" To: "Lorenzo Vicisano" , "Andrew Marlow" Cc: Subject: RE: [Rmt] agenda items for 59th IETF Date: Wed, 18 Feb 2004 22:48:52 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20040218155325.A25276@cisco.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit 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.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Actually, despite the impression that the focus of attention has been on FLUTE instead of NORM, they are pretty much in the same state at this point, i.e., FLUTE and NORM have both successfully passed RMT working group last call. I don't know beyond this where NORM is at, but FLUTE has already been reviewed by the IESG and the IESG comments on FLUTE are being addressed as I write this as FLUTE moves towards RFC status. > -----Original Message----- > From: rmt-admin@ietf.org [mailto:rmt-admin@ietf.org]On Behalf Of Lorenzo > Vicisano > Sent: Wednesday, February 18, 2004 3:53 PM > To: Andrew Marlow > Cc: rmt@ietf.org > Subject: Re: [Rmt] agenda items for 59th IETF > > > Andrew, > > > Yes, what's the status of the reference implementation please? > > Although most of the RMT specs are implemented in some > publicly available piece of software, generally speaking > we have no official "reference implementations". > > I believe that the closest we come to this is in NORM > (http://norm.pf.itd.nrl.navy.mil/) > > In the past a number of people have posted pointers > to their implementations, I'm thinking that it would > be useful to compile a list of them.. I'll start a separate > thread for this. > > Depending on the result of this poll we can consider > including presentation of the results in the meeting agenda. > > > Also I just want to point out that most of the recent attention > > seems to have been focused on flute rather than norm. > > Does this mean the norm spec is complete? > > yes: the norm BB and PI specs have been submitted to the IESG for > publication and are currently in IETF "last call". > > thanks, > Lorenzo > > > > > Regards, > > > > Andrew Marlow > > ---- > > There is an emerald here the size of a plover's egg! > > > > _______________________________________________ > Rmt mailing list > Rmt@ietf.org > https://www1.ietf.org/mailman/listinfo/rmt > _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Thu Feb 19 02:39:35 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03024 for ; Thu, 19 Feb 2004 02:39:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atim2-0007VN-TG for rmt-archive@odin.ietf.org; Thu, 19 Feb 2004 02:39:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J7d6gZ028842 for rmt-archive@odin.ietf.org; Thu, 19 Feb 2004 02:39:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atim1-0007Ul-6A for rmt-web-archive@optimus.ietf.org; Thu, 19 Feb 2004 02:39:05 -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 CAA02865 for ; Thu, 19 Feb 2004 02:39:02 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atilx-0001mM-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 02:39:01 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atikw-0001ay-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 02:37:59 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Atik0-0001Yo-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 02:37:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atik1-00075H-IO; Thu, 19 Feb 2004 02:37:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atijv-00074h-BK for rmt@optimus.ietf.org; Thu, 19 Feb 2004 02:36:55 -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 CAA02819 for ; Thu, 19 Feb 2004 02:36:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atijr-0001Xg-00 for rmt@ietf.org; Thu, 19 Feb 2004 02:36:51 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atiit-0001WC-00 for rmt@ietf.org; Thu, 19 Feb 2004 02:35:52 -0500 Received: from mx.webfountain.com ([63.161.54.39]) by ietf-mx with smtp (Exim 4.12) id 1Atihv-0001UQ-00 for rmt@ietf.org; Thu, 19 Feb 2004 02:34:51 -0500 Received: (qmail 9336 invoked from network); 19 Feb 2004 07:34:22 -0000 Received: from mail.intranet (10.1.1.37) by mx.webfountain.com with SMTP; 19 Feb 2004 07:34:22 -0000 Received: by mail.intranet (8.12.1/8.12.1/Debian -5) with SMTP id i1J7Zq8f009793; Wed, 18 Feb 2004 23:35:52 -0800 From: "Michael Luby" To: "Rmt" Cc: "Michael Luby" Subject: RE: [Rmt] implementations of RMT specs Date: Wed, 18 Feb 2004 23:33:54 -0800 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01C3F677.ABD72290" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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.7 required=5.0 tests=AWL,HTML_20_30,HTML_FONT_BIG, HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_0018_01C3F677.ABD72290 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Digital Fountain has implemented and sold products that are based on ALC/LCT/FEC for years, and we are compliant with the RFC versions of all these specs (RFC 3450, 3451, 3452) and the implementations are quite mature. There have been no interoperability tests with other vendors. (1) The Transporter Fountain product line (which supports both multicast and unicast, and also supports the latest version of theWEBRC congestion control protocol that is on its way to becoming an RFC) has been used extensively by Hollywood for moving Digital Dailies (Harry Potter 3, Last Samurai, Fast and Furious 2, Return of the Ring see e.g., http://www.digitalfountain.com/company/pressReleaseItem.cfm?uid=47), by the U.S. military in Iraq and Afghanistan (for example in the rescue of Jessica Lynch, see http://www.fcw.com/fcw/articles/2003/0630/tec-data-06-30-03.asp), and for many other applications too numerous and confidential to list. A pointer to the Transporter Fountain product is http://www.digitalfountain.com/support/index.cfm, although we are no longer actively selling this and have moved to a licensing model. (2) In the licensing model, our FEC codecs are fully compliant with the FEC building block RFC 3452 and/or the latest draft of the Compact FEC building block (that is in the RFC editor's queue and soon to be published if there are no further IETF delays), and have been or about to be deployed for a number of applications, including military (see http://www.digitalfountain.com/company/pressReleaseItem.cfm?uid=49to), automobiles, and commercial streaming applications http://www.convergedigest.com/DSL/lastmilearticle.asp?ID=9204. A pointer for our core FEC product is http://www.digitalfountain.com/licensing/products/DFcore.cfm. Sorry if this is too commercial for RMT, but heh, I didn't ask the question, I just gave the (far from full) response ;) Mike > -----Original Message----- > From: rmt-admin@ietf.org [mailto:rmt-admin@ietf.org]On Behalf Of Sami > Peltotalo > Sent: Wednesday, February 18, 2004 10:00 PM > To: Rmt > Subject: RE: [Rmt] implementations of RMT specs > > > Hi all, > > We have implemented FLUTE, so we have also implemented ALC/LCT protocols. > FLUTE is based on latest 07-draft and ALC/LCT are based on the RFCs. > Implementation is quite complete but new features are still going to be > added. We have done interoperability tests with other FLUTE > implementations > and those have succeeded quite well. > > Link to our site is http://www.atm.tut.fi/mad > > Cheers, Sami > > > > > Following the recent request from Andrew Marlow, I believe > > it would be of general interest to collect a list of publicly > > available implementations of RMT protocols. > > > > If you like to contribute, please post a pointer to your > > implementation with a brief description including: > > > > - the protocol (BB, PI) implemented > > - the relevant specs > > - is implementation current (if not which draft version > > is used) ? > > - is the implementation complete ? > > - has it been tested for interoperability ? > > > > It would probably be useful to hear about commercial, non > > public-domain implementations too. > > > > thank you, > > Lorenzo > > > _______________________________________________ > Rmt mailing list > Rmt@ietf.org > https://www1.ietf.org/mailman/listinfo/rmt > ------=_NextPart_000_0018_01C3F677.ABD72290 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Digital Fountain has implemented and = sold products=20 that are based on ALC/LCT/FEC for years, and we are compliant with = the RFC=20 versions of all these specs  (RFC 3450, 3451, 3452) and the = implementations=20 are quite mature.  There have been no interoperability tests with = other=20 vendors.

(1) The Transporter Fountain product line (which = supports both=20 multicast and unicast, and also supports the latest version of  = theWEBRC=20 congestion control protocol that is on its way to becoming an RFC) has = been used=20 extensively by Hollywood for moving Digital Dailies (Harry Potter 3, = Last=20 Samurai, Fast and Furious 2, Return of the Ring see e.g., http://www.digitalfountain.com/company/pressReleaseItem.cfm?uid=3D= 47), by the U.S. military in Iraq and Afghanistan (for example in = the=20 rescue of Jessica Lynch, see http://www.fcw.com/fcw/articles/2003/0630/tec-data-06-30-03.asp<= /FONT>), and for many other applications too numerous and = confidential to=20 list.  A pointer to the Transporter Fountain product is http://www.digitalfountain.com/support/index.cfm,=20 although we are no longer actively selling this and have moved to a = licensing=20 model. 

(2) In the licensing model, our FEC codecs are fully = compliant with the FEC building block RFC 3452 and/or the latest draft = of the=20 Compact FEC building block (that is in the RFC editor's queue and soon = to be=20 published if there are no further IETF delays), and have been or about = to be=20 deployed for a number of applications, including military (see http://www.digitalfountain.com/company/pressReleaseItem.cfm?uid=3D= 49to), automobiles, and commercial streaming applications http://www.convergedigest.com/DSL/lastmilearticle.asp?ID=3D9204<= /FONT>.  A pointer for our core FEC product is http://www.digitalfountain.com/licensing/products/DFcore.cfm.

Sorry if this is too commercial for RMT, but heh, I = didn't ask=20 the question, I just gave the (far from full)=20 response ;)
Mike  

> -----Original=20 Message-----
> From: rmt-admin@ietf.org [mailto:rmt-admin@ietf.org]On = Behalf Of=20 Sami
> Peltotalo
> Sent: Wednesday, February 18, 2004 10:00=20 PM
> To: Rmt
> Subject: RE: [Rmt] implementations of RMT=20 specs
>
>
> Hi all,
>
> We have = implemented FLUTE,=20 so we have also implemented ALC/LCT protocols.
> FLUTE is based on = latest=20 07-draft and ALC/LCT are based on the RFCs.
> Implementation is = quite=20 complete but new features are still going to be
> added. We have = done=20 interoperability tests with other FLUTE
> implementations
> = and=20 those have succeeded quite well.
>
> Link to our site is http://www.atm.tut.fi/mad
>
> Cheers,=20 Sami
>
> >
> > Following the recent request from = Andrew=20 Marlow, I believe
> > it would be of general interest to = collect a list=20 of publicly
> > available implementations of RMT = protocols.
>=20 >
> > If you like to contribute, please post a pointer to=20 your
> > implementation with a brief description = including:
>=20 >
> >   - the protocol (BB, PI) = implemented
>=20 >   - the relevant specs
> >   - is=20 implementation current (if not which draft version
>=20 >     is used) ?
> >   - is = the=20 implementation complete ?
> >   - has it been tested = for=20 interoperability ?
> >
> > It would probably be useful = to hear=20 about commercial, non
> > public-domain implementations = too.
>=20 >
> >     thank you,
> > =    =20 Lorenzo
>
>
>=20 _______________________________________________
> Rmt mailing = list
>=20 Rmt@ietf.org
> https://www1.ietf.org/mailman/listinfo/rmt
>=20

------=_NextPart_000_0018_01C3F677.ABD72290-- _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Thu Feb 19 03:40:26 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05630 for ; Thu, 19 Feb 2004 03:40: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 1Atjiv-0003FZ-Jt for rmt-archive@odin.ietf.org; Thu, 19 Feb 2004 03:39:57 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J8dvmC012491 for rmt-archive@odin.ietf.org; Thu, 19 Feb 2004 03:39:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atjiv-0003FO-06 for rmt-web-archive@optimus.ietf.org; Thu, 19 Feb 2004 03:39:57 -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 DAA05606 for ; Thu, 19 Feb 2004 03:39:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atjis-00050b-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 03:39:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atjhw-0004xG-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 03:38:57 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Atjh4-0004tm-00 for rmt-web-archive@ietf.org; Thu, 19 Feb 2004 03:38:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atjh3-0002zI-Sv; Thu, 19 Feb 2004 03:38:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atjg6-0002pB-SN for rmt@optimus.ietf.org; Thu, 19 Feb 2004 03:37:02 -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 DAA05532 for ; Thu, 19 Feb 2004 03:37:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atjg4-0004rQ-00 for rmt@ietf.org; Thu, 19 Feb 2004 03:37:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atjf9-0004oz-00 for rmt@ietf.org; Thu, 19 Feb 2004 03:36:03 -0500 Received: from mx-serv.inrialpes.fr ([194.199.18.100]) by ietf-mx with esmtp (Exim 4.12) id 1AtjeJ-0004il-00 for rmt@ietf.org; Thu, 19 Feb 2004 03:35:11 -0500 Received: from imap-serv.inrialpes.fr (imap-serv.inrialpes.fr [194.199.18.72]) by mx-serv.inrialpes.fr (8.12.10/8.12.10) with ESMTP id i1J8YQTs015561; Thu, 19 Feb 2004 09:34:26 +0100 (MET) Received: from inrialpes.fr (iseran.inrialpes.fr [194.199.24.100]) by imap-serv.inrialpes.fr (8.11.6/8.11.3/ImagV2) with ESMTP id i1J8YQQ06671; Thu, 19 Feb 2004 09:34:26 +0100 (MET) Message-ID: <40347512.2020400@inrialpes.fr> Date: Thu, 19 Feb 2004 09:34:26 +0100 From: Vincent Roca Organization: INRIA Rhone-Alpes User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031029 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lorenzo Vicisano CC: rmt@ietf.org Subject: Re: [Rmt] implementations of RMT specs References: <20040218160547.B25276@cisco.com> In-Reply-To: <20040218160547.B25276@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-INRIALPES-MailScanner-Information: Please contact the ISP for more information X-INRIALPES-MailScanner: McAfee uvscan 4241 RBL+ ORBS Found to be clean Content-Transfer-Encoding: 7bit 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.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit We, at INRIA, have implemented several RMT BBs and PIs: ** ALC PI and LCT BB, compliant with the related RFCs FLUTE (v-07) is also implemented (some advanced features are missing, though) and successful interoperability tests have been carried out with three other implementations. The RLC and FLID-SL (static version only) congestion control protocols are also available, even if they are not documented in any I-D/RFC. ** Open Source Large Block FEC BB This codec is available independantly (for use in other tools) and is also fully integrated in our ALC/FLUTE tools. ** NORM BB/PI is partially implemented, but is not in line with the latest documents. Yet a great part of the stuff is already here... These softwares, that follow a GNU GPL or LGPL licence (see the web site for more info on licences), are available at: http://www.inrialpes.fr/planete/people/roca/mcl/ Regards, Vincent and the other members of the MCLv3 project. ---------------------- http://www.inrialpes.fr/planete/people/roca/ INRIA Rhone-Alpes - projet planete vincent.roca@inrialpes.fr Zirst; 655 av. de l'Europe; Montbonnot phone (+33) 4.76.61.52.16 38334 ST ISMIER cedex - France fax (+33) 4.76.61.52.52 _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Fri Feb 20 07:34:23 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18298 for ; Fri, 20 Feb 2004 07:34:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9qt-0004tQ-0Z for rmt-archive@odin.ietf.org; Fri, 20 Feb 2004 07:33:55 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KCXsxL018804 for rmt-archive@odin.ietf.org; Fri, 20 Feb 2004 07:33:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9qs-0004tD-RP for rmt-web-archive@optimus.ietf.org; Fri, 20 Feb 2004 07:33:54 -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 HAA18273 for ; Fri, 20 Feb 2004 07:33:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au9qs-0002ed-00 for rmt-web-archive@ietf.org; Fri, 20 Feb 2004 07:33:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au9pv-0002b9-00 for rmt-web-archive@ietf.org; Fri, 20 Feb 2004 07:32:56 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Au9p4-0002YO-00 for rmt-web-archive@ietf.org; Fri, 20 Feb 2004 07:32:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9p3-0004j0-Nu; Fri, 20 Feb 2004 07:32:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9ou-0004iK-7z for rmt@optimus.ietf.org; Fri, 20 Feb 2004 07:31:52 -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 HAA18236 for ; Fri, 20 Feb 2004 07:31:50 -0500 (EST) From: Harsh.Mehta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au9ot-0002Wi-00 for rmt@ietf.org; Fri, 20 Feb 2004 07:31:51 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au9nw-0002Sp-00 for rmt@ietf.org; Fri, 20 Feb 2004 07:30:53 -0500 Received: from mgw-x2.nokia.com ([131.228.20.22]) by ietf-mx with esmtp (Exim 4.12) id 1Au9n9-0002QK-00 for rmt@ietf.org; Fri, 20 Feb 2004 07:30:03 -0500 Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1KCU1T17816 for ; Fri, 20 Feb 2004 14:30:01 +0200 (EET) X-Scanned: Fri, 20 Feb 2004 14:29:55 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i1KCTtNA024341 for ; Fri, 20 Feb 2004 14:29:55 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 00weSKbT; Fri, 20 Feb 2004 14:29:55 EET Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1KCTs728766 for ; Fri, 20 Feb 2004 14:29:54 +0200 (EET) Received: from esebe007.NOE.Nokia.com ([172.21.138.47]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 20 Feb 2004 14:29:53 +0200 Received: from trebe006.NOE.Nokia.com ([172.22.232.181]) by esebe007.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 20 Feb 2004 14:29:51 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Rmt] implementations of RMT specs Date: Fri, 20 Feb 2004 14:29:50 +0200 Message-ID: Thread-Topic: [Rmt] implementations of RMT specs Thread-Index: AcP2fKyqdOj268S0RKGWeDhL+nv+lQBMD+OA To: X-OriginalArrivalTime: 20 Feb 2004 12:29:51.0075 (UTC) FILETIME=[3C5EBB30:01C3F7AD] 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi all,=20 The following are available details for existing implementations or = implementations under development at Nokia based on RMT protocols:=20 1. Flexible platform Unix/linux server code is undergoing development = and testing. The code fulfills requirements set out by ALC/LCT and FLUTE = draft version 07. The code is Nokia proprietary (non open-source) and no = public release or contact details are available at this time. Further = details remain confidential.=20 2. Flexible platform Symbian/Unix/Linux code is undergoing development = and testing. The code fulfills the requirements set out by ALC/LCT and = FLUTE draft version 07. The code is Nokia proprietary (non open-sourse) = and no public release or contact details are available at this time. = Further details remain confidential.=20 3. Experimental Linux code that implements ALC/LCT and FLUTE with No = Code Compact FEC for testing the FLUTE protocol, interoperability tests = and as a reference design for product implementations. The code is Nokia = proprietary and not for wide deployment on the General Internet. No = WEBRC or FEC support is intended at this point. The code has undergone = very successful interoperability testing with implementations from the = Tampere University of Technology, INRIA and University of Bremen on both = mboned and multicast. For further information, contact = rod.walsh@nokia.com.=20 Regards, Harsh.=20 > -----Original Message----- > From: rmt-admin@ietf.org [mailto:rmt-admin@ietf.org]On Behalf Of ext > Lorenzo Vicisano > Sent: 19 February, 2004 02:06 > To: rmt@ietf.org > Subject: [Rmt] implementations of RMT specs >=20 >=20 >=20 > Following the recent request from Andrew Marlow, I believe > it would be of general interest to collect a list of publicly > available implementations of RMT protocols. >=20 > If you like to contribute, please post a pointer to your > implementation with a brief description including: >=20 > - the protocol (BB, PI) implemented > - the relevant specs > - is implementation current (if not which draft version > is used) ? > - is the implementation complete ? > - has it been tested for interoperability ? >=20 > It would probably be useful to hear about commercial, non > public-domain implementations too. >=20 > thank you, > Lorenzo >=20 > _______________________________________________ > Rmt mailing list > Rmt@ietf.org > https://www1.ietf.org/mailman/listinfo/rmt >=20 _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Fri Feb 20 07:38:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18518 for ; Fri, 20 Feb 2004 07:38:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9us-0005LG-KO for rmt-archive@odin.ietf.org; Fri, 20 Feb 2004 07:38:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KCc2SV020523 for rmt-archive@odin.ietf.org; Fri, 20 Feb 2004 07:38:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9ur-0005Ks-Ek for rmt-web-archive@optimus.ietf.org; Fri, 20 Feb 2004 07:38:01 -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 HAA18464 for ; Fri, 20 Feb 2004 07:37:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au9uq-0002xk-00 for rmt-web-archive@ietf.org; Fri, 20 Feb 2004 07:38:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au9ts-0002t8-00 for rmt-web-archive@ietf.org; Fri, 20 Feb 2004 07:37:01 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Au9sw-0002pE-00 for rmt-web-archive@ietf.org; Fri, 20 Feb 2004 07:36:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9sw-0004xj-Sj; Fri, 20 Feb 2004 07:36:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9sr-0004wh-PR for rmt@optimus.ietf.org; Fri, 20 Feb 2004 07:35:57 -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 HAA18373 for ; Fri, 20 Feb 2004 07:35:56 -0500 (EST) From: Rod.Walsh@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au9sr-0002o5-00 for rmt@ietf.org; Fri, 20 Feb 2004 07:35:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au9ry-0002ke-00 for rmt@ietf.org; Fri, 20 Feb 2004 07:35:03 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1Au9rB-0002gw-00 for rmt@ietf.org; Fri, 20 Feb 2004 07:34:13 -0500 Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1KCY5K27890; Fri, 20 Feb 2004 14:34:05 +0200 (EET) X-Scanned: Fri, 20 Feb 2004 14:34:02 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i1KCY23Z008868; Fri, 20 Feb 2004 14:34:02 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 00UJay7R; Fri, 20 Feb 2004 14:34:00 EET Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1KCXx702025; Fri, 20 Feb 2004 14:34:00 +0200 (EET) Received: from esebe001.NOE.Nokia.com ([172.21.138.30]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 20 Feb 2004 14:33:59 +0200 Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 20 Feb 2004 14:33:59 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Rmt] agenda items for 59th IETF Date: Fri, 20 Feb 2004 14:33:59 +0200 Message-ID: Thread-Topic: [Rmt] agenda items for 59th IETF Thread-Index: AcP1vmLeM4Co8ragT66gNv8pJ4VV+gB7xeOw To: , X-OriginalArrivalTime: 20 Feb 2004 12:33:59.0409 (UTC) FILETIME=[D0637E10:01C3F7AD] 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: , 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,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi Lorenzo I can give a 5 minute update on FLUTE (or you could handle it in this = RMT Status Update at the start :) There has been progress with both FLUTE interop and the related ID - do = you want to include this in the compiled "Implementations of RMT Specs" = slot? Cheers, Rod. -----Original Message----- From: rmt-admin@ietf.org [mailto:rmt-admin@ietf.org]On Behalf Of ext Lorenzo Vicisano Sent: Wednesday, February 18, 2004 3:23 AM To: rmt@ietf.org Subject: [Rmt] agenda items for 59th IETF If you have discussion items that you would like to include in the agenda please let us know. thank you, the chairs. _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Fri Feb 20 07:42:27 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18666 for ; Fri, 20 Feb 2004 07:42:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9yf-0005g5-Dy for rmt-archive@odin.ietf.org; Fri, 20 Feb 2004 07:41:57 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KCfvps021819 for rmt-archive@odin.ietf.org; Fri, 20 Feb 2004 07:41:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9yf-0005fq-9q for rmt-web-archive@optimus.ietf.org; Fri, 20 Feb 2004 07:41:57 -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 HAA18636 for ; Fri, 20 Feb 2004 07:41:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au9ye-0003D6-00 for rmt-web-archive@ietf.org; Fri, 20 Feb 2004 07:41:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au9xh-00039I-00 for rmt-web-archive@ietf.org; Fri, 20 Feb 2004 07:40:57 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Au9wu-00036K-00 for rmt-web-archive@ietf.org; Fri, 20 Feb 2004 07:40:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9wq-0005UL-1Y; Fri, 20 Feb 2004 07:40:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au9vo-0005QF-07 for rmt@optimus.ietf.org; Fri, 20 Feb 2004 07:39:00 -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 HAA18577 for ; Fri, 20 Feb 2004 07:38:58 -0500 (EST) From: Rod.Walsh@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au9vn-00032Y-00 for rmt@ietf.org; Fri, 20 Feb 2004 07:38:59 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au9v3-0002zc-00 for rmt@ietf.org; Fri, 20 Feb 2004 07:38:14 -0500 Received: from mgw-x3.nokia.com ([131.228.20.26]) by ietf-mx with esmtp (Exim 4.12) id 1Au9uQ-0002us-00 for rmt@ietf.org; Fri, 20 Feb 2004 07:37:34 -0500 Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1KCapS00915 for ; Fri, 20 Feb 2004 14:37:22 +0200 (EET) X-Scanned: Fri, 20 Feb 2004 14:36:07 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i1KCa7qF017646 for ; Fri, 20 Feb 2004 14:36:07 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks003.ntc.nokia.com 00Chimhs; Fri, 20 Feb 2004 14:36:06 EET Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1KCa5703640 for ; Fri, 20 Feb 2004 14:36:05 +0200 (EET) Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 20 Feb 2004 14:36:04 +0200 Received: from esebe016.NOE.Nokia.com ([172.21.138.55]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 20 Feb 2004 14:36:04 +0200 Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe016.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 20 Feb 2004 14:36:03 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Rmt] implementations of RMT specs Date: Fri, 20 Feb 2004 14:36:03 +0200 Message-ID: Thread-Topic: [Rmt] implementations of RMT specs Thread-Index: AcP2fKyqdOj268S0RKGWeDhL+nv+lQBMD+OAAAA71dA= To: , X-OriginalArrivalTime: 20 Feb 2004 12:36:03.0952 (UTC) FILETIME=[1A9F3F00:01C3F7AE] 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable the email's great but you _must_ send these for internal review first: minimum of Rod & = Toni for FLUTE. Rod. -----Original Message----- From: rmt-admin@ietf.org [mailto:rmt-admin@ietf.org]On Behalf Of ext Harsh.Mehta@nokia.com Sent: Friday, February 20, 2004 2:30 PM To: rmt@ietf.org Subject: RE: [Rmt] implementations of RMT specs Hi all,=20 The following are available details for existing implementations or = implementations under development at Nokia based on RMT protocols:=20 1. Flexible platform Unix/linux server code is undergoing development = and testing. The code fulfills requirements set out by ALC/LCT and FLUTE = draft version 07. The code is Nokia proprietary (non open-source) and no = public release or contact details are available at this time. Further = details remain confidential.=20 2. Flexible platform Symbian/Unix/Linux code is undergoing development = and testing. The code fulfills the requirements set out by ALC/LCT and = FLUTE draft version 07. The code is Nokia proprietary (non open-sourse) = and no public release or contact details are available at this time. = Further details remain confidential.=20 3. Experimental Linux code that implements ALC/LCT and FLUTE with No = Code Compact FEC for testing the FLUTE protocol, interoperability tests = and as a reference design for product implementations. The code is Nokia = proprietary and not for wide deployment on the General Internet. No = WEBRC or FEC support is intended at this point. The code has undergone = very successful interoperability testing with implementations from the = Tampere University of Technology, INRIA and University of Bremen on both = mboned and multicast. For further information, contact = rod.walsh@nokia.com.=20 Regards, Harsh.=20 > -----Original Message----- > From: rmt-admin@ietf.org [mailto:rmt-admin@ietf.org]On Behalf Of ext > Lorenzo Vicisano > Sent: 19 February, 2004 02:06 > To: rmt@ietf.org > Subject: [Rmt] implementations of RMT specs >=20 >=20 >=20 > Following the recent request from Andrew Marlow, I believe > it would be of general interest to collect a list of publicly > available implementations of RMT protocols. >=20 > If you like to contribute, please post a pointer to your > implementation with a brief description including: >=20 > - the protocol (BB, PI) implemented > - the relevant specs > - is implementation current (if not which draft version > is used) ? > - is the implementation complete ? > - has it been tested for interoperability ? >=20 > It would probably be useful to hear about commercial, non > public-domain implementations too. >=20 > thank you, > Lorenzo >=20 > _______________________________________________ > Rmt mailing list > Rmt@ietf.org > https://www1.ietf.org/mailman/listinfo/rmt >=20 _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Mon Feb 23 02:24:33 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11126 for ; Mon, 23 Feb 2004 02:24:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvARh-0003zk-IJ for rmt-archive@odin.ietf.org; Mon, 23 Feb 2004 02:24:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1N7O5Ka015270 for rmt-archive@odin.ietf.org; Mon, 23 Feb 2004 02:24:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvARe-0003xe-JC for rmt-web-archive@optimus.ietf.org; Mon, 23 Feb 2004 02:24:02 -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 CAA11065 for ; Mon, 23 Feb 2004 02:23:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvARa-0000Xz-00 for rmt-web-archive@ietf.org; Mon, 23 Feb 2004 02:23:58 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvAQd-0000Ua-00 for rmt-web-archive@ietf.org; Mon, 23 Feb 2004 02:23:00 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AvAPk-0000RZ-00 for rmt-web-archive@ietf.org; Mon, 23 Feb 2004 02:22:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvAPi-0003Sy-MZ; Mon, 23 Feb 2004 02:22:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvAOi-0003FS-VK for rmt@optimus.ietf.org; Mon, 23 Feb 2004 02:21:00 -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 CAA10832 for ; Mon, 23 Feb 2004 02:20:57 -0500 (EST) From: Rod.Walsh@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvAOf-0000OF-00 for rmt@ietf.org; Mon, 23 Feb 2004 02:20:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvANi-0000M4-00 for rmt@ietf.org; Mon, 23 Feb 2004 02:19:58 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1AvAN1-0000Jq-00 for rmt@ietf.org; Mon, 23 Feb 2004 02:19:16 -0500 Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1N7JFH00217 for ; Mon, 23 Feb 2004 09:19:15 +0200 (EET) X-Scanned: Mon, 23 Feb 2004 09:19:03 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i1N7J35n027205 for ; Mon, 23 Feb 2004 09:19:03 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks001.ntc.nokia.com 00nd0wPR; Mon, 23 Feb 2004 09:19:02 EET Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1N7J1702177 for ; Mon, 23 Feb 2004 09:19:01 +0200 (EET) Received: from esebe017.NOE.Nokia.com ([172.21.138.56]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 23 Feb 2004 09:19:00 +0200 Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe017.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 23 Feb 2004 09:19:00 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Rmt] implementations of RMT specs Date: Mon, 23 Feb 2004 09:18:58 +0200 Message-ID: Thread-Topic: [Rmt] implementations of RMT specs Thread-Index: AcP2fKyqdOj268S0RKGWeDhL+nv+lQBMD+OAAAA71dAAi54vIA== To: X-OriginalArrivalTime: 23 Feb 2004 07:19:00.0090 (UTC) FILETIME=[4EC185A0:01C3F9DD] 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: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Oops! Sorry about occupying your inboxes with a run-away internal mail = (and the follow-up too :) Anyway as Harsh's email said, there's running FLUTE code in Nokia too. = The TUT, INRIA, Nokia & Bremen interop has already played a very = successful role in tightening up the FLUTE spec so I'd recommend this = approach to anyone. Cheers, Rod. --- The following are available details for existing implementations or = implementations under development at Nokia based on RMT protocols:=20 1. Flexible platform Unix/linux server code is undergoing development = and testing. The code fulfills requirements set out by ALC/LCT and FLUTE = draft version 07. The code is Nokia proprietary (non open-source) and no = public release or contact details are available at this time. Further = details remain confidential.=20 2. Flexible platform Symbian/Unix/Linux code is undergoing development = and testing. The code fulfills the requirements set out by ALC/LCT and = FLUTE draft version 07. The code is Nokia proprietary (non open-sourse) = and no public release or contact details are available at this time. = Further details remain confidential.=20 3. Experimental Linux code that implements ALC/LCT and FLUTE with No = Code Compact FEC for testing the FLUTE protocol, interoperability tests = and as a reference design for product implementations. The code is Nokia = proprietary and not for wide deployment on the General Internet. No = WEBRC or FEC support is intended at this point. The code has undergone = very successful interoperability testing with implementations from the = Tampere University of Technology, INRIA and University of Bremen on both = mboned and multicast. For further information, contact = rod.walsh@nokia.com.=20 Regards, Harsh.=20 _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Mon Feb 23 09:17:03 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26820 for ; Mon, 23 Feb 2004 09:17:03 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvGsr-0004FX-RT for rmt-archive@odin.ietf.org; Mon, 23 Feb 2004 09:16:35 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1NEGXmG016329 for rmt-archive@odin.ietf.org; Mon, 23 Feb 2004 09:16:33 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvGsr-0004FI-Nt for rmt-web-archive@optimus.ietf.org; Mon, 23 Feb 2004 09:16:33 -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 JAA26799 for ; Mon, 23 Feb 2004 09:16:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvGsp-0006CB-00 for rmt-web-archive@ietf.org; Mon, 23 Feb 2004 09:16:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvGrn-00067I-00 for rmt-web-archive@ietf.org; Mon, 23 Feb 2004 09:15:28 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AvGrQ-00062p-00 for rmt-web-archive@ietf.org; Mon, 23 Feb 2004 09:15:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvGrQ-00047g-Hp; Mon, 23 Feb 2004 09:15:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvGqw-000469-8o for rmt@optimus.ietf.org; Mon, 23 Feb 2004 09:14:34 -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 JAA26687 for ; Mon, 23 Feb 2004 09:14:31 -0500 (EST) From: Harsh.Mehta@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvGqu-00061c-00 for rmt@ietf.org; Mon, 23 Feb 2004 09:14:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvGq7-0005wJ-00 for rmt@ietf.org; Mon, 23 Feb 2004 09:13:44 -0500 Received: from mgw-x3.nokia.com ([131.228.20.26]) by ietf-mx with esmtp (Exim 4.12) id 1AvGp4-0005po-00 for rmt@ietf.org; Mon, 23 Feb 2004 09:12:38 -0500 Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1NEBvS06766 for ; Mon, 23 Feb 2004 16:12:27 +0200 (EET) X-Scanned: Mon, 23 Feb 2004 16:11:40 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i1NEBe4Q005096 for ; Mon, 23 Feb 2004 16:11:40 +0200 Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks001.ntc.nokia.com 00OpPNt5; Mon, 23 Feb 2004 16:11:38 EET Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1NEBRO24295 for ; Mon, 23 Feb 2004 16:11:27 +0200 (EET) Received: from esebe007.NOE.Nokia.com ([172.21.138.47]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 23 Feb 2004 16:10:43 +0200 Received: from trebe006.NOE.Nokia.com ([172.22.232.181]) by esebe007.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 23 Feb 2004 16:10:42 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 23 Feb 2004 16:10:42 +0200 Message-ID: Thread-Topic: Internet-Draft: FLUTE IneroperabilityTesting Guidelines ver 01 Thread-Index: AcP6FtKOHe6RnqO2QEyLpOV/fXB72A== To: X-OriginalArrivalTime: 23 Feb 2004 14:10:42.0874 (UTC) FILETIME=[D2C339A0:01C3FA16] Content-Transfer-Encoding: quoted-printable Subject: [Rmt] Internet-Draft: FLUTE IneroperabilityTesting Guidelines ver 01 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.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi All,=20 A new version of the Internet-draft on "FLUTE Interoperability Testing = Guidelines" is now available:=20 http://www.ietf.org/internet-drafts/draft-mehta-rmt-flute-iop-01.txt All comments are very welcome.=20 Regards,=20 Harsh Mehta.=20 _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Thu Feb 26 14:47:18 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05068 for ; Thu, 26 Feb 2004 14:47:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRT7-0005Fb-VF for rmt-archive@odin.ietf.org; Thu, 26 Feb 2004 14:46:51 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1QJknI3020181 for rmt-archive@odin.ietf.org; Thu, 26 Feb 2004 14:46:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRT7-0005FQ-IE for rmt-web-archive@optimus.ietf.org; Thu, 26 Feb 2004 14:46:49 -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 OAA04970 for ; Thu, 26 Feb 2004 14:46:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwRT4-0004Tp-00 for rmt-web-archive@ietf.org; Thu, 26 Feb 2004 14:46:46 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwRSA-0004Oc-00 for rmt-web-archive@ietf.org; Thu, 26 Feb 2004 14:45:51 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AwRRP-0004JK-00 for rmt-web-archive@ietf.org; Thu, 26 Feb 2004 14:45:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRRP-00050z-BS; Thu, 26 Feb 2004 14:45:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRRB-0004zq-58 for rmt@optimus.ietf.org; Thu, 26 Feb 2004 14:44:49 -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 OAA04893 for ; Thu, 26 Feb 2004 14:44:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwRR8-0004Hi-00 for rmt@ietf.org; Thu, 26 Feb 2004 14:44:46 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwRQE-0004CR-00 for rmt@ietf.org; Thu, 26 Feb 2004 14:43:51 -0500 Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AwRPY-000479-00; Thu, 26 Feb 2004 14:43:08 -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 i1QJh4k01712; Thu, 26 Feb 2004 11:43:06 -0800 (PST) Message-Id: <200402261943.i1QJh4k01712@gamma.isi.edu> To: IETF-Announce: ; 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: Thu, 26 Feb 2004 11:43:04 -0800 Subject: [Rmt] RFC 3695 on Compact Forward Error Correction (FEC) Schemes 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=-1.6 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3695 Title: Compact Forward Error Correction (FEC) Schemes Author(s): M. Luby, L. Vicisano Status: Experimental Date: February 2004 Mailbox: luby@digitalfountain.com, lorenzo@cisco.com Pages: 13 Characters: 32012 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rmt-bb-fec-supp-compact-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3695.txt This document introduces some Forward Error Correction (FEC) schemes that supplement the FEC schemes described in RFC 3452. The primary benefits of these additional FEC schemes are that they are designed for reliable bulk delivery of large objects using a more compact FEC Payload ID, and they can be used to sequentially deliver blocks of an object of indeterminate length. Thus, they more flexibly support different delivery models with less packet header overhead. This document also describes the Fully-Specified FEC scheme corresponding to FEC Encoding ID 0. This Fully-Specified FEC scheme requires no FEC coding and is introduced primarily to allow simple interoperability testing between different implementations of protocol instantiations that use the FEC building block. 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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040226114057.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3695 --OtherAccess Content-Type: Message/External-body; name="rfc3695.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040226114057.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From exim@www1.ietf.org Thu Feb 26 14:47:18 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05070 for ; Thu, 26 Feb 2004 14:47:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRT8-0005Fx-Bj for rmt-archive@odin.ietf.org; Thu, 26 Feb 2004 14:46:51 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1QJko3I020199 for rmt-archive@odin.ietf.org; Thu, 26 Feb 2004 14:46:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRT8-0005Fi-8Q for rmt-web-archive@optimus.ietf.org; Thu, 26 Feb 2004 14:46:50 -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 OAA04975 for ; Thu, 26 Feb 2004 14:46:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwRT5-0004Tu-00 for rmt-web-archive@ietf.org; Thu, 26 Feb 2004 14:46:47 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwRSB-0004Ok-00 for rmt-web-archive@ietf.org; Thu, 26 Feb 2004 14:45:52 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AwRRQ-0004JL-00 for rmt-web-archive@ietf.org; Thu, 26 Feb 2004 14:45:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRRN-00050f-Mv; Thu, 26 Feb 2004 14:45:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRR9-0004zf-7a for rmt@optimus.ietf.org; Thu, 26 Feb 2004 14:44:47 -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 OAA04883 for ; Thu, 26 Feb 2004 14:44:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwRR6-0004HT-00 for rmt@ietf.org; Thu, 26 Feb 2004 14:44:44 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwRQC-0004C4-00 for rmt@ietf.org; Thu, 26 Feb 2004 14:43:49 -0500 Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AwRPX-000476-00; Thu, 26 Feb 2004 14:43:08 -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 i1QJh5k01749; Thu, 26 Feb 2004 11:43:06 -0800 (PST) Message-Id: <200402261943.i1QJh5k01749@gamma.isi.edu> To: IETF-Announce: ; 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: Thu, 26 Feb 2004 11:43:05 -0800 Subject: [Rmt] RFC 3695 on Compact Forward Error Correction (FEC) Schemes 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=-1.6 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3695 Title: Compact Forward Error Correction (FEC) Schemes Author(s): M. Luby, L. Vicisano Status: Experimental Date: February 2004 Mailbox: luby@digitalfountain.com, lorenzo@cisco.com Pages: 13 Characters: 32012 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rmt-bb-fec-supp-compact-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3695.txt This document introduces some Forward Error Correction (FEC) schemes that supplement the FEC schemes described in RFC 3452. The primary benefits of these additional FEC schemes are that they are designed for reliable bulk delivery of large objects using a more compact FEC Payload ID, and they can be used to sequentially deliver blocks of an object of indeterminate length. Thus, they more flexibly support different delivery models with less packet header overhead. This document also describes the Fully-Specified FEC scheme corresponding to FEC Encoding ID 0. This Fully-Specified FEC scheme requires no FEC coding and is introduced primarily to allow simple interoperability testing between different implementations of protocol instantiations that use the FEC building block. 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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040226114057.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3695 --OtherAccess Content-Type: Message/External-body; name="rfc3695.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040226114057.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt