<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: World IPv6 Launch 6.6.2012</title>
	<atom:link href="http://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Sun, 05 Apr 2026 18:35:45 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1853873</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sun, 18 May 2025 12:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1853873</guid>
		<description><![CDATA[IT: &quot;Hey boss? I want to enable IPv6 on our network.&quot;
Boss: &quot;How long will it take?
IT: &quot;A few months probably from IT, probably 3-4 sprints from Dev to get all the legacy apps updated.&quot;
Boss: &quot;Will it make things simpler?&quot;
IT: &quot;No, it&#039;ll be at least twice as complex.&quot;
Boss: &quot;Will it make things cheaper?&quot;
IT: &quot;We&#039;ll save a few dozen dollars a month on IPv4 addresses, but no, we will need to buy some new hardware and some staff need to be trained.&quot;
Boss: &quot;Will our customers notice and appreciate it?&quot;
IT: &quot;Nope. They won&#039;t notice a difference.&quot;
Boss: &quot;Will it make us more secure?
IT: &quot;Eh, maybe in some trivial cases, if you ignore the recent high-severity IPv6 CVEs in Windows.&quot;
Boss: &quot;Since IPv6 adds encryption, can we do away with TLS?&quot;
IT: &quot;No, we still need that.&quot;
Boss: &quot;Will it add functionality?&quot;
IT: &quot;Yes, now all our internal servers will be directly addressable from anywhere on the internet and employees in theory can connect directly to any server without a VPN.&quot;
Boss: &quot;Do we want them to do that?&quot;
IT: &quot;No, our security policy says they must connect to the VPN and then use MFA against our PAM server to broker a connection on their behalf to the intentionally isolated network segment where those servers live.&quot;
Boss: &quot;Is this urgent because we running out of IPs?&quot;
IT: &quot;No, in fact we use less IPs than ever because all our servers are behind SNI capable load-balancers and Cloudflare&quot;
Boss: &quot;Can we get rid of NAT? Have nothing at all on our perimeter?&quot;
IT: &quot;Well, sort of, but now we need NPTv6 to translate prefixes on the network boundary so our complex internal network isn&#039;t wholly addressed by our ISP which might change&quot;
Boss: &quot;Well, how much time will you save without NAT?&quot;
IT: &quot;About 20 minutes a year&quot;
Boss: &quot;Ah, but FTP will be simpler!&quot;
IT: &quot;Yes, but FTP is a terrible protocol so we changed to SFTP years ago.&quot;

Gee, I wonder why it hasn&#039;t taken off in a lot of businesses.]]></description>
		<content:encoded><![CDATA[<p>IT: &#8220;Hey boss? I want to enable IPv6 on our network.&#8221;<br />
Boss: &#8220;How long will it take?<br />
IT: &#8220;A few months probably from IT, probably 3-4 sprints from Dev to get all the legacy apps updated.&#8221;<br />
Boss: &#8220;Will it make things simpler?&#8221;<br />
IT: &#8220;No, it&#8217;ll be at least twice as complex.&#8221;<br />
Boss: &#8220;Will it make things cheaper?&#8221;<br />
IT: &#8220;We&#8217;ll save a few dozen dollars a month on IPv4 addresses, but no, we will need to buy some new hardware and some staff need to be trained.&#8221;<br />
Boss: &#8220;Will our customers notice and appreciate it?&#8221;<br />
IT: &#8220;Nope. They won&#8217;t notice a difference.&#8221;<br />
Boss: &#8220;Will it make us more secure?<br />
IT: &#8220;Eh, maybe in some trivial cases, if you ignore the recent high-severity IPv6 CVEs in Windows.&#8221;<br />
Boss: &#8220;Since IPv6 adds encryption, can we do away with TLS?&#8221;<br />
IT: &#8220;No, we still need that.&#8221;<br />
Boss: &#8220;Will it add functionality?&#8221;<br />
IT: &#8220;Yes, now all our internal servers will be directly addressable from anywhere on the internet and employees in theory can connect directly to any server without a VPN.&#8221;<br />
Boss: &#8220;Do we want them to do that?&#8221;<br />
IT: &#8220;No, our security policy says they must connect to the VPN and then use MFA against our PAM server to broker a connection on their behalf to the intentionally isolated network segment where those servers live.&#8221;<br />
Boss: &#8220;Is this urgent because we running out of IPs?&#8221;<br />
IT: &#8220;No, in fact we use less IPs than ever because all our servers are behind SNI capable load-balancers and Cloudflare&#8221;<br />
Boss: &#8220;Can we get rid of NAT? Have nothing at all on our perimeter?&#8221;<br />
IT: &#8220;Well, sort of, but now we need NPTv6 to translate prefixes on the network boundary so our complex internal network isn&#8217;t wholly addressed by our ISP which might change&#8221;<br />
Boss: &#8220;Well, how much time will you save without NAT?&#8221;<br />
IT: &#8220;About 20 minutes a year&#8221;<br />
Boss: &#8220;Ah, but FTP will be simpler!&#8221;<br />
IT: &#8220;Yes, but FTP is a terrible protocol so we changed to SFTP years ago.&#8221;</p>
<p>Gee, I wonder why it hasn&#8217;t taken off in a lot of businesses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1853871</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sun, 18 May 2025 11:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1853871</guid>
		<description><![CDATA[IPv4 has a pretty long history, and despite signals suggesting that its impending replacement would become the norm any day now from the early 2010s, it&#039;s still sticking around. IPv6 was developed to combat the clear problem that would soon be faced by IPv4, yet the current state of IPv6 adoption (globally and by regions and industries) isn&#039;t where it was predicted to be. There was always going to be a transition period, but there have been a number of barriers slowing its deployment,

https://www.xda-developers.com/ipv4-meant-dead-happening-ipv6/?fbclid=IwY2xjawKWoFFleHRuA2FlbQIxMQABHtBDynInwQ8D1EFVpTI0JBqEx4l1MnYj9e0Z0aFyZcb0Mijig1fppENRb8Qj_aem_LQC6WNvelQrQ9iokI0fNUw]]></description>
		<content:encoded><![CDATA[<p>IPv4 has a pretty long history, and despite signals suggesting that its impending replacement would become the norm any day now from the early 2010s, it&#8217;s still sticking around. IPv6 was developed to combat the clear problem that would soon be faced by IPv4, yet the current state of IPv6 adoption (globally and by regions and industries) isn&#8217;t where it was predicted to be. There was always going to be a transition period, but there have been a number of barriers slowing its deployment,</p>
<p><a href="https://www.xda-developers.com/ipv4-meant-dead-happening-ipv6/?fbclid=IwY2xjawKWoFFleHRuA2FlbQIxMQABHtBDynInwQ8D1EFVpTI0JBqEx4l1MnYj9e0Z0aFyZcb0Mijig1fppENRb8Qj_aem_LQC6WNvelQrQ9iokI0fNUw" rel="nofollow">https://www.xda-developers.com/ipv4-meant-dead-happening-ipv6/?fbclid=IwY2xjawKWoFFleHRuA2FlbQIxMQABHtBDynInwQ8D1EFVpTI0JBqEx4l1MnYj9e0Z0aFyZcb0Mijig1fppENRb8Qj_aem_LQC6WNvelQrQ9iokI0fNUw</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1853869</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sun, 18 May 2025 11:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1853869</guid>
		<description><![CDATA[IPv4 was meant to be dead within a decade; what&#039;s happening with IPv6?
https://www.xda-developers.com/ipv4-meant-dead-happening-ipv6/?fbclid=IwY2xjawKWoFFleHRuA2FlbQIxMQABHtBDynInwQ8D1EFVpTI0JBqEx4l1MnYj9e0Z0aFyZcb0Mijig1fppENRb8Qj_aem_LQC6WNvelQrQ9iokI0fNUw

In the early 1990s, internet engineers sounded the alarm: the pool of numeric addresses that identify every device online was not infinite. IPv4, the fourth version of the Internet Protocol, used 32-bit addresses, about 4.3 billion unique numbers, which, at the dawn of the internet, seemed unimaginably large. Yet as the internet exploded in the 1990s and 2000s, experts predicted those addresses would soon run out. A new protocol, IPv6, was devised and hailed as the solution, with exhaustion of IPv4 addresses leading many to expect IPv4&#039;s replacement within a decade. Fast-forward to today, fourteen years after IANA exhausted its unassigned pool of IPv4 addresses, and IPv4 is still very much alive, while IPv6 adoption has been a slow uphill climb.]]></description>
		<content:encoded><![CDATA[<p>IPv4 was meant to be dead within a decade; what&#8217;s happening with IPv6?<br />
<a href="https://www.xda-developers.com/ipv4-meant-dead-happening-ipv6/?fbclid=IwY2xjawKWoFFleHRuA2FlbQIxMQABHtBDynInwQ8D1EFVpTI0JBqEx4l1MnYj9e0Z0aFyZcb0Mijig1fppENRb8Qj_aem_LQC6WNvelQrQ9iokI0fNUw" rel="nofollow">https://www.xda-developers.com/ipv4-meant-dead-happening-ipv6/?fbclid=IwY2xjawKWoFFleHRuA2FlbQIxMQABHtBDynInwQ8D1EFVpTI0JBqEx4l1MnYj9e0Z0aFyZcb0Mijig1fppENRb8Qj_aem_LQC6WNvelQrQ9iokI0fNUw</a></p>
<p>In the early 1990s, internet engineers sounded the alarm: the pool of numeric addresses that identify every device online was not infinite. IPv4, the fourth version of the Internet Protocol, used 32-bit addresses, about 4.3 billion unique numbers, which, at the dawn of the internet, seemed unimaginably large. Yet as the internet exploded in the 1990s and 2000s, experts predicted those addresses would soon run out. A new protocol, IPv6, was devised and hailed as the solution, with exhaustion of IPv4 addresses leading many to expect IPv4&#8242;s replacement within a decade. Fast-forward to today, fourteen years after IANA exhausted its unassigned pool of IPv4 addresses, and IPv4 is still very much alive, while IPv6 adoption has been a slow uphill climb.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1847995</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Mon, 10 Mar 2025 08:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1847995</guid>
		<description><![CDATA[https://hackaday.com/2025/03/09/ipv4-ipv6-hey-what-happened-to-ipv5/]]></description>
		<content:encoded><![CDATA[<p><a href="https://hackaday.com/2025/03/09/ipv4-ipv6-hey-what-happened-to-ipv5/" rel="nofollow">https://hackaday.com/2025/03/09/ipv4-ipv6-hey-what-happened-to-ipv5/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1840466</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 04 Dec 2024 08:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1840466</guid>
		<description><![CDATA[https://hackaday.com/2024/12/03/a-month-without-ipv4-is-like-a-month-without/]]></description>
		<content:encoded><![CDATA[<p><a href="https://hackaday.com/2024/12/03/a-month-without-ipv4-is-like-a-month-without/" rel="nofollow">https://hackaday.com/2024/12/03/a-month-without-ipv4-is-like-a-month-without/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1838644</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Mon, 04 Nov 2024 13:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1838644</guid>
		<description><![CDATA[The realities of building an IPv6-only city
https://blog.apnic.net/2024/10/29/the-realities-of-building-an-ipv6-only-city/

As previously discussed in this post, Xiong’an New Area (Xiong’an), a pilot city established in 2017 about 100 kilometres west of Beijing, aims to be a model for future digital cities, built with IPv6-only infrastructure from the start. To achieve this, the local government is prioritizing IPv6 in its top-level planning, designing for the deployment of 198,000 sensors per square kilometre, and supporting over 1 million Internet of Things (IoT) devices per square kilometre. This post will look at the lessons the Xiong’an team has learned so far from building this IPv6-only city.]]></description>
		<content:encoded><![CDATA[<p>The realities of building an IPv6-only city<br />
<a href="https://blog.apnic.net/2024/10/29/the-realities-of-building-an-ipv6-only-city/" rel="nofollow">https://blog.apnic.net/2024/10/29/the-realities-of-building-an-ipv6-only-city/</a></p>
<p>As previously discussed in this post, Xiong’an New Area (Xiong’an), a pilot city established in 2017 about 100 kilometres west of Beijing, aims to be a model for future digital cities, built with IPv6-only infrastructure from the start. To achieve this, the local government is prioritizing IPv6 in its top-level planning, designing for the deployment of 198,000 sensors per square kilometre, and supporting over 1 million Internet of Things (IoT) devices per square kilometre. This post will look at the lessons the Xiong’an team has learned so far from building this IPv6-only city.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1838469</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 30 Oct 2024 12:48:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1838469</guid>
		<description><![CDATA[The IPv6 transition
https://blog.apnic.net/2024/10/22/the-ipv6-transition/?fbclid=IwY2xjawGKt5FleHRuA2FlbQIxMQABHQPzWhd0QWpbblT7CHzSk3mYwOxfmpiAiHOYw-RKYMNRVZ2iBqQeqXcwLw_aem_Zf53vAyQmBtd3pOuk6QGZg]]></description>
		<content:encoded><![CDATA[<p>The IPv6 transition<br />
<a href="https://blog.apnic.net/2024/10/22/the-ipv6-transition/?fbclid=IwY2xjawGKt5FleHRuA2FlbQIxMQABHQPzWhd0QWpbblT7CHzSk3mYwOxfmpiAiHOYw-RKYMNRVZ2iBqQeqXcwLw_aem_Zf53vAyQmBtd3pOuk6QGZg" rel="nofollow">https://blog.apnic.net/2024/10/22/the-ipv6-transition/?fbclid=IwY2xjawGKt5FleHRuA2FlbQIxMQABHQPzWhd0QWpbblT7CHzSk3mYwOxfmpiAiHOYw-RKYMNRVZ2iBqQeqXcwLw_aem_Zf53vAyQmBtd3pOuk6QGZg</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1836012</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 20 Sep 2024 09:42:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1836012</guid>
		<description><![CDATA[https://vinfrastructure.it/2024/08/critical-vulnerability-in-ipv6-protocol-on-windows-systems/]]></description>
		<content:encoded><![CDATA[<p><a href="https://vinfrastructure.it/2024/08/critical-vulnerability-in-ipv6-protocol-on-windows-systems/" rel="nofollow">https://vinfrastructure.it/2024/08/critical-vulnerability-in-ipv6-protocol-on-windows-systems/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1836011</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 20 Sep 2024 09:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1836011</guid>
		<description><![CDATA[https://blog.lacnic.net/en/five-ipv6-trends-for-2024/]]></description>
		<content:encoded><![CDATA[<p><a href="https://blog.lacnic.net/en/five-ipv6-trends-for-2024/" rel="nofollow">https://blog.lacnic.net/en/five-ipv6-trends-for-2024/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/05/world-ipv6-launch-6-6-2012/comment-page-1/#comment-1836010</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Fri, 20 Sep 2024 09:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11673#comment-1836010</guid>
		<description><![CDATA[https://www.google.com/url?sa=t&amp;source=web&amp;rct=j&amp;opi=89978449&amp;url=https://www.rolandberger.com/publications/publication_pdf/Global-IPv6-Development-Report-2024_EN.pdf&amp;ved=2ahUKEwi4wPuwm9GIAxXJBRAIHagUAbwQFnoECBAQAQ&amp;usg=AOvVaw2iPFd-522P59rfEiYcDXPr]]></description>
		<content:encoded><![CDATA[<p><a href="https://www.google.com/url?sa=t&#038;source=web&#038;rct=j&#038;opi=89978449&#038;url=https://www.rolandberger.com/publications/publication_pdf/Global-IPv6-Development-Report-2024_EN.pdf&#038;ved=2ahUKEwi4wPuwm9GIAxXJBRAIHagUAbwQFnoECBAQAQ&#038;usg=AOvVaw2iPFd-522P59rfEiYcDXPr" rel="nofollow">https://www.google.com/url?sa=t&#038;source=web&#038;rct=j&#038;opi=89978449&#038;url=https://www.rolandberger.com/publications/publication_pdf/Global-IPv6-Development-Report-2024_EN.pdf&#038;ved=2ahUKEwi4wPuwm9GIAxXJBRAIHagUAbwQFnoECBAQAQ&#038;usg=AOvVaw2iPFd-522P59rfEiYcDXPr</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
