Research ways of adding Extended ORPort support to pyptlib
A server-side pluggable transport, before proxying the deobfuscated data to the ORPort, it must do the Extended ORPort dance (during which it sends to Tor the IP address of its client, the name of the pluggable transport used, etc.).
It would be nice if developers that write pluggable transports (like flashproxy, stegotorus, etc.) didn't have to care about the Extended ORPort protocol, but still enjoy its benefits. Since these pluggable transports are supposed to be using pyptlib for their managed-proxy needs, it would make sense for pyptlib to also handle the Extended ORPort part.
We should research ways of implementing the Extended ORPort logic to pyptlib without dictating a certain way of thinking and programming to the pluggable transports developer. For example, pyptlib should not use twisted to do the Extended ORPort dance, since that would pretty-much force the developer to use twisted for his transport too.