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

Paul Long Plong at SMITHMICRO.COM
Sun Jun 4 21:52:10 EDT 2000


Anatoli,

This may be a poor choice for the name of the new field. By "earlyH245," I
think Paul means that an encapsulated H.245 message is being conveyed
earlier than H.323 would otherwise allow--in a Setup message that also
contains fastStart. I don't think he meant "Early H.245" at least as I have
been using the term, i.e., establishing a separate H.245 channel through the
h245Address field prior to the receipt of Connect. Maybe this means we need
to call the field something else. That's why I called it "earlyH245Control"
in my response. Any other suggestions? I don't know, how about
"alternateH245Control?"

Paul Long
Smith Micro Software, Inc.

-----Original Message-----
From: Anatoli Levine [mailto:alevine at RADVISION.COM]
Sent: Saturday, June 03, 2000 5:46 PM
To: ITU-SG16 at MAILBAG.INTEL.COM
Subject: Re: On TD26 - Fast TCS and M/S negotiation in H.323v4


Paul,

why do we need "earlyH245" field in the SETUP-UUIE? Technically, just
the
presence of H245Address in the SETUP H323-UU-PDU has a meaning of
"earlyH245". I
thought we were trying to resolve an issue with Tunneling and Fast Start
- how
is this "earlyH245" field will help?

Anatoli

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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