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,448 of 4,612    |
|    Victor Sudakov to Benny Pedersen    |
|    2:5057/53    |
|    05 Jul 18 21:59:54    |
      Dear Benny,              05 Jul 18 06:46, you wrote to me:               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        BP>>> with binkp.net listnings               VS>> Last time I checked, binkp.net did not rely solely on DDN, you        VS>> could enter any RR for your node manually via a Web page (which I        VS>> did long ago). So if you have created a RR for your node in        VS>> binkp.net, there should be no technical problem using a        VS>> binkp.net-derived name in the nodelist flags.               BP> i did not know its a webpage aswell, if the web lets users create rr        BP> that are not in nodelist, hmm :)              Yes, it does. It started this way. It is very convenient, and works as a       regular DNS zone with a Web editor.              Of course, if you try to register at https://binkp.net/ as 2:5005/49, a       Netmail with a confirmation code will be sent to 2:5005/49. So it's pretty       safe, you can create any RR only for your own node.               VS>> The requirement in FTS-5004               VS>> If the INA flag (or any of the protocol flags) of any node        VS>> carries host name built from the FTN address using DDN or any        VS>> other method, that node MUST be skipped and MUST NOT appear in        VS>> resulting NS zone. In general, such names SHOULD NOT appear in        VS>> the nodelist.               BP> +1               VS>> has always seemed technically unfounded (or at least the        VS>> unarticulated "any other method" statement) to me. Does it mean        VS>> that I can use the INA:fido.sibptus.ru flag all right, but cannot        VS>> use the INA:node49.net5005.sibptus.ru flag? Why?               BP> it does not work since binkd only handle single root-domain in        BP> binkd.cfg               BP> try in cfg:              I'm not going to put "root-domain sibptus.ru" in binkd's config, that's a       silly idea. I mean that a sysop has the right to put any DNS name she finds       necessary into the INA flag, no matter if it's derived from the FTN address or       not. A nodelist has no concept of "root-domain", a DNS name is just a DNS name.              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