IPv6 deployment for hosting and developers

From Rixort Wiki
Revision as of 08:37, 10 September 2020 by Paul (Sọ̀rọ̀ | contribs)
Jump to navigation Jump to search

Talk on the implications of deploying IPv6 for hosting platforms and developers.

Rough notes

  • Stats on incoming traffic from hosting providers
  • Stats on outgoing traffic from ISPs(?)
  • Percentage of sites running IPv6
  • Percentage of other services running IPv6

Problems

  • Adding AAAA records 'breaks' SSH.
  • Mail over IPv6 without SPF and DKIM stops delivery to large mail providers (e.g. Google).
  • If multiple protocols are available, which should be preferred? Linux seems to go for IPv6 first, but any which prefer IPv4 will never see the v6 service.

Competition concerns

  • 'Buy IPv4 addresses, they're not making them anymore'
  • RIPE 733: "The size of the allocation made will be exactly one /24.", "The sum of all allocations made to a single LIR by the RIPE NCC is limited to a maximum of 256 IPv4 addresses (a single /24). If this allocation limit has been reached or exceeded, an LIR cannot request an IPv4 allocation under this policy."
Retrieved from ‘https://wiki.rixort.com/index.php?title=IPv6_deployment_for_hosting_and_developers&oldid=922’