[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5487 [Analysis]: Write an updated version of the Tor Design paper
#5487: Write an updated version of the Tor Design paper
----------------------+-----------------------------------------------------
Reporter: karsten | Owner: sjmurdoch
Type: project | Status: new
Priority: normal | Milestone: Sponsor F: November 1, 2012
Component: Analysis | Version:
Keywords: | Parent:
Points: | Actualpoints:
----------------------+-----------------------------------------------------
Comment(by cypherpunks):
This is Paul. (To answer Karsten, no I don't have a Trac account. I will
if I
must, but I figure it's just one more thing to keep track of and learn how
to
use properly. I get virtually all the Trac updates in my mail and seem to
remain
aware of the relevant ones. I find getting accounts and learning proper
committing/participating in new-to-me idioms a significant distraction
from work,
but will do it if my not having one becomes an even larger inconvenience
to others.)
Mike's suggestion is a good one, but also possibly a huge one. I can't see
something
of publishable length that sets out the differences in design as things
now are vs.
2003/4 plus future plans. At the time of the Tor design paper, we could
just barely
cram all of that in a single paper. I think we know enough and have enough
stuff
on the current and future plates that we should decide if we want to do
the current
design description and motivation or something more like the design
challenges paper
that was never published except as an NRL CHACS report. Even doing just
one of those
threatens to be unwieldy large unless it's all at a very high level.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5487#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs