From: Andreas Gruenbacher Subject: Re: Re: [NFS] NFSv4 ACL and POSIX interaction / mask, draft-ietf-nfsv4-acls-00 not ready Date: Fri, 14 Jul 2006 21:02:44 +0200 Message-ID: <200607142102.45216.agruen@suse.de> References: <200607032310.15252.agruen@suse.de> <200607071355.30624.agruen@suse.de> <20060714175930.GD20999@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Cc: "J. Bruce Fields" , Sam Falkner , Spencer Shepler , nfs@lists.sourceforge.net, Brian Pawlowski Return-path: To: nfsv4@ietf.org In-Reply-To: <20060714175930.GD20999@fieldses.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nfsv4-bounces@ietf.org List-ID: On Friday, 14. July 2006 19:59, J. Bruce Fields wrote: > For a server that doesn't support the new attributes, the client still > has available any of the current options: give up on non-destructive > chmod, or fall back on representing mask bits with DENIES. Maybe not what you meant, but shouldn't the client rely on the server to do "the right thing" when it sees a mode SETATTR? I think it would be a bad idea for the client to guess such details as which exact file security model a server implements. Instead, the server should be responsible for doing what the client is asking for (and erring towards more restrictive permissions if necessary). Andreas _______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www1.ietf.org/mailman/listinfo/nfsv4