IETF Logo Mail Archive

Re: [xml2rfc] xml2rfc.tools.ietf.org site availability

Carsten Bormann <cabo@tzi.org> Tue, 13 October 2020 05:49 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 457583A0E53 for <xml2rfc@ietfa.amsl.com>; Mon, 12 Oct 2020 22:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 u-xf1xV58VPs for <xml2rfc@ietfa.amsl.com>; Mon, 12 Oct 2020 22:49:05 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A71633A0D0E for <xml2rfc@ietf.org>; Mon, 12 Oct 2020 22:49:05 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc60.dip0.t-ipconnect.de [84.141.204.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4C9Pk768vfzyQD; Tue, 13 Oct 2020 07:49:03 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <C68CE326-E5F7-46BF-9EC0-313AB5431F6E@mnot.net>
Date: Tue, 13 Oct 2020 07:49:03 +0200
Cc: xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 624260942.880482-203418f0e1d3337465f3cd78d3231c1a
Content-Transfer-Encoding: quoted-printable
Message-Id: <3517F297-B215-4A94-878C-64C8B3307EE4@tzi.org>
References: <C68CE326-E5F7-46BF-9EC0-313AB5431F6E@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/iuzTgz7BKvniZExRm9VoTCqFahU>
Subject: Re: [xml2rfc] xml2rfc.tools.ietf.org site availability
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2020 05:49:08 -0000

I’m wondering whether kramdown-rfc should be using more of the datatracker features here, as in

https://datatracker.ietf.org/doc/bibxml3/draft-ietf-core-groupcomm-bis/xml (*)

Pro: datatracker might have a higher reliability
Pro: datatracker is faster in having the data available for new I-Ds
Con: that solves only part of the problem (only works for I-Ds, other bibxmls including RFCs would still need to be taken from xml2rfc.tools.ietf.org).

(The fetch timeout currently is 60 s for new fetches; I don’t think adding to that will make a difference.)

Grüße, Carsten

(*) Oh: https://redbot.org/?id=87dhdaee


> On 2020-10-13, at 03:07, Mark Nottingham <mnot@mnot.net> wrote:
> 
> Hello,
> 
> The xml2rfc Web site's availability has been causing errors in the HTTP WG document builds (and elsewhere, anecdotally) for a little while now.
> 
> For example:
> 
> ~~~
> 68 /github/home/.cache/xml2rfc/reference.RFC.7234.xml: fetching
> 69  *** execution expired while fetching https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7234.xml
> 70  *** No such file or directory @ rb_sysopen - /github/home/.cache/xml2rfc/reference.RFC.7234.xml for /github/home/.cache/xml2rfc/reference.RFC.7234.xml
> 71  make: *** [draft-ietf-httpbis-client-hints.xml] Error 66
> ~~~
> 
> at <https://github.com/httpwg/http-extensions/runs/1244800935?check_suite_focus=true#step:6:68>. This has been happening fairly often in the last month or two.
> 
> Does the Tools team have some sense of why this is? E.g., is the site monitored? Can it be put behind a CDN to improve availability?
> 
> Also, looking at the responses served (e.g., <https://redbot.org/?id=2n90ryy0>), I notice that there isn't explicit freshness on them, which means that some caches won't store them, while others will choose their own freshness lifetime. It would be better to set an explicit one, e.g., `Cache-Control: max-age=3600`.
> 
> Cheers,
> 
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc

v2.23.0 | Report a Bug | By Email