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.

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

Switch position on zstd to positive #1042

Merged
merged 1 commit into from
Jun 24, 2024
Merged

Switch position on zstd to positive #1042

merged 1 commit into from
Jun 24, 2024

Conversation

jesup
Copy link
Member

@jesup jesup commented Jun 18, 2024

Feel free to bikeshed on the wording. Switched the issue to 775 where we agreed to ship zstd

Copy link
Member

@tantek tantek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated summary and position reflect latest discussions in #775.

Only nit I have is that https://datatracker.ietf.org/doc/html/rfc8478 says "Category: Informational" so should this be labeled a "Proposal" rather than "IETF" since as the RFC says:

Despite use of the word "standard" as part of its name, readers are
advised that this document is not an Internet Standards Track
specification; it is being published for informational purposes only.

And if it's actually (being) interoperably implemented, who is taking care of moving this to a standards-track working group to get it officially (not just de facto) standardized?

@adamroach
Copy link
Contributor

As the person who wrote the quoted text: based on the history of this document in the IETF, I'm pretty comfortable asserting that no one is likely to ever have the appetite to push the zstd specification onto a standards track. Unless some other SDO takes up the work of publishing a standard, its status as "informational" is likely permanent.

I agree with Tantek that "proposal" is the correct category for this feature, per my understanding of feature characterizations.

@zcorpan zcorpan merged commit 438f990 into mozilla:main Jun 24, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants