Questions re: Upcoming changes to revocation reasons

[Osiris]

@aarongable

3. Requests for revocation which are authenticated using the key of the Subscriber who originally ordered the certificate will be able to request reason "keyCompromise". Previously, only requests authenticated using the certificate's private key could request this reason. However, requests for revocation with reason "keyCompromise" but which do not demonstrate said compromise will not result in the key being blocklisted from future issuance, nor result in all other certificates which share that key also being revoked for the same reason.

I'm not sure this is allowed in the current baseline requirements? 4.9.1.1 item 3 states:

3. The CA obtains evidence that the Subscriber’s Private Key corresponding to the
   Public Key in the Certificate suffered a Key Compromise;

If I revoke my cert with keyCompromise, how is that not "evidence"? The BR do not state I need to "demonstrate" controle over the key. It just states "evidence". And I think the revocation reason keyCompromise is evidence enough?