From exim@www1.ietf.org  Mon Mar  1 20:38: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 UAA20443
	for <rmt-archive@odin.ietf.org>; Mon, 1 Mar 2004 20:38: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 1AxyrF-00087s-WB
	for rmt-archive@odin.ietf.org; Mon, 01 Mar 2004 20:38:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i221c5ct031204
	for rmt-archive@odin.ietf.org; Mon, 1 Mar 2004 20:38:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxyrF-00086y-DN
	for rmt-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 20:38: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 UAA20408
	for <rmt-web-archive@ietf.org>; Mon, 1 Mar 2004 20:38:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxyrC-00012E-00
	for rmt-web-archive@ietf.org; Mon, 01 Mar 2004 20:38:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxyqD-0000uc-00
	for rmt-web-archive@ietf.org; Mon, 01 Mar 2004 20:37:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxypE-0000l2-00
	for rmt-web-archive@ietf.org; Mon, 01 Mar 2004 20:36:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxypF-0007o9-IS; Mon, 01 Mar 2004 20:36:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxyoW-0007mp-4Y
	for rmt@optimus.ietf.org; Mon, 01 Mar 2004 20:35:16 -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 UAA20300
	for <rmt@ietf.org>; Mon, 1 Mar 2004 20:35:12 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxyoT-0000hN-00
	for rmt@ietf.org; Mon, 01 Mar 2004 20:35:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axync-0000aX-00
	for rmt@ietf.org; Mon, 01 Mar 2004 20:34:21 -0500
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axymz-0000T5-00
	for rmt@ietf.org; Mon, 01 Mar 2004 20:33:41 -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 i221Xe726630
	for <rmt@ietf.org>; Tue, 2 Mar 2004 03:33:40 +0200 (EET)
X-Scanned: Tue, 2 Mar 2004 03:33:36 +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 i221XaUw020131
	for <rmt@ietf.org>; Tue, 2 Mar 2004 03:33:36 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00nq9sjy; Tue, 02 Mar 2004 03:33:34 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 i221XYO20323
	for <rmt@ietf.org>; Tue, 2 Mar 2004 03:33:34 +0200 (EET)
