<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="https://drupalinl.info.ucl.ac.be" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>INL: IP Networking Lab - Traffic Engineering</title>
 <link>https://drupalinl.info.ucl.ac.be/taxonomy/term/11/0</link>
 <description></description>
 <language>en</language>
<item>
 <title>MPLS autobandwidth</title>
 <link>https://drupalinl.info.ucl.ac.be/blogs/11-03-07-mpls-autobandwidth</link>
 <description>&lt;p&gt;Since several years, Cisco routers have included a feature called &lt;code&gt;mpls autobandwidth&lt;/code&gt; that allows the router to compute automatically the bandwidth required for an LSP and adjust the reserved bandwidth. This feature seems interesting, but personally I have always feared that it could cause oscillations in a network if the change in reserved bandwidth leads to a change in paths for the concerned LSPs.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://drupalinl.info.ucl.ac.be/blogs/11-03-07-mpls-autobandwidth&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="https://drupalinl.info.ucl.ac.be/category/visibility/public">Public</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/mpls">MPLS</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/traffic-engineering">Traffic Engineering</category>
 <pubDate>Mon, 07 Mar 2011 12:27:22 +0000</pubDate>
 <dc:creator>obo</dc:creator>
 <guid isPermaLink="false">782 at https://drupalinl.info.ucl.ac.be</guid>
</item>
<item>
 <title>DeSiNe: a flow-level QoS Simulator of Networks</title>
 <link>https://drupalinl.info.ucl.ac.be/publications/desine-flow-level-qos-simulator-networks</link>
 <description>&lt;p&gt;In this paper we present DeSiNe, a modular flow-level network&lt;br /&gt;
simulator. DeSiNe is aimed at performance analysis and bench-&lt;br /&gt;
marking of Quality of Service routing algorithms and traffic engi-&lt;br /&gt;
neering extensions. Several well-known QoS routing algorithms&lt;br /&gt;
and traffic engineering extensions have been implemented in De-&lt;br /&gt;
SiNe. The flow-level nature provides scalability, such that large&lt;br /&gt;
networks and heavy-traffic conditions are possible. In this paper,&lt;br /&gt;
the functional and structural design of DeSiNe are presented and&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://drupalinl.info.ucl.ac.be/publications/desine-flow-level-qos-simulator-networks&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="https://drupalinl.info.ucl.ac.be/category/visibility/public">Public</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/qos">QoS</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/simulator">simulator</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/traffic-engineering">Traffic Engineering</category>
 <pubDate>Thu, 11 Dec 2008 10:16:52 +0000</pubDate>
 <dc:creator>bqu</dc:creator>
 <guid isPermaLink="false">542 at https://drupalinl.info.ucl.ac.be</guid>
</item>
<item>
 <title>Interdomain Traffic Engineering in a Locator/Identifier Separation Context</title>
 <link>https://drupalinl.info.ucl.ac.be/publications/interdomain-traffic-engineering-locatoridentifier-separation-context</link>
 <description>&lt;p&gt;The Routing Research Group (RRG) of the Internet Research Task Force&lt;br /&gt;
(IRTF) is currently discussing several architectural solutions to&lt;br /&gt;
build an interdomain routing architecture that scales better than the&lt;br /&gt;
existing one. The solutions family currently being discussed concerns the addresses&lt;br /&gt;
separation into locators and identifiers, LISP being one of them.&lt;br /&gt;
Such a separation provides opportunities in terms of traffic&lt;br /&gt;
engineering.  In this paper, we propose an open and flexible solution&lt;br /&gt;
that allows an ISP using identifier/locator separation to engineer its&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://drupalinl.info.ucl.ac.be/publications/interdomain-traffic-engineering-locatoridentifier-separation-context&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="https://drupalinl.info.ucl.ac.be/category/visibility/public">Public</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/idips">IDIPS</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/inm">INM</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/lisp">LISP</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/traffic-engineering">Traffic Engineering</category>
 <pubDate>Fri, 12 Sep 2008 15:02:33 +0000</pubDate>
 <dc:creator>dsaucez</dc:creator>
 <guid isPermaLink="false">514 at https://drupalinl.info.ucl.ac.be</guid>
