- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Wed, 11 Jan 2017 23:10:51 -0500
- To: public-digital-verification@w3.org, Web Payments <public-webpayments@w3.org>
Hi all, I've been getting a number of new pings about the HTTP Signatures specification (new implementation queries, can you add signature mechanism X, how compatible is this with JWS, why hasn't this moved forward at IETF, etc.). This was being incubated over in the Web Payments CG[1], but I'm moving it to the Digital Verification CG[2] as it makes more sense to have it there: https://w3c-dvcg.github.io/http-signatures/ and https://w3c-dvcg.github.io/http-signatures-audit/ This spec is implemented in node.js via the http-signature library, which has 10.3M downloads in the last month (much of that is due to the node.js request library's dependency on the package): https://www.npmjs.com/package/http-signature The Github repos are here: https://github.com/w3c-dvcg/http-signatures https://github.com/w3c-dvcg/http-signatures-audit The spec is 4 years old at this point and has been stable for the past 2 years. We've just not had the time to push it forward at IETF. I may give it a shot at this upcoming IETF in Chicago. We'd like to see more implementations of it before pushing it further. This email is just noting the migration of the spec to the DVCG. -- manu [1]https://www.w3.org/community/webpayments/ [2]https://www.w3.org/community/digital-verification/ -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: Rebalancing How the Web is Built http://manu.sporny.org/2016/rebalancing/
Received on Thursday, 12 January 2017 04:11:22 UTC