From mailman-bounces@ietf.org  Mon Nov  1 08:07:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28607
	for <rmt-web-archive@ietf.org>; Mon, 1 Nov 2004 08:07:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COc9S-0006kY-Vr
	for rmt-web-archive@ietf.org; Mon, 01 Nov 2004 08:23:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COZcP-0002In-Jz
	for rmt-web-archive@ietf.org; Mon, 01 Nov 2004 05:40:57 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: rmt-web-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.23197.1099304194.20557.mailman@lists.ietf.org>
Date: Mon, 01 Nov 2004 05:16:34 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for rmt-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
rmt@ietf.org                             HFbT      
https://www1.ietf.org/mailman/options/rmt/rmt-web-archive%40ietf.org


From rmt-bounces@ietf.org  Thu Nov  4 03:24:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26056
	for <rmt-web-archive@ietf.org>; Thu, 4 Nov 2004 03:24:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPdAd-0005KL-UI
	for rmt-web-archive@ietf.org; Thu, 04 Nov 2004 03:40:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPcmA-000707-6o; Thu, 04 Nov 2004 03:15:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPcca-0005c1-DI
	for rmt@megatron.ietf.org; Thu, 04 Nov 2004 03:05:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24396
	for <rmt@ietf.org>; Thu, 4 Nov 2004 03:05:24 -0500 (EST)
Received: from 67.110.226.239.ptr.us.xo.net ([67.110.226.239]
	helo=mx.webfountain.com) by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CPcry-0004uo-IU for rmt@ietf.org; Thu, 04 Nov 2004 03:21:26 -0500
Received: (qmail 4882 invoked from network); 4 Nov 2004 08:04:47 -0000
Received: from mail.intranet (HELO mail) (10.1.1.37)
	by 67.110.226.239.ptr.us.xo.net with SMTP; 4 Nov 2004 08:04:47 -0000
Received: by mail (8.12.1/8.12.1/Debian -5) with ESMTP id iA488dsB015954;
	Thu, 4 Nov 2004 00:08:39 -0800
Message-Id: <200411040808.iA488dsB015954@mail>
From: "Mike Luby" <luby@digitalfountain.com>
To: <avt@ietf.org>, <rmt@ietf.org>
Date: Thu, 4 Nov 2004 00:05:24 -0800
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTCRQnPL3uqwYCvQhKrcuemRkjgvg==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 509eeaf340e89c687918a6101c6def35
Cc: magnus.westerlund@ericsson.com, lorenzo@cisco.com,
        "'Allison Mankin'" <mankin@psg.com>, luby@digitalfountain.com,
        csp@csperkins.org, woja@alum.mit.edu
Subject: [Rmt] Other pieces of FEC for streaming in 3GPP
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>
Content-Type: multipart/mixed; boundary="===============1218127078=="
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 73948e4d005645343fd08e813e5615ef

This is a multi-part message in MIME format.

--===============1218127078==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002A_01C4C201.FC1F44C0"

This is a multi-part message in MIME format.

------=_NextPart_000_002A_01C4C201.FC1F44C0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Magnus sent an interesting email to the avt list about work going on within
3GPP that is relevant to avt, and Rod Walsh was kind enough to forward this
email to the rmt list since this work is also relevant to rmt.   To complete
the story of what is going on within 3GPP, in addition to the link to
S4-AHP159.zip that Magnus provided in his original email, please also see:

 

http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP181.zip 

This document summarizes the 3GPP agreement made at the meeting, and this
document was approved at the 3GPP meeting.

 

http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP138.zip

http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP166.zip

These two documents describe some considerations in the FEC packet and
source block architecture, and along with S4-AHP159.zip, are referenced in
S4-AHP181.zip.

Mike Luby.

 

 

-----Original Message-----

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of ext

Magnus Westerlund

Sent: Thursday, October 28, 2004 5:37 PM

To: IETF AVT WG

Subject: [AVT] Work on FEC framework for RTP within 3GPP

 

 

Hi,

 

I would like to make all aware of the work on a FEC framework for RTP 

that is ongoing within the 3GPP SA4. It was agreed in the SA4 ad hoc 

meeting 11-13th of October on a working assumption that is according to:

http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP159.zip

with the following changes:

 

- The FEC stream and the original data stream will be SSRC multiplexed 

instead of session multiplexed.

 

- The FEC payload header (the "FEC Tag") will be moved from last in the 

payload to first in the payload for the original stream format.

 

3GPP SA4 will continue to work in neckbreaking speed on this. A proposal 

for specification text for this FEC framework is expected to be 

available in time for the next SA4 meeting (22-26th Nov). The 

specification text needs to be approved on that meeting to meet the 

current deadline.

 

Comments on the approach is solicited.

 

Cheers

 

Magnus Westerlund 

 


------=_NextPart_000_002A_01C4C201.FC1F44C0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Magnus sent an interesting email to the avt list about work =
going on
within 3GPP that is relevant to avt, and Rod Walsh was kind enough to =
forward
this email to the rmt list since this work is also relevant to rmt. =
&nbsp;&nbsp;To
complete the story of what is going on within 3GPP, in addition to the =
link to
S4-AHP159.zip that Magnus provided in his original email, please also =
see:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><a
href=3D"http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP18=
1.zip">http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP181=
.zip</a>
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>This document summarizes the 3GPP agreement made at the meeting, =
and
this document was approved at the 3GPP =
meeting.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><a
href=3D"http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP13=
8.zip">http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP138=
.zip</a><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><a
href=3D"http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP16=
6.zip">http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP166=
.zip</a><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>These two documents describe some considerations in the FEC =
packet and
source block architecture, and along with S4-AHP159.zip, are referenced =
in
S4-AHP181.zip.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Mike Luby.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>-----Original Message-----<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On =
Behalf Of
ext<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Magnus Westerlund<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Sent: Thursday, October 28, 2004 5:37 =
PM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>To: IETF AVT WG<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Subject: [AVT] Work on FEC framework for RTP within =
3GPP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I would like to make all aware of the work on a FEC framework =
for RTP <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>that is ongoing within the 3GPP SA4. It was agreed in the SA4 ad =
hoc <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>meeting 11-13th of October on a working assumption that is =
according
to:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/Ad-hoc_PSM/Docs/S4-AHP15=
9.zip<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>with the following changes:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- The FEC stream and the original data stream will be SSRC =
multiplexed <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>instead of session multiplexed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>- The FEC payload header (the &quot;FEC Tag&quot;) will be moved =
from
last in the <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>payload to first in the payload for the original stream =
format.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>3GPP SA4 will continue to work in neckbreaking speed on this. A
proposal <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>for specification text for this FEC framework is expected to be =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>available in time for the next SA4 meeting (22-26th Nov). The =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>specification text needs to be approved on that meeting to meet =
the <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>current deadline.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Comments on the approach is =
solicited.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Cheers<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Magnus Westerlund&nbsp;</span><o:p></o:p></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_002A_01C4C201.FC1F44C0--



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

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

