Re: [nfsv4] Re: NFSv4 ACL and POSIX interaction / mask, draft-ietf-nfsv4-acls-00 not ready

Spencer Shepler <spencer.shepler@sun.com> Mon, 10 July 2006 15:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzxdB-0005Fs-QU; Mon, 10 Jul 2006 11:25:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzxdA-0005Dk-En for nfsv4@ietf.org; Mon, 10 Jul 2006 11:25:04 -0400
Received: from nwkea-mail-1.sun.com ([192.18.42.13]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fzxd9-0004o2-1j for nfsv4@ietf.org; Mon, 10 Jul 2006 11:25:04 -0400
Received: from jurassic.eng.sun.com ([129.146.56.36]) by nwkea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k6AFP2gC013480; Mon, 10 Jul 2006 08:25:02 -0700 (PDT)
Received: from sheplap.local (vpn-129-150-34-170.Central.Sun.COM [129.150.34.170]) by jurassic.eng.sun.com (8.13.6+Sun/8.13.6) with ESMTP id k6AFP19r754127; Mon, 10 Jul 2006 08:25:01 -0700 (PDT)
Received: by sheplap.local (Postfix, from userid 76367) id 1C688274A08; Mon, 10 Jul 2006 10:25:00 -0500 (CDT)
Date: Mon, 10 Jul 2006 10:25:00 -0500
From: Spencer Shepler <spencer.shepler@sun.com>
To: nfsv4@ietf.org
Subject: Re: [nfsv4] Re: NFSv4 ACL and POSIX interaction / mask, draft-ietf-nfsv4-acls-00 not ready
Message-ID: <20060710152500.GA1510@137.96.227.10.in-addr.arpa>
Mail-Followup-To: nfsv4@ietf.org, nfs@lists.sourceforge.net
References: <C98692FD98048C41885E0B0FACD9DFB8028CEAAC@exnane01.hq.netapp.com> <200607101007.43824.agruen@suse.de> <20060710142445.GB978@fieldses.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20060710142445.GB978@fieldses.org>
User-Agent: Mutt/1.4.2.1i
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: nfs@lists.sourceforge.net
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: spencer.shepler@sun.com
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
Errors-To: nfsv4-bounces@ietf.org

On Mon, J. Bruce Fields wrote:
> On Mon, Jul 10, 2006 at 10:07:43AM +0200, Andreas Gruenbacher wrote:
> >  - define mechanisms which can be used to achieve *full* POSIX compliance of
> >    NFSv4.1 ACLs, on systems which implement a POSIX compliant ACL model,
> 
> All of these "POSIX" requirements (including the language about
> additional and alternate access control mechanisms) are from the one
> draft, right?
> 
> In other words, this is stuff people tried and failed to come to some
> agreement on in the past.
> 
> Other things being equal, I've got nothing against full compliance with
> that draft, but careless use of the word posix here may make it look
> like a bigger requirement than it really is.

I would like to echo that sentiment.  There are Posix "draft" ACLs.
As we know, they were part of a larger document that were never agreed to.

The way I have been looking at the problem is that we have NFSv4 ACLs
that need further interpretation to make the specification more useful.
We also have the issue of dealing with NFSv4 ACLs in environments like
the Posix APIs.

Spencer

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4