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

[Brian Pawlowski <[e-mail]>]

Good day, apologies for the inexcusable delay.

I am deferring final consensus call on this security to take on the
personal draft "draft-dnoveck-nfsv4-security which "It was written as part
of rfc5661bis effort and is intended to result in a standards-track
document." as a working group document.

I want to give Chris Inacio time to review draft prior to IETF 116. I will
redo the consensus call at IETF 116. This is not a judgment in any way on
the draft which is related to draft-dnoveck-nfsv4 which we just brought
into the working group. Please focus on draft-dnoveck-nfsv4 in WG right
now.

Are there any questions?

Brian Pawlowski
NFS V4 co-chair

P.S. Belated thanks to Chris for taking on editor role for
draft-dnoveck-nfsv4.

---------- Forwarded message ---------
From: David Noveck <[e-mail]>
Date: Thu, Oct 13, 2022 at 11:07 AM
Subject: Adoption call for draft-dnoveck-nfsv4-security
To: NFSv4 <[e-mail]>
Cc: nfsv4-chairs <[e-mail]>, <[e-mail]>


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:

----

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.