Ah-ha. I probably should have gotten that. Again, this sort of depends on exactly what you're trying to do. If you're trying to do something like send individual packets from a single TCP connection through different paths, doing this at a fine granularity depends on being able to make forwarding decisions based on probability or something like a hashed packet header, and these are not features supported by OpenFlow. So in cases like that, no, this is not possible strictly with OpenFlow 1.0 (it might be possible if you could, say, match on arbitrary bits in the TCP sequence number).
-- Murphy On Jul 12, 2012, at 6:45 PM, Qingyun Zuo wrote: > Oh, maybe I didn't address clearly. What I mean is that multicast and > multipath unicast is different. Multicast duplicates date on multiple ports, > however, multipath unicast uses multiple path to send but don't duplicate > data. > What I want to do is to implement multipath unicast, So I don't know whether > OpenFlow 1.0 can support it. > Thank you ! > > 2012/7/13 Murphy McCauley <[email protected]> > I think this really depends on what you mean by multipath and what you're > trying to accomplish. Certainly you could duplicate data on node or edge > disjoint paths using OpenFlow 1.0 by simply having one or multiple switches > use multiple output actions and installing disjoint paths on the rest of the > switches... > > -- Murphy > > > On Jul 12, 2012, at 5:17 PM, Qingyun Zuo wrote: > >> Hi, >> Thank you for yor kindly reply. >> I know that OpenFlow 1.1 spec add group type which support multipath or >> multicast. >> However, OpenFlow 1.0 is in the most switches and environment. It is >> easy to implent multicast in OpenFlow 1.0, but how could I implement >> multipath using flow table entries in OpenFlow 1.0? >> >> >> 2012/7/13 Murphy McCauley <[email protected]> >> If you add multiple output actions, it simply means that the packet is >> duplicated. >> >> You could rewrite the address to be a multicast address, and you can create >> flow table entries that act on multicast addresses, but there's no "built >> in" support for multicast in the OpenFlow 1.0 spec. Of course, a switch may >> have its own multicast behavior outside of OpenFlow, but that's up to the >> switch. >> >> Hope that helps. >> >> -- Murphy >> >> On Jul 12, 2012, at 1:08 AM, Qingyun Zuo wrote: >> >>> Hi, >>> Does OpenFlow switch support multipath unicast? or multicast? >>> When I edit a flow entry, I add two egress ports to the ACTION, is it >>> multicast? >>> >>> -- >>> Best Regards >>> Zuo Qingyun >>> >> >> >> >> >> -- >> Best Regards >> Zuo Qingyun >> > > > > > -- > Best Regards > Zuo Qingyun >
