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

Jim Reid <jim@rfc1035.com> Mon, 13 May 2019 04:51 UTC

Return-Path: <jim@rfc1035.com>
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 B231E1200EA for <dnsop@ietfa.amsl.com>; Sun, 12 May 2019 21:51:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 QwQ_ERZ3jHIx for <dnsop@ietfa.amsl.com>; Sun, 12 May 2019 21:51:27 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCF2C120043 for <dnsop@ietf.org>; Sun, 12 May 2019 21:51:26 -0700 (PDT)
Received: from [10.196.28.82] (unknown [203.155.148.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 665C224205E6; Mon, 13 May 2019 04:51:23 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <7023B4C5-5207-4183-A945-244E65F00302@isc.org>
Date: Mon, 13 May 2019 05:51:20 +0100
Cc: dnsop WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C3E3ADC-16FE-467B-B0D4-26AEE698A153@rfc1035.com>
References: <155771990790.31813.2767356343632633845.idtracker@ietfa.amsl.com> <7023B4C5-5207-4183-A945-244E65F00302@isc.org>
To: =?utf-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/H6-tvC5GD_8lsc0zWi-13M7qKWU>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-sury-deprecate-obsolete-resource-records-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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 May 2019 04:51:29 -0000

On 13 May 2019, at 05:06, Ondřej Surý <ondrej@isc.org> wrote:
> 
> But I do have a question for the WG - should we add a text that would allow the “Expert Review” to formally DEPRECATE (as defined in this I-D) other RRTYPEs?

I'm not sure an expert reviewer could or should be in a position to make that determination Ondřej. They could probably put dead/dying RRtypes on a list that says something like "These RRtypes will be deprecated in N months time. Scream now if you disagree.". If nobody screams after a reasonable notice period, the RRtype(s) can then be killed. If there are complaints, we'd know if the RRtype(s) are still in use and/or if that use remains valid.

> This would make things much simpler in the future when we want to formally cleanup more obsoleted records (like NINFO and RKEY, etc...).

NINFO and RKEY were specifically created for use in .tel. If they are used there -- I don't know or care -- they should mainly be seen by the Telnic-controlled name servers and apps that use .tel domain names. [Unless Telnic's T&Cs have changed, registrants can't delegate these names to arbitrary name servers.] Someone would need to contact Telnic to find out how often these RRypes are found or looked up. They're the only ones who could say for sure if the RRtypes are obsolete or not. An expert reviewer probably wouldn't know that unless they asked.