Re: [TOOLS-DEVELOPMENT] Notes for 12Feb tools call

Alissa Cooper <> Tue, 12 February 2019 14:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 49B3A1271FF for <>; Tue, 12 Feb 2019 06:19:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=Qq5ggibY; dkim=pass (2048-bit key) header.b=PsG2kWZz
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8ooH_u9GOR_3 for <>; Tue, 12 Feb 2019 06:19:24 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DB29F1200B3 for <>; Tue, 12 Feb 2019 06:19:23 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id C290B2319C; Tue, 12 Feb 2019 09:19:22 -0500 (EST)
Received: from mailfrontend1 ([]) by compute7.internal (MEProxy); Tue, 12 Feb 2019 09:19:22 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm2; bh=y7HJJoe5HNDIGWMMmaOWlbQ QwIJXnu3TRfNoNKTx0JA=; b=Qq5ggibYWX7dYbrLCy7XWqOukw6on5Qv9Cr9SdN DYyq3xD3JKJmHt9baxrg2gSqCca+Av0igHsmkNdeqVoUtkeynK+zq/bPszXLK1Mg 0mEOjT8u/2DAItxSiAOR9NLQgkrU9g7qP0oAabylFuhxWu57+u+CDRm5h/QlBaBs iLzF3z2jVbQ1qKAMgwtVSerYF9FlVRO1a1c1DU5PNySPoMx/uXg1kzolkB1uKnRz 6BC2cm203hK7OeI9FORXjnKOKOoRveIQsxn3ET85+nKyVgCWHGl097fhebybsTZv WHqujNRLIXCSUmFIpvqj+93kwEqeiIDO5tjT6o+EEnNkJ3Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc: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=y7HJJo e5HNDIGWMMmaOWlbQQwIJXnu3TRfNoNKTx0JA=; b=PsG2kWZzsbG+A//CnzWdMv L9oYYJfvmBwo4hknpI6BvXn46hDmQgMuFKdpNapc/BVv0tT8Iop+sfOfh/KPbK1t Tr2SHvcCiuxmk7pOoRJR8ln7uml5mp3vkcOMtisqqgX1ctmlEjrcxVReKJ4PMxqP LBjSyp4kH1O27M6bjwlDeljExr2Hk+TBYnwVxcGABhaZVAR0qNNez/N95ALcx/A5 eqFxc3hMZgP7wBHFYX4oWhoCjBbyrtfejb9lOpTtx7oGfpbl/zujUIZq1dcXKbpU O2a8cTRNaEulFI/SE17HtinafQ0nmVyEVwi2YVXLcAVfpHKlLaWUuqeUgaHBWdrg ==
X-ME-Sender: <xms:6tViXKooeKEfqzRdYBWh2RZ4hXMNPuRdkxZPhI0viBOQWHXMhrVUhg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledruddtuddgieegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenogfuuhhsphgvtghtffhomh grihhnucdlgeelmdenucfjughrpefhkfgtggfuffgjvfhfofesrgdtmherhhdtvdenucfh rhhomheptehlihhsshgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrih hnqeenucffohhmrghinhepghhoohhglhgvrdgtohhmpdhivghtfhdrohhrghenucfkphep udejfedrfeekrdduudejrdekjeenucfrrghrrghmpehmrghilhhfrhhomheprghlihhssh grsegtohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:6tViXIyN-6fGCNKfGETxsyutBx2rjpnnnp4ZHFdsIlntRgd8uMK7bQ> <xmx:6tViXHIWKtpo8d-ZQUffYzMv9tQvcE9yR0ORNZYbtAwdUAP0Tm9O2A> <xmx:6tViXCK7XKRp44UPXqWavWHsgYMEjASft4qT3Wb_LyB_JyU1sEwYQw> <xmx:6tViXPJPigeG0JDybdV7UT8VBdoc4AVqd8JVRu0ThuiCIjiEU8ZhyQ>
Received: from (unknown []) by (Postfix) with ESMTPA id AC4DDE461F; Tue, 12 Feb 2019 09:19:21 -0500 (EST)
From: Alissa Cooper <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4D020DF1-D586-4AFF-A8C7-DA30BF2CBAFE"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 12 Feb 2019 09:19:27 -0500
In-Reply-To: <>
Cc: Robert Sparks <>, IETF Tools Development <>
To: Eric Rescorla <>
References: <> <> <> <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
Subject: Re: [TOOLS-DEVELOPMENT] Notes for 12Feb tools call
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: Tue, 12 Feb 2019 14:19:26 -0000

