Hi, (2014/02/19 16:37), FUJITA Tomonori wrote: >> "The Pop PBB header action does not remove the backbone VLAN >> header (B-TAG)" as described in openflow spec 1.3.3. >> The format of I-TAG TCI is pcp,..,I-SID,C-DA,C-SA as in >> 802.1Q-2011 Figure 9-3. > > Thanks a lot! As you pointed out, the action should not remove B-TAG. > > I have a question about the expected packet (I'm not familiar with > this area). The format of the packet (ether/t-tag/s-tag/c-tag/...) is > valid (used in the real world)? -snip-
I have not played with PBB capable real switch, but my understanding is that any tagged packets are OK as far as it is a valid frame and switches just does not forward unsupported frames. 802.1Q spec illustrates a provider bridge "service", and a set of properties that a PBB capable switch is expected to have, and outline of the operations with those equipments. There're four types of interface defined in clause 25.2, Port based, S-tagged, I-tagged and Transparent. B-DA,B-SA,I-TAG,EtherType,Data frame on an I-tagged trunk interface would be the shortest case (see Figure 25-6). -snip- > I thought that it might be better to fix the 'ingress' packet format? > Another potentially fix might be pop_vlan before pop_pbb but currently > the action testes verify one action in general. With the following > patch, Trema and CPqD pass this test). -snip- Agreed. ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
