IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 19 October 2020 17:40 UTC

Return-Path: <mcr+ietf@sandelman.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 B0C693A0EB9 for <tools-discuss@ietfa.amsl.com>; Mon, 19 Oct 2020 10:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 EqfgDEz7cM9G for <tools-discuss@ietfa.amsl.com>; Mon, 19 Oct 2020 10:40:51 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8542D3A09FF for <tools-discuss@ietf.org>; Mon, 19 Oct 2020 10:40:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 1212A38992; Mon, 19 Oct 2020 13:46:59 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id d-mfj2kXsRN2; Mon, 19 Oct 2020 13:46:58 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 73A5E38990; Mon, 19 Oct 2020 13:46:58 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9E9A9715; Mon, 19 Oct 2020 13:40:49 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Julian Reschke <julian.reschke@gmx.de>, tools-discuss@ietf.org
In-Reply-To: <8b5ebbef-6dca-1f56-0576-f395815c4b40@gmx.de>
References: <181dadfc-37bf-46ad-b907-853cad3dccd2@www.fastmail.com> <9ee90430-405b-4cf2-b1e7-5d241698a108@www.fastmail.com> <32564.1603119444@localhost> <8b5ebbef-6dca-1f56-0576-f395815c4b40@gmx.de>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 19 Oct 2020 13:40:49 -0400
Message-ID: <9568.1603129249@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/SZNLe3V1OUY4KtVzqoLuFt7C-nw>
Subject: Re: [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 17:40:53 -0000

Julian Reschke <julian.reschke@gmx.de> wrote:
    >> Martin Thomson <mt@lowentropy.net> wrote:
    >> > As someone pointed out to me, this is now working again.  The original
    >> > question stands.
    >>
    >> 10.1145 works for me today using the link you listed.
    >> I had the same problem last weekend.  Very annoying.
    >> I could wget things from /rfc/bibxml/FOO, but not /rfc/bibxmlX/FOO.
    >>
    >> How do you typically use the URLs?
    >> In ENTITY statements, via <?rfc include=, or does kramdown generate things?
    >> I think that ENTITY statements are the least portable, and should be
    >> discouraged to the point of having warnings from xml2rfc.
    >> ...

    > How so? They are an integral part of XML.

If you use a specific URL, then it needs to be alive.
While many of the other abstractions can be retrieved from a variety of
sources and can be easily cached.

I suspect that there are smarter things you can put into the ENTITY,
I don't know how to do it, and I think neither do many other people.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email