From: Noveck, Dave (Dave.Noveck@netapp.com)
Date: 01/28/03-12:30:41 PM Z
Message-ID: <C8CF60CFC4D8A74E9945E32CF096548A072A55@SILVER.nane.netapp.com> From: "Noveck, Dave" <Dave.Noveck@netapp.com> Subject: RE: [Dan.Oscarsson@kiconsulting.se: Comments on NFSv4 rfc3010bis- 05 draft] Date: Tue, 28 Jan 2003 10:30:41 -0800 Dan Oscarsson wrote: > RFC 3454 "stringprep" is fine for the attributes in the NFSv4 protocol, > not for handling file names. Attributes? All the names of the mandatory and recommended attributes in v4 are pure ascii so I don't see where all the stringprep stuff would have any applicability at all. I guess there is no absolute guarantee that would stay true in future minor versions but that's a really good bet. Or are you talking about named attributes? These are essentially filenames in a special directory so if stringprep isn't good for filenames then why would it be good for named attributes?
This archive was generated by hypermail 2.1.2 : 03/04/05-01:50:51 AM Z CST