Skip to content

Proposal: Add additional reliability guarantees #13

@luna-duclos

Description

@luna-duclos

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions