FLUTE - File Delivery over Unidirectional Transport
draft-ietf-rmt-flute-revised-14

The information below is for an old version of the document
Document Type Active Internet-Draft (rmt WG)
Last updated 2012-05-14 (latest revision 2012-03-12)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs 6 more YES or NO OBJECTION positions to pass.
Responsible AD Martin Stiemerling
IESG note Needs ietf-types review and four downrefs in IETF LC.
Send notices to rmt-chairs@tools.ietf.org, draft-ietf-rmt-flute-revised@tools.ietf.org
Reliable Multicast Transport (RMT)                              T. Paila
Internet-Draft                                                     Nokia
Obsoletes: 3926 (if approved)                                   R. Walsh
Intended status: Standards Track        Tampere University of Technology
Expires: September 13, 2012                                      M. Luby
                                                          Qualcomm, Inc.
                                                                 V. Roca
                                                                   INRIA
                                                             R. Lehtonen
                                                             TeliaSonera
                                                          March 12, 2012

          FLUTE - File Delivery over Unidirectional Transport
                    draft-ietf-rmt-flute-revised-14

Abstract

   This document defines FLUTE, a protocol for the unidirectional
   delivery of files over the Internet, which is particularly suited to
   multicast networks.  The specification builds on Asynchronous Layered
   Coding, the base protocol designed for massively scalable multicast
   distribution.  This document obsoletes RFC3926.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 13, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Paila, et al.          Expires September 13, 2012               [Page 1]
Internet-Draft                    FLUTE                       March 2012

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Paila, et al.          Expires September 13, 2012               [Page 2]
Internet-Draft                    FLUTE                       March 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.  Applicability Statement  . . . . . . . . . . . . . . . . .  6
       1.1.1.  The Target Application Space . . . . . . . . . . . . .  6
       1.1.2.  The Target Scale . . . . . . . . . . . . . . . . . . .  6
       1.1.3.  Intended Environments  . . . . . . . . . . . . . . . .  7
       1.1.4.  Weaknesses . . . . . . . . . . . . . . . . . . . . . .  7
   2.  Conventions used in this Document  . . . . . . . . . . . . . .  8
   3.  File delivery  . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.1.  File delivery session  . . . . . . . . . . . . . . . . . .  9
     3.2.  File Delivery Table  . . . . . . . . . . . . . . . . . . . 11
     3.3.  Dynamics of FDT Instances within file delivery session . . 13
     3.4.  Structure of FDT Instance packets  . . . . . . . . . . . . 16
       3.4.1.  Format of FDT Instance Header  . . . . . . . . . . . . 17
       3.4.2.  Syntax of FDT Instance . . . . . . . . . . . . . . . . 18
       3.4.3.  Content Encoding of FDT Instance . . . . . . . . . . . 22
Show full document text