From rmt-bounces@ietf.org Thu Jan 11 10:58:09 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H52JZ-0000Ui-J6; Thu, 11 Jan 2007 10:58:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H52JY-0000UL-Mv; Thu, 11 Jan 2007 10:58:04 -0500
Received: from mx2.grc.nasa.gov ([128.156.11.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H52JX-0004LX-B6; Thu, 11 Jan 2007 10:58:04 -0500
Received: from lombok-fi.grc.nasa.gov (seraph.grc.nasa.gov [128.156.10.10])
	by mx2.grc.nasa.gov (Postfix) with ESMTP id 1D25FC275;
	Thu, 11 Jan 2007 10:58:00 -0500 (EST)
Received: from apataki.grc.nasa.gov (apataki.grc.nasa.gov [139.88.112.35])
	by lombok-fi.grc.nasa.gov (NASA GRC TCPD 8.13.7/8.13.7) with ESMTP id
	l0BFvumQ007815; Thu, 11 Jan 2007 10:57:56 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by apataki.grc.nasa.gov (NASA GRC TCPD 8.13.7/8.13.7) with ESMTP id
	l0BFvuUs016666; Thu, 11 Jan 2007 10:57:56 -0500 (EST)
Received: from apataki.grc.nasa.gov ([127.0.0.1])by localhost 
	(apataki.grc.nasa.gov [127.0.0.1]) (amavisd-new,
	port 10024)with ESMTP id 
	krzYsOlfF34d; Thu, 11 Jan 2007 10:57:55 -0500 (EST)
Received: from drpepper.grc.nasa.gov (gr2134391.grc.nasa.gov 
	[139.88.44.123])by apataki.grc.nasa.gov (NASA GRC TCPD 8.13.7/8.13.7)
	with ESMTP id l0BFvsNS016651;Thu, 11 Jan 2007 10:57:54 -0500 (EST)
Received: by drpepper.grc.nasa.gov (Postfix, from userid 501)id E35F54FE10; 
	Thu, 11 Jan 2007 10:55:41 -0500 (EST)
Date: Thu, 11 Jan 2007 10:55:41 -0500
From: Wesley Eddy <weddy@grc.nasa.gov>
To: iccrg@cs.ucl.ac.uk, tsvwg@ietf.org, tcpm@ietf.org, tsv-area@ietf.org,
	dccp@ietf.org, rmt@ietf.org
Message-ID: <20070111155541.GA25291@grc.nasa.gov>
Mime-Version: 1.0
Content-Type: text/plain;
	charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.5.1i
X-imss-version: 2.045
X-imss-result: Passed
X-imss-scores: Clean:65.94000 C:2 M:6 S:5 R:5
X-imss-settings: Baseline:1 C:2 M:2 S:2 R:2 (0.0000 0.0000)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: 
Subject: [Rmt] review solicitation for ICCRG congestion control survey
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: weddy@grc.nasa.gov
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
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>
Errors-To: rmt-bounces@ietf.org

In the ICCRG's goal to foster a long-term congestion control
architecture for the Internet, its initial step is to understand all of
the current mechanisms in use.  As an aid to this, the ICCRG is working
on a document that summarizes all of the congestion control mechanisms
and other guidance that the IETF has produced and published in the RFC
series.  The initial version of this document is online:
http://tools.ietf.org/group/irtf/draft-irtf-iccrg-cc-rfcs-00.txt

We think this is a fairly complete listing of the RFCs that relate to
congestion control, but if you know of others that should be included,
we would like to hear about it.

Also, comments on what can be done to make this more useful or readable
are welcome.  Comments on and improvements to the text summarizing each
RFC are also welcome.

The goal is to gather these inputs before the ICCRG meeting in
mid-February.  After the ICCRG meeting, the document will be updated
based on these comments and discussion from the meeting.

Please send all comments to the ICCRG list (iccrg@cs.ucl.ak.uk).  Although
this request is being sent to multiple lists, this is only to notify
people not on the ICCRG list; we do not want to burden the other mailing
lists with replies, so please trim the "to" and "cc" fields of replies.

Thanks in advance.

-- 
Wesley M. Eddy
Verizon Federal Network Systems

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



From rmt-bounces@ietf.org Mon Jan 22 15:50:42 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H967X-0007Mx-47; Mon, 22 Jan 2007 15:50:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9679-000799-TC; Mon, 22 Jan 2007 15:50:03 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H9679-0007BP-KQ; Mon, 22 Jan 2007 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 988F726EC2;
	Mon, 22 Jan 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1H9678-00082S-82; Mon, 22 Jan 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1H9678-00082S-82@stiedprstage1.ietf.org>
Date: Mon, 22 Jan 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: rmt@ietf.org
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-bb-fec-raptor-object-05.txt 
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
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>
Errors-To: rmt-bounces@ietf.org

--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		: Raptor Forward Error Correction Scheme for Object Delivery
	Author(s)	: M. Luby, et al.
	Filename	: draft-ietf-rmt-bb-fec-raptor-object-05.txt
	Pages		: 52
	Date		: 2007-1-22
	
This document describes a Fully-Specified FEC scheme, corresponding
   to FEC Encoding ID 1, for the Raptor forward error correction code
   and its application to reliable delivery of data objects.

   Raptor is a fountain code, i.e., as many encoding symbols as needed
   can be generated by the encoder on-the-fly from the source symbols of
   a source block of data.  The decoder is able to recover the source
   block from any set of encoding symbols only slightly more in number
   than the number of source symbols.

   The Raptor code described here is a systematic code, meaning that all
   the source symbols are among the encoding symbols that can be
   generated.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-raptor-object-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-fec-raptor-object-05.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-fec-raptor-object-05.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: <2007-1-22142221.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-fec-raptor-object-05.txt

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

Content-Type: text/plain
Content-ID: <2007-1-22142221.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From rmt-bounces@ietf.org Tue Jan 23 01:57:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9Faa-0001pA-2W; Tue, 23 Jan 2007 01:57:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9FaY-0001p5-S7
	for rmt@ietf.org; Tue, 23 Jan 2007 01:57:02 -0500
Received: from exbe04.ex.dslextreme.net ([66.51.199.86]
	helo=EXVS01.ex.dslextreme.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9FaX-0004CH-Fj
	for rmt@ietf.org; Tue, 23 Jan 2007 01:57:02 -0500
Received: from 63.164.47.227 ([63.164.47.227]) by EXVS01.ex.dslextreme.net
	([192.168.7.220]) via Exchange Front-End Server
	owa.dslextreme.net ([192.168.7.126]) with Microsoft Exchange
	Server HTTP-DAV ; Tue, 23 Jan 2007 06:56:56 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 22 Jan 2007 22:56:54 -0800
Subject: Re: [Rmt] I-D ACTION:draft-ietf-rmt-bb-fec-raptor-object-05.txt 
From: Mark Watson <mark@digitalfountain.com>
To: "rmt@ietf.org" <rmt@ietf.org>
Message-ID: <C1DAF1B6.125DB%mark@digitalfountain.com>
Thread-Topic: [Rmt] I-D ACTION:draft-ietf-rmt-bb-fec-raptor-object-05.txt 
Thread-Index: Acc+u6pH6L/hf6quEdutzAAX8sJN9g==
In-Reply-To: <E1H9678-00082S-82@stiedprstage1.ietf.org>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.1 (++)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
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>
Errors-To: rmt-bounces@ietf.org

All,

This is just a repost because the previous draft had expired. There are no
changes except the date.

Regards,

Mark


On 1/22/07 12:50 PM, "Internet-Drafts@ietf.org" <Internet-Drafts@ietf.org>
wrote:

> 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  : Raptor Forward Error Correction Scheme for Object Delivery
> Author(s) : M. Luby, et al.
> Filename : draft-ietf-rmt-bb-fec-raptor-object-05.txt
> Pages  : 52
> Date  : 2007-1-22
> 
> This document describes a Fully-Specified FEC scheme, corresponding
>    to FEC Encoding ID 1, for the Raptor forward error correction code
>    and its application to reliable delivery of data objects.
> 
>    Raptor is a fountain code, i.e., as many encoding symbols as needed
>    can be generated by the encoder on-the-fly from the source symbols of
>    a source block of data.  The decoder is able to recover the source
>    block from any set of encoding symbols only slightly more in number
>    than the number of source symbols.
> 
>    The Raptor code described here is a systematic code, meaning that all
>    the source symbols are among the encoding symbols that can be
>    generated.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-raptor-object-05.txt
> 
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message. 
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> 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-fec-raptor-object-05.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-fec-raptor-object-05.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.
> Content-Type: text/plain
> Content-ID: <2007-1-22142221.I-D@ietf.org>
> 
> _______________________________________________
> 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 rmt-bounces@ietf.org Mon Jan 29 15:50:11 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBdS3-0007fU-4G; Mon, 29 Jan 2007 15:50:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBdRy-0007dK-RB; Mon, 29 Jan 2007 15:50:03 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HBdRy-0006td-Fj; Mon, 29 Jan 2007 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 4A34426ECD;
	Mon, 29 Jan 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HBdRy-0001WW-6N; Mon, 29 Jan 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HBdRy-0001WW-6N@stiedprstage1.ietf.org>
Date: Mon, 29 Jan 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: rmt@ietf.org
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-flute-revised-03.txt 
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
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>
Errors-To: rmt-bounces@ietf.org

--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, et al.
	Filename	: draft-ietf-rmt-flute-revised-03.txt
	Pages		: 34
	Date		: 2007-1-29
	
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-revised-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-revised-03.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-revised-03.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: <2007-1-29103533.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-1-29103533.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From rmt-bounces@ietf.org Wed Jan 31 08:35:34 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCFcL-0003LA-7m; Wed, 31 Jan 2007 08:35:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCFcK-0003Ky-0E
	for rmt@ietf.org; Wed, 31 Jan 2007 08:35:16 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCFcC-0007ZU-CD
	for rmt@ietf.org; Wed, 31 Jan 2007 08:35:15 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A85892110E; Wed, 31 Jan 2007 14:35:03 +0100 (CET)
X-AuditID: c1b4fb3e-aeed1bb0000007e1-56-45c09b07a63d 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	876CE201F9; Wed, 31 Jan 2007 14:35:03 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Jan 2007 14:35:03 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Jan 2007 14:35:03 +0100
Message-ID: <45C09B07.8080905@ericsson.com>
Date: Wed, 31 Jan 2007 14:35:03 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: rmt@ietf.org,  mark@digitalfountain.com, 
	Michael Luby <luby@digitalfountain.com>,
	Lorenzo Vicisano <lorenzo@vicisano.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jan 2007 13:35:03.0127 (UTC)
	FILETIME=[9C9D7E70:01C7453C]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: 
Subject: [Rmt] AD comments on draft-ietf-rmt-bb-fec-revised-04
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>,
	<mailto:rmt-request@ietf.org?subject=unsubscribe>
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>
Errors-To: rmt-bounces@ietf.org

Hi,

Sorry for the delay in reviewing. However here are some comments.

1. The draft needs to in the following 3 places provide explicit mention 
that this document obsoletes RFC 3452: In the left side of the first 
page header: Obsoletes: RFC 3452 (if approved), the abstract, and in the 
introduction. Even if redundant this is what is required to be clear.

2. The abstract: I think the abstract is unclear on what framework this 
document relates to. The abstract indicates that the information present 
in the document applies to any data transport. I think this is a bit 
more generic than the reality of the RMT framework. I would appreciate 
some clearer pointers to the RMT framework.

3. A question on status of discussion. If I remember correctly there has 
been some discussion about changing the FEC payload ID from a globally 
unique Integer per FEC scheme to be a dynamically mapped identifier for 
a longer name. Are all these discussion put on the shelf for the moment? 
I don't see any strict need to do this currently, as the publication 
rate of FEC schemes has be relative low. It is definitely not comparable 
with payload formats in RTP.

4. Section 6.2.4:
"Maximum-Source-Block-Length:  a non-negative integer indicating the
       maximum number of source symbols in a source block"

Isn't this wrongly named. It is only implicitly a length, the current 
definition is a maximum number of source symbols and should much more 
appropriately be called "Max-Number-Source-Symbols"

5. Section 11. To me this document seems to incorrectly cover the need 
for both source authentication and packet integrity for any FEC symbols. 
The draft makes a large push for integrity, while integrity without 
source authentication still allows an attacker to insert erroneous 
symbols into any block.

6. Section 12.1.:

   "This document defines a name-space for FEC Encoding IDs named:
                               ietf:rmt:fec:encoding

    The values that can be assigned within the "ietf:rmt:fec:encoding"
    name-space are numeric indexes in the range [0, 255], boundaries
    included.  Assignment requests are granted on a "IETF Consensus"
    basis as defined in [2]."

I think that one should point out that this document in general provides 
restrictions on what is acceptable for documents going for registration. 
As IANA or someone looking in the registry may start by looking at the 
IANA rules in this document a self reference regarding the existence of 
rules in this document makes sense.

7. Lorenzo needs to update his address information.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



