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

From: [email-masked]
Date: Tue, 26 Nov 2002 12:16:28 -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-644040 ] RTP-Info base-URL ([email-masked])

--__--__--

Message: 1
To: [email-masked]
From: [email-masked]
Date: Tue, 26 Nov 2002 03:35:39 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-644040 ] RTP-Info base-URL

Bugs item #644040, was opened at 2002-11-26 12:35
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=644040&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: RTP-Info base-URL

Initial Comment:
The RTP-Info header uses a media URL to reference the
media which the information applies to. However there
is nothing specified regarding use of relative URL. The
BNF in RFC 2326 does only reference url which is
undefined. Draft 02 has instead clarified this and does
allow relative URL. 

The use of relative URL however is present in some
commerical products out there. So should this behavior
be specifed or specified as illegal and the BNF updated. 

If allowed, what should the Base-URL be? The use of
Content-Base does seem to be a bad choice. Should one
use the request URL as base?

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

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

End of Rtspspec-bugs Digest

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