Re: [dnsext] afasterinternet.com trial and draft-vandergaast-edns-client-subnet-00

Ted Hardie <ted.ietf@gmail.com> Tue, 06 September 2011 17:38 UTC

Return-Path: <ted.ietf@gmail.com>
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 30F9921F8C7F for <dnsext@ietfa.amsl.com>; Tue, 6 Sep 2011 10:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 mWNtXbmUk8pE for <dnsext@ietfa.amsl.com>; Tue, 6 Sep 2011 10:38:48 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 62CE421F8C7A for <dnsext@ietf.org>; Tue, 6 Sep 2011 10:38:48 -0700 (PDT)
Received: by gyf3 with SMTP id 3so4688112gyf.31 for <dnsext@ietf.org>; Tue, 06 Sep 2011 10:40:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=7s9tHyI7WvESSswUR4liV5tbFFAJKnHKUodKohnDdK8=; b=A6tfM7gPrUbRogBrEKDgjjY3z4iDnvpGUDJYlkGizbEkPyibMw0CbVwy+D4HHYjEpA Xp/47s2O+weaRIe0Y4vMmtYAi1sX1+q9Dd1BAhA6XPieerfpwxBpGahxNen11rooen/l bi69kvs2oGf04h0EMkfz1Elw9AndjE/ThR484=
MIME-Version: 1.0
Received: by 10.236.179.103 with SMTP id g67mr8751156yhm.49.1315330834424; Tue, 06 Sep 2011 10:40:34 -0700 (PDT)
Received: by 10.236.110.174 with HTTP; Tue, 6 Sep 2011 10:40:34 -0700 (PDT)
In-Reply-To: <39736B7C-63B4-4C3F-B87F-92D05C7B88AA@icsi.berkeley.edu>
References: <20110830162134.GB84494@shinkuro.com> <CA+9kkMCih-NWxaxBRD+9LphZEb2k+ce8NkNBm6HHubJ1kDO9TQ@mail.gmail.com> <CAMbvoaKFvxqVR2GRYxF_WOctdM=0Pdw35vqKKtDyCePdN3VM8g@mail.gmail.com> <6.2.5.6.2.20110905114918.08670a18@resistor.net> <20110906072857.GA23307@merboo.mamista.net> <CA+9kkMCqp0gMFtVtW95SUYWKKqKZMihzRErkWu7Mcyi5y+K3TQ@mail.gmail.com> <39736B7C-63B4-4C3F-B87F-92D05C7B88AA@icsi.berkeley.edu>
Date: Tue, 06 Sep 2011 10:40:34 -0700
Message-ID: <CA+9kkMASFwpNW9J0-9mNkyt+-fgcqPXu4qDK37pQtuqPNHq3KQ@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Nicholas Weaver <nweaver@icsi.berkeley.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: dnsext@ietf.org
Subject: Re: [dnsext] afasterinternet.com trial and draft-vandergaast-edns-client-subnet-00
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>
X-List-Received-Date: Tue, 06 Sep 2011 17:38:49 -0000

On Tue, Sep 6, 2011 at 10:28 AM, Nicholas Weaver
<nweaver@icsi.berkeley.edu> wrote:
>
> On Sep 6, 2011, at 10:25 AM, Ted Hardie wrote:
(adding Marty's comment back in )
On Tue, Sep 6, 2011 at 12:28 AM, Martin Barry <marty@supine.com> wrote:
> $quoted_author = "SM" ;
>>
>> From Section 9.1 of draft-vandergaast-edns-client-subnet-00:
>>
>>   "Users who wish their full IP address to be hidden can include an
>>    edns-client-subnet option specifying the wildcard address 0.0.0.0/0"
>
>> Users who do not wish to provide a client identifier will have to
>> update their software to support this specification.
>
> Or they could just not use OpenDNS, Google DNS or any other 3rd party
> recursive DNS provider who enables edns-client-subnet.
>

>> Hi Marty,
>>
>> The current draft says:
>>
>>   In any case, the response from the resolver to the client MUST NOT
>>   contain the edns-client-subnet option if none was present in the
>>   client's original request.  If the original client request contained
>>   a valid edns-client-subnet option that was used during recursion, the
>>   Recursive Resolver MUST include the edns-client-subnet option from
>>   the Authoritative Nameserver response in the response to the client.
>>
>> Given that, how is the client to know whether the service they are using enables
>> edns-client-subnet?
>
> a)  Does it matter?
>
> b)  Do a query with EDNS0 client subnet and see what happens.
>

The upshot of this is that SM is right:  clients who do not wish to
provide a client
identifier will have to update their software to achieve this goal,
since they cannot
identify whether a service is using it without that update.

regards,

Ted Hardie

>