Re: [Sip] PING/PONG

Jonathan Rosenberg <jdrosen@cisco.com> Wed, 17 November 2004 16:52 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 LAA18424 for <sip-web-archive@ietf.org>; Wed, 17 Nov 2004 11:52:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUT4z-0005yP-6H for sip-web-archive@ietf.org; Wed, 17 Nov 2004 11:54:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUSxi-0005bZ-J5; Wed, 17 Nov 2004 11:47:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUSr6-0003b9-KV for sip@megatron.ietf.org; Wed, 17 Nov 2004 11:40:28 -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 LAA16954 for <sip@ietf.org>; Wed, 17 Nov 2004 11:40:25 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUStW-0005Xo-CU for sip@ietf.org; Wed, 17 Nov 2004 11:43:00 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 17 Nov 2004 08:55:01 -0800
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com [171.71.163.28]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAHGdg3O012898; Wed, 17 Nov 2004 08:39:42 -0800 (PST)
Received: from [161.44.55.231] (dhcp-161-44-55-231.cisco.com [161.44.55.231]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AFU44516; Wed, 17 Nov 2004 08:39:43 -0800 (PST)
Message-ID: <419B7ECF.1030103@cisco.com>
Date: Wed, 17 Nov 2004 11:39:43 -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: Christian Stredicke <Christian.Stredicke@snom.de>
Subject: Re: [Sip] PING/PONG
References: <B52FDDEC7CBE9D40B36FE900C9AD78B4176DD6@merenge.intern.snom.de>
In-Reply-To: <B52FDDEC7CBE9D40B36FE900C9AD78B4176DD6@merenge.intern.snom.de>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit


Christian Stredicke wrote:

> So my understanding is:
> 
> 1. We should use *only* STUN for refreshing bindings (either UDP or TCP,
> what about TLS)

Yes, TLS too. TLS runs ontop of TCP after all.

> 
> 2. The user agent indicates if it can do it (no negotiation on
> capabilities)
> 
> 3. Refreshing must be done from the client
> 
> Can we agree on that?

Yes.

Server originating refreshing is in the wrong direction. It is the 
client utilizing the service; if it wishes to make use of that service, 
it has to be responsible for refreshing the connection.

-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