<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>MPLS TE Archives - Network Solution</title>
	<atom:link href="https://blog.network-solution.net/tag/mpls-te/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.network-solution.net/tag/mpls-te/</link>
	<description></description>
	<lastBuildDate>Wed, 12 Aug 2015 21:42:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.7</generator>

<image>
	<url>https://blog.network-solution.net/wp-content/uploads/2021/06/favicon.ico</url>
	<title>MPLS TE Archives - Network Solution</title>
	<link>https://blog.network-solution.net/tag/mpls-te/</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">88039135</site>	<item>
		<title>IS-IS TE</title>
		<link>https://blog.network-solution.net/is-is-te/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=is-is-te</link>
					<comments>https://blog.network-solution.net/is-is-te/#respond</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Wed, 12 Aug 2015 21:42:29 +0000</pubDate>
				<category><![CDATA[ISIS]]></category>
		<category><![CDATA[ISIS Traffic engineering]]></category>
		<category><![CDATA[MPLS]]></category>
		<category><![CDATA[MPLS TE]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=229</guid>

					<description><![CDATA[<p>IS-IS Traffic Engineering (TE) is an extension of IS-IS to support MPLS TE. As specified in&#160;RFC 5305 and RFC 4205, IS-IS TE defines new TLVsand sub-TLVs&#160;in IS-IS LSPs to carry TE information, floods LSPs to implement the flooding and synchronization of TE information, and transmits TE information to the CSPF module. IS-IS TE supports MPLS &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/is-is-te/">IS-IS TE</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/is-is-te/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">229</post-id>	</item>
		<item>
		<title>Configuring an Integrated IP RAN (PWE3 + L3VPN) with Ethernet NodeBs</title>
		<link>https://blog.network-solution.net/configuring-an-integrated-ip-ran-pwe3-l3vpn-with-ethernet-nodebs/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=configuring-an-integrated-ip-ran-pwe3-l3vpn-with-ethernet-nodebs</link>
					<comments>https://blog.network-solution.net/configuring-an-integrated-ip-ran-pwe3-l3vpn-with-ethernet-nodebs/#respond</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Tue, 14 Apr 2015 21:13:52 +0000</pubDate>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[IPRAN]]></category>
		<category><![CDATA[IPRAN configuration]]></category>
		<category><![CDATA[L3VPN]]></category>
		<category><![CDATA[MPLS TE]]></category>
		<category><![CDATA[NodeB]]></category>
		<category><![CDATA[PWE3]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=119</guid>

					<description><![CDATA[<p>Networking Requirements The integrated L2VPN access to L3VPN solution allows Ethernet NodeBs to communicate with Radio Network Controllers (RNCs). It terminates the L2VPN and connects the L3VPN on a SR by creating a Virtual Ethernet group (VE-group). PW redundancy is configured to protect PWs on the L2VPN and VPN FRR is configured to protect links &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/configuring-an-integrated-ip-ran-pwe3-l3vpn-with-ethernet-nodebs/">Configuring an Integrated IP RAN (PWE3 + L3VPN) with Ethernet NodeBs</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/configuring-an-integrated-ip-ran-pwe3-l3vpn-with-ethernet-nodebs/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">119</post-id>	</item>
		<item>
		<title>MPLS Structure</title>
		<link>https://blog.network-solution.net/mpls-structure/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=mpls-structure</link>
					<comments>https://blog.network-solution.net/mpls-structure/#respond</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Thu, 09 Apr 2015 21:31:27 +0000</pubDate>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[MPLS]]></category>
		<category><![CDATA[MPLS TE]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=110</guid>

					<description><![CDATA[<p>l MPLS network forwards packet according to the label. But how does label be generated? What mechanism does MPLS adopt to implement data forwarding? l MPLS includes two plane: control plane and data plane. l Control plane’s charge is to generate and maintain routing information and label information. Data plane’s charge is conventional IP packet &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/mpls-structure/">MPLS Structure</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/mpls-structure/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">110</post-id>	</item>
		<item>
		<title>Introduction to MPLS TE</title>
		<link>https://blog.network-solution.net/introduction-to-mpls-te/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=introduction-to-mpls-te</link>
					<comments>https://blog.network-solution.net/introduction-to-mpls-te/#respond</comments>
		
		<dc:creator><![CDATA[mammoura]]></dc:creator>
		<pubDate>Thu, 02 Apr 2015 13:52:53 +0000</pubDate>
				<category><![CDATA[IPRAN]]></category>
		<category><![CDATA[MPLS TE]]></category>
		<category><![CDATA[Introduction to MPLS TE]]></category>
		<category><![CDATA[MPLS]]></category>
		<guid isPermaLink="false">http://blog.network-solution.net/?p=94</guid>

					<description><![CDATA[<p>Purpose In a traditional IP network, a node select the shortest path as the route regardless of other factors such as bandwidth. The shortest path, however, may be congested with traffic, whereas other available paths are idle. Figure 1 Problems in Traditional Routing As shown in Figure 1, assume that links have the same metric. &#8230; </p>
<p>The post <a href="https://blog.network-solution.net/introduction-to-mpls-te/">Introduction to MPLS TE</a> appeared first on <a href="https://blog.network-solution.net">Network Solution</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.network-solution.net/introduction-to-mpls-te/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">94</post-id>	</item>
	</channel>
</rss>
