From rmt-bounces@ietf.org Mon Feb 05 10:31:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE5nr-0006RY-SG; Mon, 05 Feb 2007 10:30:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HE5c7-0000uV-Gb
	for rmt@ietf.org; Mon, 05 Feb 2007 10:18:39 -0500
Received: from s2.itd.nrl.navy.mil ([132.250.83.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE5bX-0007UN-OH
	for rmt@ietf.org; Mon, 05 Feb 2007 10:18:06 -0500
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by s2.itd.nrl.navy.mil (8.13.6+Sun/8.12.8) with SMTP id l15FHvFp028736; 
	Mon, 5 Feb 2007 10:17:57 -0500 (EST)
Received: from [132.250.92.151] ([132.250.92.151])
	by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.12.43) with SMTP id
	M2007020510175516618 ; Mon, 05 Feb 2007 10:17:56 -0500
Mime-Version: 1.0
Message-Id: <p06230906c1ecf93a7dce@[132.250.92.151]>
Date: Mon, 5 Feb 2007 10:17:54 -0500
To: rmt@ietf.org
From: Brian Adamson <adamson@itd.nrl.navy.mil>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-Mailman-Approved-At: Mon, 05 Feb 2007 10:30:45 -0500
Cc: adamson@itd.nrl.navy.mil
Subject: [Rmt] RMT WG Last Call: draft-ietf-rmt-bb-fec-ldpc-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

Please be advised that the LDPC FEC Scheme draft:

http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-ldpc-04.txt

is now officially in WG Last Call that will expire February 23th, 2007.

Please address any comments to the document authors and this mailing
list.

Thank you,
the WG chairs.


-- 
Brian
__________________________________
Brian Adamson
<mailto:adamson@itd.nrl.navy.mil>

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



From rmt-bounces@ietf.org Mon Feb 05 10:42:00 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE5yi-00062l-Ae; Mon, 05 Feb 2007 10:42:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HE5xg-0005GW-RV
	for rmt@ietf.org; Mon, 05 Feb 2007 10:40:56 -0500
Received: from s2.itd.nrl.navy.mil ([132.250.83.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE5xf-0003Tq-JC
	for rmt@ietf.org; Mon, 05 Feb 2007 10:40:56 -0500
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by s2.itd.nrl.navy.mil (8.13.6+Sun/8.12.8) with SMTP id l15Fes50000097; 
	Mon, 5 Feb 2007 10:40:54 -0500 (EST)
Received: from [132.250.92.151] ([132.250.92.151])
	by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.12.43) with SMTP id
	M2007020510405216752 ; Mon, 05 Feb 2007 10:40:53 -0500
Mime-Version: 1.0
Message-Id: <p06230909c1ecfb2af22a@[132.250.92.151]>
Date: Mon, 5 Feb 2007 10:40:51 -0500
To: rmt@ietf.org
From: Brian Adamson <adamson@itd.nrl.navy.mil>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-Mailman-Approved-At: Mon, 05 Feb 2007 10:41:59 -0500
Cc: adamson@itd.nrl.navy.mil
Subject: [Rmt] RMT WG Last Call: draft-rmt-bb-norm-revised-02
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

Please be advised that the revised NORM Building Block draft:

http://www.ietf.org/internet-drafts/draft-rmt-bb-norm-revised-02.txt

is now officially in WG Last Call that will expire February 23th, 2007.

Please address any comments to the document authors and this mailing
list.

Thank you,
the WG chairs.


-- 
Brian
__________________________________
Brian Adamson
<mailto:adamson@itd.nrl.navy.mil>

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



From rmt-bounces@ietf.org Fri Feb 16 14:24:27 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI8go-0003zr-G3; Fri, 16 Feb 2007 14:24:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HI8gm-0003zl-UF
	for rmt@ietf.org; Fri, 16 Feb 2007 14:24:12 -0500
Received: from mail6.sea5.speakeasy.net ([69.17.117.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HI8gi-0007Um-Bu
	for rmt@ietf.org; Fri, 16 Feb 2007 14:24:12 -0500
Received: (qmail 8182 invoked from network); 16 Feb 2007 19:24:01 -0000
Received: from 67.110.226.222.ptr.us.xo.net (HELO mela.intranet)
	(lvicisano@[67.110.226.222]) (envelope-sender <lorenzo@vicisano.net>)
	by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted
	SMTP for <toni.paila@nokia.com>; 16 Feb 2007 19:24:01 -0000
Date: Fri, 16 Feb 2007 11:24:05 -0800
From: Lorenzo Vicisano <lorenzo@vicisano.net>
To: OMA-LIAISON@mail.openmobilealliance.org
Message-ID: <20070216192405.GA9115@digitalfountain.com>
References: <E1HHpGd-0006Zu-Ks@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1HHpGd-0006Zu-Ks@ietf.org>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: magnus.westerlund@ericsson.com, adamson@itd.nrl.navy.mil,
	Toni Paila <toni.paila@nokia.com>, rmt@ietf.org
Subject: [Rmt] Re: New Liaison Statement,
	"OMA LS 166 Liaison Statement to the IETF Requesting Guidance
	on using LCT revised"
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,

I will make sure to add this discussion item to the agenda of WG
meeting that will be held in Prague on March 21st.

    Regards,
    Lorenzo Vicisano


On Thu, Feb 15, 2007 at 05:39:55PM -0500, Dean Willis wrote:
> 
> Title: OMA LS 166 Liaison Statement to the IETF Requesting Guidance on using LCT revised
> Submission Date: 2007-02-15
> URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=298 
> Please reply by 2007-03-23
> 
> From: Dean Willis(OMA) <dean.willis@softarmor.com>
> To: IETF Reliable Multicast Transport (RMT) Working Group(adamson@itd.nrl.navy.mil,  lorenzo@vicisano.net)
> Cc: magnus.westerlund@ericsson.com
> lars.eggert@nokia.com
> rmt@ietf.org
> Reponse Contact: Toni Paila <toni.paila@nokia.com>
> Technical Contact: Toni Paila <toni.paila@nokia.com>
> Purpose: For action 
> Body: 1	Overview
> 
> OMA BAC-BCAST has a question to IETF RMT on the stability of standards-track evolution of 'Layered Coding Transport (LCT) Building Block'. The latest Internet-Draft revision -04 (expired) of LCT introduced the header extension EXT_TIME for the purpose of signalling time stamps of different nature. OMA BAC-BCAST would be interested to use that method but is hesitant to refer to ongoing IETF work unless such work can be considered stable. Our concrete questions are: 
> 
> 1.	Does IETF RMT consider the revision of LCT building block stable enough so that we can refer to that in OMA BCAST 1.0 specification?
> 
> 2.	What is estimated schedule for revising the RMT RFCs on the Standards Track?
> 
> 2	Requested Action(s)
> OMA BAC-BCAST requests IETF RMT to provide guidance on the two questions presented in this liaison.
> 
> 3	Conclusion
> 
> 
> We thank you for your consideration.
> 
> With best regards, 
> OMA BAC BCAST 
> (Mobile Broadcast Services sub working group)
> Attachment(s):
>      PDF of liaison statement (https://datatracker.ietf.org/documents/LIAISON/file400.pdf)
> 
> 

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



From rmt-bounces@ietf.org Wed Feb 21 21:16:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HK3UI-0000EJ-8H; Wed, 21 Feb 2007 21:15:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HK3UE-0000Bc-Rg
	for rmt@ietf.org; Wed, 21 Feb 2007 21:15:10 -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 1HK3QY-0001Fs-1Z
	for rmt@ietf.org; Wed, 21 Feb 2007 21:11:23 -0500
Received: from 67.110.226.222 ([67.110.226.222]) 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 ; Thu, 22 Feb 2007 02:11:16 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Wed, 21 Feb 2007 18:11:16 -0800
From: Mark Watson <mark@digitalfountain.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	"rmt@ietf.org" <rmt@ietf.org>, Michael Luby <luby@digitalfountain.com>,
	Lorenzo Vicisano <lorenzo@vicisano.net>
Message-ID: <C2023BC4.12F63%mark@digitalfountain.com>
Thread-Topic: AD comments on draft-ietf-rmt-bb-fec-revised-04
Thread-Index: AcdWJruh+e0visIZEduFFAAX8sJN9g==
In-Reply-To: <45C09B07.8080905@ericsson.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: 
Subject: [Rmt] Re: 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

Magnus,

Thanks for your comments and apologies for the delay in replying!

1. Ok
2. I have updated this to refer to "bulk data transfer over IP multicast".
"bulk data transfer" is the phrase used in RFC 2887 ("The Reliable Multicast
Design Space for Bulk Data Transfer")
3. I don't think there has been any recent discussion of this possibility. I
agree with you that it does not seem necessary to have dynamically
assignable FEC Payload ID types.
4. Strictly, of course, you are right. However, the terms "length" and
"size" are commonly (ab)used to refer to things measured in bytes or
multiples of bytes and (more importantly) this term is already embedded in
several other standards (3GPP and DVB). I'd prefer to leave the term as it
is if we can to avoid confusion.
5. I didn't quite follow the comment: The section recommends object
integrity and source authentication for the object and then recommends
packet authentication (e.g. TESLA). It doesn't refer to packet integrity
checking without authentication.
6. Ok
7. Ok

...Mark


On 1/31/07 5:35 AM, "Magnus Westerlund" <magnus.westerlund@ericsson.com>
wrote:

> 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



From rmt-bounces@ietf.org Wed Feb 21 21:28:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HK3hX-0004Tg-Vp; Wed, 21 Feb 2007 21:28:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HK3hX-0004TG-Ai
	for rmt@ietf.org; Wed, 21 Feb 2007 21:28:55 -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 1HK3hW-00008k-2N
	for rmt@ietf.org; Wed, 21 Feb 2007 21:28:55 -0500
Received: from 67.110.226.222 ([67.110.226.222]) 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 ; Thu, 22 Feb 2007 02:28:49 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Wed, 21 Feb 2007 18:28:48 -0800
From: Mark Watson <mark@digitalfountain.com>
To: "rmt@ietf.org" <rmt@ietf.org>
Message-ID: <C2023FE0.12F6A%mark@digitalfountain.com>
Thread-Topic: Question about draft-mehta-rmt-flute-sdp
Thread-Index: AcdWKS6rbV+fCcIcEduFFAAX8sJN9g==
Mime-version: 1.0
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: [Rmt] Question about draft-mehta-rmt-flute-sdp
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="===============0244280811=="
Errors-To: rmt-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0244280811==
Content-type: multipart/alternative;
	boundary="B_3254927329_1935314"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3254927329_1935314
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

It=B9s expired. Is it dead ? Or is it being progressed somewhere else ?

I had intended to propose re-use of some of these attributes in FECFRAME,
but if the proposal is dead then we=B9ll have to take a different tack.

...Mark

--B_3254927329_1935314
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Question about draft-mehta-rmt-flute-sdp</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>It&#8=
217;s expired. Is it dead ? Or is it being progressed somewhere else ?<BR>
<BR>
I had intended to propose re-use of some of these attributes in FECFRAME, b=
ut if the proposal is dead then we&#8217;ll have to take a different tack.<B=
R>
<BR>
...Mark</SPAN></FONT>
</BODY>
</HTML>


--B_3254927329_1935314--



--===============0244280811==
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

--===============0244280811==--





From rmt-bounces@ietf.org Thu Feb 22 11:37:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKGwq-00055a-GL; Thu, 22 Feb 2007 11:37:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKGwp-00055J-I4
	for rmt@ietf.org; Thu, 22 Feb 2007 11:37:35 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKGwi-0005qT-VN
	for rmt@ietf.org; Thu, 22 Feb 2007 11:37:35 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5967E21065; Thu, 22 Feb 2007 17:37:26 +0100 (CET)
X-AuditID: c1b4fb3e-af6d2bb0000007e1-84-45ddc6c61ad2 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	422572107A; Thu, 22 Feb 2007 17:37:26 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 Feb 2007 17:37:26 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 Feb 2007 17:37:25 +0100
Message-ID: <45DDC6C5.3040805@ericsson.com>
Date: Thu, 22 Feb 2007 17:37:25 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Mark Watson <mark@digitalfountain.com>
References: <C2023BC4.12F63%mark@digitalfountain.com>
In-Reply-To: <C2023BC4.12F63%mark@digitalfountain.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Feb 2007 16:37:25.0706 (UTC)
	FILETIME=[BBFD0AA0:01C7569F]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: Michael Luby <luby@digitalfountain.com>, rmt@ietf.org
Subject: [Rmt] Re: 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

Mark Watson skrev:
> 
> 
> Magnus,
> 
> Thanks for your comments and apologies for the delay in replying!
> 
> 1. Ok
> 2. I have updated this to refer to "bulk data transfer over IP multicast".
> "bulk data transfer" is the phrase used in RFC 2887 ("The Reliable Multicast
> Design Space for Bulk Data Transfer")

Okay

> 3. I don't think there has been any recent discussion of this possibility. I
> agree with you that it does not seem necessary to have dynamically
> assignable FEC Payload ID types.

This is okay. If we see us consuming a lot of the space then one can fix 
this. But so far there is no mad rush for FEC Payload ID numbers.

> 4. Strictly, of course, you are right. However, the terms "length" and
> "size" are commonly (ab)used to refer to things measured in bytes or
> multiples of bytes and (more importantly) this term is already embedded in
> several other standards (3GPP and DVB). I'd prefer to leave the term as it
> is if we can to avoid confusion.

I can buy that argument.

> 5. I didn't quite follow the comment: The section recommends object
> integrity and source authentication for the object and then recommends
> packet authentication (e.g. TESLA). It doesn't refer to packet integrity
> checking without authentication.

Re-reading section 11. My interpretation of this is that although the 
text mention source authentication is that it doesn't put enough stress 
on the need for authentication.

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



From rmt-bounces@ietf.org Thu Feb 22 15:13:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKKJH-0007M9-7k; Thu, 22 Feb 2007 15:12:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKKJG-0007M1-2X
	for rmt@ietf.org; Thu, 22 Feb 2007 15:12:58 -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 1HKKJE-0005Tb-OL
	for rmt@ietf.org; Thu, 22 Feb 2007 15:12:58 -0500
Received: from 64.2.18.5 ([64.2.18.5]) 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 ; Thu, 22 Feb 2007 20:12:55 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 22 Feb 2007 12:12:53 -0800
From: Mark Watson <mark@digitalfountain.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <C2033945.12F9F%mark@digitalfountain.com>
Thread-Topic: AD comments on draft-ietf-rmt-bb-fec-revised-04
Thread-Index: AcdWn749lsVpNTfeQZ6VCPPMJdnh/QAHhcHb
In-Reply-To: <45DDC6C5.3040805@ericsson.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: Michael Luby <luby@digitalfountain.com>, "rmt@ietf.org" <rmt@ietf.org>
Subject: [Rmt] Re: 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

Magnus,

Ok, I will beef up the text on authentication.

...Mark


On 2/22/07 8:37 AM, "Magnus Westerlund" <magnus.westerlund@ericsson.com>
wrote:

> Mark Watson skrev:
>> 
>> 
>> Magnus,
>> 
>> Thanks for your comments and apologies for the delay in replying!
>> 
>> 1. Ok
>> 2. I have updated this to refer to "bulk data transfer over IP multicast".
>> "bulk data transfer" is the phrase used in RFC 2887 ("The Reliable Multicast
>> Design Space for Bulk Data Transfer")
> 
> Okay
> 
>> 3. I don't think there has been any recent discussion of this possibility. I
>> agree with you that it does not seem necessary to have dynamically
>> assignable FEC Payload ID types.
> 
> This is okay. If we see us consuming a lot of the space then one can fix
> this. But so far there is no mad rush for FEC Payload ID numbers.
> 
>> 4. Strictly, of course, you are right. However, the terms "length" and
>> "size" are commonly (ab)used to refer to things measured in bytes or
>> multiples of bytes and (more importantly) this term is already embedded in
>> several other standards (3GPP and DVB). I'd prefer to leave the term as it
>> is if we can to avoid confusion.
> 
> I can buy that argument.
> 
>> 5. I didn't quite follow the comment: The section recommends object
>> integrity and source authentication for the object and then recommends
>> packet authentication (e.g. TESLA). It doesn't refer to packet integrity
>> checking without authentication.
> 
> Re-reading section 11. My interpretation of this is that although the
> text mention source authentication is that it doesn't put enough stress
> on the need for authentication.
> 
> 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



From rmt-bounces@ietf.org Thu Feb 22 15:44:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKKnS-0007lj-0c; Thu, 22 Feb 2007 15:44:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKKnQ-0007lT-RB
	for rmt@ietf.org; Thu, 22 Feb 2007 15:44:08 -0500
Received: from s2.itd.nrl.navy.mil ([132.250.83.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKKnP-0001o3-Jk
	for rmt@ietf.org; Thu, 22 Feb 2007 15:44:08 -0500
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by s2.itd.nrl.navy.mil (8.13.6+Sun/8.12.8) with SMTP id l1MKi1Vk013760; 
	Thu, 22 Feb 2007 15:44:01 -0500 (EST)
Received: from [192.168.1.201] ([132.250.218.64])
	by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.12.43) with SMTP id
	M2007022215440004532 ; Thu, 22 Feb 2007 15:44:01 -0500
Mime-Version: 1.0
Message-Id: <p06240804c203b06f6f1e@[192.168.1.201]>
In-Reply-To: <C2033945.12F9F%mark@digitalfountain.com>
References: <C2033945.12F9F%mark@digitalfountain.com>
Date: Thu, 22 Feb 2007 15:43:59 -0500
To: "rmt@ietf.org" <rmt@ietf.org>
From: Brian Adamson <adamson@itd.nrl.navy.mil>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: "rmt@ietf.org" <rmt@ietf.org>, Michael Luby <luby@digitalfountain.com>
Subject: [Rmt] draft-ietf-rmt-bb-fec-basic-schemes-revised resubmittal or
 resurrection
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

Hello,

The "draft-ietf-rmt-bb-fec-basic-schemes-revised" is expired and 
needs to be resubmitted or otherwise resurrected if possible.

Will one of the authors volunteer to do this?   I don't think the 
document requires any updating.  It has simply expired due to lack of 
action.  If we can revive it, I think it is more than ready for last 
call ...


-- 
Brian

Brian Adamson
<adamson@itd.nrl.navy.mil>

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



From rmt-bounces@ietf.org Thu Feb 22 17:00:48 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKLz7-0003vs-Vc; Thu, 22 Feb 2007 17:00:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKLz6-0003vk-EP
	for rmt@ietf.org; Thu, 22 Feb 2007 17:00:16 -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 1HKLz5-0003uo-6k
	for rmt@ietf.org; Thu, 22 Feb 2007 17:00:16 -0500
Received: from 64.2.18.5 ([64.2.18.5]) 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 ; Thu, 22 Feb 2007 22:00:14 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 22 Feb 2007 14:00:12 -0800
Subject: Re: [Rmt] draft-ietf-rmt-bb-fec-basic-schemes-revised resubmittal
	or resurrection
From: Mark Watson <mark@digitalfountain.com>
To: Brian Adamson <adamson@itd.nrl.navy.mil>,
	"rmt@ietf.org" <rmt@ietf.org>
Message-ID: <C203526C.12FB6%mark@digitalfountain.com>
Thread-Topic: [Rmt] draft-ietf-rmt-bb-fec-basic-schemes-revised
	resubmittal or resurrection
Thread-Index: AcdWwkVIhdigumZFTOaFXvoli8xGjgACo3rA
In-Reply-To: <p06240804c203b06f6f1e@[192.168.1.201]>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 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>
Errors-To: rmt-bounces@ietf.org

Brian,

I resubmitted it just an hour ago.

Also ALC and LCT, as well as the Raptor draft and the updated FEC Building
Block with Magnus' comments addressed. You should see them shortly.

...Mark


On 2/22/07 12:43 PM, "Brian Adamson" <adamson@itd.nrl.navy.mil> wrote:

> Hello,
> 
> The "draft-ietf-rmt-bb-fec-basic-schemes-revised" is expired and
> needs to be resubmitted or otherwise resurrected if possible.
> 
> Will one of the authors volunteer to do this?   I don't think the
> document requires any updating.  It has simply expired due to lack of
> action.  If we can revive it, I think it is more than ready for last
> call ...
> 


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



From rmt-bounces@ietf.org Fri Feb 23 15:14:26 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKgo3-00016J-JX; Fri, 23 Feb 2007 15:14:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKgo2-00015i-VW
	for rmt@ietf.org; Fri, 23 Feb 2007 15:14:14 -0500
Received: from s2.itd.nrl.navy.mil ([132.250.83.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKgnC-0008LC-RJ
	for rmt@ietf.org; Fri, 23 Feb 2007 15:13:24 -0500
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by s2.itd.nrl.navy.mil (8.13.6+Sun/8.12.8) with SMTP id l1NKDFsw008099
	for <rmt@ietf.org>; Fri, 23 Feb 2007 15:13:16 -0500 (EST)
Received: from [132.250.92.151] ([132.250.92.151])
	by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.12.43) with SMTP id
	M2007022315131409944
	for <rmt@ietf.org>; Fri, 23 Feb 2007 15:13:15 -0500
Mime-Version: 1.0
Message-Id: <p06230904c204e452d593@[132.250.92.151]>
Date: Fri, 23 Feb 2007 15:13:13 -0500
To: "rmt@ietf.org" <rmt@ietf.org>
From: Brian Adamson <adamson@itd.nrl.navy.mil>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Subject: [Rmt] draft-ietf-rmt-bb-fec-rs-02 Comments
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


1) The document currently defines a single FEC Encoding ID and a 
single EXT_FTI format.  I think the formats for FEC Payload and 
EXT_FTI providede are generally useful for 8 and 16 bit RS codes. 
But, it may be useful to additionally have separate FEC Encoding ID 
specifically for 8-bit Reed Solomon codes.  I propose that document 
_also_ assign a FEC Encoding ID for the fully-specified 8-bit (m = 8) 
Reed Solomon code and G =1.  Then a more compact EXT_FTI could be 
specified for this format.  The rationale for this is the case where 
very loosely coordinated multicast operation may wish to include 
EXT_FTI as part of the packet header.

E.g., for an m = 8, G = 1 RS code, the corresponding EXT_FTI could be:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |   HET = 64    |     HEL       |                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +
    |                      Transfer-Length (L)                      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |   Encoding Symbol Length (E)  | MaxBlkLen (B) |   max_n       |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


2) We may also wish to assign an "instance id" value for the 
underspecified small block systematic FEC codes (defined in the FEC 
Basic Schemes BB) that corresponds to this fully-specified protocol? 
This may seem unnecessary but the rationale for this is that the FEC 
Payload ID formats of that specification could then be used if 
desired.  More specifically, the FEC Payload ID format of the Small 
Block Systematic FEC Scheme has the "Source Block Length" field 
available if needed.

3) Section 6.4

Comment: There are a couple of minor editorial issues in wording of 
sentences in the first two paragraphs.  And I found the third 
paragraph difficult to read.  I also came up with an alternative 
"Figure 5" Here is a suggested rewording for these first three 
paragraphs of this section:

In a packet erasure channel, each packet (and symbol(s) since packets 
contain G >= 1 symbols) is either correctly received or erased.  The 
location of the erased symbols in the sequence of symbols must be 
known.  The following specification describes the use of Reed-Solomon 
codes for generating redundant symbols from the k source symbols and 
for recovering the source symbols from any set of k received symbols.

The k source symbols of a source block are assumed to be composed of 
S m-bit elements.  Each m-bit element corresponds to an element of 
the finite field GF(2^^m) through the polynomial representation 
(Section 6.1).  If some of the source symbols contain less than S 
elements, they are virtually padded with zero elements (it can be the 
case for the last symbol of the last block of the object).

The encoding process produces n-k repair symbols of size S m-bit 
elements where the k source symbols are also part of the total n 
encoding symbols (Figure 5) (i.e., a systematic FEC code).  The m-bit 
elements of the repair symbols are calculated using the corresponding 
m-bit elements of the source symbol set.  A logical j-th source 
vector, comprised of the j-th elements from the set of source 
symbols, is used to calculate a j-th encoding vector.  This j-th 
encoding vector then provides the j-th elements for the set encoding 
symbols calculated for the block.  As a systematic code, the first k 
encoding symbols are the same as the k source symbols and the last 
n-k repair symbols are the result of the Reed Solomon encoding.


        Input:  k source symbols

  0             j                                  S-1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|             |X|                                   | source symbol 0
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|             |X|                                   | source symbol 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

              . . .

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|             |X|                                   | source symbol k-1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                *

        +----------------+
        |                |
        |  generator     |
        |    matrix      |
        |      GM        |
        |   (k x n)      |
        |                |
        +----------------+

                |
                V

      Output: n encoding symbols (source + repair)

  0             j                                  S-1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|             |X|                                   | encoding symbol 0
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|             |X|                                   | encoding symbol 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

              . . .

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|             |Y|                                   | encoding symbol n-1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


         Figure 5: Packet encoding scheme


-- 
Brian
__________________________________
Brian Adamson
<mailto:adamson@itd.nrl.navy.mil>

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



From rmt-bounces@ietf.org Fri Feb 23 15:50:39 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhNA-0008Cf-5a; Fri, 23 Feb 2007 15:50:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhMh-0006aZ-KF; Fri, 23 Feb 2007 15:50:03 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HKhMh-0006QW-52; Fri, 23 Feb 2007 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id ACF8C329D0;
	Fri, 23 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HKhMg-00070B-IK; Fri, 23 Feb 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: <E1HKhMg-00070B-IK@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 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-06.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-06.txt
	Pages		: 52
	Date		: 2007-2-23
	
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-06.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-06.txt".

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

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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rmt-bb-fec-raptor-object-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

Content-Type: text/plain
Content-ID: <2007-2-23103420.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 Fri Feb 23 15:50:39 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhN9-0008BM-Sv; Fri, 23 Feb 2007 15:50:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhMi-0006bw-0I; Fri, 23 Feb 2007 15:50:04 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HKhMh-0006QU-75; Fri, 23 Feb 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 079DF26EC5;
	Fri, 23 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HKhMg-00070n-RA; Fri, 23 Feb 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: <E1HKhMg-00070n-RA@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: rmt@ietf.org
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-bb-lct-revised-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		: Layered Coding Transport (LCT) Building Block
	Author(s)	: M. Luby, et al.
	Filename	: draft-ietf-rmt-bb-lct-revised-05.txt
	Pages		: 42
	Date		: 2007-2-23
	
Layered Coding Transport (LCT) provides transport level support for
   reliable content delivery and stream delivery protocols.  LCT is
   specifically designed to support protocols using IP multicast, but
   also provides support to protocols that use unicast.  LCT is
   compatible with congestion control that provides multiple rate
   delivery to receivers and is also compatible with coding techniques
   that provide reliable delivery of content.  This document obsoletes
   RFC3451

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-lct-revised-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-lct-revised-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-lct-revised-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-2-23110114.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-lct-revised-05.txt

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

Content-Type: text/plain
Content-ID: <2007-2-23110114.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 Fri Feb 23 15:51:06 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhNe-0000om-W8; Fri, 23 Feb 2007 15:51:02 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhNB-0008FO-Ip; Fri, 23 Feb 2007 15:50:33 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HKhNB-0005YD-3j; Fri, 23 Feb 2007 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 0D97417628;
	Fri, 23 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HKhMg-00070d-Oo; Fri, 23 Feb 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: <E1HKhMg-00070d-Oo@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: rmt@ietf.org
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-fec-bb-revised-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		: Forward Error Correction (FEC) Building Block
	Author(s)	: M. Watson, et al.
	Filename	: draft-ietf-rmt-fec-bb-revised-05.txt
	Pages		: 32
	Date		: 2007-2-23
	
This document describes how to use Forward Error Correction (FEC)
   codes to efficiently provide and/or augment reliability for bulk data
   transfer over IP multicast.  This document defines a framework for
   the definition of the information that needs to be communicated in
   order to use an FEC code for bulk data transfer, in addition to the
   encoded data itself, and for definition of formats and codes for
   communcation of that information.  Both information communicated with
   the encoded data itself and information that needs to be communicated
   'out-of-band' are considered.  The procedures for specifying new FEC
   codes, defining the information communication requirements associated
   with those codes and registering them with the Internet Assigned
   Numbers Authority (IANA) are also described.  The requirements on
   Content Delivery Protocols which wish to use FEC codes defined within
   this framework are also defined.  The companion document titled, "The
   Use of Forward Error Correction (FEC) in Reliable Multicast"
   describes some applications of FEC codes for delivering content.
   This document obsoletes RFC3452.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-fec-bb-revised-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-fec-bb-revised-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-fec-bb-revised-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-2-23105815.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-2-23105815.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 Fri Feb 23 15:52:14 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhOd-0002R2-Mc; Fri, 23 Feb 2007 15:52:05 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhNC-0008I0-Cy; Fri, 23 Feb 2007 15:50:34 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HKhNC-0005YX-2u; Fri, 23 Feb 2007 15:50:34 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 355212ACFE;
	Fri, 23 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HKhMg-000710-Ud; Fri, 23 Feb 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: <E1HKhMg-000710-Ud@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 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-bb-fec-basic-schemes-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		: Basic Forward Error Correction (FEC) Schemes
	Author(s)	: M. Watson
	Filename	: draft-ietf-rmt-bb-fec-basic-schemes-revised-03.txt
	Pages		: 25
	Date		: 2007-2-23
	
This document provides FEC Scheme specifications according to the RMT
   FEC Building Block for the Compact No-Code FEC Scheme, the Small
   Block, Large Block and Expandable FEC Scheme, the Small Block
   Systematic FEC Scheme and the Compact FEC Scheme.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-basic-schemes-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-bb-fec-basic-schemes-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-bb-fec-basic-schemes-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-2-23111149.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-bb-fec-basic-schemes-revised-03.txt

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

Content-Type: text/plain
Content-ID: <2007-2-23111149.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 Fri Feb 23 16:27:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhOV-0002MT-Tx; Fri, 23 Feb 2007 15:51:56 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKhNB-0008GJ-PO; Fri, 23 Feb 2007 15:50:33 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HKhNB-0005YG-7s; Fri, 23 Feb 2007 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 2D4091764E;
	Fri, 23 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HKhMg-00070u-TV; Fri, 23 Feb 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: <E1HKhMg-00070u-TV@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: rmt@ietf.org
Subject: [Rmt] I-D ACTION:draft-ietf-rmt-pi-alc-revised-04.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		: Asynchronous Layered Coding (ALC) Protocol Instantiation
	Author(s)	: M. Luby, et al.
	Filename	: draft-ietf-rmt-pi-alc-revised-04.txt
	Pages		: 28
	Date		: 2007-2-23
	
This document describes the Asynchronous Layered Coding (ALC)
   protocol, a massively scalable reliable content delivery protocol.
   Asynchronous Layered Coding combines the Layered Coding Transport
   (LCT) building block, a multiple rate congestion control building
   block and the Forward Error Correction (FEC) building block to
   provide congestion controlled reliable asynchronous delivery of
   content to an unlimited number of concurrent receivers from a single
   sender.  This document obsoletes RFC3450.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-pi-alc-revised-04.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-pi-alc-revised-04.txt".

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

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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rmt-pi-alc-revised-04.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-2-23110452.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rmt-pi-alc-revised-04.txt

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

Content-Type: text/plain
Content-ID: <2007-2-23110452.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 Mon Feb 26 03:47:28 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLbVR-0004oh-1O; Mon, 26 Feb 2007 03:46:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLbVQ-0004oM-JC
	for rmt@ietf.org; Mon, 26 Feb 2007 03:46:48 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLbVF-0003BL-FO
	for rmt@ietf.org; Mon, 26 Feb 2007 03:46:48 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	AD6052042D; Mon, 26 Feb 2007 09:46:28 +0100 (CET)
X-AuditID: c1b4fb3c-ae7c5bb0000007de-56-45e29e646198 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9416820417; Mon, 26 Feb 2007 09:46:28 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 09:46:28 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Feb 2007 09:46:28 +0100
Message-ID: <45E29E63.3080300@ericsson.com>
Date: Mon, 26 Feb 2007 09:46:27 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Mark Watson <mark@digitalfountain.com>,  rmt@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Feb 2007 08:46:28.0212 (UTC)
	FILETIME=[9ADCA340:01C75982]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: 
Subject: [Rmt] One more comment on draft-ietf-rmt-fec-bb-revised-05
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 Mark,

It seems that you will have to do one more spin of this draft. There is 
a warning nit that has to do with that reference [5] is not used in the 
text. Either included it somewhere in the text or remove it from the list.

See the last one of the checked references.
http://tools.ietf.org/wg/rmt/draft-ietf-rmt-fec-bb-revised/draft-ietf-rmt-fec-bb-revised-05.nits.txt

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



From rmt-bounces@ietf.org Mon Feb 26 17:50:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLog6-0004vJ-Cp; Mon, 26 Feb 2007 17:50:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLnoY-0007lK-6U
	for rmt@ietf.org; Mon, 26 Feb 2007 16:55:22 -0500
Received: from s2.itd.nrl.navy.mil ([132.250.83.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLnnh-0006Mk-4E
	for rmt@ietf.org; Mon, 26 Feb 2007 16:54:30 -0500
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by s2.itd.nrl.navy.mil (8.13.6+Sun/8.12.8) with SMTP id l1QLs5TG028599
	for <rmt@ietf.org>; Mon, 26 Feb 2007 16:54:05 -0500 (EST)
Received: from [132.250.92.151] ([132.250.92.151])
	by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.12.43) with SMTP id
	M2007022616540424723
	for <rmt@ietf.org>; Mon, 26 Feb 2007 16:54:04 -0500
Mime-Version: 1.0
Message-Id: <p06230908c2090679d98b@[132.250.92.151]>
Date: Mon, 26 Feb 2007 16:54:03 -0500
To: rmt@ietf.org
From: Brian Adamson <adamson@itd.nrl.navy.mil>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [Rmt] Call for Agenda Items, 68th IETF - Prague
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


The RMT WG meeting at the 67th IETF is currently scheduled for 
Wednesday, 21 March 2007 from 1:00 - 3:00 PM.

If you have items to add to the agenda please contact Lorenzo 
<lorenzo@vicisano.net> and/or Brian <adamson@itd.nrl.navy.mil>.   The 
draft working group agenda is due by 7 March and a final revision by 
12 March, so please provide any input ASAP or by 6 March.



best regards,



-- 
Brian
__________________________________
Brian Adamson
<mailto:adamson@itd.nrl.navy.mil>

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



