IETF Logo Mail Archive

Re: [TLS] Questions about ALPN

Martin Thomson <martin.thomson@gmail.com> Wed, 09 April 2014 20:53 UTC

Return-Path: <martin.thomson@gmail.com>
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 94B2D1A023F for <tls@ietfa.amsl.com>; Wed, 9 Apr 2014 13:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 ar9WMpTNpw4W for <tls@ietfa.amsl.com>; Wed, 9 Apr 2014 13:53:51 -0700 (PDT)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 966321A025E for <tls@ietf.org>; Wed, 9 Apr 2014 13:53:51 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id x48so2951918wes.7 for <tls@ietf.org>; Wed, 09 Apr 2014 13:53:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ccMv9zp4LceqHacANnjkfguqAmKeaMUSDDKjoAGnTMs=; b=vzjLM9Wajw9uMVgjwIdEcvVDWva+f3gB1DGz1yr/vvAzwUkT3c51BWgHpcZ/CdjSNw STb8KT9Z56G4LCYOfOH1voEic0biegFgqJ3s7Idh58wo7UJJPu1dynyMbmAa8M4ASfbV k65S5vpfmK0c5z5RXF4/+YgXMmZEGjpDDWOeAL8Dza90i7QqQnMUFauNW8kB00NVFKlt 6iuZi8os1uGvy1e4MQ0YqtOMW0f8UFJPSs7w/KUrvWXvTKjcQKvf2n4GV9B6/2A+GVUS U+KLnHcJHEjlPGFpAlEXBx9vF8V3hEMzNpK+HPsAzm09aze2owmhTflGuzPbETPc3+D/ ktNA==
MIME-Version: 1.0
X-Received: by 10.180.92.196 with SMTP id co4mr11853233wib.50.1397076830592; Wed, 09 Apr 2014 13:53:50 -0700 (PDT)
Received: by 10.227.144.132 with HTTP; Wed, 9 Apr 2014 13:53:50 -0700 (PDT)
In-Reply-To: <719f0ee665324b929a0da56e127588fe@BL2PR03MB419.namprd03.prod.outlook.com>
References: <53456D1B.1010804@alum.mit.edu> <CAL9PXLzF5AZ4WuTdCUBu3BY0BDRBj=120DnJefMd7hs-0hcU5w@mail.gmail.com> <CABkgnnUvfHUwHH-BKQjHqToao4FqzRTRhHZBw7cROFXoq1Ftiw@mail.gmail.com> <CAL9PXLw1Z-MBU0N=BWdiXW=C9rjG7pXc7zhnOdzwMUavSb-GwQ@mail.gmail.com> <4bf0dffe7f4e475abf38f1e14e09388e@BL2PR03MB419.namprd03.prod.outlook.com> <CABkgnnUPM=AQTk6y2juQoEcPksNWSTCkgPe4846FWDwm5waxPQ@mail.gmail.com> <e01a57761d5d4776968b0d26e86b44b9@BL2PR03MB419.namprd03.prod.outlook.com> <CABkgnnUSU_R2DmCjLV2FPFVX4TCfOfFEZ7ta5bVdakc3bsVkZA@mail.gmail.com> <53459638.50309@alum.mit.edu> <f6cfbd996c9c4456bcfb2fbec10f9f13@BL2PR03MB419.namprd03.prod.outlook.com> <53459E6B.4030900@alum.mit.edu> <5c4a4616b1d34efbb85643d1f26e5410@BL2PR03MB419.namprd03.prod.outlook.com> <CABkgnnX7W8axLhhVg1wUmaUSmHZ_0F+=0ypKC=sN4utp9iD04g@mail.gmail.com> <719f0ee665324b929a0da56e127588fe@BL2PR03MB419.namprd03.prod.outlook.com>
Date: Wed, 09 Apr 2014 13:53:50 -0700
Message-ID: <CABkgnnVF4Dt+uOciVSYggvkcauhkhOfn8x_m9cMy3LWET85bag@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Andrei Popov <Andrei.Popov@microsoft.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/OQpj5RjgpUwDrTassHmU52mjU0Q
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Questions about ALPN
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, 09 Apr 2014 20:53:54 -0000

On 9 April 2014 13:23, Andrei Popov <Andrei.Popov@microsoft.com> wrote:
> This is why I feel that "HTTP/2 over TLS" makes little sense specifically in the context of ALPN, and "HTTP/2 over TCP" makes even less sense in this context. Both of these protocol stack identifiers may be useful outside the context of ALPN, as you correctly explain.

Agreed.

I think that we only disagree on the scope of the registry.  I'll note
that we've consensus in httpbis to use the greater scope, and will
(reluctantly) establish a separate registry if we need to.  We'll
probably put in a non-overlapping + inclusion requirement for the ALPN
registry to avoid issues.  It would be easier for us to just use
ALPN's registry.

v2.23.0 | Report a Bug | By Email