Re: [lamps] Last Call: <draft-ietf-lamps-hash-of-root-key-cert-extn-02.txt> (Hash Of Root Key Certificate Extension) to Informational RFC

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

 




> On Jan 10, 2019, at 2:15 PM, Salz, Rich <rsalz@xxxxxxxxxx> wrote:
> 
>> If both checks succeed, then the potential Root CA certificate is
>> added to the trust anchor store and the current Root CA certificate is
>> removed.
> 
> I suggest adding "after an appropriate amount of time (such as no old certificate chains being in use)."
> 
> Does that solve the issue?

There are two cases.  In one case, there is an enterprise directory system, and there is no concern with the discovery of the old-in-new and the new-in-old certificates. The old certificate can be removed without any concerns in this situation.  In the second case, there is no appropriate directory, and keeping the old certificate for some amount of time would prevent the issue raised by DKG.

Russ





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux