Re: [TF-AP] FYI - HTTP Web Push protocol

Hi Dave,

I reviewed the webpush draft 2 weeks ago in Prague and hope to align CoAP Pub-Sub with webpush patterns and architecture as much as is practical. 

Webpush has a good mapping to REST principles and some interesting reliability features, but as I recall there is not a keep-alive ping function. I believe webpush depends on existing methods for TCP (really TLS) firewall traversal.

Firewall traversal seems to be a cross layer issue of sorts, between the application and the transport. Maybe there is something in HTTP/2 that addresses this?

I haven’t seen much discussion of the firewall problem in the WoT IG. What’s the position or expectation?

Best regards,

Michael


On Aug 5, 2015, at 4:31 AM, Dave Raggett <dsr@w3.org> wrote:

> The IETF webpush WG seems relevant to the binding of the web of things data model to HTTP, and is analogous to the CoAP OBSERVE mechanism.  In essence, a client subscribes to events that are then pushed to it via HTTP 2 server push. I haven’t looked at the details, but suspect this includes provision for keep alive messages to ensure that a Firewall/NAT doesn’t block the server push messages.
> 
> Webpush WG: https://datatracker.ietf.org/wg/webpush/documents/
> 
> One of the recent drafts is: "Generic Event Delivery Using HTTP Push”
> 
>    draft-ietf-webpush-protocol-00,  published 20 July 2015
> ]  https://datatracker.ietf.org/doc/draft-ietf-webpush-protocol/?include_text=1
> 
> —
>    Dave Raggett <dsr@w3.org>
> 
> 
>