Usually connections are launched from a SOCKSPort, or some equivalent client port. What would you want this control command to do? Once the connection was created, how would an application use it?
The primary purpose would be to providing supporting infra for #28841 (moved). We could make control command as parametrizable as we need to. For example, it could have a way to specify exact introduction point to talk to. Or is there a better way?
Not yet sure if we need to allow an application to use the onion service circuit that would be established this way. Perhaps it shouldn't?
Hm. I think I'd need to see a design here. Maybe having just one command isn't the right thing here, if what we want to allow is really fine-grained control over the process. Instead, for example, we might want to have a separate command for each stage, like we do for HSFETCH.