Description
Please vote Yes if you agree with all of the following. If you disagree, please vote No. If you don't have an opinion, please vote Abstain. I move that: The TC agrees to resolve the following specification issue: Issue #147: should clarify VLAN tagging requirement with or without VIRTIO_NET_F_CTRL_VLAN -------------------------------------- The software virtio implementation in QEMU differentiates VLAN tagging disposition subject to the presence of VIRTIO_NET_F_CTRL_VLAN feature: - when VIRTIO_NET_F_CTRL_VLAN is negotiated, the device starts with all VLANs filtered (meaning only untagged traffic can be received, and traffic with VLAN tag will be dropped). - when VIRTIO_NET_F_CTRL_VLAN is not negotiated, all traffic including untagged and tagged can be received. It is essential to capture this expectation in the spec. Otherwise live migraiton between different virtio implemenations won't work, either from software to vDPA, or cross different vDPA vendors. See the discussion thread in: https://lists.oasis-open.org/archives/virtio-dev/202301/msg00231.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/202301/msg00231.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-cs01", and future versions of the specification. -------------------------------------- Reminder: A Voting Member must be active in a TC to maintain voting rights. As the Virtio TC has adopted a standing rule to conduct business only by electronic ballot, without Meetings, a Voting Member who fails to cast a ballot in two consecutive Work Product Ballots loses his or her voting rights at the close of the second ballot missed. --------------------------------------
