[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #14165 [Tor]: Tor needs a protocol versioning scheme

#14165: Tor needs a protocol versioning scheme
-----------------------------+-------------------------------------
     Reporter:  TvdW         |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:  Tor: 0.2.???
    Component:  Tor          |    Version:
   Resolution:               |   Keywords:  tor-spec needs-proposal
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-------------------------------------
Changes (by nickm):

 * keywords:  tor-spec => tor-spec needs-proposal
 * milestone:   => Tor: 0.2.???


Comment:

 One interesting issue here is that protocol versions come in several
 potential flavors.  For example, to learn what you can do when connecting
 to a server, you can deal with its "link protocol version"... but if you
 are going to be extending a circuit through a server, you need to know
 what it supports for _that_, and if you're using hidden services served at
 a server, you're going to need a version for that too.

 Once we walk far enough down this road, we'll find that these protocols
 aren't fully dependent: one can provide hidden services version X but
 relay protocol version Y.  Decoupling these would make our protocol design
 much more challanging.

 So perhaps the question is: how much of this can we do without harming
 anything else/

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/14165#comment:2>
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