Re: [Sip] PING/PONG

"Bob Penfield" <bpenfield@acmepacket.com> Tue, 09 November 2004 12:42 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 HAA19842 for <sip-web-archive@ietf.org>; Tue, 9 Nov 2004 07:42:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRVLa-0001si-KQ for sip-web-archive@ietf.org; Tue, 09 Nov 2004 07:43:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRVJG-0004Gp-FE; Tue, 09 Nov 2004 07:41:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRVBJ-0003gM-NW for sip@megatron.ietf.org; Tue, 09 Nov 2004 07:33:05 -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 HAA19117 for <sip@ietf.org>; Tue, 9 Nov 2004 07:33:04 -0500 (EST)
Received: from s-utl01-dcpop.stsn.com ([63.240.218.73]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRVBu-0001g6-3x for sip@ietf.org; Tue, 09 Nov 2004 07:33:52 -0500
Received: from dcpop.smtp.stsn.com ([127.0.0.1]) by s-utl01-dcpop.stsn.com (SAVSMTP 3.1.0.29) with SMTP id M2004110907324811539 for <sip@ietf.org>; Tue, 09 Nov 2004 07:32:48 -0500
Received: from BPenfield2 ([10.67.87.87]) by dcpop.smtp.stsn.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 9 Nov 2004 07:32:47 -0500
Message-ID: <00b001c4c658$4e32f2c0$5757430a@BPenfield2>
From: Bob Penfield <bpenfield@acmepacket.com>
To: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>, 'Christian Stredicke' <Christian.Stredicke@snom.de>, fluffy@cisco.com
References: <F8EFC4B4A8C016428BC1F589296D4FBF07B0876E@esealnt630.al.sw.ericsson.se>
Subject: Re: [Sip] PING/PONG
Date: Tue, 09 Nov 2004 07:33:23 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-OriginalArrivalTime: 09 Nov 2004 12:32:47.0889 (UTC) FILETIME=[3866A810:01C4C658]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: sip@ietf.org
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: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Christer Holmberg (JO/LMF)"
> But, we also have to remember, that eventhough PING would
> have a response (which CRLC does not have), due to the
> transcation timeout- and re-transmission timers it would
> still take a while (until the transcation expires) to
> figure out that the NAT binding has been closed.
>

With UDP, the PING will create a new NAT binding and the server can update
its mapping for the UA.

With TCP, if you want to be able to detect that the NAT binding is gone on
the order of a transaction timeout, you would need to send a PING every 32
seconds or so. Given that NAT bindings for TCP live longer than that, I
don't see what the CRLF buys you.

cheers,
(-:bob

Robert F. Penfield
Chief Software Architect
Acme Packet, Inc.
130 New Boston Street
Woburn, MA 01801
bpenfield@acmepacket.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