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

Joe Abley <jabley@hopcount.ca> Fri, 29 January 2010 00:56 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 2C8283A67A5; Thu, 28 Jan 2010 16:56:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 IFIzrZ+SZG9U; Thu, 28 Jan 2010 16:56:15 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62]) by core3.amsl.com (Postfix) with ESMTP id 804543A6407; Thu, 28 Jan 2010 16:56:15 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1Naf3S-000NsF-1U for namedroppers-data0@psg.com; Fri, 29 Jan 2010 00:49:46 +0000
Received: from [2001:4900:1:392:213:20ff:fe1b:3bfe] (helo=monster.hopcount.ca) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1Naf3P-000Nrm-MG for namedroppers@ops.ietf.org; Fri, 29 Jan 2010 00:49:43 +0000
Received: from [114.134.0.21] (helo=[10.30.157.227]) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1Naf3G-000JVk-LR; Fri, 29 Jan 2010 00:49:40 +0000
Subject: Re: [dnsext] Re: I-D ACTION:draft-vandergaast-edns-client-ip-00.txt
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <7c31c8cc1001271556w4918093er6e94e07cb92c4dc4@mail.gmail.com>
Date: Fri, 29 Jan 2010 13:49:30 +1300
Cc: namedroppers@ops.ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB12CD2F-7371-4A45-9FF1-322ABAE84418@hopcount.ca>
References: <7c31c8cc1001271556w4918093er6e94e07cb92c4dc4@mail.gmail.com>
To: Wilmer van der Gaast <wilmer@google.com>
X-Mailer: Apple Mail (2.1077)
X-SA-Exim-Connect-IP: 114.134.0.21
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
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/>

On 2010-01-28, at 12:56, Wilmer van der Gaast wrote:

> 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.

My initial reading of the proposal suggests that the client that originates the DNS request is the one that MAY populate a client-address option, and that any other resolver or proxy in the chain between the client and a server (cache or authority) which supplies an answer MAY NOT change the client-address option data.

Suppose most clients are numbered using RFC 1918 addresses behind a NAT, and have no trivial way of discovering a non-RFC1918 address that the world might see them as. In that case isn't the address information that ultimately arrives at cache or authority nameservers useless for any purpose other than identifying that RFC 1918 addresses are in use?

I have some suggestions that relate specifically to the text, but the general utility of the proposal seems limited to me: I have doubts that there are significant client populations in 2010 which have useful address information to send.


Joe