IETF Logo Mail Archive

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

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Wed, 05 March 2014 14:35 UTC

Return-Path: <fluffy@cisco.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 DFE461A0223 for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 06:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.048
X-Spam-Level:
X-Spam-Status: No, score=-115.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 L1RfGHQDPSPC for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 06:35:57 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id CABC21A065A for <rtcweb@ietf.org>; Wed, 5 Mar 2014 06:35:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1218; q=dns/txt; s=iport; t=1394030147; x=1395239747; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=SwUpwBfoNUaD4m/S14Npb/Ax5sLTngwsbwBUvJsZby4=; b=bDsPJUoxw6B19D0SGtnnxPMOvXcysJKCuEUWvUezFMVa6SkOPRtDCR1m tZ6uf1yDMplFmHD8pRl6/Eh4SoO+l+ehBR3Oy8hnbPEmBafLqSMsF/rvU XnJ7oUCoxh8rxjrHOmsZzBZ6QoiChegae/wMSbhIQQN8lCjD+u/LnPhe4 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAFc1F1OtJV2d/2dsb2JhbABagwaBEsELgRcWdIIlAQEBAwF5EAIBCBguMiUCBA4Fh3EIzhQXjh4zB4MkgRQBA5RSg2uSK4Mtgio
X-IronPort-AV: E=Sophos;i="4.97,593,1389744000"; d="scan'208";a="308293694"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 05 Mar 2014 14:35:42 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s25EZg4A008903 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Mar 2014 14:35:42 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.113]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Wed, 5 Mar 2014 08:35:42 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: tim panton <tim@phonefromhere.com>
Thread-Topic: [rtcweb] draft-ietf-rtcweb-rtp-usage-12 Client-to-Mixer Audio Level
Thread-Index: AQHPOG7/fizbxTQF/UyT77go6S8SfprS6duAgAACN4CAAAU4AIAAAicAgAAA8wA=
Date: Wed, 05 Mar 2014 14:35:41 +0000
Message-ID: <FEE68505-90BA-407F-ABEF-CE8819BA3189@cisco.com>
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> <32D95060-6273-4804-A398-712311481E73@phonefromhere.com>
In-Reply-To: <32D95060-6273-4804-A398-712311481E73@phonefromhere.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.104.132]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <EF2431CC8AAB5345B71CF9ACA4555650@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/t9tdbdWP7TAiTsjbyJL-3bVvFwo
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 14:36:00 -0000

On Mar 5, 2014, at 2:33 PM, tim panton <tim@phonefromhere.com> wrote:

> 
> On 5 Mar 2014, at 14:25, Justin Uberti <juberti@google.com> wrote:
> 
>> So there are three things here:
>> 1) MUST the implementation offer encrypted header extensions? (i.e. mandatory-to-implement)
>> 2) MUST the implementation use encrypted header extensions? (i.e. mandatory-to-use)
>> 3) MUST the implementation expose an API to control this? (i.e. no SDP munging needed)
>> 
>> I think we want yes for #1, no for #2, and #3 is potentially interesting but out of scope for 1.0.
>> That gives encrypted headers for audio on by default, but remote parties can negotiate this off using RFC 6904 mechanisms.
>> 
> 
> In order to agree with that I’d need to be persuaded that there isn’t a known-plaintext attack risk there
> (e.g. detecting a muted mic therefore knowing the ulaw content of a packet), since
> any weakening  in DTLS also impacts the data channel and video channels - assuming bundle.
> 
> Like I say, I’m not enough of a cryptographer to know.

No - it does not weaken DTLS to know the plaintext (and if it did, DTLS would have series security problems )

v2.23.0 | Report a Bug | By Email