Re: [netmod] Missing references

Henrik Levkowetz <henrik@levkowetz.com> Thu, 08 February 2018 13:32 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47A8012D95A for <netmod@ietfa.amsl.com>; Thu, 8 Feb 2018 05:32:39 -0800 (PST)
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 EN7ScXvUmt0u for <netmod@ietfa.amsl.com>; Thu, 8 Feb 2018 05:32:37 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34D5112D943 for <netmod@ietf.org>; Thu, 8 Feb 2018 05:32:37 -0800 (PST)
Received: from h-99-61.a357.priv.bahnhof.se ([82.196.99.61]:49635 helo=[192.168.1.120]) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1ejmJV-0001cc-7h; Thu, 08 Feb 2018 05:32:34 -0800
To: Benoit Claise <bclaise@cisco.com>, "t.petch" <ietfc@btconnect.com>, NETMOD Working Group <netmod@ietf.org>
References: <26131545-049c-9a1a-eb2b-cdad6fce3190@cisco.com> <036201d39c25$7bb5a060$4001a8c0@gateway.2wire.net> <db7e2a8d-ab53-5930-99cc-8b257190b519@cisco.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <ddb71ff2-3152-f51c-c346-f914400e0367@levkowetz.com>
Date: Thu, 08 Feb 2018 14:32:25 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <db7e2a8d-ab53-5930-99cc-8b257190b519@cisco.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="RItjovtWlW0opwCreDQK39s3jJU6L6AbV"
X-SA-Exim-Connect-IP: 82.196.99.61
X-SA-Exim-Rcpt-To: netmod@ietf.org, ietfc@btconnect.com, bclaise@cisco.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/nUBEx0sxlXLOzrvVDA2gs7FvExg>
Subject: Re: [netmod] Missing references
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2018 13:32:39 -0000

Hi Benoit,

On 2018-02-07 12:56, Benoit Claise wrote:
> Hi Henrik,
> 
> Could this check be added to idnits?

Yes.  I thought I had something like this already, but it was specifically
to look out for mentions of RFC2119.

As you may know, I'm due to begin a complete rewrite of idnits, from the
current implementation (idnits started as a 10-line AWK program to check
draft line lengths, in 2000 or 2001) to Python, this March.  I'd like to
defer this till then; adding code to the now close to 4000 lines of mixed
AWK and bash isn't always straightforward.


Best regards,

	Henrik

> Regards, Benoit
>> I just came across (yet) another example of a reference to an RFC in a
>> description clause of a YANG module that appears nowhere else in the
>> I-D.
>>
>> This seems to be a systematic error that some YANG module authors make;
>> can the tools be modified to pick it up?  The logic is simple enough.
>>
>> The latest example is in draft-ietf-rtgwg-yang-rip-09 which fails to
>> reference RFC5952;  I think that the I-D is in the RFC Editor queue.
>>
>> Tom Petch
>>
>> .
>>
> 
>