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:11 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 53393126CC7 for <dnsop@ietfa.amsl.com>; Fri, 23 Mar 2018 11:11:33 -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 2sjFRNgwgNht for <dnsop@ietfa.amsl.com>; Fri, 23 Mar 2018 11:11:31 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 E299E126B6D for <dnsop@ietf.org>; Fri, 23 Mar 2018 11:11:31 -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 BD8CF3AB041; Fri, 23 Mar 2018 18:11:31 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id ABA67160051; Fri, 23 Mar 2018 18:11:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 9BFAA16006D; Fri, 23 Mar 2018 18:11:31 +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 0b_lqfe_LrZU; Fri, 23 Mar 2018 18:11:31 +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 49E42160051; Fri, 23 Mar 2018 18:11:31 +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: <5AB53F8B.9070504@redbarn.org>
Date: Fri, 23 Mar 2018 18:11:27 +0000
Cc: Bob Harold <rharolde@umich.edu>, dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7CF21F70-9419-4D6A-B555-FC229F90E8A9@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>
To: Paul Vixie <paul@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pgjMqenTq3RSTrMPVsciJp8W9s8>
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:11:33 -0000

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. You can you whatever you want, it will be your responsibility (and costs), not the implementors. So, the people can keep their old system running, they just can’t expect the current DNS to interoperate with them.

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 
--
Ondřej Surý — ISC

> On 23 Mar 2018, at 17:55, Paul Vixie <paul@redbarn.org>; wrote:
> 
> 
> 
> Ondřej Surý wrote:
>> Thanks, now I understand what you are asking for;), so what about:
>> 
>> “No existing Internet Standard uses these Resource Records and there no
>> know practical usage in the public Internet.”
> 
> i think this is overbroad. if we aren't also sure that it's not being used in some private network somewhere, we should not tell implementers to remove support. a lot of private networks use internet protocols and implementations to support their local apps and users.
> 
> mf, mg, mb, and mail1 are i think still in use on some as/400 intranets.
> 
> when i removed UID and GID from BIND it was because there was no RFC, not because i wasn't fully aware of some older athena implementations still in use at that time which used these instead of TXT.
> 
> ideally we'd put out an extended call for comments about anything we'd like to remove if it ever worked to anyone's knowledge. if it never worked, like extended label types in EDNS, they can just be removed.
> 
> this is how we handled IQUERY deprecation and i think it went well.
> 
> -- 
> P Vixie
>