Re: [Sip] PING/PONG

Jonathan Rosenberg <jdrosen@cisco.com> Sat, 04 December 2004 07:02 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21513 for <sip-web-archive@ietf.org>; Sat, 4 Dec 2004 02:02:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaU1q-00019O-0k for sip-web-archive@ietf.org; Sat, 04 Dec 2004 02:08:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CaTkS-0000ay-Rv; Sat, 04 Dec 2004 01:50:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CaTaT-0005wD-ID for sip@megatron.ietf.org; Sat, 04 Dec 2004 01:40:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17701 for <sip@ietf.org>; Sat, 4 Dec 2004 01:40:08 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaTgK-0000f9-R7 for sip@ietf.org; Sat, 04 Dec 2004 01:46:15 -0500
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 03 Dec 2004 22:44:54 -0800
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com [171.71.163.28]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iB46dXAJ016302; Fri, 3 Dec 2004 22:39:33 -0800 (PST)
Received: from [192.168.1.102] (che-vpn-cluster-2-5.cisco.com [10.86.242.5]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AGC78378; Fri, 3 Dec 2004 22:39:31 -0800 (PST)
Message-ID: <41B135A5.1040208@cisco.com>
Date: Fri, 03 Dec 2004 22:57:25 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [Sip] PING/PONG
References: <CD9775120D600F43B9C50329395E9DB64F321F@ivor.citel.com> <13719E43-3D96-11D9-93B0-000D93326732@nostrum.com> <41A43E4D.8020102@cisco.com> <59BC20AE-3E26-11D9-93B0-000D93326732@nostrum.com>
In-Reply-To: <59BC20AE-3E26-11D9-93B0-000D93326732@nostrum.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: sip@ietf.org, Christian Stredicke <Christian.Stredicke@snom.de>, Steve Langstaff <steve.langstaff@citel.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit

inline.

Robert Sparks wrote:

>>
>>> Endpoints behind the things we are wanting to do this refresh things 
>>> to can be signaling
>>> directly with endpoints that aren't (a service provider could let 
>>> people talk to voice-mail
>>> or conference servers directly).
>>
>>
>> I don't see how that practically works in the presence of nat. If you 
>> are using tcp/tls, the thing to which you have a connection open is 
>> the only place from which you can get subsequent requests. Thus, if I 
>> make a call that lands on a voicemail server, the proxy holding my 
>> tcp/tls connection has to be on the signaling path, or it just won't 
>> work.
> 
> 
> If I can establish a tcp/tls connection to that voicemail server, then 
> subsequent requests from it can
> come back down that connection assuming we can keep it alive.

My point is, there may not (indeed, won't be) a connection to that thing 
in the first place. It would need to be established only after the call 
setup is complete. How would the client know to do that? You also have a 
race condition, whereby even if the client knew to do this, a sip 
request could arrive from the voicemail server before the client can 
establish the connection. I'm just not seeing the benefit here.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com


_______________________________________________
Sip mailing list  https://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