= Сообщение: 4100 из 7124 ====================================== FTSC_PUBLIC = От : Markus Reschke 2:240/1661 09 Dec 18 19:49:00 Кому : mark lewis 09 Dec 18 19:49:00 Тема : FTS-5001 FGHI : area://FTSC_PUBLIC?msgid=2:240/1661+5bfd8f7f На : area://FTSC_PUBLIC?msgid=1:3634/12.73+5c0d4b4a = Кодировка сообщения определена как: LATIN1 ================================= ============================================================================== Hello Mark!
Dec 09 11:57 2018, mark lewis wrote to Michiel van der Vlist:
ml> i don't understand what conflicting interpretations of which flag ml> there are...
Let's try some example. ;) Carol's nodelist entry includes:
INA:shenks.synchro.net,IBN:shenks.dyndns.org
Carol has explained that in Z1's view both FQDNs should be used for binkp.
Based on the FTSC doc multiple addresses should be listed either as
INA:shenks.synchro.net,INA:shenks.dyndns.org,IBN
or as
IBN:shenks.synchro.net,IBN:shenks.dyndns.org
The INA flag is meant to list a common FQDN for all protocols/services. If the IBN flag carries an address it should be used for binkp. It prevails any common address(es) from the INA flag(s) because it's specific to binkp. But this contradicts the method Carol has explained.
A nodelist converter for binkd following FTSC-5001 would extract just shenks.dyndns.org since it's the binkp specific address. And based on the undocumented way the tool would extract shenks.dyndns.org and shenks.synchro.net. Maybe you'll understand the problem now.
