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

Proposal: Add additional reliability guarantees #13

Open
luna-duclos opened this issue Jun 28, 2014 · 1 comment
Open

Proposal: Add additional reliability guarantees #13

luna-duclos opened this issue Jun 28, 2014 · 1 comment

Comments

@luna-duclos
Copy link

I'd like to propose adding two additional types of reliability guarantees to CurveCPR, which could be negotiated using two extensions.

The first type would be a fully unreliable connection, where no attempt at reliability, acknowledgement or congestion control is done.

The second is a sequenced stream, where in the face of packet reordering, only the latest packet is kept, and older ones are discarded, again, with this, no attempt at extra reliability, acknowledgement or congestion control is done. The idea is that the data is so time critical that any resending would yield outdated data anyway as fresher data would've been sent.

I was hoping for some guidance on where the code changes for this would be, as well as feedback on whether or not this belongs in curveCPR itself.
I've investigating implementing it purely in the callbacks, but I found no way to implement it cleanly without screwing up chicago or the reliability code.

@luna-duclos
Copy link
Author

As a clarification: I'll very much be implementing these myself, but I'd like some feedback first :)

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

1 participant