* Dan Geist <[email protected]>

> Is that the reason for the pool.ntp.org being ipv4-only and
> 2.pools.ntp.org having v4 and v6 together?

Ask Bjørn Hansen stated back in March that the reason why not all the
service hostnames are dual-stacked is, quote, «We need more IPv6
enabled servers. Many countries have very sparse IPv6 coverage in the
pool.»

http://lists.ntp.org/pipermail/pool/2015-March/007284.html

However, when I tried to verify this claim I found that the percentage
of IPv6-capable NTP servers in every country the amount of IPv6-enabled
pool servers exceed the amount IPv6-enabled end users in that country.
Thus enabling IPv6 for these countries would lead to a net increase in
available NTP server capacity as IPv6 users will be able to migrate to
the IPv6 servers, freeing up capacity on the IPv4 servers. Because the
share of IPv6 pool servers is greater than the share of IPv6 users in
the countries in question, there will be fewer users per IPv6 server
too.

http://lists.ntp.org/pipermail/pool/2015-March/007313.html

Belgium is the exception to the above. In this country the percentage
of IPv6-enabled end users slightly exceeds the percentage of
IPv6-enabled pool servers. However, enabling dual-stack would be a net
benefit also for Belgium. This is because the pool clients are
currently all ganging up on the IPv4 pool servers, while the IPv6
servers are left to mostly idle. Dual-stacking will thus ensure the
IPv6 servers are utilised better. As a result, the clients - regardless
of them using IPv4 and IPv6 - will need to share their assigned pool
server with fewer clients than what is currently the case.

http://lists.ntp.org/pipermail/pool/2015-March/007314.html

So to me the numbers seem to suggest that dual-stacking all of the NTP
pool would constitute a net win for performance and load sharing.
Unfortunately however, the March thread died off without any further
comment from anyone who would be in a position to actually implement
such a change. :-(

Tore
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool

Reply via email to