[httpapi] Last Call: <draft-ietf-httpapi-deprecation-header-05.txt> (The Deprecation HTTP Header Field) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Fri, 23 August 2024 15:25 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: httpapi@ietf.org
Delivered-To: httpapi@ietfa.amsl.com
Received: from [10.244.2.19] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id BFCF5C14F5E7; Fri, 23 Aug 2024 08:25:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.22.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <172442671239.127588.8133983778126810167@dt-datatracker-584cd6c8dd-fvr2f>
Date: Fri, 23 Aug 2024 08:25:12 -0700
Message-ID-Hash: KV3JD7PXK4HWD27E75TWFT7AZBS6M7UT
X-Message-ID-Hash: KV3JD7PXK4HWD27E75TWFT7AZBS6M7UT
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-httpapi-deprecation-header@ietf.org, francesca.palombini@ericsson.com, httpapi-chairs@ietf.org, httpapi@ietf.org, rsalz@akamai.com
X-Mailman-Version: 3.3.9rc4
Reply-To: last-call@ietf.org
Subject: [httpapi] Last Call: <draft-ietf-httpapi-deprecation-header-05.txt> (The Deprecation HTTP Header Field) to Proposed Standard
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/8aH-oC5-cqI0Svr9q8Qku6O3sCA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Owner: <mailto:httpapi-owner@ietf.org>
List-Post: <mailto:httpapi@ietf.org>
List-Subscribe: <mailto:httpapi-join@ietf.org>
List-Unsubscribe: <mailto:httpapi-leave@ietf.org>
The IESG has received a request from the Building Blocks for HTTP APIs WG (httpapi) to consider the following document: - 'The Deprecation HTTP Header Field' <draft-ietf-httpapi-deprecation-header-05.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2024-09-06. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The Deprecation HTTP response header field is used to signal to consumers of a resource (in the sense of 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 additional information about planned or existing deprecation, and possibly ways in which clients can best manage deprecation. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-httpapi-deprecation-header/ No IPR declarations have been submitted directly on this I-D.
- [httpapi] Last Call: <draft-ietf-httpapi-deprecat… The IESG
- [httpapi] Re: Last Call: <draft-ietf-httpapi-depr… Salz, Rich
- [httpapi] Re: Last Call: <draft-ietf-httpapi-depr… Julian Reschke
- [httpapi] Re: Last Call: <draft-ietf-httpapi-depr… Mark Nottingham
- [httpapi] Re: Last Call: <draft-ietf-httpapi-depr… Julian Reschke
- [httpapi] Re: Last Call: <draft-ietf-httpapi-depr… Sanjay Dalal