Re: [dnsext] Uploaded: edns-client-subnet-00

Wilmer van der Gaast <wilmer@google.com> Thu, 17 February 2011 20:26 UTC

Return-Path: <wilmer@google.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 992623A6ABD for <dnsext@core3.amsl.com>; Thu, 17 Feb 2011 12:26:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[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 ihfh1U0PgwoP for <dnsext@core3.amsl.com>; Thu, 17 Feb 2011 12:26:14 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 7A06E3A6A00 for <dnsext@ietf.org>; Thu, 17 Feb 2011 12:26:13 -0800 (PST)
Received: from hpaq14.eem.corp.google.com (hpaq14.eem.corp.google.com [172.25.149.14]) by smtp-out.google.com with ESMTP id p1HKQiKG008373 for <dnsext@ietf.org>; Thu, 17 Feb 2011 12:26:45 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1297974405; bh=KDza7UZhQA1YRqm+4jzvckyAeD4=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=wgzUuS71OiiLHCjZ0R2fX+dxzxAbfWLyZzpZXWEuYDm3Lt9KhYtZGBI0ZrqzKzdWs WP9ekDxEglJ4dtlgQgxZg==
Received: from ewy6 (ewy6.prod.google.com [10.241.103.6]) by hpaq14.eem.corp.google.com with ESMTP id p1HKQESU022642 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <dnsext@ietf.org>; Thu, 17 Feb 2011 12:26:43 -0800
Received: by ewy6 with SMTP id 6so1197989ewy.12 for <dnsext@ietf.org>; Thu, 17 Feb 2011 12:26:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=cg2pdsOcSL/UiS6yGELISCZFb4++erhhcbIx1VC5Lak=; b=C3hSRwntwCDqGNAXiPBl64bbyTfXqgWDfiks3xfTM4hiK+KG8LbvsK46I3ZsJNY1Rt vJQCsAAABt3WfFaOBSpA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Rb5BI6B3FK3BonyFPBewOi+vt91iKlGuAXzwYM1qHQMsPqmLUEaiB9hAXPmfBBHfY1 YH2QD5+syJDtMScvP0Tg==
MIME-Version: 1.0
Received: by 10.213.3.20 with SMTP id 20mr2807176ebl.5.1297974400456; Thu, 17 Feb 2011 12:26:40 -0800 (PST)
Received: by 10.213.14.139 with HTTP; Thu, 17 Feb 2011 12:26:40 -0800 (PST)
In-Reply-To: <AANLkTi=f2ZATArwdhzkNKTu7AADQHsf0u6tCt4OkGaGS@mail.gmail.com>
References: <AANLkTi=f2ZATArwdhzkNKTu7AADQHsf0u6tCt4OkGaGS@mail.gmail.com>
Date: Thu, 17 Feb 2011 20:26:40 +0000
Message-ID: <AANLkTinyS-DV4RUF7PSYfGP0586w_sF-1QDx5dE0aSYs@mail.gmail.com>
From: Wilmer van der Gaast <wilmer@google.com>
To: dnsext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-System-Of-Record: true
Cc: edns-client-subnet@googlegroups.com
Subject: Re: [dnsext] Uploaded: edns-client-subnet-00
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 17 Feb 2011 20:26:15 -0000

On 9 February 2011 13:01, Wilmer van der Gaast <wilmer@google.com> wrote:
> Also, since the release of the last draft we have:
>
> * Added support for handling edns-client-subnet options to both our
> authoritative nameservers and Google Public DNS, using option code
> 0x50fa (not officially allocated and *not* to be used permanently).
> * Started a small-scale experiment of using edns-client-subnet in real
> life, to measure latency improvements and confirm that the idea is
> generally feasible. We're working with several third parties (CDNs but
> also resolvers) and are looking forward to hearing from anyone else
> interested in participating.
>
Addition to this:

* Wrote a patch against BIND's dig utility that adds a +client= flag
to send edns-client-subnet options, useful to test and debug
implementations. The patch can be downloaded from
http://wilmer.gaa.st/edns-client-subnet/.


Regards,

-- 
Wilmer van der Gaast, Traffic SRE/Google Public DNS team.
Google Ireland.