[Doh] HTTP/2 and constrained environments

Mateusz Jończyk <mat.jonczyk@o2.pl> Wed, 23 May 2018 09:40 UTC

Return-Path: <mat.jonczyk@o2.pl>
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 4FBBD12DA68 for <doh@ietfa.amsl.com>; Wed, 23 May 2018 02:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 gVCq3IEI5Pko for <doh@ietfa.amsl.com>; Wed, 23 May 2018 02:40:36 -0700 (PDT)
Received: from mx-out.tlen.pl (mx-out.tlen.pl [193.222.135.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 085E012DA49 for <doh@ietf.org>; Wed, 23 May 2018 02:40:35 -0700 (PDT)
Received: (wp-smtpd smtp.tlen.pl 27883 invoked from network); 23 May 2018 11:40:32 +0200
Received: from agsm225.neoplus.adsl.tpnet.pl (HELO [192.168.1.22]) (mat.jonczyk@o2.pl@[217.99.90.225]) (envelope-sender <mat.jonczyk@o2.pl>) by smtp.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted SMTP for <doh@ietf.org>; 23 May 2018 11:40:32 +0200
To: DoH WG <doh@ietf.org>
From: =?UTF-8?Q?Mateusz_Jo=c5=84czyk?= <mat.jonczyk@o2.pl>
Openpgp: preference=signencrypt
Message-ID: <4b620bc5-9445-f3b0-cc3d-2ad2b9ac154a@o2.pl>
Date: Wed, 23 May 2018 11:40:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hGDx7CwmlFNUMEej5Ifr6nbVp6aO45Lxl"
X-WP-MailID: df03ceb466991badfaac68350b07a800
X-WP-AV: skaner antywirusowy Poczty o2
X-WP-SPAM: NO 0000000 [0eM0]
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/Y5TizWEkwqNImSd7rjVvX8gkkls>
Subject: [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 09:40:46 -0000

Hello,
I have been thinking about the possibility of running a DOH API server on a home
router - mostly for resolution of names of local devices.

Currently, most (if not a vast majority) of home routers are capable of working
as a DNS forwarder.

One of my routers (FunBox 2.0, provided by my ISP - Orange) has a DNS server
with the capability to resolve names of local devices. As we all know, IPs of
local devices may be assigned via DHCP, so they change from time to time. To
have static names, it is possible to assign DNS names to MAC addresses so that
irrespectively of the IP address the device gets, it may be resolved by the DNS
name by the local DNS/DHCP server.

Performance in this case would not be critical, as requests would be rare.

I am not sure if this is currently supported by dnsmasq.

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? 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.

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?

We may ask for input from dnsmasq developers.

Greetings,
Mateusz Jończyk