Re: [I18ndir] NFS i18n

[John Levine <[e-mail]>]

In article <[e-mail]>,
Marc Blanchet  <[e-mail]> wrote:
>On 21 May 2020, at 13:57, Pete Resnick wrote:
>
>> We've been asked to do an early review the NFS i18n document 
>> (draft-dnoveck-nfsv4-internationalization; about 23 pages). Does 
>> anybody want to be the official reviewer, or shall I randomly pick the 
>> next person on the list?
>
>I’m no volunteering, but I would expect that they would have a Precis 
>(RFC8264) profile or if not, why they are not using one. A quick 
>browsing does not seem to tell that.

You need to read the i18n parts of RFC7530 (NFSv4) and RFC5661
(NFSv4.1 and 4.2) and the comments on them in the draft. They created
a stringprep profile for NFSv4.1 a decade ago which nobody ever
implemented.

My quick scan says that NFS character sets are a historical mess but
they seem to be making the best of it and trying to end up at UTF-8
with some reasonable normalization. They specifically note that
normalization and case mapping is language specific with the Turkish
"i" as an example so it is locale dependent. Most of this draft is
unchanged from Sec 12 of RFC 7530 with the biggest change I can see a
switch from IDNA2003 to IDNA2008 for things like server names which
are domain names. Filenames are not domain names so IDNA doesn't
apply.

One thing I would suggest is an appendix at the end summarizing the changes
from RFC7530.  They're mentioned in the text but it'd be nice to have them
in one place for NFS implementors who have already slogged through the
300 and 600 page documents this updates.

R's,
John
-- 
Regards,
John Levine, [e-mail], Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly