IETF Logo Mail Archive

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

Nicholas Weaver <nweaver@icsi.berkeley.edu> Sun, 02 October 2011 00:06 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 CE78C21F8E22; Sat, 1 Oct 2011 17:06:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1317514001; bh=H427X4dVR2+zPlyBC4qxXFOM2snTztWRWzmHwqx5k64=; 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=CpqBbkFsGocqG5RuzCiuAsZBYwxvyZQ3rCwFBh5wdSxVeIh0elEyJJWfKNidcigeK jdYYEwHF8yT7nrUnOJM+SOhnXYXf4bX9+1W1dKt4g71s6RAh8iOnGHN40LKfAG3318 PxYDBoOSVR+BulhvA3isdZQqFkiPxsSUJEIWN+qE=
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 8DDE221F8E22 for <dnsext@ietfa.amsl.com>; Sat, 1 Oct 2011 17:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599]
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 Eorneguo5iHm for <dnsext@ietfa.amsl.com>; Sat, 1 Oct 2011 17:06:40 -0700 (PDT)
Received: from rock.ICSI.Berkeley.EDU (rock.ICSI.Berkeley.EDU [192.150.186.19]) by ietfa.amsl.com (Postfix) with ESMTP id F142021F8C18 for <dnsext@ietf.org>; Sat, 1 Oct 2011 17:06:39 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id D66982C4015; Sat, 1 Oct 2011 17:09:37 -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 pg6knNqDJlHx; Sat, 1 Oct 2011 17:09:37 -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 80F8A2C4002; Sat, 1 Oct 2011 17:09:37 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
From: Nicholas Weaver <nweaver@icsi.berkeley.edu>
In-Reply-To: <4E87A9C8.8090401@necom830.hpcl.titech.ac.jp>
Date: Sat, 1 Oct 2011 17:09:37 -0700
Message-Id: <6C66E591-5278-415B-A7A8-21AB824F2599@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> <4E87A9C8.8090401@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.1244.3)
Cc: 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 5:01 PM, Masataka Ohta wrote:
> And only for SDNS.
> 
> Maybe, google is considering to always use this transport with
> hardwired addresses of 8.8.8.8 and 8.8.4.4 even for plain DNS
> to get privacy information of clients from HTTP headers.

For google, the information they get from Public DNS is a poor source of data by Google's standards.


a)  Google's privacy policy is clear on what data they keep and discard from Public DNS.  http://code.google.com/speed/public-dns/privacy.html

Full IP logs are kept for 24-48 hours, after that, IP addresses are replaced with a network & city level GeoIP localization, which means it is very poor for user tracking.  Which is excellent for tracking aggregate information but fails completely for user tracking.


b)  Google +1 and Analytics capture much much much more information about what users are reading on the web.  The rumors (threats?) about +1 being used by the pagerank algorithm are particularly disturbing.


Rather, it appears Google Public DNS is about having a public DNS service where an NXDOMAIN remains an NXDOMAIN, since half of those NXDOMAINs from the browser result in a Google search anyway (the other half go to Bing), so there is little point in monetizing NXDOMAINs for Google.

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

v2.8.7 | Report a Bug | By Email