idnits 2.17.1 draft-mogul-http-delta-10.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3229 5 Title: Delta encoding in HTTP 6 Author(s): J. Mogul, B. Krishnamurthy, F. Douglis, 7 A. Feldmann, Y. Goland, A. van Hoff, 8 D. Hellerstein 9 Status: Standards Track 10 Date: January 2002 11 Mailbox: JeffMogul@acm.org, bala@research.att.com, 12 douglis@research.att.com, anja@cs.uni-sb.de, 13 yaron@goland.org, avh@marimba.com, 14 danielh@crosslink.net 15 Pages: 49 16 Characters: 111953 17 Updates/Obsoletes/SeeAlso: None 19 I-D Tag: draft-mogul-http-delta-10.txt 21 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3229.txt 23 This document describes how delta encoding can be supported as a 24 compatible extension to HTTP/1.1. 26 Many HTTP (Hypertext Transport Protocol) requests cause the retrieval 27 of slightly modified instances of resources for which the client 28 already has a cache entry. Research has shown that such modifying 29 updates are frequent, and that the modifications are typically much 30 smaller than the actual entity. In such cases, HTTP would make more 31 efficient use of network bandwidth if it could transfer a minimal 32 description of the changes, rather than the entire new instance of the 33 resource. This is called "delta encoding." 35 This is now a Proposed Standard Protocol. 37 This document specifies an Internet standards track protocol for 38 the Internet community, and requests discussion and suggestions 39 for improvements. Please refer to the current edition of the 40 "Internet Official Protocol Standards" (STD 1) for the 41 standardization state and status of this protocol. Distribution 42 of this memo is unlimited. 44 This announcement is sent to the IETF list and the RFC-DIST list. 45 Requests to be added to or deleted from the IETF distribution list 46 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 47 added to or deleted from the RFC-DIST distribution list should 48 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 50 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 51 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 52 help: ways_to_get_rfcs. For example: 54 To: rfc-info@RFC-EDITOR.ORG 55 Subject: getting rfcs 57 help: ways_to_get_rfcs 59 Requests for special distribution should be addressed to either the 60 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 61 specifically noted otherwise on the RFC itself, all RFCs are for 62 unlimited distribution.echo 63 Submissions for Requests for Comments should be sent to 64 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 65 Authors, for further information.