Changes between Version 2 and Version 3 of PathletRouting

09/08/10 13:21:23 (14 years ago)



  • PathletRouting

    v2 v3  
    1 = Summary =
    3 Pathlet routing is an exciting new routing protocol, proposed by [ Brighten Godfrey], a promising new faculty member at the University of Illinois at Urbana-Champaign.  Pathlet Routing is designed to provide more flexibility to both internet providers and users. In a nutshell, it's source routing over a virtual topology. By representing the Internet as a virtual topology independent of the physical topology, network owners can declare services and policy constraints very expressively. By allowing users to select any path within this virtual topology, users can select routes that are appropriate to the application or more efficient and can react quickly to dynamics in the network.
    5 Pathlet routing was first presented at [ HotNets 2008], a prestigious networking workshop on innovative network research. A completed version was also published in [ SIGCOMM 2009], one of the most competitive and influential conferences within the networking community. 
    7 For more information refer to [ pathlet's website]
    9 Pathlets are an alternative to IP routing and thus, it's not feasible to deploy the protocol natively for large scale testing within the current Internet architecture where IP is the only option.
    11 GENI is the ideal environment where Pathlet routing can be deployed and matured before integrating to the global Internet. For Gec8 we have integrated the pathlet routing technology within the GPO's GENI infrastructure. We are now looking for expanding this deployment in more GENI sites.
    13 = Technical Requirements for GENI Integration =
    14 In order to be able to support Pathlet routing within a GENI site, it's needed :
    15  * an '''OpenFlow switch''' running version 1.0 of the OpenFlow protocol
    16  * the switch should be controlled by a '''Flowvisor''', preferably locally but if this is not available, GPO can provide a FlowVisor running at the GPO lab
    17  * the ability to point traffic from the pathlet slice to a Nox controller running remotely (@GPO)
    19 In order to be able to fully test the pathlet architecture, some end hosts should also be deployed in some sites :
    20  * a PlanetLab host that is connected to the OpenFlow switch, the host should be controlled by a local [ myPLC]
    22 == Contact info ==
    23 ||'''PI'''|| Brighten Godfrey || [] ||
    24 ||'''grad student'''|| Ashish Vulimir || [] ||
    25 ||'''grad student'''|| Qingxi Li || [] ||