IETF Logo Mail Archive

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

Christopher Morrow <morrowc.lists@gmail.com> Wed, 13 July 2016 21:27 UTC

Return-Path: <christopher.morrow@gmail.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 39B8F12D93C for <dnsop@ietfa.amsl.com>; Wed, 13 Jul 2016 14:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 eMaZYaUAzWGr for <dnsop@ietfa.amsl.com>; Wed, 13 Jul 2016 14:27:42 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 9D86712D93B for <dnsop@ietf.org>; Wed, 13 Jul 2016 14:27:36 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id s63so56566051qkb.2 for <dnsop@ietf.org>; Wed, 13 Jul 2016 14:27:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=QWCFPk+vtfUGrzgnSMLufb98Qe4YkWFBduGmwXRQWPg=; b=zUqYGWu3R8EonadoZCaCbUNNFGi6HS+nYJQVVSabWvI9KB6E8suAwezKeg57zLPobB mXTV2TH+qHHLWKx2qGyBPeZiYy9jhmD9X/yC0ASBydaftg89M6AzzX3G5Rn9vBRkGVjs xCJ172ykImtFZkgln8bAuMJoI2XVo3KAhQ3XKFMtOPzeijr8J/7r4cI1o/P6Tt7ODr2b Q4vhB9zY0nMBpRKDTcKXfArUYrwIHnWxVfkrGs2gDZPjkRVdeuzAmhrJ+iYPyvkDHS8j kaRVqSYDn4VTohuACzeu61BSlHJqefjB+1ZcRCia7JJ2hLuwYRp0p8Kz/qyOFkPfZzam vG5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=QWCFPk+vtfUGrzgnSMLufb98Qe4YkWFBduGmwXRQWPg=; b=lwx0+2PAM+BM2TonCVGl8MWI/Wh/9Kg5UFF2hM8vPvEXN9kzOQv1CaB/dqwc3Ww8mz xBisnGfxqXjRhNPCIW4nJOhWlkLLagF4PaSYkoUuqFedYL8+azaUNfxnikuzOqM0szeh mWGFtVXBnKThCjt3DBGnWWoQFvrWk6AnhZxZNRE0U2UQNhfVfdRhr7UUpg1nx/UuuB78 i9BblP1nV+Mvnt7z0SqCX3Y/qyJbMUsl4OwGBbfVCmJz2//3wKNO2mASW1Xb7cRoUH3n A4kEBHournOVXhT4x9zupJppzBrqSCGnFgBrSVEYj3BpvKvCW6IfZJlYjCewM7nU1vPO jCPw==
X-Gm-Message-State: ALyK8tLFTh9cB5j40c7hpxZa2g1EqRtNUbGdJUcPyXKB4kJv+tkgx+jP7/jLfQe6/nDCvfVZ22/BR0z4G8AfrQ==
X-Received: by 10.55.15.27 with SMTP id z27mr13222892qkg.58.1468445255770; Wed, 13 Jul 2016 14:27:35 -0700 (PDT)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.85.116 with HTTP; Wed, 13 Jul 2016 14:27:35 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.11.1607131038580.59935@ary.lan>
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> <alpine.OSX.2.11.1607131038580.59935@ary.lan>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Wed, 13 Jul 2016 22:27:35 +0100
X-Google-Sender-Auth: boj3u9mITtpUWqgSAoRs1EEkclo
Message-ID: <CAL9jLaaD1_MBFeevUc9djteRWwMG69_wyU=0zOzCPTcEqa3JeQ@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary="001a11475b5cd7a96a05378b0d3d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0rh1nR3W_w-IAwLdGZ7yfdbFBnU>
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 21:27:44 -0000

On Wed, Jul 13, 2016 at 3:42 PM, John R Levine <johnl@taugh.com> wrote:

> 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.
>
>
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)

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