-
Notifications
You must be signed in to change notification settings - Fork 122
Fix formatting in table 1.2.1 #613
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.
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wthayer-fastly
approved these changes
Aug 27, 2025
wthayer
approved these changes
Aug 27, 2025
dzacharo
added a commit
that referenced
this pull request
Oct 17, 2025
* SC-081: Introduce Schedule of Reducing Validity and Data Reuse Periods (#553) * Introduce Schedule of Reducing Validity and Data Reuse Periods * Expand Section 4.2.1 to detail allowed data reuse periods for validation data (both for domains/IPs and for everything else in 3.2) * Overall reduction of non-SAN validation reuse from 825 to 366 days * Overall reduction of SAN validation reuse from 398 days to 10 days * Expand section 6.3.2 to detail schedule of reducing maximum validity periods in coming years * Overall reduction of maximum valdiity period from 398 days to 45 days * Update Table Row header Fix copy/pasted table row header * Update SC-081 * Shift dates to March * Align on 3 dates for changes to take effect (2026, 2027, 2028) * Address various comments with corrections to wording * Update table formatting (to hopefully produce better-looking headings in the PDF output) * Update Tables * Update Table headings in 4.2.1 * Add "days" to tables for clarity * Remove 1 September 2020 date to align with table * Fix capitalization Remove erroneous capitalization of "Validation Data Reuse Periods" * Increase SII reuse period * Update table in Section 3.2.1 for "Subject Identity Information validation data reuse periods" to increase the Maximum data reuse period after March 15, 2026 from 366 days to 398 days. * Shift timeline of Validity Period * Move the reduction from 100 days maximum Validity Period to 47 days maximum Validity Period back by 1 year (from March 15, 2028 to March 15, 2029) * This change is based on discussion in the Servercert-wg call on Feb 13, 2025 and on-list for ballot SC-081. * Fix other 47-day timeline dates * Delay 10 day DCV reuse date Based on discussion in the Feb 27, 2025 SCWG meeting, this commit pushes the enforcement date for reducing the maximum reuse period of domain validation to 10 days from March 15, 2028 to March 15, 2029 -- aligning with the date for reducing the maximum validity period of certificates to 47 days. * Fixing workflow file Updating build-draft-docs.yml to match main * Introduce Schedule of Reducing Validity and Data Reuse Periods * Expand Section 4.2.1 to detail allowed data reuse periods for validation data (both for domains/IPs and for everything else in 3.2) * Overall reduction of non-SAN validation reuse from 825 to 366 days * Overall reduction of SAN validation reuse from 398 days to 10 days * Expand section 6.3.2 to detail schedule of reducing maximum validity periods in coming years * Overall reduction of maximum valdiity period from 398 days to 45 days * Update Table Row header Fix copy/pasted table row header * Update SC-081 * Shift dates to March * Align on 3 dates for changes to take effect (2026, 2027, 2028) * Address various comments with corrections to wording * Update table formatting (to hopefully produce better-looking headings in the PDF output) * Update Tables * Update Table headings in 4.2.1 * Add "days" to tables for clarity * Remove 1 September 2020 date to align with table * Fix capitalization Remove erroneous capitalization of "Validation Data Reuse Periods" * Increase SII reuse period * Update table in Section 3.2.1 for "Subject Identity Information validation data reuse periods" to increase the Maximum data reuse period after March 15, 2026 from 366 days to 398 days. * Shift timeline of Validity Period * Move the reduction from 100 days maximum Validity Period to 47 days maximum Validity Period back by 1 year (from March 15, 2028 to March 15, 2029) * This change is based on discussion in the Servercert-wg call on Feb 13, 2025 and on-list for ballot SC-081. * Fix other 47-day timeline dates * Delay 10 day DCV reuse date Based on discussion in the Feb 27, 2025 SCWG meeting, this commit pushes the enforcement date for reducing the maximum reuse period of domain validation to 10 days from March 15, 2028 to March 15, 2029 -- aligning with the date for reducing the maximum validity period of certificates to 47 days. * Fixing workflow file Updating build-draft-docs.yml to match main * Update version number and recent changes. --------- Co-authored-by: dzacharo <dzacharo@yahoo.com> * Bump workflow versions (#581) * Bump workflow versions * Set fetch-depth for changelog * Bump action workflow version * SC-081: Introduce Schedule of Reducing Validity and Data Reuse Periods Fixed table format * Fix formatting and effective date in section 1.2.2 (#595) * Fix formatting in 3.2.2.9 * Fix numbering in 5.4.1 * Fix effective date in 1.2.2 * SC-085: Require Validation of DNSSEC (when present) for CAA and DCV Lookups (#579) * require DNSSEC * SHOULD to MAY Co-authored-by: Dimitris Zacharopoulos <dzacharo@users.noreply.github.com> * RFCs in sec 1.6.3. * Improved RFC 6840 reference * added effective dates and changed other should to may. * change ICANN DNSSEC root to IANA DNSSEC root * Added updates in response to CBonnell suggestions. * states typo fix * Using dzacharo 's proposed wording for SHOULD EDNS buffer size. * changed RFC 4035 reference to Section 5. * wording change * Updated effective date to March 15th, 2026 * explicitly omit DNSSEC validation from Section 8.7 self audits per @geegeea's proposal Co-authored-by: Gurleen Grewal <gurleen.grewal@gmail.com> * add exclusion to self audit for DCV DNSSEC checks Co-authored-by: Gurleen Grewal <gurleen.grewal@gmail.com> --------- Co-authored-by: Dimitris Zacharopoulos <dzacharo@users.noreply.github.com> Co-authored-by: Gurleen Grewal <gurleen.grewal@gmail.com> * SC085: Require Validation of DNSSEC (when present) for CAA and DCV Lookups (#606) * Update version number, recent changes and relevant dates * fix version * SC-089: Mass Revocation Planning (#611) * SC-089: Mass Revocation Planning (#610) * Initial draft of 5.7.1.2 Here is an initial draft of a proposal to add section 5.7.1.2 to the TLS Baseline Requirements. See Issue #602 * Added CPS Compliance Date Added a CPS compliance date of Dec. 1, 2025 --------- Co-authored-by: Ben Wilson <63610154+BenWilson-Mozilla@users.noreply.github.com> * Updated version number and relevant dates. * Fix formatting --------- Co-authored-by: Ben Wilson <63610154+BenWilson-Mozilla@users.noreply.github.com> * Fix formatting in table 1.2.1 (#613) --------- Co-authored-by: Clint Wilson <clint@wilsonovi.com> Co-authored-by: Paul van Brouwershaven <vanbroup@users.noreply.github.com> Co-authored-by: Henry Birge-Lee <henrybirgelee@gmail.com> Co-authored-by: Gurleen Grewal <gurleen.grewal@gmail.com> Co-authored-by: Ben Wilson <63610154+BenWilson-Mozilla@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.