H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments 2326, Internet Engineering Task Force, Apr. 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....is a timing relationship that must be observed during the rendering of the media in order to reproduce it correctly. This timing relationship must be followed otherwise the integrity of the media is destroyed, i.e. the information that was intended to be presented can be lost or misunderstood [132]. In the particular case where media is transmitted over the network and reproduced at a different location, this implies that the destination must reproduce the timing relationship that existed at the source. This contrasts with the usual approach adopted for data transmission in which ....

....and QoS monitoring. An application protocol developed by Netscape Corporation and Real Networks was accepted by IETF as a draft standard. The Real Time Streaming Protocol (RTSP) offers a WWW based and HTTP friendly interface to allow on demand delivery of real time media over the Internet [132]. RTSP is built on top of the currently available transport protocols (RTP, TCP and UDP) The protocol provides mechanisms to request delivery of real time data, specify the transport layer to be used and the destination for the delivery, request information about the encoding format, control the ....

H. Schulzrinne, A. Rao and R. Lamphier "Real-Time Streaming Protocol (RTSP)", Internet Enginnering Task Force, Internet Draft, November 1996.

....a particular protocol by filtering based on the appropriate TCP UDP port number. Use of tcpdump for multimedia traffic is complicated because the majority of multimedia applications use dynamically assigned UDP port numbers. For example, protocols such as the Real Time Streaming Protocol (RTSP) [1], the Session Initiation Protocol (SIP) 2] and H.323 [3] use a well known TCP port number for control traffic but typically use dynamically negotiated port numbers for the actual media traffic. To address this problem we have created a new utility we call mmdump that is based on tcpdump but ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)." RFC 2336, April 1998.

....stored. This allows the local portal to provide VCR like controls to the client even when the content being viewed is coming from a remote portal. It also allows the local portal to cache the recently viewed content in case users wish to review it later. The Real Time Streaming Protocol (RTSP) [1] is used between clients and portals, and portals and live sources to control delivery of streaming content. As shown in Figure 1, the three types of elements are connected together by the following components to form the PRISM architecture: Content distribution network (CDN) transfers content ....

....what cable head end the content was sent over in order to allow for local content insertion modification. The syntax of our naming scheme is shown in Figure 3. The channel name (described in detail below) identifies a unique stream of content. The start and stop times are expressed as UTC times [1] (e.g. utc:20000215T2200 ) The program name is a text string identifying content within a particular channel, and the time offset is an offset relative to the start of a program in seconds (e.g. pro distributor ; location : stv: channel name stv: channel name spec : ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)." RFC 2326, April 1998.

....data redundancy. The Video Audio Archive object models a component which physically owns the video audio documents. Upon request, it starts the streaming activity, i.e. the transmission of multimedia data from a server to a client without downloading of the entire document to the client host [6]. The object provides functions to start stop the streaming of an audio video document, and send receive an audio video packet or a synchronization message. The Video Audio Player object can issue requests to an archive for the delivering of documents, and has features to model the streaming ....

....[1 h] h] 0.01 100] 0.1 Fault rate for the Network Links Fault duration for the Network Links l S S s S [1 h] h] h] 0.05 50] 0.00025 0.25] 0.0000025 0. 0025] Fault rate for the Film Servers (FSs) Fault mean duration for the FSs Standard deviation for the FSs l ds [1 h] [10 9 10 6 ] Fault rate for the Video Server (for a single memory location) Table 1 Fault injection parameters The following fault models have been assumed: Corruption of data and control packets Packets are sent over the network. If the Network is hit by a fault while a packet is traversing it, ....

H. Schulzrinne, A. Rao, and R. Lanphier. "Real Time Streaming Protocol (RTSP)", Internet Engineering Task Force RFC 2326, April 1998.

....transmissions are simply initiated on the Web. Then, the client s player contacts the multimedia server using a different set of protocols that are better suited to streaming applications. For example, the RealNetworks client and server communicate using the Real Time Streaming Protocol (RTSP) [1], an IETF draft standard that derives from HTTP. RTSP is used in a number of commercial streaming media applications, including the RealNetworks client and server. Despite the advent of new multimedia protocols, today s audio and video applications typically experience high start up delay, due to ....

