[standards-jig] LAST CALL: SOCKS5 Bytestreams (JEP-0065)

Casey Crabb crabbkw at nafai.dyndns.org
Mon Jan 13 20:28:15 UTC 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

An issue I noticed with the JEP.

Section 4.2, after example 5, before example 6:
"Once the Target receives the IQ-set from the Initiator, it MUST either
refuse or accept the bytestream offered by the Initiator. The IQ cannot
be ignored.

If the Target is unwilling to accept the bytestream, it MUST return an
IQ-error to the Initiator with an error code of 406 ("Not Acceptable")."

This works for objects that actually implement the jep, but since we
cannot assume that an object has implemented it we either must
a) have some sort of feature-negotiation involved before we send the
request; or
b) allow for the iq-set to be ignored.

I understand why we don't want the iq-set to be ignored, but
implementations should be able to time-out the listening sockets after a
time if the iq-set is ignored.


Thoughts?

- --
Casey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+IyFeUidG/HUEju8RAo/bAJ994ZmbFfqlL6yuvNygI5T2HEBdZQCff+WE
ylCmK5ySerOLZBK91ZdLWXo=
=TDff
-----END PGP SIGNATURE-----




More information about the Standards mailing list