* Florian Schmaus <f...@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: ยง8.5.3.2.1. https://xmpp.org/rfcs/rfc6121.html#rules-localpart-fulljid-nomatch 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) Georg -- || 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 ||_________________________________________________||
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
