You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2023. It is now read-only.
Hi, I'm @msporny, primary author of the HTTP Signatures specification at IETF for many years now. You've implemented some variation of that specification.
I need your help to move that specification towards a global standard at IETF. Hearing from implementers, such as you, is a big part of determining if the work toward a global standard should proceed. The IETF HTTP Working Group is determining whether the work should proceed right now. This is very good news, because the European Banking API community, W3C DID Working Group, W3C Credentials Community Group and other standards setting organizations depend on implementations standardizing on a way to do HTTP Signatures.
The deadline for noting your support is Jan 31st 2020 (in ~10 days).
Write an email stating:
4.1 That you support the adoption of the draft.
4.2 Why you support the adoption of the draft.
4.3 How you plan to make use the specification, either directly, or indirectly (via someone else's software).
Set up an email filter to put all mail sent to [email protected] into its own folder. The mailing list averages ~350 emails/month. You can also leave the mailing list immediately after sending the email above if that amount of email traffic is unacceptable to you.
For an example of the type of email you could write, see this:
Thanks a ton for supporting the specification through your implementation. I hope you consider helping us take the specification across the goal line by voicing your support in the IETF HTTP Working Group!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, I'm @msporny, primary author of the HTTP Signatures specification at IETF for many years now. You've implemented some variation of that specification.
I need your help to move that specification towards a global standard at IETF. Hearing from implementers, such as you, is a big part of determining if the work toward a global standard should proceed. The IETF HTTP Working Group is determining whether the work should proceed right now. This is very good news, because the European Banking API community, W3C DID Working Group, W3C Credentials Community Group and other standards setting organizations depend on implementations standardizing on a way to do HTTP Signatures.
The deadline for noting your support is Jan 31st 2020 (in ~10 days).
Here's where you can make a difference...
Here is the IETF HTTP WG Call for Adoption:
https://lists.w3.org/Archives/Public/ietf-http-wg/2020JanMar/0002.html
To note your support of the specification:
4.1 That you support the adoption of the draft.
4.2 Why you support the adoption of the draft.
4.3 How you plan to make use the specification, either directly, or indirectly (via someone else's software).
For an example of the type of email you could write, see this:
https://lists.w3.org/Archives/Public/ietf-http-wg/2020JanMar/0018.html
Thanks a ton for supporting the specification through your implementation. I hope you consider helping us take the specification across the goal line by voicing your support in the IETF HTTP Working Group!
The text was updated successfully, but these errors were encountered: