Subj : Re: 2:46/5555
To   : Michiel van der Vlist
From : Nodelist Police Commissioner
Date : Mon May 30 2022 15:43:54

Hello Michiel,

On 2022-05-30 15:22:08, you wrote to me:

 NC>> There is a DO4:binkp.net flag for the region, so not necessarily
 NC>> wrong.

 MvdV> From FTS-5004.001:

 MvdV>  4. NS zone generation.

 MvdV>  The only valid source for DDN records is FTS-5000 world nodelist.
 MvdV>  Data from partial (network etc.) segments SHOULD NOT appear in
 MvdV>  DDN until they get into world nodelist. Data from any sources
 MvdV>  other than nodelist MUST NOT appear in DDN NS zones.

 MvdV>  To be published in DDN, the node MUST have at least one Internet
 MvdV>  address published in the nodelist. The IP protocol flags or the
 MvdV>  INA flag SHOULD be used for that purpose, but some nodes use the
 MvdV>  system name instead, so the implementations SHOULD look for a
 MvdV>  hostname in the protocol flag, the INA flag and the system name
 MvdV>  field in that order.

 MvdV> So no host name in the nodelist is definitely wrong.

I can't argue with the standards. But in practice since nodes can enter a nodes connection address directly at binkp.net, you can have a fF.nN.zZ.binkp.net host name resolve, without there being a connection address published in the nodelist...

The option to enter the connection address directly at https://www.binkp.net/ shouldn't exist if you follow the standard described above.

Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: NPC Station (2:280/464)

.