[saag] wpkops, "WebPKI" and citations
Michael Richardson <[email protected]> Mon, 17 Nov 2025 13:44:13 -0500
| Newsgroups | gmane.ietf.saag |
|---|---|
| Message-ID | <[email protected]> |
A decade ago an attempt was made to charter a wpkops WG. I don't think it got off the ground, and I'm not proposing to restart that. What I would like is a consensus way to describe the nebulous, not really a thing, that we call the WebPKI. It's not *A* thing, but rather a set of loosely coordinate trust anchor stores in commodity operating systems and browsers. We often need to talk about this, and I don't think we have a good definition/reference that we can cite. Olle Johansson and I have been struggling with this, and he noticed: > https://www.ietf.org/archive/id/draft-ietf-tls-cert-abridge-02.html > doesn’t explain the term, even though it’s in the title. In my case, I want to discuss how we can have name "collisions", a la Comodogate, and how this has partly driven CT. And how private PKIs introduce further challenges. I would expect that anything I write in an I-D is gonna be challenged by at least two reviewers and one AD. So I'm asking in advance. I poked around cabforum.org, and I think that they try very hard not to say anything, probably for the same anti-trust reasons that caused the forum to exist. -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide _______________________________________________ saag mailing list -- [email protected] To unsubscribe send an email to [email protected]
signature.asc
(application/pgp-signature, 487 B)
-----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmkbbP0ACgkQgItw+93Q 3WVKFggAhQ/kgsJhl0+nn/UEr6B14DDhPVoL3Ei7L9axlvFyHFgtdC0f0YaElW9Q 95t3l1MGJ5EDqqXC+ZZLIoRozhPHLyhrEU24pCE1/tfC/GsgzFwHGCeJw3ZhPXB7 GVe0gGcRfTCAF0BD8qgOb9VINzZQYY3R98Tlf7PHQ0dq2m5tyqBn7weMAe2oOLen gXi/ubOTJFPMJEE5x6TIqPqfVGQqc9vCwqXtG/qhkkSLyW0NJIoHgofdiymIAI0y dT3TvanNp/GI1ffWE6t613pyqPLMh9FnRLtgTKZ3bQgS2smTBIInInt5pznA8eCp aAVhWIE2S4R9b2VT9Gw/+4GiGNTYXA== =lcPd -----END PGP SIGNATURE-----