Re: [MMUSIC] Request URI with query and control URI

["HAAS Christian" <Christian.Haas at frequentis.com>]

Hello again;

From: Magnus Westerlund [mailto:magnus.westerlund at ericsson.com] 
> [...]
> So in fact maintaining the URI query component requires one to copy it
> into the relative reference, i.e.
> 
> rtsp://server:554/greetings/?person=Bob
> Controls (in SDP) for audio and video streams:
> a=control:voice_audio?person=Bob
> a=control:front_image?person=Bob
> 
> Which when processed would result in:
> 
> rtsp://server:554/greetings/voice_audio?person=Bob

I don't know how complex the virtual paths for resources can become on a
server, but with this method I believe it is going to be difficult to find
out what is what (base URI together with the query and the control name) -
although I could think of servers first working with the session id, which
then already has associated what the original parameters were. Stripping them
away should leave the control name.


> > Proposal:
> > rtsp://server:554/greetings/?person=Bob#voice_audio
> > 
> > Fragments are currently not defined (allowed) for messaging
> > between client and server and one stream of several within
> > a presentation could be seen as 'fragment' of the presentation.
>
> Yes, because they are client local instructions. [...]

Which is why I proposed to use them - since they were handled (and thus
filtered) by the client, they would have been available for the signalization
between client and server; But I just got remembered about a case where a
RTSP URI (with query) links to a specific section only of the audio stream
for example (which would look like this:
rtsp://server:554/meetings/audio_track?id=1234#introduction).

In sum, the 'best' solution would be to have the query put into the control
URI as well, as you described. Although, since these relative strings are
only appended to the original URI by some clients (as seen with Real Player
and Quicktime), the server might end up receiving something like
rtsp://server:554/greetings/?person=Bob/voice_audio?person=Bob
To cover all bases, I guess the best a server could do with queried URIs is
to put the absolute string for the control property.

>From my point of view, the tracker item can be closed.


Regarding the fragments (derailing the original topic a little): How are
these fragments defined/interpreted for and by the client anyway? In my
example above, how would the client know fragment 'introduction' refers to
npt=10.0-120.0 ?
The spec only states
> The user agent also needs to interpret the value of the fragment
> based on the media type the request relates to; i.e., the media
> type indicated in Content-Type header in the response to DESCRIBE
This might be a dedicated topic (for SDP?)...

Regards,
ch
____________________________________________________
Christian Haas
Team DIVOS, Software Engineer
FREQUENTIS AG

Innovationsstraße 1, 1100 Vienna, Austria
Phone   +43-1-811 50 - 8353
Mobile   +43-664-60 850 - 8353
Fax       +43-1-811 50 - 77 8353
Web      www.frequentis.com
E-Mail    christian.haas at frequentis.com
 
Handelsgericht Wien (Vienna Commercial Court): FN 72115 b
DVR 0364797, ATU 14715600
____________________________________________________
Diese E-Mail könnte vertrauliche und/oder rechtlich geschützte Informationen
enthalten. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser E-Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorised
copying, disclosure or distribution of the material in this e-mail is
strictly forbidden. 



_______________________________________________
mmusic mailing list
mmusic at ietf.org
https://www.ietf.org/mailman/listinfo/mmusic