About a behavior if multiple accounts are associated with the same domain

Thank you for replying!

But I found that domain validation was required to the old account

The old account means the first account to issue a certificate.

In the question, Any reference about not needing validation after renewing a cretificate?, the certificate is renewed (replaced). There is only one account.

But, here in this question, It differs in that there are multiple accounts.

Let me describe the detail chronologically:

  1. The certificate A was issued to a domain by Let's encrypt account A.
  2. The certificate B was issued to the domain by Let's encrypt account B.
  3. The certificate C was issued to the domain by Let's encrypt account A.

In the step 3, It was needed to perform domain validation for the domain even though it was already done in the step 1.

Therefore, I think domain validation for the same domain which was performed previously is abolished. Is this true?

And if yes, as I explained earlier,

Is this behavior derived from the service specification of Let’s encrypt?

Or, is there any reference such as IETF draft describing about this?
(As long as I looked up, I couldn’t find any helpful references.)