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

--===============2308853004797700150==
Content-Type: multipart/signed; boundary="nextPartOohr6YpfRVGNjLCU_dainQ";
 micalg="pgp-sha512"; protocol="application/pgp-signature"

--nextPartOohr6YpfRVGNjLCU_dainQ
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Goffi <[email protected]>
To: XMPP Standards <[email protected]>
Date: Tue, 02 Jun 2026 18:36:04 +0200
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

Le mardi 2 juin 2026, 17:06:27 heure d=E2=80=99=C3=A9t=C3=A9 d=E2=80=99Euro=
pe centrale Marvin W. via=20
Standards a =C3=A9crit :
> Hey,
>=20
> 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?

An entity (which can be a person, a bot, a group of human, whatever), but n=
ot=20
a device.
=20
> 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.

OMEMO is per-device, it doesn't work here. It's also far more complicated t=
o=20
implement. OX could be used, but the key sharing mechanism is not specified=
=20
anyway, and again it's more complicated to implement the whole thing (and i=
t's=20
not widespread). The current implementation is relatively easy for most=20
clients, as Ed25519 is already used for OMEMO.


> 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.

One of the main purpose of this proposal is to have a ID working for=20
serverless, on which I'll be working soon. I've chosen something easily=20
mappable to LibP2P's Peer ID.

Best,
Goffi
--nextPartOohr6YpfRVGNjLCU_dainQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEsNZvWyEnjW9SVudbKqmcu6xuKwwFAmofBnQACgkQKqmcu6xu
KwxG5gf/Va8UmGgTtEagm6b1k9fjowM32k6j/aNgzhkGKbejwEjmiX0LAuFdhEEi
Ir0yrXVwi6UrDaWHXbH89UeOGZM1JfzgxLBgO4Xn+jIIRY144zSlbYuhXDslcoQc
2qvQPBzAJSbP3LjG8P9AdAYQqzLGVHkeNhA35L1Yu0yFhCAFWJiMnLzkk/ODmkIs
JulA7nEQxScBn6Ze31vscwq5K+/+CuyRWhTwC7jJUh2tgxZ+8tfZFo2Er+DvkQCN
7djcALW7eqy8FfwmCeELdbeEoJPtoBZwJRBHKW2TFTJMRWmt3ENZHKO48mRhsi9a
Eexyv3ftV1DMitIx1Lv0Ahb5n80xkQ==
=8jGF
-----END PGP SIGNATURE-----

--nextPartOohr6YpfRVGNjLCU_dainQ--




--===============2308853004797700150==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--===============2308853004797700150==--