IETF Logo Mail Archive

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

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Wed, 05 March 2014 16:41 UTC

Return-Path: <sergio.garcia.murillo@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 104B81A012A for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 08:41:06 -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 obAUz6Bt8TgI for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 08:41:03 -0800 (PST)
Received: from mail-ee0-x236.google.com (mail-ee0-x236.google.com [IPv6:2a00:1450:4013:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5521A00A3 for <rtcweb@ietf.org>; Wed, 5 Mar 2014 08:41:03 -0800 (PST)
Received: by mail-ee0-f54.google.com with SMTP id d49so579566eek.41 for <rtcweb@ietf.org>; Wed, 05 Mar 2014 08:40:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=lTiSg9RfP1ryrMftW8DxGhzK0Kpg4iKR+5wX1bKAlWk=; b=F8tYaZ/04wDkhuroJN1PqfCqRRZRDaiDrwuVxI9A5tITyQFiPeKgqQaxpCcy3Zz5P/ xsQbJen/i2JBCF9jY471GBLhODO8Fgr+bbgv0xvTofikrU2Crss1QxXy5qQsB8Slb3Xg R+Unb38oiQOPVNdKBslWk0AwG+g2WFvYK8g/TN+/9D9T1Em5QVBznGmpGvZbOzZLO0ih w+smNDxe3r5q4wCBWItODn/lK9zHqwXMiQoVDgt7gwyGFGlwZ/vcsUdZgNSU6xAscyUv 4e5OrvYj/u+gmMjRH9IADbJ6/hsJNRJb5Ajr08TxUMtgud335xM2Ni9/dmtQ8qaj9ri5 +XmQ==
X-Received: by 10.15.21.2 with SMTP id c2mr6828722eeu.77.1394037659449; Wed, 05 Mar 2014 08:40:59 -0800 (PST)
Received: from [192.168.1.35] (105.Red-81-33-134.dynamicIP.rima-tde.net. [81.33.134.105]) by mx.google.com with ESMTPSA id m9sm10939262eeh.3.2014.03.05.08.40.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Mar 2014 08:40:58 -0800 (PST)
Message-ID: <5317539C.7020305@gmail.com>
Date: Wed, 05 Mar 2014 17:41:00 +0100
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@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>
In-Reply-To: <212442C8-F66F-4D7A-B64D-C37629B1F710@skype.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/VxvbK-QCvXgbl5AjOmQ1i2uqtHs
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:41:06 -0000

In that case, we could link the usage of EKT to unencripted rtp header 
extensions (and not only audio-to-mixer level), moreover as you suggest 
that it would not be enabled in P2P communications and only when a mixer 
is involved.

Best regards
Sergio
El 05/03/2014 17:34, Matthew Kaufman (SKYPE) escribió:
> EKT is one possible answer to this concern.
>
> 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)
>
> Matthew Kaufman
>
> Sent from my iPad
>
>> On Mar 5, 2014, at 8:23 AM, "Sergio Garcia Murillo" <sergio.garcia.murillo@gmail.com> wrote:
>>
>> El 05/03/2014 16:45, Jonathan Lennox escribió:
>>> That said, I’m not sure I believe in Cullen’s use case — there’s too much other information that this unauthorized conference mixer wouldn’t be able to do.  (e.g., request I-frames, or detect them, for switching; or generate proper RTCP reports for sometimes-on streams).
>> I have deeper doubts, I don't really know how a RTP router/mixer would be able to work without acting as DTLS endpoint and decripting/encripting the RTP data.  Or is there a way to setup/share a DTLS session between more than two peers so the same DTLS/SRTP packet is decriptable by more than one receiver?
>>
>> Best regards
>> Sergio
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email