Re: [AVT] Meeting in San Francisco

[Greg Herlein <gherlein@herlein.com>]

> Working code appears to be more useful than meetings of the I* society...
> http://lists.digium.com/pipermail/asterisk-users/2003-February/007532.html

Well, I might as well introduce myself on this list by
disagreeing.  :)  

Your link discusses Asterisk's non-standard implementation of the
use of Speex in RTP.  It may be working code for asterisk, but it
can't talk to anything else.  In fact, it may work for Asterisk,
but since it does not do dyunamic payload types, it can't talk to
much of anything else.

Currently, Speex is trying to finalize a draft profile for use in
RTP.  Currently, there is interoperability between gnomemeeting
and ohphone, for example, but only because both use the OpenH323
implementation of speex.  Linphone can talk to other linphone
apps, but I don't know of any other SIP-based apps that have
implemented libspeex.  We do have a draft that we just submitted
that should make interoperability possible.

Getting to where we are has been a lot of hours spent emailing
between the primary authors of the above apps to get everyone to
agree.  I'd rather not repeat that when the next VoIP app comes
along and wants to play.  I'd rather say "go read the RFC."

Now, if like Asterisk, they chose to not even follow the basic
rules, that't their issue.

The objective of these meetings is to get specs to a point where
there is hope for interoperable implementations.  Working code is
easy - any fool programmer can do that.  Getting that code to
interoperate with other implementations is much harder.

Greg

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt