<?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 - INM</title>
 <link>https://drupalinl.info.ucl.ac.be/taxonomy/term/131/0</link>
 <description></description>
 <language>en</language>
<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>
</channel>
</rss>
