Re: [TOOLS-DEVELOPMENT] Transition of to IETF control

Russ Housley <> Wed, 05 June 2019 20:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8EBE7120158 for <>; Wed, 5 Jun 2019 13:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DlKj72NybKLd for <>; Wed, 5 Jun 2019 13:40:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5D7EF12014B for <>; Wed, 5 Jun 2019 13:40:23 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4B018300AEA for <>; Wed, 5 Jun 2019 16:21:05 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10026) with ESMTP id xSYsTI1tkdJN for <>; Wed, 5 Jun 2019 16:21:04 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown []) by (Postfix) with ESMTPSA id 1579D300260; Wed, 5 Jun 2019 16:21:04 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <>
In-Reply-To: <>
Date: Wed, 5 Jun 2019 16:40:20 -0400
Cc: IETF Tools Development <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Robert Sparks <>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <>
Subject: Re: [TOOLS-DEVELOPMENT] Transition of to IETF control
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 05 Jun 2019 20:40:28 -0000

Greg Wood suggested that the site could be could be restructured to remove the email address altogether.  However, we need to have forwarded to some IETF email address, and of course, someone needs to be responsible or reading the traffic that comes there.


> On Jun 5, 2019, at 4:22 PM, Robert Sparks <> wrote:
> Yes, if we take this, I strongly suggest putting it in a container, with its database also containerized. If it is just wordpress (that is, nobody's done anything special), all we'd really need is a copy of the database (IIRC, wordpress keeps its static content (like photos) in that database).
> I think whoever is supposed to manage the content (see e.g. the "Donor Wall" at the bottom of the page) should get some training from whoever's been doing that at ISOC so far.
> You're thinking ISOC would forward to whatever address we created? It seems to me that this will have to land on a person who can manage taking a donation. Until the LLC appoints someone else, I think that has to be the executive director, no?
> RjS
> On 6/5/19 2:57 PM, Russ Housley wrote:
>> Dear Tools Team:
>> The IETF LLC is working on transferring control of the IETF Endowment bank accounts from ISOC to the IETF, a process which should be completed on June 28. As a result, the related website and domain ( need to be transferred to IETF.
>> I have asked Glen to work with ISOC to get the domain name transferred to the IETF Trust.
>> The web site is a WordPress-driven site. I am unaware of any any associated source control.
>> In addition, the site points people to, so we will need to create a new mailbox for that.  I do not yet understand who will read the mail sent there, so I do not have a suggest way forward yet.
>> Is this a candidate for a new container?
>> Russ