W3C home > Mailing lists > Public > public-credentials@w3.org > January 2022

RE: Verifiable Credential Refresh 2021

From: John, Anil <anil.john@hq.dhs.gov>
Date: Mon, 3 Jan 2022 20:39:02 +0000
To: W3C Credentials CG <public-credentials@w3.org>
Message-ID: <SA1PR09MB8815F54BC6F39A7DFB155638C5499@SA1PR09MB8815.namprd09.prod.outlook.com>
>Verifiable Credentials can expire. 
>It is useful to provide instructions on refreshing the credential for the times when expiration is imminent or has already occurred. 
>The refresh can be performed manually or, with the prior consent of the credential holder, automatically.

Happy New Year!

Good to see more work and thought being put into this so that this can be standardized!

Manu -- could you provide a perspective on the flexibility/optionality/signaling of support for these capabilities by the issuer?

Context -- In the work we (U.S. Citizenship and Immigration Services which is a DHS Operational Component) are doing in the issuance of digital personal/immigration credentials (U.S. Permanent Resident Card, U.S. Employment Authorization Document etc.), we made a concrete/explicit decision that our Issuer infrastructure *WILL NOT* support a refresh request coming directly from the Verifier as it removes "... control and consent from the holder and allow the verifiable credential to be issued directly to the verifier, thereby bypassing the holder"  (as per VC Data Model Section 5.5 Note).  We explicitly require the Holder to be in the loop for such a request for privacy, accountability and business process reasons.

Is there some manner of an indicator/signal that is part of this refresh request that can be implemented by the Issuer to notify the a caller of what we support and what we do not?

Best Regards,

Anil

Anil John
Technical Director, Silicon Valley Innovation Program 
Science and Technology Directorate 
US Department of Homeland Security 
Washington, DC, USA 

Email Response Time – 24 Hours
Received on Monday, 3 January 2022 20:39:35 UTC

This archive was generated by hypermail 2.4.0 : Monday, 3 January 2022 20:39:37 UTC