From rmt-bounces@ietf.org Thu Apr 12 17:50:34 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc7BZ-0007bv-NK; Thu, 12 Apr 2007 17:50:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc7BY-0007Zs-73 for rmt@ietf.org; Thu, 12 Apr 2007 17:50:32 -0400 Received: from hu-out-0506.google.com ([72.14.214.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc7BV-0007DR-SE for rmt@ietf.org; Thu, 12 Apr 2007 17:50:32 -0400 Received: by hu-out-0506.google.com with SMTP id 38so600832huc for ; Thu, 12 Apr 2007 14:50:29 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=eZbRlbsx7XNc6ecXxCMAIh07jd0jFWASOe5wBcNEsLBAkxzNpavS+hQ5zk3rjrFnHHvbcnulxm+D30DBMUNEK2ayY8AjGP9uONpnhZLJFBuMhQlqOpj2OuLGUw/bcMLnwQghnnID/+fRujVPu6Yyo3K7CV87PAXofj+hnPOuy0c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=IdccMByVxy7fAWnd7tURYDru98awDWCrFCh0ZiNwhIUeJNFA9iqLMQNbURuQQ15qe3iTLKDB0ZsZ+r7f0V3m2JEKyX/gssyfu3fV2gGyMYBnZF0PL4EEj5rSvu2wlDN4VH0VxZxac54oH3Qsu/y6Nyvnoyg9neF7r39uf9T4bmc= Received: by 10.78.123.4 with SMTP id v4mr528268huc.1176414628811; Thu, 12 Apr 2007 14:50:28 -0700 (PDT) Received: by 10.78.43.3 with HTTP; Thu, 12 Apr 2007 14:50:28 -0700 (PDT) Message-ID: <38c19b540704121450k611cfa11ic3ff20deee967849@mail.gmail.com> Date: Thu, 12 Apr 2007 14:50:28 -0700 From: "Greg Shepherd" To: fecframe@ietf.org, rmt@ietf.org, mmusic@ietf.org, avt@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.1 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Cc: Subject: [Rmt] Request For FEC Schemes 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: , Content-Type: multipart/mixed; boundary="===============1517963195==" Errors-To: rmt-bounces@ietf.org --===============1517963195== Content-Type: multipart/alternative; boundary="----=_Part_30859_12924349.1176414628761" ------=_Part_30859_12924349.1176414628761 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Greetings, >From the 68th IETF meeting in Prague, the FECFrame working group came away with some action items which we need to get to in order stay on track with our milestones: 1) Streaming Content Delivery Protocol Define specific protocol elements for signalling the use of FEC SDP, in particular, requires coordination with mmusic, avt and rmt - thus the current distribution. Call for volunteers to participate as the part of a Design Team. 2) Call for FEC Schemes: Like the RMT FEC Building Block, we should define the requirements that FECFRAME FEC Schemes should meet; Data elements that must be defined Procedures that must be defined Format for FEC Scheme specifications If you're interested enough to be on this list, and/or interested enough to attend the WG meetings, then you must be interested enough to see this through to functional result - please step-up. Thanks, Greg ------=_Part_30859_12924349.1176414628761 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Greetings,

From the 68th IETF meeting in Prague, the FECFrame working group came away with some action items which we need to get to in order stay on track with our milestones:

1) Streaming Content Delivery Protocol
       Define specific protocol elements for signalling the use of FEC
       SDP, in particular, requires coordination with mmusic, avt and rmt - thus the current distribution.
       Call for volunteers to participate as the part of a Design Team.


2) Call for FEC Schemes:

     Like the RMT FEC Building Block, we should define the requirements that FECFRAME FEC Schemes should meet;
          Data elements that must be defined
          Procedures that must be defined
          Format for FEC Scheme specifications

If you're interested enough to be on this list, and/or interested enough to attend the WG meetings, then you must be interested enough to see this through to functional result - please step-up.

Thanks,
Greg

