draft-ietf-rmt-bb-lct

Last Version:	draft-ietf-rmt-bb-lct-04.txt		Tracker Entry
Date:	03-Mar-2006
Disposition:	RFC3451 (diff)
Previous Versions:	draft-ietf-rmt-bb-lct-04.txt (diff)[ps]    - 29-Mar-2004
	draft-ietf-rmt-bb-lct-04.txt (diff)[ps]    - 07-Jan-2003
	draft-ietf-rmt-bb-lct-03.txt (diff)[ps]    - 17-Feb-2002
	draft-ietf-rmt-bb-lct-02.txt (diff)[ps]    - 29-Nov-2001
	draft-ietf-rmt-bb-lct-01.txt (diff)[ps]    - 20-Oct-2001
	draft-ietf-rmt-bb-lct-00.txt (diff)    - 24-Jul-2001

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


        RFC 3451

        Title:      Layered Coding Transport (LCT) Building Block
        Author(s):  M. Luby, J. Gemmell, L. Vicisano, L. Rizzo,
                    M. Handley, J. Crowcroft
        Status:     Experimental
        Date:       December 2002
        Mailbox:    luby@digitalfountain.com, jgemmell@microsoft.com,
                    lorenzo@cisco.com, luigi@iet.unipi.it,
                    mjh@aciri.org, Jon.Crowcroft@cl.cam.ac.uk
        Pages:      29
        Characters: 72594
        Updates/Obsoletes/See Also:   None

        I-D Tag:    draft-ietf-rmt-bb-lct-04.txt

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


Layered Coding Transport (LCT) provides transport level
support for reliable content delivery and stream delivery
protocols.  LCT is specifically designed to support protocols
using IP multicast, but also provides support to protocols
that use unicast.  LCT is compatible with congestion control
that provides multiple rate delivery to receivers and is also
compatible with coding techniques that provide reliable
delivery of content.

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