Received: from esebe012.NOE.Nokia.com ([172.21.138.51]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Tue, 2 Mar 2004 03:33:34 +0200
Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe012.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Tue, 2 Mar 2004 03:33:34 +0200
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Tue, 2 Mar 2004 03:33:33 +0200
Message-ID: <D0299AFF29E01E478321564030AD690953949D@trebe003.europe.nokia.com>
Thread-Topic: 59th IETF - RMT Cancelled
Thread-Index: AcP/L4RsKqIyG2C4Thu4UDRS6N2wLQAxtHgQ
To: <rmt@ietf.org>
X-OriginalArrivalTime: 02 Mar 2004 01:33:34.0578 (UTC) FILETIME=[60B15D20:01C3FFF6]
Content-Transfer-Encoding: quoted-printable
Subject: [Rmt] FW: 59th IETF - RMT Cancelled
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: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=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

FYI...

-----Original Message-----
From: owner-ietf-announce@ietf.org
[mailto:owner-ietf-announce@ietf.org]On Behalf Of ext agenda@ietf.org
Sent: Monday, March 01, 2004 10:33 AM
Subject: 59th IETF - RMT Cancelled


The RMT meeting scheduled for Tuesday at 1700-1800 has
been cancelled.


_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From exim@www1.ietf.org  Mon Mar  1 21:25:02 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 VAA23781
	for <rmt-archive@odin.ietf.org>; Mon, 1 Mar 2004 21:25:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzaG-0006tH-Qj
	for rmt-archive@odin.ietf.org; Mon, 01 Mar 2004 21:24:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i222Oa9S026487
	for rmt-archive@odin.ietf.org; Mon, 1 Mar 2004 21:24:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzaG-0006t8-NZ
	for rmt-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 21:24: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 VAA23707
	for <rmt-web-archive@ietf.org>; Mon, 1 Mar 2004 21:24:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzaD-0007O0-00
	for rmt-web-archive@ietf.org; Mon, 01 Mar 2004 21:24:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzZP-0007EW-00
	for rmt-web-archive@ietf.org; Mon, 01 Mar 2004 21:23:44 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzYg-00073u-00
	for rmt-web-archive@ietf.org; Mon, 01 Mar 2004 21:22:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzYi-0006kD-9w; Mon, 01 Mar 2004 21:23:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzYB-0006fg-I9
	for rmt@optimus.ietf.org; Mon, 01 Mar 2004 21:22:27 -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 VAA23526
	for <rmt@ietf.org>; Mon, 1 Mar 2004 21:22:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzY8-00071N-00
	for rmt@ietf.org; Mon, 01 Mar 2004 21:22:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzXE-0006ss-00
	for rmt@ietf.org; Mon, 01 Mar 2004 21:21:28 -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 1AxzWI-0006cj-00
	for rmt@ietf.org; Mon, 01 Mar 2004 21:20:30 -0500
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i222JwuA000360;
	Mon, 1 Mar 2004 18:19:58 -0800 (PST)
Received: (from lorenzo@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id SAA23024;
	Mon, 1 Mar 2004 18:19:58 -0800 (PST)
Date: Mon, 1 Mar 2004 18:19:57 -0800
From: Lorenzo Vicisano <lorenzo@cisco.com>
To: Rod.Walsh@nokia.com
Cc: rmt@ietf.org
Subject: Re: [Rmt] FW: 59th IETF - RMT Cancelled
Message-ID: <20040301181957.C12980@cisco.com>
References: <D0299AFF29E01E478321564030AD690953949D@trebe003.europe.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D0299AFF29E01E478321564030AD690953949D@trebe003.europe.nokia.com>
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: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=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

The reason for this is the lack of any agenda item
of general interest.

The WG work is pretty much on track and most
of our outstanding drafts are either under IESG
review or in the final stage pre-RFC publication.

The only exeptions are:

draft-ietf-rmt-bb-pgmcc
draft-ietf-rmt-bb-tfmcc

that are currently expired. The last thime I check on these,
they were ready for publication or close to it.

	thanks,
	Lorenzo



On Tue, Mar 02, 2004 at 03:33:33AM +0200, Rod.Walsh@nokia.com wrote:
> FYI...
> 
> -----Original Message-----
> From: owner-ietf-announce@ietf.org
> [mailto:owner-ietf-announce@ietf.org]On Behalf Of ext agenda@ietf.org
> Sent: Monday, March 01, 2004 10:33 AM
> Subject: 59th IETF - RMT Cancelled
> 
> 
> The RMT meeting scheduled for Tuesday at 1700-1800 has
> been cancelled.
> 
> 
> _______________________________________________
> 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  Tue Mar 30 17:41:13 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 RAA18937
	for <rmt-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:41:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjk-0006Xa-EA
	for rmt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1R9QFeb003810
	for rmt-archive@odin.ietf.org; Fri, 27 Feb 2004 04:26:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AweG6-0000zN-O5
	for rmt-web-archive@optimus.ietf.org; Fri, 27 Feb 2004 04:26:14 -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 EAA21883
	for <rmt-web-archive@ietf.org>; Fri, 27 Feb 2004 04:26:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AweG3-000277-00
	for rmt-web-archive@ietf.org; Fri, 27 Feb 2004 04:26:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AweF4-0001wD-00
	for rmt-web-archive@ietf.org; Fri, 27 Feb 2004 04:25:11 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AweEA-0001nK-00
	for rmt-web-archive@ietf.org; Fri, 27 Feb 2004 04:24:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AweE5-0000Gf-2W; Fri, 27 Feb 2004 04:24:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AwdLs-0005h8-Nn
	for rmt@optimus.ietf.org; Fri, 27 Feb 2004 03:28: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 DAA20405
	for <rmt@ietf.org>; Fri, 27 Feb 2004 03:28:06 -0500 (EST)
From: Harsh.Mehta@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwdLq-0004Nm-00
	for rmt@ietf.org; Fri, 27 Feb 2004 03:28:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwdKu-0004Ju-00
	for rmt@ietf.org; Fri, 27 Feb 2004 03:27:09 -0500
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwdKg-0004FZ-00
	for rmt@ietf.org; Fri, 27 Feb 2004 03:26:54 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1R8Qtt13042
	for <rmt@ietf.org>; Fri, 27 Feb 2004 10:26:55 +0200 (EET)
X-Scanned: Fri, 27 Feb 2004 10:26:48 +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 i1R8QmmH010109
	for <rmt@ietf.org>; Fri, 27 Feb 2004 10:26:48 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00YHE4eh; Fri, 27 Feb 2004 10:26:46 EET
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1R8Qk704734
	for <rmt@ietf.org>; Fri, 27 Feb 2004 10:26:46 +0200 (EET)
Received: from esebe014.NOE.Nokia.com ([172.21.138.53]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Fri, 27 Feb 2004 10:26:46 +0200
Received: from trebe006.NOE.Nokia.com ([172.22.232.181]) by esebe014.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 27 Feb 2004 10:26:45 +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: Fri, 27 Feb 2004 10:26:44 +0200
Message-ID: <C7A7BDCB8B7122488C76018140CB5BBE011C756D@trebe006.europe.nokia.com>
Thread-Topic: FLUTE Interoperability tests
Thread-Index: AcP9C27sPC7F6ebJQT6UhMYMIZujCA==
To: <rmt@ietf.org>
X-OriginalArrivalTime: 27 Feb 2004 08:26:45.0768 (UTC) FILETIME=[6FBDC080:01C3FD0B]
Content-Transfer-Encoding: quoted-printable
Subject: [Rmt] FLUTE Interoperability tests
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: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=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
>=20
> For those interested, this is a status update on the Interoperability =
tests for FLUTE that we have done in the past few months.=20
>=20
> The tests started with implementations from Tampere University of =
Technology (TUT), INRIA and Nokia. University of Bremen also joined in =
later. The tests have been largely based on the FLUTE Interoperabiltiy =
Testing Guidelines Internet-draft =
http://www.ietf.org/internet-drafts/draft-mehta-rmt-flute-iop-01.txt. As =
recommended in the I-D, the MD5 checksum was used to check correctness =
of transmitted files.=20
>=20
> In general, all the tests were very successful and a high level of =
interoperability was achieved. It should be noted that all the above =
implementations are capable of using FLUTE on both unicast and =
multicast. Here are some more details:
>=20
> 1. The first set of tests conducted were one-on-one unicast tests =
among the implementations from INRIA, TUT and Nokia. These tests were =
based on sections 5, 6, 7 and 10 of the Interoperability I-D. The basic =
tests conducted were to establish the proper operation of the =
implementations with regard to interpreting the FDT (File Delivery =
Table) defined by FLUTE. Interoperability was further tested with the =
transmission of single files, multiple files, and multiple large files =
within a session. All the tests were conducted using no Congestion =
Control and COMPACT NO CODE FEC (NULL FEC).=20
>=20
> 2. A further set of unicast one-on-one tests were conducted between =
four implementations (the University of Bremem implementation also =
became involved). The tests were similar to those in (1) above. Tests =
corresponding to section 5, 6, 7, 8 and 10 of the I-D were carried out.
>=20
> 3. A series of multicast tests were conducted using mbone. These tests =
involved a sender from each implementation sending to multiple =
implementations. The tests were on the lines of sections 5, 6, 7, 8 and =
10 of the Internet-draft, using NULL FEC and no RMT-based congestion =
control.=20
>=20
> 4. A series of advanced multicast tests were done among the TUT, INRIA =
and University of Bremen implementations. These were done using (i) Reed =
Solomon FEC 129 (ii) Multiple layers (RLC). The implementations were =
tested for interoperability with regard to the File Delivery Table, =
reception of single and multiple files of various sizes withing a single =
session and the correct reception and interpretation of FLUTE and file =
data.=20
>=20
(Since the implementers have sent details of their implementations and =
contacts to the RMT list I'm not repeating them here).

Regards,=20
Harsh Mehta.=20


_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From exim@www1.ietf.org  Tue Mar 30 18:04:45 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 SAA24149
	for <rmt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:04:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjY-0006Xa-GB
	for rmt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OAs752012762
	for rmt-archive@odin.ietf.org; Fri, 24 Oct 2003 06:54:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACza2-0003Jh-6j
	for rmt-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 06:54:06 -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 GAA25144
	for <rmt-web-archive@ietf.org>; Fri, 24 Oct 2003 06:53:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACzZw-0001Tq-00
	for rmt-web-archive@ietf.org; Fri, 24 Oct 2003 06:54:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACzZv-0001Tm-00
	for rmt-web-archive@ietf.org; Fri, 24 Oct 2003 06:53:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACzZy-0003JA-GJ; Fri, 24 Oct 2003 06:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACzZU-0003ES-Om
	for rmt@optimus.ietf.org; Fri, 24 Oct 2003 06:53:33 -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 GAA25104
	for <rmt@ietf.org>; Fri, 24 Oct 2003 06:53:19 -0400 (EDT)
From: Rod.Walsh@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACzZQ-0001Sd-00
	for rmt@ietf.org; Fri, 24 Oct 2003 06:53:28 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACzZP-0001SU-00
	for rmt@ietf.org; Fri, 24 Oct 2003 06:53:27 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9OArRI27582
	for <rmt@ietf.org>; Fri, 24 Oct 2003 13:53:27 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T657ac7a52bac158f21082@esvir01nok.ntc.nokia.com>;
 Fri, 24 Oct 2003 13:53:21 +0300
Received: from esebe012.NOE.Nokia.com ([172.21.138.51]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 24 Oct 2003 13:53:20 +0300
Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe012.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 24 Oct 2003 13:53:09 +0300
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Fri, 24 Oct 2003 13:53:04 +0300
Message-ID: <2BF0AD29BC31FE46B7887732114404310357E6DB@trebe003.europe.nokia.com>
Thread-Topic: [Rmt] Extended attributes
Thread-Index: AcOKiTeO9H5fXbS+R6yOq4FmSPVkOwDtkCogAvWMMkA=
To: <rmt@ietf.org>
Cc: <toni.paila@nokia.com>, <luby@digitalfountain.com>,
        <rami.lehtonen@teliasonera.com>, <vincent.roca@inrialpes.fr>
X-OriginalArrivalTime: 24 Oct 2003 10:53:09.0253 (UTC) FILETIME=[030EB350:01C39A1D]
Content-Transfer-Encoding: quoted-printable
Subject: [Rmt] flute comments
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: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi All

A few of us have been implementing flute and have performed some initial =
interoperability tests. We actually got three separate implementations =
working together in a single day, so I that means the FLUTE spec is =
splendid, but I'm writing to ask for improvements rather than to praise =
:) We spotted a few issues that would be helpful to deal with in the =
spec - clarifications to make a coder's life that bit easier.

All of these are about making the spec nicer and we think it can all be =
handled in in editorial changes after last call (i.e. if these delay =
last call, we'd be amazed).

1. A flag usage

ALC allows packets without TOI, which is useful for end of session (A =
flag) no payload packets. FLUTE does not allow this - just an oversight.

FLUTE-02 speficication says (Page 6, 3th paragraph): "* The TOI field =
MUST be used in ALC/LCT packets"

It can be changed to "* When sending an empty A flag packet the use of =
TOI is optional, otherwise the TOI field MUST be used in ALC/LCT =
packets"

It's a pretty triavial change, but would allow this ALC feature to be =
also usable for FLUTE.


2. Default SBN & ESI lengths

ALC gives an example with FEC ID 128 (SBN & ESI lengths are 4 bytes =
each). In our tests we made null fec - fec id 0 - the default, so 2 byte =
lengths in each. The specifications are correct, but two coders =
seperately overlooked this when adding FLUTE on top of ALC. It would be =
helpful to warn unwarey coders to take care with these lengths and check =
the specifics of the fec codes used - and if that doesn't prevent =
someone tripping up, they'll have to find out through the hex dumps :)

3. Expires time insufficiently described

Some improvements to the FDT Instance expiration time information (3.3 =
bullet 7 of ID_02) would be:
(1) provide a reference to the NTP spec
(2) NTP can be 64 bit, so you mean the most significant half - the other =
32bits are for fractions of a second. This needs a mention "...value in =
seconds (note, NTP also offers an additional 32 bits to describe =
fractions of a second, these are not used for FLUTE)"
(3) wrap around will occur (2034?) so prehaps an advisory would be =
helpful like "Wrap-around of the 32 bit time is to be handled according =
to NTP [NTP]. For the purpose of identifying past and future times, it =
is recommended that 2^31 integers in advance of the current time are =
interpreted as future times and (2^31)-1 integers preceeding the current =
time are interpreted as past. For systems where sub-second =
synchronisation accuracy of clocks is not feasible, a system jitter of =
24 hours (86400 seconds) may be used (as jitter tolerence) to avoid the =
situation where there is ambiguity whether the time is past or future. =
In this case some times would not be reliable: before (current_time - =
(2^32)-1 + (86400/2)); and after (current_time + 2^32-1 - (86400/2))."
(4) Sometimes you want to say "never expires". Adding this informational =
text would be helpful: "To factilitate something close to a 'never =
expires' option, a time long into the future, e.g. 2^30 ahead of the =
current time, may be used. As this represents many years into the =
future, this specification assumes that it is sufficient approxomation =
to 'never expires'."  Note, other alternatives come with problems that =
aren't worth solving (e.g. make the expires field optional, not allow =
'never expires', have a special 'key word' instead of a number (zero =
would be a bad idea as it is a valid NTP time)).

So add [NTP], and add to the end of that bullet "(Note, NTP also offers =
an additional 32 bits to describe fractions of a second, these are not =
used for FLUTE). To factilitate something close to a 'never expires' =
option, a time long into the future, e.g. 2^30 ahead of the current =
time, may be used. As this represents many years into the future, this =
specification assumes that it is sufficient approxomation to 'never =
expires'. Wrap-around of the 32 bit time is to be handled according to =
NTP [NTP]. Wrap-around of the 32 bit time is to be handled according to =
NTP [NTP]. For the purpose of identifying past and future times, it is =
recommended that 2^31 integers in advance of the current time are =
interpreted as future times and (2^31)-1 integers preceeding the current =
time are interpreted as past. For systems where sub-second =
synchronisation accuracy of clocks is not feasible, a system jitter of =
24 hours (86400 seconds) may be used (as jitter tolerence) to avoid the =
situation where there is ambiguity whether the time is past or future. =
In this case some times would not be reliable: before (current_time - =
(2^32)-1 + (86400/2)); and after (current_time + 2^32-1 - (86400/2))."

Note, this addition deals with rare and unusual problems so may seem =
overly detailed or complex compared with the simplicity of the problem. =
Maybe it would be added as an informational appendix instead?

4. Modifying a FDT Instance

There are some problems with allowing modified FDT Instances as opposed =
to "complementing". for complementing it, you are only adding (optional) =
info which does not inhibit (or confuse) reception. For modifying, you =
can do anything, e.g. change the MD5 checksum. There may be a use case =
for this but as far as I can see it is much simpler just to force a TOI =
change if reception-critical parameters change. The spec fix to this is =
in 3.3 bullet 6:
change "..., not to include it, complement the description or modify the =
description. In the last..." to "..., not to include it or complement =
the description."

If someone really needs to keep the same TOI, some limitations related =
to modifying the description could be made instead, but we have all =
sorts of exceptions about updating all receivers, not sending packets =
from two fifferent files on the same TOI, etc. The above proposal is =
definately the simplest.

5. Fixing source block lengths

We are not absolutely sure if a change is needed here, because we =
haven't done enough implementation and testing to work out the =
optomisation needs. In anycase here are some observations.

How necessary are variable length source blocks? I know this came up =
once before so I missed some of the lgic (maybe someone just needs to =
explain this).

To enable on-the-fly one step reception/decoding/saving/ready_for_use, =
it is essential for a receiver to know the source block lengths so it =
can decode and save to the right part of storage. Otherwise it is forced =
to store individual source blocks and then afterwards sort/defrag/copy =
to storage. Enabling the one step option cuts down on memory and time =
(and maybe total processing cycles). We haven't stress tested the =
implementations yet, but I feel this may be important for battery =
powered devices - espcially for wireless/mobile reception. Fixing this =
requires more stable source block lengths.

Fixing lengths gives 3 options:
a. all source blocks are the same. simple but requires stuffing in the =
last source block (wasted congestion) if the file is not an exact =
interger multiple of the source block size
b. all but the last source block is the same. Removes the stuffing but =
means that you ought to receive packets (encoding symbols) from as least =
two source blocks before you are ready for one-step-receive/store =
(incase the first synbols are from the last, shorter block).
c. all but the last 2 source blocks are the same and the last two are =
the same length as each other. Similar to the "all but the last" but you =
must get symbols from at least 3 blocks to be sure. On the other hand, =
it was suggested that keeping the minimum source block size no smaller =
than half the maximum is a good idea - but can someone explain (my head =
is spinning now :)

2 of the 3 implementations went for option b, and the other only used =
one souce block anyway, but we used null fec (id 0) so I may have missed =
something simple here. Even if no chnage is made, we can pick this up =
again in as an experimental RFC, which is the normal place from =
implemenation experience changes I guess.

Cheers, Rod.

_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From exim@www1.ietf.org  Tue Mar 30 18:27:16 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 SAA00396
	for <rmt-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:27:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjN-0006WI-EZ
	for rmt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAS9n9u8018603
	for rmt-archive@odin.ietf.org; Fri, 28 Nov 2003 04:49:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APfFM-0004pu-6k
	for rmt-web-archive@optimus.ietf.org; Fri, 28 Nov 2003 04:49: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 EAA20070
	for <rmt-web-archive@ietf.org>; Fri, 28 Nov 2003 04:48:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APfFI-00060i-00
	for rmt-web-archive@ietf.org; Fri, 28 Nov 2003 04:49:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1APfFI-00060b-00
	for rmt-web-archive@ietf.org; Fri, 28 Nov 2003 04:49:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APfFH-0004mH-Pk; Fri, 28 Nov 2003 04:49:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1APfEH-0004dr-Kf
	for rmt@optimus.ietf.org; Fri, 28 Nov 2003 04:48: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 EAA19888
	for <rmt@ietf.org>; Fri, 28 Nov 2003 04:47:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1APfEE-0005xk-00
	for rmt@ietf.org; Fri, 28 Nov 2003 04:47:58 -0500
Received: from [217.32.166.20] (helo=relhubc02-ukbr.tcrelay.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1APfED-0005xD-00
	for rmt@ietf.org; Fri, 28 Nov 2003 04:47:58 -0500
Received: from mail pickup service by relhubc02-ukbr.tcrelay.net with Microsoft SMTPSVC;
	 Fri, 28 Nov 2003 09:41:59 +0000
Received: from asgard.ietf.org ([132.151.6.40]) by relhubc02-ukbr.tcrelay.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 26 Nov 2003 16:14:26 +0000
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AP1iV-0004Og-9K
	for ietf-announce-list@asgard.ietf.org; Wed, 26 Nov 2003 10:36:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AP1dm-0004LQ-Tb
	for all-ietf@asgard.ietf.org; Wed, 26 Nov 2003 10:31:42 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12192;
	Wed, 26 Nov 2003 10:31:29 -0500 (EST)
Message-Id: <200311261531.KAA12192@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, 26 Nov 2003 10:31:28 -0500
Precedence: bulk
X-OriginalArrivalTime: 26 Nov 2003 16:14:29.0644 (UTC) FILETIME=[5EB2A4C0:01C3B438]
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-flute-06.txt
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=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		: FLUTE - File Delivery over Unidirectional Transport
	Author(s)	: T. Paila
	Filename	: draft-ietf-rmt-flute-06.txt
	Pages		: 32
	Date		: 2003-11-26
	
This document defines FLUTE, a protocol for the unidirectional
delivery of files over the Internet, which is particularly suited to
multicast networks.  The specification builds on Asynchronous Layered
Coding, the base protocol designed for massively scalable multicast
distribution.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-flute-06.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-flute-06.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-flute-06.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-11-26103652.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-flute-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rmt-flute-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-11-26103652.I-D@ietf.org>

--OtherAccess--

--NextPart--




_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From exim@www1.ietf.org  Tue Mar 30 19:00:41 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 TAA09070
	for <rmt-archive@odin.ietf.org>; Tue, 30 Mar 2004 19:00:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Ris-0006a4-4a
	for rmt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AJeDC2022406
	for rmt-archive@odin.ietf.org; Fri, 10 Oct 2003 15:40:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A837V-0005p9-7s
	for rmt-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 15:40:13 -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 PAA15945
	for <rmt-web-archive@ietf.org>; Fri, 10 Oct 2003 15:40:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A837T-0000Xv-00
	for rmt-web-archive@ietf.org; Fri, 10 Oct 2003 15:40:11 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A837T-0000Xs-00
	for rmt-web-archive@ietf.org; Fri, 10 Oct 2003 15:40:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A837T-0005m6-4W; Fri, 10 Oct 2003 15:40:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A836v-0005dU-N1
	for rmt@optimus.ietf.org; Fri, 10 Oct 2003 15:39:37 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15869;
	Fri, 10 Oct 2003 15:39:29 -0400 (EDT)
Message-Id: <200310101939.PAA15869@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: Fri, 10 Oct 2003 15:39:28 -0400
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-pi-norm-08.txt,.ps,.pdf
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=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		: NACK-Oriented Reliable Multicast Protocol (NORM)
	Author(s)	: B. Adamson, C. Bormann, M. Handley, J. Macker
	Filename	: draft-ietf-rmt-pi-norm-08.txt,.ps,.pdf
	Pages		: 78
	Date		: 2003-10-10
	
This document describes the messages and procedures of the Negative-
acknowledgement (NACK) Oriented Reliable Multicast (NORM) protocol.
This protocol is designed to provide end-to-end reliable transport of
bulk data objects or streams over generic IP multicast routing and
forwarding services.  NORM uses a selective, negative acknowledgement
mechanism for transport reliability and offers additional protocol
mechanisms to conduct reliable multicast sessions with limited 'a
priori' coordination among senders and receivers.  A congestion
control scheme is specified to allow the NORM protocol fairly share
available network bandwidth with other transport protocols such as
Transmission Control Protocol (TCP).  It is capable of operating with
both reciprocal multicast routing among senders and receivers and with
asymmetric connectivity (possibly a unicast return path) from the
senders to receivers.  The protocol offers a number of features to
allow different types of applications or possibly other higher level
transport protocols to utilize its service in different ways.  The
protocol leverages the use of FEC-based repair and other IETF reliable
multicast transport (RMT) building blocks in its design.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-pi-norm-08.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rmt-pi-norm-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rmt-pi-norm-08.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-10-10143352.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-pi-norm-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rmt-pi-norm-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-10-10143352.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



From exim@www1.ietf.org  Tue Mar 30 19:00:53 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 TAA09095
	for <rmt-archive@odin.ietf.org>; Tue, 30 Mar 2004 19:00:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Ris-0006ZK-3P
	for rmt-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AJeCnk022351
	for rmt-archive@odin.ietf.org; Fri, 10 Oct 2003 15:40:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A837T-0005mc-OC
	for rmt-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 15:40:11 -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 PAA15942
	for <rmt-web-archive@ietf.org>; Fri, 10 Oct 2003 15:40:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A837R-0000Xp-00
	for rmt-web-archive@ietf.org; Fri, 10 Oct 2003 15:40:10 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A837R-0000Xl-00
	for rmt-web-archive@ietf.org; Fri, 10 Oct 2003 15:40:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A837R-0005lf-7E; Fri, 10 Oct 2003 15:40:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A836r-0005dM-8p
	for rmt@optimus.ietf.org; Fri, 10 Oct 2003 15:39:33 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15855;
	Fri, 10 Oct 2003 15:39:24 -0400 (EDT)
Message-Id: <200310101939.PAA15855@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: Fri, 10 Oct 2003 15:39:24 -0400
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-bb-norm-07.txt,.ps,.pdf
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=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		: NACK-Oriented Reliable Multicast (NORM) Building Blocks
	Author(s)	: B. Adamson, C. Bormann, M. Handley, J. Macker
	Filename	: draft-ietf-rmt-bb-norm-07.txt,.ps,.pdf
	Pages		: 33
	Date		: 2003-10-10
	
This document discusses the creation the of negative-acknowledgment
This document discusses the creation the of negative-acknowledgment
(NACK)-oriented reliable multicast (NORM) protocols.  The rationale
for NORM goals and assumptions are presented.  Technical challenges
for NACK-oriented (and in some cases general) reliable multicast
protocol operation are identified.  These goals and challenges are
resolved into a set of functional 'building blocks' that address
different aspects of NORM protocol operation.  It is anticipated that
these building blocks will be useful in generating different
instantiations of reliable multicast protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-norm-07.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-norm-07.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-norm-07.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-10-10143339.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-norm-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rmt-bb-norm-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-10-10143339.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt



