Evolving how RFCs are edited and published - Deferred
rfc-editor@rfc-editor.org Tue, 12 May 2026 16:05 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E68EDED344D0; Tue, 12 May 2026 09:05:38 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id D59852BAAC6; Tue, 12 May 2026 09:05:38 -0700 (PDT)
To: ietf-announce@ietf.org
Subject: Evolving how RFCs are edited and published - Deferred
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260512160538.D59852BAAC6@rfcpa.rfc-editor.org>
Date: Tue, 12 May 2026 09:05:38 -0700
Message-ID-Hash: GEQ624J5IBCZXM2VZLZDRGYKRX45CX2W
X-Message-ID-Hash: GEQ624J5IBCZXM2VZLZDRGYKRX45CX2W
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/fmv7HWmbtjok1xFXa5z8RKtzuys>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
Launch of the new tools for editing and publishing RFCs originally anticipated for tomorrow (13 May) is being deferred until the week of 18 May. In preparing for deployment, a gap in Datatracker -- which is tightly integrated into the new RPC workflow -- was discovered. The Tools Team is working now to close that gap this week ahead of the launch. Please send questions and comments to rfc-interest@rfc-editor.org. RFC Editor and the IETF Tools Team