IETF Logo Mail Archive

Re: [netmod] Missing references

Benoit Claise <bclaise@cisco.com> Wed, 07 February 2018 11:56 UTC

Return-Path: <bclaise@cisco.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 1CEE7124235 for <netmod@ietfa.amsl.com>; Wed, 7 Feb 2018 03:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 cDZUAFTXQzxy for <netmod@ietfa.amsl.com>; Wed, 7 Feb 2018 03:56:11 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1321126CE8 for <netmod@ietf.org>; Wed, 7 Feb 2018 03:56:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=550; q=dns/txt; s=iport; t=1518004571; x=1519214171; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=OhvUaHUayrHmfl6JDzFijWdwiJBySmNiXX8neogg8po=; b=hhZyGcY7hAYmtwCq43kZK+MQR+Gaw/Tw5RSlPx1211ZOqsj4ieSS8zS+ eeALjztVWGMDYZcrJpZfZcwYLBv4rO4JJHP8RU8eVFg94738jyn2flFV5 +xs7ft7p2W06aU7Gc9VTL1IVSsGfOwORh1KXOBUY4/lTA1RLKr2ix5mep k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ByAQCE6Hpa/xbLJq1dGQEBAQEBAQEBAQEBAQcBAQEBAYUnhA2LGI8MmhEKhTEKAoM/FAECAQEBAQEBAmsohSQGIxVRCxoCJgICVwYBDAgBAYoxshGCJ4UAg3iCCgEBAQEBAQEDAQEBAQEBIoEPg2aDbIIRDIJ5iDmCZQEEpCkJlXqCBYoziAaPc4gXgTw2IoFQMxoIGxWDBIR3QI5NAQEB
X-IronPort-AV: E=Sophos;i="5.46,473,1511827200"; d="scan'208";a="1864273"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Feb 2018 11:56:09 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w17Bu8Ij015367; Wed, 7 Feb 2018 11:56:08 GMT
To: "t.petch" <ietfc@btconnect.com>, Henrik Levkowetz <henrik@levkowetz.com>, NETMOD Working Group <netmod@ietf.org>
References: <26131545-049c-9a1a-eb2b-cdad6fce3190@cisco.com> <036201d39c25$7bb5a060$4001a8c0@gateway.2wire.net>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <db7e2a8d-ab53-5930-99cc-8b257190b519@cisco.com>
Date: Wed, 07 Feb 2018 12:56:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <036201d39c25$7bb5a060$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/tfR0qS5XT5a3LsnYKL_BRyGnb8Y>
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: Wed, 07 Feb 2018 11:56:13 -0000

Hi Henrik,

Could this check be added to idnits?

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
>
> .
>

v2.23.0 | Report a Bug | By Email