> My plan is to just enable AAAA records for "2.pool.ntp.org" (and
> 2.fedora.pool.ntp.org etc) and see how that goes.  Depending on the
> outcome, we can make a "ipv6.pool.ntp.org" IPv6-enabled or IPv6-only
> pool.

For the use case I envision (production-style support for v6-only
hosts), it doesn't really matter whether ipv6.pool is IPv6-enabled
or IPv6-only - the v6-only hosts would go only after AAAA records,
anyway.

It's just that I dislike the beta. label that you proposed at some
point as it indicates that it's *not* production-level. I don't
mind having *also* beta.pool.ntp.org, which would have the vision
of becoming the standard pool at some day - but then I'd like to see
some a-priori criterion as to when this beta installation would take
over the production installation (after one year? when there are
more than N servers in each region? ...)

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

Reply via email to