[Openid-specs-risc] IETF Push Delivery draft needs more support if it's to ever finish

[Mike Jones]

The Push Delivery draft https://tools.ietf.org/html/draft-ietf-secevent-http-push-05 needs more support in the SecEvent working group if it's ever going to finish.  Response to the Working Group Last Call (WGLC) was anemic, leading the chairs to conclude that there wasn't consensus to proceed with the draft.  During the working group meeting today, the chair asked for public demonstrations of more support for the draft.  Given that the existing RISC deployments use it, I'd think that a number of people in this working group would be interested in seeing it become an RFC.  If you want to see it finish, please do this ASAP:


  *   Have a look at the draft https://tools.ietf.org/html/draft-ietf-secevent-http-push-05.
  *   Sign up for the working group mailing list at https://www.ietf.org/mailman/listinfo/id-event (if you haven't already done so).
  *   Send a note to id-event at ietf.org<mailto:id-event at ietf.org> providing any comments you have on the draft and saying that you want to see it become an RFC (or not if you disagree).  A simple "Please publish" note is fine or more detailed comments would also be appreciated, if you have them.
  *   If you have an implementation, or are considering implementing, please also say that.

I know for instance, that Adobe has implemented and deployed the spec.  Who at Adobe could say so to the SecEvents working group?

                                                          Thanks all,
                                                          -- Mike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20190327/85863420/attachment.html>