Re: [rtcweb] CNAMEs and multiple peer connections

Justin Uberti <juberti@google.com> Wed, 12 March 2014 04:40 UTC

Return-Path: <juberti@google.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 05CC61A08DB for <rtcweb@ietfa.amsl.com>; Tue, 11 Mar 2014 21:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level:
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, 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 H7nPBSo2bkbQ for <rtcweb@ietfa.amsl.com>; Tue, 11 Mar 2014 21:40:44 -0700 (PDT)
Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3175D1A08D9 for <rtcweb@ietf.org>; Tue, 11 Mar 2014 21:40:44 -0700 (PDT)
Received: by mail-vc0-f180.google.com with SMTP id lf12so3906309vcb.11 for <rtcweb@ietf.org>; Tue, 11 Mar 2014 21:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VGmDqyARrgJo5ytkCuOqbuPekLkNWOSGbxfztmQMBIA=; b=CUutB/fzzvXaSQNKN/JwWjTEPxaSgsDsqFpUa6M7WhT65LCvYUVOnFO9fX5N2pQn/m 5kfDiqszy1ztGCmTdves6PZRvIXAcAE9KNJzIELI2V3sRb4q4tBUsT+BBAVFiMMy0M7k wjdyzAAOIgALykRJyIUz4rIS+1f9mEe46KH92eKEy+tEmFhk9yqBinc5VlU9DRobUy3z cWruLd6PgWLLDM5Pnpnd3ghX4E3QA8UXyn0+QP31F/o9+/erPtEnvezZFA8idVpCgtFr ND0lDVp8E17zOVkZHREwXZWaMJ3CPa9Ky5oLnFIffO9mDItfY2dca/XcQdEJsWo2/yak s36g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=VGmDqyARrgJo5ytkCuOqbuPekLkNWOSGbxfztmQMBIA=; b=kxuRn9JzpdlUtJfcg+cErJ0CFoVtdQlT5LdaKhqrMWmoG26eujwbjXUiVM79Hc9XxW TISCSgQD3oeJ9ialajlntFvkr+s7yvfdriAJQ+zzhwhZ0QVb5c05xIoGZPNwe7NStuSd QWnr35eZt39qwXSmefqCQMMCtUrbIhlI0DD0dY9IE4g/E5uliB7xFMd73A0mICWGGqzM Ay1jCGzD7kvYbJgYWmkf/AEQOjC3qxFAoY6QTCqe7FXbigWkUHpgrxwA6tOhgdUpDvH9 cS+wODCFHjre+VxvLVGDvc6hSM1t3oycWJZjAOco84haf0Ge6IOKYbCVHTU7MtmqtzuU EP8w==
X-Gm-Message-State: ALoCoQn75eXlK9H0VoN3IYp0DLk8tStnrwrHZhFOaC0M+muBSFTn4AvJJYyyKlZ6upfL5MBwjN+xJ/oR5LQ8IAOGrF3xYr+PKR4lh51RguFAr8xgNnFsAmMSOba++Ze30tlmh1Ymn314oiPGn0ZrumcEvzODQS4FONmuTiI8TOInsBEpY/QzXw2EO4bKd8/YsHUmRs0e5jLY
X-Received: by 10.58.100.100 with SMTP id ex4mr30870533veb.2.1394599238144; Tue, 11 Mar 2014 21:40:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Tue, 11 Mar 2014 21:40:17 -0700 (PDT)
In-Reply-To: <CABkgnnVscHB6_weLkxHunQxLue7g-WvBwO-P_CW6eEU_JYqVuw@mail.gmail.com>
References: <CABkgnnWGQ7GtKd33iF-RNbkeAyqKYshaPDDB=sAh5o-izKichQ@mail.gmail.com> <53171C20.3020001@ericsson.com> <CABkgnnWWoCLKga7RDEmS1kDOuBPaiKaJ+_yj6-yPRSV8LVc=2A@mail.gmail.com> <CAOJ7v-1J=F-MNnBS96gt3_BXyoQB6jTCoHp0MTEBC-nWrF-BhA@mail.gmail.com> <CABkgnnWQbtKYTuvUyMiCaEijv3KVydR8sxGXZep08B4EQXArxA@mail.gmail.com> <531DD807.9090602@ericsson.com> <CABkgnnVscHB6_weLkxHunQxLue7g-WvBwO-P_CW6eEU_JYqVuw@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Tue, 11 Mar 2014 21:40:17 -0700
Message-ID: <CAOJ7v-2LxH4ZgEb5dw=ZYA39k9rZg4Bn1hnBeBchZSu60GXAiw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b33c70631aa3a04f461705a
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/sTT8NyiszTL_R6r12kbDojjn0sc
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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, 12 Mar 2014 04:40:46 -0000

Future versions of the API should have the knobs needed to control the
CNAMEs more exactly. For WebRTC 1.0 though, scoping CNAMEs to a
PeerConnection feels like a prudent simplification.


On Mon, Mar 10, 2014 at 8:49 AM, Martin Thomson <martin.thomson@gmail.com>wrote;wrote:

> On 10 March 2014 16:19, Magnus Westerlund
> <magnus.westerlund@ericsson.com> wrote:
> > Can you please think through the linkage issue a bit first before
> > changing this property.
>
> We already came to the conclusion that if media was being forwarded by
> a peer, then that is new media originated by that peer, not the same
> media.  Thus, if looping occurs, it is at the application layer.  We
> definitely already agreed that RTP forwarding is not a function that a
> browser will support.
>
> Obviously, if we add that feature, CNAMEs will be just one of the
> manifold issues that will arise and we will have to reconsider.
> Compromising the privacy of users doesn't seem like a good trade-off
> against some minor advantages in terms of loop detection (unlikely)
> and synchronization (easy to apply manually).
>