Re: slot attributes & last call

Nico Williams <nico@cryptonector.com> Thu, 18 December 2014 01:23 UTC

Return-Path: <nico@cryptonector.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 C8D9A1A00BB; Wed, 17 Dec 2014 17:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 si1gzmR1cJ5M; Wed, 17 Dec 2014 17:23:06 -0800 (PST)
Received: from homiemail-a70.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 1AC051A0026; Wed, 17 Dec 2014 17:23:06 -0800 (PST)
Received: from homiemail-a70.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTP id BE9C4768059; Wed, 17 Dec 2014 17:23:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=Wz/P8XgKoq683J JSzVU7kG72TnI=; b=gcPlqEU4CmwidsoP9vcAGRQ9WjCrwRfl2sSjPbhacCSHvq exwJBW2mdE7yHqmmunsX/A3JMiEc+jU+dkotNVNwCq1CTzTOAz1/EVwBaa9twcic XSWtdF5I8jlFy+rN7Q/MXbIAp4uP2dg3Hr+cxa2w3slYW8UQuAc2Dxt5bPBNg=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTPA id 12628768057; Wed, 17 Dec 2014 17:23:05 -0800 (PST)
Date: Wed, 17 Dec 2014 19:23:04 -0600
From: Nico Williams <nico@cryptonector.com>
To: Jan Pechanec <jan.pechanec@oracle.com>
Subject: Re: slot attributes & last call
Message-ID: <20141218012300.GP9443@localhost>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.GSO.2.00.1412171704530.4549@keflavik>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QAYp1gNWWz-7sMyw8ABzZn2eLG4
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:23:07 -0000

On Wed, Dec 17, 2014 at 05:10:08PM -0800, Jan Pechanec wrote:
> On Wed, 17 Dec 2014, Nico Williams wrote:
> >> 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 

This might be the reason to use slot-id in your case: that any token
reader device could claim to be a "Sun Metaslot" even though it's not.

When you know that slot #0 is is the "Sun Metaslot" then you can be more
certain that you're getting the "Sun Metaslot" than if you use the slot
label.

> 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 agree now.

> 	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.

Thanks,

Nico
--