> There is a very obvious solution to this which everyone seems to be > overlooking: we need a new element with a guaranteed unique, non-spoofed > UUID; should a server feel the need to do bad things, it can set the > 'spoofed' attribute to true and then clients can act accordingly. what entity would set that element? the sending client? the server of that client? the server of the receiving client?
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
