<?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 on: MPLS LDP-IGP synchronization</title>
	<atom:link href="http://www.hauwaerts.be/2009/02/22/mpls-ldp-igp-synchronization/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hauwaerts.be/2009/02/22/mpls-ldp-igp-synchronization/</link>
	<description>The whole truth and nothing but the truth!</description>
	<lastBuildDate>Mon, 17 May 2010 21:03:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Geert</title>
		<link>http://www.hauwaerts.be/2009/02/22/mpls-ldp-igp-synchronization/comment-page-1/#comment-306</link>
		<dc:creator>Geert</dc:creator>
		<pubDate>Fri, 06 Mar 2009 11:50:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=766#comment-306</guid>
		<description>Traffic will be routed over an alternate IGP path.

   In detail: when LDP is not &quot;fully operational&quot; (see below) on a given
   link, the IGP will advertise the link with maximum cost to avoid any
   transit traffic over it.  In the case of OSPF, this cost is
   LSInfinity (16-bit value 0xFFFF), as proposed in [RFC3137].  In the
   case of ISIS, the maximum metric value is 2^24-2 (0xFFFFFE).  Indeed,
   if a link is configured with 2^24-1 (the maximum link metric per
   [RFC5305]), then this link is not advertised in the topology.  It is
   important to keep the link in the topology to allow IP traffic to use
   the link as a last resort in case of massive failure.</description>
		<content:encoded><![CDATA[<p>Traffic will be routed over an alternate IGP path.</p>
<p>   In detail: when LDP is not &#8220;fully operational&#8221; (see below) on a given<br />
   link, the IGP will advertise the link with maximum cost to avoid any<br />
   transit traffic over it.  In the case of OSPF, this cost is<br />
   LSInfinity (16-bit value 0xFFFF), as proposed in [RFC3137].  In the<br />
   case of ISIS, the maximum metric value is 2^24-2 (0xFFFFFE).  Indeed,<br />
   if a link is configured with 2^24-1 (the maximum link metric per<br />
   [RFC5305]), then this link is not advertised in the topology.  It is<br />
   important to keep the link in the topology to allow IP traffic to use<br />
   the link as a last resort in case of massive failure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shivlu jain</title>
		<link>http://www.hauwaerts.be/2009/02/22/mpls-ldp-igp-synchronization/comment-page-1/#comment-302</link>
		<dc:creator>shivlu jain</dc:creator>
		<pubDate>Fri, 06 Mar 2009 08:40:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=766#comment-302</guid>
		<description>I have one concern:-
During the time of LDP &amp; IGP Sync what will be the flow of my IP traffic.</description>
		<content:encoded><![CDATA[<p>I have one concern:-<br />
During the time of LDP &amp; IGP Sync what will be the flow of my IP traffic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Follow up on MPLS LDP-IGP synchronization &#124; Geert's blog - Casu Consulto</title>
		<link>http://www.hauwaerts.be/2009/02/22/mpls-ldp-igp-synchronization/comment-page-1/#comment-281</link>
		<dc:creator>Follow up on MPLS LDP-IGP synchronization &#124; Geert's blog - Casu Consulto</dc:creator>
		<pubDate>Wed, 04 Mar 2009 17:36:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=766#comment-281</guid>
		<description>[...] recent blogpost about the subject explains the issue and the solution to prevent an IP link from being used while LDP is not fully [...]</description>
		<content:encoded><![CDATA[<p>[...] recent blogpost about the subject explains the issue and the solution to prevent an IP link from being used while LDP is not fully [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
