[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #3587 [Tor Bridge]: Accounting should work with pluggable transports
#3587: Accounting should work with pluggable transports
------------------------+---------------------------------------------------
Reporter: asn | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: unspecified
Component: Tor Bridge | Version:
Keywords: | Parent: #3591
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by asn):
Replying to [comment:10 nickm]:
> I think we should do a new transport metadata proposal together. We
should IMO not edit 180 any further: instead, we should extract the
implemented part of 180 into a new spec.
>
> I don't have a strong feeling about what goes in which protocol. I think
that keeping the addresses as part of the extended or port idea could be a
good idea, since otherwise Tor doesn't know where the connection is really
coming from for a little while. But there could be a way to make it work
simply, maybe.
>
> I don't think that this blocks #4685 in any straightforward way.
Please see https://lists.torproject.org/pipermail/tor-
dev/2012-January/003225.html for a draft.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3587#comment:11>
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