Re: [TLS] Fwd: TLS Paris Interim Minutes

Bodo Moeller <bmoeller@acm.org> Wed, 05 November 2014 14:56 UTC

Return-Path: <bmoeller@acm.org>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C23941A1F70 for <tls@ietfa.amsl.com>; Wed, 5 Nov 2014 06:56:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.262
X-Spam-Level:
X-Spam-Status: No, score=-0.262 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
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 BKH-c4FNKJ0S for <tls@ietfa.amsl.com>; Wed, 5 Nov 2014 06:56:05 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.13]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CA4D1ACCF2 for <tls@ietf.org>; Wed, 5 Nov 2014 06:56:05 -0800 (PST)
Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com [209.85.218.44]) by mrelayeu.kundenserver.de (node=mreue103) with ESMTP (Nemesis) id 0M8opw-1Xtgz833kK-00C9PK; Wed, 05 Nov 2014 15:56:03 +0100
Received: by mail-oi0-f44.google.com with SMTP id h136so12189193oig.31 for <tls@ietf.org>; Wed, 05 Nov 2014 06:56:00 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.202.212.207 with SMTP id l198mr30114215oig.12.1415199360429; Wed, 05 Nov 2014 06:56:00 -0800 (PST)
Received: by 10.60.32.42 with HTTP; Wed, 5 Nov 2014 06:56:00 -0800 (PST)
In-Reply-To: <CAL9PXLyDTodniZ4n6Uy8mtpNRMY02LeKwKtt9CwhjEbDZDrtBA@mail.gmail.com>
References: <54A8F330-D25A-40FF-81BF-7CA35C69343C@ieca.com> <CADMpkcKrTFGOyCwMEcRK3Sftqy5QTsYtb93LYn_FBpG35J6bmg@mail.gmail.com> <CADMpkcL6=+qMVWwsd8xC0kmnDEPfA0Q2fXLx-p3znNDvuW=zpw@mail.gmail.com> <CAL9PXLyDTodniZ4n6Uy8mtpNRMY02LeKwKtt9CwhjEbDZDrtBA@mail.gmail.com>
Date: Wed, 05 Nov 2014 15:56:00 +0100
Message-ID: <CADMpkc+zstQiRpfqJ+ofHyih4TpMiztOwKzR-HbZnYvtag3vDw@mail.gmail.com>
From: Bodo Moeller <bmoeller@acm.org>
To: Adam Langley <agl@google.com>
Content-Type: multipart/alternative; boundary="001a113d24222a3d6e05071dc7de"
X-Provags-ID: V02:K0:dYOtwi+fyoCDi0uV+C2ir1s8vp9tqdwe7rSH4HSHN4i 3Kj3v/3uBvQBYLV1CUq+bwKvvkdceZGo9YlT7CiDXW2uZ2jftD 8ritqijAFtwxLwbtjcDuK5rNRAbHaQtnOFBwn/0y7dFQ/pbOty yIerqmvaW77N1oWg5249GSt+WBGwXhKmJ/H9LEK7+uVDSZVref DOZwbYlLx17rpJhnrr6OxcBzXxyEDo9h8aO0rd7D/QSwsELE/h aEF1jLTiHArussAJhayHC6+tFw5GgwwRf7ArWoM82pUR8Zdexy TLfBa46dD5CBzUkM76VJe1ycuth/+I9n5Aay/gLZrV3ck8vcbp ixADNwtR2V2jUHqOhjA2h5Co+zjH5YJhkH2s/CrgEZskC4rHMG lf3snOuAvAfoU7UlkMRE6n9+6+u0tGPl1OAk0gC4YPQq62RHKy 6OqcW
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/e0aHGSWpt-62hiIUnXhbnE2wcMs
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Fwd: TLS Paris Interim Minutes
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 14:56:11 -0000

Adam Langley <agl@google.com>:

> On Wed, Nov 5, 2014 at 4:49 AM, Bodo Moeller <bmoeller@acm.org> wrote:
>


> > This isn't correct, and isn't what was said at the meeting. As discussed
> at
> > the meeting, YouTube currently allows two cipher suites for video
> streams,
> > TLS_RSA_WITH_AES_128_GCM_SHA256 and TLS_RSA_WITH_RC4_128_SHA, but Firefox
> > doesn't support the former without ECDHE
> > (https://bugzilla.mozilla.org/show_bug.cgi?id=1029179).
>


> Some locations additionally support ECDHE_RSA_AES_128_GCM_SHA256,
> which we are testing now.
>

Yes, but the above is about correcting the 2014-10-21 minutes, not updating
them to reflect the current status.

Bodo