Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Submit to a standards body #98

Open
mooreds opened this issue Jan 5, 2024 · 1 comment
Open

Submit to a standards body #98

mooreds opened this issue Jan 5, 2024 · 1 comment

Comments

@mooreds
Copy link

mooreds commented Jan 5, 2024

Hi folks,

Apologies if this isn"t the correct place, but I"m wondering if/why you haven"t submitted this to a standards body. Seems like a great thing to go through the w3c or IETF process to become a full blown standard, rather than a vendor consortium document. I saw this which discussed related efforts.

Here"s a list of the IETF working groups. I"m not familiar with all of them, but there may be a fit.

Is this something for the future, or an action you"ve considered and then discarded? If the latter, I"d love to know why. If the former, I know a few folks who work on standards who would good to chat with to discuss appropriate steps.
@sjatwood
Copy link

Along the same lines, I"m curious about the relationship (if any) between this effort and the WebSub protocol which was a W3C recommendation from 2018: https://www.w3.org/TR/websub/

Skimming through the spec, there seems to be some similarity/overlap (e.g. use of HMAC for auth). Have you all reviewed that older standard? It would be nice to align where feasible and/or highlight gaps in that existing spec that this effort is aimed at addressing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mooreds @sjatwood