draft-ietf-mmusic-rfc2326bis-35.txt   draft-ietf-mmusic-rfc2326bis-36.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: March 6, 2014 R. Lanphier Expires: March 15, 2014 R. Lanphier
M. Westerlund M. Westerlund
Ericsson AB Ericsson AB
M. Stiemerling (Ed.) M. Stiemerling (Ed.)
NEC NEC
September 2, 2013 September 11, 2013
Real Time Streaming Protocol 2.0 (RTSP) Real Time Streaming Protocol 2.0 (RTSP)
draft-ietf-mmusic-rfc2326bis-35 draft-ietf-mmusic-rfc2326bis-36
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 March 6, 2014. This Internet-Draft will expire on March 15, 2014.
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 38, line 7 skipping to change at page 38, line 7
Section 18.17) and Content-Type (see Section 18.19). A message body Section 18.17) and Content-Type (see Section 18.19). A message body
MUST NOT be included in a request or response if the specification of MUST NOT be included in a request or response if the specification of
the particular method (see Method Definitions (Section 13)) does not the particular method (see Method Definitions (Section 13)) does not
allow sending a message body. In case a message body is received in allow sending a message body. In case a message body is received in
a message when not expected the message body data SHOULD be a message when not expected the message body data SHOULD be
discarded. This is to allow future extensions to define optional use discarded. This is to allow future extensions to define optional use
of message body. of message body.
5.4. Message Length 5.4. Message Length
RTSP Messages that doesn't contain any message body is terminated by An RTSP Message that does not contain any message body is terminated
the first empty line after the header fields (Note: An empty line is by the first empty line after the header fields (Note: An empty line
a line with nothing preceding the CRLF.). In RTSP messages that is a line with nothing preceding the CRLF.). In RTSP messages that
contains message bodies the empty line is followed by the message contain message bodies the empty line is followed by the message
body. The length of that body is determined by the value of the body. The length of that body is determined by the value of the
Content-Length header (Section 18.17). The headers value represents Content-Length header (Section 18.17). The value in the header
the length of the message-body in octets. If this header field is represents the length of the message-body in octets. If this header
not present, a value of zero is assumed, i.e. no message body present field is not present, a value of zero is assumed, i.e., no message
in message. Unlike an HTTP message, an RTSP message MUST contain a body present in the message. Unlike an HTTP message, an RTSP message
Content-Length header whenever it contains a message body. Note that MUST contain a Content-Length header whenever it contains a message
RTSP does not support the HTTP/1.1 "chunked" transfer coding (see body. Note that RTSP does not support the HTTP/1.1 "chunked"
[H3.6.1]). transfer coding (see [H3.6.1]).
Given the moderate length of presentation descriptions returned, Given the moderate length of presentation descriptions returned,
the server should always be able to determine its length, even if the server should always be able to determine its length, even if
it is generated dynamically, making the chunked transfer encoding it is generated dynamically, making the chunked transfer encoding
unnecessary. unnecessary.
6. General Header Fields 6. General Header Fields
General headers are headers that may be used in both requests and General headers are headers that may be used in both requests and
responses. The general headers are listed in Table 1: responses. The general headers are listed in Table 1:
skipping to change at page 46, line 35 skipping to change at page 46, line 35
no 300 (Multiple Choices in HTTP) is defined for RTSP. An response no 300 (Multiple Choices in HTTP) is defined for RTSP. An response
with unrecognized status code MUST NOT be cached. For example, if an with unrecognized status code MUST NOT be cached. For example, if an
unrecognized status code of 431 is received by the client, it can unrecognized status code of 431 is received by the client, it can
safely assume that there was something wrong with its request and safely assume that there was something wrong with its request and
treat the response as if it had received a 400 status code. In such treat the response as if it had received a 400 status code. In such
cases, user agents SHOULD present to the user the message body cases, user agents SHOULD present to the user the message body
returned with the response, since that message body is likely to returned with the response, since that message body is likely to
include human-readable information which will explain the unusual include human-readable information which will explain the unusual
status. status.
+--------------------------------+-------------------------+--------+ +------+---------------------------------+--------------------------+
| Code | Reason | Method | | Code | Reason | Method |
+--------------------------------+-------------------------+--------+ +------+---------------------------------+--------------------------+
| 100 | Continue | all | | 100 | Continue | all |
| | | | | | | |
| | | | | | | |
| 200 | OK | all | | 200 | OK | all |
| | | | | | | |
| | | | | | | |
| 301 | Moved Permanently | all | | 301 | Moved Permanently | all |
| | | | | | | |
| 302 | Found | all | | 302 | Found | all |
| | | | | | | |
| 303 | reserved | n/a | | 303 | reserved | n/a |
| | | | | | | |
| 304 | Not Modified | all | | 304 | Not Modified | all |
| | | | | | | |
| 305 | Use Proxy | all | | 305 | Use Proxy | all |
| 400 | Bad Request | all | | 400 | Bad Request | all |
| | | | | | | |
| 401 | Unauthorized | all | | 401 | Unauthorized | all |
| | | | | | | |
| 402 | Payment Required | all | | 402 | Payment Required | all |
| | | | | | | |
| 403 | Forbidden | all | | 403 | Forbidden | all |
| | | | | | | |
| 404 | Not Found | all | | 404 | Not Found | all |
| | | | | | | |
| 405 | Method Not Allowed | all | | 405 | Method Not Allowed | all |
| | | | | | | |
| 406 | Not Acceptable | all | | 406 | Not Acceptable | all |
| | | | | | | |
| 407 | Proxy Authentication | all | | 407 | Proxy Authentication Required | all |
| | Required | | | | | |
| | | | | 408 | Request Timeout | all |
| 408 | Request Timeout | all | | | | |
| | | | | 410 | Gone | all |
| 410 | Gone | all | | | | |
| | | | | 412 | Precondition Failed | DESCRIBE, SETUP |
| Precondition Failed | DESCRIBE, SETUP | 413 | | | | |
| | | | | 413 | Request Message Body Too Large | all |
| Request Message Body Too Large | all | 414 | | | | |
| | | | | 414 | Request-URI Too Long | all |
| Request-URI Too Long | all | 415 | | | | |
| | | | | 415 | Unsupported Media Type | all |
| Unsupported Media Type | all | 451 | | | | |
| | | | | 451 | Parameter Not Understood | SET_PARAMETER, |
| Parameter Not Understood | SET_PARAMETER, | 452 | | | | GET_PARAMETER |
| | GET_PARAMETER | | | | | |
| | | | | 452 | reserved | n/a |
| reserved | n/a | 453 | | | | |
| | | | | 453 | Not Enough Bandwidth | SETUP |
| Not Enough Bandwidth | SETUP | 454 | | | | |
| | | | | 454 | Session Not Found | all |
| Session Not Found | all | 455 | | | | |
| | | | | 455 | Method Not Valid In This State | all |
| Method Not Valid In This State | all | 456 | | | | |
| | | | | 456 | Header Field Not Valid | all |
| Header Field Not Valid | all | 457 | | | | |
| | | | | 457 | Invalid Range | PLAY, PAUSE |
| Invalid Range | PLAY, PAUSE | 458 | | | | |
| | | | | 458 | Parameter Is Read-Only | SET_PARAMETER |
| Parameter Is Read-Only | SET_PARAMETER | 459 | | | | |
| | | | | 459 | Aggregate Operation Not Allowed | all |
| Aggregate Operation Not | all | 460 | | | | |
| Allowed | | | | 460 | Only Aggregate Operation | all |
| Only Aggregate Operation | all | 461 | | | Allowed | |
| Allowed | | | | | | |
| | | | | 461 | Unsupported Transport | all |
| Unsupported Transport | all | 462 | | | | |
| | | | | 462 | Destination Unreachable | all |
| Destination Unreachable | all | 463 | | | | |
| | | | | 463 | Destination Prohibited | SETUP |
| Destination Prohibited | SETUP | 464 | | | | |
| | | | | 464 | Data Transport Not Ready Yet | PLAY |
| Data Transport Not Ready Yet | PLAY | 465 | | | | |
| | | | | 465 | Notification Reason Unknown | PLAY_NOTIFY |
| Notification Reason Unknown | PLAY_NOTIFY | 466 | | | | |
| | | | | 466 | Key Management Error | all |
| Key Management Error | all | 470 | | | | |
| | | | | 470 | Connection Authorization | all |
| Connection Authorization | all | 471 | | | Required | |
| Required | | | | | | |
| | | | | 471 | Connection Credentials not | all |
| Connection Credentials not | all | 472 | | | accepted | |
| accepted | | | | | | |
| | | | | 472 | Failure to establish secure | all |
| Failure to establish secure | all | | | | connection | |
| connection | | | | | | |
| | | | | | | |
| | | 500 | | 500 | Internal Server Error | all |
| | | | | | | |
| Internal Server Error | all | 501 | | 501 | Not Implemented | all |
| | | | | | | |
| Not Implemented | all | 502 | | 502 | Bad Gateway | all |
| | | | | | | |
| Bad Gateway | all | 503 | | 503 | Service Unavailable | all |
| | | | | | | |
| Service Unavailable | all | 504 | | 504 | Gateway Timeout | all |
| | | | | | | |
| Gateway Timeout | all | 505 | | 505 | RTSP Version Not Supported | all |
| | | | | | | |
| RTSP Version Not Supported | all | 551 | | 551 | Option Not Supported | all |
| | | | | | | |
| Option Not Supported | all | 553 | | 553 | Proxy Unavailable | all |
| | | | +------+---------------------------------+--------------------------+
| Proxy Unavailable | all | |
+--------------------------------+-------------------------+--------+
Table 4: Status codes and their usage with RTSP methods Table 4: Status codes and their usage with RTSP methods
8.2. Response Headers 8.2. Response Headers
The response-headers allow the request recipient to pass additional The response-headers allow the request recipient to pass additional
information about the response which cannot be placed in the Status- information about the response which cannot be placed in the Status-
Line. This header gives information about the server and about Line. This header gives information about the server and about
further access to the resource identified by the Request-URI. All further access to the resource identified by the Request-URI. All
headers currently classified as response headers are listed in headers currently classified as response headers are listed in
 End of changes. 7 change blocks. 
123 lines changed or deleted 121 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/