Delta encoding in HTTP
draft-mogul-http-delta-10
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3229.
|
|
---|---|---|---|
Authors | Arthur van Hoff , Fred Douglis , Balachander Krishnamurthy , Yaron Y. Goland , Daniel M. Hellerstein , Anja Feldmann , Jeffrey Mogul | ||
Last updated | 2013-03-02 (Latest revision 2001-10-04) | ||
RFC stream | Legacy | ||
Intended RFC status | Proposed Standard | ||
Formats | |||
Stream | Legacy state | (None) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Became RFC 3229 (Proposed Standard) | |
Action Holders |
(None)
|
||
Telechat date | (None) | ||
Responsible AD | Ned Freed | ||
IESG note | |||
Send notices to | (None) |
draft-mogul-http-delta-10
A new Request for Comments is now available in online RFC libraries. RFC 3229 Title: Delta encoding in HTTP Author(s): J. Mogul, B. Krishnamurthy, F. Douglis, A. Feldmann, Y. Goland, A. van Hoff, D. Hellerstein Status: Standards Track Date: January 2002 Mailbox: JeffMogul@acm.org, bala@research.att.com, douglis@research.att.com, anja@cs.uni-sb.de, yaron@goland.org, avh@marimba.com, danielh@crosslink.net Pages: 49 Characters: 111953 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-mogul-http-delta-10.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3229.txt This document describes how delta encoding can be supported as a compatible extension to HTTP/1.1. Many HTTP (Hypertext Transport Protocol) requests cause the retrieval of slightly modified instances of resources for which the client already has a cache entry. Research has shown that such modifying updates are frequent, and that the modifications are typically much smaller than the actual entity. In such cases, HTTP would make more efficient use of network bandwidth if it could transfer a minimal description of the changes, rather than the entire new instance of the resource. This is called "delta encoding." This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.