You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"body": "* Simplify language for right-shift loops at 1.4.3 and 2.6.2.3. `sn` must be non-zero entering each of the loops, so the `sn = 0` exit condition can never occur.\r\n* Move 'until' to the start of the loop lines to clarify that the condition should be checked before entering the loop. The previous language (inherited from RFC 9162) is slightly more ambiguous and could be interpreted as right-shifting and _then_ checking the condition.\r\n* Make some other minor formatting tweaks and use language similar to RFC 9162 for the comparisons at the end.",
"body": "*Conditional on this not causing a lot of list drama*, I don't mind this adding this. However, keep in mind that, the work here is already unavoidably extensible to what you're trying to do. If it can bind a TBSCertificate and the TBSCertificate is constructed by the log operator, it can be extended. It's just how X.509 non-critical extensions work.\r\n\r\nAnd, of course, there is an inherent extension point here: the things the RP trusts. You can always make a new CAs that implement different signature algorithms, etc. Indeed that's the very extension point we're looking to use here. The lack of extension point has never been the limiting factor here.",
8259
+
"createdAt": "2025-08-30T22:22:31Z",
8260
+
"updatedAt": "2025-08-30T23:20:40Z"
8261
+
},
8262
+
{
8263
+
"originalPosition": 5,
8264
+
"body": "New sentence seems reasonable, but, per comments on other PR and our discussion, losing the \"batching techniques\" sentence loses what the text was trying to communicate. Without it, the discussion about involving the CA in tree construction doesn't make sense. The request was to integrate the text you wanted to add, without breaking core meaning of the text.\r\n\r\nI've gone ahead and done that below:\r\n\r\n```suggestion\r\nThe PLANTS Working Group will define a mechanism that integrates log construction into certificate issuance, and reduces the amount of data in individual log entries and the TLS handshake. Integrating the log into certificate issuance enables techniques where one signature can cover multiple key/identifier bindings, e.g. by signing Merkle Tree hashes.\r\n```",
0 commit comments