IETF Logo Mail Archive

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

Wilmer van der Gaast <wilmer@google.com> Tue, 02 February 2010 19:10 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 81A453A6833; Tue, 2 Feb 2010 11:10:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.506
X-Spam-Level:
X-Spam-Status: No, score=-105.506 tagged_above=-999 required=5 tests=[AWL=0.471, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 W4NNflOivmD6; Tue, 2 Feb 2010 11:10:00 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62]) by core3.amsl.com (Postfix) with ESMTP id C6DC93A67B4; Tue, 2 Feb 2010 11:10:00 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1NcO1T-000Fc3-8j for namedroppers-data0@psg.com; Tue, 02 Feb 2010 19:02:51 +0000
Received: from [216.239.33.17] (helo=smtp-out.google.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <wilmer@google.com>) id 1NcO1O-000Faq-WE for namedroppers@ops.ietf.org; Tue, 02 Feb 2010 19:02:49 +0000
Received: from kpbe18.cbf.corp.google.com (kpbe18.cbf.corp.google.com [172.25.105.82]) by smtp-out.google.com with ESMTP id o12J2il4029890 for <namedroppers@ops.ietf.org>; Tue, 2 Feb 2010 19:02:44 GMT
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1265137365; bh=78JFnHusZRQhyzqfK1GvTX6z40g=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=QtPXba1HwkynNaSoO+9IXUBC+MXw3FbTeDgcmFAuegh9mbpqa8bor/PSnhtr/SSea KeTfd61j+NVpKcxOt5yHQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=AWnVJEv2WcP89Ec4Mu/iMvFZ8eXNejsYJVXDAL4hzYGSpZUGxNX3veYgH4bz4n3lk DbeVQP7vhUvgv095Ju2zw==
Received: from bwz23 (bwz23.prod.google.com [10.188.26.23]) by kpbe18.cbf.corp.google.com with ESMTP id o12J2gpY013690 for <namedroppers@ops.ietf.org>; Tue, 2 Feb 2010 11:02:43 -0800
Received: by bwz23 with SMTP id 23so368201bwz.1 for <namedroppers@ops.ietf.org>; Tue, 02 Feb 2010 11:02:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.204.140.25 with SMTP id g25mr3811828bku.197.1265137362153; Tue, 02 Feb 2010 11:02:42 -0800 (PST)
In-Reply-To: <d791b8791002021046i5049c50anb74273eb0e45b984@mail.gmail.com>
References: <7c31c8cc1001271556w4918093er6e94e07cb92c4dc4@mail.gmail.com> <6e04e83a1002011109u1cd55c99k8b584648184cdc73@mail.gmail.com> <162E0DB1-EC86-4206-AB36-6FEFA786B24C@ICSI.Berkeley.EDU> <6e04e83a1002011402u395f599g74180d28fdbe5707@mail.gmail.com> <939BB577-FDBE-4573-9129-8CA29B0FB493@sackheads.org> <7B06A582-38E3-4387-BA16-932825A4A62B@rfc1035.com> <F2E927AA-B07C-45D0-9D26-AFE8115F2CC2@icsi.berkeley.edu> <B7A5F1C5-E972-4915-A90F-E561B041A133@rfc1035.com> <23AAB144-AF85-45C7-A99C-C1E7A5334F9C@ICSI.Berkeley.EDU> <d791b8791002021046i5049c50anb74273eb0e45b984@mail.gmail.com>
Date: Tue, 02 Feb 2010 19:02:42 +0000
Message-ID: <7c31c8cc1002021102t66b3100bw8ea4a22638f87df8@mail.gmail.com>
Subject: Re: [dnsext] draft-vandergaast-edns-client-ip-00.txt
From: Wilmer van der Gaast <wilmer@google.com>
To: Matthew Dempsky <matthew@dempsky.org>
Cc: Nicholas Weaver <nweaver@icsi.berkeley.edu>, namedroppers@ops.ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
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 2 February 2010 18:46, Matthew Dempsky <matthew@dempsky.org> wrote:
>
> I don't understand RFC 2671 5.3 as requiring a server to reply with
> one of those codes (otherwise it would have made more sense to specify
> which one).  Instead, I read it as a warning/reminder to the reader
> that a server might not gracefully handle new extensions, and clients
> should be prepared to deal with that possibility when making use of
> them.
>
+1

Just out of curiosity I did a few test queries to my own server
running BIND, to OpenDNS, Google Public DNS, and amazon.com and
microsoft.com nameservers. They all ignore the option, except the
last: From what I can see this is done by their Netscalers though, not
their nameservers. (dig . ns @65.55.37.62  shows a very typical
response that I've only seen from Netscalers so far)


Wilmer.

-- 
Wilmer van der Gaast, Dublin Traffic SRE.
Google Ireland.

v2.23.0 | Report a Bug | By Email