IETF Logo Mail Archive

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

Tony Finch <dot@dotat.at> Wed, 13 July 2016 09:59 UTC

Return-Path: <dot@dotat.at>
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 0337D12D75A for <dnsop@ietfa.amsl.com>; Wed, 13 Jul 2016 02:59:30 -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, SPF_HELO_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 P4Wd8fHGCKrB for <dnsop@ietfa.amsl.com>; Wed, 13 Jul 2016 02:59:26 -0700 (PDT)
Received: from ppsw-30.csi.cam.ac.uk (ppsw-30.csi.cam.ac.uk [131.111.8.130]) (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 9A12212D735 for <dnsop@ietf.org>; Wed, 13 Jul 2016 02:59:25 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:34280) by ppsw-30.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1bNGwq-0011dY-fW (Exim 4.86_36-e07b163) (return-path <dot@dotat.at>); Wed, 13 Jul 2016 10:59:20 +0100
Date: Wed, 13 Jul 2016 10:59:20 +0100
From: Tony Finch <dot@dotat.at>
To: Shane Kerr <shane@time-travellers.org>
In-Reply-To: <20160712221041.783a2b04@pallas.home.time-travellers.org>
Message-ID: <alpine.DEB.2.11.1607131058310.8225@grey.csi.cam.ac.uk>
References: <e5c97630-a11f-0c93-8f4b-482764c85f71@gmail.com> <20160711235005.29302.qmail@ary.lan> <20160712221041.783a2b04@pallas.home.time-travellers.org>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wiaa-0qTE2g745-T8GgihUp5HzU>
Cc: dnsop@ietf.org, John Levine <johnl@taugh.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: Wed, 13 Jul 2016 09:59:30 -0000

Shane Kerr <shane@time-travellers.org> wrote:
>
> OTOH, I am (obviously) not a web developer, so perhaps I overestimate
> the difficulty in working with DNS binary-format. Maybe it's a
> relatively compact set of JavaScript functions that can be used?

It wouldn't be completely horrible to parse DNS packets using JavaScript
typed arrays.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Typed_arrays

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Humber, Thames: Variable mainly northwesterly 3 or 4, increasing 5 at times.
Slight, occasionally moderate. Showers. Good.

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