Re: [core] #394 (coap-tcp-tls): Ping/pong
Carsten Bormann <cabo@tzi.org> Mon, 13 June 2016 13:07 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2788F12D783; Mon, 13 Jun 2016 06:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NIsiliplpzxJ; Mon, 13 Jun 2016 06:07:28 -0700 (PDT)
Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [IPv6:2001:4b98:c:538::194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CD0212D607; Mon, 13 Jun 2016 06:07:28 -0700 (PDT)
Received: from mfilter44-d.gandi.net (mfilter44-d.gandi.net [217.70.178.175]) by relay2-d.mail.gandi.net (Postfix) with ESMTP id 7BFBDC5ABE; Mon, 13 Jun 2016 15:07:26 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter44-d.gandi.net
Received: from relay2-d.mail.gandi.net ([IPv6:::ffff:217.70.183.194]) by mfilter44-d.gandi.net (mfilter44-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 5JEyJ5yvomJh; Mon, 13 Jun 2016 15:07:25 +0200 (CEST)
X-Originating-IP: 134.226.52.39
Received: from nar-3.local (csopen.scss.tcd.ie [134.226.52.39]) (Authenticated sender: cabo@cabo.im) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 93984C5A83; Mon, 13 Jun 2016 15:06:51 +0200 (CEST)
Message-ID: <575EAFEA.4040604@tzi.org>
Date: Mon, 13 Jun 2016 14:06:50 +0100
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>
References: <054.2c97c757dda98e52472c800c6ee42ad0@trac.tools.ietf.org> <069.ebec57bc2f93f5436f4ed043b753cade@trac.tools.ietf.org> <69F643BF912B4BB7BA09F160EACAB6EE@WeiGengyuPC> <4EBB3DDD0FBF694CA2A87838DF129B3C017D5668@DEFTHW99EL4MSX.ww902.siemens.net>
In-Reply-To: <4EBB3DDD0FBF694CA2A87838DF129B3C017D5668@DEFTHW99EL4MSX.ww902.siemens.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/7cDhB2gidYNyR6oo9KvLgTP9QlY>
Cc: "core@ietf.org" <core@ietf.org>, "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "trac+core@zinfandel.tools.ietf.org" <trac+core@zinfandel.tools.ietf.org>
Subject: Re: [core] #394 (coap-tcp-tls): Ping/pong
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2016 13:07:30 -0000
Right; as the draft says, just about any transport (TCP, TLS, Websocket) already has a keepalive; it just turns out those may be hard to reach (or not working very well) in some implementations. The very simple method of sending and then ignoring empty messages should provide enough of a keepalive for most applications that need just that and can't get it from transport. Ping/pong really is more of an application-layer thing (in particular with the custody option), so it is definitely not being replaced by keepalive at any layer (transport or CoAP). Right now people are doing ping/pong by designating a resource they post to; this of course will continue to work -- it may just be too much work in the general case to find the specific resource that has been designated for this. But it is useful to keep this in mind before inventing too much to add to ping/pong -- specialized resources may be much better for those more specialized purposes. Grüße, Carsten
- Re: [core] #394 (coap-tcp-tls): Ping/pong core issue tracker
- Re: [core] #394 (coap-tcp-tls): Ping/pong core issue tracker
- Re: [core] #394 (coap-tcp-tls): Ping/pong weigengyu
- Re: [core] #394 (coap-tcp-tls): Ping/pong weigengyu
- Re: [core] #394 (coap-tcp-tls): Ping/pong weigengyu
- [core] #394 (coap-tcp-tls): Ping/pong core issue tracker
- Re: [core] #394 (coap-tcp-tls): Ping/pong core issue tracker
- Re: [core] #394 (coap-tcp-tls): Ping/pong Julien Vermillard
- Re: [core] #394 (coap-tcp-tls): Ping/pong Klaus Hartke
- Re: [core] #394 (coap-tcp-tls): Ping/pong Carsten Bormann
- Re: [core] #394 (coap-tcp-tls): Ping/pong Hannes Tschofenig
- Re: [core] #394 (coap-tcp-tls): Ping/pong Hannes Tschofenig
- Re: [core] #394 (coap-tcp-tls): Ping/pong Carsten Bormann
- Re: [core] #394 (coap-tcp-tls): Ping/pong core issue tracker
- Re: [core] #394 (coap-tcp-tls): Ping/pong core issue tracker
- Re: [core] #394 (coap-tcp-tls): Ping/pong weigengyu
- Re: [core] #394 (coap-tcp-tls): Ping/pong Kovatsch, Matthias
- Re: [core] #394 (coap-tcp-tls): Ping/pong Carsten Bormann
- Re: [core] #394 (coap-tcp-tls): Ping/pong Michael Koster
- Re: [core] #394 (coap-tcp-tls): Ping/pong Carsten Bormann
- Re: [core] #394 (coap-tcp-tls): Ping/pong Michael Koster
- Re: [core] #394 (coap-tcp-tls): Ping/pong Carsten Bormann
- Re: [core] #394 (coap-tcp-tls): Ping/pong Kovatsch, Matthias