From: Mike Eisler (mike@eisler.com)
Date: 01/24/03-03:00:43 PM Z
Message-ID: <3E31A97B.3F88645C@eisler.com> Date: Fri, 24 Jan 2003 13:00:43 -0800 From: Mike Eisler <mike@eisler.com> Subject: Re: [Dan.Oscarsson@kiconsulting.se: Comments on NFSv4 rfc3010bis- 05 draft] Nicolas Williams wrote: > > On Fri, Jan 24, 2003 at 10:33:10AM -0800, Mike Eisler wrote: > > Nicolas Williams wrote: > > > > > Er, no, utf8str_cs requires that a normalization form be used, just not > > > on the wire. So the problem of legacy filesystems remains even if we do > > > not act to recommend or require a specific normalization form on the > > > wire. > > > > It requires a normalization form only if the server is case insensitive. > > This is not my reading of the draft. > > Section 11.1.1 clearly specifies what to do with respect to filenames > with equal names but different encoding [due to different normalization > forms used by the clients that create them]. Section 11.1.1 necessarily > requires that the server perform normalization of client inputs to some > form of the server's choosing. I don't see the text. Section 11.1.4 says no normalization form is specified. Stringprep has tables B1 and B2. B1 is required to be processed, but I didn't see anything in stringprep that said that normalization went with table B1. Table B2 explicitly says KC, and B2 is for dealing with case insensitive stuff. Section 3 of stringprpe (now RFC 3454) refers to Appendix B and the various tables. It says nothing about normization for B1, whereas it does say something about normalization with respect to B2 and B3. Now I am admittably quite ignorant on this topic, but it seems rather odd that B1 requires normalization (and according to RFC 3454, B1 is mandatory), and yet B3 is specified to allow applications to not use normalization when case matching. Section 2 of RFC 3454 distinguishes between the mapping phase and the normalization phase, and mapping is the topic of section 3 and appendix B. So if your reading is correct, then it seems to me RFC 3454 has a paradox. We apparently need an "RFC 3454 for Dummies" document. -mre
This archive was generated by hypermail 2.1.2 : 03/04/05-01:50:49 AM Z CST