<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.bishop-httpbis-push-cases" target="https://datatracker.ietf.org/doc/html/draft-bishop-httpbis-push-cases-00">
   <front>
      <title>HTTP/2 Server Push Use Cases</title>
      <author initials="M." surname="Bishop" fullname="Mike Bishop">
         <organization>Akamai</organization>
      </author>
      <date month="June" day="29" year="2018" />
      <abstract>
	 <t>   HTTP/2 defines the wire mechanics of Server Push.  Though the
   mechanics of how a pushed resource is delivered are well-specified,
   the use cases that describe which resources can be pushed, in what
   states, and for what purpose are not described in HTTP/2.  As a
   result, support between implementations varies widely.

   This document attempts to enumerate interesting scenarios, in hopes
   that a more concrete taxonomy can assist the community in arriving at
   a standard set of supported scenarios.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-bishop-httpbis-push-cases-00" />
   
</reference>
