Re: [nfsv4] Chapter 12 for next rfc3530bis

<david.noveck@emc.com> Tue, 12 October 2010 18:47 UTC

Return-Path: <david.noveck@emc.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BD703A69FF for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 11:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.683
X-Spam-Level:
X-Spam-Status: No, score=-6.683 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvitToGo0d1a for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 11:47:35 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 8642E3A69B6 for <nfsv4@ietf.org>; Tue, 12 Oct 2010 11:47:35 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id o9CImixP014152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Oct 2010 14:48:44 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 12 Oct 2010 14:48:41 -0400
Received: from corpussmtp4.corp.emc.com (corpussmtp4.corp.emc.com [10.254.169.197]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id o9CImXOc006085; Tue, 12 Oct 2010 14:48:37 -0400
Received: from CORPUSMX50A.corp.emc.com ([128.221.62.41]) by corpussmtp4.corp.emc.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 12 Oct 2010 14:47:41 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Oct 2010 14:47:40 -0400
Message-ID: <BF3BB6D12298F54B89C8DCC1E4073D80027DDA91@CORPUSMX50A.corp.emc.com>
In-Reply-To: <20101012182853.GA25673@fieldses.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [nfsv4] Chapter 12 for next rfc3530bis
Thread-Index: ActqO24tnT8dbmJSR3i7l9LcdhaSsAAAhQwQ
References: <BF3BB6D12298F54B89C8DCC1E4073D80027DD8CC@CORPUSMX50A.corp.emc.com> <20101012170759.GA22495@fieldses.org> <20101012170936.GB22495@fieldses.org> <BF3BB6D12298F54B89C8DCC1E4073D80027DDA78@CORPUSMX50A.corp.emc.com> <20101012182853.GA25673@fieldses.org>
From: <david.noveck@emc.com>
To: <bfields@fieldses.org>
X-OriginalArrivalTime: 12 Oct 2010 18:47:41.0036 (UTC) FILETIME=[F2DDC2C0:01CB6A3D]
X-EMM-MHVC: 1
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] Chapter 12 for next rfc3530bis
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 18:47:36 -0000

You as the server can enforce it by simply checking whether it is UTF-8
and returning INVAL if it isn't.

The client is going to have some understanding of what it is being
presented with and certainly can map an o-umlaut for example, to the
UTF-8 version of that which is two bytes.  It is supposed to send UTF-8.


-----Original Message-----
From: J. Bruce Fields [mailto:bfields@fieldses.org] 
Sent: Tuesday, October 12, 2010 2:29 PM
To: Noveck, David
Cc: Black, David; jlentini@netapp.com; nfsv4@ietf.org
Subject: Re: [nfsv4] Chapter 12 for next rfc3530bis

On Tue, Oct 12, 2010 at 02:12:55PM -0400, david.noveck@emc.com wrote:
> On Tue, Oct 12, 2010 at 01:07:59PM -0400, bfields wrote:
> > I just want to make sure I'm getting into the business of mapping
> 
> (I meant to have a "not" there!)
> 
> > non-ascii non-utf8 usernames....
> 
> UVMUST says it MUST be UTF-8.  So if you get into the business of
> mapping non-ascii non-utf8, you are non-compliant and you have only
> yourself to blame for having to map stuff that you aren't supposed to
> have accepted in the first place. 

I have some control over nfsd, but none over useradd.  If there are
people out there with /etc/passwd's containing non-utf8 non-ascii
usernames then the only way I'd see to enforce a MUST of utf-8 would be
by taking a stab at what encoding they're using and then mapping to and
from utf-8.  No thanks!

Hm, but non-ascii usernames can't be used in email addresses, can they?
So maybe we'll never see them in practice.

--b.