Re: [Doh] HTTP/2 and constrained environments

Martin Thomson <martin.thomson@gmail.com> Wed, 23 May 2018 22:41 UTC

Return-Path: <martin.thomson@gmail.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 95A3F12D86D for <doh@ietfa.amsl.com>; Wed, 23 May 2018 15:41:16 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 EeFqWWrTbqHV for <doh@ietfa.amsl.com>; Wed, 23 May 2018 15:41:12 -0700 (PDT)
Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::231]) (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 3B74212E8E4 for <doh@ietf.org>; Wed, 23 May 2018 15:41:08 -0700 (PDT)
Received: by mail-ot0-x231.google.com with SMTP id g7-v6so27141286otj.11 for <doh@ietf.org>; Wed, 23 May 2018 15:41:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=8EheOuRpw4wpXt7x9eulozrlnLfXHQALF/C1lB6dcGQ=; b=fSPQQClr8weswQJ69qBZW3PV8vF+idyjtg3qKJiGKMvT8QvT8Aw4WRORhMEWJwDe6q 7Cu37DSbN6bmVdc43ET0OVpBBHy49XeJoOne6+nYVoGdc6irctw3PGQYR/+zy8gHOY6T FeqA5TKEaPks6W185L7K3W2KM+GgjRW/6PoL47dwPNq1wofiWIbl+TBsD/k6AGwPuTVp V2YtKpOBah2ykRjYwEITEmmuD27blrsDwJNlQeH7j0lFvvlR2i+ibbwyXlP1G6c+TYCQ zxideXigCBc9RLShV2BQYAWYw6uuDXw0U69FppMEaGlHLIGzUxntXNJmEB6VaAs1KL+t Ewnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=8EheOuRpw4wpXt7x9eulozrlnLfXHQALF/C1lB6dcGQ=; b=mM8IrG/gXjlT0r9BXdMHhjDlXI3znlyowXnmNK9cpzu3FYn7Kz3fpsUOOepz2JMiY5 vRjhTEWkFX7cfpb6s52UiCEcBGO9n5NFdtV/jPJfHBWJlRye2+IsxmrzIUVjNRik5ezR iaUVzjmQCVO4WnsgiTkqddNP8gN62VyXbMQBg4PFROLJsoUBUj6iblJYorG7Thzs1H1N PNe5xoqq5KgnIP9XnkfivNe7ZczKABvzh4Ki+KtRpMrxtTqruP5fXN4gItnMB6mLr2z3 X8cG5TZ0CO6Wd+OOgKStbzLYXeXeIvfq0k9PK9bTTTQVFRPmEGr5IodJhKu/eRvncDnK /jZw==
X-Gm-Message-State: ALKqPwcTs6UZyFLkmXeEUcJ4f2Ixg95ErUjqh7+fhCUlRToWWBl+WCoA 0Z9xy4065HA0YkbWQC7BcImV2pUIbj7s+bmCmlY=
X-Google-Smtp-Source: AB8JxZqcmKLM6MbOkLNFAdpp7OJrixAMhJkp7zXUBB4LN0tTRiTUIfvIgtLd25BF3uydZOTlfOuFpF26GCNzpsGhPds=
X-Received: by 2002:a9d:354a:: with SMTP id l10-v6mr3210549ote.15.1527115267567; Wed, 23 May 2018 15:41:07 -0700 (PDT)
MIME-Version: 1.0
References: <4b620bc5-9445-f3b0-cc3d-2ad2b9ac154a@o2.pl> <CAOdDvNpMzArPtoFUp_BtHtmZn4jgFmMT20mDFBEv+j5cF2Og9A@mail.gmail.com>
In-Reply-To: <CAOdDvNpMzArPtoFUp_BtHtmZn4jgFmMT20mDFBEv+j5cF2Og9A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 24 May 2018 08:40:56 +1000
Message-ID: <CABkgnnWWU_dn+FqivQt02dy=ONwckL8khZrkHHJAST8DQJjM8g@mail.gmail.com>
To: patrick mcmanus <pmcmanus@mozilla.com>
Cc: =?UTF-8?Q?Mateusz_Jo=C5=84czyk?= <mat.jonczyk@o2.pl>, DoH WG <doh@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/orneZVqi9hTIoY1M6rodw3HacTE>
Subject: Re: [Doh] HTTP/2 and constrained environments
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: Wed, 23 May 2018 22:41:24 -0000

See also https://tools.ietf.org/html/draft-montenegro-httpbis-h2ot-00
On Thu, May 24, 2018 at 7:13 AM Patrick McManus <pmcmanus@mozilla.com>;
wrote:



> On Wed, May 23, 2018 at 5:40 AM, Mateusz Jończyk <mat.jonczyk@o2.pl>;
wrote:


>> How difficult it would be to implement HTTP/2 on a home router with 8 MB
of
>> flash and 32 MB of RAM? Would it at all be possible?


> no problem really. HTTP/2 provides a number of mechanisms for either peer
to scale things down (e.g.reducing state in the compression dictionary,
limiting the number of outstanding streams , small flow control windows,
etc ).

> searching for nginx and dd-wrt yields lots of howto's
https://www.dd-wrt.com/phpBB2/viewtopic.php?t=312701&sid=dfc6638ad8a57c7d3540d4b3aae828d3
  .. nginx has http/2 support.


>> Would it be much more
>> difficult to implement than HTTP/1.0? All of my routers support only
HTTP/1..0 in
>> the management interface.


> I'm just speculating, but I suspect that has more to do with https and
the challenges of provisioning certs on that kind of device than anything
else.


>> Would it be beneficial to specify that DNS API clients SHOULD support
DNS API
>> servers that only talk HTTP/1.0 or HTTP/1.1?


> imo we shouldn't be explicitly encouraging older protocols.



> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh