Re: [rtcweb] draft-ietf-rtcweb-rtp-usage-12 Client-to-Mixer Audio Level

Martin Thomson <martin.thomson@gmail.com> Wed, 05 March 2014 16:46 UTC

Return-Path: <martin.thomson@gmail.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 DB3661A0140 for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 08:46:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 u96mW-yYh8WI for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 08:46:53 -0800 (PST)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 7D3411A0652 for <rtcweb@ietf.org>; Wed, 5 Mar 2014 08:46:53 -0800 (PST)
Received: by mail-wg0-f41.google.com with SMTP id n12so1577419wgh.12 for <rtcweb@ietf.org>; Wed, 05 Mar 2014 08:46:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=pyvmGb7t9UlGKSy34tw2A/kWyAG1HfllaQQRSJsi3io=; b=l7AoTNvUgv2AHR4z/NCtWOfc9OIEjuekVQvHt7EDx+IqjEp7WKLxayvy3Jka3NDIBe 8ZqR0PpFolqqnN0OMW7JqQlOVcFeeq1PCDU/ooSB+x6LeoCF1/X/tXdGEL38EWBxSYZX /PokZQu6rqp2bHO09N++z4xBaP7nxcOrr/wb5oOsP4pDpe5IPLcYBgAth2KWsEszmDap DV8NS0VeHeiSm83riyQsapgovi72wJ2VOLsdrBFpvHOV9MpATayUJw1NyZK72UD/HF8K Hk7xR1Jpi/Rdk1iYbrl5Z1xRFpnddrTt+FRtBQcaYb4TGMy//Ff/4XDlAIJ/+UWTt2AD gUfA==
MIME-Version: 1.0
X-Received: by 10.194.188.41 with SMTP id fx9mr2602154wjc.56.1394038009512; Wed, 05 Mar 2014 08:46:49 -0800 (PST)
Received: by 10.227.10.196 with HTTP; Wed, 5 Mar 2014 08:46:49 -0800 (PST)
In-Reply-To: <212442C8-F66F-4D7A-B64D-C37629B1F710@skype.net>
References: <1BC59A5D-D1C9-4E3F-ABFB-C1D664CD7ACF@cisco.com> <EEF5B1D0-7782-4EB8-90DF-F1D56B2D2ADC@phonefromhere.com> <0526965B-6AC9-42F4-9E62-CF3BF29872D3@cisco.com> <CAOJ7v-3JAKZDHtrx9J2v=hqksQ9xdz7XW_1HbqioEzWMqUrn7A@mail.gmail.com> <E7C174FB-B137-4E6D-81AC-06C8C2B30FE1@vidyo.com> <53174F6B.2030706@gmail.com> <212442C8-F66F-4D7A-B64D-C37629B1F710@skype.net>
Date: Wed, 5 Mar 2014 16:46:49 +0000
Message-ID: <CABkgnnVKFkuibEkEGAsk7+rt8idtHNgfJnKjL6uKqaKOm8xQ7Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/S1GbIXBFN0qENyqpUFNtnWLUsEk
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] draft-ietf-rtcweb-rtp-usage-12 Client-to-Mixer Audio Level
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 16:46:55 -0000

On 5 March 2014 16:34, Matthew Kaufman (SKYPE)
<matthew.kaufman@skype.net> wrote:
> By the way: If and when we specify EKT for RTCWEB, there is a simple rule we should establish: A "browser" must not initiate the use of EKT. That way, browser to browser sessions would be unable to force a known key... That could only happen when talking to non-browser endpoints (likely mixers)

I've talked to several people about this and we all agree on this
point.  It's important, if browsers ever implement EKT.

We might also require that "private" sessions not accept attempts to
use EKT too.