|
Should the TC accept changes listed in the description to resolve issue 142,
for inclusion in specification version(s) "virtio-v1.3-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:
Issue #142: virtio-vsock: add VIRTIO_VSOCK_F_NO_IMPLIED_STREAM feature bit
--------------------------------------
Initially virtio-vsock only supported the stream type, which is why
there was no feature. Later we added the seqpacket type and in the future
we may have other types (e.g. datagram).
seqpacket is an extension of stream, so it might be implied that if
seqpacket is supported, stream is too, but this might not be true for
other types.
As we discussed [here](http://markmail.org/message/2s3qd74drgjxkvte) should be better to add a new
VIRTIO_VSOCK_F_NO_IMPLIED_STREAM feature bit to avoid this implication.
Let's also add normative sections to better define the behavior when
VIRTIO_VSOCK_F_NO_IMPLIED_STREAM is negotiated or not.
Latest patch sent:
https://lists.oasis-open.org/archives/virtio-comment/202207/msg00034.html
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202207/msg00034.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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.
--------------------------------------
|
