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

"Mark Delany" <f4t@november.emu.st> Thu, 12 February 2015 06:51 UTC

Return-Path: <f4t@november.emu.st>
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 A98AC1A9077 for <dnsop@ietfa.amsl.com>; Wed, 11 Feb 2015 22:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level:
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 YHiy2i55hFtj for <dnsop@ietfa.amsl.com>; Wed, 11 Feb 2015 22:51:26 -0800 (PST)
Received: from smtp1.bushwire.net (f5.bushwire.net [199.48.133.46]) by ietfa.amsl.com (Postfix) with SMTP id D69D91A906C for <dnsop@ietf.org>; Wed, 11 Feb 2015 22:51:25 -0800 (PST)
Received: (qmail 68264 invoked by uid 1001); 12 Feb 2015 06:51:19 -0000
Delivered-To: qmda-intercept-dnsop@ietf.org
DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=s384; d=november.emu.st; b=OP8OX71Nw5BEIA5wAquxJQHRaFUALaiC9SuF0qvKsEsLJRKNNbrmyF9CwfryRkeE;
Comments: DomainKeys? See http://en.wikipedia.org/wiki/DomainKeys
DomainKey-Trace-MD: h=16; b=49; l=C18R71D32M65F41M32T18S39?43R60?53M17C50?66C27I65;
Comments: QMDA 0.3
Received: (qmail 68257 invoked by uid 1001); 12 Feb 2015 06:51:19 -0000
Date: Thu, 12 Feb 2015 06:51:19 +0000
Message-ID: <20150212065119.68256.qmail@f5-external.bushwire.net>
From: Mark Delany <f4t@november.emu.st>
Mail-Followup-To: dnsop@ietf.org
To: dnsop@ietf.org
References: <629002B1-7A32-4A83-ACA1-0185F5355641@gmail.com> <20141224195229.4342.qmail@f5-external.bushwire.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="HxY/eTLWEtH+OqMc"
Content-Disposition: inline
In-Reply-To: <20141224195229.4342.qmail@f5-external.bushwire.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/f7PE3tVVU-tQ_pBlfQaL1jd2lyk>
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: Thu, 12 Feb 2015 06:51:27 -0000

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.