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

RE: Latest ipsec-pki-req-04.txt


Greg Carter wrote:
> Hi,
> 3.1 The extendedKeyUsage field
> Maybe I missed it, but did anybody respond why the 
> extendedKeyUsage MUST
> contain only the
> object identifier iKEIntermediate?
> This now means all ipsec entities require a special ipsec cert.  

Perhaps I missed this also.  Some reasoning as to why ONLY the
iKEIntermediate OID can be present in an end entity cert would be great.  

> A. Obtaining a Certificate for a Device
> "Regardless of the protocol used, a CA who gets an IKE system's
> enrollment request that includes the subject and 
> subjectAltName desired
> for the device MUST include exactly the same subject and 
> subjectAltName
> in the certificate."
> As I have said before this will require that a user type in 
> the DN at some
> console somewhere and get it right.  I don't see the need for this
> restriction.  I believe the subject can be modified by the CA in CMP
> (rfc2510).  

I agree completely. 

> A.1 Enrollment requests with PKCS10 plus out of band information
> I am glad this has been spelt out, however it should be 
> mentioned here or in
> the security considerations section that a hash (fingerprint) 
> of the ASN.1
> DER encoded p10 message be done and made available to the operator for
> verification with the CA.

Agree here also.  

In addition I'd like to clarify the following section of appendix A.1

".... In addition to CMP and CMC, there are
at least two other non-IETF protocols that have been used by a number
of IPsec vendors and CAs.

The IPsec market has coalesced around one method of enrollment that is
not fully defined anywhere other than this document. That method can be
called "PKCS10 plus out of band" or "P10POUB", described below. All
IKE systems that need to obtain a certificate for the public key MAY
do P10POUB, and MAY do CMP and/or CMC in the near future."

You will find that CMC has fully defined the P10POUB method described.  In
fact, one of the main goals of CMC was to standardize and define the use of
a simple PKCS#10 and PKCS#7 message for certificate enrollment.  It is known
as the "simple PKI request/response" method in CMC.