I received a comment back in July from Tim Bruijnzeels that step 3 of the
keyroll document
that the document lacked details in step 3 of the described procedure and in
particular that
the procedure should note that step 3 includes the publication of the empty CRL
and the
initial manifest for the NEW CA.
In response to this comment I'd like to propose altering the document such that
step 3 of
the procedure as follows:
Current:
3. Request the entity's Issuer to generate and publish a NEW CA
certificate, with an issuer-selected Subject Name that is
distinct from the Subject Name used in the CURRENT CA
certificate for this entity.
Proposed:
3. Request the entity's Issuer to generate and publish a NEW CA
certificate, with an issuer-selected Subject Name that is
distinct from the Subject Name used in the CURRENT CA
certificate for this entity.
A more detailed view of this step is to:
- Wait for the superior CA to publish the NEW CA
certificate, and store the URL of the NEW CA's
publication point as the NEW CA's repository
publication point.
- Use the key pair associated with the NEW CA to generate
an initial empty CRL, and publish this CRL in the NEW
CA's repository publication point.
- Generate a new key pair, and form an associated EE
certificate request, with an AIA value of the NEW CA's
repository publication point, pass this EE certificate
request to the NEW CA, and mark the returned EE
certificate as the manifest EE certificate.
- Generate a manifest containing the published CRL as the
only entry, and sign it with the private key associated
with the manifest EE certificate, generate the CMS
signing object for the manifest which includes the EE
certificate and publish the manifest at the NEW CA's
repository publication point.
- If the NEW CA has opted to use a single-use EE
certificate for the manifest, discard the key pair
associated with the manifest EE certificate.
I'm unsure as to the appropriate level of detail of the description of this
procedure,
so I'm asking others for comments as to whether this proposed additional level
is
getting too far into the specific implementation details, or whether this
additional
information is helpful in the context of the document's overall purpose.
thanks,
Geoff
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr