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

Joe Abley <jabley@hopcount.ca> Mon, 13 May 2019 05:03 UTC

Return-Path: <jabley@hopcount.ca>
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 7B1821200EA for <dnsop@ietfa.amsl.com>; Sun, 12 May 2019 22:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 Om4-PSdxEzlF for <dnsop@ietfa.amsl.com>; Sun, 12 May 2019 22:03:25 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14377120043 for <dnsop@ietf.org>; Sun, 12 May 2019 22:03:25 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id n19so6521368pfa.1 for <dnsop@ietf.org>; Sun, 12 May 2019 22:03:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=LaZRaxADXAetJjc6AVcrVIuoLTkHxnoQGS7g5oDd/t8=; b=jTpG7cQOGDqVbaYOs1Xz3CdescdvodOXLmLTeW+JNj/GlQ2Zvpdk8Y1RsI2rbvNW8q iEuLThMb1fiQN8AObqlv0JK5292T+vbxvv1DZu51diyWOoroXVU94yC6TzREM8x9/QSp Qt1h0x7rfMpO+2SttHV5EfsEZU3Jc59BvFm4o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=LaZRaxADXAetJjc6AVcrVIuoLTkHxnoQGS7g5oDd/t8=; b=l46Nzr++xshBqONqIhoCTHtCP0rFOdP7YVWekAMwPl8H37KXcotgZcbs/UJ1B2jrVN hnxtGvScXKQVJuTjR2W0uiVARTBYC+NyUsgb4zA8C63PmZdE9G4LluwOLe42fLd1UyyT NzBjTUw9GK3ESoOZv7EHq1KSrIeFHv7v7FC7kI90ngdytL+UURF1LHIV9GMOSA18zAJ2 2AA3O/nxEwktZFlGuGDjZ6WdPUAVX5Iu/Z3rEHQx0/dsIeVHMLstlItq27pwAc1afnVC TKRDK+hNoFyJuStvP8QxnOW9wEh6QCQM+29e4BwT99yDitih64uauRe734uGelw+jpYA tYpA==
X-Gm-Message-State: APjAAAVzAHmQn4pMqOqaMaAOFJq5NR+4CUIyFIvjf9bq1djsO7Re5aI8 h9oc0cVXzQwidm87iXMKavzXrw==
X-Google-Smtp-Source: APXvYqzEuJUNglIWxbIxdRtVh8YUaQse8QpIUXtJmB6A90qf3i0c8hoexhYM0CJj19HVXCT6ECzM2g==
X-Received: by 2002:a63:d652:: with SMTP id d18mr12204234pgj.112.1557723804479; Sun, 12 May 2019 22:03:24 -0700 (PDT)
Received: from [10.196.28.49] ([203.155.148.62]) by smtp.gmail.com with ESMTPSA id h6sm25555632pfk.188.2019.05.12.22.03.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 May 2019 22:03:23 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
Message-Id: <2316B135-B048-491B-8E35-2D8FAC76A0A8@hopcount.ca>
Content-Type: multipart/signed; boundary="Apple-Mail=_0EA10412-C03C-4310-BC99-9F0DFBF88363"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Mon, 13 May 2019 12:03:20 +0700
In-Reply-To: <7023B4C5-5207-4183-A945-244E65F00302@isc.org>
Cc: dnsop <dnsop@ietf.org>
To: =?utf-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org>
References: <155771990790.31813.2767356343632633845.idtracker@ietfa.amsl.com> <7023B4C5-5207-4183-A945-244E65F00302@isc.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/iFjirsHZ6FlLEs35AMsd7cKTvoQ>
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 05:03:27 -0000

On 13 May 2019, at 11: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?  This would make things much simpler in the
> future when we want to formally cleanup more obsoleted records (like NINFO and RKEY, etc...).

I don't know what experts could be expected to know enough about the entire ecosystem to make that call. I also don't know that there's any measurement that could be used in all cases to indicate that an RRTYPE is dead. These both seem like shortcuts that could have unintended consequences.

I think it's better to rely upon a consensus process. Following the example you're setting here might mean that this is an exercise we repeat in the IETF every year or two. I think that's ok.


Joe