Standards Track A. Rao Netscap - RFC Editor

More documents

Recommendations

Info

RFC 2326 Real Time Streaming Protocol April 1998request has been acknowledged.Re-using HTTP functionality has advantages in at least two areas,namely security and proxies. The requirements are very similar, sohaving the ability to adopt HTTP work on caches, proxies andauthentication is valuable.While most real-time media will use RTP as a transport protocol, RTSPis not tied to RTP.RTSP assumes the existence of a presentation description format thatcan express both static and temporal properties of a presentationcontaining several media streams.2 Notational ConventionsSince many of the definitions and syntax are identical to HTTP/1.1,this specification only points to the section where they are definedrather than copying it. For brevity, [HX.Y] is to be taken to referto Section X.Y of the current HTTP/1.1 specification (RFC 2068 [2]).All the mechanisms specified in this document are described in bothprose and an augmented Backus-Naur form (BNF) similar to that used in[H2.1]. It is described in detail in RFC 2234 [17], with thedifference that this RTSP specification maintains the "1#" notationfor comma-separated lists.In this memo, we use indented and smaller-type paragraphs to providebackground and motivation. This is intended to give readers who werenot involved with the formulation of the specification anunderstanding of why things are the way that they are in RTSP.3 Protocol Parameters3.1 RTSP Version[H3.1] applies, with HTTP replaced by RTSP.3.2 RTSP URLThe "rtsp" and "rtspu" schemes are used to refer to network resourcesvia the RTSP protocol. This section defines the scheme-specificsyntax and semantics for RTSP URLs.rtsp_URL = ( "rtsp:" | "rtspu:" )"//" host [ ":" port ] [ abs_path ]host =
RFC 2326 Real Time Streaming Protocol April 1998of RFC 1123 \cite{rfc1123}>port = *DIGITabs_path is defined in [H3.2.1].Note that fragment and query identifiers do not have a well-definedmeaning at this time, with the interpretation left to the RTSPserver.The scheme rtsp requires that commands are issued via a reliableprotocol (within the Internet, TCP), while the scheme rtspu identifiesan unreliable protocol (within the Internet, UDP).If the port is empty or not given, port 554 is assumed. The semanticsare that the identified resource can be controlled by RTSP at theserver listening for TCP (scheme "rtsp") connections or UDP (scheme"rtspu") packets on that port of host, and the Request-URI for theresource is rtsp_URL.The use of IP addresses in URLs SHOULD be avoided whenever possible(see RFC 1924 [19]).A presentation or a stream is identified by a textual mediaidentifier, using the character set and escape conventions [H3.2] ofURLs (RFC 1738 [20]). URLs may refer to a stream or an aggregate ofstreams, i.e., a presentation. Accordingly, requests described inSection 10 can apply to either the whole presentation or an individualstream within the presentation. Note that some request methods canonly be applied to streams, not presentations and vice versa.For example, the RTSP URL:rtsp://media.example.com:554/twister/audiotrackidentifies the audio stream within the presentation "twister", whichcan be controlled via RTSP requests issued over a TCP connection toport 554 of host media.example.com.Also, the RTSP URL:rtsp://media.example.com:554/twisteridentifies the presentation "twister", which may be composed ofaudio and video streams.This does not imply a standard way to reference streams in URLs.The presentation description defines the hierarchical relationshipsin the presentation and the URLs for the individual streams. Apresentation description may name a stream "a.mov" and the wholepresentation "b.mov".Schulzrinne, et. al. Standards Track [Page 15]
Page 2 and 3: RFC 2326 Real Time Streaming Protoc
Page 7: RFC 2326 Real Time Streaming Protoc
Page 64 and 65:
RFC 2326 Real Time Streaming Protoc
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92:
show all

Standards Track A. Rao Netscap - RFC Editor

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?