See page 7 of the 1.0 spec. 1. If the action includes "set VLAN ID" then in both cases, the packet will have a VLAN header on egress. 2. If the action includes "strip VLAN header" then for B, the packet will not have a VLAN header on egress. For A, it is undefined and would depend on whether the switch requires that the corresponding match indicate that the packet have a VLAN header to match. 3. Otherwise, the packet should egress with the same tag with which it arrived.
For hybrid switches, it depends on your definition hybrid; specifically, how VLAN tag management is negotiated between the OF and non-OF sides of the switch. -Dan On Monday, October 31, 2011 at 2:42 PM, Vitaly Vovnoboy wrote: > Hi Team, > Imagine there is a pure OpenFlow 1.0 switch with one flow of one action - > every packet ingresses on port 1 forward to port 2. > > What is correct payload of port 2 egress packet in following cases: > A) no VLAN is presented in packet coming into port 1 > B) a VLAN header (802.1q tag) is presented in packet coming into port 1 > > Should egress packet (going out from port 2) be 802.1q tagged or untagged in > case A? In case B? > Is it defind by v1.0.0.0 spec? I not found a clear answer in the text. > > Same question about hybrid switch. > > Thanks, > Vitaly Vovnoboy > > _______________________________________________ > openflow-discuss mailing list > [email protected] > (mailto:[email protected]) > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
