Skip to content

non normative language around revocation policies.#301

Open
andorsk wants to merge 1 commit into
ask/update_linksfrom
andorsk-patch-2
Open

non normative language around revocation policies.#301
andorsk wants to merge 1 commit into
ask/update_linksfrom
andorsk-patch-2

Conversation

@andorsk

@andorsk andorsk commented May 15, 2024

Copy link
Copy Markdown
Collaborator

Addresses #138. To discuss over next call.

@andorsk andorsk changed the title ask/update_revocation non normative language around revocation policies. May 15, 2024
@andorsk

andorsk commented May 15, 2024

Copy link
Copy Markdown
Collaborator Author

add in additional language in the companion guide to add further information or reference the original issue.

@andorsk andorsk added the stage: needs review needs review label Sep 4, 2024
@andorsk andorsk marked this pull request as ready for review September 4, 2024 14:40
@andorsk

andorsk commented Sep 4, 2024

Copy link
Copy Markdown
Collaborator Author
  • decision : revocation is explicit or implicit permission.
  • Liran : Reference implementation does not do chained delegation.
  • Revoking direct delegations only doesn't cover common enterprise case
  • Make revocation an explicit permission. UCAN adopted.
  • Is it a v0.0.1 or v0.0.2 problem.
  • Breaking change.

TODO: add more examples, speak specifically to construct to the spec.

@andorsk andorsk requested a review from LiranCohen September 4, 2024 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant