IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Wed, 13 July 2016 14:42 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 2137312D814 for <dnsop@ietfa.amsl.com>; Wed, 13 Jul 2016 07:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=PIlucnr9; dkim=pass (1536-bit key) header.d=taugh.com header.b=GRtqFKpB
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 2ZkrCv2pxfhK for <dnsop@ietfa.amsl.com>; Wed, 13 Jul 2016 07:42:11 -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 523D512D661 for <dnsop@ietf.org>; Wed, 13 Jul 2016 07:42:11 -0700 (PDT)
Received: (qmail 79019 invoked from network); 13 Jul 2016 14:42:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=134aa.57865342.k1607; bh=6Xy409if+Nbxezw2BhXcel2g4zTPb7ih2yQ5DjnzNjA=; b=PIlucnr9uMYvA9+WgF4NhufyZlKITaUa4Kp5thVwGpSV3K9g6pbV/B6K8E5zBqE5uQv7VTae89JMKKBABA48uPF72uj3Tq13tQUmbSxMLYmJrRBYeZD5VTQlJPYM2cMuDnDxSka+v7lHr40Rv+gvC9Iv629Bb1kw8nZJb/cje0QvR4RIgTpWe6r+tJ/fiXwsinCvRAtM5iNkQ2UDeDPtwinj29Ksym/Oj1RJBsvra5QoGg2e7CWYsuYC5wjE5PId
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=134aa.57865342.k1607; bh=6Xy409if+Nbxezw2BhXcel2g4zTPb7ih2yQ5DjnzNjA=; b=GRtqFKpBOOkKyQLaoVHrjrvvn4Xf16gvxxjpoziCSuV7iYNavVh+yBLc9RRxjnoQhNGMJhKFoHPl4LbhZb5U1m8x7ZySow4h+LkgEB4esJkeWSV/dvq8WyvL0LsUKB+0ZZxiWhkfedLRtJYF9hvBpotZTk3rnLMAPutLHCvKDVMlJ/0Npaj2lMewBiR+ieMtloSBfM/7tKTPGw+25hkcozd+bJovj/jX/WoOXErS5b9zFg01W5BYnjSZ2BjHZmiD
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 13 Jul 2016 14:42:09 -0000
Date: Wed, 13 Jul 2016 10:42:09 -0400
Message-ID: <alpine.OSX.2.11.1607131038580.59935@ary.lan>
From: John R Levine <johnl@taugh.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <CAL9jLaZ0Yc1bUzixccw7S1tP+21XCHoaqNPjvdeNQ2ERkqqe1A@mail.gmail.com>
References: <e5c97630-a11f-0c93-8f4b-482764c85f71@gmail.com> <20160711235005.29302.qmail@ary.lan> <20160712221041.783a2b04@pallas.home.time-travellers.org> <alpine.DEB.2.11.1607131058310.8225@grey.csi.cam.ac.uk> <CAL9jLaZ0Yc1bUzixccw7S1tP+21XCHoaqNPjvdeNQ2ERkqqe1A@mail.gmail.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tTbbIeh-H08EDMg3XOtbwFfCY9s>
Cc: dnsop <dnsop@ietf.org>
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: Wed, 13 Jul 2016 14:42:13 -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...)
>
> why bother with a bunch of javascript tomfoolery?

Security in IoT is close to an oxymoron, but my device would like to check 
the signature before trusting what your proxy says.

Also, as I mentioned in another message, unless you plan to carefully 
maintain your proxy to handle and translate every rrtype, we're going to 
want to use rr's that it doesn't handle.  I suppose it might return a json 
blob of TYPE1234, but you might as well just send the binary stuff at that 
point.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

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