draft-ietf-rmt-pi-alc

Last Version:	draft-ietf-rmt-pi-alc-08.txt		Tracker Entry
Date:	03-Mar-2006
Disposition:	RFC3450 (diff)
Previous Versions:	draft-ietf-rmt-pi-alc-08.txt (diff)[ps]    - 29-Mar-2004
	draft-ietf-rmt-pi-alc-08.txt (diff)[ps]    - 07-Jan-2003
	draft-ietf-rmt-pi-alc-07.txt (diff)[ps]    - 06-May-2002
	draft-ietf-rmt-pi-alc-06.txt (diff)[ps]    - 30-Mar-2002
	draft-ietf-rmt-pi-alc-05.txt (diff)[ps]    - 17-Feb-2002
	draft-ietf-rmt-pi-alc-04.txt (diff)[ps]    - 17-Feb-2002
	draft-ietf-rmt-pi-alc-03.txt (diff)[ps]    - 29-Nov-2001
	draft-ietf-rmt-pi-alc-02.txt (diff)[ps]    - 23-Jun-2001
	draft-ietf-rmt-pi-alc-01.txt (diff)    - 07-Dec-2000
	draft-ietf-rmt-pi-alc-00.txt (diff)    - 19-Jul-2000

A new Request for Comments is now available in online RFC libraries.


        RFC 3450

        Title:      Asynchronous Layered Coding (ALC) Protocol
                    Instantiation
        Author(s):  M. Luby, J. Gemmell, L. Vicisano, L. Rizzo,
                    J. Crowcroft
        Status:     Experimental
        Date:       December 2002
        Mailbox:    [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected]
        Pages:      34
        Characters: 86022
        Updates/Obsoletes/See Also:   None

        I-D Tag:    draft-ietf-rmt-pi-alc-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3450.txt


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 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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.