RFC 3451 (rfc3451) - Page 2 of 29


Layered Coding Transport (LCT) Building Block



Alternative Format: Original Text Document



RFC 3451                   LCT Building Block              December 2002


Table of Contents

   1. Introduction...................................................2
   2. Rationale......................................................3
   3. Functionality..................................................4
   4. Applicability..................................................7
     4.1 Environmental Requirements and Considerations...............8
     4.2 Delivery service models....................................10
     4.3 Congestion Control.........................................11
   5. Packet Header Fields..........................................12
     5.1 Default LCT header format..................................12
     5.2 Header-Extension Fields....................................17
   6. Operations....................................................20
     6.1 Sender Operation...........................................20
     6.2 Receiver Operation.........................................22
   7. Requirements from Other Building Blocks.......................23
   8. Security Considerations.......................................24
   9. IANA Considerations...........................................25
   10. Acknowledgments..............................................25
   11. References...................................................25
   Authors' Addresses...............................................28
   Full Copyright Statement.........................................29

1.  Introduction

   Layered Coding Transport provides transport level support for
   reliable content delivery and stream delivery protocols.  Layered
   Coding Transport is specifically designed to support protocols using
   IP multicast, but also provides support to protocols that use
   unicast.  Layered Coding Transport 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 describes a building block as defined in RFC 3048 [26].
   This document is a product of the IETF RMT WG  and follows the
   general guidelines provided in RFC 3269 [24].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119 [2].










Luby, et. al.                 Experimental