| 59 | ==== Monitoring Prototype ==== |
| 60 | |
| 61 | Demonstration of GENI aggregate-based reporting and alerting system prototype. System is designed to collect data from shared sources provided by aggregators. |
| 62 | |
| 63 | Participants: |
| 64 | * V. Cody Bumgardner, cody@uky.edu, Univ. of Kentucky |
| 65 | |
| 66 | ==== Internet2 OpenFlow ==== |
| 67 | |
| 68 | Internet2 will demo virtualization on the Advanced Layer 2 Service with Flowspace Firewall, showing a guest controller in addition to the standard Advanced Layer 2 Service OESS controller. We will talk about how we plan to allow experimental OpenFlow controllers, including GENI controllers, running alongside our production controller. |
| 69 | |
| 70 | Participants: |
| 71 | * Matt Zekauskas, matt@internet2.edu, Internet2 |
| 72 | |
| 151 | ==== Virtual Topology Service (VTS) ==== |
| 152 | |
| 153 | The Virtual Topology Service (VTS) will allow experimenters to reserve complex and flexible programmable virtual topologies on top of GENI substrates. Virtual switches supporting various SDN technologies (multiple versions of OpenFlow, etc), and simple traditional switches, will be available, and VTS tools will make it easy to reserve an entirely topology from a single descriptive rspec. We will demonstrate the current state of the service, and expect a prototype to be ready for brave early adopters to try out soon after GEC. |
| 154 | |
| 155 | Participants: |
| 156 | * Nick Bastin, nick.bastin@gmail.com |
| 157 | |
| 158 | ==== Simulation, Detection, and Denial of ping Attack ==== |
| 159 | |
| 160 | Simulation, Detection, and Denial of ping attack: The demo topology in GENI consist of 2 nodes say Host1 and Host2. Host1 will send the ping's to the Host2. Host2 will continuously measure the number of ping's received from the Host1 and detect the ping attack. The detection will trigger re-programming of the network to deny pinging connection. |
| 161 | |
| 162 | Participants: |
| 163 | * Satyajeet M. Padmanabhi, smpadmanabhi@gmail.com |
| 164 | * Deniz Gurkan, dgurkan@central.uh.edu, Univ. of Houston |
| 165 | |
| 166 | ==== Tapestry in GENI ==== |
| 167 | |
| 168 | In this demonstration we will explain how Tapestry, a software defined application (Developed by Infoblox/flowforwarding.org) will help in continuous monitoring of the network and gives us the Network Complexity Index. Tapestry will be installed and running on a SDN switch which fully monitors the entire network and extracting the complexity index based on the DNS requests made on the network. |
| 169 | |
| 170 | Our aim is to run this Tapestry on the GENI cloud platform and identify the complexity based on the DNS requests made on the network and also focus on how rapidly the network complexity is growing and is needed to better management and control. |
| 171 | |
| 172 | Participants: |
| 173 | * rbagli@uh.edu, Univ. of Houston |
| 174 | * Deniz Gurkan, dgurkan@central.uh.edu, Univ. of Houston |
| 175 | |
| 176 | ==== Protocol Pattern Matching on LINC Switch ==== |
| 177 | |
| 178 | To optimize a protocol pattern matching mechanism on the LINC switch: inspiration was derived from Protocol Oblivious Forwarding (POF), which can be compatible with any new protocol. |
| 179 | |
| 180 | Participants: |
| 181 | * v_chanpol@hotmail.com, Univ. of Houston |
| 182 | * Deniz Gurkan, dgurkan@central.uh.edu, Univ. of Houston |
| 183 | |
| 184 | ==== Network Characterization of Hadoop using GENI ==== |
| 185 | |
| 186 | Hadoop’s implementation of !MapReduce in a multi-rack cluster is dependent upon the top of the rack switches and of the aggregator switches connecting multiple racks. We will demo network characterization and requirements perspective for Hadoop using the GENI testbed. |
| 187 | |
| 188 | Participants: |
| 189 | * Abdul Navaz, navaz.enc@gmail.com, Univ. of Houston |
| 190 | * Deniz Gurkan, dgurkan@central.uh.edu, Univ. of Houston |
| 191 | |
| 204 | ==== Content Retrieval in MobilityFirst FIA ==== |
| 205 | |
| 206 | Global Unique Identifiers (GUIDs) used in the !MobilityFirst Future Internet Architecture can be used to address different classes of Internet objects, from devices to contents, from services to context. In this demo we will showcase how contents can be retrieved through the use of the proof of concept prototype we have implemented working on any Linux/Android device. More information on !MobilityFirst FIA project can be found at http://mobilityfirst.winlab.rutgers.edu |
| 207 | |
| 208 | Participants: |
| 209 | * Wireless Information Network Laboratory (WINLAB) at Rutgers University |
| 210 | * Franceso Bronzino, bronzino@winlab.rutgers.edu |
| 211 | * Ivan Seskar, seskar@winlab.rutgers.edu |
| 212 | * Kiran Nagaraja, nkiran@winlab.rutgers.edu |
| 213 | |
| 214 | ==== Clemson Vertical Handover ==== |
| 215 | |
| 216 | A GENI testbed for vertical handovers. The Clemson GENI !WiFi and WiMAX networks have been integrated into a vertical handover testbed where experimenters can evaluate novel handover algorithms. |
| 217 | |
| 218 | Participants: |
| 219 | * Ryan Izard, rizard@clemson.edu, Clemson Univ. |
| 220 | * Adam Hodges, hodges8@g.clemson.edu, Clemson Univ. |
| 221 | |
| 222 | ==== Course Modules for Teaching Networking Concepts ==== |
| 223 | |
| 224 | We will demonstrate the education modules we have developed for educators to use in their undergraduate Computer Networking classes. These consist of concept demonstration modules as well as student assignment modules. Each module is comprised of a short overview video, longer tutorial videos, written tutorials, and canned demonstrations. The concept modules also include presentation slides while the assignment modules include completed assignments as samples for the instructor. |
| 225 | |
| 226 | Participants: |
| 227 | * Jay Aikat, aikat@cs.unc.edu, Univ. of North Carolina |
| 228 | |
| 229 | ==== Virtualized Services via OpenFlow Based end-to-end Networking ==== |
| 230 | |
| 231 | This system demonstrates a novel methodology for providing arbitrary virtualized services via Software Defined Networking (SDN). The tabletop demonstration provides virtual channels for services from the service provider all the way through to the user passed the user networking hardware. The system utilizes OpenFlow to control the network which enables priority based packet forwarding for required services. As an example, the updated emergency communication system implemented as the priority service will be demonstrated. Since the last demonstration, this demo has been updated on several levels. The additional services were implemented, thick clients replaced by thin clients, improved GUI made. |
| 232 | |
| 233 | Participants: |
| 234 | * Milos Manic, misko@uidaho.edu, Univ. of Idaho |
| 235 | * Dumidu Wijayasekara, dumidu.wijayasekara@gmail.com |
| 236 | |
| 254 | |
| 255 | ==== VNODE and FLARE ==== |
| 256 | |
| 257 | We updated VNode system to next version and we will be showing our progress of VNode system, especially focusing on applications working over VNode system. We are planning to prepare three kinds of demos, one for video multicasting and transcoding in virtual network, second for FLARE switch, and at last for federation between different virtualization platforms. |
| 258 | |
| 259 | Participants: |
| 260 | * Univ. of Tokyo |
| 261 | * Akihiro Nakao, nakao@iii.u-tokyo.ac.jp |
| 262 | * Shu Yamamoto, shu@iii.u-tokyo.ac.jp |
| 263 | * Toshiaki Tarui, toshiaki.tarui.my@hitachi.com, Hitachi |
| 264 | |
| 265 | ==== Federation Tools, Authorities, and APIs ==== |
| 266 | |
| 267 | In this demo we will demonstrate the further integration of what was discussed at GEC18 (International federation, federation tool session). How can we set up a federation with the Federation APIs, what tools and authorities support this and what are the advantages and experiences. |
| 268 | |
| 269 | Participants: |
| 270 | * Brecht Vermeulen, brecht.vermeulen@iminds.be, iMinds |
| 271 | * Rob Ricci, ricci@cs.utah.edu, Univ. of Utah |
| 272 | * Marshall Brinn, mbrinn@bbn.com, GPO |