> 2) A restricted user may not have the ability to type the correct jid. > > This doesn't seem to be addressed, but could be with minor modifications. For > example, if I have the ascii-fied jid of [email protected], I could > have my client request the correct spelling, in effect, and get back > remko.tronç[email protected]. Presumably in this case, it would need to > request this from swift.example, and not the client's local server - though > it's possible that the local server might forward along the request. > > This becomes rather more useful for asian jids, where the user may well have > both a ascii (and possibly even European) variant of their name as well as > the correct script.
This gets really fun when you consider internationalized domain names. So at that point you don't really know who to send the request to. But, disregarding that, having a query to ask a server for an even more proper representation of a JID does seem doable. What would the logic be for that though? 1) A server that supports this kind of aliasing MUST set a user's JID to the non-aliased version during binding. So an alias JID wouldn't ever be sent out by that server. 2) Before interacting with a new JID, a client SHOULD send an alias query to the given JID's server and discard and remap the given JID in favor of the result. This is independent of being able to prep a JID, so this would apply to *all* clients which allow a user to type in a JID. 3) The main question: if the server for the user with an alias receives a request to the alias JID, does it forward it to the proper JID, or return an error saying to try again with the real JID? 4) Just for fun: If I had both an internationalized domain name, and an ASCII version, could I alias JIDs between them. Ie, could an alias map to a JID on another domain? Security considerations abound. I'm in favor of specifying this behavior in its own XEP, since it is generally applicable to all clients, not just those in constrained environments without access to stringprep/precis/etc (e.g. browsers). -- Lance
smime.p7s
Description: S/MIME cryptographic signature
