RFC 7826 on Real-Time Streaming Protocol Version 2.0

rfc-editor@rfc-editor.org Tue, 27 December 2016 19:30 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 (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5E136129B19; Tue, 27 Dec 2016 11:30:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.302
X-Spam-Status: No, score=-7.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id KVMfHgNx5sLi; Tue, 27 Dec 2016 11:30:37 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE1EF129B0C; Tue, 27 Dec 2016 11:30:36 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A6E88B803D9; Tue, 27 Dec 2016 11:30:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7826 on Real-Time Streaming Protocol Version 2.0
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161227193036.A6E88B803D9@rfc-editor.org>
Date: Tue, 27 Dec 2016 11:30:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/jPczdb6Jv2wgC-DE8s7pq4aqx5Y>
Cc: drafts-update-ref@iana.org, mmusic@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 27 Dec 2016 19:30:50 -0000

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

        RFC 7826

        Title:      Real-Time Streaming Protocol Version 2.0 
        Author:     H. Schulzrinne, A. Rao,
                    R. Lanphier, M. Westerlund,
                    M. Stiemerling, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2016
        Mailbox:    schulzrinne@cs.columbia.edu, 
        Pages:      318
        Characters: 746422
        Obsoletes:  RFC 2326

        I-D Tag:    draft-ietf-mmusic-rfc2326bis-40.txt

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

        DOI:        10.17487/RFC7826

This memorandum defines the Real-Time Streaming Protocol (RTSP)
version 2.0, which obsoletes RTSP version 1.0 defined in RFC 2326.

RTSP is an application-layer protocol for the setup and control of
the delivery of data with real-time properties.  RTSP provides an
extensible framework to enable controlled, on-demand delivery of
real-time data, such as audio and video.  Sources of data can include
both live data feeds and stored clips.  This protocol is intended to
control multiple data delivery sessions; provide a means for choosing
delivery channels such as UDP, multicast UDP, and TCP; and provide a
means for choosing delivery mechanisms based upon RTP (RFC 3550).

This document is a product of the Multiparty Multimedia Session Control 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/retrieve/bulk

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