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

Shane Kerr <shane@time-travellers.org> Mon, 26 March 2018 08:24 UTC

Return-Path: <shane@time-travellers.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 6D40712D86A for <dnsop@ietfa.amsl.com>; Mon, 26 Mar 2018 01:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 jqcDnhk-pUk9 for <dnsop@ietfa.amsl.com>; Mon, 26 Mar 2018 01:24:15 -0700 (PDT)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF7D41204DA for <dnsop@ietf.org>; Mon, 26 Mar 2018 01:24:15 -0700 (PDT)
Received: from 1.ip-192-99-247.net ([192.99.247.1] helo=[127.0.0.1]) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1f0NR7-0004kb-MX for dnsop@ietf.org; Mon, 26 Mar 2018 08:25:01 +0000
To: dnsop@ietf.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> <CCAE4014-67F8-4E73-A893-AA06B83E880B@isc.org> <20180324124958.GA29255@puck.nether.net> <CAJhMdTPRn=mUQ6xh_HFdFLBk109b_M2+saS86KFxsttb8_oVvw@mail.gmail.com> <dc666131-be55-4d20-254d-0f77fc338be5@pletterpet.nl>
From: Shane Kerr <shane@time-travellers.org>
Message-ID: <5ce52d0d-0eaa-d9f4-5f07-606580adb57f@time-travellers.org>
Date: Mon, 26 Mar 2018 08:23:00 +0000
MIME-Version: 1.0
In-Reply-To: <dc666131-be55-4d20-254d-0f77fc338be5@pletterpet.nl>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hAdb83RChfVtLGRs3IxhNyzT7-E>
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: Mon, 26 Mar 2018 08:24:18 -0000

All,

Matthijs Mekking:
> 
> 
> On 24-03-18 14:48, Joe Abley wrote:
>> On Mar 24, 2018, at 13:49, Jared Mauch <jared@puck.nether.net>; wrote:
>>
>>>     isc/bind can and perhaps should implement logging for these
>>> rrtypes that say they may be going away so folks can see the impact.
>>
>> I'm actually surprised to see that support for rarely-used RRTypes is
>> really upsetting the camel.

I'm not that surprised. It's pretty close to a bike shed topic; everyone
can understand it, it is not *that* important, and so everyone can have
an opinion that is basically as valid as any other. ;-)

> To me this deprecating obsolete records is more an exercise of picking
> the low hanging fruit. Start with an easy task, gain experience for more
> difficult "unloading the camel".

I agree with Matthijs here.

I think Paul's advice of looking at prior work in deprecating unused (or
harmful) bits of the DNS protocol makes sense. Since the way software is
deployed and used is not exactly the same now as it was in 2002, so we
actually have to repeat the exercise and see how stuff breaks now (or
not... I mean... MB?).

Cheers,

--
Shane