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 832
    • Issues 832
    • 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
  • #14987

Closed
Open
Created Feb 22, 2015 by Damian Johnson@atagar

Settle on a name for descriptors

As discussed on #14784 we call self-published descriptors quite a few things...

  • 'GETINFO desc/*' and Stem call the main self-published descriptors server descriptors. Metrics also uses a "server-descriptor 1.0" annotation for them.
  • The dir-spec calls them router descriptors... usually. It opts for 'server descriptor' in section 6.2.
  • CollecTor calls them relay descriptors.

Having three different names is confusing for new contributors and... well, us too. We should standardize on a name.

This primarily straddles Tor's spec, Stem, and CollecTor. Personally I'd like for us to standardize on server descriptors because it's codified in the Metrics annotation and classes Stem vends.

Karsten, Nick: any objections? If not then I'm happy to provide a spec patch and file a CollecTor ticket for this.

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