Re: [DNSOP] call for adoption: draft-vandergaast-dnsop-edns-client-subnet

Peter DeVries <peter@devries.tv> Fri, 13 February 2015 12:59 UTC

Return-Path: <peter@devries.tv>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CAF61A6F07 for <dnsop@ietfa.amsl.com>; Fri, 13 Feb 2015 04:59:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7SiBtIsVdjz for <dnsop@ietfa.amsl.com>; Fri, 13 Feb 2015 04:59:23 -0800 (PST)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C19211A6FFD for <dnsop@ietf.org>; Fri, 13 Feb 2015 04:59:18 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id hi2so11853716wib.0 for <dnsop@ietf.org>; Fri, 13 Feb 2015 04:59:17 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Vq95VbZ0uHklI6RnXRB9wraqgJZVRu65qzpJ441iSKk=; b=TxCU0dlIOgePa/D5jYS/mpeU1aoVVfp4BofUjH+fHQGyC0a7XslYbvdBF/nM1S2L7b 3ib5q5VGP/VCuiHGp4jLWP3uxRqg7x3D3tTLLauwAz6UTW0z7vzgHFTo5hG/ga+L2eZn zMvBDoZPGIwcL37IqvsccbMSMsEzwGwipKmQl3aR/eK3CLioS7JVbbYEApYTazciWmZT OMSZd/L3o20cwMx+LY6iRNV1buX3XgfYz6si4zgfz91CckYCQkslBDqMn0P1+9AM2slS AcHzet5/stVTdvbPF+YwUx+MG+kPkb/1owrr04Lrq5xovSbl+i8y2przBFj+EfZKcUjk LP9w==
X-Gm-Message-State: ALoCoQn48it6x4IgXlPeyOzFn7vGYsZF7L2m6gwjHRvh8fGPjz24qrpDTxshLcVAf9woypZ2tSMF
MIME-Version: 1.0
X-Received: by 10.180.211.206 with SMTP id ne14mr15594426wic.79.1423832357459; Fri, 13 Feb 2015 04:59:17 -0800 (PST)
Received: by 10.194.65.136 with HTTP; Fri, 13 Feb 2015 04:59:17 -0800 (PST)
In-Reply-To: <20150212065119.68256.qmail@f5-external.bushwire.net>
References: <629002B1-7A32-4A83-ACA1-0185F5355641@gmail.com> <20141224195229.4342.qmail@f5-external.bushwire.net> <20150212065119.68256.qmail@f5-external.bushwire.net>
Date: Fri, 13 Feb 2015 07:59:17 -0500
Message-ID: <CAJyJpgAPb7vykLpQVr9YMzT6aN_viGYBJxxsya_UQ_gixyrRaA@mail.gmail.com>
From: Peter DeVries <peter@devries.tv>
To: dnsop@ietf.org
Content-Type: multipart/alternative; boundary="001a11c37d44e2ef3e050ef7cdc0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/4D4wVkkXsBzjfEXMrUGV6UeDD5Y>
Subject: Re: [DNSOP] call for adoption: draft-vandergaast-dnsop-edns-client-subnet
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 12:59:26 -0000

My dayjob supports this as well and has been running resolvers with similar
functionality implemented for a while now.   We are looking to switch to
edns-clent-subnet once it is standardized and have been approached by
parties willing to invest in development.

Peter

On Thu, Feb 12, 2015 at 1:51 AM, Mark Delany <f4t@november.emu.st> wrote:

> On 24Dec14, Mark Delany allegedly wrote:
> > > The draft is available here:
> http://datatracker.ietf.org/doc/draft-vandergaast-dnsop-edns-client-subnet/
> >
> > a) 6.2 - Intent of SCOPE NETMASK
> >
> >   "In both cases, the value of the SCOPE NETMASK in the reply has strong
> >   implications with regard to how the reply will be cached"
> >
> > I wonder whether SCOPE NETMASK should have a bigger impact beyond how
> > the reply is cached?
>
> Tap tap tap. Is this thing turned on?
>
> I think 3-4 people made some well-considered feedback on this draft,
> but there has been zero discussion or author feedback for some six
> weeks now.
>
> Does that mean there is insufficient interest in progressing this draft?
>
> I ask because in my dayjob we've been recently approached by some
> large eyeball providers who are now willing to invest in upgrading
> their resolver infrastructure to support client-subnet now that they
> see the benefits.
>
> It'd be a pity if this died on the vine just as others are starting to
> come around to the idea.
>
>
> Mark.
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>