....stream s SSRC, the sequence number of the last RTP packet sent, the wallclock time of the last transmission, and the number of RTP packets and bytes sent. The client can use the RTP timestamp and wallclock time information for media synchronization. 2. 3 Real Time Streaming Protocol (RTSP) RTSP [1] coordinates the delivery of multimedia files, acting as a VCR remote control. RTSP typically runs over TCP, though UDP can also be used. Though conceptually similar to HTTP 1.1 [15] RTSP is stateful and has several different methods. The OPTIONS method inquires about server capabilities (e.g. ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments 2326, April 1998.

....or workahead transmission, without introducing client delay. While transmitting the prefix to the client, the proxy can simultaneously request the remainder of the stream from the server using existing protocol mechanisms, such as the range requests available in HTTP 1. 1 [2] and RTSP [3] . Multimedia proxy services, such as prefix caching, can play an important role in improving user performance and network efficiency for streaming audio and video in the Internet. For ease of deployment, these services should not require changes to existing client server software or network ....

....the last transmission, and the number of RTP packets and bytes sent. The client can use the RTP timestamp and wallclock time information for media synchronization. Design Considerations for an RTSP Based Prefix Caching Proxy for Multimedia Streams 4 2. 3 Real Time Streaming Protocol (RTSP) RTSP [3] coordinates the delivery of multimedia files, acting as a VCR remote control. RTSP typically runs over TCP, though UDP can also be used. Though conceptually similar to HTTP 1.1 [2] RTSP is stateful and has a number of different methods. The OPTIONS method inquires about server capabilities ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments 2326, April 1998.

....are possible. The Video Archive (VA) and Audio Archive (AA) objects own the physical video and audio documents, respectively. Upon request of an authorized Player, they start the streaming activity, i.e. the transmission of multimedia documents from a server to a client without downloading [5]. The main functions of the VA and AA are: Add delete document The Archive adds removes an Audio Video document to from the local list of available documents. Open Close Stream The Archive starts stops the streaming of an Audio Video document towards an authorized Player. Send packet ....

H. Schulzrinne, A. Rao, and R. Lanphier. "Real Time Streaming Protocol (RTSP)", Internet Engineering Task Force RFC 2326, April 1998.

....and deleting users, and for modifying a user s rights. The Archive Server (AS) object models a component which physically owns the video audio documents. Upon request, it starts the streaming activity, i.e. the transmission of multimedia documents from a server to a client without downloading [6]. The AS object provides functions to start stop streaming of an audio video document, and send receive an audio video packet or a synchronization message. The Multimedia Client (MC) object can issue requests to the archives for the delivering of documents, and has functions to model the ....

SCHULZRINNE H., RAO A., LANPHIER R., "Real Time Streaming Protocol (RTSP)". In: Internet Engineering Task Force RFC 2326, April 1998.

....network using xDSL or HFC technologies. In the following we briefly outline the delivery procedure for continuous media objects. The client directs its request for a particular continuous media object to its assigned proxy server (for instance by using the Real Time Streaming Protocol (RTSP) [16]) If the continuous media object is not cached in the proxy, that is, in the case of a cache miss, the proxy forwards the request to the appropriate origin server. The origin server streams the continuous media object to the proxy server. The proxy relays the stream to the requesting client and ....

....model the random start times of the video streams and the client interactions by assigning to video object i the random phase i . These client interactions such as pause resume and forward backward temporal jumps can be communicated to the proxy using the Real Time Streaming Protocol (RTSP) [16]; we assume in our model that the temporal jumps have the granularity of blocks, i.e. K frames. It is natural to assume that the random phases i ; i = 1; I , are in 5 dependent and uniformly distributed over [0; N Gamma 1] In our model the amount of data retrieved from disk for ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) 2326, Internet Engineering Task Force,, Apr. 1998.

....network using xDSL or HFC technologies. In the following we briefly outline the delivery procedure for continuous media objects. The client directs its request for a particular continuous media object to its assigned proxy server (for instance by using the Real Time Streaming Protocol (RTSP) [15]) If the continuous media object is not cached in the proxy, that is, in the case of a cache miss, the proxy forwards the request to the appropriate origin server. The origin server streams the continuous media object to the proxy server. The proxy relays the stream to the requesting client and ....

....model the random start times of the video streams and the client interactions by assigning to video object i the random phase i . These client interactions such as pause resume and forward backward temporal jumps can be communicated to the proxy using the Real Time Streaming Protocol (RTSP) [15]; we assume in our model that the temporal jumps have the granularity of blocks, i.e. K frames. It is natural to assume that the random phases i ; i = 1; I , are independent and uniformly distributed over [0; N=K Gamma 1] In our model the amount of data retrieved from disk for video ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) 2326, Internet Engineering Task Force,, Apr. 1998.

