Should the TC accept changes listed in the description to resolve issue 162,
for inclusion in specification version(s) "virtio-v1.3-cs01", and future versions of the specification?
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 #162: virtio-net: define the VIRTIO_NET_F_CTRL_RX_EXTRA feature bit
--------------------------------------
The VIRTIO_NET_F_CTRL_RX_EXTRA feature bit is mentioned in the spec
since version 1.0, but it's not properly defined.
This patch defines the feature bit and defines the dependency on VIRTIO_NET_F_CTRL_VQ.
Since this dependency is missing in previous versions, we add it now as
a "SHOULD".
https://lists.oasis-open.org/archives/virtio-comment/202302/msg00508.html
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202302/msg00508.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.
--------------------------------------
|