IETF Logo Mail Archive

Re: [dnsoverhttp] New draft: draft-hoffman-dns-over-http-00.txt

Patrick McManus <pmcmanus@mozilla.com> Thu, 22 September 2016 16:29 UTC

Return-Path: <pmcmanus@mozilla.com>
X-Original-To: dnsoverhttp@ietfa.amsl.com
Delivered-To: dnsoverhttp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6385D12BAEA for <dnsoverhttp@ietfa.amsl.com>; Thu, 22 Sep 2016 09:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 uf2w_aQlxQIX for <dnsoverhttp@ietfa.amsl.com>; Thu, 22 Sep 2016 09:29:25 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id 3F78412C059 for <dnsoverhttp@ietf.org>; Thu, 22 Sep 2016 09:29:03 -0700 (PDT)
Received: from mail-io0-f176.google.com (mail-io0-f176.google.com [209.85.223.176]) by linode64.ducksong.com (Postfix) with ESMTPSA id D2BB63A084 for <dnsoverhttp@ietf.org>; Thu, 22 Sep 2016 12:29:02 -0400 (EDT)
Received: by mail-io0-f176.google.com with SMTP id m186so91137084ioa.2 for <dnsoverhttp@ietf.org>; Thu, 22 Sep 2016 09:29:02 -0700 (PDT)
X-Gm-Message-State: AA6/9RmRQkcNxYCoEMnlGIvRge2lMkE69ndQTLGMRElaXHf3ybnsI7vojluAAXJ3JlsayF3cosnjfalxQtwkjA==
X-Received: by 10.107.185.3 with SMTP id j3mr4018849iof.3.1474561742327; Thu, 22 Sep 2016 09:29:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.148.50 with HTTP; Thu, 22 Sep 2016 09:29:01 -0700 (PDT)
In-Reply-To: <CABkgnnX3XBd588W5R1hK05-t9QFL0uetzVoNige0KoyiuoO69A@mail.gmail.com>
References: <147438228195.28999.4355943522486567954.idtracker@ietfa.amsl.com> <D1E3CC44-FE5A-4ACE-90A1-EF9B5EE975D7@icann.org> <CAOdDvNpWdN=w0R7pOkghbwg0-SwHnD9=AqvpnAM7tQfmRpVGEw@mail.gmail.com> <A7C77948-ACEA-49F1-83CC-72E12B6EFA2B@icann.org> <CABkgnnX3XBd588W5R1hK05-t9QFL0uetzVoNige0KoyiuoO69A@mail.gmail.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Thu, 22 Sep 2016 18:29:01 +0200
X-Gmail-Original-Message-ID: <CAOdDvNrpsYXwuBFwTOSmLo_2OMETJiQgF4oDE4TWEG92grq6oA@mail.gmail.com>
Message-ID: <CAOdDvNrpsYXwuBFwTOSmLo_2OMETJiQgF4oDE4TWEG92grq6oA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c071c30d9d5cd053d1b2863
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsoverhttp/5WjM2PZKUMg55XYdCswoAd8Izsg>
Cc: "dnsoverhttp@ietf.org" <dnsoverhttp@ietf.org>, Paul Hoffman <paul.hoffman@icann.org>, Patrick McManus <pmcmanus@mozilla.com>
Subject: Re: [dnsoverhttp] New draft: draft-hoffman-dns-over-http-00.txt
X-BeenThere: dnsoverhttp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of DNS over HTTP <dnsoverhttp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsoverhttp>, <mailto:dnsoverhttp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsoverhttp/>
List-Post: <mailto:dnsoverhttp@ietf.org>
List-Help: <mailto:dnsoverhttp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsoverhttp>, <mailto:dnsoverhttp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Sep 2016 16:29:27 -0000

On Thu, Sep 22, 2016 at 3:19 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 22 September 2016 at 01:24, Paul Hoffman <paul.hoffman@icann.org>
> wrote:
>
> The problem that I think Patrick is worried about is one where
> arbitrary content can make claims about DNS answers.
>

That's one small bit, but my focus is actually more prosaic.

unless you are pushing into a .wk that carries a semantic meaning, the
client really doesn't know what to do with this application/json-dns data.
Sure its DNS data but should it be used for resolutions? Maybe its part of
a file system backup, or the archive of a dataset from some uni project, or
whatever.. I think we need more info than "thiis is DNS info" to use it for
a resolution - and a path seems like the way to express that to me.

v2.8.7 | Report a Bug | By Email