RFC 5740 on NACK-Oriented Reliable Multicast (NORM) Transport Protocol

rfc-editor@rfc-editor.org Tue, 24 November 2009 00:36 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 737B33A6B08; Mon, 23 Nov 2009 16:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.132
X-Spam-Status: No, score=-17.132 tagged_above=-999 required=5 tests=[AWL=-0.133, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id YznXe1-n6tTM; Mon, 23 Nov 2009 16:36:26 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id 6DEC73A6B1B; Mon, 23 Nov 2009 16:36:25 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id BE494372B82; Mon, 23 Nov 2009 16:31:14 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5740 on NACK-Oriented Reliable Multicast (NORM) Transport Protocol
From: rfc-editor@rfc-editor.org
Message-Id: <20091124003114.BE494372B82@bosco.isi.edu>
Date: Mon, 23 Nov 2009 16:31:14 -0800
Cc: rmt@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2009 00:36:27 -0000

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

        RFC 5740

        Title:      NACK-Oriented Reliable Multicast (NORM) Transport 
        Author:     B. Adamson, C. Bormann,
                    M. Handley, J. Macker
        Status:     Standards Track
        Date:       November 2009
        Mailbox:    adamson@itd.nrl.navy.mil, 
        Pages:      96
        Characters: 268831
        Obsoletes:  RFC3940

        I-D Tag:    draft-ietf-rmt-pi-norm-revised-14.txt

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

This document describes the messages and procedures of the Negative-
ACKnowledgment (NACK) Oriented Reliable Multicast (NORM) protocol.
This protocol can provide end-to-end reliable transport of bulk data
objects or streams over generic IP multicast routing and forwarding
services.  NORM uses a selective, negative acknowledgment mechanism
for transport reliability and offers additional protocol mechanisms
to allow for operation with minimal a priori coordination among
senders and receivers.  A congestion control scheme is specified to
allow the NORM protocol to fairly share available network bandwidth
with other transport protocols such as Transmission Control Protocol
(TCP).  It is capable of operating with both reciprocal multicast
routing among senders and receivers and with asymmetric connectivity
(possibly a unicast return path) between the senders and receivers.
The protocol offers a number of features to allow different types of
applications or possibly other higher-level transport protocols to
utilize its service in different ways.  The protocol leverages the
use of FEC-based (forward error correction) repair and other IETF
Reliable Multicast Transport (RMT) building blocks in its design.
This document obsoletes RFC 3940.  [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

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
USC/Information Sciences Institute