Hi! I would like to highlight the reason of "H.323-XXX" work in ITU-T as described in the initial paper.
H.323 is NOT new to Internet. Internet is evolving and new specifications in "IP telephony" area are being defined in IETF. This is a time to consider each one of these specifications to be applied to H.323. If found useful from technical point of view (as a kind of Back End Services) or just as required for interworking purposes (such as H.323-SIP scenarios), standard definitions for H.323 should be formulated. These two are connected since the first definitely helps the second.
The written above agenda is a proposal for the work scope. Based on our discussions, it seems like more then one company would like to see this work beyond the topic of H.323-SIP interoperability. (forget the name :-) ) If we agree that standardization is needed for this kind of work, the only possible way to do it is to participate in ITU-T process (with all its meaning).
Currently we are in the beginning of the process sorting out topics of our interest. I think most of us are aware of the work being done in other organizations. We would like to see experts (including from TIPHON and IETF) presenting their concepts to ITU (starting from the mailing list) keeping us from repeating their work and being aligned with them.
Best Regards, Orit Levin RADVision Inc. 575 Corporate Drive Suite 420 Mahwah, NJ 07430 Tel: 1 201 529 4300 (230) Fax: 1 201 529 3516 www.radvision.com orit@radvision.com