Re: SNI requirement for H2

Roberto Peon <grmocg@gmail.com> Fri, 03 April 2015 19:10 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
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 AF49B1B2A28 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Apr 2015 12:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 2ikRC0yQPCny for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 Apr 2015 12:10:40 -0700 (PDT)
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 BB04E1ACF6C for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 3 Apr 2015 12:10:40 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Ye6vr-0006jQ-Bj for ietf-http-wg-dist@listhub.w3.org; Fri, 03 Apr 2015 19:07:07 +0000
Resent-Date: Fri, 03 Apr 2015 19:07:07 +0000
Resent-Message-Id: <E1Ye6vr-0006jQ-Bj@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <grmocg@gmail.com>) id 1Ye6vn-0006ia-EW for ietf-http-wg@listhub.w3.org; Fri, 03 Apr 2015 19:07:03 +0000
Received: from mail-ob0-f169.google.com ([209.85.214.169]) by lisa.w3.org with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128) (Exim 4.80) (envelope-from <grmocg@gmail.com>) id 1Ye6vm-0000aT-Jp for ietf-http-wg@w3.org; Fri, 03 Apr 2015 19:07:03 +0000
Received: by obvd1 with SMTP id d1so182019385obv.0 for <ietf-http-wg@w3.org>; Fri, 03 Apr 2015 12:06:36 -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; bh=ktRkKpjTqGGK8fgb2nliW32AWFxtbvgHEJPyTYX4oDU=; b=RGqdQjX/jVICs42we3KKlcByRcXhNxAOew8d8Y8C5M+f+C70ei0uEOQMqWFxrAmIP6 ymmS7gDETMSiKHTW7emfqEguD2+bfqY0xPHeSW9E2ZU794W9Cggp46q9/uy9PJFvv2Hw 9ml9JId6j456i4zKTGhvTzQpRkivAM8Dz1FKtAqodoDrwXyhqZJG7iQGEUIWaYT1n0T9 TPReWZ8aqwGXOKwJVeQRnkbxATN9JymMhhMfURskUH7HjwruTsZnE4JwdZnYPgHWQ6K0 bNqo/AqOgJuQAK24DmkDilU1v5WgRyUnr6ytkhtn3ljszglQ5khhyTF/j+lakWDabu+D nfHw==
MIME-Version: 1.0
X-Received: by 10.60.47.80 with SMTP id b16mr4604215oen.10.1428087996711; Fri, 03 Apr 2015 12:06:36 -0700 (PDT)
Received: by 10.76.128.51 with HTTP; Fri, 3 Apr 2015 12:06:36 -0700 (PDT)
In-Reply-To: <CAGxKgz2-5OSwPGs=S_EVwPv-dYvPSO-H4YCiXX5wt-CxTxMVpg@mail.gmail.com>
References: <CAGxKgz2-5OSwPGs=S_EVwPv-dYvPSO-H4YCiXX5wt-CxTxMVpg@mail.gmail.com>
Date: Fri, 03 Apr 2015 12:06:36 -0700
Message-ID: <CAP+FsNcGAJjRXpQPKOs9rLk-5=JYjj24=DxNHCAv+Mib5v+2GA@mail.gmail.com>
From: Roberto Peon <grmocg@gmail.com>
To: Nicholas Hurley <hurley@mozilla.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a11c20fb8c08a680512d6a559"
Received-SPF: pass client-ip=209.85.214.169; envelope-from=grmocg@gmail.com; helo=mail-ob0-f169.google.com
X-W3C-Hub-Spam-Status: No, score=-6.5
X-W3C-Hub-Spam-Report: AWL=0.289, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1Ye6vm-0000aT-Jp 1c3845931011140154b66b2fdf986a32
X-Original-To: ietf-http-wg@w3.org
Subject: Re: SNI requirement for H2
Archived-At: <http://www.w3.org/mid/CAP+FsNcGAJjRXpQPKOs9rLk-5=JYjj24=DxNHCAv+Mib5v+2GA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29238
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Does anyone recall why 6066 has no SNI for IP literals? (It could be an
empty SNI field or the SNI could indicate the IP literal)?
-=R

On Fri, Apr 3, 2015 at 11:37 AM, Nicholas Hurley <hurley@mozilla.com> wrote:

> All,
>
> While looking at https://github.com/molnarg/node-http2/issues/69 I came
> to the realization that it appears we have (unintentionally) made it
> impossible to speak h2 when connecting directly to an IP address (as in, IP
> address typed into URL bar as opposed to hostname typed into URL bar) and
> remain compliant with both the h2 spec and RFC 6066. 6066 specifies that
> SNI is not to be sent for an IP literal, while h2 requires SNI. You can see
> the conflict.
>
> In node-http2, we have decided to relax the SNI requirement, and still
> speak h2 to clients that don't give us any SNI, under the assumption that
> this (IP in URL bar, or equivalent) is the case we are hitting. I had also
> filed a bug against Firefox to stop advertising h2 in the cases where we
> won't send SNI, but am rethinking that idea, as it was pointed out (rightly
> so) that a lot of test servers never have a hostname associated with them,
> and not being able to talk h2 to test servers seems like a Bad Idea :)
>
> FWIW, I checked Safari, Chrome, IE (11 on Windows 7), and Firefox. Both
> Safari and Chrome send SNI regardless of IP or hostname, so they will not
> run into this problem. IE and Firefox both send SNI only for hostnames (at
> least in the configurations I tested), so they will hit this problem.
> (Obvious caveat: non-Firefox browsers may have changed their behavior in
> later versions than I have access to, so of course my testing may not hold
> true in the future.)
>
> I talked briefly to Martin offline, and he says we may be able to get a
> clarification on this point in during AUTH48 to (my words, now, not his)
> perhaps relax this restriction, or at least make it clear that you probably
> don't need to require SNI in a testing situation, in order to avoid this
> problem.
>
> Thoughts?
>