Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion charter-ietf-plants.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The PLANTS Working Group will define a mechanism that integrates log constructio

The Working Group will initially put down roots and define the mechanisms needed to interoperably construct and consume certificates:

1. A transparency log structure, maintained by a CA, containing the key/identifier bindings that the CA has certified.
1. An externally monitorable transparency log structure, maintained by a CA, containing the key/identifier bindings that the CA has certified.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This prompts a few unanswered questions, but I think that's a good thing (i.e. let's leave them unanswered for the WG):

  • External to whom? I think the obvious answer is "the public can monitor", but private PKIs might have a more nuanced answer, so leaving that to the deployment seems solid
  • How is it accessed? Is it the CA that guarantees access or mirrors or both? Does the spec have an opinion on this or do we leave it to deployments?


2. Certificate constructions to prove to relying parties that a binding is both in the CA's view of the log and externally monitorable.

Expand Down