On TD26 - Fast TCS and M/S negotiation in H.323v4
pete at TECH-KNOW-WARE.COM
Mon Jun 5 14:53:33 EDT 2000
Well if you want to
kick the final bit of life out of H.323 then add another field to H.323 that
does much the same as something that's already in there. Heck, we'll
probably have to do something similar with a few other features as well, so
this change would hardly be noticed.
The issue is a bit like the ozone layer and CFCs. A squirt of deodorant in
the morning surely didn't make much difference to the ozone layer. But the
fact was that it all added up. Fortuneately policy has come in to attempt
to address the ozone layer problem, and hopefully we can avoid having to go
around covered from head to toe in future. We face much the same issue with
H.225, but we already have to wear factor 50 sun cream all the time!!!
On the other hand, defining this addition using the packages field would
stop this beating a dead horse approach. I've attached a doc that shows
what is involved. Note that most of the procedure elements would have to be
included with what ever approach is taken and they do not represent a
burden of implementing this using packages.
pete at tech-know-ware.com
----- Original Message -----
From: Francois Audet
To: ITU-SG16 at MAILBAG.INTEL.COM
Sent: 05 June 2000 16:39
Subject: Re: On TD26 - Fast TCS and M/S negotiation in H.323v4
> Woohoo!!!! :-)
> Actually, I suppose earlyH245Control could contain multiple
> H.245 messages,
> since it will presumably be defined the same as h245Control:
Yes, I had meant to make a comment about this yesterday, but I had
already disconnect from dial-up.
> H245Control ::= SEQUENCE OF OCTET STRING OPTIONAL
> h245Control H245Control,
> earlyh245Control H245Control,
Looks good to me.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 37376 bytes
Desc: not available
More information about the sg16-avd