RE: [Sip] PING/PONG
"Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com> Tue, 09 November 2004 13: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 IAA21559 for <sip-web-archive@ietf.org>; Tue, 9 Nov 2004 08:02:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRVdv-0002UI-EN for sip-web-archive@ietf.org; Tue, 09 Nov 2004 08:02:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRVWa-0006IT-ID; Tue, 09 Nov 2004 07:55:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRVV8-000656-Rl for sip@megatron.ietf.org; Tue, 09 Nov 2004 07:53:34 -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 HAA20932 for <sip@ietf.org>; Tue, 9 Nov 2004 07:53:29 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRVVe-0002Aq-Ul for sip@ietf.org; Tue, 09 Nov 2004 07:54:17 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119]) by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id iA9CrIh5001571 for <sip@ietf.org>; Tue, 9 Nov 2004 13:53:18 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 9 Nov 2004 13:53:18 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72) id <WFZ21LM2>; Tue, 9 Nov 2004 13:53:17 +0100
Message-ID: <F8EFC4B4A8C016428BC1F589296D4FBF07B08772@esealnt630.al.sw.ericsson.se>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: 'Bob Penfield' <bpenfield@acmepacket.com>, 'Christian Stredicke' <Christian.Stredicke@snom.de>, fluffy@cisco.com
Subject: RE: [Sip] PING/PONG
Date: Tue, 09 Nov 2004 13:52:58 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
X-OriginalArrivalTime: 09 Nov 2004 12:53:18.0660 (UTC) FILETIME=[15FF6840:01C4C65B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
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: 9ed51c9d1356100bce94f1ae4ec616a9
Hi, >With UDP, the PING will create a new NAT binding and the >server can update its mapping for the UA. So will CRLF, won't it? The difference is that the UA will not be informed that the message has reached the destination (since there is no response), but the question is if we really would need that information for every keep-nat-binding message that we send (ie we use CRLF most of the time, and every now and then we use a SIP request to make sure that everything really works). >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. My point was that using PING you will not be able to detect problems immediately, since you will have to wait for the transaction timeout before you can determine that something is wrong. What I do NOT want to do is to send SIP requests too often, and therefor I was wondering if it would be possible to also use CRLF :) Regards, Christer Holmberg Ericsson Finland > > 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
- [Sip] PING/PONG Christian Stredicke
- RE: [Sip] PING/PONG Christer Holmberg (JO/LMF)
- RE: [Sip] PING/PONG Steve Langstaff
- Re: [Sip] PING/PONG Bob Penfield
- RE: [Sip] PING/PONG Christer Holmberg (JO/LMF)
- RE: [Sip] PING/PONG Christian Stredicke
- Re: [Sip] PING/PONG Bob Penfield
- RE: [Sip] PING/PONG Chris Boulton
- RE: [Sip] PING/PONG Christian Stredicke
- RE: [Sip] PING/PONG Steve Langstaff
- RE: [Sip] PING/PONG Christian Stredicke
- RE: [Sip] PING/PONG Chris Boulton
- RE: [Sip] PING/PONG Steve Langstaff
- Re: [Sip] PING/PONG Spencer Dawkins
- RE: [Sip] PING/PONG Christian Stredicke
- Re: [Sip] PING/PONG Klaus Darilion
- Re: [Sip] PING/PONG Jonathan Rosenberg
- [Sip] How to get old messages on archives!! vikram bhuskute
- RE: [Sip] PING/PONG Christian Stredicke
- Re: [Sip] PING/PONG Jonathan Rosenberg
- RE: [Sip] PING/PONG Steve Langstaff
- RE: [Sip] PING/PONG Christian Stredicke
- RE: [Sip] PING/PONG Steve Langstaff
- Re: [Sip] PING/PONG Jonathan Rosenberg
- Re: [Sip] PING/PONG Charles Eckel
- Re: [Sip] PING/PONG Jonathan Rosenberg
- Re: [Sip] PING/PONG Robert Sparks
- Re: [Sip] PING/PONG Jonathan Rosenberg
- Re: [Sip] PING/PONG Robert Sparks
- Re: [Sip] PING/PONG Jonathan Rosenberg
- Re: [Sip] PING/PONG Robert Sparks
- Re: [Sip] PING/PONG Jonathan Rosenberg
- Re: [Sip] PING/PONG Robert Sparks