Re: [core] #395 (coap-tcp-tls): Session resumption
"core issue tracker" <trac+core@zinfandel.tools.ietf.org> Tue, 05 April 2016 02:50 UTC
Return-Path: <trac+core@trac.tools.ietf.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 C0BB112D651; Mon, 4 Apr 2016 19:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 JtZk3ZW5tT2S; Mon, 4 Apr 2016 19:50:16 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34E4912D63D; Mon, 4 Apr 2016 19:50:16 -0700 (PDT)
Received: from localhost ([::1]:43125 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+core@trac.tools.ietf.org>) id 1anH4K-0007jN-29; Mon, 04 Apr 2016 19:50:16 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: core issue tracker <trac+core@zinfandel.tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: draft-ietf-core-coap-tcp-tls@ietf.org, Hannes.Tschofenig@gmx.net
X-Trac-Project: core
Date: Tue, 05 Apr 2016 02:50:16 -0000
X-URL: https://tools.ietf.org/core/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/wg/core/trac/ticket/395#comment:1
Message-ID: <069.8b1d47a2e85bb9e67c3581bf4f771043@trac.tools.ietf.org>
References: <054.c9e708f420e3b5d1c3d469cf6a66a31c@trac.tools.ietf.org>
X-Trac-Ticket-ID: 395
In-Reply-To: <054.c9e708f420e3b5d1c3d469cf6a66a31c@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-core-coap-tcp-tls@ietf.org, Hannes.Tschofenig@gmx.net, core@ietf.org
X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: draft-ietf-core-coap-tcp-tls@ietf.org
Resent-Message-Id: <20160405025016.34E4912D63D@ietfa.amsl.com>
Resent-Date: Mon, 04 Apr 2016 19:50:16 -0700
Resent-From: trac+core@trac.tools.ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/i9CufHls4WoB8rjzvgKr5Z-RGYA>
Cc: core@ietf.org
Subject: Re: [core] #395 (coap-tcp-tls): Session resumption
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: trac+core@zinfandel.tools.ietf.org
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: Tue, 05 Apr 2016 02:50:18 -0000
#395: Session resumption Comment (by Hannes.Tschofenig@gmx.net): In http://www.ietf.org/mail-archive/web/core/current/msg06909.html Hannes assumed that the question was about TLS session resumption. Instead the question focused on TCP, as Klaus clarified in http://www.ietf.org/mail- archive/web/core/current/msg06948.html ------------------- > When DTLS / TLS client communicates with a server then it typically > establishes a session cache to allow session resumption. [...] To clarify, the question is about sessions at the CoAP level, not at the DTLS/TLS level. Should it be possible to send a CoAP request, close the TCP connection, reconnect and receive the response? ------------- Both Klaus and Carsten subsequently agree that there is no expectation that a re-connect from the client would allow it to retrieve (buffered) data. Instead the connection lifetime is bound to the TCP connection. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-core-coap-tcp- hartke@tzi.org | tls@ietf.org Type: protocol | Status: new enhancement | Milestone: Priority: minor | Version: Component: coap-tcp- | Resolution: tls | Severity: Active WG | Document | Keywords: | -------------------------+------------------------------------------------- Ticket URL: <https://trac.tools.ietf.org/wg/core/trac/ticket/395#comment:1> core <https://tools.ietf.org/core/>
- Re: [core] #395 (coap-tcp-tls): Session resumption core issue tracker
- [core] #395 (coap-tcp-tls): Session resumption core issue tracker
- Re: [core] #395 (coap-tcp-tls): Session resumption core issue tracker
- Re: [core] #395 (coap-tcp-tls): Session resumption core issue tracker
- Re: [core] #395 (coap-tcp-tls): Session resumption core issue tracker
- Re: [core] #395 (coap-tcp-tls): Session resumption core issue tracker