Subject: [MMUSIC] Rtspspec-bugs digest, Vol 1 #102 - 5 msgs

From: [email-masked]
Date: Wed, 22 Oct 2003 20:28:29 -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-795295 ] TEARDOWN using * and the Ready-nm state (SourceForge.net)
   2. [ rtspspec-Bugs-810666 ] Removal of SETUP in play state (SourceForge.net)
   3. [ rtspspec-Bugs-810666 ] Removal of SETUP in play state (SourceForge.net)
   4. [ rtspspec-Bugs-585865 ] Use of Date, and Host in RTSP (SourceForge.net)
   5. [ rtspspec-Bugs-795295 ] TEARDOWN using * and the Ready-nm state (SourceForge.net)

--__--__--

Message: 1
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Wed, 22 Oct 2003 09:04:36 -0700
Subject: [rtspspec-bugs] [ rtspspec-Bugs-795295 ] TEARDOWN using * and the Ready-nm state

Bugs item #795295, was opened at 2003-08-26 14:08
Message generated for change (Comment added) made by magwes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=795295&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: Magnus Westerlund (magwes)
Summary: TEARDOWN using * and the Ready-nm state

Initial Comment:
The 20 february 2002 we discussed
http://rtsp.org/bug506412, for conclusion of that
discussion see minutes:
http://rtsp.org/2002/telecon/minutes20Feb.html

However to me it seems that the need for state Ready-nm
is not that great. Also the use of "*" as a URL will
not work when proxies are present, unless requirements
are put on them to maintain certain state in regards to
sessions. The use of the presentation URL also is
problematic as some sessions may not have a defined
session URL, like for example for sessions intended to
be used in non-aggregted mode. 

Therefore my suggestion is that the Ready-nm state is
removed and that teardown using "*" is dissallowed.
Comments please. 

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

>Comment By: Magnus Westerlund (magwes)
Date: 2003-10-22 18:04

Message:
Logged In: YES 
user_id=302620

As no comments has been raised, this will be edited out. 

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

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

--__--__--

Message: 2
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Wed, 22 Oct 2003 09:03:52 -0700
Subject: [rtspspec-bugs] [ rtspspec-Bugs-810666 ] Removal of SETUP in play state

Bugs item #810666, was opened at 2003-09-22 17:30
Message generated for change (Comment added) made by magwes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=810666&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: Magnus Westerlund (magwes)
Summary: Removal of SETUP in play state

Initial Comment:
On MMUSIC there is a proposal to remove the
functionality for setup in play state to add a new
individual media stream. This not about changing
transport parameters!

First the need for this is not clear. The only use
cases seems to be to do switching between different
media streams variants. As this doesn't look as the
best method and secondly that switching at all is an
add on functionality this seem to not belong in core spec.

Secondly removing this will simplify the specification
writing.

Third, if the method is need in the future it will be
possible to write an extension specification. 

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

>Comment By: Magnus Westerlund (magwes)
Date: 2003-10-22 18:03

Message:
Logged In: YES 
user_id=302620

No comment against this removal has been raised. Therefore
this will be editied.

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

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

--__--__--

Message: 3
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Wed, 22 Oct 2003 09:30:01 -0700
Subject: [rtspspec-bugs] [ rtspspec-Bugs-810666 ] Removal of SETUP in play state

Bugs item #810666, was opened at 2003-09-22 17:30
Message generated for change (Comment added) made by magwes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=810666&group_id=23194

Category: None
>Group: Resolved - Added to text
Status: Open
>Resolution: Accepted
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Magnus Westerlund (magwes)
Summary: Removal of SETUP in play state

Initial Comment:
On MMUSIC there is a proposal to remove the
functionality for setup in play state to add a new
individual media stream. This not about changing
transport parameters!

First the need for this is not clear. The only use
cases seems to be to do switching between different
media streams variants. As this doesn't look as the
best method and secondly that switching at all is an
add on functionality this seem to not belong in core spec.

Secondly removing this will simplify the specification
writing.

Third, if the method is need in the future it will be
possible to write an extension specification. 

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

>Comment By: Magnus Westerlund (magwes)
Date: 2003-10-22 18:30

Message:
Logged In: YES 
user_id=302620

