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