Standards Track A. Rao Netscap - RFC Editor

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]