IETF Logo Mail Archive

Re: Fwd: problem with recent drafts on tools.ietf.org? {35440727}

Paul Wouters <paul@nohats.ca> Thu, 04 March 2021 00:11 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87A883A0AB8 for <wgchairs@ietfa.amsl.com>; Wed, 3 Mar 2021 16:11:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_HELO_NONE=0.001, SPF_NONE=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=nohats.ca
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 71ul00hetmcP for <wgchairs@ietfa.amsl.com>; Wed, 3 Mar 2021 16:11:38 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 0795B3A0AB4 for <wgchairs@ietf.org>; Wed, 3 Mar 2021 16:11:38 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4DrWW65NLRzFKH; Thu, 4 Mar 2021 01:11:30 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1614816690; bh=CEQdkmDZ5Tq1erG56basSvAZgSDOZS0J2N7LGE5U4Pc=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=YuWJ6pNiFfN+G+sBeCMfclD5Y62pQ8cLyy5O0M02EDL7ntADTLzz6AaaPoQKv0SiM nMoV7Gw/4Ava8CcciAioWdM8F2zcmS6fu2ekrFHjBlCr0JCXyceLWPOCNEdD7t64f/ DOkrTmxVXD43IvNm9VMeR5OUccP4YebOxX2dzwoM=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id H9hcykWXJaqr; Thu, 4 Mar 2021 01:11:29 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 4 Mar 2021 01:11:29 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 3D4186029B62; Wed, 3 Mar 2021 19:11:28 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 3BF2D66B1E; Wed, 3 Mar 2021 19:11:28 -0500 (EST)
Date: Wed, 03 Mar 2021 19:11:28 -0500
From: Paul Wouters <paul@nohats.ca>
To: Lou Berger <lberger@labn.net>
cc: Working Chairs <wgchairs@ietf.org>
Subject: Re: Fwd: problem with recent drafts on tools.ietf.org? {35440727}
In-Reply-To: <fcb1efac-931e-3c68-21f6-954c053c99e3@labn.net>
Message-ID: <f67944c-ed65-4873-a625-941bd4f19f15@nohats.ca>
References: <35440727.JitbitHelpdesk.46704.0bb5cf6e-5ee4-475f-a405-1f97b826a0a9@jitbit.com> <fcb1efac-931e-3c68-21f6-954c053c99e3@labn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/NJqk-tLdRgqSVL_hMm1Dwmc_nPw>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2021 00:11:41 -0000

On Wed, 3 Mar 2021, Lou Berger wrote:

> Well this is a troubling response -- does anyone know if there's plans for tools.ietf.org? I would have thought that some thought would be given to this and
> maybe some announcement made to the IETF.  Did I miss it???  Are we just destined to the whims of bit rot?

> As you are probably aware, tools.ietf.org is owned and operated by Henrik who has, unfortunately, departed the IETF.

I would really like some clarification about what happened, and who owns
the rights of the content on tools.ietf.org, and if it is not IETF or
ISOC, how we ended up in a position where we didn't own what we
published for many years. And what the plans are with regard to ensuring
URLs posted there remain valid - even if only to redirect back to
something that _is_ under IETF / ISOC change control.

Paul

v2.23.0 | Report a Bug | By Email