Subject: [MMUSIC] Rtspspec-bugs digest, Vol 1 #90 - 1 msg

From: [email-masked]
Date: Fri, 12 Sep 2003 20:25:37 -0700

This is an automatic digest of bugs submitted and changed on the RTSP bug tracker.  To see a list of bugs, visit:

http://sf.net/projects/rtspspec

When replying, please make your Subject line more specific than "Re: Rtspspec-bugs digest"

Today's Topics:

   1. [ rtspspec-Bugs-804219 ] How to handle sync in re-SETUP (SourceForge.net)

--__--__--

Message: 1
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Thu, 11 Sep 2003 00:20:31 -0700
Subject: [rtspspec-bugs] [ rtspspec-Bugs-804219 ] How to handle sync in re-SETUP

Bugs item #804219, was opened at 2003-09-11 09:20
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=804219&group_id=23194

Category: None
Group: Fix for DS - Need WG Input
Status: Open
Resolution: None
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Nobody/Anonymous (nobody)
Summary: How to handle sync in re-SETUP

Initial Comment:
When using SETUP to change transport parameters, there

seem to be two ways of handling media sync after

parameter change.

A. Put a requirement on the servers to maintain the

timestamp <-> play time from before the change. 

B. Put in a Range and RTP-Info headers to carry sync

information in the SETUP response. 

B. will require the client to here implement the same

mechanism as for PLAY when maintaining buffer

information from before a pause. 

Are there any need for B, like use cases etc?

Comments on the two approach are desired. 

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=804219&group_id=23194

End of Rtspspec-bugs Digest

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