IETF Logo Mail Archive

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

Jim Reid <jim@rfc1035.com> Mon, 13 May 2019 08:33 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 85FE7120047 for <dnsop@ietfa.amsl.com>; Mon, 13 May 2019 01:33:33 -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 Vx9oeP908S5N for <dnsop@ietfa.amsl.com>; Mon, 13 May 2019 01:33:32 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E11812003E for <dnsop@ietf.org>; Mon, 13 May 2019 01:33:32 -0700 (PDT)
Received: from [192.168.23.216] (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 4262424205E6; Mon, 13 May 2019 08:33:27 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <8174CA97-1D61-4EC5-9D65-6EB9819416C0@hopcount.ca>
Date: Mon, 13 May 2019 09:33:24 +0100
Cc: dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <289681F3-7C77-402A-99ED-FE6AEA8F726D@rfc1035.com>
References: <155771990790.31813.2767356343632633845.idtracker@ietfa.amsl.com> <7023B4C5-5207-4183-A945-244E65F00302@isc.org> <1A7FE19D-E4B1-48FB-8225-DCD055E4FDCD@icann.org> <20190513080019.GB28485@isc.org> <F8E0E608-524F-452A-9549-B5085C927487@icann.org> <8174CA97-1D61-4EC5-9D65-6EB9819416C0@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hKb4wXdLlSc32IxisbVJdB3XU1w>
Subject: Re: [DNSOP] [Ext] 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 08:33:34 -0000


> On 13 May 2019, at 09:22, Joe Abley <jabley@hopcount.ca> wrote:
> 
> I would prefer documented agreement about what is obsolete and what is not.

+1

Though a definition of what is meant by obsolete might be needed too: "no longer seen in the wild but could still be alive in closed environments", "deader than Elvis", "implementers MUST completely ignore this", "implementers SHOULD now treat this as an unknown RRype", etc.

v2.23.0 | Report a Bug | By Email