(yes: this is mostly the same text as I posted for Bug #241305 because the same problems apply)
This issue has been reported over 4 years ago, and has become a serious real-life problem for organisations. IANA (global supply) ran out of IPv4 addresses in February 2011. Shortly after that APNIC (Asia-Pacific supply) ran out. In September 2012 RIPE NCC (Europe/Middle-East/parts of Asia) ran out of IPv4 addresses.
Being able to run an IPv6-only network is increasingly important. Sure, hacks like NAT64/DNS64 exist. They form performance bottlenecks and single-points-of-failure in networks. Having native IPv6 support on a service like ntp.ubuntu.com is important.
The Canonical Sysadmins are notified of this issue, so I hope they take action as soon as possible. This is something that should have been fixed last year.
(yes: this is mostly the same text as I posted for Bug #241305 because the same problems apply)
This issue has been reported over 4 years ago, and has become a serious real-life problem for organisations. IANA (global supply) ran out of IPv4 addresses in February 2011. Shortly after that APNIC (Asia-Pacific supply) ran out. In September 2012 RIPE NCC (Europe/ Middle- East/parts of Asia) ran out of IPv4 addresses.
Being able to run an IPv6-only network is increasingly important. Sure, hacks like NAT64/DNS64 exist. They form performance bottlenecks and single- points- of-failure in networks. Having native IPv6 support on a service like ntp.ubuntu.com is important.
The Canonical Sysadmins are notified of this issue, so I hope they take action as soon as possible. This is something that should have been fixed last year.