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

Is this still an active project ? #17

Open
amiracam opened this issue Sep 27, 2019 · 3 comments
Open

Is this still an active project ? #17

amiracam opened this issue Sep 27, 2019 · 3 comments

Comments

@amiracam
Copy link

hi, can somebody categorize the level of maturity of the protocol, is it used exercised actively by some ? which outfits ? etc

thanks

-Charles

@war59312
Copy link

war59312 commented Jun 5, 2020

Seems like it is dead, as:

Latest commit 25c9a85 on Jul 15, 2016

It would be best if an admin would mark it as such. GitHub needs a feature to auto mark prone is dead, like if no commits for a year mark it as dead until admin un-marks it.

@xkpx64
Copy link

xkpx64 commented May 26, 2021

It maybe dead but i think the soft is okey to use

@intgr
Copy link

intgr commented Sep 17, 2021

Strangely enough, there was activity in the IETF "tcpinc" working group up until 2019, and they concluded by publishing the specifications:

However, the protocol implemented by this repository is different from the one described in the above two RFCs. To my knowledge, there are no public implementations of RFC 8548. Even code in this repositroy was not updated to follow the spec, since the code predates the working group.

Is it even fair for a standards body to publish something if there are no implementations? Do we know if they are implementable? This is bizarre.

I hope I am wrong and someone corrects me.

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

No branches or pull requests

4 participants