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

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 28 January 2010 16:47 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 CDA0928C0F2; Thu, 28 Jan 2010 08:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.34
X-Spam-Level:
X-Spam-Status: No, score=-106.34 tagged_above=-999 required=5 tests=[AWL=0.259, BAYES_00=-2.599, 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 9UJxPrRJkih4; Thu, 28 Jan 2010 08:47:21 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62]) by core3.amsl.com (Postfix) with ESMTP id 1344A28C0E9; Thu, 28 Jan 2010 08:47:21 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1NaXRL-000Hcq-TV for namedroppers-data0@psg.com; Thu, 28 Jan 2010 16:41:55 +0000
Received: from [192.245.12.227] (helo=balder-227.proper.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <paul.hoffman@vpnc.org>) id 1NaXRF-000Hah-R8 for namedroppers@ops.ietf.org; Thu, 28 Jan 2010 16:41:49 +0000
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o0SGfZLg085835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jan 2010 09:41:36 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624086ac7876ddb5b35@[10.20.30.158]>
In-Reply-To: <48894.1264695230@nsa.vix.com>
References: <7c31c8cc1001271556w4918093er6e94e07cb92c4dc4@mail.gmail.com> <6184.1264657589@nsa.vix.com> <4966825a1001280807i768a33ccs98f809366bce33d8@mail.gmail.com> <48894.1264695230@nsa.vix.com>
Date: Thu, 28 Jan 2010 08:41:17 -0800
To: Paul Vixie <vixie@isc.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [dnsext] Re: I-D ACTION:draft-vandergaast-edns-client-ip-00.txt
Cc: namedroppers@ops.ietf.org
Content-Type: text/plain; charset="us-ascii"
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/>

At 4:13 PM +0000 1/28/10, Paul Vixie wrote:
> > From: Carlo Contavalli <ccontavalli@google.com>
>> Date: Thu, 28 Jan 2010 16:07:05 +0000
>>
>> On Thu, Jan 28, 2010 at 5:46 AM, Paul Vixie <vixie@isc.org> wrote:
>> > if we're going to add client identity to the query, can we do so in a more
>> > general way?  i'd like to know lat-long, country, isp, language, and
>> > adult/child.  and the ip address should be multiprotocol, covering
>> > ipv6.
>
>> The doc does cover ipv6, and allows for other protocols to be supported,
>> if necessary.
>
>great.
>
>> Rather than adding client identity, what we're trying to do is address
>> a concrete problem that affects CDNs, open resolvers, and many large
>> sites, that for whatever reason, use the source ip of the query to
>> determine which reply to return to the user.
>
>i don't think that's a general enough solution to be worth standardizing.
>please investigate the larger context of client identity, beyond the needs
>of CDN's.

OK, I'll bite. I thought your first message was you using your dry humor voice; now it seems like you really meant it.

What technical problem would identifying the lat-long of the requester solve? I'm not asking "is there someone who would want to collect this information for later marketing purposes"; I'm asking what technical problem would knowing that information solve.

Ditto for the other things you listed, of course, but they seemed less likely (to me) to have an answer to the question.

--Paul Hoffman, Director
--VPN Consortium