[VOIPSEC] 4G Issue Map: signaling complexity

[Hadriel Kaplan]

> -----Original Message-----
> From: Voipsec-bounces at voipsa.org [mailto:Voipsec-bounces at voipsa.org] On
> Behalf Of Paul E. Jones
>
> SIP compression apparently came about because people felt like they needed
> to consume less bandwidth over wireless links.  Why that matters when you
> then send a bunch of RTP packets out seems illogical to me, but I suppose
> that's why I'm not making wireless handsets.  

Actually, its my understanding it's not so much the bandwidth (although that
may also matter when you take into account the number of phones in a cell,
where few are actually in-call but there's still signaling).  But the real
reasons were serialization delay and bit error rate.  The delay ended up
creating very long call setup times.  And BER obviously would make it worse
(not to mention consume more bandwidth).

 
> Perhaps, but machines do not get debugged all the time.  Further, I have
> never had any trouble personally debugging protocols written in ASN.1.
> When
> messages are decoded, you can print the contents on the screen.
> 
> Only 2 or 3 times in my life have I ever seen the binary decode operation
> fail.  The reason is that people generally use well-tested commercial
> compilers and libraries from companies like OSS.

Wow.  We must live in different worlds.  I get "H.323" traces all the time
Ethereal can't decode and I end up asking the vendor for their secret
decoder ring.  This literally happened last week.  When Ethereal can't parse
someone's SIP, I still can. (well, unless sigcomp is used ;)  

-hadriel