....by filtering based on the appropriate TCP UDP port number. Use of tcpdump for multimedia traffic is complicated, since the majority of multimedia applications use dynamically assigned UDP port numbers for media transfer. For example, protocols such as the Real Time Streaming Protocol (RTSP) [1], the Session Initiation Protocol (SIP) 2] and ITU H.323 [3] allow use of dynamically assigned UDP ports, in each case relying on a well known TCP port to allow sender and receiver to agree on the port values to use. To address this problem we have designed a new utility called mmdump which is ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)." RFC 2336, April 1998.

.... data and control architecture currently incorporating protocols such as RSVP (RFC 2205 [2] for reserving network resources, the real time transport protocol (RTP) RFC 1889 [3] for transporting real time data and providing QOS feedback, the real time streaming protocol (RTSP) RFC 2326 [4]) for controlling delivery of streaming media, the session announcement protocol (SAP) 5] for advertising multimedia sessions via multicast and the session description protocol (SDP) RFC 2327 [6] for describing multimedia sessions. However, the functionality and operation of SIP does not depend ....

....for example (in order of preference) an RFC, a published paper, a patent filing, a technical report, documented source code or a computer manual; # Contact information (postal and email address) Registrations should be sent to iana iana.org. This procedure has been borrowed from RTSP [4] and the RTP AVP [30] 5 Response After receiving and interpreting a request message, the recipient responds with a SIP response message. The response message format is shown below: Response = Status Line ; Section 5.1 ( general header # response header # entity header ) CRLF [ ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments 2326, Internet Engineering Task Force, Apr. 1998.

....between RTP payload type values and the payload formats they represent for formats that do not have a predefined payload type value. Examples of such protocols include the Session Initiation Protocol (SIP) RFC 2543 [6] H. 323 [7] and applications using SDP (RFC 2327 [8] such as RTSP (RFC 2326 [9]) For simple applications, electronic mail or a conference database may also be used. The specification of such protocols and mechanisms is outside the scope of this document. 4 Byte Order, Alignment, and Time Format All integer fields are carried in network byte order, that is, most ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) 2326, Internet Engineering Task Force, Apr. 1998.

....Berlin, April 2000. 1 In particular, H.323 call signaling is inspired by H.320 [6] for ISDN, and call control by H.324 [7] for GSTN terminals. SIP [1] developed in the IETF, builds on a simple text based request response architecture similar to other Internet protocols such as HTTP [8] and RTSP [9]. With the exception of conference control, SIP provides a similar set of basic services as H.323 [10, 11] Interworking between the protocols is made simpler since both operate over IP (Internet Protocol) and use RTP (Real time Transport Protocol [12] for transferring realtime audio video data, ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) 2326, Internet Engineering Task Force, Apr. 1998.

....kinds of signaling capability, such as voice mail control. In analog systems, only DTMF can be used, while even in ISDN, all such signaling would have to carried in user to user elements within existing signaling messages. In an Internet context, adding another control protocol, for example, RTSP [5] for voice mail or a presence protocol, can be done independently of the telephony signaling protocol. Internet telephony enables the creation of new services that integrate telephone services with existing Internet protocols and services. Since Internet telephony addresses are URLs, the Internet ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) 2326, Internet Engineering Task Force, Apr. 1998.

....(For senders, the expected RTCP 2 Figure 2: Global Program Manager Prototype interval is roughly five seconds, so there are ample opportunities for redundancy. On receiving the signal for a commercial or local conent break, the management server at the local station requests the local RTSP [17] server to start playing the local content. During this time, the local station ceases forwarding RTP packets. While RTP timestamps can be aligned with the primary station, the local station has to generate its own sequence numbers. 3 Related Work Jonas et al. 19] have introduced the concepts ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) 2326, Internet Engineering Task Force, Apr. 1998.

