[wp-meta] [Making WordPress.org] #3090: WordPress.org API not accessible over IPv6
Making WordPress.org
noreply at wordpress.org
Tue Aug 15 02:04:50 UTC 2023
#3090: WordPress.org API not accessible over IPv6
-------------------------+-------------------------
Reporter: deaky | Owner: (none)
Type: enhancement | Status: closed
Priority: high | Milestone:
Component: API | Resolution: maybelater
Keywords: |
-------------------------+-------------------------
Changes (by dd32):
* status: reopened => closed
* resolution: => maybelater
Comment:
This is not something the Meta team has any control over at this point in
time. I'm re-closing this, purely as there's nothing actionable for the
Meta team at present.
The WordPress.org systems team DO have IPv6 plans, but at present there
are higher priority tasks and there's no widespread requirement for IPv6
connectivity.
Due to the size of traffic that WordPress.org see's (especially APIs) I
expect there'd also be concerns around rate limiting (as IPv6 would be 4x
the memory requirement, so 5x IPv4 for a dual-stack 4+6 limits).
If a host/DC is IPv6-only, they need to offer a NAT64 or DNS64 service,
[https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-
nat64-dns64.html such as what Amazon suggests for AWS].
This is for more than just WordPress.org, this is also needed for a
variety of other web services which are either unavailable over IPv6 or
simply have bad IPv6 routes.
There's a reason why desktops retry over IPv4/connect over both 4+6 and
use the first successful connection.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3090#comment:12>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list