Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#4671 closed task (implemented)

Start a list of designs that are related to proposal 182

Reported by: karsten Owned by: nickm
Priority: Medium Milestone:
Component: Metrics/Analysis Version:
Severity: Keywords: SponsorF20120315
Cc: sjmurdoch, arma, tschorsch@… Actual Points:
Parent ID: #4682 Points:
Reviewer: Sponsor:

Description

We have this sponsor F deliverable for March 15, 2012: "Build and execute a plan for proposal from Florian and Björn, to change Tor's incoming and outgoing rate limiting to play better with TCP. We should figure out how it does or does not relate to the n23 congestion control design, to Ian's ideas about Defenestrator, etc. [Steven, Nick, Mike, Roger]"

Nick said he would like to have a list of designs that are related to proposal 182. The idea is to gather all the related proposals that seem to do something similar and figure out which are likely to conflict.

Child Tickets

Change History (5)

comment:1 Changed 7 years ago by karsten

Parent ID: #4682

comment:2 Changed 7 years ago by Flo

Cc: tschorsch@… added

comment:3 Changed 7 years ago by arma

Resolution: implemented
Status: newclosed

The good news is that I think proposal 182 is independent of the defenestrator design: the former is a rate limiting thing, and the latter is a flow control thing.

I've started a table at https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/Performance to keep things organized, and to track progress.

I'm going to call this task done. (The table could always use some more entries, but that will be true forever.)

comment:4 in reply to:  3 Changed 7 years ago by arma

Replying to arma:

The good news is that I think proposal 182 is independent of the defenestrator design: the former is a rate limiting thing, and the latter is a flow control thing.

For those not inside my head, my 'rate limiting' I mean "Tor manages the total number of bytes going into or out of it"; and by flow control I mean "Tor decides whether it's appropriate to send another cell on a given circuit".

comment:5 Changed 7 years ago by karsten

Keywords: SponsorF20120315 added
Milestone: Sponsor F: March 15, 2012

Switching from using milestones to keywords for sponsor deliverables. See #6365 for details.

Note: See TracTickets for help on using tickets.