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

Paul E. Jones paulej at PACKETIZER.COM
Mon May 29 22:46:18 EDT 2000


Pete, Sasha, Francois, Dale, et al,

I have concerns about this document that differ from Pete's.  However, since
discussion on this document has started, I thought I might as well express
my concerns now while the material is fresh on people's minds.

The issue has to do with the very first sentence of the proposal, which says
to strike "shall not" and replace it with "may".  So, V2 devices shall not
send a fastStart element and an H.245 message in SETUP, but V4 may.  This
seems to be a serious backward compatibility issue.  If a V2 device were to
receive a SETUP containing fastStart and an encapsulated H.245 message, what
would it do?  I believe the behavior is not defined.

Would somebody like to comment?

Paul

----- Original Message -----
From: "Pete Cordell" <pete at TECH-KNOW-WARE.COM>
To: <ITU-SG16 at mailbag.cps.intel.com>
Sent: Saturday, May 20, 2000 1:57 PM
Subject: On TD26 - Fast TCS and M/S negotiation in H.323v4


> I note that TD-26 has been accepted to show how TCS can be conveyed in
> parallel with fast start.
>
> However, the example shows the use of call proceeding for receiving TCS
back
> from the remote endpoint.  This is not typically an end-to-end message,
and
> therefore how the procedure works with the gatekeeper routed model needs
to
> be addressed.
>
> Possible solutions are:
>
> 1. Refer to the new text that says it is the responsibility of the
> gatekeeper to forward any tunnelled message for which none is available
> using FACILITY.  (There might be some objection from some to using a
> facility message this early in the call setup process though.)
>
> 2. Restrict the tunnelling (and probably the fast start info) to Alerting,
> Connect and Facility, which generally are end-to-end.  I believe this is
> compatible with the latest procedures for deciding when fast start has
been
> ignored.
>
> Which ever option is chosen, it would also be nice to have a picture for
it
> also!
>
> Pete
>
> =============================================
> Pete Cordell
> pete at tech-know-ware.com
> =============================================
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 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