Brian (sent from my > On 26/02/2020, at 4:56 PM, Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote: > > 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. Those are two of the three types of RFP message sent to IETF-announce and coincidentally two of the three types planned for rfp-announce (the third one being “Here’s the Q&A for this RFP”). In other words, I don’t want rfp-announce to grow on volume. It would useful for me to understand why subscribing to rfp-announce is not an option? In the context of the IETF’s high usage of mailing lists, this seems like a particularly low barrier to entry. Jay -- Jay Daley IETF Executive Director +64 21 678840 > > 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. > > Regards > Brian > >> 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] rfp-announce@xxxxxxxx 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] https://www.ietf.org/mailman/listinfo/rfp-announce >> [2] https://www.ietf.org/about/administration/rfps/ >> [3] https://www.open-contracting.org/data-standard/ >> >
