IETF Logo Mail Archive

Re: [TLS] Confirming consensus for ALPN

Adam Langley <agl@imperialviolet.org> Fri, 22 March 2013 11:38 UTC

Return-Path: <alangley@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B08EF21F896C for <tls@ietfa.amsl.com>; Fri, 22 Mar 2013 04:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iNq8OjVmTAZK for <tls@ietfa.amsl.com>; Fri, 22 Mar 2013 04:38:32 -0700 (PDT)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 89EE221F8511 for <tls@ietf.org>; Fri, 22 Mar 2013 04:38:31 -0700 (PDT)
Received: by mail-la0-f46.google.com with SMTP id fq12so7082753lab.33 for <tls@ietf.org>; Fri, 22 Mar 2013 04:38:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=c850e4S/xMJQbvvMucSJzgZQoXWQS/hDIHWQXrcWbuA=; b=v0GNPrnuk78j+Kx+JNi67jtMaBXBmyKAE7Lar7y8PQuG1crij6AD5CTYeErNGTRiNZ lCW/zkdfXTaq72WnBQtn06SZoWiqonIHajt1U1FF0t/hM/rIr4ffjzC6EECQJtooQuwT e36A4eaoo20PgUTvUW1tMXcmpNVcNwX6vGm9LPXZ4BTB2A1LKY1ktYfhB+zux/D00X0q FuREgKdo+glffiYJS3/ld0nHM8Tbxvm04auD83n7hQ1EMVnJAGLnxhlX55ownnxtHIeS yiZwPDxJIYtbWIAEZZBs5j3BwinaKyvRd0X3i6jHp0iNUj6G1e/IwgHqxXpfkoZ9r7/C cV8w==
MIME-Version: 1.0
X-Received: by 10.112.42.162 with SMTP id p2mr925501lbl.103.1363952310486; Fri, 22 Mar 2013 04:38:30 -0700 (PDT)
Sender: alangley@gmail.com
Received: by 10.112.61.7 with HTTP; Fri, 22 Mar 2013 04:38:29 -0700 (PDT)
In-Reply-To: <514BE843.3040808@KingsMountain.com>
References: <514BE843.3040808@KingsMountain.com>
Date: Fri, 22 Mar 2013 07:38:29 -0400
X-Google-Sender-Auth: y1hPC7GkW8BUu-yD1QvU9M3qBbc
Message-ID: <CAMfhd9UcyJ0k6vM319MN+e=NbaHXpU9zAc4c7JLrh11ECaWzUA@mail.gmail.com>
From: Adam Langley <agl@imperialviolet.org>
To: =JeffH <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset="UTF-8"
Cc: IETF TLS WG <tls@ietf.org>
Subject: Re: [TLS] Confirming consensus for ALPN
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 22 Mar 2013 11:38:32 -0000

On Fri, Mar 22, 2013 at 1:12 AM, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
> Ok, but it's not clear from the above what you were advocating --
> draft-agl-tls-nextprotoneg-04 or "current code" ?

I was advocating draft-agl-tls-nextprotoneg-04

> Was the aforementioned transformation in the currently shipping code (eg
> Chrome Version 25 or thereabouts) or in draft-agl-tls-nextprotoneg-04 ?

The latter. The currently shipping code was always going to change, if
nothing else because of a change of extension number.


Cheers

AGL

--
Adam Langley agl@imperialviolet.org http://www.imperialviolet.org

v2.23.0 | Report a Bug | By Email