Changes between Version 18 and Version 19 of Internal/OpenFlow/Controllers/MultiCtl


Ignore:
Timestamp:
Sep 26, 2012, 8:50:10 PM (12 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/OpenFlow/Controllers/MultiCtl

    v18 v19  
    1414 [#w4 week4][[BR]]
    1515 [#w5 week5][[BR]]
     16 [#w6 week6][[BR]]
     17 [#w7 week7][[BR]]
     18 [#w8 week8][[BR]]
    1619
    1720== Overview. == #i
     
    159162However, it appears that all three channels use similar-enough channel pipelines, whose only differences lie in which handler is being used; therefore some work to be done in the future include a consolidation of the three !PipelineFactories. 
    160163
     164[[BR]]
    161165End of week3 :[#iv Back to Logs.]
     166==== (9/26) ==== #w4
     167Things seem to be headed towards architectural experimentation.
     168 
     169Three things to investigate:
     170 1. '''''Radio Resource Management (RRM)''''' : incorporate advertisements somehow, for between controllers
     171 1. '''''Authentication''''' : A entity that allows/denies a host to tx/rx on a network. This combined with forwarding elements provide a base foundation for collaborative multi-controller networks.
     172 1. '''''Discovery''''' : Controllers discover and establish links with, other controllers within the control plane, sans explicit configuration, like DHCP.   
     173
     174The first two are test cases to add credibility to a architecture like this one. In any case, the syntax for service/capabilities adverts must be defined. 
     175
    162176----
    163177[#home Home.]