Orit, I am a bit confused on what should be done here. I have only found in TD-74 (ITU-T SG16 Working Party 2 Report) the following passages:

"D.352(2/16) [Various] - H.323 SIP Interworking

This document calls for a joint ITU-T/IETF study of H.323/SIP interworking.

D.413(2/16) [Canada] - Interworking Between H.323 and SIP Networks

This calls for the creation of an interoperability question in SG16, that would cover among other things, H.323/SIP interworking.

With regard to both D.352/D.413, it was noted that there are several versions of SIP, it is hard to start any work to interoperate with SIP as SIP is ill-defined at this point in time. The wisdom of starting a new question near the end of the study period was also questioned. It was also mentioned that a great deal of work needs to be done in terms of defining the procedures and architecture that would apply to this work. One suggestion is that interoperability should be between standards bodies such as the ITU and IETF, and this should be the focus of the work, i.e. that

target is official IETF RFCs and not SIP type documents produced by various other bodies. There were various expressions of support that this should be studied, and contributions related to architectures and priorities are solicited. It was agreed that contributions should address both Q13 and Q14."

Is there anything else as "Mission Statement" for the interim work?

Regards, Istvan

-------------------------------------------------------------------------- Dr. Istvan Sebestyen Siemens AG, ICN M CS27, Hofmannstr. 51 D-81359 Munich Tel:+49-89-722-47230 Fax:+49-89-722-47713 E-Mail office: istvan.sebestyen@icn.siemens.de; istvan@sebestyen.de E-mail private: istvan_sebestyen@yahoo.com; Siemens Intranet:http://netinfo.icn.siemens.de/es/team/essp/team/essp4 Siemens FTP: ftp://mchhpn006a.mch.pn.siemens.de ---------------------------------------------------------------------------

Hello Sebestyen! There is additional chapter from Q.14 Report with the same meaning, but I am sure it doesn't answer your question. During Geneva meeting additional related aspects were discussed. In my previous mail I was referring to the attached paper. (You will find references to relevant contributions in this paper.) Currently this paper is one of the opinions and possible directions. We are having this discussion on the list in order to get an understanding of the work we would like to pursue and prepare contributions for Osaka meeting. 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 -----Original Message----- From: Sebestyen Istvan ICN M CS 27 <Istvan.Sebestyen@icn.siemens.de> To: ITU-SG16@mailbag.cps.intel.com <ITU-SG16@mailbag.cps.intel.com>; 'Orit Levin' <orit@radvision.com> Date: Thursday, February 24, 2000 2:02 PM Subject: RE: [H.323-SIP/Internet] The reason. the -

----------------

...

---------- From: Orit Levin[SMTP:orit@radvision.com] Reply To: Orit Levin Sent: Thursday, February 24, 2000 6:53 PM To: ITU-SG16@mailbag.cps.intel.com Subject: [H.323-SIP/Internet] The reason.

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