Re: Changes to the way we manage RFPs

Jay Daley <jay@ietf.org> Wed, 26 February 2020 06:17 UTC

Return-Path: <jay@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A9CD3A0E6A for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2020 22:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 U8E8WjhmuQJg; Tue, 25 Feb 2020 22:17:13 -0800 (PST)
Received: from [192.168.1.49] (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id D5D183A0E66; Tue, 25 Feb 2020 22:17:12 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Jay Daley <jay@ietf.org>
Mime-Version: 1.0 (1.0)
Subject: Re: Changes to the way we manage RFPs
Date: Wed, 26 Feb 2020 19:17:10 +1300
Message-Id: <50C32A6F-3B30-4665-936A-6C411F9A8853@ietf.org>
References: <397FF897-441C-41A7-8C74-F667C232BC64@ietf.org>
Cc: IETF <ietf@ietf.org>
In-Reply-To: <397FF897-441C-41A7-8C74-F667C232BC64@ietf.org>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: iPad Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PWm7IzvqzN1I4qhPSrbMZEmrofo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2020 06:17:15 -0000

I’m sorry, using mobile devices accurately is defeating me today  - I meant “useful for me to understand why subscribing to rfp-announce is not an option”

-- 
Jay Daley
IETF Executive Director

> On 26/02/2020, at 7:10 PM, Jay Daley <jay@ietf.org> wrote:
> 
> Bob
> 
> 
>> On 26/02/2020, at 6:01 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>> 
>> Jay,
>> 
>>>> On Feb 25, 2020, at 7:15 PM, IETF Executive Director <exec-director@ietf.org> wrote:
>>> 
>>> The IETF Administration LLC is changing the way we manage RFPs.  These changes are part of a larger overhaul that will see further changes come in future.  The changes being made today are:
>>> 
>>> 1. As of next week, we will be using a new RFP Announcement Mailing List [1] rfp-announce@ietf.org for all announcements relating to RFPs and stop using IETF-Announce.  This change is intended to help us reach a wider network of potential vendors, both directly through a lower volume, more focused list and indirectly through automated redistribution of issued RFPs.
>> 
>> This sounds fine to me, I agree it isn’t reasonable to ask potential bidders to watch the ietf-announce list for RFPs.   That said, I think there is value to also cc: the ietf-announce list, doing that would improve transparency.    For example, I have no plans to subscribe to an rfp-announce list, but I do read the ietf-announce list.
> 
> As I said to Brian, it would be useful for me to understand why subscribing to rfp-announce - did I just need to make it clearer that this is a zero sum change as far as email volume goes?
> 
> My concern btw is the lack of a clear principle that decides what gets copied to ietf-announce and why (assuming you don’t mean everything that goes to rfp-announce). 
> 
> Jay
> 
>> 
>> Bob
>> 
>> 
>>> 
>>> 2. We have a new formal process for managing RFPs, published on the RFPs page [2].
>>> 
>>> 3. The RFPs page [2] now includes links to the all of the contracts for RFPs issued by the LLC.  These have the financial informaton redacted and where possible, signatures also redacted.
>>> 
>>> 
>>> Planned changes include:
>>> 
>>> * Publishing vendor Conflict of Interest (COI) forms, once reviewed by the LLC Board.
>>> 
>>> * Publishing contract templates and non-negotiables (e.g. contract transparency) to allow vendors to study them before bidding.
>>> 
>>> * Engaging the community on the principles and processes we use for managing RFPs and what is and isn't appropriate for us to expect in our contracts.
>>> 
>>> * We will also investigate implementing some elements of the Open Contracting Data Standard [3]
>>> 
>>> 
>>> Please feel free to contact me directly if you have any questions or feedback.
>>> 
>>> [1] https://www.ietf.org/mailman/listinfo/rfp-announce
>>> [2] https://www.ietf.org/about/administration/rfps/
>>> [3] https://www.open-contracting.org/data-standard/
>>> 
>>> --
>>> Jay Daley
>>> IETF Executive Director
>>> exec-director@ietf.org
>>> 
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>