RFC 7198 on Duplicating RTP Streams

rfc-editor@rfc-editor.org Fri, 25 April 2014 18:42 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 016CF1A06AE; Fri, 25 Apr 2014 11:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.174
X-Spam-Level:
X-Spam-Status: No, score=-102.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CCpvRsJf0r4U; Fri, 25 Apr 2014 11:42:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id AF35D1A06A9; Fri, 25 Apr 2014 11:42:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0BBDB1801FF; Fri, 25 Apr 2014 11:41:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7198 on Duplicating RTP Streams
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140425184112.0BBDB1801FF@rfc-editor.org>
Date: Fri, 25 Apr 2014 11:41:12 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/McC3syHeLfIIy-BpVrkC-nGreuw
Cc: drafts-update-ref@iana.org, avtext@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 25 Apr 2014 18:42:18 -0000

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

        
        RFC 7198

        Title:      Duplicating RTP Streams 
        Author:     A. Begen, C. Perkins
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2014
        Mailbox:    abegen@cisco.com, 
                    csp@csperkins.org
        Pages:      13
        Characters: 29317
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avtext-rtp-duplication-06.txt

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

Packet loss is undesirable for real-time multimedia sessions but can
occur due to a variety of reasons including unplanned network
outages.  In unicast transmissions, recovering from such an outage
can be difficult depending on the outage duration, due to the
potentially large number of missing packets.  In multicast
transmissions, recovery is even more challenging as many receivers
could be impacted by the outage.  For this challenge, one solution
that does not incur unbounded delay is to duplicate the packets and
send them in separate redundant streams, provided that the underlying
network satisfies certain requirements.  This document explains how
Real-time Transport Protocol (RTP) streams can be duplicated without
breaking RTP or RTP Control Protocol (RTCP) rules.

This document is a product of the Audio/Video Transport Extensions Working Group of the IETF.

This is now a Proposed Standard.

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/search
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