Re: [nfsv4] Chapter 12 for next rfc3530bis

<david.noveck@emc.com> Tue, 12 October 2010 18:12 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 B5F103A6A0E for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 11:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.685
X-Spam-Level:
X-Spam-Status: No, score=-6.685 tagged_above=-999 required=5 tests=[AWL=-0.086, 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 Qdd+2K3VoRdR for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 11:12:22 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id B023E3A67EB for <nfsv4@ietf.org>; Tue, 12 Oct 2010 11:12:22 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id o9CIDTcU019091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Oct 2010 14:13:30 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Tue, 12 Oct 2010 14:13:26 -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 o9CID7kE024578; Tue, 12 Oct 2010 14:13:07 -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:12:56 -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:12:55 -0400
Message-ID: <BF3BB6D12298F54B89C8DCC1E4073D80027DDA78@CORPUSMX50A.corp.emc.com>
In-Reply-To: <20101012170936.GB22495@fieldses.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [nfsv4] Chapter 12 for next rfc3530bis
Thread-Index: ActqMGpVCugZeDWlQmCcxzKgQ2cHQAAAxWzw
References: <BF3BB6D12298F54B89C8DCC1E4073D80027DD8CC@CORPUSMX50A.corp.emc.com> <20101012170759.GA22495@fieldses.org> <20101012170936.GB22495@fieldses.org>
From: <david.noveck@emc.com>
To: <bfields@fieldses.org>
X-OriginalArrivalTime: 12 Oct 2010 18:12:56.0182 (UTC) FILETIME=[18324960:01CB6A39]
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:12:25 -0000

Inline. 

-----Original Message-----
From: J. Bruce Fields [mailto:bfields@fieldses.org] 
Sent: Tuesday, October 12, 2010 1:10 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 01:07:59PM -0400, bfields wrote:
> On Mon, Oct 11, 2010 at 07:42:46PM -0400, david.noveck@emc.com wrote:
> >           <t hangText="ascii_must/ASCII:">
> >             indicating that strings of this type MUST be
> >             pure ASCII, and thus automatically UTF-8.
> >             The processing of these string must ensure
> >             that they are only have ASCII characters but 
> 			^^^^^^^^^^^^^
> 
> I know, you put that in there just to check if anyone was reading....

Of course.  You pass the test :-)

> 
> 
> >         <c>prinpfx4</c>
> >           <c>UVMUST</c>
> >           <c>NFS</c>
> >           <c>
> >             Must match one of a list of valid users
> >             or groups for that particular domain.  
> 
> What have the traditional restrictions on usernames been?  (A subset
of
> ascii?)

I'm guessing there has been some stuff in the 80-ff range for people who
have common European accents, umlauts, tildes, and whatever you call the
angstrom thing.

As far as a subset, probably NULs and such are out.  I haven't seen a
list.

The point is that what is valid depends primarily on presence on the
list.  If there is no name "aaaaa" then it is invalid in exactly the
same way a name consisting of a NUL would be.  They both are not on the
list.  There is no reason to divide this into two errors, at least that
I can see. 

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

> 
> --b.