IETF Logo Mail Archive

Re: [dnsext] draft-mohan-dns-query-xml-00.txt

Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Sat, 01 October 2011 18:22 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 995CE21F91D2; Sat, 1 Oct 2011 11:22:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1317493349; bh=xC32dRnYM/U58FzULiBqzwS4CmNNoL9miYE2DVQtMo8=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=d9bf9SsHJ2q10P4pzmF7IrnjOc4fUP1Wtq+mMY0B7HKCTDN+fZpE4ngDcWOj0LR9J BAFiKuPJaIGcVntt8tBxgHHmg8Y95NLRqWfCatekixPAn6dfSIVhv4v3NbhppKjQfG 4xcUt6/jda7OrHr1ubE/JstfILeesAFE0rT/f3X0=
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 024EF21F91D2 for <dnsext@ietfa.amsl.com>; Sat, 1 Oct 2011 11:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.209
X-Spam-Level:
X-Spam-Status: No, score=-2.209 tagged_above=-999 required=5 tests=[AWL=-0.210, BAYES_00=-2.599, J_CHICKENPOX_14=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3igWOeRbLo86 for <dnsext@ietfa.amsl.com>; Sat, 1 Oct 2011 11:22:28 -0700 (PDT)
Received: from rock.ICSI.Berkeley.EDU (rock.ICSI.Berkeley.EDU [192.150.186.19]) by ietfa.amsl.com (Postfix) with ESMTP id 21FC521F91CA for <dnsext@ietf.org>; Sat, 1 Oct 2011 11:22:28 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id A8A382C4015; Sat, 1 Oct 2011 11:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ICSI.Berkeley.EDU
Received: from rock.ICSI.Berkeley.EDU ([127.0.0.1]) by localhost (maihub.ICSI.Berkeley.EDU [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5Ww8qHS+gck6; Sat, 1 Oct 2011 11:25:24 -0700 (PDT)
Received: from [10.0.1.2] (c-76-103-166-40.hsd1.ca.comcast.net [76.103.166.40]) (Authenticated sender: nweaver) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id 4313F2C4002; Sat, 1 Oct 2011 11:25:24 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
In-Reply-To: <5C4E07BC-E6CC-45A6-8018-10C2A799A55E@vpnc.org>
Date: Sat, 1 Oct 2011 11:25:22 -0700
Message-Id: <66077D12-F568-426A-8E5C-CC077CC24622@ICSI.Berkeley.EDU>
References: <CACU5sDnBx5AijEgFXKNPjtcVdtBnBJamsn-f_ye0Jm3TQq0mvw@mail.gmail.com> <0394FB3B-6C2B-4D47-B1FA-AA54B7EB1053@kirei.se> <DDD7529C-9EF3-427F-AF90-2872CCD71ECF@cisco.com> <201110010458.26859.vixie@isc.org> <D3890C96-DA07-4BA1-AB57-1A81EA2ED477@icsi.berkeley.edu> <5C4E07BC-E6CC-45A6-8018-10C2A799A55E@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1244.3)
Cc: DNSEXT Working Group <dnsext@ietf.org>
Subject: Re: [dnsext] draft-mohan-dns-query-xml-00.txt
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

On Oct 1, 2011, at 8:25 AM, Paul Hoffman wrote:

> On Oct 1, 2011, at 8:01 AM, Nicholas Weaver wrote:
> 
>> Web caches don't work.  
> 
> +1.
> 
>> In our experience, nearly 50% of those in Netalyzr tests cache things they shouldn't, so if the worry is cache-staleness, include a cache-buster.
> 
> -.5. You are assuming that a bad HTTP cache will be bad in a predictable fashion. I'm not against using nonces to bust caches, but I don't think we should rely on it.

No, what I'm assuming is SOME minimal-level of nonborkenness.

IF a cache takes url 

http://www.example.com/url_a

and instead returns

http://www.example.com/url_b

Its going to be so b0rken for everything that HTTP will be nonusable.


Thus making the URLs like

http://www.dnsresolver.com/name/rtype/NONCEA.json

will be noncached, because if it instead returns the results of a previous fetch

http://www.dnsresolver.com/name/rtype/NONCEB.json

the cache will be not subtly broken, but so broken-as-to-uselessness.


THats the other reason for json:  If the middlebox is content aware, JSON is one thing that will be let through because block application/json these days you might as well block the web altogether.

So encoded as JSON, transfered as mimetype application/json, is most likely to get through.

_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext

v2.8.7 | Report a Bug | By Email