Re: [nfsv4] Chapter 12 for next rfc3530bis

<david.black@emc.com> Wed, 13 October 2010 14:58 UTC

Return-Path: <david.black@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 1D3113A6956 for <nfsv4@core3.amsl.com>; Wed, 13 Oct 2010 07:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.508
X-Spam-Level:
X-Spam-Status: No, score=-106.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 an+sxe1kiwJA for <nfsv4@core3.amsl.com>; Wed, 13 Oct 2010 07:58:44 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 0BE6C3A68FD for <nfsv4@ietf.org>; Wed, 13 Oct 2010 07:58:43 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id o9DExr27014357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Oct 2010 10:59:53 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 13 Oct 2010 10:59:41 -0400
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.169.196]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id o9DEweUQ001639; Wed, 13 Oct 2010 10:58:45 -0400
Received: from mxhub06.corp.emc.com ([128.221.46.114]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 13 Oct 2010 10:58:42 -0400
Received: from mx14a.corp.emc.com ([169.254.1.11]) by mxhub06.corp.emc.com ([128.221.46.114]) with mapi; Wed, 13 Oct 2010 10:58:41 -0400
From: <david.black@emc.com>
To: <bfields@fieldses.org>
Date: Wed, 13 Oct 2010 10:58:40 -0400
Thread-Topic: [nfsv4] Chapter 12 for next rfc3530bis
Thread-Index: ActqO21dsEh48Xl9S5i5IpFJiDUX9AAq0HHw
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E03D1C63E6E@MX14A.corp.emc.com>
References: <BF3BB6D12298F54B89C8DCC1E4073D80027DD8CC@CORPUSMX50A.corp.emc.com> <20101012170759.GA22495@fieldses.org> <20101012170936.GB22495@fieldses.org> <BF3BB6D12298F54B89C8DCC1E4073D80027DDA78@CORPUSMX50A.corp.emc.com> <20101012182853.GA25673@fieldses.org>
In-Reply-To: <20101012182853.GA25673@fieldses.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Oct 2010 14:58:42.0290 (UTC) FILETIME=[20593D20:01CB6AE7]
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: Wed, 13 Oct 2010 14:58:45 -0000

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

That's in the works, see draft-ietf-eai-frmwrk-4952bis, which also provides some indirect support for the pragmatic approach we're taking to i18n in rfc3530bis.

Thanks,
--David


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