You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the specification is not clear how the two following requirements could interlace:
contain the expiration datetime after which it SHOULD NOT be considered valid anymore and it MUST NOT be greater than the one contained in the Digital Credential which it refers to; Link
have a validity period not greater than 24 hours; Link
For example if the expiration datetime would be set after 30days and validity period set after 12 hours, it's not clear if the Status Attestation, while being valid (expiration datetime) cannot be used after the validity time (expired validity)
The text was updated successfully, but these errors were encountered:
pietroACN
changed the title
[Credential Lifecycle - Status Attestation ] - Functional Requirements
[Credential Lifecycle - Status Attestation ] - Functional Requirements - Status Attestation
Apr 16, 2024
status attestations are short lived and cannot expire after the expiration of the credential where they are bound to, eg: credential expires in the next 5 hours, the linked status attestation cannot expire after the next 5 hours.
expiration is part of the validity evaluation, while validity is a more complex concept that brings signature verification, revocation verification, issuer revocation and so on.
From the specification is not clear how the two following requirements could interlace:
For example if the expiration datetime would be set after 30days and validity period set after 12 hours, it's not clear if the Status Attestation, while being valid (expiration datetime) cannot be used after the validity time (expired validity)
The text was updated successfully, but these errors were encountered: