Re: [Tools-discuss] Lost bibxml for some non-final I-Ds that led to an RFC?

Robert Sparks <rjsparks@nostrum.com> Thu, 19 January 2023 15:22 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 2AA95C14CE4A for <tools-discuss@ietfa.amsl.com>; Thu, 19 Jan 2023 07:22:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AhJ6moNB4Y1T for <tools-discuss@ietfa.amsl.com>; Thu, 19 Jan 2023 07:22:13 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84243C14CE47 for <tools-discuss@ietf.org>; Thu, 19 Jan 2023 07:22:13 -0800 (PST)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 30JFMBkM040761 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 19 Jan 2023 09:22:12 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1674141732; bh=VnDoitmpdRjUinVIdv1oYA9428pN5DcGLkZ3iMeTiiM=; h=Date:To:References:From:Subject:In-Reply-To; b=WYSPTofakZ4B6tdsmAPSr/fEDBI3HAxATjHgfg8UQqOeBIXcVLU82E2AnQTMd5pd/ NvqWXk/x8OxLVIOtHfegUn7JBBQltNS5UaemXl7M5JfoI4ussuO6cEVVeOTkesQ6tB 7BHE+Vd27QgZn4s+PQuecp90p+quw2fRCI9KrUIM=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Message-ID: <ce2b5b87-0e97-0e05-6036-0f9b64c4ca11@nostrum.com>
Date: Thu, 19 Jan 2023 09:22:06 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
Content-Language: en-US
To: Carsten Bormann <cabo@tzi.org>, Tools Team Discussion <tools-discuss@ietf.org>
References: <FC4F5C0B-F4C1-4EA8-AA84-3124CA715172@tzi.org>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <FC4F5C0B-F4C1-4EA8-AA84-3124CA715172@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Z66Ua8gPJZ_0QYpIBNBjabzDL0I>
Subject: Re: [Tools-discuss] Lost bibxml for some non-final I-Ds that led to an RFC?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
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, 19 Jan 2023 15:22:17 -0000

This has the same root as 
https://github.com/ietf-tools/datatracker/issues/4933

There are no DocHistory records (which are what would know about the 
authors and title for each of the older draft versions if they had 
changed) for anything except version 19.

(And the "rock meets hard place" issue 
(https://github.com/ietf-tools/datatracker/issues/4581) we are 
experiencing with author initials interacts with the above. Because of 
the change we made at 
https://github.com/ietf-tools/datatracker/pull/4470, we aren't _really_ 
returning author information from the history at the moment, which is 
clearly wrong).

RjS


On 1/18/23 4:24 PM, Carsten Bormann wrote:
> GOOD:
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-roll-rpl.xml
> HTTP/2 200
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-roll-rpl-19.xml
> HTTP/2 200
>
> BAD:
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-roll-rpl-00.xml
> HTTP/2 404
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-roll-rpl-07.xml
> HTTP/2 404
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-roll-rpl-18.xml
> HTTP/2 404
>
> GOOD:
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-6lo-btle.xml
> HTTP/2 200
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-6lo-btle-00.xml
> HTTP/2 200
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-6lo-btle-07.xml
> HTTP/2 200
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-6lo-btle-16.xml
> HTTP/2 200
>
> $ curl -I https://datatracker.ietf.org/doc/bibxml3/draft-ietf-6lo-btle-17.xml
> HTTP/2 200
>
>
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org - https://www.ietf.org/mailman/listinfo/tools-discuss