Re: [lamps] [EXTERNAL] Re: I-D Action: draft-ietf-lamps-im-keyusage-00.txt

[Rohan Mahy <[e-mail]>]

I used to work for Wire. Wire added custom automated cert enrollment to
Smallstep's step-ca (an open-source certificate authority and enrollment
server), and bundles it with Wire server. Adding this extended key usage
could be deployed in step-ca solely via a change in certificate template
configuration, and would satisfy concerns raised by specific customers.
Requiring the extended key usage would require a small change to the client
validation code.

MIMI will soon start considering specific credential formats, with X.509
and W3C Verifiable Credentials being two obvious contenders. If we use
X.509, I believe this extended key usage will be a useful addition to the
toolbag. Time will tell.

Thanks,
-rohan

On Wed, Apr 17, 2024 at 1:54 PM Salz, Rich <[e-mail]> wrote:

> The target usage of an IM identity is not TLS, it is end-to-end encryption
> applications where a user or client (say Alice) wants to verify the
> identity of another user or client (say Bob), and often have no transport
> encryption link to.
>
>
>
> Oops.  Yes, of course.  Sorry for the noise.
>
>
>
> And still would like a reply to my more first question: Have any IM
> providers/vendors/open-source groups said they are interested in deploying
> this?
>
>
>
>
>