Russ Housley <housley@vigilsec.com> Mon, 25 February 2019 23:37 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6CE98131196 for <tools-development@ietfa.amsl.com>; Mon, 25 Feb 2019 15:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id lSKax_KJFGua for <tools-development@ietfa.amsl.com>; Mon, 25 Feb 2019 15:37:15 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 326A7131171 for <tools-development@ietf.org>; Mon, 25 Feb 2019 15:37:14 -0800 (PST)
Received: from localhost (localhost []) by mail.smeinc.net (Postfix) with ESMTP id 4D032300AB6 for <tools-development@ietf.org>; Mon, 25 Feb 2019 18:18:56 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([]) by localhost (mail.smeinc.net []) (amavisd-new, port 10026) with ESMTP id osSrB-WjwTXv for <tools-development@ietf.org>; Mon, 25 Feb 2019 18:18:55 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-108-45-137-105.washdc.fios.verizon.net []) by mail.smeinc.net (Postfix) with ESMTPSA id 5DFFD300250; Mon, 25 Feb 2019 18:18:55 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Message-Id: <24D08941-8016-40B9-A223-C646C2B3EC9C@vigilsec.com>
Date: Mon, 25 Feb 2019 18:37:11 -0500
Cc: IETF Tools Development <tools-development@ietf.org>
To: Portia Wenze-Danley <pwdanley@ietf.org>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/iQV0nIyHpEgZ7OmkXbg_tRmzVF8>
Subject: [TOOLS-DEVELOPMENT] Idea about the IDIQ
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: Mon, 25 Feb 2019 23:37:17 -0000


I have an idea.  Tell me if you like it or not.

We could add to the cover that any responder to this RFP should indicate whether they are also interested in becoming an IDIQ contractor, and that we will use this projects response as the example rather than the one currently pointed to in the outstanding IDIQ RFP.

I would think that the winning bidder is qualified, so they should be added to the IDIQ pool if they are interested.  Also, the other bidders can be evaluated for possible addition to the IDIQ pool.