Re: [nfsv4] [PATCH nfs-utils v3 00/14] add NFS over AF_VSOCK support

Stefan Hajnoczi <stefanha@redhat.com> Fri, 15 September 2017 11:52 UTC

Return-Path: <stefanha@redhat.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 562D41331D2 for <nfsv4@ietfa.amsl.com>; Fri, 15 Sep 2017 04:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NhmEbCF-W9yj for <nfsv4@ietfa.amsl.com>; Fri, 15 Sep 2017 04:52:33 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E94A3133071 for <nfsv4@ietf.org>; Fri, 15 Sep 2017 04:52:32 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 58DEA461C1; Fri, 15 Sep 2017 11:52:25 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 58DEA461C1
Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=stefanha@redhat.com
Received: from localhost (ovpn-117-224.ams2.redhat.com [10.36.117.224]) by smtp.corp.redhat.com (Postfix) with ESMTP id 7CF6C6F118; Fri, 15 Sep 2017 11:52:24 +0000 (UTC)
Date: Fri, 15 Sep 2017 12:52:23 +0100
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: David Noveck <davenoveck@gmail.com>, Christoph Hellwig <hch@infradead.org>, Linux NFS Mailing List <linux-nfs@vger.kernel.org>, Jeff Layton <jlayton@redhat.com>, Steve Dickson <steved@redhat.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>, "J. Bruce Fields" <bfields@fieldses.org>, NeilBrown <neilb@suse.com>, Matt Benjamin <mbenjami@redhat.com>
Message-ID: <20170915115223.GB14994@stefanha-x1.localdomain>
References: <20170913102650.10377-1-stefanha@redhat.com> <20170913162111.GA14389@infradead.org> <CADaq8jd2VaHUX=9rVbG41tTPj+9R8Grkjnaoh1hfKv8sVn5-GA@mail.gmail.com> <EE7BAC64-DE4E-4A46-B692-08C0D7FE9D72@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <EE7BAC64-DE4E-4A46-B692-08C0D7FE9D72@oracle.com>
User-Agent: Mutt/1.8.3 (2017-05-23)
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Fri, 15 Sep 2017 11:52:25 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/chE-ZMk-41wLR-61R48a6dJkxxM>
X-Mailman-Approved-At: Fri, 15 Sep 2017 08:52:34 -0700
Subject: Re: [nfsv4] [PATCH nfs-utils v3 00/14] add NFS over AF_VSOCK support
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Sep 2017 14:46:30 -0000

On Wed, Sep 13, 2017 at 11:21:36AM -0700, Chuck Lever wrote:
> 
> > On Sep 13, 2017, at 11:18 AM, David Noveck <davenoveck@gmail.com> wrote:
> > 
> > > and how to ask IESG to assign it?
> > 
> > The way to get the IESG to assign it would be to write an RFC and get it approved as a Proposed Standard but I don't think you need to do that.  There is a portion of the netid registry that is assigned on a first-come-first-served basis (see RFCs 5665 and 5226) and if you are OK with that, the IESG doesn't have to be involved.  You simply have to ask IANA to assign it, providing the information (pretty limited) mentioned in those RFCs.
> 
> Stefan also needs to define a universal address format.
> 
> And somewhere we need to specify how this new RPC transport works.
> In hand-waving mode, it's basically TCP (with the same connection
> and record-marking semantics) but using a different address family.
> 
> So it may not be as simple as a single IANA action.

Thanks Christoph, David, and Chuck.  I'll reread the RFCs and try to
make progress on this.

Stefan