IETF Logo Mail Archive

Re: [TLS] Minutes from Tuesday

Bodo Moeller <bmoeller@acm.org> Tue, 11 November 2014 11: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 6D0FA1A8704 for <tls@ietfa.amsl.com>; Tue, 11 Nov 2014 03:56:48 -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 4TcEB_C6AFGE for <tls@ietfa.amsl.com>; Tue, 11 Nov 2014 03:56:47 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (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 D00821A1A88 for <tls@ietf.org>; Tue, 11 Nov 2014 03:56:46 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by mrelayeu.kundenserver.de (node=mreue002) with ESMTP (Nemesis) id 0MAYXK-1Xi4Ri0zPe-00Bcve; Tue, 11 Nov 2014 12:56:44 +0100
Received: by mail-ob0-f172.google.com with SMTP id wp4so7296926obc.17 for <tls@ietf.org>; Tue, 11 Nov 2014 03:56:41 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.60.160.206 with SMTP id xm14mr7359360oeb.7.1415707001944; Tue, 11 Nov 2014 03:56:41 -0800 (PST)
Received: by 10.60.32.42 with HTTP; Tue, 11 Nov 2014 03:56:41 -0800 (PST)
In-Reply-To: <CAL9PXLzVHfQocskS0nx=_sGm8wkwu=37omgadLUs7k2n5jg70w@mail.gmail.com>
References: <2A0EFB9C05D0164E98F19BB0AF3708C71D3A8C4AA6@USMBX1.msg.corp.akamai.com> <CADMpkcKM222eU+49U=aNBvq0QRF+C9wAunOW1rBcsJdnC2gxKw@mail.gmail.com> <CAL9PXLzVHfQocskS0nx=_sGm8wkwu=37omgadLUs7k2n5jg70w@mail.gmail.com>
Date: Tue, 11 Nov 2014 12:56:41 +0100
Message-ID: <CADMpkc+FQaANdCSeWfLXbOm-=8_bw=qUgcxH9jz7BaJ2bXuQmw@mail.gmail.com>
From: Bodo Moeller <bmoeller@acm.org>
To: "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="089e0115f6baf5064f050793f8e2"
X-Provags-ID: V02:K0:LTn51kp0F5wHvk8p/Gy734JqWW+btdpgmxPrKjmKI2m X0Q85Jgg3FtOLqvVaGjXKwTe0Cut6TmLLm34kPOsIpTeZAZ93c xOJnH5baFq5PxE61j68jdm2BCO+l9AfiAd/gbdk5eGOhvXN+X0 r+L0KV+AvRWxEnd85J/itiakity3hQWxTbHTyzmfX4yYl+59mp 6UgOkKie+3SBKzRRF0eWI4rk6r2anGZKNI8/F4T9NZyJwOsSab g/UO9HBCU+wMalah0x2gLtBFIdIi4E+dz51JIVfZssd5LryMEt G4mZ7FJYt6kN8GYDZOYbiVC5gBnFuq+a953YFjtQKPlSt0yp80 4+QIbHeIAEcwmcHesqVnXTOkU4ZDPNQDm1pm96tGKic7EFia4a qSro9bW1Xhjh/cqoaodrRBIFsiCGW0YHyHmd1rph+2ILrVVDNy CgNq9
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/kfQ6OvT1MZoRyBkL6weK4wWXycE
Subject: Re: [TLS] Minutes from Tuesday
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: Tue, 11 Nov 2014 11:56:48 -0000

2014-10-22 3:35 GMT+02:00 Adam Langley <agl@google.com>:

> On Tue, Oct 21, 2014 at 9:41 AM, Bodo Moeller <bmoeller@acm.org> wrote:
> > That's not right: YouTube video streams currently can use two cipher
> suites,
> > TLS_RSA_WITH_AES_128_GCM_SHA256 and TLS_RSA_WITH_RC4_128_SHA. The
> > interoperability problem mentioned in the meeting was that
> > TLS_RSA_WITH_AES_128_GCM_SHA256 (without ECDHE) isn't a supported cipher
> > suite in Firefox, and RC4 is RC4;
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1029179.
>


> (And TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 support is coming -- it's
> already enabled in some locations.)
>

And by now, should be enabled everywhere.

v2.23.0 | Report a Bug | By Email