Skip to content

SC-1XX EVG Cleanup and BR Sync - #680

Open
richardwsmith wants to merge 1 commit into
cabforum:mainfrom
richardwsmith:SC-1XX--EVG-Cleanup-and-BR-Sync
Open

SC-1XX EVG Cleanup and BR Sync#680
richardwsmith wants to merge 1 commit into
cabforum:mainfrom
richardwsmith:SC-1XX--EVG-Cleanup-and-BR-Sync

Conversation

@richardwsmith

Copy link
Copy Markdown
Contributor

Redline for ballot SC-1XX (EVG Cleanup and BR Sync). The Guidelines for the Issuance and Management of Extended Validation Certificates (EV Guidelines) incorporate the Baseline Requirements by reference, so this ballot removes EV Guidelines text that duplicates, contradicts, or has fallen behind the Baseline Requirements, and migrates the Extended Validation (EV) certificate profile from EV Guidelines Section 7 into Baseline Requirements Section 7, including the subject attribute rules, the cabfOrganizationIdentifier extension, and Appendices G and H. The EV Guidelines that remain are a validation-methods document.

@richardwsmith
richardwsmith requested a review from a team as a code owner September 3, 2026 22:18
Comment thread docs/EVG.md
| UTC(k) | National realization of Coordinated Universal Time |

### 1.6.3 References

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest to add "No stipulation." instead of leaving the section blank.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, Roman. I don't disagree but it was decided years ago, for reasons I no longer recall, that CA/B Forum documents would simply leave blank sections blank. If we decide we want to change that I have no objection but would prefer that it be done by a singular "Add 'No stipulation'," ballot.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I wasn't aware of that decision. I just read the TLS BR 1.1 where it says: "However, rather than beginning with a “no stipulation” comment in all empty sections, the CA/Browser Forum is leaving such sections initially blank until a decision of “no stipulation” is made." and thought that this would be applicable here since we explicitly removed the refernces... But I'm in no way insisting. 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants