Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    IPV6    |    The convoluted hot-mess that is IPV6    |    4,612 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,446 of 4,612    |
|    Victor Sudakov to Benny Pedersen    |
|    2:5057/53    |
|    05 Jul 18 12:08:42    |
      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        NA:fido.sibptus.ru flag all right, but cannot use the INA:node49       net5005.sibptus.ru flag? Why?              Victor Sudakov, VAS4-RIPE, VAS47-RIPN       --- GoldED+/BSD 1.1.5-b20160322-b20160322        * Origin: Ulthar (2:5005/49)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca