[Standards] XEP-0065: SOCKS5 acknowledgement after stream activation

Jakob Schroeter js at camaya.net
Mon Apr 30 22:37:18 UTC 2007


According to XEP-0065, Section 4.9: after activation of the bytestream by the 

  The Proxy MUST then send SOCKS5 acknowledgement of the connection to
  the Target.

  Example 19. StreamHost Acknowledges Connection to Target

    STATUS = X'00'

I can see that it may be interesting for the target to know when the stream is 
active, i.e. when the initiator established its connection to the proxy. This 
would be handy for bi-directional or reverse streams.

However, it seems this is not inline with the SOCKS5 spec[1], e.g. immediately 
after the proxy acknowledged the connection to the target (Section 4.6 in 
XEP-0065) the stream is ready to be used as far as SOCKS5 is concerned. So 
calling this a 'SOCKS5 acknowledgement' is wrong, IMHO.

Further, it appears neither of the clients I tested against (Iris/Kopete/Psi, 
Gajim, Tkabber) nor proxy65 are sending or expecting such additional byte/s 
(if it were SOCKS5, it'd be at least two bytes: X'05', X'00').

Is this a left-over from an earlier revision? Would peeple be interested in a 
(in-band?) stream-active notification from stream host to target?


[1] http://tools.ietf.org/html/rfc1928
-------------- 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/20070501/478d72bb/attachment.sig>

More information about the Standards mailing list