</item>
<item>
 <title>On BGP Communities</title>
 <link>https://drupalinl.info.ucl.ac.be/publications/bgp-communities</link>
 <description>&lt;p&gt;This paper focuses on BGP communities, a particular BGP attribute that has not yet been extensively studied by the research community.  It allows an operator to group destinations in a single entity to which the same routing decisions might be applied.  In this paper, we show that the usage of this attribute has increased and that it also contributes to routing table growth.  In addition, we propose a taxonomy of BGP community attributes to allow operators to better document their communities.  We further manually collect information on BGP communities and tag it according to our taxonomy.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://drupalinl.info.ucl.ac.be/publications/bgp-communities&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="https://drupalinl.info.ucl.ac.be/category/visibility/public">Public</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/bgp">BGP</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/community-attribute">community attribute</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/traffic-engineering">Traffic Engineering</category>
 <pubDate>Thu, 06 Mar 2008 13:31:11 +0000</pubDate>
 <dc:creator>donnet</dc:creator>
 <guid isPermaLink="false">430 at https://drupalinl.info.ucl.ac.be</guid>
</item>
<item>
 <title>IDIPS : ISP-Driven Informed Path Selection</title>
 <link>https://drupalinl.info.ucl.ac.be/publications/idips-isp-driven-informed-path-selection</link>
 <description>&lt;p&gt;This draft describes a simple network-based protocol to facilitate Path Selection and to improve traffic engineering capabilities in multihomed corporate networks. With this protocol, any network device that requires to select a path among a list of different paths asks a Traffic Engineering service called IDIPS (ISP-Driven Informed Path Selection) to obtain an ordered list of the possible paths. The ordering is constructed according to policies and performance requirements of both the host and network provider.&lt;/p&gt;
</description>
 <category domain="https://drupalinl.info.ucl.ac.be/category/visibility/public">Public</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/lisp">LISP</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/rrg">RRG</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/shim6">shim6</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/traffic-engineering">Traffic Engineering</category>
 <enclosure url="https://drupalinl.info.ucl.ac.be/system/files/draft-saucez-idips-00_0.txt" length="49550" type="text/plain" />
 <pubDate>Mon, 18 Feb 2008 16:41:04 +0000</pubDate>
 <dc:creator>dsaucez</dc:creator>
 <guid isPermaLink="false">416 at https://drupalinl.info.ucl.ac.be</guid>
</item>
<item>
 <title>The case for an informed path selection service</title>
 <link>https://drupalinl.info.ucl.ac.be/publications/case-informed-path-selection-service</link>
 <description>&lt;p&gt;With today&#039;s peer-to-peer applications, more and more content is available from multiple sources. In tomorrow&#039;s Internet hosts will have multiple paths to reach one destination host with the deployment of dual-stack IPv4/IPv6 hosts, but also with new techniques such as shim6 or other locator/identifier mechanisms being discussed within the IRTF RRG. All these hosts will need to rank paths in order to select the best paths to reach a given destination/content.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://drupalinl.info.ucl.ac.be/publications/case-informed-path-selection-service&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="https://drupalinl.info.ucl.ac.be/category/visibility/public">Public</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/lisp">LISP</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/rrg">RRG</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/shim6">shim6</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/traffic-engineering">Traffic Engineering</category>
 <enclosure url="https://drupalinl.info.ucl.ac.be/system/files/draft-bonaventure-informed-path-selection-00.txt" length="46444" type="text/plain" />
 <pubDate>Mon, 18 Feb 2008 16:37:32 +0000</pubDate>
 <dc:creator>dsaucez</dc:creator>
 <guid isPermaLink="false">415 at https://drupalinl.info.ucl.ac.be</guid>
</item>
</channel>
</rss>
