[jdev] voicechat again

Jacek Konieczny jajcus at bnet.pl
Fri Mar 5 04:22:15 CST 2004

On Thu, Mar 04, 2004 at 08:47:09PM +0100, Ulrich Staudinger wrote:
> putting this into a compliance test is a very good idea. But I'd not go 
> native streaming with one fixed codec, going compliant to RTP seems 
> simply better - it's not reinventing like substituting a round wheel 
> with an eightsided one ...

RTP is not a protocol on its own. Read the RFC 1889:

   RTP represents a new style of protocol following the principles of
   application level framing and integrated layer processing proposed by
   Clark and Tennenhouse [1]. That is, RTP is intended to be malleable
   to provide the information required by a particular application and
   will often be integrated into the application processing rather than
   being implemented as a separate layer. RTP is a protocol framework
   that is deliberately not complete.  This document specifies those
   functions expected to be common across all the applications for which
   RTP would be appropriate. Unlike conventional protocols in which
   additional functions might be accommodated by making the protocol
   more general or by adding an option mechanism that would require
   parsing, RTP is intended to be tailored through modifications and/or
   additions to the headers as needed. Examples are given in Sections
   5.3 and 6.3.3.

RTP should be used for Voice chats in Jabber but is not enough. Still many
things should be defined for Jabber separately. And that is OK.


More information about the JDev mailing list