Re: [Webpush] WGLC for draft-ietf-webpush-protocol-05

[Shida Schubert <[e-mail]>]

Hi Richard;

This has nothing to do with the subject. 

As mentioned in the other e-mail, please refrain your comments to the draft in subject. 

Thanks! 
Shida as co-chair

> On May 18, 2016, at 11:20 PM, Richard Maher <[e-mail]> wrote:
> 
> Interesting developments: -
> 
> GCM has been rebranded to Firebase Cloud Messaging (FCM). FCM <http://firebase.google.com/docs/cloud-messaging/> inherits the reliable and scalable GCM infrastructure, plus new features! See the FAQ <http://firebase.google.com/support/known-issues/#messaging-difference> to learn more. If you are integrating messaging in a new app, start with FCM. GCM users are strongly recommended to upgrade to FCM, in order to benefit from new FCM features today and in the future.
> 
> FIREbase - Hell of a catchy name! What's Mozilla's Autopush called?
> 
> "Firebase the bullet-proof, scaleable, industrial-strength infrastructure behind Firefox." I like it.
> 
> On Tue, May 17, 2016 at 9:50 AM, Richard Maher <[e-mail] <mailto:[e-mail]>> wrote:
> "5.4 Updating Push Messages" is based on the misconception that "Topics" are "Collapse Keys". The standard as proposed has been superseded by event on the ground by established, successful, and more importantly scalable solutions: -
> 
> Google Cloud Messaging: -
> https://developers.google.com/cloud-messaging/topic-messaging <https://developers.google.com/cloud-messaging/topic-messaging>
> 
> Azure Notification Hubs: -
>  https://blogs.windows.com/buildingapps/2013/09/16/delivering-push-notifications-to-millions-of-devices-with-windows-azure-notification-hubs/ <https://blogs.windows.com/buildingapps/2013/09/16/delivering-push-notifications-to-millions-of-devices-with-windows-azure-notification-hubs/>
> 
> Whether the Topics are identified via HTTP headers or JSON Tokens is the only moot point. What is clear is that the proposed protocol attempts to conflate the Topic and Collapse Key features: -
> https://developers.google.com/cloud-messaging/concept-options#collapsible_and_non-collapsible_messages <https://developers.google.com/cloud-messaging/concept-options#collapsible_and_non-collapsible_messages>
> 
> The fact that quintessential Push Notification feature "Broadcasting" has been descoped from this protocol must be sufficient to reject the proposal.
> 
> Please do not make the same mistake that you made with Geofences. IETF and W3C credibility has already suffered enough.
> 
> On Tue, May 17, 2016 at 2:32 AM, Shida Schubert <[e-mail] <mailto:[e-mail]>> wrote:
> All;
> 
> As discussed at the IETF 95, as last issue surrounding the subscription re-use is addressed, we are starting a Working Group Last Call for the webpush protocol. 
> 
> https://tools.ietf.org/html/draft-ietf-webpush-protocol-05 <https://tools.ietf.org/html/draft-ietf-webpush-protocol-05>
> 
> If you have any issues or questions regarding the draft please submit it to the list, when raising issues please provide constructive resolution when possible.
> 
> Please acknowledge on the list even when you are content/happy with the status of the draft. 
> 
> The Working Group Last Call will end on June 6th (3 weeks). 
> 
> Shida
> As co-chair
> 
> _______________________________________________
> Webpush mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/webpush <https://www.ietf.org/mailman/listinfo/webpush>
> 
> 
> 
> _______________________________________________
> Webpush mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/webpush