--===============1218127078==--




From rmt-bounces@ietf.org  Mon Nov  8 13:59:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13621
	for <rmt-web-archive@ietf.org>; Mon, 8 Nov 2004 13:59:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CREk6-0001mv-DM
	for rmt-web-archive@ietf.org; Mon, 08 Nov 2004 13:59:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CREav-0007Q6-UV; Mon, 08 Nov 2004 13:50:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CREJ1-0003RO-18
	for rmt@megatron.ietf.org; Mon, 08 Nov 2004 13:31:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10191
	for <rmt@ietf.org>; Mon, 8 Nov 2004 13:31:42 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CREJP-0000zX-Bp for rmt@ietf.org; Mon, 08 Nov 2004 13:32:22 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 08 Nov 2004 10:42:38 -0800
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iA8IV7om007856
	for <rmt@ietf.org>; Mon, 8 Nov 2004 10:31:08 -0800 (PST)
Received: (from lorenzo@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id KAA24472
	for rmt@ietf.org; Mon, 8 Nov 2004 10:31:09 -0800 (PST)
Date: Mon, 8 Nov 2004 10:31:09 -0800
From: "'Lorenzo Vicisano'" <lorenzo@cisco.com>
To: rmt@ietf.org
Message-ID: <20041108103109.A14643@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Subject: [Rmt] [luby@digitalfountain.com: ]
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>
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f

Dear RMTers,

In the light of the recent issues brought up by FEC ID authors and
the attempt to re-use the BEF BB in an AVT/Streaming context,
Mike luby and I have put together a proposal to revise the FEC BB
before the submission for Standard Track RFC.

The proposal is attached, comments welcome. For those who are
attending the DC IETF, I'm planning to include this on tomorrow's
agenda.

	thanks you,
	Lorenzo

Proposed revisions to FEC building block in transition from
Experimental to Proposed Standard:

(0) A primary goal is to update the FEC-BB in a backward-compatible
way. It is possible that changes will need to be made to dependent
specifications, however it is desirable that the already defined
protocols have an unmodified behavior "on the wire".

(1) A Fully-Specified Encoding ID should fully and explicitly describe
the encoder and decoder, the FEC OTI, the FEC Payload ID(s), the
algorithm for how object is partitioned into source blocks (for object
delivery), exactly which bits are placed into payloads of packets. The
encoder needs to be completely specified to the point that there are
no ambiguities (to ensure inoperability for decoders using different
encoder implementations.) There should be at least enough description
of the decoder to understand how decoding generally operates, although
the requirements on the encoder are much higher (in terms of
specificity), as there may be different implementations of decoders
and some implementations may decide to skip certain steps or not fully
decode to reduce complexity, etc. For object delivery or streaming
there should be enough information in the FEC OTI and FEC Payload ID
to allow a decoder to fully understand and receive the object/stream.

(2) General descriptions that may be applicable to multiple FEC
Encoding IDs, like suggested algorithms for how to partition an object
into multiple source blocks, can be put into the FEC building block
(for example, the object partitioning algorithm currently described in
FLUTE).

(3) The FEC OTI must be more explicitly described than the vague
terminology used now, i.e., explicit parameter names and what there
values mean. Some help from AVT/SDP experts on exactly how to do this
would be highly beneficial.  A nice goal would be to be coherent with
the names: ie. if 2 names refer to the same concept in 2 different FEC
OTIs, then they should be the same. A way to achieve this would be
IANA registration, but that could be an overkill.  It should be made
more explicit that the FEC Encoding ID and FEC Instance ID (if
applicable) are required parts of the FEC OTI.

(4) Emphasize more than now that payload may contain more than one
encoding symbol, and the ESI identifies how all the encoding symobls
in the packet are generated.  This is already in the FEC building
block, but seems to be missed by most people reading it (so there is
no backward compatibility issue, it is already there.)

(5a) Add the following: If a FEC Encoding ID defines a systematic code
(encoding symbols = source symbols + repair symbols) then it may
define two different FEC Payload IDs, one for source packets carrying
source symbols and a different one for repair packets carrying repair
symbols.  In this case, it is the responsibility of the upper layer
protocols to distinguish source packets from repair packets, i.e.,
this is out of band of the FEC building block. (Just like it is now
the responsibility of the upper layer protocols to distinguish packets
for different objects/streams). 

(5b) In conjunction with (5a), it is suggested to use one of the two
reserved bits in the LCT header to indicate whether the packet is a
source of repair packet if a systematic FEC Encoding ID with two
different FEC Payload IDs is used.  This will also allow ALC and FLUTE
to use this same bit for the same purpose.  (For RTP, it turns out
that the payload type can be used to distinguish between the two types
of packets.)

(6) Consider reserving part (half?) of the FEC Encoding IDs for future
use, looking forward to dynamic allocation of FEC Encoding IDs if we
start running out of FEC Encoding IDs.

(7) Explicitly allow FEC Encoding IDs for streaming, or dual use
(object + streaming), although exactly how this would work and exactly
what part of this work would be in AVT and in RMT is still up for
discussion. Should at least discuss this in the meeting as this may
affect the RMT charter.

(8) Recommend leaving the semantics of the Under-Specified FEC
Encoding IDs pretty much the same as in the current FEC BB, subject to
the above changes.  In particular, the FEC Instance ID is not to be
thought of as the next level in a hierarchy, but instead only to be
thought of as being used to name an FEC Scheme that for whatever
reason (too many details or proprietary) the proposer doesn't want to
fully specify. One thing that needs to be worked out here is the
following inconsistency in the current FEC BB. The current FEC BB says
that the same FEC Encoding ID must be used if the FEC Payload ID
format is the same for an Under-Specified FEC scheme as the FEC
Payload ID for an existing FEC Encoding ID.  This suggests implicitly
that the FEC OTI doesn't have to be the same. The current FEC BB also
says that an FEC Encoding ID completely specifies the FEC Payload ID
and the FEC OTI, which means that you could not reuse the same FEC
Encoding ID for an Under-Specified scheme if the FEC Payload ID were
the same but the FEC OTI were different.  Thus, we need to resolve
this one of two ways: (1) an new Under-Specified FEC Scheme must use
an existing FEC Encoding ID if the FEC Payload ID and the FEC OTI are
exactly the same (and also say that new Under-Specified FEC Schemes
should try to use an already existing FEC Encoding ID if at all
possible); (2) an Under-Specified FEC Scheme must use an existing FEC
Encoding ID if the FEC Payload ID is exactly the same, but it can
augment the generic FEC OTI parameters defined by the Under-Specified
FEC Scheme by registering additional fields with IANA [the
registration of the fields would be Instance-specific]. If the generic
part of the FEC OTI defined by the Under-Specified FEC Encoding ID
doesn't apply to the specific scheme, then a new Instance ID + OTI
must be specified (even it the format of the FEC Payload ID is the
same).

(9) One FEC Encoding ID should be defined per RFC or section, with no
mixing between them (fully specify one, then the next, and not mixed
details of the different schemes in the same section).

(10) The FEC BB should describe exactly how new FEC Encoding IDs
should be written in recipe style, i.e., specify the different
sections of a newly specified RFC describing a new FEC Encoding ID and
what explicitly they should contain, so that the new FEC Encoding ID
specifications are as similar in style and complete and easy to
understand as possible.


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


From rmt-bounces@ietf.org  Sun Nov 14 12:29:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27140
	for <rmt-web-archive@ietf.org>; Sun, 14 Nov 2004 12:29:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTODO-0007se-5z
	for rmt-web-archive@ietf.org; Sun, 14 Nov 2004 12:31:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTO7k-0005Ed-EI; Sun, 14 Nov 2004 12:25:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTO4R-0004uu-Kd
	for rmt@megatron.ietf.org; Sun, 14 Nov 2004 12:21:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26736
	for <rmt@ietf.org>; Sun, 14 Nov 2004 12:21:44 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTO6G-0007c5-1B
	for rmt@ietf.org; Sun, 14 Nov 2004 12:23:41 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAEHKav29763; Sun, 14 Nov 2004 19:20:37 +0200 (EET)
X-Scanned: Sun, 14 Nov 2004 19:18:49 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iAEHIm7U027985;
	Sun, 14 Nov 2004 19:18:49 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00dDgmQN; Sun, 14 Nov 2004 19:18:47 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
	iAEHIla28112; Sun, 14 Nov 2004 19:18:47 +0200 (EET)
Received: from esebe001.NOE.Nokia.com ([172.21.138.30]) by
	esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Sun, 14 Nov 2004 19:18:47 +0200
Received: from trebe051.NOE.Nokia.com ([172.22.124.60]) by
	esebe001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Sun, 14 Nov 2004 19:18:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
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] [luby@digitalfountain.com: ]
Date: Sun, 14 Nov 2004 19:18:46 +0200
Message-ID: <B3C148BF4CBD19489565161DF52D7963460F10@trebe051.ntc.nokia.com>
Thread-Topic: [Rmt] [luby@digitalfountain.com: ]
Thread-Index: AcTFxSmT1Uba5Fr/Q1atSUmp0kjxmQAl7KGA
To: <lorenzo@cisco.com>, <rmt@ietf.org>
X-OriginalArrivalTime: 14 Nov 2004 17:18:46.0968 (UTC)
	FILETIME=[00131380:01C4CA6E]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Content-Transfer-Encoding: quoted-printable
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>
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Content-Transfer-Encoding: quoted-printable

