|
Should the TC accept changes listed in the description to resolve issue VIRTIO-152,
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-152: exposing host MTU to guest
--------------------------------------
It is helpful for a host to indicate its MTU value to the guest.
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
http://marc.info/?i=1474307357-13816-1-git-send-email-aconole@redhat.com
Subject: [PATCH v12] virtio-net: add Max MTU configuration field
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio 1.1 cs01", and future versions of the
specification.
Note: should this proposal be accepted and approved, one or more
claims disclosed to the TC admin and listed on the Virtio TC
IPR page https://www.oasis-open.org/committees/virtio/ipr.php
might become Essential Claims.
--------------------------------------
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.
--------------------------------------
|
