-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tony Hoyle wrote:
> As ipv6 usage grows more servers come online, so it > should never get to the point that ipv6.pool.ntp.org gets flooded. If we use a name like ipv6.pool.ntp.org, we have lost. You seem to be one of those people who has to keep IPv6 and IPv4 apart in their minds. If you do that you actually make it much harder for the rest of us. All that needs to happen is the ability to place AAAA records alongside the A records now served from the pools, and ensure that there are minimums of each present. Since I see 12 A records in the response to "dig pool.ntp.org a" right now, and I have all the data available (all NS servers in the response, as well as their addresses), it comes out to 388 bytes. You still want to stay below 512 bytes (unless EDNS0 is used, then the client says how big it can handle) so 512 = 388 = 124 bytes left. I believe each IPv6 address will add 26 bytes to the response, 2 for name pointer (compression and all), 4 TTL, 2 class, 2 type, and 16 for the IPv6 address itself. This means we could add 4 addresses easily, and if a few less A records were presented, more. Each A record removed would give us back approximately 16 bytes. - --Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGc1X7uzMQWQwZDN0RAmouAJ49iE0i6bayJOzIEAmLnQGez0jx7QCfcLwq 5Tkp1L4D5DB2xfHmE+T2Db8= =rOcj -----END PGP SIGNATURE----- _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