Thanks Lorenzo & Mike - excellent initiative.

Please see some in-liners (as I am not in DC to say this myself)...

> Proposed revisions to FEC building block in transition from
> Experimental to Proposed Standard:

Sensible approach.

> (0) A primary goal is to update the FEC-BB in a backward-compatible
> way. It is possible that changes will need to be made to dependent
> specifications, however it is desirable that the already defined
> protocols have an unmodified behavior "on the wire".

Excellent.

> (1) A Fully-Specified Encoding ID should fully and explicitly describe
> the encoder and decoder, the FEC OTI, the FEC Payload ID(s), the
> algorithm for how object is partitioned into source blocks (for object
> delivery), exactly which bits are placed into payloads of packets. The
> encoder needs to be completely specified to the point that there are
> no ambiguities (to ensure inoperability for decoders using different
> encoder implementations.) There should be at least enough description
> of the decoder to understand how decoding generally operates, although
> the requirements on the encoder are much higher (in terms of
> specificity), as there may be different implementations of decoders
> and some implementations may decide to skip certain steps or not fully
> decode to reduce complexity, etc. For object delivery or streaming
> there should be enough information in the FEC OTI and FEC Payload ID
> to allow a decoder to fully understand and receive the object/stream.

The level of specification is to enable interoperability - this must be =
the first point (which everyone probably is already happy with).

Is it really necessary in all cases to fully specify an encoder to =
achieve this? (Forgive me my ignorance - not being a FEC maestro)

(Note, I agree with most of the above paragraph - I just want to sanity =
check that the level of normative specification is not beyond the =
necessary).

> (2) General descriptions that may be applicable to multiple FEC
> Encoding IDs, like suggested algorithms for how to partition an object
> into multiple source blocks, can be put into the FEC building block
> (for example, the object partitioning algorithm currently described in
> FLUTE).

Excellent.

> (3) The FEC OTI must be more explicitly described than the vague
> terminology used now, i.e., explicit parameter names and what there
> values mean. Some help from AVT/SDP experts on exactly how to do this
> would be highly beneficial.  A nice goal would be to be coherent with
> the names: ie. if 2 names refer to the same concept in 2 different FEC
> OTIs, then they should be the same. A way to achieve this would be
> IANA registration, but that could be an overkill.  It should be made
> more explicit that the FEC Encoding ID and FEC Instance ID (if
> applicable) are required parts of the FEC OTI.

Excellent.

> (4) Emphasize more than now that payload may contain more than one
> encoding symbol, and the ESI identifies how all the encoding symobls
> in the packet are generated.  This is already in the FEC building
> block, but seems to be missed by most people reading it (so there is
> no backward compatibility issue, it is already there.)

OK. I think it's already quite clear but improving clarity is usually a =
good thing. Naturally a FEC spec will determine whether or not it =
always/sometimes/never stuffs more than one encoding symbol into a =
payload.

For compact no code FEC, it is logical that only one symbol per payload =
is used (symbol length usually selected for the expected end-to-end MTU =
limits). But I don't think we need to make that mandatory for all cases.

