Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES

Next message: J. Bruce Fields: "Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES"
Previous message: Haynes, Tom: "[nfsv4] Why can't SECINFO return NFS4ERR_WRONGSEC?"
In reply to: J. Bruce Fields: "Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES"
Next in thread: J. Bruce Fields: "Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES"
Reply: J. Bruce Fields: "Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES"

Lisa.Week@Sun.COM

Date: Thu, 16 Dec 2004 16:00:51 -0700
From: Lisa Week <Lisa.Week@Sun.COM>
Subject: Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES
Message-id: <41C213A3.9090104@Sun.COM>

J. Bruce Fields wrote:
> On Thu, Dec 16, 2004 at 11:42:26AM -0800, Gordon Waidhofer wrote:
> 
>>The question of NFSV4_{READ|WRITE}_NAMED_ATTRIBUTES
>>should be deferred for as long as possible, certainly
>>in the near term. Why? Simply because there is unspoken
>>discord about what a named attribute is.
> 
> 
> I agree about the {READ|WRITE}_NAMED_ATTRIBUTES bits.
> 

Just to be clear...What are we actually saying with "The question of 
NFSV4_{READ|WRITE}_NAMED_ATTRIBUTES should be deferred for as long as 
possible"?  Go with the I-D interpretation?  Leave them unspecified? 
Something else?

Thanks.
Lisa

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