Skip to content

Commit

Permalink
Additional Text about Subject Name
Browse files Browse the repository at this point in the history
The problem is that RFC 5280 says that the subject name is contained in the subject field and/or the subjectAltName extension. The ASN.1 does not seem to support the case that the subject field is optional
  • Loading branch information
hannestschofenig authored Sep 3, 2024
1 parent 43d6647 commit d195217
Showing 1 changed file with 7 additions and 5 deletions.
12 changes: 7 additions & 5 deletions draft-ietf-uta-tls13-iot-profile.md
Original file line number Diff line number Diff line change
Expand Up @@ -481,17 +481,19 @@ MUST NOT be marked critical.

This section outlines the requirements for root CA certificates.

## subjectName
## Subject

{{!RFC5280}} defines the subjectName field as follows: "The subject field identifies
the entity associated with the public key stored in the subject public key
field." RFC 5280 adds "If the subject is a CA then the subject field MUST be
Section 4.1.2.6 of {{!RFC5280}} defines the subject field as follows: "The subject field identifies
the entity associated with the public key stored in the subject public key field. The subject name
MAY be carried in the subject field and/or the subjectAltName extension."

RFC 5280 adds "If the subject is a CA then the subject field MUST be
populated with a non-empty distinguished name matching the contents of the
issuer field in all certificates issued by the subject CA."

Root CA certificates MUST have a non-empty subjectName.

The subjectName MUST contain the commonName, the organizationName, and the countryName attribute and MAY contain an organizationalUnitName attribute.
The subjectName MUST contain the commonName, the organizationName, and the countryName attribute and MAY contain an organizationalUnitName attribute.

### Authority Key Identifier

Expand Down

0 comments on commit d195217

Please sign in to comment.