Jonathan Schleifer wrote:
Dirk Meyer <[EMAIL PROTECTED]> wrote:

You open a stream from client to client. It could be based on In-band
bytestreams. Normally used for file transfer and stuff like that we
use it to open a new stream. So you have one stream to the server and
one stream (maybe tunneled through the server) to the other
client. You can open as many streams to other clients as you want.

So you encode that XML stream in base64 and transfer it inbound? Ah,
ok. That explains how you can have more than one of them. But this
looks VERY hacky to me. Base64 encoded XML in XML.

It's not hacky, it's a clever hack:

1. Negotiate a reliable transport (could be a direct TCP connection, could be in-band bytestreams over XMPP, whatever).

2. Start an XML stream.

3. Upgrade the stream to encrypted using STARTTLS.

You'll notice that this is exactly what we already do for XMPP as defined in RFC 3920. It's just that for end-to-end streams the transport might not be a direct TCP connection as in RFC 3920.

/psa

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to