Changes to the way we manage RFPs

IETF Executive Director <> Wed, 26 February 2020 03:15 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 85DFE3A0B15 for <>; Tue, 25 Feb 2020 19:15:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Executive Director <>
To: "IETF Announcement List" <>
Subject: Changes to the way we manage RFPs
X-Test-IDTracker: no
X-IETF-IDTracker: 6.118.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 25 Feb 2020 19:15:35 -0800
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 26 Feb 2020 03:15:36 -0000

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] 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.  

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.


Jay Daley
IETF Executive Director