<?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; router security</title>
	<atom:link href="http://blogs.cisco.com/tag/router-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.cisco.com</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 18:55:13 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Securing BGP sounds great but is there a tradeoff in terms of router performance?</title>
		<link>http://blogs.cisco.com/security/securing-bgp-sounds-great-but-is-there-a-tradeoff-in-terms-of-router-performance/</link>
		<comments>http://blogs.cisco.com/security/securing-bgp-sounds-great-but-is-there-a-tradeoff-in-terms-of-router-performance/#comments</comments>
		<pubDate>Wed, 10 Oct 2012 21:45:28 +0000</pubDate>
		<dc:creator>John Stuppi</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[BGP]]></category>
		<category><![CDATA[Border Gateway Protocol]]></category>
		<category><![CDATA[router security]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=86365</guid>
		<description><![CDATA[This article highlights recent updates made to the "Protecting Border Gateway Protocol for the Enterprise" White Paper (http://www.cisco.com/web/about/security/intelligence/protecting_bgp.html) to reflect the impact on router memory when implementing features that enhance the security of the BGP configuration.]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/securing-bgp-sounds-great-but-is-there-a-tradeoff-in-terms-of-router-performance/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