> (5a) Add the following: If a FEC Encoding ID defines a systematic code
> (encoding symbols =3D source symbols + repair symbols) then it may
> define two different FEC Payload IDs, one for source packets carrying
> source symbols and a different one for repair packets carrying repair
> symbols.  In this case, it is the responsibility of the upper layer
> protocols to distinguish source packets from repair packets, i.e.,
> this is out of band of the FEC building block. (Just like it is now
> the responsibility of the upper layer protocols to distinguish packets
> for different objects/streams).=20

OK.

I believe the desired functionality is allowed already - one FEC =
encoding ID for source (e.g. ID=3D0) and one for redundant (e.g. =
ID=3D130).=20

Your proposal is to add a 1/0 payload id to the FEC OTI (in addition to =
FEC encoding id an FEC instance id) - right?

> (5b) In conjunction with (5a), it is suggested to use one of the two
> reserved bits in the LCT header to indicate whether the packet is a
> source of repair packet if a systematic FEC Encoding ID with two
> different FEC Payload IDs is used.  This will also allow ALC and FLUTE
> to use this same bit for the same purpose.  (For RTP, it turns out
> that the payload type can be used to distinguish between the two types
> of packets.)

Were any other options considered?

> (6) Consider reserving part (half?) of the FEC Encoding IDs for future
> use, looking forward to dynamic allocation of FEC Encoding IDs if we
> start running out of FEC Encoding IDs.

Makes sense, though we don't exactly have a rush of work in RMT at the =
moment :)

> (7) Explicitly allow FEC Encoding IDs for streaming, or dual use
> (object + streaming), although exactly how this would work and exactly
> what part of this work would be in AVT and in RMT is still up for
> discussion. Should at least discuss this in the meeting as this may
> affect the RMT charter.

Great - but isn't this already allowed? I guess the new aspect is to =
require that FEC I-Ds explicitly state their applicability to RTP and =
ALC (and any limitations like "only FLUTE"). OTOH, the level of FEC =
specification suggested above (exactly how bits are put into packets) =
would force this anyway.

