Re: Changes to the way we manage RFPs

Bob Hinden <bob.hinden@gmail.com> Wed, 26 February 2020 05:01 UTC

Return-Path: <bob.hinden@gmail.com>
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 73B7F3A0D2A; Tue, 25 Feb 2020 21:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 492VLiOUAFpE; Tue, 25 Feb 2020 21:01:11 -0800 (PST)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8DC03A0D29; Tue, 25 Feb 2020 21:01:11 -0800 (PST)
Received: by mail-pf1-x431.google.com with SMTP id s1so797634pfh.10; Tue, 25 Feb 2020 21:01:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=XPXJpWvu698mpcAXmogLsKPgkB2+XBy5d48c5nps5O8=; b=sxauROUU6jsRRe37Z8N+GSXmZ6ifxl9Yq6thx/s0cA6QDYzlIbjoE8ylhCTEb1LGHC zOrW9wmOeDSkaNOT30vSebAqKjX+R+3HWCxjhSUcmSlacVm/7JZgJd/jv/EIk2KGwky+ UH2FzjkVarCMq0TyseEv91ipvhZ0EMK1Gt8C3rm1/X9k6Q5Q5vEZuZ4povQbaAbHvT0v /LqGzbztWlnU0BfjwpVdjHOntoB6ox25EfcJEnDT7NxpUiR20VoqRPqcHm/w42yzLxwj EPMuqQegUTB3r4SRYN4fP4Yv+BO6iZf3UiT8AfSd1YW/to6+yVGgtRpPiwG9FMwy++JL LrvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=XPXJpWvu698mpcAXmogLsKPgkB2+XBy5d48c5nps5O8=; b=hg0npbBEOSBKFvrItpXFTi4XDfaSpulIMIA5WEkUdKIGOSWDlnQO49dfm8GDOG0GH8 yjEtCGFLAnug5jzGVeGTeHPzzAWfQ5ov5JkalMZTFSF4p2d9s0tgeb8h57VeKak2zlW9 J2Tg2wPBu1Bqq7MluzGrQtcWUQLkmBLoVpUDicS+MH9YFqN9mTIZVijO4dHAcQzdl3EF 2bTJRQP1YVMk6xRmQHKRSh1uKmM0+Biw0ixhvuhrlvus60NwJ0M3KhZdvPMAvDAmMNn6 GKEKOP/WJmK5XndKJeHg5Ay+G0DeUBLmKalSdrW9kvhnjkrj7ZYTgKa+ri4Ou6HTxJ+q Qfgw==
X-Gm-Message-State: APjAAAUhdun1EOP9zAW4QRVn7Lb98eS0ZEmyWmn105T0ddsuGawb2J+U yI0rhj+ovwkSsseXFLfB465/OhwR/E4=
X-Google-Smtp-Source: APXvYqxb2OfNRBWBaQjxw4LIeEGq4kV5j+2jwpaSHyHF+19oWTacvMf+uhuM3CYUokLnzPAxB5cVSg==
X-Received: by 2002:a63:d10c:: with SMTP id k12mr1918430pgg.392.1582693270769; Tue, 25 Feb 2020 21:01:10 -0800 (PST)
Received: from [10.52.7.85] (rrcs-67-52-140-11.west.biz.rr.com. [67.52.140.11]) by smtp.gmail.com with ESMTPSA id d2sm777056pjv.18.2020.02.25.21.01.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Feb 2020 21:01:09 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <908BCE29-8F0B-4451-B25F-A318B967EBC0@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1D6897F0-80C8-474E-AA0F-A5E829681D7B"; 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: Tue, 25 Feb 2020 21:01:08 -0800
In-Reply-To: <158268693548.11166.3290940777172353007.idtracker@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: Jay Daley <jay@ietf.org>
References: <158268693548.11166.3290940777172353007.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nirvUAKKnwQa9HrEpdO4f6kPhP8>
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 05:01:15 -0000

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.

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