IETF Logo Mail Archive

Re: [DNSOP] Second Working Group Last Call: draft-ietf-dnsop-refuse-any

Stephane Bortzmeyer <bortzmeyer@nic.fr> Sun, 19 March 2017 21:53 UTC

Return-Path: <bortzmeyer@nic.fr>
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 10CBB12940D for <dnsop@ietfa.amsl.com>; Sun, 19 Mar 2017 14:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 sMpvSL6v_i3P for <dnsop@ietfa.amsl.com>; Sun, 19 Mar 2017 14:53:08 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6BA112940B for <dnsop@ietf.org>; Sun, 19 Mar 2017 14:53:08 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 4B61831C7E; Sun, 19 Mar 2017 22:53:07 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id 65795190680; Sun, 19 Mar 2017 22:50:11 +0100 (CET)
Date: Sun, 19 Mar 2017 22:50:11 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Doug Barton <dougb@dougbarton.us>
Cc: Havard Eidnes <he@uninett.no>, dnsop@ietf.org
Message-ID: <20170319215011.GD13608@sources.org>
References: <d8f1076e-a635-7620-5e2b-0c70efe2c0cf@dougbarton.us> <EDDF24B8-42F6-4BCA-8162-5A5C7CDC8CA2@rfc1035.com> <65cec05f-bb1b-cb9e-d874-a73c9c4653ac@dougbarton.us> <20170317.112234.1061898802480941262.he@uninett.no> <1f14d1bb-ba25-0569-c73b-f167d4fb43d3@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1f14d1bb-ba25-0569-c73b-f167d4fb43d3@dougbarton.us>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 8.7
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZFUsYc7N5mK4c7Sqq_Zt8bSJzAo>
Subject: Re: [DNSOP] Second Working Group Last Call: draft-ietf-dnsop-refuse-any
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 19 Mar 2017 21:53:10 -0000

On Fri, Mar 17, 2017 at 10:19:27AM -0700,
 Doug Barton <dougb@dougbarton.us> wrote 
 a message of 63 lines which said:

> he has made the excellent point that the query exists, and has
> well-defined semantics

Well-defined, may be (but I do not think so, RFC 1035 is almost silent
on it), but not well-understood by many developpers.

> I find it astonishing that there is this overwhelming "We must
> preserve backwards compatibility at all costs!" sentiment on so many
> ridiculous topics in the DNS, and yet because people hate the ANY
> query (and particularly one software author's perceived
> misappropriation of it) SO MUCH y'all are willing to throw backwards
> compatibility out the door for something that it's absolutely clear
> will break deployed applications

Using QTYPE=ANY and expecting all the records in the answer does not
work TODAY (and even yesterday, see Evan Hunt and Mark Andrews'
messages). So, we break nothing.

v2.23.0 | Report a Bug | By Email