Re: slot attributes & last call

Jan Pechanec <jan.pechanec@oracle.com> Fri, 19 December 2014 07:28 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 BBB911A1B3F; Thu, 18 Dec 2014 23:28:46 -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 2Qmbenuk5H8t; Thu, 18 Dec 2014 23:28:45 -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 A94F81A03A4; Thu, 18 Dec 2014 23:28:45 -0800 (PST)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id sBJ7SYqu006337 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 19 Dec 2014 07:28:35 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id sBJ7SW39006875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 Dec 2014 07:28:33 GMT
Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id sBJ7SV3j017193; Fri, 19 Dec 2014 07:28:32 GMT
Received: from keflavik.us.oracle.com (/10.132.148.214) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 18 Dec 2014 23:28:31 -0800
Date: Thu, 18 Dec 2014 23:28:30 -0800 (PST)
From: Jan Pechanec <jan.pechanec@oracle.com>
X-X-Sender: jpechane@keflavik
To: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Subject: Re: slot attributes & last call
In-Reply-To: <1418971932.28712.2.camel@gnutls.org>
Message-ID: <alpine.GSO.2.00.1412182314240.20181@keflavik>
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> <5492B8E1.6010709@Oracle.COM> <1418971932.28712.2.camel@gnutls.org>
User-Agent: Alpine 2.00 (GSO 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Mj8F8M34Nk8Q_7UjIfqtx4TE1Q8
X-Mailman-Approved-At: Fri, 19 Dec 2014 09:57:11 -0800
Cc: Darren J Moffat <Darren.Moffat@oracle.com>, Stef Walter <stef@thewalter.net>, Jaroslav Imrich <jaroslav.imrich@gmail.com>, Nikos Mavrogiannopoulos <n.mavrogiannopoulos@gmail.com>, saag@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: Fri, 19 Dec 2014 07:28:46 -0000

On Fri, 19 Dec 2014, Nikos Mavrogiannopoulos wrote:

>> > 	for example, metaslot on Solaris is always 0 so slot-id=0
>> > would be reliable there to use to access the soft token.  Jan.
>> 
>> It is the zeroth slot in the list of slots not a slotid with a value of 
>> 0 - the distinction is subtle.
>> I don't think we should have slot-id, it isn't stable and I know that 
>> some vendors use random values.
>
>Jan,
> Given that this was the main argument for adding slot-id, is there any
>other reason for adding it? Aren't the description and manufacturer
>sufficient for the applications which want to restrict to a specific
>slot?

	hi Nikos, I still think that its ID is 0 since I've been using 
it that way in C_GetMechanismInfo(0, ...).  However, my point is that 
some modules MAY provide stable IDs and since there is no serial 
number as for token then description/manufacturer may not be enough to 
uniquely identify a slot.  That's why it could be useful in certain 
situations.

	I somehow think that people would end up using it anyway and 
partly for that reason we added "pin-value" which was initially 
rejected, too.  If we define slot-id we avoid different parsers to use 
different names like "slot", "slotid", or "slot-id".  That's why I 
think it might be better to include it with a proper note.

	regards, Jan.

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