[apps-discuss] HTTP header field for "URI lifetime"

Erik Wilde <dret@berkeley.edu> Wed, 20 May 2015 06:23 UTC

Return-Path: <dret@berkeley.edu>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CCA61A020A for <apps-discuss@ietfa.amsl.com>; Tue, 19 May 2015 23:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.511
X-Spam-Level:
X-Spam-Status: No, score=-1.511 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qo5Mzg5W7asp for <apps-discuss@ietfa.amsl.com>; Tue, 19 May 2015 23:23:21 -0700 (PDT)
Received: from cm06fe.IST.Berkeley.EDU (cm06fe.IST.Berkeley.EDU [169.229.218.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7109F1A0169 for <apps-discuss@ietf.org>; Tue, 19 May 2015 23:23:21 -0700 (PDT)
Received: from host1-145-static.44-85-b.business.telecomitalia.it ([85.44.145.1] helo=dretair11.local) by cm06fe.ist.berkeley.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1YuxPS-0004P5-MH for apps-discuss@ietf.org; Tue, 19 May 2015 23:23:21 -0700
Message-ID: <555C284E.1030208@berkeley.edu>
Date: Wed, 20 May 2015 08:23:10 +0200
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: IETF Apps Discuss <apps-discuss@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/F4d3olHm0OsDDQ5pGyqVjirQXnY>
Subject: [apps-discuss] HTTP header field for "URI lifetime"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 May 2015 06:23:23 -0000

hello.

we had some discussions at www2015 about a possible HTTP header for 
exposing a URI's "lifetime". please do not get hung up on any 
terminology, but the scenarios we discussed included:

- a service entering the sunset period and wanting to expose the fact 
that it is going to stop operating at some point in time.

- a service doing archiving and wanting to expose that resources will 
only be kept until a certain time, and then disposed.

- a service that might want to encourage users to check back regularly 
so that they might implement some strategy to check back periodically 
and see if the resource is still available or not.

we could not think of an exiting HTTP header field for exposing this 
kind of information. i have two questions:

- is there such a header field?

- if not, is that something that people find interesting and possibly 
useful, or do people think that's not needed or even a bad idea?

thanks a lot and cheers,

dret.

-- 
erik wilde | mailto:dret@berkeley.edu  -  tel:+1-510-2061079 |
            | UC Berkeley  -  School of Information (ISchool) |
            | http://dret.net/netdret http://twitter.com/dret |