Subject: [MMUSIC] RTSP: Minutes, April 3 telecon

From: Rob Lanphier <[email-masked]>
Date: Wed, 10 Apr 2002 17:57:09 -0700 (Pacific Daylight Time)

Below are the minutes from the RTSP telecon on April 3.  Also available
online:

http://rtsp.org/2002/telecon/minutes03Apr.html

Rob

  RtspTcMinutes03Apr2002

------------------------------------------------------------------------

   1. Agenda
   2. Attendees
   3. Discussion
         1. Issue: SETUP and TEARDOWN in "play" state
         2. ISSUE: End of media state
         3. Issue: Resume point at end of range

  1 Agenda

    * Agenda: http://rtsp.org/2002/telecon/agenda03Apr.html

  2 Attendees

Attendees (phone):

    * Magnus Westerlund (MW)
    * Anders Klemets (AK)
    * Anne Jones (AJ)
    * Milko Boic (MB)
    * David Walker (DW)
    * Rob Lanphier (RL)
    * Jonathan Sergent (JS)
    * Sean Sheedy (SS)
    * Aravind Narasimhan (AN)
    * Tom Marshall (TM)
    * Thomas Zeng (TZ)

Attendees (IRC):

    * Virago (?)

  3 Discussion

    3.1 Issue: SETUP and TEARDOWN in "play" state

Issue: Should SETUP and TEARDOWN be allowed in "play" state in the RTSP
state machine?

    * JS: Our decision with PLAY and PAUSE would point to an answer of "no"
    * MW: this would be new functionality
    * RL: uses lots of ports
    * JS: doesn't increase the maximum number of ports
    * MB: what about MPEG-4
    * JS: my understanding with BIFS is that it arrives in a single stream
    * JS: bad to have two mechanisms for same thing
    * MB: slightly different features
    * JS: lots of extra func in 2326, need to trim
    * RL: interest in mute/unmute functionality
    * JS: yes
    * AN: qustion of client functionality
    * TM: original spec includes functionality
    * MW: mute method should be optional
    * MW: regardless of which way we go
    * AK: I always thought that setup and teardown were always allowed
    * MW: old spec was unclear. should be marked as new feature with
      feature tag
    * MW: we should still allow chaging of transport parameters using
      SETUP during PLAY
    * AK: we implement setup and teardown during PLAY
    * JS: interop is tough if we have lots of different options
    * MB: this also allows people to implement just the core functionality
    * JS: spec doesn't really define this new functionality
    * AN: it does specify TEARDOWN
    * JS: should stay as extension
    * RESOLUTION: no resolution. Take to list. Should specification
      allow SETUP on existing stream? Should specification allow SETUP
      of a new stream?
    * ACTION ITEM: AN to drive discussion

    3.2 ISSUE: End of media state

ISSUE: 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?

    * RL: I think that it should stay at the end. Other opinions?
    * SS: doesn't the current spec imply that the media is reset?
    * JS: unclear in current RFC....most do the same thing
    * AN: not necessarily...if a range is sent, everything is reset
    * JS: we may break if we change things
    * SS: we go back to the beginning
    * AN: our server stops at the end
    * JS: are there clients that take advantage of either?
    * MW: auto rewind will fail anyway
    * MW: ..because of new PAUSE req.
    * JS: not necessarily
    * MW: we need to have no automatic state transition
    * JS: Are there clients that break?
    * AN: Apple client normally sends PAUSE at the end
    * TZ: when we reach the end of the clip, we send notification to the
      player
    * TZ: "END_OF_CLIP" method sent to client
    * AK: we also send end of clip in SET_PARAMETER
    * SS: we send notification as well
    * JS: should be draft
    * RL: not sure....the state should be client driven
    * MW: would like to force client to send PAUSE at end...that's the
      notification
    * JS: need to not break current client
    * RL: resolution? When end of media is reached, server stays in
      "play" state.
    * JS: should be "invalid range" if PAUSE/PLAY (no range) issued
    * RL: resolution? server stays in play state at "error" time at end
      of clip. subsequent PLAY request needs to follow pause, and must
      have new range
    * /resolution was made, but subsequently reversed. See next resolution/

    3.3 Issue: Resume point at end of range

ISSUE: 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?

    * ??: revise previous resolution
    * RESOLUTION (for this and last): server issues Range: in PAUSE
      request which is at the end of the clip. A subsequent PLAY with no
      range will be identical to PLAY request with the Range returned in
      the in PAUSE

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