Oren Tirosh <oren@hishome.net> wrote:
>SSH supports connection multiplexing which allows sharing a single TCP
>connection for multiple sessions.

It does? I guess you could call the ability to handle multiple distinct
tunnels over the same TCP connection multiplexing.

>Inverse multiplexing would let a
>single session to span multiple TCP connections.

Or to let a single TCP tunnel span multiple SSH connections.

>An inverse multiplexing layer would be added between the the connection
>layer and multiple instances of the transport layer. The imux layer
>would appear to the connection layer as a transport layer with relaxed
>ordering guarantees: SSH packets with the same channel id would be
>delivered in order but packets from separate channels can have
>different latencies.

Why bother doing this inside the ssh protocol? Wouldn't it be much cleaner
to use tcp-level multiplexing and run ssh on top of that (or that on top
of SSH tunnels)?
--
Mark Rafn dagon@dagon.net <http://www.dagon.net/>