draft-ietf-mmusic-rfc2326bis-33.txt   draft-ietf-mmusic-rfc2326bis-34.txt 
MMUSIC Working Group H. Schulzrinne MMUSIC Working Group H. Schulzrinne
Internet-Draft Columbia University Internet-Draft Columbia University
Obsoletes: 2326 (if approved) A. Rao Obsoletes: 2326 (if approved) A. Rao
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: September 23, 2013 R. Lanphier Expires: October 6, 2013 R. Lanphier
M. Westerlund M. Westerlund
Ericsson AB Ericsson AB
M. Stiemerling (Ed.) M. Stiemerling (Ed.)
NEC NEC
March 22, 2013 April 4, 2013
Real Time Streaming Protocol 2.0 (RTSP) Real Time Streaming Protocol 2.0 (RTSP)
draft-ietf-mmusic-rfc2326bis-33 draft-ietf-mmusic-rfc2326bis-34
Abstract Abstract
This memorandum defines RTSP version 2.0 which obsoletes RTSP version This memorandum defines RTSP version 2.0 which obsoletes RTSP version
1.0 defined in RFC 2326. 1.0 defined in RFC 2326.
The Real Time Streaming Protocol, or RTSP, is an application-level The Real Time Streaming Protocol, or RTSP, is an application-level
protocol for setup and control of the delivery of data with real-time protocol for setup and control of the delivery of data with real-time
properties. RTSP provides an extensible framework to enable properties. RTSP provides an extensible framework to enable
controlled, on-demand delivery of real-time data, such as audio and controlled, on-demand delivery of real-time data, such as audio and
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 23, 2013. This Internet-Draft will expire on October 6, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 274, line 16 skipping to change at page 274, line 16
The Session Description Protocol (SDP, [RFC4566]) may be used to The Session Description Protocol (SDP, [RFC4566]) may be used to
describe streams or presentations in RTSP. This description is describe streams or presentations in RTSP. This description is
typically returned in reply to a DESCRIBE request on an URI from a typically returned in reply to a DESCRIBE request on an URI from a
server to a client, or received via HTTP from a server to a client. server to a client, or received via HTTP from a server to a client.
This appendix describes how an SDP file determines the operation of This appendix describes how an SDP file determines the operation of
an RTSP session. Thus, it is worth pointing out that the an RTSP session. Thus, it is worth pointing out that the
interpretation of the SDP is done in the context of the SDP receiver, interpretation of the SDP is done in the context of the SDP receiver,
which is the one being configured. This is the same as in SAP which is the one being configured. This is the same as in SAP
[RFC2974]; this differs from SDP Offer/Answer [RFC3264] where the SDP [RFC2974]; this differs from SDP Offer/Answer [RFC3264] where each
describes what the agent providing the SDP is ready to receive and SDP is interpreted in the context of the agent providing it.
willing to send.
SDP as is provides no mechanism by which a client can distinguish, SDP as is provides no mechanism by which a client can distinguish,
without human guidance, between several media streams to be rendered without human guidance, between several media streams to be rendered
simultaneously and a set of alternatives (e.g., two audio streams simultaneously and a set of alternatives (e.g., two audio streams
spoken in different languages). The SDP extension "Grouping of Media spoken in different languages). The SDP extension "Grouping of Media
Lines in the Session Description Protocol (SDP)" [RFC5888] provides Lines in the Session Description Protocol (SDP)" [RFC5888] provides
such functionality to some degree. Appendix D.4 describes the usage such functionality to some degree. Appendix D.4 describes the usage
of SDP media line grouping for RTSP. of SDP media line grouping for RTSP.
D.1. Definitions D.1. Definitions
 End of changes. 5 change blocks. 
7 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/