<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for Pattincon Blog</title>
	<atom:link href="http://blog.pattincon.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pattincon.com</link>
	<description>Network and Telecoms Technologies</description>
	<lastBuildDate>Tue, 03 Jan 2012 05:42:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>Comment on Techtip &#8211; Determining Optic connectors using Cisco IOS by Steve B</title>
		<link>http://blog.pattincon.com/techtip-determining-optic-connectors-using-cisco-ios/#comment-626</link>
		<dc:creator>Steve B</dc:creator>
		<pubDate>Tue, 03 Jan 2012 05:42:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/?p=1178#comment-626</guid>
		<description>Noted this down for reference when this popped into my RSS Feed and stumbled across said note just now and realised I never said thank you. So thanks for the tip, very useful to know.

On a side note I noticed the &quot;sh idprom int&quot; output tells you very straightforwardly which ASIC a port is on which can be of use too.</description>
		<content:encoded><![CDATA[<p>Noted this down for reference when this popped into my RSS Feed and stumbled across said note just now and realised I never said thank you. So thanks for the tip, very useful to know.</p>
<p>On a side note I noticed the &#8220;sh idprom int&#8221; output tells you very straightforwardly which ASIC a port is on which can be of use too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on LISP &#8211; Separate MS / MR by Amit Bhagat</title>
		<link>http://blog.pattincon.com/lisp-separate-ms-mr/#comment-625</link>
		<dc:creator>Amit Bhagat</dc:creator>
		<pubDate>Wed, 05 Oct 2011 02:14:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/?p=986#comment-625</guid>
		<description>Hi Terry,

This is an excellent series of posts on LISP. Also, thank you for the introduction to CloudShark - it looks fantastic.

I have a couple of questions for you-

1. In multiple Service Providers environment, how is the ALT topology built? I understand BGP is used over GRE. From your example, GRE tunnel is built between MS and MR.

2. In multiple Service Providers environment, how are MS and MR decided or recognized?

Appreciate your effort behind these posts.

Thanks,
AB.</description>
		<content:encoded><![CDATA[<p>Hi Terry,</p>
<p>This is an excellent series of posts on LISP. Also, thank you for the introduction to CloudShark &#8211; it looks fantastic.</p>
<p>I have a couple of questions for you-</p>
<p>1. In multiple Service Providers environment, how is the ALT topology built? I understand BGP is used over GRE. From your example, GRE tunnel is built between MS and MR.</p>
<p>2. In multiple Service Providers environment, how are MS and MR decided or recognized?</p>
<p>Appreciate your effort behind these posts.</p>
<p>Thanks,<br />
AB.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on LISP Data Plane by Anouar Belkacem</title>
		<link>http://blog.pattincon.com/lisp-data-plane/#comment-620</link>
		<dc:creator>Anouar Belkacem</dc:creator>
		<pubDate>Sun, 26 Jun 2011 19:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/?p=431#comment-620</guid>
		<description>Hi,

Is there any MPLS in the public Internet? I will be surprised if yes... 
You&#039;re true about the overhead of LISP, pros will say this overhead will be limited to xTR (edge routers only), the core routers won&#039;t have to carry about LISP or GRE. Ok, but this is a problem because, as I know, ISP&#039;s edge routers are what we call the of core the Internet (there are few exceptions). So if these edges are slowed down all the Internet will suffer. 

If I understand, the map cache will allow to speed up RLOC lookup, but the cache is a problem by itself (many example for this : processor cache, browsers cache...).</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Is there any MPLS in the public Internet? I will be surprised if yes&#8230;<br />
You&#8217;re true about the overhead of LISP, pros will say this overhead will be limited to xTR (edge routers only), the core routers won&#8217;t have to carry about LISP or GRE. Ok, but this is a problem because, as I know, ISP&#8217;s edge routers are what we call the of core the Internet (there are few exceptions). So if these edges are slowed down all the Internet will suffer. </p>
<p>If I understand, the map cache will allow to speed up RLOC lookup, but the cache is a problem by itself (many example for this : processor cache, browsers cache&#8230;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Identity / Location by Anouar</title>
		<link>http://blog.pattincon.com/identity-location/#comment-619</link>
		<dc:creator>Anouar</dc:creator>
		<pubDate>Sun, 26 Jun 2011 18:12:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/?p=179#comment-619</guid>
		<description>Hi,

I like your nice introduction to LISP, it&#039;s LISP for dummies :-)</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I like your nice introduction to LISP, it&#8217;s LISP for dummies <img src='http://blog.pattincon.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Underlying causes for an expanding Internet Routing Table by Terry</title>
		<link>http://blog.pattincon.com/underlying-causes-for-an-expanding-internet-routing-table/#comment-612</link>
		<dc:creator>Terry</dc:creator>
		<pubDate>Tue, 07 Jun 2011 15:37:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/underlying-causes-for-an-expanding-internet-routing-table-part-1/#comment-612</guid>
		<description>Great catch Gabriel, thanks. I&#039;ve corrected accordingly.</description>
		<content:encoded><![CDATA[<p>Great catch Gabriel, thanks. I&#8217;ve corrected accordingly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Underlying causes for an expanding Internet Routing Table by Gabriel</title>
		<link>http://blog.pattincon.com/underlying-causes-for-an-expanding-internet-routing-table/#comment-611</link>
		<dc:creator>Gabriel</dc:creator>
		<pubDate>Wed, 25 May 2011 22:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/underlying-causes-for-an-expanding-internet-routing-table-part-1/#comment-611</guid>
		<description>&lt;blockquote&gt;If an ISP were allocated 10/8 and 11/8, it would neither aggregate to 10/9&lt;/blockquote&gt;

You probably meant 10/7?</description>
		<content:encoded><![CDATA[<blockquote><p>If an ISP were allocated 10/8 and 11/8, it would neither aggregate to 10/9</p></blockquote>
<p>You probably meant 10/7?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on LISP &#8211; New CLI by Terry</title>
		<link>http://blog.pattincon.com/lisp-new-cli/#comment-595</link>
		<dc:creator>Terry</dc:creator>
		<pubDate>Thu, 05 May 2011 08:37:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/?p=957#comment-595</guid>
		<description>IPv6 support is integral to LISP. In fact, 646 or even 464 tunnelling topologies are natively supported. Think of LISP as GRE (at the data plane level) with automatic end-point discovery and tunnel setup, built from the ground up to scale. Therefore it delivers a number of services more traditionally the domain of GRE. I&#039;ll cover IPv6 tunnelling over an IPv4 infrastructure in a future post.</description>
		<content:encoded><![CDATA[<p>IPv6 support is integral to LISP. In fact, 646 or even 464 tunnelling topologies are natively supported. Think of LISP as GRE (at the data plane level) with automatic end-point discovery and tunnel setup, built from the ground up to scale. Therefore it delivers a number of services more traditionally the domain of GRE. I&#8217;ll cover IPv6 tunnelling over an IPv4 infrastructure in a future post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on LISP &#8211; New CLI by D.M. Geurts</title>
		<link>http://blog.pattincon.com/lisp-new-cli/#comment-594</link>
		<dc:creator>D.M. Geurts</dc:creator>
		<pubDate>Thu, 05 May 2011 08:22:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/?p=957#comment-594</guid>
		<description>What about IPv6 support?</description>
		<content:encoded><![CDATA[<p>What about IPv6 support?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Advanced network access with SecureCRT by Terry</title>
		<link>http://blog.pattincon.com/advanced-network-access-with-securecrt/#comment-536</link>
		<dc:creator>Terry</dc:creator>
		<pubDate>Thu, 31 Mar 2011 09:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/?p=762#comment-536</guid>
		<description>Yep - I like efficiency and Security can be an obstacle. Tomorrow takes the theme of efficiency further, as I talk about Dynamic SSH tunnelling. This saves on the manual configuration required in static tunnels.</description>
		<content:encoded><![CDATA[<p>Yep &#8211; I like efficiency and Security can be an obstacle. Tomorrow takes the theme of efficiency further, as I talk about Dynamic SSH tunnelling. This saves on the manual configuration required in static tunnels.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Advanced network access with SecureCRT by Ryan</title>
		<link>http://blog.pattincon.com/advanced-network-access-with-securecrt/#comment-535</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Thu, 31 Mar 2011 08:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pattincon.com/?p=762#comment-535</guid>
		<description>Hi Terry,
Nice write up.
It goes to show that there technologies and standard functions of services, in this case SSH that do deliver good security practices that we generally don&#039;t follow.

Cheers</description>
		<content:encoded><![CDATA[<p>Hi Terry,<br />
Nice write up.<br />
It goes to show that there technologies and standard functions of services, in this case SSH that do deliver good security practices that we generally don&#8217;t follow.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>
