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

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Wed, 05 March 2014 14:41 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 7ABBD1A0691 for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 06:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.048
X-Spam-Level:
X-Spam-Status: No, score=-110.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 BPTMSpRedRcQ for <rtcweb@ietfa.amsl.com>; Wed, 5 Mar 2014 06:41:58 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 2733F1A068A for <rtcweb@ietf.org>; Wed, 5 Mar 2014 06:41:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=962; q=dns/txt; s=iport; t=1394030514; x=1395240114; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=3XwglVs3VZy7lsV9Q8YEuUJj+KeFBb/YxFmQ3FmOhNY=; b=RHNNUQUiVGVuwRaY7rp/4CglZte1eAgIK2ux0lPbaJm6nOZHTPJ8BSyY LJr+Akyj1XfTfML3oqdas9TP9OqYATHSzZtdrzHQFaGv8tCOUmFNIDxic dqY/yvdjXrRAWwHLP2QBFjKm8HDuf83eoC/Q9hWi/hcTt2VIKLKLbNWnF o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAMA2F1OtJXG//2dsb2JhbABagwaBEsELgRcWdIIlAQEBAwF5BQsCAQgOODIlAgQOBYdxCM4XF44eMweDJIEUAQOYPZIrgy2CKg
X-IronPort-AV: E=Sophos;i="4.97,593,1389744000"; d="scan'208";a="25105304"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by alln-iport-4.cisco.com with ESMTP; 05 Mar 2014 14:41:54 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s25EfsCQ027517 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Mar 2014 14:41:54 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.113]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0123.003; Wed, 5 Mar 2014 08:41:54 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Justin Uberti <juberti@google.com>
Thread-Topic: [rtcweb] draft-ietf-rtcweb-rtp-usage-12 Client-to-Mixer Audio Level
Thread-Index: AQHPOG7/fizbxTQF/UyT77go6S8SfprS6duAgAACN4CAAAU4AIAABNeA
Date: Wed, 5 Mar 2014 14:41:53 +0000
Message-ID: <F99B5539-EEB7-4A3C-B8E4-4B6B607D8B2F@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>
In-Reply-To: <CAOJ7v-3JAKZDHtrx9J2v=hqksQ9xdz7XW_1HbqioEzWMqUrn7A@mail.gmail.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: <FB2572E375FF644595A0B5CBF3FD93A3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/5YYftHTxIXf4DQTauaDrHDj1Zxk
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:41:59 -0000

On Mar 5, 2014, at 2:25 PM, 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)
I’m fine with yes

> 2) MUST the implementation use encrypted header extensions? (i.e. mandatory-to-use)
I think this needs to be No. Never mind my current use case - if the far end does not negotiate RFC 6094 with the browser, the media and headers should not fail. 

> 3) MUST the implementation expose an API to control this? (i.e. no SDP munging needed)
I prefer control surfaces to SDP munging but as you say, I could live with SDP munging in 1.0 

> 
> 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.
> 


seems workable