[Standards] [E2E] Why we need a <body> element

Jonathan Schleifer js-xmpp-standards at webkeks.org
Tue Sep 30 16:44:19 UTC 2008

Am 30.09.2008 um 18:32 schrieb Dirk Meyer:

> Why do you want to inform the receiver? He can not do anything about
> the problem. It is the sender who has to fix it by either re-open the
> e2e stream with the new client and resend the message or if that is
> not possible (the new client has no e2e support) it should inform the
> sender about the problem suggesting an insecure resend. If the user
> does not want to use insecure communication, the client may drop the
> message. Anyway, IF you want to inform the receiver, the sender could
> generate a new message 'e2e stream broken, message not delivered' and
> send it to the receiver.

With the problem that the sender doesn't always notice it, and if you  
know it as a receiver, you can tell the sender to please send it again.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://mail.jabber.org/pipermail/standards/attachments/20080930/f3bc863b/attachment.sig>

More information about the Standards mailing list