[Tools-discuss] Future idnits feature request

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 04 October 2020 20:01 UTC

To: Tools Team Discussion <tools-discuss@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <8714b6cf-a590-b58e-ac8d-472b1c2fc4c8@gmail.com>
Date: Mon, 05 Oct 2020 09:01:08 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/ebs8FYDGWgzTdzsj1FzMBgLBBNQ>
Subject: [Tools-discuss] Future idnits feature request
Precedence: list

idnits correctly produces warnings such as:

 ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200)

However, afaik, it does not produce warnings like:

 ** Updated normative reference: RFC 791 (Updated by Updated by RFC 1349, RFC 2474, RFC 6864)

I believe this would be of benefit, since it ought to prompt the authors or reviewers to check whether those updates affect the draft. In fact I've often seen references to RFC791 that show ignorance of RFC2474, so this is not an artificial problem.

(I came to this by noticing that the proposed updates to the RFC style guide have removed the statement that the RFC Editor catches references to obsoleted RFCs, as described at https://tools.ietf.org/html/rfc7322#section-4.8.6).

Regards
   Brian Carpenter

[Tools-discuss] Future idnits feature request Brian E Carpenter