<?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-05-02T15:50:00+00:00</dc:date>

	
	<item>
		<title> Network Dis-Aggregation and SDN: Different, But Related (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20170317_network_dis_aggregation_and_sdn_different_but_related</guid>
		<link>https://circleid.com/posts20170317_network_dis_aggregation_and_sdn_different_but_related</link>
		<description><![CDATA[Two of the hottest trends in networking today are network dis-aggregation and SDN. This is great for many reasons. It's also confusing. The marketing hype makes it hard to understand either topic. SDN has become so vague that if you ask 10 experts what it means, you are likely to get 12 different answers. Network dis-aggregation seems straightforward enough until it gets confused with SDN. We need to take a step back. In a recent Packet Pushers blog post; I start with a simple explanation of each of these trends and then map how they interact. <a href="https://circleid.com/posts20170317_network_dis_aggregation_and_sdn_different_but_related">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Building the Future of Enterprise - Notes from AWS re:Invent 2016 (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20161221_building_the_future_of_enterprise_notes_from_aws_reinvent_2016</guid>
		<link>https://circleid.com/posts20161221_building_the_future_of_enterprise_notes_from_aws_reinvent_2016</link>
		<description><![CDATA[I attended AWS re:Invent 2016 about three or four weeks ago. Being new to both AWS and to re:Invent I was an outsider again, observing with virgin eyes. This means I learned a lot. Hopefully it means I saw things a bit differently than those more fully entrenched in this new community. So while others have long since covered the product announcements and other major news from the event, I'll take this opportunity to touch on some of the things that struck me as descriptive and/or indicative of the greater trends at play here. <a href="https://circleid.com/posts20161221_building_the_future_of_enterprise_notes_from_aws_reinvent_2016">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> The Shadow of the Web (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20151228_the_shadow_of_the_web</guid>
		<link>https://circleid.com/posts20151228_the_shadow_of_the_web</link>
		<description><![CDATA[I believe in the Internet As an ideal. As a web of human minds. As a wonder of the world, not built through totalitarian control but rather through fierce coopetition. As a technological pillar held up by a newer, better, governance structure. As the facilitator of knowledge sharing and communication on a level so advanced that it would appear supernatural to folks living just a century ago, or less. I worry for the Internet While it has been a major disruptive force, it is also susceptible to the existing paradigm. <a href="https://circleid.com/posts20151228_the_shadow_of_the_web">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #10: Deploying IPv6 is Too Risky (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150325_ipv6_security_myth_10_deploying_ipv6_is_too_risky</guid>
		<link>https://circleid.com/posts20150325_ipv6_security_myth_10_deploying_ipv6_is_too_risky</link>
		<description><![CDATA[After a quick break to catch our breath (and read all those IPv6 Security Resources), it's now time to look at our tenth and final IPv6 Security Myth. In many ways this myth is the most important myth to bust. Let's take a look at why... Myth: Deploying IPv6 Makes My Network Less Secure... I can hear you asking "But what about all those security challenges we identified in the other myths?" <a href="https://circleid.com/posts20150325_ipv6_security_myth_10_deploying_ipv6_is_too_risky">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #9: There Aren't Any IPv6 Security Resources (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150312_ipv6_security_myth_9_there_arent_any_ipv6_security_resources</guid>
		<link>https://circleid.com/posts20150312_ipv6_security_myth_9_there_arent_any_ipv6_security_resources</link>
		<description><![CDATA[We are approaching the end of this 10 part series on the most common IPv6 security myths. Now it's time to turn our eyes away from security risks to focus a bit more on security resources. Today's myth is actually one of the most harmful to those who hold it. If you believe that there is no good information out there, it's nearly impossible to find that information. So let's get down to it and dispel our 9th myth. <a href="https://circleid.com/posts20150312_ipv6_security_myth_9_there_arent_any_ipv6_security_resources">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #8: It Supports IPv6 (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150305_ipv6_security_myth_8_it_supports_ipv6</guid>
		<link>https://circleid.com/posts20150305_ipv6_security_myth_8_it_supports_ipv6</link>
		<description><![CDATA[Most of our IPv6 Security Myths are general notions, often passed on unwittingly between colleagues, friends, conference attendees, and others. Today's myth is one that most often comes specifically from your vendors or suppliers. Whether it's a hardware manufacturer, software developer, or Internet Service Provider (ISP), this myth is all about trust, but verify. <a href="https://circleid.com/posts20150305_ipv6_security_myth_8_it_supports_ipv6">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #7: 96 More Bits, No Magic (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150301_ipv6_security_myth_7_96_more_bits_no_magic</guid>
		<link>https://circleid.com/posts20150301_ipv6_security_myth_7_96_more_bits_no_magic</link>
		<description><![CDATA[This week's myth is interesting because if we weren't talking security it wouldn't be a myth. Say what? The phrase "96 more bits, no magic" is basically a way of saying that IPv6 is just like IPv4, with longer addresses. From a pure routing and switching perspective, this is quite accurate. OSPF, IS-IS, and BGP all work pretty much the same, regardless of address family. Nothing about finding best paths and forwarding packets changes all that much from IPv4 to IPv6. <a href="https://circleid.com/posts20150301_ipv6_security_myth_7_96_more_bits_no_magic">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #6: IPv6 is Too New to be Attacked (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150219_ipv6_security_myth_6_ipv6_is_too_new_to_be_attacked</guid>
		<link>https://circleid.com/posts20150219_ipv6_security_myth_6_ipv6_is_too_new_to_be_attacked</link>
		<description><![CDATA[Here we are, half-way through this list of the top 10 IPv6 security myths! Welcome to myth #6. Since IPv6 is just now being deployed at any real scale on true production networks, some may think that the attackers have yet to catch up. As we learned in Myth #2, IPv6 was actually designed starting 15-20 years ago. While it didn't see widespread commercial adoption until the last several years, there has been plenty of time to develop at least a couple suites of test/attack tools. <a href="https://circleid.com/posts20150219_ipv6_security_myth_6_ipv6_is_too_new_to_be_attacked">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #5: Privacy Addresses Fix Everything! (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150216_ipv6_security_myth_5_privacy_addresses_fix_everything</guid>
		<link>https://circleid.com/posts20150216_ipv6_security_myth_5_privacy_addresses_fix_everything</link>
		<description><![CDATA[Internet Protocol addresses fill two unique roles. They are both identifiers and locators. They both tell us which interface is which (identity) and tell us how to find that interface (location), through routing. In the last myth, about network scanning, we focused mainly on threats to IPv6 addresses as locators. That is, how to locate IPv6 nodes for exploitation. Today's myth also deals with IPv6 addresses as identifiers. <a href="https://circleid.com/posts20150216_ipv6_security_myth_5_privacy_addresses_fix_everything">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #4: IPv6 Networks are Too Big to Scan (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150205_ipv6_security_myth_4_ipv6_networks_are_too_big_to_scan</guid>
		<link>https://circleid.com/posts20150205_ipv6_security_myth_4_ipv6_networks_are_too_big_to_scan</link>
		<description><![CDATA[Here we are, all the way up to Myth #4! That makes this the 4th installment of our 10 part series on the top IPv6 Security Myths. This myth is one of my favorite myths to bust when speaking with folks around the world. The reason for that is how many otherwise well-informed and highly experienced engineers, and others, hold this myth as truth. It's understandable, really. <a href="https://circleid.com/posts20150205_ipv6_security_myth_4_ipv6_networks_are_too_big_to_scan">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #3: No IPv6 NAT Means Less Security (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150129_ipv6_security_myth_3_no_ipv6_nat_means_less_security</guid>
		<link>https://circleid.com/posts20150129_ipv6_security_myth_3_no_ipv6_nat_means_less_security</link>
		<description><![CDATA[We're back again with part 3 in this 10 part series that seeks to bust 10 of the most common IPv6 security myths. Today's myth is a doozy. This is the only myth on our list that I have seen folks raise their voices over. For whatever reason, Network Address Translation (NAT) seems to be a polarizing force in the networking world. It also plays a role in differentiating IPv4 from IPv6. <a href="https://circleid.com/posts20150129_ipv6_security_myth_3_no_ipv6_nat_means_less_security">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> The IETF's *Other* Diversity Challenge: An Update (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150129_the_ietfs_other_diversity_challenge_an_update</guid>
		<link>https://circleid.com/posts20150129_the_ietfs_other_diversity_challenge_an_update</link>
		<description><![CDATA[Last June I wrote an article titled "The IETF's <em>Other</em> Diversity Challenge" where I discussed the positive steps the Internet Engineering Task Force (IETF) is taking to increase the diversity of its participants and raised a potentially overlooked demographic: Network Operators. That essay was a problem statement of sorts, and I was long ago taught that you should only raise problems that you have a solution for, or are at least willing to help solve. <a href="https://circleid.com/posts20150129_the_ietfs_other_diversity_challenge_an_update">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #2: IPv6 Has Security Designed In (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150122_ipv6_security_myth_2_ipv6_has_security_designed_in</guid>
		<link>https://circleid.com/posts20150122_ipv6_security_myth_2_ipv6_has_security_designed_in</link>
		<description><![CDATA[Today we continue with part 2 of the 10 part series on IPv6 Security Myths by debunking one of the myths I overhear people propagating out loud far too much: That you don't need to worry about security because IPv6 has it built into the protocol. In this post, we'll explore several of the reasons that this is in fact a myth and look at some harsh realities surrounding IPv6 security. <a href="https://circleid.com/posts20150122_ipv6_security_myth_2_ipv6_has_security_designed_in">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> IPv6 Security Myth #1: I'm Not Running IPv6 so I Don't Have to Worry (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150118_im_not_running_ipv6_so_i_dont_have_to_worry_ipv6_security_myth_1</guid>
		<link>https://circleid.com/posts20150118_im_not_running_ipv6_so_i_dont_have_to_worry_ipv6_security_myth_1</link>
		<description><![CDATA[Now that IPv6 is being actively deployed around the world, security is more and more a growing concern. Unfortunately, there are still a large number of myths that plague the IPv6 security world. These are things that people state as fact but simply aren't true. While traveling the world, talking to the people who've already deployed IPv6, I've identified what I believe are the ten most common IPv6 security myths. <a href="https://circleid.com/posts20150118_im_not_running_ipv6_so_i_dont_have_to_worry_ipv6_security_myth_1">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	
	<item>
		<title> The IETF's *Other* Diversity Challenge (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20140612_the_ietfs_other_diversity_challenge</guid>
		<link>https://circleid.com/posts20140612_the_ietfs_other_diversity_challenge</link>
		<description><![CDATA[The Internet Engineering Task Force (IETF) is the standards body for the Internet. It is the organization that publishes and maintains the standards describing the Internet Protocol (IP -- versions 4 and 6), and all directly related and supporting protocols, such as TCP, UDP, DNS (and DNSSEC), BGP, DHCP, NDP, the list goes on, and on... But how do they do that? How does the IETF produce documents, and ensure that they are high quality, relevant, and influential? <a href="https://circleid.com/posts20140612_the_ietfs_other_diversity_challenge">More...</a>]]></description>
		<dc:date>2026-05-02T08:50:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>