Re: [Tools-discuss] another case of links not updating

Robert Sparks <rjsparks@nostrum.com> Thu, 07 May 2020 14:05 UTC

Return-Path: <rjsparks@nostrum.com>
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 4B4D03A0408 for <tools-discuss@ietfa.amsl.com>; Thu, 7 May 2020 07:05:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.404
X-Spam-Level:
X-Spam-Status: No, score=-1.404 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.275, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 tJZf7CnpfaJw for <tools-discuss@ietfa.amsl.com>; Thu, 7 May 2020 07:05:35 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 527683A0406 for <tools-discuss@ietf.org>; Thu, 7 May 2020 07:05:34 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 047E5OtQ000810 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 7 May 2020 09:05:25 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1588860326; bh=Q6F+yfL4/yGy1aE3ygS1W/4gvz6b3HcOeYsswc+P60M=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=tXIrfHlWdRaBGoP/HQS2no27j6WuZ7lVkz9gW84LEtJfo+mRnP5AvTeYxzy+Ogwfi 181ukYWEjX4L/RiXELvImkGnJ5CFXEe3bysvc77RGUD4gKQxwBOEXDPi9GPuFrIMOu dw6Q0xgdYZxi02cuDDo/VAzkjTLdDdJGWda61r+I=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Julian Reschke <julian.reschke@gmx.de>, Carsten Bormann <cabo@tzi.org>
Cc: Paul Wouters <paul@nohats.ca>, Henrik Levkowetz <henrik@levkowetz.com>, tools-discuss@ietf.org
References: <alpine.LRH.2.21.2005061024040.16512@bofh.nohats.ca> <d538a7da-8e90-cf26-3c39-b0dd5b2241b9@levkowetz.com> <alpine.LRH.2.21.2005061352200.20509@bofh.nohats.ca> <ae0875b4-13b6-387a-df7a-f157e39c1992@nostrum.com> <B8FBCD91-94F2-414F-B34C-1296F5552304@tzi.org> <e1d064d6-fc25-618a-bbcd-4333d8d9040e@gmx.de>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <b9e5060b-9b23-b20e-d25b-ee5159c7301e@nostrum.com>
Date: Thu, 7 May 2020 09:05:22 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <e1d064d6-fc25-618a-bbcd-4333d8d9040e@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/agNQrLTej0worZT2nkQ9SJ9aXDI>
Subject: Re: [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: Thu, 07 May 2020 14:05:40 -0000

On 5/6/20 10:35 PM, Julian Reschke wrote:
> On 06.05.2020 22:31, Carsten Bormann wrote:
>> Hi Robert,
>>
>>> On 2020-05-06, at 20:15, Robert Sparks <rjsparks@nostrum.com> wrote:
>>>
>>> The datatracker doesn't have this problem.
>>
>> That is good to know.
>>
>> Paul’s insistence on a fix is also an indication that we continue to 
>> rely on the tools server.  Its format for presenting RFCs, and the 
>> links that point to it, are still widely used by many people, inside 
>> and outside the IETF.
>> ...
>
> Which reminds me that for drafts published using V3 XML, we now have a
> public URI for the proper HTML version to link to, but these URIs get
> broken when the draft expires.

Thanks - I've captured that as a ticket.

FWIW: https://www.ietf.org/archive/id/draft-reschke-http-jfv-10.html

>
> Best regards, Julian