[DNSOP] Soon-to-come DNS over HTTP drafts

Shane Kerr <shane@time-travellers.org> Wed, 04 November 2015 05:03 UTC

Return-Path: <shane@time-travellers.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id AA66B1AC442 for <dnsop@ietfa.amsl.com>; Tue, 3 Nov 2015 21:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 78HYnXY3LA2n for <dnsop@ietfa.amsl.com>; Tue, 3 Nov 2015 21:03:46 -0800 (PST)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B41451ACCE7 for <dnsop@ietf.org>; Tue, 3 Nov 2015 21:03:46 -0800 (PST)
Received: from s20010c4000003024c68e8ffffef564bd.v6.meeting.ietf94.jp ([2001:c40:0:3024:c68e:8fff:fef5:64bd] helo=pallas.home.time-travellers.org) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1ZtqEX-0003BW-BT for dnsop@ietf.org; Wed, 04 Nov 2015 05:03:41 +0000
Date: Wed, 04 Nov 2015 14:03:31 +0900
From: Shane Kerr <shane@time-travellers.org>
To: dnsop@ietf.org
Message-ID: <20151104140331.16463c3f@pallas.home.time-travellers.org>
X-Mailer: Claws Mail 3.13.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/jvoEsimKghPOc-7eJLhOp9qOdjE>
Subject: [DNSOP] Soon-to-come DNS over HTTP drafts
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2015 05:03:48 -0000


At BII we have been working on a couple of drafts that might be of
interest to the dnsop working group. We are happy to work them through
as independent submissions, but if there is interest in the working
group then we are also happy to do the work here.

Sorry we don't have the drafts submitted yet. :( But here is a rough
idea about them.

We have one document that is a kind of survey document of DNS over
HTTP. We go through the whole taxonomy of DNS over HTTP, starting from
DNS just using port 80 instead of port 53, through various levels of
encapsulation, and finally ending up with REST-style API's at the very

The other document describes our specific implementation, which sits
kind of in the middle of the the previous document, using DNS packets
sent in wire format via application/octet-stream. While of less general
interest, probably this is more important to standardize for
interoperability reasons.

Anyway, I am sure the quality of any resulting RFCs will be higher if
the working group adopts them, but I this is not super important in
either case. We are happy either way. :)