Re: tools.ietf.org -- basics not working?

Havard Eidnes <he@uninett.no> Sat, 16 October 2021 10:42 UTC

Return-Path: <he@uninett.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D3A3A1347 for <ietf@ietfa.amsl.com>; Sat, 16 Oct 2021 03:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, 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=uninett.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 b6vKN2Gc3-By for <ietf@ietfa.amsl.com>; Sat, 16 Oct 2021 03:42:39 -0700 (PDT)
Received: from smistad.uninett.no (smistad.uninett.no [IPv6:2001:700:1:0:eeb1:d7ff:fe59:fbaa]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 230933A1345 for <ietf@ietf.org>; Sat, 16 Oct 2021 03:42:37 -0700 (PDT)
Received: from smistad.uninett.no (smistad.uninett.no [158.38.62.77]) by smistad.uninett.no (Postfix) with ESMTP id 05ED443E99D; Sat, 16 Oct 2021 12:42:33 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uninett.no; s=he201803; t=1634380953; bh=IOuumRosEpql6mqWCFp21lev9FPKfdQR42RIHyNdpQE=; h=Date:To:Cc:Subject:From:In-Reply-To:References:From; b=Iii0W0Ku+ZGyznwbSbrZuZQT0dZ8Gf6bB9ys5loSoYDm3csC4SsCHvhWgayPBgrs2 pRxFmE68k2PgWk25k6PvLrHcLY493OIN7fr/kVzlkymB7IwJMPVcwql5hExluolMfk DbfKEv/nyJ5WmF/rnzX5GFIx7sj7jESKsr96pmzk=
Date: Sat, 16 Oct 2021 12:42:32 +0200 (CEST)
Message-Id: <20211016.124232.936466035773757308.he@uninett.no>
To: Brian.E.Carpenter@gmail.com
Cc: ietf@ietf.org
Subject: Re: tools.ietf.org -- basics not working?
From: Havard Eidnes <he@uninett.no>
In-Reply-To: <3bb21641-3f3a-6618-6f11-7120632215b6@gmail.com>
References: <20211015.214613.911587687528063461.he@uninett.no> <3bb21641-3f3a-6618-6f11-7120632215b6@gmail.com>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CeQSpQyvQyHnCJuqGuJFYzf4A9Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Oct 2021 10:42:45 -0000

> I guess you missed this:
> https://mailarchive.ietf.org/arch/msg/ietf/0n-6EXEmkTp3Uv_vj-5Vnm3o0bo

That's entirely possible, though I did catch some related
discussion.

Someone pointed out that the "fetch RFC by number" functionality
is now again working, so that's good, at least.

The document indexes for "RFCs" and "Documents" are still dead.

I would have hoped for and expected a "make before break"
transition strategy...

Regards,

- HÃ¥vard