e or stored. RTSP is intended to control multiple data delivery sessions, provide a means for choosing delivery channels such as UDP, multicast UDP, or TCP, and provide a means for choosing delivery mechanisms in conjunction with RTP. The RTSP allows interoperability between client/server multimedia products from multiple vendors. It can be implemented across a broad array of client-side operating systems such as Macintosh and various flavors of Windows and Unix. It is supported by an equally large number of server-side platforms including Macintosh, Windows NT, and variations of UNIX. Using RTSP, application developers can create products that will interoperate within the heterogeneous environment of the Internet and corporate intranets. The protocol defines how a server can connect to a client-side receiver (or multiple receivers) to stream multimedia content. Streaming multimedia can be anything that includes time-based information, such as on-demand multimedia playback, live Real-Time feeds, or stored non-Real-Time programming. RTSP is closely associated with the ITU-T H.323 protocol stack, and facilitates merging of the separate spheres of telephony, conferencing, and multimedia broadcasting. RTSP allows non-traditional broadcasters to leverage IP networks to compete with television and radio programmers. The protocol allows data to be displayed as it is received, rather after all packets are stored and processed. This makes RTSP ideal for developing network computer applications in which hard disks are either non- existent or very small, or when rights management does not favor distributing files. Until 1999, vendors developed applications independently or in collaborative, but proprietary efforts. This did not meet the needs of the Internet, which relies upon open protocols. Progressive Networks, Inc. (RealNetworks) and Netscape Communications spearheaded the collaborative efforts of forty companies on the development of RTSP. RTSP allows content providers to create and manage the delivery of programs in a