Proposal for CT Operator-published log metadata

[Clint Wilson]

Hello all!

Building on the fantastic work that’s occurred over the last year to provide more robust information about the state of CT Logs, such as https://googlechrome.github.io/CertificateTransparency/inclusion_request_schema.json and https://github.com/FiloSottile/sunlight/commit/49406f3a7f9339c4554ed0f94db6d2e8f2e46575, we want to propose a further evolution of CT Log metadata published by Log Operators to support additional automation within the CT Ecosystem.

The proposal is shared here: https://docs.google.com/document/d/1KIBO8OjTHcmf6e2OsEGYanovC9LWIQL6sS9N8XODmt4 and should be publicly accessible and allow comments from anyone.

We’d love to hear your thoughts on this proposal, from Log Operators, Monitors, technology maintainers, Log Programs, and interested parties or other stakeholders.

Thank you!

-Clint

[Matthew McPherrin]

In order to be able to try out the schemas and read them in something with nicer indentation than the doc, I've checked the schemas and examples into a repository at https://github.com/mcpherrinm/ctmeta

There is also a schema verification tool included now, and depending on how the discussion goes, may add a few more small tools for working with these files.

--
You received this message because you are subscribed to the Google Groups "Certificate Transparency Policy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ct-policy+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/ct-policy/32B00CE7-D981-4253-A18C-5AB45EC1ECCA%40apple.com.