MR> This is what I've meant with the confusion about which "standard" MR> applies. Apparently Jerry's converter follows the undocumented MR> feature Carol mentioned. So it would extract additional addresses MR> which aren't intended for binkp for a node entry following the FTSC MR> docs (if listed take just the address in the IBN flag). How do we MR> resolve this dilemma?
It seems that we have at least two methods that are used to deal with multi-homed systems, both methods are currently used and very popular.
Jerry's script processes one INA and one IBN record (both with addresses) as multi-homed. Binkp.net seems to ignore the fact that multi-homed systems even exist, it returns only one address for all combinations of INA/IBN. We haven't been told what Markus' and Uli's tools do, so there may be two other methods. FTS-5001 does not document either one of these methods.
How will you clean this up? Be specific. "Change FTS-5001" isn't a good answer. Tell us WHAT you will change and what you will change it to. Keep in mind that FTSC standards document "current practice".
Answer quickly... There are only 2 days left in the voting period.
--- Msged/NT 6.0.1 * Origin: Somewhere in New Hampshire's White Mountains (1:132/174)
