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

Mark Nottingham <mnot@mnot.net> Tue, 13 October 2020 01:07 UTC

Return-Path: <mnot@mnot.net>
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 D74B73A0AE4 for <xml2rfc@ietfa.amsl.com>; Mon, 12 Oct 2020 18:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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=mnot.net header.b=oCl5LGEf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VYgt/PP5
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 CZ3qPpRRh9rA for <xml2rfc@ietfa.amsl.com>; Mon, 12 Oct 2020 18:07:41 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3BCC3A0A62 for <xml2rfc@ietf.org>; Mon, 12 Oct 2020 18:07:41 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 9433B15C5 for <xml2rfc@ietf.org>; Mon, 12 Oct 2020 21:07:38 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 12 Oct 2020 21:07:38 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:to; s=fm3; bh=dPGfdeqUBNg5LTnp6XdRQzC0BtYPI/1th +dZu7H5O8o=; b=oCl5LGEfbOEnLVeHvPVdd5s/gAOtVDB2mQVRsgyG6alMBnAa4 Il4WfjMszpuVkeqN3wcfz01/5On+yUkTwsrFIUBmaFq/UDIj8jnOVylVLC/gF9YE yEY7nbt1budK74qylngYpN/6Zqzpg3WSxVXZVD8dsUbcxkUl95MhbqbxS9ht7Qea 7XBxJ+OrneiAg+EeJ69AVeFlvw/SNsWDNw4viafeWz/LQwjx73yiioWPw4cw4Rhw pAY2nkJhr2joYZ/hnWJ9cHp11YeIH2XGO7lSsIR5dFvkXUH3pD4W9UfloM2yM7sq DeDhEyLyvPnIWmF2zVN2loZNUK2aF6t+THM6A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding: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=dPGfde qUBNg5LTnp6XdRQzC0BtYPI/1th+dZu7H5O8o=; b=VYgt/PP5Yaqb4a81e2peJJ VL2zyHM6UNrbccZb1MYCkSOi5yITd7YV+xR6zPZSir6IVzhISQ6+Ui7pT/XjCJ7E SAuXi68L9nP2Gkjt4PYogbb0mCaE5rcH93EDojmbOONJTwBiGB0KgfaolD/wFOLq 2Y/zmEv0xW2fS3pinEk30Hx+oKsNKLN7yRpsxL3Zi0/+9l3F1iN1cOzF+BdUBhkN aVP4d91QHHtNh3qCK+VRGwR5LG+A7u/378ZqN0H0KmQapDsILZzlsCucylrIzFFN EYjh+MiHF1hBHro4gqqUT8IU5H1Fy6RZntYP+FESMgJL3mprq2awr3fXAuk/Mqog ==
X-ME-Sender: <xms:2f2EX0F48Vuj3F-EA3EkmeAkrFj6BKMVww0VNRrdDRUI88DTeqmzMw> <xme:2f2EX9W1vJnyQSA-Mw04KMq3IA4RmTac_DP1pgRtyfchmC4QXwPDB4_p8QT3ktySd AsgeiZFkhFF_fwNhw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrheekgdeggecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephfgtgfgguffkfffvofesthhqmhdthh dtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohht rdhnvghtqeenucggtffrrghtthgvrhhnpedvvdegjeeikefhueeijeetheejvefhudehle fhkedugeefuefhteetveegheefueenucffohhmrghinhepihgvthhfrdhorhhgpdhgihht hhhusgdrtghomhdprhgvuggsohhtrdhorhhgpdhmnhhothdrnhgvthenucfkphepuddule drudejrdduheekrddvhedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:2f2EX-Ihc04BuWXGh2974NPkI2UgeKxsW-BBQ8aHOhBJ_9-Xu-If_g> <xmx:2f2EX2HlsVR_B8oPKYFBm6qW9242aySkQOJAHooHqPor6DboJqjD7w> <xmx:2f2EX6WUg7PlM72U12GAfvmpTZSzdzjsMmfVBnS9EZOuWC5f0FSAQQ> <xmx:2v2EX9fbwekqH-HMC_KSpdls_OKiYoaM6nfenDv4xNceCqx3uYmJXg>
Received: from marks-air.mnot.net (119-17-158-251.77119e.mel.static.aussiebb.net [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 81BF63280059 for <xml2rfc@ietf.org>; Mon, 12 Oct 2020 21:07:36 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Message-Id: <C68CE326-E5F7-46BF-9EC0-313AB5431F6E@mnot.net>
Date: Tue, 13 Oct 2020 12:07:33 +1100
To: xml2rfc@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/5OXMvZ9HP1r7x0Htux3e9Orsd7w>
Subject: [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 01:07:44 -0000

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/