From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36217) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUDa8-0003HG-Ql for qemu-devel@nongnu.org; Sun, 30 Mar 2014 07:07:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WUDa4-000636-M6 for qemu-devel@nongnu.org; Sun, 30 Mar 2014 07:07:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56483) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUDa4-00062y-DX for qemu-devel@nongnu.org; Sun, 30 Mar 2014 07:07:12 -0400 Date: Sun, 30 Mar 2014 14:07:36 +0300 From: "Michael S. Tsirkin" Message-ID: <20140330110736.GC24476@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] [chet.ensign@oasis-open.org: [members] 15-day Public Review for Virtual I/O Device (VIRTIO) V1.0 - ends 14 April] List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, qemu-devel@nongnu.org ----- Forwarded message from Chet Ensign ---= -- Date: Fri, 28 Mar 2014 17:54:16 -0400 From: Chet Ensign To: tc-announce@lists.oasis-open.org, members@lists.oasis-open.org, virti= o@lists.oasis-open.org, virtio-comment@lists.oasis-open.org Subject: [members] 15-day Public Review for Virtual I/O Device (VIRTIO) V= 1.0 - ends 14 April Message-ID: The OASIS Virtual I/O Device (VIRTIO) TC members [1] have produced an upd= ated Committee Specification Draft (CSD) and submitted this specification for = 15-day public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 02 / Public Review Draft 02 11 March 2014 With the release we are testing a convenience option for submitting comme= nts to the Technical Committee. Please see the details under =E2=80=98Public Rev= iew Period=E2=80=99 below. Specification Overview: This document describes the specifications of the "virtio" family of devi= ces. These devices are found in virtual environments, yet by design they are n= ot all that different from physical devices, and this document treats them as su= ch. 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 pe= r-OS mechanisms. This is the second public review draft, incorporating significant feedbac= k on clarity from the first draft. TC Description:=20 The TC has spent the past two months processing all the feedback for incorporation into the document. We believe the result is a clearer, cris= per draft and welcome further feedback. There are only a small number of chan= ges to the intent of the spec, and these are highlighted at the top of the chang= elog.=20 Public Review Period: The public review starts 31 March 2014 at 00:00 GMT and ends 14 April 201= 4 at 23:59 GMT. The specification was previously submitted for public review [= 2]. Due to the extensive number of changes, the complete Committee Specificat= ion Draft is open for review.=20 This is an open invitation to comment. OASIS solicits feedback from poten= tial users, developers and others, whether OASIS members or not, for the sake = of improving the interoperability and quality of its technical work. With this public review, we are testing a new convenience feature for sen= ding comments to the Technical Committee. The file http://docs.oasis-open.org/virtio/virtio/v1.0/csprd02/ virtio-v1.0-csprd02-COMMENT-TAGS.html contains the HTML version of the draft with a =E2=80=9C[comment?]=E2=80=9D= link next to each section heading. Clicking on this link will launch your email application= and begin a message to virtio-comment@lists.oasis-open.org with the specific section number and title in the subject line. (For example, =E2=80=9CPubl= ic review comment for virtio-v1.0-csprd02: 1.3 Terminology.=E2=80=9D) Simply enter = your comment and click send. You must be subscribed to the virtio-comment@lists.oasis-open.org mailing= list in order to send your comments. Instructions on how to subscribe can be f= ound at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=3Dv= irtio. Note that the Table of Contents doesn=E2=80=99t work in this version and = other internal document links may not work in this file. That is one of the items we nee= d fix before making this capability more broadly available. Please feel free to= let us know if you find this feature helpful. We plan to refine it and make i= t a part of our normal public review process. URIs: The prose specification document and related files are available here: Editable source (Authoritative): http://docs.oasis-open.org/virtio/virtio/v1.0/csprd02/tex/=20 HTML:=20 http://docs.oasis-open.org/virtio/virtio/v1.0/csprd02/virtio-v1.0-csprd02= .html PDF: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd02/virtio-v1.0-csprd02= .pdf ZIP distribution files (complete): For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can downl= oad the ZIP file here: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd02/virtio-v1.0-csprd02= .zip Additional information about this specification and the VIRTIO TC may be = found on the TC's public home page located at: http://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 accessed via the button labeled "Send A Comment" at the top of the TC public home page, or directly at: http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=3Dvirtio Feedback submitted by TC non-members for this work and for other work of = this TC is publicly archived and can be viewed at: http://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 publi= c review of 'Virtual I/O Device (VIRTIO) Version 1.0', we call your attenti= on to the OASIS IPR Policy [3] applicable especially [4] 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 right= s that read on an approved OASIS specification. OASIS invites any persons who kn= ow 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. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Additional references: [1] OASIS Virtual I/O Device (VIRTIO) Technical Committee http://www.oasis-open.org/committees/virtio/ [2] Previous public reviews:=20 30-day public review, 24 December 2014: https://lists.oasis-open.org/arch= ives/ members/201312/msg00013.html - Comment resolution log: http://docs.oasis-open.org/virtio/virtio/v1.0/c= sprd01 /virtio-v1.0-csprd01-comment-resolution-log.xlsx=20 [3] http://www.oasis-open.org/policies-guidelines/ipr [4] http://www.oasis-open.org/committees/virtio/ipr.php https://www.oasis-open.org/policies-guidelines/ipr#licensing_req Non-Assertion Mode=20 -- /chet=20 ---------------- Chet Ensign Director of Standards Development and TC Administration=20 OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393=20 Check your work using the Support Request Submission Checklist at http:// www.oasis-open.org/committees/download.php/47248/ tc-admin-submission-checklist.html=20 TC Administration information and support is available at http:// www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open ----- End forwarded message -----