<?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 - IDIPS</title>
 <link>https://drupalinl.info.ucl.ac.be/taxonomy/term/112/0</link>
 <description></description>
 <language>en</language>
<item>
 <title>The PROXIDOR Service</title>
 <link>https://drupalinl.info.ucl.ac.be/publications/draft-akonjang-alto-proxidor-00</link>
 <description>&lt;p&gt;Several applications, such as peer-to-peer (P2P), content&lt;br /&gt;
   distribution and realtime services rely on selection mechanisms in&lt;br /&gt;
   order to select the peer or server from which to request the service.&lt;br /&gt;
   Examples of such services are: file sharing, media streaming and&lt;br /&gt;
   voice gateways.&lt;/p&gt;
&lt;p&gt;   Application-layer selection algorithms do not typically take into&lt;br /&gt;
   account network-layer topology information; either that information&lt;br /&gt;
   is unavailable to them, or when such information is available (e.g.,&lt;br /&gt;
   from BGP Looking Glass servers), it does not include sufficient&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://drupalinl.info.ucl.ac.be/publications/draft-akonjang-alto-proxidor-00&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>
 <pubDate>Tue, 03 Mar 2009 14:19:24 +0000</pubDate>
 <dc:creator>dsaucez</dc:creator>
 <guid isPermaLink="false">564 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>Why should the Traffic Optimization not be restricted to the Application-Layer?</title>
 <link>https://drupalinl.info.ucl.ac.be/publications/why-should-traffic-optimization-not-be-restricted-application-layer</link>
 <description>&lt;p&gt;The Application-Layer Traffic Optimization (ALTO) problem is being discussed within the IETF and more globally by the research community and some enterprises. In this memo, we argue that it is important to conceive general-purpose mechanisms to solve this problem. By general-purpose we say not only application independent but also layer independent mechanism. The generality can be obtained because the underlying problem is the same regardless the application or the layer.&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/alto">ALTO</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/generalization">generalization</category>
 <category domain="https://drupalinl.info.ucl.ac.be/keywords/idips">IDIPS</category>
 <pubDate>Mon, 07 Jul 2008 12:12:32 +0000</pubDate>
 <dc:creator>dsaucez</dc:creator>
 <guid isPermaLink="false">480 at https://drupalinl.info.ucl.ac.be</guid>
</item>
</channel>
</rss>
