[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MMUSIC] RTSP: Clarifying setup in Multicast
On Monday 03 November 2008 19:01:33 ext Magnus Westerlund, you wrote:
> dest_addr using Session Decription Information: The information
> included in the transport header can all be comming from the
> session description, e.g. the SDP c= and m= line. This
> mitigates some of the security issues of the previous methods
> as it is the session provider that picks the multicast group
> and scope. The client SHALL include the information if it is
> available in the session description.
>
> No dest_addr: The lack of an explicit multicast group request the
> server to decide the group address and its scope. For this to
> work the server needs to have a context about what scope that
> works. This method is currently under specified.
I don't really understand the subtlety here. I mean, how would we end up in
the no dest_addr case? Should the server not provide the infos in DESCRIBE in
the first place?
Conversely, if the SDP is not obtained via RTSP (DESCRIBE), and does contain a
multicast transport address, why would the client (need to) talk to the RTSP
server at all? Supposedly this is a permanent multicast stream then
(without "seeking" capabilities).
Perhaps we should remove the "No dest_addr" case.
--
Rémi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
mmusic mailing list
mmusic at ietf.org
https://www.ietf.org/mailman/listinfo/mmusic