The FEC BB rewrite will make it's applicability to both RTP and ALC (not =
forgetting NORM and everything else) clear. I guess the essential issue =
is to ensure the "RTP RMT-FEC-BB payload wrapper" is supported in both =
RMT and AVT. (BTW, it's a great idea!!!)

> (8) Recommend leaving the semantics of the Under-Specified FEC
> Encoding IDs pretty much the same as in the current FEC BB, subject to
> the above changes.  In particular, the FEC Instance ID is not to be
> thought of as the next level in a hierarchy, but instead only to be
> thought of as being used to name an FEC Scheme that for whatever
> reason (too many details or proprietary) the proposer doesn't want to
> fully specify. One thing that needs to be worked out here is the
> following inconsistency in the current FEC BB. The current FEC BB says
> that the same FEC Encoding ID must be used if the FEC Payload ID
> format is the same for an Under-Specified FEC scheme as the FEC
> Payload ID for an existing FEC Encoding ID.  This suggests implicitly
> that the FEC OTI doesn't have to be the same. The current FEC BB also
> says that an FEC Encoding ID completely specifies the FEC Payload ID
> and the FEC OTI, which means that you could not reuse the same FEC
> Encoding ID for an Under-Specified scheme if the FEC Payload ID were
> the same but the FEC OTI were different.  Thus, we need to resolve
> this one of two ways: (1) an new Under-Specified FEC Scheme must use
> an existing FEC Encoding ID if the FEC Payload ID and the FEC OTI are
> exactly the same (and also say that new Under-Specified FEC Schemes
> should try to use an already existing FEC Encoding ID if at all
> possible); (2) an Under-Specified FEC Scheme must use an existing FEC
> Encoding ID if the FEC Payload ID is exactly the same, but it can
> augment the generic FEC OTI parameters defined by the Under-Specified
> FEC Scheme by registering additional fields with IANA [the
> registration of the fields would be Instance-specific]. If the generic
> part of the FEC OTI defined by the Under-Specified FEC Encoding ID
> doesn't apply to the specific scheme, then a new Instance ID + OTI
> must be specified (even it the format of the FEC Payload ID is the
> same).

It's late so I might be wrong but: (1) sounds cleaner - allowing =
different OTI to be use a different FEC Encoding ID. (The term "Payload =
ID" needs defining - if someone gets to the correct definition document =
first - please share the news!)

BTW I guess "an existing FEC Encoding ID" -> "an existing under =
specified FEC Encoding ID" would be correct (and less ambiguous)

> (9) One FEC Encoding ID should be defined per RFC or section, with no
> mixing between them (fully specify one, then the next, and not mixed
> details of the different schemes in the same section).

This may turn out to be academic, but in the theoretical case where two =
codes are 95% identical, it makes very little sense to repeat the 95% =
part of the algorithm a second time (though copy & paste ought to avoid =
it introducing new bugs). In another theoretical case, where a FEC =
scheme is a derivative of another, and RFC which properly references an =
earlier RFC is better (due to less documentation overhead and =
consistency checking) than two fully-specified schemes. Naturally, if no =
such schemes exist then this is academic and one fully specified (in all =
detail) FEC Encoding ID per section of a standards track RFC (and I-D =
going for standards track) is reasonable. Any such codes?

(Note, in any case I think this should not apply to Informational and =
Experimental RFCs who's normal purpose are to spread information and =
provide some basis for interoperable testing anyway.)

> (10) The FEC BB should describe exactly how new FEC Encoding IDs
> should be written in recipe style, i.e., specify the different
> sections of a newly specified RFC describing a new FEC Encoding ID and
> what explicitly they should contain, so that the new FEC Encoding ID
> specifications are as similar in style and complete and easy to
> understand as possible.

Sounds like a good idea. It would be useful to get _all_ the authors of =
current FEC RFCs and I-Ds involved to sanity check that the =
one-size-fits-all recipe fits at least the prior work and =
work-in-progress.


Cheers, Rod.

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


From rmt-bounces@ietf.org  Mon Nov 15 23:34:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01240
	for <rmt-web-archive@ietf.org>; Mon, 15 Nov 2004 23:34:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTv4n-0002nk-Le
	for rmt-web-archive@ietf.org; Mon, 15 Nov 2004 23:36:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTv10-00073T-EM; Mon, 15 Nov 2004 23:32:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTuxv-0006NI-R1
	for rmt@megatron.ietf.org; Mon, 15 Nov 2004 23:29:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00680
	for <rmt@ietf.org>; Mon, 15 Nov 2004 23:29:00 -0500 (EST)
Received: from 67.110.226.239.ptr.us.xo.net ([67.110.226.239]
	helo=mx.webfountain.com) by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CTuzo-0002hP-A4 for rmt@ietf.org; Mon, 15 Nov 2004 23:31:15 -0500
Received: (qmail 6889 invoked from network); 16 Nov 2004 04:28:20 -0000
Received: from mail.intranet (HELO mail) (10.1.1.37)
	by 67.110.226.239.ptr.us.xo.net with SMTP; 16 Nov 2004 04:28:20 -0000
Received: by mail (8.12.1/8.12.1/Debian -5) with SMTP id iAG4WTsB028438;
	Mon, 15 Nov 2004 20:32:29 -0800
From: "Michael Luby" <luby@digitalfountain.com>
To: <Rod.Walsh@nokia.com>, <rmt@ietf.org>
Subject: RE: [Rmt] [luby@digitalfountain.com: ]
Date: Mon, 15 Nov 2004 20:27:55 -0800
Message-ID: <MLEAJLFPEBEIKPLNBLGIIEDNEPAA.luby@digitalfountain.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
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: <B3C148BF4CBD19489565161DF52D7963460F10@trebe051.ntc.nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 453b1bfcf0292bffe4cab90ba115f503
Content-Transfer-Encoding: 7bit
Cc: lorenzo@cisco.com, Michael Luby <luby@digitalfountain.com>
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>
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a4cdc653ecdd96665f2aa1c1af034c9e
Content-Transfer-Encoding: 7bit

Rod, Comments inline.  Thx for your support.
Best, Mike

> -----Original Message-----
> From: rmt-bounces@ietf.org [mailto:rmt-bounces@ietf.org]On Behalf Of
> Rod.Walsh@nokia.com
> Sent: Sunday, November 14, 2004 9:19 AM
> To: lorenzo@cisco.com; rmt@ietf.org
> Subject: RE: [Rmt] [luby@digitalfountain.com: ]
>
>
> Thanks Lorenzo & Mike - excellent initiative.
>
> Please see some in-liners (as I am not in DC to say this myself)...
>
> > Proposed revisions to FEC building block in transition from
> > Experimental to Proposed Standard:
>
> Sensible approach.
>
> > (0) A primary goal is to update the FEC-BB in a backward-compatible
> > way. It is possible that changes will need to be made to dependent
> > specifications, however it is desirable that the already defined
> > protocols have an unmodified behavior "on the wire".
>
> Excellent.
>
> > (1) A Fully-Specified Encoding ID should fully and explicitly describe
> > the encoder and decoder, the FEC OTI, the FEC Payload ID(s), the
> > algorithm for how object is partitioned into source blocks (for object
> > delivery), exactly which bits are placed into payloads of packets. The
> > encoder needs to be completely specified to the point that there are
> > no ambiguities (to ensure inoperability for decoders using different
> > encoder implementations.) There should be at least enough description
> > of the decoder to understand how decoding generally operates, although
> > the requirements on the encoder are much higher (in terms of
> > specificity), as there may be different implementations of decoders
> > and some implementations may decide to skip certain steps or not fully
> > decode to reduce complexity, etc. For object delivery or streaming
> > there should be enough information in the FEC OTI and FEC Payload ID
> > to allow a decoder to fully understand and receive the object/stream.
>
> The level of specification is to enable interoperability - this
> must be the first point (which everyone probably is already happy with).
>
> Is it really necessary in all cases to fully specify an encoder
> to achieve this? (Forgive me my ignorance - not being a FEC maestro)

Of course at this point we are only talking about Fully-Specified FEC
Schemes, not Under-Specified FEC Schemes.   Clearly you don't literally have
to fully explain each detail of the encoder (like data structures), but it
must be down to the level that the spec exactly describes what is carried
"on the wire", i.e., the received FEC OTI and the FEC Payload ID must fully
specify the exact encoding symbol bits carried in the payload.  This is the
same type of requirements that I understand are used for RTP.

>
> (Note, I agree with most of the above paragraph - I just want to
> sanity check that the level of normative specification is not
> beyond the necessary).
>
> > (2) General descriptions that may be applicable to multiple FEC
> > Encoding IDs, like suggested algorithms for how to partition an object
> > into multiple source blocks, can be put into the FEC building block
> > (for example, the object partitioning algorithm currently described in
> > FLUTE).
>
> Excellent.
>
> > (3) The FEC OTI must be more explicitly described than the vague
> > terminology used now, i.e., explicit parameter names and what there
> > values mean. Some help from AVT/SDP experts on exactly how to do this
> > would be highly beneficial.  A nice goal would be to be coherent with
> > the names: ie. if 2 names refer to the same concept in 2 different FEC
> > OTIs, then they should be the same. A way to achieve this would be
> > IANA registration, but that could be an overkill.  It should be made
> > more explicit that the FEC Encoding ID and FEC Instance ID (if
> > applicable) are required parts of the FEC OTI.
>
> Excellent.
>
> > (4) Emphasize more than now that payload may contain more than one
> > encoding symbol, and the ESI identifies how all the encoding symobls
> > in the packet are generated.  This is already in the FEC building
> > block, but seems to be missed by most people reading it (so there is
> > no backward compatibility issue, it is already there.)
>
> OK. I think it's already quite clear but improving clarity is
> usually a good thing. Naturally a FEC spec will determine whether
> or not it always/sometimes/never stuffs more than one encoding
> symbol into a payload.
>
> For compact no code FEC, it is logical that only one symbol per
> payload is used (symbol length usually selected for the expected
> end-to-end MTU limits). But I don't think we need to make that
> mandatory for all cases.
>
> > (5a) Add the following: If a FEC Encoding ID defines a systematic code
> > (encoding symbols = source symbols + repair symbols) then it may
> > define two different FEC Payload IDs, one for source packets carrying
> > source symbols and a different one for repair packets carrying repair
> > symbols.  In this case, it is the responsibility of the upper layer
> > protocols to distinguish source packets from repair packets, i.e.,
> > this is out of band of the FEC building block. (Just like it is now
> > the responsibility of the upper layer protocols to distinguish packets
> > for different objects/streams).
>
> OK.
>
> I believe the desired functionality is allowed already - one FEC
> encoding ID for source (e.g. ID=0) and one for redundant (e.g. ID=130).

Actually, it is not at all clear that what you suggest is a legitimate usage
based on the current FEC building block.  I don't think it explicitly says
one way or the other that you can or cannot use different FEC Encoding IDs
to deliver the same object (which is the example you gave above).  I think
it even says explicitly somewhere (but perhaps it is only in LCT or ALC or
FLUTE, I would need to check carefully) that you can only use  one FEC
Encoding ID per object, i.e., you explicitly cannot use two FEC Encoding IDs
for hte same object.  The proposal is to make the use of different FEC
Payload IDs explicitly legitimate in the umbrella of one FEC Encoding ID,
i.e., one FEC Encoding ID will have two possible FEC Payload ID formats, one
for source and one for repair.  The proposal still would not allow using two
FEC Encoding IDs for the delivery of one object.

>
> Your proposal is to add a 1/0 payload id to the FEC OTI (in
> addition to FEC encoding id an FEC instance id) - right?

It would not be in the FEC OTI (which is generally carried out of band).  It
would simply define two FEC Payload IDs, one for source and one for repair
packets.  It would be up to higher layer protocols to distinguish source
from repair packets, and this would determine the actual FEC Payload ID used
in the packet.

>
> > (5b) In conjunction with (5a), it is suggested to use one of the two
> > reserved bits in the LCT header to indicate whether the packet is a
> > source of repair packet if a systematic FEC Encoding ID with two
> > different FEC Payload IDs is used.  This will also allow ALC and FLUTE
> > to use this same bit for the same purpose.  (For RTP, it turns out
> > that the payload type can be used to distinguish between the two types
> > of packets.)
>
> Were any other options considered?

Yes, but this is the one way of doing this that would allow backwards
compatibility, since any existing FEC Encoding ID only uses one FEC Payload
ID, and thus this bit would be set to 0.  Thus, any current implementations
would have this reserved bit set to zero, and it would only be for new FEC
Encoding IDs that defined two different FEC Payload IDs for source and
repair packets that this bit would ever be set to 1 (for repair packets).

>
> > (6) Consider reserving part (half?) of the FEC Encoding IDs for future
> > use, looking forward to dynamic allocation of FEC Encoding IDs if we
> > start running out of FEC Encoding IDs.
>
> Makes sense, though we don't exactly have a rush of work in RMT
> at the moment :)
>
> > (7) Explicitly allow FEC Encoding IDs for streaming, or dual use
> > (object + streaming), although exactly how this would work and exactly
> > what part of this work would be in AVT and in RMT is still up for
> > discussion. Should at least discuss this in the meeting as this may
> > affect the RMT charter.
>
> Great - but isn't this already allowed? I guess the new aspect is
> to require that FEC I-Ds explicitly state their applicability to
> RTP and ALC (and any limitations like "only FLUTE"). OTOH, the
> level of FEC specification suggested above (exactly how bits are
> put into packets) would force this anyway.

