Re: [rtcweb] CNAMEs and multiple peer connections

Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 05 March 2014 12:44 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A096B1A03A6 for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 04:44:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y5435pLl6btG for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 04:44:23 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 38F691A0400 for <rtcweb@ietf.org>; Wed, 5 Mar 2014 04:44:21 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-fe-53171c21637e
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 0B.D1.04249.12C17135; Wed, 5 Mar 2014 13:44:17 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.41) with Microsoft SMTP Server id 14.2.347.0; Wed, 5 Mar 2014 13:44:16 +0100
Message-ID: <53171C20.3020001@ericsson.com>
Date: Wed, 5 Mar 2014 12:44:16 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <CABkgnnWGQ7GtKd33iF-RNbkeAyqKYshaPDDB=sAh5o-izKichQ@mail.gmail.com>
In-Reply-To: <CABkgnnWGQ7GtKd33iF-RNbkeAyqKYshaPDDB=sAh5o-izKichQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphluLIzCtJLcpLzFFi42KZGfG3RldRRjzY4MItPotrZ/4xWqz9187u wOSxc9Zddo8lS34yBTBFcdmkpOZklqUW6dslcGXsP3eGteCMYMXd99/YGxjb+LoYOTkkBEwk bmxpZ4KwxSQu3FvP1sXIxSEkcIRRYt7UfiYIZxmjxJv5sxlBqngFtCV6W1+yg9gsAioSx89d YAGx2QQsJG7+aGQDsUUFgiV2HvgNVS8ocXLmE7AaEYEQiSNt01lBbGEBK4knhw+AxYUEAiS6 vm8H6uXg4BQIlLh6wAPElBAQl+hpDAKpYBbQk5hytYURwpaXaN46mxmiU1uioamDdQKj4Cwk y2YhaZmFpGUBI/MqRo7i1OKk3HQjg02MwJA8uOW3xQ7Gy39tDjFKc7AoifN+fOscJCSQnliS mp2aWpBaFF9UmpNafIiRiYNTqoFxedjXre/WfpivscH8ROQCWy7lx6m2Bc8LTWebxj+Xk1r4 3ntCjq0f25S7rewP2o8IZM/NCFppUnz7o1zgvPcKWdMKpp30f6ty/yLbMa3O7pKJm6dzVE/u EjBf2ZkyOeRZysnD/Np1KipPK6df+rLEzC6Ya8fmQH6Nhy0PzTIe3FRVlPmt4DlRiaU4I9FQ i7moOBEA3fIVUhcCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/_A5mHp0MWDvjVvd3cmJ28Sv1LXU
Subject: Re: [rtcweb] CNAMEs and multiple peer connections
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 05 Mar 2014 12:44:25 -0000

On 2014-03-05 10:04, Martin Thomson wrote:
> I haven't thought about this in detail yet, but I wanted to ensure
> that this issue is tracked.  I think that our chairs might be able to
> create an issue in some tracker.  Can I request that they do that for
> this issue?
> 

I will currently not stuff anything into our tracker.

However, I will give a bit of context from what the rtp-usage says about
this.

On the receiver side, we have a clear requirement on handling multiple
CNAMEs in Section 11.

   A WebRTC endpoint MUST support receiving multiple MediaStreamTracks,
   where each of different MediaStreamTracks (and their sets of
   associated packet streams) uses different CNAMEs.  However,
   MediaStreamTracks that are received with different CNAMEs have no
   defined synchronisation.

On the sending side the text says the following:

   The same MediaStreamTrack can also be included in multiple
   MediaStreams, thus multiple sets of MediaStreams can implicitly need
   to use the same synchronisation base.  To ensure that this works in
   all cases, and don't forces a endpoint to change synchronisation base
   and CNAME in the middle of a ongoing delivery of any packet streams,
   which would cause media disruption; all MediaStreamTracks and their
   associated SSRCs originating from the same endpoint MUST be sent
   using the same CNAME within one RTCPeerConnection as well as across
   all RTCPeerConnections part of the same communication session
   context, which for a browser are a single origin.


Martin, you talked about linking in this context. I wonder if there
really are an issue with linking as this is all in the same
communication context. Can you please make clear your concerns?

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------