Skip to content

SC-XXX: Set presence of AIA extension to SHOULD for Subscriber Certificates. #665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
e3n0 wants to merge 5 commits into
base: main
Choose a base branch
from
+2 −2
Open

SC-XXX: Set presence of AIA extension to SHOULD for Subscriber Certificates. #665

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
de19a70
Set presence of id-ad-caIssuers and AIA extension to MAY.
e3n0 May 6, 2026
a5ae9a3
Update AIA to may in 7.1.2.7.6.
e3n0 May 6, 2026
56dd621
Update AIA to MAY for other certificates as well.
e3n0 May 6, 2026
621a3c4
Limit change to AIA to subscriber certificates.
e3n0 May 6, 2026
d3fc033
Update to make AIA SHOULD, keep caIssuers a SHOULD.
e3n0 Jun 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/BR.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2791,7 +2791,7 @@ In addition, `subject` Attributes MUST NOT contain only metadata such as '.', '-

| **Extension** | **Presence** | **Critical** | **Description** |
| --------------------------------- | ----------- | ------------ | -------------------------------------- |
| `authorityInformationAccess` | MUST | N | See [Section 7.1.2.7.7](#71277-subscriber-certificate-authority-information-access) |
| `authorityInformationAccess` | SHOULD | N | See [Section 7.1.2.7.7](#71277-subscriber-certificate-authority-information-access) |
| `authorityKeyIdentifier` | MUST | N | See [Section 7.1.2.11.1](#712111-authority-key-identifier) |
| `certificatePolicies` | MUST | N | See [Section 7.1.2.7.9](#71279-subscriber-certificate-certificate-policies) |
| `extKeyUsage` | MUST | N | See [Section 7.1.2.7.10](#712710-subscriber-certificate-extended-key-usage) |
Expand All @@ -2811,7 +2811,7 @@ In addition, `subject` Attributes MUST NOT contain only metadata such as '.', '-

##### 7.1.2.7.7 Subscriber Certificate Authority Information Access

The `AuthorityInfoAccessSyntax` MUST contain one or more `AccessDescription`s. Each `AccessDescription` MUST only contain a permitted `accessMethod`, as detailed below, and each `accessLocation` MUST be encoded as the specified `GeneralName` type.
If present, the `AuthorityInfoAccessSyntax` MUST contain one or more `AccessDescription`s. Each `AccessDescription` MUST only contain a permitted `accessMethod`, as detailed below, and each `accessLocation` MUST be encoded as the specified `GeneralName` type.

The `AuthorityInfoAccessSyntax` MAY contain multiple `AccessDescription`s with the same `accessMethod`, if permitted for that `accessMethod`. When multiple `AccessDescription`s are present with the same `accessMethod`, each `accessLocation` MUST be unique, and each `AccessDescription` MUST be ordered in priority for that `accessMethod`, with the most-preferred `accessLocation` being the first `AccessDescription`. No ordering requirements are given for `AccessDescription`s that contain different `accessMethod`s, provided that previous requirement is satisfied.

Expand Down