Re: [Sip] PING/PONG [bcc][faked-from][heur] [mx][spf]

Cullen Jennings <fluffy@cisco.com> Sat, 11 December 2004 19:37 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 OAA12930 for <sip-web-archive@ietf.org>; Sat, 11 Dec 2004 14:37:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdDBL-0000b5-BW for sip-web-archive@ietf.org; Sat, 11 Dec 2004 14:45:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdCvA-00074x-S2; Sat, 11 Dec 2004 14:28:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdCti-0006kB-JS for sip@megatron.ietf.org; Sat, 11 Dec 2004 14:27:22 -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 OAA12292 for <sip@ietf.org>; Sat, 11 Dec 2004 14:27:16 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdD19-0000Oi-QB for sip@ietf.org; Sat, 11 Dec 2004 14:35:01 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-5.cisco.com with ESMTP; 11 Dec 2004 11:27:14 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBBJQe5M018816; Sat, 11 Dec 2004 11:26:41 -0800 (PST)
Received: from [10.0.1.3] (sjc-vpn1-439.cisco.com [10.21.97.183]) by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AUR49215; Sat, 11 Dec 2004 11:26:42 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Sat, 11 Dec 2004 05:34:28 -0800
Subject: Re: [Sip] PING/PONG [bcc][faked-from][heur] [mx][spf]
From: Cullen Jennings <fluffy@cisco.com>
To: Christian Jansson <christian.jansson@hotsip.com>, Spencer Dawkins <spencer@mcsr-labs.org>, Christian Stredicke <Christian.Stredicke@snom.de>
Message-ID: <BDE03764.1E29A%fluffy@cisco.com>
In-Reply-To: <B7192C0D8D60754DADA9E22294C573696316D3@mailserver.hotsip.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.7 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: "sip@ietf.org" <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.7 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

On 11/12/04 4:00 AM, "Christian Jansson" <christian.jansson@hotsip.com>
wrote:

> I'm not sure how often keep-alives have to be sent over TCP to ensure
> that NAT/FWs do not remove the state. Preferabely NAT/FWs never remove
> the state, but I have heard that it happens. Does anyone have a
> reference to test statistics of NAT/FWs behavior? The keep-alive default
> interval should probably be set just below the shortest of all detected
> values.

Have not done extensive testing but on the ones I have tested, it has been
around 7200 seconds, and the default TCP keep alive in most OS is also 7200
seconds so they are matched and you can ignore it. I imagine they are not
all this way. The argument for TCP CRLF has been to detect the "liveness" of
the connection for reliably - not so much an argument for nat state refresh


_______________________________________________
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