Ballot Details: Resolve Issue #75: virtio-net: Speed and Duplex documentation mistakes (CLOSED)

Ballot Question Should the TC accept changes listed in the description to resolve issue 75, for inclusion in specification version(s) "virtio-v1.2-cs01", and future versions of the specification?
Ballot 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 #75: virtio-net: Speed and Duplex documentation mistakes
--------------------------------------
The spec says that the duplex field has the value 0x00 for full duplex and 0x01 for half duplex, however the current implementations in QEMU and the virtio Linux driver use the values the other way around. DUPLEX_FULL is defined as 1 and DUPLEX_HALF is defined as 0. These values are put into the field if the corresponding config value (duplex=full/half) is found.

Also, when describing the possible values of the speed config field, the maximum value and the value for unknown speed are listed as "0x7ffffffff" and "0xfffffffff" respectively. They both have an extraneous "f" nibble, as they wouldn't fit into a 32-bit field this way.

Proposal ("[PATCH] virtio-net: fix speed, duplex") can be found at:
https://lists.oasis-open.org/archives/virtio-comment/202009/msg00000.html
--------------------------------------

The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202009/msg00000.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
VOTING CLOSED: Tuesday, 7 September 2021 @ 4:45 pm EDT
Yes 6 100
No 0 0
Abstain 1
Open Date Tuesday, 31 August 2021 @ 4:45 pm EDT
Close Date Tuesday, 7 September 2021 @ 4:45 pm EDT
Ballot Type Official, as defined by organization policies and procedures

Voting Statistics

Number of votes cast (excluding abstentions) 6
Eligible members who have voted 7 of 8 87.5%
Eligible members who have not voted 1 of 8 12.5%

Voting Summary by Option

Options with highest number of votes are bold
Option # Votes % of Total
Yes 6 100%
No 0 0%
Abstain 1

Voting Details

Voter Name Company Vote * Time (UTC) Comments
* Carabas, Mihai Oracle Yes 2021-09-01 18:45:00
* Hajnoczi, Stefan Red Hat Yes 2021-09-02 14:53:00
* Kiszka, Jan Siemens AG Yes 2021-09-06 07:14:00
* Moell, Matti OpenSynergy GmbH Yes 2021-09-01 09:18:00
* Pasic, Halil IBM Yes 2021-09-02 09:02:00
* Tsirkin, Michael S. Red Hat Yes 2021-09-01 02:30:00
* Granata, Enrico Google Inc. Abstain 2021-08-31 21:09:00
* Huck, Cornelia Red Hat --