Re: NF* (Re: PKCS#11 URI slot attributes & last call)

Jan Pechanec <jan.pechanec@oracle.com> Sun, 04 January 2015 03:59 UTC

Return-Path: <jan.pechanec@oracle.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 9467E1A1B13; Sat, 3 Jan 2015 19:59:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 JGxUsmgPd9MA; Sat, 3 Jan 2015 19:59:04 -0800 (PST)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF8921A1B06; Sat, 3 Jan 2015 19:59:04 -0800 (PST)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t043wtX9011792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Jan 2015 03:58:56 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id t043wsk6017861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 4 Jan 2015 03:58:55 GMT
Received: from abhmp0006.oracle.com (abhmp0006.oracle.com [141.146.116.12]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id t043wsk9017849; Sun, 4 Jan 2015 03:58:54 GMT
Received: from keflavik.us.oracle.com (/10.132.148.214) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 03 Jan 2015 19:58:54 -0800
Date: Sat, 3 Jan 2015 19:58:52 -0800 (PST)
From: Jan Pechanec <jan.pechanec@oracle.com>
X-X-Sender: jpechane@keflavik
To: Nico Williams <nico@cryptonector.com>
Subject: Re: NF* (Re: PKCS#11 URI slot attributes & last call)
In-Reply-To: <20141231091906.GO24442@localhost>
Message-ID: <alpine.GSO.2.00.1501031946310.6923@keflavik>
References: <CAK3OfOgm_ZYj-rY+4ExZzY8KY4G3rz2KLrZ8hQJi7ZUR4yiP0Q@mail.gmail.com> <alpine.GSO.2.00.1412300946340.4549@keflavik> <CAK3OfOha9qu=uDtqwDTdV78waLMaorYq0T6cq1YX3VzQn2OpKA@mail.gmail.com> <A4CC6CEC-D17E-4235-B615-9D2AD88096D4@frobbit.se> <20141231070328.GK24442@localhost> <B08B813F-B8B4-49F1-A0B9-60F322C8E9C7@frobbit.se> <20141231074641.GM24442@localhost> <947CA101-D717-4B56-8EEE-84B3A53BF4A1@frobbit.se> <20141231082551.GN24442@localhost> <48A18B23-AAF9-44EA-8557-D25EBE398B56@frobbit.se> <20141231091906.GO24442@localhost>
User-Agent: Alpine 2.00 (GSO 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ESlIH-BGytSK2apE8tsi5v6A8wM
Cc: Darren J Moffat <Darren.Moffat@oracle.com>, John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>, "saag@ietf.org" <saag@ietf.org>, =?ISO-8859-15?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
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: Sun, 04 Jan 2015 03:59:06 -0000

On Wed, 31 Dec 2014, Nico Williams wrote:

>I'm in favor of saying "do form-insensitive comparison".  I'd settle for
>"always normalize to NFC when creating PKCS#11 resources" because, after
>all, that's what IRIs need anyways, it's just that a PKCS#11 URI-using
>app might not be in a position to make "normalize on create" happen.

	we could recommend the normalize-before-matching approach.  
Even for objects (keys), the application could use only non-UTF-8 
value attributes in the PKCS#11 search template.  Then, go through all 
returning objects and for UTF-8 value attributes, do NFC normalization 
first before matching them.

	however, I think that "SHOULD" would be too strong.  I think 
it could be mentioned side by side to the warning text based on what 
John noted about situations with a need to use non-ASCII characters.

	Jan

-- 
Jan Pechanec <jan.pechanec@oracle.com>