Hello, On Mon, 7 Jul 2014 08:35:28 +0200 (CEST) Szymon Mentel <[email protected]> wrote:
> I'm a developer of an OpenFlow switch LINC [1]. Recently I've came across an > issue from one of our users on VLAN_VID match field [2]. He suggests that > LINC behaves incorrectly while not setting the 13th bit in the value of the > match field that is sent in a packet_in message to the controller. In that > case LINC would have to set the value to 0x1**** (where **** is the VLAN ID) > when a VLAN tag is matched. > > On the other hand, I believe that LINC is compliant with the spec. If a > switch sends packet_in with a match on VLAN it's obvious that the VLAN tag > was indeed present in the packet and this information doesn't have to be > carried in an additional bit. If the VLAN is not present the match field for > VLAN is simply omitted in the packet_in. > > What is your opinion on this topic? I guess that match should have 0x1**** in a PacketIn message because a PacketIn message is supposed to include a match that a controller sent. A controller is supposed to send a FlowMod with a match field with 0x1****. IIRC, OVS works in such way. ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
