Resource Maps
draft-eriksson-http-resource-map-00

Document Type Expired Internet-Draft (individual)
Last updated 2017-05-04 (latest revision 2016-10-31)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-eriksson-http-resource-map-00.txt

Abstract

When the 'out-of-band' content coding ('OOB') is used for delivering a number of resources from a primary server via a secondary server, the additional round trips for OOB responses and load on the primary server can be a significant nuisance. In such situations, it is useful for the primary server to be able to provide the client with OOB response information for several resources in one go anticipating future client requests. This document describes a format for providing the client with the information, called a resource map, and how the resource map could be delivered to a client.

Authors

Goran Eriksson (goran.ap.eriksson@ericsson.com)
Christer Holmberg (christer.holmberg@ericsson.com)
Zaheduzzaman Sarker (Zaheduzzaman.Sarker@ericsson.com)
Julian Reschke (julian.reschke@greenbytes.de)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)