On Thursday December 19 2013 20:32, you wrote to me:
MvdV>> What we need is a flag to signal that the node can not accept MvdV>> incoming calls via IPv4.
BP> no no no no no no, definaly no
Yes, yes yes, definitely yes.
MvdV>> See FSP-1038.001, the INO4 flag.
BP> is this writed from users that have ipv6 working ?, not via tunnels :(
It has nothing to do with IPv6 over a tunnel or native IPv6.
BP> nodelist should not solve ipv4/ipv6 problems ever !
Consider the following situation:
XYZZY is an IPv4 only node. XYZZY runs an IP cabable node, but XYXXY's software is IPv4 only. When doing a DNS lookup for a host name, XYZZY will only look for an IPv4 address. When the node that is to be called only has an IPv6 address, the DNS lookup will fail. And it will keep on failing. An example of such a setup is a classic POTS mailer like Frontdoor that is fooled into thinking it is making a classic modem connection, but actually talks over IP via a shim like Vmodem, Netserial or similar. Frontdoor can easily be configured to never attempt to call a node that carries an INO4 flag.
Without such a flag, it is not possible to stop it from attempting to call an IPv6 only node.
