Request For FEC Schemes

_______________________________________________
mmusic mailing list
mmusic <at> ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

Re: Request For FEC Schemes

I am interested. Please let me know the next step.

  Andrea Vitali (STMicroelectronics)

> 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
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/avt

--

-- 
 ______________________________________________________________

  Andrea VITALI                            andrea.vitali <at> st.com

  tel (+39) 039 603 7244             mobile (+39) 347 93 08 433
  fax (+39) 039 603 6129

  STMicroelectronics
  Centro Direzionale COLLEONI - Palazzo "DIALETTICA"
  20041 Agrate Brianza (MI) ITALY
 ______________________________________________________________

_______________________________________________
Audio/Video Transport Working Group
avt <at> ietf.org
https://www1.ietf.org/mailman/listinfo/avt

I-D ACTION:draft-ietf-rmt-fec-bb-revised-07.txt

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 <at> 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 <at> 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.

_______________________________________________
Rmt mailing list
Rmt <at> ietf.org
https://www1.ietf.org/mailman/listinfo/rmt

Protocol Action: 'Forward Error Correction (FEC) Building Block' to Proposed Standard

The IESG has approved the following document:

- 'Forward Error Correction (FEC) Building Block '
   <draft-ietf-rmt-fec-bb-revised-07.txt> 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.

I-D ACTION:draft-ietf-rmt-bb-fec-raptor-object-08.txt

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 <at> 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 <at> 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.

_______________________________________________
Rmt mailing list
Rmt <at> ietf.org
https://www1.ietf.org/mailman/listinfo/rmt

Last Call: draft-ietf-rmt-bb-fec-raptor-object (Raptor Forward Error Correction Scheme for Object Delivery) to Proposed Standard

The IESG has received a request from the Reliable Multicast Transport WG 
(rmt) to consider the following document:

- 'Raptor Forward Error Correction Scheme for Object Delivery '
   <draft-ietf-rmt-bb-fec-raptor-object-08.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2007-05-15. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-raptor-object-08.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=12920&rfc_flag=0