On Tue, 2024-06-18 at 22:49 -0700, Christoph Hellwig wrote: > What happened to the requirement that all protocol extensions added > to Linux need to be standardized in IETF RFCs? > The point of the side band protocol here is literally just to discover if the server on the other end of the connection is me, myself and I. IOW: did the IP + port that was used to set up a connection end up, through the magic of routing, connecting to a knfsd service that is running on the same machine as the client. The only requirement for interoperability with other servers is that we don't break them when probing. Hence the side band protocol, which uses the fact that it is an RPC program with a value that will be ignored by all other servers except the Linux servers that implement it. Otherwise, the protocol is private to the Linux client and knfsd. So, if the consensus is that this still needs to go through the IETF, then fine, we can do that, and register the side band program name with IANA. If there is a better way to determine that we're talking to our own server (which may be running in a container with its own network namespace) then I'm all ears. -- Trond Myklebust Linux NFS client maintainer, Hammerspace trond.myklebust@xxxxxxxxxxxxxxx
