Last Call: <draft-ietf-webpush-protocol-10.txt> (Generic Event Delivery Using HTTP Push) to Proposed Standard

The IESG <> Tue, 27 September 2016 15:40 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 5CD8712B228; Tue, 27 Sep 2016 08:40:15 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-webpush-protocol-10.txt> (Generic Event Delivery Using HTTP Push) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 27 Sep 2016 08:40:15 -0700
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 27 Sep 2016 15:40:15 -0000

The IESG has received a request from the Web-Based Push Notifications WG
(webpush) to consider the following document:
- 'Generic Event Delivery Using HTTP Push'
  <draft-ietf-webpush-protocol-10.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2016-10-11. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   A simple protocol for the delivery of real-time events to user agents
   is described.  This scheme uses HTTP/2 server push.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc2818: HTTP Over TLS (Informational - IETF stream)
This reference is already listed in the acceptable Downref Registry.