IETF Logo Mail Archive

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:59 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 387931A8826; Mon, 12 Jan 2015 16:59:16 -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 y1O0WE3EJnVN; Mon, 12 Jan 2015 16:59:15 -0800 (PST)
Received: from homiemail-a34.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 02FAF1A8746; Mon, 12 Jan 2015 16:59:15 -0800 (PST)
Received: from homiemail-a34.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a34.g.dreamhost.com (Postfix) with ESMTP id B373C10060; Mon, 12 Jan 2015 16:59:14 -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=ph8gkIoCFoh3LW Z3d0k3xkA6ogo=; b=dQ1ZICR2vXnxmz5eRMZQwsDSzEx1btJn6z/i8VidWClJxo CZPucea0/xw848Rk6OlSeGKrsFWQeqMkrBtbIrJ5kaDG1GT1e5KYdVH4lyXEedG2 2RA8uQTVU9EQyKhVQzly6B7jFZ4kagzHIiaFyATCwKJAAvflApt8LaPgEcg2I=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a34.g.dreamhost.com (Postfix) with ESMTPA id 3F85E10059; Mon, 12 Jan 2015 16:59:14 -0800 (PST)
Date: Mon, 12 Jan 2015 18:59:13 -0600
From: Nico Williams <nico@cryptonector.com>
To: Jan Pechanec <jan.pechanec@oracle.com>
Subject: Re: [saag] i18n requirements (was: Re: NF* (Re: PKCS#11 URI slot attributes & last call))
Message-ID: <20150113005909.GY16323@localhost>
References: <9A043F3CF02CD34C8E74AC1594475C73AAF5744C@uxcn10-tdc05.UoA.auckland.ac.nz> <2A0EFB9C05D0164E98F19BB0AF3708C71D55675E67@USMBX1.msg.corp.akamai.com> <20150112045411.GD16323@localhost> <54B45A75.1050503@qti.qualcomm.com> <20150113000854.GW16323@localhost> <alpine.GSO.2.00.1501121636360.8555@keflavik>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.GSO.2.00.1501121636360.8555@keflavik>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/P3UxmD85070JU9Ula_2-AW9VtDk>
Cc: "Salz, Rich" <rsalz@akamai.com>, Pete Resnick <presnick@qti.qualcomm.com>, Peter Gutmann <pgut001@cs.auckland.ac.nz>, "saag@ietf.org" <saag@ietf.org>, "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:59:16 -0000

On Mon, Jan 12, 2015 at 04:45:57PM -0800, Jan Pechanec wrote:
> On Mon, 12 Jan 2015, Nico Williams wrote:
> >unfortunately they left other I18N details out.
> 
> 	hi Nico, the PKCS#11 specification says those strings are 
> UTF-8 back in the last version that is still current (2.20) from 2004 
> (didn't check earlier versions).  [...]

Huh.  Why did I remember octet strings??  Version 2.01 (1997) did have
plain octet strings with no character set nor codeset defined.  But
still, 2004 is pretty late.

> 	I think that saying that characters from US-ASCII set SHOULD 
> be used for labels and names since the PKCS#11 spec is not clear about 
> the normalization should be safe here.

Yes.

Nico
--

v2.23.0 | Report a Bug | By Email