Re: Draft RFC for ONC RPC over AF_VSOCK

[Stefan Hajnoczi <stefanha@redhat.com>]

On Fri, Oct 13, 2017 at 10:13:18AM -0400, Chuck Lever wrote:
> 
> > On Oct 12, 2017, at 8:17 AM, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > 
> > On Thu, Oct 05, 2017 at 04:53:07PM -0400, Chuck Lever wrote:
> >>> On Oct 5, 2017, at 4:08 PM, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > 
> >> An unchanging public reference to a specification of VSOCK is
> >> important to cite. If you can't find one, you'll have to explain
> >> why in the document. If the VSOCK specification is not an IETF
> >> document, it will have to be an Informative reference, and this
> >> I-D will also have to be Informative.
> > 
> > There is no formal specification.  VMware has published developer
> > documentation that explains the use of VSOCK in the context of VMware
> > products.
> 
> If there is nothing else, this is the most appropriate reference
> to cite. It provides a description of the technology made by the
> agent who invented and ultimately controls it (we believe: it
> may be that someone else did, and VMware is just taking credit;
> I think we need to know that too).
> 
> You should contact VMware to see if they have anything more, and
> to ask if they already have NFS on VSOCK. Let them know you are
> submitting standards in this area.
>
> > I will submit a vsock(7) man page to the Linux man-pages project
> > (similar to ip(7), tcp(7), etc).  It will document the semantics of the
> > AF_VSOCK address family.  Maybe this can serve as a reference?
> 
> The IESG will ultimately decide, but IMO citing a man page that
> you wrote would not be adequate unless you yourself invented the
> VSOCK technology.

Okay.  I'll check with Jorgen Hansen (VMware), Linux net/vmw_vsock/
maintainer, and see what the best reference is.

Stefan