Internationalization for the NFSv4 Protocols
draft-dnoveck-nfsv4-internationalization-02
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
David Noveck
|
|
Last updated |
|
2020-09-06
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
NFSv4 D. Noveck
Internet-Draft NetApp
Updates: 5661, 7530 (if approved) September 6, 2020
Intended status: Standards Track
Expires: March 10, 2021
Internationalization for the NFSv4 Protocols
draft-dnoveck-nfsv4-internationalization-02
Abstract
This document describes the handling of internationalization for all
NFSv4 protocols, including NFSv4.0, NFSv4.1, NFSv4.2 and extensions
thereof, and future minor versions.
It updates RFC7530 and RFC5661.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 10, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Noveck Expires March 10, 2021 [Page 1]
Internet-Draft NFSv4 Inernationalization September 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
2.1. Requirements Language Definition . . . . . . . . . . . . 4
2.2. Requirements Language Derivation . . . . . . . . . . . . 4
3. History . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Changes Relative to RFC7530 . . . . . . . . . . . . . . . . . 11
5. Limitations on Internationalization-Related Processing in the
NFSv4 Context . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Summary of Server Behavior Types . . . . . . . . . . . . . . 12
7. The Attribute Fs_charset_cap . . . . . . . . . . . . . . . . 13
7.1. The Attribute Fs_charset_cap in Published NFSv4.1
Specifications . . . . . . . . . . . . . . . . . . . . . 14
7.2. The Attribute Fs_charset_cap in Future NFSv4.1
Specifications . . . . . . . . . . . . . . . . . . . . . 16
8. String Encoding . . . . . . . . . . . . . . . . . . . . . . . 18
9. Normalization . . . . . . . . . . . . . . . . . . . . . . . . 19
10. Case-Insensitive Processing of File Names . . . . . . . . . . 19
10.1. Implementing Case-Insensitive Comparison of File Names . 23
10.2. Important Examples of Case-insensitive Handling of File
Names . . . . . . . . . . . . . . . . . . . . . . . . . 25
11. Internationalization-related Processing of File Names by
Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
11.1. Server Restrictions to Deal with Lack of Client
Knowledge . . . . . . . . . . . . . . . . . . . . . . . 29
11.2. Client Processing of File Names for Current NFSv4
Protocols . . . . . . . . . . . . . . . . . . . . . . . 30
11.3. Client Processing of File Names for Future NFSv4
Protocols . . . . . . . . . . . . . . . . . . . . . . . 34
12. String Types with Processing Defined by Other Internet Areas 35
12.1. Effect of IDNA Changes . . . . . . . . . . . . . . . . . 37
12.2. Potential Compatibility Issues Related to IDNA Changes . 38
13. Errors Related to UTF-8 . . . . . . . . . . . . . . . . . . . 40
14. Servers That Accept File Component Names That Are Not Valid
UTF-8 Strings . . . . . . . . . . . . . . . . . . . . . . . . 41
15. Future Minor Versions and Extensions . . . . . . . . . . . . 42
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43
17. Security Considerations . . . . . . . . . . . . . . . . . . . 43
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 44
Show full document text