IETF Logo Mail Archive

Re: [DNSOP] I-D Action: draft-ietf-dnsop-refuse-any-04.txt

Robert Edmonds <edmonds@mycre.ws> Mon, 13 February 2017 17:38 UTC

Return-Path: <edmonds@mycre.ws>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DADA4126DFB for <dnsop@ietfa.amsl.com>; Mon, 13 Feb 2017 09:38:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 fRbk4YRY7FEa for <dnsop@ietfa.amsl.com>; Mon, 13 Feb 2017 09:38:02 -0800 (PST)
Received: from mycre.ws (mycre.ws [45.33.102.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B07171293EB for <dnsop@ietf.org>; Mon, 13 Feb 2017 09:38:01 -0800 (PST)
Received: by chase.mycre.ws (Postfix, from userid 1000) id 0C52212C0E75; Mon, 13 Feb 2017 12:38:01 -0500 (EST)
Date: Mon, 13 Feb 2017 12:38:01 -0500
From: Robert Edmonds <edmonds@mycre.ws>
To: Richard Gibson <rgibson@dyn.com>
Message-ID: <20170213173801.j7dpxzjy5morksg5@mycre.ws>
References: <148661979638.4286.4234665114055399732.idtracker@ietfa.amsl.com> <CAC94RYZM+KMS2c3CVx=8Q005XYGQqNRv--23H7_aTpuY05tEMQ@mail.gmail.com> <CAN6NTqy9_jKXT4Fc9KhmcW7Fq6DTiU2HmzBoWn+YA1fALOh5zA@mail.gmail.com> <CAC94RYYhV0ye252bLNSGPmqQhdZ772AkaJ7us86X1j4nppsWDg@mail.gmail.com> <alpine.DEB.2.11.1702131258580.23062@grey.csi.cam.ac.uk> <CAC94RYbSkp2h_jOBgmrP3oZouSigPp9xPVxoKxkYft55qMyiZQ@mail.gmail.com> <alpine.DEB.2.11.1702131642360.23062@grey.csi.cam.ac.uk> <CAC94RYZSLzv=SDMxXTh2ZWZJUbG0AtMhmO62ynCpg-WO8XJcYg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAC94RYZSLzv=SDMxXTh2ZWZJUbG0AtMhmO62ynCpg-WO8XJcYg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mAj3RHkJXrWwiHAK6UKAsOR8acQ>
Cc: Tony Finch <dot@dotat.at>, Ólafur Guðmundsson <olafur@cloudflare.com>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-refuse-any-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 13 Feb 2017 17:38:05 -0000

Richard Gibson wrote:
> On Mon, Feb 13, 2017 at 11:46 AM, Tony Finch <dot@dotat.at> wrote:
> 
> > OK. But does an EDNS flag help? What if you are using old tools?
> 
> 
> If you are using old tools, then you don't get new conveniences (the same
> is true of using OPT class to specify a maximum payload size exceeding 512
> bytes, using the DO bit to request DNSSEC records, and using the COOKIE
> option for authentication). But a flag would still be there, conveying
> information even if any given client or tool isn't looking for it.

It looks like dig does display unknown EDNS flags -- as a masked hex
value:

https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=blob;f=lib/dns/message.c;h=45bd0ba9ea31be49ffa5bca2aebb77ebc2f3b95c;hb=4801fbccaa431ca6a72753150cbb58e5d4627cc4#l3408

You think this would actually provide any sort of useful information? No
operator would understand what "MBZ: 0xNNNN" means without re-training,
and if you're re-training operators you may as well point them to this
document.

-- 
Robert Edmonds

v2.23.0 | Report a Bug | By Email