[Tools-discuss] STD URLs in Datatracker ... incomplete/broken
Toerless Eckert <tte@cs.fau.de> Thu, 27 July 2023 17:48 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 DD183C15EB2E for <tools-discuss@ietfa.amsl.com>; Thu, 27 Jul 2023 10:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 7nj5bDoh6vRU for <tools-discuss@ietfa.amsl.com>; Thu, 27 Jul 2023 10:48:32 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (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 91E8CC151B1E for <tools-discuss@ietf.org>; Thu, 27 Jul 2023 10:48:31 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4RBdXr0RtrznkXM for <tools-discuss@ietf.org>; Thu, 27 Jul 2023 19:48:28 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4RBdXq70kxzkwYQ; Thu, 27 Jul 2023 19:48:27 +0200 (CEST)
Date: Thu, 27 Jul 2023 19:48:27 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: tools-discuss@ietf.org
Message-ID: <ZMKt65O9eh7cKRpj@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/6s40P-PHxiF2vhNzbnqR7DL_u5o>
Subject: [Tools-discuss] STD URLs in Datatracker ... incomplete/broken
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, 27 Jul 2023 17:48:37 -0000
1. If i should raise an issue for this to be tracked, pls. remind me where the URL for cases is.. 2. Problem (example): If you go to https://datatracker.ietf.org/doc/rfc1112, there is a hot link for the faxct that this is (part of) STD 5: https://datatracker.ietf.org/doc/std5/ This redirects to https://datatracker.ietf.org/doc/rfc1112/ Which i personally extremely appreciate, but i think it is incorrect, because STD5 is actually what e.g. RFC editor says correctly: https://www.rfc-editor.org/info/std5 Aka (from std-index.txt): 0005 Internet Protocol. J. Postel. September 1981. (Format: TXT=241903 HTML= bytes) (Also RFC0791, RFC0792, RFC0919, RFC0922, RFC0950, RFC1112) Like several other STD's it is a list of RFCs. None of the other RFCs in STD 5 have a STD's element in their datatracker page, which is rally not a good thing. Same thing for all other STDs conssiting of more than one RFC. Only one of them gets STD recognition in datatracker. 3. Proposed solution: I have not found on datatracker an equivalent to RFC editors STDs pages, but that is really the only correct way to show a STD, aka: include the list of all contributing RFCs. Not sure if it would be good enough to point all dattracker RFC pages if applicable to the RFC-editor URLs for the Standard, or to replicate this into datracker. But i would not like to see that datatracker removed STD information. If i am not mistaken, Datatracker should even be more authoritative on STD status of RFCs than RFC Editor (aka: IETF/ISE designating document status, RFC-Editor just publishing them). Cheers Toerless
- [Tools-discuss] STD URLs in Datatracker ... incom… Toerless Eckert
- Re: [Tools-discuss] STD URLs in Datatracker ... i… Toerless Eckert
- Re: [Tools-discuss] STD URLs in Datatracker ... i… Carsten Bormann
- Re: [Tools-discuss] STD URLs in Datatracker ... i… Robert Sparks
- Re: [Tools-discuss] STD URLs in Datatracker ... i… Toerless Eckert