Re: [nfsv4] Adoption call for draft-dnoveck-nfsv4-security

> On Oct 13, 2022, at 11:07 AM, David Noveck <davenoveck@gmail.com> wrote:
> 
> This is an adoption call for draft-dnoveck-nfsv4-security.
> 
> This document describes nfsv4 security for all nfsv4 minor versions.  It was written as part of rfc5661bis effort and is intended to result in a standards-track document.  PAs stated in the abstract:

First impressions:

This document is huge - I thought we agreed to no longer do large WG documents?

There are a log of author notes - it does not appear to be a close to finished document.

Who has agreed to do the changes in their implemementations? I.e., security is important, but which vendors have agreed to make changes in their v4.0, v4.1, and v4.2 product implementations?

To be fair, I would have defined the  security issue with NFSv4 to be AUTH_SYS versus other models. I would not have dragged in  Labeled NFS, ACLS, OPEN, etc.

I might have included TLS vs Kerberos as  providing over date in flight security.

I would like us to focus on changes to the requirements to provide in flight security, which does not necessitate changes to the various protocols, versus new requirements which force us to change  existing implemementations.

> 
> ----
> 
> This document describes the core features of the NFSv4 family of protocols, applying to all minor versions. The discuss includes use of security features provided by RPC on a per-connection basis.
> 
> The current version of the document is intended,  in large part, to resulting working group discussion regarding existing NFSv4 security issues and to provide a framework for addressing these issues and obtaining working group consensus regarding necessary changes.
> 
> When the resulting document is eventually published as an RFC, it will supersede the description of security in existing minor version specification documents such as RFC 7530 and RFC 8881.
> 
> ----
> 
> The chairs would like to establish if there is interest in adopting this document by the nfsv4 working group.  The call will run for two weeks until the end of day on 10/26/2022 (UTC time).  Please send any objections or expressions of support for adoption to the wg mailing list.
> 
> As stated previously, since I am the editor of this document, I will not be involved in determining whether a consensus exists.  That responsibility will fall to Brian with Zahed available to fill in if Brian is unable to perform that role.
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4