Return-Path: X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8E9B1A1A72 for ; Thu, 5 Feb 2015 14:25:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.289 X-Spam-Level: X-Spam-Status: No, score=-6.289 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 kmDEHernAwwF for ; Thu, 5 Feb 2015 14:25:12 -0800 (PST) Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 579CD1A0673 for ; Thu, 5 Feb 2015 14:25:12 -0800 (PST) Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from ) id 1YJUoB-0002FC-Na for ietf-http-wg-dist@listhub.w3.org; Thu, 05 Feb 2015 22:21:59 +0000 Resent-Date: Thu, 05 Feb 2015 22:21:59 +0000 Resent-Message-Id: Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from ) id 1YJUo6-0002ER-HU for ietf-http-wg@listhub.w3.org; Thu, 05 Feb 2015 22:21:54 +0000 Received: from mail-qg0-f49.google.com ([209.85.192.49]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from ) id 1YJUo5-0003Ql-Aw for ietf-http-wg@w3.org; Thu, 05 Feb 2015 22:21:54 +0000 Received: by mail-qg0-f49.google.com with SMTP id e89so8484660qgf.8 for ; Thu, 05 Feb 2015 14:21:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=em2ZxZ5xbSONgWWCYWbO3Cz8Yy2bMbMVIgPU/UkYDLI=; b=1FZm0FwaASzX9/pwzC6rWbzCVnIcFsmrq34hvDxDvw77q8GIj752cXgOoany3Xk0My GMBWCcwahgN6VaZkZivh4YxeMvNlO5X+VFkJwQyo5SJ3IotEzFHidHmFmd+Far3fyFaX aJAYH2f2aMELhjKmgL4/haIaPoNUZ9ypPs2nSoCa06WIfMPUFk8UmryT1rxvdHwB5U2I 0XBNUX3jlrtN6jYsau4ogA/vkSQbrScq9+Y+edJ6kaj4sH4EZPMEpWkxTy13fCv5WR21 0KP0rS9HRCAu7FUEKUMUy1D0rD2C81C/6pmQwLnMqBDuPFAGNKZzBT/6XU1SR1Q2uBBf 8SKg== MIME-Version: 1.0 X-Received: by 10.140.89.41 with SMTP id u38mr953522qgd.20.1423174886799; Thu, 05 Feb 2015 14:21:26 -0800 (PST) Sender: nygren@gmail.com Received: by 10.140.84.47 with HTTP; Thu, 5 Feb 2015 14:21:26 -0800 (PST) In-Reply-To: <20150205162845.GA13872@LK-Perkele-VII> References: <20150205162845.GA13872@LK-Perkele-VII> Date: Thu, 5 Feb 2015 17:21:26 -0500 X-Google-Sender-Auth: lBxkYH9d9lurwT8jTZBfTecqVwc Message-ID: From: Erik Nygren To: Ilari Liusvaara Cc: "ietf-http-wg@w3.org Group" Content-Type: multipart/alternative; boundary=001a11c135de954240050e5eb9f7 Received-SPF: pass client-ip=209.85.192.49; envelope-from=nygren@gmail.com; helo=mail-qg0-f49.google.com X-W3C-Hub-Spam-Status: No, score=-3.3 X-W3C-Hub-Spam-Report: AWL=-2.638, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 X-W3C-Scan-Sig: maggie.w3.org 1YJUo5-0003Ql-Aw 43a7f0baa1a48f967ac2ae67df706bd0 X-Original-To: ietf-http-wg@w3.org Subject: Re: http2 opportunistic security negotiation Archived-At: Resent-From: ietf-http-wg@w3.org X-Mailing-List: archive/latest/28765 X-Loop: ietf-http-wg@w3.org Resent-Sender: ietf-http-wg-request@w3.org Precedence: list List-Id: List-Help: List-Post: List-Unsubscribe: --001a11c135de954240050e5eb9f7 Content-Type: text/plain; charset=UTF-8 On Thu, Feb 5, 2015 at 11:28 AM, Ilari Liusvaara < ilari.liusvaara@elisanet.fi> wrote: > > Even TLS 1.3 won't encrypt the ALPN (at least as TLS 1.3 currently is). Why can't the server's ALPN response be in EncryptedExtensions for a TLS 1.3 ServerHello even if the client's ALPN (a superset so less interesting) is in-the-clear in the ClientHello? Erik --001a11c135de954240050e5eb9f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, Feb 5, 2015 at 11:28 AM, Ilari Liusvaara <ilari.liusvaara@e= lisanet.fi> wrote:

Even TLS 1.3 won't encrypt the ALPN (at least as TLS 1.3 current= ly is).


Why can't the server's ALPN respon= se be in EncryptedExtensions for a TLS 1.3 ServerHello
even if the clien= t's ALPN (a superset so less interesting) is in-the-clear in the Client= Hello?

=C2=A0=C2=A0=C2=A0=C2=A0 Erik

--001a11c135de954240050e5eb9f7--