On Mon, 26 May 2014, Sean Dennis wrote to mark lewis:

 ml> IREX is not fully binkp 1.1 compliant... IREX implements part of 
 ml> binkp 1.1 and some things were changed/added to the proposal after 
 ml> the IREX author quit supporting IREX... binkp 1.1 is still a 
 ml> proposal...

 SD> As I was shown, MBSE has a workaround that forces its binkd to 
 SD> drop to an older specification and it does work quite nicely with 
 SD> 'Rex 2.31 systems. 

yep!

FWIW: this was discussed some weeks back in the BINKD echo when michael van
der vlist ran into it after updating his system to using binkd from
whatever he had been using before... at least one of the systems he
connects to is running MBSE and his binkd would not talk to them because
they had used this setting for his system... apparently he had been using
IREX and then switched... so the problem was that the MBSE systems were
forcing binkp 1.0 but still indicating binkp 1.1 and his binkd was not
switching to binkp 1.0 because of this false indication... he was finally
able to get hold of those operators and have them turn off that option and
things have been fine ever since... he's asked several times for a similar
switch in binkd to force binkp 1.0 capability on a system so that one can
at least connect and exchange mail to tell them of the problem... without
this capability, it is possible that some system will be cut off and assume
the worse and have no way of contacting the other operator to try to
resolve it...

)\/(ark

One of the great tragedies of life is the murder of a beautiful theory by a
gang of brutal facts. --Benjamin Franklin

--- FMail/Win32 1.60