There's been a lot of virtual slander of the work in the IETF on this list lately...
I keep wondering, why doesn't people like us start working more in the IETF and change stuff? Are we not patience enough, are we not brilliant enough?
For myself I can't spend much time on it, since it doesn't generate any immediate revenue. There's a lot of stuff I could do, but at the end of the month, I would have no salary that pays for food... It's quite simple.
Which means that the result in the IETF is far away from reality and that we reach further separation between IETF SIP and practical implementations, which is BAD for the overall community.
/O
Olle E. Johansson writes:
I keep wondering, why doesn't people like us start working more in the IETF and change stuff? Are we not patience enough, are we not brilliant enough?
ietf sip wg was taken over by ims guys already many years ago. all they seem to do is rubber stamp ims specifications to make them look like internet stuff.
-- juha
El Sábado, 7 de Noviembre de 2009, Juha Heinanen escribió:
Olle E. Johansson writes:
I keep wondering, why doesn't people like us start working more in the IETF and change stuff? Are we not patience enough, are we not brilliant enough?
ietf sip wg was taken over by ims guys already many years ago. all they seem to do is rubber stamp ims specifications to make them look like internet stuff.
For example, IMS vendors are not interested in "multidomain" as in their private networks there is no *real* multidomain (a PSTN number identifies an user globally, domain "doesn't matter").
actually from time to time we contribute but probably out of interest areas of prevailing ietf participants. identity concerns are all answered by 4474, its SDP protection is no problem because noone rewrites SDP, diagnostics is just not interesting enough, etc. etc....
-jiri
Iñaki Baz Castillo wrote:
El Sábado, 7 de Noviembre de 2009, Juha Heinanen escribió:
Olle E. Johansson writes:
I keep wondering, why doesn't people like us start working more in the IETF and change stuff? Are we not patience enough, are we not brilliant enough?
ietf sip wg was taken over by ims guys already many years ago. all they seem to do is rubber stamp ims specifications to make them look like internet stuff.
For example, IMS vendors are not interested in "multidomain" as in their private networks there is no *real* multidomain (a PSTN number identifies an user globally, domain "doesn't matter").
Olle E. Johansson schrieb:
There's been a lot of virtual slander of the work in the IETF on this list lately...
I keep wondering, why doesn't people like us start working more in the IETF and change stuff? Are we not patience enough, are we not brilliant enough?
Because IETF is too cumbersome and simple pragmatic solutions are not accepted :-)
For myself I can't spend much time on it, since it doesn't generate any immediate revenue. There's a lot of stuff I could do, but at the end of the month, I would have no salary that pays for food... It's quite simple.
Which means that the result in the IETF is far away from reality and that we reach further separation between IETF SIP and practical implementations, which is BAD for the overall community.
/O
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Klaus Darilion wrote:
Olle E. Johansson schrieb:
There's been a lot of virtual slander of the work in the IETF on this list lately...
I keep wondering, why doesn't people like us start working more in the IETF and change stuff? Are we not patience enough, are we not brilliant enough?
Because IETF is too cumbersome and simple pragmatic solutions are not accepted :-)
There may be some truth to the answer, but there is also the fact that simple pragmatic solutions often only work for a very limited audience.
Take the nathelper example. Sure it works brilliantly if you have a simple network and have everything under your control. But when things get a bit more complex, there is interop issues aplenty.
Most of the stuff coming out of IETF you can easily ignore. And if you have something working, you may very well get it through. XMPP is an example of that. In the SIP world, it seems the attitude currently is changing a bit towards that too.
Regards, Martin
On Mon, Nov 9, 2009 at 2:11 PM, Martin Hoffmann martin.hoffmann@telio.ch wrote: (snip)
Most of the stuff coming out of IETF you can easily ignore. And if you have something working, you may very well get it through. XMPP is an example of that. In the SIP world, it seems the attitude currently is changing a bit towards that too.
These are a couple of very fresh messages from today:
http://www.ietf.org/mail-archive/web/dispatch/current/msg00901.html http://money.cnn.com/news/newsfeeds/articles/marketwire/0556433.htm
Cheers,
-
Iñaki Baz Castillo -
jh＠tutpro.com -
Jiri Kuthan -
Klaus Darilion -
Martin Hoffmann -
Olle E. Johansson -
Victor Pascual Avila