Our process for RFPs is as follows:
- The RFP is publicly issued, posted to this page and announced to the RFP Announcement Mailing List, which anyone can subscribe to.
- Potential bidders have until (issue date + 2 weeks) to submit any questions by email to firstname.lastname@example.org. Questions will be treated as anonymous but not private, as explained below. If you do not receive confirmation that your questions have been received within 24 hours then please resend until you do.
- A written response to all questions is provided on or before (issue date + 3 weeks), direct to those parties that sent questions, by email to the RFP Announcement Mailing List and posted on this page. The response will include the questions asked and the answers, but will not identify the company asking the question. If required, the RFP may be updated to correct or clarify any issues identified.
- Bids are due by (issue date + 4 weeks) by email to email@example.com. If you do not receive confirmation that your bid has been received within 24 hours then please resend until you do. The bid should include the following information:
- Executive summary
- Project approach including any assumptions.
- Project plan and schedule including when the work will begin and end, and any other milestones, as well as any dependencies that may delay delivery.
- Fee and payment schedule. Fixed priced bids are preferred but if that is not possible then a maximum fee must be specified.
- Warranty including a proposal for fee reduction/refund due to late- or non-delivery
- The IETF Administration LLC and designated contractors and volunteers will select a preferred bid and notify the bidder by (issue date + 6 weeks). The selection process may include questions by email and/or conference call.
- The IETF Administration LLC then enters into contract negotiation with the preferred bidder, based on its standard contract and using the relevant sections of the Statement of Work below. If contract negotiation fails then a different preferred bidder may be chosen.
- Contract negotiation is anticipated to complete by (issue date + 8 weeks) and result in the award of the contract. All RFP contract awards are posted on this page and announced to the RFP Announcement Mailing List. The terms of the contract are later posted publicly on this page, with the fee information and signatures (where possible) redacted. In addition any Conflict of Interest declarations required of the preferred bidder are also posted publicly on our website. This transparency is non-negotiable.
- Work generally begins immediately after award of the contract, unless specified otherwise in the Statement of Work or negotiated contract.
The table below lists all RFPs issued by the IETF LLC. Please note the following:
- RFPs that are still open have "OPEN" in the Vendor/Contract columns
- Not all RFPs have a Q&A
- Award links to the announcement of the award of the contract. Not all awards have been announced but all will be in future.
- Contracts are posted with financial information and signatures (where possible) redacted.
- The conflict of interest (COI) form posted is required of all contractors by IETF LLC Policy. Where the contract was completed before this policy came into place, no COI form was requested.Trac and Subversion migration to GitHub RFP
- For RFPs posted before the creation of the IETF LLC, please see the archived IAOC site.
|May 31, 2021||Author tools web services re-implementation||RFP|
|May 17, 2021||Trac and Subversion migration to GitHub||RFP||CLOSED|
|May 3, 2021||Trac wiki migration to Wiki.js||RFP|
|May 3, 2021||BibXML Service||RFP||CLOSED|
|July 16, 2020||Review of current landscape of IETF document processing tools||RFP||Not awarded||Not awarded|
|June 29, 2020||Reimplementing IETF Website Wagtail templates||RFP|
|February 5, 2020||Security Review and Remediation of the RFC Production Center Web Accessible Code||RFP|
|October 4, 2019||Temporary RFC Series Project Manager||RFP|
|September 27, 2019||Security Review and Remediation of the RFC Production Center Web Accessible Code||RFP|
|Not awarded||Not awarded|
|September 13, 2019||Automatic Schedule Builder||RFP||DashCare B.V.||Award|
|August 30, 2019||Tools Support (3 components)||RFP|
|1. Minor Tools Enhancements||Painless Security||Award|
|2. YANG Catalog Maintenance||PANTHEON.tech s.r.o||Award|
|3. Tools Maintenance||Elf Tools|
|June 24, 2019||Secretariat Services (4 components)||RFP|
|1. CPA Financial Services||GRF CPAs & Advisors||Award|
|2. All other components||Association Management Solutions||Award|
|April 30, 2019||IRSG Ballots Tool||RFP|
|April 8, 2019||RFC Errata Merge Tool||RFP|
|Soaring Hawk Consulting|
|February 28, 2019||Datatracker Meeting Application Improvements||RFP||IOLA||Contract|
|January 23, 2019||YANG Catalog Conversion||RFP||PANTHEON.tech s.r.o||Contract|
Long-Standing Service Contracts
The IETF LLC has a number of long-standing service contracts, which predate the formation of the LLC.
|RFC Production Center||Association Management Solutions||Contract|
|Meeting Network Services||Linespeed||Contract||COI|
|Meeting Remote Participation Services||Meetecho||Contract 2018|
|Legal Services (General)||Biddle Law||COI|
|Legal Services (Litigation and Privacy)||Thompson Hine||COI|
The IETF LLC has a small number of special contracts which are not subject to our normal contracting process and not subject to our COI disclosure requirements.ICANN-IETF Supplemental Agreement 2021
|IANA||The Internet Assigned Numbers Authority (IANA) administers many parameters of IETF protocols. The Internet Corporation for Assigned Names and Numbers (ICANN) provides these services to the Internet community through an arrangement with Public Technical Identifiers (PTI).||Original MoU (2000)|
Legal contracts with the Internet Society (ISOC) can be found on the LLC overview.