Re: Verifiable Claims expiration

If you force an expiry date, issuers who don't want one will use an
arbitrary future date, e.g., 9999/12/31. The largest such number that
fits the typical inspector-verify test suite will rapidly become the de
facto setting for "no expiration".
Trying to force policy into the data model just wastes bytes.

-j


On Sat, Sep 16, 2017, at 11:55 PM, David Chadwick wrote:
> And from a security perspective this is flawed, since no cryptography> will last for ever
> 
> On 17/09/2017 01:07, Manu Sporny wrote:
>> On 09/16/2017 03:34 PM, Adam Sobieski wrote:
>>> I thought that omission of the expires property
>>> (https://w3c.github.io/vc-data-model/#expiration) results in an
>>> open-ended or non-expiring claim or statement.
>> 
>> This is correct.
>> 
>> We'll want to correct the spec text if it doesn't already say this.
>> 
>> -- manu
>> 
> 

--
Joe Andrieu, PMP
joe@joeandrieu.com
+1(805)705-8651
http://blog.joeandrieu.com