Thanks for the comment. The I-D describes how to add VCs as a certificate type in TLS while maintaining the interoperability with other certificates. The aim is to move SSI-based authentication from the application layer down to TLS without changing the way SSI and TLS work. The SSI model (based on the use of VC [0] and DIDs [1]) specifies the use of DLT (or more generally Verifiable Data Registry) to store and retrieve public keys. We will clarify this point in the abstract and introduction of the next version.
Andrea Vesco [0] https://www.w3.org/TR/vc-data-model-2.0/ [1] https://www.w3.org/TR/did-core/ > On 19 Feb 2024, at 13:40, Yanlei(Ray) <ray.yan...@huawei.com> wrote: > > The motivation for your design needs to be described in the draft. > Why do you want to put the public key in the distributed ledger? > > Lei YAN > > -----Original Message----- > From: Uta <uta-boun...@ietf.org> On Behalf Of Andrea Vesco > Sent: Monday, February 19, 2024 4:57 PM > To: uta@ietf.org > Subject: [Uta] New I-D on VC and TLS > > L.Perugini and I have written an I-D on the use of Verifiable Credential (VC) > as a new means of authentication in TLS. We think it might be of interest > and in the scope of the UTA WG. > > Could you please give us your opinion? > > Draft > Datatracker https://datatracker.ietf.org/doc/draft-vesco-vcauthtls/ > Github https://github.com/Cybersecurity-LINKS/draft-vesco-vcauthtls > > Kind Regards, > Andrea Vesco > _______________________________________________ > Uta mailing list > Uta@ietf.org > https://www.ietf.org/mailman/listinfo/uta _______________________________________________ Uta mailing list Uta@ietf.org https://www.ietf.org/mailman/listinfo/uta
