IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Mon, 19 October 2020 16:18 UTC

Return-Path: <julian.reschke@gmx.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 A84D53A0BBA for <tools-discuss@ietfa.amsl.com>; Mon, 19 Oct 2020 09:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.246
X-Spam-Level:
X-Spam-Status: No, score=-0.246 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 xVzRYAFX4q8b for <tools-discuss@ietfa.amsl.com>; Mon, 19 Oct 2020 09:18:11 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9B503A0BB1 for <tools-discuss@ietf.org>; Mon, 19 Oct 2020 09:18:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1603124288; bh=G46t4q75w2TB4gZqlDMZ8hJkWP4dTBooOggNl0YYQ4o=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=d/CSV1EdgBlzo6gJp35Pquay/2RuWxSKqcUZUHegGNb0v7UTwFGIF7oaA6O8NelTP YqfGzQvxsidcz/oXV7ATOSrdxg9Z31qCjtCY8Xn4CoGmaJVnruy6flkfirywZjPntW Mt/yU/fQrS6rVlAzuncC1Nt7PTBksaPwINQ/ercg=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([84.171.157.37]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MiJVG-1jz2bG2K9e-00fSaH for <tools-discuss@ietf.org>; Mon, 19 Oct 2020 18:18:08 +0200
To: tools-discuss@ietf.org
References: <181dadfc-37bf-46ad-b907-853cad3dccd2@www.fastmail.com> <9ee90430-405b-4cf2-b1e7-5d241698a108@www.fastmail.com> <32564.1603119444@localhost>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <8b5ebbef-6dca-1f56-0576-f395815c4b40@gmx.de>
Date: Mon, 19 Oct 2020 18:18:09 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.3.3
MIME-Version: 1.0
In-Reply-To: <32564.1603119444@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:4ZskasTp7Rj2+0L6YQMV44sNlam6qkSUzvXD/USixWW+bJdDPvh AGJLXKB956X7p+tWgPObHZdcjUDMvLC/49K+ZewBk0OJGUkLPE14RsYFcqZc3kERNTUe8d/ IGqYJS20gJvX6kr8iuZT6DE+RzpI8SYTVZLDZnV88B0cmfLG5ND6pnkdmvAA2wY+NTi963f joCFyr98KerCRIy44/3Xg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:WyJMEsI3Ylc=:K2mnnTp14AeFkMciBKPkyz K3VcFpBx1QyozxJc9mYGj4lKcSnDKc4FE/kULCBIa7QTe3PGHEsFCmye2rYmBwiFdi8KdVAu4 gNSk0CTpxGYXYhQgEK1554zYXYgPcboz6im9R53OalLfZo17b0HP1HDn5e0GLvIGM0+pQIrEy X1CghEWP7XgVDxpaVR+ZRhvXBytumrX5sokuNlVaqYbuhiWECl4JMRGMdx+VWr6vAUhF8y/NW drA9dLPuRfIYrdxwP7W+XHKD7R98+hzb0mgf8dj/cw3qQvGZymMrSTYGGjRQaa9Pwm66/DwNn 6ACVfr0eR58EV3K3BL1lI36da20Pd9eRQH8Crfzfz/80hlPSIT33CgVUGhZY5fa69h0jbEaCw zyvbZFQ5jEk7QZ62Ye8LKceN57nSm41VZSRbdjzuMwPjegfo083IRY2Wy3pY3YhQR/6hOEDA2 3gM3/DW4Ob93xfnI9d2cTaQxcmgOBhHZGC3inlo/15Ii/yfhQM2eqTDicUbDa1zt+7AWtSEMl 8d0sAHZWqAy/RiiAgtoa3gVYwVyJSherti90pJI5WUFznOEeMLBFU4ERTGee3jzVbhirpnynz VFgvdyjSiyAV+LYKI8b7S/pPMVo8QTLz0KoCbFKXg2uM6eC+pO8Sm483iIFqeERcizaf1rkGE IX164zMn9+08d6hi/LKj8BJ7cysUZvyovucbateK/GtIp19n1nO76KqIuIVpNBMquGdYtByLQ 8TV4SCekwf1Jh3DdjrYj9oNDxj7eB7eh2gvJWKD/eMoJLQEx6umTsE3GerS1IB8yo+HvybLee yUD+k1FFrFZzwuFdlNn/AtCW5Cek1oF7nBdPkL/ka0dvsP8mk3cRzFm1UclmWJF5gDt1aMrLV DjC47qyUiaZy5MycDQtg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/70TJTXb2aiRx_s3FngkWLwFEbWs>
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 16:18:13 -0000

Am 19.10.2020 um 16:57 schrieb Michael Richardson:
>
> 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.

Best regards, Julian

v2.23.0 | Report a Bug | By Email