The Sunset HTTP Header Field
draft-wilde-sunset-header-09
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Active Internet-Draft (individual in art area) | |
| Last updated | 2018-12-29 (latest revision 2018-11-29) | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Mark Nottingham | ||
| Shepherd write-up | Show (last changed 2018-11-29) | ||
| IESG | IESG state | Approved-announcement to be sent::Point Raised - writeup needed | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alexey Melnikov | ||
| IESG note |
Checking with HTTPBIS whether there are any objections to publish. It is not clear whether this document needs to be Proposed Standard, Informational would suffice for a header field registration. |
||
| Send notices to | Mark Nottingham <mnot@mnot.net> | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
Network Working Group E. Wilde
Internet-Draft December 29, 2018
Intended status: Informational
Expires: July 2, 2019
The Sunset HTTP Header Field
draft-wilde-sunset-header-09
Abstract
This specification defines the Sunset HTTP response header field,
which indicates that a URI is likely to become unresponsive at a
specified point in the future. It also defines a sunset link
relation type that allows linking to resources providing information
about an upcoming resource or service sunset.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 2, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Wilde Expires July 2, 2019 [Page 1]
Internet-Draft Sunset Header December 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Temporary Resources . . . . . . . . . . . . . . . . . . . 3
1.2. Migration . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Retention . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4. Deprecation . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. The Sunset HTTP Response Header Field . . . . . . . . . . . . 4
4. Sunset and Caching . . . . . . . . . . . . . . . . . . . . . 5
5. Sunset Scope . . . . . . . . . . . . . . . . . . . . . . . . 5
6. The Sunset Link Relation Type . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7.1. The Sunset Response Header Field . . . . . . . . . . . . 7
7.2. The Sunset Link Relation Type . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
10.1. Normative References . . . . . . . . . . . . . . . . . . 9
10.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
As a general rule, URIs should be stable and persistent, so that
applications can use them as stable and persistent identifiers for
resources. However, there are many scenarios where for a variety of
reasons, URIs have a limited lifetime. In some of these scenarios,
this limited lifetime is known in advance. In this case, it can be
useful for clients if resources make this information about their
limited lifetime known. This specification defines the Sunset HTTP
response header field, which indicates that a URI is likely to become
unresponsive at a specified point in the future.
This specification also defines a link relation type "sunset" that
allows to provide information about a resource's or a service's
sunset policy, and/or upcoming sunsets, and/or possible mitigation
scenarios for resource/service users. This specification does not
place any constraints on the nature of the linked resource, which can
be targeted at humans, at machines, or a combination of both.
Possible scenarios for known lifetimes of resources include, but are
not limited to the following scenarios.
Wilde Expires July 2, 2019 [Page 2]
Internet-Draft Sunset Header December 2018
Show full document text