From: Nicolas Williams (Nicolas.Williams@sun.com)
Date: 01/26/03-02:22:35 PM Z
Date: Sun, 26 Jan 2003 14:22:35 -0600 From: Nicolas Williams <Nicolas.Williams@sun.com> Subject: Re: [Dan.Oscarsson@kiconsulting.se: Comments on NFSv4 rfc3010bis-05 draft] Message-ID: <20030126142235.U16765@binky.central.sun.com> On Sun, Jan 26, 2003 at 05:31:46PM +0100, Dan Oscarsson wrote: > In summary: > I think NFSv4 must require ONE encoding of character data. > UCS normalised using form KC or form C with forbidden characters, > encoded as UTF-8. It is the responsibility of the server/client > to convert between local system encoding and the protocol > format. I think NFSv4 must require at the very least that filenames be stored normalized to some form (we should probably specify if it can be a K form or not, but D vs. C is not so important) and let clients and servers deal with that. This is pretty much what the draft says or implies. My concern is that specifying an on-the-wire normalization form could have limited the amount of normalization code needed in OS kernels (they'd only have to check normalization, rather than perform it). As such I think that NFSv4's utf8str_cs spec is correct, but sub-optimal. Cheers, Nico --
This archive was generated by hypermail 2.1.2 : 03/04/05-01:50:49 AM Z CST