Return-Path: nfsv4-bounces@ietf.org From: Chuck Lever In-Reply-To: <20171012120814.GB5957@stefanha-x1.localdomain> Date: Thu, 12 Oct 2017 12:40:20 -0400 Message-Id: References: <20171005200835.GA31525@stefanha-x1.localdomain> <20171012120814.GB5957@stefanha-x1.localdomain> To: Stefan Hajnoczi Subject: Re: [nfsv4] Draft RFC for ONC RPC over AF_VSOCK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Linux NFS Mailing List , Matt Benjamin , NFSv4 Content-Type: multipart/mixed; boundary="===============9198866999815791686==" Errors-To: nfsv4-bounces@ietf.org Sender: "nfsv4" MIME-Version: 1.0 List-ID: --===============9198866999815791686== Content-Type: multipart/alternative; boundary=Apple-Mail-1D611ACA-1783-4A07-84AA-7DFC05FC0943 Content-Transfer-Encoding: 7bit --Apple-Mail-1D611ACA-1783-4A07-84AA-7DFC05FC0943 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Oct 12, 2017, at 8:08 AM, Stefan Hajnoczi wrote: >=20 >> On Thu, Oct 05, 2017 at 04:50:55PM -0400, Matt Benjamin wrote: >>> On Thu, Oct 5, 2017 at 4:08 PM, Stefan Hajnoczi wr= ote: >>> I have previously submitted patches that implement NFS client and nfsd >>> support for the AF_VSOCK address family. In order for this to be >>> acceptable for merge the AF_VSOCK transport needs to be defined in an >>> IETF RFC. Below is a draft RFC that defines ONC RPC over AF_VSOCK. >>>=20 >>> My patches use netid "vsock" but "tcpv" has also been suggested. This d= raft >>> RFC still uses "vsock" but I'll update it to "tcpv" if there is consensu= s. >>>=20 >>=20 >> I think "vsock" is the appropriate netid, not "tcpv." Stream >> orientation, if anything, is the general category containing TCP and >> VSOCK, not the reverse. But really I think it's just more clear. >>=20 >> I think this draft needs to be sent to the IETF NFSv4 working group >> alias, nfsv4@ietf.org. >=20 > Thanks. Will send the next revision properly formatted to the NFSv4 > working group. Don=E2=80=99t do that. Please submit a personal draft via: https://datatracker.ietf.org/submit/ once you have appropriate permission from RH legal counsel to contribute to the IETF. Then approach the working group to introduce your submitted document. Thanks!= --Apple-Mail-1D611ACA-1783-4A07-84AA-7DFC05FC0943 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

On Oct 12, 2017, at 8:08 AM, Stefan Ha= jnoczi <stefanha@redhat.com&g= t; wrote:

On Thu, Oct 05,= 2017 at 04:50:55PM -0400, Matt Benjamin wrote:
On Thu, Oct 5, 2017 at 4:08 PM, Stefan Hajnoczi <stefanha@redhat.com> wrote:
I = have previously submitted patches that implement NFS client and nfsd=
support for the AF_VSOCK address family.  In order for th= is to be
acceptable for merge the AF_VSOCK transport nee= ds to be defined in an
IETF RFC.  Below is a draft = RFC that defines ONC RPC over AF_VSOCK.

My patches use netid "vsock" but "tcpv" has also be= en suggested.  This draft
RFC still uses "vsoc= k" but I'll update it to "tcpv" if there is consensus.


I think &= quot;vsock" is the appropriate netid, not "tcpv."  Stre= am
orientation, if a= nything, is the general category containing TCP and
=
VSOCK, not the reverse.  But really I = think it's just more clear.

I think thi= s draft needs to be sent to the IETF NFSv4 working group
alias, nfsv4@ietf.org.

Thanks= .  Will send the next revision properly formatted to the NFSv4<= br>working group.

Do= n=E2=80=99t do that. Please submit a personal draft via:


once you have appropriate pe= rmission from RH legal
counsel to contribute to the IETF. Then ap= proach the
working group to introduce your submitted document.

Thanks!
= --Apple-Mail-1D611ACA-1783-4A07-84AA-7DFC05FC0943-- --===============9198866999815791686== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www.ietf.org/mailman/listinfo/nfsv4 --===============9198866999815791686==--