\section{Open Issues}

\begin{enumerate}
\item Define text/rtsp-parameter MIME type.

\item PLAY response should return starting sequence number to allow
client to flush old packets after PAUSE.

% ADDED by hgs
%\item Allow hh:mm:ss.ff fraction for NPT type.

\item Allow byte offsets for Range (Prasoon Tiwari).

\item Reverse: Scale: -1, with reversed start times, or both?

\item HS believes that RTSP should only control individual media objects
rather than aggregates.  This avoids disconnects between presentation
descriptions and streams and avoids having to deal separately with
single-host and multi-host case.  Cost:  several PLAY/PAUSE/RECORD in
one packet, one for each stream.

\item Allow changing of transport for a stream that's playing? May not
be a great idea since the same can be accomplished by tear down and
re-setup. Exception: near-video-on-demand, where the server changes the
address in a PLAY response. Servers may not be able to reliably send
TEARDOWN to clients and the client wouldn't know why this happened in
any event.

\item How does the server get back to the client unless a persistent
connection is used? Probably cannot, in general.

\item Server issues TEARDOWN and other 'event' notifications to client? 
This raises the problem discussed in the previous open issue, but is
useful for the client if the data stream contains no end indication.


\end{enumerate}
