RFC 7089 on HTTP Framework for Time-Based Access to Resource States -- Memento

rfc-editor@rfc-editor.org Fri, 20 December 2013 21:23 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B971AE156 for <ietf-announce@ietfa.amsl.com>; Fri, 20 Dec 2013 13:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Level:
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 Nd5BC8ouuxQP for <ietf-announce@ietfa.amsl.com>; Fri, 20 Dec 2013 13:22:59 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 27A051A1F33 for <ietf-announce@ietf.org>; Fri, 20 Dec 2013 13:22:57 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DBF667FC3A4; Fri, 20 Dec 2013 13:22:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7089 on HTTP Framework for Time-Based Access to Resource States -- Memento
From: rfc-editor@rfc-editor.org
Message-Id: <20131220212254.DBF667FC3A4@rfc-editor.org>
Date: Fri, 20 Dec 2013 13:22:54 -0800
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Fri, 20 Dec 2013 21:23:04 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7089

        Title:      HTTP Framework for Time-Based Access 
                    to Resource States -- Memento 
        Author:     H. Van de Sompel,
                    M. Nelson,
                    R. Sanderson
        Status:     Informational
        Stream:     Independent
        Date:       December 2013
        Mailbox:    hvdsomp@gmail.com, 
                    mln@cs.odu.edu, 
                    azaroth42@gmail.com
        Pages:      50
        Characters: 107130
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-vandesompel-memento-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7089.txt

The HTTP-based Memento framework bridges the present and past Web.  It
facilitates obtaining representations of prior states of a given
resource by introducing datetime negotiation and TimeMaps.  Datetime
negotiation is a variation on content negotiation that leverages the
given resource's URI and a user agent's preferred datetime.  TimeMaps
are lists that enumerate URIs of resources that encapsulate prior
states of the given resource.  The framework also facilitates
recognizing a resource that encapsulates a frozen prior state of
another resource.


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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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