<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Cisco Blog &#187; access router</title>
	<atom:link href="http://blogs.cisco.com/tag/access-router/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.cisco.com</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 18:51:19 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Why Cisco, Not Juniper? OpEx, CapEx and the Frankenkluge in the Branch Office Closet</title>
		<link>http://blogs.cisco.com/borderless/why-cisco-not-juniper-opex-capex-and-the-frankenkluge-in-the-branch-office-closet/</link>
		<comments>http://blogs.cisco.com/borderless/why-cisco-not-juniper-opex-capex-and-the-frankenkluge-in-the-branch-office-closet/#comments</comments>
		<pubDate>Tue, 17 Jan 2012 19:30:14 +0000</pubDate>
		<dc:creator>Prashanth Shenoy</dc:creator>
				<category><![CDATA[Borderless Networks]]></category>
		<category><![CDATA[access router]]></category>
		<category><![CDATA[branch office]]></category>
		<category><![CDATA[Cisco Integrated Services Router]]></category>
		<category><![CDATA[Cisco ISR]]></category>
		<category><![CDATA[juniper]]></category>
		<category><![CDATA[routers]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=57298</guid>
		<description><![CDATA[One of the great things about being at Cisco HQ in Silicon Valley is the wonderful diversity we have here. [...]]]></description>
		<wfw:commentRss>http://blogs.cisco.com/borderless/why-cisco-not-juniper-opex-capex-and-the-frankenkluge-in-the-branch-office-closet/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>
