Hi Alberto, Robert, I'm really excited to LISP used as an SDN enabler!!
A few initial comments: On 02/18/2014 12:15 PM, Alberto Rodriguez-Natal wrote: > Hi Robert, > > > On Tue, Feb 18, 2014 at 4:14 AM, Robert Raszuk <[email protected] > <mailto:[email protected]>> wrote: > [...] > But I must ask why limit yourself to 5 or 7 tuples if another > standards body (at least one claims to be the SDO) > > already > long time > ago defined 39 tuples to be SDN primitives or building blocks. > Is there something among those > > > 39 tuples xTRs can't do ? I guess not as both could be same boxes > from same ODM vendor :) > > > You are right here. More fields beyond just the addresses, protocol and > ports can be taken into account. For now, we are focusing on these only, > but we expect to cover more in the future (thus, the n-tuple notation on > the draft). I think covering more fields is a good idea. > > Besides, please note that we may won't cover the same types that OF > covers. We don't want to compete with OF, but rather to complement it. I don't think you would be competing with OF by specifying the same match types as the ONF does, you would be using (implementing?) OpenFlow, and that would lead to less fragmentation and more code reuse. > It's about using the right tool for the job. OF is (generally speaking) > focused on L2, while LISP is (generally speaking) focused on L3. That's > why the 5-tuple makes more sense for LISP as a flow identifier than, > let's say, ETH or ARP fields. Hope I had brought some light here ;) Well, OpenFlow is slowly adding support for L3 only flows, and LISP is slowly adding support for L2 encaps. Even if you're initially focusing on a few match fields, the design should accommodate a variable number of fields, and the specification of field prerequisites (e.g., if you're matching on a TCP port number, you should have an IPv4 or IPv6 packet). As Robert, I would really like OpenFlow compatible match support. -Lori _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
