Changes between Version 1 and Version 2 of GEC16Agenda/WiMAX-Developers


Ignore:
Timestamp:
03/05/13 11:03:29 (9 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC16Agenda/WiMAX-Developers

    v1 v2  
     1
    12[[PageOutline]]
    23
    3 = WiMAX Developers' Meeting =
     4= WiMAX Developers Meeting at GEC-16 =
    45
    56== Schedule ==
    67
    7 Tuesday, 3:30pm - 5pm
    8 
    9 == Session Leaders ==
    10 
    11 Harry Mussman,  GENI Project Office.
    12 
    13 
    14 == Agenda / Details ==
    15 
     8Tuesday, October 24, 3pm - 5pm [[BR]]
     9Room:  TBD [[BR]]
     10Session leader:  Harry Mussman (GENI Project Office, Raytheon BBN Technologies) [[BR]]
    1611
    1712== Pre-Requisites ==
    1813
    1914None
     15
     16== Description ==
     17
     18First, this session will review Spiral 5 goals for GENI WiMAX campus deployments and experiments.  [[BR]]
     19
     20Next, it will review the status of GENI WiMAX campus deployments and extensions, plus plans for local experiments.  [[BR]] 
     21
     22Finally, review several WiMAX deployment tasks and issues.  [[BR]]
     23
     24
     25
     26== Agenda ==
     27This is a tentative agenda, which may change. [[BR]]
     28
     29NOTE:  We have many topics to cover in a short time.  PLEASE bring only the designated number of slides, and provide a link to additional information.  THANKS!  [[BR]]
     30
     31== 1)  Introductions ==
     323:00pm  [[BR]]
     33
     34== 2)  Goals and Extensions ==
     353:05pm   [[BR]]
     36
     37=== 2.1)  Spiral 5 Goals ===
     383:05pm [[BR]]
     39Harry Mussman (GPO) [[BR]]
     40
     41a)  Where necessary, complete deployments planned for Spiral 4:  [[BR]]
     42 Get experimental frequency from the FCC, that does not interfere with Clearwire services  [[BR]]
     43 Install Airspan base station(s), with local NetSpan management system  [[BR]]
     44 Optional when multiple cells:  backhaul control and data traffic to central equipment site  [[BR]]
     45 Add OMF/OML structures, including LoginService [[BR]]
     46 Connect via switch to I2 backbone, via OF switches if there [[BR]]
     47 WiFi access point for dual-homing operating on custom PC node  [[BR]]
     48 Vehicular mobile station operating on custom PC node    [[BR]]
     49 Fixed “mobile station” for remote experimenters operating on custom PC node   [[BR]]
     50
     51b)  Plan local research experiments for Spiral 5  [[BR]]
     52 Focus on goals, configurations, steps  [[BR]]
     53 Identify necessary extended site capabilities needed in Spiral 5  [[BR]]
     54
     55c)  Complete deployments of necessary extended site capabilities needed in Spiral 5, from this list of options:  (technology supplier or coordinator shown)  [[BR]]
     56 Additional base station  (Rutgers WINLAB)  [[BR]]
     57 Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
     58 Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     59 Connection to I2  (coordinated by BBN) [[BR]]
     60 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     61 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     62 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     63 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     64 WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     65 Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     66 Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     67 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     68
     69d)  Support unified GENI operations:  [[BR]]
     70 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     71 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     72 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     73
     74e)  Complete and support experiments:  [[BR]]
     75 Local research experiments [[BR]]
     76 Experiments by remote experimenters, including those at tutorials  [[BR]]
     77 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     78 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     79
     80f)  Concern: how can we get all of this done? [[BR]]
     81 Common platforms and services  [[BR]]
     82 Clear plans, good schedules  [[BR]]
     83 Close cooperation!!  [[BR]]
     84 
     85
     86
     87=== 2.2)  Options for Introducing LTE Equipment ===
     88GEC14 discussion:  [[BR]]
     89 Moderator:  Harry Mussman  (GPO)  [[BR]]
     90 Ray Raychaudhuri  (WINLAB)  [[BR]]
     91 Ivan Seskar  (WINLAB)  [[BR]]
     92 Patrick Gossman (Wayne State) [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/WiMAXPlanning/The%20Case%20for%20LTE.pptx  The Case for LTE]  [[BR]]
     93 Gregg Tome (Airspan)  [[BR]]
     94
     95Discussion group formed: [[BR]]
     96 Moderator:  Suman Banerjee  (Wisconsin) [[BR]]
     97 Ray Raychaudhuri  (WINLAB)  [[BR]]
     98 Ivan Seskar  (WINLAB)  [[BR]]
     99 Patrick Gossman (Wayne State) [[BR]]
     100 Bryan Lyles (NSF)  [[BR]]
     101 Jacobus (Kobus) Van der Merwe (Utah)  (new)   [[BR]]
     102 Tod Sizer (Bell Labs/Alcatel-Lucent)  (new)   [[BR]]
     103 Walt Magnusen (Texas A&M)  (new)  [[BR]]
     104 Harry Mussman  (GPO)  [[BR]]
     105
     106What are our goals?   [[BR]]
     107
     108How do we match available:  base station equipment, on-air frequencies and mobile stations? [[BR]]
     109
     110[http://niviuk.free.fr/lte_band.php  LTE frequency bands (from Ivan)] [[BR]]
     111
     112Gregg Tome:  Airspan has equipment that operates at 2.6GHz (but this is outside of EBS band) [[BR]]
     113
     114Tod Sizer:  Have used commercial small cells operating at low power, borrowed commercial spectrum, and commercial devices, in a lab setting. [[BR]]
     115
     116Ivan and Tod:  There is available open-source back-end software (Fraunhoffer?) [[BR]]
     117
     118Walt:  Has equipment to test for LTE in public safety, from General Dynamics/IPWireless  [[BR]]
     119
     120What are next steps?   [[BR]]
     121 *  Tod to talk with Ray and Ivan [[BR]]
     122 *  Suman to organize calls/meetings   [[BR]]
     123
     124
     125=== 2.3)  Lab Experiments to Teach Wireless Basics ===
     1263:10pm  [[BR]]
     127Thanasis Korakis  (NYU Poly)  [[BR]]
     128
     129 Funded project (1/13 - 12/13) to define lab experiments for students to teach wireless basics  [[BR]]
     130 To be executed on GENI wireless sites, using both WiMAX and WiFi  [[BR]]
     131 Overview and status [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/NYUPolyWirelessLab.pptx slides] [[BR]]
     132
     133What are next steps?   [[BR]]
     134 *  Early versions of lab experiments to be provided by GEC16 [[BR]]
     135
     136
     137=== 2.4)  Multiple Site Experiment:  Mobility First ===
     138GEC14 presentation:  [[BR]]
     139Kiran Nagaraja (WINLAB)  [[BR]]
     140
     141[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/MF-GEC12-PlenaryDemo-10-3-2011.pdf  slides] [[BR]]
     142
     143Overview of current Mobility First multiple-site experiment. [[BR]]
     144
     145What additions are needed?  [[BR]]
     1461)  Add WiFi AP to each site.  [[BR]]
     1472)  L2 path from MS to core  [[BR]]
     148
     149Experiment done without human intervention, by using x2 MAC addresses, and emulating packet loss to fake mobility.  [[BR]]
     150Consider these as possible sites by GEC13:  WINLAB;  BBN;  NYU Poly;  UCLA;  Colorado.  [[BR]]
     151
     152=== 2.5)  Access to Commercial Broadband Services via MVNO Arrangements ===
     153
     154
     155
     156== 3)  GENI WiMAX site deployment status and local experiment plans ==
     1573:15pm  [[BR]]
     158
     159Each site will indicate:  [[BR]]
     160
     161a)  Status of deployments planned for Spiral 4:  [[BR]]
     162
     163b)  Plan for local research experiments in Spiral 5:  [[BR]]
     164
     165c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:  [[BR]]
     166
     167d)  Support for unified GENI operations:  [[BR]]
     168
     169e)  Support for experiments:  [[BR]]
     170
     171
     172=== 3.1)  BBN Site Extension Plan ===
     1733:15pm  [[BR]]
     174Manu Gosain (GPO)  [[BR]]
     175
     176GEC14 status:  [[BR]]
     177 [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/BBNStatus%200710wimaxmeeting14gec.ppt slide]  [[BR]]
     178
     179GEC15 status:  [[BR]]
     180a)  Status of deployments planned for Spiral 4:  [[BR]]
     181 Get experimental frequency from the FCC, that does not interfere with Clearwire services   (yes, new frequency) [[BR]]
     182 Install Airspan base station(s), with local NetSpan management system   (yes) [[BR]]
     183 Add OMF/OML structures, including LoginService  (yes)  [[BR]]
     184 Connect via switch to I2 backbone, via OF switches if there  (yes) [[BR]]
     185 WiFi access point for dual-homing operating on custom PC node  (partial)  [[BR]]
     186 Fixed “mobile station” for remote experimenters operating on custom PC node (yes)  [[BR]]
     187
     188b)  Plan for local research experiments in Spiral 5:   [[BR]]
     189 Repeat throughput and range, comparing NEC and Airspan [[BR]]
     190
     191c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
     192 Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
     193 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     194 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     195 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     196 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     197 WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     198 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     199
     200d)  Support for unified GENI operations:  [[BR]]
     201 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     202 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     203 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     204
     205e)  Support for experiments:  [[BR]]
     206 Local research experiments [[BR]]
     207 Experiments by remote experimenters, including those at tutorials  [[BR]]
     208 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     209 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     210
     211
     212
     213=== 3.2)  WINLAB/Rutgers University Site Extension Plan ===
     2143:20pm  [[BR]]
     215Ivan Seskar (WINLAB) [[BR]]
     216
     217GEC14 status: [[BR]]
     218 * Status  [[BR]]
     219  * Bringing Airspan on Busch campus  [[BR]]
     220  * Continuing remote access to BSs [[BR]]
     221  * Connected to I2 backbone network [[BR]]
     222
     223 * Local and remote experiments [[BR]]
     224
     225GEC15 status:  [[BR]]
     226 * WINLAB site:  [[BR]]
     227  1)  NEC base station, with fixed mobile station [[BR]]
     228  2)  Sandbox:  NEC base station, connected via programmable RF attenuator to fixed mobile station [[BR]]
     229
     230 * Busch campus site:  [[BR]]
     231  3)  Airspan base station, for use by students on campus [[BR]]
     232
     233a)  Status of deployments planned for Spiral 4:  [[BR]]
     234 Install Airspan base station(s), with local NetSpan management system  (yes) [[BR]]
     235 Optional when multiple cells:  backhaul control and data traffic to central equipment site (yes) [[BR]]
     236 Add OMF/OML structures, including LoginService  (yes) [[BR]]
     237 Connect via switch to I2 backbone, via OF switches if there  (yes) [[BR]]
     238 WiFi access point for dual-homing operating on custom PC node   (yes)  [[BR]]
     239 Vehicular mobile station operating on custom PC node  (yes)  [[BR]]
     240 Fixed “mobile station” for remote experimenters operating on custom PC node  (yes)  [[BR]]
     241
     242b)  Plan for local research experiments in Spiral 5:   [[BR]]
     243 What is new?  [[BR]]
     244
     245c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
     246 Additional base station  (Rutgers WINLAB)  [[BR]]
     247 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     248 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     249 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     250 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     251 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     252
     253d)  Support for unified GENI operations:  [[BR]]
     254 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     255 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     256 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     257
     258e)  Support for experiments:  [[BR]]
     259 Local research experiments [[BR]]
     260 Experiments by remote experimenters, including those at tutorials  [[BR]]
     261 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     262 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     263
     264
     265
     266=== 3.3)  UCLA Site Extension Plans ===
     2673:25pm  [[BR]]
     268Giovanni Pau, Mario Gerla (UCLA) [[BR]]
     269
     270GEC14 status:  [[BR]]
     271 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/ucla%20%20%202012-July-10-GEC.pptx  slides]   [[BR]]
     272
     273 * Extension plan  [[BR]]
     274  * Add x1 Airspan BS near UCLA dormitories;  possibly other BSs.  [[BR]] 
     275  * x1  (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
     276
     277 * License [[BR]]
     278  * Renewed Experimental License [[BR]]
     279  * Coordination with Clearwire Started [[BR]]
     280
     281 
     282GEC15 status:
     283 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/2012-July-10-GEC%20UCLA%20GEC15.pptx  slides]  [[BR]]
     284
     285 * Airspan Installation [[BR]]
     286  * Location selected:  top of Spraul Hall;  pole installed [[BR]]
     287  * On hold for poweer, network connections  [[BR]]
     288  * Temporary:  in use in lab for WiMAX RF AggMgr software testing  [[BR]]
     289
     290 * Connection to Mesoscale Infrastructure   [[BR]]
     291  * Completed [[BR]]
     292
     293a)  Status of deployments planned for Spiral 4:  [[BR]]
     294 Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes) [[BR]]
     295 Install Airspan base station(s), with local NetSpan management system  (pending, partial) [[BR]]
     296 Optional when multiple cells:  backhaul control and data traffic to central equipment site (pending)  [[BR]]
     297 Add OMF/OML structures, including LoginService  (yes) [[BR]]
     298 Connect via switch to I2 backbone, via OF switches if there   (yes) [[BR]]
     299 WiFi access point for dual-homing operating on custom PC node  (?) [[BR]]
     300 Vehicular mobile station operating on custom PC node  (?)  [[BR]]
     301 Fixed “mobile station” for remote experimenters operating on custom PC node (yes)  [[BR]]
     302
     303b)  Plan for local research experiments in Spiral 5:   [[BR]]
     304 Coverage and performance, with Teltonica and NEC, also Airspan  [[BR]]
     305 Mobile experiments with permanent vehicular nodes  [[BR]]
     306 NDN experiments over WiMAX
     307
     308c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
     309 Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
     310 Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     311 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     312 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     313 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     314 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     315 WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     316 Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     317 Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     318 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     319
     320d)  Support for unified GENI operations:  [[BR]]
     321 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     322 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     323 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     324
     325e)  Support for experiments:  [[BR]]
     326 Local research experiments [[BR]]
     327 Experiments by remote experimenters, including those at tutorials  [[BR]]
     328 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     329 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     330
     331What are next steps?   [[BR]]
     332 * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
     333 * Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput  (due 12/15/12) [[BR]]
     334 * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
     335
     336
     337=== 3.4)  Clemson University Site Deployment Plan ===
     3383:30pm  [[BR]]
     339K-C Wang, Reece Johnson (Clemson)
     340
     341GEC13 plans:  [[BR]]
     342[http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/WiMAXPlanning/GEC13-WiMAX-Clemson.pdf Clemson slides][[BR]]
     343
     344GEC14 status:  [[BR]]
     345 * Status:  [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/GEC14-WiMAX-Clemson.ppt slides]  [[BR]] 
     346
     347 * Extension plan   [[BR]]
     348  * Add x1 Airspan BS near campus [[BR]]
     349  * Add x2 Airspan BS near Greenville;  connect via DOT fibers.  [[BR]]
     350  * Want handover near I85/I385 intersection.  [[BR]]
     351  * x3 (2510 Lo:  2496 to 2570 MHz)  [[BR]]
     352
     353GEC15 status:  [[BR]]
     354 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/GEC15-WiMAX-clemson.ppt slides]  [[BR]]
     355
     356
     357 * Clemson campus location:
     358  * Installed, on-the-air:  signal strength measurements completed
     359
     360 * Greenville locations:
     361  * Installed, with power and fiber connections
     362  * Both report "RF failure";  Netspan and/or base station issue
     363
     364a)  Status of deployments planned for Spiral 4:  [[BR]]
     365 Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes)  [[BR]]
     366 Install Airspan base station(s), with local NetSpan management system  (partial: 3 installed, 1 of 3 on-the-air) [[BR]]
     367 Optional when multiple cells:  backhaul control and data traffic to central equipment site  (yes) [[BR]]
     368 Add OMF/OML structures, including LoginService  (pending) [[BR]]
     369 Connect via switch to I2 backbone, via OF switches if there (?) [[BR]]
     370 WiFi access point for dual-homing operating on custom PC node (use campus network?) [[BR]]
     371 Vehicular mobile station operating on custom PC node  (pending)  [[BR]]
     372 Fixed “mobile station” for remote experimenters operating on custom PC node (no)  [[BR]]
     373
     374b)  Plan for local research experiments in Spiral 5:   [[BR]]
     375 Working with Wisconsin handover project  [[BR]]
     376 Focus on "uniform solution for handover in heterogeneous networks, e.g., WiFi off-loading  [[BR]]
     377
     378c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
     379 Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
     380 Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     381 Connection to I2  (coordinated by BBN) [[BR]]
     382 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     383 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     384 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     385 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     386 WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     387 Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     388 Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     389 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     390
     391d)  Support for unified GENI operations:  [[BR]]
     392 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     393 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     394 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     395
     396e)  Support for experiments:  [[BR]]
     397 Local research experiments [[BR]]
     398 Experiments by remote experimenters, including those at tutorials  [[BR]]
     399 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     400 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     401
     402What are next steps?   [[BR]]
     403 * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
     404 * Complete installation of Airspan base stations, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput  (due 12/15/12) [[BR]]
     405 * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
     406 
     407=== 3.5)  University of Wisconsin Site Extension Plan ===
     4083:35pm  [[BR]]
     409Suman Banerjee, Derek Meyer (Wisconsin)  [[BR]]
     410
     411GEC14 status:  [[BR]]
     412 * Status [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/2012_07_09_Geni_Conference.ppt  slides]  [[BR]]
     413
     414 * Extension plan  [[BR]]
     415  * Add Airspan to building/tower near Capitol.  [[BR]]
     416  * Connect via Madison unified fiber project  [[BR]]
     417  * Outside contributions for power and poles.  [[BR]]
     418  * x1 (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
     419
     420
     421GEC15 status:  [[BR]]
     422 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf  slides]  [[BR]]
     423
     424
     425 * Airspan status [[BR]]
     426  * Planned installation blocked by site issues [[BR]]
     427  * Instead, will move quickly to install on CS building (where Cisco base station was installed) [[BR]]
     428
     429a)  Status of deployments planned for Spiral 4:  [[BR]]
     430 Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes)  [[BR]]
     431 Install Airspan base station(s), with local NetSpan management system  (no;  restarting) [[BR]]
     432 Optional when multiple cells:  backhaul control and data traffic to central equipment site  (?) [[BR]]
     433 Add OMF/OML structures, including LoginService  (partial) [[BR]]
     434 Connect via switch to I2 backbone, via OF switches if there (?) [[BR]]
     435 WiFi access point for dual-homing operating on custom PC node  (no)  [[BR]]
     436 Vehicular mobile station operating on custom PC node  (no)  [[BR]]
     437 Fixed “mobile station” for remote experimenters operating on custom PC node  (no) [[BR]]
     438
     439b)  Plan for local research experiments in Spiral 5:   [[BR]]
     440 Focus on mobility experiments from bus  [[BR]]
     441 Planning multi-site video experiment with NYU Poly  [[BR]]
     442 Begin classroom use in Spring 2013  [[BR]]
     443
     444c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
     445 Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
     446 Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     447 Connection to I2  (coordinated by BBN) [[BR]]
     448 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     449 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     450 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     451 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     452 WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB) (or use local service?) [[BR]]
     453 Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     454 Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     455 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     456
     457d)  Support for unified GENI operations:  [[BR]]
     458 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     459 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     460 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     461
     462e)  Support for experiments:  [[BR]]
     463 Local research experiments [[BR]]
     464 Experiments by remote experimenters, including those at tutorials  [[BR]]
     465 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     466 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     467
     468What are next steps?   [[BR]]
     469 * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
     470 * Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput  (due 12/15/12) [[BR]]
     471 * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
     472
     473=== 3.6)  University of Michigan Site Deployment Plan ===
     4743:40pm [[BR]]
     475Morley Mao  (Michigan)  [[BR]]
     476
     477GEC13 plans:
     478 * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/WiMAXPlanning/WIMAXexperimentMichigan.pdf  slides]  [[BR]]
     479
     480GEC14 status:  [[BR]]
     481 * Extension plan  [[BR]]
     482  * Add one Airspan on top of building  [[BR]]
     483  * Will signals penetrate into buildings?  [[BR]]
     484  * One frequency from Clearwire  [[BR]]
     485  * x1 (2510 Lo:  2496 to 2570 MHz)  [[BR]]
     486  * Location and backhaul [[BR]]
     487  * Mobility and handover [[BR]]
     488
     489GEC15 status:[[BR]]
     490 * Base station installed, local Netspan ready, but waiting for power  [[BR]]
     491 * I2 connection pending  [[BR]]
     492
     493a)  Status of deployments planned for Spiral 4:  [[BR]]
     494 Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes) [[BR]]
     495 Install Airspan base station(s), with local NetSpan management system  (pending) [[BR]]
     496 Add OMF/OML structures, including LoginService  (no) [[BR]]
     497 Connect via switch to I2 backbone, via OF switches if there   (pending) [[BR]]
     498 WiFi access point for dual-homing operating on custom PC node (no) [[BR]]
     499 Fixed “mobile station” for remote experimenters operating on custom PC node (no)  [[BR]]
     500
     501b)  Plan for local research experiments in Spiral 5:   [[BR]]
     502 Content delivery service [[BR]]
     503
     504c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
     505 Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
     506 Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     507 Connection to I2  (coordinated by BBN) [[BR]]
     508 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     509 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     510 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     511 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     512 WiFi access point for dual-homing operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     513 Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     514 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     515
     516d)  Support for unified GENI operations:  [[BR]]
     517 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     518 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     519 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     520
     521e)  Support for experiments:  [[BR]]
     522 Local research experiments [[BR]]
     523 Experiments by remote experimenters, including those at tutorials  [[BR]]
     524 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     525 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     526
     527What are next steps?   [[BR]]
     528 * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
     529 * Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput  (due 12/15/12) [[BR]]
     530 * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
     531
     532
     533=== 3.7)  Wayne State University Site Deployment Plan ===
     5343:45m   [[BR]]
     535Hongwei Zhang, Yu Chu (Wayne State)  [[BR]]
     536
     537GEC14 status:
     538 * Status [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/WayneWiMAX-deployment-planAndStatus-GEC14.pdf  slides]  [[BR]]
     539
     540 * Extension plan  [[BR]]
     541  * Plan: one site with three sectors, and 3 Airspan base stations. [[BR]] 
     542  * One frequency (10MHz) from Clearwire  [[BR]] 
     543  * x3 (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
     544
     545 * Spectrum loan from Clearwire: done [[BR]]
     546  * 10MHz band: 2591MHz – 2601MHz (belongs to 2510 Mid band of 2560MHz~2630MHz) [[BR]] 
     547  * Current loan valid until March 1, 2013; to be renewed annually afterwards [[BR]] 
     548
     549GEC15 status:  [[BR]]
     550 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/WayneWiMAX-deployment-planAndStatus-GEC15-final.pdf  slides]  [[BR]]
     551
     552 * Airspan base stations: [[BR]]
     553  * 2 installed on 17th floor, and on the air;  CINR measured [[BR]]
     554
     555
     556a)  Status of deployments planned for Spiral 4:  [[BR]]
     557 Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes)  [[BR]]
     558 Install Airspan base station(s), with local NetSpan management system  (yes, 2 of 3) [[BR]]
     559 Optional when multiple cells:  backhaul control and data traffic to central equipment site (yes, to equipment room) [[BR]]
     560 Add OMF/OML structures, including LoginService (no) [[BR]]
     561 Connect via switch to I2 backbone, via OF switches if there  (pending) [[BR]]
     562 Vehicular mobile station operating on custom PC node  (no)  [[BR]]
     563 Fixed “mobile station” for remote experimenters operating on custom PC node (no)  [[BR]]
     564
     565b)  Plan for local research experiments in Spiral 5:   [[BR]]
     566 Enable handoff between different base stations/sectors [[BR]]
     567 Develop measurement services  [[BR]]
     568 Measurement campaign: spatiotemporal behavior in static & mobile scenarios: smart grid and smart transportation [[BR]]
     569 ns-3 integration [[BR]]
     570 GENI-fy OpenXC vehicular sensing and infotainment platform [[BR]]
     571 Refine OpenXC, virtualization, etc [[BR]]
     572 Integrate with OMF, measurement tools [[BR]]
     573 Integrate with v2V & V2I platforms (i.e., SDR) as well as vehicle sensing and control apps [[BR]]
     574
     575c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
     576 Additional base station   (pending) (Rutgers WINLAB)  [[BR]]
     577 Custom PC nodes  ("yellow nodes")  (Rutgers WINLAB)  [[BR]]
     578 Login Service plus OMF/OML services operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     579 Connection to I2  (coordinated by BBN) [[BR]]
     580 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     581 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     582 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     583 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     584 Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     585 Fixed “mobile station” for remote experimenters operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     586 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     587
     588d)  Support for unified GENI operations:  [[BR]]
     589 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     590 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     591 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     592
     593e)  Support for experiments:  [[BR]]
     594 Local research experiments [[BR]]
     595 Experiments by remote experimenters, including those at tutorials  [[BR]]
     596 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     597 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     598
     599What are next steps?   [[BR]]
     600 * Establish a plan for all of your Spiral 5 tasks, and document  (due 12/1/12)  [[BR]]
     601 * Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput  (due 12/15/12) [[BR]]
     602 * Complete connection to I2 backbone, and demonstrate a service with another site(s)  (due 1/15/12)  [[BR]]
     603
     604
     605=== 3.8) NYU Poly Site Update ===
     6063:50pm   [[BR]]
     607Thanasis Korakis, Fraida Fund (NYU-Poly)[[BR]]
     608
     609GEC14 status:  [[BR]]
     610 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/GEC14-WiMAX-NYUPoly.pdf  slides] [[BR]]
     611
     612 * Operational OMF/OML installation[[BR]]
     613 * Connected to I2 backbone network[[BR]]
     614 * Testbed open to experimenters since GEC12[[BR]]
     615
     616GEC15 status:  [[BR]]
     617
     618 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/NYUPolyGEC15.pdf slides] [[BR]]
     619
     620 * Airspan base station isntallation still pending.
     621 * Working closely with UMass Amherst on use of GIMI tools with WiMAX
     622 * Supporting experimenters, including students and tutorials
     623
     624a)  Status of deployments planned for Spiral 4:  [[BR]]
     625 Get experimental frequency from the FCC, that does not interfere with Clearwire services  (yes)  [[BR]]
     626 Install Airspan base station(s), with local NetSpan management system  (pending) [[BR]]
     627 Optional when multiple cells:  backhaul control and data traffic to central equipment site  (?) [[BR]]
     628 Add OMF/OML structures, including LoginService  (yes)  [[BR]]
     629 Connect via switch to I2 backbone, via OF switches if there  (yes) [[BR]]
     630 WiFi access point for dual-homing operating on custom PC node  (yes) [[BR]]
     631 Vehicular mobile station operating on custom PC node  (?)  [[BR]]
     632 Fixed “mobile station” for remote experimenters operating on custom PC node (yes)  [[BR]]
     633
     634b)  Plan for local research experiments in Spiral 5:   [[BR]]
     635 Many experiments formulated for students, and tutorials, including: [[BR]]
     636  StreamLoad [[BR]]
     637  NetCheck [[BR]]
     638  AFFIX [[BR]]
     639 Working on set of lab experiments to teach wireless principals  [[BR]]
     640
     641c)  Plan to complete deployments of extended site capabilities needed in Spiral 5:   [[BR]]
     642 GIMI I&M services (UMass Amherst/NYU Poly)  [[BR]]
     643 Multiple base-station management service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     644 Data-path gateway service operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     645 Mobility/handover/multi-homing service  (coordinated by Wisconsin/Clemson)   [[BR]]
     646 Vehicular mobile station operating on custom PC node  (Rutgers WINLAB)  [[BR]]
     647 Unlocked Android WiMAX/WiFi handsets.   (Wisconsin)  [[BR]]
     648
     649d)  Support for unified GENI operations:  [[BR]]
     650 Forward site monitoring information to the central monitoring server  (Rutgers WINLAB)  [[BR]]
     651 Cooperate with Rutgers WINLAB and Clearwire to avoid interference with Clearwire’s services [[BR]]
     652 When necessary, do an “emergency stop” of your transmissions.  [[BR]]
     653
     654e)  Support for experiments:  [[BR]]
     655 Local research experiments [[BR]]
     656 Experiments by remote experimenters, including those at tutorials  [[BR]]
     657 Classroom instruction experiments by students   (NYU Poly)  [[BR]]
     658 Multi-site experiments, e.g., MobilityFirst  (Rutgers WINLAB) [[BR]]
     659
     660What are next steps?   [[BR]]
     661 * Complete installation of Airspan base station, use early release of WiMAX RF AggMgr with local OMF/OML to configure, check over-the-air throughput  (due 12/15/12) [[BR]]
     662
     663
     664=== 3.9) UMass Amherst Site Update ===
     6653:55pm   [[BR]]
     666Mike Zink, Cong Wang (UMass Amherst)  [[BR]]
     667
     668GEC14 status:
     669 * Add OMF/OML:  have installed  [[BR]]
     670 * Connect to I2 backbone network:  plan to do soon  [[BR]]
     671
     672 * Planned experiments:  use to integrate GIMI tools [[BR]]
     673
     674GEC15 status:  BR]]
     675 No report  [[BR]]
     676
     677=== 3.xx)  Temple University Site Deployment Plan ===
     678Shan Lin, Jie Wu (Temple)  [[BR]]
     679
     680GEC14 status:  [[BR]]
     681 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/geni-meeting-temple-july2012.pptx slides]  [[BR]]
     682
     683 * Extension plan  [[BR]]
     684  * x1 (or x2?) Airspan base stations (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
     685  * Two frequencies from Clearwire, shared with Drexel  [[BR]]
     686  * Location and backhaul [[BR]]
     687  * Mobility and handover [[BR]]
     688
     689 * License application approved by Clear [[BR]] 
     690  * License is valid until Jan 31, 2013 [[BR]] 
     691  * Frequencies: 2585-2595 & 2603-2613 MHz [[BR]] 
     692  * Clearwire holds the right to terminate operation with 30 days prior notice [[BR]] 
     693
     694 * Wimax base station purchased and arrived [[BR]] 
     695  * One Air4G-MacroMAXe 2510M Air4G-W24-2510MT [[BR]] 
     696  * Installation contract placed  [[BR]] 
     697  * Latitude & Longitude: (39.98038, -75.15703) [[BR]] 
     698  * Height: 12th floor (131 ft)  [[BR]]   
     699
     700 * Experiments (with the existing TU-WiMax) [[BR]] 
     701  * Observe highly irregular ranges (longest range>2.29mile) [[BR]] 
     702  * High bandwidth (>700kbps) only very close to the base station (<0.5mile) [[BR]] 
     703  * Significant shadowing among buildings [[BR]] 
     704
     705
     706GEC15 status:  BR]]
     707 * No report  [[BR]]
     708 
     709=== 3.xx)  Drexel University Site Deployment Plan ===
     710Kevin Wanuga, Jeff Wildman, Kapil Dandekar (Drexel)  [[BR]]
     711
     712GEC13 plans:  [[BR]]
     713 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/GEC13%20%20drexel%20%20GENI.ppt slides] [[BR]]
     714
     715GEC14 status:  [[BR]]
     716 * Extension plan  [[BR]]
     717  * x1 (or x2?) Airspan base stations (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
     718  * Two frequencies from Clearwire, shared with Temple  [[BR]]
     719  * Location and backhaul [[BR]]
     720  * Mobility and handover [[BR]]
     721
     722 * Kevin Wanuga reports: [[BR]]
     723  * Planning for top of 18-story building;  3m radiation safety clearance [[BR]]
     724  * More urban than Temple [[BR]]
     725  * Airspan order placed;  not yet received [[BR]]
     726  * Kiva networks to install base station [[BR]]
     727  * Contract engineer mast;  recommendation from Giovanni:  check masts at GNE supply [[BR]]
     728  * Questions about power cable; recommendation from Harry:  call us, and we can explain parameters [[BR]]
     729
     730
     731GEC15 status:  BR]]
     732 * No report  [[BR]]
     733
     734
     735
     736=== 3.xx) Univ of Colorado at Boulder Site Update ===
     737Dirk Grunwald (Colorado)  [[BR]]
     738
     739
     740GEC15 status:  BR]]
     741 * No report  [[BR]]
     742
     743=== 3.xx) Columbia University Site Update ===
     744Henning Schulzrinne, Jan Janak (Columbia)  [[BR]]
     745
     746
     747GEC15 status:  BR]]
     748 * No report  [[BR]]
     749
     750== 4)  GENI WiMAX Deployment Tasks and Issues ==
     7514:00pm  [[BR]]
     752
     753
     754=== 4.1)  Co-exist with Clearwire ===
     7554:00pm  [[BR]]
     756Manu Gosain  (GPO) and Ivan Seskar (WINLAB)
     757
     758 * Current approach, as an alternative to an agreement that leases Clearwire spectrum to GENI sites:  [[BR]]
     759  * Operate under an experimental license from the FCC;  otherwise require contract between site and Clearwire, with $ and conditions   [[BR]]
     760  * Agreement between Rutgers WINLAB and Clearwire, on enhanced cooperation  [[BR]]
     761  * Maintain accurate DB of site information and contacts at Rutgers, and share with Clearwire  [[BR]]
     762  * Responsive local contact, at each site  [[BR]]
     763  * Centralized monitoring server at Rutgers WINLAB  [[BR]]
     764  * Ability to quickly turn off site transmitter, if interference suspected  [[BR]]
     765  * Possible extension:  remote emergency stop, with access to GMOC  [[BR]]
     766
     767
     768 * [http://wimax.orbit-lab.org/wiki/WiMAX/00/01#a1.3GENICampusDeployments  GENI WiMAX Site Information]  [[BR]]
     769
     770 * [http://oml.orbit-lab.org:4040/tab/home_tab  GENI WiMAX Site Dashboard]  [[BR]]
     771
     772What are next steps?   [[BR]]
     773 *  Review information on site information and site dashboard pages, and finalize [[BR]]
     774 *  Establish process to add site information, then maintain and track   [[BR]]
     775 *  Establish email list for operations issues  [[BR]]
     776 *  Provide operations interface to GMOC and Clearwire   [[BR]]
     777 *  Complete agreement with Clearwire [[BR]]
     778 *  Encourage all GENI sites to obtain experimental licenses [[BR]]
     779 *  Include WiMAX into GENI emergency stop process  [[BR]]
     780 *  Consider adding a WiMAX "emergency stop" button, for use by the GMOC  [[BR]]
     781
     782=== 4.2)  New services:  Multiple Base-Station Mgmt Srvc and  Data-Path GW Srvc ===
     7834:10pm  [[br]]
     784Ivan Seskar  (Rutgers WINLAB) and Davide Pesavento (UCLA)  [[BR]]
     785
     786 * Multiple Base-Station Mgmt Srvc:  [[BR]]
     787
     788 * 1)  Have updated WiMAX RF AggMgr for NEC base station to 2.5.3+;  additional updates coming  [[BR]]
     789  * Feeds management data to centralized DB at WINLAB, for GENI-wide monitoring  [[BR]]
     790  * Due:  ?  [[BR]]
     791
     792 *  2)  New WiMAX RF AggMgr for Airspan base station  [[BR]]
     793  * Provides configuration, to replace Netspan;  now running  [[BR]]
     794  * Provides node authorization, and measurements per client  [[BR]]
     795  * First version due:  12/15/12 [[BR]]
     796  * Could BBN, NYU Poly begin testing early version, to replace Netspan?    [[BR]]
     797  * Could early version be shipped to sites on yellow node, with OMF/OML?   [[BR]]
     798
     799 *  3)  Build WiMAX RF AggMgr that can control multiple BSs, either NEC and/or Airspan, with same API  [[BR]]
     800  * Should be useful for handover/multi-homing functions:  shared white list of MS, allowed to connect to one BS or another  [[BR]]
     801  * What other features are needed?  [[BR]]
     802  * First version due:  3/15/13  [[BR]]
     803
     804 * Data-path GW Srvc:  [[BR]]
     805  * Bridges each base station to global datapath  [[BR]]
     806  * Includes CLICK router (two types) [[BR]]
     807  * Includes OpenV switch  (open-source OF) [[BR]]
     808  * Should be useful for handover/multi-homing functions [[BR]]
     809  * First version due:  3/15/13  [[BR]]
     810  * Could there be an earlier version, that provides basic functions, and be manually configured? 
     811  * Could BBN, NYU Poly begin testing early version?    [[BR]]
     812  * Could early version be shipped to sites on yellow node?   [[BR]]
     813 
     814What are next steps?   [[BR]]
     815 * Finalize features for WiMAX RF AggMgr releases  (due 11/15/12) [[BR]]
     816 * Establish delivery schedule for WiMAX RF AggMgr releases [[BR]]
     817 * Could there be an earlier version fo WiMAX RF AggMgr, that provides just basic functions, and be manually configured?  released by 11/15/12?  [[BR]]
     818 * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]]
     819 * Finalize features for Data-path GW Srvc releases (due 11/15/12)  [[BR]]
     820 * Establish delivery schedule for Data-path GW Srvc releases [[BR]]
     821 * Establish acceptance test plan by BBN, NYU Poly, for WiMAX RF AggMgr releases [[BR]]
     822
     823=== 4.3)  WiScape Measurement Framework ===
     8244:20pm  [[BR]]
     825Suman Banerjee (Univ Wisc)
     826
     827 * Overview of current functions  [[BR]]
     828  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/mse-banerjee.pdf  slides]  [[BR]]
     829  * A data measurement framework with APIs, that the clients and the measurement server expose  [[BR]]
     830  * Clients (e.g., on an Android device) measure network performance, and then report measurements to the server  [[BR]]
     831  * Measurement include latency, loss, throughput, TCP or UDP  [[BR]]
     832  * Provides feedback to network selection  [[BR]]
     833  * [http://wiscape.wings.cs.wisc.edu/new_wiscape/index.php  link to WiScape]  [[BR]]
     834
     835What are next steps?   [[BR]]
     836 * Work with handover project, to see if WiScape measurement framework can be part of a GENI mobility/handover/multi-homing solution  [[BR]]
     837
     838=== 4.4)  Mobility/handover/multi-homing services  ===
     8394:25pm  [[BR]]
     840Parmesh Ramanathan  (Wisconsin)  [[BR]]
     841
     842 * Projects requiring handover include:  Clemson, Wayne State, Wisconsin and UCLA.    [[BR]]
     843 * Projects that can contribute handover technology include:  Rutgers WINLAB and Wisconsin.  [[BR]]
     844 * Also, commercial handover technology available from Airspan.  (Gregg Tome (Airspan))  [[BR]]
     845
     846 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/WiMAXUpdate/handover_parmesh%20%20GEC15.pptx  slides]  [[BR]]
     847
     848 * Layer 2 handoff
     849  * Minimal:  Mobile node breaks its connection with current WiMAX BS and then establishes connection with the new WiMAX BS  [[BR]]
     850  * Better:  Mobile node needs two interfaces, in the simplest form, one interface always connects to BS1 while the other connects to BS2  [[BR]]
     851  * Need: suggested configurations, estimates of required software and level of effort  [[BR]]
     852
     853 * Layer 3 handoff
     854  * Minimal:  Controller node re-routes through new BS after IP address re-write, BUT does not allow initiation of incoming connection
     855  [[BR]]
     856  * Better:  Use open source mobile IP s/w (Transparent Mobile IP [http://sourceforge.net/projects/tmip/ link], and OpenFlow s/w in mobile node to de-encapsulate IP packets  [[BR]]
     857  * Need: suggested configurations, estimates of required software and level of effort  [[BR]]
     858
     859 * Suggested steps:    [[BR]]
     860  1) Yellow mobile nodeode with two interfaces, doing handover between two BS on the same subnet [[BR]]
     861  2) Transparent MobileIP working to implement a baseline Layer 3 handover scheme [[BR]]
     862  3) Support new Layer 3 solutions like Mobility First? [[BR]]
     863  4) Demonstrate heterogeneous network handovers [[BR]]
     864
     865What are next steps?   [[BR]]
     866 * Better define proposed configurations 1) and 2) (due 11/15/12)  [[BR]]
     867 * Review with other interested projects  [[BR]]
     868 * Understand proposed Multiple Base-Station Mgmt Srvc and  Data-Path GW Srvc, and how they could be used in the implementation  [[BR]]
     869 * Understand how Yellow Nodes could be used in the implementation  [[BR]]
     870 * Understand how Android handsets could be used in the implementation  [[BR]]
     871 * Consider potential uses of WiScape Measurement Framework  [[BR]]
     872 * With other projects, define a workplan  (due 12/15/12)  [[BR]]
     873
     874
     875=== 4.5)  Mobility/handover/multi-homing plans ===
     8764:30pm  [[BR]]
     877All  [[BR]]
     878
     879 * What is the best roadmap to useful mobility/handover/multi-homing services based on planned and available platforms and software?  [[BR]]
     880
     881
     882=== 4.6)  Add "yellow nodes" to WiMAX Sites ===
     8834:45pm  [[BR]]
     884Ivan Seskar  (WINLAB) [[BR]]
     885
     886 * These are "yellow nodes", introduced in ORBIT testbed [[BR]]
     887
     888 * Can be used as:   [[BR]]
     889  * General fixed servers  [[BR]]
     890  * Support Multiple Base-Station Mgmt Srvc   [[BR]]
     891  * Support Data-Path GW Srvc  [[BR]]
     892  * Support OMF/OML and Login services  [[BR]]
     893  * Provide WiFi access points  [[BR]]
     894  * Act as fixed "mobile stations"  [[BR]]
     895  * Act as vehicular mobile station (option:  12v power supply)  [[BR]]
     896
     897  * Currently used by:  Rutgers WINLAB;  NYU Poly;  BBN  [[BR]]
     898
     899 * How can these be provided to sites?  [[BR]]
     900  * One design to serve all needs  [[BR]]
     901  * Approximate cost:  $800 - $1500  [[BR]]
     902
     903What are next steps?   [[BR]]
     904  * Working with other projects, refine design to balance functionality and cost, and decide what nodes are needed at which sites   [[BR]]
     905  * Order parts (due 11/15/12)  [[BR]]
     906  * Assemble and deliver to sites  (due 1/15/13)  [[BR]]
     907  * Can a few of the current yellow nodes be delivered to sites right away with OMF/OML and new WiMAX RF AggMgr?  [[BR]]
     908
     909
     910=== 4.7)  Mobile Station using Android Handset ===
     9114:55pm  [[BR]]
     912Derek Meyer (Univ Wisconsin)[[BR]]
     913
     914 * Summary of discussions with Sprint about unlocked HTC Evo handset  [[BR]]
     915  * 3-way NDA was signed  [[BR]]
     916  * Sprint has subcontractor who handles such purchases: contact is ? [[BR]]
     917  * Many handsets in warehouse, such as HTC Evo 4G;  approx $300 per handset[[BR]]
     918  * Must be unlocked by subcontractor, so can register with GENI network;  need to provide config to subcontractor (done by Ivan)[[BR]]
     919  * Must be sure can download Android apps[[BR]]
     920
     921What are next steps?   [[BR]]
     922 * Working with other projects, establish how many handsets are needed at which sites   [[BR]]
     923 * Consider how to provide handsets to projects no longer supported by the GPO  [[BR]]
     924 * Complete negotiation with Sprint subcontractor (WSA Distributing), and order devices  (due 12/1/12) [[BR]]
     925 * Get and check samples?  [[BR]]
     926 * Verify operation, and loading of apps [[BR]]
     927 * Deliver handsets to other projects  (due 1/15/13)  [[BR]]
     928 * Support use by other projects  [[BR]]
     929 * Maintain relationship with WSA Distributing  [[BR]]
     930
     931 
     932
     933== 5) Adjourn ==
     9345:00pm  [[BR]]
     935
     936Please join us for a Wimax BoF dinner. Please indicate on this poll, if you will be attending
     937
     938 http://www.doodle.com/gtz6rdv9b37gg4rc
     939
     940== References ==
     941
     942
     943=== R1  GENI WiMAX Spiral 4 Goals ===
     944Harry Mussman (GPO) [[BR]]
     945
     946a)  Goals for GENI WiMAX site deployments: [[BR]]
     947  Satisfy needs of local research experiments [[BR]]
     948  Support multi-site experiments, e.g., MobilityFirst   [[BR]]
     949  Support remote experimenters [[BR]]
     950
     951  Support multi-site applications? [[BR]]
     952
     953  Are we missing something?  support for instruction? [[BR]]
     954
     955b)  Sol 2 base station deployments: [[BR]]
     956  Update to include OMF/OML structures, including LoginService [[BR]]
     957  Add GENI AM API [[BR]]
     958
     959  Complete, and update to new software that support multiple VLANs, etc. [[BR]]
     960  Connect via switch to I2 backbone, via OF switches if there [[BR]]
     961
     962  Consider how to setup multi-site slice, and include other GENI resources [[BR]]
     963  Consider federated operation [[BR]]
     964  Consider adding WiFi AP to support dual-homed experiments, e.g., MobilityFirst [[BR]]
     965 
     966c)  Sol 3 base station deployments: [[BR]]
     967  Consider 3.6GHz operation? [[BR]]
     968  Study commercial campus deployments, to understand coverage and applications:  U Colorado, Boulder;  Northern Mich U;  UMass Dartmouth [[BR]]
     969  Order Airspan base stations and related items, for delivery 1/2012 [[BR]]
     970  Complete installation within Spiral 4!  (within 1 year) [[BR]]
     971
     972  Decide on how to provide ASN-GW for handover [[BR]]
     973  Consider open-source ASN-GW?  or ASN-GW from Airspan? [[BR]]
     974  How could we use Wisconsin mobility engine? [[BR]]
     975
     976  [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/UoC%20-%20MacroMAXe%20RF%20Plan%20V1.1.pptx  Airspan Deployment Plan for Univ Colorado at Boulder][[BR]]
     977
     978d)  Mobile stations: [[BR]]
     979  Reference MS is Linux netbook, with Intel WIMAX modem card, internal or external [[BR]]
     980  Reference vehicular MS? [[BR]]
     981  Reference handset MS?  Need to be able to unlock Sprint-supported device? [[BR]]
     982
     983e)  Experiment support: [[BR]]
     984  Move to OMF/OML, for better support and for easier sharing [[BR]]
     985  Consider alternate techniques for throughput measurements [[BR]]
     986  Consider how to setup multi-site slice, and include other GENI resources [[BR]]
     987
     988  GIMI project committed to supporting WiMAX sites [[BR]]
     989
     990  How can we make it easy for experimenters? [[BR]]
     991
     992f) Other topics: [[BR]]
     993  Interworking with carriers (Clemson) [[BR]]
     994  Use of carrier resources, i.e., WiNTeB [[BR]]
     995  How could we add LTE?  any match of equipment, frequencies and mobile stations? [[BR]]
     996
     997g)  CONCERN: [[BR]]
     998  Do not have resources to do all of the above!  how do we decide? [[BR]]
     999  What is the best way to support campus projects? [[BR]]
     1000  What is the best way to support experimenters? [[BR]]
     1001
     1002
     1003
     1004=== R2) Overview of GENI WiMAX Sites and Experiments ===
     1005Harry Mussman (GPO) [[BR]]
     1006
     1007Paper including sections on basic and extended WiMAX sites, and on WiMAX research and service experiments:    [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/WiMAXPlanning/020112b_ExtendingGENI_TridentCom2012.pdf  pdf]  [[BR]]
     1008
     1009
     1010=== R3) Airspan Profile-C Base Station, with Associated Hardware and Software ===
     1011Ivan Seskar (WINLAB) and Harry Mussman (GPO) [[BR]]
     1012
     1013 
     1014a)  Choice of Airspan to provide a WiMAX base station for new GENI WiMAX sites [[BR]]
     1015NEC is not able to provide a WiMAX base station for new GENI WiMAX sites [[BR]]
     1016WINLAB and the GPO have decided to purchase base stations from Airspan, a commercial company pursuing target customers such as universities and small carriers. [[BR]]
     1017For example, the Univ of Colorado at Boulder IT Dept has installed an Airspan system with 4 sectors, that covers the campus.  They have been pleased with Airspan. [[BR]]
     1018WINLAB has a frim quote from Airspan for their MacroMAXe profile-C WiMAX base station unit, and related items. [[BR]]
     1019
     1020[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/WiMAX_Brochure_Rev_J3.pdf  Airspan brochure][[BR]]
     1021[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/MacroMAXe%20Product%20Specification%20_Rel%209%200%201_%20Vx%5B1%5D.pdf  MacroMAXe Product Specification]  [[BR]] 
     1022[http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/UoC%20-%20MacroMAXe%20RF%20Plan%20V1.1.pptx  Airspan Deployment Plan for Univ Colorado at Boulder][[BR]]
     1023
     1024b)  Rutgers will provide a kit including: [[BR]]
     1025Airspan MacroMAXe profile-C WiMAX base station unit, for outside mounting[[BR]]
     1026  Choice of frequency:   [[BR]]
     1027  (2510 Lo:  2496MHz to 2570MHz)   [[BR]]
     1028  (2510 Mid:  2560MHz to 2630MHz)  [[BR]]
     1029  (2510 Hi:  2620MHz to 2690MHz)  [[BR]]
     1030  (3650: 3650MHz to 3700MHz)]  [[BR]]
     1031
     1032NOTE:  WINLAB needs to know frequency choices during November (or early December), so that they can place an order with Airspan for delivery late 2011 or early 2012!
     1033
     1034Sector antenna, with x4 RF jumper cables [[BR]]
     10352x4 MIMO, supported by base station and antenna [[BR]]
     1036GPS antenna, with surge suppressor and cable [[BR]]
     1037DC power cable, from base station unit (outside) to testbed (inside) [[BR]]
     1038Network management software license, 1 per base station [[BR]]
     1039
     1040
     1041c)  Campus will need to provide: [[BR]]
     1042Pole for mounting [[BR]]
     1043DC power supply (-48v, approx 300W) [[BR]]
     1044Ethernet cable, from base station unit (outside) to testbed (inside);  consider copper (may be a problem with lightning surge) or fiber (requires MM fiber cable, and fiber interface on switch) [[BR]]
     1045Windows server to host network management software [[BR]]
     1046Linux server to host OMF software [[BR]]
     1047Ethernet switches, and other network equipment, for access (configuration to be provided) [[BR]]       
     1048
     1049d)  Additional kits can be purchased from Airspan [[BR]]
     1050  Price is approximately $15,000. [[BR]]
     1051 
     1052e)  It is expected that additional base stations kits will be purchased for some (or all) Sol 3 GENI sites in Spiral 5. [[BR]]
     1053  Thus, campus site might be able to add additional sectors, at no cost. [[BR]]
     1054  Planning for next year will be done later this year. [[BR]]
     1055  Consider including additional sectors within your technical plan right away.   [[BR]]
     1056
     1057f)  Note:  Airspan indicates that they expect to introduce a new base station unit within the next year. [[BR]]
     1058  Somewhat reduced performance/range. [[BR]]
     1059  Approximately half the cost [[BR]]
     1060
     1061g)  Airspan indicates that their sector antenna provides:[[BR]]
     1062  A 90degree pattern, which is consistent with proper coverage over a 120degree sector.[[BR]]
     1063  Four internal elements, to support 2x4 MIMO.[[BR]]
     1064  Airspan can provide provide x4 omni-directional antennas, but the cost is much higher, and the range is signifcantly reduced.[[BR]]
     1065
     1066h)  Airspan shows that their profile-C base station unit can be configured to operate without an ASN GW and without a RADIUS (authentication) server.[[BR]]
     1067  In this mode, a list of allowed base stations must be configured into the base station, and groups of these base stations are mapped to a VLAN on the ethernet port.[[BR]]
     1068  This appears to be consistent with the current NEC base station unit operated with the ASN GW/WiMAX RF AggMgr code that has been provided by Rutgers/WINLAB[[BR]]
     1069  [http://groups.geni.net/geni/attachment/wiki/GEC12WiMaxDeploymentAndExperimentation/CS%20Network%20Configuration%20Setup%20Guide.pdf  MacroMAXe Configuration Guide][[BR]]
     1070
     1071i)  Airspan shows that if handover operation is desired, an ASN GW must be provided, plus typically an associated RADIUS (authentication) server.[[BR]]
     1072  In this case, the base station unit operates with IP at the interface.  [[BR]]
     1073
     1074
     1075j)  Airspan installation instructions [http://wimax.orbit-lab.org/wiki/WiMAX/01b  link]  [[BR]]
     1076
     1077
     1078
     1079=== R4)  Netspan Network Management System for Airspan Base Station ===
     1080Manu Gosain  (GPO)  [[BR]]
     1081
     1082 * Suggest:  add Netspan system at each site with Airspan base station  [[BR]]
     1083 * Requires:  Windows server [[BR]]
     1084 * Use: setup of Netspan base station to provide basic functions  [[BR]]
     1085
     1086[http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/NetspanMgmtSystem%20%200710wimaxmeeting14gec.ppt slides]  [[BR]]
     1087
     1088[http://wimax.orbit-lab.org/wiki/WiMAX/01b#a3.4NetspanInstallationInstructions   installation instructions]  [[BR]]
     1089
     1090 * Coming: replace with new WiMAX RF AggMgr  [[BR]]
     1091
     1092
     1093
     1094
     1095
     1096=== R5) Add OMF/OML to WiMAX sites ===
     1097Fraida Fund (NYU Poly), Manu Gosain (GPO), Derek Meyer (Wisconsin), [[BR]]
     1098
     1099 * Equip a WiMAX site with full OMF/OML capabilities, installing on VMs  [[BR]]
     1100 * Include Login Service for Remote Users [[BR]]
     1101
     1102 * NYU Poly configuration:  [[BR]]
     1103
     1104 * 1) physical host acting as base station controller, runs the asn-gw and wimaxrf AM. [[BR]]
     1105  * (1) and (2) run Ubuntu, (3) runs Windows.  [[BR]]
     1106  * It has Ethernet connections to the NEC IDU, NYU-Poly network (and Internet), and very soon GENI backbone (campus IS just informed me that they will be testing that tomorrow).  [[BR]]
     1107  * We have firewall rules set up so this host only accepts traffic from host (2) on the wimaxrf AM port. This allows us to make sure that only users with a current reservation can configure the BS. [[BR]]
     1108
     1109 * 2) physical host running OMF 5.3 AM, EC, and some other services that are useful for the testbed. [[BR]]
     1110  * (1) and (2) run Ubuntu, (3) runs Windows.  [[BR]]
     1111  * It has Ethernet connections to NYU-Poly network (internet) and OMF control network.  [[BR]]
     1112  * This is the host that testbed users log on to. We have firewall rules set up on this host so that only users with a current reservation can configure the BS or communicate with the testbed nodes. [[BR]]
     1113
     1114 * 3) physical host that serves our group website and the reservation system for the testbed. It's connected to the NYU-Poly network (and Internet)  [[BR]]
     1115  * (1) and (2) run Ubuntu, (3) runs Windows. [[BR]]
     1116
     1117 * Our testbed nodes are scattered throughout several CS labs and research areas (not part of our group).  [[BR]]
     1118  * They are connected to the pre-existing Ethernet jacks in the walls and floors of those rooms, which all go back to a CS server room, where we patch them through to our own (non-openflow) switch for the control network. [[BR]]
     1119  * We do have an openflow switch that we plan to deploy somewhere at some point. [[BR]]
     1120
     1121
     1122
     1123
     1124 * BBN experience  (need summary)  [[BR]]
     1125
     1126 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/vmsetup_at_uwmadison.pdf Wisconsin configuration] [[BR]]
     1127
     1128 * All services are running on the same physical machine. [[BR]]
     1129  * HP server that came with the base station.  [[BR]]
     1130  * The base OS is Debian and virtual machines using for the services (Virtualbox)  [[BR]]
     1131
     1132 * Physical machine network connections: [[BR]]
     1133  * Eth0 (128.105.22.xxx): University network (internet) [[BR]]
     1134  * Eth1 (10.3.8.126): Network to IDU of base station [[BR]]
     1135  * Eth2 (10.0.0.1): Control network for omf [[BR]]
     1136  * Eth3: Connected to openflow (physically, but not enabled until we can get a vlan tag to GENI backbone) [[BR]]
     1137
     1138 * Base operating system:  Debian [[BR]]
     1139
     1140 * Virtualbox guests: [[BR]]
     1141  * 1.  Ubuntu 9.04 ->  aggmgr 5.2 ->  wimaxrf service [[BR]]
     1142  * Eth0 (128.105.22.xxx):  bridged interface to university network [[BR]]
     1143  * Eth1(10.3.8.254):  bridged interface to base station network [[BR]]
     1144
     1145  * 2.  Ubuntu 10.04 ->  aggmgr 5.3 ->  cmcStub, Frisbee, inventory, pxe, result, saveimage [[BR]]
     1146  * Also expctl, resctl, and xmpp on same machine [[BR]]
     1147  * Eth0 (128.105.22.xxx): bridged interface to university network [[BR]]
     1148  * Eth1 (10.0.0.200): bridged interface to control network [[BR]]
     1149
     1150
     1151
     1152 * Coming:  plan to federate with ProtoGENI cluster  [[BR]]
     1153  *  Reference: [http://www.tridentcom.org/2012/program  TridentCom 2012]  :  "Federating wired and wireless test facilities through Emulab and OMF: the iLab.t use case", Stefan Bouckaert (IBBT - Ghent University)  [[BR]]
     1154  *  BBN is exploring how to utilize this to better integrate WiMAX sites into GENI, and be able to utilize the GENI AM API to assgin resources.  [[BR]]
     1155
     1156
     1157
     1158
     1159=== R6)  Connect WiMAX sites to I2 backbone network, to support multi-site experiments ===
     1160Manu Gosain (GPO), Fraida Fund (NYU Poly), Ivan Seskar (WINLAB)  [[BR]]
     1161
     1162* Connect a WiMAX site to the GENI I2 backbone network  [[BR]]
     1163  * Update WiMAX RF Agg Mgr to map MS groups into VLAN tags [[BR]]
     1164  * Add switch  [[BR]]
     1165  * Connect switch to I2 backbone  [[BR]]
     1166  * VLAN connections from each site to "L2 router" at WINLAB   [[BR]]
     1167
     1168[http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/WiMAXSiteConnectivity%20%200710wimaxmeeting14gec.ppt slide]  [[BR]]
     1169
     1170 * When can other WiMAX sites can be added?  [[BR]]
     1171  * UCLA; has physical connection;  needs to configure;  when?  [[BR]]
     1172  * Wisconsin;  when?  [[BR]]
     1173  * Clemson;  when?  [[BR]]
     1174  * UMass Amherst; has physical connection;  needs to configure;  when?  [[BR]]
     1175
     1176 * How is core network configured to support multi-site experiments?   [[BR]]
     1177
     1178 * How is new Data-path GW Srvc use at site to interface with core network? [[BR]]
     1179
     1180What are next steps?  (Manu Gosain)  [[BR]]
     1181 * Establish planned configuration  (due 11/15/12) [[BR]]
     1182 * Establish plan with schedule to connect all sites  (due 11/15/12) [[BR]]
     1183 * Track connection of sites, and assist them as needed  [[BR]]
     1184
     1185=== R7) GENI WiMAX Experiments, Demos and Tutorials ===
     1186
     1187[http://groups.geni.net/geni/wiki/Experiments  link]  [[BR]]