没有合适的资源?快使用搜索试试~ 我知道了~
首页RTSP 协议 规范 pdf
该协议用于C/S模型,是一个基于文本的协议,用于在客户端和服务器端建立和协商实时流会话。 实时流协议(RTSP)是应用级协议,控制实时数据的发送。RTSP提供了一个可扩展框架,使实时数据,如音频与视频,的受控、点播成为可能。数据源包括现场数据与存储在剪辑中数据。该协议目的在于控制多个数据发送连接,为选择发送通道,如UDP、组播UDP与TCP,提供途径,并为选择基于RTP上发送机制提供方法。 实时流协议(RTSP)建立并控制一个或几个时间同步的连续流媒体。尽管连续媒体流与控制流交换是可能的,通常它本身并不发送连续流。换言之,RTSP充当多媒体服务器的网络远程控制。RTSP连接没有绑定到传输层连接,如TCP。在RTSP连接期间,RTSP用户可打开或关闭多个对服务器的可传输连接以发出RTSP请求。此外,可使用无连接传输协议,如UDP。RTSP流控制的流可能用到RTP,但RTSP操作并不依赖用于携带连续媒体的传输机制。 协议支持的操作如下: (1)从媒体服务器上检索媒体:用户可通过HTTP或其它方法提交一个演示描述。如演示是组播,演示式就包含用于连续媒体的的组播地址和端口。如演示仅通过单播发送给用户,用户为了安全应提供目的地址。 (2)媒体服务器邀请进入会议:媒体服务器可被邀请参加正进行的会议,或回放媒体,或记录其中一部分,或全部。这种模式在分布式教育应用上很有用,会议中几方可轮流按远程控制按钮。 (3)将媒体加到现成讲座中:如服务器告诉用户可获得附加媒体内容,对现场讲座显得尤其有用。如HTTP/1.1中类似,RTSP请求可由代理、通道与缓存处理
资源详情
资源推荐
Internet Engineering Task Force MMUSIC WG
INTERNET-DRAFT H. Schulzrinne, A. Rao, R. Lanphier
draft-ietf-mmusic-rtsp-09.ps Columbia U./Netscape/RealNetworks
February 2, 1998
Expires: August 2, 1998
Real Time Streaming Protocol (RTSP)
Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced,
or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as “work in progress”.
To learn the current status of any Internet-Draft, please check the “1id-abstracts.txt” listing contained
in the Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au
(Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast).
Distribution of this document is unlimited.
Copyright Notice
Copyright (c) The Internet Society (1998). All Rights Reserved.
Abstract
The Real Time Streaming Protocol, or RTSP, is an application-level protocol for control over 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 1889).
Contents
1 Introduction 5
1.1 Purpose ............................................. 5
1.2 Requirements .......................................... 6
1.3 Terminology........................................... 6
1.4 Protocol Properties ....................................... 8
1.5 ExtendingRTSP......................................... 9
1.6 OverallOperation........................................ 10
1.7 RTSPStates........................................... 10
1.8 RelationshipwithOtherProtocols ............................... 11
2 Notational Conventions 11
3 Protocol Parameters 11
3.1 RTSPVersion.......................................... 11
3.2 RTSPURL ........................................... 12
INTERNET-DRAFT draft-ietf-mmusic-rtsp-09.ps February 2, 1998
3.3 ConferenceIdentifiers...................................... 13
3.4 SessionIdentifiers........................................ 13
3.5 SMPTERelativeTimestamps.................................. 13
3.6 NormalPlayTime........................................ 13
3.7 AbsoluteTime.......................................... 14
3.8 OptionTags........................................... 14
3.8.1 RegisteringNewOptionTagswithIANA....................... 15
4 RTSP Message 15
4.1 MessageTypes ......................................... 15
4.2 MessageHeaders ........................................ 15
4.3 MessageBody.......................................... 16
4.4 MessageLength......................................... 16
5 General Header Fields 16
6 Request 16
6.1 RequestLine .......................................... 17
6.2 RequestHeaderFields ..................................... 17
7 Response 18
7.1 Status-Line ........................................... 18
7.1.1 StatusCodeandReasonPhrase ............................ 18
7.1.2 Response Header Fields ................................ 20
8 Entity 20
8.1 Entity Header Fields ...................................... 20
8.2 Entity Body ........................................... 22
9 Connections 22
9.1 Pipelining............................................ 22
9.2 Reliability and Acknowledgements . . . ............................ 22
10 Method Definitions 23
10.1 OPTIONS ........................................... 23
10.2 DESCRIBE ........................................... 24
10.3 ANNOUNCE .......................................... 25
10.4 SETUP ............................................. 26
10.5 PLAY .............................................. 27
10.6 PAUSE ............................................. 28
10.7 TEARDOWN .......................................... 29
10.8 GET
PARAMETER ...................................... 30
10.9 SET
PARAMETER ...................................... 30
10.10REDIRECT ........................................... 31
10.11RECORD ............................................ 31
10.12Embedded(Interleaved)BinaryData.............................. 32
H. Schulzrinne, A. Rao, R. Lanphier Expires August 2, 1998 [Page 2]
INTERNET-DRAFT draft-ietf-mmusic-rtsp-09.ps February 2, 1998
11 Status Code Definitions 33
11.1 Success 2xx ........................................... 33
11.1.1 250LowonStorageSpace............................... 33
11.2Redirection3xx......................................... 33
11.3ClientError4xx......................................... 33
11.3.1 405MethodNotAllowed ............................... 33
11.3.2 451ParameterNotUnderstood............................. 33
11.3.3 452 Conference Not Found . . . ............................ 33
11.3.4 453 Not Enough Bandwidth . . ............................ 33
11.3.5 454 Session Not Found ................................. 33
11.3.6 455MethodNotValidinThisState .......................... 34
11.3.7 456HeaderFieldNotValidforResource ....................... 34
11.3.8 457InvalidRange ................................... 34
11.3.9 458ParameterIsRead-Only.............................. 34
11.3.10459AggregateOperationNotAllowed ........................ 34
11.3.11460OnlyAggregateOperationAllowed........................ 34
11.3.12 461 Unsupported Transport . . ............................ 34
11.3.13 462 Destination Unreachable . . ............................ 34
11.3.14 551 Option not supported . . . ............................ 34
12 Header Field Definitions 34
12.1 Accept . ............................................. 35
12.2 Accept-Encoding . ....................................... 35
12.3 Accept-Language . ....................................... 35
12.4Allow .............................................. 35
12.5Authorization .......................................... 35
12.6Bandwidth............................................ 37
12.7Blocksize ............................................ 37
12.8Cache-Control.......................................... 37
12.9Conference ........................................... 39
12.10Connection ........................................... 39
12.11Content-Base .......................................... 39
12.12Content-Encoding........................................ 39
12.13Content-Language . ....................................... 39
12.14Content-Length ......................................... 39
12.15Content-Location ........................................ 40
12.16Content-Type .......................................... 40
12.17CSeq............................................... 40
12.18Date............................................... 40
12.19Expires ............................................. 40
12.20From............................................... 41
12.21Host............................................... 41
12.22If-Match ............................................. 41
12.23If-Modified-Since . ....................................... 41
12.24Last-Modified.......................................... 41
H. Schulzrinne, A. Rao, R. Lanphier Expires August 2, 1998 [Page 3]
INTERNET-DRAFT draft-ietf-mmusic-rtsp-09.ps February 2, 1998
12.25Location............................................. 41
12.26Proxy-Authenticate ....................................... 42
12.27Proxy-Require . . . ....................................... 42
12.28Public .............................................. 42
12.29Range .............................................. 42
12.30Referer ............................................. 42
12.31Retry-After ........................................... 43
12.32Require ............................................. 43
12.33RTP-Info ............................................ 43
12.34Scale............................................... 44
12.35Speed .............................................. 45
12.36Server.............................................. 45
12.37Session ............................................. 45
12.38Timestamp ........................................... 46
12.39Transport ............................................ 46
12.40Unsupported ........................................... 48
12.41User-Agent ........................................... 48
12.42Vary............................................... 49
12.43Via................................................ 49
12.44WWW-Authenticate ...................................... 49
13 Caching 49
14 Examples 49
14.1MediaonDemand(Unicast) .................................. 50
14.2StreamingofaContainerfile.................................. 51
14.3SingleStreamContainerFiles ................................. 54
14.4LiveMediaPresentationUsingMulticast ........................... 55
14.5Playingmediaintoanexistingsession ............................. 56
14.6Recording............................................ 57
15 Syntax 59
15.1BaseSyntax........................................... 60
16 Security Considerations 61
A RTSP Protocol State Machines 62
A.1 ClientStateMachine ...................................... 63
A.2 ServerStateMachine...................................... 63
B Interaction with RTP 64
C Use of SDP for RTSP Session Descriptions 65
C.1 Definitions............................................ 65
C.1.1 ControlURL ...................................... 65
C.1.2 Mediastreams ..................................... 66
H. Schulzrinne, A. Rao, R. Lanphier Expires August 2, 1998 [Page 4]
INTERNET-DRAFT draft-ietf-mmusic-rtsp-09.ps February 2, 1998
C.1.3 Payloadtype(s)..................................... 66
C.1.4 Format-specificparameters............................... 66
C.1.5 Rangeofpresentation ................................. 66
C.1.6 Time of availability . .................................. 67
C.1.7 ConnectionInformation ................................ 67
C.1.8 Entity Tag . ....................................... 67
C.2 AggregateControlNotAvailable................................ 67
C.3 AggregateControlAvailable .................................. 68
D Minimal RTSP implementation 68
D.1 Client .............................................. 68
D.1.1 BasicPlayback..................................... 69
D.1.2 Authentication-enabled................................. 70
D.2 Server.............................................. 70
D.2.1 BasicPlayback..................................... 70
D.2.2 Authentication-enabled................................. 71
E Author Addresses 71
F Acknowledgements 72
1 Introduction
1.1 Purpose
The Real-Time Streaming Protocol (RTSP)establishes and controls either a single or several time-synchronized
streams of continuous media such as audio and video. It does not typically deliver the continuous streams
itself, although interleaving of the continuous media stream with the control stream is possible (see Section
10.12). In other words, RTSP acts as a “network remote control” for multimedia servers.
The set of streams to be controlled is defined by a presentation description. This memorandum does not
define a format for a presentation description.
There is no notion of an RTSP connection; instead, a server maintains a session labeled by an identifier.
An RTSP session is in no way tied to a transport-level connection such as a TCP connection. During an
RTSP session, an RTSP client may open and close many reliable transport connections to the server to issue
RTSP requests. Alternatively, it may use a connectionless transport protocol such as UDP.
The streams controlled by RTSP may use RTP [1], but the operation of RTSP does not depend on the
transport mechanism used to carry continuous media.
The protocol is intentionally similar in syntax and operation to HTTP/1.1 [2] so that extension mecha-
nisms to HTTP can in most cases also be added to RTSP. However, RTSP differs in a number of important
aspects from HTTP:
RTSP introduces a number of new methods and has a different protocol identifier.
An RTSP server needs to maintain state by default in almost all cases, as opposed to the stateless
nature of HTTP.
Both an RTSP server and client can issue requests.
H. Schulzrinne, A. Rao, R. Lanphier Expires August 2, 1998 [Page 5]
剩余73页未读,继续阅读
shaoyundong
- 粉丝: 0
- 资源: 6
上传资源 快速赚钱
- 我的内容管理 收起
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
会员权益专享
最新资源
- zigbee-cluster-library-specification
- JSBSim Reference Manual
- c++校园超市商品信息管理系统课程设计说明书(含源代码) (2).pdf
- 建筑供配电系统相关课件.pptx
- 企业管理规章制度及管理模式.doc
- vb打开摄像头.doc
- 云计算-可信计算中认证协议改进方案.pdf
- [详细完整版]单片机编程4.ppt
- c语言常用算法.pdf
- c++经典程序代码大全.pdf
- 单片机数字时钟资料.doc
- 11项目管理前沿1.0.pptx
- 基于ssm的“魅力”繁峙宣传网站的设计与实现论文.doc
- 智慧交通综合解决方案.pptx
- 建筑防潮设计-PowerPointPresentati.pptx
- SPC统计过程控制程序.pptx
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功