IPv6 (on AMS-IX) currently accounts for 20G/s of traffic at peak times compared to 2.8T/s overall. That said, the amount of traffic that IPv6 generates has almost quadrupled since August last year. Stating that IPv6 is not on the PSF's list of priorities is, as far as I'm concerned, short sighted. It doesn't have to work tomorrow but it should be on the list of things to get to.
PyPi not being available over IPv6 anymore is not "we're not willing to do extra work to enable it", it's a regression. I understand that this is not something the PSF can solve but it should at least push Fastly to roll out IPv6. -- Daniele Sluijters On 10 June 2014 12:20, Noah Kantrowitz <n...@coderanger.net> wrote: > Both, supporting IPv6 is not a priority and so no extra work will be done for > it. This is true across the board for all PSF services. > > --Noah > > On Jun 10, 2014, at 2:40 AM, Wichert Akkerman <wich...@wiggy.net> wrote: > >> I just noticed that my uploads to PyPI are now using IPv4 instead of IPv6. >> Looking closer it looks like PyPI is not reachable over IPv6 at all anymore, >> which is somewhat disappointing. Was dropping IPv6 a deliberate choice, or >> an unfortunate side-effect of switching to Fastly’s CDN? >> >> Regards, >> Wichert. >> _______________________________________________ >> Distutils-SIG maillist - Distutils-SIG@python.org >> https://mail.python.org/mailman/listinfo/distutils-sig > > > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig > -- Daniele Sluijters _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
