From: Paul Knight <paul.knight@oasis-open.org>
To: project-announce@lists.oasis-open.org,
members@lists.oasis-open.org, virtio@lists.oasis-open.org,
virtio-comment@lists.oasis-open.org
Subject: Invitation to comment on Virtual I/O Device (VIRTIO) Version 1.2 - ends June 8th
Date: Mon, 9 May 2022 14:45:39 -0400 [thread overview]
Message-ID: <CADgeAH9Vk7akPBA5srW9D8bB=W=jTeb1Zg0AnnZTi76nZNo+Kg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4133 bytes --]
OASIS members and other interested parties,
OASIS and the OASIS Virtual I/O Device (VIRTIO) TC are pleased to announce
that Virtual I/O Device (VIRTIO) Version 1.2 is now available for public
review and comment.
Specification Overview:
This document describes the specifications of the 'virtio' family of
devices. These devices are found in virtual environments, yet by design
they look like physical devices to the guest within the virtual machine -
and this document treats them as such. This similarity allows the guest to
use standard drivers and discovery mechanisms. The purpose of virtio and
this specification is that virtual environments and guests should have a
straightforward, efficient, standard and extensible mechanism for virtual
devices, rather than boutique per-environment or per-OS mechanisms.
The documents and related files are available here:
Virtual I/O Device (VIRTIO) Version 1.2
Committee Specification Draft 01
09 May 2022
Editable source (Authoritative):
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/tex/
HTML:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01.html
PDF:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01.pdf
Example driver listing:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/listings/
PDF file marked to indicate changes from Version 1.1 Committee
Specification 01:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01-diff-from-v1.1-cs01.pdf
For your convenience, OASIS provides a complete package of the
specification document and any related files in ZIP distribution files. You
can download the ZIP file at:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01.zip
A public review metadata record documenting this and any previous public
reviews is available at:
https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01-public-review-metadata.html
How to Provide Feedback
OASIS and the OASIS Virtual I/O Device (VIRTIO) TC value your feedback. We
solicit input from developers, users and others, whether OASIS members or
not, for the sake of improving the interoperability and quality of its
technical work.
The public review starts 10 May 2022 at 00:00 UTC and ends 08 June 2022 at
23:59 UTC.
Comments may be submitted to the TC by any person through the use of the
OASIS TC Comment Facility which can be used by following the instructions
on the TC's "Send A Comment" page (
https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=virtio).
Comments submitted by TC non-members for this work and for other work of
this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/virtio-comment/
All comments submitted to OASIS are subject to the OASIS Feedback License,
which ensures that the feedback you provide carries the same obligations at
least as the obligations of the TC members. In connection with this public
review, we call your attention to the OASIS IPR Policy [1] applicable
especially [2] to the work of this technical committee. All members of the
TC should be familiar with this document, which may create obligations
regarding the disclosure and availability of a member's patent, copyright,
trademark and license rights that read on an approved OASIS specification.
OASIS invites any persons who know of any such claims to disclose these if
they may be essential to the implementation of the above specification, so
that notice of them may be posted to the notice page for this TC's work.
Additional information about the specification and the VIRTIO TC can be
found at the TC's public home page:
https://www.oasis-open.org/committees/virtio/
========== Additional references:
[1] https://www.oasis-open.org/policies-guidelines/ipr
[2] https://github.com/oasis-tcs/virtio-admin/blob/master/IPR.md
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode
--
Paul Knight <paul.knight@oasis-open.org>....Document Process Analyst
<https://www.oasis-open.org/people/staff/paul-knight>
OASIS <https://www.oasis-open.org/> - Setting the standard for open
collaboration
[-- Attachment #2: Type: text/html, Size: 6108 bytes --]
reply other threads:[~2022-05-11 7:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADgeAH9Vk7akPBA5srW9D8bB=W=jTeb1Zg0AnnZTi76nZNo+Kg@mail.gmail.com' \
--to=paul.knight@oasis-open.org \
--cc=members@lists.oasis-open.org \
--cc=project-announce@lists.oasis-open.org \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).