The RMT wg charter does not currently include streaming, and thus any
current references to streaming are informational only, not normative.

>
> The FEC BB rewrite will make it's applicability to both RTP and
> ALC (not forgetting NORM and everything else) clear. I guess the
> essential issue is to ensure the "RTP RMT-FEC-BB payload wrapper"
> is supported in both RMT and AVT. (BTW, it's a great idea!!!)
>
> > (8) Recommend leaving the semantics of the Under-Specified FEC
> > Encoding IDs pretty much the same as in the current FEC BB, subject to
> > the above changes.  In particular, the FEC Instance ID is not to be
> > thought of as the next level in a hierarchy, but instead only to be
> > thought of as being used to name an FEC Scheme that for whatever
> > reason (too many details or proprietary) the proposer doesn't want to
> > fully specify. One thing that needs to be worked out here is the
> > following inconsistency in the current FEC BB. The current FEC BB says
> > that the same FEC Encoding ID must be used if the FEC Payload ID
> > format is the same for an Under-Specified FEC scheme as the FEC
> > Payload ID for an existing FEC Encoding ID.  This suggests implicitly
> > that the FEC OTI doesn't have to be the same. The current FEC BB also
> > says that an FEC Encoding ID completely specifies the FEC Payload ID
> > and the FEC OTI, which means that you could not reuse the same FEC
> > Encoding ID for an Under-Specified scheme if the FEC Payload ID were
> > the same but the FEC OTI were different.  Thus, we need to resolve
> > this one of two ways: (1) an new Under-Specified FEC Scheme must use
> > an existing FEC Encoding ID if the FEC Payload ID and the FEC OTI are
> > exactly the same (and also say that new Under-Specified FEC Schemes
> > should try to use an already existing FEC Encoding ID if at all
> > possible); (2) an Under-Specified FEC Scheme must use an existing FEC
> > Encoding ID if the FEC Payload ID is exactly the same, but it can
> > augment the generic FEC OTI parameters defined by the Under-Specified
> > FEC Scheme by registering additional fields with IANA [the
> > registration of the fields would be Instance-specific]. If the generic
> > part of the FEC OTI defined by the Under-Specified FEC Encoding ID
> > doesn't apply to the specific scheme, then a new Instance ID + OTI
> > must be specified (even it the format of the FEC Payload ID is the
> > same).
>
> It's late so I might be wrong but: (1) sounds cleaner - allowing
> different OTI to be use a different FEC Encoding ID. (The term
> "Payload ID" needs defining - if someone gets to the correct
> definition document first - please share the news!)

Lorenzo and I discussed this point, and I actually prefer (1) also, but
Lorenzo pointed out (rightly so) that this might mean little sharing of
Under-Specified FEC Encoding IDs by FEC schemes.  However, if we could try
to go route (1) and see if it works and then fall back to (2) if it doesn't,
I would like that, as you are right (1) is definitely cleaner.

>
> BTW I guess "an existing FEC Encoding ID" -> "an existing under
> specified FEC Encoding ID" would be correct (and less ambiguous)

Yes.

>
> > (9) One FEC Encoding ID should be defined per RFC or section, with no
> > mixing between them (fully specify one, then the next, and not mixed
> > details of the different schemes in the same section).
>
> This may turn out to be academic, but in the theoretical case
> where two codes are 95% identical, it makes very little sense to
> repeat the 95% part of the algorithm a second time (though copy &
> paste ought to avoid it introducing new bugs). In another
> theoretical case, where a FEC scheme is a derivative of another,
> and RFC which properly references an earlier RFC is better (due
> to less documentation overhead and consistency checking) than two
> fully-specified schemes. Naturally, if no such schemes exist then
> this is academic and one fully specified (in all detail) FEC
> Encoding ID per section of a standards track RFC (and I-D going
> for standards track) is reasonable. Any such codes?

This is a good point, and I'm not sure if it is too academic or not.  The
intent of course is to not have completely different FEC schemes defined in
an intermixed way in the same RFC (and there has been some instances of
this, of which I think I am also guilty in the past).  Properly organized
descriptions of FEC schemes should make the docs more readable...

>
> (Note, in any case I think this should not apply to Informational
> and Experimental RFCs who's normal purpose are to spread
> information and provide some basis for interoperable testing anyway.)
>
> > (10) The FEC BB should describe exactly how new FEC Encoding IDs
> > should be written in recipe style, i.e., specify the different
> > sections of a newly specified RFC describing a new FEC Encoding ID and
> > what explicitly they should contain, so that the new FEC Encoding ID
> > specifications are as similar in style and complete and easy to
> > understand as possible.
>
> Sounds like a good idea. It would be useful to get _all_ the
> authors of current FEC RFCs and I-Ds involved to sanity check
> that the one-size-fits-all recipe fits at least the prior work
> and work-in-progress.
>
>
> Cheers, Rod.
>
> _______________________________________________
> 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  Fri Nov 19 15:25:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10565
	for <rmt-web-archive@ietf.org>; Fri, 19 Nov 2004 15:25:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVFMo-0005ti-4n
	for rmt-web-archive@ietf.org; Fri, 19 Nov 2004 15:28:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVF3K-0005y5-Fn; Fri, 19 Nov 2004 15:08:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVF13-0003lC-Ob; Fri, 19 Nov 2004 15:05:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08015;
	Fri, 19 Nov 2004 15:05:55 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVF3w-0005S5-Ds; Fri, 19 Nov 2004 15:08:56 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id iAJK4ft06640;
	Fri, 19 Nov 2004 12:04:41 -0800 (PST)
Message-Id: <200411192004.iAJK4ft06640@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 19 Nov 2004 12:04:41 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: rmt@ietf.org, rfc-editor@rfc-editor.org
Subject: [Rmt] RFC 3940 on Negative-acknowledgment (NACK)-Oriented Reliable
	Multicast (NORM) Protocol
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>
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 3940

        Title:      Negative-acknowledgment (NACK)-Oriented
                    Reliable Multicast (NORM) Protocol
        Author(s):  B. Adamson, C. Bormann, M. Handley, J. Macker
        Status:     Experimental
        Date:       November 2004
        Mailbox:    adamson@itd.nrl.navy.mil, cabo@tzi.org,
                    M.Handley@cs.ucl.ac.uk, macker@itd.nrl.navy.mil
        Pages:      80
        Characters: 220549
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rmt-pi-norm-10.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3940.txt


This document describes the messages and procedures of the
Negative-acknowledgment (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
acknowledgment mechanism for transport reliability and offers
additional protocol mechanisms to allow for operation with minimal "a
priori" coordination among senders and receivers.  A congestion
control scheme is specified to allow the NORM protocol to 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) between the
senders and 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.

This document is a product of the Reliable Multicase 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.

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: <041119120223.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3940

--OtherAccess
Content-Type: Message/External-body; name="rfc3940.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <041119120223.RFC@RFC-EDITOR.ORG>


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

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

--NextPart--



From rmt-bounces@ietf.org  Fri Nov 19 15:37:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12943
	for <rmt-web-archive@ietf.org>; Fri, 19 Nov 2004 15:37:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVFYY-0006YR-MV
	for rmt-web-archive@ietf.org; Fri, 19 Nov 2004 15:40:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVFKf-0001kI-U4; Fri, 19 Nov 2004 15:26:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVF3R-00062m-3P; Fri, 19 Nov 2004 15:08:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08325;
	Fri, 19 Nov 2004 15:08:23 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVF6J-0005V1-7w; Fri, 19 Nov 2004 15:11:24 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id iAJK6at07398;
	Fri, 19 Nov 2004 12:06:36 -0800 (PST)
Message-Id: <200411192006.iAJK6at07398@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 19 Nov 2004 12:06:36 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: rmt@ietf.org, rfc-editor@rfc-editor.org
Subject: [Rmt] RFC 3941 on Negative-Acknowledgment (NACK)-Oriented Reliable
	Multicast (NORM) Building Blocks
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>
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 3941

        Title:      Negative-Acknowledgment (NACK)-Oriented Reliable
                    Multicast (NORM) Building Blocks
        Author(s):  B. Adamson, C. Bormann, ,M. Handley J. Macker
        Status:     Experimental
        Date:       November 2004
        Mailbox:    adamson@itd.nrl.navy.mil, cabo@tzi.org,
                    M.Handley@cs.ucl.ac.uk, macker@itd.nrl.navy.mil
        Pages:      36
        Characters: 92785
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rmt-bb-norm-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3941.txt


This document discusses the creation 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.

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.

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: <041119120504.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3941

--OtherAccess
Content-Type: Message/External-body; name="rfc3941.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <041119120504.RFC@RFC-EDITOR.ORG>


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

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

--NextPart--



From rmt-bounces@ietf.org  Fri Nov 19 16:47:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27615
	for <rmt-web-archive@ietf.org>; Fri, 19 Nov 2004 16:47:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVGed-0002xw-3T
	for rmt-web-archive@ietf.org; Fri, 19 Nov 2004 16:50:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVGLq-0003vl-Qf; Fri, 19 Nov 2004 16:31:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVFUF-0000FF-0o
	for rmt@megatron.ietf.org; Fri, 19 Nov 2004 15:36:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12638
	for <rmt@ietf.org>; Fri, 19 Nov 2004 15:36:04 -0500 (EST)
Received: from 67.110.226.239.ptr.us.xo.net ([67.110.226.239]
	helo=mx.webfountain.com) by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CVFX7-0006Qs-4R for rmt@ietf.org; Fri, 19 Nov 2004 15:39:06 -0500
Received: (qmail 6606 invoked from network); 19 Nov 2004 20:35:30 -0000
Received: from mail.intranet (HELO mail) (10.1.1.37)
	by 67.110.226.239.ptr.us.xo.net with SMTP; 19 Nov 2004 20:35:30 -0000
Received: by mail (8.12.1/8.12.1/Debian -5) with SMTP id iAJKdisB007418;
	Fri, 19 Nov 2004 12:39:44 -0800
From: "Michael Luby" <luby@digitalfountain.com>
To: "Rmt@ietf. org" <rmt@ietf.org>
Date: Fri, 19 Nov 2004 12:35:06 -0800
Message-ID: <MLEAJLFPEBEIKPLNBLGIEEEJEBAA.luby@digitalfountain.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 1.0 (+)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Michael Luby <luby@digitalfountain.com>
Subject: [Rmt] Proposal for RMT wg item
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>
Content-Type: multipart/mixed; boundary="===============0215279022=="
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30

This is a multi-part message in MIME format.

--===============0215279022==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0030_01C4CE34.3300D3D0"

This is a multi-part message in MIME format.

------=_NextPart_000_0030_01C4CE34.3300D3D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

RMT colleagues,

At the recent IETF there was an individual draft submission that can be
obtained by clicking on the link below:
http://www.ietf.org/internet-drafts/draft-luby-rmt-bb-fec-raptor-object-00.t
xt

A presentation on this draft was also made during the RMT meeting, which can
be obtained by clicking on the link below:
http://www1.ietf.org/proceedings_new/04nov/slides/rmt-2/sld1.htm

The proposal is to make this an RMT wg item.  Please send any comments to
the list.

Regards, Mike Luby



------=_NextPart_000_0030_01C4CE34.3300D3D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1458" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial size=3D2>RMT=20
colleagues,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>At the recent IETF there was an =
individual draft=20
submission that can be obtained by clicking on the link =
below:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-luby-rmt-bb-fec-raptor-=
object-00.txt">http://www.ietf.org/internet-drafts/draft-luby-rmt-bb-fec-=
raptor-object-00.txt</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>A presentation on this draft was also=20
made&nbsp;during the&nbsp;RMT meeting, which can be obtained by clicking =
on the=20
link below:</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://www1.ietf.org/proceedings_new/04nov/slides/rmt-2/sld1.htm"=
=20
target=3D_blank>http://www1.ietf.org/proceedings_new/04nov/slides/rmt-2/s=
ld1.htm</A></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial>The proposal is to make this an =
RMT wg=20
item.&nbsp; Please send any comments to the list.</FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial>Regards, Mike Luby</FONT></DIV>
<DIV><BR><BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_0030_01C4CE34.3300D3D0--



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

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

--===============0215279022==--




From rmt-bounces@ietf.org  Sat Nov 20 12:02:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07817
	for <rmt-web-archive@ietf.org>; Sat, 20 Nov 2004 12:02:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVYg7-0000t8-Vp
	for rmt-web-archive@ietf.org; Sat, 20 Nov 2004 12:05:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVYUJ-0002Gn-Ce; Sat, 20 Nov 2004 11:53:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVYNS-00010E-5v
	for rmt@megatron.ietf.org; Sat, 20 Nov 2004 11:46:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06812
	for <rmt@ietf.org>; Sat, 20 Nov 2004 11:46:19 -0500 (EST)
Received: from aardvark.cs.ucl.ac.uk ([128.16.11.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVYQW-0000Xs-K4
	for rmt@ietf.org; Sat, 20 Nov 2004 11:49:33 -0500
Received: from aardvark.cs.ucl.ac.uk (localhost [127.0.0.1])
	by aardvark.cs.ucl.ac.uk (8.12.11/8.12.8) with ESMTP id iAKGkDBp079244; 
	Sat, 20 Nov 2004 16:46:15 GMT
	(envelope-from mjh@aardvark.cs.ucl.ac.uk)
From: Mark Handley <M.Handley@cs.ucl.ac.uk>
X-Organisation: UCL
To: Michael Luby <luby@digitalfountain.com>
Subject: Re: [Rmt] Proposal for RMT wg item 
In-reply-to: Your message of "Fri, 19 Nov 2004 12:35:06 PST."
	<MLEAJLFPEBEIKPLNBLGIEEEJEBAA.luby@digitalfountain.com> 
Date: Sat, 20 Nov 2004 16:46:13 +0000
Message-ID: <79243.1100969173@aardvark.cs.ucl.ac.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: "Rmt@ietf. org" <rmt@ietf.org>
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>
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3


>At the recent IETF there was an individual draft submission that can be
>obtained by clicking on the link below:
>http://www.ietf.org/internet-drafts/draft-luby-rmt-bb-fec-raptor-object-00.t
>xt
>
>A presentation on this draft was also made during the RMT meeting, which can
>be obtained by clicking on the link below:
>http://www1.ietf.org/proceedings_new/04nov/slides/rmt-2/sld1.htm
>
>The proposal is to make this an RMT wg item.  Please send any comments to
>the list.

In the WG meeting, I asked if the RAND terms of Digital Fountain's
patent licensing would permit open-source implementations, and you
said you'd look into this.  Any progress to report?

For those who weren't there: this is extremely cool technology.  I
encourage you to take a look at it.

 - Mark

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


From rmt-bounces@ietf.org  Wed Nov 24 11:08:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06557
	for <rmt-web-archive@ietf.org>; Wed, 24 Nov 2004 11:08:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWzl5-0001pX-Sj
	for rmt-web-archive@ietf.org; Wed, 24 Nov 2004 11:12:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWzWF-0007MM-VT; Wed, 24 Nov 2004 10:57:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWzOT-0005BT-7W; Wed, 24 Nov 2004 10:49:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05122;
	Wed, 24 Nov 2004 10:49:18 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWzSB-0008Bb-91; Wed, 24 Nov 2004 10:53:22 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAOFn7h5005937; Wed, 24 Nov 2004 16:49:07 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 24 Nov 2004 16:49:07 +0100
Received: from [147.214.97.153] (permit153.er.ki.sw.ericsson.se
	[147.214.97.153]) by esealnt610.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XRD5YW3M; Wed, 24 Nov 2004 16:48:35 +0100
Message-ID: <41A4AD4C.7060607@ericsson.com>
Date: Wed, 24 Nov 2004 16:48:28 +0100
X-Sybari-Trust: 5abed82a 8ac546dc 47ea6b95 00000979
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, rmt@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Nov 2004 15:49:07.0413 (UTC)
	FILETIME=[21BDA050:01C4D23D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Subject: [Rmt] 3GPP includes RTP FEC framework in MBMS specificaiton 26.346
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>
Sender: rmt-bounces@ietf.org
Errors-To: rmt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

Hi,

3GPP WG SA4 has this week agreed to include the specification text 
present in the contribution;
http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/TSGS4_33/Docs/S4-040698.zip
to be included in 3GPP Technical specification 26.346 in Release 6.

There is know that some small changes are necessary to certain details. 
The changes known, is to the actual reference to the FEC encoding ID 
utilized in the RTP payload, which will be harmonized with the 
declaration used for FLUTE in SDP.

Cheers

Magnus Westerlund

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


