哥伦比亚大学课件-通俗易懂-RFC 2326(RTSP)，RFC 2327(SDP).ppt

Real Time Streaming Protocol Akshat Sikarwar Columbia University November 12, 2008 Overview Introduction Protocol properties RTSP messages Important messages * From RFC 2326 Introduction RTSP is like a network remote control for multimedia servers RTSP establishes and controls streams of continuous media Streaming data is carried out of band (interleaving is possible) * From RFC 2326 Protocol Properties RTSP is text based and HTTP like Transport independent (can use UDP or TCP) Unlike HTTP commands can be sent in either direction RTSP is a stateful protocol. Server maintains session state. * From RFC 2326 RTSP Connections RTSP messages can be sent over: One persistent transport connection for several request-response transactions One connection per transaction Connectionless mode Transport connection != Session Server can send message to client only in persistent connection * From RFC 2326 RTSP Reliability If using reliable transport message is sent just once. If using unreliable transport, RTSP will retransmit if it does not receive ACK Timeout is initially set to 500 ms Can re-compute timeout based on RTT like TCP For retransmission CSeq is not incremented Timestamp is used to overcome retransmission ambiguity problem * From RFC 2326 RTSP URI rtsp://:554/twister/audio rtsp identifies reliable protocol rtspu identifies unreliable protocol Default port is 554 Presentation: twister Stream: audio * From RFC 2326 RTSP Message Text based messages Messages use Unicode (ISO 10646) character set encoded using UTF-8 Lines are terminated by CRLF Messages can be request or response by either client or server Message structure is HTTP like * From RFC 2326 Request Message Method URI Version CRLF Header1:Value CRLF Header2:Value CRLF CRLF Body First line is Request line URI is always absolute (unlike HTTP) URI can be * Example OPTIONS * RTSP/1.0 * From RFC 2326 Response Message Version Status-Code Reason-Phrase CRLF Status-Codes are HTTP like 1xx: Informational 2xx: Succe