Protocol Action: 'Real Time Streaming Protocol 2.0 (RTSP)' to Proposed Standard (draft-ietf-mmusic-rfc2326bis-40.txt)

The IESG <> Tue, 11 February 2014 15:58 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 610601A0583; Tue, 11 Feb 2014 07:58:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vXh4rf8wgjE2; Tue, 11 Feb 2014 07:58:16 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id A67EC1A0602; Tue, 11 Feb 2014 07:58:08 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'Real Time Streaming Protocol 2.0 (RTSP)' to Proposed Standard (draft-ietf-mmusic-rfc2326bis-40.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 11 Feb 2014 07:58:08 -0800
Cc: mmusic chair <>, mmusic mailing list <>, RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 11 Feb 2014 15:58:18 -0000

The IESG has approved the following document:
- 'Real Time Streaming Protocol 2.0 (RTSP)'
  (draft-ietf-mmusic-rfc2326bis-40.txt) as Proposed Standard

This document is the product of the Multiparty Multimedia Session Control
Working Group.

The IESG contact persons are Gonzalo Camarillo and Richard Barnes.

A URL of this Internet Draft is:

Technical Summary

The document defines RTSP version 2.0 which obsoletes RTSP version 1.0 defined in RFC 2326.

The Real Time Streaming Protocol, or RTSP, is an application-level protocol for 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).

Working Group Summary

The document has been work in progress for an extended period of time dating back to 2002. Earlier versions saw decent WG participation however the later versions have primarily been driven by the document authors with limited overall discussion in the group, especially towards the end of the process. There are no known issues or major discussion points, and there has been no indication of lack of consensus in the WG.

Document Quality

The document has been reviewed in detail several times after WGLC and in preparation for the publication request and the authors have made several updates as a result of those. The document is considered to be of high quality at this point.

There is one known implementation of the specification, and many of the extensions compared to RTSP 1.0 have been implemented separately as well.

A Media type review was done for "text/parameters". The review thread can be found at:

Document Shepherd: Flemming Andreasen
Responsible AD: Gonzalo Camarillo

RFC Editor's Note:

Section 2 of this document and its subsections provide "an informative overview
of the different mechanisms in the RTSP 2.0 protocol, to give the reader a high
level understanding".  As such, it's very important that it be clear and well
written.  Some reviewers have found the English to be difficult.  Please take
an especially critical pen to this section, making sure that the grammar and
usage are correct, and that the language is clear.