On Thu, Oct 12, 2017 at 12:40:20PM -0400, Chuck Lever wrote: > > > > On Oct 12, 2017, at 8:08 AM, Stefan Hajnoczi <stefanha@xxxxxxxxxx> 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@xxxxxxxxxx> wrote: > >>> 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. > >>> > >>> My patches use netid "vsock" but "tcpv" has also been suggested. This draft > >>> RFC still uses "vsock" but I'll update it to "tcpv" if there is consensus. > >>> > >> > >> 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. > >> > >> I think this draft needs to be sent to the IETF NFSv4 working group > >> alias, nfsv4@xxxxxxxx. > > > > Thanks. Will send the next revision properly formatted to the NFSv4 > > working group. > > Don’t 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. Okay, thanks! Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
