Re: PKCS#11 URI slot attributes & last call

Darren J Moffat <Darren.Moffat@Oracle.COM> Thu, 18 December 2014 11:23 UTC

Return-Path: <Darren.Moffat@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 0D6AE1A6F2E; Thu, 18 Dec 2014 03:23:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 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] 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 q1Vi_0tU8gGh; Thu, 18 Dec 2014 03:23:55 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D545B1A07BE; Thu, 18 Dec 2014 03:23:54 -0800 (PST)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id sBIBNnie023029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Dec 2014 11:23:50 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id sBIBNm3O029269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Dec 2014 11:23:49 GMT
Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by userz7022.oracle.com (8.14.5+Sun/8.14.4) with ESMTP id sBIBNlbk005351; Thu, 18 Dec 2014 11:23:47 GMT
Received: from [10.163.198.80] (/10.163.198.80) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 18 Dec 2014 03:23:47 -0800
Message-ID: <5492B941.3030408@Oracle.COM>
Date: Thu, 18 Dec 2014 11:23:45 +0000
From: Darren J Moffat <Darren.Moffat@Oracle.COM>
Organization: Oracle Solaris Security
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:17.0) Gecko/20140924 Thunderbird/17.0.11
MIME-Version: 1.0
To: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Subject: Re: PKCS#11 URI slot attributes & last call
References: <alpine.GSO.2.00.1412161359100.4549@keflavik> <CAB6OCMvGxT99cGGBSBbz=XU2+F1xRzBa97z6dY-qPSJk1GWXyQ@mail.gmail.com> <20141217230150.GB9443@localhost> <CAB6OCMvkPSfNYqftAgbcN5KrG7kxb5ooico205O6EffcsU8SwQ@mail.gmail.com> <20141218000736.GL9443@localhost> <alpine.GSO.2.00.1412171614240.4549@keflavik> <CAB6OCMsAdTarz5XBHgTnU=v9qweS5B6mk-tb7Gbf7kwkDFBDMg@mail.gmail.com> <20141218004717.GN9443@localhost> <alpine.GSO.2.00.1412171704530.4549@keflavik> <20141218012300.GP9443@localhost> <alpine.GSO.2.00.1412172154150.14405@rejewski> <1418900792.7577.5.camel@gnutls.org>
In-Reply-To: <1418900792.7577.5.camel@gnutls.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/K3ODEAKXdba7RI-1DDs9bG_tGDY
X-Mailman-Approved-At: Thu, 18 Dec 2014 08:23:38 -0800
Cc: Stef Walter <stef@thewalter.net>, Jaroslav Imrich <jaroslav.imrich@gmail.com>, ietf@ietf.org, saag@ietf.org, Jan Pechanec <jan.pechanec@Oracle.COM>
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: Thu, 18 Dec 2014 11:23:56 -0000


On 12/18/14 11:06, Nikos Mavrogiannopoulos wrote:
> On Wed, 2014-12-17 at 22:54 -0800, Jan Pechanec wrote:
>
>> +   Slot ID is a Cryptoki-assigned number that is not guaranteed stable
>> +   across PKCS#11 module initializations.  However, slot description and
>> +   manufacturer ID may not be enough to uniquely identify a specific
>> +   reader.  In situations where slot information is necessary use of
>> +   "slot-id" attribute may be justified if sufficient slot ID stability
>> +   is provided in the PKCS#11 provider itself or externaly.
>
> Hello Jan,
> I'd like to propose the following text instead:
> "Slot ID is a Cryptoki-assigned number that is not guaranteed stable
> across PKCS#11 module initializations. However, there are certain
> libraries and modules which provide stable slot numbers and
> descriptions. For these cases, when the manufacturer ID is not
> sufficient to uniquely identify a specific reader, the slot
> information could be used to increase the precision of the token
> identification. In other scenarios, using the slot identifiers is
> likely to cause usability issues."
>
> That text discusses both the benefits and the risks.

If the consensus is that slot-id stays then I think text exactly like 
you wrote is essential.

-- 
Darren J Moffat