IPv6 deployment for hosting and developers - Revision history

Paul at 13:32, 26 September 2020

2020-09-26T13:32:11Z

← Older revision		Revision as of 13:32, 26 September 2020
Line 11:		Line 11:
	* BBC iPlayer?		* BBC iPlayer?
	* [https://blog.apnic.net/2020/08/26/netflix-over-ipv6-a-longitudinal-study/ Netflix]		* [https://blog.apnic.net/2020/08/26/netflix-over-ipv6-a-longitudinal-study/ Netflix]
			* Digital Ocean - IPv6 but not on load balancers?
			* Big CDNs?

	== Topics ==		== Topics ==

Paul: /* Links */

2020-09-25T14:53:19Z

Links

← Older revision		Revision as of 14:53, 25 September 2020
Line 73:		Line 73:
	* [https://www.youtube.com/watch?v=GK6vl5z-8NY UKNOF43 - Psychology of IPv6]		* [https://www.youtube.com/watch?v=GK6vl5z-8NY UKNOF43 - Psychology of IPv6]
	* [https://www.youtube.com/watch?v=ZJhIeiWx1xg UKNOF36 - IPv6-only Hosting Panel Discussion]		* [https://www.youtube.com/watch?v=ZJhIeiWx1xg UKNOF36 - IPv6-only Hosting Panel Discussion]
			* [https://tv.theiet.org/?videoid=9485 BBC IPv6 update]

	[[Category:Talks]]		[[Category:Talks]]

Paul: /* Links */

2020-09-25T08:39:17Z

Links

← Older revision		Revision as of 08:39, 25 September 2020
Line 69:		Line 69:
	* [https://www.netweaver.uk/ipv6-use-2019/ Netweaver: IPv6 use in 2019]		* [https://www.netweaver.uk/ipv6-use-2019/ Netweaver: IPv6 use in 2019]
	* [https://www.mythic-beasts.com/ipv6/health-check Mythic Beasts IPv6 health check] - phpdeveloper.org.uk gets 11/11		* [https://www.mythic-beasts.com/ipv6/health-check Mythic Beasts IPv6 health check] - phpdeveloper.org.uk gets 11/11
			* [https://www.youtube.com/watch?v=91hN3PvYUrc UKNOF34 - IPv6 Only Hosting]
			* [https://www.youtube.com/watch?v=-qbTWlG5VI4 UKNOF36 - Single Stack IPv6 Hosting for the masses]
			* [https://www.youtube.com/watch?v=GK6vl5z-8NY UKNOF43 - Psychology of IPv6]
			* [https://www.youtube.com/watch?v=ZJhIeiWx1xg UKNOF36 - IPv6-only Hosting Panel Discussion]

	[[Category:Talks]]		[[Category:Talks]]

Paul: /* Problems */

2020-09-25T06:59:37Z

Problems

← Older revision		Revision as of 06:59, 25 September 2020
Line 39:		Line 39:
	* DNS - if someone has a CNAME which points at one of your hostnames and you add AAAA records to that hostname, all the CNAMEs get it too (e.g. www.example.com CNAME host.myhost.com, add AAAA to host.myhost.com, www.example.com also gets AAAA)		* DNS - if someone has a CNAME which points at one of your hostnames and you add AAAA records to that hostname, all the CNAMEs get it too (e.g. www.example.com CNAME host.myhost.com, add AAAA to host.myhost.com, www.example.com also gets AAAA)
	* To date has mostly been an ISP problem, e.g. no big hosting providers represented on the IPv6 Council organisation		* To date has mostly been an ISP problem, e.g. no big hosting providers represented on the IPv6 Council organisation
			* Capturing IP address data and passing it on to third parties who might not have heard of v6

	== Competition concerns ==		== Competition concerns ==

Paul: /* Problems */

2020-09-25T06:57:11Z

Problems

← Older revision		Revision as of 06:57, 25 September 2020
Line 38:		Line 38:
	* More customer co-operation required (c.f. ISP where you can often switch it on silently, especially if you manage their equipment or can push out updates)		* More customer co-operation required (c.f. ISP where you can often switch it on silently, especially if you manage their equipment or can push out updates)
	* DNS - if someone has a CNAME which points at one of your hostnames and you add AAAA records to that hostname, all the CNAMEs get it too (e.g. www.example.com CNAME host.myhost.com, add AAAA to host.myhost.com, www.example.com also gets AAAA)		* DNS - if someone has a CNAME which points at one of your hostnames and you add AAAA records to that hostname, all the CNAMEs get it too (e.g. www.example.com CNAME host.myhost.com, add AAAA to host.myhost.com, www.example.com also gets AAAA)
			* To date has mostly been an ISP problem, e.g. no big hosting providers represented on the IPv6 Council organisation

	== Competition concerns ==		== Competition concerns ==

Paul: /* Problems */

2020-09-25T06:53:03Z

Problems

← Older revision		Revision as of 06:53, 25 September 2020
Line 21:		Line 21:
	== Problems ==		== Problems ==

	* Why is IPv6 deployment so slow?		* Why is IPv6 deployment so slow? It has been around for 20+ years.
	* Adding AAAA records 'breaks' SSH - interactive stopped working, so did automatic deployments, SSH wouldn't listen on v6 because of firewall, add <code>AddressFamily inet</code> to <code>.ssh/config</code>		* Adding AAAA records 'breaks' SSH - interactive stopped working, so did automatic deployments, SSH wouldn't listen on v6 because of firewall, add <code>AddressFamily inet</code> to <code>.ssh/config</code>
	* Mail over IPv6 without SPF and DKIM stops delivery to large mail providers (e.g. Google).		* Mail over IPv6 without SPF and DKIM stops delivery to large mail providers (e.g. Google).

Paul: /* Competition concerns */

2020-09-25T06:52:50Z

Competition concerns

← Older revision		Revision as of 06:52, 25 September 2020
Line 43:		Line 43:
	* [https://www.ripe.net/publications/docs/ripe-733 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."		* [https://www.ripe.net/publications/docs/ripe-733 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."
	* Who regulates RIPE et al? They have power to allocate a scarce and valuable resource.		* Who regulates RIPE et al? They have power to allocate a scarce and valuable resource.
			* Do we need regulation to force ISPs to deploy v6 (yes) - would allow v6-only hosting providers

	== Advice ==		== Advice ==

Paul: /* Problems */

2020-09-19T13:42:57Z

Problems

← Older revision		Revision as of 13:42, 19 September 2020
Line 24:		Line 24:
	* Adding AAAA records 'breaks' SSH - interactive stopped working, so did automatic deployments, SSH wouldn't listen on v6 because of firewall, add <code>AddressFamily inet</code> to <code>.ssh/config</code>		* Adding AAAA records 'breaks' SSH - interactive stopped working, so did automatic deployments, SSH wouldn't listen on v6 because of firewall, add <code>AddressFamily inet</code> to <code>.ssh/config</code>
	* Mail over IPv6 without SPF and DKIM stops delivery to large mail providers (e.g. Google).		* Mail over IPv6 without SPF and DKIM stops delivery to large mail providers (e.g. Google).
	* Harder to manage things like IP reputation and IP ACLs (where IPv4 limited address space is an advantage in many ways).		* Harder to manage things like IP reputation and IP ACLs (where IPv4 limited address space is an advantage in many ways). Enabling v6 and using the wrong prefix = locked out of my Nextcloud instance.
	* Apache <code>VirtualHost *:80</code> includes v4 and v6, whereas nginx requires you to use <code>listen 80</code> and <code>listen [::]:80</code>		* Apache <code>VirtualHost *:80</code> includes v4 and v6, whereas nginx requires you to use <code>listen 80</code> and <code>listen [::]:80</code>
	* 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.		* 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.

Paul: /* Problems */

2020-09-19T13:42:21Z

Problems

← Older revision		Revision as of 13:42, 19 September 2020
Line 24:		Line 24:
	* Adding AAAA records 'breaks' SSH - interactive stopped working, so did automatic deployments, SSH wouldn't listen on v6 because of firewall, add <code>AddressFamily inet</code> to <code>.ssh/config</code>		* Adding AAAA records 'breaks' SSH - interactive stopped working, so did automatic deployments, SSH wouldn't listen on v6 because of firewall, add <code>AddressFamily inet</code> to <code>.ssh/config</code>
	* Mail over IPv6 without SPF and DKIM stops delivery to large mail providers (e.g. Google).		* Mail over IPv6 without SPF and DKIM stops delivery to large mail providers (e.g. Google).
	* Harder to manage things like IP reputation (where IPv4 limited address space is an advantage in many ways).		* Harder to manage things like IP reputation and IP ACLs (where IPv4 limited address space is an advantage in many ways).
	* Apache <code>VirtualHost *:80</code> includes v4 and v6, whereas nginx requires you to use <code>listen 80</code> and <code>listen [::]:80</code>		* Apache <code>VirtualHost *:80</code> includes v4 and v6, whereas nginx requires you to use <code>listen 80</code> and <code>listen [::]:80</code>
	* 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.		* 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.

Paul at 11:39, 19 September 2020

2020-09-19T11:39:49Z

← Older revision		Revision as of 11:39, 19 September 2020
Line 11:		Line 11:
	* BBC iPlayer?		* BBC iPlayer?
	* [https://blog.apnic.net/2020/08/26/netflix-over-ipv6-a-longitudinal-study/ Netflix]		* [https://blog.apnic.net/2020/08/26/netflix-over-ipv6-a-longitudinal-study/ Netflix]

			== Topics ==

			* What's the current state of play
			* Competition issues
			* What are some of the problems deploying v6
			* How to avoid the problems

	== Problems ==		== Problems ==