Re: [DNSOP] Soon-to-come DNS over HTTP drafts
"jewforice ." <jewforice@gmail.com> Wed, 04 November 2015 05:30 UTC
Return-Path: <jewforice@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED4D61ACD4E for <dnsop@ietfa.amsl.com>; Tue, 3 Nov 2015 21:30:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 dOoTXks6ySIK for <dnsop@ietfa.amsl.com>; Tue, 3 Nov 2015 21:30:09 -0800 (PST)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (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 82ACE1ACD56 for <dnsop@ietf.org>; Tue, 3 Nov 2015 21:30:00 -0800 (PST)
Received: by wicll6 with SMTP id ll6so24861553wic.1 for <dnsop@ietf.org>; Tue, 03 Nov 2015 21:29:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pOll+r2ZIaCmcnLjc1kVgyE0jQogMx7axRDv6pqtLwo=; b=ywK5Qrz4sTeJBTqQp8I0Kq05DffrWN5/tIscpyNTGw4MDndSuORXByqwEiz1YCpP3U C100IKSkKEyOzqg6xTIFfYg+B0qf7NGoKiGFoqn6jvZs6NPuqBLA+rKLEzEFUWCb5Dz3 yHL+VtSafCRcoNOJXIgVcdNJ3gzzkidYGEKKJ0cvhdQI2PnMAY/lfb/yrOMH45dnUVqv LGMWjehzydyjVHJebILWiICCFltdglMpPsMB8Pp+dccn5pGnZPXRlCerLfT5mr9+sWDy e/dV0nHwxJLq/5bSUBH7ySwFNnJbaSStBN4pV9dfPVdpbMEJyVIudYGfLWpmLBGwV/Km 9zKg==
MIME-Version: 1.0
X-Received: by 10.194.157.9 with SMTP id wi9mr32963467wjb.154.1446614998925; Tue, 03 Nov 2015 21:29:58 -0800 (PST)
Received: by 10.194.221.33 with HTTP; Tue, 3 Nov 2015 21:29:58 -0800 (PST)
In-Reply-To: <CAKr6gn2_r-HmU++Q95AA38zcGX4pf15yp665zi-TyT_C85kMrA@mail.gmail.com>
References: <20151104140331.16463c3f@pallas.home.time-travellers.org> <CAKr6gn2_r-HmU++Q95AA38zcGX4pf15yp665zi-TyT_C85kMrA@mail.gmail.com>
Date: Wed, 04 Nov 2015 13:29:58 +0800
Message-ID: <CAB3ZD+krmurk3p=xnBnNpi+GWz+-gt2AKwqdxzaz4NuFhiysDA@mail.gmail.com>
From: "jewforice ." <jewforice@gmail.com>
To: George Michaelson <ggm@algebras.org>
Content-Type: multipart/alternative; boundary="089e013c622e234a720523b04d14"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/1Hjw5xjPvCeTjV-xvl9RYJue904>
Cc: Shane Kerr <shane@time-travellers.org>, dnsop WG <dnsop@ietf.org>
Subject: Re: [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:30:11 -0000
Hi Shane We've been using our implementation of DNS over HTTP for about 2 years ( Of course not in RESTFUL style, just some rough plain text format ). So I strongly support working on this draft to help standardize this kind of DNS service. On Wed, Nov 4, 2015 at 1:08 PM, George Michaelson <ggm@algebras.org> wrote: > \o/ > > -G > > On Wed, Nov 4, 2015 at 2:03 PM, Shane Kerr <shane@time-travellers.org> > wrote: > >> All, >> >> 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 >> end. >> >> 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. :) >> >> Cheers, >> >> -- >> Shane >> >> _______________________________________________ >> DNSOP mailing list >> DNSOP@ietf.org >> https://www.ietf.org/mailman/listinfo/dnsop >> > > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop > >
- [DNSOP] Soon-to-come DNS over HTTP drafts Shane Kerr
- Re: [DNSOP] Soon-to-come DNS over HTTP drafts George Michaelson
- Re: [DNSOP] Soon-to-come DNS over HTTP drafts jewforice .
- Re: [DNSOP] Soon-to-come DNS over HTTP drafts Robert Edmonds