On TD26 - Fast TCS and M/S negotiation in H.323v4

Pete Cordell pete at TECH-KNOW-WARE.COM
Tue Jun 6 12:27:08 EDT 2000


Why not?

... More helpfully, if you would like to define a 450 supplementary service
for it, then as long as it meets with the concensus of the group that that
is the way to go, then I would prefer that to new ASN.1 in the base spec.

Pete.

=============================================
Pete Cordell
Tech-Know-Ware
pete at tech-know-ware.com
+44 1473 635863
=============================================

----- Original Message -----
From: Callaghan, Robert <Robert.Callaghan at ICN.SIEMENS.COM>
To: <ITU-SG16 at MAILBAG.INTEL.COM>
Sent: 06 June 2000 16:40
Subject: Re: On TD26 - Fast TCS and M/S negotiation in H.323v4


> Pete,
>
> Please NO packages!
>
> Bob
>
> -----Original Message-----
> From: Pete Cordell [mailto:pete at TECH-KNOW-WARE.COM]
> Sent: Monday, June 05, 2000 2:54 PM
> To: ITU-SG16 at mailbag.cps.intel.com
> Subject: Re: On TD26 - Fast TCS and M/S negotiation in H.323v4
>
>
> 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.
>
> =============================================
> Pete Cordell
> 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
>
>
> > Francois,
> >
> > 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.
> > Given:
> > H245Control ::= SEQUENCE OF OCTET STRING OPTIONAL
> >
> > therefore:
> >         h245Control                     H245Control,
> > and:
> >         earlyh245Control                H245Control,
> Looks good to me.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> For help on this mail list, send "HELP ITU-SG16" in a message to
> listserv at mailbag.intel.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com



More information about the sg16-avd mailing list