-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -171,7 +171,7 @@ In this scenario delegation issued by the [`did:mailto`] identifier MAY be signe | |
|
||
If delegation is signed with _attestation signature_, but is not accompanied with [UCAN attestation] from trusted [authority] it MUST be considered invalid. In this scenario implementer MAY initiate interactive verification flow and issue [UCAN attestation] retroactively instead of denying service. | ||
|
||
> When received delegation is issued by the `did:mailto:web.mail:alice`, signed with _attestation signature_, but is not accompanied by [ucan attestation], receiver could iteratively confirm authorization by sending an email to `[email protected]` address with a confirmation link, which when followed issues [attestation] from the receiver resuming the invocation. | ||
> When received delegation is issued by the `did:mailto:web.mail:alice`, signed with _attestation signature_, but is not accompanied by [UCAN attestation], receiver could iteratively confirm authorization by sending an email to `[email protected]` address with a confirmation link, which when followed issues [attestation] from the receiver resuming the invocation. | ||
#### Attestation Signature Format | ||
|
||
|