Typical Network connections for ActiveMQ are uniplexed - fully connectivity being established between brokers by both brokers connecting to one another. For brokers on the same network, this is trivial, as discovery automates the process.
However, for brokers that are remote, where multicast discovery isn't possible and where outbound connections are the only option, a new type of network connection is required that proivdes full multiplex message transfer from the remote location.
In addition, the protocol should be based on the peer:// protocol, enabling a JMS client to create an embedded broker automatically, that uses remote network connections. This enables the client to publish messages, even if the transport has diconnected.