Re: Proposed XMPP Extension: XMPP Decentralized ID (XID)
Goffi <[email protected]> Sun, 07 Jun 2026 18:50:17 +0200
| Newsgroups | gmane.network.jabber.standards-jig |
|---|---|
| Message-ID | <[email protected]> |
--===============4191034281625104373== Content-Type: multipart/signed; boundary="nextPartVu2YxOWoT0mcYrssYxMkwA"; micalg="pgp-sha512"; protocol="application/pgp-signature" --nextPartVu2YxOWoT0mcYrssYxMkwA 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: Sun, 07 Jun 2026 18:50:17 +0200 Message-ID: <[email protected]> In-Reply-To: <[email protected]> MIME-Version: 1.0 Hi singpolyma, Le mardi 2 juin 2026, 19:45:11 heure d=E2=80=99=C3=A9t=C3=A9 d=E2=80=99Euro= pe centrale Stephen Paul=20 Weber a =C3=A9crit : > >URL: https://xmpp.org/extensions/inbox/xid.html >=20 > I am unclear on the goal here. It doesn't give us e2e auth, nor does it g= ive=20 > us decentralized routing. What can I actually accomplish with this that I= =20 > cannot accomplish without it? Indeed, it's not about auth nor routing; it's a decentralized DNS-independa= nt=20 ID for an entity (not a device). I need that for serverless, but it has several other use cases as explained= in=20 the protoXEP, and we don't have equivalent AFAIK for that (OX would be the= =20 closest, but more complicate and difficult to use in those case). It's inspired from Peer ID from libP2P, and relatively simple to implement = and=20 use. > I'm also concerned about formatting them as valid JIDs since this may get= =20 > confusing on the live network. That's why a `.internal` TLD was used for, but as pointed out by other in t= his=20 thread, it's not the best choice. Probably `.alt` would be a better fit, as= =20 it's a non-DNS namespace. Best, Goffi --nextPartVu2YxOWoT0mcYrssYxMkwA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEsNZvWyEnjW9SVudbKqmcu6xuKwwFAmoloUkACgkQKqmcu6xu KwwS5Qf8C/kjKBVCXBGd5n1apqOrzAW8QnP99URslHecIYkdmL98vdeAskJrBi8T Rf8ThuP2DF5fPNE6OgoOJACjXYrP8CevGtc4E8p/Twv3xydqw6lG0xTzxDutF9uD M+tSY++82H7PircA/rDzTsoAQaEajawqJrl3GgSiQZkWt8Btdbi2F+Ge/V9nKneY t/+w+6EbbMP13rhhQRD5lTgtReX0Ydh/9OEzCxmrg2IwaVSeQ1jWEYZKhRd21lAE HFgpo7NyR0Tfnk1SFmkuZRnwNctqeVHESzJUw1xeOgyJJSsfM9OAS0rHi/1sN7Dd xyvPd6HqOTBa1aWNhWaX4wluWkYRGg== =1o2g -----END PGP SIGNATURE----- --nextPartVu2YxOWoT0mcYrssYxMkwA-- --===============4191034281625104373== 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] --===============4191034281625104373==--