[nfsv4] Re: Our different approaches to draft POSIX ACL support in NFSv4

Christoph Hellwig <hch@lst.de> Thu, 25 July 2024 20:38 UTC

Return-Path: <hch@lst.de>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDF5FC151520 for <nfsv4@ietfa.amsl.com>; Thu, 25 Jul 2024 13:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jUv26xZzOUmP for <nfsv4@ietfa.amsl.com>; Thu, 25 Jul 2024 13:38:37 -0700 (PDT)
Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B365AC14F5F3 for <nfsv4@ietf.org>; Thu, 25 Jul 2024 13:38:36 -0700 (PDT)
Received: by verein.lst.de (Postfix, from userid 2407) id CC1F968AFE; Thu, 25 Jul 2024 22:38:32 +0200 (CEST)
Date: Thu, 25 Jul 2024 22:38:32 +0200
From: Christoph Hellwig <hch@lst.de>
To: Chuck Lever III <chuck.lever=40oracle.com@dmarc.ietf.org>
Message-ID: <20240725203832.GA6797@lst.de>
References: <83c39a7b12c05b0f1a0fa6e069b08e399864277a.camel@hammerspace.com> <CADaq8jfw1FVH3dxOEJAZLrw_S5y2F6eaGkcfpha4X8BBNWgRSQ@mail.gmail.com> <6903782a95875541489844e33541114f0bf01acb.camel@hammerspace.com> <CADaq8jdFYo_DtRxS3h17dyQSFqXeoR60OjsjMM=o35HDg8ZnNg@mail.gmail.com> <111D8D84-CFA9-4823-A5FD-A7B58045356C@oracle.com> <46897779-93DF-4A33-90A7-94AD55CD76E1@cert.org> <7E5AF217-C170-443A-8BFA-BF120FD1BF93@cert.org> <3C9C338E-DF1F-4845-AF03-5D10BDE965FC@oracle.com> <22E0D388-CF68-4812-84D0-10B63D3B4930@cert.org> <E0A2C3DF-ECC0-447B-B7E0-E8B14A7F0E41@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E0A2C3DF-ECC0-447B-B7E0-E8B14A7F0E41@oracle.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Message-ID-Hash: 6R4ROOYUV2ENVUAN3B4PNEJDPCKR4GFM
X-Message-ID-Hash: 6R4ROOYUV2ENVUAN3B4PNEJDPCKR4GFM
X-MailFrom: hch@lst.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Trond Myklebust <trondmy@hammerspace.com>, Bruce Fields <bfields@fieldses.org>, "nfsv4@ietf.org" <nfsv4@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [nfsv4] Re: Our different approaches to draft POSIX ACL support in NFSv4
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/AyEhbSqysrUgD2GaAh1OXUkCLEM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>

On Thu, Jul 25, 2024 at 05:53:01PM +0000, Chuck Lever III wrote:
> I personally would like to move forward, and as I said earlier
> I think it wouldn't be much effort at all. What I wasn't sensing
> was a strong consensus from other WG members that it would be a
> welcome effort.
> 
> My thought was I would author the document; the only obligation
> from WG members would be review.

My 2cents based on the previous discussion:  I think a draft documenting
the historical NFSACL sideband protocol would be nice to have for a lot
of reason, and I'd appreciate any effort put into it, but I don't think
it is needed for or really very helpful for adding Posix draft style
ACLs to NFSv4.