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