
The farther you get down this list with your research topic, the more likely it is to ultimately get adopted or otherwise affect change in Tor (or any other privacy or software project that you care about). Consider current and future design compatibility!Įxperienced researchers will immediately notice that a lot of published research, even at top-tier venues, only makes it two steps deep into this list.Ensure others can reproduce your results easily!.So, here is your list of goals, in order of increasing difficulty, when conducting relevant research: At the end of this post, we will look at a positive example of excellent research that successfully accomplished all of these goals and give overall takeaways. Each successive goal is more difficult to accomplish than the previous one. We have structured this post in terms of an ordered list of goals for research. The purpose of this post is to discuss what good research needs to do in order to ensure it has the best chance of being adopted by Tor or any other large software project. Within Tor, we have found that integrating new research findings isn't seamless or predictable, and good ideas are often lost or deemed incompatible without significantly more analysis and research. However it is all too common that good research ideas don't make their way into practice. TLS 1.3 is one recent example of where a symbiotic research/practitioner relationship has improved the protocol's design and safety. For project maintainers, research that identifies vulnerabilities, creates new solutions to existing problems, and verifies proposed designs helps improve projects and make them safer for end users.

When researchers work closely with the design and development of deployed systems, this not only results in better research, but also better systems.

As we mentioned in our previous post about Tor research topics, Tor greatly benefits from the research community.
