[Standards] Problems with IM Message Routing: Message Types

Georg Lukas georg at op-co.de
Sat Nov 11 11:04:58 UTC 2017

* Florian Schmaus <flo at geekplace.eu> [2017-11-10 21:54]:
> > - bare-JID = all-clients + archive
> > - full-JID = single client, no carbons, no archive, no redirection
> Which rules of RFC 6121 do you exactly need/want to bend or violate?

The only RFC6121 rule that needs to go is the re-routing of "chat"
messages sent to an unavailable full-JID: §

However, the above rules would break the following XEPs:

- resource locking (must get rid of it for messages)
- Carbons (no more CCing of full-JID messages)
- MAM (no archiving of full-JID messages)

|| http://op-co.de ++  GCS d--(++) s: a C+++ UL+++ !P L+++ !E W+++ N  ++
|| gpg: 0x962FD2DE ||  o? K- w---() O M V? PS+ PE-- Y++ PGP+ t+ 5 R+  ||
|| Ge0rG: euIRCnet ||  X(+++) tv+ b+(++) DI+++ D- G e++++ h- r++ y?   ||
++ IRCnet OFTC OPN ||_________________________________________________||
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20171111/5b317a92/attachment.sig>

More information about the Standards mailing list