Files replaced: RFC 9796 on SIP Call-Info Parameters for Rich Call Data
rfc-editor@rfc-editor.org Fri, 08 August 2025 18:58 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 9E56A51D0D32; Fri, 8 Aug 2025 11:58:55 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 6A433267CC0; Fri, 8 Aug 2025 11:58:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Files replaced: RFC 9796 on SIP Call-Info Parameters for Rich Call Data
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250808185855.6A433267CC0@rfcpa.rfc-editor.org>
Date: Fri, 08 Aug 2025 11:58:55 -0700
Message-ID-Hash: ZLADUAPH325XRBDGP2BTG4ENJALPCZTM
X-Message-ID-Hash: ZLADUAPH325XRBDGP2BTG4ENJALPCZTM
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/UWy_3zcqWGVWCnqlaF69L182grE>
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>
During the publication of RFC 9796 on 10 July 2025, the "not prepped" XML file and its outputs, rather than the "prepped" file and its outputs, were mistakenly placed in the public repository even though the "prepped" files had been generated. Here, "prepped" refers to having made automated changes to the RFCXML in order to support the archival nature of RFCs. (See [1] and [2] for more information.) The RPC has corrected this error by replacing the "not prepped" files with the "prepped" files. There is no difference in the semantic content of the files. The original publication announcement for this RFC is [3]. [1] https://www.rfc-editor.org/faq/#notprepped [2] https://authors.ietf.org/en/rfcxml-overview#the-prep-tool [3] https://mailarchive.ietf.org/arch/msg/rfc-dist/SFVYjy-1vKBwt5Jk9QDke6jI4mM/ The RFC Editor Team