Re: [saag] i18n requirements (was: Re: NF* (Re: PKCS#11 URI slot attributes & last call))

Nico Williams <nico@cryptonector.com> Tue, 13 January 2015 00:09 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1591ACE2A; Mon, 12 Jan 2015 16:09:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 lL5--xMnOmMF; Mon, 12 Jan 2015 16:09:00 -0800 (PST)
Received: from homiemail-a89.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 4B08D1ACE29; Mon, 12 Jan 2015 16:09:00 -0800 (PST)
Received: from homiemail-a89.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a89.g.dreamhost.com (Postfix) with ESMTP id 122D031805D; Mon, 12 Jan 2015 16:09:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=vqbI3wNkMYcHIq 2NQOy3YNwqR+c=; b=dLAzNFx64WiQubXYy3UD3fwl9EmvCw59KW3j/wmARReX/K H81bP8hdwiN9PY7EA1OO6BCWpTajCiDyF4Kk4/hYRifgm0ItuWo2TVqYiTXbkWlo wSr2/SzuIslukML/hzwmLGV6Lyd0jNo46cxy6QScrBOtrbIatumThYWQkjdSg=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a89.g.dreamhost.com (Postfix) with ESMTPA id 82DEE31805C; Mon, 12 Jan 2015 16:08:59 -0800 (PST)
Date: Mon, 12 Jan 2015 18:08:59 -0600
From: Nico Williams <nico@cryptonector.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: [saag] i18n requirements (was: Re: NF* (Re: PKCS#11 URI slot attributes & last call))
Message-ID: <20150113000854.GW16323@localhost>
References: <9A043F3CF02CD34C8E74AC1594475C73AAF5744C@uxcn10-tdc05.UoA.auckland.ac.nz> <2A0EFB9C05D0164E98F19BB0AF3708C71D55675E67@USMBX1.msg.corp.akamai.com> <20150112045411.GD16323@localhost> <54B45A75.1050503@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54B45A75.1050503@qti.qualcomm.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BUekSQEoq9glGNJnlS1tAmC2dzw>
Cc: "Salz, Rich" <rsalz@akamai.com>, Peter Gutmann <pgut001@cs.auckland.ac.nz>, "saag@ietf.org" <saag@ietf.org>, Jan Pechanec <jan.pechanec@oracle.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jan 2015 00:09:02 -0000

On Mon, Jan 12, 2015 at 05:36:21PM -0600, Pete Resnick wrote:
> On 1/11/15 10:54 PM, Nico Williams wrote:
> 
> >On Sun, Jan 11, 2015 at 05:28:30PM -0500, Salz, Rich wrote:
> >
> >>>I'd go even further than that and just mandate MUST ASCII.
> >>I don't know if the IETF is "allowed" to do that any more, but +1 for
> >>the reasons you list.
> >I'm not sure if the IESG will agree to that...
> 
> Given that this particular member of the IESG has (successfully)
> argued vehemently for ASCII-only on multiple occasions in the recent
> past, I would say that your worries on that score are overdone. :-)

Well alright.  I'd love to see a set of guidelines for I18N activities.

When should we try to support Unicode, and when should we not?  Is it
one of those "I know it when I see it" kinds of guidelines?  That
wouldn't be useful enough :(

Mind you, IIRC PKCS#11 didn't even say anything about ASCII before.
Token labels and such used to be fixed-sized octet strings containing
character data.  Jan can correct me if I'm wrong.  I'm not sure even
saying "ASCII-only" would necessarily be safe in that case...

Fortunately the OASIS PKCS11 TC has clarified that these are UTF-8;
unfortunately they left other I18N details out.

Nico
--