-
New Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
AS A user with only IPv6 connectivity
I WANT to be able to use MusicBrainz just as well as a user who only has IPv4 connectivity
Worth having a think about what would be needed to make this happen.
DNS
- Do our DNS zones support AAAA records?
- Are our NS's reachable by IPv6?
everydns isn't
ns1.digitalwest.net isn't
ns2.digitalwest.net is
- Are all the other dependent DNS servers reachable by IPv6?
- Also check CNAMEs pointing to external domains: their NSs, their dependent NSs, the name itself, ...
Hosting
- DW servers (or at least, user endpoints) need IPv6 addresses
todo
- Non-DW user endpoints (OSL@OSU, hefty, ...?) need IPv6 addresses
ftp.musicbrainz.org => musicbrainz.osuosl.org => ftp.osuosl.org => no AAAA
rsync.musicbrainz.org => rsync.osuosl.org => no AAAA
Infrastructure
- carl/lenny nginx. Does it "just work"?
- carl/lenny incoming connections SMTP (etc)
- Does webalizer support IPv6?
Software
- Is mb_server limited to IPv4 only?
- How would mb_server per-IP rate limiting work?
- Client apps (Picard etc), as long as they use IPv4/6-agnostic code, it should hopefully "just work".
No progress, but i'll start on this soon, at least for underlying infrastructure.
We can start to:
But many MeB apps aren't IPv6 ready yet, a full audit is needed.