[standards-jig] JEP 65 - Bytestreams
dizzyd at jabber.org
Wed Dec 18 04:35:35 UTC 2002
-----BEGIN PGP SIGNED MESSAGE-----
Given the discussion of the past week, a significant amount of work has
gone into identifying the core requirements for the concept of
establishing peer-to-peer and proxied binary connections (a.k.a.
bytestreams) between Jabber entities. The culmination of this work can
now be found in JEP 65 - Bytestreams. You can find the JEP at:
I would encourage everyone to comment -- whether you love it or hate
it. We need to get past this quagmire of establishing a bytestream
connections. We can only do that if the community makes a clear
statement around which protocols are appropriate to for this purpose.
I am currently in the process of writing a reference bytestream Proxy
(per this JEP) that will be available on jabber.org immediately
following the upcoming holidays. Additionally, I am encouraging client
authors and Council members to review and try and implement the
specification laid out in this JEP. Finally, I hope to see the File
Transfer JEP (JEP 052) adjusted to specify how it could use JEP 65 and
JEP 47 to perform file transfers.
Some strengths of the methodology used in this JEP:
* Uses an IETF standard protocol for the out-band negotiation (SOCKS5)
* Supports proxied bytestreams
* Supports IPv6 out of the box (thanks to SOCKS5 specification)
* Supports bi-directional exchanges in the bytestream
Please consider this JEP as a candidate for a community driven standard.
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 (Build 349) Beta
-----END PGP SIGNATURE-----
More information about the Standards