Subject: [MMUSIC] Rtspspec-bugs digest, Vol 1 #20 - 4 msgs

From: [email-masked]
Date: Thu, 07 Feb 2002 13:41:02 -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-448521 ] URLs in Rtp-Info need to be quoted ([email-masked])
   2. [ rtspspec-Bugs-477404 ] Errors in table in chapter 12 ([email-masked])
   3. [ rtspspec-Bugs-511233 ] Timed PLAY requests has RTP-Info problem ([email-masked])
   4. [ rtspspec-Bugs-511686 ] Timed PLAY requests has RTP-Info problem ([email-masked])

--__--__--

Message: 1
To: [email-masked]
From: [email-masked]
Date: Tue, 29 Jan 2002 17:54:15 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-448521 ] URLs in Rtp-Info need to be quoted

Bugs item #448521, was opened at 2001-08-06 13:01
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=377744&aid=448521&group_id=23194

Category: None
>Group: Fix - Discussed/Resolved
Status: Open
Resolution: None
Priority: 5
Submitted By: Anders Klemets (klemets)
Assigned to: Rob Lanphier (robla)
Summary: URLs in Rtp-Info need to be quoted

Initial Comment:
The Rtp-Info header contains URLs, but those URLs are 
not quoted, causing problems when the URLs contain 
semi-colon, equal signs and comma characters.

The best way to quote URLs are by using double-
quotes.  Using angle-brackets has also been proposed, 
but using double-quotes is more likely to be 
compatbile with existing implementations, because 
other RTSP/HTTP headers use double-quote characters 
in similar situations.

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

Comment By: David W. Walker (davidwwalker)
Date: 2002-01-28 14:20

Message:
Logged In: YES 
user_id=437905

RESOLUTION: (Jan 9, 2002 telecon) 
Proposed solution was accepted.  Alternative use of 
semicolon and comma were considered  by classified 
as "dangerous characters" ans would break existing 
implementations.

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

Comment By: Henning Schulzrinne (hgschulz)
Date: 2002-01-09 09:20

Message:
Logged In: YES 
user_id=115926

URL escaping (%xx) doesn't work since you lose the
distinction between syntactically significant semicolons
(etc.) and just characters that were escaped in the original
URL.

Only comma and semicolon need to be escaped, since equal
signs are not delimiters.

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

Comment By: Rob Lanphier (robla)
Date: 2001-12-13 09:26

Message:
Logged In: YES 
user_id=3796

I should probably clarify the comments made yesterday.  This is a genuine issue, but
it needs to be weighed against backward-compatibility needs.  Would like input from
implementors on what the best solution is.

We would propose the following: 
*  We need to define the problem characters.  ";" and "=" are two, there may be others
*  URLs MUST not be quoted when no problem characters are present in the URL.  This will help maintain 
backwards-compatibilty with current implementations
*  URLs MUST be quoted when problem characters are present

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

Comment By: Rob Lanphier (robla)
Date: 2001-12-12 14:14

Message:
Logged In: YES 
user_id=3796

add quotes only when sending problem characters (";", "=", ",", need to think further)

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

Comment By: Rob Lanphier (robla)
Date: 2001-08-07 07:21

Message:
Logged In: YES 
user_id=3796

This is primarily to test if mail to confctrl is working

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

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

--__--__--

Message: 2
To: [email-masked]
From: [email-masked]
Date: Tue, 29 Jan 2002 18:14:04 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-477404 ] Errors in table in chapter 12

Bugs item #477404, was opened at 2001-11-01 23:22
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=377744&aid=477404&group_id=23194

Category: None
>Group: Fix for DS - Large task
Status: Open
Resolution: None
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Nobody/Anonymous (nobody)
Summary: Errors in table in chapter 12

Initial Comment:
 Table with RTSP headers page 45, contains the following errors?:
  - A session header is not required when using describe.
  - Proxy Authenticate is missing all values on what it is.
  - The transport header is specifed as required in 12.0 table, but
    the text in 12.39 says it MAY be included in requests and responses.

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

Comment By: David W. Walker (davidwwalker)
Date: 2002-01-28 14:41

Message:
Logged In: YES 
user_id=437905

RESOLUTION:  

The latest SIP draft has an equivalent table. It has been  
recommended that we evaluate this SIP table and unless 
someone objects and justifies the need to make a change 
let's adopt the SIP draft specification version. 

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

Comment By: Rob Lanphier (robla)
Date: 2002-01-22 19:47

Message:
Logged In: YES 
user_id=3796

Here's a discrepency between the initial CVS checkin and RFC 2326
  12  Header Field Definitions (Table 3):
   Change from:
   Content-Type         r      req.      entity
   To:
   Content-Type        e    req.   SET_PARAMETER, ANNOUNCE

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

Comment By: Rob Lanphier (robla)
Date: 2001-12-13 09:53

Message:
Logged In: YES 
user_id=3796

These are all good examples of what's wrong with this table.  We need to do an audit of the table, and we 
may restructure this table for clarity.  Suggestions for a new table format would be appreciated.

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

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

--__--__--

Message: 3
To: [email-masked]
From: [email-masked]
Date: Thu, 31 Jan 2002 07:37:54 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-511233 ] Timed PLAY requests has RTP-Info problem

Bugs item #511233, was opened at 2002-01-31 07:37
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=377744&aid=511233&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: Timed PLAY requests has RTP-Info problem

Initial Comment:
In a PLAY with a range header, "time=" can be used to give activation time. This request shall be 
responded immediately to the client. In the response the server should give synchronization data 
like RTP TS which will be used when the PLAY is activated sometime in the future. It is hard to 
impossible for the server to produce such data. If no other PLAY request is done between request 
time and activation it is possible to give an accurate TS and sequnce number. But if another 
request is activated in the time between, the given RTP TS or sequnce number will not be correct. 

This problem is the same that queued plays has, see bugreport #477432, but due to different 
reasons.

One possible solution would be to introduce a SYNC method which a server can send at or slightly 
before activation of a queued or delayed play. This method would carry a RTP-info header and a 
range header, giving the information; what is playing and the synchronization information. 

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

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

--__--__--

Message: 4
To: [email-masked]
From: [email-masked]
Date: Fri, 01 Feb 2002 05:17:27 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-511686 ] Timed PLAY requests has RTP-Info problem

Bugs item #511686, was opened at 2002-02-01 05:17
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=377744&aid=511686&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: Timed PLAY requests has RTP-Info problem

Initial Comment:
In a PLAY with a range header, "time=" can be used to give activation time. This request shall be 
responded immediately to the client. In the response the server should give synchronization data 
like RTP TS which will be used when the PLAY is activated sometime in the future. It is hard to 
impossible for the server to produce such data. If no other PLAY request is done between request 
time and activation it is possible to give an accurate TS and sequnce number. But if another 
request is activated in the time between, the given RTP TS or sequnce number will not be correct. 

This problem is the same that queued plays has, see bugreport #477432, but due to different 
reasons.

One possible solution would be to introduce a SYNC method which a server can send at or slightly 
before activation of a queued or delayed play. This method would carry a RTP-info header and a 
range header, giving the information; what is playing and the synchronization information. 

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

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

End of Rtspspec-bugs Digest

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