Re: Changes to the way we manage RFPs

Bob Hinden <> Wed, 26 February 2020 15:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0FEC73A091C; Wed, 26 Feb 2020 07:11:33 -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 39T4wJOviKBR; Wed, 26 Feb 2020 07:11:31 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C99813A091B; Wed, 26 Feb 2020 07:11:30 -0800 (PST)
Received: by with SMTP id y17so3466557wrn.6; Wed, 26 Feb 2020 07:11:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Ya7gcBLFz3v1hOU/HTMc9JYAsxL26ff23CHuhscwD+Y=; b=toz+2sbMh53bm+1Vd3YeRI0tZI9+QnUOSjsSG3R9/Y8AhRWUZY6qGFd2zya9Di6il+ 1j/dGqEr4h/ZTlbSfLzCP8WSzVYnE+6Bf3IJkUjv72cLakmZO2xN57grnpQUeuOTGTGO DF2hxQF3OSOUjsBlH52W2L1FHIdRAYAelVQdYBe2zHUH8hMfPmxOsbJQ72oCMqXc8UUs FWJCh3EP1Y6FLq5RVlgaawgtd99VVSlOkfYGymyLJ6EIL8F0LKIhIqlHLQP5gPkTD1FK U9aUw4uFf0P5I78UoPYFyZxQOcPJTPyyTiDhKzv8uYi+LFcIu/FTzeuLcURXxJ07S5dp fj3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Ya7gcBLFz3v1hOU/HTMc9JYAsxL26ff23CHuhscwD+Y=; b=r8nIYZOGJ1zSuQUEIM6YGqQRK4BPuqPAhFvfE7BQjc26DnYaCE8oyUoMnx4uV2HtEd ENM2uJem32Q+S6/A+kvf9zWz4L/YpfujLlGRdfSqo3tojMgZi6Fn71ClMOdl7iJD1inY Rv4U1qpJWcN3KDO5nfKSxW0aJK/XJpfSvq/FLIv7Tjv1uTJCen+myTn6fL8FtfB8c2i6 gA5iu1PqPqfPCJR+dQcc1myackN/MQxLTshkkAoBAKSJmGK+q4Lzf6lvHjbK0npooOcE Sh0p33C+lBPBcWBs+vMXngDjyyF+UJRcuxQRBuoWYKoZY7N3kLejHmuMmGSuMkAZYYTX HR0Q==
X-Gm-Message-State: APjAAAXgWUtz7V6UcIramIIjqO7wPyYdx7SSnqE3v+4Zw7mfy4tyBxS9 8jUV3W2UUK6/yaao2mKIGHgdyQYo
X-Google-Smtp-Source: APXvYqw9ipD+wlACVyZ3DQQh60hvyEk/FLMsdHnYs2z+ftGHPisqQ7uHj5n0KF3B8Tdnbm8xDVZiyw==
X-Received: by 2002:adf:e542:: with SMTP id z2mr6392922wrm.150.1582729888618; Wed, 26 Feb 2020 07:11:28 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id j20sm3637269wmj.46.2020. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Feb 2020 07:11:27 -0800 (PST)
From: Bob Hinden <>
Message-Id: <>
Content-Type: multipart/signed; boundary="Apple-Mail=_A0DEEE11-6E90-4B25-8C18-A6C0698415C6"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Changes to the way we manage RFPs
Date: Wed, 26 Feb 2020 07:11:21 -0800
In-Reply-To: <>
Cc: Bob Hinden <>, IETF <>
To: Jay Daley <>
References: <> <>
X-Mailer: Apple Mail (2.3445.104.11)
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 15:11:33 -0000


> On Feb 25, 2020, at 10:09 PM, Jay Daley <> wrote:
> Bob
>> On 26/02/2020, at 6:01 PM, Bob Hinden <> wrote:
>> Jay,
>>> On Feb 25, 2020, at 7:15 PM, 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.
>> 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?

I was assuming that the people who would subscribe to the rfp-announce list were people who might want to bid on IETF work.   I also assume the reason to create a separate list was for the people who were interested in bidding, but who didn’t care about other  things like what RFCs were published.

I am not planning to bid on any IETF RFPs.   I would still like to follow what is being put out to bid and what contracts were awarded.   I think copying the larger group would make the bidding process visible to a larger group of IETFers.

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

My answer to that is things that are of general interest to the IETF should be sent to the IETF-announce list.   This includes RFP and contract awards.

Is there a reason to not copy these emails to ietf-announce?   I note it might result in more bids as they would reach a larger audience.

Hope this helps.


> 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]
>>> [2]
>>> [3]
>>> --
>>> Jay Daley
>>> IETF Executive Director
>>> _______________________________________________
>>> IETF-Announce mailing list