<?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 LSP &#8211; Label Switched Path &#8211; L2VPN Pseudowire</title>
	<atom:link href="http://www.hauwaerts.be/2009/01/10/mpls-lsp-label-switched-path-l2vpn-pseudowire/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hauwaerts.be/2009/01/10/mpls-lsp-label-switched-path-l2vpn-pseudowire/</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: MPLS L2VPN &#8211; Pseudowire Redundancy &#124; Geert's blog - Casu Consulto</title>
		<link>http://www.hauwaerts.be/2009/01/10/mpls-lsp-label-switched-path-l2vpn-pseudowire/comment-page-1/#comment-4024</link>
		<dc:creator>MPLS L2VPN &#8211; Pseudowire Redundancy &#124; Geert's blog - Casu Consulto</dc:creator>
		<pubDate>Sat, 25 Jul 2009 19:57:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=427#comment-4024</guid>
		<description>[...] basic configuration for MPLS, OSPF and interfaces are explained in my previous post. You need to choose a unique VC-ID per circuit; in this example I will use VC-ID 100 for the [...]</description>
		<content:encoded><![CDATA[<p>[...] basic configuration for MPLS, OSPF and interfaces are explained in my previous post. You need to choose a unique VC-ID per circuit; in this example I will use VC-ID 100 for the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MPLS Targeted LDP - tLDP - Label Forwarding &#124; Geert's blog - Casu Consulto</title>
		<link>http://www.hauwaerts.be/2009/01/10/mpls-lsp-label-switched-path-l2vpn-pseudowire/comment-page-1/#comment-810</link>
		<dc:creator>MPLS Targeted LDP - tLDP - Label Forwarding &#124; Geert's blog - Casu Consulto</dc:creator>
		<pubDate>Wed, 08 Apr 2009 19:29:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=427#comment-810</guid>
		<description>[...] past few months I&#8217;ve received a lot of feedback on my L2VPN Pseudowire blog post. Most questions where related to tLDP (Targeted LDP), PHP (Penultimate Hop Popping), [...]</description>
		<content:encoded><![CDATA[<p>[...] past few months I&#8217;ve received a lot of feedback on my L2VPN Pseudowire blog post. Most questions where related to tLDP (Targeted LDP), PHP (Penultimate Hop Popping), [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geert</title>
		<link>http://www.hauwaerts.be/2009/01/10/mpls-lsp-label-switched-path-l2vpn-pseudowire/comment-page-1/#comment-599</link>
		<dc:creator>Geert</dc:creator>
		<pubDate>Wed, 01 Apr 2009 18:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=427#comment-599</guid>
		<description>You are correct. The diagram is a bit confusing and your diagram is correct.

When the router receives the customer frames (InnerL2-&gt;IP) it will establish a directed LDP session to the destination router. Exchange labels for that specific pseudowire, this is the bottom label of the stack. Then it will find the FEC to the destination router with a label exchanged from his next-hop neighbour which is the top label of the stack. Then it adds his own l2 header to push the traffic to the next hop.

So to conclude:
  - The customer l2 frame isn&#039;t touched but placed behind the MPLS label. 
  - Pseudowires have (at least) two MPLS labels.
  - The l2 header in the designs is the one between two routers to exchane traffic.</description>
		<content:encoded><![CDATA[<p>You are correct. The diagram is a bit confusing and your diagram is correct.</p>
<p>When the router receives the customer frames (InnerL2->IP) it will establish a directed LDP session to the destination router. Exchange labels for that specific pseudowire, this is the bottom label of the stack. Then it will find the FEC to the destination router with a label exchanged from his next-hop neighbour which is the top label of the stack. Then it adds his own l2 header to push the traffic to the next hop.</p>
<p>So to conclude:<br />
  &#8211; The customer l2 frame isn&#8217;t touched but placed behind the MPLS label.<br />
  &#8211; Pseudowires have (at least) two MPLS labels.<br />
  &#8211; The l2 header in the designs is the one between two routers to exchane traffic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Balaji</title>
		<link>http://www.hauwaerts.be/2009/01/10/mpls-lsp-label-switched-path-l2vpn-pseudowire/comment-page-1/#comment-570</link>
		<dc:creator>Balaji</dc:creator>
		<pubDate>Mon, 30 Mar 2009 16:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=427#comment-570</guid>
		<description>Hi ,
Is that diagram shows the encapsulation of packets for L2VPN Architecture?
Because, i wonder why MPLS header came in between the IP and L2Hdr. If it is L2VPN,
then the entire L2 Frame should be included inside a MPLS Label when it enters the Provider Network, isn&#039;t it?
Like, Outer-L2Hdr-&gt;MPLS-&gt;InnerL2Hdr-&gt;IP ????
Please Clarify.
Thanks,</description>
		<content:encoded><![CDATA[<p>Hi ,<br />
Is that diagram shows the encapsulation of packets for L2VPN Architecture?<br />
Because, i wonder why MPLS header came in between the IP and L2Hdr. If it is L2VPN,<br />
then the entire L2 Frame should be included inside a MPLS Label when it enters the Provider Network, isn&#8217;t it?<br />
Like, Outer-L2Hdr-&gt;MPLS-&gt;InnerL2Hdr-&gt;IP ????<br />
Please Clarify.<br />
Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MPLS LDP-IGP synchronization &#124; Geert's blog - Casu Consulto</title>
		<link>http://www.hauwaerts.be/2009/01/10/mpls-lsp-label-switched-path-l2vpn-pseudowire/comment-page-1/#comment-225</link>
		<dc:creator>MPLS LDP-IGP synchronization &#124; Geert's blog - Casu Consulto</dc:creator>
		<pubDate>Sun, 22 Feb 2009 19:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=427#comment-225</guid>
		<description>[...] explained in my previous MPLS LSP post you use the IGP such as OSPF or IS-IS its CEF FIB (Cisco Express Forwarding - Forwarding [...]</description>
		<content:encoded><![CDATA[<p>[...] explained in my previous MPLS LSP post you use the IGP such as OSPF or IS-IS its CEF FIB (Cisco Express Forwarding &#8211; Forwarding [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.hauwaerts.be/2009/01/10/mpls-lsp-label-switched-path-l2vpn-pseudowire/comment-page-1/#comment-22</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sun, 11 Jan 2009 16:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=427#comment-22</guid>
		<description>Damn, accidently pressed submit too soon. -___-</description>
		<content:encoded><![CDATA[<p>Damn, accidently pressed submit too soon. -___-</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.hauwaerts.be/2009/01/10/mpls-lsp-label-switched-path-l2vpn-pseudowire/comment-page-1/#comment-21</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sun, 11 Jan 2009 16:19:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauwaerts.be/?p=427#comment-21</guid>
		<description>The configuration methods seem so be very straightforward. I would have expected a whole lot more commands.
The text and schematics makes it a lot easier to understand. It makes it easy to understand.

Keep up the good work! Don&#039;t forget to spam the 30-head NOC from one of your previous posts with this piece of art.
Can&#039;t wait to see more of this.</description>
		<content:encoded><![CDATA[<p>The configuration methods seem so be very straightforward. I would have expected a whole lot more commands.<br />
The text and schematics makes it a lot easier to understand. It makes it easy to understand.</p>
<p>Keep up the good work! Don&#8217;t forget to spam the 30-head NOC from one of your previous posts with this piece of art.<br />
Can&#8217;t wait to see more of this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
