Title Resolve Issue #16: rework notifications terminology
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 #16: rework notifications terminology
--------------------------------------
The terminology around notifications is currently somewhat fragmented. Unify notifications terminology using available and used buffer notification consistently for the virtqueue notifications. Consistent use of the term configuration change notification is of concern.
--------------------------------------

The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio/201806/msg00032.html
--------------------------------------

The TC agrees to include the above change(s) in specification version(s) "virtio-v1.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.

--------------------------------------
Ballot Options Ballot has closed
[ ] Yes
[ ] No
[ ] Abstain
Opening Date Fri, Jul 27 2018 7:45 am EDT
Closing Date Fri, Aug 3 2018 7:45 am EDT
Ballot has closed.

Referenced Items

Name Type Date Actions

03228: Resolve Issue #16: rework notifications terminology

Document (Archive)

2018-08-03