Re: [I18ndir] NFS i18n

John Levine <johnl@taugh.com> Thu, 21 May 2020 21:26 UTC

Return-Path: <johnl@iecc.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 092FF3A0BFF for <i18ndir@ietfa.amsl.com>; Thu, 21 May 2020 14:26:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.45
X-Spam-Level:
X-Spam-Status: No, score=-1.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, PP_MIME_FAKE_ASCII_TEXT=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=iecc.com header.b=ZI+r6WS3; dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=taugh.com header.b=iXOuMPOf
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 D__0QAwbbQ47 for <i18ndir@ietfa.amsl.com>; Thu, 21 May 2020 14:26:40 -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 EC3753A0BF6 for <i18ndir@ietf.org>; Thu, 21 May 2020 14:26:39 -0700 (PDT)
Received: (qmail 56666 invoked by uid 100); 21 May 2020 21:26:38 -0000
Date: 21 May 2020 21:26:38 -0000
Message-ID: <ra6rmd$1nah$1@gal.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: i18ndir@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=dd53.5ec6f20e.k2005; i=news@user.iecc.com; bh=r73kJKYo3m6l2iSpz8aDJyIPSV13YhaLJav774/Seik=; b=ZI+r6WS3hcOOa4qAQ+S/0Px+IXLBnAVUx0PO56Lbnv9ENCaNxyy2QiqxHhruL3LtHrH17KZcjVNnEHPQo6YIbV/G7lP/WNvuPTZkEmwaJEsEafrFFvl95GJN6VzHP0nnzTx0xVqdNlZcHW4EHAFldVZ8U5Nw+1/OenLxdSZsrDrAvgcgerCj+f1+KgduwXtfXHrOhzoL0v11cAeSyphkS7WtM4UjI6LaDJh4cmsa+WmKfuf48pDvmfTVn5jlnrs2
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=dd53.5ec6f20e.k2005; olt=news@user.iecc.com; bh=r73kJKYo3m6l2iSpz8aDJyIPSV13YhaLJav774/Seik=; b=iXOuMPOfEyhcbDZIJ+hdERAe8eHKybFPLtzjdue0JeED/3k6nrfbYhax9/46azpdlRpeKk7NU7wPmRbx2gSunROzwz+OvANoGmcUpFQcCZ55/3axQhdl/cI0jedHWc0vw92p5SiovY95R2xjZxwaqL/tarwwDkvprS6X/Nit1JvctbJP2RMXvjTn88obwrYxvYFRfOA7agVcXLZ5txTm4h3rVeUPSnQE6s0Tfe+cGDyhU1OvKHQ6rvrmmant747D
Organization: Taughannock Networks
References: <4DC95412-CAE3-414C-8B28-42CB5E129224@episteme.net> <CCED5FB7-4D12-483C-BC4D-7F7393AB0D8B@viagenie.ca>
In-Reply-To: <4DC95412-CAE3-414C-8B28-42CB5E129224@episteme.net> <CCED5FB7-4D12-483C-BC4D-7F7393AB0D8B@viagenie.ca>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@iecc.com (John Levine)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/OVYWX1OZtQxo6pQtsQdDKrr1vdA>
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: Thu, 21 May 2020 21:26:42 -0000

In article <CCED5FB7-4D12-483C-BC4D-7F7393AB0D8B@viagenie.ca>ca>,
Marc Blanchet  <marc.blanchet@viagenie.ca> 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, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly