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

Congestion control layer in/on-top of IPv8 #39

Closed
synctext opened this issue Feb 12, 2018 · 3 comments
Closed

Congestion control layer in/on-top of IPv8 #39

synctext opened this issue Feb 12, 2018 · 3 comments
Labels
priority: low Should be addressed at some point in the future priority: medium Enhancements, features or exotic bugs

Comments

@synctext
Copy link
Member

Transport any binary blob:

@qstokkink
Copy link
Collaborator

There is also this Dispersy utp community I made more than half a year ago:
https://github.com/qstokkink/gumby/blob/utp_community/experiments/utp/utp_community.py

@qstokkink qstokkink added the priority: medium Enhancements, features or exotic bugs label Feb 13, 2018
@qstokkink
Copy link
Collaborator

Also that QUIC link appears to be for:

computing a sparse inverse covariance matrix estimation using quadratic approximation

Not Google's QUIC protocol.

@qstokkink qstokkink added the priority: low Should be addressed at some point in the future label Jun 12, 2018
@qstokkink
Copy link
Collaborator

By design philosophy we do not want congestion control inside of IPv8, on top is fine. If an overlay ever needs congestion control, it is doing something wrong.

This does not mean that there is no use-case for large blob transfer. This does mean that this is not so much an issue for IPv8, as it is for layers building on IPv8 (like Tribler/tribler#3489).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low Should be addressed at some point in the future priority: medium Enhancements, features or exotic bugs
Development

No branches or pull requests

2 participants