Re: CNAME use

Here is what the RTP usage draft says:


   Taking the discussion in Section 11<http://tools.ietf.org/html/draft-ietf-rtcweb-rtp-usage-14#section-11> into account, a WebRTC end-point
   MUST NOT use more than one RTCP CNAME in the RTP sessions belonging
   to single RTCPeerConnection (that is, an RTCPeerConnection forms a
   synchronisation context).  RTP middleboxes MAY generate RTP packet
   streams associated with more than one RTCP CNAME, to allow them to
   avoid having to resynchronize media from multiple different end-
   points part of a multi-party RTP session.


[BA] Currently ORTC API doesn't provide a way to indicate that multiple tracks should share a synchronization context.

On May 31, 2014, at 1:26 AM, "Emil Ivov" <emcho@jitsi.org<mailto:emcho@jitsi.org>> wrote:

We have been looking at recording WebRTC conferences lately and have noticed how Chrome sends different CNAMEs for every media source.

CNAMEs have traditionally been used to determine whether two streams are synchronise-able so having unique CNAMEs for an audio and a video flow originating at the same host is kind of awkward.

Do we have a position on this for ORTC implementations? Should they be encouraged to share CNAMEs within the same session (page). If not, then should we provide a way for the page to control that?

Emil



--
https://jitsi.org