.... 14, 2000 field field name bits field field name bits 1 LARc[0] 6 39 xmc[22] 3 2 LARc[1] 6 40 xmc[23] 3 3 LARc[2] 5 41 xmc[24] 3 4 LARc[3] 5 42 xmc[25] 3 5 LARc[4] 4 43 Nc[2] 7 6 LARc[5] 4 44 bc[2] 2 7 LARc[6] 3 45 Mc[2] 2 8 LARc[7] 3 46 xmaxc[2] 6 9 Nc[0] 7 47 xmc[26] 3 10 bc[0] 2 48 xmc[27] 3 11 Mc[0] 2 49 xmc[28] 3 12 xmaxc[0] 6 50 xmc[29] 3 13 xmc[0] 3 51 xmc[30] 3 14 xmc[1] 3 52 xmc[31] 3 15 xmc[2] 3 53 xmc[32] 3 16 xmc[3] 3 54 xmc[33] 3 17 xmc[4] 3 55 xmc[34] 3 18 xmc[5] 3 56 xmc[35] 3 19 xmc[6] 3 57 xmc[36] 3 20 xmc[7] 3 58 xmc[37] 3 21 xmc[8] 3 59 xmc[38] 3 22 ....

....offering a byte stream abstraction, such as TCP, possibly multiplexed with other data. If the application does not define its own method of delineating RTP and RTCP packets, it SHOULD prefix each packet with a two octet length field in network order (most significant octet first) Note: RTSP [27] provides its own encapsulation and does not need an extra length indication. Schulzrinne Casner Expires July 14, 2000 [Page 21] INTERNET DRAFT draft ietf avt profile new 08.ps January 14, 2000 PT encoding media type clock rate name (Hz) 24 unassigned V 25 CelB V 90000 26 JPEG V 90000 27 ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) RFC 2326, Internet Engineering Task Force, Apr. 1998.

.... 21, 1999 field field name bits field field name bits 1 LARc[0] 6 39 xmc[22] 3 2 LARc[1] 6 40 xmc[23] 3 3 LARc[2] 5 41 xmc[24] 3 4 LARc[3] 5 42 xmc[25] 3 5 LARc[4] 4 43 Nc[2] 7 6 LARc[5] 4 44 bc[2] 2 7 LARc[6] 3 45 Mc[2] 2 8 LARc[7] 3 46 xmaxc[2] 6 9 Nc[0] 7 47 xmc[26] 3 10 bc[0] 2 48 xmc[27] 3 11 Mc[0] 2 49 xmc[28] 3 12 xmaxc[0] 6 50 xmc[29] 3 13 xmc[0] 3 51 xmc[30] 3 14 xmc[1] 3 52 xmc[31] 3 15 xmc[2] 3 53 xmc[32] 3 16 xmc[3] 3 54 xmc[33] 3 17 xmc[4] 3 55 xmc[34] 3 18 xmc[5] 3 56 xmc[35] 3 19 xmc[6] 3 57 xmc[36] 3 20 xmc[7] 3 58 xmc[37] 3 21 xmc[8] 3 59 xmc[38] 3 22 ....

....V 90000 Table 5: Payload types (PT) for video and combined encodings Schulzrinne Casner Expires April 21, 2000 [Page 23] INTERNET DRAFT draft ietf avt profile new 07.ps October 21, 1999 delineating RTP and RTCP packets, it SHOULD prefix each packet with a two octet length field. Note: RTSP [27] provides its own encapsulation and does not need an extra length indication. 8 Port Assignment As specified in the RTP protocol definition, RTP data SHOULD be carried on an even UDP or TCP port number and the corresponding RTCP packets SHOULD be carried on the next higher (odd) port number. ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) RFC 2326, Internet Engineering Task Force, Apr. 1998.

....two man months. H.323 uses a binary representation for its messages, based on ASN.1 and the packed encoding rules (PER) ASN.1 generally requires special code generators to parse. SIP, on the other hand, encodes its messages as text, similar to HTTP [2] and the Real Time Streaming Protocol (RTSP) [3]. This leads to simple parsing and generation, particularly when done with powerful text processing languages such as Perl. The textual encoding also simplifies debugging, allowing manual entry and perusing of messages. Its similarity to HTTP also allows for code reuse; existing HTTP parsers can ....

H. Schulzrinne, R. Lanphier, and A. Rao, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) 2326, Internet Engineering Task Force, Apr. 1998.

