Hey everyone,
I've started writing a RFC for capability URIs a few weeks ago, and after a first round of very interesting feedbacks, I think it's starting to get close to complete, so I'd love your opinion.
https://kephas.github.io/cap-uri/
It features an evolution of web-keys and explanations of attenuation, revocation and responsibility tracking. I tried to find a balance to explain some capability security basics without going into too much details.
I wonder if some areas may need fleshed out examples (like the interaction between storage and photo annotation service in the section about attenuation).
I also wonder if I should mention proof of possession? Maybe adding UCAN as a token format could be a simple and existing way to provide proof of possession, as UCANs delegations are separate from UCANs' invocations…
Curiously,
Pierre Thierry
--
pie...@nothos.net 0xD9D50D8A