The removal has now been performed and checked in in the
following commit:

/cvsroot/rtspspec/changes.tex,v  <--  changes.tex
new revision: 1.18; previous revision: 1.17
/cvsroot/rtspspec/iana.tex,v  <--  iana.tex
new revision: 1.14; previous revision: 1.13
/cvsroot/rtspspec/machine.tex,v  <--  machine.tex
new revision: 1.13; previous revision: 1.12
/cvsroot/rtspspec/methods.tex,v  <--  methods.tex
new revision: 1.33; previous revision: 1.32

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

Comment By: Magnus Westerlund (magwes)
Date: 2003-10-22 18:03

Message:
Logged In: YES 
user_id=302620

No comment against this removal has been raised. Therefore
this will be editied.

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

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

--__--__--

Message: 4
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Wed, 22 Oct 2003 09:43:08 -0700
Subject: [rtspspec-bugs] [ rtspspec-Bugs-585865 ] Use of Date, and Host in RTSP

Bugs item #585865, was opened at 2002-07-24 13:22
Message generated for change (Comment added) made by magwes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=585865&group_id=23194

Category: General
>Group: Resolved - Added to text
Status: Open
Resolution: None
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Magnus Westerlund (magwes)
Summary: Use of Date, and Host in RTSP

Initial Comment:
There exist a number of HTTP headers that are just
referenced into the specification. Several is hard to
interpret on how they relate to RTSP and what
requirement level that is needed. 

Date:
The date header MUST be sent by origin server in
responses. What is an origin server and what exceptions
exist for RTSP? For RTSP does that include requests also?

Host:
The comment is that this should not be used in RTSP.
This should be reflected in the heade table. 

Other headers that are simply referenced needs most
probably some specification on applicability and
exceptions.

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

>Comment By: Magnus Westerlund (magwes)
Date: 2003-10-22 18:43

Message:
Logged In: YES 
user_id=302620

The Host and Date header has both been clarified on there
usage. Edits are checked in for both. The Date has been
there for some versions, while the host text is new. 

If some other headers also needs edit, has not been
evaluated at this time. 

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

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

--__--__--

Message: 5
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Wed, 22 Oct 2003 09:30:27 -0700
Subject: [rtspspec-bugs] [ rtspspec-Bugs-795295 ] TEARDOWN using * and the Ready-nm state

Bugs item #795295, was opened at 2003-08-26 14:08
Message generated for change (Comment added) made by magwes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=795295&group_id=23194

Category: None
>Group: Resolved - Added to text
Status: Open
>Resolution: Accepted
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Magnus Westerlund (magwes)
Summary: TEARDOWN using * and the Ready-nm state

Initial Comment:
The 20 february 2002 we discussed
http://rtsp.org/bug506412, for conclusion of that
discussion see minutes:
http://rtsp.org/2002/telecon/minutes20Feb.html

However to me it seems that the need for state Ready-nm
is not that great. Also the use of "*" as a URL will
not work when proxies are present, unless requirements
are put on them to maintain certain state in regards to
sessions. The use of the presentation URL also is
problematic as some sessions may not have a defined
session URL, like for example for sessions intended to
be used in non-aggregted mode. 

Therefore my suggestion is that the Ready-nm state is
removed and that teardown using "*" is dissallowed.
Comments please. 

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

>Comment By: Magnus Westerlund (magwes)
Date: 2003-10-22 18:30

Message:
Logged In: YES 
user_id=302620

The removal has now been performed and checked in in the
following commit:

/cvsroot/rtspspec/changes.tex,v  <--  changes.tex
new revision: 1.18; previous revision: 1.17
/cvsroot/rtspspec/iana.tex,v  <--  iana.tex
new revision: 1.14; previous revision: 1.13
/cvsroot/rtspspec/machine.tex,v  <--  machine.tex
new revision: 1.13; previous revision: 1.12
/cvsroot/rtspspec/methods.tex,v  <--  methods.tex
new revision: 1.33; previous revision: 1.32

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

Comment By: Magnus Westerlund (magwes)
Date: 2003-10-22 18:04

Message:
Logged In: YES 
user_id=302620

As no comments has been raised, this will be edited out. 

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

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

End of Rtspspec-bugs Digest

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