Re: [quicwg/base-drafts] Keep alive advice (#729)
mirjak <notifications@github.com> Mon, 14 August 2017 10:21 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4AE132194 for <quic-issues@ietfa.amsl.com>; Mon, 14 Aug 2017 03:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 UhrukbY1CHFG for <quic-issues@ietfa.amsl.com>; Mon, 14 Aug 2017 03:21:37 -0700 (PDT)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 183AF132143 for <quic-issues@ietf.org>; Mon, 14 Aug 2017 03:21:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=orIr1HVYNF1MYgV4NQz+Wvwkw/Q=; b=ixm/R+emzCyOGYbi M39lwzR/XO/9SyqVSSjkg09Nrodcijem5I/codpHLJSYbm780O1P/b86St+K82ly Polr7jHSEo0osq4SJMFl2EuToZZldHbGvpKnHEF8o5/MMUjk823hTkNTKSVNjYMC rcPSfLZtpK8gPIezpI1Y/WR7qBM=
Received: by filter0426p1mdw1.sendgrid.net with SMTP id filter0426p1mdw1-20044-599179AC-21 2017-08-14 10:21:32.406934025 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0038p1mdw1.sendgrid.net (SG) with ESMTP id UnUvQeDJRYmPCIuezLyxgw for <quic-issues@ietf.org>; Mon, 14 Aug 2017 10:21:32.162 +0000 (UTC)
Date: Mon, 14 Aug 2017 10:21:32 +0000
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbbd44fca181a02cdff41cd1bdd030bae40fffa2492cf0000000115a93bab92a169ce0ee65d1b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/729/322154733@github.com>
In-Reply-To: <quicwg/base-drafts/issues/729@github.com>
References: <quicwg/base-drafts/issues/729@github.com>
Subject: Re: [quicwg/base-drafts] Keep alive advice (#729)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_599179abdfec6_100c3fc209e7fc38544ca"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3+e7eiYnnawcWyvDwmaNfZPJDIUMZNQdPvkv Lc4PgNkhdJC+Dj+T3+3xssIODp9zRSEvGjAD5VlPYrm83NmZbmxDP0jaYx7r+rpynwohnjweWKCzsc SPH5OTjrs3/iIiMoh3IX0BFRJGVP98BUHBBH/s/oZm7teJQo5BqucG6Y94heVfvXTK3vjXDNM6s9bF c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/3MMdnUHBHD3uzX0EoE9JI92_tj4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Aug 2017 10:21:39 -0000
While this all sounds good, isn't this basically provided by having a connection close signal from the application? Meaning, if the application didn't indicate to close the connection, quic keeps the connection open and by default sends pings every 15-30ms? I guess you can have another interface where the application can change the keep alive interval (and potentially set it infinity to never send any). Further, if no keep-alives are used, there are actually also two options in the case where the application did not close the connection and tries to send something but this fails (because path state is gone). Eiter quic can tell the application that it failed, or it could seamlessly try to reconnect... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/729#issuecomment-322154733
- [quicwg/base-drafts] Keep alive advice (#729) Martin Thomson
- Re: [quicwg/base-drafts] Keep alive advice (#729) mirjak
- Re: [quicwg/base-drafts] Keep alive advice (#729) ianswett
- Re: [quicwg/base-drafts] Keep alive advice (#729) janaiyengar
- Re: [quicwg/base-drafts] Keep alive advice (#729) Martin Thomson
- Re: [quicwg/base-drafts] Keep alive advice (#729) janaiyengar