[Tools-discuss] another case of links not updating

Paul Wouters <paul@nohats.ca> Wed, 06 May 2020 14:27 UTC

Return-Path: <paul@nohats.ca>
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 83A3B3A0ADF for <tools-discuss@ietfa.amsl.com>; Wed, 6 May 2020 07:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_NONE=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=nohats.ca
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 Y_Mr7-tPe2nh for <tools-discuss@ietfa.amsl.com>; Wed, 6 May 2020 07:27:21 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED3EB3A0AEB for <tools-discuss@ietf.org>; Wed, 6 May 2020 07:27:20 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 49HJny4YdSzF55 for <tools-discuss@ietf.org>; Wed, 6 May 2020 16:27:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1588775238; bh=EIQtwQD+SnInXlRI5OBo4wMZb+22p6DmtEErTky8aZU=; h=Date:From:To:Subject; b=P3u8QxTb9zeGW7eM8qDLqbQS9GxqptkmF1BV3DJ5XZL1j2Wx86TBCEA//oMswwmre 30al+zhBNhZSDvWvGZR4SQL3/35PtTZ8aGS31xwxJqhvhBIN2KDZ654aYmUNVcaeRL 9I4CgWRGsup3izcTIKqjegyYOAonLPaCSBZdMiRE=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 6HH41mJG3UXk for <tools-discuss@ietf.org>; Wed, 6 May 2020 16:27:16 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <tools-discuss@ietf.org>; Wed, 6 May 2020 16:27:16 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 7FF6B6029BA6; Wed, 6 May 2020 10:27:15 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 7F29C66B7C for <tools-discuss@ietf.org>; Wed, 6 May 2020 10:27:15 -0400 (EDT)
Date: Wed, 6 May 2020 10:27:15 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: tools-discuss@ietf.org
Message-ID: <alpine.LRH.2.21.2005061024040.16512@bofh.nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Wwa_OORU-1w4FjLc2dIfsxNIQxU>
Subject: [Tools-discuss] another case of links not updating
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, 06 May 2020 14:27:32 -0000

I see another case of links in older drafts not updating that there is a
newer draft.

See https://tools.ietf.org/html/draft-pwouters-powerbind-03

There is a -04 version but it is not indicating this.

The -04 is also not listed in the 00 to 03 version.

It's not a "timing" thing either as the -04 was submitted on April 30.


This issue has been present for years and I reported back on this many
times. Perhaps the tools team can share where this code lives, so that
others including me can have a look at it.

Paul