tHeWiZaRdOfDoS, on 09 August 2013 - 10:58 AM, said:
Sure about that?
Why adding an additional tag, a 32 bit community tag have more than enough place for SCT.
And for compatibility reasons I will add to Neo whatever SCT version gets agreed upon as community standard, in preparation for that I already commented out the RangeMaps so that once I add that bis again with the selected SCT implementation there will be no Neos around still using the old one.
tHeWiZaRdOfDoS, on 09 August 2013 - 10:58 AM, said:
First of all you can use IPv6 with servers, and petermrg is providing the server software for that.
About NeoKad, the licence is not a legal/fundamental problem, It is perfectly fine to distribute an eMule application binary together with a NeoKad service binary. Its only an ideological problem for those whom make it a problem for them selves.
And It will work as expected, as I explained in the same thread.
Lets be honest now you have 2 arguments form authority, and non of the two can in any way prove his point its a mater of personal preference hose argument you believe more.
An simple yet important IPv6 extension that can be added, is to keep Kad IPv4 only but let NATed the users publish their open IPv6 address so that the client can work for sharing as a normal HighID client.
Anyway as I posted before, I really don't care, we can add a full tag for each feature.
But I think we should at least Keep IPv6 and SCT in the same tag as ExtSX and NatT, espetialy that Ext SX is also needed for IPv6, that as explained above can be used good without the need for a IPv6 kad.
David X.