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

Alissa Cooper <> Thu, 06 June 2019 07:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 71BAB1201AF for <>; Thu, 6 Jun 2019 00:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=YJICcQ0X; dkim=pass (2048-bit key) header.b=dwNWdsLX
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rdqFD2Z7Zg45 for <>; Thu, 6 Jun 2019 00:08:43 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D9606120182 for <>; Thu, 6 Jun 2019 00:08:42 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id E1B9C22293; Thu, 6 Jun 2019 03:08:41 -0400 (EDT)
Received: from mailfrontend1 ([]) by compute7.internal (MEProxy); Thu, 06 Jun 2019 03:08:41 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=s 0wAVhXzrdqFCQMH+2ERKTPIKWmMjhqp+bTuc+eVvyI=; b=YJICcQ0X1J5yXjg78 29RHXkLam2D9DvsCB4ijdNZmMFjjrgfzjiA8f+7RDp3QMYAUKYYPLfnH8nVQzjoM K66A9wxAUH/HsJ+8g1aCCwcFG//LIbVwgBBVAcqHsa5XBMzjC8O0BNMnNMA56F3f jmVKKNPgBtbrPG7BiND74Ymg+HPf2ZQhZCg2ng1qi4M9Sw8rSzJDDBPZ6Ufcf98i WVyxdyNHNyVdgH+W1sKSVGbp4XPa7dVnPAcSu4PI7D8g0mEhoWB0PP700QvaBhKQ rbj/JBU+NDVqyfiA8ZkDgo2Hx6YV7AswC3YgV1zryAp2i1DcQCjzrv3Ru1h+CVug YHjlw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=s0wAVhXzrdqFCQMH+2ERKTPIKWmMjhqp+bTuc+eVv yI=; b=dwNWdsLXfMOeoJF2Rj+mpSaA5qlPzEi9Lxk1P0hRvxX/aHjkHYeIAWFGX DZ7GXv8T2oQJ8noTeTYDsO84L5AB6LjLNs3N2l8CIOMQuZmdLG02y8PMDhvwWmNp RDdL+S2z/UGJW6+dOz1S4GEsGbV8x7rnhwRqs6tdVbotolgNFwMmp5hZa1d44rib VzvWCwdh3nY9t0C6SqrjbGzjBCN/faPfQnUeAF69UuXGpuELxZGFsYktgwI1SwYL mygYzxjCfIzYMc+toccngw6Rpf7xJUqcnsxYlvyfeYSgS7nDigMoUkupaR201qgN saakOK/e2y90oUFlQ+LroScPpRCYA==
X-ME-Sender: <xms:-bv4XLJpnUCAnTJthp6FKMWz98TsP-E7UGZ8PS_KaGYu_4mGorh-8A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudegfedgudduhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeetlhhi shhsrgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomh grihhnpehivghtfhdrohhrghdpshhushhtrghinhhivghtfhdrohhrghenucfkphepudej fedrfeekrdduudejrdekkeenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrse gtohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:-bv4XJ79PxRU9idBQqFINN4luIySdnLXqZCpVaDPvpOfMeTVeJwscQ> <xmx:-bv4XCnAZftQmQVCBXHs7PsTOgklQubm_DAwJrqUH6O79a_eD3G4Kw> <xmx:-bv4XLIADMVXGcDHd6IlOQXtXwvlVU9zoIfgxItS1CVwc54sLfW4dQ> <xmx:-bv4XCUmpQIctYmo68RYm5cXO1BIA2yAQ9qrIDbkmGXJM9ohJfeS3w>
Received: from (unknown []) by (Postfix) with ESMTPA id F1B3780059; Thu, 6 Jun 2019 03:08:40 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <>
In-Reply-To: <>
Date: Thu, 6 Jun 2019 09:08:41 +0200
Cc: IETF Tools Development <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <>
To: Russ Housley <>
X-Mailer: Apple Mail (2.3445.9.1)
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 07:08:46 -0000

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.


> 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