Cathy Zhou writes: > additional headers in the payload *transparent to" the driver. For those > drivers which can support VLAN tag insertion/removal though, the extra 4 > bytes cannot be used for other additional headers but VLAN tags, they should > only announce their margin to be 0. > > That means in order to support VLANs over such driver, we'd need another > approach to indicate its VLAN tag insertion/removal capability. But the > difference between "the margin capable" and "the VLAN tag insertion/removal > capaple devices" should be made, because the way they handle the extra VLAN > tag is different.
I agree with that path. If we need to support this sort of hardware (a bit of a weird design center, if you ask me), it should be a separate explicit capability and not just treated as partly-crippled margin support. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
