[Tools-discuss] idnits tool strangeness

Carsten Bormann <cabo@tzi.org> Fri, 26 April 2013 10:18 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33B6721F989F for <tools-discuss@ietfa.amsl.com>; Fri, 26 Apr 2013 03:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MHFkwh7uPvD3 for <tools-discuss@ietfa.amsl.com>; Fri, 26 Apr 2013 03:18:23 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 0A68021F989C for <tools-discuss@ietf.org>; Fri, 26 Apr 2013 03:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r3QAIGTP021528 for <tools-discuss@ietf.org>; Fri, 26 Apr 2013 12:18:16 +0200 (CEST)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 7F3463B81; Fri, 26 Apr 2013 12:18:16 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 26 Apr 2013 12:18:15 +0200
To: "tools-discuss@ietf.org Discussion" <tools-discuss@ietf.org>
Message-Id: <0FE055C8-AD6D-4355-98B2-0E874A0C16FB@tzi.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Subject: [Tools-discuss] idnits tool strangeness
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 10:18:24 -0000

Something is not right about the online idnits tools.

From a recent mail exchange:

> I do not know why the nits check tool http://www.ietf.org/tools/idnits/ reports so many problems.  While I do not understand many of them, for example:
> 
> /tmp/draft-ietf-lwig-terminology-04.txt(185): update_references(    [RFC6606] distinguishes "power-affluent" nodes (mains-powered or)

This instance seems to work better:

http://tools.ietf.org/tools/idnits/

Still, you have to ignore the barrage of "outdated state file" messages at the start, though (see below).

I'm using the homebrew idnits (just submitted a pull request there, BTW), so I'm not directly concerned.
But can we restore online idnits to its former greatness?

Grüße, Carsten


idnits 2.12.16 

tmp/draft-ietf-lwig-terminology.txt:
 - The draft- state file is not from today.
   Attempting to download a newer one...
 - No draft-brandt-6man-lowpanz state file. Attempting to download it...
 - No draft-clausen-lln-rpl-experiences state file. Attempting to download it...
 - No draft-hui-vasseur-roll-rpl-deployment state file. Attempting to download it...
 - No draft-ietf-6lowpan-btle state file. Attempting to download it...
 - No draft-ietf-lwig-terminology state file. Attempting to download it...
 - No draft-ietf-roll-terminology state file. Attempting to download it...
 - No draft-mariager-6lowpan-v6over-dect-ule state file. Attempting to download it...
 - No rfc0793 state file. Attempting to download it...
   Attempted to download rfc0793 state...
   Failure fetching the file, proceeding without it.
 - The rfc1024 state file is not from today.
   Attempting to download a newer one...
 - The rfc172 state file is not from today.
   Attempting to download a newer one...
 - The rfc1981 state file is not from today.
   Attempting to download a newer one...
 - No rfc218 state file. Attempting to download it...
 - No rfc250 state file. Attempting to download it...
 - No rfc284 state file. Attempting to download it...
   Attempted to download rfc284 state...
   Failure fetching the file, proceeding without it.
 - No rfc3149 state file. Attempting to download it...
 - The rfc421 state file is not from today.
   Attempting to download a newer one...
 - The rfc4838 state file is not from today.
   Attempting to download a newer one...
 - No rfc4919 state file. Attempting to download it...
 - No rfc6551 state file. Attempting to download it...
 - No rfc6606 state file. Attempting to download it...
 - The rfc793 state file is not from today.
   Attempting to download a newer one...
 - The rfc802 state file is not from today.
   Attempting to download a newer one...
 - No rfc9959 state file. Attempting to download it...
   Attempted to download rfc9959 state...
   Failure fetching the file, proceeding without it.

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  http://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/id-info/1id-guidelines.txt: