id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
216	tolerate more TCP endpoint syntax	Brian Warner		"Ticket #203 is about supporting arbitrary twisted ""endpoint"" specifiers. The end goal is to just pass the connecting hint into Twisted and accept whatever the reactor can handle (running TLS on top of whatever pipe it gives us). The first intermediate goal (implemented in [0395476], in 0.6.5) from #203 is to accept {{{tcp:host=XYZ:port=999}}} . The second intermediate goal (also mentioned in #203) is to accept {{{tcp:XYZ:999}}}, which is apparently legal TCP endpoint syntax too.

This ticket is about that second goal.

#203 suggests going all the way to the end and passing the hint into twisted's endpoint API. But I'm not confident that that will work, because we may get back endpoints that don't support {{{.startTLS()}}}. So I want us to study it more first, specifically to decide whether we want to run TLS over i2p/tor, or if we rely upon the transport security that they give us, and what the FURLS would look like if we did (set the tubid to the onion address and then leave the connection hints blank?).
"	defect	closed	major	0.7.0	negotiation	0.6.4	fixed