[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Straw poll for Algorithm Identifiers in Subject Public Key Info.

To: "Kemp, David P." <DPKemp@xxxxxxxxxxxxxx>
Subject: RE: Straw poll for Algorithm Identifiers in Subject Public Key Info.
From: Daniel Brown <DBrown@xxxxxxxxxxxx>
Date: Tue, 16 Jan 2007 16:03:10 -0500
Cc: ietf-pkix@xxxxxxx
In-reply-to: <FA998122A677CF4390C1E291BFCF598906677CB2@xxxxxxxxxxxxxxxxxxx>
List-archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-id: <ietf-pkix.imc.org>
List-unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
Sender: owner-ietf-pkix@xxxxxxxxxxxx

David P. Kemp wrote on 01/16/2007 12:21:27 PM: > > > - The structured algorithm OID is maybe not the hardest to define > > but the worse alternative in every other aspect. > > Agree. >
Suppose that a subject has an ECMQV-only cert, and wishes to allow either SHA-256 or SHA-384 based KDFs, but no other KDFs. Also, the EKU field says that the cert can be used for SMIME, IPSec, SSH, or TLS (suppose the private key is on the user's smart card). The X9.62 "structured" approach allows for this. How would the other approaches allow for this?

Regards,

Dan Brown (905) 501-3857 http://www.certicom.com

Follow-Ups:
- RE: Straw poll for Algorithm Identifiers in Subject Public Key Info.
  - From: Kemp, David P.
- RE: Straw poll for Algorithm Identifiers in Subject Public Key Info.
  - From: Stefan Santesson

References:
- RE: Straw poll for Algorithm Identifiers in Subject Public Key Info.
  - From: Kemp, David P.

Prev by Date: decdBAGG
Next by Date: RE: Straw poll for Algorithm Identifiers in Subject Public Key Info.
Previous by thread: RE: Straw poll for Algorithm Identifiers in Subject Public Key Info.
Next by thread: RE: Straw poll for Algorithm Identifiers in Subject Public Key Info.
Index(es):
- Date
- Thread