H.323 watershed

[Paul Long]

I think I'm going to puke. :-@ Built-in, purposeful non-backwards
compatibility! Alright! We've come close in the past, but this time we hit
it on the nail:

8.1.7.2 "An H.323 Version 4 or higher entity that uses Fast Connect in a
call shall use H.245 tunneling when an H.245 Control Channel is required and
shall always set the h245Tunneling field to TRUE. The process for switching
to a separate H.245 connection is described in 8.2.3 and may be used by
Version 3 or older entities or by newer H.323 entities when communicating
with Version 3 or older entities for the purpose of maintaining backward
compatibility."

First of all, "...when an H.245 Control Channel is required..." is redundant
and should be removed because an H.245 channel is _always_ required:
6.2.8/H.323v4: "The endpoint shall establish exactly one H.245 Control
Channel for each call that the endpoint is participating in." But mainly, v4
and post-v4 EPs are not interoperable with pre-v4 EPs that do not support
Fast Connect. Wave goodbye to NetMeeting! :-)

Paul Long
ipDialog

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