------=_Part_30859_12924349.1176414628761-- --===============1517963195== 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 --===============1517963195==-- From rmt-bounces@ietf.org Wed Apr 18 18:50:49 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeIzA-0001lp-1L; Wed, 18 Apr 2007 18:50:48 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeIyv-0001Iy-9y; Wed, 18 Apr 2007 18:50:33 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HeIyu-0005nq-UY; Wed, 18 Apr 2007 18:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id AE63317634; Wed, 18 Apr 2007 22:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HeIyQ-00038q-FT; Wed, 18 Apr 2007 18:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 18 Apr 2007 18:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Cc: rmt@ietf.org Subject: [Rmt] I-D ACTION:draft-ietf-rmt-fec-bb-revised-07.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: , 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-07.txt Pages : 33 Date : 2007-4-18 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-07.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-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rmt-fec-bb-revised-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-4-18160138.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rmt-fec-bb-revised-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rmt-fec-bb-revised-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-4-18160138.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 Apr 23 16:50:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg5UR-0000Gr-GC; Mon, 23 Apr 2007 16:50:27 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg5UO-0000DZ-54; Mon, 23 Apr 2007 16:50:24 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hg5UM-0003Ly-RT; Mon, 23 Apr 2007 16:50:24 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id BD7E82AD89; Mon, 23 Apr 2007 20:49:52 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hg5Ts-0005sa-Hf; Mon, 23 Apr 2007 16:49:52 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 23 Apr 2007 16:49:52 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Cc: rmt chair , Internet Architecture Board , rmt mailing list , RFC Editor Subject: [Rmt] Protocol Action: 'Forward Error Correction (FEC) Building Block' to Proposed Standard 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: , Errors-To: rmt-bounces@ietf.org The IESG has approved the following document: - 'Forward Error Correction (FEC) Building Block ' as a Proposed Standard This document is the product of the Reliable Multicast Transport Working Group. The IESG contact persons are Magnus Westerlund and Lars Eggert. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rmt-fec-bb-revised-07.txt Technical Summary This document describes how to use Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for data transport. This document defines a framework for the definition of the information that needs to be communicated in order to use an FEC code for delivering content, in addition to the encoded data itself, and for definition of formats and codes for communication of that information. 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. This document is a building block upon which other specification of the RMT WG are based. Working Group Summary There is consensus in the WG to publish these documents. Protocol Quality A previous version of this document was reviewed by the IESG and published as RFC 3452. The current version does not differ significantly from RFC 3452 and it allows backward compatible implementation of known protocols that used RFC 3452. The content of this document is the base for a number of existing protocol implementations, both complying to this version of the document and to the previous version documented in RFC 3452. There are multiple independent implementations of 2 different protocols, known as NORM and ALC, that use the specification in this document. Different implementations of each protocols are interoperable. ALC is also adopted in the 3GPP standard TS26.346. Personell Lorenzo Vicisano is the Document Shepherd. Magnus Westerlund the responsible AD. Note to RFC Editor Section 15.2: OLD: [7] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, April 1992. NEW: [7] Federal Information Processing Standards Publication (FIPS PUB) 180-1, Secure Hash Standard, 17 April 1995. _______________________________________________ Rmt mailing list Rmt@ietf.org https://www1.ietf.org/mailman/listinfo/rmt From rmt-bounces@ietf.org Mon Apr 30 15:50:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HibtR-0005No-Ir; Mon, 30 Apr 2007 15:50:41 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HibtJ-00058D-Ql; Mon, 30 Apr 2007 15:50:33 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HibtJ-00033C-5B; Mon, 30 Apr 2007 15:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id C69EE175E0; Mon, 30 Apr 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hibso-0001l7-ED; Mon, 30 Apr 2007 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 30 Apr 2007 15:50:02 -0400 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-08.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: , 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-08.txt Pages : 53 Date : 2007-4-30 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-08.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-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rmt-bb-fec-raptor-object-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-4-30144552.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rmt-bb-fec-raptor-object-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rmt-bb-fec-raptor-object-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-4-30144552.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--