Subject: [MMUSIC] Agenda for Thursday RTSP meeting (more detail)

From: Rob Lanphier <[email-masked]>
Date: Wed, 20 Mar 2002 19:57:53 -0800 (Pacific Standard Time)

Hi all,

There's a few minor tweaks to this agenda, mainly fleshing out the detail
in numbered points on state machine and queued play.

I'm not changing the times on the meeting, but I would like to move more
quickly than the scheduled 60 minutes for the first part if possible.

*  Agenda bashing (10 minutes)
*  Define roadmap for RTSP (60 minutes)
   *  Getting core specification to Draft Standard
      *  Interop logistics
   *  Specifications/groups which may extend RTSP
      *  JPEG 2000
      *  CATS
      *  MUTE/UNMUTE
      *  RADPLAY
   *  General concept for RTSP extensions
   *  Scope for RTSP with respect to extensions (in vs. out)
   *  Come up with procedure for post DS work on RTSP
   *  Registration of feature tags for optional features (need to audit
      spec)
*  Close on other decisions in Wednesday RTSP discussion (15 minutes)
   *  Clarify aggregate/non-aggregate control
      *  Reworked state machine
         1. In the both playing states, is SETUP and TEARDOWN allowed?
         2. When a media reaches the end of a media should the resume
            point be set to begining of clip, although it will remain in
            playing state?
         3. When a media reaches the end of the specified range(s) should
            the resume point be set to 0.0 or the end of the range?
         4. Should we have the READY-nm state that this version shows?
         5. When doing setup for recording is there a requirement to have
            done announce before?
         6. Should REDIRECT without range or reaching the readirect point
            result in imediatly closeing of the session? This is
            suggested by the old client state machine that send the client
            to Init on redirect. The text in chapter 10.10 says that the
            client should issue a teardown of previous session.
   *  Should we eliminate queued play? (yes)
      1.  How do you queue timed PLAY requests
      2.  Implementation of accurate RTP-Info for queued play
      3.  Very complex interaction with MUTE
      4.  Lack of implementer interest
          -   Not sure what practical use cases are
   *  RECORD....needs specification work from implementer (may need to
      drop)
   *  Transport model requirements
      *  Is persistent TCP mode required?  (yes)
      *  Is non-persistent TCP mode required? (no, will define feature
         tag and "Supported" header from SIP)
*  Wrapup (5 minutes)

We're on a pretty tight agenda, so please endeavor to be on time, and
please don't save agenda bashing for the meeting.

Look forward to seeing you there.

Rob

_______________________________________________
mmusic mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mmusic