headers
Internet-Drafts | 24 Aug 2010 22:15
Picon
Favicon

I-D Action:draft-ietf-rmt-bb-fec-raptorq-04.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           : RaptorQ Forward Error Correction Scheme for Object Delivery
	Author(s)       : M. Luby, et al.
	Filename        : draft-ietf-rmt-bb-fec-raptorq-04.txt
	Pages           : 68
	Date            : 2010-08-24

This document describes a Fully-Specified FEC scheme, corresponding
to FEC Encoding ID 6 (to be confirmed (tbc)), for the RaptorQ forward
error correction code and its application to reliable delivery of
data objects.

RaptorQ codes are a new family of codes that provide superior
flexibility, support for larger source block sizes and better coding
efficiency than Raptor codes in RFC5053.  RaptorQ is also 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 for most cases equal to the number of source
symbols and in rare cases with slightly more than the number of
source symbols.

The RaptorQ 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-raptorq-04.txt
(Continue reading)

Permalink | Reply | 0 comments |
headers
Luby, Michael | 24 Aug 2010 22:20

draft-ietf-rmt-bb-fec-raptorq-04

RMT participants,
I have just uploaded draft-ietf-rmt-bb-fec-raptorq-04 as a new Internet Draft, updating the draft-ietf-rmt-bb-fec-raptorq-03.  The only changes between the –03 and –04 drafts are a couple of small typos and the improved systematic index table shown in Section 5.6 (as we had indicated that we would be doing just after we submitted the –03 version).   

We have not heard any comments back from WGLC, and presumably enough time has passed for people to review and provide any WGLC they had?  (As noted earlier, there are a few different implementations of the RaptorQ codes at this point that have been shown to be inoperable, and through that process we received lots of feedback on the drafts).  There is nothing in this new –04 draft that should cause any additional comments beyond those provided on the –03 draft in WGLC (which was called on July 7 and was supposed to expire on July 23).
Mike Luby 
_______________________________________________
Rmt mailing list
Rmt <at> ietf.org
https://www.ietf.org/mailman/listinfo/rmt
Permalink | Reply | 0 comments |
headers
Luby, Michael | 25 Aug 2010 21:03

Re: Rmt Digest, Vol 73, Issue 1

BTW, as pointed out to me privately, “inoperable” should have been “interoperable” in the email I sent out yesterday.


On 8/25/10 12:00 PM, "rmt-request <at> ietf.org" <rmt-request <at> ietf.org> wrote:

If you have received this digest without all the individual message
attachments you will need to update your digest options in your list
subscription.  To do so, go to

https://www.ietf.org/mailman/listinfo/rmt

Click the 'Unsubscribe or edit options' button, log in, and set "Get
MIME or Plain Text Digests?" to MIME.  You can set this option
globally for all the list digests you receive at this point.



Send Rmt mailing list submissions to
 rmt <at> ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
 https://www.ietf.org/mailman/listinfo/rmt
or, via email, send a message with subject or body 'help' to
 rmt-request <at> ietf.org

You can reach the person managing the list at
 rmt-owner <at> ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rmt digest..."
_______________________________________________
Rmt mailing list
Rmt <at> ietf.org
https://www.ietf.org/mailman/listinfo/rmt
Permalink | Reply | 0 comments |
headers
Luby, Michael | 26 Aug 2010 19:28

More info about draft-ietf-rmt-bb-fec-raptorq-04

With respect to draft-ietf-rmt-bb-fec-raptorq-04, I should have also mentioned the following in my previous email:

As mentioned in the RaptorQ presentation given by Brian Adamson on our behalf during the RMT working group meeting at the recent IETF, the systematic index values provided in Section 5.6 were to be updated in the –04 draft after verification by simulation.  I wanted to verify that we did compute updated systematic index values for Section 5.6 and include them in the –04 draft, and we did run the many billions and billions of simulations to verify the properties of these updated values. We are confident that there will be no further changes to these systematic index values, as all of our rigorous tests were passed.

Mike Luby
 
_______________________________________________
Rmt mailing list
Rmt <at> ietf.org
https://www.ietf.org/mailman/listinfo/rmt
Permalink | Reply | 0 comments |

Gmane