Re: [Doh] How to start HTTP/2?

Patrick McManus <pmcmanus@mozilla.com> Tue, 16 January 2018 15:31 UTC

Return-Path: <pmcmanus@mozilla.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2A5131528 for <doh@ietfa.amsl.com>; Tue, 16 Jan 2018 07:31:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 NoKMlZdFjCea for <doh@ietfa.amsl.com>; Tue, 16 Jan 2018 07:31:06 -0800 (PST)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id CDE1F131568 for <doh@ietf.org>; Tue, 16 Jan 2018 07:29:59 -0800 (PST)
Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) by linode64.ducksong.com (Postfix) with ESMTPSA id 907493A069 for <doh@ietf.org>; Tue, 16 Jan 2018 10:29:56 -0500 (EST)
Received: by mail-lf0-f52.google.com with SMTP id q17so7726960lfa.9 for <doh@ietf.org>; Tue, 16 Jan 2018 07:29:56 -0800 (PST)
X-Gm-Message-State: AKwxytcSvtg+G2RykNjwMVKurqOcwh9ViYEQGjTP5W3BJBKVGZbPmmfi qsxmIWKbvwG9Z2QjfyUwzlPC+JB2P3pOcyzp91M=
X-Google-Smtp-Source: ACJfBosGPVJENaUvrvjthjEtOH1Uzn+M+WOz7U3OR/peEzzoECCWHjXAuB/6+z8CHmacQHznwjL5knk1vt6QzVun3xE=
X-Received: by 10.25.142.203 with SMTP id a72mr12821549lfl.79.1516116595166; Tue, 16 Jan 2018 07:29:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.166.201 with HTTP; Tue, 16 Jan 2018 07:29:54 -0800 (PST)
In-Reply-To: <20180116152145.qhgqoo3dqmebb6aa@nic.fr>
References: <20180116150246.dvr3d3nstozqfadn@nic.fr> <alpine.DEB.2.20.1801161607110.20551@tvnag.unkk.fr> <20180116152145.qhgqoo3dqmebb6aa@nic.fr>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Tue, 16 Jan 2018 10:29:54 -0500
X-Gmail-Original-Message-ID: <CAOdDvNqTB=RxtJ5+ykbN_4KKhZS=_DnPdpK3yPh0cL2ey-7GKA@mail.gmail.com>
Message-ID: <CAOdDvNqTB=RxtJ5+ykbN_4KKhZS=_DnPdpK3yPh0cL2ey-7GKA@mail.gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Daniel Stenberg <daniel@haxx.se>, doh@ietf.org
Content-Type: multipart/alternative; boundary="f403045f4c7c17d5170562e66702"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/8CFDGG6L13qzKY8XYF7z6kkLdzI>
Subject: Re: [Doh] How to start HTTP/2?
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2018 15:31:09 -0000

On Tue, Jan 16, 2018 at 10:21 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>
wrote:

> On Tue, Jan 16, 2018 at 04:12:39PM +0100,
>  Daniel Stenberg <daniel@haxx.se> wrote
>  a message of 27 lines which said:
>
> > If you stick to HTTPS (which the spec says we must in section 4)
> > then there's only one way: negotiate HTTP version with ALPN. It also
> > happens to be the easiest way for clients IMHO.
>
> OK, but could it be better to say explicitely "Servers and clients
> MUST start HTTP/2 using the ALPN extension of TLS, as specified in RFC
> 7540, section 3.3"?
>
>
imo, no.. a] h2 isn't required.. and even where its a should it is h2 or
its successors. successors might do it differently.

b] a large point of using h2 as a substrate is that you just reuse h2 and
don't need to restate things (possibly incorrectly by accident)

c] h2 can be extended in ways that could conflict with that language. I
don't see the value in forcing those extensions to be aware enough to also
extend DoH.


> (Then, what a server should do if the client did not use ALPN? Start
> HTTP/2 anyway, because of the robustness principle?)
>
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>