> On Feb 8, 2019, at 12:40 PM, Eric Rescorla <> wrote:
> On Fri, Feb 8, 2019 at 9:29 AM Robert Sparks < <>> wrote:
> On 2/8/19 11:20 AM, Eric Rescorla wrote:
>> On Fri, Feb 8, 2019 at 8:51 AM Robert Sparks < <>> wrote:
>> # IETF Website #
>> Torchbox has completed their last major deliverable (upgrading the 
>> website to a more modern version of wagtail). There are a small number 
>> of tickets related to documentation and requests for information we 
>> should have before shifting the code into our own public code 
>> repository. Note that the wagtail project continues to issue new 
>> releases. The project with torchbox brought us to wagtail 2.2.2. The 
>> current release now is 2.4.
>> However, we are blocked on deploying this latest deliverable. The way we 
>> are serving python applications via Apache right now (mod_wsgi) only 
>> allows the use of one version of python. Many of our applications are on 
>> Python 2.7 right now. This includes the datatracker and the mailarchive. 
>> Wagtail, on the other hand, dropped support for python 2.7 at Wagtail 
>> 2.0. Waiting until we have all exisiting deployed applications ported to 
>> python 3 to deploy the deliverable from Torchbox is exceedingly 
>> suboptimal. It will delay the current plan for the tools-team to take 
>> over maintenance of the website code and start adding features the 
>> secretariat has asked for. We've started conversations about what other 
>> options we have besides waiting for everything to be ported to python 3.
>> Why does the version of datatracker impact the version of Wagtail we run? They seem to be on different hosts, so can't they run different versions of Python?
> They are currently served from the same machine, even if they have different hostnames.
> This seems like a good opportunity to move one to a different machine, or better yet, to some system (containers?) where hardware assignment doesn't matter.
>> # Yangcatalog #
>> We've shifted the plan for short-term deployment and development to 
>> occur using the existing externally hosted server.
>> Can you provide some more background for this? Why can't this be moved to an IETF server (or IETF-managed cloud)
> There were some difficulties trying to move this to an IETF server given the current level of access to internals (shell access to the machine) required by the application. Eric and the developers were experiencing connectivity problems that couldn't be reproduced from other locations, and it appears some trouble with outbound connections that Glen's team couldn't isolate. The goal is _definitely_ to be where we could deploy anywhere. The first task in the outstanding SoW includes the work needed to get the project to the point that shell access isn't required by the developers or application expert. It will also improve release packaging to make deploying wherever more feasible.''
> Hmm.... So my instinct here would be to hold off on doing anything else until that's happened. Alissa, WDYT?

I think that sounds like what the SOW calls for.

> -Ekr
>> -Ekr
>> The meeting application improvement SoW is essentially ready to issue.
>> I have text from Ekr to work into the RPC security code review SoW. The 
>> RPC has asked that we hold off issuing that RFP until some changes 
>> related to the new format are better integrated into their repository so 
>> that the review focuses more on the code that will actually be used.
>> The Inline-Errata SoW is still under review and has several unresolved 
>> comments. The lastest version is at 
>> < <>>. 
>> One of the major observations in the comments is that this project is 
>> focusing on the existing (old-format) publication format, and is not 
>> targetting or taking advantage of the new format in any way. That's 
>> intentional. We need to have some run-time experience with the new 
>> format before we can sensibly ask a contractor to work on inlining 
>> errata into it. We plan to learn from this project, and apply what we 
>> learn into the new format with a future project.
>> The next SoW to be developed is for IANA expert review tracking.
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>> <>
>> <>
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list