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

Portia Wenze-Danley <> Thu, 06 June 2019 14:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0EF021200EA for <>; Thu, 6 Jun 2019 07:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zv-9V2bHprfa; Thu, 6 Jun 2019 07:26:48 -0700 (PDT)
Received: from [IPv6:2601:14d:8101:1c3c:2d67:1d90:f0a:89e3] (unknown [IPv6:2601:14d:8101:1c3c:2d67:1d90:f0a:89e3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id C39AC1200DE; Thu, 6 Jun 2019 07:26:47 -0700 (PDT)
From: Portia Wenze-Danley <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_72A9CD2E-AC70-4A36-9177-8ADD8D517ABB"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Thu, 6 Jun 2019 10:25:23 -0400
In-Reply-To: <>
Cc: IETF Tools Development <>, Alissa Cooper <>
To: Russ Housley <>
References: <> <> <> <> <>
X-Mailer: Apple Mail (2.3445.102.3)
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: Thu, 06 Jun 2019 14:26:50 -0000

Additionally once the LLC finalizes details of the future site, the ED will most likely be the person to receive endowment email.

Portia Wenze-Danley
IETF Administration LLC Executive Director (Interim)
(Formerly IETF Administrative Director (IAD)	
Internet Engineering Task Force (IETF)

> On Jun 6, 2019, at 3:08 AM, Alissa Cooper <> wrote:
> To clarify: planning for the domain transfer at this point seems fine since that is a certainty, but the future of the site content is unclear.
> Alissa
>> On Jun 6, 2019, at 8:49 AM, Alissa Cooper <> wrote:
>> There is discussion in the LLC Board about taking the site down altogether, so I would suggest that folks hold off on making plans for it for a bit.
>> Alissa
>>> On Jun 5, 2019, at 10:40 PM, Russ Housley <> wrote:
>>> 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.
>>> Russ
>>>> 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
>>> _______________________________________________
>>> TOOLS-DEVELOPMENT mailing list
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list