Futures

You can connect two mbones with two umbone configurations - simplest example is a small site (e.g. a school) with a unicast router and a local mbone router and an ISDN link and a unicast router. There might be administrative reasons for not running a tunnel over the link. You can extend this model to allow non-mbone-application level gatewaying - e.g. an analog phone gateway. A touch tone dial interface to a remote SD client would be the obvious control interface [c.f.. Internet Phone model in the glorious rfc 1789].

Simplifications

The modified sd server and mixer may be co-located or even the same process. In some cases (e.g. no ISDN), the SLP step might not be needed, and the user site might simply get session advertisements mixed down to them always. In other cases, the RLJMP step might not be needed, if there were few sessions, and all could be accommodated.

Implementation

The Session Directory tool is being modified to accommodate SLP, and to be able to run as a daemon/server without a GUI. The mash program can be extended easily to accommodate RLJMP, and then enhanced through a user space version of CBQ to provide appropriate action when inbound traffic to the mixer exceeds outbound bandwidth.