IETF Last Call Review of draft-ietf-nfsv4-internationalization-16
review-ietf-nfsv4-internationalization-16-genart-lc-robles-2026-08-03-00

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-nfsv4-internationalization-16
Reviewer: Ines Robles
Review Date: 2026-08-03
IETF LC End Date: 2026-08-03
IESG Telechat date: Not scheduled for a telechat

Summary:

This document describes the handling of internationalization for all NFSv4
protocols, including NFSv4.0, NFSv4.1, NFSv4.2, their extensions, and future
minor versions. It updates RFC 7530 and RFC 8881.

The document is well written. I have a few minor comments that I believe should
be addressed before publication.

Comments/Questions:

1- It would be helpful to add a section summarizing the updates to RFC 8881,
similar to the section that summarizes the updates to RFC 7530. This would make
it easier for readers to identify the changes introduced by this document.

2- Section 2.2: For the definition of Canonical Equivalence (of strings), it
might be helpful to add a reference to the Unicode definition of canonical
equivalence, for example, Unicode Standard Annex #15, Unicode Normalization
Forms (https://www.unicode.org/reports/tr15/) ?

3- Section 7.1: HEBREW LETTER BET WITH DAGESH (U+FB3) --> HEBREW LETTER BET
WITH DAGESH (U+FB31)

4- Section 7.2: "Servers MAY treat name strings that only differ as to case as
identical when searching for a given file without making any change in the name
presented when the file is created. When the OPTIONAL attributes
case_insensitive and case_preserving are implemented, their values will be true
and false, respectively."

Based on my understanding, case_preserving should be true, not false, since the
capitalization of the name is preserved when the file is created.

Nits:

5- all minor version --> all minor versions

6- each effected --> each affected

7- file name are --> file names are

8- Such file are --> Such file systems are

9- they do not to define --> they do not define

10- can also represented --> can also be represented

11- [RFC8178]) --> [RFC8178]

12- The making this shift --> By making this shift... ?

13- (in Section 7.3)." --> (in Section 7.3).

14- related as to normalization --> related to normalization

15- former chose --> former was chosen

16- earlier version --> earlier versions ?

17- ACTUE --> ACUTE ?

18- use by the server --> used by the server

19- previous implementation --> previous implementations

20- fit it one byte --> fit in one byte

21- "xn--"formed --> missing space

22- ACII --> ASCII

23- There is likely to be few or no implementations --> There are likely to be
few or no implementations

24- there a number of troubling --> there are a number of troubling

25- chances of that occurring is --> chances of that occurring are

26- UTF8-8 --> UTF-8

27- such the determinations --> such determinations

28- other sorts strings --> other sorts of strings

29- In the event that happens --> In the event that this happens

30- information about potential future needs are discussed --> information
about potential future needs is discussed

31- The document alternates between "filesystem" and "file system". It would be
nice to adopt a single form throughout the document.

Thanks for this document,

Ines.