Le mardi 2 juin 2026, 14:14:35 heure d’été d’Europe centrale Dave Cridland a
écrit :
Repeating my GH comment verbatim:
Repleating my
reply:
Hi @dwd thanks for your feedbacks (very valuable, as always).
- I've chosen `.internal` because it's reserved for private application use
(
https://en.wikipedia.org/wiki/.internal,
https://www.rfc-editor.org/info/
rfc6762/#appendix-G) actually to avoid accidental reach of a real server. But
you're right that on private networks it can be an issue. Your `xid.xmpp.org`
proposal can be a solution. I would like to have more inputs on it before
changing though.
- The use of JID syntax is to make XID trivially usable in many use cases with
little to no adaptation code (I'm thinking about "from"/"to"
attribute with
serverless, but in general anywhere were a JID is expected, a XID could be
used). Please note the server mapping feature, and also in business rules, the
example of "publisher" attribute for pubsub. We have also `xmpp:` URIs re-
usable without any modification.
- Your challenge comments are very relevant, I'll update after Council vote if
the spec is accepted.
- expiry would be nice indeed. Probably not mandatory though.
- Multiple XIDs are already explicitly allowed, as well as having the same XID
for various account on different domain names.
- I'll have a look to what you suggest, but note that I try to make something
simple and easy to implement. The first byte is there to extend algorithms
easily later if necessary (for PQ or some other reason). One of the advantages
of `Ed25519` is that it's already used with OMEMO, so most clients already
have an implementation.
I would like to avoid the discussion here if possible, and rather see it on
standard@ (more eyes, no need to chase feedbacks everywhere, and archives are
easier to retrieve).
Best,
Goffi