FF135 Certificate Transparency#37812
Conversation
|
Preview URLs External URLs (3)URL:
URL:
(comment last updated: 2025-01-27 00:08:18) |
| Browser implementations are based on the obsoleted specification {{rfc("6962","Certificate Transparency")}} (January 2025). | ||
| The current specification is {{rfc("9162","Certificate Transparency Version 2.0")}}. |
There was a problem hiding this comment.
This bit fixes #35570 by noting the spec things are implemented on and the current version.
Note, I'd do this with spec-urls metadata but they shows unknown specs for both.
I'm also in discussion with BCD team about whether the version data can go into BCD, which IMO would be better.
There was a problem hiding this comment.
whether the version data can go into BCD, which IMO would be better.
This would be great
bsmth
left a comment
There was a problem hiding this comment.
Leaving a +1 and we can follow-up with spec_urls or BCD 👍🏻
Should we add a TODO in 37811 so we don't forget?
|
@bsmth Thanks. The TODO is effectively the BCD note in 37811 - I'm waiting on a slack response. If I don't get one then there will be no BCD and this won't change. So merging. If we do get one then I'll create a new PR with the tidy. The point you know I've given up on BCD is when I mark dev-docs-complete in the tracking issue. |
FF135 provides support Certificate Transparency. This adds a release note and minor updates to the CT doc.
Fixes #35570
Related docs work can be tracked in #37811