.... June 25, 1999 field field name bits field field name bits 1 LARc[0] 6 39 xmc[22] 3 2 LARc[1] 6 40 xmc[23] 3 3 LARc[2] 5 41 xmc[24] 3 4 LARc[3] 5 42 xmc[25] 3 5 LARc[4] 4 43 Nc[2] 7 6 LARc[5] 4 44 bc[2] 2 7 LARc[6] 3 45 Mc[2] 2 8 LARc[7] 3 46 xmaxc[2] 6 9 Nc[0] 7 47 xmc[26] 3 10 bc[0] 2 48 xmc[27] 3 11 Mc[0] 2 49 xmc[28] 3 12 xmaxc[0] 6 50 xmc[29] 3 13 xmc[0] 3 51 xmc[30] 3 14 xmc[1] 3 52 xmc[31] 3 15 xmc[2] 3 53 xmc[32] 3 16 xmc[3] 3 54 xmc[33] 3 17 xmc[4] 3 55 xmc[34] 3 18 xmc[5] 3 56 xmc[35] 3 19 xmc[6] 3 57 xmc[36] 3 20 xmc[7] 3 58 xmc[37] 3 21 xmc[8] 3 59 xmc[38] 3 22 xmc[9] 3 60 ....

....V 90000 Table 5: Payload types (PT) for video and combined encodings Schulzrinne Casner Expires December 25, 1999 [Page 23] INTERNET DRAFT draft ietf avt profile new 06.ps June 25, 1999 delineating RTP and RTCP packets, it SHOULD prefix each packet with a two octet length field. Note: RTSP [27] provides its own encapsulation and does not need an extra length indication. 8 Port Assignment As specified in the RTP protocol definition, RTP data SHOULD be carried on an even UDP or TCP port number and the corresponding RTCP packets SHOULD be carried on the next higher (odd) port number. ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) RFC 2326, Internet Engineering Task Force, Apr. 1998.

....for MPEG 4 March 09, 1998 Herpel et al. Page 5] means. The required descriptors will be defined by DMIF and may either be encapsulated in a DMIF defined protocol or may be part of an SDP [7] session description. They might be conveyed through native signaling, using e.g. SIP [8] INVITE or RTSP [9] DESCRIBE methods. b) Once an object bundle is defined, it is considered to be a single payload type MPEG 4 FlexMux Stream for RTP purposes and thus identified as a single RTP session. Given that there are also applications with fewer objects and, hence, Elementary Streams, a second RTP payload ....

H. Schulzrinne, A. Rao, R. Lamphier `Real Time Streaming Protocol (RTSP)', Internet Engineering Task Force, Nov.

.... xmaxc[3] 6 26 Nc[1] 7 64 xmc[39] 3 27 bc[1] 2 65 xmc[40] 3 28 Mc[1] 2 66 xmc[41] 3 29 xmaxc[1] 6 67 xmc[42] 3 30 xmc[13] 3 68 xmc[43] 3 31 xmc[14] 3 69 xmc[44] 3 32 xmc[15] 3 70 xmc[45] 3 33 xmc[16] 3 71 xmc[46] 3 34 xmc[17] 3 72 xmc[47] 3 35 xmc[18] 3 73 xmc[48] 3 36 xmc[19] 3 74 xmc[49] 3 37 xmc[20] 3 75 xmc[50] 3 38 xmc[21] 3 76 xmc[51] 3 Table 2: Ordering of GSM variables Schulzrinne Expires May 18, 1999 [Page 15] INTERNET DRAFT draft ietf avt profile new 04.ps November 18, 1998 Octet Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 0 1 1 0 1 LARc0.0 LARc0.1 LARc0.2 LARc0.3 1 LARc0.4 ....

....it may be necessary to carry RTP in protocols offering a byte stream abstraction, such as TCP, possibly multiplexed with other data. If the application does not define its own method of delineating RTP and RTCP packets, it SHOULD prefix each packet with a two octet length field. Note: RTSP [20] provides its own encapsulation and does not need an extra length indication. 8 Port Assignment As specified in the RTP protocol definition, RTP data is to be carried on an even UDP or TCP port number and the corresponding RTCP packets are to be carried on the next higher (odd) port number. ....

H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) RFC 2326, Internet Engineering Task Force, Apr. 1998.

No context found.

H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," Tech. Rep., April 1998, RFC 2326.

No context found.

SCHULZRINNE H., RAO A., LANPHIER R., "Real Time Streaming Protocol (RTSP)". In: Internet Engineering Task Force RFC 2326, April 1998.

No context found.

H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," Tech. Rep., April 1998, RFC 2326.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC