Skip to content

Improve onion service (aka hidden service) modeling #58

@sporksmith

Description

@sporksmith

Some things to revisit after merging #5

  • Measure HS circuits per HS user: We currently calculate the number of non-HS-circuits-per-non-HS-user and then also use that as the HS-circuits-per-HS-user. Ideally we ought to more directly measure the latter, perhaps using the technique from section 6.3 of https://torusage-imc2018.github.io/paper.pdf.

  • Measure fraction of HS traffic and/or users: The user currently specifies what fraction of traffic to make hidden-service traffic. Probably better to estimate the fraction of HS traffic in the real network and use that (perhaps still with a user-configurable multiplier on top).

  • Generate HS markov models?: The HS traffic may be different enough in character from everything else that it'd be worth learning and using separate markov models for HS brackground traffic.

  • Split HS metrics: HS metrics are currently lumped in with non-HS metrics, but are likely to be substantially different. Probably better to split these out to separate lines or graphs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions