IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 19 October 2020 14:57 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 021443A00D2 for <tools-discuss@ietfa.amsl.com>; Mon, 19 Oct 2020 07:57:30 -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 4lG30lDewP-K for <tools-discuss@ietfa.amsl.com>; Mon, 19 Oct 2020 07:57:27 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 438F73A005E for <tools-discuss@ietf.org>; Mon, 19 Oct 2020 07:57:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 554C638994; Mon, 19 Oct 2020 11:03:33 -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 R0NaveKSM1Ov; Mon, 19 Oct 2020 11:03:32 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 854DC38993; Mon, 19 Oct 2020 11:03:32 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2517C976; Mon, 19 Oct 2020 10:57:24 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Martin Thomson <mt@lowentropy.net>, tools-discuss@ietf.org
In-Reply-To: <9ee90430-405b-4cf2-b1e7-5d241698a108@www.fastmail.com>
References: <181dadfc-37bf-46ad-b907-853cad3dccd2@www.fastmail.com> <9ee90430-405b-4cf2-b1e7-5d241698a108@www.fastmail.com>
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 10:57:24 -0400
Message-ID: <32564.1603119444@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/brpmq-vGtr4F5x-6ystcPmM5hsc>
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 14:57:30 -0000

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.

Given that the contents are are static and are rsync'able, and I don't see
why they shouldn't be replicated widely.   An annoyance is that xml2rfc won't
use the local copy if the network copy returns 404, unless you specify --no-network,
which naturally only works if you already have *all* the references.

You can set $XML_LIBRARY to a path, and I think also set it to a URL.
At least you could, but I don't know if I've done this lately.

I also see, but maybe this doesn't do what I think:
  --rfc-base-url RFC_BASE_URL
                        Base URL for RFC links
  --id-base-url ID_BASE_URL
                        Base URL for Internet-Draft links
  --rfc-reference-base-url RFC_REFERENCE_BASE_URL
                        Base URL for RFC reference targets, replacing the
                        target="..." value given in the reference entry
  --id-reference-base-url ID_REFERENCE_BASE_URL
                        Base URL for I-D reference targets

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

At this point, xmlrfc.ietf.org redirects to xml2rfc.tools.ietf.org.
I thought that we were trying to bring tools into secretariat supported
hosts, and this certainly seems like low hanging fruit.

    >>
    >> 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.
    >>
    >> ___________________________________________________________
    >> Tools-discuss mailing list
    >> Tools-discuss@ietf.org
    >> https://www.ietf.org/mailman/listinfo/tools-discuss
    >>
    >> Please report datatracker.ietf.org and mailarchive.ietf.org
    >> bugs at http://tools.ietf.org/tools/ietfdb
    >> or send email to datatracker-project@ietf.org
    >>
    >> Please report tools.ietf.org bugs at
    >> http://tools.ietf.org/tools/issues
    >> or send email to webmaster@tools.ietf.org
    >>

    > ___________________________________________________________
    > Tools-discuss mailing list
    > Tools-discuss@ietf.org
    > https://www.ietf.org/mailman/listinfo/tools-discuss

    > Please report datatracker.ietf.org and mailarchive.ietf.org
    > bugs at http://tools.ietf.org/tools/ietfdb
    > or send email to datatracker-project@ietf.org

    > Please report tools.ietf.org bugs at
    > http://tools.ietf.org/tools/issues
    > or send email to webmaster@tools.ietf.org

--
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