On Thu, Oct 15, 2009 at 9:14 AM, James Kempf <james.kempf at ericsson.com> wrote: > Hi Rob, > > I guess FlowVisor could rewrite the OpenFlow protocol coming from the virtualized controllers to insert LAN QoS, right? That would enforce isolation for Enterprise GENI. Exactly, although the QoS mechanism that we're proposing are not necessarily limited to the LAN. If you're interested, I would be happy to chat with you (or others) about the current proposals to extend OpenFlow to include QoS support. Also, in addition to bandwidth, there are other (maybe less obvious) network resources that need to be isolated, e.g., forwarding table entries, switch/router CPU, and who controls the traffic-- what we call "flowspace". > I was mainly thinking about the WAN case. My understanding from a discussion in the PlanetLab GENI meeting in Seattle is that the plan was to use IP overlays between Enterprise GENI networks. IP tunnels between eGENI islands are definitely one direction we're pursuing. That said, we're also trying to deploy eGENI on backbone research networks like Internet2. So, the idea is: if there is a consistent policy across eGENI islands and the islands are directly connected (i.e., Stanford peers with Internet2) then it should be possible to have a consistent virtual "slice" across both LAN and WAN. We're actively trying to set up a demonstration of this and I'm hoping that we will be able to show some of it at GEC6. - Rob .
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.