Re: [Tools-discuss] Strange IDnits behavior (or is it something else?)

Lars Eggert <lars@eggert.org> Wed, 30 September 2020 07:33 UTC

Return-Path: <lars@eggert.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 063373A129C for <tools-discuss@ietfa.amsl.com>; Wed, 30 Sep 2020 00:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 TiCk9wkuJvFG for <tools-discuss@ietfa.amsl.com>; Wed, 30 Sep 2020 00:33:57 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 43D353A129A for <tools-discuss@ietf.org>; Wed, 30 Sep 2020 00:33:57 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:64e8:8d4c:6d6a:9695] (unknown [IPv6:2a00:ac00:4000:400:64e8:8d4c:6d6a:9695]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id DFBC7617C83; Wed, 30 Sep 2020 10:33:15 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1601451195; bh=zYDx9C0QNdN15p4Hz9HrJw94FgS9uDXeiyt67z2jRCg=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=lLh/3wGbKE4ztJBGsRBoWxS113JR/PRbjYNw3uWnOJItNPjleIOmopJGGFV2/zbQh ZNlRsTp8PoF46OeTpNj3xc5yrDNJ+Dbrj798kfag2tVr4KzLDZ/9LIcSvrace/p9Ga HsY8EknhG/rwpD52uwLpxA0Uj6RknBrNuQBMCWTs=
From: Lars Eggert <lars@eggert.org>
Message-Id: <D91053BB-B1C5-4B69-805E-526849B05D96@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_14E693C8-601C-45C7-8E23-787F03448536"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 30 Sep 2020 10:33:15 +0300
In-Reply-To: <235fce42-4ba4-718b-a957-5cc0875375b7@levkowetz.com>
Cc: tools-discuss@ietf.org
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <CAKKJt-eeYvfOuFwqTtXeHrYjnw3hQR_u8hb4sc9c1zSi5oXK0Q@mail.gmail.com> <3f032b28-3159-355e-db2c-8be749fad47e@gmx.de> <0B6004B7-8BBD-4A22-A155-7E8D47F6727D@eggert.org> <6742c6a8-5402-f62d-67ee-fed8b2f81619@levkowetz.com> <2DC190C0-F601-4CC0-99F1-644A4765B061@eggert.org> <235fce42-4ba4-718b-a957-5cc0875375b7@levkowetz.com>
X-MailScanner-ID: DFBC7617C83.A392E
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/4c-5TPh1EnIvVSdQnzdrEAmL99s>
Subject: Re: [Tools-discuss] Strange IDnits behavior (or is it something else?)
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 30 Sep 2020 07:33:59 -0000

Hi,

On 2020-9-23, at 0:26, Henrik Levkowetz <henrik@levkowetz.com> wrote:
> Being worked at; complete rewrite.  Not ready for primetime; will be within
> months.

is this development happening in the open, e.g., is there a GitHub repo?

The current idnits is basically broken (mostly because the state files seem to have gone AWOL), and I'd be happy to try a development version of whatever is next rather than live with the current defunct one.

Thanks,
Lars