Re: Proposed XMPP Extension: XMPP Decentralized ID (XID)

Hey,

I am a little confused about what is the intended scope of a XID, that
is, what it is meant to identify? A device/resource? An entity? A user?
Multiple users? A human?

If we are fine with binding a XID to a specific device/resource, we
could "just" use the OMEMO public key for it. Then binding the XID to a
specific user in a cryptographically sane way would just be the same
issue as doing that for OMEMO (which while not entirely solves, has a
lot of work put into it) and there would be no additional identity or
key management tasks.

This reminds me of something I had in mind for reviving XEP-0174:
adding a TXT key that carries a signature of other parts of the mDNS
records, so that one can discover that a known OMEMO contact is nearby
and send messages to them directly rather than through the server.

Marvin


On Tue, 2026-06-02 at 09:39 +0000, Daniel Gultsch wrote:
> The XMPP Extensions Editor has received a proposal for a new XEP.
> 
> Title: XMPP Decentralized ID (XID)
> Abstract:
> XMPP Decentralized ID (XID) is a DNS independent XMPP entity
> identifier. This specification describes how to generate, use, and
> handle them.
> 
> URL: https://xmpp.org/extensions/inbox/xid.html
> 
> The Council will decide in the next two weeks whether to accept this
> proposal as an official XEP.
_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]