Unbound Server Push (USP) for HTTP/QUIC
draft-pardue-quic-http-unbound-server-push-01

Document Type Active Internet-Draft (individual)
Last updated 2018-07-01
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                                          L. Pardue
Internet-Draft                                BBC Research & Development
Intended status: Informational                              July 1, 2018
Expires: January 2, 2019

                Unbound Server Push (USP) for HTTP/QUIC
             draft-pardue-quic-http-unbound-server-push-01

Abstract

   This document defines an HTTP semantic extension, Unbound Server Push
   (USP), which allows HTTP resources to be pushed without the need for
   a prior HTTP request.  HTTP/QUIC clients opt in to this feature via
   an HTTP/QUIC setting.

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
   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 January 2, 2019.

Copyright Notice

   Copyright (c) 2018 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.

Pardue                   Expires January 2, 2019                [Page 1]
Internet-Draft              USP for HTTP/QUIC                  July 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  The Unbound Promise Stream Type . . . . . . . . . . . . . . .   3
   3.  The SETTINGS_ENABLE_UNBOUND_PUSH Parameter  . . . . . . . . .   3
   4.  Usage of Unbound Server Push  . . . . . . . . . . . . . . . .   3
   5.  0-RTT Considerations  . . . . . . . . . . . . . . . . . . . .   4
   6.  Handling Multiple Clients . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Registration of Unbound Promise Stream Type . . . . . . .   4
     8.2.  Registration of SETTINGS_ENABLE_UNBOUND_PUSH Parameter  .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   HTTP server push is a feature of HTTP/2 [RFC7540] and HTTP/QUIC
   [QUIC-HTTP] that allows a server to pre-emptively send HTTP resources
   to a client in association with a previous client-initiated request.
   This binding to a request object aligns with paradigms familiar to
   client and server implementations.  Unbound server push, in contrast,
   may provide benefits for use cases where holding a request object
   open for long periods (long polling) is undesirable, or where a
   request object does not exist (unidirectional flows).  (The
   introduction of unidirectional streams in the QUIC transport
   [QUIC-TRANSPORT] provides a direct expression of this message
   exchange pattern.)

   This document defines an HTTP/QUIC protocol extension that allows a
   server to send one or more HTTP/QUIC "PUSH_PROMISE" frame on a new
   server-initiated unidirectional stream type: the unbound promise
   stream Section 2.  Endpoints opt in to the unbound server push
   feature using a "SETTINGS" parameter (Section 3) in accordance with
   Section 5.5 of [RFC7540].  This is the only behavioural change to
   server push as described in [QUIC-HTTP].  Unbound server push
   operates in addition to bound server push for any HTTP/QUIC
   connection.

   Unbound server push should be used with care.  It may introduce
   complexities for implementations, particularly intermediaries, and it
   can pose challenges for presentation to the application above HTTP.

   In deployments where multiple client connections are trunked by a
   reverse proxy onto a single upstream connection, unbound server push

Pardue                   Expires January 2, 2019                [Page 2]
Internet-Draft              USP for HTTP/QUIC                  July 2018
Show full document text