Dave Cridland wrote:
> On Sat Jun  7 00:07:36 2008, XMPP Extensions Editor wrote:
>> The XMPP Extensions Editor has received a proposal for a new XEP.
>>
>> Title: XMPP Transport Layer Security
>
> Some comments:
>
> 1) I like using streams, too, that seems to make perfect sense,
> especially given XEP-0174.
[...]
> However, I got talking to Rob McQueen - there's a certain amount of
> sense in, instead of describing this in terms of IBB, describing it
> in terms of Jingle.
>
> It's possible - and reasonable - to consider an XMPP stream as
> content, in which case the TLS becomes a transport (or possibly
> attribute of the transport).

An one hand it is reasonable to use Jingle, I had something like this
is my first draft. On the other hand I would like to reduce the number
of roundtrips needed to set up an XTLS "connection". I would even
consider making XTLS different to remove one roundtrip by adding IBB
open to the xtls iq:

| <iq from='[EMAIL PROTECTED]/orchard'
|     id='xtls_1'
|     to='[EMAIL PROTECTED]/balcony'
|     type='set'>
|   <xtls xmlns='urn:xmpp:tmp:xtls'>
|     <open xmlns='http://jabber.org/protocol/ibb'
|           block-size='4096'
|           sid='MySid'/>
|   </xtls>
| </iq>

I'm not sure if it violates any rules, but IMHO this would be the
fastest way to set up a client-to-client TLS stream. In my scenario I
have many bots talking to each other so I want to reduce the server
load to avoid sending too much stanzas when a new bot comes up.

So we have two choices here:

1. Use jingle and re-use XEP-0174 code.
   + looks reasonable
   + makes it possible to use something else except IBB
   - more roundtrips, even more if you try SOCKS5 and it does not work

2. XTLS the way it is now, maybe the shortcut from above
   + faster to set up
   - special handling since it is different from XEP-0174

I prefer the second one, but I guess that is something for the XMPP
Cousil to vote for.



Dirk
 
-- 
-----------------------------------------------------------------------------
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
-----------------------------------------------------------------------------

Reply via email to