Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #20961

Closed (moved)
Open
Opened Dec 13, 2016 by David Goulet@dgoulet🐋

prop224: Implement consensus params to adjust portion of the protocol

After discussion with developers and tor-dev@ thread here https://lists.torproject.org/pipermail/tor-dev/2016-December/011725.html, implementing consensus parameters to control some portion of the protocol. What comes to mind:

  • Default number of introduction points and maximum number
  • Timeframe and number of introduce before rotating an intro point.
  • Descriptor lifetime.
  • How many HSDir for a descriptor
  • Rendezvous timeout time.

There are probably more.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#20961