<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

	<channel>

	<title>&#45; CircleID</title>
	<link>https://www.circleid.com/blogs/</link>
	<description>Postings from  on CircleID</description>
	<dc:language>en</dc:language>
	<dc:rights>Copyright 2026, unless where otherwise noted.</dc:rights>
	<dc:date>2026-04-30T19:14:00+00:00</dc:date>

	
	<item>
		<title> Shim6 Host-Based IPv6 Multihoming: Ready for Testing (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts87191_shim6_host_based_ipv6_multihoming</guid>
		<link>https://circleid.com/posts87191_shim6_host_based_ipv6_multihoming</link>
		<description><![CDATA[During the last decade, the Internet Engineering Task Force (IETF) has been designing IPv6 as a replacement for IPv4. Most of the initial benefits of IPv6 (security, QoS, autoconfiguration,...) have been ported to IPv4 and IPv6 deployment has been limited. However, thanks to the huge IPv6 addressing space, it is possible to design protocols and mechanisms that are more scalable and more powerful than with IPv4. A typical example is the multihoming problem. This problem occurs when a site is attached to several Internet Service providers... <a href="https://circleid.com/posts87191_shim6_host_based_ipv6_multihoming">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>