= Сообщение: 5575 из 7402 ============================================= IPV6 = От : Victor Sudakov 2:5005/49 05 Jul 18 12:08:42 Кому : Benny Pedersen 05 Jul 18 12:08:42 Тема : 2:5057/53 FGHI : area://IPV6?msgid=2:5005/49+5b3da7de На : area://IPV6?msgid=2:230/0+5b3d2563 = Кодировка сообщения определена как: CP866 ================================== Ответ: area://IPV6?msgid=2:230/0+5b3dc063 ============================================================================== Dear Benny,
04 Jul 18 19:52, you wrote to Michiel van der Vlist:
MvdV>> Let's give him and his NC a chance to correct it...
BP> it basicly there own problem, but binkp.net should reject ina with BP> binkp.net listnings
Last time I checked, binkp.net did not rely solely on DDN, you could enter any RR for your node manually via a Web page (which I did long ago). So if you have created a RR for your node in binkp.net, there should be no technical problem using a binkp.net-derived name in the nodelist flags.
The requirement in FTS-5004
If the INA flag (or any of the protocol flags) of any node carries host name built from the FTN address using DDN or any other method, that node MUST be skipped and MUST NOT appear in resulting NS zone. In general, such names SHOULD NOT appear in the nodelist.
has always seemed technically unfounded (or at least the unarticulated "any other method" statement) to me. Does it mean that I can use the INA:fido.sibptus.ru flag all right, but cannot use the INA:node49.net5005.sibptus.ru flag? Why?
