RFC 7089: HTTP Framework for Time-Based Access to Resource States -- Memento
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7089
- Published
- December 2013
- Authors
- H. Van de Sompel; M. Nelson; R. Sanderson
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 50
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6983Models for HTTP-Adaptive-Streaming-Aware Content Distribution Network Interconnection (CDNI)Current
July 2013
- RFC 6903Additional Link Relation TypesCurrent
March 2013
- RFC 3507Internet Content Adaptation Protocol (ICAP)Current
April 2003
- RFC 7230Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and RoutingObsoleted
June 2014
- RFC 7231Hypertext Transfer Protocol (HTTP/1.1): Semantics and ContentObsoleted
June 2014
- RFC 7232Hypertext Transfer Protocol (HTTP/1.1): Conditional RequestsObsoleted
June 2014
- RFC 7234Hypertext Transfer Protocol (HTTP/1.1): CachingObsoleted
June 2014
- RFC 7235Hypertext Transfer Protocol (HTTP/1.1): AuthenticationObsoleted
June 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?