RE: [Sip] PING/PONG

"Steve Langstaff" <steve.langstaff@citel.com> Wed, 17 November 2004 17:31 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 MAA22541 for <sip-web-archive@ietf.org>; Wed, 17 Nov 2004 12:31:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUTgq-00076d-3b for sip-web-archive@ietf.org; Wed, 17 Nov 2004 12:33:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUTWm-0006eE-HN; Wed, 17 Nov 2004 12:23:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUTCV-0000gE-37 for sip@megatron.ietf.org; Wed, 17 Nov 2004 12:02:35 -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 MAA19576 for <sip@ietf.org>; Wed, 17 Nov 2004 12:02:32 -0500 (EST)
Received: from firewall.citel.com ([62.190.107.60] helo=ivor.citel.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CUTEx-0006HU-1q for sip@ietf.org; Wed, 17 Nov 2004 12:05:07 -0500
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Subject: RE: [Sip] PING/PONG
Date: Wed, 17 Nov 2004 16:58:11 -0000
Message-ID: <CD9775120D600F43B9C50329395E9DB64F3213@ivor.citel.com>
Thread-Topic: [Sip] PING/PONG
Thread-Index: AcTMxdvvfCy/R4b+R7CteRr8GeoUkQAALiag
From: Steve Langstaff <steve.langstaff@citel.com>
To: Jonathan Rosenberg <jdrosen@cisco.com>, Christian Stredicke <Christian.Stredicke@snom.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable
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: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: quoted-printable

Should point 2 read "The user agent server indicates if it can respond to client refresh requests"?

--
Steve Langstaff.


-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org]On Behalf Of
Jonathan Rosenberg
Sent: 17 November 2004 16:40
To: Christian Stredicke
Cc: sip@ietf.org
Subject: Re: [Sip] PING/PONG




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

_______________________________________________
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