Capability revocation

[Alan Karp]

I made a comment in the Distributed Web Node (DWN) discussion list that revocation is something that is better to think about earlier in the design process than later.  Since I opened my big yap, I've not been tasked with explaining what I mean.

I think I should start with the various options.  I came up with 

1. No revocation; rely on short-lived capabilities.
2. Revocation is a specific permission.
3. The holder of a capability can revoke it.
4. The delegator of a capability can revoke any direct delegations.
5. The delegator of a capability can revoke any delegation deeper in the chain.
6. For certificate-based capabilities, revoke the public key it's issued to.

What did I miss?

--------------
Alan Karp

[Mark S. Miller]

Is Caretaker, Membrane, Horton all covered by #2?

--
You received this message because you are subscribed to the Google Groups "cap-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cap-talk+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/CANpA1Z2%3DFJyy-3H5VqRKuxfRhojUaS0rGmWwNtUQMwT6Go2a3A%40mail.gmail.com.

--

  Cheers,
  --MarkM

[Alan Karp]

That's my understanding.

--------------
Alan Karp

To view this discussion on the web visit https://groups.google.com/d/msgid/cap-talk/CAK5yZYjvSRCnPa5ZVCJJpHXVdT_AQ6oB7yeJ0LTXkS93F_7L-w%40mail.gmail.com.