From rmt-bounces@ietf.org Fri Oct 1 01:37:22 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 BAA09004 for ; Fri, 1 Oct 2004 01:37:22 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDGF1-0005ur-Eq for rmt-web-archive@ietf.org; Fri, 01 Oct 2004 01:46:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDG2f-0006el-BX; Fri, 01 Oct 2004 01:33:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDFm1-0002wS-2A for rmt@megatron.ietf.org; Fri, 01 Oct 2004 01:16:05 -0400 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 BAA07247 for ; Fri, 1 Oct 2004 01:16:03 -0400 (EDT) Received: from mail2.cs.tut.fi ([130.230.4.14]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDFuO-0005U3-R2 for rmt@ietf.org; Fri, 01 Oct 2004 01:24:45 -0400 Received: from samipelt (samipelt.atm.tut.fi [130.230.52.31]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail2.cs.tut.fi (Postfix) with ESMTP id 7CC6A157936; Fri, 1 Oct 2004 08:15:29 +0300 (EEST) From: "Sami Peltotalo" To: "Rmt@ietf. org" Subject: RE: [Rmt] Fully-specified or Under-Specified Reed-Solomon Date: Fri, 1 Oct 2004 08:16:45 +0300 Message-ID: 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.6604 (9.0.2911.0) x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <1095448915.7552.382.camel@bog> X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Content-Transfer-Encoding: 7bit X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Multicast Transport List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rmt-bounces@ietf.org Errors-To: rmt-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Content-Transfer-Encoding: 7bit Hi All, Seems that this issue doesn't raise very much conversation. Why? Seems that there is only very few "active" members at the RMT group. Do we now have consensus about this issue? People have had three weeks time (or three months) to say their opinion. The initial proposal was Under-Specified FEC scheme. Now we have got two votes for Fully-Specified FEC scheme (Luby and Chapweske). Is this enough to change to Fully-Specified? Cheers, Sami > -----Original Message----- > From: rmt-bounces@ietf.org [mailto:rmt-bounces@ietf.org]On Behalf Of > Justin Chapweske > Sent: 17. syyskuuta 2004 22:22 > To: Michael Luby > Cc: Rmt@ietf. org > Subject: Re: [Rmt] Fully-specified or Under-Specified Reed-Solomon > > > I agree that it should be a Fully Specific scheme, though it would take > someone a bit of work to document the various polynomials used for 8 and > 16 bit codes, exactly how the matrices are generated, etc. > > To date, Luigi's code is the only real "documentation" of these > parameters and it would be nice to see documentation that would allow > interoperable implementation from a fresh code base. > > Thanks, > > -Justin > > On Fri, 2004-09-10 at 18:05 -0700, Michael Luby wrote: > > RMTers, > > > > One question that has come up in off-line discussions is how to > develop a > > Reed-Solomon based FEC codec, i.e. as either a Fully-Specified > FEC scheme or > > as an Under-Specified FEC scheme. > > > > I'm personally in favor of a Fully-Specified FEC scheme for a lot of > > reasons, but there are arguments on both sides. The purpose of > this email > > is not to provide those arguments, but to open up the dialog so > that in this > > email thread individuals can make the arguments on both sides > with the goal > > of finding a consensus answer to this question. > > > > Best, Mike > > > > > > _______________________________________________ > > Rmt mailing list > > Rmt@ietf.org > > https://www1.ietf.org/mailman/listinfo/rmt > -- > Justin Chapweske > > > _______________________________________________ > 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 mailman-bounces@ietf.org Fri Oct 1 09:33:37 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 JAA28480 for ; Fri, 1 Oct 2004 09:33:36 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDNfz-0007LW-6f for rmt-web-archive@ietf.org; Fri, 01 Oct 2004 09:42:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDK6M-0003kR-1I for rmt-web-archive@ietf.org; Fri, 01 Oct 2004 05:53:22 -0400 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: Date: Fri, 01 Oct 2004 05:20:37 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list 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 Sat Oct 2 11:54: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 LAA23934 for ; Sat, 2 Oct 2004 11:54:25 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDmM2-0005aP-Q2 for rmt-web-archive@ietf.org; Sat, 02 Oct 2004 12:03:26 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDm8t-0007lc-Rh; Sat, 02 Oct 2004 11:49:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDlyt-0004vH-UF for rmt@megatron.ietf.org; Sat, 02 Oct 2004 11:39:32 -0400 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 LAA23268 for ; Sat, 2 Oct 2004 11:39:29 -0400 (EDT) Received: from venus.open.ac.uk ([194.66.147.160]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDm7a-0005Ea-Do for rmt@ietf.org; Sat, 02 Oct 2004 11:48:30 -0400 Received: from oufcnt2.open.ac.uk (actually host halley.open.ac.uk) by venus.open.ac.uk via SMTP Local (Mailer 3.1) with ESMTP; Sat, 2 Oct 2004 16:38:48 +0100 Message-id: Date: Sat, 02 Oct 2004 16:38:47 +0100 Subject: Re: [Rmt] Fully-specified or Under-Specified Reed-Solomon To: Sami Peltotalo From: Andrew Marlow References: In-Reply-To: MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 8bit Cc: "Rmt@ietf. org" X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Multicast Transport List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rmt-bounces@ietf.org Errors-To: rmt-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: 8bit Sami Peltotalo on 01 October 2004 at 06:16 +0000 wrote: >Hi All, > >Seems that this issue doesn't raise very much conversation. Why? well I have a theory about that. The limited amount of discussion that does take place seems to be just in this mailing list. USENET stays pretty much silent and the RMT-related web sites remain as cobweb sites. When there are RMT developments perhaps these could be mentioned with a relevant URL, in various USENET groups. There are C/C++ experimental implementations, e.g the one by Brian Adamson, so mentions on comp.lang.c++ etc might generate more interest. Multicast is frequently raised on other forums such as the one on ACE (where they are currently experimenting with PGM) so a mention there would not go amiss, IMO. Regards, Andrew Marlow ---- There is an emerald here the size of a plover's egg! _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From rmt-bounces@ietf.org Tue Oct 5 19:56:46 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 TAA26762 for ; Tue, 5 Oct 2004 19:56:45 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEzK9-0004SM-3Y for rmt-web-archive@ietf.org; Tue, 05 Oct 2004 20:06:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEywB-0008Rn-8w; Tue, 05 Oct 2004 19:41:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEynj-0006nR-Lp; Tue, 05 Oct 2004 19:32:59 -0400 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 TAA23567; Tue, 5 Oct 2004 19:32:56 -0400 (EDT) Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEyx7-0008QX-4X; Tue, 05 Oct 2004 19:42:41 -0400 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 i95NVZJ00665; Tue, 5 Oct 2004 16:31:35 -0700 (PDT) Message-Id: <200410052331.i95NVZJ00665@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: Tue, 05 Oct 2004 16:31:35 -0700 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: e1b0e72ff1bbd457ceef31828f216a86 Cc: rmt@ietf.org, rfc-editor@rfc-editor.org Subject: [Rmt] RFC 3926 on FLUTE - File Delivery over Unidirectional Transport X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Multicast Transport List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rmt-bounces@ietf.org Errors-To: rmt-bounces@ietf.org X-Spam-Score: -14.6 (--------------) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3926 Title: FLUTE - File Delivery over Unidirectional Transport Author(s): T. Paila, M. Luby, R. Lehtonen, V. Roca, R. Walsh Status: Experimental Date: October 2004 Mailbox: toni.paila@nokia.com, luby@digitalfountain.com, rami.lehtonen@teliasonera.com, vincent.roca@inrialpes.fr, rod.walsh@nokia.com Pages: 35 Characters: 81224 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rmt-flute-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3926.txt This document defines FLUTE, a protocol for the unidirectional delivery of files over the Internet, which is particularly suited to multicast networks. The specification builds on Asynchronous Layered Coding, the base protocol designed for massively scalable multicast distribution. 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: <041005163030.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3926 --OtherAccess Content-Type: Message/External-body; name="rfc3926.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <041005163030.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 Thu Oct 14 17:11: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 RAA04975 for ; Thu, 14 Oct 2004 17:11:25 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CID3w-0005Rt-AB for rmt-web-archive@ietf.org; Thu, 14 Oct 2004 17:23:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CICO3-0006wm-JQ; Thu, 14 Oct 2004 16:39:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIC6D-0000ov-0L; Thu, 14 Oct 2004 16:21:21 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25765; Thu, 14 Oct 2004 16:21:18 -0400 (EDT) Message-Id: <200410142021.QAA25765@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 14 Oct 2004 16:21:18 -0400 Cc: rmt@ietf.org Subject: [Rmt] I-D ACTION:draft-ietf-rmt-bb-tfmcc-04.txt X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Multicast Transport List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rmt-bounces@ietf.org Errors-To: rmt-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b --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 : TCP-Friendly Multicast Congestion Control (TFMCC):Protocol Specification Author(s) : J. Widmer, M. Handley Filename : draft-ietf-rmt-bb-tfmcc-04.txt,.ps Pages : 30 Date : 2004-10-14 This document specifies TCP-Friendly Multicast Congestion Control (TFMCC). TFMCC is a congestion control mechanism for multicast transmissions in a best-effort Internet environment. It is a single-rate congestion control scheme, where the sending rate is adapted to the receiver experiencing the worst network conditions. TFMCC is reasonably fair when competing for bandwidth with TCP flows and has a relatively low variation of throughput over time, making it suitable for applications such as streaming media where a relatively smooth sending rate is of importance. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-tfmcc-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-bb-tfmcc-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-bb-tfmcc-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: <2004-10-14164606.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rmt-bb-tfmcc-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rmt-bb-tfmcc-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-14164606.I-D@ietf.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 Oct 22 19:01:44 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 TAA10076 for ; Fri, 22 Oct 2004 19:01:44 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL8cj-00084V-So for rmt-web-archive@ietf.org; Fri, 22 Oct 2004 19:15:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL7qu-0007z6-HA; Fri, 22 Oct 2004 18:25:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL7QO-0001X8-W8 for rmt@megatron.ietf.org; Fri, 22 Oct 2004 17:58:17 -0400 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 RAA26775 for ; Fri, 22 Oct 2004 17:58:12 -0400 (EDT) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL7dE-000449-Sz for rmt@ietf.org; Fri, 22 Oct 2004 18:11:34 -0400 Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-5.cisco.com with ESMTP; 22 Oct 2004 14:57:58 -0700 X-BrightmailFiltered: true Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i9MLvm9b024770 for ; Fri, 22 Oct 2004 14:57:48 -0700 (PDT) Received: (from lorenzo@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id OAA11877 for rmt@ietf.org; Fri, 22 Oct 2004 14:57:48 -0700 (PDT) Date: Fri, 22 Oct 2004 14:57:48 -0700 From: Lorenzo Vicisano To: rmt@ietf.org Message-ID: <20041022145748.F23112@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: a7d6aff76b15f3f56fcb94490e1052e4 Subject: [Rmt] [mankin@psg.com: remind authors to update their IPR boilerplate, please!] X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Multicast Transport List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rmt-bounces@ietf.org Errors-To: rmt-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 RMT authors, please check Allison's note below about the new IPR boilerplate for ID submissions. thanks, Lorenzo ----- Forwarded message from Allison Mankin ----- X-BrightmailFiltered: true X-Ironport-AV: i="3.86,94,1096873200"; d="scan'208"; a="6778872:sNHT19519392" To: tsv-chairs@ietf.org Subject: remind authors to update their IPR boilerplate, please! Reply-To: mankin@psg.com Date: Fri, 22 Oct 2004 09:26:24 -0700 From: Allison Mankin X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f X-PMX-Version: 4.7.0.111621 X-from-outside-Cisco: 128.107.234.205 Folks, Please please remind everyone to update their IPR boilerplate to RFC 3667, or, even better, the fixed version, as documented in http://www.ietf.org/ietf/1id-guidelines.txt. Right at the 00 cutoff, the Secretariat somewhat graciously (or with gritted teeth, I'm not sure which) let at least three TSV id-s re-submit after the IPR boilerplate bounced them. But the Secretariat might not feel they need to do this for Oct 25 cutoff, especially if they get a lot of these bounces, since the number of submissions is high, and they have a lot of other work right then. So please get all authors to be extra careful! Allison and Jon ----- End forwarded message ----- _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From rmt-bounces@ietf.org Fri Oct 29 03:39:35 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 DAA03062 for ; Fri, 29 Oct 2004 03:39:35 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNRaU-0007jt-Ic for rmt-web-archive@ietf.org; Fri, 29 Oct 2004 03:54:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNRDv-0006qp-KZ; Fri, 29 Oct 2004 03:30:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNQyh-0007PW-TB for rmt@megatron.ietf.org; Fri, 29 Oct 2004 03:15:16 -0400 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 DAA01555 for ; Fri, 29 Oct 2004 03:15:13 -0400 (EDT) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNRCu-0007Fb-BS for rmt@ietf.org; Fri, 29 Oct 2004 03:29:57 -0400 Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-4.cisco.com with ESMTP; 29 Oct 2004 00:16:42 -0700 X-BrightmailFiltered: true Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i9T7Ee1m010087; Fri, 29 Oct 2004 00:14:40 -0700 (PDT) Received: (from lorenzo@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id AAA27935; Fri, 29 Oct 2004 00:14:40 -0700 (PDT) Date: Fri, 29 Oct 2004 00:14:40 -0700 From: Lorenzo Vicisano To: rmt@ietf.org Message-ID: <20041029001440.B25547@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: 08e48e05374109708c00c6208b534009 Cc: Lorenzo Vicisano , Roger Kermode Subject: [Rmt] call for aganda items X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Multicast Transport List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rmt-bounces@ietf.org Errors-To: rmt-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad for the Washington IETF. RMT is scheduled to meet Tuesday, November 9 from 14:15 to 15:15. Please reply to this email with your request. Thank you, the Chairs. _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From rmt-bounces@ietf.org Fri Oct 29 04:05:34 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 EAA05470 for ; Fri, 29 Oct 2004 04:05:34 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNRze-00009s-DU for rmt-web-archive@ietf.org; Fri, 29 Oct 2004 04:20:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNRPH-00065b-5a; Fri, 29 Oct 2004 03:42:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNRG6-0000U1-Pq for rmt@megatron.ietf.org; Fri, 29 Oct 2004 03:33:14 -0400 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 DAA02720 for ; Fri, 29 Oct 2004 03:33:11 -0400 (EDT) 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 1CNRUH-0007c1-29 for rmt@ietf.org; Fri, 29 Oct 2004 03:47:56 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 29 Oct 2004 00:42:04 -0700 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 i9T7WbQ0024627 for ; Fri, 29 Oct 2004 00:32:37 -0700 (PDT) Received: (from lorenzo@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id AAA03987; Fri, 29 Oct 2004 00:32:37 -0700 (PDT) Date: Fri, 29 Oct 2004 00:32:37 -0700 From: Lorenzo Vicisano To: rmt@ietf.org Message-ID: <20041029003237.C25547@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: 68c8cc8a64a9d0402e43b8eee9fc4199 Subject: [Rmt] WG last call for draft-ietf-rmt-bb-tfmcc-04.txt X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Multicast Transport List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rmt-bounces@ietf.org Errors-To: rmt-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Please be advised that starting today October 29, draft-ietf-rmt-bb-tfmcc-04.txt is in WG last call. You are invited to reply to this email with your feedback by November 19. You can also comment in person at the upcoming IETF RMT meeting. Please note that the last call period is longer than usual due to its ovelap with the IETF meeting. Thank you, The chairs. _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From rmt-bounces@ietf.org Fri Oct 29 04:20:54 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 EAA06767 for ; Fri, 29 Oct 2004 04:20:54 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNSEU-0000WQ-47 for rmt-web-archive@ietf.org; Fri, 29 Oct 2004 04:35:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNRpc-0005li-VM; Fri, 29 Oct 2004 04:09:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNRaP-0003hX-2T for rmt@megatron.ietf.org; Fri, 29 Oct 2004 03:54:13 -0400 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 DAA04352 for ; Fri, 29 Oct 2004 03:54:11 -0400 (EDT) Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNRoa-0008Ey-WE for rmt@ietf.org; Fri, 29 Oct 2004 04:08:56 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-1.cisco.com with ESMTP; 29 Oct 2004 01:05:21 -0700 X-BrightmailFiltered: true Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9T7rbLO012277 for ; Fri, 29 Oct 2004 00:53:37 -0700 (PDT) Received: (from lorenzo@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id AAA06203; Fri, 29 Oct 2004 00:53:36 -0700 (PDT) Date: Fri, 29 Oct 2004 00:53:36 -0700 From: Lorenzo Vicisano To: rmt@ietf.org Message-ID: <20041029005336.B4894@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: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [Rmt] WG last call for draft-ietf-rmt-bb-pgmcc-03.txt X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Multicast Transport List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rmt-bounces@ietf.org Errors-To: rmt-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Please be advised that starting today October 29, draft-ietf-rmt-bb-pgmcc-03.txt is in WG last call. You are invited to reply to this email with your feedback by November 19. You can also comment in person at the upcoming IETF RMT meeting. Please note that the last call period is longer than usual due to its overlap with the IETF meeting. Thank you, The chairs. _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From rmt-bounces@ietf.org Fri Oct 29 09:42:18 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 JAA29104 for ; Fri, 29 Oct 2004 09:42:18 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNXFa-0007HU-1D for rmt-web-archive@ietf.org; Fri, 29 Oct 2004 09:57:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNWhk-0007fi-Kb; Fri, 29 Oct 2004 09:22:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNWZz-0001A7-0A for rmt@megatron.ietf.org; Fri, 29 Oct 2004 09:14:07 -0400 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 JAA27269 for ; Fri, 29 Oct 2004 09:14:05 -0400 (EDT) From: Rod.Walsh@nokia.com Received: from mgw-x3.nokia.com ([131.228.20.26]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNWoF-0006gW-KZ for rmt@ietf.org; Fri, 29 Oct 2004 09:28:53 -0400 Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121]) by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i9TDE3l07567 for ; Fri, 29 Oct 2004 16:14:03 +0300 (EET DST) X-Scanned: Fri, 29 Oct 2004 16:13:36 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i9TDDaW7014594 for ; Fri, 29 Oct 2004 16:13:36 +0300 Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks002.ntc.nokia.com 00NafsOX; Fri, 29 Oct 2004 12:56:41 EEST Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i9T9ufS20033 for ; Fri, 29 Oct 2004 12:56:41 +0300 (EET DST) Received: from esebe016.NOE.Nokia.com ([172.21.138.55]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 29 Oct 2004 12:56:33 +0300 Received: from trebe051.NOE.Nokia.com ([172.22.124.60]) by esebe016.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 29 Oct 2004 12:56:33 +0300 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 Date: Fri, 29 Oct 2004 12:56:32 +0300 Message-ID: Thread-Topic: [AVT] Work on FEC framework for RTP within 3GPP Thread-Index: AcS8/XIMlvUHMygNTtmRJlxuMQQzAQAn39yA To: X-OriginalArrivalTime: 29 Oct 2004 09:56:33.0222 (UTC) FILETIME=[921EBE60:01C4BD9D] X-Spam-Score: 0.3 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Content-Transfer-Encoding: quoted-printable Subject: [Rmt] FW: [AVT] Work on FEC framework for RTP within 3GPP X-BeenThere: rmt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Multicast Transport List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rmt-bounces@ietf.org Errors-To: rmt-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Content-Transfer-Encoding: quoted-printable FYI... (After this I guess anyone from RMT who's interested will be subscribed = to AVT, so no more mass forwarding from me on this subject :) Cheers, Rod. -----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=20 that is ongoing within the 3GPP SA4. It was agreed in the SA4 ad hoc=20 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=20 instead of session multiplexed. - The FEC payload header (the "FEC Tag") will be moved from last in the=20 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=20 available in time for the next SA4 meeting (22-26th Nov). The=20 specification text needs to be approved on that meeting to meet the=20 current deadline. Comments on the approach is solicited. 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 _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt