Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 831
    • Issues 831
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #40202

Closed
Open
Created Nov 24, 2020 by Mike Perry@mikeperryDeveloper

Ressurect Conflux Proposal

@dgoulet wrote an initial conflux proposal draft. In the network-team meeting on Nov 17th, we discussed reviving it, but based on Proposal 324.

Things we definitely need:

  • Unreliable conflux (no resumption windows)
  • Use Prop324 congestion window information to decide which circ to send data on
  • Add sequence numbers to relay cells on each leg (Prop 325? Or other approach?)
  • Minimize the reorder window at Exits for stream assembly (pushback tradeoffs, etc)
  • Side channel analysis section

Nice to have:

  • Pre-emptive circuit discussion
  • Minimize client reorder window
  • Resumption if a circuit leg dies

This is Sponsor 61, Objective 3.1 material.

Edited Nov 24, 2020 by Mike Perry
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking