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 315
    • Issues 315
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • 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
  • #5392
Closed
Open
Created Mar 14, 2012 by Roger Dingledine@armaReporter

Write proposal for n23 patch behavior

In legacy/trac#4488 (moved) we located and updated the n23 patch from the Defenestrator paper. It's now in branch 'n23-2' in my git repo.

The next step is to refactor connection_or_consider_sending_flowcontrol_cell(). To do that, we need to know what the function is supposed to be doing.

Under what circumstances do we send a flowcontrol cell, and how do we pick the values for it? Just as important, in what cases (e.g. if we're a client) do we not send flowcontrol cells?

I'm hoping Mashael will do this, with Ian's help.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking