Ethan Kim o Websites o o Media Players o o Windows Media Player, Real Player Video Conferencing o o Youtube, Hulu, Fox, NBC, etc. Skype, MSN Messenger , Ventrilo Involved Computing Industry Giants o iTunes, iPhone/iPad, Google Wave, Google Voice, Silverlight o Multiparty Multimedia Session Control Work Group (MMUSIC WG) o o o Part of Internet Engineering Task Force (IETF) Published documentation as RFC 2326 (1998) MMUSIC goals and milestones incomplete since August 2009 o o o o Primary usage of Internet required no delay constraints TCP/IP performance satisfactory Multimedia services gain popularity TCP/IP identified with limitations o o o o Unacceptable delay in playback No mechanism to check bandwidth TCP does not provide timing information RTSP developed o o Intentionally similar to HTTP in syntax and operation Differences o o o o o o New methods and protocol identifier RTSP server maintains state by default Both server and client can issue requests Data is transferred by different protocol Use ISO 10646 (UTF-8) Request-URI contains absolute URI o Privacy o o Security o o Does not pertain to protocol HTTP authentication methods, transport and network layer security mechanism apply Pervasiveness o o Almost all media data is controlled by RTSP Protocol is used internationally o Reliability o o o Involves unreliable data, protocol is reliable Allow control by both client and server Robustness o o o No significant bugs or errors have been identified Both playback and recording controls are possible Allow for multi-servers for multicast and unicast network o Interoperability o o o o o o Loose coupling No dependent protocols Transport-independent Requires no specific format Interoperation between clients and servers from different vendors Support of the Community o Maintained by MMUSIC WG of IETF o Maintainability o o o No revision has been made since development in 1998 Revision was planned for December 2009 Ease of Use o o o o o o Requires knowledge of coding, other internet transport protocols RTSP is flexible, easy to implement Easy extendibility Easy to parse Proxy and firewall friendly HTTP friendly o o Implemented in streaming media players “Network remote control” o Designed to control multiple data delivery sessions o o o o Breaks data into packets User is able start listening Simultaneously more packets are downloaded and decopressed Examples o Youtube, Windows Media Player, Skype o o o Necessary and well developed Flexible, robust, interoperable, extendable, secure, pervasive, and reliable Constant evolving Internet o o Flash vs. HTML5 RTSP is highly adaptable o Work Cited o o o Huuhtanen, Juha. "Real-Time Streaming Protocol (RTSP)." Real-Time Streaming Protocol (RTSP). Helsinki University of Technology, 22 Nov. 1998. Web. 19 Apr. 2010. <http://www.tml.tkk.fi/Studies/Tik110.300/1998/Essays/rtsp.htmlming_ Protocol>. "Multiparty Multimedia Session Control (mmusic)." IETF Datatracker. Web. 19 Apr. 2010. <http://datatracker.ietf.org/wg/mmusic/ch arter/>. Schulzrinne, H., A. Rao, and R. Lanphier. "Real Time Streaming Protocol (RTSP)." Internet Engineering Task Force. MMUSIC WG, Apr. 1998. Web. 19 Apr. 2010. <http://www.ietf.org/rfc/rfc2326.txt>.