Note entirely clear if this is a feature request or bug.

Use case:
One of the methods that LDAP allows to authenticate is X509 client authentication.
Part of the access control mandates setting multiple DC fields in the certificate as well as multiple OUs potentially.
The DC field is commonly included as of the standard definition of DN
https://www.ibm.com/docs/en/ibm-mq/7.5?topic=certificates-distinguished-names

It is also mentioned within tge RFC, but only in the context of LDAP and not under the official Subject spec
https://www.rfc-editor.org/rfc/rfc5280.txt

Problem:
In the current certificate spec it is not possible to set a single DC , yet again multiple which is needed for the LDAP client certificate.

If not mistaken, setting multiple OU or DC fields would also have this bug #3203

DC doesn't feature in subject section in spec (4.1.2.6), which is probably why it doesn't appear in pkix.Name type used for the field.
That type allows setting other extra names as a contingency for these commonly used names, it would be great if we could map DCs and multiple OUs as well.

/kind feature