IETF Logo Mail Archive

Re: [DNSOP] JavaScript use case for DNS-over-HTTP (was Call for Adoption: draft-song-dns-wireformat-http)

"John Levine" <johnl@taugh.com> Thu, 14 July 2016 01:53 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0AFB12D6A8 for <dnsop@ietfa.amsl.com>; Wed, 13 Jul 2016 18:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 IobCySYdNjwe for <dnsop@ietfa.amsl.com>; Wed, 13 Jul 2016 18:53:36 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42F7712D0FA for <dnsop@ietf.org>; Wed, 13 Jul 2016 18:53:36 -0700 (PDT)
Received: (qmail 17179 invoked from network); 14 Jul 2016 01:53:34 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 14 Jul 2016 01:53:34 -0000
Date: Thu, 14 Jul 2016 01:53:12 -0000
Message-ID: <20160714015312.38023.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <CAL9jLaaD1_MBFeevUc9djteRWwMG69_wyU=0zOzCPTcEqa3JeQ@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZGecGG0DCSP1xJ1YjGNU5mtLQ1c>
Cc: morrowc.lists@gmail.com
Subject: Re: [DNSOP] JavaScript use case for DNS-over-HTTP (was Call for Adoption: draft-song-dns-wireformat-http)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 14 Jul 2016 01:53:38 -0000

>> why all that complexity? if some remote device (iot thingy) wants 'dns over
>>> http' why would it not (as a first order answer) just ask
>>> /cgi-bin/dnslookup for 'srv:foo.com' ? (returned answer in txt, json,
>>> etc...)

>> Security in IoT is close to an oxymoron, but my device would like to check
>> the signature before trusting what your proxy says.
>>
>ok, I'm sure your device has some agreement with the cooperating http(s)
>server though, right? it can get the text / bas64 rrsig content just as
>easily as if it were doing udp/dns. (it should probably also check ssl
>certificates/etc to make sure traffic did not get wonked in flight)

I don't understand what problem this solves.  If you're going to
provide all of the DNS results in a gooped up form, why not just
provide them in a native form and let the client deal with it?

R's,
John

v2.37.1 | Report a Bug | By Email | System Status