Re: [rtcweb] Proposal for dealing with CNAMEs and MSIDs for synchronization

Harald Alvestrand <harald@alvestrand.no> Sat, 09 February 2013 14:40 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B0BB21F882A for <rtcweb@ietfa.amsl.com>; Sat, 9 Feb 2013 06:40:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qQr35AMAcTni for <rtcweb@ietfa.amsl.com>; Sat, 9 Feb 2013 06:40:37 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 64AA921F87FA for <rtcweb@ietf.org>; Sat, 9 Feb 2013 06:40:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 525A639E194 for <rtcweb@ietf.org>; Sat, 9 Feb 2013 15:40:34 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCw5l-2AwWbx for <rtcweb@ietf.org>; Sat, 9 Feb 2013 15:40:33 +0100 (CET)
Received: from [192.168.1.84] (70-91-193-41-BusName-NewEngland.hfc.comcastbusiness.net [70.91.193.41]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id E292139E151 for <rtcweb@ietf.org>; Sat, 9 Feb 2013 15:40:30 +0100 (CET)
Message-ID: <51165FCA.2040707@alvestrand.no>
Date: Sat, 09 Feb 2013 15:40:10 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CABcZeBO105HXWoRAbaAR0fGTCLtDmAyjt-DOM=aKy80sg2SG_Q@mail.gmail.com> <51140038.3040001@ericsson.com> <CABcZeBP_-ce-JT-oDkpkDoRKjrZo+m7NLTcifCOsRBM_qKPTmg@mail.gmail.com> <511407AA.1040501@ericsson.com> <CABcZeBO0oSYw-M-1wVujftiYdBtJ67SBfMp4k5gSm45HFhZ+=A@mail.gmail.com> <92B7E61ADAC1BB4F941F943788C0882804788D71@xmb-aln-x08.cisco.com> <51157034.3020800@alvestrand.no> <51164AFC.80700@ericsson.com>
In-Reply-To: <51164AFC.80700@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] Proposal for dealing with CNAMEs and MSIDs for synchronization
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 14:40:38 -0000

On 02/09/2013 02:11 PM, Stefan Håkansson LK wrote:
> On 2013-02-08 22:37, Harald Alvestrand wrote:
>> On 02/07/2013 09:08 PM, Charles Eckel (eckelcu) wrote:
>>>> -----Original Message-----
>>>> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
>>>> Behalf Of Eric Rescorla
>>>> Sent: Thursday, February 07, 2013 3:03 PM
>>>> To: Stefan Hakansson LK
>>>> Cc: rtcweb@ietf.org
>>>> Subject: Re: [rtcweb] Proposal for dealing with CNAMEs and MSIDs for
>>>> synchronization
>>>>
>>>>
>>>>
>>>> On Thu, Feb 7, 2013 at 11:59 AM, Stefan Hakansson LK
>>>> <stefan.lk.hakansson@ericsson.com> wrote:
>>>>
>>>>
>>>>     On 02/07/2013 08:43 PM, Eric Rescorla wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>             My question is basically: what if the sender creates two
>>>>             MediaStreams for which all tracks have local sources
>>>> (cam's,
>>>>             mike's), sends them to a peer, will the RTP streams for
>>>> both
>>>>             MediaStreams have the same or different CNAME?
>>>>
>>>>             I argued for that they should have the same.
>>>>
>>>>
>>>>         Yes, I think this is a separate (and fraught) question. :)
>>>>
>>>>
>>>>
>>>>     Separate question, but I think the answer should be documented
>>>> (regardless on if it is "same", "different" or "implementers choice").
>>>>
>>>>
>>>>
>>>> Agreed.
>>> I think SHOULD is the correct thing to document. I can imagine there
>>> will be cases in which the sender will be a somewhat distributed app
>>> that does not really know that the media source should be
>>> synchronized, so it will assign a different CNAME.
>>> The rest of the proposal sounded good as well.
>>>
>>>
>> SHOULD often makes me unhappy, because it can lead easily to something
>> being true so much of the time, people forget to check for whether it is
>> true or not.
>>
>> I think "all the streams have local sources" is a property that we
>> shouldn't require that one end of a PeerConnection reveals to the other
>> end.
>
> When you say "streams" above I guess you mean RTP streams (or 
> MediaStreamTracks) as it would not make sense to make this a secret 
> when they are transported in different MediaStreams but expose it if 
> they are in the same.
When they are in the same MediaStream, they are required to have the 
same CNAME (unless I lost track of the conversation), so it's only when 
they're in different MediaStreams that it matters whether the CNAME is 
the same or not.

>
> What info would reveal this ("have local sources")? Is it them having 
> the same CNAME?

Yes.