[Rmt] RFC 6726 on FLUTE - File Delivery over Unidirectional Transport

rfc-editor@rfc-editor.org Tue, 06 November 2012 21:53 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rmt@ietfa.amsl.com
Delivered-To: rmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E33D21F843D; Tue, 6 Nov 2012 13:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level:
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-bpNPygZT8a; Tue, 6 Nov 2012 13:53:27 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id CF22B21F8900; Tue, 6 Nov 2012 13:53:27 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1BB7EB1E01A; Tue, 6 Nov 2012 13:46:57 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121106214657.1BB7EB1E01A@rfc-editor.org>
Date: Tue, 6 Nov 2012 13:46:57 -0800 (PST)
Cc: rmt@ietf.org, rfc-editor@rfc-editor.org
Subject: [Rmt] RFC 6726 on FLUTE - File Delivery over Unidirectional Transport
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmt>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 21:53:28 -0000

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

        
        RFC 6726

        Title:      FLUTE - File Delivery over 
                    Unidirectional Transport 
        Author:     T. Paila, R. Walsh,
                    M. Luby, V. Roca,
                    R. Lehtonen
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2012
        Mailbox:    toni.paila@gmail.com, 
                    roderick.walsh@tut.fi, 
                    luby@qti.qualcomm.com,
                    vincent.roca@inria.fr, 
                    rami.lehtonen@teliasonera.com
        Pages:      46
        Characters: 108261
        Obsoletes:  RFC3926

        I-D Tag:    draft-ietf-rmt-flute-revised-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6726.txt

This document defines File Delivery over Unidirectional Transport
(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 RFC 3926.  [STANDARDS-TRACK]

This document is a product of the Reliable Multicast Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC