Re: SSH feature suggestion - inverse connection multiplexing

Oren Tirosh <oren@xxxxxxxxxxx> 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@xxxxxxxxx <http://www.dagon.net/>
.

Relevant Pages

  • Re: [SLE] ssh for email question - Success!
    ... multiple forwards in one ssh line. ... 1> The connection speed. ... client but again, if you were using a VPN client ...
    (SuSE)
  • Re: speed limitation with scp and sftp using openssh
    ... I believe (but I haven't examined the protocol) that the issue is the ssh method ... and multiple X windows forwarded at the same time, over the same SSH connection. ...
    (SSH)
  • Re: downloading a single file using multiple threads
    ... The multi part requests in HTTP1.1 are meant to request a single part or multiple parts in a single request, but you can't requests multiple parts in parallel from multiple client threads. ... I know that down-load managers claim to work over HTTP, but that doesn't mean they support multi-part parallel request handling over the same or multiple connections, I don't even know if the protocol allows you to issue new range request when you have a range requests pending. ... If on one connection the client asks for the first megabyte and on a second connection the same client asks for the second megabyte, then if the server is capable of servicing both requests at the same time, there's no reason the client can't wind up receiving both the first and second megabytes in parallel. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: downloading a single file using multiple threads
    ... The multi part requests in HTTP1.1 are meant to request a single part or multiple parts in a single request, but you can't requests multiple parts in parallel from multiple client threads. ... There's nothing about HTTP that requires servers to restrict their communications to a given client to a single connection, and there's nothing about HTTP that stipulates that an HTTP server needs to coordinate communications on independent connections. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: SSH feature suggestion - inverse connection multiplexing
    ... I guess you could call the ability to handle multiple distinct ... tunnels over the same TCP connection multiplexing. ... Or to let a single TCP tunnel span multiple SSH connections. ...
    (comp.security.ssh)