Standards Track A. Rao Netscap - RFC Editor

More documents

Recommendations

Info

RFC 2326 Real Time Streaming Protocol April 1998D.1.1 Basic PlaybackTo support on-demand playback of media streams, the client MUSTadditionally be able to do the following:* generate the PAUSE request;* implement the REDIRECT method, and the Location header.D.1.2 Authentication-enabledIn order to access media presentations from RTSP servers that requireauthentication, the client MUST additionally be able to do thefollowing:* recognize the 401 status code;* parse and include the WWW-Authenticate header;* implement Basic Authentication and Digest Authentication.D.2 ServerA minimal server implementation MUST be able to do the following:* Implement the following methods: SETUP, TEARDOWN, OPTIONS andeither PLAY (for a minimal playback server) or RECORD (for aminimal recording server). If RECORD is implemented, ANNOUNCEshould be implemented as well.* Include the following headers in responses: Connection,Content-Length, Content-Type, Content-Language, Content-Encoding,Transport, Public. The capability to include the Location headershould be implemented if the RECORD method is. RTP-compliantimplementations should also implement the RTP-Info field.* Parse and respond appropriately to the following headers inrequests: Connection, Session, Transport, Require.Though not required, the following are highly recommended at the timeof publication for practical interoperability with initialimplementations and/or to be a "good citizen".* Implement RTP/AVP/UDP as a valid transport.* Inclusion of the Server header.* Implement the DESCRIBE method.* Generate SDP session descriptions as defined in Appendix CThere may be RTSP applications different from those initiallyenvisioned by the contributors to the RTSP specification for whichthe requirements above do not make sense. Therefore, therecommendations above serve only as guidelines instead of strictrequirements.Schulzrinne, et. al. Standards Track [Page 86]
RFC 2326 Real Time Streaming Protocol April 1998D.2.1 Basic PlaybackTo support on-demand playback of media streams, the server MUSTadditionally be able to do the following:* Recognize the Range header, and return an error if seeking is notsupported.* Implement the PAUSE method.In addition, in order to support commonly-accepted user interfacefeatures, the following are highly recommended for on-demand mediaservers:* Include and parse the Range header, with NPT units.Implementation of SMPTE units is recommended.* Include the length of the media presentation in the mediainitialization information.* Include mappings from data-specific timestamps to NPT. When RTPis used, the rtptime portion of the RTP-Info field may be used tomap RTP timestamps to NPT.Client implementations may use the presence of length informationto determine if the clip is seekable, and visibly disable seekingfeatures for clips for which the length information is unavailable.A common use of the presentation length is to implement a "sliderbar" which serves as both a progress indicator and a timelinepositioning tool.Mappings from RTP timestamps to NPT are necessary to ensure correctpositioning of the slider bar.D.2.2 Authentication-enabledIn order to correctly handle client authentication, the server MUSTadditionally be able to do the following:* Generate the 401 status code when authentication is required forthe resource.* Parse and include the WWW-Authenticate header* Implement Basic Authentication and Digest AuthenticationSchulzrinne, et. al. Standards Track [Page 87]
Page 2 and 3:
RFC 2326 Real Time Streaming Protoc
Page 4 and 5:
Page 7:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37: RFC 2326 Real Time Streaming Protoc
Page 92: RFC 2326 Real Time Streaming Protoc
show all

Standards Track A. Rao Netscap - RFC Editor

Create successful ePaper yourself

Delete template?

Save as template?