Subject: [MMUSIC] Rtspspec-bugs digest, Vol 1 #62 - 3 msgs

From: [email-masked]
Date: Tue, 19 Nov 2002 12:14:05 -0800

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-640272 ] Default way of deriving aggregate URL ([email-masked])
   2. [ rtspspec-Bugs-640298 ] Use cases for RTSP ([email-masked])
   3. [ rtspspec-Bugs-640848 ] umbiguity in aggregate/non-aggregate pla ([email-masked])

--__--__--

Message: 1
To: [email-masked]
From: [email-masked]
Date: Mon, 18 Nov 2002 12:19:13 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-640272 ] Default way of deriving aggregate URL

Bugs item #640272, was opened at 2002-11-18 21:19
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=640272&group_id=23194

Category: General
Group: Fix for DS - Need WG Input
Status: Open
Resolution: None
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Rob Lanphier (robla)
Summary: Default way of deriving aggregate URL

Initial Comment:
Currently there is very little said on which aggregated
control URL to use. The only given case is the
a=control attribute in SDP at session level. In cases
when one aggregates media stream that have no common
SDP declaration or dependencies in other ways the URL
can't be derived. Examples of such cases is when you
would like to aggregate a session multiplexed
retransmission stream with the original data stream,
without requiring aggregatation between all media types
part of a stream. Another example is aggregation of
streams that are lacking a common SDP description but
still can be intressting to aggregate. 

To fix this a way to derive what a valid aggregate URL
is needs to be specified. 

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

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

--__--__--

Message: 2
To: [email-masked]
From: [email-masked]
Date: Mon, 18 Nov 2002 12:55:01 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-640298 ] Use cases for RTSP

Bugs item #640298, was opened at 2002-11-18 21:55
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=640298&group_id=23194

Category: General
Group: Fix for DS - Need WG Input
Status: Open
Resolution: None
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Rob Lanphier (robla)
Summary: Use cases for RTSP

Initial Comment:
Today very little is defined regarding the different
use cases that RTSP can be deployed in. This should be
specified at least so that we can know what to think
of. It is properly not possible to ensure and implement
all of the use cases that are interesting, however we
should ensure that the base spec allows for extensions
to support them. 

Use case:
1. On-demand streaming with single receiver in a
session. A single client creates a session with unicast
media transport to itself from the server. 

2. Live streaming to single user. A single user creates
a session with unicast delviery from a live source. The
control logic for this sessin is differnet compared to 1. 

3. On-deman streaming with multicast delivery: Controll
is an issue. Different models exist:
- Externally controlled
- By session leader only
- Common control for all receivers.

4. Live streaming with multicast delivery. Who is
controlling the media delivery in the session can be
different:
- Externally controlled 
- By session leader
- Common control for all receivers.
5. Common session with media deliver by unicast to each
of the participants. The control can be any of the
above from 3 and 4.  

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

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

--__--__--

Message: 3
To: [email-masked]
From: [email-masked]
Date: Tue, 19 Nov 2002 10:24:21 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-640848 ] umbiguity in aggregate/non-aggregate pla

Bugs item #640848, was opened at 2002-11-19 18:24
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=640848&group_id=23194

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Go Hori (ghori)
Assigned to: Nobody/Anonymous (nobody)
Summary: umbiguity in aggregate/non-aggregate pla

Initial Comment:
It is not clear to me who's choice it is to pick
aggregate play vs. non-aggregate play.  

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

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

End of Rtspspec-bugs Digest

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