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

Nikos Mavrogiannopoulos <> Mon, 12 January 2015 10:56 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 08AF21A8A97; Mon, 12 Jan 2015 02:56:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.278
X-Spam-Status: No, score=-3.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PE27PLiItSBM; Mon, 12 Jan 2015 02:56:44 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CA9621A89BB; Mon, 12 Jan 2015 02:56:43 -0800 (PST)
Received: by with SMTP id l89so16977634qgf.12; Mon, 12 Jan 2015 02:56:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=i9Xfbo5e9Udfs4kzaozY05EHdhESk/CBw3YL/Omrgks=; b=UQwRCi+cMQiOMnoihs+RZB3F09WsSyGuBFyr//5IizDMavAQgZTgPsBHyqON1FSi// Vfbns7zPAnjHS/T92U0pW1XriJCudIKu6ELaOS94d5ot+oG1bgwL6nhcMkuogZ4KsKKi txb6w5882uGU1UUNP9O4BGkhMki3po4GeJHw1ONbw8lzkhGmEXh0edHmytInoB65Mh8M tBfoOEK1S9gEKHp29+C8KaUM57fZCTNduwuRkUK77aMCFmLNDFatl0STxK+RwCuuv0UV W3NPfilO/tznBjR9w5e7c+EAkFLh7gH1FCVhb1ba9OkP3689Z8lkowk6evT5BEoig1aP 9u1Q==
MIME-Version: 1.0
X-Received: by with SMTP id v5mr48013538qag.59.1421060203048; Mon, 12 Jan 2015 02:56:43 -0800 (PST)
Received: by with HTTP; Mon, 12 Jan 2015 02:56:42 -0800 (PST)
In-Reply-To: <>
References: <>
Date: Mon, 12 Jan 2015 11:56:42 +0100
X-Google-Sender-Auth: 1VeGLmpzgZmCjxPMGnuD0Gsa0lE
Message-ID: <>
Subject: Re: [saag] i18n requirements (was: Re: NF* (Re: PKCS#11 URI slot attributes & last call))
From: Nikos Mavrogiannopoulos <>
To: Peter Gutmann <>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: <>
Cc: "" <>, Jan Pechanec <>, "" <>
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 10:56:55 -0000

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.