[dnsoverhttp] HTTP/2

Martin Thomson <martin.thomson@gmail.com> Mon, 30 October 2017 01:27 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: dnsoverhttp@ietfa.amsl.com
Delivered-To: dnsoverhttp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED5513FD1A for <dnsoverhttp@ietfa.amsl.com>; Sun, 29 Oct 2017 18:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 N3tCcCS-tVu0 for <dnsoverhttp@ietfa.amsl.com>; Sun, 29 Oct 2017 18:27:22 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B21C13FCDB for <dnsoverhttp@ietf.org>; Sun, 29 Oct 2017 18:27:22 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id q4so19407958oic.7 for <dnsoverhttp@ietf.org>; Sun, 29 Oct 2017 18:27:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=G4jKFknWUr64lRUubAFJ3iS4hne7S4fuTg3XE0VV2tQ=; b=H+8WbEPrfxVR+bXwi4nCRFaqlw7xbGXeGYQDfGykkoD+UZbgIiAV/wE9Xu9JuYX12b ewWFTy8pLSvEXZp7KfUcEj/00noLGThnCNj0C5PsQrF8bBDOtdCiwDvH0FqT/fTNd9gK DvCDjjlWk9hUqqpaP6ORUIaPlYZpZDq/nSb0f//LEq86l2/y+Q3J71XN1UdoaUk3ytR/ cl2b49JqdjLBh7fuBX4lI8u4IVmHeloGJE3AgqmeL+m+wkSahZnn/DIQSbwJgvSP7TeI +tT9OVQ/lXt0VNIuKqKb4avvsEu2fO85CKmv0US28Wgg5USV6KqYfwT7IUQPULv2XKmT OVLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=G4jKFknWUr64lRUubAFJ3iS4hne7S4fuTg3XE0VV2tQ=; b=j32fNdaA81QlNRvxj61glQvLWMf4E7YAGVoP3UnLjQaniTIFkzrkRMpIkmEyDA3doy 6QOljM8QEEzoMXcmJ7XexZ8wai4oyeSnJNqrCKzuVPNDTaiJ3clSd1K92cdfBZQpuWZD WiuMfh2o67l7cfVPBVF8q4Q6567o9y9848PYIlXg8/DitsDwJtduCQx28iIlODih4XnC Sp2Lcqc5XDaznClracNToUKxj5IVx7cyJzpVCFAUXPXeO7ITkZi0SRRmX+sTDuI84NpK wYyChI4kzaoYhuZMm+Jmgdo+knZVRpQW9fM+zob2RZzLlvjsFDpXp64pLmSD18VxaHg0 xC0g==
X-Gm-Message-State: AMCzsaX0gsl7XV08IsuyaEpGeqZCOstl0uYsz5bpshPCPSV1dJUoTCGh fB/PvrblLcn0Nd9V8t8PpXsr4Q+ZyRPSqM9EQREmPMsy
X-Google-Smtp-Source: ABhQp+QjyqzugSAJnRl1S51YMencrJ6W0TWX+chUHcDWitlv9aTUlV6yKiq9pOJ/igjDwWinbtmPKIBWLjhKj0n24PQ=
X-Received: by 10.157.91.61 with SMTP id x58mr4910163oth.89.1509326841151; Sun, 29 Oct 2017 18:27:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.72.178 with HTTP; Sun, 29 Oct 2017 18:27:20 -0700 (PDT)
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 30 Oct 2017 12:27:20 +1100
Message-ID: <CABkgnnXBdsYLv4dHiLH4GdvYCvDZ3JRxS6jG6Z-VvoMyfCkHLw@mail.gmail.com>
To: dnsoverhttp@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsoverhttp/iOMRrBecjWmsSoiXHYFuzMnySTM>
Subject: [dnsoverhttp] HTTP/2
X-BeenThere: dnsoverhttp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of DNS over HTTP <dnsoverhttp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsoverhttp>, <mailto:dnsoverhttp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsoverhttp/>
List-Post: <mailto:dnsoverhttp@ietf.org>
List-Help: <mailto:dnsoverhttp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsoverhttp>, <mailto:dnsoverhttp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 01:27:24 -0000

I've said this elsewhere, but I don't think that mandating HTTP/2 is
necessary [11].

The draft does this to pick up the security requirements of HTTP/2,
but that can be achieved in other ways that are less disruptive to the
stack.  I would prefer that we soften the requirement and encourage
the use of good practices - HTTP/2 certainly has many virtues that
make it a good choice - but not mandate a specific version.  See also
[56] and [7525].

I do think that the draft needs to be more precise about server push.
Right now, the description of server push is rather oblique and it
could use some more clarity [12].

[11] https://github.com/paulehoffman/draft-ietf-doh-dns-over-https/issues/11
[56] https://mnot.github.io/I-D/bcp56bis/#specifying-the-use-of-http
[7525] https://tools.ietf.org/html/rfc7525
[12] https://github.com/paulehoffman/draft-ietf-doh-dns-over-https/issues/12