Then they overlap. If the field is not present it means the flow accepts any value for that field.
Think backwards. Two flow entries do not overlap is if there is at least one bit for which one flow entry matches on 0 and the other matches on 1. From: Emma Anderson [mailto:em.anderso...@yahoo.com] Sent: Tuesday, September 23, 2014 6:39 PM To: Zoltán Lajos Kis; openflow-discuss@lists.stanford.edu Subject: Re: [openflow-discuss] Conflicting flow Zoltan What happens if one of flow entries has a match filed that is not present in the other? Does that mean flows do not overlap? On Tuesday, 23 September 2014, 14:19, Zoltán Lajos Kis <zoltan.lajos....@ericsson.com<mailto:zoltan.lajos....@ericsson.com>> wrote: Hi, If by “conflicting flows” you mean “overlapping flows”, then you can go with something like: Two flow entries overlap if they have the same priority and for every match field which is present in both flow entries it is true for every bit that either its mask is set to zero in at least one flow entry, or its value is the same in both flow entries. BR, Zoltan From: openflow-discuss [mailto:openflow-discuss-boun...@lists.stanford.edu] On Behalf Of Emma Anderson Sent: Tuesday, September 23, 2014 3:36 PM To: openflow-discuss@lists.stanford.edu Subject: [openflow-discuss] Conflicting flow Hi all, How "conflicting flows" in OpenFlow manual can be exactly defined based on match fields?
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
