Hi Ulf,
thanks for the good suggestion. To be honest, this will not be something that happens immediately. The reason is that this needs the full implementation of BEEP tuning profiles, which is something the current code base does not deal with. It's not a simple matter of adding just SSL encryption to the channel (of course, that would work - but that wouldn't be real RFC 3195, just a proprietary add-on). And to be honest one time more: RFC 3195 demand in the marketplace is *extremyl* low. So chances we move tuning profiles to a high spot on the todo list are very low given the current demand.
I know this might not be the answer you were looking for, but at least it is a honest one
Rainer Gerhards
Adiscon