RFC 8594 on The Sunset HTTP Header Field
rfc-editor@rfc-editor.org Thu, 16 May 2019 03:04 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F94F1202C7 for <ietf-announce@ietfa.amsl.com>; Wed, 15 May 2019 20:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 QcoetknJU9ni for <ietf-announce@ietfa.amsl.com>; Wed, 15 May 2019 20:04:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 398F7120417 for <ietf-announce@ietf.org>; Wed, 15 May 2019 20:04:15 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 84B36B82B0D; Wed, 15 May 2019 20:04:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8594 on The Sunset HTTP Header Field
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190516030401.84B36B82B0D@rfc-editor.org>
Date: Wed, 15 May 2019 20:04:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/IODANIDVDjo3NIGyPKxcs59JBSk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 03:04:24 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8594
Title: The Sunset HTTP Header Field
Author: E. Wilde
Status: Informational
Stream: IETF
Date: May 2019
Mailbox: erik.wilde@dret.net
Pages: 11
Characters: 23588
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-wilde-sunset-header-11.txt
URL: https://www.rfc-editor.org/info/rfc8594
DOI: 10.17487/RFC8594
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.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
- RFC 8594 on The Sunset HTTP Header Field rfc-editor