SC-1XX EVG Cleanup and BR Sync - #680
richardwsmith wants to merge 1 commit into
Conversation
| | UTC(k) | National realization of Coordinated Universal Time | | ||
|
|
||
| ### 1.6.3 References | ||
|
|
There was a problem hiding this comment.
I suggest to add "No stipulation." instead of leaving the section blank.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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. 😉
|
|
||
| **CA Key Pair**: A Key Pair where the Public Key appears as the Subject Public Key Info in one or more Root CA Certificate(s) and/or Subordinate CA Certificate(s). | ||
|
|
||
| **Canonical Date Representation**: A date that is formatted as YYYY-MM-DD, where "YYYY" is the four-digit year, "MM" is the two-digit month, and "DD" is the two-digit day of the month. Each element of the date is separated with a single hyphen-minus "-" (0x2D (ASCII), U+002D (UTF-8)). Each element is padded with leading zeroes as needed to ensure that year values consist of four digits and month and day of the month values consist of two digits. Example dates in this representation: "0748-04-02", "2024-10-14". |
There was a problem hiding this comment.
Is this date format being used instead of ISO 8601 for simplicity? 8601 is pretty universal, but it has some subtle complexity that may not be warranted here.
3 participants
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.