Re: slot attributes & last call

Jan Pechanec <jan.pechanec@oracle.com> Thu, 18 December 2014 01:10 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 4635C1A00BD; Wed, 17 Dec 2014 17:10:20 -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 QU2OZwPsJ3eu; Wed, 17 Dec 2014 17:10:18 -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 223521A0092; Wed, 17 Dec 2014 17:10:18 -0800 (PST)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id sBI1ADeF019914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Dec 2014 01:10:13 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id sBI1ABUN028417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Dec 2014 01:10:12 GMT
Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15]) by userz7022.oracle.com (8.14.5+Sun/8.14.4) with ESMTP id sBI1AAmo015264; Thu, 18 Dec 2014 01:10:10 GMT
Received: from keflavik.us.oracle.com (/10.132.148.214) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 17 Dec 2014 17:10:09 -0800
Date: Wed, 17 Dec 2014 17:10:08 -0800 (PST)
From: Jan Pechanec <jan.pechanec@oracle.com>
X-X-Sender: jpechane@keflavik
To: Nico Williams <nico@cryptonector.com>
Subject: Re: slot attributes & last call
In-Reply-To: <20141218004717.GN9443@localhost>
Message-ID: <alpine.GSO.2.00.1412171704530.4549@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> <CAB6OCMsAdTarz5XBHgTnU=v9qweS5B6mk-tb7Gbf7kwkDFBDMg@mail.gmail.com> <20141218004717.GN9443@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: acsinet22.oracle.com [141.146.126.238]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/N1wIwkGfbf2q-sORcO16vyOACwQ
X-Mailman-Approved-At: Thu, 18 Dec 2014 08:24:55 -0800
Cc: Darren J Moffat <Darren.Moffat@oracle.com>, Stef Walter <stef@thewalter.net>, Jaroslav Imrich <jaroslav.imrich@gmail.com>, ietf@ietf.org, saag@ietf.org, Nikos Mavrogiannopoulos <n.mavrogiannopoulos@gmail.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 01:10:21 -0000

On Wed, 17 Dec 2014, Nico Williams wrote:

>> > >I think so.  This is really for Jan to answer.  Maybe the Solaris
>> > >libpkcs11 should just ensure a meaningful (stable and distinct) slot
>> > >label.  If that could be done then slot-id could be excluded here.
>> > >
>> > >Jan?
>> >
>> >         for example, metaslot on Solaris is always 0 so slot-id=0
>> > would be reliable there to use to access the soft token.  Jan.
>> 
>> And there is no other URI that could identify that slot without the slot-id
>> attribute? i.e. pkcs11:slot-description=metaslot
>
>I would think so.  Maybe Jan misunderstood my question; he certainly
>didn't answer it.

	I did, I'm sorry.  The description is distinct, "Sun Metaslot" 
and it's defacto stable but what I wanted to say was that I don't 
think it is about whether we find a way not to use the attribute since 
we could probably do without other attributes as well, I still think 
that if we add slot-description and slot-manufacturer, we should add 
slot-id since there are situations where it may be useful.

	I will draft new text including the slot-id attribute first 
and send it here but will not file it yet.

	thank you for reviewing this last minute proposals.  J.

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