We had proposals for end-to-end encryption using TLS here. It was suggested to use a stream in a stream using Jingle inbound. These stream will be encapsulated in the stream using <message>s or <iq>s then. And I think we should go for <message>s, but also include a <body> that states that this is part of an encrypted session. It was argued that the message may never get to the wrong resource when I mentioned that problem, but the example posted before states the opposite, that it indeed DOES happen in the real world.

--
Jonathan

Attachment: PGP.sig
Description: This is a digitally signed message part

Reply via email to