Re: [DNSOP] Fwd: New Version Notification for draft-sury-deprecate-obsolete-resource-records-00.txt

Ondřej Surý <ondrej@isc.org> Fri, 23 March 2018 18:32 UTC

Return-Path: <ondrej@isc.org>
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 0DFFA126579 for <dnsop@ietfa.amsl.com>; Fri, 23 Mar 2018 11:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 1bIxWsEg7kCQ for <dnsop@ietfa.amsl.com>; Fri, 23 Mar 2018 11:32:11 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 8AA99124B18 for <dnsop@ietf.org>; Fri, 23 Mar 2018 11:32:11 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 659E13AB06D; Fri, 23 Mar 2018 18:32:11 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 55BFD160070; Fri, 23 Mar 2018 18:32:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 4767F16006D; Fri, 23 Mar 2018 18:32:11 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id oQkUl66AqIRl; Fri, 23 Mar 2018 18:32:11 +0000 (UTC)
Received: from [100.101.127.104] (ip-37-188-152-153.eurotel.cz [37.188.152.153]) by zmx1.isc.org (Postfix) with ESMTPSA id E42AF160051; Fri, 23 Mar 2018 18:32:10 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: =?utf-8?Q?Ond=C5=99ej_Sur=C3=BD?= <ondrej@isc.org>
X-Mailer: iPhone Mail (15D100)
In-Reply-To: <5AB546CB.3030408@redbarn.org>
Date: Fri, 23 Mar 2018 18:32:07 +0000
Cc: Bob Harold <rharolde@umich.edu>, dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCAE4014-67F8-4E73-A893-AA06B83E880B@isc.org>
References: <152180695934.17546.2068402636242578841.idtracker@ietfa.amsl.com> <9CEA4F8F-4E71-4508-A088-103DD58F88E1@isc.org> <CA+nkc8DhXEEhiDqwHuA-_zNQc0n=rTZ-VZ6X8-0w-tY_0SC0eA@mail.gmail.com> <40ABB9EB-58EC-48FF-8117-60EE0E7006EF@isc.org> <CA+nkc8BfMKRUHuW+3EzOCeZHfmu1jeOgfVcszTbTYh9k2VTBcA@mail.gmail.com> <002DCABB-24CE-42FA-8DA6-2A458E5F89A1@isc.org> <5AB53F8B.9070504@redbarn.org> <7CF21F70-9419-4D6A-B555-FC229F90E8A9@isc.org> <5AB546CB.3030408@redbarn.org>
To: Paul Vixie <paul@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/v0SCK0YtdqNgEalT2KJqfBiBLi0>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-sury-deprecate-obsolete-resource-records-00.txt
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: Fri, 23 Mar 2018 18:32:13 -0000

What’s so wrong of using TYPExxx for these if you absolutely need them to run the ancient technology while at the same time running the latest version of BIND (or your favorite DNS server)?

Your argument feels like strawman to me. And I am not the one sitting on a pile of passive DNS data, so I can’t pull the numbers...

We are not taking the ability to put random TYPEnnn records into the zone, we are just saying the tools just won’t understand them anymore. Again nothing is going to break on the day one.

Ondrej
--
Ondřej Surý — ISC

> On 23 Mar 2018, at 18:26, Paul Vixie <paul@redbarn.org>; wrote:
> 
> 
> 
> Ondřej Surý wrote:
>> I strongly disagree. The DNS protocol deserve cleanup. Deprecating
>> RRTYPEs doesn’t mean the will stop working on the day the RFC is
>> published, neither are people going to backport the removal of
>> RRTYPEs to existing DNS software releases.
>> 
>> It just means - whatever ancient stuff you are using - you are on
>> your own now. It’s same as with the stuff that never got the RFC.
> 
> so anyone supporting an older internal network using modern tools has to stop upgrading their tooling. that's not constructive for anybody. all of us will be less safe if these tools become non-upgradeable.
> 
>> Paul, sorry, but the argument “but I know of people running” ancient
>> systems can’t be used at every attempt to cleanup the kitchensink
>> protocol that DNS is right now.
> 
> ondrej, if you're looking for stuff to kill that nobody is using and that needlessly fattens the camel, there's a lot of lower hanging fruit.
> 
> to say it's complicated, let's simplify it, and oh by the way we need to add a CNAME to support the never-workable RFC 5011 plan we adopted in ignorance many years back, in the same breath, confuses me.
> 
> -- 
> P Vixie
>