The Sunset HTTP Header
draft-wilde-sunset-header-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-08-03
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           E. Wilde
Internet-Draft                                               UC Berkeley
Intended status: Standards Track                          August 3, 2015
Expires: February 4, 2016

                         The Sunset HTTP Header
                      draft-wilde-sunset-header-00

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.

Note to Readers

   This draft should be discussed on the apps-discuss mailing list [1].

   Online access to all versions and files is available on github [2].

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 http://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 February 4, 2016.

Copyright Notice

   Copyright (c) 2015 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
   (http://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

Wilde                   Expires February 4, 2016                [Page 1]
Internet-Draft                Sunset Header                  August 2015

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The Sunset HTTP Response Header . . . . . . . . . . . . . . .   3
   4.  Sunset and Caching  . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  The Sunset Response Header  . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Non-Normative References  . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

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 some point in the future.

   Possible scenarios for known lifetimes of resources include, but are
   not limited to the following:

      Temporary Resources: Some resources may have a limited lifetime by
      definition.  For example, a pending order represented by a
      resource may already list all the details of the order, but may
      only exist for a limited time unless it is confirmed and only then
      becomes permanent.  In such a case, the service managing the
      pending order can make this limited lifetime explicit, allowing
      clients to understand that the pending order, unless confirmed,
      will disappear at some point in time.

      Migration: If resources are changing identity because a service
      migrates them, then this may be known in advance.  While it may
      not yet be appropriate to use HTTP redirect status codes (3xx), it

Wilde                   Expires February 4, 2016                [Page 2]
Internet-Draft                Sunset Header                  August 2015

      may be interesting for clients to learn about the service's plan
      to take down the original resource.

      Retention: There are many cases where regulation or legislation
Show full document text