Aah an ASN.1 firefight!
It's been a LONG time since we've had one of those, but they used to be a
regularly scheduled event on this list.
I used to have opinions on this debate - for a trip down memory lane, check
out the canonical X.400 vs SMTP debate on my website (sorry, typing
offline
: Tuesday, August 26, 2003 2:50 AM
To: Karl Auerbach
Cc: IETF
Subject: ASN.1 (Re: Pretty clear ... SIP)
Aah an ASN.1 firefight!
It's been a LONG time since we've had one of those, but they
used to be a
regularly scheduled event on this list.
I used to have opinions on this debate
Dean Anderson writes:
I find H.323 to be qualitiatively worse, as measured in units of
elegance, than SIP.
I find just the opposite. Now I have to worry about the security of SIP
phones, and that they might be used for evesdropping. H323 and and
trusted ASN.1 compilers can go a
It has been my experience that ASN.1, no matter which encoding rules are
used, has proven to be a failure and lingering interoperability and
denial-of-service disaster.
I think the nugget of our discussion is the old, and probably
unanswerable, question of what is the proper balance
Anderson
Cc: IETF
Subject: Re: Pretty clear ... SIP
It has been my experience that ASN.1, no matter which
encoding rules are
used, has proven to be a failure and lingering
interoperability and
denial-of-service disaster.
I think the nugget of our discussion is the old
At 19:03 -0700 8/23/03, Karl Auerbach wrote:
On Sat, 23 Aug 2003, Dean Anderson wrote:
H.323 and ASN.1 eventually surpass ...
Ummm, based on my own direct experience with ASN.1 since the mid 1980's
(X.400, SNMP, CMIP...), I disagree.
It has been my experience that ASN.1, no matter which encoding
Err, I think there are some things missing:
1) H.323 closely matches PSTN protocols and capabilities. Its
interoperability with ISDN and SS7 are far more natural.
2) H.323 is more efficiently coded using ASN.1. One might not think that
this matters, but in fact it matters a great deal in large
On Sat, 23 Aug 2003, Dean Anderson wrote:
H.323 and ASN.1 eventually surpass ...
Ummm, based on my own direct experience with ASN.1 since the mid 1980's
(X.400, SNMP, CMIP...), I disagree.
It has been my experience that ASN.1, no matter which encoding rules are
used, has proven to be a failure
Hi -
From: Karl Auerbach [EMAIL PROTECTED]
To: IETF [EMAIL PROTECTED]
Sent: Saturday, August 23, 2003 7:03 PM
Subject: Re: Pretty clear ... SIP
On Sat, 23 Aug 2003, Dean Anderson wrote:
H.323 and ASN.1 eventually surpass ...
Ummm, based on my own direct experience with ASN.1 since
At Sat, 23 Aug 2003 21:31:19 -0700, Randy Presuhn wrote:
In fairness,
1) SNMP's (ab)use of ASN.1 pretty much precludes the use of ASN.1 compiler
technology. All the implementations I know of used hand-coded encoders and
decoders. The vulnerabilities aren't a result of
on 8/24/2003 1:53 AM Rob Austein wrote:
I've used ASN.1 compiler technology for a project that included an
H.323-related frob, and ended up wishing I hadn't. Can you say more
than 2MB just for the ASN.1 PER encoder/decoder on a box with an 8MB
flash chip? (For comparision, the embedded
On Sat, 23 Aug 2003, Karl Auerbach wrote:
On Sat, 23 Aug 2003, Dean Anderson wrote:
H.323 and ASN.1 eventually surpass ...
Ummm, based on my own direct experience with ASN.1 since the mid 1980's
(X.400, SNMP, CMIP...), I disagree.
It has been my experience that ASN.1, no matter which
The difference between internet telephony and voice chat.
This is fairly critical actually. It doesn't matter if you're talking
about H323 or SIP although obviously there is a bias in each one
towards one or the other. The commonly used VoIP name does NOT do
enough to differentiate, we need to
Since SIP is IETF not ITU its only reasonable to have internet believers
lean towards it.
H.323 ? Ahhh no thanks.
No serious look at these can even consider H.323 etc and its derivitives as
useful in the general case. The only reason they were used is the absence of
a better alternative.
Try to
14 matches
Mail list logo
