Changes between Version 12 and Version 13 of GENIBibliography


Ignore:
Timestamp:
04/08/14 14:47:44 (10 years ago)
Author:
Mark Berman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIBibliography

    v12 v13  
    466466
    467467
     468<a class="EntryGoto" id="Bastin, Nicholas and Bavier, Andy and Blaine, Jessica and Chen, Jim and Krishnan, Narayan and Mambretti, Joe and McGeer, Rick and Ricci, Rob and Watts, Nicki"></a>
     469<b class="myheading" style="position: relative; left: 5%;">Bastin, Nicholas and Bavier, Andy and Blaine, Jessica and Chen, Jim and Krishnan, Narayan and Mambretti, Joe and McGeer, Rick and Ricci, Rob and Watts, Nicki</b>
     470
     471<div class="BibEntry">
     472
     473<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     474
     475<li>
     476
     477
     478<tr>
     479     <td valign="top">Author</td>
     480     <td valign="top">Bastin, Nicholas and Bavier, Andy and Blaine, Jessica and Chen, Jim and Krishnan, Narayan and Mambretti, Joe and McGeer, Rick and Ricci, Rob and Watts, Nicki</td>
     481</tr>
     482
     483<tr>
     484     <td valign="top">Title</td>
     485     <td valign="top">The InstaGENI initiative: An architecture for distributed systems and advanced programmable networks</td>
     486</tr>
     487
     488<tr>
     489     <td valign="top">Journal</td>
     490     <td valign="top">Computer Networks</td>
     491</tr>
     492
     493<tr>
     494     <td valign="top">Year</td>
     495     <td valign="top">2014</td>
     496</tr>
     497
     498<tr>
     499     <td valign="top">Abstract</td>
     500     <td valign="top">In this paper, we describe InstaGENI, a distributed cloud based on programmable networks designed for the GENI Mesoscale deployment and large-scale distributed research projects. The InstaGENI architecture closely integrates a lightweight cluster design with software-defined networking, Hardware-as-a-Service and Containers-as-a-Service, remote monitoring and management, and high-performance inter-site networking. The initial InstaGENI deployment will encompass 34 sites across the United States, interconnected through a specialized GENI backbone network deployed over national, regional and campus research and education networks, with international network extensions to sites across the world.</td>
     501</tr>
     502
     503
     504
     505<tr>
     506     <td valign="top">DOI</td>
     507     <td valign="top">10.1016/j.bjp.2013.12.034</td>
     508</tr>
     509
     510
     511
     512<tr>
     513     <td valign="top">URL</td>
     514     <td valign="top"><a href="http://dx.doi.org/10.1016/j.bjp.2013.12.034">http://dx.doi.org/10.1016/j.bjp.2013.12.034</a></td>
     515</tr>
     516
     517
     518</li>
     519
     520</table></div><br><br>
     521
     522
     523
     524
    468525<a class="EntryGoto" id="Bavier, Andy and Coady, Yvonne and Mack, Tony and Matthews, Chris and Mambretti, Joe and McGeer, Rick and Mueller, Paul and Snoeren, Alex and Yuen, Marco"></a>
    469526<b class="myheading" style="position: relative; left: 5%;">Bavier, Andy and Coady, Yvonne and Mack, Tony and Matthews, Chris and Mambretti, Joe and McGeer, Rick and Mueller, Paul and Snoeren, Alex and Yuen, Marco</b>
     
    29132970
    29142971
     2972<a class="EntryGoto" id="Jofre, Jordi and Velayos, Celia and Landi, Giada and Giertych, Micha&#x0142; and Hume, Alastair C. and Francis, Gareth and Vico Oton, Albert"></a>
     2973<b class="myheading" style="position: relative; left: 5%;">Jofre, Jordi and Velayos, Celia and Landi, Giada and Giertych, Micha&#x0142; and Hume, Alastair C. and Francis, Gareth and Vico Oton, Albert</b>
     2974
     2975<div class="BibEntry">
     2976
     2977<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     2978
     2979<li>
     2980
     2981
     2982<tr>
     2983     <td valign="top">Author</td>
     2984     <td valign="top">Jofre, Jordi and Velayos, Celia and Landi, Giada and Giertych, Micha&#x0142; and Hume, Alastair C. and Francis, Gareth and Vico Oton, Albert</td>
     2985</tr>
     2986
     2987<tr>
     2988     <td valign="top">Title</td>
     2989     <td valign="top">Federation of the BonFIRE multi-cloud infrastructure with networking facilities</td>
     2990</tr>
     2991
     2992<tr>
     2993     <td valign="top">Journal</td>
     2994     <td valign="top">Computer Networks</td>
     2995</tr>
     2996
     2997<tr>
     2998     <td valign="top">Year</td>
     2999     <td valign="top">2014</td>
     3000</tr>
     3001
     3002<tr>
     3003     <td valign="top">Abstract</td>
     3004     <td valign="top">Network performance in terms of throughput, latency, packet loss or jitter significantly influences user's quality of experience of cloud applications. Network services impact on cloud applications performance and this impact is even more significant when the cloud infrastructure spreads over different administrative domains, such as in a federated cloud or hybrid-cloud scenarios. Given this strong coupling between cloud application performance and network performance there is great value to be gained by supporting advanced controlled networking functionalities between distributed cloud infrastructures. These functionalities would be useful to the Future Internet (FI) experimentation community as well as future production clouds. This paper describes an architecture and a set of procedures to interconnect a multi-cloud environment with advanced facilities for controlled networking. This integration allows the provisioning of customized network functions and services in support of experiments running in a multi-cloud test-bed. The possibility to control the network connectivity is a key feature to provide better performance for the experimenters' cloud applications. We focus on the details of federating three advanced networking facilities with the BonFIRE multi-cloud environment. These three networking facilities are: FEDERICA, which supports controlled routing; G&#x45;&#x0301;ANT's Bandwidth-on-Demand service and OFELIA that uses OpenFlow to provide Software Defined Network functionalities. The interconnections with FEDERICA and G&#x45;&#x0301;ANT are already active, while OFELIA is envisaged as future work for a third facility to interconnect.</td>
     3005</tr>
     3006
     3007
     3008
     3009<tr>
     3010     <td valign="top">DOI</td>
     3011     <td valign="top">10.1016/j.bjp.2013.11.012</td>
     3012</tr>
     3013
     3014
     3015
     3016<tr>
     3017     <td valign="top">URL</td>
     3018     <td valign="top"><a href="http://dx.doi.org/10.1016/j.bjp.2013.11.012">http://dx.doi.org/10.1016/j.bjp.2013.11.012</a></td>
     3019</tr>
     3020
     3021
     3022</li>
     3023
     3024</table></div><br><br>
     3025
     3026
     3027
     3028
    29153029<a class="EntryGoto" id="Ju, Xi and Zhang, Hongwei and Zeng, Wenjie and Sridharan, Mukundan and Li, Jing and Arora, Anish and Ramnath, Rajiv and Xin, Yufeng"></a>
    29163030<b class="myheading" style="position: relative; left: 5%;">Ju, Xi and Zhang, Hongwei and Zeng, Wenjie and Sridharan, Mukundan and Li, Jing and Arora, Anish and Ramnath, Rajiv and Xin, Yufeng</b>
     
    31193233
    31203234
     3235<a class="EntryGoto" id="Kim, Dongkyun and Kim, Joobum and Wang, Gicheol and Park, Jin-Hyung and Kim, Seung-Hae"></a>
     3236<b class="myheading" style="position: relative; left: 5%;">Kim, Dongkyun and Kim, Joobum and Wang, Gicheol and Park, Jin-Hyung and Kim, Seung-Hae</b>
     3237
     3238<div class="BibEntry">
     3239
     3240<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     3241
     3242<li>
     3243
     3244
     3245<tr>
     3246     <td valign="top">Author</td>
     3247     <td valign="top">Kim, Dongkyun and Kim, Joobum and Wang, Gicheol and Park, Jin-Hyung and Kim, Seung-Hae</td>
     3248</tr>
     3249
     3250<tr>
     3251     <td valign="top">Title</td>
     3252     <td valign="top">K-GENI testbed deployment and federated meta operations experiment over GENI and KREONET</td>
     3253</tr>
     3254
     3255<tr>
     3256     <td valign="top">Journal</td>
     3257     <td valign="top">Computer Networks</td>
     3258</tr>
     3259
     3260<tr>
     3261     <td valign="top">Year</td>
     3262     <td valign="top">2014</td>
     3263</tr>
     3264
     3265<tr>
     3266     <td valign="top">Abstract</td>
     3267     <td valign="top">The classical Internet has confronted many drawbacks in terms of network security, scalability, and performance, although it has strongly influenced the development and evolution of diverse network technologies, applications, and services. Therefore, new innovative research on the Future Internet has been performed to resolve the inherent weaknesses of the traditional Internet, which, in turn, requires new at-scale network testbeds and research infrastructure for large-scale experiments. In this context, K-GENI has been developed as an international programmable Future Internet testbed in the GENI spiral-2 program, and it has been operational between the USA (GENI) and Korea (KREONET) since 2010. The K-GENI testbed and the related collaborative efforts will be introduced with two major topics in this paper: (1) the design and deployment of the K-GENI testbed and (2) the federated meta operations between the K-GENI and GENI testbeds. Regarding the second topic in particular, we will describe how meta operations are federated across K-GENI between GMOC (GENI Meta Operations Center) and DvNOC (Distributed virtual Network Operations Center on KREONET/K-GENI), which is the first trial of an international experiment on the federated network operations over GENI.</td>
     3268</tr>
     3269
     3270
     3271
     3272<tr>
     3273     <td valign="top">DOI</td>
     3274     <td valign="top">10.1016/j.bjp.2013.11.016</td>
     3275</tr>
     3276
     3277
     3278
     3279<tr>
     3280     <td valign="top">URL</td>
     3281     <td valign="top"><a href="http://dx.doi.org/10.1016/j.bjp.2013.11.016">http://dx.doi.org/10.1016/j.bjp.2013.11.016</a></td>
     3282</tr>
     3283
     3284
     3285</li>
     3286
     3287</table></div><br><br>
     3288
     3289
     3290
     3291
    31213292<a class="EntryGoto" id="Kim, Hyunjun and Lee, Sungwon"></a>
    31223293<b class="myheading" style="position: relative; left: 5%;">Kim, Hyunjun and Lee, Sungwon</b>
     
    32583429
    32593430
     3431<a class="EntryGoto" id="Kobayashi, Masayoshi and Seetharaman, Srini and Parulkar, Guru and Appenzeller, Guido and Little, Joseph and van Reijendam, Johan and Weissmann, Paul and McKeown, Nick"></a>
     3432<b class="myheading" style="position: relative; left: 5%;">Kobayashi, Masayoshi and Seetharaman, Srini and Parulkar, Guru and Appenzeller, Guido and Little, Joseph and van Reijendam, Johan and Weissmann, Paul and McKeown, Nick</b>
     3433
     3434<div class="BibEntry">
     3435
     3436<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     3437
     3438<li>
     3439
     3440
     3441<tr>
     3442     <td valign="top">Author</td>
     3443     <td valign="top">Kobayashi, Masayoshi and Seetharaman, Srini and Parulkar, Guru and Appenzeller, Guido and Little, Joseph and van Reijendam, Johan and Weissmann, Paul and McKeown, Nick</td>
     3444</tr>
     3445
     3446<tr>
     3447     <td valign="top">Title</td>
     3448     <td valign="top">Maturing of OpenFlow and Software-defined Networking through deployments</td>
     3449</tr>
     3450
     3451<tr>
     3452     <td valign="top">Journal</td>
     3453     <td valign="top">Computer Networks</td>
     3454</tr>
     3455
     3456<tr>
     3457     <td valign="top">Year</td>
     3458     <td valign="top">2014</td>
     3459</tr>
     3460
     3461<tr>
     3462     <td valign="top">Abstract</td>
     3463     <td valign="top">Software-defined Networking (SDN) has emerged as a new paradigm of networking that enables network operators, owners, vendors, and even third parties to innovate and create new capabilities at a faster pace. The SDN paradigm shows potential for all domains of use, including data centers, cellular providers, service providers, enterprises, and homes. Over a three-year period, we deployed SDN technology at our campus and at several other campuses nation-wide with the help of partners. These deployments included the first-ever SDN prototype in a lab for a (small) global deployment. The four-phased deployments and demonstration of new networking capabilities enabled by SDN played an important role in maturing SDN and its ecosystem. We share our experiences and lessons learned that have to do with demonstration of SDN's potential; its influence on successive versions of OpenFlow specification; evolution of SDN architecture; performance of SDN and various components; and growing the ecosystem.</td>
     3464</tr>
     3465
     3466
     3467
     3468<tr>
     3469     <td valign="top">DOI</td>
     3470     <td valign="top">10.1016/j.bjp.2013.10.011</td>
     3471</tr>
     3472
     3473
     3474
     3475<tr>
     3476     <td valign="top">URL</td>
     3477     <td valign="top"><a href="http://dx.doi.org/10.1016/j.bjp.2013.10.011">http://dx.doi.org/10.1016/j.bjp.2013.10.011</a></td>
     3478</tr>
     3479
     3480
     3481</li>
     3482
     3483</table></div><br><br>
     3484
     3485
     3486
     3487
    32603488<a class="EntryGoto" id="Krishnappa, D. K. and Irwin, D. and Lyons, E. and Zink, M."></a>
    32613489<b class="myheading" style="position: relative; left: 5%;">Krishnappa, D. K. and Irwin, D. and Lyons, E. and Zink, M.</b>
     
    39034131
    39044132
     4133<div class="BibEntry">
     4134
     4135<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     4136
     4137<li>
     4138
     4139
     4140<tr>
     4141     <td valign="top">Author</td>
     4142     <td valign="top">Maccherani, E. and Femminella, M. and Lee, J. W. and Francescangeli, R. and Janak, J. and Reali, G. and Schulzrinne, H.</td>
     4143</tr>
     4144
     4145<tr>
     4146     <td valign="top">Title</td>
     4147     <td valign="top">Extending the NetServ autonomic management capabilities using OpenFlow</td>
     4148</tr>
     4149
     4150<tr>
     4151     <td valign="top">Booktitle</td>
     4152     <td valign="top">Network Operations and Management Symposium (NOMS), 2012 IEEE</td>
     4153</tr>
     4154
     4155<tr>
     4156     <td valign="top">Year</td>
     4157     <td valign="top">2012</td>
     4158</tr>
     4159
     4160
     4161
     4162<tr>
     4163     <td valign="top">DOI</td>
     4164     <td valign="top">10.1109/NOMS.2012.6211961</td>
     4165</tr>
     4166
     4167
     4168
     4169<tr>
     4170     <td valign="top">URL</td>
     4171     <td valign="top"><a href="http://dx.doi.org/10.1109/NOMS.2012.6211961">http://dx.doi.org/10.1109/NOMS.2012.6211961</a></td>
     4172</tr>
     4173
     4174
     4175</li>
     4176
     4177</table></div><br><br>
     4178
     4179
    39054180
    39064181
     
    40344309
    40354310
     4311<a class="EntryGoto" id="Mambretti, Joe and Chen, Jim and Yeh, Fei"></a>
     4312<b class="myheading" style="position: relative; left: 5%;">Mambretti, Joe and Chen, Jim and Yeh, Fei</b>
     4313
     4314<div class="BibEntry">
     4315
     4316<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     4317
     4318<li>
     4319
     4320
     4321<tr>
     4322     <td valign="top">Author</td>
     4323     <td valign="top">Mambretti, Joe and Chen, Jim and Yeh, Fei</td>
     4324</tr>
     4325
     4326<tr>
     4327     <td valign="top">Title</td>
     4328     <td valign="top">Creating environments for innovation: Designing and implementing advanced experimental network research testbeds based on the Global Lambda Integrated Facility and the StarLight Exchange</td>
     4329</tr>
     4330
     4331<tr>
     4332     <td valign="top">Journal</td>
     4333     <td valign="top">Computer Networks</td>
     4334</tr>
     4335
     4336<tr>
     4337     <td valign="top">Year</td>
     4338     <td valign="top">2014</td>
     4339</tr>
     4340
     4341
     4342
     4343<tr>
     4344     <td valign="top">DOI</td>
     4345     <td valign="top">10.1016/j.bjp.2013.12.024</td>
     4346</tr>
     4347
     4348
     4349
     4350<tr>
     4351     <td valign="top">URL</td>
     4352     <td valign="top"><a href="http://dx.doi.org/10.1016/j.bjp.2013.12.024">http://dx.doi.org/10.1016/j.bjp.2013.12.024</a></td>
     4353</tr>
     4354
     4355
     4356</li>
     4357
     4358</table></div><br><br>
     4359
     4360
     4361
     4362
    40364363<a class="EntryGoto" id="Mandvekar, Lokesh and Qiao, Chunming and Husain, Mohammad I."></a>
    40374364<b class="myheading" style="position: relative; left: 5%;">Mandvekar, Lokesh and Qiao, Chunming and Husain, Mohammad I.</b>
     
    43244651
    43254652
     4653<a class="EntryGoto" id="Medhi, Deep and Ramamurthy, Byrav and Scoglio, Caterina and Rohrer, Justin P. and &#x43;&#x0327;etinkaya, Egemen K. and Cherukuri, Ramkumar and Liu, Xuan and Angu, Pragatheeswaran and Bavier, Andy and Buffington, Cort and Sterbenz, James P. G."></a>
     4654<b class="myheading" style="position: relative; left: 5%;">Medhi, Deep and Ramamurthy, Byrav and Scoglio, Caterina and Rohrer, Justin P. and &#x43;&#x0327;etinkaya, Egemen K. and Cherukuri, Ramkumar and Liu, Xuan and Angu, Pragatheeswaran and Bavier, Andy and Buffington, Cort and Sterbenz, James P. G.</b>
     4655
     4656<div class="BibEntry">
     4657
     4658<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     4659
     4660<li>
     4661
     4662
     4663<tr>
     4664     <td valign="top">Author</td>
     4665     <td valign="top">Medhi, Deep and Ramamurthy, Byrav and Scoglio, Caterina and Rohrer, Justin P. and &#x43;&#x0327;etinkaya, Egemen K. and Cherukuri, Ramkumar and Liu, Xuan and Angu, Pragatheeswaran and Bavier, Andy and Buffington, Cort and Sterbenz, James P. G.</td>
     4666</tr>
     4667
     4668<tr>
     4669     <td valign="top">Title</td>
     4670     <td valign="top">The GpENI testbed: Network infrastructure, implementation experience, and experimentation</td>
     4671</tr>
     4672
     4673<tr>
     4674     <td valign="top">Journal</td>
     4675     <td valign="top">Computer Networks</td>
     4676</tr>
     4677
     4678<tr>
     4679     <td valign="top">Year</td>
     4680     <td valign="top">2014</td>
     4681</tr>
     4682
     4683<tr>
     4684     <td valign="top">Abstract</td>
     4685     <td valign="top">The Great Plains Environment for Network Innovation (GpENI) is an international programmable network testbed centered initially in the Midwest US with the goal to provide programmability across the entire protocol stack. In this paper, we present the overall GpENI framework and our implementation experience for the programmable routing environment and the dynamic circuit network (DCN). GpENI is built to provide a collaborative research infrastructure enabling the research community to conduct experiments in Future Internet architecture. We present illustrative examples of our experimentation in the GpENI platform.</td>
     4686</tr>
     4687
     4688
     4689
     4690<tr>
     4691     <td valign="top">DOI</td>
     4692     <td valign="top">10.1016/j.bjp.2013.12.027</td>
     4693</tr>
     4694
     4695
     4696
     4697<tr>
     4698     <td valign="top">URL</td>
     4699     <td valign="top"><a href="http://dx.doi.org/10.1016/j.bjp.2013.12.027">http://dx.doi.org/10.1016/j.bjp.2013.12.027</a></td>
     4700</tr>
     4701
     4702
     4703</li>
     4704
     4705</table></div><br><br>
     4706
     4707
     4708
     4709
    43264710<a class="EntryGoto" id="Mitroff, Sarah"></a>
    43274711<b class="myheading" style="position: relative; left: 5%;">Mitroff, Sarah</b>
     
    51525536
    51535537
     5538<a class="EntryGoto" id="Schwerdel, Dennis and Reuther, Bernd and Zinner, Thomas and M\\uller, Paul and Tran-Gia, Phouc"></a>
     5539<b class="myheading" style="position: relative; left: 5%;">Schwerdel, Dennis and Reuther, Bernd and Zinner, Thomas and M\\uller, Paul and Tran-Gia, Phouc</b>
     5540
     5541<div class="BibEntry">
     5542
     5543<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     5544
     5545<li>
     5546
     5547
     5548<tr>
     5549     <td valign="top">Author</td>
     5550     <td valign="top">Schwerdel, Dennis and Reuther, Bernd and Zinner, Thomas and M\\uller, Paul and Tran-Gia, Phouc</td>
     5551</tr>
     5552
     5553<tr>
     5554     <td valign="top">Title</td>
     5555     <td valign="top">Future Internet research and experimentation: The G-Lab approach</td>
     5556</tr>
     5557
     5558<tr>
     5559     <td valign="top">Journal</td>
     5560     <td valign="top">Computer Networks</td>
     5561</tr>
     5562
     5563<tr>
     5564     <td valign="top">Year</td>
     5565     <td valign="top">2014</td>
     5566</tr>
     5567
     5568<tr>
     5569     <td valign="top">Abstract</td>
     5570     <td valign="top">The German Lab (G-Lab) project aims to investigate architectural concepts and technologies for a new inter-networking architecture as an integrated approach between theoretic and experimental studies. Thus G-Lab consists of two major fields of activities: research studies of future network components and the design and setup of experimental facilities. Both are controlled by the same community to ensure that the experimental facility meets the demands of the researchers. Researchers gain access to virtualized resources or may gain exclusive access to resources if necessary. We present the current setup of the experimental facility, describing the available hardware, management of the platform, the utilization of the PlanetLab software and the user management. Moreover, a new approach to setup and deploy virtual network topologies will be described.</td>
     5571</tr>
     5572
     5573
     5574
     5575<tr>
     5576     <td valign="top">DOI</td>
     5577     <td valign="top">10.1016/j.bjp.2013.12.023</td>
     5578</tr>
     5579
     5580
     5581
     5582<tr>
     5583     <td valign="top">URL</td>
     5584     <td valign="top"><a href="http://dx.doi.org/10.1016/j.bjp.2013.12.023">http://dx.doi.org/10.1016/j.bjp.2013.12.023</a></td>
     5585</tr>
     5586
     5587
     5588</li>
     5589
     5590</table></div><br><br>
     5591
     5592
     5593
     5594
    51545595<a class="EntryGoto" id="Scoglio, Caterina M. and Sydney, Ali and Youssef, Mina and Schumm, Phillip and Kooij, Robert E."></a>
    51555596<b class="myheading" style="position: relative; left: 5%;">Scoglio, Caterina M. and Sydney, Ali and Youssef, Mina and Schumm, Phillip and Kooij, Robert E.</b>
     
    59286369
    59296370
     6371<a class="EntryGoto" id="Su&#x6e;&#x0303;&#x65;&#x0301;, M. and Bergesio, L. and Woesner, H. and Rothe, T. and K\\opsel, A. and Colle, D. and Puype, B. and Simeonidou, D. and Nejabati, R. and Channegowda, M. and Kind, M. and Dietz, T. and Autenrieth, A. and Kotronis, V. and Salvadori, E. and Salsano, S. and K\\orner, M. and Sharma, S."></a>
     6372<b class="myheading" style="position: relative; left: 5%;">Su&#x6e;&#x0303;&#x65;&#x0301;, M. and Bergesio, L. and Woesner, H. and Rothe, T. and K\\opsel, A. and Colle, D. and Puype, B. and Simeonidou, D. and Nejabati, R. and Channegowda, M. and Kind, M. and Dietz, T. and Autenrieth, A. and Kotronis, V. and Salvadori, E. and Salsano, S. and K\\orner, M. and Sharma, S.</b>
     6373
     6374<div class="BibEntry">
     6375
     6376<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     6377
     6378<li>
     6379
     6380
     6381<tr>
     6382     <td valign="top">Author</td>
     6383     <td valign="top">Su&#x6e;&#x0303;&#x65;&#x0301;, M. and Bergesio, L. and Woesner, H. and Rothe, T. and K\\opsel, A. and Colle, D. and Puype, B. and Simeonidou, D. and Nejabati, R. and Channegowda, M. and Kind, M. and Dietz, T. and Autenrieth, A. and Kotronis, V. and Salvadori, E. and Salsano, S. and K\\orner, M. and Sharma, S.</td>
     6384</tr>
     6385
     6386<tr>
     6387     <td valign="top">Title</td>
     6388     <td valign="top">Design and implementation of the OFELIA FP7 facility: The European OpenFlow testbed</td>
     6389</tr>
     6390
     6391<tr>
     6392     <td valign="top">Journal</td>
     6393     <td valign="top">Computer Networks</td>
     6394</tr>
     6395
     6396<tr>
     6397     <td valign="top">Year</td>
     6398     <td valign="top">2014</td>
     6399</tr>
     6400
     6401<tr>
     6402     <td valign="top">Abstract</td>
     6403     <td valign="top">The growth of the Internet in terms of number of devices, the number of networks associated to each device and the mobility of devices and users makes the operation and management of the Internet network infrastructure a very complex challenge. In order to address this challenge, innovative solutions and ideas must be tested and evaluated in real network environments and not only based on simulations or laboratory setups. OFELIA is an European FP7 project and its main objective is to address the aforementioned challenge by building and operating a multi-layer, multi-technology and geographically distributed Future Internet testbed facility, where the network itself is precisely controlled and programmed by the experimenter using the emerging OpenFlow technology. This paper reports on the work done during the first half of the project, the lessons learned as well as the key advantages of the OFELIA facility for developing and testing new networking ideas. An overview on the challenges that have been faced on the design and implementation of the testbed facility is described, including the OFELIA Control Framework testbed management software. In addition, early operational experience of the facility since it was opened to the general public, providing five different testbeds or islands, is described.</td>
     6404</tr>
     6405
     6406
     6407
     6408<tr>
     6409     <td valign="top">DOI</td>
     6410     <td valign="top">10.1016/j.bjp.2013.10.015</td>
     6411</tr>
     6412
     6413
     6414
     6415<tr>
     6416     <td valign="top">URL</td>
     6417     <td valign="top"><a href="http://dx.doi.org/10.1016/j.bjp.2013.10.015">http://dx.doi.org/10.1016/j.bjp.2013.10.015</a></td>
     6418</tr>
     6419
     6420
     6421</li>
     6422
     6423</table></div><br><br>
     6424
     6425
     6426
     6427
    59306428<a class="EntryGoto" id="Sydney, A. and Nutaro, J. and Scoglio, C. and Gruenbacher, D. and Schulz, N."></a>
    59316429<b class="myheading" style="position: relative; left: 5%;">Sydney, A. and Nutaro, J. and Scoglio, C. and Gruenbacher, D. and Schulz, N.</b>
     
    60226520
    60236521
     6522<a class="EntryGoto" id="Sydney, Ali and Ochs, David S. and Scoglio, Caterina and Gruenbacher, Don and Miller, Ruth"></a>
     6523<b class="myheading" style="position: relative; left: 5%;">Sydney, Ali and Ochs, David S. and Scoglio, Caterina and Gruenbacher, Don and Miller, Ruth</b>
     6524
     6525<div class="BibEntry">
     6526
     6527<table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;">
     6528
     6529<li>
     6530
     6531
     6532<tr>
     6533     <td valign="top">Author</td>
     6534     <td valign="top">Sydney, Ali and Ochs, David S. and Scoglio, Caterina and Gruenbacher, Don and Miller, Ruth</td>
     6535</tr>
     6536
     6537<tr>
     6538     <td valign="top">Title</td>
     6539     <td valign="top">Using GENI for experimental evaluation of Software Defined Networking in smart grids</td>
     6540</tr>
     6541
     6542<tr>
     6543     <td valign="top">Journal</td>
     6544     <td valign="top">Computer Networks</td>
     6545</tr>
     6546
     6547<tr>
     6548     <td valign="top">Year</td>
     6549     <td valign="top">2014</td>
     6550</tr>
     6551
     6552<tr>
     6553     <td valign="top">Abstract</td>
     6554     <td valign="top">The North American Electric Reliability Corporation (NERC) envisions a smart grid that aggressively explores advance communication network solutions to facilitate real-time monitoring and dynamic control of the bulk electric power system. At the distribution level, the smart grid integrates renewable generation and energy storage mechanisms to improve the reliability of the grid. Furthermore, dynamic pricing and demand management provide customers an avenue to interact with the power system to determine the electricity usage that best satisfies their lifestyle. At the transmission level, efficient communication and a highly automated architecture provide visibility in the power system and as a result, faults are mitigated faster than they can propagate. However, such higher levels of reliability and efficiency rest on the supporting communication infrastructure. To date, utility companies are moving towards Multiprotocol Label Switching (MPLS) because it supports traffic engineering and virtual private networks (VPNs). Furthermore, it provides Quality of Service (QoS) guarantees and fail-over mechanisms in addition to meeting the requirement of non-routability as stipulated by NERC. However, these benefits come at a cost for the infrastructure that supports the full MPLS specification. With this realization and given a two week implementation and deployment window in GENI, we explore the modularity and flexibility provided by the low cost OpenFlow Software Defined Networking (SDN) solution. In particular, we use OpenFlow to provide (1) automatic fail-over mechanisms, (2) a load balancing, and (3) Quality of Service guarantees: all essential mechanisms for smart grid networks.</td>
     6555</tr>
     6556
     6557
     6558
     6559<tr>
     6560     <td valign="top">DOI</td>
     6561     <td valign="top">10.1016/j.bjp.2013.12.021</td>
     6562</tr>
     6563
     6564
     6565
     6566<tr>
     6567     <td valign="top">URL</td>
     6568     <td valign="top"><a href="http://dx.doi.org/10.1016/j.bjp.2013.12.021">http://dx.doi.org/10.1016/j.bjp.2013.12.021</a></td>
     6569</tr>
     6570
     6571
     6572</li>
     6573
     6574</table></div><br><br>
     6575
     6576
     6577
     6578
    60246579<a class="EntryGoto" id="Teerapittayanon, Surat and Fouli, Kerim and M&#x65;&#x0301;dard, Muriel and Montpetit, Marie-Jos&#x65;&#x0301; and Shi, Xiaomeng and Seskar, Ivan and Gosain, Abhimanyu"></a>
    60256580<b class="myheading" style="position: relative; left: 5%;">Teerapittayanon, Surat and Fouli, Kerim and M&#x65;&#x0301;dard, Muriel and Montpetit, Marie-Jos&#x65;&#x0301; and Shi, Xiaomeng and Seskar, Ivan and Gosain, Abhimanyu</b>
     
    74087963<tr>
    74097964     <td valign="top">Abstract</td>
    7410      <td valign="top">Computer networking researchers often have access to a few di
    7411 erent network testbeds (Section 1.2) for their experiments. However, those testbeds are limited in resources; contentions for resources are prominent in those testbeds especially when conference deadline is looming. Moreover, services running on those testbeds are subject to seasonal and daily trac spikes from users all round the world. Hence, demand for resources at the testbeds are high. Some researchers can use other testbeds in conjunction with the ones they are using. Even though each of the testbeds may have di
    7412 erent infrastructures, and characteristics, in the end, what the researchers receive in return is a set of computing resources, either virtual machines or physical machines. Essentially, those testbeds are providing a similar service, but researchers have to manage the credentials for accessing the testbeds manually, and they have to manually request resources from di
    7413 erent testbeds in order to setup experiments that span across di
    7414 erent testbeds. This thesis presents GENICloud, a project that enables the federation of testbeds with clouds. Computing and storage resources can be provisioned to researchers and services running on existing testbeds dynamically from an Eucalyptus cloud. As a part of the GENICloud project, the user proxy (Section 3.4) provides a less arduous method for testbeds administrators to federate with other testbeds; the same serviceiv also manages researchers credentials, so they do not have to acquire resources from each testbed individually. The user proxy provides a single interface for researchers to interact with di
    7415 erent testbeds and clouds and manage their experiments. Furthermore, GENICloud demonstrates that there are, in fact, quite a few architectural similarities between di
    7416 erent testbeds and even clouds</td>
     7965     <td valign="top">Computer networking researchers often have access to a few dierent network testbeds (Section 1.2) for their experiments. However, those testbeds are limited in resources; contentions for resources are prominent in those testbeds especially when conference deadline is looming. Moreover, services running on those testbeds are subject to seasonal and daily trac spikes from users all round the world. Hence, demand for resources at the testbeds are high. Some researchers can use other testbeds in conjunction with the ones they are using. Even though each of the testbeds may have dierent infrastructures, and characteristics, in the end, what the researchers receive in return is a set of computing resources, either virtual machines or physical machines. Essentially, those testbeds are providing a similar service, but researchers have to manage the credentials for accessing the testbeds manually, and they have to manually request resources from dierent testbeds in order to setup experiments that span across dierent testbeds. This thesis presents GENICloud, a project that enables the federation of testbeds with clouds. Computing and storage resources can be provisioned to researchers and services running on existing testbeds dynamically from an Eucalyptus cloud. As a part of the GENICloud project, the user proxy (Section 3.4) provides a less arduous method for testbeds administrators to federate with other testbeds; the same serviceiv also manages researchers credentials, so they do not have to acquire resources from each testbed individually. The user proxy provides a single interface for researchers to interact with dierent testbeds and clouds and manage their experiments. Furthermore, GENICloud demonstrates that there are, in fact, quite a few architectural similarities between dierent testbeds and even clouds</td>
    74177966</tr>
    74187967