[Rfp-announce] RFI for Infrastructure Services

IETF Executive Director <exec-director@ietf.org> Tue, 07 February 2023 14:17 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: rfp-announce@ietfa.amsl.com
Delivered-To: rfp-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02025C187980 for <rfp-announce@ietfa.amsl.com>; Tue, 7 Feb 2023 06:17:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf-org.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XREcwDsSvWT8 for <rfp-announce@ietfa.amsl.com>; Tue, 7 Feb 2023 06:17:18 -0800 (PST)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C0F1C151719 for <rfp-announce@ietf.org>; Tue, 7 Feb 2023 06:17:18 -0800 (PST)
Received: by mail-wr1-x431.google.com with SMTP id h16so13673024wrz.12 for <rfp-announce@ietf.org>; Tue, 07 Feb 2023 06:17:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-org.20210112.gappssmtp.com; s=20210112; h=to:cc:date:message-id:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=KTRUbZ2ugOJjzu0/PO+NIlZbiB8ozhGDxVvUkxZkj5s=; b=IT8NlYFbMWiEniLPJ7oCoYLi3aX/kSzC8tZVmBAqMdpaXlnIuYV/jXwnTVq9NC71Id Kd2SmkkwamtYnV7K4MBfG0I/I8zlgzkYwIE4d26uZMQYqe/tMw78EFXM38RGY4C1yRcb f6NCTgE7z2DBuhUuAdYT/7AGs8Qm5zXaQdzWRMLUsCWAmf5QDlolE7ClytpaBe4mX/yL KtpXjxzRMLGBIhxgwU2netLTmNDCm1on0VsxIZImAIgVJ/xe5xAK+ht3XhN6ttctSmt8 VfCpgQKf9Z8vp3nMVaSFC36jHvPLMqn4zhLUtv8+6gUYr/C3k82lG2JKcbHtq2E5gwus GtLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:cc:date:message-id:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=KTRUbZ2ugOJjzu0/PO+NIlZbiB8ozhGDxVvUkxZkj5s=; b=MvDfM7ZwuzOY05rqCi8eXIOokXY4p3n+kp4/IztJwALFeniL/x5IqnwXzzWtUBzqCS MGUs9XaZm0UnkutArkgHPnJyFkaA3OK8LYoNTf7SPhZk1kuWkGeyYYFVtmkPqmfT3it6 0zgyHVE6ep0BTp1TdNY/smOwLaU+pSjpPJedAo7pjRmxC+jJaUi08lZtmjCghXrImgd+ zXWjIdOdrdPEm+Rr+JGUCAAm8o8lF0x4pfZjx/X896X5XOsYOuUsF2fB1qQ1U9C/Vc6/ Bx0HHhugOMuzncQR2h29ZKKcJvY1rutzuoGJ5Xwm8k7KsdP5MvgBgn0HDbCClqDWqu8H lEpw==
X-Gm-Message-State: AO0yUKWoPalYYGBG6+168Q8+0pBbhHR4dtoxaeTC7rDTt/XgvCwnX+CD 8wfuSDMuNq4WuLpooYTZwcqZEqBl6a531YTjVuZ+2w==
X-Google-Smtp-Source: AK7set/P+f2l9MBqlrdBOsXpQazuXuLci23gKBh2nU323J6Dv6b7k97YAdDtMItZhyS08rQhEvjovw==
X-Received: by 2002:adf:f145:0:b0:2c3:ee0d:563 with SMTP id y5-20020adff145000000b002c3ee0d0563mr3154146wro.28.1675779435877; Tue, 07 Feb 2023 06:17:15 -0800 (PST)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id p14-20020a5d68ce000000b002c3da499290sm10285000wrw.84.2023.02.07.06.17.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2023 06:17:10 -0800 (PST)
From: IETF Executive Director <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
Message-Id: <BD673CE2-11EC-404A-9E24-DBD52254C4DF@ietf.org>
Date: Tue, 07 Feb 2023 14:16:58 +0000
Cc: IETF Announcement List <ietf-announce@ietf.org>
To: rfp-announce@ietf.org
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfp-announce/O1YERF19sEEnnDF4N17131yrsDQ>
Subject: [Rfp-announce] RFI for Infrastructure Services
X-BeenThere: rfp-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Announcement of IETF RFPs <rfp-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfp-announce>, <mailto:rfp-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfp-announce/>
List-Post: <mailto:rfp-announce@ietf.org>
List-Help: <mailto:rfp-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfp-announce>, <mailto:rfp-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2023 14:17:23 -0000

The IETF Administration LLC is soliciting information to inform planned RFPs for Infrastructure Services


Overview:

The current contract for IETF IT infrastructure services is a black box contract - we specify the systems to be maintained along with a very basic SLA, and the provider is responsible for the underlying infrastructure on which those systems operate, including the system administration strategy. The provider has always been much more accommodating than that in responding to requests for changes inside the black box, but these requests were for a long time piecemeal and not part of an overall strategy.

There have been regular complaints from the community that our infrastructure is more prone to failure, more difficult to upgrade and more difficult to accommodate new services, compared to a modern best practice infrastructure.  The IETF Administration LLC has consulted with the community on the best way to address this and worked with the community to develop a new operational strategy for how the infrastructure should be operated.

The IETF intends to issue one or more RFPs for a service provider to migrate and manage our infrastructure services in line with this new strategy, but before doing there are a number of decisions to be made on how those RFPs are to be structured.  This document is a Request For Information to help the IETF make these decisions and issue high quality RFPs.

Timeline:

07 February 2023	This RFI Issued
26 February 2023	This RFI closes


Full details of the RFI, including instructions on how to respond, can be found at https://www.ietf.org/media/documents/IETF_Infrastructure_Services_RFI.pdf

More information on our RFP and Contracts can be found at https://www.ietf.org/about/administration/rfps-and-contracts/

Please note that in order to maintain a fair and transparent RFI process, all questions or feedback regarding this RFI should be made to the email address specified in the RFI.

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org