[standards-jig] A few thoughts on JEP 0035

Robert Norris rob at cataclysm.cx
Wed Jul 10 01:12:59 UTC 2002


> How about having the initialization consist of sending a request and 
> closing the stream?
> 
> i.e.
> C: <stream:stream xmlns='jabber:client'
>                  xmlns:stream='http://etherx.jabber.org/streams'
>                  xmlns:tls='http://www.ietf.org/rfc/rfc2595.txt'
>                  to='jabber.org'>
> S: <stream:stream xmlns='jabber:client'
>                  xmlns:stream='http://etherx.jabber.org/streams'
>                  xmlns:tls='http://www.ietf.org/rfc/rfc2595.txt'
>                  id='12345678'>
>   
> C: <tls:starttls/></stream:stream>
> S: </stream:stream>
> 
> {begin negotiation, etc.}

Because you can't be informed of a failure. Admittedly, the JEP doesn't
allow for this, but it probably should. Is there ever a reason that TLS
would be offered but initialization not succeed?

Rob.

-- 
Robert Norris                                       GPG: 1024D/FC18E6C2
Email+Jabber: rob at cataclysm.cx                Web: http://cataclysm.cx/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20020710/fc136029/attachment.sig>


More information about the Standards mailing list