Should the TC accept changes listed in the description to resolve issue VIRTIO-163,
for inclusion in specification version(s) "virtio 1.1 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:
VIRTIO-163: ccw: Be more precise about the semantic of revision 1
--------------------------------------
Revision 1 of the CCW transport is currently defined as virtio 1.0. This
could become confusing when we bump the version of the virtio
specification to 1.1, in a sense that it could be interpreted like one
can not use any features not part of the 1.0 specification.
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio/201802/msg00038.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio 1.1 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.
--------------------------------------
|