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

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        G. Eriksson
Internet-Draft                                               C. Holmberg
Intended status: Informational                                 Z. Sarker
Expires: May 4, 2017                                            Ericsson
                                                              J. Reschke
                                                              greenbytes
                                                        October 31, 2016

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

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.

Editorial Note (To be removed by RFC Editor before publication)

   Distribution of this document is unlimited.  Although this is not a
   work item of the HTTPbis Working Group, comments should be sent to
   the Hypertext Transfer Protocol (HTTP) mailing list at
   ietf-http-wg@w3.org [1], which may be joined by sending a message
   with subject "subscribe" to ietf-http-wg-request@w3.org [2].

   Discussions of the HTTPbis Working Group are archived at
   <http://lists.w3.org/Archives/Public/ietf-http-wg/>.

   XML versions, latest edits, and issue tracking for this document are
   available from
   <https://github.com/EricssonResearch/Blind-Cache-Drafts>.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering

Eriksson, et al.           Expires May 4, 2017                  [Page 1]
Internet-Draft                Resource Maps                 October 2016

   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 4, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Eriksson, et al.           Expires May 4, 2017                  [Page 2]
Internet-Draft                Resource Maps                 October 2016

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Notational Conventions . . . . . . . . . . . . . . . . . .  4
   2.  Basic procedure for providing a Resource Map . . . . . . . . .  4
   3.  Updating the Resource Map  . . . . . . . . . . . . . . . . . .  6
     3.1.  Primary server need to update Resource Map . . . . . . . .  6
     3.2.  Piggyback  . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.3.  Using Web Push . . . . . . . . . . . . . . . . . . . . . .  6
     3.4.  Continuous Updates . . . . . . . . . . . . . . . . . . . .  7
     3.5.  Resource Map Timer . . . . . . . . . . . . . . . . . . . .  7
     3.6.  Resource Map compression . . . . . . . . . . . . . . . . .  7
       3.6.1.  gzip . . . . . . . . . . . . . . . . . . . . . . . . .  7
       3.6.2.  Formulas . . . . . . . . . . . . . . . . . . . . . . .  7
   4.  The Resource Map format  . . . . . . . . . . . . . . . . . . .  8
     4.1.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  8
     4.2.  Updates for Resource Map . . . . . . . . . . . . . . . . .  8
     4.3.  Secondary Servers and Mapping of Resources . . . . . . . .  9
Show full document text