IETF Logo Mail Archive

Re: [I18ndir] NFS i18n

John R Levine <johnl@taugh.com> Fri, 22 May 2020 01:34 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340003A0D68 for <i18ndir@ietfa.amsl.com>; Thu, 21 May 2020 18:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=pn2zd5h/; dkim=pass (1536-bit key) header.d=taugh.com header.b=EduNZOEl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ObPfsgGYYIx for <i18ndir@ietfa.amsl.com>; Thu, 21 May 2020 18:34:45 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E101C3A0C3D for <i18ndir@ietf.org>; Thu, 21 May 2020 18:34:44 -0700 (PDT)
Received: (qmail 5245 invoked from network); 22 May 2020 01:34:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=147b.5ec72c32.k2005; i=johnl-iecc.com@submit.iecc.com; bh=EyGNpq0sN0SlcVZgqNTeaWrR1Y7wNXlElpLryyvIlbE=; b=pn2zd5h/c0gYPHqYKdgz3QyDvR1Jig1PlQB4DN2IQk8VzwVplR8Wu6BDQ0Hpgd/A3PIHIBtXj3MSxYYfQmgfxF+2X+kOd4CdYM+cto3VB4k/BhNra5ek3L1wxX31+lFCLN5/qp7InBaZIPyHFtg4ra0lJLqRjh2GZociVMbOht/4o8tOz0rjs/kRX5HrFkvfMpeyM+YkIctNMAPAU7ll184YnDMfJA7DKcTAVpTNvUqJijmJWga0/1WpNpk6ixSQ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=147b.5ec72c32.k2005; olt=johnl-iecc.com@submit.iecc.com; bh=EyGNpq0sN0SlcVZgqNTeaWrR1Y7wNXlElpLryyvIlbE=; b=EduNZOElLaIPywffEjNMvmyu6rSC6Hn0awd/pP6mm5TjIsEEkMgHTSfZpOObtPFXSfORYdlmcc4pQ2eLSSbckHVoyXf+slmPH0I8x7zRFZb3FuMl4ADhUbGRegFK1mOhGnamJhtv8Y3ZdBwyRG88IwOFYKi+BikXrkWl0oA3tmGhO22N28N+BvDESlGsUGq1NFmmZKW5YJxqbhAG61fyozcupyWd+ocMESSp2Zn8QpejQ/MdwULwxYRxSs5Sxxwp
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 22 May 2020 01:34:41 -0000
Date: Thu, 21 May 2020 21:34:41 -0400
Message-ID: <alpine.OSX.2.22.407.2005212130371.6217@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Nico Williams <nico@cryptonector.com>
Cc: i18ndir@ietf.org
In-Reply-To: <20200521224857.GL18021@localhost>
References: <4DC95412-CAE3-414C-8B28-42CB5E129224@episteme.net> <CCED5FB7-4D12-483C-BC4D-7F7393AB0D8B@viagenie.ca> <ra6rmd$1nah$1@gal.iecc.com> <20200521224857.GL18021@localhost>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/1u4DVviNTH9__R91yiQE3tdSP6U>
Subject: Re: [I18ndir] NFS i18n
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 May 2020 01:34:48 -0000

>> 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. ...

> [The following is all about I18N as to file names, not domainnames.]
>
> NFSv4 servers can't realistically support varying locales by client, ...

I agree, but a NFS server in Turkey will want to use Turkish case mapping, 
not some generic UTS46 one-size-fits-badly mapping.  That's the point, 
they don't prescribe a single mapping.

> Thus it is my opinion is that NFSv4 shouldn't have that much to say
> normatively about I18N for file names!

It doesn't.  How about reading the draft, and comparing it to the part of 
the NFS RFC it updates, and reviewing it for us?

R's,
John

PS:

> Instead we should have an RFC laying out requirements and 
> recommendations for filesystems used via Internet remote/distributed 
> filesystem protocols.

That strikes me as something the IETF is very poorly qualified to do, and 
that nobody would pay attention to since it would be about 40 years too 
late.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email