I just thought we should Cc kvm list to make sure everyone sees this announcement, and has a chance to give us feedback. If there are other lists we should Cc pls feel free to forward. ----- Forwarded message from Paul Knight <paul.knight@xxxxxxxxxxxxxx> ----- Date: Tue, 24 Dec 2013 14:14:55 -0500 From: Paul Knight <paul.knight@xxxxxxxxxxxxxx> To: members@xxxxxxxxxxxxxxxxxxxx, virtio@xxxxxxxxxxxxxxxxxxxx, tc-announce@xxxxxxxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, freebsd-virtualization@xxxxxxxxxxx, qemu-devel@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx Subject: [virtio] 30-day Public Review for Virtual I/O Device (VIRTIO) Version 1.0 Message-ID: <CADgeAH8DZdjxmniEKcWbX1U9nh8x5RtHF96jdUGRf2uWz77sLQ@xxxxxxxxxxxxxx> Season's greetings all: The OASIS Virtual I/O Device (VIRTIO) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted this specification for 30-day (*) public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 01 / Public Review Draft 01 03 December 2013 Specification Overview: This document describes the specifications of the "virtio" family of devices. These devices are found in virtual environments, yet by design they are not all that different from physical devices, and this document treats them as such. This 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. This is the first public review draft, after months of hard work by the VIRTIO Technical Committee. TC Description: The goal of the OASIS Virtual I/O Device (VIRTIO) TC is to simplify virtual devices, making them more extensible and more recognizable. The purpose of VIRTIO is to ensure that virtual environments and guests have a straightforward, efficient, standard, and extensible mechanism for virtual devices, rather than boutique per-environment or per-OS mechanisms. Public Review Period: (*) The TC has requested an extended Public Review period due to the holiday season. The public review starts 00:00 GMT 25 December 2013 and ends 23:59 GMT 31 January 2014. This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work. URIs: The prose specification document and related files are available here: PDF (Authoritative): http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/virtio-v1.0-csprd01.pdf HTML: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/virtio-v1.0-csprd01.html Editable TeX Source: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/tex/ For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/virtio-v1.0-csprd01.zip Additional information about the specification and the OASIS Virtual I/O Device (VIRTIO) TC can be found at the TC's public home page: https://www.oasis-open.org/committees/virtio/ Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button labeled "Send A Comment" at the top of the TC public home, or directly at: 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 of "Virtual I/O Device (VIRTIO) Version 1.0", we call your attention to the OASIS IPR Policy [2] applicable especially [3] 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 references: [1] OASIS Virtual I/O Device (VIRTIO) TC https://www.oasis-open.org/committees/virtio/ [2] http://www.oasis-open.org/who/intellectualproperty.php [3] http://www.oasis-open.org/committees/virtio/ipr.php https://www.oasis-open.org/policies-guidelines/ipr#s10.3 Non-Assertion IPR Mode Best regards, Paul -- Paul Knight - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst ----- End forwarded message ----- -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
