Hi everyone,
If I am not wrong, the discussions and the benefits of IMTC groups are more or less restricted to IMTC members. And to become a IMTC member, it costs $7500 anually which will restrict the open contribution from small companies and enthusiastic fellows.
As mentioned by Radhika, the purpose is to come out with a proposal which is widely accepted and commented by a large community. So , I would rather prefer SG16 to be a better place of discussion.
I would like to have the views of other members also from this group.
Best Regards Vipin Palawat
----- Original Message ----- From: Roy, Radhika R, ALARC rrroy@ATT.COM To: ITU-SG16@mailbag.cps.intel.com Sent: Wednesday, March 08, 2000 9:57 PM Subject: Re: FYI - SIP-H.323 Interworking BOF
Hi, Everyone:
ITU-T and IETF are the formal standard bodies to create standards for
H.323
and SIP, respectively, and the interworking standard between the two is
also
a part of it..
However, all inputs from other organizations will definitely be welcomed.
Best regards, Radhika R. Roy AT&T
-----Original Message----- From: Euchner Martin [SMTP:Martin.Euchner@MCHP.SIEMENS.DE] Sent: Wednesday, March 08, 2000 4:16 AM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Re: FYI - SIP-H.323 Interworking BOF
just for your information for those interested in H.323/SIP:
I would like to draw your attention to an activity group already
debating
H.323-SIP interworking for quite a while: IMTC aHIT!. To my knowledge
they
already came out with some first results on architectures and
interworking
scenarios. Please get in touch with this group and consider their
results.
see also http://www.imtc.org/act_ahit.htm http://www.imtc.org/act_ahit.htm and discussions on their mailing list.
Thus, it appears to me that there are already quite a few groups (IETF, IMTC, ETSI) discussing H323/SIP interworking. I do not quite see
necessity
to have ITU-T SG16 as yet another group for this topic.
regards
Martin.
| Dipl.-Inf. Phone: +49 89 636-46201 | Martin Euchner Fax : +49 89 636-48000 | Siemens AG | ZT IK 3 mailto:Martin.Euchner@mchp.siemens.de | mailto:martin.euchner@ties.itu.int | Otto-Hahn-Ring 6 Intranet:
http://zt-security.mchp.siemens.de/de/Competence/Standardization/ITU-T_SG1
6/ index.html | D-81730 Muenchen Internet: http://www.siemens.de | __________________ | Germany
-----Original Message----- From: Joon Maeng [SMTP:joon_maeng@VTEL.COM] Sent: Saturday, March 04, 2000 6:56 PM To: ITU-SG16@mailbag.cps.intel.com Subject: Re: FYI - SIP-H.323 Interworking BOF Roy, you your are right. It is focused on the SIP and H.323interworking. I attached the tentative agenda for the BOF. Depending on the speakers we identify, the agenda may inlcude some presenters but the main focus will not be modified. Regards, Joon
BOF: SIP and H.323 Interworking (sip323) Area: Transport Time requested: one 1 hour slot Chairs: Joon Maeng <joon_maeng@vtel.com> Dave Walker <drwalker@ss8networks.com> Description: There are two competing standards in the industry for
establishing
and managing real-time interactive media communications over IP.
One
is the proposed IETF standard, Session Initiation Protocol (RFC 2543), and the other is the ITU recommendation, H.323. Although they use the same protocol (RTP) for media streaming, they cannot establish calls between them. In the absence of any formal interoperability standards, many vendors are beginning to develop proprietary application
gateways
for interworking between SIP and H.323.
In order to provide interoperability between the two standards,
it
is urgent to define a common interworking specifications for the industry. The recognition of the need for this interworking specification has lead to calls for its development from both manufacturers and service providers, individually and through industry consortia (such as IMTC) and other bodies concerned with interoperability (such as ETSI).
In this BOF, we are going to discuss SIP and H.323 interworkingissues, execution plans and the scope of the work.
Agenda: - Do we need SIP-H.323 interworking? - Coordination with other groups? - Scope of interworking - Outcome of the work? - Suggestions? Helpful reading: - draft-singh-sip-h323-00.txt - SIP: Session Initiation Protocol (RFC 2543) - SDP: Session Description Protocol (RFC 2327) - ITU recommendations: H.323, H.225.0, H.245 > -----Original Message----- > From: Roy, Radhika R, ALARC [mailto:rrroy@att.com] > Sent: Friday, March 03, 2000 3:12 PM > To: ITU-SG16@mailbag.cps.intel.com > Subject: Re: FYI - SIP-H.323 Interworking BOF > > > Hi, Everyone: > > It appears that BOF is focused only on SIP-H.323 Interworking(not > H.323-Internet Interworking as titled by Orit). I guess that > Joon and Dave > will clarify this better. > > Best regards, > Radhika R. Roy > AT&T > > > -----Original Message----- > > From: Orit Levin [SMTP:orit@radvision.com] > > Sent: Friday, March 03, 2000 3:57 PM > > To: ITU-SG16@MAILBAG.INTEL.COM > > Subject: Re: FYI - SIP-H.323 Interworking BOF > > > > Great! > > I am attaching the revised so far TOR. Please, send your comments. > > Hope you will find it useful in Australia. > > 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: Joon Maeng joon_maeng@VTEL.COM > > To: ITU-SG16@MAILBAG.INTEL.COM ITU-SG16@MAILBAG.INTEL.COM > > Date: Thursday, March 02, 2000 8:18 PM > > Subject: FYI - SIP-H.323 Interworking BOF > > > > > > >Hi folks. There will be a SIP-H.323 Interworking BOF at > the IETF meeting > > in > > >Australia. Dave Walker with SS8 Networks and I will chair > the BOF. You > > can > > >find the agenda at http://www.ietf.org/meetings/IETF-47.html when IETF > posts > >agendas. > >Regards, > >Joon << File: H323-Internet.zip >>