Title Resolve Issue #62: add vendor specific cfg type
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 #62: add vendor specific cfg type
--------------------------------------
    Vendors might want to add their own capability in the PCI capability
    list. However, Virtio already uses the vendor specific capability ID
    (0x09) for its own purposes.
    
    Provide a structure for vendor specific extensions.
    
https://lists.oasis-open.org/archives/virtio-comment/201910/msg00036.html
--------------------------------------

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

The TC agrees to include the above change(s) in specification version(s) "virtio-v1.2-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 Sun, Nov 24 2019 7:30 am EST
Closing Date Sun, Dec 1 2019 7:30 am EST
Ballot has closed.

Referenced Items

Name Type Date Actions

03450: Resolve Issue #62: add vendor specific cfg type

Document (Archive)

2019-12-01