RFC 9745 on The Deprecation HTTP Response Header Field
rfc-editor@rfc-editor.org Mon, 17 March 2025 11:09 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 E1BCBCED69A; Mon, 17 Mar 2025 04:09:17 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id A06AE1C5D8E; Mon, 17 Mar 2025 04:09:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9745 on The Deprecation HTTP Response Header Field
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250317110917.A06AE1C5D8E@rfcpa.rfc-editor.org>
Date: Mon, 17 Mar 2025 04:09:17 -0700
Message-ID-Hash: PWZGCTDLMBA5BPL3GYPWQRSMYQMRYH4N
X-Message-ID-Hash: PWZGCTDLMBA5BPL3GYPWQRSMYQMRYH4N
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, drafts-update-ref@iana.org, httpapi@ietf.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/yp8CnddvLjkhMQDIiUdi44EThck>
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>
A new Request for Comments is now available in online RFC libraries.
RFC 9745
Title: The Deprecation HTTP Response Header Field
Author: S. Dalal,
E. Wilde
Status: Standards Track
Stream: IETF
Date: March 2025
Mailbox: sanjay.dalal@cal.berkeley.edu,
erik.wilde@dret.net
Pages: 8
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-httpapi-deprecation-header-09.txt
URL: https://www.rfc-editor.org/info/rfc9745
DOI: 10.17487/RFC9745
The Deprecation HTTP response header field is used to signal to
consumers of a resource (identified by a URI) that the resource will
be or has been deprecated. Additionally, the deprecation link relation
can be used to link to a resource that provides further information about
planned or existing deprecation. It may also provide ways in which
client application developers can best manage deprecation.
This document is a product of the Building Blocks for HTTP APIs Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team