RFC 7728 on RTP Stream Pause and Resume

rfc-editor@rfc-editor.org Fri, 05 February 2016 23:57 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 3F29C1B302F; Fri, 5 Feb 2016 15:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id t0RYt62cKll1; Fri, 5 Feb 2016 15:57:39 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D376B1B302E; Fri, 5 Feb 2016 15:57:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id BD527180014; Fri, 5 Feb 2016 15:57:19 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7728 on RTP Stream Pause and Resume
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160205235719.BD527180014@rfc-editor.org>
Date: Fri, 05 Feb 2016 15:57:19 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/kdfUGu9445dAzCjuX996NfrhEQs>
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: <https://mailarchive.ietf.org/arch/browse/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, 05 Feb 2016 23:57:41 -0000

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

        RFC 7728

        Title:      RTP Stream Pause and Resume 
        Author:     B. Burman, 
                    A. Akram,
                    R. Even, 
                    M. Westerlund
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2016
        Mailbox:    bo.burman@ericsson.com, 
        Pages:      55
        Characters: 135619
        Updates:    RFC 5104

        I-D Tag:    draft-ietf-avtext-rtp-stream-pause-10.txt

        URL:        https://www.rfc-editor.org/info/rfc7728

        DOI:        http://dx.doi.org/10.17487/RFC7728

With the increased popularity of real-time multimedia applications,
it is desirable to provide good control of resource usage, and users
also demand more control over communication sessions.  This document
describes how a receiver in a multimedia conversation can pause and
resume incoming data from a sender by sending real-time feedback
messages when using the Real-time Transport Protocol (RTP) for real-
time data transport.  This document extends the Codec Control Message
(CCM) RTP Control Protocol (RTCP) feedback package by explicitly
allowing and describing specific use of existing CCMs and adding a
group of new real-time feedback messages used to pause and resume RTP
data streams.  This document updates RFC 5104.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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 https://www.rfc-editor.org/search
For downloading RFCs, see https://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