[Doh] Implementation of DOH in dnsmasq

Mateusz Jończyk <mat.jonczyk@o2.pl> Thu, 14 June 2018 19:33 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 B88F9130EE0 for <doh@ietfa.amsl.com>; Thu, 14 Jun 2018 12:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 0ZzhiByCHZls for <doh@ietfa.amsl.com>; Thu, 14 Jun 2018 12:33:00 -0700 (PDT)
Received: from mx-out.tlen.pl (mx-out.tlen.pl [193.222.135.142]) (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 1D7F5130E88 for <doh@ietf.org>; Thu, 14 Jun 2018 12:32:59 -0700 (PDT)
Received: (wp-smtpd smtp.tlen.pl 2941 invoked from network); 14 Jun 2018 21:32:56 +0200
Received: from agkn52.neoplus.adsl.tpnet.pl (HELO [192.168.1.22]) (mat.jonczyk@o2.pl@[217.99.141.52]) (envelope-sender <mat.jonczyk@o2.pl>) by smtp.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted SMTP for <doh@ietf.org>; 14 Jun 2018 21:32:56 +0200
From: Mateusz Jończyk <mat.jonczyk@o2.pl>
To: dnsmasq-discuss@lists.thekelleys.org.uk, DoH WG <doh@ietf.org>
Openpgp: preference=signencrypt
Message-ID: <ebce03d1-eb9a-e209-8bf0-08034a6fedb4@o2.pl>
Date: Thu, 14 Jun 2018 21:32:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="Ho8eJquasGR2jO5qGav0nMqKDmcLs7Vrt"
X-WP-MailID: e7ae8f3d53dd91075b8fa3fa30d12e7e
X-WP-AV: skaner antywirusowy Poczty o2
X-WP-SPAM: NO 0000000 [8SNk]
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/I2QCxf33C3Hpm3p4P9r8jkyV9sE>
Subject: [Doh] Implementation of DOH in dnsmasq
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.26
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: Thu, 14 Jun 2018 19:33:02 -0000

// I am writing to dnsmasq developers to ask them about viability of
// implementing HTTP/2 in dnsmasq.

Hello,

As You may know, IETF is developing a new standard called DOH - DNS over HTTPS.
It will allow tunelling DNS requests over HTTPS.

Current version of the standard can be found on
	https://github.com/dohwg/draft-ietf-doh-dns-over-https/blob/master/draft-ietf-doh-dns-over-https-latest.mkd

This standard is currently being finished.

Current version of this standard recommends use of HTTP/2.0 as the data
transport, but allows use of earlier versions of HTTP. It does not, however,
require clients to support servers that talk HTTP/1.0 or HTTP/1.1 only.

How difficult would it be to add support to DNS over HTTP/2.0 in dnsmasq, for
example in constrained environments like home routers?

Please send any replies to the DoH mailing list at <doh@ietf.org>.


Greetings,
Mateusz Jończyk