Re: Changes to the way we manage RFPs

Brian E Carpenter <> Wed, 26 February 2020 03:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E619C3A0BDD; Tue, 25 Feb 2020 19:56:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jF4sNSwMlZiu; Tue, 25 Feb 2020 19:56:09 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DF15A3A0BD9; Tue, 25 Feb 2020 19:56:07 -0800 (PST)
Received: by with SMTP id e9so689793pjr.4; Tue, 25 Feb 2020 19:56:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=1GA2SspyLNfDJWjM74ppNKRpenY6OyHfUC4PhJFycmA=; b=YwFMlLk31KSdYI7jvtL7L5ATFY2oxPY5UQc4KDGc0ousydv2e0QGBe4bAa6WqtHAYp NVDOBq2LQM1Jpldb+/L+Ls9irQ7Iy+a4aD20zAvgviey6wKGza703nD/NPiAwCrfYmgs pV2yse74ADTiYwnhPGtpPARkUMVeCQoXk7z2913EVSUpeabmvLEUIjuc6gnGRkpx/odV Wa6amxJMaqGhqCQPr/QJpSvRKuZJ/fx8BLe1PoIMUT2dkpxIdiwA8rI+MrO2SCVTzDl9 m40Up8Wi1Kh/cMvo5jbpSIhg5+mTe/NDYL12kd3qQ78VrDDUXUQe8UfZgB0ajxHHbf7R 1biA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=1GA2SspyLNfDJWjM74ppNKRpenY6OyHfUC4PhJFycmA=; b=q7F5yCPGVMx/327vqBQI0Y9T6y1Y0YYvS51I8sCCUpb4f9JzlScA5VZZ3CuKNo+CKP 4QPNNFIHH8FAhMLQ7ePFsOWOne1oxoSQ+DQGoI0GUG4XCUvm5bfVuYNLIVO1pfeLOh0s LhDOkXZEqvNcAdLcYur5JKo99dM9Wu+tv5d8LhcDQT3XEzA3eBYSzf2joNeeoz6jfLgb 8JVTmTIL8z2OMunkNpNUw616jF0gJIw64DZIg1wFh3QwN/6p223Cm1t5jke6snfvhcLm 6PswB2kftZNNYFMKYozM57rcNXGmsaIvgsAdN2YDPTAWDKWRkpfvWp6sii9qd0jJVQBE 8v1Q==
X-Gm-Message-State: APjAAAWfXEp72Zx8xn6SNbzG70tTEp5VFuM6P0qjlvZWwQHxbT4Sd3fk DKAKwcUvgIj6Eb2nTgkAKBbFnuy4
X-Google-Smtp-Source: APXvYqwzucHxnCj2TnEEYaWY16p/e/GpnYZIK09HitAXcY3iDRd2HkK8+9HuiIlqONYNR8GiaKIUrg==
X-Received: by 2002:a17:902:426:: with SMTP id 35mr1932517ple.176.1582689366811; Tue, 25 Feb 2020 19:56:06 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id c1sm621692pfa.51.2020. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Feb 2020 19:56:06 -0800 (PST)
Subject: Re: Changes to the way we manage RFPs
To: IETF Executive Director <>
References: <>
From: Brian E Carpenter <>
Message-ID: <>
Date: Wed, 26 Feb 2020 16:56:02 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 26 Feb 2020 03:56:11 -0000

Hi Jay,

I fully understand the arguments for this change. However, I think it would be good to continue to send a *summary* of the CFP messages to ietf-announce, for community awareness. Ditto for the "Award of contract" messages.

If I see "RFP for IETF Cookie services" or "Award of contract for IETF Cookie services" and I care, then I can go and look for more.


On 26-Feb-20 16:15, IETF Executive Director 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] 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.
> [1]
> [2]
> [3]