Re: [dnsext] Re: I-D ACTION:draft-vandergaast-edns-client-ip-00.txt

Ondřej Surý <ondrej.sury@nic.cz> Mon, 01 February 2010 14:37 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF7AF3A6959; Mon, 1 Feb 2010 06:37:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.699
X-Spam-Level:
X-Spam-Status: No, score=-105.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_23=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pvdN8S-N2NJW; Mon, 1 Feb 2010 06:36:59 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62]) by core3.amsl.com (Postfix) with ESMTP id D52963A6952; Mon, 1 Feb 2010 06:36:59 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1NbxDJ-0006iE-99 for namedroppers-data0@psg.com; Mon, 01 Feb 2010 14:25:17 +0000
Received: from [2001:1488:800:400::400] (helo=mail.nic.cz) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <ondrej.sury@nic.cz>) id 1NbxDG-0006he-IV for namedroppers@ops.ietf.org; Mon, 01 Feb 2010 14:25:15 +0000
Received: from [IPv6:2001:1488:ac14:1400:224:e8ff:fea9:f617] (unknown [IPv6:2001:1488:ac14:1400:224:e8ff:fea9:f617]) by mail.nic.cz (Postfix) with ESMTPSA id 9E05D76C026 for <namedroppers@ops.ietf.org>; Mon, 1 Feb 2010 15:25:05 +0100 (CET)
Message-ID: <4B66E441.6090104@nic.cz>
Date: Mon, 01 Feb 2010 15:25:05 +0100
From: Ondřej Surý <ondrej.sury@nic.cz>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1
MIME-Version: 1.0
To: namedroppers@ops.ietf.org
Subject: Re: [dnsext] Re: I-D ACTION:draft-vandergaast-edns-client-ip-00.txt
References: <7c31c8cc1001271556w4918093er6e94e07cb92c4dc4@mail.gmail.com>
In-Reply-To: <7c31c8cc1001271556w4918093er6e94e07cb92c4dc4@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

I am replying to several mails at once, since some of them address my 
concerns after reading whole draft.

On 28.1.2010 00:56, Wilmer van der Gaast wrote:
> Hello everyone,
>
> I spoke to Olafur about this idea in Hiroshima last year. I'm afraid
> the deadline for Anaheim already passed, but we hope we can discuss it
> on-line in the meantime and decide if it should become a WG item in
> Maastricht later this year.
>
> To summarize the I-D: It specifies an EDNS0 option that carries IP
> address information (by default only the first 24 bits to preserve
> privacy) of the user that triggered a DNS resolution. This should
> allow authoritative nameservers that give geo-targeted responses to be
> more accurate, even in cases where the resolver and its users aren't
> close to each other. To preserve the ability to cache such responses
> efficiently, the option in the response can indicate which exact
> subnet it should be cached for.
>
> Comments are more than welcome.

#1: There should be a way how to ask recursive resolver if he has set 
edns-client-ip on query or not, so end client knows if authoritative 
server knows his IP or not. (let's call it stalk flag)


On 28.1.2010 20:02, Nicholas Weaver wrote:
 >> it's not worth a global upgrade to DNS in its current form.
 >
 > It can be done WITHOUT a global upgrade: you can do it with JUST
 > upgrades to the recursive resolvers and authorities desiring such
 > behavior, see my note on fallbacks from the resolver point of view.

No you can't.  Since all end users would loose privacy from day zero, 
since this proposal is opt-out, not opt-in.  Therefore you need to do a 
global upgrade.

On 29.1.2010 12:32, Stephane Bortzmeyer wrote:
 > 2) A more ambitious one (may be too ambitious), to have an EDNS option
 > code "Client info", with sub-codes and various fields (and a registry
 > at IANA to register these fields) to carry absolutely everything from
 > the desktop client to the authoritative name server. IP address
 > information would then be just a special case.

I like this proposal, you can then set country to CZ, or language to 
"cs" as opt-in (same as in the browser).  I would just hate if my 
resolver starts to send my IP address to authoritative DNS without 
asking me.

Ondrej
-- 
  Ondřej Surý
  vedoucí výzkumu/R&D manager
  -------------------------------------------
  CZ.NIC, z.s.p.o.    --    Laboratoře CZ.NIC
  Americka 23, 120 00 Praha 2, Czech Republic
  mailto:ondrej.sury@nic.cz    http://nic.cz/
  tel:+420.222745110       fax:+420.222745112
  -------------------------------------------