IETF Logo Mail Archive

[Tools-discuss] How do we diagnose DOI errors?

Martin Thomson <mt@lowentropy.net> Mon, 19 October 2020 01:59 UTC

Return-Path: <mt@lowentropy.net>
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 6FED03A1216 for <tools-discuss@ietfa.amsl.com>; Sun, 18 Oct 2020 18:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=ZBPiRTcT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=LzqpTW9d
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 EyTtN4PCTAF1 for <tools-discuss@ietfa.amsl.com>; Sun, 18 Oct 2020 18:59:06 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 146993A1215 for <tools-discuss@ietf.org>; Sun, 18 Oct 2020 18:59:05 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 97A535C0097 for <tools-discuss@ietf.org>; Sun, 18 Oct 2020 21:59:04 -0400 (EDT)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Sun, 18 Oct 2020 21:59:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:date:from:to:subject:content-type; s= fm3; bh=OgIZu0eXmfm54tayM4is0aGsY35b37AKf52Qi4wkFIM=; b=ZBPiRTcT Ix++0oNkI5Zn7aCRjrRvpdgsZIUZ73S9b/UngrlT6sA03YWboKNCks68cqjJ30Mb 2Icv53uxUCxgF7EELPB8uBDCeIGYoHmJ+NcxERsLNXrqTGIf+yS8QFPYvtp215LJ 9vrznYb7ETHo5BIOx1DYw/xiAAxxGwB9dw6s5/KRImsHplxta429ZCCmkcdekqtO bdbf2ocp/y6ji2AqaWroP6jchjdJI3BN2coarNVWovB4slXI5t3euKoJRon377Hn bVDwd9UvqDerRI2/qZyEsrhMXAyoFu3Yk0V/jr3f1ZshvhYPuiMLQgxJ1KT1OrQA s4BsDkcEGmFFoA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=OgIZu0eXmfm54tayM4is0aGsY35b3 7AKf52Qi4wkFIM=; b=LzqpTW9dD1+d5WgFIIjPJEt0r//B5yMbmFnkhETadMSZJ Vaikf9ZCQFJKkLyX73GyiameOYh9kOTrIpQp7QfXcMW4bqM6f3Fjj2EBTa7bRbS7 uwHoXqcR6c6XpM9B+zUYfjyCkvvtnEiwOlThX0iVieGt5vIclGgCRotOlX956WO5 5v0OISYWgCPlgN9REz8aaE6SAvuWhUeKZuPGh+HrvuX7QyCHawSAyUQpwMMDesx9 a2uCUEjlgfmHsEUVCbHnU9UcvXZQMuFkkOrVYOLjUCn8fZfVy9c/qOvj2BuaRNQN xeWHo7wkvXvO3rV47b2c2IkzVPPBnKvaeoOnGAw3w==
X-ME-Sender: <xms:6PKMX-bnvk6uDY7e0xfIhzUqpTl2d7s5b0MVbvjVNx878DzjxlDAhQ> <xme:6PKMXxZ9n4-ainBVMNrpymIIh-oXgc19RIdTDevO2HYgqW_s4H22iswFE3EARxPqy gtE3FB9tpT9hre-7c4>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrjedtgdehfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesthdtredtre ertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghn thhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepgfehieeggfeileekhfdthfdtff egjeffvdekudffgfeltddujefhieeihffhveegnecuffhomhgrihhnpehivghtfhdrohhr ghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmth eslhhofigvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:6PKMX49e8swpw8h8S5TzWEPMw-Li0Fo2SC0XgOHUHbhTw8I_F16u2Q> <xmx:6PKMXwop3nZ9sfwnhiP3iTwWRWHDjJEkDwfxzdZVasb1-JIqR6sMIg> <xmx:6PKMX5o58vKcQCncgyVfjp6R4oapv4coEbD_rOkyr_eqSpCcoiXs5w> <xmx:6PKMX20pMqOnqtxvATrjOlSv5IojvxTImUA6GTW2rtyDNWIHtqRRAg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 32714201EA; Sun, 18 Oct 2020 21:59:04 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-489-gf39678d-fm-20201011.001-gf39678d0
Mime-Version: 1.0
Message-Id: <181dadfc-37bf-46ad-b907-853cad3dccd2@www.fastmail.com>
Date: Mon, 19 Oct 2020 12:58:44 +1100
From: Martin Thomson <mt@lowentropy.net>
To: tools-discuss@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Y2doL2JXp6mID3hBhmuqH1Orwew>
Subject: [Tools-discuss] How do we diagnose DOI errors?
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: Mon, 19 Oct 2020 01:59:07 -0000

https://xml2rfc.tools.ietf.org/public/rfc/bibxml7/reference.DOI.10.1145/357401.357402.xml returns 404.  It did not used to.

https://xml2rfc.tools.ietf.org/public/rfc/bibxml7/reference.DOI.10.6028_NIST.FIPS.180-4.xml is fine.

I've come to rely on this mechanism for citing documents, but it isn't good if it isn't reliable.  Some better information about how this operates would be great.

v2.23.0 | Report a Bug | By Email