idnits 2.17.1 draft-ietf-rmt-pi-alc-08.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3450 5 Title: Asynchronous Layered Coding (ALC) Protocol 6 Instantiation 7 Author(s): M. Luby, J. Gemmell, L. Vicisano, L. Rizzo, 8 J. Crowcroft 9 Status: Experimental 10 Date: December 2002 11 Mailbox: luby@digitalfountain.com, jgemmell@microsoft.com, 12 lorenzo@cisco.com, luigi@iet.unipi.it, 13 Jon.Crowcroft@cl.cam.ac.uk 14 Pages: 34 15 Characters: 86022 16 Updates/Obsoletes/See Also: None 18 I-D Tag: draft-ietf-rmt-pi-alc-08.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3450.txt 22 This document describes the Asynchronous Layered Coding (ALC) 23 protocol, a massively scalable reliable content delivery protocol. 24 Asynchronous Layered Coding combines the Layered Coding Transport 25 (LCT) building block, a multiple rate congestion control building 26 block and the Forward Error Correction (FEC) building block to provide 27 congestion controlled reliable asynchronous delivery of content to an 28 unlimited number of concurrent receivers from a single sender. 30 This document is a product of the Reliable Multicast Transport Working 31 Group of the IETF. 33 This memo defines an Experimental Protocol for the Internet community. 34 It does not specify an Internet standard of any kind. Discussion and 35 suggestions for improvement are requested. Distribution of this memo 36 is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.