IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] Draft of an SoW for the 2019 yangcatalog projects

Alissa Cooper <alissa@cooperw.in> Thu, 17 January 2019 21:54 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33A4D130EF1 for <tools-development@ietfa.amsl.com>; Thu, 17 Jan 2019 13:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=VOxXOnp4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gn4HtYX/
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 tkuRwIEAJ_Ic for <tools-development@ietfa.amsl.com>; Thu, 17 Jan 2019 13:54:41 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC26012958B for <tools-development@ietf.org>; Thu, 17 Jan 2019 13:54:40 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id D50B928A2C; Thu, 17 Jan 2019 16:54:38 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 17 Jan 2019 16:54:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=w DPGBmLr1jBtx99pg/65ZGTRJ2A+6cGZVl9rNJ/Lj/s=; b=VOxXOnp4MI/4fbjnS RoF9kfLkVJxNwQtgKSzi/D+cJ6nc6pSWuwFyQl2CD4ZG6kCPHb77oVm36HY8hw4G NjB35yefKAU7cTD9Spn/1Hj98t4FxSCkY9rfsZxEX3egKou8bmD3pbnbNKDwxkKJ aMDVRv2AnPICfgNW4URE58SE4K4FSIbzos1WhhS4p8N3/X0HBpcNwPrYOJQU8H6R hvWDkSK3rouD+BbWFLjOqd3FOIzKPucVrVfrtwBiR+Gmtx1AhTyI/tJ7eWHS/Muf D8Iv+1Td1CmsaY7ue67ON3QxatuTHUE4o9NrFgUGUlRqqD5L40J+gcE+VFflX/W2 GHJRw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; 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=fm1; bh=wDPGBmLr1jBtx99pg/65ZGTRJ2A+6cGZVl9rNJ/Lj /s=; b=gn4HtYX/N4rSRR9OkvILRRwcmd910a1wsprwYIk9Wm/yIJjnY5h7yIHDb u72Xc2kS9YF/5hAR6/ynNcq5iBw0MBP2++NNz8OfTHj1KECXCvqehuqgIhJdTFcf aboMVbUvYWoOIqgQ2NOswWi0FwPiJs2qHHKUnILhE8+3qC1R7CBqIkpzQZ+EqkZw KNBZEeWp1NcjjBs9UKws1vHkqj/IWs+E+WKVAfvqB56KI/sV8MGxWO7T1QlbBImH TmsWCSpJN+F+j0dCSNDU1D9dFV03HhlkzPLq1NbWu6EfCa1+X/p2P7gMFP3Kbip0 gPkSZaqdFM+xB3cqR9eqcFLSHciqA==
X-ME-Sender: <xms:nvlAXEspLvHbG2vJleBywQbvjHia-sH7fGhoUxY5LYkar9mIJ_KAdg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrgeekgdduheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjff fgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceo rghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrihhnpehivghtfhdrohhrgh enucfkphepuddvkedruddtjedrvdeguddrudejfeenucfrrghrrghmpehmrghilhhfrhho mheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:nvlAXBV2x2XfARbONhI0Rd9apKdbwrbe1s5gbMqvp_1j-vNuj01Y6g> <xmx:nvlAXNErOPJCF0coqlCsyihQL8QlQ2yiK1pKrRQAtuPtZS3XwMG0Ug> <xmx:nvlAXDYlpSNZCJi2m9jjwQnuqk79oxdvNvzMuUCVBab5ZRdd33Gojw> <xmx:nvlAXIVSqfqnUTbzKVUSJT4HfKptooilTyT7pIkNd6swnSoNTfeZAg>
Received: from dhcp-10-155-208-94.cisco.com (unknown [128.107.241.173]) by mail.messagingengine.com (Postfix) with ESMTPA id 15D76E425A; Thu, 17 Jan 2019 16:54:38 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <86d5b213-3c0b-308d-b9a7-0460c52996dd@nostrum.com>
Date: Thu, 17 Jan 2019 13:54:37 -0800
Cc: IETF Tools Development <tools-development@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8183824-D026-486A-BF87-59FF56CBADC5@cooperw.in>
References: <86d5b213-3c0b-308d-b9a7-0460c52996dd@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/Cp3INXeQy10BwoHpPHlzXaTCJrQ>
Subject: Re: [TOOLS-DEVELOPMENT] Draft of an SoW for the 2019 yangcatalog projects
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2019 21:54:43 -0000

Hi Robert,

> On Jan 17, 2019, at 11:48 AM, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> I've restructured Eric's original draft of this SoW to make what is being bid on a little more concrete.
> 
> The first two sections look very similar, and it is tempting to combine them. However, from IM conversations with Eric, he feels keeping them separate is useful, and we may choose to award them to different contractors.
> 
> Also, we should discuss how long the RFP process is likely to take. Eric was originally hoping to have contractors in place in early February, but I think the RFP process will take at least 6 weeks. If we were to finalize the SoW quickly, we would still be looking at early to mid-March for awarding contracts.

Can you say how you calculated that amount of time? Given the nature of this project, it seems like we could put out the call for 2.5-3 weeks and then hopefully select a bidder within a week or two, ideally.

Alissa

> 
> RjS
> 
> 
> 
> <sow-2019-yangcatalog-v1.pdf><sow-2019-yangcatalog-v1.docx>_______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development

v2.23.0 | Report a Bug | By Email