<?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>Stephane Bourque &#45; CircleID</title>
		<link>http://www.circleid.com/</link>
		<description>Postings from Stephane Bourque on CircleID</description>
		<dc:language>en</dc:language>
		<dc:rights>Copyright 2013, unless where otherwise noted.</dc:rights>
		<dc:date>2013-04-16T09:58:00-08:00</dc:date>
		

		
		<item>
			<title> What's the Best IPv6 Transition Option for You? (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/20130416_what_is_the_best_ipv6_transition_option_for_you</guid>
			<link>http://www.circleid.com/posts/20130416_what_is_the_best_ipv6_transition_option_for_you</link>
			<description><![CDATA[After decades of talk, the time for IPv6 has finally arrived. There are several transition options available, but whatever approach you choose, the challenge will be to make sure that your subscribers don't experience a reduction in quality of service. IPv4 is likely to co-exist with IPv6 for some time, so a native dual-stack migration strategy will be the best transition option for most providers... With dual-stack mode, there is no disruption to the service if a client requests an IPv4 address. <a href="http://www.circleid.com/posts/20130416_what_is_the_best_ipv6_transition_option_for_you">More...</a>]]></description>
			<dc:date>2013-04-16T09:58:00-08:00</dc:date>
		</item>
		
		<item>
			<title> Cable in China (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/20130131_cable_in_china</guid>
			<link>http://www.circleid.com/posts/20130131_cable_in_china</link>
			<description><![CDATA[I'm writing this piece on the plane on my way back to Vancouver after a 12-day trip in China. I've written about China before, and every time I go, I understand and appreciate this complex country and culture a little more. If you think China is "up and coming," well, you might want to go and take a look for yourself. To be honest, I think they are already here. <a href="http://www.circleid.com/posts/20130131_cable_in_china">More...</a>]]></description>
			<dc:date>2013-01-31T12:12:00-08:00</dc:date>
		</item>
		
		<item>
			<title> The Year Ahead: Predictions for 2013 (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/20130103_the_year_ahead_predictions_for_2013</guid>
			<link>http://www.circleid.com/posts/20130103_the_year_ahead_predictions_for_2013</link>
			<description><![CDATA[I recently talked about the top trends of 2012. Well, now it's time for me to look into my crystal ball and predict the future. I believe that this year we'll see great developments when it comes to TR-069. I know you'll say that this was a trend last year, but I'm confident that 2013 is the year that this protocol will really shine. <a href="http://www.circleid.com/posts/20130103_the_year_ahead_predictions_for_2013">More...</a>]]></description>
			<dc:date>2013-01-03T14:09:00-08:00</dc:date>
		</item>
		
		<item>
			<title> Looking Back on 2012: What's in our Rearview Mirror? (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/looking_back_on_2012_whats_in_our_rearview_mirror</guid>
			<link>http://www.circleid.com/posts/looking_back_on_2012_whats_in_our_rearview_mirror</link>
			<description><![CDATA[Well, 2012 is almost over, and we can now reflect on the major events that hit our industry this year. If I had to choose the top three trends from the past 12 months, they would have to be: 1. Over-the-top (OTT) services; 2. IPv6 deployments (finally!); 3. TR-069 adoption. Let's examine each of these in more detail. <a href="http://www.circleid.com/posts/looking_back_on_2012_whats_in_our_rearview_mirror">More...</a>]]></description>
			<dc:date>2012-12-18T07:30:00-08:00</dc:date>
		</item>
		
	</channel>
</rss>