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

Jan Pechanec <> Mon, 12 January 2015 17:18 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 00AD31ACCF5; Mon, 12 Jan 2015 09:18:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.21
X-Spam-Status: No, score=-6.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vIzSHL8PGCaN; Mon, 12 Jan 2015 09:18:18 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 406511ACCDE; Mon, 12 Jan 2015 09:18:18 -0800 (PST)
Received: from ( []) by (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t0CHGmrG009153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Jan 2015 17:16:49 GMT
Received: from ( []) by (8.14.4+Sun/8.14.4) with ESMTP id t0CHGmNH028525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 12 Jan 2015 17:16:48 GMT
Received: from ( []) by (8.14.4+Sun/8.14.4) with ESMTP id t0CHGmhY028518; Mon, 12 Jan 2015 17:16:48 GMT
Received: from (/ by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 12 Jan 2015 09:16:47 -0800
Date: Mon, 12 Jan 2015 09:16:46 -0800 (PST)
From: Jan Pechanec <>
X-X-Sender: jpechane@keflavik
To: Nikos Mavrogiannopoulos <>
Subject: Re: [saag] i18n requirements (was: Re: NF* (Re: PKCS#11 URI slot attributes & last call))
In-Reply-To: <>
Message-ID: <alpine.GSO.2.00.1501120909400.8555@keflavik>
References: <> <>
User-Agent: Alpine 2.00 (GSO 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Source-IP: []
Archived-At: <>
Cc: "" <>, "" <>, Peter Gutmann <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 12 Jan 2015 17:18:20 -0000

On Mon, 12 Jan 2015, Nikos Mavrogiannopoulos wrote:

>On Sun, Jan 11, 2015 at 11:26 PM, Peter Gutmann
><> wrote:
>>>I would urge, as I think I did before, some fairly strong warnings that, at
>>>least until the issues are clarified in PKCS#11 itself, one should be very
>>>certain one knows what one is doing (and what the consequences of one's
>>>choices will be) if one decides to move beyond the safety and general
>>>understanding of the ASCII/ ISO 646/ IA5 letter and digit repertoire.
>> I'd go even further than that and just mandate MUST ASCII.  This is a simple
>> means of pointing to a PKCS #11 object, not a universal means of communicating
>> abstract concepts in any language known to man.
>Correct, but that can be done by the OASIS PKCS #11 group, not by
>IETF. Here the draft proposes a way to expose PKCS #11 objects/tokens
>as a URI. It cannot mandate the format of the PKCS #11 attributes a
>module will contain.

	hi Nikos, I agree with Nico that RECOMMENDed for ASCII use in 
labels would be fine.  I'm gonna leave the new text for the new draft 
18 discussing issues with the PKCS#11 spec not being clear about how 
to normalize UTF-8 encoded Unicode characters, and what is our 
recommendation with regard to that.  I will revisit it today and send 
a new version draft for draft 18 here.  J.

Jan Pechanec <>