RE: [Sip] about H.323 and SIP

"Rosen, Brian" <Brian.Rosen@marconi.com> Fri, 14 September 2001 19:10 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 PAA24829 for <sip-archive@odin.ietf.org>; Fri, 14 Sep 2001 15:10:26 -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 OAA07467; Fri, 14 Sep 2001 14:25:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07438 for <sip@optimus.ietf.org>; Fri, 14 Sep 2001 14:25:34 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24012 for <sip@ietf.org>; Fri, 14 Sep 2001 14:26:02 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA26698 for <sip@ietf.org>; Fri, 14 Sep 2001 14:24:57 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA17820 for <sip@ietf.org>; Fri, 14 Sep 2001 14:25:02 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21) id <R5ZYD42M>; Fri, 14 Sep 2001 14:24:59 -0400
Message-ID: <313680C9A886D511A06000204840E1CF57C17E@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: sip@ietf.org
Subject: RE: [Sip] about H.323 and SIP
Date: Fri, 14 Sep 2001 14:24:58 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
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

I'd like to ask that this thread be allowed to die.
It serves no purpose germane to the work of the SIP WG.

Brian

> -----Original Message-----
> From: Paul Long [mailto:plong@ipdialog.com]
> Sent: Friday, September 14, 2001 2:22 PM
> To: sip@ietf.org
> Subject: RE: [Sip] about H.323 and SIP
> 
> 
> Michael,
> 
> No, the pregranted ARQ is part of the registration process and is not
> involved with call setup. Let me say it again, call setup can be
> accomplished with a single message, so H.323 is no different 
> than SIP in
> this regard.
> 
> Also, H.323 and SIP have influenced each other, so it's not 
> by any means a
> one-way street.
> 
> Paul Long
> ipDialog, Inc.
> 
> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf 
> Of Michel
> A. Maddux
> Sent: Friday, September 14, 2001 9:52 AM
> To: 'Paul Long'; sip@ietf.org
> Subject: RE: [Sip] about H.323 and SIP
> 
> 
> 
> Paul Long writes:
> 
> If the H.323 endpoint is unregistered or uses the direct call 
> model and
> pregranted ARQs, only a single message (Setup) is necessary 
> in H.323 to
> setup a call.
> --------------
> 
> Hmmm, and yet, the need to have the pre-granted ARQ is part 
> of the call
> setup
> sequence... and in fact, depending upon exactly how the 
> Gatekeeper bandwidth
> management is provided, could itself cause some problems.  
> For example, if
> 1000 endpoints all request a pre-granted ARQ (this is after 
> registration
> sequence
> and etc...), and the Gatekeeper allows only 1000 calls - no 
> calls are in
> progress at that time, and yet the gatekeeper could disallow the next
> request.
> 
> Clearly, pre-granted ARQ and Fast Start are examples of the 
> changes to the
> original H.323 spec which were specifically designed to 
> address the issues
> of excessive message traffic.  My comment to Lina in the 
> original post was
> not intended to describe the many intricacies of the two 
> protocols (because
> I believe that they both have a place in the industry), 
> rather to point out
> what I believe to be the fundamental difference between them 
> - pursuant to
> the question.
> 
> thanks. /m.
> 
> 
> _______________________________________________
> 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