[standards-jig] jep 65 - bytestream type

Justin Karneges justin-jdev at affinix.com
Thu Jul 24 07:54:57 UTC 2003

JEP-65 is intended to be generic like TCP.  What you do with it is your own 
business.  For instance, file transfer JEPs have been written to use JEP-65 
as a basis.  However, this does not require modification to JEP-65, in much 
the same way we did not have to modify TCP to create Jabber.

I suggest you look into JEP-95.


On Thursday 24 July 2003 12:06 am, Ulrich B. Staudinger wrote:
> Hi,
> reading over jep65 again i miss a feature:
> i wonder if it makes sense to define the bytestream type?
> GT2.7 i uses GSM for voice streaming. But, because gt does support a
> specific bytestream (type gsm) i respond
> <iq
>     type='result'
>     from='target at host2/bar'
>     to='initiator at host1/foo'
>     id='hello'>
>   <query xmlns='http://jabber.org/protocol/disco#info'>
>     <feature var='http://jabber.org/protocol/bytestreams/gsm'/>
>   </query>
> </iq>
> to an iq query.
> Especially plain bytestreams with no start and no end don't need a very
> complicative negotiation session before setting up the bytestream.
> Either a client supports gsm or not. same goes with mp3 streams.
> Just a thought.
> ulrich

More information about the Standards mailing list