Subj : FSP-1038.001
To   : Michiel van der Vlist
From : Alexey Vissarionov
Date : Tue Nov 05 2013 10:44:44

Good ${greeting_time}, Michiel!

04 Nov 2013 22:24:32, you wrote to All:

 MV> Publication:    FSP-1038
 MV> Revision:       1
 MV> Title:          The INO4 flag.

As I already told, it's useless.

When a system is IPv6-only, it may be listed using IP literal:

,9999,SysName,City,Sysop_Name,00-00-000000,300,CM,INA:[2001:0DB8::2:2:9999],IBN

So, as the IPv6 addresses are unlikely to be allocated dynamically (and thus changed frequently), this may work as desired.

One single not-really-a-problem raises only when the nodelist line contains INA:f.q.d.n flag, as the old mailers may be unable to detect EAI_ADDRFAMILY returned by getaddrinfo() or NO_ADDRESS returned by archaic gethostbyname()

Once faced, that may be solved by either:
1. Updating the mailer.
2. Checking that manually.

So leaving it up to sysops seems to be the best solution. And, of course, we should recommend checking for EAI_ADDRFAMILY to the developers. At least here:

* Originally in FTSC_PUBLIC
* Crossposted in IPV6

--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

.... :wq!
--- /bin/vi
 * Origin: http://openwall.com/Owl (2:5020/545)

.