Come up with a recommended approach for an external program that discovers bridge addresses to tell Tor about them
Sponsor F deliverable 7 says: "pluggable transports: Come up with a recommended approach for an external program that discovers bridge addresses to tell Tor about them. Does it tell Vidalia, which setconfs them? Should it be a Vidalia plugin, or launched by Vidalia? Or can we integrate it into Torbutton? Or should it be a separate program and talk the controller protocol itself? Should we extend the stdin/stdout PT protocol? Or should the separate program just be an independent proxy, and never even tell Tor about the bridges? I am thinking in particular of the ISC program that will take in an n-tuple from a rendezvous service and output some bridge addresses, but it would be good to have a plan for future similar tools. Write proposals and start implementation as needed. [Nick, George, Tomas, Mike, Roger, everybody]"
Mike and I decided to split this deliverable into two substeps:
Discuss possible designs.
Write proposals and start implementing them.
Assigning this project ticket to Mike. He said he's fine taking the lead on the discussion task, but not on the proposal writing task. Hopefully the discussion will give us some hints who could write the proposals and start implementing them.