Re: [apps-discuss] Sunset HTTP header field

James M Snell <jasnell@gmail.com> Tue, 04 August 2015 01:55 UTC

Return-Path: <jasnell@gmail.com>
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 9B5F51B3186 for <apps-discuss@ietfa.amsl.com>; Mon, 3 Aug 2015 18:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 TNdTKjyDTQ4W for <apps-discuss@ietfa.amsl.com>; Mon, 3 Aug 2015 18:55:10 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1910D1B31A3 for <apps-discuss@ietf.org>; Mon, 3 Aug 2015 18:55:08 -0700 (PDT)
Received: by obbop1 with SMTP id op1so112956405obb.2 for <apps-discuss@ietf.org>; Mon, 03 Aug 2015 18:55:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=JACJ/23KHe2HjCSZaRQQ3rezCLHOOjTJf/+apHCdn/8=; b=EyumplJ7IAKyWbCk8SkXd0n3Ufwgg/jO2XspkXeB+CfiouQWCZwY4yy9ce/+H5W1fr gxoT4l8Qyg4R/F6Rg+MEbN0MelqhqER5mYBIRfWuLaNYE2v1H2i0ormFbHlDGjlcNkR6 qtwJOL1nua1dc2+8IsCf+jph1jBOK67y6f1WKGq7mEHxsyC8hGoWB2PfYCXJ3yapyGP1 dseLz+BJFs6KSuJcaB5MBd+itQxRKFYgG1TSthXqLmtKf90QQa8+DemY4w8JcYANy7s0 noynbjjtBhuItFxymVkCQoNXTpv4eAPAJsRmmw+VGXjd6L3uklJVb+x1T7JzjueVHN2t TsnQ==
X-Received: by 10.60.92.37 with SMTP id cj5mr922673oeb.30.1438653307474; Mon, 03 Aug 2015 18:55:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.37.65 with HTTP; Mon, 3 Aug 2015 18:54:48 -0700 (PDT)
In-Reply-To: <55C018E1.8080405@berkeley.edu>
References: <55C018E1.8080405@berkeley.edu>
From: James M Snell <jasnell@gmail.com>
Date: Mon, 03 Aug 2015 18:54:48 -0700
Message-ID: <CABP7RbdfxC0O3jv5+RNGMfh9VGR+gd=bbNp5fhLc-XyyuHep6Q@mail.gmail.com>
To: Erik Wilde <dret@berkeley.edu>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/ln68u17jR7_TEKVQEcuqozvfvB8>
Cc: "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Sunset HTTP header field
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 04 Aug 2015 01:55:11 -0000

This is certainly interesting, but I'm not quite sure it goes far
enough. In general, when a particular API is being deprecated, there
is generally some form of replacement or alternative that developers
are being pushed towards, and potentially some form of notice that
should be displayed.

Considering that, a Link header might be an interesting possible approach:

Link: </deprecation-notice.html>; rel="sunset"; title="This API will
be sunset on 2015-12-12"; sunset=2015-12-12

- James

On Mon, Aug 3, 2015 at 6:44 PM, Erik Wilde <dret@berkeley.edu> wrote:
> hello.
>
> a little while ago there was a brief thread on apps-discuss regarding how to
> expose information about "URI lifetime" in an HTTP response:
>
> https://www.ietf.org/mail-archive/web/apps-discuss/current/msg14343.html
>
> it took me a little while to write something up, but i have just published a
> first draft proposing a "Sunset" HTTP header field, that serves that
> purpose:
>
> https://tools.ietf.org/html/draft-wilde-sunset-header-00
>
> it is as simple as possible right now (a simple timestamp advertising when a
> resource might become unavailable). i'd be very interested in some feedback
> about what else might be needed, and of course in people finding this useful
> and maybe implementing it in their services.
>
> 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 |
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss