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 15:00 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 AB4F21A0039 for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 07:00:37 -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 6Q4BjJH5vqUd for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 07:00:36 -0800 (PST)
Received: from mail-bk0-x231.google.com (mail-bk0-x231.google.com [IPv6:2a00:1450:4008:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1981A0171 for <rtcweb@ietf.org>; Wed, 5 Mar 2014 07:00:35 -0800 (PST)
Received: by mail-bk0-f49.google.com with SMTP id my13so471179bkb.36 for <rtcweb@ietf.org>; Wed, 05 Mar 2014 07:00:32 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bNFjy7yoatSZUuwwHSVTi/DxqDYE3xxE3MeBz10Zu3I=; b=BGx14Cuod5UFWjowAZvgOiD8wr0vfs0Lc6Msf0M9LOmnp63uTWohMcJZvb25VciGLX oGAIrERjZEtOwqFPedjyyiqB/U5rFdHLOYSwJKRSvHSbtx4eGw1riJnc3Lxbeu4u60Bk xYJvqFKGpYXhO4ojm7fzky8Hq4cGMOrr55gD8RjalJ5WtEDSmNboss08cZOKat2BDgCq wQf6QvhF6tL43wuF3IK8uTU4Vd2d1BKIErs+alpnUsesSh94EFrmOoRPiR1czPaUOV9V WExLIofzrCER36HtbakEla27o/YA58EKaGPGeunrb+RP6w8lEG3af1Yv/ASwzQ+qxx/N 7usA==
X-Received: by 10.204.76.7 with SMTP id a7mr2117008bkk.17.1394031632098; Wed, 05 Mar 2014 07:00:32 -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 dj6sm5245054bkc.5.2014.03.05.07.00.30 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Mar 2014 07:00:30 -0800 (PST)
Message-ID: <53173C11.8060504@gmail.com>
Date: Wed, 05 Mar 2014 16:00:33 +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: rtcweb@ietf.org
References: <1BC59A5D-D1C9-4E3F-ABFB-C1D664CD7ACF@cisco.com>
In-Reply-To: <1BC59A5D-D1C9-4E3F-ABFB-C1D664CD7ACF@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/Zr_2C24HgMt7blHVIi9xbDB9MVk
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 15:00:37 -0000

El 05/03/2014 13:32, Cullen Jennings (fluffy) escribió:
> I am opposed to mandating that Client-to-Mixer Audio Level RTP header is REQUIRED to be encrypted. It means that we can not really build conferencing system where the mixers do not have access to decrypt the media.
>
>
Hi Cullen,

I am not sure I am following you. AFAIK DTLS is only possible to be 
setup between two peers, so in a multiconference solution the mixer will 
anyway have to establish a DTLS/SRTP session which each peer and 
decrypt/encrypt before sending to any of participants in the conference. 
In case of a full meshed conference, there is no need of a mixer at all, 
and the logic could be directly implemented on each of the endpoints.

Am I missing something? Please correct me if I am wrong.

Best regards
Sergio

v2.14.0 | Report a Bug | By Email