RE: [Sip] about H.323 and SIP

Henry Sinnreich <henry.sinnreich@wcom.com> Thu, 13 September 2001 21:19 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16200 for <sip-archive@odin.ietf.org>; Thu, 13 Sep 2001 17:19:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA26682; Thu, 13 Sep 2001 17:01:26 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA26651 for <sip@ns.ietf.org>; Thu, 13 Sep 2001 17:01:24 -0400 (EDT)
Received: from dgesmtp01.wcom.com (dgesmtp01.wcom.com [199.249.16.16]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15831 for <sip@ietf.org>; Thu, 13 Sep 2001 17:01:17 -0400 (EDT)
Received: from dgismtp04.wcomnet.com ([166.38.58.144]) by firewall.wcom.com (PMDF V5.2-33 #42260) with ESMTP id <0GJM0065JC6CSQ@firewall.wcom.com> for sip@ietf.org; Thu, 13 Sep 2001 20:42:12 +0000 (GMT)
Received: from dgismtp04.wcomnet.com by dgismtp04.wcomnet.com (PMDF V5.2-33 #42262) with SMTP id <0GJM00801C6ADM@dgismtp04.wcomnet.com>; Thu, 13 Sep 2001 20:42:11 +0000 (GMT)
Received: from hsinnreich ([166.35.226.44]) by dgismtp04.wcomnet.com (PMDF V5.2-33 #42262) with ESMTP id <0GJM005JXC4VBF@dgismtp04.wcomnet.com>; Thu, 13 Sep 2001 20:41:48 +0000 (GMT)
Date: Thu, 13 Sep 2001 15:41:19 -0500
From: Henry Sinnreich <henry.sinnreich@wcom.com>
Subject: RE: [Sip] about H.323 and SIP
In-reply-to: <NEBBIELHMLDIACLLJHCNMEKHDDAA.plong@ipdialog.com>
To: 'Paul Long' <plong@ipdialog.com>, sip@ietf.org
Message-id: <001e01c13c94$82969ea0$2ce223a6@open.wcomnet.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset="US-ASCII"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id RAA26652
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
Content-Transfer-Encoding: 8bit

> H.323 does not use "old-style" circuit-switched thinking. 
> This is SIP propaganda.

H.323 is part of the H.3xx suite and was developed to be compatible with
H.321, H.322, H324 - ISDN, ATM and POTS - all are circuit switched,
propaganda or not.

Its architecture has certainly started with ISDN multimedia.

Henry

Henry Sinnreich
WorldCom
400 International Parkway
Richardson, Texas 75081
USA 

> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On 
> Behalf Of Paul Long
> Sent: Thursday, September 13, 2001 11:17 AM
> To: sip@ietf.org
> Subject: RE: [Sip] about H.323 and SIP
> 
> 
> Peter,
> 
> H.323 does not use "old-style" circuit-switched thinking. 
> This is SIP propaganda.
> 
> Paul Long
> ipDialog, Inc.
> 
> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Na Li
> Sent: Thursday, September 13, 2001 10:12 AM
> To: sip@ietf.org
> Subject: FW: [Sip] about H.323 and SIP
> 
> 
> 
> 
> -----Original Message-----
> From: Peter.Gajdos@proin.com [mailto:Peter.Gajdos@proin.com]
> Sent: Thursday, September 13, 2001 3:51 AM
> To: Na Li
> Subject: Re: [Sip] about H.323 and SIP
> 
> 
> Hi Lina,
> 
> to your questions:
> 
> 1) The fundamental difference is in the model these two use - 
> as you probably know the SIP uses the Internet model - 
> transaction oriented
> (IETF) while H.323 uses "old-style" circtuit switched 
> thinking (ITU-T).
> 
> 2) This is implementation specific. I can say that they are 
> vendors whose equipment can do exactly what you write (incl. 
> the situation when H.323 is replaced by SIP).
> 
> 3) There's no standard, but as far as I remember there is a 
> draft dealing with this: draft-agrawal-sip-h323-interworking-01.txt
> 
> Kind regards
> 
> --Peter
> 
> 
> 
> 
> "Na Li" <lina@ashleylaurent.com>
> Sent by: sip-admin@ietf.org
> 09/13/2001 02:15 AM
> 
>         To:        <sip@ietf.org>
>         cc:
>         Subject:        [Sip] about H.323 and SIP
> 
> 
> 
> Hello,
> 
> I have several questions relating to H.323
> 
> 1) What's the fundamental difference between H.323 (including fast
> setup) and SIP? I don't mean the text encoding or ANS.1 encoding.
> 2) Could Media gateway controller use H.323 for session 
> creation, and use Megaco to communicate with media gateway?
> 3) Is any standard there to map H.323 with SIP?
> 
> Thanks, have a nice day
> 
> Lina
> 
> _______________________________________________
> Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sipping@ietf.org for new developments on the 
> application of sip
> 
> 
> 
> _______________________________________________
> Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sipping@ietf.org for new developments on the 
> application of sip
> 
> 
> _______________________________________________
> Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sipping@ietf.org for new developments on the 
> application of sip
> 


_______________________________________________
Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip